Bug 151742 - systemsettings crash andcaused signal 11(sigsegv)
Summary: systemsettings crash andcaused signal 11(sigsegv)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings-kde3
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 152507 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-11-02 14:15 UTC by riccardo
Modified: 2013-09-28 00:06 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
The Crash log (1.75 KB, text/plain)
2008-01-27 21:35 UTC, Sadanand Hegde
Details
VIDEO MANAGER AND FILE MANAGER (2.77 KB, application/octet-stream)
2010-01-07 16:34 UTC, mary lani
Details

Note You need to log in before you can comment on or make changes to this bug.
Description riccardo 2007-11-02 14:15:47 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
Compiler:          ubuntu 
OS:                Linux

when lanching form console the output is:


rikkazzo@Rikkazzolandia:~$ systemsettings
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
KCrash: Application 'systemsettings' crashing...
rikkazzo@Rikkazzolandia:~$

and appear the kde crash handler with short description :
The application System Settings crashed and caused the signal 11(sigsegv)


the backtrace 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)
(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 -1233553184 (LWP 5308)]
(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  0x080aeea0 in ?? ()
#8  0x00000000 in ?? ()
Comment 1 Belette 2007-11-05 09:26:55 UTC
I got it too, I think since 3.5.8 update.

(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 -1232942880 (LWP 7683)]
(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  0x080fa5c8 in ?? ()
#8  0x00000000 in ?? ()
Comment 2 Pino Toscano 2007-11-18 17:47:50 UTC
*** Bug 152507 has been marked as a duplicate of this bug. ***
Comment 3 audrius 2007-11-18 19:02:41 UTC
after update to kde 3.5.8

audrius@xxx:~$ systemsettings
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  147
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  147
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
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 -1232684832 (LWP 5957)]
(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  0x080c04b8 in ?? ()
#8  0x00000000 in ?? ()


Comment 4 Will Stephenson 2007-11-23 11:27:43 UTC
Please install kdelibs and kdebase debug packages and add new backtraces.
Comment 5 Travis Carlson 2007-11-23 20:47:45 UTC
I recompiled with --enable-debug=full and ran in gdb. Hopefully this helps.

root@dell:~/tmp/kde-systemsettings-0.0svn20070312/systemsettings# gdb ./systemsettings
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) run
Starting program: /home/travis/tmp/kde-systemsettings-0.0svn20070312/systemsettings/systemsettings
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread -1233745712 (LWP 19620)]
Qt: gdb: -nograb added to command-line options.
         Use the -dograb option to enforce grabbing.
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
systemsettings: MenuName: "systemsettings".
systemsettings: Unable to load menu "systemsettings" from KServiceGroup.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1233745712 (LWP 19620)]
0x0805ed7d in QValueList<RowIconView*>::detach (this=0x78) at /usr/share/qt3/include/qvaluelist.h:562
562         void detach() { if ( sh->count > 1 ) detachInternal(); }
(gdb) bt
#0  0x0805ed7d in QValueList<RowIconView*>::detach (this=0x78) at /usr/share/qt3/include/qvaluelist.h:562
#1  0x0805efc7 in QValueList<RowIconView*>::operator[] (this=0x78, i=0) at /usr/share/qt3/include/qvaluelist.h:536
#2  0x0805e682 in KcmSearch (this=0x810d418, moduleViewList=0x80b4370, parent=0x810cf50, name=0x806a22a "search") at kcmsearch.cpp:31
#3  0x08064da2 in MainWindow::buildActions (this=0x80b42b0) at mainwindow.cpp:129
#4  0x08065fee in MainWindow (this=0x80b42b0, embed=true, menuFile=@0xbf88763c, parent=0x0, name=0x0) at mainwindow.cpp:65
#5  0x080634b5 in main (argc=134653804, argv=0xbf8877c4) at main.cpp:56
(gdb) p sh
Cannot access memory at address 0x78
(gdb) return
Make QValueList<RowIconView*>::detach() return now? (y or n) y
#0  0x0805efc7 in QValueList<RowIconView*>::operator[] (this=0x78, i=0) at /usr/share/qt3/include/qvaluelist.h:536
536         T& operator[] ( size_type i ) { QT_CHECK_INVALID_LIST_ELEMENT; detach(); return sh->at(i)->data; }
(gdb) p sh
Cannot access memory at address 0x78
(gdb) return
Make QValueList<RowIconView*>::operator[](unsigned int) return now? (y or n) y
#0  0x0805e682 in KcmSearch (this=0x810d418, moduleViewList=0x80b4370, parent=0x810cf50, name=0x806a22a "search") at kcmsearch.cpp:31
31                                      : KIconViewSearchLine(parent, moduleViewList->at(0)->groups[0], name){
(gdb) p moduleViewList
$1 = (class QPtrList<ModulesView> *) 0x80b4370
(gdb) p moduleViewList->at(0)
$2 = (class ModulesView *) 0x0
Comment 6 Sadanand Hegde 2008-01-27 21:35:36 UTC
Created attachment 23313 [details]
The Crash log
Comment 7 Sadanand Hegde 2008-01-27 21:36:19 UTC
I have the same problem
Here is the information:

I reloaded my system with Kubuntu 7.10
I did aptitude update/upgrade/dist-upgrade

I am not sure when it started but now my systemsettings does not work. It just crashes.

<code> systemsettings --version
Qt: 3.3.7
KDE: 3.5.8
System Settings: 0.2
</code>
The trace log is attached 
Comment 8 Roland Dunzendorfer 2008-12-29 22:43:24 UTC
i face the same probleme after an update to kubuntu 8.04

KDE version 3.5.10

here is the logfile:
[code]
(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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb683a6c0 (LWP 6449)]
(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  0x0805bced in ?? ()
#7  0x08061d07 in ?? ()
#8  0x0806284f in ?? ()
#9  0x0805ff95 in ?? ()
#10 0xb79d4450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#11 0x08059381 in ?? ()
[/code]
Comment 9 Dario Andres 2008-12-30 01:46:19 UTC
*** This bug has been confirmed by popular vote. ***
Comment 10 Roland Dunzendorfer 2008-12-30 09:40:38 UTC
i installed kdelibs and kdebase debug packages as suggested in comment 4 and got the following backtrace report:

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb68106c0 (LWP 26492)]
[KCrash handler]
#6  0x0805bced in ?? ()
#7  0x08061d07 in ?? ()
#8  0x0806284f in ?? ()
#9  0x0805ff95 in ?? ()
#10 0xb79aa450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#11 0x08059381 in ?? ()
Comment 11 mary lani 2010-01-07 16:34:15 UTC
Created attachment 39655 [details]
VIDEO MANAGER AND FILE MANAGER

PLEASE CHECK IT IS VERY IMPORTANT TO HAVE THIS PROGRMAS RUN ASAP SUCH AS THE FILE MANAGER WHERE I ALWAYS GO TO LOOK FOR MY FILES AND ANY SYSTEMS ATTACHED TO MY LAPTAP AND ALSO THE VIDEO MANAGER WHERE I USUALLY VIEW VIDEOS SAVED IIN THE LAPTAP AND OTHER DEVICE. I NEED THIS MATTER RESOLVE PLEASE. THANK YOU SO MUCH.
Comment 12 Jekyll Wu 2013-09-28 00:06:45 UTC
This systemsettings-kde3 from kubuntu has been unmaintained for many years.