Description of problem: After logging out of a "Gnome on Xorg" session, I logged back in as the same user choosing "Gnome Classic" on the greeter settings. The abrt was prompted twice immediately after the desktop loaded after that login. Version-Release number of selected component: evolution-data-server-3.24.5-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx7983x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/7983/2 crash_function: strlen executable: /usr/libexec/evolution-addressbook-factory-subprocess journald_cursor: s=cff41d712355442a99e8cc83e9e19a8b;i=3d7a;b=bf98b4a6a857403c8c661abac67313fe;m=b7b809108;t=557129a84ed26;x=6acbd33727d0b093 kernel: 4.12.5-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:106 #1 g_strdup at gstrfuncs.c:362 #2 schedule_call_in_idle at gdbusnamewatching.c:195 #3 do_call at gdbusnamewatching.c:217 #4 ffi_call_unix64 at ../src/x86/unix64.S:76 #5 ffi_call at ../src/x86/ffi64.c:525 #6 g_cclosure_marshal_generic at gclosure.c:1490 #11 emit_closed_in_idle at gdbusconnection.c:1358 #16 g_main_context_iteration at gmain.c:4033 #17 dconf_gdbus_worker_thread at dconf-gdbus-thread.c:82 Potential duplicate: bug 1220320
Created attachment 1315614 [details] File: backtrace
Created attachment 1315615 [details] File: cgroup
Created attachment 1315616 [details] File: core_backtrace
Created attachment 1315617 [details] File: cpuinfo
Created attachment 1315618 [details] File: dso_list
Created attachment 1315619 [details] File: environ
Created attachment 1315620 [details] File: exploitable
Created attachment 1315621 [details] File: limits
Created attachment 1315622 [details] File: maps
Created attachment 1315623 [details] File: open_fds
Created attachment 1315624 [details] File: proc_pid_status
Created attachment 1315625 [details] File: var_log_messages
Thanks for a bug report. I guess this is related to bug #1340203, the crash even didn't happen in the evolution-data-server code.
*** Bug 1486678 has been marked as a duplicate of this bug. ***
*** Bug 1491050 has been marked as a duplicate of this bug. ***
*** Bug 1493227 has been marked as a duplicate of this bug. ***
Similar problem has been detected: logged into my computer after a fresh boot and received a crash notification reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx1872x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/1872/3 crash_function: strlen executable: /usr/libexec/evolution-calendar-factory-subprocess journald_cursor: s=62f2f79697604d0ebd7dc519de8ed33d;i=4990;b=e59dafdd79bc4df593fea87889f22020;m=2a5fe063;t=559ccd9d564ef;x=9b15e35b8e32088a kernel: 4.12.14-300.fc26.x86_64 package: evolution-data-server-3.24.6-1.fc26 reason: evolution-calendar-factory-subprocess killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1495002 has been marked as a duplicate of this bug. ***
*** Bug 1493951 has been marked as a duplicate of this bug. ***
Similar problem has been detected: It died whilst the machine was idle over the weekend. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx14378x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/14378/2 crash_function: g_type_check_instance executable: /usr/libexec/evolution-addressbook-factory-subprocess journald_cursor: s=32b55581e41f4362a0537a0648a8be00;i=2102c3;b=972a186726a04d2481207d030d5fe549;m=28b4c41451;t=559c6ca890326;x=3b080946af3af291 kernel: 4.12.13-300.fc26.x86_64 package: evolution-data-server-3.24.6-1.fc26 reason: evolution-addressbook-factory-subprocess killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 500
Similar problem has been detected: Occured on gnome session startup following reboot prior to any user post-login action. Evolution had been shut down normally during a previous session reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2644x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/2644/2 crash_function: strlen executable: /usr/libexec/evolution-addressbook-factory-subprocess journald_cursor: s=2371d044360d4afb805caf3bbd2b8363;i=8c2f9;b=7c055e7d68004cae8c6ea43e126f83c4;m=5de59ebaa;t=55a7059fa9208;x=90817510e1b3eee kernel: 4.12.14-300.fc26.x86_64 package: evolution-data-server-3.24.6-1.fc26 reason: evolution-addressbook-factory-subprocess killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 502
*** Bug 1497554 has been marked as a duplicate of this bug. ***
Evolution continues to be usable, however the issue is repeats on gnome session startup following reboot. There appears not to be any SELinux error report. (In reply to Colin Barker from comment #21) > Similar problem has been detected: > > Occured on gnome session startup following reboot prior to any user > post-login action. > Evolution had been shut down normally during a previous session > > reporter: libreport-2.9.1 > backtrace_rating: 4 > cmdline: /usr/libexec/evolution-addressbook-factory-subprocess > --factory local --bus-name > org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2644x2 > --own-path > /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/2644/2 > crash_function: strlen > executable: /usr/libexec/evolution-addressbook-factory-subprocess > journald_cursor: > s=2371d044360d4afb805caf3bbd2b8363;i=8c2f9; > b=7c055e7d68004cae8c6ea43e126f83c4;m=5de59ebaa;t=55a7059fa9208; > x=90817510e1b3eee > kernel: 4.12.14-300.fc26.x86_64 > package: evolution-data-server-3.24.6-1.fc26 > reason: evolution-addressbook-factory-subprocess killed by SIGSEGV > rootdir: / > runlevel: N 5 > type: CCpp > uid: 502
I tried to reproduce this last Friday, without success. It might be my setup is different or something, I do not know. (In reply to Colin Barker from comment #23) > ... repeats on gnome session startup following reboot. I'm sorry, I'm unsure of the above sentence. Does it mean that you reboot the machine and log into the GNOME (on Wayland) session and the evolution-addressbook-factory crashes straight away? The report shows that it's a local address book, thus On This Computer/Personal (or any other address book created under On This Computer). Do you have them filled with contacts? The only reason to have it opened after start, I can think of, is that the address book is marked to be used in the Birthdays & Anniversaries calendar and you have that calendar checked for inclusion for Reminders. Then after log in, the evolution-alarm-notify process is auto-started, it opens the Birthdays & Anniversaries calendar and this opens the address book. You can have eventually opened some other application accessing address books after start, but I would guess you do not have.
Hello, I will try to clarify for you. (In reply to Milan Crha from comment #24) > I tried to reproduce this last Friday, without success. It might be my setup > is different or something, I do not know. > > (In reply to Colin Barker from comment #23) > > ... repeats on gnome session startup following reboot. > > I'm sorry, I'm unsure of the above sentence. Does it mean that you reboot > the machine and log into the GNOME (on Wayland) session and the > evolution-addressbook-factory crashes straight away? Yes I receive a pop-up alert that it has crashed at the same moment the session displays the desktop. The alert allowed me to report the issue to bugzilla. > > The report shows that it's a local address book, thus On This > Computer/Personal (or any other address book created under On This > Computer). Do you have them filled with contacts? The only reason to have it > opened after start, I can think of, is that the address book is marked to be > used in the Birthdays & Anniversaries calendar and you have that calendar > checked for inclusion for Reminders. Then after log in, the > evolution-alarm-notify process is auto-started, it opens the Birthdays & > Anniversaries calendar and this opens the address book. You can have > eventually opened some other application accessing address books after > start, but I would guess you do not have. Yes I do have contacts in my local address book (about 75 in all including two distribution lists one with 35 and the other with only 4 names) and I have a very few calendar reminders set up. One 'All Day' reminder on 28th September, but none on the 30th Sept nor 1st Oct. I do not believe that I am running any other apps to access the address book. I will update here whether this issue is still occuring.
Hello (In reply to Colin Barker from comment #25) > I will update here whether this issue is still occuring. The last couple of restarts the issue has not recurred. I have now today also updated to the latest rpm versions and see no recurrence afterwards. I will update again if it recurrs. Thank you for your help, Milan.
I'm afraid it's just matter of luck that it didn't strike yet/again. Do any of your contacts have set either Birthday or Anniversary dates? When you open the book Properties (in the context menu, when you select and then right-click the book name on the left side of the Contact view), does it have checked "Use in Birthdays & Anniversaries calendar"? When you look into Edit->Preferences->Calendar and Tasks->Reminders tab, is the Contacts/Birthdays & Anniversaries calendar checked at the list of available calendars to be used for Reminders? These things influence whether the book is opened after login (by evolution-alarm-notify). The Birthdays & Anniversaries calendar can be also opened by GNOME Shell, by its calendar server, which fills events in the clock popup.
I'm getting this abrt every night when I close evolution and log out. I use evolution only for email, and have no tasks, contacts, calendar, or memo entries.
You were right of course and it has struck again today. (In reply to Milan Crha from comment #27) > I'm afraid it's just matter of luck that it didn't strike yet/again. > > Do any of your contacts have set either Birthday or Anniversary dates? > > When you open the book Properties (in the context menu, when you select and > then right-click the book name on the left side of the Contact view), does > it have checked "Use in Birthdays & Anniversaries calendar"? Yes for one book. No for the others. > > When you look into Edit->Preferences->Calendar and Tasks->Reminders tab, is > the Contacts/Birthdays & Anniversaries calendar checked at the list of > available calendars to be used for Reminders? Yes it is. > > These things influence whether the book is opened after login (by > evolution-alarm-notify). The Birthdays & Anniversaries calendar can be also > opened by GNOME Shell, by its calendar server, which fills events in the > clock popup. I will turn this off in both places and wait and see if this issue still recurs over a longer period this time.
I somehow managed to reproduce this semi-consistently. From what I see I believe the problem is in glib2, some use-after-free in gdbusnamewatching.c, probably on the GDBusConnection object. I'm investigating this further and I'll let you know when I know more.
Created attachment 1334916 [details] backtrace Okay, so from what I see there is a race condition in on_connection_disconnected(). This function is always called in a dedicated thread. When the factory subprocess closes, it calls g_bus_unown_name(), which also freed the 'client' structure, but that's still used inside the other thread. The attached backtrace proves it. See Thread 1 there, the client_unref() is called with the same address as is user_data of on_connection_disconnected() being in the call of Thread 8.
Created attachment 1334921 [details] proposed patch This change helped me. I'm not able to reproduce the crash with it, but I also didn't notice the conditions which precede to the crash. I created a test build with it included [1], thus you can try whether it'll help also in your environments. The patch still needs a review from glib2 folks, I do not know all the internals involved, this is only a change, which helped me when I've been trying to figure out what's going wrong there. [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=22269615
*** Bug 1499024 has been marked as a duplicate of this bug. ***
*** Bug 1499105 has been marked as a duplicate of this bug. ***
*** Bug 1499220 has been marked as a duplicate of this bug. ***
I just found out [1], which contains an upstream fix for this, which is included in glib2-2.54.0. It would be good to add it into the Fedora 26 as well, because there are too many crashes due to it. [1] https://bugzilla.gnome.org/show_bug.cgi?id=777307
*** Bug 1505441 has been marked as a duplicate of this bug. ***
*** Bug 1505535 has been marked as a duplicate of this bug. ***
Similar problem has been detected: directly after gnome login the problem popped up reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx6028x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/6028/3 crash_function: g_type_check_instance executable: /usr/libexec/evolution-calendar-factory-subprocess journald_cursor: s=f2c7ab90c9cc451785fec610a94e75b1;i=9ee6;b=01ee367809dc4c42bc899112e5519ed3;m=b0c3977f;t=55c7738215cf9;x=7e06cbdbfb10038b kernel: 4.13.9-200.fc26.x86_64 package: evolution-data-server-3.24.7-1.fc26 reason: evolution-calendar-factory-subprocess killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1507956 has been marked as a duplicate of this bug. ***
glib2-2.52.3-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-9d797ffb4b
glib2-2.52.3-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-9d797ffb4b
Similar problem has been detected: After logging out of the gnome desktop session I logged straight back in (as I had logged out by mistake). The alert came up straightaway. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx5809x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/5809/2 crash_function: g_type_check_instance executable: /usr/libexec/evolution-calendar-factory-subprocess journald_cursor: s=1431966bf9c04aa9aa16c21ffe161c56;i=37c44;b=f3833387009d4bf99160dfd45e40293f;m=1d5eb3455;t=55da963506c26;x=845b5681113eaa3d kernel: 4.13.11-200.fc26.x86_64 package: evolution-data-server-3.24.7-1.fc26 reason: evolution-calendar-factory-subprocess killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 502
glib2-2.52.3-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.