[Touch-packages] [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- 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/1931994 Title: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code Status in Ubuntu on IBM z Systems: Fix Committed Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Focal: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Released Bug description: Problem description: When passing a NULL key to reset AES EVC state, the state wouldn't be completely reset on s390x. https://github.com/openssl/openssl/pull/14900 Solution available here: https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8 Should be applied to all distros where openssl 1.1.1 is included for consistency reason. -> 21.10, 20.04, 18.04. I think not needed for 16.04 anymore [Test plan] $ sudo apt install libssl-dev $ gcc test.c -o evc-test -lcrypto -lssl # See https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for the test.c program $ ./evc-test && echo OK [Where problems could occur] This patch only touches s390x code paths, so there shouldn't be any regression on other architectures. However, on s390x this could reveal latent bugs by spreading a NULL key to new code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Do you need to update the sof-firmware apart from changing the kernel? -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
So, the overall steps would be make a clone of https://github.com/thesofproject/linux.git and run following commands ``` sudo apt install build-essential sudo apt-get build-dep linux-image-`uname -r` #(the running kernel) ``` and after that copied over current cofig Removed --> #CONFIG_SYSTEM_TRUSTED_KEYS sudo make menuconfig sudo make clean sudo make deb-pkg LOCALVERSION=-custom KDEB_PKGVERSION=$(make kernelversion) -1 Will this be sufficient -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1905285] Autopkgtest regression report (openssh/1:8.4p1-5ubuntu1.1)
All autopkgtests for the newly accepted openssh (1:8.4p1-5ubuntu1.1) for
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:
sshuttle/1.0.4-1ubuntu4 (s390x, ppc64el)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#openssh
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1905285
Title:
socket-activated sshd breaks on concurrent connections
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Focal:
Fix Committed
Status in openssh source package in Hirsute:
Fix Committed
Bug description:
[Impact]
Users of the systemd socket activated ssh service may experience a
race condition that may lead an ssh instance to fail.
The race condition happens when, for a running socket activated ssh
service,
an instance A is started, creating the RuntimeDirectory for the
service; then
an instance B is started, relying on the RuntimeDirectory created for
instance A; then
instance A halts, causing the RuntimeDirectory to be deleted.
If, at this point, instance B has not chrooted into RuntimeDirectory
yet, then instance B will fail.
The proposed patch fixes the issue by preserving the RuntimeDirectory
after an instance A of the socket activated ssh service halts.
[Test Plan]
1) Stop any running instances of ssh.
`systemctl stop ssh`
2) Start the socket activated ssh service.
`systemctl start ssh.socket`
3) Verify that no errors related to ssh were logged in /var/log/auth.log
`cat /var/log/auth.log | grep 'sshd.*fatal.*chroot.*No such file or
directory'`
4) perform several ssh connections to the running server in a short time
span. ssh-keyscan may help here.
`ssh-keyscan localhost`
5) Verify that errors related to ssh were logged in /var/log/auth.log
`cat /var/log/auth.log | grep 'sshd.*fatal.*chroot.*No such file or
directory'`
6) Apply the proposed fix (make sure the socket activated service is
restarted)
7) repead step (4), then verify that no new entries were appended to
the step (5) output
[Where problems could occur]
If the changes to the socket activated unit file are wrong, the socket
activated service may fail to start after the package upgrade. In this
case, we would need to instruct users to perform local changes to the
unit file with possible additional fixes while a new version of the
patch lands.
[racb] There might be cases where users are inadvertently depending on
the cleanup that will now be disabled - for example by a bug or
misconfiguration that would result in /run filling up otherwise. By
disabling systemd cleanup and relying solely on openssh for cleanup,
such a bug or misconfiguration may be exposed and cause problems on
such systems.
[Other Info]
This fix has been forwarded to Debian and accepted in
https://salsa.debian.org/ssh-team/openssh/-/merge_requests/12
[Original message]
This is mostly the same issue as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=934663.
With the default configuration of openssh-server and systemd, sshd
will complain and crash when multiple connections are made and
terminated in a quick succession, e.g. with `ssh-keyscan`. It results
in the following errors in /var/log/auth.log:
```
Nov 22 20:53:34 {host} sshd[14567]: Unable to negotiate with {client} port
41460: no matching host key type found. Their offer:
sk-ecdsa-sha2-nistp...@openssh.com [preauth]
Nov 22 20:53:34 {host} sshd[14570]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:34 {host} sshd[14569]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:34 {host} sshd[14568]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:34 {host} sshd[14566]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:47 {host} sshd[14584]: Connection closed by {client} port 59312
[preauth]
Nov 22 20:53:47 {host} sshd[14586]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:48 {host} sshd[14585]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
```
as well as e.g. missing responses in ssh-keyscan:
```
$ ssh-keyscan -vvv {host}
debug2: fd 3 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 2
debug2: fd 4 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 4
debug2: fd 5 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 8
debug2: fd 6 setting O_NONBLOCK
debug3: conalloc: oname
[Touch-packages] [Bug 1928989] Re: expiring trust anchor compatibility issue
Hello Dimitri, or anyone else affected, Accepted openssl into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.0.2g-1ubuntu4.20 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1928989 Title: expiring trust anchor compatibility issue Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Trusty: New Status in openssl source package in Xenial: Fix Committed Bug description: [Impact] * openssl fails to talk to letsencrypt website past September 2021, despite trusting the letsencrypt root certificate. [Test Plan] * Import staging cert equivalent to ISRG Root X1 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem * Import expired staging cert equivalen tto DST Root CA X3 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem * Test connectivity to the expired-root-ca test website https://expired-root-ca-test.germancoding.com setup: apt install openssl ca-certificates wget wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem cat letsencrypt-stg-root-x1.pem letsencrypt-stg-root-dst.pem >> ca.pem test case: openssl s_client -connect expired-root-ca-test.germancoding.com:443 -servername expired-root-ca-test.germancoding.com -verify 1 -verifyCAfile ca.pem bad result: connection failed verify depth is 1 CONNECTED(0003) depth=3 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Doctored Durian Root CA X3 verify error:num=10:certificate has expired notAfter=Jan 30 14:01:15 2021 GMT 140672978626200:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1264: good result: connection successful verify depth is 1 CONNECTED(0003) depth=2 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Pretend Pear X1 verify return:1 depth=1 C = US, O = (STAGING) Let's Encrypt, CN = (STAGING) Artificial Apricot R3 verify return:1 depth=0 CN = expired-root-ca-test.germancoding.com verify return:1 --- Certificate chain 0 s:/CN=expired-root-ca-test.germancoding.com i:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 1 s:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 2 s:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Doctored Durian Root CA X3 --- Server certificate -BEGIN CERTIFICATE- Connection should be successful and trusted with correctly working openssl s_client that can manage to ignore expired CA, and build a valid trust path using non-expired CA in the chain. [Testcase #2] $ sudo apt install ca-certificates wget faketime # Good connectivity $ wget -O /dev/null https://canonical.com --2021-07-13 11:54:20-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 30933 (30K) [text/html] Saving to: '/dev/null' /dev/null 100%[>] 30.21K --.-KB/sin 0.001s 2021-07-13 11:54:20 (22.3 MB/s) - '/dev/null' saved [30933/30933] # Jump to october to experience failure $ faketime
[Touch-packages] [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code
Hello bugproxy, or anyone else affected, Accepted openssl into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1931994 Title: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code Status in Ubuntu on IBM z Systems: In Progress Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Focal: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Released Bug description: Problem description: When passing a NULL key to reset AES EVC state, the state wouldn't be completely reset on s390x. https://github.com/openssl/openssl/pull/14900 Solution available here: https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8 Should be applied to all distros where openssl 1.1.1 is included for consistency reason. -> 21.10, 20.04, 18.04. I think not needed for 16.04 anymore [Test plan] $ sudo apt install libssl-dev $ gcc test.c -o evc-test -lcrypto -lssl # See https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for the test.c program $ ./evc-test && echo OK [Where problems could occur] This patch only touches s390x code paths, so there shouldn't be any regression on other architectures. However, on s390x this could reveal latent bugs by spreading a NULL key to new code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+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 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
So, I give this a try and attempted to reproduce the issue. I set up a VM acting as the KDC, and configured sshd in it with the following options: GSSAPIAuthentication yes GSSAPICleanupCredentials yes GSSAPIKeyExchange yes I then configured an LXD container to act as the krb5 client. I created a user "john" both in the KDC and in the client, then was able to verify that kinit was working fine. With that out of the way, I tried to connect via ssh to the KDC: $ ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex -o GSSAPIKeyExchange=yes krb5.test.lan The connection worked. I did the RH bug and tried to check if there was anything else I could do, but apparently the bug should have manifested with what I did. I also tried to start sshd by hand using the options you mentioned (plus "-o UsePam=yes"), to no avail. So I'm a bit lost here, and would also appreciate more info. Thanks. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1938144 Title: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange Status in openssh package in Ubuntu: Incomplete Bug description: I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and server) with the option "GSSAPIKeyExchange=yes", and this causes the connection to fail. The server has GSSAPI (Kerberos authentication) enabled, but is is only used for non-root users (root uses SSH keys). Client command: ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@server -v -p -o GSSAPIKeyExchange=yes Client log: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /home/user/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to compute-test [130.75.80.46] port . debug1: Connection established. debug1: identity file /home/rother/.ssh/id_rsa type 0 debug1: identity file /home/rother/.ssh/id_rsa-cert type -1 debug1: identity file /home/rother/.ssh/id_dsa type -1 debug1: identity file /home/rother/.ssh/id_dsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa type -1 debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519 type -1 debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_xmss type -1 debug1: identity file /home/rother/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400 debug1: Authenticating to server: as 'root' debug1: Offering GSSAPI proposal: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q== debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g== debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: Doing group exchange debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Received GSSAPI_COMPLETE debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Rekey has happened - updating saved versions debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent debug1: Will attempt key: /home/user/.ssh/id_dsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/user/.ssh/id_ed25519 debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk debug1: Will attempt key: /home/user/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO received debug1:
[Touch-packages] [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code
Hello bugproxy, or anyone else affected, Accepted openssl into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1f-1ubuntu2.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- 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/1931994 Title: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code Status in Ubuntu on IBM z Systems: In Progress Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: In Progress Status in openssl source package in Focal: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Released Bug description: Problem description: When passing a NULL key to reset AES EVC state, the state wouldn't be completely reset on s390x. https://github.com/openssl/openssl/pull/14900 Solution available here: https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8 Should be applied to all distros where openssl 1.1.1 is included for consistency reason. -> 21.10, 20.04, 18.04. I think not needed for 16.04 anymore [Test plan] $ sudo apt install libssl-dev $ gcc test.c -o evc-test -lcrypto -lssl # See https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for the test.c program $ ./evc-test && echo OK [Where problems could occur] This patch only touches s390x code paths, so there shouldn't be any regression on other architectures. However, on s390x this could reveal latent bugs by spreading a NULL key to new code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
Hello Dan, or anyone else affected, Accepted openssl into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1j-1ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-hirsute ** Tags added: verification-needed verification-needed-hirsute ** Tags removed: block-proposed-hirsute verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- 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/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Groovy: Fix Released Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Released Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 Test builds are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1931994] Re: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code
Hello bugproxy, or anyone else affected, Accepted openssl into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1j-1ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Summary changed: - [Ubuntu 20.04] OpenSSL bugs im s390x AES code + [Ubuntu 20.04] OpenSSL bugs in the s390x AES code ** Changed in: openssl (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- 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/1931994 Title: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code Status in Ubuntu on IBM z Systems: In Progress Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: In Progress Status in openssl source package in Focal: In Progress Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Released Bug description: Problem description: When passing a NULL key to reset AES EVC state, the state wouldn't be completely reset on s390x. https://github.com/openssl/openssl/pull/14900 Solution available here: https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8 Should be applied to all distros where openssl 1.1.1 is included for consistency reason. -> 21.10, 20.04, 18.04. I think not needed for 16.04 anymore [Test plan] $ sudo apt install libssl-dev $ gcc test.c -o evc-test -lcrypto -lssl # See https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for the test.c program $ ./evc-test && echo OK [Where problems could occur] This patch only touches s390x code paths, so there shouldn't be any regression on other architectures. However, on s390x this could reveal latent bugs by spreading a NULL key to new code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+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 1923845] Re: Please compress packages with zstd by default
This bug was fixed in the package diffoscope - 179
---
diffoscope (179) unstable; urgency=medium
* Ensure that various LLVM tools are installed, even when testing whether
a MacOS binary has zero differences when compared to itself.
(Closes: reproducible-builds/diffoscope#270)
-- Chris Lamb Fri, 30 Jul 2021 09:05:01 +0100
** Changed in: diffoscope (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Fix Released
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in reprepro source package in Focal:
Fix Released
Status in reprepro source package in Groovy:
Fix Released
Status in reprepro source package in Hirsute:
Fix Released
Status in debian-el package in Debian:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed
[Touch-packages] [Bug 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
** Package changed: linux (Ubuntu) => ubuntu-meta (Ubuntu) ** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938588 Title: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata Status in ubuntu-meta package in Ubuntu: New Bug description: We have several factory-fresh Mitac industrial motherboards (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we are unable to install Ubuntu Server 18.04.5 on. When we boot from the installation media we get the following error and the installation hangs (see attached screenshot, I've transcribed the error below too) ``` [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-241) ``` Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04. The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place. I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet). I have tried the following to modify the Ubuntu Server ISO, without success: 1- Adding the microcode to initrd --- I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https://www.kernel.org/doc/html/latest/x86/microcode.html to add the intel-microcode firmware to the image. Then I recompressed initrd.gz, and rebuild the ISO using xorisso. This did not have any effect: Ubuntu Server still encountered the same error when trying to install. 2- Using initrd from Ubuntu Desktop 18.04.5 -- I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again. The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session. At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it. If you need any additional information/logs/etc... please let me know and I'll be happy to provide them. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1938588/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Thanks @mblack154 its working now. -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1938588] [NEW] Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
You have been subscribed to a public bug: We have several factory-fresh Mitac industrial motherboards (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we are unable to install Ubuntu Server 18.04.5 on. When we boot from the installation media we get the following error and the installation hangs (see attached screenshot, I've transcribed the error below too) ``` [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-241) ``` Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04. The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place. I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet). I have tried the following to modify the Ubuntu Server ISO, without success: 1- Adding the microcode to initrd --- I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https://www.kernel.org/doc/html/latest/x86/microcode.html to add the intel-microcode firmware to the image. Then I recompressed initrd.gz, and rebuild the ISO using xorisso. This did not have any effect: Ubuntu Server still encountered the same error when trying to install. 2- Using initrd from Ubuntu Desktop 18.04.5 -- I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again. The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session. At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it. If you need any additional information/logs/etc... please let me know and I'll be happy to provide them. Thanks! ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment intel-microcode kernel-bug ubuntu-server -- Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata https://bugs.launchpad.net/bugs/1938588 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta 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 1905285] Re: socket-activated sshd breaks on concurrent connections
Hello Marcin, or anyone else affected,
Accepted openssh into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.2p1-4ubuntu0.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: openssh (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1905285
Title:
socket-activated sshd breaks on concurrent connections
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Focal:
Fix Committed
Status in openssh source package in Hirsute:
Fix Committed
Bug description:
[Impact]
Users of the systemd socket activated ssh service may experience a
race condition that may lead an ssh instance to fail.
The race condition happens when, for a running socket activated ssh
service,
an instance A is started, creating the RuntimeDirectory for the
service; then
an instance B is started, relying on the RuntimeDirectory created for
instance A; then
instance A halts, causing the RuntimeDirectory to be deleted.
If, at this point, instance B has not chrooted into RuntimeDirectory
yet, then instance B will fail.
The proposed patch fixes the issue by preserving the RuntimeDirectory
after an instance A of the socket activated ssh service halts.
[Test Plan]
1) Stop any running instances of ssh.
`systemctl stop ssh`
2) Start the socket activated ssh service.
`systemctl start ssh.socket`
3) Verify that no errors related to ssh were logged in /var/log/auth.log
`cat /var/log/auth.log | grep 'sshd.*fatal.*chroot.*No such file or
directory'`
4) perform several ssh connections to the running server in a short time
span. ssh-keyscan may help here.
`ssh-keyscan localhost`
5) Verify that errors related to ssh were logged in /var/log/auth.log
`cat /var/log/auth.log | grep 'sshd.*fatal.*chroot.*No such file or
directory'`
6) Apply the proposed fix (make sure the socket activated service is
restarted)
7) repead step (4), then verify that no new entries were appended to
the step (5) output
[Where problems could occur]
If the changes to the socket activated unit file are wrong, the socket
activated service may fail to start after the package upgrade. In this
case, we would need to instruct users to perform local changes to the
unit file with possible additional fixes while a new version of the
patch lands.
[racb] There might be cases where users are inadvertently depending on
the cleanup that will now be disabled - for example by a bug or
misconfiguration that would result in /run filling up otherwise. By
disabling systemd cleanup and relying solely on openssh for cleanup,
such a bug or misconfiguration may be exposed and cause problems on
such systems.
[Other Info]
This fix has been forwarded to Debian and accepted in
https://salsa.debian.org/ssh-team/openssh/-/merge_requests/12
[Original message]
This is mostly the same issue as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=934663.
With the default configuration of openssh-server and systemd, sshd
will complain and crash when multiple connections are made and
terminated in a quick succession, e.g. with `ssh-keyscan`. It results
in the following errors in /var/log/auth.log:
```
Nov 22 20:53:34 {host} sshd[14567]: Unable to negotiate with {client} port
41460: no matching host key type found. Their offer:
sk-ecdsa-sha2-nistp...@openssh.com [preauth]
Nov 22 20:53:34 {host} sshd[14570]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:34 {host} sshd[14569]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:34 {host} sshd[14568]: fatal: chroot("/run/sshd"): No such file
or
[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names
I think it would be good to write a release note entry about this change for Ubuntu 21.10 and possibly updating the release notes for Ubuntu 20.04.3 (if these changes make it there in time). ** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in Release Notes for Ubuntu: New Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Focal: Fix Committed Status in shadow source package in Groovy: Won't Fix Status in shadow source package in Hirsute: Fix Committed Status in shadow source package in Impish: Fix Released Bug description: [Impact] * If a fully numeric username is created, it will cause problems with systemd. One example is that the user with this type of name can log in, but loginctl will not create a session for them. * This can also cause users to be unable to log in to a gdm environment [Test Case] * `useradd 123` (this command should succeed) * `userdel 123` to clean up the user that was just added * Install `shadow` from -proposed * `useradd 123` should now fail [Regression Potential] * If there were a logic error in the fix, it is possible that valid usernames would now be disallowed. * Many test cases have been added to ensure this is not the case, and --badnames would still provide a work-around * [racb] Users may have scripts that are currently using numeric usernames and these scripts will break as a consequence of this deliberate change in stable Ubuntu releases. However, based on the discussion in the bug, we think this is preferable to leaving such users with unstable behaviour such as systemd's behaviour described. [Original Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1927078/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
yes i did. I am doing it all over again just in case if i miss anything. Thank you for the advise @mblack154 -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1905285] Re: socket-activated sshd breaks on concurrent connections
Hello Marcin, or anyone else affected,
Accepted openssh into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openssh/1:8.4p1-5ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: openssh (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1905285
Title:
socket-activated sshd breaks on concurrent connections
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Focal:
In Progress
Status in openssh source package in Hirsute:
Fix Committed
Bug description:
[Impact]
Users of the systemd socket activated ssh service may experience a
race condition that may lead an ssh instance to fail.
The race condition happens when, for a running socket activated ssh
service,
an instance A is started, creating the RuntimeDirectory for the
service; then
an instance B is started, relying on the RuntimeDirectory created for
instance A; then
instance A halts, causing the RuntimeDirectory to be deleted.
If, at this point, instance B has not chrooted into RuntimeDirectory
yet, then instance B will fail.
The proposed patch fixes the issue by preserving the RuntimeDirectory
after an instance A of the socket activated ssh service halts.
[Test Plan]
1) Stop any running instances of ssh.
`systemctl stop ssh`
2) Start the socket activated ssh service.
`systemctl start ssh.socket`
3) Verify that no errors related to ssh were logged in /var/log/auth.log
`cat /var/log/auth.log | grep 'sshd.*fatal.*chroot.*No such file or
directory'`
4) perform several ssh connections to the running server in a short time
span. ssh-keyscan may help here.
`ssh-keyscan localhost`
5) Verify that errors related to ssh were logged in /var/log/auth.log
`cat /var/log/auth.log | grep 'sshd.*fatal.*chroot.*No such file or
directory'`
6) Apply the proposed fix (make sure the socket activated service is
restarted)
7) repead step (4), then verify that no new entries were appended to
the step (5) output
[Where problems could occur]
If the changes to the socket activated unit file are wrong, the socket
activated service may fail to start after the package upgrade. In this
case, we would need to instruct users to perform local changes to the
unit file with possible additional fixes while a new version of the
patch lands.
[racb] There might be cases where users are inadvertently depending on
the cleanup that will now be disabled - for example by a bug or
misconfiguration that would result in /run filling up otherwise. By
disabling systemd cleanup and relying solely on openssh for cleanup,
such a bug or misconfiguration may be exposed and cause problems on
such systems.
[Other Info]
This fix has been forwarded to Debian and accepted in
https://salsa.debian.org/ssh-team/openssh/-/merge_requests/12
[Original message]
This is mostly the same issue as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=934663.
With the default configuration of openssh-server and systemd, sshd
will complain and crash when multiple connections are made and
terminated in a quick succession, e.g. with `ssh-keyscan`. It results
in the following errors in /var/log/auth.log:
```
Nov 22 20:53:34 {host} sshd[14567]: Unable to negotiate with {client} port
41460: no matching host key type found. Their offer:
sk-ecdsa-sha2-nistp...@openssh.com [preauth]
Nov 22 20:53:34 {host} sshd[14570]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:34 {host} sshd[14569]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:34 {host} sshd[14568]: fatal:
[Touch-packages] [Bug 1938584] Re: [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card
I just checked it: I could show a newscast from France 24. Both audio and video worked * with firefox * with an alternatively snap-installed Chromium browser. On my trials mentioned above, I also used Version 92.0.4515.107 (Offizieller Build) snap (64-Bit). I thought to have installed it the apt install way, but possibly this is also just another way to really get a snap packet. I was not aware of that. What I could not test that way: On my target system, I uninstalled firefox since I only need one browser. Installing something else is possible on a live system (albeit the installation is only present until shutdown). However, it is only possible as installing does not alter any kernel component which apparently happens sometimes when updating requires a reboot. Anyway: Would it make sense to copy system files from the live system (via a USB stick or directly by mounting the Linux system partition)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1938584 Title: [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: This problem came up after installing Xubuntu 20.04.02 on this computer, which used Xubuntu 18.04 before. Ifter installing the system, I installed some programs, among them Sound Switcher Indicator 2.3.6 and I unistalled firefox after I had installed Chromium instead. My first test of Audio/Video: When streaming e.g. from https://www.france24.com/fr/direct, I can see the video part but I hear nothing. I am sure that the loudspeaker is not muted. pavucontrol shows me a blue slider switch. Its tab "playback" shows a varying Chromium playback indicator and the associated fader has influence on the amplitude of the shown intensity. (Note: I am using a German version so my transaltions of the items might be off a bit, still I hpe that it can be understood). I have no HDMI cable connected to the computer and no USB-sound device is plugged into it. The laptop has an internal microphone and an internal loudspeaker. In pavucontrol's tab "output devices" it shows something like "no output devices available" when "only hardware devices" are selected there. In pavucontrol's tab "configuration" I can select nothing. I am quite confident that this is not a hardware bug, because the audio system worked before I upgraded to Xubuntu 20.04.02. I also tried alsamixer. in F2 it offers two cards: 0: PCH and 1: HDMI. When I type 0 there to select the PCH one, nothing happens. If I type 1, nothing happens either (I expected the latter since there is no HDMI-device connected). In the levels above, one of the offered items is highlighted and the selection can be moved by up or down. Most of the files in /proc/asound are empty: $ ls -l /proc/asound insgesamt 0 dr-xr-xr-x 6 root root 0 2021-07-30 17:46 card0 dr-xr-xr-x 6 root root 0 2021-07-30 17:46 card1 -r--r--r-- 1 root root 0 2021-07-30 17:46 cards -r--r--r-- 1 root root 0 2021-07-30 17:46 devices lrwxrwxrwx 1 root root 5 2021-07-30 17:46 HDMI -> card1 -r--r--r-- 1 root root 0 2021-07-30 17:46 hwdep -r--r--r-- 1 root root 0 2021-07-30 17:46 modules dr-xr-xr-x 4 root root 0 2021-07-30 17:46 oss lrwxrwxrwx 1 root root 5 2021-07-30 17:46 PCH -> card0 -r--r--r-- 1 root root 0 2021-07-30 17:46 pcm dr-xr-xr-x 6 root root 0 2021-07-30 17:46 seq -r--r--r-- 1 root root 0 2021-07-30 17:46 timers -r--r--r-- 1 root root 0 2021-07-30 17:46 version Probably this will give a hint (perhaps it is also visible from the automatically collected information). I think I had tried the sound system with the live stick before installation. But I'll repeat that test again and tell you the outcome. Kind regards melolontha ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 30 17:08:50 2021 InstallationDate: Installed on 2021-07-28 (1 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
Re: [Touch-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Did you clone the src files from here? https://github.com/thesofproject/linux.git On 7/30/21 1:34 PM, Raish khaitu wrote: > I am getting this error @mblack154: > > BTF: .tmp_vmlinux.btf: pahole (pahole) is not available > Failed to generate BTF for vmlinux > Try to disable CONFIG_DEBUG_INFO_BTF > make[3]: *** [Makefile:1177: vmlinux] Error 1 > make[2]: *** [debian/rules:7: build-arch] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 > make[1]: *** [scripts/Makefile.package:77: deb-pkg] Error 2 > make: *** [Makefile:1560: deb-pkg] Error 2 > > > Any advise would be helpful. should i just try and disable BTF? > -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
I am getting this error @mblack154: BTF: .tmp_vmlinux.btf: pahole (pahole) is not available Failed to generate BTF for vmlinux Try to disable CONFIG_DEBUG_INFO_BTF make[3]: *** [Makefile:1177: vmlinux] Error 1 make[2]: *** [debian/rules:7: build-arch] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 make[1]: *** [scripts/Makefile.package:77: deb-pkg] Error 2 make: *** [Makefile:1560: deb-pkg] Error 2 Any advise would be helpful. should i just try and disable BTF? -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
** Changed in: lxd (Ubuntu) Status: New => Invalid ** Changed in: iptables (Ubuntu) Status: New => Invalid ** Changed in: launchpad-buildd Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Bug description: when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1938585] Re: sysctl.d file is misnamed and unneeded
For clarity, I explicitly added SRU release targets and marked them as either invalid (for bionic, since the file doesn't exist there) or wont- fix (as explained in the description). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1938585 Title: sysctl.d file is misnamed and unneeded Status in procps package in Ubuntu: In Progress Status in procps source package in Bionic: Invalid Status in procps source package in Focal: Invalid Status in procps source package in Hirsute: Won't Fix Status in procps source package in Impish: In Progress Bug description: [impact] the sysctl.d file /usr/lib/sysctl.d/protect-links.conf is misnamed, due to lacking the expected leading number to order it. This results in it being evaluated after all other number-prefixed conf files, effectively overriding any conflicting configuration in the other files, including any admin-provided files in /etc/sysctl.d. Additionally, this file should not be included at all, as (unlike Debian) Ubuntu assumes systemd will always be installed, thus the sysctl settings from this file will be provided by the systemd- provided sysctl config files. [test case] create a file, e.g. /etc/sysctl.d/99-test.conf, with any config that also exists in /usr/lib/sysctl.d/protect-links.conf but with a different setting, and reboot, then check which value was used. [regression potential] any regression would likely result in incorrect or unexpected values for the sysctls contained in this conf file [scope] this is needed in f and later this file is not present in b however, see other info [other info] while this bug exists in f and later, it's also trivial to work around it (though not obvious) by renaming the manual configuration file, e.g. instead of using /etc/sysctl.d/99-custom.conf a local admin should instead use /etc/sysctl.d/z-custom.conf so the custom file is lexically after 'protect-links.conf'. Since removing the file entirely could result in a change in behavior, if the local admin has explicitly modified the file or taken other steps, and since it's trivial (though again, not obvious) to override the file lexically, this seems like it should not be SRUed, but only fixed in the development release. Also, since Debian's policy does allow for systems that do *not* use systemd, I'm not opening a bug against Debian to remove the file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1938585/+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 1938585] [NEW] sysctl.d file is misnamed and unneeded
Public bug reported: [impact] the sysctl.d file /usr/lib/sysctl.d/protect-links.conf is misnamed, due to lacking the expected leading number to order it. This results in it being evaluated after all other number-prefixed conf files, effectively overriding any conflicting configuration in the other files, including any admin-provided files in /etc/sysctl.d. Additionally, this file should not be included at all, as (unlike Debian) Ubuntu assumes systemd will always be installed, thus the sysctl settings from this file will be provided by the systemd-provided sysctl config files. [test case] create a file, e.g. /etc/sysctl.d/99-test.conf, with any config that also exists in /usr/lib/sysctl.d/protect-links.conf but with a different setting, and reboot, then check which value was used. [regression potential] any regression would likely result in incorrect or unexpected values for the sysctls contained in this conf file [scope] this is needed in f and later this file is not present in b however, see other info [other info] while this bug exists in f and later, it's also trivial to work around it (though not obvious) by renaming the manual configuration file, e.g. instead of using /etc/sysctl.d/99-custom.conf a local admin should instead use /etc/sysctl.d/z-custom.conf so the custom file is lexically after 'protect-links.conf'. Since removing the file entirely could result in a change in behavior, if the local admin has explicitly modified the file or taken other steps, and since it's trivial (though again, not obvious) to override the file lexically, this seems like it should not be SRUed, but only fixed in the development release. Also, since Debian's policy does allow for systems that do *not* use systemd, I'm not opening a bug against Debian to remove the file. ** Affects: procps (Ubuntu) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: procps (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Affects: procps (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: procps (Ubuntu Hirsute) Importance: Undecided Status: Won't Fix ** Affects: procps (Ubuntu Impish) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: procps (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: procps (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: procps (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: procps (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: procps (Ubuntu Bionic) Status: New => Invalid ** Changed in: procps (Ubuntu Focal) Status: New => Invalid ** Changed in: procps (Ubuntu Hirsute) Status: New => Won't Fix ** Changed in: procps (Ubuntu Impish) Status: New => In Progress ** Changed in: procps (Ubuntu Impish) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: procps (Ubuntu Impish) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1938585 Title: sysctl.d file is misnamed and unneeded Status in procps package in Ubuntu: In Progress Status in procps source package in Bionic: Invalid Status in procps source package in Focal: Invalid Status in procps source package in Hirsute: Won't Fix Status in procps source package in Impish: In Progress Bug description: [impact] the sysctl.d file /usr/lib/sysctl.d/protect-links.conf is misnamed, due to lacking the expected leading number to order it. This results in it being evaluated after all other number-prefixed conf files, effectively overriding any conflicting configuration in the other files, including any admin-provided files in /etc/sysctl.d. Additionally, this file should not be included at all, as (unlike Debian) Ubuntu assumes systemd will always be installed, thus the sysctl settings from this file will be provided by the systemd- provided sysctl config files. [test case] create a file, e.g. /etc/sysctl.d/99-test.conf, with any config that also exists in /usr/lib/sysctl.d/protect-links.conf but with a different setting, and reboot, then check which value was used. [regression potential] any regression would likely result in incorrect or unexpected values for the sysctls contained in this conf file [scope] this is needed in f and later this file is not present in b however, see other info [other info] while this bug exists in f and later, it's also trivial to work around it (though not obvious) by renaming the manual configuration file, e.g. instead of using /etc/sysctl.d/99-custom.conf a local admin should instead use /etc/sysctl.d/z-custom.conf so the custom file is lexically after
[Touch-packages] [Bug 1938584] [NEW] [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: This problem came up after installing Xubuntu 20.04.02 on this computer, which used Xubuntu 18.04 before. Ifter installing the system, I installed some programs, among them Sound Switcher Indicator 2.3.6 and I unistalled firefox after I had installed Chromium instead. My first test of Audio/Video: When streaming e.g. from https://www.france24.com/fr/direct, I can see the video part but I hear nothing. I am sure that the loudspeaker is not muted. pavucontrol shows me a blue slider switch. Its tab "playback" shows a varying Chromium playback indicator and the associated fader has influence on the amplitude of the shown intensity. (Note: I am using a German version so my transaltions of the items might be off a bit, still I hpe that it can be understood). I have no HDMI cable connected to the computer and no USB-sound device is plugged into it. The laptop has an internal microphone and an internal loudspeaker. In pavucontrol's tab "output devices" it shows something like "no output devices available" when "only hardware devices" are selected there. In pavucontrol's tab "configuration" I can select nothing. I am quite confident that this is not a hardware bug, because the audio system worked before I upgraded to Xubuntu 20.04.02. I also tried alsamixer. in F2 it offers two cards: 0: PCH and 1: HDMI. When I type 0 there to select the PCH one, nothing happens. If I type 1, nothing happens either (I expected the latter since there is no HDMI- device connected). In the levels above, one of the offered items is highlighted and the selection can be moved by up or down. Most of the files in /proc/asound are empty: $ ls -l /proc/asound insgesamt 0 dr-xr-xr-x 6 root root 0 2021-07-30 17:46 card0 dr-xr-xr-x 6 root root 0 2021-07-30 17:46 card1 -r--r--r-- 1 root root 0 2021-07-30 17:46 cards -r--r--r-- 1 root root 0 2021-07-30 17:46 devices lrwxrwxrwx 1 root root 5 2021-07-30 17:46 HDMI -> card1 -r--r--r-- 1 root root 0 2021-07-30 17:46 hwdep -r--r--r-- 1 root root 0 2021-07-30 17:46 modules dr-xr-xr-x 4 root root 0 2021-07-30 17:46 oss lrwxrwxrwx 1 root root 5 2021-07-30 17:46 PCH -> card0 -r--r--r-- 1 root root 0 2021-07-30 17:46 pcm dr-xr-xr-x 6 root root 0 2021-07-30 17:46 seq -r--r--r-- 1 root root 0 2021-07-30 17:46 timers -r--r--r-- 1 root root 0 2021-07-30 17:46 version Probably this will give a hint (perhaps it is also visible from the automatically collected information). I think I had tried the sound system with the live stick before installation. But I'll repeat that test again and tell you the outcome. Kind regards melolontha ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 30 17:08:50 2021 InstallationDate: Installed on 2021-07-28 (1 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2011 dmi.bios.release: 21.0 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2100V2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 21.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2100V2:bd08/24/2011:br21.0:efr21.0:svnSonyCorporation:pnVPCCA3S1E:pvrC609VVH0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCCA3S1E dmi.product.sku: N/A dmi.product.version: C609VVH0 dmi.sys.vendor: Sony Corporation ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1938584 Title: [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: This problem came up after installing Xubuntu 20.04.02 on this computer, which used Xubuntu 18.04 before. Ifter installing the system, I installed some programs, among them Sound Switcher Indicator 2.3.6 and I unistalled firefox
Re: [Touch-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Had to compile with: copied over current cofig Removed --> #CONFIG_SYSTEM_TRUSTED_KEYS sudo make menuconfig sudo make clean sudo make deb-pkg LOCALVERSION=-custom KDEB_PKGVERSION=$(make kernelversion)-1 Then installed the deb files. Let me know if this works. Michael On 7/30/21 10:17 AM, Raish khaitu wrote: > @mblack154 How did you resolve this issue: > arch/x86/Makefile:148: CONFIG_X86_X32 enabled but no binutils support > sed: can't read modules.order: No such file or directory > make: *** [Makefile:1485: __modinst_pre] Error 2 > > i am still stuck here even after running these: > sudo apt install build-essential > sudo apt-get build-dep linux-image- (the running kernel) > -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1933530] Re: Translation error with accentuation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: language-pack-pt-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1933530 Title: Translation error with accentuation Status in language-pack-pt-base package in Ubuntu: Confirmed Bug description: An alert is issued when the snap is called ```sh # LANG=pt_BR snap refresh 2021/05/30 22:22:17.293001 main.go:176: description of prepare-image's "" is lowercase: "o directório de destino" Todos os snaps atualizados. ```sh In en_US works as expected ```sh # LANG=en_US snap refresh All snaps up to date. ``` Patch Attached Change line 4581 of data/pt/LC_MESSAGES/snappy.po ``` -msgstr "o directório de destino" +msgstr "O directório de destino" ``` Bug cross posted in https://bugs.launchpad.net/snappy/+bug/1930175 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1933530/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
@mblack154 How did you resolve this issue: arch/x86/Makefile:148: CONFIG_X86_X32 enabled but no binutils support sed: can't read modules.order: No such file or directory make: *** [Makefile:1485: __modinst_pre] Error 2 i am still stuck here even after running these: sudo apt install build-essential sudo apt-get build-dep linux-image- (the running kernel) -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1920813] Re: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session required pam_loginuid.so" for compatibility with user applications
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1920813 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1920813 Title: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session requiredpam_loginuid.so" for compatibility with user applications Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.04 2. Launch MATE Terminal 3. Execute `cat /proc/self/loginuid` Expected results: * above command returned 1000 Actual results: * above command returned 4294967295 Remediation: * edit /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin to uncomment session requiredpam_loginuid.so for compatibility with user applications. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 22 22:41:05 2021 InstallationDate: Installed on 2021-03-21 (1 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1920813/+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 1920813] Re: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session required pam_loginuid.so" for compatibility with user applications
** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1920813 Title: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session requiredpam_loginuid.so" for compatibility with user applications Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.04 2. Launch MATE Terminal 3. Execute `cat /proc/self/loginuid` Expected results: * above command returned 1000 Actual results: * above command returned 4294967295 Remediation: * edit /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin to uncomment session requiredpam_loginuid.so for compatibility with user applications. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 22 22:41:05 2021 InstallationDate: Installed on 2021-03-21 (1 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1920813/+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 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
** Tags removed: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" Status in Ubuntu MATE: New Status in ayatana-indicator-power package in Ubuntu: Confirmed Status in indicator-power package in Ubuntu: Confirmed Status in mate-indicator-applet package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Click on the battery indicator. 2. Click "Show Percentage on Menu Bar" to enable it. 3. Do it again to disable it. 4. Battery indicator disappears Output from dmesg: [ 613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000] [ 749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000] [ 775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000] [ 816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000] [ 841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+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 1934941] Re: Xorg freeze
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1934941 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: hello developers when I start my ubantu after entering passward somentimes when I open the screen divided into 4 screen and starts blinking for that I have to restart the computer. It does not happens daily but it sucks when happens. I have also problem in my blutooth it disconnect after sometimes of connect and once disconnect you can not connect again . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 02:47:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2021-07-03 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=20708d08-341d-4530-803a-7e28abc56637 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.release: 15.109 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 33.71 dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/23/2014:br15.109:efr33.71:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1934941/+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 1938053] Re: HDMI Problem
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1938053 Title: HDMI Problem Status in xorg package in Ubuntu: New Bug description: Cannot connect second monitor with hdmi after update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 26 17:49:36 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics [1462:12c1] InstallationDate: Installed on 2021-06-05 (50 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Micro-Star International Co., Ltd. Modern 14 B10MW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=375930f6-29d7-4278-861a-7bf26f514a10 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2020 dmi.bios.release: 1.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14D1IMS.10B dmi.board.asset.tag: Default string dmi.board.name: MS-14D1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14D1IMS.10B:bd12/22/2020:br1.11:svnMicro-StarInternationalCo.,Ltd.:pnModern14B10MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14D1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Modern dmi.product.name: Modern 14 B10MW dmi.product.sku: 14D1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1938053/+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 1938249] Re: Xorg freeze
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1938249 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: my system very frequently hang or crash when i establish internet connection. please ubuntu support help me to fix this problem. thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 28 10:05:05 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610/M74 [Mobility Radeon HD 2400 XT] [1002:94c8] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] RV610/M74 [Mobility Radeon HD 2400 XT] [1025:012f] MachineType: Acer Volvi ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=UUID=3517ff6d-a96d-4899-96e2-8dfde5a99c61 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.14 dmi.board.name: Volvi dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.14:bd11/05/2007:svnAcer:pnVolvi:pvr0100:rvnAcer:rnVolvi:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Volvi dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jul 28 09:57:43 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1938249/+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 1888042] Re: Qualcomm Atheros QCA6174
** Changed in: ubuntu-mate Status: New => Incomplete ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1888042 Title: Qualcomm Atheros QCA6174 Status in Ubuntu MATE: Incomplete Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: On Ubuntu Mate 20 (and also Linux Mint 20) Ping over lan wireless result: icmp_seq=1 Destination Host Unreachable Network card Wireless Qualcomm Atheros QCA6174 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1888042/+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 1884303] Re: LAN printing hell on 20.04 (UPnP VS mDNS? Or maybe IPv4 vs IPv6??)
** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1884303 Title: LAN printing hell on 20.04 (UPnP VS mDNS? Or maybe IPv4 vs IPv6??) Status in Ubuntu MATE: New Status in cups package in Ubuntu: New Bug description: Hello, I have been experiencing this problem for at least 2 LTS versions I believe and it concerns and issue with a LAN printer. I am still not quite too sure if it involves a happy mix-up of TCPvsmDNSvsuPnP and|or if it's a lpstat VS GUI binary setting and|or ?? Anyways, when using 20.04 fully patched(and also possibly not) while using a LAN printer there seems to be a "duplicated-corrupted entry" that ends up somewhat generated in the system. For example: $ lpstat -p printer Samsung_C460_Series_SEC30CDA7A49F15_ now printing Samsung_C460_Series_SEC30CDA7A49F15_-12. enabled since Fri 19 Jun 2020 01:09:47 PM $ And MATE agrees with that (See attachment "1.jpg") But when using Atril (See "2.jpg") or LOWriter (See "3.jpg") (or any other binary such as firefox) the story isn't so clear. That brought me back to this: $ lpstat -p lpstat: No destinations added. $ And MATE still agrees with that (See "4.jpg") Yet LOWriter (and co) seemed a bit still challenged (See "5.jpg") Anyways, time to delete everything and readd. But why are there 2x choices? (See "6.jpg") Looking carefully at both entries, I believe that one is the TCP socket (See "7.jpg") while the 2nd one is via SSDP/UPnP (See "8.jpg"). But anyways, I always go for the TCP entry and that's done (See "9.jpg"). $ lpstat -p 1 ↵ printer Samsung-C460 is idle. enabled since Fri 19 Jun 2020 02:36:42 PM $ And MATE again agrees (See "10.jpg") Yaaay! Time to print out that SOB, so let's go back into Atril and print it (See "11.jpg") Nothing surprising there: the old ghosted/MAC addressed profile still shows. But did printing on the newly added via TCP one actually worked? YES! This time it did. Why this time? Because in other times it will just die in the spoiler and have me started back at the very beginning of this ticket. Also, a major point of interest is: after having readded the printer, notice how lpstat named it, it was "Samsung-C460". Well, if/when I'll reboot the system, that simple name will be gone and will have been changed to "Samsung-C460-Series-SEC30CDA7A49F15" while still showing this "Samsung_C460_Series_SEC30CDA7A49F15_" ghost. From the printer's perspective, here is what's opened on it: PORT STATE SERVICE VERSION 80/tcpopen httpSamsung SyncThru Web Service |_http-favicon: Unknown favicon MD5: 10E320BB701D0D099E175B6C339958F9 | http-methods: |_ Supported Methods: GET POST | http-robots.txt: 1 disallowed entry |_* |_http-title: Site doesn't have a title (text/html; charset=utf-8). 427/tcp open svrloc? 515/tcp open printer? | fingerprint-strings: | TerminalServerCookie: |_PortThru lpd: No Jobs on this queue 631/tcp open httpSamsung SyncThru Web Service |_http-favicon: Unknown favicon MD5: 10E320BB701D0D099E175B6C339958F9 | http-methods: |_ Supported Methods: GET POST |_http-title: Site doesn't have a title (text/html; charset=utf-8). 5200/tcp open targus-getdata? | fingerprint-strings: | DNSStatusRequestTCP, DNSVersionBindReqTCP, FourOhFourRequest, GenericLines, GetRequest, HTTPOptions, Help, Kerberos, LDAPSearchReq, LPDString, RPCCheck, RTSPRequest, SMBProgNeg, SSLSessionReq, TLSSessionReq, TerminalServerCookie, X11Probe: | HTTP/1.1 405 Method Not Allowed | Connection: close |_Server: ESWeb/0.5 9100/tcp open jetdirect? 10001/tcp open scp-config? Here's what /var/log/cups/error_log as to say about all of this: E [19/Jun/2020:00:00:00 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [19/Jun/2020:13:02:02 -0400] [Job 10] File \'\' not found E [19/Jun/2020:13:05:58 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [19/Jun/2020:13:08:09 -0400] [Job 11] No destination host name supplied by cups-browsed for printer \"Samsung_C460_Series_SEC30CDA7A49F15_\", is cups-browsed running? E [19/Jun/2020:13:08:39 -0400] [Job 12] No destination host name supplied by cups-browsed for printer \"Samsung_C460_Series_SEC30CDA7A49F15_\", is cups-browsed running? E [19/Jun/2020:13:09:58 -0400] [Client 2371] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/11) from localhost. E [19/Jun/2020:13:09:58 -0400] [Client 2493] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/11) from
[Touch-packages] [Bug 1888125] Re: refreshing cache stuck in ubuntu mate 20.04
** Changed in: ubuntu-mate Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1888125 Title: refreshing cache stuck in ubuntu mate 20.04 Status in Ubuntu MATE: Incomplete Status in software-properties package in Ubuntu: Incomplete Bug description: i have a very annoying bug which is refreshing cache is just not closing only if i rebooted the system! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1888125/+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 1898771] Re: suspend does not lock screen Fresh Ubuntu Mate 20.04.1
** Tags removed: lightdm lock security suspend unlock ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1898771 Title: suspend does not lock screen Fresh Ubuntu Mate 20.04.1 Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: New Bug description: When suspending my freshly installed 20.04.1 system I noticed that on waking a password is not required. lightdm does not have locking enabled on suspend. A workaround I found from pszafer on archlinux blog. Quoted below: create lockscreen.sh file somewhere in your home directory with: #!/bin/sh XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" dm-tool lock - I've prefer just for sure creating dmlock.service file in home dir and create symlink to /etc/systemd/system. File has to be in /etc/systemd/system/dmlock.service [Unit] Description=DM Lock before sleep Before=sleep.target [Service] ExecStart=/home/user/dir/lockscreen.sh [Install] WantedBy=sleep.target For your needs, you probably need hibernate.target. Next run following commands: systemctl daemon-reload systemctl enable dmlock.service Just for sure it is working you could run: systemctl list-unit-files systemctl start dmlock.service Hope it helps you a little To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1898771/+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 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04
** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Also affects: mate-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1906138 Title: Indeterminate Qt progress bars don't display properly in 20.04 Status in Ubuntu MATE: New Status in mate-themes package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar (meaning its minimum and maximum values have both been set to zero) does not display properly. It is supposed to animate in a way that shows that something is happening with an unknown time remaining. Instead, it sits still with its progress bar showing approximately 25 to 30% progress. To test this, make a simple Qt program with a QProgressBar in the main window, and add these lines to the constructor of the main window: ui->progressBar->setMinimum(0); ui->progressBar->setMaximum(0); This problem is not present in standard Ubuntu 20.04. Standard Ubuntu correctly animates the indeterminate progress bar. It's unclear to me which package is at fault, but it seems to be something specific to Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem. Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it doesn't have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1906138/+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 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
Hello Niklas! You're welcome again. Thanks for adding more information... Good to know we can put Ansible apart from this. Anyway, we would need more information about the Kerberos configuration you mentioned before as you noticed it is involved because we don't have the complete picture to reproduce the issue. Also sshd configuration is needed for both client and server. In the time we receive that, I will mark the report as "Incomplete", but thanks a lot for progressing on it. When you submit new information, please mark the bug as "New" so we can continue with it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1938144 Title: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange Status in openssh package in Ubuntu: New Bug description: I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and server) with the option "GSSAPIKeyExchange=yes", and this causes the connection to fail. The server has GSSAPI (Kerberos authentication) enabled, but is is only used for non-root users (root uses SSH keys). Client command: ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@server -v -p -o GSSAPIKeyExchange=yes Client log: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /home/user/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to compute-test [130.75.80.46] port . debug1: Connection established. debug1: identity file /home/rother/.ssh/id_rsa type 0 debug1: identity file /home/rother/.ssh/id_rsa-cert type -1 debug1: identity file /home/rother/.ssh/id_dsa type -1 debug1: identity file /home/rother/.ssh/id_dsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa type -1 debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519 type -1 debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_xmss type -1 debug1: identity file /home/rother/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400 debug1: Authenticating to server: as 'root' debug1: Offering GSSAPI proposal: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q== debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g== debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: Doing group exchange debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Received GSSAPI_COMPLETE debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Rekey has happened - updating saved versions debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent debug1: Will attempt key: /home/user/.ssh/id_dsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/user/.ssh/id_ed25519 debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk debug1: Will attempt key: /home/user/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Delegating credentials debug1: Delegating credentials debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1:
[Touch-packages] [Bug 1460347] Re: B43 did not offer channel 11-13
** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1460347 Title: B43 did not offer channel 11-13 Status in network-manager package in Ubuntu: Incomplete Bug description: Ubuntu Mate 15.04 i386 / Lenovo ideapad S10-2 / Broadcom 4312 After install simple login and take a look at available wlans in the area. You will see all between 1 and 10, but none in the 11-13 range. It's also not possible to connect them as hidden network. In physical this machine was shipped with windows and it can use full range in Europe / Germany Under ubuntu we see: eric@selene:~$ iwlist chan wlan0 32 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 12 : 2.467 GHz Channel 13 : 2.472 GHz Full range but network-manager is in denial of that. eric@selene:~$ iw reg get country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 40), (N/A, 20), (N/A), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), (0 ms), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), (0 ms), DFS (57240 - 65880 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CurrentDesktop: MATE Date: Sat May 30 23:17:24 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-30 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release i386 (20150422.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.101 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Elysion20 30f1d787-c4d3-4652-950f-e656990cbe9d 802-11-wireless 0 never yes no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- Kabelnetzwerkverbindung 1 aae849bd-3bcc-49fb-bd6c-8aff25c05e51 802-3-ethernet 1433020571 Sa 30 Mai 2015 23:16:11 CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth0activated /org/freedesktop/NetworkManager/ActiveConnection/2 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/1 Kabelnetzwerkverbindung 1 aae849bd-3bcc-49fb-bd6c-8aff25c05e51 /org/freedesktop/NetworkManager/ActiveConnection/2 wlan0wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- ttyACM1 gsm unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1460347/+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 1448605] Re: package libsqlite3-0:i386 3.8.7.4-1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured
** Changed in: sqlite3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1448605 Title: package libsqlite3-0:i386 3.8.7.4-1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured Status in sqlite3 package in Ubuntu: Incomplete Bug description: Don't know, I am relatively new to bug reports! ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libsqlite3-0:i386 3.8.7.4-1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3 Architecture: amd64 CrashReports: 600:0:119:438468:2015-04-26 16:57:42.337173223 +1000:2015-04-26 16:57:43.337173223 +1000:/var/crash/libssl1.0.0:i386.0.crash 640:1000:119:15552325:2015-04-25 16:09:33.959912807 +1000:2015-04-25 18:53:09.238786763 +1000:/var/crash/_usr_bin_caja.1000.crash 600:0:119:438463:2015-04-26 16:57:42.313156604 +1000:2015-04-26 16:57:43.313156604 +1000:/var/crash/libsqlite3-0:i386.0.crash 600:0:119:438462:2015-04-26 16:57:43.249112800 +1000:2015-04-26 16:57:41.792113154 +1000:/var/crash/libjson-c2:i386.0.crash Date: Sun Apr 26 16:57:43 2015 Dependencies: gcc-5-base 5.1~rc1-0ubuntu1 libc6 2.21-0ubuntu4 libgcc1 1:5.1~rc1-0ubuntu1 multiarch-support 2.21-0ubuntu4 DuplicateSignature: package:libsqlite3-0:i386:3.8.7.4-1:package libsqlite3-0:i386 is already installed and configured ErrorMessage: package libsqlite3-0:i386 is already installed and configured InstallationDate: Installed on 2015-04-25 (1 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: sqlite3 Title: package libsqlite3-0:i386 3.8.7.4-1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1448605/+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 1820866] Re: File dialog extremely slow scanning network mounts
I have the same problem on Ubuntu 20.04.2 LTS since a couple of days, esp. in libreoffice and evince. Sometimes I have to kill the applications. The problem occurred out of the blue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1820866 Title: File dialog extremely slow scanning network mounts Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: From any application where you have a "save as" or "open" option, the dialog displays, but it takes forever. I have a i5 with 16GB RAM and 2 SSD's, so the machine is not slow. However, if I use gedit and click open / Other documents it takes 6 to 7 seconds before the file dialog is properly displayed. This does not even get better with reuse. I opened gedit just now and the first time it took 7 seconds. Then I pressed Cancel and repeated the process - it still took more than 6 seconds before the dialog was properly displayed. Often I would only see "Other locations" and then default places (Home, Documents etc) and bookmarks (I have about 8 bookmarks of which 2 are network shares) are displayed. These items are added one by one - maybe one every half second. Often it takes a few seconds before the first location other than "Other Locations" is displayed. Even the file panel is not immediate at first and you can see how lines are added one by one. Take into account that my home folder is on an SSD, so populating a file list should be lightning fast. I have looked at the CPU activity, but it does not go over about 10% during display of open and close dialogs. Just be aware that this is not specific to gedit - all applications using gnome file dialog has the same problem. Please see the attached screen recording. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 19 16:14:16 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['nohotcor...@azuri.free.fr', 'weather-extens...@xeked.com', 'openweather-extens...@jenslody.de']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-12-02 (107 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820866/+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 1406687] Re: Missing icon for mouse battery power
** Changed in: indicator-power (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1406687 Title: Missing icon for mouse battery power Status in indicator-power package in Ubuntu: Incomplete Bug description: I am using Ubuntu MATE 14.04. have a Logitech wireless mouse. The battery icon for the mouse is missing in the panel. It shows up as a white rectangle with a red circle. I have attached screenshots. Admittedly, this might not be a MATE buA as this bug report shows: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1144504 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1406687/+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 1017428] Re: avahi-demon is not disabled when on unicast '.local' domain
** Changed in: avahi (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1017428 Title: avahi-demon is not disabled when on unicast '.local' domain Status in avahi package in Ubuntu: Incomplete Bug description: Version : Linux Mint 13 Mate 64bits The avahi daemon messes with .local name resolution. There are scripts in mint to automatically disable the avahi-daemon when a .local domain is detected. They don't work anymore. /etc/resolvconf/update-libc.d/avahi-daemon : executes another script if it exists : /usr/lib/avahi/avahi-daemon-check-dns.sh : supposed to detect .local domains and disable avahi-daemon accordingly. avahi-daemon-check-dns.sh returns : grep: /etc/resolv.conf: No such file or directory resolv.conf was removed, which is why this script works no more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1017428/+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 1369958] Re: indicator-keyboard crashes in Ubuntu MATE live installer
** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1369958 Title: indicator-keyboard crashes in Ubuntu MATE live installer Status in lightdm package in Ubuntu: Incomplete Bug description: I am the maintainer of Ubuntu MATE Remix, we are currently working towards being an official Ubuntu flavour. While trying to resolve an issue with lightdm crashing (https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1369952) I noticed .xsession-errors was complaining indicators were not available in the live installer. I have recently added the following indicators to the live installer: * indicator-application * indicator-datetime * indicator-keyboard * indicator-power * indicator-session The others appear to be working correctly but I just found crash dump in /var/crash for indicator-keyboard. You can download a Ubuntu MATE iso image that exhibits this issue from https://ubuntu- mate.org/1369958/ ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: indicator-keyboard 0.0.0+14.10.20140620.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CasperVersion: 1.344 Date: Tue Sep 16 09:06:58 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service LiveMediaBuild: Ubuntu MATE 14.10 "Utopic Unicorn" - pre-beta2.25818 amd64 (20140915) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= Signal: 5 SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1369958/+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 1367098] Re: Pulseaudio doesn't start at boot
** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1367098 Title: Pulseaudio doesn't start at boot Status in pulseaudio package in Ubuntu: Incomplete Bug description: It's been happening for a week now. When I log in, I hear no sound, and when I check the sound setup and it shows no sound card. I tried to kill pulseaudio and then restart it, but sometimes it can't even be killed. The most embarrasing thing about this is that the system cannot be shut down properly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mate 1947 F pulseaudio /dev/snd/controlC0: mate 1947 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 9 06:43:45 2014 InstallationDate: Installed on 2014-04-20 (141 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Pumori dmi.board.vendor: AMD dmi.board.version: Base 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.20:bd10/24/2012:svnTOSHIBA:pnSATELLITEC855D-15V:pvrPSKD6E-005004HU:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE C855D-15V dmi.product.version: PSKD6E-005004HU dmi.sys.vendor: TOSHIBA modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2014-06-08T06:32:23.092640 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1367098/+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 1405976] Re: package libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it b
** Changed in: jackd2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1405976 Title: package libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in jackd2 package in Ubuntu: Incomplete Bug description: I was loading the Mate desktop through the terminal while browsing with Chromium when eventoccurred. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Sat Dec 27 11:30:18 2014 DuplicateSignature: package:libjack-jackd2-0:i386:1.9.9.5+20130622git7de15e7a-1ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-08-19 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: i386 SourcePackage: jackd2 Title: package libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1405976/+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 1399854] Re: Hangs at logoff or shutdown
** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1399854 Title: Hangs at logoff or shutdown Status in lightdm package in Ubuntu: Incomplete Bug description: I use a desktop environment MATE. When I try to shut down the computer or log off the screen freezes for 30 seconds, then turns black. The computer does not respond to keyboard and mouse, I can turn it off only with the aid of keys Alt + SysRq + O. After installing the kernel http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.17.1-utopic/ problem disappeared. If you are using the latest kernel from the repository or http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.16.7-ckt2-utopic/ problem exists. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Dec 6 05:57:38 2014 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.lightdm.conf: [modified] mtime.conffile..etc.init.lightdm.conf: 2014-11-12T21:32:04.127872 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1399854/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
** Tags removed: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in tilix package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1069964] Re: Two processes attempt to mount blank optical discs
** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: unity-settings-daemon (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Two processes attempt to mount blank optical discs Status in OEM Priority Project: Won't Fix Status in glib2.0 package in Ubuntu: Incomplete Status in unity-settings-daemon package in Ubuntu: Incomplete Bug description: This behavior can be reproduced using either a live USB or an installed version of the effected flavors. Simply insert a blank optical disc in the drive. The behavior differs slightly in Ubuntu GNOME as the notification to either Open with CD/DVD Creator or Eject is displayed twice - that is after simply clicking on the X to close that notification it closes but a new duplicate notification appaers immediately. The GNOME Classic session is not effected at all. In all other effected flavors and/or desktop environments a notification appears stating "Unable to mount Blank disc. Location is already mounted". Effected flavors and DE's include Ubuntu w/Unity, gnome-session-flashback, and Ubuntu MATE. Versions effected include Trusty, Utopic, and Vivid. I assume that two separate processes are actually attempting to mount the blank optical media, rather than just the file manager attemting to do so, because both Nautilus and Caja are effected (based on some of the comments below possibly also Nemo). While purely cosmetic in nature I'd certainly be willing to try and troubleshoot this if someone more tech savvy would provide some debugging instructions. Original content begins below: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1069964/+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 1555331] Re: crash in g_slist_remove_all from gtk_rc_clear_realized_style
** Changed in: gtk+2.0 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1555331 Title: crash in g_slist_remove_all from gtk_rc_clear_realized_style Status in gtk+2.0 package in Ubuntu: Incomplete Status in mate-panel package in Ubuntu: Won't Fix Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-panel 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Mar 9 22:49:55 2016 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2016-02-25 (12 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: mate-panel SegvAnalysis: Segfault happened at: 0x7f4fa6439b1c :cmp %rbp,(%rdi) PC (0x7f4fa6439b1c) ok source "%rbp" ok destination "(%rdi)" (0x160016) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: g_slist_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gtk_rc_reset_styles () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: mate-panel crashed with SIGSEGV in g_slist_remove_all() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1555331/+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 1591704] Re: bluetoothd crashed with SIGSEGV in __GI__IO_wsetb()
** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1591704 Title: bluetoothd crashed with SIGSEGV in __GI__IO_wsetb() Status in bluez package in Ubuntu: Incomplete Bug description: Bluetooth crashinfo displayed shortly after login. This happens repeatedly. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-powerpc-smp 4.4.8 Uname: Linux 4.4.0-22-powerpc-smp ppc ApportVersion: 2.20.1-0ubuntu2.1 Architecture: powerpc Date: Sat Jun 11 11:26:29 2016 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2015-09-16 (269 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha powerpc (20150827) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 05ac:0215 Apple, Inc. Internal Keyboard/Trackpad (ISO) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 003: ID 05ac:8207 Apple, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/lib/bluetooth/bluetoothd ProcEnviron: LANG=de_AT.UTF-8 LANGUAGE=de_AT:de PATH=(custom, no user) ProcKernelCmdLine: root=UUID=e7580396-741d-4923-8a8a-50db1b938df3 ro rootflags=subvol=@ quiet splash Signal: 11 SourcePackage: bluez StacktraceTop: __GI__IO_wsetb (f=f@entry=0x204b7ca0 <_IO_stdout_>, b=b@entry=0x0, eb=eb@entry=0x0, a=a@entry=0) at wgenops.c:105 _IO_unbuffer_all () at genops.c:918 _IO_cleanup () at genops.c:960 __run_exit_handlers (status=0, listp=, run_list_atexit=run_list_atexit@entry=true) at exit.c:95 __GI_exit (status=) at exit.c:104 Title: bluetoothd crashed with SIGSEGV in __GI__IO_wsetb() UpgradeStatus: Upgraded to xenial on 2016-05-08 (35 days ago) UserGroups: hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:14:51:95:FF:B4 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING RX bytes:534 acl:0 sco:0 events:27 errors:0 TX bytes:612 acl:0 sco:0 commands:26 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1591704/+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 1638833] Re: at-spi-bus-launcher crashed with SIGSEGV in strlen()
** Changed in: at-spi2-core (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1638833 Title: at-spi-bus-launcher crashed with SIGSEGV in strlen() Status in at-spi2-core package in Ubuntu: Incomplete Bug description: Pops up shortly after starting the desktop. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: at-spi2-core 2.22.0-3 ProcVersionSignature: Ubuntu 4.8.0-26.28-powerpc-smp 4.8.0 Uname: Linux 4.8.0-26-powerpc-smp ppc ApportVersion: 2.20.3-0ubuntu8 Architecture: powerpc Date: Thu Nov 3 08:36:20 2016 ExecutablePath: /usr/lib/at-spi2-core/at-spi-bus-launcher InstallationDate: Installed on 2016-11-03 (0 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161103) ProcCmdline: /usr/lib/at-spi2-core/at-spi-bus-launcher ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=de_AT:de LANG=de_AT.UTF-8 Signal: 11 SourcePackage: at-spi2-core StacktraceTop: strlen () at ../sysdeps/powerpc/powerpc32/strlen.S:98 g_variant_is_object_path () from /lib/powerpc-linux-gnu/libglib-2.0.so.0 g_dbus_proxy_new_for_bus () from /usr/lib/powerpc-linux-gnu/libgio-2.0.so.0 ?? () ?? () Title: at-spi-bus-launcher crashed with SIGSEGV in strlen() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1638833/+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 1887220] Re: Clicking on preinstalled /usr/share/applications/vim.desktop ends with "There was an error launching the application." and Vim is not launched
Blacklisted on MATE level. ** Changed in: vim (Ubuntu) Status: Confirmed => Fix Released ** Tags removed: groovy ** Tags added: impish ** Changed in: vim (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1887220 Title: Clicking on preinstalled /usr/share/applications/vim.desktop ends with "There was an error launching the application." and Vim is not launched Status in vim package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu MATE installed 2. Open Caja, navigate to /usr/share/applications/ 3. Click on Vim Expected result: * Vim is launched Actual result: * Vim is not launched, the error window is shown with text "There was an error launching the application." Notes: the /usr/share/applications/vim.desktop refers to `vim` executable which is not installed. The /usr/share/applications/vim.desktop came from ``` $ dpkg -S /usr/share/applications/vim.desktop vim-common: /usr/share/applications/vim.desktop $ aptitude why vim-common i vim-tiny Depends vim-common (= 2:7.4.1689-3ubuntu1.2) $ aptitude why vim-tiny i ubuntu-minimal Depends vim-tiny ``` So it is a dependency issue. Having vim.desktop without installed `vim` executable is useless. All Ubuntu versions are affected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-minimal 1.361.2 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Sat Jul 11 11:05:44 2020 InstallationDate: Installed on 2018-08-07 (703 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1887220/+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 1923052] Re: screen reader does not read ubiquity window
** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window Status in at-spi2-core package in Ubuntu: Confirmed Status in orca package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+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 1870213] Re: "Switching to another layout" shortcut was not set by oem-config for end-user
** Changed in: console-setup (Ubuntu) Status: New => Confirmed ** Changed in: oem-config (Ubuntu) Status: New => Confirmed ** Changed in: ubiquity (Ubuntu) Status: New => Confirmed ** Tags removed: groovy ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1870213 Title: "Switching to another layout" shortcut was not set by oem-config for end-user Status in console-setup package in Ubuntu: Confirmed Status in oem-config package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Launch Ubuntu MATE 20.04 LTS installer in OEM mode 2. Confirm using English locale 3. While setting OS for end user specify Russian language, confirm system configuration 4. Login to the configured system Expected result: * the keyboard layout switcher shows two layouts - *en* and *ru*, reacts on + hotkey Actual result: * the keyboard layout switcher shows two layouts - *en* and *ru*, but does not react on + hotkey Note: the contents of keyboard configuration files is the following: ``` $ cat /etc/default/keyboard # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="us,ru" XKBVARIANT="," XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" ``` so keyboard layout switcher is not defined here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: keyboard-configuration 1.194ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: MATE Date: Thu Apr 2 00:43:16 2020 InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1870213/+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 1918855] Re: Xorg xserver got signal 6 to abort
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Committed
Status in mesa source package in Hirsute:
Fix Committed
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
This issue should be fixed by this mesa commit https://cgit.freedesktop.org/mesa/mesa/commit/?id=3199172eaa703ac4c1fc3830c8e49c367725c3b8 which should be included since Ubuntu 20.04/focal. Please reopen this issue if you still have this problem. ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Fix Released Status in supertuxkart package in Ubuntu: Invalid Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1
[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
Resolving supertuxkart issue, actually it was a mesa issue now fixed. ** Changed in: supertuxkart (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Fix Released Status in supertuxkart package in Ubuntu: Invalid Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1 amd64Mesa
[Touch-packages] [Bug 1429222] Re: lightdm fails to start on boot of ubuntu mate but starts when restarted
** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1429222 Title: lightdm fails to start on boot of ubuntu mate but starts when restarted Status in lightdm package in Ubuntu: Incomplete Bug description: boot March 6th daily ubuntu mate installation went fine restarted got to grub started up and did not load any further switched to tty and no gui or splash screen came up. I switched to tty 1 and was able to login. lightdm: Installed: 1.13.1-0ubuntu2 Candidate: 1.13.1-0ubuntu2 Version table: *** 1.13.1-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 to reproduce install ubuntu-mate using manaul partitioning using an ext4 / partition and reusing an xfs /home. I expected lightdm to come up and display a GUI and I could get it to start by restarting it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 6 09:45:52 2015 InstallationDate: Installed on 2015-03-06 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha amd64 (20150306) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1429222/+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 1938505] [NEW] 1/4 screenshot issue in ubuntu cinnamon remix
Public bug reported: hello, i am reporting 1/4 screenshot issue in ubuntu cinnamon remix in 20.4 & 21.04 my laptop is dell 14 7400 , i5 11gen , gpu intel gpu , i am not able to use mx350 gpu in my dell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Fri Jul 30 11:47:16 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:09d9] Subsystem: Dell GP107M [GeForce MX350] [1028:09d9] InstallationDate: Installed on 2021-07-13 (16 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210422) MachineType: Dell Inc. Inspiron 7400 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.11.0-25-generic root=UUID=4afa5195-02a4-45d3-84e1-df9f5bade23a ro rootflags=subvol=@ quiet splash resume=UUID=1b62aa58-2234-4ada-bf43-f19e45ece46a vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 068X1V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd10/27/2020:br1.3:svnDellInc.:pnInspiron7400:pvr:rvnDellInc.:rn068X1V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7400 dmi.product.sku: 09D9 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu ** Attachment added: "Screenshot from 2021-07-30 11-42-12.png" https://bugs.launchpad.net/bugs/1938505/+attachment/5514711/+files/Screenshot%20from%202021-07-30%2011-42-12.png -- 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/1938505 Title: 1/4 screenshot issue in ubuntu cinnamon remix Status in xorg package in Ubuntu: New Bug description: hello, i am reporting 1/4 screenshot issue in ubuntu cinnamon remix in 20.4 & 21.04 my laptop is dell 14 7400 , i5 11gen , gpu intel gpu , i am not able to use mx350 gpu in my dell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Fri Jul 30 11:47:16 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:09d9] Subsystem: Dell GP107M [GeForce MX350] [1028:09d9] InstallationDate: Installed on 2021-07-13 (16 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210422) MachineType: Dell Inc. Inspiron 7400 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.11.0-25-generic root=UUID=4afa5195-02a4-45d3-84e1-df9f5bade23a ro rootflags=subvol=@ quiet splash resume=UUID=1b62aa58-2234-4ada-bf43-f19e45ece46a vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 068X1V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
