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 463272 - crash in Rhythmbox Music Player: Nothing
crash in Rhythmbox Music Player: Nothing
Status: RESOLVED DUPLICATE of bug 434003
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-03 21:55 UTC by ranitax23
Modified: 2007-08-07 13:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ranitax23 2007-08-03 21:55:28 UTC
What were you doing when the application crashed?
Nothing


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 161816576 vsize: 161816576 resident: 37634048 share: 19779584 rss: 37634048 rss_rlim: 4294967295
CPU usage: start_time: 1186177974 rtime: 493 utime: 446 stime: 47 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208682784 (LWP 5378)]
[New Thread -1238492272 (LWP 5437)]
[New Thread -1226765424 (LWP 5435)]
[New Thread -1322275952 (LWP 5433)]
[New Thread -1311786096 (LWP 5424)]
[New Thread -1224688752 (LWP 5403)]
[New Thread -1257645168 (LWP 5397)]
(no debugging symbols found)
0x004b6402 in __kernel_vsyscall ()

Thread 2 (Thread -1238492272 (LWP 5437))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libgthread-2.0.so.0
  • #10 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #11 ??
  • #12 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #13 ??
  • #14 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0


----------- .xsession-errors (8 sec old) ---------------------
  Resource id:  0x180265e
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x50
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x18026d9
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x50
QApplication::postEvent: Unexpected null receiver
~ScimInputContextPlugin()
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-08-07 13:06:40 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 434003 ***