Also, during the same round of testing I reported bug #1426876, which describes how the user can enter a PIN on the SIM unlock screen and have it not take effect. This occurs more frequently than the problem described by this bug.
I just lowered the Importance to High, as it's extremely hard to reproduce this bug. I've hit it 3 or 4 times out of 100 reboots. That said, if it's possible to identify the conditions in which the indicator can start, but not display any panel icons, the indicator should be re-factored to never do this. The cellular modem is a dynamic complex pieces of hardware and the indicator needs to be tolerant of what may seem to be invalid states which may exist temporarily. ** Changed in: indicator-network (Ubuntu) Importance: Critical => High ** Description changed: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed It's possible for the device to boot in such a manner that the network- indicator doesn't display an icon on the top panel ( see attached screenshot ). - I was testing a change to ofono ( currently in silo ubuntu-013 ) which - fixes a MTK-specific bug where the device boots and the 2nd SIM slot - isn't recognized. So to test, I continually rebooted the device. I - have two SIMs installed, the first unlocked, the second is locked. + This bug was discovered while testing an ofono vivid silo. The + associated ofono merge request is: + + https://code.launchpad.net/~phablet-team/ofono/ww10-update/+merge/250665 + + The version of ofono in the silo (ubuntu-013) is: + + 1.12.bzr6888+15.04.20150224-0ubuntu1 + + This version of ofono fixes a couple of bugs, the most important being a + regression on krillin where the 2nd SIM isn't always recognized on boot. + + My testing was performed using two SIMs, with the 2nd SIM being PIN- + locked. In the case of the missing icon, no PIN unlock screen was displayed after booting. I checked using 'ps' and an indicator-network process is running, however when I checked /home/phablet/.cache/upstart, there only indicator-network log files I see are the saved .gz files. There's no unzipped/current indicator-network.log. The .gz log file with the most recent timestamp shows a single log message: phablet@ubuntu-phablet:~/.cache/upstart$ less indicator-network.log.1.gz void core::dbus::Property<T>::handle_changed(const core::dbus::types::Variant&) [with PropertyType = org::freedesktop::URfkill::Interface::Killswitch::Property::State]: org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist I checked and urfkilld is running on the system. I also verified that there were no crash files present on the system. I also checked and there was nothing relevant in syslog. This bug is hard to reproduce as well. I've hit it 4 or 5 times out of a total of maybe 45-50 reboots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426467 Title: Indicator can fail to display panel icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1426467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
