The importance on this ticket is incorrect: it should not be marked
"low". According to https://dev.launchpad.net/BugTriage#importance)
"Low" is defined as "legitimate but that is not scheduled for Canonical
staff to fix in the next 6 months."
This is a MAJOR issue. As W-barath-hotmail noted it can cause some
extremely serious side effects for anyone who relies on power
management. As such, this ticket should have an importance of "High"
("we believe we will work on in the next six months"). To ignore it for
six or more months would be to deliberately cause serious user damage.
Also, this bug is difficult for users to track down. It's not like
problematic tabs flash red or something, so each user has to figure out
on their own that not only is Chrome the source of the problem, but a
specific tab within Chrome. As a result, the number of users affected by
this bug is undoubtedly much higher than what's reflected on this page,
as many affected users just aren't able to track the problem to this
page.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs are open
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
