Hello Jörg Frings-Fürst,
I am not maintaining roger-router, but just saw this report.
Do you still receive this segmentation fault?
If yes you might run roger like the following:
(That should print the backtrace when the segmentation fault happens.)
gdb -q -ex run -ex bt -ex detach -ex quit --a
severity 865460 important
thanks
On 08.09.2017 00:40, Jörg Frings-Fürst wrote:
> roger is unusablel with this bug. So I set the severity to grave.
Hello Jörg,
thank you for the report. FWIW, roger runs fine for me, albeit on an
Ubuntu system. In your original report you write "since some days
severity 865460 grave
thanks
Hello,
roger is unusablel with this bug. So I set the severity to grave.
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56
Old pgp Key: BE581B
Package: roger-router
Version: 1.8.14-2+b3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
since some days roger-router don't login at start and crashes at reconnect.
[quote]
$ roger
ALSA lib pcm_dsnoop.c:618:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmi
4 matches
Mail list logo