Public bug reported:
accerciser cannot explore Unity's accessibility object hierarchy
** Affects: unity
Importance: Undecided
Status: New
** Affects: unity/7.2
Importance: Undecided
Status: New
** Affects: unity (Ubuntu)
Importance: Undecided
Status: Ne
Well, this is not needed for the lp:unity/7.2 as it's already correct.
Just going to mark the tasks Fix Released then:)
** No longer affects: unity/7.2
** Changed in: unity
Status: New => Fix Released
** Changed in: unity (Ubuntu)
Status: New => Fix Released
--
You received this
** Also affects: unity/7.2
Importance: Undecided
Status: New
** Changed in: unity/7.2
Status: New => In Progress
** Changed in: unity/7.2
Importance: Undecided => Medium
** Changed in: unity/7.2
Assignee: (unassigned) => Andrea Azzarone (azzar1)
** Changed in: unity/7.2
** Also affects: unity/7.2
Importance: Undecided
Status: New
** Changed in: unity/7.2
Status: New => In Progress
** Changed in: unity/7.2
Importance: Undecided => High
** Changed in: unity/7.2
Assignee: (unassigned) => Andrea Azzarone (azzar1)
** Changed in: unity/7.2
** Also affects: unity/7.2
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1301394
Title:
Launcher damange th
** Also affects: unity/7.2
Importance: Undecided
Status: New
** Changed in: unity/7.2
Status: New => In Progress
** Changed in: unity/7.2
Importance: Undecided => Medium
** Changed in: unity (Ubuntu)
Importance: Undecided => Medium
** Changed in: unity/7.2
Assignee:
Definitely not a Compiz issue. Most likely a bug in the BIOS that
affects Linux, but Windows has a workaround in place for. I will put
this in the Linux kernel category and if someone there wants to change,
they will.
** Package changed: compiz (Ubuntu) => linux (Ubuntu)
--
You received this b
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: unity/7.2
Milestone: None => 7.2.6
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.n
Importance: Medium
Assignee: Christopher Townsend (townsend)
Status: Confirmed
** Affects: unity (Ubuntu)
Importance: Medium
Assignee: Christopher Townsend (townsend)
Status: Confirmed
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
Importance: Medium
Assignee: Christopher Townsend (townsend)
Status: Confirmed
** Affects: unity (Ubuntu)
Importance: Medium
Assignee: Christopher Townsend (townsend)
Status: Confirmed
** Also affects: unity
Importance: Undecided
Status: New
.
** Affects: unity
Importance: Medium
Assignee: Christopher Townsend (townsend)
Status: Confirmed
** Affects: unity (Ubuntu)
Importance: Medium
Assignee: Christopher Townsend (townsend)
Status: Confirmed
** Also affects: unity
Importance: Undecided
After some discussion w/ Marco, he determined that this is some issue in
Gtk3. Adding that package as affected too.
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
** Also affects: gsettings-desktop-schemas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1456241
Tit
27;lower'
** Changed in: ubuntu-settings (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-settings (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-settings (Ubuntu)
Assignee: (unassigned) => Christopher Townsend (townsend)
** No longer
I fixed this up in ubuntu-settings. I've made a branch as well as
attaching a patch.
** Patch added: "lower_middle_click.patch"
https://bugs.launchpad.net/unity/+bug/1456241/+attachment/4399746/+files/lower_middle_click.patch
--
You received this bug notification because you are a member of
This is indeed a Gtk3 issue. I tried Gtk 3.16.3 from ppa:ubuntu-
desktop/ww and the issue no longer reproduces.
** No longer affects: unity (Ubuntu)
** Changed in: unity
Status: In Progress => Invalid
** Changed in: unity
Assignee: Christopher Townsend (townsend) => (unas
ecided
Status: New
** Changed in: unity/7.2
Status: New => Triaged
** Changed in: unity/7.2
Importance: Undecided => Medium
** Changed in: unity/7.2
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: unity/7.2
Milestone: None => 7.2.6
--
You
*** This bug is a duplicate of bug 1456241 ***
https://bugs.launchpad.net/bugs/1456241
Uhh, didn't realize there was already a bug opened on this. At any
rate, I'm going to dup it to bug #1456241 since that is where I did the
investigation.
** This bug has been marked a duplicate of bug 1456
Since I can't reproduce this issue and no one has said that it still
occurs, I'm going to mark this Fix Released. If it does still occur,
then this bug report can be reopened or a new one can be opened.
Thanks!
** Changed in: unity
Milestone: 7.3.3 => None
** Changed in: unity
Status
*** This bug is a duplicate of bug 269904 ***
https://bugs.launchpad.net/bugs/269904
Hi Szilárd Páll,
Yes, please file a new bug using 'ubuntu-bug compiz'. I'll keep an eye
out for the new bug and we can go from there.
--
You received this bug notification because you are a member of Deskt
** Changed in: unity
Status: In Progress => Fix Committed
** No longer affects: unity-scope-home
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/120
** Changed in: unity
Status: In Progress => Fix Committed
** No longer affects: nautilus (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs
** Changed in: compiz (Ubuntu)
Status: Triaged => Invalid
** No longer affects: compiz (Ubuntu Trusty)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/b
: Undecided => High
** Changed in: unity
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: unity
Milestone: None => 7.3.3
** Changed in: unity (Ubuntu)
Status: Triaged => In Progress
** Changed in: unity (Ubuntu)
Assignee: (unassigned)
For those that still see this issue, I'm tracking this under bug
#989588. I think I have a fix and will propose a solution soon. Please
follow that bug since this bug is already Fix Released.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Changed in: unity/7.2
Status: New => In Progress
** Changed in: unity/7.2
Importance: Undecided => Critical
** Changed in: unity/7.2
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: unity/7.2
Milestone: None => 7.2.6
--
You received this bug notific
Most definitely not a Unity issue then. Reassigning the bug to linux-
generic-lts-utopic.
** Package changed: unity (Ubuntu) => linux-meta-lts-utopic (Ubuntu)
** No longer affects: unity
** Changed in: linux-meta-lts-utopic (Ubuntu)
Status: Incomplete => New
--
You received this bug no
Public bug reported:
When calling gtk.gdk.Window.get_origin(), it returns 3 values instead of
the documented 2-tuple of the x & y origin of the window. I'm not sure
if the 3 values is intended and the documentation is wrong or if this is
truly a bug.
Here is a simple way to reproduce.
1. Open a
Assignee: Christopher Townsend (townsend)
Status: In Progress
** Affects: unity (Ubuntu)
Importance: Medium
Assignee: Christopher Townsend (townsend)
Status: In Progress
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity
Since the proposed patches to X have been rejected, what can be done
here to fix this properly?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1200829
Title:
Regression: Enabling
Since the proposed patches to X have been rejected, what can be done
here to fix this properly?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1171342
Title:
mouse scroll wheel no
Since the proposed patches to X have been rejected, what can be done
here to fix this properly?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1240957
Title:
Scrolling behaviour a
Since the proposed patches to X have been rejected, what can be done
here to fix this properly?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1184159
Title:
[saucy] scrolling wit
e was actually caught during Autopilot testing on multi-
monitors.
** Affects: unity
Importance: Medium
Assignee: Christopher Townsend (townsend)
Status: In Progress
** Affects: unity (Ubuntu)
Importance: Medium
Assignee: Christopher Townsend (townsend)
Statu
Public bug reported:
A stop gap workaround has been put in place for bug #1313597, but the
proper fix is to use the input::Monitor when it merges. See
https://code.launchpad.net/~3v1n0/unity/lockscreen-grabbing
** Affects: unity
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v
Look like this issue was actually fixed some time ago. Marking as such.
** Changed in: unity
Status: Triaged => Fix Released
** Changed in: unity
Milestone: 7.3.2 => None
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity
This seems fixed as no new activity has occurred for this bug in some
time. I also cannot reproduce, albeit, on an Intel graphics machine.
Going to mark it Fixed Released. We can either reopen this bug or
submit a new bug report if it still occurs for anyone.
** Changed in: unity
Status:
As has been mentioned before, this seems to be an issue with apps using
"Minimize to Tray" when there is no "tray" in Unity. Marking this as
Fix Released in Unity as the core issue of showing the running app in
the Launcher is fixed.
** Changed in: unity
Status: Triaged => Fix Released
**
longer affects: unity/7.2
** Package changed: unity (Ubuntu) => compiz (Ubuntu)
** Changed in: compiz (Ubuntu)
Status: Incomplete => Triaged
** Changed in: compiz (Ubuntu)
Importance: Medium => Low
** Changed in: compiz
Assignee: (unassigned) => Christopher Townsend
** Changed in: compiz (Ubuntu)
Status: New => Triaged
** Changed in: compiz
Importance: Undecided => Medium
** Changed in: compiz (Ubuntu)
Importance: Undecided => Medium
** Changed in: compiz
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in:
** Changed in: unity (Ubuntu)
Importance: Undecided => Low
** Changed in: unity
Milestone: None => 7.3.2
** Changed in: unity
Assignee: (unassigned) => Christopher Townsend (townsend)
--
You received this bug notification because you are a member of Desktop
Packages, which is
Actually, this isn't the Gtk grabbing stuff. This has been in Compiz
since 2008! I agree that the desktop should be focused if the mouse is
over it. I wonder why more people haven't brought up this issue...
At any rate, I'm going to add a config option to allow the behavior as
it currently is,
** Changed in: compiz
Status: Triaged => In Progress
** Changed in: compiz (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1427636
T
** Changed in: compiz
Status: Confirmed => In Progress
** Changed in: compiz (Ubuntu)
Status: Confirmed => In Progress
** Changed in: compiz (Ubuntu)
Importance: Undecided => Medium
** Changed in: compiz (Ubuntu)
Assignee: (unassigned) => Christopher Townse
** Also affects: compiz/0.9.11
Importance: Undecided
Status: New
** Changed in: compiz/0.9.11
Status: New => Confirmed
** Changed in: compiz/0.9.11
Importance: Undecided => Medium
** Changed in: compiz/0.9.11
Assignee: (unassigned) => Christopher Townsend
BTW, this is most likely a Compiz issue, so I'm changing the
project/package to reflect that.
** Project changed: unity => compiz
** Changed in: compiz
Milestone: 7.3.3 => None
** Package changed: unity (Ubuntu) => compiz (Ubuntu)
--
You received this bug notification because you are a mem
Hmm, seems fixed some time ago, so going to mark the main Unity task as
such as well and remove the milestone.
** Changed in: unity
Status: Triaged => Fix Released
** Changed in: unity
Milestone: 7.3.3 => None
--
You received this bug notification because you are a member of Desktop
This is a rather old bug that I can't seem to reproduce and has been set
Incomplete for some time. It's probably been fixed in some release and
going to mark as such.
If it still occurs, we can either reopen this bug or open a new one.
** Changed in: unity
Status: Incomplete => Fix Releas
This is a rather old bug that has been sitting stale for some time.
Since no one responded to Marco in his comment on 2013-09-16, I'm going
to say it's been fixed in some release and going to mark as such.
If this does indeed still occur, then we can either reopen this bug or
open a new one.
** C
Since no one responded to Andrea's inquiry on 2015-01-17 and Ubuntu
12.10 is out of support, I'm going to surmise this was fixed somewhere
along the way.
If it still does occur, we can either reopen this bug or open a new one.
** Changed in: unity
Status: Incomplete => Fix Released
** Cha
This is a rather old bug and is sitting stale. Since no one responded
to Andrea on his 2014-12-01 inquiry about being able to reproduce this,
I'm going to mark it fixed as some prior release probably fixed it.
If this still does occur, then we can reopen this bug or open a new one.
** Changed in
This was a conscious decision to maximize a window in a different
workspace if >50% of the window is in a different workspace. I believe
Design felt that if a user makes a decision to put over half a window in
another workspace, that window is really intended for that workspace.
This is solely a
This is quite an old bug and I have not seen any new bug reports about
this in a very long while, so I'm guessing it has been fixed along the
way. I'm going to mark it Fixed Released.
If this still does occur, then we can either reopen this bug or open a
new one.
** Changed in: unity
Stat
This bug is rather old and I have not seen any new bugs like this
reported. I'm guessing this has been fixed along the way and marking as
Fix Released.
If this does still occur, we can either reopen this bug or open a new
one.
** Changed in: unity
Status: Confirmed => Invalid
** Changed
Based on some of the later comments in here, I'm going to go ahead an
close the Unity part of this Fix Released.
If it still occurs, then I think a new bug needs to be opened since it's
most likely a different issue.
** Changed in: unity
Status: Confirmed => Fix Released
** No longer affe
This is a very old bug and the crash has not been seen in a long time.
It seems it has been fixed some releases ago, so going to mark Fix
Released.
If it does still occur, we can either reopen this bug or open a new one.
** Changed in: unity (Ubuntu)
Status: Confirmed => Fix Released
** C
This is a rather old bug and the crash has not been reported in a very
log time. It seems this has been fixed some releases ago and as such,
marking Fix Released.
If it does still occur, then we can either reopen this bug or open a new
one.
** No longer affects: unity/5.0
** No longer affects:
This is a rather old bug and it sure looks like it doesn't occur
anymore. Since it's been some time since a crash like this has been
reported, it seems it's been fixed some release ago and I'm marking as
such.
If it does still occur, we can reopen this bug report or open a new one.
** Changed in
This is a rather old bug report now and there have been no new reports
of this issue. It seems it's been fixed some releases ago, so I'm
marking as such.
If this does still occur, we can either reopen this bug report or open a
new one.
** Changed in: unity
Status: Confirmed => Fix Release
This is a rather old bug that was submitted against a now unsupported
release. Looking at the last bug that was dup'ed to this one, that bug
was against 13.10. It appears the crash has been fixed by at 14.04, so
I'm going to mark it as such.
If this does still occur, we can either reopen this bu
Hmm, looking at errors.ubuntu.com, it looks like this one does show up
from time to time, even on 15.04, so going to reopen.
** Changed in: compiz
Status: Fix Released => Confirmed
** Changed in: compiz (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: compiz
Milestone:
** Changed in: unity
Assignee: Michal Hruby (mhr3) => (unassigned)
** Changed in: unity/7.2
Assignee: Michal Hruby (mhr3) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad
On 14.04, scrolling over the sound indicator does not close the Dash.
Based on the bug description's expected behavior, I say this is fixed.
Whether or not if the Dash should close when clicking on indicators
should be discussed in a different bug report. Closing Fix Released.
** Changed in: uni
Removing the 7.3.3 milestone as this no longer an issue. It *could*
still perhaps be an issue on 12.04, so I'm adding a task for that, so
someone can investigate further sometime.
** Also affects: unity/5.0
Importance: Undecided
Status: New
** Changed in: unity
Milestone: 7.3.3 =>
Removing this from the 7.3.3 milestone as it seems this only affects
Unity on 12.04. Even that, I'm not sure if 12.04 is still affected, but
will keep that task open for now.
** Changed in: unity
Milestone: 7.3.3 => None
** Changed in: unity
Status: Confirmed => Fix Released
** Chang
In my last comment, I meant to say, this has been *fixed* some releases
ago.
** No longer affects: compiz
** Changed in: unity
Status: Confirmed => Fix Released
** Changed in: unity
Milestone: 7.3.3 => None
** Changed in: unity (Ubuntu)
Status: Confirmed => Fix Released
--
Y
Based on comment #15, I'm going to close this Fix Released since it's no
long unusable. I agree that running Compiz/Unity on llvmpipe is not fun
and miss Unity 2d for these types of systems.
** Changed in: unity
Milestone: 7.3.3 => None
** Changed in: unity
Status: Confirmed => Fix Re
Ok, Brandon does not see anymore either, so closing Fix Released.
** Changed in: unity
Status: Triaged => Fix Released
** Changed in: unity (Ubuntu)
Status: Triaged => Fix Released
** Changed in: unity
Milestone: 7.3.3 => None
--
You received this bug notification because you
Brandon also can't reproduce, so going to mark this Fixed Released and
remove the linked branch.
We can reopen if we have misunderstand the repro steps.
** Changed in: unity (Ubuntu)
Importance: Undecided => Low
** Changed in: unity
Status: In Progress => Fix Released
** Changed in: u
Yep, after getting educated by andyrock, I can reproduce, so I'll set
this bug back to where it should be.
** Changed in: unity
Status: Triaged => In Progress
** Changed in: unity/7.2
Status: Triaged => In Progress
** Changed in: unity (Ubuntu)
Status: Fix Released => In Pro
** Branch linked: lp:~azzar1/unity/fix-1029114
** Also affects: unity/7.2
Importance: Undecided
Status: New
** Changed in: unity/7.2
Status: New => Confirmed
** Changed in: unity/7.2
Importance: Undecided => Low
** Changed in: unity/7.2
Assignee: (unassigned) => Andrea
Since there has been no more activity in this bug report, I'm going to
mark the Fix Released. If it still does occur, we can either reopen
this bug report or open a new one.
** Changed in: unity
Status: Incomplete => Fix Released
** Changed in: unity
Milestone: 7.3.3 => None
** Chang
; None
** Changed in: compiz
Milestone: None => 0.9.12.2
** Package changed: unity (Ubuntu) => compiz (Ubuntu)
** Changed in: compiz
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: compiz (Ubuntu)
Assignee: (unassigned) => Christopher Townsend (
Thanks, I'll mark Fix Released then.
** Changed in: unity
Milestone: 7.3.3 => None
** Changed in: unity
Status: Incomplete => Fix Released
** Changed in: unity (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Deskto
n: compiz/0.9.11
Importance: Undecided => Medium
** Changed in: compiz/0.9.11
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: compiz/0.9.11
Milestone: None => 0.9.11.4
--
You received this bug notification because you are a member of Desktop
Packages, whic
@Ryan,
This bug is about random log off's, not preventing a machine from going
to sleep and issues derived from that. I believe you commented in the
wrong bug. Please either find an appropriate bug or enter a new bug
report altogether. Thanks!
All others,
This is a bug closed as Fixed Released
** Changed in: compiz
Importance: Undecided => Low
** Changed in: compiz
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/735677
Title:
Vertical ma
** Changed in: compiz
Status: Triaged => In Progress
** Changed in: compiz (Ubuntu)
Status: Triaged => In Progress
** Changed in: compiz (Ubuntu)
Assignee: (unassigned) => Christopher Townsend (townsend)
** Also affects: compiz/0.9.11
Importance: Undecided
** Changed in: compiz
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1251777
Title:
[regression] Semi-maxi
I don't think this is happening anymore for some time, probably was
fixed with the fix for bug #1070735. As such, I'm going to mark Fix
Released. If this does indeed still occur, we can either reopen this
bug report or open a new one.
** Changed in: unity
Status: Triaged => Fix Released
** Branch linked: lp:~3v1n0/unity/switcher-terminates-spread
** Changed in: unity
Assignee: Christopher Townsend (townsend) => Marco Trevisan (Treviño)
(3v1n0)
** Changed in: unity (Ubuntu)
Assignee: Christopher Townsend (townsend) => Marco Trevisan (Treviño)
(3v1n0)
** Also a
Public bug reported:
When opening a Quicklist while in Spread, the Quicklist and Launcher can
sometimes be unusable. The Quicklist will be open, but it doesn't
accept clicks nor does the Launcher. In order to clear out this
condition, I enter keynav mode for the Launcher.
** Affects: unity
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/729979
Title:
[nvidia] Windows appear blank white
Status in Compiz
The same fix for bug #729979 is used for this bug in Trusty. Since that
bug was verified, then I'm marking this bug as verified-done as well.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages,
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1424013
Title:
Compiz high CPU and UI freeze on NVIDIA after fix fo
Hi Eloy,
Could you open CCSM and disable the X11 Sync and see if the issue still
occurs?
CCSM->OpenGL and uncheck "X11 Sync objects"
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/b
Hey Eloy,
Regarding the question of why going back to the previous COmpiz version
works, my guess is that a bug exists in the GPU and/or the Nvidia 304 in
which it doesn't handle the GL_EXT_x11_sync_object OpenGL extension. So
far in all of the user testing of this patch, only the GeForce 6150SE
Hmm, we now have two different GPU's mentioned as being negatively
affected by the X11 Sync Nvidia patch. However, both of these GPU's are
integrated in the motherboard chipset. On top of that, Nvidia has
dropped driver support for these GPU's.
I'm thinking about maybe adding some sort of blackl
Hey Ryan,
Thanks for the additional info. Hmm, it seems there are folks who still
use the 304 driver on newer machines. I'm also not sure if folks are
having the refresh issue using 304 drivers on newer GPUs, so I don't
think it's a good idea to blacklist the 304 driver.
I found a list of inte
Hey All,
Could you please do the following to help me figure out what render
strings I should key on?
1. Install glxinfo on the machine.
2. Then run 'glxinfo | grep "OpenGL renderer string' from a terminal.
3. Paste the output in this bug.
Thanks!
--
You received this bug notification because
Hi Lucas,
I see you have integrated Nvidia graphics and I'm wondering if you are
affected by the X11 Sync Nvidia patch introduced in the last SRU. It
seems that patch may not play nice with Nvidia integrated graphics for
some reason.
If you are able to start CCSM, could you try going to OpenGL a
*** This bug is a duplicate of bug 1424013 ***
https://bugs.launchpad.net/bugs/1424013
** This bug has been marked a duplicate of bug 1424013
Compiz high CPU and UI freeze on NVIDIA after fix for #269904 in
trusty-updates
--
You received this bug notification because you are a member of
n: compiz/0.9.11
Importance: Undecided => High
** Changed in: compiz/0.9.11
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: compiz/0.9.11
Milestone: None => 0.9.11.4
** Changed in: compiz/0.9.11
Milestone: 0.9.11.4 => 0.9.11.3
--
You received
Hi Eloy,
Thanks for the info. I'm currently working on a more permanent fix in
Compiz in which I will "blacklist" known GPU's that are affected by
this.
There shouldn't be any performance penalty when running with X11 Sync
turned off. What that is supposed to do is keep the GPU's rendering in
S
Hi All,
I believe I have a fix/workaround for this issue in which I blacklist
the affected GPUs from using the X11 Sync stuff. However, I do not have
a machine that I can test this with, so I'm asking for your help.
I have versions of Compiz built for Vivid and Trusty w/ this fix built
in a PPA.
You can try looking in /var/carsh and see if there is a compiz related
crash in there. Also, could you post the relevant lines in your syslog?
Sometimes, compiz segfaults due to buggy drivers as well. Was there any
update to your graphics driver? Are you using fglrx or radeon for your
graphics
I can't reproduce this anymore and believe it's been fixed some time
ago, including 14.04. I'm marking as Fix Released. If this does indeed
still occur, this bug report can either be reopened or open a new one.
** Changed in: unity
Status: Triaged => Fix Released
** Changed in: unity/7.2
It's weird that the Compiz update would cause this. The only changes in
the last Compiz SRU are a blacklist for Nvidia cards for disable X to GL
syncs and the removal of a texturesCache in the animation plugin that
caused issues on Nvidia cards and that's it. The texturesCache was
unused and only
Thanks for the detailed update. I'll close this as Invalid.
** Changed in: compiz (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1449089
Ti
** Also affects: unity/7.2
Importance: Undecided
Status: New
** Changed in: unity/7.2
Status: New => Triaged
** Changed in: unity/7.2
Importance: Undecided => Medium
** Changed in: unity/7.2
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed
1 - 100 of 832 matches
Mail list logo
