[greeter] strange persistent "Enter SIM1 PIN" dialog on Greeter

[Olga Kemmet]

Build r133 Krillin

I'm not entirely sure how to reproduce this bug but I try to sum up the conditions and how the phone was set up before.

1. Make sure both SIM cards are inserted
2. SIM1 is locked
3. reboot device
4 skip SIM PIN entry

When skipping the SIM PIN entry screen, you can see a small glitch on the top of the screen. It looks like a dialog/snap but it disappears very quickly.

Now, I had my device locked for a while and when I unlocked it via the hard key button a snap decision appeared on top of the greeter saying "Enter SIM PIN1". It is possible to swipe away the greeter screen but then this is it. You are basically stuck.
I managed as well to pull down the notifications menu but the snap stayed on top of that.
It looks like there is there passcode screen in the background and if you want to return back to the greeter you have to lock/unlock the device with the hard key button.

Maybe anyone can reproduce this bug or knows what causes it. Please see attached screenshots for more visual info.

Update:
14.04 r269 krillin

The glitch of briefly appearing dialog still persists. Every time the device is rebooted and user has to enter the SIM PIN.

--------UX comment---------

The desired resolution is that users are presented with the actual SIM PIN screen without the appearing glitch.

[Michał Sawicz (saviq)]

Yeah, so... this is the SIM PIN dialog... before it understands it's actually a fullscreen SIM PIN dialog. Usually it's just a split second between the two, but somehow you got it stuck.

Would be nice to know if you find a way to reproduce. Adding an indicator-network and unity-notifications tasks in the mean time, as it's either i-n keeping the notification up, or maybe i-n crashed and the notification did not get pulled...

Being able to swipe it away would be useful, too, as per bug #1355422.

[kevin gunn (kgunn72)]

@paul - might be good to just try and repro for a bit. if you give it a good amount of time & fail to repro then mark it incomplete.

[Antti Kaijanmäki (kaijanmaki)]

the interesting part is that the full dialog was not shown. Even if i-network would have crashed after requesting the dialog, unity8 still should load it and show it fully.

Then again, the dialog would not do anything if i-network is dead, so the notification-service (unity8) should monitor the snap-decision invokers and automatically clean up any snap decisions from a d-bus unique name that loses it's owner.

[Michał Sawicz (saviq)]

I think it might not load it fully if it can't read the menumodel, which went away, is all.

[kevin gunn (kgunn72)]

changing as paul is missing a krillin

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Pete Woods (pete-woods)]

I semi-recently made some improvements to the notifications server in unity8 to kill off the notifications of any process that dies. So The SIM unlock code in the indicator has also had much improvement.

So I think this is *likely* :) to not occur again.

[Olga Kemmet (olga-kemmet)]

I'm really sorry but it still does happen on krillin: tested it on 15.04 (r140)