[Desktop-packages] [Bug 2047629] [NEW] gnome-shell crashed with SIGSEGV in __GI_getenv()
Public bug reported: Just started, no applications active ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Dec 28 08:28:30 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-12-10 (18 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.2-3ubuntu1 SegvAnalysis: Segfault happened at: 0x7f8199c45e5d <__GI_getenv+77>: cmp(%rbx),%r12b PC (0x7f8199c45e5d) ok source "(%rbx)" (0x5596cecb6618) not located in a known VMA region (needed readable region)! destination "%r12b" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7f81962d5e5a "EXPAT_ENTROPY_DEBUG") at ./stdlib/getenv.c:31 ?? () from /lib/x86_64-linux-gnu/libexpat.so.1 ?? () from /lib/x86_64-linux-gnu/libexpat.so.1 XML_ParseBuffer () from /lib/x86_64-linux-gnu/libexpat.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace noble ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2047629 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() Status in gnome-shell package in Ubuntu: New Bug description: Just started, no applications active ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Dec 28 08:28:30 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-12-10 (18 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.2-3ubuntu1 SegvAnalysis: Segfault happened at: 0x7f8199c45e5d <__GI_getenv+77>: cmp (%rbx),%r12b PC (0x7f8199c45e5d) ok source "(%rbx)" (0x5596cecb6618) not located in a known VMA region (needed readable region)! destination "%r12b" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7f81962d5e5a "EXPAT_ENTROPY_DEBUG") at ./stdlib/getenv.c:31 ?? () from /lib/x86_64-linux-gnu/libexpat.so.1 ?? () from /lib/x86_64-linux-gnu/libexpat.so.1 XML_ParseBuffer () from /lib/x86_64-linux-gnu/libexpat.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047585] Re: gnome-remote-desktop-daemon stops responding to mouse input
The input issues were upstream-wise already fixed some months ago (See for this https://gitlab.freedesktop.org/libinput/libei/-/issues/46, https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3273). First, update your system. According to your Dependencies.txt log, you use an old version of mutter, while the current one (45.2) already gets rid one source of that bug (Ubuntu appears to ship mutter-45.2). Always update your system before reporting a bug. The other sources of input bugs in g-r-d and libei were fixed in g-r-d-45.1 and libei-1.2.0. These releases were already done some time ago, but the Ubuntu Desktop Team did not push these updates to Ubuntu, which Ubuntu is notorious for. I suggest you to nag the Ubuntu Desktop Team to push these updates. That's the only way for a chance to get them into Ubuntu. ** Bug watch added: gitlab.freedesktop.org/libinput/libei/-/issues #46 https://gitlab.freedesktop.org/libinput/libei/-/issues/46 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2047585 Title: gnome-remote-desktop-daemon stops responding to mouse input Status in gnome-remote-desktop package in Ubuntu: New Bug description: Using Ubuntu 23.10 mantic, RDClient on MacOS or even Windows Remote Desktop Client, the RDP session suddenly freezes with the following entries in logs 2023-12-27T14:15:57.255492-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: [14:14:10:011] [1685:140241] [INFO][ 14:15:57 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.256197-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.379168-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 119 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:57.379816-05:00 ubuntuvm gnome-shell[1772]: Client error: socket disconnected 2023-12-27T14:15:57.379912-05:00 ubuntuvm gnome-shell[1772]: Failed to add device, disconnecting client 2023-12-27T14:15:57.380164-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.380837-05:00 ubuntuvm gnome-shell[1772]: Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4. 2023-12-27T14:15:57.381471-05:00 ubuntuvm gnome-shell[1772]: message repeated 17 times: [ Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4.] 2023-12-27T14:15:57.381510-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.381586-05:00 ubuntuvm gnome-shell[1772]: Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4. 2023-12-27T14:15:57.382172-05:00 ubuntuvm gnome-shell[1772]: message repeated 19 times: [ Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4.] 2023-12-27T14:15:57.382205-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.947437-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 345 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:58.067012-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: 14:15:58 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:58.096724-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:58.930342-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 404 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:59.006279-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: 14:15:59 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:59.008501-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:59.539393-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 208 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating
[Desktop-packages] [Bug 2047602] [NEW] suid missing
Public bug reported: $ ls -l `which bwrap` -rwxr-xr-x 1 root root 72160 Feb 28 2023 /usr/bin/bwrap Expected output (otherwise it refuses to run from non-root): $ ls -l `which bwrap` -rwsr-xr-x 1 root root 72160 Feb 28 2023 /usr/bin/bwrap Manual `chroot u+s` seems to fix the issue. Version: 0.8.0-2 Ubuntu Noble ** Affects: bubblewrap (Ubuntu) Importance: Undecided Status: New ** Description changed: $ ls -l `which bwrap` -rwxr-xr-x 1 root root 72160 Feb 28 2023 /usr/bin/bwrap Expected output (otherwise it refuses to run from non-root): $ ls -l `which bwrap` -rwsr-xr-x 1 root root 72160 Feb 28 2023 /usr/bin/bwrap Manual `chroot u+s` seems to fix the issue. + + Version: 0.8.0-2 + Ubuntu Noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2047602 Title: suid missing Status in bubblewrap package in Ubuntu: New Bug description: $ ls -l `which bwrap` -rwxr-xr-x 1 root root 72160 Feb 28 2023 /usr/bin/bwrap Expected output (otherwise it refuses to run from non-root): $ ls -l `which bwrap` -rwsr-xr-x 1 root root 72160 Feb 28 2023 /usr/bin/bwrap Manual `chroot u+s` seems to fix the issue. Version: 0.8.0-2 Ubuntu Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/2047602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
Microsoft has implemented an IPSec stack: https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies "The Microsoft implementation of IPsec uses Windows Filtering Platform to setup IPsec policies." This page is a bit thin on which applications to open, which buttons to click, etc, but they do have IPSec available in their ecosystem. Microsoft has implemented LT2P: https://learn.microsoft.com/en- US/troubleshoot/windows-server/networking/configure-l2tp-ipsec-server- behind-nat-t-device "This article describes how to configure a L2TP/IPsec server behind a NAT-T device." A third party has implemented OpenVPN for Windows: https://openvpn.net/client/client-connect-vpn-for-windows/ "For Windows 7, 8, 10, and 11. Note: Windows 7 and 8 are not officially supported anymore." A third party has implemented Wireguard for Windows: https://www.wireguard.com/install/#windows-7-81-10-11-2008r2-2012r2-2016-2019-2022 " Windows [7, 8.1, 10, 11, 2008R2, 2012R2, 2016, 2019, 2022 – v0.5.3]" Selecting a replacement requires some effort on the part of the network administrator with knowledge of what features and operating systems they need for their environment. I think pptp is bad enough that removing it makes sense. On the other hand, we still have telnet, and there's appropriate uses and inappropriate uses, and maybe this falls into the same category of compatibility software where users should expect a significant reduction in security if it is used. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Incomplete Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. IPSec OpenVPN Strongswan are much better alternatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046633] Re: Don't include 'nmcli -f all con' output in bug report (for privacy)
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2046633 Title: Don't include 'nmcli -f all con' output in bug report (for privacy) Status in network-manager package in Ubuntu: New Bug description: The apport bug reporting hooks for this package (/usr/share/apport/package/hooks/source_network-manager{,-applet}.py) include the output of `nmcli -f all con`. This lists all wifi SSIDs that the user has ever connected to, and the date of last connection. I think this is a privacy problem, as it tends to reveal the user's recent whereabouts, and it's posted publicly on launchpad. (Imagine for instance an entry for "LoveMotelGuestWifi" at a time when the user had said they were at the office...) It is disclosed to the user before the report is sent, but only if they think to expand that item in the "Send / Don't send" dialog (which is not descriptively labeled), and there is no way to opt out of it. You can delete it manually from launchpad afterward, which is what I am going to do with this bug report, but I doubt most people would know to do that. This info should probably not be included at all, or if it is, it should be sanitized. Also, it might be a good idea to purge launchpad of all such files. (Marking this as "security" in case you consider this kind of a privacy leak to be something the security team should handle. If not, feel free to demote it to an ordinary bug.) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Dec 16 14:38:45 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-06-03 (1657 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.13 dev enxa0cec8c4f782 proto dhcp src 192.168.1.60 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev enxa0cec8c4f782 proto kernel scope link src 192.168.1.60 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-12-14 (3 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-04T11:07:36.415303 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1992257] Re: gnome-control-center crashed with SIGSEGV in _gtk_widget_is_sensitive(widget=0x0) from gtk_shortcut_controller_run_controllers()
** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1992257 Title: gnome-control-center crashed with SIGSEGV in _gtk_widget_is_sensitive(widget=0x0) from gtk_shortcut_controller_run_controllers() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/1cb8db326cd012507ef5cb0f421d0d1cb07c961f --- Crashes instantly and consistently on the Sharing page on multiple installs. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:54:48 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-10-08 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) JournalErrors:  أكتوبر 08 21:54:38 hostname gnome-control-c[13302]: Could not set system time: GDBus.Error:org.freedesktop.timedate1.AutomaticTimeSyncEnabled: Automatic time synchronization is enabled  أكتوبر 08 21:54:49 hostname kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:c0:05:c2:16:ce:e0:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=58818 PROTO=2  أكتوبر 08 21:54:51 hostname kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:90:56:82:00:cf:8c:08:00 SRC=192.168.0.11 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 ProcCmdline: gnome-control-center sound SegvAnalysis:  Segfault happened at: 0x7fc4a5233600:mov0x18(%rax),%rax  PC (0x7fc4a5233600) ok  source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)!  destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop:  ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1  ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1  ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1  ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1  ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1992257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047591] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1992257 *** https://bugs.launchpad.net/bugs/1992257 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1992257, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2047591/+attachment/5733585/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2047591/+attachment/5733587/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2047591/+attachment/5733589/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2047591/+attachment/5733590/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2047591/+attachment/5733591/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2047591/+attachment/5733592/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2047591/+attachment/5733593/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1992257 gnome-control-center crashed with SIGSEGV in _gtk_widget_is_sensitive(widget=0x0) from gtk_shortcut_controller_run_controllers() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2047591 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: Vanilla Ubuntu, but modified to be a "Rolling Release": sudo sed -i 's/focal/devel/g' /etc/apt/sources.list apt-get dist-upgrade apt update apt upgrade Run in VirtualBox, with VBoxGuestAdditions. I had a possibly similar bug minutes before: I installed code_1.85.1-1702462158_amd64.deb of VS Code (from https://code.visualstudio.com/docs/setup/linux), then I started VS Code. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:45.0-1ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 27 13:39:08 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-12-07 (20 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-control-center ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f86ecbeb623:mov0x18(%rax),%rax PC (0x7f86ecbeb623) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2047591/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047585] [NEW] gnome-remote-desktop-daemon stops responding to mouse input
Public bug reported: Using Ubuntu 23.10 mantic, RDClient on MacOS or even Windows Remote Desktop Client, the RDP session suddenly freezes with the following entries in logs 2023-12-27T14:15:57.255492-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: [14:14:10:011] [1685:140241] [INFO][ 14:15:57 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.256197-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.379168-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 119 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:57.379816-05:00 ubuntuvm gnome-shell[1772]: Client error: socket disconnected 2023-12-27T14:15:57.379912-05:00 ubuntuvm gnome-shell[1772]: Failed to add device, disconnecting client 2023-12-27T14:15:57.380164-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.380837-05:00 ubuntuvm gnome-shell[1772]: Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4. 2023-12-27T14:15:57.381471-05:00 ubuntuvm gnome-shell[1772]: message repeated 17 times: [ Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4.] 2023-12-27T14:15:57.381510-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.381586-05:00 ubuntuvm gnome-shell[1772]: Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4. 2023-12-27T14:15:57.382172-05:00 ubuntuvm gnome-shell[1772]: message repeated 19 times: [ Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4.] 2023-12-27T14:15:57.382205-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.947437-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 345 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:58.067012-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: 14:15:58 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:58.096724-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:58.930342-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 404 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:59.006279-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: 14:15:59 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:59.008501-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:59.539393-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 208 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:59.543880-05:00 ubuntuvm dbus-daemon[1521]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.26" pid=3585 label="snap.firefox.firefox" peer_pid=1772 peer_label="unconfined" 2023-12-27T14:15:59.550634-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:59.988595-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 227 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:16:00.112724-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: 14:16:00 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:16:00.116829-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:16:00.188927-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 30 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: devi
[Desktop-packages] [Bug 2047579] [NEW] gnome-software unuable to install updates (Prepared update not found)
Public bug reported: Click on 'Software' then 'Updates' then on 'Download' then 'Restart & Update' I have a error message: 'Unable to install updates: Prepared update not found:/var/lib/PackageKit/prepared-update' lsb_release -a : 'Ubuntu 22.04.3 LTS' (however this is Xubuntu 22.04.3). apt-cache policy gnome-software: installed 41.5-2ubuntu2 Note: My bug report seems very similar to bug #1900167 opened in october 2020 by a other user (on Ubuntu 20.10). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-software 41.5-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Dec 27 17:36:48 2023 InstallationDate: Installed on 2023-03-27 (275 days ago) InstallationMedia: Xubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) InstalledPlugins: Â gnome-software-plugin-flatpak N/A Â gnome-software-plugin-snap41.5-2ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot error message (Prepared update not found)" https://bugs.launchpad.net/bugs/2047579/+attachment/5733511/+files/screenshot_2023-12-17_12-43-57_Error_Prepared_update_not_found.png ** Description changed: Click on 'Software' then 'Updates' then on 'Download' then 'Restart & Update' I have a message: Unable to install updates: GDBus.error... Prepared update not found:/var/lib/PackageKit/prepared-update lsb_release -a : 'Ubuntu 22.04.3 LTS' (however this is Xubuntu 22.04.3). apt-cache policy gnome-software: installed 41.5-2ubuntu2 - Note: My bug report seems very similar to bug #1900167 opened in october - 2020 by a other user (on Ubuntu 20.10). + Note: My bug report seems very similar to bug #1900167 opened in october 2020 by a other user (on Ubuntu 20.10). + Note: I make this new bug report because this is the third time I have this issue on computers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-software 41.5-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Dec 27 17:36:48 2023 InstallationDate: Installed on 2023-03-27 (275 days ago) InstallationMedia: Xubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) InstalledPlugins: - gnome-software-plugin-flatpak N/A - gnome-software-plugin-snap41.5-2ubuntu2 + Â gnome-software-plugin-flatpak N/A + Â gnome-software-plugin-snap41.5-2ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - Click on 'Software' then 'Updates' then on 'Download' then 'Restart & Update' I have a message: - Unable to install updates: GDBus.error... Prepared update not found:/var/lib/PackageKit/prepared-update + Click on 'Software' then 'Updates' then on 'Download' then 'Restart & Update' I have a error message: + 'Unable to install updates: Prepared update not found:/var/lib/PackageKit/prepared-update' lsb_release -a : 'Ubuntu 22.04.3 LTS' (however this is Xubuntu 22.04.3). apt-cache policy gnome-software: installed 41.5-2ubuntu2 - Note: My bug report seems very similar to bug #1900167 opened in october 2020 by a other user (on Ubuntu 20.10). - Note: I make this new bug report because this is the third time I have this issue on computers. + Note: My bug report seems very similar to bug #1900167 opened in october + 2020 by a other user (on Ubuntu 20.10). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-software 41.5-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Dec 27 17:36:48 2023 InstallationDate: Installed on 2023-03-27 (275 days ago) InstallationMedia: Xubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) InstalledPlugins: Â gnome-software-plugin-flatpak N/A Â gnome-software-plugin-snap41.5-2ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047579 Title: gnome-software unuable to install updates (Prepared update not found) Status in gnome-software package in Ubuntu: New Bug description: Click on 'Software' then 'Updates' then on 'Download' then 'Restart & Update' I have a error message: 'Unable to install updates: Prepared update no
[Desktop-packages] [Bug 2047511] [NEW] Screen brightness
Public bug reported: Ubuntu 22.04.3 LTS Release: 22.04 Brightness of the screen is down to minimum and I can't change it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 27 11:15:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] NVIDIA Corporation GK107M [GeForce GT 645M] [10de:0fd9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 645M] [17aa:3904] InstallationDate: Installed on 2023-12-10 (16 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 20202 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.release: 0.49 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN31WW(V1.10) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvr71CN31WW(V1.10):bd11/16/2012:br0.49:efr1.49:svnLENOVO:pn20202:pvrLenovoIdeaPadZ500:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500:skuLENOVO_MT_20202: dmi.product.family: IDEAPAD dmi.product.name: 20202 dmi.product.sku: LENOVO_MT_20202 dmi.product.version: Lenovo IdeaPad Z500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2047511 Title: Screen brightness Status in xorg package in Ubuntu: New Bug description: Ubuntu 22.04.3 LTS Release: 22.04 Brightness of the screen is down to minimum and I can't change it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 27 11:15:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] NVIDIA Corporation GK107M [GeForce GT 645M] [10de:0fd9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 645M] [17aa:3904] InstallationDate: Installed on 2023-12-10 (16 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 20202 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG