trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: September 2019

Re: [trinity-users] Konqueror mount error

From: "Michele Calgaro via trinity-users" <trinity-users@...>
Date: Wed, 11 Sep 2019 00:31:35 +0900
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi Thierry,
see comments below and screenshots attached.

> 
> I did not spend so much time logged as root. I did not see the problem then, but I'd have to spend more time trying
> to give a real answer.
That may help, jsut to understand if the problem is general or strictly related to user or policies.


>> Re 5), when it fails, you can go in Konqueror, search the Storage Media in the treeview which in turn lists the
>> available known drives. Then double click on your failed disk and see if it gets mounted again or not. 
>> Alternatively, you can type "media:/sdg1" (or whatever path) in the location bar and press enter.
> 
> media:/sdg1 works
So the second time around it works.

> 
>> Now that you have d-feet installed, can you also make another test. After a failed mounting, open d-feet, search
>> the system bus for udisk2 and select it. On the right side you will see many interfaces. Search for object path 
>> /org/freedesktop/UDisks2/block_devices/sdg1 (or other path), expand it and please paste a screenshot.
> 
> Done (4 snapshots!)Sorry, that is the wrong path :-$
See example screenshot d-feet.png, take note the path includes "block_devices". If the disk is recognized, you should
see your sdg1 disk there and using the Mount/Unmount functions you can try to mount/unmount the disk directly from
d-feet. use {} as parameter of the calls.

> 
>> Finally, one more thing. Open KDCOP, search for kded -> mediamanager -> fullList function (going by memory here,
>> may be slightly different name). Double click to execute. In the result section, you will have a list of known
>> disks. Can you find your disk there? If so, can you paste a screenshot of the properties of that disk?
> 
> You get another snapshot
See example screenshot kdcop.png. You need to double click fullList() function and search for your disk in the section
below. This is to see if you disk has been detected by TDE or not.

It seems there may be something interfering with the first attempt of mounting the disk. Whether this is somewhere in
TDE code or not, I am not sure. I will see if I can reproduce the problem here.

Cheers
  Michele
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl13wdcACgkQKnW3yore
1c8vfhAAvaeNQxrUPnAkNs7u0hgmwDc+UZVaTnLcxmBjtqRmOD2AadRX7/Ku0XIM
/klmzISk5ZGSCQXisB90TSGQJZaVIT5E/R1KGgxPczj43jL5RigFdhRjmb9emt/E
CGkKbW44b6v0y1cUW9IuxEHONpzi78Fkaw5MaZxV0dO42VleTF3aF3Y8DBxrEcWw
zTiDarrv5JkRf4ivckPVRRVpUKeWGm4v3Uw0lN+H+ea0GRR7eK+vHUGBX0IcbrLK
79EN6e/25/2Rji4ABIAux4E2rk/YORCzYkVzeSbzF43vdkWbqRaSrAW0DAbXMjdk
1jFHkmpmkT/2kAvFfl2rVYmmtUhOoL9ySjvW4ZFCWd5kTtBhpecqzwbWw2kD7T1l
KP+BYZzzAKdPdBAle5Rk1VY1mb0hKA1Irq1RE+dCLgpiNHZ47ShDDX/2XM04NcrI
1SIo7THC3xTWZhKWS6Tvsz1bQHHHabtkmhKcO+ea2IFqRKwE1T8gzcMKZgwwVnzg
od7rwZskVlDq0qeJVyzHo0fnX9Hwhp/K+ZB1kgX47A5Fqt6TaDy16LLo5sOhZkAq
JI1S6+TG3IYyOe2y5KTSoL211MjUNmk6cKKe2E/pAk+vcl2S5TFk+G6KF9RuWRi+
sAZEm3HqIDc4uKbiY0Kejmuo6HYVZE3LM8QCbNHQ8/Eb2QquEEI=
=T4L3
-----END PGP SIGNATURE-----

Attachments: