Description of problem: Crash happened when I make call in Telegram Version-Release number of selected component: gnome-shell-45~rc-2.fc40 Additional info: reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=0e3561501c164684900f15783dd8bae0;i=131b4e;b=307f4bff8ba1492cbb772b60d12ba7f1;m=6a1c489;t=6053f49c9162d;x=446b4837637bb942 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.6.0-0.rc1.14.fc40.x86_64+debug package: gnome-shell-45~rc-2.fc40 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-45~rc-2.fc40.x86_64 (Fedora Project) 1694111593 backtrace_rating: 4 crash_function: meta_surface_actor_is_effectively_obscured comment: Crash happened when I make call in Telegram Truncated backtrace: Thread no. 1 (37 frames) #0 meta_surface_actor_is_effectively_obscured at ../src/compositor/meta-surface-actor.c:468 #1 update_inhibitation at ../src/wayland/meta-wayland-idle-inhibit.c:147 #2 inhibitor_proxy_completed at ../src/wayland/meta-wayland-idle-inhibit.c:234 #3 g_task_return_now at ../gio/gtask.c:1371 #4 g_task_return at ../gio/gtask.c:1440 #6 init_second_async_cb at ../gio/gdbusproxy.c:1771 #7 g_task_return_now at ../gio/gtask.c:1371 #8 g_task_return at ../gio/gtask.c:1440 #10 async_init_get_all_cb at ../gio/gdbusproxy.c:1399 #11 g_task_return_now at ../gio/gtask.c:1371 #12 g_task_return at ../gio/gtask.c:1440 #14 g_dbus_connection_call_done at ../gio/gdbusconnection.c:5897 #15 g_task_return_now at ../gio/gtask.c:1371 #16 complete_in_idle_cb at ../gio/gtask.c:1385 #19 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284 #20 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349 #22 meta_context_run_main_loop at ../src/core/meta-context.c:514 #23 ffi_call_unix64 at ../src/x86/unix64.S:104 #24 ffi_call_int at ../src/x86/ffi64.c:673 #25 ffi_call at ../src/x86/ffi64.c:710 #26 Gjs::Function::invoke at ../gi/function.cpp:1058 #27 Gjs::Function::call at ../gi/function.cpp:1236 #28 CallJSNative at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/Interpreter.cpp:486 #29 js::InternalCallOrConstruct at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/Interpreter.cpp:566 #30 InternalCall at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/Interpreter.cpp:647 #31 js::CallFromStack at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/Interpreter.cpp:652 #32 js::Interpret at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/Interpreter.cpp:3395 #33 MaybeEnterInterpreterTrampoline at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/Interpreter.cpp:400 #34 js::RunScript at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/Interpreter.cpp:458 #35 js::InternalCallOrConstruct at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/Interpreter.cpp:612 #36 InternalCall at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/Interpreter.cpp:647 #37 js::Call at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/Interpreter.cpp:679 #38 JS::Call at /usr/src/debug/mozjs115-115.2.0-1.fc40.x86_64/vm/CallAndConstruct.cpp:117 #40 GjsContextPrivate::run_main_loop_hook at ../gjs/context.cpp:1428 #41 GjsContextPrivate::eval_module at ../gjs/context.cpp:1545 #42 gjs_context_eval_module at ../gjs/context.cpp:1324 #43 gjs_context_eval_module_file at ../gjs/context.cpp:1629
Created attachment 1988684 [details] File: proc_pid_status
Created attachment 1988685 [details] File: maps
Created attachment 1988686 [details] File: limits
Created attachment 1988687 [details] File: environ
Created attachment 1988688 [details] File: open_fds
Created attachment 1988689 [details] File: mountinfo
Created attachment 1988690 [details] File: os_info
Created attachment 1988691 [details] File: cpuinfo
Created attachment 1988692 [details] File: core_backtrace
Created attachment 1988693 [details] File: exploitable
Created attachment 1988694 [details] File: var_log_messages
Created attachment 1988695 [details] File: backtrace
❯ ~/Downloads/Telegram/Telegram QPainter::begin: Paint device returned engine == 0, type: 2 QWidget::render: Cannot render with an inactive painter qt.core.qobject.connect: QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*) qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment (Telegram:23701): Gtk-WARNING **: 23:03:21.384: Theme parsing error: <data>:1:0: Expected a valid selector qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment The Wayland connection experienced a fatal error: Protocol error And time to time it even leads to gnome-shell crash. It started after Telegram update to version 4.9.6, last good version of Telegram was 4.9.5
Crash happened when I play video in Telegram reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=0e3561501c164684900f15783dd8bae0;i=131b4e;b=307f4bff8ba1492cbb772b60d12ba7f1;m=6a1c489;t=6053f49c9162d;x=446b4837637bb942 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.6.0-0.rc1.14.fc40.x86_64+debug package: gnome-shell-45~rc-2.fc40 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-45~rc-2.fc40.x86_64 (Fedora Project) 1694111593 backtrace_rating: 4 crash_function: meta_surface_actor_is_effectively_obscured comment: Crash happened when I play video in Telegram
Crash happened when I join to video chat in Telegram reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=0e3561501c164684900f15783dd8bae0;i=131b4e;b=307f4bff8ba1492cbb772b60d12ba7f1;m=6a1c489;t=6053f49c9162d;x=446b4837637bb942 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.6.0-0.rc1.14.fc40.x86_64+debug package: gnome-shell-45~rc-2.fc40 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-45~rc-2.fc40.x86_64 (Fedora Project) 1694111593 backtrace_rating: 4 crash_function: meta_surface_actor_is_effectively_obscured comment: Crash happened when I join to video chat in Telegram
gnome-shell crashed when I join to video chat in Telegram reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=960d3f4efad44b79aebf2d34dd14b9e1;i=52b5bd;b=390993188d7e4741bc4cc2c76a5efb8d;m=44a0cd3;t=605667c4404e3;x=ecb5636af381dc52 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.6.0-0.rc1.20230914gitaed8aee11130.16.fc40.x86_64+debug package: gnome-shell-45~rc-2.fc40 runlevel: N 5 backtrace_rating: 4 crash_function: meta_surface_actor_is_effectively_obscured comment: gnome-shell crashed when I join to video chat in Telegram
gnome-shell crashed when I join to video chat in Telegram reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=960d3f4efad44b79aebf2d34dd14b9e1;i=52b5bd;b=390993188d7e4741bc4cc2c76a5efb8d;m=44a0cd3;t=605667c4404e3;x=ecb5636af381dc52 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.6.0-0.rc1.20230914gitaed8aee11130.16.fc40.x86_64+debug package: gnome-shell-45~rc-2.fc40 runlevel: N 5 comment: gnome-shell crashed when I join to video chat in Telegram backtrace_rating: 4 crash_function: meta_surface_actor_is_effectively_obscured
*** Bug 2239718 has been marked as a duplicate of this bug. ***
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.