Package: quassel-core Version: 0.8.0-1 Severity: normal Tags: patch The init script /etc/init.d/quassel-core allows starting quassel-core before its databases are set up. This is OK in the default configuration where quassel-core uses SQLite, but on large setups quassel-core is set up using a back-end of PostgreSQL or MySQL, so quassel-core has no database when it initially starts. This causes quassel-core to go into "initial set-up mode", allowing anyone who connects with it to reconfigure it.
The solution is to only start quassel-core when mysql and postgresql have started, if they exist. Therefore, these two services should be added to the Should-Start and Should-Stop lines: # Should-Start: mysql postgresql # Should-Stop: mysql postgresql Filing as normal, because this bug only appears on non-default (but common) set-ups, and makes the application initially unusable on them. Only after a restart of the daemon (preferably before someone re-configuring it) does the application start to act as intended. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages quassel-core depends on: ii adduser 3.113+nmu3 ii libc6 2.13-38 ii libgcc1 1:4.7.2-5 ii libqca2 2.0.3-4 ii libqt4-network 4:4.8.2+dfsg-11 ii libqt4-script 4:4.8.2+dfsg-11 ii libqt4-sql 4:4.8.2+dfsg-11 ii libqt4-sql-sqlite 4:4.8.2+dfsg-11 ii libqtcore4 4:4.8.2+dfsg-11 ii libstdc++6 4.7.2-5 ii lsb-base 4.1+Debian8 ii openssl 1.0.1e-1 quassel-core recommends no packages. quassel-core suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
