https://bugzilla.novell.com/show_bug.cgi?id=819514 https://bugzilla.novell.com/show_bug.cgi?id=819514#c1 Roberto Cristian <roberto@echelon-it.ro> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roberto@echelon-it.ro --- Comment #1 from Roberto Cristian <roberto@echelon-it.ro> 2013-05-11 23:44:07 UTC --- (In reply to comment #0)

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0

First reported in this Forum thread http://forums.opensuse.org/english/get-technical-help-here/network-internet/...

For others in the thread, unknown whether recommendations were helpful. Note that others in the thread were not using Network Manager, whereas I am.

For myself, my wireless networking was not functional (for that matter any networking) was functional resuming from sleep.

Attempted to systemctl stop|start|restart network.service

systemctl status network service returned Active with no errors after each above attempt. Service was verified stopped and restarted without errors.

After rebooting, my network was still unavailable. Attampted again to stop|start|restart services.

Then, I did a hardware NIC disable/re-enable which resulted in NM reporting networking enabled, but wireless "undetermined" (no check or unchecked box, a weird white box).

Using NM, unchecked, re-checked "networking" and the wireless box was "normal, unchecked" Checked the box an wireless is working.

After the wireless working was working again, I re-ran "systemctl status network.service" with the following results

NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Sat 2013-05-11 14:35:15 PDT; 56s ago Main PID: 26829 (NetworkManager) CGroup: name=systemd:/system/NetworkManager.service └─26829 /usr/sbin/NetworkManager --no-daemon

May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr2): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/virbr2-nic: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr0): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr2): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/virbr2-nic: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> ModemManager available in the bus

The above may not be helpful, I suspect that the errors only refer to a number of virtual device bridges I have configured on this machine, but of course NM does not support managing those.

Reproducible: Always

Steps to Reproduce: 1. zypper up 5/10/2013 2. Put machine to sleep 3. resume machine Actual Results: Networking unavailable.

Expected Results: Network should re-connect to available networks automatically

Assigning Major, but impact likely depends on whether the User is able to regain networking either by restarting the network service or re-booting. If there are critical programs which would be adversely affected by a re-boot, then the problem is very serious, maybe even critical.

I've opened the forum thread. I experience the issue with wired ethernet, no wifi. After the update I have to manually restart the network.service every time I resume from Sleep or log-in after logging out. It works though if I reboot the PC. I am on 12.2 x64 KDE -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=819514 https://bugzilla.novell.com/show_bug.cgi?id=819514#c3 --- Comment #3 from Tony Su <tonysu@su-networking.com> 2013-05-13 23:20:20 UTC --- This bug seems to be short-lived. Once addressed by boot or whatever, is not seen again. So, IMO this is not a bug that itself needs to be fixed, but should be understood so not repeated in the future. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=819514 http://bugzilla.novell.com/show_bug.cgi?id=819514#c7 Andor Dávid <david-andor@kozpontiagy.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david-andor@kozpontiagy.hu --- Comment #7 from Andor Dávid <david-andor@kozpontiagy.hu> --- I have the same problem on openSUSE tumbleweed with "Wired connection 1" When I turn on my laptop both wireless and wired connections work well but after a suspend only the wireless connection works even if I stop and start the "network.service" with systemctl. The wired connection doesn't work after resume. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=819514 http://bugzilla.novell.com/show_bug.cgi?id=819514#c9 Erik Martre <erik.martre@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erik.martre@gmail.com --- Comment #9 from Erik Martre <erik.martre@gmail.com> --- I have this bug too on my laptop (ASUS with Realtek PCIe gbe ethernet card), with OpenSuse Tubleweed upgraded from Leap 42.3, but with KDE Desktop instead of Gnome. In the previous days, it would not connect again even after rebooting and I'd have to boot on my W10 partition - ethernet was still disconnected and I had to run "netsh winsock reset" in powershell. Now, after some package updates I just have to reboot Tumbleweed (sudo systemctl restart NetworkManager has no visible effect, apart network icon disappearing and coming back, of course). I'm not experienced in network problems but I do not see the reason why this bug should be related to Firefox ??? Should I open a new bug file ? -- You are receiving this mail because: You are on the CC list for the bug.