| Summary: | Random plasma segfault. | ||
|---|---|---|---|
| Product: | [Unmaintained] Network Management | Reporter: | P. Varet <p.varet> |
| Component: | Plasma Widget | Assignee: | Sebastian Kügler <sebas> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | aaronluna75, lamarque, p.varet, wstephenson |
| Priority: | NOR | ||
| Version: | 0.9 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
P. Varet
2012-03-25 12:54:54 UTC
Created attachment 70045 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0
- What I was doing when the application crashed:
Nothing whatsoever. It happened completely randomly.
-- Backtrace (Reduced):
#6 0x00007f06a8996422 in qobject_cast<Solid::Control::Ifaces::NetworkInterfaceNm09*> (object=0x51) at ../../../../../solidcontrolfuture/libs/solid/control/ifaces/networkinterface.h:166
#7 Solid::Control::NetworkInterfaceNm09::connectionState (this=<optimized out>) at ../../../../../solidcontrolfuture/libs/solid/control/networkinterface.cpp:125
#8 0x00007f06a94b5a41 in NetworkManagerApplet::interfaceConnectionStateChanged (this=0x2047f90) at ../../applet/networkmanager.cpp:562
#9 0x00007f06a94b7f19 in NetworkManagerApplet::networkInterfaceRemoved (this=0x2047f90, uni=...) at ../../applet/networkmanager.cpp:532
#10 0x00007f06a94b9ae9 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./networkmanager.moc:101
Wich Plasma NM version do you use? You can see the version in "Manage Connections" -> "Other". OBS: I am asking the Plasma NM version, not NetworkManager's version. Please upgrade to the latest Plasma NM and check if that solves your problem: http://lamarque-lvs.blogspot.com.br/2012/02/plasma-nm-090.html Hi Lamarque, thank you for the reply! I'm on Plasma NM 0.9.0, which appears to be the latest version. If the bug is NM-related, maybe this additional bit of information about my setup will be useful: I've got two network cards, with only one with a cable plugged in. (Not sure how that could be relevant, but you never know?) According to the crash log Plasma NM received a NMNetworkManagerNm09::nameOwnerChanged from NetworkManager, which means NetworkManager was stopped or crashed. Which NetworkManager version do you use? Is there any error message in NetworkManager's log? Hi Lamarque! Thank your for your reply. Sorry about the delay in my response. I have NetworkManager version 0.9.1.90-0ubuntu5.1. And good catch, I have NM segfaults in my logs: syslog.1:Apr 3 08:50:18 linux kernel: [128706.401841] NetworkManager[9329]: segfault at 8 ip 0000000000442751 sp 00007fffca60eb20 error 4 in NetworkManager[400000+ce000] So I guess there are two problems, then: 1/ the segfault in NM, and 2/ the segfault in Plasma NM when NM aborts for its own reasons! Git commit 5fee138a29f1d5c14fa67f7222ee110a5e87bb68 by Lamarque V. Souza. Committed on 06/04/2012 at 20:05. Pushed by lvsouza into branch 'nm09'. Do not send the interfaceRemoved signal if NM stopped or crashed. If it has crashed we can crash too if we send the interfaceRemoved signal here. M +1 -8 solidcontrolfuture/solid/networkmanager-0.9/manager.cpp http://commits.kde.org/networkmanagement/5fee138a29f1d5c14fa67f7222ee110a5e87bb68 Fantastic! Thank you, you've been very helpful. Looking forward to the next release! *** Bug 311285 has been marked as a duplicate of this bug. *** |