I can second what I mentioned elsewhere: This is *not* related to
nouveau. Nor is it related to Compiz effects.
I get these symptoms maybe 10-20 per day: Screen freezes. Music/sound
continues to work. Can move mouse but not click. Keyboard unresponsive.
After maybe 10s the system comes back up.
Seeing this as well. But the slowness of the dash reveal is disregarding
whether I use mouse or keyboard to reveal the dash.
** Also affects: unity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Changed in: unity
Status: New = Confirmed
** Tags added: nvidia
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/855414
Title:
Unity dash becomes very slow/laggy
Marked Invalid for Unity and Nux components as this crash seems caused
by a bug in the nouveau driver, in some GL functionality that we have to
assume is working.
If there are indicators that we can fix or work around this in Nux or
Unity please reopen.
** Changed in: unity (Ubuntu)
With latest rounds of updates (2011-01-17) I can't reproduce this
anymore. Annoying to not know what caused this, but seems like a wasted
effort to track down at this point.
** Changed in: unity
Status: Confirmed = Fix Released
** Changed in: xorg (Ubuntu)
Status: New = Fix
For those of you using CLUTTER_VBLANK=none - you shouldn't be too
afraid of all the spooky error messages in the terminal. The worst
thing it should give you would be some rendering glitches - which is
nothing compared to the pain you have now anyway I guess ;-)
My initial command to make the
Hi everyone - I'm one of the devs that have spent extensive time chasing
this slowness issue. I assure you I can relate to your disappointment
over a sluggish system. It's buggering me a lot as well.
The problem is that on some systems Unity runs perfectly fast (for
instance on my Eee 1001, intel
Works well here with mesa_7.9~git20100909-0ubuntu2
--
choosing netbook for login session results in a blank white screen
https://bugs.launchpad.net/bugs/638725
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
(Just for reference here's the batch of updates Markus got:
http://paste.ubuntu.com/483828/)
--
[RV515] Unity keeps reloading with a white background
https://bugs.launchpad.net/bugs/616997
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Vish: Can you confirm that the latest round of updates work? (run 'apt-
cache policy unity' as Markus above and check you have at least
0.2.28-0ubuntu3 or a newer version of Unity)
--
[RV515] Unity keeps reloading with a white background
https://bugs.launchpad.net/bugs/616997
You received this
Vish: Cool you followed through on this - thanks! Your test output
indicates that all the tests are happy. Which is good of course, but
deepens the mystery...
Markus: Thanks for the xsession-error log!
Looking in both of your xession-error logs I see a:
(mutter:1347):
Vish: That's odd... These devel packages should definitely be available
in the repos. I don't have an explanation off the top of my head...
Markus:Ok, that sounds like an up-to-date Maverick installation. Is
there anything non-standard in the way you run it? Like from a usb-
stick, in a virtual
This is *not* a fix, but I need some help nailing this one. So if any
one that can reproduce this could check this for me:
1) bzr branch lp:~unity-team/dee/import-model-crash dee.import-model-crash
2) cd dee.import-model-crash ./autogen --prefix=/usr make check
** Branch linked:
Sorry, I just realized that in order to run the test suite you also need
to install lp:dbus-test-runner and lp:gtx both with --prefix=/usr
--
[RV515] Unity keeps reloading with a white background
https://bugs.launchpad.net/bugs/616997
You received this bug notification because you are a member
Thanks Markus!
Markus' mutter.crash.retraced dump indicates what I suspected. The
callback we get from dbus-glib passes in invalid data to
clone_callback() function's 4th argument (GPtrArray rows) (dee-shared-
model.c line 1055 in the attached branch).
This probably means that there is a double
Vish, Markus: What version of dbus-glib do you have - and which Ubuntu
version? From Vish's dump it looks like you only have 0.86?
--
[RV515] Unity keeps reloading with a white background
https://bugs.launchpad.net/bugs/616997
You received this bug notification because you are a member of
I am sorry to ask a question that'll be laborious to answer, but I
simply can't reproduce it here... Is it always segfaulting in libdee,
and is it always the same place?
Looking at the stack trace it looks like libdee receives garbage data in
a callback from libdbus-glib. It's not that dbus-glib
** Changed in: unity
Milestone: 2010-08-12 = 2010-08-19
--
unity quits with CheckGLError in ./ctk-render-target.c:285
https://bugs.launchpad.net/bugs/593380
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
18 matches
Mail list logo
