Bug 6331 - X crashes when push Volume button in Gnome Totem player
Summary: X crashes when push Volume button in Gnome Totem player
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 6.9.0
Hardware: x86 (IA32) FreeBSD
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords: have-backtrace
Depends on:
Blocks:
 
Reported: 2006-03-21 19:09 UTC by Oleg Lomaka
Modified: 2007-02-22 14:26 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Back trace (1.73 KB, text/plain)
2006-03-23 20:00 UTC, Oleg Lomaka
no flags Details
Xorg config file (2.16 KB, text/plain)
2006-03-23 20:04 UTC, Oleg Lomaka
no flags Details
Xorg log file (47.19 KB, text/plain)
2006-03-23 20:06 UTC, Oleg Lomaka
no flags Details

Description Oleg Lomaka 2006-03-21 19:09:19 UTC
If push Volume button in Totem player, X terminating with signal 11. This is
without DRM modules loaded (drm.ko & radeon.ko).

When modules loaded, i've managed to open volume control popup by pushing Volume
button several times. But at the end it terminated anyway.

#0  0x282d05da in memcpy () from /lib/libc.so.6
#1  0x286f15b4 in RADEONCopyData ()
   from /usr/X11R6/lib/modules/drivers/radeon_drv.so
#2  0x286f2836 in RADEONPutImage ()
   from /usr/X11R6/lib/modules/drivers/radeon_drv.so
#3  0x080ad588 in xf86XVPutImage ()
#4  0x2836a815 in XvdiPutImage ()
   from /usr/X11R6/lib/modules/extensions/libextmod.so
#5  0x2836d4ee in ProcXvShmPutImage ()
   from /usr/X11R6/lib/modules/extensions/libextmod.so
#6  0x08582800 in ?? ()
#7  0x082f38c0 in ?? ()
#8  0x08582f00 in ?? ()
#9  0x00000000 in ?? ()
Comment 1 Michel Dänzer 2006-03-22 21:22:41 UTC
Please try to get a backtrace with debugging symbols, and attach (as opposed to
paste) X server config and log files.
Comment 2 Oleg Lomaka 2006-03-23 20:00:49 UTC
Created attachment 5028 [details]
Back trace
Comment 3 Oleg Lomaka 2006-03-23 20:04:35 UTC
Created attachment 5029 [details]
Xorg config file
Comment 4 Oleg Lomaka 2006-03-23 20:06:58 UTC
Created attachment 5030 [details]
Xorg log file
Comment 5 Oleg Lomaka 2006-03-23 20:11:11 UTC
(In reply to comment #1)

> Please try to get a backtrace with debugging symbols, and attach (as opposed to
> paste) X server config and log files.

Ok, it's done. But this time i don't see messages like "Caught signal 11" at the
bottom of the log file.
Comment 6 Erik Andren 2006-03-26 02:23:25 UTC
Can you reproduce this problem in other movie players?
Comment 7 Oleg Lomaka 2006-03-26 02:58:17 UTC
(In reply to comment #6)
> Can you reproduce this problem in other movie players?

Nope. Actually this was music, not movie. I don't watch movies on this box. In
general i use xmms, but accidently open mp3 file with Totem and when decided to
tune a volume Xorg crashed with signal 11. I've reproduced this several times to
make sure this is X server error and post a bug. 

If it is important, i am able to try different players like mplayer and KDE's
one. But only on Monday. Is it needed?

BTW, totem works well untill you try to open volume-control box to tune it. So i
 am not sure it will reproduce in any other player.
Comment 8 Michel Dänzer 2006-03-28 19:13:00 UTC
Seems related to the driver's support for RGB XVideo formats, see e.g. bug 4640.
Comment 9 Michel Dänzer 2006-05-08 20:55:03 UTC
Does this still happen with xf86-video-ati CVS HEAD or the patch from bug 4640?
Comment 10 Timo Jyrinki 2007-02-22 14:26:57 UTC
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status.

Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.