[Touch-packages] [Bug 1853567] Re: Bluetooth keyboard after upgrade consumes rapidly battery
Ubuntu 19.04 and 19.10 use the same version of BlueZ so I doubt that's the issue. Are you able to try some different kernel versions? https://kernel.ubuntu.com/~kernel-ppa/mainline/ ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Tags added: eoan -- 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/1853567 Title: Bluetooth keyboard after upgrade consumes rapidly battery Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from ubuntu 19.04 to 19.10 the bluetooth keyboard Logitech K810 is consuming faster the battery. Now it needs recharging almost every week, while with 19.04 it was every couple of months. My impression is that either the kernel or the bluez is pinging more often the keyboard and doesn't let it sleep when not in use. There was a similar problem some years ago and with an updated kernel it was fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853567/+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 1853567] [NEW] Bluetooth keyboard after upgrade consumes rapidly battery
You have been subscribed to a public bug: After upgrading from ubuntu 19.04 to 19.10 the bluetooth keyboard Logitech K810 is consuming faster the battery. Now it needs recharging almost every week, while with 19.04 it was every couple of months. My impression is that either the kernel or the bluez is pinging more often the keyboard and doesn't let it sleep when not in use. There was a similar problem some years ago and with an updated kernel it was fixed. ** Affects: bluez (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- Bluetooth keyboard after upgrade consumes rapidly battery https://bugs.launchpad.net/bugs/1853567 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853567] Re: Bluetooth keyboard after upgrade consumes rapidly battery
** Package changed: linux (Ubuntu) => bluez (Ubuntu) -- 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/1853567 Title: Bluetooth keyboard after upgrade consumes rapidly battery Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from ubuntu 19.04 to 19.10 the bluetooth keyboard Logitech K810 is consuming faster the battery. Now it needs recharging almost every week, while with 19.04 it was every couple of months. My impression is that either the kernel or the bluez is pinging more often the keyboard and doesn't let it sleep when not in use. There was a similar problem some years ago and with an updated kernel it was fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853567/+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 1856298] [NEW] Tried to start xdiagnose and got error.
Public bug reported: No more details that I know other than what's in the summary. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Dec 13 03:32:46 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04d8] InstallationDate: Installed on 2019-12-06 (7 days ago) InstallationMedia: It MachineType: Dell Inc. Dell System Inspiron N7110 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=29f55db3-5639-47d5-82af-087cfc3e019d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 05VJ58 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd09/05/2012:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn05VJ58:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System Inspiron N7110 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1856298 Title: Tried to start xdiagnose and got error. Status in xorg package in Ubuntu: New Bug description: No more details that I know other than what's in the summary. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Dec 13 03:32:46 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04d8] InstallationDate: Installed on 2019-12-06 (7 days ago) InstallationMedia: It MachineType: Dell Inc. Dell System Inspiron N7110 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=29f55db3-5639-47d5-82af-087cfc3e019d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 05VJ58 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd09/05/2012:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn05VJ58:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System Inspiron N7110 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2:
[Touch-packages] [Bug 1827958] Re: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system
Any solution for that bug ? I'm on Manjaro and I've this bug too. -- 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/1827958 Title: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system Status in alsa-driver package in Ubuntu: New Bug description: The inbuilt microphone has never worked on the version of ubuntu on this computer. The hardware works completely fine on other operating systems (Windows). Distribution: Ubuntu 18.04.2 LTS alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:54:58 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 1 0 3 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1273 F pulseaudio lune 1908 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827958/+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 1856298] Re: Tried to start xdiagnose and got error.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (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/1856298 Title: Tried to start xdiagnose and got error. Status in xorg package in Ubuntu: Incomplete Bug description: No more details that I know other than what's in the summary. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Dec 13 03:32:46 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04d8] InstallationDate: Installed on 2019-12-06 (7 days ago) InstallationMedia: It MachineType: Dell Inc. Dell System Inspiron N7110 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=29f55db3-5639-47d5-82af-087cfc3e019d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 05VJ58 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd09/05/2012:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn05VJ58:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System Inspiron N7110 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856298/+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 1791245] Re: bonding 802.3ad with systemd-networkd: duplicate MAC address on 2 different hosts
** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1791245 Title: bonding 802.3ad with systemd-networkd: duplicate MAC address on 2 different hosts Status in systemd package in Ubuntu: Invalid Bug description: The problem seems to incriminate systemd-networkd (v229-4ubuntu21.1), not the network/bonding configuration. When a full bonding configuration is made with systemd in /etc/systemd/network, on 2 two differents physical hosts, same hardware and in same VLAN: - bond0.netdev -- [NetDev] Name=bond0 Kind=bond [Bond] Mode=802.3ad TransmitHashPolicy=layer3+4 MIIMonitorSec=100ms LACPTransmitRate=fast - vlan3147.netdev -- [NetDev] Name=vlan3147 Kind=vlan [VLAN] Id=3147 - bond0.network -- [Match] Name=bond0 [Network] VLAN=vlan3147 BindCarrier=enp1s0f1 enp1s0f0 LinkLocalAddressing=no - enp1s0f0.network -- [Match] Name=enp1s0f0 [Network] Bond=bond0 - enp1s0f1.network -- [Match] Name=enp1s0f1 [Network] Bond=bond0 - vlan3147.network -- [Match] Name=vlan3147 [Address] Address=**masked ip***/25 [Route] Destination=10.0.0.0/8 Gateway=**masked ip*** [Route] Destination=**masked ip***/16 Gateway=**masked ip*** And in /etc/modprobe.d/bonding.conf options bonding max_bonds=0 . the two different physicals hosts have the same MAC address on bonding: on host A: 32: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 16:d6:b0:24:16:3b brd ff:ff:ff:ff:ff:ff on host B: 32: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 16:d6:b0:24:16:3b brd ff:ff:ff:ff:ff:ff So strange... how the MAC is generated ? There is no relevant rules in /etc/udev/rules.d/70-persistent-net.rules to explain it, and issue occurs only with systemd-network, *NOT* with legacy configuration /etc/network/interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1791245/+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 1826459] Re: systemd-networkd not installing GatewayOnlink=true
> addresses: [ 95.216.96.148/26 ] > gateway4: 95.216.96.129 here you are configuring your default gateway as 95.216.96.129; all traffic outside your "subnet" will be routed to it. > - to: 95.216.96.128/26 > via: 95.216.96.129 > on-link: true now, you're trying to say that you can't actually reach anything in your /26 "subnet", so actually, *all* your traffic should be routed to the gateway. so what you're doing is actually misconfiguring your network; you're trying to set up your address with a /26 subnet, but in reality you have a /32 subnet. Try this config instead: ethernets: enp0s31f6: addresses: [ 95.216.96.148/32 ] nameservers: addresses: - "8.8.8.8" - "1.1.1.1" routes: - to: 0.0.0.0/0 via: 95.216.96.129 on-link: true ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: netplan Status: New => Invalid -- 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/1826459 Title: systemd-networkd not installing GatewayOnlink=true Status in netplan: Invalid Status in systemd package in Ubuntu: Invalid Bug description: root@search-3 /run/systemd/network # for i in *; do echo $i; echo; cat $i; done ; sudo service systemd-networkd stop; SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd 10-netplan-enp0s31f6.network [Match] Name=enp0s31f6 [Network] LinkLocalAddressing=ipv6 Address=95.216.96.148/26 Gateway=95.216.96.129 DNS=8.8.8.8 DNS=1.1.1.1 Domains=148.96.216.95.clients.your-server.de VLAN=vlan4000 [Route] Destination=95.216.96.148/26 Gateway=95.216.96.129 GatewayOnlink=true 10-netplan-vlan4000.netdev [NetDev] Name=vlan4000 MTUBytes=1400 Kind=vlan [VLAN] Id=4000 10-netplan-vlan4000.network [Match] Name=vlan4000 [Network] LinkLocalAddressing=ipv6 Address=10.0.2.3/24 ConfigureWithoutCarrier=yes Failed to read $container of PID 1, ignoring: Permission denied Found container virtualization none. Bus n/a: changing state UNSET → OPENING Bus n/a: changing state OPENING → AUTHENTICATING Failed to open configuration file '/etc/systemd/networkd.conf': No such file or directory timestamp of '/etc/systemd/network' changed timestamp of '/run/systemd/network' changed Ignoring /run/systemd/network/10-netplan-enp0s31f6.network, because it's not a regular file with suffix .netdev. Ignoring /run/systemd/network/10-netplan-vlan4000.network, because it's not a regular file with suffix .netdev. Ignoring /lib/systemd/network/99-default.link, because it's not a regular file with suffix .netdev. Ignoring /lib/systemd/network/80-container-vz.network, because it's not a regular file with suffix .netdev. Ignoring /lib/systemd/network/80-container-ve.network, because it's not a regular file with suffix .netdev. Ignoring /lib/systemd/network/80-container-host0.network, because it's not a regular file with suffix .netdev. vlan4000: loaded vlan Ignoring /run/systemd/network/10-netplan-vlan4000.netdev, because it's not a regular file with suffix .network. Ignoring /lib/systemd/network/99-default.link, because it's not a regular file with suffix .network. tun0: MAC address not found for new device, continuing without tun0: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +POINTOPOINT +NOARP tun0: Link 12 added tun0: udev initialized link tun0: Saved original MTU: 1500 veth20a5a67: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST veth20a5a67: Link 8 added veth20a5a67: udev initialized link veth20a5a67: Saved original MTU: 1500 vlan4000: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST vlan4000: Link 6 added vlan4000: udev initialized link vlan4000: netdev has index 6 vlan4000: Saved original MTU: 1400 br-c7cc901345e8: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST br-c7cc901345e8: Link 5 added br-c7cc901345e8: udev initialized link br-c7cc901345e8: Saved original MTU: 1500 docker0: Flags change: +UP +MULTICAST +BROADCAST docker0: Link 3 added docker0: udev initialized link docker0: Saved original MTU: 1500 enp0s31f6: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST enp0s31f6: Link 2 added enp0s31f6: udev initialized link enp0s31f6: Saved original MTU: 1500 lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING lo: Link 1 added lo: udev initialized link lo: Saved original MTU: 0 vlan4000: Adding address: fe80::921b:eff:fe93:5015/64 (valid forever) vlan4000: Gained IPv6LL tun0: Adding address: 10.0.0.13/24 (valid forever) vlan4000: Adding address: 10.0.2.3/24 (valid forever) br-c7cc901345e8: Adding address: 172.18.0.1/16 (valid forever) docker0: Adding address: 172.17.0.1/16 (valid forever) enp0s31f6: Adding address: 95.216.96.148/26 (valid
[Touch-packages] [Bug 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs
** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu) Status: New => In Progress -- 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/1841157 Title: have /usr/bin/oem-getlogs in apport to collect all in one logs Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: In Progress Bug description: plan to use command like $ sudo oem-getlogs to collect all logs that oem project could need. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1841157/+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 1849261] Re: Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart=
** Description changed: [impact] services configured with both OnFailure= and Restart= directives will both start the failure service(s), as well as restarting itself. The documentation (and later versions) indicate that OnFailure= services will only be started once the service actually does stop (due to failure) once its restart limit has been exceeded. [test case] create service files as: - ubuntu@lp1849261-b:/etc/systemd/system$ cat test.service + ubuntu@lp1849261-b:/etc/systemd/system$ cat test.service [Unit] OnFailure=failure.service [Service] ExecStart=/bin/sh -c '/bin/sleep 10; /bin/false' Restart=always - ubuntu@lp1849261-b:/etc/systemd/system$ cat failure.service + ubuntu@lp1849261-b:/etc/systemd/system$ cat failure.service [Service] ExecStart=/bin/true - perform daemon-reload, and then start test service: - ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl daemon-reload + ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl daemon-reload ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl start test wait for a while for the test service to exit - at least 10 seconds, as that's what we configured in the service, although I have waited longer in this example. Then check the journal for both test and failure services: ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u test -- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:18:34 UTC. -- Dec 13 01:17:43 lp1849261-b systemd[1]: Started test.service. Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 1. Dec 13 01:17:53 lp1849261-b systemd[1]: Stopped test.service. Dec 13 01:17:53 lp1849261-b systemd[1]: Started test.service. Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 2. Dec 13 01:18:04 lp1849261-b systemd[1]: Stopped test.service. Dec 13 01:18:04 lp1849261-b systemd[1]: Started test.service. Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 3. Dec 13 01:18:14 lp1849261-b systemd[1]: Stopped test.service. Dec 13 01:18:14 lp1849261-b systemd[1]: Started test.service. Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 4. Dec 13 01:18:24 lp1849261-b systemd[1]: Stopped test.service. Dec 13 01:18:24 lp1849261-b systemd[1]: Started test.service. Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 5. Dec 13 01:18:34 lp1849261-b systemd[1]: Stopped test.service. Dec 13 01:18:34 lp1849261-b systemd[1]: Started test.service. - ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u failure -- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:19:15 UTC. -- Dec 13 01:17:53 lp1849261-b systemd[1]: Started failure.service. Dec 13 01:18:03 lp1849261-b systemd[1]: Started failure.service. Dec 13
[Touch-packages] [Bug 1664844] Re: No distinction between link-up and link-down interfaces
** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Bug description: [Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+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 1806012] Re: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server
as the merge request for this was rejected as not needed, i'm marking this bug as wontfix. ** Changed in: systemd (Ubuntu Disco) Status: In Progress => Won't Fix ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Won't Fix ** Changed in: systemd (Ubuntu Cosmic) Status: In Progress => Won't Fix ** Changed in: systemd (Ubuntu) Status: In Progress => Won't Fix -- 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/1806012 Title: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server Status in systemd package in Ubuntu: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Won't Fix Bug description: Whilst debugging 'slow instance performance' on a Ubuntu Bionic based cloud, I observed that the default cpu governor configuration was set to 'powersave'; toggling this to 'performance' (while in not anyway a particularly green thing todo) resulted in the instance slowness disappearing and the cloud performance being as expected (based on a prior version of the deploy on Ubuntu Xenial). AFAICT Xenial does the same thing albeit in a slight different way, but we definitely did not see the same performance laggy-ness under a Xenial based cloud. Raising against systemd (as this package sets the governor to 'powersave') - I feel that the switch to 'performance' although appropriate then obscures what might be a performance/behavioural difference in the underlying kernel when a machine is under load. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 30 10:05:46 2018 Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt intel_iommu=on SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012/+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 1846232] Re: networkd pads interface MTU by 4 bytes for vlan even when told not to
** Description changed: [impact] vlan interface has wrong mtu, which may cause lost packets due to incorrect mtu [test case] configure a system using the netplan cfg similar to comment 2. alternately, networkd config can be used, similar to: ubuntu@lp1846232-e:/run/systemd/network$ grep . * 10-netplan-ens3.2667.netdev:[NetDev] 10-netplan-ens3.2667.netdev:Name=ens3.2667 10-netplan-ens3.2667.netdev:MTUBytes=1500 10-netplan-ens3.2667.netdev:Kind=vlan 10-netplan-ens3.2667.netdev:[VLAN] 10-netplan-ens3.2667.netdev:Id=2667 10-netplan-ens3.2667.network:[Match] 10-netplan-ens3.2667.network:Name=ens3.2667 10-netplan-ens3.2667.network:[Network] 10-netplan-ens3.2667.network:LinkLocalAddressing=ipv6 10-netplan-ens3.2667.network:Address=1.2.3.4/32 10-netplan-ens3.2667.network:ConfigureWithoutCarrier=yes 10-netplan-ens3.link:[Match] 10-netplan-ens3.link:OriginalName=ens3 10-netplan-ens3.link:[Link] 10-netplan-ens3.link:WakeOnLan=off 10-netplan-ens3.link:MTUBytes=1500 10-netplan-ens3.network:[Match] 10-netplan-ens3.network:Name=ens3 10-netplan-ens3.network:[Network] 10-netplan-ens3.network:LinkLocalAddressing=ipv6 10-netplan-ens3.network:VLAN=ens3.2667 - The reboot and check the mtus: ubuntu@lp1846232-e:~$ ip l show ens3 2: ens3: mtu 1504 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 - link/ether 52:54:00:12:99:1b brd ff:ff:ff:ff:ff:ff + link/ether 52:54:00:12:99:1b brd ff:ff:ff:ff:ff:ff ubuntu@lp1846232-e:~$ ip l show ens3.2667 3: ens3.2667@ens3: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 - link/ether 52:54:00:12:99:1b brd ff:ff:ff:ff:ff:ff - + link/ether 52:54:00:12:99:1b brd ff:ff:ff:ff:ff:ff The base interface should have a mtu of only 1500. [regression potential] As this corrects/adjusts the mtu of the interface, regressions would likely involve interface(s) being assigned incorrect mtu values, which then would lead to dropped packets and/or lowered network performance. + [scope] + + this is needed only for Eoan. + + disco and earlier don't have the patch that introduces this problem, + commit 4b151b71320bbee1549afcbad5554a40d90d63b4 + + focal already has the patches that fix this, commit + f6fcc1c2a41eae749467de58453174296b635a69 (and the commit before it) + + see comment 4 for more details + [other info] - disco and earlier don't have the patch that introduces this problem, and - focal already has the patch that fixes this (see comment 4 for details), - so this is needed only for eoan. - original description: --- - From https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel- amd64/916/console: == FAIL: test_ip_output (vmtests.test_network_vlan.EoanTestNetworkVlan) -- Traceback (most recent call last): File "/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py", line 311, in test_ip_output routes) File "/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py", line 337, in check_interface int(ipcfg[key])) AssertionError: 1500 != 1504 >> begin captured stdout << - parsed ip_a dict: interface0: broadcast: 10.245.175.255 group: default inet4: - address: 10.245.168.16 prefixlen: '21' scope: global valid_lft: forever inet6: - address: fec0::d6be:d9ff:fea8:4913 prefixlen: '64' scope: site valid_lft: 86256sec - address: fe80::d6be:d9ff:fea8:4913 prefixlen: '64' scope: link valid_lft: forever interface: interface0 loopback: false lower_up: false mac_address: d4:be:d9:a8:49:13 mtu: '1500' multicast: false qdisc: fq_codel qlen: '1000' running: false state: UP up: false interface1: broadcast: 10.245.188.255 group: default inet4: - address: 10.245.188.2 prefixlen: '24' scope: global valid_lft: forever inet6: - address: fec0::d6be:d9ff:fea8:4915 prefixlen: '64' scope: site valid_lft: 86256sec - address: fe80::d6be:d9ff:fea8:4915 prefixlen: '64' scope: link valid_lft: forever interface: interface1 loopback: false lower_up: false mac_address: d4:be:d9:a8:49:15 mtu: '1504' multicast: false qdisc: fq_codel qlen: '1000' running: false state: UP up: false interface1.2667: broadcast: 10.245.184.255 group: default inet4: - address: 10.245.184.2 prefixlen: '24'
[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU
** Also affects: cloud-init (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: systemd (Ubuntu Focal) Importance: Medium Status: Fix Released ** Also affects: netplan.io (Ubuntu Focal) Importance: Undecided Status: Fix Released ** Also affects: cloud-init (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Eoan) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #13914 https://github.com/systemd/systemd/issues/13914 ** Also affects: systemd via https://github.com/systemd/systemd/issues/13914 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu Focal) Status: Fix Released => In Progress ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Disco) Status: Triaged => In Progress ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: Balint Reczey (rbalint) => Dan Streetman (ddstreet) ** Changed in: netplan.io (Ubuntu Eoan) Status: New => Fix Released ** Tags added: bionic ddstreet disco eoan focal systemd -- 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd: Unknown Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: Fix Released Status in systemd source package in Bionic: In Progress Status in cloud-init source package in Disco: New Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: In Progress Status in cloud-init source package in Eoan: New Status in netplan.io source package in Eoan: Fix Released Status in systemd source package in Eoan: In Progress Status in cloud-init source package in Focal: Confirmed Status in netplan.io source package in Focal: Fix Released Status in systemd source package in Focal: In Progress Bug description: = netplan.io = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Apply a netplan configuration that specifices ipv6-mtu: network: version: 2 ethernets: eth0: dhcp4: true dhcp6: true ipv6-mtu: 6000 * Check that MTU bytes, is at least IPv6MTUBytes on the interface: $ sysctl net.ipv6.conf.eth0.mtu net.ipv6.conf.eth0.mtu = 6000 [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of netplan.io = = systemd = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Use IPv6MTUBytes= setting in a .network unit * Restart systemd-network * Check that there no error messages / warnings about not-recognizing this option * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where
[Touch-packages] [Bug 1856330] [NEW] journalctl missing grep
Public bug reported: the man page for journalctl and the usage (journalctl --help) advertise an option (-g, --grep=) to grep the MESSAGE portion of events for a pcre pattern. journalctl is linked against libpcre, but doesn't recognize the option when used. $ journalctl -g dhcp journalctl: invalid option -- 'g' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573660262~18.04~d11b582~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 09:26:08 2019 MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=UUID=25721613-9f9a-4e8d-ac61-a6869852d0e2 ro ipv6.disable=1 usbhid.quirks=0x1B1C:0x1B13:0x400 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-10-05 (433 days ago) dmi.bios.date: 06/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0411 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: Desktop dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0411:bd06/28/2013:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrDesktop: dmi.product.family: ASUS MB dmi.product.name: Wild Dog Performance dmi.product.sku: All dmi.product.version: wilp10 dmi.sys.vendor: System76, Inc. mtime.conffile..etc.systemd.resolved.conf: 2018-10-08T15:18:41.655856 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1856330 Title: journalctl missing grep Status in systemd package in Ubuntu: New Bug description: the man page for journalctl and the usage (journalctl --help) advertise an option (-g, --grep=) to grep the MESSAGE portion of events for a pcre pattern. journalctl is linked against libpcre, but doesn't recognize the option when used. $ journalctl -g dhcp journalctl: invalid option -- 'g' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573660262~18.04~d11b582~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 09:26:08 2019 MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=UUID=25721613-9f9a-4e8d-ac61-a6869852d0e2 ro ipv6.disable=1 usbhid.quirks=0x1B1C:0x1B13:0x400 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-10-05 (433 days ago) dmi.bios.date: 06/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0411 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: Desktop dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0411:bd06/28/2013:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrDesktop: dmi.product.family: ASUS MB dmi.product.name: Wild Dog Performance dmi.product.sku: All dmi.product.version: wilp10 dmi.sys.vendor: System76, Inc. mtime.conffile..etc.systemd.resolved.conf: 2018-10-08T15:18:41.655856 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1856330/+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 1823171] Re: systemd-resolve hides DS records in explicit queries
** Changed in: systemd (Ubuntu) Status: In Progress => Confirmed ** Changed in: systemd (Ubuntu) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Tags removed: bionic systemd -- 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/1823171 Title: systemd-resolve hides DS records in explicit queries Status in systemd package in Ubuntu: Confirmed Bug description: When querying for DS resource records on a DNSSEC signed domain using dig, the DS records are not shown when the system is using systemd- resolve. Run: dig +short DS ripe.net Expected: something like 40991 8 2 D8D3C88263D58930A8B5FE16427130AB84CA73A4988385B2F4B121A7 2E5299A6 Actual result: no output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.15 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 4 14:14:06 2019 MachineType: MSI MS-7A70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=/dev/mapper/system-slash ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.80 dmi.board.asset.tag: Default string dmi.board.name: B250M PRO-VDH (MS-7A70) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd07/03/2018:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A70 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823171/+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 1664844] Re: No distinction between link-up and link-down interfaces
** Changed in: systemd (Ubuntu) Status: Fix Released => Confirmed ** Changed in: systemd (Ubuntu) Status: Confirmed => 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Bug description: [Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+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 1856330] Re: journalctl missing grep
** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Eoan) Status: New => Fix Released ** Changed in: systemd (Ubuntu Disco) Status: New => Won't Fix ** Changed in: systemd (Ubuntu Bionic) Status: New => Won't Fix -- 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/1856330 Title: journalctl missing grep Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: the man page for journalctl and the usage (journalctl --help) advertise an option (-g, --grep=) to grep the MESSAGE portion of events for a pcre pattern. journalctl is linked against libpcre, but doesn't recognize the option when used. $ journalctl -g dhcp journalctl: invalid option -- 'g' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573660262~18.04~d11b582~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 09:26:08 2019 MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=UUID=25721613-9f9a-4e8d-ac61-a6869852d0e2 ro ipv6.disable=1 usbhid.quirks=0x1B1C:0x1B13:0x400 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-10-05 (433 days ago) dmi.bios.date: 06/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0411 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: Desktop dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0411:bd06/28/2013:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrDesktop: dmi.product.family: ASUS MB dmi.product.name: Wild Dog Performance dmi.product.sku: All dmi.product.version: wilp10 dmi.sys.vendor: System76, Inc. mtime.conffile..etc.systemd.resolved.conf: 2018-10-08T15:18:41.655856 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1856330/+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 1316518] Re: [900X3G, Realtek ALC282, Mic, Internal] inverted mic not working
** Tags removed: vivid -- 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/1316518 Title: [900X3G, Realtek ALC282, Mic, Internal] inverted mic not working Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Internal Mic of Samsung Ativ book 9 (NP900X3G) is not supported properly. Stereo recording in audacity records sound from mic in L channel and only loud noise in R channel (phase inverted?) Muting R channel, and setting L channel to around 16%, in pavucontrol allows to record audio, but in poor quality. alsa-info.sh output: http://www.alsa- project.org/db/?f=064f0b536a1b068efd30d58c2641b5ec2348f059 Ubuntu Gnome 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sarah 2014 F pulseaudio sarah 8509 F alsamixer /dev/snd/controlC0: sarah 2014 F pulseaudio CurrentDesktop: GNOME Date: Tue May 6 11:55:36 2014 InstallationDate: Installed on 2014-04-29 (6 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Internes Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [900X3G, Realtek ALC282, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04ADU.023.140414.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP900X3G-K02DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04ADU.023.140414.PS:bd04/14/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP04ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3G-K02DE:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 900X3G dmi.product.version: P04ADU dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarah 2004 F pulseaudio /dev/snd/controlC1: sarah 2004 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=b4bd3914-d1c4-40f0-ba32-fb19aa9af13c InstallationDate: Installed on 2014-04-29 (27 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=92ac4966-692f-4e06-a1dd-da069008e861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 StagingDrivers: rts5139 Tags: trusty trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04ADU.023.140414.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP900X3G-K02DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04ADU.023.140414.PS:bd04/14/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP04ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3G-K02DE:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 900X3G dmi.product.version: P04ADU dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go
[Touch-packages] [Bug 1450947] Re: [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys have no effect
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1450947 Title: [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys have no effect Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Since upgrade to 15.04 from 14.10, the physical volume keys (mute, up, down) on my ThinkPad X60 have no effect. I can adjust the volume via the menubar indicator, but the buttons are dead. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: andrew 2071 F...m pulseaudio /dev/snd/controlC0: andrew 2071 F pulseaudio CurrentDesktop: XFCE Date: Fri May 1 19:05:06 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-12 (535 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel, playback] volume slider problem UpgradeStatus: Upgraded to vivid on 2015-05-01 (0 days ago) dmi.bios.date: 11/20/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7BETD7WW (2.18 ) dmi.board.name: 170686U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7BETD7WW(2.18):bd11/20/2008:svnLENOVO:pn170686U:pvrThinkPadX60:rvnLENOVO:rn170686U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 170686U dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450947/+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 1450027] Re: [HP ProBook 6550b, IDT 92HD75B3X5, Green Headphone Out, Front] Playback problem - audio works fine without headphones
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- 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/1450027 Title: [HP ProBook 6550b, IDT 92HD75B3X5, Green Headphone Out, Front] Playback problem - audio works fine without headphones Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Audio works fine through built-in speakers, doesn't work with headphones plugged in. This is related to the 15.04 release, as they previously worked fine. I've tested with other headphones just in case! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jim1770 F...m pulseaudio /dev/snd/controlC0: jim1770 F pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Apr 29 15:33:17 2015 InstallationDate: Installed on 2014-03-23 (401 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [HP ProBook 6550b, IDT 92HD75B3X5, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to vivid on 2015-04-28 (1 days ago) dmi.bios.date: 06/25/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CDE Ver. F.01 dmi.board.name: 146D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 73.11 dmi.chassis.asset.tag: CNU0334019 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CDEVer.F.01:bd06/25/2010:svnHewlett-Packard:pnHPProBook6550b:pvr:rvnHewlett-Packard:rn146D:rvrKBCVersion73.11:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6550b dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1450027/+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 1446457] Re: [HDA-Intel - HDA Intel PCH, recording] No autoswitch
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1446457 Title: [HDA-Intel - HDA Intel PCH, recording] No autoswitch Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Acer E3-112 Ubuntu 14.04, 14.10, 15.04 After plugging in headset only headset earphones detected, mic from headset not detected and recording is only from built in mic. Appending 'options snd-hda-intel model=dell-headset-multi' to /etc/modprobe.d/alsa-base.conf helps to tell xubuntu that headset mic may be plugged, but after plugging in, xubuntu doesn't automaticaly detect that mic is plugged, it can see only headset's earphones, so i need evreytime in pavucontrol tell xubuntu that mic is plugged in even after adding option. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mishurov 2000 F pulseaudio CurrentDesktop: XFCE Date: Tue Apr 21 07:03:19 2015 InstallationDate: Installed on 2015-04-04 (16 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Type: No auto-switch between inputs Title: [HDA-Intel - HDA Intel PCH, recording] No autoswitch UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd08/20/2014:svnAcer:pnNC-E3-112-C97Q:pvrV1.10:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: NC-E3-112-C97Q dmi.product.version: V1.10 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-04-21T06:35:28.960726 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1446457/+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 1450207] Re: [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] volume slider problem
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1450207 Title: [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] volume slider problem Status in alsa-driver package in Ubuntu: Won't Fix Bug description: When starting Ubuntu from boot-up, sometimes the F11 and F12 keys have no effect on the sound volume, even though it can be controlled by the slider in the Sound window. This can often be restored by re-booting the OS. When the F11 and F12 keys are working as expected, a "pop" is heard in the speakers indicating a change of volume level. The output volume slider in the Sound window has the same effect. However, when adjusting the volume using the slider in the pull-down menu at the top right of the desktop, the sound level is adjusted as seen by the slider moving in the Sound window. However, this produces no audible "pop" as occurs when the volume level is adjusted by other methods. Ubuntu 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1590 F pulseaudio /dev/snd/controlC1: david 1590 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 29 22:13:15 2015 InstallationDate: Installed on 2015-04-23 (6 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Volume slider, or mixer problems Title: [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] volume slider problem UpgradeStatus: Upgraded to vivid on 2015-04-23 (6 days ago) dmi.bios.date: 09/11/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0D13CR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/11/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450207/+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 1201528] Re: [INTEL DP55WG, Realtek ALC889] - Audio Playback Unavailable
** Tags removed: raring vivid ** Tags added: xenial -- 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/1201528 Title: [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in alsa-driver source package in Vivid: Confirmed Status in linux source package in Vivid: Won't Fix Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm 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:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita 13188 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b InstallationDate: Installed on 2014-05-11 (366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Tags: vivid vivid vivid vivid Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-11 (61 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1201528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1452258] Re: [MS-7520, Creative CA0110-IBG] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1452258 Title: [MS-7520, Creative CA0110-IBG] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: X-fi PCI-e card seems to be the issue. Hasn't worked since, I believe, kernel 3.8.x - sound failed on Ubuntu 14.10 and 15.04. Last working config was using 14.04 on, I believe, kernel 3.8.x - although Google tells me 14.04.2 used kernel 3.16 ... I vaguely recall rolling back to an earlier kernel as a workaround that persisted until I recently installed 15.04. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jack 11756 F pulseaudio /dev/snd/controlC1: jack 11756 F pulseaudio CurrentDesktop: Unity Date: Wed May 6 21:49:18 2015 InstallationDate: Installed on 2015-05-05 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: [SB X-Fi Xtreme Audio] CA0110-IBG (SB1040) - HDA Creative Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jack 11756 F pulseaudio /dev/snd/controlC1: jack 11756 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [MS-7520, Creative CA0110-IBG, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.13 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Eclipse SLI (MS-7520) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd05/18/2010:svnMSI:pnMS-7520:pvr1.0:rvnMSI:rnEclipseSLI(MS-7520):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7520 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1452258/+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 1856255] Re: Apport-bug wrongly complains about the program not being installed
Hi, You are correct: now that I checked, “apport-bug apport” and “apport-bug net-tools” works fine. I agree that this is not a bug. It can however be rephrased as an enhancement: I believe that most people think of programs, not packages (at least I do ☺). So if there is a bug with a program, I just call “apport-bug” followed by the program name (which most of the case actually corresponds to the package name, but as instanced here, not always). When typing a non-existent command in the shell, I usually get a message “try installing this package”: do you think that it would be easy to add a feature of Apport such that if the package is non-installed, but that there is a command with this name, it suggests a package name instead? I think that this would greatly help getting useful bug reports ☺ Maybe the code from gnome-terminal that looks for such package can be reused? Have a nice day, Martin. -- 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/1856255 Title: Apport-bug wrongly complains about the program not being installed Status in apport package in Ubuntu: Incomplete Bug description: I typed “apport-bug ifconfig” because ifconfig was wrongly behaving. Apport told me that ifconfig was not installed. But it was! So I restarted my computer, just in case, but the bug is still there. And for all programs that it tried. Including Apport itself. Currently, when I type “apport-bug apport-bug”, I get a window “Problem in apport-bug” with the following message: “The problem cannot be reported: This report is about a package that is not installed.” (See screenshot here-attached.) The error message is clearly wrong: apport-bug must be installed to be able to display this window. --- ProblemType: Bug ApportLog: ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: called for pid 7431, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable: /home/martin/.steam/ubuntu12_64/vulkandriverquery (command line "/home/martin/.steam/ubuntu12_32/../ubuntu12_64/vulkandriverquery") ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable does not belong to a package, ignoring ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (105 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: apport 2.20.9-0ubuntu7.9 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1856255/+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 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
missing SRU style description -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` Status in bash-completion package in Ubuntu: Triaged Status in gawk package in Ubuntu: Invalid Status in mawk package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in util-linux package in Ubuntu: New Status in bash-completion source package in Focal: Triaged Status in gawk source package in Focal: Invalid Status in mawk source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Invalid Status in util-linux source package in Focal: New Status in Debian: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+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 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- 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/1470730 Title: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work Status in alsa-driver package in Ubuntu: Incomplete Bug description: When I plug in external speakers to line in/line out combo on the laptop the internal speakers are turned off but when I plug the speakers into the docking station (HP UltraSlim Dock 2013 EURO, D9Y32AA) music keeps playing in the internal speakers. Similar behaviour (nothing happens) is experienced with microphone connected to line in on docking station. ### Expected behaviour Plugging in external speakers to docking station should turn off sound from laptop internal speakers. Plugging in microphone to line in on docking station should switch from "internal microphone" to "microphone" in Ubuntu sound settings. ### Current behaviour Sound keeps playing in internal speakers when plugging in external speakers to docking station. Plugging in microphone to line in on docking station, nothing happens. ### Hardware Laptop: HP EliteBook 840 G2 Product number: H9W19EA#AK8 Docking station: HP UltraSlim Dock 2013 EURO Product number: D9Y32AA ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chol 2001 F pulseaudio /dev/snd/controlC0: chol 2001 F pulseaudio /dev/snd/controlC1: chol 2001 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 2 08:16:15 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-05 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.04 dmi.board.name: 2216 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.54 dmi.chassis.asset.tag: 5CG5093YZ7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009D410303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G2 dmi.product.version: A3009D410303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1470730/+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 1856257] Re: SIOCSIFFLAGS: Input/output error
I think that I already executed the command “apport-collect 1856257” just after reporting the bug (I had issues understanding how to use Apport: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1856255 ). Do you want me to execute it again? (As you say to call it only once, I don’t want to mess with anything here.) I have to admit that the difference between “apport-bug” and “ubuntu- bug” always confused me. Is there a difference? I’ve run the following three commands, and am attaching the two files “output” and “output2”. ```bash $ dmesg > output $ sudo ifconfig wlp59s0 up $ dmesg > output2 ``` ** Attachment added: "dmesg > output" https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+attachment/5312189/+files/output -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1856257 Title: SIOCSIFFLAGS: Input/output error Status in net-tools package in Ubuntu: New Bug description: My wifi is no longer working since a recent update (yesterday, I think). When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` This error message is not really helpful: I would have expected ifconfig to provide a more user-friendly explanation about what is not working well. Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. wlp59s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` I’m calling apport-collect on this bug to add other relevant information. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libpcre3 2:8.39-9 libselinux1 2.7-2build2 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+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 1856257] Re: SIOCSIFFLAGS: Input/output error
** Attachment added: "Result of dmesg after calling ifconfig" https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+attachment/5312198/+files/output2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1856257 Title: SIOCSIFFLAGS: Input/output error Status in net-tools package in Ubuntu: New Bug description: My wifi is no longer working since a recent update (yesterday, I think). When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` This error message is not really helpful: I would have expected ifconfig to provide a more user-friendly explanation about what is not working well. Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. wlp59s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` I’m calling apport-collect on this bug to add other relevant information. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libpcre3 2:8.39-9 libselinux1 2.7-2build2 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+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 1856257] Re: SIOCSIFFLAGS: Input/output error
(Note: the output of the ifconfig command above was, as before, “SIOCSIFFLAGS: Input/output error”.) ** Changed in: net-tools (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1856257 Title: SIOCSIFFLAGS: Input/output error Status in net-tools package in Ubuntu: New Bug description: My wifi is no longer working since a recent update (yesterday, I think). When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` This error message is not really helpful: I would have expected ifconfig to provide a more user-friendly explanation about what is not working well. Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. wlp59s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` I’m calling apport-collect on this bug to add other relevant information. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libpcre3 2:8.39-9 libselinux1 2.7-2build2 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+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 1447767] Re: [XPS 13 9343, Intel Broadwell HDMI, Digital Out, HDMI] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- 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/1447767 Title: [XPS 13 9343, Intel Broadwell HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I installed Ubuntu 15.04 64 bit (desktop editition) on a DELL XPS 13 notebook (model 9343) and I have no sound at all. Before installing Ubuntu I upgraded bios to A03. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cribari1733 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 23 15:46:30 2015 InstallationDate: Installed on 2015-04-23 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cribari1733 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [XPS 13 9343, Intel Broadwell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1447767/+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 1448362] Re: [Standard, Realtek ALC269VB, Speaker, Internal] No sound at all after upgrade to ubuntu 15.04
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- 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/1448362 Title: [Standard, Realtek ALC269VB, Speaker, Internal] No sound at all after upgrade to ubuntu 15.04 Status in alsa-driver package in Ubuntu: Won't Fix Bug description: After upgrading to ubuntu 15.04 I can't hear sounds at all. The microphone seems to be ok. It doesn't matter if I'm watch a video through the internet or just playing a audio track from my computer. I've tried to hear using headphones and it works normally, but the speakers are mute. I've checked the drivers and they're ok. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: igor 2126 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 24 22:42:29 2015 InstallationDate: Installed on 2015-02-06 (77 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: igor 2126 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Standard, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago) dmi.bios.date: 05/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.07 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Standard dmi.board.vendor: Standard dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Standard dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.07:bd05/06/2013:svnStandard:pnStandard:pvrTobefilledbyO.E.M.:rvnStandard:rnStandard:rvrTobefilledbyO.E.M.:cvnStandard:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Standard dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Standard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1448362/+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 1856255] Re: Apport-bug wrongly complains about the program not being installed
** Changed in: apport (Ubuntu) Status: Incomplete => Invalid ** Summary changed: - Apport-bug wrongly complains about the program not being installed + Apport-bug could suggest a package instead of complaining about the program not being installed -- 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/1856255 Title: Apport-bug could suggest a package instead of complaining about the program not being installed Status in apport package in Ubuntu: Invalid Bug description: I typed “apport-bug ifconfig” because ifconfig was wrongly behaving. Apport told me that ifconfig was not installed. But it was! So I restarted my computer, just in case, but the bug is still there. And for all programs that it tried. Including Apport itself. Currently, when I type “apport-bug apport-bug”, I get a window “Problem in apport-bug” with the following message: “The problem cannot be reported: This report is about a package that is not installed.” (See screenshot here-attached.) The error message is clearly wrong: apport-bug must be installed to be able to display this window. --- ProblemType: Bug ApportLog: ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: called for pid 7431, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable: /home/martin/.steam/ubuntu12_64/vulkandriverquery (command line "/home/martin/.steam/ubuntu12_32/../ubuntu12_64/vulkandriverquery") ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable does not belong to a package, ignoring ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (105 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: apport 2.20.9-0ubuntu7.9 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1856255/+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 1855647] Re: When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc?
@Daniel, I think it's rather gio which has the logic for mounts and their icons? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1855647 Title: When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc? Status in glib2.0 package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Dock 3) When an ISO image is loaded, a disc with ISO tag would be displayed on the dock. 4) A disc drive was displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1855647/+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 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS
This randomly started happening on 18.04.3 on WSL, but @pujanm's fix did the trick! https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/comments/11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1785778 Title: Hash Sum mismatch Ubuntu Server 18.04.1 LTS Status in apt package in Ubuntu: Invalid Bug description: Hi, I'm getting weird Hashes mismatch error while trying to update Ubuntu server 18.04.1 LTS server. The error I'm receiving is as follows. $ sudo apt-get update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources [2,676 B] Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [277 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [105 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [157 kB] Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages Hash Sum mismatch Hashes of expected file: - Filesize:157408 [weak] - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak] - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak] Hashes of received file: - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak] - MD5Sum:a33f0341357c0be32207618a14b500db [weak] - Filesize:157408 [weak] Last modification reported: Tue, 07 Aug 2018 07:15:09 + Release file created at: Tue, 07 Aug 2018 07:15:03 + Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [71.0 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [3,772 B] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [2,376 B] Err:14 http://download.webmin.com/download/repository sarge InRelease Could not connect to download.webmin.com:80 (108.60.199.109), connection timed out Fetched 329 kB in 30s (10.9 kB/s) Reading package lists... Done W: Failed to fetch http://download.webmin.com/download/repository/dists/sarge/InRelease Could not connect to download.webmin.com:80 (108.60.199.109), connection timed out E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 Hash Sum mismatch Hashes of expected file: - Filesize:157408 [weak] - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak] - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak] Hashes of received file: - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak] - MD5Sum:a33f0341357c0be32207618a14b500db [weak] - Filesize:157408 [weak] Last modification reported: Tue, 07 Aug 2018 07:15:09 + Release file created at: Tue, 07 Aug 2018 07:15:03 + W: Some index files failed to download. They have been ignored, or old ones used instead. I have tried solution provided in search as "removing all files in /var/lib/apt/lists and update again" but it doesn't work. Don't know how to resolve it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/+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 1856330] Re: journalctl missing grep
Unfortunately, systemd in Bionic and Disco was built without the pcre2 library, and that's what journalctl uses to implement --grep. So before Eoan, journalctl --grep will fail with: "Compiled without pattern matching support" Since adding this support now would pull in an additional dependency to the systemd package, fixing this bug would mean breaking automatic updates for everyone using systemd (on Bionic or Disco) but without libpcre2 installed, since a package won't be automatically updated if it requires new dependencies that aren't currently installed. Also unfortunately, the journalctl -g option was left out of the options string, so it prints "invalid option" as you mentioned; that is trivial to fix, but won't actually make journalctl grep work, since it would just change from "invalid option" to "compile without pattern matching support". So while the -g error message for journalctl in Bionic is a bit confusing, I don't think it's worth a patch just to slightly improve the error message without actually getting --grep working. Please note that --grep (and -g) works starting in Eoan. Also, I'll mention that you can still simply pipe journalctl output into the 'grep' tool; it's a bit less efficient but should still work. Sorry. ** Changed in: systemd (Ubuntu) Status: New => 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/1856330 Title: journalctl missing grep Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: the man page for journalctl and the usage (journalctl --help) advertise an option (-g, --grep=) to grep the MESSAGE portion of events for a pcre pattern. journalctl is linked against libpcre, but doesn't recognize the option when used. $ journalctl -g dhcp journalctl: invalid option -- 'g' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573660262~18.04~d11b582~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 09:26:08 2019 MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=UUID=25721613-9f9a-4e8d-ac61-a6869852d0e2 ro ipv6.disable=1 usbhid.quirks=0x1B1C:0x1B13:0x400 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-10-05 (433 days ago) dmi.bios.date: 06/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0411 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: Desktop dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0411:bd06/28/2013:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrDesktop: dmi.product.family: ASUS MB dmi.product.name: Wild Dog Performance dmi.product.sku: All dmi.product.version: wilp10 dmi.sys.vendor: System76, Inc. mtime.conffile..etc.systemd.resolved.conf: 2018-10-08T15:18:41.655856 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1856330/+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 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
** Tags removed: ddstreet -- 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/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.montemar.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. [Other Info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to Eoan now, as I don't want to disturb the merge. If needed after the merge, I'll add to Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1831787] Re: Bogus routes after DHCP lease change
** Changed in: systemd (Ubuntu Disco) Importance: Medium => High ** Changed in: systemd (Ubuntu Bionic) Importance: Medium => High -- 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/1831787 Title: Bogus routes after DHCP lease change Status in netplan: Invalid Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: Fix Released Bug description: [impact] networkd does not remove old route(s) after DHCP address change [test case] on a system using networkd, that is connected to a network where you can control the addresses that the DHCP server provides, setup system with networkd to get address via DHCP, e.g. [Match] Name=ens3 [Network] DHCP=ipv4 (re)start networkd or reboot, so the system gets an ipv4 DHCP address, and corresponding route to the gateway. Then on the dhcp server, change the subnet to a different subnet. On the client, once its renews its DHCP address, the server will provide a new address in the new subnet, and the client will add a new default route to the new gateway address. However, the old default route to the old gateway address isn't removed. Note this also happens without changing the entire subnet, but is more subtle as shown in the original description. [regression potential] this affects how networkd handles routes, so has the potential to leave a system with partial or incorrect networking, or no networking at all. Any regression would most likely occur during networkd (re)start or during renewal of a DHCP lease, or when an interface is brought up. [other info] original description: --- Netplan config: network: version: 2 renderer: networkd ethernets: eno4: dhcp4: no eno1np0: dhcp4: no addresses: - 172.16.0.2/24 bridges: br0: dhcp4: yes interfaces: - eno4 On initial boot, machine got 10.0.15.109 IP address: May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 10.0.15.109/23 via 10.0.15.253 At one point, DHCP server reserver this IP address and client eventually picked up new IP address: May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address 10.0.15.128/23 via 10.0.15.253 This resulted in IP addresses: # ip -o a 1: loinet 127.0.0.1/8 scope host lo\ valid_lft forever preferred_lft forever 1: loinet6 ::1/128 scope host \ valid_lft forever preferred_lft forever 2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\ valid_lft forever preferred_lft forever 2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \ valid_lft forever preferred_lft forever 6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\ valid_lft 503sec preferred_lft 503sec 6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \ valid_lft forever preferred_lft forever So far, everything is fine. But, the routes on the machine are bogus: # ip r default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100 default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100 10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100 172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2 routes with src 10.0.15.109 should have been removed when lease was renewed. I'm not sure if this is a bug in netplan or systemd. This is 18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1831787/+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 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
** Description changed: + [Impact] + + * Running gzip on WSL1 results in the following error: +$ gzip +-bash: /bin/gzip: cannot execute binary file: Exec format error + * The error occurs frequently in package updates and makes gzip inoperable on WSL1 + * The problem is caused by PT_LOAD offset pointing past the end of file and the fix is fixing strip to not generate such ELF files and recompiling gzip with the fixed strip. + + [Test Case] + + * Check the gzip binary for wrong offset: + $ FILE=/usr/bin/gzip; readelf -W --program-headers $FILE | awk -v size=$(stat -c %s $FILE) '/^ LOAD/ {if (strtonum($2) > size) {print "wrong offset ("$2" ("strtonum($2)") points past EOF:" size; exit 1;}}' + + [ Regression Potential ] + + * The binutils fix could cause binutils to generate invalid ELF files. The fix is very small and isolated and has been tested and accepted by upstream, which makes such problems unlikely. + * Bugs in the toolchain in general can make the rebuilt gzip show new errors, but this generally applies to many SRUs and security updates. The testing period in proposed should mitigate this risk. + + [Originial Bug Text] + Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: - Installed: 1.10-0ubuntu3 - Candidate: 1.10-0ubuntu3 - Version table: - *** 1.10-0ubuntu3 500 - 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.10-0ubuntu3 + Candidate: 1.10-0ubuntu3 + Version table: + *** 1.10-0ubuntu3 500 + 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: Confirmed Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: [Impact] * Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error * The error occurs frequently in package updates and makes gzip inoperable on WSL1 * The problem is caused by PT_LOAD offset pointing past the end of file and the fix is fixing strip to not generate such ELF files and recompiling gzip with the fixed strip. [Test Case] * Check the gzip binary for wrong offset: $ FILE=/usr/bin/gzip; readelf -W --program-headers $FILE | awk -v size=$(stat -c %s $FILE) '/^ LOAD/ {if (strtonum($2) > size) {print "wrong offset ("$2" ("strtonum($2)") points past EOF:" size; exit 1;}}' [ Regression Potential ] * The binutils fix could cause binutils to generate invalid ELF files. The fix is very small and isolated and has been tested and accepted by upstream, which makes such problems unlikely. * Bugs in the toolchain in general can make the rebuilt gzip show new errors, but this generally applies to many SRUs and security updates. The testing period in proposed should mitigate this risk. [Originial Bug Text] Summary: Running gzip on WSL1 results
[Touch-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
I solved this issue by the next actions: - run the touchpad-edge-detector tool from the libevdev-utils package in my case command is sudo touchpad-edge-detector 96x46 /dev/input/event6 - then I pasted output of previous command to file /lib/udev/hwdb.d/60-evdev.hwdb - and apply this changes by commands sudo systemd-hwdb update sudo udevadm trigger /dev/input/event* like commented in head of redacted file And problem solved. In my case code is: EVDEV_ABS_00=1261:5717:46 EVDEV_ABS_01=1001:4907:85 EVDEV_ABS_35=1261:5717:46 EVDEV_ABS_36=1001:4907:85 On my notebook touchpad is rectangular and not a square. -- 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/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in systemd: Fix Released Status in libinput package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Status in libinput package in Fedora: Confirmed Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1825499/+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 1856366] [NEW] PCI/internal sound card not detected
Public bug reported: No sound card detected with kernel 5.5.0-050500rc1-generic 1. Description: Ubuntu 19.10 Release:19.10 2. linux-image- unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb 3. have at least one soundcard 4. cat /proc/asound/cards reports: --- no soundcards --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.5.0-050500rc1-generic x86_64 NonfreeKernelModules: hda_intel ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 22:09:17 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1856366 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No sound card detected with kernel 5.5.0-050500rc1-generic 1. Description: Ubuntu 19.10 Release: 19.10 2. linux-image- unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb 3. have at least one soundcard 4. cat /proc/asound/cards reports: --- no soundcards --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.5.0-050500rc1-generic x86_64 NonfreeKernelModules: hda_intel ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 22:09:17 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+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 1671951] Re: networkd should allow configuring IPV6 MTU
** Merge proposal linked: https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/376801 -- 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd: Unknown Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: Fix Released Status in systemd source package in Bionic: In Progress Status in cloud-init source package in Disco: New Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: In Progress Status in cloud-init source package in Eoan: New Status in netplan.io source package in Eoan: Fix Released Status in systemd source package in Eoan: In Progress Status in cloud-init source package in Focal: Confirmed Status in netplan.io source package in Focal: Fix Released Status in systemd source package in Focal: In Progress Bug description: = netplan.io = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Apply a netplan configuration that specifices ipv6-mtu: network: version: 2 ethernets: eth0: dhcp4: true dhcp6: true ipv6-mtu: 6000 * Check that MTU bytes, is at least IPv6MTUBytes on the interface: $ sysctl net.ipv6.conf.eth0.mtu net.ipv6.conf.eth0.mtu = 6000 [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of netplan.io = = systemd = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Use IPv6MTUBytes= setting in a .network unit * Restart systemd-network * Check that there no error messages / warnings about not-recognizing this option * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1671951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication
** Changed in: network-manager (Ubuntu Bionic) Assignee: Till Kamppeter (till-kamppeter) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/942856 Title: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: In Progress Bug description: * Impact Selecting AES-{192,256}-CBC keys to connect isn't working * Test case 1. Start with a working (cleartext or DES-3) private key/cert for a network. Set up a connection and verify that everything works. 2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in working-key.pem -out aes-key.pem -aes256" (the output should have a line starting with "DEK-Info: AES-256-CBC,") 3. Delete the settings for the test network and attempt to reconnect using the new key. That should work * Regression potential That's new code for an extra type of keys, it shouldn't impact existing options -- NetworkManager does not appear to support private keys encrypted with AES. At the very least, it will not validate such a key in nm-util when setting up a WPA 802.1x TLS wifi connection. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/942856/+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 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
NB for an easier reproducer on eoan without requiring a reinstall, you can use 'sudo update-alternatives --config awk' to change the target of /usr/bin/awk to mawk. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` Status in bash-completion package in Ubuntu: Incomplete Status in gawk package in Ubuntu: Invalid Status in mawk package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in util-linux package in Ubuntu: New Status in bash-completion source package in Focal: Incomplete Status in gawk source package in Focal: Invalid Status in mawk source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Invalid Status in util-linux source package in Focal: New Status in Debian: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+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 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
marking incomplete based on Timo's request for a proper SRU bug template ** Changed in: bash-completion (Ubuntu Focal) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` Status in bash-completion package in Ubuntu: Incomplete Status in gawk package in Ubuntu: Invalid Status in mawk package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in util-linux package in Ubuntu: New Status in bash-completion source package in Focal: Incomplete Status in gawk source package in Focal: Invalid Status in mawk source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Invalid Status in util-linux source package in Focal: New Status in Debian: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+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 1809132] Re: Updated bionic to the current 1.10 stable version
** Changed in: network-manager (Ubuntu) Assignee: Till Kamppeter (till-kamppeter) => (unassigned) ** Changed in: network-manager (Ubuntu Bionic) Assignee: Till Kamppeter (till-kamppeter) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1809132 Title: Updated bionic to the current 1.10 stable version Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: In Progress Bug description: * Impact The updates in the stable serie include several fixes for misbehaviour, segfaults and security issues, those are the sort of improvements that should be in the LTS The detail of the changes can be seen in the NEWS entry https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS * Test case There is no specific test case for the update, the changelog includes some specific bugs which have their own test case, otherwise it's important to get testing/feedback from users on desktop & server, using IPv4, IPv6, VPN, wifi, eth connections, etc. * Regression potential The update is non trivial, there are several changes are IPv6 and DNS (especially in the context of VPNs) handling so it would be good to give those extra testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809132/+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 1856370] [NEW] GPU has fallen off the bus
Public bug reported: Every time I suspend my laptop, after I resume it, a black screen shows with the error message - GPU has fallen off the bus It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590 with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5 Description:Ubuntu 19.10 Release:19.10 nvidia driver 435 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 16:31:58 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905] Subsystem: Dell Device [1028:0905] InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages 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/1856370 Title: GPU has fallen off the bus Status in xorg package in Ubuntu: New Bug description: Every time I suspend my laptop, after I resume it, a black screen shows with the error message - GPU has fallen off the bus It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590 with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5 Description: Ubuntu 19.10 Release: 19.10 nvidia driver 435 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 16:31:58 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed
[Touch-packages] [Bug 1856370] Re: GPU has fallen off the bus
I've just tested switching between the nvidia-driver-435 and nvidia- driver-430 packages and I get the same error with both. I do not get any problems with xserver-xorg-vide-nouveau. -- 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/1856370 Title: GPU has fallen off the bus Status in xorg package in Ubuntu: New Bug description: Every time I suspend my laptop, after I resume it, a black screen shows with the error message - GPU has fallen off the bus It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590 with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5 Description: Ubuntu 19.10 Release: 19.10 nvidia driver 435 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 16:31:58 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905] Subsystem: Dell Device [1028:0905] InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856370/+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 1856257] Re: SIOCSIFFLAGS: Input/output error
To answer your question on apport-bug, ubuntu-bug ; on my 20.04 box guiverc@d960-ubu2:/sbin$ whereis ubuntu-bug apport-bug ubuntu-bug: /usr/bin/ubuntu-bug /usr/share/man/man1/ubuntu-bug.1.gz apport-bug: /usr/bin/apport-bug /usr/share/man/man1/apport-bug.1.gz guiverc@d960-ubu2:/sbin$ file /usr/bin/ubuntu-bug /usr/bin/apport-bug /usr/bin/ubuntu-bug: symbolic link to apport-bug /usr/bin/apport-bug: POSIX shell script, ASCII text executable (ie. ubuntu-bug just calls and runs apport-bug). The information that is collected can vary depending on the package the bug report is filed against) Thank you for uploading dmesg :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1856257 Title: SIOCSIFFLAGS: Input/output error Status in net-tools package in Ubuntu: New Bug description: My wifi is no longer working since a recent update (yesterday, I think). When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` This error message is not really helpful: I would have expected ifconfig to provide a more user-friendly explanation about what is not working well. Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. wlp59s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` I’m calling apport-collect on this bug to add other relevant information. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libpcre3 2:8.39-9 libselinux1 2.7-2build2 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+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 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
Hello Hayden, or anyone else affected, Accepted binutils into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/binutils/2.33-2ubuntu1.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 and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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: binutils (Ubuntu Eoan) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: Confirmed Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Status in binutils source package in Eoan: Fix Committed Bug description: [Impact] * Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error * The error occurs frequently in package updates and makes gzip inoperable on WSL1 * The problem is caused by PT_LOAD offset pointing past the end of file and the fix is fixing strip to not generate such ELF files and recompiling gzip with the fixed strip. [Test Case] * Check the gzip binary for wrong offset: $ FILE=/usr/bin/gzip; readelf -W --program-headers $FILE | awk -v size=$(stat -c %s $FILE) '/^ LOAD/ {if (strtonum($2) > size) {print "wrong offset ("$2" ("strtonum($2)") points past EOF:" size; exit 1;}}' [ Regression Potential ] * The binutils fix could cause binutils to generate invalid ELF files. The fix is very small and isolated and has been tested and accepted by upstream, which makes such problems unlikely. * Bugs in the toolchain in general can make the rebuilt gzip show new errors, but this generally applies to many SRUs and security updates. The testing period in proposed should mitigate this risk. [Originial Bug Text] Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to:
[Touch-packages] [Bug 1856366] Re: PCI/internal sound card not detected
[ 24.279630] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-icl.ri failed with error -2 [ 24.279632] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-icl.ri failed err: -2 [ 24.279634] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [ 24.279635] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 Please put this firmware to /lib/firmware/intel/sof/; then reboot, and upload the dmesg. If you want your machine use legacy audio driver instead of sof driver, you could add: options snd-hda-intel dsp_driver=0 in the /etc/modprobe.d/alsa- base.conf, then reboot. ** Attachment added: "sof-icl.ri" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+attachment/5312296/+files/sof-icl.ri -- 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/1856366 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No sound card detected with kernel 5.5.0-050500rc1-generic 1. Description: Ubuntu 19.10 Release: 19.10 2. linux-image- unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb 3. have at least one soundcard 4. cat /proc/asound/cards reports: --- no soundcards --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.5.0-050500rc1-generic x86_64 NonfreeKernelModules: hda_intel ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 22:09:17 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+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 1856376] Re: "Dummy Output" -- built-in audio not detected
[ 485.617034] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0 [ 485.618569] snd_hda_intel :00:1f.3: no codecs found! Maybe you don't install the codec driver's module (ls /lib/modules/'uname -r'/kernel/sound/pci/hda -la) or your machine has hardware problem on codec? -- 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/1856376 Title: "Dummy Output" -- built-in audio not detected Status in alsa-driver package in Ubuntu: New Bug description: I no longer seem to be getting audio on my laptop, and only "Dummy Output" shows up in the sound settings dialog. This sounds similar to LP #1781294 (including the same PCI device), though that seems to have been marked expired. alex@tapada:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Lenovo Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 64, IRQ 159 Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K] Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl alex@tapada:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 23:38:35 2019 InstallationDate: Installed on 2019-08-31 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+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 1856366] Re: PCI/internal sound card not detected
Hi Hui, thanks I was already experimenting with sof-icl.ri from the sof project. I also compiled and tested my own version. When I put the file you provided and then modprobe for snd_sof_pci then I get the following dmesg: [ 1220.050239] HDMI HDA Codec ehdaudio0D2: Max dais supported: 3 [ 1221.652307] sof-audio-pci :00:1f.3: error: cl_copy_fw: timeout HDA_DSP_SRAM_REG_ROM_STATUS read [ 1221.652890] sof-audio-pci :00:1f.3: error: load fw failed ret: -110 [ 1221.652955] sof-audio-pci :00:1f.3: error: status = 0x002c panic = 0x [ 1221.652978] sof-audio-pci :00:1f.3: error: failed to reset DSP [ 1221.652981] sof-audio-pci :00:1f.3: error: failed to boot DSP firmware -110 [ 1221.652984] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -110 I see in lsmod it got loaded, but no sound cards. I also compiled my own version of sof-pci-dev.ko using linux-5.5-rc1. What is strange I had to compile it with EXTRAVERSION="-050500rc1-generic SMP mod_unload" for insmod to accept it. The compiled driver also did not help to find any sound card. I will try now with "options snd-hda-intel dsp_driver=0" -- 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/1856366 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No sound card detected with kernel 5.5.0-050500rc1-generic 1. Description: Ubuntu 19.10 Release: 19.10 2. linux-image- unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb 3. have at least one soundcard 4. cat /proc/asound/cards reports: --- no soundcards --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.5.0-050500rc1-generic x86_64 NonfreeKernelModules: hda_intel ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 22:09:17 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+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 1856366] Re: PCI/internal sound card not detected
OMG, with dsp_driver=0 it works. Thanks so much :) -- 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/1856366 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No sound card detected with kernel 5.5.0-050500rc1-generic 1. Description: Ubuntu 19.10 Release: 19.10 2. linux-image- unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb 3. have at least one soundcard 4. cat /proc/asound/cards reports: --- no soundcards --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.5.0-050500rc1-generic x86_64 NonfreeKernelModules: hda_intel ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 22:09:17 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+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 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
This bug was fixed in the package binutils - 2.33.1-6ubuntu1 --- binutils (2.33.1-6ubuntu1) focal; urgency=medium * Merge with Debian; remaining changes: - Build from upstream sources. - Don't generate control file entries for any native mips* packages. * Cherry-pick from binutils master branch: PR25237, set no file contents PT_LOAD p_offset to first page (LP: #1843479) binutils (2.33.1-6) unstable; urgency=medium * Update from the binutils 2.33 branch: - [gas] Implement .cfi_negate_ra_state directive (AArch64). -- Balint Reczey Fri, 13 Dec 2019 16:24:27 +0100 ** Changed in: binutils (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: Confirmed Status in binutils package in Ubuntu: Fix Released Status in gzip package in Ubuntu: In Progress Status in binutils source package in Eoan: Fix Committed Bug description: [Impact] * Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error * The error occurs frequently in package updates and makes gzip inoperable on WSL1 * The problem is caused by PT_LOAD offset pointing past the end of file and the fix is fixing strip to not generate such ELF files and recompiling gzip with the fixed strip. [Test Case] * Check the gzip binary for wrong offset: $ FILE=/usr/bin/gzip; readelf -W --program-headers $FILE | awk -v size=$(stat -c %s $FILE) '/^ LOAD/ {if (strtonum($2) > size) {print "wrong offset ("$2" ("strtonum($2)") points past EOF:" size; exit 1;}}' [ Regression Potential ] * The binutils fix could cause binutils to generate invalid ELF files. The fix is very small and isolated and has been tested and accepted by upstream, which makes such problems unlikely. * Bugs in the toolchain in general can make the rebuilt gzip show new errors, but this generally applies to many SRUs and security updates. The testing period in proposed should mitigate this risk. [Originial Bug Text] Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+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 1844100] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
[Expired for evolution-data-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evolution-data-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1844100 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() Status in evolution-data-server package in Ubuntu: Expired Bug description: it crashed ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evolution-data-server 3.33.91-3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 16 09:53:33 2019 ExecutablePath: /usr/libexec/evolution-calendar-factory InstallationDate: Installed on 2013-09-03 (2203 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: /usr/libexec/evolution-calendar-factory ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f7b13f583ae <__GI___libc_malloc+286>: mov (%r8),%rsi PC (0x7f7b13f583ae) ok source "(%r8)" (0x7f7a0002) not located in a known VMA region (needed readable region)! destination "%rsi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: tcache_get (tc_idx=) at malloc.c:2937 __GI___libc_malloc (bytes=40) at malloc.c:3051 pvl_newlist () at /usr/lib/x86_64-linux-gnu/libical.so.3 () at /usr/lib/x86_64-linux-gnu/libical.so.3 i_cal_component_new () at /usr/lib/x86_64-linux-gnu/libical-glib.so.3 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to eoan on 2018-01-26 (597 days ago) UserGroups: adm autopilot cdrom dip docker libvirt lpadmin lxd plugdev sambashare stapdev stapsys stapusr sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1844100/+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 1856376] [NEW] "Dummy Output" -- built-in audio not detected
Public bug reported: I no longer seem to be getting audio on my laptop, and only "Dummy Output" shows up in the sound settings dialog. This sounds similar to LP #1781294 (including the same PCI device), though that seems to have been marked expired. alex@tapada:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Lenovo Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 64, IRQ 159 Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K] Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl alex@tapada:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 23:38:35 2019 InstallationDate: Installed on 2019-08-31 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1856376 Title: "Dummy Output" -- built-in audio not detected Status in alsa-driver package in Ubuntu: New Bug description: I no longer seem to be getting audio on my laptop, and only "Dummy Output" shows up in the sound settings dialog. This sounds similar to LP #1781294 (including the same PCI device), though that seems to have been marked expired. alex@tapada:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Lenovo Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 64, IRQ 159 Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K] Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl alex@tapada:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 23:38:35 2019 InstallationDate: Installed on 2019-08-31 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset
[Touch-packages] [Bug 1856376] Re: "Dummy Output" -- built-in audio not detected
I do seem to have some things in that directory: alex@tapada:~$ ls -la /lib/modules/`uname -r`/kernel/sound/pci/hda/ total 1036 drwxr-xr-x 2 root root 4096 Dec 4 06:10 . drwxr-xr-x 26 root root 4096 Dec 4 06:10 .. -rw-r--r-- 1 root root 24081 Nov 14 06:10 snd-hda-codec-analog.ko -rw-r--r-- 1 root root 7297 Nov 14 06:10 snd-hda-codec-ca0110.ko -rw-r--r-- 1 root root 162449 Nov 14 06:10 snd-hda-codec-ca0132.ko -rw-r--r-- 1 root root 22593 Nov 14 06:10 snd-hda-codec-cirrus.ko -rw-r--r-- 1 root root 8561 Nov 14 06:10 snd-hda-codec-cmedia.ko -rw-r--r-- 1 root root 31113 Nov 14 06:10 snd-hda-codec-conexant.ko -rw-r--r-- 1 root root 105369 Nov 14 06:10 snd-hda-codec-generic.ko -rw-r--r-- 1 root root 89473 Nov 14 06:10 snd-hda-codec-hdmi.ko -rw-r--r-- 1 root root 89057 Nov 14 06:10 snd-hda-codec-idt.ko -rw-r--r-- 1 root root 202025 Nov 14 06:10 snd-hda-codec.ko -rw-r--r-- 1 root root 165681 Nov 14 06:10 snd-hda-codec-realtek.ko -rw-r--r-- 1 root root 13001 Nov 14 06:10 snd-hda-codec-si3054.ko -rw-r--r-- 1 root root 30721 Nov 14 06:10 snd-hda-codec-via.ko -rw-r--r-- 1 root root 76505 Nov 14 06:10 snd-hda-intel.ko Anything in particular I should be looking for? -- 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/1856376 Title: "Dummy Output" -- built-in audio not detected Status in alsa-driver package in Ubuntu: New Bug description: I no longer seem to be getting audio on my laptop, and only "Dummy Output" shows up in the sound settings dialog. This sounds similar to LP #1781294 (including the same PCI device), though that seems to have been marked expired. alex@tapada:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Lenovo Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 64, IRQ 159 Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K] Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl alex@tapada:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 23:38:35 2019 InstallationDate: Installed on 2019-08-31 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+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