Your message dated Mon, 25 Sep 2017 20:53:38 +0100
with message-id <20170925195338.6uv2mo2m6lapb...@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#740139: gnome-maps fails to start
has caused the Debian Bug report #740139,
regarding gnome-maps fails to start
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.)
--
740139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-maps
Version: 3.10.2-1
Severity: grave
Justification: renders package unusable
Trying to start gnome-maps I get the following stderr output:
JS ERROR: !!! Exception was: Gio.DBusError: Error calling
StartServiceByName for org.freedesktop.GeoClue2:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited
with unknown return code 253
JS ERROR: !!! message = '"Error calling StartServiceByName for
org.freedesktop.GeoClue2:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited
with unknown return code 253"'
JS ERROR: !!! fileName = '"/usr/share/gjs-1.0/overrides/Gio.js"'
JS ERROR: !!! lineNumber = '250'
JS ERROR: !!! stack = '"0
anonymous(null)@/usr/share/gjs-1.0/overrides/Gio.js:250
1 anonymous("cancellable" = null, "asyncCallback" = undefined, "object" =
""/org/freedesktop/GeoClue2/Manager"", "name" = ""org.freedesktop.GeoClue2"",
"bus" = [object GObject_Object])@/usr/share/gjs-1.0/overrides/Gio.js:209
2 anonymous()@/usr/share/gnome-maps/js/geoclue.js:110
3 wrapper()@/usr/share/gjs-1.0/lang.js:213
4 anonymous()@/usr/share/gjs-1.0/lang.js:154
5 anonymous()@/usr/share/gjs-1.0/lang.js:248
6 anonymous("overlay" = [object GObject_Object])@/usr/share/gnome-
maps/js/mapView.js:87
7 wrapper([object GObject_Object])@/usr/share/gjs-1.0/lang.js:213
8 anonymous("app" = [object GObject_Object])@/usr/share/gnome-
maps/js/mainWindow.js:69
9 wrapper([object GObject_Object])@/usr/share/gjs-1.0/lang.js:213
10 anonymous([object GObject_Object])@/usr/share/gjs-1.0/lang.js:154
11 anonymous([object GObject_Object])@/usr/share/gjs-1.0/lang.js:248
12 anonymous()@/usr/share/gnome-maps/js/application.js:97
13 wrapper()@/usr/share/gjs-1.0/lang.js:213
14 anonymous()@/usr/share/gnome-maps/js/application.js:102
15 wrapper()@/usr/share/gjs-1.0/lang.js:213
16 start()@/usr/share/gnome-maps/js/main.js:28
17 <TOP LEVEL>@<command line>:1
"'
Is it somehow possible to start the geoclue2 dbus service manually to try and
debug this?
Sincerly,
Marcus Lundblad
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnome-maps depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.18.0-1
ii geoclue-2.0 2.0.0-4
ii gir1.2-champlain-0.12 0.12.5-1
ii gir1.2-clutter-1.0 1.14.4-3
ii gir1.2-cogl-1.0 1.14.0-3
ii gir1.2-gdkpixbuf-2.0 2.30.5-1
ii gir1.2-geocodeglib-1.0 3.10.0-1
ii gir1.2-glib-2.0 1.36.0-2+b1
ii gir1.2-gtk-3.0 3.10.7-1
ii gir1.2-gtkchamplain-0.12 0.12.5-1
ii gir1.2-gtkclutter-1.0 1.4.4-3
ii gjs 1.36.1-2
gnome-maps recommends no packages.
gnome-maps suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.8.0-2
On Sun, 16 Mar 2014 at 12:22:00 +0100, Andreas Henriksson wrote:
> Control: fixed -1 1.8.0-2
...
> This makes me suspect the automatic reloading of dbus did not
> work properly and as Simon McVittie already suggested
> using dpkg triggers to be definitely sure that a reload
> happens I'm reassigning this bug report to dbus where
> I think it can be closed when the triggers has been
> implemented (which it already has?).
Closing this bug (marking it fixed does not actually close it).
Regards,
smcv
--- End Message ---
