For the record, I can't reproduce it either.
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
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.
--
des
** Changed in: compiz (Ubuntu)
Importance: High => Medium
Assignee: Ken VanDine (ken-vandine) => (unassigned)
** Tags added: ct-rev
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you a
I just tried to reproduce this with jaunty on my i386 box with a Intel
G965 graphics card, didn't crash. I also tested on my jaunty amd64
laptop with Intell 4500 graphics, didn't crash.
Is anyone able to reproduce this with jaunty?
--
compiz.real crashed with SIGSEGV when attempting to unlock s
ken - can you please take a look?
** Changed in: compiz (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => Ken VanDine
(ken-vandine)
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notifica
** Changed in: compiz (Ubuntu)
Assignee: compiz packagers (compiz) => Canonical Desktop Team
(canonical-desktop-team)
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ub
** Changed in: compiz (Ubuntu)
Status: Confirmed => Triaged
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
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-screensav
I was wandering why my lock screen shortcut (Ctrl+Alt+Break) stoped
working in Intrepid. I had the System -> Preferences -> Keyboard
Shortcuts dialogue active when the crash notification poped up. I'm not
sure if I actually pressed my key combination. BTW, I had to change the
shortcut to Ctrl+Alt+S
Sounds like bug 145360 and another 129 duplicates are duplicates too.
Opinions?
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gn
Bug 191365 seems to be a duplicate of this one and it has another 18
duplicates.
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to g
I got this problem when I tried to wake the screen (running on a
Presario V6000, nVidia GeForce Go chipset) I restarted the X server
(loosing some data) and found that compiz crashed when I logged back
in. I can reproduce this reliably if it'll be a help to anyone...just
tell me what you need. (
sometimes when I reboot X server copiz crashes. I dont think it ever
crashes after a full restart.
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Apport has marked my Compiz bug as a dupe of this one. I get it
intermittently when switching virtual workspaces (ctrl+alt+arrows).
Unfortunately I cannot reliably reproduce it.
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You receive
** Changed in: compiz (Ubuntu)
Target: ubuntu-8.04-beta => None
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
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-scree
** Changed in: compiz (Ubuntu)
Target: hardy-alpha-6 => ubuntu-8.04-beta
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gn
It certainly appears that this bug is still present, given that new
duplicates are still being filed against the current version via apport.
Marking as 'confirmed' again, lest the bug be incorrectly expired out.
** Changed in: compiz (Ubuntu)
Status: Incomplete => Confirmed
--
compiz.real
No special options needed.
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
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
Not sure, This but is a result from suspending to ram, and then waking
it up, but I guess I could try, what options do you want from valgrind?
i've only used it for memleaks and a callgraph :P
/Sven
Travis Watkins wrote:
> Forgot to mention, if you are still having this problem, can you produce
I haven't had this in a while - i had it once a month or so ago, but not
beyond that. Will be interesting to see what others come up with.
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you ar
Forgot to mention, if you are still having this problem, can you produce
it while running compiz under valgrind and attach the log?
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a memb
Is anyone still having this problem? I thought we had it fixed.
** Changed in: compiz (Ubuntu)
Status: Confirmed => Incomplete
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a m
** Changed in: compiz (Ubuntu)
Target: hardy-alpha-5 => hardy-alpha-6
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
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
** Changed in: gnome-screensaver (Ubuntu)
Target: hardy-alpha-4 => None
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
** Tags added: qa-hardy-desktop
** Tags removed: qa-hardy-list
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-screensa
** Changed in: compiz (Ubuntu)
Target: None => hardy-alpha-5
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-scre
The bug was, it seems, accidentally marked "invalid" for compiz, when it
should only be "invalid" for gnome-screensaver.
** Changed in: compiz (Ubuntu)
Status: Invalid => Confirmed
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
As Ted Gould points out, this seems to be a bug with compiz or X, not
gnome-screensaver.
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Invalid
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug
On Mon, 2008-02-04 at 06:59 +, Ted Gould wrote:
> No, I marked it invalid because it doesn't make sense that there is
> something gnome-screensaver could do would crash compiz. Even if there
> was, that's a bug with compiz not gnome-screensaver. They're at the
> wrong places in the stack to a
On Mon, 2008-02-04 at 23:29 +, edschofield wrote:
> Ted, have you really marked a segfault bug with 22 duplicates as
> "invalid" because you personally have not experienced it on your
> particular hardware?
No, I marked it invalid because it doesn't make sense that there is
something gnome-scr
i have experienced this bug on both x86 and x86_64 8.04 hardy versions on
random events while running a number of programs.
even though 32bit version seems to be more unstable about it.
resuming from screensaver (password protect on) does not seem to be exclusively
affected in my case. i have re
I may have moved the wrong one to confirmed, this seems (by the
responses) to be a compiz bug. Please correct me if i have confirmed
the wrong one, and I can go ahead and fix it.
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You recei
i still experience this error, that is why i've switched it back to
confirmed
** Changed in: gnome-screensaver (Ubuntu)
Status: Invalid => Confirmed
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notificati
Why was this marked invalid?? Surely over 100 users are NOT wrong about
this bug which we are still experiencing, can someone change this back
please, one users installation vs 100 is not right.
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/1
Ted, have you really marked a segfault bug with 22 duplicates as
"invalid" because you personally have not experienced it on your
particular hardware?
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification bec
I can unlock screensavers using metacity. Have been regularly for
several weeks. I'm reasonably certain that this is not a gnome-
screensaver bug.
** Changed in: gnome-screensaver (Ubuntu)
Assignee: Ted Gould (ted-gould) => (unassigned)
Status: Triaged => Invalid
--
compiz.real cra
I also get a SIGSEGV on Hardy amd64 when resuming from suspend with an
Intel G965 graphics card. I presume it's the same bug. My stack trace
is:
Stacktrace:
#0 0x7f25ae818f33 in ?? () from /usr/lib/compiz/libworkarounds.so
#1 0x7f25ae819dfa in ?? () from /usr/lib/compiz/libworkarounds.
** Changed in: gnome-screensaver (Ubuntu)
Target: hardy-alpha-3 => hardy-alpha-4
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, I can still reproduce this.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHhDCJ7/o1b30rzoURAhWDAKCWzYGOFbh49uw87zCO/jXuO3cTlACfQQ/J
hyrAQuOU5fx4WwynfWIvAJs=
Can anyone confirm that this bug is still present with the current
version of compiz in hardy, 1:0.6.99+git20080102-0ubuntu3? All of the
stack traces are against previous versions of the source, which makes it
more challenging to track down a segfault.
--
compiz.real crashed with SIGSEGV when at
I use metacity and this happens to me too so I don't think the cause is
compiz.
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact fo
Not sure how this same bug could be happening under metacity, the
segfault is shown to happen in compiz rather than gnome-screensaver?
Even if gnome-screensaver is triggering it, that says to me it's a
compiz bug.
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.l
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Triaged
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
** Changed in: gnome-screensaver (Ubuntu)
Assignee: (unassigned) => Ted Gould (ted-gould)
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
spoken to amaranth, looks like this is really a gnome-screensaver bug,
as it's happening under metacity too.
** Also affects: gnome-screensaver (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided => High
Status: New => Con
43 matches
Mail list logo