[Touch-packages] [Bug 1872016] Re: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
There is no bug in the glibc/expat dependencies here. The libexpat1 in bionic Depends: libc6 (>= 2.25), which is the version that provides this symbol. The problem is that new libexpat1 has been unpacked (but not configured) before the new libc6, so anything which depends on libexpat1 does not have its dependencies satisfied, and the xenial version of gir1.2-ibus-1.0 appears to invoke python3 in its prerm script, which fails. I'm not sure if it's possible for apt to fix this, or if it would need to be fixed in the gir1.2-ibus-1.0 maintainer script to handle the case where py3clean is executable but fails. Of course this maintainer script is also generated by dh_python3, so fixing it might take a bit of effort. -- 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/1872016 Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in glibc package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1872016/+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 1872016] Re: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Also affects: ibus (Ubuntu) Importance: Undecided Status: New -- 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/1872016 Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in glibc package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1872016/+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 986779] Re: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis)
No such feature seen yet on Focal version of ubuntu-bug either. ** Tags added: focal ** Changed in: apport (Ubuntu) Status: Incomplete => Confirmed -- 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/986779 Title: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis) Status in apport package in Ubuntu: Confirmed Bug description: Wishlist: When ubuntu-bug is asked to send a bug on PID, it should check whether the PID shows symptoms of being in an infinite loop and if so, include stack trace of the process to the bug report or ask the user whether he would like to include details needed for retracing in the bug report. In many cases simply sending SEGV signal to the process does indeed manage to generate retraceable coredumps when /proc/sys/kernel/core_pattern points to apport, but such SEGVs can be masked for several reasons. Bug 986774 is an example of a bug report which would benefit from having this kind of feature in apport/ubuntu-bug - in that case pasuspender seems to be masking the apport SEGV handling. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apport 2.0.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 22 10:01:02 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120112) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IE:en TERM=xterm PATH=(custom, no user) LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/986779/+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 1870811] Re: compile auto test failure, and root-unittest failure, is extremely noisy
** Changed in: systemd (Ubuntu Xenial) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1870811 Title: compile auto test failure, and root-unittest failure, is extremely noisy Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build, e.g. https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] Xenial does not use meson, so can not be adjusted. This is needed in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes
** Description changed: [impact] when a service configured to restart crashes, under certain configurations, that service is not correctly restarted. [test case] see comment 8 [regression potential] this changes the job mode of manager-triggered restarts to 'replace' any existing queued job(s), instead of failing if there are queued job(s). thus any regressions would occur when a service fails, that is configured to restart on failure. [scope] This is needed only for Xenial and Bionic. this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51 which is included already in Eoan. + + Fixed in Disco with the backported v240 patch from + https://github.com/systemd/systemd/commit/677b4cc753f183731fc54fcb68ad46f806c394bc [other info] original description: --- Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. -- 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. Fixed in Disco with the backported v240 patch from https://github.com/systemd/systemd/commit/677b4cc753f183731fc54fcb68ad46f806c394bc [other info] original description: --- Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871916] Re: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu
Not reproducible on fresh install on same hardware. -- 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/1871916 Title: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu Status in xorg package in Ubuntu: New Bug description: Installed (upgraded 16->18->20 beta) ubuntu appears to utilize incorrect x.org drivers for RX 5500 XT. Those drivers appear to be missing features like multi-monitor support. On the other hand live- usb of 20.04 beta did manage to utilize all 3 connected monitors (before crashing), so the issue may also be related to upgrading process (used do-release-upgrade since update-managed does not scale down to 800x600 fallback which 18.04 used with unsupported hardware). Yes, this report is in need of some triaging, unless it happens to be a clear duplicate of another bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 22:01:36 2020 DistUpgraded: 2020-04-09 04:40:21,578 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.132, 5.3.0-46-generic, x86_64: installed nvidia, 390.132, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2016-09-25 (1292 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=4ae0053b-f333-4800-b242-42a9efca3dde ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago) XorgConf: Section "Device" Identifier "AMD" Driver "amdgpu" EndSection dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 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 N/A 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 xserver.bootTime: Thu Apr 9 04:46:16 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.7-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes
** Bug watch removed: github.com/systemd/systemd/issues #11456 https://github.com/systemd/systemd/issues/11456 -- 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. Fixed in Disco with the backported v240 patch from https://github.com/systemd/systemd/commit/677b4cc753f183731fc54fcb68ad46f806c394bc [other info] original description: --- Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
** Changed in: libxml2
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in libxml2:
New
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+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 1869814] Re: ubuntu-docs build failure - possible solution
** Bug watch added: gitlab.gnome.org/GNOME/libxml2/issues #64
https://gitlab.gnome.org/GNOME/libxml2/issues/64
** Changed in: libxml2
Remote watch: bugzilla.gnome.org/ #789714 =>
gitlab.gnome.org/GNOME/libxml2/issues #64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in libxml2:
Unknown
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+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 1869814] Re: ubuntu-docs build failure - possible solution
** Also affects: libxml2 via
https://bugzilla.gnome.org/show_bug.cgi?id=789714
Importance: Unknown
Status: Unknown
** Bug watch removed: gitlab.gnome.org/GNOME/libxml2/issues #64
https://gitlab.gnome.org/GNOME/libxml2/issues/64
** Bug watch removed: gitlab.gnome.org/GNOME/libxml2/-/issues #12
https://gitlab.gnome.org/GNOME/libxml2/-/issues/12
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in libxml2:
Unknown
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+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 1871726] Re: "systemd --user" and child processes fail to exit when user logs out
Could you try this using lightdm? It's possible that this may be a display-manager issue. I did notice that in a different (customized) configuration of Xubuntu, the user processes still remained after logout, but then killing the "systemd --user" process resulted in the login session ending. Anyway, here is the output you requested, in the original test environment: # LC_ALL=C loginctl user-status skunk | cat skunk (1000) Since: Fri 2020-04-10 18:40:19 EDT; 3min 11s ago State: closing Sessions: *c2 Linger: no Unit: user-1000.slice |-session-c2.scope | |-1288 /usr/libexec/geoclue-2.0/demos/agent | `-1345 /usr/bin/python3 /usr/share/system-config-printer/applet.py `-user@1000.service |-at-spi-dbus-bus.service | |-1131 /usr/libexec/at-spi-bus-launcher | `-1136 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 |-dbus.service | |-1042 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only | |-1140 /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd | |-1291 /usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd | |-1302 /usr/libexec/dconf-service | |-1391 /usr/libexec/goa-daemon | `-1404 /usr/libexec/goa-identity-service |-evolution-addressbook-factory.service | `-1438 /usr/libexec/evolution-addressbook-factory |-evolution-calendar-factory.service | `-1396 /usr/libexec/evolution-calendar-factory |-evolution-source-registry.service | `-1374 /usr/libexec/evolution-source-registry |-gvfs-afc-volume-monitor.service | `-1501 /usr/libexec/gvfs-afc-volume-monitor |-gvfs-daemon.service | |-1153 /usr/libexec/gvfsd | |-1158 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes | `-1509 /usr/libexec/gvfsd-trash --spawner :1.13 /org/gtk/gvfs/exec_spaw/0 |-gvfs-goa-volume-monitor.service | `-1497 /usr/libexec/gvfs-goa-volume-monitor |-gvfs-gphoto2-volume-monitor.service | `-1493 /usr/libexec/gvfs-gphoto2-volume-monitor |-gvfs-metadata.service | `-1515 /usr/libexec/gvfsd-metadata |-gvfs-mtp-volume-monitor.service | `-1489 /usr/libexec/gvfs-mtp-volume-monitor |-gvfs-udisks2-volume-monitor.service | `-1484 /usr/libexec/gvfs-udisks2-volume-monitor |-init.scope | |-1017 /lib/systemd/systemd --user | `-1018 (sd-pam) `-obex.service `-1464 /usr/lib/bluetooth/obexd Apr 10 18:41:21 test-ubuntu64 systemd[1017]: Stopped Indicator Application Service. Apr 10 18:41:21 test-ubuntu64 systemd[1017]: indicator-keyboard.service: Succeeded. Apr 10 18:41:21 test-ubuntu64 systemd[1017]: Stopped Indicator Keyboard Backend. Apr 10 18:41:21 test-ubuntu64 systemd[1017]: Stopping Indicator Session Service... Apr 10 18:41:21 test-ubuntu64 systemd[1017]: indicator-session.service: Succeeded. Apr 10 18:41:21 test-ubuntu64 systemd[1017]: Stopped Indicator Session Service. Apr 10 18:41:22 test-ubuntu64 indicator-sound[1250]: g_object_ref: assertion 'old_val > 0' failed Apr 10 18:41:22 test-ubuntu64 systemd[1017]: pulseaudio.service: Succeeded. Apr 10 18:41:22 test-ubuntu64 systemd[1017]: indicator-sound.service: Succeeded. Apr 10 18:41:22 test-ubuntu64 systemd[1017]: Stopped Indicator Sound Service. If I kill the "systemd --user" process, the output slims down to this: # LC_ALL=C loginctl user-status skunk | cat skunk (1000) Since: Fri 2020-04-10 18:40:19 EDT; 5min ago State: closing Sessions: *c2 Linger: no Unit: user-1000.slice `-session-c2.scope `-1288 /usr/libexec/geoclue-2.0/demos/agent Apr 10 18:45:14 test-ubuntu64 systemd[1017]: pk-debconf-helper.socket: Succeeded. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: Closed debconf communication socket. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: pulseaudio.socket: Succeeded. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: Closed Sound System. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: snapd.session-agent.socket: Succeeded. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: Closed REST API socket for snapd user session agent. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: Reached target Shutdown. Apr 10 18:45:14 test-ubuntu64
[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
** No longer affects: itstool (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1869814/+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 1871615] Re: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt
Thanks Balint! I gave a very quick read to the 2.2 debdiff and couldn't spot the fix, though -- I'd just like to double-check that the fix made it to the packaging. Thanks -- 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/1871615 Title: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt Status in apparmor package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: I have no definite idea what happened, it just popped up randomly. I can only assume it was trying to show the usual update notification ProblemType: Package DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 AptOrdering: apparmor:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Apr 8 13:57:33 2020 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2020-03-25 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=66ca0e88-1f73-48ce-a0ae-cfa14442ffe1 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: apparmor Syslog: Apr 8 13:04:35 sebipc dbus-daemon[1090]: [system] AppArmor D-Bus mediation is enabled Apr 8 13:04:44 sebipc dbus-daemon[1479]: [session uid=125 pid=1479] AppArmor D-Bus mediation is enabled Apr 8 13:05:16 sebipc dbus-daemon[2072]: [session uid=1000 pid=2072] AppArmor D-Bus mediation is enabled Apr 8 13:55:52 sebipc dbus-daemon[2072]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/" interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" name="com.canonical.Unity" pid=11890 label="snap.telegram-desktop.telegram-desktop" peer_pid=2359 peer_label="unconfined" Apr 8 13:55:53 sebipc dbus-daemon[2072]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/ScreenSaver" interface="org.freedesktop.ScreenSaver" member="GetSessionIdleTime" mask="send" name="org.freedesktop.ScreenSaver" pid=11890 label="snap.telegram-desktop.telegram-desktop" peer_pid=2462 peer_label="unconfined" Title: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apparmor.d.abstractions.base: 2020-03-26T13:00:28.401582 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1871615/+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 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used
** Summary changed: - explicit key offered after all agent keys, auth fails before explicit key used + explicit key offered after all agent keys, auth can fail before explicit key used -- 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/1872145 Title: explicit key offered after all agent keys, auth can fail before explicit key used Status in openssh package in Ubuntu: New Bug description: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1872145/+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 1872145] [NEW] explicit key offered after all agent keys, auth fails before explicit key used
Public bug reported: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1872145 Title: explicit key offered after all agent keys, auth fails before explicit key used Status in openssh package in Ubuntu: New Bug description: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1872145/+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 1872141] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872141/+attachment/5351565/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en_US SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872141/+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 1872141] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872141/+attachment/5351567/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872141/+attachment/5351556/+files/CoreDump.gz ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Medium ** Summary changed: - evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() + evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en_US SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872141/+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 1872141] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1872141/+attachment/5351566/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en_US SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872141/+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 1872141] evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch()
StacktraceTop: ?? () invoke_set_property_in_idle_cb (_data=0x7f9f34012820) at ../../../gio/gdbusconnection.c:4225 g_main_context_dispatch () from /tmp/apport_sandbox_ax_n61ir/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1 g_main_context_iterate.isra () from /tmp/apport_sandbox_ax_n61ir/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1 g_main_loop_run () from /tmp/apport_sandbox_ax_n61ir/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en_US SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872141/+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 1872141] [NEW] evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb()
Public bug reported: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0:Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en_US SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: evolution-data-server (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-crash focal ** Information type changed from Private to Public ** Changed in: evolution-data-server (Ubuntu) Status: New => Incomplete ** Description changed: + [Joshua Peisach] + I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= - LANGUAGE=en_US + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= + LANGUAGE=en_US SegvAnalysis: - Segfault happened at: 0x0: Cannot access memory at address 0x0 - PC (0x) not located in a known VMA region (needed executable region)! + Segfault happened at: 0x0: Cannot access memory at address 0x0 + PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: - ?? () - ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 - g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () + ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 + g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64
[Touch-packages] [Bug 1872110] Re: sonido
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872110 Title: sonido Status in xorg package in Ubuntu: New Bug description: tengo instalado ubuntu 18.04 de 32 bits y no hay forma de que pueda hacer funcionar el sonido, ya probe reinstalando alsa y pulseaudio y no hay forma, necesito una ayuda para poder quedarme con este sistema operativo, muchas gracias. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-97.98-generic 4.15.18 Uname: Linux 4.15.0-97-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Apr 10 14:00:24 2020 DistUpgraded: 2020-04-10 10:09:39,450 WARNING no activity on terminal for 300 seconds (printer-driver-foo2zjs (i386) instalado) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Atom Processor D2xxx/N2xxx Integrated Graphics Controller [144d:c664] InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 100NZA ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-97-generic root=UUID=0e55513e-8acd-4784-affc-3ae8ec7bd17d ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) dmi.bios.date: 10/07/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 00OT dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Intel powered classmate PC dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD dmi.board.version: 0.1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr00OT:bd10/07/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn100NZA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD:rnIntelpoweredclassmatePC:rvr0.1:cvnSAMSUNGELECTRONICSCO.,LTD:ct9:cvr0.1: dmi.product.family: CedarTrail System dmi.product.name: 100NZA dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Apr 10 13:45:55 2020 xserver.configfile: default xserver.errors: modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872110/+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 1872110] [NEW] sonido
You have been subscribed to a public bug: tengo instalado ubuntu 18.04 de 32 bits y no hay forma de que pueda hacer funcionar el sonido, ya probe reinstalando alsa y pulseaudio y no hay forma, necesito una ayuda para poder quedarme con este sistema operativo, muchas gracias. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-97.98-generic 4.15.18 Uname: Linux 4.15.0-97-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Apr 10 14:00:24 2020 DistUpgraded: 2020-04-10 10:09:39,450 WARNING no activity on terminal for 300 seconds (printer-driver-foo2zjs (i386) instalado) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Atom Processor D2xxx/N2xxx Integrated Graphics Controller [144d:c664] InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 100NZA ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-97-generic root=UUID=0e55513e-8acd-4784-affc-3ae8ec7bd17d ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) dmi.bios.date: 10/07/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 00OT dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Intel powered classmate PC dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD dmi.board.version: 0.1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr00OT:bd10/07/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn100NZA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD:rnIntelpoweredclassmatePC:rvr0.1:cvnSAMSUNGELECTRONICSCO.,LTD:ct9:cvr0.1: dmi.product.family: CedarTrail System dmi.product.name: 100NZA dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Apr 10 13:45:55 2020 xserver.configfile: default xserver.errors: modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic compiz-0.9 i386 ubuntu -- sonido https://bugs.launchpad.net/bugs/1872110 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
Adding a snapd Ubuntu task, marking as In Progress and assigning to mvo since he is preparing a 20.04 upload. ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu Focal) Assignee: (unassigned) => Michael Vogt (mvo) ** Changed in: snapd (Ubuntu Focal) Status: New => In Progress ** Changed in: snapd (Ubuntu Focal) Importance: Undecided => High ** Changed in: snapd (Ubuntu Focal) Milestone: None => ubuntu-20.04 -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: In Progress Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: In Progress Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
keep having the same modinfo error on all kernels 5.6.x , running Ubuntu 20.04. modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory On kernel 5.5.16 this modinfo error does not appear. Since the report also have this same message, maybe someone knows something ? -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1869814] Re: ubuntu-docs build failure - possible solution
To the sponsor:
libxml2 2.9.10+dfsg-5, including the patch, is now available in Debian
unstable. So please sync libxml2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in itstool package in Ubuntu:
Invalid
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1871148] Re: services start before apparmor profiles are loaded
** Changed in: snapd Status: In Progress => Fix Released -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
@Gunnar, thanks for testing! The sleep is a workaround, not a proper fix though. I would guess that something in the gtk widgets used is taking a grab which prevents the shell to be able to displays it's dialog so the proper fix would be to try to understand if that's an event or something we need to wait on before doing the call to polkit. If I don't success to find a better fix I will upload the sleep workaround -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Invalid Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]
I have some thing similar I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report /var/crash/_usr_sbin_dhcpd.0.crash /var/crash/_usr_sbin_dhcpd.0.crash shows ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Fri Apr 10 17:20:15 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1586210315 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 6828 Ngid: 0 Pid: 6828 PPid: 1 TracerPid: 0 Uid: 113 113 113 113 Gid: 118 118 118 118 FDSize:128 Groups: NStgid:6828 NSpid: 6828 NSpgid:6828 NSsid: 6828 VmPeak: 236244 kB VmSize: 170764 kB VmLck:0 kB VmPin:0 kB VmHWM:12064 kB VmRSS:12064 kB RssAnon: 5940 kB RssFile: 6124 kB RssShmem: 0 kB VmData: 30792 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5424 kB VmPTE: 76 kB VmSwap: 0 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/7609 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:00018000 CapInh: CapPrm: CapEff: CapBnd:003f CapAmb: NoNewPrivs:0 Seccomp: 0 Speculation_Store_Bypass: thread vulnerable Cpus_allowed: 3 Cpus_allowed_list: 0-1 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches: 111 nonvoluntary_ctxt_switches:144 Signal: 6 Uname: Linux 5.4.0-21-generic x86_64 UserGroups: ** Changed in: isc-dhcp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872106 Title: isc-dhcp-server crashing constantly [Ubuntu 20.04] Status in isc-dhcp package in Ubuntu: Confirmed Bug description: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]
please ignore this is fixed by https://bugs.launchpad.net/bugs/1870729, but then the above happens -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872106 Title: isc-dhcp-server crashing constantly [Ubuntu 20.04] Status in isc-dhcp package in Ubuntu: Confirmed Bug description: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+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 1872118] [NEW] DHCP Cluster crashes after a few hours
Public bug reported: I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report /var/crash/_usr_sbin_dhcpd.0.crash /var/crash/_usr_sbin_dhcpd.0.crash shows ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Fri Apr 10 17:20:15 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1586210315 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 6828 Ngid: 0 Pid: 6828 PPid: 1 TracerPid: 0 Uid: 113 113 113 113 Gid: 118 118 118 118 FDSize:128 Groups: NStgid:6828 NSpid: 6828 NSpgid:6828 NSsid: 6828 VmPeak: 236244 kB VmSize: 170764 kB VmLck:0 kB VmPin:0 kB VmHWM:12064 kB VmRSS:12064 kB RssAnon: 5940 kB RssFile: 6124 kB RssShmem: 0 kB VmData: 30792 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5424 kB VmPTE: 76 kB VmSwap: 0 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/7609 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:00018000 CapInh: CapPrm: CapEff: CapBnd:003f CapAmb: NoNewPrivs:0 Seccomp: 0 Speculation_Store_Bypass: thread vulnerable Cpus_allowed: 3 Cpus_allowed_list: 0-1 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches: 111 nonvoluntary_ctxt_switches:144 Signal: 6 Uname: Linux 5.4.0-21-generic x86_64 UserGroups: ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872118 Title: DHCP Cluster crashes after a few hours Status in isc-dhcp package in Ubuntu: New Bug description: I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020:
[Touch-packages] [Bug 1869024] Re: add support for DynamicUser feature of systemd
The abstraction is meant to cover the client, not systemd internal specifics. A client simply accessing that DBus API won't need it and a client simply accessing those sockets won't need it. It very well might be that a profiled application is using some *ctl command from systemd that would need it, but in that case said command would need to be added to the policy and the boot-id could be added at that time. -- 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/1869024 Title: add support for DynamicUser feature of systemd Status in snapd: In Progress Status in apparmor package in Ubuntu: Fix Released Bug description: systemd offers to create dynamic (and semi-stable) users for services. This causes many services using Apparmor profiles to trigger those denials (even when they don't use the DynamicUser feature): audit: type=1107 audit(1585076282.591:30): pid=621 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.systemd1" pid=709 label="/usr/sbin/squid" peer_pid=1 peer_label="unconfined" And more recently with systemd 245 this also get shown: audit: type=1400 audit(1585139000.628:39): apparmor="DENIED" operation="open" profile="/usr/sbin/squid" name="/run/systemd/userdb/" pid=769 comm="squid" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Additional information: # lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 # uname -a Linux foo.example.com 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # apt-cache policy apparmor squid apparmor: Installed: 2.13.3-7ubuntu2 Candidate: 2.13.3-7ubuntu2 Version table: *** 2.13.3-7ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status squid: Installed: 4.10-1ubuntu1 Candidate: 4.10-1ubuntu1 Version table: *** 4.10-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1869024/+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 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT
I will update the policy for the write access. I suggest removing the crash file in /var/crash, then if you see the crash again, file a new bug with the crash information (eg, apport-cli if on a server) so it can be analyzed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1870729 Title: DHCP Server regularly killed code=killed, status=6/ABRT Status in isc-dhcp package in Ubuntu: In Progress Bug description: On Ubuntu 20.04 The idc-dhcp- server version is isc-dhcp-server: Installed: (none) Candidate: 4.4.1-2.1ubuntu3 Version table: 4.4.1-2.1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages The DHCP server is being regularly killed, when searching google the bug looks very similar to an older bug regarding accessing a lease file, that was fixed year ago. As a temporary fix in systemd I have enabled a restart every time the main process fails. The error got worse when i start to run a pair of dhcp servers syncing state between each other I regularly see the following in the syslog Apr 4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ?? Apr 4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ?? Apr 4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ?? Apr 4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ?? Apr 4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ?? Apr 4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. Apr 4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart job, restart counter is at 3. Apr 4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server. Apr 4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server. Apr 4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 audit(1585958700.678:46): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Apr 4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1 Apr 4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1 Apr 4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium. Apr 4 00:05:00 gw sh[2049]: All rights reserved. Apr 4 00:05:00 gw sh[2049]: For info, please visit https://www.isc.org/software/dhcp/ Apr 4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems Consortium. Apr 4 00:05:00 gw dhcpd[2049]: All rights reserved. Apr 4 00:05:00 gw dhcpd[2049]: For info, please visit https://www.isc.org/software/dhcp/ Apr 4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 audit(1585958700.678:47): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Apr 4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 audit(1585958700.682:48): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Apr 4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf Apr 4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf Apr 4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases Apr 4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid Apr 4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases Apr 4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid Apr 4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+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 1871615] Re: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt
Thanks! -- 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/1871615 Title: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt Status in apparmor package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: I have no definite idea what happened, it just popped up randomly. I can only assume it was trying to show the usual update notification ProblemType: Package DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 AptOrdering: apparmor:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Apr 8 13:57:33 2020 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2020-03-25 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=66ca0e88-1f73-48ce-a0ae-cfa14442ffe1 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: apparmor Syslog: Apr 8 13:04:35 sebipc dbus-daemon[1090]: [system] AppArmor D-Bus mediation is enabled Apr 8 13:04:44 sebipc dbus-daemon[1479]: [session uid=125 pid=1479] AppArmor D-Bus mediation is enabled Apr 8 13:05:16 sebipc dbus-daemon[2072]: [session uid=1000 pid=2072] AppArmor D-Bus mediation is enabled Apr 8 13:55:52 sebipc dbus-daemon[2072]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/" interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" name="com.canonical.Unity" pid=11890 label="snap.telegram-desktop.telegram-desktop" peer_pid=2359 peer_label="unconfined" Apr 8 13:55:53 sebipc dbus-daemon[2072]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/ScreenSaver" interface="org.freedesktop.ScreenSaver" member="GetSessionIdleTime" mask="send" name="org.freedesktop.ScreenSaver" pid=11890 label="snap.telegram-desktop.telegram-desktop" peer_pid=2462 peer_label="unconfined" Title: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apparmor.d.abstractions.base: 2020-03-26T13:00:28.401582 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1871615/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
@Sebastien: I can confirm that your workaround fixes it for me. (Race condition?) Would be nice if it could be uploaded to focal to start with... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Invalid Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1872106] [NEW] isc-dhcp-server crashing constantly [Ubuntu 20.04]
Public bug reported: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872106 Title: isc-dhcp-server crashing constantly [Ubuntu 20.04] Status in isc-dhcp package in Ubuntu: New Bug description: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+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 1872104] [NEW] Lenovo x230 fails to get into login mode after reboot - just purple screen or sometimes login w fprint and same purple screen
Public bug reported: "Fresh" install, /home kept, via "Other " on install from usb Powering off gets me into sleep mode, power button configured to only on/off. More on/off gets real shut down. I have to go through safe mode, and have not found what gets it working. Last time I did all, and had to reboot again, because of same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: login 1:4.8.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 17:48:48 2020 InstallationDate: Installed on 2019-01-14 (451 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (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 shadow in Ubuntu. https://bugs.launchpad.net/bugs/1872104 Title: Lenovo x230 fails to get into login mode after reboot - just purple screen or sometimes login w fprint and same purple screen Status in shadow package in Ubuntu: New Bug description: "Fresh" install, /home kept, via "Other " on install from usb Powering off gets me into sleep mode, power button configured to only on/off. More on/off gets real shut down. I have to go through safe mode, and have not found what gets it working. Last time I did all, and had to reboot again, because of same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: login 1:4.8.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 17:48:48 2020 InstallationDate: Installed on 2019-01-14 (451 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1872104/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
Given that all the other linux package hook symlinks are made in apport I think it would make sense to include the linux-firmware symlink there. [ 8:47AM 10484 ] [ bdmurray@impulse:~/source-trees/apport/focal ] $ head -n15 debian/apport.links /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-meta-oem-osp1.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-meta-oem.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-meta.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-oem-osp1.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-oem.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed-oem-osp1.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed-oem.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed-5.4.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-signed-oem-5.4.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-5.4.py /usr/share/apport/package-hooks/source_linux.py /usr/share/apport/package-hooks/source_linux-oem-5.4.py /usr/bin/apport-bug /usr/bin/ubuntu-bug /usr/share/man/man1/apport-bug.1.gz /usr/share/man/man1/ubuntu-bug.1.gz /usr/share/man/man1/apport-bug.1.gz /usr/share/man/man1/apport-collect.1.gz -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in apport source package in Focal: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name:
[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT
ran for a few hours then crashed with ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: called for pid 1900, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: apport: report /var/crash/_usr_sbin_dhcpd.0.crash already exists and unseen, doing nothing to avoid disk usage DoS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1870729 Title: DHCP Server regularly killed code=killed, status=6/ABRT Status in isc-dhcp package in Ubuntu: In Progress Bug description: On Ubuntu 20.04 The idc-dhcp- server version is isc-dhcp-server: Installed: (none) Candidate: 4.4.1-2.1ubuntu3 Version table: 4.4.1-2.1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages The DHCP server is being regularly killed, when searching google the bug looks very similar to an older bug regarding accessing a lease file, that was fixed year ago. As a temporary fix in systemd I have enabled a restart every time the main process fails. The error got worse when i start to run a pair of dhcp servers syncing state between each other I regularly see the following in the syslog Apr 4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ?? Apr 4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ?? Apr 4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ?? Apr 4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ?? Apr 4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ?? Apr 4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. Apr 4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart job, restart counter is at 3. Apr 4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server. Apr 4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server. Apr 4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 audit(1585958700.678:46): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Apr 4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1 Apr 4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1 Apr 4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium. Apr 4 00:05:00 gw sh[2049]: All rights reserved. Apr 4 00:05:00 gw sh[2049]: For info, please visit https://www.isc.org/software/dhcp/ Apr 4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems Consortium. Apr 4 00:05:00 gw dhcpd[2049]: All rights reserved. Apr 4 00:05:00 gw dhcpd[2049]: For info, please visit https://www.isc.org/software/dhcp/ Apr 4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 audit(1585958700.678:47): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Apr 4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 audit(1585958700.682:48): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Apr 4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf Apr 4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf Apr 4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases Apr 4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid Apr 4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases Apr 4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid Apr 4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+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 1872071] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()
** Information type changed from Private to Public -- 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/1872071 Title: ibus-x11 crashed with SIGSEGV in __GI___poll() Status in ibus package in Ubuntu: New Bug description: This happened at start up after software updater requested a restart.I attached unattended-upgrades.log unattended-upgrades-dpkg.log dpkg.log to show what packages were installed before the restart. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 07:16:32 2020 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-03-14 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f6b2b2919f6 <__run_exit_handlers+198>: mov 0x10(%rax),%rdx PC (0x7f6b2b2919f6) ok source "0x10(%rax)" (0x1042f359537650) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __GI___poll (fds=0x7f6af80067e0, nfds=3, timeout=1766) at ../sysdeps/unix/sysv/linux/poll.c:29 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () Title: ibus-x11 crashed with SIGSEGV in __GI___poll() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872071/+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 1870805] Re: pas de son
toujour rien pa de pilote je pensse -- 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/1870805 Title: pas de son Status in pulseaudio package in Ubuntu: Incomplete Bug description: je n'ai pas de son qui sort de l'ordinateur, pas de sortie audio ni d'applications pour le son avec Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 17:25:31 2020 InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2018 dmi.bios.version: HQ-BI-14.1-Y116CR600-CC34I-014-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvn:bvrHQ-BI-14.1-Y116CR600-CC34I-014-D:bd01/08/2018:svnSCHNEIDER:pnSCL141CTP:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SCL141CTP dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: SCHNEIDER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870805/+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 1835660] Re: initramfs unpacking failed
In post#14, I showed how my gzip booted faster. "We currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system." If 'harmless', then why the error in the first place? Something is causing it. Sticking the error in the sand is NOT the answer! -- 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/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1871451] Re: powerpc segfault on exponential of negative in python
This would be an issue for the package, I will close the track for cloud-images. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-images Status: New => Invalid -- 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/1871451 Title: powerpc segfault on exponential of negative in python Status in cloud-images: Invalid Status in python3-defaults package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: When calculating the exponential of a negative number in python 3.6 with the Ubuntu 18.04 Docker image (ppcle64), I receive a segfault. ``` python3 -c "import math; math.exp(-1)" qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault ``` I am running this in Docker on macOS. Here are the steps to reproduce the error. ``` docker run --rm -it --platform linux/ppc64le ubuntu:18.04 apt-get update -qq && apt-get install -y -qq python3 python3 -c "import math; print(math.exp(0))" # 1.0 python3 -c "import math; print(math.exp(-0))" # 1.0 python3 -c "import math; print(math.exp(1))" # 2.718281828459045 python3 -c "import math; print(math.exp(-1))" ``` This error does not happen when using the debian:10 or alpine images. Here is the output of docker version on my machine: ``` Client: Docker Engine - Community Version: 19.03.8 API version: 1.40 Go version:go1.12.17 Git commit:afacb8b Built: Wed Mar 11 01:21:11 2020 OS/Arch: darwin/amd64 Experimental: true Server: Docker Engine - Community Engine: Version: 19.03.8 API version: 1.40 (minimum version 1.12) Go version: go1.12.17 Git commit: afacb8b Built:Wed Mar 11 01:29:16 2020 OS/Arch: linux/amd64 Experimental: true containerd: Version: v1.2.13 GitCommit:7ad184331fa3e55e52b890ea95e65ba581ae3429 runc: Version: 1.0.0-rc10 GitCommit:dc9208a3303feef5b3839f4323d9beb36df0a9dd docker-init: Version: 0.18.0 GitCommit:fec3683 ``` Cross-posted to StackOverflow: https://stackoverflow.com/questions/61084969/python-segfault- calculating-exponential-of-negative-ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1871451/+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 1870850] Re: Multi-line paste broken between kitty and nano 4.8 [focal]
Thanks Benno for providing the patches, I've uploaded it to focal now (I will let other people deal wit requesting a ffe for a newer nano if wanted) ** Changed in: nano (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1870850 Title: Multi-line paste broken between kitty and nano 4.8 [focal] Status in nano package in Ubuntu: Fix Committed Bug description: Ubuntu 20.04 Focal beta (as of 2020-04-04) nano 4.8-1 What I expect to happen: multi-line paste into nano via kitty pastes multiple lines. What happens instead: pasted multi-line text is one line with no line breaks. There is a bit of a spat between the developers of kitty (gnome- terminal:kitty::screen:tmux, basically) and nano about how to do multi-line pasting. See e.g.: * https://savannah.gnu.org/bugs/?58010 * https://lists.gnu.org/archive/html/nano-devel/2020-03/msg5.html * https://github.com/kovidgoyal/kitty/issues/994 Without taking sides, the facts are: * With the current versions in focal (kitty 0.15.0 and nano 4.8), pasting multi-line will result in newlines being eaten. * nano 4.9 introduces a fix (commit 481529e8650d105c3280def764e4917af0cabb49) which brings the newline handling more in line with other terminal-aware programs (treating raw \n as line break). Peripherally, nano 4.8 introduced new bracketed paste mode support. This makes a read of the kitty github issue above harder, since the issue being reported here is about an incompatibility in bracketed paste mode between kitty and nano, not pre-bracketed ^J handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+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 1866820] Re: crash in nano-4.8 when typing ^6 ^J [patch]
Thanks Benno for providing the patches, I've uploaded it to focal now (I will let other people deal wit requesting a ffe for a newer nano if wanted) ** Changed in: nano (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1866820 Title: crash in nano-4.8 when typing ^6 ^J [patch] Status in nano package in Ubuntu: Fix Committed Bug description: Nanos since version 4.0 contain a silly oversight: when the user tries to justify an empty region (with ^6 ^J, or similar), nano crashes. Attached upstream patch fixes the problem. Please apply to Focal before it is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1866820/+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 1872066] Re: ibus-x11 crashed with SIGSEGV
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: ibus (Ubuntu) Importance: Undecided => Low ** Changed in: ibus (Ubuntu) Status: New => Incomplete ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1872066 Title: ibus-x11 crashed with SIGSEGV Status in ibus package in Ubuntu: Incomplete Bug description: Problema con el IBus ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:15:34 2020 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon ProcEnviron: LANG=es_VE.UTF-8 LANGUAGE=es_VE:es PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f053a3079f6 <__run_exit_handlers+198>: mov 0x10(%rax),%rdx PC (0x7f053a3079f6) ok source "0x10(%rax)" (0x1036daa0e28aa0) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () ?? () ?? () Title: ibus-x11 crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872066/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@Seb Sorry for the inconvenience, I will be more careful next time, thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed
For me its happening the same, if lz4 is activated get this initramfs unpacking failed: Decoding failed at first line of boot, if switch to gzip the error is gone, switching back to lz4 make the initramfs unpacking failed: Decoding failed back again at boot, staying at gzip for the time being. Also no idea if relative, on my machine running Ubuntu Cinnamon 20.04 , when the lz4 is activated over the initramfs , it gives the error at boot and will not show the oem logo during boot, if gzip is activated, no error and it does show the oem logo during boot. Secure boot on my machine have been always disabled and remains disabled. ** Changed in: initramfs-tools (Ubuntu) Status: Invalid => Confirmed -- 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/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
Thanks for the bionic patch, please read https://packaging.ubuntu.com/html/fixing-a-bug.html for next time though and provide a proper debdiff I'm fixing your changes and uploaded now, what was missing is - only the patch to the upstream code should be in debian/patches, the changelog needs to be directly updates - the patch should be listed in the serie - the bug reference should be listed as 'lp: #...' in the changelog (especially important for a SRU since the bug is what ensure the testing process can be followed) ** Changed in: pulseaudio (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
Oh, also there was already a 1:11.1-1ubuntu7.5 in bionic-proposed so the update needed to be rebased on this one and become ubuntu7.6, I did that as well now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859581] Re: land oem-getlogs in focal and enable apport-unpack to process apport.gz file
@Brain, Thanks! ** No longer affects: apport ** Changed in: oem-priority Status: Confirmed => Fix Released -- 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/1859581 Title: land oem-getlogs in focal and enable apport-unpack to process apport.gz file Status in OEM Priority Project: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: LP: #1841157 seems forgeting to include oem-getlogs in debian/apport.install. Also, add the attached patch so that apport-unpack can process apport.gz that oem-getlogs generate directly. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1859581/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
The focal fix landed now (but didn't autoclose since the bug was not mentioned in the changelog) ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871639] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@2512:main:run:do_install
This bug was fixed in the package unattended-upgrades - 2.2 --- unattended-upgrades (2.2) unstable; urgency=medium * ci: Use apt-get instead of apt to avoid warnings * Don't raise NoAllowedOriginError from call_adjusted() (LP: #1871633) * Clear cache changes in do_install() instead of raising error when a package is marked for removal. (LP: #1871639) -- Balint Reczey Thu, 09 Apr 2020 15:29:33 +0200 ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1871639 Title: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended- upgrade@2512:main:run:do_install Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.1, the problem page at https://errors.ubuntu.com/problem/d0937d96aee2ec9db0f22e609e974f5fea9ef2b7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1871639/+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 1871633] Re: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-upgrade@2512:main:run:mark_upgrade_adjusted:call_adjusted
This bug was fixed in the package unattended-upgrades - 2.2 --- unattended-upgrades (2.2) unstable; urgency=medium * ci: Use apt-get instead of apt to avoid warnings * Don't raise NoAllowedOriginError from call_adjusted() (LP: #1871633) * Clear cache changes in do_install() instead of raising error when a package is marked for removal. (LP: #1871639) -- Balint Reczey Thu, 09 Apr 2020 15:29:33 +0200 ** Changed in: unattended-upgrades (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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1871633 Title: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended- upgrade@2512:main:run:mark_upgrade_adjusted:call_adjusted Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.1, the problem page at https://errors.ubuntu.com/problem/35c5901c0d348051e3aff713e5b3d4072816cecd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1871633/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** No longer affects: apport (Ubuntu Eoan) ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** No longer affects: apport (Ubuntu Bionic) -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in apport source package in Focal: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1865474] Re: sysytemd-resolved automatically use an ipv6 dns server on lan
I have DDWRT based WiFi router and affected the same bug. DHCP6 as well as DNS6 in the router are disabled. My problem was, that local DNS names provided by router stop resolved after few minutes since reconnecting to the router WiFi or LAN, while global domain names seems always resolved fine. Bypassing systemd-resolve by editing manually nameservers in the /etc/resolv.conf which is linked to the ../run/systemd/resolve/stub- resolv.conf can fix the problem with local DNS names. First I tried, as it was suggested in some discussions of the similar issue, without success to set DNSSEC=no explicitly. Seems this systemd- resolve setting is default now. Then I tried to set DNS servers manually in the Network Manager. This didn't help also. Here the output when local DNS names provided by router stop resolved. ---8< $ systemd-resolve --status Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp1s0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: fe80::22cf:30ff:fece:c98 DNS Servers: 172.20.1.250 172.20.1.1 8.8.8.8 fe80::22cf:30ff:fece:c98 DNS Domain: ~. lan Link 2 (enp3s0f0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no ---8< Any idea what was the IP v6 DNS server address fe80::22cf:30ff:fece:c98 assigned? I fixed the problem by changing Network Manager IP v6 mode setting from Automatic to Ignore. -- 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/1865474 Title: sysytemd-resolved automatically use an ipv6 dns server on lan Status in systemd package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 i installed focal from the netboot version mini.iso. i encountered some problem on dsn configuration and i found that systemd-resolved was using an ipv6 dns address this is my netplan configuration: network: version: 2 renderer: networkd ethernets: ens3: addresses: - 192.168.1.1/24 gateway4: 192.168.1.212 nameservers: search: [xxx.com] addresses: [192.168.1.191, 192.168.1.206] this is the output of "systemd-resolved --status" Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa
[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT
dhcp-primary started to log the same errors so applied the same fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1870729 Title: DHCP Server regularly killed code=killed, status=6/ABRT Status in isc-dhcp package in Ubuntu: In Progress Bug description: On Ubuntu 20.04 The idc-dhcp- server version is isc-dhcp-server: Installed: (none) Candidate: 4.4.1-2.1ubuntu3 Version table: 4.4.1-2.1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages The DHCP server is being regularly killed, when searching google the bug looks very similar to an older bug regarding accessing a lease file, that was fixed year ago. As a temporary fix in systemd I have enabled a restart every time the main process fails. The error got worse when i start to run a pair of dhcp servers syncing state between each other I regularly see the following in the syslog Apr 4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ?? Apr 4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ?? Apr 4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ?? Apr 4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ?? Apr 4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ?? Apr 4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. Apr 4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart job, restart counter is at 3. Apr 4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server. Apr 4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server. Apr 4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 audit(1585958700.678:46): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Apr 4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1 Apr 4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1 Apr 4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium. Apr 4 00:05:00 gw sh[2049]: All rights reserved. Apr 4 00:05:00 gw sh[2049]: For info, please visit https://www.isc.org/software/dhcp/ Apr 4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems Consortium. Apr 4 00:05:00 gw dhcpd[2049]: All rights reserved. Apr 4 00:05:00 gw dhcpd[2049]: For info, please visit https://www.isc.org/software/dhcp/ Apr 4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 audit(1585958700.678:47): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Apr 4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 audit(1585958700.682:48): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Apr 4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf Apr 4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf Apr 4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases Apr 4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid Apr 4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases Apr 4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid Apr 4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+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 1865474] Re: sysytemd-resolved automatically use an ipv6 dns server on lan
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1865474 Title: sysytemd-resolved automatically use an ipv6 dns server on lan Status in systemd package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 i installed focal from the netboot version mini.iso. i encountered some problem on dsn configuration and i found that systemd-resolved was using an ipv6 dns address this is my netplan configuration: network: version: 2 renderer: networkd ethernets: ens3: addresses: - 192.168.1.1/24 gateway4: 192.168.1.212 nameservers: search: [xxx.com] addresses: [192.168.1.191, 192.168.1.206] this is the output of "systemd-resolved --status" Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (ens3) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: fe80::6670:2ff:feb5:d9c8 DNS Servers: 192.168.1.191 192.168.1.206 fe80::6670:2ff:feb5:d9c8 DNS Domain: xxx.com -- as you can see systemd is using the ipv6 dns server. i found that such ip was the address of my openwrt wifi router. dnsmasq is disabled for ipv4 lan interface on the router and i never configured an ipv6 network. Anyway i disabled all the ipv6 dnsmasq feature on the router and after a restart this fixed the problem. But i think that this is a bug. In my netplan i never configured an ipv6 dns nor a ipv6 network; furthermore none of my other ubuntu bionic servers showed such a behaviour. Also another focal netboot installation i made three weeks ago didn't show this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1865474/+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 1869913] Re: "Click or press a key to unlock" string not translated into french
The new langpack include the translation and the format fix ** Changed in: language-pack-gnome-fr (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 language-pack-gnome-fr in Ubuntu. https://bugs.launchpad.net/bugs/1869913 Title: "Click or press a key to unlock" string not translated into french Status in language-pack-gnome-fr package in Ubuntu: Fix Released Bug description: On the lockscreen, the "Click or press a key to unlock" string is not translated, at least in french. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 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: ubuntu:GNOME Date: Tue Mar 31 14:56:11 2020 InstallationDate: Installed on 2019-02-21 (404 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-fr/+bug/1869913/+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 1872016] Re: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
thank you for your bug report, the error is a libexpact/glibc missing symbol, reassigning ** Package changed: ibus (Ubuntu) => glibc (Ubuntu) -- 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/1872016 Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in glibc package in Ubuntu: New Bug description: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1872016/+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 1868319] Re: PCI/internal sound card not detected
@Hui "And from -42, it enabled the dmic_detect by default. And it introduced a regression from stable patches. It is fixed in the -46." As per my post #6 - it's not fixed in -46 kernel. So I deleted dmic_detect=0 from alsa-base.conf and created a symbolic link as per post #10. Rebooted. I did get sound, but it feels like it's very quiet comparing with the legacy driver (I can't hear anything below 40% volume setting and barely can hear sound at 50% setting). Also I found that microphone was enabled by default after reboot and I don't like that. So overall I'm not happy with this solution and will get back to legacy driver (dmic_detect=0 in alsa-base.config). Output of dmesg is attached and here is also an aplay output: user@G3:~$ aplay -l List of PLAYBACK Hardware Devices card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofsklhdacard [sof-skl_hda_card], device 0: HDA Analog (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: sofsklhdacard [sof-skl_hda_card], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofsklhdacard [sof-skl_hda_card], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofsklhdacard [sof-skl_hda_card], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofsklhdacard [sof-skl_hda_card], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ** Attachment added: "dmesg_output_v46_with_symbLink.csv" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+attachment/5351257/+files/dmesg_output_v46_with_symbLink.csv -- 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/1868319 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.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: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+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 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT
FIXED
on the backup DHCP server I kept seeing
Apr 10 11:10:08 dhcp-backup kernel: [ 86.045487] audit: type=1400
audit(1586513408.708:44): apparmor="DENIED" operation="open"
profile="/usr/sbin/dhcpd" name="/proc/1404/task/1417/comm" pid=1404
comm="dhcpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Apr 10 11:10:08 dhcp-backup kernel: [ 86.047925] audit: type=1400
audit(1586513408.708:45): apparmor="DENIED" operation="open"
profile="/usr/sbin/dhcpd" name="/proc/1404/task/1418/comm" pid=1404
comm="dhcpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Apr 10 11:10:08 dhcp-backup kernel: [ 86.048075] audit: type=1400
audit(1586513408.708:46): apparmor="DENIED" operation="open"
profile="/usr/sbin/dhcpd" name="/proc/1404/task/1419/comm" pid=1404
comm="dhcpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Changing
/etc/apparmor.d/usr.sbin.dhcpd
# owner @{PROC}/[0-9]*/task/[0-9]*/comm r,
owner @{PROC}/[0-9]*/task/[0-9]*/comm rw,
then reloading the policy into the kernel with: sudo apparmor_parser -r
/etc/apparmor.d/usr.sbin.dhcpd
resolved the issue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729
Title:
DHCP Server regularly killed code=killed, status=6/ABRT
Status in isc-dhcp package in Ubuntu:
In Progress
Bug description:
On Ubuntu 20.04 The idc-dhcp- server version is
isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
4.4.1-2.1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
The DHCP server is being regularly killed, when searching google the bug
looks very similar to an older bug regarding accessing a lease file, that was
fixed year ago. As a temporary fix in systemd I have enabled a restart every
time the main process fails. The error got worse when i start to run a pair of
dhcp servers syncing state between each other
I regularly see the following in the syslog
Apr 4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361:
INSIST(!sock->pending_send) failed, back trace
Apr 4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
Apr 4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
Apr 4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
Apr 4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
Apr 4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
Apr 4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited,
code=killed, status=6/ABRT
Apr 4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result
'signal'.
Apr 4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart
job, restart counter is at 3.
Apr 4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
Apr 4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
Apr 4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400
audit(1585958700.678:46): apparmor="DENIED" operation="open"
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr 4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
Apr 4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
Apr 4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
Apr 4 00:05:00 gw sh[2049]: All rights reserved.
Apr 4 00:05:00 gw sh[2049]: For info, please visit
https://www.isc.org/software/dhcp/
Apr 4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems
Consortium.
Apr 4 00:05:00 gw dhcpd[2049]: All rights reserved.
Apr 4 00:05:00 gw dhcpd[2049]: For info, please visit
https://www.isc.org/software/dhcp/
Apr 4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400
audit(1585958700.678:47): apparmor="DENIED" operation="open"
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr 4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400
audit(1585958700.682:48): apparmor="DENIED" operation="open"
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr 4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
Apr 4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
Apr 4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
Apr 4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
Apr 4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
Apr 4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
Apr 4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1871972] Re: Update pango for Unicode 13.0
Yes, only 20.04. ** Description changed: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ - Pango is used by many apps (particularly GTK apps) to display emoji. - - By doing this update for Ubuntu 18.04 LTS now, it will be easier to get + By doing this update for Ubuntu 20.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts-noto- color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. - References - =- https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 - https://emojipedia.org/emoji-13.0/ - https://github.com/googlefonts/noto-emoji/releases -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871972 Title: Update pango for Unicode 13.0 Status in pango1.0 package in Ubuntu: Fix Committed Bug description: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ By doing this update for Ubuntu 20.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts- noto-color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+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 1871726] Re: "systemd --user" and child processes fail to exit when user logs out
Thank you for your bug report, I can't confirm the bug on focal Using an uptodate system - start to gdm - login is 'userone' - create a 'dbguser' - logout from the 'userone' session - ssh dbguser@ $ loginctl list-sessions SESSION UID USER SEAT TTY 27 1001 dbguser pts/0 c3 124 gdm seat0 tty1 What's the output of $ loginctl user-status skunk for you? (you need to ssh as another user otherwise the fact that you connect with the user to start the command is going to interfer) -- 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/1871726 Title: "systemd --user" and child processes fail to exit when user logs out Status in systemd package in Ubuntu: New Bug description: This concerns systemd 245.2-1ubuntu2 in Ubuntu focal. I am using the Xfce desktop. After the user logs out from a desktop session, numerous desktop-related processes are left over. Here is a listing, taken over twenty minutes after logout: skunk853 0.0 0.2 18912 10300 ?Ss 17:55 0:00 /lib/systemd/systemd --user skunk854 0.0 0.0 103304 3496 ?S17:55 0:00 (sd-pam) skunk881 0.0 0.1 8076 5324 ?Ss 17:55 0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only skunk970 0.0 0.1 305364 6776 ?Ssl 17:55 0:00 /usr/libexec/at-spi-bus-launcher skunk975 0.0 0.1 7352 4452 ?S17:55 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 skunk979 0.0 0.1 230196 5900 ?Sl 17:55 0:00 /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd skunk992 0.0 0.1 239704 7676 ?Ssl 17:55 0:00 /usr/libexec/gvfsd skunk997 0.0 0.1 378332 6444 ?Sl 17:55 0:00 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes skunk 1133 0.0 0.1 156116 5596 ?Sl 17:56 0:00 /usr/libexec/dconf-service skunk 1139 0.0 0.1 236884 4828 ?Sl 17:56 0:00 /usr/libexec/geoclue-2.0/demos/agent skunk 1186 0.0 0.8 59324 34792 ?S17:56 0:00 /usr/bin/python3 /usr/share/system-config-printer/applet.py skunk 1201 0.0 0.6 391676 25688 ?Ssl 17:56 0:00 /usr/libexec/evolution-source-registry skunk 1224 0.0 0.8 616644 35492 ?Sl 17:56 0:00 /usr/libexec/goa-daemon skunk 1235 0.0 0.7 708928 30512 ?Ssl 17:56 0:00 /usr/libexec/evolution-calendar-factory skunk 1243 0.0 0.2 314744 8980 ?Sl 17:56 0:00 /usr/libexec/goa-identity-service skunk 1271 0.0 0.7 681460 29344 ?Ssl 17:56 0:00 /usr/libexec/evolution-addressbook-factory skunk 1302 0.0 0.1 43968 6432 ?Ss 17:56 0:00 /usr/lib/bluetooth/obexd skunk 1322 0.0 0.2 313872 9076 ?Ssl 17:56 0:00 /usr/libexec/gvfs-udisks2-volume-monitor skunk 1327 0.0 0.1 235684 6468 ?Ssl 17:56 0:00 /usr/libexec/gvfs-mtp-volume-monitor skunk 1331 0.0 0.1 237956 6876 ?Ssl 17:56 0:00 /usr/libexec/gvfs-gphoto2-volume-monitor skunk 1335 0.0 0.1 235864 5760 ?Ssl 17:56 0:00 /usr/libexec/gvfs-goa-volume-monitor skunk 1339 0.0 0.2 316716 8800 ?Ssl 17:56 0:00 /usr/libexec/gvfs-afc-volume-monitor skunk 1347 0.0 0.1 313684 7836 ?Sl 17:56 0:00 /usr/libexec/gvfsd-trash --spawner :1.13 /org/gtk/gvfs/exec_spaw/0 skunk 1353 0.0 0.1 162128 6028 ?Ssl 17:56 0:00 /usr/libexec/gvfsd-metadata When a user logs out of the system, all processes associated with the login session should be terminated (barring the use of nohup(1) or the like). If I sent a SIGINT to the "systemd --user" process above (PID 853), then all the processes promptly go away. This needs to occur on logout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+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 1871950] Re: I am unable to check the checkmark next to "Canonical Partners" in the software-properties menu
let's consider it duplicate but launchpad timeouts when trying to mark it such so closing, please subscribe to bug #1727908 instead ** Changed in: software-properties (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1871950 Title: I am unable to check the checkmark next to "Canonical Partners" in the software-properties menu Status in software-properties package in Ubuntu: Invalid Bug description: Whenever I attempt to click the "Canonical Partners" checkbox in the Other Sources section of Software Properties, the software ignores the clicks and the checkmark remains unchecked. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Thu Apr 9 18:00:48 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1871950/+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 1872041] Re: cupsd assert failure: free(): invalid pointer while printing
*** This bug is a duplicate of bug 1846334 *** https://bugs.launchpad.net/bugs/1846334 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1846334, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872041/+attachment/5351187/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351190/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351203/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351205/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351206/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351207/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351208/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1846334 cupsd assert failure: free(): invalid pointer ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1872041 Title: cupsd assert failure: free(): invalid pointer while printing Status in cups package in Ubuntu: New Bug description: Starting a job to a printer through Wifi network, cupsd failed, and network printers discovery (and availability) stopped. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-daemon 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AssertionMessage: free(): invalid pointer CasperMD5CheckResult: skip CupsErrorLog: E [10/Apr/2020:00:00:21 +0200] Missing value on line 1204 of /var/cache/cups/job.cache. W [10/Apr/2020:09:16:17 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'C48x-Series-Gray..\' already exists W [10/Apr/2020:09:16:17 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'C48x-Series-CMYK..\' already exists E [10/Apr/2020:11:31:51 +0200] [Job 196] File \'\' not found E [10/Apr/2020:11:34:57 +0200] [Job 197] No destination host name supplied by cups-browsed for printer \"Samsung_C48x_Series_SEC8425199A158D_\", is cups-browsed running? Date: Fri Apr 10 11:32:38 2020 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-21 (413 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: device for C48x-Series: usb://Samsung/C48x%20Series?serial=08GMB8GM5E0076E=1 device for Samsung_C48x_Series_SEC8425199A158D_: implicitclass://Samsung_C48x_Series_SEC8425199A158D_/ device for toshiba3505_fernbach1_MacBook_Pro_6_: ///dev/null device for TOSHIBA_e_STUDIO2000AC_11689878: dnssd://TOSHIBA%20e-STUDIO2000AC-11689878._ipp._tcp.local/?uuid=1a657c0f-8d51-4514-8e3b-c1c5fffbc672 device for TOSHIBA_e_STUDIO257_11225681: ipp://MFP11225681.local:631/Print MachineType: HP HP ProBook 430 G5 Papersize: a4 PpdFiles: Samsung_C48x_Series_SEC8425199A158D_: Samsung C48x Series, driverless, cups-filters 1.27.3 C48x-Series: Samsung C48x Series PS TOSHIBA_e_STUDIO257_11225681: TOSHIBA e-STUDIO257, driverless, cups-filters 1.20.2 TOSHIBA_e_STUDIO2000AC_11689878: e-STUDIO2000AC ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffbc76c8285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7ffbc76c64ae "free(): invalid pointer") at malloc.c:5347 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /usr/lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: Upgraded to focal on 2020-03-20 (20
[Touch-packages] [Bug 1870601] Re: Software & Updates window stops responding after I click "prereleased updates"
no error, even when it exit? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1870601 Title: Software & Updates window stops responding after I click "prereleased updates" Status in software-properties package in Ubuntu: Incomplete Bug description: Whenever I check the "Prerelease updates" checkbox in Software & Updates, the app stops responding and Ubuntu asks me to force-quit, ever single time. software-properties-gtk: Installed: 0.98.7 Candidate: 0.98.7 Version table: *** 0.98.7 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status Description: Ubuntu Focal Fossa (development branch) Release: 20.04 This issue happened after I booted the PC for the first time and logged in, and then opened Software & Updates after Ubuntu said updates were available and downloaded. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Fri Apr 3 14:52:37 2020 InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1870601/+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 1846334] Re: cupsd assert failure: free(): invalid pointer
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Confirmed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Ok, I'm a machine where I get the issue now editing /usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py l853 in def on_isv_source_toggled to add (before the try) import time time.sleep(0.1) seems enough to workaround the bug ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-shell (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Invalid Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1846334] Re: cupsd assert failure: free(): invalid pointer
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Confirmed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+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 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
Same problem on Lenovo IdeaPad 310-15IKB, ubuntu 19.10 with kernel 5.3.0-46. Muting the right channel solved the problem tempuraly. -- 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/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) Status in alsa-driver package in Ubuntu: Confirmed Bug description: This is a metabug for all machines that are having phase inverted internal microphones. If your internal mic is either completely silent (no signal), or you can possibly pick a very small sound, with much background noise, even though you have set gain to maximum, there is something you could try. Install the pavucontrol application, start it and go to the "Input Devices" tab. Unlock the channels (there is a keylock icon), then mute the right channel while keeping the left channel at the volume you want. If the internal mic is now working correctly, you have an inverted internal mic, so that your right channel cancels out the left one. (If you're not running PulseAudio, you can try doing the same through AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try changing "Capture" level or "Internal Mic" or "Internal Mic Boost" using the Q,E,Z,C keys.) If so, please file a separate bug against the alsa-driver for your issue, make sure hardware info gets attached to it (either alsa-info as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones that follows when you do "ubuntu-bug alsa-driver" ), then write a comment in this bug, with your machine name and a pointer to the other bug. As time permits, I'll try to work on fixing them for the next Ubuntu release. Thanks! -- David Henningsson To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+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 1872000] Re: 2020'Q1 Intel new media release
This bug was fixed in the package intel-mediasdk - 20.1.0-0ubuntu1 --- intel-mediasdk (20.1.0-0ubuntu1) focal; urgency=medium * New upstream release. (LP: #1872000) * control: Use debhelper-compat, bump to 12. * control: Bump policy to 4.5.0. -- Timo Aaltonen Fri, 10 Apr 2020 09:58:14 +0300 ** Changed in: intel-mediasdk (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1872000 Title: 2020'Q1 Intel new media release Status in intel: New Status in intel-gmmlib package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: New Status in intel-media-driver-non-free package in Ubuntu: New Status in intel-mediasdk package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in libva-utils package in Ubuntu: New Bug description: Description: Open Source Media Stack 2020’Q1 release is available for customers with below improvements. 1.Capability extension. Enabled HEVC SCC Decoding and Tile mode support for TGL, added AYUV/ARGB10/Y410 format support in HEVC VDEnc. 2.SW modularity & extendibility enhancement by refactoring VP SFC, MediaOS and MSDK HEVC encoding. 3.Better performance, by enabling VP9 VDEnc scalability and HEVC VDEnc DirtyROI. 4.New MSDK API and features: Media SDK API v1.32 added SCC HEVC decoding, VP mirroring, Tile mode support, and Sliding Window/Weighted Prediction/Fade Detection support for HEVC encoding. • Media driver: intel-media-20.1.1 • Media SDK: intel-mediasdk-20.1.0 • Libva: 2.7.0 • Libva-utils: 2.7.1 • Gmmlib: intel-gmmlib-20.1.1 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1872000/+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 1869913] Re: "Click or press a key to unlock" string not translated into french
language-pack-gnome-fr 1:20.04+20200407 is now available in Focal, could you check if this resolves the issue? (I don't know if the date format has been changed/affected, that might be a separate issue) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-fr in Ubuntu. https://bugs.launchpad.net/bugs/1869913 Title: "Click or press a key to unlock" string not translated into french Status in language-pack-gnome-fr package in Ubuntu: Fix Committed Bug description: On the lockscreen, the "Click or press a key to unlock" string is not translated, at least in french. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 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: ubuntu:GNOME Date: Tue Mar 31 14:56:11 2020 InstallationDate: Installed on 2019-02-21 (404 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-fr/+bug/1869913/+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 1868319] Re: PCI/internal sound card not detected
@David, No need to change alsa-base.conf after every update. And from -42, it enabled the dmic_detect by default. And it introduced a regression from stable patches. It is fixed in the -46. Even in 18.04, you could still try with the symbollink. Please edit alsa-base.conf to remove the dmic_detect=0, then generate link as #10, please test it and upload the dmesg. After that, you could delete that symbollink and restore the dmic_detect=0 in the alsa-base.conf. thx -- 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/1868319 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.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: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+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 1871185] Re: urls in ubuntu-bugs dialog not really clickable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1871185 Title: urls in ubuntu-bugs dialog not really clickable Status in apport package in Ubuntu: Confirmed Bug description: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+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 1871185] Re: urls in ubuntu-bugs dialog not really clickable
** Tags added: focal -- 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/1871185 Title: urls in ubuntu-bugs dialog not really clickable Status in apport package in Ubuntu: Confirmed Bug description: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+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 1871950] Re: I am unable to check the checkmark next to "Canonical Partners" in the software-properties menu
Thanks, that looks similar to bug #1727908 ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1871950 Title: I am unable to check the checkmark next to "Canonical Partners" in the software-properties menu Status in software-properties package in Ubuntu: New Bug description: Whenever I attempt to click the "Canonical Partners" checkbox in the Other Sources section of Software Properties, the software ignores the clicks and the checkmark remains unchecked. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Thu Apr 9 18:00:48 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1871950/+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 1871952] Re: Ubuntu falsely claims via a notificat ion that I have broken packages, even though I am using a fresh install without updating any packages yet.
Thank you for your bug report. WHat's the output of? $ /usr/lib/update-notifier/apt-check ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871952 Title: Ubuntu falsely claims via a notificat ion that I have broken packages, even though I am using a fresh install without updating any packages yet. Status in apt package in Ubuntu: Incomplete Bug description: After logging into Ubuntu after installing the beta, I changed the update settings to allow proposed updates and backports. I then refreshed the cache and checked for updates. APT said no errors. However, on the menu bar, I received a notifcation saying brokenPackages > 0, even though that is not true and my system is working without issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Thu Apr 9 18:13:10 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: apt 2.0.1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1871952/+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 1868319] Re: PCI/internal sound card not detected
@Hui, First of all thanks for the response - the trick with alsa-base.conf worked fine. Sound is restored. I'm guessing I'll have to edit alsa-base.conf after every update? If so, is there a more permanent solution? Also I'm not on 19.10, I'm on 18.04. And what happened with sof-firmware between kernels -40 and -42 (that's when sound disappeared)? -- 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/1868319 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.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: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+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 1872034] [NEW] [Focal] No HDMI output through thunderbolt docking station
Public bug reported: I can find monitor in display list, but no output from it. Also, I can't switch to extend mode, it failed to apply the setting and switched back to mirror mode. [Steps] 1. Connect a thunderbolt docking station to thunderbolt port. 2. Connect HDMI monitor to HDMI port on the docking station. 3. Switch mode in display setting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:44:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-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 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/1872034 Title: [Focal] No HDMI output through thunderbolt docking station Status in xorg package in Ubuntu: New Bug description: I can find monitor in display list, but no output from it. Also, I can't switch to extend mode, it failed to apply the setting and switched back to mirror mode. [Steps] 1. Connect a thunderbolt docking station to thunderbolt port. 2. Connect HDMI monitor to HDMI port on the docking station. 3. Switch mode in display setting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:44:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-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
[Touch-packages] [Bug 1871972] Re: Update pango for Unicode 13.0
Jeremy, you mean 20.04 when you wrote 18.04 there right? I also saw an update in the queue from you with what looks like the patch described there so I'm going to mark the bug as fix commit and assign to you to reflect the status ** Changed in: pango1.0 (Ubuntu) Importance: Undecided => Low ** Changed in: pango1.0 (Ubuntu) Status: New => Fix Committed ** Changed in: pango1.0 (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871972 Title: Update pango for Unicode 13.0 Status in pango1.0 package in Ubuntu: Fix Committed Bug description: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ Pango is used by many apps (particularly GTK apps) to display emoji. By doing this update for Ubuntu 18.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts- noto-color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. References =- https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 https://emojipedia.org/emoji-13.0/ https://github.com/googlefonts/noto-emoji/releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+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 1872028] [NEW] [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound from internal speaker
Public bug reported: [Reproduce steps] 1. Install 20.04 daily build on 4/9. 2. Do dist-upgrade after installation. 3. Go to System Setting->Sound->Output, press the test button. 4. There is no sound output while press the Front right and Front left button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1358 F pulseaudio /dev/snd/pcmC0D0c: u 1358 F...m pulseaudio /dev/snd/pcmC0D0p: u 1358 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 04:11:26 2020 InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) 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 Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1358 F pulseaudio /dev/snd/pcmC0D0c: u 1358 F...m pulseaudio /dev/snd/pcmC0D0p: u 1358 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: HP dmi.bios.version: R12 Ver. 02.03.01 dmi.board.name: 85A2 dmi.board.vendor: HP dmi.board.version: KBC Version 08.93.00 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR12Ver.02.03.01:bd09/26/2019:svnHP:pnHPProOne400G520.0-inAll-in-One:pvr:rvnHP:rn85A2:rvrKBCVersion08.93.00:cvnHP:ct13:cvr: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP ProOne 400 G5 20.0-in All-in-One dmi.product.sku: 6AE44AV dmi.sys.vendor: HP ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1872028 Title: [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound from internal speaker Status in alsa-driver package in Ubuntu: New Bug description: [Reproduce steps] 1. Install 20.04 daily build on 4/9. 2. Do dist-upgrade after installation. 3. Go to System Setting->Sound->Output, press the test button. 4. There is no sound output while press the Front right and Front left button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1358 F pulseaudio /dev/snd/pcmC0D0c: u 1358 F...m pulseaudio /dev/snd/pcmC0D0p: u 1358 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 04:11:26 2020 InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) 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 Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1358 F pulseaudio /dev/snd/pcmC0D0c: u 1358 F...m pulseaudio /dev/snd/pcmC0D0p: u 1358 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: HP dmi.bios.version: R12 Ver. 02.03.01 dmi.board.name: 85A2 dmi.board.vendor: HP dmi.board.version: KBC Version 08.93.00 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR12Ver.02.03.01:bd09/26/2019:svnHP:pnHPProOne400G520.0-inAll-in-One:pvr:rvnHP:rn85A2:rvrKBCVersion08.93.00:cvnHP:ct13:cvr: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP ProOne 400 G5 20.0-in All-in-One dmi.product.sku: 6AE44AV dmi.sys.vendor: HP To manage notifications about this bug go to:
[Touch-packages] [Bug 1872016] Re: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1872016 Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in ibus package in Ubuntu: New Bug description: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872016/+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 1871615] Re: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt
@jdstrand @seth-arnold I may have fixed the issue in 2.2, please monitor if it occurs again with 2.2 which hopefully gets accepted today. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Incomplete -- 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/1871615 Title: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt Status in apparmor package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: I have no definite idea what happened, it just popped up randomly. I can only assume it was trying to show the usual update notification ProblemType: Package DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 AptOrdering: apparmor:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Apr 8 13:57:33 2020 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2020-03-25 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=66ca0e88-1f73-48ce-a0ae-cfa14442ffe1 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: apparmor Syslog: Apr 8 13:04:35 sebipc dbus-daemon[1090]: [system] AppArmor D-Bus mediation is enabled Apr 8 13:04:44 sebipc dbus-daemon[1479]: [session uid=125 pid=1479] AppArmor D-Bus mediation is enabled Apr 8 13:05:16 sebipc dbus-daemon[2072]: [session uid=1000 pid=2072] AppArmor D-Bus mediation is enabled Apr 8 13:55:52 sebipc dbus-daemon[2072]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/" interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" name="com.canonical.Unity" pid=11890 label="snap.telegram-desktop.telegram-desktop" peer_pid=2359 peer_label="unconfined" Apr 8 13:55:53 sebipc dbus-daemon[2072]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/ScreenSaver" interface="org.freedesktop.ScreenSaver" member="GetSessionIdleTime" mask="send" name="org.freedesktop.ScreenSaver" pid=11890 label="snap.telegram-desktop.telegram-desktop" peer_pid=2462 peer_label="unconfined" Title: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apparmor.d.abstractions.base: 2020-03-26T13:00:28.401582 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1871615/+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 1872016] [NEW] package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1872016 Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in ibus package in Ubuntu: New Bug description: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872016/+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 1872015] [NEW] resolv.conf symlink is broken
Public bug reported: see description here: https://askubuntu.com/a/1041631/436647 *The Default* $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 39 Apr 26 12:07 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf I deleted this and pointed to the correct file. After rebooting, this solved my issue. And I was even able to switch networks on my laptop and the DNS switched correctly. Of course when on external networks I can't resolve any of my local machines but that is expected. As soon as I switch back to my local network, all the local machines resolve correctly because my router is the DNS. - *The Fix* $ sudo rm -f /etc/resolv.conf $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 32 May 29 08:48 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf $ sudo reboot ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Apr 10 07:04:17 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP ProLiant MicroServer Gen8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=2351ab04-e595-4761-ad9d-d2d5975d1b08 ro maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2014 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ06:bd06/06/2014:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP mtime.conffile..etc.systemd.resolved.conf: 2020-04-10T06:39:38.172640 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan uec-images -- 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/1872015 Title: resolv.conf symlink is broken Status in systemd package in Ubuntu: New Bug description: see description here: https://askubuntu.com/a/1041631/436647 *The Default* $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 39 Apr 26 12:07 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf I deleted this and pointed to the correct file. After rebooting, this solved my issue. And I was even able to switch networks on my laptop and the DNS switched correctly. Of course when on external networks I can't resolve any of my local machines but that is expected. As soon as I switch back to my local network, all the local machines resolve correctly because my router is the DNS. - *The Fix* $ sudo rm -f /etc/resolv.conf $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 32 May 29 08:48 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf $ sudo reboot ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Apr 10 07:04:17 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP ProLiant MicroServer Gen8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=2351ab04-e595-4761-ad9d-d2d5975d1b08 ro maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2014 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ06:bd06/06/2014:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP mtime.conffile..etc.systemd.resolved.conf: 2020-04-10T06:39:38.172640 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872015/+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 1650683] Re: tracker runs despite search being set to off
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tracker (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1650683 Title: tracker runs despite search being set to off Status in tracker package in Ubuntu: Confirmed Bug description: The master switch in the Search control panel is set to OFF (see attached screenshot). Yet the tracker daemon runs (poorly, cf. bug #1650681). This could under some circumstances lead to privacy violations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1650683/+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 1871540] Re: Include IPs in apt-get output
@juliank : could we at least get a debug flag of some sort that would just log everything ? With timings ? So that we could map, for each file, the IP of the server it got downloaded from, time when the download started (maybe even time when the HTTP request got sent, time when we start receiving data), time at the end of transfer. And also, very important, proxy information as well, if any. And so whenever someones reports "slowness" or misbehaviour, we can give him this flag and ask for output and debug on our end. Would that be possible ? Thanks ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871540 Title: Include IPs in apt-get output Status in apt package in Ubuntu: New Bug description: Hi, When running apt-get update/dist-upgrade, output looks like this: | Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease | Get:7 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [972 kB] | Get:8 http://archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata [29.1 kB] | ... | Need to get 101 MB of archives. | After this operation, 10.5 MB of additional disk space will be used. | Do you want to continue? [Y/n] y | Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 dpkg amd64 1.19.7ubuntu3 [1128 kB] | Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 login amd64 1:4.8.1-1ubuntu4 [221 kB] | Get:3 http://archive.ubuntu.com/ubuntu focal/main amd64 libc6-dbg amd64 2.31-0ubuntu7 [5673 kB] With various online CI/CD services such as GitHub Actions, it looks like this: | Get:14 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [833 kB] | Get:16 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [292 kB] | Get:17 http://azure.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1044 kB] | ... | Get:31 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 cmake amd64 3.10.2-1ubuntu2.18.04.1 [3152 kB] | Get:32 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic/main amd64 gdb amd64 8.2-0ubuntu1~18.04 [3024 kB] | Get:33 http://azure.archive.ubuntu.com/ubuntu bionic/universe amd64 epstool amd64 3.08+repack-7 [108 kB] archive.u.c resolves to multiple IPs. azure.archive.u.c resolves to a load balancer (Azure's Traffic Manager). It would be nice if we also had the IPs of the servers/hosts in the output and would really help us in determining which servers or regions users may be experiencing issues with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1871540/+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 1872000] Re: 2020'Q1 Intel new media release
libva 2.7.0 is in ** Changed in: libva (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1872000 Title: 2020'Q1 Intel new media release Status in intel: New Status in intel-gmmlib package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: New Status in intel-media-driver-non-free package in Ubuntu: New Status in intel-mediasdk package in Ubuntu: New Status in libva package in Ubuntu: Fix Released Status in libva-utils package in Ubuntu: New Bug description: Description: Open Source Media Stack 2020’Q1 release is available for customers with below improvements. 1.Capability extension. Enabled HEVC SCC Decoding and Tile mode support for TGL, added AYUV/ARGB10/Y410 format support in HEVC VDEnc. 2.SW modularity & extendibility enhancement by refactoring VP SFC, MediaOS and MSDK HEVC encoding. 3.Better performance, by enabling VP9 VDEnc scalability and HEVC VDEnc DirtyROI. 4.New MSDK API and features: Media SDK API v1.32 added SCC HEVC decoding, VP mirroring, Tile mode support, and Sliding Window/Weighted Prediction/Fade Detection support for HEVC encoding. • Media driver: intel-media-20.1.1 • Media SDK: intel-mediasdk-20.1.0 • Libva: 2.7.0 • Libva-utils: 2.7.1 • Gmmlib: intel-gmmlib-20.1.1 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1872000/+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 1871997] Re: The primary display will cause black screen when external 4K monitor is configured to flipped
Thank you for your bug report. Could you add your 'journalctl -b 0' log to the bug after getting the issue? ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1871997 Title: The primary display will cause black screen when external 4K monitor is configured to flipped Status in xorg package in Ubuntu: Incomplete Bug description: The primary (built-in) display will cause black screen when external 4K monitor is configured to flipped Steps to reproduce: 1. plug 4K monitor via HDMI 2. open gnome-control-center 3. select Displays -> Orientation -> Landscape (flipped) 4. apply 5. black screen on built-in displays The primary display can be recovered if HDMI cable is re-plugged again. Machine: Dell XPS 13 9380 (Intel Coffee Lake) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:24:13 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-07 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=60712c21-4620-4018-821e-afb9a77f9ec8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.10.2 dmi.board.name: 0SSY11 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.10.2:bd01/15/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0SSY11:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871997/+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 1872000] Re: 2020'Q1 Intel new media release
gmmlib is already at 20.1.1 ** Package changed: ubuntu => intel-media-driver (Ubuntu) ** Also affects: intel-media-driver-non-free (Ubuntu) Importance: Undecided Status: New ** Also affects: intel-gmmlib (Ubuntu) Importance: Undecided Status: New ** Also affects: intel-mediasdk (Ubuntu) Importance: Undecided Status: New ** Also affects: libva (Ubuntu) Importance: Undecided Status: New ** Also affects: libva-utils (Ubuntu) Importance: Undecided Status: New ** Changed in: intel-gmmlib (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1872000 Title: 2020'Q1 Intel new media release Status in intel: New Status in intel-gmmlib package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: New Status in intel-media-driver-non-free package in Ubuntu: New Status in intel-mediasdk package in Ubuntu: New Status in libva package in Ubuntu: Fix Released Status in libva-utils package in Ubuntu: New Bug description: Description: Open Source Media Stack 2020’Q1 release is available for customers with below improvements. 1.Capability extension. Enabled HEVC SCC Decoding and Tile mode support for TGL, added AYUV/ARGB10/Y410 format support in HEVC VDEnc. 2.SW modularity & extendibility enhancement by refactoring VP SFC, MediaOS and MSDK HEVC encoding. 3.Better performance, by enabling VP9 VDEnc scalability and HEVC VDEnc DirtyROI. 4.New MSDK API and features: Media SDK API v1.32 added SCC HEVC decoding, VP mirroring, Tile mode support, and Sliding Window/Weighted Prediction/Fade Detection support for HEVC encoding. • Media driver: intel-media-20.1.1 • Media SDK: intel-mediasdk-20.1.0 • Libva: 2.7.0 • Libva-utils: 2.7.1 • Gmmlib: intel-gmmlib-20.1.1 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1872000/+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 1871540] Re: Include IPs in apt-get output
** Changed in: apt (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871540 Title: Include IPs in apt-get output Status in apt package in Ubuntu: New Bug description: Hi, When running apt-get update/dist-upgrade, output looks like this: | Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease | Get:7 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [972 kB] | Get:8 http://archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata [29.1 kB] | ... | Need to get 101 MB of archives. | After this operation, 10.5 MB of additional disk space will be used. | Do you want to continue? [Y/n] y | Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 dpkg amd64 1.19.7ubuntu3 [1128 kB] | Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 login amd64 1:4.8.1-1ubuntu4 [221 kB] | Get:3 http://archive.ubuntu.com/ubuntu focal/main amd64 libc6-dbg amd64 2.31-0ubuntu7 [5673 kB] With various online CI/CD services such as GitHub Actions, it looks like this: | Get:14 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [833 kB] | Get:16 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [292 kB] | Get:17 http://azure.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1044 kB] | ... | Get:31 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 cmake amd64 3.10.2-1ubuntu2.18.04.1 [3152 kB] | Get:32 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic/main amd64 gdb amd64 8.2-0ubuntu1~18.04 [3024 kB] | Get:33 http://azure.archive.ubuntu.com/ubuntu bionic/universe amd64 epstool amd64 3.08+repack-7 [108 kB] archive.u.c resolves to multiple IPs. azure.archive.u.c resolves to a load balancer (Azure's Traffic Manager). It would be nice if we also had the IPs of the servers/hosts in the output and would really help us in determining which servers or regions users may be experiencing issues with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1871540/+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
