ERR<eo>lib/eo/eo.c:611 in lib/edje/edje_object.eo.c:134: func 'edje_obj_signal_emit': obj_id=0x555f915eb270 is an invalid ref.

[srakitnican]

This messages appears when adjusting volume with a mouse scroll wheel. Using development branch commit 90e5ccb .

May 13 09:01:10 machine /usr/libexec/gdm-x-session[6320]: ERR<eo>lib/eo/eo.c:611 in lib/edje/edje_object.eo.c:134: func 'edje_obj_signal_emit': obj_id=0x555f915eb270 is an invalid ref.
May 13 09:01:10 machine /usr/libexec/gdm-x-session[6320]: ERR<edje>lib/edje/edje_util.c:3968 file /usr/share/enlightenment/data/themes/default.edj, group e/modules/notification/main has a non-fixed part 'notification.swallow.app_icon'. Adding 'fixed: 1 1;' to source EDC may help. Continuing discarding faulty part.

[thewaiter]

Hmm, I am not able to reproduce this. I used the mouse wheel above the mixer gadget icon. Tell me more please.

[rbtylee]

OK I also am unable to duplicate this. But I am sure we should add the 'fixed:1 1;' part to the notification theme. It is present in the enlightenment part of the elementary theme and has been since 2015-06-16 with commit notification: set fixed on app icon to eliminate edje calc error.

Hence I am backporting this: commit 13d064b.

Does this fix the issue?

[srakitnican]

The second message is gone by using 1bb5885, the following message is still present though, but it seems it now appears only when notification pops up, it seems it is no longer updating when adjusting volume.

May 13 16:09:00 machine /usr/libexec/gdm-x-session[11254]: ERR<eo>lib/eo/eo.c:611 in lib/edje/edje_object.eo.c:134: func 'edje_obj_signal_emit': obj_id=0x55f917ce33c0 is an invalid ref.

[srakitnican]

I am also able to reproduce with command notify-send "Test".

[rbtylee]

I am not getting the same error msgs exactly but I can duplicate the notification not always working when the volume is changed. Maybe the error msgs you are getting is a result of using gdm? Never thought about the possibility of different errors using different dms. But I will look for the commit that caused this issue and or a fix. May also play around with different dms...

[srakitnican]

You are right, the message doesn't appear when I start Moksha using startx. I can't reproduce notification not appearing every time though. To me it appears pretty consistently.