[Touch-packages] [Bug 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up
/etc/systemd/system/ssh.service.d/override.conf [Unit] After=network-online.target auditd.service -- 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/216847 Title: sshd will not start at boot if ListenAddress is set, because network interface is not yet up Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Confirmed Bug description: Binary package hint: openssh-server The sshd will not start at boot if the ListenAddress option in /etc/ssh/sshd_config is set to an IPv4 address other then 0.0.0.0 . I am using Ubuntu 7.10 and the version 1:4.6p1-5ubuntu0.2 of the openssh-server package. I would expect that sshd is started after boot but it will not and I found this in /var/log/auth.log: sshd[4527]: error: Bind to port 22 on 10.1.1.22 failed: Cannot assign requested address. sshd[4527]: fatal: Cannot bind any address. Once the System is started you can start/stop the sshd with the /etc/init.d/ssh script without any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/216847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841745] Re: Update to 1.2.0
** Changed in: libxt (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxt in Ubuntu. https://bugs.launchpad.net/bugs/1841745 Title: Update to 1.2.0 Status in libxt package in Ubuntu: Fix Released Status in libxt package in Debian: Fix Released Bug description: The new version has non trivial change and is not in Debian/Fedora yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxt/+bug/1841745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
I've been scratching my head over this regression [1] for a while now, in the context of running a hirsute container on a 20.04 host (in particular, a GitHub workflow machine) In my case, the symptom is that after upgrading glibc, `which` is broken; that of course also uses faccessat(), similar to test -x. I tried all sorts of the "usual" workarounds, as seccomp has been giving trouble for a while now [2]. But this failure is robust against fuse- overlayfs vs. vfs (inefficient full copies of the file system), root vs. user podman, podman vs. docker, and, relevant for this bug, it *also happens* with --security-opt=seccomp=unconfined and/org --privileged, both of which should disable seccomp. Hence I believe this bug can't at least only be in libseccomp. [1] https://github.com/martinpitt/umockdev/runs/1984769591?check_suite_focus=true#step:3:1019 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1900021 ** Bug watch added: Red Hat Bugzilla #1900021 https://bugzilla.redhat.com/show_bug.cgi?id=1900021 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in glibc package in Ubuntu: Triaged Status in libseccomp package in Ubuntu: Fix Committed Status in glibc source package in Hirsute: Triaged Status in libseccomp source package in Hirsute: Fix Committed Bug description: glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899193] Re: local denial of service due to parsing bugs in arfile.cc
** Information type changed from Private Security to Public Security -- 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/1899193 Title: local denial of service due to parsing bugs in arfile.cc Status in apt package in Ubuntu: Fix Released Status in aptdaemon package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Released Bug description: # GitHub Security Lab (GHSL) Vulnerability Report: `GHSL-2020-168`, `GHSL-2020-169`, `GHSL-2020-170` The [GitHub Security Lab](https://securitylab.github.com) team has identified potential security vulnerabilities in aptd. We are committed to working with you to help resolve these issues. In this report you will find everything you need to effectively coordinate a resolution of these issues with the GHSL team. If at any point you have concerns or questions about this process, please do not hesitate to reach out to us at `security...@github.com` (please include `GHSL-2020-168`, `GHSL-2020-169`, or `GHSL-2020-170` as a reference). If you are _NOT_ the correct point of contact for this report, please let us know! ## Summary The aptd daemon is a system service for installing and updating packages. It is accessible via [dbus](https://www.freedesktop.org/wiki/Software/dbus/) and has a method named "InstallFile" which is used for installing local `.deb` packages. Although polkit is used to prevent an unprivileged user from using "InstallFile" to install a malicious `.deb` package, it does not prevent aptd from parsing the contents of the `.deb` file. The parsing logic is provided by two packages, [libapt-pkg- dev](https://packages.ubuntu.com/focal/libapt-pkg-dev) and [python- apt](https://packages.ubuntu.com/source/focal/python-apt), and is implemented in C. These two packages contain several bugs, which an unprivileged user can exploit to trigger a local denial of service attack. ## Product aptd ## Tested Version * libapt-pkg-dev: version 2.0.2ubuntu0.1 * python-apt: 2.0.0ubuntu0.20.04.1 * Tested on Ubuntu 20.04.1 LTS ## Details ### Issue 1: aptd crash due to integer overflow in arfile.cc (GHSL-2020-168) A crafted `.deb` package can trigger a negative integer overflow at [arfile.cc, line 116](https://git.launchpad.net/ubuntu/+source/apt/tree/apt- pkg/contrib/arfile.cc?h=applied/ubuntu/focal- updates=4c264e60b524855b211751e1632ba48526f6b44d#n116): ```c Memb->Size -= Len; ``` Due to the integer overflow, the value of `Memb->Size` is `0x`. This leads to an out-of-memory error at [arfile.cc, line 602](https://git.launchpad.net/ubuntu/+source/python- apt/tree/python/arfile.cc?h=applied/ubuntu/focal- updates=0f7cc93acdb51d943114f1cd79002288c4ca4d24#n602): ```c char* value = new char[member->Size]; ``` The out-of-memory error causes aptd to crash. Please note that the source locations above refer to two separate files, both named `arfile.cc`. The first is from the libapt-pkg-dev package and the second is from the python-apt package. To trigger the crash, first use the attached source file named "createdeb.c" to generate the malicious `.deb` file: ```bash gcc createdeb.c -o createdeb ./createdeb crash test.deb ``` Now use `dbus-send` to send the malicious `.deb` file to aptd: ```bash $ dbus-send --system --type="method_call" --print-reply --dest=org.debian.apt /org/debian/apt org.debian.apt.InstallFile string:`realpath test.deb` boolean:true method return time=1602245339.731762 sender=:1.287 -> destination=:1.288 serial=8 reply_serial=2 string "/org/debian/apt/transaction/90f29de930854568964af1918f6ca5eb" $ dbus-send --system --type="method_call" --print-reply --dest=org.debian.apt /org/debian/apt/transaction/90f29de930854568964af1918f6ca5eb org.debian.apt.transaction.Run ``` Note that you need to use the "transaction id" returned by the first `dbus-send` in the second `dbus-send` command. Impact This issue may lead to local denial of service. Resources I have attached `createdeb.c`, which can be used to generate the malicious `.deb` file. ### Issue 2: aptd infinite loop due to integer overflow in arfile.cc (GHSL-2020-169) This issue is very similar to issue 1, but is caused by a different bug. This bug occurs during the call to `StrToNum` at [arfile.cc, line 92](https://git.launchpad.net/ubuntu/+source/apt/tree/apt- pkg/contrib/arfile.cc?h=applied/ubuntu/focal- updates=4c264e60b524855b211751e1632ba48526f6b44d#n92): ```c StrToNum(Head.Size,Memb->Size,sizeof(Head.Size)) == false) ``` The bug is due to the use of `strtoul` in [StrToNum](https://git.launchpad.net/ubuntu/+source/apt/tree/apt- pkg/contrib/strutl.cc?h=applied/ubuntu/focal- updates=4c264e60b524855b211751e1632ba48526f6b44d#n1169): ```c
[Touch-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
Also caused FTBFS in ukui-control-center
https://launchpadlibrarian.net/524640709/buildlog_ubuntu-hirsute-amd64
.ukui-control-center_3.0.2-2_BUILDING.txt.gz
** Also affects: ukui-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1916705
Title:
glib2.0 >=2.67.3 breaks include from an extern C context
Status in glib2.0 package in Ubuntu:
New
Status in qemu package in Ubuntu:
Triaged
Status in ukui-control-center package in Ubuntu:
New
Bug description:
qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz
Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages
Error:
../../disas/arm-a64.cc
In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
from
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
from /usr/include/glib-2.0/glib/gtypes.h:32,
from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
from ../../disas/arm-a64.cc:21:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
56 | template
| ^~~~
../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
20 | extern "C" {
| ^~
Also in disas/nanomips.cpp, ...
And indeed disas/arm-a64.cc has:
20 extern "C" {
21 #include "qemu/osdep.h"
22 #include "disas/dis-asm.h"
23 }
Through the chain of headers as reported above this gets to the templates
in /usr/include/c++/10/type_traits which fails due to that.
So C++ constructs within a C scope which is this bug.
Upstream qemu has not recently changed yet for this.
The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
Include osdep.h first" by Peter Maydell.
But what was different before to break it now?
To find that I was comparing Hirsute vs Hirsute-proposed ...
It is indeed failing in -proposed but working in hirsute-release.
10.2.1-20ubuntu1 : bad
repro in broken build:
$ cd /root/qemu-5.2+dfsg/b/qemu
$ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp
With that I have a test env...
Doko asked me to test
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
It must be something else.
The difference were ~340 packages I was upgrading them to spot what broke it.
I eventually found glib 2.66 -> 2.67 to break it.
libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1]
libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
Old:
/*
* We can
[Touch-packages] [Bug 1917091] Re: package linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Package changed: ubuntu => initramfs-tools (Ubuntu) -- 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/1917091 Title: package linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: none ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 26 18:08:41 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-30 (272 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917091] [NEW] package linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
You have been subscribed to a public bug: none ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 26 18:08:41 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-30 (272 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- package linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 https://bugs.launchpad.net/bugs/1917091 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools 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 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
Also having the same issue, any workarounds besides getting a bluetooth headset? -- 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/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917074] Re: cups ppi parameter should be a string
** Changed in: cups Status: Unknown => New -- 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/1917074 Title: cups ppi parameter should be a string Status in CUPS: New Status in cups package in Ubuntu: New Status in cups-filters package in Ubuntu: New Bug description: cups encode.c treats parameter ppi as an integer, but it should be a string. the image filter drivers expect the form ppi=300x600 to specify source image dpi for images where it is asymmetric. I encountered this issue trying to print full-sized images without scaling on a dymo 450 label printer. This bug causes images to print across 2 labels when trying to use the 300x600dpi graphics mode. This should print a single label: lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 -o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium -o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 ~/Desktop/test_Graphics_portrait.png where the png is a 664*2224 image without any dpi metadata. Instead the ppi option gets sanitized to 300, and the image gets printed across 2 labels. Description: Ubuntu 20.04.2 LTS Release: 20.04 cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1917074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917074] Re: cups ppi parameter should be a string
Thank you very much. ** Changed in: cups Importance: Undecided => Unknown ** Changed in: cups Status: New => Unknown ** Changed in: cups Remote watch: None => github.com/OpenPrinting/cups/issues #115 -- 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/1917074 Title: cups ppi parameter should be a string Status in CUPS: Unknown Status in cups package in Ubuntu: New Status in cups-filters package in Ubuntu: New Bug description: cups encode.c treats parameter ppi as an integer, but it should be a string. the image filter drivers expect the form ppi=300x600 to specify source image dpi for images where it is asymmetric. I encountered this issue trying to print full-sized images without scaling on a dymo 450 label printer. This bug causes images to print across 2 labels when trying to use the 300x600dpi graphics mode. This should print a single label: lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 -o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium -o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 ~/Desktop/test_Graphics_portrait.png where the png is a 664*2224 image without any dpi metadata. Instead the ppi option gets sanitized to 300, and the image gets printed across 2 labels. Description: Ubuntu 20.04.2 LTS Release: 20.04 cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1917074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917074] Re: cups ppi parameter should be a string
i've reported this upstream, the github issue is: https://github.com/OpenPrinting/cups/issues/115 ** Bug watch added: github.com/OpenPrinting/cups/issues #115 https://github.com/OpenPrinting/cups/issues/115 -- 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/1917074 Title: cups ppi parameter should be a string Status in CUPS: New Status in cups package in Ubuntu: New Status in cups-filters package in Ubuntu: New Bug description: cups encode.c treats parameter ppi as an integer, but it should be a string. the image filter drivers expect the form ppi=300x600 to specify source image dpi for images where it is asymmetric. I encountered this issue trying to print full-sized images without scaling on a dymo 450 label printer. This bug causes images to print across 2 labels when trying to use the 300x600dpi graphics mode. This should print a single label: lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 -o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium -o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 ~/Desktop/test_Graphics_portrait.png where the png is a 664*2224 image without any dpi metadata. Instead the ppi option gets sanitized to 300, and the image gets printed across 2 labels. Description: Ubuntu 20.04.2 LTS Release: 20.04 cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1917074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894356] Re: could not acquire name on session bus by simultaneous login by XDMCP and keyboard
** Changed in: lightdm (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1894356 Title: could not acquire name on session bus by simultaneous login by XDMCP and keyboard Status in Light Display Manager: New Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: New Status in lightdm package in Debian: Confirmed Bug description: This symptom is observed with Ubuntu Mate 20.04. 1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as [XDMCPServer] enabled=true and restart lightdm. 2. Login as a normal user from keyboard. 3. Login as the same user as 2 from XDMCP gives "Could not acquire name on session bus" and I cannot login from XDMCP. Without Step 2, XDMCP login succeeds. The same symptom is reported at https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001 which recommends removal of "dbus-user-session" Ubuntu package. I worked around the above issue by putting "unset DBUS_SESSION_BUS_ADDRESS" in /etc/X11/Xsession.d/ The same issue is also reported at https://bugs.launchpad.net/ubuntu-mate/+bug/1769353 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1894356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1900068] Re: Upgrade to zeitgeist-1.0.3
** Changed in: zeitgeist (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1900068 Title: Upgrade to zeitgeist-1.0.3 Status in zeitgeist package in Ubuntu: New Status in zeitgeist package in Debian: Fix Released Bug description: Please do upgrade zeitgeist from current 1.0.2 to 1.0.3. It is required for GNOME Activity Journal to work. GNOME Activity Journal has been ported to GTK3. It will be available in GNOME repos shortly. For more details: https://discourse.gnome.org/t/zeitgeist-gnome-activity- journal-1-0/4521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1900068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914884] Re: udev tries to assign identical name to multiple network cards
closing per comment 1 ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1914884 Title: udev tries to assign identical name to multiple network cards Status in systemd package in Ubuntu: Invalid Bug description: Upon upgrading from U18.04 to U20.04.2, the network interface names became unpredictable. They could be *any* of eth0, eth1, eth2 and ens2. Further inspection shows error messages like "systemd-udevd: eth1: Failed to rename network interface 3 from 'eth1' to 'ens2': File exists" The installation is plain vanilla; in fact, the system had not been used at all yet. Neither of the files '/lib/udev/rules.d/75 -persistent-net-generator.rules', '/etc/udev/rules.d/70-persistent- net.rules' or '/lib/udev/rules.d/71-biosdevname.rules' exist. On U18.04, 'ls /sys/class/net' yielded "enp5s0 enp14s0 enp9s0 lo". After the upgrade, it currently shows "ens2 eth0 eth1 lo". For each of these entries, 'udevadm test-builtin net_id $nic 2>/dev/null' gives the following: /sys/class/net/ens2 ID_NET_NAMING_SCHEME=v245 ID_NET_NAME_MAC=enx002481d13e60 ID_OUI_FROM_DATABASE=Hewlett Packard ID_NET_NAME_PATH=enp14s0 ID_NET_NAME_SLOT=ens2 /sys/class/net/eth0 ID_NET_NAMING_SCHEME=v245 ID_NET_NAME_MAC=enx001018b197dc ID_OUI_FROM_DATABASE=Broadcom ID_NET_NAME_PATH=enp5s0 ID_NET_NAME_SLOT=ens2 /sys/class/net/eth1 ID_NET_NAMING_SCHEME=v245 ID_NET_NAME_MAC=enx00101897069a ID_OUI_FROM_DATABASE=Broadcom ID_NET_NAME_PATH=enp9s0 ID_NET_NAME_SLOT=ens2 This seems to be a case where the naming scheme v245 should be replaced by v247, according to https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.html The situation does not change with passing "net.naming-scheme=latest" to the kernel. The installed version of udev is 245.4-4ubuntu3.4. Since this faulty behavior happened completely out of the blue on a practically pristine LTS installation, I hope to have some kind of solution similar to a backport. Thanks for comments! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES
** Changed in: isc-dhcp (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 isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1894172 Title: isc-dhcp-server using wrong env variable for INTERFACES Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Bionic: Confirmed Status in isc-dhcp source package in Focal: Confirmed Status in isc-dhcp source package in Groovy: Confirmed Bug description: When checking isc-dhcp-server unit file I saw isc-dhcp-server is being started by: ConditionPathExists=/etc/default/isc-dhcp-server ConditionPathExists=|/etc/ltsp/dhcpd.conf ConditionPathExists=|/etc/dhcp/dhcpd.conf [Service] EnvironmentFile=/etc/default/isc-dhcp-server RuntimeDirectory=dhcp-server # The leases files need to be root:dhcpd even when dropping privileges ExecStart=/bin/sh -ec '\ CONFIG_FILE=/etc/dhcp/dhcpd.conf; \ if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \ [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \ chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \ chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \ exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES' But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and $INTERFACESv6. This has only been working because cmdline sets -4 and subnet declaration in dhcpd.conf file makes dhcp-server to bind to the correct interfaces, as it looks like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
While a KeyboardInterrupt handler has been introduced to ubuntu-release-
upgrader apt is actually sending the SIGINT back to the distribution
upgrade process. This can be fixed in apt by removing the following:
--- apt-2.1.10ubuntu0.2/apt-pkg/contrib/fileutl.cc 2021-01-14
03:29:25.0 -0800
+++ apt-2.1.10ubuntu0.3~ppa1/apt-pkg/contrib/fileutl.cc 2021-02-26
09:13:10.0 -0800
@@ -140,10 +140,6 @@
return _error->Errno("waitpid","Couldn't wait for subprocess");
}
- // Restore sig int/quit
- signal(SIGQUIT,SIG_DFL);
- signal(SIGINT,SIG_DFL);
-
// Check for an error code.
if (WIFEXITED(Status) == 0 || WEXITSTATUS(Status) != 0)
{
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Hirsute)
Importance: Undecided => High
** Changed in: apt (Ubuntu Hirsute)
Status: New => Triaged
** Changed in: apt (Ubuntu Hirsute)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
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/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
Status in apt package in Ubuntu:
Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
In Progress
Status in apt source package in Hirsute:
Triaged
Status in ubuntu-release-upgrader source package in Hirsute:
In Progress
Bug description:
As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
version; just all packages including new ones. Version updates had to be
initiated manually, and I was always asked if I really wanted the new ?ubuntu
version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked.
I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a
number of times earlier; just to *check* if the upgrade was on offer; but this
is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected
through an adequate pipe? Are you sitting with full batteries; better
a power supply?" would be convenient; since I am using my PC for
urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898026/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
Looking at the tags that were added by the BZ bridge (targetmilestone- inin2004), it's focal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Tags added: patch -- 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/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917074] Re: cups ppi parameter should be a string
The attachment "cups_ppi_patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1917074 Title: cups ppi parameter should be a string Status in CUPS: New Status in cups package in Ubuntu: New Status in cups-filters package in Ubuntu: New Bug description: cups encode.c treats parameter ppi as an integer, but it should be a string. the image filter drivers expect the form ppi=300x600 to specify source image dpi for images where it is asymmetric. I encountered this issue trying to print full-sized images without scaling on a dymo 450 label printer. This bug causes images to print across 2 labels when trying to use the 300x600dpi graphics mode. This should print a single label: lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 -o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium -o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 ~/Desktop/test_Graphics_portrait.png where the png is a 664*2224 image without any dpi metadata. Instead the ppi option gets sanitized to 300, and the image gets printed across 2 labels. Description: Ubuntu 20.04.2 LTS Release: 20.04 cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1917074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
This bug was fixed in the package network-manager - 1.30.0-1ubuntu1 --- network-manager (1.30.0-1ubuntu1) hirsute; urgency=medium * Resynchronize on Debian, remaining changes: - Use systemd-resolved instead of dnsmasq - debian/control: + Depend on isc-dhcp-client instead of recommends + Recommend network-manager-pptp + Suggest avahi-autoipd for IPv4LL support - debian/rules, debian/network-manager.postinst: + Don't restart NetworkManager on upgrade but recommend restarting the computer - debian/rules, debian/network-manager.postinst: + Don't install sysvinit scripts or migrate from sysvinit - debian/network-manager.postinst: + Don't add the netdev group. + drop in an empty override file for NetworkManager to manage all devices for upgrade from any version, as long as there is no netplan configuration yet. - debian/default-wifi-powersave-on.conf, debian/rules: + Install a config file to enable WiFi powersave - Enable build tests - Add autopkgtests - debian/source_network-manager.py, debian/network-manager.install, debian/network-manager.links: Add apport hook - Add network-manager-config-connectivity-ubuntu package - NetworkManager.conf: disable MAC randomization feature. There is no easy way for desktop users to disable this feature yet. And there are reports that it doesn't work well with some systems. - Update Vcs links to point to Ubuntu branch - Add patches. See patch descriptions for more details: + Provide-access-to-some-of-NM-s-interfaces-to-whoopsie.patch + Update-dnsmasq-parameters.patch + Disable-general-with-expect.patch + libnm-Check-self-still-NMManager-or-not.patch + dns-manager-don-t-merge-split-DNS-search-domains.patch (but disabled) + Read-system-connections-from-run.patch - debian/tests/urfkill-integration - don't stop/start network manager - debian/patches/ubuntu_revert_systemd.patch: + temporarly revert an upstream commit that made udev enabled under lxc, the new systemd doesn't work there (lp: #1914062) -- Sebastien Bacher Thu, 25 Feb 2021 15:30:59 +0100 ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
I've started drafting this patch. I want to prepare a PPA for you to try, can you please let me know which Ubuntu release is best / easiest for you to test? Hirsute? Focal? Bionic? ** Patch added: "dhcp_broadcast_qeth_l3.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914740/+attachment/5467722/+files/dhcp_broadcast_qeth_l3.patch -- 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/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916032] Re: /usr/share/initramfs-tools/hooks/lvm2 does not have executable bit set
** Tags added: hirsute ** Changed in: lvm2 (Ubuntu) Status: Confirmed => Triaged ** Tags added: rls-hh-incoming ** Changed in: lvm2 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1916032 Title: /usr/share/initramfs-tools/hooks/lvm2 does not have executable bit set Status in lvm2 package in Ubuntu: Triaged Bug description: In lvm2 2.03.11-2ubuntu1, /usr/share/initramfs-tools/hooks/lvm2 is not an executable. $ dpkg-deb -c lvm2_2.03.11-2ubuntu1_amd64.deb | grep /usr/share/initramfs-tools/hooks/lvm2 -rw-r--r-- root/root 691 2021-02-08 23:25 ./usr/share/initramfs-tools/hooks/lvm2 Systems whose root filesystem is on LVM will be unable to boot, because /sbin/lvm is not included in initramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1916032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916418] Re: Custom properties set with ENV{WHATEVER} in parent no longer imported with IMPORT{parent} in udev rule
** Tags added: rls-hh-incoming
--
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/1916418
Title:
Custom properties set with ENV{WHATEVER} in parent no longer imported
with IMPORT{parent} in udev rule
Status in systemd package in Ubuntu:
New
Bug description:
DisplayLink uses these udev rules to start the displaylink service
when a displaylink device is plugged in:
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
ATTR{idVendor}=="17e9", IMPORT{builtin}="usb_id",
ENV{DISPLAYLINK_DEVNAME}="$env{DEVNAME}",
ENV{DISPLAYLINK_DEVICE_ID}="$env{ID_BUS}-$env{BUSNUM}-$env{DEVNUM}-$env{ID_SERIAL}",
ENV{REMOVE_CMD}="/opt/displaylink/udev.sh $root
$env{DISPLAYLINK_DEVICE_ID} $env{DISPLAYLINK_DEVNAME}"
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
ATTRS{idVendor}=="17e9", ATTR{bInterfaceClass}=="ff",
ATTR{bInterfaceProtocol}=="03", IMPORT{parent}="DISPLAYLINK*",
RUN+="/opt/displaylink/udev.sh $root $env{DISPLAYLINK_DEVICE_ID}
$env{DISPLAYLINK_DEVNAME}"
The important thing to note here is that the first rule is for the
device that is the parent of the device triggers the second rule, and
the first rule sets ENV{DISPLAYLINK_DEVNAME} and
ENV{DISPLAYLINK_DEVICE_ID}, and the second rule attempts to import
them with IMPORT{parent} and then use them.
This worked fine in 20.04.
It does not work in 21.04.
When the second rule is triggered, DISPLAYLINK_DEVICE_ID and
DISPLAYLINK_DEVNAME are not set.
I have confirmed via udevadm monitor that the variables are getting
set on the parent.
I have confirmed via udevadm info --attribute-walk that the device
triggering the second rule is the child of the device triggering the
first one.
I have tried to import the variables explicitly instead of using a
glob pattern and that doesn't work either.
When I modify the rule to import DEVNAME, ID_BUS, BUSNUM, DEVNUM, and
ID_SERIAL directly, that works. The problem appears to be that these
custom properties we are setting in the parent can't be imported in
the child.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: udev 247.3-1ubuntu2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 60-brother-libsane-type1.rules 99-displaylink.rules~
70-snap.core.rules 70-snap.snap-store.rules 99-x10.rules
60-brother-brscan4-libsane-type1.rules 50-yubikey.rules
70-snap.canonical-livepatch.rules 70-snap.gnome-system-monitor.rules
70-snap.chromium.rules 99-displaylink.rules
Date: Sun Feb 21 19:21:20 2021
InstallationDate: Installed on 2019-01-02 (781 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
MachineType: Acer Predator G6-710
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-14-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to hirsute on 2021-02-21 (0 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1916418/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886235] Re: EMU 1212m card (emu10k1 driver) stops working after PCI reset snd_emu10k1 invalid position buffer size
With an original Soundblaster Live! something like this is happening to me on Linux 5.11. My audio gets completely corrupted and sudo echo 1 > /sys/bus/pci/devices/:05:04.0/reset fixes it (replacing my pci device ofc), if I don't do that I must shutdown my PC and actually turn of my PSU for 10 seconds or I get corrupt audio, it has been working fine for over a year before this. I'm using Bionic if that matters, I might try re-slotting the soundcard itself and see if that helps -- 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/1886235 Title: EMU 1212m card (emu10k1 driver) stops working after PCI reset snd_emu10k1 invalid position buffer size Status in alsa-driver package in Ubuntu: New Bug description: After using my computer for a day or so and coming back to it, my sound card, EMU 1212m, randomly stops to work. And the only solution I have found is completely turn off the power to the motherboard and wait a few minutes until powering back on. When the card works, I am able to reproduce the problem after typing: sudo echo 1 > /sys/bus/pci/devices/:05:04.0/reset Executing that command stops the card from outputting any sound, and I see the following printed in dmesg: [ 73.029029] snd_pcm_update_hw_ptr0: 3153 callbacks suppressed [ 73.029033] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.029114] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.029122] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.040768] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.046208] snd_emu10k1 :05:04.0: interrupt: PCI error [ 73.046235] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046244] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046250] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046255] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046261] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046266] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] Further resets result in [ 497.663897] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.663971] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.663997] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.674025] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.684046] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.694065] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 It seems this is a problem with the driver snd_emu10k1 (maybe invalid buffer size?). In the past, I have used this card in earlier Ubuntu's before without any issues. All I had to do was to build and install the latest alsa-firmware, alsa-lib, and alsa-utils from https://www.alsa-project.org/wiki/Download. It's surprising that this card is not natively supported out of the box in 20.04, but even worse, the driver emu10k1 appears to be broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 14:56:03 2020 InstallationDate: Installed on 2020-06-16 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1409 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 1917074] Re: cups ppi parameter should be a string
Please report this upstream on https://github.com/OpenPrinting/cups as this is not only concerning Ubuntu, but any OS which uses CUPS. -- 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/1917074 Title: cups ppi parameter should be a string Status in CUPS: New Status in cups package in Ubuntu: New Status in cups-filters package in Ubuntu: New Bug description: cups encode.c treats parameter ppi as an integer, but it should be a string. the image filter drivers expect the form ppi=300x600 to specify source image dpi for images where it is asymmetric. I encountered this issue trying to print full-sized images without scaling on a dymo 450 label printer. This bug causes images to print across 2 labels when trying to use the 300x600dpi graphics mode. This should print a single label: lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 -o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium -o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 ~/Desktop/test_Graphics_portrait.png where the png is a 664*2224 image without any dpi metadata. Instead the ppi option gets sanitized to 300, and the image gets printed across 2 labels. Description: Ubuntu 20.04.2 LTS Release: 20.04 cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1917074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917074] Re: cups ppi parameter should be a string
this patch lets the ppi setting be a string ** Attachment added: "cups_ppi_patch" https://bugs.launchpad.net/cups/+bug/1917074/+attachment/5467716/+files/cups_ppi_patch -- 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/1917074 Title: cups ppi parameter should be a string Status in CUPS: New Status in cups package in Ubuntu: New Status in cups-filters package in Ubuntu: New Bug description: cups encode.c treats parameter ppi as an integer, but it should be a string. the image filter drivers expect the form ppi=300x600 to specify source image dpi for images where it is asymmetric. I encountered this issue trying to print full-sized images without scaling on a dymo 450 label printer. This bug causes images to print across 2 labels when trying to use the 300x600dpi graphics mode. This should print a single label: lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 -o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium -o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 ~/Desktop/test_Graphics_portrait.png where the png is a 664*2224 image without any dpi metadata. Instead the ppi option gets sanitized to 300, and the image gets printed across 2 labels. Description: Ubuntu 20.04.2 LTS Release: 20.04 cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1917074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917079] [NEW] package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1
Public bug reported: The same error sent before. I will boot by a USB and try to change the privileges of the file!! ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sudo 1.8.31-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 26 15:33:11 2021 DpkgTerminalLog: Configurando sudo (1.8.31-1ubuntu1.2) ... chown: alterando o dono de '/etc/sudoers': Operação não permitida [1mdpkg:[0m erro ao processar o pacote sudo (--configure): o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 ErrorMessage: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2018-12-12 (806 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: sudo Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to focal on 2020-09-30 (148 days ago) VisudoCheck: /etc/sudoers: análise OK /etc/sudoers.d/README: análise OK mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421 ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1917079 Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 Status in sudo package in Ubuntu: New Bug description: The same error sent before. I will boot by a USB and try to change the privileges of the file!! ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sudo 1.8.31-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 26 15:33:11 2021 DpkgTerminalLog: Configurando sudo (1.8.31-1ubuntu1.2) ... chown: alterando o dono de '/etc/sudoers': Operação não permitida [1mdpkg:[0m erro ao processar o pacote sudo (--configure): o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 ErrorMessage: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2018-12-12 (806 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: sudo Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to focal on 2020-09-30 (148 days ago) VisudoCheck: /etc/sudoers: análise OK /etc/sudoers.d/README: análise OK mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1917079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917073] [NEW] Internal laptop speakers after connecting other sound devices
Public bug reported: I have a bug that I reproduced 2 times: - my laptop is plugged to a screen in HDMI with headphones on the jack port - I unplug my laptop and connect to another screen in HDMI and USB with headphones and microphone connected on the screen - I try to use a bluetooth headphones, it doesn't work - I use the internal laptop speakers, they work - I try to change to everything else (USB audio device or something else) and the sound remains on the internal speakers, even if another output device is selected I'm on Ubuntu 20.04.2 with pulseaudio 1:13.99.1-1ubuntu3.10 on a Dell Latitude E5570. Thank you ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1917073 Title: Internal laptop speakers after connecting other sound devices Status in pulseaudio package in Ubuntu: New Bug description: I have a bug that I reproduced 2 times: - my laptop is plugged to a screen in HDMI with headphones on the jack port - I unplug my laptop and connect to another screen in HDMI and USB with headphones and microphone connected on the screen - I try to use a bluetooth headphones, it doesn't work - I use the internal laptop speakers, they work - I try to change to everything else (USB audio device or something else) and the sound remains on the internal speakers, even if another output device is selected I'm on Ubuntu 20.04.2 with pulseaudio 1:13.99.1-1ubuntu3.10 on a Dell Latitude E5570. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1917073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917074] [NEW] cups ppi parameter should be a string
Public bug reported: cups encode.c treats parameter ppi as an integer, but it should be a string. the image filter drivers expect the form ppi=300x600 to specify source image dpi for images where it is asymmetric. I encountered this issue trying to print full-sized images without scaling on a dymo 450 label printer. This bug causes images to print across 2 labels when trying to use the 300x600dpi graphics mode. This should print a single label: lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 -o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium -o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 ~/Desktop/test_Graphics_portrait.png where the png is a 664*2224 image without any dpi metadata. Instead the ppi option gets sanitized to 300, and the image gets printed across 2 labels. Description:Ubuntu 20.04.2 LTS Release:20.04 cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: cups Importance: Undecided Status: New ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: focal groovy ** Also affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Also affects: cups Importance: Undecided Status: New ** Tags added: focal groovy -- 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/1917074 Title: cups ppi parameter should be a string Status in CUPS: New Status in cups package in Ubuntu: New Status in cups-filters package in Ubuntu: New Bug description: cups encode.c treats parameter ppi as an integer, but it should be a string. the image filter drivers expect the form ppi=300x600 to specify source image dpi for images where it is asymmetric. I encountered this issue trying to print full-sized images without scaling on a dymo 450 label printer. This bug causes images to print across 2 labels when trying to use the 300x600dpi graphics mode. This should print a single label: lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 -o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium -o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 ~/Desktop/test_Graphics_portrait.png where the png is a 664*2224 image without any dpi metadata. Instead the ppi option gets sanitized to 300, and the image gets printed across 2 labels. Description: Ubuntu 20.04.2 LTS Release: 20.04 cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1917074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915547] Re: sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial
** Description changed:
- == Begin SRU Template ==
[Impact]
+ During an upgrade from trusty to xenial, users will be prompted to make a
decision regarding the diff on unattended-upgrades. This is not a good user
experience, specially because the user can make an uninformed decision of
keeping the old config file, which will make unattended-upgrades to not work as
we expect.
+
+ [Test case]
+
+ To reproduce the issue, you can:
+
+ 1. Launch a trusty vm
+ 2. Perform a do-release-upgrade and observe that you will be prompted with
the 50unattended-upgrades change
+
+ To verify that the error is fixed:
+
+ 1. Launch a trusty vm
+ 2. Import this ppa into the system:
+https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
+ 3. Configure do-release-upgrade to allow using third parties during upgrade
+ 4. Run a do-release-upgrade
+ 5. Verify the prompt is no longer there and that we end up with the
+expected 50unattended-upgrades config file
+
+ [Where problems could occur]
+
+ The changes in this package should only surface during an upgrade
+ operation. With this change, we are now delivering a new file to the
+ system and configuring postinst to use it. Because of that, we believe
+ this is the only scenario that could be affected in case of a regression
+ is discovered in the package.
+
+
+ [Discussion]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08
19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644
2020-02-17 18:03:38
@@ -1,11 +1,13 @@
- // Automatically upgrade packages from these (origin:archive) pairs
- Unattended-Upgrade::Allowed-Origins {
+ // Automatically upgrade packages from these (origin:archive) pairs
+ Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
- "${distro_id}:${distro_codename}-security";
- // Extended Security Maintenance; doesn't necessarily exist for
- // every release and this system may not have it installed, but if
- // available, the policy for updates is such that unattended-upgrades
- // should also install from here by default.
+ "${distro_id}:${distro_codename}-security";
+ // Extended Security Maintenance; doesn't necessarily exist for
+ // every release and this system may not have it installed, but if
+ // available, the policy for updates is such that unattended-upgrades
+ // should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
- // "${distro_id}:${distro_codename}-updates";
- // "${distro_id}:${distro_codename}-proposed";
- // "${distro_id}:${distro_codename}-backports";
+ // "${distro_id}:${distro_codename}-updates";
+ // "${distro_id}:${distro_codename}-proposed";
+ // "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- - Add 50unattended-upgrades.md5sum file into the xenial package
- - Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- - Modify ucf command in postinst to be aware of the md5sum history file
+ - Add 50unattended-upgrades.md5sum file into the xenial package
+ - Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
+ - Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
- [Test Case]
We have performed a manual test with a modified version of the xenial package:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
Using that package, we were able to verify that the config change prompt
no longer happens from trusty to xenial.
+ Since we are modifying are features on unattended-upgrades, just adding
+ a new file to package, we don't believe there is any regression
+ potential
- [Regression Potential]
- Since we are modifying are features on unattended-upgrades, just adding a new
file to package, we don't believe there is any regression potential
-
- [Discussion]
-
- == End SRU Template ==
== Changelog ==
- * data: add md5sum history file on the data folder
- - This file contains md5sum of several supported 50unattended-upgrades
- config files
- * data: add xenial md5sum of 50unattented-upgrades into md5sum file
- * debian/postint: make ucf command reference the md5sum history file
+ * data: add md5sum history file on the data folder
+ - This file contains md5sum of several supported
[Touch-packages] [Bug 1905510] Re: utils-linux 2.36.1 breaks user mounts (cifs)
** Changed in: util-linux (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1905510 Title: utils-linux 2.36.1 breaks user mounts (cifs) Status in Util-Linux-ng: Fix Released Status in util-linux package in Ubuntu: Fix Released Status in util-linux package in Debian: New Bug description: I'm working on merging samba from Debian (2:4.13.2+dfsg-1), and while running the autopkgtests for the package I noticed that two tests are failing. These tests attempt to invoke mount.cifs in order to mount a user mount point. I investigated and found this on dmesg: [ 53.586709] CIFS: Attempting to mount //localhost/myshare1760 [ 53.586735] CIFS: Unknown mount option "symfollow" After some more investigation, I noticed that there are both a Debian and an upstream bug reported about this failure, and that upstream has fixed it in util-linux 2.36.2. I would be nice to have this version in hirsute so that cifs user mounts can work again. To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1905510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES
** Changed in: isc-dhcp (Ubuntu Groovy) Status: Fix Released => Confirmed ** Changed in: isc-dhcp (Ubuntu) Status: Confirmed => In Progress ** Changed in: isc-dhcp (Ubuntu) Assignee: (unassigned) => Utkarsh Gupta (utkarsh) ** Changed in: isc-dhcp (Ubuntu Bionic) Assignee: (unassigned) => Utkarsh Gupta (utkarsh) ** Changed in: isc-dhcp (Ubuntu Focal) Assignee: (unassigned) => Utkarsh Gupta (utkarsh) ** Changed in: isc-dhcp (Ubuntu Groovy) Assignee: (unassigned) => Utkarsh Gupta (utkarsh) -- 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/1894172 Title: isc-dhcp-server using wrong env variable for INTERFACES Status in isc-dhcp package in Ubuntu: In Progress Status in isc-dhcp source package in Bionic: Confirmed Status in isc-dhcp source package in Focal: Confirmed Status in isc-dhcp source package in Groovy: Confirmed Bug description: When checking isc-dhcp-server unit file I saw isc-dhcp-server is being started by: ConditionPathExists=/etc/default/isc-dhcp-server ConditionPathExists=|/etc/ltsp/dhcpd.conf ConditionPathExists=|/etc/dhcp/dhcpd.conf [Service] EnvironmentFile=/etc/default/isc-dhcp-server RuntimeDirectory=dhcp-server # The leases files need to be root:dhcpd even when dropping privileges ExecStart=/bin/sh -ec '\ CONFIG_FILE=/etc/dhcp/dhcpd.conf; \ if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \ [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \ chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \ chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \ exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES' But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and $INTERFACESv6. This has only been working because cmdline sets -4 and subnet declaration in dhcpd.conf file makes dhcp-server to bind to the correct interfaces, as it looks like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774342] Re: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable
*** This bug is a duplicate of bug 1894172 *** https://bugs.launchpad.net/bugs/1894172 ** Also affects: isc-dhcp (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Hirsute) 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/1774342 Title: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable Status in isc-dhcp package in Ubuntu: New Status in isc-dhcp source package in Bionic: New Status in isc-dhcp source package in Focal: New Status in isc-dhcp source package in Groovy: New Status in isc-dhcp source package in Hirsute: New Bug description: package: isc-dhcp-server /etc/default/isc-dhcp-server define the variables INTERFACESv4 and INTERFACESv6 for define listening network interface, but /lib/systemd/system/isc-dhcp-server.service and /lib/systemd/system /isc-dhcp-server6.service use the variable INTERFACES (exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES'). This causes the service to listen on all interfaces. The correct way would be for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACESv4' .. for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf $CONFIG_FILE $INTERFACESv6' . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1774342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905969] Re: Asus Zephyrus G14 microphone not works
Hello everyone ! I have the same problem on my Asus Zephyrus G14 GA401II (AMD Ryzen 7 4800HS and NVIDIA GeForce GTX 1650) on ubuntu 20.04.2 LTS. To be more precise, the problem disappears when there is a kernel update, but reappears as soon as I boot on my Windows 10 in dual boot (Family Edition, fast boot disabled). I have read that it happens to Windows to turn off / reconfigure peripherals and I think that may be the source of our problem. But so it's more of a driver problem. For information : $ uname -r 5.8.0-44-generic Thanks for your consideration and your help! -- 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/1905969 Title: Asus Zephyrus G14 microphone not works Status in pulseaudio package in Ubuntu: Confirmed Bug description: I got an Asus Zephyrus G14 GA401IH-HE003 with AMD Ryzen 7 4800HS and a NVIDIA GeForce GTX 1650. I am use 5.9.8-050908-generic kernel from (kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.8/) dmamchyts@ga401ih:~$ cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" I have some problem with notebook microphone. When I use headphones via 3.5 jack - all works fine. But without headphones - system doesn't see any microphone device in settings. I am using KDE dmamchyts@ga401ih:/sys/class/hwmon/hwmon6$ aplay -l List of PLAYBACK Hardware Devices card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic_1 [HD-Audio Generic], device 0: ALC289 Analog [ALC289 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Also, I try to report issue into kernel team (they help me to fix issue with speakers), you can find some into it: https://bugzilla.kernel.org/show_bug.cgi?id=210359 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 Uname: Linux 5.9.8-050908-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 17:13:59 2020 InstallationDate: Installed on 2020-11-10 (17 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IH.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IH 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.ec.firmware.release: 3.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IH.210:bd11/05/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IH_GA401IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IH_GA401IH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905969] Re: Asus Zephyrus G14 microphone not works
** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1905969 Title: Asus Zephyrus G14 microphone not works Status in pulseaudio package in Ubuntu: Confirmed Bug description: I got an Asus Zephyrus G14 GA401IH-HE003 with AMD Ryzen 7 4800HS and a NVIDIA GeForce GTX 1650. I am use 5.9.8-050908-generic kernel from (kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.8/) dmamchyts@ga401ih:~$ cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" I have some problem with notebook microphone. When I use headphones via 3.5 jack - all works fine. But without headphones - system doesn't see any microphone device in settings. I am using KDE dmamchyts@ga401ih:/sys/class/hwmon/hwmon6$ aplay -l List of PLAYBACK Hardware Devices card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic_1 [HD-Audio Generic], device 0: ALC289 Analog [ALC289 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Also, I try to report issue into kernel team (they help me to fix issue with speakers), you can find some into it: https://bugzilla.kernel.org/show_bug.cgi?id=210359 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 Uname: Linux 5.9.8-050908-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 17:13:59 2020 InstallationDate: Installed on 2020-11-10 (17 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IH.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IH 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.ec.firmware.release: 3.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IH.210:bd11/05/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IH_GA401IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IH_GA401IH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES
** Changed in: isc-dhcp (Ubuntu Bionic) Status: Triaged => 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/1894172 Title: isc-dhcp-server using wrong env variable for INTERFACES Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Bionic: Confirmed Status in isc-dhcp source package in Focal: Confirmed Status in isc-dhcp source package in Groovy: Fix Released Bug description: When checking isc-dhcp-server unit file I saw isc-dhcp-server is being started by: ConditionPathExists=/etc/default/isc-dhcp-server ConditionPathExists=|/etc/ltsp/dhcpd.conf ConditionPathExists=|/etc/dhcp/dhcpd.conf [Service] EnvironmentFile=/etc/default/isc-dhcp-server RuntimeDirectory=dhcp-server # The leases files need to be root:dhcpd even when dropping privileges ExecStart=/bin/sh -ec '\ CONFIG_FILE=/etc/dhcp/dhcpd.conf; \ if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \ [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \ chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \ chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \ exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES' But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and $INTERFACESv6. This has only been working because cmdline sets -4 and subnet declaration in dhcpd.conf file makes dhcp-server to bind to the correct interfaces, as it looks like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES
** Merge proposal linked: https://code.launchpad.net/~utkarsh/ubuntu/+source/isc-dhcp/+git/isc-dhcp/+merge/398790 -- 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/1894172 Title: isc-dhcp-server using wrong env variable for INTERFACES Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Bionic: Triaged Status in isc-dhcp source package in Focal: Confirmed Status in isc-dhcp source package in Groovy: Fix Released Bug description: When checking isc-dhcp-server unit file I saw isc-dhcp-server is being started by: ConditionPathExists=/etc/default/isc-dhcp-server ConditionPathExists=|/etc/ltsp/dhcpd.conf ConditionPathExists=|/etc/dhcp/dhcpd.conf [Service] EnvironmentFile=/etc/default/isc-dhcp-server RuntimeDirectory=dhcp-server # The leases files need to be root:dhcpd even when dropping privileges ExecStart=/bin/sh -ec '\ CONFIG_FILE=/etc/dhcp/dhcpd.conf; \ if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \ [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \ chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \ chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \ exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES' But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and $INTERFACESv6. This has only been working because cmdline sets -4 and subnet declaration in dhcpd.conf file makes dhcp-server to bind to the correct interfaces, as it looks like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
I follow LTS-to-LTS normally and upgraded a btrfs subvolume copy all the way up to Hirsute now. I suspect that this is cruft from bionic or even earlier. I will look into it more as I find time. I usually don't boot into this hirsute system much. -- 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/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Incomplete Status in fam package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in ipfm package in Ubuntu: Incomplete Status in n2n package in Ubuntu: Incomplete Status in pfm package in Ubuntu: Incomplete Status in shadowsocks package in Ubuntu: Incomplete Status in sysfsutils package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in virtualbox package in Ubuntu: Incomplete Status in xl2tpd package in Ubuntu: Incomplete Status in systemd package in Debian: Unknown Bug description: systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388955] systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.389412] systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a native systemd unit file.
[Touch-packages] [Bug 1917046] [NEW] package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: »installiertes lightdm-Skript des Paketes post-installation«-Unterprozess wurde durch Signal (Beendet)
Public bug reported: I think the problem was the dialog for asking whether I want to use gdm or lightdm, when I was installing the package over SSH ProblemType: Package DistroRelease: Ubuntu 20.10 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 26 14:07:22 2021 ErrorMessage: »installiertes lightdm-Skript des Paketes post-installation«-Unterprozess wurde durch Signal (Beendet) getötet Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: lightdm Title: package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: »installiertes lightdm-Skript des Paketes post-installation«-Unterprozess wurde durch Signal (Beendet) getötet UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1917046 Title: package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: »installiertes lightdm-Skript des Paketes post- installation«-Unterprozess wurde durch Signal (Beendet) getötet Status in lightdm package in Ubuntu: New Bug description: I think the problem was the dialog for asking whether I want to use gdm or lightdm, when I was installing the package over SSH ProblemType: Package DistroRelease: Ubuntu 20.10 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 26 14:07:22 2021 ErrorMessage: »installiertes lightdm-Skript des Paketes post-installation«-Unterprozess wurde durch Signal (Beendet) getötet Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: lightdm Title: package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: »installiertes lightdm-Skript des Paketes post-installation«-Unterprozess wurde durch Signal (Beendet) getötet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1917046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840908] Re: Stick to 1.16 for hirsute
** Summary changed: - Stick to 1.16 for eoan + Stick to 1.16 for hirsute ** Tags removed: version-skip-1.17.2 ** Tags added: version-skip-1.17.4 ** Description changed: - There is no stable 1.18 planned for before eoan and nothing we really + There is no stable 1.18 planned for before hirsute and nothing we really need in 1.17 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1840908 Title: Stick to 1.16 for hirsute Status in cairo package in Ubuntu: Triaged Bug description: There is no stable 1.18 planned for before hirsute and nothing we really need in 1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1840908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Changed in: bluez (Ubuntu Hirsute) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Fix Released Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
** Changed in: mesa (Fedora) Status: Unknown => Confirmed ** Changed in: mesa (Fedora) Importance: Unknown => High -- 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/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES
** Changed in: isc-dhcp (Ubuntu) Status: Fix Released => 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/1894172 Title: isc-dhcp-server using wrong env variable for INTERFACES Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Bionic: Triaged Status in isc-dhcp source package in Focal: Confirmed Status in isc-dhcp source package in Groovy: Fix Released Bug description: When checking isc-dhcp-server unit file I saw isc-dhcp-server is being started by: ConditionPathExists=/etc/default/isc-dhcp-server ConditionPathExists=|/etc/ltsp/dhcpd.conf ConditionPathExists=|/etc/dhcp/dhcpd.conf [Service] EnvironmentFile=/etc/default/isc-dhcp-server RuntimeDirectory=dhcp-server # The leases files need to be root:dhcpd even when dropping privileges ExecStart=/bin/sh -ec '\ CONFIG_FILE=/etc/dhcp/dhcpd.conf; \ if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \ [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \ chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \ chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \ exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES' But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and $INTERFACESv6. This has only been working because cmdline sets -4 and subnet declaration in dhcpd.conf file makes dhcp-server to bind to the correct interfaces, as it looks like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774342] Re: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable
*** This bug is a duplicate of bug 1894172 *** https://bugs.launchpad.net/bugs/1894172 ** No longer affects: isc-dhcp (Ubuntu Groovy) -- 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/1774342 Title: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable Status in isc-dhcp package in Ubuntu: New Status in isc-dhcp source package in Bionic: New Status in isc-dhcp source package in Focal: New Bug description: package: isc-dhcp-server /etc/default/isc-dhcp-server define the variables INTERFACESv4 and INTERFACESv6 for define listening network interface, but /lib/systemd/system/isc-dhcp-server.service and /lib/systemd/system /isc-dhcp-server6.service use the variable INTERFACES (exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES'). This causes the service to listen on all interfaces. The correct way would be for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACESv4' .. for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf $CONFIG_FILE $INTERFACESv6' . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1774342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774342] Re: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable
*** This bug is a duplicate of bug 1894172 *** https://bugs.launchpad.net/bugs/1894172 ** Also affects: isc-dhcp (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Groovy) 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/1774342 Title: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable Status in isc-dhcp package in Ubuntu: New Status in isc-dhcp source package in Bionic: New Status in isc-dhcp source package in Focal: New Bug description: package: isc-dhcp-server /etc/default/isc-dhcp-server define the variables INTERFACESv4 and INTERFACESv6 for define listening network interface, but /lib/systemd/system/isc-dhcp-server.service and /lib/systemd/system /isc-dhcp-server6.service use the variable INTERFACES (exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES'). This causes the service to listen on all interfaces. The correct way would be for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACESv4' .. for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf $CONFIG_FILE $INTERFACESv6' . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1774342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916893] Re: Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode parts cause serious regressions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python2.7 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1916893 Title: Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode parts cause serious regressions Status in python2.7 package in Ubuntu: Confirmed Bug description: [Scenario] A security update was made for python2.7 in xenial and bionic that can cause a serious regression since it is modifying unicode code for python2.7. [Issue] It can cause a serious break in the way python prints, rprs, unicode information, causing serious damage for any application that is running python2.7 in that scenario. [More info] https://ubuntu.com/security/CVE-2021-3177 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916915] Re: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)
*** This bug is a duplicate of bug 1916893 *** https://bugs.launchpad.net/bugs/1916893 The bug report about the regression is bug 1916893, and now links to https://ubuntu.com/security/notices/USN-4754-2, so I'm just going to mark this as a duplicate of that bug. ** This bug has been marked a duplicate of bug 1916893 Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode parts cause serious regressions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1916915 Title: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale) Status in python2.7 package in Ubuntu: Confirmed Bug description: Apt tries to get the python2.7 package and some of its dependencies with version (2.7.17-1~18.04ubuntu1.3). However it returns an error with: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb 404 Not Found [IP: 91.189.88.152 80] The problem is present on BIONIC distro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)
** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- 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/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693709] Re: Wrong substitution for TimesNewRomanPSMT in evince / postscriptname not used
I am seeing this even on 20.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1693709 Title: Wrong substitution for TimesNewRomanPSMT in evince / postscriptname not used Status in fontconfig package in Ubuntu: Confirmed Bug description: A PDF I got referenced the not embedded font TimesNewRomanPSMT. Document viewer evince by fontconfig used DejaVu Sans to display it. But „TimesNewRomanPSMT“ is the postscriptname of Times New Roman, so it looks like fontconfig is not looking for the postscript names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1693709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693709] Re: Wrong substitution for TimesNewRomanPSMT in evince / postscriptname not used
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1693709 Title: Wrong substitution for TimesNewRomanPSMT in evince / postscriptname not used Status in fontconfig package in Ubuntu: Confirmed Bug description: A PDF I got referenced the not embedded font TimesNewRomanPSMT. Document viewer evince by fontconfig used DejaVu Sans to display it. But „TimesNewRomanPSMT“ is the postscriptname of Times New Roman, so it looks like fontconfig is not looking for the postscript names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1693709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
Julian said in comment #9 that 2.5.1 would be good. But then Florians comment #11 does not make me feel so sure. In any case we now have: libseccomp | 2.5.1-1ubuntu1 | hirsute| source Does that mean we are good now? Subscribing Alex who did the 2.5.1 upload ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in glibc package in Ubuntu: Triaged Status in libseccomp package in Ubuntu: Fix Committed Status in glibc source package in Hirsute: Triaged Status in libseccomp source package in Hirsute: Fix Committed Bug description: glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)
** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=211853 Importance: Unknown Status: Unknown ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
The bug is still present in 21.04 but a new fix has been proposed in: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/587 ** Tags added: hirsute ** No longer affects: mesa (Ubuntu) -- 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/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in xorg-server package in Ubuntu: Triaged Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1823516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)
For those having kernel 5.11 - you may debug already, being helped-out here https://bugzilla.kernel.org/show_bug.cgi?id=211853 ** Bug watch added: Linux Kernel Bug Tracker #211853 https://bugzilla.kernel.org/show_bug.cgi?id=211853 -- 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/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset) Status in pulseaudio package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916935] Re: Major changes in sorting method upgrade 18.04->18.04.5 due to base-files change
FYI: Until resolved, hard setting the "other" LC_* values will get you either behavior as you need it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1916935 Title: Major changes in sorting method upgrade 18.04->18.04.5 due to base- files change Status in base-files package in Ubuntu: New Status in glibc package in Ubuntu: Invalid Status in postgresql-10 package in Ubuntu: Invalid Status in base-files source package in Bionic: New Bug description: I had an Ubuntu 18.04.0 with Postgres 9.6. Before Ubuntu upgrade following command result was: [code] vodka@ubuntu140:~$ ( echo "1-1"; echo "11" ) | LC_COLLATE=en_US.UTF-8 sort 1-1 11 [/code] But after upgrading Ubuntu 18.04 to latest release via apt upgrade (18.04.5) result of the command above totally changed: [code] vodka@ubuntu140:~$ ( echo "1-1"; echo "11" ) | LC_COLLATE=en_US.UTF-8 sort 11 1-1 [/code] Due to this our production Postgres database started work very slowly and we had a long downtime for REINDEX. Sorting method is very important for Postgres database: https://wiki.postgresql.org/wiki/Locale_data_changes Please, read "Testing collation" part. Is it normal behavior for Ubuntu? Why glibc totally changed within LTS release without 'major upgrade'? I did not expect this... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libc-bin 2.27-3ubuntu1.4 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Thu Feb 25 13:13:03 2021 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.4 libgcc1 1:8.4.0-1ubuntu1~18.04 InstallationDate: Installed on 2021-02-25 (0 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1916935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916935] Re: Major changes in sorting method of glibc on Ubuntu 18.04 after upgrading to Ubuntu 18.04.5
FYI - This happens only to a login shell $ ssh ubuntu@192.168.122.177 "env | grep LC_NUM"; LC_NUMERIC=de_DE.UTF-8 ssh ubuntu@192.168.122.177 -t 'bash -l -c "env | grep LC_NUM"' LC_NUMERIC=C.UTF-8 And while downgrading I saw the suspicious /etc/profile.d/01-locale-fix.sh: line 2: /usr/bin/locale-check: No such file or directory $ cat /etc/profile.d/01-locale-fix.sh # Make sure the locale variables are set to valid values. eval $(/usr/bin/locale-check C.UTF-8) And indeed on "release" Bionic that binary used there isn't present. I checked where it came from: $ dpkg -S /usr/bin/locale-check base-files: /usr/bin/locale-check So it seems this check was always meant to work, but on bionic-release calls a file that isn't present and therefore is not in effect to "fixup" the locales on a login shell. Now that I know that I was able to swicth between old/new behavior by switching "just" base files 10.1ubuntu2 <-> 10.1ubuntu2.10. That change was introduced back in 2018 via bug 1134036 as far as I found. I'm not sure what to do, this is "longer in the field with the new behavior" and not new at all. So changing it either way might regress people. But in any case we can re-target this bug against base-files for re-consideration now that we know all that. ** Also affects: base-files (Ubuntu) Importance: Undecided Status: New ** Changed in: postgresql-10 (Ubuntu) Status: Incomplete => Invalid ** No longer affects: postgresql-10 (Ubuntu Bionic) ** Changed in: glibc (Ubuntu) Status: New => Invalid ** No longer affects: glibc (Ubuntu Bionic) ** Summary changed: - Major changes in sorting method of glibc on Ubuntu 18.04 after upgrading to Ubuntu 18.04.5 + Major changes in sorting method upgrade 18.04->18.04.5 due to base-files change -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1916935 Title: Major changes in sorting method upgrade 18.04->18.04.5 due to base- files change Status in base-files package in Ubuntu: New Status in glibc package in Ubuntu: Invalid Status in postgresql-10 package in Ubuntu: Invalid Status in base-files source package in Bionic: New Bug description: I had an Ubuntu 18.04.0 with Postgres 9.6. Before Ubuntu upgrade following command result was: [code] vodka@ubuntu140:~$ ( echo "1-1"; echo "11" ) | LC_COLLATE=en_US.UTF-8 sort 1-1 11 [/code] But after upgrading Ubuntu 18.04 to latest release via apt upgrade (18.04.5) result of the command above totally changed: [code] vodka@ubuntu140:~$ ( echo "1-1"; echo "11" ) | LC_COLLATE=en_US.UTF-8 sort 11 1-1 [/code] Due to this our production Postgres database started work very slowly and we had a long downtime for REINDEX. Sorting method is very important for Postgres database: https://wiki.postgresql.org/wiki/Locale_data_changes Please, read "Testing collation" part. Is it normal behavior for Ubuntu? Why glibc totally changed within LTS release without 'major upgrade'? I did not expect this... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libc-bin 2.27-3ubuntu1.4 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Thu Feb 25 13:13:03 2021 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.4 libgcc1 1:8.4.0-1ubuntu1~18.04 InstallationDate: Installed on 2021-02-25 (0 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1916935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
