LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Problem with KDE 3.5.3 on Slackware-Current (https://www.linuxquestions.org/questions/slackware-14/problem-with-kde-3-5-3-on-slackware-current-451833/)

KeithE 06-05-2006 12:40 PM

Problem with KDE 3.5.3 on Slackware-Current
 
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.

tubatodd 06-05-2006 12:42 PM

I have no experienced that exact problem however, the storage applet does not work properly on the kicker....at least not for me


**EDIT**
That must have been a momentary thing, because it is working fine now.

willysr 06-05-2006 11:22 PM

i have no problem at all with KDE 3.5.3 either (up to now) :D

davidsrsb 06-05-2006 11:35 PM

Smoothest KDE upgrade for a long time

rkelsen 06-05-2006 11:37 PM

Quote:

Originally Posted by KeithE
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.

theoffset 06-05-2006 11:40 PM

I'm having two problems:

The 1st one is that dreaded, useless warning:
Code:

kbuildsycoca: WARNING: '/usr/share/application/{gxine,gimp,openoffice}.desktop' specifies undefined mimetype/servicetype: '{mime}'
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 :)

KeithE 06-06-2006 12:40 AM

2nd machine, same exact problem
 
Tried the same upgrade on my home machine (slackware-current upgraded from 10.2). Kicker and the taskbar both crash.

I wonder if it's a mirror issue? Both machines were upgraded from the slackware.cs.utah.edu mirror via swaret.

KeithE 06-06-2006 09:18 AM

It does look like a .kde problem
 
Quote:

Originally Posted by rkelsen
Are you trying to use old KDE configs?

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.

Thanks.

tubatodd 06-06-2006 11:55 AM

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.

KeithE 06-06-2006 09:00 PM

Found the problem: System Monitor Applet
 
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." :D

theoffset 06-07-2006 12:02 AM

Quote:

Originally Posted by KeithE
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." :D

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?

KeithE 06-07-2006 09:29 AM

Quote:

Originally Posted by theoffset
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.


All times are GMT -5. The time now is 12:10 AM.