SliTaz SliTaz Forum

You are not logged in.

#1 2011-12-16 14:01:13

gustavolwalker
Member
Registered: 2011-06-17
Posts: 4

Block Xterm Upgrade : xterm-276.tazpkg missing files on cooking repo

Estou usando a versão cooking 20110531 e hoje quando fiz o upgrade pelo tazpkg o xterm sumiu, verifiquei na lista de atualizações e realmente foi atualizado, contato o mesmo não existe mais após a atualização (2011-12-16).

Offline

#2 2011-12-16 15:50:35

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Block Xterm Upgrade : xterm-276.tazpkg missing files on cooking repo

To fix:

Boot into cooking iso you installed from.

#tazpkg repack xterm

Save repacked xterm tazpkg to disk.

Boot into install with broken xterm.

ctrl+alt F2

Logon as root password: root

#tazpkg install /path/to/repacked /xterm-xxx.tazpkg --forced

ctrl+alt F7

Open xterm

#tazpkg block xterm

Offline

#3 2011-12-16 16:56:04

gustavolwalker
Member
Registered: 2011-06-17
Posts: 4

Re: Block Xterm Upgrade : xterm-276.tazpkg missing files on cooking repo

Now xterm is work, but I test more applications after upgrade and not work, example is "Slitaz Panel", "tazx" don't running graphical mode, basically any programs to configuring Slitaz.

Offline

#4 2011-12-18 01:53:39

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Block Xterm Upgrade : xterm-276.tazpkg missing files on cooking repo

Slitaz Panel / TazPanel Troubleshooter

All commands in xterm:

tazweb

Does tazweb open ?

Yes, Ctrl+c

tazweb http://tazpanel:82

No:

midori http://tazpanel:82

Browser opens,you see TazPanel Authentication,login to Tazpanel.

Problem is tazweb, post tazweb error messages in reply.

Browser opens, you see error:

Cannot resolve hostname (tazpanel)

#leafpad /etc/hosts

Add tazpanel to hosts file:

127.0.0.1   localhost slitaz tazpanel

Reload/refresh browser

Cannot connect to destination (tazpanel)

#tazpanel start

Reload/refresh browser you see TazPanel Authentication,login to Tazpanel.

Tazpanel web server should autostart on boot by /etc/init.d/system.sh

Check  system.sh (owned by slitaz-boot-scripts.tazpkg)and that it is listed in the correct order in /etc/rcS.conf

#leafpad /etc/rcS.conf

RUN_SCRIPTS="bootopts.sh network.sh system.sh local.sh"

Offline

#5 2011-12-23 08:39:41

Guest
Guest

Re: Block Xterm Upgrade : xterm-276.tazpkg missing files on cooking repo

hello,

first sorry for my poor english

i had this problem a week ago, when i upgrade my fresh install. Slitaz was not able to find xterm. (I had also problems to recharge list of applications)

This morning I reinstall slitaz (last cooking). i upgrade in console (it doesn't work in tazpanel). xterm is installed with a new icon and work.

BUT when i put login and password in TazPanel Authentication ,it reappear always.

console say:

'root@slitaz:~# tazweb http://tazpanel:82

libp11-kit.so.0: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type

Failed to load module: /usr/lib/gio/modules/libgiognutls.so'

I've check the files decribe above, No problem.

Another problem after upgrading:pcman work but disappear from the menu.

thanks for replies

#6 2011-12-23 20:25:20

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Block Xterm Upgrade : xterm-276.tazpkg missing files on cooking repo

The build server crashed December 10 and distributed bad tazpkgs onto the mirrors. Since the crash I don't upgrade anything without repacking the version on my system first for backup/restore.You can also repack from livecd as described in my first reply.The tazpkgs that cannot be repacked like busybox, don't upgrade without backing up your entire install.

Try this:

#tazpkg get-install p11-kit

If username/password still fails with tazpanel:

# sed -i 's/:root:.*/:root:*/' /etc/slitaz/httpd.conf

And tazpanel should use your root account password.

Repack pcmanfm from livecd,it's bad on mirror and cook.slitaz.org/packages

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]