FS#39036 - [gnome-shell] last update (3.10.4-1) breaks shell layout

Attached to Project: Arch Linux
Opened by William Di Luigi (wil93) - Monday, 24 February 2014, 21:50 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 02 April 2014, 20:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Ionut Biru (wonder)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 9
Private No

Details

Description:

The last gnome-shell update (3.10.4-1) breaks the shell layout: I can't even reach the button to reboot/shutdown because all the icons are stretched down and partially invisible.

Solution: I downgraded to the last version I had in the cache (3.10.2.1-4).

I'm quite sure gnome-shell was the problem, since by downgrading I solved the issue on two different PCs.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 02 April 2014, 20:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  Should be fixed in 3.12. Not adding this patch to 3.10 anymore.
Comment by Doug Newgard (Scimmia) - Monday, 24 February 2014, 23:08 GMT
Need more information. Theme, video hardware/driver info, etc.
Comment by William Di Luigi (wil93) - Monday, 24 February 2014, 23:12 GMT
I didn't customize the theme, it was standard gnome-shell on both PCs.

Video drivers: xf86-video-intel 2.99.910-1

Hardware: Intel HD Graphics 4000, I don't exactly remember it for the other PC, but I'm sure it has lower specs.
Comment by Jan de Groot (JGC) - Thursday, 27 February 2014, 19:59 GMT
I could reproduce this once today, but after using alt+f2 -> r, the shell works fine again. Guess this is related to the high dpi changes that were added to 3.10.4.
Comment by William Di Luigi (wil93) - Thursday, 27 February 2014, 21:12 GMT
Yes. I just upgraded again and rebooted: I can confirm that restarting gnome-shell with Alt+F2 "r" solves the issue.
Comment by Skyler Hawthorne (dead10ck) - Saturday, 08 March 2014, 03:53 GMT
Confirming this bug on my laptop.

xf86-video-intel 2.99.910-1

Not sure if it's relevant, but I checked my journal and noticed warnings about clutter trying to allocate negative window sizes:

entTime used to choose focus window; focus window may not be correct.
WARNING **: ./clutter-actor.c:9814: Actor 'StIMText' tried to allocate a size of -44.00 x 16.00
WARNING **: ./clutter-actor.c:9814: Actor 'StIMText' tried to allocate a size of -44.00 x 16.00
WARNING **: zeitgeist-datahub.vala:209: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: inte
: Name owner ':1.61' vanished
ebug: Name owner ':1.61' vanished
WARNING **: ./clutter-actor.c:9814: Actor 'StIMText' tried to allocate a size of -44.00 x 16.00
WARNING **: ./clutter-actor.c:9814: Actor 'StIMText' tried to allocate a size of -44.00 x 16.00
WARNING **: ./clutter-actor.c:9814: Actor 'StIMText' tried to allocate a size of -44.00 x 16.00
WARNING **: ./clutter-actor.c:9814: Actor 'StIMText' tried to allocate a size of -22.00 x 16.00
Comment by Boyan Ding (jdbrown) - Sunday, 09 March 2014, 01:10 GMT
Also confirming this bug on my laptop.

Strange thing is that I upgraded gnome-shell to 3.10.4-1 about two weeks ago but this bug only appeared after another update lately. Many people are suffering from the same issue. See https://bbs.archlinux.org/viewtopic.php?id=178079 and https://bbs.archlinux.org/viewtopic.php?id=178088.

Another fact worth noticing is that scaling factor hack doesn't fix for me (and some others).
Comment by mjb (mjb) - Monday, 10 March 2014, 07:50 GMT
Another fact worth mentioning: I have the same problem on an ATI Radeon chipset.
Comment by Boyan Ding (jdbrown) - Thursday, 13 March 2014, 13:31 GMT
It is said that this has been fixed in git: https://git.gnome.org/browse/gnome-shell/commit/?id=29addc499ca0f8dc5bf9cf6d18eaaa01a5c2b985 and have been in 3.10 branch.
Comment by Skyler Hawthorne (dead10ck) - Thursday, 13 March 2014, 15:31 GMT
Any idea when that's going to be pushed through stable?
Comment by Boyan Ding (jdbrown) - Friday, 14 March 2014, 08:05 GMT
I don't know when it's going stable. I have built a package with this patch and it works for me. Maybe you can build one yourself or wait until the next version arrives.

Loading...