Hello,
I'm new to this list, a bit curious about udev and the upper
layers. I have some questions, not too dumb I wish.
- re-expliciting to understand myself -
** What I want : **
I want the ability for a simple user to set ANY action
automatically done according to device events ...
with
Hi,
I experience segault using devicekit-disks 007
(both gentoo ebuild of gnome overlay and from sources)
It probably stops in :
"for (n = 0; props->device_file_by_id[n] != NULL; n++)"
of do_show_info() in devkit-disks.c
The backtrace is helpless :
#0 0x00403637 in do_show_info ()
#1 0x
As a precision :
dbus_g_proxy_call() returns 0 but hash_table contains 0
entry.
It's maybe related to the fact that
props->device_file_by_id[n]
and
props->device_file_by_path[n]
are NULL => segfault
the "for" loop should probably contains something like :
props->device_file_by_id != NULL
and
props
As no answer has (yet) been given,
I would like to rewrite differently my
thoughts :
I want to give a simple user the ability the do
something when a block subsystem event happens.
1) with udev it means using libudev and rewriting a udev subset
2) with hal it means "hook"ing a helper in a policy
[patch attached about the segfault]
About the NULL values :
dbus_g_proxy_call doesn't succeed :
$ /usr/libexec/devkit-disks-daemon
(devkit-disks-daemon:346): devkit-disks-daemon-WARNING **: Failed to acquire
org.freedesktop.DeviceKit.Disks
(devkit-disks-daemon
On Sat, Oct 03, 2009 at 07:24:08AM +0100, Scott James Remnant wrote:
> On Tue, 2009-09-29 at 11:47 +0200, gibbo...@gmail.com wrote:
>
> > ** What I want : **
> > I want the ability for a simple user to set ANY action
> > automatically done according to device events ...
> > with the "state-of-art"
On Tue, Oct 06, 2009 at 12:18:37AM +0200, gibbo...@gmail.com wrote:
> $ devkit-disks --show-info /dev/sda7
> devkit-disks-daemon throws :
>
> ** (devkit-disks-daemon:9668): WARNING **: introspection data references
> non-existing property NativePath
> [ ... same message for each property follow .
Hi,
I attempted to do what I wanted.
(just a POF, but I'm still without any advice
about the correct way to do)
So here comes 11k of noobish-bloated code which :
- parse some config files of this format (GKeyFile) :
[spec]
name=this_device
event=DeviceMounted
exec=echo ADDED docus >> /tmp/dk.log
attachment
dkd_actions.tar.gz
Description: Binary data
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel
Hi Stef,
>From what I uinderstand, udev is to low-level.
My 1st goal is to get all devices (known and unknown) automounted.
Then, to let a user spawn any action for any block device event
(added, removed, mounted, unmounted)
1) I have set all the rules for my known hardware in the fstab
so users h
Hello,
On Wed, Oct 14, 2009 at 10:39:42AM +0200, Stef Bon wrote:
> Hello Raph,
>
> I'm sorry to say, but your email is too technical (complicated) for me.
> I'll go through your answer checking what you mean:
I'm really sorry, I was to quick to write, and wrote as if you wanted to
understand the
Hi again,
I still keep my noise restricted to this thread.
typo in :
- DeviceKit-disks.7.html
DKD_PRESENTATION_NAME
The name to user for the device when presenting it to the user.
=>
The name to use for the device when presenting it to the user.
and trivial changes :
- Like device_file_by_path
archive attached
On Wed, Oct 28, 2009 at 12:31:08AM +0100, gibbo...@gmail.com wrote:
[...]
devkit-disks-trigger.tar.gz
Description: Binary data
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinf
On Fri, Nov 06, 2009 at 12:41:30AM +0100, Martin Pitt wrote:
> gibbo...@gmail.com [2009-10-08 4:02 +0200]:
> > Resolved the 'introspection data references non-existing property'
> > by updating dbus-glib from 0.76 to 0.80, it should *really* be
> > noted in the README for the ease of maintainers a
14 matches
Mail list logo
