[Bug 2018160] Re: gnome-shell crashes when top right panel touched on touchscreen
This bug is closed. Please open a new bug by running: ubuntu-bug mutter and include the log details: Aug 02 01:55:44 connor-83BV gnome-shell[9448]: Received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 11941 error_code 2 request_code 131 (XInputExtension) minor_code 53) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the MUTTER_SYNC environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the meta_x_error() function.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2018160 Title: gnome-shell crashes when top right panel touched on touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2018160] Re: gnome-shell crashes when top right panel touched on touchscreen
This bug also affects me. I just installed 23.04, and touching the power/wifi/combo button causes an almost instantaneous crash of GNOME shell. Here's the error report your instructions generated: https://errors.ubuntu.com/oops/413de504-30f9-11ee-b2c2-fa163e55efd0. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2018160 Title: gnome-shell crashes when top right panel touched on touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2021412] Re: nautilus hang creating a folder
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2021412 Title: nautilus hang creating a folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2021412/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924689] Re: Window border corruption after changing display scale between 100% and 200% in Xorg
> likely to happen at most once ever Come to think of it, most people changing display scale will never encounter the bug at all. Because most systems will get a Wayland session by default and Wayland is not affected. This bug only affects Xorg sessions. So that means some Nvidia systems, some virtual machines, and not much more. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1924689 Title: Window border corruption after changing display scale between 100% and 200% in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924689] Re: Window border corruption after changing display scale between 100% and 200% in Xorg
I agree this is an ugly bug but since it's likely to happen at most once ever (assuming you don't change display scales often), it doesn't qualify for high priority compared to our other work. Still, this is open source and anyone is entitled to try and debug it and offer fixes. It's not "mainly present in Snap apps". It's been known to occur in other (deb) apps from the beginning. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1924689 Title: Window border corruption after changing display scale between 100% and 200% in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029276] Re: Some area on screen on which I am unable to click
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2012388, so it 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. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-appindicator (Ubuntu) ** This bug has been marked a duplicate of bug 2012388 X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2029276 Title: Some area on screen on which I am unable to click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2029276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029276] [NEW] Some area on screen on which I am unable to click
You have been subscribed to a public bug: Some area on screen on which I am unable to click specially on cross button on any application at top right location. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 1 20:52:55 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:17f3] InstallationDate: Installed on 2023-08-01 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Hewlett-Packard HP ProBook 4440s ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-26-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2019 dmi.bios.release: 15.104 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.68 dmi.board.name: 17F3 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.21 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 88.33 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4440s:pvrA1018C1100:rvnHewlett-Packard:rn17F3:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuC1B73PA#UUF: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 4440s dmi.product.sku: C1B73PA#UUF dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 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: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu wayland-session -- Some area on screen on which I am unable to click https://bugs.launchpad.net/bugs/2029276 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029308] [NEW] Crashed in batch fille size reduction
Public bug reported: Using Linux Mint 21.1 Cinnamon, based on Ubuntu Jammy. I was using Gimp's batch processor to reduce the size of 65 photos and it gave me an error message, asking me to submiot a bug report. However, on checking, the batch processing seems to have completed successfully. ``` GNU Image Manipulation Program version 2.10.30 git-describe: GIMP_2_10_30 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 11.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-gcn/usr --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.2.0 (Ubuntu 11.2.0-16ubuntu1) # Libraries # using babl version 0.1.92 (compiled against version 0.1.88) using GEGL version 0.4.34 (compiled against version 0.4.34) using GLib version 2.72.4 (compiled against version 2.71.1) using GdkPixbuf version 2.42.8 (compiled against version 2.42.6) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.50.6 (compiled against version 1.50.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 58433 - Thread 58433 # [New LWP 58435] [New LWP 58436] [New LWP 58437] [New LWP 58438] [New LWP 58439] [New LWP 58440] [New LWP 58441] [New LWP 58442] [New LWP 58443] [New LWP 58444] [New LWP 58445] [New LWP 58446] [New LWP 58447] [New LWP 58448] [New LWP 58449] [New LWP 58450] [New LWP 58451] [New LWP 58452] [New LWP 58453] [New LWP 58454] [New LWP 58455] [New LWP 58456] [New LWP 58606] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___libc_read (nbytes=256, buf=0x7ffca3fd4f90, fd=22) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7faca3e37e80 (LWP 58433) "gimp-2.10" __GI___libc_read (nbytes=256, buf=0x7ffca3fd4f90, fd=22) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7faca354e640 (LWP 58435) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7faca2d4d640 (LWP 58436) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7faca254c640 (LWP 58437) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7faca1d4b640 (LWP 58438) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7faca154a640 (LWP 58439) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7faca0d49640 (LWP 58440) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7fac93fff640 (LWP 58441) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7fac937fe640 (LWP 58442) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 10 Thread 0x7fac92ffd640 (LWP 58443) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 11 Thread 0x7fac927fc640 (LWP 58444) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7fac91ffb640 (LWP 58445) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7fac917fa640 (LWP 58446) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 14 Thread 0x7fac90ff9640 (LWP 58447) "worker" syscall (
[Bug 2029278] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for cpp no debug symbol package found for dbus-user-session no debug symbol package found for debianutils no debug symbol package found for dnsmasq-base no debug symbol package found for fontconfig-config no debug symbol package found for fwupd-signed no debug symbol package found for gir1.2-accountsservice-1.0 no debug symbol package found for gir1.2-adw-1 no debug symbol package found for gir1.2-atk-1.0 no debug symbol package found for gir1.2-atspi-2.0 no debug symbol package found for gir1.2-freedesktop no debug symbol package found for gir1.2-gck-1 no debug symbol package found for gir1.2-gcr-3 no debug symbol package found for gir1.2-gdesktopenums-3.0 no debug symbol package found for gir1.2-gdkpixbuf-2.0 no debug symbol package found for gir1.2-gdm-1.0 no debug symbol package found for gir1.2-geoclue-2.0 no debug symbol package found for gir1.2-glib-2.0 no debug symbol package found for gir1.2-gnomebg-4.0 no debug symbol package found for gir1.2-gnomebluetooth-3.0 no debug symbol package found for gir1.2-gnomedesktop-4.0 no debug symbol package found for gir1.2-graphene-1.0 no debug symbol package found for gir1.2-gstreamer-1.0 no debug symbol package found for gir1.2-gtk-3.0 no debug symbol package found for gir1.2-gtk-4.0 no debug symbol package found for gir1.2-gweather-4.0 no debug symbol package found for gir1.2-harfbuzz-0.0 no debug symbol package found for gir1.2-ibus-1.0 no debug symbol package found for gir1.2-javascriptcoregtk-4.1 no debug symbol package found for gir1.2-json-1.0 no debug symbol package found for gir1.2-mutter-12 no debug symbol package found for gir1.2-nm-1.0 no debug symbol package found for gir1.2-nma4-1.0 no debug symbol package found for gir1.2-packagekitglib-1.0 no debug symbol package found for gir1.2-pango-1.0 no debug symbol package found for gir1.2-polkit-1.0 no debug symbol package found for gir1.2-rsvg-2.0 no debug symbol package found for gir1.2-soup-3.0 no debug symbol package found for gir1.2-upowerglib-1.0 no debug symbol package found for gir1.2-vte-2.91 no debug symbol package found for gir1.2-webkit2-4.1 no debug symbol package found for gnome-menus no debug symbol package found for ipp-usb no debug symbol package found for libavahi-common-data no debug symbol package found for libbolt-16-dev no debug symbol package found for libgtk2.0-bin no debug symbol package found for libjpeg8 no debug symbol package found for libmagic-mgc no debug symbol package found for libperl5.36 no debug symbol package found for libtag1v5 no debug symbol package found for perl no debug symbol package found for perl-base no debug symbol package found for pipewire no debug symbol package found for pipewire-pulse no debug symbol package found for policykit-1 no debug symbol package found for secureboot-db no debug symbol package found for systemd-sysv no debug symbol package found for tcl no debug symbol package found for xserver-xorg no debug symbol package found for xserver-xorg-input-all no debug symbol package found for xserver-xorg-video-all no debug symbol package found for libnvidia-gl-535 no debug symbol package found for libnvidia-gl-525 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2029278/+attachment/5689847/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2029278 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2029278/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029278] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2029278/+attachment/5689861/+files/ThreadStacktrace.txt ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2029278 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2029278/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029278] gnome-shell crashed with SIGSEGV
Stacktrace: #0 0x7fb176890ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffcdc2423e0 StacktraceSource: #0 0x7fb176890ffb in ?? () StacktraceTop: ?? () -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2029278 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2029278/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029278] [NEW] gnome-shell crashed with SIGSEGV
Public bug reported: crashed after login to desktop ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 44.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 1 23:53:35 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-07-08 (24 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.3-1ubuntu1 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7fb176890ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffcdc2423e0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin nordvpn plugdev sudo users separator: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash mantic need-amd64-retrace third-party-packages wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2029278 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2029278/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924689] Re: Window border corruption after changing display scale between 100% and 200% in Xorg
It's more than 2 years after this bug was filed first. Does this mean that there is no interest in fixing the Ubuntu desktop? Is that even a mutter bug? Triaging was seemingly done under false assumptions about the boundaries of the bug. Any hints why this bug is mainly present in Snap apps? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1924689 Title: Window border corruption after changing display scale between 100% and 200% in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029264] Re: nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 2029151 *** https://bugs.launchpad.net/bugs/2029151 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 #2029151, 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/2029264/+attachment/5689775/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2029264/+attachment/5689777/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2029264/+attachment/5689780/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2029264/+attachment/5689781/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2029264/+attachment/5689782/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2029264/+attachment/5689783/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2029264/+attachment/5689784/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 2029151 nautilus crashed with SIGSEGV ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2029264 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2029264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029264] [NEW] nautilus crashed with SIGSEGV
Public bug reported: crash after choosing files on VLC Snap Version ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: nautilus 1:44.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 1 15:47:29 2023 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2023-07-29 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230729) JournalErrors: août 01 15:47:23 hostname gnome-shell[3164]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed août 01 15:47:28 hostname (udev-worker)[32242]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x5646d257f40a: mov0x18(%r12),%rdi PC (0x5646d257f40a) ok source "0x18(%r12)" (0xfeb8) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: usr_lib_nautilus: nautilus-extension-gnome-terminal 3.48.1-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash mantic need-amd64-retrace third-party-packages wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2029264 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2029264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976259] Re: librsvg ftbfs in the jammy release pocket
This bug was fixed in the package librsvg - 2.52.5+dfsg-3ubuntu0.2 --- librsvg (2.52.5+dfsg-3ubuntu0.2) jammy-security; urgency=medium * SECURITY UPDATE: Arbitrary file read when xinclude href has special characters - debian/patches/CVE-2023-38633.patch: validate URLs in include/librsvg/rsvg.h, src/error.rs, src/lib.rs, src/url_resolver.rs, tests/*. - CVE-2023-38633 * Don't fail the build on tests error for i386 (LP: #1976259) -- Marc Deslauriers Fri, 28 Jul 2023 08:55:53 -0400 ** Changed in: librsvg (Ubuntu) Status: Triaged => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-38633 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1976259 Title: librsvg ftbfs in the jammy release pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1976259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882825] Re: Does not save the configuration file under ~/.config/
** Changed in: w3m (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/882825 Title: Does not save the configuration file under ~/.config/ To manage notifications about this bug go to: https://bugs.launchpad.net/gconf/+bug/882825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882825] Re: Does not save the configuration file under ~/.config/
For w3m, discussion on maintainer's repo is here [1]. Still no XDG compliant [2]. [1] https://github.com/tats/w3m/issues/130 [2] https://github.com/tats/w3m/issues/130#issuecomment-1361228346 ** Bug watch added: github.com/tats/w3m/issues #130 https://github.com/tats/w3m/issues/130 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/882825 Title: Does not save the configuration file under ~/.config/ To manage notifications about this bug go to: https://bugs.launchpad.net/gconf/+bug/882825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029216] [NEW] Generating an escrow-packet fails
Public bug reported: https://access.redhat.com/documentation/en- us/red_hat_enterprise_linux/6/html/storage_administration_guide/ch- volumekey Attempting to generate an escrow-packet as documented at the above link fails with the following error: ``` sudo volume_key --save ./luks.img --output ./escrow-packet volume_key: Error opening `./luks.img': Error getting information about volume `./luks.img': Invalid argument ``` The exact same command works on Fedora Workstation 38. To replicate the issue, do the following: - On Ubuntu 22.04 (haven't tested other releases) - Install `volume-key` package - Generate a LUKS encrypted volume ``` # Pre-allocate a 1GB volume sudo fallocate -l 1GB ./luks.img sudo cryptsetup luksFormat ./luks.img # Follow prompts to setup the volume with a passphrase ``` - Try to generate the escrow-packet ``` sudo volume_key --save ./luks.img --output ./escrow-packet ``` ** Affects: volume-key (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to volume-key in Ubuntu. https://bugs.launchpad.net/bugs/2029216 Title: Generating an escrow-packet fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/volume-key/+bug/2029216/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
