[Touch-packages] [Bug 2060150] [NEW] openssh sets PAM_RHOST to UNKNOWN causing slow logins
Public bug reported: When using sshd's -i option with stdio that is not a AF_INET/AF_INET6 socket, auth_get_canonical_hostname() returns "UNKNOWN" which is then set as the value of PAM_RHOST, causing pam to try to do a reverse DNS query of "UNKNOWN", which times out multiple times, causing a substantial slowdown when logging in. upstream PR: https://github.com/openssh/openssh-portable/pull/388 upstream email: https://lists.mindrot.org/pipermail/openssh-unix-dev/2024-April/041289.html Fedora backport: https://src.fedoraproject.org/rpms/openssh/pull-request/71 Debian backport: https://salsa.debian.org/ssh-team/openssh/-/merge_requests/25 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2060150 Title: openssh sets PAM_RHOST to UNKNOWN causing slow logins Status in openssh package in Ubuntu: New Bug description: When using sshd's -i option with stdio that is not a AF_INET/AF_INET6 socket, auth_get_canonical_hostname() returns "UNKNOWN" which is then set as the value of PAM_RHOST, causing pam to try to do a reverse DNS query of "UNKNOWN", which times out multiple times, causing a substantial slowdown when logging in. upstream PR: https://github.com/openssh/openssh-portable/pull/388 upstream email: https://lists.mindrot.org/pipermail/openssh-unix-dev/2024-April/041289.html Fedora backport: https://src.fedoraproject.org/rpms/openssh/pull-request/71 Debian backport: https://salsa.debian.org/ssh-team/openssh/-/merge_requests/25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2060150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
The previous lvm2 upload has now migrated from proposed to noble. cryptsetup 2.7.0 is also now available in noble, which also can make use of this bug fix. -- 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/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Noble: Confirmed Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is a problem when software like systemd via libcryptsetup try to open a volume, and get an unrecognizable error out of it. With the fix in libdm and libcryptsetup, there is a clear ENOKEY returned when a key is missing and activation fails for that reason. This allows systemd (and other applications) to make the right decision depending on the failure case. Without this, the same generic error is returned in any case. For more details, see: https://gitlab.com/cryptsetup/cryptsetup/-/issues/841 libcryptsetup 2.7.0, now available in debian stable, and systemd v255, shipped in Noble, make use of this error code. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
** Merge proposal linked: https://code.launchpad.net/~bluca/ubuntu/+source/lvm2/+git/lvm2/+merge/461372 ** Merge proposal unlinked: https://code.launchpad.net/~bluca/ubuntu/+source/lvm2/+git/lvm2/+merge/460984 -- 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/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Noble: Confirmed Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is a problem when software like systemd via libcryptsetup try to open a volume, and get an unrecognizable error out of it. With the fix in libdm and libcryptsetup, there is a clear ENOKEY returned when a key is missing and activation fails for that reason. This allows systemd (and other applications) to make the right decision depending on the failure case. Without this, the same generic error is returned in any case. For more details, see: https://gitlab.com/cryptsetup/cryptsetup/-/issues/841 libcryptsetup 2.7.0, now available in debian stable, and systemd v255, shipped in Noble, make use of this error code. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
** Description changed: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. + + This is a problem when software like systemd via libcryptsetup try to + open a volume, and get an unrecognizable error out of it. With the fix + in libdm and libcryptsetup, there is a clear ENOKEY returned when a key + is missing and activation fails for that reason. This allows systemd + (and other applications) to make the right decision depending on the + failure case. Without this, the same generic error is returned in any + case. + + For more details, see: + + https://gitlab.com/cryptsetup/cryptsetup/-/issues/841 + + libcryptsetup 2.7.0, now available in debian stable, and systemd v255, + shipped in Noble, make use of this error code. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 -- 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/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Noble: Confirmed Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is a problem when software like systemd via libcryptsetup try to open a volume, and get an unrecognizable error out of it. With the fix in libdm and libcryptsetup, there is a clear ENOKEY returned when a key is missing and activation fails for that reason. This allows systemd (and other applications) to make the right decision depending on the failure case. Without this, the same generic error is returned in any case. For more details, see: https://gitlab.com/cryptsetup/cryptsetup/-/issues/841 libcryptsetup 2.7.0, now available in debian stable, and systemd v255, shipped in Noble, make use of this error code. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
Note that currently in noble lvm2 fails to build due to https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683 which is unrelated to the MR linked here -- 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/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Noble: Confirmed Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
** Changed in: lvm2 (Ubuntu Noble) Status: New => Confirmed -- 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/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Noble: Confirmed Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
Merge request opened at https://code.launchpad.net/~bluca/ubuntu/+source/lvm2/+git/lvm2/+merge/460984 ** Tags added: patch patch-accepted-upstream ** Merge proposal linked: https://code.launchpad.net/~bluca/ubuntu/+source/lvm2/+git/lvm2/+merge/460984 -- 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/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: New Status in lvm2 source package in Noble: New Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054620] [NEW] libdm returns wrong error code when dm-verity key cannot be found
Public bug reported: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Affects: lvm2 (Ubuntu Noble) Importance: Undecided Status: New ** Tags: patch patch-accepted-upstream ** Also affects: lvm2 (Ubuntu Noble) Importance: Undecided Status: New -- 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/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: New Status in lvm2 source package in Noble: New Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
** Changed in: libsolv (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
Fix Released
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Fix Released
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
Fix Released
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
Invalid
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in python-debian package in Ubuntu:
Fix Released
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in reprepro source package in Focal:
Fix Released
Status in reprepro source package in Groovy:
Fix Released
Status in reprepro source package in Hirsute:
Fix Released
Status in debian-el package in Debian:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
SUSE and Fedora have started to compress repodata with zstd, so it is now
impossible to bootstrap those distributions from Ubuntu via dnf/zypper due to
the lack of zstd support in libsolve. This affects my CI jobs running in Jammy.
The fix is trivial as the version already supports it, but it needs to
build-depend on libzstd and enable the build config flag for it. I will prepare
SRUs for mantic/lunar/jammy. It will be fixed in noble with the next sync from
Debian unstable, at version 0.7.26-2.
** Changed in: libsolv (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
Fix Released
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Fix Released
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
Confirmed
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
Invalid
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in python-debian package in Ubuntu:
Fix Released
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in reprepro source package in Focal:
Fix Released
Status in reprepro source package in Groovy:
Fix Released
Status in reprepro source package in Hirsute:
Fix Released
Status in debian-el package in Debian:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see
[Touch-packages] [Bug 2029019] Re: PulseAudio doesn't start by logging in after a standby
Logs entries related to PulseAudio:
03:14:20 PM systemd: pulseaudio.socket: Failed with result
'service-start-limit-hit'.
03:14:13 PM dbus-daemon: [system] Activating via systemd: service
name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.189' (uid=1000
pid=3142 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo"
label="unconfined")
03:14:13 PM systemd: pulseaudio.service: Succeeded.
03:08:45 PM sudo: luca : TTY=pts/0 ; PWD=/home/luca ; USER=root ;
COMMAND=/usr/bin/apt purge pulseaudio
03:07:18 PM pulseaudio: GetManagedObjects() failed:
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez':
timed out (service_start_timeout=25000ms)
03:07:14 PM systemd: pulseaudio.service: Succeeded.
03:06:53 PM dbus-daemon: [system] Activating via systemd: service
name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.161' (uid=1000
pid=2849 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo"
label="unconfined")
03:06:52 PM systemd: pulseaudio.service: Succeeded.
03:05:24 PM pulseaudio: Error opening PCM device front:0: File or directory
does not exist
4 oct 03:31:04 PM systemd: pulseaudio.socket: Succeeded.
4 oct 03:30:49 PM pulseaudio: GetManagedObjects() failed:
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez':
timed out (service_start_timeout=25000ms)
4 oct 03:30:35 PM systemd: gnome-launched-pulseaudio.desktop-1603.scope:
Succeeded.
4 oct 03:30:26 PM dbus-daemon: [system] Activating via systemd: service
name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.71' (uid=1000
pid=1383 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo"
label="unconfined")
4 oct 03:29:12 PM system76-schedu: (Assignment(CpuPriority(-11),
Realtime(PriorityLevel(0))), {"pipewire", "pipewire-pulse", "wireplumber"})
--
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/2029019
Title:
PulseAudio doesn't start by logging in after a standby
Status in pulseaudio package in Ubuntu:
New
Bug description:
Often when I log in after a standby PulseAudio doesn't play any audio, the
service is working but no audio is heard. I noticed that when this happens, if
I adjust volume the system shows Dummy Output instead of the usual speaker
small window. Also, one day when I was having right this issue I simply took a
screenshot to a game that I was playing and audio was played 廊.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: luca 1456 F pulseaudio
/dev/snd/pcmC0D0p: luca 1456 F...m pulseaudio
/dev/snd/controlC1: luca 1456 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: zorin:GNOME
DistroRelease: Zorin OS 16
InstallationDate: Installed on 2022-10-01 (325 days ago)
InstallationMedia: Zorin-OS 16.1 Core 64bit
Package: pulseaudio 1:13.99.1-1ubuntu3.13 [origin: Ubuntu]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-78.85~20.04.1-generic 5.15.99
Tags: focal third-party-packages
Uname: Linux 5.15.0-78-generic x86_64
UnreportableReason: Questo non è un pacchetto ufficiale di Zorin. Rimuovere
tutti i pacchetti di terze parti, quindi riprovare.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/28/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52N.218
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K52N
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrK52N.218:bd01/28/2011:br4.6:svnASUSTeKComputerInc.:pnK52N:pvr1.0:rvnASUSTeKComputerInc.:rnK52N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku:
dmi.product.name: K52N
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/2029019/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989124] Re: libunwind-(13/14)-dev conflicts with libunwind-dev
This is hitting me on Github Actions where the llvm toolchain is installed by default, any chance it could be fixed in Jammy with an SRU? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1989124 Title: libunwind-(13/14)-dev conflicts with libunwind-dev Status in libunwind package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Bug description: Tested on Ubuntu 22.04. Since these two packages (libunwind-14 and libunwind-dev) conflict with each other, I cannot install some libraries and tools that depend on them. For example, I cannot install libc++-14-dev and libgstreamer1.0-dev together, and that's really unfortunate. I'm not sure which packages should be somehow fixed (if any), so feel free to reassign this bug wherever it fits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1989124/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2029019] Re: PulseAudio doesn't start by logging in after a standby
https://forum.zorin.com/t/no-audio-after-relogging-in/26234 -- 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/2029019 Title: PulseAudio doesn't start by logging in after a standby Status in pulseaudio package in Ubuntu: New Bug description: Often when I log in after a standby PulseAudio doesn't play any audio, the service is working but no audio is heard. I noticed that when this happens, if I adjust volume the system shows Dummy Output instead of the usual speaker small window. Also, one day when I was having right this issue I simply took a screenshot to a game that I was playing and audio was played 廊. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1456 F pulseaudio /dev/snd/pcmC0D0p: luca 1456 F...m pulseaudio /dev/snd/controlC1: luca 1456 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: zorin:GNOME DistroRelease: Zorin OS 16 InstallationDate: Installed on 2022-10-01 (325 days ago) InstallationMedia: Zorin-OS 16.1 Core 64bit Package: pulseaudio 1:13.99.1-1ubuntu3.13 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-78.85~20.04.1-generic 5.15.99 Tags: focal third-party-packages Uname: Linux 5.15.0-78-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Zorin. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/28/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K52N.218 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K52N dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK52N.218:bd01/28/2011:br4.6:svnASUSTeKComputerInc.:pnK52N:pvr1.0:rvnASUSTeKComputerInc.:rnK52N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku: dmi.product.name: K52N 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/2029019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835315] Re: Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs
Hello, sadly I can not reproduce as I don't have the hardware anymore, I suppose if no one else reported the issue it is solved. -- 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/1835315 Title: Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs Status in mesa package in Ubuntu: Incomplete Bug description: Ubuntu version: 18.04.2 LTS Mesa version: 19.0.2 Mesa-vulkan-driver version: 19.0.2, POLARIS10, DRM 3.27.0, 5.0.0-20-generic, LLVM 8.0.0) Video card: AMD RX 580 8GB, There is an issue when the Vulkan mesa RADV drivers are compiled with LLVM 8, due to an LLVM 8 bug, resulting in no visual output in some programs using the RADV Vulkan backend Upgrading to a mesa build compiled with LLVM 9, or reverting back to the bionic version from bionic-updates (which uses LLVM 6) fixes the problem. Using the AMDVLK vulkan driver workarounds the problem too. The program I have personally tested is RPCS3 I could put additional info about the LLVM bug but at this moment I do not have the upstream reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835315/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2027712] Re: Switch from usrmerge to usr-is-merged
Thanks - up to you how to solve it of course, but please bear in mind that you'll also need to patch debootstrap - and debootstrap from other distro (say, from Debian build an Ubuntu image) might break as a result -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/2027712 Title: Switch from usrmerge to usr-is-merged Status in cloud-images: Confirmed Status in init-system-helpers package in Ubuntu: New Bug description: Last year in Debian we added the 'usr-is-merged' binary package to the 'usrmerge' source package. Its purpose is to be an empty metapackage that simply asserts that the system is usr-merged. This is done via the postinst. Contrary to usrmerge, it doesn't ship any additional code, perform any additional action or have any additional dependencies. In Debian, we have an essential package (init-system-helpers) that depends on usrmerge | usr-is-merged, so that on upgrade for already installed images usrmerge is pulled in and all systems are forcibly merged. But for new images being built, the boostrap (eg: debootstrap) process will instead pull in usr-is-merged, which will save space and reduce the overall code footprint. The problem in Ubuntu is that while usrmerge is in main, usr-is-merged is in universe, so unless the bootstrap tool enables universe for the initial bootstrap phase, usrmerge is always pulled in. Refs: https://packages.ubuntu.com/mantic/usr-is-merged https://packages.ubuntu.com/mantic/usrmerge https://packages.ubuntu.com/mantic/init-system-helpers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2027712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023180] Re: Autopkgtest failure for kinetic kernels
** Description changed: autopkgtest [10:10:45]: test networkd-test.py: [--- systemd-network:x:100:102:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin test_bridge_init (__main__.BridgeTest) ... ok test_bridge_port_priority (__main__.BridgeTest) ... ok test_bridge_port_priority_set_zero (__main__.BridgeTest) It should be possible to set the bridge port priority to 0 ... ok test_bridge_port_property (__main__.BridgeTest) Test the "[Bridge]" section keys ... ok test_coldplug_dhcp_ip4_only (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers ... ERROR test_resolved_etc_hosts (__main__.DnsmasqClientTest) resolved queries to /etc/hosts ... ok test_route_only_dns (__main__.DnsmasqClientTest) ... ok test_route_only_dns_all_domains (__main__.DnsmasqClientTest) ... ok test_transient_hostname (__main__.DnsmasqClientTest) networkd sets transient hostname from DHCP ... ok test_transient_hostname_with_static (__main__.DnsmasqClientTest) transient hostname is not applied if static hostname exists ... ok test_basic_matching (__main__.MatchClientTest) Verify the Name= line works throughout this class. ... ok test_inverted_matching (__main__.MatchClientTest) Verify that a '!'-prefixed value inverts the match. ... ok test_coldplug_dhcp_ip4_only (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_coldplug_dhcp_yes_ip4 (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.NetworkdClientTest) ... ok test_dhcp_timezone (__main__.NetworkdClientTest) networkd sets time zone from DHCP ... ok test_dropin (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_route_only_dns (__main__.NetworkdClientTest) ... ok test_route_only_dns_all_domains (__main__.NetworkdClientTest) ... ok test_search_domains (__main__.NetworkdClientTest) ... ok test_catchall_config (__main__.UnmanagedClientTest) Verify link states with a catch-all config, hot-plug. ... ok test_catchall_config_coldplug (__main__.UnmanagedClientTest) Verify link states with a catch-all config, cold-plug. ... ok test_unmanaged_setting (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, hot-plug. ... ok test_unmanaged_setting_coldplug (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, cold-plug. ... ok == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.W3rkSo/build.Vi6/src/test/networkd-test.py", line 680, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 420, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 524, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 158.633s FAILED (errors=1, skipped=2) autopkgtest [10:13:25]: test networkd-test.py: ---] autopkgtest [10:13:25]: test networkd-test.py: - - - - - - - - - - results - - - - - - - - - - networkd-test.py FAIL non-zero exit status 1 To be determined if the issue is in the package or linux kernel + + --- + External link: https://warthogs.atlassian.net/browse/PEL-424 -- 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/2023180 Title: Autopkgtest failure for kinetic kernels Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Kinetic: New Bug description: autopkgtest [10:10:45]: test networkd-test.py: [---
[Touch-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake
In my case, a simple > pulseaudio -k < on terminal fixes but surely I'd prefer a solution rather than having to apply this command. -- 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/1888598 Title: Pulseaudio breaks HDMI audio on sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected
Hi everyone! This issue is fixed in https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4674, maybe it could be backported to Ubuntu 22.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Status in gtk4 package in Ubuntu: Triaged Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1878076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992178] Re: autopkgtest: upstream tests that run in qemu hang on ppc64el
Backtraces are on the upstream bug, eg: https://github.com/systemd/systemd/issues/25091#issuecomment-1401824195 https://github.com/systemd/systemd/issues/25091#issuecomment-1402425787 It would be better if the IBM developers could engage directly on the upstream ticket for the initial investigation, given the information is recorded there. Thanks! -- 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/1992178 Title: autopkgtest: upstream tests that run in qemu hang on ppc64el Status in systemd: Unknown Status in The Ubuntu-power-systems project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Bug description: I believe this started early in the kinetic cycle, cf. https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el. Timeouts in the upstream tests have been an issue for a while, but kinetic on ppc64el consistently times out with upstream tests that run in QEMU. Skipping individual tests does not help, because *which* tests time out appears to change with each build. For example, in 251.4-1ubuntu4 the TEST-36-NUMAPOLICY test was consistently the culprit, but now in 251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out. I have not been able to identify a root cause for this, but it seems that running tests in QEMU is very fragile on ppc64el, where as the tests that run in nspawn are more consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1992178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992178] Re: autopkgtest: upstream tests that run in qemu hang on ppc64el
We are suspecting issues in the ppc64el toolchain. The problem is only reproducible on Ubuntu ppc, and not on other distributions. The backtrace show some borken pointers that can't be explained. The upstream issue has all the details. None of us speak ppc assembly so we can't really check the binaries. -- 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/1992178 Title: autopkgtest: upstream tests that run in qemu hang on ppc64el Status in systemd: Unknown Status in The Ubuntu-power-systems project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Bug description: I believe this started early in the kinetic cycle, cf. https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el. Timeouts in the upstream tests have been an issue for a while, but kinetic on ppc64el consistently times out with upstream tests that run in QEMU. Skipping individual tests does not help, because *which* tests time out appears to change with each build. For example, in 251.4-1ubuntu4 the TEST-36-NUMAPOLICY test was consistently the culprit, but now in 251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out. I have not been able to identify a root cause for this, but it seems that running tests in QEMU is very fragile on ppc64el, where as the tests that run in nspawn are more consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1992178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2001890] Re: Network Manager cannot using the 'add' button for openvpn
As you can see in the screenshot I am using the following settings and I cannot click the 'add' button. ** Attachment added: "Screenshot2.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2001890/+attachment/5639245/+files/Screenshot2.png ** Description changed: Hi everyone, - After upgrading my laptop to ubuntu 22.10 I cannot add an openvpn in the - network settings. + This issue is related to network-manager with an openvpn connection on + Ubuntu 22.10. + + I am using a openvpn connection with as connection type "Password with + Certificate (TLS)". + + After upgrading my laptop from ubuntu 22.04 to ubuntu 22.10, I am no longer able to save the TLS certificate password + for my user only. + If I select the "for my user only" option, I cannot save the profile (i.e. button is disabled). + + The only option I currently have is to never save the password, which + does work. + + This issue only popped up after the upgrade to 22.10. Not touching the VPN connection makes network-manager ask for + the password. Have a look at the screenshot below for further information. + Any help would be appreciated. + Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2001890 Title: Network Manager cannot using the 'add' button for openvpn Status in network-manager package in Ubuntu: New Bug description: Hi everyone, This issue is related to network-manager with an openvpn connection on Ubuntu 22.10. I am using a openvpn connection with as connection type "Password with Certificate (TLS)". After upgrading my laptop from ubuntu 22.04 to ubuntu 22.10, I am no longer able to save the TLS certificate password for my user only. If I select the "for my user only" option, I cannot save the profile (i.e. button is disabled). The only option I currently have is to never save the password, which does work. This issue only popped up after the upgrade to 22.10. Not touching the VPN connection makes network-manager ask for the password. Have a look at the screenshot below for further information. Any help would be appreciated. Thank you in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2001890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2001890] [NEW] Network Manager cannot using the 'add' button for openvpn
Public bug reported: Hi everyone, After upgrading my laptop to ubuntu 22.10 I cannot add an openvpn in the network settings. Have a look at the screenshot below for further information. Thank you in advance! ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "As you can see in the screenshot I am using the following settings and I cannot click the 'add' button." https://bugs.launchpad.net/bugs/2001890/+attachment/5639238/+files/Screenshot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2001890 Title: Network Manager cannot using the 'add' button for openvpn Status in network-manager package in Ubuntu: New Bug description: Hi everyone, After upgrading my laptop to ubuntu 22.10 I cannot add an openvpn in the network settings. Have a look at the screenshot below for further information. Thank you in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2001890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged
> In addition to that though, I notice that mkosi in Jammy does refer to /usr/bin/systemd-repart. Will the Jammy packaged mkosi therefore change behaviour if you start shipping it in Ubuntu? Those references are for the dracut configuration, i.e. to get those files from the target image to the target image's initrd. What is available on the host is independent of that. -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. Runtime behavior of existing components is not affected by the build config change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged
** Description changed: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd-repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. + + Runtime behavior of existing components is not affected by the build + config change. -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and
[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged
** Description changed: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? - The bug reporter would like to use it in our new raspberry pi images + The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd-repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to
[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged
debdiff enabling systemd repart in the jammy/devel branch ** Patch added: "systemd_repart.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+attachment/5605761/+files/systemd_repart.debdiff -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in our new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged
The upstream systemd developers team would like to request to enable systemd-repart in Jammy in the next proposed-updates. MR: https://code.launchpad.net/~bluca/ubuntu/+source/systemd/+git/systemd/+merge/427557 -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in our new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged
** Changed in: systemd (Ubuntu) Status: Triaged => Fix Released ** Changed in: systemd (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in our new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged
** Description changed: + [Impact] + systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? - I'd like to use it in our new raspberry pi images where we don't have - cloud-init installed. We're already using systemd-growfs, but we are - missing the nice partition resizing part (so are using cloud-initramfs- - growroot). + The bug reporter would like to use it in our new raspberry pi images + where they don't have cloud-init installed. The reporter is already + using systemd-growfs, but they are missing the nice partition resizing + part (so are using cloud-initramfs-growroot). - Could you please consider enabling it? In another binary package - so it - can have extra deps - would be just fine by me. + Furthermore, in the mkosi image builder + (https://github.com/systemd/mkosi), the systemd/mkosi developers would + like to start using systemd-repart for partitioning. Unfortunately, + they're currently blocked on this because 22.04 doesn't ship systemd- + repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy + and will do so until the next Ubuntu LTS is released. If we have to wait + for the next LTS to be released, we'll have to wait for a considerable + amount of time before we're able to start using systemd-repart. + + Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, + as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to + be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. + + [Test Plan] + This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. + + [Where problems could occur] + Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. + + Given that there's no risk involved with enabling systemd-repart, and + given the useful features it provides, the systemd/mkosi developers + would like to request that systemd-repart be enabled in Ubuntu and + backported to Jammy so that they can start adopting it in mkosi. -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Triaged Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in our new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given
[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged
Any chance it could be enabled now that Jammy shipped? It's really fine to enable it in 249 for 20.10, there's really no reason to wait for a new version -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Triaged Status in systemd package in Debian: Fix Released Bug description: systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? I'd like to use it in our new raspberry pi images where we don't have cloud-init installed. We're already using systemd-growfs, but we are missing the nice partition resizing part (so are using cloud- initramfs-growroot). Could you please consider enabling it? In another binary package - so it can have extra deps - would be just fine by me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959047] Re: systemd ignores RootDirectory option in .service units
Is there a chance to SRU a targeted patch for LXD in Bionic to fix the issue instead? -- 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/1959047 Title: systemd ignores RootDirectory option in .service units Status in systemd package in Ubuntu: Confirmed Bug description: The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the following contents: # /etc/systemd/system/lsb-release.service [Unit] Description=LSB Release Information [Service] Type=simple RootDirectory=/var/chroot/trusty ExecStartPre=/bin/pwd ExecStart=/usr/bin/lsb_release -a You should have a chroot environment in the specified RootDirectory, even though you can still deduce if systemd attempted to chroot or not from the resulting error message. In my example, I installed an end-of-life Ubuntu 14.04 Trusty Tahr in the chroot environment. On systems NOT affected by the problem, I get the following result when I start this test service. This is what I'd expect. Jan 25 20:40:40 dolly systemd[1]: Starting LSB Release Information... Jan 25 20:40:40 dolly pwd[361]: / Jan 25 20:40:40 dolly systemd[1]: Started LSB Release Information. Jan 25 20:40:40 dolly lsb_release[362]: No LSB modules are available. Jan 25 20:40:40 dolly lsb_release[362]: Distributor ID:Ubuntu Jan 25 20:40:40 dolly lsb_release[362]: Description:Ubuntu 14.04 LTS Jan 25 20:40:40 dolly lsb_release[362]: Release:14.04 Jan 25 20:40:40 dolly lsb_release[362]: Codename:trusty Jan 25 20:40:40 dolly systemd[1]: lsb-release.service: Succeeded. On the problematic system, however, I get the following result. Jan 25 21:21:08 savelog systemd[1]: Starting LSB Release Information... Jan 25 21:21:08 savelog systemd[1]: Started LSB Release Information. Jan 25 21:21:08 savelog pwd[81114]: / Jan 25 21:21:08 savelog lsb_release[81115]: No LSB modules are available. Jan 25 21:21:08 savelog lsb_release[81115]: Distributor ID:Ubuntu Jan 25 21:21:08 savelog lsb_release[81115]: Description:Ubuntu Jammy Jellyfish (development branch) Jan 25 21:21:08 savelog lsb_release[81115]: Release:22.04 Jan 25 21:21:08 savelog lsb_release[81115]: Codename:jammy Jan 25 21:21:08 savelog systemd[1]: lsb-release.service: Deactivated successfully. It totally run the service on the host's root filesystem, it didn't care even the slightest that a RootDirectory is specified. Tested on the following releases / systemd versions: Ubuntu 18.04.6 Bionic Beaver – ISSUE NOT PRESENT systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid Ubuntu 20.04.3 Focal Fossa – ISSUE NOT PRESENT systemd 245 (245.4-4ubuntu3.15) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Ubuntu 21.10 Impish Indri – ISSUE NOT PRESENT systemd 248 (248.3-1ubuntu8.2) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Ubuntu 22.04 Jammy Jellyfish (development branch) – ISSUE PRESENT systemd 249 (249.5-2ubuntu4) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Note that the problem is produced under an LXC container; since systemd detects virtualization, it might change how it behaves. It's either a bug or an intentional change I don't understand yet (i.e. the RootDirectory option has deprecated and is about to be replaced with something else, or there are additional conditions to be met before RootDirectory is considered), but I think in the latter case I should at least get a warning that there is a change in configuration. I imagine suddenly everyone's existing service units utilizing RootDirectory silently stop working without any information regarding why. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959047/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1959047] Re: systemd ignores RootDirectory option in .service units
This is caused by https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/patches/debian/UBUNTU- Revert-namespace-be-more-careful-when-handling- namespacin.patch?h=ubuntu/jammy From upstream's point of view, ignoring sandboxing options requested by unit owners is quite dangerous. It can result in programs running completely unconstrained. See: https://github.com/systemd/systemd/issues/22760 ** Bug watch added: github.com/systemd/systemd/issues #22760 https://github.com/systemd/systemd/issues/22760 ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units Status in systemd package in Ubuntu: Confirmed Bug description: The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the following contents: # /etc/systemd/system/lsb-release.service [Unit] Description=LSB Release Information [Service] Type=simple RootDirectory=/var/chroot/trusty ExecStartPre=/bin/pwd ExecStart=/usr/bin/lsb_release -a You should have a chroot environment in the specified RootDirectory, even though you can still deduce if systemd attempted to chroot or not from the resulting error message. In my example, I installed an end-of-life Ubuntu 14.04 Trusty Tahr in the chroot environment. On systems NOT affected by the problem, I get the following result when I start this test service. This is what I'd expect. Jan 25 20:40:40 dolly systemd[1]: Starting LSB Release Information... Jan 25 20:40:40 dolly pwd[361]: / Jan 25 20:40:40 dolly systemd[1]: Started LSB Release Information. Jan 25 20:40:40 dolly lsb_release[362]: No LSB modules are available. Jan 25 20:40:40 dolly lsb_release[362]: Distributor ID:Ubuntu Jan 25 20:40:40 dolly lsb_release[362]: Description:Ubuntu 14.04 LTS Jan 25 20:40:40 dolly lsb_release[362]: Release:14.04 Jan 25 20:40:40 dolly lsb_release[362]: Codename:trusty Jan 25 20:40:40 dolly systemd[1]: lsb-release.service: Succeeded. On the problematic system, however, I get the following result. Jan 25 21:21:08 savelog systemd[1]: Starting LSB Release Information... Jan 25 21:21:08 savelog systemd[1]: Started LSB Release Information. Jan 25 21:21:08 savelog pwd[81114]: / Jan 25 21:21:08 savelog lsb_release[81115]: No LSB modules are available. Jan 25 21:21:08 savelog lsb_release[81115]: Distributor ID:Ubuntu Jan 25 21:21:08 savelog lsb_release[81115]: Description:Ubuntu Jammy Jellyfish (development branch) Jan 25 21:21:08 savelog lsb_release[81115]: Release:22.04 Jan 25 21:21:08 savelog lsb_release[81115]: Codename:jammy Jan 25 21:21:08 savelog systemd[1]: lsb-release.service: Deactivated successfully. It totally run the service on the host's root filesystem, it didn't care even the slightest that a RootDirectory is specified. Tested on the following releases / systemd versions: Ubuntu 18.04.6 Bionic Beaver – ISSUE NOT PRESENT systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid Ubuntu 20.04.3 Focal Fossa – ISSUE NOT PRESENT systemd 245 (245.4-4ubuntu3.15) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Ubuntu 21.10 Impish Indri – ISSUE NOT PRESENT systemd 248 (248.3-1ubuntu8.2) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Ubuntu 22.04 Jammy Jellyfish (development branch) – ISSUE PRESENT systemd 249 (249.5-2ubuntu4) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Note that the problem is produced under an LXC container; since systemd detects virtualization, it might change how it behaves. It's either a bug or an intentional change I don't understand yet (i.e. the RootDirectory option has deprecated and is about to be replaced with something else,
[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Fixed also in systemd v250.4 and v249.11 -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: New Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: New Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel
[Touch-packages] [Bug 1961610] Re: i386: seed inclusion for libfakechroot
Bug against fakechroot: https://bugs.launchpad.net/ubuntu/+source/fakechroot/+bug/1875298 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1961610 Title: i386: seed inclusion for libfakechroot Status in ubuntu-meta package in Ubuntu: New Bug description: As per instructions on https://wiki.ubuntu.com/i386 fakechroot (arch: all) requires libfakechroot, but this is not built for i386: https://packages.ubuntu.com/jammy/libfakechroot init-system-helpers, which builds a package allow-listed for i386 builds, now build-depends on fakechroot for build-time unit tests, but given libfakechroot is not available for i386, the i386 build cannot start and thus migration from proposed is held back: https://launchpad.net/ubuntu/+source/init-system-helpers https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html init-system-helpers (1.61 to 1.62) Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: missing build on i386: init (from 1.61) Please enable the libfakechroot i386 build. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1961610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961610] Re: i386: seed inclusion for libfakechroot
Note that the only dependency is libjemalloc, whicih already has an i386 build, so there would be no other new i386 builds apart from libfakechroot itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1961610 Title: i386: seed inclusion for libfakechroot Status in ubuntu-meta package in Ubuntu: New Bug description: As per instructions on https://wiki.ubuntu.com/i386 fakechroot (arch: all) requires libfakechroot, but this is not built for i386: https://packages.ubuntu.com/jammy/libfakechroot init-system-helpers, which builds a package allow-listed for i386 builds, now build-depends on fakechroot for build-time unit tests, but given libfakechroot is not available for i386, the i386 build cannot start and thus migration from proposed is held back: https://launchpad.net/ubuntu/+source/init-system-helpers https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html init-system-helpers (1.61 to 1.62) Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: missing build on i386: init (from 1.61) Please enable the libfakechroot i386 build. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1961610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961610] [NEW] i386: seed inclusion for libfakechroot
Public bug reported: As per instructions on https://wiki.ubuntu.com/i386 fakechroot (arch: all) requires libfakechroot, but this is not built for i386: https://packages.ubuntu.com/jammy/libfakechroot init-system-helpers, which builds a package allow-listed for i386 builds, now build-depends on fakechroot for build-time unit tests, but given libfakechroot is not available for i386, the i386 build cannot start and thus migration from proposed is held back: https://launchpad.net/ubuntu/+source/init-system-helpers https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html init-system-helpers (1.61 to 1.62) Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: missing build on i386: init (from 1.61) Please enable the libfakechroot i386 build. Thank you! ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1961610 Title: i386: seed inclusion for libfakechroot Status in ubuntu-meta package in Ubuntu: New Bug description: As per instructions on https://wiki.ubuntu.com/i386 fakechroot (arch: all) requires libfakechroot, but this is not built for i386: https://packages.ubuntu.com/jammy/libfakechroot init-system-helpers, which builds a package allow-listed for i386 builds, now build-depends on fakechroot for build-time unit tests, but given libfakechroot is not available for i386, the i386 build cannot start and thus migration from proposed is held back: https://launchpad.net/ubuntu/+source/init-system-helpers https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html init-system-helpers (1.61 to 1.62) Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: missing build on i386: init (from 1.61) Please enable the libfakechroot i386 build. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1961610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1938983] Re: missing modules after 5.11.0-25-generic update
Bug affects also to me in upgrading to 5.11.0-27 ~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal The solution proposed by @MikeR works for me: I have created a file t.txt with missing modules with the base LinuxFromScratch URL: https://anduin.linuxfromscratch.org/sources/linux- firmware/i915/ and then ~$ cd /lib/firmware/i915/ /lib/firmware/i915$ cat ~/tmp/t.txt | while read a; do sudo wget $a; done /lib/firmware/i915$ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic update-initramfs: Generating /boot/initrd.img-5.8.0-63-generic Thank you all guys, maybe files should be integrated in `linux-firmware` package? Can any janitor confirm pls so me or someone of my FSUG can try to propose a patch for the package itself? ** Attachment added: "My list of "probably missing modules". BEWARE your list can be different!" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938983/+attachment/5520102/+files/t.txt -- 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/1938983 Title: missing modules after 5.11.0-25-generic update Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After updating to kernel 5.11.0-25-generic wireless driver failed to recognize WiFi card. Possible reasons/symptoms: $ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.8.0-63-generic $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: July2021 Release: 20.04 Codename: focal Workaround: connected Ethernet. (Inconvenient) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920248] Re: Anker Soundcore Life Q10 microphone not working
Hi Daniel, no, if I change the profile from A2DP to HSP/HFP nothing changes and the microphone is still not working. -- 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/1920248 Title: Anker Soundcore Life Q10 microphone not working Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a ThinkPad E560 with ubuntu 20.04 and I'm trying to use my Soundcore Life Q10 with it, but the microphone doesn't work. I tried also to follow some answers here, but no one worked for me. I tried to use blueman, but I get Failed to change profile to headset_head_unit. I tried to install oFono, but I cannot compile phonesim due to some problem with dependencies version. I think that PulseAudio does not support HFP out of the box, and I found many other people that has this problem (see for example https://itectec.com/ubuntu/ubuntu-use-bluetooth-headset-with- microphone-hfp-in-ubuntu-18-04/) Is there any way to make my headset working? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1920248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920248] [NEW] Anker Soundcore Life Q10 microphone not working
Public bug reported: I have a ThinkPad E560 with ubuntu 20.04 and I'm trying to use my Soundcore Life Q10 with it, but the microphone doesn't work. I tried also to follow some answers here, but no one worked for me. I tried to use blueman, but I get Failed to change profile to headset_head_unit. I tried to install oFono, but I cannot compile phonesim due to some problem with dependencies version. I think that PulseAudio does not support HFP out of the box, and I found many other people that has this problem (see for example https://itectec.com/ubuntu/ubuntu-use-bluetooth-headset-with-microphone- hfp-in-ubuntu-18-04/) Is there any way to make my headset working? ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth microphone pulseaudio -- 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/1920248 Title: Anker Soundcore Life Q10 microphone not working Status in pulseaudio package in Ubuntu: New Bug description: I have a ThinkPad E560 with ubuntu 20.04 and I'm trying to use my Soundcore Life Q10 with it, but the microphone doesn't work. I tried also to follow some answers here, but no one worked for me. I tried to use blueman, but I get Failed to change profile to headset_head_unit. I tried to install oFono, but I cannot compile phonesim due to some problem with dependencies version. I think that PulseAudio does not support HFP out of the box, and I found many other people that has this problem (see for example https://itectec.com/ubuntu/ubuntu-use-bluetooth-headset-with- microphone-hfp-in-ubuntu-18-04/) Is there any way to make my headset working? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1920248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863369] Re: Livepatch is running, but appears OFF in 'software & updates'
I also have the same exact issue (with Ubuntu 20.04.1). Livepatch is running: > sudo canonical-livepatch status last check: 1 minute ago kernel: 5.4.0-56.62-generic server check-in: succeeded patch state: ✓ no livepatches needed for this kernel yet but the 'Software & Updates' Livepatch tab also reports "Livepatch requires an internet connection"... although my machine is online all the time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1863369 Title: Livepatch is running, but appears OFF in 'software & updates' Status in software-properties package in Ubuntu: New Bug description: I have a similar problem to #1758980 Enabling LivePatch fails, but not so sure it is the same. When I verify Livepatch status (sudo canonical-livepatch status): client-version: 9.4.8 architecture: x86_64 cpu-model: Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz last-check: 2020-02-14T09:29:57-03:00 boot-time: 2020-02-14T07:29:23-03:00 uptime: 2h26m29s status: - kernel: 4.15.0-76.86-generic running: true livepatch: checkState: checked patchState: nothing-to-apply version: "" fixes: "" But in 'Software & Updates' Livepatch tab all I got is 'OFF', and I can't switch ON or click on it. It is written 'Livepatch requires an internet connection'. Is this a known bug to be ignored, or something else that must be fixed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1863369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Since it has been marked as "Fix Released", what are the required steps to follow in order to bypass the installation crash? Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in apt source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in glibc source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893967] [NEW] After reboot/power up, even if headphones are connected, the selected output are the speakers
Public bug reported: The bug is little: after power up/reboot the selected output for audio are always the speakers, even if the headphones are connected. Audio works as supposed, I have just to switch from speakers to headphones in the audio panel inside the settings page if I have headphones plugged in. My system is an upgrade from Ubuntu 16.04 LTS (now 18.04 LTS) uname -a output Linux muletto 5.4.0-45-generic #49~18.04.2-Ubuntu SMP Wed Aug 26 16:29:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd output Description:Ubuntu 18.04.5 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-45.49~18.04.2-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muletto5653 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Sep 2 17:37:39 2020 InstallationDate: Installed on 2016-09-04 (1459 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 5570, Realtek ALC3246, Black Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to bionic on 2018-08-21 (742 days ago) dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd08/15/2018:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1893967 Title: After reboot/power up, even if headphones are connected, the selected output are the speakers Status in alsa-driver package in Ubuntu: New Bug description: The bug is little: after power up/reboot the selected output for audio are always the speakers, even if the headphones are connected. Audio works as supposed, I have just to switch from speakers to headphones in the audio panel inside the settings page if I have headphones plugged in. My system is an upgrade from Ubuntu 16.04 LTS (now 18.04 LTS) uname -a output Linux muletto 5.4.0-45-generic #49~18.04.2-Ubuntu SMP Wed Aug 26 16:29:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd output Description: Ubuntu 18.04.5 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-45.49~18.04.2-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muletto5653 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Sep 2 17:37:39 2020 InstallationDate: Installed on 2016-09-04 (1459 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 5570, Realtek ALC3246, Black Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to bionic on 2018-08-21 (742 days ago) dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd08/15/2018:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893967/+subscriptions --
[Touch-packages] [Bug 1878469] [NEW] Ubuntu 20.04 causing green vertical stripes on my desktop
Public bug reported: As soon as I upgraded to Ubuntu 20.04, two green pixel stripes appeared on my desktop. They do not interfere with windows when opened, whether they are browsers, files or other items, and they do not seem to have an impact on the general behavior of the PC. Still, something tells me that they are not supposed to be there. I have a dual boot, Windows and Ubuntu, and two drivers: VGA compatbile controller: Intel UHD Graphics 630 (mobile) 3D controller: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] Any support would be welcome. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34 Uname: Linux 5.4.0-31-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 13 18:55:14 2020 DistUpgraded: 2020-05-13 13:02:22,581 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] InstallationDate: Installed on 2018-12-23 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-lowlatency root=UUID=d49b534b-1745-4089-80d9-cb11f85d2570 ro acpi=force nvidia.NVreg_EnableBacklightHandler=1 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-05-13 (0 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1878469 Title: Ubuntu 20.04 causing green vertical stripes on my desktop Status in xorg package in Ubuntu: New Bug description: As soon as I upgraded to Ubuntu 20.04, two green pixel stripes appeared on my desktop. They do not interfere with windows when opened, whether they are browsers, files or other items, and they do not seem to have an impact on the general behavior of the PC. Still, something tells me that they are not supposed to be there. I have a dual boot, Windows and Ubuntu, and two drivers: VGA compatbile controller: Intel UHD Graphics 630 (mobile) 3D controller: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] Any support would be welcome. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34 Uname: Linux 5.4.0-31-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 13 18:55:14 2020 DistUpgraded: 2020-05-13 13:02:22,581 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] InstallationDate: Installed on 2018-12-23 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus
[Touch-packages] [Bug 1871282] Re: libpam fails to install during upgrade from 19.10 to 20.20 beta
** Description changed: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' + + I had some extra repos added: + google-chrome + flacon-ubuntu-ppa-eoan + kubuntu-ppa-ubuntu-backports-disco + otto-kesselgulasch-ubuntu-gimp-bionic + virtualbox.list + skype-stable.list -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1871282 Title: libpam fails to install during upgrade from 19.10 to 20.20 beta Status in pam package in Ubuntu: New Bug description: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' I had some extra repos added: google-chrome flacon-ubuntu-ppa-eoan kubuntu-ppa-ubuntu-backports-disco otto-kesselgulasch-ubuntu-gimp-bionic virtualbox.list skype-stable.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871282] [NEW] libpam fails to install during upgrade from 19.10 to 20.20 beta
Public bug reported: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1871282 Title: libpam fails to install during upgrade from 19.10 to 20.20 beta Status in pam package in Ubuntu: New Bug description: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816271] Re: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19
Issue still reproducible on ubuntu 18.04 LTS -- 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/1816271 Title: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19 Status in pulseaudio package in Ubuntu: Invalid Bug description: 19.04,kern 4.19.0-13 just took update and now does not recognize soundcard or something plugged in to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it wakes up and recognizes it and works fine. I thought I had this prob a few days ago and restored back to the 10th, and updated all but alsa and worked fine. This morning I checked and a bunch of alsa stuff was no longer showing in updates, took everything, and worked fine. Just took updates (Software Updater), and checked speakers and no go. When this happened, it also would not allow sound to HDTV via HDMI, no matter what. Just tested and was able to get sound via hdmi, but remember, I have already "woken it up" by unplugging and plugging headphones (actually sony vaio computer speakers) ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast! I expected sound to recognize soundcard/speakers. It did not until I unplug/replug headphones. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 19:20:26 2019 InstallationDate: Installed on 2019-02-09 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gst-plugins-good1.0 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kris 1512 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-09 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Tags: disco Uname: Linux 4.19.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETB4WW (2.74 ) dmi.board.asset.tag: Not Available dmi.board.name: 23943J8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T530 dmi.product.name: 23943J8 dmi.product.sku: LENOVO_MT_2394 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1857099] [NEW] strerror_r used as non-portable format
Public bug reported: I got a elfutils-0.178 glibc provides two different signatures for strerror_r. One is GNU-specific and it is not portable. The other is int strerror_r(int errnum, char *buf, size_t buflen); /* XSI-compliant */ char *strerror_r(int errnum, char *buf, size_t buflen); /* GNU-specific */ man strerror(3) says: The XSI-compliant strerror_r() is preferred for portable applications. It returns the error string in the user-supplied buffer buf of length buflen. musl implements strerror_r as XSI-compliant version while elfutils uses GNU-specific variant. The solution should not simply ignore strerror_r return value as it would break build when -Werror=unused-result is set. An alternative is to do something like: https://github.com/luizluca/openwrt/blob/a79698fefdd9dacb84865c870bf75aee978c005d/package/libs/elfutils/patches/100 -musl-compat.patch#L51 ** Affects: elfutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1857099 Title: strerror_r used as non-portable format Status in elfutils package in Ubuntu: New Bug description: I got a elfutils-0.178 glibc provides two different signatures for strerror_r. One is GNU-specific and it is not portable. The other is int strerror_r(int errnum, char *buf, size_t buflen); /* XSI-compliant */ char *strerror_r(int errnum, char *buf, size_t buflen); /* GNU-specific */ man strerror(3) says: The XSI-compliant strerror_r() is preferred for portable applications. It returns the error string in the user-supplied buffer buf of length buflen. musl implements strerror_r as XSI-compliant version while elfutils uses GNU-specific variant. The solution should not simply ignore strerror_r return value as it would break build when -Werror=unused-result is set. An alternative is to do something like: https://github.com/luizluca/openwrt/blob/a79698fefdd9dacb84865c870bf75aee978c005d/package/libs/elfutils/patches/100 -musl-compat.patch#L51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1857099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
Issue appears since a week, more or less, in 18.04LTS -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: New Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193 The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838806] Re: vulkan apps makes desktop freeze with kernel 5.0 on amdgpu raven ridge
Fixed in mesa-vulkan-drivers:amd64 (19.0.8-0ubuntu0~18.04.3) ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released -- 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/1838806 Title: vulkan apps makes desktop freeze with kernel 5.0 on amdgpu raven ridge Status in mesa package in Ubuntu: Fix Released Bug description: After yesterday update to 5.0.0-23-generic of the linux-generic- hwe-18.04 kernel every vulkan applications (e.g. steam or vulkan- smoketest) make my desktop freeze (ssh continue working, but the only option is to use sysqr to reboot the system). Similar bug reports: https://github.com/ValveSoftware/steam-for-linux/issues/6268 says it has been fixed in mesa 19.X but don't specify which version this seems related too https://lists.freedesktop.org/archives/amd-gfx/2018-March/020569.html APU: ryzen 2200g workaround: use AMDVLK instead of RADV ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault (src_id:0 ring:158 vmid:3 pasid:32768, for process vulkan-smoketes pid 6759 thread vulkan-smoketes pid 6759) ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: in page starting at address 0x00174000 from 27 ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0030153D ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault (src_id:0 ring:158 vmid:3 pasid:32768, for process vulkan-smoketes pid 6759 thread vulkan-smoketes pid 6759) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mesa-vulkan-drivers (not installed) ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Aug 2 20:11:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] [1002:15dd] InstallationDate: Installed on 2018-11-30 (244 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.90 dmi.board.name: AB350M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.90:bd07/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1838806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838806] Re: vulkan apps makes desktop freeze with kernel 5.0 on amdgpu raven ridge
** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1838806/+attachment/5280568/+files/CurrentDmesg.txt -- 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/1838806 Title: vulkan apps makes desktop freeze with kernel 5.0 on amdgpu raven ridge Status in mesa package in Ubuntu: New Bug description: After yesterday update to 5.0.0-23-generic of the linux-generic- hwe-18.04 kernel every vulkan applications (e.g. steam or vulkan- smoketest) make my desktop freeze (ssh continue working, but the only option is to use sysqr to reboot the system). Similar bug reports: https://github.com/ValveSoftware/steam-for-linux/issues/6268 says it has been fixed in mesa 19.X but don't specify which version this seems related too https://lists.freedesktop.org/archives/amd-gfx/2018-March/020569.html APU: ryzen 2200g workaround: use AMDVLK instead of RADV ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault (src_id:0 ring:158 vmid:3 pasid:32768, for process vulkan-smoketes pid 6759 thread vulkan-smoketes pid 6759) ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: in page starting at address 0x00174000 from 27 ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0030153D ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault (src_id:0 ring:158 vmid:3 pasid:32768, for process vulkan-smoketes pid 6759 thread vulkan-smoketes pid 6759) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mesa-vulkan-drivers (not installed) ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Aug 2 20:11:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] [1002:15dd] InstallationDate: Installed on 2018-11-30 (244 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.90 dmi.board.name: AB350M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.90:bd07/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1838806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838806] [NEW] vulkan apps makes desktop freeze with kernel 5.0 on amdgpu raven ridge
Public bug reported: After yesterday update to 5.0.0-23-generic of the linux-generic- hwe-18.04 kernel every vulkan applications (e.g. steam or vulkan- smoketest) make my desktop freeze (ssh continue working, but the only option is to use sysqr to reboot the system). Similar bug reports: https://github.com/ValveSoftware/steam-for-linux/issues/6268 says it has been fixed in mesa 19.X but don't specify which version this seems related too https://lists.freedesktop.org/archives/amd-gfx/2018-March/020569.html APU: ryzen 2200g workaround: use AMDVLK instead of RADV ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault (src_id:0 ring:158 vmid:3 pasid:32768, for process vulkan-smoketes pid 6759 thread vulkan-smoketes pid 6759) ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: in page starting at address 0x00174000 from 27 ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0030153D ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault (src_id:0 ring:158 vmid:3 pasid:32768, for process vulkan-smoketes pid 6759 thread vulkan-smoketes pid 6759) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mesa-vulkan-drivers (not installed) ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Aug 2 20:11:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] [1002:15dd] InstallationDate: Installed on 2018-11-30 (244 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.90 dmi.board.name: AB350M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.90:bd07/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1838806/+attachment/5280554/+files/CurrentDmesg.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1838806/+attachment/5280557/+files/Lsusb.txt -- 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/1838806 Title: vulkan apps makes desktop freeze with kernel 5.0 on amdgpu raven ridge Status in mesa package in Ubuntu: New Bug description: After yesterday update to 5.0.0-23-generic of the linux-generic- hwe-18.04 kernel every vulkan applications (e.g. steam or vulkan- smoketest) make my desktop freeze (ssh continue working, but the only option is to use sysqr to reboot the system). Similar bug reports: https://github.com/ValveSoftware/steam-for-linux/issues/6268 says it has been fixed in mesa 19.X but don't specify which version this seems related too https://lists.freedesktop.org/archives/amd-gfx/2018-March/020569.html APU: ryzen 2200g workaround: use AMDVLK instead of RADV ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault (src_id:0 ring:158
[Touch-packages] [Bug 1835213] Re: CVE-2019-13132
Hello, I have made the report public. The issue has been posted to oss- security, and the upstream releases are in progress and will be available in a few minutes. ** 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 zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1835213 Title: CVE-2019-13132 Status in zeromq3 package in Ubuntu: In Progress Bug description: Dear Security Team, I am the upstream maintainer of libzmq/zeromq - https://github.com/zeromq/libzmq CVE-2019-13132 has been reported privately, and I have confirmed it is not only valid but quite bad (TM). The bug allows any unauthenticated client to cause a stack overflow on any server that is supposed to be protected by encryption/authentication. Arbitrary data sent by the client will overwrite the stack, so although the reporter didn't provide a specific exploit, it is entirely possible that a crafty attacker could take advantage of this vulnerability to do more than "just" crash the server. The bug affects all libzmq/zeromq releases from 4.0.0 onward. Any server running with CURVE encryption/authentication is vulnerable. Due to the severity, I have not yet published the details on the CVE or the issue tracker, and would like to do a release before it is disclosed, to let the fix percolate in all distros. The proposed plan is as follows: I will release upstream versions 4.3.2, 4.1.7 and 4.0.9 on Monday the 8th of July at 16:00 UTC. I would kindly ask to hold on publishing the security updates with the attached patches until the above time or later, as your schedule permits, if possible. The CVE details and the upstream issue tracker will then be published a week later, on the 15th. The per-version patches cover the following distro releases: xenial 4.1.4 bionic 4.2.5 cosmic 4.2.5 disco 4.3.1 Thank you for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1835213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835315] [NEW] Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs
Public bug reported: Ubuntu version: 18.04.2 LTS Mesa version: 19.0.2 Mesa-vulkan-driver version: 19.0.2, POLARIS10, DRM 3.27.0, 5.0.0-20-generic, LLVM 8.0.0) Video card: AMD RX 580 8GB, There is an issue when the Vulkan mesa RADV drivers are compiled with LLVM 8, due to an LLVM 8 bug, resulting in no visual output in some programs using the RADV Vulkan backend Upgrading to a mesa build compiled with LLVM 9, or reverting back to the bionic version from bionic-updates (which uses LLVM 6) fixes the problem. Using the AMDVLK vulkan driver workarounds the problem too. The program I have personally tested is RPCS3 I could put additional info about the LLVM bug but at this moment I do not have the upstream reference ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1835315 Title: Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs Status in mesa package in Ubuntu: New Bug description: Ubuntu version: 18.04.2 LTS Mesa version: 19.0.2 Mesa-vulkan-driver version: 19.0.2, POLARIS10, DRM 3.27.0, 5.0.0-20-generic, LLVM 8.0.0) Video card: AMD RX 580 8GB, There is an issue when the Vulkan mesa RADV drivers are compiled with LLVM 8, due to an LLVM 8 bug, resulting in no visual output in some programs using the RADV Vulkan backend Upgrading to a mesa build compiled with LLVM 9, or reverting back to the bionic version from bionic-updates (which uses LLVM 6) fixes the problem. Using the AMDVLK vulkan driver workarounds the problem too. The program I have personally tested is RPCS3 I could put additional info about the LLVM bug but at this moment I do not have the upstream reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835315/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1602900] Re: libzmq3 crashes when 'getifaddrs()' is unavailable
Fixed since Bionic ** Changed in: zeromq3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1602900 Title: libzmq3 crashes when 'getifaddrs()' is unavailable Status in IPython: Fix Released Status in zeromq3 package in Ubuntu: Fix Released Bug description: libzmq3 crashes when used on a computer where the kernel is unable to provide any information about network-device addresses. This is uncommon with normal Ubuntu configurations. But is currently always the case with Ubuntu as run under the new Windows Subsystem for Linux. This has already been diagnosed and fixed upstream: https://github.com/jupyter/notebook/issues/1331 I have backported the fix; an updated package (based on the stock Ubuntu 14.04 package but with the backport as an added patch) is available in this PPA: https://launchpad.net/~aseering/+archive/ubuntu/wsl This has been reported in a couple other bugtrackers. Even with the fix in a PPA, there's still some amount of user confusion: https://github.com/jupyter/notebook/issues/1331 https://github.com/Microsoft/BashOnWindows/issues/185 It would be great if this fix could be pulled into Ubuntu 14.04 directly, so that people stop hitting this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ipython/+bug/1602900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833532] Re: systemd-backlight does not restore screen brightness after reboot
After resetting the BIOS this doesn't happen anymore... ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833532 Title: systemd-backlight does not restore screen brightness after reboot Status in systemd package in Ubuntu: Incomplete Bug description: As the title says, on this laptop the brightness controls are NOT saved after reboot. What is saved instead, is only the keyboard brightness. I have tested two distros, Ubuntu 18.04.2 LTS and 19.04, happens on both systems. But there is a difference On 19.04, "systemctl status systemd-backlight@:*intel_screen_backlight_*" shows: "Saved brightness 20 too low, increasing to 75" On 18.04.2 does not show anything rather than the service starting normally The laptop is a Dell XPS 15 9550, the screen backlight driver is the intel one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833532] [NEW] systemd-backlight does not restore screen brightness after reboot
Public bug reported: As the title says, on this laptop the brightness controls are NOT saved after reboot. What is saved instead, is only the keyboard brightness. I have tested two distros, Ubuntu 18.04.2 LTS and 19.04, happens on both systems. But there is a difference On 19.04, "systemctl status systemd-backlight@:*intel_screen_backlight_*" shows: "Saved brightness 20 too low, increasing to 75" On 18.04.2 does not show anything rather than the service starting normally The laptop is a Dell XPS 15 9550, the screen backlight driver is the intel one. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833532 Title: systemd-backlight does not restore screen brightness after reboot Status in systemd package in Ubuntu: New Bug description: As the title says, on this laptop the brightness controls are NOT saved after reboot. What is saved instead, is only the keyboard brightness. I have tested two distros, Ubuntu 18.04.2 LTS and 19.04, happens on both systems. But there is a difference On 19.04, "systemctl status systemd-backlight@:*intel_screen_backlight_*" shows: "Saved brightness 20 too low, increasing to 75" On 18.04.2 does not show anything rather than the service starting normally The laptop is a Dell XPS 15 9550, the screen backlight driver is the intel one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
https://bugzilla.kernel.org/show_bug.cgi?id=195303 This bug tracker is more updated ** Summary changed: - Microphone distorted sound on ALC892 + Microphone distorted sound on ALC892/1220 on AMD chipsets -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Some info regarding this, looks like a common problem with also other different codecs and the only thing in common is the AMD chipset. The same codecs on Intel looks to play just fine -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Just for curiosity, how did you test if it works or not? I personally use this web program https://webcammictest.com/check- microphone.html So I can hear myself, and for me it is still present with every workaround I try... -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Tried that, it does not work for me Daemon.conf has sample rate of 48000 even in my case, and setting that module parameter still did not fix anything I'm stuck with an USB sound card again AMD chipset, ALC892 realtek codec -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811531] Re: remote execution vulnerability
Hi Eduardo, thanks for taking care of this. The amd64 binaries look fine to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: Fix Committed Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Unknown Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811531]
This issue has been assigned CVE-2019-6250 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811531]
(In reply to Luca Boccassi from comment #0) > The latest version will hopefully arrive in disco via debian unstable soon, > but I would recommend patching older releases. s/disco/tumbleweed/ s/debian unstable/obs factory/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811531] Re: remote execution vulnerability
This issue has been assigned CVE-2019-6250 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-6250 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811531] Re: remote execution vulnerability
** Description changed: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. + + [1] https://github.com/zeromq/libzmq/issues/3351 ** Bug watch added: Debian Bug tracker #919098 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919098 ** Also affects: zeromq3 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919098 Importance: Unknown Status: Unknown ** Bug watch added: bugzilla.opensuse.org/ #1121717 https://bugzilla.opensuse.org/show_bug.cgi?id=1121717 ** Also affects: zeromq (Suse) via https://bugzilla.opensuse.org/show_bug.cgi?id=1121717 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Unknown Status in zeromq package in Suse: Unknown Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811531] Re: remote execution vulnerability
Also note that this was introduced in 4.2.0, so xenial is not affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811531] [NEW] remote execution vulnerability
*** This bug is a security vulnerability *** Public security bug reported: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. ** Affects: zeromq3 (Ubuntu) Importance: Undecided Status: New ** Patch added: "backported patch for 4.2.5" https://bugs.launchpad.net/bugs/1811531/+attachment/5228726/+files/pointer_overflow.patch ** 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 zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Seems to be the same problem as https://bugzilla.kernel.org/show_bug.cgi?id=195303 With ALC1220 codecs The last comment was "I might have found the source of this problem at least for me. A while ago I set my Pulseaudio sample rate to 44100 to reduce crackling in my virtual machine audio but the sound card on my board runs at 48000. What I did: arecord --list-devices arecord -f dat -r 6 -D hw:CARDIDHERE,DEVICEIDHERE -d 5 test.wav arecord told me that it could not record of a rate of 6 and instead got 48000. This means my card has a sample rate of 48000 So I ran: arecord -f dat -r 48000 -D hw:1,0 -d 5 test.wav And suddenly I had a clear recording! The only problem is I have changed my sampling rate and alternate sample rate in /etc/pulse/daemon.conf back to 48000 but it still seems to be defaulting to 44100 in all programs. If I run: arecord -f cd -d 10 test-mic.wav I observe it defaulting to 44100 and playing it back sounds awful again. Same with any other recording software, they are all still using 44100 for some reason which is causing the crackling." This also applies to me, is there a temporary workaround for that I can apply to ALSA or Pulseaudio? ** Bug watch added: Linux Kernel Bug Tracker #195303 https://bugzilla.kernel.org/show_bug.cgi?id=195303 -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Done, for sending an email to them using that CC you mean without the bugzilla site? Should I just put the bugzilla link in that email? -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Yes I already did that but I may not understand how to add the required maintainers into the mailing list Here is it https://bugzilla.kernel.org/show_bug.cgi?id=201613 ** Bug watch added: Linux Kernel Bug Tracker #201613 https://bugzilla.kernel.org/show_bug.cgi?id=201613 -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Any updates on this? -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Tried all those values through HDAAnalyzer, but nothing relevant changed, the noise is still there. A note: In Windows or FreeBSD i was not using any echo cancel software, the noise is just not present. There is still tjhe normal environmental one, but not the robotic one only present on Linux. Here is a recording, amplified so you can easily hear the noise in question. If I don't amplify the input, the noise is still there, just the volume is low. ** Attachment added: "recording.ogg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+attachment/5216803/+files/recording.ogg -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
So yes even with the module-echo-cancel enabled is still happening, I'll try modifying the realtek patch on the kernel -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
1) Happens with both Front mic and Rear mic. 2) No, it still sounds bad. Something I found is that on FreeBSD is working fine. -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Uhm yes I know that, but apport-collect is just not working as I already said... -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
I tried running it, I don't know honestly if that worked because when I clicked on that link a browser page just appeared showing nothing relevant ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] [NEW] Microphone distorted sound on ALC892
Public bug reported: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "alsa-info" https://bugs.launchpad.net/bugs/1801540/+attachment/5208845/+files/alsa-info ** Package changed: alsa-lib (Ubuntu) => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892 Status in alsa-driver package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801320] [NEW] new icons on desktop should appear on primary display
Public bug reported: Have ubuntu 18.04 with communitheme Ubuntu is running on laptop (on my left side) while I have my external monitor in front of me (so on right side of the laptop), and primary desktop is on external monitor. If I create a new file on desktop the icon is aligned on left side is considering both screens, it should be aligned on left side only considering primary display. ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1801320 Title: new icons on desktop should appear on primary display Status in librsvg package in Ubuntu: New Bug description: Have ubuntu 18.04 with communitheme Ubuntu is running on laptop (on my left side) while I have my external monitor in front of me (so on right side of the laptop), and primary desktop is on external monitor. If I create a new file on desktop the icon is aligned on left side is considering both screens, it should be aligned on left side only considering primary display. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1801320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound
I'm getting the same on ALC892 -- 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/1716654 Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Have checked under windows (same computer in dual-boot & same headset), and the sound is crystal clear, so 99% sure this is not a hardware problem. Motherboard is ASUS Crosshair Hero 6. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: paul 2587 F pulseaudio /dev/snd/controlC0: paul 2587 F pulseaudio /dev/snd/controlC1: paul 2587 F pulseaudio /dev/snd/controlC2: paul 2587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 11:48:05 2017 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic successful Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.
Since yesterday's update, it is working now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1770176 Title: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange. Status in network-manager package in Ubuntu: Confirmed Bug description: In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour on my Dell XPS 15. This laptop doesn't have an integrated Ethernet port, so I've to use external USB 3.0 Ethernet adapters. When I boot Ubuntu with the adapter plugged in, the wired connection section in the top right menu doesn't show the "Via cavo collegato" section (in Italian, sorry... maybe in English it is "Through connected cable") in the correct way, often but not every time... The menu section title is sometimes " collegato" and expanding the section it doesn't list all the defined Ethernet connection profiles I've on my machine. To access all profiles and to change it I've to select the "Wired network settings" item in the section and so the system settings window appears and all defined profiles are there (so I can change connection by clicking here). Another strange behaviour occours with the "VPN" section in the same topright menu. I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN type). If I select one of this two profiles, VPN connection is established but the switch button in the menu doesn't reflect the state of the connection. To see the correct state of the VPN connection I've to open the "system settings" window, again. It seems there is some trouble in the topright menu communication with the NetworkManager subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1770176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.
Some follow-up. My wifi is disabled by default. Even being able to connect to an OpenVPN, the menu is not able to disconnect an OpenVPN connection (as it does not know it was up). As the reporter, I can only see the correct status using gnome setting. There I can enable/disable wifi, list wifi hotspots, connect to them, enable/disable OpenVPN, etc. And there, it also shows the correct visual feedback. The problem is only with the menu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1770176 Title: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange. Status in network-manager package in Ubuntu: Confirmed Bug description: In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour on my Dell XPS 15. This laptop doesn't have an integrated Ethernet port, so I've to use external USB 3.0 Ethernet adapters. When I boot Ubuntu with the adapter plugged in, the wired connection section in the top right menu doesn't show the "Via cavo collegato" section (in Italian, sorry... maybe in English it is "Through connected cable") in the correct way, often but not every time... The menu section title is sometimes " collegato" and expanding the section it doesn't list all the defined Ethernet connection profiles I've on my machine. To access all profiles and to change it I've to select the "Wired network settings" item in the section and so the system settings window appears and all defined profiles are there (so I can change connection by clicking here). Another strange behaviour occours with the "VPN" section in the same topright menu. I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN type). If I select one of this two profiles, VPN connection is established but the switch button in the menu doesn't reflect the state of the connection. To see the correct state of the VPN connection I've to open the "system settings" window, again. It seems there is some trouble in the topright menu communication with the NetworkManager subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1770176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.
Same here. I'm using lang pt_BR. I upgraded from 17.10. There is no text in the gnome top menu item which open the wired connections. Translation issues? The menu does not list any wireless settings/connection as if I had no wireless adapter. I do and it list and works when I use nmcli. OpenVPN items list correctly. When I click on any connection, it does connect correctly. However, the switch button in gnome menu is never on and there is no visual clue that something happened. Again, nmcli is simply correct. Maybe it is related to OpenVPN presence? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1770176 Title: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange. Status in network-manager package in Ubuntu: Confirmed Bug description: In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour on my Dell XPS 15. This laptop doesn't have an integrated Ethernet port, so I've to use external USB 3.0 Ethernet adapters. When I boot Ubuntu with the adapter plugged in, the wired connection section in the top right menu doesn't show the "Via cavo collegato" section (in Italian, sorry... maybe in English it is "Through connected cable") in the correct way, often but not every time... The menu section title is sometimes " collegato" and expanding the section it doesn't list all the defined Ethernet connection profiles I've on my machine. To access all profiles and to change it I've to select the "Wired network settings" item in the section and so the system settings window appears and all defined profiles are there (so I can change connection by clicking here). Another strange behaviour occours with the "VPN" section in the same topright menu. I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN type). If I select one of this two profiles, VPN connection is established but the switch button in the menu doesn't reflect the state of the connection. To see the correct state of the VPN connection I've to open the "system settings" window, again. It seems there is some trouble in the topright menu communication with the NetworkManager subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1770176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Many many many thanks :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Sorry guys to bother you, I'm the reporter of https://bugs.launchpad.net/ubuntu/+bug/1744045 Having this bug fixed exactly what does it means on Ubuntu 16.04 and on the upcoming 18.04? With a clean installation (on an encrypted disk) the boot partition will be removed automatically? Or do I have to upgrade manually /etc/apt/apt.conf.d/50unattended-upgrades uncommenting this parameter? //Unattended-Upgrade::Remove-Unused-Dependencies "true"; I'm asking since some of my colleagues doesn't use command line (so they don't use autoremove) and they rely on Software update Application. Thanks for understanding -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
in17.04 sound work with the patch, but my 64Gb microSD does not, nor the inernation. In addition if the notebook is closed, the sound is removed and does not return if the computer is not turned off and sometimes does not load correctly during boot. Unfortunately, this PC, even it's perfect with linux, was not born for this and even for windows that takes up all the memory... you have to adapt or sell it. Il gio 5 apr 2018 22:06 Devin Petroff <1563...@bugs.launchpad.net> ha scritto: > Just wanted to follow up on the status of this? It says fix committed > and released, however speakers/headphone jack still not supported in > 16.04.4 and 17.10.1 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1563110 > > Title: > No sound on Asus e200ha, intel sst with cx2072x codec > > Status in ALSA driver: > Unknown > Status in alsa-driver package in Ubuntu: > Fix Committed > Status in linux package in Ubuntu: > Fix Released > > Bug description: > I've recently bought an Asus e200ha. > Sound in this laptop doesn't work. > The sound card is an intel sst with codec conexant cx2072x > > aplay -l: > aplay: device_list:268: no soundcard found... > in the sound setting there is a "Dummy output" > --- > ApportVersion: 2.14.1-0ubuntu3.19 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: XFCE > DistroRelease: Ubuntu 14.04 > HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a > InstallationDate: Installed on 2016-03-28 (0 days ago) > InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 > Lsusb: >Bus 002 Device 002: ID 0781:5583 SanDisk Corp. >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 13d3:3496 IMC Networks >Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. E200HA > Package: linux (not installed) > ProcEnviron: >TERM=xterm >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=it_IT.UTF-8 >SHELL=/bin/bash > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic > root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 > RelatedPackageVersions: >linux-restricted-modules-3.19.0-32-generic N/A >linux-backports-modules-3.19.0-32-generic N/A >linux-firmware 1.127.16 > Tags: rosa > Uname: Linux 3.19.0-32-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 11/26/2015 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: E200HA.203 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: E200HA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: ATN12345678901234567 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.name: E200HA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002:
[Touch-packages] [Bug 1602900] Re: libzmq3 crashes when 'getifaddrs()' is unavailable
This is fixed since upstream version 4.2.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1602900 Title: libzmq3 crashes when 'getifaddrs()' is unavailable Status in IPython: New Status in zeromq3 package in Ubuntu: Confirmed Bug description: libzmq3 crashes when used on a computer where the kernel is unable to provide any information about network-device addresses. This is uncommon with normal Ubuntu configurations. But is currently always the case with Ubuntu as run under the new Windows Subsystem for Linux. This has already been diagnosed and fixed upstream: https://github.com/jupyter/notebook/issues/1331 I have backported the fix; an updated package (based on the stock Ubuntu 14.04 package but with the backport as an added patch) is available in this PPA: https://launchpad.net/~aseering/+archive/ubuntu/wsl This has been reported in a couple other bugtrackers. Even with the fix in a PPA, there's still some amount of user confusion: https://github.com/jupyter/notebook/issues/1331 https://github.com/Microsoft/BashOnWindows/issues/185 It would be great if this fix could be pulled into Ubuntu 14.04 directly, so that people stop hitting this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ipython/+bug/1602900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
The proposed fix works on my machine. Thanks. Ubuntu 16.04; Processor: Intel® Core™ i5 CPU M 540 @ 2.53GHz × 4; Graphics: Intel® Ironlake Mobile description: Laptop product: Latitude E4310 vendor: Dell Inc. version: 0001 serial: G4N8XN1 width: 64 bits capabilities: smbios-2.6 dmi-2.6 vsyscall32 configuration: boot=normal chassis=laptop uuid=44454C4C-3400-104E-8038-C7C04F584E31 *-core description: Motherboard product: 012JJ4 vendor: Dell Inc. physical id: 0 version: A01 *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: A15 date: 05/12/2017 size: 64KiB capacity: 960KiB *-display description: VGA compatible controller product: Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623792] Re: possible sigbus
The fix was released in version 4.2.0 last year and is available in
Ubuntu since Zesty.
** Changed in: zeromq3 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1623792
Title:
possible sigbus
Status in zeromq3 package in Ubuntu:
Fix Released
Bug description:
The following function looks like it will access a 32-bit data element
that is improperly aligned:
void zmq::socket_base_t::monitor_event (int event_, int value_, const
std::string _)
{
if (monitor_socket) {
// Send event in first frame
zmq_msg_t msg;
zmq_msg_init_size (, 6);
uint8_t *data = (uint8_t *) zmq_msg_data ();
*(uint16_t *) (data + 0) = (uint16_t) event_;
*(uint32_t *) (data + 2) = (uint32_t) value_;
zmq_sendmsg (monitor_socket, , ZMQ_SNDMORE);
// Send address in second frame
zmq_msg_init_size (, addr_.size());
memcpy (zmq_msg_data (), addr_.c_str (), addr_.size ());
zmq_sendmsg (monitor_socket, , 0);
}
}
On many platforms this will cause a SIGBUS.
It looks like upstream has already fixed this issue:
https://github.com/zeromq/libzmq/blob/master/src/socket_base.cpp#L1683
The current code looks like:
void zmq::socket_base_t::monitor_event (int event_, intptr_t value_, const
std::string _)
{
if (monitor_socket) {
// Send event in first frame
zmq_msg_t msg;
zmq_msg_init_size (, 6);
uint8_t *data = (uint8_t *) zmq_msg_data ();
// Avoid dereferencing uint32_t on unaligned address
uint16_t event = (uint16_t) event_;
uint32_t value = (uint32_t) value_;
memcpy (data + 0, , sizeof(event));
memcpy (data + 2, , sizeof(value));
zmq_sendmsg (monitor_socket, , ZMQ_SNDMORE);
// Send address in second frame
zmq_msg_init_size (, addr_.size());
memcpy (zmq_msg_data (), addr_.c_str (), addr_.size ());
zmq_sendmsg (monitor_socket, , 0);
}
}
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1623792/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718253] Re: dependency mismatch in libzmq3-dev and libzmq5-dev for Xenial
libzmq5-dev is a virtual package. libzmq5 is the correct dependency, and it is in Xenial: https://packages.ubuntu.com/xenial/libzmq5 ** Changed in: zeromq3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1718253 Title: dependency mismatch in libzmq3-dev and libzmq5-dev for Xenial Status in zeromq3 package in Ubuntu: Invalid Bug description: Trying to install libzmq5-dev instead selects libzmq3-dev. libzmq3-dev then has an incorrect dependency on libzmq5 instead of libzmq3, the latter of which is not available in the repos for Xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1718253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727390] Re: New bugfix release 17.2.4
** Changed in: mesa (Ubuntu) Status: New => Fix Released -- 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/1727390 Title: New bugfix release 17.2.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in mesa source package in Artful: New Bug description: [Impact] A new upstream bugfix release is available. Release note diff compared to 17.2.2: "Mesa 17.2.3 is now available. In this release we have: The Vulkan drivers ANV and RADV have multiple small fixes. The EGL code has improved handling of the new wl_dmabuf codepath. SWR no longer crashes when checking environment variables. Other gallium drivers have also seen updates - freedreno, nouveau and radeonsi. The gallivm module, used by llvmpipe et al. has gained little endian PPC64 fixes. The VA and VDPAU state-trackers have seems improvements handling interlaced videos. We're using python3 compatible constructs which gives us SCons 3.0 support." "Mesa 17.2.4 is now available. In this release we have: In Mesa Core we have included a change to prevent KOTOR from breaking when in combination with the ATI fragment shader extension. Additionally, NIR has also received a correction. Mesa's state tracker has gotten a patch to avoid leaks in certain situations like when resizing a window. Intel drivers have received several fixes. The compiler has gotten a couple, while anv also received one. i965 got a patch to avoid VA- API, Beignet and other contexts in the system to break when in combination with previous versions of Mesa 17.2.x. AMD's compiler has received a couple of fixes while radv has also received another couple, including one to avoid a hang due to an overflow on huge textures. Broadcom's vc4 has corrected a problem when compiling with Android's clang. clover has also seen fixed a problem compiling after a specific clang revision. Vulkan's WSI has gotten plugged a memory leak for X11." [Test case] Test typical use cases on the most common hw/driver combinations: intel/i965 nvidia/nouveau radeon/radeonsi [Regression potential] These releases are tested against compliance, bugfix releases in particular have minimal risk of regressing anything major at least. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721704] [NEW] Printer settings stuck on loading drivers database
Public bug reported: 1) Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 2) ubuntu-settings: Installed: 17.10.17 Candidate: 17.10.17 3) The printer configuration goes fine and I can print 4) Printer settings stuck on loading drivers database and finally no drivers list available. Only 'cancel' button active. Note: I'm trying to configure a Brother HL-2030 connected to Network through a FritzBox 7940 router. The printer works fine both on Fedora and macOS X systems. I opened 'System Settings', then select 'Devices' > 'Printers' > 'Add a Printer'. I entered the router address and the window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I selected the printer and pressed the 'Add' button, a window 'Select Printer Driver' appears and stuck with 'Loading drivers database...'. After about 2 minutes, stopped loading and remains blank. No drivers selection is available and I can only push the 'Cancel' button. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1721704 Title: Printer settings stuck on loading drivers database Status in ubuntu-settings package in Ubuntu: New Bug description: 1) Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 2) ubuntu-settings: Installed: 17.10.17 Candidate: 17.10.17 3) The printer configuration goes fine and I can print 4) Printer settings stuck on loading drivers database and finally no drivers list available. Only 'cancel' button active. Note: I'm trying to configure a Brother HL-2030 connected to Network through a FritzBox 7940 router. The printer works fine both on Fedora and macOS X systems. I opened 'System Settings', then select 'Devices' > 'Printers' > 'Add a Printer'. I entered the router address and the window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I selected the printer and pressed the 'Add' button, a window 'Select Printer Driver' appears and stuck with 'Loading drivers database...'. After about 2 minutes, stopped loading and remains blank. No drivers selection is available and I can only push the 'Cancel' button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1721704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720525] [NEW] Update package to newer version
Public bug reported: In Artful (and older releases) the version of the package is 0.4.7 even though 0.7.0 is already out. Debian Buster and Sid has 0.7.0 in the repos. The changes are bug fixes and features (see http://python-evdev.readthedocs.io/en/latest/changelog.html). ** Affects: python-evdev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1720525 Title: Update package to newer version Status in python-evdev package in Ubuntu: New Bug description: In Artful (and older releases) the version of the package is 0.4.7 even though 0.7.0 is already out. Debian Buster and Sid has 0.7.0 in the repos. The changes are bug fixes and features (see http://python-evdev.readthedocs.io/en/latest/changelog.html). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-evdev/+bug/1720525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1155307] Re: zconf.h header file is missing for 32 bits arch
This issue is more than 4 years old... Thanks Ubuntu... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1155307 Title: zconf.h header file is missing for 32 bits arch Status in zlib package in Ubuntu: Confirmed Bug description: zconf.h was moved to multiarch directory (zlib1g-dev package) because it contains an arch dependant declaration. Problem is programs using zlib doesn't compile anymore using 32bits target arch. (zconf.h is not found) I suppose a 32 bits version of zconf.h should be added into lib32z1-dev package ? Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 x86_64 lib32z1-dev 1:1.2.7.dfsg-13ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lib32z1-dev 1:1.2.7.dfsg-13ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 14 20:54:10 2013 InstallationDate: Installed on 2013-02-21 (21 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130221) MarkForUpload: True ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 XDG_RUNTIME_DIR= SourcePackage: zlib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1155307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690336] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Public bug reported: bug ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed May 10 18:56:29 2017 DuplicateSignature: package:gconf2-common:3.2.6-3ubuntu7 Setting up gconf2-common (3.2.6-3ubuntu7) ... dpkg: error processing package gconf2-common (--configure): subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2017-05-10 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1690336 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in gconf package in Ubuntu: New Bug description: bug ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed May 10 18:56:29 2017 DuplicateSignature: package:gconf2-common:3.2.6-3ubuntu7 Setting up gconf2-common (3.2.6-3ubuntu7) ... dpkg: error processing package gconf2-common (--configure): subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2017-05-10 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1690336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
Same issue on Acer Aspire ES1-111M-C1LE with Ubuntu 16.10 (before) and 17.04 (now). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition
Never had this problem before but now it's happening constantly on Ubuntu 16.04, I had to shut down the processes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/911981 Title: tracker-store uses 100% cpu and fills all the disk space in home partition Status in tracker package in Ubuntu: Confirmed Bug description: I recently noticed that several tracker related programs were using 100% cpu on my system and in particular tracker-store filled up completely all the available disk space in my home partition. I rerun tracker-preferences to make sure that indexing would not proceed if less than 20% of free space is available, but it seems that tracker-store ignores it. After I noticed that I had left only 44Kb free on the home partition, I deleted the cache from another program and I noticed that tracker-store filled up again the disk space that I freed few minutes before. This is the content of my .cache/tracker/ directory: totale 772068 -rw-r--r-- 1 eclipse eclipse 3072 2011-06-26 22:56 contents.db -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt -rw-r--r-- 1 eclipse eclipse 3072 2010-12-05 21:29 email-contents.db -rw-r--r-- 1 eclipse eclipse 3072 2009-05-06 19:16 email-fulltext.db -rw-r--r-- 1 eclipse eclipse 2359292 2011-06-26 22:54 email-index.db -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db -rw-r--r-- 1 eclipse eclipse 17062912 2011-06-26 19:30 file-contents.db -rw-r--r-- 1 eclipse eclipse 15014912 2010-01-12 20:26 file-fulltext.db -rw-r--r-- 1 eclipse eclipse 75609207 2011-06-26 22:54 file-index.db -rw-r--r-- 1 eclipse eclipse 37027840 2011-06-26 19:31 file-meta.db -rw--- 1 eclipse eclipse 1180048 2009-05-05 22:57 file-update-index.db -rw-r--r-- 1 eclipse eclipse 28376064 2011-10-20 09:34 fulltext.db -rw-r--r-- 1 eclipse eclipse 1024 2012-01-04 21:24 meta.db -rw-r--r-- 1 eclipse eclipse 4653056 2012-01-04 21:26 meta.db-shm -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 miner-applications-locale.txt -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb and this is how much space I have left on my home partition after I KILLED the tracker-store process: /dev/sda8 31G 30G 418M 99% /home --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 DistroRelease: Ubuntu 11.10 Package: tracker 0.10.24-1build2 PackageArchitecture: i386 ProcEnviron: LANGUAGE=it_IT:it:en_GB:en PATH=(custom, user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric Uname: Linux 3.0.0-14-generic i686 UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago) UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser pulse-access sambashare src video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/911981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
any news? -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1660042] [NEW] problem mouse notebook not work
Public bug reported: the mouse embedded in my notebook asux does not work. Only works one connected with USB ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jan 28 16:46:10 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:246a] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a] InstallationDate: Installed on 2017-01-13 (15 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X556UB ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=fb5d428d-a22c-43e8-8e66-c0b89de0d30a ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.405 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.405:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jan 28 16:43:42 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14573 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1660042 Title: problem mouse notebook not work Status in xorg package in Ubuntu: New Bug description: the mouse embedded in my notebook asux does not work. Only works one connected with USB ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jan 28 16:46:10 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:246a] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a] InstallationDate: Installed on 2017-01-13 (15 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X556UB ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=fb5d428d-a22c-43e8-8e66-c0b89de0d30a ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.405 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10
[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.
Xenial's package worked for me, although I got these warnings (I guess is an unrelated problem though): /etc/cron.daily/update-notifier-common: Get:1 http://downloads.sourceforge.net/corefonts/andale32.exe [198 kB] Fetched 198 kB in 2s (69,3 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/andale32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Get:1 http://downloads.sourceforge.net/corefonts/arial32.exe [554 kB] Fetched 554 kB in 3s (155 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/arial32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Get:1 http://downloads.sourceforge.net/corefonts/arialb32.exe [168 kB] Fetched 168 kB in 2s (62,1 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/arialb32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Get:1 http://downloads.sourceforge.net/corefonts/comic32.exe [246 kB] Fetched 246 kB in 2s (87,9 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/comic32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Get:1 http://downloads.sourceforge.net/corefonts/courie32.exe [646 kB] Fetched 646 kB in 3s (165 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/courie32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Get:1 http://downloads.sourceforge.net/corefonts/georgi32.exe [392 kB] Fetched 392 kB in 3s (119 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/georgi32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Get:1 http://downloads.sourceforge.net/corefonts/impact32.exe [173 kB] Fetched 173 kB in 2s (62,5 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/impact32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Get:1 http://downloads.sourceforge.net/corefonts/times32.exe [662 kB] Fetched 662 kB in 3s (177 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/times32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Get:1 http://downloads.sourceforge.net/corefonts/trebuc32.exe [357 kB] Fetched 357 kB in 3s (115 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/trebuc32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Get:1 http://downloads.sourceforge.net/corefonts/verdan32.exe [352 kB] Fetched 352 kB in 3s (113 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/verdan32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Get:1 http://downloads.sourceforge.net/corefonts/webdin32.exe [185 kB] Fetched 185 kB in 2s (66,7 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/webdin32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) After that there was more output (without errors) but the process succeeded. -- 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/1651923 Title: apt https method decodes redirect locations and sends them to the destination undecoded. Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Bug description: [Impact] Downloads via HTTPS fail if the URL contains a space (before yakkety only if there is no redirect from a previous space-free https URL). This breaks packages like ttf-mscorefonts-installer and various third party hosters. [Test case] Install/Upgrade apt-transport-https, that's where the fix is. Check that /usr/lib/apt/apt-helper download-file http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb test.deb can successfully download the file (or at least start downloading it) and does not fail early with a 505 HTTP version not supported error message. This problem does not occur with that file on xenial, as it first redirects to an https URI without a space which then redirects to an HTTPS uri with a space (http w/o space -> https w/o space -> https w/ space). In xenial, https->https redirects where handled internally by curl. Another test (applicable to xenial) is to install
[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.
Should we test that package too in xenial? Or there will be another test package for xenial? -- 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/1651923 Title: apt https method decodes redirect locations and sends them to the destination undecoded. Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Bug description: [Impact] Downloads via HTTPS fail if the URL contains a space. This breaks packages like ttf-mscorefonts-installer and various third party hosters. [Test case] Check that /usr/lib/apt/apt-helper download-file http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb test.deb can successfully download the file (or at least start downloading it) and does not fail early with a 505 HTTP version not supported error message. [Regression potential] The added code is: Uri.Path = QuoteString(Uri.Path, "+~ "); Some servers might not like + or ~ being quoted. We use the same quoting call for the http method too, though, so it seems highly unlikely to cause an issue. [Original bug report] Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety apt version 1.3.3 (also tried 1.4-beta2 .deb, same results) When trying to install a package hosted on s3 from the kxstudio repo, the download fails with an HTTP error: nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: wine1.6-amd64 The following NEW packages will be installed wine1.6-amd64 wineasio-amd64 0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade. Need to get 30.9 kB/32.6 kB of archives. After this operation, 184 kB of additional disk space will be used. Do you want to continue? [Y/n] y Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 amd64 0.9.0+git20110613-2kxstudio3 505 HTTP Version not supported E: Failed to fetch https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment; filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream 505 HTTP Version not supported E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Error allegedly not present in Ubuntu 14.04 and 16.04 More details in these forum posts: https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503 https://www.linuxmusicians.com/viewtopic.php?t=16056 https://www.drupal.org/node/2324991 (clues on root cause) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apt 1.3.3 ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6 Uname: Linux 4.8.0-30-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Dec 22 02:31:47 2016 InstallationDate: Installed on 2016-10-20 (62 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
