Unity session crash when playing movie with any player except xbmc

[norberto]

Unity session crash when playing movie with any player except xbmc

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sat Feb 18 14:08:47 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 org.gnome.nautilus.window-state geometry '939x515+65+24'
 org.gnome.nautilus.window-state sidebar-width 286
 org.gnome.nautilus.window-state start-with-status-bar true
SourcePackage: nautilus
UpgradeStatus: Upgraded to precise on 2012-02-16 (1 days ago)

[norberto (netcaster)]

Workaround: open terminal, execute gnome-properties goto video tab, select output X Window System (without Xv)

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[norberto (netcaster)]

Ok if you prefer change the words crash session with unexpect closed session, for the users is only semantic, but the real problem comes when using Xv video output. I'm using updated precise development version. There no are any crash file related to this unity crash in /var/crash/ This is my xvinfo.

norberto@wall-e:~$ xvinfo
X-Video Extension version 2.2
screen #0
  Adaptor #0: "AMD Radeon AVIVO Video"
    number of ports: 4
    port base: 143
    operations supported: PutImage
    supported visuals:
      depth 24, visualID 0x23
      depth 24, visualID 0x24
      depth 24, visualID 0x25
      depth 24, visualID 0x26
      depth 24, visualID 0x27
      depth 24, visualID 0x28
      depth 24, visualID 0x29
      depth 24, visualID 0x2a
      depth 24, visualID 0x2b
      depth 24, visualID 0x2c
      depth 24, visualID 0x2d
      depth 24, visualID 0x2e
      depth 24, visualID 0x2f
      depth 24, visualID 0x30
      depth 24, visualID 0x31
      depth 24, visualID 0x32
      depth 24, visualID 0x33
      depth 24, visualID 0x34
      depth 24, visualID 0x35
      depth 24, visualID 0x36
      depth 24, visualID 0x37
      depth 24, visualID 0x38
      depth 24, visualID 0x39
      depth 24, visualID 0x3a
      depth 24, visualID 0x3b
      depth 24, visualID 0x3c
      depth 24, visualID 0x3d
      depth 24, visualID 0x3e
      depth 24, visualID 0x3f
      depth 24, visualID 0x40
      depth 24, visualID 0x41
      depth 24, visualID 0x42
      depth 24, visualID 0x43
      depth 24, visualID 0x44
      depth 24, visualID 0x45
      depth 24, visualID 0x46
      depth 24, visualID 0x47
      depth 24, visualID 0x48
      depth 24, visualID 0x49
      depth 24, visualID 0x4a
      depth 24, visualID 0x4b
      depth 24, visualID 0x4c
      depth 24, visualID 0x4d
      depth 24, visualID 0x4e
      depth 24, visualID 0x4f
      depth 24, visualID 0x50
      depth 24, visualID 0x51
      depth 24, visualID 0x52
      depth 24, visualID 0x53
      depth 24, visualID 0x54
      depth 24, visualID 0x55
      depth 24, visualID 0x56
      depth 24, visualID 0x57
      depth 24, visualID 0x58
      depth 24, visualID 0x59
      depth 24, visualID 0x5a
      depth 24, visualID 0x5b
      depth 24, visualID 0x5c
      depth 24, visualID 0x5d
      depth 24, visualID 0x5e
      depth 24, visualID 0x5f
      depth 24, visualID 0x60
      depth 24, visualID 0x61
      depth 24, visualID 0x62
      depth 24, visualID 0x63
      depth 24, visualID 0x64
      depth 24, visualID 0x65
      depth 24, visualID 0x66
      depth 24, visualID 0x67
      depth 24, visualID 0x68
      depth 24, visualID 0x69
      depth 24, visualID 0x6a
      depth 24, visualID 0x6b
      depth 24, visualID 0x6c
      depth 24, visualID 0x6d
      depth 24, visualID 0x6e
      depth 24, visualID 0x6f
      depth 24, visualID 0x70
      depth 24, visualID 0x71
      depth 24, visualID 0x72
    number of attributes: 10
      "XV_SET_DEFAULTS" (range 0 to 1)
              client settable attribute
      "XV_DOUBLE_BUFFER" (range 0 to 1)
              client settable attribute
              client gettable attribute (current value is 1)
      "XV_BRIGHTNESS" (range -1000 to 10...

[Omer Akram (om26er)]

you cannot confirm your own bugs, result of xvinfo are prolly not required for this bug report. I am not really sure what is the issue you want to report, could you make a video of that problem?

[norberto (netcaster)]

a) Sorry, I have not time to reproduce the bug again and take a video and may be you don't need a video, the bug is very clear.

Precise by default has the video output as auto in gstreamer-properties. that means that the output is auto selected between X11/Xv and X11/Shm.

As you can see in xvinfo has the right graphics support, but if you play any video on totem or vlc or mplayer the session is unexpectedly closed and go out to lightdm screen. This not happens with xbmc. This make me suspect about some bug that affect those players.

Later I discover that if we change the video output as X11/Shm (not Xv) on gstreamer-properties, all the players play any video without any trouble.

Seems as the Xv is selected on auto, because as you can see on xvinfo is supported, but when you make this parameter as auto or Xv in configuration, the session is unexpectedly closed and go to lightdm screen.

As you can understand, users sees as the unity session crash

[Omer Akram (om26er)]

try removing pulseaudio and restart and let us know if the issue happens still. sounds like bug 932096 but that's specific to armel.

[norberto (netcaster)]

Hi, I make this test

sudo apt-get purge pulseaudio*
sudo reboot

To test:
gstreamer-properties
select video tab
On default output complement I select X Window System (Without Xv)
Pipeline is ximagesink
Pushing Test output its OK

after
On default output complement I select
X Window System (X11/XShm/Xv)
Pipeline is xvimagesink
Pushing Test Unity Session is closed. The issue still alive and is not same as bug 932096.

[Kim Chee Leong (kc-leong)]

I believe I'm getting the same error. When I open a video using totem in precise I get a crash and the login-screen/lightdm is shown. I'm sure apport is enabled but no crash report is generated in /var/crash/. My hardware is a AMD E350 (CPU+GPU) with an integrated Radeon HD 6300.

In the xorg log a seg fault is shown, is this related to the crash when playing videos? I've included the xorg log in the attachments.

[norberto (netcaster)]

Hi Kim, would you be so good as to make this test?

open terminal and:

gstreamer-properties

select video tab

On default output complement select X Window System (Without Xv)
Pipeline must be ximagesink

Push Test output

if the test is ok and a bar graph appear stop the test and:

On default output complement select X Window System (X11/XShm/Xv)

Pipeline must be xvimagesink

Push Test again.

Thank's on advance.

[cain (streetgal)]

@norberto

I just upgraded to Precise and am having the same issue as well. X Window System (X11/XShm/Xv) logs me right out.

Thanks for the (temporary) workaround!

[Martin Niclasen (davsser)]

I can also comfrm norberto. With no xv i am able to play video. with xv i get logged out,

I would like to note this was first a problem when i installed catalyst driver. Thsi is my second install of bata 1 and second catalyst driver. With the standard driver I ould play video without log-out/crash

[ellis booker (ellisbooker)]

I can confirm this too. With X11/XShm/Xv I'm logged out. Would this explain the Skype crashes too?

[cain (streetgal)]

@ellis
Possibly. My Skype crashes too, in the middle of a video chat...

[Katsiaris Simos (spider623)]

i also have this problem but after i set it in no Xv it's working properly the strange thing was that i didn't have any problems in games or web so i thing is a wrong line in the amd's avivo source code or in the kernels header like the one in 11.10 where we could not start avivo

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Antti Kaijanmäki (kaijanmaki)]

I've witnessed the same problem. I managed to get a backtrace over ssh and attching GDB to the X process and then trying to watch a video with totem. I've also witnessed the same to happen with mplayer and vlc. Probably something to do with hardware accelerated video playback or scaling or something.

Anyway, it seems that the problem is in the proprieaty AMD video driver.

Program received signal SIGSEGV, Segmentation fault.
0x00007f4118798c72 in xs111LookupPrivate ()
   from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so
(gdb) bt
#0 0x00007f4118798c72 in xs111LookupPrivate ()
   from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so
#1 0x00007f411816b75d in xclLookupPrivate ()
   from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so
#2 0x00007f41147078de in X740XvPutImage ()
   from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/amdxmm.so
#3 0x00007f411c881bae in ?? ()
#4 0x00007f411988ccb2 in ?? ()
   from /usr/lib/xorg/modules/extensions/libextmod.so
#5 0x00007f411c829721 in ?? ()
#6 0x00007f411c81864a in ?? ()
#7 0x00007f411a99876d in __libc_start_main (main=0x7f411c8182b0, argc=10,
    ubp_av=0x7fff66145ef8, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fff66145ee8) at libc-start.c:226
#8 0x00007f411c81893d in _start ()

I tried to use gdb generate-core-file but the machine ended up dead locked. I could try again with serial console + crashkernel if that's any use, but as it's proprietary driver, I doubt it would be.

[Antti Kaijanmäki (kaijanmaki)]

I tried a second time by first stopping lightdm and then running startx from the console:

antti@beasty:~$ sudo stop lightdm
lightdm stop/waiting
antti@beasty:~$ sudo startx

 Now trying to play a video with mplayer X crashes in another place:

Program received signal SIGSEGV, Segmentation fault.
0x00007fd23fd148f6 in X740XvPutImage ()
   from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/amdxmm.so
(gdb) bt
#0 0x00007fd23fd148f6 in X740XvPutImage ()
   from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/amdxmm.so
#1 0x00007fd247e8ebae in ?? ()
#2 0x00007fd244e99cb2 in ?? ()
   from /usr/lib/xorg/modules/extensions/libextmod.so
#3 0x00007fd247e36721 in ?? ()
#4 0x00007fd247e2564a in ?? ()
#5 0x00007fd245fa576d in __libc_start_main (main=0x7fd247e252b0, argc=6,
    ubp_av=0x7ffffdcf05c8, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7ffffdcf05b8) at libc-start.c:226
#6 0x00007fd247e2593d in _start ()

And here's the output from startx:

X.Org X Server 1.11.3
Release Date: 2011-12-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-30-server x86_64 Ubuntu
Current Operating System: Linux beasty 3.2.0-18-generic #28-Ubuntu SMP Fri Mar 2 20:02:50 UTC 2012 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=a8bcb914-d443-415c-bc5c-395358d8e52a ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
Build Date: 08 March 2012 12:01:51AM
xorg-server 2:1.11.4-0ubuntu5 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.24.4
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 11 20:42:21 2012
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(WW) fglrx: No matching Device section for instance (BusID PCI:0@4:0:1) found
[- XMM_GLX] [I ]glesxXvInit Configureable RGBOutputColorRange

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x26) [0x7fd247f70206]
1: /usr/bin/X (0x7fd247de8000+0x18c0aa) [0x7fd247f740aa]
2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fd24710e000+0xfcb0) [0x7fd24711dcb0]
3: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/amdxmm.so (X740XvPutImage+0x146) [0x7fd23fd148f6]
4: /usr/bin/X (0x7fd247de8000+0xa6bae) [0x7fd247e8ebae]
5: /usr/lib/xorg/modules/extensions/libextmod.so (0x7fd244e8b000+0xecb2) [0x7fd244e99cb2]
6: /usr/bin/X (0x7fd247de8000+0x4e721) [0x7fd247e36721]
7: /usr/bin/X (0x7fd247de8000+0x3d64a) [0x7fd247e2564a]
8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7fd245fa576d]
9: /usr/bin/X (0x7fd247de8000+0x3d93d) [0x7fd247e2593d]
Segmentation fault at address 0xa4

Caught signal 11 (Segmentation fault). Server aborting

Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
Please also check the log file at "/var/lo...

[norberto (netcaster)]

I can comfirm that this bug report is a duplicate of bug #921384. Installing ATI Catalayst 12.2 fixes the problem for me.

[jonas antunes da silva (jonasconcordia)]

This problem affects me too. I'm using ubuntu 12.04 Beta and when I try to play any video, the session is closed and the login screen shows. The workaround shown by norberto solved the problem for me.