Your message dated Wed, 1 May 2019 13:24:00 +0100 with message-id <[email protected]> and subject line Re: Bug#928264: [gnome-maps] Gnome Maps crashes as soon as you search for a city. has caused the Debian Bug report #928264, regarding [gnome-maps] Gnome Maps crashes as soon as you search for a city. 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 [email protected] immediately.) -- 928264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928264 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnome-maps Version: 3.22.2 Severity: serious Tags: patch --- Please enter the report below this line. --- Now Gnome Maps crashes as soon as you search for a city, any type of city. This behavior was not present before. My system is default, nothing strange, nothing out of the ordinary, no package installed from non- official Debian repositories, the system is freshly installed with all default applications. --- System information. --- Architecture: Kernel: Linux 4.9.0-9-amd64 Debian Release: 9.9 500 stable-updates ftp.de.debian.org 500 stable security.debian.org 500 stable ftp.de.debian.org --- Package information. --- Depends (Version) | Installed ==========================================-+-============== geoclue-2.0 (>= 2.0) | 2.4.5-1 gir1.2-champlain-0.12 | 0.12.15-1 gir1.2-clutter-1.0 | 1.26.0+dfsg-3 gir1.2-cogl-1.0 | 1.22.2-2 gir1.2-gdkpixbuf-2.0 | 2.36.5-2+deb9u2 gir1.2-geoclue-2.0 | 2.4.5-1 gir1.2-geocodeglib-1.0 (>= 3.15.2) | 3.20.1-2 gir1.2-glib-2.0 (>= 1.41) | 1.50.0-1+b1 gir1.2-goa-1.0 | 3.22.5-1 gir1.2-gtk-3.0 (>= 3.10) | 3.22.11-1 gir1.2-gtkchamplain-0.12 | 0.12.15-1 gir1.2-gtkclutter-1.0 | 1.8.2-2 gir1.2-gfbgraph-0.2 | 0.2.3-1+b2 gir1.2-gweather-3.0 | 3.20.4-1 gir1.2-rest-0.7 | 0.8.0-2 gir1.2-secret-1 | 0.18.5-3.1 gir1.2-soup-2.4 | 2.56.0-2+deb9u2 gir1.2-webkit2-4.0 | 2.18.6-1~deb9u1 gjs (>= 1.44.0) | 1.46.0-1+b2 libglib2.0-bin (>= 2.40.0-3) | 2.50.3-2 dconf-gsettings-backend | 0.26.0-2+b1 OR gsettings-backend | libatk1.0-0 (>= 1.12.4) | 2.22.0-1 libc6 (>= 2.4) | 2.24-11+deb9u4 libcairo-gobject2 (>= 1.10.0) | 1.14.8-1 libcairo2 (>= 1.2.4) | 1.14.8-1 libchamplain-0.12-0 (>= 0.11.0) | 0.12.15-1 libclutter-1.0-0 (>= 1.10.0) | 1.26.0+dfsg-3 libcogl-pango20 (>= 1.17.4) | 1.22.2-2 libcogl-path20 (>= 1.17.4) | 1.22.2-2 libcogl20 (>= 1.17.4) | 1.22.2-2 libdrm2 (>= 2.3.1) | 2.4.74-1 libegl1-mesa (>= 7.8.1) | 13.0.6-1+b2 OR libegl1-x11 | libfolks25 (>= 0.9.7) | 0.11.3-2 libgbm1 (>= 7.11~1) | 13.0.6-1+b2 libgdk-pixbuf2.0-0 (>= 2.22.0) | 2.36.5-2+deb9u2 libgee-0.8-2 (>= 0.8.3) | 0.18.1-1 libgeocode-glib0 (>= 3.16.2) | 3.20.1-2 libglib2.0-0 (>= 2.43.91) | 2.50.3-2 libgtk-3-0 (>= 3.15.9) | 3.22.11-1 libjson-glib-1.0-0 (>= 0.12.0) | 1.2.6-1 libpango-1.0-0 (>= 1.14.0) | 1.40.5-1 libpangocairo-1.0-0 (>= 1.14.0) | 1.40.5-1 librest-0.7-0 (>= 0.7) | 0.8.0-2 libsoup2.4-1 (>= 2.4.0) | 2.56.0-2+deb9u2 libwayland-client0 (>= 1.0.2) | 1.12.0-1+deb9u1 libwayland-cursor0 (>= 1.0.2) | 1.12.0-1+deb9u1 libwayland-egl1-mesa (>= 10.0.2) | 13.0.6-1+b2 OR libwayland-egl1 | libwayland-server0 (>= 1.0.2) | 1.12.0-1+deb9u1 libx11-6 | 2:1.6.4-3+deb9u1 libxcomposite1 (>= 1:0.3-1) | 1:0.4.4-2 libxdamage1 (>= 1:1.1) | 1:1.1.4-2+b3 libxext6 | 2:1.3.3-1+b2 libxfixes3 | 1:5.0.3-1 libxi6 | 2:1.7.9-1 libxkbcommon0 (>= 0.5.0) | 0.7.1-2~deb9u1 libxml2 (>= 2.7.4) | 2.9.4+dfsg1-2.2+deb9u2 libxrandr2 | 2:1.5.1-1 Package's Recommends field is empty. Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---Version: 3.26.1-1 On Wed, 01 May 2019 at 14:13:00 +0200, Bernhard Übelacker wrote: > Control: fixed 928264 libgeocode-glib0/3.26.1-1 This doesn't close the bug. I'm closing it as fixed in that version so that it doesn't show up in the list of release blockers for buster. > but just fixed in buster yet The BTS has version-tracking, so it will correctly indicate that the version in stretch still has this bug. If someone wants to backport a fix to geocode-glib in stretch, they will need to go through the stable updates process. smcv
--- End Message ---
