Hi, I understand that it's difficult to deal with several bugs that look the same. Before I file a new bug. Is there anything I can do to distinguish the bug I have from the solve one? They have the same symptoms. Rafael. On Nov 14, 2013 10:31 PM, "Martin Pitt" <[email protected]> wrote:
> Rafael, thanks for testing. We know that this update does not fix the > problem for everyone, but it seems to fix it for half/most of the > reporters here. So may I ask for only declaring this verification-failed > if you see a regression, i. e. if this version makes it worse than > before? After you get this update, and we can exclude that particular > failure mode, we need a new bug report (as this has grown way too big > and noisy with too many subscribers, and this particular root cause has > been understood and fixed), where we do a new round of debugging and log > collection. Thank you! > > ** Tags removed: verification-failed > ** Tags added: verification-needed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1184262 > > Title: > times out too early, stuck in PrepareForSleep, causing network and > other services to not resume > > Status in “systemd” package in Ubuntu: > Invalid > Status in “systemd-shim” package in Ubuntu: > Fix Released > Status in “systemd” source package in Saucy: > Invalid > Status in “systemd-shim” source package in Saucy: > Fix Committed > Status in “systemd” source package in Trusty: > Invalid > Status in “systemd-shim” source package in Trusty: > Fix Released > > Bug description: > After a suspend/resume, network-manager claimed that wireless was not > available and would not let me reconnect to the wireless here. > 'iwlist wlan1 scan' would also not work; so thinking that it was a > driver problem, I rebooted the system. When it came back up, nm- > applet in lightdm claimed that networking was disabled, and the option > to enable it was greyed out. It could also not be enabled by nmcli. > I ended up stopping network-manager, bringing up the interface via > /etc/network/interfaces, and logging in... at which point, restarting > network-manager *did* let me enable networking from my logged-in > session. > > So there are several problems here: > - after a reboot, network-manager claimed networking was disabled. > - nm-applet is not letting me enable networking from the lightdm > session. > - the networking was failing after a suspend/resume cycle, and could > not be enabled even from inside the user session. > > The last issue probably *was* a kernel driver problem; but the first > two issues are network-manager problems of some kind. > > SRU INFORMATION: > ---------------- > Reproducer: > - Force suspend to take very long by adding a sleep: > echo -e '#!/bin/sh\nsleep 15\nexit 1' | sudo tee > /usr/lib/pm-utils/sleep.d/00break > (this will also make suspend fail, which eases testing) > - Suspend from the menu or with > sudo gdbus call -y -d org.freedesktop.login1 -o > /org/freedesktop/login1 -m org.freedesktop.login1.Manager.Suspend true > - With the 13.10 final version, systemd-shim will (often) time out, and > the next Suspend call from above will fail with "Operation already in > progress" and the network does not come back up. With the fixed version, > network should be back up and the Suspend() call can be issued many times. > > Fix: > https://github.com/desrt/systemd-shim/commit/136ed1143077d13c2 > https://github.com/desrt/systemd-shim/commit/16a7fdc0652ad78f4 > > Regression potential: Errors in this code could potentially break > suspend/shutdown completely, so for verification both of these > functionalities ought to be tested on real hardware. > > ProblemType: Bug > DistroRelease: Ubuntu 13.10 > Package: network-manager 0.9.8.0-0ubuntu8 > ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 > Uname: Linux 3.9.0-2-generic x86_64 > ApportVersion: 2.10.2-0ubuntu1 > Architecture: amd64 > Date: Sat May 25 21:38:31 2013 > InstallationDate: Installed on 2010-09-24 (974 days ago) > InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 > (20100816.1) > IpRoute: > default via 192.168.1.1 dev wlan1 > 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 > 169.254.0.0/16 dev wlan1 scope link metric 1000 > 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 > 192.168.122.0/24 dev virbr0 proto kernel scope link src > 192.168.122.1 > MarkForUpload: True > NetworkManager.state: > [main] > NetworkingEnabled=false > WirelessEnabled=true > WWANEnabled=true > SourcePackage: network-manager > UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) > WifiSyslog: > > nmcli-con: > Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: > ** (process:11977): WARNING **: Could not initialize NMClient > /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager > was not provided by any .service files > Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't > match. Force execution using --nocheck, but the results are unpredictable. > nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit > code 8: Error: NetworkManager is not running. > nmcli-nm: > RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE > WIFI WWAN-HARDWARE WWAN > not running unknown unknown unknown unknown > unknown unknown unknown > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: times out too early, stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
