Bug 163979 - The application Plasma Workspace () crashed and caused the signal 11 (SIGSEGV).
Summary: The application Plasma Workspace () crashed and caused the signal 11 (SIGSEGV).
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-systemtray (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-13 18:16 UTC by Ian Ossher
Modified: 2008-09-06 18:49 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 Ian Ossher 2008-06-13 18:16:46 UTC
Version:            (using KDE 4.0.80)
Installed from:    Ubuntu Packages
OS:                Linux

Plasma crashes after trying to add calculator widget to the taskbar.
Application: Plasma Workspace (<unknown>), signal SIGSEGV
(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)
(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 0xb562d720 (LWP 14203)]
[New Thread 0xb181ab90 (LWP 14206)]
[New Thread 0xb3542b90 (LWP 14204)]
(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)
(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)
(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)
[KCrash handler]
#6  0xb76f0f14 in QObject::connect () from /usr/lib/libQtCore.so.4
#7  0xb1fc8c15 in ?? ()
   from /usr/lib/kde4/lib/kde4/plasma_applet_systemtray.so
#8  0xb6d27d92 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#9  0xb6d513ba in ?? () from /usr/lib/libQtGui.so.4
#10 0xb5a99bf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#11 0xb5a9ce5e in ?? () from /usr/lib/libglib-2.0.so.0
#12 0xb5a9d3ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#13 0xb7708f98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#14 0xb6d511b5 in ?? () from /usr/lib/libQtGui.so.4
#15 0xb76dc92d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#16 0xb76dcabd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#17 0xb76ded3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#18 0xb6cbd567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#19 0xb7fc3456 in kdemain () from /usr/lib/kde4/lib/libkdeinit4_plasma.so
#20 0x08048582 in _start ()
#0  0xb7fdb410 in __kernel_vsyscall ()
Comment 1 Aaron J. Seigo 2008-06-13 18:20:29 UTC
thanks for the report; unfortunately the backtrace as provided doesn't give us much of a clue as to what happened. would it be possible to provide a more complete backtrace, as explained in the following article?

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

also, if you could provide some details as to what led up to this crash (e.g. were you removing the system tray when it happened? did it happen immediately after an application was launched? if so, which one?) that would be very helpful as well.

thanks =)
Comment 2 Ian Ossher 2008-06-13 20:47:36 UTC
I clicked on the little plasma icon on the right of the lower panel, clicked on "Add Widgets", selected Calculator from the window, and clicked "Add Widget". At this point Plasma crashes.
Comment 3 Marco Martin 2008-06-13 23:03:10 UTC
works fine here (altough the calculator in the panel sucks because it totaaly don't know about those formfactors..)
seems you have an older build of the calculator, check all packaes are of exactly the same version
Comment 4 Sebastian Sauer 2008-06-24 04:51:23 UTC
Hi Ian, could you please provide a useful backtrace like described at the link provided at comment #1 ? Cause else I would agree with Marco and since there is no way to future process the report if no such backtrace is provided, I would suggest to close the report. So, thanks in advance for a proper backtrace! :)
Comment 5 Anne-Marie Mahfouf 2008-06-29 14:29:32 UTC
Ian, do you still have this crash? If so, can you install the Ubuntu debug packages and get us a more useful backtrace so we can fix this?

Thanks in advance!
Comment 6 Ian Ossher 2008-06-30 00:51:07 UTC
Will do - will be offline travelling till thursday, but will replicate it and 
send the results.

Ian O.

On June 29, 2008 08:29:33 Anne-Marie Mahfouf wrote:
[bugs.kde.org quoted mail]
Comment 7 Aaron J. Seigo 2008-07-18 18:24:21 UTC
if the original reporter gets back to us and can reproduce, we can reopen.
Comment 8 Horst Streit 2008-09-03 15:53:29 UTC
I' using SuSE opensource system 11.0
System crashes irrepairabel with signal 11(SIGSERV) It happens at the start. 
"The application 'Plasma-Arbeitsflaeche' (plasma) crashed and caused the signal 11(SIGSERV)"
Didn't it all the time before, so I think there is a failure in an update.
Strange things happens: ALT-F2 brings the command line...
But even a complete update procedure has the same effect.. Next I try will be an complete re-installment.

Thanks for listening
Horst
Comment 9 Evgeny Viktorenko 2008-09-06 18:49:54 UTC
(In reply to comment #8)
> I' using SuSE opensource system 11.0
> System crashes irrepairabel with signal 11(SIGSERV) It happens at the start. 
> "The application 'Plasma-Arbeitsflaeche' (plasma) crashed and caused the signal
> 11(SIGSERV)"
> Didn't it all the time before, so I think there is a failure in an update.
> Strange things happens: ALT-F2 brings the command line...
> But even a complete update procedure has the same effect.. Next I try will be
> an complete re-installment.
> 
> Thanks for listening
> Horst
> 

have absolutely the same thing with opensuse 11.0. update doesen't help! still using 3.5.9.