Summary: | Plasma-desktop crash after restarting network-manager service | ||
---|---|---|---|
Product: | [Unmaintained] Network Management | Reporter: | Ruszkai Ákos <erakionv43> |
Component: | KDED Module | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | erakionv43, lamarque |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ruszkai Ákos
2011-03-14 16:02:26 UTC
*** Bug 268475 has been marked as a duplicate of this bug. *** ark5 is part of your wireless card driver. The crash log you sent has nothing to do with NetworkManagement, it shows a crash in Plasma itself. (In reply to comment #2) > ark5 is part of your wireless card driver. The crash log you sent has nothing > to do with NetworkManagement, it shows a crash in Plasma itself. Thank you for the explanation. However, for various reasons (mainly for performance and quality of wireless connection) I've removed and blacklisted the rtl8187 driver shipped by the kernel, and switched to ndiswrapper. I couldn't reproduce the bug since that, thought it's been since only a few hours now. Shall I report, if I can't experience problems with ndiswrapper? (In reply to comment #3) > (In reply to comment #2) > > ark5 is part of your wireless card driver. The crash log you sent has nothing > > to do with NetworkManagement, it shows a crash in Plasma itself. > > Thank you for the explanation. However, for various reasons (mainly for > performance and quality of wireless connection) I've removed and blacklisted > the rtl8187 driver shipped by the kernel, and switched to ndiswrapper. I > couldn't reproduce the bug since that, thought it's been since only a few hours > now. Shall I report, if I can't experience problems with ndiswrapper? That is strange, ar5k is part of atheros wireless driver. rtl8187 is from Realtek. It may be that you had a problem with your wireless driver but I have seen that backtrace regarding KIconLoaderPrivate::makeCacheKey in some recent bug reports. Fixing bugs in cache can be very tricky, they are difficult to reproduce. Hello On a totally different computer, with totally different hardware (no wireless card even!), I've managed to reproduce the bug by doing: alsa force-reload as root. Backtrace: http://pastebin.com/Fwm187Qs The crashreporter window still complains about ar5k, however I have: 02:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 01) That KIconEffect::fingerprint bug is a old bug in KDE, it is not Plasma NM specific, it seems it is a problem in KIconLoader, which is a library that several KDE programs use, including Plasma NM, Amarok, Kopete, the panel, etc. Unfortunately it is very difficult to reproduce it and even more to diagnostic it. It seems to happen because of a memory corruption that nobody has been able to identify where it happens. *** This bug has been marked as a duplicate of bug 226596 *** |