GNOME Bugzilla – Bug 624825
Crashed with SIGSEGV in malloc()
Last modified: 2018-05-24 15:23:18 UTC
In Ubuntu Lucid James Dearing reported: Rhythmbox crashes as soon as I start it. When run from a terminal, the following output is given: ---begin terminal output--- $ rhythmbox ** (rhythmbox:4550): DEBUG: Loading the real store page liboauth: data to sign='GET&https%3A%2F%2Fone.ubuntu.com%2Fmusic%2Flogin&oauth_callback%3DNone%26oauth_consumer_key%3Dubuntuone%26oauth_nonce%3Ds6kJV5RfdAnqAmaYCgqsPGydj%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1270489222%26oauth_token%3DpKL7SdN6pGdzTRznGTP3%26oauth_verifier%3DNone%26oauth_version%3D1.0' liboauth: key='hammertime&QfzL5M1wBs9TPCj9qj1mkPB7szqLH43xlDFbn1VC9lLQ6rl9jfFQk2d73kgFqLKPHLBK0BwrSNsK1JzJ' Segmentation fault (core dumped) ---end terminal output--- ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: rhythmbox 0.12.8-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: wl nvidia Architecture: amd64 CrashCounter: 1 Date: Mon Apr 5 10:35:17 2010 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcCmdline: rhythmbox ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fba428d573a: mov 0x8(%rbx),%rdx PC (0x7fba428d573a) ok source "0x8(%rbx)" (0x6e495f656c707049) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /lib/libc.so.6 ?? () from /lib/libc.so.6 malloc () from /lib/libc.so.6 ?? () from /lib/libc.so.6 usb_os_find_busses () from /lib/libusb-0.1.so.4 Title: rhythmbox crashed with SIGSEGV in malloc() UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare Launchpad ref: https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/555885 Thanks!
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Hi, in launchpad bug, there is a valgrind log, if this enough? if not please switch to needinfo again. http://launchpadlibrarian.net/43394390/valgrind.log Thanks!
When you're forwarding bugs from launchpad, you need to include all the information from the original bug report.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/950.