On Saturday 16 January 2021 09:46:12 Dr. Nikolaus Klepp wrote:
Hi all!
I just found that after my latest updates to 14.0.10 I lost the "Delete" funtionality in konqueror. When I do a right click on at file on a FAT32 usb thumbdrive, then the context menu pops up with the "Delete" entry greyed out. Pressing "<DEL>"-key consequently des not delete the file nor move it to the thrashcan. Pressing "<shift>+<DEL>" deletes the file.
Does somebody else see this, too?
Nik
I just upgraded a couple days ago, and I don't have that problem. Everything works the same as before.
The problem, however, may reside in the flash drive itself, and the fat32 filesystem. I've had problems with both flash drives and SD cards: sometimes they mount and behave normally, sometimes not. Do you have the delete function when you are using Konqueror with non-fat drives, such as your
other
hard drives?
You might dig up your konquerorrc file, where the delete function can be set or unset. You might be able to override other changes by changing that file.
Bill ____________________________________________________
I need to use fat32 because I still have some itsinks clients (thankfully that's fading)
Stock formatted usb and SD cards do exhibit problems like that in general. That's why I always format them with linux before use. I never have a problem after that.
NTFS, when I have to use that crap, sometimes will. HFS doesn't give me much of a problem, less than NTFS more than fat32.
Try clean formatting the drives before use and make use you chown to your user just in case.
Kate
On Saturday 16 January 2021 11:19:51 BorgLabs - Kate Draven wrote:
On Saturday 16 January 2021 09:46:12 Dr. Nikolaus Klepp wrote:
Hi all!
I just found that after my latest updates to 14.0.10 I lost the "Delete" funtionality in konqueror. When I do a right click on at file on a FAT32 usb thumbdrive, then the context menu pops up with the "Delete" entry greyed out. Pressing "<DEL>"-key consequently des not delete the file nor move it to the thrashcan. Pressing "<shift>+<DEL>" deletes the file.
Does somebody else see this, too?
Nik
I just upgraded a couple days ago, and I don't have that problem. Everything works the same as before.
The problem, however, may reside in the flash drive itself, and the fat32 filesystem. I've had problems with both flash drives and SD cards: sometimes they mount and behave normally, sometimes not. Do you have the delete function when you are using Konqueror with non-fat drives, such as your
other
hard drives?
You might dig up your konquerorrc file, where the delete function can be set or unset. You might be able to override other changes by changing that file.
Bill ____________________________________________________
I need to use fat32 because I still have some itsinks clients (thankfully that's fading)
Stock formatted usb and SD cards do exhibit problems like that in general. That's why I always format them with linux before use. I never have a problem after that.
NTFS, when I have to use that crap, sometimes will. HFS doesn't give me much of a problem, less than NTFS more than fat32.
Try clean formatting the drives before use and make use you chown to your user just in case.
Kate
Except ... maybe users need to use those items with other devices that do not read Linux filesystems? e.g., SD cards in smartphones, or flash drives to be used with other computers. Maybe, the unfortunate user is forced by job or circumstances to take those flash drives or SD cards and use them on [*SHUDDER of horror*] Windozes or Rotten Apples? In such cases, fat32 is read by all of them; ext3 or ext4, not.
'Twould be nice if Linux could handle fat32 sometimes without having to format it to a Linux filesystem.
:-/
Bill
On Sat, Jan 16, 2021 at 11:44:27AM -0800, William Morder via tde-users wrote:
'Twould be nice if Linux could handle fat32 sometimes without having to format it to a Linux filesystem.
As far as I know, all Linux distros should be able to handle fat32.
man mkfs.fat
should give you the options for formatting drives as a FAT system. Normally you don't call that directly, but call it through `mkfs` with the -t option.
mkfs -t vfat <device>
I would expect that all modern Linux distros support full read/write permissions on FAT drives.
There's plenty of other people who have this issue, not just TDE:
https://duckduckgo.com/?q=linux+cannot+move+file+to+trash
To support "move to trash", your drive needs to have a hidden trash directory. That's the case for other desktops, I assume TDE requires the same. I think that's normally called something like .Trash-1000 where the number at the end is your user id.
Do you have write permission in top (root) directory of the USB stick? If you do an `ls -a` of that directory, can you see a hidden trash directory, and do you have permissions to write to it?
If you make any changes to the permissions, you probably should unmount and remove the USB stick, then remount it, just in case TDE doesn't spot the changes.
On Saturday 16 January 2021 19:10:20 Steven D'Aprano via tde-users wrote:
On Sat, Jan 16, 2021 at 11:44:27AM -0800, William Morder via tde-users
wrote:
'Twould be nice if Linux could handle fat32 sometimes without having to format it to a Linux filesystem.
As far as I know, all Linux distros should be able to handle fat32.
man mkfs.fat
should give you the options for formatting drives as a FAT system. Normally you don't call that directly, but call it through `mkfs` with the -t option.
mkfs -t vfat <device>
I would expect that all modern Linux distros support full read/write permissions on FAT drives.
There's plenty of other people who have this issue, not just TDE:
https://duckduckgo.com/?q=linux+cannot+move+file+to+trash
To support "move to trash", your drive needs to have a hidden trash directory. That's the case for other desktops, I assume TDE requires the same. I think that's normally called something like .Trash-1000 where the number at the end is your user id.
Do you have write permission in top (root) directory of the USB stick? If you do an `ls -a` of that directory, can you see a hidden trash directory, and do you have permissions to write to it?
If you make any changes to the permissions, you probably should unmount and remove the USB stick, then remount it, just in case TDE doesn't spot the changes.
The problem is that Linux systems in general seem to have a problem sometimes with mounting a flash drive or SD card, but only after they have been used in another device, such as a smartphone or a non-Linux system.
I put a large music collection on a new SD card, for listening while I am outdoors walking, but when I went to change some of the items, now I find that my Linux system refuses to mount the drive. The same has happened with fat32 flash drives.
This does not happen with other hard drives, such as an external hard drive that is formatted NTFS; only with fat32 flash drives or (I forget the filesystem here) SD cards.
Also I believe that smartphones can really mess up the data on SD cards, as I had a lot of weirdness there. For example: a folder for one artist was instead filled with music from an entirely different artist. This could not have been a mistake on my part, as I have the originals, all tidy and organized, and the contents of the flash drive were first organized on a folder that resides in my desktop computer. Thus all I need to do is copy the contents of that folder to my SD card.
It is only when I tried to copy the contents of that SD card to another location, then suddenly everything got messed up.
So I believe that Kate might be onto something there, that formatting with Linux first could eliminate some of that mess.
Bill
Hi all!
Anno domini 2021 Sat, 16 Jan 19:41:35 -0800 William Morder via tde-users scripsit:
[...]
The problem is that Linux systems in general seem to have a problem sometimes with mounting a flash drive or SD card, but only after they have been used in another device, such as a smartphone or a non-Linux system.
I put a large music collection on a new SD card, for listening while I am outdoors walking, but when I went to change some of the items, now I find that my Linux system refuses to mount the drive. The same has happened with fat32 flash drives.
This does not happen with other hard drives, such as an external hard drive that is formatted NTFS; only with fat32 flash drives or (I forget the filesystem here) SD cards.
Also I believe that smartphones can really mess up the data on SD cards, as I had a lot of weirdness there. For example: a folder for one artist was instead filled with music from an entirely different artist. This could not have been a mistake on my part, as I have the originals, all tidy and organized, and the contents of the flash drive were first organized on a folder that resides in my desktop computer. Thus all I need to do is copy the contents of that folder to my SD card.
It is only when I tried to copy the contents of that SD card to another location, then suddenly everything got messed up.
So I believe that Kate might be onto something there, that formatting with Linux first could eliminate some of that mess.
Bill ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
Looks like this is complints about FAT32 are not the cause of my observations. Please see the attached screenshot: upper half of windows uses system:/media/sdb and shows the describes malfuncions (i.e.: <del> not working, no autorefresh), the lower half shows the very device but where it's mounted in the filesystem as /media/toshiba and there it works as expected (i.e.: <del> working and autorefresh working).
So this is definitly a TDE problem. Is there a way to get rid of "system:/media/" and just use the real mountpoint instead?
Nik
Anno domini 2021 Sun, 17 Jan 10:15:26 +0100 Dr. Nikolaus Klepp scripsit:
Hi all!
Anno domini 2021 Sat, 16 Jan 19:41:35 -0800 William Morder via tde-users scripsit:
[...]
The problem is that Linux systems in general seem to have a problem sometimes with mounting a flash drive or SD card, but only after they have been used in another device, such as a smartphone or a non-Linux system.
I put a large music collection on a new SD card, for listening while I am outdoors walking, but when I went to change some of the items, now I find that my Linux system refuses to mount the drive. The same has happened with fat32 flash drives.
This does not happen with other hard drives, such as an external hard drive that is formatted NTFS; only with fat32 flash drives or (I forget the filesystem here) SD cards.
Also I believe that smartphones can really mess up the data on SD cards, as I had a lot of weirdness there. For example: a folder for one artist was instead filled with music from an entirely different artist. This could not have been a mistake on my part, as I have the originals, all tidy and organized, and the contents of the flash drive were first organized on a folder that resides in my desktop computer. Thus all I need to do is copy the contents of that folder to my SD card.
It is only when I tried to copy the contents of that SD card to another location, then suddenly everything got messed up.
So I believe that Kate might be onto something there, that formatting with Linux first could eliminate some of that mess.
Bill ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
Looks like this is complints about FAT32 are not the cause of my observations. Please see the attached screenshot: upper half of windows uses system:/media/sdb and shows the describes malfuncions (i.e.: <del> not working, no autorefresh), the lower half shows the very device but where it's mounted in the filesystem as /media/toshiba and there it works as expected (i.e.: <del> working and autorefresh working).
So this is definitly a TDE problem. Is there a way to get rid of "system:/media/" and just use the real mountpoint instead?
Nik
Oh, I forgot: "media:/sdb" shows the same bad behaviour as "system:/media/sdb", so can I get rid of that, too?
Nik
Dr. Nikolaus Klepp wrote:
Oh, I forgot: "media:/sdb" shows the same bad behaviour as "system:/media/sdb", so can I get rid of that, too?
I've been observing similar issues with NFS and I was thinking of filing a bug or looking into the whole TDEIO stuff, which I started doing recently, but it is too much spaghetti to eat :) I do not have the clear picture to be able to debug and I enabled debugging for TDEIO, so this is what I found for my exotic mobile phone. In the case of the mobile it works under system:/media/Unbekanntes Gerät 2-1.5:1.0/
I have not tried looking under /media/Unbekanntes Gerät 2-1.5:1.0/
I think you should file a bug for what you are experiencing
[2021/01/14 12:53:36.951] [tdepowersave] unmonitored device changed: /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/host6/target6:0:0/6:0:0:0/ [2021/01/14 12:53:36.975] [tdepowersave] unmonitored device changed: /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/host6/target6:0:0/6:0:0:0/block/sdb//dev/sdb [2021/01/14 12:53:36.982] [tdepowersave] unmonitored device changed: /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/host6/target6:0:0/6:0:0:0/block/sdb//dev/sdb [2021/01/14 12:53:38.543] [kontact] processNewMail false,status=1 [2021/01/14 12:53:43.072] [kded] HomeDirNotify::FilesAdded [2021/01/14 12:53:43.072] [kded] HomeDirNotify::toHomeURL(media:/) [2021/01/14 12:53:43.072] [kded] result => KURL() [2021/01/14 12:53:43.073] [kded] SystemDirNotify::toSystemURL(media:/) [2021/01/14 12:53:43.074] [kded] system:/media/ [2021/01/14 12:53:43.074] [kded] MediaNotifier::onMediumChange( Unbekanntes Gerät 2-1.5:1.0, false) [2021/01/14 12:53:43.075] [kded] HomeDirNotify::FilesAdded [2021/01/14 12:53:43.075] [kded] HomeDirNotify::toHomeURL(system:/media/) [2021/01/14 12:53:43.075] [kded] result => KURL() [2021/01/14 12:53:43.075] [kded] SystemDirNotify::toSystemURL(system:/media/) [2021/01/14 12:53:43.075] [kded] KURL() [2021/01/14 12:53:43.075] [kded] HomeDirNotify::FilesChanged [2021/01/14 12:53:43.075] [kded] HomeDirNotify::toHomeURL(system:/) [2021/01/14 12:53:43.075] [kded] result => KURL() [2021/01/14 12:53:43.075] [kded] SystemDirNotify::toSystemURL(system:/) [2021/01/14 12:53:43.075] [kded] KURL() [tdeinit] Got EXEC_NEW 'tdeio_system' from launcher. [2021/01/14 12:53:43.109] [tdeio_system] SystemProtocol::listDir: system:/ [2021/01/14 12:53:43.109] [tdeio_system] SystemImpl::listRoot [2021/01/14 12:53:43.111] [tdeio_system] SystemImpl::createEntry [2021/01/14 12:53:43.112] [tdeio_system] path = /opt/trinity/share/apps/systemview/documents.desktop [2021/01/14 12:53:43.117] [tdeio_system] SystemImpl::createEntry [2021/01/14 12:53:43.117] [tdeio_system] path = /opt/trinity/share/apps/systemview/home.desktop [2021/01/14 12:53:43.119] [tdeio_system] SystemImpl::createEntry [2021/01/14 12:53:43.119] [tdeio_system] path = /opt/trinity/share/apps/systemview/media.desktop [2021/01/14 12:53:43.119] [tdeio_system] SystemImpl::createEntry [2021/01/14 12:53:43.119] [tdeio_system] path = /opt/trinity/share/apps/systemview/remote.desktop [2021/01/14 12:53:43.119] [tdeio_system] SystemImpl::createEntry [2021/01/14 12:53:43.120] [tdeio_system] path = /opt/trinity/share/apps/systemview/users.desktop
Anno domini 2021 Sun, 17 Jan 10:39:14 +0100 deloptes scripsit:
Dr. Nikolaus Klepp wrote:
Oh, I forgot: "media:/sdb" shows the same bad behaviour as "system:/media/sdb", so can I get rid of that, too?
I've been observing similar issues with NFS and I was thinking of filing a bug or looking into the whole TDEIO stuff, which I started doing recently, but it is too much spaghetti to eat :) I do not have the clear picture to be able to debug and I enabled debugging for TDEIO, so this is what I found for my exotic mobile phone. In the case of the mobile it works under system:/media/Unbekanntes Gerät 2-1.5:1.0/
I have not tried looking under /media/Unbekanntes Gerät 2-1.5:1.0/
I think you should file a bug for what you are experiencing
[2021/01/14 12:53:36.951] [tdepowersave] unmonitored device changed: /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/host6/target6:0:0/6:0:0:0/ [2021/01/14 12:53:36.975] [tdepowersave] unmonitored device changed: /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/host6/target6:0:0/6:0:0:0/block/sdb//dev/sdb [2021/01/14 12:53:36.982] [tdepowersave] unmonitored device changed: /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/host6/target6:0:0/6:0:0:0/block/sdb//dev/sdb [2021/01/14 12:53:38.543] [kontact] processNewMail false,status=1 [2021/01/14 12:53:43.072] [kded] HomeDirNotify::FilesAdded [2021/01/14 12:53:43.072] [kded] HomeDirNotify::toHomeURL(media:/) [2021/01/14 12:53:43.072] [kded] result => KURL() [2021/01/14 12:53:43.073] [kded] SystemDirNotify::toSystemURL(media:/) [2021/01/14 12:53:43.074] [kded] system:/media/ [2021/01/14 12:53:43.074] [kded] MediaNotifier::onMediumChange( Unbekanntes Gerät 2-1.5:1.0, false) [2021/01/14 12:53:43.075] [kded] HomeDirNotify::FilesAdded [2021/01/14 12:53:43.075] [kded] HomeDirNotify::toHomeURL(system:/media/) [2021/01/14 12:53:43.075] [kded] result => KURL() [2021/01/14 12:53:43.075] [kded] SystemDirNotify::toSystemURL(system:/media/) [2021/01/14 12:53:43.075] [kded] KURL() [2021/01/14 12:53:43.075] [kded] HomeDirNotify::FilesChanged [2021/01/14 12:53:43.075] [kded] HomeDirNotify::toHomeURL(system:/) [2021/01/14 12:53:43.075] [kded] result => KURL() [2021/01/14 12:53:43.075] [kded] SystemDirNotify::toSystemURL(system:/) [2021/01/14 12:53:43.075] [kded] KURL() [tdeinit] Got EXEC_NEW 'tdeio_system' from launcher. [2021/01/14 12:53:43.109] [tdeio_system] SystemProtocol::listDir: system:/ [2021/01/14 12:53:43.109] [tdeio_system] SystemImpl::listRoot [2021/01/14 12:53:43.111] [tdeio_system] SystemImpl::createEntry [2021/01/14 12:53:43.112] [tdeio_system] path = /opt/trinity/share/apps/systemview/documents.desktop [2021/01/14 12:53:43.117] [tdeio_system] SystemImpl::createEntry [2021/01/14 12:53:43.117] [tdeio_system] path = /opt/trinity/share/apps/systemview/home.desktop [2021/01/14 12:53:43.119] [tdeio_system] SystemImpl::createEntry [2021/01/14 12:53:43.119] [tdeio_system] path = /opt/trinity/share/apps/systemview/media.desktop [2021/01/14 12:53:43.119] [tdeio_system] SystemImpl::createEntry [2021/01/14 12:53:43.119] [tdeio_system] path = /opt/trinity/share/apps/systemview/remote.desktop [2021/01/14 12:53:43.119] [tdeio_system] SystemImpl::createEntry [2021/01/14 12:53:43.120] [tdeio_system] path = /opt/trinity/share/apps/systemview/users.desktop ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
LOL ... you have ended in the same mess I did some years ago, just I was not able to get decent debug output. Is there a way to get even more output, e.g. the passed parameters in detail?
Nik
Dr. Nikolaus Klepp wrote:
LOL ... you have ended in the same mess I did some years ago, just I was not able to get decent debug output. Is there a way to get even more output, e.g. the passed parameters in detail?
Don't know exactly - what I remember from one discussion on debugging - the compiling of debug messages in debian is not enabled by default, but I could be wrong as it was years ago (may be Slavek or Michele can confirm).
I compile the desktop for various reasons myself, so I have it at hand here. I use export DEB_BUILD_OPTIONS=debug
I don't know about parameters ... usually it depends what the debug functions is doing but usually it prints the parameters and the values or memory references if the debug symbols are available (it prints the signature and the memory references of the methods and properties).
On Sunday 17 January 2021, Dr. Nikolaus Klepp wrote:
Hi all!
Anno domini 2021 Sat, 16 Jan 19:41:35 -0800
William Morder via tde-users scripsit:
[...]
The problem is that Linux systems in general seem to have a problem sometimes with mounting a flash drive or SD card, but only after they have been used in another device, such as a smartphone or a non-Linux system.
I put a large music collection on a new SD card, for listening while I am outdoors walking, but when I went to change some of the items, now I find that my Linux system refuses to mount the drive. The same has happened with fat32 flash drives.
This does not happen with other hard drives, such as an external hard drive that is formatted NTFS; only with fat32 flash drives or (I forget the filesystem here) SD cards.
Also I believe that smartphones can really mess up the data on SD cards, as I had a lot of weirdness there. For example: a folder for one artist was instead filled with music from an entirely different artist. This could not have been a mistake on my part, as I have the originals, all tidy and organized, and the contents of the flash drive were first organized on a folder that resides in my desktop computer. Thus all I need to do is copy the contents of that folder to my SD card.
It is only when I tried to copy the contents of that SD card to another location, then suddenly everything got messed up.
So I believe that Kate might be onto something there, that formatting with Linux first could eliminate some of that mess.
Bill ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydes ktop.org
Looks like this is complints about FAT32 are not the cause of my observations. Please see the attached screenshot: upper half of windows uses system:/media/sdb and shows the describes malfuncions (i.e.: <del> not working, no autorefresh), the lower half shows the very device but where it's mounted in the filesystem as /media/toshiba and there it works as expected (i.e.: <del> working and autorefresh working).
So this is definitly a TDE problem. Is there a way to get rid of "system:/media/" and just use the real mountpoint instead?
Nik
Ok I just checked out all the media* options and delete appears in all of them. What distro are you using. Try using a live CD and see what happens.
Kate
Anno domini 2021 Sun, 17 Jan 13:52:12 -0500 BorgLabs - Kate Draven scripsit:
On Sunday 17 January 2021, Dr. Nikolaus Klepp wrote:
Hi all!
Anno domini 2021 Sat, 16 Jan 19:41:35 -0800
William Morder via tde-users scripsit:
[...]
The problem is that Linux systems in general seem to have a problem sometimes with mounting a flash drive or SD card, but only after they have been used in another device, such as a smartphone or a non-Linux system.
I put a large music collection on a new SD card, for listening while I am outdoors walking, but when I went to change some of the items, now I find that my Linux system refuses to mount the drive. The same has happened with fat32 flash drives.
This does not happen with other hard drives, such as an external hard drive that is formatted NTFS; only with fat32 flash drives or (I forget the filesystem here) SD cards.
Also I believe that smartphones can really mess up the data on SD cards, as I had a lot of weirdness there. For example: a folder for one artist was instead filled with music from an entirely different artist. This could not have been a mistake on my part, as I have the originals, all tidy and organized, and the contents of the flash drive were first organized on a folder that resides in my desktop computer. Thus all I need to do is copy the contents of that folder to my SD card.
It is only when I tried to copy the contents of that SD card to another location, then suddenly everything got messed up.
So I believe that Kate might be onto something there, that formatting with Linux first could eliminate some of that mess.
Bill ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydes ktop.org
Looks like this is complints about FAT32 are not the cause of my observations. Please see the attached screenshot: upper half of windows uses system:/media/sdb and shows the describes malfuncions (i.e.: <del> not working, no autorefresh), the lower half shows the very device but where it's mounted in the filesystem as /media/toshiba and there it works as expected (i.e.: <del> working and autorefresh working).
So this is definitly a TDE problem. Is there a way to get rid of "system:/media/" and just use the real mountpoint instead?
Nik
Ok I just checked out all the media* options and delete appears in all of them. What distro are you using. Try using a live CD and see what happens.
Which mount helper do you use? I have udisks2 here. I think I did not see that problem when I had pmount (but that had a different set of problems which I dislike more than that missing <del>.
Nik
Kate ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On Saturday 16 January 2021 19:10:20 Steven D'Aprano via tde-users wrote:
On Sat, Jan 16, 2021 at 11:44:27AM -0800, William Morder via tde-users
wrote:
'Twould be nice if Linux could handle fat32 sometimes without having to format it to a Linux filesystem.
What I mean is, these drives will not mount when using my Linux desktop, but they still work fine in other devices.
As far as I know, all Linux distros should be able to handle fat32.
man mkfs.fat
should give you the options for formatting drives as a FAT system. Normally you don't call that directly, but call it through `mkfs` with the -t option.
mkfs -t vfat <device>
I would expect that all modern Linux distros support full read/write permissions on FAT drives.
There's plenty of other people who have this issue, not just TDE:
https://duckduckgo.com/?q=linux+cannot+move+file+to+trash
To support "move to trash", your drive needs to have a hidden trash directory. That's the case for other desktops, I assume TDE requires the same. I think that's normally called something like .Trash-1000 where the number at the end is your user id.
Do you have write permission in top (root) directory of the USB stick? If you do an `ls -a` of that directory, can you see a hidden trash directory, and do you have permissions to write to it?
If you make any changes to the permissions, you probably should unmount and remove the USB stick, then remount it, just in case TDE doesn't spot the changes.
I enclosed a screenshot. Neither my SD card, nor flash drives, can be mounted; I have gone about it every which way. Once they have been used on another device, they become essentially unusable with my desktop. They cannot be mounted, formatted, or anything else.
When I try to mount them, I get an error message about permissions and fstab, but I've tried changing those. My Devuan Jessie system had no problems here, by the way. I found a web page with some nifty ideas about how to force auto-mounting, if so desired:
https://www.linuxquestions.org/questions/linux-newbie-8/how-can-i-automount-...
Since nobody else uses my desktop, this works for me; or rather, it used to work in my Jessie system. Now that I am running Devuan Beowulf, it doesn't work. It is long since that I hacked my system to behave as I wish about mounting, but none of it works any more since upgrading to Beowulf.
Bill
P.S. See attachments for a screenshot of the non-mounting SD card, as well as two other files which I got from the web page mentioned above.
On Sunday 17 January 2021, William Morder via tde-users wrote:
On Saturday 16 January 2021 19:10:20 Steven D'Aprano via tde-users wrote:
On Sat, Jan 16, 2021 at 11:44:27AM -0800, William Morder via tde-users
wrote:
'Twould be nice if Linux could handle fat32 sometimes without having to format it to a Linux filesystem.
What I mean is, these drives will not mount when using my Linux desktop, but they still work fine in other devices.
As far as I know, all Linux distros should be able to handle fat32.
man mkfs.fat
should give you the options for formatting drives as a FAT system. Normally you don't call that directly, but call it through `mkfs` with the -t option.
mkfs -t vfat <device>
I would expect that all modern Linux distros support full read/write permissions on FAT drives.
There's plenty of other people who have this issue, not just TDE:
https://duckduckgo.com/?q=linux+cannot+move+file+to+trash
To support "move to trash", your drive needs to have a hidden trash directory. That's the case for other desktops, I assume TDE requires the same. I think that's normally called something like .Trash-1000 where the number at the end is your user id.
Do you have write permission in top (root) directory of the USB stick? If you do an `ls -a` of that directory, can you see a hidden trash directory, and do you have permissions to write to it?
If you make any changes to the permissions, you probably should unmount and remove the USB stick, then remount it, just in case TDE doesn't spot the changes.
I enclosed a screenshot. Neither my SD card, nor flash drives, can be mounted; I have gone about it every which way. Once they have been used on another device, they become essentially unusable with my desktop. They cannot be mounted, formatted, or anything else.
When I try to mount them, I get an error message about permissions and fstab, but I've tried changing those. My Devuan Jessie system had no problems here, by the way. I found a web page with some nifty ideas about how to force auto-mounting, if so desired:
https://www.linuxquestions.org/questions/linux-newbie-8/how-can-i-automount -my-drives-in-debian-4175436306/
Since nobody else uses my desktop, this works for me; or rather, it used to work in my Jessie system. Now that I am running Devuan Beowulf, it doesn't work. It is long since that I hacked my system to behave as I wish about mounting, but none of it works any more since upgrading to Beowulf.
Bill
P.S. See attachments for a screenshot of the non-mounting SD card, as well as two other files which I got from the web page mentioned above.
Bill go into file associations > inode and see what's at the top of the list. It should be konqueror or your file manager of choice. Also check embedded. Should be konq_something or the like
Kate
On Sunday 17 January 2021 11:01:15 BorgLabs - Kate Draven wrote:
'Twould be nice if Linux could handle fat32 sometimes without having to format it to a Linux filesystem.
[SNIP]
Bill go into file associations > inode and see what's at the top of the list. It should be konqueror or your file manager of choice. Also check embedded. Should be konq_something or the like
Kate
Thanks, but I already found an adequate workaround solution for myself. It was included in the post under the heading "Re: Konqueror & FAT32 - SOLVED?"
Here is the web page that provided my solution: https://www.techwalla.com/articles/how-to-mount-an-sd-card-in-linux https://web.archive.org/web/20201023025122/https://www.techwalla.com/article...
When I get a free moment, however, I will try to format my flash drive. My reason for waiting is that it takes a LONG time to load music files onto a 128 gb SD card, when using a USB 1.0 hub. And in the meanwhile, I want to keep listening to music when I go outdoors for a walk.
Once I have a new, bigger flash drive, I will format that, then load music onto it. And then I will format the old one, too. Otherwise, I gotta wait for a week or so to get all the music loaded up again.
Bill
On Sun, Jan 17, 2021 at 11:20:15AM -0800, William Morder via tde-users wrote:
Thanks, but I already found an adequate workaround solution for myself. It was included in the post under the heading "Re: Konqueror & FAT32 - SOLVED?"
Here is the web page that provided my solution: https://www.techwalla.com/articles/how-to-mount-an-sd-card-in-linux https://web.archive.org/web/20201023025122/https://www.techwalla.com/article...
And doing that brings back the "Delete" functionality in TDE?
[...]
Once I have a new, bigger flash drive, I will format that, then load music onto it. And then I will format the old one, too. Otherwise, I gotta wait for a week or so to get all the music loaded up again.
You don't have an old USB stick or SD card you can experiment on? I still have the very first USB stick I ever purchased, with 128MB on it. Very handy as a scratch disk.
On Sunday 17 January 2021 13:06:07 Steven D'Aprano via tde-users wrote:
On Sun, Jan 17, 2021 at 11:20:15AM -0800, William Morder via tde-users
wrote:
Thanks, but I already found an adequate workaround solution for myself. It was included in the post under the heading "Re: Konqueror & FAT32 - SOLVED?"
Here is the web page that provided my solution: https://www.techwalla.com/articles/how-to-mount-an-sd-card-in-linux https://web.archive.org/web/20201023025122/https://www.techwalla.com/arti cles/how-to-mount-an-sd-card-in-linux
And doing that brings back the "Delete" functionality in TDE?
The "delete" functionality never went away for me. But Nik also mentioned problems with system:/media and media:/
... and somehow this led into problems with mounting of flash drives and SD cards.
[...]
Once I have a new, bigger flash drive, I will format that, then load music onto it. And then I will format the old one, too. Otherwise, I gotta wait for a week or so to get all the music loaded up again.
You don't have an old USB stick or SD card you can experiment on?
My next-door neighbor blew the fuse here, on a shared electrical circuit. (Much of San Francisco is like living in a third-world country, but without the friendliness.) This fried a flash drive, and now I only have one left.
I still have the very first USB stick I ever purchased, with 128MB on it. Very handy as a scratch disk.
I know, it's this damned lockdown. Everything now is a terrible bother; to go out to local shops for computer gear requires that I call ahead, then go in to pick up my items. I would prefer to go to an actual *place*, somewhere outside in the real world, not just to order online. For one thing, I like to browse a little, to think about what else I might need, for now or later. Also I like to ask questions, so I am better able to decide.
Anyway, all in good time. There is nothing else to do but wait.
Bill
B
[SNIP!!!]
<On Saturday 16 January 2021 19:10:20 Steven D'Aprano via tde-users wrote:
<So I believe that Kate might be onto something there, that formatting with Linux first could eliminate some of that mess.
Check out this web page: https://www.techwalla.com/articles/how-to-mount-an-sd-card-in-linux https://web.archive.org/web/20201023025122/https://www.techwalla.com/article...
Okay, so this solves my own problem with getting my SD card to mount in an external reader. I had to adjust the commands slightly to fit my own /dev/sd-, and also my SD card is exfat rather than vfat. Once I did that, it worked like a charm, and now I can browse the files on my SD card again for the first time in ages.
It occurs to me that the same idea might be adapted by Nik to get those pesky flash drives to mount. What do you think?
Bill