Discussion:
Bug#951117: libecore1: .xsession-errors eats all disk space
(too old to reply)
Ross Vandegrift
2020-02-11 22:30:01 UTC
Permalink
Control: severity -1 normal
Control: reassign -1 enlightenment 0.23.1-4
Control: retitle -1 eo logs in .xsession-errors eat all disk space
Package: libecore1
Version: 1.23.3-6
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
it's critical as it eats all disk space causing other programs fail and
lose data.
I haven't seen this, so lowering the priority to normal. Let's try to
figure out the trigger.
I don't know how to reproduce it. It happens after several days of
running enlightenment. (My desktop is always on.)
At the beginning all works fine, and ~/.xsession-errors takes less than
100Kb. But some time later I find it taking all free space (dozen
gigabytes in my case).
How do you start enlightenment? Does your desktop suspend after
inactivity? Do you leave any other EFL apps running?
ERR<32091>:eo ../src/lib/eo/eo.c:2192 efl_data_scope_get() Eo ID 0x4000002d3617 is not a valid object. Current thread: main. This ID has probably been deleted or this was never a valid object ID. (domain=0, current_domain=0, local_domain=0, available_domains=[0 1 ], generation=217, id=b4d, ref=1)
ERR<32091>:eo ../src/lib/eo/eo.c:1814 efl_isa() Eo ID 0x4000002d3617 is not a valid object. Current thread: main. This ID has probably been deleted or this was never a valid object ID. (domain=0, current_domain=0, local_domain=0, available_domains=[0 1 ], generation=217, id=b4d, ref=1)
Does this end if you restart enlightenemnt? (Main -> Enlightenment ->
Restart)
With the previous version of E all worked fine, began to happen with the
update to 0.23.1-4
This bug was opened against libecore1, not enlightenment. I've
reassigned.

Ross
sergio
2020-02-12 12:50:01 UTC
Permalink
Post by Ross Vandegrift
I haven't seen this, so lowering the priority to normal. Let's try to
figure out the trigger.
I'm sure there no trigger, just something fails inside E.
Post by Ross Vandegrift
How do you start enlightenment?
With enlightenment_start in ~/.xsession via xdm.
Post by Ross Vandegrift
Does your desktop suspend after inactivity?
No suspend, noway! I have only xscreensaver and
xorg.conf.d/00-flags.conf that turns off my monitors after 40 minutes of
inactivity.
Post by Ross Vandegrift
Do you leave any other EFL apps running?
I don't use EFL apps at all. Moreover my E settings are very
minimalistic: most modules are disables. I have only system/dbus,
core/notifications, core/settings/panel, core/windows_switcher and all
settings modules.
Post by Ross Vandegrift
Does this end if you restart enlightenemnt? (Main -> Enlightenment ->
Restart)
I don't know even how to check it. I notice this error only when free
space ends, and I must kill / restart x session to release
.xsession-errors file.
Post by Ross Vandegrift
This bug was opened against libecore1, not enlightenment. I've
reassigned.
I was misled efl_ functions.
--
sergio.
sergio
2020-02-16 19:20:02 UTC
Permalink
Post by Ross Vandegrift
Does this end if you restart enlightenemnt? (Main -> Enlightenment ->
Restart)
I've just captured this condition before the end of the free space and
can answer the question: yes, enlightenemnt restart stops this errors.
--
sergio.
Ross Vandegrift
2020-02-17 06:10:01 UTC
Permalink
Post by sergio
Post by Ross Vandegrift
Does this end if you restart enlightenemnt? (Main -> Enlightenment ->
Restart)
I've just captured this condition before the end of the free space and
can answer the question: yes, enlightenemnt restart stops this errors.
Okay great- about how long it was from the time the session started to the time
you saw the log messages?

Thanks,
Ross
sergio
2020-02-20 09:00:01 UTC
Permalink
Post by Ross Vandegrift
Okay great- about how long it was from the time the session started to the time
you saw the log messages?
I'm monitoring .xsession-errors and can't say anything definite.
Sometimes it takes several hours, sometimes I don't see it for a day or
two. Anyway I see no obvious triggers. I have a couple apps runned
permanently and have no idea what it can be.
--
sergio.
Ross Vandegrift
2020-02-21 00:10:01 UTC
Permalink
Post by sergio
Post by Ross Vandegrift
Okay great- about how long it was from the time the session started to the time
you saw the log messages?
I'm monitoring .xsession-errors and can't say anything definite.
Sometimes it takes several hours, sometimes I don't see it for a day or
two. Anyway I see no obvious triggers. I have a couple apps runned
permanently and have no idea what it can be.
Thanks, I've setup a session to stay open and idle for tonight. Let's
see what happens if I let it sit for a while.

Thanks,
Ross
sergio
2020-02-21 08:20:02 UTC
Permalink
Post by Ross Vandegrift
Thanks, I've setup a session to stay open and idle for tonight. Let's
see what happens if I let it sit for a while.
I've just realized that I've another E runned permanently on intel NUC,
there no above errors, but a lot of

ERR<1162>:evas_main ../src/lib/evas/canvas/evas_object_smart.c:145
evas_object_smart_data_get() calling smart object API on non-smart object!

$ ls -l .xsession-errors
554K 2020-02-21 .xsession-errors

$ grep 'ERR<1162>:evas_main
../src/lib/evas/canvas/evas_object_smart.c:145
evas_object_smart_data_get() calling smart object API on non-smart
object!' .xsession-errors | wc -l
3805
--
sergio.
Ross Vandegrift
2020-02-21 17:00:01 UTC
Permalink
Post by sergio
Post by Ross Vandegrift
Thanks, I've setup a session to stay open and idle for tonight. Let's
see what happens if I let it sit for a while.
So far, no results - E logged zero messages overnight while I wasn't
interacting with it.

Which rendering backend do you use? You can check in Settings -> Look
-> Compositor -> Rendering.
Post by sergio
I've just realized that I've another E runned permanently on intel NUC,
there no above errors, but a lot of
ERR<1162>:evas_main ../src/lib/evas/canvas/evas_object_smart.c:145
evas_object_smart_data_get() calling smart object API on non-smart object!
Do you logs contain any backtraces along with these messages? While
investigating this bug, I found these too - they are trigered when
interacting with EFL windows.

When I asked upstream, I was told that there should be a backtrace along
with the message if libunwindsupport was built in. I don't get any
backtrace, but haven't had time to investigate further.

Ross
sergio
2020-02-21 21:50:01 UTC
Permalink
Post by Ross Vandegrift
Which rendering backend do you use?
OpenGL with "Tear-free updates" and "Texture from pixmap" on both hosts.

Swapping method is "Auto" on the first host and "Triple buffered" on NUC
Post by Ross Vandegrift
Post by sergio
I've just realized that I've another E runned permanently on intel NUC,
there no above errors, but a lot of
ERR<1162>:evas_main ../src/lib/evas/canvas/evas_object_smart.c:145
evas_object_smart_data_get() calling smart object API on non-smart object!
Do you logs contain any backtraces along with these messages?
No.
Post by Ross Vandegrift
While investigating this bug, I found these too - they are trigered
when interacting with EFL windows.
The only EFL window I use on both hosts it's right-click favorites menu,
opening it produces no errors. But opening settings gives:

ERR<2144776>:evas_main ../src/lib/evas/canvas/evas_object_smart.c:145
evas_object_smart_data_get() calling smart object API on non-smart object!
ERR<2144776>:evas-gl_x11
../src/modules/evas/engines/gl_x11/evas_engine.c:1967 _native_bind_cb()
eglCreateImage() for Pixmap 0x0x16fbe89 failed: 0x3003

Looks like closing tilix window gives:
ERR<2144776>:evas-gl_x11
../src/modules/evas/engines/gl_x11/evas_engine.c:1967 _native_bind_cb()
eglCreateImage() for Pixmap 0x0x1661d26 failed: 0x3003
but not every time.
--
sergio.
sergio
2020-02-22 10:30:02 UTC
Permalink
Now (2020-02-22 12:10 GMT+3) I just woke up and found that there are no
free scree space due to the same error.

1. The session was started at 2020-02-20 10:50 GMT+3, so it takes about
2 days, moreover host was rebooted before the session start, uprecords
shows 2 days 21 hour (2020-02-19 15:25)

2. This bug is not related with user actions. Before going to sleep
there was no errors records as I monitor .xsession-errors.


GUI apps opened permanently: urxvt, riot-web (electron), GTK3: firefox,
thunderbird, tilix, pavucontrol, deluge, GTK2: liferea.

I have no hourly cron scripts and daily scripst are the same as on NUC,
that doesn't have this error even session there lives longer.

Not sure if this could be the reason, but my desktop has ATI FirePro
2460 with 4 miniDP and 3 monitors connected. (NUC is intel with only one
monitor)
--
sergio.
sergio
2020-02-23 01:10:01 UTC
Permalink
I know how to trigger it:

Alt-Esc, Alt-PgDown, Ctrl-d

Open tilix window, fullscreen it and close. It happens not every time,
but quite often.

ALT + Escape is Launch/Command x-terminal-emulator
ALT + Next is Maximize Fullscreen
x-terminal-emulator is /usr/bin/tilix.wrapper
--
--
sergio.
sergio
2020-02-23 19:40:01 UTC
Permalink
More details:

instead of fullscreening the tilix it can be closed when it's above
another fullscreen window

I'm unable to reproduce it just after session start, but after restart
it reproduces frequently.

So the sequence is:

1. restart enlightment
2. open tilix
3. put tilix above another fullscreen window or fullscreen itself
4. close it
5. repeat the sequence several times untill errors will be massively
printed into ~/.xsession-errors

I've checked this on NUC, and it's reproducable.
--
sergio.
Ross Vandegrift
2020-02-23 22:20:02 UTC
Permalink
Post by sergio
instead of fullscreening the tilix it can be closed when it's above
another fullscreen window
I'm unable to reproduce it just after session start, but after restart
it reproduces frequently.
1. restart enlightment
2. open tilix
3. put tilix above another fullscreen window or fullscreen itself
4. close it
5. repeat the sequence several times untill errors will be massively
printed into ~/.xsession-errors
I've checked this on NUC, and it's reproducable.
Thanks for the details. Unfortunately, I still cannot reproduce this. I've
tried restarting Enlightenment and then opening tilix, making it fullscreen,
and then exiting. Even after two dozen cycles, no constant stream of logs is
triggered.

How do you get a window on top of fullscreened tilix? As soon as I do anything
that would raise another window (Ctrl-Alt-down, Alt-Tab, etc), tilix exits
fullscreen mode.

I've also tried testing with and without fullscreen compositing enabled, it
doesn't seem to make a difference.

Ross
sergio
2020-02-23 23:10:01 UTC
Permalink
Post by Ross Vandegrift
Thanks for the details. Unfortunately, I still cannot reproduce this.
I've
Post by Ross Vandegrift
tried restarting Enlightenment and then opening tilix, making it fullscreen,
and then exiting.
You should be able to reproduce this bug with the config that I've send you
for the next one.
Post by Ross Vandegrift
How do you get a window on top of fullscreened tilix?
Sorry for bad explanation, it should be vice-versa: tilix on top of
another fullscreened window.
Post by Ross Vandegrift
As soon as I do anything that would raise another window
(Ctrl-Alt-down, Alt-Tab, etc), tilix exits fullscreen mode.
My settings:

Windows -> Window Geometry -> Maximization
Policy: Fullscreen
Direction: Both
Manipulation:
Allow manipulation of maximized windows: yes
Allow windows above fullscreen window: yes
--
sergio.
Ross Vandegrift
2020-02-24 06:40:02 UTC
Permalink
Post by Ross Vandegrift
Post by Ross Vandegrift
Thanks for the details. Unfortunately, I still cannot reproduce this.
I've
Post by Ross Vandegrift
tried restarting Enlightenment and then opening tilix, making it
fullscreen,
Post by Ross Vandegrift
and then exiting.
You should be able to reproduce this bug with the config that I've send you
for the next one.
Post by Ross Vandegrift
How do you get a window on top of fullscreened tilix?
Sorry for bad explanation, it should be vice-versa: tilix on top of
another fullscreened window.
Post by Ross Vandegrift
As soon as I do anything that would raise another window
(Ctrl-Alt-down, Alt-Tab, etc), tilix exits fullscreen mode.
Windows -> Window Geometry -> Maximization
Policy: Fullscreen
Direction: Both
Allow manipulation of maximized windows: yes
Allow windows above fullscreen window: yes
I still can't trigger the issue with your configuration. Have you tried with a
fresh E config? IF that doesn't trigger the issue, then I think we just
haven't found the right settings. If it does trigger, there might be something
else different about your system.

Ross
sergio
2020-02-24 11:10:01 UTC
Permalink
Post by Ross Vandegrift
I still can't trigger the issue with your configuration. Have you
tried with a fresh E config?
Just tried, yes, I can trigger it on the clean user profile, with only
one file left:

% cat .xsession
enlightenment_start

Looks like you need to remove the shelf.
Post by Ross Vandegrift
If it does trigger, there might be something else different about your
system.
Have you exactly Maximize Fullscreen'ed? It's not just Fullscreen.

See screenshot attached.
--
sergio.
Ross Vandegrift
2020-02-26 06:20:01 UTC
Permalink
Post by sergio
Just tried, yes, I can trigger it on the clean user profile, with only
% cat .xsession
enlightenment_start
Looks like you need to remove the shelf.
Post by Ross Vandegrift
If it does trigger, there might be something else different about your
system.
Have you exactly Maximize Fullscreen'ed? It's not just Fullscreen.
Now I can trigger the message, but not a nonstop stream. E prints it while
opening and closing tilix, but not otherwise. Moreover, I can only trigger it
in the same session where I do all of the config. After logging out and back
in, the message is not printed. Also, it doesn't happen under Xephyr at all.

Sorry but I don't think I can really help further. Maybe the upstream folks
would be able to track something down.


For the record, the full sequence I came up with is:
0. Install tilix and E.
1. Start a fresh E profile, go through the first run wizard.
2. Delete the default shelf.
3. Open Settings
a. Windows -> Window Geometry -> Maximization
i. Set Policy to Fullscreen
ii. Enable "Allow manipulation of maximized windows"
iii. Enable "Allow windows above fullscreen windows"
iv. OK
b. Input -> Key Bindings
i. Add a binding for Window:State:Maximize Fullscreen
ii. OK
4. Restart Enlightenment from the Enlightenment menu
5. Run tilix and maximize with the key binding from 3.b.i
6. Run tilix and close it immediately by exiting the terminal.

Repeat 6 a few times, eventually it logs this a few times:
ERR<2605>:eo ../src/lib/eo/eo.c:2192 efl_data_scope_get() Eo ID 0x400000098cfa is not a valid object. Current thread: main. This ID has probably been deleted or this was never a valid object ID. (domain=0, current_domain=0, local_domain=0, available_domains=[0 1 ], generation=fa, id=263, ref=1)

Ross
sergio
2020-02-26 23:20:01 UTC
Permalink
Post by Ross Vandegrift
Now I can trigger the message
Great.
Post by Ross Vandegrift
but not a nonstop stream
Indeed.
Post by Ross Vandegrift
E prints it while opening and closing tilix, but not otherwise.
If there are no other windows, closing tilix stops this messages, but in
my session with other windows, closing tilix doesn't help, I need to
close other windows, but not all of them
Post by Ross Vandegrift
Moreover, I can only trigger it in the same session where I do all of
the config.
Sorry, what config?
Post by Ross Vandegrift
After logging out and back in, the message is not printed.
Sure.
Post by Ross Vandegrift
Also, it doesn't happen under Xephyr at all.
I'm not able to reproduce it under Xephyr too.
Post by Ross Vandegrift
Sorry but I don't think I can really help further. Maybe the upstream folks
would be able to track something down.
OK, I'll report this bug on phab.enlightenment.org but really I so tired
of E bugs, that I'm thinking to switch to another WM (possibly tiling
with good float mode support). The only thing stopping me is time I need
for choice and configuration.
--
sergio.
sergio
2020-02-29 12:20:01 UTC
Permalink
https://phab.enlightenment.org/T8621
--
sergio.
Ross Vandegrift
2020-03-01 00:20:01 UTC
Permalink
Control: forwarded -1 https://phab.enlightenment.org/T8621
Control: tags -1 upstream
Post by sergio
Post by Ross Vandegrift
Sorry but I don't think I can really help further. Maybe the upstream
folks
Post by Ross Vandegrift
would be able to track something down.
OK, I'll report this bug on phab.enlightenment.org but really I so tired
of E bugs, that I'm thinking to switch to another WM (possibly tiling
with good float mode support). The only thing stopping me is time I need
for choice and configuration.
Thanks for that. Sorry that you've had issues with your use-cases.

I still can't seem to trigger this like you can, but I was able to get some
backtraces today. I'll post these to the phab as well.

ERR<36232>:eo ../src/lib/eo/eo.c:2192 efl_data_scope_get() Eo ID 0x4000003d1edf is not a valid object. Current thread: main. This ID has probably been deleted or this was never a valid object ID. (domain=0, current_domain=0, local_domain=0, available_domains=[0 1 ], generation=2df, id=f47, ref=1)

/usr/lib/x86_64-linux-gnu/libeina.so.1 | ./obj-x86_64-linux-gnu/../src/lib/eina/eina_log.c : 2054 @ eina_log_print_cb_stderr.part.0()
/usr/lib/x86_64-linux-gnu/libeina.so.1 | ./obj-x86_64-linux-gnu/../src/lib/eina/eina_log.c : 1456 @ eina_log_print_unlocked()
/usr/lib/x86_64-linux-gnu/libeina.so.1 | ./obj-x86_64-linux-gnu/../src/lib/eina/eina_log.c : 2259 @ eina_log_print()
/usr/lib/x86_64-linux-gnu/libeo.so.1 | ??/?? : 2259 @ _eo_obj_pointer_get()
/usr/lib/x86_64-linux-gnu/libeo.so.1 | ../src/lib/eo/eo.c : 2192 @ efl_data_scope_get()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/ecore_exe.c : 218 @ ecore_exe_pid_get()
/usr/bin/enlightenment| ../src/bin/e_exec.c : 814 @ _e_exec_startup_id_pid_find()
/usr/lib/x86_64-linux-gnu/libeina.so.1 | ./obj-x86_64-linux-gnu/../src/lib/eina/eina_iterator.c: 150 @ eina_iterator_foreach()
/usr/lib/x86_64-linux-gnu/libeina.so.1 | ./obj-x86_64-linux-gnu/../src/lib/eina/eina_hash.c : 1241 @ eina_hash_foreach()
/usr/bin/enlightenment| ../src/bin/e_exec.c : 298 @ e_exec_startup_id_pid_instance_find()
/usr/bin/enlightenment| ../src/bin/e_client.c : 2202 @ _e_client_eval()
/usr/bin/enlightenment| ../src/bin/e_client.c : 2540 @ e_client_idler_before()
/usr/bin/enlightenment| ../src/bin/e_main.c : 1810 @ _e_main_cb_idle_before()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/ecore_idler.c : 35 @ _ecore_factorized_idle_process()
/usr/lib/x86_64-linux-gnu/libeo.so.1 | ??/?? : 35 @ _event_callback_call()
/usr/lib/x86_64-linux-gnu/libeo.so.1 | ??/?? : 35 @ efl_event_callback_call()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/ecore_main.c : 2413 @ _ecore_main_loop_iterate_internal()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/ecore_main.c : 1198 @ _ecore_main_loop_begin()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/efl_loop.c : 58 @ _efl_loop_begin()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/src/lib/ecore/efl_loop.eo.c : 28 @ efl_loop_begin()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/ecore_main.c : 1285 @ ecore_main_loop_begin()
/usr/bin/enlightenment| ../src/bin/e_main.c : 1100 @ main()
/lib/x86_64-linux-gnu/libc.so.6 | /build/glibc-TrjWJf/glibc-2.29/csu/../csu/libc-start.c : 342 @ __libc_start_main()
/usr/bin/enlightenment| ??/?? : 342 @ _start()



ERR<36232>:eo ../src/lib/eo/eo.c:1814 efl_isa() Eo ID 0x4000003d1edf is not a valid object. Current thread: main. This ID has probably been deleted or this was never a valid object ID. (domain=0, current_domain=0, local_domain=0, available_domains=[0 1 ], generation=2df, id=f47, ref=1)

/usr/lib/x86_64-linux-gnu/libeina.so.1 | ./obj-x86_64-linux-gnu/../src/lib/eina/eina_log.c : 2054 @ eina_log_print_cb_stderr.part.0()
/usr/lib/x86_64-linux-gnu/libeina.so.1 | ./obj-x86_64-linux-gnu/../src/lib/eina/eina_log.c : 1456 @ eina_log_print_unlocked()
/usr/lib/x86_64-linux-gnu/libeina.so.1 | ./obj-x86_64-linux-gnu/../src/lib/eina/eina_log.c : 2259 @ eina_log_print()
/usr/lib/x86_64-linux-gnu/libeo.so.1 | ??/?? : 2259 @ _eo_obj_pointer_get()
/usr/lib/x86_64-linux-gnu/libeo.so.1 | ../src/lib/eo/eo.c : 1814 @ efl_isa()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/ecore_exe.c : 219 @ ecore_exe_pid_get()
/usr/bin/enlightenment| ../src/bin/e_exec.c : 814 @ _e_exec_startup_id_pid_find()
/usr/lib/x86_64-linux-gnu/libeina.so.1 | ./obj-x86_64-linux-gnu/../src/lib/eina/eina_iterator.c: 150 @ eina_iterator_foreach()
/usr/lib/x86_64-linux-gnu/libeina.so.1 | ./obj-x86_64-linux-gnu/../src/lib/eina/eina_hash.c : 1241 @ eina_hash_foreach()
/usr/bin/enlightenment| ../src/bin/e_exec.c : 298 @ e_exec_startup_id_pid_instance_find()
/usr/bin/enlightenment| ../src/bin/e_client.c : 2202 @ _e_client_eval()
/usr/bin/enlightenment| ../src/bin/e_client.c : 2540 @ e_client_idler_before()
/usr/bin/enlightenment| ../src/bin/e_main.c : 1810 @ _e_main_cb_idle_before()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/ecore_idler.c : 35 @ _ecore_factorized_idle_process()
/usr/lib/x86_64-linux-gnu/libeo.so.1 | ??/?? : 35 @ _event_callback_call()
/usr/lib/x86_64-linux-gnu/libeo.so.1 | ??/?? : 35 @ efl_event_callback_call()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/ecore_main.c : 2413 @ _ecore_main_loop_iterate_internal()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/ecore_main.c : 1198 @ _ecore_main_loop_begin()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/efl_loop.c : 58 @ _efl_loop_begin()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/src/lib/ecore/efl_loop.eo.c : 28 @ efl_loop_begin()
/usr/lib/x86_64-linux-gnu/libecore.so.1| ./obj-x86_64-linux-gnu/../src/lib/ecore/ecore_main.c : 1285 @ ecore_main_loop_begin()
/usr/bin/enlightenment| ../src/bin/e_main.c : 1100 @ main()
/lib/x86_64-linux-gnu/libc.so.6 | /build/glibc-TrjWJf/glibc-2.29/csu/../csu/libc-start.c : 342 @ __libc_start_main()
/usr/bin/enlightenment| ??/?? : 342 @ _start()

Ross
Adrian Immanuel Kiess
2020-04-29 09:30:02 UTC
Permalink
Package: enlightenment
Version: 0.23.1-5
Followup-For: Bug #951117

Dear Maintainer,

* What led up to the situation?
Upgrading E17
* What was the outcome of this action?
The logfiles (syslog, systemd logs) get flooded and up to 20 Gigabyte
large per day
* What outcome did you expect instead?
No error messages in syslog and systemd logs

currently in Debian/testing the logfiles getting flooded with the following
error using the current E17 desktop from Debian/testing:

Apr 29 11:09:42 g6 /usr/libexec/gdm-x-session[5217]: ERR<5217>:eo
../src/lib/eo/eo.c:1814 efl_isa() Eo ID 0x40000030fb46 is not a valid object.
Current thread: main. This ID has probably been deleted or this was never a
valid object ID. (domain=0, current_domain=0, local_domain=0,
available_domains=[0 1 ], generation=346, id=c3e, ref=1)
Apr 29 11:09:42 g6 /usr/libexec/gdm-x-session[5217]: ERR<5217>:eo
../src/lib/eo/eo.c:2192 efl_data_scope_get() Eo ID 0x40000030fb46 is not a
valid object. Current thread: main. This ID has probably been deleted or this
was never a valid object ID. (domain=0, current_domain=0, local_domain=0,
available_domains=[0 1 ], generation=346, id=c3e, ref=1)
Apr 29 11:09:42 g6 /usr/libexec/gdm-x-session[5217]: ERR<5217>:eo
../src/lib/eo/eo.c:1814 efl_isa() Eo ID 0x40000030fb46 is not a valid object.
Current thread: main. This ID has probably been deleted or this was never a
valid object ID. (domain=0, current_domain=0, local_domain=0,
available_domains=[0 1 ], generation=346, id=c3e, ref=1)
Apr 29 11:09:42 g6 /usr/libexec/gdm-x-session[5217]: ERR<5217>:eo
../src/lib/eo/eo.c:2192 efl_data_scope_get() Eo ID 0x40000030fb46 is not a
valid object. Current thread: main. This ID has probably been deleted or this
was never a valid object ID. (domain=0, current_domain=0, local_domain=0,
available_domains=[0 1 ], generation=346, id=c3e, ref=1)
Apr 29 11:09:42 g6 /usr/libexec/gdm-x-session[5217]: ERR<5217>:eo
../src/lib/eo/eo.c:1814 efl_isa() Eo ID 0x40000030fb46 is not a valid object.
Current thread: main. This ID has probably been deleted or this was never a
valid object ID. (domain=0, current_domain=0, local_domain=0,
available_domains=[0 1 ], generation=346, id=c3e, ref=1)
Apr 29 11:09:42 g6 /usr/libexec/gdm-x-session[5217]: ERR<5217>:eo
../src/lib/eo/eo.c:2192 efl_data_scope_get() Eo ID 0x40000030fb46 is not a
valid object. Current thread: main. This ID has probably been deleted or this
was never a valid object ID. (domain=0, current_domain=0, local_domain=0,
available_domains=[0 1 ], generation=346, id=c3e, ref=1)
Apr 29 11:09:42 g6 /usr/libexec/gdm-x-session[5217]: ERR<5217>:eo
../src/lib/eo/eo.c:1814 efl_isa() Eo ID 0x40000030fb46 is not a valid object.
Current thread: main. This ID has probably been deleted or this was never a
valid object ID. (domain=0, current_domain=0, local_domain=0,
available_domains=[0 1 ], generation=346, id=c3e, ref=1)
... and so on.

The log files get up to 20 Gigabyte large per day because of this happening.
The only difference here is that I don't get this error messages logged to
.xsession-errors but to /var/log/syslog and journalctl.

I can reproduce this bug reported here before.

Is there any workaround known for this or an bug fix on it's way?

Thank you very much for you're kind attention.

Sincerely,

Adrian Kiess



-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.5.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages enlightenment depends on:
ii dbus-user-session [default-dbus-session-bus] 1.12.16-2
ii dbus-x11 [dbus-session-bus] 1.12.16-2
ii enlightenment-data 0.23.1-5
ii libasound2 1.2.2-2.1
ii libbluetooth3 5.50-1.2
ii libc6 2.30-4
ii libecore-con1 1.23.3-8
ii libecore-drm2-1 1.23.3-8
ii libecore-evas1 1.23.3-8
ii libecore-file1 1.23.3-8
ii libecore-input1 1.23.3-8
ii libecore-ipc1 1.23.3-8
ii libecore-wl2-1 1.23.3-8
ii libecore-x1 1.23.3-8
ii libecore1 1.23.3-8
ii libedje-bin 1.23.3-8
ii libedje1 1.23.3-8
ii libeet1 1.23.3-8
ii libeeze1 1.23.3-8
ii libefreet-bin 1.23.3-8
ii libefreet1a 1.23.3-8
ii libeina1a 1.23.3-8
ii libeio1 1.23.3-8
ii libelementary1 1.23.3-8
ii libelput1 1.23.3-8
ii libemile1 1.23.3-8
ii libemotion1 1.23.3-8
ii libevas1 1.23.3-8
ii libevas1-engines-drm 1.23.3-8
ii libevas1-engines-wayland 1.23.3-8
ii libevas1-engines-x 1.23.3-8
ii libpam0g 1.3.1-5
ii libpulse0 13.0-5
ii libuuid1 2.34-0.1
ii libwayland-client0 1.18.0-1
ii libwayland-server0 1.18.0-1
ii libxcb-keysyms1 0.4.0-1+b2
ii libxcb-shape0 1.14-2
ii libxcb1 1.14-2
ii libxkbcommon0 0.10.0-1

Versions of packages enlightenment recommends:
ii acpid 1:2.0.32-1
ii bc 1.07.1-2+b2
ii bluez 5.50-1.2
ii deepin-terminal [x-terminal-emulator] 5.0.0+ds1-2
ii eterm [x-terminal-emulator] 0.9.6-6
ii gnome-terminal [x-terminal-emulator] 3.36.1.1-3
ii libevas-loaders 1.23.3-8
ii mate-terminal [x-terminal-emulator] 1.24.0-3
ii mrxvt [x-terminal-emulator] 0.5.4-2
ii packagekit 1.1.13-2+b1
ii rxvt-unicode [x-terminal-emulator] 9.22-6+b2
ii terminology [x-terminal-emulator] 1.6.0-2
ii tilix [x-terminal-emulator] 1.9.3-4+b1
ii udisks2 2.8.4-1
ii xfce4-terminal [x-terminal-emulator] 0.8.9.2-1
ii xterm [x-terminal-emulator] 353-1

Versions of packages enlightenment suggests:
ii gdb 9.1-3

-- no debconf information
Ross Vandegrift
2020-05-01 06:00:02 UTC
Permalink
Post by Adrian Immanuel Kiess
The log files get up to 20 Gigabyte large per day because of this happening.
The only difference here is that I don't get this error messages logged to
.xsession-errors but to /var/log/syslog and journalctl.
I can reproduce this bug reported here before.
Is there any workaround known for this or an bug fix on it's way?
Upstream has made some changes to make logging quieter, it'll be available in
E24. It should be available before too long - EFL1.24 is just out, and E24 is
scheduled for soon after.

Ross
Adrian Immanuel Kieß
2020-05-01 08:30:01 UTC
Permalink
Dear Ross,

thank you very much for your reply.

I'd then wait for Enlightenment v24 coming into Debian/testing.

Sincerely,

Adrian Kieß
Post by Ross Vandegrift
Post by Adrian Immanuel Kiess
The log files get up to 20 Gigabyte large per day because of this happening.
The only difference here is that I don't get this error messages logged to
.xsession-errors but to /var/log/syslog and journalctl.
I can reproduce this bug reported here before.
Is there any workaround known for this or an bug fix on it's way?
Upstream has made some changes to make logging quieter, it'll be available in
E24. It should be available before too long - EFL1.24 is just out, and E24 is
scheduled for soon after.
Ross
--
With many greetings from Leipzig, Germany.
Adrian Immanuel Kieß

Gothaer Straße 34
D-04155 Leipzig

Administrator & programmer
UNIX ∧ Perl ∧ Java ∧ LaTeX

📪 — < ***@kiess.onl >

--SYSTEM--
echo "Your fortune cookie: " && /usr/games/fortune -c -s de
Post by Ross Vandegrift
(zitate) % Sorgen sind wie Babies: Je mehr man sie hätschelt, desto besser gedeihen sie. -- Helmut Qualtinger
echo "g6.lan.dac uptime: " && /usr/bin/uptime
Post by Ross Vandegrift
10:07:22 up 2 days, 6:23, 1 user, load average: 1,53, 1,70, 1,73
Loading...