Bug 262655 - Plasma crashes when you try add "Battery Monitor" widget to system tray
Summary: Plasma crashes when you try add "Battery Monitor" widget to system tray
Status: RESOLVED DUPLICATE of bug 245208
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 263980 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-09 14:01 UTC by Oleg Tsarev
Modified: 2011-11-21 13:03 UTC (History)
4 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 Oleg Tsarev 2011-01-09 14:01:00 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.5.4 (KDE 4.5.4)
Qt Version: 4.7.1
Operating System: Linux 2.6.35.10-74.fc14.x86_64 x86_64
Distribution: "Fedora release 14 (Laughlin)"

-- Information about the crash:
1) Remove "Battery Monitor" widget from system tray.
2) Click on system tray -> Panel Options -> Add widgets
3) Try drag "Battery Monitor" from catalog to system tray.
4) Plasma crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault
[KCrash Handler]
#6  QCoreApplication::postEvent (receiver=0x1bec900, event=0x1e2fbf0, priority=0) at kernel/qcoreapplication.cpp:1133
#7  0x00000035db644ae9 in QX11Data::xdndHandleFinished (this=<value optimized out>, xe=0x7fff2d485400, passive=false) at kernel/qdnd_x11.cpp:1254
#8  0x00000035db636e83 in QApplication::x11ClientMessage (this=<value optimized out>, w=0x1d0f640, event=<value optimized out>, passive_only=<value optimized out>) at kernel/qapplication_x11.cpp:3135
#9  0x00000035db6353db in QApplication::x11ProcessEvent (this=0xb6fee0, event=0x7fff2d485400) at kernel/qapplication_x11.cpp:3703
#10 0x00000035db65c896 in x11EventSourceDispatch (s=0xb87330, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#11 0x0000003e34241e33 in g_main_dispatch (context=0xb86120) at gmain.c:2149
#12 g_main_context_dispatch (context=0xb86120) at gmain.c:2702
#13 0x0000003e34242610 in g_main_context_iterate (context=0xb86120, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780
#14 0x0000003e342428ad in g_main_context_iteration (context=0xb86120, may_block=1) at gmain.c:2843
#15 0x00000035d9d868bf in QEventDispatcherGlib::processEvents (this=0xb56380, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#16 0x00000035db65c59e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:207
#17 0x00000035d9d5ab42 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#18 0x00000035d9d5ad8c in QEventLoop::exec (this=0x7fff2d485710, flags=...) at kernel/qeventloop.cpp:201
#19 0x00000035d9d5f24b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#20 0x00000035e0637f88 in kdemain (argc=1, argv=0x7fff2d485b08) at /usr/src/debug/kdebase-workspace-4.5.4/plasma/desktop/shell/main.cpp:118
#21 0x0000003e31e1ee7d in __libc_start_main (main=0x400920 <main(int, char**)>, argc=1, ubp_av=0x7fff2d485b08, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff2d485af8) at libc-start.c:226
#22 0x0000000000400849 in _start ()

Possible duplicates by query: bug 262318, bug 260767, bug 256732, bug 256146, bug 255482.

Reported using DrKonqi
Comment 1 Dario Andres 2011-01-09 14:42:55 UTC
[Comment from a bug triager]
Looks like some old drag-and-drop related bugs.
- Does this happen if you drag another widget ?
- Does this happen if you drop it on another place ? (panel or desktop)
Regards
Comment 2 Oleg Tsarev 2011-01-09 16:54:22 UTC
If I already have "Battery monitor" under panel (but not in system tray) this retry everywhere.
If I don't have "Battey monitor" under panel all good.
I can't reproduce this with another widgets
Comment 3 Aaron J. Seigo 2011-01-27 23:11:14 UTC
*** Bug 263980 has been marked as a duplicate of this bug. ***
Comment 4 Beat Wolf 2011-11-21 13:03:42 UTC

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