compiz crashes with segfault after recent updates

Bug #1282342 reported by Doug Smythies on 2014-02-20
This bug affects 7 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)

Bug Description

My Ubuntu Desktop 14.04 VM became unusable (unity shell) a few days ago, and after some significant updates.
Things are fine after I log in and until I try to do something. Then compiz will crash and my system becomes unusable. I do have sshd running and can connect via ssh to re-boot or shurdown or get new updates are whatever.

This bug report is being sent while logged on with GNOME shell, which also has been having issues since January 17th, ( see bug 1273276 ) but there is a workaround that allows me to use it.

For the last few days, I see log entries in both kern.log and syslog saying about compiz complaing about segfaults.

Everything was working fine for unity log in until a few days ago. (well, and as expected during the development phase, there have been issues.)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140218.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3
Uname: Linux 3.13.0-10-generic x86_64

ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
CurrentDmesg: [ 122.391354] init: plymouth-stop pre-start process (3894) terminated with status 1
Date: Wed Feb 19 16:57:06 2014
DistUpgraded: 2013-11-17 13:21:47,309 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2013-09-04 (168 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-10-generic root=UUID=4d6f0b17-9e14-4801-ab59-a7737cde6271 ro quiet splash
Renderer: Software
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2013-11-17 (94 days ago) 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: Bochs
dmi.sys.vendor: Bochs
version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Feb 19 16:55:20 2014
xserver.configfile: default
 input Power Button KEYBOARD, id 6
 input AT Translated Set 2 keyboard KEYBOARD, id 7
 input ImExPS/2 Generic Explorer Mouse MOUSE, id 8
 open /dev/dri/card0: No such file or directory
 open /dev/fb0: No such file or directory
 vmware(0): Failed to open drm.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log

xserver.version: 2:1.15.0-1ubuntu6

Doug Smythies (dsmythies) wrote :
Doug Smythies (dsmythies) wrote :

Just a screen shot I captured one time.

Doug Smythies (dsmythies) wrote :
Doug Smythies (dsmythies) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in unity (Ubuntu):
status: New → Confirmed
Jens (jens-launchpad-net) wrote :

See also #1283671.

Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Doug Smythies (dsmythies) wrote :

I had the trusty daily iso from 2014.02.15. It installs and runs fine.
I'm saying that this issue was introduced on approximately 2014.02.16 or 2014.02.17
The bug 1283671 referred to above says 2014.02.21, but I think it was a few days prior.

Doug Smythies (dsmythies) wrote :

These are the commands I used to create and install new VM's today:

1.) Using daily iso from 2014.02.15 (works fine)

sudo virt-install -n desk_tt2 -r 8192 --disk path=/media/newhd/desk_tt2.img,bus=virtio,size=50 -c trusty-desktop-amd64-20140215.iso --network bridge=br0,model=virtio --video=vmvga --graphics vnc,listen= --noautoconsole -v --vcpus=4

2.) Using daily iso from 2014.02.24 (does not work due to issues of this bug report)

sudo virt-install -n desk_tt -r 8192 --disk path=/media/newhd/desk_tt.img,bus=virtio,size=50 -c trusty-desktop-amd64-20140224.iso --network bridge=br0,model=virtio --video=vmvga --graphics vnc,listen= --noautoconsole -v --vcpus=4

Doug Smythies (dsmythies) wrote :

The bug 1283671 is for a 32 bit installation. My 32 bit trusty VM has this issue also.

I have also tried: One CPU instead of four; Less memory, down to 2 gigabytes; The cirrus video driver instead of vmvga.

Without a stack trace from the coredump, we cannot be sure what is causing this crash. I have a feeling this is the same crash that is afflicting many users (myself included), but as I said, without the stack trace, I cannot be sure.

Until you can provide a valid stack trace of your failure, I'm going to mark this Incomplete. If you do produce one, you can update this bug, and I will look over it.

Changed in unity (Ubuntu):
status: Confirmed → Incomplete
importance: Undecided → High
Doug Smythies (dsmythies) wrote :

This is the entire file, and I assume contains what you want. Otherwise just let me know, I'll to anything to help with this.

Hi Doug,

Thanks for attaching the full crash file. I took a look over it, but unfortunately, the stack trace has no good information in it, so I still can't determine what the cause of the crash is.

If you get another crash, perhaps we can get a little better information from the core dump.

Doug Smythies (dsmythies) wrote :

Well thanks very much for looking. I actually have several of those files from about 4 different VM's.
For whatever reason those files do not get generated for every occurrence of the issue.
Since posting the full file earlier, I have been learning about how to use apport-retrace (and gdb) to extract the stack trace for myself, so maybe I can eventually come back with something useful. So far it isn't working though.

My system seems to have hung again while "installing extra package compiz-core to get Executable path", or similar the terminal window has actually disappeared now. However, I did get this just now and via a SSH session:

Core was generated by `compiz'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f75e06e9c24 in __memmove_sse2 (dest=0x26a8d7e0, src=<optimized out>, len=973293064) at ../string/memmove.c:99
99 ../string/memmove.c: No such file or directory.

I'll also add an attachment in a minute, but I have to delete the cor dump becuase the file is over 50 megabytes..

Doug Smythies (dsmythies) wrote :

This time including the entire file, while still a large file it is much smaller than the last one with the core dump included.

Hi Doug,

Thanks for digging into this. There is enough info in your last attachment to determine this is a duplicate of bug #1284536 and I'm going to mark it as such. I saw some chatter on IRC that this could be an issue in Mesa.

To post a comment you must log in.