** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Impish)
Importance: Undecided => High
--
You received this bug notification because
I confirm this bug. I am not able to get any smart data from my NVME,
which btw is my boot drive. This is NOT a low importance bug, please
change to high importance, as it may lead to loss of critical data. The
user should be able to know the SMART data and health of his/her NVME
drive.
I am wonde
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.ne
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.laun
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launc
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/49579
Title:
screen doesn't lock when some menu is open
To manage notifications about this bug go to
** Tags added: nvidia
** Changed in: oem-priority
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1963701
Title:
[NVIDIA][Wayland] graphic target not a
I submitted a pull request to the libwacom github repo. Here is the
URL. https://github.com/linuxwacom/libwacom/pull/481
If someone wants to fix it put the file data/isdv4-10g.tablet in
/usr/share/libwacom/. It is here:
https://github.com/linuxwacom/libwacom/pull/481/commits/c7ed96462403b17cf3
I just noticed something this morning that may or may not be relevant.
I normally have vlc running on my system and it was on and running at
and after the point where I updated to the new release. When testing
with a new user I closed down everything on my usual user. I now find
that vlc hits the
This is still occurring on 20.04 with:
AMD® Radeon rx 5600 xt
Dell U3219Q
Connected by DisplayPort
#50 describes reproduction steps
#63 describes workaround
Despite workaround, the bug *still exists* in 20.04 with single monitor
and there do not seem to be any open bugs tracking this issue.
--
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1292041
Title:
Lockscreen doesn't turn off the screen
To manage notifications about this bug g
could you install
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/2.24.32-4ubuntu4/+build/18229140/+files/libgail18-dbgsym_2.24.32-4ubuntu4_amd64.ddeb
and get another backtrace?
you can also try downgrading gtk3 then, the backtrace has more details
but the bug still doesn't really make sense
th
Additional back trace after installing additional .ddeb file. Any help?
** Attachment added: "gdb-fcl3.txt"
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+attachment/5566368/+files/gdb-fcl3.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.laun
** Tags added: nvidia-wayland
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1963701
Title:
[NVIDIA][Wayland] graphic target not able to reach
To manage notifications about this bug
[Expired for gdm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/b
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-contro
** Summary changed:
- [NVIDIA][Wayland] graphic target not able to reach
+ [NVIDIA][Wayland] graphic target not able to reach as the only monitor
connect to NV GPU only on I+N machine
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to g
19 matches
Mail list logo
