can't get KDE pannel in Megapup003 (solved)

Using applications, configuring, problems
Post Reply
Message
Author
User avatar
eponyn
Posts: 31
Joined: Mon 24 Jul 2006, 08:36

can't get KDE pannel in Megapup003 (solved)

#1 Post by eponyn »

I'm running puppy 2.01 kernel 2.6.16.7 with megapup003 and I am having problems with KDE and the panel. Every other program from the megapup003 launcher is working except that if I click on the KDE pannel alone nothing happens and if try to switch to KDE when Xrestarts the monitor goes blank and the computer freezes, needing a hardboot. The only files in my /mnt/home directory are megapup003_201.sfs, pup_save.3fs and devx-qt-renamed_201.sfs.
The computer running it is an AMD64 X2 Dualcore 4200+ with 1GB RAM
Any ideas would be much appreciated
Last edited by eponyn on Mon 31 Jul 2006, 15:48, edited 1 time in total.

User avatar
Béèm
Posts: 513
Joined: Sun 16 Apr 2006, 16:18
Location: Brussels

#2 Post by Béèm »

Sorry I can't help you with this problem, but I am with having the same problem in 2.01
Now I am in 2.02 and the problem still persists.

I found reference http://www.murga.org/%7Epuppy/viewtopic.php?t=6771 for another 900MB megapup file, but the website referenced isn't accessable.
Puppy Linux 2.02 SMkey, KDE354mini, wine0.9.20, devx-qt-renamed.
Puppy Linux 2.10r1 SMkey, JWM, devx_qt_renamed_210, KDE355mini

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#3 Post by MU »

run the
/usr/local/megapup003/megapup003-launcher
from a consolewindow, then click on the button.
This should display some helpfull errormessages, please copy them in your next reply.
Mark

User avatar
eponyn
Posts: 31
Joined: Mon 24 Jul 2006, 08:36

#4 Post by eponyn »

Ok I did as you asked and this is what I get:

sh-3.00# sh: kicker: command not found

Thanks

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#5 Post by MU »

please look, if you have these 2 files:
/etc/kderc

/opt/kde/bin/kicker

Mark

User avatar
eponyn
Posts: 31
Joined: Mon 24 Jul 2006, 08:36

#6 Post by eponyn »

yes they were there. I clicked directly on the /opt/kde/bin/kicker and got the KDE pannel up and running. It still won't go from the launcher, but I can make a shortcut to this one in my desktop for it to work. Thanks much!

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#7 Post by MU »

Maybe you upgraded Puppy from 2.00 to 2.01, what overwrote /etc/.profile.

You can delete /etc/kderc , then run megapup-launcher again, this will add the search-path to /etc/profile again and create a new kderc.

Mark

User avatar
eponyn
Posts: 31
Joined: Mon 24 Jul 2006, 08:36

#8 Post by eponyn »

2.01 is the first puppy I use on this computer, yy old computer was running 1.0.8. Would moving from 2.01r1 to 2.01r2 have the same problem? I had the KDE panel for a while until I put the wrong disk on with 2.01r1. When I rebooted with the r2 the problems started, infact everytime I try to leave reboot or restart X, the computer freezes and I have to do a hard boot.
I tried deleting /etc/kderc and running the launcher, but it is still the same. Is a reboot needed for the changes to take effect?

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#9 Post by MU »

yes, any Puppy-upgrade seems to overwrite /etc/profile.

A reboot is needed for the changes of my launcher to take effect.
Mark

User avatar
eponyn
Posts: 31
Joined: Mon 24 Jul 2006, 08:36

#10 Post by eponyn »

I'm having the problem with not being able to reboot properly so the chages do not get saved to the pup_save.sfs aparently. Everything else in puppy seems to be working fine but all the choices from the shutdown menu, from JMW restart, to power off, make the screen go bacl immediately and it freezes without running the shutdown scripts. even the symlinks I created the last session are not there anymore on the desktop. Is there a way to see any error messages at shutdown?

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#11 Post by MU »

run in a consolewindow "sync" to force, that all changes are written to the harddrive.

Then hit CTRL-ALT-Backspace to exit X.
Then type "reboot" or "halt" or "poweroff" to see possible errors, but they might pass too fast, but maybe you can see something suspicious.

Mark

User avatar
eponyn
Posts: 31
Joined: Mon 24 Jul 2006, 08:36

#12 Post by eponyn »

Awesome! The first time, I did what you said and even though it gave me a message about not been able to unmount / it rebooted fine. repeated the process of deleting kderc, and sync. this time the reboot had no failures and now I can access KDE panel from the launcher. Thanks, so much! you rock!

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#13 Post by MU »

ok, so I wonder why your reboot does not work proper from JWM.

Look in /root/.jwmrc with a texteditor, it should have this line:

Code: Select all

   <Program label="Reboot computer" icon="mini-turn.xpm">exec /usr/X11R6/bin/wmreboot</Program>
Then look in /usr/X11R6/bin/wmreboot

It should look like this:

Code: Select all

#!/bin/sh
#introduced v0.9.8
#called from /root/.fvwm95rc, .jwmrc at shutdown.

echo -n "reboot" > /tmp/wmexitmode.txt
sync
#PSLIST="`ps`"
#kill `echo "$PSLIST" |grep "X "|grep -v "grep"|sed "s/^\ *//"|sed "s/ .*$//"|head -n 1`
#exec killall X
killall X #default is SIGTERM.
sleep 1           #v1.0.7
exec killall -9 X #v1.0.7 make sure X is killed.

#after exit from X, there is a return to /usr/X11R6/bin/xwin,
#which reads /tmp/wmexitmode.
If that is different on your system, something got broken during your upgrade.
In that case correct the entries as above.
But I would wonder, as I upgraded, too to r2.

If everything is identical, it might be a little bit more complicated, we had to add some more lines to wmreboot, that unmount all drives and run "reboot" then.

Mark

User avatar
eponyn
Posts: 31
Joined: Mon 24 Jul 2006, 08:36

#14 Post by eponyn »

I checked both files and everything matches your information.I am not sure exactly what the problem was, but I tried rebooting again and the error message for unmount does not come up anymore after doing the sync and kderc steps a little while ago.

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#15 Post by MU »

ok, if it works now, I see no sense in changing the scripts.
If you encounter reboot-problems again, post it as a new topic please, then we might have a closer look :)
Mark

Post Reply