Summary: | plasma crash | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | amedeo.delle.bande.nere |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bhush94, jr, notmart, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.3.1 | ||
Target Milestone: | 1.0 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
attachment-16767-0.html
attachment-17372-0.html |
Description
amedeo.delle.bande.nere
2015-06-24 20:16:42 UTC
debug symbols seems ok for Qt, can it be reproduced with debug packages installed for plasma-framework? *** This bug has been marked as a duplicate of bug 346118 *** Created attachment 93327 [details] attachment-16767-0.html To get connected and to reply to your question I had to reboot twice, plus a ctrl+alt+backspace Then at the 4th attempt (lucky, it takes 7 tries at least) I connected to my wifi Then while typing this email the connection has been dropping 3 times, right now it seems to stay alive. As you KDE team decided to BIND the CRAPPY network-manager to the whole kubuntu-desktop - I mean to the whole thing - and as the previous 14.10 kubuntu worked FLAWLESSLY with the ath9k driver and WICD network manager, the *point and core question *is: Are you going to unlink the graphical manager from the network manager, aren't you? so that the user (for example I) will be able to uninstall network-manager and replace it with the previous WORKING one? Are you going to make ath9k working again, so that I would get rid of ndiswrapper? or do I have to be glad to rely on Micro$oft stuff again? Thanks Amedeo On Thu, Jun 25, 2015 at 4:29 AM, Marco Martin <notmart@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=349580 > > Marco Martin <notmart@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |notmart@gmail.com > > --- Comment #1 from Marco Martin <notmart@gmail.com> --- > debug symbols seems ok for Qt, can it be reproduced with debug packages > installed for plasma-framework? > > -- > You are receiving this mail because: > You reported the bug. > (In reply to amedeo.delle.bande.nere from comment #3) > the *point and core question *is: > > Are you going to unlink the graphical manager from the network manager, > aren't you? so that the user (for example I) will be able to uninstall > network-manager and replace it with the previous WORKING one? You can uninstall plasma-nm package if you don't want to use the Plasma Network manager. > > Are you going to make ath9k working again, so that I would get rid of > ndiswrapper? or do I have to be glad to rely on Micro$oft stuff again? > This has nothing to do with Plasma or even KDE to that regards. And on sidenote : Please don't CC mails directly to developer on bug reports.. Just commenting here is enough to notify us. Created attachment 93328 [details] attachment-17372-0.html That below for the sake of the truth amedeo@corinthiano:~$ sudo apt-get remove plasma-nm [sudo] password for amedeo: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: baloo-utils kde-style-oxygen-qt5 krdc libkf5activitiesexperimentalstats1 libkf5modemmanagerqt6 libkfontinst5 libkfontinstui5 libndp0 liboath0 libopenconnect3 liboxygenstyle5-5 liboxygenstyleconfig5-5 libstoken1 libtomcrypt0 libtommath0 libxcb-record0 linux-headers-3.19.0-20 linux-headers-3.19.0-20-generic linux-image-3.19.0-20-generic linux-image-extra-3.19.0-20-generic network-manager network-manager-pptp plasma-desktop-data sni-qt Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: * kde-config-touchpad kde-touchpad kubuntu-desktop plasma-desktop plasma-nm plasma-nm-dbg* 0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded. After this operation, 30,3 MB disk space will be freed. Do you want to continue? [Y/n] Also, I can't remove the previous kernel because is way more reliable Amedeo On Thu, Jun 25, 2015 at 12:37 PM, Bhushan Shah <bhush94@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=349580 > > --- Comment #4 from Bhushan Shah <bhush94@gmail.com> --- > (In reply to amedeo.delle.bande.nere from comment #3) > > the *point and core question *is: > > > > Are you going to unlink the graphical manager from the network manager, > > aren't you? so that the user (for example I) will be able to uninstall > > network-manager and replace it with the previous WORKING one? > > You can uninstall plasma-nm package if you don't want to use the Plasma > Network > manager. > > > > > Are you going to make ath9k working again, so that I would get rid of > > ndiswrapper? or do I have to be glad to rely on Micro$oft stuff again? > > > > This has nothing to do with Plasma or even KDE to that regards. > > And on sidenote : Please don't CC mails directly to developer on bug > reports.. > Just commenting here is enough to notify us. > > -- > You are receiving this mail because: > You reported the bug. > Looks like Kubuntu packages have a hard depends on plasma-nm, I've fixed this now but it won't be changed until the 5.3.2 update to stop loading plasma-nm just remove its .desktop file sudo rm /usr/share/kservices5/plasma-applet-org.kde.plasma.networkmanagement.desktop |