On 18/11/11 15:50, Mike Blumenkrantz wrote:
On Fri, 18 Nov 2011 15:48:22 +1100
Jochen Schröder<[email protected]>  wrote:

On 18/11/11 13:16, Mike Blumenkrantz wrote:
On Fri, 18 Nov 2011 09:18:50 +1100
Jochen Schröder<[email protected]>   wrote:

Hi all,

I'm still trying to get eeze mount to work in E_FM. I have build eeze
with libmount support (2.19.1). And I am building E17 with ./configure
--disable-mount-hal --disable-mount-udisks, here is the relevant
configure output:


Preferred Backends:
    * device..............: eeze
    * hal_mount...........: no
    * udisks_mount........: no
    * eeze_mount..........: yes


Additionally I have uncommented the following line in sysactions.conf

# uncomment this line to enable eeze mounting for users
user:   someuser allow: /bin/mount /bin/umount /usr/bin/eject


When plugging in a device on the usb port nothing appears on the desktop
or in the file menu. xsession-errrors reports some dbus error
(attached). This system is debian sid. This seems to be the same problem
that was reported here:
http://osdir.com/ml/enlightenment-development-linux-ui/2011-08/msg00503.html


Additionally, when logging out E waits until the logout now, wait longer
dialogue shows up (however I have not 100% confirmed that this is related).

Cheers
Jochen
hmm definitely strange since it looks like your devices are being properly
detected. please start your e with EINA_LOG_LEVELS=efm:5 and post back your
xsession log again.


For what it's worth if I compile e with udisks mount support only, i.e.
configure --disable-mount-hal --disable-mount-eeze

Icons show up on the desktop and I can mount and unmount, however when I
pull the usb drive out, the icon stays on the desktop, another
xsession-errors attached. Don't know if the two errors are related.

Cheers
Jochen
ooh looks like you got a nice crash in efm. gdb attach to it and run whatever
you did again to get a backtrace for me


OK here it is:

to reproduce I compile e with --disable-mount-hal --disable-mount-eeze

start e
attach gdb to e_fm

plugin usb stick,
unmount usb stick
pull usb still
-> BOOM

first time I did this all screens went black and I had to hard reset (didn't have a 2nd PC to test if I could ssh into the machine).

Seems something is writing where it should not.


Continuing.

Program received signal SIGABRT, Aborted.
0x00007f4b78643405 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#0  0x00007f4b78643405 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f4b78646680 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f4b78679dbb in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x00007f4b78683606 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x00007f4b7868833c in free () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x0000000000407695 in _e_fm_shared_device_storage_free (s=0x1acd070) at 
../e_fm_shared_device.c:11
#6  0x0000000000406d68 in _e_fm_main_udisks_cb_dev_del (data=<optimized out>, 
msg=<optimized out>) at e_fm_main_udisks.c:268
#7  0x00007f4b7965afee in cb_signal_dispatcher (conn=<optimized out>, 
msg=0x1ac56e0) at e_dbus_signal.c:271
#8  0x00007f4b79657254 in e_dbus_filter (conn=<optimized out>, 
message=0x1ac56e0, user_data=0x1abdeb0) at e_dbus.c:404
#9  0x00007f4b791dc276 in dbus_connection_dispatch () from 
/lib/x86_64-linux-gnu/libdbus-1.so.3
#10 0x00007f4b7965803d in e_dbus_idler (data=0x1abdeb0) at e_dbus.c:435
#11 0x00007f4b7a0b3284 in _ecore_call_task_cb (data=<optimized out>, 
func=<optimized out>) at ecore_private.h:264
#12 _ecore_idle_enterer_call () at ecore_idle_enterer.c:164
#13 0x00007f4b7a0b4965 in _ecore_main_loop_iterate_internal (once_only=0) at 
ecore_main.c:1765
#14 0x00007f4b7a0b4faf in ecore_main_loop_begin () at ecore_main.c:887
#15 0x000000000040336e in main (argc=<optimized out>, argv=<optimized out>) at 
e_fm_main.c:157
1       #ifdef HAVE_CONFIG_H
2       #include "config.h"
3       #endif
4       
5       #ifdef HAVE_ALLOCA_H
6       # include <alloca.h>
7       #elif defined __GNUC__
8       # define alloca __builtin_alloca
9       #elif defined _AIX
10      # define alloca __alloca
quit
A debugging session is active.

        Inferior 1 [process 2172] will be detached.

Quit anyway? (y or n) Detaching from program: 
/opt/e17/lib/enlightenment/utils/enlightenment_fm, process 2172
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to