Bug 266675 - Plasma Crash after Login
Summary: Plasma Crash after Login
Status: RESOLVED DUPLICATE of bug 255437
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:
: 266996 267003 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-02-19 17:37 UTC by Marc Prospero
Modified: 2011-11-20 22:06 UTC (History)
4 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 Marc Prospero 2011-02-19 17:37:48 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 3"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.7-default i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
After logging in as root Plasma crashes. Blamk Screen. Able to start programs with ALt+F2.
Logging in as user ABC, plasma works.

The crash can be reproduced every time.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Aborted
[KCrash Handler]
#6  0xffffe430 in __kernel_vsyscall ()
#7  0xb5ed87ff in raise () from /lib/libc.so.6
#8  0xb5eda140 in abort () from /lib/libc.so.6
#9  0xb60ce7dd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#10 0xb60cc533 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb60cc56f in std::terminate() () from /usr/lib/libstdc++.so.6
#12 0xb60cc73a in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#13 0xb6d063d7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#14 0xb6d0ac70 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#15 0xb623e164 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#16 0xb35a7665 in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#17 0x0804e5b1 in _start ()

This bug may be a duplicate of or related to bug 266219.

Possible duplicates by query: bug 266637, bug 266616, bug 266610, bug 266605, bug 266501.

Reported using DrKonqi
Comment 1 Dario Andres 2011-02-19 17:49:56 UTC
[Comment from a bug triager]
- What third-party (or non-official) plasma widgets do you use ?
Regards
Comment 2 Lamarque V. Souza 2011-02-24 17:43:08 UTC
*** Bug 266996 has been marked as a duplicate of this bug. ***
Comment 3 Lamarque V. Souza 2011-02-24 17:43:56 UTC
*** Bug 267003 has been marked as a duplicate of this bug. ***
Comment 4 unix1 2011-03-08 02:32:45 UTC
For me it was fancytasks that was causing this crash.

I loaded KDE (with crashed plasma), uninstalled fancytasks plasmoid RPM, started plasma-desktop from konsole without any issues.
Logged out, back in, plasma starts normally. There is a plasmoid box with an error message where fancytasks used to be. Get rid of it and it's all back to normal.

Still, I think it would be nice if plasma-desktop caught the exception and disabled the rogue plasmoid automatically (informing user of the event, of course).
Comment 5 cpilgrim33 2011-03-08 07:56:24 UTC
Un-installing fancytasks worked for me ad well thanks for the tip...

Sent from my iPhone

On Mar 7, 2011, at 6:32 PM, <unix1@live.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=266675
> 
> 
> 
> 
> 
> --- Comment #4 from  <unix1 live com>  2011-03-08 02:32:45 ---
> For me it was fancytasks that was causing this crash.
> 
> I loaded KDE (with crashed plasma), uninstalled fancytasks plasmoid RPM,
> started plasma-desktop from konsole without any issues.
> Logged out, back in, plasma starts normally. There is a plasmoid box with an
> error message where fancytasks used to be. Get rid of it and it's all back to
> normal.
> 
> Still, I think it would be nice if plasma-desktop caught the exception and
> disabled the rogue plasmoid automatically (informing user of the event, of
> course).
> 
> -- 
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
Comment 6 Beat Wolf 2011-11-20 22:06:11 UTC

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