+1 for what @saviq has mentioned in #10 - I see exactly the same
behaviour. ENABLE_DAEMON = 0 causes upgrade to fail.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1058518
Title:
This still happens with
transmission-daemon/trusty-updates,trusty-security,now 2.82-1.1ubuntu3.1
amd64
When ENABLE_DAEMON is 0 in /etc/default, the post-install script tries
to restart the daemon but fails, because the upstart job return value is
not 0 if daemon is disabled.
--
You received thi
The workaround I found was to edit the configuration file of
transmission-daemon
sudo vim /etc/default/transmission-daemon
setting
ENABLE_DAEMON=1
instead of
ENABLE_DAEMON=0
upgrading the package and then changing the value of ENABLE_DAEMON
again.
--
You received this bug notification because
Please note that changing the user makes no difference to me, in fact
mine is "debain-trasmission"
sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
1 not fully inst
I'm using transmission-d 2.76-0 and have the same exact problem is
this "fixable"? Is there any workaround?
Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1058518
Titl
Is there any progress on this bug? If not, anything I can do to help
move this one along?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1058518
Title:
package transmission-daemo
I'd accept that as a workaround. However, previous versions upgraded
happily, so ...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1058518
Title:
package transmission-daemon 2.5
I experienced the same issue.
Prior the upgrade I had changed the user in /etc/init.d/transmission-daemon to
my username.
To resolve the issue, I restored the original user "debian-transmission" and
then the upgrade process went ok.
--
You received this bug notification because you are a member
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: transmission (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1058518
Title:
package transmission-daemon 2.51-0ubuntu1.1 failed to install/upgrade:
subpr
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1058518
Title:
package transmission-daemon 2.51-0ubuntu1.1 failed to install/upgrade:
subprocess installed post-installation scrip
/var/log/syslog:
Sep 29 09:22:09 htpc transmission-daemon: transmission-daemon Error
loading config file -- exiting. (daemon.c:462)
No changes made to any configuration files.
root@htpc:/etc/transmission-daemon# ls -larth settings.json
-rwsr-x--- 1 debian-transmission debian-transmission 2.3K A
12 matches
Mail list logo