[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 248357] New: plasma crashes on moving clock plasmoid from
From:       Leo Savernik <l.savernik () aon ! at>
Date:       2010-08-19 10:22:20
Message-ID: bug-248357-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

           Summary: plasma crashes on moving clock plasmoid from desktop
                    to panel
           Product: plasma
           Version: unspecified
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: NEW
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: plasma-bugs@kde.org
        ReportedBy: l.savernik@aon.at


Application: plasma-desktop (0.3)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
When suddenly my digital-clock plasmoid disappeared in the panel, I tried to
readd it. First I tried to add it to the panel directly via rmb/Add applet
which didn't work for some reason.

Then I dropped the applet onto the desktop (it appeared), from there I tried to
drop it onto the panel which didn't work.

Then I opened panel settings from rmb/settings for panel and then I tried to
drop the digital clock onto the panel.

First I found no suitable spot (crossed drop cursor), then the cursor became
enabled just between the embedded window plasmoid and desktop switcher. When I
dropped it there, plasma crashed.

Backtrace resembles that of bug 192000, but it's not the same.

I cannot reproduce the bug as Plasma doesn't let me add *anything* to the panel
since then.
I tried with styles Air and Aya, but it makes no difference.


 -- Backtrace:
Application: Plasma-Arbeitsfläche (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7805aa0 (LWP 1438))]

Thread 3 (Thread 0xaabb9b70 (LWP 1442)):
#0  0x00fa6422 in __kernel_vsyscall ()
#1  0x00eedb86 in poll () from /lib/tls/i686/cmov/libc.so.6
#2  0x01ced4eb in g_poll () from /lib/libglib-2.0.so.0
#3  0x01ce00ac in ?? () from /lib/libglib-2.0.so.0
#4  0x01ce04b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x0113b60f in QEventDispatcherGlib::processEvents (this=0x95e6fc0,
flags=...) at kernel/qeventdispatcher_glib.cpp:414
#6  0x0110e059 in QEventLoop::processEvents (this=0xaabb9290, flags=) at
kernel/qeventloop.cpp:149
#7  0x0110e4aa in QEventLoop::exec (this=0xaabb9290, flags=...) at
kernel/qeventloop.cpp:201
#8  0x0100a5a8 in QThread::exec (this=0x96135b0) at thread/qthread.cpp:487
#9  0x010edc1b in QInotifyFileSystemWatcherEngine::run (this=0x96135b0) at
io/qfilesystemwatcher_inotify.cpp:248
#10 0x0100d32e in QThreadPrivate::start (arg=0x96135b0) at
thread/qthread_unix.cpp:248
#11 0x0023296e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#12 0x00efba4e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xaa3b8b70 (LWP 1443)):
#0  0x00fa6422 in __kernel_vsyscall ()
#1  0x00237015 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0x06facc97 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x70861a0) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2304
#3  0x06facce1 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=0x70861a0) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1438
#4  0x0023296e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0x00efba4e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb7805aa0 (LWP 1438)):
[KCrash Handler]
#6  QCoreApplication::postEvent (receiver=0x9c98f70, event=0x9c57250,
priority=0) at kernel/qcoreapplication.cpp:1105
#7  0x0110f9ac in QCoreApplication::postEvent (receiver=0x9c98f70,
event=0x9c57250) at kernel/qcoreapplication.cpp:1066
#8  0x0111f8a4 in QObject::deleteLater (this=0x9c98f70) at
kernel/qobject.cpp:2158
#9  0x013faa25 in QX11Data::xdndHandleFinished (this=0x913c458, xe=0xbfd02d7c,
passive=false) at kernel/qdnd_x11.cpp:1239
#10 0x013daeb6 in QApplication::x11ClientMessage (this=0x9132cc0, w=0x9c469b0,
event=0xbfd02d7c, passive_only=false) at kernel/qapplication_x11.cpp:3090
#11 0x013ea879 in QApplication::x11ProcessEvent (this=0x9132cc0,
event=0xbfd02d7c) at kernel/qapplication_x11.cpp:3633
#12 0x0141a60a in x11EventSourceDispatch (s=0x913bba8, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#13 0x01cdc5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#14 0x01ce02d8 in ?? () from /lib/libglib-2.0.so.0
#15 0x01ce04b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#16 0x0113b5d5 in QEventDispatcherGlib::processEvents (this=0x9138b80,
flags=...) at kernel/qeventdispatcher_glib.cpp:412
#17 0x0141a135 in QGuiEventDispatcherGlib::processEvents (this=0x9138b80,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#18 0x0110e059 in QEventLoop::processEvents (this=0xbfd03074, flags=) at
kernel/qeventloop.cpp:149
#19 0x0110e4aa in QEventLoop::exec (this=0xbfd03074, flags=...) at
kernel/qeventloop.cpp:201
#20 0x0111269f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#21 0x0135a577 in QApplication::exec () at kernel/qapplication.cpp:3579
#22 0x08fd805e in kdemain (argc=1, argv=0x9129ef8) at
../../../../plasma/desktop/shell/main.cpp:112
#23 0x0804e133 in launch (argc=<value optimized out>, _name=<value optimized
out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x90e8c80 "",
reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x8051465 "0") at ../../kinit/kinit.cpp:717
#24 0x0804ec6d in handle_launcher_request (sock=<value optimized out>,
who=<value optimized out>) at ../../kinit/kinit.cpp:1209
#25 0x0804f190 in handle_requests (waitForPid=<value optimized out>) at
../../kinit/kinit.cpp:1402
#26 0x0804fe4f in main (argc=4, argv=0xbfd03b24, envp=0xbfd03b38) at
../../kinit/kinit.cpp:1845

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

Possible duplicates by query: bug 247792, bug 247467, bug 246848, bug 246493,
bug 243188.

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]