Bug 154966

Summary:	system settings doesn't load after an update
Product:	[Applications] systemsettings	Reporter:	fugifox <fugifox>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	andresbajotierra
Priority:	NOR
Version:	3.96.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description fugifox 2008-01-02 11:25:43 UTC

Version:            (using KDE KDE 3.97.0)
Installed from:    Ubuntu Packages
OS:                Linux

After installing the latest updates from Ubuntu's synaptic package manager
KDE 4 system settings doesn't load.

I have seen the same behavior in bug 150945 but that was for KDE 3.5.8,
so I thought I have to report it under KDE 4 section.
If you need any more information e.g. about specific packages version
please let me know.

Comment 1 Pino Toscano 2008-01-02 11:49:41 UTC

Can you run it on console, and see what it says?

Comment 2 ijen 2008-03-13 00:21:23 UTC

i have same problem under opensuse since i have upgrade from 4.0 to 4.01.
systemsettings crash when I select it in kickermenu.
A Fatal Error Occurred
The application System Settings (systemsettings) crashed and caused the signal 11 (SIGSEGV).
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

[?1034h(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb64d98e0 (LWP 10915)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (process 10915)]

Thread 1 (Thread 0xb64d98e0 (LWP 10915)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7db2033 in __waitpid_nocancel () from /lib/libpthread.so.0
#2  0xb7ae731f in ?? () from /usr/lib/libkdeui.so.5
#3  0x00002aa4 in ?? ()
#4  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()

Comment 3 Will Stephenson 2008-06-26 09:24:52 UTC

Still a problem?  if so can you install the kdebase4-debuginfo and kdelibs4-debuginfo (and debugsource packages if your version of suse provides it) and add a complete backtrace.

Comment 4 Dario Andres 2008-12-31 13:43:49 UTC

No reponse, closing. Please reopen this bug report if you experience the same bug. Thanks :)