Actually, I just checked gnome-online-accounts in the gnome-control-
center under X11 nvidia and it is also broken for the Google login.
Clicking the Google Account under the Online Accounts options, produces
and empty window whereas under Wayland nvidia, the sign in content is
displayed. So
FYI, I see that same bug, with no content in the Help application, for
both the 6.5.0-5.5 and 6.5.0-6.6 kernels. Only resorting to the
change...
Exec=env WEBKIT_DISABLE_COMPOSITING_MODE=1 yelp %u
or using Wayland suppresses the bug.
--
You received this bug notification because you are a
FYI, I am running mantic on a workstation with secure boot enabled for
the second drive containing Windows 11 in case that might have some
impact on the bug. The linux debs that are installed are...
ii linux-base4.5ubuntu9
all
** Attachment added: "yelp nvidia bug.png"
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+attachment/5705507/+files/yelp%20nvidia%20bug.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
I still see the bug with your build. One correction though. Apparently
my proposed fix of changing...
* debian/control.in: Bump Standards-Version to 4.6.2
is insufficient. It seems that my previous workaround of changing
/usr/share/applications/yelp.desktop to contain...
Exec=env
So I assume the blank windows in the Help application under X11 using
the nvidia drivers on Mantic would be resolved if the yelp package were
rebuilt with...
debian/control.in: Bump Standards-Version to 4.6.2
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
This behavior is seen for both a dist-upgrade of Ubuntu 23.10 from 23.04
or for a clean install of Ubuntu 23.10.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/bugs/2037633
Title:
Help
Public bug reported:
The Help browser in the dock on Mantic produces an empty window without
content when launch under X11 using the nvidia-driver-535
535.104.05-0ubuntu4 video drivers. If I logout and login back in under
Wayland, the Help browser behaves normally and produces the expected
Daniel, I disagree. This bug is actually about the fact that the test
crafted in /lib/udev/rules.d/61-gdm.rules doesn't parse as expected in
udev. We also should probably file a bug report against upstream udev as
the changes added to support escaped quotes in #6890 aren't robust
enough.
--
You
Note that I stumbled onto the above fix after noticing the example shown
for the udev escaped quoting support showed an example with double
quotes surrounded by single quotes which in turn surrounded escaped
double quotes...
I have found that current /lib/udev/rules.d/61-gdm.rules can be fixed by
swapping the order of the single and escaped double quotes from...
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/'
Public bug reported:
The current /lib/udev/rules.d/61-gdm.rules has a broken rule for
detecting the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1.
This issue can be seen by adding a file /etc/modprobe.d/nvidia-power-
management.conf containing the line...
options nvidia
I am wondering if the use of escaped quotes in the failing rule of
/lib/udev/rules.d/61-gdm.rules is really being honored. There don't seem
to be any other examples of deployed udev rules which actually use such
escaped quotes.
--
You received this bug notification because you are a member of
How can we even know whether the Nvidia power mananagement support is
broken or working if the Ubuntu Nvidia packaging never starts nvidia-
hibernate.service, nvidia-powerd.service, nvidia-resume.service and
nvidia-suspend.service like rpmfusion on Fedora? Of course, we would
need a
--
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/1969243
Title:
gdm 42.0-1ubuntu4 no longer shows Wayland option
To manage notifications about this bug go to:
As importantly, how can we even know whether the Nvidia power
mananagement support is broken or working if the Ubuntu Nvidia packaging
never starts nvidia-hibernate.service, nvidia-powerd.service, nvidia-
resume.service and nvidia-suspend.service like rpmfusion on Fedora. Of
course, we would need
"gdm3 (42.0-1ubuntu6) jammy; urgency=medium
* Fix Wayland no longer being available for everyone
- Fix by adding a separate revert patch instead of trying to
rebase the cherry-picked patches (LP: #1969243)
* Please note that Wayland is not currently available for
systems using
What is Ubuntu's definition of a 'stable release update' in this case
regarding Nvidia driver support for Wayland? Does this imply, as I fear,
an update only after the fix has been deployed in another full Ubuntu
release? If so, this would imply that we won't have Nvidia Wayland
support until
Looks like Fedora 36 won't have this problem with Wayland on Nvidia
because their associated rpmfusion packaging for xorg-x11-drv-nvidia
adds a nvidia-power-management.conf with the following contents into
/etc/modprobe.d...
#
# Save and restore all video memory allocations.
options nvidia
gdm3 42.0-1ubuntu6 is in proposed and Wayland is apparently going to be
unavailable for the 22.04 LTS release. Cnet is going to have to rewrite
its review.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
So this isn't a single bug but multiple points of failure.
--
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/1969243
Title:
gdm 42.0-1ubuntu4 no longer shows Wayland option
To manage
Alternatively, you can add a /etc/modprobe.d/nvidia-hack.conf file
containing the line...
options nvidia NVreg_PreserveVideoMemoryAllocations=1
and work around the apparently broken line...
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e
Does the line...
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
in /lib/udev/rules.d/61-gdm.rules parse correctly?
Adding /etc/modprobe.d/nvidia-hack.conf containing 'options
The fact that a /etc/modprobe.d/nvidia-hack.conf file with 'options
nvidia NVreg_PreserveVideoMemoryAllocations=1' doesn't bring back the
Wayland option suggests that the line...
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e
On an X570 motherboard with 5600X processor and GTX 1050 graphics card,
I was able to restore Wayland by simply commenting out the lines...
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/'
*** This bug is a duplicate of bug 1968929 ***
https://bugs.launchpad.net/bugs/1968929
I am able to get Wayland back under gdm3 42.0-1ubuntu4 by commenting out
the following two new lines that were added to
/lib/udev/rules.d/61-gdm.rules
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
gdm3 (42.0-1ubuntu4) breaks using Wayland on a X570 UD v1.1 motherboard
with 5600X processor and Nvidia GTX 1050 graphics card that worked
perfectly under gdm3 (42.0-1ubuntu2). I filed a bug against gdm3
(42.0-1ubuntu4) while it was in proposed updates but the bug report was
ignored and gdm3
gdm3 42.0-1ubuntu4 still blocks use of wayland on a X570 UD v1.1
motherboard with an AMD 5600X and Nvidia 1050 graphics card.
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969198
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Like the previous proposed 42.0-1ubuntu3 packaging of gdm3, the proposed
42.0-1ubuntu4 prevents Wayland from being used on a X570 UD v1.1
motherboard with 5600X processor and Nvidia GT 1050 graphics card. This
proposed change in the gdm3 should be considered a blocker as it
Public bug reported:
Like the previous proposed 42.0-1ubuntu3 packaging of gdm3, the proposed
42.0-1ubuntu4 prevents Wayland from being used on a X570 UD v1.1
motherboard with 5600X processor and Nvidia GTX 1050 graphics card. This
proposed change in the gdm3 should be considered a blocker as it
gdm3 42.0-1ubuntu3 blocks use of wayland on a X570 UD v1.1 motherboard
with an AMD 5600X and Nvidia 1050 graphics card.
--
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/1968809
Title:
I've seen the same issue with focal and System76 Stable PPA's
460.32.03-1pop0~1611601564~20.04~11a4029~dev nvidia packaging. All text
was corrupted after waking from suspend but it has only occurred once so
far.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
When updating Ubuntu 20.04 to the current proposed updates with the
accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome
session crashes out reproducibly into the the gdm3 greeter. At that
point, when you try to log back in, only the background color is
This bug is definitely triggered by the built kernel image loading the
nvidia drivers. The autologin failures and associated hangs on restarts
can be suppressed as follows...
1) Edit /etc/config/grub to remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT
2) Regenerate /boot/grub/grub.cfg with 'sudo
Couldn't the nvidia packages all be modified to prune 'splash' from
/boot/grub/grub.cfg prior to rebuilding its kernel modules and thus
regenerating the initrd.img files?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session
Confirmed that setting 'WaylandEnable=false' in /etc/gdm3/custom.conf
under 20.04 has no impact on the autologin bug with nvidia-340.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
20.04 RC shows the same problem with the nvidia-340 drivers on a MacPro
3,1 with Mac ROM'd GTX680. The autologin is ignored and the greeter is
shown instead. While the login works fine at the point, restarting then
causes the system to hang rather than completing the restart.
--
You received
Public bug reported:
The nautilus handling of removable media capable of automated insertion
is flawed. On a MacPro 3,1, running bionic for instance, the first use
of the eject key on the keyboard ejects the SuperDrive DVD tray but the
second use of the eject key doesn't cause the tray to
38 matches
Mail list logo
