systemsettings crashing in KDE 3.5.8

[Uqbar]

Binary package hint: kde-systemsettings

After the upgrade to KDE 3.5.8, the systemsettings program is failing to launch.
If I run it from the commandline I get this:

KCrash: Application 'systemsettings' crashing...

While a window from the crash manager says something about the SIGSEGV.
The backtrace seems not to be useful.

[Jonathan Riddell (jr)]

Feisty (7.04) or Gutsy (7.10)?

[Uqbar (uqbar)]

Feisty, up to date.

[Jonathan Riddell (jr)]

Got a backtrace? Installing kdelibs-dbg and kdebase-dbg may help.

[jlpearce (pearcejl)]

I get the same thing with my Feisty up to date install.

[Uqbar (uqbar)]

Here it comes!

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232627488 (LWP 3265)]
[KCrash handler]
#6 0x0805bd7d in ?? ()
#7 0x08102c38 in ?? ()
#8 0x00000000 in ?? ()

I think it's still useless, but maybe I'm badly wrong.

[Uqbar (uqbar)]

Of course I've restarted both X and KDE before trying.

[Marco Vimercati (m-vime)]

I confirm the problem with Kubuntu Festy and kde 3.5.8

[ajkain (ajkain)]

Same problem with Kubuntu Festy and KDE 3.5.8

[Wivaldo Jr (wivaldojr)]

Same problem with Feisty and KDE 3.5.8

[bmorency (bmorency)]

Same problem after I upgraded Fiesty to kde 3.5.8

here is my backtrace.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232553760 (LWP 18463)]
[KCrash handler]
#5 0x0805bd7d in ?? ()
#6 0x0810ca10 in ?? ()
#7 0x00000000 in ?? ()

[derektorr (derektorr)]

I confirm, Kubuntu 7.04, updated KDE from 3.5.7 to 3.5.8.

[Uqbar (uqbar)]

Upgraded to Gutsy: now it works. But I don't think this is the solution as the whole systems changed!

[Paul Loughman (snowhog)]

I too, have this issue. I upgraded KDE yesterday from 3.5.6 to 3.5.8. K Menu | System Settings now crashes on launch with SIGSEGV. Backtrace was useless. I did install (afterwards) kdelibs-dbg and kdebase-dbg, but the backtrace results still only report:

(no debugging symbols found)
 Using host libthread_db library "/lib/libthread_db.so.1".
 [Thread debugging using libthread_db enabled]
 [New Thread -1232553760 (LWP 18463)]
 [KCrash handler]
 #5 0x0805bd7d in ?? ()
 #6 0x0810ca10 in ?? ()
 #7 0x00000000 in ?? ()

K Menu | System Settings was working fine in 3.5.6. I can still access the separate application with Alt+F2 and running kcontrol.

So what's causing the problem?? What changed in 3.5.8 that is causing the problem??

[Paul Loughman (snowhog)]

As a note. With kdelibs-dbg and kdebase-dbg packages installed, running backtrace does show four additional entries (#1, #2, etc), but you can't capture them - the screen clears and the previously posted trace result is all you get.

[wastedfluid (wastedfluid)]

I'll confirm this. I have the dbg packages installed.

Here is my backtrace:

Fiesty, upgraded.. no updates available.. updated from 3.5.6, to 3.5.8 today..

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232926496 (LWP 9445)]
[KCrash handler]
#6 0x0805bd7d in ?? ()
#7 0x0810ad68 in ?? ()
#8 0x00000000 in ?? ()

[astr (anatolistrigin)]

Confirming again. The trace is

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232992032 (LWP 6861)]
[KCrash handler]
#6 0x0805bd7d in ?? ()
#7 0x080c43d0 in ?? ()
#8 0x00000000 in ?? ()

BTW what is 0x0805bd7d?

[wastedfluid (wastedfluid)]

Anything new on this? It's not exactly easy to change stuff without that panel. I've became greedy.

[Marco Vimercati (m-vime)]

The old kcontrol still works...

[Alexander Smirnov (smirnoff-mail)]

>The old kcontrol still works...
Not for me, unfortunately. It launches, but doesn't contain panel, where all the settings located.

[Thomas David (nemphis)]

I can confirm this with Kubuntu Feisty and KDE 3.5.8. Here the backtrace of KDE Crashmanager:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233422112 (LWP 6355)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0x0805bd7d in ?? ()
#7 0x0810bfa0 in ?? ()
#8 0x00000000 in ?? ()

[Goodness (1-goodness)]

Hello,

it works with following changes on my feisty-system.

i moved the "system-settings-merge.menu" from the folder /etc/xdg/menus/kde-applications-merged to the folder /etc/xdg/menus/applications-merged (the *.menu place in gutsy) an it's works

[Goodness (1-goodness)]

i forget the why

"(the *.menu place in gutsy)" Gutsy use also KDE 3.5.8

[astr (anatolistrigin)]

>>Goodness

I followed your advice - and it worked. Thank you very much

[wastedfluid (wastedfluid)]

I can confirm that Goodness's fix works on Fiesty 3.5.8.

[Paul Loughman (snowhog)]

I confirm that moving the file system-settings-merge.menu from /etc/xdg/menus/kde-applications-merged to /etc/xdg/menus/applications-merged works. Please mark this bug as confirmed and note the "fix" that corrects it. Please have the developers move this into production for an update to KDE 3.5.8

[Goodness (1-goodness)]

@ Paul L.
I confirmed the bug-thread.

You wrote: "and note the "fix" that corrects it. Please have the developers move this into production for an update to KDE 3.5.8", i don´ t now what you mean?

Please change this self

[m.assenov (m-assenov)]

 I have problem with Adept Installer and i cannot be install any software.
For example i cannot install multimedia codes on my Kubuntu 7.10 destribution.

no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233058112 (LWP 6044)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb65f0a0b in KAudioManagerPlay::KAudioManagerPlay ()
   from /usr/lib/libartskde.so.1
#7 0xb66ad893 in KNotify::restartedArtsd () from /usr/lib/kde3/knotify.so
#8 0xb66af96d in KNotify::KNotify () from /usr/lib/kde3/knotify.so
#9 0xb66b01aa in kdemain () from /usr/lib/kde3/knotify.so
#10 0x0804e67f in ?? ()
#11 0x00000001 in ?? ()
#12 0x08085308 in ?? ()
#13 0x00000001 in ?? ()
#14 0x00000000 in ?? ()

[Jonathan Thomas (echidnaman)]

Systemsettings in Intrepid doesn't use the .menu system for module registering, so this is no longer an issue.