Bug 167156

Summary:	KDE Crash Handler report kcmshell crashed and caused the signal 11 (SIGSEGV) Jist after reqiest for my password.
Product:	[Unmaintained] kdeprint	Reporter:	Graham M Whittenberg <csdiwhitt>
Component:	general	Assignee:	KDEPrint Devel Mailinglist <kde-print-devel>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	andresbajotierra, csdiwhitt
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Graham M Whittenberg 2008-07-21 18:29:14 UTC

Version:            (using KDE 3.5.9)
Installed from:    Ubuntu Packages

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 0x7f4a5bde26f0 (LWP 6524)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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]
#5  0x00007f4a5acbb265 in KCModuleProxy::realModule ()
   from /usr/lib/libkutils.so.1
#6  0x00007f4a5b9eaba2 in kdemain () from /usr/lib/libkdeinit_kcmshell.so
#7  0x00007f4a5af021c4 in __libc_start_main () from /lib/libc.so.6
#8  0x0000000000400559 in ?? ()
#9  0x00007fff63e0c998 in ?? ()
#10 0x0000000000000000 in ?? ()

Comment 1 Dario Andres 2008-12-28 02:47:09 UTC

The backtrace doesn't have useful information. If this is still a problem in a current version (4.1.3 / 4.2beta2 / 4.2svn), please attach more information like described in http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports. Thanks :)

Comment 2 John Layt 2008-12-29 19:01:55 UTC

Is this a crash in the KDEprint kcm?  If so please note that KDEPrint does not exist in KDE4 so this error will not be reproducible there.  You will need to confirm if this crash still occurs in the latest 3.5 packages on the latest version of your distro and produce a backtrace for that.  

If not KDEprint then please reassign to the correct product.

Comment 3 Dario Andres 2009-02-07 00:15:08 UTC

No news from the bug reporter, closing. Please reopen this bug report if you experience the same bug again with a recent KDE (4.1.4 / 4.2.0 / 4.2svn / 4.3svn) . Thanks :)