GNOME Bugzilla – Bug 138661
links2 (aka glinks) windows are not decorated
Last modified: 2004-12-30 18:08:23 UTC
Description of Problem: The glinks web browser (links2 from http://atrey.karlin.mff.cuni.cz/~clock/twibright/links/) . New windows are not decorated (they have no window borders or title bar). Resizing the window fixes the problem. Steps to reproduce the problem: 1. Open a new links2 window in graphical X mode 2. Be running Metacity with default theme Opening a new window in the running instance also has the same problem How often does this happen? Often, but not every time.
Could you please do the following: Get a glinks window open so that it is not decorated. Then, from a terminal, type "xprop" then click on the glinks window. Attach the output of the command to this bug. Thanks.
xprop results: _NET_WM_ICON_GEOMETRY(CARDINAL) = 554, 745, 181, 22 _NET_WM_DESKTOP(CARDINAL) = 0 _NET_WM_STATE(ATOM) = WM_STATE(WM_STATE): window state: Normal icon window: 0x0 WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW WM_ICON_NAME(STRING) = "Links - Google" WM_NAME(STRING) = "Links - Google" WM_CLASS(STRING) = "Links - Google", "Links - Google" WM_HINTS(WM_HINTS): Client accepts input or input focus: True bitmap id # to use for icon: 0x2a00009
Need a log file to see why it ended up without decorations
I'm sorry, how would I do that? Can metacity be started in debugging mode? I don't see this as a command-line option. The system is Gentoo Linux on x86 with 2.6.3
2.6.3 I meant Metacity, not the kernel, of course
To get a log file, run METACITY_DEBUG=1 METACITY_USE_LOGFILE=1 metacity --replace That command will display the file that it logs things to; you can then reproduce this bug and send us a zipped version of that log file. It may also be helpful if you could try out a newer version of Metacity as well. 2.6.3 is getting somewhat old and there have been numerous changes and fixes in the meantime.
Eugene: Does this problem still occur for you? Can you get a logfile for us? Also, it looks like I left out METACITY_VERBOSE=1 on that command line.
Looks like this is the same bug as 133584, so I'll mark it as such.
*** This bug has been marked as a duplicate of 133584 ***