[Bug 2003291] [NEW] Ubuntu22.04 does not support high resolution 2560x1440(HDMI) on the 12th generation CPU(integrated graphics)
Public bug reported: Dell Intel 12th generation CPU (i5-12400), integrated graphics (UHD Graphics 730) Monitor is AOC 27 inch, the standard resolution is 2560x1440 After installing Ubuntu 22.04, the maximum resolution of the display(using HDMI cable) can only maximum support 1980 x 1080 I have upgraded the kernel to 6.14, but it still doesn't work. When install Ubuntu22.04 on a Dell computer with an Intel 11th generation CPU (i5-11400, integrated graphics) or below, the resolution 2560x1440 is supported and works well through HDMI. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1 Uname: Linux 6.1.4-060104-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 19 11:19:24 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-01-10 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/2003291 Title: Ubuntu22.04 does not support high resolution 2560x1440(HDMI) on the 12th generation CPU(integrated graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2003291/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994011] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_data_gbm()
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-mutter-44 fixed-upstream ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- 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/1994011 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_data_gbm() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003283] [NEW] Ubuntu22.04 Remote Desktop doesn't support to display the screen of the second monitor
Public bug reported: Ubuntu 22.04 Remote Desktop can only show the screen of the main monitor but not for the second monitor. It did work in Ubuntu 20.04 without any problem on the same computer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1 Uname: Linux 6.1.4-060104-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 19 11:03:30 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-01-10 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/2003283 Title: Ubuntu22.04 Remote Desktop doesn't support to display the screen of the second monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2003283/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003237] Re: Monitor does not turn off after idle timeout is reached
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) -- 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/2003237 Title: Monitor does not turn off after idle timeout is reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003237/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions
Scott, Please open a new bug by running: ubuntu-bug gnome-shell so that we can investigate your system separately. -- 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/1982560 Title: Mouse lag/stutter (missed frames) in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003237] [NEW] Monitor does not turn off after idle timeout is reached
You have been subscribed to a public bug: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power off as it's supposed to - the screen is simply black. Please see the attached video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2018-03-17 (1768 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago) dmi.bios.date: 05/29/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4211 dmi.board.asset.tag: Default string dmi.board.name: H110M-D dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug jammy ubuntu wayland-session -- Monitor does not turn off after idle timeout is reached https://bugs.launchpad.net/bugs/2003237 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode
I was expecting upstream to say "won't fix". Aside from the protocol saying it's the expected behaviour, we also wouldn't want to impact performance of fullscreen games just because they accidentally used RGBA instead of RGBX or RGB. So disallowing anything to show through in full screen makes sense to me, on balance. ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/wayland/wayland-protocols/-/issues #116 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/116 ** Also affects: wayland via https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/116 Importance: Unknown Status: Unknown ** Changed in: wayland (Ubuntu) Status: New => Won't Fix ** Changed in: mutter (Ubuntu) Status: Triaged => Won't Fix ** Changed in: mutter (Ubuntu) Importance: High => Undecided -- 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/2003104 Title: gnome-terminal transparency ignored in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2003104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
That's probably not as good as sticking to nouveau because it will fall back to software rendering instead. But the third and best option is to install an Nvidia driver using the 'Additional Drivers' app. -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2003031/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752680] Re: Night light does not work after resume from suspend or unlock.
** Tags added: gamma nightlight -- 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/1752680 Title: Night light does not work after resume from suspend or unlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1752680/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772212] Re: [nvidia] Night light doesn't cover all monitors fully
** Tags added: gamma nightlight -- 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/1772212 Title: [nvidia] Night light doesn't cover all monitors fully To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1772212/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1995783] Re: Nightlight fails after suspend
** Tags added: nightlight -- 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/1995783 Title: Nightlight fails after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1995783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1972720] Re: Night light does not work on laptop screen when disconnecting from external screen
** Tags added: nightlight -- 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/1972720 Title: Night light does not work on laptop screen when disconnecting from external screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1972720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999122] Re: Gnome 42.5 Nigth Light does not work properly with dual monitors
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- 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/1999122 Title: Gnome 42.5 Nigth Light does not work properly with dual monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: gnome-terminal transparency ignored in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2003104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode
I verified that this regression also shows in Fedora 37. I verified there because Fedora and Ubuntu ship a patch to enable transparency in gnome-terminal; gnome-terminal upstream does not have that feature. I also verified that this regression was introduced in mutter 43.1. (transparency works in 43.0 but not in 43.1). With that information, I found an upstream bug report. The initial response was that the new behavior conforms to the specification and it was suggested to maximize gnome-terminal instead of using fullscreen mode if you want this feature. ** Changed in: mutter (Ubuntu) Assignee: Jeremy Bicha (jbicha) => (unassigned) ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2520 https://gitlab.gnome.org/GNOME/mutter/-/issues/2520 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2520 Importance: Unknown Status: Unknown -- 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/2003104 Title: gnome-terminal transparency ignored in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2003104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions
I tried the lines: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 MUTTER_DEBUG_FORCE_KMS_MODE=simple in /etc/environment as suggested. It does not help. Or it did not help much. I think the keyboard lag might be less prevalent, but the mouse is still problematic. My symptoms remain the same: 1. everything is fine right after the window manager starts 2. After between 1 and 4 days (depending on usage), the mouse starts to skip and lag and stutter. During this condition, moving the mouse in small circles is enough to send 'gnome-shell' CPU use to 100% and cause updates to the display to stall or pause for long intervals, sometimes many seconds, until I take a break with the mouse movement -- for example Gnome System Monitor won't update its contents or rarely will, until I pause the mouse movement. I am using the integrated GPU on my laptop in this case (no discrete GPU, Ryzen 4750U processor). 'radontop' indicates about half of the 2GB memory reserved for the GPU is used, and GPU usage drops to 0% during the stalls. 3. If I log out of my user and log back in, everything is back to normal, for a few days. Switching to xorg fixes it (but causes other problems). I recently updated to 22.10 to see if that helped, it does not. -- 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/1982560 Title: Mouse lag/stutter (missed frames) in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions
I tried the lines: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 MUTTER_DEBUG_FORCE_KMS_MODE=simple in /etc/environment as suggested. It does not help. Or it did not help much. I think the keyboard lag might be less prevalent, but the mouse is still problematic. My symptoms remain the same: 1. everything is fine right after the window manager starts 2. After between 1 and 4 days (depending on usage), the mouse starts to skip and lag and stutter. During this condition, moving the mouse in small circles is enough to send 'gnome-shell' CPU use to 100% and cause updates to the display to stall or pause for long intervals, sometimes many seconds, until I take a break with the mouse movement -- for example Gnome System Monitor won't update its contents or rarely will, until I pause the mouse movement. I am using the integrated GPU on my laptop in this case (no discrete GPU, Ryzen 4750U processor). 'radontop' indicates about half of the 2GB memory reserved for the GPU is used, and GPU usage drops to 0% during the stalls. 3. If I log out of my user and log back in, everything is back to normal, for a few days. Switching to xorg fixes it (but causes other problems). I recently updated to 22.10 to see if that helped, it does not. -- 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/1982560 Title: Mouse lag/stutter (missed frames) in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode
Thank you for reporting this bug and helpinig to make Ubuntu better. I'm going to collect more data to report this issue upstream since this issue is blocking us from being able to successfully SRU 43.2 to Ubuntu 22.10. ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Tags added: regression-release ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- 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/2003104 Title: gnome-terminal transparency ignored in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
I have blacklisted this now using: sudo vim /etc/modprobe.d/blacklist-nouveau.conf adding: blacklist nouveau options nouveau modeset=0 -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2003031/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003108] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2003108/+attachment/5642301/+files/ProcCpuinfoMinimal.txt -- 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/2003108 Title: Nautilus still says "do not unplug the device" even if the writing process is finished To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2003108/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003108] Re: Nautilus still says "do not unplug the device" even if the writing process is finished
apport information ** Tags added: apport-collected jammy third-party-packages wayland- session ** Description changed: After I click on the "unmount" icon next to the USB device in the file tree sidebar on Nautilus, the notification appears with the text "do not unplug/remove the device". The problem is that the notification doesn't go away for several time, even if the writing process is already finished, also with that notification still visible in the right top corner I can remount the USN by clicking its name in Nautilus, use it, and unmount it. If I copy something in the USB, the "copying files" popup process should finish only if the writing process is really completed (as it was in the previous Ubuntu versions...). I'm using Ubuntu 22.04.1 LTS. apt-cache policy nautilus: nautilus: Installato: 1:42.2-0ubuntu1 Candidato: 1:42.2-0ubuntu1 Tabella versione: *** 1:42.2-0ubuntu1 100 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + GsettingsChanges: + b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" + b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" + b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' + b'org.gnome.nautilus.window-state' b'maximized' b'true' + InstallationDate: Installed on 2022-10-06 (103 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + Package: nautilus 1:42.2-0ubuntu1 [origin: unknown] + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=it_IT.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 + Tags: jammy third-party-packages wayland-session + Uname: Linux 5.15.0-56-generic x86_64 + UnreportableReason: Questo non sembra essere un pacchetto ufficiale Ubuntu. Riprova dopo aver aggiornato gli indici dei pacchetti disponibili, se non funziona rimuovere i relativi pacchetti di terze parti e riprovare. + UpgradeStatus: Upgraded to jammy on 2022-10-06 (103 days ago) + UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + usr_lib_nautilus: + evince42.3-0ubuntu2 + file-roller 3.42.0-1 + nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 + nautilus-share0.7.3-2ubuntu6 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2003108/+attachment/5642300/+files/Dependencies.txt -- 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/2003108 Title: Nautilus still says "do not unplug the device" even if the writing process is finished To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2003108/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000423] Re: "Alternate Characters Key" UI not reflecting current choice
I accomplished the steps in the test plan using gnome-control-
center{,-data} 1:41.7-0ubuntu0.22.04.6 from jammy-proposed. Issue fixed
as expected.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-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/2000423
Title:
"Alternate Characters Key" UI not reflecting current choice
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2000423/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode
Yes, it is. I tested it in a VM, and can reproduce it. -- 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/2003104 Title: gnome-terminal transparency ignored in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Merge proposal linked: https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435960 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Changed in: metacity (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode
Sergio, you mean that it looks like this bug was triggered when your system updated from mutter 43.0-1ubuntu5 to https://launchpad.net/ubuntu/+source/mutter/43.2-4ubuntu1 right? ** Summary changed: - Transparency ignored in full screen mode + gnome-terminal transparency ignored in full screen mode ** Package changed: gnome-terminal (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: gnome-terminal transparency ignored in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Merge proposal unlinked: https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435956 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Merge proposal linked: https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435957 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Changed in: metacity (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Merge proposal linked: https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435956 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Description changed: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash + + * Fix: install fix from ppa: + * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 + * sudo apt update + * sudo reboot # or alternatively, restart display manager + * run python3 Untitled.py + * Undock one of the application's child windows + * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003184] [NEW] gtk-key-theme Emacs has no effect in 22.10
Public bug reported: Setting the key binding theme for GTK to Emacs through the usual method of running ``` gsettings set org.gnome.desktop.interface gtk-key-theme Emacs ``` has no effect. Opening Nautilus, typing a word, and then pressing ctrl-a will select the whole word instead of moving the caret to the beginning of the line. The same behaviour can be observed in other GTK inputs such as the search field of Gnome Shell. ``` └$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic └$ gnome-shell --version GNOME Shell 43.1 ``` ** Affects: gtk4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2003184 Title: gtk-key-theme Emacs has no effect in 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2003184/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003104] Re: Transparency ignored in full screen mode
It's not random, at least in my system. Also, the tricks in that bug report don't work: I tried changing the transparency value, disabling and enabling again, but no dice. If I had to bet, I would say that the problem is in the fullscreen redirection to avoid composition overload with games... but I don't know if Wayland has that... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: Transparency ignored in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2003104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003104] Re: Transparency ignored in full screen mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: Transparency ignored in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2003104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003104] Re: Transparency ignored in full screen mode
Confirmed that this happens when libmutter/mutter-common are updated to version 11. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: Transparency ignored in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2003104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
** Description changed: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 - * The fix is already included in 3.46.0 version: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 - * Focal(3.36.1) and Jammy (3.44.0) needs the fix to be backported + * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 + * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored + * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 + * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window - * Result: Metacity will crash + * Result: Metacity will crash * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
Reproducer script: ** Attachment added: "Untitled.py" https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+attachment/5642194/+files/Untitled.py -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] [NEW] SRU: metacity crashes while minimizing a windows that has undocked child
Public bug reported: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Affects: metacity (Ubuntu Focal) Importance: Undecided Assignee: Mustafa Kemal Gilor (mustafakemalgilor) Status: New ** Affects: metacity (Ubuntu Jammy) Importance: Undecided Assignee: Mustafa Kemal Gilor (mustafakemalgilor) Status: New ** Also affects: metacity (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: metacity (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: metacity (Ubuntu Focal) Assignee: (unassigned) => Mustafa Kemal Gilor (mustafakemalgilor) ** Changed in: metacity (Ubuntu Jammy) Assignee: (unassigned) => Mustafa Kemal Gilor (mustafakemalgilor) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1991777] Re: gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older (than supported) kernels
** Summary changed: - gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older kernels + gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older (than supported) kernels ** 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/1991777 Title: gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older (than supported) kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1991777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Answer from email to comment #57: It appears your CPU/GPU (i7-1280P) is too new for that old kernel (5.14.0-1055-oem). And so you are hitting this bug: https://launchpad.net/bugs/1991777 But the solution is simple: Just install 22.10 and don't downgrade the kernel. It should be kernel version 5.19 when Ubuntu 22.10 is installed properly. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1991777] Re: gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older kernels
If atomic KMS is disabled then the same bug may present as: Failed to post KMS update: drmModeCrtcSetGamma on CRTC 80 failed: Function not implemented -- 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/1991777 Title: gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1991777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Please collect a log from the previous boot where it froze: journalctl -b-1 > prevboot.txt and create a new bug with that file attached. Also check for /var/crash files and create new bugs for each using 'ubuntu-bug'. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003168] [NEW] SIdebar, files gets unresponsive after unlocking locked season.
Public bug reported: SIdebar, files gets unresponsive after unlocking locked season. Clicking on search bar also freezes the whole season. Issue requires Restarting GTK3 or restarting the season. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78 Uname: Linux 5.15.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 13:35:36 2023 InstallationDate: Installed on 2021-06-20 (576 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003168 Title: SIdebar, files gets unresponsive after unlocking locked season. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
I have the same or similar bug. I tried the workaround to Add to /etc/environmen in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple And my computer froze on startup on the Ubuntu screen. When I deleted the line, my computer again booted up fine. I have a Thinkpad X1 with Ubuntu 20.04 preinstalled which I have updated to 22.10. It has Mesa Intel® Graphics (ADL GT2) graphics. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
