This bug is still present.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename: trusty
$ apt-cache policy xscreensaver
xscreensaver:
Installed: 5.15-3ubuntu1
...
--
You received this bug notification
Possibly relevant from the xscreensaver faq:
https://www.jwz.org/xscreensaver/faq.html#popup-windows
The window manager I'm using is metacity 1:2.34.13-0ubuntu4.1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xscreensaver in Ubuntu.
** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
** Bug watch added: www.eglibc.org/issues/ #23
http://www.eglibc.org/issues/issue23
** Also affects: eglibc via
http://www.eglibc.org/issues/issue23
Importance: Unknown
Status: Unknown
--
You
Why is this being discussed on ubuntu's bug tracker, instead of
wayland's, or the wayland mailing list. Or even the wayland IRC
channel. You're both often in there.
min2: Using scalable vector graphics just implies using a non-raster
graphics format. It does not require dealing with pointer
Steve, I originally opened this bug, and then realized my main problem
was failure to properly detect my monitor: bug 958439. You may want to
look in that direction. Monitors *should* be communicating their
capabilities to the computer, and at that point it should be easy for
the OS to determine
The bug I opened for failed monitor detection was bug 958439.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/958424
Title:
[regression] Can't change refresh rate 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
Public bug reported:
Ran overnight, 9 hours, looks like it has scanned 7 of my backup
directories and is working on the 8th. There are 44.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: baobab 3.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-utils in Ubuntu.
https://bugs.launchpad.net/bugs/986597
Title:
Way too slow scanning drive
Status in “gnome-utils” package in Ubuntu:
New
Bug description:
Ran overnight, 9
I rebooted to make sure caches were cleared.
# /usr/bin/time du dancer-2011-03-01 panic-2011-03-01 panic-2012-01-01
dancer-2010-12-01 panic-2011-02-01 panic-2010-11-29 panic-2012-02-01 du.out
9.32user 32.55system 7:52.79elapsed 8%CPU (0avgtext+0avgdata
1577136maxresident)k
So it takes 8
Getting The partition is misaligned by 506880 bytes. 4tb partition on
a raid 0 of two 2tb drives, created by palimpsest (gnome disk utility).
On Oneric.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
-
gtk-3.4.1-patched.txt
robster Darxus, that crash is in the ubuntu code - it assumes that its
running under X11 .. /usr/lib/liboverlay-scrollbar3-0.2.so.0 is the
ubuntu scroll library
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Tags: wayland
--
You received
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:
Wayland segfault. (After
patching to default to X11 before Wayland, and remove the cairo-gl
dependency.)
- Backtrace: http://www.chaosreigns.com/wayland/dl/gdb-
- gtk-3.4.1-patched.txt
-
robster Darxus, that crash is in the ubuntu code - it assumes that its
running under X11 .. /usr/lib
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
** Also affects: gnome-games (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-games in Ubuntu.
https://bugs.launchpad.net/bugs/979066
Title:
Wayland support
Status in
** Tags added: wayland
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/975713
Title:
Doesn't work with wayland
Status in “gnome-disk-utility” package in Ubuntu:
New
Bug
** 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
Public bug reported:
palimpsest: symbol lookup error: /usr/lib/libunique-3.0.so.0: undefined
symbol: gdk_x11_display_get_startup_notification_id
gdk_x11_ and Xlib calls need to be wrapped in both build-time and run-time
backend checks to work with wayland:
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/975713
Title:
Doesn't work with wayland
Status in “gnome-disk-utility” package in Ubuntu:
New
Bug description:
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
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
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
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.
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
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:
Thanks.
** Changed in: gparted (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/958196
Title:
status window
Public bug reported:
First thing I noticed when booting Precise was the screen flickering.
Yes, I'm still using a CRT. I don't see any way to make the flickering
go away by setting the refresh rate to something sane (for a CRT).
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package:
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/958424
Title:
Can't change refresh rate in Displays
Status in “gnome-control-center” package in Ubuntu:
New
Bug
Looks like the problem is automatic monitor detection, not inability to
manually configure refresh rate. Oneric does fine with auto-detection.
It detects my monitor as a 'Viewsonic Corporation 20'. Precise doesn't
detect it. It's a Viewsonic G220fb.
** Changed in: gnome-control-center (Ubuntu)
** 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 member
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
** 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 in
** 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
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
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.
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.
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
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
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
Public bug reported:
Add --enable-wayland-backend to build flags. I believe this is all
that's necessary for wayland to work with the existing Precise gtk
packages.
Wayland has one released version, 0.85, which is in the precise
archives: https://launchpad.net/ubuntu/+source/wayland/
I'm told
You're right, I used the wrong word. And I'm not familiar enough with
nautilus to know there are different sidebar modes. Sorry I was
unclear.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Seriously? Did you read the bug? In what way were those steps for
reproducing the problem, expected behavior, and encountered behavior,
not entirely clear?
1: Specific actions for reproducing the problem:
Click Places.
Click Home Folder.
Right click anything in your home folder - any file or
43 matches
Mail list logo
