Re: GNOME 3.4 Blocker Report
Le 09/03/2012 12:50, Andre Klapper a écrit : This is a list of potential release blockers plus some should-fix tickets according to yesterday's release team meeting. Hey, I'm not sure that's the right medium for that but I would like to point those gtk issues as potential would be nice to address for 3.4, maybe that can motivate some people to help fixing seem ;-) * GTK smooth scrolling not being optimized: https://bugzilla.gnome.org/show_bug.cgi?id=672091 in practice it makes scrolling generate lot of events and redraw and turns smooth scrolling to slow scrolling in some way, not sure it's a blocker but it's something quite some users noticed and which reflects on how responsive the system feels * GTK missing enter events on touch devices The bug has a testcase and a video, seems only the first enter event is generated, that leads to issue in menus (no highlighting) after the first entry for example https://bugzilla.gnome.org/show_bug.cgi?id=672009 Those issues are probably xserver 1.12 specific, but most distro to release with GNOME 3.4 should have that version... Thanks for considering, Sebastien Bacher ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.4 Blocker Report
Le vendredi 09 mars 2012, à 12:50 +0100, Andre Klapper a écrit : === GNOME-SESSION === fail whale extension list looks bad https://bugzilla.gnome.org/show_bug.cgi?id=671693 Needs more information and testing. I don't think it's a blocker, and we're past the freeze to change the UI there. [PATCH] Need signal matching Setenv dbus method so apps in initialization phase can update their env too https://bugzilla.gnome.org/show_bug.cgi?id=662528 Five patches available awaiting review for two months now Patches don't work, as mentioned by Cosimo in a comment. There is discussion on using another approach too. It's highly annoying for technical users so blocker, indeed. gnome-session no longer starts desktop files under /usr/share/gdm/autostart/LoginWindow https://bugzilla.gnome.org/show_bug.cgi?id=663721 Inline patch that needs more work available Not sure why this is a blocker? Certainly a valid bug we should get fixed, though. fail whale triggers too easily https://bugzilla.gnome.org/show_bug.cgi?id=671694 This used to work fine (I think Colin had fixed a similar issue a while ago, but I could be wrong). Did something change on gnome-shell's side, when it's being restarted? Cheers, Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.4 Blocker Report
On Fri, Mar 9, 2012 at 7:53 AM, Vincent Untz vu...@gnome.org wrote: Le vendredi 09 mars 2012, à 12:50 +0100, Andre Klapper a écrit : === GNOME-SESSION === fail whale extension list looks bad https://bugzilla.gnome.org/show_bug.cgi?id=671693 Needs more information and testing. I don't think it's a blocker, and we're past the freeze to change the UI there. I don't really see how the fail whale would be particularly affected by the ui freeze. The current screen looks _really_ bad... fail whale triggers too easily https://bugzilla.gnome.org/show_bug.cgi?id=671694 This used to work fine (I think Colin had fixed a similar issue a while ago, but I could be wrong). Did something change on gnome-shell's side, when it's being restarted? I filed the bug, so I'll investigate. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.4 Blocker Report
Le vendredi 09 mars 2012, à 11:29 -0500, Matthias Clasen a écrit : On Fri, Mar 9, 2012 at 7:53 AM, Vincent Untz vu...@gnome.org wrote: Le vendredi 09 mars 2012, à 12:50 +0100, Andre Klapper a écrit : === GNOME-SESSION === fail whale extension list looks bad https://bugzilla.gnome.org/show_bug.cgi?id=671693 Needs more information and testing. I don't think it's a blocker, and we're past the freeze to change the UI there. I don't really see how the fail whale would be particularly affected by the ui freeze. There might be documentation mentioning it, so that it's not just the horrible death dialog that nobody explains anywhere. I expect people to look for more information about that kind of dialogs either on next login, or thanks to another device while it's on screen. The current screen looks _really_ bad... It didn't look that bad last time I got it (with 3.3.5?). I'll try with latest code of everything. Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.4 Blocker Report
On Fri, Mar 9, 2012 at 11:43 AM, Vincent Untz vu...@gnome.org wrote: The current screen looks _really_ bad... It didn't look that bad last time I got it (with 3.3.5?). I'll try with latest code of everything. http://mclasen.fedorapeople.org/fail-whale-fail.png ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.4 Blocker Report
W dniu 9 marca 2012 19:15 użytkownik Matthias Clasen matthias.cla...@gmail.com napisał: http://mclasen.fedorapeople.org/fail-whale-fail.png Haha, last time I got that I assumed it was an artifact caused by a bug in nouveau. -- Patryk Zawadzki I solve problems. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
