Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#38135 - Gnome Control Center overly wide

Attached to Project: Arch Linux
Opened by Britt Yazel (brittyazel) - Saturday, 14 December 2013, 18:57 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 19 January 2014, 20:05 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

As many of you know about the Gnome Control Center found in Gnome 3.0-3.10, the size of the window is unchangeable. Unfortunately, as of the past month or so, the Control Center is become 300-400 pixels wider than it used to be, making each of the menu's overly stretched and awkward looking. In the middle section of icons, there used to be two rows. Now there is just a single (long) row, perhaps that is what is pushing the window to be far wider than it should be.

Additional info:
Gnome-Control-Center 3.10.2-1
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Sunday, 19 January 2014, 20:05 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#37937 
Comment by Britt Yazel (brittyazel) - Saturday, 14 December 2013, 19:09 GMT
Here is the screen shot of the wide Gnome Control Center. It looks as if the icons in the "hardware" section are not wrapping as they should be, and are forcing the window to be extra wide to fit.
   Screenshot from 2013-12-14 11... (83.3 KiB)
Comment by Jelle van der Waa (jelly) - Monday, 30 December 2013, 20:09 GMT
Please report it upstream
Comment by Britt Yazel (brittyazel) - Monday, 30 December 2013, 22:28 GMT
I think it might have already been fixed upstream. I am not sure, but someone on a similar bug report to this one reported that there was a fix already in place for it.

Loading...