Hello there!
On Tue, Apr 28, 2020 at 12:35:52AM +0200, Bernhard Übelacker wrote:
> Dear Maintainer,
> looking at the backtrace from message 13 and at the changes
> done by upstream, following commit sounds related:
>
> https://github.com/OpenPrinting/system-config-printer/commit/b9289dfe105bdb502
Dear Maintainer,
looking at the backtrace from message 13 and at the changes
done by upstream, following commit sounds related:
https://github.com/OpenPrinting/system-config-printer/commit/b9289dfe105bdb502f183f0afe7a115ecae5f2af#diff-d3f2f90b6e176486d4b8dfe3222577f7
Kind regards,
Bernhard
Backtrace attachment with related dbgsym installed.
Regards
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x7f3de0cb055b in __GI_abort () at abort.c:79
#2 0x7f3de0d09008 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7f3de0e1
Package: system-config-printer-udev
Version: 1.5.12-1
Followup-For: Bug #958104
Dear Maintainer,
in my case it's a strange bug, when I physically turn on the printer I see the
segv and coredump in the logs, but then the printer works, system log attached.
Note that for this printer I had to inst
Package: system-config-printer-udev
Version: 1.5.12-1
Hi,
every time I connect my printer, a new failed systemd service appear.
It has been this way for at least a year (when I started looking at
failed systemd units), and I'm only now reporting it.
An example:
root@warren ~ # systemctl status
5 matches
Mail list logo
