[Desktop-packages] [Bug 929067] Re: Crash during restore: "assert ropath.index == (), ropath.index"
Just hit this bug on duplicity 0.8.23 on a modern FreeBSD PKG install. Modern Debian apt package is 0.8.22 LOL. Now trying to get it installed using python pip directly... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/929067 Title: Crash during restore: "assert ropath.index == (), ropath.index" Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Released Bug description: Duplicity version: 0.6.15 Python version: 2.7.2+ OS: Ubuntu 11.10 Target filesystem: Linux (Synology NAS, via sftp) I'm experiencing a repeatable crash which manifests itself on restore, when the initial backup is interrupted and resumed. The data I use doesn't seem to matter. Steps to reproduce: 1. Create a directory of test data. Mine was around 125MiB 2. duplicity --no-encryption TestDir ssh://user@target/backup/TestDir 3. Wait until one or two tar files have been uploaded, then Ctrl-C to kill duplicity 4. duplicity --no-encryption TestDir ssh://user@target/backup/TestDir (duplicity should resume the backup where it left off; allow it to complete this time) 5. duplicity --no-encryption TestDir ssh://user@target/backup/TestDir (repeat the command a third time - note that duplicity reports a nonzero number of DeletedFiles even though the data has not changed. 6. rm -r TestDir 7. duplicity --no-encryption ssh://user@target/backup/TestDir TestDir (attempt to restore -> crash) The crash output is as follows: user@laptop:~$ duplicity --no-encryption ssh://user@target/backup/Test4 Test4 Local and Remote metadata are synchronized, no sync needed. Last full backup date: Wed Feb 8 19:29:16 2012 Traceback (most recent call last): File "/usr/bin/duplicity", line 1359, in with_tempdir(main) File "/usr/bin/duplicity", line 1342, in with_tempdir fn() File "/usr/bin/duplicity", line 1276, in main restore(col_stats) File "/usr/bin/duplicity", line 591, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in Write_ROPaths ITR( ropath.index, ropath ) File "/usr/lib/python2.7/dist-packages/duplicity/lazy.py", line 320, in __call__ self.process_w_branch(index, self.root_branch, args) File "/usr/lib/python2.7/dist-packages/duplicity/lazy.py", line 293, in process_w_branch branch.start_process, args) File "/usr/lib/python2.7/dist-packages/duplicity/robust.py", line 37, in check_common_error return function(*args) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 545, in start_process assert ropath.index == (), ropath.index AssertionError: somefile.dat I can provide more information, log output, test data (although the data doesn't seem to matter), or test with other versions of duplicity if requested. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/929067/+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 2051383] Re: gnome-shell high CPU utilization when moving a high frequency mouse
It seems to also track mouse movement when playing games in full-screen mode which reduces FPS. Is this normal? -- 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/2051383 Title: gnome-shell high CPU utilization when moving a high frequency mouse Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051572] Re: Always preseed core and snapd snap in server seed
Based on the data, I'm in the "No" camp as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2054163] [NEW] Figure out packaging repo details
Public bug reported: Ubuntu's gnome-snapshot packaging had to diverge from Debian's because current Rust policy for Ubuntu main requires that it be vendored. This conflicts with best practice in Debian to devendor packages. Ubuntu changes to GNOME packages are normally pushed to a separate branch in Salsa in the same repo as the Debian packages. This usually adds a slight overhead to the Debian repo in exchange for a better Ubuntu workflow and easier sharing between Debian and Ubuntu. In this case, I think the overhead is more significant. The vendor/ directory is very large. The vendored orig tarball is currently 33 megabytes. In comparison, the devendored tarball is only 1 megabyte. Every new upstream release would add permanently significantly increase the git repo size. Suggestions === - A "fork" of the Salsa repo, in Salsa Forks can have different names so we could name it something like https://salsa.debian.org/gnome-team/snapshot-ubuntu to preserve the existing team access. ** Affects: gnome-snapshot (Ubuntu) Importance: Low Status: Triaged ** Tags: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-snapshot in Ubuntu. https://bugs.launchpad.net/bugs/2054163 Title: Figure out packaging repo details Status in gnome-snapshot package in Ubuntu: Triaged Bug description: Ubuntu's gnome-snapshot packaging had to diverge from Debian's because current Rust policy for Ubuntu main requires that it be vendored. This conflicts with best practice in Debian to devendor packages. Ubuntu changes to GNOME packages are normally pushed to a separate branch in Salsa in the same repo as the Debian packages. This usually adds a slight overhead to the Debian repo in exchange for a better Ubuntu workflow and easier sharing between Debian and Ubuntu. In this case, I think the overhead is more significant. The vendor/ directory is very large. The vendored orig tarball is currently 33 megabytes. In comparison, the devendored tarball is only 1 megabyte. Every new upstream release would add permanently significantly increase the git repo size. Suggestions === - A "fork" of the Salsa repo, in Salsa Forks can have different names so we could name it something like https://salsa.debian.org/gnome-team/snapshot-ubuntu to preserve the existing team access. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-snapshot/+bug/2054163/+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 2054162] [NEW] package install-info 6.8-4build1 failed to install/upgrade: el subproceso instalado paquete install-info script post-installation devolvió el código de salida de
Public bug reported: ackage install-info 6.8-4build1 failed to install/upgrade: el subproceso instalado paquete install-info script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: install-info 6.8-4build1 Uname: Linux 6.7.4-2-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 16 21:13:43 2024 ErrorMessage: el subproceso instalado paquete install-info script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2024-01-29 (18 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: texinfo Title: package install-info 6.8-4build1 failed to install/upgrade: el subproceso instalado paquete install-info script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/2054162 Title: package install-info 6.8-4build1 failed to install/upgrade: el subproceso instalado paquete install-info script post-installation devolvió el código de salida de error 1 Status in texinfo package in Ubuntu: New Bug description: ackage install-info 6.8-4build1 failed to install/upgrade: el subproceso instalado paquete install-info script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: install-info 6.8-4build1 Uname: Linux 6.7.4-2-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 16 21:13:43 2024 ErrorMessage: el subproceso instalado paquete install-info script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2024-01-29 (18 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: texinfo Title: package install-info 6.8-4build1 failed to install/upgrade: el subproceso instalado paquete install-info script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/2054162/+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 1855699] Re: Click pen icon on right side of path bar to enter custom path.
I'm marking this fixed since the upstream issue has been fixed in Nautilus 46 Beta. The location in the headerbar can be directly edited by simply clicking on it. Ubuntu 24.04 LTS will be released later this year with Nautilus 46. ** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1855699 Title: Click pen icon on right side of path bar to enter custom path. Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) Add a pen icon to the right side of the path bar. If a user clicks the pen icon, the path bar would become editable. 4) Unable to enter a custom path. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1855699/+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
Re: [Desktop-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
On Fri, Feb 16, 2024 at 06:51:46PM -, Philip Roche wrote: > @vorlon @jchittum @paelzer given the above findings are you still -1 on > any snap preseeding? Based on the data, I vote not to preseed any snaps. That is my position. Thanks for bringing data to this! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2051572] Re: Always preseed core and snapd snap in server seed
With only snapd snap preseeded I get boot times very similar to ``` ubuntu@cloudimg:~$ systemd-analyze Startup finished in 3.757s (kernel) + 12.458s (userspace) = 16.216s graphical.target reached after 12.061s in userspace. ``` Which shows we are still taking a boot time hit of ~1.5 seconds... however with snaps snap preseeded we are seeing a much faster "first snap" install. From ~21 seconds down to 17 seconds. To summarise. * Definitely faster boot without any snaps preseeded @ ~1.5 seconds in my tests * Still slower boot with only snapd snap preseeded but faster first snap install time by about ~4 seconds I have been unable to get any data on LXD usage numbers on cloud/server to help. So the question remains do we want faster boot by ~1.5 seconds (based on my test environment) at the expense of first snap install speed improvements of between 4 (if only snapd snap is preseeded) seconds and up to ~15 seconds (if a core snap is also preseeded)? @vorlon @jchittum @paelzer given the above findings are you still -1 on any snap preseeding? Based on the data, I vote not to preseed any snaps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2037767] Re: file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event()
** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2037767 Title: file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event() Status in file-roller package in Ubuntu: New Bug description: Archive Manager (file-roller) often crashes when I open Qt source archives. I usually build (most of) Qt modules myself from the source archive "qt-everywhere-src-X.Y.Z.tar.xz". When I open the archive to select the directories I wish to extract, Archive Manager often crashes so I have to try again some times to succeed. Steps to reproduce the issue: 1) Download the file https://download.qt.io/official_releases/qt/6.5/6.5.3/single/qt- everywhere-src-6.5.3.tar.xz, 2) Open it with Archive Manager, 3) Browse the directories. The application will eventually crash. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: file-roller 43.0-1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 19:13:52 2023 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2023-05-16 (136 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230516) ProcCmdline: /usr/bin/file-roller /home/username/Downloads/qt-everywhere-src-6.5.3.tar.xz SegvAnalysis: Segfault happened at: 0x563107aa36c0:mov(%rbx),%rsi PC (0x563107aa36c0) ok source "(%rbx)" (0x20006) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ??? () ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with SIGSEGV in ???() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users vboxusers wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2037767/+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 2054150] Re: file-roller crashed with SIGSEGV in ???()
*** This bug is a duplicate of bug 2037767 *** https://bugs.launchpad.net/bugs/2037767 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2037767, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2054150/+attachment/5746693/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2054150/+attachment/5746695/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2054150/+attachment/5746699/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2054150/+attachment/5746700/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2054150/+attachment/5746701/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2054150/+attachment/5746702/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2054150/+attachment/5746703/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 2037767 file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2054150 Title: file-roller crashed with SIGSEGV in ???() Status in file-roller package in Ubuntu: New Bug description: File-roller crashes while browsing the contents of big archives. I'm actually trying to select and extract some folders from https://download.qt.io/official_releases/qt/6.6/6.6.2/single/qt- everywhere-src-6.6.2.tar.xz $ lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 $ apt-cache policy file-roller file-roller: Installed: 43.1-1 Candidate: 43.1-1 Version table: *** 43.1-1 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: file-roller 43.1-1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 14:37:59 2024 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2023-05-16 (276 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230516) ProcCmdline: /usr/bin/file-roller /home/username/Downloads/qt-everywhere-src-6.6.2.tar.xz SegvAnalysis: Segfault happened at: 0x55c7652e82d0:mov(%rbx),%rsi PC (0x55c7652e82d0) ok source "(%rbx)" (0x20006) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ??? () ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with SIGSEGV in ???() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users vboxusers wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2054150/+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 2051572] Re: Always preseed core and snapd snap in server seed
> * boot times w/ and w/o preseeded snaps Without preseeded snaps: ``` ubuntu@cloudimg:~$ systemd-analyze Startup finished in 3.609s (kernel) + 11.026s (userspace) = 14.636s graphical.target reached after 10.642s in userspace. ``` With preseeded snapd and core22 snaps: ``` ubuntu@cloudimg:~$ systemd-analyze Startup finished in 3.733s (kernel) + 12.566s (userspace) = 16.300s graphical.target reached after 12.175s in userspace. ``` This is on a powerful AMD threadripper machine using qemu. I ran this 3 times for each image with similar results so we are definitely seeing a boot speed improvement without the snaps preseeded. I will try with only snapd snap too for comparison. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2049988] Re: Latest kernel kills wifi.
Any news on this bug? Latest patches did not affect it -- 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/2049988 Title: Latest kernel kills wifi. Status in network-manager package in Ubuntu: New Bug description: New kernel 6.0.5-14 boot up system does not recognize built in wifi adapter. When I drop to last kernel install wifi works fine. HP Pavillion With intel core I7 chip. Output of lshow --C network: *-network description: Wireless interface product: MT7921 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: b4:8c:9d:28:0e:cb width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=mt7921e driverversion=6.2.0-39-generic firmware=01-20220209150915 ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 memory:601210-60121f memory:601220-6012203fff memory:6012204000-6012204fff --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick2379 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-15 (432 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Laptop 15-eg2xxx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/08/2023 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 89F7 dmi.board.vendor: HP dmi.board.version: 14.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.27 dmi.modalias: dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg2xxx dmi.product.sku: 6W540UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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 2054149] [NEW] Super+2 shortcut gets captured by windows since 23.10 (AZERTY keyboard)
Public bug reported: I have Ubuntu 23.10 with mutter 45.2-0ubuntu3. I have an AZERTY keyboard. In order to switch to another application, I use Super+num (switch to application number 'num' in my dock). Since last update (Ubuntu 23.10), when the keyboard is captured by the current window, I cannot move to application 2 with Super+2 Instead, it writes a 'é' (this is the number 2 key on a US English keyboard). I have the same problem with Super+7 (è in AZERTY keyboard), but all other Super+num works fine. This behavior occurs only when I am on a window capturing my keyboard. Example: - If I am reading a PDF with Evince (keyboard is not captured for writing), everything works perfectly. - If I am writing something on Firefox/gnome-terminal, keyboards write 'é' whenever I press Super+2, and cannot move to the wanted application. - On some other applications, everything works fine (Emacs for example, even when keyboard is captured for writing). I think this bug is related with bug #2035076, and so with mutter. Indeed, I had the same capitalization problem with the same apps than in this bug (i.e. not working with Firefox and gnome-terminal but working with perfectly with Emacs). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 45.2-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 18:13:16 2024 InstallationDate: Installed on 2021-11-05 (833 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-12-06 (72 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054149 Title: Super+2 shortcut gets captured by windows since 23.10 (AZERTY keyboard) Status in mutter package in Ubuntu: New Bug description: I have Ubuntu 23.10 with mutter 45.2-0ubuntu3. I have an AZERTY keyboard. In order to switch to another application, I use Super+num (switch to application number 'num' in my dock). Since last update (Ubuntu 23.10), when the keyboard is captured by the current window, I cannot move to application 2 with Super+2 Instead, it writes a 'é' (this is the number 2 key on a US English keyboard). I have the same problem with Super+7 (è in AZERTY keyboard), but all other Super+num works fine. This behavior occurs only when I am on a window capturing my keyboard. Example: - If I am reading a PDF with Evince (keyboard is not captured for writing), everything works perfectly. - If I am writing something on Firefox/gnome-terminal, keyboards write 'é' whenever I press Super+2, and cannot move to the wanted application. - On some other applications, everything works fine (Emacs for example, even when keyboard is captured for writing). I think this bug is related with bug #2035076, and so with mutter. Indeed, I had the same capitalization problem with the same apps than in this bug (i.e. not working with Firefox and gnome-terminal but working with perfectly with Emacs). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 45.2-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 18:13:16 2024 InstallationDate: Installed on 2021-11-05 (833 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-12-06 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054149/+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 2053207] Re: glib requires gobject-introspection >= 1.78.1-13
No, it does not need an epoch, but we do need to do another gobject- introspection upload to stop building the binary packages that glib now provides. I have requested a review from another Debian maintainer: https://salsa.debian.org/gnome-team/gobject-introspection/-/merge_requests/14 ** Also affects: gobject-introspection (Ubuntu) Importance: Undecided Status: New ** Changed in: gobject-introspection (Ubuntu) Importance: Undecided => High ** Changed in: gobject-introspection (Ubuntu) Status: New => In Progress ** Changed in: gobject-introspection (Ubuntu) Assignee: (unassigned) => Jeremy Bícha (jbicha) ** Tags added: ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2053207 Title: glib requires gobject-introspection >= 1.78.1-13 Status in glib2.0 package in Ubuntu: Fix Committed Status in gobject-introspection package in Ubuntu: In Progress Bug description: glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate out of noble-proposed before or at the same as glib2.0. I'm filing this bug to explain why glib2.0 isn't migrating despite the excuses page saying "Will attempt migration" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+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 2054135] Re: soffice.bin crashed with SIGSEGV in rtl_uString_release()
*** This bug is a duplicate of bug 2052384 *** https://bugs.launchpad.net/bugs/2052384 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2052384, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2054135/+attachment/5746674/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2054135/+attachment/5746676/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2054135/+attachment/5746679/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2054135/+attachment/5746680/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2054135/+attachment/5746681/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2054135/+attachment/5746682/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2054135/+attachment/5746683/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 2052384 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2054135 Title: soffice.bin crashed with SIGSEGV in rtl_uString_release() Status in libreoffice package in Ubuntu: New Bug description: soffice.bin crashed with SIGSEGV in rtl_uString_release() ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libreoffice-core 4:24.2.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Fri Feb 16 13:42:53 2024 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2024-02-02 (14 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240202) JournalErrors: -- No entries -- ProcAttrCurrent: libreoffice-soffice (complain) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc file:///home/username/Dropbox/Dropbox%20Raiz%20Pogorelsky/Docpog/02-Docpog%20Backup/Contas/A%C3%A7%C3%B5es.ods --splash-pipe=5 SegvAnalysis: Segfault happened at: 0x7f9fddceec64 :mov (%rdi),%eax PC (0x7f9fddceec64) ok source "(%rdi)" (0x7f9fae2324c0) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: rtl_uString_release () from /usr/lib/libreoffice/program/libuno_sal.so.3 ?? () from /usr/lib/libreoffice/program/libmergedlo.so ?? () from /usr/lib/libreoffice/program/libmergedlo.so __run_exit_handlers (status=0, listp=0x7f9fd85fe680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at ./stdlib/exit.c:111 __GI_exit (status=) at ./stdlib/exit.c:141 Title: soffice.bin crashed with SIGSEGV in rtl_uString_release() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip fax floppy lpadmin plugdev sambashare sudo tape users video separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2054135/+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 2053207] Re: glib requires gobject-introspection >= 1.78.1-13
It's marked failed to upload on all architectures right now: INFOgir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 INFOgir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 I guess that means an epoch is needed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2053207 Title: glib requires gobject-introspection >= 1.78.1-13 Status in glib2.0 package in Ubuntu: Fix Committed Bug description: glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate out of noble-proposed before or at the same as glib2.0. I'm filing this bug to explain why glib2.0 isn't migrating despite the excuses page saying "Will attempt migration" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+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 2054109] Re: nautilus fails to build on armhf
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2054109 Title: nautilus fails to build on armhf Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Nautilus 46 fails to build on armhf because of a test failure. However, the test failure might be revealing a bug in nautilus's functions that would affect 32-bit architectures. I have filed the issue with the Nautilus developers. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2054109/+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 2054132] [NEW] when have splash parameter in cmdline, desktop remain with black screen
Public bug reported: Hello, I installed today Ubuntu Studio, Ubuntu Official and Ubuntu Unity - 24.04. And i notice behaviour regarding plymouth and splash parameter. When have splash parameter in cmdline, desktop remain with black screen forever. For workaround, i remove "splash" parameter from cmdline. System: CPU: 11th Gen Intel(R) Core(TM) i7-1185GRE @ 2.80GHz OS: 24.04 (Noble Numbat) VGA: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) Firmware: 20240202.git36777504-0ubuntu1 00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] Flags: bus master, fast devsel, latency 0, IRQ 161 Memory at 60 (64-bit, non-prefetchable) [size=16M] Memory at 40 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Capabilities: [320] Single Root I/O Virtualization (SR-IOV) Kernel driver in use: i915 Kernel modules: i915, xe ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2054132 Title: when have splash parameter in cmdline, desktop remain with black screen Status in plymouth package in Ubuntu: New Bug description: Hello, I installed today Ubuntu Studio, Ubuntu Official and Ubuntu Unity - 24.04. And i notice behaviour regarding plymouth and splash parameter. When have splash parameter in cmdline, desktop remain with black screen forever. For workaround, i remove "splash" parameter from cmdline. System: CPU: 11th Gen Intel(R) Core(TM) i7-1185GRE @ 2.80GHz OS: 24.04 (Noble Numbat) VGA: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) Firmware: 20240202.git36777504-0ubuntu1 00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] Flags: bus master, fast devsel, latency 0, IRQ 161 Memory at 60 (64-bit, non-prefetchable) [size=16M] Memory at 40 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Capabilities: [320] Single Root I/O Virtualization (SR-IOV) Kernel driver in use: i915 Kernel modules: i915, xe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2054132/+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 2054121] Re: Random Freezing
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in xorg package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2054121/+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 2054121] [NEW] Random Freezing
You have been subscribed to a public bug:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug freeze mantic ubuntu
--
Random Freezing
https://bugs.launchpad.net/bugs/2054121
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
--
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 2054111] [NEW] [SRU] libreoffice 7.6.5 for mantic
Public bug reported: [Impact] * LibreOffice 7.6.5 is in its fifth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.5_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.4 see the list of bugs fixed in the release candidates of 7.6.5 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.6.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.5/RC2#List_of_fixed_bugs 7.6.5 RC1 is identical to the 7.6.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1816/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15791929/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240216_132420_3c270@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240216_140709_197f6@/log.gz * [armhf] ... * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240216_130131_fd665@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240216_141429_f0d16@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libreoffice (Ubuntu Mantic) Importance: High Assignee: Rico Tzschichholz (ricotz) Status: New ** Also affects: libreoffice (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Mantic) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Mantic) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released ** Description changed: [Impact] * LibreOffice 7.6.5 is in its fifth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.5_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.4 see the list of bugs fixed in the release candidates of 7.6.5 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.6.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.5/RC2#List_of_fixed_bugs 7.6.5 RC1 is identical to the 7.6.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1816/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests
[Desktop-packages] [Bug 2054109] [NEW] nautilus fails to build on armhf
Public bug reported: Nautilus 46 fails to build on armhf because of a test failure. However, the test failure might be revealing a bug in nautilus's functions that would affect 32-bit architectures. I have filed the issue with the Nautilus developers. ** Affects: nautilus Importance: Unknown Status: Unknown ** Affects: nautilus (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs noble update-excuse ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #3322 https://gitlab.gnome.org/GNOME/nautilus/-/issues/3322 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/3322 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2054109 Title: nautilus fails to build on armhf Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Nautilus 46 fails to build on armhf because of a test failure. However, the test failure might be revealing a bug in nautilus's functions that would affect 32-bit architectures. I have filed the issue with the Nautilus developers. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2054109/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: devhelp (Ubuntu) Status: Confirmed => Fix Released ** Changed in: devhelp (Ubuntu) Assignee: (unassigned) => Georgia Garcia (georgiag) ** Changed in: epiphany-browser (Ubuntu) Status: Confirmed => Fix Released ** Changed in: epiphany-browser (Ubuntu) Assignee: (unassigned) => Georgia Garcia (georgiag) ** Changed in: evolution (Ubuntu) Status: Confirmed => Fix Released ** Changed in: evolution (Ubuntu) Assignee: (unassigned) => Georgia Garcia (georgiag) ** Changed in: opam (Ubuntu) Status: Confirmed => Fix Released ** Changed in: opam (Ubuntu) Assignee: (unassigned) => Georgia Garcia (georgiag) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: In Progress Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Committed Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: In Progress Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: In Progress Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released 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/akonadiconsole/+bug/2046844/+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 2051572] Re: Always preseed core and snapd snap in server seed
@vorlon > Also, statically seeding a particular base snap is bad form, as soon as lxd upgrades its base you lose your performance benefit and have to play catch-up in a stable release. yes I don't like this either. Even if we do change it later to core24 then the expectations people have for their snap startup/install time for snaps, not LXD, which use core22 will change/break. > If "time to initialize lxd" is your metric, I think you're measuring the wrong thing :) Well it isn't just LXD though - any snap install/init will be affected with this change @jchittum > * the amount of time/slow down for `lxd` booting from `lxd-installer` in a "no snaps pre-seeded" setting We do have this. In initial tests it 15 seconds vs 29 seconds. > * the _usage_ and _expectation_ about the speed here. I will try get this info from LXD team > * boot times w/ and w/o preseeded snaps I will gather this info @paelzer > I never heard someone complaining that LXD takes a bit there, but every > second of boot time seems to be valued highly. > Now that we had to reduce this to the lxd-installer everywhere (Due to LP > #2051346) it is really worth to be re-revaluated. Thank you for driving this > Phil! Yes I really want this to be a decision we know we are making and consciously making. >IMHO now that your first LXD command will take a bit longer already (due to >fetching LXD snap), the exact amount of that "a bit longer" (as being more by >also fetching snapd and base) seems almost irrelevant as long as it is in the >same ballpark. is 15 seconds vs 30 seconds really in the same ballpark? > Furthermore as Simon showed (thanks), by snapd being a baseless snap we'd not even gain something by having that around already for the latter fetch of lxd by lxd-installer. Not true. It still takes time to fetch and install the snapd snap - 6.738s in my test in qemu > I further appreciate John's comment that we should back up some of our > current assumptions (how much will this slow down lxc interactions, how much > will the boot speed gain) with some actual data. I will continue to gather data on the boot speed implications. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: ghostwriter (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: In Progress Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Committed Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: In Progress Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: In Progress Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released 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/akonadiconsole/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: akonadiconsole (Ubuntu) Importance: Undecided Status: New ** Changed in: akonadiconsole (Ubuntu) Importance: Undecided => High ** Changed in: akonadiconsole (Ubuntu) Status: New => In Progress ** Changed in: akonadiconsole (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: akonadiconsole (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: In Progress Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: In Progress Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: In Progress Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released 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/akonadiconsole/+bug/2046844/+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
