[Vagrant Cascadian]
much less to go on.
Well, enough to have a fighting chance. I'm testing with this
implementation now.
#!/usr/bin/python
# requires python-notify
import pynotify
import sys
import string
import os
# Do not run on Gnome, as gnome detect the ltspfs mounts on its own.
xdgdirs =
On Thu, Jun 24, 2010 at 11:15:20AM +0200, Petter Reinholdtsen wrote:
[Vagrant Cascadian]
this is definitely worth including the the examples section... though it
might
just be seen as noise for a gnome install, so i'm not sure it should be
installed by default.
I tested it on KDE, and
[Vagrant Cascadian]
this is definitely worth including the the examples section... though it might
just be seen as noise for a gnome install, so i'm not sure it should be
installed by default.
I tested it on KDE, and it work there too. I believe it should be
enabled by default to improve the
On Fri, May 07, 2010 at 08:54:35PM +0200, Petter Reinholdtsen wrote:
I'm starting to wonder if the approach from Sune might be better for
now, issuing notify events on the session dbus. :/
An platform independent approach might be to use the python and
pynotify to submit the notifications.
[Petter Reinholdtsen]
I'm starting to wonder if the approach from Sune might be better for
now, issuing notify events on the session dbus. :/
An platform independent approach might be to use the python and
pynotify to submit the notifications. This code fragment will show a
popup on any
[Petter Reinholdtsen]
This script work, and causes a LTSP entry to show up in the list of
removable devices:
But it only work for root, and the ltspfs hook run as the user. I
tried using this trick in a /etc/ltspfs/mounter.d/hal-notify script,
and hal-device fail because only root can run it.
[Oliver Grawert]
that might be because you attach it directly to the computer device
in the tree,
Thanks for the tip.
create an ltsp devicetree first that acts as the parent for your
disk, that should give you more opportunities to fiddle with
permissions through dbus service files (there
[Oliver Grawert]
you could include the calling code into lbmount, it already runs
suid root on the server ;)
Good point. That should work. I tested this, and discovered that KDE
crashed again, but this time in HalDevice::queryDeviceInterface(). A
closer look show that the hal device have no
[Petter Reinholdtsen]
Michael Biebl tested to use hal-device --add to generate the
approporiate HAL event, but this one caused KDE to crash because
some value is missing. Posting it her to have it documented.
I investigated this some more by looking at the crash backtrace and
reading the KDE
Michael Biebl tested to use hal-device --add to generate the
approporiate HAL event, but this one caused KDE to crash because some
value is missing. Posting it her to have it documented.
cat /tmp/device-info.txt EOF
block.is_volume = true (bool)
info.capabilities = {'volume', 'block'} (string
Based on input from Dario Freddi on IRC, I ran lshal --monitor in
Debian/Lenny while inserting a USB stick, to see what hal events were
generated.
First, these three showed up:
23:00:09.685: usb_device_90c_1000_A8026288 added
23:00:10.007: usb_device_90c_1000_A8026288_if0
11 matches
Mail list logo
