** Changed in: gtk+3.0 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
Status in “gtk+3.0” package in
This bug was fixed in the package gtk+3.0 - 3.6.4-0ubuntu2
---
gtk+3.0 (3.6.4-0ubuntu2) raring; urgency=low
* Enable Wayland backend (LP: #954352)
-- DarxusFri, 25 Jan 2013 22:48:49 +0100
** Changed in: gtk+3.0 (Ubuntu Raring)
Status: Fix Committed => Fix Released
--
> Somebody want to un-close this bug for raring? Won't let me.
done
** Changed in: gtk+3.0 (Ubuntu Raring)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net
Oh, I'm sorry but this isn't going to be possible.
Extra backends get compiled right into GDK. This means that libgtk-3-0
gets a dependency on wayland and libxkbcommon and there's no way to
split it out. It would always have been difficult to get wayland into
main as a build dep of GTK, but it rea
** Also affects: gtk+3.0 (Ubuntu Quantal)
Importance: Wishlist
Status: Confirmed
** Also affects: gtk+3.0 (Ubuntu R-series)
Importance: Undecided
Status: New
** Changed in: gtk+3.0 (Ubuntu Quantal)
Status: Confirmed => Won't Fix
** Changed in: gtk+3.0 (Ubuntu R-series)
Worked for me. (But I'm an expert and never have computer problems :D)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
Status in “gtk+3.0” package
I should say I am testing on 12.04 with unity3d and unity 2d on a laptop
with intel graphics.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
Stat
I have successfully tested the code in darxus's ppa and it works great
for the regular desktop and also allows GTK clients to run in the weston
compositor. Would be rather smashing to get this in to Quantal from the
start.
--
You received this bug notification because you are a member of Desktop
The attachment "gtk+3.0_3.4.1-0ubuntu1.dsc-
gtk+3.0_3.4.1-0ubuntu1+wayland2.dsc.debdiff" of this bug report has been
identified as being a patch in the form of a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. In
This is a debdiff from the gtk package currently in precise
(3.4.1-0ubuntu1) to my ppa which has the wayland backend enabled
(3.4.1-0ubuntu1+wayland2 in https://launchpad.net/~darxus/+archive
/wayland-gtk ). What is needed to get this in quantal?
The changes are:
1) 1 patch to default to X11 outp
Got GTK packages working with the Wayland backend enabled:
https://launchpad.net/~darxus/+archive/wayland-gtk
Thanks to a workaround from seb128 - you just need to "export
LIBOVERLAY_SCROLLBAR=0".
More info here: http://lists.freedesktop.org/archives/wayland-
devel/2012-April/003009.html
Than
Found another problem, Ubuntu's modifications to GTK+ are incompatible
with Wayland, bug #984914.
I've been tagging things that affect wayland with "wayland":
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=wayland
I've been trying to build GTK+ packages with the Wayland backend enabled:
http
** Tags added: wayland
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
Status in “gtk+3.0” package in Ubuntu:
Confirmed
Bug description:
Add
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
Status in “gtk+3.0” package i
Pierre: Thank you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
Status in “gtk+3.0” package in Ubuntu:
Confirmed
Bug description:
Add --e
I did see Eric's thread on the nvnews.net forums, but I'd been keeping
an eye on this for a while now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland back
Nvidia proposed a solution to the Nvidia proprietary + cairo-gl memory problem:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/967149
Opened as bug #967149.
Eric: Did you cause this? If so, thanks.
--
You received this bug notification because you are a member of Deskt
Eric: Go for it.
"NVidia knows about this and will not do anything." -
http://lists.freedesktop.org/archives/wayland-
devel/2012-March/002652.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad
I'd ask on nvnews for Nvidia insight.
A lot of their Linux staff post there.
http://www.nvnews.net/vbulletin/forumdisplay.php?f=14
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Now that I know that the Nvidia problem is due to Nvidia choosing to
build their driver in a way that doesn't allow shared memory...
"While not a big deal on machines with 2+GB ram on older machines with 1
GB it does represent a bit of an issue." - Bug #725434
It's seeming more reasonable to go a
Rob Bradford provided a patch to make gtk built with both wayland and
x11 backends usable:
https://bugzilla.gnome.org/show_bug.cgi?id=672358#c8 (by disabling the
wayland clipboard when both are built).
When GTK+ 3.4 is released next week it will be merged into Ubuntu
Precise. But it appears to ha
> Get the Nvidia proprietary driver to reduce memory consumption. I haven't
> touched this one.
Tech. support here: http://nvidia.custhelp.com/app/ask
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launch
Enabling the wayland and x11 backends of gtk+ simultaneously appears to
be unusable: https://bugzilla.gnome.org/show_bug.cgi?id=672361
Related to the cairo-gl vs. Nvidia proprietary problem:
A) Get cairo-gl to only load libGL when an application requests it:
https://bugs.freedesktop.org/show_b
Bug #725434 resulted in cairo-gl being disabled for causing "a 300%
increase in memory use at login as compared to previously". Comment #12
mentioned a theory that this memory problem was actually in a version of
libc nolonger used in Precise. I just tested the difference between
memory use of so
** Attachment added: "Memory usage with cairo-gl enabled"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+attachment/2893665/+files/nvidia.cairo-gl-enabled.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in
** Attachment added: "Memory usage with cairo-gl disabled"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+attachment/2893664/+files/nvidia.cairo-gl-disabled.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 i
** Attachment added: "~/.xsession-errors from using gtk+ with wayland and x11
backends enabled, and BACKEND=x11 vars set"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+attachment/2893306/+files/xsession-errors.txt
--
You received this bug notification because you are a membe
I did some testing of the previously mentioned ppa:ricotz/staging under Precise.
It is not at all usable. Due, I believe, to problems in gtk+, not the
packaging. ricotz tells me that enabling both the wayland and x11 backends for
gtk+ is just broken.
Without adding a ~/.xsessionrc, X does not
Better link for that ppa, including the warning that these packages are
risky to play with: https://launchpad.net/~ricotz/+archive/staging/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bug
https://launchpad.net/~ricotz/+archive/staging/+packages
In this repo, the gtk+ packages have the wayland backend enabled, and the cairo
packages have cairo-gl enabled.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
h
darxus, plus a small patch for gtk: the wayland backend exported some private
symbol by accident. the fix is upstreamed already.
rob, it seems we'll need cairo-gl. but there also seems to be some chances,
that the cairo-gl vs. nvidia issue was a TLS bug in libc 2.13 (at least that's
what the gen
Matthias: So what was necessary, just enabling wayland in gtk, and
enabling cairo-gl in cairo?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
St
Rob: My understanding is that for the wayland sample clients (weston),
cairo-gl is optional, and for the wayland backend of gtk it is required.
In the wayland build instructions for cairo-gl:
"The Wayland clients can render using cairo-gl, but fall back to software when
cairo-gl is not available
I don't suppose enabling cairo-gles2 instead gets around the nv bug?
Wayland will work happily w/ egl+gles2+cairo-gles2 combo..
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Tit
darxus - uch, that hurts!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
Status in “gtk+3.0” package in Ubuntu:
Confirmed
Bug description:
A
https://launchpad.net/~hasselmm/+archive/ppa/+builds?build_state=building
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
Status in “gtk+3.0” pack
It looks like there is a serious problem with enabling cairo-gl, related to the
nvidia proprietary drivers: Bug #725434 .
The cairo packager has closed a request to enable cairo-gl as wontfix due to
this problem: Bug #804379.
--
You received this bug notification because you are a member of D
ok, next problem: for whatever reason GtkSocket and GtkPlug get lost if
you build with --enable-wayland
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland bac
ok, it's more work than just passing --enable-wayland-backend:
configure: error: Package requirements ( cairo-gl) were not met:
No package 'cairo-gl' found
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https
I'd like to see Wayland in action cause X is ancient even with the newly
written stuff and composite extensions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wa
how about setting up a PPA to verify this theory?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
Status in “gtk+3.0” package in Ubuntu:
Confirm
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/9543
42 matches
Mail list logo
