Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 654388 - mail-client/evolution - segmentation fault in libglib-2.0.so.0.5200.3
Summary: mail-client/evolution - segmentation fault in libglib-2.0.so.0.5200.3
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-30 05:59 UTC by Paul Osmialowski
Modified: 2018-09-09 18:09 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.info,18.53 KB, text/plain)
2018-04-30 06:01 UTC, Paul Osmialowski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Osmialowski 2018-04-30 05:59:59 UTC
mail-client/evolution-3.24.6:2.0: segfault while I was reading email messages. Reporting just in case. Unfortunately, not much of information from this (e.g. I didn't start it in the console so stdout/stderr is lost), the only trace I could find was in kernel 'dmesg':
evolution[5743]: segfault at a ip 00007f87498ae87b sp 00007fffa3fec9a0 error 4 in libglib-2.0.so.0.5200.3[7f8749844000+112000]

Reproducible: Didn't try

Steps to Reproduce:
So far it happened once.
Actual Results:  
segfault

Expected Results:  
no segfault

So far, after restarting it, it still works.
Comment 1 Paul Osmialowski 2018-04-30 06:01:02 UTC
Created attachment 528988 [details]
emerge --info
Comment 2 Paul Osmialowski 2018-04-30 06:05:20 UTC
[ebuild   R    ] dev-libs/glib-2.52.3:2::gentoo  USE="dbus (mime) systemtap utils xattr -debug (-fam) (-selinux) -static-libs {-test}" ABI_X86="32 (64) (-x32)" PYTHON_TARGETS="python2_7" 0 KiB
[ebuild   R    ] mail-client/evolution-3.24.6:2.0::gentoo  USE="archive bogofilter crypt geolocation highlight ldap spamassassin spell ssl weather -ytnef" 0 KiB
Comment 3 Paul Osmialowski 2018-07-30 08:01:04 UTC
Happened again today, under a heavy load caused by gentoo system being updated at the same time.
Such a thing found in dmesg:

[12846.799554] CPU2: Package temperature above threshold, cpu clock throttled (total events = 1104631)
[12846.799555] CPU5: Package temperature above threshold, cpu clock throttled (total events = 1104631)
[12846.799556] CPU4: Package temperature above threshold, cpu clock throttled (total events = 1104631)
[12846.799557] CPU7: Package temperature above threshold, cpu clock throttled (total events = 1104631)
[12919.475191] evolution[16130]: segfault at 1c ip 00007f857146288f sp 00007ffd21842690 error 4 in libevolution-mail.so[7f85713df000+101000]
[13146.809579] CPU0: Package temperature/speed normal
[13146.809580] CPU1: Package temperature/speed normal
[13146.809582] CPU2: Package temperature/speed normal
[13146.809583] CPU7: Package temperature/speed normal
[13146.809584] CPU3: Package temperature/speed normal
[13146.809585] CPU5: Package temperature/speed normal
[13146.809586] CPU6: Package temperature/speed normal
[13146.809586] CPU4: Package temperature/speed normal
Comment 4 Mart Raudsepp gentoo-dev 2018-07-30 08:16:38 UTC
Is there a backtrace available in coredumpctl perhaps? If using systemd.
Comment 5 Paul Osmialowski 2018-09-03 09:15:11 UTC
Evolution crashed again and again system was heavily loaded at that moment.

[10775.077601] evolution[5661]: segfault at 1c ip 00007f3a7922b88f sp 00007fff495f4670 error 4 in libevolution-mail.so[7f3a791a8000+101000]

$ coredumpctl -1 gdb
...
Core was generated by `/usr/bin/evolution'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f3a7922b88f in ?? () from /usr/lib64/evolution/libevolution-mail.so
[Current thread is 1 (Thread 0x7f3ac7839a40 (LWP 5661))]
(gdb) bt
#0  0x00007f3a7922b88f in ?? () from /usr/lib64/evolution/libevolution-mail.so
#1  0x00007f3ac5d67f25 in g_closure_invoke () from /usr/lib64/libgobject-2.0.so.0
#2  0x00007f3ac5d79f52 in ?? () from /usr/lib64/libgobject-2.0.so.0
#3  0x00007f3ac5d82b9f in g_signal_emit_valist () from /usr/lib64/libgobject-2.0.so.0
#4  0x00007f3ac5d82f7f in g_signal_emit () from /usr/lib64/libgobject-2.0.so.0
#5  0x00007f3ac3a3f595 in ?? () from /usr/lib64/libwebkit2gtk-4.0.so.37
#6  0x00007f3ac3a24d37 in ?? () from /usr/lib64/libwebkit2gtk-4.0.so.37
#7  0x00007f3ac379fb3d in ?? () from /usr/lib64/libwebkit2gtk-4.0.so.37
#8  0x00007f3ac397c004 in ?? () from /usr/lib64/libwebkit2gtk-4.0.so.37
#9  0x00007f3ac397177c in ?? () from /usr/lib64/libwebkit2gtk-4.0.so.37
#10 0x00007f3ac36f0109 in ?? () from /usr/lib64/libwebkit2gtk-4.0.so.37
#11 0x00007f3ac37d4bc2 in ?? () from /usr/lib64/libwebkit2gtk-4.0.so.37
#12 0x00007f3ac36ebb4b in ?? () from /usr/lib64/libwebkit2gtk-4.0.so.37
#13 0x00007f3ac36ec818 in ?? () from /usr/lib64/libwebkit2gtk-4.0.so.37
#14 0x00007f3abba4f7cf in WTF::RunLoop::performWork() () from /usr/lib64/libjavascriptcoregtk-4.0.so.18
#15 0x00007f3abba784a9 in ?? () from /usr/lib64/libjavascriptcoregtk-4.0.so.18
#16 0x00007f3ac5a8e3d2 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#17 0x00007f3ac5a8e750 in ?? () from /usr/lib64/libglib-2.0.so.0
#18 0x00007f3ac5a8ea72 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#19 0x00007f3ac6578fe5 in gtk_main () from /usr/lib64/libgtk-3.so.0
#20 0x000055b30bf150fd in main ()
(gdb)
Comment 6 Mart Raudsepp gentoo-dev 2018-09-09 18:09:08 UTC
I suppose evolution-3.26.6 doesn't help here either? And maybe newer webkit-gtk, though the very newest still needs to be bumped to