compiz.real crashed with SIGSEGV in doPoll()

In order to make a backtrace I looked at https://wiki.ubuntu.com/Backtrace, but I cannot work out how to start compiz under gdb. I went into the Appearance setting and changed 'Visual Effects' to 'None' and then tried these two ideas, neither of which worked:

duncan@duncan-laptop:~$ gdb compiz-core 2>&1 | tee gdb-compiz-core.txt
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
compiz-core: No such file or directory.
(gdb)

duncan@duncan-laptop:~$ gdb compiz 2>&1 | tee gdb-compiz.txt
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
"/usr/bin/compiz": not in executable format: File format not recognized
(gdb)

Tell me what to do and I'll try it.

StacktraceTop:doPoll (timeout=<value optimized out>) at ../../src/display.c:1434
eventLoop () at ../../src/display.c:1882
main (argc=7, argv=0xbfd0a8b4) at ../../src/main.c:441

Just to clarify an unclear issue... I installed Gutsy fresh from the 9/24 daily build. Updated to current, added the nvidia driver, and all the codecs and other "essential" stuff. All is working fine. Create new user, and log in. The desktop is oversized (1600x1400 on a 1280x1024 screen) and compiz crashed. So it is a issues on a clean install, not an upgrade issue. My files are in the dupe bug [Bug 146409]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, this compiz package is not from the official Ubuntu repositories, and as such is not supported here. Please report this bug upstream at [WWW] https://bugs.freedesktop.org/enter_bug.cgi?product=xorg . Thanks!

I closed the wrong set of bugs, sorry.

David: I'm a bit confused but I will assume that this bug is okay here for now. Any idea how we can get a real stack trace on this?

My Kubuntu 7.10 just crashed. The bug report says "Extra debug information will be added to the bug report automatically." I hope that's true. I also hope (but doubt) it has the stack trace.

MacBook 2nd generation Intel Duo Core 2.16 Ghz

 Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Hello

I just had this crash on my Ubuntu Hardy which is up-to-date as of 080222.

Confirmed due to bug 194273.

I've had it happen when using ctrl-alt-backspace to restart the window environment and also when restarting from hibernate

the same problem.when i used ctrl.alt.backspace to restart

I have the same problem changing the visual efects from "None" to "Normal" with compiled nvidia module.

when choosing a new screensaver, compiz crash

With NVIDIA, get XID error again with the hardy kernel and latest nvidia driver.
[54625.052083] NVRM: Xid (0001:00): 6, PE0000 0200 05000000 0000f848 00efebe7 03200000
[54637.292322] compiz.real[6190]: segfault at 2c08d rip 40feb0 rsp 7fffa4184690 error 4

Happens after acpi/gnome-power manager state change (i.e after ac plug/unplug) and even without statechange (i.e when screensaver kicks in etc).

This did not happen with 2.6.23 kernel with redhat patches.

sometimes compiz.real crashes just after the loading of all the OS....

Same problem, randomly:

2.6.24-16-generic 64bit, Feisty
Dual quad-core Intel Xeon E5335
NVidia Quadro FX 3450, 256MB
Restricted drivers 169.12
Two Dell 2407wfp monitors, 3840x1200 pixel total, 24 bit

I got this crash too when trying to enable compiz.

I didn't do anything else than start my computer and there it was ready to be sent...

NO idea whatsoever of why. But apport sent the report.

Restarted computer after doing latest updates. Using Intrepid Ibex Alpha 5 64 bit all updates applied.

I have this bug too, in 8.10 alpha 5

I just start my computer and there it was ready to be sent...

I've got this same bug everytime I boot.

Im having this problem in ubuntu 8.10

I can confirm this using up-to-date Intrepid. It happened when I started my computer and session today. I have set the desktop effects to normal. Those are still working btw.

problem in Ubuntu 8.10 when starting a 1TB HDD USB at a very slow laptop. I think its a reply timeout in combination with my slow laptop.

With 135 duplicates and Compiz being shipped by default I think it would be good if this bug had a bit more attention, or any attention. If anyone has a suggestion for how to get things moving or a request for more information please say so.

Hi Kjell,

I did it over once more. Same old, same old.

thomas@thomas-laptop:~$ gdb --args compiz.real --replace 2>&1 | tee gdb-compiz.real.txt
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 "i486-linux-gnu"...
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/compiz.real --replace
[Thread debugging using libthread_db enabled]
[New Thread 0xb7b426c0 (LWP 7634)]
/usr/bin/compiz.real (core) - Fatal: GLX_EXT_texture_from_pixmap is missing
/usr/bin/compiz.real (core) - Error: Failed to manage screen: 0
/usr/bin/compiz.real (core) - Fatal: No manageable screens found on display :0.0

Program exited with code 01.
(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.
(gdb) thread apply all backtrace
No registers.
(gdb) quit
thomas@thomas-laptop:~$

thomas@thomas-laptop:/var/crash$ lsb_release -rd ; uname -a ; apt-cache policy gnome-terminal compiz apport-gtk linux network-manager synaptic update-managerDescription: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686 GNU/Linux
gnome-terminal:
  Installed: 2.24.0-0ubuntu1
  Candidate: 2.24.0-0ubuntu1
  Version table:
 *** 2.24.0-0ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
compiz:
  Installed: 1:0.7.7+git20080807-0ubuntu12
  Candidate: 1:0.7.7+git20080807-0ubuntu12
  Version table:
 *** 1:0.7.7+git20080807-0ubuntu12 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
apport-gtk:
  Installed: 0.116
  Candidate: 0.116
  Version table:
 *** 0.116 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux:
  Installed: (none)
  Candidate: 2.6.27.4.4
  Version table:
     2.6.27.4.4 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
network-manager:
  Installed: 0.7~~svn20080928t225540+eni0-0ubuntu2
  Candidate: 0.7~~svn20080928t225540+eni0-0ubuntu2
  Version table:
 *** 0.7~~svn20080928t225540+eni0-0ubuntu2 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
synaptic:
  Installed: 0.62.1ubuntu9
  Candidate: 0.62.1ubuntu9
  Version table:
 *** 0.62.1ubuntu9 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
update-manager:
  Installed: 1:0.93.19
  Candidate: 1:0.93.19
  Version table:
 *** 1:0.93.19 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
thomas@thomas-laptop:/var/crash$

got this bug report (as said in the header on top) after second boot on 8.10 beta (new upgrade from 8.0.4)
at the screensaver section

Got the bug too with 8.10 beta some Secounds after the start of the gnome desktop and without starting of any extra application.

Got the bug too with 8.10 beta some Secounds after the start of the gnome desktop and without starting of any extra application. Compiz seems to restart immediately. I cant't see any visual indications of the crash. Only the notification of the apport system.

Same as Johanness, got the crash report without starting any app, there is no visual indication either.
Ubuntu 8.10 beta

Yes
Am Sonntag, den 05.10.2008, 15:33 +0000 schrieb Johannes Köster:
> Got the bug too with 8.10 beta some Secounds after the start of the
> gnome desktop and without starting of any extra application. Compiz
> seems to restart immediately. I cant't see any visual indications of the
> crash. Only the notification of the apport system.
>

every time I logon the compiz is not loaded (no WM) I have to manualy go to appearance and choose to enable effects... searches for drivers, and applies the compiz.

a dirty fixup for this (fighting effect rather than cause) is to use fusion-icon.
Add that to your gnome session and you get as a bonus a cute looking icon.

Bug #201849 and duplicates are crashing at doPoll, also.

I have no idea. Screen comes up, there is a crash icon. Only thing I notice is no connection to my router, but surely that is a different issue?

Same error, happens on login after x session starts up. Confirmed after updating all packages tonight.

I can confirm this. With the updates that came in this morning.

Confirmed just after installing the latest kernel, 2.6.27.6-generic.

me too,
8.10 updated + 2.6.24.6

compiz error appears after every login, but it doesn't aafect to the running compiz which works fine !

got the same since i updated my intrepid from alpha to now..., everything still works fine, just apport tells me compiz crashed...

Had this bug just now.
8.10 updated yesterday + 2.6.27.7
apport says it crashed, however compiz still seems to work.

I noticed a new update to compiz this morning in software update. So, went to change Visual Settings (in Appearance) to 'Normal', which used to kick this error off for me.

It doesn't any more. Yay.

It kicks this error off instead. Boo!
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/275054

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 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:~$

Please mark bug #279820 as public.

Also take a look at:

#145360
#280961
#183685

Problem appeared after updating to 0.7.8. Also I noticed a general choppyness after the update, even on scrolling and moving windows. It's not nice.

Hi, I have two crash reports on this one and it could be Kjell is on a holiday. Please give me instructions on how to obtain a backtrace and the right person to assign this to.

Please mark bug #279820 as public.

Also take a look at:

#145360
#280961
#183685
#282201

Is there anyone who can reproduce this in a reliable way? From what I can gather in this report it looks like:
a) the crash notification appears on login, but compiz works fine
b) it seems to happen after upgrade, does it then hapen on each login or just the first one?

I suspect it might be something that makes it crash during shutdown and/or because of upgrades/on-disk-changes. The w=0x1 in the backtrace is something that can only be explained by memory corruption. If someone can reproduce it in a reliable way, I can provide debug patches.

Thanks,
 Michael

@Michael,

Yes, the notification appears on login but compiz works fine. I'm not positive that it happens after an upgrade but it did happen again to me this morning after an upgrade and only on the first login.

Chris

1) Yes the crash happens on login, but compiz works.
2) It happens on both my hardy machines which I have upgraded. It doesn't only happen once but over and over again at login. Unfortunately it doesn't occur every time, it seems random.

Hi!

I could not reproduce it, but after the first few times it stopped for
me. Unfortunately until I turned off every desktop effects my windows
refresh was buggy... after a window change the content of the window was
some crap. (un)maximizing and mouse movements refreshed it.
I turned off all effects... everything "works" fine.

Bye!
 Einon

2008. 10. 13, hétfő keltezéssel 12.01-kor Michael Vogt ezt írta:
> Is there anyone who can reproduce this in a reliable way? From what I can gather in this report it looks like:
> a) the crash notification appears on login, but compiz works fine
> b) it seems to happen after upgrade, does it then hapen on each login or just the first one?
>
> I suspect it might be something that makes it crash during shutdown
> and/or because of upgrades/on-disk-changes. The w=0x1 in the backtrace
> is something that can only be explained by memory corruption. If someone
> can reproduce it in a reliable way, I can provide debug patches.
>
> Thanks,
> Michael
>

Hy, I tried to reproduce it in some ways, but it didn't work.
So error just appears on login after a upgrade + it doesn't happen on another compiz activated user on my laptop.

Maybe it's realted to a plugin??

Compiz reported crash immediately after login.
The only thing that I did was start a terminal and run powertop.

I had just rebooted after applying todays updates.

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 compiz.real ; 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
W: Unable to locate package compiz.real
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.

Got this signal on 8.10, clean install.

Did a 100% clean and straight install, rebooted, updated, rebooted - and the message was waiting. Firefox is the first program I'm using in 8.10 (except for the updating programs).

I just got confirmation via irc that the crash file roughly correlates with the logout time (but not on a compiz upgrade apparently).

Hi Michael,

I used to be able to reproduce this with 'sudo dpkg-reconfigure -aup low' (as described above), but with the current configuration (see below) this is no longer possible. I could not do a clean backtrace but Kjell Braden thought me a trick: 'thomas@thomas-laptop:~$ gdb --args compiz.real --replace 2>&1 | tee gdb-compiz.real.txt'. The problem is I am running a direct download now and this crash is fatal. Maybe with all the updates it will work now. I will try it in half an hour unless you beat me to it.

Cheers,

Thomas

My other (possibly related?) 'compiz.real crashed with SIGSEGV' bug is: Bug #183685.

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_logDescription: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-7-generic #1 SMP Tue Oct 14 18:40:44 UTC 2008 i686 GNU/Linux
linux:
  Installed: 2.6.27.7.9
  Candidate: 2.6.27.7.9
  Version table:
 *** 2.6.27.7.9 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
linux-image:
  Installed: 2.6.27.7.9
  Candidate: 2.6.27.7.9
  Version table:
 *** 2.6.27.7.9 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.11
  Candidate: 2.6.27-7.11
  Version table:
 *** 2.6.27-7.11 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-headers-generic:
  Installed: 2.6.27.7.9
  Candidate: 2.6.27.7.9
  Version table:
 *** 2.6.27.7.9 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-restricted-modules:
  Installed: 2.6.27.7.9
  Candidate: 2.6.27.7.9
  Version table:
 *** 2.6.27.7.9 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
compiz:
  Installed: 1:0.7.8-0ubuntu3
  Candidate: 1:0.7.8-0ubuntu3
  Version table:
 *** 1:0.7.8-0ubuntu3 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
thomas@thomas-laptop:~$

BTW Michael,

did you notice the following line in my .xsession-errors file?

/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format

Thanks,

Thomas

OK,

I also noticed that both this crash reports were incomplete:

Bug #145360:
    * Dependencies.txt (1006 bytes, text/plain; charset="utf-8")
    * Disassembly.txt (447 bytes, text/plain; charset="utf-8")
    * ProcMaps.txt (17.4 KiB, text/plain; charset="utf-8")
    * ProcStatus.txt (664 bytes, text/plain; charset="utf-8")
    * Registers.txt (444 bytes, text/plain; charset="utf-8")
    * ThreadStacktrace.txt (146 bytes, text/plain; charset="utf-8")

Bug #183685:
    * Dependencies.txt (1.0 KiB, text/plain; charset="utf-8")
    * Disassembly.txt (583 bytes, text/plain; charset="utf-8")
    * ProcMaps.txt (32.2 KiB, text/plain; charset="utf-8")
    * ProcStatus.txt (678 bytes, text/plain; charset="utf-8")
    * Registers.txt (1007 bytes, text/plain; charset="utf-8")
    * Stacktrace.txt (411 bytes, text/plain; charset="utf-8")
    * ThreadStacktrace.txt (438 bytes, text/plain; charset="utf-8")

I will attach two more crash files: my own Stacktrace and CoreDump.

The crash is still fatal:

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 "i486-linux-gnu"...
(no debugging symbols found)
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/compiz.real --replace
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb79e96c0 (LWP 19320)]
/usr/bin/compiz.real (core) - Fatal: GLX_EXT_texture_from_pixmap is missing
/usr/bin/compiz.real (core) - Error: Failed to manage screen: 0
/usr/bin/compiz.real (core) - Fatal: No manageable screens found on display :0.0

Program exited with code 01.
(gdb)
(gdb)
(gdb)
(gdb)
(gdb)
(gdb)
(gdb)
(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.
(gdb) thread apply all backtrace
No registers.
(gdb) quit

Hi,

strace worked,

but I doubt it contains usefull info.

Cheers,

Thomas

Hi,

there seem to be a couple of Xorg errors, maybe this is useful?

Cheers,

Thomas

Thomas, thanks for your efforts. We don't need most of the information
you post, we'll tell you when we want something more. For now, no
further action from your side is required.

hi

I was adjusting the settings in the sound preferences, the test window froze and while attempting to close it, the crash occurred

thanks

I can confirm this:

When you open volume control and adjust something, you can sometimes induce a crash. It looks like this thing is very similar to #252046 gvfs-hal-volume-monitor crashed with SIGSEGV in strlen().

Another way to induce a (fatal) crash is simply: ($ sudo compiz).

This could be due to my /home/$USER settings:

thomas@thomas-laptop:~$ ls -la ./.d*
-rwxrwxrwx 1 thomas thomas 51 2008-10-08 00:22 ./.devede
-rwxrwxrwx 1 thomas thomas 28 2008-10-15 21:29 ./.dmrc

./.dbus:
total 12
drwxrwxrwx 3 thomas root 4096 2008-10-03 00:57 .
drwxrwxrwx 69 thomas thomas 4096 2008-10-16 23:26 ..
drwxrwxrwx 2 thomas root 4096 2008-10-03 00:57 session-bus
thomas@thomas-laptop:~$ cd ./.db*/sess*
thomas@thomas-laptop:~/.dbus/session-bus$ ls -la
total 12
drwxrwxrwx 2 thomas root 4096 2008-10-03 00:57 .
drwxrwxrwx 3 thomas root 4096 2008-10-03 00:57 ..
-rwxrwxrwx 1 thomas root 463 2008-10-16 23:22 00e2e23118afd712ae53375648e55de3-0
thomas@thomas-laptop:~/.dbus/session-bus$ cat ./00*
# This file allows processes on the machine with id 00e2e23118afd712ae53375648e55de3 using
# display :0 to find the D-Bus session bus with the below address.
# If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will
# be used rather than this file.
# See "man dbus-launch" for more details.
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-inY1BQYKBn,guid=b48c171592d4350b2150d3d048f7be87
DBUS_SESSION_BUS_PID=6306
DBUS_SESSION_BUS_WINDOWID=4194305
thomas@thomas-laptop:~/.dbus/session-bus$

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 "i486-linux-gnu"...
(no debugging symbols found)
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/pulseaudio
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New process 7485]
Executing new program: /proc/7485/exe
/proc/7485/exe: Permission denied.
(gdb) backtrace full
#0 0xb80c07f0 in ?? ()
No symbol table info available.
(gdb) info registers
eax 0x0 0
ecx 0x0 0
edx 0x0 0
ebx 0x0 0
esp 0xbfad98d0 0xbfad98d0
ebp 0x0 0x0
esi 0x0 0
edi 0x0 0
eip 0xb80c07f0 0xb80c07f0
eflags 0x200292 [ AF SF IF ID ]
cs 0x73 115
ss 0x7b 123
ds 0x7b 123
es 0x7b 123
fs 0x0 0
gs 0x0 0
(gdb) thread apply all backtrace
/build/buildd/gdb-6.8/gdb/linux-nat.c:2467: internal-error: linux_nat_thread_alive: Assertion `is_lwp (ptid)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) /build/buildd/gdb-6.8/gdb/linux-nat.c:2467: internal-error: linux_nat_thread_alive: Assertion `is_lwp (ptid)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) (gdb) thread apply all backtrace
/build/buildd/gdb-6.8/gdb/linux-nat.c:2467: internal-error: linux_nat_thread_alive: Assertion `is_lwp (ptid)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) /build/buildd/gdb-6.8/gdb/linux-nat.c:2467: internal-error: linux_nat_thread_alive: Assertion `is_lwp (ptid)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) (gdb) quit
The program is running. Exit anyway? (y or n) Not confirmed.
(gdb) y
Undefined command: "y". Try "help".
(gdb) quit
The program is running. Exit anyway? (y or n) W: core-util.c: setpriority(): Permission denied
W: ltdl-bind-now.c: Failed to find original dlopen loader.
E: pid.c: Daemon already running.
E: main.c: pa_pid_file_create() failed.

While viewing online motion video using my onboard ATI 780G graphics chipset (ATI drivers), I went to view SCREENSAVER options where this error occured. The screensaver being viewed was GFlux. Maybe a crash between system drivers used when viewing video movement off internet and high intensive GFlux running at the same time.

crashed too frequently and it's an event even more frequent

it crashes each time after restart of the desktop but after all I don't see any issues,.....

Bug #277906 and duplicates are also crashing in doPoll.

Is this bug actually a duplicate of #131679? That's a very similar bug.

Ok, thanks. Any luck on getting it solved? It's kinda hard to work
when your system is always crashing

On Thu, 2009-02-05 at 14:17 +0000, Duncan Lithgow wrote:
> Is this bug actually a duplicate of #131679? That's a very similar bug.
>

I thought I marked as a duplicate. My problem went away after
rebooting. A very Microsoft solution, I know.

Dan

On Thu, Feb 5, 2009 at 10:53 AM, Jeeves_Moss <email address hidden> wrote:
> Ok, thanks. Any luck on getting it solved? It's kinda hard to work
> when your system is always crashing
>
>
> On Thu, 2009-02-05 at 14:17 +0000, Duncan Lithgow wrote:
>> Is this bug actually a duplicate of #131679? That's a very similar bug.
>>
>
> --
> compiz.real crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/145360
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Compiz: Confirmed
> Status in "compiz" source package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: compiz
>
> ProblemType: Crash
> Architecture: i386
> Date: Wed Sep 26 22:13:05 2007
> DistroRelease: Ubuntu 7.10
> ExecutablePath: /usr/bin/compiz.real
> NonfreeKernelModules: nvidia
> Package: compiz-core 1:0.5.2+git20070918-0ubuntu5
> PackageArchitecture: i386
> ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --loose-binding --sm-client-id default0 ccp
> ProcCwd: /home/duncan
> ProcEnviron:
> PATH=/home/duncan/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=en_DK.UTF-8
> SHELL=/bin/bash
> Signal: 11
> SourcePackage: compiz
> Stacktrace:
> #0 0x08054b7d in ?? ()
> #1 0x0807b908 in ?? ()
> #2 0x00000003 in ?? ()
> #3 0x000000fa in ?? ()
> #4 0x00000000 in ?? ()
> StacktraceTop:
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> Title: compiz.real crashed with SIGSEGV
> Uname: Linux duncan-laptop 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
> UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
>
> The different reports have different ideas of what triggers this bug, this is what happened to me when I first reported it:
> * Set Visual Effects to 'Normal'. Restarted X (CTRL+ALT+DEL) and it still worked, rebooted and it still worked.
> * Set Visual Effects to 'Extra'. Restarted X as above and it still worked, rebooted and it worked (it seems to still be working now) so I started Evolution as soon as I grabbed the top of the window to check the window wobble effect was working, then this crash. I must emphasize that compiz has not actually stopped and is still working. But something generated the crash report, so here it is:
>
>

It must be an automatic bug reporting of compiz, since I never posted the
bug manually. I even do not know what happened exactly, I only saw that
the crash was detected, but on my desktop it had no effect that I could
see. I'm only using the very basic features of compiz, nothing special. So
for me this bug has no importance. Hope it will not change to worse :-)

From:
Jeeves_Moss <email address hidden>
To:
<email address hidden>
Date:
02/05/2009 06:05 PM
Subject:
Re: [Bug 145360] Re: compiz.real crashed with SIGSEGV

Ok, thanks. Any luck on getting it solved? It's kinda hard to work
when your system is always crashing

On Thu, 2009-02-05 at 14:17 +0000, Duncan Lithgow wrote:
> Is this bug actually a duplicate of #131679? That's a very similar bug.
>

--
compiz.real crashed with SIGSEGV
https://bugs.launchpad.net/bugs/145360
You received this bug notification because you are a direct subscriber
of the bug.

Just got this crash report on Jaunty 9.04 AMD-64.
Just did some updates(50), restarted and got this just as the Desktop finished loading.

Is bug #277906 the same? With another 145(!) duplicates, and not yet connected to this one it seems likely. Although I have to admit I didn't take a closer look.

Yes, likely enough. Go ahead and close this duplicate submission from me.
Will refile if repeated closer to release.

/Stefan

On Sat, Mar 21, 2009 at 7:14 AM, Cruncher <email address hidden> wrote:

> Is bug #277906 the same? With another 145(!) duplicates, and not yet
> connected to this one it seems likely. Although I have to admit I didn't
> take a closer look.
>
> --
> compiz.real crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/145360
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Compiz: Confirmed
> Status in “compiz” source package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: compiz
>
> ProblemType: Crash
> Architecture: i386
> Date: Wed Sep 26 22:13:05 2007
> DistroRelease: Ubuntu 7.10
> ExecutablePath: /usr/bin/compiz.real
> NonfreeKernelModules: nvidia
> Package: compiz-core 1:0.5.2+git20070918-0ubuntu5
> PackageArchitecture: i386
> ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace
> --loose-binding --sm-client-id default0 ccp
> ProcCwd: /home/duncan
> ProcEnviron:
>
> PATH=/home/duncan/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=en_DK.UTF-8
> SHELL=/bin/bash
> Signal: 11
> SourcePackage: compiz
> Stacktrace:
> #0 0x08054b7d in ?? ()
> #1 0x0807b908 in ?? ()
> #2 0x00000003 in ?? ()
> #3 0x000000fa in ?? ()
> #4 0x00000000 in ?? ()
> StacktraceTop:
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> Title: compiz.real crashed with SIGSEGV
> Uname: Linux duncan-laptop 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT
> 2007 i686 GNU/Linux
> UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev
> powerdev scanner video
>
> The different reports have different ideas of what triggers this bug, this
> is what happened to me when I first reported it:
> * Set Visual Effects to 'Normal'. Restarted X (CTRL+ALT+DEL) and it still
> worked, rebooted and it still worked.
> * Set Visual Effects to 'Extra'. Restarted X as above and it still worked,
> rebooted and it worked (it seems to still be working now) so I started
> Evolution as soon as I grabbed the top of the window to check the window
> wobble effect was working, then this crash. I must emphasize that compiz has
> not actually stopped and is still working. But something generated the crash
> report, so here it is:
>

--
Stefan Lindmark
Mobile: +46 76 126 999 1

On Saturday 21 March 2009 08:14:56 Cruncher wrote:
> Is bug #277906 the same? With another 145(!) duplicates, and not
yet
> connected to this one it seems likely. Although I have to admit I didn't
> take a closer look.

I am sorry, but I don't use Ubuntu.

I use Arch Linux.

This is a duplicate of bug 131679

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