Re: DevTray borked :( reviewd

On Thu, 26 Sep 2013 22:40:47 +0100
Abrolag <[email protected]> wrote:

> On Wed, 25 Sep 2013 07:09:44 +0100
> Stephen Watson <[email protected]> wrote:
> 
> > Abrolag <[email protected]> wrote:
> > 
> > > This has been a bit flaky for a while now producing 'Insertion Error' when
> > > trying to open CDs but nevertheless succeeding eventually, and as I don't
> > have
> > > much use for CDs these days I've not bothered with it.
> > > 
> > > However, with the latest version of debian testing it has failed
> > completely.
> > > (This is on the computer at work - I haven't done the latest upgrade at
> > home)
> > > 
> > > Also, I can't file a bug report because the error 'save' dialogue doesn't
> > work
> > > either!
> > > 
> > > Looking at the on-screen report there is something about HAL and udev not
> > > getting a reply in time.
> > > 
> > > As a temporary measure I can get round this using pmount and pumount but I
> > > really would like a solution that plays nice with ROX. If I use pmount to
> > > access a USB stick I can't then unmount via the ROX dialogue .
> > > 
> > > I know there hasn't been any development for a long time now, but I'd be
> > very
> > > grateful if someone could have a look at this.
> > 
> > If you want the risk, try
> > 
> > http://kerofin.demon.co.uk/~stephen/snapshots/DiskMan.tar.gz
> > 
> > which is the replacement I'm using.  It's a little rough around the edges
> > but mostly works.
> > 
> 
> A bit more info.
> 
> With DevTray it seems that dbus is timing out when trying to talk to HAL, which
> it never did before the latest debian upgrade.
> 
> I tried DiskMan here at home first and it seemed OK, but on the works computer
> I get a permissions failure when it tries to mount the USB drive. I have no idea
> how that could come about! If I run it from a root task window it works OK.

I don't know if anyone is still watching this list, but here goes anyway.

DiskMan insists on using the full URI when mounting a memory device. I can see
the rational for this but it has some rather unfortunate side effects -
especially when using something like rsync, and I still haven't worked out why
it works on some machines but not on others with (seemingly) the same
OS/version.

DevTray is much better in that respect, in that it interrogates the device name
and, for all debian versions up to and including 'squeeze', it works. It is from
'testing' onwards when it is borked.

So, does anyone know what has changed that creates this problem? I've tried
examining the code itself, but really don't have a clue what I'm supposed
to be looking for. I have two problems here. First I've no idea how OO
programming works. Second I'm used to moderately sized single file programs!

If nobody has the time (or interest) to resolve this, can you at least give me
some idea of where to start?

-- 
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk