[Bug 194795] New: plasma crashed when I was doing nothing

Miguel Tadeu m_tadeu at yahoo.com
Sun May 31 20:52:59 BST 2009


https://bugs.kde.org/show_bug.cgi?id=194795

           Summary: plasma crashed when I was doing nothing
           Product: kde
           Version: unspecified
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: m_tadeu at yahoo.com


Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1))
Qt Version: 4.5.1
Operating System: Linux 2.6.28-11-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
Hi,
plasma crashed after logging in. I was actualy doing nothing at the moment

 -- Backtrace:
Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault
[Current thread is 0 (LWP 4170)]

Thread 2 (Thread 0xa8151b90 (LWP 4171)):
#0  0xb800e430 in __kernel_vsyscall ()
#1  0xb50e10e5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0xb63312ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb65155b2 in QWaitCondition::wait (this=0x9aa55d8, mutex=0x9aa55d4,
time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb7973ae2 in QHostInfoAgent::run (this=0x9aa55c8) at
kernel/qhostinfo.cpp:260
#5  0xb651456e in QThreadPrivate::start (arg=0x9aa55c8) at
thread/qthread_unix.cpp:189
#6  0xb50dd4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb632249e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb3d0c730 (LWP 4170)):
[KCrash Handler]
#6  TaskManager::Task::window (this=0xa060ad8) at
/build/buildd/kdebase-workspace-4.2.85/libs/taskmanager/task.cpp:356
#7  0xb6618f0f in QObject::event (this=0xa060ad8, e=0x0) at
kernel/qobject.cpp:1082
#8  0xb6f1c257 in QGraphicsWidget::event (this=0xa060ad8, event=0xbf92981c) at
graphicsview/qgraphicswidget.cpp:1340
#9  0xb6893bcc in QApplicationPrivate::notify_helper (this=0x94d3f30,
receiver=0xa060ad8, e=0xbf92981c) at kernel/qapplication.cpp:4057
#10 0xb689bede in QApplication::notify (this=0x94cb4d0, receiver=0xa060ad8,
e=0xbf92981c) at kernel/qapplication.cpp:3604
#11 0xb76f5c9d in KApplication::notify (this=0x94cb4d0, receiver=0xa060ad8,
event=0xbf92981c) at
/build/buildd/kde4libs-4.2.85/kdeui/kernel/kapplication.cpp:307
#12 0xb66087ab in QCoreApplication::notifyInternal (this=0x94cb4d0,
receiver=0xa060ad8, event=0xbf92981c) at kernel/qcoreapplication.cpp:610
#13 0xb6637b31 in QTimerInfoList::activateTimers (this=0x94d646c) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#14 0xb6634280 in timerSourceDispatch (source=0x94d6438) at
kernel/qeventdispatcher_glib.cpp:164
#15 0xb4edbb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0xb4edf0eb in ?? () from /usr/lib/libglib-2.0.so.0
#17 0xb4edf268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#18 0xb66341d8 in QEventDispatcherGlib::processEvents (this=0x94d3540, flags={i
= -1080911464}) at kernel/qeventdispatcher_glib.cpp:324
#19 0xb6935765 in QGuiEventDispatcherGlib::processEvents (this=0x94d3540,
flags={i = -1080911416}) at kernel/qguieventdispatcher_glib.cpp:202
#20 0xb6606dda in QEventLoop::processEvents (this=0xbf929a40, flags={i =
-1080911352}) at kernel/qeventloop.cpp:149
#21 0xb660721a in QEventLoop::exec (this=0xbf929a40, flags={i = -1080911288})
at kernel/qeventloop.cpp:200
#22 0xb66096c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#23 0xb6893a47 in QApplication::exec () at kernel/qapplication.cpp:3526
#24 0xb7fb2290 in kdemain (argc=1, argv=0xbf929bf4) at
/build/buildd/kdebase-workspace-4.2.85/plasma/shells/desktop/main.cpp:50
#25 0x08048712 in main (argc=0, argv=0x0) at
/build/buildd/kdebase-workspace-4.2.85/obj-i486-linux-gnu/plasma/shells/desktop/plasma-desktop_dummy.cpp:3

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list