View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0018674 | MMW 5 | General | public | 2021-12-15 00:45 | 2022-09-14 14:39 |
Reporter | peke | Assigned To | |||
Priority | high | Severity | minor | Reproducibility | always |
Status | feedback | Resolution | open | ||
Product Version | 5.0.2 | ||||
Target Version | 5.2 | ||||
Summary | 0018674: MediaMonkey crashes when Write rights are missing | ||||
Description | User at Ticket 3236 pointed out that each time he uses MM he gets MediaMonkey.ini can't be created error. It is case when MM do not have enough rights to Modify/Write to MediaMonkey.ini (this also affect other files that MM tries to open Modify/Write access (eg. MM5.DB/Persistent.json/....) Beside constant can't create MediaMonkey.ini MM crashes on close with error runtime error 214. Possible Solutions: a) Workaround even there is no Write/Modify permission available is to Rename MediaMonkey.ini to 1MediaMonkey.ini -> copy all values from 1MediaMonkey.ini to newly created MediaMonkey.ini -> kill existing MM processes -> restart MM again. b) Load MediaMonkey.ini in read-Only mode -> Auto rename MediaMonkey.ini -> Mediamonkey.ini.temp and Delete it if Write access is obtained or Rename it again to Mediamonkey.ini (???).fail* in case it can't be accessed for deletion. * = (???) means number of duplicated fail attempts WARNING: In case of Portable installation to prevent MM starting as normal installation Values from old INI files eg. 1MediaMonkey.INi as newly created MediaMonkey ini would not contain [Portable] section. NOTE: This should also apply to all other essential MM files like MM5.DB | ||||
Steps To Reproduce | 1. Install MM5 As Portable -> Start and Close it 2. Edit Permissions to MediaMonkey.ini (Disable inherited permissions) so that Only Read and Read and Execute rights are allowed for all listed (See attached Picture) 3. Start MM 4. It will start but will constantly show dialog that MediaMonkey.ini can't be created even it is correctly read on start. 5. Closing MM would result in Runtime error 214 and MM.exe processes will not terminate. | ||||
Additional Information | Ticket # 3236 | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
|
|
I guess that showing the "access is denied" error is just fine as it is true, the only problem is that in debug build it also generates debug log to submit (although it is not MM error). So unless you want to show a native MM message dialog explaining better what is going on and what the user needs change (with another wording) this is just fine. |
|
I would only Show unified dialog instead of error that file not accessible for writing instead of runtime error, Also it would be best if New INI can be created eg. mediamonkey.ini.tmp that which would trigger MM to check if mediamonkey.ini is writable on next start and use .tmp meantime. Another case was found where Could sync and backup apps lock file till backup is not finished that prevent MM to save to file. This is also non standard usage, but adds another twwo cases when this can happen. |