Control: reassign -1 libgeocode-glib0 3.26.0-2
Control: severity 925539 serious
Control: forcemerge 925539 -1
On Tue, 23 Apr 2019 at 01:05:55 +0200, gpe wrote:
> I confirm. Installing libgeocode-glib0 3.26.1-1 resolves the issue.
Reassigning to libgeocode-glib0 and merging with the existing bug,
Le mardi 23 avril 2019 à 00:44 +0200, Bernhard Übelacker a écrit :
> Hello gpe,
> this stack trace looks really like that one
> submitted in https://bugs.debian.org/927728 .
>
> Possibly you can install just libgeocode-glib0 3.26.1-1
> from unstable?
>
> From my findings in
Hello gpe,
this stack trace looks really like that one
submitted in https://bugs.debian.org/927728 .
Possibly you can install just libgeocode-glib0 3.26.1-1
from unstable?
>From my findings in https://bugs.debian.org/927728
I would expect that this crash should then be gone.
Kind regards,
Le mardi 23 avril 2019 à 00:20 +0200, Bernhard Übelacker a écrit :
> Hello gpe92,
> maybe you could add some more information for the maintainer
> by following steps, if possible:
> - install the package "systemd-coredump"
> - try to start gnome-maps again
> - forward the output of following
Hello gpe92,
maybe you could add some more information for the maintainer
by following steps, if possible:
- install the package "systemd-coredump"
- try to start gnome-maps again
- forward the output of following command to this bug:
journalctl | sed -n '/dumped core/,/systemd-coredump@/p'
I
Package: gnome-maps
Version: 3.30.3-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
starts gnome-maps
* What exactly did you do (or not do) that was effective (or
ineffective)?
run gnome-maps in CLI
* What was the
6 matches
Mail list logo
