compiz team mailing list archive

["James P. Carter" <james.p.carter@xxxxxxxxx>]

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<mykool_0@xxxxxxxxx> 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 <amaranth@xxxxxxxxxx> wrote:
>
> From: Travis Watkins <amaranth@xxxxxxxxxx>
> Subject: [Bug 131679] Re: Crash inside doPoll()
> To: mykool_0@xxxxxxxxx
> 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  0x00000003 in ?? ()
>  #3  0x000000fa in ?? ()
>  #4  0x00000000 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
> 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  0x00000003 in ?? ()
>  #3  0x000000fa in ?? ()
>  #4  0x00000000 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 compiz
packagers, which is subscribed to compiz in ubuntu.