Bug 276898

Summary:	mobile busy notifier does not close after system startuo
Product:	[Unmaintained] Active	Reporter:	Robby Engelmann <robby.engelmann>
Component:	Plasma mobile shell	Assignee:	Marco Martin <notmart>
Status:	RESOLVED FIXED
Severity:	normal	CC:	active, robby.engelmann
Priority:	NOR
Version:	unspecified
Target Milestone:	unscheduled
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Robby Engelmann 2011-07-01 15:59:40 UTC

Version:           unspecified (using Devel) 
OS:                Linux

busy notifier remains on top of the desktop and have to be closed manually. It seems to collide somehow with Knetworkmanager, which asks for password for kwallet on startup

Reproducible: Always

Steps to Reproduce:
1. Set up system to manage connections via Networkmanager
2. Set up an WLAN connection to connect automatically
3. Restart.

Actual Results:  
busy notifier do not close after startup complete. It has to be closed manually using new task switcher. After that, kwallet password dialogue has to be bring to front before network connection can be established

Expected Results:  
busy notifier immediately shuts after startup completed. Kwallet password dialogue should be the active window.

I am using OpenSuse 11.4 with Kusc and Plasma Active packages on a WeTab.

Comment 1 Robby Engelmann 2011-07-06 20:13:53 UTC

After usage my tablet for a while, I recognized some more usecases where busy notifier have to be closed manually. e.g. sometimes after launching rekonq.

Comment 2 Sebastian Kügler 2011-07-14 10:41:26 UTC

This issue looks fixed, haven't seen it pop up for a while.

Robby, can you still reproduce it with current packages? (If so, I'll reopen.)

Comment 3 Robby Engelmann 2011-07-14 18:48:23 UTC

I tried it this evening (after updating). At system startup, after I typed my password for kwallet, knetwork-manager establishes connection. And: busy-notifier still needs much longer to close than wlan needs to be established.
By the way: In my mind, during establishing a network connection the user should not have to wait. It is a process in the background.

Thus the bug should be re-opened?

Comment 4 Aaron J. Seigo 2011-07-15 07:25:09 UTC

from your description, i think there are a few issues:

* kwallet should not have a password on these devices, and it should be imho pre-configured to be passwordless.

* busy widget shouldn't show at all for network connection, though i'm guessing that the busy widget is probably waiting for something else that is starting up?

one other configuration note.. i don't know if it is already configured this way, but i figure that on these devices session management probably doesn't make much sense. on log out (rare?) or power cycle, we probably do not need applications restored. for persistent application presence, i'd suggest that that would be the job of sleep/resume cycles. this should help start up times a bit.

Comment 5 Robby Engelmann 2011-07-15 18:03:38 UTC

as an answer to your issues raised:
1. Even if system startup is completed or I suspended to RAM at an place, where I did not have any connections available, after I manually establish a newly wlan connection at another place the busy notifier appears.
2. Considering the kwallet issue: In my opinion, kwallet should be configured with a password. I think a mobile device can easier be lost and I would not like to see my passwords in foreign hands.