From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] `deluged` does not work on first startup unless `/var/lib/deluge/.config/deluge` directory is manually created
Date: Tue, 16 Nov 2021 14:22:27 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34103@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
New issue by TinfoilSubmarine on void-packages repository
https://github.com/void-linux/void-packages/issues/34103
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: Void 5.13.19_1 x86_64 AuthenticAMD notuptodate rrmFFFFFFFFFFFFFFFFF
* package: deluge-2.0.3_14
### Expected behavior
`deluged` should start with no issues.
### Actual behavior
`deluged` outputs:
```
Traceback (most recent call last):
File "/usr/bin/deluged", line 33, in <module>
sys.exit(load_entry_point('deluge==2.0.3', 'console_scripts', 'deluged')())
File "/usr/lib/python3.10/site-packages/deluge/core/daemon_entry.py", line 105, in start_daemon
file_handler = FileHandler(options.logfile)
File "/usr/lib/python3.10/logging/__init__.py", line 1167, in __init__
StreamHandler.__init__(self, self._open())
File "/usr/lib/python3.10/logging/__init__.py", line 1197, in _open
return open_func(self.baseFilename, self.mode,
PermissionError: [Errno 13] Permission denied: '/var/lib/deluge/.config/deluge/deluged.log
```
### Steps to reproduce the behavior
Manually run `deluged`: `sudo /etc/sv/deluged/run`
next reply other threads:[~2021-11-16 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 13:22 TinfoilSubmarine [this message]
2021-11-17 0:21 ` [ISSUE] [CLOSED] " sgn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34103@inbox.vuxu.org \
--to=tinfoilsubmarine@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).