GNOME Bugzilla – Bug 554043
crash in Rhythmbox Music Player: Subir el volumen.
Last modified: 2008-09-27 08:24:46 UTC
Version: 0.11.6 What were you doing when the application crashed? Subir el volumen. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Wed Sep 10 16:46:13 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 142852096 vsize: 142852096 resident: 46841856 share: 21630976 rss: 46841856 rss_rlim: 4294967295 CPU usage: start_time: 1222501908 rtime: 780 utime: 720 stime: 60 cutime:0 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0xb6553720 (LWP 5776)] [New Thread 0xb3c87b90 (LWP 5799)] [New Thread 0xb45abb90 (LWP 5798)] [New Thread 0xb1577b90 (LWP 5790)] [New Thread 0xb1d78b90 (LWP 5789)] [New Thread 0xb2579b90 (LWP 5788)] [New Thread 0xb2d7ab90 (LWP 5787)] [New Thread 0xb5f91b90 (LWP 5785)] [New Thread 0xb4e95b90 (LWP 5782)] 0xb7f00424 in __kernel_vsyscall ()
+ Trace 207439
Thread 5 (Thread 0xb1d78b90 (LWP 5789))
----------- .xsession-errors --------------------- TotemEmbedded-Message: totem_embedded_open_internal 'fd://0' is-browser-stream 1 start-play 1 TotemEmbedded-Message: BEFORE _open TotemEmbedded-Message: AFTER _open (ret: 1) TotemEmbedded-Message: Viewer state: PLAYING ** Message: OpenStream reply ** Message: NewStream mimetype 'video/x-ms-wmv' URL 'http://vida1.stileproject.com/dl/b42bdf8a4080be8f85056d4be64a9c88/48ddd4b0/sativa.wmv' ** Message: Should be dual type 'video/x-ms-asf', making sure now ** Message: Is not dual type 'video/x-ms-asf' ** Message: Is not playlist: totem_pl_parser_can_parse_from_data failed (len 1440) ** Message: totemGMPPlugin dtor [0xadc8f0d0] ** Message: totemPlugin dtor [0xa45b8940] ** Message: NP_Shutdown ** Message: totemGMPPlugin dtor [0xa58215e0] Cannot access memory at address 0xa Cannot access memory at address 0xa --------------------------------------------------
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 527572 ***