** Changed in: libwnck
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/63208
Title:
Patches For Compiz/Beryl Compatibility
To manage notifications about this bug
** Changed in: libwnck
Importance: Unknown = Medium
--
Patches For Compiz/Beryl Compatibility
https://bugs.launchpad.net/bugs/63208
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
closing the bug, those changes are not something that should still be
used in hardy
** Changed in: libwnck (Ubuntu)
Status: Confirmed = Invalid
** Tags removed: qa-hardy-desktop
** Tags added: qa-hardy-desktop
** Tags removed: qa-hardy-desktop
--
Patches For Compiz/Beryl Compatibility
** Tags added: qa-hardy-desktop
** Tags removed: qa-hardy-list
--
Patches For Compiz/Beryl Compatibility
https://bugs.launchpad.net/bugs/63208
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Tags added: qa-hardy-list
--
Patches For Compiz/Beryl Compatibility
https://bugs.launchpad.net/bugs/63208
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Sebastien, I understand what you are saying re: Compiz/Beryl not being
supported. But, I think that's a bad position to take. Compiz/Beryl
*WORKED* in edgy, and the edgy libwnck packages *have the patches
applied*. You can't enable functionality like this in one version, then
disable it in the
Compiz/Beryl *WORKED* in edgy, and the edgy libwnck packages *have the
patches applied*.
no they didn't, you likely installed the patched version from the non-
Ubuntu compiz archive. We had some discussion with the guy working on
those packages after tracking a bunch of crasher sent on launchpad
Sebastien is correct. Ubuntu never had these patches. It would be nice
if they got added since beryl is in the repository, even if it is in the
unsupported parts.
There is a bug open in the beryl-project for this. I added a comment to
explain.
http://bugs.beryl-project.org/ticket/1971
Ciao!
Compiz/Beryl *WORKED* in edgy, and the edgy libwnck packages *have
the patches applied*.
no they didn't, you likely installed the patched version from the non-
Ubuntu compiz archive. We had some discussion with the guy working on
those packages after tracking a bunch of crasher sent on
0ubuntu1.1 is a non maintainer upload revision and has not been used in
any Ubuntu desktop upload, you can look at the changelog of the package
if you want to know from where it's coming
compiz is working, what is not is the wnck integration when using the
cube. Using the cube is only an option,
The workaround posted by Christian Holtje is the one I am using, and
Sebastian Bacher is right -- it sucks for many reasons, but its better
than having a non-functioning desktop. So I'm stuck with it until
libwnck packages are fixed in feisty (which I'm hoping is sooner rather
than later --
the Ubuntu desktop is functioning correctly, you decided to install a
window manager that requires non supported workarounds which creates
your need
--
Patches For Compiz/Beryl Compatibility
https://bugs.launchpad.net/bugs/63208
You received this bug notification because you are a member of
Note that if you use non official packages you will get a new set of
bugs, you will not get official support so don't open new bugs in
launchpad and it might break upgrades to the next version of Ubuntu
--
Patches For Compiz/Beryl Compatibility
https://bugs.launchpad.net/bugs/63208
You received
version 2.18.0-0ubuntu1 is still broken; it does not understand virtual
workspaces correctly and does not allow windows to be selected as
Always on Visible Viewport, Move to Another Viewport, etc when run
with beryl/compiz. Downgrade to 2.16.1-0ubuntu1.1 (from edgy) solves
this problem for now,
The feisty package ships one of those patches now:
libwnck (2.17.92-0ubuntu2) feisty; urgency=low
.
* debian/patches/80_from_bugzilla_add_action_above.patch:
- patch from http://bugzilla.gnome.org/show_bug.cgi?id=352383,
useful for compiz (Ubuntu: #63208)
--
Patches For
My personal opinion in this matter (as I told you on IRC too): it's
better to get these changes upstream first.
The rationale is very simple: you add API, enums and structs, you change
API severely, which is generally just fine. But what if upstream decides
to implement this differently? We can't
** Changed in: libwnck (upstream)
Status: Unknown = Confirmed
--
Patches For Compiz/Beryl Compatibility
https://launchpad.net/bugs/63208
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: libwnck (Ubuntu)
Importance: Undecided = Wishlist
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: Unconfirmed = Confirmed
** Bug watch added: GNOME Bug Tracker #352383
http://bugzilla.gnome.org/show_bug.cgi?id=352383
** Also affects: libwnck (upstream) via
** Description changed:
Compiz/Beryl both need a patched libwnck to have a proper context menu.
These patches to add always on current viewport, move to current
viewport, setting the appearance of a window and moving the window.
Without them several features of compiz/beryl are not
The patches are not trivial, could anybody working with them could
provide some description of why they are required, what the changes
achieve, etc?
--
Patches For Compiz/Beryl Compatibility
https://launchpad.net/bugs/63208
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The above patch fixes the above checkbox to work with compiz... from within the
patch itself:
There's no _NET_WM_ACTION_ABOVE hint so always add it if window manager claims
to support_NET_WM_STATE_ABOVE
The viewport patch gives libwnck support for viewports which are used by
compiz/beryl
21 matches
Mail list logo
