After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 484939 - crash in Rhythmbox Music Player: rhythmbox crashed on sta...
crash in Rhythmbox Music Player: rhythmbox crashed on sta...
Status: RESOLVED INCOMPLETE
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-09 05:55 UTC by Johannes Rohr
Modified: 2007-10-09 22:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Johannes Rohr 2007-10-09 05:55:23 UTC
Version: 0.10.1

What were you doing when the application crashed?
rhythmbox crashed on startup


Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 58580992 vsize: 58580992 resident: 33185792 share: 17080320 rss: 33185792 rss_rlim: 4294967295
CPU usage: start_time: 1191908990 rtime: 195 utime: 164 stime: 31 cutime:70 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b476c0 (LWP 8040)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b476c0 (LWP 8040))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.14.1/glib/gspawn.c line 364
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.14.1/glib/gspawn.c line 672
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 IA__g_logv
  • #10 IA__g_log
  • #11 IA__g_assert_warning
    at /tmp/buildd/glib2.0-2.14.1/glib/gmessages.c line 552
  • #12 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #13 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (86 sec old) ---------------------
ALSA lib pcm_dmix.c:803:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:803:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL softvol
ALSA lib pcm_dmix.c:803:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL dmixer
ALSA lib pcm_dmix.c:803:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:803:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL softvol
ALSA lib pcm_dmix.c:803:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL dmixer
** ERROR **: file dbus-gproxy.c: line 659 (unassociate_proxies): assertion failed: (priv->associated)
aborting...
(soffice.bin:8301): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-10-09 11:12:11 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Johannes Rohr 2007-10-09 16:46:46 UTC
Hi there, I installed pretty much every -dbg package that Debian offers, so I'm really surprised that this bug is labelled incomplete. Please let me know what is missing (debugging information from which binaries/libraries)
Comment 3 Jonathan Matthew 2007-10-09 22:55:04 UTC
You're missing symbols from dbus-glib, at least.