New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 811533 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 23
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

stop spamming to xsession-errors when screensaver is not installed

Reported by jod35...@gmail.com, Feb 12 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36

Steps to reproduce the problem:
1. uninstall screensaver
2. run chromium
3. take a look at the .xsession-errors file

What is the expected behavior?
Same as when networkmanager is not installed. No spamming to log when unneeded software is not present in the system.

What went wrong?
massive spamming to the .xsession-errors file when the screensaver is not installed.

Did this work before? N/A 

Chrome version: 64.0.3282.119  Channel: stable
OS Version: Debain Sid Xfce
Flash Version:
 
Labels: Needs-Triage-M64
Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue!

@Reporter: Could you please share a sample test file/extension which helps us to triage the issue in a better way. Any further inputs may helps us.

Comment 3 by jod35...@gmail.com, Feb 14 2018

After removing xscreensaver, reboot. Run chromium and play some youtube video. Then you have in the .xsession-errors file:

[2016:2053:0214/093009.113375:ERROR:connection_factory_impl.cc(381)] Failed to connect to MCS endpoint with error -106
[2067:2067:0214/093009.193300:ERROR:sandbox_linux.cc(375)] InitializeSandbox() called with multiple threads in process gpu-process.
Gtk-Message: 09:31:53.399: GtkDialog mapped without a transient parent. This is discouraged.
[2016:2054:0214/093312.931906:ERROR:object_proxy.cc(626)] Failed to call method: org.freedesktop.ScreenSaver.Inhibit: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ScreenSaver was not provided by any .service files
[2016:2054:0214/093312.931941:ERROR:power_save_blocker_x11.cc(338)] No response to Inhibit() request!
[2016:2054:0214/093316.037926:ERROR:object_proxy.cc(626)] Failed to call method: org.freedesktop.ScreenSaver.UnInhibit: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ScreenSaver was not provided by any .service files
[2016:2054:0214/093316.037963:ERROR:power_save_blocker_x11.cc(411)] No response to Uninhibit() request!
Project Member

Comment 4 by sheriffbot@chromium.org, Feb 14 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "vamshi.kommuri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
Checked by searching "xscreensaver" in chrome using Ubuntu 14.04 on reported chrome version 64.0.3282.119, but there weren't any results named with that extension.

@Reporter: It would be highly helpful if provided with the URL of the extension. And please clarify on the word "reboot" in comment#3 first line, does that mean rebooting the system?

Thanks!

Comment 6 by jod35...@gmail.com, Feb 23 2018

Of course there is not xscreensaver in the chrome code, just generic org.freedesktop.ScreenSaver. 

After removing your current screen saver, reboot the PC and inspect the .xsession-errors file
Cc: krajshree@chromium.org
jod35fan@ - Please check the issue using latest chrome stable #66.0.3359.181 and please let us know if the issue still persists or not.
The latest chrome builds can be downloaded from the below URL:
https://www.chromium.org/getting-involved/dev-channel

Thanks...!!
Project Member

Comment 8 by sheriffbot@chromium.org, May 24 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
As per comment#7 adding Needs-Feedback label to the issue.

Thanks!
Status: WontFix (was: Unconfirmed)
As there isn't any Feedback from reporter since long time, closing this issue and marking it as Won't Fix.

@Reporter: Requesting you to file/raise a new issue if this happens in latest chrome versions.

Thanks!

Sign in to add a comment