20 Nov
2021
20 Nov
'21
3:55 p.m.
Whenever I try to open such devices as USB flash drives or solid state
drives, the 'Unlock storage device' window appears and asks me to enter
the password. I do so, whereupon the window expands at the bottom with
the following message: 'Feature only available with HAL.'
I find that message strange, as I thought that HAL had been superseded
by Dbus, but perhaps I am mistaken. In any event I would appreciate it
if somebody could inform me as to how to open such encrypted devices in
a box with Debian Bullseye and TDE.
Regards, Ken Heard
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
20 Nov
20 Nov
4:09 p.m.
On 2021/11/21 12:55 AM, Ken Heard wrote:
Whenever I try to open such devices as USB flash
drives or solid state
drives, the 'Unlock storage device' window appears and asks me to enter
the password. I do so, whereupon the window expands at the bottom with
the following message: 'Feature only available with HAL.'
I find that message strange, as I thought that HAL had been superseded
by Dbus, but perhaps I am mistaken. In any event I would appreciate it
if somebody could inform me as to how to open such encrypted devices in
a box with Debian Bullseye and TDE.
Regards, Ken Heard
Hi Ken,
R14.0.x does not support opening encrypted devices from GUI directly, you get exactly the
error that you reported.
A workaround is to unlock the device from CLI first, then you can mount the unlocked
device.
R14.1.0 will support unlocking/mounting/unmounting/locking LUKS disks from GUI. In fact if
you use R14.1.0 [Development]
it already supports that, as long as you have udisks2 (recommended) or udevil or pmount
installed. You may need a polkit
agent installed to gain access to it (policykit-1-gnome will do for the moment -- a TDE
polkit agent is under
development and will be included in R14.1.0 when ready).
On a side note, I have been running TDE on Debian testing since 2012, I never had many
issues. The fact that you see so
many problems (see other emails from you) let me think you may be missing some packages or
have done something wrong
during the installation. Like the DCOP issue for example.
In general, TDE on a Debian box is as good as it gets :-)
Cheers
Michele
21 Nov
21 Nov
10:24 a.m.
Michele Calgaro via tde-users wrote:
On a side note, I have been running TDE on Debian
testing since 2012, I
never had many issues. The fact that you see so many problems (see other
emails from you) let me think you may be missing some packages or have
done something wrong during the installation. Like the DCOP issue for
example. In general, TDE on a Debian box is as good as it gets :-)
I can only second that and there is the preliminary stable and test builds
(PSB and PTB) ready to install where I think PTB is the development that
Michele referred to.
https://wiki.trinitydesktop.org/Preliminary_Testing_Builds
889
days inactive
890
days old
2 comments
3 participants
participants (3)
-
deloptes -
Ken Heard -
Michele Calgaro