Bug 770184 - "This shouldn't happen!" in "Window manager warning"
Summary: "This shouldn't happen!" in "Window manager warning"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-23 22:56 UTC by Michal Jaegermann
Modified: 2019-07-31 17:48 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-01 06:26:19 UTC
Type: ---


Attachments (Terms of Use)

Description Michal Jaegermann 2011-12-23 22:56:45 UTC
Description of problem:

The following are showing up in ~/.xsession-errors while running a 'gnome-shell' session:

Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!

It is hard to say what is really this "Window manager" or "pager" but I am guessing that these will be some gnome-shell elements.

Version-Release number of selected component (if applicable):
gnome-shell-3.2.1-2.fc16

Additional info:
Maybe this is related to bug 770183? Hard to tell.

Comment 1 Fabian Deutsch 2012-02-20 11:35:02 UTC
This error also appears in my logs, right after the shell-freezes:
      JS LOG: GNOME Shell started at Mon Feb 20 2012 12:31:30 GMT+0100 (CET)
** Message: applet now embedded in the notification area
Fensterverwalter-Warnung:CurrentTime used to choose focus window; focus window may not be correct.
Fensterverwalter-Warnung:Got a request to focus 0x220008c (fabiand@ap) with a timestamp of 0.  This shouldn't happen!


Any hint where this comes from or what to do about it?

Comment 2 Nicolas Berrehouc 2012-12-06 18:14:05 UTC
Avertissement du gestionnaire de fenêtres : CurrentTime used to choose focus window; focus window may not be correct.
Avertissement du gestionnaire de fenêtres : Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!

Same problem. Gnome-Shell crash and back to GDM Login Screen.

Version-Release number of selected component (if applicable):
gnome-shell-3.4.1-6.fc17.x86_64

Comment 3 collura 2013-06-03 06:03:47 UTC
still in .xsession-errors as of 

  gnome-shell-3.6.3.1-1.fc18.x86_64


please update version to fc18


related bugs:

https://bugzilla.gnome.org/show_bug.cgi?id=646328
"However, really, gnome-shell is just wrong here; it shouldn't be focusing the
window with CurrentTime or with the result of get_current_time_roundtrip() at
the time of the timeout, it should be focusing it with the time of the leave
event that caused the timeout to be queued. (There isn't actually a race
condition in the current code, because MessageTray only restores focus to the
previously-focused window if focus is still on the stage at the time the
timeout handler runs, so if you leave and then very quickly click another
window, you're ok.)"

https://bugzilla.gnome.org/show_bug.cgi?id=678373
https://bugzilla.redhat.com/show_bug.cgi?id=770184

https://bugzilla.gnome.org/show_bug.cgi?id=624563
https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/985660
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652013

Comment 4 Fedora End Of Life 2013-07-04 01:42:24 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Larry O'Leary 2013-07-31 03:56:47 UTC
I am seeing this in F19 as well so if someone can bump the version.


Jul 30 14:29:23 home03 /usr/bin/dbus-launch[844]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Jul 30 14:29:23 home03 /usr/bin/dbus-launch[844]: Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!

Comment 6 Fedora End Of Life 2013-08-01 06:26:26 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 7 Pedro Francisco 2013-08-01 09:58:07 UTC
Comment 5 (Larry O'Leary): since no-one bumped it my guess is you should open a new bug report and refer on the new bug it is a continuation of this one which was closed due to being tagged to a EOL'ed Fedora version.

Comment 8 Pablo Iranzo Gómez 2014-03-07 21:27:15 UTC
This happens to me on F20, 

Can't we just bump version to F20 and reopen or should a new one be filled?

gnome-shell-3.10.4-1.fc20.x86_64


Note You need to log in before you can comment on or make changes to this bug.