Bug 193129 - Screensaver generates a SIGSEV error on leaving
Summary: Screensaver generates a SIGSEV error on leaving
Status: RESOLVED DUPLICATE of bug 189592
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-18 17:15 UTC by chris
Modified: 2009-05-20 17:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description chris 2009-05-18 17:15:01 UTC
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    SuSE RPMs

I get 6 plasmoids running on the screensaver.
Each times I leave it, a SIGSEV error appears.

It gives this :
Cette pile des appels apparaît être inutilisable.
C'est probablement dû au fait que votre paquetage a été construit d'une manière qui empêche de créer des piles d'appels corrects, ou que le cadre de pile a été sérieusement corrompu dans l'incident.

[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 0xb4018b40 (LWP 16058)]
[New Thread 0xa80b3b90 (LWP 16060)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe430 in __kernel_vsyscall ()
[Current thread is 0 (LWP 16058)]

Thread 2 (Thread 0xa80b3b90 (LWP 16060)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6460ed1 in select () from /lib/libc.so.6
#2  0xb7139707 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb706771e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb7006175 in start_thread () from /lib/libpthread.so.0
#5  0xb6467dae in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb4018b40 (LWP 16058)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb700dbab in waitpid () from /lib/libpthread.so.0
#2  0xb76fa05f in ?? () from /usr/lib/libkdeui.so.5
#3  0xb76fafb3 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#4  <signal handler called>
#5  0xb7290996 in ?? () from /usr/lib/libQtDBus.so.4
#6  0xb729132c in ?? () from /usr/lib/libQtDBus.so.4
#7  0xb7171d68 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#8  0xb71721a0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9  0xb717222b in QObject::destroyed () from /usr/lib/libQtCore.so.4
#10 0xb7172f79 in QObject::~QObject () from /usr/lib/libQtCore.so.4
#11 0xb7c8dded in KIO::Scheduler::~Scheduler () from /usr/lib/libkio.so.5
#12 0xb7c92314 in ?? () from /usr/lib/libkio.so.5
#13 0xb7bde78b in ?? () from /usr/lib/libkio.so.5
#14 0xb63c78f1 in exit () from /lib/libc.so.6
#15 0xb63b05fd in __libc_start_main () from /lib/libc.so.6
#16 0x0805b061 in _start ()
#0  0xffffe430 in __kernel_vsyscall ()
Comment 1 Oswald Buddenhagen 2009-05-18 18:25:52 UTC
i should point out that the french message is most useless to the majority of those who will look at this report. ;)
Comment 2 Dario Andres 2009-05-19 00:42:24 UTC
As you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here?
You need to install the "kdelibs5-debuginfo", "libqt4-debuginfo" packages (may be "kdebase4-*-debuginfo" package too)
 Thanks
Comment 3 chris 2009-05-20 17:50:33 UTC
Now, I installed some debug package, the backtrack gives that :


Application: Plasma pour l'écran de veille (plasma-overlay), signal: Segmentation fault
[KCrash Handler]
#6  0xb725e996 in QDBusAdaptorConnector::relaySlot (this=0x86dd750, argv=0xbfa490fc) at qdbusabstractadaptor.cpp:268
#7  0xb725f32c in QDBusAdaptorConnector::qt_metacall (this=0x86dd750, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfa490fc) at qdbusabstractadaptor.cpp:364
#8  0xb713fd68 in QMetaObject::activate (sender=0x86e3948, from_signal_index=0, to_signal_index=1, argv=0xbfa490fc) at kernel/qobject.cpp:3120
#9  0xb71401a0 in QMetaObject::activate (sender=0x86e3948, m=0x8082e98, from_local_signal_index=0, to_local_signal_index=1, argv=0xbfa490fc) at kernel/qobject.cpp:3214
#10 0xb714022b in QObject::destroyed (this=0x86e3948, _t1=0x86e3948) at .moc/release-shared/moc_qobject.cpp:143
#11 0xb7140f79 in ~QObject (this=0x86e3948) at kernel/qobject.cpp:769
#12 0xb7cc1f0d in KIO::Scheduler::~Scheduler () from /usr/lib/libkio.so.5
#13 0xb7cc5251 in ?? () from /usr/lib/libkio.so.5
#14 0xb7bf9cfb in ?? () from /usr/lib/libkio.so.5
#15 0xb63958f1 in exit () from /lib/libc.so.6
#16 0xb637e5fd in __libc_start_main () from /lib/libc.so.6
#17 0x0805b6d1 in _start ()

Now, gimme me some feedbacks please,
Cordialy
Comment 4 Dario Andres 2009-05-20 17:56:19 UTC
Thanks for the backtrace.
Comment 5 Dario Andres 2009-05-20 17:57:34 UTC
Marking as duplicate of bug 189592. Thanks

*** This bug has been marked as a duplicate of bug 189592 ***