Announcement

Collapse
No announcement yet.

Suspend / resume problems

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Suspend / resume problems

    On resume from suspend (to memory) two problems occur at my desktop machine
    1) the wired network is usually (but not always) not connected properly. It has IP address, but it has no default gateway. I have to manually disconnect the network and reconnect it. It uses DHCP through the network manager.


    Route shows something like this:

    Code:
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
    Aftehr the reconnect the line gets added
    Code:
    default         192.168.1.1    0.0.0.0         UG    100    0        0 eth0
    and the network works again


    I try to fix it by adding a script like this to /etc/pm/sleep.d, but it does'nt seem to get called.
    Code:
    #!/bin/sh
    ase "${1}" in
            resume|thaw)
                nmcli d disconnect eth0
                nmcli d connect eth0
                             ;;
    esac
    exit 0
    running this script manually with resume works fine and restores the network as it should.

    2) kwin sometimes shows a distorted picture after unlocking the screen. The unlock screen looks fine, but the screen looks like a patch work of the original desktop. running kwin_x11 --replace must be run to restore the proper desktop.

    Any thoughts on how to fix either problem?

    On the previous version of Kubuntu it all worked fine.

    #2
    I've also seen the distorted screen you report.
    On my laptop it only happens with newer nVidia drivers, no problem with nVidia 304.

    About the network, make sure in the network configuration you've enabled All users can connect (or such).

    Comment


      #3
      Thanx I'll try the older drivers and see what happens

      The user rights are not the issue, as I can connect / disconnect manually through the networkmanager gui. That works fine.

      Comment


        #4
        I'm not talking about user rights, thing is that it needs 'your' rights to reconnect and they are not available during the resume.
        Allowing 'all' users to connect alleviates this issue.

        Not saying this is your issue but it is 100% reproducible on WIFI.

        Comment


          #5
          The setting in the networks to allow all users to connect is enabled, as well as automatically connect to the network for the wired connection.
          the output of nmcli premissions as a user is:

          > nmcli g permissions
          PERMISSION VALUE
          org.freedesktop.NetworkManager.enable-disable-network yes
          org.freedesktop.NetworkManager.enable-disable-wifi yes
          org.freedesktop.NetworkManager.enable-disable-wwan yes
          org.freedesktop.NetworkManager.enable-disable-wimax yes
          org.freedesktop.NetworkManager.sleep-wake no
          org.freedesktop.NetworkManager.network-control yes
          org.freedesktop.NetworkManager.wifi.share.protecte d yes
          org.freedesktop.NetworkManager.wifi.share.open yes
          org.freedesktop.NetworkManager.settings.modify.sys tem yes
          org.freedesktop.NetworkManager.settings.modify.own yes
          org.freedesktop.NetworkManager.settings.modify.hos tname auth

          Comment


            #6
            Confirm the erratic wireless connection on waking up from standby. The list of wireless stations is not shown anymore. The older nvidia 340 seems to clear the screen tearing and corruption of the latest driver from standby. One more thing, I cannot wake up the computer using my wireless Logitech keyboard. Work fine in my dual boot windows 7 though.

            Comment

            Working...
            X