Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#37650 - [quassel-core] ignores both user and listen directives in /etc/conf.d/quassel

Attached to Project: Community Packages
Opened by Justin Dray (justin8) - Tuesday, 05 November 2013, 10:16 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 15 June 2014, 14:09 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Jelle van der Waa (jelly)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The package comes with an /etc/conf.d/quassel file that has 'QUASSEL_USER=quassel' and 'LISTEN=127.0.0.1'. The service file ignores the user directive and runs as root, and has a hardcoded '--listen 127.0.0.1' instead of reading in the variable

Additional info:
* package version(s)
0.9.1-1
* config and/or log files etc.


Steps to reproduce:
1. Install quassel-core
2. cat /usr/lib/systemd/system/quassel.service
3. cat /etc/conf.d/quassel
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 15 June 2014, 14:09 GMT
Reason for closing:  Fixed
Comment by Justin Dray (justin8) - Tuesday, 05 November 2013, 10:25 GMT
Adding in 'EnvironmentFile=/etc/conf.d/quassel' and changing the ExecStart to '/usr/bin/quasselcore --listen=${LISTEN} --configdir=/var/lib/quassel' solves the listen port portion of this bug.
Comment by Justin Dray (justin8) - Monday, 11 November 2013, 11:36 GMT
  • Field changed: Percent Complete (100% → 0%)
The user part is a duplicate of that bug. Ignoring the IP specified in the config file is not. Perhaps just remove the root user part of this bug then but leave it open?
Comment by Doug Newgard (Scimmia) - Saturday, 14 June 2014, 20:59 GMT
justin8, it looks to me like this was fixed last Nov, can you confirm?
Comment by Justin Dray (justin8) - Sunday, 15 June 2014, 13:46 GMT
That does appear to have been fixed now. Thanks

Loading...