[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/607926
Title:
video players (totem, vlc) crash during video mode change when using
Xv and compiz
Status in “xorg-server” package in Ubuntu:
Expired
Bug description:
If video is playing during a video mode change, the player application
will crash, under certain conditions.
To reproduce: Using Lucid, nvidia drivers 195, and compiz. Play any
video in any video player, such as totem or compiz. While the video is
playing, change video mode, either via gnome-display-properties, or
xrandr (in some cases it may be necessary to change video mode twice).
The video player will crash.
What I expect to happen: The video player doesn't crash.
Notes: This only happens if compiz is in use; the bug is not present
with metacity. It only happens if Xv is used for video; if you turn
off Xv via gstreamer-properties, totem will not crash during mode
switch (although vlc still will; presumably, it ignores that
particular setting). This didn't happen under Jaunty with a similar
configuration, and so is a regression. So this looks like some ugly
interaction between Xv, compiz, and nvidia.
Additional note: The player will also crash if it is active during a
suspend-to-RAM/resume operation, presumably because resume involves a
video mode change. In that case, however, there is an additional
problem, which is that after the resume (only if a video player was
running at the time of suspend!), Xorg consumes huge amounts of RAM
and CPU time, and system responsiveness is seriously degraded,
requiring a complete system restart (restarting Xorg does not
suffice). I don't know if this is a different symptom of the same bug
or a separate bug.
The error message produced by totem when it crashes is:
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 507 error_code 11 request_code 133 minor_code 19)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
I will be happy to provide more detailed information of any sort.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/607926/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
