rhythmbox-metadata crashed with SIGSEGV in reconstruct_single_channel()

Bug #761930 reported by Stefan Beller
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

Rythmbox was scanning my music folder after starting.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: rhythmbox 0.13.3-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 15 17:31:43 2011
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f3a9affa486: movss %xmm1,(%r11)
 PC (0x7f3a9affa486) ok
 source "%xmm1" ok
 destination "(%r11)" (0x7f3a9bc37000) in non-writable VMA region: 0x7f3a9bc37000-0x7f3a9bc3d000 r-xp /usr/lib/gstreamer-0.10/libgstcoreindexers.so
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA /usr/lib/gstreamer-0.10/libgstcoreindexers.so
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/libfaad.so.2
 reconstruct_single_channel () from /usr/lib/libfaad.so.2
 ?? ()
 ?? ()
 ?? ()
Title: rhythmbox-metadata crashed with SIGSEGV in reconstruct_single_channel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Stefan Beller (stefanbeller) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 quant_to_spec (ics=0x7f3a9bc30336, quant_data=0x7f3a9bc2fb30, spec_data=0x7f3a9bc2eaf0, hDecoder=<value optimized out>, frame_len=<value optimized out>) at specrec.c:624
 reconstruct_single_channel (hDecoder=0x19a7c00, ics=0x7f3a9bc30336, sce=0x7f3a9bc30330, spec_data=0x7f3a9bc2fb30) at specrec.c:943
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

visibility: private → public
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Omer Akram (om26er) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Stefan Beller (stefanbeller) wrote : Re: [Bug 761930] Re: rhythmbox-metadata crashed with SIGSEGV in reconstruct_single_channel()

Yeah, I tried to reproduce that bug.

But it was gone when I started trying to reproduce.
(There were some heavier system updates, maybe the needed configuration is gone)
So I thought maybe it would come back, but it did not come back over time.

And that's why I forgot this bug. Sorry for not answering for so long.

2011/6/4 Omer Akram <email address hidden>:
> We'd like to figure out what's causing this bug for you, but we haven't
> heard back from you in a while. Could you please provide the requested
> information? Thanks!
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/761930
>
> Title:
>  rhythmbox-metadata crashed with SIGSEGV in
>  reconstruct_single_channel()
>
> Status in “rhythmbox” package in Ubuntu:
>  Incomplete
>
> Bug description:
>  Binary package hint: rhythmbox
>
>  Rythmbox was scanning my music folder after starting.
>
>  ProblemType: Crash
>  DistroRelease: Ubuntu 11.04
>  Package: rhythmbox 0.13.3-0ubuntu5
>  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
>  Uname: Linux 2.6.38-8-generic x86_64
>  NonfreeKernelModules: nvidia
>  Architecture: amd64
>  CrashCounter: 1
>  Date: Fri Apr 15 17:31:43 2011
>  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
>  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
>  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
>  ProcEnviron:
>   SHELL=/bin/bash
>   PATH=(custom, user)
>   LANGUAGE=en_US:en
>   LANG=en_US.UTF-8
>  SegvAnalysis:
>   Segfault happened at: 0x7f3a9affa486:        movss  %xmm1,(%r11)
>   PC (0x7f3a9affa486) ok
>   source "%xmm1" ok
>   destination "(%r11)" (0x7f3a9bc37000) in non-writable VMA region: 0x7f3a9bc37000-0x7f3a9bc3d000 r-xp /usr/lib/gstreamer-0.10/libgstcoreindexers.so
>   Stack memory exhausted (SP below stack segment)
>  SegvReason: writing VMA /usr/lib/gstreamer-0.10/libgstcoreindexers.so
>  Signal: 11
>  SourcePackage: rhythmbox
>  StacktraceTop:
>   ?? () from /usr/lib/libfaad.so.2
>   reconstruct_single_channel () from /usr/lib/libfaad.so.2
>   ?? ()
>   ?? ()
>   ?? ()
>  Title: rhythmbox-metadata crashed with SIGSEGV in reconstruct_single_channel()
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/761930/+subscribe
>

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
Neal McBurnett (nealmcb)
Changed in rhythmbox (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Neal McBurnett (nealmcb) wrote :

I saw this bug in Precise 12.04. I've got an apport report in /var/crash/_usr_lib_rhythmbox_rhythmbox-metadata.1000.crash but am not sure if that tells you what you need, or how to attach that info to this report.

Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in rhythmbox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
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.