no network after wake from sleep, also no messages file in /var/log

after wake from sleep my computer has no network, I tried service network restart but didn’t help. I can ping my router 192.168.1.1 but cannot ping any public IP like e.g. 8.8.8.8 = google DNS. It’s really anoying. It happens pretty often after waking from sleep and I’ve to restart - it happens to be some serious bug. And what’s even more worrying that I’ve no messages file in /var/log

From a Tumbleweed point of view and an older ThinkPad, I’m not seeing it here with KDE (on a wifi connection). After sleeping the network reconnection is fast, and visible on Network Manager’s tray icon.

Have you searched through openSUSE bugzilla for a similar report?

What is your default route when the problem occurs?

sudo /sbin/route -n

I haven’t found it in bugzilla, currently I rather dont resetart my laptop :smiley: maybe after new kerenl/update

now I am really confused, I want to report a bug via command line (I installed bugzilla). so I did buzilla --help but nothing quite useful ( like where to specify server where I am reporting a bug…) I read this manual on opensuse bugzilla page but still https://bugzilla.opensuse.org/docs/en/html/bugreports.html#fillingbugs -but htere is nothing about command line. so I tried on buzilla page to click new-> but no create a bug or smth like that.

On 2014-12-19 11:46, roberto68 wrote:
>
> now I am really confused, I want to report a bug via command line (I
> installed bugzilla). so I did buzilla --help but nothing quite useful (
> like where to specify server where I am reporting a bug…) I read this
> manual on opensuse bugzilla page but still http://tinyurl.com/l8saoet
> -but htere is nothing about command line. so I tried on buzilla page to
> click new-> but no create a bug or smth like that.

Bugailla is not a command. It is system with a webpage that we use to
officially report bugs. But you have not proven you found a bug. We
simply told you to search there for something similar to your problem.

openSUSE:Submitting bug
reports


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

On Thu, 25 Dec 2014 23:43:07 +0000, Carlos E. R. wrote:

> Bugailla is not a command.

Information for package python-bugzilla:

Repository: Main Repository (OSS)
Name: python-bugzilla
Version: 0.9.0suse3-4.1.4
Arch: noarch
Vendor: openSUSE
Installed: No
Status: not installed
Installed Size: 219.6 KiB
Summary: Python library for bugzilla
Description:
This is a python module that provides a nice, python-ish interface to
Bugzilla
over XMLRPC.
It was originally written specifically for Red Hat’s Bugzilla instance,
but
now
supports the Web Services provided by upstream Bugzilla 3.0 and 3.2
also.
It also includes a ‘bugzilla’ commandline client which can be used for
quick,
ad-hoc bugzilla jiggery-pokery. I guess you could use it in shell
scripts too,
but gosh - why not just write something in Python instead?

:slight_smile:


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

On 2014-12-26 03:07, Jim Henderson wrote:
> On Thu, 25 Dec 2014 23:43:07 +0000, Carlos E. R. wrote:
>
>> Bugailla is not a command.
>
> Information for package python-bugzilla:

Gosh! :-o

> Installed Size: 219.6 KiB
> Summary: Python library for bugzilla

Ah, then it is “only” a library…

> It also includes a ‘bugzilla’ commandline client which can be used for
> quick,

Ah, “not only” a library, then.

I have the suspicion that the interface would send even seasoned users
running for their life ;-p


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

On Fri, 26 Dec 2014 02:33:06 +0000, Carlos E. R. wrote:

> On 2014-12-26 03:07, Jim Henderson wrote:
>> On Thu, 25 Dec 2014 23:43:07 +0000, Carlos E. R. wrote:
>>
>>> Bugailla is not a command.
>>
>> Information for package python-bugzilla:
>
> Gosh! :-o
>
>> Installed Size: 219.6 KiB Summary: Python library for bugzilla
>
> Ah, then it is “only” a library…
>
>> It also includes a ‘bugzilla’ commandline client which can be used
>> for
>> quick,
>
> Ah, “not only” a library, then.
>
> I have the suspicion that the interface would send even seasoned users
> running for their life ;-p

“cnf bugzilla” was useful to find this out. :slight_smile:

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

I have the same problem. Can replicate it on 13.2 too. After suspend, the network is disabled.
On the Gnome desktop, the system tray says “hardware disabled- use hardware switch to enable”.

I found a perhaps relevant point in the 13.2 release notes (see section 4.5)- http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.2/#technical

From that, i checked my /etc/polkit-default-privs.standard, and noticed the following lines:

# org.freedesktop.network-manager-settings.system.modify          auth_admin_keep_always 
org.freedesktop.network-manager-settings.system.hostname.modify auth_admin_keep 
org.freedesktop.network-manager-settings.system.wifi.share.protected auth_admin 
org.freedesktop.network-manager-settings.system.wifi.share.open auth_admin 
org.freedesktop.NetworkManager.enable-disable-network           auth_admin:auth_admin:yes 
org.freedesktop.NetworkManager.enable-disable-wifi              auth_admin:auth_admin:yes 
org.freedesktop.NetworkManager.enable-disable-wwan              auth_admin:auth_admin:yes 
org.freedesktop.NetworkManager.use-user-connections             auth_admin:auth_admin:yes 
**# auth_admin probably causes issues with suspend here (bnc#716291) **
org.freedesktop.NetworkManager.network-control                  no:no:yes 
org.freedesktop.NetworkManager.sleep-wake                       auth_admin:auth_admin:yes 
# bnc#680140

That comment seems important…?

Thanks for any help, would really like to solve this problem!

Cant edit previous post, so sorry for reposting.

An old thread mentions a possible solution: https://forums.opensuse.org/showthread.php/449420-After-Hibernate-or-Sleep-can-t-connect-to-any-wireless-network?p=2252505#post2252505

Will try and report back. Thanks.

I have something which might be related: Since some time around christmas, my home server does no longer wake up (wake on lan) after suspend. I cannot exactly pinpoint after which Tumbleweed-update this happened, as I restart the server seldom.

Everything is configured right according to BIOS and ethtool, and wol has been working for months before.

It is not the kernel (downgrade to standard 13.2 kernel did not work), and switching from wicked to NetworkManager didn’t help, too.

Maybe there has been some change concerning the network setup when suspending/resuming recently?

So after the latest updates (on 13.2), even my touchscreen device is not detected after wake from sleep.
I’ll try asking around in another section of the forums…