clementine crashed with SIGSEGV in oil_init()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
clementine (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
reading files off a smb share, only happens when there is a delay in access, like hard drive on remove computer which shares files is spinning up.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: clementine 1.1.1+dfsg-1ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-31-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Mon Sep 30 17:46:45 2013
ExecutablePath: /usr/bin/clementine
InstallationDate: Installed on 2012-01-06 (633 days ago)
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: /usr/bin/clementine
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7f43ceb6e071: mov 0x20(%rax),%rax
PC (0x7f43ceb6e071) ok
source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%rax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: clementine
StacktraceTop:
?? () from /usr/lib/
oil_init () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: clementine crashed with SIGSEGV in oil_init()
UpgradeStatus: Upgraded to raring on 2013-04-27 (156 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(dropbox:18621): Gtk-WARNING **: /var/lib/
(dropbox:18621): Gtk-WARNING **: /var/lib/
(steam:19330): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",
(steam:19330): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",
(steam:19330): Gtk-WARNING **: Failed to load type module: (null)
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 #1206390, 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.