They are used for different platform of different OEM. The OEM platform
owner tracks specific platform bugs by platform tag in the private bug
and we are not able to share the platform information cross OEM.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
** Tags added: 2-in-1 apport-collected jammy oem-priority wayland-
session
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Status: New => Confirmed
** Changed in: oem-priority
Importance: Undecided => High
--
You received this bug
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2026228
Title:
gnome-control-center crashed when sw
Update for summarizing current symptoms and workaround solution:
[Steps to reproduce]
1. Enable auto login through GUI ("Settings"->"Users"->"Automatic Login" to
enable)
2. reboot
3. system stop at gdm login screen
There are two symptom I found currently:
4.1 enter correct password is not able to
@Marco,
Hi, here is the steps when verifying mutter from focal-proposed:
1. Upgrade all packages to latest version in focal-updates.
2. Enable focal-proposed in source list
3. sudo apt install mutter
4. Configure external screen orientation by selecting "Portrait Right"
5. Screen orientation does
I tried to install stock 20.04.1 ubuntu with 'Install third party pkgs
(e.g. nvidia)' + enable login automatically. After a reboot because of
installation completed, the system will stuck in GDM login screen and
can't login even if typing correct password.
--
You received this bug notification be
** Changed in: oem-priority
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subs
[Summary]
Here are two scenario of auto login with groovy (20.10) daily build[1]:
1. Checked "Install third-party software" (e.g. nvidia-driver) with
enabling "Login automatically".
2. Install with default options
2.1 Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive.
2.2 Enable "Lo
Here is the debdiff.
** Patch added: "gdb3~oem-1891965.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5405674/+files/gdb3~oem-1891965.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-
[Summary]
Here are two scenario of auto login with groovy (20.10) daily build[1]:
1. Checked "Install third-party software" (e.g. nvidia-driver) with
enabling "Login automatically".
2. Install with default options
2.1 Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive.
2.2 Enable "Lo
[Summary]
Here are two scenario of auto login with groovy (20.10) daily build[1]:
1. Checked "Install third-party software" (e.g. nvidia-driver) with
enabling "Login automatically".
2. Install with default options
2.1 Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive.
2.2 Enable "Lo
I'd updated the debdiff to insert a DEP-3 header.
Here is the new debdiff.
** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5406013/+files/gdm3_3.34.1-1ubuntu2.debdiff
** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff"
** Changed in: oem-priority
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all su
I'd confirmed the regression with enabling Wayland.
Due to nvidia-driver (nvidia-driver-440) disable wayland as default, I'll
separate the verification to two scenarios.
1. Make sure the new gdm3 fixes this issue.
2. Make sure the new gdm3 without the regression
(https://gitlab.gnome.org/GNOME/g
** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407599/+files/gdm3_3.34.1-1ubuntu2.debdiff
** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/184
Hi All,
I'd confirmed this issue is be fixed by gdm3 3.36.3-0ubuntu0.20.04.1 and
passed the 30 times reboot stress test by using stress/reboot_30 from
checkbox.
The environment:
kernel: 5.4.0-47-generic
gdm3: 3.36.3-0ubuntu0.20.04.1
nvidia-driver-440: 440.100-0ubuntu0.20.04.1
GPU: VGA compatible
** No longer affects: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1874567
Title:
[nvidia] Rotating secondary monitor to portrait fails, results in
landscape
To ma
I'd some verification on this ticket.
[Steps]
1. Install an Ubuntu image (5.6.0-1027 kernel)
2. sudo apt upgrade
3. enable focal-proposed
4. sudo apt install gdm3
5. reboot
[Test scenarios]
* With attaching nVidia graphic P2000:
(NVIDIA Corporation GP106GL [Quadro P2000] [10de:1c30])
** using
** Tags added: originate-from-1898665 stella
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1873184
Title:
Wired and wireless connection details have not enough height
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1936303
Title:
[SRU] Debounce multiple rfkill events
To
/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Assignee: jeremyszu (os369510)
Status: New
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => jeremyszu (os369510)
** Descripti
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Des
This patch doesn't need to apply to jammy/impish because
debian/patches/gdm.rules-Keep-wayland-enabled-in-all-nvidia-configuratio.patch
Please let me know if my assumption is incorrect.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Description changed:
+ [Impact]
+
+ * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
+ * If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm start
the "gdm-wait-for-drm" is only maintain in ubuntu-focal also upstream
doesn't use "gdm-disable-wayland" anymore but "gdm-runtime-config"
instead.
Anyway, I will try the gdm from upstream version to see whether having
the same issue.
--
You received this bug notification because you are a member
I tried the upstream gdm on focal (60 reboot cycles) and can not
reproduce the issue.
I'm trying jammy and could reproduce this issue.
Let me build upstream version on jammy.
** Description changed:
[Impact]
* In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
ca
The issue is happening in debian/ubuntu only. Thus, I'm not sure the
upstream is correct place to discuss instead of debian/ubuntu.
This commit (536491641) works good.
| * 1c9e4c93d (HEAD, refs/bisect/bad) New upstream release
| * 4106a87d5 Update upstream source from tag 'upstream/41.0'
| |\
When I build the 536491641, I use meson build.
When 1c9e4c93d, I use gbp buildpackage.
Thus, I tried dh_quilt_patch then gbp buildpackage on 1c9e4c93d.
The issue is gone.
Based on above test, I think it's likely related to debian/rules.
Something cause it (or has higher fail rate) happens.
Also
** Description changed:
[Impact]
* In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm start
** Changed in: oem-priority
Status: In Progress => Confirmed
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO
To manage
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Importance: Undecided => High
--
You received this bug notification because you are a member of
yes, FWIK, we incline to provide the LTS branch (stable) for Ubuntu users.
For some cutting edge graphic cards, which will use 495 (since 470 doesn't
support) and the 495 will eventually upgrade to next LTS version (FWIK, 510) in
the future.
The installation logic is implemented in ubuntu-driver
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) => jeremyszu (os369510)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
u-d-c patch for jammy
** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.jammy.patch"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562733/+files/0001-Make-sure-nvidia-drm-rules-action-processed.jammy.patch
--
You received this bug n
u-d-c for impish
** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.impish.patch"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562739/+files/0001-Make-sure-nvidia-drm-rules-action-processed.impish.patch
--
You received this bug noti
u-d-c for focal
** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562740/+files/0001-Make-sure-nvidia-drm-rules-action-processed.focal.debdiff
--
You received this bug not
** Description changed:
[Impact]
- * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
+ * In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some
oem-priority
Importance: Critical
Assignee: jeremyszu (os369510)
Status: Confirmed
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: oem-priority
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priori
s/edit?disco=VxVMzfA
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
Test on my P350 with nvidia-510 on Jammy daily build with dist-upgrade.
** Patch added: "gdm.rules-Prefer-Wayland-with-NVIDIA-510.debdiff"
https://bugs.launchpad.net/oem-priority/+bug/1962523/+attachment/5564288/+files/gdm.rules-Prefer-Wayland-with-NVIDIA-510.debdiff
** Changed in: oem-priori
** Description changed:
+ [Impact]
+
+ * In Ubuntu 22.04, gdm should use Wayland by default even if proprietary
nVidia driver is in use.
+ * gdm upstream prefers Wayland if nvidia version newer than (or equal) to
510. It same as Ubuntu's strategy[1].
+
+ [Test Plan]
+
+ Steps:
+ 1. Downloa
** Summary changed:
- [Wayland][Nvidia] gdm default use Xorg in 22.04
+ [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia
installed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.laun
@Daniel,
So for lp:#1959888, user confirmed it seems be fixed by nvidia-510. It makes
sense on the patch.
The patch from comment#1 is indeed enable Wayland only if nvidia-510.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in U
m-priority
Importance: High
Assignee: jeremyszu (os369510)
Status: Confirmed
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy oem-priority originate-from-1956556 sutton
--
You received this bug notification because you ar
** Attachment added: "journal-b.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701/+attachment/5565824/+files/journal-b.txt
** Tags added: oem-priority originate-from-1956556 sutton
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** 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
** Tags removed: gdm3
** Tags added: nvidia
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia dri
Hi Daniel,
The patch from comment#1 is from upstream.
https://gitlab.gnome.org/GNOME/gdm/-/commit/dda2fbb175ca00fc4f6c4e3c149464a570e1dca4
--
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
*** This bug is a duplicate of bug 1959888 ***
https://bugs.launchpad.net/bugs/1959888
Hi Daniel,
This issue is talking about I+N desktop.
It may not same as a hybrid laptop.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 i
I did a review on the upstream MP that Daniel shared.
It looks to me that the upstream intend to disable Wayland in many of scenarios.
It contains a case:
(proprietary nvidia) + (hybrid graphics) + (laptop)
It make me feel curious that why only impact "hybrid laptop" but "hybrid
desktop/workstatio
Hi Seb,
FWIK, the fix from gdm is not mandatory.
The display-manager (inside u-d-c) will handle it.
but if any flavor which doesn't use u-d-c then gdm upstream also provide this
commit
https://gitlab.gnome.org/GNOME/gdm/-/commit/ecbd9694458194e24f356ba9d37fc4f3a515c3dd#note_1402863
to fix this i
Hi Daniel,
yes, in hybrid system, different BIOS have their own way to configure
it. We just need to make sure the memory point of efifb passed from BIOS
is correct one and it's correct in this case, the boot_vga is dGPU.
I'll risk this issue on upstream to discuss and share the upstream bug
here
** Tags added: jiayi
--
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 as the only monitor
connect to NV GPU only on I
** Tags added: jiayi
--
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/1962523
Title:
[Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia
installed
To manage notific
Still could reproduce this issue with Jammy daily build (3/13)
$ sha256sum ~/Downloads/jammy-desktop-amd64.iso
1c46933bf1837e6427f994676c60d54515c6ce011276dbfe4c5a63e427fdc2c5
/home/jeremysu/Downloads/jammy-desktop-amd64.iso
1. Install third-part drivers during the installation.
2. After insta
In daily build:
kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX
platforms 470.103.01
From comment#2:
kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 510.39.01
In latest ubuntu archive:
kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX
Mar 14 02:38:53 ubuntu ubiquity: WARNING:root:_pkg_get_support
nvidia-driver-510: package has invalid Support PBheader, cannot determine
support level
Mar 14 02:38:53 ubuntu ubiquity: WARNING:root:_pkg_get_support
nvidia-driver-510-server: package has invalid Support PBheader, cannot
determine
It seems a regression since https://launchpad.net/ubuntu/+source/nvidia-
graphics-drivers-510/510.54-0ubuntu0.18.04.1
because of
```
* debian/templates/control.in:
- Set XB-Support to PB (production branch).
```
Checking with maintainer on
https://chat.canonical.com/canonical/pl/5bheikgti7
Report a bug as https://bugs.launchpad.net/oem-priority/+bug/1964747
--
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 a
This issue has been fixed in 510.54.
For installed incorrect version, please see comment#16.
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: oem-priority
Status: Confirmed => Fix Released
** Changed in: nvidia-graphics-driv
Also submit MP to salsa
https://salsa.debian.org/gnome-team/gdm/-/merge_requests/14
--
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/1962523
Title:
[Wayland][Nvidia] gdm default use Xo
** Changed in: oem-priority
Status: Triaged => Fix Released
--
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/1962523
Title:
[Wayland][Nvidia] gdm default use Xorg in 22.04 if pro
Tested focal version
```
ubuntu-drivers-common:
Installed: 1:0.9.0~0.20.04.6
```
and the log shows
```
...
Takes 640ms to wait for nvidia udev rules completed.
```
thus, the result is PASS.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received thi
Tested impish version
```
ubuntu-drivers-common:
Installed: 1:0.9.2.4~0.21.10.1
```
and the log shows
```
...
Takes 660ms to wait for nvidia udev rules completed.
```
thus, the result is PASS.
** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done ver
ed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Importance: Undecided => High
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ub
ok, I arranged one machine to give it a try.
I will share the result here later.
BTW, I'm not able to check bug 1965246
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1959888
Title:
This issue comes from OEM partner which certifying with Ubuntu 20.04.
We may still need to consider a fix in X for 20.04 or switching to X from gdm
in 22.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bu
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to rac
Follow-up from comment#12, I can reproduce this issue on I+N (external
hdmi port wires to dGPU) on DELL-Precision-7760.
---
三 31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc27c980
of type IBusText has been finalized while it was still owned by gjs, this is
due to invalid m
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Status: New => Confirmed
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Importance: Undecided => High
** Change
Hi Daniel,
Thanks for sharing!
If there is a patch either from salsa or PPA then I can help to verify it in my
case.
** Tags added: jiayi
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/b
Hi Daniel,
In this case, do we have any ticket for nvidia to fix the GBM issue?
We would like to highlight this to nVidia.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1959888
Titl
The related issue reported when using Xorg:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1966050
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967450
Title:
** Tags added: jiayi oem-priority
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967450
Title:
When switc
"Jammy Jellyfish" - Daily amd64 (20220409)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: oem-priority
Importance: Critical
Assignee: jeremyszu (os369510)
Status: Confirmed
** Affects: mutter (Ubuntu)
Importance:
Undecided => Critical
** Changed in: oem-priority
Status: New => Confirmed
** Tags added: nvidia-wayland wayland wayland-session
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
--
You received this bug notification because you are a member of Ubuntu
Des
Confirmed the gnome will not crash but the system will back to gdm login
screen in 1st hot-plugging.
Report the bug https://bugs.launchpad.net/oem-priority/+bug/1969121
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a m
Confirmed the gnome will not crash but the system will back to gdm login
screen in 1st hot-plugging.
Report the bug https://bugs.launchpad.net/oem-priority/+bug/1969121
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Assignee: jeremyszu (os369510)
Status: Confirmed
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy jiayi nvidia oem-priority wayland
--
You rec
ed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Status: New => Confirmed
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
Yo
** Description changed:
[Steps to reproduce]
1. Install Jammy and dist-ugprade
2. systemctl suspend
3. press power button to resume
[Expect result]
system resume smoothly
[Actual result]
display glitch (please see the attachment)
+
+ Pieces of log
+ ```
+ 四 14 22:55:10 ker
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1959888
Title:
Wayland sessions can't use external monitors that
Hi Michael,
do you mean the patch to disable wayland on nVidia?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1969121
Title:
System fallback to gdm login screen when hot-plugging
and for https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969142 as
well.
BTW, I think we should say "on nvidia as boot_vga systems"?
Says, Hybrid desktop (boot from intel or boot from nvidia) or nvidia
only laptops or other scenarios.
Hybrid desktop boot from nvidia is needed to be considere
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Copied the finding from
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969142 since this
bug is created long time.
Pieces of log
```
四 14 22:55:10 kernel: NVRM: GPU at PCI::01:00:
GPU-581d669f-ec00-4588-ca5f-15ab24136974
四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, G
For comment#10:
NVreg_TemporaryFilePath means to use the specific path, if you didn't
specify it then it will default to use /tmp. (if your /tmp has enough
space to use then it's fine)
FWIK, the firefox is now from snap and the stable firefox is disable
Wayland. Thus, it could be the other proble
Hi Marcos,
For bug description:
---
[Workarounds]
* Always log into a Xorg session and if corruption occurs then type:
Alt+F2, R, Enter
*
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0
---
It should be workaround by adding "NVreg_Preser
Hi Macros,
would you please share the output of `journalctl -b` when issuing
happening?
--
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/1876632
Title:
[nvidia] Corrupted/missin
after upgrading to 42.0-1ubuntu7 and can not reproduce this issue (default X).
Selected to Wayland can not reproduce this issue as well.
** Changed in: oem-priority
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
Hi, would you please share:
1. lspci -nvk
2. /var/log/gpu-manager.log
3. journalctl -b -k
4. dpkg -l | grep nvidia
5. lsmod | grep nvidia
--
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/
Hi,
I aware you don't have "nvidia_drm" which is needed for gdm as well.
u-d-c was wait the "nvidia_drm" be probed and your nvidia driver is 340 is
quite old as what I known.
FWIK, the legacy driver should be nvidia-390 and the next is 470.
I wondering why nvidia-340 is not yet be transited to 3
ok, I aware the `nvidia-drm` should support in nvidia-340.
Did you blacklist it?
Can you check the nvidia-drm whether presenting in your system?
you could probably found it under
find ... /lib/modules/$(uname -r)/...
--
You received this bug notification because you are a member of Ubuntu
Deskto
update:
no transition plan for nvidia-340.
Then let's see why your nvidia-drm gone.
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot
but it doesn't show in your lsmod.
how about `modinfo nvidia_drm`?
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race
nope, drm is not nvidia_drm.
I don't have 5.4 + nvidia-340 environment.
Thus, I would like to get more information from you.
Could you please share
1. dkms status
2. find /lib/modules/$(uname -r) -name 'nvidia*'
3. your "/var/lib/dkms/" probably have nvidia-340 build log with your current
kernel
looks like nvidia-drm is not built in nvidia-340.
could you report the other bug for it takes 10 seconds when booting in
nvidia-340?
and we can leave the information there.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubunt
I can confirmed the original issue gone after installing the version
from comment#37
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to clutter-gst-3.0 in Ubuntu.
https
Hi Aleksandr,
sound more likely the other issue.
Since this issue is fixed, could you please report the other with attaching
logs?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1959
Daniel,
Thus, does the PPA from comment#14 can fix your case?
if it doesn't, then probably there are two issues or other patch(s) are needed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net
1 - 100 of 130 matches
Mail list logo
