[Desktop-packages] [Bug 1833322] Comment bridged from LTC Bugzilla
Now? CPUs are faster; if you disable irqtune, you can observe in /proc/interrupts that various device interrupts are still sent to CPUs other than CPU0, they just don't go ping-ponging around between all of them like they do with irqtune. A big difference compared to the early days, for example for ethernet a lot of the work that was done in the interrupt handler back then, the interrupt handler now does the bare minimum and does the rest of the work with a kernel thread (same for wifi, which tends to be a bit of an interrupt and CPU hog). Meaning the actual interrupts take much less time to run now than they did then. The total CPU time could still add up to more than 1 core can handle if you had, say, 10gbps ethernet. But the kernel threads can be scheduled to any CPU core just like any other thread even if the interrupts are tied to one CPU. -- 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/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
Just for perspective on this, I've used Linux since about 1993 (originally Slackware, then Gentoo, then Ubuntu) and recall manually adding irqtune to my system in the distant past. When irqtune was originally developed, it was common to run XT-PIC, all interrupts were went to CPU 0, period. When one turned on IO-APIC back then, interrupts still went to CPU 0 by default but could be rerouted. This was largely to be able to hit gigabit+ speeds on systems of the time. Now? CPUs are faster, memory is faster, and the interrupt handlers are much more efficient than in the kernel of, say, 15 or 20 years ago. If you disable irqtune, you can observe in /proc/interrupts that various device interrupts are still sent to CPUs other than CPU0, they just don't go ping-ponging around between all of them like they do with irqtune. A big difference compared to the early days, for example for ethernet a lot of the work that was done in the interrupt handler back then, the interrupt handler now does the bare minimum and does the rest of the work with a kernel thread (same for wifi, which tends to be a bit of an interrupt and CPU hog). Meaning the actual interrupts take much less time to run now than they did then. The total CPU time could still add up to more than 1 core can handle if you had, say, 10gbps ethernet (or 1gbps ethernet or wifi on a slower CPU). But the kernel threads can be scheduled to any CPU core just like any other thread even if the interrupts are tied to one CPU.. -- 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/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+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 2054217] [NEW] Settings app in Ubuntu Mantic keeps crashing
Public bug reported: The GNOME settings app in Ubuntu Mantic (23.10, GNOME 45) occasionally keeps crashing when I move around its various sections. At times it even happens consecutively. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu3.1 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: pass CurrentDesktop: ubuntu:GNOME Date: Sun Feb 18 08:05:00 2024 InstallationDate: Installed on 2024-02-16 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2054217 Title: Settings app in Ubuntu Mantic keeps crashing Status in gnome-control-center package in Ubuntu: New Bug description: The GNOME settings app in Ubuntu Mantic (23.10, GNOME 45) occasionally keeps crashing when I move around its various sections. At times it even happens consecutively. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu3.1 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: pass CurrentDesktop: ubuntu:GNOME Date: Sun Feb 18 08:05:00 2024 InstallationDate: Installed on 2024-02-16 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2054217/+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 2054212] [NEW] System starts, but monitor on HDMI has no signal
Public bug reported: I have been running with kernel 6.2 without any problems. However, when the system upgraded to kernel 6.5, the system boots, but the monitor connected via HDMI has no signal. The system seems to think everything is OK, there are no errors in the Xorg log, xrandr shows both displays, so does inxi -Fxxxrz. Both monitors are connected via the AMD Radeon RX 6600 graphics card, the LG using DisplayPort, the Benq using HDMI. The Benq monitor will show "No Signal Detected" when the system boots and I log into the desktop. The LG monitor shows the correct display. The Display app will show both monitors as present, it's just that nothing is actually sent via the cable to the monitor. So the monitor doesn't get any signal. If I connect the Benq via DisplayPort and the LG via HDMI, then the LG shows "No Signal Detected". Comparing the Xorg.0.log files from using kernel 6.2 and 6.5, I don't see any errors or indications why the HDMI output isn't sending data. I've attached a tar.gz file with the 6.2 and 6.5 kernel results for the Xorg.0.log, the output of "inxi -Fxxxrz" and "xrandr -q". My current work around is to boot into kernel 6.2, but I would like to see the new kernel functioning properly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: zfs .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Feb 17 17:09:53 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.50, 6.2.0-39-generic, x86_64: installed virtualbox/6.1.50, 6.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: XFX Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1eae:6505] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c8) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cezanne [1043:8809] InstallationDate: Installed on 2015-08-11 (3112 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-18-generic root=UUID=e6fe56b0-c6a6-48fd-9203-44e7395670df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2604 dmi.board.asset.tag: Default string dmi.board.name: PRIME B550-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2604:bd02/25/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB550-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 jammy ubuntu ** Attachment added: "kernel-6.5_bug-report.tar.gz" https://bugs.launchpad.net/bugs/2054212/+attachment/5746971/+files/kernel-6.5_bug-report.tar.gz -- 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/2054212 Title: System starts, but monitor on HDMI has no signal Status in xorg package in Ubuntu: New Bug description: I have been running with kernel 6.2 without any problems. However, when the system upgraded to kernel 6.5, the system boots, but the monitor connected via HDMI has no signal. The system seems to think everything is OK, there ar
[Desktop-packages] [Bug 2036315] Re: sol takes a long time to start
** Changed in: aisleriot (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2036315 Title: sol takes a long time to start Status in aisleriot package in Ubuntu: Fix Released Bug description: sol takes a long time to start I see a msg: corrado@corrado-n12-mm-0915:~$ sol ;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm ;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: aisleriot 1:3.22.23-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-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 17:01:29 2023 InstallationDate: Installed on 2023-09-15 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2036315/+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 929067] Re: Crash during restore: "assert ropath.index == (), ropath.index"
If you install via pip, be sure to remove the pkg first. Different install locations will cause problems. See https://gitlab.com/duplicity/duplicity. We moved years ago. -- 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 1988643] Re: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1988643 Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: Confirmed Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 02:00:33 2022 Disassembly: => 0x7f4e338e34f0: Cannot access memory at address 0x7f4e338e34f0 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1662228023', '--until=@1662228043'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/ibus-x11 RebootRequiredPkgs: Error: path contained symlinks. SegvAnalysis: Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 0x7f4e338e34f0 PC (0x7f4e338e34f0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 2032900] Re: gsd-xsettings crashed with SIGSEGV in g_closure_invoke()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2032900 Title: gsd-xsettings crashed with SIGSEGV in g_closure_invoke() Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: crashed when change to dark mode ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-settings-daemon 44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 24 15:59:41 2023 Disassembly: => 0x7f5cc9f924b0: Cannot access memory at address 0x7f5cc9f924b0 ExecutablePath: /usr/libexec/gsd-xsettings InstallationDate: Installed on 2023-07-08 (47 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) ProcCmdline: /usr/libexec/gsd-xsettings SegvAnalysis: Segfault happened at: 0x7f5cc9f924b0:Cannot access memory at address 0x7f5cc9f924b0 PC (0x7f5cc9f924b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gsd-xsettings crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin nordvpn plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2032900/+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 2036315] Re: sol takes a long time to start
After last updates which include guile-3.0-libs problem is solved. The following packages will be upgraded: apparmor apt apt-utils dracut-install gnome-sudoku guile-3.0-libs hunspell-en-gb hunspell-en-za hunspell-it hyphen-en-ca hyphen-en-gb hyphen-it inxi iptables libapparmor1 libapt-pkg6.0 libatkmm-1.6-1v5 libbabl-0.1-0 libcap-ng0 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libgc1 libglibmm-2.68-1 libigdgmm12 libinput-bin libinput10 libip4tc2 libip6tc2 libkeyutils1 liblirc-client0 liblwp-protocol-https-perl liburi-perl libuv1 libxtables12 mesa-utils mesa-utils-bin mythes-en-us mythes-it python3-idna python3-markupsafe python3-pexpect 45 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2036315 Title: sol takes a long time to start Status in aisleriot package in Ubuntu: Confirmed Bug description: sol takes a long time to start I see a msg: corrado@corrado-n12-mm-0915:~$ sol ;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm ;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: aisleriot 1:3.22.23-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-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 17:01:29 2023 InstallationDate: Installed on 2023-09-15 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2036315/+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 2054183] Re: nautilus not generating thumbnails anymore
After some digging I found https://github.com/flatpak/flatpak/issues/5462 and alas: sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 makes thumbnail generation work again. -- 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/2054183 Title: nautilus not generating thumbnails anymore Status in nautilus package in Ubuntu: New Bug description: After the upgrade to 24.04, nautilus is not generating thumbnails for new files. Old thumbnails are displayed ok. I cleaned out $HOME/.cache/thumbnails/ and found that only a subdirectory "fail" is being generated. It contains a subdirectory "gnome-thumbnail-factory" which in turn contains lots of PNG files: ece577c54f5ca98e1f7aaa5b4e932aa4.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ee638c64b1c285684412717bf120e295.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ef811735cfb8e69447b5d3a53f361c63.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0b3ab2f77c342daa3579bfcf9c72481.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0ddb101b8342e4b298b4c7121881422.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45.2.1-4ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 08:49:55 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-04-16 (1767 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-02-14 (3 days ago) usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2054183/+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 2054183] Re: nautilus not generating thumbnails anymore
I id some tests, and while root was able to create thumbnails in nautilus, I checked the logs and found: Feb 17 09:20:51 comet kernel: audit: type=1400 audit(1708158051.561:1699): apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=142479 comm="bwrap" requested="userns_create" denied="userns_create" Feb 17 09:20:51 comet kernel: audit: type=1400 audit(1708158051.565:1700): apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=142480 comm="bwrap" requested="userns_create" denied="userns_create" Feb 17 09:20:51 comet kernel: audit: type=1400 audit(1708158051.569:1701): apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=142481 comm="bwrap" requested="userns_create" denied="userns_create" This coincides with me deleting the bogus 1x1 thumbnails an re-entering the folder... ** Bug watch added: github.com/flatpak/flatpak/issues #5462 https://github.com/flatpak/flatpak/issues/5462 -- 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/2054183 Title: nautilus not generating thumbnails anymore Status in nautilus package in Ubuntu: New Bug description: After the upgrade to 24.04, nautilus is not generating thumbnails for new files. Old thumbnails are displayed ok. I cleaned out $HOME/.cache/thumbnails/ and found that only a subdirectory "fail" is being generated. It contains a subdirectory "gnome-thumbnail-factory" which in turn contains lots of PNG files: ece577c54f5ca98e1f7aaa5b4e932aa4.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ee638c64b1c285684412717bf120e295.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ef811735cfb8e69447b5d3a53f361c63.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0b3ab2f77c342daa3579bfcf9c72481.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0ddb101b8342e4b298b4c7121881422.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45.2.1-4ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 08:49:55 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-04-16 (1767 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-02-14 (3 days ago) usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2054183/+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 2054181] Re: Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu
** 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/2054181 Title: Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu Status in xorg package in Ubuntu: New Bug description: Dear Ubuntu Bug Tracking Team, I hope this message finds you well. I am writing to report an issue I have encountered while using Ubuntu. Issue Description: When connecting my BenQ monitor to a Belkin docking station via DisplayPort, Ubuntu fails to detect the monitor. Other monitor connected to same docking station via hdmi is working Thank you for your attention to this matter. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 12:33:13 2024 DistUpgraded: 2022-09-23 16:50:19,545 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nct6687d/20240204-15, 6.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22ac] InstallationDate: Installed on 2020-06-01 (1355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=b6e3b307-fcfb-4b70-ba21-5b72784f279c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-09-23 (511 days ago) dmi.bios.date: 07/17/2023 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: N2SET31W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvrN2SET31W(1.25):bd07/17/2023:br1.25:efr1.6:svnLENOVO:pn20SDCTO1WW:pvrThinkPadX390:rvnLENOVO:rn20SDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SD_BU_Think_FM_ThinkPadX390: dmi.product.family: ThinkPad X390 dmi.product.name: 20SDCTO1WW dmi.product.sku: LENOVO_MT_20SD_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/2054181/+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 2054181] [NEW] Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu
You have been subscribed to a public bug: Dear Ubuntu Bug Tracking Team, I hope this message finds you well. I am writing to report an issue I have encountered while using Ubuntu. Issue Description: When connecting my BenQ monitor to a Belkin docking station via DisplayPort, Ubuntu fails to detect the monitor. Other monitor connected to same docking station via hdmi is working Thank you for your attention to this matter. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 12:33:13 2024 DistUpgraded: 2022-09-23 16:50:19,545 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nct6687d/20240204-15, 6.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22ac] InstallationDate: Installed on 2020-06-01 (1355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=b6e3b307-fcfb-4b70-ba21-5b72784f279c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-09-23 (511 days ago) dmi.bios.date: 07/17/2023 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: N2SET31W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvrN2SET31W(1.25):bd07/17/2023:br1.25:efr1.6:svnLENOVO:pn20SDCTO1WW:pvrThinkPadX390:rvnLENOVO:rn20SDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SD_BU_Think_FM_ThinkPadX390: dmi.product.family: ThinkPad X390 dmi.product.name: 20SDCTO1WW dmi.product.sku: LENOVO_MT_20SD_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 jammy ubuntu wayland-session -- Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu https://bugs.launchpad.net/bugs/2054181 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 2054183] [NEW] nautilus not generating thumbnails anymore
Public bug reported: After the upgrade to 24.04, nautilus is not generating thumbnails for new files. Old thumbnails are displayed ok. I cleaned out $HOME/.cache/thumbnails/ and found that only a subdirectory "fail" is being generated. It contains a subdirectory "gnome-thumbnail-factory" which in turn contains lots of PNG files: ece577c54f5ca98e1f7aaa5b4e932aa4.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ee638c64b1c285684412717bf120e295.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ef811735cfb8e69447b5d3a53f361c63.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0b3ab2f77c342daa3579bfcf9c72481.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0ddb101b8342e4b298b4c7121881422.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45.2.1-4ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 08:49:55 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-04-16 (1767 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-02-14 (3 days ago) usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- 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/2054183 Title: nautilus not generating thumbnails anymore Status in nautilus package in Ubuntu: New Bug description: After the upgrade to 24.04, nautilus is not generating thumbnails for new files. Old thumbnails are displayed ok. I cleaned out $HOME/.cache/thumbnails/ and found that only a subdirectory "fail" is being generated. It contains a subdirectory "gnome-thumbnail-factory" which in turn contains lots of PNG files: ece577c54f5ca98e1f7aaa5b4e932aa4.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ee638c64b1c285684412717bf120e295.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ef811735cfb8e69447b5d3a53f361c63.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0b3ab2f77c342daa3579bfcf9c72481.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0ddb101b8342e4b298b4c7121881422.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45.2.1-4ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 08:49:55 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-04-16 (1767 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-02-14 (3 days ago) usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2054183/+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
