SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Kicker and the taskbar both crash with Signal 11 immediately upon initialization. The rest of the desktop seems to be working fine. This is with Slackware-current upgraded from 10.1, with a 2.4.29 kernel.
Kicker and the taskbar both crash with Signal 11 immediately upon initialization. The rest of the desktop seems to be working fine. This is with Slackware-current upgraded from 10.1, with a 2.4.29 kernel.
Are you trying to use old KDE configs?
Try deleting/renaming ~/.kde and report back with the results.
Which first appeared with KDE 3.4.something and dissapeared with KDE 3.5.2, but came back from dead with 3.5.3. I don't really care since it doesn't hurts at all.
The 2nd one doesn't seems to hurt, but doesn't inspire confidence either, is that I've hit like 3 or 4 assertions now. Next time I'm gonna tee the stdout of kde (or figure out how to use kdebugdialog) and check if I have to report a bug to KDE or what.
Other than those minor things, everything seems to work as it should
Try deleting/renaming ~/.kde and report back with the results.
That seems to fix the problem on my work machine. I'll have to check and see what broke between versions. This shouldn't happen on a minor upgrade like 3.5.2 to 3.5.3.
So far for me, 3.5.3 has been great. The only "glitch" of sorts has been the Storage Manager applet for the kicker. Sometimes it works...sometimes it doesn't. BTW, 3.5.3 was installed after a brand new install of Slack 10.2.
After renaming my .kde directory and starting over, I added my applets and buttons one at a time. As soon as I tried to add the System Monitor applet to Kicker, it crashed. It also caused the X server to shut down.
Looks like the system monitor in 3.5.3 is useless. Right now, the fix is the second line of the joke that begins with "Doc, it hurts when I do this."
After renaming my .kde directory and starting over, I added my applets and buttons one at a time. As soon as I tried to add the System Monitor applet to Kicker, it crashed. It also caused the X server to shut down.
Looks like the system monitor in 3.5.3 is useless. Right now, the fix is the second line of the joke that begins with "Doc, it hurts when I do this."
I got it running with no problems and it has succesfuly loaded without any crashing at all.
Under which circumstances you get the crash? Any funny configs?
I got it running with no problems and it has succesfuly loaded without any crashing at all.
Under which circumstances you get the crash? Any funny configs?
Nothing special, but it happened on both my home (no-name 1.1 GHz Athlon box) and work (HP/Compaq with a 2.2 GHz Celeron processor) machines.
All I did was attempt to add the System Monitor applet to Kicker the normal way ("Add Applet" from the Kicker menu). All other applets and buttons (system tray, lock/logout, 8-screen pager, Korn mail monitor, external taskbar, and buttons for Firefox, KMix, and Konsole) work perfectly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.