Actually, it's not yet included in the release - I still have the very
same trouble in with the same setup in Maverick. I suppose that would be
a new bug.
For the time being, rather than use xorg-edgers, I'm sticking to a
single monitor.
--
You received this bug notification because you are a me
As anything in xorg-edgers in Lucid would be included in a more recent
release I'm going to close this bug as fixed. As I don't think we'll get
a fix backported to lucid I'm also closing the lucid subbug.
** Changed in: compiz (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: comp
This bug report is being closed due to your last comment regarding this
being fixed with a configuration change. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
Hmm, could this be a DRI vs DRI2 limitation?
--
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/685682
Title:
[fglrx] compiz crashed with SIGSEGV in
nux::IOpenGLSurface::UnlockRect()
__
This resolve my problem. Thanks a lot.
On Mon, Jan 17, 2011 at 3:14 PM, Moustafa Chamli
wrote:
> Michael: You simply need to delete them.
>
> Log out and back in. It's possible Compiz won't be enabled, just enable
> it and it should keep working afterwards.
>
> --
> You received this bug notific
Fwiw, I did browse cursorily through other existing nvidia bug reports
but didn't spot one matching this one. So once Didier has completed his
testing, next step is to notify NVIDIA about this.
--
You received this bug notification because you are a member of compiz
packagers, which is subscribe
Yes, this should be documented. Super will be the primary key for window
management and other Unity functions.
--
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/704231
Title:
Unity steal
Public bug reported:
Binary package hint: compiz
After starting Firefox or Chrome i must always run gtk-window-decorator
because i don't have any window decoration.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: compiz-gnome 1:0.9.2.1+glibmainloop4-0ubuntu2
ProcVersionSignature: Ubuntu 2.
--
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/704602
Title:
gtk-window-decoration crashes after starting firefox or chrome
___
Mailing li
@ DavidBarth
right now its only when enabling things in compiz and its only when
enabling things not actually changing settings within the already
enabled plugins
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in ubuntu.
https://
CD Live 20110118 got this bug on IBM Thinkpad T40 ati radeon mobility
7500. Note, gnome-panel up since during boot there was a message:
"choose another session"
Jerry
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz
It would be great if you could backport the compiz workaround to
10.04LTS.
--
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/144406
Title:
some windows do not appear in the window list
_
** Also affects: compiz (Ubuntu Natty)
Importance: Low
Assignee: Jason Smith (jassmith)
Status: In Progress
--
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/659816
Title:
** Also affects: compiz (Ubuntu Natty)
Importance: Medium
Status: Triaged
** Also affects: unity (Ubuntu Natty)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in ubuntu.
h
Well, it isn't lying, you don't have a GLXFBConfig for depth 32. Do you
have something in /etc/X11/xorg.conf.d/? This appears to be a
configuration issue.
** Changed in: compiz (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of compiz
pack
** Tags added: compiz-0.9
--
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/703216
Title:
compiz crashed with SIGSEGV in g_source_get_id()
___
** Tags added: compiz-0.9
--
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/703291
Title:
compiz 9.2.1+glibmainloop4-0ubuntu2 breaks desktop-based viewport
switching
__
** Tags added: compiz-0.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/703448
Title:
Compiz doesn't work well for me in Lubuntu. No GLXFBConfig for depth
32 Launching fallback win
** Tags added: compiz-0.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/703621
Title:
Application calling GLX 1.3 function "glXDestroyPixmap" when GLX 1.3
is not supported! This is
For me, the seg-fault was caused by not having installed the compiz-kde
package. Once it was installed, compiz began to run without issues. Of
course, the Compiz default settings are now to have everything turned
off, including window decorations, so even once it began working, it
didn't look lik
confirming the issue on current natty
** Changed in: compiz (Ubuntu)
Importance: Undecided => Low
** 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:
** Changed in: unity
Milestone: 3.4 => 3.6
--
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/704231
Title:
Unity steals modifier key
___
** Attachment added: "two-focused-window.png"
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/704413/+attachment/1797967/+files/two-focused-window.png
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in ubuntu.
https://bu
Public bug reported:
This seems to happen randomly, I've seen that sometimes with unmaximized
window. particularly when you switch between workspaces.
Will try to add additional info if I can find a more reproduceable test
case.
** Affects: unity
Importance: Undecided
Status: New
Public bug reported:
1. open a first application (not maximized and which shouldn't be maximized)
-> title bar draw the close/minimize/maximize buttons with color (as the
window is focused)
2. open another application
-> title bar of the new application is drawn with colored
close/minimize/ma
** Changed in: unity
Status: Confirmed => Fix Released
** Changed in: unity
Milestone: 3.4 => 3.2.12
** Changed in: compiz (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to comp
** Changed in: unity
Importance: High => Critical
** Changed in: unity
Milestone: 3.2.12 => 3.2.16
--
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/691561
Title:
compiz crash on
** Changed in: unity
Importance: High => Critical
** Changed in: unity
Milestone: 3.2.12 => 3.2.14
--
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/693073
Title:
Panel and applic
** Changed in: unity
Importance: High => Critical
** Changed in: unity
Status: Confirmed => Triaged
** Changed in: unity
Milestone: 3.2.12 => 3.2.14
** Changed in: unity
Assignee: (unassigned) => Sam "SmSpillaz" Spilsbury (smspillaz)
--
You received this bug notification bec
** Changed in: unity
Milestone: 3.2.12 => 3.2.16
--
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/683523
Title:
compiz crashed with SIGSEGV in CompPlugin::windowInitPlugins()
__
I'm having the same problem with a 1280x1024 and 1920x1200 setup.
I've found that this also happens in reverse with the 1280x1024 screen
on the right. In this case the problem was on the 1280x1024 screen.
So for me, it seems, the problem is on the right-hand screen when
different resolutions are
** Changed in: unity
Importance: Medium => Critical
** Changed in: unity
Status: Confirmed => Triaged
** Changed in: unity
Milestone: 3.2.10 => 3.2.16
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in ubuntu.
https
The apport information is already in the report.
Unfortunatelly I can't find another way to reproduce the bug, is there any way
to make the error more visible the next time it happens?
** Changed in: compiz (Ubuntu)
Status: Incomplete => New
--
You received this bug notification becaus
This is a compiz bug which grabs the key even when the functions are returning
False:
In the unity code:
bool
UnityScreen::showLauncherKeyInitiate (CompAction *action,
CompAction::State state,
CompOption::Vecto
35 matches
Mail list logo
