[Touch-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by kdesu
** No longer affects: software-properties (Ubuntu) ** No longer affects: software-properties (Ubuntu Impish) ** No longer affects: software-properties (Ubuntu Jammy) ** No longer affects: policykit-1 (Ubuntu Impish) ** No longer affects: policykit-1 (Ubuntu Jammy) ** No longer affects: policykit-1 (Ubuntu) ** Summary changed: - software-properties-qt can no longer launch when called by kdesu + applications can no longer launch when called by kdesu ** Also affects: ubuntustudio-default-settings via https://bugs.kde.org/show_bug.cgi?id=452532 Importance: Unknown Status: Unknown ** No longer affects: ubuntustudio-default-settings ** No longer affects: ubuntustudio-default-settings (Ubuntu Impish) ** No longer affects: sudo (Ubuntu Impish) ** No longer affects: kubuntu-settings (Ubuntu Impish) ** No longer affects: kdesu (Ubuntu Impish) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Confirmed Status in kubuntu-settings package in Ubuntu: In Progress Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu
** Also affects: sudo (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Also affects: ubuntustudio-default-settings (Ubuntu Kinetic) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Also affects: kubuntu-settings (Ubuntu Kinetic) Importance: High Status: In Progress ** Also affects: kdesu (Ubuntu Kinetic) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Confirmed Status in kubuntu-settings package in Ubuntu: In Progress Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Confirmed Status in kubuntu-settings source package in Kinetic: In Progress Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011624 ** Bug watch added: Debian Bug tracker #1011624 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011624 ** Also affects: kdesu (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011624 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Confirmed Status in kubuntu-settings package in Ubuntu: In Progress Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Confirmed Status in kubuntu-settings source package in Kinetic: In Progress Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: In Progress Status in kdesu package in Debian: Unknown Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu
** Changed in: kdesu (Ubuntu Jammy) Assignee: (unassigned) => Rik Mills (rikmills) ** Changed in: kdesu (Ubuntu Kinetic) Assignee: (unassigned) => Rik Mills (rikmills) ** Changed in: kdesu (Ubuntu Kinetic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Fix Committed Status in kubuntu-settings package in Ubuntu: In Progress Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Committed Status in kubuntu-settings source package in Kinetic: In Progress Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: In Progress Status in kdesu package in Debian: Unknown Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu
** Changed in: kubuntu-settings (Ubuntu Kinetic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Committed Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: Fix Committed Status in kdesu package in Debian: New Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu
** Changed in: kdesu (Ubuntu Jammy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing
> Is it necessary for wireplumber to conflict with pipewire-media-session? > Should we add Replaces? wireplumber already conflicts/replaces pipewire-media-session It was not shown in the image I posted on IRC, but pipewire-media- session was 'removed' at the start of the apt full-upgrade Sadly it was removed and NOT purged Currently in Kubuntu Kinetic it is required to 'apt purge pipewire- media-session' to get things working if you also remove pulseaudio to complete the pipewire switch -- 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/1977564 Title: wireplumber conflicts with pipewire-media-session & needs fixing Status in pipewire-media-session package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Triaged Status in wireplumber package in Ubuntu: Triaged Status in pipewire-media-session package in Debian: Confirmed Bug description: This issue was reported on IRC and we should probably fix it before installing wireplumber by default so I'm setting the block-proposed tag. https://i.imgur.com/L5VFZO8.png wireplumber is apparently too forceful in how it enables PipeWire. Both Arch Linux and Debian had to https://archlinux.org/news/undone-replacement-of-pipewire-media- session-with-wireplumber/ Is it necessary for wireplumber to conflict with pipewire-media- session? Should we add Replaces? What files does pipewire-media-session need to clean up when it is removed? See https://salsa.debian.org/gnome-team/gnome-remote- desktop/-/commit/52799cfd for an example of how files that aren't technically conffiles can be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing
The pipewire-media-session postrm is:
#!/bin/sh
set -e
# Automatically added by dh_installsystemduser/13.7.1ubuntu1
if [ "$1" = "remove" ]; then
if [ -z "${DPKG_ROOT:-}" ] && [ -x "/usr/bin/deb-systemd-helper" ] ;
then
deb-systemd-helper --user mask 'pipewire-media-session.service'
>/dev/null || true
fi
fi
if [ "$1" = "purge" ]; then
if [ -z "${DPKG_ROOT:-}" ] && [ -x "/usr/bin/deb-systemd-helper" ] ;
then
deb-systemd-helper --user purge
'pipewire-media-session.service' >/dev/null || true
deb-systemd-helper --user unmask
'pipewire-media-session.service' >/dev/null || true
fi
fi
# End automatically added section
--
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/1977564
Title:
wireplumber conflicts with pipewire-media-session & needs fixing
Status in pipewire-media-session package in Ubuntu:
Triaged
Status in ubuntu-meta package in Ubuntu:
Triaged
Status in wireplumber package in Ubuntu:
Triaged
Status in pipewire-media-session package in Debian:
Confirmed
Bug description:
This issue was reported on IRC and we should probably fix it before
installing wireplumber by default so I'm setting the block-proposed
tag.
https://i.imgur.com/L5VFZO8.png
wireplumber is apparently too forceful in how it enables PipeWire.
Both Arch Linux and Debian had to
https://archlinux.org/news/undone-replacement-of-pipewire-media-
session-with-wireplumber/
Is it necessary for wireplumber to conflict with pipewire-media-
session?
Should we add Replaces?
What files does pipewire-media-session need to clean up when it is
removed?
See https://salsa.debian.org/gnome-team/gnome-remote-
desktop/-/commit/52799cfd for an example of how files that aren't
technically conffiles can be removed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu
** Description changed: - See description below. As the driver manager is done inside software- - properties-qt, it's basically the same bug, but now it's affected by - something we can't exactly get into the mechanism of: plasma-discover's - "Software Sources" link. + kdesu fails to authenticate with sudo from Jammy. - Steps to recrate: + See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 - 1) Open Plasma-discover - 2) Go to Settings - 3) Under click on "Software Sources" - 4) Attempt to enter password + Examples: Kubuntu driver manager, launching ksystemlog from the main + menu, or trying to run krusader root mode option via its 'Tools > Start + Krusader Root Mode' menu entry. Assuming that the current user is a + member of the sudo group. - Expected: Software properties opens + On entering the correct password authentication is refused, stating that + possibly an incorrect password has been entered. - Actual: Pkexec keeps asking for password. + It appears that kdesu fails to cope with the sudo config change in this + commit: - -- + https://salsa.debian.org/sudo- + team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 - Earlier description: + kdesu was fixed in Debian with: - The driver manager for both Ubuntu Studio and Kubuntu can no longer - launch due to some updated security measures in PolicyKit. + https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- + into-unstable/ - The original behavior was that systemsettings would open - /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-manger) - via pkexec, which would then open software-settings-qt. Unfortunately, - the new behavior does not act correctly to pkexec and pkexec does not - see the user as available in the sudoers file. + The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers + with the contents - The only way around this was to pass "export DISPLAY=:0" inside the - appropriate driver manager executable with the command "sudo software- - properties-qt". The KCM itself needs to execute the driver-manager via - xterm, which then prompts for a password. It's ugly, but it works. - - I will attach a debdiff for the kubuntu-settings package. + Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] ** Summary changed: - applications can no longer launch when called by kdesu + kdesu fails to authenticate with sudo from Jammy. ** Description changed: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Kubuntu driver manager, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. - On entering the correct password authentication is refused, stating that + On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. - It appears that kdesu fails to cope with the sudo config change in this + It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ + + and fixed in kinetic with: + + https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 1
[Touch-packages] [Bug 1965439] Re: kdesu fails to authenticate with sudo from Jammy.
** Description changed: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 - Examples: Kubuntu driver manager, launching ksystemlog from the main - menu, or trying to run krusader root mode option via its 'Tools > Start - Krusader Root Mode' menu entry. Assuming that the current user is a - member of the sudo group. + Examples: Launch Kubuntu driver manager from system setting, launching + ksystemlog from the main menu, or trying to run krusader root mode + option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming + that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty - ProblemType: Bug - DistroRelease: Ubuntu 22.04 - Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] - ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 - Uname: Linux 5.15.0-22-lowlatency x86_64 - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia - ApportVersion: 2.20.11-0ubuntu79 - Architecture: amd64 - CasperMD5CheckResult: unknown - CurrentDesktop: KDE - Date: Thu Mar 17 12:19:44 2022 - InstallationDate: Installed on 2021-03-20 (361 days ago) - InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) - PackageArchitecture: all - SourcePackage: ubuntustudio-default-settings - UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) - modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] + [Impact] + + * Users are unable to authenticate to and launch applications via kdesu. + * This should be backported to restore functionality that users expect. + + [Test Plan] + + * Launch Kubuntu driver manager from system setting, launching + ksystemlog from the main menu, or trying to run krusader root mode + option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming + that the current user is a member of the sudo group. + + * Confirm that the application authentcate and launch as successfully as + in previous releases. + + [Where problems could occur] + + * Examples. ** Summary changed: - kdesu fails to authenticate with sudo from Jammy. + [SRU] kdesu fails to authenticate with sudo from Jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: [SRU] kdesu fails to authenticate with sudo from Jammy Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with
[Touch-packages] [Bug 1980210] Re: [SRU] Unable download from store.kde.org with error "invalid number of concurrent streams"
In testing on hardware and VM, this fixes the issue for me. No adverse impact observed. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1980210 Title: [SRU] Unable download from store.kde.org with error "invalid number of concurrent streams" Status in qtbase-opensource-src package in Ubuntu: Triaged Status in qtbase-opensource-src source package in Jammy: Fix Committed Bug description: Version: 5.15.3+dfsg-2 Release: Jammy 22.04 In KDE systemsettings or Discover, trying to download new plasma themes or similar assets from store.kde.org results in an error dialogue stating "invalid number of concurrent streams". KDE Bug: https://bugs.kde.org/show_bug.cgi?id=455540 Fixed in KDE Qt patch collection with: https://invent.kde.org/qt/qt/qtbase/-/commit/ec68c541a72bde122a1ab5ba89f41b58c370537f Fixed in Kinetic with: https://launchpad.net/ubuntu/+source/qtbase- opensource-src/5.15.4+dfsg-3ubuntu1 Also fixed in Debian experimental as part on the planned Qt 5.15.5 transition: https://metadata.ftp- master.debian.org/changelogs//main/q/qtbase-opensource-src/qtbase- opensource-src_5.15.5+dfsg-2_changelog The update has also been shipped to our updates and backports PPA, and confirmed to be working by users. [Impact] * Users are unable to download new assets from store.kde.org. This is an important feature for users to be able to easily and safely customise their systems. [Test Plan] * Confirm that you can reproduce the bug with the unpatched Qtbase in the main archive. * Apply the update and test. * Confirm that assets now download without error. * Check a selection of other Qt based applications that access the internet to confirm as mush as is practical that there are not adverse consequences to the update. [Where problems could occur] * We are changing somewhat how Qt responds to these http requests, so some testing of other Qt based applications is desirable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1980210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980210] Re: [SRU] Unable download from store.kde.org with error "invalid number of concurrent streams"
** Changed in: qtbase-opensource-src (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1980210 Title: [SRU] Unable download from store.kde.org with error "invalid number of concurrent streams" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Jammy: Fix Released Bug description: Version: 5.15.3+dfsg-2 Release: Jammy 22.04 In KDE systemsettings or Discover, trying to download new plasma themes or similar assets from store.kde.org results in an error dialogue stating "invalid number of concurrent streams". KDE Bug: https://bugs.kde.org/show_bug.cgi?id=455540 Fixed in KDE Qt patch collection with: https://invent.kde.org/qt/qt/qtbase/-/commit/ec68c541a72bde122a1ab5ba89f41b58c370537f Fixed in Kinetic with: https://launchpad.net/ubuntu/+source/qtbase- opensource-src/5.15.4+dfsg-3ubuntu1 Also fixed in Debian experimental as part on the planned Qt 5.15.5 transition: https://metadata.ftp- master.debian.org/changelogs//main/q/qtbase-opensource-src/qtbase- opensource-src_5.15.5+dfsg-2_changelog The update has also been shipped to our updates and backports PPA, and confirmed to be working by users. [Impact] * Users are unable to download new assets from store.kde.org. This is an important feature for users to be able to easily and safely customise their systems. [Test Plan] * Confirm that you can reproduce the bug with the unpatched Qtbase in the main archive. * Apply the update and test. * Confirm that assets now download without error. * Check a selection of other Qt based applications that access the internet to confirm as mush as is practical that there are not adverse consequences to the update. [Where problems could occur] * We are changing somewhat how Qt responds to these http requests, so some testing of other Qt based applications is desirable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1980210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: [SRU] kdesu fails to authenticate with sudo from Jammy
** Description changed: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty [Impact] - * Users are unable to authenticate to and launch applications via kdesu. - * This should be backported to restore functionality that users expect. + * Users are unable to authenticate to and launch applications via kdesu. + * This should be backported to restore functionality that users expect. [Test Plan] - * Launch Kubuntu driver manager from system setting, launching + * Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. * Confirm that the application authentcate and launch as successfully as in previous releases. [Where problems could occur] - * Examples. + * While this update only returns sudo to its default behaviour (used in + previous releases and virtually all other distributions) for kdesu, care + should be taken to test some other applications that seek root + permissions to confirm that no unexpected consequences occur. ** Changed in: sudo (Ubuntu Kinetic) Status: Confirmed => Won't Fix ** Changed in: sudo (Ubuntu Jammy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: [SRU] kdesu fails to authenticate with sudo from Jammy Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Won't Fix Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Won't Fix Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty [Impact] * Users are unable to authenticate to and launch applications via kdesu. * This should be backported to restore functionality that users expect. [Test Plan] * Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. * Confirm that the application authentcate and launch
[Touch-packages] [Bug 1965439] Re: [SRU] kdesu fails to authenticate with sudo from Jammy
An upload of kdesu to fix this is currently in the Jammy unapproved queue, awaiting review by the SRU team -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: [SRU] kdesu fails to authenticate with sudo from Jammy Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Won't Fix Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Won't Fix Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty [Impact] * Users are unable to authenticate to and launch applications via kdesu. * This should be backported to restore functionality that users expect. [Test Plan] * Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. * Confirm that the application authentcate and launch as successfully as in previous releases. [Where problems could occur] * While this update only returns sudo to its default behaviour (used in previous releases and virtually all other distributions) for kdesu, care should be taken to test some other applications that seek root permissions to confirm that no unexpected consequences occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://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 1965439] Re: [SRU] kdesu fails to authenticate with sudo from Jammy
On 31/08/2022 10:38, mtu wrote: > Note that with kdesu fixed, the hotfix to kubuntu-settings by Erich > Eickmeyer can possibly be reverted, removing the ugly xterm workaround > when launching Driver Manager from Kubuntu Settings. Yes, if this update gets accepted into the main archive for jammy, that will be the next thing to do. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: [SRU] kdesu fails to authenticate with sudo from Jammy Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: Fix Committed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Won't Fix Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Won't Fix Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty [Impact] * Users are unable to authenticate to and launch applications via kdesu. * This should be backported to restore functionality that users expect. [Test Plan] * Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. * Confirm that the application authentcate and launch as successfully as in previous releases. [Where problems could occur] * While this update only returns sudo to its default behaviour (used in previous releases and virtually all other distributions) for kdesu, care should be taken to test some other applications that seek root permissions to confirm that no unexpected consequences occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: [SRU] kdesu fails to authenticate with sudo from Jammy
Note: also tested some other apps/control modules that gain root permission via other methods for certain contentions. e.g. partitionmanager, sddm (display manager) control module. These worked correctly as before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: [SRU] kdesu fails to authenticate with sudo from Jammy Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: Fix Committed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Won't Fix Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Won't Fix Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty [Impact] * Users are unable to authenticate to and launch applications via kdesu. * This should be backported to restore functionality that users expect. [Test Plan] * Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. * Confirm that the application authentcate and launch as successfully as in previous releases. [Where problems could occur] * While this update only returns sudo to its default behaviour (used in previous releases and virtually all other distributions) for kdesu, care should be taken to test some other applications that seek root permissions to confirm that no unexpected consequences occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2074059] Re: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1
** Also affects: kwin (Ubuntu) Importance: Undecided Status: New ** Changed in: kwin (Ubuntu) Status: New => Fix Committed ** Changed in: wayland (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2074059 Title: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1 Status in kwin package in Ubuntu: Fix Committed Status in wayland package in Ubuntu: In Progress Status in wayland package in Debian: Fix Released Bug description: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2074059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2074059] Re: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1
** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2074059 Title: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1 Status in kwin package in Ubuntu: Fix Committed Status in wayland package in Ubuntu: In Progress Status in wayland package in Debian: Fix Released Bug description: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2074059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2077918] [NEW] librsvg 2.58.93+dfsg-4 causes FTBFS and autopkgtes fail due to missing dependencies
Public bug reported: librsvg 2.58.93+dfsg-4 in oracular-proposed causes FTBFS due to missing dependencies. Also fails it's autopkgtest build test for the same reasons. *** Example FTBFS: https://launchpad.net/ubuntu/+source/kio- extras/4:23.08.5-0ubuntu7 -- Importing target librsvg via pkg-config (librsvg-2.0, shared) -- Checking for module 'librsvg-2.0' -- Package 'harfbuzz', required by 'librsvg-2.0', not found Package 'libxml-2.0', required by 'librsvg-2.0', not found Package 'pangocairo', required by 'librsvg-2.0', not found Package 'pangoft2', required by 'librsvg-2.0', not found CMake Error at /usr/share/cmake-3.30/Modules/FindPkgConfig.cmake:645 (message): The following required packages were not found: - librsvg-2.0 *** stdout of the failed build test autopkgtest 1..1 Package harfbuzz was not found in the pkg-config search path. Perhaps you should add the directory containing `harfbuzz.pc' to the PKG_CONFIG_PATH environment variable Package 'harfbuzz', required by 'librsvg-2.0', not found Package 'libxml-2.0', required by 'librsvg-2.0', not found Package 'pangocairo', required by 'librsvg-2.0', not found Package 'pangoft2', required by 'librsvg-2.0', not found simple.c:1:10: fatal error: glib-object.h: No such file or directory 1 | #include | ^~~ compilation terminated. *** ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New ** Affects: librsvg (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1079729 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079729 ** Also affects: librsvg (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079729 Importance: Unknown Status: Unknown ** Description changed: librsvg 2.58.93+dfsg-4 in oracular-proposed causes FTBFS due to missing dependencies. Also fails it's autopkgtest build test for the same reasons. *** Example FTBFS: https://launchpad.net/ubuntu/+source/kio- extras/4:23.08.5-0ubuntu7 -- Importing target librsvg via pkg-config (librsvg-2.0, shared) -- Checking for module 'librsvg-2.0' -- Package 'harfbuzz', required by 'librsvg-2.0', not found Package 'libxml-2.0', required by 'librsvg-2.0', not found Package 'pangocairo', required by 'librsvg-2.0', not found Package 'pangoft2', required by 'librsvg-2.0', not found CMake Error at /usr/share/cmake-3.30/Modules/FindPkgConfig.cmake:645 (message): - The following required packages were not found: + The following required packages were not found: -- librsvg-2.0 + - librsvg-2.0 *** stdout of the failed build test autopkgtest - - *** 1..1 Package harfbuzz was not found in the pkg-config search path. Perhaps you should add the directory containing `harfbuzz.pc' to the PKG_CONFIG_PATH environment variable Package 'harfbuzz', required by 'librsvg-2.0', not found Package 'libxml-2.0', required by 'librsvg-2.0', not found Package 'pangocairo', required by 'librsvg-2.0', not found Package 'pangoft2', required by 'librsvg-2.0', not found simple.c:1:10: fatal error: glib-object.h: No such file or directory - 1 | #include - | ^~~ + 1 | #include + | ^~~ compilation terminated. *** -- 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/2077918 Title: librsvg 2.58.93+dfsg-4 causes FTBFS and autopkgtes fail due to missing dependencies Status in librsvg package in Ubuntu: New Status in librsvg package in Debian: Unknown Bug description: librsvg 2.58.93+dfsg-4 in oracular-proposed causes FTBFS due to missing dependencies. Also fails it's autopkgtest build test for the same reasons. *** Example FTBFS: https://launchpad.net/ubuntu/+source/kio- extras/4:23.08.5-0ubuntu7 -- Importing target librsvg via pkg-config (librsvg-2.0, shared) -- Checking for module 'librsvg-2.0' -- Package 'harfbuzz', required by 'librsvg-2.0', not found Package 'libxml-2.0', required by 'librsvg-2.0', not found Package 'pangocairo', required by 'librsvg-2.0', not found Package 'pangoft2', required by 'librsvg-2.0', not found CMake Error at /usr/share/cmake-3.30/Modules/FindPkgConfig.cmake:645 (message): The following required packages were not found: - librsvg-2.0 *** stdout of the failed build test autopkgtest 1..1 Package harfbuzz was not found in the pkg-config search path. Perhaps you should add the directory containing `harfbuzz.pc' to the PKG_CONFIG_PATH environment variable Package 'harfbuzz', required by 'librsvg-2.0', not found Package 'libxml-2.0', required by 'librsvg-2.0', not found Package 'pangocairo', required by 'librsvg-2.0', not found Package 'pangoft2', required by 'librsvg-2.0', not found simple.c:1:10: fatal error: glib-object.h: N
[Touch-packages] [Bug 2068612] Re: Please remove wireless-tools from oracular
https://launchpad.net/ubuntu/+source/kubuntu-meta/1.457 kubuntu-meta (1.457) oracular; urgency=medium * Refreshed dependencies * Removed wireless-tools from desktop -- 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/2068612 Title: Please remove wireless-tools from oracular Status in ubuntu-meta package in Ubuntu: Confirmed Status in wireless-tools package in Ubuntu: Confirmed Bug description: Wireless Extensions support in the kernel has been deprecated[1] for a long time now. wireless-tools[2] userspace utility should be removed. iw[3] is considered as the alternate. See page[4] for comparison between wireless-tools and iw. iw supports everything except deprecated Wireless-Extensions. See page[5] for replacing iwconfig with iw. $ reverse-depends wireless-tools Reverse-Recommends == * broadcom-sta-dkms * hw-probe * laptop-mode-tools * task-laptop * whereami Reverse-Depends === * aircrack-ng [amd64 ppc64el s390x] * kubuntu-desktop [amd64 arm64 armhf ppc64el] * lubuntu-desktop [amd64 arm64 armhf ppc64el s390x] * vanilla-gnome-desktop [amd64 arm64 armhf ppc64el] Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b wireless-tools Reverse-Build-Depends = * networkd-dispatcher [1] https://wireless.wiki.kernel.org/en/developers/documentation/wireless-extensions [2] https://hewlettpackard.github.io/wireless-tools/Tools.html [3] https://wireless.wiki.kernel.org/en/users/documentation/iw [4] https://wiki.archlinux.org/title/Network_configuration/Wireless#iw_and_wireless_tools_comparison [5] https://wireless.wiki.kernel.org/en/users/documentation/iw/replace-iwconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2068612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2068612] Re: Please remove wireless-tools from oracular
** Changed in: kubuntu-meta (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2068612 Title: Please remove wireless-tools from oracular Status in kubuntu-meta package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-gnome-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in wireless-tools package in Ubuntu: Confirmed Bug description: Wireless Extensions support in the kernel has been deprecated[1] for a long time now. wireless-tools[2] userspace utility should be removed. iw[3] is considered as the alternate. See page[4] for comparison between wireless-tools and iw. iw supports everything except deprecated Wireless-Extensions. See page[5] for replacing iwconfig with iw. $ reverse-depends wireless-tools Reverse-Recommends == * broadcom-sta-dkms * hw-probe * laptop-mode-tools * task-laptop * whereami Reverse-Depends === * aircrack-ng [amd64 ppc64el s390x] * kubuntu-desktop [amd64 arm64 armhf ppc64el] * lubuntu-desktop [amd64 arm64 armhf ppc64el s390x] * vanilla-gnome-desktop [amd64 arm64 armhf ppc64el] Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b wireless-tools Reverse-Build-Depends = * networkd-dispatcher [1] https://wireless.wiki.kernel.org/en/developers/documentation/wireless-extensions [2] https://hewlettpackard.github.io/wireless-tools/Tools.html [3] https://wireless.wiki.kernel.org/en/users/documentation/iw [4] https://wiki.archlinux.org/title/Network_configuration/Wireless#iw_and_wireless_tools_comparison [5] https://wireless.wiki.kernel.org/en/users/documentation/iw/replace-iwconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2068612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2080620] [NEW] Semitransparency of Plasma panel/widgets broken using llvmpipe on x11 since 24.2.2
Public bug reported: Version: 24.2.2-1ubuntu1 Release: oracular 24.10 After upgrade to mesa 24.2.2-1ubuntu1 in oracular, semitransparency of Plasma panel/widgets broken using llvmpipe on x11. This is particularly prominent for testers trying our live ISO session (is still X11 for compatibility) in VMs such as Virtualbox/qmemu/etc with no acceleration. With the 24.10 beta coming in less than a weeks time, this is bad timing. An issue has been opened upstream by a user/developer on Mandriva with the same issue. https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840#top Screen shots can be seen there of the impact. I have commented and added screenshots from Kubuntu 24.10. ** Affects: mesa Importance: Unknown Status: Unknown ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: oracular ** Description changed: - Version: 24.2.2-1ubuntu1 + Version: 24.2.2-1ubuntu1 Release: oracular 24.10 After upgrade to mesa 24.2.2-1ubuntu1 in oracular, semitransparency of Plasma panel/widgets broken using llvmpipe on x11. This is particularly prominent for testers trying our live ISO session (is still X11 for compatibility) in VMs such as Virtualbox/qmemu/etc with no acceleration. With the 24.10 beta coming in less than a weeks time, this is bad timing. + + An issue has been opened upstream by a user/developer on Mandriva with + the same issue. + + https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840#top + + Screen shots can be seen there of the impact. I have commented and added + screenshots from Kubuntu 24.10. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11840 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840 Importance: Unknown Status: Unknown ** Tags added: oracular -- 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/2080620 Title: Semitransparency of Plasma panel/widgets broken using llvmpipe on x11 since 24.2.2 Status in Mesa: Unknown Status in mesa package in Ubuntu: New Bug description: Version: 24.2.2-1ubuntu1 Release: oracular 24.10 After upgrade to mesa 24.2.2-1ubuntu1 in oracular, semitransparency of Plasma panel/widgets broken using llvmpipe on x11. This is particularly prominent for testers trying our live ISO session (is still X11 for compatibility) in VMs such as Virtualbox/qmemu/etc with no acceleration. With the 24.10 beta coming in less than a weeks time, this is bad timing. An issue has been opened upstream by a user/developer on Mandriva with the same issue. https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840#top Screen shots can be seen there of the impact. I have commented and added screenshots from Kubuntu 24.10. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2080620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2080620] Re: Semitransparency of Plasma panel/widgets broken using llvmpipe on x11 since 24.2.2
** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/2080620 Title: Semitransparency of Plasma panel/widgets broken using llvmpipe on x11 since 24.2.2 Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Bug description: Version: 24.2.2-1ubuntu1 Release: oracular 24.10 After upgrade to mesa 24.2.2-1ubuntu1 in oracular, semitransparency of Plasma panel/widgets broken using llvmpipe on x11. This is particularly prominent for testers trying our live ISO session (is still X11 for compatibility) in VMs such as Virtualbox/qmemu/etc with no acceleration. With the 24.10 beta coming in less than a weeks time, this is bad timing. An issue has been opened upstream by a user/developer on Mandriva with the same issue. https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840#top Screen shots can be seen there of the impact. I have commented and added screenshots from Kubuntu 24.10. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2080620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2080620] Re: Semitransparency of Plasma panel/widgets broken using llvmpipe on x11 since 24.2.2
** Tags added: kubuntu ** Description changed: Version: 24.2.2-1ubuntu1 Release: oracular 24.10 After upgrade to mesa 24.2.2-1ubuntu1 in oracular, semitransparency of Plasma panel/widgets broken using llvmpipe on x11. This is particularly prominent for testers trying our live ISO session (is still X11 for compatibility) in VMs such as Virtualbox/qmemu/etc with no acceleration. With the 24.10 beta coming in less than a weeks time, this is bad timing. An issue has been opened upstream by a user/developer on Mandriva with the same issue. https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840#top Screen shots can be seen there of the impact. I have commented and added screenshots from Kubuntu 24.10. + + EDIT: Also as a result of this issue, the try/install screen on the live + ISO session is wrongly tinted orange. This occurs under the same + conditions as the transparency issue. -- 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/2080620 Title: Semitransparency of Plasma panel/widgets broken using llvmpipe on x11 since 24.2.2 Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Bug description: Version: 24.2.2-1ubuntu1 Release: oracular 24.10 After upgrade to mesa 24.2.2-1ubuntu1 in oracular, semitransparency of Plasma panel/widgets broken using llvmpipe on x11. This is particularly prominent for testers trying our live ISO session (is still X11 for compatibility) in VMs such as Virtualbox/qmemu/etc with no acceleration. With the 24.10 beta coming in less than a weeks time, this is bad timing. An issue has been opened upstream by a user/developer on Mandriva with the same issue. https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840#top Screen shots can be seen there of the impact. I have commented and added screenshots from Kubuntu 24.10. EDIT: Also as a result of this issue, the try/install screen on the live ISO session is wrongly tinted orange. This occurs under the same conditions as the transparency issue. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2080620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047023] Re: Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1
Perhaps this upload helps?
https://launchpad.net/ubuntu/+source/qtbase-opensource-
src/5.15.10+dfsg-5ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/2047023
Title:
Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1
Status in qtbase-opensource-src package in Ubuntu:
New
Bug description:
After upgrading Qt5 libraries to 5.15.10+dfsg-5build1, several Qt5
applications (including lxqt-panel and goldendict) crashed, leaving a
"*** buffer overflow detected ***: terminated" message in console.
It seems that the crashed applications all used the QSettings. The
following sample code will crash with 5.15.10+dfsg-5build1, but not
with 5.15.10+dfsg-5
#include
int main(int argc, char *argv[])
{
QSettings s("/tmp/a.ini", QSettings::IniFormat);
s.setValue("a", 123);
s.sync();
return 0;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2047023/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047023] Re: Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1 in noble-proposed
Note that 5.15.10+dfsg-5build1 is from the noble-propose pocket, which
should not normally be installed on a machine you expect to be
relatively stable.
** Summary changed:
- Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1
+ Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1 in
noble-proposed
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/2047023
Title:
Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1
in noble-proposed
Status in qtbase-opensource-src package in Ubuntu:
Confirmed
Bug description:
After upgrading Qt5 libraries to 5.15.10+dfsg-5build1, several Qt5
applications (including lxqt-panel and goldendict) crashed, leaving a
"*** buffer overflow detected ***: terminated" message in console.
It seems that the crashed applications all used the QSettings. The
following sample code will crash with 5.15.10+dfsg-5build1, but not
with 5.15.10+dfsg-5
#include
int main(int argc, char *argv[])
{
QSettings s("/tmp/a.ini", QSettings::IniFormat);
s.setValue("a", 123);
s.sync();
return 0;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2047023/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046624] Re: apparmor breaks surfshark vpn
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 ** This bug has been marked a duplicate of bug 2046844 AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046624 Title: apparmor breaks surfshark vpn Status in apparmor package in Ubuntu: New Bug description: with the new apparmor Candidate: 4.0.0~alpha2-0ubuntu7 Breaks my VPN *surfshark [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap It will work with --no-sandbox "surfshark --no-sandbox" not ideal. I removed apparmor for proof *apt policy apparmor apparmor: Installed: (none) Candidate: 4.0.0~alpha2-0ubuntu7 Version table: 4.0.0~alpha2-0ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages Now my VPN works as expected, spent 2 hrs this morning with surfshark support, they will get back to me in a day or two, but they can't find anything wrong on their end. So far it points to apparmor ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apparmor (not installed) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Dec 16 10:40:00 2023 InstallationDate: Installed on 2023-12-10 (6 days ago) InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047023] Re: Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1 in noble-proposed
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Rik Mills (rikmills)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/2047023
Title:
Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1
in noble-proposed
Status in qtbase-opensource-src package in Ubuntu:
Confirmed
Bug description:
After upgrading Qt5 libraries to 5.15.10+dfsg-5build1, several Qt5
applications (including lxqt-panel and goldendict) crashed, leaving a
"*** buffer overflow detected ***: terminated" message in console.
It seems that the crashed applications all used the QSettings. The
following sample code will crash with 5.15.10+dfsg-5build1, but not
with 5.15.10+dfsg-5
#include
int main(int argc, char *argv[])
{
QSettings s("/tmp/a.ini", QSettings::IniFormat);
s.setValue("a", 123);
s.sync();
return 0;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2047023/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: kontact (Ubuntu) Importance: Undecided Status: New ** Changed in: kontact (Ubuntu) Status: New => Confirmed ** Changed in: kontact (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in apparmor package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Confirmed Status in kontact package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: freecad (Ubuntu) Importance: Undecided Status: New ** Changed in: freecad (Ubuntu) Status: New => Confirmed ** Changed in: freecad (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in apparmor package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in kontact package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047023] Re: Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1 in noble-proposed
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/2047023
Title:
Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1
in noble-proposed
Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Bug description:
After upgrading Qt5 libraries to 5.15.10+dfsg-5build1, several Qt5
applications (including lxqt-panel and goldendict) crashed, leaving a
"*** buffer overflow detected ***: terminated" message in console.
It seems that the crashed applications all used the QSettings. The
following sample code will crash with 5.15.10+dfsg-5build1, but not
with 5.15.10+dfsg-5
#include
int main(int argc, char *argv[])
{
QSettings s("/tmp/a.ini", QSettings::IniFormat);
s.setValue("a", 123);
s.sync();
return 0;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2047023/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error
** Changed in: kaccounts-integration (Ubuntu)
Status: Fix Committed => Invalid
** Changed in: kaccounts-providers (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libaccounts-glib in
Ubuntu.
https://bugs.launchpad.net/bugs/1451728
Title:
[master] kde-config-telepathy-accounts package install error
Status in Kubuntu PPA:
Fix Released
Status in Telepathy KDE:
Fix Released
Status in kaccounts-integration package in Ubuntu:
Invalid
Status in kaccounts-providers package in Ubuntu:
Invalid
Status in ktp-accounts-kcm package in Ubuntu:
Won't Fix
Status in libaccounts-glib package in Ubuntu:
Fix Released
Status in kaccounts-providers source package in Wily:
Won't Fix
Status in ktp-accounts-kcm source package in Wily:
Won't Fix
Bug description:
Installing from Kubuntu 15.04 backports:
Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1)
over (0.9.0-0ubuntu1) ...
dpkg: error processing archive
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
(--unpack):
trying to overwrite '/usr/share/accounts/services/facebook-im.service',
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
SRU information
===
[Impact] It's not possible to install KDE and Unity in co-existence
because of several file conflicts: many files under
/usr/share/accounts/{providers,services}/ are provided by both the
package "kaccounts-providers" and packages build from the "account-
plugins" source package, for example 'account-plugin-facebook'.
[Test case] Install both kaccounts-providers and account-plugin-facebook:
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service
and /usr/share/accounts/providers/facebook.provider.
You might get other conflicts as well, but those are due to bug 1565772 (also
nominated for SRU).
[Regression potential] Minimal: the changed packages belong to the
default KDE installation, and have already landed in Yakkety. Things
appear to be working fine there: account creation is still possible
under KDE, even after changing the file paths as per this fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Erich: Actually the web browser widget or picture frame are from the kdeplasma-addons source. So not a core part of the Plasma desktop. We just seed those addons packages by default as they are good to have for users. However, you are correct that when installed and a user tries to add them to the desktop, the resulting crash does bring down the whole desktop. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in apparmor package in Ubuntu: Confirmed Status in devhelp package in Ubuntu: New Status in digikam package in Ubuntu: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in gnome-packagekit package in Ubuntu: Confirmed Status in kontact package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047780] Re: BlueZ release 5.71
> Also, why is the tarball different from the Debian one? At least for 5.71, it looks as if Ubuntu are using the tar.xz from the kernel.org download url in the debian/watch file, while debian are fetching or making a tar from the git.kernel.org (or gihub mirror) bluez repo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by kdesu
** Summary changed: - software-properties-qt can no longer launch when called by pkexec + software-properties-qt can no longer launch when called by kdesu ** Changed in: policykit-1 (Ubuntu Jammy) Status: Confirmed => Invalid ** Changed in: policykit-1 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Confirmed Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Invalid Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by kdesu
The breaking change in sudo appears to be one of those in: https://tracker.debian.org/news/1237774/accepted-sudo-196-1exp2-source- into-experimental/ -- 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/1965439 Title: software-properties-qt can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Confirmed Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Impish: Invalid Status in kubuntu-settings source package in Impish: Invalid Status in policykit-1 source package in Impish: Invalid Status in software-properties source package in Impish: Invalid Status in sudo source package in Impish: Invalid Status in ubuntustudio-default-settings source package in Impish: Invalid Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Invalid Status in software-properties source package in Jammy: Confirmed Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by kdesu
Seems to be caused by: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 Commenting out the: 'Defaults use_pty' in /etc/suduoers seems to fix things for me. Now as that was added to fix a CVE, reverting that probably isn't a easy fix -- 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/1965439 Title: software-properties-qt can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Confirmed Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Impish: Invalid Status in kubuntu-settings source package in Impish: Invalid Status in policykit-1 source package in Impish: Invalid Status in software-properties source package in Impish: Invalid Status in sudo source package in Impish: Invalid Status in ubuntustudio-default-settings source package in Impish: Invalid Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Invalid Status in software-properties source package in Jammy: Confirmed Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1953712] [NEW] 5.15.2 rebuild against libopenssl3 requires patches and dependency fixes
Public bug reported: 5.15.2+dfsg-14ubuntu2 >From IRC: [03:22:54] https://launchpad.net/ubuntu/+source/qtbase- opensource-src/5.15.2+dfsg-14ubuntu2 is defective. It still depends on libssl1.1 (debian/control:161) and doesn't have the necessary patch for the function renames applied. As discussed on IRC, in #ubuntu-release and #ubuntu-qt, debian qt uploader has patches and changes queued in salsa, so to prevent breakage of Qt and KDE things 5.15.2+dfsg-14ubuntu2 must not migrate to release pocket. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed ** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1953712 Title: 5.15.2 rebuild against libopenssl3 requires patches and dependency fixes Status in qtbase-opensource-src package in Ubuntu: New Bug description: 5.15.2+dfsg-14ubuntu2 From IRC: [03:22:54] https://launchpad.net/ubuntu/+source/qtbase- opensource-src/5.15.2+dfsg-14ubuntu2 is defective. It still depends on libssl1.1 (debian/control:161) and doesn't have the necessary patch for the function renames applied. As discussed on IRC, in #ubuntu-release and #ubuntu-qt, debian qt uploader has patches and changes queued in salsa, so to prevent breakage of Qt and KDE things 5.15.2+dfsg-14ubuntu2 must not migrate to release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1953712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1953712] Re: 5.15.2 rebuild against libopenssl3 requires patches and dependency fixes
Or preferably, remove the build from proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1953712 Title: 5.15.2 rebuild against libopenssl3 requires patches and dependency fixes Status in qtbase-opensource-src package in Ubuntu: New Bug description: 5.15.2+dfsg-14ubuntu2 From IRC: [03:22:54] https://launchpad.net/ubuntu/+source/qtbase- opensource-src/5.15.2+dfsg-14ubuntu2 is defective. It still depends on libssl1.1 (debian/control:161) and doesn't have the necessary patch for the function renames applied. As discussed on IRC, in #ubuntu-release and #ubuntu-qt, debian qt uploader has patches and changes queued in salsa, so to prevent breakage of Qt and KDE things 5.15.2+dfsg-14ubuntu2 must not migrate to release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1953712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1953712] Re: 5.15.2 rebuild against libopenssl3 requires patches and dependency fixes
** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1953712 Title: 5.15.2 rebuild against libopenssl3 requires patches and dependency fixes Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: 5.15.2+dfsg-14ubuntu2 From IRC: [03:22:54] https://launchpad.net/ubuntu/+source/qtbase- opensource-src/5.15.2+dfsg-14ubuntu2 is defective. It still depends on libssl1.1 (debian/control:161) and doesn't have the necessary patch for the function renames applied. As discussed on IRC, in #ubuntu-release and #ubuntu-qt, debian qt uploader has patches and changes queued in salsa, so to prevent breakage of Qt and KDE things 5.15.2+dfsg-14ubuntu2 must not migrate to release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1953712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959325] Re: New binutils causes build failures for many RISC-V packages
Looks like this will cause most KDE things to FTBFS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1959325 Title: New binutils causes build failures for many RISC-V packages Status in binutils package in Ubuntu: Confirmed Bug description: binutils 2.37.90.20220126-0ubuntu1 changes the -march flags. We see a lot of packages not building in proposed anymore: OpenSBI, ktexteditor, ... Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959325] Re: New binutils causes build failures for many RISC-V packages
** Changed in: binutils (Ubuntu) Importance: Undecided => Critical ** Also affects: binutils (Ubuntu Jammy) Importance: Critical Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1959325 Title: New binutils causes build failures for many RISC-V packages Status in binutils package in Ubuntu: Confirmed Status in binutils source package in Jammy: Confirmed Bug description: binutils 2.37.90.20220126-0ubuntu1 changes the -march flags. We see a lot of packages not building in proposed anymore: OpenSBI, ktexteditor, ... Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959325] Re: New binutils causes build failures for many RISC-V packages
KDE (and other) things now seem to be building ok with the latest 2.37.90.20220130-0ubuntu2 Thank you doko (Matthias) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1959325 Title: New binutils causes build failures for many RISC-V packages Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Jammy: Fix Released Bug description: binutils 2.37.90.20220126-0ubuntu1 changes the -march flags. We see a lot of packages not building in proposed anymore: OpenSBI, ktexteditor, ... Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960220] Re: kubuntu's desktop seed should depend on xdg-desktop-portal-gtk for better desktop snaps integration
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) => Rik Mills (rikmills)
** Changed in: ubuntu-meta (Ubuntu)
Status: Confirmed => In Progress
** Also affects: kubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kubuntu-meta (Ubuntu)
Status: New => Invalid
** Changed in: kubuntu-meta (Ubuntu)
Status: Invalid => In Progress
** Changed in: ubuntu-meta (Ubuntu)
Status: In Progress => Invalid
** Also affects: ubuntu-meta (Ubuntu Jammy)
Importance: Medium
Assignee: Rik Mills (rikmills)
Status: Invalid
** Also affects: kubuntu-meta (Ubuntu Jammy)
Importance: Undecided
Status: In Progress
** Changed in: kubuntu-meta (Ubuntu Jammy)
Assignee: (unassigned) => Rik Mills (rikmills)
** Changed in: ubuntu-meta (Ubuntu Jammy)
Assignee: Rik Mills (rikmills) => (unassigned)
** Changed in: kubuntu-meta (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: kubuntu-meta (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/1960220
Title:
kubuntu's desktop seed should depend on xdg-desktop-portal-gtk for
better desktop snaps integration
Status in kubuntu-meta package in Ubuntu:
Fix Committed
Status in ubuntu-meta package in Ubuntu:
Invalid
Status in kubuntu-meta source package in Jammy:
Fix Committed
Status in ubuntu-meta source package in Jammy:
Invalid
Bug description:
See https://bugzilla.mozilla.org/show_bug.cgi?id=1753732 (especially
comment #8) for some context.
A number of desktop snaps are GTK apps, and without xdg-desktop-
portal-gtk installed on the host system the theming integration is
poor.
ubuntu's desktop-minimal seed has this line:
* (xdg-desktop-portal-gtk) # Useful for desktop snaps
I suggest kubuntu's desktop seed should consider installing it by
default too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1960220/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962389] [NEW] Sync upower 0.99.16-2 (main) from Debian unstable (main)
Public bug reported: Please sync upower 0.99.16-2 (main) from Debian unstable (main) Changelog entries since current jammy version 0.99.16-1: upower (0.99.16-2) unstable; urgency=medium * Cherry-pick FD handling fixes from upstream (Closes: #1006368) -- Michael Biebl Sat, 26 Feb 2022 10:43:19 +0100 As per https://gitlab.freedesktop.org/upower/upower/-/issues/174 this should fix KDE not registering and acting on laptop lid closure. ** Affects: upower (Ubuntu) Importance: High Status: New ** Changed in: upower (Ubuntu) Importance: Undecided => Wishlist ** Changed in: upower (Ubuntu) Importance: Wishlist => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962389 Title: Sync upower 0.99.16-2 (main) from Debian unstable (main) Status in upower package in Ubuntu: New Bug description: Please sync upower 0.99.16-2 (main) from Debian unstable (main) Changelog entries since current jammy version 0.99.16-1: upower (0.99.16-2) unstable; urgency=medium * Cherry-pick FD handling fixes from upstream (Closes: #1006368) -- Michael Biebl Sat, 26 Feb 2022 10:43:19 +0100 As per https://gitlab.freedesktop.org/upower/upower/-/issues/174 this should fix KDE not registering and acting on laptop lid closure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1962389/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952977] Re: Invalid security certificates everywhere in KDE
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1952977
Title:
Invalid security certificates everywhere in KDE
Status in qtbase-opensource-src package in Ubuntu:
Triaged
Bug description:
Upgrading 5.15.2+dfsg-13 to 5.15.2+dfsg-14 results in security cert.
errors like this https://imgur.com/a/7Kyt8U6
This causes problems for discover, downloading widgets, using the
weather widget, using the kde browser integrations, downloading tabs
for ksysguard, etc.
you can get console errors like this
org.kde.plasma.discover: Trying to open unexisting file
QUrl("file:///home/chad/%25F")
adding empty sources model QStandardItemModel(0x5646c6ed2e80)
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend"
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id qt.network.ssl:
QSslSocket: cannot resolve SSL_get_peer_certificate
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libqt5network5 5.15.2+dfsg-14
Uname: Linux 5.15.5-051505-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Dec 1 21:43:08 2021
InstallationDate: Installed on 2021-11-26 (5 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20211126)
SourcePackage: qtbase-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1952977/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952977] Re: Invalid security certificates everywhere in KDE
What is hopefully a temporary fix is now building in:
ppa:ci-train-ppa-service/4730
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1952977
Title:
Invalid security certificates everywhere in KDE
Status in qtbase-opensource-src package in Ubuntu:
Triaged
Bug description:
Upgrading 5.15.2+dfsg-13 to 5.15.2+dfsg-14 results in security cert.
errors like this https://imgur.com/a/7Kyt8U6
This causes problems for discover, downloading widgets, using the
weather widget, using the kde browser integrations, downloading tabs
for ksysguard, etc.
you can get console errors like this
org.kde.plasma.discover: Trying to open unexisting file
QUrl("file:///home/chad/%25F")
adding empty sources model QStandardItemModel(0x5646c6ed2e80)
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend"
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id qt.network.ssl:
QSslSocket: cannot resolve SSL_get_peer_certificate
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libqt5network5 5.15.2+dfsg-14
Uname: Linux 5.15.5-051505-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Dec 1 21:43:08 2021
InstallationDate: Installed on 2021-11-26 (5 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20211126)
SourcePackage: qtbase-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1952977/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952977] Re: Invalid security certificates everywhere in KDE
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1952977
Title:
Invalid security certificates everywhere in KDE
Status in qtbase-opensource-src package in Ubuntu:
Fix Committed
Bug description:
Upgrading 5.15.2+dfsg-13 to 5.15.2+dfsg-14 results in security cert.
errors like this https://imgur.com/a/7Kyt8U6
This causes problems for discover, downloading widgets, using the
weather widget, using the kde browser integrations, downloading tabs
for ksysguard, etc.
you can get console errors like this
org.kde.plasma.discover: Trying to open unexisting file
QUrl("file:///home/chad/%25F")
adding empty sources model QStandardItemModel(0x5646c6ed2e80)
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend"
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id qt.network.ssl:
QSslSocket: cannot resolve SSL_get_peer_certificate
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libqt5network5 5.15.2+dfsg-14
Uname: Linux 5.15.5-051505-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Dec 1 21:43:08 2021
InstallationDate: Installed on 2021-11-26 (5 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20211126)
SourcePackage: qtbase-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1952977/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757747] Re: Please port your package away from Qt 4
** Changed in: lightdm (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1757747 Title: Please port your package away from Qt 4 Status in lightdm package in Ubuntu: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1757747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757884] Re: Please port your package away from Qt 4
** Changed in: syncevolution (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1757884 Title: Please port your package away from Qt 4 Status in syncevolution package in Ubuntu: Fix Released Status in syncevolution package in Debian: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syncevolution/+bug/1757884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757625] Re: Please port your package away from Qt 4
** Changed in: dee-qt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dee-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757625 Title: Please port your package away from Qt 4 Status in dee-qt package in Ubuntu: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dee-qt/+bug/1757625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993800] Re: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2>
https://launchpadlibrarian.net/632541247/buildlog_ubuntu-lunar- armhf.qtquickcontrols-opensource-src_5.15.6-2_BUILDING.txt.gz LLVM ERROR: Cannot select: 0x2c26c78: v4i32 = ARMISD::VCMPZ 0x2c79870, Constant:i32<2> 0x2c79870: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.326)> 0x2c3a588, 0x2c2d4d8, Constant:i32<4> 0x2c2d4d8: i32 = add 0x2c615c0, Constant:i32<64> 0x2c615c0: i32,ch = CopyFromReg 0x27bc73c, Register:i32 %35 0x2c2e590: i32 = Register %35 0x2c48da8: i32 = Constant<64> 0x2c639c0: i32 = Constant<4> 0x2c63b70: i32 = Constant<2> In function: fs_variant_partial Aborted (core dumped) similar with qtdatavis3d-everywhere-src and qtdeclarative-opensource-src -- 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/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: Fix Released Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in openSUSE: Unknown Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993800] Re: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2>
Also: https://launchpad.net/ubuntu/+source/qtlocation-opensource- src/5.15.6+dfsg-2 Bumped to High, as causing multiple FTBFS in Lunar ** Changed in: llvm-toolchain-15 (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: Fix Released Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in openSUSE: Unknown Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error
** Changed in: kaccounts-providers (Ubuntu Wily)
Status: Triaged => Won't Fix
** Changed in: ktp-accounts-kcm (Ubuntu Wily)
Status: Triaged => Won't Fix
** Changed in: ktp-accounts-kcm (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libaccounts-glib in
Ubuntu.
https://bugs.launchpad.net/bugs/1451728
Title:
[master] kde-config-telepathy-accounts package install error
Status in Kubuntu PPA:
Fix Released
Status in Telepathy KDE:
Fix Released
Status in kaccounts-integration package in Ubuntu:
Fix Committed
Status in kaccounts-providers package in Ubuntu:
Fix Committed
Status in ktp-accounts-kcm package in Ubuntu:
Won't Fix
Status in libaccounts-glib package in Ubuntu:
Fix Released
Status in kaccounts-providers source package in Wily:
Won't Fix
Status in ktp-accounts-kcm source package in Wily:
Won't Fix
Bug description:
Installing from Kubuntu 15.04 backports:
Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1)
over (0.9.0-0ubuntu1) ...
dpkg: error processing archive
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
(--unpack):
trying to overwrite '/usr/share/accounts/services/facebook-im.service',
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
SRU information
===
[Impact] It's not possible to install KDE and Unity in co-existence
because of several file conflicts: many files under
/usr/share/accounts/{providers,services}/ are provided by both the
package "kaccounts-providers" and packages build from the "account-
plugins" source package, for example 'account-plugin-facebook'.
[Test case] Install both kaccounts-providers and account-plugin-facebook:
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service
and /usr/share/accounts/providers/facebook.provider.
You might get other conflicts as well, but those are due to bug 1565772 (also
nominated for SRU).
[Regression potential] Minimal: the changed packages belong to the
default KDE installation, and have already landed in Yakkety. Things
appear to be working fine there: account creation is still possible
under KDE, even after changing the file paths as per this fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727811] Re: signon-ui crashes when trying to use KDE systemsettings to add a google account
** Changed in: signon-ui (Ubuntu Artful) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1727811 Title: signon-ui crashes when trying to use KDE systemsettings to add a google account Status in signon-ui package in Ubuntu: Fix Released Status in signon-ui source package in Artful: Won't Fix Status in signon-ui source package in Bionic: Fix Released Bug description: 0.17+17.10.20170606-0ubuntu1 in Artful & Bionic crash when trying to use KDE systemsettings to add a google account "There was an error while trying to process the request: userActionFinished error: 2" This results in no Google account be added. This appears to be the result of changes implemented for Unity. A WIP solution is discussed in the reported issue upstream: https://gitlab.com/accounts-sso/signon-ui/issues/1 However, that solution requires KDE upstream to adapt it's Kaccounts KCM. As KDE is now the only user of signon-ui (Unity dropping it's use) in Artful and abovea temporary solution is to revert to the last working version 0.17+17.04.20161109-0ubuntu1 This has been built here: https://launchpad.net/~rikmills/+archive/ubuntu/kio-grive and tested successfully, allowing the the addition of Google accounts, and the use of kio-gdrive to access google drive from Dolphin file manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1727811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377497] Re: Unable to unlock guest seesion in Kubuntu 14.04
** Changed in: lightdm (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1377497 Title: Unable to unlock guest seesion in Kubuntu 14.04 Status in lightdm package in Ubuntu: Won't Fix Bug description: OS: Kubuntu 14.04 Desktop: KDE Applidation: KDE Screen Lock (sorry, don't know the exact package name) Symptom: After being left alone, Kubutnu will lock the guest user's session. It is then not possible to resume (blank passwords or obvious possibles like "password", "guest" are no accepted) and the computer needs to be rebooted to gain access (losing any files and data that the guest might have in-use). Expected behaviour: Either the screen does not lock, or the guest account is informed of the password to use during log-in I have read bug 1059625 but that appears to applyt to Gnome (or possibly Unity) whereas this affects Kubuntu/KDE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1377497/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059928] Re: Lightdm [Kubuntu) not displaying user thumbnail photos
** Changed in: accountsservice (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: lightdm (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1059928 Title: Lightdm [Kubuntu) not displaying user thumbnail photos Status in accountsservice package in Ubuntu: Won't Fix Status in lightdm package in Ubuntu: Won't Fix Bug description: On the Kubuntu login screen (I'm assuming lightdm?), there are just generic pictures for users. I expected it to display my photo along with my user name, as I configured in System Settings -> Account Details -> Change your image. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 1 21:53:35 2012 EcryptfsInUse: Yes InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120928) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1059928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1997004] [NEW] autopkgtests fail with gpgme1.0 1.18.0-2ubuntu1 from lunar proposed
Public bug reported: Release: Lunar Version: 0.10.0-1 Failure due to the upstream gpgme-config script not being shipped by debian with gpgme1.0 1.18.0-2 Related bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023601 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348 [gpgme-sys 0.10.0] running: "sh" "-c" "gpgme-config --version" [gpgme-sys 0.10.0] sh: 1: gpgme-config: not found [gpgme-sys 0.10.0] command did not execute successfully, got: exit status: 127 [gpgme-sys 0.10.0] Error: () error: failed to run custom build command for `gpgme-sys v0.10.0 (/usr/share/cargo/registry/gpgme-sys-0.10.0)` Caused by: process didn't exit successfully: `/tmp/tmp.DkCl1cHFak/target/debug/build/gpgme-sys-cf9d18ac09e05ddc/build-script-build` (exit status: 1) --- stdout cargo:rerun-if-env-changed=GPGME_PREFIX cargo:rerun-if-env-changed=GPGME_INCLUDE cargo:rerun-if-env-changed=GPGME_LIB_DIR cargo:rerun-if-env-changed=GPGME_LIBS cargo:rerun-if-env-changed=GPGME_CONFIG --- stderr running: "sh" "-c" "gpgme-config --version" sh: 1: gpgme-config: not found command did not execute successfully, got: exit status: 127 Error: () ** Affects: gpgme1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: rust-gpgme-sys (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: gpgme1.0 (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse ** Description changed: Release: Lunar - Version: 0.10.0-2 + Version: 0.10.0-1 Failure due to the upstream gpgme-config script not being shipped by debian with gpgme1.0 1.18.0-2 Related bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023601 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348 - [gpgme-sys 0.10.0] running: "sh" "-c" "gpgme-config --version" [gpgme-sys 0.10.0] sh: 1: gpgme-config: not found [gpgme-sys 0.10.0] command did not execute successfully, got: exit status: 127 [gpgme-sys 0.10.0] Error: () error: failed to run custom build command for `gpgme-sys v0.10.0 (/usr/share/cargo/registry/gpgme-sys-0.10.0)` Caused by: - process didn't exit successfully: `/tmp/tmp.DkCl1cHFak/target/debug/build/gpgme-sys-cf9d18ac09e05ddc/build-script-build` (exit status: 1) - --- stdout - cargo:rerun-if-env-changed=GPGME_PREFIX - cargo:rerun-if-env-changed=GPGME_INCLUDE - cargo:rerun-if-env-changed=GPGME_LIB_DIR - cargo:rerun-if-env-changed=GPGME_LIBS - cargo:rerun-if-env-changed=GPGME_CONFIG + process didn't exit successfully: `/tmp/tmp.DkCl1cHFak/target/debug/build/gpgme-sys-cf9d18ac09e05ddc/build-script-build` (exit status: 1) + --- stdout + cargo:rerun-if-env-changed=GPGME_PREFIX + cargo:rerun-if-env-changed=GPGME_INCLUDE + cargo:rerun-if-env-changed=GPGME_LIB_DIR + cargo:rerun-if-env-changed=GPGME_LIBS + cargo:rerun-if-env-changed=GPGME_CONFIG - --- stderr - running: "sh" "-c" "gpgme-config --version" - sh: 1: gpgme-config: not found - command did not execute successfully, got: exit status: 127 - Error: () + --- stderr + running: "sh" "-c" "gpgme-config --version" + sh: 1: gpgme-config: not found + command did not execute successfully, got: exit status: 127 + Error: () -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1997004 Title: autopkgtests fail with gpgme1.0 1.18.0-2ubuntu1 from lunar proposed Status in gpgme1.0 package in Ubuntu: New Status in rust-gpgme-sys package in Ubuntu: New Bug description: Release: Lunar Version: 0.10.0-1 Failure due to the upstream gpgme-config script not being shipped by debian with gpgme1.0 1.18.0-2 Related bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023601 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348 [gpgme-sys 0.10.0] running: "sh" "-c" "gpgme-config --version" [gpgme-sys 0.10.0] sh: 1: gpgme-config: not found [gpgme-sys 0.10.0] command did not execute successfully, got: exit status: 127 [gpgme-sys 0.10.0] Error: () error: failed to run custom build command for `gpgme-sys v0.10.0 (/usr/share/cargo/registry/gpgme-sys-0.10.0)` Caused by: process didn't exit successfully: `/tmp/tmp.DkCl1cHFak/target/debug/build/gpgme-sys-cf9d18ac09e05ddc/build-script-build` (exit status: 1) --- stdout cargo:rerun-if-env-changed=GPGME_PREFIX cargo:rerun-if-env-changed=GPGME_INCLUDE cargo:rerun-if-env-changed=GPGME_LIB_DIR cargo:rerun-if-env-changed=GPGME_LIBS cargo:rerun-if-env-changed=GPGME_CONFIG --- stderr running: "sh" "-c" "gpgme-config --version" sh: 1: gpgme-config: not found command did not execute successfully, got: exit status: 127 Error: () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1997004/+subscriptions -- Mailing list: https://launchp
[Touch-packages] [Bug 1997004] Re: autopkgtests fail with gpgme1.0 1.18.0-2ubuntu1 from lunar proposed
Turns of that rust-gpgme-sys 0.10.0-2 in proposed has a fix, but was FTBFS when synced. On poking the builds again, they built. Tests now pass when the trigger for 0.10.0-2 is added. https://autopkgtest.ubuntu.com/packages/r/rust-gpgme-sys/lunar/amd64 ** Changed in: gpgme1.0 (Ubuntu) Status: New => Invalid ** Changed in: rust-gpgme-sys (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1997004 Title: autopkgtests fail with gpgme1.0 1.18.0-2ubuntu1 from lunar proposed Status in gpgme1.0 package in Ubuntu: Invalid Status in rust-gpgme-sys package in Ubuntu: Fix Committed Bug description: Release: Lunar Version: 0.10.0-1 Failure due to the upstream gpgme-config script not being shipped by debian with gpgme1.0 1.18.0-2 Related bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023601 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348 [gpgme-sys 0.10.0] running: "sh" "-c" "gpgme-config --version" [gpgme-sys 0.10.0] sh: 1: gpgme-config: not found [gpgme-sys 0.10.0] command did not execute successfully, got: exit status: 127 [gpgme-sys 0.10.0] Error: () error: failed to run custom build command for `gpgme-sys v0.10.0 (/usr/share/cargo/registry/gpgme-sys-0.10.0)` Caused by: process didn't exit successfully: `/tmp/tmp.DkCl1cHFak/target/debug/build/gpgme-sys-cf9d18ac09e05ddc/build-script-build` (exit status: 1) --- stdout cargo:rerun-if-env-changed=GPGME_PREFIX cargo:rerun-if-env-changed=GPGME_INCLUDE cargo:rerun-if-env-changed=GPGME_LIB_DIR cargo:rerun-if-env-changed=GPGME_LIBS cargo:rerun-if-env-changed=GPGME_CONFIG --- stderr running: "sh" "-c" "gpgme-config --version" sh: 1: gpgme-config: not found command did not execute successfully, got: exit status: 127 Error: () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1997004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1997338] Re: libdbus-1-3 uninstallable on autopkgtest
> This seems to be affecting a lot more stuff than just libatk- bridge2.0-0 and more architectures than just i386. Seems that the base testbed (see 'testbed-packages' from artefacts.tar.gz) on many runs includes packages from proposed. e.g. the dbus 1.14.0-2ubuntu3 and curl 7.86.0-2 proposed versions. A test then say wanting to install test deps of dbus-x11 1.14.0-2ubuntu2 depending on the other dbus 1.14.0-2ubuntu2 packages from the release pocket is going to fail to satisfy deps, as seems to be happening. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1997338 Title: libdbus-1-3 uninstallable on autopkgtest Status in dbus package in Ubuntu: Confirmed Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/v/vlc/20221121_104906_b4207@/log.gz Starting pkgProblemResolver with broken count: 9 Starting 2 pkgProblemResolver with broken count: 9 Investigating (0) libvlccore9:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken libvlccore9:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32 Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32 Investigating (0) libqt5dbus5:i386 < none -> 5.15.6+dfsg-1 @un puN Ib > Broken libqt5dbus5:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4 Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4 Investigating (0) libpulse0:i386 < none -> 1:16.1+dfsg1-1ubuntu3 @un puN Ib > Broken libpulse0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4 Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4 Investigating (0) libavahi-client3:i386 < none -> 0.8-6ubuntu1 @un puN Ib > Broken libavahi-client3:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2 Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2 Investigating (0) libatspi2.0-0:i386 < none -> 2.46.0-3 @un puN Ib > Broken libatspi2.0-0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0 Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0 Investigating (0) vlc-plugin-base:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken vlc-plugin-base:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0 Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0 Investigating (0) libfluidsynth3:i386 < none -> 2.2.8-1 @un puN Ib > Broken libfluidsynth3:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0 Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0 Investigating (0) libatk-bridge2.0-0:i386 < none -> 2.46.0-3 @un puN Ib > Broken libatk-bridge2.0-0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0 Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0 Investigating (0) libdebuginfod1:i386 < none -> 0.187-4 @un puN Ib > Broken libdebuginfod1:i386 Depends on libcurl3-gnutls:i386 < none | 7.85.0-1 @un uH > (>= 7.28.0) Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0 Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libatk-bridge2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libatspi2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libavahi-client3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libdebuginfod1:i386 : Depends: libcurl3-gnutls:i386 (>= 7.28.0) but it is not going to be installed libfluidsynth3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libpulse0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libqt5dbus5:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be
[Touch-packages] [Bug 1997533] [NEW] flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep
Public bug reported: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep which is not built in Ubuntu for i386 https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410 Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as B-D" This prevents migration of flac (if/once tests succeed), and will block migration of packages that now build in proposed and depend on the bumped libs in flac 1.4 (libflac++10 and libflac12) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#flac e.g.amongst several others so far https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#kwave ** Affects: flac (Ubuntu) Importance: Undecided Status: New ** Tags: lunar ** Description changed: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep which is not built in Ubuntu for i386 https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410 Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as B-D" This prevents migration of flac (if/once tests succeed), and will block migration of packages that now build in proposed and depend on the bumped libs in flac 1.4 (libflac++10 and libflac12) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#flac + + e.g.amongst several others so far + + https://people.canonical.com/~ubuntu-archive/proposed- + migration/update_excuses.html#kwave ** Tags added: lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flac in Ubuntu. https://bugs.launchpad.net/bugs/1997533 Title: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep Status in flac package in Ubuntu: New Bug description: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep which is not built in Ubuntu for i386 https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410 Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as B-D" This prevents migration of flac (if/once tests succeed), and will block migration of packages that now build in proposed and depend on the bumped libs in flac 1.4 (libflac++10 and libflac12) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#flac e.g.amongst several others so far https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#kwave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1997533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1997533] Re: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep
** Changed in: flac (Ubuntu) Status: New => Confirmed ** Changed in: flac (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flac in Ubuntu. https://bugs.launchpad.net/bugs/1997533 Title: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep Status in flac package in Ubuntu: Confirmed Bug description: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep which is not built in Ubuntu for i386 https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410 Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as B-D" This prevents migration of flac (if/once tests succeed), and will block migration of packages that now build in proposed and depend on the bumped libs in flac 1.4 (libflac++10 and libflac12) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#flac e.g.amongst several others so far https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#kwave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1997533/+subscriptions -- Mailing list: https://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 1997533] Re: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep
On 24/11/2022 08:36, Sebastien Bacher wrote: > It's not likely that we can build pandoc on i386, it would require > starting building the haskell stack there, someone probably needs to > patch flac to not build with pandoc on i386 In that case as possible solution would be: https://launchpad.net/~rikmills/+archive/ubuntu/bug1997533/+sourcepub/14167146/+listing-archive-extra Sorry for no debdiff, but that does not preserve making the install file executable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flac in Ubuntu. https://bugs.launchpad.net/bugs/1997533 Title: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep Status in flac package in Ubuntu: Confirmed Bug description: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep which is not built in Ubuntu for i386 https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410 Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as B-D" This prevents migration of flac (if/once tests succeed), and will block migration of packages that now build in proposed and depend on the bumped libs in flac 1.4 (libflac++10 and libflac12) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#flac e.g.amongst several others so far https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#kwave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1997533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1997533] Re: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flac in Ubuntu. https://bugs.launchpad.net/bugs/1997533 Title: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep Status in flac package in Ubuntu: Confirmed Bug description: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep which is not built in Ubuntu for i386 https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410 Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as B-D" This prevents migration of flac (if/once tests succeed), and will block migration of packages that now build in proposed and depend on the bumped libs in flac 1.4 (libflac++10 and libflac12) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#flac e.g.amongst several others so far https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#kwave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1997533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1997533] Re: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep
** Changed in: flac (Ubuntu) Assignee: (unassigned) => Rik Mills (rikmills) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flac in Ubuntu. https://bugs.launchpad.net/bugs/1997533 Title: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep Status in flac package in Ubuntu: Fix Committed Bug description: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep which is not built in Ubuntu for i386 https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410 Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as B-D" This prevents migration of flac (if/once tests succeed), and will block migration of packages that now build in proposed and depend on the bumped libs in flac 1.4 (libflac++10 and libflac12) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#flac e.g.amongst several others so far https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#kwave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1997533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
Also caused FTBFS in ukui-control-center
https://launchpadlibrarian.net/524640709/buildlog_ubuntu-hirsute-amd64
.ukui-control-center_3.0.2-2_BUILDING.txt.gz
** Also affects: ukui-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1916705
Title:
glib2.0 >=2.67.3 breaks include from an extern C context
Status in glib2.0 package in Ubuntu:
New
Status in qemu package in Ubuntu:
Triaged
Status in ukui-control-center package in Ubuntu:
New
Bug description:
qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz
Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages
Error:
../../disas/arm-a64.cc
In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
from
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
from /usr/include/glib-2.0/glib/gtypes.h:32,
from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
from ../../disas/arm-a64.cc:21:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
56 | template
| ^~~~
../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
20 | extern "C" {
| ^~
Also in disas/nanomips.cpp, ...
And indeed disas/arm-a64.cc has:
20 extern "C" {
21 #include "qemu/osdep.h"
22 #include "disas/dis-asm.h"
23 }
Through the chain of headers as reported above this gets to the templates
in /usr/include/c++/10/type_traits which fails due to that.
So C++ constructs within a C scope which is this bug.
Upstream qemu has not recently changed yet for this.
The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
Include osdep.h first" by Peter Maydell.
But what was different before to break it now?
To find that I was comparing Hirsute vs Hirsute-proposed ...
It is indeed failing in -proposed but working in hirsute-release.
10.2.1-20ubuntu1 : bad
repro in broken build:
$ cd /root/qemu-5.2+dfsg/b/qemu
$ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp
With that I have a test env...
Doko asked me to test
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
It must be something else.
The difference were ~340 packages I was upgrading them to spot what broke it.
I eventually found glib 2.66 -> 2.67 to break it.
libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1]
libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
Old:
/*
* We can
[Touch-packages] [Bug 1920665] Re: Ubiquity crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Some diagnosis as follows: - Loaded a previous snapshot of a Kubuntu 21.04 VM from before 16th March 2021. - Installed ubiquity. - Tested whether ubiquity launches. - Ubiquity launches. - Then looked at what was upgradable in the release pocket. - Sequentially upgraded likely culprits, rebooted, and tried to launch ubiquity after each small update. Result: Found that upgrading Mesa packages from 20.3.4-1 to 21.0.0-1 is all that is required to trigger the crash. Upgraded the following packages: libegl-mesa0 (20.3.4-1) to 21.0.0-1 libgbm1 (20.3.4-1) to 21.0.0-1 libgl1-mesa-dri (20.3.4-1) to 21.0.0-1 libglapi-mesa (20.3.4-1) to 21.0.0-1 libglx-mesa0 (20.3.4-1) to 21.0.0-1 libxatracker2 (20.3.4-1) to 21.0.0-1 mesa-va-drivers (20.3.4-1) to 21.0.0-1 mesa-vdpau-drivers (20.3.4-1) to 21.0.0-1 mesa-vulkan-drivers (20.3.4-1) to 21.0.0-1 ** Also affects: ubiquity (Ubuntu Hirsute) Importance: Critical Status: New ** Also 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/1920665 Title: Ubiquity crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Summary changed: - Ubiquity crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" + Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Testing a no change rebuild of ubiquity 21.04.11 in a PPA, it seems this is all that is required to remedy the crash with the latest ISO build. https://launchpad.net/~rikmills/+archive/ubuntu/hirsute/+sourcepub/12212560 /+listing-archive-extra -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
No crash with today's ISO 20210322 on real hardware (intel graphics laptop) However, in a Virtualbox VM the crash persists. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Description changed: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. + + Try/Install crash: + + Screen fails to start, or starts then crashes on any user action. The + user is presented with: + + "Installation failed - The installer encountered an unrecoverable error. + A desktop session will now be run so that you may investigate the problem or try installing again" + + Live session crash: + + The installer does not start from the desktop icon. Starting ubiquity + from the terminal results in an "Aborted (core dumped)" message and + nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I would also note that on real hardware here, the crash can be reproduced by booting in safe graphics mode. This is what Bob H said he was doing in his other duplicate bug. Booting in full mode on my hardware is still no crash. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
A no change rebuild of ubiquity no longer seems to fix the issue with the latest ISO -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
In reverse of my previous installation bisect, I can confirm that force downgrading mesa to the previous major release results in these crashes going away. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Changed in: mesa (Ubuntu Hirsute) Importance: Undecided => Critical -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Description changed: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. + Cases where the crash can be triggered: + + - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE + - Start the ISO on real hardware in 'safe graphics mode' + + Cases where the crash is not encountered: + - Start the ISO on real intel (HD graphics) hardware with full acceleration. + + NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to + the previous 20.3.4 in hirsute. + Try/Install crash: - Screen fails to start, or starts then crashes on any user action. The + Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 1
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
Tested in focal. Before test with proposed keyring packages: 'apt update' failed with the aforementioned error. dbgsym packages could not be installed from ddebs.ubuntu.com After upgrading to proposed keyring packages: 'apt update' succeeded. A sampling of dbgsym packages could be installed from ddebs.ubuntu.com ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Committed Status in ubuntu-keyring source package in Focal: Fix Committed Status in ubuntu-keyring source package in Groovy: Fix Committed Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
On 31/03/2021 14:21, Timo Aaltonen wrote: > Can ubiquity be run manually? Or there would need to be another > reproducer for this, otherwise bisecting mesa would be impossible. Ubiquity can be run from the command line in a terminal to reproduce. You also do not have to do it from a ISO live session, but can install 'ubiquity' and 'ubiquity-frontend-kde' on a installed hirsute VM. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Tags added: rls-hh-incoming -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
To test the slight possibility that builds with the current toolchain might be at fault, I rebuilt mesa 20.03.4 against current release+proposed pockets and downgraded mesa to the result. Ubiquity/greeter does not crash with that combination. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Description changed: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. + The crash is most commonly "malloc(): unaligned tcache chunk detected", + but inevitably from this sort of memory issue can be something like + "realloc(): invalid next size" + An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) Source
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Changed in: mesa (Ubuntu Hirsute) Status: Opinion => Confirmed -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
@Bob Your crash log confirms it is the same issue. It crashes the installer at the try/install stage (what you are reporting, and what results in the message you see) AND when the installer is manually launched from a live session. At the moment all anyone can do is wait for the result of the mesa uploaders git bisect, to find the commit/cause in the new mesa that landed in the release pocket @ around the 17th of March. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.ne
Re: [Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
On 06/04/2021 17:35, Timo Aaltonen wrote: > I've tried to bisect mesa to see where it regressed, but turns out that > an older git snapshot (~20.3.0) crashes just like with 21.0, so looks > like this is caused by something else like the toolchain instead? The rebuild of 20.3.4 here does not crash in my tests. https://launchpad.net/~rikmills/+archive/ubuntu/mesa Not the version is bumped to make upgrading on a system easier, but it is a rebuild of 20.3.4 against the same toolchain crashy 21.0.x were done with. Please try those -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: h
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Changed in: mesa (Ubuntu Hirsute) Status: Confirmed => Fix Committed -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Committed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
The ISO file integrity check was recently changed so it now runs in the background. It does not show while booting or delay boot. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Released Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Changed in: ubiquity (Ubuntu Hirsute) Status: Incomplete => Invalid -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Invalid Status in mesa source package in Hirsute: Fix Released Status in ubiquity source package in Hirsute: Invalid Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901609] Re: signond causes qprocess crash
I have tested with the patch applied in this upload to hirsute: https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu3 That fixes the crash for me. ** Changed in: signon (Ubuntu Hirsute) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Committed Status in signon source package in Focal: Confirmed Status in signon source package in Groovy: Confirmed Status in signon source package in Hirsute: Fix Committed Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- Mailing list: https://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 1901609] Re: signond causes qprocess crash
On 14/12/2020 18:48, Łukasz Zemczak wrote: > Sadly I cannot release the focal SRU as it seems that the signon package > FTBFS on ppc64el there: > > https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.04.1/+build/20365793 > > It seems to have built fine previously. Can someone take a look? > > ** Changed in: signon (Ubuntu Focal) >Status: Fix Committed => Incomplete > seems that failed to build without a log, so likely a launchpad 'burp'. a retry made it build ok -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Incomplete Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- Mailing list: https://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 1817453] Re: 19.04 installer displays keyboard layouts in the wrong language
On 15/03/2019 14:53, Launchpad Bug Tracker wrote: > This bug was fixed in the package console-setup - 1.178ubuntu11 This now causes LP: #1810647 to occur again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1817453 Title: 19.04 installer displays keyboard layouts in the wrong language Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Disco: Fix Released Bug description: When you select the Spanish language in the installer, when you go to the keyboard layout selection these are in another language. The options for Latin American Spanish do not appear. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.5 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 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 24 06:51:45 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1817453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version
** Changed in: plasma-discover (Ubuntu) Status: Confirmed => Fix Released ** Changed in: plasma-discover (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to a new version Status in packagekit package in Ubuntu: Fix Released Status in plasma-discover package in Ubuntu: Fix Released Status in packagekit source package in Bionic: Fix Released Status in plasma-discover source package in Bionic: Fix Released Bug description: [Impact] Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. [Test case] Upgrade packagekit using pkcon, make sure it does not "crash". [Regression potential] It could only lead to old packagekitd processes not restarting. packagekit will still be told to restart itself like before, the restart being added was unintended. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832120] [NEW] i386 - Test fails 'get_file_package() on foreign arches and releases'
Public bug reported: Version: 2.20.11-0ubuntu2 Release: Eoan 19.10 This failure is currently blocking Konsole 19.04.2-0ubuntu1 from migrating from proposed. The test 'get_file_package() on foreign arches and releases' now appears to be failing, at least the majority of the time, on i386 with: FAIL: test_get_file_package_uninstalled_multiarch (__main__.T) get_file_package() on foreign arches and releases -- Traceback (most recent call last): File "./test_backend_apt_dpkg.py", line 346, in test_get_file_package_uninstalled_multiarch True, cache_dir, arch='even') AssertionError: OSError not raised by get_file_package The test history can be seen here: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386 This fails against multiple triggers, including itself in the release pocket. I would also note that the same failure has been seen recently on amd64: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64 however that then passed on subsequent retries. Something that does not seem to be the case after multiple retries on i386. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Description changed: Version: 2.20.11-0ubuntu2 Release: Eoan 19.10 This failure is currently blocking Konsole 19.04.2-0ubuntu1 from migrating from proposed. - The test 'get_file_package() on foreign arches and releases' is now - appears to me failing at least the majority of the time with: + The test 'get_file_package() on foreign arches and releases' now appears + to be failing, at least the majority of the time, on i386 with: FAIL: test_get_file_package_uninstalled_multiarch (__main__.T) get_file_package() on foreign arches and releases -- Traceback (most recent call last): - File "./test_backend_apt_dpkg.py", line 346, in test_get_file_package_uninstalled_multiarch - True, cache_dir, arch='even') + File "./test_backend_apt_dpkg.py", line 346, in test_get_file_package_uninstalled_multiarch + True, cache_dir, arch='even') AssertionError: OSError not raised by get_file_package The test history can be seen here: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386 This fails against multiple triggers, including itself in the release pocket. I would also note that the same failure has been seen recently on amd64: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64 however that then passed on subsequent retries. Something that does not seem to be the case after multiple retries on i386. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1832120 Title: i386 - Test fails 'get_file_package() on foreign arches and releases' Status in apport package in Ubuntu: New Bug description: Version: 2.20.11-0ubuntu2 Release: Eoan 19.10 This failure is currently blocking Konsole 19.04.2-0ubuntu1 from migrating from proposed. The test 'get_file_package() on foreign arches and releases' now appears to be failing, at least the majority of the time, on i386 with: FAIL: test_get_file_package_uninstalled_multiarch (__main__.T) get_file_package() on foreign arches and releases -- Traceback (most recent call last): File "./test_backend_apt_dpkg.py", line 346, in test_get_file_package_uninstalled_multiarch True, cache_dir, arch='even') AssertionError: OSError not raised by get_file_package The test history can be seen here: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386 This fails against multiple triggers, including itself in the release pocket. I would also note that the same failure has been seen recently on amd64: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64 however that then passed on subsequent retries. Something that does not seem to be the case after multiple retries on i386. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1832120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832120] Re: i386 - Test fails 'test_get_file_package_uninstalled_multiarch'
** Summary changed: - i386 - Test fails 'get_file_package() on foreign arches and releases' + i386 - Test fails 'test_get_file_package_uninstalled_multiarch' ** Description changed: Version: 2.20.11-0ubuntu2 Release: Eoan 19.10 This failure is currently blocking Konsole 19.04.2-0ubuntu1 from migrating from proposed. - The test 'get_file_package() on foreign arches and releases' now appears - to be failing, at least the majority of the time, on i386 with: + The test 'test_get_file_package_uninstalled_multiarch' now appears to be + failing, at least the majority of the time, on i386 with: FAIL: test_get_file_package_uninstalled_multiarch (__main__.T) get_file_package() on foreign arches and releases -- Traceback (most recent call last): File "./test_backend_apt_dpkg.py", line 346, in test_get_file_package_uninstalled_multiarch True, cache_dir, arch='even') AssertionError: OSError not raised by get_file_package The test history can be seen here: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386 This fails against multiple triggers, including itself in the release pocket. I would also note that the same failure has been seen recently on amd64: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64 however that then passed on subsequent retries. Something that does not seem to be the case after multiple retries on i386. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1832120 Title: i386 - Test fails 'test_get_file_package_uninstalled_multiarch' Status in apport package in Ubuntu: New Bug description: Version: 2.20.11-0ubuntu2 Release: Eoan 19.10 This failure is currently blocking Konsole 19.04.2-0ubuntu1 from migrating from proposed. The test 'test_get_file_package_uninstalled_multiarch' now appears to be failing, at least the majority of the time, on i386 with: FAIL: test_get_file_package_uninstalled_multiarch (__main__.T) get_file_package() on foreign arches and releases -- Traceback (most recent call last): File "./test_backend_apt_dpkg.py", line 346, in test_get_file_package_uninstalled_multiarch True, cache_dir, arch='even') AssertionError: OSError not raised by get_file_package The test history can be seen here: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386 This fails against multiple triggers, including itself in the release pocket. I would also note that the same failure has been seen recently on amd64: http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64 however that then passed on subsequent retries. Something that does not seem to be the case after multiple retries on i386. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1832120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768752] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in
*** This bug is a duplicate of bug 1617564 *** https://bugs.launchpad.net/bugs/1617564 ** This bug has been marked a duplicate of bug 1617564 [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1768752 Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 Status in account-plugins package in Ubuntu: New Status in kaccounts-providers package in Ubuntu: New Bug description: apart from kde config telepathy accounts package install error, I even cant update ubuntu base as i try every time the results is broken file. then it asks me to report the bug. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sun Apr 29 07:05:33 2018 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2018-04-26 (6 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1768752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801439] Re: Unable to add software sources via the software-properties-qt
I suspect a regression may heave been introduced with this change? https://git.launchpad.net/ubuntu/+source/software- properties/commit/?h=ubuntu/bionic&id=f57935235ca0f52b32da7efe2a24cb26c7fc4573 -- 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/1801439 Title: Unable to add software sources via the software-properties-qt Status in software-properties package in Ubuntu: Triaged Bug description: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the example repo given in the dialog, which is not a PPA) 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1801439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1746128] Re: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in packa
libdbusmenu-qt (0.9.3+16.04.20160218-1ubuntu1) bionic; urgency=medium * Breaks/Replaces on libdbusmenu-qt5 for libdbusmenu-qt5-2. libdbusmenu-qt5 exists in Ubuntu archive, but not debian history. Can be dropped after 18.04. ** Changed in: libdbusmenu-qt (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1746128 Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu- qt5.so.2.6.0', which is also in package libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 Status in libdbusmenu-qt package in Ubuntu: Fix Released Bug description: i don't know to be specific ProblemType: Package DistroRelease: Kali 2018.1 Package: libdbusmenu-qt5-2 (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Jan 29 21:00:43 2018 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in package libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 InstallationDate: Installed on 2018-01-26 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.19.0.5kali1 apt 1.6~alpha7 SourcePackage: libdbusmenu-qt Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in package libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1746128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757730] Re: Please port your package away from Qt 4
** Changed in: libdbusmenu-qt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757730 Title: Please port your package away from Qt 4 Status in libdbusmenu-qt package in Ubuntu: Fix Released Status in libdbusmenu-qt package in Debian: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1757730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856953] Re: Misconfigured Debian control file makes dist-upgrading with package libdbusmenu-qt5 crash
A direct xenial to eoan upgrade path is NOT supported. The correct breaks/replaces are in place for any supported upgrade paths, and have quite correctly been dropped after Bionic, where keeping that delta to debian is no longer required. ** Changed in: libdbusmenu-qt (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1856953 Title: Misconfigured Debian control file makes dist-upgrading with package libdbusmenu-qt5 crash Status in libdbusmenu-qt package in Ubuntu: Won't Fix Bug description: Dear maintainers, Lacking of `Breaks` and `Replaces` parts in the Debian control file of libdbusmenu-qt5-2 package (version 0.9.3+16.04.20160218-2) would make dist-upgrading from Xenial (with libdbusmenu-qt5 installed) to Eoan or Focal crash. Expected behavior of dist-upgrading: - should deconfigure `libdbusmenu-qt5` first - only then can `libdbusmenu-qt5-2` be installed What happened instead: - dpkg unpacks `libdbusmenu-qt5-2` over files of `libdbusmenu-qt5`, thus causing a crash Steps to reproduce: 1. install a fresh Ubuntu 16.04.6 and upgrade packages 2. change the release in apt source list from `xenial` to `eoan` or `focal` and include universe section 3. perform `apt dist-upgrade` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1856953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682297] Re: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pa
** Changed in: libdbusmenu-qt (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1682297 Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdbusmenu- qt5.so.2.6.0', wat ook in pakket libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit Status in libdbusmenu-qt package in Ubuntu: Won't Fix Bug description: i clicked to install a lot of software at once ProblemType: Package DistroRelease: Kali 2017.1 Package: libdbusmenu-qt5-2 (not installed) ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-lowlatency 4.8.17 Uname: Linux 4.8.0-46-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Apr 12 23:45:47 2017 ErrorMessage: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit InstallationDate: Installed on 2017-04-11 (1 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.23kali1 apt 1.2.19 SourcePackage: libdbusmenu-qt Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1682297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 852276] Re: package libdbusmenu-qt2 0.8.2-0ubuntu2 failed to install/upgrade: archive du système de fichiers corrompue - archive du paquet corrompue
** Changed in: libdbusmenu-qt (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/852276 Title: package libdbusmenu-qt2 0.8.2-0ubuntu2 failed to install/upgrade: archive du système de fichiers corrompue - archive du paquet corrompue Status in libdbusmenu-qt package in Ubuntu: Won't Fix Bug description: apres telechargement du drivers nvidia 280.13 pas moyen de l'ouvrir pour l'intaller .!!! ProblemType: Package DistroRelease: Ubuntu 11.04 Package: libdbusmenu-qt2 0.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Sep 17 01:10:25 2011 ErrorMessage: archive du système de fichiers corrompue - archive du paquet corrompue InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: libdbusmenu-qt Title: package libdbusmenu-qt2 0.8.2-0ubuntu2 failed to install/upgrade: archive du système de fichiers corrompue - archive du paquet corrompue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/852276/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
