[Touch-packages] [Bug 971018] Re: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware
Precise and trusty are no longer supported and have reached end-of-life. Also comment #30 seems to relate to a different desktop environment. Anyone still experiencing problems should open a new bug. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: libxfixes (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxfixes in Ubuntu. https://bugs.launchpad.net/bugs/971018 Title: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware Status in Unity: Opinion Status in libxfixes package in Ubuntu: Won't Fix Status in unity package in Ubuntu: Opinion Status in xorg-server package in Ubuntu: Won't Fix Bug description: Ubuntu Precise 12.04 Beta 2 AMD64 DVD: I am running Ubuntu Precise 12.04 Beta 2 in a VirtualBox 4.1.8 session. VirtualBox Guest Additions have been installed via "jockey-gtk" from the Ubuntu Precise repository, and Unity is running in 3D mode with Compiz. When the Unity Launcher is set to "autohide," the Launcher will never reveal when the mouse pointer is moved to the left edge of the screen. It does not matter how much "pressure" is applied; the Launcher never appears. I have tried the following VirtualBox window "form-factors," all with the same result (the Launcher never appears): -- VirtualBox session running in a non-maximized window -- VirtualBox session running in a maximized window -- VirtualBox session running full-screen I have attached a screen capture (OGV) with Ubuntu Precise running in a maximized VirtualBox window. Note: This Bug may be related to the following other Bugs reported on LaunchPad: -- Bug 965643: Unity 5.8: auto-hide using mouse reveals launcher inconsistently -- -- https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/965643 -- Bug 923749: New "push mouse offscreen" feature really difficult to get -- -- https://bugs.launchpad.net/unity/+bug/923749 -- Bug 937792: Left launcher does not revel when in autohide mode on multi-monitor setups -- -- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/937792 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Apr 1 14:46:23 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/971018/+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 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
After some work and testing, here are my findings.
- The dogtag-pki autopkgtest failure is manually reproducible
using autopkgtest-virt-lxd.
- The dogtag-pki autopkgtests pass with in Impish using
libnss3 *from the archive* (uploaded and built on Hirsute).
- The dogtag-pki autopkgtests FAIL when using the very same
libnss3 version but rebuilt from source on a Hirsute schroot.
The debdiff between the two binary packages is:
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Installed-Size: [-4255-] {+4318+}
- This seems to be s390x-specific (I can't reproduce on my
amd64 laptop)
- I tried merging the latest version of src:nss from Debian,
which required refreshing a s390x-specific patch, so I was
really hoping this would fix it, but no: it fails in the
same way.
FWIW I have a branch ready for merging 2:3.67-2 to Impish, but
I'm not sure on how to handle this dogtag-pki autopkgtest failure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1931104
Title:
Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-
proposed
Status in nss package in Ubuntu:
New
Bug description:
The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz
Bad:
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end
closed connection without response'))
ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote
end closed connection without response'))
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 995, in spawn
cert = deployer.setup_cert(client, tag)
File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py",
line 355, in setup_cert
return client.setupCert(request)
File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert
response = self.connection.post(
File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
r = self.session.post(
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in
post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in
send
raise ConnectionError(err, request=request)
CA spawn failed:
Good:
nstalling CA into /var/lib/pki/pki-tomcat.
Notice: Trust flag u is set automatically if the private key is present.
/usr/lib/python3/dist-packages/urllib3/connection.py:455:
SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`,
falling back to check for a `commonName` for now. This feature is being removed
by major browsers and deprecated by RFC 2818. (See
https://github.com/urllib3/urllib3/issues/497 for details.)
warnings.warn(
==
INSTALLATION SUMMARY
==
...
The good test above was with:
ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security
Service libraries
ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite -
server
Worth to know, the good case test still fails later on with:
IOException: SocketException cannot write on socket: Failed to write to
socket: (-5938) Encountered end of file.
ERROR: CalledProcessError: Command '['pki', '-d',
'/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U',
'https://i-dogtag:8443', 'securitydomain-join', '--session',
'4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag',
'--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']'
returned non-zero exit status 255.
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 1038, in spawn
subsystem.join_security_domain(
File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201,
in join_se
[Touch-packages] [Bug 1937019] [NEW] FIDO2 tokens not supported on this build
Public bug reported: I'm trying to test systemd-cryptenroll with FIDO2 keys in the new systemd version 248 on impish. Running "systemd-cryptenroll --fido2-device=list" results in the message: FIDO2 tokens not supported on this build. Would it be possible to build systemd with FIDO support in time for the impish release? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #991129 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991129 ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991129 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937019 Title: FIDO2 tokens not supported on this build Status in systemd package in Ubuntu: New Status in systemd package in Debian: Unknown Bug description: I'm trying to test systemd-cryptenroll with FIDO2 keys in the new systemd version 248 on impish. Running "systemd-cryptenroll --fido2-device=list" results in the message: FIDO2 tokens not supported on this build. Would it be possible to build systemd with FIDO support in time for the impish release? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937019/+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 1937021] [NEW] video playback both online and offline sort of rewinds say 500 millisecs at any random instanr
Public bug reported: Video playback is not smooth. Videos on vlc, youtube etc.. does some crazy back and forth loop for a few milliseconds in between the playback. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prashant 2246 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jul 21 12:52:37 2021 InstallationDate: Installed on 2021-07-17 (3 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2019 dmi.bios.release: 15.145 dmi.bios.vendor: Insyde dmi.bios.version: F.91 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A4 dmi.board.vendor: HP dmi.board.version: 91.1E dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 91.30 dmi.modalias: dmi:bvnInsyde:bvrF.91:bd08/20/2019:br15.145:efr91.30:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1E:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: T0Z59PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** 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/1937021 Title: video playback both online and offline sort of rewinds say 500 millisecs at any random instanr Status in pulseaudio package in Ubuntu: New Bug description: Video playback is not smooth. Videos on vlc, youtube etc.. does some crazy back and forth loop for a few milliseconds in between the playback. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prashant 2246 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jul 21 12:52:37 2021 InstallationDate: Installed on 2021-07-17 (3 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2019 dmi.bios.release: 15.145 dmi.bios.vendor: Insyde dmi.bios.version: F.91 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A4 dmi.board.vendor: HP dmi.board.version: 91.1E dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 91.30 dmi.modalias: dmi:bvnInsyde:bvrF.91:bd08/20/2019:br15.145:efr91.30:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1E:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: T0Z59PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937021/+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 1937021] Re: video playback both online and offline sort of rewinds say 500 millisecs at any random instanr
What app/browser is exhibiting the problem for YouTube? ** Package changed: pulseaudio (Ubuntu) => vlc (Ubuntu) -- 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/1937021 Title: video playback both online and offline sort of rewinds say 500 millisecs at any random instanr Status in vlc package in Ubuntu: New Bug description: Video playback is not smooth. Videos on vlc, youtube etc.. does some crazy back and forth loop for a few milliseconds in between the playback. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prashant 2246 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jul 21 12:52:37 2021 InstallationDate: Installed on 2021-07-17 (3 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2019 dmi.bios.release: 15.145 dmi.bios.vendor: Insyde dmi.bios.version: F.91 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A4 dmi.board.vendor: HP dmi.board.version: 91.1E dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 91.30 dmi.modalias: dmi:bvnInsyde:bvrF.91:bd08/20/2019:br15.145:efr91.30:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1E:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: T0Z59PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1937021/+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 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: systemd (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: systemd (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Fix Committed Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: Fix Committed Status in netplan.io source package in Impish: Confirmed Status in systemd source package in Impish: Fix Committed Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1893925] Re: WF-SP800N Bluetooth ear pods not detected as sound device
Still a problem in hirsute ** Attachment added: "bluetooth settings UI" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893925/+attachment/5512392/+files/Screenshot%20from%202021-07-21%2009-43-30.png -- 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/1893925 Title: WF-SP800N Bluetooth ear pods not detected as sound device Status in alsa-driver package in Ubuntu: New Bug description: They seem to pair ok, but don't show up as sound hardware, either microphone or speaker/headphones. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robertc3384 F pulseaudio /dev/snd/pcmC0D0p: robertc3384 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 2 22:00:24 2020 InstallationDate: Installed on 2020-07-07 (56 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893925/+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 1937032] [NEW] package linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: no idea ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 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 CasperMD5CheckResult: skip Date: Wed Jul 21 06:21:52 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-12 (434 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937032 Title: package linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: no idea ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 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 CasperMD5CheckResult: skip Date: Wed Jul 21 06:21:52 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-12 (434 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937032/+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 1937019] Re: FIDO2 tokens not supported on this build
** Changed in: systemd (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937019 Title: FIDO2 tokens not supported on this build Status in systemd package in Ubuntu: New Status in systemd package in Debian: New Bug description: I'm trying to test systemd-cryptenroll with FIDO2 keys in the new systemd version 248 on impish. Running "systemd-cryptenroll --fido2-device=list" results in the message: FIDO2 tokens not supported on this build. Would it be possible to build systemd with FIDO support in time for the impish release? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937019/+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 1937036] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: I think my boot partition is full. Idea: could it have a pre-install script that checks if the install partition has space, and if not then provide a link to some documentation on how to find and purge old kernels? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 09:50:16 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-21 (90 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937036 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I think my boot partition is full. Idea: could it have a pre-install script that checks if the install partition has space, and if not then provide a link to some documentation on how to find and purge old kernels? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 09:50:16 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-21 (90 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937036/+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 1915776] Re: crash report crashes in 21.04+Mate
** Also affects: marco (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1915776 Title: crash report crashes in 21.04+Mate Status in Ubuntu MATE: New Status in apport package in Ubuntu: New Status in marco package in Ubuntu: New Bug description: I downloaded an ISO for 21.04 + Mate, (daily build) installed in a VirtualBox. Quite happy with it, works well, but every boot it pops up a box of 'crash report' and 'can I report?' Watching the network traffic, nothing is getting reported and the crashes still happen. I am looking for somebody I can email the last dozen lines or so of the boot-log to. My personal email is kneedragon1...@gmail.com. I would be very happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1915776/+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 1926256] Re: Pasted text in the terminal is always highlighted and selected
** Tags added: impish -- 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/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted 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 Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 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/1926256/+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
Tried versions 1.6, 1.7 and 1.8. Results from dmesg for each are below. 1.6 - [2.813265] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [2.814293] snd_hda_intel :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver [3.043586] snd_hda_intel :01:00.1: enabling device ( -> 0002) [3.043747] snd_hda_intel :01:00.1: Disabling MSI [3.043758] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [3.085850] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [3.086244] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver [3.086263] sof-audio-pci :00:1f.3: enabling device ( -> 0002) [3.086518] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [4.419572] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.506416] sof-audio-pci :00:1f.3: use msi interrupt mode [4.526665] sof-audio-pci :00:1f.3: hda codecs found, mask 4 [4.623692] sof-audio-pci :00:1f.3: Firmware info: version 1:6:1-53680 [4.623701] sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:18:0 [4.635902] sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:18:0 [4.655486] sof-audio-pci :00:1f.3: ASoC: physical link SDW3-Capture (id 4) not exist [4.655496] sof-audio-pci :00:1f.3: ASoC: topology: could not load header: -22 [4.655760] sof-audio-pci :00:1f.3: error: tplg component load failed -22 [4.655767] sof-audio-pci :00:1f.3: error: failed to load DSP topology -22 [4.655770] sof-audio-pci :00:1f.3: ASoC: error at snd_soc_component_probe on :00:1f.3: -22 [4.655773] sof-audio-pci :00:1f.3: ASoC: failed to probe component -22 [4.655815] sof_sdw sof_sdw: ASoC: failed to instantiate card -22 [8.695612] sof_sdw sof_sdw: snd_soc_register_card failed -22 [8.695632] sof_sdw: probe of sof_sdw failed with error -22 1.7 - [3.062326] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver [3.062905] sof-audio-pci :00:1f.3: enabling device ( -> 0002) [3.064154] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [4.236932] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.460375] sof-audio-pci :00:1f.3: use msi interrupt mode [4.486526] sof-audio-pci :00:1f.3: hda codecs found, mask 4 [4.487058] sof-audio-pci :00:1f.3: Firmware info: version 1:7:0-47d07 [4.487062] sof-audio-pci :00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:18:0 [4.487065] sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel [4.487070] sof-audio-pci :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [4.595907] sof-audio-pci :00:1f.3: Firmware info: version 1:7:0-47d07 [4.595914] sof-audio-pci :00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:18:0 [4.595918] sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel [4.610245] sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:18:0 [4.629440] sof-audio-pci :00:1f.3: ASoC: physical link SDW3-Capture (id 4) not exist [4.629448] sof-audio-pci :00:1f.3: ASoC: topology: could not load header: -22 [4.629706] sof-audio-pci :00:1f.3: error: tplg component load failed -22 [4.629712] sof-audio-pci :00:1f.3: error: failed to load DSP topology -22 [4.629713] sof-audio-pci :00:1f.3: ASoC: error at snd_soc_component_probe on :00:1f.3: -22 [4.629715] sof-audio-pci :00:1f.3: ASoC: failed to probe component -22 [4.629745] sof_sdw sof_sdw: ASoC: failed to instantiate card -22 [4.634785] sof_sdw sof_sdw: snd_soc_register_card failed -2 1.8 - [2.791146] snd_hda_intel :01:00.1: enabling device ( -> 0002) [2.792978] snd_hda_intel :01:00.1: Disabling MSI [2.792997] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [3.039625] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [3.040157] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver [3.040172] sof-audio-pci :00:1f.3: enabling device ( -> 0002) [3.040381] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [4.130786] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.390775] sof-audio-pci :00:1f.3: use msi interrupt mode [4.432864] sof-audio-pci :00:1f.3: hda codecs found, mask 4 [4.433568]
[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
Rebuilding the same source package on Groovy produces a "good" libnss3
package (the Impish dogtag-pki autopkgtests pass when using it). This
means that a build-dependency that was upgraded in Hirsute caused the
regression.
(As Christian made me notice rebuilding on Hirsute *release* with no
updates may still produce a broken package, even if the "good" package
in the archive was built on Hirsute. This is because back when the
Hirsute package was built Hirsute was still in development. The true way
to go back to what Hirsute was initially is to go back to Groovy.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1931104
Title:
Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-
proposed
Status in nss package in Ubuntu:
New
Bug description:
The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz
Bad:
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end
closed connection without response'))
ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote
end closed connection without response'))
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 995, in spawn
cert = deployer.setup_cert(client, tag)
File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py",
line 355, in setup_cert
return client.setupCert(request)
File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert
response = self.connection.post(
File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
r = self.session.post(
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in
post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in
send
raise ConnectionError(err, request=request)
CA spawn failed:
Good:
nstalling CA into /var/lib/pki/pki-tomcat.
Notice: Trust flag u is set automatically if the private key is present.
/usr/lib/python3/dist-packages/urllib3/connection.py:455:
SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`,
falling back to check for a `commonName` for now. This feature is being removed
by major browsers and deprecated by RFC 2818. (See
https://github.com/urllib3/urllib3/issues/497 for details.)
warnings.warn(
==
INSTALLATION SUMMARY
==
...
The good test above was with:
ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security
Service libraries
ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite -
server
Worth to know, the good case test still fails later on with:
IOException: SocketException cannot write on socket: Failed to write to
socket: (-5938) Encountered end of file.
ERROR: CalledProcessError: Command '['pki', '-d',
'/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U',
'https://i-dogtag:8443', 'securitydomain-join', '--session',
'4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag',
'--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']'
returned non-zero exit status 255.
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 1038, in spawn
subsystem.join_security_domain(
File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201,
in join_security_domain
subprocess.check_call(cmd)
File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f
/etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join
--session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port
8080 --secure-port 8443 TKS i-dogtag 8443
Please check pkispaw
[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
Diff of the sbuild Installed-Build-Depends from the "good" Hirsute build that produced the nss packages now in the archive and a "bad" Hirsute build done in an up-to-date Hirsute schroot: --- good2021-07-21 12:02:03.870339411 +0200 +++ bad 2021-07-21 12:03:20.367850047 +0200 @@ -3,38 +3,39 @@ automake (= 1:1.16.3-2ubuntu1), autopoint (= 0.21-3ubuntu2), autotools-dev (= 20180224.1+nmu1), - base-files (= 11ubuntu16), + base-files (= 11ubuntu19), base-passwd (= 3.5.49), - bash (= 5.1-1ubuntu1), - binutils (= 2.36.1-0ubuntu1), - binutils-common (= 2.36.1-0ubuntu1), - binutils-s390x-linux-gnu (= 2.36.1-0ubuntu1), - bsdextrautils (= 2.36.1-1ubuntu2), - bsdutils (= 1:2.36.1-1ubuntu2), + bash (= 5.1-2ubuntu1), + binutils (= 2.36.1-6ubuntu1), + binutils-common (= 2.36.1-6ubuntu1), + binutils-s390x-linux-gnu (= 2.36.1-6ubuntu1), + bsdextrautils (= 2.36.1-7ubuntu2), + bsdutils (= 1:2.36.1-7ubuntu2), build-essential (= 12.8ubuntu3), - bzip2 (= 1.0.8-4ubuntu2), + bzip2 (= 1.0.8-4ubuntu3), coreutils (= 8.32-4ubuntu2), - cpp (= 4:10.2.0-1ubuntu1), - cpp-10 (= 10.2.1-19ubuntu1), + cpp (= 4:10.3.0-1ubuntu1), + cpp-10 (= 10.3.0-1ubuntu1), dash (= 0.5.11+git20200708+dd9ef66+really0.5.11+git20200708+dd9ef66-5ubuntu1), debconf (= 1.5.74), - debhelper (= 13.3.3ubuntu2), + debhelper (= 13.3.4ubuntu1), debianutils (= 4.11.2), + debugedit (= 1:0.1-0ubuntu2), dh-autoreconf (= 20), - dh-exec (= 0.23.2), + dh-exec (= 0.23.4), dh-strip-nondeterminism (= 1.11.0-1), diffutils (= 1:3.7-3ubuntu1), - dpkg (= 1.20.7.1ubuntu2), - dpkg-dev (= 1.20.7.1ubuntu2), - dwz (= 0.13+20210201-1), + dpkg (= 1.20.9ubuntu1), + dpkg-dev (= 1.20.9ubuntu1), + dwz (= 0.14-1), file (= 1:5.39-3), - findutils (= 4.7.0-1ubuntu2), - g++ (= 4:10.2.0-1ubuntu1), - g++-10 (= 10.2.1-19ubuntu1), - gcc (= 4:10.2.0-1ubuntu1), - gcc-10 (= 10.2.1-19ubuntu1), - gcc-10-base (= 10.2.1-19ubuntu1), - gcc-11-base (= 11-20210207-1ubuntu1), + findutils (= 4.8.0-1ubuntu1), + g++ (= 4:10.3.0-1ubuntu1), + g++-10 (= 10.3.0-1ubuntu1), + gcc (= 4:10.3.0-1ubuntu1), + gcc-10 (= 10.3.0-1ubuntu1), + gcc-10-base (= 10.3.0-1ubuntu1), + gcc-11-base (= 11.1.0-1ubuntu1~21.04), gettext (= 0.21-3ubuntu2), gettext-base (= 0.21-3ubuntu2), grep (= 3.6-1), @@ -43,113 +44,114 @@ hostname (= 3.23), init-system-helpers (= 1.60), intltool-debian (= 0.35.0+20060710.5), - libacl1 (= 2.2.53-10), + libacl1 (= 2.2.53-10ubuntu1), libarchive-zip-perl (= 1.68-1), - libasan6 (= 10.2.1-19ubuntu1), - libatomic1 (= 11-20210207-1ubuntu1), - libattr1 (= 1:2.4.48-6), + libasan6 (= 11.1.0-1ubuntu1~21.04), + libatomic1 (= 11.1.0-1ubuntu1~21.04), + libattr1 (= 1:2.4.48-6build1), libaudit-common (= 1:3.0-2ubuntu1), libaudit1 (= 1:3.0-2ubuntu1), - libbinutils (= 2.36.1-0ubuntu1), - libblkid1 (= 2.36.1-1ubuntu2), - libbz2-1.0 (= 1.0.8-4ubuntu2), - libc-bin (= 2.33-0ubuntu2), - libc-dev-bin (= 2.33-0ubuntu2), - libc6 (= 2.33-0ubuntu2), - libc6-dev (= 2.33-0ubuntu2), + libbinutils (= 2.36.1-6ubuntu1), + libblkid1 (= 2.36.1-7ubuntu2), + libbz2-1.0 (= 1.0.8-4ubuntu3), + libc-bin (= 2.33-0ubuntu5), + libc-dev-bin (= 2.33-0ubuntu5), + libc6 (= 2.33-0ubuntu5), + libc6-dev (= 2.33-0ubuntu5), libcap-ng0 (= 0.7.9-2.2build1), - libcap2 (= 1:2.44-1), - libcc1-0 (= 11-20210207-1ubuntu1), - libcom-err2 (= 1.45.7-1ubuntu1), - libcrypt-dev (= 1:4.4.17-1ubuntu1), - libcrypt1 (= 1:4.4.17-1ubuntu1), - libctf-nobfd0 (= 2.36.1-0ubuntu1), - libctf0 (= 2.36.1-0ubuntu1), - libdb5.3 (= 5.3.28+dfsg1-0.6ubuntu3), - libdebconfclient0 (= 0.256ubuntu1), - libdebhelper-perl (= 13.3.3ubuntu2), - libdpkg-perl (= 1.20.7.1ubuntu2), - libelf1 (= 0.183-1), + libcap2 (= 1:2.44-1build1), + libcc1-0 (= 11.1.0-1ubuntu1~21.04), + libcom-err2 (= 1.45.7-1ubuntu2), + libcrypt-dev (= 1:4.4.17-1ubuntu3), + libcrypt1 (= 1:4.4.17-1ubuntu3), + libctf-nobfd0 (= 2.36.1-6ubuntu1), + libctf0 (= 2.36.1-6ubuntu1), + libdb5.3 (= 5.3.28+dfsg1-0.6ubuntu4), + libdebconfclient0 (= 0.256ubuntu3), + libdebhelper-perl (= 13.3.4ubuntu1), + libdpkg-perl (= 1.20.9ubuntu1), + libdw1 (= 0.183-8), + libelf1 (= 0.183-8), libfile-stripnondeterminism-perl (= 1.11.0-1), - libgcc-10-dev (= 10.2.1-19ubuntu1), - libgcc-s1 (= 11-20210207-1ubuntu1), - libgcrypt20 (= 1.8.7-2ubuntu1), + libgcc-10-dev (= 10.3.0-1ubuntu1), + libgcc-s1 (= 11.1.0-1ubuntu1~21.04), + libgcrypt20 (= 1.8.7-2ubuntu2), libgdbm-compat4 (= 1.19-2), libgdbm6 (= 1.19-2), - libgmp10 (= 2:6.2.1+dfsg-1ubuntu1), - libgomp1 (= 11-20210207-1ubuntu1), - libgpg-error0 (= 1.38-2), + libgmp10 (= 2:6.2.1+dfsg-1ubuntu2), + libgomp1 (= 11.1.0-1ubuntu1~21.04), + libgpg-error0 (= 1.38-2build1), libgssapi-krb5-2 (= 1.18.3-4), - libicu67 (= 67.1-6ubuntu1), - libisl23 (= 0.23-1), - libitm1 (= 11-20210207-1ubuntu1), + libicu67 (= 67.1-6ubuntu2), + libisl23 (= 0.23-1build1), + libitm1 (= 11.1.0-1ubuntu1~21.04), libk5crypto3 (= 1.18.3-4), libkeyutils1 (= 1.6.1-2ubuntu1), libkrb5-3 (= 1.18.3-4), libkrb5support0 (= 1.18.3-4), - liblz4-1 (= 1.9.3-1), - liblzma5 (= 5.2.5-1.0), + liblz4-1 (=
[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
My plan is now to:
- Setup a Groovy container
- Build nss 2:3.61-1ubuntu2 and verify the libnss3 is good
- Add Hirsute to sources.list and manually update the
Build-Deps, starting from the usual suspects (compilers),
hopefully finding which package breaks the dogtag-pki tests.
The testbed system will remain fixed (ubuntu:impish lxd container).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1931104
Title:
Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-
proposed
Status in nss package in Ubuntu:
New
Bug description:
The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz
Bad:
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end
closed connection without response'))
ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote
end closed connection without response'))
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 995, in spawn
cert = deployer.setup_cert(client, tag)
File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py",
line 355, in setup_cert
return client.setupCert(request)
File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert
response = self.connection.post(
File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
r = self.session.post(
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in
post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in
send
raise ConnectionError(err, request=request)
CA spawn failed:
Good:
nstalling CA into /var/lib/pki/pki-tomcat.
Notice: Trust flag u is set automatically if the private key is present.
/usr/lib/python3/dist-packages/urllib3/connection.py:455:
SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`,
falling back to check for a `commonName` for now. This feature is being removed
by major browsers and deprecated by RFC 2818. (See
https://github.com/urllib3/urllib3/issues/497 for details.)
warnings.warn(
==
INSTALLATION SUMMARY
==
...
The good test above was with:
ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security
Service libraries
ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite -
server
Worth to know, the good case test still fails later on with:
IOException: SocketException cannot write on socket: Failed to write to
socket: (-5938) Encountered end of file.
ERROR: CalledProcessError: Command '['pki', '-d',
'/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U',
'https://i-dogtag:8443', 'securitydomain-join', '--session',
'4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag',
'--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']'
returned non-zero exit status 255.
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 1038, in spawn
subsystem.join_security_domain(
File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201,
in join_security_domain
subprocess.check_call(cmd)
File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f
/etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join
--session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port
8080 --secure-port 8443 TKS i-dogtag 8443
Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log
Well one issue at a time ... the current install issue first.
Since it worked with the nss in -release I was upgrading this to the new nss.
ii 389-ds
[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault
** Description changed: - systemd-resolve keep crashing and it is very annoying as sometimes it - severely interrupt normal dns resolving. + [Impact] + + * systemd-resolved stops replying to clients on the local LAN. + * logging segfault crashes in dmesg: + [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] + [836786.046524] Code: Bad RIP value. + [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] + [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] + [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 + + * The upload backports the upstream fix + (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. + + [Test Plan] + + * Setup /etc/systemd/resolved.conf: + [Resolve] + DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net + DNSSEC=yes + DNSOverTLS=opportunistic + MulticastDNS=no + LLMNR=no + Cache=yes + DNSStubListener=yes + Domains=~. + + * wait for ~24-48 hours and observe if any crash happens + + [Where problems could occur] + + * Any regression would likely cause crashes in systemd-resolved, making + it unresponsive to DNS network name requests to local applications. + + [Other Info] + + * Reported upstream: https://github.com/systemd/systemd/issues/18427 + * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 + + === Original description === + + + systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 - Typical error in dmesg: + Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd /libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Bug description: [Impact] * systemd-resolved stops replying to clients on the local LAN. * logging segfault crashes in dmesg: [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] [836786.046524] Code: Bad RIP value. [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in syste
[Touch-packages] [Bug 1937069] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: update-initramfs: Generating /boot/initrd.img-5.4.0-80-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-80-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/initramfs-tools.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 4.15.0-151.157-generic 4.15.18 Uname: Linux 4.15.0-151-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 12:43:03 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-07-21 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937069 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: update-initramfs: Generating /boot/initrd.img-5.4.0-80-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-80-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/initramfs-tools.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 4.15.0-151.157-generic 4.15.18 Uname: Linux 4.15.0-151-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 12:43:03 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-07-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937069/+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 1937069] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937069 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: update-initramfs: Generating /boot/initrd.img-5.4.0-80-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-80-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/initramfs-tools.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 4.15.0-151.157-generic 4.15.18 Uname: Linux 4.15.0-151-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 12:43:03 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-07-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937069/+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 357732] Re: cups always prints with the default page size
Having kind of this issue on my Ubuntu Xenial (16.04) with Brother MFC Laser-Printer. The printer worked fine on the same system for over 1 year and suddenly every(!) custom settings from GUI printing dialog was ignored. I need papersize A4 but always got letter format. The only workaround I found was to set A4 hard-coded in default PPA file. But since today I can't switch dublex-printing or switch from color-printing (default) to black and white! Very annoying and I don't know what may have changed between once working and stopped ignoring my custom printing settings for a new printing-job. In my case there already is '/usr/lib/cups/filter/pstopdf'. Reinstalling the packages 'cups-filters cups-filters-core-drivers' didn't help. -- 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/357732 Title: cups always prints with the default page size Status in GS-GPL: Invalid Status in cups package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Invalid Status in cups source package in Intrepid: Invalid Status in ghostscript source package in Intrepid: Invalid Status in cups source package in Jaunty: Fix Released Status in ghostscript source package in Jaunty: Invalid Bug description: After the upgrade to Jaunty some users experience that a part of the page is cut when printing, or other kinds of misalignment. (A fix is available, see below) Details: Cups does not print in any other page size than the one set in /etc/papersize, if the requested page size is specified as a job option rather than within the PS file. Pages are passed through "gs -sDEVICE=pdfwrite ..." which sets the page size to the default page size. Yet, I don't know whether this is a bug in ghostscript or the intended behavior of ghostscript and a bug in cups. Since the upgrade to Jauny beta, I experienced that evince would shift a document up when printing. It is reproducible. I print in A4 on a Canon IR3170Ci. The printed output is translated up. The upper part of the contents in not visible. I also tried another printer driver (hpijs instead of post-script) and did not observe any improvement. Changing /etc/papersize from letter to a4 allows me to print in a4. Printing from evince also working fine in intrepid. To reproduce the bug: lpr -omedia=A3 testpage.ps There should not be a problem if the postscript file itself requests a page size. FIX: # (For simplicity, just paste this section to a terminal.) # Download the attached pstopdf and install it in /usr/lib/cups/filter/ cd /tmp wget http://launchpadlibrarian.net/25537150/pstopdf sudo cp pstopdf /usr/lib/cups/filter/ # Then change the permissions of the installed file: sudo chmod ugo+rx /usr/lib/cups/filter/pstopdf # that's all. To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/357732/+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 357732] Re: cups always prints with the default page size
Is there a good reason for still using 16.04? -- 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/357732 Title: cups always prints with the default page size Status in GS-GPL: Invalid Status in cups package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Invalid Status in cups source package in Intrepid: Invalid Status in ghostscript source package in Intrepid: Invalid Status in cups source package in Jaunty: Fix Released Status in ghostscript source package in Jaunty: Invalid Bug description: After the upgrade to Jaunty some users experience that a part of the page is cut when printing, or other kinds of misalignment. (A fix is available, see below) Details: Cups does not print in any other page size than the one set in /etc/papersize, if the requested page size is specified as a job option rather than within the PS file. Pages are passed through "gs -sDEVICE=pdfwrite ..." which sets the page size to the default page size. Yet, I don't know whether this is a bug in ghostscript or the intended behavior of ghostscript and a bug in cups. Since the upgrade to Jauny beta, I experienced that evince would shift a document up when printing. It is reproducible. I print in A4 on a Canon IR3170Ci. The printed output is translated up. The upper part of the contents in not visible. I also tried another printer driver (hpijs instead of post-script) and did not observe any improvement. Changing /etc/papersize from letter to a4 allows me to print in a4. Printing from evince also working fine in intrepid. To reproduce the bug: lpr -omedia=A3 testpage.ps There should not be a problem if the postscript file itself requests a page size. FIX: # (For simplicity, just paste this section to a terminal.) # Download the attached pstopdf and install it in /usr/lib/cups/filter/ cd /tmp wget http://launchpadlibrarian.net/25537150/pstopdf sudo cp pstopdf /usr/lib/cups/filter/ # Then change the permissions of the installed file: sudo chmod ugo+rx /usr/lib/cups/filter/pstopdf # that's all. To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/357732/+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 1937069] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1937036 *** https://bugs.launchpad.net/bugs/1937036 ** This bug has been marked a duplicate of bug 1937036 package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937069 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: update-initramfs: Generating /boot/initrd.img-5.4.0-80-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-80-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/initramfs-tools.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 4.15.0-151.157-generic 4.15.18 Uname: Linux 4.15.0-151-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 12:43:03 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-07-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937069/+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 1937036] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937036 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I think my boot partition is full. Idea: could it have a pre-install script that checks if the install partition has space, and if not then provide a link to some documentation on how to find and purge old kernels? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 09:50:16 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-21 (90 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937036/+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 1937072] [NEW] Screen tearing & mouse cursor glitch with unable change brightness of my display
Public bug reported: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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 -- 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/1937072 Title: Screen tearing & mouse cursor glitch with unable change brightness of my display Status in xorg package in Ubuntu: New Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.relea
[Touch-packages] [Bug 1937032] Re: package linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937032 Title: package linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: no idea ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 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 CasperMD5CheckResult: skip Date: Wed Jul 21 06:21:52 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-12 (434 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937032/+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 1916651] Re: asks about irc user home directory during upgrade
Hello Joe, or anyone else affected, Accepted base-passwd into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/base- passwd/3.5.49ubuntu1 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: base-passwd (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 base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1916651 Title: asks about irc user home directory during upgrade Status in base-passwd package in Ubuntu: Fix Released Status in base-passwd source package in Hirsute: Fix Committed Status in base-passwd package in Debian: Fix Released Bug description: [Test Case] 1) On an Ubuntu 20.10 system edit your /etc/apt/sources.list file to have hirsute instead of groovy (this is the easiest way to verify the fix because the release upgrade process disables -proposed) 2) Run apt-get update 3) Execute 'sudo apt-get install base-passwd' With the version of base-passwd in the release component you'll receive a prompt about moving the 'irc' user's home directory from '/var/run/ircd' to '/run/ircd'. With the version of base-passwd from -proposed you will not receive a prompt and will instead see the following dpkg message: "Changing home-directory of irc from /var/run/ircd to /run/ircd" [Where Problems Could Occur] In the event that there is a logical error when checking for the irc user and its old home directory being /var/run/ircd a debconf prompt may not be presented when it really should be. [Original Description] Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's home directory should be moved from `/var/run/ircd` to `/run/ircd`. Having no IRC server installed makes this very confusing, but appears harmless (https://askubuntu.com/questions/876975/user-irc-inside-of-default-ubuntu-16-04-server). Possibly caused by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946884, but can this not prompt the user for a decision? ProblemType: BugDistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Feb 23 12:02:59 2021 InstallationDate: Installed on 2019-08-17 (556 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: libc6 libc6 libssl1.1 libssl1.1SourcePackage: base-passwd UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1916651/+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 1937080] [NEW] Screen tearing & mouse cursor glitch
Public bug reported: screen tearing and cursor glitch screen, When I type something it display after 2sec high latency on display. I have installed almost 25 linux distro almost all ubuntu flavors and arch linux distro all have same problem. I think it is kernal issue. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 18:10:10 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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 corruption hirsute ubuntu wayland-session ** Attachment added: "Video and Image sample" https://bugs.launchpad.net/bugs/1937080/+attachment/5512522/+files/20210721_18.tar.xz -- 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/1937080 Title: Screen tearing & mouse cursor glitch Status in xorg package in Ubuntu: New Bug description: screen tearing and cursor glitch screen, When I type something it display after 2sec high latency on display. I have installed almost 25 linux distro almost all ubuntu flavors and arch linux distro all have same problem. I think it is kernal issue. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 18:10:10 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chas
[Touch-packages] [Bug 1937082] [NEW] gunzip fails to extract data from stdin when the zip holds multiple files
Public bug reported:
There is no good reason for this command to fail:
$ wget --quiet -O -
https://web.archive.org/web/20210721004028/freefontsdownload.net/download/76451/lucida_fax.zip
| gunzip -
The output is:
[InternetShortcut]
URL=HOMESITEfree-lucida_fax-font-76451.htmgzip: stdin has more than one
entry--rest ignored
What's happening is gzip logic has gotten tangled up with the gunzip
logic. If gzip receives an input stream, it's sensible that the
resulting archive contain just one file. But there's no reason gunzip
should not be able to produce multiple files from a zip stream. Note
that -c was not given to gunzip, so it should not have the constraints
that use of stdout would impose.
The man page is also a problem. The gunzip portion of the aggregated man
page makes no statement about how stdin is expected to operate. At a
minimum, it should say that a minus ("-") directs gunzip to read from
stdin.
** Affects: gzip (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1937082
Title:
gunzip fails to extract data from stdin when the zip holds multiple
files
Status in gzip package in Ubuntu:
New
Bug description:
There is no good reason for this command to fail:
$ wget --quiet -O -
https://web.archive.org/web/20210721004028/freefontsdownload.net/download/76451/lucida_fax.zip
| gunzip -
The output is:
[InternetShortcut]
URL=HOMESITEfree-lucida_fax-font-76451.htmgzip: stdin has more than one
entry--rest ignored
What's happening is gzip logic has gotten tangled up with the gunzip
logic. If gzip receives an input stream, it's sensible that the
resulting archive contain just one file. But there's no reason gunzip
should not be able to produce multiple files from a zip stream. Note
that -c was not given to gunzip, so it should not have the constraints
that use of stdout would impose.
The man page is also a problem. The gunzip portion of the aggregated
man page makes no statement about how stdin is expected to operate.
At a minimum, it should say that a minus ("-") directs gunzip to read
from stdin.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1937082/+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 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => In Progress ** Changed in: systemd (Ubuntu Hirsute) Status: Fix Committed => In Progress ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in netplan.io source package in Focal: New Status in systemd source package in Focal: In Progress Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: In Progress Status in netplan.io source package in Impish: Confirmed Status in systemd source package in Impish: In Progress Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1926062] Please test proposed package
Hello Jatin, or anyone else affected, Accepted gnome-settings-daemon into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-settings- daemon/3.36.1-0ubuntu1.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- 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. -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D
[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Hello Jatin, or anyone else affected, Accepted gnome-settings-daemon into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-settings- daemon/3.38.1-3ubuntu3.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: gnome-settings-daemon (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: gnome-settings-daemon (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLE
[Touch-packages] [Bug 1937089] [NEW] System76 - systemd and gnome errors, crash with black screen
You have been subscribed to a public bug: I'm uncertain if this is specific to System76, or if it is resulting from an error in systemd or gdm3. Symptoms: Unprompted, screen will go black, and then bring you back to the login screen. Upon entering the password to log back in you're brought back to a black screen. Hitting ctrl+alt+f5 I'm able to get back to a terminal, login, and restart gdm to be brought back to the desktop (sudo systemctl restart gdm) Specs: System76 Darter Pro inxi CPU: Quad Core Intel Core i7-10510U (-MT MCP-) speed/min/max: 1195/400/4900 MHz Kernel: 5.11.0-7620-generic x86_64 Up: 30m Mem: 5091.7/31984.5 MiB (15.9%) Storage: 465.76 GiB (76.2% used) Procs: 371 Shell: bash 5.0.17 inxi: 3.0.38 lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Logs >From /var/log/syslog at the time of the disruption: Jul 21 08:18:36 user-Darter-Pro systemd-resolved[1289]: Freeing transaction 62282. Jul 21 08:18:38 user-Darter-Pro systemd[1]: We couldn't coldplug machine-qemu\x2d1\x2dubuntu20.04.scope, proceeding anyway: Connection timed out Jul 21 08:18:38 user-Darter-Pro systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro NetworkManager[1364]: [1626873518.6564] caught SIGTERM, shutting down normally. Jul 21 08:18:38 user-Darter-Pro systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: switcheroo-control.service: Succeeded. Jul 21 08:18:38 user-Darter-Pro systemd[1]: accounts-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: gdm.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro thermald[1409]: Terminating ... Jul 21 08:18:38 user-Darter-Pro system76-power[1406]: [INFO] caught signal: SIGTERM Jul 21 08:18:38 user-Darter-Pro systemd[1]: system76-power.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Got SIGTERM, quitting. Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-machined.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe01:19ab. Jul 21 08:18:38 user-Darter-Pro kernel: [ 2399.879916] wlp0s20f3: deauthenticating from 30:23:03:db:ac:19 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 21 08:18:38 user-Darter-Pro ModemManager[1518]: Caught signal, shutting down... Jul 21 08:18:38 user-Darter-Pro systemd[1]: avahi-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro pulseaudio[2373]: X connection to :0 broken (explicit kill or server shutdown). Jul 21 08:18:38 user-Darter-Pro systemd[1]: ModemManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663429:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663447:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663498:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro bluetoothd[1357]: Terminating Jul 21 08:18:38 user-Darter-Pro /usr/lib/gdm3/gdm-x-session[2471]: (WW) modeset(0): flip queue failed: Permission denied Jul 21 08:18:38 user-Darter-Pro /usr/lib/gdm3/gdm-x-session[2471]: (WW) modeset(0): Page flip failed: Permission denied Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-machined.service: Succeeded. Jul 21 08:18:38 user-Darter-Pro wpa_supplicant[1411]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=30:23:03:db:ac:19 reason=3 locally_generated=1 Jul 21 08:18:38 user-Darter-Pro gnome-shell[2614]: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jul 21 08:18:38 user-Darter-Pro systemd[1]: polkit.service: Unexpected
[Touch-packages] [Bug 1937089] [NEW] System76 - systemd and gnome errors, crash with black screen
Public bug reported: I'm uncertain if this is specific to System76, or if it is resulting from an error in systemd or gdm3. Symptoms: Unprompted, screen will go black, and then bring you back to the login screen. Upon entering the password to log back in you're brought back to a black screen. Hitting ctrl+alt+f5 I'm able to get back to a terminal, login, and restart gdm to be brought back to the desktop (sudo systemctl restart gdm) Specs: System76 Darter Pro inxi CPU: Quad Core Intel Core i7-10510U (-MT MCP-) speed/min/max: 1195/400/4900 MHz Kernel: 5.11.0-7620-generic x86_64 Up: 30m Mem: 5091.7/31984.5 MiB (15.9%) Storage: 465.76 GiB (76.2% used) Procs: 371 Shell: bash 5.0.17 inxi: 3.0.38 lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Logs >From /var/log/syslog at the time of the disruption: Jul 21 08:18:36 user-Darter-Pro systemd-resolved[1289]: Freeing transaction 62282. Jul 21 08:18:38 user-Darter-Pro systemd[1]: We couldn't coldplug machine-qemu\x2d1\x2dubuntu20.04.scope, proceeding anyway: Connection timed out Jul 21 08:18:38 user-Darter-Pro systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro NetworkManager[1364]: [1626873518.6564] caught SIGTERM, shutting down normally. Jul 21 08:18:38 user-Darter-Pro systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: switcheroo-control.service: Succeeded. Jul 21 08:18:38 user-Darter-Pro systemd[1]: accounts-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: gdm.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro thermald[1409]: Terminating ... Jul 21 08:18:38 user-Darter-Pro system76-power[1406]: [INFO] caught signal: SIGTERM Jul 21 08:18:38 user-Darter-Pro systemd[1]: system76-power.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Got SIGTERM, quitting. Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-machined.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe01:19ab. Jul 21 08:18:38 user-Darter-Pro kernel: [ 2399.879916] wlp0s20f3: deauthenticating from 30:23:03:db:ac:19 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 21 08:18:38 user-Darter-Pro ModemManager[1518]: Caught signal, shutting down... Jul 21 08:18:38 user-Darter-Pro systemd[1]: avahi-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro pulseaudio[2373]: X connection to :0 broken (explicit kill or server shutdown). Jul 21 08:18:38 user-Darter-Pro systemd[1]: ModemManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663429:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663447:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663498:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro bluetoothd[1357]: Terminating Jul 21 08:18:38 user-Darter-Pro /usr/lib/gdm3/gdm-x-session[2471]: (WW) modeset(0): flip queue failed: Permission denied Jul 21 08:18:38 user-Darter-Pro /usr/lib/gdm3/gdm-x-session[2471]: (WW) modeset(0): Page flip failed: Permission denied Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-machined.service: Succeeded. Jul 21 08:18:38 user-Darter-Pro wpa_supplicant[1411]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=30:23:03:db:ac:19 reason=3 locally_generated=1 Jul 21 08:18:38 user-Darter-Pro gnome-shell[2614]: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jul 21 08:18:38 user-Darter-Pro systemd[1]: polkit.service: Unexpected error response from
[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names
** Description changed: [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 + * 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 + * `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 + * 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 this 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 ** Description changed: [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 this 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. + * [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 behaviou
[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names
Hello Victor, or anyone else affected, Accepted shadow into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shadow/1:4.8.1-1ubuntu8.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: shadow (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 shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Focal: In Progress 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/+source/shadow/+bug/1927078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe
[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names
Unsubscribing sponsors. -- 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 shadow package in Ubuntu: Fix Released Status in shadow source package in Focal: In Progress 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/+source/shadow/+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 1928989] Re: expiring trust anchor compatibility issue
Assigning the verification and publication to xenial-security to myself. Thanks. ** Changed in: openssl (Ubuntu Xenial) Assignee: (unassigned) => Steve Beattie (sbeattie) -- 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: Confirmed 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 '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- 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. ERROR: cannot verify canonical.com's certificate, issued by 'CN=R3,O=Let\'s Encrypt,C=US': Issued certificate has expired. To connect to canonical.com insecurely, use `--no-check-certificate'. # upgrade to new openssl, to see that connectivity is restored, even in october $ dpkg-query -W libssl1.0.0 libssl1.0.0:amd64 1.0.2g-1ubuntu4.20 $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2c, 2001:67c:1360:8001::2b, 91.189.88.180, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2c|: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-10-01 00:00:00 (21.9 MB/s) - '/dev/null' save
[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: 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 Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 804178] Re: "Front" ALSA volume control affects headphones on some machines
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- 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/804178 Title: "Front" ALSA volume control affects headphones on some machines Status in pulseaudio package in Ubuntu: Expired Bug description: There is no sound playing through my headphones, nor through my computer speakers. They worked for a moment, but stopped abruptly. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 20' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,103c2a9e,00100202' Controls : 35 Simple ctrls : 20 Date: Fri Jul 1 07:59:15 2011 LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Internal Audio - HDA NVidia Symptom_DevicesInUse: 4622 10827 Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [AY020AA-ABA p6320f, Realtek ALC888, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: VIOLET6 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 6.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/12/2009:svnHP-Pavilion:pnAY020AA-ABAp6320f:pvr:rvnPEGATRONCORPORATION:rnVIOLET6:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: AY020AA-ABA p6320f dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/804178/+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 im s390x AES code
** Attachment added: "Standalone C program from the upstream test case" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/+attachment/5512579/+files/evp_extra_test.c -- 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 im s390x AES code Status in Ubuntu on IBM z Systems: Triaged Status in openssl package in Ubuntu: New Status in openssl source package in Bionic: New Status in openssl source package in Focal: New Status in openssl source package in Groovy: New Status in openssl source package in Hirsute: New Status in openssl source package in Impish: New Bug description: Problem description: 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 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 1927078] Re: Don't allow useradd to use fully numeric names
Hello Victor, or anyone else affected, Accepted shadow into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shadow/1:4.8.1-1ubuntu5.20.04.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- 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: shadow (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 shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names 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/+source/shadow/+bug/1927078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.ne
[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot
can you provide steps to reproduce the problem?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930738
Title:
network configuration failed on reboot
Status in systemd package in Ubuntu:
Incomplete
Bug description:
This issue was reported at
https://github.com/systemd/systemd/issues/17012
**Used distribution**
> Ubuntu 20.04.1 LTS
**systemd version the issue has been seen with**
> 245.4-4ubuntu3.2
**Issue details**
I configured 255 IPv4 address (including primary IP) using netplan but when
the server restart, it time out on configuring the interface. If I limit total
IPv4 addresses to 181 or less, it works. But anything larger than 181 fails.
Below are my configurations and error logs.
**/etc/netplan/10-ens3.yaml**
```
network:
version: 2
renderer: networkd
ethernets:
ens3:
dhcp4: no
addresses:
- 140.XX.XX.XX/23
- 103.XXX.XX.1/24
- 103.XXX.XX.2/24
- CONTINUED IP ADDRESS UPTO BELOW ...
- 103.XXX.XX.254/24
gateway4: 140.XX.XX.X
nameservers:
addresses: [1.1.1.1, 1.0.0.1]
routes:
- to: 169.254.0.0/16
via: 140.XX.XX.X
metric: 100
```
The above config works if I run `netplan apply` but when I reboot, it does
not work.
**networkctl**
```
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 ens3 etherroutablefailed
2 links listed.
```
**/etc/systemd/system/systemd-networkd.service.d/override.conf**
```
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
```
**systemctl status systemd-networkd.service**
```
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service;
enabled-runtime; vendor preset: enabled)
Drop-In: /etc/systemd/system/systemd-networkd.service.d
└─override.conf
Active: active (running) since Thu 2020-09-10 19:46:58 UTC; 1min 36s ago
Docs: man:systemd-networkd.service(8)
Main PID: 346 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 1074)
Memory: 3.8M
CGroup: /system.slice/systemd-networkd.service
└─346 /lib/systemd/systemd-networkd
Sep 10 19:47:03 test-server systemd-networkd[346]: NDISC: Sent Router
Solicitation, next solicitation in 7s
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: No RA received
before link confirmation timeout
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Invoking callback
for 'timeout' event.
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Sent Router
Solicitation, next solicitation in 15s
Sep 10 19:47:23 test-server systemd-networkd[346]: Assertion 'm->sealed'
failed at src/libsystemd/sd-netlink/netlink-message.c:582, function
netlink_message_read_internal(). Ignoring.
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Could not set
address: Connection timed out
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Failed
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: State changed:
configuring -> failed
Sep 10 19:47:23 test-server systemd-networkd[346]: Sent message type=signal
sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sep 10 19:47:23 test-server systemd-networkd[346]: NDISC: Stopping IPv6
Router Solicitation client
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+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 1937110] [NEW] dhcp option 121 & 249
Public bug reported: Hello, I'm running into issues with subiquity on a cloud provider. The cloud provider is using an on-link L3 gateway. His DHCP response looks like this: OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 172.31.1.1 OPTION: 51 ( 4) IP address leasetime 86400 (24h) OPTION: 1 ( 4) Subnet mask 255.255.255.255 OPTION: 3 ( 4) Routers 172.31.1.1 OPTION: 6 ( 12) DNS server OPTION: 121 ( 14) Classless Static Route20ac1f010100 ... ac1f0101 .. OPTION: 249 ( 14) MSFT - Classless route20ac1f010100 ... ac1f0101 .. Im booting the subiquity process with an patched ipxe (https://github.com/ipxe/ipxe/pull/104) like this: #!ipxe kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null initrd .../initrd boot initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso Sadly subiquity is stuck with a broken network (because of missing dhcp option 121/249 support). It happens when its running the /init from the kernel right after kernel is booted, i guess even before the subiquity is started(?). After further debugging, it looks like the provided kernel 5.4.80 #90 Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc- dhclient-4.4.1 which is lacking the given options. Would be awesome if this could be fixed.. maybe just a simple busybox compile option? ** Affects: subiquity Importance: Undecided Status: New ** Affects: busybox (Ubuntu) Importance: Undecided Status: New ** Also affects: busybox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1937110 Title: dhcp option 121 & 249 Status in subiquity: New Status in busybox package in Ubuntu: New Bug description: Hello, I'm running into issues with subiquity on a cloud provider. The cloud provider is using an on-link L3 gateway. His DHCP response looks like this: OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 172.31.1.1 OPTION: 51 ( 4) IP address leasetime 86400 (24h) OPTION: 1 ( 4) Subnet mask 255.255.255.255 OPTION: 3 ( 4) Routers 172.31.1.1 OPTION: 6 ( 12) DNS server OPTION: 121 ( 14) Classless Static Route20ac1f010100 ... ac1f0101 .. OPTION: 249 ( 14) MSFT - Classless route20ac1f010100 ... ac1f0101 .. Im booting the subiquity process with an patched ipxe (https://github.com/ipxe/ipxe/pull/104) like this: #!ipxe kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null initrd .../initrd boot initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso Sadly subiquity is stuck with a broken network (because of missing dhcp option 121/249 support). It happens when its running the /init from the kernel right after kernel is booted, i guess even before the subiquity is started(?). After further debugging, it looks like the provided kernel 5.4.80 #90 Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc- dhclient-4.4.1 which is lacking the given options. Would be awesome if this could be fixed.. maybe just a simple busybox compile option? To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937110/+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 1937089] Re: System76 - systemd and gnome errors, crash with black screen
something appears to have stopped or restarted your dbus service, which will cause widespread problems on the system; you'll need to attach more complete logs for any further debug ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937089 Title: System76 - systemd and gnome errors, crash with black screen Status in systemd package in Ubuntu: Incomplete Bug description: I'm uncertain if this is specific to System76, or if it is resulting from an error in systemd or gdm3. Symptoms: Unprompted, screen will go black, and then bring you back to the login screen. Upon entering the password to log back in you're brought back to a black screen. Hitting ctrl+alt+f5 I'm able to get back to a terminal, login, and restart gdm to be brought back to the desktop (sudo systemctl restart gdm) Specs: System76 Darter Pro inxi CPU: Quad Core Intel Core i7-10510U (-MT MCP-) speed/min/max: 1195/400/4900 MHz Kernel: 5.11.0-7620-generic x86_64 Up: 30m Mem: 5091.7/31984.5 MiB (15.9%) Storage: 465.76 GiB (76.2% used) Procs: 371 Shell: bash 5.0.17 inxi: 3.0.38 lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal Logs From /var/log/syslog at the time of the disruption: Jul 21 08:18:36 user-Darter-Pro systemd-resolved[1289]: Freeing transaction 62282. Jul 21 08:18:38 user-Darter-Pro systemd[1]: We couldn't coldplug machine-qemu\x2d1\x2dubuntu20.04.scope, proceeding anyway: Connection timed out Jul 21 08:18:38 user-Darter-Pro systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro NetworkManager[1364]: [1626873518.6564] caught SIGTERM, shutting down normally. Jul 21 08:18:38 user-Darter-Pro systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: switcheroo-control.service: Succeeded. Jul 21 08:18:38 user-Darter-Pro systemd[1]: accounts-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: gdm.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro thermald[1409]: Terminating ... Jul 21 08:18:38 user-Darter-Pro system76-power[1406]: [INFO] caught signal: SIGTERM Jul 21 08:18:38 user-Darter-Pro systemd[1]: system76-power.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Got SIGTERM, quitting. Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-machined.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe01:19ab. Jul 21 08:18:38 user-Darter-Pro kernel: [ 2399.879916] wlp0s20f3: deauthenticating from 30:23:03:db:ac:19 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 21 08:18:38 user-Darter-Pro ModemManager[1518]: Caught signal, shutting down... Jul 21 08:18:38 user-Darter-Pro systemd[1]: avahi-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro pulseaudio[2373]: X connection to :0 broken (explicit kill or server shutdown). Jul 21 08:18:38 user-Darter-Pro systemd[1]: ModemManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663429:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663447:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663498:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro bluetoothd[1357]: Terminating Jul 21 08:18:38 user-Darter-Pro /usr/lib/gdm3/gdm-x-session[2471]: (WW) modeset(0): flip queue failed: Permission denied Jul 21 08:18:38 user-Darter-Pro /usr/lib/gdm3/gdm-x-session[2471]:
[Touch-packages] [Bug 1937089] Re: System76 - systemd and gnome errors, crash with black screen
Here is a sosreport of the affected system. ** Attachment added: "sosreport of affected system" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937089/+attachment/5512592/+files/sosreport-blackscreen.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937089 Title: System76 - systemd and gnome errors, crash with black screen Status in systemd package in Ubuntu: Incomplete Bug description: I'm uncertain if this is specific to System76, or if it is resulting from an error in systemd or gdm3. Symptoms: Unprompted, screen will go black, and then bring you back to the login screen. Upon entering the password to log back in you're brought back to a black screen. Hitting ctrl+alt+f5 I'm able to get back to a terminal, login, and restart gdm to be brought back to the desktop (sudo systemctl restart gdm) Specs: System76 Darter Pro inxi CPU: Quad Core Intel Core i7-10510U (-MT MCP-) speed/min/max: 1195/400/4900 MHz Kernel: 5.11.0-7620-generic x86_64 Up: 30m Mem: 5091.7/31984.5 MiB (15.9%) Storage: 465.76 GiB (76.2% used) Procs: 371 Shell: bash 5.0.17 inxi: 3.0.38 lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal Logs From /var/log/syslog at the time of the disruption: Jul 21 08:18:36 user-Darter-Pro systemd-resolved[1289]: Freeing transaction 62282. Jul 21 08:18:38 user-Darter-Pro systemd[1]: We couldn't coldplug machine-qemu\x2d1\x2dubuntu20.04.scope, proceeding anyway: Connection timed out Jul 21 08:18:38 user-Darter-Pro systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro NetworkManager[1364]: [1626873518.6564] caught SIGTERM, shutting down normally. Jul 21 08:18:38 user-Darter-Pro systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: switcheroo-control.service: Succeeded. Jul 21 08:18:38 user-Darter-Pro systemd[1]: accounts-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: gdm.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro thermald[1409]: Terminating ... Jul 21 08:18:38 user-Darter-Pro system76-power[1406]: [INFO] caught signal: SIGTERM Jul 21 08:18:38 user-Darter-Pro systemd[1]: system76-power.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Got SIGTERM, quitting. Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-machined.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe01:19ab. Jul 21 08:18:38 user-Darter-Pro kernel: [ 2399.879916] wlp0s20f3: deauthenticating from 30:23:03:db:ac:19 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 21 08:18:38 user-Darter-Pro ModemManager[1518]: Caught signal, shutting down... Jul 21 08:18:38 user-Darter-Pro systemd[1]: avahi-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro pulseaudio[2373]: X connection to :0 broken (explicit kill or server shutdown). Jul 21 08:18:38 user-Darter-Pro systemd[1]: ModemManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663429:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663447:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663498:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro bluetoothd[1357]: Terminating Jul 21 08:18:38 user-Darter-Pro /usr/lib/gdm3/gdm-x-session[2471]: (WW) modeset(0): flip queue failed: Permission denied Jul 21 08:18:38 user-Darter-Pro /usr/lib/gdm3/gdm-x-session[2471]: (WW) modeset(0): Page flip
[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
The good news is that the test passes when building nss in a Groovy lxd
container, but fails when copying that container (lxc copy), upgrading
the copy to Hirsute and rebuilding there, so I have good pair of
containers to do the "bisect" on.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1931104
Title:
Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-
proposed
Status in nss package in Ubuntu:
New
Bug description:
The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz
Bad:
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end
closed connection without response'))
ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote
end closed connection without response'))
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 995, in spawn
cert = deployer.setup_cert(client, tag)
File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py",
line 355, in setup_cert
return client.setupCert(request)
File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert
response = self.connection.post(
File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
r = self.session.post(
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in
post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in
send
raise ConnectionError(err, request=request)
CA spawn failed:
Good:
nstalling CA into /var/lib/pki/pki-tomcat.
Notice: Trust flag u is set automatically if the private key is present.
/usr/lib/python3/dist-packages/urllib3/connection.py:455:
SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`,
falling back to check for a `commonName` for now. This feature is being removed
by major browsers and deprecated by RFC 2818. (See
https://github.com/urllib3/urllib3/issues/497 for details.)
warnings.warn(
==
INSTALLATION SUMMARY
==
...
The good test above was with:
ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security
Service libraries
ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite -
server
Worth to know, the good case test still fails later on with:
IOException: SocketException cannot write on socket: Failed to write to
socket: (-5938) Encountered end of file.
ERROR: CalledProcessError: Command '['pki', '-d',
'/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U',
'https://i-dogtag:8443', 'securitydomain-join', '--session',
'4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag',
'--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']'
returned non-zero exit status 255.
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 1038, in spawn
subsystem.join_security_domain(
File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201,
in join_security_domain
subprocess.check_call(cmd)
File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f
/etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join
--session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port
8080 --secure-port 8443 TKS i-dogtag 8443
Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log
Well one issue at a time ... the current install issue first.
Since it worked with the nss in -release I was upgrading this to the new nss.
ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite -
server
ii libnss3:s390x 2:3.63-1ubuntu1 s39
[Touch-packages] [Bug 1937087] Re: 21.04 - Sound hell (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input)
** Also affects: mate-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1937087 Title: 21.04 - Sound hell (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) Status in Ubuntu MATE: New Status in mate-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when restoring the session and that the volume went back to 100% and that the default hardware output felt back to analog stereo duplex ON TOP of that it seems there is a UI defect (look at the picture I will be posting after this). Hope this is clear If not, thanks for letting me know. xo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1937087/+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 1937085] Re: 21.04 - Xerox printer is properly configured and install at OS but not at re-add??
** 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/1937085 Title: 21.04 - Xerox printer is properly configured and install at OS but not at re-add?? Status in Ubuntu MATE: New Status in cups package in Ubuntu: New Bug description: This is kind of a follow-up to: https://bugs.launchpad.net/ubuntu- mate/+bug/1937083 and I am not sure if it needs to be opened or not hence I am opening it as a different bug. I am using a Xerox Versalink C405 printer; I have totally reinstalled UM 21.04-latest as fresh OS; My Xerox Versalink C405 printer has been working fine from LAN and from windoze machines; I have had a "hardware problem" w/ my Xerox printer in Linux and since that problem it stopped working; My solution was to readd the printer (See the bug I opened previously); The bug/problem: I am unable to reinstall Xerox Versalink C405 when adding manually. Why on Earth was the default OS able to install it w/ 0 user interaction but when I need to reinstall it manually from inside the OS it is unable to find it's driver? So what I did was: browse for a driver and look @ /opt/XeroxOffice/prtsys/ppd/XROFFSTD.ppd and have pointed to it = Xerox printer is now installed. But it says "Xerox-CommonXCPT". When I try to print, it doesn't do anything. Here is what /var/log/cups/ entries say about this: ╰─➤ cat page_log C405 dd 988 [21/Jul/2021:09:06:01 -0400] total 0 - localhost Centre de retours en ligne na_letter_8.5x11in_borderless - _xeroxofficetq1_ lp 989 [21/Jul/2021:09:06:01 -0400] total 0 - localhost PrtDrv-m6AN7m - - Xerox-CommonXCPT dd 990 [21/Jul/2021:09:23:34 -0400] total 0 - localhost Centre de retours en ligne na_letter_8.5x11in_borderless - ╭─dd@T-2033.t /var/log/cups ╰─➤ cat error_log E [21/Jul/2021:00:00:02 -0400] Unknown directive BrowseOrder on line 24 of /etc/cups/cupsd.conf. E [21/Jul/2021:00:00:02 -0400] Unknown directive BrowseAllow on line 25 of /etc/cups/cupsd.conf. E [21/Jul/2021:00:00:02 -0400] Unknown browse protocol "CUPS" ignored. E [21/Jul/2021:00:00:02 -0400] Unknown directive BrowseAddress on line 27 of /etc/cups/cupsd.conf. W [21/Jul/2021:00:00:02 -0400] No limit for Validate-Job defined in policy default and no suitable template found. W [21/Jul/2021:00:00:02 -0400] No limit for Cancel-Jobs defined in policy default - using Pause-Printer's policy. W [21/Jul/2021:00:00:02 -0400] No limit for Cancel-My-Jobs defined in policy default - using Send-Document's policy. W [21/Jul/2021:00:00:02 -0400] No limit for Close-Job defined in policy default - using Send-Document's policy. W [21/Jul/2021:00:00:02 -0400] No JobPrivateAccess defined in policy default - using defaults. W [21/Jul/2021:00:00:02 -0400] No JobPrivateValues defined in policy default - using defaults. W [21/Jul/2021:00:00:02 -0400] No SubscriptionPrivateAccess defined in policy default - using defaults. W [21/Jul/2021:00:00:02 -0400] No SubscriptionPrivateValues defined in policy default - using defaults. W [21/Jul/2021:00:00:02 -0400] No limit for Validate-Job defined in policy authenticated - using Print-Job's policy. W [21/Jul/2021:00:00:02 -0400] No limit for Cancel-Jobs defined in policy authenticated - using Pause-Printer's policy. W [21/Jul/2021:00:00:02 -0400] No limit for Cancel-My-Jobs defined in policy authenticated - using Send-Document's policy. W [21/Jul/2021:00:00:02 -0400] No limit for Close-Job defined in policy authenticated - using Send-Document's policy. W [21/Jul/2021:00:00:02 -0400] No JobPrivateAccess defined in policy authenticated - using defaults. W [21/Jul/2021:00:00:02 -0400] No JobPrivateValues defined in policy authenticated - using defaults. W [21/Jul/2021:00:00:02 -0400] No SubscriptionPrivateAccess defined in policy authenticated - using defaults. W [21/Jul/2021:00:00:02 -0400] No SubscriptionPrivateValues defined in policy authenticated - using defaults. E [21/Jul/2021:00:00:02 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [21/Jul/2021:09:08:07 -0400] [CGI] ippfind (PID 4108744) stopped with status 1! E [21/Jul/2021:09:14:39 -0400] [CGI] ippfind (PID 4109374) stopped with status 1! E [21/Jul/2021:09:14:39 -0400] [cups-deviced] PID 4109371 (driverless) stopped with status 1! E [21/Jul/2021:09:19:09 -0400] [CGI] ippfind (PID 4109554) stopped with status 1! As a reminder, the official driver is located @ https://www.support.xerox.com/en-us/product/versalink-c405/downloads My next step will be: 1. purge installed printer; 2. rm -rf /opt/Xerox* 3. Redownload the driver @ support.xerox.com + reinstall + retest; 4. Update you with the result Thanks <3 To manage notifications about this bug go to: https
[Touch-packages] [Bug 1937083] Re: [21.04] Funky new printer (Netowkr printer autofind)
** 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/1937083 Title: [21.04] Funky new printer (Netowkr printer autofind) Status in Ubuntu MATE: New Status in cups package in Ubuntu: New Bug description: Using 21.04-latest on my main desktop, I am using a Xerox Versalink C405 via IPv4 and it always worked pretty good. Boring pre-ambule: I have been running this system for at least 90+ days and yesterday I had the black cartridge being switched for a new one and ever since it doesn't work. (But it still works from a windoze machine). Situation: After being unable to print from Linux my first reaction was to reinstall the printer. I have therefore went under MATE menu -> printers -> add -> Network Printer -> Find Network printer -> Question #1: is it me or in previous UM versions after clicking on "finder network printer" after a couple of seconds it automatically found and configured it? Actually, when installing 21.04 it had automatically found and configured my Xerox printer.. Question #2: Since nothing is auto-discovered after 2+ minutes of waiting in the New printer wizard (Find network printer), I have manually forced the printer's IP into the Host text field and then pressed on FIND. And this is the reason why I am opening this ticket. See the bottom picture because I do not think this is normal PS: The finality is that I am UNABLE to readd this printer. (But again it was automatically installed+configured at OS installation) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1937083/+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 1927078] Re: Don't allow useradd to use fully numeric names
The verification passed for hirsute. jawn-smith@lvm:~$ apt-cache policy passwd passwd: Installed: 1:4.8.1-1ubuntu8 Candidate: 1:4.8.1-1ubuntu8.1 Version table: 1:4.8.1-1ubuntu8.1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 Packages *** 1:4.8.1-1ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status jawn-smith@lvm:~$ sudo useradd 123 jawn-smith@lvm:~$ grep "^123" /etc/passwd 123:x:1001:1001::/home/123:/bin/sh jawn-smith@lvm:~$ sudo userdel 123 jawn-smith@lvm:~$ sudo apt install passwd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: passwd 1 upgraded, 0 newly installed, 0 to remove and 45 not upgraded. Need to get 793 kB of archives. After this operation, 298 kB disk space will be freed. Get:1 http://us.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 passwd amd64 1:4.8.1-1ubuntu8.1 [793 kB] Fetched 793 kB in 0s (1,711 kB/s) (Reading database ... 188906 files and directories currently installed.) Preparing to unpack .../passwd_1%3a4.8.1-1ubuntu8.1_amd64.deb ... Unpacking passwd (1:4.8.1-1ubuntu8.1) over (1:4.8.1-1ubuntu8) ... Setting up passwd (1:4.8.1-1ubuntu8.1) ... Processing triggers for man-db (2.9.4-2) ... jawn-smith@lvm:~$ useradd 123 useradd: invalid user name '123' jawn-smith@lvm:~$ grep "^123" /etc/passwd jawn-smith@lvm:~$ ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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 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/+source/shadow/+bug/1
[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names
The verification passed for focal. jawn-smith@focal-vm:~$ apt-cache policy passwd passwd: Installed: 1:4.8.1-1ubuntu5.20.04 Candidate: 1:4.8.1-1ubuntu5.20.04.1 Version table: 1:4.8.1-1ubuntu5.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages *** 1:4.8.1-1ubuntu5.20.04 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.8.1-1ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages jawn-smith@focal-vm:~$ sudo useradd 123 jawn-smith@focal-vm:~$ grep "^123" /etc/passwd 123:x:1001:1001::/home/123:/bin/sh jawn-smith@focal-vm:~$ sudo userdel 123 jawn-smith@focal-vm:~$ sudo apt install passwd Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-5.8.0-43-generic linux-headers-5.8.0-50-generic linux-hwe-5.8-headers-5.8.0-43 linux-hwe-5.8-headers-5.8.0-50 linux-image-5.8.0-43-generic linux-image-5.8.0-50-generic linux-modules-5.8.0-43-generic linux-modules-5.8.0-50-generic linux-modules-extra-5.8.0-43-generic linux-modules-extra-5.8.0-50-generic Use 'sudo apt autoremove' to remove them. The following packages will be upgraded: passwd 1 upgraded, 0 newly installed, 0 to remove and 49 not upgraded. Need to get 799 kB of archives. After this operation, 1,024 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 passwd amd64 1:4.8.1-1ubuntu5.20.04.1 [799 kB] Fetched 799 kB in 0s (2,027 kB/s) (Reading database ... 275608 files and directories currently installed.) Preparing to unpack .../passwd_1%3a4.8.1-1ubuntu5.20.04.1_amd64.deb ... Unpacking passwd (1:4.8.1-1ubuntu5.20.04.1) over (1:4.8.1-1ubuntu5.20.04) ... Setting up passwd (1:4.8.1-1ubuntu5.20.04.1) ... Processing triggers for man-db (2.9.1-1) ... jawn-smith@focal-vm:~$ sudo useradd 123 useradd: invalid user name '123' jawn-smith@focal-vm:~$ grep "^123" /etc/passwd jawn-smith@focal-vm:~$ ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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 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-sy
[Touch-packages] [Bug 1926062] Autopkgtest regression report (gnome-settings-daemon/3.38.1-3ubuntu3.1)
All autopkgtests for the newly accepted gnome-settings-daemon (3.38.1-3ubuntu3.1) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: indicator-session/17.3.20+21.04.20210327-0ubuntu1 (armhf) 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#gnome-settings-daemon [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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1937087] Re: 21.04 - Sound hell (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input)
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1937087 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Also affects: alsa-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: mate-control-center (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-mate Status: New => Invalid ** Changed in: alsa-tools (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete ** Summary changed: - 21.04 - Sound hell (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) + 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) -- 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/1937087 Title: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) Status in Ubuntu MATE: Invalid Status in alsa-tools package in Ubuntu: Incomplete Status in mate-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when restoring the session and that the volume went back to 100% and that the default hardware output felt back to analog stereo duplex ON TOP of that it seems there is a UI defect (look at the picture I will be posting after this). Hope this is clear If not, thanks for letting me know. xo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1937087/+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 1930738] Re: network configuration failed on reboot
From fresh installation of ubuntu, I simply configured one main and 255
IPv4 address from /24 subnet as mentioned on original post in
/etc/netplan/10-ens3.yaml and this issue occurs. Even tried Ubuntu
20.04.2 LTS, same issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930738
Title:
network configuration failed on reboot
Status in systemd package in Ubuntu:
Incomplete
Bug description:
This issue was reported at
https://github.com/systemd/systemd/issues/17012
**Used distribution**
> Ubuntu 20.04.1 LTS
**systemd version the issue has been seen with**
> 245.4-4ubuntu3.2
**Issue details**
I configured 255 IPv4 address (including primary IP) using netplan but when
the server restart, it time out on configuring the interface. If I limit total
IPv4 addresses to 181 or less, it works. But anything larger than 181 fails.
Below are my configurations and error logs.
**/etc/netplan/10-ens3.yaml**
```
network:
version: 2
renderer: networkd
ethernets:
ens3:
dhcp4: no
addresses:
- 140.XX.XX.XX/23
- 103.XXX.XX.1/24
- 103.XXX.XX.2/24
- CONTINUED IP ADDRESS UPTO BELOW ...
- 103.XXX.XX.254/24
gateway4: 140.XX.XX.X
nameservers:
addresses: [1.1.1.1, 1.0.0.1]
routes:
- to: 169.254.0.0/16
via: 140.XX.XX.X
metric: 100
```
The above config works if I run `netplan apply` but when I reboot, it does
not work.
**networkctl**
```
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 ens3 etherroutablefailed
2 links listed.
```
**/etc/systemd/system/systemd-networkd.service.d/override.conf**
```
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
```
**systemctl status systemd-networkd.service**
```
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service;
enabled-runtime; vendor preset: enabled)
Drop-In: /etc/systemd/system/systemd-networkd.service.d
└─override.conf
Active: active (running) since Thu 2020-09-10 19:46:58 UTC; 1min 36s ago
Docs: man:systemd-networkd.service(8)
Main PID: 346 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 1074)
Memory: 3.8M
CGroup: /system.slice/systemd-networkd.service
└─346 /lib/systemd/systemd-networkd
Sep 10 19:47:03 test-server systemd-networkd[346]: NDISC: Sent Router
Solicitation, next solicitation in 7s
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: No RA received
before link confirmation timeout
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Invoking callback
for 'timeout' event.
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Sent Router
Solicitation, next solicitation in 15s
Sep 10 19:47:23 test-server systemd-networkd[346]: Assertion 'm->sealed'
failed at src/libsystemd/sd-netlink/netlink-message.c:582, function
netlink_message_read_internal(). Ignoring.
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Could not set
address: Connection timed out
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Failed
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: State changed:
configuring -> failed
Sep 10 19:47:23 test-server systemd-networkd[346]: Sent message type=signal
sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sep 10 19:47:23 test-server systemd-networkd[346]: NDISC: Stopping IPv6
Router Solicitation client
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+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 1937117] [NEW] misconfigured networkd may break after networkd restart
Public bug reported: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd-networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. [regression potential] the main potential is for problems for those with misconfigured systems, relying on specific previous incorrect behavior, specifically interfaces controlled by systemd-networkd in part, but also with manual configuration performed outside of systemd-networkd configuration. [scope] this is needed for bionic and focal to restore the previous incorrect behavior; the correct behavior should remain in impish, and (arguably) should remain in hirsute as well [other info] see bug 1929560 for details of the original bug ** Affects: systemd (Ubuntu) Importance: Undecided Status: Invalid ** Affects: systemd (Ubuntu Bionic) Importance: Critical Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Focal) Importance: Critical Assignee: Dan Streetman (ddstreet) Status: In Progress ** Tags: regression-update ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu Focal) Importance: High => Critical ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd- networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. [regression pote
[Touch-packages] [Bug 1929560] Re: link mac isn't set if already up
> This backport to 18.04 LTS broke all our OpenStack compute nodes I've opened bug 1937117 to revert this fix, however keep in mind your networkd configuration is incorrect and should be fixed as you will have problems later if you continue to mix systemd-networkd management of interface(s) as well as manual/external configuration of those same systemd-networkd-managed interface(s). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1929560 Title: link mac isn't set if already up Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: [impact] if link is already up, configured mac isn't set this also affects the master/nomaster configuration [test case] create .network config for the link, for example: [Match] Name=eth0 [Link] MACAddress=00:16:3e:ff:ff:ff [Network] DHCP=yes make sure the link is already up, and restart systemd-networkd: root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# ip l set dev eth0 up root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# systemctl restart systemd-networkd root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# ip l set dev eth0 down root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# systemctl restart systemd-networkd root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:ff:ff:ff brd ff:ff:ff:ff:ff:ff link-netnsid 0 [regression potential] any regression would likely result in incorrectly set link mac and/or master, or failure to correctly set mac and/or master [scope] this is needed for g and earlier this is fixed upstream by commit e16e4b3bedc57919b3ecb4096e941709a5d39b8a which is included in v247 so this is fixed already in h and later [other info] this moves the configuration of the link mac and master out of the link_up() function, so this also allows repeated calls to link_up() without reconfiguring the link mac and master. That behavior is useful for the commits for bug 1664844 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1929560/+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 1937119] [NEW] apt-add-repository --remove -S ... also deletes other components
Public bug reported: apt-add-repository --remove -S deb http://us.archive.ubuntu.com/ubuntu hirsute xyzzx wrongly disables *every* component, not just xyzzx. This happens because the entire existing line is commented out in /etc/apt/sources.list rather than just editing out the deleted component. When *adding* a component, and existing line is edited IN to an existing line for that repository; the reverse should probably be done when removing a component if there are other components which should remain enabled. In other words, commenting out the whole line should be done only if the LINE specified in the remove command specifies all the currently-enabled components. STEPS TO REPRODUCE: 1. sudo cp /etc/apt /tmp/apt.BAK 2. Remove all references to "multiverse" in /etc/apt/sources.list 3. sudo apt-add-repository -y --no-update -S deb http://us.archive.ubuntu.com/ubuntu hirsute multiverse 4. diff -r /etc/apt.BAK /etc/apt (Should show 'multiverse' added to an existing line in /etc/apt/sources.list) diff -r /tmp/apt.BAK/sources.list /etc/apt/sources.list 4,5c4,5 < deb http://us.archive.ubuntu.com/ubuntu hirsute main restricted < # deb-src http://us.archive.ubuntu.com/ubuntu hirsute main restricted --- > deb http://us.archive.ubuntu.com/ubuntu hirsute restricted main multiverse > # deb-src http://us.archive.ubuntu.com/ubuntu hirsute restricted main multiverse 5. sudo apt-add-repository --remove -y --no-update -S deb http://us.archive.ubuntu.com/ubuntu hirsute multiverse 6. diff -r /etc/apt.BAK /etc/apt (Should show 'multiverse' removed from existing line in /etc/apt/sources.list, but...) diff -r /tmp/apt.BAK/sources.list /etc/apt/sources.list 4,5c4,5 < deb http://us.archive.ubuntu.com/ubuntu hirsute main restricted < # deb-src http://us.archive.ubuntu.com/ubuntu hirsute main restricted --- > # deb http://us.archive.ubuntu.com/ubuntu hirsute multiverse restricted main > # deb-src http://us.archive.ubuntu.com/ubuntu hirsute restricted main multiverse (7. sudo rm -rf /etc/apt; sudo cp -a /tmp/apt.BAK /etc/apt) # restore RESULTS: *every* component (including 'main') is disabled EXPECTED RESULTS: Only the specified component is disabled. In other words, --remove should un-do whatever the effect of an 'add' with the same LINE argument ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: software-properties-common 0.99.10 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 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Jul 21 18:02:20 2021 InstallationDate: Installed on 2021-07-20 (0 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute uec-images -- 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/1937119 Title: apt-add-repository --remove -S ... also deletes other components Status in software-properties package in Ubuntu: New Bug description: apt-add-repository --remove -S deb http://us.archive.ubuntu.com/ubuntu hirsute xyzzx wrongly disables *every* component, not just xyzzx. This happens because the entire existing line is commented out in /etc/apt/sources.list rather than just editing out the deleted component. When *adding* a component, and existing line is edited IN to an existing line for that repository; the reverse should probably be done when removing a component if there are other components which should remain enabled. In other words, commenting out the whole line should be done only if the LINE specified in the remove command specifies all the currently- enabled components. STEPS TO REPRODUCE: 1. sudo cp /etc/apt /tmp/apt.BAK 2. Remove all references to "multiverse" in /etc/apt/sources.list 3. sudo apt-add-repository -y --no-update -S deb http://us.archive.ubuntu.com/ubuntu hirsute multiverse 4. diff -r /etc/apt.BAK /etc/apt (Should show 'multiverse' added to an existing line in /etc/apt/sources.list) diff -r /tmp/apt.BAK/sources.list /etc/apt/sources.list 4,5c4,5 < deb http://us.archive.ubuntu.com/ubuntu hirsute main restricted < # deb-src http://us.archive.ubuntu.com/ubuntu hirsute main restricted --- > deb http://us.archive.ubuntu.com/ubuntu hirsute restricted main multiverse > # deb-src http://us.archive.ubuntu.com/ubuntu hirsute restricted main multiverse 5. sudo apt-add-repository --remove -y --no-update -S deb http://us.archive.ubuntu.com/ubuntu hirsute multiverse 6. diff -r /etc/apt.BAK /etc/apt (Should show 'multiverse' rem
[Touch-packages] [Bug 1937117] Re: misconfigured networkd may break after networkd restart
Note that the *proper* way to place eth0 into a bridge while also being under systemd-networkd management is to create a .netdev for the bridge and assign eth0 to it, e.g.: $ cat 10-br0.netdev [NetDev] Name=br0 Kind=bridge cat 10-netplan-eth0.network [Match] Name=eth0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Bridge=br0 [DHCP] RouteMetric=100 UseMTU=true Or alternately, just remove the .network file for 'eth0' so it's not under systemd-networkd control, and manually and/or externally control it (i.e. manually bring up eth0 and manually place it into br0). ** Description changed: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd-networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. + e.g., in a newly created cloud-image container, with normal netplan, + check the networkd control of eth0: + + root@lp1937117-f:~# networkctl list eth0 + IDX LINK TYPE OPERATIONAL SETUP + 159 eth0 ether routableconfigured + + create a new bridge and manually place eth0 into it: + + root@lp1937117-f:~# ip l add dev br0 type bridge + root@lp1937117-f:~# ip l set up dev br0 + root@lp1937117-f:~# ip l set dev eth0 master br0 + root@lp1937117-f:~# ip l show dev eth0 + 159: eth0@if160: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 + link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 + + now restart systemd-networkd, and check if eth0 remains under br0: + + root@lp1937117-f:~# systemctl restart systemd-networkd + root@lp1937117-f:~# ip l show dev eth0 + 159: eth0@if160: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 + link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 + + [regression potential] the main potential is for problems for those with misconfigured systems, relying on specific previous incorrect behavior, specifically interfaces controlled by systemd-networkd in part, but also with manual configuration performed outside of systemd-networkd configuration. [scope] this is needed for bionic and focal to restore the previous incorrect behavior; the correct behavior should remain in impish, and (arguably) should remain in hirsute as well [other info] see bug 1929560 for details of the original bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd- networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different
[Touch-packages] [Bug 1937117] Re: misconfigured networkd may break after networkd restart
** Patch added: "lp1937117-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+attachment/5512598/+files/lp1937117-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd- networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. e.g., in a newly created cloud-image container, with normal netplan, check the networkd control of eth0: root@lp1937117-f:~# networkctl list eth0 IDX LINK TYPE OPERATIONAL SETUP 159 eth0 ether routableconfigured create a new bridge and manually place eth0 into it: root@lp1937117-f:~# ip l add dev br0 type bridge root@lp1937117-f:~# ip l set up dev br0 root@lp1937117-f:~# ip l set dev eth0 master br0 root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 now restart systemd-networkd, and check if eth0 remains under br0: root@lp1937117-f:~# systemctl restart systemd-networkd root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 [regression potential] the main potential is for problems for those with misconfigured systems, relying on specific previous incorrect behavior, specifically interfaces controlled by systemd-networkd in part, but also with manual configuration performed outside of systemd-networkd configuration. [scope] this is needed for bionic and focal to restore the previous incorrect behavior; the correct behavior should remain in impish, and (arguably) should remain in hirsute as well [other info] see bug 1929560 for details of the original bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+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 1937117] Re: misconfigured networkd may break after networkd restart
Attached debdiffs for b/f. Note that Bionic only needs a revert of the patch for the original bug, but Focal requires the patch revert plus an additional small patch to restore the previous behavior, due to other patches added for bug 1664844. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd- networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. e.g., in a newly created cloud-image container, with normal netplan, check the networkd control of eth0: root@lp1937117-f:~# networkctl list eth0 IDX LINK TYPE OPERATIONAL SETUP 159 eth0 ether routableconfigured create a new bridge and manually place eth0 into it: root@lp1937117-f:~# ip l add dev br0 type bridge root@lp1937117-f:~# ip l set up dev br0 root@lp1937117-f:~# ip l set dev eth0 master br0 root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 now restart systemd-networkd, and check if eth0 remains under br0: root@lp1937117-f:~# systemctl restart systemd-networkd root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 [regression potential] the main potential is for problems for those with misconfigured systems, relying on specific previous incorrect behavior, specifically interfaces controlled by systemd-networkd in part, but also with manual configuration performed outside of systemd-networkd configuration. [scope] this is needed for bionic and focal to restore the previous incorrect behavior; the correct behavior should remain in impish, and (arguably) should remain in hirsute as well [other info] see bug 1929560 for details of the original bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+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 1937117] Re: misconfigured networkd may break after networkd restart
** Patch added: "lp1937117-bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+attachment/5512599/+files/lp1937117-bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd- networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. e.g., in a newly created cloud-image container, with normal netplan, check the networkd control of eth0: root@lp1937117-f:~# networkctl list eth0 IDX LINK TYPE OPERATIONAL SETUP 159 eth0 ether routableconfigured create a new bridge and manually place eth0 into it: root@lp1937117-f:~# ip l add dev br0 type bridge root@lp1937117-f:~# ip l set up dev br0 root@lp1937117-f:~# ip l set dev eth0 master br0 root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 now restart systemd-networkd, and check if eth0 remains under br0: root@lp1937117-f:~# systemctl restart systemd-networkd root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 [regression potential] the main potential is for problems for those with misconfigured systems, relying on specific previous incorrect behavior, specifically interfaces controlled by systemd-networkd in part, but also with manual configuration performed outside of systemd-networkd configuration. [scope] this is needed for bionic and focal to restore the previous incorrect behavior; the correct behavior should remain in impish, and (arguably) should remain in hirsute as well [other info] see bug 1929560 for details of the original bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Fixed for me, I have suspended laptop and after that I still could turn on bluetooth, before that it didn't work Ubuntu 21.04 3.38.1-3ubuntu3.1 -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1937126] [NEW] bug found
Public bug reported: I downloaded version 21.04 of ubuntu, then I realized that when I downloaded the gnome shell tweaking tool, I realized that when I changed the theme of the dock and added in the top bar the option to show the option of locations on the system, it leaves my language after performing some accesses in the application menu this behavior appears. I also noticed that by accessing the applications menu the dock that I modified to appear in the lower corner of the screen is now also displayed on the left side of my monitor. I apologize for the English, but I live in Brazil and I am not fluent in this language. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 16:23:56 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a] InstallationDate: Installed on 2021-07-17 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 002: ID :3825 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81S9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 1.50 dmi.bios.vendor: LENOVO dmi.bios.version: ASCN50WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IWL dmi.ec.firmware.release: 1.50 dmi.modalias: dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL: dmi.product.family: IdeaPad S145-15IWL dmi.product.name: 81S9 dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL dmi.product.version: Lenovo IdeaPad S145-15IWL dmi.sys.vendor: LENOVO 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 wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1937126 Title: bug found Status in xorg package in Ubuntu: New Bug description: I downloaded version 21.04 of ubuntu, then I realized that when I downloaded the gnome shell tweaking tool, I realized that when I changed the theme of the dock and added in the top bar the option to show the option of locations on the system, it leaves my language after performing some accesses in the application menu this behavior appears. I also noticed that by accessing the applications menu the dock that I modified to appear in the lower corner of the screen is now also displayed on the left side of my monitor. I apologize for the English, but I live in Brazil and I am not fluent in this language. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 16:23:56 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: in
[Touch-packages] [Bug 1937071] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937071 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: it does not complete the update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 19:16:15 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-07-28 (1089 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-05 (288 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937071/+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 1937071] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937071 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: it does not complete the update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 19:16:15 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-07-28 (1089 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-05 (288 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937071/+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 1937071] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Hello Rucel, my guess is you've installed the lilo package. This is not supported. If you can identify a bugfix it could probably be integrated but honestly it'd be easier to either figure out how to use grub in your environment or switch to another distribution that does support using lilo. Grub just works for most people, and it should work for you, too. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937071 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: it does not complete the update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 19:16:15 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-07-28 (1089 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-05 (288 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937071/+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 1927078] Autopkgtest regression report (shadow/1:4.8.1-1ubuntu5.20.04.1)
All autopkgtests for the newly accepted shadow (1:4.8.1-1ubuntu5.20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: mysql-8.0/8.0.25-0ubuntu0.20.04.1 (arm64, i386, ppc64el, amd64) 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/focal/update_excuses.html#shadow [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 shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names 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/+source/shadow/+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 1927078] Autopkgtest regression report (shadow/1:4.8.1-1ubuntu8.1)
All autopkgtests for the newly accepted shadow (1:4.8.1-1ubuntu8.1) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: mysql-8.0/8.0.25-0ubuntu0.21.04.1 (i386, ppc64el, amd64, arm64) 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#shadow [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 shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names 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/+source/shadow/+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 1937132] [NEW] package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meggs 940 F pulseaudio /dev/snd/pcmC0D0p: meggs 940 F...m pulseaudio CasperMD5CheckResult: unknown Date: Thu Jul 22 07:49:35 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=15bb9107-24ab-4a84-b6e4-81535fd81dce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu45 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (69 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: G31M-S2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/05/2009:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937132 Title: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meggs 940 F pulseaudio /dev/snd/pcmC0D0p: meggs 940 F...m pulseaudio CasperMD5CheckResult: unknown Date: Thu Jul 22 07:49:35 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=15bb9107-24ab-4a84-b6e4-81535fd81dce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu45 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (69 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: G31M-S2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/05/2009:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage no
[Touch-packages] [Bug 1937132] Re: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937132 Title: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meggs 940 F pulseaudio /dev/snd/pcmC0D0p: meggs 940 F...m pulseaudio CasperMD5CheckResult: unknown Date: Thu Jul 22 07:49:35 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=15bb9107-24ab-4a84-b6e4-81535fd81dce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu45 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (69 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: G31M-S2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/05/2009:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937132/+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 1937117] Re: misconfigured networkd may break after networkd restart
This bug was fixed in the package systemd - 245.4-4ubuntu3.11 --- systemd (245.4-4ubuntu3.11) focal-security; urgency=medium * d/p/lp1937117/0001-revert-lp1929560-network-move-set-MAC-and-set-nomaster-operations-out.patch, d/p/lp1937117/0002-avoid-changing-interface-master-if-interface-already-up.patch: - Don't change interface master if interface is already up, due to users expecting previous buggy behavior (LP: #1937117) -- Dan Streetman Wed, 21 Jul 2021 15:00:21 -0400 ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd- networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. e.g., in a newly created cloud-image container, with normal netplan, check the networkd control of eth0: root@lp1937117-f:~# networkctl list eth0 IDX LINK TYPE OPERATIONAL SETUP 159 eth0 ether routableconfigured create a new bridge and manually place eth0 into it: root@lp1937117-f:~# ip l add dev br0 type bridge root@lp1937117-f:~# ip l set up dev br0 root@lp1937117-f:~# ip l set dev eth0 master br0 root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 now restart systemd-networkd, and check if eth0 remains under br0: root@lp1937117-f:~# systemctl restart systemd-networkd root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 [regression potential] the main potential is for problems for those with misconfigured systems, relying on specific previous incorrect behavior, specifically interfaces controlled by systemd-networkd in part, but also with manual configuration performed outside of systemd-networkd configuration. [scope] this is needed for bionic and focal to restore the previous incorrect behavior; the correct behavior should remain in impish, and (arguably) should remain in hirsute as well [other info] see bug 1929560 for details of the original bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+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 804178] Re: "Front" ALSA volume control affects headphones on some machines
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/804178 Title: "Front" ALSA volume control affects headphones on some machines Status in pulseaudio package in Ubuntu: Expired Bug description: There is no sound playing through my headphones, nor through my computer speakers. They worked for a moment, but stopped abruptly. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 20' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,103c2a9e,00100202' Controls : 35 Simple ctrls : 20 Date: Fri Jul 1 07:59:15 2011 LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Internal Audio - HDA NVidia Symptom_DevicesInUse: 4622 10827 Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [AY020AA-ABA p6320f, Realtek ALC888, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: VIOLET6 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 6.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/12/2009:svnHP-Pavilion:pnAY020AA-ABAp6320f:pvr:rvnPEGATRONCORPORATION:rnVIOLET6:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: AY020AA-ABA p6320f dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/804178/+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 1937117] Re: misconfigured networkd may break after networkd restart
This bug was fixed in the package systemd - 237-3ubuntu10.50 --- systemd (237-3ubuntu10.50) bionic-security; urgency=medium * d/p/lp1937117-revert-lp1929560-network-move-set-MAC-and-set-nomaster-operations-out.patch: Revert patch due to users expecting previous buggy behavior (LP: #1937117) -- Dan Streetman Wed, 21 Jul 2021 14:51:38 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd- networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. e.g., in a newly created cloud-image container, with normal netplan, check the networkd control of eth0: root@lp1937117-f:~# networkctl list eth0 IDX LINK TYPE OPERATIONAL SETUP 159 eth0 ether routableconfigured create a new bridge and manually place eth0 into it: root@lp1937117-f:~# ip l add dev br0 type bridge root@lp1937117-f:~# ip l set up dev br0 root@lp1937117-f:~# ip l set dev eth0 master br0 root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 now restart systemd-networkd, and check if eth0 remains under br0: root@lp1937117-f:~# systemctl restart systemd-networkd root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 [regression potential] the main potential is for problems for those with misconfigured systems, relying on specific previous incorrect behavior, specifically interfaces controlled by systemd-networkd in part, but also with manual configuration performed outside of systemd-networkd configuration. [scope] this is needed for bionic and focal to restore the previous incorrect behavior; the correct behavior should remain in impish, and (arguably) should remain in hirsute as well [other info] see bug 1929560 for details of the original bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: 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 Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1937132] Re: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937132 Title: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meggs 940 F pulseaudio /dev/snd/pcmC0D0p: meggs 940 F...m pulseaudio CasperMD5CheckResult: unknown Date: Thu Jul 22 07:49:35 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=15bb9107-24ab-4a84-b6e4-81535fd81dce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu45 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (69 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: G31M-S2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/05/2009:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937132/+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 1937126] Re: bug found
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1937126 Title: bug found Status in gnome-shell package in Ubuntu: New Bug description: I downloaded version 21.04 of ubuntu, then I realized that when I downloaded the gnome shell tweaking tool, I realized that when I changed the theme of the dock and added in the top bar the option to show the option of locations on the system, it leaves my language after performing some accesses in the application menu this behavior appears. I also noticed that by accessing the applications menu the dock that I modified to appear in the lower corner of the screen is now also displayed on the left side of my monitor. I apologize for the English, but I live in Brazil and I am not fluent in this language. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 16:23:56 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a] InstallationDate: Installed on 2021-07-17 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 002: ID :3825 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81S9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 1.50 dmi.bios.vendor: LENOVO dmi.bios.version: ASCN50WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IWL dmi.ec.firmware.release: 1.50 dmi.modalias: dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL: dmi.product.family: IdeaPad S145-15IWL dmi.product.name: 81S9 dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL dmi.product.version: Lenovo IdeaPad S145-15IWL dmi.sys.vendor: LENOVO 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+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
According to #15, it looks like the topology file is not suitable for this machine. Please file a bug to Intel/sof, let Intel engineers take a look at this issue. https://github.com/thesofproject/linux/issues/new -- 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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
^^^ ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1937080] Re: Screen tearing & mouse cursor glitch
Thanks for the bug report. This sounds like several unrelated issues. Please choose a single issue for this bug to be about. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1937080 Title: Screen tearing & mouse cursor glitch Status in Ubuntu: Incomplete Bug description: screen tearing and cursor glitch screen, When I type something it display after 2sec high latency on display. I have installed almost 25 linux distro almost all ubuntu flavors and arch linux distro all have same problem. I think it is kernal issue. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 18:10:10 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1937080/+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 1937072] Re: Screen tearing & mouse cursor glitch with unable change brightness of my display
Thanks for the bug report. This sounds like several unrelated issues. Please choose a single issue for this bug to be about. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1937072 Title: Screen tearing & mouse cursor glitch with unable change brightness of my display Status in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1937072/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Test on HP desktop with following steps 1. Open gnome-control-center and select Wi-Fi 2. Turn off Wi-Fi via UI 3. Select Bluetooth column 4. Turn off Bluetooth via UI 5. Turn Off AirPlane Mode in Bluetooth menu Bluetooth works fine. [OS] Focal ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1930945] Re: ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg)
** Description changed: Ubuntu Desktop Impish daily test on - - - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) + - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) Changing display positions in settings. I have two monitors, one above the other (so not the default). I made change and it looked okay so I said keep. I noticed I was wrong having TOP/BOTTOM displays the wrong way (detected via mouse movements between displays) so I made another change of the TOP/BOTTOM displays in "DISPLAYS" of GNOME settings clicked apply again & keep... ** Expected Results On changing display orientation I expect wallpaper to be redrawn, or remain on screen ** Actual Results I now have BLUE background on both displays. (this was soon changing.. but that didn't occur until I tried to change wallpapers...) /var/crash is empty... operation appears normal; I lost background. lots of TRAP messages though fill `dmesg` ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-desktop 1.469 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 5 03:01:52 2021 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Package changed: ubuntu-meta (Ubuntu) => gnome-shell (Ubuntu) -- 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/1930945 Title: ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg) Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu Desktop Impish daily test on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) Changing display positions in settings. I have two monitors, one above the other (so not the default). I made change and it looked okay so I said keep. I noticed I was wrong having TOP/BOTTOM displays the wrong way (detected via mouse movements between displays) so I made another change of the TOP/BOTTOM displays in "DISPLAYS" of GNOME settings clicked apply again & keep... ** Expected Results On changing display orientation I expect wallpaper to be redrawn, or remain on screen ** Actual Results I now have BLUE background on both displays. (this was soon changing.. but that didn't occur until I tried to change wallpapers...) /var/crash is empty... operation appears normal; I lost background. lots of TRAP messages though fill `dmesg` ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-desktop 1.469 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 5 03:01:52 2021 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/gnome-shell/+bug/1930945/+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
