[Touch-packages] [Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
try boot kernel 5.15.0-23-generic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS Status in wpa package in Ubuntu: Confirmed Bug description: Using the current beta of Jammy, I no longer have stable WiFi after April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There is a chance it may also be related to network-manager going from 1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to wpasupplicant (see below) Wifi is stable often, but also often it fails to load webpages intermittently or fails to download the packages using apt for example, so it's not browser related. Example output of journalctl -xe -u wpasupplicant: Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1 Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with fc:34:97:23:4c:3c Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-94 txrate=27 Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=-95 txrate=27 Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying completed with fc:34:97:23:4c:3c [GTK=CCMP] Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-95 txrate=243000 Additional info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy wpasupplicant wpasupplicant: Geïnstalleerd: 2:2.10-6 Kandidaat: 2:2.10-6 Versietabel: *** 2:2.10-6 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 8 21:28:12 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-12 (27 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311)
[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
Confirmed issue still persists with Ubuntu 22.04 and Nginx 1.18.0 with letsencrypt certbot renewal checks. [3861805.583095] nginx[254589]: segfault at 10 ip 7fadfd915593 sp 7ffcca68cc30 error 4 in libperl.so.5.30.0[7fadfd8ad000+166000] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault Status in perl package in Ubuntu: Confirmed Bug description: [Steps to reproduce] 1) launch a focal container $ lxc launch images:ubuntu/focal focal-1897561 2) enter the container $ lxc shell focal-1897561 3) install libnginx-mod-http-perl # apt-get install -y nginx-core libnginx-mod-http-perl 4) check nginx journal # journalctl -fu nginx & 5) reload nginx 2-3 times # systemctl reload nginx Eventually you will see this from the journal: Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web server and a reverse proxy server. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, code=dumped, status=11/SEGV Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 'core-dump'. [Workaround] If libnginx-mod-http-perl is not needed, purging it and restarting nginx sidesteps the problem. [Original bug description] Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in libperl.so.5.30.0[7fbf321a5000+166000] Symptom: Nginx terminates --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Package: perl 5.30.0-9build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959508] Re: enable BMFF support in exiv2
** Changed in: exiv2 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1959508 Title: enable BMFF support in exiv2 Status in exiv2 package in Ubuntu: Confirmed Status in exiv2 package in Debian: Fix Released Bug description: On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that Ubuntu 22.04 currently includes exiv2 0.27.3 Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file format has been the Canon camera-raw file format since mid 2018, and is probably one of the most common raw image file formats today. Applications such as darktable, amongst others, use exiv2 to extract image metadata, thumbnails and previews, and can only open CR3 files when linked with exiv2 0.27.5 or later. Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On to enable *.CR3 support. Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled included in Ubuntu 22.04? Note that a similar request exists for Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788 References https://github.com/exiv2/exiv2#2-19 https://github.com/Exiv2/exiv2/issues/1229 https://github.com/darktable-org/darktable/pull/10332 https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918 https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968448] [NEW] package libxslt1.1:i386 1.1.34-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: Hi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxslt1.1:i386 1.1.34-4 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 9 11:46:28 2022 DuplicateSignature: package:libxslt1.1:i386:1.1.34-4 Setting up mesa-utils (8.4.0-1build1) ... dpkg: error processing package libxslt1.1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: libxslt Title: package libxslt1.1:i386 1.1.34-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxslt (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package focal i386 need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxslt in Ubuntu. https://bugs.launchpad.net/bugs/1968448 Title: package libxslt1.1:i386 1.1.34-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxslt package in Ubuntu: New Bug description: Hi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxslt1.1:i386 1.1.34-4 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 9 11:46:28 2022 DuplicateSignature: package:libxslt1.1:i386:1.1.34-4 Setting up mesa-utils (8.4.0-1build1) ... dpkg: error processing package libxslt1.1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: libxslt Title: package libxslt1.1:i386 1.1.34-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1968448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
Minor update: when the WiFi is being flaky, I often get see 100% CPU usage for ksoftirqd, but not always. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS Status in wpa package in Ubuntu: Confirmed Bug description: Using the current beta of Jammy, I no longer have stable WiFi after April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There is a chance it may also be related to network-manager going from 1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to wpasupplicant (see below) Wifi is stable often, but also often it fails to load webpages intermittently or fails to download the packages using apt for example, so it's not browser related. Example output of journalctl -xe -u wpasupplicant: Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1 Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with fc:34:97:23:4c:3c Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-94 txrate=27 Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=-95 txrate=27 Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying completed with fc:34:97:23:4c:3c [GTK=CCMP] Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-95 txrate=243000 Additional info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy wpasupplicant wpasupplicant: Geïnstalleerd: 2:2.10-6 Kandidaat: 2:2.10-6 Versietabel: *** 2:2.10-6 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 8 21:28:12 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-12 (27 days ago)
[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled via gnome-system-tools
This bug was fixed in the package ubuntu-mate-meta - 1.282 --- ubuntu-mate-meta (1.282) jammy; urgency=medium * Refreshed dependencies * Removed gnome-system-tools from core-recommends, desktop-recommends (LP: #1706770) -- Martin Wimpress Sat, 09 Apr 2022 01:01:57 +0100 ** Changed in: ubuntu-mate-meta (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled via gnome- system-tools Status in arctica-greeter package in Ubuntu: Invalid Status in gnome-system-tools package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Invalid Status in mate-screensaver package in Ubuntu: Invalid Status in mate-session-manager package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: Fix Released Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1706770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965636] Re: libfuse2 no longer included in jammy, required for AppImages
** Also affects: ubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: kubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: xubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: ubuntustudio-meta (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: lubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: ubuntukylin-meta (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: ubuntu-budgie-meta (Ubuntu Jammy) Importance: Undecided Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965636 Title: libfuse2 no longer included in jammy, required for AppImages Status in kubuntu-meta package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-budgie-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntukylin-meta package in Ubuntu: Confirmed Status in ubuntustudio-meta package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: Fix Released Status in kubuntu-meta source package in Jammy: Fix Released Status in lubuntu-meta source package in Jammy: Confirmed Status in ubuntu-budgie-meta source package in Jammy: Fix Released Status in ubuntu-meta source package in Jammy: Confirmed Status in ubuntukylin-meta source package in Jammy: Confirmed Status in ubuntustudio-meta source package in Jammy: Fix Released Status in xubuntu-meta source package in Jammy: Fix Released Bug description: Attempting to run an AppImage in Xubuntu 22.04 displays the following error: $ ./cryptomator-1.6.5-x86_64.AppImage dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information --- Simply installing libfuse2 resolves this issue. Some flavors seem to still include it. I noticed that today's Ubuntu MATE daily still does. Ubuntu and Xubuntu do not. Ubuntu: https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest Xubuntu: https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest Ubuntu MATE: https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968434] Re: Output Device shows only Dummy Output
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1968434 Title: Output Device shows only Dummy Output Status in alsa-driver package in Ubuntu: New Bug description: Audio was working yesterday. I turned on my computer today and the only output device is Dummy Output. Running aplay -l output is aplay: device_list:276: no soundcards found. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 12:04:59 2022 InstallationDate: Installed on 2021-05-24 (319 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2802 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2802:bd10/21/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-04-09T11:38:59.731560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1968434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968434] [NEW] Output Device shows only Dummy Output
You have been subscribed to a public bug: Audio was working yesterday. I turned on my computer today and the only output device is Dummy Output. Running aplay -l output is aplay: device_list:276: no soundcards found. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 12:04:59 2022 InstallationDate: Installed on 2021-05-24 (319 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2802 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2802:bd10/21/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-04-09T11:38:59.731560 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Output Device shows only Dummy Output https://bugs.launchpad.net/bugs/1968434 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828220] Re: apt-get --install-suggests applied recursively
I agree. This recursive behaviour of '--install-suggests' option makes it unusable, because it pulls enormous amount of dependancies your never want. I suggest just changing it to non recursive without even adding other options, as I hardly believe somebody wants it as it is now. By the way, hackish, non-universal workaround :) apt show PACKAGE | sed -nr '/^(Suggests|Package): /{s///;s/( \|[^,]+)?,//g;p}' | xargs apt install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1828220 Title: apt-get --install-suggests applied recursively Status in apt package in Ubuntu: Opinion Bug description: In a blatent violation of the principal of least surprise, --install- suggests installs packages that are in the suggested packages for packages that are not listed on the command line. It installs suggested packages for other packages deep in the dependency hierarchy. Do not type this command except on an expendable (virtual) machine: sudo apt-get --install-suggests install -y geda geda-utils geda-examples kicad kicad-doc-en librecad oregano qelectrotech xcircuit gerbv pcb pcb-gtk pcb-common pcb-rnd pcb2gcode visolate caneda fritzing In this case, something installed clang which depends on clang-6.0. clang-6.0 very foolishly suggested gnustep which, since apt inappropriately applied --installed-suggests many layers down the dependency tree, then installed the entire gnustep suite of applications. Gnustep, after several more layers of inappropriate suggestsions, caused roaraudio to be installed which caused errors on every apt-get install command. aptitude why roaraudio i clang Depends clang-6.0 (>= 6.0~) i A clang-6.0 Suggests gnustep i A gnustepSuggests mpdcon.app i A mpdcon.app Suggests mpd i A mpdDepends libroar2 i A libroar2 Suggests libmuroar0 i A libmuroar0 Suggests roaraudio | muroard clang later gets installed explicitly, so I cant trace the specific path back to the CAD packages that were installed but clang-6.0 and roaraudio are first installed after the listed apt-get command above. Which ultimately installs 2675 packages. Tracing forward with debtree --with-suggests also doesn't make it clear why clang was installed but debtree doesn't include dependencies of recommended packages. The actual recommends of these packages listed on the apt-get command were rather modest: Recommends: geda-gsymcheck, geda-gattrib Recommends: geda Recommends: xsltproc Recommends: gnucap Recommends: qelectrotech-examples (= 1:0.5-2), qelectrotech-data (= 1:0.5-2), qttranslations5-l10n Recommends: extra-xdg-menus Recommends: extra-xdg-menus The following command suggests that a single package, geda, is sufficient to reproduce the bug. apt-rdepends --follow=Depends,PreDepends,Suggests,Recommends geda | fgrep -i clang It also shows that adding Suggests blows up the dependency tree from 664 lines of dependency info to 49965 lines corresponding to 5865 unique packages vs 173. clang traces back to i18nspector (through python), though it isn't clear why that was needed. It may trace baqck to check-all-the-things and from ther to devscripts but for some reason that isn't included in the apt-rdepends output. debmake, gem2deb, git-buildpackage, javahelper, duck, devscripts-el, svn-buildpackage, and mozzila- devscipts all depend on devscripts. Like many dependencies that should not have been followed, check-all-the-things was only a suggests. i18nspector -> python3-rply -> python3-appdirs -> clang/clang-6.0 This debacle left me with about 6368 packages installed and about 20GB of extra disk space wasted compared to running a fairly similar set of many apt-get commands, without selectively including --install- recommends on a few, on another machine. And ultimately, it appears will be necessary to completely reinstall this computer from scratch to undo the damage. In total, there were only about 50 packages included in "Suggests" without recursion. Not only does --install-suggests behave incorrectly but the man page fails to document this destructive behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.10 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 7 23:11:00 2019 InstallationDate: Installed on 2019-05-02 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1968433] [NEW] dictionaries-common post-install script returns an error
Public bug reported: Ubuntu Release Info: Description:Ubuntu 20.04.4 LTS Release:20.04 dictionaries-common Info: dictionaries-common: Installed: 1.28.1 Candidate: 1.28.1 Version table: *** 1.28.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status The post-install script should have completed, but I am getting: sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up dictionaries-common (1.28.1) ... Processing triggers for dictionaries-common (1.28.1) ... update-default-wordlist: Could not make the default symlink to "/usr/share/dict/american-english". This may be a temporary problem due to installation ordering. If that file is not present after installation, please file a bugreport against wordlist package owning that file. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess retur ned error exit status 2 Errors were encountered while processing: dictionaries-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: dictionaries-common 1.28.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 13:31:15 2022 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dictionaries-common UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dictionaries-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1968433 Title: dictionaries-common post-install script returns an error Status in dictionaries-common package in Ubuntu: New Bug description: Ubuntu Release Info: Description: Ubuntu 20.04.4 LTS Release: 20.04 dictionaries-common Info: dictionaries-common: Installed: 1.28.1 Candidate: 1.28.1 Version table: *** 1.28.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status The post-install script should have completed, but I am getting: sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up dictionaries-common (1.28.1) ... Processing triggers for dictionaries-common (1.28.1) ... update-default-wordlist: Could not make the default symlink to "/usr/share/dict/american-english". This may be a temporary problem due to installation ordering. If that file is not present after installation, please file a bugreport against wordlist package owning that file. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess retur ned error exit status 2 Errors were encountered while processing: dictionaries-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: dictionaries-common 1.28.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 13:31:15 2022 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dictionaries-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1968433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
Awesome, thanks a lot everyone!!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator
For me Application in Terminal are continuing to run in the default MATE Terminal. I have latest Ubuntu MATE 22.04 LTS: ``` $ gsettings get org.mate.applications-terminal exec 'tilix' $ ls /etc/alternatives/x-terminal-emulator -al lrwxrwxrwx 1 root root 22 апр 9 19:01 /etc/alternatives/x-terminal-emulator -> /usr/bin/tilix.wrapper ``` Also please note that mate-desktop-environment is not installed on UM 22.04 LTS by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1873750 Title: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator Status in brisk-menu package in Ubuntu: Invalid Status in classicmenu-indicator package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Confirmed Status in mate-desktop-environment package in Ubuntu: Fix Released Status in mate-menu package in Ubuntu: Invalid Status in mate-menus package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: Invalid Status in mate-settings-daemon package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Fix Released Status in vala-panel-appmenu package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 20.04 LTS 2. Install non-default terminal - Tilix, by `sudo apt-get install tilix` 3. Install terminal-based application - Midnight Commander, by `sudo apt-get install mc` 3. Set Tilix as default terminal in `mate-default-applications-properties` or programmatically: gsettings set org.mate.applications-terminal exec "'tilix'" 4. Set Tilix as alternative for x-terminal-emulator by update- alternatives: update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper sudo update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper 5. Reboot 6. Add Custom Application Launcher to the MATE Panel: Type: Application in Terminal Name: mc Command: mc 7. Click the icon of just created Custom Application Launcher Expected results: * Midnight Commander is opened in the user-defined terminal - in Tilix Actual results: * Midnight Commander is default terminal - in MATE Terminal Notes: * This also happens with desktop-files installed by Midnight Commander, it opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, Dock, + menu, Advanced Mate Menu (`mate-menu` package) * What is interesting, the + respects user preferences and uses Tilix * Also ++ opens Tilix as expected. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mate-panel 1.24.0-2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Apr 20 10:48:51 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)
Bug does not exist in Ubuntu MATE 22.04 LTS. Thanks to ayatana- indicator-datetime! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1828725 Title: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries) Status in Indicator Date and Time: New Status in ayatana-indicator-datetime package in Ubuntu: Fix Released Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu with `indicator-datetime` and `evolution` 2. Add event to *Personal* calendar (default color) 3. Add new calendar and name it for example *Work* (red color) 4. Create contact with two dates - birthday and anniversary (it is pink color) Expected results: * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 LTS (see screenshot - ubuntu-12-04.png) Actual results: * `indicator-datetime` show for event without color squares in the left of them (see screenshot - ubuntu-19-10.png) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Sun May 12 14:54:43 2019 InstallationDate: Installed on 2019-04-28 (13 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1828725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815318] Re: mate 18.04.1 xserver won't open caja on local machine
Bug still exists in latest Ubuntu MATE 22.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1815318 Title: mate 18.04.1 xserver won't open caja on local machine Status in MATE Desktop: New Status in caja package in Ubuntu: Confirmed Status in openssh package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have installed Ubuntu MATE 18.04 LTS (you know its hostname and IP - i.e. 192.168.1.162) 2. Install SSH server on Ubuntu MATE 18.04 LTS 3. Open terminal on other remote system (client) and execute command to run Caja over X forwarding: ssh -X user@192.168.1.162 caja Expected results: * Caja is shown on remote (client) screen with window title *folder (on hostname)* Actual results: * Caja is not shown on remote (client) screen, but launches on server locally. Note: this works normally if server runs Ubuntu MATE 16.04 LTS, but fails with 18.04 LTS. --- Original description below: I can open a remote terminal using ssh -X 192.168.1.162. All other gui's that I've tested opened locally except the file manager Caja. When issuing caja in the remote terminal, I get nothing locally. Caja does open on the remote machine however, just not locally. The ssh -X 18.04.1 client still works connecting to a mate 16.04 server. I've tested this on numerous mate 18.04 clients, two 16.04 servers and two 18.04 servers, all mate. Something is wonky with caja on an 18.04.1 server. Please let me know if I can provide any more information. The only file manager I've tested that works is an X file manager, xfimage. X2go works and connects to servers, SSH Connect to Server works, why isn't the remote X terminal working using caja? To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1815318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
The bug still exists in Ubuntu MATE 22.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in human-theme: New Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Confirmed Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/human-theme/+bug/1721955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968074] Re: moc fails to parse include inside enum
This bug was fixed in the package qtbase-opensource-src - 5.15.3+dfsg-2 --- qtbase-opensource-src (5.15.3+dfsg-2) experimental; urgency=medium [ Andrea Pappacoda ] * Backport upstream patch to fix qtconcurrentthreadengine.h with GCC 11. - Closes: #1008391 [ Dmitry Shachnev ] * Backport upstream patch to fix parsing include inside enum (LP: #1968074). -- Dmitry Shachnev Thu, 07 Apr 2022 18:50:52 +0300 ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1968074 Title: moc fails to parse include inside enum Status in gudhi package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: Seen while trying to rebuild gudhi against qtbase5-dev/ 5.15.3+dfsg-1 : AutoMoc subprocess error The moc process failed to compile "SRC:/src/GudhUI/gui/MainWindow.cpp" into "SRC:/build/userversion/src/GudhUI/GudhUI_autogen/include/MainWindow.moc" included by "SRC:/src/GudhUI/gui/MainWindow.cpp" ... Output -- usr/include/tbb/tbb_profiling.:29: Parse error at "/usr/include/tbb/internal/_tbb_strings.h" Previous builds against qtbase5-dev/5.15.2+dfsg-15 were successful [1]. I found an upstream bug [2] with the same error, although the versions differ. I also found similar bug [3] that is reported to be fixed in 5.15.6. [1] https://launchpad.net/ubuntu/+source/gudhi/3.5.0+dfsg-1ubuntu1 [2] https://bugreports.qt.io/browse/QTBUG-94790 [3] https://bugreports.qt.io/browse/QTBUG-80990 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gudhi/+bug/1968074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
(In reply to semaj4712 from comment #596) > I am assuming this is the same issue. My laptop is a Yoga 9 and I am able > to get sound but it is very quite, not nearly as loud as in Windows. I have > the pavucontrol cranked all the way up and its still super quite. > > Host: 82LU Yoga 9 14IAP7 > Kernel: 5.17.1-arch1-1 > > I was under the understanding that upgrading to 5.17 would fix this but I > guess not. Any help is appreciated Use aslamixer to increase max volume (command line tool). Some recent versions of pipewire tends to reset devices to very low levels and pavucontrol is not able to override the volume limiters. A couple of my systems required this method to fix sound volumes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
I am assuming this is the same issue. My laptop is a Yoga 9 and I am able to get sound but it is very quite, not nearly as loud as in Windows. I have the pavucontrol cranked all the way up and its still super quite. Host: 82LU Yoga 9 14IAP7 Kernel: 5.17.1-arch1-1 I was under the understanding that upgrading to 5.17 would fix this but I guess not. Any help is appreciated -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS Status in wpa package in Ubuntu: Confirmed Bug description: Using the current beta of Jammy, I no longer have stable WiFi after April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There is a chance it may also be related to network-manager going from 1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to wpasupplicant (see below) Wifi is stable often, but also often it fails to load webpages intermittently or fails to download the packages using apt for example, so it's not browser related. Example output of journalctl -xe -u wpasupplicant: Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1 Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with fc:34:97:23:4c:3c Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-94 txrate=27 Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=-95 txrate=27 Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying completed with fc:34:97:23:4c:3c [GTK=CCMP] Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-95 txrate=243000 Additional info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy wpasupplicant wpasupplicant: Geïnstalleerd: 2:2.10-6 Kandidaat: 2:2.10-6 Versietabel: *** 2:2.10-6 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 8 21:28:12 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-12 (27 days
[Touch-packages] [Bug 1832414] Re: Removing document files spam from cups
Today 2022-04-09, I also saw this on my Rocky Linux (updated) after a reboot after a crash, but "systemctl stop cups" and then "systemctl start cups" as root, resolved the issue. Sorry I have no more info than that. ; cups-2.2.6-40.el8.x86_64, Linux 4.18.0-348.12.2.el8_5.x86_64 #1 SMP Wed Jan 19 17:53:40 UTC 2022 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832414 Title: Removing document files spam from cups Status in cups package in Ubuntu: Confirmed Bug description: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1216969] Re: man page names the same file twice -- are there really 2?
** Changed in: bash (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1216969 Title: man page names the same file twice -- are there really 2? Status in bash package in Ubuntu: Triaged Status in bash package in Debian: New Bug description: In the bash(1) man page, INVOCATION section, second-to-last paragraph (begins with "Bash attempts to determine"), it says, in part: "it reads and executes commands from ~/.bashrc and ~/.bashrc," naming the same file twice. I suspect there's a file in /etc that gets read, but in any event the duplication should be either removed or corrected.q ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bash 4.2-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.2.0-49.75-generic-pae 3.2.46 Uname: Linux 3.2.0-49-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Mon Aug 26 07:59:26 2013 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True ProcEnviron: TERM=xterm LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.bash.bashrc: [modified] mtime.conffile..etc.bash.bashrc: 2012-10-05T23:02:00.509472 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1216969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
This bug was fixed in the package systemd - 249.11-0ubuntu3 --- systemd (249.11-0ubuntu3) jammy; urgency=medium * oomd: calculate 'used' memory with MemAvailable instead of MemFree (LP: #1966381) File: debian/patches/lp1966381-oomd-calculate-used-memory-with-MemAvailable-instead-of-M.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15fc4c53d726e1dcae7296a9306cfd453fd1a046 * hwdb: remove the tablet pad entry for the UC-Logic 1060N (LP: #1926860) File: debian/patches/lp1926860-hwdb-remove-the-tablet-pad-entry-for-the-UC-Logic-1060N.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7bf31946a52e55f9f6ea4ecfa30e311685b20997 -- Nick Rosbrook Thu, 07 Apr 2022 15:28:15 -0400 ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966381] Re: systemd-oomd is counting cached as used and triggering more easily than it should
This bug was fixed in the package systemd - 249.11-0ubuntu3 --- systemd (249.11-0ubuntu3) jammy; urgency=medium * oomd: calculate 'used' memory with MemAvailable instead of MemFree (LP: #1966381) File: debian/patches/lp1966381-oomd-calculate-used-memory-with-MemAvailable-instead-of-M.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15fc4c53d726e1dcae7296a9306cfd453fd1a046 * hwdb: remove the tablet pad entry for the UC-Logic 1060N (LP: #1926860) File: debian/patches/lp1926860-hwdb-remove-the-tablet-pad-entry-for-the-UC-Logic-1060N.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7bf31946a52e55f9f6ea4ecfa30e311685b20997 -- Nick Rosbrook Thu, 07 Apr 2022 15:28:15 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966381 Title: systemd-oomd is counting cached as used and triggering more easily than it should Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968412] [NEW] When trying to open the program it says that i need to be in a special group to use it
Public bug reported: Version: 0.99.22 Kubuntu version 22.04 I expected it to open up the software properties without any errors. It said that i need to be in a special group (wheel) to use it. It says the password is incorrect even though i use this password to log in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.22 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 9 11:59:59 2022 InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1968412 Title: When trying to open the program it says that i need to be in a special group to use it Status in software-properties package in Ubuntu: New Bug description: Version: 0.99.22 Kubuntu version 22.04 I expected it to open up the software properties without any errors. It said that i need to be in a special group (wheel) to use it. It says the password is incorrect even though i use this password to log in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.22 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 9 11:59:59 2022 InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1216969] Re: man page names the same file twice -- are there really 2?
> "I unfortunately don't know what the first ~/.bashrc should be replaced with." The author has confirmed that it should just be removed, not replaced. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1216969 Title: man page names the same file twice -- are there really 2? Status in bash package in Ubuntu: Triaged Status in bash package in Debian: Unknown Bug description: In the bash(1) man page, INVOCATION section, second-to-last paragraph (begins with "Bash attempts to determine"), it says, in part: "it reads and executes commands from ~/.bashrc and ~/.bashrc," naming the same file twice. I suspect there's a file in /etc that gets read, but in any event the duplication should be either removed or corrected.q ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bash 4.2-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.2.0-49.75-generic-pae 3.2.46 Uname: Linux 3.2.0-49-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Mon Aug 26 07:59:26 2013 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True ProcEnviron: TERM=xterm LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.bash.bashrc: [modified] mtime.conffile..etc.bash.bashrc: 2012-10-05T23:02:00.509472 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1216969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL
Also affects: gzip (=1.10-4ubuntu4) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL Status in gzip: New Status in gzip package in Ubuntu: Confirmed Bug description: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gzip/+bug/1966849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968313] Re: Bash manual contains an error in the "Invocation" section
*** This bug is a duplicate of bug 1216969 *** https://bugs.launchpad.net/bugs/1216969 Thanks for taking your time to report this issue and help making Ubuntu better. While looking into this issue, I found that it has been discovered and reported by various people over the years. I'm trying to gather the reports into one single place, so I'm marking this as a duplicate of bug 1216969. ** This bug has been marked a duplicate of bug 1216969 man page names the same file twice -- are there really 2? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1968313 Title: Bash manual contains an error in the "Invocation" section Status in bash package in Ubuntu: New Bug description: This is a minor error in the Bash manual, which I have confirmed with one of the authors (Chet Ramey). The error appears to have been created in Debian, and therefore Ubuntu has inherited it. DETAIL In the Bash manual ("man bash"), in the "Invocation" section, the penultimate paragraph has this phrase: "… it reads and executes commands from ~/.bashrc and ~/.bashrc" The file ~/.bashrc should be stated just once, because it's confusing having it mentioned twice. This needs correcting at the Debian level, so that all Debian-based distributions will inherit the fix. • Ubuntu 20.04.4 LTS, Lubuntu 20.04, Ubuntu 21.10 • apt-cache policy bash: 5.0-6ubuntu1.1 • bash --version: GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 11:18:38 2022 InstallationDate: Installed on 2020-09-05 (579 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1968313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1216969] Re: man page names the same file twice -- are there really 2?
Can confirm this issue is still present in bash 5.1-6ubuntu1 on Ubuntu Jammy ( http://manpages.ubuntu.com/manpages/jammy/en/man1/bash.1.html#invocation ). It has been discovered and reported by various people over the years (see the attached bug watch for a corresponding Debian report), so I'm trying to gather the duplicates in one place her. >It doesn't seem to be upstream bash, No, this is also confirmed by duplicate bug 1968313 I believe it should be a simple fix, but I unfortunately don't know what the first ~/.bashrc should be replaced with. ** Bug watch added: Debian Bug tracker #601105 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601105 ** Also affects: bash (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601105 Importance: Unknown Status: Unknown ** Tags added: bionic focal jammy manpage string-fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1216969 Title: man page names the same file twice -- are there really 2? Status in bash package in Ubuntu: Triaged Status in bash package in Debian: Unknown Bug description: In the bash(1) man page, INVOCATION section, second-to-last paragraph (begins with "Bash attempts to determine"), it says, in part: "it reads and executes commands from ~/.bashrc and ~/.bashrc," naming the same file twice. I suspect there's a file in /etc that gets read, but in any event the duplication should be either removed or corrected.q ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bash 4.2-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.2.0-49.75-generic-pae 3.2.46 Uname: Linux 3.2.0-49-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Mon Aug 26 07:59:26 2013 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True ProcEnviron: TERM=xterm LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.bash.bashrc: [modified] mtime.conffile..etc.bash.bashrc: 2012-10-05T23:02:00.509472 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1216969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728709] Re: bash man page has a typo, repeating .bashrc when one should be /etc/bash.bashrc
*** This bug is a duplicate of bug 1216969 *** https://bugs.launchpad.net/bugs/1216969 I took the liberty of marking this as a duplicate of bug 1216969 which is already marked as triaged. ** This bug has been marked a duplicate of bug 1216969 man page names the same file twice -- are there really 2? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1728709 Title: bash man page has a typo, repeating .bashrc when one should be /etc/bash.bashrc Status in bash package in Ubuntu: Confirmed Bug description: The INVOCATION section of the man page has the text "reads and executes commands from ~/.bashrc and ~/.bashrc, if these files exist and are readable" which repeats "~/.bashrc". By experiment, I find it probable that the first of these .bashrc references should read "/etc/bash.bashrc". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bash 4.3-14ubuntu1.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Oct 30 13:28:43 2017 InstallationDate: Installed on 2016-08-08 (447 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1728709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
Now with latest update to x86_64-linux-gnu/libQt5Network.so.5.15.3 there's no hack available anymore -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: Incomplete Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968399] [NEW] Display Server Crashes
Public bug reported: If I switch from one computer to another using my hardware KVM, when I switch back the display server has crashed and the Ubuntu boot screen is showing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..11.00.0: Error: path was not a regular file. .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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 00:49:23 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104GL [RTX A4000] [10de:24b0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA104GL [RTX A4000] [10de:14ad] InstallationDate: Installed on 2022-04-07 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=c56061b9-1478-4914-a919-96eb077fff48 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F62d dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF62d:bd10/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X470 MB dmi.product.name: X470 AORUS ULTRA GAMING dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1968399 Title: Display Server Crashes Status in xorg package in Ubuntu: New Bug description: If I switch from one computer to another using my hardware KVM, when I switch back the display server has crashed and the Ubuntu boot screen is showing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..11.00.0: Error: path was not a regular file. .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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass