Slackware 10.2 and KDE 3.5

dave`2005 · 02-09-2006, 10:13 AM

Hi all,

When KDE shuts down i get:

Code:

*** glibc detected *** corrupted double-linked list: 0x080a14b8 *** kicker: crashHandler called
startkde: shutting down...
klauncher: Exiting on signal 1
kicker: sighandler called
KCrash: application 'kicker' crashing...
startkde: Running shutdown scripts...
startkde: Done.

waiting for X server to shut down

(root@localhost ~) kicker: sighandler called

Then i have to do ctrl+c to get the prompt back.

Can anyone tell me why this happens and hopefully how to fix it? Also one more thing, sometimes slackware crashes randomly in KDE and and i get that sigfault box on the desktop, any ideas on this? Or do i need to record the error next time it happens?

Any help appreciated.

satinet · 02-09-2006, 10:20 AM

have you tried updating your version of glibc?

also have you googled this? seems a few things....

Woodsman · 02-10-2006, 01:19 AM

One of the more common bugs with the Kicker is enabling the KDE menu Services menu option. Disable that menu option and see if the error messages stop.

Twister512 · 02-10-2006, 06:46 AM

I had been having problems with KDE 3.5, I used Konstruct, took about 1 1/2 days to complete, rebooted, and no kde 3.5?!?!? so I went to KDE website, looked for distro specific packages, found the ones for slackware, downloaded from the FTP site, followed instructions with the README that came with those, and bang boom, KDE 3.5 works nicely

Yalla-One · 02-10-2006, 06:50 AM

For running KDE 3.5 series, I _highly_ recommend going to Slackware.com and download the latest -current which includes original packages for 3.5.1. They work flawlessly.

-Y1

satinet · 02-10-2006, 07:15 AM

are you sure about that?

i just went and KDE 3.4.2 is the latest kde from www.slackware.com

i believe there are some KDE 3.5.0 packages at www.kde.org

Yalla-One · 02-10-2006, 07:23 AM

satinet,

KDE 3.5.1 is the latest from www.kde.org - it's righ there in the middle of the title screen.

If you go to slackware.com and check -current, you'll see that 3.5.1 is the latest there too - trust me - I'm running packages off it right now. Maybe you have to reload the page in your browser if it's cached, or maybe you need to make sure you're checking -current and not -stable.

-Y1

satinet · 02-10-2006, 07:30 AM

wierd it's telling 3.4.2

anyway, i might give 3.5.1 a bash on my test slack.

raska · 02-10-2006, 09:29 AM

well just a few days ago I downloaded the sources for KDE 3.5.1, compiled everything on hand (unpack every package and basically do ./configure, make and make install) and it's working real nice.

It took a damn lot of time (around 1 day) but weird messages like "Bad X window" and "Kicker crashing" stopped outright

Not a single application has crashed since then.

Woodsman · 02-10-2006, 07:07 PM

Quote:

are you sure about that?

FWIW, yesterday (Feb 9, 2006) I received a changelog notice email and PV has updated KDE to version 3.5.1.

Quote:

It took a damn lot of time (around 1 day) but weird messages like "Bad X window" and "Kicker crashing" stopped outright

Wow! Finally! Miracles do happen! Woohoo!

Unfortunately I do not have access to broadband and I have to wait until I visit somebody in the big city with broadband or PV issues the next release.

satinet · 02-11-2006, 01:41 PM

maybe the next release will have a 2.6 kernel!!!

10.2 was a nothing release IMHO. i hope the next release adds something so that slackware doesnt fade away...

joe83 · 02-11-2006, 02:42 PM

Quote:

Originally Posted by Yalla-One

For running KDE 3.5 series, I _highly_ recommend going to Slackware.com and download the latest -current which includes original packages for 3.5.1. They work flawlessly.

-Y1

Well, it worked less than "flawlessly" in my case, I kept getting an error message regarding "libcairo.so not found " which prevented me from using firefox, mozilla etc. Got that sorted out, and then another error message regarding yet another missing library. Installed it, and now everything seems OK. Is it just me, or are KDE updates just a general pain in the a$#?

drumz · 02-11-2006, 03:01 PM

Joe, you answered my question "How safe is it to selectively update packages from current?" Answer: If you want current, you better just take all of it.

bird603568 · 02-11-2006, 03:02 PM

The upgrade crashed artsd. This only started to happen when I use the offical .tgz THe sound was fine under a selfcompiled 3.5

dive · 02-11-2006, 03:05 PM

I had problems with 3.5 (compiled from source using konstruct) + kdevelop (wouldnt compile)
I was told over on the kdevelop forum that 3.5 had a bdb bug and to use 3.5.1 which was released soon after. I did an upgrade-all with slackpg earlier and it installed 3.5, which could be a mirror problem I guess.

Anyway it seems there were problems with 3.5.