On 18/11/11 16:56, Mike Blumenkrantz wrote: > On Fri, 18 Nov 2011 16:35:24 +1100 > Jochen Schröder<cycoma...@gmail.com> wrote: > >> On 18/11/11 15:50, Mike Blumenkrantz wrote: >>> On Fri, 18 Nov 2011 15:48:22 +1100 >>> Jochen Schröder<cycoma...@gmail.com> wrote: >>> >>>> On 18/11/11 13:16, Mike Blumenkrantz wrote: >>>>> On Fri, 18 Nov 2011 09:18:50 +1100 >>>>> Jochen Schröder<cycoma...@gmail.com> 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. >> >> > hmmmmm super weird. can you run e in valgrind and reproduce this? that would > give me a better idea of what's breaking >
OK I was just trying to use valgrind, how do I log to a file and keep the console operational to answer the attach debugger questions? Also I've just had a kernel oops when pulling out the usb stick (dmesg below), so not sure if this even is an e problem Nov 19 15:20:21 aptosidbox kernel: [ 4160.178957] sd 9:0:0:0: [sdc] Attached SCSI removable disk Nov 19 15:20:22 aptosidbox kernel: [ 4160.460176] sd 9:0:0:0: [sdc] 7856127 512-byte logical blocks: (4.02 GB/3.74 GiB) Nov 19 15:20:22 aptosidbox kernel: [ 4160.465202] sdc: sdc1 Nov 19 15:26:32 aptosidbox kernel: [ 4531.039494] usb 1-2.1.2: USB disconnect, device number 8 Nov 19 15:26:32 aptosidbox kernel: [ 4531.041185] scsi: killing requests for dead queue Nov 19 15:26:32 aptosidbox kernel: [ 4531.043011] PGD 755ed067 PUD 755ee067 PMD 0 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043011] CPU 1 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043011] Modules linked in: af_packet ppdev lp rfcomm bnep bluetooth rfkill powernow_k8 mperf cpufreq_powersave cpufreq_stats cpufreq_conservative pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) fuse dm_crypt snd_hda_codec_hdmi joydev snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device snd edac_core soundcore edac_mce_amd snd_page_alloc i2c_nforce2 k10temp parport_pc parport evdev pcspkr psmouse serio_raw button processor ext4 mbcache jbd2 crc16 dm_mod usb_storage uas sg usbhid hid sd_mod sr_mod crc_t10dif cdrom ata_generic ohci_hcd radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core power_supply pata_acpi sata_nv ehci_hcd pata_amd libata usbcore scsi_mod ssb mmc_core pcmcia forcedeth pcmcia_core [last unloaded: scsi_wait_scan] Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] Pid: 1750, comm: udisks-daemon Tainted: G O 3.1-1.slh.4-aptosid-amd64 #1 To Be Filled By O.E.M. To Be Filled By O.E.M./N68-S Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] RIP: 0010:[<ffffffffa029777b>] [<ffffffffa029777b>] sd_revalidate_disk+0x33/0x161d [sd_mod] Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] RSP: 0018:ffff880075485af8 EFLAGS: 00010246 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] RAX: 0000000000000000 RBX: ffff88007cc296c0 RCX: 0000000000000002 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] RDX: 0000000000000002 RSI: ffff880062c8b280 RDI: ffff880015565400 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] RBP: 0000000000000000 R08: 00000008ffffffff R09: 0000000000000005 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] R10: 0000000000000246 R11: ffff88007fc91b00 R12: ffff880015565400 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] R13: 0000000000000000 R14: ffff88007cc296d8 R15: ffff88007cc296c0 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] FS: 00007fc6c5ca67a0(0000) GS:ffff88007fc80000(0000) knlGS:0000000000000000 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] CR2: 0000000000000008 CR3: 00000000755ec000 CR4: 00000000000006e0 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] Process udisks-daemon (pid: 1750, threadinfo ffff880075484000, task ffff880076255d70) Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] ffff88007fc91b00 ffffffff810e8b2b ffffffff81172662 ffff880015565448 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] 0000000000000000 ffff880015565400 000000000000001d ffffffff81307448 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] ffff88007fc91b00 ffff880015565400 ffff88007cc296c0 ffff88007cc296c0 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810e8b2b>] ? iget5_locked+0x61/0x13d Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff81172662>] ? kref_put+0x3e/0x47 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff81307448>] ? _raw_spin_unlock+0x1d/0x2b Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff81121495>] ? rescan_partitions+0xac/0x41b Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810fad94>] ? __blkdev_get+0x1a6/0x37e Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810fb226>] ? blkdev_get+0x2ba/0x2ba Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810fb13c>] ? blkdev_get+0x1d0/0x2ba Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff81307448>] ? _raw_spin_unlock+0x1d/0x2b Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810fb226>] ? blkdev_get+0x2ba/0x2ba Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810d3f90>] ? __dentry_open+0x18c/0x2cc Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810e0703>] ? do_last+0x45f/0x5a7 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810e0b78>] ? path_openat+0xce/0x31c Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffffa007fab4>] ? ioctl_internal_command.constprop.4+0x62/0x15c [scsi_mod] Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff81063cec>] ? module_refcount+0x80/0x95 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810e0e88>] ? do_filp_open+0x2a/0x6e Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff81307448>] ? _raw_spin_unlock+0x1d/0x2b Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810e9e89>] ? alloc_fd+0x109/0x11b Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff810d4e55>] ? do_sys_open+0x5e/0xe5 Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] [<ffffffff81307f52>] ? system_call_fastpath+0x16/0x1b Nov 19 15:26:32 aptosidbox kernel: [ 4531.043742] RSP <ffff880075485af8> Nov 19 15:26:32 aptosidbox kernel: [ 4531.099217] ---[ end trace da2439847618e5d0 ]--- ------------------------------------------------------------------------------ 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
