| Summary: | Network manager has crashed when wifi connects to a WPA2/PEAP/MSCHAPv2 network | ||
|---|---|---|---|
| Product: | [Unmaintained] Network Management | Reporter: | kurik |
| Component: | Plasma Widget | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | asraniel, bacaro, blackmetalowiec, carlos.gomezsa, crose, dmedianero, Enygma2002_ro, exitsec, gcarter, germano.massullo, iacob_m, j.r.roodhart, jan.basko, juhana.uotila, kde, kevin.kofler, lamarque, lordinfinitus, lucas.gary, mail.thedan, public.bs, rdieter, sheeponpatrol, shiverma, tbtnow, wstephenson |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
I suppose you use NetworkManager-0.9, right? What is the kde-plasma-networkmanagement package version you are using? I cannot reproduce this problem here. I was able to create a WPA Enterprise connection without crashes, even though I do not have a WPA Enterprise server here. I need more information about what were you doing when the crash happened. WPA Enterprise Now I noticed you are using Solid's networkmanager-0.7 backend. If you have NetworkManager-0.8.x installed that is not a problem. If you have NetworkManager-0.9 installed then that can explain the crash. If you have both backends installed you can change their priorities in systemsettings -> Infomation Source -> Network Manager Infrastructure (or something like that, my desktop is not in English). There is also a Fedora update for Plasma NM that corrects the backends priorites. Well, I am puzzled :-( In the debug info, automatically attached by the KDE's crash-report wizard is reported networkmanager-0.7. Howewer RPM shows different versions: # rpm -qa | grep -i networkmanage kde-plasma-networkmanagement-pptp-0.9-0.47.20110323.fc15.x86_64 NetworkManager-pptp-0.8.999-1.fc15.x86_64 NetworkManager-vpnc-0.8.999-2.fc15.x86_64 kde-plasma-networkmanagement-0.9-0.47.20110323.fc15.x86_64 NetworkManager-glib-0.8.9997-1.git20110531.fc15.x86_64 NetworkManager-openvpn-0.8.999-1.fc15.x86_64 kde-plasma-networkmanagement-libs-0.9-0.47.20110323.fc15.x86_64 kde-plasma-networkmanagement-vpnc-0.9-0.47.20110323.fc15.x86_64 kde-plasma-networkmanagement-debuginfo-0.9-0.47.20110323.fc15.x86_64 kde-plasma-networkmanagement-openvpn-0.9-0.47.20110323.fc15.x86_64 NetworkManager-0.8.9997-1.git20110531.fc15.x86_64 I am using standard Fedora-15, there was no manual upgrade of parts of KDE nor wifi/network packages (except the kernel's rtl8192 driver, which is proprietary). In the "Information Sources" panel, I can see only Network Manager 0.7. Is there any specific information I can provide to help to solve this issue ? Thanks for your effort. Ok, I checked and that package you are using is the Fedora's own solution to make Plasma NM (for NM-0.8) work with NM-0.9. Please contact Fedora about this bug since that implementation is not supported by us. Things are confusing in this transition between NM-0.8.x to NM-0.9. Let me try to explain: Today there are four Plasma NM versions: 1. Plasma NM for NM-0.8: this one is in version 0.9 for several years (even before NM-0.9 was announced), it is supported by us and is the Plasma NM version shipped by almost all distributions, usually with version 0.9 in its package version although it does *not* work with NM-0.9. Plasma NM uses Solid's NetworkManager backend to talk to NetworkManager. The directory /usr/src/debug/kdebase-workspace-4.6.3/x86_64-redhat-linux-gnu/solid/networkmanager-0.7/ mentioned in the crash log is the Solid's backend, which is *not* part of Plasma NM source code. In despite of the 0.7 version number the Solid's backend works with both NM-0.7 and NM-0.8. I know, that is confusing already, but there is more... 2. Fedora's own solution to make Plasma NM (for *NM-0.8*) work with *NM-0.9*: this is an in house solution developed by Fedora to make #1 work with NM-0.9. This is the package you are using and it is not supported by us. Fedora guys created that solution because they decided not wait for us (Plasma NM developers) to create the official solution. So basicaly your Plasma NM version 0.9, created to work with NetworkManager 0.8 and use Solid's 0.7 backend, has been modified by Fedora to talk to NetworkManager 0.9 :-) 3. Plasma NM/branch nm09: this is our intermidate implementation for NM-0.9. Of course it is supported by us. As far as I know Fedora is the only distribution that ships this version along side with #2. Solid's 0.9 backend is included in this version, so everything here is 0.9: Plasma NM version 0.9, created to work with NetworkManager 0.9 and use Solid's 0.9 backend, talks to NetworkManager 0.9 :-) When everybody stops using NM-0.8 things are going to go back to normal. 4. Plasma NM/branch libnm-qt: this is going to be our official implemenation for NM-0.9. Of course this one is also supported by us, it is not ready yet, I have never tested it myself, and probably no distributions ships it. libnm-qt is the replacement for Solid's NM backed. The last two are in development stage, I use #3 in my notebook with almost no problems. I just need to clean up the source code and fix one problem with system VPN connections. OK. Thanks for you effort you spent investigating this issue and explaining me this. I will open this issue with Fedora guys. Please file this bug at https://bugzilla.redhat.com/ . FYI, we have a snapshot of "3. Plasma NM/branch nm09" available for testing in the kde-redhat unstable repository. But be warned that there is at this time no automatic migration of settings from 2. (what you're using) to 3., so you will have to reconfigure your networks if you go for that option (which is why the package sits in kde-unstable and not e.g. kde-testing). Making this migration work is the same problem as migrating user settings from 1. to 3. (our changes do not touch settings storage at all), so it should eventually get done, but it is not currently implemented. I'm also going to clear up a few things: * Solution 2. requires changes to both NetworkManager itself (compatibility API) and plasma-NM, which is why it is only a temporary solution. * It's not that we didn't WANT to wait, it's that we COULDN'T wait. Your official solution only started getting usable a week after the Fedora 15 release, 3+ weeks after the final change deadline. We have a time-based release schedule. What we shipped was the only thing we could ship. (We had to ship NM 0.9 because gnome-shell's network management applet requires it.) * We want to eventually phase out that custom solution even for Fedora 15 updates and migrate to the official one, but automatic migration of settings (both from the current Fedora 15 (2.) and from Fedora 14 (1.), but as I explained, that's really the same problem) is a major concern for us. FYI, this turned out to be an issue originating from upstream code, BUT you already fixed the missing NULL check on April 19: https://projects.kde.org/projects/extragear/base/networkmanagement/repository/revisions/ff9076fe85f31b0cfa388d92a0c6d288ad07f396/diff/applet/nmpopup.cpp I'm backporting your fix to our packages. The good news is that we are planning to prepare a Fedora 15 update from the nm09 branch, without any unmaintained compatibility patches, within the next couple weeks (now that migration of settings is implemented). We are also planning to upgrade Fedora 14 (which has NM 0.8.4) to a newer trunk snapshot of plasma-networkmanagement around that time. (Fedora 13 is nearing its end of life and as such will not get a newer snapshot than its current 20110323 snapshot. The update I'm now building to fix this missing NULL check with a backported patch will probably be the last kde-plasma-networkmanagement package update for Fedora 13.) By the way, this bug is now filed as: https://bugzilla.redhat.com/show_bug.cgi?id=710996 Ok, I need more people testing the nm09 branch, specially VPN, I can only test VPNC myself. *** Bug 275274 has been marked as a duplicate of this bug. *** Fixed Fedora 15 package: https://admin.fedoraproject.org/updates/kde-plasma-networkmanagement-0.9-0.47.20110323.fc15.1 *** Bug 275708 has been marked as a duplicate of this bug. *** *** Bug 276469 has been marked as a duplicate of this bug. *** *** Bug 276440 has been marked as a duplicate of this bug. *** *** Bug 276470 has been marked as a duplicate of this bug. *** *** Bug 276431 has been marked as a duplicate of this bug. *** So this is very strange. I already backported your check against NULL in kde-plasma-networkmanagement-0.9-0.47.20110323.fc15.1. But unfortunately, this appears not to be sufficient, because we must be getting an INVALID object, not a NULL one. This doesn't seem to happen with either NM 0.8 nor the native NM 0.9 API, it appears to be a bug in the compatibility API. And the latest NetworkManager-0.8.9997-4.git20110620.fc15 build seems to be causing this for most or all users now, not just for a few people as before, and doesn't seem to work reliably even when it doesn't crash: https://bugzilla.redhat.com/show_bug.cgi?id=716446 But somehow these problems are NOT reproducible with your upstream nm09 code, at least not to our knowledge. We have this update: https://admin.fedoraproject.org/updates/kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15 in updates-testing now. This is a recent snapshot from the nm09 branch, and does not use that Fedora-specific compatibility API anymore. To all users who are experiencing crashes with the kde-plasma-networkmanagement-0.9-0.47.20110323.fc15 or kde-plasma-networkmanagement-0.9-0.47.20110323.fc15.1 builds, please try kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15 from updates-testing! We would like to push that 20110616 snapshot to the stable updates as soon as possible. (Please note that kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15 should be used together with NetworkManager-0.8.9997-4.git20110620.fc15. With the previous NetworkManager build, you may experience KDE bug #276004.) I've tried kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15 myself and have run into a couple issues with WPA-EAP secrets, see bug #276485 and bug #276486. (There have also been other issues with secrets reported on our mailing list, hopefully the reproducible ones will get bugs filed.) Now we're a bit stuck, the current build in F15 doesn't work anymore and the new one still has trouble migrating our existing connections. :-( (And migration issues cannot be fixed with a later update because it is a one-time event which deletes the original connections. I forgot to back up my networkmanagementrc, so I probably won't be able to do any further migration testing.) *** Bug 276477 has been marked as a duplicate of this bug. *** *** Bug 276495 has been marked as a duplicate of this bug. *** *** Bug 276496 has been marked as a duplicate of this bug. *** *** Bug 276481 has been marked as a duplicate of this bug. *** *** Bug 276506 has been marked as a duplicate of this bug. *** *** Bug 276529 has been marked as a duplicate of this bug. *** Created attachment 61359 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.2
- What I was doing when the application crashed:
Trying to connect WPA. On LAN connection it works, only with wifi it crush.
-- Backtrace (Reduced):
#11 0x48134ece in metacall (argv=0xbf9d7618, idx=26, cl=QMetaObject::InvokeMetaMethod, object=0xa0c1430) at kernel/qmetaobject.cpp:237
[...]
#14 0x4d1f28be in Plasma::CheckBox::toggled (this=0xa179838, _t1=false) at /usr/src/debug/kdelibs-4.6.3/i686-redhat-linux-gnu/plasma/checkbox.moc:145
#15 0x4d1f2967 in Plasma::CheckBox::qt_metacall (this=0xa179838, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf9d7898) at /usr/src/debug/kdelibs-4.6.3/i686-redhat-linux-gnu/plasma/checkbox.moc:96
#16 0x48134ece in metacall (argv=0xbf9d7898, idx=22, cl=QMetaObject::InvokeMetaMethod, object=0xa179838) at kernel/qmetaobject.cpp:237
[...]
#19 0x48fe12be in QAbstractButton::toggled (this=0xa17a4d8, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:213
*** Bug 276579 has been marked as a duplicate of this bug. *** *** Bug 276623 has been marked as a duplicate of this bug. *** *** Bug 276661 has been marked as a duplicate of this bug. *** *** Bug 276690 has been marked as a duplicate of this bug. *** *** Bug 276694 has been marked as a duplicate of this bug. *** *** Bug 276666 has been marked as a duplicate of this bug. *** *** Bug 276670 has been marked as a duplicate of this bug. *** *** Bug 276749 has been marked as a duplicate of this bug. *** *** Bug 276738 has been marked as a duplicate of this bug. *** *** Bug 276809 has been marked as a duplicate of this bug. *** *** Bug 276848 has been marked as a duplicate of this bug. *** |
Application: plasma-desktop (0.4) KDE Platform Version: 4.6.3 (4.6.3) Qt Version: 4.7.2 Operating System: Linux 2.6.38.6-27.fc15.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: "Edit network connection" dialog box was openned to connect to a WiFi with the following parameters: Security: WPA/WPA2 Authentication: PEAP Inner Authentication: MSCHAPv2 When I press the "OK" button the plasma crashed and got restarted. I do not observe this behavior when connecting to different WiFi networks (such as WEP encrypted, or using different Authentication i.e. WPA2/Personal). I am using Lenovo T410s laptop with built in WiFi: # lspci -v -s 03:00.0 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. Device e020 Flags: bus master, fast devsel, latency 0, IRQ 17 I/O ports at 2000 [size=256] Memory at f2400000 (32-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 88-55-22-fe-ff-4c-e0-00 Kernel driver in use: rtl819xSE Kernel modules: r8192se_pci The crash can be reproduced every time. -- Backtrace: Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #6 0x00007f2bd17ca1a5 in NMPopup::updateHasWireless (this=0x1d86260) at /usr/src/debug/networkmanagement-0.9/applet/nmpopup.cpp:536 #7 0x00007f2bd17ca937 in NMPopup::networkingEnabledToggled (this=0x1d86260, checked=false) at /usr/src/debug/networkmanagement-0.9/applet/nmpopup.cpp:512 #8 0x00007f2bd17c3ed4 in NMPopup::qt_metacall (this=0x1d86260, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffcd787190) at /usr/src/debug/networkmanagement-0.9/x86_64-redhat-linux-gnu/applet/moc_nmpopup.cpp:107 #9 0x0000003718b6ceca in QMetaObject::activate (sender=0x1e5da50, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffcd787190) at kernel/qobject.cpp:3278 #10 0x00000034e49ddddf in Plasma::CheckBox::toggled (this=<optimized out>, _t1=false) at /usr/src/debug/kdelibs-4.6.3/x86_64-redhat-linux-gnu/plasma/checkbox.moc:145 #11 0x00000034e49dde49 in Plasma::CheckBox::qt_metacall (this=0x1e5da50, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffcd787550) at /usr/src/debug/kdelibs-4.6.3/x86_64-redhat-linux-gnu/plasma/checkbox.moc:96 #12 0x0000003718b6ceca in QMetaObject::activate (sender=0x1e5dba0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffcd787550) at kernel/qobject.cpp:3278 #13 0x000000371ca18d02 in QAbstractButton::toggled (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:213 #14 0x000000371c76426e in QAbstractButton::setChecked (this=0x1e5dba0, checked=false) at widgets/qabstractbutton.cpp:766 #15 0x00007f2bd17ca526 in NMPopup::managerNetworkingEnabledChanged (this=0x1d86260, enabled=false) at /usr/src/debug/networkmanagement-0.9/applet/nmpopup.cpp:590 #16 0x00007f2bd17c3ef4 in NMPopup::qt_metacall (this=0x1d86260, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffcd7876e0) at /usr/src/debug/networkmanagement-0.9/x86_64-redhat-linux-gnu/applet/moc_nmpopup.cpp:108 #17 0x0000003718b6ceca in QMetaObject::activate (sender=0x1d200c0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffcd7876e0) at kernel/qobject.cpp:3278 #18 0x0000003727c1aeb2 in Solid::Control::NetworkManager::Notifier::networkingEnabledChanged (this=<optimized out>, _t1=false) at /usr/src/debug/kdebase-workspace-4.6.3/x86_64-redhat-linux-gnu/libs/solid/control/networkmanager.moc:138 #19 0x0000003727c1af64 in Solid::Control::NetworkManager::Notifier::qt_metacall (this=0x1d200c0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffcd787820) at /usr/src/debug/kdebase-workspace-4.6.3/x86_64-redhat-linux-gnu/libs/solid/control/networkmanager.moc:90 #20 0x0000003727c1b3d0 in Solid::Control::NetworkManagerPrivate::qt_metacall (this=0x1d200c0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffcd787820) at /usr/src/debug/kdebase-workspace-4.6.3/x86_64-redhat-linux-gnu/libs/solid/control/networkmanager_p.moc:76 #21 0x0000003718b6ceca in QMetaObject::activate (sender=0x1dfb570, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffcd787820) at kernel/qobject.cpp:3278 #22 0x00007f2bd0caf48f in NMNetworkManager::networkingEnabledChanged (this=<optimized out>, _t1=false) at /usr/src/debug/kdebase-workspace-4.6.3/x86_64-redhat-linux-gnu/solid/networkmanager-0.7/manager.moc:111 #23 0x00007f2bd0cb1fde in NMNetworkManager::propertiesChanged (this=0x1dfb570, properties=<optimized out>) at /usr/src/debug/kdebase-workspace-4.6.3/solid/networkmanager-0.7/manager.cpp:281 #24 0x00007f2bd0cb2b01 in NMNetworkManager::qt_metacall (this=0x1dfb570, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffcd787c00) at /usr/src/debug/kdebase-workspace-4.6.3/x86_64-redhat-linux-gnu/solid/networkmanager-0.7/manager.moc:98 #25 0x0000003718b6ceca in QMetaObject::activate (sender=0x1df9690, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffcd787c00) at kernel/qobject.cpp:3278 #26 0x00007f2bd0cbc3f5 in OrgFreedesktopNetworkManagerInterface::PropertiesChanged (this=<optimized out>, _t1=<optimized out>) at /usr/src/debug/kdebase-workspace-4.6.3/x86_64-redhat-linux-gnu/solid/networkmanager-0.7/nm-manager-clientinterface.moc:175 #27 0x00007f2bd0cbcc24 in OrgFreedesktopNetworkManagerInterface::qt_metacall (this=0x1df9690, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fffcd788000) at /usr/src/debug/kdebase-workspace-4.6.3/x86_64-redhat-linux-gnu/solid/networkmanager-0.7/nm-manager-clientinterface.moc:107 #28 0x00000037194205eb in QDBusConnectionPrivate::deliverCall (this=0x15b1010, object=0x1df9690, msg=..., metaTypes=..., slotIdx=7) at qdbusintegrator.cpp:941 #29 0x0000003719429d7f in QDBusCallDeliveryEvent::placeMetaCall (this=<optimized out>, object=<optimized out>) at qdbusintegrator_p.h:103 #30 0x0000003718b70a8a in QObject::event (this=0x1df9690, e=<optimized out>) at kernel/qobject.cpp:1217 #31 0x000000371c3b73d4 in notify_helper (e=0x294ca00, receiver=0x1df9690, this=0x1542b20) at kernel/qapplication.cpp:4462 #32 QApplicationPrivate::notify_helper (this=0x1542b20, receiver=0x1df9690, e=0x294ca00) at kernel/qapplication.cpp:4434 #33 0x000000371c3bc261 in QApplication::notify (this=0x1529400, receiver=0x1df9690, e=0x294ca00) at kernel/qapplication.cpp:4341 #34 0x000000371e641806 in KApplication::notify (this=0x1529400, receiver=0x1df9690, event=0x294ca00) at /usr/src/debug/kdelibs-4.6.3/kdeui/kernel/kapplication.cpp:311 #35 0x0000003718b5a1bc in QCoreApplication::notifyInternal (this=0x1529400, receiver=0x1df9690, event=0x294ca00) at kernel/qcoreapplication.cpp:731 #36 0x0000003718b5d784 in sendEvent (event=0x294ca00, receiver=0x1df9690) at kernel/qcoreapplication.h:215 #37 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x14ddcb0) at kernel/qcoreapplication.cpp:1372 #38 0x0000003718b848c3 in sendPostedEvents () at kernel/qcoreapplication.h:220 #39 postEventSourceDispatch (s=0x15489c0) at kernel/qeventdispatcher_glib.cpp:277 #40 0x000000370f642b6d in g_main_dispatch (context=0x15488e0) at gmain.c:2440 #41 g_main_context_dispatch (context=0x15488e0) at gmain.c:3013 #42 0x000000370f643348 in g_main_context_iterate (context=0x15488e0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3091 #43 0x000000370f6435dc in g_main_context_iteration (context=0x15488e0, may_block=1) at gmain.c:3154 #44 0x0000003718b84d1f in QEventDispatcherGlib::processEvents (this=0x14df7c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #45 0x000000371c459f2e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207 #46 0x0000003718b596d2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #47 0x0000003718b598cf in QEventLoop::exec (this=0x7fffcd7889c0, flags=...) at kernel/qeventloop.cpp:201 #48 0x000000371c7e2181 in QMenu::exec (this=<optimized out>, p=..., action=0x0) at widgets/qmenu.cpp:2059 #49 0x00000034e49661e3 in Plasma::PopupApplet::eventFilter (this=0x1d186d0, watched=<optimized out>, event=0x7fffcd788cd0) at /usr/src/debug/kdelibs-4.6.3/plasma/popupapplet.cpp:515 #50 0x0000003718b5a348 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<optimized out>, receiver=0x1fccac0, event=0x7fffcd788cd0) at kernel/qcoreapplication.cpp:846 #51 0x000000371c3b739f in notify_helper (e=0x7fffcd788cd0, receiver=0x1fccac0, this=0x1542b20) at kernel/qapplication.cpp:4458 #52 QApplicationPrivate::notify_helper (this=0x1542b20, receiver=0x1fccac0, e=0x7fffcd788cd0) at kernel/qapplication.cpp:4434 #53 0x000000371c3bc74c in QApplication::notify (this=<optimized out>, receiver=0x1fe48a0, e=0x7fffcd789040) at kernel/qapplication.cpp:4102 #54 0x000000371e641806 in KApplication::notify (this=0x1529400, receiver=0x1fe48a0, event=0x7fffcd789040) at /usr/src/debug/kdelibs-4.6.3/kdeui/kernel/kapplication.cpp:311 #55 0x0000003718b5a1bc in QCoreApplication::notifyInternal (this=0x1529400, receiver=0x1fe48a0, event=0x7fffcd789040) at kernel/qcoreapplication.cpp:731 #56 0x000000371c434048 in sendSpontaneousEvent (event=0x7fffcd789040, receiver=0x1fe48a0) at ../../src/corelib/kernel/qcoreapplication.h:218 #57 QETWidget::translateMouseEvent (this=<optimized out>, event=<optimized out>) at kernel/qapplication_x11.cpp:4466 #58 0x000000371c432eba in QApplication::x11ProcessEvent (this=0x1529400, event=0x7fffcd7898d0) at kernel/qapplication_x11.cpp:3587 #59 0x000000371c45a23c in x11EventSourceDispatch (s=0x15499b0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148 #60 0x000000370f642b6d in g_main_dispatch (context=0x15488e0) at gmain.c:2440 #61 g_main_context_dispatch (context=0x15488e0) at gmain.c:3013 #62 0x000000370f643348 in g_main_context_iterate (context=0x15488e0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3091 #63 0x000000370f6435dc in g_main_context_iteration (context=0x15488e0, may_block=1) at gmain.c:3154 #64 0x0000003718b84d1f in QEventDispatcherGlib::processEvents (this=0x14df7c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #65 0x000000371c459f2e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207 #66 0x0000003718b596d2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #67 0x0000003718b598cf in QEventLoop::exec (this=0x7fffcd789ca0, flags=...) at kernel/qeventloop.cpp:201 #68 0x0000003718b5da17 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008 #69 0x00000034e523f1e3 in kdemain (argc=1, argv=0x7fffcd78a088) at /usr/src/debug/kdebase-workspace-4.6.3/plasma/desktop/shell/main.cpp:120 #70 0x000000370fa2143d in __libc_start_main (main=0x400890 <main(int, char**)>, argc=1, ubp_av=0x7fffcd78a088, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffcd78a078) at libc-start.c:226 #71 0x00000000004008c1 in _start () Reported using DrKonqi