rhythmbox crashed with SIGSEGV in gst_pad_query()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
-
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: rhythmbox 3.4.2-4ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Apr 5 20:12:19 2018
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2018-03-02 (34 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
ProcCmdline: rhythmbox
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=cs_CZ.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f127b4dafa6: mov 0x30(%r12),%rdi
PC (0x7f127b4dafa6) ok
source "0x30(%r12)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
gst_pad_query () from /usr/lib/
Title: rhythmbox crashed with SIGSEGV in gst_pad_query()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1302634, 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.