Bug 246742 - Plasma-desktop crashes after every boot
Summary: Plasma-desktop crashes after every boot
Status: RESOLVED DUPLICATE of bug 245192
Alias: None
Product: marble
Classification: Applications
Component: plasmoid (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-04 23:44 UTC by jose maturana
Modified: 2010-08-08 20:07 UTC (History)
2 users (show)

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 jose maturana 2010-08-04 23:44:46 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.32.16-150.fc12.x86_64 x86_64
Distribution: "Fedora release 12 (Constantine)"

-- Information about the crash:
I installed some widget in dashboard: notes, unit converter, calculator, yawp and world clock. This error seems related to world clock. After that, plasma-desktop crashes after every boot. If I launch plasma-desktop in already started (and crashed) session, plasma crashes immediately.



The crash can be reproduced every time.

 -- Backtrace:
Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f5333eff880 (LWP 1959))]

Thread 2 (Thread 0x7f5313fff710 (LWP 1961)):
#0  0xffffffffff60013b in ?? ()
#1  0x00007f5313ffe980 in ?? ()
#2  0x00007fff125fd952 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7f5333eff880 (LWP 1959)):
[KCrash Handler]
#5  ref (this=0x27c4510, other=...) at ../../src/corelib/arch/qatomic_x86_64.h:121
#6  QString::operator= (this=0x27c4510, other=...) at tools/qstring.cpp:1280
#7  0x00007f531cbdab76 in Marble::WorldClock::init (this=<value optimized out>) at /usr/src/debug/kdeedu-4.4.5/marble/src/plasmoid/worldclock.cpp:119
#8  0x0000003eaad13487 in Plasma::Corona::loadLayout (this=<value optimized out>, configName=<value optimized out>) at /usr/src/debug/kdelibs-4.4.5/plasma/corona.cpp:419
#9  0x0000003eaad142f2 in Plasma::Corona::initializeLayout (this=0x20be040, configName=...) at /usr/src/debug/kdelibs-4.4.5/plasma/corona.cpp:335
#10 0x0000003eaa04bee5 in PlasmaApp::corona (this=0x20ba430) at /usr/src/debug/kdebase-workspace-4.4.5/plasma/desktop/shell/plasmaapp.cpp:684
#11 0x0000003eaa04c1d8 in PlasmaApp::setupDesktop (this=0x20ba430) at /usr/src/debug/kdebase-workspace-4.4.5/plasma/desktop/shell/plasmaapp.cpp:276
#12 0x0000003eaa04ca9d in PlasmaApp::qt_metacall (this=0x20ba430, _c=InvokeMetaMethod, _id=12, _a=0x7fff124bc6c0)
    at /usr/src/debug/kdebase-workspace-4.4.5/x86_64-redhat-linux-gnu/plasma/desktop/shell/plasmaapp.moc:141
#13 0x0000003880166606 in QMetaObject::activate (sender=0x21bca70, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3295
#14 0x000000388016bcff in QSingleShotTimer::timerEvent (this=0x21bca70) at kernel/qtimer.cpp:308
#15 0x000000388016299e in QObject::event (this=0x21bca70, e=0x7fff124bce20) at kernel/qobject.cpp:1212
#16 0x00000038813ab36c in QApplicationPrivate::notify_helper (this=0x20d2920, receiver=0x21bca70, e=0x7fff124bce20) at kernel/qapplication.cpp:4306
#17 0x00000038813b173b in QApplication::notify (this=<value optimized out>, receiver=0x21bca70, e=0x7fff124bce20) at kernel/qapplication.cpp:4189
#18 0x0000003ea7206ac6 in KApplication::notify (this=0x20ba430, receiver=0x21bca70, event=0x7fff124bce20) at /usr/src/debug/kdelibs-4.4.5/kdeui/kernel/kapplication.cpp:302
#19 0x00000038801539cc in QCoreApplication::notifyInternal (this=0x20ba430, receiver=0x21bca70, event=0x7fff124bce20) at kernel/qcoreapplication.cpp:726
#20 0x000000388017c182 in sendEvent (this=0x20d6000) at kernel/qcoreapplication.h:215
#21 QTimerInfoList::activateTimers (this=0x20d6000) at kernel/qeventdispatcher_unix.cpp:603
#22 0x0000003880179704 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#23 0x0000003d6dc3923e in g_main_dispatch (context=0x20d5120) at gmain.c:1960
#24 IA__g_main_context_dispatch (context=0x20d5120) at gmain.c:2513
#25 0x0000003d6dc3cc28 in g_main_context_iterate (context=0x20d5120, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#26 0x0000003d6dc3cd4a in IA__g_main_context_iteration (context=0x20d5120, may_block=1) at gmain.c:2654
#27 0x00000038801793f3 in QEventDispatcherGlib::processEvents (this=0x20a1f80, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#28 0x000000388144a86e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x0000003880152412 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#30 0x00000038801526dc in QEventLoop::exec (this=0x7fff124bd0c0, flags=...) at kernel/qeventloop.cpp:201
#31 0x0000003880155dab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#32 0x0000003eaa037e52 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.4.5/plasma/desktop/shell/main.cpp:112
#33 0x0000003d6c41eb1d in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, 
    rtld_fini=<value optimized out>, stack_end=0x7fff124bd448) at libc-start.c:226
#34 0x00000000004007c9 in _start ()

Reported using DrKonqi
Comment 1 jose maturana 2010-08-05 00:01:08 UTC
I uninstalled marble (kdeedu-marble) and plasma works well. The bad thing is digikam gones with him.
Comment 2 Dennis Nienhüser 2010-08-08 20:07:23 UTC

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