compiz.real crashed with SIGSEGV

This crash has the same stack trace characteristics as bug #144785. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

Hi there Pedro,

Kjell Braden is not responding, possibly on a Holiday. I am reassigning all compiz.real bugs to you, since I do not know the developers of this package. I will also notify the launchpad team. This is obviously a very important bug. Cheers, Thomas.

thomas@thomas-laptop:~$ lsb_release -rd ; uname -a ; apt-cache policy linux linux-image linux-source-2.6.27 linux-headers-generic linux-restricted-modules compiz ; hwinfo +all log=hw_log
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-7-generic #1 SMP Fri Oct 10 03:55:24 UTC 2008 i686 GNU/Linux
linux:
  Installed: 2.6.27.7.8
  Candidate: 2.6.27.7.8
  Version table:
 *** 2.6.27.7.8 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
linux-image:
  Installed: 2.6.27.7.8
  Candidate: 2.6.27.7.8
  Version table:
 *** 2.6.27.7.8 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-source-2.6.27:
  Installed: 2.6.27-7.10
  Candidate: 2.6.27-7.10
  Version table:
 *** 2.6.27-7.10 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-headers-generic:
  Installed: 2.6.27.7.8
  Candidate: 2.6.27.7.8
  Version table:
 *** 2.6.27.7.8 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-restricted-modules:
  Installed: 2.6.27.7.8
  Candidate: 2.6.27.7.8
  Version table:
 *** 2.6.27.7.8 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
compiz:
  Installed: 1:0.7.8-0ubuntu2
  Candidate: 1:0.7.8-0ubuntu2
  Version table:
 *** 1:0.7.8-0ubuntu2 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
thomas@thomas-laptop:~$

This is reproducible by running '$ sudo dpkg-reconfigure -aup low' after a system update/upgrade. I use the update/upgrade command:

sudo apt-get -fy --force-yes update ; sudo apt-get -fy --force-yes upgrade ; sudo apt-get -fy --force-yes dist-upgrade ; sudo apt-get -fy --force-yes install ; sudo dpkg --configure -a ; sudo update-manager -c -d ; sudo synaptic

After you reboot the crash is presented through apport-gtk. Possibly dpkg-reconfigure xserver-xorg x-session-manager will suffice.

Hi Michael,

I think this is probably a copy of 145360. Can you mark this as a duplicate or as a new bug? If not, can you reassign this to a good triager like Kjell Braden or Pedro Villvicencio?

Thanks,

Thomas

I've just subscribed to this bug after the same problem, my compiz just crashed randomly after I changed some settings in Orca Screen Reader

I just had this same crash couple of minutes after booting from a live USB flash. The only thing I did was change the CD from the CD-ROM and connect a(nother) USB flash drive into the computer. I'm also attaching the var/crash file for compiz.real and copying the end what "dmesg" gave me at the terminal:

[ 69.979044] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/device:02/input/input6
[ 70.029529] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
[ 70.052976] acpi device:07: registered as cooling_device3
[ 70.054048] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:06/input/input7
[ 70.109278] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 70.151377] ACPI: AC Adapter [ACAD] (on-line)
[ 70.810542] iwl3945 0000:03:00.0: PCI INT A disabled
[ 70.811210] sdhci-pci 0000:05:06.1: SDHCI controller found [1180:0822] (rev 19)
[ 70.811230] sdhci-pci 0000:05:06.1: enabling device (0000 -> 0002)
[ 70.811240] sdhci-pci 0000:05:06.1: PCI INT B -> GSI 23 (level, low) -> IRQ 23
[ 70.812274] sdhci-pci 0000:05:06.1: Will use DMA mode even though HW doesn't fully claim to support it.
[ 70.812287] sdhci-pci 0000:05:06.1: setting latency timer to 64
[ 70.814364] mmc0: SDHCI controller on PCI [0000:05:06.1] using DMA
[ 70.814503] Yenta: CardBus bridge found at 0000:05:04.0 [17aa:3828]
[ 70.814539] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 70.814544] Yenta: Routing CardBus interrupts to PCI
[ 70.814553] Yenta TI: socket 0000:05:04.0, mfunc 0x01111c12, devctl 0x44
[ 71.045877] Yenta: ISA IRQ mask 0x0000, PCI irq 16
[ 71.045885] Socket status: 30000006
[ 71.045891] Yenta: Raising subordinate bus# of parent bus (#05) from #05 to #09
[ 71.045902] pcmcia: parent PCI bridge I/O window: 0x2000 - 0x2fff
[ 71.045908] cs: IO port probe 0x2000-0x2fff: clean.
[ 71.046382] pcmcia: parent PCI bridge Memory window: 0xd0100000 - 0xd01fffff
[ 71.046387] pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x53ffffff
[ 71.052957] Synaptics Touchpad, model: 1, fw: 6.3, id: 0x1a0b1, caps: 0xa04713/0x200000
[ 71.080814] ACPI: Battery Slot [BAT1] (battery present)
[ 71.130666] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input8
[ 71.612010] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 71.612046] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 71.949385] cs: IO port probe 0x100-0x3af: clean.
[ 71.951578] cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
[ 71.952553] cs: IO port probe 0x820-0x8ff: clean.
[ 71.953320] cs: IO port probe 0xc00-0xcf7: clean.
[ 71.954388] cs: IO port probe 0xa00-0xaff: clean.
[ 83.288161] Adding 1485972k swap on /dev/sda5. Priority:-1 extents:1 across:1485972k
[ 83.511190] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 84.870632] ACPI: WMI: Mapper loaded
[ 86.379676] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use)
[ 86.426207] apm: BIOS not found.
[ 86.519629] lp: driver loaded but no devices found
[ 86.558698] ppdev: user-space parallel port driver
[ 88.327657] cdrom: This disc doesn't have any tracks ...

This happened to me too, but compiz didn't actually crash.

Steps to produce
1. I just merely rebooted system after being on windows
2. logged into gnome like normal,
3. the crash had happened immediately.

I cannot reproduce this crash, it just happened this time.

No noticeable differences on my desktop after this crash.

delete my last post, I cannot obtain my crash log and I thought it was already included in my last post.

thomas@thomas-laptop:~$ lsb_release -rd ; uname -a ; apt-cache policy linux compiz libcanberra-gnome
Description: Ubuntu 8.10
Release: 8.10
Linux thomas-laptop 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 GNU/Linux
linux: 2.6.27.10.13
compiz: 1:0.7.8-0ubuntu4.1
libcanberra-gnome: 0.6-0ubuntu3 0

Just booted this morning, came back to PC and found this crash. Running off live USB startup disk. PC was running Windoze last.

Just booted into ubuntu this morning, crash happens immediately after desktop loaded. no dual boot, only default gnome application running.

this problem is very annoying... hope it can be fixed as soon as possible.

thanks

For me crash also happens right after booting.

After some updating the problem seems to have gone away...

On Tue, Jan 27, 2009 at 12:50 PM, spitfire <email address hidden>wrote:

> For me crash also happens right after booting.
>
> --
> compiz.real crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/279820
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "compiz" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: compiz
>
> No idea. Something crashed and then wireless networking wasn't working.
> Rebooted and crash report came up and here I am. Nothing seems busted.
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/compiz.real
> Package: compiz-core 1:0.7.7+git20080807-0ubuntu13
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace
> --indirect-rendering core ccp
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> Signal: 11
> SourcePackage: compiz
> Stacktrace: #0 0x08055bed in ?? ()
> StacktraceTop: ?? ()
> ThreadStacktrace:
>
> Title: compiz.real crashed with SIGSEGV
> Uname: Linux 2.6.27-6-generic i686
> UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev
> vboxusers video
>

--
* * * *
Rob Maurer
508.648.5254 voice
508.833.0945 work
253.276.5340 fax
<email address hidden>

Crash always after the boot.

seems harmless. Never actually noticed any failures, everything still works. Can ya just make the crash report go away? ;-)

Simply hiding the crash report does not seem like a good solution to me. A better question is: why is there a crash report if it appears as if everything is still working correctly?

Does the problem still occur on Jaunty with Compiz 1:0.7.9+git20090211-0ubuntu4 ?

yes, this is with Jaunty and all updates applied. Seems to have
started after an update from yesterday because it wasn't happening
last week.

I no longer can reproduce as I had to go back to 810 for other issues.

Thank you for the help.

Eric.
-----Original Message-----
From: itismike <email address hidden>
Reply-to: Bug 279820 <email address hidden>
To: <email address hidden>
Subject: Re: [Bug 279820] Re: compiz.real crashed with SIGSEGV
Date: Mon, 16 Feb 2009 12:30:24 -0000

yes, this is with Jaunty and all updates applied. Seems to have
started after an update from yesterday because it wasn't happening
last week.

Compiz crashed multiple times on my laptop. After the last update it did become better, but it ain't good yet.

It freezes a lot and the screen is flashing. Sometimes it crashes right away, sometimes it takes a while.

Running Jaunty on Acer 5715z

I have Jaunty Jackalope in a IBM T43. it also crashed as soon it finished booting.

Running Jaunty kernel 2.6.28-8-generic #24-Ubuntu SMP Wed Feb 18 20:36:18 UTC 2009 x86_64 GNU/Linux with all updates, distribution updates installed. After rebooting this error was displayed via crash handler.
Running top shows compiz.real is running and using less than 1.5% of cpu and memory resources since the crash and compiz is still working fine.

One thing I've just noticed is that there's no longer a Quit option is the System menu.

This crash occurred during a routine update.

As above. I sent an 'instant ' crash report, but don't know where the log files have gone that generated with that. If you need any config files etc. please contact me.

Logfiles are in /var/crash

Attached mine.

I haven't seen Compiz in Preferences for a couple of days. Running Jaunty Alpha 5. Just updated - including latest Linux headers and Amarok and had a crash report after the required restart.

Jaunty Alpha 5 64 bits. Like Christopher, I got the crash after the required restart.

Same here, required reboot after update and it crashed... Was going to submit another report but didn't when I found this report.

You shouldn't attach raw .crash reports, as they may contain sensitive information. Removed attachments.

Has anyone discovered steps that always reproduce this issue?

Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report.

I looked through the report first, of course. Apport has the ability to send these and warns you about information leakage as well, so removing mine was unecessary and not called for at all. Also: I am pretty sure the report you removed included a backtrace.

I am not sure removing all the debugging info and setting this to "incomplete" made sense...

.crash files should only be submitted through apport, they should not be attached to existing bugs.

Unless you had the relevant debug symbols installed at the time of the crash, then it would have been an incomplete backtrace. By following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash you can first install the correct debug symbols used to obtain a complete backtrace. This is what the developers will find useful in helping to pinpoint the issue.

Thanks for your help.

Fair enough.

Re: ".crash files should only be submitted through apport, they should not be attached to existing bugs." Is it really so hard explaining why instead of stating the mere fact again and again? I will remember it for the future, but it makes no sense to me without any explanation.

Same problem here. Always just after log-in in gnome, but compiz is still running:

ps -eo command|grep compiz
/bin/sh /usr/bin/compiz
/usr/bin/compiz.real --ignore-desktop-hints --replace --indirect-rendering core ccp

$ ps -eo command|grep compiz
compiz.real --replace --sm-disable --ignore-desktop-hints ccp --loose-binding
grep compiz

I get crashes from both start up, and while using during the day, forcing me to reload compiz.

Architecture: amd64
DistroRelease: Ubuntu 9.04
MachineType: To Be Filled By O.E.M. S37S
NonfreeKernelModules: nvidia
Package: compiz 1:0.8.2-0ubuntu5
PackageArchitecture: all
ProcCmdLine: root=UUID=a8aa4adb-b3e6-4e1d-b4ad-e6cd704788b2 ro
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.28-11.37~lp330814crimsun1-generic
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom davfs2 dialout dip fax floppy fuse kvm lpadmin nagios netdev plugdev polkituser sambashare scanner sudo sys syslog tape users video voice www-data

Setting this back to Incomplete status, as a backtrace has been requested but not yet provided. Again:

Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

local retrace from bug 347869

$ gdb /usr/bin/compiz.real CoreDump
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/libXcomposite.so.1...done.
Loaded symbols for /usr/lib/libXcomposite.so.1
Reading symbols from /usr/lib/libXdamage.so.1...done.
Loaded symbols for /usr/lib/libXdamage.so.1
Reading symbols from /usr/lib/libXfixes.so.3...done.
Loaded symbols for /usr/lib/libXfixes.so.3
Reading symbols from /usr/lib/libXrandr.so.2...done.
Loaded symbols for /usr/lib/libXrandr.so.2
Reading symbols from /usr/lib/libXinerama.so.1...done.
Loaded symbols for /usr/lib/libXinerama.so.1
Reading symbols from /usr/lib/libXcursor.so.1...done.
Loaded symbols for /usr/lib/libXcursor.so.1
Reading symbols from /usr/lib/libICE.so.6...done.
Loaded symbols for /usr/lib/libICE.so.6
Reading symbols from /usr/lib/libSM.so.6...done.
Loaded symbols for /usr/lib/libSM.so.6
Reading symbols from /usr/lib/libxslt.so.1...done.
Loaded symbols for /usr/lib/libxslt.so.1
Reading symbols from /usr/lib/libxml2.so.2...done.
Loaded symbols for /usr/lib/libxml2.so.2
Reading symbols from /usr/lib/libstartup-notification-1.so.0...done.
Loaded symbols for /usr/lib/libstartup-notification-1.so.0
Reading symbols from /usr/lib/libGL.so.1...done.
Loaded symbols for /usr/lib/libGL.so.1
Reading symbols from /lib/libm.so.6...Reading symbols from /usr/lib/debug/lib/libm-2.9.so...done.
done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libc.so.6...Reading symbols from /usr/lib/debug/lib/libc-2.9.so...done.
done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /usr/lib/libX11.so.6...done.
Loaded symbols for /usr/lib/libX11.so.6
Reading symbols from /usr/lib/libXext.so.6...done.
Loaded symbols for /usr/lib/libXext.so.6
Reading symbols from /lib/libdl.so.2...Reading symbols from /usr/lib/debug/lib/libdl-2.9.so...done.
done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/libXrender.so.1...done.
Loaded symbols for /usr/lib/libXrender.so.1
Reading symbols from /lib/libuuid.so.1...done.
Loaded symbols for /lib/libuuid.so.1
Reading symbols from /lib/libz.so.1...done.
Loaded symbols for /lib/libz.so.1
Reading symbols from /usr/lib/libGLcore.so.1...done.
Loaded symbols for /usr/lib/libGLcore.so.1
Reading symbols from /usr/lib/tls/libnvidia-tls.so.1...done.
Loaded symbols for /usr/lib/tls/libnvidia-tls.so.1
Reading symbols from /lib/ld-linux-x86-64.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.9.so...done.
done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /usr/lib/libxcb.so.1...done.
Loaded symbols for /usr/lib/libxcb.so.1
Reading symbols from /usr/lib/libXau.so.6...done.
Loaded symbols for /usr/lib/libXau.so.6
Reading symbols from /usr/lib/libXdmcp.so.6...done.
Loaded symbols for /usr/lib/libXdmcp.so.6
Reading symbols from /usr/...

Looks like the backtrace has been provided (and if it's insufficient, no explanation to that effect has been given)

It happens to me too. It happens only after the screen comes back from sleep.
After a restart everything comes back to normal.
I can reproduce it easily.

If you need the crash file (12MB) just tell me.

Cheers Marko.

This bug was fixed in the package compiz - 1:0.8.3+git20090914-0ubuntu1

---------------
compiz (1:0.8.3+git20090914-0ubuntu1) karmic; urgency=low

  * Pre-Version of the upcomming 0.8.4 bugfix release
    - fixes crashes LP: #268683, #284362, #346391, #351878, #352037, #380338
    - fixes crashes on 64bit arches due to issue in va_list use
    - fixes at least some of the doPoll/eventLoop crashes reported in
      LP: #131679, #145360, #279820
    - likely fixes crashes LP: #340428 and #360643
    - fixes placing of dialogs (e.g. PolicyKit) behind currently focused
      window (LP: #165161)
    - fixes placing of new windows behind fullscreen window (LP: #153676)
    - fixes wobbly bouncing near panel and screen edges (LP: #153374)
    - screenshot plugin now saves to the correct desktop directory by default
      (LP: #175116)
    - lowering a window now activates the topmost window, unless
      click-to-focus is off (LP: #122507)
    - fixes inconsistent icon sizes in switcher, ring, shift, staticswitcher
      plugins
    - fixes some memory leaks
    - texture compression is now off by default due to texture quality issues
    - ported KDE4 window decorator to KDE 4.3
  * debian/control:
    - add versionized dependency on compiz-wrapper from
      compiz-core

compiz (1:0.8.3+git20090907-0ubuntu1~ppa1) karmic; urgency=low

  * new git snapshot

compiz (1:0.8.3+git20090904-0ubuntu1~ppa2) karmic; urgency=low

  [ Travis Watkins ]
  * debian/compiz-manager:
    - set COMPIZ_PLUGINS to plugins we want to always have enabled

  [ Saïvann Carignan ]
  * debian/compiz-gnome.gconf-defaults: Re-enable desktop switching by
    default as it has been fixed by appropriate GNOME schemas. (LP: #414170)

compiz (1:0.8.3+git20090904-0ubuntu1~ppa1) karmic; urgency=low

  * new git snapshot:
    - fixes segfaults on 64bit arches
    - warning fixes
    - avoid adding core twice

compiz (1:0.8.3+git20090831-0ubuntu1) karmic; urgency=low

  [ Michael Vogt ]
  * new git snapshot with fixes from 0.8 branch:
    - fix stacking below problem with the polkit1 dialog
    - fixes doPoll() crash (LP: #131679)
    - many more bugfixes
  * debian/control:
    - add "Provides: x-window-manager" to the compiz package
      (LP: #364242)

  [ Robert Ancell ]
  * debian/control:
  * debian/rules:
    - Build a compiz-dbg package (LP: #420321)

 -- Michael Vogt <email address hidden> Mon, 14 Sep 2009 09:39:42 +0200