[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
We have narrowed it down to a flaw in a specific configuration setting on this NIC, so we're comparing the good and bad configurations now. Primary port: enp94s0f0 Secondary port: enp94s0f1d1 A] Good config for fault-tolerance (active-backup) bonding mode: -- Primary port = active interface; Secondary port = backup B] Bad config for fault-tolerance (active-backup) bonding mode: -- Primary port = backup interface; Secondary port = active We are consistently able to reproduce a drop rate difference with UDP pkts, for the above good/bad cases: Good Case UDP MTR Test Result - mtr --no-dns --report --report-cycles 60 --udp -s 1428 $DEST Start: 2020-02-10T10:14:01+ HOST: hostname Loss% Snt Last Avg Best Wrst StDev 1.|-- nn.nn.nnn.nnn 0.0%600.3 0.2 0.2 0.3 0.0 Bad Case UDP MTR Test Result --- mtr --no-dns --report --report-cycles 60 --udp -s 1428 $DEST Start: 2020-02-10T14:10:52+ HOST: hostname Loss% Snt Last Avg Best Wrst StDev 1.|-- nn.nn.nnn.nnn 8.3%600.3 0.3 0.2 0.4 0.0 -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error.
[Touch-packages] [Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
We have a new MP that fixes things for real in Focal. The former SRUs already have been set to verification-failed and can be cancelled from -proposed if it helps to clear up things. ** Changed in: rsyslog (Ubuntu Disco) Status: Fix Committed => Triaged ** Changed in: rsyslog (Ubuntu Bionic) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: In Progress Status in rsyslog source package in Bionic: Triaged Status in rsyslog source package in Disco: Triaged Status in rsyslog source package in Eoan: Triaged Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
** Changed in: rsyslog (Ubuntu) Status: Fix Released => In Progress ** Also affects: rsyslog (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: rsyslog (Ubuntu Eoan) Status: New => Triaged ** Changed in: rsyslog (Ubuntu Eoan) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: In Progress Status in rsyslog source package in Bionic: Triaged Status in rsyslog source package in Disco: Triaged Status in rsyslog source package in Eoan: Triaged Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Hi all, thanks for the fixes in Eoan. Unfortunately we have a product based on disco and cannot move forward at this time. Being a networking shop, this issue has a serious effect on us and we would like to avoid moving to something like ifupdown2 within our stable branch. For our users the real impact of the bug is not that that the interface that we are currently reconfiguring is suffering a downtime, but the fact that _all_ interfaces have their aliases removed if networkd is restarted. The proposed KeepConfiguration solution kind of beats the purpose of reconfiguring the interfaces, as old addresses are kept and need to be handled manually. Also it interferes with how DHCP works. I believe this might be an issue for others as well. >From our point of view the ideal solution would be a combination of the keepalived patch that detects VIP removal and systemd version 244 that already supports "networkctl reconfigure" and "networkctl reload". Is there any chance that v244 is backported to bionic? It is already included in focal and debian stable backports, but unfortunately I am not familiar enough with systemd development to tell what the impact of this would be. As for keepalived, in bug #1819074 there was an ongoing investigation on the patch, that implements the keepalived transition on removing the VIP. We have traced back this functionality to this patch: https://github.com/acassen/keepalived/commit/0b1528c76d3fe8d1c5765841df86c59570a036da It was born before v1.3.6 was released, so we hope that it is self- contained enough for a backport if v2.0 of keepalived is not included in bionic-backports. Best, Balint -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in Keepalived Charm: New Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Status in keepalived source package in Disco: Won't Fix Status in systemd source package in Disco: Won't Fix Status in keepalived source package in Eoan: In Progress Status in systemd source package in Eoan: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses:
[Touch-packages] [Bug 1862733] Re: crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1862733 Title: crash Status in Ubuntu: Incomplete Bug description: crach ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Feb 10 22:43:21 2020 DistUpgraded: 2020-01-15 21:02:05,550 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.3.0-28-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2286] InstallationDate: Installed on 2020-01-16 (26 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 20Q0002EUS ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=125967d5-379e-4de9-aa68-c6208d80892a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-01-16 (26 days ago) dmi.bios.date: 01/03/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET84W (1.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q0002EUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2JET84W(1.62):bd01/03/2020:svnLENOVO:pn20Q0002EUS:pvrThinkPadX390:rvnLENOVO:rn20Q0002EUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X390 dmi.product.name: 20Q0002EUS dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jan 15 20:25:03 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1862733/+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 1862733] [NEW] crash
Public bug reported: crach ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Feb 10 22:43:21 2020 DistUpgraded: 2020-01-15 21:02:05,550 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.3.0-28-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2286] InstallationDate: Installed on 2020-01-16 (26 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 20Q0002EUS ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=125967d5-379e-4de9-aa68-c6208d80892a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-01-16 (26 days ago) dmi.bios.date: 01/03/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET84W (1.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q0002EUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2JET84W(1.62):bd01/03/2020:svnLENOVO:pn20Q0002EUS:pvrThinkPadX390:rvnLENOVO:rn20Q0002EUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X390 dmi.product.name: 20Q0002EUS dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jan 15 20:25:03 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1862733 Title: crash Status in xorg package in Ubuntu: New Bug description: crach ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Feb 10 22:43:21 2020 DistUpgraded: 2020-01-15 21:02:05,550 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.3.0-28-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2286] InstallationDate: Installed on 2020-01-16 (26 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 20Q0002EUS ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=125967d5-379e-4de9-aa68-c6208d80892a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-01-16 (26 days ago) dmi.bios.date: 01/03/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET84W (1.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q0002EUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2JET84W(1.62):bd01/03/2020:svnLENOVO:pn20Q0002EUS:pvrThinkPadX390:rvnLENOVO:rn20Q0002EUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X390 dmi.product.name: 20Q0002EUS dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2
[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected
Thank you for the info Bastian. Now all we can do is wait for the bugfix. -- 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/1861063 Title: Dualshock4 controller doesn't stay connected Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all. Once the pairing is completed, if I try to connect it it doesn't stay connected. I have checked the dmesg and apparently there is a buffer overflow somewhere. I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work. Dmesg output: [4.099796] Bluetooth: Core ver 2.22 [4.099833] Bluetooth: HCI device and connection manager initialized [4.099837] Bluetooth: HCI socket layer initialized [4.099839] Bluetooth: L2CAP socket layer initialized [4.099842] Bluetooth: SCO socket layer initialized [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018 [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.855413] Bluetooth: BNEP filters: protocol multicast [6.855416] Bluetooth: BNEP socket layer initialized [ 14.234706] Bluetooth: RFCOMM TTY layer initialized [ 14.234711] Bluetooth: RFCOMM socket layer initialized [ 14.234715] Bluetooth: RFCOMM ver 1.11 [ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow Release: Description: Ubuntu 19.10 Release: 19.10 Package Info: bluez: Installed: 5.50-0ubuntu4 Candidate: 5.50-0ubuntu4 Version table: *** 5.50-0ubuntu4 500 500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 14:11:19 2020 InstallationDate: Installed on 2019-11-26 (62 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FCS33A00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago) dmi.bios.date: 03/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET68W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCS33A00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCS33A00 dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:8289 acl:41 sco:0 events:268 errors:0 TX bytes:9494 acl:44 sco:0 commands:163 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+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 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed
Got bit by this as well, recall fixing it a few years ago but must have clobbered my changes on upgrade bionic -> eoan? Having VirtualBox installed broke it, fix was to comment out this line in /lib/systemdd/system/systemd-timesyncd.service.d and restart systemd: ConditionFileIsExecutable=!/usr/sbin/VBoxService Don't recall being asked about a config file change during upgrade although maybe it did and didn't remember. Further info here: https://askubuntu.com/questions/940311/time-in-ubuntu-16-04-not- updating-from-internet#1005355 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1849156 Title: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed Status in ntp package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in ntp source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Status in ntp source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Bug description: Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd- timesyncd.service.d/disable-with-time-daemon.conf. This prevents systemd-timesyncd.service from starting if the ntp package has been installed. However, ntp.service has a Conflicts directive for systemd-timesyncd.service. If both services are enabled, neither will start on boot. This breaks upgrades from < 19.10 to 19.10 for systems that have both ntp and systemd installed. Possible workarounds: - Uninstall ntp - Disable systemd-timesyncd.service % lsb_release -rd Description:Ubuntu 19.10 Release:19.10 % apt-cache policy systemd systemd: Installed: 242-7ubuntu3 Candidate: 242-7ubuntu3 Version table: *** 242-7ubuntu3 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status % apt-cache policy ntp ntp: Installed: 1:4.2.8p12+dfsg-3ubuntu2 Candidate: 1:4.2.8p12+dfsg-3ubuntu2 Version table: *** 1:4.2.8p12+dfsg-3ubuntu2 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status % dpkg -S /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf systemd: /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf % sudo systemctl status ntp ● ntp.service - Network Time Service Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:ntpd(8) % sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: inactive (dead) Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago Docs: man:systemd-timesyncd.service(8) Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network Time Synchronization being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1849156/+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 1856008] Re: openssh-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- 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/1856008 Title: openssh-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed Status in openssh package in Ubuntu: Expired Bug description: Check if you are using third party repositories. If so disable them, since they are a common source of problems. Furthermore run the following command in a Terminal: apt-get install -f Transaction failed: The package system is broken The following packages have unmet dependencies: openssh-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed openssh-sftp-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed i will not installed the open ssh server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1856008/+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 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: Expired Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 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 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd',
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
For 18.04 and 19.10, the alsa-lib only supports ucm, Intel audio team write the ucm confs and this is sth I plan to SRU to Eoan and Bionic in this bug. For 20.04, we choose alsa-lib-1.2.1.2, it supports ucm2, and upstream writes the ucm2 confs based on the Intel audio team's work, we use #1862505 to track it. So the ucm for bionic and eoan is not backported from ucm2 of 1.2.1.2, it is maintained by Intel: https://github.com/thesofproject/alsa-ucm- conf.git the ucm2 for focal is maintained by upstream: https://github.com/alsa- project/alsa-ucm-conf.git, it is written based on the Intel's work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1862717] Re: Automatic crash report bug reports opened in gedit rather than the browser
Relevant parts from journalctl: Feb 11 13:03:53 slate systemd[6652]: Starting Notification regarding a crash report... Feb 11 13:03:53 slate update-notifier-crash[260823]: /usr/bin/whoopsie Feb 11 13:03:54 slate update-notifier-crash[260837]: /var/crash/libdleyna-core-1 Feb 11 13:04:19 slate systemd[6652]: update-notifier-crash.service: Succeeded. Feb 11 13:04:19 slate systemd[6652]: Started Notification regarding a crash report. Feb 11 13:05:51 slate polkitd(authority=local)[2853]: Operator of unix-session:2 successfully authenticated as unix-user:amurray to gain ONE-SHOT authorization for action com.ubuntu.apport.apport-gtk-root for unix-process:6652:3047 [/lib/systemd/systemd --user] (> Feb 11 13:05:51 slate pkexec[264867]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Feb 11 13:05:51 slate pkexec[264867]: amurray: Executing command [USER=root] [TTY=unknown] [CWD=/home/amurray] [COMMAND=/usr/share/apport/apport-gtk] Feb 11 13:05:51 slate systemd[6652]: Starting Notification regarding a crash report... Feb 11 13:05:51 slate update-notifier-crash[265049]: /usr/bin/whoopsie Feb 11 13:05:51 slate systemd[6652]: update-notifier-crash.service: Succeeded. Feb 11 13:05:51 slate systemd[6652]: Started Notification regarding a crash report. Feb 11 13:05:57 slate systemd[6652]: Starting Notification regarding a crash report... Feb 11 13:05:57 slate update-notifier-crash[265340]: /usr/bin/whoopsie Feb 11 13:05:58 slate systemd[6652]: update-notifier-crash.service: Succeeded. Feb 11 13:05:58 slate systemd[6652]: Started Notification regarding a crash report. Feb 11 13:06:13 slate systemd[6652]: Starting Notification regarding a crash report... Feb 11 13:06:13 slate update-notifier-crash[265816]: /usr/bin/whoopsie Feb 11 13:06:14 slate systemd[6652]: update-notifier-crash.service: Succeeded. Feb 11 13:06:14 slate systemd[6652]: Started Notification regarding a crash report. Feb 11 13:06:17 slate whoopsie[5815]: [13:06:17] Parsing /var/crash/libdleyna-core-1.0-5.0.crash. Feb 11 13:06:17 slate systemd[6652]: Starting Notification regarding a crash report... Feb 11 13:06:17 slate whoopsie[5815]: [13:06:17] Uploading /var/crash/libdleyna-core-1.0-5.0.crash. Feb 11 13:06:17 slate update-notifier-crash[265873]: /usr/bin/whoopsie Feb 11 13:06:17 slate systemd[6652]: update-notifier-crash.service: Succeeded. Feb 11 13:06:17 slate systemd[6652]: Started Notification regarding a crash report. Feb 11 13:06:20 slate whoopsie[5815]: [13:06:20] Sent; server replied with: No error Feb 11 13:06:20 slate whoopsie[5815]: [13:06:20] Response code: 200 Feb 11 13:06:20 slate whoopsie[5815]: [13:06:20] Reported OOPS ID 4948a47e-4c77-11ea-a966-fa163e983629 Feb 11 13:06:20 slate systemd[6652]: Starting Notification regarding a crash report... Feb 11 13:06:20 slate update-notifier-crash[265936]: /usr/bin/whoopsie Feb 11 13:06:20 slate systemd[6652]: update-notifier-crash.service: Succeeded. Feb 11 13:06:20 slate systemd[6652]: Started Notification regarding a crash report. Feb 11 13:06:24 slate sudo[266010]: root : TTY=unknown ; PWD=/root ; USER=amurray ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; COMMAND=/usr/bin/xdg-open https://bugs.launchpad.net/ubuntu/+source/dleyna-core/+filebug/4bc4c494-4c77-11ea-b34a-00> Feb 11 13:06:24 slate sudo[266010]: pam_unix(sudo:session): session opened for user amurray by (uid=0) Feb 11 13:06:28 slate dbus-daemon[6678]: [session uid=1000 pid=6678] Activating service name='org.gnome.gedit' requested by ':1.258' (uid=1000 pid=266018 comm="gio open https://bugs.launchpad.net/ubuntu/+source; label="unconfined") Feb 11 13:06:28 slate dbus-daemon[6678]: [session uid=1000 pid=6678] Successfully activated service 'org.gnome.gedit' Feb 11 13:06:31 slate gedit[266061]: can't init metadata tree /home/amurray/.local/share/gvfs-metadata/http:uri=https%3A%2F%2Fbugs.launchpad.net%2Fubuntu%2F+source%2Fdleyna-core%2F+filebug%2F4bc4c494-4c77-11ea-b34a-002481e7f48a%3Ffield.title%3Dpackage+libdleyna-c> Feb 11 13:06:31 slate sudo[266010]: pam_unix(sudo:session): session closed for user amurray -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1862717 Title: Automatic crash report bug reports opened in gedit rather than the browser Status in apport package in Ubuntu: New Bug description: If a crash report is triggered automatically (say from a program crash etc) then the Apport UI pops up asking whether to report this - if I choose to proceed, after about 30 seconds gedit pops up with a HTML document showing 'OpenID transaction in progress' - which is the login.launchpad.net openid page. Looking at the gedit document title this shows the URL which should have got loaded by firefox - and so it appears that gedit has been spawned instead of firefox to handle the xdg-open call to report the bug. From
[Touch-packages] [Bug 1862717] [NEW] Automatic crash report bug reports opened in gedit rather than the browser
Public bug reported: If a crash report is triggered automatically (say from a program crash etc) then the Apport UI pops up asking whether to report this - if I choose to proceed, after about 30 seconds gedit pops up with a HTML document showing 'OpenID transaction in progress' - which is the login.launchpad.net openid page. Looking at the gedit document title this shows the URL which should have got loaded by firefox - and so it appears that gedit has been spawned instead of firefox to handle the xdg-open call to report the bug. >From journalctl I can see that it is root spawning this xdg-open call: Feb 11 13:06:24 slate sudo[266010]: root : TTY=unknown ; PWD=/root ; USER=amurray ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; COMMAND=/usr/bin/xdg-open https://bugs.launchpad.net/ubuntu/+source /dleyna-core/+filebug/4bc4c494-4c77-11ea-b34a- 002481e7f48a?field.title=package+libdleyna- core-1.0-5+%28not+installed%29+failed+to+install%2Fupgrade%3A+trying+to+overwrite+%27%2Fusr%2Flib%2Fx86_64 -linux-gnu%2Flibdleyna-core-1.0.so.5.0.0%27%2C+which+is+also+in+package +libdleyna-core-1.0-3%3Aamd64+0.6.0-1 And so I wonder if it is something to do with root's configuration for preferred applications (or not...) This does not occur when running ubuntu-bug from a terminal (since I assume in this case, the xdg-open call ends up coming from the users' own session). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 13:34:42 2020 InstallationDate: Installed on 2019-11-18 (84 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-22 (19 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "gedit with the crash report" https://bugs.launchpad.net/bugs/1862717/+attachment/5327200/+files/Screenshot%20from%202020-02-11%2013-42-40.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1862717 Title: Automatic crash report bug reports opened in gedit rather than the browser Status in apport package in Ubuntu: New Bug description: If a crash report is triggered automatically (say from a program crash etc) then the Apport UI pops up asking whether to report this - if I choose to proceed, after about 30 seconds gedit pops up with a HTML document showing 'OpenID transaction in progress' - which is the login.launchpad.net openid page. Looking at the gedit document title this shows the URL which should have got loaded by firefox - and so it appears that gedit has been spawned instead of firefox to handle the xdg-open call to report the bug. From journalctl I can see that it is root spawning this xdg-open call: Feb 11 13:06:24 slate sudo[266010]: root : TTY=unknown ; PWD=/root ; USER=amurray ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; COMMAND=/usr/bin/xdg-open https://bugs.launchpad.net/ubuntu/+source /dleyna-core/+filebug/4bc4c494-4c77-11ea-b34a- 002481e7f48a?field.title=package+libdleyna- core-1.0-5+%28not+installed%29+failed+to+install%2Fupgrade%3A+trying+to+overwrite+%27%2Fusr%2Flib%2Fx86_64 -linux-gnu%2Flibdleyna- core-1.0.so.5.0.0%27%2C+which+is+also+in+package+libdleyna- core-1.0-3%3Aamd64+0.6.0-1 And so I wonder if it is something to do with root's configuration for preferred applications (or not...) This does not occur when running ubuntu-bug from a terminal (since I assume in this case, the xdg-open call ends up coming from the users' own session). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 13:34:42 2020 InstallationDate: Installed on 2019-11-18 (84 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-22 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1862717/+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 1862671] Re: Internal mic/audio doesn't work in Asus with Ubuntu 18.04 kernel 5.3. It works only when downgrading the kernel to kernel version 4.20
** Summary changed: - Internel mic/audio doesn't work in Asus with Ubuntu 18.04. It works only when downgrading the kernel to kernel version 4.20 + Internal mic/audio doesn't work in Asus with Ubuntu 18.04 kernel 5.3. It works only when downgrading the kernel to kernel version 4.20 ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Tags added: regression-release -- 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/1862671 Title: Internal mic/audio doesn't work in Asus with Ubuntu 18.04 kernel 5.3. It works only when downgrading the kernel to kernel version 4.20 Status in linux package in Ubuntu: New Bug description: Internel mic/audio doesn't work in Asus with Ubuntu 18.04. It works only when downgrading the kernel to version 4.20 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1454 F pulseaudio /dev/snd/pcmC0D0c: scott 1454 F...m pulseaudio Date: Mon Feb 10 12:10:52 2020 InstallationDate: Installed on 2020-01-30 (11 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LD_LIBRARY_PATH= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862671/+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 1862665] Re: Mimics failure to connect to internet
*** This bug is a duplicate of bug 1858280 *** https://bugs.launchpad.net/bugs/1858280 ** This bug has been marked a duplicate of bug 1858280 Firefox reports "cannot connect to internet" message -- 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/1862665 Title: Mimics failure to connect to internet Status in xorg package in Ubuntu: New Bug description: Random start-up on opening of Firefox browser, shows up as failure to connect. Run diagnose program and debug reporting. Upon reboot sometimes clears up sometimes notRandom disconnect and failure to connect to internet. Need a debug program. Any recommendations?? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Feb 10 11:31:52 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1286 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (412 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862665/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
The second port on the NIC definitely works as the active interface in an active-backup bonding configuration on the other NICs. At the moment, it's only this particular NIC that is seeing this problem that we know of. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the
[Touch-packages] [Bug 1655189] Re: Cannot record videos into Theora
** Changed in: libtheora (Ubuntu) Status: Triaged => Won't Fix ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtheora in Ubuntu. https://bugs.launchpad.net/bugs/1655189 Title: Cannot record videos into Theora Status in guvcview: Confirmed Status in recordmydesktop: Confirmed Status in theora: Unknown Status in X.Org X server: New Status in libtheora package in Ubuntu: Won't Fix Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: HOW TO REPRODUCE: - Record a video using the Theora codec. RESULT: - In the recording the image is frozen or broken. RELEVANT DETAILS: - Doesn't matter which application you use to record or play the video. - I'm attaching samples from various programs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libtheora0 1.1.1+dfsg.1-8 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 10 01:17:54 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 libogg0 1.3.2-1 multiarch-support 2.23-0ubuntu5 InstallationDate: Installed on 2013-01-25 (1445 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: libtheora UpgradeStatus: Upgraded to xenial on 2016-08-05 (157 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/guvcview/+bug/1655189/+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 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Tags added: gke -- 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/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
** Changed in: apport (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Eoan) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: In Progress Status in apport source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. [Fix] Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . SRU merge proposals in: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 [Test Case] 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: $ apport-cli --save saved.apport linux-oem-osp1 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. [Regression Potential] Low. original bug description When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
** Changed in: apport (Ubuntu Disco) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: In Progress Status in apport source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. [Fix] Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . SRU merge proposals in: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 [Test Case] 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: $ apport-cli --save saved.apport linux-oem-osp1 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. [Regression Potential] Low. original bug description When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1812574] Re: .sudo_as_admin_successful file does not follow standard directory conventions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1812574 Title: .sudo_as_admin_successful file does not follow standard directory conventions Status in sudo package in Ubuntu: Confirmed Bug description: It would be great if this module followed the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec /basedir-spec-latest.html). Instead of placing the file `.sudo_as_admin_successful` in the home directory it should be placed in the OS specific appropriate directory. This, among other things, allows a user to specify a directory in which they want all applications to look for their user configurable setting files and keep their home directory clean. Sidenote: I was first confused about this file and a quick search got me top results with confused people too, it might be even better to remove this file altogether. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1812574/+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 1856045] Re: capabilities set with setcap are not honoured
Talking about this more, the Ubuntu solution for this sort of thing is to configure sudo appropriately, so we'll close the bug here. ** Changed in: iproute2 (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1856045 Title: capabilities set with setcap are not honoured Status in iproute2 package in Ubuntu: Won't Fix Status in iproute2 source package in Eoan: Confirmed Bug description: Hi, In Ubuntu 19.10 I set capabilities as; setcap cap_net_admin,cap_sys_admin+ep /bin/ip getcap /bin/ip /bin/ip = cap_net_admin,cap_sys_admin+ep but; > ip addr add 20.20.20.20/32 dev lo RTNETLINK answers: Operation not permitted *exactly* the same works perfect on 18.04.3 LTS. BTW the set of a silly address on "lo" is just an example. Nothing works on Ubuntu 19.10 Regards, ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libcap2-bin 1:2.25-2 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 Date: Wed Dec 11 15:27:00 2019 InstallationDate: Installed on 2019-12-09 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libcap2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1856045/+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 1834875] Re: cloud-init growpart race with udev
** Merge proposal linked: https://code.launchpad.net/~raharper/ubuntu/+source/cloud-utils/+git/cloud-utils/+merge/378839 -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1860432] Re: juju agent fails to start on focal
** Tags added: rls-ff-notfixing -- 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/1860432 Title: juju agent fails to start on focal Status in juju: Fix Committed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: during bootstrap, add-machine, deploy Juju fails on Focal due to systemd not finding the service. ll /etc/systemd/system jujud-machine-1.service -> /lib/systemd/system/jujud-machine-1/jujud-machine-1.service which is linked and calls ExecStart=/lib/systemd/system/jujud-machine-1/exec-start.sh The fact that it's in a jujud-machine-1 folder vs /system itself appears to be causing systemd to not be able to run it. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1860432/+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 1859858] Re: udev has truncated ID_SERIAL value for scsi disk
** Changed in: systemd (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1859858 Title: udev has truncated ID_SERIAL value for scsi disk Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Bug description: 1. root@ubuntu:/home/ubuntu# cat /etc/cloud/build.info build_name: server serial: 20200106 root@ubuntu:/home/ubuntu# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 2. root@ubuntu:/home/ubuntu# apt-cache policy systemd systemd: Installed: 244-3ubuntu1 Candidate: 244-3ubuntu1 Version table: *** 244-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. ID_SERIAL value should be 322dc58dc023c7008 4. ID_SERIAL value is 3 -- Launching a qemu VM with the same extra scsi disk like so: -drive file=extra_disk_1.img,id=drv4,if=none,format=raw,index=4,cache=unsafe \ -device scsi-hd,drive=drv4,serial=0x22dc58dc023c7008,wwn=0x22dc58dc023c7008 On Focal udevadm info output: root@ubuntu:/home/ubuntu# udevadm info --query=property /dev/sdc DEVPATH=/devices/pci:00/:00:03.0/virtio0/host2/target2:0:2/2:0:2:0/block/sdc DEVNAME=/dev/sdc DEVTYPE=disk MAJOR=8 MINOR=32 SUBSYSTEM=block USEC_INITIALIZED=1497555 SCSI_TPGS=0 SCSI_TYPE=disk SCSI_VENDOR=QEMU SCSI_VENDOR_ENC=QEMU\x20\x20\x20\x20 SCSI_MODEL=QEMU_HARDDISK SCSI_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 SCSI_REVISION=2.5+ ID_SCSI=1 ID_SCSI_INQUIRY=1 ID_VENDOR=QEMU ID_VENDOR_ENC=QEMU\x20\x20\x20\x20 ID_MODEL=QEMU_HARDDISK ID_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 ID_REVISION=2.5+ ID_TYPE=disk SCSI_IDENT_SERIAL=0x22dc58dc023c7008 SCSI_IDENT_LUN_VENDOR=0x22dc58dc023c7008 SCSI_IDENT_LUN_NAA_EXT=22dc58dc023c7008 ID_WWN=0x22dc58dc023c7008 ID_WWN_WITH_EXTENSION=0x22dc58dc023c7008 ID_BUS=scsi ID_SERIAL=3 ID_SERIAL_SHORT=22dc58dc023c7008 MPATH_SBIN_PATH=/sbin DM_MULTIPATH_DEVICE_PATH=0 ID_PATH=pci-:00:03.0-scsi-0:0:2:0 ID_PATH_TAG=pci-_00_03_0-scsi-0_0_2_0 ID_FS_UUID=b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 ID_FS_UUID_ENC=b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 ID_FS_UUID_SUB=e06d861c-c6e2-497c-b14f-265ae37060e2 ID_FS_UUID_SUB_ENC=e06d861c-c6e2-497c-b14f-265ae37060e2 ID_FS_TYPE=btrfs ID_FS_USAGE=filesystem ID_BTRFS_READY=1 DEVLINKS=/dev/disk/by-id/scsi-3 /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_0x22dc58dc023c7008 /dev/disk/by-path/pci-:00:03.0-scsi-0:0:2:0 /dev/disk/by-id/wwn-0x22dc58dc023c7008 /dev/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_0x22dc58dc023c7008 /dev/disk/by-uuid/b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 /dev/disk/by-id/scsi-322dc58dc023c7008 TAGS=:systemd: On Bionic: root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20200112 root@ubuntu:~# lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 root@ubuntu:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@ubuntu:~# udevadm info --query=property /dev/sdc DEVLINKS=/dev/disk/by-uuid/13a8a15f-4f6b-4904-b307-339b825c445b /dev/disk/by-path/pci-:00:03.0-scsi-0:0:2:0 /dev/disk/by-id/wwn-0x22dc58dc023c7008 /dev/disk/by-id/scsi-322dc58dc023c7008 DEVNAME=/dev/sdc DEVPATH=/devices/pci:00/:00:03.0/virtio0/host2/target2:0:2/2:0:2:0/block/sdc DEVTYPE=disk ID_BTRFS_READY=1 ID_BUS=scsi ID_FS_TYPE=btrfs ID_FS_USAGE=filesystem ID_FS_UUID=13a8a15f-4f6b-4904-b307-339b825c445b ID_FS_UUID_ENC=13a8a15f-4f6b-4904-b307-339b825c445b ID_FS_UUID_SUB=81178585-f7c0-429a-b02d-aeb2f245342c ID_FS_UUID_SUB_ENC=81178585-f7c0-429a-b02d-aeb2f245342c ID_MODEL=QEMU_HARDDISK ID_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 ID_PATH=pci-:00:03.0-scsi-0:0:2:0 ID_PATH_TAG=pci-_00_03_0-scsi-0_0_2_0 ID_REVISION=2.5+ ID_SCSI=1 ID_SCSI_SERIAL=0x22dc58dc023c7008 ID_SERIAL=322dc58dc023c7008 ID_SERIAL_SHORT=22dc58dc023c7008 ID_TYPE=disk ID_VENDOR=QEMU ID_VENDOR_ENC=QEMU\x20\x20\x20\x20 ID_WWN=0x22dc58dc023c7008 ID_WWN_WITH_EXTENSION=0x22dc58dc023c7008 MAJOR=8 MINOR=32 SUBSYSTEM=block TAGS=:systemd: USEC_INITIALIZED=2069797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 244-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 NonfreeKernelModules: zfs
[Touch-packages] [Bug 1862671] [NEW] Internel mic/audio doesn't work in Asus with Ubuntu 18.04. It works only when downgrading the kernel to kernel version 4.20
Public bug reported: Internel mic/audio doesn't work in Asus with Ubuntu 18.04. It works only when downgrading the kernel to version 4.20 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1454 F pulseaudio /dev/snd/pcmC0D0c: scott 1454 F...m pulseaudio Date: Mon Feb 10 12:10:52 2020 InstallationDate: Installed on 2020-01-30 (11 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LD_LIBRARY_PATH= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1862671 Title: Internel mic/audio doesn't work in Asus with Ubuntu 18.04. It works only when downgrading the kernel to kernel version 4.20 Status in pulseaudio package in Ubuntu: New Bug description: Internel mic/audio doesn't work in Asus with Ubuntu 18.04. It works only when downgrading the kernel to version 4.20 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1454 F pulseaudio /dev/snd/pcmC0D0c: scott 1454 F...m pulseaudio Date: Mon Feb 10 12:10:52 2020 InstallationDate: Installed on 2020-01-30 (11 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LD_LIBRARY_PATH= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1862671/+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 1862665] [NEW] Mimics failure to connect to internet
Public bug reported: Random start-up on opening of Firefox browser, shows up as failure to connect. Run diagnose program and debug reporting. Upon reboot sometimes clears up sometimes notRandom disconnect and failure to connect to internet. Need a debug program. Any recommendations?? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Feb 10 11:31:52 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1286 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (412 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1862665 Title: Mimics failure to connect to internet Status in xorg package in Ubuntu: New Bug description: Random start-up on opening of Firefox browser, shows up as failure to connect. Run diagnose program and debug reporting. Upon reboot sometimes clears up sometimes notRandom disconnect and failure to connect to internet. Need a debug program. Any recommendations?? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Feb 10 11:31:52 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1286 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (412 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc.
[Touch-packages] [Bug 1862667] [NEW] systemd autopkgtest 'boot-and-services' fails with linux-kvm
Public bug reported: [impact] systemd autopkgtest 'boot-and-services' fails when running with linux- kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so the test detects failed services. [test case] check the autopkgtest results, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service multipathd.service --- -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 UTC. -- Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath Device Controller... Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_rdac not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module dm-multipath not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest multipathd[195]: start up Feb 10 13:56:07 autopkgtest multipathd[195]: read /etc/multipath.conf Feb 10 13:56:07 autopkgtest multipathd[195]: DM multipath kernel driver not loaded Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Main process exited, code=exited, status=1/FAILURE Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Failed with result 'exit-code'. Feb 10 13:56:07 autopkgtest systemd[1]: Failed to start Device-Mapper Multipath Device Controller. FAIL == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['multipathd.service loaded failed failed [38 chars]ler'] != [] First list contains 1 additional elements. First extra element 0: 'multipathd.service loaded failed failed Device-Mapper Multipath Device Controller' + [] - ['multipathd.service loaded failed failed Device-Mapper Multipath Device ' - 'Controller'] [regression potential] TBD [scope] This is needed at least in Eoan, and probably Focal. This doesn't fail on Bionic or Xenial, but that seems to be because the multipath-utils package (which provides multipathd.service) is not installed during the test for those releases. [other info] ** Affects: systemd (Ubuntu) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Eoan) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Focal) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862667 Title: systemd autopkgtest 'boot-and-services' fails with linux-kvm Status in systemd package in Ubuntu: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] systemd autopkgtest 'boot-and-services' fails when running with linux- kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so the test detects failed services. [test case] check the autopkgtest results, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service multipathd.service --- -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 UTC. -- Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath Device Controller... Feb
[Touch-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
I think it's an systemd issue, which is already reported on GitHub but not fixed yet: https://github.com/systemd/systemd/issues/6077 ** Bug watch added: github.com/systemd/systemd/issues #6077 https://github.com/systemd/systemd/issues/6077 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: New Status in GNOME Terminal: Confirmed Status in Nautilus: Confirmed Status in dbus package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Bug description: In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+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 1862657] [NEW] systemd autopkgtest 'logind' fails when running with linux-kvm
Public bug reported: [impact] the logind autopkgtest tries to access /sys/power/state, but because linux-kvm has CONFIG_PM unset, there is no /sys/power/state file [test case] check autopkgtest, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz autopkgtest [13:48:53]: test logind: ---] autopkgtest [13:48:53]: test logind: - - - - - - - - - - results - - - - - - - - - - logind FAIL stderr: grep: /sys/power/state: No such file or directory autopkgtest [13:48:53]: test logind: - - - - - - - - - - stderr - - - - - - - - - - grep: /sys/power/state: No such file or directory [regression potential] regressions would likely involve incorrectly skipped logind test. [scope] this fails for all releases; Xenial, Bionic, Eoan, and Focal. [other info] it's unclear if linux-kvm should have CONFIG_PM (and other config) enabled or not. However, it's not the intention of systemd's autopkgtests to look for missing config in the kernel; the test already skips if 'mem' isn't in /sys/power/state, so it should also skip if /sys/power/state isn't present at all. ** Affects: systemd (Ubuntu) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Xenial) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Bionic) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Eoan) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Focal) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862657 Title: systemd autopkgtest 'logind' fails when running with linux-kvm Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] the logind autopkgtest tries to access /sys/power/state, but because linux-kvm has CONFIG_PM unset, there is no /sys/power/state file [test case] check autopkgtest, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz autopkgtest [13:48:53]: test logind: ---] autopkgtest [13:48:53]: test logind: - - - - - - - - - - results - - - - - - - - - - logind FAIL stderr: grep: /sys/power/state: No such file or directory autopkgtest [13:48:53]: test logind: - - - - - - - - - - stderr - - - - - - - - - - grep: /sys/power/state: No such file or directory [regression potential] regressions would likely involve incorrectly skipped logind test. [scope] this fails for all releases; Xenial, Bionic, Eoan, and Focal. [other info] it's unclear if linux-kvm should have CONFIG_PM (and other config) enabled or not. However, it's not the intention of systemd's autopkgtests to look for missing config in the kernel; the test already skips if 'mem' isn't in /sys/power/state, so it should also skip if /sys/power/state isn't present at all. To manage notifications about this bug go to:
[Touch-packages] [Bug 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module
'storage' autopkgtest now passes (is skipped) when testing with linux-kvm: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20200210_151352_6b64a@/log.gz ** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan ** Tags added: verification-done verification-done-bionic verification-done-eoan -- 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/1847816 Title: storage autopkgtest always fails with linux-{kvm,azure,etc} kernels that don't include scsi_debug module Status in autopkgtest-cloud: New Status in linux-kvm package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in linux-kvm source package in Xenial: New Status in systemd source package in Xenial: In Progress Status in linux-kvm source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in linux-kvm source package in Disco: New Status in systemd source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: New Status in systemd source package in Eoan: Fix Committed Status in linux-kvm source package in Focal: New Status in systemd source package in Focal: Fix Released Bug description: Note: this bug touches on multiple packages: - autopkgtest-cloud: merge request open to install 'modules-extra' package - systemd: update autopkgtest to skip test if scsi_debug module isn't available (SRU template below is for this change) - linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have scsi_debug module built for this kernel [SRU template for systemd] [impact] the 'storage' autopkgtest requires the 'scsi_debug' module, and if it can't load it (and it's not built-in), the test fails. On some custom kernels, this module is included in the new 'linux-modules-extra-*' deb which isn't installed by default, so the test always fails when doing a reverse-dep autopkgtest using such a kernel's meta pkg. Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG disabled entirely; for those kernels, it will never be possible to load the scsi_debug module and the test should be skipped. [test case] run the 'storage' autopkgtest with a custom kernel that doesn't provide the scsi_debug module in the standard linux-modules deb, or check the autopkgtest.u.c history, for example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz [regression potential] as this modifies one of the autopkgtest --setup-commands, a regression would most likely cause immediate test failure due to failing to install the proper linux-* debs. For the systemd 'storage' test change, this only skips the test if the scsi_debug module can't be loaded (and isn't already present, i.e. loaded or built-in). Any regression potential from that is low, but likely would involve incorrect test skips and/or missing valid problems due to skipping the test. [scope] systemd in all releases needs to have its 'storage' test updated To manage notifications about this bug go to: https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+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 1655189] Re: Cannot record videos into Theora
Since I'm no longer using Ubuntu, I'm unsubscribing from this report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtheora in Ubuntu. https://bugs.launchpad.net/bugs/1655189 Title: Cannot record videos into Theora Status in guvcview: Confirmed Status in recordmydesktop: Confirmed Status in theora: Unknown Status in X.Org X server: New Status in libtheora package in Ubuntu: Triaged Status in xserver-xorg-video-intel package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Record a video using the Theora codec. RESULT: - In the recording the image is frozen or broken. RELEVANT DETAILS: - Doesn't matter which application you use to record or play the video. - I'm attaching samples from various programs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libtheora0 1.1.1+dfsg.1-8 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 10 01:17:54 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 libogg0 1.3.2-1 multiarch-support 2.23-0ubuntu5 InstallationDate: Installed on 2013-01-25 (1445 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: libtheora UpgradeStatus: Upgraded to xenial on 2016-08-05 (157 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/guvcview/+bug/1655189/+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 1834875] Re: cloud-init growpart race with udev
Yes, this is my read on the issue as well. The trigger is related to the inotify watch that systemd-udevd puts on the disk. Something that might help that we could try per xnox's comment around use of flock. if growpart were to flock /dev/sda (we need to sort out what flags are needed to prevent udev probe and rule execution) prior to running sgdisk, and not release this flock until after partx runs (to inform the kernel of the update) and a udevadm settle (and possibly a trigger of a CHANGE event). This should prevent early reads of the modified but not update-to-date partition data in the kernel. Lastly, another area of exploration is: why isn't a change event emitted when partx runs to update the kernel with new partition data? If there is one, and the rules then generate the correct symlink; another approach for growpart is for it to block until the size of the new partition is correct. growpart calculates what the new size should be; so it could poll for this value thus blocking cloud-init's size check from running until growpart is confident that the kernel has updated the correct value (and the subsequent rules have completed execution)! -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Any changes to have this backported to 18.04 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
Hi! Re-tested with systemd=237-3ubuntu10.39 from proposed (and libsystemd0=237-3ubuntu10.39), and it works. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Won't Fix Bug description: [impact] if networkd is configured with a static address, and the address has already been assigned by dhcp (so that it has finite valid_lft), networkd will not change the valid_lft to 'forever' during startup, which leaves networkd thinking the address is static (meaning, networkd will not attempt to renew the dhcp lease) but the address valid_lft counting down. Once the valid_lft expires, the kernel will remove the address from the interface, breaking the system's networking. [test case] configure a system with networkd similar to: [Match] Name=ens3 [Network] DHCP=ipv4 restart systemd-networkd, and ens3 should get a DHCP address, e.g.: $ ip -4 a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 192.168.122.147/24 brd 192.168.122.255 scope global dynamic ens3 valid_lft 2295sec preferred_lft 2295sec then, edit the networkd config to use a static address, e.g.: [Match] Name=ens3 [Network] Address=192.168.122.147/24 Gateway=192.168.122.1 DNS=192.168.122.1 Domains=vm make sure to use the exact same address that was provided by dhcp. Then, without rebooting, just restart networkd and check the address lft: $ sudo systemctl restart systemd-networkd $ ip -4 a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 192.168.122.147/24 brd 192.168.122.255 scope global dynamic ens3 valid_lft 2992sec preferred_lft 2992sec the address should have 'forever' valid_lft, but it doesn't. [regression potential] this changes the details of how networkd updates static addresses during startup, so any regression would occur at networkd startup when using static addresses. [scope] this is needed only in Bionic and Disco. this is fixed by upstream: https://github.com/systemd/systemd/pull/11460/commits specifically commit a47a6daebe0af26c07d8d423225eb4add110793c which is included in Eoan and later. In Xenial using networkd, testing shows this problem does not occur, because this older version of networkd removes the 'foreign' dhcp address before re-assigning it as a static address. [other info] original description: --- In bionic, running systemd 237-3ubuntu10.22 and netplan.io 0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an interface with a static IPv4 address if the statically confiugred address is the same as the interface already has gotten from DHCP. This will cause the interface to loose its IP address when the DHCP lease exires, even though you've told netplan to configure it as static. I expect systemd-networkd to actually configure an IP address as static, regardless of what address the interface has before from DHCP. # lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.22 # apt-cache policy netplan.io netplan.io: Installed: 0.97-0ubuntu1~18.04.1 A paste of systemd-networkd's debug log when I run "netplan apply" and the interface already has the static IP configured from DHCP. It seems like upon a restart, systemd-networkd will allways add whatever IP config it had before the service stopped, and then apply changes (if any). Since my new config has the same IP as it already had, it does nothing even though the new config has static configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833193/+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 1862453] Re: static ip netplan does not apply on boot
root@lei:~# journalctl --no-pager -b -u systemd-networkd -- Logs begin at Fri 2019-12-27 20:01:52 EST, end at Mon 2020-02-10 09:30:11 EST. -- Feb 05 21:58:40 lei systemd[1]: Starting Network Service... Feb 05 21:58:40 lei systemd-networkd[926]: Failed to connect to bus: Permission denied Feb 05 21:58:40 lei systemd-networkd[926]: Could not connect to bus: Permission denied Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1. Feb 05 21:58:40 lei systemd[1]: Stopped Network Service. Feb 05 21:58:40 lei systemd[1]: Starting Network Service... Feb 05 21:58:40 lei systemd-networkd[927]: Failed to connect to bus: Permission denied Feb 05 21:58:40 lei systemd-networkd[927]: Could not connect to bus: Permission denied Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 2. Feb 05 21:58:40 lei systemd[1]: Stopped Network Service. Feb 05 21:58:40 lei systemd[1]: Starting Network Service... Feb 05 21:58:40 lei systemd-networkd[929]: Failed to connect to bus: Permission denied Feb 05 21:58:40 lei systemd-networkd[929]: Could not connect to bus: Permission denied Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 3. Feb 05 21:58:40 lei systemd[1]: Stopped Network Service. Feb 05 21:58:40 lei systemd[1]: Starting Network Service... Feb 05 21:58:40 lei systemd-networkd[930]: Failed to connect to bus: Permission denied Feb 05 21:58:40 lei systemd-networkd[930]: Could not connect to bus: Permission denied Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 4. Feb 05 21:58:40 lei systemd[1]: Stopped Network Service. Feb 05 21:58:40 lei systemd[1]: Starting Network Service... Feb 05 21:58:40 lei systemd-networkd[931]: Failed to connect to bus: Permission denied Feb 05 21:58:40 lei systemd-networkd[931]: Could not connect to bus: Permission denied Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5. Feb 05 21:58:40 lei systemd[1]: Stopped Network Service. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Start request repeated too quickly. Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service. Feb 05 22:00:07 lei systemd[1]: Starting Network Service... Feb 05 22:00:07 lei systemd-networkd[3106]: Enumeration completed Feb 05 22:00:07 lei systemd[1]: Started Network Service. Feb 05 22:00:07 lei systemd-networkd[3106]: lo: Link is not managed by us Feb 05 22:00:11 lei systemd-networkd[3106]: enp0s25: Gained carrier Feb 05 22:00:12 lei systemd-networkd[3106]: enp0s25: Gained IPv6LL Feb 05 22:00:12 lei systemd-networkd[3106]: enp0s25: Configured Feb 06 06:18:31 lei systemd[1]: Stopping Network Service... Feb 06 06:18:31 lei systemd[1]: Stopped Network Service. Feb 06 06:18:31 lei systemd[1]: Starting Network Service... Feb 06 06:18:31 lei systemd-networkd[6304]: enp0s25: Gained IPv6LL Feb 06 06:18:31 lei
[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
** Changed in: systemd (Ubuntu Eoan) 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/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? Application that require Name Resolution may fail while the service is being unnecessarily restarted [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart [Regression potential] The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it will run longer, so if there are memory leaks they will become more apparent. [other info] this fix was included in the initial release of systemd for eoan, but the fix required the additional change in bug 1849608. Both the original patch plus that change (to avoid using bash-specific &>) are included in the b/d patch for this bug. [Original bug report] If a cloud server is upgraded from Xenial to Bionic, the dhclient system remains in place and any DHCP lease refreshes cause a needless restart of the system-resolved daemon Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d) Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 10.226.209.105 Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors: Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 'srv-qvjhx'. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting resolvconf-pull-resolved.service... Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal in 1466 seconds. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started resolvconf-pull-resolved.service. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.25 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu Date: Mon Nov 26 16:17:52 2018 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+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 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298
Should have provided the links for reference: https://bugzilla.kernel.org/show_bug.cgi?id=203443 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645 Appears to work on 4.19.9 kernel when recompiled with patches: https://forum.manjaro.org/t/alc294-analog-audio-card-detected-but-no-sound-internaly-or-headphones/54089/29 ** Bug watch added: Linux Kernel Bug Tracker #203443 https://bugzilla.kernel.org/show_bug.cgi?id=203443 -- 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/1834566 Title: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Unable to get system speakers working running 19.04. At max volume, sound is barely perceptible through headphones. Pavucontrol shows sounds is present, but no amount of adjustments makes a difference. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 3355 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 28 00:44:13 2019 InstallationDate: Installed on 2019-06-05 (22 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AHK.029.190425.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP930MBE-K04US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: Notebook 9 Series dmi.product.name: 930MBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK dmi.product.version: P02AHK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU
** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan ** Tags added: verification-done verification-done-bionic verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd: Unknown Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Committed Status in cloud-init source package in Disco: New Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Won't Fix Status in cloud-init source package in Eoan: New Status in netplan.io source package in Eoan: Fix Released Status in systemd source package in Eoan: Fix Committed Status in cloud-init source package in Focal: Confirmed Status in netplan.io source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Bug description: = netplan.io = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Apply a netplan configuration that specifices ipv6-mtu: network: version: 2 ethernets: eth0: dhcp4: true dhcp6: true ipv6-mtu: 6000 * Check that MTU bytes, is at least IPv6MTUBytes on the interface: $ sysctl net.ipv6.conf.eth0.mtu net.ipv6.conf.eth0.mtu = 6000 [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of netplan.io = = systemd = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Use IPv6MTUBytes= setting in a .network unit * Restart systemd-network * Check that there no error messages / warnings about not-recognizing this option * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1671951/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1846232] Re: networkd pads interface MTU by 4 bytes for vlan even when told not to
** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- 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/1846232 Title: networkd pads interface MTU by 4 bytes for vlan even when told not to Status in curtin: Invalid Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: Fix Committed Bug description: [impact] vlan interface has wrong mtu, which may cause lost packets due to incorrect mtu [test case] configure a system using the netplan cfg similar to comment 2. alternately, networkd config can be used, similar to: ubuntu@lp1846232-e:/run/systemd/network$ grep . * 10-netplan-ens3.2667.netdev:[NetDev] 10-netplan-ens3.2667.netdev:Name=ens3.2667 10-netplan-ens3.2667.netdev:MTUBytes=1500 10-netplan-ens3.2667.netdev:Kind=vlan 10-netplan-ens3.2667.netdev:[VLAN] 10-netplan-ens3.2667.netdev:Id=2667 10-netplan-ens3.2667.network:[Match] 10-netplan-ens3.2667.network:Name=ens3.2667 10-netplan-ens3.2667.network:[Network] 10-netplan-ens3.2667.network:LinkLocalAddressing=ipv6 10-netplan-ens3.2667.network:Address=1.2.3.4/32 10-netplan-ens3.2667.network:ConfigureWithoutCarrier=yes 10-netplan-ens3.link:[Match] 10-netplan-ens3.link:OriginalName=ens3 10-netplan-ens3.link:[Link] 10-netplan-ens3.link:WakeOnLan=off 10-netplan-ens3.link:MTUBytes=1500 10-netplan-ens3.network:[Match] 10-netplan-ens3.network:Name=ens3 10-netplan-ens3.network:[Network] 10-netplan-ens3.network:LinkLocalAddressing=ipv6 10-netplan-ens3.network:VLAN=ens3.2667 The reboot and check the mtus: ubuntu@lp1846232-e:~$ ip l show ens3 2: ens3: mtu 1504 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:12:99:1b brd ff:ff:ff:ff:ff:ff ubuntu@lp1846232-e:~$ ip l show ens3.2667 3: ens3.2667@ens3: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:12:99:1b brd ff:ff:ff:ff:ff:ff The base interface should have a mtu of only 1500. [regression potential] As this corrects/adjusts the mtu of the interface, regressions would likely involve interface(s) being assigned incorrect mtu values, which then would lead to dropped packets and/or lowered network performance. [scope] this is needed only for Eoan. disco and earlier don't have the patch that introduces this problem, commit 4b151b71320bbee1549afcbad5554a40d90d63b4 focal already has the patches that fix this, commit f6fcc1c2a41eae749467de58453174296b635a69 (and the commit before it) see comment 4 for more details [other info] original description: --- From https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel- amd64/916/console: == FAIL: test_ip_output (vmtests.test_network_vlan.EoanTestNetworkVlan) -- Traceback (most recent call last): File "/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py", line 311, in test_ip_output routes) File "/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py", line 337, in check_interface int(ipcfg[key])) AssertionError: 1500 != 1504 >> begin captured stdout << - parsed ip_a dict: interface0: broadcast: 10.245.175.255 group: default inet4: - address: 10.245.168.16 prefixlen: '21' scope: global valid_lft: forever inet6: - address: fec0::d6be:d9ff:fea8:4913 prefixlen: '64' scope: site valid_lft: 86256sec - address: fe80::d6be:d9ff:fea8:4913 prefixlen: '64' scope: link valid_lft: forever interface: interface0 loopback: false lower_up: false mac_address: d4:be:d9:a8:49:13 mtu: '1500' multicast: false qdisc: fq_codel qlen: '1000' running: false state: UP up: false interface1: broadcast: 10.245.188.255 group: default inet4: - address: 10.245.188.2 prefixlen: '24' scope: global valid_lft: forever inet6: - address: fec0::d6be:d9ff:fea8:4915 prefixlen: '64' scope: site valid_lft: 86256sec - address: fe80::d6be:d9ff:fea8:4915 prefixlen: '64' scope: link valid_lft: forever interface: interface1 loopback: false lower_up: false mac_address: d4:be:d9:a8:49:15 mtu: '1504' multicast: false qdisc: fq_codel qlen: '1000' running:
[Touch-packages] [Bug 1655189] Re: Cannot record videos into Theora
** Changed in: xorg-server Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtheora in Ubuntu. https://bugs.launchpad.net/bugs/1655189 Title: Cannot record videos into Theora Status in guvcview: Confirmed Status in recordmydesktop: Confirmed Status in theora: Unknown Status in X.Org X server: New Status in libtheora package in Ubuntu: Triaged Status in xserver-xorg-video-intel package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Record a video using the Theora codec. RESULT: - In the recording the image is frozen or broken. RELEVANT DETAILS: - Doesn't matter which application you use to record or play the video. - I'm attaching samples from various programs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libtheora0 1.1.1+dfsg.1-8 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 10 01:17:54 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 libogg0 1.3.2-1 multiarch-support 2.23-0ubuntu5 InstallationDate: Installed on 2013-01-25 (1445 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: libtheora UpgradeStatus: Upgraded to xenial on 2016-08-05 (157 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/guvcview/+bug/1655189/+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 1858092] Re: Network Manager not saving OpenVPN password
Is there an estimation when this will go from proposed to release? I'm working around it by looking up the connections' UID in the Network- Manager configuration and manually adding the corresponding entries in KWallet as of now.. -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1862453] Re: static ip netplan does not apply on boot
Can you provide the output from $ journalctl --no-pager -b -u systemd-networkd ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862453 Title: static ip netplan does not apply on boot Status in systemd package in Ubuntu: Incomplete Bug description: I was advised to report a bug when I posted the following thread... https://askubuntu.com/questions/1208145/netplan-apply-required-after-reboot After a reboot, I must manually run "sudo netplan apply" to set the static IP described in 50-cloud-init.yaml. Journalctl repeatedly reports: Feb 04 20:10:52 lei systemd-networkd[935]: Failed to connect to bus: Permission denied during boot. Once booted, I can manually run "netplan apply" and everything configures normally. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.38 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Feb 8 08:54:00 2020 InstallationDate: Installed on 2019-12-28 (42 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=cb6893b3-aa11-452c-8b50-cf43b1ddaee3 ro maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97 Anniversary dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd03/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Anniversary:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862453/+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 1762391] Re: pam_group.so is not evaluated by gnome-terminal
Similarly for bionic using version 237-3ubuntu10.39 verification was also successsful: ubuntu@bionic:~$ groups ubuntu adm dialout cdrom sudo dip plugdev users lpadmin sambashare vboxsf ** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan ** Tags added: verification-done verification-done-bionic verification-done-eoan -- 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/1762391 Title: pam_group.so is not evaluated by gnome-terminal Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that processes were never getting group membership they were expected to get via pam_group module. [Test Case] * Add a /etc/security/group.conf entry, e.g. *;*;*;Al-2400;dialout,users * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus). Expected result: Logged in user is a member of 'dialout' and 'users' groups. Actual result: no group membership gained from pam_group. [Regression Potential] * It introduces a new PAM warning message in some scenarios (e.g. for systemd DynamicUser=1 units) for users that can't authenticate (pam_setcred fails in such case). * In certain systems user group membership may be extended by pam_group. [Other Info] Original bug description: We are using Ubuntu in a university network with lots of ldap users. To automatically map ldap users/groups to local groups we are using pam_group.so. This has worked for years. With the upgrade from Xenial to Bionic /etc/security/group.conf is not evaluated anymore by gnome-terminal as it runs as systemd --user. Xterm, ssh, su, and tty* however do work as expected. Only the default gnome-terminal behaves different. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this might not be a bug, but a feature. Nevertheless this behavior is very unexpected when upgrading from Xenial to Bionic and therefore should at least added to the changelog. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 13:17:52 2018 InstallationDate: Installed on 2018-03-29 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1762391/+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 1762391] Re: pam_group.so is not evaluated by gnome-terminal
I have repeated verification for eoan (242-7ubuntu3.7) with identical results. ubuntu@eoan:~$ groups ubuntu adm dialout cdrom sudo dip plugdev users lpadmin lxd sambashare -- 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/1762391 Title: pam_group.so is not evaluated by gnome-terminal Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that processes were never getting group membership they were expected to get via pam_group module. [Test Case] * Add a /etc/security/group.conf entry, e.g. *;*;*;Al-2400;dialout,users * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus). Expected result: Logged in user is a member of 'dialout' and 'users' groups. Actual result: no group membership gained from pam_group. [Regression Potential] * It introduces a new PAM warning message in some scenarios (e.g. for systemd DynamicUser=1 units) for users that can't authenticate (pam_setcred fails in such case). * In certain systems user group membership may be extended by pam_group. [Other Info] Original bug description: We are using Ubuntu in a university network with lots of ldap users. To automatically map ldap users/groups to local groups we are using pam_group.so. This has worked for years. With the upgrade from Xenial to Bionic /etc/security/group.conf is not evaluated anymore by gnome-terminal as it runs as systemd --user. Xterm, ssh, su, and tty* however do work as expected. Only the default gnome-terminal behaves different. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this might not be a bug, but a feature. Nevertheless this behavior is very unexpected when upgrading from Xenial to Bionic and therefore should at least added to the changelog. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 13:17:52 2018 InstallationDate: Installed on 2018-03-29 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1762391/+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 1661447] Re: Arbitrary code execution in centos template
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-18641 -- 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/1661447 Title: Arbitrary code execution in centos template Status in lxc package in Ubuntu: Fix Released Bug description: All the RPM's which get installed in an lxc-centos container are downloaded insecurely over http and then installed with yum --nogpgcheck. A man in the middle attacker, web proxy admin, or whoever can use this to install arbitrary code in to the container which will then get executed as root. The GPG keys should probably be shipped as part of the package where they are covered by the root of trust for the host distro. Or at the very least, https should be used to fetch the RPMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1661447/+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 1861063] Re: Dualshock4 controller doesn't stay connected
Official specs say about den 2nd generation, that the weight is 209-210 grams. https://en.wikipedia.org/wiki/DualShock The Internet is full of people having problem to pair these, but it worked with older kernels. -- 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/1861063 Title: Dualshock4 controller doesn't stay connected Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all. Once the pairing is completed, if I try to connect it it doesn't stay connected. I have checked the dmesg and apparently there is a buffer overflow somewhere. I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work. Dmesg output: [4.099796] Bluetooth: Core ver 2.22 [4.099833] Bluetooth: HCI device and connection manager initialized [4.099837] Bluetooth: HCI socket layer initialized [4.099839] Bluetooth: L2CAP socket layer initialized [4.099842] Bluetooth: SCO socket layer initialized [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018 [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.855413] Bluetooth: BNEP filters: protocol multicast [6.855416] Bluetooth: BNEP socket layer initialized [ 14.234706] Bluetooth: RFCOMM TTY layer initialized [ 14.234711] Bluetooth: RFCOMM socket layer initialized [ 14.234715] Bluetooth: RFCOMM ver 1.11 [ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow Release: Description: Ubuntu 19.10 Release: 19.10 Package Info: bluez: Installed: 5.50-0ubuntu4 Candidate: 5.50-0ubuntu4 Version table: *** 5.50-0ubuntu4 500 500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 14:11:19 2020 InstallationDate: Installed on 2019-11-26 (62 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FCS33A00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago) dmi.bios.date: 03/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET68W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCS33A00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCS33A00 dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:8289 acl:41 sco:0 events:268 errors:0 TX bytes:9494 acl:44 sco:0 commands:163 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+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
Re: [Touch-packages] [Bug 1862157] [NEW] dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles
asume following: / /data /data/tftp /data/tftp/grub /data/tftp/pxe tftp on some client: tftp-root unset: tftp grub/grub.0 -> file not found tftp /grub/grub.0 -> file not found tftp data/tftp/grub/grub.0 -> loads grub. tftp /data/tftp/grub/grub.0 -> loads grub. tftp-root=/data/tftp -- this prepends tftp-root to all paths given: tftp grub/grub.0 -> /data/tftp/grub/grub.0 -> loads grub. tftp /grub/grub.0 -> /data/tftp/grub/grub.0 -> loads grub tftp data/tftp/grub/grub.0 -> /data/tftp/data/tftp/grub/grub.0 -> file not found tftp /data/tftp/grub/grub.0 -> /data/tftp/data/tftp/grub/grub.0 -> file not found This way tftp in dnsmasq exposes what directory tftp-files reside. I'd awaited it to act if tftp-root is set as: tftp grub/grub.0 -> grub/grub.0 -> loads grub. tftp /grub/grub.0 -> grub/grub.0 -> loads grub tftp data/tftp/grub/grub.0 -> data/tftp/grub/grub.0 -> file not found tftp /data/tftp/grub/grub.0 -> /data/tftp/grub/grub.0 -> file not found Thus meaning tftp-root acts like chroot making tftp-clients see set tftp-root as root of the filesystem, not as forced path into a filesystem how dnsmasq handles tftp-root makes it difficult to have further software have correct paths to boot operating systems, because dnsmasq tftp handles back full paths which may be never available to nfs or smb based remote boots. On Fri, Feb 7, 2020 at 10:25 PM Simon Kelley wrote: > tftp-root is a security feature. The tftp protocol is entirely > unauthenticated, and if a request was allowed to go outside the > specified root directory, than that effectively makes all readable files > on the host available for internet-wide access, which is not generally > desirable. If you want TFTP to be able to access any file on the > machine, don't set a tftp-root. > > > Simon. > > > On 06/02/2020 11:02, Thomas Schweikle wrote: > > Public bug reported: > > > > dnsmasq does in all cases prepend "tftp_root" to tftp-files. > > > > tftp-root=/data/tftp > > dhcp-boot=grub/i386-pc/core.0 > > > > now have some config files for different subnets: > > dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1 > > dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1 > > dhcp-boot=net:172-18-7,/var/lib/tftpboot/pxelinux.0,spacewalk-ber.bfs.de > > > > Now booting clients within subnet 172.18.1.0/24 will boot grub with: > > /data/tftp/grub/i386-pc/core.0 > > > > Booting clients within subnet 172.18.2.0/24 will boot pxelinux.0 with: > > /data/tftp/pxelinux.0 > > > > And in subnet 172.18.7.0/24 clients will boot with: > > /data/tftp/var/lib/tftpboot/pxelinux.0 > > > > and return a "File not found" error. > > > > I'd expected: > > 172.18.1: grub/i386-pc/core.0 (file found within /data/tftp -- > without exposing path) > > 172.18.2: pxelinux.0(file found within /data/tftp -- > without exposing path) > > 172.18.3: /pxelinux.0 (file found within /) > > 172.18.7: /var/lib/tftpboot/pxelinux.0 (file found within > /var/lib/tftpboot/pxelinux.0) > > > > or even better: some way to set tftp-root for every subnet-config and > > having only relative paths to access files regardless of giving absolute > > or relative paths. > > > > ProblemType: Bug > > DistroRelease: Ubuntu 18.04 > > Package: dnsmasq 2.79-1 > > ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 > > Uname: Linux 4.15.0-87-generic x86_64 > > ApportVersion: 2.20.9-0ubuntu7.10 > > Architecture: amd64 > > Date: Thu Feb 6 11:43:07 2020 > > InstallationDate: Installed on 2014-01-31 (2197 days ago) > > InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release > amd64 (20131016) > > PackageArchitecture: all > > ProcEnviron: > > TERM=xterm > > PATH=(custom, no user) > > XDG_RUNTIME_DIR= > > LANG=de_DE.UTF-8 > > SHELL=/bin/bash > > SourcePackage: dnsmasq > > UpgradeStatus: Upgraded to bionic on 2018-11-23 (439 days ago) > > mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595 > > mtime.conffile..etc.dnsmasq.conf: 2016-08-17T12:18:41.225353 > > > > ** Affects: dnsmasq (Ubuntu) > > Importance: Undecided > > Status: New > > > > > > ** Tags: amd64 apport-bug bionic > > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1862157 > > Title: > dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1862157/+subscriptions > -- Thomas -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1862157 Title: dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles Status in dnsmasq package in Ubuntu: New Bug description: dnsmasq does in all cases prepend "tftp_root" to tftp-files. tftp-root=/data/tftp dhcp-boot=grub/i386-pc/core.0 now have some config files for different subnets:
[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers
** Changed in: shadow (Ubuntu Cosmic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1659534 Title: userdel doesn't supports extrausers Status in Snappy: Fix Released Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Released Status in shadow source package in Bionic: Fix Released Status in shadow source package in Cosmic: Won't Fix Bug description: TEST CASE: - run userdel --extrausers foo on a ubuntu core system REGRESSION POTENTIAL: - low, this option will only take effect when "userdel --extrauser" is used. On an Ubuntu Core system is impossible to delete an user from the extrausers db: root@localhost:/# userdel --extrausers alice userdel: unrecognized option '--extrausers' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+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