[Bug 1584612] Re: Mobile broadband requires reboot every time

2016-10-19 Thread Con Kolivas
I considered what you said and put the sim card into a phone even though it was allegedly unlocked and set it as you suggested and indeed it does NOT ask for a pin now. I would consider the main issue resolved now, thanks! I've been fighting this for 2 years unsuccessfully so this is a major win

[Bug 1584612] Re: Mobile broadband requires reboot every time

2016-10-18 Thread Con Kolivas
Problem persists on 16.10 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-nm in Ubuntu. https://bugs.launchpad.net/bugs/1584612 Title: Mobile broadband requires reboot every time To manage notifications about this bug go to:

[Bug 1628715] Re: Kf5 based apps do not reliably storeSession and performLegacySessionSave

2016-10-02 Thread Con Kolivas
Also note that this is not confined to just konversation as quite a few other KDE applications also do not reliably resume - notably konsole, kate, kmail and ktorrent for example. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to konversation

[Bug 1628715] [NEW] Kf5 based apps do not reliably storeSession and performLegacySessionSave

2016-09-28 Thread Con Kolivas
Public bug reported: Kf5 based applications do not reliably start up again on new sessions after logging out and in again. This was noted specifically on konversation as discussed in this bug here (Konversation session doesn't resume): https://bugs.kde.org/show_bug.cgi?id=363876 but other

[Bug 1584604] Re: Slow login to kde5 waiting on breeze splash

2016-07-02 Thread Con Kolivas
Confirmed this fixes it for me too. I've removed plasma-nm from the affected packages and added breeze. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to breeze in Ubuntu. https://bugs.launchpad.net/bugs/1584604 Title: Slow login to kde5

[Bug 1584604] Re: Slow login to kde5 waiting on ?networkmanager

2016-07-02 Thread Con Kolivas
** Also affects: breeze-qt4 (Ubuntu) Importance: Undecided Status: New ** No longer affects: plasma-nm (Ubuntu) ** Summary changed: - Slow login to kde5 waiting on ?networkmanager + Slow login to kde5 waiting on breeze splash ** Also affects: breeze (Ubuntu) Importance: Undecided

[Bug 1584604] Re: Slow login to kde5 waiting on ?networkmanager

2016-06-09 Thread Con Kolivas
** Summary changed: - Slow login to kde5 waiting on networkmanager + Slow login to kde5 waiting on ?networkmanager -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-nm in Ubuntu. https://bugs.launchpad.net/bugs/1584604 Title: Slow

[Bug 1584604] Re: Slow login to kde5 waiting on networkmanager

2016-05-26 Thread Con Kolivas
I'm not sure what other debugging info I can add then to help find the cause. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-nm in Ubuntu. https://bugs.launchpad.net/bugs/1584604 Title: Slow login to kde5 waiting on networkmanager

[Bug 1584604] Re: Slow login to kde5 waiting on networkmanager

2016-05-26 Thread Con Kolivas
I checked on my desktop PC as well which has the login lag and systemd- analyze blame gave me these top 10 with the same first candidate: 7.851s NetworkManager-wait-online.service 303ms apt-daily.service 239ms dev-sda2.device 223ms upower.service

[Bug 1584612] [NEW] Mobile broadband requires reboot every time

2016-05-23 Thread Con Kolivas
Public bug reported: I have a laptop with a mobile broadband device which only ever initialises on a reboot. If I suspend to ram and then resume it fails to work. If I power the machine down and then cold boot it asks for the sim pin code which then also asks for the administrator password.

[Bug 1584604] [NEW] Slow login to kde5 waiting on networkmanager

2016-05-23 Thread Con Kolivas
Public bug reported: I still get the slow login as happened with kubuntu 15.10 now on a fresh install of kubuntu 16.04 on multiple systems. The pause is identical to as happened in this bug which is marked as closed, but it does not appear to be bluetooth related this time: