clementine crashed with SIGSEGV in gst_element_set_state()

Bug #1862488 reported by Chris Guiver
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
clementine (Ubuntu)
New
Medium
Unassigned

Bug Description

Clementine has been crashing many times a day in recent day(s).

I tried submitting `ubuntu-bug` each time, but no offers to login to browser were offered (possibly because my stack was outdated as it had started nagging me to).

It usually crashes after finishing a song/track & moving to the next track.

There will/could be a number of entries in it's playlists that no longer exist (one of my playlists has no files present, that directory was erased; but I can 'play' that playlist and it just skips from one to the other endlessly without crashing which is expected behavior)

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: clementine 1.3.1+git609-g623a53681+dfsg-1build1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CrashCounter: 1
CurrentDesktop: LXQt
Date: Sun Feb 9 11:37:00 2020
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/clementine
ExecutableTimestamp: 1541880273
InstallationDate: Installed on 2017-11-16 (814 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/clementine
ProcCwd: /home/guiverc
SegvAnalysis:
 Segfault happened at: 0x7fc119bb3734 <gst_element_set_state+36>: cmp %rax,(%rbx)
 PC (0x7fc119bb3734) ok
 source "%rax" ok
 destination "(%rbx)" (0xffffffff) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: clementine
StacktraceTop:
 gst_element_set_state () at /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
 QObjectPrivate::signalIndex(char const*, QMetaObject const**) const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 ()
 QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
Title: clementine crashed with SIGSEGV in gst_element_set_state()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo vboxusers
separator:

Revision history for this message
Chris Guiver (guiverc) wrote :
information type: Private → Public Security
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gst_element_set_state (element=0x7fc1080462b0, state=GST_STATE_NULL) at gstelement.c:2802
 QObjectPrivate::signalIndex (this=0x7fc1080462b0, signalName=0x7fc0f4018410 "\243", meta=0x0) at kernel/qobject.cpp:3869
 ?? ()
 QCoreApplicationPrivate::sendThroughApplicationEventFilters (event=<optimized out>, receiver=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qlist.h:170
 QCoreApplicationPrivate::sendThroughApplicationEventFilters (this=<optimized out>, receiver=<optimized out>, event=<optimized out>) at kernel/qcoreapplication.cpp:1181

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in clementine (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Eduardo Barretto (ebarretto) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Public Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.