As geez did above, I installed libmutter-7-0, mutter, and mutter-common
from groovy-proposed. Zoom now opens and seems to run fine, which is
the snap that, for me, previously did not open. There seems to be a
draw issue that I have never had before though. When I close the
application, the
I also upgraded everything from the proposed repo and tested. This issue
is fixed for me as well. I power cycled each monitor monitor (I have
two.) in succession, and the output device selected remained the
motherboard line out throughout. Line out was also selected at boot,
where previously at
I think this is a duplicate of bug 1847570. If you agree, will you mark
it as a duplicate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849157
Title:
Default sound output device is never the
*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570
** This bug has been marked a duplicate of bug 1847570
PulseAudio automatically switches to HDMI sound output on login
--
You received this bug notification because you are a member of Ubuntu
Bugs,
In case it's helpful, I posted a bug about this (but, perhaps,
incorrectly as an ALSA problem) with my Alsa and PulseAudio information:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846290
Above, it was mentioned that perhaps this is regards to module-switch-
on-connect. FWIW, when
Apologies for changing status from triaged to confirmed. That was not my
intention. Next time I get an email about a bug update, I'll wait to
get to my pc, rather than checking on mobile.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: mutter (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847551
Title:
Mutter 3.34.1 broke Night Light, screen color profiles
To manage
** Changed in: gnome-settings-daemon (Ubuntu)
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/1846249
Title:
Num lock works in reverse on Ubuntu 19.10 wayland
To
Prior to filing a bug myself I searched launchpad for "num lock", so
this bug with "numlock" in the title did not show up. The bug I filed
is Bug #1846249. I am experiencing the same issue under 19.10 when
logged in with Wayland. The problem is not present in an X session. In
fact I can do the
** Package changed: x11-utils (Ubuntu) => gnome-settings-daemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846249
Title:
Num lock works in reverse on Ubuntu 19.10 wayland
To manage
When I am logged into Wayland (and therefore experiencing the issue, the
output of gsettings list-recursively | grep -e numlock is this when the
numlock led is off but the numbers work anyway:
org.gnome.desktop.peripherals.keyboard remember-numlock-state true
Essentially, it seems like when logging in under Wayland, the system
remembers the status of the numlock LED, BUT it always starts the system
with the numlock functionality disabled. This is why the LED is out of
sync if it's on when logging on, but not if it's off when logging in.
--
You
When I am logged into an X session (and therefore not experiencing the
issue), the output of gsettings list-recursively | grep -e numlock is
this when the numlock led is off and the numbers don't work:
org.gnome.desktop.peripherals.keyboard remember-numlock-state true
Public bug reported:
I have two monitors hooked up to an AMD RX570 via displayport. In the
sound settings they appear as "Ellesmere HDMI Audio [Radeon RX
470/480/560/570/580/590]" and Ubuntu 19.10 selected one of them as the
output device by default. My speakers are connected to a green mini-
I have also noticed that the num lock button seems to sync properly IF
num lock is off at boot. If I turn num lock after boot, then the key
and indicator light function the way i expect (light on == numbers;
light off == arrows, etc). If num lock is on at boot, then the
indicator light and key
Public bug reported:
I updated to the Ubuntu 19.10 beta yesterday, and since updating, the
num lock key on my keyboard (DASKeyboard Prime 13 from System76) is
reversed. When it is on (indicator light is lit), the numbers do not
work, but the arrows, page up/down, home, end keys, etc. work. When
Public bug reported:
I am running Ubuntu 19.04 with an AMD RX570, using the open source
driver, and I have two Dell U2415 monitors connected via DisplayPort
(not daisy-chained). Gnome Night Light only changes the color on the
monitor dubbed "Monitor 1" in display settings (though the monitor I
Public bug reported:
Background:
I am running a fully updated 16.04.1 installation of Ubuntu using open
source nVidia drivers. When I press the power button on my PC to wake
the computer from suspend, the login screen appears and freezes. The
box around my username becomes somewhat opaque and
18 matches
Mail list logo
