** Changed in: gdm3 (Ubuntu)
Importance: Medium => High
** Changed in: gdm3 (Ubuntu)
Milestone: None => ubuntu-22.04
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Jeremy Bicha (jbicha)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Description changed:
+ The Nvidia driver corrupts and/or forgets its textures when resuming
+ from suspend. Unfortunately for the moment it's a "feature" of the
+ Nvidia driver documented here:
+
+
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
+
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Another quick update: in recent days we've gone from "blank white space"
back to "incorrect stride corruption" in all documented cases (embedded
browsers, help windows, MiniBrowser, etc).
I note in the dpkg logs, libglx-mesa0 got updated a few days ago, but
unfortunately I'm unsure exactly when
I read the comment #19 and I was able to suspend correctly using s0ix
method. The problem is: The method requires using "echo mem |sudo tee
/sys/power/state" to enter on suspend mode, but I think the default
method, when using menu option and "systemctl suspend", is "freeze", not
"mem". Using
the recent update suggests the white rendering was indeed bug #1966418
which is resolved now
--
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/1924251
Title:
Embedded browser display
** Information type changed from Public Security to Public
--
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/1968929
Title:
No Wayland support on NVIDIA systems
To manage notifications
I read the comment #19 and I was able to suspend correctly using s0ix
method. The problem is: The method requires using "echo mem |sudo tee
/sys/power/state" to enter on suspend mode, but I think the default
method, when using menu option and "systemctl suspend", is "freeze", not
"mem". Using
Here you can see the GNOME extension Vitals showing corrupted values
after a suspend
** Attachment added: "Corrupted screen"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+attachment/5581433/+files/Screenshot%20from%202022-04-19%2008-21-28.png
--
You received this bug
*** This bug is a duplicate of bug 1876632 ***
https://bugs.launchpad.net/bugs/1876632
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1876632, so it is being marked as such. Please
** Package changed: gnome-session (Ubuntu) => unity (Ubuntu)
--
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/1969357
Title:
Unity7 crashes on Jammy with 22.04's gnome-session
This seems to be a misunderstanding/overreaction to bug 1876632. We can
live with that but should still try to fix it in future. The issue was
further confused by Nvidia hybrid laptop users becoming involved these
past few days thanks to bug 1969243.
Wayland support for Nvidia should be
** Description changed:
+ [Impact]
+
The Nvidia driver corrupts and/or forgets its textures when resuming
from suspend, by design. Documented here:
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
Although it's so awkward to implement
** Summary changed:
- No Wayland support on my NVIDA laptop
+ No Wayland support on NVIDIA systems
--
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/1968929
Title:
No Wayland support
The attachment "gnome-control-center_3.36.5-0ubuntu4.debdiff" seems to
be a debdiff. The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff. If
the attachment isn't a patch, please remove the "patch" flag from the
attachment,
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
** Changed in: mutter (Ubuntu)
Status: New => Triaged
--
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/1968999
Public bug reported:
Just installed 22.04 and Shotwell but I cannot enable any plugin, no one
available.
May be a lib path error?
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: shotwell 0.30.14-1ubuntu5 [modified:
usr/share/applications/shotwell.desktop]
ProcVersionSignature: Ubuntu
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-session (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
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
Is 'lv3:none' a valid XKB option?
I can't reproduce your problem on my jammy. Even if I set "Alternate
Characters Key" to "Right Alt" in Settings, the 'compose:ralt' option
overrides it and RightAlt/AltGr works as a compose key. That's true also
if I use the Swedish layout, which — unlike the
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-42.1 fixed-upstream
--
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/1967274
Title:
** Information type changed from Public to Public Security
--
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/1968929
Title:
No Wayland support on NVIDIA systems
To manage notifications
Updated gdm3 to 42.0-1ubuntu6, still no Wayland by default as it used to
be (for a short span).
> * Please note that Wayland is not currently available for
systems using the Nvidia graphics drivers because those drivers
don't properly handle suspend and resuming from suspend. It is
** Description changed:
The Nvidia driver corrupts and/or forgets its textures when resuming
from suspend, by design. Documented here:
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
Although it's so awkward to implement everywhere that
Public bug reported:
Upstream bug:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1038
[Impact]
* DUT will remain `Single Display` mode when 4k monitor is plugged.
Not every 4K monitor will cause this issue.
[Test Plan]
* Find a 4k monitor (Philips 276E)
* Plug HDMI cable
Upload debdiff for focal
** Patch added: "gnome-control-center_3.36.5-0ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969428/+attachment/5581392/+files/gnome-control-center_3.36.5-0ubuntu4.debdiff
** Tags added: oem-priority originate-from-1967088
** Tags added: jammy
--
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/1876632
Title:
[nvidia] Corrupted/missing shell textures when switching users or
resuming from suspend
To
** Summary changed:
- Graphical glitches when minimizing and maximizing apps
+ Window minimize animation flickers and appears in the wrong place
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Changed in: evolution (Ubuntu)
Status: Invalid => New
** Changed in: evolution (Ubuntu)
Status: New => Confirmed
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
** Changed in: yaru-theme (Ubuntu)
Status: New => Confirmed
** No longer
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided => High
** Changed in:
** Tags added: focal
--
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/1969428
Title:
External display will be `Single Display` when HDMI plugged
To manage
This looks like the problem, assuming the right section of the system
log is attached in comment #1:
[36178.231698] Dapple gnome-shell[3998]: == Stack trace for context
0x5562d03ed170 ==
[36178.231698] Dapple gnome-shell[3998]: #0 5562ed968248 i
Please uninstall all of these extensions and then reboot:
'activities-config@nls1729', 'places-menu@gnome-shell-
extensions.gcampax.github.com', 'babar@fthx', 'timepp@zagortenay333',
'launch-new-insta...@gnome-shell-extensions.gcampax.github.com',
'vertical-overv...@rensalthuis.github.com',
Thanks for the bug report.
Can you take a photo of the screen when the problem happens next, and
attach it here?
** Tags added: nvidia
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1968929
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I'm working on a SRU for apparmor and evince to introduce the snap_browsers
abstraction on apparmor as a workaround for this issue.
It is based on these two merge requests from upstream:
https://gitlab.com/apparmor/apparmor/-/merge_requests/806
I downloaded a similar file from
ftp://ftp.pdbj.org/pub/pdb/data/structures/all/pdb/pdb163l.ent.gz
...
and with the current version of file-roller and jmol, I could not reproduce
this bug.
So I consider it as non-reproducible, and will close it.
** Changed in: file-roller (Ubuntu)
Thanks, indeed, and stderr displays
[CRT] plugins_search_for_plugins: assertion 'G_TYPE_CHECK_INSTANCE_TYPE
(dir, g_file_get_type ())' failed
using
$ SHOTWELL_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/shotwell/plugins/ shotwell
workaround the issue, so it seems somehow it's trying to use the wrong
On Tue, Apr 19, 2022 at 06:42:15AM -, Gunnar Hjalmarsson wrote:
> Is 'lv3:none' a valid XKB option?
I have no idea. But until I set it, I was seeing conflicting lv3
options.
> I can't reproduce your problem on my jammy. Even if I set "Alternate
> Characters Key" to "Right Alt" in Settings,
sounds like probably an issue with the build fix we added for the new
valac in
http://launchpadlibrarian.net/592733380/shotwell_0.30.14-1ubuntu2_0.30.14-1ubuntu3.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in
it sounds like something that we should fix one way or another at least
for the LTS, maybe in the futur we will have evince as a snap instead
and the situation will be different. Could you suggest a patch for
review with the change you described?
--
You received this bug notification because you
** Description changed:
- On a fresh install of ubuntu 22.04, ubuntu-store won't uninstall any
+ On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any
application
- If you want to uninstall a sottware, tthere is an error message : "no
+ If you want to uninstall a software,
** Description changed:
+ Desired Functionality
+ -
+ Systems using Nvidia graphics drivers should have an option to use Wayland
but Xorg should be the default.
+
+ Hybrid systems using Nvidia graphics drivers should use Wayland by
+ default.
+
+ Impact
+ --
+
+ Test
** Changed in: file-roller (Ubuntu)
Assignee: (unassigned) => Georges Khaznadar (georgesk)
** Changed in: jmol (Ubuntu)
Assignee: (unassigned) => Georges Khaznadar (georgesk)
** Changed in: rasmol (Ubuntu)
Assignee: (unassigned) => Georges Khaznadar (georgesk)
--
You received
Public bug reported:
As part of our ISO testing for the Pi desktop, we attempt to play
https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4
with the shipped totem video player. Unfortunately, on the current Jammy
image, totem simply reports "The specified movie
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1969512
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Hello Daniel,
Issue is still present, as requested I opened a new bug #1969516
--
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/1945061
Title:
gdm3 crashed with SIGSEGV in
uploaded to focal
--
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/1969428
Title:
External display will be `Single Display` when HDMI plugged
To manage notifications
Random thoughts there
VNC was never on by default, if it's enabled it is because the user went
to the setting to turn it on so it shouldn't come to a surprise to them
that they are sharing their desktop. Since it's an user decision and
something they might rely on, it feels rude to turn if off
Public bug reported:
Hi Guys,
Exactly the same issue as bug #1945061
GDM still crash when switching user.
To reproduce the issue:
Login as user A, keep user A logged in and lock the screen. Try to
switch to user B, enter the password and you got back to the user list
(loop)
avr 19 20:12:25
>> 1. Which keyboard layout are you using?
>
> English (Dvorak, alt. intl.)
There is something with that layout. With that enabled I can reproduce
the problem. Both on jammy and impish.
>> 2. What happens if you drop the 'lv3:none' option, so you only have:
>> ['altwin:menu', 'compose:ralt']
>
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Fix Released
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
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_/'
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...
Public bug reported:
gjs-console error reported everytime opening a gnome-extension settings
prefs on Ubuntu 22.04
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion:
Crash report generated by opening and closing Dash to Panel settings.
** Attachment added: "_usr_bin_gjs-console.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1969530/+attachment/5581525/+files/_usr_bin_gjs-console.1000.crash
--
You received this bug notification because
To make it clear we have two separate requirements I've opened bug
1969566 too.
** Changed in: gdm3 (Ubuntu)
Assignee: Jeremy Bicha (jbicha) => (unassigned)
** Changed in: gdm3 (Ubuntu)
Status: Triaged => In Progress
** Summary changed:
- No Wayland support on NVIDIA systems
+
Public bug reported:
NVIDIA has requested that we default to Xorg on NVIDIA-only systems.
(I've been told by @jbicha that @kenvandine was advised so)
One possible reason cited was:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317
but if anyone finds additional reasons then please add
** Summary changed:
- Default to Xorg on Nvidia-only systems
+ Default to Xorg on NVIDIA-only systems
** Description changed:
- Nvidia has requested that we default to Xorg on Nvidia-only systems.
+ NVIDIA has requested that we default to Xorg on NVIDIA-only systems.
(I've been told by
** Description changed:
NVIDIA has requested that we default to Xorg on NVIDIA-only systems.
- (I've been told by @jbicha that @kenvandine was advised so)
+ (@kenvandine was advised so)
One possible reason cited was:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317
but if
I concluded that the description was related to the use of the
us+dvorak-alt-intl layout, and not to g-c-c setting incorrect options.
Observations from use of the us+intl layout:
Alternate Characters Key to None
$ gsettings get org.gnome.desktop.input-sources
Public bug reported:
Issue with gnome-extensions-app
While the main Extensions windows behaves normally when being resizes,
for Extension Settings, when dragging the bottom corner up, the top of
the window also goes down. If I drag the bottom corner down, the top
edge goes up... See screenshots
** Description changed:
[Impact]
The Nvidia driver corrupts and/or forgets its textures when resuming
from suspend, by design. Documented here:
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
Although it's so awkward to implement
** No longer affects: gnome-shell-extensions (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
--
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/1969558
Public bug reported:
Settings > About reports GPUs in the wrong order
In a typical hybrid setup you have:
Primary GPU: Intel
Secondary GPU: Nvidia
and Intel does all the shell rendering.
Yet when I look in Settings > About, the Graphics line reports Nvidia
first and cuts off the Intel GPU
Hello sam, or anyone else affected,
Accepted gvfs into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gvfs/1.44.1-1ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
In order to confirm this is the same issue as bug 1945061 we will need a
stack trace so...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1.
> And AFAICT gnome-control-center sets the expected XKB options,
> so it's not a g-c-c bug. Maybe an xkeyboard-config bug.
From my initial bug report:
Setting Alternate Characters Key to None, and moving the Compose Key
setting around between different options (and then back to Right Alt),
the
Still an issue in 21.10. And probably a duplicate of
https://bugs.launchpad.net/ubuntu/+source/gnome-color-
manager/+bug/862992
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
I've accepted this into -proposed on the basis that it'll make it
possible for you to verify, and it's easy to reject if it turns out you
can't verify it its easy to remove from proposed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
All autopkgtests for the newly accepted gvfs (1.44.1-1ubuntu1.1) for focal have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.44.1-1ubuntu1.1 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding
I'm not totally sure we need this bug. The problem with Wayland sessions
missing on Nvidia is tracked in bug 1968929. And the use of
NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS should be tracked in bug
1876632. So essentially this bug is just pointing out that we haven't
fixed bug 1876632 yet.
--
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Andy Chi (andch)
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I think comments #22 and #24 probably belong in bug 1876632, not here.
--
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/1968929
Title:
No Wayland support on NVIDIA systems
To manage
76 matches
Mail list logo
