[Touch-packages] [Bug 1838771] Re: http:Fix Host header in proxied https connections
** Bug watch added: Debian Bug tracker #977930 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977930 ** Also affects: apt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977930 Importance: Unknown Status: Unknown -- 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/1838771 Title: http:Fix Host header in proxied https connections Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Disco: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Currently CONNECT requests use the name of the proxy as Host value, instead of the origin server's name. According to RFC 2616 "The Host field value MUST represent the naming authority of the origin server or gateway given by the original URL." The current implementation causes problems with some proxy vendors. This commit[0] fixes this. [0] - https://salsa.debian.org/apt- team/apt/commit/86d4d98060f36c7e71c34af20a1193a75496ef72#54d3193c5d10a0032c80c3a6d3f069507265547f [Test Case] Here's one reproducer an impacted user brought to my attention: # /etc/environment http_proxy="http://internal:8080"; https_proxy="http://interal:8080"; To support application development activities in-house, I had to configure Azure CLI APT repository following the instructions from "https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-apt?view =azure-cli-latest": $ sudo apt-get update $ sudo apt-get install curl apt-transport-https lsb-release gnupg $ curl -sL https://packages.microsoft.com/keys/microsoft.asc | \ $ gpg --dearmor | \ $ sudo tee /etc/apt/trusted.gpg.d/microsoft.asc.gpg > /dev/null $ AZ_REPO=$(lsb_release -cs) $ echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $ $ AZ_REPO main" | \ $ sudo tee /etc/apt/sources.list.d/azure-cli.list $ sudo apt update In the final "apt update" command, APT respects system-wide network proxy variables and successfully fetched Canonical repository data over HTTP. However, it was unable to fetch the newly added Microsoft packages repository served via HTTPS. By using Wireshark to examine the HTTPS request made by APT, the request body reveals as: CONNECT packages.microsoft.com:443 HTTP/1.1\r\n Host: internal:8080\r\n User-Agent: Debian APT-HTTP/1.3 (1.6.11)\r\n ... ... There also is an automated test case in the package that runs as part of autopkgtest that tests a scenario like this, see the commit. [Regression Potential] * Fix already in debian, and Eoan * Has been reviewed/approved by juliank * A test package (pre-sru) has been provided to an impacted user, and he confirms it solves the situation. [Other Info] # salsa $ git describe --contains 86d4d98060f36c7e71c34af20a1193a75496ef72 1.9.0~8 # rmadison apt => apt | 1.6.11 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x => apt | 1.8.1 | disco-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x apt | 1.9.1 | eoan | source, amd64, arm64, armhf, i386, ppc64el, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1838771/+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 465433]
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/465433 Title: dolphin crashed in [PolygonRegion, QRegion, QX11PaintEngine::updateState] (assert failure) Status in Qt: Incomplete Status in qt4-x11 package in Ubuntu: Triaged Bug description: Binary package hint: kdebase Release: Kubuntu 9.10, i386 Dolphin package version: 4:4.3.2-0ubuntu3 Dolphin crashed when I tried to move one picture from one folder to another folder (each opened in separate Dolphin windows). Expected result: - picture gets moved - both windows stay opened Actual result: - picture got moved - Dolphin crashed (all opened windows disappeared) ProblemType: Crash Architecture: i386 AssertionMessage: *** glibc detected *** dolphin: corrupted double-linked list: 0x09c774f0 *** Date: Fri Oct 30 20:39:43 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/dolphin Package: dolphin 4:4.3.2-0ubuntu3 ProcCmdline: dolphin -session 10d2dc656600012567575210229620045_1256913310_108428 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic Signal: 6 SourcePackage: kdebase StacktraceTop: __kernel_vsyscall () *__GI_raise (sig=6) *__GI_abort () at abort.c:92 __libc_message (do_abort=2, malloc_printerr (action=, Title: dolphin assert failure: *** glibc detected *** dolphin: corrupted double-linked list: 0x09c774f0 *** Uname: Linux 2.6.31-14-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (polkit-gnome-authentication-agent-1:2444): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/465433/+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 1901053] Re: apt preferences files do nothing re: apt-cache policy
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (Ubuntu) Status: Incomplete => Expired -- 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/1901053 Title: apt preferences files do nothing re: apt-cache policy Status in apt package in Ubuntu: Expired Bug description: apt-cache policy does not reflect priority set in /etc/apt/preferences.d/* avery@ChubbyChipmunk:/etc/apt/preferences.d$ apt-cache policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu focal/main amd64 Packages release v=20.04,o=LP-PPA-webupd8team-y-ppa-manager,a=focal,n=focal,l=Y PPA Manager,c=main,b=amd64 origin ppa.launchpad.net 500 http://ppa.launchpad.net/system76/pop/ubuntu groovy/main amd64 Packages release v=20.10,o=LP-PPA-system76-pop,a=groovy,n=groovy,l=Pop!_OS PPA,c=main,b=amd64 origin ppa.launchpad.net 500 https://packagecloud.io/slacktechnologies/slack/debian jessie/main amd64 Packages release v=1,o=packagecloud.io/slacktechnologies/slack,a=jessie,n=jessie,l=slack,c=main,b=amd64 origin packagecloud.io 500 http://apt.pop-os.org/proprietary groovy/main amd64 Packages release v=20.10,o=system76,a=groovy,n=groovy,l=System76,c=main,b=amd64 origin apt.pop-os.org 500 https://download.mono-project.com/repo/ubuntu stable-focal/main amd64 Packages release v=20.04,o=XamarinFocal,a=stable-focal,n=focal,l=Xamarin-Stable-Focal,c=main,b=amd64 origin download.mono-project.com 500 https://packages.microsoft.com/ubuntu/18.04/prod bionic/main amd64 Packages release o=microsoft-ubuntu-bionic-prod bionic,a=bionic,n=bionic,l=microsoft-ubuntu-bionic-prod bionic,c=main,b=amd64 origin packages.microsoft.com 500 http://ppa.launchpad.net/linuxuprising/shutter/ubuntu groovy/main amd64 Packages release v=20.10,o=LP-PPA-linuxuprising-shutter,a=groovy,n=groovy,l=Shutter screenshot tool and dependencies,c=main,b=amd64 origin ppa.launchpad.net 500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages release v=1.0,o=Google LLC,a=stable,n=stable,l=Google,c=main,b=amd64 origin dl.google.com 500 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04 Packages release o=obs://build.opensuse.org/devel:kubic:libcontainers:stable/xUbuntu_20.04,n=xUbuntu_20.04,l=devel:kubic:libcontainers:stable,c= origin download.opensuse.org 500 http://packages.microsoft.com/ubuntu/18.04/mssql-server-2019 bionic/main amd64 Packages release o=mssql-server-2019-bionic bionic,a=bionic,n=bionic,l=mssql-server-2019-bionic bionic,c=main,b=amd64 origin packages.microsoft.com 500 http://mirrors.vcea.wsu.edu/ubuntu groovy-proposed/main i386 Packages release v=20.10,o=Ubuntu,a=groovy-proposed,n=groovy,l=Ubuntu,c=main,b=i386 origin mirrors.vcea.wsu.edu 500 http://mirrors.vcea.wsu.edu/ubuntu groovy-proposed/main amd64 Packages release v=20.10,o=Ubuntu,a=groovy-proposed,n=groovy,l=Ubuntu,c=main,b=amd64 origin mirrors.vcea.wsu.edu 500 http://mirrors.vcea.wsu.edu/ubuntu groovy-proposed/multiverse i386 Packages release v=20.10,o=Ubuntu,a=groovy-proposed,n=groovy,l=Ubuntu,c=multiverse,b=i386 origin mirrors.vcea.wsu.edu 500 http://mirrors.vcea.wsu.edu/ubuntu groovy-proposed/multiverse amd64 Packages release v=20.10,o=Ubuntu,a=groovy-proposed,n=groovy,l=Ubuntu,c=multiverse,b=amd64 origin mirrors.vcea.wsu.edu 500 http://mirrors.vcea.wsu.edu/ubuntu groovy-proposed/restricted i386 Packages release v=20.10,o=Ubuntu,a=groovy-proposed,n=groovy,l=Ubuntu,c=restricted,b=i386 origin mirrors.vcea.wsu.edu 500 http://mirrors.vcea.wsu.edu/ubuntu groovy-proposed/restricted amd64 Packages release v=20.10,o=Ubuntu,a=groovy-proposed,n=groovy,l=Ubuntu,c=restricted,b=amd64 origin mirrors.vcea.wsu.edu 500 http://mirrors.vcea.wsu.edu/ubuntu groovy-proposed/universe i386 Packages release v=20.10,o=Ubuntu,a=groovy-proposed,n=groovy,l=Ubuntu,c=universe,b=i386 origin mirrors.vcea.wsu.edu 500 http://mirrors.vcea.wsu.edu/ubuntu groovy-proposed/universe amd64 Packages release v=20.10,o=Ubuntu,a=groovy-proposed,n=groovy,l=Ubuntu,c=universe,b=amd64 origin mirrors.vcea.wsu.edu 500 http://mirrors.vcea.wsu.edu/ubuntu groovy-security/universe i386 Packages release v=20.10,o=Ubuntu,a=groovy-security,n=groovy,l=Ubuntu,c=universe,b=i386 origin mirrors.vcea.wsu.edu 500 http://mirrors.vcea.wsu.edu/ubuntu groovy-security/universe amd64 Packages release v=20.10,o=Ubuntu,a=groovy-security,n=groovy,l=Ubuntu,c=universe,b=amd64 origin mirrors.vcea.wsu.edu 500 http://mirrors.v
[Touch-packages] [Bug 1908639] Re: Will not authenticate to Icecast 2 server
Confirmed functional. Great job everyone!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libshout in Ubuntu. https://bugs.launchpad.net/bugs/1908639 Title: Will not authenticate to Icecast 2 server Status in Libshout: Fix Released Status in Mixxx: Fix Released Status in libshout package in Ubuntu: New Status in mixxx package in Ubuntu: Confirmed Bug description: Mixx will not perform a Basic login authentication. When receiving an authentication challange from the Icecast server, it quits and produces the following error: Please retry current operation. Please check your connection to the Internet and verify that your username and password are correct. WIRESHARK ENTIRE TCP STREAM AS FOLLOWS: SOURCE /wolfradio HTTP/1.0 Host: fm.wolflake:8080 User-Agent: libshout/2.4.3 Content-Type: application/ogg Content-Length: 0 Connection: Keep-Alive ice-public: 0 ice-name: Wolf Lake ice-description: This stream is online for testing purposes! ice-genre: Live Mix ice-url: http://fm.wolflake ice-irc: ice-aim: ice-icq: ice-audio-info: bitrate=128 HTTP/1.0 401 Authentication Required Server: Icecast 2.4.3 Date: Fri, 18 Dec 2020 05:24:10 GMT Content-Type: text/plain; charset=utf-8 WWW-Authenticate: Basic realm="Icecast2 Server" Cache-Control: no-cache Expires: Mon, 26 Jul 1997 05:00:00 GMT Pragma: no-cache Access-Control-Allow-Origin: * You need to authenticate END OF WIRESHARK STREAM There are no more transactions. MIXXX running on: Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal ICECAST2 running on: Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-29 (235 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mixxx 2.2.3~dfsg-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Tags: focal Uname: Linux 5.4.0-58-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/libshout/+bug/1908639/+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 1902217] Re: package ca-certificates 20201027ubuntu0.20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ca-certificates (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1902217 Title: package ca-certificates 20201027ubuntu0.20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu 20.04.1 LTS Release: 20.04 2) ca-certificates: Installiert: 20201027ubuntu0.20.04.1 Installationskandidat: 20201027ubuntu0.20.04.1 Versionstabelle: *** 20201027ubuntu0.20.04.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 100 /var/lib/dpkg/status 20190110ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages 3) Update runs smooth without errors 4) Installation error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ca-certificates 20201027ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 30 12:11:41 2020 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-11-02 (2188 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: ca-certificates Title: package ca-certificates 20201027ubuntu0.20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-08-02 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1902217/+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 1908639] Re: Will not authenticate to Icecast 2 server
** Changed in: libshout Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libshout in Ubuntu. https://bugs.launchpad.net/bugs/1908639 Title: Will not authenticate to Icecast 2 server Status in Libshout: Fix Released Status in Mixxx: Fix Released Status in libshout package in Ubuntu: New Status in mixxx package in Ubuntu: Confirmed Bug description: Mixx will not perform a Basic login authentication. When receiving an authentication challange from the Icecast server, it quits and produces the following error: Please retry current operation. Please check your connection to the Internet and verify that your username and password are correct. WIRESHARK ENTIRE TCP STREAM AS FOLLOWS: SOURCE /wolfradio HTTP/1.0 Host: fm.wolflake:8080 User-Agent: libshout/2.4.3 Content-Type: application/ogg Content-Length: 0 Connection: Keep-Alive ice-public: 0 ice-name: Wolf Lake ice-description: This stream is online for testing purposes! ice-genre: Live Mix ice-url: http://fm.wolflake ice-irc: ice-aim: ice-icq: ice-audio-info: bitrate=128 HTTP/1.0 401 Authentication Required Server: Icecast 2.4.3 Date: Fri, 18 Dec 2020 05:24:10 GMT Content-Type: text/plain; charset=utf-8 WWW-Authenticate: Basic realm="Icecast2 Server" Cache-Control: no-cache Expires: Mon, 26 Jul 1997 05:00:00 GMT Pragma: no-cache Access-Control-Allow-Origin: * You need to authenticate END OF WIRESHARK STREAM There are no more transactions. MIXXX running on: Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal ICECAST2 running on: Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-29 (235 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mixxx 2.2.3~dfsg-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Tags: focal Uname: Linux 5.4.0-58-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/libshout/+bug/1908639/+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 1483975] Re: update-initramfs complains about missing /sbin/fsck.btrfs
I'm still seeing this message in Ubuntu Mate 20.04 on December 22,2020: "W: /sbin/fsck.btrfs doesn't exist, can't install to initramfs" Has the released fix just not been incorporated into the distros after 18 months? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1483975 Title: update-initramfs complains about missing /sbin/fsck.btrfs Status in btrfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Confirmed Status in btrfs-tools package in Debian: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: /sbin/fsck.btrfs moved to /bin/fsck.btrfs with btrfs-tools 4.0-2 (http://bugs.debian.org/784234), which causes $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs, ignoring. I assume this means that fsck won’t run on a btrfs /, which seems bad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1483975/+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 1908639] Re: Will not authenticate to Icecast 2 server
2.4.3-1 is the buggy libshout version. Please upgrade to Mixxx 2.2.4 which statically links to libshout 2.4.1. sudo add-apt-repository ppa:mixxx/mixxx sudo apt-get update sudo apt-get install mixxx please report if this solves the issue. ** Changed in: mixxx (Ubuntu) Status: New => Confirmed ** Also affects: mixxx Importance: Undecided Status: New ** Changed in: mixxx Status: New => Fix Released ** Changed in: mixxx Milestone: None => 2.4.0 ** Bug watch added: gitlab.xiph.org/xiph/icecast-libshout/issues #2308 https://gitlab.xiph.org/xiph/icecast-libshout/issues/2308 ** Also affects: libshout via https://gitlab.xiph.org/xiph/icecast-libshout/issues/2308 Importance: Unknown Status: Unknown ** Also affects: libshout (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libshout in Ubuntu. https://bugs.launchpad.net/bugs/1908639 Title: Will not authenticate to Icecast 2 server Status in Libshout: Unknown Status in Mixxx: Fix Released Status in libshout package in Ubuntu: New Status in mixxx package in Ubuntu: Confirmed Bug description: Mixx will not perform a Basic login authentication. When receiving an authentication challange from the Icecast server, it quits and produces the following error: Please retry current operation. Please check your connection to the Internet and verify that your username and password are correct. WIRESHARK ENTIRE TCP STREAM AS FOLLOWS: SOURCE /wolfradio HTTP/1.0 Host: fm.wolflake:8080 User-Agent: libshout/2.4.3 Content-Type: application/ogg Content-Length: 0 Connection: Keep-Alive ice-public: 0 ice-name: Wolf Lake ice-description: This stream is online for testing purposes! ice-genre: Live Mix ice-url: http://fm.wolflake ice-irc: ice-aim: ice-icq: ice-audio-info: bitrate=128 HTTP/1.0 401 Authentication Required Server: Icecast 2.4.3 Date: Fri, 18 Dec 2020 05:24:10 GMT Content-Type: text/plain; charset=utf-8 WWW-Authenticate: Basic realm="Icecast2 Server" Cache-Control: no-cache Expires: Mon, 26 Jul 1997 05:00:00 GMT Pragma: no-cache Access-Control-Allow-Origin: * You need to authenticate END OF WIRESHARK STREAM There are no more transactions. MIXXX running on: Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal ICECAST2 running on: Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-29 (235 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mixxx 2.2.3~dfsg-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Tags: focal Uname: Linux 5.4.0-58-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/libshout/+bug/1908639/+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 1908733] Re: CVE-2020-1971 OpenSSL package upgrade issue
Hello, you've replaced the Ubuntu OpenSSL packages with Ondrej's OpenSSL packages. You can ask him if he has performed the corresponding update yet: https://github.com/oerdnj/deb.sury.org Thanks ** Information type changed from Private Security to Public Security ** Changed in: openssl (Ubuntu) Status: New => Invalid -- 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/1908733 Title: CVE-2020-1971 OpenSSL package upgrade issue Status in openssl package in Ubuntu: Invalid Bug description: Hello, I have tested it on 4 vurtual machines (details below): # uname -a Linux web2 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ apt-cache policy openssl openssl: Installed: 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 Candidate: 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 Version table: *** 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 500 500 http://ppa.launchpad.net/ondrej/apache2/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 500 500 http://ppa.launchpad.net/ondrej/php/ubuntu bionic/main amd64 Packages 1.1.1-1ubuntu2.1~18.04.7 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.1.0g-2ubuntu4 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages My OpenSSL version is: openssl 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 I wanted to install patch to fix "CVE-2020-1971" on my virtual machines. But found next issue: there is article ( https://ubuntu.com/security/CVE-2020-1971) with package name (version), where "CVE-2020-1971" issues is fixed --> "1.1.1-1ubuntu2.1~18.04.7". Normal (expected?) behaviour for me (in my case) is to do next: sudo apt update sudo apt upgrade After this all packages in my system should be upgraded to latest versions. But in fact - OpenSSL package remained same 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 When i check: $ apt list openssl Listing... Done openssl/bionic,now 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 amd64 [installed] N: There are 3 additional versions. Please use the '-a' switch to see them. $ apt list openssl -a Listing... Done openssl/bionic,now 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 amd64 [installed] openssl/bionic 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 amd64 openssl/bionic-updates,bionic-security 1.1.1-1ubuntu2.1~18.04.7 amd64 openssl/bionic 1.1.0g-2ubuntu4 amd64 Ok, lets install latest package --> 1.1.1-1ubuntu2.1~18.04.7: sudo apt install openssl=1.1.1-1ubuntu2.1~18.04.7 And here i receive next: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be DOWNGRADED: openssl 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Need to get 614 kB of archives. After this operation, 132 kB disk space will be freed. Do you want to continue? [Y/n] yn Get:1 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 openssl amd6 4 1.1.1-1ubuntu2.1~18.04.7 [614 kB] Fetched 614 kB in 0s (1,367 kB/s) dpkg: warning: downgrading openssl from 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 to 1.1.1-1ubuntu2.1~18.04.7 Is this correct behavior? Why newest version (mentioned in https://ubuntu.com/security/CVE-2020-1971) considered as DOWNGRADE? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1908733/+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 1909032] [NEW] No sound through HDMI, option listed even without cable
Public bug reported: The hdmi audio output option is always in the list (even without the cable) but it doesn't work ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 15714 F pulseaudio /dev/snd/controlC1: marco 15714 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 19:06:51 2020 InstallationDate: Installed on 2020-05-21 (215 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Audio interno - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 15714 F pulseaudio /dev/snd/controlC1: marco 15714 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [X550JD, Intel Generic, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to groovy on 2020-12-22 (0 days ago) dmi.bios.date: 10/08/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JD.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JD.303:bd10/08/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550JD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JD dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-12-21T11:16:00.079207 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1909032 Title: No sound through HDMI, option listed even without cable Status in alsa-driver package in Ubuntu: New Bug description: The hdmi audio output option is always in the list (even without the cable) but it doesn't work ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 15714 F pulseaudio /dev/snd/controlC1: marco 15714 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 19:06:51 2020 InstallationDate: Installed on 2020-05-21 (215 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Audio interno - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 15714 F pulseaudio /dev/snd/controlC1: marco 15714 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [X550JD, Intel Generic, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to groovy on 2020-12-22 (0 days ago) dmi.bios.date: 10/08/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JD.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JD.303:bd10/08/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550JD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JD dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-12-21T11:16:00.079207 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1909032/+subscriptions -- Mailing list: ht
[Touch-packages] [Bug 1909028] [NEW] Lines coming up on screen
Public bug reported: Multiple times I see that the scrolling/ video playing is not smooth and things come up in layers. This issue is especially visible while scrolling in vertical (tablet) orientation and watching videos with a lot of motion. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 22:43:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-42-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80d0] Subsystem: Hewlett-Packard Company GM108M [GeForce 930M] [103c:80d0] InstallationDate: Installed on 2020-12-15 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:57c4 Realtek Semiconductor Corp. HP Truevision HD Bus 001 Device 007: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=2518abd7-c310-4c54-84cb-86e6f8d53f4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.19 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80D0 dmi.board.vendor: HP dmi.board.version: 84.29 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP ENVY x360 Convertible dmi.product.sku: T5Q56PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- 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/1909028 Title: Lines coming up on screen Status in xorg package in Ubuntu: New Bug description: Multiple times I see that the scrolling/ video playing is not smooth and things come up in layers. This issue is especially visible while scrolling in vertical (tablet) orientation and watching videos with a lot of motion. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabili
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: apt (Ubuntu) Assignee: star hvh (starhvh) => (unassigned) -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmd
[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
** Changed in: systemd Status: Unknown => New -- 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python testemail2jira/testemail2jira.py User=root [Install] WantedBy=multi-user.target Perhaps the problem is that my service file is a template (testemail2jira@.service), but I symlinked it as a regular 'testemail2jira.service'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 16 14:13:06 2020 InstallationDate: Installed on 2020-05-27 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1887744/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: apt (Ubuntu) Assignee: (unassigned) => star hvh (starhvh) -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmd
[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
** Bug watch added: github.com/systemd/systemd/issues #18058 https://github.com/systemd/systemd/issues/18058 ** Also affects: systemd via https://github.com/systemd/systemd/issues/18058 Importance: Unknown Status: Unknown -- 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd: Unknown Status in systemd package in Ubuntu: Confirmed Bug description: On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python testemail2jira/testemail2jira.py User=root [Install] WantedBy=multi-user.target Perhaps the problem is that my service file is a template (testemail2jira@.service), but I symlinked it as a regular 'testemail2jira.service'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 16 14:13:06 2020 InstallationDate: Installed on 2020-05-27 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1887744/+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 1909006] [NEW] Split screen
Public bug reported: My screen is split in 4 and forums have directed me to try and update my video graphics drivers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 14:52:26 2020 DistUpgraded: 2020-08-03 22:59:11,316 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fb30] InstallationDate: Installed on 2020-02-09 (316 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TOSHIBA Satellite C850-F74T 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.4.0-58-generic root=UUID=ed9c77f9-c96b-4904-8ba9-1576f2c3a198 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-03 (140 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: PLCSF8 dmi.board.vendor: Intel dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.00:bd08/31/2012:svnTOSHIBA:pnSatelliteC850-F74T:pvrPSCBWF-011004F3:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite C850-F74T dmi.product.sku: PSCBWF dmi.product.version: PSCBWF-011004F3 dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- 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/1909006 Title: Split screen Status in xorg package in Ubuntu: New Bug description: My screen is split in 4 and forums have directed me to try and update my video graphics drivers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 14:52:26 2020 DistUpgraded: 2020-08-03 22:59:11,316 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fb30] InstallationDate: Installed on 2020-02-09 (316 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TOSHIBA Satellite C850-F74T 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.4.0-58-generic root=UUID=ed9c77f9-c96b-4904-8ba9-1576f2c3a198 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-03 (140 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: PLCSF8 dmi.board.vendor: Intel dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.
[Touch-packages] [Bug 1908998] Re: Failed to start Service for snap application tor.tor.
** Package changed: ubuntu => systemd (Ubuntu) -- 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/1908998 Title: Failed to start Service for snap application tor.tor. Status in systemd package in Ubuntu: New Bug description: In the important tab of Logs I get this error: /* Sender: systemd Message: Failed to start Service for snap application tor.tor. Subject: A start job for unit snap.tor.tor.service has failed Defined by: systemd A start job for unit snap.tor.tor.service has finished with a failure. The job identifier is 2061 and the job result is failed. */ My syslog and kern.log files are huge > 80GB each and I was told that I should resolve errors there in order for the files to return to normal sizes. OS: Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.0.0-1070.76-oem-osp1 5.0.21 Uname: Linux 5.0.0-1070-oem-osp1 x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 12:22:20 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1070-oem-osp1 root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908998/+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 1908998] [NEW] Failed to start Service for snap application tor.tor.
You have been subscribed to a public bug: In the important tab of Logs I get this error: /* Sender: systemd Message: Failed to start Service for snap application tor.tor. Subject: A start job for unit snap.tor.tor.service has failed Defined by: systemd A start job for unit snap.tor.tor.service has finished with a failure. The job identifier is 2061 and the job result is failed. */ My syslog and kern.log files are huge > 80GB each and I was told that I should resolve errors there in order for the files to return to normal sizes. OS: Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.0.0-1070.76-oem-osp1 5.0.21 Uname: Linux 5.0.0-1070-oem-osp1 x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 12:22:20 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1070-oem-osp1 root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Failed to start Service for snap application tor.tor. https://bugs.launchpad.net/bugs/1908998 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1907850] Re: Cache not generated for all translations
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- 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/1907850 Title: Cache not generated for all translations Status in apt package in Ubuntu: Confirmed Bug description: [Impact] In bug 1161743 we discovered that if a system is configured with multiple locales, only the locales of the user who generated the apt-cache will be available for translated descriptions. [Test case] # apt install locales-all # get the locale # export LANG=sv_SE.UTF-8 # locale LANG=sv_SE.UTF-8 LANGUAGE= LC_CTYPE="sv_SE.UTF-8" LC_NUMERIC="sv_SE.UTF-8" LC_TIME="sv_SE.UTF-8" LC_COLLATE="sv_SE.UTF-8" LC_MONETARY="sv_SE.UTF-8" LC_MESSAGES="sv_SE.UTF-8" LC_PAPER="sv_SE.UTF-8" LC_NAME="sv_SE.UTF-8" LC_ADDRESS="sv_SE.UTF-8" LC_TELEPHONE="sv_SE.UTF-8" LC_MEASUREMENT="sv_SE.UTF-8" LC_IDENTIFICATION="sv_SE.UTF-8" LC_ALL= # apt update # apt-cache show tasksel | grep Desc Description-sv: tool for selecting tasks for installation on Debian systems Description-md5: cbbb747708986d11ea77c80b9b038fec # apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: sv File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec [...] So far so good, but now assume the root user actually has C configured as locale, and e.g. runs apt-cache show (or apt-daily.service does an update): root@g:~# rm /var/cache/apt/*.bin root@g:~# LANG=C apt-cache show tasksel [...] Description-en: tool for selecting tasks for installation on Debian systems This package provides 'tasksel', a simple interface for users who want to configure their system to perform a specific task. root@g:~# apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec This should show the sv locale as well given that it's still around (also we are still running with LANG=sv_SE.UTF-8), but it only generated the cache with the english language description in here. [Where problems could occur] Unknown so far, we've not investigated the cause or solution yet. [Other Info] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1907850/+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 1907850] Re: Cache not generated for all translations
I found that update-manager causes such wrong cache generation. If it fetches updated information about packages during "Checking for updates..." it will generate wrong cache and "apt show" will not display translated descriptions. -- 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/1907850 Title: Cache not generated for all translations Status in apt package in Ubuntu: Confirmed Bug description: [Impact] In bug 1161743 we discovered that if a system is configured with multiple locales, only the locales of the user who generated the apt-cache will be available for translated descriptions. [Test case] # apt install locales-all # get the locale # export LANG=sv_SE.UTF-8 # locale LANG=sv_SE.UTF-8 LANGUAGE= LC_CTYPE="sv_SE.UTF-8" LC_NUMERIC="sv_SE.UTF-8" LC_TIME="sv_SE.UTF-8" LC_COLLATE="sv_SE.UTF-8" LC_MONETARY="sv_SE.UTF-8" LC_MESSAGES="sv_SE.UTF-8" LC_PAPER="sv_SE.UTF-8" LC_NAME="sv_SE.UTF-8" LC_ADDRESS="sv_SE.UTF-8" LC_TELEPHONE="sv_SE.UTF-8" LC_MEASUREMENT="sv_SE.UTF-8" LC_IDENTIFICATION="sv_SE.UTF-8" LC_ALL= # apt update # apt-cache show tasksel | grep Desc Description-sv: tool for selecting tasks for installation on Debian systems Description-md5: cbbb747708986d11ea77c80b9b038fec # apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: sv File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec [...] So far so good, but now assume the root user actually has C configured as locale, and e.g. runs apt-cache show (or apt-daily.service does an update): root@g:~# rm /var/cache/apt/*.bin root@g:~# LANG=C apt-cache show tasksel [...] Description-en: tool for selecting tasks for installation on Debian systems This package provides 'tasksel', a simple interface for users who want to configure their system to perform a specific task. root@g:~# apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec This should show the sv locale as well given that it's still around (also we are still running with LANG=sv_SE.UTF-8), but it only generated the cache with the english language description in here. [Where problems could occur] Unknown so far, we've not investigated the cause or solution yet. [Other Info] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1907850/+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 1908991] Re: Compose key doesn't work after a while
** Attachment added: "xev output (buggy/not working case)" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+attachment/5445763/+files/xev.bad -- 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/1908991 Title: Compose key doesn't work after a while Status in systemd package in Ubuntu: New Bug description: I attached my M-TECH keyboard to USB 2.0 hub connected to USB 2.0 port on my laptop. I also attached my mouse to the same hub. On kernels up to 5.9, compose key (which I defined as Right Super/Right Win) worked for a while, and then did not work (no accented letter inserted when typing right sequence). For example, instead of à I got `a. On 5.10 kernel (I reported this bug using custom-compiled 5.10.1 kernel), compose key does not work initially. The workaround is to open Tweaks and redefine compose key to the same key. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 Uname: Linux 5.10.1-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.snapd.rules Date: Tue Dec 22 15:44:43 2020 InstallationDate: Installed on 2020-05-05 (230 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.1-kernelorg-upstream-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:br1.4:efr1.4:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+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 1908991] Re: Compose key doesn't work after a while
** Attachment added: "xkb" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+attachment/5445761/+files/xprop-xkb -- 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/1908991 Title: Compose key doesn't work after a while Status in systemd package in Ubuntu: New Bug description: I attached my M-TECH keyboard to USB 2.0 hub connected to USB 2.0 port on my laptop. I also attached my mouse to the same hub. On kernels up to 5.9, compose key (which I defined as Right Super/Right Win) worked for a while, and then did not work (no accented letter inserted when typing right sequence). For example, instead of à I got `a. On 5.10 kernel (I reported this bug using custom-compiled 5.10.1 kernel), compose key does not work initially. The workaround is to open Tweaks and redefine compose key to the same key. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 Uname: Linux 5.10.1-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.snapd.rules Date: Tue Dec 22 15:44:43 2020 InstallationDate: Installed on 2020-05-05 (230 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.1-kernelorg-upstream-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:br1.4:efr1.4:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+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 1908991] Re: Compose key doesn't work after a while
** Attachment added: "xev output (working case)" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+attachment/5445762/+files/xev.good -- 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/1908991 Title: Compose key doesn't work after a while Status in systemd package in Ubuntu: New Bug description: I attached my M-TECH keyboard to USB 2.0 hub connected to USB 2.0 port on my laptop. I also attached my mouse to the same hub. On kernels up to 5.9, compose key (which I defined as Right Super/Right Win) worked for a while, and then did not work (no accented letter inserted when typing right sequence). For example, instead of à I got `a. On 5.10 kernel (I reported this bug using custom-compiled 5.10.1 kernel), compose key does not work initially. The workaround is to open Tweaks and redefine compose key to the same key. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 Uname: Linux 5.10.1-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.snapd.rules Date: Tue Dec 22 15:44:43 2020 InstallationDate: Installed on 2020-05-05 (230 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.1-kernelorg-upstream-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:br1.4:efr1.4:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+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 1908991] Re: Compose key doesn't work after a while
** Attachment added: "lsinput" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+attachment/5445759/+files/lsinput.list -- 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/1908991 Title: Compose key doesn't work after a while Status in systemd package in Ubuntu: New Bug description: I attached my M-TECH keyboard to USB 2.0 hub connected to USB 2.0 port on my laptop. I also attached my mouse to the same hub. On kernels up to 5.9, compose key (which I defined as Right Super/Right Win) worked for a while, and then did not work (no accented letter inserted when typing right sequence). For example, instead of à I got `a. On 5.10 kernel (I reported this bug using custom-compiled 5.10.1 kernel), compose key does not work initially. The workaround is to open Tweaks and redefine compose key to the same key. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 Uname: Linux 5.10.1-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.snapd.rules Date: Tue Dec 22 15:44:43 2020 InstallationDate: Installed on 2020-05-05 (230 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.1-kernelorg-upstream-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:br1.4:efr1.4:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+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 1908991] Re: Compose key doesn't work after a while
** Attachment added: "xkbmap" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+attachment/5445760/+files/setxkbmap -- 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/1908991 Title: Compose key doesn't work after a while Status in systemd package in Ubuntu: New Bug description: I attached my M-TECH keyboard to USB 2.0 hub connected to USB 2.0 port on my laptop. I also attached my mouse to the same hub. On kernels up to 5.9, compose key (which I defined as Right Super/Right Win) worked for a while, and then did not work (no accented letter inserted when typing right sequence). For example, instead of à I got `a. On 5.10 kernel (I reported this bug using custom-compiled 5.10.1 kernel), compose key does not work initially. The workaround is to open Tweaks and redefine compose key to the same key. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 Uname: Linux 5.10.1-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.snapd.rules Date: Tue Dec 22 15:44:43 2020 InstallationDate: Installed on 2020-05-05 (230 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.1-kernelorg-upstream-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:br1.4:efr1.4:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+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 1908991] Re: Compose key doesn't work after a while
** Attachment added: "dmesg log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+attachment/5445757/+files/dmesg.log -- 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/1908991 Title: Compose key doesn't work after a while Status in systemd package in Ubuntu: New Bug description: I attached my M-TECH keyboard to USB 2.0 hub connected to USB 2.0 port on my laptop. I also attached my mouse to the same hub. On kernels up to 5.9, compose key (which I defined as Right Super/Right Win) worked for a while, and then did not work (no accented letter inserted when typing right sequence). For example, instead of à I got `a. On 5.10 kernel (I reported this bug using custom-compiled 5.10.1 kernel), compose key does not work initially. The workaround is to open Tweaks and redefine compose key to the same key. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 Uname: Linux 5.10.1-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.snapd.rules Date: Tue Dec 22 15:44:43 2020 InstallationDate: Installed on 2020-05-05 (230 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.1-kernelorg-upstream-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:br1.4:efr1.4:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+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 1908991] Re: Compose key doesn't work after a while
** Attachment added: "evtest log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+attachment/5445758/+files/evtest.event -- 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/1908991 Title: Compose key doesn't work after a while Status in systemd package in Ubuntu: New Bug description: I attached my M-TECH keyboard to USB 2.0 hub connected to USB 2.0 port on my laptop. I also attached my mouse to the same hub. On kernels up to 5.9, compose key (which I defined as Right Super/Right Win) worked for a while, and then did not work (no accented letter inserted when typing right sequence). For example, instead of à I got `a. On 5.10 kernel (I reported this bug using custom-compiled 5.10.1 kernel), compose key does not work initially. The workaround is to open Tweaks and redefine compose key to the same key. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 Uname: Linux 5.10.1-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.snapd.rules Date: Tue Dec 22 15:44:43 2020 InstallationDate: Installed on 2020-05-05 (230 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.1-kernelorg-upstream-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:br1.4:efr1.4:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+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 1908991] [NEW] Compose key doesn't work after a while
Public bug reported: I attached my M-TECH keyboard to USB 2.0 hub connected to USB 2.0 port on my laptop. I also attached my mouse to the same hub. On kernels up to 5.9, compose key (which I defined as Right Super/Right Win) worked for a while, and then did not work (no accented letter inserted when typing right sequence). For example, instead of à I got `a. On 5.10 kernel (I reported this bug using custom-compiled 5.10.1 kernel), compose key does not work initially. The workaround is to open Tweaks and redefine compose key to the same key. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 Uname: Linux 5.10.1-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.snapd.rules Date: Tue Dec 22 15:44:43 2020 InstallationDate: Installed on 2020-05-05 (230 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.1-kernelorg-upstream-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:br1.4:efr1.4:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908991 Title: Compose key doesn't work after a while Status in systemd package in Ubuntu: New Bug description: I attached my M-TECH keyboard to USB 2.0 hub connected to USB 2.0 port on my laptop. I also attached my mouse to the same hub. On kernels up to 5.9, compose key (which I defined as Right Super/Right Win) worked for a while, and then did not work (no accented letter inserted when typing right sequence). For example, instead of à I got `a. On 5.10 kernel (I reported this bug using custom-compiled 5.10.1 kernel), compose key does not work initially. The workaround is to open Tweaks and redefine compose key to the same key. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.3 Uname: Linux 5.10.1-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.snapd.rules Date: Tue Dec 22 15:44:43 2020 InstallationDate: Installed on 2020-05-05 (230 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.1-kernelorg-upstream-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:br1.4:efr1.4:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+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
