[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
Why is it still "Low Importance"?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs are open
Status in gnome-session package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy gnome-session-bin
gnome-session-bin:
Installed: 3.18.1.2-1ubuntu1.16.04.1
Candidate: 3.18.1.2-1ubuntu1.16.04.1
Version table:
*** 3.18.1.2-1ubuntu1.16.04.1 500
500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.18.1.2-1ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
I'm using gnome-session-flashback
What happens:
The screen doesn't lock when having certain pages in Chrome tabs
Expected:
The screen should lock after the configured timeout in settings.
I've been having this issue sice before 14.04, which I recently
upgraded (fresh install) to 16.04.
After fresh install, the screen would turn down and lock the computer
after 10 minutes (or whatever time I setup). At one point it stopped
working. The screen never shuts down unless I manually lock the
session with CTRL-ALT-L.
I've followed the steps in
https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure
The culprit seems to be that Chrome issues some suspend inhibitions
through dbus when doing certain operations. Many people find this
problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
pretty sure that Chrome is doing something else of what i've found
out.
1) Gnome screen saver works correctly. I can trigger it manually with:
$ gnome-screensaver-command -a
2) Gnome screen saver never receives the "session idle" status
callback.
3) When Chrome is not running, I can manually inhibit the idle status:
$ gnome-session-inhibit --app-id test --reason "manual idle inhibit"
--inhibit-only --inhibit idle:suspend
Inhibiting until Ctrl+C is pressed...
4) I can query the inhibitors:
$ dbus-send --print-reply --dest=org.gnome.SessionManager
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103
reply_serial=2
array [
object path "/org/gnome/SessionManager/Inhibitor1686"
]
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetAppId
('test',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetReason
('manual idle inhibit',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetFlags
(uint32 12,)
12=4(suspend) + 8(idle)
5) When testing, I can inhibit for 70 seconds, idle timeout being 60
(1 minute). After these 70 seconds pass, the screen locks.
6) Regarding Chrome, this is the information I get when querying the
inhibitor:
GetAppId: ('/usr/bin/google-chrome-stable',)
GetReason: ('Uploading data to 10.200.0.163',)
GetFlags: (uint32 4,)
The flags just inhibits suspend, not locking or entering powersaving
mode.
This inhibitor seems to stay for 10-15 seconds, then goes away for
another 30-60 seconds. The screen NEVER locks when this tab is open.
No matter the inhibitor is present or not.
I'm not sure where to go on. If it's a Chrome bug it must be using
other mechanisms to prevent the idle timeout. Any ideas on what to
look for?
Julian.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash
Just got the same problem in Ubuntu 16.04.3 LTS, after updating the system. Killing /usr/bin/unity-scope-loader helped me, thanks to the comment #12! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash Status in GLib: Confirmed Status in bamf package in Ubuntu: In Progress Status in gnome-menus package in Ubuntu: Fix Released Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in gnome-menus source package in Xenial: Fix Released Status in libunity source package in Xenial: Fix Released Bug description: [Impact] I am running 15.10 development version fully up to date, I installed it a few days ago and I have an issue with newly installed applications not appearing in the dash when I search for them, they can be started via console but the icons/launchers of newly installed applications will only appear in the dash after session is restarted. [Test case] 1. Install a new applicaiton (using apt-get or the software center) 2. Make sure the application is listed in the Unity Dash [Possible Regressions] Unity fails to list all the applications, not just the newly installed ones. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Oct 16 08:41:39 2015 InstallationDate: Installed on 2015-10-11 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install)Z To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631475] [NEW] Google Chrome crashed, nouveau 0000:01:00.0: fifo: CACHE_ERROR - ch 5 [chrome[3710]] subc 0 mthd 0060 data beef0201
Public bug reported: My Chrome just crashed, and I found this line in dmesg: nouveau :01:00.0: fifo: CACHE_ERROR - ch 5 [chrome[3710]] subc 0 mthd 0060 data beef0201 Related to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1239182 ? versions: Ubuntu 16.01.01 Kernel 4.4.0-38-generic xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Description changed: My Chrome just crashed, and I found this line in dmesg: nouveau :01:00.0: fifo: CACHE_ERROR - ch 5 [chrome[3710]] subc 0 mthd 0060 data beef0201 Related to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1239182 ? + + versions: + Ubuntu 16.01.01 + Kernel 4.4.0-38-generic + xserver-xorg-video-nouveau 1:1.0.12-1build2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1631475 Title: Google Chrome crashed, nouveau :01:00.0: fifo: CACHE_ERROR - ch 5 [chrome[3710]] subc 0 mthd 0060 data beef0201 Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: My Chrome just crashed, and I found this line in dmesg: nouveau :01:00.0: fifo: CACHE_ERROR - ch 5 [chrome[3710]] subc 0 mthd 0060 data beef0201 Related to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-nouveau/+bug/1239182 ? versions: Ubuntu 16.01.01 Kernel 4.4.0-38-generic xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1631475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 120258] Re: Laptop Battery Time Remaining Outrageously Inaccurate
Does this post show some hint for this bug: http://forum.eeeuser.com/index.php?/topic/81732-battery-measurements- are-wrong-eeepc-900-ubuntu-1004/page__view__findpost__p__710079 ? Quote: This is a problem with the way the battery reports its charging state. The ubuntu applet (and the rest of the system, down to the kernel) expects the charge to be reported in mAh but instead the battery itself reports a percentage. If you look at state and info in /proc/acpi/battery/BAT0/, you'll find that a fully charged battery reports a charge of 100 mAh ... with a (reported) design capacity of 5200 mAh this works out to 1.9 %. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/120258 Title: Laptop Battery Time Remaining Outrageously Inaccurate Status in Gnome Powermanager: Unknown Status in Upower: New Status in “gnome-power-manager” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Ubuntu 7.04 Feisty Fawn Hardware is HP Pavilion DV1000 series (specific DV1588EA) Battery monitor when running on battery reports percentage of battery remaining correctly, but the corresponding remaining time is often fabulously wrong (and can swing between e.g a few minutes to tens of hours in the blink of an eye). /* What I wouldn't give for batteries that can last 14 hours between charges... */ It looks for all the world like the underlying values are being held in storage classes which are too small or where value-wrapping is not being handled quite right... BTW UBUNTU is fantastic; I'm a convert! Keep up the good work! To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/120258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
