| Summary: | kded4 and plasma-desktop crash with kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15.i686 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lukas Middendorf <lukas+fedora> |
| Component: | kde-plasma-networkmanagement | Assignee: | Rex Dieter <rdieter> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | kevin, ltinkl, rdieter |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | kde-plasma-networkmanagement-0.9-0.66.rc3.nm09.fc15 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-09 18:08:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Attachments: | |||
Hrm, without a good backtrace, I'm not sure we can even attempt to debug this. I just tried to rebuild the kde-plasma-networkmanagement from source, still the same problems (crash and debug info missing). Any clue how this build-id stuff works and where this "-" comes from? Created attachment 510695 [details]
backtrace of plasma-desktop (also seems quite useless)
That missing build-id came from nvidia driver. After switching to nouveau again that is gone, but the backtrace is still the same.
The backtrace of plasma-desktop doesn't look much more useful to me, but I attached it anyways.
When I try to start kded4 from konsole, I get the following output:
Object::connect: No such signal NMNetworkManager::wwanEnabledChanged(bool)
Object::connect: No such signal NMNetworkManager::wwanHardwareEnabledChanged(bool)
I created a new user with a clean home and there the crash does not happen. Seems to be related to some configuration I have (no, I do not want to delete ~/.kde to resolve that crash).
Could you supply your files, ~/.kde/share/config/networkmanagementrc ~/.kde/share/apps/networkmanagement/* and out of paranoia, the output of: getsebool allow_execmem (it should say "on") Created attachment 510703 [details]
~/.kde/share/apps/networkmanagement/connections/\{3b56c423-c9fe-4c70-b94b-14e75b27d487\}
$ getsebool allow_execmem
allow_execmem --> on
$ cat ~/.kde/share/config/networkmanagementrc
[Connection_{3b56c423-c9fe-4c70-b94b-14e75b27d487}]
Name=eduroam
Type=802-11-wireless
[General]
Connections={3b56c423-c9fe-4c70-b94b-14e75b27d487}
[SystemTray]
NetworkingEnabled=true
WirelessEnabled=false
I removed my user name from the attached ~/.kde/share/apps/networkmanagement/connections/\{3b56c423-c9fe-4c70-b94b-14e75b27d487\}
Deleting the named files was one of the first things I tried, but that does not seem to be the cause.
this issue *should* be fixed in https://admin.fedoraproject.org/updates/FEDORA-2011-16529/kde-plasma-networkmanagement-0.9-0.66.rc3.nm09.fc15 are you still experiencing problems? (if so, we've another update on the way) Seems to be fixed. Or I accidentally removed the configuration that made it crash in the first place, but that is quite unlikely. OK, thanks! |
Created attachment 510497 [details] quite useless backtrace Description of problem: new kde-plasma-networkmanagement leads to immediate crashes Version-Release number of selected component (if applicable): kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15.i686 NetworkManager-0.8.9997-4.git20110620.fc15.i686 kdelibs-4.6.4-5.fc15 (also with previous 4.6.3) How reproducible: Always Steps to Reproduce: 1. make sure "Network Management" is disabled in "system tray settings" 2. install kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15.i686 3. log out and log in again Actual results: kded4 crashes in new session. If you enable "Network Management" for system tray also plasma-desktop crashes. If you try to log in with "Network Management" enabled, then you end up with a desktop without plasma. Additional info: There are no error messages from NetworkManager in syslog. Unfortunately there seems to be some problems with the debug info that prevents the generation of a proper backtrace (locally or with retrace server). The debug info kernel-PAEdebug is used although I'm running kernel-PAE. One debug info file can not be found (/usr/lib/debug/.build-id/-/.debug).