[Bug 2100561] Re: Language and Region date format settings for Australia not obeyed
It seems to be working in 24.04.2 here: LC_TIME=en_AU.UTF-8 and Nautilus displays "DD MMM " for me. So I wonder what's different about your setup... -- 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/2100561 Title: Language and Region date format settings for Australia not obeyed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2100561/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100475] Re: Whole display freezes in 1 second interval for a while
Those messages are mostly bug 1857392 which we usually ignore but yours are too frequent. Please double check there are no non-standard extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and log in again. If the problem still happens after that then as an experiment try: gnome-extensions disable ubuntu-d...@ubuntu.com -- 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/2100475 Title: Whole display freezes in 1 second interval for a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2100475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823616] Re: Incorrect date format for Australia
** Changed in: gnome-shell Status: New => Fix Released -- 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/1823616 Title: Incorrect date format for Australia To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1823616/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904237] Re: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg
** Summary changed: - [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal + [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg ** Tags added: noble -- 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/1904237 Title: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904237/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2087831] Re: [SRU] Touchscreen gets disabled after resume from suspend in Xorg session
** Summary changed: - [SRU] On a laptop with NVIDIA graphics and touchscreen, touchscreen gets disabled after resume from suspend in Xorg session + [SRU] Touchscreen gets disabled after resume from suspend in Xorg session -- 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/2087831 Title: [SRU] Touchscreen gets disabled after resume from suspend in Xorg session To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2087831/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100482] Re: 2nd screen display resolution fails on resume from screen blanking
The most common cause of a mistaken default resolution is the kernel randomly not getting enough bandwidth to use the full resolution. This happens if there is an imperfection in the display cable or its connections. So I usually recommend replacing the cables between the laptop and the monitors. For HDMI, try to get an "HDMI 2.1" cable. For USB-C, try to get "Thunderbolt" cables. ** Tags added: multimonitor noble ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2100482 Title: 2nd screen display resolution fails on resume from screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2100482/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100475] Re: Whole display freezes in 1 second interval for a while
I don't use any other extensions. I disabled the Dock, now just wait until the problem reappears.. -- 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/2100475 Title: Whole display freezes in 1 second interval for a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2100475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066183] Update Released
The verification of the Stable Release Update for packagekit has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2066183 Title: AppStream metadata allow user uninstallation of PackageKit To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/2066183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066183] Re: AppStream metadata allow user uninstallation of PackageKit
Oops, hehe -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2066183 Title: AppStream metadata allow user uninstallation of PackageKit To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/2066183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066183] Re: AppStream metadata allow user uninstallation of PackageKit
The update description seems to be incorrect: "Backport patch to make PackageKit uninstallable from graphical software centers" It should be: "Backport patch to make PackageKit not uninstallable from graphical software centers" -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2066183 Title: AppStream metadata allow user uninstallation of PackageKit To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/2066183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100561] [NEW] Language and Region date format settings for Australia not obeyed
Public bug reported: After recently upgrading to 24.04.1 LTS (now 24.05.2 LTS) my "Language and Region" settings are not obeyed by Bash or Nautilus ... (24.04.2 LTS) I'm pretty certain I did not have this issue in 22.04.5 LTS (I would have noticed) Essentially my Settings are for DD/MM/ but Nautilus show MM/DD/ and bash MMM/DD my locale settings are definitely AU: locale LANG=en_AU.UTF-8 LANGUAGE=en_AU:en LC_CTYPE="en_AU.UTF-8" LC_NUMERIC="en_AU.UTF-8" LC_TIME="en_AU.UTF-8" LC_COLLATE="en_AU.UTF-8" LC_MONETARY="en_AU.UTF-8" LC_MESSAGES="en_AU.UTF-8" LC_PAPER="en_AU.UTF-8" LC_NAME="en_AU.UTF-8" LC_ADDRESS="en_AU.UTF-8" LC_TELEPHONE="en_AU.UTF-8" LC_MEASUREMENT="en_AU.UTF-8" LC_IDENTIFICATION="en_AU.UTF-8" echo $LANG responds en_AU.UTF-8 but curiously echo $LC_TIME respond with "" (nothing) which seems odd after export LC_TIME=en_AU.UTF-8 then echo $LC_TIME responds with en_AU.UTF-8 but still no change in nautilus and bash date formats ... $ lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04.2 LTS Release:24.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:46.5-0ubuntu0.24.04.1 Candidate: 1:46.5-0ubuntu0.24.04.1 Version table: *** 1:46.5-0ubuntu0.24.04.1 500 500 http://au.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:46.0.1-1ubuntu7 500 500 http://au.archive.ubuntu.com/ubuntu noble/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46.5-0ubuntu0.24.04.1 ProcVersionSignature: Ubuntu 6.8.0-54.56-generic 6.8.12 Uname: Linux 6.8.0-54-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img ./boot/grub/grub.cfg ./casper/initrd CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 08:49:48 2025 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-jammy-amd64-20230905-529 InstallationDate: Installed on 2023-09-18 (529 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-sutton-jammy-amd64-20230905-529 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to noble on 2025-02-05 (22 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- 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/2100561 Title: Language and Region date format settings for Australia not obeyed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2100561/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066183] Re: AppStream metadata allow user uninstallation of PackageKit
This bug was fixed in the package packagekit - 1.2.8-2ubuntu1.2 --- packagekit (1.2.8-2ubuntu1.2) noble; urgency=medium * Backport patch to make PackageKit uninstallable from graphical software centers (LP: #2066183) -- Alessandro Astone Wed, 08 Jan 2025 17:35:09 +0100 ** Changed in: packagekit (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2066183 Title: AppStream metadata allow user uninstallation of PackageKit To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/2066183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100307] Re: gtk4 fails to build with cpdb-libs 2.0~b7
The problem here is that the CPDB support for the GTK print dialog was created in an early stage of the formation of the second-generation API of CPDB. Some functions still had an instance name parameter and this parameter got dropped later. So in the GTK code the calls have to get corrected, removing the instance name. The patch should be proposed as merge request to GTK upstream and applied as distro patch for Plucky. Here is the commit in CPDB which did the change of dropping the instance name parameter: https://github.com/OpenPrinting/cpdb- libs/commit/fb2686ba8f2fc60dc95ae0e2421e386922bf232e So it is just removing the instance name of the calls of these functions. ** Changed in: cpdb-libs (Ubuntu) Status: Triaged => Invalid -- 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/2100307 Title: gtk4 fails to build with cpdb-libs 2.0~b7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpdb-libs/+bug/2100307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100475] Re: Whole display freezes in 1 second interval for a while
Those log messages might be relevant because the "RT" thread of gnome- shell has caused bugs before. Please try adding: MUTTER_DEBUG_KMS_THREAD_TYPE=user to /etc/environment and then reboot. ** Tags added: nvidia ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: kms-thread ** Tags added: kmsthread -- 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/2100475 Title: Whole display freezes in 1 second interval for a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2100475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100475] Re: Whole display freezes in 1 second interval for a while
** Package changed: xorg (Ubuntu) => gnome-shell (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/2100475 Title: Whole display freezes in 1 second interval for a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2100475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100482] Re: 2nd screen display resolution fails on resume from screen blanking
This problem has been plaguing me for months and now that I've created a bug report, the last two times the system went to sleep and I woke it up didn't result in the described behaviour. I'll monitor it and check in the morning again and if it's doesn't happen again, I'll close the bug. -- 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/2100482 Title: 2nd screen display resolution fails on resume from screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2100482/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100475] Re: Whole display freezes in 1 second interval for a while
Sorry, I was at work and then waited when the error reappeared.. Strange, after adding the ENV variable, the rtkit message in the syslog disappeared.. But the rest looks similar.. I added some other messages to the log, I don't know what relevance they have. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2100475/+attachment/5861050/+files/freeze.log -- 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/2100475 Title: Whole display freezes in 1 second interval for a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2100475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2069564] Re: [SRU] gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writabl
> who owns /tmp/.X11-unix after you login? in the case I can reproduce it is owned by gdm, and I can confirm it is a regression compared to *u4.1 as in *u4.1 it does not happen if /tmp/.X11-unix is owned by gdm. We're missing something different in our set ups then because exact same procedure gives different results... I'm testing in a virtual machine. After 'systemctl stop gdm; rm -r /tmp/.X11-unix; systemctl start gdm': File: /tmp/.X11-unix/ Size: 80 Blocks: 0 IO Block: 4096 directory Device: 0,32Inode: 276 Links: 2 Access: (1777/drwxrwxrwt) Uid: ( 120/ gdm) Gid: ( 122/ gdm) Access: 2025-02-27 08:35:02.481540724 +0100 Modify: 2025-02-27 08:35:02.861535505 +0100 Change: 2025-02-27 08:35:02.861535505 +0100 Birth: 2025-02-27 08:35:02.481540724 +0100 After logging in, same thing. By the way, I don't see > "Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix": 120.#012Ownership of "/tmp": 0.#012Current user: 1000." in your 4.2 log, but I see > (gnome-shell:9421): libmutter-ERROR **: 14:57:37.313: Failed to start X Wayland: Directory "/tmp/.X11-unix" is not writable in your 4.1 log, so looks like it's not the same failure Gre0 saw. > Should we move this to verification-failed? I think it is the safest to do. -- 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/2069564 Title: [SRU] gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writable"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2069564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100475] [NEW] Whole display freezes in 1 second interval for a while
You have been subscribed to a public bug: It happens anytime, even in fresh start of system (without any additional applications running). When I was watching syslog, exactly time of freeze is when in syslog appears this (repeating every second): 2025-02-27T10:00:59.144566+01:00 payne-desktop rtkit-daemon[2275]: Successfully made thread 3655 of process 3625 owned by '1000' RT at priority 20. 2025-02-27T10:00:59.144623+01:00 payne-desktop rtkit-daemon[2275]: Supervising 7 threads of 4 processes of 1 users. 2025-02-27T10:01:00.269073+01:00 payne-desktop rtkit-daemon[2275]: Successfully made thread 3655 of process 3625 owned by '1000' high priority at nice level 0. 2025-02-27T10:01:00.269220+01:00 payne-desktop rtkit-daemon[2275]: Supervising 7 threads of 4 processes of 1 users. 2025-02-27T10:01:00.349130+01:00 payne-desktop rtkit-daemon[2275]: Supervising 6 threads of 3 processes of 1 users. 2025-02-27T10:01:00.349515+01:00 payne-desktop rtkit-daemon[2275]: Supervising 6 threads of 3 processes of 1 users. 2025-02-27T10:01:00.352069+01:00 payne-desktop rtkit-daemon[2275]: Successfully made thread 3655 of process 3625 owned by '1000' RT at priority 20. 2025-02-27T10:01:00.352153+01:00 payne-desktop rtkit-daemon[2275]: Supervising 7 threads of 4 processes of 1 users. 2025-02-27T10:01:00.414952+01:00 payne-desktop rtkit-daemon[2275]: Successfully made thread 3655 of process 3625 owned by '1000' high priority at nice level 0. 2025-02-27T10:01:00.415046+01:00 payne-desktop rtkit-daemon[2275]: Supervising 7 threads of 4 processes of 1 users. 2025-02-27T10:01:00.426498+01:00 payne-desktop rtkit-daemon[2275]: Supervising 6 threads of 3 processes of 1 users. 2025-02-27T10:01:00.426880+01:00 payne-desktop rtkit-daemon[2275]: Supervising 6 threads of 3 processes of 1 users. 2025-02-27T10:01:00.429189+01:00 payne-desktop rtkit-daemon[2275]: Successfully made thread 3655 of process 3625 owned by '1000' RT at priority 20. 2025-02-27T10:01:00.429242+01:00 payne-desktop rtkit-daemon[2275]: Supervising 7 threads of 4 processes of 1 users. 2025-02-27T10:01:00.468652+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). 2025-02-27T10:01:00.468958+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 2025-02-27T10:01:00.469000+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 2025-02-27T10:01:00.469187+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 2025-02-27T10:01:00.469223+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 2025-02-27T10:01:00.469255+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 2025-02-27T10:01:00.469301+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). 2025-02-27T10:01:00.469332+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 2025-02-27T10:01:00.469364+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 2025-02-27T10:01:00.469392+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 2025-02-27T10:01:00.469420+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 2025-02-27T10:01:00.469447+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 2025-02-27T10:01:00.469480+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 2025-02-27T10:01:00.469501+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 2025-02-27T10:01:00.469535+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 2025-02-27T10:01:00.469562+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 2025-02-27T10:01:00.469600+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 2025-02-27T10:01:00.469622+01:00 payne-desktop gnome-shell[3625]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Pro
[Bug 2100482] [NEW] 2nd screen display resolution fails on resume from screen blanking
Public bug reported: This bug occurs with both X11 and Wayland. I currently have Wayland enabled, so I'll file from that perspective. Symptom: When the system recovers from having it's screens blanked, the Dell 19" (monitor 0) comes on at Standard VGA resolution. If I power the monitor down and back up again, it's recovers the correct settings. Monitors: 3 0: +*DP-2 1440/420x900/260+1440+0 DP-2 1: +DP-1 1440/410x900/260+0+0 DP-1 2: +eDP-1 1536/310x864/170+2880+36 eDP-1 0 is a Dell 19" 1 is a Benq 19" 2 is the builtin laptop monitor The are physically arranged from left to right: 1, 0, 2 I have screen blanking set to 15 minutes. # System Details Report --- ## Report details - **Date generated:** 2025-02-27 13:22:46 ## Hardware Information: - **Hardware Model:** ASUSTeK COMPUTER INC. ZenBook UX425EA_UX425EA - **Memory:** 16.0 GiB - **Processor:** 11th Gen Intel® Core™ i7-1165G7 × 8 - **Graphics:**Intel® Xe Graphics (TGL GT2) - **Disk Capacity:** 512.1 GB ## Software Information: - **Firmware Version:**UX425EA.319 - **OS Name:** Ubuntu 24.04.2 LTS - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.11.0-17-generic I'll now wait for a screen blank to occur and then attach the /var/log/syslog file for details. ** Affects: gnome-shell (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/2100482 Title: 2nd screen display resolution fails on resume from screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2100482/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2089835] Re: gnome-terminal crashes when detaching window
*** This bug is a duplicate of bug 2049923 *** https://bugs.launchpad.net/bugs/2049923 I'm having this problem now just after upgrade from ubuntu 22.04 to 24.04 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.04.2 LTS Release:24.04 Codename: noble -- 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/2089835 Title: gnome-terminal crashes when detaching window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2089835/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2049923] Re: gnome-terminal freezing, then crashing
I have this problem now after upgrading from Ubuntu 22.04 to 24.04 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.04.2 LTS Release:24.04 Codename: noble -- 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/2049923 Title: gnome-terminal freezing, then crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
