[Bug 131679] Re: Crash inside doPoll()
** Changed in: compiz Status: Confirmed => Fix Released -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: Crash inside doPoll()
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 VogtMon, 14 Sep 2009 09:39:42 +0200 ** Changed in: compiz (Ubuntu) Status: Triaged => Fix Released -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: Crash inside doPoll()
** Branch linked: lp:compiz -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 131679] Re: Crash inside doPoll()
On Thu, Jun 25, 2009 at 12:17:10PM -, mykool wrote: > How does one un-subscribe? As you probably know, last week or so ago I > (I'm sure I'm not the only one) had my e-mail box bombed with bug > reports, it was absurd. This is not the kind of bug bomb I would hope > for.(LOL). Anyway I finally started marking it all as spam. This is > the first one to make it through since the bomb, and yet again - no > 'take my name off the list' option. What gives? How do I stop getting > mail from you guys? At the bottom of each mail you received, there is a link. Click on that link, then click on the "Unsubscribe" button. Or just click here: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/131679/+subscribe -- - mdz -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 131679] Re: Crash inside doPoll()
You log into the bugs.launchpad.net and unsubscribe from 'your' submitted bugs. It's easy but you will have to wait until the subscribers column populates. Once this happens you hit the '-' (minus sign). The problem last week or perhaps 2 weeks ago was that the majority of folks were responding with 'unsubscribe' and then getting mad and sending even more messages. I was surprised at the amount of people that continued to try this method for unsubscribe even after a launchpad admin informed them they had to log in. The problem is not the site it is the people who can't seem to read their instructions in the email. -- james On Thu, Jun 25, 2009 at 5:17 AM, mykool wrote: > How does one un-subscribe? As you probably know, last week or so ago I > (I'm sure I'm not the only one) had my e-mail box bombed with bug > reports, it was absurd. This is not the kind of bug bomb I would hope > for.(LOL). Anyway I finally started marking it all as spam. This is > the first one to make it through since the bomb, and yet again - no > 'take my name off the list' option. What gives? How do I stop getting > mail from you guys? > > --- On Thu, 6/25/09, Travis Watkins wrote: > > From: Travis Watkins > Subject: [Bug 131679] Re: Crash inside doPoll() > To: mykoo...@yahoo.com > Date: Thursday, June 25, 2009, 2:41 AM > > Just so people know (and sorry for the spam) every single duplicate of > this bug is probably actually a completely different problem. Crashing > in doPoll just means something went weird in compiz that didn't trip it > up until the next time it went through this function. I'm not sure how > all of these bugs ended up as duplicates (I know many/most were done > automatically by apport) but we should probably at least have a separate > bug for each action someone was performing when this happened. > > Also, unless someone finds the right magic to harden compiz to such > problems there is probably no good way to debug this problem since the > corruption of compiz state almost certainly happens at some early point > that could be quite some time ago. > > -- > Crash inside doPoll() > https://bugs.launchpad.net/bugs/131679 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in Compiz: Confirmed > Status in “compiz” package in Ubuntu: Triaged > Status in “gnome-screensaver” package in Ubuntu: Invalid > > Bug description: > Binary package hint: compiz > > compiz.real crashed with SIGSEGV > > this happens when the screen is locked, and you try to unlock it by > putting in your password. it accepts the password, blanks the field, > says 'checking' and spins the cursor...and never stops. bumping to high > importance, due to the likely amounts of data loss each time this > happens. > > ProblemType: Crash > Architecture: i386 > Date: Fri Aug 10 19:20:26 2007 > DistroRelease: Ubuntu 7.10 > ExecutablePath: /usr/bin/compiz.real > NonfreeKernelModules: nvidia > Package: compiz-core 1:0.5.2-0ubuntu1 > PackageArchitecture: i386 > ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --indirect-rendering > --sm-client-id default0 ccp > ProcCwd: /home/sharif > 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 0x08054b70 in ?? () > #1 0x0807b8f8 in ?? () > #2 0x0003 in ?? () > #3 0x00fa in ?? () > #4 0x in ?? () > StacktraceTop: > ?? () > ?? () > ?? () > ?? () > ?? () > Title: compiz.real crashed with SIGSEGV > Uname: Linux enigma 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 > GNU/Linux > UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev > powerdev scanner video > > -- > Crash inside doPoll() > https://bugs.launchpad.net/bugs/131679 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in Compiz: Confirmed > Status in “compiz” package in Ubuntu: Triaged > Status in “gnome-screensaver” package in Ubuntu: Invalid > > Bug description: > Binary package hint: compiz > > compiz.real crashed with SIGSEGV > > this happens when the screen is locked, and you try to unlock it by putting > in your password. it accepts the password, blanks the field, says 'checking' > and spins the cursor...and never stops. bumping to high importance, due to > the likely amounts of data loss each time this happens. > > ProblemType: Crash > Architecture: i386 > Date: Fri Aug 10 19:20:26 2007 > DistroRelease: Ubuntu 7.10 >
Re: [Bug 131679] Re: Crash inside doPoll()
You log into the bugs.launchpad.net and unsubscribe from 'your' submitted bugs. It's easy but you will have to wait until the subscribers column populates. Once this happens you hit the '-' (minus sign). The problem last week or perhaps 2 weeks ago was that the majority of folks were responding with 'unsubscribe' and then getting mad and sending even more messages. I was surprised at the amount of people that continued to try this method for unsubscribe even after a launchpad admin informed them they had to log in. The problem is not the site it is the people who can't seem to read their instructions in the email. - james On Thu, Jun 25, 2009 at 5:17 AM, mykool wrote: > How does one un-subscribe? As you probably know, last week or so ago I > (I'm sure I'm not the only one) had my e-mail box bombed with bug > reports, it was absurd. This is not the kind of bug bomb I would hope > for.(LOL). Anyway I finally started marking it all as spam. This is > the first one to make it through since the bomb, and yet again - no > 'take my name off the list' option. What gives? How do I stop getting > mail from you guys? > > --- On Thu, 6/25/09, Travis Watkins wrote: > > From: Travis Watkins > Subject: [Bug 131679] Re: Crash inside doPoll() > To: mykoo...@yahoo.com > Date: Thursday, June 25, 2009, 2:41 AM > > Just so people know (and sorry for the spam) every single duplicate of > this bug is probably actually a completely different problem. Crashing > in doPoll just means something went weird in compiz that didn't trip it > up until the next time it went through this function. I'm not sure how > all of these bugs ended up as duplicates (I know many/most were done > automatically by apport) but we should probably at least have a separate > bug for each action someone was performing when this happened. > > Also, unless someone finds the right magic to harden compiz to such > problems there is probably no good way to debug this problem since the > corruption of compiz state almost certainly happens at some early point > that could be quite some time ago. > > -- > Crash inside doPoll() > https://bugs.launchpad.net/bugs/131679 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in Compiz: Confirmed > Status in “compiz” package in Ubuntu: Triaged > Status in “gnome-screensaver” package in Ubuntu: Invalid > > Bug description: > Binary package hint: compiz > > compiz.real crashed with SIGSEGV > > this happens when the screen is locked, and you try to unlock it by > putting in your password. it accepts the password, blanks the field, > says 'checking' and spins the cursor...and never stops. bumping to high > importance, due to the likely amounts of data loss each time this > happens. > > ProblemType: Crash > Architecture: i386 > Date: Fri Aug 10 19:20:26 2007 > DistroRelease: Ubuntu 7.10 > ExecutablePath: /usr/bin/compiz.real > NonfreeKernelModules: nvidia > Package: compiz-core 1:0.5.2-0ubuntu1 > PackageArchitecture: i386 > ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --indirect-rendering > --sm-client-id default0 ccp > ProcCwd: /home/sharif > 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 0x08054b70 in ?? () > #1 0x0807b8f8 in ?? () > #2 0x0003 in ?? () > #3 0x00fa in ?? () > #4 0x in ?? () > StacktraceTop: > ?? () > ?? () > ?? () > ?? () > ?? () > Title: compiz.real crashed with SIGSEGV > Uname: Linux enigma 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 > GNU/Linux > UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev > powerdev scanner video > > -- > Crash inside doPoll() > https://bugs.launchpad.net/bugs/131679 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in Compiz: Confirmed > Status in “compiz” package in Ubuntu: Triaged > Status in “gnome-screensaver” package in Ubuntu: Invalid > > Bug description: > Binary package hint: compiz > > compiz.real crashed with SIGSEGV > > this happens when the screen is locked, and you try to unlock it by putting > in your password. it accepts the password, blanks the field, says 'checking' > and spins the cursor...and never stops. bumping to high importance, due to > the likely amounts of data loss each time this happens. > > ProblemType: Crash > Architecture: i386 > Date: Fri Aug 10 19:20:26 2007 > DistroRelease: Ubuntu 7.10 >
Re: [Bug 131679] Re: Crash inside doPoll()
How does one un-subscribe? As you probably know, last week or so ago I (I'm sure I'm not the only one) had my e-mail box bombed with bug reports, it was absurd. This is not the kind of bug bomb I would hope for.(LOL). Anyway I finally started marking it all as spam. This is the first one to make it through since the bomb, and yet again - no 'take my name off the list' option. What gives? How do I stop getting mail from you guys? --- On Thu, 6/25/09, Travis Watkins wrote: From: Travis Watkins Subject: [Bug 131679] Re: Crash inside doPoll() To: mykoo...@yahoo.com Date: Thursday, June 25, 2009, 2:41 AM Just so people know (and sorry for the spam) every single duplicate of this bug is probably actually a completely different problem. Crashing in doPoll just means something went weird in compiz that didn't trip it up until the next time it went through this function. I'm not sure how all of these bugs ended up as duplicates (I know many/most were done automatically by apport) but we should probably at least have a separate bug for each action someone was performing when this happened. Also, unless someone finds the right magic to harden compiz to such problems there is probably no good way to debug this problem since the corruption of compiz state almost certainly happens at some early point that could be quite some time ago. -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a direct subscriber of a duplicate bug. Status in Compiz: Confirmed Status in “compiz” package in Ubuntu: Triaged Status in “gnome-screensaver” package in Ubuntu: Invalid Bug description: Binary package hint: compiz compiz.real crashed with SIGSEGV this happens when the screen is locked, and you try to unlock it by putting in your password. it accepts the password, blanks the field, says 'checking' and spins the cursor...and never stops. bumping to high importance, due to the likely amounts of data loss each time this happens. ProblemType: Crash Architecture: i386 Date: Fri Aug 10 19:20:26 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/compiz.real NonfreeKernelModules: nvidia Package: compiz-core 1:0.5.2-0ubuntu1 PackageArchitecture: i386 ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --indirect-rendering --sm-client-id default0 ccp ProcCwd: /home/sharif 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 0x08054b70 in ?? () #1 0x0807b8f8 in ?? () #2 0x0003 in ?? () #3 0x00fa in ?? () #4 0x in ?? () StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: compiz.real crashed with SIGSEGV Uname: Linux enigma 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: Crash inside doPoll()
Just so people know (and sorry for the spam) every single duplicate of this bug is probably actually a completely different problem. Crashing in doPoll just means something went weird in compiz that didn't trip it up until the next time it went through this function. I'm not sure how all of these bugs ended up as duplicates (I know many/most were done automatically by apport) but we should probably at least have a separate bug for each action someone was performing when this happened. Also, unless someone finds the right magic to harden compiz to such problems there is probably no good way to debug this problem since the corruption of compiz state almost certainly happens at some early point that could be quite some time ago. -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: Crash inside doPoll()
Robert, how about not messing with duplicates' status until a solution can be found for the insane amount of notification emails you are causing to be sent out. I've literally been getting hundreds of notification emails for about the past day and so have many, many other people. -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: Crash inside doPoll()
For all of those that are trying to unsubcrive from this bug and cant (due to a Launchpad timeout bug on AJAX), please user the following URL: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/131679/+subscribe -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: Crash inside doPoll()
** Changed in: compiz Status: Unknown => Confirmed -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: Crash inside doPoll()
Bug 145360 and bug 191365 are duplicates of this. They each have 169 and 19 duplicates respectively. I don't seem to be able to mark them as duplicates without manually modifying all their own duplicates first. ** Bug watch added: Compiz Plugins / Config Bugs #864 http://bugs.opencompositing.org/show_bug.cgi?id=864 ** Also affects: compiz via http://bugs.opencompositing.org/show_bug.cgi?id=864 Importance: Unknown Status: Unknown ** Changed in: compiz (Ubuntu) Importance: Medium => High -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: Crash inside doPoll()
The stack trace shows the code iterating over a list of file descriptor structures and an iteration returning invalid memory (as shown in the many duplicates). Each file descriptor has an arbitrary callback attached to it. I'd bet a lot of money the bug is the list is being modified inside on of the callbacks. ** Summary changed: - compiz.real crashed with SIGSEGV when attempting to unlock screen + Crash inside doPoll() -- Crash inside doPoll() https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
