[Desktop-packages] [Bug 2085799] [NEW] Files (nautilus) shows two windows active on dock
Public bug reported: Note: I don't know if this is a nautilus issue or a dock issue, but it only affects nautilus. When using nautilus, after some time the dock 'dots' that show the active instances seems to double up and my single window shows two dots. This happens most times I use nautilus. Ubuntu 21.10 Nautilus 1:47.0-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: nautilus 1:47.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 20:46:46 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(768, 546)' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2024-10-05 (23 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20241002) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 44.3-1 nautilus-extension-gnome-terminal 3.54.0-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular wayland-session ** Attachment added: "nautilus icon in dock showing two instances open (only one is actually open)" https://bugs.launchpad.net/bugs/2085799/+attachment/5832525/+files/Screenshot%20From%202024-10-28%2020-47-40.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2085799 Title: Files (nautilus) shows two windows active on dock Status in nautilus package in Ubuntu: New Bug description: Note: I don't know if this is a nautilus issue or a dock issue, but it only affects nautilus. When using nautilus, after some time the dock 'dots' that show the active instances seems to double up and my single window shows two dots. This happens most times I use nautilus. Ubuntu 21.10 Nautilus 1:47.0-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: nautilus 1:47.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 20:46:46 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(768, 546)' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2024-10-05 (23 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20241002) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 44.3-1 nautilus-extension-gnome-terminal 3.54.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2085799/+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 2002358] Re: Screen turned off after seconds of inactivity, fixed by xset -dpms; bug depending on kernel version?
I've noticed on Ubuntu 24.04 this appears to occur due to a mismatch between how Xorg blanks the screen and the configuration gnome-settings- daemon applies. If you go into GSD -> Power -> Screen Blank and set it to "Never", then go to Privacy & Security -> Blank Screen Delay -> Never, xset q still reports Screen Saver: prefer blanking yes, allow exposures: yes, timeout 600 cycle 600. In other words, changing the configuration in GSD does not actually turn off the screen saver in Xorg. However, this issue does not appear to impact Wayland. I was able to figure this out because my AMD box on Wayland doesn't have this problem, only my NVidia box on Xorg. A workaround is setting putting "xset s off" in your .bashrc or .xinitrc, but that still means that the configuration in GSD won't actually control your screen blank. ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2002358 Title: Screen turned off after seconds of inactivity, fixed by xset -dpms; bug depending on kernel version? Status in gnome-settings-daemon package in Ubuntu: New Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Bug description: Now and then I have the problem, that the screen turns off after seconds of keyboard or mouse inactivity. I think that it changes with kernel versions but I'm not 100% sure that kernel version is the cause. The annoying bug is present for some time then it's gone, and after a while, the problem is back. Two days ago following packages were installed or updated, since then the problem is there again: Install: linux-hwe-5.15-headers-5.15.0-57:amd64 (5.15.0-57.63~20.04.1, automatic), linux-image-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-headers-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-modules-extra-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-modules-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), update-manager-core:amd64 (1:20.04.10.10, 1:20.04.10.11), linux-libc-dev:amd64 (5.4.0-135.152, 5.4.0-136.153), libcurl4:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15), libksba8:amd64 (1.3.5-2ubuntu0.20.04.1, 1.3.5-2ubuntu0.20.04.2), update-manager:amd64 (1:20.04.10.10, 1:20.04.10.11), linux-image-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), gir1.2-nautilus-3.0:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), linux-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), libfabric1:amd64 (1.6.2-3, 1.6.2-3ubuntu0.1), nautilus:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), libnautilus-extension1a:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), python3-update-manager:amd64 (1:20.04.10.10, 1:20.04.10.11), nautilus-data:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), curl:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15) Today I figured out that xset -dpms solves the problem but xset s off does not. In gnome-control-center -> Power I have the following settings: Power Saving: Blank Screen -> 15 minutes ( Selecting Never doesn't change anything.) Suspend & Power Button: Automatic Suspend: On, Delay 15 minutes Power Button Action: Power off I'm using Description: Ubuntu 20.04.5 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 22:47:36 2023 InstallationDate: Installed on 2022-01-01 (372 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2002358/+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 2067613] Re: CVE-2024-5290 : Fix loading of arbitrary shared objects
Done! Nice write-up Rory :D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2067613 Title: CVE-2024-5290 : Fix loading of arbitrary shared objects Status in wpa package in Ubuntu: Fix Released Status in wpa package in Debian: Fix Released Bug description: Hello team We received a vulnerability report a while back - that lets users load arbitrary shared object files in the context of the wpa_supplicant process running as root in affected Ubuntu systems. TLDR : Upstream released a fix : https://w1.fi/cgit/hostap/commit/?id=c84388ee4c66bcd310db57489eac4a75fc600747 that includes a compile time config for allow-listing a set of shared objects. Details here : `wpa_supplicant` is a binary package of source `wpa` ```sh $ umt search wpa Running search command. Ubuntu packages: Release Version Pocket Component trusty 2.1-0ubuntu1.7 security main trusty/esm 2.1-0ubuntu1.7+esm4 security main xenial 2.4-0ubuntu6.8 security main bionic 2:2.6-15ubuntu2.8 security main focal 2:2.9-1ubuntu4.3security main jammy 2:2.10-6ubuntu2 updates main lunar 2:2.10-12release main mantic 2:2.10-15release main noble 2:2.10-21build4 release main Other packages: Release Version Pocket Component bookworm 2:2.10-12release main bullseye 2:2.9.0-21 release main buster 2:2.7+git20190128+0c1e29f-6+deb10u4 updates main testing 2:2.10-21.1 release main unstable 2:2.10-21.1 release main ``` Upstream - https://w1.fi/cgit upstream examples point to config that lets all users in group `wheel` access the frontend. debian and ubuntu use group membership to control access to D-Bus So in `debian/patches/02_dbus_group_policy.patch` ``` diff --git a/wpa_supplicant/dbus/dbus-wpa_supplicant.conf b/wpa_supplicant/dbus/dbus-wpa_supplicant.conf index e81b495..413c049 100644 --- a/wpa_supplicant/dbus/dbus-wpa_supplicant.conf +++ b/wpa_supplicant/dbus/dbus-wpa_supplicant.conf @@ -9,6 +9,11 @@ + + + + + ``` to allow `netdev` users access to the wpa_supplicant which gets started as a service ``` diff --git a/wpa_supplicant/systemd/wpa_supplicant.service.in b/wpa_supplicant/systemd/wpa_supplicant.service.in index 18cbc11..f02bc15 100644 --- a/wpa_supplicant/systemd/wpa_supplicant.service.in +++ b/wpa_supplicant/systemd/wpa_supplicant.service.in @@ -8,8 +8,11 @@ IgnoreOnIsolate=true [Service] Type=dbus BusName=fi.w1.wpa_supplicant1 -ExecStart=@BINDIR@/wpa_supplicant -u -s -O /run/wpa_supplicant +ExecStart=@BINDIR@/wpa_supplicant -u -s -O "DIR=/run/wpa_supplicant GROUP=netdev" ExecReload=/bin/kill -HUP $MAINPID +Group=netdev +RuntimeDirectory=wpa_supplicant +RuntimeDirectoryMode=0750 [Install] WantedBy=multi-user.target ``` If a user is able to escalate to `netdev` - they will be able to interact with the dbus interface. One of the interface `fi.w1.wpa_supplicant1` lets the user create a network interface via `CreateInterface` - See [`wpas_dbus_handler_create_interface`](http://w1.fi/wpa_supplicant/devel/dbus__new__handlers_8h.html#a4c504285e9504dc5508f35646278f867) `ConfigFile` has configurations for a network interface * for loading an opensc engine with `opensc_engine_path`which is a path to a shared object. See [`opensc_engine_path`](https://w1.fi/wpa_supplicant/devel/structwpa__config.html#a791fade4701a30852dbb2b25866ba359) * for loading a PKCS#11 engine with `pkcs11_engine_path` which is a path to a shared object. See [`pkcs11_engine_path`](https://w1.fi/wpa_supplicant/devel/structwpa__config.html#adf38e52ccfe1b621ef5a18b78b1c3a9e) Both these paths don't check for paths - any arbitrary location - leading to arbitrary code execution. Overall any user within the group `netdev` would be able to load arbitrary shared objects - in the context of a process running as root - granting privilege escalation to `root` The process that loads these objects is launched with `/usr/sbin/wpa_supplicant -u -s -O DIR=/run/wpa_supplicant GROUP=netdev ` the trace looks like ``` openat(AT_FDCWD, "/tmp/stage/loadable.so", O_RDONLY|O_CLOEXEC) = 8 read(8, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
[Desktop-packages] [Bug 2073423] Re: thunderbird from mozilla ppa repeatedly replaced by snap
Do you have unattended upgrades enabled? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2073423 Title: thunderbird from mozilla ppa repeatedly replaced by snap Status in thunderbird package in Ubuntu: New Bug description: I have thunderbird installed from the mozilla ppa. For some reason it gets automatically replaced by the thunderbird stub from ubuntu ppa, and the thunderbird snap package is being installed. Happened like 5 times already since I'm on 24.04. I "fix" it by removing the snap package and sudo apt remove -y thunderbird && sudo apt install -y thunderbird /etc/apt/sources.list.d/mozillateam-ubuntu-ppa-noble.sources: Types: deb URIs: https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ Suites: noble Components: main Signed-By: -BEGIN PGP PUBLIC KEY BLOCK- . mI0ESXMwOwEEAL7UP143coSax/7/8UdgD+WjIoIxzqhkTeoGOyw/r2DlRCBPFAOH [...] /etc/apt/preferences.d/mozillateamppa: Package: thunderbird* Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 Please stop replacing the thunderbird package with the snap version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2073423/+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 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I ran into this problem recently while upgrading from Ubuntu 22.04.04 LTS to 24.04, although mine is little more severe. I'm missing /etc/resolv.conf (which typically links to /run/systemd/resolve/stub- resolv.conf) and the systemd-resolved package was not installed or failed to install. Therefore, I have to manually download the package, along with dependencies, and install them on the server. What a mess! -- 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/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 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= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 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/2055012/+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 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind
mutter --version mutter 46.2 I am still experiencing the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2026194 Title: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Committed Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] Clicking on some maximized or fullscreen windows may not respond and the clicks fall through to the window behind. [ Test Plan ] If auto login is not enabled, enable auto login and reboot. The issue can immediately be observed with first party apps such as the software settings GUI where apt sources, update settings, and GPU drivers are located. Have anything open behind it and then try to use it. Dragging the window to another location outside of the bounds of its default size and position makes it completely unusable because it clicks through to the window behind it no matter where you click. If the desktop is behind it, then the window will be usable but entities on the desktop will be clicked if they're located beneath what you clicked on in the window. This behavior is identical for any affected application. [ Where problems could occur ] The bug and the fix appears to be X11-specific, but that can affect Wayland sessions too via Xwayland. The risk here is in the sizing and interactivity of any X11 window. Mistakes in this area can result in other bugs similar to this one where the visual boundaries of a window do not match with its input boundaries. [ Original description ] Initially I thought this was an issue with IntelliJ and filed a bug there: https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind But when I had the same issue with GIMP, I realized it's an Ubuntu or GNOME issue instead. I am assuming this is a gnome-shell problem. Every once in a while, when I maximize or tile (Win+Right) the IntelliJ window, a bottom fraction of the window (somewhere around a quarter) becomes impossible to interact with, with the mouse. Clicking in that lower area will give focus to the thing behind IntelliJ, and if it's a window, raise it to the foreground. if I restore the window so that it is not maximized, the entire window is interactive with the mouse once again. This also happened with GIMP. The attached "Screencast" is a recording. I had to crop it to hide personal information. The attached screenshot shows the state of my screen so you have context, with a bright green color used to replace personal information. For the first 10s of the recording, I simply moused over to show how the cursor changes around a quarter from the bottom of the screen. For the next 10s, I left click, then move, then left click, then move, until focus changes to Sublime, the window behind IntelliJ. For the remainder of the video I show that right-clicking and mousing over works fine on the top three quarters, until I reach the bottom again, and then the right click is sent to Sublime. Ubuntu 23.04 gnome-shell version 44.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 5 12:05:46 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-19 (289 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2026194/+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 2062667] Re: Fails on (and should be removed from) raspi desktop
This impacts all arm64 installs, not just raspberry pi. The MIR for qrtr and protection-domain-mapper [0] was requested late in the Mantic cycle and was only approved by Security since it was promised to only be used for x13s hardware enablement. Hopefully Qualcomm IPC is only enabled for x13s kernels. As noted in the qrtr MIR: > We should be cautious of IPC routers running root permissions. Similar code > has > enabled vendor backdoors [1]. Furthermore, qrtr has nearly no documentation and has no inline code comments [2]. Please remove this from the mantic and noble's ubuntu-meta package. [0] https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug/2038942 [1] https://redmine.replicant.us/projects/replicant/wiki/samsunggalaxybackdoor [2] https://github.com/linux-msm/qrtr -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2063961] [NEW] Microsoft 365 account keeps disconnecting
Public bug reported: When I use the new (24.04) settings and 'Online Accounts' to connect to Microsoft 365, it authenticates, works well for about 5 minutes and then disconnects. I have to remove that account and redo it every time I want to use it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-settings 24.04.3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 19:04:06 2024 InstallationDate: Installed on 2024-04-27 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2063961 Title: Microsoft 365 account keeps disconnecting Status in ubuntu-settings package in Ubuntu: New Bug description: When I use the new (24.04) settings and 'Online Accounts' to connect to Microsoft 365, it authenticates, works well for about 5 minutes and then disconnects. I have to remove that account and redo it every time I want to use it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-settings 24.04.3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 19:04:06 2024 InstallationDate: Installed on 2024-04-27 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2063961/+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
Re: [Desktop-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
I eventually figured out that the control bar for my external speaker had been turned off somehow in the process. I turned it on and it has worked fine since. On Thursday, February 29, 2024 at 07:46:16 AM EST, Pablo Fontoura <2043...@bugs.launchpad.net> wrote: Same thing here. Fresh 23.10 installation and no sound. My USB headset is working properly. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq: owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notification
[Desktop-packages] [Bug 2049229] Re: dbus exception apt permission denied from gnome-language-selector
** Changed in: language-selector (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2049229 Title: dbus exception apt permission denied from gnome-language-selector Status in language-selector package in Ubuntu: Incomplete Bug description: Hi, I am reposting report https://github.com/UbuntuAsahi/ubuntu- asahi/issues/84 Running `sudo gnome-language-selector` leads to: ``` dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.debian.apt: Permission denied ``` This was resolved by reinstalling dbus. Feels like there was a user namespace issue which was resolved. Are in-place dbus re-installs needed? Is apparmor involved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2049229/+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 2049229] [NEW] dbus exception apt permission denied from gnome-language-selector
Public bug reported: Hi, I am reposting report https://github.com/UbuntuAsahi/ubuntu- asahi/issues/84 Running `sudo gnome-language-selector` leads to: ``` dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.debian.apt: Permission denied ``` This was resolved by reinstalling dbus. Feels like there was a user namespace issue which was resolved. Are in- place dbus re-installs needed? Is apparmor involved? ** Affects: language-selector (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2049229 Title: dbus exception apt permission denied from gnome-language-selector Status in language-selector package in Ubuntu: New Bug description: Hi, I am reposting report https://github.com/UbuntuAsahi/ubuntu- asahi/issues/84 Running `sudo gnome-language-selector` leads to: ``` dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.debian.apt: Permission denied ``` This was resolved by reinstalling dbus. Feels like there was a user namespace issue which was resolved. Are in-place dbus re-installs needed? Is apparmor involved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2049229/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Hello all o/ This is intentional. And easy to reverse. The patch for CVE-2023-45866 works as intended and is not a regression. https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/profiles/input?id=25a471a83e02e1effb15d5a488b3f0085eaeb675 If ClassicBondedOnly is not enforced, a nearby attacker can create a HID (like a keyboard and mouse) on the victims PC when bluetooth is discoverable. An HID can be used as a keyloggers or, of course, give direct control of the session. The CVE reporter has discussed this further on https://github.com/skysafe/reblog/tree/main/cve-2023-45866 And a talk and PoC release is forthcoming. Fortunately, it is easy to enable legacy devices by setting `ClassicBondedOnly=false` in `/etc/bluetooth/input.conf`, and then running `systemctl restart bluetooth`. I ver ified that a PS3 controller works well after this :) All other distros *should* be fixing this CVE. I would love it if bloggers in the Linux gaming sphere could raise awareness about this CVE and share how to enable legacy bluetooth device support. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866 ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: bluez (Ubuntu) Assignee: Nishit Majithia (0xnishit) => Mark Esler (eslerm) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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
Re: [Desktop-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
Thanks for your response, Piotr. I tried that, but wasn't given the option for "Play HiFi quality Music". Pro Audio was the only option in the drop down menu. There were some Analog Stereo options, but they were all unplugged and unavailable. Any other suggestions? On Wednesday, November 15, 2023 at 07:20:25 AM EST, Piotr Kowalczyk <2043...@bugs.launchpad.net> wrote: I had same issue. I managed to fix it with pavucontrol (in "configuration" tab I changed Profile to "Play HiFi quality Music" (earlier it was "Pro Audio"). -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: New Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq: owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: New Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To
[Desktop-packages] [Bug 2043524] [NEW] audio disappeared after upgrade to Ubuntu 23.10
Public bug reported: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: New Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+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 2038365] Re: Audio
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2038365 Title: Audio Status in pulseaudio package in Ubuntu: New Bug description: Hi, I edited the daemon.conf file in Kubuntu 22.04, to have the quality of 50hz, in the hz part, float32le in the format, and src-sinc-best-quality. and when I updated it to 23.04 wayland, in the sound tab within the apport-bug, it appeared that pulseaudio was crashed. The sound is very low in distribution, you need to increase the volume a lot to have a loud sound, since kubuntu 22.04. When compared to Windows 11, it needs twice the volume. Example: Windows 11 is at 34%, in Kubuntu it needs to be at 72% or more. I also use the option to reach 150% on the volume bar. Even without changes to daemon.conf, the sound is low. I believe that improvements in hardware acceleration in general (GPU, audio, internet, etc.), across the entire distribution, will improve everything. Leaving hardware acceleration in general as the default, to gain performance. Thank you very much in advance. 👍😄 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+ dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: PID USER ACCESS COMMAND /dev/snd/ controlC0: leandro 1571 F pipewire leandro 1577 F wireplumber /dev/snd/seq: leandro 1571 F pipewire CasperMD5CheckR result: unknown CurrentDesktop: KDE Date: Tuesday, October 3 14:35:56 2023 Installation date: installed on 2023/09/21 (12 days ago) Installation media: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Version amd64 (20230807.1) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE= pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: Command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Updated to lunar on 9/25/2023 (7 days ago) dmi.bios.date: 12/06/2023 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios .version: GGCN55WW dmi.board. asset.tag: NO asset tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis. asset.tag: NO Asset tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis. version: IdeaPad 3 15ITL6 dmi.ec. firmware. release: 1.55 dmi.modalias: dmi:bvnLENOVO: bvrGGCN55WW: bd06/12/ 2023:br1. 55: efr1. 55:svnLENOVO: pn82MD: pvrIdeaPad315IT L6:rvnLENOVO: rnLNVNB161216: rvrSDK0T76466WI N:cvnLENOVO: ct10:cvrIdeaPad 315ITL6: skuLENOVO_ MT_82MD_ BU_idea_ FM_IdeaPad 31 5TIL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_ MT_82MD_ BU_idea_ FM_IdeaPad 3 15ITL6 dmi.product. version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO modified. conffile. .etc.pulse. daemon. conf: [modified] mtime.conffile. .etc.pulse. daemon. conf: 2023-09-21T21 :48: 25.302234 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2038365/+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 2035220] Re: cve-2023-4863
** 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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
New
Status in libwebp package in Ubuntu:
New
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
New
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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 2031406] Re: [MIR] libei
** Tags added: sec-2617 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2031406 Title: [MIR] libei Status in libei package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Availability] - The package libei is already in Ubuntu universe. - The package libei builds for the architectures it is designed to work on. - Link to package https://launchpad.net/ubuntu/+source/libei [Rationale] - The package libei is required in Ubuntu main as a new required dependency for Mutter 45 - The package libei will generally be useful for a large part of our user base - The package libei is a new runtime dependency of package mutter that we already support - There is no other/better way to solve this that is already in main or should go universe->main instead of this. The package libei is required in Ubuntu main no later than August 17 due to Ubuntu 23.10 Feature Freeze. Obviously, that's an unrealistic deadline but the dependency is in mantic-proposed now (some other work is necessary for mutter to migrate out of mantic-proposed). It might be possible to temporarily vendor libei into Mutter. [Security] - No CVEs/security issues in this software in the past (new software, only packaged now in Ubuntu) - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...) libei is a library for emulated input. It can forward physical or logical device input for use by things like GNOME Remote Desktop or sandboxed apps or for fake input for automated actions (like could be done with xdotool). [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libei/ - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libei (not in Debian yet) - Upstream https://gitlab.freedesktop.org/libinput/libei/-/issues [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpad.net/ubuntu/+source/libei/1.0.0-0ubuntu2 Note that the build test failures are temporarily ignored on s390x which is not a supported Ubuntu Desktop architecture, but the issue has been reported upstream and is being worked on: https://gitlab.freedesktop.org/libinput/libei/-/issues/41 - The package does not run an autopkgtest because we haven't written one yet. We may run upstream's build test with our autopkgtest architecture. - Some tests using libei also have been added to Mutter and we do run Mutter's tests both at build time and as installed tests with autopkgtest https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2628/commits [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field - Please link to a recent build log of the package https://launchpad.net/ubuntu/+source/libei/1.0.0-0ubuntu2 - Please attach the full output you have got from `lintian --pedantic` as an extra post to this bug. - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions higher than medium - Packaging and build is easy, link to debian/rules https://salsa.debian.org/jbicha/libei/-/blob/debian-unstable/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be Desktop Packages - Team is not yet, but will subscribe to the package before promotion - This does not use static builds - The team Desktop Packages is aware of the implications of vendored code and (as alerted by the security team) commits to provide updates and backports to the security team for any affected vendored code for the lifetime of the release (including ESM). Currently, the libei packaging includes a vendored copy of munit since munit is not packaged for Debian or Ubuntu yet. This is an optional build-time dependency only used by the test suite and does not add any run-time dependencies. https://github.com/nemequ/munit - This p
[Desktop-packages] [Bug 1993154] Re: Sane genesys 1.0.29 and later drive HP Scanjet 3670 motor beyond limits
Has there been a fix issued to resolve this problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1993154 Title: Sane genesys 1.0.29 and later drive HP Scanjet 3670 motor beyond limits Status in sane-backends package in Ubuntu: Confirmed Bug description: [Impact] When using scan-image with a HP ScanJet 3670 scanner under Xubuntu Jammy 22.04 at 300 dpi or more, the scanner motor is incorrectly driven by the driver: - when scanning an A4 page, the driver attempts to drive motor out of limits at the bottom of the page, resulting in a grinding sound. - the resulting image misses horizontal stripes. - the resulting image has an incorrect aspect ratio (it should be bigger in the vertical dimension). This doesn't happen under Xubuntu Xenial 16.04 (64 bit). This is a serious regression. [Test case] - install Xubuntu Jammy - install sane package - install flatbed scanner HP ScanJet 3670 - run Document Scanner in "Image" mode with default parameters (resulting in a full-size, color, 300 dpi scan) - check scanner noise at bottom of document and resulting image [Analysis] Genesys driver under Jammy is libsane-genesys.so.1.1.1 Genesys driver under Xenial is libsane-genesys.so.1.0.25 This library has been entirely changed between releases 1.0.28 (which is written in C) and 1.0.29 (which has been relocated in its own subdir and is written in C++). When libsane-genesys.so.1.0.25 is copied to Jammy environment and symlink libsane-genesys.so.1 is adjusted to make it point at this file, the problem disappears entirely, the scanner works as expected and the resulting image is fine. When libsane-genesys.so.1.0.29 is copied to Jammy environment and symlink libsane-genesys.so.1 is adjusted to make it point at this file, the problem appears again. Please note that other files haven't been modified and belong to Jammy's version 1.1.1. Therefore, it is likely that something has been broken between versions 1.0.28 and 1.0.29 of libsane-genesys.so, when converting its sources from C to C++. [Details] OS version: Ubuntu 22.04.1 LTS Packages versions: libsane1 1.1.1-5 Log file attached for Jammy case (will attach Xenial case in a later step if possible). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1993154/+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 2011727] Re: Seemingly random crashes of all terminal windows
I will, thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2011727 Title: Seemingly random crashes of all terminal windows Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: Typically this happens when I have 4 windows open. This seems to be a new issue for me, dating back perhaps a couple of weeks. I've used this particular 4 terminal setup for years without issues. When the issue occurs, all terminal windows vanish instantly, and I need to restart all of them. Other applications seem unaffected. Details are: log 1005=> lsb_release -rd Description: Ubuntu 20.04.5 LTS Release: 20.04 log 1006=> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages And in /var/log/syslog I'm seeing the following - (Server ID removed from log): Mar 15 10:16:19 gnome-terminal-server[96577]: VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:19 gnome-terminal-server[96577]: Bail out! VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Main process exited, code=dumped, status=6/ABRT Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Failed with result 'core-dump'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2011727/+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 2011727] Re: Seemingly random crashes of all terminal windows
Hi Egmont - While this issue occurred more often back in March, I haven't experienced this problem recently. I'm now running Ubuntu 20.04.6 instead of 20.04.5 - Perhaps something in this upgrade solved the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2011727 Title: Seemingly random crashes of all terminal windows Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: Typically this happens when I have 4 windows open. This seems to be a new issue for me, dating back perhaps a couple of weeks. I've used this particular 4 terminal setup for years without issues. When the issue occurs, all terminal windows vanish instantly, and I need to restart all of them. Other applications seem unaffected. Details are: log 1005=> lsb_release -rd Description: Ubuntu 20.04.5 LTS Release: 20.04 log 1006=> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages And in /var/log/syslog I'm seeing the following - (Server ID removed from log): Mar 15 10:16:19 gnome-terminal-server[96577]: VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:19 gnome-terminal-server[96577]: Bail out! VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Main process exited, code=dumped, status=6/ABRT Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Failed with result 'core-dump'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2011727/+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 1771880] Re: Seahorse unable to import pkcs12 certificates
Hi, thought I'd chime in here as just ran into the same issue on debian bullseye. Obtained an oh-so-precious "mycert.p12" file and resolved thus: Step 1: a) In Firefox ESR: Settings -> Privacy and Security -> View Certificates button (way down at the bottom). b) "Certificate manager" popup window, "Your Certificates", Import button c) Select mycert.p12 file and it appears in Firefox. Step 2: a) In LibreOffice Write: Tools -> Options -> Security, click "Certificate" button under "Certificate Path" This is where it got interesting - there were two selections there: x firefox:default o firefox:default-esr the top one, "firefox-default" was selected and was not working. Clicking "firefox:default-esr" instead, restart LibreOffice Write... fixed. Another important note: After changing the certificate path, it prompts "LibreOffice Write needs to restart in order to take effect. Do this now?" ...which I answered yes, but it did not actually restart. Initially thinking it didn't work. But upon manual restart, it *did* work. Maybe this approach is better since it takes Seahorse out of the loop. Would also be curious to know if Jammy is fixed and/or above works? I'm going to upgrade one of the three debian bullseye systems I did this on successfully, to debian bookworm right now. If anything breaks, I'll be sure to post that here. Hope this helps someone out there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in seahorse: New Status in gnome-keyring package in Ubuntu: Triaged Status in seahorse package in Ubuntu: Triaged Status in gnome-keyring package in Fedora: New Status in seahorse package in Fedora: Unknown Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+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 2023463] [NEW] Cannot remove items from side panel
Public bug reported: Only an annoying bug I cannot remove the attached from my menu on the side panel. Other items are removed ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 14:22:20 2023 DistUpgraded: 2023-05-30 14:55:36,989 DEBUG /openCache(), new cache size 74014 DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:100c] InstallationDate: Installed on 2023-02-08 (123 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire F5-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=d5663606-7967-4f64-9bf3-a8843f95c2b6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-05-30 (11 days ago) dmi.bios.date: 05/25/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:br0.0:efr2.70:svnAcer:pnAspireF5-572:pvrV1.18:rvnAcer:rnZoro_SL:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireF5-572_100C_1.18: dmi.product.family: SKL dmi.product.name: Aspire F5-572 dmi.product.sku: Aspire F5-572_100C_1.18 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 kinetic 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/2023463 Title: Cannot remove items from side panel Status in xorg package in Ubuntu: New Bug description: Only an annoying bug I cannot remove the attached from my menu on the side panel. Other items are removed ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 14:22:20 2023 DistUpgraded: 2023-05-30 14:55:36,989 DEBUG /openCache(), new cache size 74014 DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:100c] InstallationDate: Installed on 2023-02-08 (123 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire F5-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=d5663606-7967-4f64-9bf3-a8843f95c2b6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-05-30 (11 days ago) dmi.bios.date: 05/25/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:br0.0:efr2.70:svnAcer:pnAspireF5-572:pvrV1.18:rvnAcer:rnZoro_SL:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireF5-572_100C_1.18: dmi.product.family: SKL dmi.product.name: Aspire F5-572 dmi.product.sku: Aspire F5-572_100C_1.18 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compi
[Desktop-packages] [Bug 2019498] Re: Unable to connect to Google in GCC
Here is the output: $ journalctl -f May 19 21:05:13 nitro gnome-control-c[5879]: Error showing account: Child process exited with code 1 May 19 21:06:07 nitro org.gnome.Settings.desktop[5921]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialogue was dismissed May 19 21:06:07 nitro xdg-desktop-por[2266]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info May 19 21:06:19 nitro kernel: WebKitWebProces[6157]: segfault at 5564481e0ac8 ip 5564481e0ac8 sp 7ffc22016728 error 14 likely on CPU 2 (core 1, socket 0) May 19 21:06:19 nitro kernel: Code: Unable to access opcode bytes at 0x5564481e0a9e. May 19 21:07:39 nitro systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... May 19 21:07:39 nitro systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. May 19 21:07:39 nitro systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. May 19 21:07:39 nitro systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. May 19 21:07:41 nitro gnome-control-c[5879]: Error showing account: Child process exited with code 1 May 19 21:07:49 nitro org.gnome.Settings.desktop[6127]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialogue was dismissed May 19 21:07:50 nitro xdg-desktop-por[2266]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info May 19 21:08:01 nitro kernel: WebKitWebProces[6296]: segfault at 55ce66a0a8da ip 55ce66a0a8da sp 7ffce52facf8 error 14 likely on CPU 0 (core 0, socket 0) May 19 21:08:01 nitro kernel: Code: Unable to access opcode bytes at 0x55ce66a0a8b0. -- 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/2019498 Title: Unable to connect to Google in GCC Status in gnome-control-center package in Ubuntu: Incomplete Bug description: At installation of Ubuntu 23.04, and subsequently, when trying to use Gnome Control Center to connect my Google account in Online Accounts, I am able to enter my email address, but then the screen freezes in the transition to the screen where I'd enter my password. This happens every time. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 14 12:44:51 2023 InstallationDate: Installed on 2023-05-14 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+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
Re: [Desktop-packages] [Bug 2019498] Re: Unable to connect to Google in GCC
Hi, I'm away with work for the rest of this week, so I'll do this on Saturday for you. On Tue, 16 May 2023 at 10:59, Sebastien Bacher <2019...@bugs.launchpad.net> wrote: > Thank you for your bug report. Could you do > $ journalctl -f > then trigger the bug and see if any error is printed in the journal log? > > ** Changed in: gnome-control-center (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2019498 > > Title: > Unable to connect to Google in GCC > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > At installation of Ubuntu 23.04, and subsequently, when trying to use > Gnome Control Center to connect my Google account in Online Accounts, > I am able to enter my email address, but then the screen freezes in > the transition to the screen where I'd enter my password. > > This happens every time. > > ProblemType: Bug > DistroRelease: Ubuntu 23.04 > Package: gnome-control-center 1:44.0-1ubuntu5 > ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 > Uname: Linux 6.2.0-20-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.26.1-0ubuntu2 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Sun May 14 12:44:51 2023 > InstallationDate: Installed on 2023-05-14 (0 days ago) > InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 > (20230417) > SourcePackage: gnome-control-center > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center; > component=main; status=Incomplete; importance=Undecided; assignee=None; > Launchpad-Bug-Tags: amd64 apport-bug lunar > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: juglugs1974 seb128 > Launchpad-Bug-Reporter: Mark Smith (juglugs1974) > Launchpad-Bug-Modifier: Sebastien Bacher (seb128) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: juglugs1974 > > -- 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/2019498 Title: Unable to connect to Google in GCC Status in gnome-control-center package in Ubuntu: Incomplete Bug description: At installation of Ubuntu 23.04, and subsequently, when trying to use Gnome Control Center to connect my Google account in Online Accounts, I am able to enter my email address, but then the screen freezes in the transition to the screen where I'd enter my password. This happens every time. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 14 12:44:51 2023 InstallationDate: Installed on 2023-05-14 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+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 2019498] [NEW] Unable to connect to Google in GCC
Public bug reported: At installation of Ubuntu 23.04, and subsequently, when trying to use Gnome Control Center to connect my Google account in Online Accounts, I am able to enter my email address, but then the screen freezes in the transition to the screen where I'd enter my password. This happens every time. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 14 12:44:51 2023 InstallationDate: Installed on 2023-05-14 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "Screenshot of frozen online accounts screen" https://bugs.launchpad.net/bugs/2019498/+attachment/5672961/+files/20230514OnlineAccountsBug.jpg -- 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/2019498 Title: Unable to connect to Google in GCC Status in gnome-control-center package in Ubuntu: New Bug description: At installation of Ubuntu 23.04, and subsequently, when trying to use Gnome Control Center to connect my Google account in Online Accounts, I am able to enter my email address, but then the screen freezes in the transition to the screen where I'd enter my password. This happens every time. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 14 12:44:51 2023 InstallationDate: Installed on 2023-05-14 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+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 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
thnx, this helped me resolve problem https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/comments/38 #38 -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+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 2015273] [NEW] Errors in syslog cant update stage views actor because it needs an allocation
Public bug reported: switch from wayland to xorg and error started. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 08:37:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-18 (17 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2015273 Title: Errors in syslog cant update stage views actor because it needs an allocation Status in gnome-shell package in Ubuntu: New Bug description: switch from wayland to xorg and error started. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 08:37:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-18 (17 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015273/+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 2003259] Re: [MIR] libcupsfilters libppd cups-browsed
Since libppd MIR is no longer required per comment 37 and MM discussion, setting status to invalid and removing Security Team. ** Changed in: libppd (Ubuntu) Status: New => Invalid ** Changed in: libppd (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-browsed package in Ubuntu: Fix Released Status in libcupsfilters package in Ubuntu: Fix Released Status in libppd package in Ubuntu: Invalid Bug description: == Summary = Source packages to be promoted to Main: - libcupsfilters - libppd - cups-browsed Binary packages to be promoted to Main: - libcupsfilters2 - libcupsfilters2-common - libppd-dev - libppd2 - libppd2-common - ppdc No source packages and no binary packages which are in Main should get demoted to Universe. == Overview Due to a major change in the printing architecture [1] the cups-filters upstream project at OpenPrinting got split into 5 components [2]: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed [1] https://openprinting.github.io/current/#the-new-architecture-for-printing-and-scanning [2] https://openprinting.github.io/cups-filters-Second-Generation-First-Beta-Release/ To reflect this in the Debian/Ubuntu packaging also the cups-filters source package there is getting split, rendering 3 new source packages (+) and therefore we need this MIR: Binaries: Source BEFORE (1.x) Source AFTER (2.x) - cups-browsed cups-filters cups-browsed + cups-filters cups-filters cups-filters cups-filters-core-drivers cups-filters cups-filters libcupsfilters-dev cups-filters libcupsfilters + libcupsfilters1 X cups-filters Replaced by libcupsfilters2 * libcupsfilters2 + libcupsfilters + (NEW) libcupsfilters2-common +libcupsfilters + (NEW) libfontembed-dev X cups-filters REMOVED ** libfontembed X cups-filters REMOVED ** libppd-dev +libppd + (NEW) *** libppd2 + libppd + (NEW) *** libppd2-common +libppd + (NEW) *** ppdc + libppd + (NEW) *** * : libcupsfilters has new API generation/SONAME 1 -> 2 ** : libfontembed code folded into libcupsfilters, API removed, no other package is using it. ***: libppd contains all PPD-supporting code of CUPS, as in CUPS 3.x this code will get removed. libppd is for legacy-retro-fitting of classic CUPS drivers with PPD files. Code comes from CUPS source: cups/ppd*.[ch], scheduler/cups-driverd.cxx, ppdc/* X: Binary package getting REMOVED from Lunar +: Source or binary package to be promoted to Main via this MIR The purposes of the new generation's binary packages are principally the same as before: - cups-browsed: Daemon to auto-create queues for network printers and to form printer clusters - cups-filters: Print data format conversion filters and printer communication backends for CUPS 2.x - Complete set - cups-filters-core-drivers: Print data format conversion filters and printer communication backends for CUPS 2.x - Essential ones for minimum configurations, like mobile or IoT - libcupsfilters-dev: C Header files for libcupsfilters2 - libcupsfilters2: Shared library containing common code for print data conversion filters, printer drivers, printer model identification and distinction, PDF file manipulation, PDF font embedding, color space conversion, ... - libcupsfilters2-common: Architecture-indpendent auxiliary files - libppd2-dev: C Header files for libppd2 - libppd2: Shared library for support of PPD files, parsing the files, converting PPD options into IPP attributes, managing collections of PPDs, finding PPD for given printer, generating PPDs from CUPS' *.drv files - libppd2-common: Architecture-indpendent auxiliary files - ppdc: Command line tools to generate PPD files from *.drv files (only for development and debugging, or to keep scripts using them working, not end-user-facing) --> ALL THESE BINARY PACKAGES MUST BE IN MAIM, SO THE FOLLOWING BINARY PAC
[Desktop-packages] [Bug 2011727] Re: Seemingly random crashes of all terminal windows
Ok, thanks for the update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2011727 Title: Seemingly random crashes of all terminal windows Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: Typically this happens when I have 4 windows open. This seems to be a new issue for me, dating back perhaps a couple of weeks. I've used this particular 4 terminal setup for years without issues. When the issue occurs, all terminal windows vanish instantly, and I need to restart all of them. Other applications seem unaffected. Details are: log 1005=> lsb_release -rd Description: Ubuntu 20.04.5 LTS Release: 20.04 log 1006=> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages And in /var/log/syslog I'm seeing the following - (Server ID removed from log): Mar 15 10:16:19 gnome-terminal-server[96577]: VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:19 gnome-terminal-server[96577]: Bail out! VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Main process exited, code=dumped, status=6/ABRT Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Failed with result 'core-dump'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2011727/+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
Re: [Desktop-packages] [Bug 2011313] Re: gnome-control-center crashes after launch
I can confirm that this issue is now resolved On Thu, 16 Mar 2023 at 12:15, Mark Smith <2011...@bugs.launchpad.net> wrote: > Awesome! Thank you for your help on this. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2011313 > > Title: > gnome-control-center crashes after launch > > Status in gnome-control-center package in Ubuntu: > Fix Released > > Bug description: > I had successfully opened settings and used it to change some of the > desktop options (size of the docker icons, etc.). > Then I clicked on "Users" and ubuntu-settings crashed. > Since then, I am unable to open ubuntu-settings - it will open and flash > up on the screen before crashing. > This has continued even after restarting the machine a few times. > > ubuntu-settings version: 23.04.2 500 > > ProblemType: Bug > DistroRelease: Ubuntu 23.04 > Package: ubuntu-settings 23.04.2 > ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 > Uname: Linux 6.1.0-16-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.26.0-0ubuntu2 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Sat Mar 11 18:33:16 2023 > InstallationDate: Installed on 2023-03-11 (0 days ago) > InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) > PackageArchitecture: all > ProcEnviron: >LANG=en_US.UTF-8 >PATH=(custom, no user) >SHELL=/bin/bash >TERM=xterm-256color >XDG_RUNTIME_DIR= > SourcePackage: ubuntu-settings > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center; > component=main; status=Fix Released; importance=High; assignee= > jeremy.bi...@canonical.com; > Launchpad-Bug-Tags: amd64 apport-bug lunar > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: fthx gunnarhj juglugs1974 starkus > Launchpad-Bug-Reporter: Mark Smith (juglugs1974) > Launchpad-Bug-Modifier: Mark Smith (juglugs1974) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: juglugs1974 > > -- 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/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: Fix Released Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 2011313] Re: gnome-control-center crashes after launch
Awesome! Thank you for your help on this. -- 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/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: Fix Released Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 2011727] [NEW] Seemingly random crashes of all terminal windows
Public bug reported: Typically this happens when I have 4 windows open. This seems to be a new issue for me, dating back perhaps a couple of weeks. I've used this particular 4 terminal setup for years without issues. When the issue occurs, all terminal windows vanish instantly, and I need to restart all of them. Other applications seem unaffected. Details are: log 1005=> lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 log 1006=> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages And in /var/log/syslog I'm seeing the following - (Server ID removed from log): Mar 15 10:16:19 gnome-terminal-server[96577]: VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:19 gnome-terminal-server[96577]: Bail out! VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Main process exited, code=dumped, status=6/ABRT Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Failed with result 'core-dump'. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2011727 Title: Seemingly random crashes of all terminal windows Status in gnome-terminal package in Ubuntu: New Bug description: Typically this happens when I have 4 windows open. This seems to be a new issue for me, dating back perhaps a couple of weeks. I've used this particular 4 terminal setup for years without issues. When the issue occurs, all terminal windows vanish instantly, and I need to restart all of them. Other applications seem unaffected. Details are: log 1005=> lsb_release -rd Description: Ubuntu 20.04.5 LTS Release: 20.04 log 1006=> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages And in /var/log/syslog I'm seeing the following - (Server ID removed from log): Mar 15 10:16:19 gnome-terminal-server[96577]: VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:19 gnome-terminal-server[96577]: Bail out! VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Main process exited, code=dumped, status=6/ABRT Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Failed with result 'core-dump'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2011727/+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 2011313] Re: gnome-control-center crashes after launch
Ahaha so ubuntu-settings was rolled out into Lunar overnight NOT gnome-control-settings. I had forgotten that I had originally tagged the wrong app - in fact, I'm not going to have to go and look up the difference between them :) So - false alarm - It's not ready yet :) -- 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/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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
Re: [Desktop-packages] [Bug 2011313] Re: gnome-control-center crashes after launch
Yeah, I think that it's not worth fixing in the alpha version. Do you know when 1:44~rc will be merged? Thank you for your help with this bug! It is much appreciated :) On Sun, 12 Mar 2023 at 22:00, Gunnar Hjalmarsson <2011...@bugs.launchpad.net> wrote: > Yeah.. That "Couldn't get locale for language: (null)" warning comes > from a patch which I wrote initially, and first I feared that the > segfault is related to that. But it's not. I committed a fix which will > get rid of the warning in this situation: > > https://salsa.debian.org/gnome-team/gnome-control- > center/-/commit/53e9a9a2 > > But it still segfaults. For some reason it fails to fetch the user data > properly. > > My thought is that since the problem seems to be gone in g-c-c 1:44~rc, > it's not worth it to figure out why exactly the alpha version crashes. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2011313 > > Title: > gnome-control-center crashes after launch > > Status in gnome-control-center package in Ubuntu: > In Progress > > Bug description: > I had successfully opened settings and used it to change some of the > desktop options (size of the docker icons, etc.). > Then I clicked on "Users" and ubuntu-settings crashed. > Since then, I am unable to open ubuntu-settings - it will open and flash > up on the screen before crashing. > This has continued even after restarting the machine a few times. > > ubuntu-settings version: 23.04.2 500 > > ProblemType: Bug > DistroRelease: Ubuntu 23.04 > Package: ubuntu-settings 23.04.2 > ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 > Uname: Linux 6.1.0-16-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.26.0-0ubuntu2 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Sat Mar 11 18:33:16 2023 > InstallationDate: Installed on 2023-03-11 (0 days ago) > InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) > PackageArchitecture: all > ProcEnviron: >LANG=en_US.UTF-8 >PATH=(custom, no user) >SHELL=/bin/bash >TERM=xterm-256color >XDG_RUNTIME_DIR= > SourcePackage: ubuntu-settings > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center; > component=main; status=In Progress; importance=High; assignee= > jeremy.bi...@canonical.com; > Launchpad-Bug-Tags: amd64 apport-bug lunar > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: gunnarhj juglugs1974 starkus > Launchpad-Bug-Reporter: Mark Smith (juglugs1974) > Launchpad-Bug-Modifier: Gunnar Hjalmarsson (gunnarhj) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: juglugs1974 > > -- 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/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 2011313] Re: gnome-control-center crashes after launch
That command: gsettings reset org.gnome.ControlCenter last-panel Doesn't work for me - I get: No such schema “org.gnome.ControlCenter” -- 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/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 2011313] Re: gnome-control-center crashes after launch
And thanks for the tip ref running it without going to "Users" :) -- 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/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 2011313] Re: gnome-control-center crashes after launch
As a data point, when I run gnome-control-center from the terminal I get a "Segmentation Error" and core dump. -- 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/2011313 Title: gnome-control-center crashes after launch Status in gnome-control-center package in Ubuntu: In Progress Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 2011313] [NEW] Ubuntu-Settings crashes after launch
Public bug reported: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: Ubuntu-Settings crashes after launch Status in ubuntu-settings package in Ubuntu: New Bug description: I had successfully opened settings and used it to change some of the desktop options (size of the docker icons, etc.). Then I clicked on "Users" and ubuntu-settings crashed. Since then, I am unable to open ubuntu-settings - it will open and flash up on the screen before crashing. This has continued even after restarting the machine a few times. ubuntu-settings version: 23.04.2 500 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-settings 23.04.2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 18:33:16 2023 InstallationDate: Installed on 2023-03-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2011313/+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 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
I'm having similar issues. Following what Fabio mentioned, I think I had a firewall issue but disabling the firewall was not enough, I needed to restart the wifi after disabling the firewall. I guess that is the sequence which addresses the problem for Fabio too. -- 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/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1892559] Re: [MIR] ccid opensc pcsc-lite
Desktop no longer has engineering goals to support smart cards. Foundations team might. Security Team is blocked until there is a mandate, an owning team, hardware funding, and possibly engineering support to resolve https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930530 Unassigning Security Team. ** Changed in: ccid (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: opensc (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: pcsc-lite (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: In Progress Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
[Desktop-packages] [Bug 1995135] Re: WiFi captive portals stopped working after Kinetic upgrade
*** This bug is a duplicate of bug 1995134 *** https://bugs.launchpad.net/bugs/1995134 ** This bug has been marked a duplicate of bug 1995134 WiFi captive portals stopped working after Kinetic upgrade -- 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/1995135 Title: WiFi captive portals stopped working after Kinetic upgrade Status in gnome-shell package in Ubuntu: New Bug description: After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995135/+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 1995134] [NEW] WiFi captive portals stopped working after Kinetic upgrade
Public bug reported: After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session -- 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/1995134 Title: WiFi captive portals stopped working after Kinetic upgrade Status in gnome-shell package in Ubuntu: New Bug description: After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995134/+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 1995135] [NEW] WiFi captive portals stopped working after Kinetic upgrade
Public bug reported: After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session -- 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/1995135 Title: WiFi captive portals stopped working after Kinetic upgrade Status in gnome-shell package in Ubuntu: New Bug description: After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995135/+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 1927948] Re: Windows switch monitor after resuming from sleep
Just to add on to my last comment... something is really broken for my configuration - after ten minutes of trying to get all three monitors to wake up and play ball with the screen display settings windows and it only ever enabling two out of the three (sometimes 1 & 3, sometimes 1 & 2 and somethings 2 & 3), I gave up and rebooted and now it's fine. Think will just have to disable the monitors from sleeping when the screen is locked... Happy to investigate if given direction on what to look at on my system. -- 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/1927948 Title: Windows switch monitor after resuming from sleep Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: What I expect: Window layout/positioning is identical after resume from sleep. What I observe: After resume from sleep, windows appear on a different monitor than before. I found this possibly relevant GNOME bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 10 13:40:28 2021 InstallationDate: Installed on 2019-12-02 (524 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1927948/+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 1927948] Re: Windows switch monitor after resuming from sleep
I believe I too am affected by this problem. I have three monitors attached to my system all on the same GTX950 (GM206) adapter and after waking up from sleep the active windows move around and most annoyingly the system often struggles to 'find' all three monitors again - even though it shoes them in the display settings dialog. Sometimes it will only see two. Sometimes finds them all but mirrors two. Meaning I have to turn monitors on and off until they play ball which can take some time for the system to recognise them all again. The system works fine if I reboot it but on sleep it goes wrong. Doing a xrandr shows this: xrandr Screen 0: minimum 8 x 8, current 7680 x 2160, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 596mm x 335mm 3840x2160 30.00*+ 29.9725.0023.98 2560x1600 59.97 2560x1440 59.95 1920x1080 60.0059.9450.0029.9723.9860.0050.04 1680x1050 59.95 1440x900 59.89 1440x576 50.00 1440x480 59.94 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-0 connected 3840x2160+3840+0 (normal left inverted right x axis y axis) 596mm x 335mm 3840x2160 29.98*+ 2560x1600 59.97 2560x1440 59.95 1920x1080 60.0059.9450.00 1680x1050 59.95 1440x900 59.89 1440x576 50.00 1440x480 59.94 1280x1024 60.02 1280x960 60.00 1280x800 59.81 1280x720 60.0059.9450.00 1024x768 60.00 800x600 60.3256.25 720x576 50.00 720x480 59.94 640x480 59.94 640x350 70.10 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected (normal left inverted right x axis y axis) 3840x2160 60.00 + 30.00 2560x1600 59.97 2560x1440 59.95 1920x1080 60.0059.9450.00 1680x1050 59.95 1440x900 59.89 1440x576 50.00 1440x480 59.94 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) So the system can see all monitors and I can select all three under the Screen Display settings but setting them up and applying the changes doesn't result in them all turning off as expected until you've done it numerous times... If I work out the pattern I will update this. Am running Ubuntu 22.04.1 LTS and Gnome 42.4. Happy to run tests or help replicate. -- 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/1927948 Title: Windows switch monitor after resuming from sleep Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: What I expect: Window layout/positioning is identical after resume from sleep. What I observe: After resume from sleep, windows appear on a different monitor than before. I found this possibly relevant GNOME bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 10 13:40:28 2021 InstallationDate: Installed on 2019-12-02 (524 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1927948/+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 590837] Re: Thunderbird Memory Leak (AMD64)
This bug seems to be back on Ubuntu 20.04 version 1:91.11.0+build2-0ubuntu0.20.04.1. It eats up all of my swap then hangs with an oom error. Unfortunately, running it updates the profile so I can't just drop back to the previous version and continue (without making new profile(s)). Hrm, it works fine on a laptop (Intel) but not on my desktop (AMD). I don't know if processor architecture is relevant or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/590837 Title: Thunderbird Memory Leak (AMD64) Status in thunderbird package in Ubuntu: Expired Bug description: Binary package hint: thunderbird Thunderbird leaks memory, fast, one or two megabytes per second. Every type top updates, VIRT, has increased. Here is a example of what can be observed using top: PID %MEM RES SWAP VIRT SHR DATA S CODE TIME nFLT nDRT COMMAND 28559 67.91.3g 617m 1979m 28m 1.5g 5 15m 14:04 18 0 thunderbird-bin Problem is *always* reproducible, just launch thunderbird. Using -safe-mode does not help. I'm connecting to two IMAP mailboxes (one served by courier-imap, another served by MS Exchange). "Enable Global Search and Indexer" is *unset* "Keep messages for this account on this computer" is *unset* for both accounts (setting does not help). ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.4+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Jun 7 17:30:20 2010 ExecutablePath: /usr/lib/thunderbird-3.0.4/thunderbird-bin InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/csh SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/590837/+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 590837] Re: Thunderbird Memory Leak (AMD64)
This bug seems to be back on Ubuntu 20.04 version 1:91.11.0+build2-0ubuntu0.20.04.1. Unfortunately, running it updates the profile so I can't just drop back to the previous version and continue (without making new profile(s)). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/590837 Title: Thunderbird Memory Leak (AMD64) Status in thunderbird package in Ubuntu: Expired Bug description: Binary package hint: thunderbird Thunderbird leaks memory, fast, one or two megabytes per second. Every type top updates, VIRT, has increased. Here is a example of what can be observed using top: PID %MEM RES SWAP VIRT SHR DATA S CODE TIME nFLT nDRT COMMAND 28559 67.91.3g 617m 1979m 28m 1.5g 5 15m 14:04 18 0 thunderbird-bin Problem is *always* reproducible, just launch thunderbird. Using -safe-mode does not help. I'm connecting to two IMAP mailboxes (one served by courier-imap, another served by MS Exchange). "Enable Global Search and Indexer" is *unset* "Keep messages for this account on this computer" is *unset* for both accounts (setting does not help). ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.4+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Jun 7 17:30:20 2010 ExecutablePath: /usr/lib/thunderbird-3.0.4/thunderbird-bin InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/csh SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/590837/+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 1981623] Re: Save As Dialog Box does not allow filename change
** Attachment added: "Text entry triggers find function - not rename"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1981623/+attachment/5602933/+files/Screenshot%20at%202022-07-13%2014-38-39.png
--
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/1981623
Title:
Save As Dialog Box does not allow filename change
Status in gnome-shell package in Ubuntu:
New
Bug description:
Ubuntu Mate 22.04 - Save-as dialog boxes (chrome, firefox, etc.) open
as expected, but do not permit changing the filename. Text entry
triggers the find function as opposed to file rename.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed Jul 13 14:33:18 2022
DisplayManager: lightdm
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'draggable-border-width' b'20'
InstallationDate: Installed on 2022-05-21 (52 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1981623/+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 1981623] Re: Save As Dialog Box does not allow filename change
Similar to this, but slightly different:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968887
--
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/1981623
Title:
Save As Dialog Box does not allow filename change
Status in gnome-shell package in Ubuntu:
New
Bug description:
Ubuntu Mate 22.04 - Save-as dialog boxes (chrome, firefox, etc.) open
as expected, but do not permit changing the filename. Text entry
triggers the find function as opposed to file rename.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed Jul 13 14:33:18 2022
DisplayManager: lightdm
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'draggable-border-width' b'20'
InstallationDate: Installed on 2022-05-21 (52 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1981623/+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 1981623] [NEW] Save As Dialog Box does not allow filename change
Public bug reported:
Ubuntu Mate 22.04 - Save-as dialog boxes (chrome, firefox, etc.) open as
expected, but do not permit changing the filename. Text entry triggers
the find function as opposed to file rename.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed Jul 13 14:33:18 2022
DisplayManager: lightdm
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'draggable-border-width' b'20'
InstallationDate: Installed on 2022-05-21 (52 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy third-party-packages
--
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/1981623
Title:
Save As Dialog Box does not allow filename change
Status in gnome-shell package in Ubuntu:
New
Bug description:
Ubuntu Mate 22.04 - Save-as dialog boxes (chrome, firefox, etc.) open
as expected, but do not permit changing the filename. Text entry
triggers the find function as opposed to file rename.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed Jul 13 14:33:18 2022
DisplayManager: lightdm
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'draggable-border-width' b'20'
InstallationDate: Installed on 2022-05-21 (52 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1981623/+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 1981623] Re: Save As Dialog Box does not allow filename change
** Attachment added: "initial file dialog"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1981623/+attachment/5602932/+files/Screenshot%20at%202022-07-13%2014-38-49.png
--
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/1981623
Title:
Save As Dialog Box does not allow filename change
Status in gnome-shell package in Ubuntu:
New
Bug description:
Ubuntu Mate 22.04 - Save-as dialog boxes (chrome, firefox, etc.) open
as expected, but do not permit changing the filename. Text entry
triggers the find function as opposed to file rename.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed Jul 13 14:33:18 2022
DisplayManager: lightdm
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'draggable-border-width' b'20'
InstallationDate: Installed on 2022-05-21 (52 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1981623/+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 1976498] Re: nautilus causes gvfsd-trash 'Too many files open' error and fills syslog
Not sure this was actually a bug. I reinstalled my system anyway so the issue went away. Now marked as invalid ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1976498 Title: nautilus causes gvfsd-trash 'Too many files open' error and fills syslog Status in nautilus package in Ubuntu: Invalid Bug description: My syslog is filled (to >30GB) regularly with these messages. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: (org.gnome.Nautilus:156898): GVFS-WARNING **: 11:41:49.618: The peer-to-peer connection failed: Unable to create socket: Too many open files. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: daemon: Error creating server at address unix:path=/run/user/1000/gvfsd/socket-z3fCgn9o: Unable to create socket: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: GNOME nautilus 42.1.1 Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 mar
[Desktop-packages] [Bug 1978640] Re: FFTW_PRESERVE_INPUT does not always preserve input
** Changed in: fftw3 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fftw3 in Ubuntu.
https://bugs.launchpad.net/bugs/1978640
Title:
FFTW_PRESERVE_INPUT does not always preserve input
Status in fftw3 package in Ubuntu:
Invalid
Bug description:
libfftw3-dev:
Installed: (none)
Candidate: 3.3.8-2ubuntu8
Version table:
3.3.8-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
program to reproduce bug on Ubuntu 20.04 or 22.04 follows below
expected: success (no assert) because the input was preserved
observed: assert because the input was not preserved
```test_fftw_preserve.cc
#include
#include
#include
#include "assert.h"
int main()
{
typedef std::complex cpx;
int nfft = 125;
fftwf_plan plan = fftwf_plan_many_dft(1,&nfft,1,
NULL, NULL,1,nfft,
NULL, NULL,1,nfft,
FFTW_FORWARD,
FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED);
std::vector in(nfft,cpx(1,2));
std::vector in_copied(in);
std::vector out(nfft);
fftwf_execute_dft(plan,
reinterpret_cast(in.data()),reinterpret_cast(out.data()));
assert(in == in_copied);
fftwf_destroy_plan(plan);
return 0;
}
```
To run:
```
$ g++ test_fftw_preserve.cc -lfftw3f && ./a.out
a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied'
failed.
Aborted (core dumped)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1978640] Re: FFTW_PRESERVE_INPUT does not always preserve input
I just realized that feeding NULL to the planner is not a supported
mode. I withdraw the bug report.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fftw3 in Ubuntu.
https://bugs.launchpad.net/bugs/1978640
Title:
FFTW_PRESERVE_INPUT does not always preserve input
Status in fftw3 package in Ubuntu:
New
Bug description:
libfftw3-dev:
Installed: (none)
Candidate: 3.3.8-2ubuntu8
Version table:
3.3.8-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
program to reproduce bug on Ubuntu 20.04 or 22.04 follows below
expected: success (no assert) because the input was preserved
observed: assert because the input was not preserved
```test_fftw_preserve.cc
#include
#include
#include
#include "assert.h"
int main()
{
typedef std::complex cpx;
int nfft = 125;
fftwf_plan plan = fftwf_plan_many_dft(1,&nfft,1,
NULL, NULL,1,nfft,
NULL, NULL,1,nfft,
FFTW_FORWARD,
FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED);
std::vector in(nfft,cpx(1,2));
std::vector in_copied(in);
std::vector out(nfft);
fftwf_execute_dft(plan,
reinterpret_cast(in.data()),reinterpret_cast(out.data()));
assert(in == in_copied);
fftwf_destroy_plan(plan);
return 0;
}
```
To run:
```
$ g++ test_fftw_preserve.cc -lfftw3f && ./a.out
a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied'
failed.
Aborted (core dumped)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1978640] Re: FFTW_PRESERVE_INPUT does not always preserve input
Additional details:
If `nfft` is changed from 125 to 128, the bug is not shown.
If `fftwf_plan_many_dft` is called with buffer pointers, the bug is not
shown.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fftw3 in Ubuntu.
https://bugs.launchpad.net/bugs/1978640
Title:
FFTW_PRESERVE_INPUT does not always preserve input
Status in fftw3 package in Ubuntu:
New
Bug description:
libfftw3-dev:
Installed: (none)
Candidate: 3.3.8-2ubuntu8
Version table:
3.3.8-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
program to reproduce bug on Ubuntu 20.04 or 22.04 follows below
expected: success (no assert) because the input was preserved
observed: assert because the input was not preserved
```test_fftw_preserve.cc
#include
#include
#include
#include "assert.h"
int main()
{
typedef std::complex cpx;
int nfft = 125;
fftwf_plan plan = fftwf_plan_many_dft(1,&nfft,1,
NULL, NULL,1,nfft,
NULL, NULL,1,nfft,
FFTW_FORWARD,
FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED);
std::vector in(nfft,cpx(1,2));
std::vector in_copied(in);
std::vector out(nfft);
fftwf_execute_dft(plan,
reinterpret_cast(in.data()),reinterpret_cast(out.data()));
assert(in == in_copied);
fftwf_destroy_plan(plan);
return 0;
}
```
To run:
```
$ g++ test_fftw_preserve.cc -lfftw3f && ./a.out
a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied'
failed.
Aborted (core dumped)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1978640] [NEW] FFTW_PRESERVE_INPUT does not always preserve input
Public bug reported:
libfftw3-dev:
Installed: (none)
Candidate: 3.3.8-2ubuntu8
Version table:
3.3.8-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
program to reproduce bug on Ubuntu 20.04 or 22.04 follows below
expected: success (no assert) because the input was preserved
observed: assert because the input was not preserved
```test_fftw_preserve.cc
#include
#include
#include
#include "assert.h"
int main()
{
typedef std::complex cpx;
int nfft = 125;
fftwf_plan plan = fftwf_plan_many_dft(1,&nfft,1,
NULL, NULL,1,nfft,
NULL, NULL,1,nfft,
FFTW_FORWARD,
FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED);
std::vector in(nfft,cpx(1,2));
std::vector in_copied(in);
std::vector out(nfft);
fftwf_execute_dft(plan,
reinterpret_cast(in.data()),reinterpret_cast(out.data()));
assert(in == in_copied);
fftwf_destroy_plan(plan);
return 0;
}
```
To run:
```
$ g++ test_fftw_preserve.cc -lfftw3f && ./a.out
a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied' failed.
Aborted (core dumped)
```
** Affects: fftw3 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "reproduction example"
https://bugs.launchpad.net/bugs/1978640/+attachment/5597250/+files/test_fftw_preserve.cc
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fftw3 in Ubuntu.
https://bugs.launchpad.net/bugs/1978640
Title:
FFTW_PRESERVE_INPUT does not always preserve input
Status in fftw3 package in Ubuntu:
New
Bug description:
libfftw3-dev:
Installed: (none)
Candidate: 3.3.8-2ubuntu8
Version table:
3.3.8-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
program to reproduce bug on Ubuntu 20.04 or 22.04 follows below
expected: success (no assert) because the input was preserved
observed: assert because the input was not preserved
```test_fftw_preserve.cc
#include
#include
#include
#include "assert.h"
int main()
{
typedef std::complex cpx;
int nfft = 125;
fftwf_plan plan = fftwf_plan_many_dft(1,&nfft,1,
NULL, NULL,1,nfft,
NULL, NULL,1,nfft,
FFTW_FORWARD,
FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED);
std::vector in(nfft,cpx(1,2));
std::vector in_copied(in);
std::vector out(nfft);
fftwf_execute_dft(plan,
reinterpret_cast(in.data()),reinterpret_cast(out.data()));
assert(in == in_copied);
fftwf_destroy_plan(plan);
return 0;
}
```
To run:
```
$ g++ test_fftw_preserve.cc -lfftw3f && ./a.out
a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied'
failed.
Aborted (core dumped)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1976498] Re: DING causes gvfsd 'Too many files open' error and fills syslog
Changed from ding to nautilus after reading about nautilus gvfsd-trash bug ** Package changed: ding (Ubuntu) => nautilus (Ubuntu) ** Summary changed: - DING causes gvfsd 'Too many files open' error and fills syslog + nautilus causes gvfsd-trash 'Too many files open' error and fills syslog ** Description changed: - My syslog is filled (to >30GB) regularly with these messages. I seem to - have this thing called DING going on, which maybe causing it? + My syslog is filled (to >30GB) regularly with these messages. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: (org.gnome.Nautilus:156898): GVFS-WARNING **: 11:41:49.618: The peer-to-peer connection failed: Unable to create socket: Too many open files. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: daemon: Error creating server at address unix:path=/run/user/1000/gvfsd/socket-z3fCgn9o: Unable to create socket: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: GNOME nautilus 42.1.1 Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:
[Desktop-packages] [Bug 1975487] [NEW] zsys not installed during Kinetic ISO install with ZFS option
Public bug reported: After following the instructions at: http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results on the 20220523 daily build of Kinetic, I used the command zsysctl show and was met with the message: ~$ zsysctl show Command 'zsysctl' not found, but can be installed with: sudo apt install zsys ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 23 12:33:24 2022 InstallationDate: Installed on 2022-05-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220522) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1975487/+attachment/5592259/+files/Screenshot%20from%202022-05-23%2012-39-43.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1975487 Title: zsys not installed during Kinetic ISO install with ZFS option Status in zsys package in Ubuntu: New Bug description: After following the instructions at: http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results on the 20220523 daily build of Kinetic, I used the command zsysctl show and was met with the message: ~$ zsysctl show Command 'zsysctl' not found, but can be installed with: sudo apt install zsys ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 23 12:33:24 2022 InstallationDate: Installed on 2022-05-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220522) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1975487/+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 1968987] [NEW] Login hangs after entering password
Public bug reported: After a recent update Ubuntu 22.04 stalled and screen went black after entering password. After process of elimination it seems that the culprit is the update to gnome-remote-desktop. 1. Description: Ubuntu Jammy Jellyfish (development branch) Release:22.04 2. gnome-remote-desktop 42.0-2 3. I expected Ubuntu 22.04 to open after entering password at login. 4. Instead the login screen would freeze, then go black. Using a previous snapshot provided by zsys and synaptic package manager, I iterated on the "upgradable" updates until I had all the updates installed except the one. Whenever gnome-remote-desktop is installed, the login process fails. So, I deleted gnome-remote-desktop and all seems fine. This ubuntu is installed in a VM using KVM/QEMU ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop (not installed) ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 14 01:52:40 2022 InstallationDate: Installed on 2022-04-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1968987 Title: Login hangs after entering password Status in gnome-remote-desktop package in Ubuntu: New Bug description: After a recent update Ubuntu 22.04 stalled and screen went black after entering password. After process of elimination it seems that the culprit is the update to gnome-remote-desktop. 1. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2. gnome-remote-desktop 42.0-2 3. I expected Ubuntu 22.04 to open after entering password at login. 4. Instead the login screen would freeze, then go black. Using a previous snapshot provided by zsys and synaptic package manager, I iterated on the "upgradable" updates until I had all the updates installed except the one. Whenever gnome-remote-desktop is installed, the login process fails. So, I deleted gnome-remote-desktop and all seems fine. This ubuntu is installed in a VM using KVM/QEMU ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop (not installed) ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 14 01:52:40 2022 InstallationDate: Installed on 2022-04-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1968987/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
still seeing Apr 9 15:30:54 drafting-table /usr/libexec/gdm-x-session[355145]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found in an install which is "jammy daily iso from a week or two back with daily dist upgrades", under i3; $ dpkg -l gdm3 x11-common i3-wm Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii gdm3 42.0-1ubuntu2 amd64GNOME Display Manager ii i3-wm 4.20.1-1amd64improved dynamic tiling window manager ii x11-common 1:7.7+23ubuntu2 all X Window System (X.Org) infrastructure -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1967883] Re: [snap] Firefox Nightly Application Icon missing from "Show Applications" screen
No, It was a straight install with me present at the desktop computer all the way through - no switching or even screen locking. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967883 Title: [snap] Firefox Nightly Application Icon missing from "Show Applications" screen Status in firefox package in Ubuntu: New Bug description: From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox (nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967883/+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 1967883] Re: Application Icons missing from "Show Applications" screen
** Attachment added: "Screenshot from 2022-04-05 14-48-11.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577339/+files/Screenshot%20from%202022-04-05%2014-48-11.png -- 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/1967883 Title: Application Icons missing from "Show Applications" screen Status in gnome-shell package in Ubuntu: New Bug description: From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox (nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+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 1967883] Re: Application Icons missing from "Show Applications" screen
** Attachment added: "Screenshot from 2022-04-05 14-48-11.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577338/+files/Screenshot%20from%202022-04-05%2014-48-11.png -- 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/1967883 Title: Application Icons missing from "Show Applications" screen Status in gnome-shell package in Ubuntu: New Bug description: From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox (nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+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 1967883] [NEW] Application Icons missing from "Show Applications" screen
Public bug reported: >From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox >(nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2022-04-05 14-47-30.png" https://bugs.launchpad.net/bugs/1967883/+attachment/5577331/+files/Screenshot%20from%202022-04-05%2014-47-30.png -- 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/1967883 Title: Application Icons missing from "Show Applications" screen Status in gnome-shell package in Ubuntu: New Bug description: From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox (nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+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 1965466] [NEW] [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all
Public bug reported: auto-generated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdb2244 F pulseaudio /dev/snd/controlC1: mdb2244 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 02:51:06 2022 InstallationDate: Installed on 2018-12-10 (1193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdb2244 F pulseaudio /dev/snd/controlC1: mdb2244 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: No sound at all Title: [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RME1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH77Dx dmi.board.vendor: MEDION dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862: dmi.product.family: Erazer dmi.product.name: DEFENDER P10 dmi.product.sku: ML-210009 30028862 dmi.product.version: Not Applicable dmi.sys.vendor: MEDION ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1965466 Title: [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: auto-generated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdb2244 F pulseaudio /dev/snd/controlC1: mdb2244 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 02:51:06 2022 InstallationDate: Installed on 2018-12-10 (1193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdb2244 F pulseaudio /dev/snd/controlC1: mdb2244 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: No sound at all Title: [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RME1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH77Dx dmi.board.vendor: MEDION dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862: dmi.product.family: Erazer dmi.product.name: DEFENDER P10 dmi.product.sku: ML-210009 30028862 dmi.product.version: Not Applicable dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965466/+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 1962624] Re: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected
*** This bug is a duplicate of bug 1955758 *** https://bugs.launchpad.net/bugs/1955758 might affect bugs: 1955758 1962495 1962623 1962624 1962626 1962630 1962633 I will add this text to all open bugs. affected parts: tracker-miner-fs-3 totem gvfsd-mtp udisksd background information: - installed 18.04 lts - dist-upgraded to 20.04 lts - back up before sending hardware for repair, got replacement hardware (with default rubbish) - restore on replaced hardware with -- modified filesystem (btrfs, dont remember previously used fs) and -- full-disk encryption (multiple luks2 partitions instead of home-only) - noticed that integrating grub-2.06 correctly (building package etc) would be too much effort - downgraded luks-headers from luks2 to luks1 to make it compatible with grub used in 20.04 - added grub-setup script to include cryptmount grub module etc. - got btrfs kernel warnings regularly - dist-upgraded to 22.04 lts (beta, late January) - still btrfs kernel warnings regularly [- many updates since, as to be expected.] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1962624 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in udisks2 package in Ubuntu: New Bug description: automatically created data, did not look into it. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.chromium.rules Date: Thu Feb 24 23:58:25 2022 ExecutablePath: /usr/libexec/udisks2/udisksd InstallationDate: Installed on 2018-12-10 (1177 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MEDION DEFENDER P10 ProcCmdline: /usr/libexec/udisks2/udisksd ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/mapper/newroot Signal: 6 SourcePackage: udisks2 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7febbba0db8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7febbba105d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7febbba46c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7febbba46c80 , p=0x5627404144c0, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 08/29/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RME1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH77Dx dmi.board.vendor: MEDION dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862: dmi.product.family: Erazer dmi.product.name: DEFENDER P10 dmi.product.sku: ML-210009 30028862 dmi.product.version: Not Applicable dmi.sys.vendor: MEDION separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1962624/+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 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::
With gnome-shell 3.36.9-0ubuntu0.20.04.2 I too see this with only the built-in "Desktop Icons", "Ubuntu AppIndicators", "Ubuntu Dock" extensions and no further extensions in ~/.local/share/gnome-shell/ $ journalctl -S -1hour | grep 'Jan 07 08:19:35' | sort | uniq -c Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. 22 Jan 07 08:19:35 LAP125300 gnome-shell[3286]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 4314 Jan 07 08:19:35 LAP125300 gnome-shell[3286]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. 22 Jan 07 08:19:35 LAP125300 gnome-shell[3286]: The offending callback was paint(), a vfunc. 4291 Jan 07 08:19:35 LAP125300 gnome-shell[3286]: The offending callback was SourceFunc(). 22 Jan 07 08:19:35 LAP125300 gnome-shell[3286]: The offending signal was paint on Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock 0x5581d33fc7d0. -- 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/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Issue is explained in detail here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 16 18:56:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-01 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+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 1954911] [NEW] Xorg freeze
Public bug reported: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] MachineType: Sony Corporation VGN-FW351J ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-12-17 (363 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2050Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW351J:pvrC60184W1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-FW351J dmi.product.sku: N/A dmi.product.version: C60184W1 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze 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/1954911 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu
[Desktop-packages] [Bug 1952515] Re: QA Test Ubuntu 22.04 Gnome-shell Crashed
Unable to reproduce in VB environment
--
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/1952515
Title:
QA Test Ubuntu 22.04 Gnome-shell Crashed
Status in gnome-shell package in Ubuntu:
New
Bug description:
QA Test Ubuntu 22.04 Gnome-shell Crashed.
Apport could not send data.
Reason: Invalid core dump /tmp/apport_core_k657r8ti is truncated.
Daily Build 20211127
Crash happened while testing Ubuntu Live Test.
Opened terminal manually started Apport for this bug report.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 27 16:00:24 2021
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.5'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211127)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 40.5-1ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952515/+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 1881712] Re: gnome-software says connection is metered while is not
Same issue on 21.04 -- 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/1881712 Title: gnome-software says connection is metered while is not Status in gnome-software package in Ubuntu: Confirmed Bug description: I open gnome-software and i see a message 'automatic updates paused' for my connection is metered but my connection is NOT metered. see attached screenshot. corrado@corrado-HP-x4-gg-0525ebook-PC:~$ inxi -Fx System:Host: corrado-HP-x4-gg-0525ebook-PC Kernel: 5.4.0-26-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.2 Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100600087 serial: Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: UEFI: Insyde v: F.36 date: 12/18/2014 Battery: ID-1: BAT1 charge: 10.2 Wh condition: 16.4/16.4 Wh (100%) model: 13-42 OA03031 status: Charging CPU: Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156 Speed: 1696 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1697 2: 1696 3: 1696 4: 1697 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Suyin type: USB driver: uvcvideo bus ID: 1-1.5:3 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 20.0.7 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.4.0-26-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 08:00.0 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 port: 3000 bus ID: 09:00.0 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 689.33 GiB used: 6.76 GiB (1.0%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB ID-2: /dev/sdb vendor: SanDisk model: SSD PLUS 240GB size: 223.57 GiB Partition: ID-1: / size: 31.25 GiB used: 6.75 GiB (21.6%) fs: ext4 dev: /dev/sdb5 Swap: ID-1: swap-1 type: partition size: 4.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 39.0 C mobo: 39.0 C Fan Speeds (RPM): N/A Info: Processes: 236 Uptime: 49m Memory: 3.78 GiB used: 1.39 GiB (36.7%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.16 inxi: 3.1.00 corrado@corrado-HP-x4-gg-0525ebook-PC:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 08:57:28 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2020-05-26 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200525) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-21 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200420) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 Package: gnome-software 3.36.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1881712/+subscriptions -- Mailing list: https://
[Desktop-packages] [Bug 1291427] Re: Baobab won't start: Failed to register: Timeout was reached
It happens to me when one of the file systems is busy (USB) or the network mount unreachable. For reference, it also happens when specifying a known non-busy directory on the command-line, like /home/mark. xdiskusage fails the same way with unavailable filesystems but works fine when specifying the directory. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1291427 Title: Baobab won't start: Failed to register: Timeout was reached Status in baobab package in Ubuntu: Confirmed Bug description: Baobab just won't start on 14.04 for me. alan@wopr:~$ baobab Failed to register: Timeout was reached alan@wopr:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: baobab 3.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 12 14:58:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-02 (799 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120102) SourcePackage: baobab UpgradeStatus: Upgraded to trusty on 2013-12-09 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1291427/+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 1931813] [NEW] Alienware Area-51m / Realtek ALC215 multi-function headphone jacks configured incorrectly
Public bug reported: The built in laptop speakers / mic work ok There are two 3.5mm jack ports which end up configured one as a headphone socket and one as a microphone, whereas in Windows they are multi-function ports that support headsets. Adding `options snd-hda-intel index=0 model=dell-headset-multi` to /etc/modprobe.d/alsa-base.conf makes the port normally configured as headphones work (inserting anything shows a screen asking to know what was inserted -- headphones or headset) but the port normally configured as a microphone stays that way. I have done a bit of poking about but couldn't figure out how to make the pin configs the same (most of the documentation for compiling ALSA seems out of date). I ran RtHDDump on Windows and attached the output from that in case it's useful. Thanks! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 7732 F pulseaudio /dev/snd/pcmC0D0c: mark 7732 F...m pulseaudio /dev/snd/pcmC0D0p: mark 7732 F...m pulseaudio /dev/snd/controlC1: mark 7732 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 20:23:27 2021 InstallationDate: Installed on 2021-05-23 (21 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [Alienware Area-51m, Realtek ALC215, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 3/21/2019 dmi.bios.release: 1.3 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.2 dmi.board.name: Alienware Area-51m dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.2:bd3/21/2019:br1.3:svnAlienware:pnAlienwareArea-51m:pvr1.3.2:rvnAlienware:rnAlienwareArea-51m:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Area-51m dmi.product.sku: 08C4 dmi.product.version: 1.3.2 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-06-13T16:28:28.400989 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/bugs/1931813/+attachment/5504408/+files/RtHDDump.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1931813 Title: Alienware Area-51m / Realtek ALC215 multi-function headphone jacks configured incorrectly Status in alsa-driver package in Ubuntu: New Bug description: The built in laptop speakers / mic work ok There are two 3.5mm jack ports which end up configured one as a headphone socket and one as a microphone, whereas in Windows they are multi-function ports that support headsets. Adding `options snd-hda-intel index=0 model=dell-headset-multi` to /etc/modprobe.d/alsa-base.conf makes the port normally configured as headphones work (inserting anything shows a screen asking to know what was inserted -- headphones or headset) but the port normally configured as a microphone stays that way. I have done a bit of poking about but couldn't figure out how to make the pin configs the same (most of the documentation for compiling ALSA seems out of date). I ran RtHDDump on Windows and attached the output from that in case it's useful. Thanks! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 7732 F pulseaudio /dev/snd/pcmC0D0c: mark 7732 F...m pulseaudio /dev/snd/pcmC0D0p: mark 7732 F...m pulseaudio /dev/snd/controlC1: mark 7732 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 20:23:27 2021 InstallationDate: Installed on 2021-05-23 (21 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording te
Re: [Desktop-packages] [Bug 1926009] Re: [amdgpu] Incomplete display of text
You are right, I had forgotten about the PPA and hadn't paid close enough attention when posting the bug originally. Please accept my apologies. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1926009 Title: [amdgpu] Incomplete display of text Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1926009/+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 1926009] Re: Incomplete display of text
Ok I have been able to rollback the xserver-xorg-video-amdgpu package from 19.1.0+git2104271106.aedbf47~f~mesarc0 to 19.1.0-1, and can confirm that the issue didn't reappear. ** Attachment added: "Output of apt-cache showpkg xserver-xorg-video-amdgpu" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+attachment/5494229/+files/amdgpu-avail-versions.log -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+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
Re: [Desktop-packages] [Bug 1926009] Re: Incomplete display of text
Yes, of course leave this with me and I'll report back later. -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+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 1926009] Re: Incomplete display of text
I am happy to report that this issue looks to have been resolved. The roll back took a bit of time to do, and I am still not sure that I did it fully correctly. However it did the trick. I also note that there were some subsequent updates to both the Mesa libraries, and xserver-xorg-video-amdgpu driver, amongst which was a fix. Thank you, Sebastien, for all your help. it is very much appreciated. Many thanks, Mark. -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+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
Re: [Desktop-packages] [Bug 1926009] Re: Incomplete display of text
Certainly. I might not be able get to it for a day or two, but will let you know how I get on. Many thanks, Mark. On 27 April 2021 10:43:34 BST, Sebastien Bacher <1926...@bugs.launchpad.net> wrote: >Could you try rolling back those updates see if resolves your issue? > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1926009 > >Title: > Incomplete display of text > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+subscriptions -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+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 1926009] Re: Incomplete display of text
The issue appears to have started around the 21st April, and apart from a couple of browser upgrades some misc packages, there appear to have been a number of Mesa related upgrades (see attached). ** Attachment added: "Grepped output from /var/log/dpkg.loc" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+attachment/5492530/+files/upgradelog -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+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 1926009] Re: Incomplete display of text
> Could you add your 'journalctl -b 0' log after getting the issue? See attached. ** Attachment added: "Output of 'journalctl -b 0'" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+attachment/5492531/+files/requested-journal-logs -- 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926009/+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 1926009] [NEW] Incomplete display of text
Public bug reported: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/1926009 Title: Incomplete display of text Status in xorg package in Ubuntu: New Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.1
[Desktop-packages] [Bug 1924679] [NEW] Intel Nuc install. Icons go blank randomly, nothing opens. Need to remove power to reboot.
Public bug reported: Hi Guys, I've installed Ubuntu on my Intel Nuc, and have had issues with the OS randomly freezing. Usually the icons go blank, apps close, and I'm unable to open any applications. The only way to get the system back is to take the power out of the NUC and put it back in to form a reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:53:53 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-09 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1924679 Title: Intel Nuc install. Icons go blank randomly, nothing opens. Need to remove power to reboot. Status in gnome-shell package in Ubuntu: New Bug description: Hi Guys, I've installed Ubuntu on my Intel Nuc, and have had issues with the OS randomly freezing. Usually the icons go blank, apps close, and I'm unable to open any applications. The only way to get the system back is to take the power out of the NUC and put it back in to form a reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:53:53 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-09 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1924679/+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 1923333] [NEW] Benq G610HDA not being detected
Public bug reported: My monitor Benq G610HDA is not being detected by Ubuntu. Good VGI Cable, still Unknown display ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 13:13:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 460.39, 5.8.0-48-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-45-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:1a7d] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:1a7d] InstallationDate: Installed on 2021-02-08 (61 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. X455LB ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=def1bb03-4353-441e-b107-29aaf5b72e17 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LB.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX455LB.205:bd08/03/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnX455LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X455LB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.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:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution 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/192 Title: Benq G610HDA not being detected Status in xorg package in Ubuntu: New Bug description: My monitor Benq G610HDA is not being detected by Ubuntu. Good VGI Cable, still Unknown display ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend
[Desktop-packages] [Bug 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10
*** This bug is a duplicate of bug 1897965 *** https://bugs.launchpad.net/bugs/1897965 ** This bug has been marked a duplicate of bug 1897965 PulseAudio doesn't work when pipewire is installed (ie. KDE) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494
[Desktop-packages] [Bug 385335] Re: gnome-font-viewer default text not visible in all fonts
I found the example strings in: https://github.com/GNOME/pango/blob/master/pango/pango-language-sample- table.h and the string selection here: https://github.com/GNOME/gnome-font- viewer/blob/827b338762d45535718be637a838a75f8c218f7d/src/sushi-font- widget.c#L315 This means that it should be possible to manipulate the language though environment variables, but I've been unsuccessful in doing so because of my lack of knowledge. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/385335 Title: gnome-font-viewer default text not visible in all fonts Status in GNOME Font Viewer: New Status in gnome-font-viewer package in Ubuntu: Triaged Bug description: Binary package hint: gnome-control-center At this moment, gnome-font-viewer uses "The quick brown fox jumps over the lazy dog" as the sample text for all fonts. This however is an awful implementation for CJK-oriented fonts, because for these fonts, what the user would like to see are the Chinese characters/Japanese kanas/Korean hanguls part of the content, not Roman alphabets. In some CJK fonts that have their contents exclusively on Chinese characters/Japanese kanas/Korean hanguls, "The quick brown fox jumps over the lazy dog" sample text simply appears as a bunch of black blocks (see attached picture). This is nowhere helpful for the user to preview the font's content. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-font-viewer/+bug/385335/+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 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10
If that workaround has fixed the problem (I'm waiting a while to make sure) do I mark it as a duplicate of that bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7
[Desktop-packages] [Bug 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: li
[Desktop-packages] [Bug 1915870] Re: gnome session not starting (segfault with r300_dri.so)
Now I can confirm, applying the patch mentioned above brings my PC back to normal. Short summary for everyone else who might read this bug report: Download and save patch as patch.diff and run: sudo apt-build install --patch patch.diff libgl1-mesa-dri -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome session not starting (segfault with r300_dri.so) Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+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 1915870] Re: gnome session not starting (segfault with r300_dri.so)
Hi, I agree, the fix seems to be this https://gitlab.freedesktop.org/mesa/mesa/-/commit/58e43594fc457eaaf1b1e01e48948959a82080bc But it's not yet available. So can anyone point me to an explanation how to build such a package from source and install it? I'll be able to patch it myself. And another question. Won't ubuntu-bug do the same as apport-cli -c? It also created a bug report (linked in my previous message). But it's somehow marked as private, so I'm not sure everyone can see it. Thanks all, for your help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome session not starting (segfault with r300_dri.so) Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+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 1916463] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV
** 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-session in Ubuntu. https://bugs.launchpad.net/bugs/1916463 Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV Status in gnome-session package in Ubuntu: New Bug description: This is a follow up of Bug #1915870, now created with apport-cli -c. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-session-bin 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Feb 22 10:37:00 2021 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/gnome-session-check-accelerated-gl-helper InstallationDate: Installed on 2020-11-15 (98 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcCmdline: /usr/libexec/gnome-session-check-accelerated-gl-helper --print-renderer SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A mtime.conffile..etc.apport.crashdb.conf: 2021-02-22T10:49:13.153121 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1916463/+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 1915870] Re: gnome session not starting
I used apport-cli -c to create Bug #1916463 as the suggested workaround did not really work out. I will add the other requested files there. Maybe then this bug can be closed as being a duplicate. -- 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/1915870 Title: gnome session not starting Status in gnome-shell package in Ubuntu: Incomplete Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915870/+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 1914601] Re: GUI apps do not start from the link created
Hi,
How do you test?
- Which version of WSL you are using?
- What is the output of `echo $DISPLAY` if you open a terminal from the link
created by wslu?
- What is the content of `/etc/resolv.conf`?
I found where the issue is. On "wslu v3.2.1-1; wslusc v40", in
`/usr/share/wslu/wslusc-helper.sh` if I comment the following code, the
shortcuts start working:
# if ( eval "$ipconfig_exec" | grep -n -m 1 "Default Gateway.*: [0-9a-z]" |
cut -d : -f 1 ) >/dev/null; then
#set +H
#wsl2_d_tmp="$(eval "$ipconfig_exec" | grep -n -m 1 "Default Gateway.*:
[0-9a-z]" | cut -d : -f 1)"
#wsl2_d_tmp="$(eval "$ipconfig_exec" | sed $(( wsl2_d_tmp - 4 ))','$((
wsl2_d_tmp + 0 ))'!d' | grep IPv4 | cut -d : -f 2 | sed -e "s|\s||g" -e
"s|\r||g")"
#set -H
#export DISPLAY=${wsl2_d_tmp}:0.0
# else
wsl2_d_tmp="$(grep nameserver /etc/resolv.conf | awk '{print $2}')"
export DISPLAY=${wsl2_d_tmp}:0
# fi
This means the script is not setting DISPLAY variable properly and no
matter which X11 server you are using, it won't connect since on WSL2 it
is not in the local network. Here is what the script does without
commenting:
$ echo $DISPLAY
172.24.224.1:0 # this is what the IP should be
$ unset DISPLAY
/usr/share/wslu$ . ./wslusc-helper.sh
$ echo $DISPLAY
192.168.0.16:0.0# this is what the scripts sets, this would work on WSL1
where host and WSL are on the same network, but on WSL2 it won't work
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wslu in Ubuntu.
https://bugs.launchpad.net/bugs/1914601
Title:
GUI apps do not start from the link created
Status in wslu package in Ubuntu:
Incomplete
Bug description:
Description:Ubuntu 20.04.2 LTS
Release:20.04
wslu:
Installed: 2.3.6-0ubuntu2~20.04.0
Candidate: 2.3.6-0ubuntu2~20.04.0
Version table:
*** 2.3.6-0ubuntu2~20.04.0 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.3.6-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
C:\Users\username\Desktop>wsl -l -v
NAME STATE VERSION
* Ubuntu-20.04 Running 2
$ wslusc --version
wslu v2.3.6; wslusc v37
$ wslusc terminator
[info] Create shortcut terminator.lnk successful
C:\Users\username\Desktop>terminator.lnk
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
You need to run terminator in an X environment. Make sure $DISPLAY is
properly set
$ wslusc --gui terminator
[info] Create shortcut terminator.lnk successful
C:\Users\username\Desktop>terminator.lnk
Looks like DISPLAY propery is not set correctly by the underlying
script:
$ pwd
/usr/share/wslu
$ export DISPLAY=SHOULD_BE_SET
$ . wsl-integration.sh
$ echo $DISPLAY
SHOULD_BE_SET
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1915870] [NEW] gnome session not starting
Public bug reported: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description:Ubuntu 20.10 Release:20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_libexec_gnome-session-check-accelerated-gl-helper.126.crash" https://bugs.launchpad.net/bugs/1915870/+attachment/5464194/+files/_usr_libexec_gnome-session-check-accelerated-gl-helper.126.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome session not starting Status in gnome-session package in Ubuntu: New Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1915870/+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 1914601] Re: GUI apps do not start from the link created
$ wslsys WSL Version: 2 Locale: en_GB Release Install Date: Tue Jul 21 18:00:49 CEST 2020 Branch: vb_release Build: 19042 Full Build: 19041.1.amd64fre.vb_release.191206-1406 Display Scaling: 1 Windows Theme: light Windows Uptime: 1d 0h 25m WSL Uptime: 0d 8h 25m WSL Release: Ubuntu 20.04.2 LTS WSL Kernel: Linux 5.4.72-microsoft-standard-WSL2 Packages Count: 1449 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: Confirmed Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1914601] Re: GUI apps do not start from the link created
Hi, I am using Xming 7.7.0.60 on Windows 10 Pro 20H2 version 19042.746 build with WSL2. Even after a while the GUI won't open. If I run `terminator` command from wsl terminal it opens fine on Xming, so I don't think it's X server issue. And before `apt update` yesterday, those desktop shortcuts worked just fine. My assumption, is that `wslu v3.2.1-1; wslusc v40` assumes you have WSL1 and sets DISPLAY to a local IP which would not work in WSL2 since it's not local network anymore. And from what I've seen `wslu v2.3.6; wslusc v37` version doesn't set DISPLAY propery at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: New Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1914601] Re: GUI apps do not start from the link created
Hi, I've tested the version from PPA: $ wslusc --version wslu v3.2.1-1; wslusc v40 $ wslusc --gui terminator [warn] wsl-term.ico not found in Windows directory. Copying right now... [info] wsl-term.ico copied. Located at "/mnt/c/Users/username/wslu". [warn] wsl-gui.ico not found in Windows directory. Copying right now... [info] wsl-gui.ico copied. Located at "/mnt/c/Users/username/wslu". [info] Create shortcut terminator.lnk successful And the shortcut doesn't work and I think I know why. DISPLAY option is not set properly by the script: $ echo $DISPLAY 172.18.96.1:0 # this should be the correct one $ unset DISPLAY $ . wslusc-helper.sh $ echo $DISPLAY 192.168.0.16:0.0 # this is what is set by the script The correct way would be setting DISPLAY from /etc/reslv.conf: $ cat /etc/resolv.conf # This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf: # [network] # generateResolvConf = false nameserver 172.18.96.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: New Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1914601] Re: GUI apps do not start from the link created
Also, if I open the desktop shortcut properties I see that target is truncated: C:\Windows\System32\wscript.exe C:\\Users\\username\wslu\runHidden.vbs "C:\\Users\\username\\AppData\\Local\\Microsoft\\WindowsApps\\CanonicalGroupLimited.Ubuntu20.04onWindows_79rhkp1fndgsc\\ubuntu2004.exe" run "cd ~; . /usr/share/wslu/wsl-integration.s Could be that the target is too long when `--gui` flag is used? Without `--gui` flag, the target is much shorter: C:\Users\username\AppData\Local\Microsoft\WindowsApps\CanonicalGroupLimited.Ubuntu20.04onWindows_79rhkp1fndgsc\ubuntu2004.exe run "cd ~; terminator" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: New Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1914601] Re: GUI apps do not start from the link created
Hi, As you can see from bug description, I also tried --gui flag which also did not produce a working link. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: New Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1914601] [NEW] GUI apps do not start from the link created
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET ** Affects: wslu (Ubuntu) Importance: Undecided Status: New ** Summary changed: - GUI apps do not work + GUI apps do not work from the link created ** Summary changed: - GUI apps do not work from the link created + GUI apps do not start from the link created -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: New Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions
Will this be available in 20.04? Or is the recommendation for everyone to upgrade mutter manually? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1899206 Title: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Committed Status in mutter source package in Hirsute: Fix Released Bug description: [ Impact ] Mutter 3.36.2 breaks custom input settings [ Test case ] - Set custom settings using gnome-control-center (set custom Delay and Speed in Settings > Accessibility > Repeat Keys) or gnome-tweaks (under Additional Layout options) - Unplug / replug the input device or suspend / resume - Input device settings should be preserved [ Regression potential ] Devices added or removed may be not noticed by gnome-shell. --- I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which seems to have been introduced within the past couple of weeks. I have a couple custom keyboard settings configured in Tweaktool "Additional Layout Options". These settings work great. I have a USB keyboard plugged into the machine. If I have the keyboard plugged in when I start my Gnome session, the customized keyboard layout options are correctly applied to the USB keyboard. If I unplug and reconnect the keyboard, the keyboard does will _NOT_ have the customized keyboard settings. If I restart my Gnome session (using Alt-F2 -> "r"), the customized settings are applied to the keyboard. I think this behavior is something new. Before, I was able to unplug/reconnect my keyboard and it would apply my customized keyboard settings on reconnect. Is there anything I can do to force the application of the custom keyboard tweaks on USB keyboard reconnect? Is anyone else able to reproduce this? I don't have any other machines with Ubuntu 20.04.1 to test with. Thanks! (This is also cross-posted at askubuntu: https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional- layout-options-not-working) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Just happened to me for the first time, on 20.04, "Alt+F2" then entering "r" worked for me, thanks to all who suggested it -- 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/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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
