[Touch-packages] [Bug 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64
@jdstrand would you be willing to sponsor that for me to groovy and then I'll update this bug for SRU of this back to focal (and will add this change also for the existing libseccomp SRU for eoan/bionic/xenial in LP #1876055) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Confirmed Status in libseccomp source package in Focal: Confirmed Status in libseccomp source package in Groovy: Confirmed Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64
Tested on an up-to-date groovy install: amurray@sec-groovy-amd64:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 Codename: groovy amurray@sec-groovy-amd64:~$ dpkg -l seccomp Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--= ii seccomp2.4.3-1ubuntu1 amd64helper tools for high level interface to Linux seccomp filter amurray@sec-groovy-amd64:~$ scmp_sys_resolver -a aarch64 getrlimit -10180 amurray@sec-groovy-amd64:~$ scmp_sys_resolver -a aarch64 163 UNKNOWN amurray@sec-groovy-amd64:~$ sudo apt upgrade ... amurray@sec-groovy-amd64:~$ dpkg -l seccomp Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--= ii seccomp2.4.3-1ubuntu2 amd64helper tools for high level interface to Linux seccomp filter amurray@sec-groovy-amd64:~$ scmp_sys_resolver -a aarch64 163 getrlimit amurray@sec-groovy-amd64:~$ scmp_sys_resolver -a aarch64 getrlimit 163 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Confirmed Status in libseccomp source package in Focal: Confirmed Status in libseccomp source package in Groovy: Confirmed Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64
** Patch added: "libseccomp_2.4.3-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+attachment/5370131/+files/libseccomp_2.4.3-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Confirmed Status in libseccomp source package in Focal: Confirmed Status in libseccomp source package in Groovy: Confirmed Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64
See attached for a debdiff to fix this in groovy - this backports the PR mentioned above to add these missing syscalls for aarch64. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Confirmed Status in libseccomp source package in Focal: Confirmed Status in libseccomp source package in Groovy: Confirmed Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libseccomp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade Status in libseccomp package in Ubuntu: Confirmed Bug description: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+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 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
Yes you can make it faster again either in your mouse settings, or by completely removing the fix from: /usr/lib/udev/hwdb.d/70-mouse.hwdb and then run: sudo systemd-hwdb update and reboot. -- 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/1867421 Title: Microsoft Classic IntelliMouse moves way too fast Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] Microsoft Classic IntelliMouse moves way too fast to be usable. [test case] on a bionic system, connect affected mouse and attempt to move pointer, note it moves too fast. [regression potential] as this adds a hwdb entry for a mouse using vendor/product id and name matching, any regression would likely involve incorrectly setting dpi on a different mouse than intended. [scope] fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4 which is included starting in v240, so this is already fixed in Eoan and later. This is needed only for Xenial and Bionic. [original description] Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060531 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+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 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
I'm running Lubuntu 18.04.4 LTS and recently upgraded to a Microsoft Classic Intellimouse and find the current speed to be fine. Settings at present are the defaults (in Input Device Preferences, acceleration 2.0 and sensitivity 10). I received notification about this update today and am concerned I won't be able to change back to the current speed (cap will be put in place). Please confirm that this will be possible and if the update/changes will be easy to remove/reset later if not (steps for this would be useful). -- 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/1867421 Title: Microsoft Classic IntelliMouse moves way too fast Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] Microsoft Classic IntelliMouse moves way too fast to be usable. [test case] on a bionic system, connect affected mouse and attempt to move pointer, note it moves too fast. [regression potential] as this adds a hwdb entry for a mouse using vendor/product id and name matching, any regression would likely involve incorrectly setting dpi on a different mouse than intended. [scope] fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4 which is included starting in v240, so this is already fixed in Eoan and later. This is needed only for Xenial and Bionic. [original description] Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060531 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+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 1877536] Re: BlueZ 5.54 release
Same update, with a nicer changelog. ** Attachment added: "bluez_5.54-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877536/+attachment/5370123/+files/bluez_5.54-0ubuntu1.debian.tar.xz ** Attachment removed: "bluez_5.54-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877536/+attachment/5368222/+files/bluez_5.54-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1877536 Title: BlueZ 5.54 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.54 to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877536/+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 1878105] Re: Xorg 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) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1878105 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash is caused when visiting websites that attempt to customize the cursor layout. (Tested with Firefox 76.0 (64-bit)) The website on which the crash first occurred was the following: https://www.yellibeanz.com/ the crash is triggered after moving the cursor around. To test the hypothesis of the cursor causing the bug I also tested the following website with identical outcome: http://www.flockofsiegel.tv/ I am sure that one can find more examples here: https://onextrapixel.com/10-websites-that-replace-mouse-cursors-for-a -better-cause/ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 23:58:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:1fc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1fc0] InstallationDate: Installed on 2020-05-03 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X580GD_N580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=04dedfb2-c5a9-4447-af72-16999d76fce2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X580GD.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X580GD 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:
Re: [Touch-packages] [Bug 1231730] Re: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback problem
Dear Marcus, this was not, as it turned out, strictly a "bug" in Launchpad terms. In fact, as I and my Watcher Raymond discovered from inspired research by a guy whose name I have forgotten, it started life as a deliberate "System Restriction" approved and adopted in the minutes of Ubuntu's Central Committee. Although originally intended as an emergency remedy to cover the imminent release of the upcoming Ubuntu version, it remained in force over the next _half dozen or so_ releases. The story goes like so;- with HDMI becoming accepted it was intended to include suitable drivers in the next Ubuntu, but with the release deadline looming, it was recognised that the "Radeon" drivers for ATI video cards, were not fit to go. The sound sub-system of said drivers was seen to host a nest of insecticide resistant bugs keen to crash the entire system. The official solution was to go ahead with the release _with HDMI sound disabled_ but leaving the video. It effectively _became a bug_ when, possibly from embarrassment (?), all mention of this was omitted from the "Release Notes" of this, and following versions. There were two workarounds:- 1) select the appropriate proprietary ATI driver & install 2) follow instructions from Launchpad contributors, ignore the risk, and _simply re-enable audio._ I had fun with this at the time. Hope you find it of interest. Regards, Bob On 05/03/2020 13:14, Marcus Tomlinson wrote: > This release of Ubuntu is no longer receiving maintenance updates. If > this is still an issue on a maintained version of Ubuntu please let us > know. > > ** Changed in: alsa-driver (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1231730 Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: Invalid Bug description: I have 2 computers; 1) this with Asus M2A-VMHDMI motherboard, 2core AMD CPU and ATI HD 6000 series graphic card where I do not actually use the HDMI output ; 2) the second with Asus M4A 72 PRO motherboard, 4core Phenom and ATI HD 7000 (previously with the 6000 above), which does use the HDMI to connect to a Sharp brand TV. The symptom is the same:- i) turn computer on ii) select "system settings" iii) select "sound" iv) observe that I am presented with only 2 choices for sound "output" ---onboard analogue, or onboard digital; NO HDMI This same symptom occurs with every attempted upgrade from 12.04 Precise Pangolin, whether I upgrade online or from CD ; or erase the entire installation and re-install the later versions fresh from CD (which I often do when out of frustration I have been tempted to load proprietary ATI drivers ...resulting in little pop-ups with AMD kindly informing me that I am mounting "Unsupported Hardware" sic.) NOW:- When ASUS make half the Motherboards on the planet and ATI make half the Graphic cards, then WHY?? , if I choose on account of this prevalence to regard this as a rather general bug and and start writing this report is my computer already telling me that I have to go "unix-nerd" , and open a terminal, and install a program called "pavucontrol" which is a volume control for something called "Pulse Audio" and which as I eventually find instruction; will, if run with no options and no commands, tell me in an extremely frustrating fashion, that somewhere in it's interior it is running my desired HDMI at 100% volume !! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bob1848 F pulseaudio /dev/snd/controlC0: bob1848 F pulseaudio /dev/snd/pcmC0D0c: bob1848 F...m
[Touch-packages] [Bug 1878050] Re: Nvidia GT 240m gives problems
I can see three issues: 1. You're using Ubuntu 16.04. While that is supported, it is not well supported. Please consider trying Ubuntu 20.04 instead: https://ubuntu.com/download/desktop 2. The nvidia driver (when it is working) reports the screen is faulty: [19.136] (WW) NVIDIA(GPU-0): The EDID read for display device DFP-0 is invalid: the [19.136] (WW) NVIDIA(GPU-0): checksum for EDID version 1 is invalid. Please try to get a BIOS update from Acer to fix that. 3. The Nvidia driver is possibly not installed properly. Please uninstall it completely. Then if the system still doesn't work without it, reinstall it. ** Package changed: xorg (Ubuntu) => xorg-server (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/1878050 Title: Nvidia GT 240m gives problems Status in xorg-server package in Ubuntu: Incomplete Bug description: Can't install proprietary NVIDIA driver 340.107 X uses software rendering rather than hardware ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-178.208-generic 4.4.217 Uname: Linux 4.4.0-178-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon May 11 18:41:34 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-148-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-98-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0a34] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0688] InstallationDate: Installed on 2017-09-18 (965 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire Z5610 ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-178-generic root=UUID=398c17c4-3b3b-4a56-92f8-6f6a37b9eee1 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2010 dmi.bios.vendor: Phoenix dmi.bios.version: P01-B2L dmi.board.name: Aspire Z5610 dmi.board.vendor: Acer dmi.chassis.type: 13 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnPhoenix:bvrP01-B2L:bd01/19/2010:svnAcer:pnAspireZ5610:pvr:rvnAcer:rnAspireZ5610:rvr:cvnAcer:ct13:cvr: dmi.product.name: Aspire Z5610 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon May 11 18:16:46 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1878050/+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 1877932] Re: Bluetooth not connecting to last paired device when enabling bluetooth
** Package changed: pulseaudio (Ubuntu) => bluez (Ubuntu) ** Summary changed: - Bluetooth not connecting to last paired device when enabling bluetooth + Bluetooth not connecting to last paired device (Anker headset) when enabling bluetooth ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- 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/1877932 Title: Bluetooth not connecting to last paired device (Anker headset) when enabling bluetooth Status in bluez package in Ubuntu: New Bug description: I am using a Dell Lattitude E7470 laptop. I am trying to connect a Bluetooth headset (Anker). I am seeing this issue with the latest upgrade to the Ubuntu 20.04 LTS version. I have a Bluetooth headset which is paired with the machine. Given the Bluetooth is enabled in the Ubuntu machine and I switch on my Bluetooth headset, the ubuntu machine does not automatically connect to this device anymore. It used to do it very easily with 18.04,19.04 and 19.10 ubuntu version. I have to do a variety of steps to get it connected: * turn off and on the headset. * turn off and on the laptop bluetooth. * try manully connecting to the device from the setting menu multiple times. * Sometimes it detects and get connected automatically as it should. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 2220 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 19:42:46 2020 InstallationDate: Installed on 2019-02-21 (444 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to focal on 2020-04-27 (13 days ago) dmi.bios.date: 10/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.8 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.8:bd10/08/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877932/+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 1877871] Re: X windows hnags following upgrade from 18.04 to 20.04
Thanks for the bug report. The log in comment #2 shows lots of radeon kernel errors so I am moving this bug to the kernel. ** Tags added: radeon ** Summary changed: - X windows hnags following upgrade from 18.04 to 20.04 + [radeon] X windows hangs following upgrade from 18.04 to 20.04 ** Package changed: xorg (Ubuntu) => linux (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/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: New Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+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 1878128] [NEW] PCI/internal sound card not detected
Public bug reported: Sound mysteriously stopped working recently on my Dell XPS 9560 laptop. I only see Dummy Output and not my actual speakers. Rebooting didn't fix it, and sound continues to work in Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:24:09 2020 InstallationDate: Installed on 2020-02-14 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal -- 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/1878128 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Invalid Bug description: Sound mysteriously stopped working recently on my Dell XPS 9560 laptop. I only see Dummy Output and not my actual speakers. Rebooting didn't fix it, and sound continues to work in Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:24:09 2020 InstallationDate: Installed on 2020-02-14 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878128/+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 1878128] Re: PCI/internal sound card not detected
...ignore me. Start-Date: 2020-05-09 16:01:28 Commandline: apt install oss4-base Requested-By: logan (1000) Install: oss4-base:amd64 (4.2-build2010-5ubuntu5), libx86-1:amd64 (1.1+ds1-11, a utomatic), vbetool:amd64 (1.1-4, automatic), pm-utils:amd64 (1.4.1-19, automatic ), ethtool:amd64 (1:5.4-1, automatic) Remove: alsa-base:amd64 (1.0.25+dfsg-0ubuntu5), ubuntu-desktop-minimal:amd64 (1.450), linux-sound-base:amd64 (1.0.25+dfsg-0ubuntu5), ubuntu-desktop:amd64 (1.450) End-Date: 2020-05-09 16:01:33 ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- 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/1878128 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Invalid Bug description: Sound mysteriously stopped working recently on my Dell XPS 9560 laptop. I only see Dummy Output and not my actual speakers. Rebooting didn't fix it, and sound continues to work in Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:24:09 2020 InstallationDate: Installed on 2020-02-14 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878128/+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 1877822] Re: xorg (Ubuntu) bug reporting guidelines:
*** This bug is a duplicate of bug 1877821 *** https://bugs.launchpad.net/bugs/1877821 ** Information type changed from Private Security to Public ** This bug has been marked a duplicate of bug 1877821 xorg (Ubuntu) bug reporting guidelines: -- 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/1877822 Title: xorg (Ubuntu) bug reporting guidelines: Status in xorg package in Ubuntu: New Bug description: Please report bugs against xorg with this command: $ ubuntu-bug xorg For more tips on effective bug reporting against Ubuntu Xorg packages, please see http://wiki.ubuntu.com/X/Reporting and thanks ahead of time! Ubuntu bug reporting guidelines: Are you uncertain if your issue is really a bug? Then ask a support question about Ubuntu at http://answers.launchpad.net/ubuntu/ - these can be made into bugs later. Another support venue is http://askubuntu.com. If you are certain this is a bug please include the source package the bug is in. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage. We also need: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 10 06:15:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2020-05-05 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude 5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=55faf464-9082-49b3-9a16-cab619ffa5a9 ro dis_ucode_ldr quiet splash nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.5 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.5:bd12/26/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005091930.e622e0~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877822/+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 1877769] Re: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU
** Changed in: unattended-upgrades (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1877769 Title: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU Status in unattended-upgrades package in Ubuntu: In Progress Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] * Unattended-upgrades consumes excessive amount of CPU when rewinding cache trying to mark packages to upgrade or install even when they are already marked to be upgraded or installed. This can be triggered by packages held back. [Test Case] * Run test_rewind.py: -Fixed output: $ python3 test_rewind.py INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768) DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed . -- Ran 1 test in 0.022s OK - Not fixed output: $ python3 test_rewind.py INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768) DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed DEBUG:root:falling back to adjusting test-package's dependencies DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting test3-package's dependencies DEBUG:root:falling back to adjusting test-package's dependencies DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting test3-package's dependencies . -- Ran 1 test in 0.024s (Note the extra "DEBUG:root:falling back to adjusting" ... lines) [Regression Potential] * Minimal. The very small change fixes how call_checked() verifies that the package to be upgrades/installed is indeed marked to either being installed or upgraded. In the worst case, if call_checked() erroneously returns success for a package as a result of a regression, unattended-upgrades does not fall back to adjusting packages to make marking successful. Later unattended-upgrades finds out that the package could not be marked and should be treated as kept back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1877769/+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 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
Looking around some more, it seems it may be related to this: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974 I did add the suggested item to the /etc/gnutls and the account successfully is added to GOA now, but still isn't letting me download email due to a different error, but it does seem that it could be related to the TLS key length issue cited above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: After upgrading from 18.10 and/or on fresh install, a known-working Exchange email setup fails to sign in, giving "Error 7: Unexpected response from server". Tested the same settings and credentials on a new install of 18.10 and it worked. I have Evolution and Evolution-ews installed on all instances, working in 18.10, not in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:38:32 2019 InstallationDate: Installed on 2018-03-24 (391 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1825580/+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 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED
> - apart from feedback given by @mruffell, to also check if any of librcu consumers are depending on a full membarrier - driven by kernel - for ** shared pages among different processes ** I agree with @ddstreet, I don't think liburcu gives that sort of guarantee when it comes to cross process synchronisation. It was my belief that liburcu targets synchronisation across a set of threads within the current process only. Proof by contradiction. Assume that a program compiles against liburcu and uses it to synchronise access to shared memory pages for IPC between a sister process. If the program links against liburcu 0.9 or lower, the sys_membarrier syscall did not exist yet, and liburcu will use the default compiler based membarrier, which is only good within the current process. Synchronisation across shared memory pages fails. This is the case on Xenial, Trusty and the like. If the program links against liburcu 0.11 or newer, the sys_membarrier syscall does exist, but MEMBARRIER_CMD_SHARED is only used if the current running kernel does not support MEMBARRIER_CMD_PRIVATE_EXPEDITED. There is no toggle option in the API at all, so for users with a kernel 4.14 or higher, MEMBARRIER_CMD_PRIVATE_EXPEDITED will be used, and synchronisation across shared memory pages will fail. This is the case on Eoan, Focal, Groovy. If the program links against liburcu 0.10, and uses the -qsbr, -md and -signal variants, sys_membarrier is not used at all, and it falls back to the compiler based membarrier, which is only good within the current process. Synchronisation across shared memory pages will fail. If the program links against liburcu 0.10, and is used within a container, with a kernel version less than 4.3 that does not support sys_membarrier, such as a Bionic container on a Trusty 3.13 host, or on a 3.10 RHEL host, the sys_membarrier syscall fails, and it falls back to the compiler based membarrier. Synchronisation across shared memory pages will fail. Now, the upstream developers added MEMBARRIER_CMD_PRIVATE_EXPEDITED as the default in liburcu 0.11. They did not change the API to accommodate both MEMBARRIER_CMD_SHARED and MEMBARRIER_CMD_PRIVATE_EXPEDITED, and instead, if the kernel is greater than 4.14, MEMBARRIER_CMD_PRIVATE_EXPEDITED will be used. Upstream are well aware of their consumers, and they would not break everyone's usages out of the blue, without adding some sort of API provision for legacy users. Thus, our initial assumption that liburcu can be used to synchronise access to shared memory pages for IPC between a sister process is wrong, since no one will create a program that potentially only works in one specific environment, which is bionic on bare metal and liburcu 0.10 only. I'm not even sure how you would co-ordinate liburcu over multiple processes either. So, because of the above, I don't think any librcu consumers are depending on a full membarrier, driven by the kernel, for shared pages among different processes. I still think this is safe to SRU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liburcu in Ubuntu. https://bugs.launchpad.net/bugs/1876230 Title: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED Status in liburcu package in Ubuntu: Fix Released Status in liburcu source package in Bionic: In Progress Bug description: [Impact] In Linux 4.3, a new syscall was defined, called "membarrier". This systemcall was defined specifically for use in userspace-rcu (liburcu) to speed up the fast path / reader side of the library. The original implementation in Linux 4.3 only supported the MEMBARRIER_CMD_SHARED subcommand of the membarrier syscall. MEMBARRIER_CMD_SHARED executes a memory barrier on all threads from all processes running on the system. When it exits, the userspace thread which called it is guaranteed that all running threads share the same world view in regards to userspace addresses which are consumed by readers and writers. The problem with MEMBARRIER_CMD_SHARED is system calls made in this fashion can block, since it deploys a barrier across all threads in a system, and some other threads can be waiting on blocking operations, and take time to reach the barrier. In Linux 4.14, this was addressed by adding the MEMBARRIER_CMD_PRIVATE_EXPEDITED command to the membarrier syscall. It only targets threads which share the same mm as the thread calling the membarrier syscall, aka, threads in the current process, and not all threads / processes in the system. Calls to membarrier with the MEMBARRIER_CMD_PRIVATE_EXPEDITED command are guaranteed non-blocking, due to using inter-processor interrupts to implement memory barriers. Because of this, membarrier calls that use MEMBARRIER_CMD_PRIVATE_EXPEDITED are much faster than those that use MEMBARRIER_CMD_SHARED. Since Bionic uses a
[Touch-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
If it is a compositor bug as the Wayland library is suggesting then next please try uninstalling all non-Ubuntu gnome-shell extensions, and reboot. ** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: wayland (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) Status in gnome-terminal package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Since upgrading to 20.04 and switching to Wayland, Gnome terminal occasionally crashes. I interpret the corresponding logs to mean that it's actually Wayland that fails to do something in the background, which then takes down Gnome terminal: touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client. touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client communication (pid 11639) touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events from display: Katkennut putki touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Failed with result 'exit-code'. I have yet to nail down the precise circumstances, as this has (so far) been somewhat rare, having occurred perhaps once or twice a week. Since the log mentions pointer, I should perhaps mention that I've set `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome terminal also exhibits other misbehaviour wrt. to this, occasionally refusing to get focus, or alternatively losing the focus, despite mouse cursor being over the terminal window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xwayland 2:1.20.8-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 15:22:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed (WARNING! Diff between built and installed module!) xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2016-10-13 (1302 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
I have confirmed that the fix in -proposed fixes the issue for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The customer which is experiencing this issue cannot switch to VGA=qxl as a workaround, and must use VGA=std, hence I suggest we re-enable bochs-drm for Bionic. [Fix] I noticed on Focal, if you boot, the framebuffer is initially efifb: [ 0.603716] efifb: probing for efifb [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 0.603736] efifb: scrolling: redraw [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.604462] Console: switching to colour frame buffer device 100x37 [ 0.605829] fb0: EFI VGA frame buffer device This soon changes to bochs-drm about a second later: [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xc000 -> 0xc0ff [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1c8c000 -> 0xc1c8cfff [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100) [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA [ 0.939085] Console: switching to colour dummy device 80x25 [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5. [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB [ 0.942081] [TTM] Initializing pool allocator [ 0.942089] [TTM] Initializing DMA pool allocator [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [ 0.944019] [drm] Found EDID data blob. [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on minor 0 [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device [ 0.947712] Console: switching to colour frame buffer device 128x48 On bionic, the framebuffer never changes from efifb, since the bochs- drm kernel module is not built, and it is also present on the module banlist in /etc/modprobe.d/blacklist-framebuffer.conf bochs-drm needs to be enabled to be built in the kernel config, and removed from the module blacklist in kmod. [Testcase] Create a new QEMU/KVM virtual machine, I used virt-manager. Before you install the OS, check the box to modify settings before install. In the "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd". Set the video device to qxl while you install Bionic. Once the install is done, reboot, do a "apt update" and "apt upgrade", to ensure you have grub2 2.02-2ubuntu8.15 installed. Shut the VM down, and set the video device to VGA. Or VGA=std if you use the QEMU command line. Start the VM up, and the screen will be garbled. See attached picture. If you install my test packages, which are available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test Instructions to install (on a bionic system): 1) Enable bionic-proposed 2) sudo apt-get update 3) sudo apt install linux-image-unsigned-4.15.0-96-generic linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod 4) sudo reboot 5) uname -rv 4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 2020 If you reboot, the screen will be perfectly readable, since the bochs- drm driver will be in use. [Regression Potential] We are
[Touch-packages] [Bug 1878108] Re: new upstream release 2020a
** Description changed: There is a new upstream release of tzdata, 2020, which includes the following: - * New upstream release, affecting past and future timestamps: - - Morocco springs forward on 2020-05-31, not 2020-05-24. - - Canada's Yukon advanced to -07 year-round on 2020-03-08. - - America/Nuuk renamed from America/Godthab. + * New upstream release, affecting past and future timestamps: + - Morocco springs forward on 2020-05-31, not 2020-05-24. + - Canada's Yukon advanced to -07 year-round on 2020-03-08. + - America/Nuuk renamed from America/Godthab. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in - /usr/share/zoneinfo/). This is compared to the same output after the - updated package got installed. If those are different the verification - is considered done. + /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This + is compared to the same output after the updated package got installed. + If those are different the verification is considered done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1878108 Title: new upstream release 2020a Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: New Status in tzdata source package in Xenial: In Progress Status in tzdata source package in Bionic: In Progress Status in tzdata source package in Eoan: In Progress Status in tzdata source package in Focal: In Progress Bug description: There is a new upstream release of tzdata, 2020, which includes the following: * New upstream release, affecting past and future timestamps: - Morocco springs forward on 2020-05-31, not 2020-05-24. - Canada's Yukon advanced to -07 year-round on 2020-03-08. - America/Nuuk renamed from America/Godthab. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
Still seeing it on Ubuntu 20.04: Code 6: Unexpected response from server. We did upgrade the version of Exchange used at my work within the last year, but the odd part is setup and use works when I'm on the work network, but not when I work from home (where it used to in versions of Gnome prior, and in the Exchange version prior). Not sure if it is a server issue on my employer's side, a network configuration issue, or a Gnome issue, at this point. On Mon, May 11, 2020 at 6:01 AM Sebastien Bacher wrote: > could you try if that's still an issue in newer Ubuntu series? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1825580 > > Title: > Gnome Online Accounts fails to sign in Exchange emails > > Status in gnome-online-accounts: > New > Status in gnome-online-accounts package in Ubuntu: > Triaged > > Bug description: > After upgrading from 18.10 and/or on fresh install, a known-working > Exchange email setup fails to sign in, giving "Error 7: Unexpected > response from server". Tested the same settings and credentials on a > new install of 18.10 and it worked. > > I have Evolution and Evolution-ews installed on all instances, working > in 18.10, not in 19.04. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: gnome-online-accounts 3.32.0-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 > Uname: Linux 5.0.0-13-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Apr 19 16:38:32 2019 > InstallationDate: Installed on 2018-03-24 (391 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 > (20180208) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-online-accounts > UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/gnome-online-accounts/+bug/1825580/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: After upgrading from 18.10 and/or on fresh install, a known-working Exchange email setup fails to sign in, giving "Error 7: Unexpected response from server". Tested the same settings and credentials on a new install of 18.10 and it worked. I have Evolution and Evolution-ews installed on all instances, working in 18.10, not in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:38:32 2019 InstallationDate: Installed on 2018-03-24 (391 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1825580/+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 1878108] [NEW] new upstream release 2020a
Public bug reported: There is a new upstream release of tzdata, 2020, which includes the following: * New upstream release, affecting past and future timestamps: - Morocco springs forward on 2020-05-31, not 2020-05-24. - Canada's Yukon advanced to -07 year-round on 2020-03-08. - America/Nuuk renamed from America/Godthab. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). This is compared to the same output after the updated package got installed. If those are different the verification is considered done. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: tzdata (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: tzdata (Ubuntu Xenial) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Affects: tzdata (Ubuntu Bionic) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Affects: tzdata (Ubuntu Eoan) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Affects: tzdata (Ubuntu Focal) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: tzdata (Ubuntu) Status: New => Fix Released ** Changed in: tzdata (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Eoan) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Xenial) Status: New => In Progress ** Changed in: tzdata (Ubuntu Bionic) Status: New => In Progress ** Changed in: tzdata (Ubuntu Eoan) Status: New => In Progress ** Changed in: tzdata (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1878108 Title: new upstream release 2020a Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: New Status in tzdata source package in Xenial: In Progress Status in tzdata source package in Bionic: In Progress Status in tzdata source package in Eoan: In Progress Status in tzdata source package in Focal: In Progress Bug description: There is a new upstream release of tzdata, 2020, which includes the following: * New upstream release, affecting past and future timestamps: - Morocco springs forward on 2020-05-31, not 2020-05-24. - Canada's Yukon advanced to -07 year-round on 2020-03-08. - America/Nuuk renamed from America/Godthab. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1878108] Re: new upstream release 2020a
tzdata (2020a-0ubuntu1) groovy; urgency=medium * New upstream release, affecting past and future timestamps: - Morocco springs forward on 2020-05-31, not 2020-05-24. - Canada's Yukon advanced to -07 year-round on 2020-03-08. - America/Nuuk renamed from America/Godthab. -- Brian Murray Thu, 07 May 2020 14:04:46 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1878108 Title: new upstream release 2020a Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: New Status in tzdata source package in Xenial: In Progress Status in tzdata source package in Bionic: In Progress Status in tzdata source package in Eoan: In Progress Status in tzdata source package in Focal: In Progress Bug description: There is a new upstream release of tzdata, 2020, which includes the following: * New upstream release, affecting past and future timestamps: - Morocco springs forward on 2020-05-31, not 2020-05-24. - Canada's Yukon advanced to -07 year-round on 2020-03-08. - America/Nuuk renamed from America/Godthab. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1878105] [NEW] Xorg crash
Public bug reported: Crash is caused when visiting websites that attempt to customize the cursor layout. (Tested with Firefox 76.0 (64-bit)) The website on which the crash first occurred was the following: https://www.yellibeanz.com/ the crash is triggered after moving the cursor around. To test the hypothesis of the cursor causing the bug I also tested the following website with identical outcome: http://www.flockofsiegel.tv/ I am sure that one can find more examples here: https://onextrapixel.com/10-websites-that-replace-mouse-cursors-for-a -better-cause/ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 23:58:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:1fc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1fc0] InstallationDate: Installed on 2020-05-03 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X580GD_N580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=04dedfb2-c5a9-4447-af72-16999d76fce2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X580GD.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X580GD 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.:bvrX580GD.309:bd10/18/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX580GD_N580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X580GD_N580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal 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/1878105 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: Crash is caused when visiting websites that attempt to customize the cursor layout. (Tested with Firefox 76.0 (64-bit)) The website on which the crash first occurred was the
[Touch-packages] [Bug 1877821] Re: xorg (Ubuntu) bug reporting guidelines:
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877821 Title: xorg (Ubuntu) bug reporting guidelines: Status in xorg package in Ubuntu: New Bug description: Please report bugs against xorg with this command: $ ubuntu-bug xorg For more tips on effective bug reporting against Ubuntu Xorg packages, please see http://wiki.ubuntu.com/X/Reporting and thanks ahead of time! Ubuntu bug reporting guidelines: Are you uncertain if your issue is really a bug? Then ask a support question about Ubuntu at http://answers.launchpad.net/ubuntu/ - these can be made into bugs later. Another support venue is http://askubuntu.com. If you are certain this is a bug please include the source package the bug is in. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage. We also need: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 10 06:15:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2020-05-05 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude 5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=55faf464-9082-49b3-9a16-cab619ffa5a9 ro dis_ucode_ldr quiet splash nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.5 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.5:bd12/26/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005091930.e622e0~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877821/+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 1878059] Re: Audio device not reachable after wake up
there are some known nvidia/hdmi issue with the current kernel, reassigning ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878059 Title: Audio device not reachable after wake up Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878059/+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 1877746] Re: Lock screen not working
** Information type changed from Private Security to Public Security ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877746 Title: Lock screen not working Status in gnome-shell package in Ubuntu: New Bug description: The screen will not automatically lock on the specified timer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 08:54:58 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (678 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (11 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877746/+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 1878081] Re: dbus-launch of gnome-terminal slow on 20.04
thank you for your bug report, it looks like an issue with xdg-desktop- portal , could you try to temporarly uninstall it to see if workaround the issue? ** Package changed: dbus (Ubuntu) => xdg-desktop-portal (Ubuntu) ** Changed in: xdg-desktop-portal (Ubuntu) Importance: Undecided => Low -- 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/1878081 Title: dbus-launch of gnome-terminal slow on 20.04 Status in xdg-desktop-portal package in Ubuntu: New Bug description: Since upgrading to 20.04 I've seen a roughly 20 second delay between running 'dbus-launch gnome-terminal' and when the terminal actually opens. This happens 100% of the time and was basically instant on previous versions (I've tried on 18.04, 19.04, and 19.10). I've tried explicitly unlocking my keyring given the secret error message below and I've verified gnome-terminal-server and dbus-daemon are both running. If I run gnome-terminal without dbus-launch it activates instantly so there's something about the route through dbus that is causing an issue. I get the following output from the dbus-launch invocation: # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ # watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) # unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) # watch_established: "/org/appmenu/gtk-module/" (establishing: 0) # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ # watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) # unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) # watch_established: "/org/appmenu/gtk-module/" (establishing: 0) # Failed to use specified server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.87 was not provided by any .service files # Falling back to default server. # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) And I see the following in syslog during the launch (note the delay in timestamps): May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] AppArmor D-Bus mediation is enabled May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=1000 pid=6298 comm="/usr/bin/gnome-terminal.real " label="unconfined") May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.gtk.vfs.Daemon' May 11 09:15:57 rfairfax-ubh org.gtk.vfs.Daemon[6310]: fusermount: failed to access mountpoint /run/user/1000/gvfs: Permission denied May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.gnome.Terminal' requested by ':1.0' (uid=1000 pid=6298 comm="/usr/bin/gnome-terminal.real " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.gnome.Terminal' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.2' (uid=1000 pid=6313 comm="/usr/libexec/gnome-terminal-server " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.portal.Documents' requested by ':1.3' (uid=1000 pid=6319 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.4' (uid=1000 pid=6324 comm="/usr/libexec/xdg-document-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.freedesktop.portal.Documents' May 11 09:15:58 rfairfax-ubh systemd[1]: run-user-1000-doc.mount: Succeeded. May 11 09:15:58 rfairfax-ubh systemd[1108]: run-user-1000-doc.mount: Succeeded. May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.impl.portal.desktop.gtk' requested by ':1.3' (uid=1000 pid=6319 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='ca.desrt.dconf' requested by ':1.6' (uid=1000 pid=6345 comm="/usr/libexec/xdg-desktop-portal-gtk " label="unconfined") May 11
[Touch-packages] [Bug 1878091] Re: Non-fractional scaling not working
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1878091 Title: Non-fractional scaling not working Status in gnome-shell package in Ubuntu: New Bug description: My laptop has a 4K display. Default Resolution = 3840x2160, scale = 200%. If I set resolution to 1920x1080, everything on the desktop is scaled to double size. So, if I reduce the Scale setting from 200% to 100%, I would expect everything to look normal again, but it does not. 100% and 200% look identical. However, if I enable Fractional scaling and select 125%, that looks correct. So, Fractional scaling works correctly, but non-fractional scaling does not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 15:58:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2020-05-07 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20349 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=4f7e434e-f524-450c-8486-29302f1ca495 ro persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: K0J40709WIN dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: K0J40709WIN dmi.chassis.asset.tag: K0J40709WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvrK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 20349 dmi.product.sku: LENOVO_MT_20349_BU_idea_FM_Lenovo Y50-70 Touch dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878091/+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 1878094] Re: Ubuntu 20.04 / Pulseaudio RTP receive broken sound
Thank you for your bug report, that's likely an upstream issue, could you report it there? https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/ ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1878094 Title: Ubuntu 20.04 / Pulseaudio RTP receive broken sound Status in pulseaudio package in Ubuntu: New Bug description: just upgraded some of my computers to Ubuntu 20.04, also tried with fresh install, in all case the pulseaudio rtp receive module is giving me very poor sound. Easily reproducible on a single machine : pacmd load-module module-null-sink sink_name=MyNullSink pacmd load-module module-rtp-send source=MyNullSink.monitor loop=true pacmd load-module module-rtp-recv And then play something in the null sink, loopback sound will be bad (lags). What I noticed : if I open the rtp stream with vlc, it's ok, sound is good. Ubuntu 20 uses PulseAudio 13.99, aka (I guess) PulseAudio 14 which implements RTP through gstreamer, which is new. So I tested my rtp stream with gstreamer: gst-launch-1.0 udpsrc address=224.0.0.56 port=46586 caps="application/x-rtp, media=audio, payload=10, clock-rate=44100" ! .recv_rtp_sink_0 rtpbin ! rtpL16depay ! audioconvert ! audioresample ! pulsesink And it works fine, so I definitively believe there is an issue in the new module-rtp-recv.so bundled with PulseAudio and that is now based on gstreamer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:22:55 2020 InstallationDate: Installed on 2019-03-31 (407 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-09 (2 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1404 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX H370-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1404:bd09/13/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXH370-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [deleted] mtime.conffile..etc.pulse.daemon.conf: 2020-05-10T12:17:27.278185 mtime.conffile..etc.pulse.default.pa: 2020-05-10T12:13:15.278817 mtime.conffile..etc.pulse.system.pa: 2020-05-11T16:24:47.654012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878094/+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 1878095] [NEW] Uninstallation leads to broken system
Public bug reported: Steps to reproduce: - Have Ubuntu installed. - Install lightdm. This makes lightdm the active window manager, as far as I can remember. - Uninstall lightdm. - Reboot. Expected result: - System booting another available window manager (gdm3 in this case). - At very least an error message about something being broken (might belong to another package). Actual result: - System boots, but doesn't proceed up to visible graphics -> blank, black screen. Diagnosis: - One can still switch to a text console using Ctrl-Alt-F1..F4 - /etc contains a broken link (took me 2 full days to find that): $ ls -l /etc/systemd/system/display-manager.service ... /etc/systemd/system/display-manager.service -> /lib/systemd/system/lightdm.service Manual fix: $ cd /etc/systemd/system $ sudo ln -sf /lib/systemd/system/gdm3.service display-manager.service Suggested fix: - lightdm making another window manager active on uninstallation, just like it becomes the active manager on installation. - Printing a big ERROR message if there is no other window manager installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:18:02 2020 InstallationDate: Installed on 2016-05-04 (1468 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to focal on 2020-05-03 (7 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1878095 Title: Uninstallation leads to broken system Status in lightdm package in Ubuntu: New Bug description: Steps to reproduce: - Have Ubuntu installed. - Install lightdm. This makes lightdm the active window manager, as far as I can remember. - Uninstall lightdm. - Reboot. Expected result: - System booting another available window manager (gdm3 in this case). - At very least an error message about something being broken (might belong to another package). Actual result: - System boots, but doesn't proceed up to visible graphics -> blank, black screen. Diagnosis: - One can still switch to a text console using Ctrl-Alt-F1..F4 - /etc contains a broken link (took me 2 full days to find that): $ ls -l /etc/systemd/system/display-manager.service ... /etc/systemd/system/display-manager.service -> /lib/systemd/system/lightdm.service Manual fix: $ cd /etc/systemd/system $ sudo ln -sf /lib/systemd/system/gdm3.service display-manager.service Suggested fix: - lightdm making another window manager active on uninstallation, just like it becomes the active manager on installation. - Printing a big ERROR message if there is no other window manager installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:18:02 2020 InstallationDate: Installed on 2016-05-04 (1468 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to focal on 2020-05-03 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1878095/+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 1878094] [NEW] Ubuntu 20.04 / Pulseaudio RTP receive broken sound
Public bug reported: just upgraded some of my computers to Ubuntu 20.04, also tried with fresh install, in all case the pulseaudio rtp receive module is giving me very poor sound. Easily reproducible on a single machine : pacmd load-module module-null-sink sink_name=MyNullSink pacmd load-module module-rtp-send source=MyNullSink.monitor loop=true pacmd load-module module-rtp-recv And then play something in the null sink, loopback sound will be bad (lags). What I noticed : if I open the rtp stream with vlc, it's ok, sound is good. Ubuntu 20 uses PulseAudio 13.99, aka (I guess) PulseAudio 14 which implements RTP through gstreamer, which is new. So I tested my rtp stream with gstreamer: gst-launch-1.0 udpsrc address=224.0.0.56 port=46586 caps="application/x-rtp, media=audio, payload=10, clock-rate=44100" ! .recv_rtp_sink_0 rtpbin ! rtpL16depay ! audioconvert ! audioresample ! pulsesink And it works fine, so I definitively believe there is an issue in the new module-rtp-recv.so bundled with PulseAudio and that is now based on gstreamer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:22:55 2020 InstallationDate: Installed on 2019-03-31 (407 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-09 (2 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1404 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX H370-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1404:bd09/13/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXH370-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [deleted] mtime.conffile..etc.pulse.daemon.conf: 2020-05-10T12:17:27.278185 mtime.conffile..etc.pulse.default.pa: 2020-05-10T12:13:15.278817 mtime.conffile..etc.pulse.system.pa: 2020-05-11T16:24:47.654012 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878094 Title: Ubuntu 20.04 / Pulseaudio RTP receive broken sound Status in pulseaudio package in Ubuntu: New Bug description: just upgraded some of my computers to Ubuntu 20.04, also tried with fresh install, in all case the pulseaudio rtp receive module is giving me very poor sound. Easily reproducible on a single machine : pacmd load-module module-null-sink sink_name=MyNullSink pacmd load-module module-rtp-send source=MyNullSink.monitor loop=true pacmd load-module module-rtp-recv And then play something in the null sink, loopback sound will be bad (lags). What I noticed : if I open the rtp stream with vlc, it's ok, sound is good. Ubuntu 20 uses PulseAudio 13.99, aka (I guess) PulseAudio 14 which implements RTP through gstreamer, which is new. So I tested my rtp stream with gstreamer: gst-launch-1.0 udpsrc address=224.0.0.56 port=46586 caps="application/x-rtp, media=audio, payload=10, clock-rate=44100" ! .recv_rtp_sink_0 rtpbin ! rtpL16depay ! audioconvert ! audioresample ! pulsesink And it works fine, so I definitively believe there is an issue in the new module-rtp-recv.so bundled with PulseAudio and that is now based on gstreamer.
[Touch-packages] [Bug 608449] Re: lspci returns error on devices that don't have pci adapters (arm)
Same issue here in 2020.
===
➜ fa sudo lspci
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
➜ fa uname -a
Linux retropie 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l
GNU/Linux
➜ fa whoami
root
➜ fa lspci
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
➜ fa
===
On :
--
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/608449
Title:
lspci returns error on devices that don't have pci adapters (arm)
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Bug description:
When reporting a system bug on BeagleBoard (ARM based) with Ubuntu,
Apport shows an error while trying to list the pci devices of the
system.
As BeagleBoard doesn't have any pci adapter, the command lspci will
return an error and this error will be inside apport bug report
(besides giving a traceback at the console).
ubuntu@beagle-maverick:~$ ubuntu-bug linux
** Message: pygobject_register_sinkfunc is deprecated (GtkWindow)
** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible)
** Message: pygobject_register_sinkfunc is deprecated (GtkObject)
hook /usr/share/apport/package-hooks//source_linux.py crashed:
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/apport/report.py", line 636, in
add_hooks_info
symb['add_info'](self, ui)
File "/usr/share/apport/package-hooks//source_linux.py", line 123, in
add_info
attach_alsa(report)
File "/usr/lib/python2.6/dist-packages/apport/hookutils.py", line 202, in
attach_alsa
report['PciMultimedia'] = pci_devices(PCI_MULTIMEDIA)
File "/usr/lib/python2.6/dist-packages/apport/hookutils.py", line 354, in
pci_devices
key, value = line.split(':',1)
ValueError: need more than 1 value to unpack
On the report screen:
Lspci:
Error: command ['lspci', '-vvnn'] failed with exit code 1: pcilib: Cannot
open /proc/bus/pci
lspci: Cannot find any working access method
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/608449/+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 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected
** Changed in: gtk Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1878076/+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 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working
Description updated to reflect that this issue is not specific to a particular Intel wireless card. A number of different cards are concerned. ** Summary changed: - software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working + software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working ** Description changed: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files - are present + are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software- properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? + + EDIT: bug confirmed as affecting the following Intel wireless adapter + cards, and assumedly more to come: + + Intel Wi-Fi 6 AX200 + Intel Dual Band Wireless-AC 3165 + Intel Dual Band Wireless-AC 7260 + Intel Dual Band Wireless-AC 8260 + Intel Wireless-AC 9260 + + Also for reference here are the specs of Intel adapter cards: + + ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1859308 Title: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working Status in software-properties package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? EDIT: bug confirmed as affecting the following Intel wireless adapter cards, and assumedly more to come: Intel Wi-Fi 6 AX200 Intel Dual Band Wireless-AC 3165 Intel Dual Band Wireless-AC 7260 Intel Dual Band Wireless-AC 8260 Intel Wireless-AC 9260 Also for reference here are the specs of Intel adapter cards: ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1878091] [NEW] Non-fractional scaling not working
Public bug reported: My laptop has a 4K display. Default Resolution = 3840x2160, scale = 200%. If I set resolution to 1920x1080, everything on the desktop is scaled to double size. So, if I reduce the Scale setting from 200% to 100%, I would expect everything to look normal again, but it does not. 100% and 200% look identical. However, if I enable Fractional scaling and select 125%, that looks correct. So, Fractional scaling works correctly, but non-fractional scaling does not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 15:58:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2020-05-07 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20349 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=4f7e434e-f524-450c-8486-29302f1ca495 ro persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: K0J40709WIN dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: K0J40709WIN dmi.chassis.asset.tag: K0J40709WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvrK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 20349 dmi.product.sku: LENOVO_MT_20349_BU_idea_FM_Lenovo Y50-70 Touch dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Summary changed: - Non-ractional scaling not working + Non-fractional scaling not working -- 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/1878091 Title: Non-fractional scaling not working Status in xorg package in Ubuntu: New Bug description: My laptop has a 4K display. Default Resolution = 3840x2160, scale = 200%. If I set resolution to 1920x1080, everything on the desktop is scaled to double size. So, if I reduce the Scale setting from 200% to 100%, I would expect everything to look normal again, but it does not. 100% and 200% look identical. However, if I enable Fractional scaling and select 125%, that looks correct. So, Fractional scaling works correctly, but non-fractional scaling does not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend:
[Touch-packages] [Bug 1878050] Re: Nvidia GT 240m gives problems
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1878050 Title: Nvidia GT 240m gives problems Status in xorg package in Ubuntu: Incomplete Bug description: Can't install proprietary NVIDIA driver 340.107 X uses software rendering rather than hardware ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-178.208-generic 4.4.217 Uname: Linux 4.4.0-178-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon May 11 18:41:34 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-148-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-98-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0a34] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0688] InstallationDate: Installed on 2017-09-18 (965 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire Z5610 ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-178-generic root=UUID=398c17c4-3b3b-4a56-92f8-6f6a37b9eee1 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2010 dmi.bios.vendor: Phoenix dmi.bios.version: P01-B2L dmi.board.name: Aspire Z5610 dmi.board.vendor: Acer dmi.chassis.type: 13 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnPhoenix:bvrP01-B2L:bd01/19/2010:svnAcer:pnAspireZ5610:pvr:rvnAcer:rnAspireZ5610:rvr:cvnAcer:ct13:cvr: dmi.product.name: Aspire Z5610 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon May 11 18:16:46 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1878050/+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 1878026] Re: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1878026 Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: There is no sound at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abhi 1362 F pulseaudio /dev/snd/controlC0: abhi 1362 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 20:31:56 2020 InstallationDate: Installed on 2020-05-06 (5 days ago) InstallationMedia: It PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abhi 1362 F pulseaudio /dev/snd/controlC0: abhi 1362 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2281 dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd06/11/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn2281:rvr77.13:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: G8D90PA#ACJ dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878026/+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 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED
> - apart from feedback given by @mruffell, to also check if any of librcu consumers are depending on a full membarrier - driven by kernel - for ** shared pages among different processes ** this is a good point, although I don't think liburcu makes guarantees like that, for memory barriers outside of the current process; for example, the -qsbr, -md, and -signal flavors don't use sys_membarrier at all. @mruffell have you looked into that aspect of the change? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liburcu in Ubuntu. https://bugs.launchpad.net/bugs/1876230 Title: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED Status in liburcu package in Ubuntu: Fix Released Status in liburcu source package in Bionic: In Progress Bug description: [Impact] In Linux 4.3, a new syscall was defined, called "membarrier". This systemcall was defined specifically for use in userspace-rcu (liburcu) to speed up the fast path / reader side of the library. The original implementation in Linux 4.3 only supported the MEMBARRIER_CMD_SHARED subcommand of the membarrier syscall. MEMBARRIER_CMD_SHARED executes a memory barrier on all threads from all processes running on the system. When it exits, the userspace thread which called it is guaranteed that all running threads share the same world view in regards to userspace addresses which are consumed by readers and writers. The problem with MEMBARRIER_CMD_SHARED is system calls made in this fashion can block, since it deploys a barrier across all threads in a system, and some other threads can be waiting on blocking operations, and take time to reach the barrier. In Linux 4.14, this was addressed by adding the MEMBARRIER_CMD_PRIVATE_EXPEDITED command to the membarrier syscall. It only targets threads which share the same mm as the thread calling the membarrier syscall, aka, threads in the current process, and not all threads / processes in the system. Calls to membarrier with the MEMBARRIER_CMD_PRIVATE_EXPEDITED command are guaranteed non-blocking, due to using inter-processor interrupts to implement memory barriers. Because of this, membarrier calls that use MEMBARRIER_CMD_PRIVATE_EXPEDITED are much faster than those that use MEMBARRIER_CMD_SHARED. Since Bionic uses a 4.15 kernel, all kernel requirements are met, and this SRU is to enable support for MEMBARRIER_CMD_PRIVATE_EXPEDITED in the liburcu package. This brings the performance of the liburcu library back in line to where it was in Trusty, as this particular user has performance problems upon upgrading from Trusty to Bionic. [Test] Testing performance is heavily dependant on the application which links against liburcu, and the workload which it executes. A test package is available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf276198-test For the sake of testing, we can use the benchmarks provided in the liburcu source code. Download a copy of the source code for liburcu either from the repos or from github: $ pull-lp-source liburcu bionic # OR $ git clone https://github.com/urcu/userspace-rcu.git $ git checkout v0.10.1 # version in bionic Build the code: $ ./bootstrap $ ./configure $ make Go into the tests/benchmark directory $ cd tests/benchmark From there, you can run benchmarks for the four main usages of liburcu: urcu, urcu-bp, urcu-signal and urcu-mb. On a 8 core machine, 6 threads for readers and 2 threads for writers, with a 10 second runtime, execute: $ ./test_urcu 6 2 10 $ ./test_urcu_bp 6 2 10 $ ./test_urcu_signal 6 2 10 $ ./test_urcu_mb 6 2 10 Results: ./test_urcu 6 2 10 0.10.1-1: 17612527667 reads, 268 writes, 17612527935 ops 0.10.1-1ubuntu1: 14988437247 reads, 810069 writes, 14989247316 ops $ ./test_urcu_bp 6 2 10 0.10.1-1: 1177891079 reads, 1699523 writes, 1179590602 ops 0.10.1-1ubuntu1: 13230354737 reads, 575314 writes, 13230930051 ops $ ./test_urcu_signal 6 2 10 0.10.1-1: 20128392417 reads, 6859 writes, 20128399276 ops 0.10.1-1ubuntu1: 20501430707 reads, 6890 writes, 20501437597 ops $ ./test_urcu_mb 6 2 10 0.10.1-1: 627996563 reads, 5409563 writes, 633406126 ops 0.10.1-1ubuntu1: 653194752 reads, 4590020 writes, 657784772 ops The SRU only changes behaviour for urcu and urcu-bp, since they are the only "flavours" of liburcu which the patches change. From a pure ops standpoint: $ ./test_urcu 6 2 10 17612527935 ops 14989247316 ops $ ./test_urcu_bp 6 2 10 1179590602 ops 13230930051 ops We see that this particular benchmark workload, test_urcu sees extra performance overhead with MEMBARRIER_CMD_PRIVATE_EXPEDITED, which is explained by the extra impact that it has on the slowpath, and the extra amount of writes it did during my benchmark. The real
Re: [Touch-packages] [Bug 1877542] Re: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver
Hello Sebastien, I was too happy at the first place. Yes there is the sound on speakers (I didn't managed yet to check HDMI), but there is neither nor sound nor the possibility to connect with BT headphones (all of my 3 sets are failed to connect). And regarding the booting previous kernel: sound from speakers appear only if I boot 4.15.0-96 in safemode Bizarre! Sincerely, Alexey On Mon, 11 May 2020 at 19:05, Alexey Nuyanzin wrote: > Salut Sebastien, > > Thanks for your letter. Log file is in attachment. > > And yay it works again, but not from the first time on 4.15.0-96. I had to > reboot it second time at safemode(without any applied changes in the menu ) > and it sounded well. > Thanks again for you help, I'm not the first-timer on ubuntu, but anyhow I > didn't even thought to just reboot myself under previous version system =) > Is there anyway I can help to fight this bug ? > > Alexey > > > On Mon, 11 May 2020 at 18:35, Sebastien Bacher wrote: > >> Thank you for your bug report, could you look in /var/log/dpkg.log what >> was updated? Could you try to start a previous kernel from the boot menu >> see if that makes a difference? >> >> ** Tags added: bionic >> >> ** Changed in: alsa-driver (Ubuntu) >>Status: New => Incomplete >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1877542 >> >> Title: >> Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver >> >> Status in alsa-driver package in Ubuntu: >> Incomplete >> >> Bug description: >> Hello, >> After last general update sound stops working on all interfaces. >> speakers, headphones nor HDMI provide any sound output even bluetooth >> headphones can't be connected. >> It seems that interface is connected to HDMI >> aplay -l >> >> List of PLAYBACK Hardware Devices >> card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877542/+subscriptions >> > -- 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/1877542 Title: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hello, After last general update sound stops working on all interfaces. speakers, headphones nor HDMI provide any sound output even bluetooth headphones can't be connected. It seems that interface is connected to HDMI aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877542/+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 1878081] [NEW] dbus-launch of gnome-terminal slow on 20.04
Public bug reported: Since upgrading to 20.04 I've seen a roughly 20 second delay between running 'dbus-launch gnome-terminal' and when the terminal actually opens. This happens 100% of the time and was basically instant on previous versions (I've tried on 18.04, 19.04, and 19.10). I've tried explicitly unlocking my keyring given the secret error message below and I've verified gnome-terminal-server and dbus-daemon are both running. If I run gnome-terminal without dbus-launch it activates instantly so there's something about the route through dbus that is causing an issue. I get the following output from the dbus-launch invocation: # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ # watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) # unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) # watch_established: "/org/appmenu/gtk-module/" (establishing: 0) # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ # watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) # unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) # watch_established: "/org/appmenu/gtk-module/" (establishing: 0) # Failed to use specified server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.87 was not provided by any .service files # Falling back to default server. # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) And I see the following in syslog during the launch (note the delay in timestamps): May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] AppArmor D-Bus mediation is enabled May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=1000 pid=6298 comm="/usr/bin/gnome-terminal.real " label="unconfined") May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.gtk.vfs.Daemon' May 11 09:15:57 rfairfax-ubh org.gtk.vfs.Daemon[6310]: fusermount: failed to access mountpoint /run/user/1000/gvfs: Permission denied May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.gnome.Terminal' requested by ':1.0' (uid=1000 pid=6298 comm="/usr/bin/gnome-terminal.real " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.gnome.Terminal' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.2' (uid=1000 pid=6313 comm="/usr/libexec/gnome-terminal-server " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.portal.Documents' requested by ':1.3' (uid=1000 pid=6319 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.4' (uid=1000 pid=6324 comm="/usr/libexec/xdg-document-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.freedesktop.portal.Documents' May 11 09:15:58 rfairfax-ubh systemd[1]: run-user-1000-doc.mount: Succeeded. May 11 09:15:58 rfairfax-ubh systemd[1108]: run-user-1000-doc.mount: Succeeded. May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.impl.portal.desktop.gtk' requested by ':1.3' (uid=1000 pid=6319 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='ca.desrt.dconf' requested by ':1.6' (uid=1000 pid=6345 comm="/usr/libexec/xdg-desktop-portal-gtk " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'ca.desrt.dconf' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.secrets' requested by ':1.3' (uid=1000 pid=6319 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh org.freedesktop.secrets[6359]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh May 11 09:16:23 rfairfax-ubh xdg-desktop-por[6319]: Failed to
[Touch-packages] [Bug 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected
Thanks, there is no real need to report known upstream issue downstream though (unless it's an important issue you believe Ubuntu should prioritize or a patch is available which should be considered for a backport) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Triaged Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1878076/+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 1878076] [NEW] GTK save-dialogs input-focus moves from filename to file search if a folder is selected
Public bug reported: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 ** Affects: gtk Importance: Unknown Status: Unknown ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #326 https://gitlab.gnome.org/GNOME/gtk/issues/326 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/issues/326 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: New Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04
[Touch-packages] [Bug 1875708] Re: Truncated messages in journald since systemd v244
Thanks a lot for your efforts to analyze and fix this bug! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1875708 Title: Truncated messages in journald since systemd v244 Status in libvirt package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: [Impact] * since 09d0b46a "journal: refresh cached credentials of stdout streams" in ~244 output may be trincated. * Upstream has a fix in https://github.com/systemd/systemd/pull/15685 * Backporting the fix will avoid truncation of log output to journald [Test Case] * This could happen in any case, but is more likely when a program that has output going to journald is spawning short-lived sub-programs often. Therefore the test emphasizes on that: - Use a test service like /etc/systemd/system/test.service: [Unit] Description=Test Truncate After=network.target [Service] ExecStart=/usr/lib/test.sh long-test-for-start ExecStop=/usr/lib/test.sh long-test-for-stop Type=oneshot RemainAfterExit=yes StandardOutput=journal+console TimeoutStopSec=0 [Install] WantedBy=multi-user.target - And a test script like /usr/lib/test.sh: #!/bin/sh gettext "This will" echo gettext "usually fail" echo gettext "and be truncated" echo Start/Stopping that service without the fix will look like: Apr 30 18:56:40 f systemd[1]: Stopping Test Truncate... Apr 30 18:56:40 f test.sh[1165]: T Apr 30 18:56:40 f test.sh[1167]: T Apr 30 18:56:40 f test.sh[1167]: sually fai Apr 30 18:56:40 f test.sh[1165]: s Apr 30 18:56:40 f test.sh[1168]: s Apr 30 18:56:40 f test.sh[1168]: nd be truncate Apr 30 18:56:40 f test.sh[1165]: n Apr 30 18:56:40 f systemd[1]: test.service: Succeeded. Apr 30 18:56:40 f systemd[1]: Stopped Test Truncate. [Regression Potential] * The patches are rather small, but there might be a slightly increased memory consumption of journald for output buffers. * Issues (if any and I couldn't find any so far) should be only to journald output handling. Systemd is huge, this at least narrows down the potential places of a regression a lot. [Other Info] * n/a --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Originally reported against libvirt which happens to be one of the example-triggers Hi, when I shut down my machine I see messages from /usr/lib/libvirt /libvirt-guests.sh but there are 2 anomalies: - 3 libvirt-guests.sh processes are run - messages are truncated ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libvirt-daemon 6.0.0-0ubuntu8 Uname: Linux 5.6.7-050607-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Apr 28 19:42:56 2020 SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-multicast.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-mac-broadcast.xml: [inaccessible: [Errno 13] Permission denied:
[Touch-packages] [Bug 1877233] Re: Remove inactive Mirrors to Colombia
Right, I made a typo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1877233 Title: Remove inactive Mirrors to Colombia Status in Ubuntu: Invalid Status in python-apt package in Ubuntu: Fix Released Status in The Bionic Beaver: Invalid Status in python-apt source package in Bionic: Triaged Bug description: Hallo, Our mirror at the mirror.upb.edu.co is being hosted any longer but it is still showing up on the "Software & Updates" application. Could you please remove it? The server is already removed from this list https://launchpad.net/ubuntu/+archivemirrors in the Colombia section. Thanks a lot. Present on bionic (18.04) Present on focal (20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877233/+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 1873764] Re: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id
*** This bug is a duplicate of bug 1872564 *** https://bugs.launchpad.net/bugs/1872564 This is a dupe of https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564 which, AIUI, the server team will be performing an SRU for. ** This bug has been marked a duplicate of bug 1872564 /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice -- 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/1873764 Title: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id Status in cups package in Ubuntu: Confirmed Bug description: I noted the following messages on a just installed Ubuntu Focal: $ dmesg | grep cups [ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 comm="cups-browsed" capability=23 capname="sys_nice" [ 1776.623181] audit: type=1400 audit(1587372145.693:3012): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15510 comm="cups-browsed" capability=23 capname="sys_nice" [ 2040.426033] audit: type=1400 audit(1587372409.494:3013): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426044] audit: type=1400 audit(1587372409.494:3014): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426074] audit: type=1400 audit(1587372409.494:3015): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426092] audit: type=1400 audit(1587372409.494:3016): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426106] audit: type=1400 audit(1587372409.494:3017): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404914] audit: type=1400 audit(1587372410.473:3018): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404920] audit: type=1400 audit(1587372410.473:3019): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404926] audit: type=1400 audit(1587372410.473:3020): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404953] audit: type=1400 audit(1587372410.473:3021): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404963] audit: type=1400 audit(1587372410.473:3022): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925327] audit: type=1400 audit(1587372440.994:3028): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925330] audit: type=1400 audit(1587372440.994:3029): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925337] audit: type=1400 audit(1587372440.994:3030): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925382] audit: type=1400 audit(1587372440.994:3031): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925391] audit: type=1400 audit(1587372440.994:3032): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 It happened after installing Brother DCPL3550CDW Linux drivers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-daemon 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30 Uname: Linux 5.4.0-25-lowlatency x86_64
[Touch-packages] [Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1872564 Title: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice Status in apparmor package in Ubuntu: Fix Committed Status in apparmor source package in Focal: Confirmed Bug description: # Description On a default Focal install, systemd is used when looking up passwd and group information: # grep systemd /etc/nsswitch.conf passwd: files systemd group: files systemd Daemons confined by Apparmor that also query those "databases" will cause this Apparmor denial: audit: type=1400 audit(1586825456.411:247): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 Many daemons confined by Apparmor also happen to downgrade their privileges so they always end up looking up user/group information. # Steps to reproduce 1) launch a Focal container (named fb1 here) $ lxc launch images:ubuntu/focal fb1 2) setup apparmor inside the container (already done on official Ubuntu images) $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y 3) install bind9 $ lxc exec fb1 -- apt install bind9 -y 4) check kernel logs for DENIED $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 'profile="/usr/sbin/named"' Step 4, should not return anything. Because systemd is involved in the user/group lookups, it currently returns the following: audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 # Workaround 1) remove systemd from nsswitch.conf $ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/' /etc/nsswitch.conf 2) restart named $ lxc exec fb1 -- service named restart 3) notice no more denials in kernel logs # Additional information root@fb1:~# apt-cache policy apparmor apparmor: Installed: 2.13.3-7ubuntu4 Candidate: 2.13.3-7ubuntu4 Version table: *** 2.13.3-7ubuntu4 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@fb1:~# uname -a Linux fb1 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@fb1:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564/+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 1878059] Re: Audio device not reachable after wake up
When the devices are gone and test the missing device as $ speaker-test -D hw:0,0 -c 2 It plays the noise sound to my usual speakers. -- 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/1878059 Title: Audio device not reachable after wake up Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878059/+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 1878059] [NEW] Audio device not reachable after wake up
Public bug reported: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878059 Title: Audio device not reachable after wake up Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878059/+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 1877233] Re: Remove inactive Mirrors to Colombia
Brian, The server are: "mirror.upb.edu.co" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1877233 Title: Remove inactive Mirrors to Colombia Status in Ubuntu: Invalid Status in python-apt package in Ubuntu: Fix Released Status in The Bionic Beaver: Invalid Status in python-apt source package in Bionic: Triaged Bug description: Hallo, Our mirror at the mirror.upb.edu.co is being hosted any longer but it is still showing up on the "Software & Updates" application. Could you please remove it? The server is already removed from this list https://launchpad.net/ubuntu/+archivemirrors in the Colombia section. Thanks a lot. Present on bionic (18.04) Present on focal (20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877233/+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 1877159] Re: netlink: 'systemd-network': attribute type 5 has an invalid length.
@ddstreet, PersistentKeepalive is not needed as you'll see in the steps
to reproduce.
** Description changed:
[impact]
systemd-networkd uses incorrect netlink attribute length for wireguard's
persistent keepalive interval, which logs error messages from the
kernel, and may incorrectly set the parameter.
[test case]
- TBD
+ Only 1 Bionic VM is required to reproduce the problem:
+
+ $ lxc launch images:ubuntu/bionic --vm -c security.secureboot=false foo
+ $ sleep 10 # allow booting
+ $ lxc exec foo -- apt install -y software-properties-common
+ $ lxc exec foo -- add-apt-repository -y ppa:wireguard/wireguard
+ $ lxc exec foo -- apt install -y wireguard-tools
+
+ $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.netdev
+ # foo
+ [NetDev]
+ Name=wg0
+ Kind=wireguard
+
+ [WireGuard]
+ ListenPort=
+ PrivateKey=cBkljQSKhtEe/U8GZmCAk2MBbKWL4TLC9PVtbMFyCVQ=
+
+ [WireGuardPeer]
+ PublicKey=emfIuZ3hZ+AnWIrKex/EqCp2mfzip8AxJu6RuweyRGc=
+ AllowedIPs=192.168.255.2
+ Endpoint=bar.lxd:
+ EOF
+
+ $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.network
+ # foo
+ [Match]
+ Name=wg0
+
+ [Network]
+ Address=192.168.255.1/24
+ EOF
+
+ $ lxc exec foo -- systemctl restart systemd-networkd
+
+ # notice the invalid length in dmesg
+ $ lxc exec foo -- journalctl -kn 8
+ -- Logs begin at Mon 2020-05-11 16:56:40 UTC, end at Mon 2020-05-11 17:03:46
UTC. --
+ May 11 16:58:25 foo kernel: nf_tables: (c) 2007-2009 Patrick McHardy
+ May 11 17:01:57 foo kernel: PKCS#7 signature not signed with a trusted key
+ May 11 17:01:57 foo kernel: wireguard: module verification failed: signature
and/or required key missing - tainting kernel
+ May 11 17:01:57 foo kernel: wireguard: WireGuard 1.0.20200429 loaded. See
www.wireguard.com for information.
+ May 11 17:01:57 foo kernel: wireguard: Copyright (C) 2015-2019 Jason A.
Donenfeld . All Rights Reserved.
+ May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has
an invalid length.
+ May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has
an invalid length.
+ May 11 17:02:23 foo kernel: netlink: 'systemd-network': attribute type 5 has
an invalid length.
[regression potential]
this adjusts the length of the specific netlink parameter, so any
regression would likely relate to incorrectly setting the persistent
keepalive interval parameter, or failure to set the parameter.
[scope]
this is needed only for Bionic.
this was fixed upstream in commit
7d0b26a027118ca063780421cb31c74e9d2664ee which was first included in
v240, so this is fixed in Eoan and later. Xenial does not include
support for wireguard, so this does not apply there.
[original description]
This morning, our 2 Bionic machine configured with the wireguard's PPA
and using systemd-networkd to configure the wireguard tunnel started
misbehaving. Why this started just now is unclear ATM but their dmesg
was filled with this:
validate_nla: 100 callbacks suppressed
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
Folks in #systemd mentioned
https://github.com/systemd/systemd/issues/11575 which points to 2
commits missing from Bionic's systemd version:
https://github.com/systemd/systemd/commit/7d0b26a027118ca063780421cb31c74e9d2664ee
https://github.com/systemd/systemd/commit/624a47694cad4c87b2e807c32db656f3e9d679c5
Focal's systemd have the above commits. Would it be possible to backport
those 2 commits to Bionic?
Additional information:
# uname -a
Linux noc-eu1 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
# apt-cache policy systemd wireguard{,-tools,-dkms}
systemd:
Installed: 237-3ubuntu10.39
Candidate: 237-3ubuntu10.39
Version table:
*** 237-3ubuntu10.39 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
237-3ubuntu10.38 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
wireguard:
Installed: 1.0.20200319-1ubuntu1~18.04
Candidate: 1.0.20200319-1ubuntu1~18.04
Version table:
*** 1.0.20200319-1ubuntu1~18.04 500
[Touch-packages] [Bug 1877105] Re: AMD-Vi error message during boot
*** This bug is a duplicate of bug 1835660 *** https://bugs.launchpad.net/bugs/1835660 ** This bug has been marked a duplicate of bug 1835660 initramfs unpacking failed -- 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/1877105 Title: AMD-Vi error message during boot Status in systemd package in Ubuntu: New Bug description: When I boot my KDE 20.04 on my AMD-based Thinkpad T495 I see before the login screen the following error message: 0.703348] Initramfs unpacking failed: Decoding failed 0.713878] pci :00:00.2 AMD.Vi: Unable ro read/write to IOMMU perf couter 0.754103] tpm tpm0: tpm:try:transmit: send(): error -5 0.754122] tpm tpm0: [Firmware Bug] TPM interrupt not working, polling inst Then I see the login screen and everything looks fine. I can log in normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed May 6 14:16:15 2020 InstallationDate: Installed on 2020-05-01 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=537c947f-55fc-4bba-bb91-e7c4b91e39e6 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET49W(1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 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:bvrR12ET49W(1.19):bd01/06/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877105/+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 1877159] Re: netlink: 'systemd-network': attribute type 5 has an invalid length.
Steps to reproduce: lxc launch images:ubuntu/bionic --vm -c security.secureboot=false foo sleep 10 # allow booting lxc exec foo -- apt install -y software-properties-common lxc exec foo -- add-apt-repository -y ppa:wireguard/wireguard lxc exec foo -- apt install -y wireguard-tools cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.netdev # foo [NetDev] Name=wg0 Kind=wireguard [WireGuard] ListenPort= PrivateKey=cBkljQSKhtEe/U8GZmCAk2MBbKWL4TLC9PVtbMFyCVQ= [WireGuardPeer] PublicKey=emfIuZ3hZ+AnWIrKex/EqCp2mfzip8AxJu6RuweyRGc= AllowedIPs=192.168.255.2 Endpoint=bar.lxd: EOF cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.network # foo [Match] Name=wg0 [Network] Address=192.168.255.1/24 EOF lxc exec foo -- systemctl restart systemd-networkd lxc launch images:ubuntu/bionic --vm -c security.secureboot=false bar sleep 10 # allow booting lxc exec bar -- apt install -y software-properties-common lxc exec bar -- add-apt-repository -y ppa:wireguard/wireguard lxc exec bar -- apt install -y wireguard-tools cat << EOF | lxc exec bar -- tee /etc/systemd/network/wg0.netdev # bar [NetDev] Name=wg0 Kind=wireguard [WireGuard] ListenPort= PrivateKey=AHNwUJjVO939UYnp+SjrxYDa1ZlU1uIToCF9CHUitXE= [WireGuardPeer] PublicKey=7TJBZdnkY8zMRVPACZSxT6xL2pAi7/IL4R1DGeThEhY= AllowedIPs=192.168.255.1 Endpoint=foo.lxd: EOF cat << EOF | lxc exec bar -- tee /etc/systemd/network/wg0.network # bar [Match] Name=wg0 [Network] Address=192.168.255.2/24 EOF lxc exec bar -- systemctl restart systemd-networkd # test connectivity lxc exec foo -- ping -qc2 192.168.255.2 # notice the invalid length in dmesg $ lxc exec foo -- journalctl -kn 8 -- Logs begin at Mon 2020-05-11 16:56:40 UTC, end at Mon 2020-05-11 17:03:46 UTC. -- May 11 16:58:25 foo kernel: nf_tables: (c) 2007-2009 Patrick McHardy May 11 17:01:57 foo kernel: PKCS#7 signature not signed with a trusted key May 11 17:01:57 foo kernel: wireguard: module verification failed: signature and/or required key missing - tainting kernel May 11 17:01:57 foo kernel: wireguard: WireGuard 1.0.20200429 loaded. See www.wireguard.com for information. May 11 17:01:57 foo kernel: wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld . All Rights Reserved. May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has an invalid length. May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has an invalid length. May 11 17:02:23 foo kernel: netlink: 'systemd-network': attribute type 5 has an invalid length. -- 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/1877159 Title: netlink: 'systemd-network': attribute type 5 has an invalid length. Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] systemd-networkd uses incorrect netlink attribute length for wireguard's persistent keepalive interval, which logs error messages from the kernel, and may incorrectly set the parameter. [test case] Only 1 Bionic VM is required to reproduce the problem: $ lxc launch images:ubuntu/bionic --vm -c security.secureboot=false foo $ sleep 10 # allow booting $ lxc exec foo -- apt install -y software-properties-common $ lxc exec foo -- add-apt-repository -y ppa:wireguard/wireguard $ lxc exec foo -- apt install -y wireguard-tools $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.netdev # foo [NetDev] Name=wg0 Kind=wireguard [WireGuard] ListenPort= PrivateKey=cBkljQSKhtEe/U8GZmCAk2MBbKWL4TLC9PVtbMFyCVQ= [WireGuardPeer] PublicKey=emfIuZ3hZ+AnWIrKex/EqCp2mfzip8AxJu6RuweyRGc= AllowedIPs=192.168.255.2 Endpoint=bar.lxd: EOF $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.network # foo [Match] Name=wg0 [Network] Address=192.168.255.1/24 EOF $ lxc exec foo -- systemctl restart systemd-networkd # notice the invalid length in dmesg $ lxc exec foo -- journalctl -kn 8 -- Logs begin at Mon 2020-05-11 16:56:40 UTC, end at Mon 2020-05-11 17:03:46 UTC. -- May 11 16:58:25 foo kernel: nf_tables: (c) 2007-2009 Patrick McHardy May 11 17:01:57 foo kernel: PKCS#7 signature not signed with a trusted key May 11 17:01:57 foo kernel: wireguard: module verification failed: signature and/or required key missing - tainting kernel May 11 17:01:57 foo kernel: wireguard: WireGuard 1.0.20200429 loaded. See www.wireguard.com for information. May 11 17:01:57 foo kernel: wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld . All Rights Reserved. May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has an invalid length. May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has an invalid length.
[Touch-packages] [Bug 1628153] Re: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most restarts
** Changed in: alsa-driver (Ubuntu) Assignee: (unassigned) => Abhirup Pal (monalisarai) -- 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/1628153 Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most restarts Status in alsa-driver package in Ubuntu: Confirmed Bug description: On the vast majority of restarts of Ubuntu 16.04 I get no internal sound at all. There are no reported issues in system settings on the only sound card I have. The volume is not muted. On an estimated 1 in 10 restart, the sound works, and both the test sounds get played and other applications work fine. There is no reported errors or messages on the restarts when the sound has failed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tony 16160 F...m pulseaudio /dev/snd/controlC1: tony 16160 F pulseaudio /dev/snd/controlC0: tony 16160 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 27 15:56:02 2016 InstallationDate: Installed on 2015-10-29 (334 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) 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_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tony 16160 F...m pulseaudio /dev/snd/controlC1: tony 16160 F pulseaudio /dev/snd/controlC0: tony 16160 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-08-13 (45 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_67SF dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W65_67SF dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1628153/+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 1878051] Re: root-unittests' test-execute fails in LXC
Failing since Bionic, at least. -- 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/1878051 Title: root-unittests' test-execute fails in LXC Status in systemd package in Ubuntu: New Bug description: ... exec-bindpaths.service: Child 1573 belongs to exec-bindpaths.service. exec-bindpaths.service: Main process exited, code=exited, status=0/SUCCESS exec-bindpaths.service: Running next main command for state start. exec-bindpaths.service: Passing 0 fds to service exec-bindpaths.service: About to execute: /usr/bin/test -f /tmp/thisisasimpletest exec-bindpaths.service: Forked /usr/bin/test as 1574 PR_SET_MM_ARG_START failed, attempting PR_SET_MM_ARG_END hack: Operation not permitted PR_SET_MM_ARG_END hack failed, proceeding without: Operation not permitted Applying namespace mount on /run/systemd/unit-root/tmp/test-exec-bindpaths Followed source symlinks /tmp → /tmp. Successfully mounted /tmp to /run/systemd/unit-root/tmp/test-exec-bindpaths Applying namespace mount on /run/systemd/unit-root/tmp/test-exec-bindreadonlypaths Followed source symlinks /tmp → /tmp. Successfully mounted /tmp to /run/systemd/unit-root/tmp/test-exec-bindreadonlypaths Failed to re-mount '/run/systemd/unit-root/tmp/test-exec-bindreadonlypaths' and its submounts: Permission denied exec-bindpaths.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied exec-bindpaths.service: Executing: /usr/bin/test -f /tmp/thisisasimpletest Received SIGCHLD from PID 1574 (test). Child 1574 (test) died (code=exited, status=1/FAILURE) exec-bindpaths.service: Child 1574 belongs to exec-bindpaths.service. exec-bindpaths.service: Main process exited, code=exited, status=1/FAILURE exec-bindpaths.service: Failed with result 'exit-code'. exec-bindpaths.service: Changed start -> failed exec-bindpaths.service: Unit entered failed state. test_exec_bindpaths: exec-bindpaths.service: exit status 1, expected 0 FAIL: test-execute (code: 134) Aborted (core dumped) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1878051/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Thanks for all the help so far. -- 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/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1877871] Re: X windows hnags following upgrade from 18.04 to 20.04
** Package changed: ubuntu-release-upgrader (Ubuntu) => xorg (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/1877871 Title: X windows hnags following upgrade from 18.04 to 20.04 Status in xorg package in Ubuntu: New Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877871/+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 1877901] Re: Softare and Updates app scrolling back up automatically after enabling each of the disabled pacakges during update.
** Package changed: ubuntu-release-upgrader (Ubuntu) => software- properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1877901 Title: Softare and Updates app scrolling back up automatically after enabling each of the disabled pacakges during update. Status in software-properties package in Ubuntu: New Bug description: Ubuntu installer disables third party addons while updgrade. When manually enabling them after the upgrade, the app auto-scrolls all the way up after each individual package is enabled. This is very frustrating and impossible to use. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 19:30:55 2020 InstallationDate: Installed on 2017-08-20 (994 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to focal on 2020-05-10 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1877901/+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 1878051] [NEW] root-unittests' test-execute fails in LXC
Public bug reported: ... exec-bindpaths.service: Child 1573 belongs to exec-bindpaths.service. exec-bindpaths.service: Main process exited, code=exited, status=0/SUCCESS exec-bindpaths.service: Running next main command for state start. exec-bindpaths.service: Passing 0 fds to service exec-bindpaths.service: About to execute: /usr/bin/test -f /tmp/thisisasimpletest exec-bindpaths.service: Forked /usr/bin/test as 1574 PR_SET_MM_ARG_START failed, attempting PR_SET_MM_ARG_END hack: Operation not permitted PR_SET_MM_ARG_END hack failed, proceeding without: Operation not permitted Applying namespace mount on /run/systemd/unit-root/tmp/test-exec-bindpaths Followed source symlinks /tmp → /tmp. Successfully mounted /tmp to /run/systemd/unit-root/tmp/test-exec-bindpaths Applying namespace mount on /run/systemd/unit-root/tmp/test-exec-bindreadonlypaths Followed source symlinks /tmp → /tmp. Successfully mounted /tmp to /run/systemd/unit-root/tmp/test-exec-bindreadonlypaths Failed to re-mount '/run/systemd/unit-root/tmp/test-exec-bindreadonlypaths' and its submounts: Permission denied exec-bindpaths.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied exec-bindpaths.service: Executing: /usr/bin/test -f /tmp/thisisasimpletest Received SIGCHLD from PID 1574 (test). Child 1574 (test) died (code=exited, status=1/FAILURE) exec-bindpaths.service: Child 1574 belongs to exec-bindpaths.service. exec-bindpaths.service: Main process exited, code=exited, status=1/FAILURE exec-bindpaths.service: Failed with result 'exit-code'. exec-bindpaths.service: Changed start -> failed exec-bindpaths.service: Unit entered failed state. test_exec_bindpaths: exec-bindpaths.service: exit status 1, expected 0 FAIL: test-execute (code: 134) Aborted (core dumped) ... ** Affects: systemd (Ubuntu) Importance: Low Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1878051 Title: root-unittests' test-execute fails in LXC Status in systemd package in Ubuntu: New Bug description: ... exec-bindpaths.service: Child 1573 belongs to exec-bindpaths.service. exec-bindpaths.service: Main process exited, code=exited, status=0/SUCCESS exec-bindpaths.service: Running next main command for state start. exec-bindpaths.service: Passing 0 fds to service exec-bindpaths.service: About to execute: /usr/bin/test -f /tmp/thisisasimpletest exec-bindpaths.service: Forked /usr/bin/test as 1574 PR_SET_MM_ARG_START failed, attempting PR_SET_MM_ARG_END hack: Operation not permitted PR_SET_MM_ARG_END hack failed, proceeding without: Operation not permitted Applying namespace mount on /run/systemd/unit-root/tmp/test-exec-bindpaths Followed source symlinks /tmp → /tmp. Successfully mounted /tmp to /run/systemd/unit-root/tmp/test-exec-bindpaths Applying namespace mount on /run/systemd/unit-root/tmp/test-exec-bindreadonlypaths Followed source symlinks /tmp → /tmp. Successfully mounted /tmp to /run/systemd/unit-root/tmp/test-exec-bindreadonlypaths Failed to re-mount '/run/systemd/unit-root/tmp/test-exec-bindreadonlypaths' and its submounts: Permission denied exec-bindpaths.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied exec-bindpaths.service: Executing: /usr/bin/test -f /tmp/thisisasimpletest Received SIGCHLD from PID 1574 (test). Child 1574 (test) died (code=exited, status=1/FAILURE) exec-bindpaths.service: Child 1574 belongs to exec-bindpaths.service. exec-bindpaths.service: Main process exited, code=exited, status=1/FAILURE exec-bindpaths.service: Failed with result 'exit-code'. exec-bindpaths.service: Changed start -> failed exec-bindpaths.service: Unit entered failed state. test_exec_bindpaths: exec-bindpaths.service: exit status 1, expected 0 FAIL: test-execute (code: 134) Aborted (core dumped) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1878051/+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 1877871] [NEW] X windows hnags following upgrade from 18.04 to 20.04
You have been subscribed to a public bug: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- X windows hnags following upgrade from 18.04 to 20.04 https://bugs.launchpad.net/bugs/1877871 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878050] [NEW] Nvidia GT 240m gives problems
Public bug reported: Can't install proprietary NVIDIA driver 340.107 X uses software rendering rather than hardware ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-178.208-generic 4.4.217 Uname: Linux 4.4.0-178-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon May 11 18:41:34 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-148-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-98-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0a34] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0688] InstallationDate: Installed on 2017-09-18 (965 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire Z5610 ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-178-generic root=UUID=398c17c4-3b3b-4a56-92f8-6f6a37b9eee1 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2010 dmi.bios.vendor: Phoenix dmi.bios.version: P01-B2L dmi.board.name: Aspire Z5610 dmi.board.vendor: Acer dmi.chassis.type: 13 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnPhoenix:bvrP01-B2L:bd01/19/2010:svnAcer:pnAspireZ5610:pvr:rvnAcer:rnAspireZ5610:rvr:cvnAcer:ct13:cvr: dmi.product.name: Aspire Z5610 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon May 11 18:16:46 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1878050 Title: Nvidia GT 240m gives problems Status in xorg package in Ubuntu: New Bug description: Can't install proprietary NVIDIA driver 340.107 X uses software rendering rather than hardware ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-178.208-generic 4.4.217 Uname: Linux 4.4.0-178-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon May 11 18:41:34 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-148-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-98-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0a34] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0688] InstallationDate: Installed on 2017-09-18 (965 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire Z5610 ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-178-generic root=UUID=398c17c4-3b3b-4a56-92f8-6f6a37b9eee1 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg
[Touch-packages] [Bug 1877901] [NEW] Softare and Updates app scrolling back up automatically after enabling each of the disabled pacakges during update.
You have been subscribed to a public bug: Ubuntu installer disables third party addons while updgrade. When manually enabling them after the upgrade, the app auto-scrolls all the way up after each individual package is enabled. This is very frustrating and impossible to use. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 19:30:55 2020 InstallationDate: Installed on 2017-08-20 (994 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to focal on 2020-05-10 (0 days ago) VarLogDistupgradeTermlog: ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- Softare and Updates app scrolling back up automatically after enabling each of the disabled pacakges during update. https://bugs.launchpad.net/bugs/1877901 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815420] Re: package avahi-daemon 0.7-4ubuntu2.1 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: avahi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1815420 Title: package avahi-daemon 0.7-4ubuntu2.1 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 1 Status in avahi package in Ubuntu: Confirmed Bug description: this error is shown when installing the ubuntu upgrade ProblemType: Package DistroRelease: Ubuntu 18.10 Package: avahi-daemon 0.7-4ubuntu2.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Mon Feb 11 09:16:27 2019 ErrorMessage: installed avahi-daemon package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-03 (38 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: avahi Title: package avahi-daemon 0.7-4ubuntu2.1 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.avahi.avahi-daemon.conf: 2019-01-16T08:54:28.689053 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1815420/+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 1864307] Re: Many apps have no icon in Software on Focal
Neat :-) That should do the job for all combinations of snap-store and gnome-software, once the GS patch is in there as well. Thanks Ken for doing the integration work :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Released Status in gnome-software source package in Focal: New Status in ubuntu-meta source package in Focal: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. [Impact] * Some apt packages do not include an icon in snap-store [Test Case] * Open snap-store, search for GCompris and confirm there is an appropriate icon [Regression Potential] * Very low. Previous Ubuntu releases including apt-config-icons based on the depends in gnome-software. This just adds an apt config that can be used to fetch icons for apt packages via apt. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1877932] Re: Bluetooth not connecting to last paired device when enabling bluetooth
Hi, It is not connecting at Bluetooth level. Once I manage to get it connected, all works like charm. On Mon, May 11, 2020, 2:30 PM Sebastien Bacher wrote: > Thank you for your bug report. Is it not connecting to the device at the > bluetooth level or is connecting but not routing the sound to the > headset? > > ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) > > ** Changed in: pulseaudio (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877932 > > Title: > Bluetooth not connecting to last paired device when enabling bluetooth > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > > I am using a Dell Lattitude E7470 laptop. I am trying to connect a > Bluetooth headset (Anker). > I am seeing this issue with the latest upgrade to the Ubuntu 20.04 LTS > version. I have a Bluetooth headset which is paired with the machine. Given > the Bluetooth is enabled in the Ubuntu machine and I switch on my Bluetooth > headset, the ubuntu machine does not automatically connect to this device > anymore. It used to do it very easily with 18.04,19.04 and 19.10 ubuntu > version. > I have to do a variety of steps to get it connected: > * turn off and on the headset. > * turn off and on the laptop bluetooth. > * try manully connecting to the device from the setting menu multiple > times. > * Sometimes it detects and get connected automatically as it should. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 > Uname: Linux 5.4.0-29-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: justin 2220 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sun May 10 19:42:46 2020 > InstallationDate: Installed on 2019-02-21 (444 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > PackageArchitecture: all > ProcEnviron: >LANGUAGE=en_GB:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_GB.UTF-8 >SHELL=/usr/bin/zsh > SourcePackage: alsa-driver > Symptom: audio > Title: Bluetooth sound card not detected > UpgradeStatus: Upgraded to focal on 2020-04-27 (13 days ago) > dmi.bios.date: 10/08/2019 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.22.8 > dmi.board.name: 0T6HHJ > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.22.8:bd10/08/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: > dmi.product.family: Latitude > dmi.product.name: Latitude E7470 > dmi.product.sku: 06DC > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877932/+subscriptions > -- 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/1877932 Title: Bluetooth not connecting to last paired device when enabling bluetooth Status in pulseaudio package in Ubuntu: Incomplete Bug description: I am using a Dell Lattitude E7470 laptop. I am trying to connect a Bluetooth headset (Anker). I am seeing this issue with the latest upgrade to the Ubuntu 20.04 LTS version. I have a Bluetooth headset which is paired with the machine. Given the Bluetooth is enabled in the Ubuntu machine and I switch on my Bluetooth headset, the ubuntu machine does not automatically connect to this device anymore. It used to do it very easily with 18.04,19.04 and 19.10 ubuntu version. I have to do a variety of steps to get it connected: * turn off and on the headset. * turn off and on the laptop bluetooth. * try manully connecting to the device from the setting menu multiple times. * Sometimes it detects and get connected automatically as it should. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 2220 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 19:42:46 2020 InstallationDate: Installed on 2019-02-21 (444 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh SourcePackage:
[Touch-packages] [Bug 1877233] Re: Remove inactive Mirrors to Colombia
The application you see this in, software-properties, uses /usr/share /python-apt/templates/Ubuntu.mirrors as the source of information for the available mirrors. In Ubuntu 20.04 LTS, with python-apt version 2.0.0, I do not see "mirror.upb.edu.com", however I do see that in 18.04 LTS. We'll target this for fixing in our next upload of python-apt for Ubuntu 18.04 LTS. ** Package changed: choose-mirror (Ubuntu) => python-apt (Ubuntu) ** Changed in: python-apt (Ubuntu) Status: Incomplete => Triaged ** Changed in: python-apt (Ubuntu) Importance: Undecided => Medium ** Also affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: Ubuntu Bionic Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu Bionic) Status: New => Triaged ** Changed in: python-apt (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: python-apt (Ubuntu Bionic) Milestone: None => ubuntu-18.04.5 ** Changed in: python-apt (Ubuntu) Status: Triaged => Fix Released ** Changed in: ubuntu Status: Confirmed => Invalid ** Changed in: Ubuntu Bionic Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1877233 Title: Remove inactive Mirrors to Colombia Status in Ubuntu: Invalid Status in python-apt package in Ubuntu: Fix Released Status in The Bionic Beaver: Invalid Status in python-apt source package in Bionic: Triaged Bug description: Hallo, Our mirror at the mirror.upb.edu.co is being hosted any longer but it is still showing up on the "Software & Updates" application. Could you please remove it? The server is already removed from this list https://launchpad.net/ubuntu/+archivemirrors in the Colombia section. Thanks a lot. Present on bionic (18.04) Present on focal (20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877233/+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 1877542] Re: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver
Salut Sebastien, Thanks for your letter. Log file is in attachment. And yay it works again, but not from the first time on 4.15.0-96. I had to reboot it second time at safemode(without any applied changes in the menu ) and it sounded well. Thanks again for you help, I'm not the first-timer on ubuntu, but anyhow I didn't even thought to just reboot myself under previous version system =) Is there anyway I can help to fight this bug ? Alexey On Mon, 11 May 2020 at 18:35, Sebastien Bacher wrote: > Thank you for your bug report, could you look in /var/log/dpkg.log what > was updated? Could you try to start a previous kernel from the boot menu > see if that makes a difference? > > ** Tags added: bionic > > ** Changed in: alsa-driver (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877542 > > Title: > Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver > > Status in alsa-driver package in Ubuntu: > Incomplete > > Bug description: > Hello, > After last general update sound stops working on all interfaces. > speakers, headphones nor HDMI provide any sound output even bluetooth > headphones can't be connected. > It seems that interface is connected to HDMI > aplay -l > > List of PLAYBACK Hardware Devices > card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877542/+subscriptions > ** Attachment added: "dpkg.log" https://bugs.launchpad.net/bugs/1877542/+attachment/5369926/+files/dpkg.log -- 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/1877542 Title: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hello, After last general update sound stops working on all interfaces. speakers, headphones nor HDMI provide any sound output even bluetooth headphones can't be connected. It seems that interface is connected to HDMI aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877542/+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 1877828] Re: Missing feature: disable one specific wireless device meanwhile another remain switched on
Thank you for your bug report, the disable item not doing what expected in the indicator sounds like a gnome-shell issue Would be worth reporting upstream on https://gitlab.gnome.org/GNOME /gnome-shell/issues ** Package changed: network-manager (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1877828 Title: Missing feature: disable one specific wireless device meanwhile another remain switched on Status in gnome-shell package in Ubuntu: New Bug description: When working on laptop, we may need an external wifi adapter in order to catch a remote access point no working well with the built-in wireless card of the laptop. In such case, it would make sense to disable the internal wireless card in order to have just the external on working. However, Ubuntu does not offer a simple way to do so. Moreover, if I click on "Turn off" for the built-in wifi adapter in the top right corner menu (see the screenshot), both wifi adapters are swtiched off, which is not the desired effect. See for example: https://askubuntu.com/questions/168032/how-to- disable-built-in-wifi-and-use-only-usb-wifi-card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877828/+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 1877793] Re: [Inspiron 13-5378, Realtek ALC3253, Speaker, Internal] No sound at all
** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low -- 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/1877793 Title: [Inspiron 13-5378, Realtek ALC3253, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Is a duplicate of bug 1877766 On installation 16.04 LTS there is sound. Also sound in windows. But as soon as Ubuntu updates, no sound. Tried 18 LTS no sound Tried 20 LTS - sound comes back But I want to stick with 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1556 F pulseaudio CurrentDesktop: Unity Date: Sat May 9 22:26:24 2020 InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) 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_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1556 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 13-5378, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.28.0 dmi.board.name: 05C3PP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.28.0:bd05/10/2019:svnDellInc.:pnInspiron13-5378:pvr:rvnDellInc.:rn05C3PP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 13-5378 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877793/+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 1878026] Re: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1878026 Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: There is no sound at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abhi 1362 F pulseaudio /dev/snd/controlC0: abhi 1362 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 20:31:56 2020 InstallationDate: Installed on 2020-05-06 (5 days ago) InstallationMedia: It PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abhi 1362 F pulseaudio /dev/snd/controlC0: abhi 1362 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2281 dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd06/11/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn2281:rvr77.13:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: G8D90PA#ACJ dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878026/+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 1877233] [NEW] Remove inactive Mirrors to Colombia
You have been subscribed to a public bug: Hallo, Our mirror at the mirror.upb.edu.co is being hosted any longer but it is still showing up on the "Software & Updates" application. Could you please remove it? The server is already removed from this list https://launchpad.net/ubuntu/+archivemirrors in the Colombia section. Thanks a lot. Present on bionic (18.04) Present on focal (20.04) ** Affects: ubuntu Importance: Undecided Status: Confirmed ** Affects: python-apt (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment mirror -- Remove inactive Mirrors to Colombia https://bugs.launchpad.net/bugs/1877233 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825946] Autopkgtest regression report (network-manager/1.2.6-0ubuntu0.16.04.4)
All autopkgtests for the newly accepted network-manager
(1.2.6-0ubuntu0.16.04.4) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/229-4ubuntu21.23 (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#network-manager
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1825946
Title:
'nm' autopkgtest fails due to GI stderr output
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
Fix Committed
Status in network-manager source package in Bionic:
Fix Released
Bug description:
[impact]
'nm' testcase contains:
from gi.repository import NetworkManager, NMClient, GLib
which generates output to stderr:
/tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning:
NetworkManager was imported without specifying a version first. Use
gi.require_version('NetworkManager', '1.0') before import to ensure that the
right version gets loaded.
the gi.require_version call has already been added to cosmic and
disco.
[test case]
see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
results.
[other info]
this only fails intermittently, but the failure is clearly not an
actual problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1825946/+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 1878026] [NEW] [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all
You have been subscribed to a public bug: There is no sound at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abhi 1362 F pulseaudio /dev/snd/controlC0: abhi 1362 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 20:31:56 2020 InstallationDate: Installed on 2020-05-06 (5 days ago) InstallationMedia: It PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abhi 1362 F pulseaudio /dev/snd/controlC0: abhi 1362 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2281 dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd06/11/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn2281:rvr77.13:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: G8D90PA#ACJ dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all https://bugs.launchpad.net/bugs/1878026 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710511] Re: nano crashed with SIGSEGV in get_sysdep_segment_value()
** Changed in: nano (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1710511 Title: nano crashed with SIGSEGV in get_sysdep_segment_value() Status in nano package in Ubuntu: Incomplete Bug description: When update ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nano 2.8.6-2 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 9 20:22:31 2017 ExecutablePath: /bin/nano InstallationDate: Installed on 2017-08-09 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170806) ProcCmdline: nano /etc/defaults/grub SegvAnalysis: Segfault happened at: 0x7fdda72da0f5 <_nl_find_msg+725>: mov (%r12),%rdi PC (0x7fdda72da0f5) ok source "(%r12)" (0x30b03019) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nano StacktraceTop: get_sysdep_segment_value (name=0x7fdda7cd3364 ) at loadmsgcat.c:727 _nl_load_domain (domain_file=0x55d7c83aafc0, domainbinding=domainbinding@entry=0x0) at loadmsgcat.c:1002 _nl_find_domain (dirname=dirname@entry=0x7fdda743ca40 <_nl_default_dirname> "/usr/share/locale", locale=locale@entry=0x7ffcc307a400 "pt", domainname=domainname@entry=0x7ffcc307a420 "LC_MESSAGES/libc.mo", domainbinding=domainbinding@entry=0x0) at finddomain.c:173 __dcigettext (domainname=0x7fdda7435a40 <_libc_intl_domainname> "libc", msgid1=0x7fdda7435dfd "No such file or directory", msgid2=msgid2@entry=0x0, plural=plural@entry=0, n=n@entry=0, category=category@entry=5) at dcigettext.c:722 __GI___dcgettext (domainname=, msgid=, category=category@entry=5) at dcgettext.c:47 Title: nano crashed with SIGSEGV in get_sysdep_segment_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1710511/+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 1853825] Re: ^W ^G ^X fails to redisplay the text being edited
** Changed in: nano (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1853825 Title: ^W ^G ^X fails to redisplay the text being edited Status in nano package in Ubuntu: Fix Released Bug description: There is a silly display bug in nano-4.3 (https://savannah.gnu.org/bugs/?57295): when opening some file (for example, 'nano README') and typing the sequence Ctrl+W Ctrl+G Ctrl+X, the Search help text stays on the screen whereas the text of the README file should be redisplayed. Attached upstream patch fixes this. Please apply to Eoan. (It could be applied to Focal too, but nano-4.6 will be out within a week, so it's probably not worth the effort.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1853825/+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 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working
** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low -- 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/1877726 Title: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working Status in alsa-driver package in Ubuntu: New Bug description: Please see https://askubuntu.com/questions/1229085/ubuntu-with-rodecaster-pro-usb-soundcard/1236257#1236257 for most background. tl;dr: - The Rodecaster Pro is a USB audio standard compliant device - lsusb sees it, but alsa cannot use it - trying the exact same setup with a Scarlett 2i2 USB device works (with some caveats, see the mentioned post) Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug. Alsa info is at http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also attached. nils@blackbox:~/tmp/soundtest$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 nils@blackbox:~/tmp/soundtest$ arecord --list-devices List of CAPTURE Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 2: ALC887-VD Alt Analog [ALC887-VD Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:45:20 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-23 (1354 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AudioUsers: pulse Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: Sound works for some users but not for others Title: [HDA-Intel - HD-Audio Generic, playback] sound not working for all users UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago) dmi.bios.date: 10/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5222 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5222:bd10/14/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-09T11:23:29.080704 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877726/+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 1855009] Autopkgtest regression report (network-manager/1.2.6-0ubuntu0.16.04.4)
All autopkgtests for the newly accepted network-manager (1.2.6-0ubuntu0.16.04.4) for xenial have finished running. The following regressions have been reported in tests triggered by the package: systemd/229-4ubuntu21.23 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/xenial/update_excuses.html#network-manager [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Released Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1864307] Re: Many apps have no icon in Software on Focal
This bug was fixed in the package ubuntu-meta - 1.451 --- ubuntu-meta (1.451) groovy; urgency=medium * Refreshed dependencies * Added apt-config-icons-hidpi to desktop-minimal-recommends, desktop- recommends (LP: #1864307) * Added bind9-dnsutils to standard * Removed dnsutils from standard -- Ken VanDine Mon, 11 May 2020 09:31:32 -0400 ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Released Status in gnome-software source package in Focal: New Status in ubuntu-meta source package in Focal: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. [Impact] * Some apt packages do not include an icon in snap-store [Test Case] * Open snap-store, search for GCompris and confirm there is an appropriate icon [Regression Potential] * Very low. Previous Ubuntu releases including apt-config-icons based on the depends in gnome-software. This just adds an apt config that can be used to fetch icons for apt packages via apt. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
Thank you for your bug report, it could be worth reporting the issue upstream as explained on https://www.alsa-project.org/wiki/Bug_Tracking -- 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/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: New Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV 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.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV 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/alsa-driver/+bug/1877640/+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 1877580] Re: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all
The log has those errors [22342.556235] xhci_hcd :00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 [22342.556246] xhci_hcd :00:14.0: Looking for event-dma 000469ddc2e0 trb-start 000469ddc2f0 trb-end 000469ddc2f0 seg-start 000469ddc000 seg-end 000469ddcff0 [22888.731315] perf: interrupt took too long (5034 > 4968), lowering kernel.perf_event_max_sample_rate to 39500 unsure if that's a kernel issue ? -- 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/1877580 Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the headphones. The internal loud speakers works ok when the headphones are not plugged in. More specifically: If I open the pavucontrol without the headphones plugged in I see that is correctly mentioning the output as Port: "Speakers (plugged-in)" and everything works ok, I have sound from the speakers. The moment I plug in the headphones, for a fraction of a second I can hear sound on the headphones, and then the output port switches to "headphones" which is the moment I lose the sound. The fraction that I hear the sound is when the jack is half-inserted and I get the sound on one channel only. When is fully inserted, the computer detects it and makes the switch. I've tried also in alsamixer all possibilities I could imagine, playing with mute/unmute and gain of each channel, with no success ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bnv1312 F pulseaudio bnv 21367 F alsamixer /dev/snd/pcmC0D0c: bnv1312 F...m pulseaudio /dev/snd/pcmC0D0p: bnv1312 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri May 8 15:41:08 2020 InstallationDate: Installed on 2019-08-08 (274 days ago) InstallationMedia: Xubuntu 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_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bnv1312 F pulseaudio bnv 21367 F alsamixer /dev/snd/pcmC0D0c: bnv1312 F...m pulseaudio /dev/snd/pcmC0D0p: bnv1312 F...m pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877580/+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 1859308] Re: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working
I have the same problem with a fresh install of Ubuntu 20.04 LTS release on a Dell Latitude E5440 with Intel Wireless 7260. Also, the wifi connection is quite unstable and would sometimes freeze altogether, until I disconnect and connect again. With Ubuntu 18.04 on the same machine I have never had any problems before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1859308 Title: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working Status in software-properties package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+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 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module
This bug was fixed in the package systemd - 229-4ubuntu21.28
---
systemd (229-4ubuntu21.28) xenial; urgency=medium
* d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657)
* d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch:
- when restarting service after failure, replace existing queued jobs
(LP: #1839290)
* d/t/storage:
- fix buggy test (LP: #1831459)
- without scsi_debug, skip test (LP: #1847816)
* d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch:
- fix resolution of IntelliMouse (LP: #1867421)
* d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch:
- allow vacuuming journal 'root' dir (LP: #1858412)
* d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch:
- do not let invalid hostname break dhcpv4 (LP: #1862232)
* d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194)
* d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch:
- do not crash if NULL passted to journal destructor (LP: #1837914)
* d/e/initramfs-tools/hooks/udev:
- Follow symlinks when finding link files to copy into initramfs
(LP: #1868892)
-- Dan Streetman Mon, 20 Apr 2020 10:17:40
-0400
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1847816
Title:
storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
that don't include scsi_debug module
Status in autopkgtest-cloud:
Fix Released
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:
Fix Released
Status in linux-kvm source package in Bionic:
New
Status in systemd source package in Bionic:
Fix Released
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 Released
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 1858412] Re: systemd vacuuming does not work for remote journals
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1858412 Title: systemd vacuuming does not work for remote journals Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: [impact] attempting to vacuum journals using -D with the 'root' (in journald terms) journal directory fails to perform any vacuuming. This can lead to journal files continually increasing in size and filling up the filesystem. [test case] see original description below. [regession potential] this removes a check in the code when iterating journal directories during vacuuming, so any regression would likely occur during vacuuming, possibly causing failure to vacuum. [scope] this is fixed upstream by commit c488660e6edb3c1375ab62514a8df035c3d712bf which is included starting in version 244, so this is already included in Focal. This is needed for Eoan, Bionic, and Xenial. [original description] systemd has an issue in regard to vacuuming remote journals: https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as this version still has this problem. Steps to reproduce on "Description: Ubuntu 18.04.3 LTS": root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ Would it be possible to backport this trivial patch https://github.com/systemd/systemd/pull/13924 into 18.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+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 1831459] Re: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1831459 Title: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: 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: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: [impact] test case fails because it does not wait for the service to become active before stopping it, resulting in failure to rmmod the scsi_debug module because it's still in use. [test case] check 'storage' test results for systemd in autopkgtest logs, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz [regression potential] low; test case fix only. [other info] detected and reported by @cascardo in bug 1814373 comment 4 and 5, but separate (non-test) systemd bugfix uploaded for that bug so opening this bug to track fixing the test case. larger fixes/improvements to 'storage' testcase in bug 1829347, but those rejected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831459/+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 1839290] Re: systemd doesn't restart a service after crashes
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1839290 Title: systemd doesn't restart a service after crashes Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [impact] when a service configured to restart crashes, under certain configurations, that service is not correctly restarted. [test case] see comment 8 [regression potential] this changes the job mode of manager-triggered restarts to 'replace' any existing queued job(s), instead of failing if there are queued job(s). thus any regressions would occur when a service fails, that is configured to restart on failure. [scope] This is needed only for Xenial and Bionic. this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51 which is included already in Eoan. Fixed in Disco with the backported v240 patch from https://github.com/systemd/systemd/commit/677b4cc753f183731fc54fcb68ad46f806c394bc [other info] original description: --- Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+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 1837914] Re: restart systemd-jounald fails
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837914 Title: restart systemd-jounald fails Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: [impact] in some situations, restarting journald causes assertion failure. [test case] intermittently, when restarting journald. See upstream bug for repro details. [regression potential] this adjusts the journal file destructor, so any regression would likely occur when cleaning up journal files and/or stopping/restarting. [scope] this is fixed by commit c377a6f3ad3d9bed4ce7e873e8e9ec6b1650c57d which is included in Focal. This is needed for Eoan and earlier. [original description] While restarting systemd-jounald, the following error message occurs: systemd-journald[28007]: Assertion 'f' failed at ../src/journal /journal-file.c:143, function journal_file_close(). Aborting. release: Ubuntu 16.04.5 LTS systemd version: 229-4ubuntu21.22 This issue is reported at https://github.com/systemd/systemd/issues/12400 and solved at https://github.com/systemd/systemd/pull/12679 Please cherry-pick this fix to the ubuntu16.04 package. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837914/+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 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867421 Title: Microsoft Classic IntelliMouse moves way too fast Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] Microsoft Classic IntelliMouse moves way too fast to be usable. [test case] on a bionic system, connect affected mouse and attempt to move pointer, note it moves too fast. [regression potential] as this adds a hwdb entry for a mouse using vendor/product id and name matching, any regression would likely involve incorrectly setting dpi on a different mouse than intended. [scope] fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4 which is included starting in v240, so this is already fixed in Eoan and later. This is needed only for Xenial and Bionic. [original description] Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060531 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1862232] Re: Long hostname causes networking setup to fail
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862232 Title: Long hostname causes networking setup to fail Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [impact] networkd fails to bring up networking on systems with long hostname [test case] setting the hostname: $ sudo hostnamectl set-hostname asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf then reboot and check the networking. [regression potential] as this adjusts logging and certain error handling while performing dhcp, any regression would likely cause dhcp failure. [scope] this is fixed by upstream commit a8494759b4f14af5337391727ba295ab708b92f9 (along with some associated commits around it), which is included starting in v240, so this is included already in Eoan and later. This is needed in Bionic and Xenial. [other info] the problem around this is that Linux sets HOST_NAME_MAX to 64, but RFC 1035 limits DNS labels to 63 characters, so any host with a max- length single-label hostname (i.e. a 64 character hostname with no dots) will be "valid" from Linux's perspective, but will violate RFC 1035 and thus systemd will consider it invalid and won't pass it to the dhcp server. Also note that a 64-character hostname that is *not* single-label (i.e. a hostname with at least 1 dot) will not cause this problem. The systemd patches continue to reject sending the invalid hostname to the dhcp server, but do not prevent networkd from finishing setting up networking. [original description] 1) ubuntu version # lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 2) package version # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.31 Candidate: 237-3ubuntu10.31 Version table: *** 237-3ubuntu10.31 500 500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 Packag es 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://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages 3) I expect the network to come online correctly regardless of how long the hostname is. This is what happens with both 14.0 and 19.0 (I tested the same behavior with both of them). 4) the external network interface fails to be configured and is stuck in a (pending) state as reported by networkctl status -a setting the hostname: # hostnamectl set-hostname asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf after rebooting the machine, it no longer has network access. # journalctl Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: Starting Wait for Network to be Configured... Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd-networkd[605]: eth0: Link state is up-to-date Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd-networkd[605]: eth0: found matching network '/run/systemd/network/10-netplan-eth0.network' Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd-networkd[605]: sd-netlink: callback failed: Invalid argument Feb 06 19:29:41
[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@Kai-Heng Feng (kaihengfeng) Verified. Applied the patch for regression. Bug #1876238 (duplicate of bug #1875252). Dell Inspiron 1525. URL for the patch: https://launchpad.net/~kaihengfeng/+archive/ubuntu /fix-lp1869819 Audio is working fine now. Checked rebooting multiple times. No issues now. Thank you very much. -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
I guess it would be best to confirm if it works physically on a xenial system, but then again the original bug was reported for bionic. I think this verification should be fine. -- 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/1867421 Title: Microsoft Classic IntelliMouse moves way too fast Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] Microsoft Classic IntelliMouse moves way too fast to be usable. [test case] on a bionic system, connect affected mouse and attempt to move pointer, note it moves too fast. [regression potential] as this adds a hwdb entry for a mouse using vendor/product id and name matching, any regression would likely involve incorrectly setting dpi on a different mouse than intended. [scope] fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4 which is included starting in v240, so this is already fixed in Eoan and later. This is needed only for Xenial and Bionic. [original description] Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060531 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+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] Re: systemd autopkgtest 'logind' fails when running with linux-kvm
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862657 Title: systemd autopkgtest 'logind' fails when running with linux-kvm Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released 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: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862657/+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 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks
This bug was fixed in the package systemd - 229-4ubuntu21.28
---
systemd (229-4ubuntu21.28) xenial; urgency=medium
* d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657)
* d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch:
- when restarting service after failure, replace existing queued jobs
(LP: #1839290)
* d/t/storage:
- fix buggy test (LP: #1831459)
- without scsi_debug, skip test (LP: #1847816)
* d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch:
- fix resolution of IntelliMouse (LP: #1867421)
* d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch:
- allow vacuuming journal 'root' dir (LP: #1858412)
* d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch:
- do not let invalid hostname break dhcpv4 (LP: #1862232)
* d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194)
* d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch:
- do not crash if NULL passted to journal destructor (LP: #1837914)
* d/e/initramfs-tools/hooks/udev:
- Follow symlinks when finding link files to copy into initramfs
(LP: #1868892)
-- Dan Streetman Mon, 20 Apr 2020 10:17:40
-0400
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1868892
Title:
initramfs-tools/hooks/udev for network *.link really sucks
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Eoan:
Fix Released
Status in systemd source package in Focal:
In Progress
Bug description:
[impact]
If the /{etc,lib}/systemd/network directory itself is a symlink, the find
command will not actually find any of the files in the dir it links to.
[test case]
$ sudo touch /etc/systemd/network/lp1868892.link
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
...
$ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
usr/lib/systemd/network/lp1868892.link
$ sudo mv /etc/systemd/network /etc/systemd/network.abc
$ sudo ln -s network.abc /etc/systemd/network
$ sudo update-initramfs -u
$ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
$
[regression potential]
this adjusts how link files are included in the initramfs, so
regressions would likely occur when creating new initramfs, such as
failure to create initramfs at all, or failure to properly copy link
files into the initramfs, causing network setup failure.
[scope]
this is a Debian/Ubuntu specific file, and the Debian MR was just
opened, so this is needed for Debian and all releases of Ubuntu.
[other info]
This bug likely has a very limited impact, as it is uncommon to
symlink either the /lib/systemd/network or /etc/systemd/network dirs.
[original description]
If one creates e.g. /etc/systemd/network.cu and
/etc/systemd/network.fc and symlinks /etc/systemd/network to one of
them, network setup will fail on reboot, because /usr/share/initramfs-
tools/hooks/udev does a very poor job: it simply checks for a
directory instead of the link files and therefore skips copying
required files to the ram image. Another poor job is done when copying
the files to the ram image: instead of following symlinks it copies
them as which in turn makes them useless, because it does not copy the
related dirs and thus the symlinks point to nothing. So keeping the
system in an consistent state which such poor scripts is very hard,
asking for trouble.
Suggested fix is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1868892/+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 1870194] Re: systemd-fsckd autopkgtest always fails on arm64
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1870194 Title: systemd-fsckd autopkgtest always fails on arm64 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [impact] the autopkgtest arm64 instances fail to reboot and always fail the test [test case] check autopkgtest results for arm64 instances, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz [regression potential] these tests have never successfully run on arm64, so skipping them on arm64 should have almost no regression potential; any regression would likely involve incorrectly failed test or not-run tests. [scope] this test is already skipped on arm64 starting on Eoan. This is needed only for Xenial and Bionic. [other info] related is bug 1748280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870194/+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 1877542] Re: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver
Thank you for your bug report, could you look in /var/log/dpkg.log what was updated? Could you try to start a previous kernel from the boot menu see if that makes a difference? ** Tags added: bionic ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1877542 Title: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hello, After last general update sound stops working on all interfaces. speakers, headphones nor HDMI provide any sound output even bluetooth headphones can't be connected. It seems that interface is connected to HDMI aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877542/+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 1877502] Re: package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Thank you for your bug report. The log has this error Failed to restart cups.service: Unit -.mount is masked. Did you try to change or mask some systemd units? ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/1877502 Title: package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in cups package in Ubuntu: Incomplete Bug description: I don't know to tell you about the fail. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: cups-core-drivers 2.2.12-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Fri May 8 01:15:08 2020 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2019-11-19 (170 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Inspiron 5437 Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: cups Title: package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 01PN4H dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/09/2019:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn01PN4H:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.sku: Inspiron 5437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1877502/+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 1876238] Re: [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to 20.04 LTS Focal
*** This bug is a duplicate of bug 1875252 *** https://bugs.launchpad.net/bugs/1875252 @Hui Wang (hui.wang) Verified. Applied the patch for regression by Kai-Heng Feng (kaihengfeng). Bug #1876238 (duplicate of bug #1875252). Dell Inspiron 1525. URL for the patch: https://launchpad.net/~kaihengfeng/+archive/ubuntu /fix-lp1869819 Audio is working fine now. Checked rebooting multiple times. No issues now. Thank you very much. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876238 Title: [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to 20.04 LTS Focal Status in alsa-driver package in Ubuntu: New Bug description: Internal speakers were working fine until I upgraded the system from 19.10 LTS to 20.04 LTS on April 23, 2020. Uninstalled and reinstalled alsamixer and pavucontrol, but of no use. Killed pavucontrol and reloaded alsamixer numerous times, but of no use. (`pulseaudio -k && sudo alsa force-reload`) Waited for two kernel updates, but of no use. Presently on 5.4.0-29. Tried upgrading the kernel even up to 5.6, but of no use. The Intel sound card is not getting detected. Tried every trick like adding "options snd-hda-intel dmic_detect=0" in the /etc/modprobe.d/alsa-base.conf, but of no use. Out of the two external audio output sockets for headphone, one is working. So I can either connect a headphone or an external speaker to this jack to tide over the crisis for the time being. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raj 10952 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 09:54:23 2020 InstallationDate: Installed on 2016-12-20 (1227 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raj 10952 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-26T17:25:43.583147 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876238/+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 1877540] Re: [HDA-Intel - HDA Intel, playback] volume slider problem for subwoofer
Thank you for your bug report. Do you get any error on the command line if you start gnome-control-center from there? Could you add your 'journalctl -b 0' log after getting the issue? ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1877540 Title: [HDA-Intel - HDA Intel, playback] volume slider problem for subwoofer Status in alsa-driver package in Ubuntu: Incomplete Bug description: In standard Ubuntu volume settings subwoofer level is alwas set to zero and i cant change it if i run pavucontrol and set separate levels for each channel it works, sound is working, but if i open ubuntu sound settings and touch subwoofer level control then level is instantly set to zero again once i was unable to change subwoofer level in pavucontrol while ubuntu sound settings is opened. after it is closed i can change voluve level of sub before I install pavucontrol front speaker was very quiet nearly mute also in test speakers there is no icon on subwoofer button ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-52.46-generic 5.3.18 Uname: Linux 5.3.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 8 11:00:18 2020 InstallationDate: Installed on 2018-03-04 (795 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Dell USB3.0 Dock - Dell USB3.0 Dock Symptom_PulseAudioLog: мая 08 10:26:20 tmpuser-EP43-UD3L dbus-daemon[1168]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=119 pid=1422 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") мая 08 10:26:27 tmpuser-EP43-UD3L dbus-daemon[1168]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.135' (uid=119 pid=1422 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel, playback] volume slider problem UpgradeStatus: Upgraded to eoan on 2019-11-07 (183 days ago) dmi.bios.date: 04/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: EP43-UD3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP43-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP43-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP43-UD3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877540/+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 1877532] Re: at-spi-bus-launcher does not terminate at end of X session
** Changed in: at-spi2-core (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1877532 Title: at-spi-bus-launcher does not terminate at end of X session Status in at-spi2-core package in Ubuntu: New Bug description: This concerns at-spi2-core 2.36.0-2 in Ubuntu focal. I log into the Xfce desktop as "skunk" via xrdp, and then logout. A few minutes later, "loginctl list-sessions" shows the following: SESSION UID USER SEAT TTY 9 0 root c10 1000 skunk c9 116 lightdm seat0 3 sessions listed. Output from "loginctl session-status c10": c10 - skunk (1000) Since: Fri 2020-05-08 04:03:51 EDT; 6min ago Leader: 6009 Display: :11 Service: xrdp-sesman; type x11; class user State: closing Unit: session-c10.scope ├─6184 /usr/libexec/at-spi-bus-launcher --launch-immediately └─6199 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 These two processes stick around forever until I kill them, or their parent "systemd --user" process. Only then does the session disappear from list-sessions. When I run "session-status" while I'm logged in, I see a list of about 20 desktop-related processes. All of them except these two go away on logout. These should too. (Note that this problem does not occur when I log in/out via LightDM on the console.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1877532/+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
