Scribus 1.6.4 and Linux Mint 22.2 Cinnamon [looks like a bug]

Previous topic - Next topic

Flaxx

I'm using Scribus for quite a while on a dual-boot-system with Win 11 Pro and Linux Mint 22.2 Cinnamon, both installed on separate drives. My data usually are stored from both sides on a data drive that has to be mounted from Linux side (the latter is NTFS, of course).

While it is no problem opening or storing files on a USB stick or a "real" external drive, I failed when trying to open any other location than the preselected path in "Preferences". The same happens vice versa: When opening a new document I only can use the preselected path - in standard settings it only shows "/" as starting point and the Linux file system.

All drives, including some history (why it's there???  :-[ ) are grayed out and not accessible. "History" means that I can see not only always available local drives, but as well USB-Sticks
that had not been connected for weeks. While Scribus forgets any former document if the containing drive is not mounted before booting the application, it seems that some history is still somewhere stored.

However, the behavior is strange as I can access any location (and if I want so, even mount other permanent drives) if I'm exporting to PDF or other available formats. The import dialogue seems to work as well.

I tried the following cases:

1) Standard path settings, File -> Open...: All is grayed except the Linux file system. When trying to follow the usual Linux conventions it doesn't help.
1a) Path points towards a Windows drive: As above, but the starting path shows the preselected one.

In both cases a mounted USB-stick can be selected, even if it's grayed out.

2) While in the some file-opening-process: after trying to open any other drive, the previous preselected path only shows the Linux file system when trying to click on the respective drive. USB is still accessible.

2a) Same Scribus session, still no file is open: Starting the above procedure again, it shows now both drives as present, the preselected one and the USB.

I think, this is no feature. However, if the error sits here in front of the screen, please give me a hint where I can fix this behavior. Of course I can circumvent it, but it's not the usual work flow.



AdmFubar

Quote from: Flaxx on December 22, 2025, 05:41:24 PMI'm using Scribus for quite a while on a dual-boot-system with Win 11 Pro and Linux Mint 22.2 Cinnamon, both installed on separate drives. My data usually are stored from both sides on a data drive that has to be mounted from Linux side (the latter is NTFS, of course).
Quick question on this data drive. It is NTFS? and you are writing to it from linux? If so, stop that immediately! The NTFS drivers are for read only from linux. Your best bet is to have your data drive as a fat32. and consider exfat for the thumb drives.
Using Scribus1.6.1, 1.7.0 openSUSE 15.6
Advanced hobbyist

Flaxx

Quote from: AdmFubar on Today at 03:54:45 AMQuick question on this data drive. It is NTFS? and you are writing to it from linux? If so, stop that immediately! The NTFS drivers are for read only from linux. Your best bet is to have your data drive as a fat32. and consider exfat for the thumb drives.
Interesting proposal. I know that almost all drive formats at Linux side are more safe than everything coming from MS, but I can't see any restriction that would prevent writing from Linux on NTFS drives. In my case: all data written on this drive is mirrored on a NAS and from time to time to an external USB-device. And yes, exfat is the best for thumb drives.

However, I'm just a user and really interested to learn the technical background. I'm reading and writing to NTFS for years now without any problem, but I know of course that NTFS can't heal itself.

Actually, the day Windows will turn running exclusively as a service only, I will bite the bullet, leaving my windows payware behind. Meanwhile I hope that more and more companies are opening the market and supporting Linux solutions. At the moment FOSS has an inherent weakness: it often depends on only a few devs, if not just one.

Regarding my posted problem: I think I've found the reason. Scribus obviously has problems with drives being connected via /mnt/ as I wanted the drive being connected by using its Label while Mint started to use its uid - I still have no idea why. I commented out the respective line in my fstab and now it works as wanted: connected via /media/<user>/<Drive-Label>/...