On 28/02/14 10:05, Julian Gilbey wrote: > On Fri, Feb 28, 2014 at 08:08:44AM +0000, Julian Gilbey wrote: >> Package: aisleriot >> Version: 1:3.10.1-1 >> >> I'm following testing, and within the last few days, aisleriot has >> begun a new unpleasant behaviour. When playing freecell and >> attempting to drag a card or number of cards from one stack (is that >> the right word?) to another, the card(s) vanish(es) until they are >> placed, which is very disconcerting. Here is the content of the last >> 5 days' worth of aptitude's log, in case something in a dependency has >> caused this changed behaviour. > > I've just upgraded another machine, but this time I did it one package > at a time (or as close to it as possible) until I hit the bug. Here's > the bunch of packages which actually caused the problem: > > Aptitude 0.6.8.4: log report > Fri, Feb 28 2014 09:01:16 +0000 > > IMPORTANT: this log only lists intended actions; actions which fail due to > dpkg problems may not be completed. > > Will install 10 packages, and remove 0 packages. > 3,210 kB of disk space will be used > =============================================================================== > [INSTALL, DEPENDENCIES] libwayland-cursor0:amd64 > [INSTALL, DEPENDENCIES] libwayland-dev:amd64 > [INSTALL, DEPENDENCIES] libxkbcommon-dev:amd64 > [INSTALL, DEPENDENCIES] libxkbcommon0:amd64 > [UPGRADE] gir1.2-gtk-3.0:amd64 3.8.6-1 -> 3.10.7-1 > [UPGRADE] libgail-3-0:amd64 3.8.6-1 -> 3.10.7-1 > [UPGRADE] libgtk-3-0:amd64 3.8.6-1 -> 3.10.7-1 > [UPGRADE] libgtk-3-bin:amd64 3.8.6-1 -> 3.10.7-1 > [UPGRADE] libgtk-3-common:amd64 3.8.6-1 -> 3.10.7-1 > [UPGRADE] libgtk-3-dev:amd64 3.8.6-1 -> 3.10.7-1 > =============================================================================== > > So it's the upgrade from 3.8.6 -> 3.10.7 of gtk3 which did it.
Yes, that's what I suspected. Upstream has added a workaround for this, which I am uploading to unstable as we speak. The upstream bug report is: https://bugzilla.gnome.org/show_bug.cgi?id=702951 Regards, Emilio -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
