Ubuntu 13 Maximized Window Problem

Asked by tecknomage

REF: Ubuntu 13.04 running GNOME Fallback (aka GNOME Classic) enviroment

After upgrade foung Ubuntu 13 has a problem with maximized windows in the GNOME enviroment.

Again, with ANY window *already* maximized, the [Close][Minimized][Maximize/Unmaximize] buttons at window corners do NOT work.

In GNOME Fallback I can use right-click the Task-Bar and use the functions in the context menu.

By the way, reporting a bug is still MUCH TO COMPLEX. Selecting [Report a Bug] should take users DIRECTLY to the applicable form, NOT a overly long document.

Question information

Language:
English Edit question
Status:
Needs information
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
N1ck 7h0m4d4k15 (nicktux) said :
#1

Have you tried to re-install gnome-panel ?

    sudo apt-get install --reinstall gnome-panel

Regards
 NikTh

Revision history for this message
tecknomage (tecknode) said :
#2

Thanks NikTh, that solved my question.

Revision history for this message
tecknomage (tecknode) said :
#3

Spoke too soon.

Problem still exists after sudo.

Revision history for this message
N1ck 7h0m4d4k15 (nicktux) said :
#4

After sudo ?
Sorry but I don't understand this. What you mean "after sudo" ?

Regards
 NikTh

Revision history for this message
tecknomage (tecknode) said :
#5

NikTh,

Your "sudo" suggestion of 2013-04-27.

Note links to 2 Bug Reports.

Revision history for this message
glennric (glennric) said :
#6

This affects me as well. If an application starts maximized then the title bar of the application is completely unresponsive. None of the buttons in the window corners work, and double clicking on the title bar to unmaximize the application also does nothing. Furthermore, if an application is open and the title bar of that applicaiton is behind that of the maximized window, then the buttons for that window "will" respond. This bug used to happen with the gtk-window-decorator, but had been fixed. It seems to have resurfaced. I have no clue what the old bug number was.

Revision history for this message
glennric (glennric) said :
#7

I believe this bug is a duplicate of bug #1158267.

Can you help with this problem?

Provide an answer of your own, or ask tecknomage for more information if necessary.

To post a message you must log in.