Re: 3.20 target bugs

[Matthias Clasen]

On Mon, Feb 22, 2016 at 11:56 AM, Joanmarie Diggs  wrote:
> On 02/18/2016 07:35 AM, Matthias Clasen wrote:
>> While we are still waiting for 3.19.90 to appear, here is an initial
>> review of the bugs that have been marked as "GNOME target: 3.20"
>> during this cycle. Since this is the first review, the list is
>> somewhat long, and a bit of a mixed bag, I expect us to narrow it down
>> for .91. In any case, all these bugs are well worth fixing, and if you
>> can get one of the off the list, you will make 3.20 a better release.
>
> Can we also add this one to the list please?
> https://bugzilla.gnome.org/show_bug.cgi?id=754048
>

I've done so. Lets see if a fix appears.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: 3.20 target bugs

[Joanmarie Diggs]

On 02/18/2016 07:35 AM, Matthias Clasen wrote:
> While we are still waiting for 3.19.90 to appear, here is an initial
> review of the bugs that have been marked as "GNOME target: 3.20"
> during this cycle. Since this is the first review, the list is
> somewhat long, and a bit of a mixed bag, I expect us to narrow it down
> for .91. In any case, all these bugs are well worth fixing, and if you
> can get one of the off the list, you will make 3.20 a better release.

Can we also add this one to the list please?
https://bugzilla.gnome.org/show_bug.cgi?id=754048

--joanie

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: 3.20 target bugs

[Joanmarie Diggs]

On 02/18/2016 07:35 AM, Matthias Clasen wrote:
> While we are still waiting for 3.19.90 to appear, here is an initial
> review of the bugs that have been marked as "GNOME target: 3.20"
> during this cycle. Since this is the first review, the list is
> somewhat long, and a bit of a mixed bag, I expect us to narrow it down
> for .91. In any case, all these bugs are well worth fixing, and if you
> can get one of the off the list, you will make 3.20 a better release.

I'd like to suggest another one worth fixing:
https://bugzilla.gnome.org/show_bug.cgi?id=756371

GNOME Shell's overview is spewing around 150-300/second
object:state-changed:showing accessibility events, even if all you do is
get in the overview and stare at the screen.

And if you agree that needs to be fixed, another in the same vein:
https://bugzilla.gnome.org/show_bug.cgi?id=758575

I get over 300/second object:state-changed:showing accessibility events
for labels whose text is presumably static.

--joanie

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: 3.20 target bugs

[Giovanni Campagna]

On Thu, Feb 18, 2016 at 4:35 AM, Matthias Clasen 
wrote:

> While we are still waiting for 3.19.90 to appear, here is an initial
> review of the bugs that have been marked as "GNOME target: 3.20"
> during this cycle. Since this is the first review, the list is
> somewhat long, and a bit of a mixed bag, I expect us to narrow it down
> for .91. In any case, all these bugs are well worth fixing, and if you
> can get one of the off the list, you will make 3.20 a better release.
>
> Please help out if you can!
>
> Matthias, for the release team
>
> [...]
>


> Crashes & serious misbehavior
> -
>
> 761613 mutter crash with xwayland glamor
> 761157 libsecret libsecret-0.18.4 seems to crash gnome-shell
> 755721 glib g_inotify_file_monitor_start called with
> nullpointer for dirname causes a segfault
> 761175 librsvg Svg rendering regression from commit 3ae509 onwards
> 750508 gnome-session Logout is broken (a) when session
> inhibitor is active and (b) after logout is canceled once
> 761317 gnome-settings-daemon housekeeping: /tmp/.X11-unix/X0
> socket gets removed during housecleaning
>

I'd like to add 758073 (cogl: winsys-egl-kms: bypass initial output setup
if kms fd passed in) to this list. The patch in that bug was committed, and
it's causing crashes to various people on Intel and Nouveau. It needs to be
reverted.

Cheers,

Giovanni
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: 3.20 target bugs

[Carlos Garnacho]

Hey,

(CCing the Tracker ML for this one)

On Thu, Feb 18, 2016 at 1:35 PM, Matthias Clasen
 wrote:
> While we are still waiting for 3.19.90 to appear, here is an initial
> review of the bugs that have been marked as "GNOME target: 3.20"
> during this cycle. Since this is the first review, the list is
> somewhat long, and a bit of a mixed bag, I expect us to narrow it down
> for .91. In any case, all these bugs are well worth fixing, and if you
> can get one of the off the list, you will make 3.20 a better release.
>
> Please help out if you can!
>
> Matthias, for the release team
>
>
>
> Fallout from GTK+ changes (CSS and others)
> --
>
> 761765 bijiben Notes have a grey background rather than a custom color
> 762137 nautilus GtkPlacesSidebar: row selection jumps around
> 760525 gtk+ Labels in dialog buttons misaligned
> 760560 gtk+ Icon buttons wider in GTK+ 3.19.6
> 757503 gtk+ Selected text is white on white (invisible) -
> WebKit1 / GTK+ 3.19.7 & Adwaita
> 761686 gtk+ GtkTreeView theming problems
> 758893 gnome-shell Journal spam: Gdk-WARNING **:
> gdk-frame-clock: layout continuously requested, giving up after 4
> tries
>
> Power / Battery life problems
> -
>
> 752070 polari polari uses a lot of cpu
> 762194 tracker Indexes on battery
>
> Deprecation cleanup & build issues
> ---
>
> 760887 NetworkManager Do not depend on deprecated libnm-glib
> or dbus-glib when we only want to build the new libnma library
> 760946 NetworkManager nm-connection-editor still uses dbus-glib
> 757934 gobject-intros g-ir-scanner should not use system-provided 
> CFLAGS
> 751588 evolution Port to WebKit2
> 751185 empathy Use clutter-gst-3.0
> 749001 empathy Port to webkit2
> 728293 bijiben Port to WebKit2 or GtkTextView
> 705069 gnome-music Port from dbus-python to Gio GDBus API
> 686373 general [META] Switch to WebKit2
>
> Accessibility regressions
> 
>
> 762136 nautilus Progress of file and folder operations is no
> longer accessible to screen readers
>
> Wayland issues
> ---
>
> 749913 mutter wayland: Send frame callbacks when native
> hardware cursors get set
> 760745 mutter 100% CPU : Error transferring wayland clipboard to 
> X11
> 762104 mutter handle dnd drops on the root window
> 760567 gtk+ GDK screen size does not count for HiDPI on Wayland
> 756579 gtk+ GTK should let GDK position menus
> 748098 gdm monitors.xml not working in GDM when running
> under Wayland
> 695806 general [TRACKER] Wayland support
>
> Crashes & serious misbehavior
> -
>
> 761613 mutter crash with xwayland glamor
> 761157 libsecret libsecret-0.18.4 seems to crash gnome-shell
> 755721 glib g_inotify_file_monitor_start called with
> nullpointer for dirname causes a segfault
> 761175 librsvg Svg rendering regression from commit 3ae509 onwards
> 750508 gnome-session Logout is broken (a) when session
> inhibitor is active and (b) after logout is canceled once
> 761317 gnome-settings-daemon housekeeping: /tmp/.X11-unix/X0
> socket gets removed during housecleaning

I would like to drop https://bugzilla.gnome.org/show_bug.cgi?id=762226 here.

In short, sqlite has hidden stuff that Tracker needs behind a compile
time option (disabled by default) because of security concerns, and
Tracker only stumbles on this at runtime.

AFAICT the security concerns come from arbitrary execution of SQL
being able to alter later queries by overriding the full-text search
tokenizer, so they don't apply to Tracker (our SQL comes from a
bizarre state machine, but doesn't qualify as "arbitrary"). Most
immediately, I'll add a configure time check for this feature,
although I don't think it's ok to advice distros to enable
fts3_tokenizer system-wide. Solutions I can think of are:

- Including a static copy of sqlite in Tracker, with fts3_tokenizer() enabled
- Updating to the newer but code-wise incompatible fts5 (we use fts4),
which provides other similar hooks we can use. It's probably too
bleeding edge though, it was considered "experimental" not long ago
[1], and I haven't seen a word saying otherwise in later release
notes.

In this situation, the second option is a matter of time, I'd just
wish there were a longer board to walk.

Cheers,
  Carlos

[1] http://sqlite.org/releaselog/3_9_0.html
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: 3.20 target bugs

[Matthias Clasen]

Noted, thanks

On Thu, Feb 18, 2016 at 1:37 PM, Milan Crha  wrote:
> On Thu, 2016-02-18 at 07:35 -0500, Matthias Clasen wrote:
>> 751588 evolution Port to WebKit2
>
> Hi,
> I would change the GNOME Target to 3.22, but I'm not able to do it, the
> value is not a Drop Down, but a static text for me. The thing is that
> the port to WebKit2 won't happen in time for 3.20 for the Evolution.
> Bye,
> Milan
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: 3.20 target bugs

[Milan Crha]

On Thu, 2016-02-18 at 07:35 -0500, Matthias Clasen wrote:
> 751588 evolution Port to WebKit2

Hi,
I would change the GNOME Target to 3.22, but I'm not able to do it, the
value is not a Drop Down, but a static text for me. The thing is that
the port to WebKit2 won't happen in time for 3.20 for the Evolution.
Bye,
Milan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

3.20 target bugs

[Matthias Clasen]

While we are still waiting for 3.19.90 to appear, here is an initial
review of the bugs that have been marked as "GNOME target: 3.20"
during this cycle. Since this is the first review, the list is
somewhat long, and a bit of a mixed bag, I expect us to narrow it down
for .91. In any case, all these bugs are well worth fixing, and if you
can get one of the off the list, you will make 3.20 a better release.

Please help out if you can!

Matthias, for the release team



Fallout from GTK+ changes (CSS and others)
--

761765 bijiben Notes have a grey background rather than a custom color
762137 nautilus GtkPlacesSidebar: row selection jumps around
760525 gtk+ Labels in dialog buttons misaligned
760560 gtk+ Icon buttons wider in GTK+ 3.19.6
757503 gtk+ Selected text is white on white (invisible) -
WebKit1 / GTK+ 3.19.7 & Adwaita
761686 gtk+ GtkTreeView theming problems
758893 gnome-shell Journal spam: Gdk-WARNING **:
gdk-frame-clock: layout continuously requested, giving up after 4
tries

Power / Battery life problems
-

752070 polari polari uses a lot of cpu
762194 tracker Indexes on battery

Deprecation cleanup & build issues
---

760887 NetworkManager Do not depend on deprecated libnm-glib
or dbus-glib when we only want to build the new libnma library
760946 NetworkManager nm-connection-editor still uses dbus-glib
757934 gobject-intros g-ir-scanner should not use system-provided CFLAGS
751588 evolution Port to WebKit2
751185 empathy Use clutter-gst-3.0
749001 empathy Port to webkit2
728293 bijiben Port to WebKit2 or GtkTextView
705069 gnome-music Port from dbus-python to Gio GDBus API
686373 general [META] Switch to WebKit2

Accessibility regressions


762136 nautilus Progress of file and folder operations is no
longer accessible to screen readers

Wayland issues
---

749913 mutter wayland: Send frame callbacks when native
hardware cursors get set
760745 mutter 100% CPU : Error transferring wayland clipboard to X11
762104 mutter handle dnd drops on the root window
760567 gtk+ GDK screen size does not count for HiDPI on Wayland
756579 gtk+ GTK should let GDK position menus
748098 gdm monitors.xml not working in GDM when running
under Wayland
695806 general [TRACKER] Wayland support

Crashes & serious misbehavior
-

761613 mutter crash with xwayland glamor
761157 libsecret libsecret-0.18.4 seems to crash gnome-shell
755721 glib g_inotify_file_monitor_start called with
nullpointer for dirname causes a segfault
761175 librsvg Svg rendering regression from commit 3ae509 onwards
750508 gnome-session Logout is broken (a) when session
inhibitor is active and (b) after logout is canceled once
761317 gnome-settings-daemon housekeeping: /tmp/.X11-unix/X0
socket gets removed during housecleaning

UI review issues
---

757243 gnome-initial-setup Obscure input methods prioritised in the list
745603 gnome-control-center Language dialog has incorrect default size
761759 gnome-contacts Header bar elements are too narrow,
aren't aligned with sidebar
759004 gnome-shell Missing entries in applications menu
761939 gnome-control-center Blank/empty universal access settings panel
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list