Your message dated Mon, 17 Oct 2016 19:12:55 +0200 with message-id <1476724375.5756.5.ca...@gmail.com> and subject line Re: Bug#841082: epiphany-browser: crash when trying to show desktop notifications has caused the Debian Bug report #841082, regarding epiphany-browser: crash when trying to show desktop notifications to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 841082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: epiphany-browser Version: 3.22.1-1 Severity: important Dear Maintainer, * What led up to the situation? Visit https://davidwalsh.name/demo/notifications-api.php and click on "Show a notification" button * What was the outcome of this action? The browser crashed. Launching it from the terminal allowed me to see this error. (epiphany:760): GLib-GIO-ERROR **: Settings schema 'org.gnome.Epiphany.host' is not installed That's making the UI process crash as seen in this backtrace (no debug symbols but good enough) Thread 1 "epiphany" received signal SIGTRAP, Trace/breakpoint trap. 0x00007ffff0c36241 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 (gdb) bt #0 0x00007ffff0c36241 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007ffff0c37297 in g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00005555555d53e2 in ?? () #3 0x00007ffff0c375a4 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007ffff0c377af in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007ffff12542ef in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x00007ffff0f0e583 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x00007ffff0f1010e in g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x00007ffff0f103b1 in g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x00007ffff125559a in g_settings_new_with_backend_and_path () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #10 0x00005555555bc760 in ?? () #11 0x00005555555bc9e9 in ephy_hosts_manager_get_notifications_permission_for_address () #12 0x00005555555beed5 in ?? () * What outcome did you expect instead? Browser should show a permission request dialog. This is working fine on the MiniBrowser included in the package, so it's likely a configuration issue. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages epiphany-browser depends on: ii dbus-user-session [default-dbus-session-bus] 1.10.10-1 ii dbus-x11 [dbus-session-bus] 1.10.12-1 ii epiphany-browser-data 3.22.0-1 ii gsettings-desktop-schemas 3.22.0-1 ii iso-codes 3.67-1 ii libavahi-client3 0.6.32-1 ii libavahi-common3 0.6.32-1 ii libavahi-gobject0 0.6.32-1 ii libc6 2.23-5 ii libcairo2 1.14.6-1+b1 ii libgcr-base-3-1 3.20.0-2 ii libgcr-ui-3-1 3.20.0-2 ii libgdk-pixbuf2.0-0 2.35.5-1 ii libglib2.0-0 2.50.0-1 ii libgnome-desktop-3-12 3.21.90-3 ii libgtk-3-0 3.22.0-1 ii libjavascriptcoregtk-4.0-18 2.14.1-1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.40.2-1 ii libpangocairo-1.0-0 1.40.2-1 ii libsecret-1-0 0.18.5-2 ii libsoup2.4-1 2.54.0.1-2 ii libsqlite3-0 3.12.2-1 ii libwebkit2gtk-4.0-37 2.14.1-1 ii libx11-6 2:1.6.3-1 ii libxml2 2.9.3+dfsg1-1 ii libxslt1.1 1.1.29-1 Versions of packages epiphany-browser recommends: ii browser-plugin-evince 3.21.4-1 ii ca-certificates 20160104 ii evince 3.22.0-1 ii yelp 3.20.1-1 epiphany-browser suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Closing as moving to 3.22.1 fixed the issue. In any case perhaps we should never crash in those cases but just fail.
--- End Message ---
