** Changed in: gtk+3.0 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
h
Now with the change of plans, is it time to remove wayland from gtk+
dependencies?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about t
@bdrung, Laney: Hi, is it intended to have the udeb built with the
wayland-backend confflag too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notific
gedit and gnome-terminal actually works if you run them via dbus-launch.
dbus-launch gedit
dbus-launch gnome-terminal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland back
To run from X just run 'weston'.
To run from console first run 'sudo chmod +s /usr/bin/weston-launch' and then
run 'weston-launch' (do not run 'weston' directly!)
To run GTK applications, you first have to run 'export
GDK_BACKEND=wayland'.
Note that GTK applications does not have any window deco
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
--
That was expected. We have a main inclusion request (MIR) for
libxkbcommon, which got accepted. The package gets moved from universe
to main when an other package (in our case gtk+3.0) build depends on it.
The build is retried after the move.
--
You received this bug notification because you are
https://launchpad.net/ubuntu/+source/gtk+3.0/3.6.4-0ubuntu2/+build/4247991
looks like the build failed...
E: Unable to locate package libxkbcommon-dev
apt-get failed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Great, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bu
Thanks for your contribution. I have uploaded gtk+3.0 3.6.4-0ubuntu2
with enables the Wayland backend.
** Changed in: gtk+3.0 (Ubuntu Raring)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Branch linked: lp:~ubuntu-desktop/gtk/ubuntugtk3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https://bugs.lau
The libwayland0 MIR has been closed "fix committed". So everything
should be ready to enable the wayland backend in the gtk package? Iain
/ Benjamin?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954
Thanks for doing it. It has been on my todo list, but I haven't found
time to do it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about
There is a MIR for libxkbcommon now.
LP: #1102678
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https://bugs.launc
Looks like Timo did the libxkbcommon v0.2.0 package. So next step is a
MIR for it? Benjamin?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notificat
yay wayland support and eventually broadway :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https://bugs.launchpa
We discussed the enablement of the Broadway backend on #ubuntu-x and
answered in bug #933641 that enabling the Broadway backend makes sense
for GTK >= 3.7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
While you are at it, why not also enabling the Broadway backend?
It does not require any additional dependency.
I'm using a broadway-enabled Gtk for some months now and I did not ran into any
problem.
The relevant bug report is LP: #933641
I have a PPA here: https://launchpad.net/~malizor/+archiv
Not particularly, thanks :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
I talked to the X team. The library was experimental at the beginning,
but that has changed. Timo Aaltonen promised to update the package to
the upstream release 0.2.0. I will going to prepare a MIR, unless
someone else want to do it (Darxus, maybe?).
--
You received this bug notification because
git repo> Yeah, that's probably true. Benjamin is going to talk to the X
team. There's a proper release now which we could likely package. I
imagine he'll report his findings back to the bug soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
diff
** Patch added: "gtk+3.0_3.6.2-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+attachment/3477854/+files/gtk%2B3.0_3.6.2-0ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
I think that libxkbcommon0 description is out of date, probably written
before there was a release, when the package was built from a git repo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Tit
I looked again. See the wdiff of the Depends line after enabling wayland
Control files of package libgtk-3-0: lines which differ (wdiff format)
--
Depends: libgtk-3-common (= [-3.6.2-0ubuntu1),-] {+3.6.2-0ubuntu2),+}
libatk-bridg
> 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Ti
Somebody want to un-close this bug for raring? Won't let me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https:
Yay.
In case anybody else was trying to look up how libwayland0 ended up in main:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/810217
(MIR = Main Inclusion Request)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
On Tue, Jan 08, 2013 at 11:10:32PM -, Benjamin Drung wrote:
> libegl1-mesa depends on libwayland0 in raring. Purging libwayland0 on
> raring would purge empathy and totem. Therefore we will have libwayland0
> installed on the installation media. I see no reason to avoid letting
> gtk depend on
libegl1-mesa depends on libwayland0 in raring. Purging libwayland0 on
raring would purge empathy and totem. Therefore we will have libwayland0
installed on the installation media. I see no reason to avoid letting
gtk depend on libwayland0, but allow libegl1-mesa to depend on it.
I will enable the
Iain, are you aware the mesa packages already depend on libwayland0?
Shouldn't that make it okay for gtk to depend on libwayland0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable
Iain, could you say what exactly the reasons are for not wanting the gtk
package to depend on a wayland package?
I posted about this problem here:
http://lists.freedesktop.org/archives/wayland-devel/2013-January/006888.html
A couple people have said what they think the reasons are in replies. I
The GTK+ folks closed the above bug, to split the wayland backend into a
dynamically loadable library, "wontfix" saying "No".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayla
Thanks. GTK+ bug opened:
https://bugzilla.gnome.org/show_bug.cgi?id=690381
** Bug watch added: GNOME Bug Tracker #690381
https://bugzilla.gnome.org/show_bug.cgi?id=690381
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Hey,
On Mon, Dec 17, 2012 at 06:17:37PM -, Darxus wrote:
> Fred: I think you misunderstand.
>
> I don't think Iain is saying this can't be fixed. Somebody please
> correct me if I'm wrong, but it sounds to me like the solution which
> would make Iain happy, and not cause any problems for an
For gtk+3.0 to depend on wayland in the Ubuntu repos would require that
none of the proprietary drivers force the removal of wayland. I suppose
this could be done in such a way that wayland would be installed but
broken with the proprietary drivers installed, assuming the session and
all programs f
Fred: I think you misunderstand.
I don't think Iain is saying this can't be fixed. Somebody please
correct me if I'm wrong, but it sounds to me like the solution which
would make Iain happy, and not cause any problems for anybody else,
would be if GTK+ built its Wayland backend into a separate d
You're merely postponing the inevitable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Then let it have a dependency on wayland and libxkbcommon.
It will have to sooner or later anyway. Just a matter of time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland b
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
For Raring, we need to cherry pick
e5b88f1bdd570e9f411a8be41199adceb950c61c to work with wayland 1.0's API.
I'm doing a test build of this now and will upload to a PPA if it
succeeds. I'll then run this GTK for a bit and if there's no problems I
will upload to raring
--
You received this bug noti
Enabled 1.0.2?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bu
Updated ppa for gtk+3.0_3.5.18-0ubuntu3. debian/patches/series didn't
apply cleanly from previous debdiff, reason and solution were obvious.
** Patch added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+attachment/3338831/+files/gtk%2B3.0_3.5.18-0ubuntu3.dsc-gtk%2B3
Iain: Great, thanks. So I should remind you around when Quantal is
released?
Updated PPA for 3.5.18-0ubuntu2: https://launchpad.net/~darxus/+archive
/wayland-gtk-quantal
** Patch added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+attachment/3325626/+files/gtk%2
I propose we revisit this at the start of R-cycle. I've subscribed to
this bug, so feel free to ping if I forget to do that then.
** Changed in: gtk+3.0 (Ubuntu R-series)
Assignee: (unassigned) => Iain Lane (laney)
--
You received this bug notification because you are a member of Ubuntu
Bug
Updated PPA to gtk+3.0 - 3.5.18-0ubuntu1. I see there's a 3.5.18-0ubuntu2 here:
https://launchpad.net/ubuntu/quantal/+source/gtk+3.0/3.5.18-0ubuntu2
But not sure how to tell if I should use that or just wait for it to get to the
archives.
Updating sure is a lot faster when just applying the debd
Debdiff from gtk+3.0_3.5.16-0ubuntu1 to
gtk+3.0_3.5.16-0ubuntu1+wayland0. Nothing new from last time, except I
specified v0.95 or newer for the libwayland build dependency.
** Patch added:
"gtk+3.0_3.5.16-0ubuntu1.dsc-gtk+3.0_3.5.16-0ubuntu1+wayland0.dsc.debdiff"
https://bugs.launchpad.net/u
Updated PPA from 3.5.12-0ubuntu3+wayland0 to 3.5.16-0ubuntu1+wayland0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go t
I have still not experienced any X problems with the Wayland-enabled
GTK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug g
What needs testing (by you):
We need to verify that enabling the wayland backend does not cause regressions
(things breaking that weren't broken) with X. Verifying that things work with
wayland is not really relevant to this bug.
for now, the question is more: does turning wayland backend on
Sebastien: Because all the chicken and egg problems with wayland are
annoying, and this is a step we can take in the right direction. And
it's a huge part of the usability of wayland - which is expected to be
used by clients primarily through GTK+ and Qt. And people were testing
it and saying it
@Darxus: thanks for your work on that btw, is there any reason you want
it in the main archive? It seems like a testing ppa is the right place
for that at the moment...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
That cross-fired over IRC upstream discussion, so to summarize my
position:
- we (desktop team) have enough to work on to keep busy without that
- it seems no other distribution enable wayland (which means in reality it gets
little testing, they might also have reasons to not enable it)
- wayland
It's still unclear whether enabling wayland support would cause
regressions in GTK. Wayland support isn't a priority for 12.10, and even
Fedora doesn't enable the Wayland backend yet. It's after feature freeze
so the cost/benefit analysis makes a feature freeze exception being
granted for this unli
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+3.0 (Ubuntu R-series)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Tit
** 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)
GTK3 from the PPA it works for me too, is there any reason not to go
with it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this b
I'm running GTK with --enable-wayland from Darxus PPA mentioned above.
It seem to work. :)
I would love to see GTK compiled with --enable-wayland on Quantal. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Patch added: "debdiff from the existing official gtk package to mine with
the wayland backend enabled"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+attachment/3277191/+files/gtk%2B3.0_3.5.12-0ubuntu3.dsc-gtk%2B3.0_3.5.12-0ubuntu3%2Bwayland0.dsc.debdiff
--
You received th
GTK+ PPA with --enable-wayland-backend for Quantal:
https://launchpad.net/~darxus/+archive/wayland-gtk-quantal
As expected, just requires adding --enable-wayland backend.
And --enable-x11-backend (because if you do wayland and not x11 it disables
x11).
And less expected, there's an apparent bug i
** Changed in: gtk+3.0 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https:
** Bug watch added: Debian Bug tracker #663749
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663749
** Also affects: gtk+3.0 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663749
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
Wayland and Weston 0.95 packages are in Quantal.
I just noticed feature freeze was two days ago. I opened this bug five
months ago, and created a ppa and debdiff demosntrating the change three
months ago. Please enable wayland in the gtk packages for quantal.
--
You received this bug notificat
It looks like you're now producing Quantal specific gtk packages, and
wayland is still not enabled (
http://archive.ubuntu.com/ubuntu/pool/main/g/gtk+3.0/gtk+3.0_3.5.10-0ubuntu1.debian.tar.gz
)
Can you enable wayland in the quantal gtk package now?
--
You received this bug notification because y
Great, thanks. Since all necessary patches were in master by 2012-04-18
I'd expect them all to be in 3.5.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To ma
Quantal work has not started for that long but gtk 3.5 is being prepared
for upload (in fact it's ready for a bit but some theming changes mean
that unico needs to be updated, the current version segfaults with the
new gtk), it should go in quantal next week (this week changes are
reduced for alpha
Sebastien: But I believe it's entirely appropriate for Quantal. Why
hasn't it been applied to that yet? It's been almost two months.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
En
Unsucribing sponsors that's not a patch suitable for a stable update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go t
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notificati
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 Ubuntu
B
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
Pierre: Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage n
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 Ubunt
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enabl
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
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: "~/.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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifica
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable way
darxus - uch, that hurts!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/
https://launchpad.net/~hasselmm/+archive/ppa/+builds?build_state=building
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug g
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 U
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage
1 - 100 of 104 matches
Mail list logo
