[Maverick] Workspace layout is 1x9 instead of 3x3

Bug #642746 reported by Dave Gilbert
68
This bug affects 12 people
Affects Status Importance Assigned to Milestone
libwnck (Ubuntu)
Fix Released
Undecided
Didier Roche-Tolomelli

Bug Description

This seems to have happened in the last day; so I'm guessing the upgrade to 2.30.3-1ubuntu1

I normally have a 3x3 workspace layout (on metacity) and as of today it's showing as 1x9.

Changing the number of rows in workspace switchers preferences isn't making any difference.

Dave

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libwnck22 1:2.30.4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
CheckboxSubmission: f2d10bd9f943a85b486a282e7840a570
CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
Date: Sun Sep 19 12:41:38 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: libwnck

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

2 clarifications:
  1) This is happening on both of my machines, so it's not just a weird config on one (although they have similar setup)
  2) It's fine in compiz.

Dave

Revision history for this message
Daniel Hollocher (chogydan) wrote :

I've had this issue longer, at least a week. T-T I will check if compiz fixes it

Revision history for this message
Daniel Hollocher (chogydan) wrote :

it _sorta_ fixes it with compiz. It doesn't take up more space on the task bar like it used to. so if I want a bunch of spaces, it isn't workable.

Changed in libwnck (Ubuntu):
status: New → Confirmed
tags: removed: amd64
Revision history for this message
Yumi (tempreg) wrote :

I am troubled by this bug too. Please see discussion on http://ubuntuforums.org/showthread.php?t=1575087&page=1

tags: added: regression-potential
Revision history for this message
Bob Filipiak (bfilipiak) wrote :

I have noticed this one too.

I use both karmic and Lucid in addition to testing Maverick.

I have a 32 pixel wide "frame" around the edges of my monitor; to stash all of the launchers, etc. In both Karmic and Lucid, a workplace switcher placed in a vertical panel orients itself vertically (i.e. stacked on above the other) as a single row.

After a fresh install of Maverick into its own partition, the workplace switcher was located in the bottom panel. As soon as I moved it to the left side; things got strange. Instead of being vertically stacked, the switcher screens were horizontally stacked.

All I can say is - something broke!

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Something very strange: sometimes Maverick locks up for me. I turn off the machine, reboot, log in, and then my workspace switcher is back to normal. Then after the next lockup, I have to reboot again, and then it's broken again.

This smells of nondeterminism: something like a garbage pointer, array overrun, or race condition.

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Personally I suspect there may be a wider problem with reading configuration. I see other slightly similar things happening (in Lucid as well):
 * Sometimes after a reboot my CPU frequency management is delegated to the Performance governor instead of the Ondemand governor that I would normally get. However, changing the setting back manually fixes it.
 * Sometimes (aspects of) my desktop theme settings just seem to be forgotten. However, loading up the Appearance preferences is often enough to bring them back to normal.

Revision history for this message
Данило Шеган (danilo) wrote :

The option that seems broken is a combination of "Visual Effects: None" (using metacity, I guess) and using more than one row of workspaces.

I've tried recompiling gnome-panel package without 16_compiz_workspace_switcher.patch and that didn't help (I've also tried compiling without the wnck crasher fixes in patches 90* and 91*, but no luck). So, it might be an upstream problem though it'd be nice if someone can confirm.

I am not seeing any other problems with regards to configuration saving.

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

FTR, I have not noticed any problems with configuration saving either. Only with configuration reading, as in my previous comment, and only occasionally.

Changed in libwnck (Ubuntu):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :
Changed in libwnck (Ubuntu):
assignee: Canonical Desktop Team (canonical-desktop-team) → Didier Roche (didrocks)
Changed in libwnck (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libwnck - 1:2.30.4-0ubuntu2

---------------
libwnck (1:2.30.4-0ubuntu2) maverick; urgency=low

  * debian/patches/91_git_fix_multi_row_pagers.patch:
    - backport fix to get back multi workspace row support in metacity and
      mutter (LP: #642746)
 -- Didier Roche <email address hidden> Thu, 23 Sep 2010 13:55:49 +0200

Changed in libwnck (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Andrew Aylett (andrew-aylett) wrote :

I can confirm that the fix works for me.

Thanks, Didier :).

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Looking forward to having it! As it happens I expect to see the author of the patch next week, so that'll be an opportunity to thank him in person.

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Yep works nicely; thank you Didier!

Dave

Revision history for this message
Yumi (tempreg) wrote :

Thanks, working after yesterdays updates of Maverick. Only when panel is on theright the height of the workspace-square is to low when panel is set at 30px. By increasing to 40 and icons are showing.
 Michael

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.