[Bug 2100655] Re: [nouveau] Second monitor shows only cursor visible when using Wayland with Nouveau driver - Switching to Xorg solved issue
Yes when you have time, please do so in a Wayland 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/2100655 Title: [nouveau] Second monitor shows only cursor visible when using Wayland with Nouveau driver - Switching to Xorg solved issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2100655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100865] [NEW] Update error in Discover
Public bug reported: Rozwiązywanie kwestii zależności nie powiodło się:The following packages have unmet dependencies: libonnxruntime1.20.1: W konflikcie z: libonnxruntime1.19.2 but 1.19.2+dfsg-9build1 is to be installed ProblemType: Bug DistroRelease: Ubuntu 25.04 Package: flatpak 1.16.0-1 ProcVersionSignature: Ubuntu 6.12.0-16.16-generic 6.12.11 Uname: Linux 6.12.0-16-generic x86_64 ApportVersion: 2.32.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Mar 4 15:03:48 2025 InstallationDate: Installed on 2025-02-22 (10 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250220) SourcePackage: flatpak UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug plucky wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2100865 Title: Update error in Discover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2100865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100864] [NEW] Freedesktop Platform cannot update
Public bug reported: Nie można odmontować systemu plików revokefs-fuse w /var/tmp/flatpak- cache-DHWM22/org.gtk.Gtk3theme.Breeze-N25P22: Child process exited with code 1 ProblemType: Bug DistroRelease: Ubuntu 25.04 Package: flatpak 1.16.0-1 ProcVersionSignature: Ubuntu 6.12.0-16.16-generic 6.12.11 Uname: Linux 6.12.0-16-generic x86_64 ApportVersion: 2.32.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Mar 4 15:01:27 2025 InstallationDate: Installed on 2025-02-22 (10 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250220) SourcePackage: flatpak UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug plucky wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2100864 Title: Freedesktop Platform cannot update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2100864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2099727] Re: gnome-keyring-daemon crashed with SIGABRT in ???()
Hi, basically i dont have a specific steps or actions that caused the problem as it occurred while I'm using the desktop normally. I didn't face these issues with the recent package updates in plucky. Will update if it occurs again in the future. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2099727 Title: gnome-keyring-daemon crashed with SIGABRT in ???() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2099727/+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
Any workarounds? -- 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 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
Any workarounds? -- 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/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2098016] Re: Ubuntu 24.04 WiFi from gdm3 login screen: cannot select new network
We will only SRU the gnome-shell fix for accessing the secrets keyring, but not new polkit rules. This will bring back feature-parity with Jammy and nothing more. ** Changed in: gdm3 (Ubuntu Noble) Status: In Progress => Opinion ** Changed in: gdm3 (Ubuntu Oracular) Status: In Progress => Opinion ** Changed in: gnome-shell (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Oracular) Importance: Undecided => Medium -- 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/2098016 Title: Ubuntu 24.04 WiFi from gdm3 login screen: cannot select new network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2098016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2098016] Re: Ubuntu 24.04 WiFi from gdm3 login screen: cannot select new network
** Description changed: + [ Impact ] + + In Ubuntu 24.04 and newer, connecting to a new password-protected Wi-Fi + network from the log-in screen is not possible because the user never + gets prompted for the password; instead, the connection silently fails. + + The log-in screen of Ubuntu Desktop is implemented by running GNOME Shell in the "greeter" mode. + When requesting to connect to a new wifi network, gnome-shell tries to communicate with the org.freedesktop.secrets service to check whether the password for this network is already known, but that fails when running in "greeter" mode because gnome-keyring is registered on one dbus address while gnome-shell only has access to a dedicated/isolated dbus bus. When this fails, gnome-shell aborts the connection attempt. + + Because the log-in session runs under a special user "gdm", it will not + have any secrets stored as if it were a regular user, so it is pointless + to query the org.freedesktop.secrets service. Thus to fix the issue, we + implemented a patch that avoids querying org.freedesktop.secrets when + running in "greeter" mode altogether and instead always prompt the user + to provide a password. + + This solution was accepted by GNOME upstream. + + [ Test Plan ] + + 0. Have a password-protected Wi-Fi network available for testing. + 1. Set up an Ubuntu Desktop system on a machine with a Wi-Fi card. + 1.1 If already connected to the Wi-Fi network, navigate to Settings to "Forget Connection..." + 2. Reach the log-in screen. + 3. Click the status bar to access the quick settings. + 4. Click on the ">" arrow to expand the list of Wi-Fi networks. + 5. Select the Wi-Fi network you want to use for testing. + 6. Verify that you get prompted for the network password. + 7. Insert the network password. + 8. Verify that the connection succeeded. + + [ Regression Test Plan 1 ] + + Perform the same steps as above from a logged-in user session, rather + than from the log-in screen. + + [ Regression Test Plan 2 ] + + Verify that you can connect to an already registered Wi-Fi network from + the log-in screen. + + [ Where things could go wrong ] + + The patch modifies the Network Applet in GNOME Shell, a critical component of Ubuntu Desktop. + A grave misbehaviour could manifest with the user being unable to log-in, or being suddently logged-out of a desktop session in case of a crash. + A smaller misbehaviour could affect the network applet functionality only. The two regression plans will verify that this is not the case. + + + [ Original description ] + Steps to reproduce 1. Create LXD VM desktop-noble lxc init --vm ubuntu:24.04 desktop-noble 2. Passthrough wifi device, in my case Intel Wifi via PCI works fine, some USB devices can have problem with initialization lxc config device add desktop-noble wifipci pci address= where pci_address is address of your device seen via lspci command, i.e. 00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi (rev 11) 3. lxc start desktop-noble 2. lxc exec desktop-noble bash 3. Install ubuntu-desktop metapackage apt update apt install -y ubuntu-desktop 4. Set passwd for ubuntu user $ passwd ubuntu 5. Disable systemd-networkd-wait-online.service (otherwise it will wait for timeout) - systemctl disable --now systemd-networkd-wait-online.service + systemctl disable --now systemd-networkd-wait-online.service 6. Connect to the vga console lxc console --type=vga desktop-noble Wait for login screen to load Click on the top-right corner and pick the wifi network you would like to connect Expected result The window will popup to pick the choose the password The actual result Nothing happens, yet you will see in the logs: Feb 11 17:10:35 desktop-noble gnome-shell[1353]: Cursor update failed: drmModeAtomicCommit: Invalid argument Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Successfully made thread 1376 of process 1353 owned by '124' high priority at nice level 0. Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Supervising 8 threads of 5 processes of 1 users. Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users. Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users. Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Successfully made thread 1376 of process 1353 owned by '124' RT at priority 20. Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Supervising 8 threads of 5 processes of 1 users. Feb 11 17:10:35 desktop-noble /usr/libexec/gdm-wayland-session[3686]: discover_other_daemon: 1 Feb 11 17:10:35 desktop-noble /usr/libexec/gdm-wayland-session[1305]: dbus-daemon[1305]: [session uid=124 pid=1305] Failed to activate service 'org.freedesktop.secrets': timed out (service_start_timeout=12ms) Feb 11 17:10:37 desktop-noble kernel: Lockdown: systemd-logind: hibernation is restricted; see man kerne
[Bug 2100561] Re: Language and Region date format settings for Australia not obeyed
That's an interesting read. So perhaps I did have the problem in 22.04, I just didn't notice. Entirely possible given I and new to Linux and was "drinking from a fire hose". I now have a partial workaround, if I select UK formats the problem dissapears in Nautilus and the date-time displayed in the top bar of the desktop is now "Wed 5 Mar 09:19:12" as it should be. But not in bash, it is still "frack the bunt" for an Australian mind. -- 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 2100561] Re: Language and Region date format settings for Australia not obeyed
FYI I have just upgraded to 24.10 and my last comment is still correct.. -- 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 2100561] Re: Language and Region date format settings for Australia not obeyed
Also AFAIK Australia and the UK use identical date formats. -- 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 2100905] [NEW] FFe: poppler 25.03 transition
Public bug reported: I'd like to do a poppler 25.03 transition now for Ubuntu 25.04 for the same reasons as presented in the accompanying Debian bug. This is needed to not be stuck with Paper 48 Beta but be able to update it to 48 RC and then to 48.0 before Ubuntu 25.04 is released. libreoffice will need a fix from libreoffice 25.2.2 rc1 https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/commit/3af018486f87d xpdf needs a cherry-picked fix scribus is fixed in Unstable so we'll sync that update. No other build fixes should be needed. ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Affects: poppler (Debian) Importance: Unknown Status: Unknown ** Tags: plucky ** Bug watch added: Debian Bug tracker #1099557 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099557 ** Also affects: poppler (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099557 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/2100905 Title: FFe: poppler 25.03 transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/2100905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100905] Re: FFe: poppler 25.03 transition
** Changed in: poppler (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/2100905 Title: FFe: poppler 25.03 transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/2100905/+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
** Tags added: udeng-6305 ** Also affects: gnome-shell (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Plucky) Importance: Undecided Status: Confirmed ** Changed in: gnome-shell (Ubuntu Plucky) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Oracular) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Plucky) Milestone: None => ubuntu-25.04 ** Changed in: gnome-shell (Ubuntu Oracular) Milestone: None => oracular-updates ** Changed in: gnome-shell (Ubuntu Noble) Milestone: None => noble-updates ** Changed in: gnome-shell (Ubuntu Plucky) Status: Confirmed => Triaged ** Changed in: gnome-shell (Ubuntu Oracular) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Noble) Status: New => Triaged -- 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 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
** Tags added: udeng-6306 ** Changed in: mutter (Ubuntu) Milestone: None => ubuntu-25.04 ** Also affects: mutter (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Plucky) Importance: Medium Status: Triaged ** Also affects: mutter (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Oracular) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Oracular) Milestone: None => oracular-updates ** Changed in: mutter (Ubuntu Noble) Milestone: None => noble-updates ** Changed in: mutter (Ubuntu Oracular) Status: New => Triaged ** Changed in: mutter (Ubuntu Noble) 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/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063005/+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
Daniel, given the verification-failed, please remove the fix. -- 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 2100841] [NEW] not opening from usb drives | permission denied
Public bug reported: Can not open the files from usb drives. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gedit-usb-drive-not-open-Screenshot-from-2025-03-04 14-12-42.png" https://bugs.launchpad.net/bugs/2100841/+attachment/5862044/+files/gedit-usb-drive-not-open-Screenshot-from-2025-03-04%2014-12-42.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/2100841 Title: not opening from usb drives | permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2100841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2100655] Re: Second monitor shows only cursor visible when using Wayland with Nouveau driver - Switching to Xorg solved issue
Hi Daniel I am currently using the computer for a project - I will do so when I get a chance - Need to switch back to wayland first I suppose ? As mentioned, it is working with Xorg at the moment. Fanus On Tue, 4 Mar 2025 at 07:35, Daniel van Vugt <2100...@bugs.launchpad.net> wrote: > Thanks for the bug report. While the problem is happening, please open a > terminal and run: > > journalctl -b0 > journal.txt > > and then attach the resulting text file here. > > > ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > ** Tags added: nouveau > > ** Summary changed: > > - Second monitor shows only cursor visible when using Wayland with > Nouveau driver - Switching to Xorg solved issue > + [nouveau] Second monitor shows only cursor visible when using Wayland > with Nouveau driver - Switching to Xorg solved issue > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2100655 > > Title: > [nouveau] Second monitor shows only cursor visible when using Wayland > with Nouveau driver - Switching to Xorg solved issue > > Status in mutter package in Ubuntu: > Incomplete > > Bug description: > Your hardware: HP EliteDesk 800 G1 SFF with NVIDIA GT 620 > > Ubuntu version: 24.04 > > The issue: Second monitor works only with cursor visible when using > Wayland with Nouveau driver > > The solution that worked: Switching to Xorg by setting > WaylandEnable=false in /etc/gdm3/custom.conf > > The error message I found: "nouveau :01:00.0: gr: DATA_ERROR > 009c [] ch 5 [003f9dd000 gnome-shell[2932]] subc 0 class 9197 mthd > 0d78 data 0004" > > > Suggest that Ubuntu might want to improve detection of these older > NVIDIA cards and automatically switch to Xorg or provide a notification to > users experiencing the issue. > > ProblemType: Bug > DistroRelease: Ubuntu 24.04 > Package: xorg 1:7.7+23ubuntu3 > ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11 > Uname: Linux 6.11.0-17-generic x86_64 > NonfreeKernelModules: zfs > ApportVersion: 2.28.1-0ubuntu3.3 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: pass > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat Mar 1 12:51:37 2025 > DistUpgraded: Fresh install > DistroCodename: noble > DistroVariant: ubuntu > DpkgLog: > > GraphicsCard: >Subsystem: Hewlett-Packard Company EliteDesk 800 G1 [103c:1998] >NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if > 00 [VGA controller]) > Subsystem: Gigabyte Technology Co., Ltd GF108 [GeForce GT 620] > [1458:3547] > InstallationDate: Installed on 2024-08-10 (203 days ago) > InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 > (20240424) > MachineType: Hewlett-Packard HP EliteDesk 800 G1 SFF > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-17-generic > root=UUID=918c2851-4a60-4bfe-bc42-25f1ad513db7 ro quiet splash > nouveau.modeset=1 vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 09/09/2013 > dmi.bios.release: 2.18 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: L01 v02.18 > dmi.board.asset.tag: TRF3480BGY > dmi.board.name: 1998 > dmi.board.vendor: Hewlett-Packard > dmi.chassis.asset.tag: TRF3480BGY > dmi.chassis.type: 4 > dmi.chassis.vendor: Hewlett-Packard > dmi.modalias: > dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:br2.18:svnHewlett-Packard:pnHPEliteDesk800G1SFF:pvr:rvnHewlett-Packard:rn1998:rvr:cvnHewlett-Packard:ct4:cvr:skuH5U03EA#ACQ: > dmi.product.family: 103C_53307F G=D > dmi.product.name: HP EliteDesk 800 G1 SFF > dmi.product.sku: H5U03EA#ACQ > dmi.sys.vendor: Hewlett-Packard > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.122-1~ubuntu0.24.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.8-1ubuntu1~24.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20210115-1build1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.17-2build1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2100655/+subscriptions > > -- 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/2100655 Title: [nouveau] Second monitor shows only cursor visible when using Wayland with Nouveau driver - Switching to Xorg solved issue To manage notifications about this bug go to: https
[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
No worries, done: https://salsa.debian.org/gnome-team/mutter/-/commit/ec587865e9a947f3a860ba145e3b56629d59822c While this is still one of the top crashers in 24.10, it is nowhere to be seen in 25.04 yet. So as 24.10 reaches EOL in July, if 25.04 remains fixed then we won't have to fix anything else here. ** Changed in: mutter (Ubuntu Oracular) Status: Fix Committed => Won't Fix ** Changed in: mutter (Ubuntu Oracular) Milestone: oracular-updates => None -- 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 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
> it is nowhere to be seen in 25.04 yet Well, the patch is included in 25.04 (except it was accidentally dropped on the GNOME 48 update, and now restored). -- 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 2090824] Re: mutter crashes on Ubuntu 24.04 while playing Among Us with meta_wayland_pointer_constraint_deactivate
> I would like to confirm the expected behavior is that when the screen is touched, the pointer lock is lifted so when moving the mouse the pointer would appear? I don't think touch input should lift the pointer lock; the two should be independent. But the browser itself might interpret a touch input as lifting the pointer lock, so you might see that behaviour. Chromium and Firefox seem to handle this differently. -- 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/2090824 Title: mutter crashes on Ubuntu 24.04 while playing Among Us with meta_wayland_pointer_constraint_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2090824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2098016] Re: Ubuntu 24.04 WiFi from gdm3 login screen: cannot select new network
** Description changed: [ Impact ] In Ubuntu 24.04 and newer, connecting to a new password-protected Wi-Fi network from the log-in screen is not possible because the user never gets prompted for the password; instead, the connection silently fails. The log-in screen of Ubuntu Desktop is implemented by running GNOME Shell in the "greeter" mode. When requesting to connect to a new wifi network, gnome-shell tries to communicate with the org.freedesktop.secrets service to check whether the password for this network is already known, but that fails when running in "greeter" mode because gnome-keyring is registered on one dbus address while gnome-shell only has access to a dedicated/isolated dbus bus. When this fails, gnome-shell aborts the connection attempt. Because the log-in session runs under a special user "gdm", it will not have any secrets stored as if it were a regular user, so it is pointless to query the org.freedesktop.secrets service. Thus to fix the issue, we implemented a patch that avoids querying org.freedesktop.secrets when running in "greeter" mode altogether and instead always prompt the user to provide a password. This solution was accepted by GNOME upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3646 [ Test Plan ] 0. Have a password-protected Wi-Fi network available for testing. 1. Set up an Ubuntu Desktop system on a machine with a Wi-Fi card. 1.1 If already connected to the Wi-Fi network, navigate to Settings to "Forget Connection..." 2. Reach the log-in screen. 3. Click the status bar to access the quick settings. 4. Click on the ">" arrow to expand the list of Wi-Fi networks. 5. Select the Wi-Fi network you want to use for testing. 6. Verify that you get prompted for the network password. 7. Insert the network password. 8. Verify that the connection succeeded. + + NOTE: In order for the Wi-Fi network to still be usable after log-in, you will need to allow the "gdm" user to modify the system-wide network settings with a polkit rule like so: https://gitlab.gnome.org/GNOME/gdm/-/raw/288df842e8b76efa53a115835933f3901d064122/data/polkit-gdm.rules.in + We are going to start allowing this by default in plucky, but is outside of the scope of this SRU. [ Regression Test Plan 1 ] Perform the same steps as above from a logged-in user session, rather than from the log-in screen. [ Regression Test Plan 2 ] Verify that you can connect to an already registered Wi-Fi network from the log-in screen. [ Where things could go wrong ] The patch modifies the Network Applet in GNOME Shell, a critical component of Ubuntu Desktop. A grave misbehaviour could manifest with the user being unable to log-in, or being suddently logged-out of a desktop session in case of a crash. A smaller misbehaviour could affect the network applet functionality only. The two regression plans will verify that this is not the case. [ Original description ] Steps to reproduce 1. Create LXD VM desktop-noble lxc init --vm ubuntu:24.04 desktop-noble 2. Passthrough wifi device, in my case Intel Wifi via PCI works fine, some USB devices can have problem with initialization lxc config device add desktop-noble wifipci pci address= where pci_address is address of your device seen via lspci command, i.e. 00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi (rev 11) 3. lxc start desktop-noble 2. lxc exec desktop-noble bash 3. Install ubuntu-desktop metapackage apt update apt install -y ubuntu-desktop 4. Set passwd for ubuntu user $ passwd ubuntu 5. Disable systemd-networkd-wait-online.service (otherwise it will wait for timeout) systemctl disable --now systemd-networkd-wait-online.service 6. Connect to the vga console lxc console --type=vga desktop-noble Wait for login screen to load Click on the top-right corner and pick the wifi network you would like to connect Expected result The window will popup to pick the choose the password The actual result Nothing happens, yet you will see in the logs: Feb 11 17:10:35 desktop-noble gnome-shell[1353]: Cursor update failed: drmModeAtomicCommit: Invalid argument Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Successfully made thread 1376 of process 1353 owned by '124' high priority at nice level 0. Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Supervising 8 threads of 5 processes of 1 users. Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users. Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Supervising 7 threads of 4 processes of 1 users. Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Successfully made thread 1376 of process 1353 owned by '124' RT at priority 20. Feb 11 17:10:35 desktop-noble rtkit-daemon[1312]: Supervising 8 threads of 5 processes of 1 users. Feb 11 17:10:35 desktop-
[Bug 2098016] Re: Ubuntu 24.04 WiFi from gdm3 login screen: cannot select new network
** Changed in: gnome-shell (Ubuntu Noble) Milestone: ubuntu-24.04.3 => noble-updates -- 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/2098016 Title: Ubuntu 24.04 WiFi from gdm3 login screen: cannot select new network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2098016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2100905] Re: FFe: poppler 25.03 transition
** Description changed: I'd like to do a poppler 25.03 transition now for Ubuntu 25.04 for the same reasons as presented in the accompanying Debian bug. This is needed to not be stuck with Paper 48 Beta but be able to update it to 48 RC and then to 48.0 before Ubuntu 25.04 is released. libreoffice will need a fix from libreoffice 25.2.2 rc1 https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/commit/3af018486f87d xpdf needs a cherry-picked fix scribus is fixed in Unstable so we'll sync that update. No other build fixes should be needed. + + We'll get an auto-tracker once it is actually uploaded but this tracker + should also be good. + + https://ubuntu-archive-team.ubuntu.com/transitions/html/poppler.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/2100905 Title: FFe: poppler 25.03 transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/2100905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
