Destination file already exists error is annoying.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Low
|
Sean M. Pappalardo |
Bug Description
Some users switch back and forth between Mixxx versions (this is not that uncommon). This is even more likely to be the case if our 1.7.0 beta doesn't work well for people. After upgrading from 1.6.1 to 1.7.0, Mixxx moves your configuration files over to their new .mixxx/ location. However, if you run 1.6.1 again, and then run 1.7.0 after it, Mixxx will complain that it can't overwrite the .mixxx/ files. (It will see your 1.6.1 config files, try to move them, and complain because the 1.7.0 files will already be there.)
The error sequence in the console looks like this:
Warning: [Main]: "Error moving your library file /Users/
" The destination file already exists.
Warning: [Main]: "Error moving your settings file /Users/
" The destination file already exists.
Warning: [Main]: "Error moving your configuration file /Users/
" The destination file already exists.
It also pops up a super-annoying error message. This error message should be removed, to make it fail silently, at least.
Thanks,
Albert
Changed in mixxx: | |
assignee: | nobody → pegasus-renegadetech |
importance: | Undecided → Low |
milestone: | none → 1.7.0 |
status: | New → Confirmed |
Changed in mixxx: | |
status: | Fix Committed → Fix Released |
So how should we handle these instances? Overwrite the new version's files with those from the old version? Or just do nothing as currently but switch to a qDebug instead of a qWarning?