Do you have the fglrx driver (for your AMD card) installed?
Compiz crashes on my system when it is, so I get no unity when it is
installed, and slow to the point of unusable unity when I remove it.
Also tried using the latest version from amd.com but still no joy
--
You received this bug
Pushing to SRU-1 at least regarding quantal, will need a lot of testing.
** Changed in: unity/6.0
Milestone: 6.10.0 = 6.12.0
** Changed in: unity/6.0
Status: New = Confirmed
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to
This is not specifically related to nvidia-current. After an update last
night I currently have a broken system with ati drivers.
See also bug #1063400
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
*** This bug is a duplicate of bug 1054049 ***
https://bugs.launchpad.net/bugs/1054049
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1054049, so is being marked as such.
Public bug reported:
The session migration scripts 02_migrate_to_gsettings.py and
03_migrate_profile_independent.py are using gconf.
Without phyton-gconf the scripts are failing with the following error:
Traceback (most recent call last):
File ./02_migrate_to_gsettings.py, line 22, in module
** Description changed:
It fades the windows out/in to hide/show the desktop like the Fade to
Desktop plug-in should do instead of moving the windows out of view
like it did in the past.
- This is Compiz 0.9.7.8 with the vanvugt compiz-preproposed PPA
- installed.
+ This is happening
Public bug reported:
Since version 1:0.9.8+bzr3319-0ubuntu1, compiz/unity keeps messing up my
gsettings (keybindings and WM prefs). This was already covered in bug
1042041, but the change there mostly caused the bug to happen
consistently now.
At every session startup I have a script to fix my
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
To manage notifications about this
This is still an issue, reported as bug 1063617.
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1042041
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
I disabled all *.convert files in /usr/share/GConf/gsettings and
restarted again. This caused org.gnome.desktop.wm.preferences auto-
raise to now remain on false, so it seems this key is affected by the
gconf migration. This is handled by wm-schemas.convert:
auto-raise =
** Changed in: unity
Milestone: 5.18.0 = None
** Changed in: unity
Status: Triaged = Invalid
** Changed in: unity (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
I tried this with a freshly created user account. After the first
startup ever, the settings are like this:
test@donald:~$ gsettings get org.gnome.desktop.wm.preferences auto-raise
false
test@donald:~$ gsettings get org.gnome.desktop.wm.keybindings lower
@as []
test@donald:~$ gsettings get
If I restart the test user session again, the focus and keybinding
gsettings keys are unchanged since the second session, but now the
behaviour matches the gsettings again, i. e. the
'ControlPrimarySuperUp' keybindings, disabled lower binding, and
click-to-focus. I also now have auto-raise set to
** Changed in: compiz (Ubuntu Oneiric)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/764330
Title:
[regression] Moving windows lags behind the
** Changed in: fglrx-installer (Ubuntu)
Status: Confirmed = Invalid
** Changed in: fglrx-installer (Ubuntu Oneiric)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
** Changed in: fglrx-installer (Ubuntu)
Status: Invalid = Confirmed
** Changed in: fglrx-installer (Ubuntu Oneiric)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
Public bug reported:
Since a few days, my lock screen doesn't work anymore. The desktop seems
washed out white (I can still see it) on one of my screens, while the
other one remains visible. There is something stealing the focus, so I
can't interact with any windows anymore. Unfortunately there
Public bug reported:
Fullscreen windows should be unredirected by default, since only then
users will get optimal performance also when running full screen
applications like games. Currently users need to learn about the compiz
setting (CompizConfig Settings Manager (package
*** This bug is a duplicate of bug 1054049 ***
https://bugs.launchpad.net/bugs/1054049
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1054049, so is being marked as such.
Thanks Arnulf, I made another workaround based on your tip.
We already distributed the file /usr/share/gconf/defaults/99-our-
defaults to workstations, so we can just override the default
active_plugins specified in 10_compiz-gnome.
That file in turn comes from the package compiz-gnome and I
occurs again after a GDM update
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1060171
Title:
gtk-window-decorator crashed with SIGSEGV in
g_hash_table_lookup_node() from
*** This bug is a duplicate of bug 1054049 ***
https://bugs.launchpad.net/bugs/1054049
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1054049, so is being marked as such.
Swapping speed settings appears to only work some of the time. When a
game is running, the desktop effects become incredibly slugging (5-10fps
range), but the game will continue at an uninterrupted framerate.
--
You received this bug notification because you are a member of compiz
packagers,
Solved the window borders missing problem by deleting everything in
the home/cache folder.. Not getting the bug anymore...
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1062833
Title:
Yes I have installed fglrx manually (the legacy version), only did this
after Unity was not starting directly. This bug only happened after the
upgrade from 12.04. I did a fresh install this weekend (daily build of
quantal) and can use Unity/compiz without any trouble so far.
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: compiz (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
Hi, I hope this is the right bug report to comment on :)
For me several games still run really slowy in Unity, but run okay in Unity 2D
or on a seperate X-server. Recent examples are Dustforce, Oil Rush and
Jamestown. For example Oil Rush with ultra/high has 53 fps in the main window
on a
Public bug reported:
In Ubuntu 12.10 beta there are no alternative application switchers,
they were present in Ubuntu 12.04 and with slight tweaks they were fully
usable.
** Affects: compiz (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
This fix is available in precise-updates, so shouldn't it be listed as
fix released for precise and ubuntu?
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/980663
Title:
Compiz won't
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: compiz (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/964788
8-(
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/738864
Title:
compiz crashed with SIGSEGV in free()
To manage notifications about this bug go to:
You have been subscribed to a public bug:
Using quantal beta2:
- go to an empty ws
- open an app from the launcher
- click on the ws icon
- there is an orange rectangle around the ws but it's content is not
colored
- close the ws overview
- change ws
- open the ws overview again
- it's
This bug also affects me, and I can confirm the exact same symptoms with
12.10, latest compiz and unity. I'm using the nvidia-current package
(304.48). I'd love to help contribute system configs/logs/etc or
anything else that might help, though apport-collect won't let me submit
to this bug.
--
Confirmed. I believe the offending code is an Ubuntu distro patch to the
expo plugin. The bug does not exist in upstream compiz.
** Package changed: unity (Ubuntu) = compiz (Ubuntu)
** Project changed: unity = compiz
** Changed in: compiz
Milestone: 7.0.0 = None
** No longer affects:
** Summary changed:
- Maximized window gets unredirected when it's not fullscreen
+ [regression] Maximized window gets unredirected when it's not fullscreen
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
** Changed in: compiz (Ubuntu)
Status: New = Triaged
** Changed in: compiz
Status: New = Triaged
** Changed in: compiz (Ubuntu)
Status: Confirmed = Triaged
** Changed in: compiz
Milestone: None = 0.9.9.0
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
To clarify:
The main fix is the Compiz fix, not the Unity fix. But you really should
have both to resolve the bug.
The key Compiz fix has not been backported to precise at all. And nor
should it at least without a fix for bug 1053902 too.
** Also affects: compiz-core
Importance: Undecided
That's a mistake. It's definitely not released to precise as shown here:
https://launchpad.net/ubuntu/+source/compiz
And I cannot see the fix even committed to the precise-proposed code
yet.
** Changed in: unity (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug
Yes there are. Just install package: compiz-plugins
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1064048
Title:
There
This bug is fix released. If you have a new crash then please log a new
bug.
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/738864
Title:
compiz crashed with SIGSEGV in free()
To
I had the same issue on 12.04, I was able to fix the scale windows
problem with the steps on comment #3, however, the Show desktop is not
working after a restart, I then installed 12.10 and the show desktop
issue persists, is it going to be a permanent fix in near future?
Thanks!
--
You received
41 matches
Mail list logo
