[Touch-packages] [Bug 1860956] Re: network-manager 1.16.0-0ubuntu2 ADT test failure with linux 5.0.0-40.44
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1860956 Title: network-manager 1.16.0-0ubuntu2 ADT test failure with linux 5.0.0-40.44 Status in network-manager package in Ubuntu: Expired Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/n/network-manager/20200124_174131_d1990@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860903] Re: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.5 failed to install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它
[Expired for unattended-upgrades (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Expired -- 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/1860903 Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.5 failed to install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它 Status in unattended-upgrades package in Ubuntu: Expired Bug description: could you help me ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.5 ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 AptOrdering: xserver-xorg-lts-utopic: Install unattended-upgrades: Configure xserver-xorg-lts-utopic: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 26 14:44:29 2020 ErrorMessage: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它 InstallationDate: Installed on 2020-01-26 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.5 failed to install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2020-01-26T11:34:12.040926 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1860903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868310] Re: configure_networking fails if dhcp provides no domain search path
This bug was fixed in the package initramfs-tools - 0.136ubuntu2 --- initramfs-tools (0.136ubuntu2) focal; urgency=medium * scripts/functions:_render_netplan(): Make configure_networking() more resilient when called by set -e scripts. LP: #1868310. -- dann frazier Fri, 20 Mar 2020 14:09:47 -0600 ** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1868310 Title: configure_networking fails if dhcp provides no domain search path Status in initramfs-tools package in Ubuntu: Fix Released Bug description: configure_networking() always returns an error for me. Using 'set -x', I observed the following at the end of a test script: + for n in $ns_addrs + '[' ', ' = '["192.168.122.1", ' ']' + continue + alist='["192.168.122.1"]' + '[' -n '' ']' + echo ' nameservers:' + echo 'addresses: ["192.168.122.1"]' + '[' -n '' ']' Which corresponds to this line of code in _render_netplan(): [ -n "$slist" ] && echo "search: $slist" I noticed that my dhcp server (default libvirt net) does not provide a domain search path, which is triggering this. If I move my VM to a network w/ a DHCP server that *does* provide this search path, it continues fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1868310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763650] Re: Suspend/Resume cycle changes advertised hostname (loss of name resolution)
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/1763650 Title: Suspend/Resume cycle changes advertised hostname (loss of name resolution) Status in avahi package in Ubuntu: Confirmed Bug description: On 16.04 and 18.04 hosts on my LAN I've been suffering intermittent loss of mDNS resolution after devices have been suspended and resumed. Today I decided to investigate and noticed that on resume the hostname being advertised is changed. E.g. hephaestion.local == Cold Boot hephaestion-1.local == 1st suspend/resume hephaestion-2.local == 2nd suspend/resume ... etc. It can be reset by restarting the service: systemctl restart avahi-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1763650/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869447] [NEW] python-is-python3 & python-is-python2 do not Provides: python
Public bug reported: This is a bug in Focal prerelease. Third-party packages like Steam currently appear to Depend: upon python, but nothing Provides: python, only Conflicts: python. I believe that python-is-... should Provide: python so that packages that expect to use /usr/bin/python aren't surprised. ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Affects: what-is-python (Ubuntu) Importance: Undecided Status: New ** Also affects: what-is-python (Ubuntu) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Also affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** No longer affects: python (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1869447 Title: python-is-python3 & python-is-python2 do not Provides: python Status in python-defaults package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in what-is-python package in Ubuntu: New Bug description: This is a bug in Focal prerelease. Third-party packages like Steam currently appear to Depend: upon python, but nothing Provides: python, only Conflicts: python. I believe that python-is-... should Provide: python so that packages that expect to use /usr/bin/python aren't surprised. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1869447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869429] Re: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 12
** Package changed: ubuntu => apparmor (Ubuntu) -- 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/1869429 Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 12 Status in apparmor package in Ubuntu: New Bug description: I was running "do-release-upgrade". It prompted me that my /etc/ssh/sshd_config file was different from the maintainers; I went to look at the differences, and somehow I wasn't able to go back and say "keep my version", instead things errored out. I was able to recover at the end of the process. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apparmor 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Fri Mar 27 20:01:57 2020 Df: Dmesg: ErrorMessage: installed apparmor package post-installation script subprocess returned error exit status 12 InstallationDate: Installed on 2017-05-04 (1057 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=9e033fda-4dfa-44ab-9f9d-2984aae489de ro quiet splash pcie_aspm=off vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: apparmor Syslog: Mar 27 18:17:18 laptopsanytime dbus[861]: [system] AppArmor D-Bus mediation is enabled Mar 27 18:20:14 laptopsanytime dbus[955]: [system] AppArmor D-Bus mediation is enabled Mar 27 18:22:56 laptopsanytime dbus[963]: [system] AppArmor D-Bus mediation is enabled Mar 27 19:02:11 laptopsanytime dbus[865]: [system] AppArmor D-Bus mediation is enabled Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 12 UpgradeStatus: Upgraded to bionic on 2020-03-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1869429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869429] [NEW] package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 12
You have been subscribed to a public bug: I was running "do-release-upgrade". It prompted me that my /etc/ssh/sshd_config file was different from the maintainers; I went to look at the differences, and somehow I wasn't able to go back and say "keep my version", instead things errored out. I was able to recover at the end of the process. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apparmor 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Fri Mar 27 20:01:57 2020 Df: Dmesg: ErrorMessage: installed apparmor package post-installation script subprocess returned error exit status 12 InstallationDate: Installed on 2017-05-04 (1057 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=9e033fda-4dfa-44ab-9f9d-2984aae489de ro quiet splash pcie_aspm=off vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: apparmor Syslog: Mar 27 18:17:18 laptopsanytime dbus[861]: [system] AppArmor D-Bus mediation is enabled Mar 27 18:20:14 laptopsanytime dbus[955]: [system] AppArmor D-Bus mediation is enabled Mar 27 18:22:56 laptopsanytime dbus[963]: [system] AppArmor D-Bus mediation is enabled Mar 27 19:02:11 laptopsanytime dbus[865]: [system] AppArmor D-Bus mediation is enabled Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 12 UpgradeStatus: Upgraded to bionic on 2020-03-27 (0 days ago) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 12 https://bugs.launchpad.net/bugs/1869429 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor 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 1839290] Re: systemd doesn't restart a service after crashes
> Dan, is there any chance of this fix landing to xenial-proposed and bionic-proposed? this is in my queue and i'm planning to gather patches for some other systemd bugs in my list starting next week. https://code.launchpad.net/~ubuntu-support-team/ubuntu/+source/systemd/+git/systemd/+ref/next-x https://code.launchpad.net/~ubuntu-support-team/ubuntu/+source/systemd/+git/systemd/+ref/next-b -- 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: In Progress Status in systemd source package in Bionic: In Progress 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. [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 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867421 Title: Microsoft Classic IntelliMouse moves way too fast 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: 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 1845319] Re: writing 'add' to /sys/devices/vio/uevent fails with ENODEV
removing myself as bug owner, as I tried to send a simple patch upstream to fix this, but was told to instead make more complex changes. As the bug isn't really that important, and systemd has been patched to ignore the kernel bug, I'm just letting it go. ** Changed in: linux (Ubuntu) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: linux (Ubuntu) Status: In Progress => New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845319 Title: writing 'add' to /sys/devices/vio/uevent fails with ENODEV Status in systemd: Fix Released Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in linux source package in Eoan: Won't Fix Status in systemd source package in Eoan: Invalid Bug description: [impact] The systemd-udev-trigger service calls 'udevadm trigger --type=devices --action=add', which writes 'add' to all /sys/devices/ uevent nodes, to re-generate their uevents sent to udev. Until systemd commit 97afc0351a96e0daa83964df33937967c75c644f, any errors during this process were simply logged to debug and ignored, but now udevadm will log errors and return failure. On ppc64el, the /sys/devices/vio device returns ENODEV when writing 'add' to its uevent, which causes the udevadm command to return failure, which causes the systemd-udev-trigger system service to fail. The kernel vio driver should be fixed to not return ENODEV. [test case] On a ppc64el system, with any systemd containing commit 97afc0351a96e0daa83964df33937967c75c644f, check the status of the systemd-udev-trigger service, to see that it's failed. Alternately, again on a ppc64el system, run as root: # echo add > /sys/devices/vio/uevent -bash: echo: write error: No such device [regression potential] the potential should be low, as this appears to have always behaved this way, at least for a while now. [other info] the systemd commit that changes udevadm to start failing for this error isn't included in any Ubuntu release yet, this is found from systemd upstream testing. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1845319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869435] [NEW] Performance regression on ubuntu focal
Public bug reported: Hello, I noticed that systmed is performin some tasks much faster in bionic than in focal, I created a script which iterates doing some operations and executed that on bionic and focal: https://paste.ubuntu.com/p/zWWQjndtXx/ I see for example how systemctl daemon reload takes more time in focal even where there are less units than in bionic results: bionic: https://paste.ubuntu.com/p/z32WScydNk/ eoan: https://paste.ubuntu.com/p/V98vd5CHwq/ focal: https://paste.ubuntu.com/p/brNjKvC2gF/ The tests was done in gce using clean instances type n1-standard-2. Please tell me if you need any extra info ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1869435 Title: Performance regression on ubuntu focal Status in systemd package in Ubuntu: New Bug description: Hello, I noticed that systmed is performin some tasks much faster in bionic than in focal, I created a script which iterates doing some operations and executed that on bionic and focal: https://paste.ubuntu.com/p/zWWQjndtXx/ I see for example how systemctl daemon reload takes more time in focal even where there are less units than in bionic results: bionic: https://paste.ubuntu.com/p/z32WScydNk/ eoan: https://paste.ubuntu.com/p/V98vd5CHwq/ focal: https://paste.ubuntu.com/p/brNjKvC2gF/ The tests was done in gce using clean instances type n1-standard-2. Please tell me if you need any extra info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
Oibaf is using the development release of Mesa. It's not released yet. Mesa 20.1 isn't scheduled for release until May. You need them to backport the fix to the 20.0.x branch. Here is the upstream issue: https://gitlab.freedesktop.org/mesa/mesa/issues/2523 You can ask there for a backport to 20.0.x. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #2523 https://gitlab.freedesktop.org/mesa/mesa/issues/2523 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869116] Re: smartctl-validate is borked in a recent release
I spoke with the LXD team and they're passing through the name they get
from the kernel. It seems like this may be a bug that was introduced to
util-linux with RAID devices. I tried running lsblk on Focal against two
NVME drives and I do not see an underscore used in model names.
@cees - Can you try using a different commissioning operating system and
see if the problem is resolved? You can download 16.04 and 20.04 on the
images page and then change the commissioning operating system on the
settings page.
** Also affects: util-linux-ng
Importance: Undecided
Status: New
** No longer affects: util-linux-ng
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status in lxd:
Unknown
Status in MAAS:
Triaged
Status in util-linux package in Ubuntu:
New
Bug description:
Bug (maybe?) details first, diatribe second.
Bug Summary: multi-hdd / raid with multiple drives / multiple devices
or something along those lines cannot be commissioned anymore: 2.4.x
worked fine, 2.7.0 does not.
Here is the script output of smartctl-validate:
-
# /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66c9220df4ac' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters:
{'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i',
'name': 'sda', 'physical_blockdevice_id': 33, 'serial':
'6842b2b0740e9900260e66c9220df4ac'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
-
# /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66f924ecece0' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters: {'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i',
'name': 'sdb', 'physical_blockdevice_id': 34, 'serial':
'6842b2b0740e9900260e66f924ecece0'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
You can see that it says the storage cannot be found and immediately
lists it as a discovered device. It does it for both tests (one for
each drive), and for both servers
Bug Details:
I had maas 2.4.x for the longest time over my journey (see below journey) and
have never had any problems re-commissioning (or deleting and re-discovering
over boot PXE) 2 of my servers (r610, r710).
r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual
disk.
r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks
So commission after commission trying to get through my journey, 0
problems. After I finally get everything figured out on the juju,
network/vlan, quad-nic end, I go to re-commission and I cannot.
smartctl-validate fails on both, over and over again. I even destroyed
and re-created the raid/VDs, still not.
After spending so much time on it I remembered that it was the first
time I had tried to re-commission these two servers since doing an
upgrade from 2.4.x->2.7 in an effort to use the updated KVM
integration to add a couple more guests. Once I got all everything
figured out I went to re-commission everything and boom.
[Upgrade path notes]
In full disclosure, in case this matters. I was on apt install of 2.4.x and
using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and
did that and did not
[Touch-packages] [Bug 1867090] Re: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap
Thanks! ** Also affects: snappy Importance: Undecided Status: New ** No longer affects: snappy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1867090 Title: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap Status in ibus package in Ubuntu: Confirmed Bug description: OS: Ubuntu 19.10 IBus version: 1.5.21 Atom version: 1.45.0 When I switch to Chinese input mode (Intelligent Pinyin) and try to type Chinese into Atom 1.45.0 (snap version), it simply doesn't work. When I type the letters into the window, it shall bring up the candidate list for me to pick words. But instead, the letters are directly typed into the window, but not Chinese characters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557739] Re: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device')
** Tags added: focal ** Tags removed: focal ** Tags added: rls-ff-incoming -- 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/1557739 Title: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device') Status in apport package in Ubuntu: Confirmed Bug description: While running through the install, ubiquity crashed, then apport crashed so couldn't file a bug on ubiquity. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.367 CrashReports: 640:999:999:18776:2016-03-15 16:19:14.974973678 -0400:2016-03-15 16:19:15.974973678 -0400:/var/crash/_usr_bin_apport-bug.999.crash Date: Tue Mar 15 16:19:15 2016 ExecutablePath: /usr/bin/apport-bug InterpreterPath: /usr/bin/python3.5 LiveMediaBuild: Xubuntu Core 16.04 - amd64 - 20160314 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli ubiquity ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/apport-bug', 'ubiquity'] SourcePackage: apport Title: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device') 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/apport/+bug/1557739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869414] [NEW] Running applications always appear on the desktop
Public bug reported: Ubuntu 20.04 No matter which virtual desktop is in focus, applications running on other virtual desktop are displayed even if minimized. This makes it impossible to interact with desktop icons without closing all running applications. It is not possible to interact with the application itself when it's displayed erroneously, unless you return to its original virtual desktop. I've reinstalled from two different daily images and have been able to reproduce the problem each time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:22:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1458:2311] InstallationDate: Installed on 2020-03-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) MachineType: System76 Thelio ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_4u488c@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_4u488c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: System76 dmi.bios.version: F42a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF42aZ5:bd08/22/2019:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible 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/1869414 Title: Running applications always appear on the desktop Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.04 No matter which virtual desktop is in focus, applications running on other virtual desktop are displayed even if minimized. This makes it impossible to interact with desktop icons without closing all running applications. It is not possible to interact with the application itself when it's displayed erroneously, unless you return to its original virtual desktop. I've reinstalled from two different daily images and have been able to reproduce the problem each time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:22:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1458:2311] InstallationDate: Installed on 2020-03-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) MachineType: System76 Thelio ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_4u488c@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_4u488c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
** Changed in: sudo (Ubuntu Disco) Status: In Progress => Won't Fix ** Changed in: sudo (Ubuntu Cosmic) Status: In Progress => Won't Fix ** Changed in: sudo (Ubuntu Bionic) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: sudo (Ubuntu Xenial) Assignee: Dan Streetman (ddstreet) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in Release Notes for Ubuntu: New Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: In Progress Status in sudo source package in Bionic: In Progress Status in sudo source package in Cosmic: Won't Fix Status in sudo source package in Disco: Won't Fix Status in sudo source package in Eoan: Fix Released Bug description: [impact] sudo does not set HOME to the target user's HOME [test case] ddstreet@thorin:~$ sudo printenv | grep HOME HOME=/home/ddstreet [regression potential] this is a significant behavior change. As mentioned in comment 11 (and later, and other bugs duped to this, and the mailing list discussion, etc) users of Ubuntu so far have been used to running sudo with their own HOME set, not root's HOME. Therefore, it's inappropriate to change this behavior for existing releases; this should be changed starting in Eoan, and only the sudo and sudoers man pages changed in previous releases to indicate the actual behavior of sudo in those releases. [other info] Shortly after upstream changed the behavior, the patch to keep HOME as the calling (instead of target) user was added in bug 760140. For quick reference to anyone coming to this bug, the pre-19.10 behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home or, run sudo with the -H param. -- original description: -- I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1556302/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Changed in: autopkgtest-cloud
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/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:
In Progress
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 1867090] Re: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap
Reported to GitHub: https://github.com/snapcrafters/atom/issues/53 ** Description changed: - When I switch to Chinese input mode (Intelligent Pinyin) and try to type Chinese into Atom 1.45.0, it simply doesn't work. + OS: Ubuntu 19.10 + IBus version: 1.5.21 + Atom version: 1.45.0 + + When I switch to Chinese input mode (Intelligent Pinyin) and try to type Chinese into Atom 1.45.0 (snap version), it simply doesn't work. When I type the letters into the window, it shall bring up the candidate list for me to pick words. But instead, the letters are directly typed into the window, but not Chinese characters. ** Bug watch added: github.com/snapcrafters/atom/issues #53 https://github.com/snapcrafters/atom/issues/53 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1867090 Title: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap Status in ibus package in Ubuntu: Confirmed Bug description: OS: Ubuntu 19.10 IBus version: 1.5.21 Atom version: 1.45.0 When I switch to Chinese input mode (Intelligent Pinyin) and try to type Chinese into Atom 1.45.0 (snap version), it simply doesn't work. When I type the letters into the window, it shall bring up the candidate list for me to pick words. But instead, the letters are directly typed into the window, but not Chinese characters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Facing the same problem with an HP Spectre X360, I tested several distributions and several different kernel versions. I also followed several guides explaining how the problem could be solved, but none worked for me. What I find curious is that in Ubuntu 19.10 and 20.04 in live mode the microphone works perfectly (both internal and the headset). I copied the contents of the alsa-base.conf file from live and overwrote that of the distribution, but it also didn't work. Tested with kernel: 5.0x, 5.3.x, 5.4.x, 5.5x (family 4.x bring other problems for my hardware) I was also able to use an external microphone using a USB adapter. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() Status in glib2.0 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9 --- Happened during normal use of the desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 19:51:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-01-25 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax PC (0x7f5f54fa6444) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765649] Re: package libpng12-0 1.2.54-1ubuntu1 [modified: usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz usr/share/doc/li
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libpng (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpng in Ubuntu. https://bugs.launchpad.net/bugs/1765649 Title: package libpng12-0 1.2.54-1ubuntu1 [modified: usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz usr/share/doc/libpng12-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/KNOWNBUG', which is different from other instances of package libpng12-0:i386 Status in libpng package in Ubuntu: Confirmed Bug description: This bug appeared when I was trying to install teamviewer which doesn't work. There are some dependencies that break the installation. Then I tried to remove teamviewer: sudo apt-get remove teamviewer Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: libpng12-0 : Breaks: libpng12-0:i386 (!= 1.2.54-1ubuntu1) but 1.2.50-2+deb8u3 is to be installed libpng12-0:i386 : Depends: libc6:i386 (>= 2.11) but it is not going to be installed Depends: zlib1g:i386 (>= 1:1.1.4) but it is not going to be installed Breaks: libpng12-0 (!= 1.2.50-2+deb8u3) but 1.2.54-1ubuntu1 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). Then as suggested I tried: sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: gcc-6-base:i386 libc6:i386 libgcc1:i386 libpng12-0:i386 zlib1g:i386 Suggested packages: glibc-doc:i386 locales:i386 The following packages will be REMOVED: teamviewer The following NEW packages will be installed: gcc-6-base:i386 libc6:i386 libgcc1:i386 zlib1g:i386 The following packages will be upgraded: libpng12-0:i386 1 upgraded, 4 newly installed, 1 to remove and 210 not upgraded. 3 not fully installed or removed. Need to get 2.501 kB of archives. After this operation, 142 MB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 gcc-6-base i386 6.0.1-0ubuntu1 [14,3 kB] Get:2 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 libgcc1 i386 1:6.0.1-0ubuntu1 [46,8 kB] Get:3 http://ro.archive.ubuntu.com/ubuntu xenial-updates/main i386 libc6 i386 2.23-0ubuntu10 [2.266 kB] Get:4 http://ro.archive.ubuntu.com/ubuntu xenial-updates/main i386 zlib1g i386 1:1.2.8.dfsg-2ubuntu4.1 [52,1 kB] Get:5 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 libpng12-0 i386 1.2.54-1ubuntu1 [122 kB] Fetched 2.501 kB in 0s (4.625 kB/s) Preconfiguring packages ... (Reading database ... 253717 files and directories currently installed.) Removing teamviewer (12.0.93330) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ... Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.59ubuntu1) ... (Reading database ... 253416 files and directories currently installed.) Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1_i386.deb ... Unpacking libpng12-0:i386 (1.2.54-1ubuntu1) over (1.2.50-2+deb8u3) ... dpkg: error processing archive /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libpng12-0/KNOWNBUG', which is different from other instances of package libpng12-0:i386 Selecting previously unselected package gcc-6-base:i386. Preparing to unpack .../gcc-6-base_6.0.1-0ubuntu1_i386.deb ... Unpacking gcc-6-base:i386 (6.0.1-0ubuntu1) ... Selecting previously unselected package libgcc1:i386. Preparing to unpack .../libgcc1_1%3a6.0.1-0ubuntu1_i386.deb ... Unpacking libgcc1:i386 (1:6.0.1-0ubuntu1) ... Selecting previously unselected package libc6:i386. Preparing to unpack .../libc6_2.23-0ubuntu10_i386.deb ... Unpacking libc6:i386 (2.23-0ubuntu10) ... Replacing files in old package libc6-i386 (2.23-0ubuntu10) ... Selecting previously unselected package zlib1g:i386. Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_i386.deb ... Unpacking zlib1g:i386 (1:1.2.8.dfsg-2ubuntu4.1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Errors were encountered while processing: /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_i386.deb E: Sub-process /usr/bin/dpkg returned an error
[Touch-packages] [Bug 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
This, apport/2.20.9-0ubuntu7.13 (i386), has passed after a retest. -- 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/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: Fix Released Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Regression Potential The fix is just setting the value of a variable to True instead of checking to see if whoopsie is enabled so there really isn't any. However, it could cause a regression if there's a typo in the line being changed. Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869393] [NEW] avahi-browse -kprtf _apt_proxy._tcp does not show any output, but the server is actually alive
Public bug reported: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Have `squid-deb-proxy` on the same local network 3. Install `squid-deb-proxy-client` package on 20.04 LTS 4. Monitor logs of `squid-deb-proxy` server with tail 5. Run any `apt-get` `install`/`download`/`upgrade`/`update` on 20.04 LTS client system with Expected results: * 20.04 LTS client system uses `squid-deb-proxy` server via `squid-deb-proxy-client` package Actual results: * the avahi-browse does not work, so packages are downloaded directly from Ubuntu mirrors instead of `squid-deb-proxy` Debug: * the command `avahi-browse -kprtf _apt_proxy._tcp` which is called by `/usr/share/squid-deb-proxy-client/apt-avahi-discover` does not return any output on 20.04 LTS client. Other clients - 16.04 LTS and 19.10 have normal command output for this command. Notes: * avahi-discover GUI window is empty too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: avahi-utils 0.7-4ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 27 19:25:45 2020 InstallationDate: Installed on 2020-03-25 (2 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (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 avahi in Ubuntu. https://bugs.launchpad.net/bugs/1869393 Title: avahi-browse -kprtf _apt_proxy._tcp does not show any output, but the server is actually alive Status in avahi package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Have `squid-deb-proxy` on the same local network 3. Install `squid-deb-proxy-client` package on 20.04 LTS 4. Monitor logs of `squid-deb-proxy` server with tail 5. Run any `apt-get` `install`/`download`/`upgrade`/`update` on 20.04 LTS client system with Expected results: * 20.04 LTS client system uses `squid-deb-proxy` server via `squid-deb-proxy-client` package Actual results: * the avahi-browse does not work, so packages are downloaded directly from Ubuntu mirrors instead of `squid-deb-proxy` Debug: * the command `avahi-browse -kprtf _apt_proxy._tcp` which is called by `/usr/share/squid-deb-proxy-client/apt-avahi-discover` does not return any output on 20.04 LTS client. Other clients - 16.04 LTS and 19.10 have normal command output for this command. Notes: * avahi-discover GUI window is empty too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: avahi-utils 0.7-4ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 27 19:25:45 2020 InstallationDate: Installed on 2020-03-25 (2 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1869393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867157] Re: Improve command-not-found package headers
This bug was fixed in the package python-defaults - 2.7.17-2ubuntu4 --- python-defaults (2.7.17-2ubuntu4) focal; urgency=medium * Correct command-not-found XB-Cnf headers LP: #1867157: - Drop Extra-Commands headers, not needed - Add XB- to ensure Visible-Pkgname actually is included in the binary package heders -- Dimitri John Ledkov Fri, 13 Mar 2020 12:31:23 + ** Changed in: python-defaults (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1867157 Title: Improve command-not-found package headers Status in python-defaults package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in python3.8 package in Ubuntu: Fix Released Bug description: Improve command-not-found package headers command-not-found uses package metadata, and to improve the UX of the misspelled commands / proposed packages. python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7 python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8 python2-minimal should gain XB-Cnf-Visible-Pkgname: python2 python3-minimal should gain XB-Cnf-Visible-Pkgname: python3 This will then improve these messages from: """ command 'python2.7' from deb python2.7-minimal (2.7.17-1) command 'python3.8' from deb python3.8-minimal (3.8.0-5) command 'python2' from deb python2-minimal (2.7.17-2) command 'python3' from deb python3-minimal (3.7.5-1ubuntu1) """ To """ command 'python2.7' from deb python2.7 (2.7.17-1) command 'python3.8' from deb python3.8 (3.8.0-5) command 'python2' from deb python2 (2.7.17-2) command 'python3' from deb python3 (3.7.5-1ubuntu1) """ python3 should drop XB-Cnf-Extra-Commands: python XB-Cnf-Priority-Bonus: 5 Such that it stops suggesting that somehow python is available from python3 package, which is a lie. There is a special case for "python" command hint in command-not-found already, which simply points people to "python3". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1867157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)
So, I've upgraded my main OS (Xubuntu 18.04) to 5.3.0-42-generic, and now, it's partially suffering from the mute-toggle issue. The computer mutes or unmutes whenever something happens that produces sound (e.g., when a messenger app gives a notification, when I pause/play a video, etc), and it gives that sound through the speakers when it does (as I've recorded in the video, linked in the first post). Is there anything else I can test and/or try for you guys to gather more information? -- 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/1866681 Title: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+) Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp- pavilion-dv9000/specs/) built many years ago. Whenever I'm using any distro that's based on Ubuntu which was published from Version 19.04 onwards, I've been having a major issue with the mute button toggling on and off whenever I have something plugged into the audio out jack. I know that it's not the fault of XFCE, because I also use the latest version of Manjaro with XFCE on this same computer, and it works fine. I also know it's not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 6) also on this exact same computer, and it also works fine. Qubes, Mageia, and Fedora 31 also work perfectly fine and don't have this issue. My "lsb-release" is: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.10 DISTRIB_CODENAME=eoan DISTRIB_DESCRIPTION="Ubuntu 19.10" and "apt-cache policy pulseaudio" outputs: pulseaudio: Installed: 1:13.0-1ubuntu1.1 Candidate: 1:13.0-1ubuntu1.1 Version table: *** 1:13.0-1ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages I've uploaded a short video of the problem that I recorded with my phone here: https://www.youtube.com/watch?v=GXaHXQA-5uQ The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, Xubuntu 19.04, and Sparky 5.10 and 2020.02. I've checked pretty much everything I can think of. There's a log for my ALSA help diagnostics results on my current computer (which works properly with 18.04) at: http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829 the result output of lspci is: [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2) 00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3) 00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3) 00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1) 00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1) 00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1) 00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g WLAN (rev 01) 05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] (rev a1) 07:05.0
[Touch-packages] [Bug 1869368] Re: ubuntu_qrt_apparmor fails on ADT bionic/linux i386
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: qa-regression-testing Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1869368 Title: ubuntu_qrt_apparmor fails on ADT bionic/linux i386 Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in apparmor source package in Bionic: New Status in linux source package in Bionic: Confirmed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz Kernel version: bionic/linux 4.15.0-94.95 The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on bionic/linux i386 ADT tests. It has failed some releases in the past and I'm seeing the failure in the current release as well. I have not seen this failure on other architectures. These are the last messages on the test log: 20:12:39 ERROR| [stderr] Test mediation of file based SOCK_STREAM connect ... ok 20:12:39 ERROR| [stderr] test_libapparmor_testsuite (__main__.ApparmorTestsuites) 20:14:18 DEBUG| [stdout] unconfined_user can access confined_user's file 20:14:18 DEBUG| [stdout] unconfined_user can access default_user's file 20:14:18 DEBUG| [stdout] unconfined_user can access unconfined_group's file 20:14:18 DEBUG| [stdout] 20:15:42 ERROR| [stderr] Run libapparmor testsuite ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:15:42 ERROR| [stderr] test_libapparmor_testsuite3 (__main__.ApparmorTestsuites) 20:15:52 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:15:52 DEBUG| [stdout] 20:17:10 ERROR| [stderr] Run libapparmor testsuite (with python3) ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:17:10 ERROR| [stderr] test_old_trusty_parser_testsuite (__main__.ApparmorTestsuites) 20:17:10 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:17:10 ERROR| [stderr] Run parser regression tests from 14.04's apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 systems with the apparmor 2.10.95 SRU or newer installed) ok 20:17:10 ERROR| [stderr] test_old_trusty_regression_testsuite (__main__.ApparmorTestsuites) 20:17:10 ERROR| [stderr] Run kernel regression tests from 14.04's apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 systems with the apparmor 2.10.95 SRU or newer installed) ok 20:17:10 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites) 20:17:19 DEBUG| [stdout] 20:52:35 ERROR| [stderr] Run parser regression tests ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:52:35 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites) 20:52:42 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:52:42 DEBUG| [stdout] 21:01:56 INFO | ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1585256516localtime=Mar 26 21:01:56 Test subprocess failed rc=9 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1869368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
How to find out who submitted this code that broke the system? I wonder weather this is intentional by competitors -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1867408] Re: openssh 8.2 waiting on libfido2 MIR
Almost there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1867408 Title: openssh 8.2 waiting on libfido2 MIR Status in openssh package in Ubuntu: New Bug description: See libfido MIR https://bugs.launchpad.net/ubuntu/+source/libfido2/+bug/1864439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1867408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
This bug was fixed in the package console-setup - 1.194ubuntu3 --- console-setup (1.194ubuntu3) focal; urgency=medium [ Mantas Kriaučiūnas ] * keyboard-configuration.config:: replace not intuitive second lt(us) layout with us(altgr-intl), which contains Euro (€) and other symbols, often used in Lithuania. (lp: #1863001) -- Sebastien Bacher Fri, 27 Mar 2020 11:10:06 +0100 ** Changed in: console-setup (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: Fix Released Status in console-setup package in Debian: Unknown Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I have an Asus laptop with an internal mic. I have Ubuntu 19.10 on it and the mic will not work. I've tried everything I can think of but with no luck:( Somebody please fix this. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
This looks more a glib issue as the code in this shell utility didn't really change in the past. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() Status in glib2.0 package in Ubuntu: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9 --- Happened during normal use of the desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 19:51:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-01-25 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax PC (0x7f5f54fa6444) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends
Or did you mean adding the chrome-gnome-shell as a dependency for GNOME Extensions after this app is moved to a separate package (as noted in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1867345/comments/2)? -- 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/1866841 Title: Add chrome-gnome-shell to ubuntu-desktop recommends Status in One Hundred Papercuts: Opinion Status in chrome-gnome-shell package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Please, consider adding the chrome-gnome-shell package as a recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The chrome-gnome-shell package provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers that is necessary for users to be able to manage GNOME Shell extensions using a extensions.gnome.org website. Since the Shell Extensions support was removed from gnome-software since 3.36 and the replacement Extensions application cannot be used to find and install new extensions, there is not any user friendly way to install new Shell Extensions without having the chrome-gnome-shell package installed. More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
build worked after a retry... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: Fix Committed Status in console-setup package in Debian: Unknown Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
** Bug watch added: Debian Bug tracker #951387 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951387 ** Also affects: console-setup (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951387 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: Fix Committed Status in console-setup package in Debian: Unknown Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868927] Re: FFe: Sync shared-mime-info 1.15-1 (main) from Debian unstable (main)
This bug was fixed in the package shared-mime-info - 1.15-1 Sponsored for Amr Ibrahim (amribrahim1987) --- shared-mime-info (1.15-1) unstable; urgency=medium * New upstream release. Closes: #954669. * Update watch file for gitlab.freedesktop.org. * Update build-dependencies. * Remove ancient patches changing the magic database. Those should be reported upstream if they're still present. * Switch to debhelper-compat and bump compat to 12. * Don't hardcode full command path in postinst. -- Emilio Pozuelo Monfort Tue, 24 Mar 2020 16:58:21 +0100 ** Changed in: shared-mime-info (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1868927 Title: FFe: Sync shared-mime-info 1.15-1 (main) from Debian unstable (main) Status in shared-mime-info package in Ubuntu: Fix Released Bug description: Please sync shared-mime-info 1.15-1 (main) from Debian unstable (main) NEWS: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/blob/master/NEWS shared-mime-info 1.15 (2019-30-10) * Add Kindle 8 eBook format * Fix some HTML files being detected as XML shared-mime-info 1.14 (2019-20-09) * Add mime-type for QCOW images * Fix matching SVG files in some circumstances (again) shared-mime-info 1.13.1 (2019-11-09) * Fix matching SVG files in some circumstances shared-mime-info 1.13 (2019-11-09) * Add code of conduct document * Use itstool and gettext to generate translations * Add content-tree type for OSTree USB repositories * Add match for MPEG-4 v1 videos * Adjust a lot of user readable mime-type descriptions * Fix WOFF/WOFF2 mime-types * Prefer text/html to XHTML for *.html files * Better magic for text/html files * Fix SVG magic for files embedded in HTML * Add *.sgd as a glob for Mega Drive ROMs Specification: - Mention that sub-class-of can be aliases Tools: - Enable Large File Support in update-mime-database Test suite: - Make test suite failures fatal - Add test for duplicate mime-types - Fix WarpScript test - Generate the specification in the CI, to avoid it becoming syntactically invalid shared-mime-info 1.12 (2019-17-01) * Fix build from tarball shared-mime-info 1.11 (2019-17-01) * Add mime-type for reStructuredText * Add mime-type for Groovy scripting language * Add mime-type for Gradle build tool * Add mime-type for Maven * Add mime-type for WarpScript source code * Add mime-type for zstd and tar.zst archives * Change the preferred suffix for image/jpeg from .jpeg to .jpg * Assign *.html to XHTML pages * Better detection for *.key files (Apple Keynote vs. GPG keys) * Give weight to one of the appimage patterns Tools: - Link to GitLab for contributions and bug reports - Loads of memory and file descriptor leak fixes Spec: - Clarify the availability of C character escape support Explanation of FeatureFreeze exception: New mime-type's and improvements to the existing ones useful for the life of the new LTS. The current version 1.10 has not been updated since September 2018. Changelog entries since current focal version 1.10-1: shared-mime-info (1.15-1) unstable; urgency=medium * New upstream release. Closes: #954669. * Update watch file for gitlab.freedesktop.org. * Update build-dependencies. * Remove ancient patches changing the magic database. Those should be reported upstream if they're still present. * Switch to debhelper-compat and bump compat to 12. * Don't hardcode full command path in postinst. -- Emilio Pozuelo Monfort Tue, 24 Mar 2020 16:58:21 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1868927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
I've uploaded to focal but the build is failing :/ https://launchpadlibrarian.net/470959763/buildlog_ubuntu-focal-amd64 .console-setup_1.194ubuntu3_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: Fix Committed Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
** Changed in: console-setup (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: Fix Committed Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859246] Re: Built in audio speakers/earphones + microphone + SPDIF not activated.
For kernel 5.5.x I also found https://github.com/thesofproject/linux/issues/1917 ** Bug watch added: github.com/thesofproject/linux/issues #1917 https://github.com/thesofproject/linux/issues/1917 -- 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/1859246 Title: Built in audio speakers/earphones + microphone + SPDIF not activated. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Only audio through HDMI activated and working. Ubuntu is 20.04 LTS, but issue with audio is the same independent of Ubuntu release in use. See created alsa-information script through link: http://alsa-project.org/db/?f=c5f459dfb6183f1cd98f8a0bfd649a98869f009a Shorted below: !Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b10 irq 145 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) !!Loaded sound module options !!--- !!Module: snd_hda_intel !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Intel Kabylake HDMI Address: 2 APLAY *** List of PLAYBACK Hardware Devices *** 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/1859246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866890] Re: audio card not detected after upgrade to 20.04 (Only Dummy Output appears)
*** This bug is a duplicate of bug 1860697 *** https://bugs.launchpad.net/bugs/1860697 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1866890 Title: audio card not detected after upgrade to 20.04 (Only Dummy Output appears) Status in alsa-driver package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04 the sound card is no longer detected. This means that I can only see "Dummy Output" in the sound settings. The audio works if I use Bluetooth headphones but not if I try to use the speakers or the 3.5mm headphone jack. My machine is a Lenovo ThinkPad X1 Yoga (4th gen). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856376] Re: "Dummy Output" -- built-in audio not detected
I have apparently the same issue on my Lenovo X1 4th gen since recent upgrade: lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) (prog-if 80) Subsystem: Lenovo Cannon Point-LP High Definition Audio Controller Flags: bus master, fast devsel, latency 64, IRQ 16 Memory at ea33c000 (64-bit, non-prefetchable) [size=16K] Memory at ea00 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: snd_soc_skl Kernel modules: snd_hda_intel, snd_soc_skl, sof_pci_dev lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1856376 Title: "Dummy Output" -- built-in audio not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: I no longer seem to be getting audio on my laptop, and only "Dummy Output" shows up in the sound settings dialog. This sounds similar to LP #1781294 (including the same PCI device), though that seems to have been marked expired. alex@tapada:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Lenovo Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 64, IRQ 159 Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K] Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl alex@tapada:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 23:38:35 2019 InstallationDate: Installed on 2019-08-31 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867157] Re: Improve command-not-found package headers
This bug was fixed in the package python2.7 - 2.7.17-1ubuntu6 --- python2.7 (2.7.17-1ubuntu6) focal; urgency=medium * Add XB-Cnf-Visible-Pkgname header on the python*-minimal package to point command-not-found at the full one. LP: #1867157 -- Dimitri John Ledkov Fri, 13 Mar 2020 12:42:15 + ** Changed in: python2.7 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1867157 Title: Improve command-not-found package headers Status in python-defaults package in Ubuntu: New Status in python2.7 package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in python3.8 package in Ubuntu: Fix Released Bug description: Improve command-not-found package headers command-not-found uses package metadata, and to improve the UX of the misspelled commands / proposed packages. python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7 python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8 python2-minimal should gain XB-Cnf-Visible-Pkgname: python2 python3-minimal should gain XB-Cnf-Visible-Pkgname: python3 This will then improve these messages from: """ command 'python2.7' from deb python2.7-minimal (2.7.17-1) command 'python3.8' from deb python3.8-minimal (3.8.0-5) command 'python2' from deb python2-minimal (2.7.17-2) command 'python3' from deb python3-minimal (3.7.5-1ubuntu1) """ To """ command 'python2.7' from deb python2.7 (2.7.17-1) command 'python3.8' from deb python3.8 (3.8.0-5) command 'python2' from deb python2 (2.7.17-2) command 'python3' from deb python3 (3.7.5-1ubuntu1) """ python3 should drop XB-Cnf-Extra-Commands: python XB-Cnf-Priority-Bonus: 5 Such that it stops suggesting that somehow python is available from python3 package, which is a lie. There is a special case for "python" command hint in command-not-found already, which simply points people to "python3". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1867157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859246] Re: Built in audio speakers/earphones + microphone + SPDIF not activated.
I don't know if https://askubuntu.com/questions/1213271/microphone-does- not-work-on-new-dell-inspiron-7590/1220414#1220414 is helpful. It is my post on "ask ubuntu" to help others, as I managed to make sound working on my laptop. Notes 1) Sound is working using sof 2) sof configuration files are not in master branch of github:thesofproject/alsa-ucm-conf 3) 5.3.0-42, breaks sof again. 4) https://github.com/thesofproject/linux/issues/1877 here a discussion is opened for the 5.3.0-42 issues also. I'm new to all these but if I can help in any way I can try. ** Bug watch added: github.com/thesofproject/linux/issues #1877 https://github.com/thesofproject/linux/issues/1877 -- 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/1859246 Title: Built in audio speakers/earphones + microphone + SPDIF not activated. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Only audio through HDMI activated and working. Ubuntu is 20.04 LTS, but issue with audio is the same independent of Ubuntu release in use. See created alsa-information script through link: http://alsa-project.org/db/?f=c5f459dfb6183f1cd98f8a0bfd649a98869f009a Shorted below: !Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b10 irq 145 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) !!Loaded sound module options !!--- !!Module: snd_hda_intel !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Intel Kabylake HDMI Address: 2 APLAY *** List of PLAYBACK Hardware Devices *** 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/1859246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869330] [NEW] Hangs after eoan -> focal release upgrade on shutdown
Public bug reported: Hi, I upgraded one of my machines from eoan to focal today and the reboot after the upgrade hang with: ``` A stop job s running for Service for snap application lxd.daemon (xxx / 10min) ``` Attached is the output of "sudo journalctl -u snap.lxd.daemon.service" This machines does not use lxd heavily but it does have a running snapcraft-core20-test container ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl.lxd.daemon.service" https://bugs.launchpad.net/bugs/1869330/+attachment/5342064/+files/journalctl.lxd.daemon.service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1869330 Title: Hangs after eoan -> focal release upgrade on shutdown Status in lxc package in Ubuntu: New Bug description: Hi, I upgraded one of my machines from eoan to focal today and the reboot after the upgrade hang with: ``` A stop job s running for Service for snap application lxd.daemon (xxx / 10min) ``` Attached is the output of "sudo journalctl -u snap.lxd.daemon.service" This machines does not use lxd heavily but it does have a running snapcraft-core20-test container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1869330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869304] Re: Video Card Intel Not being used
I can see two separate issues in the logs: 1. Xorg crashed inside the radeon X driver. 2. The kernel crashed inside the intel kernel driver. It's unlikely that "Intel is not being used" because the logs seem to show that it is. We should focus on one problem per bug report so let's look at "Laptop was draining battery too fast". While the problem is happening, please run 'top', then maximize the window, take a screenshot and attach it here. Separately please check your system for crash reports and create new bugs for those: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - Video Card Intel Not being used + Laptop draining battery too fast ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1869304 Title: Laptop draining battery too fast Status in Ubuntu: Incomplete Bug description: Laptop was draining battery too fast, checked for Video Card Updates, Intel is not being used. Tried Xorg, it says fault packages are being held. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 11:07:15 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1028:078b] InstallationDate: Installed on 2020-03-23 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a05 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15-3567 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=7a4ba4e2-af26-42b5-b4bf-852d8f4e530b ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 0765NJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.0:bd05/10/2019:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0765NJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1869304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
