Bug 150983 - Kde 3.5.8: System Settings Crash
Summary: Kde 3.5.8: System Settings Crash
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-18 16:13 UTC by marco
Modified: 2007-12-20 02:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description marco 2007-10-18 16:13:02 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages

This morning I've upgraded my KDE 3.5.7 to KDE 3.5.8. 
I've used this repository, deb http://kubuntu.org/packages/kde-358 feisty main , because I'm using Kubuntu Feisty.
So when I've tried to open System Settings, it crashed!
Luckly there is KControl... but for those people that doesn't know it, it's a disaster.

I hope it's a bug only for me ;)

Here is the output of SIGSEGV, signal 11:

(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 -1232848672 (LWP 5498)]
(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  0x08117d88 in ?? ()
#8  0x00000000 in ?? ()

Bye ;)
Comment 1 Jonathan Riddell 2007-10-18 16:21:14 UTC
I suspect this is Kubuntu specific, although I'm not sure what would cause it, but please report to launchpad.net.
Comment 2 David 2007-10-19 01:30:42 UTC
I am having exactly the same situation. The output is exactly the same as well. Crashes every time.
Comment 3 David Piedra 2007-10-21 14:07:44 UTC
I have the same error, but #7 is like #7 0x090fffd0. I also got the err after updating kde to version 3.5.8 (because with 3.5.8 some times got similar error when opening some windows).

How can I fix it?

Thanks in advance
Comment 4 Andre Toussaint 2007-10-21 22:50:34 UTC
I am also getting this problem EVERY time I try to launch System Settings. Tried uninstalling & reinstalling 'systemsettings' in Adept... no change.  I'm running Kubuntu 7.04 64-bit on an AMD XP 3600 X2 dual-core cpu.  This only occurred AFTER upgrading from KDE 3.5.6 to KDE 3.5.8, using the kde.org mirror.
Comment 5 Loiseau2nuit 2007-12-20 02:35:57 UTC
Yep ! It seems that all people using KUbuntu 7.04 are meeting this issue (me either). Upgrading to 7.10 seems to fix the issue as told in another related bug submission ( see http://bugs.kde.org/show_bug.cgi?id=150945 ). I'm currently doing the O.S. upgrade. I'll tell if this fixes the problem.

Maybe the packages available on other repositories than gutsy's ones are broken or corrupted. No other way to explain, on my side...