- This topic has 32 replies, 6 voices, and was last updated Nov 7-7:25 pm by rej.
-
Posts
-
rej
BobC-
IceWM – SpaceFM produce same results.
stock a antiX 19 system
Not understanding what this means – I clean installed on the same machine changing nothing, except connecting WiFi – update/dist-upgrade and the result is the same.
Fully configured install produces the same behavior as “no changes” installation.
Variables tried, came after what was initially done below:
========
(Files were transferred from of a regular Kingston USB flash drive copied and pasted to home/documents folder)use a SpaceFM root session if you need to for mounting a device or changing permissions. Select them all (you can mark directories too) and hit copy.
use a SpaceFM normal user session to paste the files into somewhere under /home and in a separate folder, paste them in. They will now be owned as you.
Opened SpaceFM through terminal in root. -selected and copied files and folders all together in root and pasted into new test folder created in home.
in the normal user session, mark all that you need to change (Ctrl+A for all) the any particular permission to a certain value for, then right click, then click properties, then permissions. In the box that comes up, dash means leave whatever is there alone, check sets it, and empty clears it.
In home/test folder selected all files and folders – properties – permissions – unchecked execute on all 3 – checked recursive – OK.
in the normal user session, check the permissions are correct, now move them where you want them to go.
Result – files that are not in folders are now r&w, folders are now denied access.
Screen shots are:
– “denied access of folders” after change is made.
– unchanged files in the home/documents folder comparing the changed documents in the newly created test folder in home.
———–
It appears that the owner does not change.Anonymous
When you placed copies of “the antiX17 files” onto a FAT32-formatted pendrive for transfer, all their “permissions settings” were lost because FAT32 has no means to store the permission details.
lookit (quick background reading, toward understanding a couple concepts):
https://askubuntu.com/questions/555790/where-does-ubuntu-save-user-permission-of-a-file
and
https://linoxide.com/linux-command/linux-inode/#What_is_an_inode_in_LinuxWhen the antiX 19 system reads that FAT32 pendrive, regardless which file manager you use, valid permissions aren’t found. For any files you copy onto the antiX19 filesystem from the FAT32-foratted pendrive, the file manager (or the underlying filesystem) falls back to applying a default permissions mask ~~ and you wind up with all the copied files now “owned by root, and marked as accessible to all”.
If you must copy from PC to pendrive to OtherPC (meaning: for some reason you cannot use sftp or samba or whatever to transfer directly PC-to-PC), you can avoid the permissions mangling by using a pendrive which has been formatted as ext4 (not fat32, not exfat, not ntfs). Back in the day, if the file copy was successful… you were apparently using a suitably-formatted pendrive during the transfer.
BobC
You didn’t say you did the copy from the root session and the paste from the separate user session.
I would suggest keeping it as simple and small as possible,
trying just one folder with 2 or 3 files.If you did it how I said, then my guess is that you have ownership and/or permission problems, and would suggest looking at things in detail view not as icons, and from a terminal session so the gurus can spot the problem. The icons look pretty but are only telling a little piece of the story.
rej, in case you are stuck with only a FAT32-formatted pendrive in hand & don’t want to reformat it b/c it also contains “other stuff, which must be readable from windows PCs” here’s a workaround:
On the antiX 17 system, launch spaceFM and right-click }}} New }}} Archive.
Name the archivefile “transfer.tar.gz” or similar.
Right-click the new archivefile in spaceFM }} Open }} “archive manager”.You can drag the archive manager app window off to the side and, browse across your folders (using rox or spacefm) and drag/drop any items of interest onto the archivemanager window. After you have gathered the items of interest, copy the transfer.tar.gz file onto the pendrive.
-=-
When you copy transfer.tar.gz from the pendrive onto another system, you’ll only need to “sudo chown rj:rj /path/to/transfer.tar.gz” then, (as user “rj”) OpenWith archive manager. Then (as user “rj”) launch a file manager and you can drag items from the archive manager window to desired locations in the file manager and the original permissions will be preserved._____________________
(note to self: I installed in a fresh antiX 19 instance “pcmanfm” and “pcmanfm-qt” and noted that pcmanfm uses 27MB ram, pcmanfm uses 45MB ram. In comparison, spaceFM (gtk2 version) uses 48MB and rox-filer uses 47MB.I agree with skidoo.
That also applies if it’s a FAT16 formatted drive. I have had that problem with flashdrives formatted by my work PC.
skidoo-
Thank you.
I had no problem with fat32 [default] file system flash drive – deleting all in GParted and re-formatting to ext4.
The problem came in MX18, having it reject the files. The drive would no longer have files pasted, dragged or sent to it. Re-formatted again to make sure nothing else had gone wrong – same rejection of files on second attempt. Restored it to its default fat32 and the files were readily accepted on the drive.
As long as I have used MX, antiX, and Debian, the same files have been transferred on the same default formatted drives. The large storage HDD drives are probably ntfs and all the flash drives are Fat32, except for two Kingston 64gb drives which are exfat and I almost never use them for anything. Have not had a problem with imported files until antiX 19.
When I have tested various desktop environments in MX and antiX, and had a problem with them, I found an O.S. that natively uses that DE, installed it on an external HDD/SSD drive and set it up with the same configurations to see how it operates within, and could usually solve the problem present in antiX/MX that way. Again, never had any issues with transferring the files to these test operating systems.
antiX 19, on clean install or boot media, just tried one test file – freshly made with Leafpad in antiX 17 – the same executable result. From that, I surmised that it had nothing to do with something that is being mixed in with the large mass of files, folders and sub-folders that I usually start off with, on a normal installation.
This was tested on nVidia and Intel graphics laptops, used various kernels and drivers – makes no difference.
When the desktop manager was switched from SLiM to LightDM, got black wallpaper, however, when the mass of files were imported and copied into the empty home/documents folder, they displayed properly, with SpaceFM/Rox filer and opened normally in Rox filer. (With SLiM, when clicked on in Rox filer, they do not open.)
When the DM was switched back to SLiM, the files/folders still opened as they normally should, and displayed properly. This is certainly not a resolve or finding the cause, but the best solid work-around I have found to use with a huge amount of imported files and folders at once. Rebooted several times to make sure it stayed that way.
The file issue appears to arise with SLiM only. antiX 17 SLiM has never had issues like this.
Also, when logout-shutdown is selected in SLiM, it often goes [not always] to the login screen instead, and once back in, the second shutdown, shuts it down correctly. This does not seem to occur with LightDM – it flashes briefly to the login then shuts down normally.
At the end of one of your posts, there is a note regarding “pcmanfm-qt”. This worked when it was tested in antiX 17. However, it did not work well in 19, and neither did the “Open Folder as root” work after the same configuration was used as 17.
anticapitalista
Can you post your /etc/slim.conf file.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
BobC-
Thanks again for all your help.
You didn’t say you did the copy from the root session and the paste from the separate user session.
In the previous post I wrote “Opened SpaceFM through terminal in root. – selected and copied files and folders all together in root and pasted into new test folder created in home”. Had a SpaceFM window open as “root” and one next to it opened as regular user. Is this not what you meant?
Hopefully, the attached screenshots will present a simplified view of what was done, using just one folder.
Looks like this process does not work with the folders and there are too many folders and sub-folders to adjust them one by one emptying them out. It is a very good method for transferring a few folders with only files in it.
I understand what you mean about using icons for screenshots and will change if they are default – good to know.
Switching the desktop manager to import the initial folders and files and then changing it back again is probably the most practical/easiest work-around for now.
It would be nice to know what has changed between 17 & 19 that is causing this issue.
BobC-
Last screenshot – needed a separate post – because of a size limit.
Attachments:
anticapitalista –
Thank you for your help.
# Path, X server and arguments (if needed) # Note: -xauth $authfile is automatically appended # default_path /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games default_xserver /usr/bin/X11/X xserver_arguments -dpi 130 -nolisten tcp # Commands for halt, login, etc. on antiX halt_cmd /usr/local/bin/persist-config --shutdown --command halt reboot_cmd /usr/local/bin/persist-config --shutdown --command reboot console_cmd /usr/bin/urxvt -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue.net; exec /bin/login" #suspend_cmd /usr/sbin/suspend # Full path to the xauth binary xauth_path /usr/bin/X11/xauth # Xauth file for server authfile /var/run/slim.auth # Activate numlock when slim starts. Valid values: on|off # numlock on # Hide the mouse cursor (note: does not work with some WMs). # Valid values: true|false # hidecursor false # This command is executed after a succesful login. # you can place the %session and %theme variables # to handle launching of specific commands in .xinitrc # depending of chosen session and slim theme # # NOTE: if your system does not have bash you need # to adjust the command according to your preferred shell, # i.e. for freebsd use: # login_cmd exec /bin/bash -login /etc/X11/Xsession %session #################OLD COMMAND#################### # login_cmd exec /bin/bash -login ~/.xinitrc %session >~/.xsession-errors$DISPLAY 2>&1 ################################################ #LOGIN COMMAND FOR DESKTOP SESSION BELOW# ############################################################################################# login_cmd setsid /usr/local/bin/desktop-session %session ############################################################################################# # login_cmd exec dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1 # Commands executed when starting and exiting a session. # They can be used for registering a X11 session with # sessreg. You can use the %user variable # # sessionstart_cmd some command # sessionstop_cmd some command # Start in daemon mode. Valid values: yes | no # Note that this can be overriden by the command line # options "-d" and "-nodaemon" # daemon yes # Available sessions (first one is the default). # The current chosen session name is replaced in the login_cmd # above, so your login command can handle different sessions. # see the xinitrc.sample file shipped with slim sources #sessions rox-fluxbox,space-fluxbox,fluxbox,rox-icewm,space-icewm,icewm,rox-jwm,space-jwm,jwm,herbstluftwm sessiondir /usr/share/xsessions # Executed when pressing F11 (requires scrot) screenshot_cmd scrot /root/slim.png # welcome message. Available variables: %host, %domain welcome_msg (Press F1 to toggle sessions) # Session message. Prepended to the session name when pressing F1 # session_msg Session: # shutdown / reboot messages shutdown_msg The system is shutting down... reboot_msg The system is rebooting... # Focus the password field on start when default_user is set # Set to "yes" to enable this feature #focus_password no # Automatically login the default user (without entering # the password. Set to "yes" to enable this feature auto_login yes # default user, leave blank or remove this line # for avoid pre-loading the username. default_user rj # current theme, use comma separated list to specify a set to # randomly choose from current_theme BlueLines #current_theme BlueLinesLight #current_theme antiXIce #current_theme DarkCity #current_theme PrettyPink #current_theme SunnyDay # Lock file lockfile /var/run/slim.lock # Log file logfile /var/log/slim.logrej, I try to find a way that works to do a particular task, and once I’ve done that I keep doing it and try not to change things. Otherwise the permutations of things that could go wrong increase geometrically. Slim vs Lightdm… I can’t get lightdm to work. Not that it causes a problem for you or doesn’t, I wouldn’t know.
My rule is copy with root, paste with user. When you paste, I would expect the pasted files to have the user id of the person creating them.
Maybe that doesn’t work on yours. Maybe find a work around, ie change owner and group, recursive, by moving to a temporary place first, adjust everything to how you want it, and then move to a permanent location.
I suggest don’t put spaces or weird characters in file or folder names. That is trouble prone. Use a terminal to look at who owns what and what the permissions are. It’s a lot easier to understand that way.
ls -laR ~/.icewmthen copy the screen data, and paste it into code blocks. I think that will help you solve your problems just being able to see and understand what its doing so you can adjust what you are doing as needed to achieve the results you want. The slim and lightdm stuff is way over my head.
- This reply was modified 3 years, 6 months ago by BobC.
anticapitalista
rej – long shot – is your username password the same as your root password?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
anticapitalista-
Thanks – no, root password is much longer.
There was a very nice review of antiX 19 Oct 22, 2019 26:44 minutes into the Youtube video. Michael Tunnell @ TuxDigital
[https://www.youtube.com/watch?v=YsY8op8mz4Q]
- This reply was modified 3 years, 6 months ago by rej.
BobC-
Sorry – left out that I had to install Xfce to get LightDM running. Works well in IceWM, except for the unchangable black wallpaper. As soon as the files get transferred in with the proper permissions, the DM gets change the DM back to SLiM and reboot. Those imported files remain with the correct permissions and behavior.
My rule is copy with root, paste with user. When you paste, I would expect the pasted files to have the user id of the person creating them.
The screenshot #1 [in prior post] shows copied from root in home/documents, where the files were imported to in the first place, from the USB flash drive. Then in “root”, pasted to the “Test BobC” folder that was created in home/rj. “Owner” appears to be the same.
Maybe my question should be “How would I copy from “root” in a root window of SpaceFM and paste those files with the regular “user” SpaceFM, if the copied files come from “root” instance?”
Screenshot #2 shows where they originated, where they were copied to, and who has ownership before and after, in the untouched “home/rj/documents” and the “Test BobC” folder that was created in home/rj and has changed permissions as indicated.
Screenshots #3. 4 & 5 show the results in SpaceFM and Rox filer.
In Rox filer, “Test BobC” folder, the details on the files in the root instance
of Rox filer show that the individual files are still “executable” and on the right, the regular “user” window of SpaceFM, shows the “File (Folder) doesn’t exist” notification.
In SpaceFM, original home/rj/documents folder show that the individual files are still “executable” however the notification in the “Test BobC” folder window of SpaceFM, is “Permission denied”.
Attachment #6 in this post shows more clearly the folder permissions after changing.
Previous attachment #3 had left out the very end of them.Attachments #7 & #8 in this post show results after copying changed folder in “Test BobC” to home/rj/downloads – the same: “denied”.
It might be that since you are not experiencing this file permissions issue on your devices, that this works on your system, and this method might not work for someone who is experiencing it? There may be other complications involved. Can’t imagine what, since it does this with a freshly made leafpad text file from antiX 17, transferred to the 19 USB boot installation home/demo/documents folder.
I am OK with temporarily running LightDM to import a large mass of folders and files, and then switching it right back to SLiM afterwards for now. Hopefully, I will eventually find the source of the problem in 19 and correct it.
I don’t think there are any weird characters in folder or file names. Sometimes hyphens. Never had an issue with spaces to separate the words, as long as they are not on the end of the title.
rj@antix19rj:~ $ ls -laR ~/.icewm /home/rj/.icewm: total 104 drwxr-xr-x 2 rj rj 4096 Nov 2 14:57 . drwxr-xr-x 27 rj rj 4096 Nov 5 23:06 .. -rw-r--r-- 1 rj rj 5058 Aug 15 13:38 keys -rw-r--r-- 1 rj rj 3915 Nov 2 10:55 menu lrwxrwxrwx 1 rj rj 48 Sep 8 10:06 menu-applications -> /usr/share/desktop-menu/.icewm/menu-applications -rw-r--r-- 1 rj rj 4011 Sep 8 10:06 menu-numix-bevel -rw-r--r-- 1 rj rj 4030 Sep 8 10:06 menu-numix-square -rw-r--r-- 1 rj rj 3981 Sep 8 10:06 menu-papirus -rw-r--r-- 1 rj rj 166 Jun 27 2015 personal -rw-r--r-- 1 rj rj 38668 Nov 2 14:57 preferences -rwxr-xr-x 1 rj rj 12 Mar 31 2015 startup -rw-r--r-- 1 rj rj 37 Aug 20 13:50 theme -rw-r--r-- 1 rj rj 471 Jun 18 09:03 toolbar -rw-r--r-- 1 rj rj 483 Jun 18 09:03 toolbar-numix-bevel -rw-r--r-- 1 rj rj 487 Jun 18 09:04 toolbar-numix-square -rw-r--r-- 1 rj rj 471 Jun 18 09:03 toolbar-papirus -rw-r--r-- 1 rj rj 1142 Oct 21 2010 winoptions rj@antix19rj:~rej,
Yes, I copy from a flashdrive as root, and paste into a user window as me.
This might not show the real cause because it isn’t in ~/ , ie the problem might have originated with the flashdrive, but what I’m trying to get across is that there are many things you would need to know that you don’t have on those screens, even if everything was normal.
This will show you what is in your home folder, who owns it, and what the permissions are, all on one page.:
ls -laR ~/You are way beyond my ability here.
- You must be logged in to reply to this topic.
