systemsettings crash in Gutsy Gibbon

[Martin-22]

systemsettings it's not runing

Write in console:
martin@notebook:~$ systemsettings
KCrash: Application 'systemsettings' crashing...

Backtrace:
(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 -1232979744 (LWP 12324)]
(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 0x080b57e8 in ?? ()
#8 0x00000000 in ?? ()

[Giuseppe Bottiglieri (giuseppe-bottiglieri)]

I have the same problem.

[zigi (ziegleka)]

Here is my Backtrace. And all setting icons from Systemsettings and KControl are now in Lost & Found .. KControl is empty.

[gforr (gforr)]

Same problem. The systemsettings icons are now in "Lost items"

[Jeff Anderson (jander99)]

Also experienced this problem. This happened after a fresh install of Feisty and then manually updating my sources.list to gutsy and doing a dist-upgrade.

[Luca Della Vedova (lucadellavedov)]

Is this bug a duplicate of https://bugs.launchpad.net/ubuntu/+bug/115014 ?

[gforr (gforr)]

i think that it's the same problem

[Richard Birnie (rbirnie-deactivatedaccount)]

This also occurs on a clean install of gutsy from kubuntu alternate CD i386 daily build 20070604. I managed to get a slightly more detailed backtrace by following the instructions here http://wiki.kubuntu.org/DebuggingProgramCrash and installing some kde debugging packages. Backtrace attached. I also find that the things which should be in system settings are in kmenu > lost + found, see attached screenshot. As noted above kcontrol is also empty. If I run kcontrol from a terminal I get the following message:

kcontrol: WARNING: No K menu group with X-KDE-BaseGroup=settings found ! Defaulting to Settings/

Richard

[Richard Birnie (rbirnie-deactivatedaccount)]

System-settings contents end up in lost+found

[Luka Renko (lure)]

This should be milestoned for Tribe1

[Jonathan Riddell (jr)]

Should be fixed in kdebase and system settings.
Previously we used a hardcoded menu name kde-applications.menu. Now we use the new XDG prefix of kde for applications.menu but that prefix seems not to be used for the merge directories so move files back to /etc/xdg/menus/application-merged

[Michal (mikeos)]

As mentioned in the bug https://bugs.launchpad.net/ubuntu/+bug/115014 the purge+reinstall of kdebase-data helps. KDM must not be running during the operation, just feel free to kill it. Afterwards, myself I had to reinstall kicker, KDE applets and KDE theme manager, since it has been also removed during the kdebase-data purge and reinstall. My Gutsy KDE menus are ok now. System-settings do not crash on access anymore.

[sivaji (sivaji-2009)]

same problem for me also, but i am lucky kcontrol is working ..

Traceback output http://www.sivaji.pastebin.com/f11d99ef
Hardware details http://www.sivaji.pastebin.com/f62335ab9

[Luke Plant (spookylukey)]

I'm seeing this again, after recent kdelibs update (I'm on kdebase-data 4:3.5.8-0ubuntu2.1).

After the update, I first encountered bug #152325 https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/152325
which seems to be related.

To fix that, I found I had to:
 - remove a symlinked directory: /etc/xdg/menus/application-merged
 - reinstall the kdebase-data using dpkg-deb:
  sudo dpkg-deb -x /var/cache/apt/archives/kdebase-data_4%3a3.5.8-0ubuntu2.1_all.deb /
That fixed 152325.

I then reinstalled kde-systemsettings similarly:
sudo dpkg-deb -x /var/cache/apt/archives/kde-systemsettings_0.0svn20070312-0ubuntu4_i386.deb /

systemsettings now runs correctly.

Trying to use "aptitude reinstall" for either of these does *not* work. From my limited knowledge, that appears to be the basic problem -- installation of these files just doesn't happen correctly, presumably to do with the way that config files are installed. If, for example, I remove one file from an installed package:

$ sudo rm /etc/xdg/menus/applications-merged/kde-essential.menu

This will break kcontrol. I expect that this will restore the file (since the package contains the file):

$ sudo aptitude reinstall kdebase-data

But:

$ cat /etc/xdg/menus/applications-merged/kde-essential.menu
cat: /etc/xdg/menus/applications-merged/kde-essential.menu: No such file or directory

[Nesta Campbell (canen)]

I can confirm Luke's solution does work. Thanks Luke.

[otakuj462 (otakuj462)]

I ran into this bug after upgrading from Gutsy to Hardy.

I can confirm that Luke's fix works to resolve it. Thank you Luke.

I'm confused as to why this bug is marked as "Fix Released" for Gutsy, and yet still persists in Hardy.

[BooVeMan (burkhard-vogel)]

Hi,
just to confirm the same as otakuj462 happend to me and Luke's work around helped.
Thanks Luke!

[clickwir (clickwir)]

I don't know if I'd consider this fixed. I saw this problem after upgrading from Gutsy to Hardy.

To fix I needed to:

sudo mv /etc/xdg/menus/applications-merged /etc/xdg/menus/applications-merged.old
sudo mv /etc/xdg/menus/kde-applications-merged /etc/xdg/menus/kde-applications-merged.old
sudo dpkg-deb -x /var/cache/apt/archives/kdebase-data_4%3a3.5.9-0ubuntu7.1_all.deb /
sudo dpkg-deb -x /var/cache/apt/archives/kde-systemsettings_0.0svn20070312-0ubuntu5_i386.deb /

Now I can get into system settings without a kcrash message and my printers appeared now, I can print again. Before they just were not there, they were missing.

[sb (s-bialonski)]

I can confirm that this bug is still present. Yesterday, I experienced this bug when upgrading from Feisty to Gutsy and from Gutsy to Hardy. (Unluckily, I can't decide at which upgrade step this bug occurred.) Anyway, clickwir's solution worked for me. :-)