[Touch-packages] [Bug 1851337] Re: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1
** Changed in: openssh (Ubuntu) Status: Incomplete => Fix Released ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Ravi pathak (ravipathak1420184) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1851337 Title: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Fix Released Bug description: I don't know. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: openssh-server 1:8.0p1-6build1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 Date: Tue Nov 5 08:22:46 2019 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-15 (293 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: sshd: no hostkeys available -- exiting. SourcePackage: openssh Title: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago) The dpkg log shows: ... Setting up default-jre-headless (2:1.11-72) ... Setting up libpangoxft-1.0-0:amd64 (1.42.4-7) ... Setting up libqt4-network:amd64 (4:4.8.7+dfsg-7ubuntu3) ... Setting up openssh-server (1:8.0p1-6build1) ... Installing new version of config file /etc/ssh/moduli ... rescue-ssh.target is a disabled or a static unit, not starting it. Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (]8;;file://csozo-PC/lib/systemd/system/ssh.service/lib/systemd/system/ssh.service]8;;; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2019-11-05 08:22:46 CET; 6ms ago Docs: ]8;;man:sshd(8)man:sshd(8)]8;; ]8;;man:sshd_config(5)man:sshd_config(5)]8;; Process: 7160 ExecStartPre=/usr/sbin/sshd -t [0;1;31m(code=exited, status=1/FAILURE)[0m dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Apt ordering shows: ... python-lockfile:amd64: Install rygel:amd64: Install xbrlapi:amd64: Install NULL: ConfigurePending Dmesg indicates that an OOM killer event had occurred previously: [26198.228512] gsd-housekeepin invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 [26198.228515] CPU: 0 PID: 4355 Comm: gsd-housekeepin Tainted: G OE 5.0.0-32-generic #34-Ubuntu [26198.228515] Hardware name: System manufacturer System Product Name/H61M-K, BIOS 0801 07/21/2014 [26198.228516] Call Trace: [26198.228522] dump_stack+0x63/0x8a [26198.228525] dump_header+0x54/0x2fb [26198.228527] ? sched_clock+0x9/0x10 [26198.228529] oom_kill_process.cold.30+0xb/0x1d6 [26198.228530] out_of_memory+0x1c3/0x490 [26198.228532] __alloc_pages_slowpath+0xb68/0xea0 [26198.228534] __alloc_pages_nodemask+0x2c4/0x2e0 [26198.228536] alloc_pages_current+0x81/0xe0 [26198.228538] __page_cache_alloc+0x6a/0xa0 [26198.228540] filemap_fault+0x3f0/0x8b0 [26198.228541] ? filemap_map_pages+0x1ae/0x380 [26198.228544] ext4_filemap_fault+0x31/0x44 [26198.228546] __do_fault+0x3c/0x130 [26198.228548] __handle_mm_fault+0xe4b/0x1280 [26198.228550] ? __switch_to_asm+0x41/0x70 [26198.228552] handle_mm_fault+0xdd/0x210 [26198.228554] __do_page_fault+0x23a/0x4c0 [26198.228555] do_page_fault+0x2e/0xe0 [26198.228557] ? page_fault+0x8/0x30 [26198.228558] page_fault+0x1e/0x30 [26198.228560] RIP: 0033:0x7fa2d0fdd868 [26198.228563] Code: Bad RIP value. [26198.228564] RSP: 002b:7ffec9ae2620 EFLAGS: 00010203 [26198.228565] RAX: 7fa2d0fdd868 RBX: 7ffec9ae2e80 RCX: 000c [26198.228566] RDX: 7fa2d1120350 RSI: 002f RDI: 7ffec9ae2e80 [26198.228566] RBP: 7ffec9ae2e50 R08: 7fa2d0f271ca R09: 0001 [26198.228567] R10: 7fa2d1110ae0 R11: 7fa2d094763c R12: 002f [26198.228567] R13: 000d
[Touch-packages] [Bug 1855793] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1855793 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 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 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 20:35:53 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575941718 Mon 09 Dec 2019 08:35:18 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575939877 Mon 09 Dec 2019 08:04:37 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855793/+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 1855793] Re: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 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 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 20:35:53 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575941718 Mon 09 Dec 2019 08:35:18 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575939877 Mon 09 Dec 2019 08:04:37 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855793/+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 1855710] Re: Losing my printer
** No longer affects: xorg (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1855710 Title: Losing my printer Status in linux package in Ubuntu: Incomplete Bug description: Hello, After the last update of the system lost access to the printer and could not connect to it. Thanks Ferran Lindström ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 9 13:14:04 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1495] InstallationDate: Installed on 2016-10-25 (1139 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcEnviron: LANGUAGE=ca PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-170-generic root=UUID=55d2d15a-85c8-4ae0-bd45-dc47177bc25b ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.09 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.09:bd07/01/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Dec 8 17:56:16 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855710/+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 1855757] Re: Background image corrupted after standby 19.10
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Summary changed: - Background image corrupted after standby 19.10 + [nvidia] Background image corrupted after standby 19.10 ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia -- 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/1855757 Title: [nvidia] Background image corrupted after standby 19.10 Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. 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 .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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 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' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX 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-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer 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 N/A 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/gnome-shell/+bug/1855757/+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?
Is that meant to be gtk+3.0 ? -- 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 1855693] Re: microphone of the headset is not detected
Apple and Android have different definitions of 4-pin TRRS connectors, so they are not compatible with each other. You need to choose one that is compatible with Apple if you want it to work with a Macbook. See: https://www.cablechick.com.au/blog/understanding-trrs-and-audio-jacks/ ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1855693 Title: microphone of the headset is not detected Status in pulseaudio package in Ubuntu: Invalid Bug description: I have a set of headphones that work as speakers and microphone without problem on an android phone or on macos. Under ubuntu they are only detected as outputs, but not as microphone. in the audio settings I can select the output to be one of: internal speakers, hdmi monitor, or these headphones. The only input is the internal microphone of the laptop. When I make a call with microsoft teams, the other end confirms that they hear the sound from the room. The headphones are similar to these: https://www.ebay.com/itm /Earphones-Handsfree-Headphones-for-Samsung- Galaxy-S8-A5-A7-A8-A9-J1-J3-J5-J7-UK/163465454907 with a connector with four segments. I also tried another set of headphones, different brand, same behaviour: work fine in other devices, work as output-only in ubuntu ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1577 F pulseaudio /dev/snd/controlC1: peter 1577 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 11:00:07 2019 InstallationDate: Installed on 2019-11-14 (24 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 187.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr187.0.0.0.0:bd07/22/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1855693/+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 1853439] Re: xubuntu 18.04.3 rt5651 sound problem
*** This bug is a duplicate of bug 1816429 *** https://bugs.launchpad.net/bugs/1816429 Thanks. It looks like pulseaudio is being limited by a recurring kernel error: Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk pulseaudio[2075]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk pulseaudio[2075]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-bytcr_rt5651" card_name="alsa_card.platform-bytcr_rt5651" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. ** Summary changed: - xubuntu 18.04.3 rt5651 sound problem + Cherry Trail xubuntu 18.04.3 rt5651 sound problem ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853439 Title: Cherry Trail xubuntu 18.04.3 rt5651 sound problem Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: no sound ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Thu Nov 21 13:27:58 2019 InstallationDate: Installed on 2019-11-20 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=tr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853439/+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 1853439] Re: Cherry Trail xubuntu 18.04.3 rt5651 sound problem
*** This bug is a duplicate of bug 1816429 *** https://bugs.launchpad.net/bugs/1816429 I think we closed bug 1816429 too soon so let's use that... ** This bug has been marked a duplicate of bug 1816429 [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853439 Title: Cherry Trail xubuntu 18.04.3 rt5651 sound problem Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: no sound ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Thu Nov 21 13:27:58 2019 InstallationDate: Installed on 2019-11-20 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=tr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853439/+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 1855793] [NEW] Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on
Public bug reported: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description:Ubuntu 18.04.3 LTS Release:18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 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 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 20:35:53 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575941718 Mon 09 Dec 2019 08:35:18 PM EST yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575939877 Mon 09 Dec 2019 08:04:37 PM EST yes 4294966297no /org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in network-manager package in Ubuntu: New Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 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
[Touch-packages] [Bug 138094] Re: [Gutsy] desktop and keyboard freezes while mouse is moveable
I am seeing this and I am on Ubuntu 19.10. I have an Nvidia 1660Ti with the driver 435.21. When I use Nvidia drivers, I do not see this issue. If I select the new "on-demand" option under Prime-Select or even the Intel(Power-saving) option, randomly but quite consistently I see that the display freezes. Mouse works, ssh works, nothing in the logs points to a cause though. The laptop is Legion-Y545 with Intel 9750h processor. Works fine on Windows where nvidia graphics card is used on demand and Intel discrete chip is used most of the time. Major concern is the battery, while on intel chipset, I get really good battery but when I switch to Nvidia, it uses a lot of battery, I would want to be able to enable "on-demand" feature to save battery when needed. Latest Intel xorg driver is installed: 2:2.99.917+git20190815-1 -- 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/138094 Title: [Gutsy] desktop and keyboard freezes while mouse is moveable Status in xorg package in Ubuntu: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Bug description: Binary package hint: linux-source-2.6.22 I am not sure if it is kernel problem but it seems so. I had this two times in Gutsy. After some time the desktop and keyboard freezes while the mouse is still move able but nothing reacts to clicks. Another interesting point is that the first time an audio file runs along without problems in totem until it finished and the second time a video in vlc window. I could watch it normally except that I had no influence. The only keys that are still working are acpi ones like brightness (which calls sonybright acpi scripts) and the hibernate button. The laptop really went down to sleep without problems and resumes fine but it was still not possible to do anything. The video runs along too after resume except the audio but this is a general gutsy problem (under normal circumstances I had to restart the video program to get sound again). I have a Sony TX2 Laptop with Gutsy and the latest updates. I am using compiz and the i810 driver because of the intel xv problem. I have heard in #ubuntu+1 that I am not the only one with this problem so it doesn't seem to be only hardware specific. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/138094/+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 1855521] Re: [Dell Inspiron 5490] Internal microphone not detected
This machine probably has the internal dmic connected to the PCH, we need to use sof driver on this machine. Please wait for some time (maybe 1 month), we are adding sof support in the 19.10 kernel, not finished yet. -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1817721] Re: autopkgtest success rate in Bionic reached an unusable amount
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1817721 Title: autopkgtest success rate in Bionic reached an unusable amount Status in systemd package in Ubuntu: Confirmed Bug description: Hi, Sorry to bother you - it seems we have this discussion every few months or so. I was looking at this due to an SRU and I realized that the last 50-100 tests on all architectures are currently failing. http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/amd64 http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/i386 http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/ppc64el http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/s390x On one hand I see the known flaky boot-and-smoke but that is fine. On the other hand I see the test "upstream" failing always and it seems not related to the actual proposed packages. Please help to resolve this mid-term. Short term I'll submit a force-badtest for this as it seems to hold up more and more with no gain of seeing plenty of peopl just hitting retry every now and then. If test "upstream" is utterly broken consider skipping it in the next upload that you do for regular service. That would bring back at least the remaining tests coverage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817721/+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 1855782] [NEW] Typo in the documentation: "systen" -> "system"
Public bug reported: Found on 14.04, 16.04, and 18.04. 19.04 and later distributions have it fixed. The "NAME" section of dconf7 manpage(http://manpages.ubuntu.com/manpages/bionic/man7/dconf.7.html) says "dconf - A configuration systen". "systen" should be a typo for "system". ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New ** Description changed: + Found on 14.04, 16.04, and 18.04. 19.04 and later distributions have it + fixed. + The "NAME" section of dconf7 manpage(http://manpages.ubuntu.com/manpages/bionic/man7/dconf.7.html) says "dconf - A configuration systen". "systen" should be a typo for "system". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1855782 Title: Typo in the documentation: "systen" -> "system" Status in d-conf package in Ubuntu: New Bug description: Found on 14.04, 16.04, and 18.04. 19.04 and later distributions have it fixed. The "NAME" section of dconf7 manpage(http://manpages.ubuntu.com/manpages/bionic/man7/dconf.7.html) says "dconf - A configuration systen". "systen" should be a typo for "system". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1855782/+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 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
We recently had the same problem, and it appears it could be due to the debug
output.
Calling rsync with -vvv hangs at the select, but with -vv (or less than 2) it
works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync package in Ubuntu:
Confirmed
Bug description:
In the last few months my home directory backup stopped completing.
I've been able to reproduce the problem on a single subdirectory
although I had to add the --debug=all flag to reproduce it on that
smaller directory. Specifically, this command never completes:
rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
The html2 directory is a copy of
gnuradio-3.7.8.1/build/docs/doxygen/html .
When I strace the command, I see this:
write(1, "sender finished /tmp/html2/atsc_"..., 58sender finished
/tmp/html2/atsc__interleaver_8h__incl.md5
) = 58
write(1, "send_files(338, /tmp/html2/atsc_"..., 59send_files(338,
/tmp/html2/atsc__interleaver_8h__incl.png)
) = 59
open("html2/atsc__interleaver_8h__incl.png", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=264657, ...}) = 0
write(1, "html2/atsc__interleaver_8h__incl"...,
37html2/atsc__interleaver_8h__incl.png
) = 37
read(3,
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\n\253\0\0\2\233\10\6\0\0\0h\242\""...,
262144) = 262144
select(6, [5], [4], [5], {60, 0}) = 2 (in [5], out [4], left {59,
96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95)
= 95
write(4,
"r\311\0\7\177\377\232\237\264\272e\300\300\240\316\264&\314\301\252*\37\256y\225g\373^\315j\370\350"...,
51574) = 51574
select(5, [], [4], [], {60, 0}) = 1 (out [4], left {59, 97})
write(4,
"\7\320\0\7\177\377\234|\7X\223Y\273\255c\27\25f\306\212\202\214#E\272\212t\1\225A\fU"...,
53259) = 53259
select(5, [], [4], [], {60, 0}
The select command times out over and over. I get the same behavior
when trying to back up my entire home directory but I don't need the
--debug=all flag in that case.
lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
apt-cache policy rsync
rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
*** 3.1.0-2ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386
Packages
100 /var/lib/dpkg/status
3.1.0-2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CurrentDesktop: KDE
Date: Wed Dec 23 09:44:17 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-09-18 (1922 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
SourcePackage: rsync
UpgradeStatus: Upgraded to trusty on 2014-12-27 (361 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+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 1851385] Re: ubuntu 19.10 / print bug : requires authentication
*** This bug is a duplicate of bug 1849859 *** https://bugs.launchpad.net/bugs/1849859 I have the same issue. Printing was working on a network shared printer (samba), ubuntu 19.04. Now on 19.10 it is not printing. I get "Credentials required in order to print", but not modal appears to enter details. I have also tried setting authentication directly user/password via Printers>Additional Printer Settings>[PRINTER>Propeties]>Device URI> Set authentication details now.. but makes no difference. No clue in CUPS error or access logs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1851385 Title: ubuntu 19.10 / print bug : requires authentication Status in cups package in Ubuntu: Confirmed Bug description: Hello, I have 2 computers(one laptop and one desktop) which have a dual boot Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a USB port from my modem on which my computers are connected using Wi- Fi. Since the upgrade of Ubuntu to version 19.10, I cannot print. On both computers I get the same message : [The printer] requires authentication / credentials required in order to print. With Ubuntu 19.04, I had absolutely no problem. I tried with a live USB with Ubuntu 19.04, there is no problem, the printer works. With a Ubuntu live 19.10, it doesn't work. If I plug the printer directly on a USB port on my computer, I get the same error message : [The printer] requires authentication / credentials required in order to print. It's the same behaviour on both computers, no I guess it must be a bug. Anyway I don't know which authentication I could do, with which ID and password ? Thank you very much ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 15:12:07 2019 Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B MachineType: Acer Aspire V5-571 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571 dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: Aspire V5-571 dmi.product.name: Aspire V5-571 dmi.product.sku: Aspire V5-571_072A_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1851385/+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 1849886] Re: lightdm does not work on eoan on raspberry pi 4
I found the following page online https://bluesabre.org/2019/10/20/install-xubuntu-19-10-on-a-raspberry-pi-4/ the claim is that this bug is in the greeter and it has been fixed upstream. i followed the directions to install a different greeter and the xubuntu now works. i had updated to the latest kernel (1014) before trying this fix but it did not help. The blog did not give a pointer to the upstream fix but it sounds like you are a pull away from fixing this. Kenny -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1849886 Title: lightdm does not work on eoan on raspberry pi 4 Status in lightdm package in Ubuntu: Confirmed Bug description: if you follow the directions on https://wiki.ubuntu.com/ARM/RaspberryPi sudo apt-get install xubuntu-desktop about 20% thru the installation it will ask which window manager you want (using dpkg-reconfigure). if you select lightdm, you will only get a blank greeter screen after you reboot. using sudo dpkg-reconfigure gdm3 resets this to gdm3 and after a reboot, everything is fine. this was done on a clean armhf eoan install on a 4gb raspberry pi 4B. I have done the install several times. This bug is repeatable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1849886/+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 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
https://github.com/lxc/lxc/issues/3221 Another LXC-container-doesn't -start-at-all type issue also observed on Ubuntu Eoan with systemd.unified_cgroup_hierarchy as well as Fedora 31. ** Bug watch added: LXC bug tracker #3221 https://github.com/lxc/lxc/issues/3221 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxcfs package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+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 1849859] Re: smb printing fails
@Andreas Hasenack, eu também falo Alemão, se tiver um problema com CUPS, cups-filters, ... :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial
Feel free to test lvm2 in bionic-proposed (2.02.176-4.1ubuntu3.18.04.2) and provide feedback to #1854981 . - Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1573982 Title: LVM boot problem - volumes not activated after upgrade to Xenial Status in curtin: Invalid Status in MAAS: Invalid Status in lvm2 package in Ubuntu: Confirmed Bug description: Soon after upgrade to Xenial (from 15.10) the boot process got broken. I'm using LVM for /root swap and other partitions. === The current behaviour is: When I boot short after the Grub login screen I'm getting log messages like: --- Scanning for Btrfs filesystems resume: Could not state the resume device file: '/dev/mapper/VolGroup' Please type in the full path... --- Then I press ENTER, for a few minutes some errors about floppy device access are raised (for some reason it tries to scan fd0 when floppy drive is empty). And then: --- Gave up waiting for root device. Common problems: ... ... ALERT! UUID=xxx-xxx does not exist. Dropping to a shell. --- From the BusyBox shell I managed to recover the boot by issuing "lvm vgchange -ay", then exit and then boot continues fine (all LVM file systems are successfully mounted). === One workaround so far is creating /etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange -ay". But I'm looking for cleaner solution. Boot used to work fine with 15.10. Actually the first boot after upgrading to Xenial actually worked OK too, I'm not sure what might changed meanwhile (I've been fixing some packages installation since mysql server upgrade has failed). === # lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1573982/+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 1849859] Re: smb printing fails
Für das druckproblem, ja -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1849859] Re: smb printing fails
I have now reported a new bug: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1855758 But anyway I think, it belongs here. @ Andreas Hasenbeck: Ich verstehe deinen letzten Kommentar nicht, mein Englisch ist aber auch nicht so perfekt. Schreibst du da, es gibt eine Lösung? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1855757] [NEW] Background image corrupted after standby 19.10
Public bug reported: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. 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 .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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 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' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX 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-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer 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 N/A 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 corruption eoan ubuntu ** Attachment added: "Screenshot from 2019-12-09 10-59-47.png" https://bugs.launchpad.net/bugs/1855757/+attachment/5311171/+files/Screenshot%20from%202019-12-09%2010-59-47.png ** Summary changed: - Background image corrupted after standby + Background image corrupted after standby 19.10 -- 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/1855757 Title: Background image corrupted after standby 19.10 Status in xorg package in Ubuntu: New Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. 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 .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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 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
[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects
Still have it in Ubuntu 19.10. -- 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/1717995 Title: extra domains not removed from resolv.conf when VPN disconnects Status in systemd package in Ubuntu: Fix Released Bug description: I use a VPN (network manager "vpnc" config) to connect to my work network. The gateway is "webvpn.purestorage.com". When I connect, I get "purestorage.com" added to the "search" line in my /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) - which makes perfect sense, the VPN passes this info to me and then I can connect to systems within the work network without having to use a FQDN. The bug (which is a regression from older versions of Ubuntu) is that when I lose my connection to the VPN (either because I disconnect explicitly, or because the network goes down or I suspend my laptop), the "purestorage.com" domain is not removed from those "search" lines. And for some reason this prevents me from resolving webvpn.purestorage.com (which prevents me from reconnecting to the VPN). In particular, if I connect and disconnect my VPN, I get: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: resolve call failed: No appropriate name servers or networks for name found If I then edit /etc/resolv.conf by hand to remove all the purestorage.com entries from the search line - in other words, change $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org purestorage.com dev.purestorage.com to $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org and change nothing else, then: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: 192.30.189.1 (vpn.purestorage.com) -- Information acquired via protocol DNS in 25.9ms. -- Data is authenticated: no I'm not sure if the bug is in systemd, network manager, or some other package, but I'm happy to try any debugging that is helpful to resolve this (no pun intended). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 11:20:17 2017 InstallationDate: Installed on 2016-09-01 (381 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901) MachineType: LENOVO 20FRS2FK00 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET53W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2FK00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2FK00 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717995/+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 1855747] Re: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop
/lib/udev/rules.d/71-nvidia.rules is definitely involved in this somehow; I'm seeing nvidia-persistenced started/stopped repeatedly too, and that's driven by that rules file. ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: 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/1855747 Title: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I'm seeing these lines repeated: ``` Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. ``` My system has been up ~an hour: $ uptime 12:02:28 up 1:00, 1 user, load average: 4.52, 4.80, 5.50 and I've seen a lot of these: $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9" 1333 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 243-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: i3 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Mon Dec 9 11:59:10 2019 InstallationDate: Installed on 2019-05-07 (215 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2019-11-15 (23 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.udev.udev.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317 mtime.conffile..etc.udev.udev.conf: 2019-11-28T09:22:42.096686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1855747/+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 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users
Hello Balint, or anyone else affected, Accepted update-notifier into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update- notifier/3.192.26.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: update-notifier (Ubuntu Eoan) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1855271 Title: Please make /etc/update-motd.d snippets runnable by regular users Status in base-files package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: New Status in base-files source package in Eoan: Fix Committed Status in ubuntu-release-upgrader source package in Eoan: Fix Committed Status in update-notifier source package in Eoan: Fix Committed Bug description: [Impact] * /etc/update-motd.d snippets throw errors when a normal user runs them. * This prevents showing MOTD when the user is dropped to a regular user's shell in WSL. [Test Case] * Run update-motd's autopkgtest and observe scripts not throwing errors. [Regression Potential] * The fixes are fairly simple, but to ensure no breakage the scripts are also run as root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
Changed the status to New, since I was still able to reproduce the issue on Bionic, using the "patched" network-manager version. ** Changed in: network-manager (Ubuntu) Status: Fix Released => New -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: New Status in network-manager source package in Bionic: Fix Released Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+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 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users
Hello Balint, or anyone else affected, Accepted ubuntu-release-upgrader into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-release-upgrader/1:19.10.15.4 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: ubuntu-release-upgrader (Ubuntu Eoan) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1855271 Title: Please make /etc/update-motd.d snippets runnable by regular users Status in base-files package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: New Status in base-files source package in Eoan: Fix Committed Status in ubuntu-release-upgrader source package in Eoan: Fix Committed Bug description: [Impact] * /etc/update-motd.d snippets throw errors when a normal user runs them. * This prevents showing MOTD when the user is dropped to a regular user's shell in WSL. [Test Case] * Run update-motd's autopkgtest and observe scripts not throwing errors. [Regression Potential] * The fixes are fairly simple, but to ensure no breakage the scripts are also run as root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+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 1855747] [NEW] systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop
Public bug reported: I'm seeing these lines repeated: ``` Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. ``` My system has been up ~an hour: $ uptime 12:02:28 up 1:00, 1 user, load average: 4.52, 4.80, 5.50 and I've seen a lot of these: $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9" 1333 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 243-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: i3 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Mon Dec 9 11:59:10 2019 InstallationDate: Installed on 2019-05-07 (215 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2019-11-15 (23 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.udev.udev.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317 mtime.conffile..etc.udev.udev.conf: 2019-11-28T09:22:42.096686 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1855747 Title: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop Status in systemd package in Ubuntu: New Bug description: I'm seeing these lines repeated: ``` Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. ``` My system has been up ~an hour: $ uptime 12:02:28 up 1:00, 1 user, load average: 4.52, 4.80, 5.50 and I've seen a lot of these: $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9" 1333 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 243-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: i3 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Mon Dec 9
[Touch-packages] [Bug 1855747] Re: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop
(The system booted up using nouveau, which is why the Nvidia drivers won't load.) -- 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/1855747 Title: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop Status in systemd package in Ubuntu: New Bug description: I'm seeing these lines repeated: ``` Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. ``` My system has been up ~an hour: $ uptime 12:02:28 up 1:00, 1 user, load average: 4.52, 4.80, 5.50 and I've seen a lot of these: $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9" 1333 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 243-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: i3 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Mon Dec 9 11:59:10 2019 InstallationDate: Installed on 2019-05-07 (215 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2019-11-15 (23 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.udev.udev.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317 mtime.conffile..etc.udev.udev.conf: 2019-11-28T09:22:42.096686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1855747/+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 1855549] Re: ubuntu-wsl: Please recommend show-motd
Hello Balint, or anyone else affected, Accepted ubuntu-meta into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-meta/1.440.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: ubuntu-meta (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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1855549 Title: ubuntu-wsl: Please recommend show-motd Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Eoan: Fix Committed Bug description: [ Impact ] * Desktop users of WSL are 'dropped into' the Ubuntu shell instead of logging in to the WSL container, thus they don't see MOTD. Then don't get information about the system's state via desktop notifications either, because the default Ubuntu WSL system does not start the Ubuntu desktop. * To show important system information to users being dropped to a shell directly the show-motd package was created to show MOTD using a /etc/profile.d script. * To have this script in place ubuntu-wsl needs to recommend show-motd. [ Test Case ] * Use 'apt-cache show ubuntu-wsl' to check if ubuntu-wsl recommends update-motd. [ Regression Potential ] * Pulling in a /etc/profile.d script that exits can make the started shell exit immediately. For this reason the shell does not exit in any case. The script can also throw confusing errors. To avoid such errors the script is tested in an autopkgtest and many related packages were fixed where errors were observed. The update-motd package adds Breaks: against related package versions which are known to show errors in MOTD when being run as a regular user. See LP: #1855271 for more details. [ Other Info ] * The SRU upload to Eoan waits for the acceptance of update-motd to Eoan and also for the seed merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1855549/+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 1855741] [NEW] Desktop background and UI is glitching out/checkerboard
Public bug reported: The desktop background and other small UI pieces that I click on or I change are all appearing to "glitch out" or turn into checkerboard artifacts in my new Ubuntu 19.10 installation. This most recent one happened as soon as I attempted to change my desktop background through the System Settings. See the attached screenshot for an example of the problem. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop 1.440 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 11:13:02 2019 InstallationDate: Installed on 2019-12-08 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug checkerboard eoan glitch gui papercut userinterface ** Attachment added: "Checkerboard artifacts appear on the desktop after changing the desktop background." https://bugs.launchpad.net/bugs/1855741/+attachment/5311147/+files/Screenshot%20from%202019-12-09%2011-12-35.png ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1855741 Title: Desktop background and UI is glitching out/checkerboard Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The desktop background and other small UI pieces that I click on or I change are all appearing to "glitch out" or turn into checkerboard artifacts in my new Ubuntu 19.10 installation. This most recent one happened as soon as I attempted to change my desktop background through the System Settings. See the attached screenshot for an example of the problem. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop 1.440 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 11:13:02 2019 InstallationDate: Installed on 2019-12-08 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1855741/+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 1819961] Re: binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements
Any updates on this one. It will be really helpful to have this bugfix backported to bionic binutils? -- 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/1819961 Title: binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Bionic: New Status in binutils source package in Cosmic: Fix Released Bug description: Due to following bug in binutils - gnu assembler compiled code optimised for AVX512 will not work correctly. binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements https://sourceware.org/bugzilla/show_bug.cgi?id=23465 it is fixed in binutils 2.31 but bug exist in 2.30 which is release used in xenial. Please consider backporting this bugfix to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1819961/+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 1855271] Proposed package upload rejected
An upload of ubuntu-release-upgrader to eoan-proposed has been rejected from the upload queue for the following reason: "The demotion updates seem suspicious, please re-upload with those left intact from the previous upload.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1855271 Title: Please make /etc/update-motd.d snippets runnable by regular users Status in base-files package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: New Status in base-files source package in Eoan: Fix Committed Bug description: [Impact] * /etc/update-motd.d snippets throw errors when a normal user runs them. * This prevents showing MOTD when the user is dropped to a regular user's shell in WSL. [Test Case] * Run update-motd's autopkgtest and observe scripts not throwing errors. [Regression Potential] * The fixes are fairly simple, but to ensure no breakage the scripts are also run as root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
Still occurring on d/e/f, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/n/network-manager/20191208_021641_f90a7@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/n/network-manager/20191130_013521_8a691@/log.gz ** Changed in: network-manager (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: network-manager (Ubuntu Disco) Importance: Undecided => Medium -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: New Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Disco: New Status in network-manager source package in Eoan: New Status in network-manager source package in Focal: New Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout. [Other Info] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+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 1855140] Re: haproxy package misses creation of default stats socket path in Docker container
Adding a systemd task as I really think this is more a general than a haproxy specific discussion/bug/feature. -- 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/1855140 Title: haproxy package misses creation of default stats socket path in Docker container Status in haproxy package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When installing the haproxy package from the current Ubuntu 18.04 Bionic repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file /etc/haproxy/haproxy.cfg: stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners Starting HAProxy manually will show the following error: # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg [ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock] After manual creation of the directory, the start works: # mkdir /run/haproxy # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg # ps auxf USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf root 1 0.0 0.0 18376 3016 ?Ss 15:40 0:00 bash /root/entrypoint.sh haproxy 31 0.0 0.0 54284 1252 ?Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg This can be reproduced with a simple Docker container the following Dockerfile: -- FROM ubuntu:18.04 MAINTAINER Claudio Kuenzler # install packages RUN apt-get update \ && apt-get install -y -qq haproxy CMD ["/usr/sbin/haproxy","-f","/etc/haproxy/haproxy.cfg"] -- Checking the haproxy package for the run directory shows nothing: # dpkg -L haproxy | grep run ; date Wed Dec 4 15:58:52 UTC 2019 *** Update: After analysis of the haproxy package (see https://www.claudiokuenzler.com/blog/917/haproxy-ubuntu-18.04-docker- image-not-starting-cannot-bind-unix-socket), it turns out that the /run/haproxy directory is defined in debian/haproxy.tmpfile. However tmpfile's are only considered in systems with SystemD. As Docker containers run without Systemd, this directory is never created. Suggestion: Do not rely on Systemd to create /run/haproxy. Maybe use debian/haproxy.dirs? However the permissions are not set in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+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 1855140] Re: haproxy package misses creation of default stats socket path in Docker container
Maybe related discussion https://lists.debian.org/debian- devel/2019/12/msg00060.html ** Also affects: systemd (Ubuntu) Importance: Undecided Status: 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/1855140 Title: haproxy package misses creation of default stats socket path in Docker container Status in haproxy package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When installing the haproxy package from the current Ubuntu 18.04 Bionic repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file /etc/haproxy/haproxy.cfg: stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners Starting HAProxy manually will show the following error: # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg [ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock] After manual creation of the directory, the start works: # mkdir /run/haproxy # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg # ps auxf USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf root 1 0.0 0.0 18376 3016 ?Ss 15:40 0:00 bash /root/entrypoint.sh haproxy 31 0.0 0.0 54284 1252 ?Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg This can be reproduced with a simple Docker container the following Dockerfile: -- FROM ubuntu:18.04 MAINTAINER Claudio Kuenzler # install packages RUN apt-get update \ && apt-get install -y -qq haproxy CMD ["/usr/sbin/haproxy","-f","/etc/haproxy/haproxy.cfg"] -- Checking the haproxy package for the run directory shows nothing: # dpkg -L haproxy | grep run ; date Wed Dec 4 15:58:52 UTC 2019 *** Update: After analysis of the haproxy package (see https://www.claudiokuenzler.com/blog/917/haproxy-ubuntu-18.04-docker- image-not-starting-cannot-bind-unix-socket), it turns out that the /run/haproxy directory is defined in debian/haproxy.tmpfile. However tmpfile's are only considered in systems with SystemD. As Docker containers run without Systemd, this directory is never created. Suggestion: Do not rely on Systemd to create /run/haproxy. Maybe use debian/haproxy.dirs? However the permissions are not set in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
** Also affects: network-manager (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Focal) Importance: Medium Status: New ** Also affects: network-manager (Ubuntu Disco) Importance: Undecided Status: New -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: New Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Disco: New Status in network-manager source package in Eoan: New Status in network-manager source package in Focal: New Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout. [Other Info] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+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 1853669] Re: systemd resolves own hostname to link local ipv6 address
PS: I also appreciate all the other mechanisms for having upstream dns set up from dhcp or other dynamic connections. Just that one machine is set up statically. -- 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/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Incomplete Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+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 1853669] Re: systemd resolves own hostname to link local ipv6 address
> If you manually configure your network, ... Ok, so adding it to /etc/resolv.conf is actually one of the supported ways. Thanks (for info). I'll stick to that. > Why is it wrong? try connecting to that address: avl@fpc:~$ telnet fe80::4687:fcff:fe9e:4ac7 22 Trying fe80::4687:fcff:fe9e:4ac7... telnet: Unable to connect to remote host: Invalid argument The link local inet6 address alone is useless information,... avl@fpc:~$ telnet fe80::4687:fcff:fe9e:4ac7%enp4s0 22 Trying fe80::4687:fcff:fe9e:4ac7%enp4s0... Connected to fe80::4687:fcff:fe9e:4ac7%enp4s0. Escape character is '^]'. SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 ... unless the network device name (enp4s0 on my machine) is attached to the inet6 address. -- 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/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Incomplete Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+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 1849859] Re: smb printing fails
Upstream work which might help, although it's about using the smbspool krb5 wrapper, it also has changes to the smbspool binary: https://gitlab.com/samba-team/samba/merge_requests/961 ** Summary changed: - error when connecting to smb server + smb printing fails -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1852489] Re: [SRU] Enable support for Ussuri Cloud Archive
Thanks Brian. Verified successfully on bionic-proposed: root@b1:~# apt policy software-properties-common software-properties-common: Installed: 0.96.24.32.12 Candidate: 0.96.24.32.12 Version table: *** 0.96.24.32.12 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.96.24.32.11 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 0.96.24.32.1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@b1:~# sudo add-apt-repository cloud-archive:ussuri Ubuntu Cloud Archive for OpenStack Ussuri More info: https://wiki.ubuntu.com/OpenStack/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. ... root@b1:~# sudo add-apt-repository cloud-archive:ussuri-proposed Ubuntu Cloud Archive for OpenStack Ussuri [proposed] More info: https://wiki.ubuntu.com/OpenStack/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. ... root@b1:~# sudo apt install python3-oslo.utils ... root@b1:~# apt policy python3-oslo.utils python3-oslo.utils: Installed: 3.41.1-0ubuntu1~cloud0 Candidate: 3.41.1-0ubuntu1~cloud0 Version table: *** 3.41.1-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-proposed/ussuri/main amd64 Packages 500 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri/main amd64 Packages 100 /var/lib/dpkg/status 3.35.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1852489 Title: [SRU] Enable support for Ussuri Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Bug description: Please add support for: cloud-archive:ussuri cloud-archive:ussuri-proposed This will also need to be SRU'd back to bionic. [Impact] End users have to manually enable the ussuri cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:ussuri sudo add-apt-repository cloud-archive:ussuri-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852489/+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 1853669] Re: systemd resolves own hostname to link local ipv6 address
> Result is, that localhost's systemd-resolved now no longer > knows about upstream dns 10.2.2.3 -- where else am I supposed > to configure that? If you use systemd-networkd to configure your network (or, netplan, which will indirectly configure networkd or network-manager for you), then systemd-resolved will be updated to know what your actual upstream nameserver(s) are; you can query what current upstream nameservers resolved is using with the 'systemd-resolve --status' command. If you use ifupdown, there is a dhclient hook that tells resolved (or resolvconf) about your upstream nameservers. If you manually configure your network, it's up to you to also manually configure your /etc/resolv.conf file, or manually tell resolved about your upstream nameservers, which you can do with the systemd-resolved command (see its man page). > It consults the routing table, and, when doing so, it deals wrongly with > link-local > inet6 addresses. That's what this bugreport was about. Why is it wrong? All the ipv6 addresses it resolves for its own hostname are reachable locally. ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Incomplete Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+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 1854190] Re: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
*** This bug is a duplicate of bug 1829401 *** https://bugs.launchpad.net/bugs/1829401 ** This bug has been marked a duplicate of private bug 1832057 ** This bug is no longer a duplicate of bug 1832057 software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow ** This bug has been marked a duplicate of bug 1829401 gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1854190 Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow Status in software-properties package in Ubuntu: New Bug description: Upon attempting to add debug repositories to apt and then opening Software Updater, the cache loaded and then I switched to the Ubuntu Software Tab. I then clicked the checkmark next to "software restricted by copyright or legal issues." I then clicked the Close button, and then the reload button. The window that shows the reload process became stuck and would not be dismissed, softlocking me in the update-manager app and forcing me to kill the application. Expected Results: Software Update applies the changes without issue and then quits, or throws and error if that is not possible and I made a mistake Actual Results: Software Update manager hangs ans softlocks me into forcing me to kill the process. Prior to the issue occurring, I ran "echo -e "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse\ndeb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/ddebs.list" and then opened Software Update manager. I was attempting to follow the steps to debug on this URL: https://wiki.ubuntu.com/DebuggingProgramCrash However, I skipped the first step in adding the debug repositories and added the one in the second step before opening Software & Updates. Description: Ubuntu 19.10 Release: 19.10 software-properties-gtk: Installed: 0.98.5 Candidate: 0.98.5 Version table: *** 0.98.5 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.98.5 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:34:09 2019 ExecutablePath: /usr/bin/software-properties-gtk ExecutableTimestamp: 1562940163 InstallationDate: Installed on 2019-11-20 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 --toplevel 67108867 ProcCwd: /home/edwin ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', '--toplevel', '67108867'] PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1854190/+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 1832057] Re: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
*** This bug is a duplicate of bug 1829401 *** https://bugs.launchpad.net/bugs/1829401 ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1829401 gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1832057 Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow Status in software-properties package in Ubuntu: Confirmed Bug description: Falló actualización de repositorios ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.98.4 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 21:32:02 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-06-02 (5 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 --toplevel 75497475 ProcEnviron: LANGUAGE=es_SV:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_SV.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', '--toplevel', '75497475'] PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow UpgradeStatus: Upgraded to eoan on 2019-06-02 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1832057/+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 1855640] Re: UI hang during Cache Refresh
*** This bug is a duplicate of bug 1829401 *** https://bugs.launchpad.net/bugs/1829401 ** This bug has been marked a duplicate of private bug 1832057 ** This bug is no longer a duplicate of bug 1832057 software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow ** This bug has been marked a duplicate of bug 1829401 gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1855640 Title: UI hang during Cache Refresh Status in software-properties package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 0.98.5 3) Refresh cache without UI hang. 4) UI hanged during cache refresh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1855640/+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 1774611] Re: Add an option to filter out Proprietary snaps (and Flatpaks) from GNOME Software
** Changed in: software-properties (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1774611 Title: Add an option to filter out Proprietary snaps (and Flatpaks) from GNOME Software Status in software-properties package in Ubuntu: New Bug description: Currently, there's no options to filter out proprietary snaps (and, I suppose, Flatpaks?) from Software. When I click on the application drop-down for Software, it links to Software & Updates, which I suppose is where Software would be filtered. Please could an option to filter out proprietary snaps (just as there are options to filter out proprietary Debs by only enabling the main and universe pockets) be provided? The option for snaps should only be visible when gnome- software-plugin-snap is installed and the option for Flatpaks only visible when gnome-software-plugin-flatpak is installed. Like with the Debs though, perhaps this should also affect the command line, if a `snap install` is attempted for a proprietary snap, or one attempts to install a proprietary Flatpak from a remote, the command line should print something like 'The ability to install proprietary snaps' or Flatpaks 'has been disabled so the snap' or Flatpak 'will not be installed. If you would like to install the proprietary snap' or Flatpak 'then change the setting for proprietary snaps' or Flatpaks 'in Software & Updates'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Jun 1 10:25:23 2018 InstallationDate: Installed on 2017-08-03 (301 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-04-22 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1774611/+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 1855643] Re: Rename "Software & Updates" to "Application Update Sources" and integrate it into the Settings app.
*** This bug is a duplicate of bug 1058067 *** https://bugs.launchpad.net/bugs/1058067 ** Changed in: software-properties (Ubuntu) Importance: Undecided => Wishlist ** This bug has been marked a duplicate of bug 1058067 "Software Sources" opens in a separate window from System Settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1855643 Title: Rename "Software & Updates" to "Application Update Sources" and integrate it into the Settings app. Status in software-properties package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 0.98.5 3) In the Settings app, "Application Update Sources" could be placed below "Applications". 4) Could not change application update sources in Settings app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1855643/+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?
** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => glib2.0 (Ubuntu) -- 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 1855647] [NEW] When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc?
You have been subscribed to a public bug: 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. ** Affects: glib2.0 (Ubuntu) Importance: Wishlist Status: New ** Tags: eoan -- When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc? https://bugs.launchpad.net/bugs/1855647 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 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 1855710] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1855710 Title: Losing my printer Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Invalid Bug description: Hello, After the last update of the system lost access to the printer and could not connect to it. Thanks Ferran Lindström ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 9 13:14:04 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1495] InstallationDate: Installed on 2016-10-25 (1139 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcEnviron: LANGUAGE=ca PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-170-generic root=UUID=55d2d15a-85c8-4ae0-bd45-dc47177bc25b ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.09 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.09:bd07/01/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Dec 8 17:56:16 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855710/+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 1855710] Re: Losing my printer
No details were given on why Xorg was tagged. If Xorg was tagged for a reason, please leave a comment as to why and it can be changed back to "New" ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1855710 Title: Losing my printer Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Invalid Bug description: Hello, After the last update of the system lost access to the printer and could not connect to it. Thanks Ferran Lindström ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 9 13:14:04 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1495] InstallationDate: Installed on 2016-10-25 (1139 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcEnviron: LANGUAGE=ca PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-170-generic root=UUID=55d2d15a-85c8-4ae0-bd45-dc47177bc25b ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.09 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.09:bd07/01/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Dec 8 17:56:16 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855710/+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 1855710] Re: Losing my printer
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have provided, this looks to me like you'd benefit from support rather than having a bug. You tagged Xorg (graphical display server) but report a printer issue? I don't see the connection. This bug report can be converted to a question (which is aimed at support). You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community- support/709 I do see the following [ 10.312447] usblp 1-1.1:1.1: usblp0: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x03F0 pid 0x9311 however you have provided little information on how you normally access the printer, what changed, or if any new messages were obtained. From what program do you print? Does it provide anything. Are there any crash files in /var/crash/ ? Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1855710 Title: Losing my printer Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Invalid Bug description: Hello, After the last update of the system lost access to the printer and could not connect to it. Thanks Ferran Lindström ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 9 13:14:04 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1495] InstallationDate: Installed on 2016-10-25 (1139 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcEnviron: LANGUAGE=ca PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-170-generic root=UUID=55d2d15a-85c8-4ae0-bd45-dc47177bc25b ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.09 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.09:bd07/01/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Dec 8 17:56:16 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855710/+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 1849859] Re: error when connecting to smb server
A new bug please, I'm focusing on the printing case for this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: error when connecting to smb server Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1855710] [NEW] Losing my printer
Public bug reported: Hello, After the last update of the system lost access to the printer and could not connect to it. Thanks Ferran Lindström ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 9 13:14:04 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1495] InstallationDate: Installed on 2016-10-25 (1139 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcEnviron: LANGUAGE=ca PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-170-generic root=UUID=55d2d15a-85c8-4ae0-bd45-dc47177bc25b ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.09 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.09:bd07/01/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Dec 8 17:56:16 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 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/1855710 Title: Losing my printer Status in xorg package in Ubuntu: New Bug description: Hello, After the last update of the system lost access to the printer and could not connect to it. Thanks Ferran Lindström ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 9 13:14:04 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1495] InstallationDate: Installed on 2016-10-25 (1139 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcEnviron: LANGUAGE=ca PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-170-generic root=UUID=55d2d15a-85c8-4ae0-bd45-dc47177bc25b ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.09 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.09:bd07/01/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
[Touch-packages] [Bug 1853852] Re: hard to reproduce issues in systemd autopkgtest against new libseccomp 2.4.2
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/systemd/+git/systemd/+merge/376514
--
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/1853852
Title:
hard to reproduce issues in systemd autopkgtest against new libseccomp
2.4.2
Status in libseccomp:
New
Status in libseccomp package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Triaged
Bug description:
Hi,
I'm mostly reporting this if to one of the people watching systemd more
closely this is in any form a known issue or if there are any hints.
I recently merged libseccomp 2.4.2 and after a few initial cleanups that
worked well.
But on propsoed-migration I hit systemd test issues.
I have read about issues with arm NR_open defines - I had the same in
chrony - but that is fixed in libseccomp and that isn't failing in
systemd.
i386 and s390x (only those) have failing tests
- http://autopkgtest.ubuntu.com/packages/s/systemd/focal/s390x
- http://autopkgtest.ubuntu.com/packages/s/systemd/focal/i386
Example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20191120_105726_aea23@/log.gz
Failnig subtests are:
root-unittests FAIL non-zero exit status 134
upstream FAIL non-zero exit status 1
And looking at the details of root-unittest I found:
http://paste.ubuntu.com/p/N7q9PX3hFN/
== test-seccomp ===
...
/* test_memory_deny_write_execute_mmap */
Operating on architecture: s390
Failed to add shmat() rule for architecture s390, skipping: Invalid argument
Operating on architecture: s390x
Failed to add shmat() rule for architecture s390x, skipping: Invalid argument
Assertion 'p == MAP_FAILED' failed at src/test/test-seccomp.c:493, function
test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at src/test/test-seccomp.c:507, function
test_memory_deny_write_execute_mmap(). Aborting.
FAIL: test-seccomp (code: 134)
But when installing source of systemd and the new libseccomp in a
Focal VM with proposed enabled it works just fine. Actually I just
found that it does have a good RC but breaks so maybe it is debuggable
after all.
To manage notifications about this bug go to:
https://bugs.launchpad.net/libseccomp/+bug/1853852/+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 1853669] Re: systemd resolves own hostname to link local ipv6 address
I do agree that it is correct(TM) behaviour to not ask upstream DNS for
bare ("single label") names. But this is not what this bugreport was
about.
The point is what systemd-resolved does in such a case, where it cannot
consult upstream DNS, and also doesn't find the name in local
/etc/hosts:
It consults the routing table, and, when doing so, it deals wrongly with
link-local inet6 addresses. That's what this bugreport was about.
--
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/1853669
Title:
systemd resolves own hostname to link local ipv6 address
Status in systemd package in Ubuntu:
Confirmed
Bug description:
I've got an ethernet-device that only has a configured ipv4 address,
and some auto-generated link-local (aka "scope link") ipv6 address.
Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
DNS-server listening on 127.0.0.53) for this host's hostname gets back
two addresses: the correct ipv4 address, and a broken ipv6 address.
Unlike on ipv4, it is possible for the same ipv6-address to be
assigned to multiple devices, and therefore the address is only valid
in the context of the eth-device.
Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64
scopeid 0x20"
then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall
connect() typically fails with EINVAL.
To make it a valid address, it needs to be suffixed with a "%" and the device
name, like:
fe80::4687:fcff:fe9e:4ac7%enp4s0
Either the resolver can return the link name attached to the address
separated with a "%" char, or it needs to ignore link-local inet6
addresses.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+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 1853852] Re: hard to reproduce issues in systemd autopkgtest against new libseccomp 2.4.2
Issue is in systemd, fix known (now).
I'll prep an MP to discuss, but given how much extra churn systemd updates
usually cause this most likely won't be uploaded "on its own"
** Changed in: libseccomp (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
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/1853852
Title:
hard to reproduce issues in systemd autopkgtest against new libseccomp
2.4.2
Status in libseccomp:
New
Status in libseccomp package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Triaged
Bug description:
Hi,
I'm mostly reporting this if to one of the people watching systemd more
closely this is in any form a known issue or if there are any hints.
I recently merged libseccomp 2.4.2 and after a few initial cleanups that
worked well.
But on propsoed-migration I hit systemd test issues.
I have read about issues with arm NR_open defines - I had the same in
chrony - but that is fixed in libseccomp and that isn't failing in
systemd.
i386 and s390x (only those) have failing tests
- http://autopkgtest.ubuntu.com/packages/s/systemd/focal/s390x
- http://autopkgtest.ubuntu.com/packages/s/systemd/focal/i386
Example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20191120_105726_aea23@/log.gz
Failnig subtests are:
root-unittests FAIL non-zero exit status 134
upstream FAIL non-zero exit status 1
And looking at the details of root-unittest I found:
http://paste.ubuntu.com/p/N7q9PX3hFN/
== test-seccomp ===
...
/* test_memory_deny_write_execute_mmap */
Operating on architecture: s390
Failed to add shmat() rule for architecture s390, skipping: Invalid argument
Operating on architecture: s390x
Failed to add shmat() rule for architecture s390x, skipping: Invalid argument
Assertion 'p == MAP_FAILED' failed at src/test/test-seccomp.c:493, function
test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at src/test/test-seccomp.c:507, function
test_memory_deny_write_execute_mmap(). Aborting.
FAIL: test-seccomp (code: 134)
But when installing source of systemd and the new libseccomp in a
Focal VM with proposed enabled it works just fine. Actually I just
found that it does have a good RC but breaks so maybe it is debuggable
after all.
To manage notifications about this bug go to:
https://bugs.launchpad.net/libseccomp/+bug/1853852/+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 1853439] Re: xubuntu 18.04.3 rt5651 sound problem
var/crash folder is empty output: erkan@unluturk:~$ ps auxw | grep pulse erkan 1417 0.8 1.7 1557368 33520 ? Sl 13:56 0:00 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libpulseaudio-plugin.so 9 10485799 pulseaudio PulseAudio Eklentisi PulseAudio ses sisteminin ses yüksekliğini ayarlayın erkan 2104 0.0 0.0 23416 1088 pts/0S+ 13:57 0:00 grep --color=auto pulse erkan@unluturk:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853439 Title: xubuntu 18.04.3 rt5651 sound problem Status in pulseaudio package in Ubuntu: Incomplete Bug description: no sound ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Thu Nov 21 13:27:58 2019 InstallationDate: Installed on 2019-11-20 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=tr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853439/+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 1853439] Re: xubuntu 18.04.3 rt5651 sound problem
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853439/+attachment/5311074/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853439 Title: xubuntu 18.04.3 rt5651 sound problem Status in pulseaudio package in Ubuntu: Incomplete Bug description: no sound ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Thu Nov 21 13:27:58 2019 InstallationDate: Installed on 2019-11-20 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=tr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853439/+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 1855693] [NEW] microphone of the headset is not detected
Public bug reported: I have a set of headphones that work as speakers and microphone without problem on an android phone or on macos. Under ubuntu they are only detected as outputs, but not as microphone. in the audio settings I can select the output to be one of: internal speakers, hdmi monitor, or these headphones. The only input is the internal microphone of the laptop. When I make a call with microsoft teams, the other end confirms that they hear the sound from the room. The headphones are similar to these: https://www.ebay.com/itm/Earphones- Handsfree-Headphones-for-Samsung- Galaxy-S8-A5-A7-A8-A9-J1-J3-J5-J7-UK/163465454907 with a connector with four segments. I also tried another set of headphones, different brand, same behaviour: work fine in other devices, work as output-only in ubuntu ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1577 F pulseaudio /dev/snd/controlC1: peter 1577 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 11:00:07 2019 InstallationDate: Installed on 2019-11-14 (24 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 187.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr187.0.0.0.0:bd07/22/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1855693 Title: microphone of the headset is not detected Status in pulseaudio package in Ubuntu: New Bug description: I have a set of headphones that work as speakers and microphone without problem on an android phone or on macos. Under ubuntu they are only detected as outputs, but not as microphone. in the audio settings I can select the output to be one of: internal speakers, hdmi monitor, or these headphones. The only input is the internal microphone of the laptop. When I make a call with microsoft teams, the other end confirms that they hear the sound from the room. The headphones are similar to these: https://www.ebay.com/itm /Earphones-Handsfree-Headphones-for-Samsung- Galaxy-S8-A5-A7-A8-A9-J1-J3-J5-J7-UK/163465454907 with a connector with four segments. I also tried another set of headphones, different brand, same behaviour: work fine in other devices, work as output-only in ubuntu ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1577 F pulseaudio /dev/snd/controlC1: peter 1577 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 11:00:07 2019 InstallationDate: Installed on 2019-11-14 (24 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 187.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr187.0.0.0.0:bd07/22/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1855693/+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 1832414] Re: Removing document files spam from cups
Same problem here with Ubuntu Server 19.10 (cups 2.2.12-2ubuntu1) + LogLevel to debug. Thousands of lines per second as below... it happen when printing and fill badly the logs too. D [09/Dec/2019:11:00:16 +0100] [Job 50127] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) D [09/Dec/2019:11:00:16 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" D [09/Dec/2019:11:00:16 +0100] [Job 50128] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) D [09/Dec/2019:11:00:16 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" D [09/Dec/2019:11:00:16 +0100] [Job 50129] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) D [09/Dec/2019:11:00:16 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" D [09/Dec/2019:11:00:16 +0100] [Job 50130] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) D [09/Dec/2019:11:00:16 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" D [09/Dec/2019:11:00:16 +0100] [Job 50131] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) D [09/Dec/2019:11:00:16 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" D [09/Dec/2019:11:00:16 +0100] [Job 50132] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832414 Title: Removing document files spam from cups Status in cups package in Ubuntu: Confirmed Bug description: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854689] Re: BlueZ 5.52 release
Here's a new release of 5.52 with 5.51-0ubuntu2 included. ** Attachment added: "bluez_5.52-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+attachment/5311063/+files/bluez_5.52-0ubuntu1.debian.tar.xz -- 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/1854689 Title: BlueZ 5.52 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.52 release: http://www.bluez.org/release-of-bluez-5-52/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+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 1855521] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311061/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1855521] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311060/+files/UdevDb.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1854689] Re: BlueZ 5.52 release
Seb just pointed out this needs redoing because this appeared over the weekend: https://launchpad.net/ubuntu/+source/bluez/5.51-0ubuntu2 -- 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/1854689 Title: BlueZ 5.52 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.52 release: http://www.bluez.org/release-of-bluez-5-52/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+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 1855521] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311059/+files/RfKill.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855521] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311058/+files/PulseList.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855521] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311053/+files/ProcCpuinfo.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855521] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311052/+files/Lspci.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855521] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311057/+files/ProcModules.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855521] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311056/+files/ProcInterrupts.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855521] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311055/+files/ProcEnviron.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855521] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311054/+files/ProcCpuinfoMinimal.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855521] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311050/+files/CurrentDmesg.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855521] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311051/+files/IwConfig.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1855521] Re: [Dell Inspiron 5490] Internal microphone not detected
apport information ** Tags added: apport-collected ** Description changed: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: tom1357 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-12-06 (2 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD + Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint + Bus 001 Device 004: ID 8087:0aaa Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. Inspiron 5490 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-24-generic N/A + linux-backports-modules-5.3.0-24-generic N/A + linux-firmware1.183.2 + Tags: eoan + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/30/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.3.0 + dmi.board.name: 0012KY + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 5490 + dmi.product.sku: 0955 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311048/+files/AlsaInfo.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops
[Touch-packages] [Bug 1855521] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1855521/+attachment/5311049/+files/CRDA.txt -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (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: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1849859] Re: error when connecting to smb server
Or should I open a new bug report? This new bug is very annoying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: error when connecting to smb server Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1846787] Re: systemd-logind leaves leftover sessions and scope files
This bug was fixed in the package dbus - 1.10.6-1ubuntu3.5
---
dbus (1.10.6-1ubuntu3.5) xenial; urgency=medium
* Prevent logind from leaking session files (LP: #1846787). Fixed by
upstream patches:
- d/p/Only-read-one-message-at-a-time-if-there-are-fds-pen.patch
- d/p/bus-Fix-timeout-restarts.patch
- d/p/DBusMainLoop-ensure-all-required-timeouts-are-restar.patch
-- Heitor Alves de Siqueira Mon, 07 Oct 2019
08:29:04 -0300
** Changed in: dbus (Ubuntu Xenial)
Status: Fix Committed => 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/1846787
Title:
systemd-logind leaves leftover sessions and scope files
Status in dbus package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Xenial:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Bug description:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
$ git describe --contains d8fdc62037b5
v230~71^2~2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34
