desktop switcher compromises maximus effect

Bug #316461 reported by Michael Fox on 2009-01-12
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Desktop Layout Switcher
New
Undecided
Unassigned
Maximus
Undecided
Unassigned

Bug Description

On an MSI Wind U100 (dual-boot, Ubuntu 8.04.1), I tried Desktop Switcher for the first time a few days ago. Using it caused a thin version of the window border with the window controls (minimize-maximize-close) to appear above all applications. This does not remove the Maximus effect in the menubar, so the option to hide or dismiss the menu is still there where expected using Maximus. It just adds another vertical layer between it and the rest of the application's windows, losing part of the space-saving effect of Maximus.

I have tried using Desktop Switcher to change back to the classic windows, and this results in the persistence of the thin window border, even after uninstalling Maximus. The window border should go back to its usual height at this point, but doesn't. Installing and uninstalling Maximus, changing configurations with Desktop Switcher, and even uninstalling Desktop Switcher have no effect on the window border.

Neil J. Patel (njpatel) wrote :

In Classic mode Maximus will _not_ undecorate the windows, this is because it trys to adhere to the default Ubuntu preferences. However, when you switch back to netbook mode, Maximus should then start to undecorate windows again.

If this isn't the case, it would seem that some gconf options were altered. To force Maximus to undecorate windows, run gconf-editor and navigate to /apps/maximus on the left pane. Then make sure the "undecorate" option is checked (in the right pane).

Changed in netbook-remix:
status: New → Triaged
Michael Fox (mfox-trentu) wrote :

This wasn't the case when I went back to netbook mode; the undecorate option wasn't checked. Checking it resulted in the correct behaviour. (Thanks; I didn't know about gconf-editor.) The question still remains why undecorate wasn't checked, but at least there's a way back.

Paul Larson (pwlars) wrote :

Changing the netbook-remix task to maximus since netbook-remix is no longer a valid target for bugs.

affects: netbook-remix → maximus
Neil J. Patel (njpatel) on 2009-08-26
Changed in maximus:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers