Missleading error meassage when settingsPath can not be accessed

Bug #1650190 reported by Daniel Schürmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Triaged
Medium
Unassigned

Bug Description

When there are no write permissions in the setting path given by "mixxx --settingsPath", Mixxx is complaining that it can not establish a database connection.
This is missleading. Instead it should complain about the settingsPath permissions.

Tags: easy
tags: added: easy
description: updated
Changed in mixxx:
importance: Undecided → Medium
summary: - Missleading error meassage when settingsPath does not exists
+ Missleading error meassage when settingsPath can not be accessed
description: updated
Revision history for this message
Nimit Bhardwaj (nimitbhardwaj) wrote :

I have found the cause of the bug, now I am solving it, its cause is in src/library/trackcollection.cpp , this happens in the constructor, which calls the open function, and results in unfaithful error message, I am going to fix it

Changed in mixxx:
assignee: nobody → Nimit Bhardwaj (nimitbhardwaj)
Revision history for this message
Sébastien BLAISOT (sblaisot) wrote :

I don't think it should complain about settingspath not being writable.
It should complain about not being able to create the database file (with a user-friendly "unable to write database file to settingspath/database.sql" instead of "unable to establish a connection to database".

Trying to write to the settings path once, then relying on the result of this test to assume later it will stay writable during the whole mixxx session is imho a misconception.

Revision history for this message
Sébastien BLAISOT (sblaisot) wrote :

don't forget that settingspath is usually in $HOME and historically UNIX $HOME can be an NFS share whose ability to write in depends on network availability. Not a common setup for home desktops, but thinking of it this way leads you to appropriate way to handle this.

Revision history for this message
Nimit Bhardwaj (nimitbhardwaj) wrote :
Changed in mixxx:
status: New → In Progress
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Due to lack of progress, marking Triaged and clearing assignee. Feel
free to revert if it is in fact still in progress :).

Changed in mixxx:
assignee: Nimit Bhardwaj (nimitbhardwaj) → nobody
status: In Progress → Triaged
Revision history for this message
ronso0 (ronso0) wrote :

the error message is still an issue, see lp:1973401

Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8721

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.