[Bug 983673] Re: me-tv-client doesn't interrupt screensaver
Good point. According to comment 40 in https://trac.videolan.org/vlc/ticket/4739 at least for Gnome org.freedesktop.ScreenSaver.Inhibit is a proxy org.gnome.SessionManager.Inhibit. I guess it should be similar for KDE. What about Unity? ** Bug watch added: VLC Trac #4739 http://trac.videolan.org/vlc/ticket/4739 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/983673 Title: me-tv-client doesn't interrupt screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/me-tv/+bug/983673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 983673] Re: me-tv-client doesn't interrupt screensaver
I guess for Gnome 3 this should be relatively easy to implement via org.gnome.SessionManager-Inhibit. For Unity there is surely something in com.canonical.Unity.*. that can be revealed via d-feet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/983673 Title: me-tv-client doesn't interrupt screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/me-tv/+bug/983673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475559] Re: thinkpad x30 suspend/resume problems (was OK under Jaunty)
Just in case someone is interested. The bug is related to KMS and is still present in all recent Ubuntu versions (actually, in all recent kernels too, as it affects i915 module) The good thing is that people are trying to fix it upstream: https://bugs.freedesktop.org/show_bug.cgi?id=49838 ** Bug watch added: freedesktop.org Bugzilla #49838 https://bugs.freedesktop.org/show_bug.cgi?id=49838 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/475559 Title: thinkpad x30 suspend/resume problems (was OK under Jaunty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/475559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999462] Re: ExpressCard34 slot not hotplugable after boot
I confirm that rduke15's workaround also solves the problem on my Thinkpad Z61m running Ubuntu 12.04. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/999462 Title: ExpressCard34 slot not hotplugable after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/999462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 641816] Re: iscsi mounts not restarted after suspend/resume
This bug is still present in Ubuntu 11.04 but in a slightly different form. After resume the open-iscsi service is always stopped even though it was running before the suspend. After resume I have $sudo service open-iscsi status * iscsid is not running If you start it by hand and then login to your storage again $sudo service open-iscsi start * Starting iSCSI initiator service iscsid [ OK ] * Setting up iSCSI targets [ OK ] $sudo iscsiadm -m node --targetname iqn-2011-09.com.mydomain:storage.seagate --portal 192.168.4.43:3260 --login Logging in to [iface: default, target: iqn-2011-09.com.mydomain:storage.seagate, portal: 192.168.4.43,3260] Login to [iface: default, target: iqn-2011-09.com.mydomain:storage.seagate, portal: 192.168.4.43,3260]: successful Everything works again. I believe that Ubuntu stops the service before a suspend but forget to start it after resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/641816 Title: iscsi mounts not restarted after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/641816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 641816] Re: iscsi mounts not restarted after suspend/resume
Oops, forgot to say that you also need node.session.auth.authmethod = CHAP in /etc/iscsi/iscsid.conf. Sorry for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/641816 Title: iscsi mounts not restarted after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/641816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 641816] Re: iscsi mounts not restarted after suspend/resume
Here is a very ugly workaround for the problem
$sudo nano /etc/iscsi/iscsid.conf
node.startup = automatic
node.session.auth.username = mylogin
node.session.auth.password = mypass
$sudo nano /etc/pm/sleep.d/20_iscsi
PATH=/sbin:/usr/sbin:/bin:/usr/bin
case ${1} in
hibernate|suspend)
;;
thaw|resume)
/bin/sleep 6 /etc/init.d/open-iscsi start
;;
esac
$sudo chmod +x /etc/pm/sleep.d/20_iscsi
This way after resume the open-iscsi service is started. Because of
node.startup = automatic it also mounts all known nodes. A very ugly
hack indeed, but for a home NAS it works good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/641816
Title:
iscsi mounts not restarted after suspend/resume
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/641816/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
