Ubuntu
libsoup package

rhythmbox crashed with SIGSEGV in strchr()

Bug #415397 reported by Alexander Hunziker
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libsoup (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

Rhythmbox crased after a a while of sitting in the tray inactively.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Aug 18 16:10:15 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.12.3-1ubuntu2
ProcCmdline: rhythmbox
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
SegvAnalysis:
 Segfault happened at: 0xb6f60983 <strchr+99>: mov (%eax),%ecx
 PC (0xb6f60983) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 strchr () at ../sysdeps/i386/strchr.S:127
 ?? () from /usr/lib/libsoup-2.4.so.1
 ?? () from /usr/lib/libsoup-2.4.so.1
 IA__g_cclosure_marshal_VOID__VOID (closure=0xb2e4bc50,
 IA__g_closure_invoke (closure=0xb2e4bc50, return_value=0x0,
Title: rhythmbox crashed with SIGSEGV in strchr()
Uname: Linux 2.6.31-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Alexander Hunziker (alex-hunziker) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:strchr () at ../sysdeps/i386/strchr.S:127
?? () from /usr/lib/libsoup-2.4.so.1
?? () from /usr/lib/libsoup-2.4.so.1
IA__g_cclosure_marshal_VOID__VOID (closure=0xb2e4bc50,
IA__g_closure_invoke (closure=0xb2e4bc50, return_value=0x0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Pedro Villavicencio (pedro)
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Also, please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will greatly aid us in tracking down your problem and resolving this bug. Looks like a libsoup crash.

Changed in rhythmbox (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Incomplete
Revision history for this message
Alexander Hunziker (alex-hunziker) wrote :

Pedro,

it is "reproducible" in that it happened again. But it's reproducible in a sense that I have to keep it in the tray for a day and wait until it crashes. If you can think of a debugging strategy, I'll be happy to try.

Pedro Villavicencio (pedro)
affects: rhythmbox (Ubuntu) → libsoup (Ubuntu)
Changed in libsoup (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: Incomplete → New
Revision history for this message
dino99 (9d9) wrote :

This version has died long ago; no more supported

Changed in libsoup (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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