FS#65494 - [enlightenment] segfaults when going "Offline"
Attached to Project:
Community Packages
Opened by Philippe Bourjac (philippeb) - Friday, 14 February 2020, 09:32 GMT
Last edited by Carsten Haitzler (raster) - Wednesday, 16 June 2021, 08:13 GMT
Opened by Philippe Bourjac (philippeb) - Friday, 14 February 2020, 09:32 GMT
Last edited by Carsten Haitzler (raster) - Wednesday, 16 June 2021, 08:13 GMT
|
Details
Description:
When switched to "Offline" mode, Enlightenment segfaults. Additional info: * package version(s) enlightenment 0.23.1-1 efl 1.23.2-1 connman 1.37-2 * config and/or log files etc. N/A * link to upstream bug report, if any N/A Steps to reproduce: Click on Settings/Modes/Offline in Enlightenment menus, and wait for the Offline mode notification to disappear. This also happens when restarting connman service without switching the Offline mode explicitly. |
This task depends upon
Closed by Carsten Haitzler (raster)
Wednesday, 16 June 2021, 08:13 GMT
Reason for closing: Deferred
Additional comments about closing: will vanish next version upgrade as previous comment
Wednesday, 16 June 2021, 08:13 GMT
Reason for closing: Deferred
Additional comments about closing: will vanish next version upgrade as previous comment
Comment by freswa (frederik) -
Friday, 14 February 2020, 13:26 GMT
Comment by
Philippe Bourjac (philippeb) -
Friday, 14 February 2020, 14:08 GMT
Comment by
Philippe Bourjac (philippeb) -
Monday, 17 February 2020, 10:00 GMT
Comment by
Carsten Haitzler (raster) -
Wednesday, 16 June 2021, 08:13 GMT
Please provide the log including the segfault. Thanks :)
Unfortunately, neither enlightenment nor efl is compiled with
debugging symbols, so here is all that I could get.
In fact, running with Valgrind shows this is caused by the
"Notification" core module which tries to write configuration to
an empty file
($HOME/e/.e/config/profilename/module.notification.cfg.tmp). It
does not raise any error when the module is not loaded.
the bt just says it's in eet... but .. upstream no longer has an
offline mode, so this is moot and will vanish next release, so may
as well close until some other code path has such an issue with
notification and i get fuller backtraces. this is precisely why i
made the efl-git-asan and enlightenment-git-asan packages in aur -
when you have these issues, first try latest git and see if it is
fixed yet or not AND asan gives proper reports valgrind-like but
is usable unlike valgrind (sloooow). so please truy these packages
next time and then report what asan says... perhaps also get a
backtrace too.