I have somewhat artificial steps but they reproduce this problem pretty easily
on my Sandy Bridge laptop.
Open video with gmplayer and start switching fullscreen/windowed using 'f' key
and scroll forward using right arrow simultaneously. Usually it takes less then
30 seconds before crash.
--
Critical bug in xorg ... I suspect the desktop team will want to look at
it again, so assigning
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Changed in: mesa (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Canonical
X.org (canonical-x)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/926379
Title:
compiz
Launchpad has imported 8 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=46739.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: mesa (Ubuntu)
Milestone: ubuntu-12.04-beta-1 = ubuntu-12.04-beta-2
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/926379
Title:
compiz crashed with SIGSEGV in
This seems to have hit me again: bug 942662
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/926379
Title:
compiz crashed with SIGSEGV in intel_miptree_release() (Needs
mesa-8.0.1)
To manage
I also just got bitten by this - on a freshly updated + rebooted precise
laptop with mesa 8.0.1-0ubuntu2 installed. Reopening...
** Changed in: mesa (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Tags removed: apport-crash bugpattern-needed
** Tags added: apport-request-retrace
** Tags added: apport-crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/926379
Title:
compiz crashed
Hmm, bummer. I wonder if it is indeed the prior bug, or just some
secondary fallout.
I've re-enabled the apport collector so hopefully it can bring us
another stacktrace. Meanwhile, please do whatever you can to reproduce
the crash one more time, so we can get an updated stack trace for the
new
Possibly is this upstream bug:
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=46303
we'll have to check once someone's posted a stacktrace.
** Changed in: mesa (Ubuntu)
Importance: High = Critical
** Bug watch added: www.libreoffice.org/bugzilla/ #46303
http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/9022
http://www.mail-archive.com/intel-gfx@lists.freedesktop.org/msg08585.html
https://bugs.freedesktop.org/show_bug.cgi?id=44970
** Bug watch added: freedesktop.org Bugzilla #44970
Our guess is that the 8.0.1 patch solved these crashes for the general
case, but there are corner cases. The aforementioned links indicate
that this crash happens when compiz renders to a large texture. If that
is true, it would mean that this bug can be reproduced only on systems
with large
I don't have a sandybridge/ironlake system on hand, and can't reproduce
on my other intel hardware.
However if someone does have that hardware and can reproduce the issue,
here's what we need right now:
a) Gather a full backtrace (see https://wiki.ubuntu.com/Backtrace)
b) Is it reproducible on
Bryce, do you still need me to attach dmesg/Xorg.0.log/xsession-errors?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/926379
Title:
compiz crashed with SIGSEGV in intel_miptree_release()
There have been two patches proposed upstream (one to mesa, one to
libdrm) which purportedly fix this crash, however they've not yet been
reviewed or accepted into any official git trees. If someone figures
out a reliable way to reproduce the crash, we can package the patches
for testing
I won't be able to get a backtrace today, but will do so tomorrow if
nobody beats me to it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/926379
Title:
compiz crashed with SIGSEGV in
Guilherme, yes a fresh dmesg/Xorg.0.log/.xsession-errors would be
helpful. The backtrace is the most important bit though so we
definitely need that.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
From elmo's dupe bug #942966
.xsession-errors:
Gtk-WARNING **: Unable to locate theme engine in module_path: pixmap,
ERROR:dbus.service:Unable to append ({'CanGoNext': True, 'CanPause': True,
'Shuffle': True, 'CanControl': True, 'LoopStatus': 'None', 'PlaybackStatus':
'Paused', 'Volume': 1.0,
I've forwarded this bug upstream to:
https://bugs.freedesktop.org//show_bug.cgi?id=46739
I think we have enough info now, although I wouldn't mind seeing other
stacktraces in case there are more permutations on this bug.
** Bug watch added: freedesktop.org Bugzilla #46739
This bug was fixed in the package mesa - 8.0.1-0ubuntu1
---
mesa (8.0.1-0ubuntu1) precise; urgency=low
* Merge from Debian experimental.
mesa (8.0.1-1) UNRELEASED; urgency=low
* New upstream bugfix release. (LP: #926379)
mesa (8.0-2) experimental; urgency=low
[ Julien
Great, then yeah this looks like it's an HiZ issue.
We'll be updating to 8.0.1 soon enough, not worth the trouble to
cherrypick the patches.
** Summary changed:
- compiz crashed with SIGSEGV in intel_miptree_release()
+ compiz crashed with SIGSEGV in intel_miptree_release() (Needs mesa-8.0.1)
21 matches
Mail list logo
