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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
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
** 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
** 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
Bugs, which is subscribed to Ubuntu.
--
** 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
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
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is
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
** 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
Bugs, which is subscribed to Ubuntu.
--
** 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
Bugs, which is subscribed to Ubuntu.
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
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
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
** 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
Bugs, which is subscribed to Ubuntu.
--
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
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
** 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
Bugs, which is the 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
Bugs, which is the bug contact for Ubuntu.
--
** 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
Bugs, which is the bug contact for Ubuntu.
--
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
You
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
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
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
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
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
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
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
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
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
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
** 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
Bugs, which is the bug contact
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
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
Bugs, which is the bug contact for
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
-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=
** 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
Bugs, which is the 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
Bugs, which is the bug
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 =
** Changed in: compiz (Ubuntu)
Importance: Medium = High
Target: None = hardy-alpha-3
** Summary changed:
- compiz.real crashed with SIGSEGV
+ compiz.real crashed with SIGSEGV when attempting to unlock screen
** Description changed:
Binary package hint: compiz
compiz.real
** Tags added: qa-hardy-list
--
compiz.real crashed with SIGSEGV
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: compiz (Ubuntu)
Assignee: (unassigned) = compiz packagers (compiz)
Status: New = Confirmed
--
compiz.real crashed with SIGSEGV
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Visibility changed to: Public
--
compiz.real crashed with SIGSEGV
https://bugs.launchpad.net/bugs/131679
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
47 matches
Mail list logo
