9 Sep
2019
9 Sep
'19
6:29 a.m.
Hello all,
Debian Buster with R.14.07 (Development).
I have an external SATA to USB enclosure with removable discs. When I slip a
disc in and turn it on, I get a Konqueror error (unable to mount this device,
see attachment). However, I can mount it with no problem from the command
line.
My guess is that it's a timing problem, Konqueror trying to mount something
that is not yet available, but I don't know what to do.
I did not have this with Stretch and "stable" TDE, so it might also ave to do
with de "Development" version.
Thierry
9 Sep
9 Sep
6:43 a.m.
Thierry de Coulon wrote:
My guess is that it's a timing problem, Konqueror
trying to mount
something that is not yet available, but I don't know what to do.
Hi Thierry,
this should be a new installation for you - not an upgrade? IF so did you
check your rights and permissions? So that the user is in the required
group?
regards
6:48 a.m.
New subject: [trinity-users] Re: Konqueror mount error
Anno domini 2019 Mon, 09 Sep 08:43:44 +0200
deloptes scripsit:
Thierry de Coulon wrote:
+1 - I remember, I had the same issue when I removed policykit on devuan.
My guess is that it's a timing problem,
Konqueror trying to mount
something that is not yet available, but I don't know what to do.
Hi Thierry,
this should be a new installation for you - not an upgrade? IF so did you
check your rights and permissions? So that the user is in the required
group?
regards
---------------------------------------------------------------------
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
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
8:02 a.m.
New subject: [trinity-users] Re: Konqueror mount error
On Monday 09 September 2019 08.43:44 deloptes wrote:
Hi Thierry,
this should be a new installation for you - not an upgrade? IF so did you
check your rights and permissions? So that the user is in the required
group?
Yes, it's a new installation. My user has the usual groups, I can't see any
group that would have to do with mounting removable drives.
What's more, some drives do mount (thumb drives), others don't, even some
discs in my external enclosure mount, others don't. Very strange.
Thierry
9:22 a.m.
New subject: [trinity-users] Re: Konqueror mount error
Hi Thierry!
Anno domini 2019 Mon, 9 Sep 10:02:26 +0200
Thierry de Coulon scripsit:
On Monday 09 September 2019 08.43:44 deloptes wrote:
Could you check: Those that mount have a partitiontabe, those who don't do not have a
partition table.
Nik
Hi Thierry,
this should be a new installation for you - not an upgrade? IF so did you
check your rights and permissions? So that the user is in the required
group?
Yes, it's a new installation. My user has the usual groups, I can't see any
group that would have to do with mounting removable drives.
What's more, some drives do mount (thumb drives), others don't, even some
discs in my external enclosure mount, others don't. Very strange.
Thierry
---------------------------------------------------------------------
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
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
9:25 a.m.
New subject: [trinity-users] Re: Konqueror mount error
Anno domini 2019 Mon, 9 Sep 11:22:55 +0200
Dr. Nikolaus Klepp scripsit:
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
Hi Thierry!
Anno domini 2019 Mon, 9 Sep 10:02:26 +0200
Thierry de Coulon scripsit:
Sorry, just saw your screenshot ... nothing to do with my old problem.
Nik
On Monday 09 September 2019 08.43:44 deloptes
wrote:
Could you check: Those that mount have a partitiontabe, those who don't do not have a
partition table.
Nik Hi Thierry,
this should be a new installation for you - not an upgrade? IF so did you
check your rights and permissions? So that the user is in the required
group?
Yes, it's a new installation. My user has the usual groups, I can't see any
group that would have to do with mounting removable drives.
What's more, some drives do mount (thumb drives), others don't, even some
discs in my external enclosure mount, others don't. Very strange.
Thierry
---------------------------------------------------------------------
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
11:58 a.m.
New subject: [trinity-users] Konqueror mount error
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2019/09/09 03:29 PM, Thierry de Coulon wrote:
Hello all,
Debian Buster with R.14.07 (Development). I have an external SATA to USB enclosure with
removable discs. When I
slip a disc in and turn it on, I get a Konqueror error (unable to mount this device, see
attachment). However, I
can mount it with no problem from the command line.
My guess is that it's a timing problem, Konqueror trying to mount something that is
not yet available, but I don't
know what to do.
I did not have this with Stretch and "stable" TDE, so it might also ave to do
with de "Development" version.
Thierry
Hi Thierry,
a few questions to gather further info.
1) do you have policykit installed? I guess so, if you say some partitions on external
drives can be mounted.
2) Does the disk have a valid partition in sdg1?
3) is the disk in /etc/fstab?
4) what command do you use to mount the partition from CLI?
5) if you retry from Konqueror, do you have a failure again?
6) what does "fdisk -l /dev/sdg" or "gdisk -l /dev/sdg" prints?
7) what happens if you try as root instead of normal user?
Additionally, do you have d-feet installed on your computer? That could help in
troubleshooting since I see in your
screenshot the error is reported by udisks2 dbus call.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl12PmEACgkQKnW3yore
1c84QA//bucJ3uNavE3cf5kN8vK7RiSvpYHOqnU47sDbWetYPHiKzeV6aGMmPDei
9aFRdzc502B8l/mR9ZDwS6UE1QQIYtrPcpIz0SHGUS54wtIVjNTdA4BzMvlCaA1D
IxU+paQ5VAG+eiHAZLkLF6x/V3Xyx8Kk/h96YaSmi4kSdkcxI6DGPa/33C2R+dsv
ceaVX5fncZCLfyZ7WKUEvT5E759dcbNXzz/jdPKPYUyWq8DqecotyqS7oEHydbvc
CnacZ6RPoaIawUe4/ZdBeT4jyEt4aQOQyTStpPrA1Yo6QgjTZ4CPhh0uPgpCXRvN
/MKNKdCmBX5HAPEm32dBKouKZMz5bm80RRrxk9s+wqxq6HOioCbs33TqSJuWWbM2
DIil8ufzDVL/TZD3srjpATmMUrOUNPFx9LDyxz29Sa5DIlYWjvbKLUiVGyEnIN+C
TeOlBdfvtLxE8Nj3NueOjAi144OflwQmR/CMdLOLzjG+UGQsYiG5mHlbfrIjftvl
kBK51Qw7IJBQQUgag34FKYlF+xQW2ueStQALaprmPemHapVMrcMxlUTvSSL3M6D7
OuYRDucbSsGEt135FHHegeFfjlQaq6uhbOdHVajmT6nxa+OWPLPXLFrwGxghcPQu
gmyhHCvoPsRbrWHWswNoBM6bnDY1Q2zk6gE0ZjIhdDldh06LQT0=
=ttBv
-----END PGP SIGNATURE-----
2:48 p.m.
New subject: [trinity-users] Konqueror mount error
On Monday 09 September 2019 13.58:29 Michele Calgaro via trinity-users wrote:
Hi Thierry,
a few questions to gather further info.
1) do you have policykit installed? I guess so, if you say some partitions
on external drives can be mounted.
Is installed
2) Does the disk have a valid partition
in sdg1?
Yes. ext4, mbr
3) is the disk in /etc/fstab?
No
4) what command do you use to mount the partition from
CLI?
mount /dev/sdx /<mount directory>. As root. sdx is usually sdg or sdi,
depending on
other connected drives.
5) if you retry from Konqueror, do you have a failure
again?
I don't see what you want me to do. The error message appears when I plug
in /
switch on the external drive. If/when it works the drive gets mounted
on /media/<user>/<drive> and konqueror opens a window on its content. If/when
it fails nothing is mounted and I can't do it from Konqueror (or I don't know
I can :).
6) what does "fdisk -l /dev/sdg" or
"gdisk -l /dev/sdg" prints?
root@junior:/home/thierry# fdisk -l /dev/sdg
Disk /dev/sdg: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: HD103SI
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb6bc5d97
Device Boot Start End Sectors Size Id Type
/dev/sdg1 63 1953520064 1953520002 931.5G 83 Linux
root@junior:/home/thierry# gdisk -l /dev/sdg
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Disk /dev/sdg: 1953525168 sectors, 931.5 GiB
Model: HD103SI
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 88036014-EE81-4D56-92FA-6212E6693E3C
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 5099 sectors (2.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 63 1953520064 931.5 GiB 8300 Linux filesystem
Note that after running fdisk -l nothing happens, while after running gdisk
the drive got mounted!
7) what happens if you try as root instead of normal
user?
It found the drive OK, but did not open Konqueror, instead asked what to do
(attachment).
Additionally, do you have d-feet installed on your
computer? That could
help in troubleshooting since I see in your screenshot the error is
reported by udisks2 dbus call.
I did not, I have now.
Cheers
Michele
Also, I've noticed that "Safely remove" as user causes unmounting and
immediate re-mounting, "unmount" correctly unmounts.
As root both work as expected.
Thanks,
Thierry
4:56 p.m.
Thierry de Coulon wrote:
Also, I've noticed that "Safely remove"
as user causes unmounting and
immediate re-mounting, "unmount" correctly unmounts.
As root both work as expected.
I think we have updated the policy recently for this reason and AFAIR there
was a ticket, but might be I am wrong.
My user is in 46(plugdev)
And also I recall now that it was udisks2 that provides the service for dbus
$ dpkg -S /etc/dbus-1/system.d/org.freedesktop.UDisks2.conf
udisks2: /etc/dbus-1/system.d/org.freedesktop.UDisks2.conf
We actually simplyfied
/etc/dbus-1/system.d/org.trinitydesktop.hardwarecontrol.conf
but it is unrelated to this I guess.
10 Sep
10 Sep
2:15 a.m.
New subject: [trinity-users] Konqueror mount error
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Thierry,
thanks for answering the list of questions.
5) if you
retry from Konqueror, do you have a failure again?
I don't see what you want me
to do. The error message appears when I plug in / switch on the external drive.
If/when it works the drive gets mounted on /media/<user>/<drive> and
konqueror opens a window on its content.
If/when it fails nothing is mounted and I can't do it from Konqueror (or I don't
know I can :).
Also, I've noticed that "Safely remove" as user causes unmounting and
immediate re-mounting, "unmount" correctly
unmounts.
As root both work as expected.
Thanks,
Thierry
As root both work as expected.
Do you mean that
as root you don't have the problem at all?
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.
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.
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?
Last (but not least), is this a real system or is it running inside VirtualBox (or other
VM)? (not a stupid question,
trust me).
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl13BzUACgkQKnW3yore
1c/HOg/6Azse1lJik1VZ3gYdjEaDoP1lUSdvFOIi1SXT1WhRjKnhFxBbhP/Gugq3
usqidj0Zy7mPOBbfBDk87mC5bLRbThGvVpn4fjaQI1agB3iq4Fev1JgfAvtPzAbs
PZRRsvEb6hbR5tukpv8A1HfUgs9nvzCk/dGnWWLxyrlbShGVCyxOLCq8dtzgflgU
xej4MRQBBI2Ql1WFIc/ifjoqtiDUxAC1Dcm/Os3hedtLHciOW6KgmorMnPkiu2kI
goVC/r+AO1UCktzwEZ0cN3Hr71D9nDHdNCqWmB20qKsThkHEnLECDBkMnt0LTXvX
CVexHwAats+9bIrx7ZO+PUuWQlWGhjoLy4n7c0LrZEBunEdKweJpy9f5/Q8ld+lV
E/MbJG83iX4+/l+r8CYAmR5LP93iZ9CB0dSjK8OC/hOv58xGSCSH0tEXCjMfD+2I
j5FsOnwCxm9rU9A4+kqRpqw44xG1g8sVFIkuq32t/uEKrNCs9tmeeHIkU6XuOAgm
q4X9ZV9sL4iHe7PEhfBxveLw0cxdxOcNVxMjyhUE5fSNY1hYt7X0ou6dnbYsBKdZ
n160/4ZeH1HA1zTc6c/Q7+UGolI/7xlcpTO1hBzSnP355929PK21ex3uQ3HhrOr7
cDwhEJ7uzbomv8XiCb/aAiMGWrmt2BiKL6dbhq1mFK7gZeMMgus=
=hO7I
-----END PGP SIGNATURE-----
11:32 a.m.
New subject: [trinity-users] Konqueror mount error
On Tuesday 10 September 2019 04.15:17 Michele Calgaro via trinity-users wrote:
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.
As root both
work as expected.
Do you mean that as root you don't have the problem at all? 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
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!)
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
Last (but not least), is this a real system or is it
running inside
VirtualBox (or other VM)? (not a stupid question, trust me).
It's a real system.
Cheers
Michele
---------------------------------------------------------------------
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
3:13 p.m.
New subject: [trinity-users] Konqueror mount error
On Tuesday 10 September 2019 04:32:39 Thierry de Coulon wrote:
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.
There are a lot of pages that come up under this and similar questions, but
this one had answers that worked for me.
https://www.linuxquestions.org/questions/linux-newbie-8/how-can-i-automount…
With this, I created udev rules and a shell script (all should be explained in
this page). On a new installation, I just copy these items (udev rules and
shell script) from my secure storage location to these places, like so:
udev rules
sudo
cp -r -v -f /media/<storage_location>/etc/udev/rules.d/52-usb-memory.rules -t
/etc/udev/rules.d/
mount script
sudo
cp -r -v -f /media/<storage_location>/usr/local/sbin/mount-usb.sh -t
/usr/local/sbin/
After reboot, everything works like one expects, no surprises.
lotsa luck
Bill
On Tuesday 10 September 2019 04.15:17 Michele Calgaro
via trinity-users
wrote:
As root both work as expected.
Do you mean that as root you don't have the problem at all? 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
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!)
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
Last (but not least), is this a real system or is
it running inside
VirtualBox (or other VM)? (not a stupid question, trust me).
It's a real system.
> Cheers
> Michele
3:31 p.m.
New subject: [trinity-users] Konqueror mount error
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Thierry,
see comments below and screenshots attached.
So the second time around it works.
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.
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
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 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 :-$ 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 -----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-----
4:03 p.m.
New subject: [trinity-users] Konqueror mount error
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2019/09/09 03:29 PM, Thierry de Coulon wrote:
Hello all,
Debian Buster with R.14.07 (Development). I have an external SATA to USB enclosure with
removable discs. When I
slip a disc in and turn it on, I get a Konqueror error (unable to mount this device, see
attachment). However, I
can mount it with no problem from the command line.
My guess is that it's a timing problem, Konqueror trying to mount something that is
not yet available, but I don't
know what to do.
I did not have this with Stretch and "stable" TDE, so it might also ave to do
with de "Development" version.
Thierry
As an additional thought, it is possible that perhaps TDEHW is notified by udev of
the existence of the new device
before UDisks2 has created the related object path. Therefore an immediate attempt to
automount the device would
result in the error displayed in the original screenshot (object path
/org/freedesktop/UDisks2/block_devices/sdg1 not
existing).
This would also be consistent with the fact that a later attempt to mount the device (even
from Konqueror) works fine.
I assume you have chosen to automount the device when inserted in the tde control center,
right?
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl13yU4ACgkQKnW3yore
1c9TBw//aoc4SjUk9qeSkdNsNg3s7TV6T31XYvEQQTGMQAKoxAcSGo8Enw5Pb0hw
tO4M2i0EgSobMKEScoxURDsfGvlc5NDJCu66FUGDA8Es53zVFDFDDlnznTz/gAvA
3tQ2cKGJEceZCaGkv5VnEqsfv92eUZ0XorbAy0pPAsCWId8AJdiSGWfwh7bzepf0
kQnmHTviWEtbUN9lKFl5uMEEHQmtn8MR2BwE6g18dCevqdFtJTicN6bVJVt5dAHr
0zxVivwMkmWe+cfbHkZ2vBj9XACDRgN67UhvRn0cicdY5Yrb5C/9eFUS3yYIoqgP
at7zbi9JvVuJNddiJwY+hFp6WSMCr2Ty4kZID+EodIMxl30FwtHKAx2cKBNMNorW
S9KbOWRUSxDcWE6qpA353hfqwL54fly7NcIVWcaQG4536LMhBnKII/phjX2/PB8Z
ZwGEXweperD4/rVnacex+UlioymlMPZlDjtlmOezionZQXXfgUznk016ZGESNBvC
sxgGH8ZIkTcrwUywpzFZzg2qhGjRy1PQecy8H6ySLQw9FLtoeRbwC9Fdh2uYT6dj
Zi0VPsvYT2cW+jaZwQLVzWV0HhGSpegiwbrPDwQGT5DkkcSv4dsLGuDR96Yv64hl
Hc7fsOBSiQXX4WrrK+ArXyAyNkQ9o00KlyVyoTQUJQSVcOm7y48=
=/hEE
-----END PGP SIGNATURE-----
8:11 p.m.
New subject: [trinity-users] Konqueror mount error
On Tuesday 10 September 2019 18.03:27 Michele Calgaro via trinity-users wrote:
As an additional thought, it is possible that perhaps
TDEHW is notified by
udev of the existence of the new device before UDisks2 has created the
related object path. Therefore an immediate attempt to automount the device
would result in the error displayed in the original screenshot (object path
/org/freedesktop/UDisks2/block_devices/sdg1 not existing).
Sound plausible to me, as these disks do mount at a later stage
This would also be consistent with the fact that a
later attempt to mount
the device (even from Konqueror) works fine. I assume you have chosen to
automount the device when inserted in the tde control center, right?
Humm... not really. I have "chosen" nothing (at least knowing I did). I may
have said yes to mounting them the first time I got a popup window asking for
it (which would explain why I get that window as root but not as user).
In storage media I have "Enable medium application autostart after mount"
checked. "Mount automaticaly", "Read only" and "Quiet" are
unchecked, "UTF-8"
and "Mount as user" are checked, "Synchronous", "Access time
updates"
and "Flushed IO" show a minus, which I imagine means undefined.
Cheers
Michele
Thierry
11 Sep
11 Sep
12:18 p.m.
New subject: [trinity-users] Konqueror mount error
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Thierry,
I have done some research in R14.0.x.
Since your system tries to automap the disk when insterted, most likely you selected the
option to automatically open
the disk in Konqueror the very first time and then this is what is happening. No big deal
though.
I have tried to replicate the problem here, but I am not able to do so. Do you see
anything in your .xsession-errors
log file that could give some clue (although you may need TDE compiled with debug options
for that)?
Cheers
Michele
This would
also be consistent with the fact that a later attempt to mount the device (even from
Konqueror) works
fine. I assume you have chosen to automount the device when inserted in the tde control
center, right?
Humm... not really. I have "chosen" nothing (at least knowing I did). I may
have said yes to mounting them the
first time I got a popup window asking for it (which would explain why I get that window
as root but not as user). -----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl145hUACgkQKnW3yore
1c+uQA//fSWyuiax8HOhRoVHh4K3Li0x1cYYxMs6Y2tR6hVfp8mq8gYQFuTBbMaY
hjuP8H0X7QsqQrpx/+XcQCp60WggKiQGc5dPiI93BMb653gv9kSs80BT+gUW1dWs
fRFlU1VLOaNMR1np52GgXIz7tyMtLmQ1ietQiRqIu1Se1F6HUXbJedGHKkhT9PmO
qw7ol6w9tLfaYkihFi9C1Nm5SjuRD0wmFz+PY6OZRT06jUCb/CPS64lqAcKztHj7
kvDpwJ4KRp1Yq3Qt76u2d/oqCpBt3lLUL175hxy/Mfi2DJROCHjtma/wFO0RXIXS
oZiaUTRwDYk7DcS0QD8pYxROQJsz/+ffh8GFkfB+3GwtZ+yk6WAz/4UvueplGEp6
Khb26fj/oAwaO2CyJn9UYaam3hnbukGzko23jLsfbdY4I2FzMfM5Vjmm5Rw+D9vl
SKv8Dy2TE/C/aKwvLifu7dLSUUqfRI0zSCBKmSJSfNWxcWHi/6qrt5aNDOTcCA19
p3SUimxTQPTPFb7b/3gdMn+GBcBrcx5oRJaJCgx1bJJieCHkgg4rRXydmXFKRD6b
Xv0DaiSNAQarT+jHvdlMwkX8Jp+EK2ViwsmY7kp/3Qqe4uwILfFQUkdqqnyPt0GS
lQAlapmCc1iLF4ED4akaDcysZOT+FVjpsddJKLaGGXnFksLpJww=
=cBaw
-----END PGP SIGNATURE-----
1702
days inactive
1704
days old
15 comments
5 participants
participants (5)
-
deloptes -
Dr. Nikolaus Klepp -
Michele Calgaro via trinity-users -
Thierry de Coulon -
William Morder via trinity-users