trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: September 2012

Re: [trinity-devel] TDEHW Summary

From: Darrell Anderson <humanreadable@...>
Date: Sun, 2 Sep 2012 16:31:37 -0700 (PDT)
> > Does 'eject' work from the command line at all on your system?
> 
> Yes and no.
> 
> The eject command works great to open and close the drive
> tray --- until I insert a disk. When I insert a disk and the
> drive tray closes, the eject command stops working. When I
> use the drive button to eject the disk, the eject command
> thereafter starts working again.
> 
> Hence my previous comment that there might be some kind of
> soft lock occuring.
> 
> I don't know why this does not happen on your system. Do you
> build with both WITH_HAL=ON and WITH_TDEHW=ON? If yes,
> possibly HAL is grabbing the Eject and Safely Remove
> commands rather than TDEHW?
> 
> I see that the Safely Remove option is a service type:
> 
> Exec=kio_media_mounthelper -s %u
> 
> and the Eject command is a service type too:
> 
> Exec=kio_media_mounthelper -e %u
> 
> Looks like kio_media_mounthelper is a good place to
> troubleshoot? Perhaps that command builds differently under
> WITH_HAL and WITH_TDEHW?

I'm looking at tdebase/kioslave/media/mediamanager/CMakeLists.txt. I notice two differences:

Under WITH_HAL, linuxcdpolling.cpp is built but not otherwise. Second, under WITH_HAL, the LINK option includes ${DBUS_TQT_LIBRARIES} but otherwise not.

In other words, when building with WITH_HAL=OFF and WITH_TDEHW=ON, those two differences come into play.

I could try a simple patch to add those options and see what happens. Worse case is tdebase fails to build.

Darrell