Zandronum Chat @
Get the latest version: 3.0
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003396Doomseeker[All Projects] Bugpublic2018-03-03 20:102018-03-03 20:46
Assigned To 
Platformx86_64OSDebian GNU/LinuxOS Versionbuster/sid
Product Version1.1 
Target VersionFixed in Version 
Summary0003396: Doomseeker startup error may display an empty list of directories which couldn't be created (chmod 0000 with empty directory)
Doomseeker will not run because following directories cannot be created:

This error message is void of directories and unhelpful.
Steps To ReproduceIn Doomseeker 1.1:

  1. Remove the default config directory, e.g. $HOME/.doomseeker (rm -rf $HOME/.doomseeker). Do not start Doomseeker yet.
  2. Create a new default config directory with no read/write/execute permissions: mkdir $HOME/.doomseeker && chmod 0000 $HOME/.doomseeker
  3. Attempt launching Doomseeker.

In Doomseeker 1.2~beta-1: Ditto, but repeat the instructions for $HOME/.config/doomseeker directory path too before launching Doomseeker.
Additional Information
  • ext4 file system
  • Qt 5.9.2
Attached Filespng file icon 2018-03-03-200348_500x103_scrot.png [^] (7,392 bytes) 2018-03-03 20:10

- Relationships

-  Notes
User avatar (0019114)
WubTheCaptain (developer)
2018-03-03 20:24

In Doomseeker 1.1, if $HOME permissions are set to 0000, then this works as intended.

In Doomseeker 1.2~beta-1, if $HOME/.config (not $HOME/.config/doomseeker) permissions are set to 0000, then this also works as intended.

It does not seem to matter in this "working as intended" scenario (parent directory is not writeable and/or executable) whether the Doomseeker directory doesn't exist, is empty or post-first start. The problem described here is when the Doomseeker directory itself not writable/executable.
User avatar (0019115)
WubTheCaptain (developer)
2018-03-03 20:30

I thought of bumping the severity to "major" given how much of a griefance this could potentially be to a new user with no apparent solution, but the problem itself is with the text and thus possibly "text" severity.

We can change the text or additional information to the dialog for a resolution, and we could add a reason from the filesystem why they couldn't be created (e.g. permission error, no disk space) after the directory.
User avatar (0019117)
WubTheCaptain (developer)
2018-03-03 20:45
edited on: 2018-03-03 20:46

I mean, the bug here is that dialog is shown even though the directory technically exists but has no permissions. What Doomseeker should really show is that the config directory cannot be written to, or is not readable due to lack of +r or +x permissions (I didn't test which). This is a seperate dialog.

Issue Community Support
Only registered users can voice their support. Click here to register, or here to log in.
Supporters: No one explicitly supports this issue yet.
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2018-03-03 20:10 WubTheCaptain New Issue
2018-03-03 20:10 WubTheCaptain File Added: 2018-03-03-200348_500x103_scrot.png
2018-03-03 20:11 WubTheCaptain Additional Information Updated View Revisions
2018-03-03 20:12 WubTheCaptain Steps to Reproduce Updated View Revisions
2018-03-03 20:13 WubTheCaptain Description Updated View Revisions
2018-03-03 20:24 WubTheCaptain Note Added: 0019114
2018-03-03 20:30 WubTheCaptain Note Added: 0019115
2018-03-03 20:31 WubTheCaptain Priority low => high
2018-03-03 20:31 WubTheCaptain Severity minor => text
2018-03-03 20:33 WubTheCaptain Priority high => low
2018-03-03 20:33 WubTheCaptain Severity text => major
2018-03-03 20:38 WubTheCaptain Additional Information Updated View Revisions
2018-03-03 20:45 WubTheCaptain Note Added: 0019117
2018-03-03 20:45 WubTheCaptain Note Edited: 0019117 View Revisions
2018-03-03 20:46 WubTheCaptain Note Edited: 0019117 View Revisions
2018-03-03 20:46 WubTheCaptain Note Edited: 0019117 View Revisions

Questions or other issues? Contact Us.


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker