[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
I have a laptop acer aspire 1350 with chipset VIA KM400 and an LCD with a size of 1024x768, I added this line: Option "PanelSize" "1024x768" in the xorg.conf file in the device section and now I can use mplayer, vlc and totem with the XV driver without problems. I use the openchrome driver with svn revision 747. This is my "device" section in the xorg.conf file: Section "Device" Identifier "VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video" Driver "openchrome" Option "PanelSize" "1024x768" EndSection -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
Memory timings are really low. Make sure the memory timings are correct in the bios. If unsure, reset to factory defaults. -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
Could You please check if this error exists before? If yes, please check, in which revision this error appeared. For example to get revision 713 type: svn update -r713 Build instruction I described at: https://help.ubuntu.com/community/OpenChrome -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
Thanks. Let's wait and see what upstream comes back with. ** Tags added: videoplayback -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
Oh, sorry, stupid of me. Here's another gdb output with the symbols installed. But the gdb output gives me a symbol error in the end. #38 0xb7af04ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 No symbol table info available. dpkg -S gives me: gus...@gustav-laptop:~$ dpkg -S /lib/tls/i686/cmov/libpthread.so.0 libc6-i686: /lib/tls/i686/cmov/libpthread.so.0 The package libc6-i686-dbgsym and libc6-dbgsym are installed. I don't know what to do to get rid of those outputs. ** Attachment added: "gdb log dbgsym bt full" http://launchpadlibrarian.net/26430904/gdb.txt -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
Please attach the output of "bt full" once you hit the gdk_x_error breakpoint. Thanks. -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
Ok, great instructions! Here's the new log from gdb. This time from gdb's own logging. ** Attachment added: "gdb log with dgbsym installed" http://launchpadlibrarian.net/26414412/gdb.txt -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
You should be able to see both what you type and what gdb prints back, while also logging at the same time. Anyway, the gdb trace looks good except you're missing some debug symbols so you get a lot of stack frames like this: #1 0xb754b647 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 For fix this you need to install debug symbols for the package that ships the file, in this case "/usr/lib/libgdk-x11-2.0.so.0". You can find out which package that is by running "dpkg -S filename" and in this case: $ dpkg -S /usr/lib/libgdk-x11-2.0.so.0 libgtk2.0-0: /usr/lib/libgdk-x11-2.0.so.0 Which means that it ships in the libgtk2.0-0 package. Now, for most packages there is no -dbg package on the main repositories so you need to add the debug symbol repositories first. For jaunty you need to have these lines in source.list (just like a PPA basically): deb http://ddebs.ubuntu.com jaunty main restricted universe multiverse deb http://ddebs.ubuntu.com jaunty-updates main restricted universe multiverse deb http://ddebs.ubuntu.com jaunty-security main restricted universe multiverse deb http://ddebs.ubuntu.com jaunty-proposed main restricted universe multiverse Then run "sudo apt-get update" and after that you should have a special debug symbol package suffixed -dbgsym for all the packages in main. So in the case above you can now install: sudo apt-get install libgtk2.0-0-dbgsym You can read about the ddebs repo here: https://wiki.ubuntu.com/DebuggingProgramCrash This is a pretty powerful and very useful technique in general because it allows you to trace any crash in any Ubuntu software. --- Anyway, you need to install -dbgsym packages for all the .so files in your previous backtrace. After that run gdb again and attach the complete stacktrace both here and in the upstream bug report. -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
** Changed in: openchrome Status: Unknown => New -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
** Bug watch added: OpenChrome Trac #301 http://www.openchrome.org/trac/ticket/301 ** Also affects: openchrome via http://www.openchrome.org/trac/ticket/301 Importance: Unknown Status: Unknown -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
I added the PPA and ran sudo apt-get update and sudo apt-get upgrade I got in to X without any problems, so I guess the old bug (the one with the link in the first post) is squashed. But I still can't play video. I managed to figure out how to run GDB the way you like, I think at least. I ran GDB with logging. But I think the terminal output is nicer. Then you can see if I messed up any command, since I'm new to GDB. I'll head over to openchrome trac now and post the bug with all the info from here. ** Attachment added: "gdb_terminal_output.txt" http://launchpadlibrarian.net/26409120/gdb_terminal_output.txt -- XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) https://bugs.launchpad.net/bugs/372469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372469] Re: XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome)
** Summary changed: - Xv video output crashes player after upgrade to Jaunty + XV video crashes player on Jaunty (VIA KM400/KN400/P4M800, S3 UniChrome) ** Description changed: Binary package hint: xserver-xorg-video-openchrome I had some trouble with openchrome after upgrading to Jaunty. At first I couldn't get into X at all. But after applying a fix (https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/293326) I got it working. Now I can't play media with any of my media players. Totem, VLC or mplayer. The players crashes immediately after pressing play, well not mplayer, but it still doesn't play properly. Here's the terminal output with VLC: [] x11 video output error: X11 request 132.19 failed with error code 11: BadAlloc (insufficient resources for operation) X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 132 (XVideo) Minor opcode of failed request: 19 () Serial number of failed request: 83 Current serial number in output stream: 84 And Xorg.0.log says: (II) CHROME(0): ViaLCDPower: On. (II) CHROME(0): CH7xxxLCDPower: On (--) CHROME(0): CH7xxxLCDPower: [1]write 0x63 = 4B! (--) CHROME(0): CH7xxxLCDPower: [1]write 0x63 = B! (--) CHROME(0): CH7xxxLCDPower: [1]CH7019 PLL lock fail! (--) CHROME(0): CH7xxxLCDPower: [1]0x66 = 24! (--) CHROME(0): CH7xxxLCDPower: [2]write 0x63 = 4B! (--) CHROME(0): CH7xxxLCDPower: [2]write 0x63 = B! (--) CHROME(0): CH7xxxLCDPower: [2]CH7019 PLL lock fail! (--) CHROME(0): CH7xxxLCDPower: [2]0x66 = 24! (--) CHROME(0): CH7xxxLCDPower: [3]write 0x63 = 4B! (--) CHROME(0): CH7xxxLCDPower: [3]write 0x63 = B! (--) CHROME(0): CH7xxxLCDPower: [3]CH7019 PLL lock fail! (--) CHROME(0): CH7xxxLCDPower: [3]0x66 = 24! (--) CHROME(0): CH7xxxLCDPower: [4]write 0x63 = 4B! (--) CHROME(0): CH7xxxLCDPower: [4]write 0x63 = B! (--) CHROME(0): CH7xxxLCDPower: [4]CH7019 PLL lock fail! (--) CHROME(0): CH7xxxLCDPower: [4]0x66 = 20! (--) CHROME(0): CH7xxxLCDPower: [5]write 0x63 = 4B! (--) CHROME(0): CH7xxxLCDPower: [5]write 0x63 = B! (--) CHROME(0): CH7xxxLCDPower: [5]CH7019 PLL lock fail! (--) CHROME(0): CH7xxxLCDPower: [5]0x66 = 24! (--) CHROME(0): CH7xxxLCDPower: [6]write 0x63 = 4B! (--) CHROME(0): CH7xxxLCDPower: [6]write 0x63 = B! (--) CHROME(0): CH7xxxLCDPower: [6]CH7019 PLL lock fail! (--) CHROME(0): CH7xxxLCDPower: [6]0x66 = 24! (--) CHROME(0): CH7xxxLCDPower: [7]write 0x63 = 4B! (--) CHROME(0): CH7xxxLCDPower: [7]write 0x63 = B! (--) CHROME(0): CH7xxxLCDPower: [7]CH7019 PLL lock fail! (--) CHROME(0): CH7xxxLCDPower: [7]0x66 = 20! (--) CHROME(0): CH7xxxLCDPower: [8]write 0x63 = 4B! (--) CHROME(0): CH7xxxLCDPower: [8]write 0x63 = B! (--) CHROME(0): CH7xxxLCDPower: [8]CH7019 PLL lock fail! (--) CHROME(0): CH7xxxLCDPower: [8]0x66 = 20! (--) CHROME(0): CH7xxxLCDPower: [9]write 0x63 = 4B! (--) CHROME(0): CH7xxxLCDPower: [9]write 0x63 = B! (--) CHROME(0): CH7xxxLCDPower: [9]CH7019 PLL lock fail! (--) CHROME(0): CH7xxxLCDPower: [9]0x66 = 24! (--) CHROME(0): CH7xxxLCDPower: [10]write 0x63 = 4B! Totem in terminal gives me: /var/lib/python-support/python2.6/gdata/tlslite/utils/cryptomath.py:9: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha 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 92 error_code 11 request_code 132 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.) And totem Xorg.0.log Freed 12587008 (pool 2) Freed 13373440 (pool 2) Freed 12587008 (pool 0) Fulfilled via DRI at 12587008 Freed 13373440 (pool 0) Fulfilled via DRI at 13373440 And mplayer terminal: gus...@gustav-laptop:~$ mplayer -vo xv American.Dad.S04E18.REPACK.PDTV.XviD-DOT.avi MPlayer 1.0rc2-4.3.3 (C) 2000-2007 MPlayer Team CPU: Mobile AMD Athlon(tm) XP 2600+ (Family: 6, Model: 10, Stepping: 0) CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 0 Compiled with runtime CPU detection. mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing American.Dad.S04E18.REPACK.PDTV.XviD-DOT.avi. AVI file format detected. [aviheader] Video stream found, -vid 0 [aviheader] Audio stream found, -aid 1 VIDEO: [XVID] 512x384 12bpp 23.976 fps 1021.1 kbps (124.6 kbyte/s) xscreensaver_disable: Could not find XScreenSaver window. GNOME screensaver d
