Hide Forgot
Description of problem: This error occurs during GNOME session startup, i.e. right after logging in with no other action performed. Version-Release number of selected component: mail-notification-5.4-88.git.9ae8768.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: mail-notification crash_function: _XInternAtom executable: /usr/bin/mail-notification global_pid: 31449 kernel: 4.8.8-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _XInternAtom at IntAtom.c:76 #1 XInternAtom at IntAtom.c:175 #2 egg_tray_icon_constructed at src/eggtrayicon.c:181 #3 g_object_new_internal at gobject.c:1823 #4 g_object_new_valist at gobject.c:2042 #5 GET_NEW_VARG at mn-mail-icon.c:206 #6 mn_mail_icon_new at src/mn-mail-icon.gob:298 #7 mn_shell_init_icon_base at src/mn-shell.gob:361 #8 mn_shell_init_icon at src/mn-shell.gob:382 #9 mn_shell_constructor at src/mn-shell.gob:117
Created attachment 1224852 [details] File: backtrace
Created attachment 1224853 [details] File: cgroup
Created attachment 1224854 [details] File: core_backtrace
Created attachment 1224855 [details] File: dso_list
Created attachment 1224856 [details] File: environ
Created attachment 1224857 [details] File: exploitable
Created attachment 1224858 [details] File: limits
Created attachment 1224859 [details] File: maps
Created attachment 1224860 [details] File: mountinfo
Created attachment 1224861 [details] File: namespaces
Created attachment 1224862 [details] File: open_fds
Created attachment 1224863 [details] File: proc_pid_status
Created attachment 1224864 [details] File: var_log_messages
Same problem on F26 final
Confirm, same problem on F26 final.
Process 6510 (mail-notificati) of user 1000 dumped core. Stack trace of thread 6510: #0 0x00007f761bb13dee _XInternAtom (libX11.so.6) #1 0x00007f761bb1418a XInternAtom (libX11.so.6) #2 0x00005652a9e19c59 egg_tray_icon_constructed (mail-notification) #3 0x00007f761969e670 g_object_new_internal (libgobject-2.0.so.0) #4 0x00007f76196a024d g_object_new_valist (libgobject-2.0.so.0) #5 0x00005652a9e09b38 GET_NEW_VARG.constprop.2 (mail-notification) #6 0x00005652a9e15239 mn_shell_init_icon_base (mail-notification) #7 0x00005652a9e160f9 mn_shell_init_icon (mail-notification) #8 0x00005652a9e161c0 ___constructor (mail-notification) #9 0x00007f761969e2ee g_object_new_internal (libgobject-2.0.so.0) #10 0x00007f76196a024d g_object_new_valist (libgobject-2.0.so.0) #11 0x00005652a9e16608 GET_NEW_VARG.constprop.6 (mail-notification) #12 0x00005652a9e074b3 main (mail-notification) #13 0x00007f76166d850a __libc_start_main (libc.so.6) #14 0x00005652a9e078da _start (mail-notification) Stack trace of thread 6513: #0 0x00007f76167bcacd poll (libc.so.6) #1 0x00007f761b81e569 g_main_context_iterate.isra.25 (libglib-2.0.so.0) #2 0x00007f761b81e902 g_main_loop_run (libglib-2.0.so.0) #3 0x00007f76199a6cb6 gdbus_shared_thread_func (libgio-2.0.so.0) #4 0x00007f761b845536 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f7616a9036d start_thread (libpthread.so.0) #6 0x00007f76167c8bbf __clone (libc.so.6) Stack trace of thread 6511: #0 0x00007f76167bcacd poll (libc.so.6) #1 0x00007f761b81e569 g_main_context_iterate.isra.25 (libglib-2.0.so.0) #2 0x00007f761b81e67c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f7604be4f3d dconf_gdbus_worker_thread (libdconfsettings.so) #4 0x00007f761b845536 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f7616a9036d start_thread (libpthread.so.0) #6 0x00007f76167c8bbf __clone (libc.so.6) Stack trace of thread 6512: #0 0x00007f76167bcacd poll (libc.so.6) #1 0x00007f761b81e569 g_main_context_iterate.isra.25 (libglib-2.0.so.0) #2 0x00007f761b81e67c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f761b81e6c1 glib_worker_main (libglib-2.0.so.0) #4 0x00007f761b845536 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f7616a9036d start_thread (libpthread.so.0) #6 0x00007f76167c8bbf __clone (libc.so.6)
It's because they do X11 calls in a Wayland session. Running "GNOME on Xorg" doesn't exhibit the issue.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.