[Bug 956120] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
This bug has been closed for 6 years so probably shouldn't be recycled. If you're experiencing a similar crash in 23.04 then please report it by running: ubuntu-bug /var/crash/YOURFILE.crash -- 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/956120 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/956120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998267] Re: glib not aware of snap confinement
Hello Robert, or anyone else affected, Accepted glib2.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.72.4-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib2.0 (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015264] Re: gnome-shell
Thanks for the bug report. Please explain what kind of problem you are experiencing. -- 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/2015264 Title: gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774053] Re: Missing characters in gnome-shell after lock screen
If your primary GPU is Nvidia then bug 1876632 is more likely your issue. -- 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/1774053 Title: Missing characters in gnome-shell after lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1774053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 956120] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
It also affects Ubuntu 23.04 -- 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/956120 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/956120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976]
*** Bug 1825991 has been marked as a duplicate of this bug. *** -- 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/1987976 Title: firefox black window To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012287] Re: GNOME Characters search provider for GNOME Shell 44 crashes
seeing this on Ubuntu 23.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012287 Title: GNOME Characters search provider for GNOME Shell 44 crashes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-characters/+bug/2012287/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
This is still an issue with 22.04.2 LTS. If both dock auto-hide and 200% scaling are enabled, search results can not be clicked. Changing either setting allows clicking. Installed gnome-shell-extension-ubuntu-dock version is 72~ubuntu5.22.04.1 -- 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/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015262] Re: gnome-control-center
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2015262 Title: gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015267] Re: gnome-system-monitor
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: gnome-system-monitor (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/2015267 Title: gnome-system-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2015267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015273] [NEW] Errors in syslog cant update stage views actor because it needs an allocation
Public bug reported: switch from wayland to xorg and error started. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 08:37:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-18 (17 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2015273 Title: Errors in syslog cant update stage views actor because it needs an allocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015267] [NEW] gnome-system-monitor
Public bug reported: gnome-system-monitor fix bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-system-monitor 42.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:25:40 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy wayland-session ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/2015267 Title: gnome-system-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2015267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015262] [NEW] gnome-control-center
Public bug reported: gnome-control-center logs fix ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:21:28 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2015262 Title: gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015264] [NEW] gnome-shell
Public bug reported: gnome-shell fix ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:22:35 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2015264 Title: gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006500] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported()
the fix has been commited upstream now ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2006500 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2006500/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013107] Re: [lunar] GNOME does not display high contrast app icons
It looks like indeed a bug due to the new Icon theme support, in GNOME Shell though. ** Changed in: yaru-theme (Ubuntu) Status: New => Won't Fix -- 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/2013107 Title: [lunar] GNOME does not display high contrast app icons To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2013107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015237] [NEW] evince logs
Public bug reported: evince logs kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 15:49:21 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) KernLog: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy wayland-session ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2015237 Title: evince logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2015237/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
** Changed in: eog Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015230] [NEW] gimp text tool frame item
Public bug reported:
```
Éditeur d’image GIMP 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)
```
> GIMP-CRITIQUE: gimp_text_tool_frame_item: assertion 'GIMP_IS_LAYER
> (text_tool->layer)' failed
Stack trace:
```
# Stack traces obtained from PID 8339 - Thread 8339 #
[New LWP 8342]
[New LWP 8343]
[New LWP 8344]
[New LWP 8345]
[New LWP 8346]
[New LWP 8348]
[New LWP 8441]
[New LWP 13029]
[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=0x7ffcae200590, fd=17) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7ffaa803ee80 (LWP 8339) "gimp-2.10" __GI___libc_read
(nbytes=256, buf=0x7ffcae200590, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7ffaa6bdf640 (LWP 8342) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7ffaa63de640 (LWP 8343) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7ffaa5bdd640 (LWP 8344) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7ffaa4ec5640 (LWP 8345) "gmain" 0x7ffaa8918d7f in
__GI___poll (fds=0x5618e21ec010, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
6Thread 0x7ffa97fff640 (LWP 8346) "gdbus" 0x7ffaa8918d7f in
__GI___poll (fds=0x5618e2205e40, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
7Thread 0x7ffa893ff640 (LWP 8348) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7ffa88bfe640 (LWP 8441) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9Thread 0x7ffa5d365640 (LWP 13029) "pool-gimp-2.10" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 9 (Thread 0x7ffa5d365640 (LWP 13029) "pool-gimp-2.10"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7ffaa8dae6dc in g_cond_wait_until () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7ffaa8d2f3e1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7ffaa8d2f566 in g_async_queue_timeout_pop () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7ffaa8d91759 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7ffaa8d8ea51 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x7ffaa8894b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140723229819216,
3584004385534124782, 140713282393664, 0, 140714546120784, 140723229819568,
-3582531506214264082, -3582153987644316946}, mask_was_saved = 0}}, priv
[Bug 2006500] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported()
In progress upstream: https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/1762 ** Description changed: + https://errors.ubuntu.com/problem/c917df7aa152ef3144e7356e4290c799e31475b3 + gnome-control-center crashed when i try change refresh rate to other value than 60 Hz. Its crash after I tap keep changes ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 7 19:59:50 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-02-07 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) JournalErrors: lut 07 19:59:50 hostname kernel: show_signal_msg: 4 callbacks suppressed ProcCmdline: gnome-control-center SegvAnalysis: - Segfault happened at: 0x55a5f2b496d4:mov(%rdi),%rax - PC (0x55a5f2b496d4) ok - source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x55a5f2b496d4:mov(%rdi),%rax + PC (0x55a5f2b496d4) ok + source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center 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 + ?? () + 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: gnome-control-center crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2333 Importance: Unknown Status: Unknown ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2006500 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2006500/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015054] Re: /usr/bin/gnome-control-center:11:cc_display_config_manager_get_night_light_supported:dialog_update_state:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
*** This bug is a duplicate of bug 2006500 *** https://bugs.launchpad.net/bugs/2006500 ** This bug has been marked a duplicate of bug 2006500 gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2015054 Title: /usr/bin/gnome-control- center:11:cc_display_config_manager_get_night_light_supported:dialog_update_state:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
And from a core file on lunar:
(gdb) bt -full
#0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {11}}
ret =
#1 __pthread_kill_internal (signo=11, threadid=) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at
./nptl/pthread_kill.c:89
#3 0x7f464d03c406 in __GI_raise (sig=sig@entry=11) at
../sysdeps/posix/raise.c:26
ret =
#4 0x56282c4afaea in dump_gjs_stack_on_signal_handler (signo=11) at
../src/main.c:495
sa = {__sigaction_handler = {sa_handler = 0x56282c4af730
, sa_sigaction = 0x56282c4af730
}, sa_mask = {__val = {0 }},
sa_flags = 0, sa_restorer = 0x0}
i =
#5 0x7f464d03c4b0 in () at
/lib/x86_64-linux-gnu/libc.so.6
#6 0x7f464ad8d344 in js::gc::Cell::storeBuffer() const (this=, this=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/Cell.h:357
buffer = 0x0
#7 js::gc::PostWriteBarrierImpl(void*, JSObject*, JSObject*)
(next=, prev=, cellp=) at
/usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:646
buffer = 0x0
#8 js::gc::PostWriteBarrier(js::SavedFrame**, js::SavedFrame*,
js::SavedFrame*) (next=, prev=, vp=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:658
#9 js::InternalBarrierMethods::postBarrier(js::SavedFrame**, js::SavedFrame*, js::SavedFrame*)
(next=, prev=, vp=0x7f4630022da0) at
/usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:350
#10 js::InternalBarrierMethods::postBarrier(js::SavedFrame**, js::SavedFrame*, js::SavedFrame*)
(vp=0x7f4630022da0, prev=, next=) at
/usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:349
#11 0x7f464d91f721 in js::BarrierMethods::postWriteBarrier(JSObject**, JSObject*, JSObject*) (next=0x0,
prev=, vp=0x7f4630022da0) at
/usr/include/mozjs-102/js/RootingAPI.h:795
p = 0x7f4630022da0
#12 JS::Heap::postWriteBarrier(JSObject* const&, JSObject* const&)
(next=, prev=@0x7f4630022da0: 0x1c8a30a483a0,
this=0x7f4630022da0, this=, prev=,
next=)
at /usr/include/mozjs-102/js/RootingAPI.h:376
p = 0x7f4630022da0
#13 JS::Heap::~Heap() (this=0x7f4630022da0, this=) at
/usr/include/mozjs-102/js/RootingAPI.h:338
p = 0x7f4630022da0
#14 mozilla::detail::VectorImpl, 0ul,
js::SystemAllocPolicy, false>::destroy(JS::Heap*,
JS::Heap*) (aEnd=0x7f4630022da8, aBegin=) at
/usr/include/mozjs-102/mozilla/Vector.h:65
p = 0x7f4630022da0
#15 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector()
(this=0x56282d2db9d8, this=) at
/usr/include/mozjs-102/mozilla/Vector.h:901
#16 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector()
(this=0x56282d2db9d8, this=) at
/usr/include/mozjs-102/js/GCVector.h:43
#17 GjsContextPrivate::~GjsContextPrivate() (this=0x56282d2db960,
this=) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gjs/context.cpp:487
#18 0x7f464d9211e3 in gjs_context_finalize(GObject*)
(object=0x56282d2dbae0) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gjs/context.cpp:500
gjs =
#19 0x7f464e02ee4c in g_object_unref (_object=0x56282d2dbae0) at
../../../gobject/gobject.c:3938
weak_locations =
nqueue = 0x56282d8fc5c0
object = 0x56282d2dbae0
old_ref =
__func__ = "g_object_unref"
#20 0x7f464dc2508d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:752
_pp =
_ptr =
#21 0x56282c4af00f in main (argc=, argv=) at
../src/main.c:776
context = 0x56282cd4e780
debug_flags_string = 0x56282d06c7b0
"backtrace-aborts:backtrace-math-errors:backtrace-crashes-all:backtrace-all"
error = 0x0
shell_debug =
ecode = 0
(gdb)
--
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/1974293
Title:
gnome-shell crashed on logout with SIGSEGV in
js::gc::Cell::storeBuffer() from
js::gc::PostWriteBarrierImpl()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1974293/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
Debugging the release binaries in lunar is the only way I can capture
the crash:
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7fd27998d344 in js::gc::Cell::storeBuffer (this=,
this=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/Cell.h:357
357 inline StoreBuffer* Cell::storeBuffer() const { return
chunk()->storeBuffer; }
(gdb) bt
#0 0x7fd27998d344 in js::gc::Cell::storeBuffer() const
(this=, this=)
at /usr/src/mozjs102-102.9.0-1/js/src/gc/Cell.h:357
#1 js::gc::PostWriteBarrierImpl(void*, JSObject*, JSObject*)
(next=, prev=, cellp=)
at /usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:646
#2 js::gc::PostWriteBarrier(js::SavedFrame**, js::SavedFrame*,
js::SavedFrame*)
(next=, prev=, vp=)
at /usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:658
#3 js::InternalBarrierMethods::postBarrier(js::SavedFrame**, js::SavedFrame*, js::SavedFrame*)
(next=, prev=, vp=0x5647cc6bff20)
at /usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:350
#4 js::InternalBarrierMethods::postBarrier(js::SavedFrame**, js::SavedFrame*, js::SavedFrame*)
(vp=0x5647cc6bff20, prev=, next=)
at /usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:349
(gdb) frame 5
No frame at level 5.
(gdb) frame 6
No frame at level 6.
(gdb)
Not sure why I only get 4 frames in gdb.
--
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/1974293
Title:
gnome-shell crashed on logout with SIGSEGV in
js::gc::Cell::storeBuffer() from
js::gc::PostWriteBarrierImpl()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1974293/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Yup, I have seen a few (rare and random this time) crashes when pressing the Activities corner button (or super shortcut key). It indeed restarts quickly after that, but I assumed it was linked to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 Let me know if I can provide any other info or help :) -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
These messages: avril 02 18:51:02 mana gnome-shell[33312]: Failed to create offscreen effect framebuffer: Failed to create an OpenGL framebuffer object avril 02 18:51:02 mana gnome-shell[33312]: Failed to create offscreen effect framebuffer: Failed to create an OpenGL framebuffer object avril 02 18:51:02 mana kernel: gnome-shell[33312]: segfault at 1 ip 7fc6e255ceac sp 7ffd13b5ba70 error 4 in libnvidia-glcore.so.530.41.03[7fc6e1701000+25e5000] may relate to bug 2012225 happening. But when it does the whole shell will crash (and restart quickly, hopefully). So it's possible the entire problem here is bug 2012225 occurring and the new gnome-shell not being able to recover the window decoration state automatically. -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Thanks. I wonder if the new window decorator (mutter-x11-frames) is mistakenly running on the NVIDIA GPU when it should be running on Intel by default. ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
Libva 2.17.0 added support for DRI3: https://github.com/intel/libva/pull/614 so that's in lunar ** No longer affects: libva ** Bug watch added: github.com/intel/libva/issues #79 https://github.com/intel/libva/issues/79 ** Also affects: libva via https://github.com/intel/libva/issues/79 Importance: Unknown Status: Unknown ** Changed in: libva (Ubuntu) Status: Triaged => Fix Released ** No longer affects: mutter (Ubuntu) -- 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/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Output of lspci -k Please note that this happens consistently, it's not random or a rare occurrence. After boot, opening Thunderbird for example makes it lack the title bar background immediately. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+attachment/5660750/+files/lspcik.txt -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Output of journalctl -b0 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+attachment/5660743/+files/journal.txt -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015183] [NEW] Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.c:1192)
Public bug reported: I don't experience crashes but valgrind gnome-shell reports: ==15231== Invalid read of size 8 ==15231==at 0x4D2D599: g_type_check_instance_is_fundamentally_a (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D149EA: g_object_set_data (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x363DCFD9: free_fetch_user_request (act-user-manager.c:1717) ==15231==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4C382AB: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4C28801: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BCE64C: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231== Address 0x3063be20 is 0 bytes inside a block of size 64 free'd ==15231==at 0x484620F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==15231==by 0x4D2C66B: g_type_free_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D1A0A6: g_object_notify (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x363E3519: UnknownInlinedFun (act-user.c:562) ==15231==by 0x363E3519: UnknownInlinedFun (act-user.c:557) ==15231==by 0x363E3519: _act_user_update_from_object_path (act-user.c:1346) ==15231==by 0x363E3C3F: fetch_user_incrementally (act-user-manager.c:1804) ==15231==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4C382AB: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4C28801: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231== Block was alloc'd at ==15231==at 0x4848A13: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==15231==by 0x4DB5550: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7600.1) ==15231==by 0x4D31B7C: g_type_create_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D1920F: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D1A7B7: g_object_new_with_properties (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D1B560: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x363DE5F1: create_new_user (act-user-manager.c:707) ==15231==by 0x363E41D8: act_user_manager_get_user (act-user-manager.c:1896) ==15231==by 0x5DDE8B5: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.2) ==15231==by 0x5DDB34C: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.2) ==15231==by 0x5DDDF32: ffi_call (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.2) ==15231==by 0x4F28BD8: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: accountsservice 22.08.8-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 4 14:29:55 2023 InstallationDate: Installed on 2022-11-28 (126 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Summary changed: - Invalid read of size 8 from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.c:1192) + Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.c:1192) ** Description changed: - I don't experience crashes but Valgrind still reports: + I don't experience crashes but valgrind gnome-shell reports: ==15231== Invalid read of size 8 ==15231==at 0x4D2D599: g_type_check_instance_is_fundamentally_a (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D149EA: g_object_set_data (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by
[Bug 2015181] nautilus crashed with signal 7 in g_main_context_dispatch()
StacktraceTop: nautilus_view_model_get_item_from_file (self=0x55bc174bd047, file=) at ../src/nautilus-view-model.c:392 on_clipboard_contents_received (source_object=, res=, user_data=) at ../src/nautilus-list-base.c:1316 g_task_return_now (task=0x55b94d014ab0) at ../../../gio/gtask.c:1309 complete_in_idle_cb (task=0x55b94d014ab0) at ../../../gio/gtask.c:1323 g_main_dispatch (context=0x55b949b47930) at ../../../glib/gmain.c:3460 ** 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/2015181 Title: nautilus crashed with signal 7 in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2015181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Someone please help us to find the cause of this bug by: 1. Remove all workarounds. 2. Add kernel parameter: drm.debug=0xff 3. Add to /etc/environment: MUTTER_DEBUG=kms 4. Reboot. 5. Reproduce the bug. 6. Run: journalctl -b0 > journal.txt 7. Attach the resulting text file here. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Tags added: dt-469 -- 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/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2004475] Re: Archive type selection drop-down in archive creation window is clipped
** Changed in: nautilus Status: Unknown => Fix Released -- 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/2004475 Title: Archive type selection drop-down in archive creation window is clipped To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2004475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions
** Changed in: mutter Status: Unknown => New -- 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/2012733 Title: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012733/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015181] [NEW] nautilus crashed with signal 7 in g_main_context_dispatch()
Public bug reported: Just started gedit but no recent operations with nautilus. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 07:57:12 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1099, 732)' InstallationDate: Installed on 2023-03-31 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 7 SourcePackage: nautilus StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with signal 7 in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 nautilus-share0.7.5-0.3 python3-nautilus 4.0-1build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash lunar need-amd64-retrace 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/2015181 Title: nautilus crashed with signal 7 in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2015181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
