Bug 493155 – crash in Rhythmbox Music Player:

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 493155 - crash in Rhythmbox Music Player:


Summary:	crash in Rhythmbox Music Player:


Status:	RESOLVED DUPLICATE of bug 484988

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.10.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-03 19:25 UTC by smietana
Modified:	2007-11-07 05:12 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description smietana 2007-11-03 19:25:31 UTC

Version: 0.10.1

What were you doing when the application crashed?



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

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: AluminumAlloy-Volcanic
Icon Theme: gnome

Memory status: size: 103858176 vsize: 103858176 resident: 45084672 share: 20434944 rss: 45084672 rss_rlim: 4294967295
CPU usage: start_time: 1194086434 rtime: 91845 utime: 87317 stime: 4528 cutime:0 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/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bd26c0 (LWP 4694)]
[New Thread 0xb680cb90 (LWP 4757)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 174939



----------- .xsession-errors (30 sec old) ---------------------
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-11-07 05:12:47 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 ***