Differences

This shows you the differences between two versions of the page.

--- bugs_known_issues [2021/09/05 08:37] – gordonj
+++ bugs_known_issues [2024/05/04 08:58] (current) – johnsanc
@@ Line 1: / Line 1: @@
-====== Known Issues ======
+~~NOTOC~~
+====== Bugs & Known Issues ======
-  * If a file has permissions that disallow deletion during a fix operation, RomVault with throw a friendly error. Upon dismissing this message a hard crash will occur with an error and the cache will become corrupted. RomVault will not start again until the corrupt cache file is removed.
+<WRAP tip>Help us help you! If you find a bug or experience a crash, please report it on the [[https://discord.com/channels/619198661838241795/622121052364865591|ROMVault Discord in the bug-reporting channel]]. Its always helpful to provide context around your setup, details about when the crash occurred, screenshots, and how to reproduce (if possible).</WRAP>
-  * If a file is in use by another process during a fix operation on that file, RomVault will crash and throw an error. At this point the cache will be out of sync with the files on disk and a rescan will be needed.
+<WRAP important>**All bugs and feature requests are tracked on Convas. Please refer to the [[https://romvault.convas.io/bugs|RomVault Bug Tracker]] before reporting any bugs.** \\ Feel free to add any new bugs discovered along with relevant info to reproduce the issue.</WRAP>
-  * A fix operation on a 7z file can leave orphaned files in the 7z cache directory. It appears these orphaned files are then completely ignored  by RomVault, even if they match a file in a DAT.
-  * Single Archive settings do not work properly unless the DATs are each in their own folder.
-  * If the Single Archive + No SubDirs settings are used when a DAT is NOT in its own subfolder in the DATRoot, then subdirectories are still created. If the DAT is in its own subfolder, then the settings work as expected. This issue has been reported by people who are also using "File" as the Archive Type.
-  * If you generate fixDats on directories that are using the Single Archive setting with "Add SubDirs if multiple roms" then RomVault will crash with an error. The text reports will not cause a crash, but the reports will not include any information from the directories using Single Archive. This may also occur under other directory setting scenarios but this is unconfirmed.
-  * DATs with zero entries are automatically selected in the tree after a DAT Update, even if the DATs did not change.
-  * The side icons are not visible when RomVault is used on Linux. This is likely a PNG transparency issue.
-  * Corrupt archive icons are only displayed at levels above the directory where the corrupt archive resides. E.g. an archive sitting in the base directory of your ToSort will not appear as corrupt when clicking on ToSort in the tree.
-  * Files can be deleted in certain scenarios with unrecommended directory settings. For example, if you map a directory in your RomRoot to a ToSort directory then a fix operation will delete files that RomVault thinks are not needed because they reside elsewhere. In this case the directory deleted from and the location of the undeeded roms are the same. An extra check is needed to prevent unwanted deletions.
-  * Files without read permissions are completely skipped by RomVault with no indicators. Ideally these files should be flagged with a blue status.
-  * RomVault throws a "Rescan needed" error during a fix operation if the fix is to correct the character case of the ROM. If you close this error and attempt the fix again, RomVault proceeds past this error. A rescan is not required.
-  * Missing counts in the tree and summary panes include ROMs that are in blue locked status. For example, an unneeded locked file will count as missing even if you have all other ROMs marked as "Have."
-  * If RomVault does not have proper access to a directory, scanning an uncompressed file in that directory will throw a "ZipErrorOpeningFile" error. This is unrelated to opening a zip file.
-  * The Dat Info pane can display information that does not reflect what is selected in the tree. This can be reproduced by navigating with right and left clicks in the right pane. (Fixed, in next release.)