[Desktop-packages] [Bug 2063128] [NEW] Upgrade from mantic to noble shows a debconf prompt
Public bug reported: Reproducer: * Run Ubuntu Studio Mantic in a VM * Run `do-release-upgrade -d` to upgrade it to Noble * After the package download phase, the packages upgrade starts, and you quickly get prompted by jackd2 asking `Enable realtime process priority?` This can be avoided with `export DEBIAN_FRONTEND=noninteractive`, that's why it didn't show up in the CI, but we can't expect users to rely on this. I've attached a screenshot of the prompt, that contains more details on what exactly is asked. ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2024-04-22-16_31_14.png" https://bugs.launchpad.net/bugs/2063128/+attachment/5769449/+files/2024-04-22-16_31_14.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/2063128 Title: Upgrade from mantic to noble shows a debconf prompt Status in jackd2 package in Ubuntu: New Bug description: Reproducer: * Run Ubuntu Studio Mantic in a VM * Run `do-release-upgrade -d` to upgrade it to Noble * After the package download phase, the packages upgrade starts, and you quickly get prompted by jackd2 asking `Enable realtime process priority?` This can be avoided with `export DEBIAN_FRONTEND=noninteractive`, that's why it didn't show up in the CI, but we can't expect users to rely on this. I've attached a screenshot of the prompt, that contains more details on what exactly is asked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2063128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
With the latest upload of mutter (46.0-1ubuntu7), we still have `gnome- shell` crashes during Jammy to Noble upgrades. Here is a recent oops: https://errors.ubuntu.com/oops/0ec860d4-fd60-11ee-9dae-fa163ec44ecd Let me know if you need anything else. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Feb 21 21:39:12 autopkgtest gnome-shell[17959]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 https://errors.ubuntu.com/problem/bf714caff944bed915a3c4321664107c65547d1f https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058930] Re: Missing in i386 Packages index
Apparently this was linked to the extra `setup-commands` issue that made us loose the `proposed` pocket, and got "fixed" by updating the database with the `no-proposed` tag. TL;DR: fixed, and we didn't loose any cowboy specific to that issue, everything is fine. ** Changed in: libvpx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/2058930 Title: Missing in i386 Packages index Status in libvpx package in Ubuntu: Fix Released Bug description: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057490] Re: Crash during upgrade from Jammy/Mantic to Noble
There, I finally got an apport crash file. Is that enough for you to have a first look? ** Attachment added: "_usr_sbin_NetworkManager.0.crash" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+attachment/5756023/+files/_usr_sbin_NetworkManager.0.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble Status in network-manager package in Ubuntu: New Bug description: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057490] Re: Crash during upgrade from Jammy/Mantic to Noble
I'll see for reproducing that locally and provide you with a crash report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble Status in network-manager package in Ubuntu: New Bug description: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057490] [NEW] Crash during upgrade from Jammy/Mantic to Noble
Public bug reported: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "mantic-noble-ubuntu-mate_network-manager_crash.zip" https://bugs.launchpad.net/bugs/2057490/+attachment/5755245/+files/mantic-noble-ubuntu-mate_network-manager_crash.zip ** Summary changed: - Crash during upgrade from Mantic to Noble + Crash during upgrade from Jammy/Mantic to Noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble Status in network-manager package in Ubuntu: New Bug description: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056432] Re: Thunderbird profile not migrated to snap
*** This bug is a duplicate of bug 2056434 *** https://bugs.launchpad.net/bugs/2056434 ** This bug has been marked a duplicate of bug 2056434 Thunderbird profile not migrated to snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056432 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: New Bug description: Today's update installed the thunderbird snap and removed the thunderbird binary but it did not migrate my thunderbird profile. Now I don't have access to any old mails anymore. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: thunderbird 1:115.8.1+build1+snap2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Mar 7 09:57:56 2024 InstallationDate: Installed on 2021-05-26 (1016 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SnapChanges: IDStatus Spawn Ready Summary 1092 Done2024-03-07T09:44:07+01:00 2024-03-07T09:54:05+01:00 Install "thunderbird" snap SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056668] Re: Thunderbird Snap migration loses user profile
Here is how I worked around this:
* close thunderbird, make sure it's not running in the background
* `rsync -raxPHAX ~/.thunderbird/ ~/snap/thunderbird/common/.thunderbird/`
* edit `~/snap/thunderbird/common/.thunderbird/profiles.ini` to make sure the
only profile listed here is the one with the data (the biggest folder in
`~/snap/thunderbird/common/.thunderbird/`)
* run thunderbird
So far, everything seems to be in order, including contacts, calendars
on multiple accounts, sieve filter and message redirect plugins.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056668
Title:
Thunderbird Snap migration loses user profile
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
version?
I consider this bug to be Grave since it not only affects thunderbid,
but also a huge number of depending other services, bug-reporting
amongst it.
Thunderbird Snap migration loses user profile
With the migration from normal deb to snap all and any settings, addons,
accounts, etc got lost.
This is a big no-no.
Architecture: amd64
Version: 1:115.8.1+build1+snap2
No LSB modules are available.
Description: Ubuntu Noble Numbat (development branch)
Release: 24.04
root@kyle:/opt/DATA/media/incoming/tmp# apt-cache policy thunderbird
thunderbird:
Installed: 1:115.8.1+build1+snap2
Candidate: 1:115.8.1+build1+snap2
Version table:
*** 1:115.8.1+build1+snap2 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
1:115.8.1+build1-0ubuntu0.23.10.1 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
1:115.3.1+build1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
neuffer@kyle:~$ ls -la ~/.thunderbird/
total 28
drwx-- 5 neuffer neuffer 4096 Okt 7 2019 .
drwxr-x--- 26 neuffer neuffer 4096 Mär 10 11:09 ..
drwx-- 17 neuffer neuffer 4096 Mär 5 17:50 8ru3o2xn.default
drwx-- 4 neuffer neuffer 4096 Mär 5 15:58 'Crash Reports'
-rw-rw-r-- 1 neuffer neuffer 45 Okt 7 2019 installs.ini
drwx-- 2 neuffer neuffer 4096 Apr 2 2019 'Pending Pings'
-rw-rw-r-- 1 neuffer neuffer 166 Okt 7 2019 profiles.ini
neuffer@kyle:~$
neuffer@kyle:~$ thunderbird --ProfileManager
_IceTransSocketINETConnect() no usable address for kyle:44955
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:14:30.844: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
console.error: (new UnknownError("IndexedDB:
thunderbird/url-classifier-skip-urls getLastModified() IndexedDB: The
operation failed for reasons unrelated to the database itself and not covered
by any other error code.", "resource://services-settings/IDBHelpers.jsm", 18))
_IceTransSocketINETConnect() no usable address for kyle:44955
[ImapModuleLoader] Using nsImapService.cpp
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:15:38.811: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0
unprotected)"
console.error: ({})
JavaScript error: chrome://messenger/content/aboutMessage.js, line 119:
NS_ERROR_ILLEGAL_VALUE: Component returned
[Desktop-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
Yeah, sorry, I forgot to mention. The crashes that happen in our Jenkins are already pushed to the error tracker. Here are links to the latest oopses: gnome-shell: https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c tracker-extract: https://errors.ubuntu.com/oops/7c05a805-d101-11ee-8a58-fa163ec8ca8c Maybe Tim will have a link for the polkit crash, but I couldn't find one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
** Also affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Also affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
Here is the whole Jenkins archive. The file you asked is in `archive/ubuntu-jammy-noble-xubuntu- amd64_qemu/20240105.141607/artifacts/upgrade_run/system_details/dist- upgrade/main.log`, along with many other files that may also be interesting. ** Attachment added: "archive.zip" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2043820/+attachment/5745887/+files/archive.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Noble: Confirmed Status in snapd source package in Noble: Confirmed Bug description: When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade fails consistently at the `Installing the firefox snap` step. This was first detected on Jenkins [1], then reproduced locally with `auto-upgrade-testing`, then finally by manually running a `do- release-upgrade -d` in a VM. [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade- list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull (Jenkins full log attached) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.17 ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Fri Nov 17 18:24:22 2023 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049907] [NEW] tracker-extract-3 crash with SIGSYS when upgrading from 22.04 to 24.04
Public bug reported: Very similar behavior as this existing bug: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859 Almost copy-paste of original report: When upgrading Ubuntu Desktop from 22.04 to 24.04, there's often (pretty much always) a crash from tracker-extract, as described in the following error report: https://errors.ubuntu.com/oops/7a86fbf0-b52b-11ee-b9e4-fa163e171f02 The crash occurs during the upgrade, which means it's fairly hard to investigate exactly what's going on as apport fails to extract a stack trace, the binaries being overwritten during the upgrade. ** Affects: tracker-miners (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/2049907 Title: tracker-extract-3 crash with SIGSYS when upgrading from 22.04 to 24.04 Status in tracker-miners package in Ubuntu: New Bug description: Very similar behavior as this existing bug: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859 Almost copy-paste of original report: When upgrading Ubuntu Desktop from 22.04 to 24.04, there's often (pretty much always) a crash from tracker-extract, as described in the following error report: https://errors.ubuntu.com/oops/7a86fbf0-b52b-11ee-b9e4-fa163e171f02 The crash occurs during the upgrade, which means it's fairly hard to investigate exactly what's going on as apport fails to extract a stack trace, the binaries being overwritten during the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2049907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
