This is still present for me in Ubuntu 20.04, so I do not think it is
resolved.
Moreover, through time memory usage of the app grows substantially. I
suspect there is a memory leak.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This is still a problem in Ubuntu 20.04.
I am also noticing high CPU usage and UI often triggers "this app is
frozen, kill it?" message.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
I can confirm this is not working on Bionic. vainfo output:
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_1
error: failed to resolve
** Tags removed: removal-candidate verification-needed
verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Sorry for the delay.
I have just now tested the package and can confirm that it works for me.
I can resize/scale screens and move them around and I always get "apply"
button I can use.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I made this patch for myself and it solved the problem.
** Patch added: "scaling-displays.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823857/+attachment/5254413/+files/scaling-displays.patch
--
You received this bug notification because you are a member of
Public bug reported:
I have been debugging why I do not get "Apply" button in Displays view
when my primary monitor is on the left of the external monitor, but it
appears when it is on the right. I traced the problem down to this issue
and patch:
https://gitlab.gnome.org/GNOME/mutter/issues/412
I can confirm that in 18.04 and Wayland this works as expected and only
the frame flashes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1733727
Title:
visual-bell-type
Public bug reported:
In Ubuntu artful, there is no nopasswdlogin group anymore. It seems also
that the option to configure user to not have a password is missing.
Moreover, in the login screen, "login" button is disabled if the
password input box is empty, so even if I force set an empty
It seems this one is reporting the issue:
https://bugzilla.gnome.org/show_bug.cgi?id=652580
There are few patches, but it does not like fixed.
So I do not care so much about switcher than the behavior described:
Observed behavior: Actvities overview (got by pressing the logo key),
however,
Public bug reported:
I have disabled workspaces on primary display only, and I have enabled
workspaces to span displays, in tweak tool.
Now things mostly work how I expect. Windows are isolated to the
workspace they are and I can move them between displays (monitors). The
issue is if I go into
Public bug reported:
I tried to enable visual bell, frame-flash type, by doing:
gsettings set org.gnome.desktop.wm.preferences visual-bell true
gsetings set org.gnome.desktop.wm.preferences visual-bell-type 'frame-flash'
The issue is that while visual bell gets enabled, it always flashes the
Public bug reported:
Running debsums on my machine report that /usr/lib/x86_64-linux-
gnu/old.libgbm.so.1.0.0 has changed. Sadly even running "apt-get
install --reinstall libgbm1-lts-wily:amd64 libgbm1:amd64" does not fix
the problem.
(BTW, I cannot report this against the libgbm1 package,
13 matches
Mail list logo
