Martey: Yes, the bug will hit you after you returned to Metacity for a
short period. In particular, this happens if Compiz cannot start because
of a driver problem, because before you fix it you need Metacity to run
instead. But what I said is that if you still suffer from this bug,
disable the
I can confirm it too on karmic
on every reboot, i have to do a compiz --reload
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'd like to be sure we agree on the problem here. If you want to use
Compiz, just disable Metacity compositor in GConf (using gconf-editor,
under /apps/metacity/general/compositing_manager). If you want to use
Metacity, just turn off desktop effects, and then set Metacity as a
compositor or not
On Friday 29 May 2009 23:48:57 Milan wrote:
If you want to use Compiz, just disable Metacity compositor in GConf (using
gconf-editor, under /apps/metacity/general/compositing_manager).
I want to use Compiz *AND* Gnome-DO (with composite so it has the Glassy
skin).
--
Hi, I'm BUGabundo, and I
Milan, comment #22
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/178953/comments/22
suggests that this is not the case. I found this bug because compiz
could not load because of a graphics driver issue. Even when that issue
was resolved, compiz still refused to load. It was not until I
I would just like to note that this is still an issue in Karmic with
compiz 1:0.8.2-0ubuntu11.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks!
Took your advice, my report bug 363517
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
OK, sorry for being so incredibly late about this but hey, better late
than never!
I disabled the blacklist and am STILL having problems. I ran compiz from the
Terminal, here are the errors:
compiz
Checking for Xgl: not present.
xset q doesn't reveal the location of the log file. Using fallback
Bobby: the bug you experience is not the one reported here. Please open
a new report, and there somebody will be able to help you. Thanks!
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member
Bobby, to force compiz to run, you should disable the blacklist. It
works on my latop, which is also Intel GM965. However, some effects
(blur, rain...) don't work, and sometimes your framerates drops really
low. Overall its ok though. (I simply commented the blackline in the
compiz script, all the
I can confirm this in Jaunty.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Results of compiz-check:
Gathering information about your system...
Distribution: Ubuntu 9.04
Desktop environment: GNOME
Graphics chip: Intel Corporation Mobile GM965/GL960 Integrated
Graphics Controller (rev 0c)
Driver in use: intel
Rendering method: AIGLX
I was angry beacuse of this! I'ce searching why compiz wont start and
found compiz-check script, what helped me. This bug is really stupid.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a
I can confirm this bug also in Intrepid and the workaround.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I confirm this bug, and it's present in intrepid.
If I running metacity and execute this :
gconftool-2 --type bool --set /apps/metacity/general/compositing_manager
true
Ok, I'am running metacity with compositing, but If I try :
System-Preferences-Appearance-Effects Tab and Try to activate any
It seems that this could be a real compiz bug, and it still affects
Intrepid. Marking the compiz task as confirmed again, so it doesn't
fall all the way off the radar.
** Changed in: compiz (Ubuntu)
Importance: Undecided = Medium
Status: New = Confirmed
--
compiz doesn't start if
I'd just like to point out that this bug isn't really fixed. That crash
is only tangentally related to the main bug.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug was fixed in the package metacity - 1:2.23.34-0ubuntu1
---
metacity (1:2.23.34-0ubuntu1) intrepid; urgency=low
* New upstream release
- Fix possible compositor crash (LP: #178953)
-- Pedro Fragoso [EMAIL PROTECTED] Tue, 17 Jun 2008 17:17:05 +0100
** Changed in:
I am no expert at this, but the problem seems to be quite simple:
xrender_unmanage_screen in src/compositor/compositor-xrender.c always
calls meta_screen_unset_cm_selection which calls XSetSelectionOwner with
None as the owner. It should only do this when giving up the compositor
selection
Compiz fails to check return code of XSetSelectionOwner which is
returning it a low-level X error.
** Changed in: compiz (Ubuntu)
Status: Invalid = New
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification
(Sorry, that wasn't a reply to crdlb; I only just got the notification
email.)
@crdlb: Your first paragraph sounds like a good solution. I'll try it
out this evening and see what I find.
Your second para is entirely correct, of course, but a failure there
doesn't necessarily mean that it's the
Here are my thoughts.
Part one, the background reading: It seems to me after a while of
digging through the ICCCM that Travis Watkins was incorrect back in
December when he said that Metacity was not giving up control of the
compositor selection. Section 2.8 of the ICCCM says that anyone who
Metacity compositing manager is enabled by default if compiz fails.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
With trunk it causes Metacity to crash (it may well have done in earlier
situations too, since the session manager sees Metacity going down and
brings up another one, so crashes can be invisible). This is not a
happy situation. I'm escalating.
Expect some kind of patch by tonight, I hope.
--
** Changed in: metacity
Status: Confirmed = In Progress
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Patch to fix the segfault is committed to upstream trunk, but it still
doesn't let Compiz accept the CM selection! I shall continue to
investigate, and hope to get more information to you tomorrow.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
Recently Compiz Fusion stopped working on my computer (Ubuntu 8.04
Hardy). Whenever I tried to re-enable it, a message appeared saying that
Visual Effects could not be enabled. I discovered the reason was
Metacity compositing had somehow been enabled. I definitely did not
enable Metacity
Max, the compositor is enabled by default. So if compiz just segfaulted
or got replaced by metacity in any case, it would stay. Tilll you do
something about it, that is.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug
@qinjuehang: Please don't say the compositor to mean Compiz, in a
Metacity bug about Metacity's compositor. (I assume that's what you
mean from context.) It does muddy the waters rather.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You
@max
By entering
$ gconftool-2 --type bool --set
/apps/metacity/general/compositing_manager true
you *activate* metacity's abilities to work as compositing manager. By
$ gconftool-2 --type bool --set
/apps/metacity/general/compositing_manager false
you disable this feature again. After you
@qinjuehang: I'm afraid I don't understand. What would stay? And which
compositor? The fact of the matter is, Ubuntu is supposed to allow me to
enable Visual Effects through the Appearance config dialog, but it
wouldn't until I typed an arcane command in a terminal:
gconftool-2 --type bool --set
Chris, thank you for your reply but I think that you misunderstand. I
did not ever activate metacity's abilities to work as a compositing
manager. It somehow got enabled on its own, possibly after an update
installed through the update manager. I therefore had to disable
metacity's compositing
** Changed in: metacity
Status: New = Confirmed
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: GNOME Bug Tracker #530702
http://bugzilla.gnome.org/show_bug.cgi?id=530702
** Also affects: metacity via
http://bugzilla.gnome.org/show_bug.cgi?id=530702
Importance: Unknown
Status: Unknown
--
compiz doesn't start if metacity compositor is enabled
** Changed in: metacity
Status: Unknown = New
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm that, this bug is still present in final version of hardy.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
HI,
you may find turning off metacity's compiz module resolves this issue
or at least it did for me.
/apps/metacity/general/compositing_manager set to false in gconf.
Your results may vary,
Neal
On Tue, 2008-04-29 at 09:30 +, Miłosz Kosobucki wrote:
I can
In theory it would, because there is no compositor to fight with compiz,
but the problem is that it is turned on by default. For users who know
what they are doing it won't cause much more pain than 20 mins figuring
out the problem, but for less savvy users this is a potential problem.
--
compiz
Thomas: according to the wm-spec and the ICCCM, a composition manager
must take ownership of the _NEW_WM_CM_Sx selection, and relinquish it on
request to another composition manager. Here are the relevant links:
* http://standards.freedesktop.org/wm-spec/wm-spec-1.4.html#id2552725
*
Oh, wonderful. Thanks for finding that. I'll see about implementing it
soon (unless Iain does).
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can confirm that the above work around fixes the problem. Not ideal
though.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
A temporary workaround is not to put metacity into restart style in
sessions, and instead of compiz --replace, use killall metacity;
compiz --replace. They must be merged in 1 command because if metacity
is killed, it strangely becomes impossible to type at all.
--
compiz doesn't start if
My last comment wasn't completely accurate, the problem is kwin does not
look for or set this selection so you can do crazy things like run the
kwin compositor at the same time as xcompmgr.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You
Kwin 4.0 can replace compiz and compiz can replace Kwin 4.0 when kwin is
in compositing mode. Metacity is the odd man out here.
** Changed in: compiz (Ubuntu)
Status: Incomplete = Invalid
** Changed in: metacity (Ubuntu)
Status: Incomplete = Confirmed
--
compiz doesn't start if
Any news on this?
** Changed in: metacity (Ubuntu)
Status: New = Incomplete
** Changed in: compiz (Ubuntu)
Status: New = Incomplete
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are
Still happening with up-to-date hardy install
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Does it work with kwin? If it does, I'll see how they do it.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Metacity is not giving up control of the compositor selection.
** Changed in: metacity (Ubuntu)
Sourcepackagename: compiz = metacity
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of
This is not, as far as I can see, a Metacity problem. Compiz is failing
to start because it sees another compositor is running. I am not closing
the metacity bug here because I may be wrong, but I will check when I'm
less immediately busy.
** Also affects: compiz (Ubuntu)
Importance: Undecided
Compiz code for taking over as composite manager:
XSetSelectionOwner (dpy, cmSnAtom, newCmSnOwner, wmSnTimestamp);
if (XGetSelectionOwner (dpy, cmSnAtom) != newCmSnOwner)
{
compLogMessage (d, core, CompLogLevelError,
Could not
50 matches
Mail list logo
