Need approval for bug #696366
Hey, that bug is really bad as it may make people to lose their documents. https://bugzilla.gnome.org/show_bug.cgi?id=696366 Regards -- Ignacio Casal Quinteiro ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Orca: Code Freeze Break Request
Joanmarie Diggs wrote: Hey Release Team. I'm afraid a regression snuck into Orca. The impact is that when a braille user is using Orca's Flat Review feature and encounters a check box or radio button, Orca spits up. The bug, along with its three-line patch which was tested by the reporter: https://bugzilla.gnome.org/show_bug.cgi?id=696334 Ok; 1 of 2 for release team. Fred ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break request: Remove the blur and desaturation from the lock screen
On Thu, 2013-03-21 at 15:53 -0400, Jasper St. Pierre wrote: Requesting a freeze break for https://bugzilla.gnome.org/show_bug.cgi?id=696322 Performance issue and simple patch; r-t approval 1 of 2. gnome-user-docs/gnome-help/C/figures/shell-lock.png likely needs an update. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Need approval for bug #696366
Ignacio Casal Quinteiro wrote: Hey, that bug is really bad as it may make people to lose their documents. https://bugzilla.gnome.org/show_bug.cgi?id=696366 Okay; would be bad; 1 of 2 for release team. Fred ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Orca: Code Freeze Break Request
On Fri, 2013-03-22 at 10:16 +0100, Frederic Peters wrote: Joanmarie Diggs wrote: Hey Release Team. I'm afraid a regression snuck into Orca. The impact is that when a braille user is using Orca's Flat Review feature and encounters a check box or radio button, Orca spits up. The bug, along with its three-line patch which was tested by the reporter: https://bugzilla.gnome.org/show_bug.cgi?id=696334 Ok; 1 of 2 for release team. Fred r-t approval 2 of 2. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break request: Remove the blur and desaturation from the lock screen
Jasper St. Pierre wrote: halfline took some screenshots in the old bug: http://people.gnome.org/~halfline/blur-more-saturated.png http://people.gnome.org/~halfline/noblur-fully-saturated.png Thanks; second approval, just like Andre said it would be a nice polish to have the screenshot in the documentation updated to match. Fred ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: gnome-shell hard code freeze break request
On Thu, Mar 21, 2013 at 2:01 PM, Colin Walters walt...@verbum.org wrote: https://bugzilla.gnome.org/show_bug.cgi?id=691987 I'd characterize the risk of this change as low/medium. I tested the change of course (in gnome-ostree FWIW) but it's a nontrivial change to a nontrivial part of the code. The benefit is that we're less likely to leave the user's session in an unlocked state. I have been pushing to get this merged before, but I think we should leave this to 3.8.1 at this point. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Need approval for bug #696366
On Fri, Mar 22, 2013 at 4:01 AM, Ignacio Casal Quinteiro nacho.r...@gmail.com wrote: Hey, that bug is really bad as it may make people to lose their documents. https://bugzilla.gnome.org/show_bug.cgi?id=696366 I've commented on the patch. Not sure about one aspect of it. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Need approval for bug #696366
Removed the ifdef for osx. On Fri, Mar 22, 2013 at 10:49 AM, Matthias Clasen matthias.cla...@gmail.com wrote: On Fri, Mar 22, 2013 at 4:01 AM, Ignacio Casal Quinteiro nacho.r...@gmail.com wrote: Hey, that bug is really bad as it may make people to lose their documents. https://bugzilla.gnome.org/show_bug.cgi?id=696366 I've commented on the patch. Not sure about one aspect of it. -- Ignacio Casal Quinteiro ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: gnome-shell hard code freeze break request
On Fri, 2013-03-22 at 05:44 -0400, Matthias Clasen wrote: On Thu, Mar 21, 2013 at 2:01 PM, Colin Walters walt...@verbum.org wrote: https://bugzilla.gnome.org/show_bug.cgi?id=691987 I'd characterize the risk of this change as low/medium. I tested the change of course (in gnome-ostree FWIW) but it's a nontrivial change to a nontrivial part of the code. The benefit is that we're less likely to leave the user's session in an unlocked state. I have been pushing to get this merged before, but I think we should leave this to 3.8.1 at this point. Ok. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Wayland announcement
Think we should create an announcement for Wayland. Focus on what we plan to deliver and when. What we suggest distributions to do. Give a hint that we really like systemd, but still optional, etc. At same time, small item about non-Linux impact. Obviously it would've been better if this email contained a proposal, but oh well, it does not :P Any takers? -- Regards, Olav ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
gst-plugins-base 1.0.6
ChangeLog = 2013-03-22 Tim-Philipp Müller t...@centricular.net * configure.ac: releasing 1.0.6 2013-02-14 01:35:45 +0100 Arnaud Vrac av...@freebox.fr * gst/subparse/gstsubparse.c: * gst/subparse/gstsubparse.h: subparse: fix off by one offset calculation Do not use the buffer start offset when it is invalid, otherwise a discontinuity is detected on the next buffer, and the subtitle parser reset and some subtitle lines are not shown. Also remove unused next_offset field. https://bugzilla.gnome.org/show_bug.cgi?id=693981 2013-03-22 09:35:21 + Tim-Philipp Müller tim.mul...@collabora.co.uk * gst/typefind/gsttypefindfunctions.c: typefinding: fix y4m caps We need to specify the y4mversion field now. https://bugzilla.gnome.org/show_bug.cgi?id=696282 2013-03-21 15:37:31 +0100 Sebastian Dröge sebastian.dro...@collabora.co.uk * gst/playback/gstsubtitleoverlay.c: subtitleoverlay: Return ANY caps for the GET_CAPS query subtitleoverlay handles any caps, not just the ones for which a subtitle parser/renderer exist. It will just ignore any unsupported streams instead of causing an error. https://bugzilla.gnome.org/show_bug.cgi?id=688476 2013-03-20 19:34:06 +0100 Jan Schole jan581...@web.de * gst/videoscale/gstvideoscale.c: videoscale: Correct DAR and border calculations changed: gst_video_scale_set_info in gst/videoscale/gstvideoscale.c DAR on sink side now calculated with PAR on sink side ratio of output width/height now calculated with inverse PAR additional condition that borders are 0:0 for passthrough mode https://bugzilla.gnome.org/show_bug.cgi?id=696019 2013-03-21 11:42:43 +0100 Sebastian Dröge sebastian.dro...@collabora.co.uk * gst/playback/gstplaysinkconvertbin.c: playsinkconvertbin: Use gst_caps_is_subset() for handling the ACCEPT_CAPS query 2013-03-21 13:33:44 +0100 Sebastian Dröge sebastian.dro...@collabora.co.uk * gst/playback/gstplaysinkconvertbin.c: playsinkconvertbin: Make sure to return all allowed caps in the GET_CAPS query Add all the caps that we can convert to to the filter caps, otherwise downstream might just return EMPTY caps because it doesn't handle the filter caps but we could still convert to these caps, causing us to return EMPTY caps although conversion would be possible. https://bugzilla.gnome.org/show_bug.cgi?id=688803 2013-03-21 13:29:06 +0100 Sebastian Dröge sebastian.dro...@collabora.co.uk * sys/ximage/ximagesink.c: ximagesink: Don't access structures of EMPTY caps If the intersection between our caps and the filter caps is empty, just immediately return EMPTY caps instead of trying to access the (non-existant) structures. 2013-03-11 21:55:28 -0600 Greg Rutz g...@gsr-tek.com * ext/libvisual/gstaudiovisualizer.c: libvisual: fix improper video frame clear operation The current code is memsetting the GstVideoFrame.data address to 0s (which causes a segfault). This member is actually an array of data buffers (one for each plane). This fix iterates over each data plane to clear them all. https://bugzilla.gnome.org/show_bug.cgi?id=695655 2013-02-13 21:08:48 +0100 Stefan Sauer enso...@users.sf.net * gst/adder/gstadder.c: * tests/check/elements/adder.c: adder: fix setting caps via the caps property We were setting the query-func on the sink-pad, which got overwritten when adding the new pad to collect pads. Instead register our query-func with the collect pads object. This fixes filter caps. Add a test for it. 2013-02-12 17:22:23 + Vincent Penquerc'h vincent.penque...@collabora.co.uk * gst/encoding/gstencodebin.c: encodebin: sync muxer state with parent bin Other elements were synced, but not the muxer. Makes sure the muxer is in the right state even when encodebin gets added to the pipeline dynamically after the pipeline has been started. 2013-02-07 21:51:06 + Tim-Philipp Müller tim.mul...@collabora.co.uk * configure.ac: build: fix build with automake 1.13 AM_CONFIG_HEADER - AC_CONFIG_HEADERS 2013-02-08 00:05:24 +1100 Jan Schmidt thay...@noraisin.net * ext/pango/gstbasetextoverlay.c: pango: 3rd time's the charm. Fix attribute list handling. Really really fix attribute list handling by taking a copy of the original attributes that pango_attr_list_filter can mutate, but keep the original around intact to restore later. 2013-02-07 23:45:26 +1100 Jan Schmidt thay...@noraisin.net
gst-plugins-good 1.0.6
News Changes since 1.0.5: * auparse: fix caps leak * avidemux: push mode: handle some more 0-size buffer cases * deinterlace: fix infinite loop on EOS with non-default methods or fields * dvdemux: don't return FALSE when dropping sink events, fixes flow errors * level: send a last message on EOS * mp4mux: in faststart mode, don't output up to 4 kB of garbage at the end * osxvideosink: Fix crash in osxvideosink with external window output * osxvideosink: Make GstGLView propagate input events to its parent view * osxvideosink: Make GstNavigation key input events in osxvideosink compatible with x(v)imagesink ones * pulsesink: don't error out if pa_stream_proplist_update() with new tags fails * qtdemux: fix potential crash on short MOOV atom * qtdemux: fix sample leak when processing private qt tags * qtdemux: push mode: only parse moov 1 once * qtdemux: skip disabled tracks * qtmux: set stream language code from tag * rtph264pay: Don't use upstream caps with peer_query_caps() * rtpmp4gdepay: streamtype is not put by all RTSP server, not make it optional * rtpptdemux: forward sticky events and then set caps * rtpsession: Fix wrong code organisation in case of collision * rtspsrc: flush connection when stopping * rtspsrc: only EOS when our source sends BYE * rtspsrc: save the stream SSRC * v4l2: don't check stride for encoded formats * v4l2: fix compilation against newer kernel headers as on FC19 * videomixer2: avoid caps leak * videomixer: fix eos timestamp check * ximagesrc: Set the pixel aspect ratio correctly in the caps * build: allow calling autogen.sh from out-of-tree * build: fix build with automake 1.13 Bugs fixed since 1.0.5: * 628790 : qtdemux: OSD displays persistent chapters subtitles * 656068 : pulsesink: errors out if pa_stream_proplist_update() fails with old pulseaudio versions * 675453 : rtspsrc: only EOS if BYE came from SSRC of the stream * 678429 : souphttpsrc: should return GST_FLOW_ERROR from create function in case of HTTP error 404 not found * 684924 : rtspsrc: flush connection when going to null state * 684944 : avidemux: unhandled buffer size error for cyuv.avi in push mode * 688935 : rtpjitterbuffer not always correctly warns about resetting skew * 689809 : osxvideosink: inconsistent keyboard navigation events * 691484 : osxvideosink: crash when displaying on Qt widget * 691570 : [isomp4/qtdemux] lots of critical warnings on this sample file * 691580 : ximagesrc sets bad pixel-aspect-ratio caps * 691832 : osxvideosink doesn't propagate input events to output window * 692309 : allow autogen.sh to be call out-of-tree * 692786 : CAPS event is forwarded before STREAM_START in rtpptdemux element * 692935 : videomixer: hangs on eos * 692950 : rtpjitterbuffer properties can't be changed after pipeline is started * 693055 : level: 32-bit formats don't work because of typo in format list: S32LEF32LE * 693173 : deinterlace method=greedyl fields=top does not complete * 693307 : videomixer2 leaks caps reference * 693373 : 1.0 branch is still using AM_CONFIG_HEADER * 694010 : qtdemux: crash with partial mp4 / moov atom * 694184 : Wrong code organisation in case of collision in rtpsession * 694275 : auparse: src_caps are leaked * 695629 : rtph264pay: caps negotiation fails if upstream caps is not NULL * 695643 : dvdemux: returns wrong value when it is not processing the sink events * 695644 : deinterlace: going to infinite loop on EOS with method=scalerbob fields=bff * 696355 : qtdemux: sample leak in tag handling * 696358 : qtmux: set language code on streams ChangeLog = http://download.gnome.org/sources/gst-plugins-good/1.0/gst-plugins-good-1.0.6.changes (8.82K) Download http://download.gnome.org/sources/gst-plugins-good/1.0/gst-plugins-good-1.0.6.tar.xz (2.59M) sha256sum: 67f7690a9826d9a6ab28b9af2536a6f3e833ee412bd59dd603c48fb3c6823e0d ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
gnome-control-center: Code freeze break request for 696394
Hi release-team, I'd like to fix the bug 696394 of gnome-control-center. It prevents users from opening the a11y zoom option window. The fix is just correct a typo in a .ui file. Could I commit it? https://bugzilla.gnome.org/show_bug.cgi?id=696394 -- Jiro Matsuzawa E-mail: jmatsuz...@gnome.org jmatsuz...@src.gnome.org matsuzawa...@gmail.com GPG Key ID: 0xECC442E9 GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: gnome-control-center: Code freeze break request for 696394
Jiro Matsuzawa wrote: Hi release-team, I'd like to fix the bug 696394 of gnome-control-center. It prevents users from opening the a11y zoom option window. The fix is just correct a typo in a .ui file. Could I commit it? https://bugzilla.gnome.org/show_bug.cgi?id=696394 Here's a first approval. Fred ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Hard code freeze break request for Nautilus
Hi, https://bugzilla.gnome.org/show_bug.cgi?id=696372 fixes an inconsistency in how NoDisplay=true applications are handled by Nautilus; they're currently displayed in the Open With context menus when they shouldn't. The fix is low risk and doesn't impact any translation or documentation. OK to commit for 3.8.0? Thanks! Cosimo ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
gnome-shell freeze break request
Hi, I'd like to get the patch from https://bugzilla.gnome.org/show_bug.cgi?id=696404 into 3.8 it fixes a regression where opening the application view in the overview (or any other shell UI where we use the edge fade effect) can cause a 30 second lag for every paint on older hardware. The patch from the bug just reverts the behavior to what we had in 3.6, so it is low (~0) risk. We can revisit for 3.10 once / if we have a fixed mesa but for now this is the best thing to do. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
A critical fix for gnome-settings-daemon
Heya, If you ever saw the screen turning off after 15 seconds in your normal session, you know who to blame: gnome-shell for crashing. I'm joking. This bug happens when gnome-shell crashes while in screensaver mode (or more likely, is killed). gnome-settings-daemon would think the screensaver was still on, and turn the screen off after 15 seconds whatever their settings. Patch here: https://bugzilla.gnome.org/show_bug.cgi?id=696290 Cheers ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: gnome-shell freeze break request
On Fri, Mar 22, 2013 at 2:23 PM, drago01 drag...@gmail.com wrote: Hi, I'd like to get the patch from https://bugzilla.gnome.org/show_bug.cgi?id=696404 into 3.8 it fixes a regression where opening the application view in the overview (or any other shell UI where we use the edge fade effect) can cause a 30 second lag for every paint on older hardware. The patch from the bug just reverts the behavior to what we had in 3.6, so it is low (~0) risk. We can revisit for 3.10 once / if we have a fixed mesa but for now this is the best thing to do. Thats the responsible thing to do. Approval 1 for the release team ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: A critical fix for gnome-settings-daemon
On Thu, Mar 21, 2013 at 1:32 PM, Bastien Nocera had...@hadess.net wrote: Heya, If you ever saw the screen turning off after 15 seconds in your normal session, you know who to blame: gnome-shell for crashing. I'm joking. This bug happens when gnome-shell crashes while in screensaver mode (or more likely, is killed). gnome-settings-daemon would think the screensaver was still on, and turn the screen off after 15 seconds whatever their settings. Patch here: https://bugzilla.gnome.org/show_bug.cgi?id=696290 Approval 1 for the release team. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Hard code freeze break request for Nautilus
Cosimo Cecchi wrote: that's not the behavior we want, and it's a bug in Evince that has been outstanding for a couple of years now: https://bugzilla.gnome.org/show_bug.cgi?id=634245 Oh, of course I remember this now :/ I don't think we should have it blocking the Nautilus fix, which is correct IMO. Sure; patch looks fine. Fred ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Hard code freeze break request for Nautilus
On Fri, Mar 22, 2013 at 5:03 PM, Frederic Peters fpet...@gnome.org wrote: Cosimo Cecchi wrote: that's not the behavior we want, and it's a bug in Evince that has been outstanding for a couple of years now: https://bugzilla.gnome.org/show_bug.cgi?id=634245 Oh, of course I remember this now :/ I don't think we should have it blocking the Nautilus fix, which is correct IMO. Sure; patch looks fine. Second approval from me. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Hard code freeze break request for GtkSourceView
Hello, There was an ABI break in GtkSourceView, because some private functions were exported and G_GNUC_INTERNAL has been added to them during this cycle [1]. So GtkSourceView needs to bump the soname version. The patch is at [2], because GSV was still not using Libtool versioning. Thanks, Sébastien [1] https://bugzilla.gnome.org/show_bug.cgi?id=696412 [2] https://bugzilla.gnome.org/show_bug.cgi?id=477709 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: A last blocker review for 3.8
On Fri, 2013-03-22 at 07:24 -0400, Matthias Clasen wrote: 695741nor Nor Linugnome-contacUNCO contacts is really slow to start It's possible that this is due to a performance issue in libfolks. We've been picking up performance work lately (starting with adding some profiling tests to our test suite), so we'll hopefully be in much better shape for 3.10. The main bugs to keep an eye on are bgo#689549 and bgo#687671. But as far as blockers, this and the other performance bugs won't be fixed by Monday, but hopefully within the next month or so. -Travis ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
