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 492778 - crash in Rhythmbox Music Player: I changed some keyboard ...
crash in Rhythmbox Music Player: I changed some keyboard ...
Status: RESOLVED DUPLICATE of bug 484988
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-02 17:36 UTC by tamcleay
Modified: 2007-11-03 08:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description tamcleay 2007-11-02 17:36:15 UTC
Version: 0.10.1

What were you doing when the application crashed?
I changed some keyboard shortcuts so that they don't clash with the EMACS GTK+ Keyboard theme distributed with GTK+, and then quit Rhythmbox. It crashed just after I chose quit.


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.23.1 #1 SMP Sun Oct 28 23:04:30 KGT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Retroified
Icon Theme: ROX-SVG

Memory status: size: 111894528 vsize: 111894528 resident: 43974656 share: 21127168 rss: 43974656 rss_rlim: 4294967295
CPU usage: start_time: 1193974454 rtime: 13083 utime: 12335 stime: 748 cutime:0 cstime: 2 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/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c7f6c0 (LWP 15832)]
[New Thread 0xb4953b90 (LWP 15843)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()


----------- .xsession-errors (3504 sec old) ---------------------
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
wrong wireless interface
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-11-03 08:04:43 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 484988 ***