dleyna-renderer-service crashed with SIGSEGV in dlr_device_unsubscribe()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dleyna-renderer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
happened in 16.10, 17.04 and now 17.10 consistently and it takes a bit of time after using apps for it to occur. Happens in gnome-shell
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10
dleyna-renderer:
Installed: 0.4.0-1
Candidate: 0.4.0-1
Version table:
*** 0.4.0-1 500
500 http://
100 /var/lib/
the bug message to stop and the underlying issue resolved, I don't know how this affects the system since its totally useable but every time I login I get the error which is pretty annoying.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: dleyna-renderer 0.4.0-1
ProcVersionSign
Uname: Linux 4.12.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Sep 16 16:05:48 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2015-09-25 (722 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150826.1)
JournalErrors:
Error: command ['journalctl', '-b', '--priority=
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
ProcCmdline: /usr/lib/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_US
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f0d99acfe52 <dlr_device_
PC (0x7f0d99acfe52) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: dleyna-renderer
StacktraceTop:
dlr_device_
dlr_upnp_
() at /usr/lib/
() at /usr/lib/
g_main_
Title: dleyna-
UpgradeStatus: Upgraded to artful on 2017-09-07 (9 days ago)
UserGroups: sudo
tags: | removed: need-amd64-retrace |
information type: | Private → Public |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1440509, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.