After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 630642 - Workspace switcher applet unable to initially display in vertical mode
Workspace switcher applet unable to initially display in vertical mode
Status: RESOLVED DUPLICATE of bug 630229
Product: gnome-panel
Classification: Other
Component: workspace switcher
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-26 17:06 UTC by Samuel Hym
Modified: 2010-09-27 16:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Samuel Hym 2010-09-26 17:06:20 UTC 
Since my last upgrade of gnome-panel (debian package version 2.30.2-2, though I do not remember the version before the upgrade, even whether it was < 2.30), the workspace switcher applet refuses to display anything when it is started in a vertical panel (adding it 10 times shows a bit of a difference, so I imagine it uses a height of a pixel or two). Switching the panel to the horizontal mode brings the display. Switching back to the vertical mode then works.

(The vertical mode is properly detected, since the preferences rightly states "how many columns" instead of "how many rows" should the applet display, even if that function is currently broken also, but this looks already reported as bug #480710).

[Also reported in Debian as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598122 with the full list of packages.]

Best regards,
Samuel Hym
Comment 1 Joachim Breitner 2010-09-26 17:32:11 UTC 
This issue is most likely cause by the patch fixing #472773
Comment 2 Josselin Mouette 2010-09-27 16:08:03 UTC 
Actually this is caused by the unitialized value in libwnck, which is fixed in 2.30.5.
Comment 3 Vincent Untz 2010-09-27 16:24:11 UTC 
(In reply to comment #2)
> Actually this is caused by the unitialized value in libwnck, which is fixed in
> 2.30.5.

Thanks, I was wondering about it.

*** This bug has been marked as a duplicate of bug 630229 ***