Ask Your Question

estrauch's profile - activity

2019-03-31 15:56:41 -0500 marked best answer Udev mounted USB HD cannot write special characters

After upgrading to F29, I noticed I was getting errors on backups to external USB Hard Drive. At first I thought it was an issue with rsync. Then I discovered that the USB HD filenames would not accept special chars like ? and : Looking at /etc/mtab, I see the HD mount options as shown below.

/dev/sdb1 /run/media/estrauch/FantomHD fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0

If I knew how to add mount option, iocharset=ascii, that would fix the problem. But digging into udev rules is a little beyond me.

Any ideas?

2019-03-31 15:56:41 -0500 received badge  Scholar (source)
2019-03-31 15:56:40 -0500 commented answer Udev mounted USB HD cannot write special characters

Yes, that is the solution I'm looking for. I will need to backup my backup drive, and re-format as ext4. Thank you.

2019-03-30 16:41:08 -0500 commented answer Udev mounted USB HD cannot write special characters

I agree that these characters are not wise to use. However I do have files like "what?.flac" already on the external har

2019-03-30 15:22:59 -0500 received badge  Rapid Responder (source)
2019-03-30 15:22:59 -0500 answered a question Udev mounted USB HD cannot write special characters

Acutally the characters ? : are ascii characters. But when I do touch x\? to a Hard drive directory, I get following err

2019-03-30 12:50:17 -0500 asked a question Udev mounted USB HD cannot write special characters

Udev mounted USB HD cannot write special characters After upgrading to F29, I noticed I was getting errors on backups to

2017-09-13 13:44:56 -0500 received badge  Famous Question (source)
2017-09-12 12:59:29 -0500 received badge  Popular Question (source)
2017-09-12 12:59:29 -0500 received badge  Notable Question (source)
2017-07-14 08:06:11 -0500 commented answer F26 Tiger VNC server still has blank screen.

Changing 'exec gnone-session' to just 'gnone-session' in startup did fix error message "Failed to import environment". Still blank screen.

2017-07-14 08:02:24 -0500 commented answer F26 Tiger VNC server still has blank screen.

yes I did this.

2017-07-13 10:57:19 -0500 commented answer F26 Tiger VNC server still has blank screen.

This bugzilla thread provides a patch for the SELinux problem. I'm just disabling SELinux for now using 'setenforce 0' command. Additionally, it suggests adding Environment=XDGSESSIONTYPE=x11 to vncserver@.service file. I tried that but still same problem, i.e. "Failed to import environment: Process org.freedesktop.systemd1 exited" message in .vnc/<host>:1.log file. Running vncserver from command line works just fine, but not from systemctl. It appears the problem may be that systemctl tries to run vncserver as root, as I get the sudo password prompt.

2017-07-13 00:27:27 -0500 commented question F26 Tiger VNC server still has blank screen.

When I run vncserver :1 from command line, it works. When I run from systemctl, I get this error message in $HOME/.vnc/<hostname>:1.log Failed to import environment: Process org.freedesktop.systemd1 exited with status 1

2017-07-12 13:34:31 -0500 received badge  Student (source)
2017-07-12 13:26:48 -0500 asked a question F26 Tiger VNC server still has blank screen.

The vncserver 'black screen' issue persists into Fedora 26. Here are the workarounds I've done so far. 1) Disable SELinux (setenforce 0) so I can get vncserver running using systemctl. 2) Login using 'GNOME on Xorg' for both server and client. 3) On the server, edit $HOME/.vnc/xstartup. Replace 'exec /etx/X11/xinit/xinitrc' with 'exec gnome-session'.

The vncviewer comes up with cursor working, but always a blank screen. This appears to be a GNOME display manager issue.