Re: Bug#827335: evince: assertion failed: (wayland_display->cursor_theme_name)

2016-10-15 Thread intrigeri
Control: reassign -1 apparmor Control: notfound -1 evince/3.20.0-4 Control: found -1 apparmor/2.10.95-4 Control: affects -1 + evince Control: retitle -1 evince crashes under Wayland with AppArmor enabled: assertion failed: (wayland_display->cursor_theme_name) Hi, intrigeri: >

Re: Bug#827335: evince: assertion failed: (wayland_display->cursor_theme_name)

2016-10-13 Thread intrigeri
Hi, Michael Biebl: + owner /{,var/}run/user/*/weston-shared-* rw, I've run into this bug myself last month and submitted a pull request to AppArmor upstream that does basically that, except I do it by introducing a new 'wayland' abstraction, that I include in the 'gnome' one:

Re: Bug#827335: evince: assertion failed: (wayland_display->cursor_theme_name)

2016-10-12 Thread Jason Crain
On Wed, Oct 12, 2016 at 03:13:33PM +0200, Michael Biebl wrote: > I've tried running evince under GNOME/Wayland and I don't have a > /run/user/*/weston-shared-* directory > > Since I know nothing about apparmor, I'd prefer having input from the > apparmor and wayland maintainers first, if the

Re: Bug#827335: evince: assertion failed: (wayland_display->cursor_theme_name)

2016-10-12 Thread Michael Biebl
Am 11.10.2016 um 22:53 schrieb Jason Crain: > On Tue, Oct 11, 2016 at 09:44:48PM +0200, Michael Biebl wrote: >> Am 11.10.2016 um 19:52 schrieb Diane Trout: >>> --- debian/evince/etc/apparmor.d/usr.bin.evince 2016-10-10 >>> 23:32:09.826405495 -0700 >>> +++ /etc/apparmor.d/usr.bin.evince