Bug 214539 - plasma-desktop keeps crashing after KDM login, when google-translator plasmoid has been added in the KDE session before
Summary: plasma-desktop keeps crashing after KDM login, when google-translator plasmoi...
Status: RESOLVED DUPLICATE of bug 213348
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-14 16:29 UTC by Anastasios Hatzis
Modified: 2009-11-20 00:41 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 Anastasios Hatzis 2009-11-14 16:29:24 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic-pae i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
During my last KDE session I did install google-translator.plasmoid using "add widget" on desktop. During this session there was no problem with the widget. But at the next session after login (KDM) the plasma-desktop is crashing. Restarting plasma-desktop doesn't help (crash again). Ignoring the crash means no desktop, no activity bar etc.

Right during the session where I add the google-translator.plasmoid I experience no problems with this widget (or any other plasma-related software), it just works fine.

I had this phenomenon twice, each time in the next login after the session where i added google-translator.plasmoid. I'm rather sure crash is somehow related to this plasmoid, perhaps in combination with this "start KDE with last session" feature I have activated in Settings -> Session management. The README of the plasmoid tells me that it tries to recover the user-entered and translated sentence from the last session. I would start looking for the bug at this feature, but I'm no programmer ;)

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb571a700 (LWP 1882))]

Thread 2 (Thread 0xa744ab70 (LWP 1885)):
#0  0xb7745430 in __kernel_vsyscall ()
#1  0xb5e74e15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb603878d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb754de67 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#4  0xb5d86922 in ?? () from /usr/lib/libQtNetwork.so.4
#5  0xb754ce32 in ?? () from /usr/lib/libQtCore.so.4
#6  0xb5e7080e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb602b7ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb571a700 (LWP 1882)):
[KCrash Handler]
#6  0xb547c6ee in Plasma::Applet::flushPendingConstraintsEvents() () from /usr/lib/libplasma.so.3
#7  0xb54a07dd in Plasma::Corona::loadLayout(QString const&) () from /usr/lib/libplasma.so.3
#8  0xb54a18be in Plasma::Corona::initializeLayout(QString const&) () from /usr/lib/libplasma.so.3
#9  0xb42ae1d6 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#10 0xb42ae4da in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#11 0xb42ae733 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#12 0xb7653263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#13 0xb7653ec2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#14 0xb7658387 in ?? () from /usr/lib/libQtCore.so.4
#15 0xb765849c in ?? () from /usr/lib/libQtCore.so.4
#16 0xb764d3bf in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#17 0xb62b6f54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0xb62be67c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0xb6d06bfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#20 0xb763d6cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#21 0xb766a7ce in ?? () from /usr/lib/libQtCore.so.4
#22 0xb76680e0 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb5ebce78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0xb5ec0720 in ?? () from /lib/libglib-2.0.so.0
#25 0xb5ec0853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0xb766802c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb6357be5 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb763bc79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0xb763c0ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0xb763e53f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#31 0xb62b6dd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#32 0xb429180d in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#33 0x0804dde1 in _start ()

Reported using DrKonqi
Comment 1 Beat Wolf 2009-11-14 16:52:15 UTC

*** This bug has been marked as a duplicate of bug 213348 ***
Comment 2 Anastasios Hatzis 2009-11-20 00:41:19 UTC
Yesterday, I experienced the same crash issue, but with the Currency Converter plasmoid, instead of the Google Translator plasmoid.  Until now I 've been using a dozen or more different plasmoids.

I like to add, that I have not experienced any crash after installation as reported in bug 213348, marked duplicate, my problem only occurrs reproducably with these two plasmoids, and this is weeks after installing a fresh Kubuntu 9.10 Karmic. I don't know if this matters anyhow.

Please do let me know if I can help ("advanced end-user").