[Bug 1969566] Re: Default to Xorg on NVIDIA-only systems
** 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 anyone finds additional reasons then please add them here. But good news: This is only for NVIDIA desktops. Hybrid laptops where Intel/AMD is the primary GPU are unaffected and should default to Wayland (after bug 1968929 is resolved). -- 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/1969566 Title: Default to Xorg on NVIDIA-only systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969566] Re: Default to Xorg on NVIDIA-only systems
** 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 @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 them here. - But good news: This is only for Nvidia desktops. Hybrid laptops where + But good news: This is only for NVIDIA desktops. Hybrid laptops where Intel/AMD is the primary GPU are unaffected and should default to Wayland (after bug 1968929 is resolved). -- 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/1969566 Title: Default to Xorg on NVIDIA-only systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
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 + Missing Wayland login option 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: Missing Wayland login option on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969566] [NEW] Default to Xorg on NVIDIA-only 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 them here. But good news: This is only for NVIDIA desktops. Hybrid laptops where Intel/AMD is the primary GPU are unaffected and should default to Wayland (after bug 1968929 is resolved). ** Affects: gdm3 (Ubuntu) Importance: High Status: In Progress ** Tags: 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/1969566 Title: Default to Xorg on NVIDIA-only systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969561] [NEW] Settings > About reports GPUs in the wrong order
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 information. This is misleading because the system is really using the Intel GPU for everything until such time as an app is opened explicitly on the "discrete" GPU. Intel should be the most prominent GPU on the Graphics line. ** Affects: gnome-control-center (Ubuntu) Importance: Low Status: New ** Tags: jammy -- 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/1969561 Title: Settings > About reports GPUs in the wrong order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969561/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969558] Re: Incorrect Window Resizing for Extension Settings
** 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 Title: Incorrect Window Resizing for Extension Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** 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 everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. - [Workaround] + [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 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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 manage notifications about
[Bug 1969396] Re: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout
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 xkb-options ['lv3:ralt_alt'] Right Alt according to xev: Alt_R Alternate Characters Key to None + Compose key to Right Ctrl $ gsettings get org.gnome.desktop.input-sources xkb-options ['lv3:ralt_alt', 'compose:rctrl'] Right Alt according to xev: Alt_R Right Ctrl according to xev: Multi_key Alternate Charters Key to None + Compose key to Right Alt - $ gsettings get org.gnome.desktop.input-sources xkb-options ['lv3:ralt_alt', 'compose:ralt'] Right Alt according to xev: Multi_key I see only expected options and expected results. So please elaborate on how you think that g-c-c behaves incorrectly, preferably with a reproducible use case. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1969396 Title: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969558] [NEW] Incorrect Window Resizing for Extension Settings
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 attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell-extensions (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Also affects: gnome-shell-extensions (Ubuntu) Importance: Undecided Status: New -- 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 Title: Incorrect Window Resizing for Extension Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
** 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 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 about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969447] Re: 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
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. -- 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/1969447 Title: 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969447/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969516] Re: gdm3 crash when switching users
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. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Incomplete -- 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/1969516 Title: gdm3 crash when switching users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Autopkgtest regression report (gvfs/1.44.1-1ubuntu1.1)
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 afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#gvfs [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Re: Slow file dialogs, open and save
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 to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885953] Re: color-cc-panel calls gcm-calibrate which was removed from package
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. https://bugs.launchpad.net/bugs/1885953 Title: color-cc-panel calls gcm-calibrate which was removed from package To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1885953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969396] Re: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout
> 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 behavior of the Right Alt key is still AltGr and not Compose. So no, gnome-control-center was not setting the expected XKB options either. ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1969396 Title: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Re: Slow file dialogs, open and save
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gvfs (Ubuntu Focal) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969530] Re: gjs-console error on gnome-extension prefs (Ubuntu 22.04)
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 you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1969530 Title: gjs-console error on gnome-extension prefs (Ubuntu 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1969530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969447] Re: 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
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...
https://git.alternativebit.fr/NinjaTrappeur/Systemd/commit/7e760b79ad143b26a5c937afa7666a7c40508f85
udev-rules: all values can contain escaped double quotes now (#6890)
This is primarly useful to support escaped double quotes in PROGRAM or
IMPORT{program} directives.
The only possibilty before this patch was to use an external shell script but
this seems too cumbersome for trivial logics such as
PROGRAM=="/bin/sh -c 'FOO=\"%s{model}\"; echo ${FOO:0:4}'"
or any similar shell constructs that needs to deals with patterns including
whitespaces.
As it's the case for single quote and for directives running a program, words
within escaped double quotes will be considered as a single argument.
Fixes: #6835
--
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/1969447
Title:
42.0-1ubuntu6 doesn't recongize the presence of
NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969447/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969447] Re: 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
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_/' /proc/driver/nvidia/params\""
which fails to parse correctly to...
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'"
which parses properly and allows the test for
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1",
GOTO="gdm_disable_wayland"
to succeed when /etc/modprobe.d/nvidia-power-management.conf contains...
options nvidia NVreg_PreserveVideoMemoryAllocations=1
--
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/1969447
Title:
42.0-1ubuntu6 doesn't recongize the presence of
NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969447/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969530] [NEW] gjs-console error on gnome-extension prefs (Ubuntu 22.04)
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: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 00:25:33 2022 InstallationDate: Installed on 2022-04-18 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220418) SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1969530 Title: gjs-console error on gnome-extension prefs (Ubuntu 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1969530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
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 for them on upgrade and probably not what users are going to expect? we probably still want the blue bar since that's the only way to avoid the possibility of 'unknowingly running a VNC remote desktop server.'. Upgrades aren't the only case to consider, we will have users copying a grdctl cmd from the internet and forgetting about it or not understand what they are doing. -- 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/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
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 about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1969428 Title: External display will be `Single Display` when HDMI plugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969516] Re: gdm3 crash when switching users
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. https://bugs.launchpad.net/bugs/1969516 Title: gdm3 crash when switching users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945061] Re: gdm3 crashed with SIGSEGV in ensure_display_for_seat()
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 ensure_display_for_seat() To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1945061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969396] Re: gnome-control-center compose key setting does not set compose key
>> 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'] > > This works. It doesn't work for me with the "English (Dvorak, alt. intl.)" layout. Unlike when using for instance the Swedish or "English (US, intl., with dead keys)" layout, 'compose:ralt' does not override the layout's default definition of "Right Alt" as the 3rd level key. Can it be some kind of race condition? So it seems to be the combination of Right Alt as compose key and the English (Dvorak, alt. intl.) layout which does not work. I changed the bug title accordingly. And AFAICT gnome-control-center sets the expected XKB options, so it's not a g-c-c bug. Maybe an xkeyboard-config bug. @Steve: Are we agreed on this problem description? ** Summary changed: - gnome-control-center compose key setting does not set compose key + Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout ** Package changed: gnome-control-center (Ubuntu) => xkeyboard-config (Ubuntu) ** Changed in: xkeyboard-config (Ubuntu) Importance: High => Medium ** Changed in: xkeyboard-config (Ubuntu) Status: Incomplete => Confirmed ** Tags added: impish -- 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/1969396 Title: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1969396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969516] [NEW] gdm3 crash when switching users
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 Jupiter /usr/libexec/gdm-x-session[2478]: (II) NVIDIA(0):
Setting mode
"HDMI-1:2560x1440_120+2560+0{ForceCompositionPipeline=On,ForceFullCompositionPipeline=On},DP-0:2560x1440_120+0+0{ForceCompositionPipeline=On,ForceFullCompositionPipeline=On}"
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event2 - Power
Button: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event2 - Power
Button: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind:
got resume for 13:64
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event0 - Sleep
Button: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event0 - Sleep
Button: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind:
got resume for 13:71
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event7 - Eee PC
WMI hotkeys: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event7 - Eee PC
WMI hotkeys: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind:
got resume for 13:70
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event6 - Cooler
Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) Keyboard: is tagged
by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event6 - Cooler
Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) Keyboard: device is
a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind:
got resume for 13:65
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event1 - Power
Button: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event1 - Power
Button: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind:
got resume for 13:77
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event13 - Razer
Razer Viper Mini: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event13 - Razer
Razer Viper Mini: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind:
got resume for 13:69
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event5 - Cooler
Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) System Control: is
tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event5 - Cooler
Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) System Control:
device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind:
got resume for 13:74
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event10 - Razer
Razer Viper Mini: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event10 - Razer
Razer Viper Mini: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind:
got resume for 13:68
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event4 - Cooler
Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) Consumer Control:
is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event4 - Cooler
Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) Consumer Control:
device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind:
got resume for 13:72
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event8 - Razer
Razer Viper Mini: is tagged by udev as: Mouse
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event8 - Razer
Razer Viper Mini: device is a pointer
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind:
got resume for 13:67
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event3 - Cooler
Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB): is tagged by udev
as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event3 - Cooler
Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB): device is a
keyboard
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule:
"libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind:
not releasing fd for 13:74, still in use
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule:
"libinput"
avr 19 20:12:36 Jupiter
[Bug 1969512] Re: totem unable to play bbb mp4: "The specified movie could not be found"
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, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: totem unable to play bbb mp4: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] [NEW] totem unable to play bbb mp4: "The specified movie could not be found"
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 could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: totem unable to play bbb mp4: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1159492] Re: science PDB file is not processed correctly after extraction
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) Status: New => Fix Released ** Changed in: jmol (Ubuntu) Status: New => Fix Released ** Changed in: rasmol (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1159492 Title: science PDB file is not processed correctly after extraction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1159492/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1159492] Re: science PDB file is not processed correctly after extraction
** 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 this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1159492 Title: science PDB file is not processed correctly after extraction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1159492/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969303] Re: "No package to remove" error when attempting to uninstall
** 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, there is an error message : "no package to remove" No problem to uninstall this same software with synaptic for example -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969439] Re: Plugins not available
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 Ubuntu. https://bugs.launchpad.net/bugs/1969439 Title: Plugins not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1969439/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1969396] Re: gnome-control-center compose key setting does not set compose key
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, 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 basic us layout — sets > 'lv3:ralt_switch' by default in the background. > More questions: > 1. Which keyboard layout are you using? English (Dvorak, alt. intl.) > 2. What happens if you drop the 'lv3:none' option, so you only have: > ['altwin:menu', 'compose:ralt'] This works. > ? While you need to set 'altwin:menu' elsewhere (Tweaks?), setting > 'compose:ralt' can be accomplished from Settings: > * Disable "Alternate Characters Key" by switching to "Use layout > default" > * Select "Right Alt" for "Compose Key" That was not the behavior here. *Now*, toggling Alternate Characters Key is not having any effect; but previously, choosing 'Use layout default' was giving me lv3:ralt_alt, lv3:switch. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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/1969396 Title: gnome-control-center compose key setting does not set compose key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969439] Re: Plugins not available
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 directory build log https://launchpadlibrarian.net/595087445/buildlog_ubuntu-jammy-amd64.shotwell_0.30.14-1ubuntu5_BUILDING.txt.gz shows --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu but it seems it was the same on impish where it works and the corresponding source didn't seem to change between the version... ** Changed in: shotwell (Ubuntu) Importance: Undecided => Low ** Changed in: shotwell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1969439 Title: Plugins not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1969439/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
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 https://gitlab.com/apparmor/apparmor/-/merge_requests/877 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
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 are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
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, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: No Wayland support on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
** 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 Case + - + Create a new user (since existing users can choose their own session). + Restart your system after applying the update. + Select your name on the login screen. + A gear button should appear in the lower right of the screen. + Click the gear button. Ubuntu should be selected unless you are using a system with only an Nvidia graphics card where Ubuntu on Xorg should be selected. + + Remaining concerns + - + Upgrades may still use Wayland? + + There are some suspend & resume issues with Wayland for Nvidia graphics + drivers in Ubuntu. + + Original Bug Report + --- + I'm using Ubuntu 22.04 on a Dell G15 5511 laptop that have an NVIDIA 3060 GPU. I saw in the last update in the gdm3 package that Wayland will be disabled in machines with hybrid graphics. The question is: In this laptop I can enable optimus to use Intel and sometimes NVIDIA or keep only on NVIDIA (I use this option). So even it's detected two GPUs the Intel one is unused. I think the problem could extend for people with a desktop with an integrated intel GPU and a discrete NVIDIA GPU, since both will be present in the system. So maybe will be necessary to check with more accuracy to check if there are two GPUs, but only one is being used or have a documented option to force the enablement of 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/1968929 Title: No Wayland support on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
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 corruption under Wayland on Pi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969263] Re: crashed file manager
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 us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1969263 Title: crashed file manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1969263/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
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 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 about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
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 "echo freeze |sudo tee /sys/power/state" my laptop woke up again after a few seconds. -- 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 about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
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 "echo freeze |sudo tee /sys/power/state" my laptop woke up again after a few seconds. -- 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 about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
** 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 about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
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 the change occurred so this is speculation on my part. -- 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 corruption under Wayland on Pi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
** 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. https://bugs.launchpad.net/bugs/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969447] [NEW] 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
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 NVreg_PreserveVideoMemoryAllocations=1
and then rebooting. Manually executing the test used in
/lib/udev/rules.d/61-gdm.rules as...
/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"
produces the desired...
NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
for the actual test in /lib/udev/rules.d/61-gdm.rules of...
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\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"
However, this test still is treated as failing as seen by the absence of
Wayland on Nvidia at that point. Currently, the only workaround is to
disable this particular test.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu6
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 19 05:20:49 2022
InstallationDate: Installed on 2022-03-31 (18 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2022-04-01T05:39:42.178574
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy third-party-packages
** Description changed:
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 NVreg_PreserveVideoMemoryAllocations=1
- and then rebooting. Since manually executing the test used in
+ and then rebooting. Manually executing the test used in
/lib/udev/rules.d/61-gdm.rules as...
/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"
produces the desired...
NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
for the actual test in /lib/udev/rules.d/61-gdm.rules of...
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\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"
However, this test still is treated as failing as seen by the absence of
Wayland on Nvidia at that point. Currently, the only workaround is to
disable this particular test.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu6
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 19 05:20:49 2022
InstallationDate: Installed on 2022-03-31 (18 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
ProcEnviron:
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2022-04-01T05:39:42.178574
--
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/1969447
Title:
42.0-1ubuntu6 doesn't recongize the presence of
NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969447/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969447] Re: 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
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 Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1969447 Title: 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969447/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
** 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 about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969439] [NEW] Plugins not available
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 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 19 11:04:59 2022 InstallationDate: Installed on 2022-04-16 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "strace -f -e trace=file shotwell output" https://bugs.launchpad.net/bugs/1969439/+attachment/5581403/+files/strace_file_shotwell.txt.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1969439 Title: Plugins not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1969439/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** 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: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968999] Re: [jammy] Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.
** 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 Title: [jammy] Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968999/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
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, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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 about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969266] Re: application windows frozen after screen blanking
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', 'user-theme@gnome-shell- extensions.gcampax.github.com', 'apps-menu@gnome-shell- extensions.gcampax.github.com', 'auto-move-windows@gnome-shell- extensions.gcampax.github.com', 'vit...@corecoding.com', 'cpufreq@konkor', 'gpa...@gnome-shell-extensions.gnome.org', 'gsconn...@andyholmes.github.io', 'workspace-indicator@gnome-shell- extensions.gcampax.github.com' Does the problem still occur? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5330 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5330 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5330 Importance: Unknown Status: Unknown -- 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/1969266 Title: application windows frozen after screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969266] Re: application windows frozen after screen blanking
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 resource:///org/gnome/shell/ui/windowManager.js:1542 (339f27529c90 @ 23) [36178.231698] Dapple gnome-shell[3998]: #1 7ffd1afab520 b self-hosted:1181 (3ed1fbfb0a10 @ 454) [36178.231698] Dapple gnome-shell[3998]: #2 5562ed9681c8 i resource:///org/gnome/shell/ui/main.js:260 (3ed1fbfef150 @ 12) [36178.231698] Dapple gnome-shell[3998]: GNOME Shell crashed with signal 11 [36178.231698] Dapple gnome-shell[3998]: == Stack trace for context 0x5562d03ed170 == [36178.231698] Dapple gnome-shell[3998]: #0 5562ed9681c8 i resource:///org/gnome/shell/ui/main.js:260 (3ed1fbfef150 @ 12) [36178.232108] Dapple gnome-shell[3998]: JS ERROR: TypeError: window is null _destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16 -- 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/1969266 Title: application windows frozen after screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969266] Re: application windows frozen after screen blanking
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. https://bugs.launchpad.net/bugs/1969266 Title: application windows frozen after screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
** 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 affects: evolution (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1969251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on NVIDIA systems
** 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 on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969140] Re: Window minimize animation flickers and appears in the wrong place
** 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. https://bugs.launchpad.net/bugs/1969140 Title: Window minimize animation flickers and appears in the wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** 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 everywhere that realistically compositors never will support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. - + [Test Plan] + + [Where problems could occur] + + [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** 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 everywhere that realistically compositors never will support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
** 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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
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 stella ** Tags added: originate-from-1966906 -- 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 about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] [NEW] External display will be `Single Display` when HDMI plugged
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 to internal HDMI port on DUT [Where problems could occur] * This change makes DUT more stable when connecting external monitor. * This fix is also include in impish and jammy ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969396] Re: gnome-control-center compose key setting does not set compose key
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 basic us layout — sets 'lv3:ralt_switch' by default in the background. More questions: 1. Which keyboard layout are you using? 2. What happens if you drop the 'lv3:none' option, so you only have: ['altwin:menu', 'compose:ralt'] ? While you need to set 'altwin:menu' elsewhere (Tweaks?), setting 'compose:ralt' can be accomplished from Settings: * Disable "Alternate Characters Key" by switching to "Use layout default" * Select "Right Alt" for "Compose Key" ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1969396 Title: gnome-control-center compose key setting does not set compose key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on my NVIDA laptop
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 reinstated ASAP and the remaining issue then tracked in bug 1876632. We do not need to wait for Nvidia to fix a driver bug we've known about for years already. -- 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 my NVIDA laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** 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 realistically compositors never will support it fully. Instead we're waiting for an Nvidia driver fix. + + *NOTE* that this is actually not a common problem because the system + must be using Nvidia as the primary GPU to be affected. So generally + only desktop users will encounter the bug, not laptops. And even then, + only desktops that use suspend/resume and VT switching may trigger it, + if ever. Even in development the bug cannot be reproduced reliably. I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on my NVIDA laptop
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 intended for those drivers to be fixed in a future stable release update for Ubuntu 22.04 LTS. See bug 1968929" I am confused whether this means we are not getting "Wayland by default" back on laptops with hybrid graphics using 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/1968929 Title: No Wayland support on my NVIDA laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** 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: nvidia-graphics-drivers-470 (Ubuntu) Status: Confirmed => Triaged ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Confirmed => Triaged ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Confirmed => Triaged ** 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 support the feature that realistically + Although it's so awkward to implement everywhere that realistically compositors never will support it fully. Instead we're waiting for an Nvidia driver fix. I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** 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 + + Although it's so awkward to support the feature that realistically + compositors never will support it fully. Instead we're waiting for an + Nvidia driver fix. + + + I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 - GCC version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 + GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] + NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** 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: + 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 support the feature that realistically compositors never will support it fully. Instead we're waiting for an Nvidia driver fix. I recently installed
[Bug 1968929] Re: No Wayland support on my NVIDA laptop
** 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, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: No Wayland support on my NVIDA laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969142] Re: Display glitch after resume on Wayland if boot vga is nvidia
*** 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 look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1876632 [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend -- 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/1969142 Title: Display glitch after resume on Wayland if boot vga is nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
** 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 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1969357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
