Please attach 'lspci -vvnn' and Xorg.log (just after start, after run
Totem, after run Mplayer).
--
Xv video output crashes player after upgrade to Jaunty
https://bugs.launchpad.net/bugs/372469
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi gustav-brogren,
Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log
(and maybe Xorg.0.log.old) file from after reproducing this issue. If you've
made any customizations to your /etc/X11/xorg.conf please attach that as well.
[This is an automated message.
Here's Xorg.0.log after boot.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/26400074/Xorg.0.log
--
Xv video output crashes player after upgrade to Jaunty
https://bugs.launchpad.net/bugs/372469
You received this bug notification because you are a member of Ubuntu
Bugs, which
Here's xorg.conf, which is the default one.
** Attachment added: xorg.conf
http://launchpadlibrarian.net/26400034/xorg.conf
--
Xv video output crashes player after upgrade to Jaunty
https://bugs.launchpad.net/bugs/372469
You received this bug notification because you are a member of Ubuntu
Here's lspci -vvnn.
** Attachment added: lspci -vvnn.txt
http://launchpadlibrarian.net/2645/lspci%20-vvnn.txt
--
Xv video output crashes player after upgrade to Jaunty
https://bugs.launchpad.net/bugs/372469
You received this bug notification because you are a member of Ubuntu
Bugs, which
Xorg.o.log, trying to play video in VLC directly after boot.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/26400409/Xorg.0.log
--
Xv video output crashes player after upgrade to Jaunty
https://bugs.launchpad.net/bugs/372469
You received this bug notification because you are a
And finally Xorg.0.log after boot and trying to play video in Totem.
(I made a little typo above, but I can't a way to edit the posts)
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/26400635/Xorg.0.log
--
Xv video output crashes player after upgrade to Jaunty
@Gustav, can you please run totem under gdb and obtain a backtrace so we
can see in what function it crashes? If it just exits instead of dying
on a signal you can usually put a breakpoints on exit, gdk_x_error
and abort. You might also need to run totem with the --sync
parameter. If you are able
