wingpanel steals focus & rises up to 100% of cpu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Wingpanel |
New
|
Undecided
|
Unassigned |
Bug Description
Everything has been working perfect with Freya. After reinstall to Loki beta2:
I noticed that after while (1-2 minutes) wingpanel start steals every X seconds focus. For example I write "letter" and wingpanel makes it "etet" because of stolen focus.
This behaviour also takes approx. 10-90% of one CPU (observed with htop).
$ killall wingpanel - helps for 1-2 minutes, until it happends again.
Not sure exactly how to reproduce it, but for example when time switches 00:05 -> 00:06, then it steal focus.. Nothing is written in log when that happends.
wingpanel log:
$ killall wingpanel && wingpanel
[INFO 00:01:13.251270] Application.
[INFO 00:01:13.251334] Application.
[FATAL 00:01:13.374333] Manager.vala:55: GDBus.Error:
[FATAL 00:01:13.376186] wingpanel_
[FATAL 00:01:13.376877] wingpanel_
[FATAL 00:01:13.508991] [GLib-GIO] g_file_get_child: assertion 'G_IS_FILE (file)' failed
[FATAL 00:01:13.509040] [GLib-GIO] g_file_
[FATAL 00:01:13.509061] [GLib-GIO] g_file_get_child: assertion 'G_IS_FILE (file)' failed
[FATAL 00:01:13.509092] [GLib-GIO] g_file_
[FATAL 00:01:13.509124] gee_abstract_
[WARNING 00:01:13.509153] Theme.vala:508: Currently selected gtk+ theme 'elementary' does not provide a dock theme, fallback to the built-in defaults!
[FATAL 00:01:13.621630] [GLib] g_hash_
[22:01:14.016052 Warning] [DesktopFileInfo] Key file does not have key 'Type' in group 'Desktop Entry'
[22:01:14.044275 Warning] [DesktopFileInfo] Unable to get exec for Other
** (process:12604): CRITICAL **: string_contains: assertion 'self != NULL' failed
** (process:12604): CRITICAL **: string_contains: assertion 'self != NULL' failed
[22:01:31.420061 GLib-GObject-
Also I run two monitor setup (2x 1920x1080, VGA1 & DP1). Wingpanel is placed on second one (DP1, set as primary), which is unrelated to issue.
Similar behaviour here. My laptop fan is going mad.
Laptop on a docking station, secondary monitor set to primary, wingpanel lives on it when docked.
Nvidia 340 graphics driver.
Every time I walk away from my pc and come back, wingpanel is unresponsive and consuming 100% of cpu. Killing wingpanel causes it to relaunch and cpu usage goes down, but only temporarily.
Seems to lock up when the displays go to sleep, but I can't state that it never happens if kept awake for a fact.
I am not experiencing wingpanel stealing focus though. Before I determined the issue was wingpanel I would work normally, although my pc was slow, and only notice it when I tried to adjust the volume and found wingpanel unresponsive.