Bug#752394: cups installation hangs in triggers
Control: severity -1 important
Le mardi, 24 juin 2014 02.13:10, vous avez écrit :
> On 2014-06-23 19:02:50 +0200, Didier 'OdyX' Raboud wrote:
> > Can you reproduce this problem or was it a one-off problem?
>
> I tried to reproduce the problem by doing a reinstall on the cups
> related packages. I even did:
> (…)
> which corresponds to the upgrade, but again, everything is fine.
Well, if neither you or me are able to reproduce this problem (and noone
else if experiencing it), I don't see how we'll be able to solve it; I'm
therefore hereby downgrading this bug to important.
> Could you eventually attach your /etc/cups/cupsd.conf file?
>
> Attached, but AFAIK, that's the default file.
Indeed.
> I've looked at the /var/log/syslog messages, and here are the messages
> that occurred during the upgrade. They seem to be normal.
>
> [...]
> Jun 23 13:03:49 ypig PackageKit: daemon quit
> (…)
> Jun 23 13:07:52 ypig dbus[1959]: [system]
> Activating service name='org.freedesktop.PackageKit' (using
> servicehelper)
> Jun 23 13:07:52 ypig PackageKit: daemon start
> Jun 23 13:07:52 ypig dbus[1959]: [system] Successfully activated
> service 'org.freedesktop.PackageKit' [...]
>
> The messages at 13:04:53 and 13:06:53 correspond to ssh to the
> machine (since I did the upgrade remotely).
>
> I suspect that
>
> Jun 23 13:03:49 ypig PackageKit: daemon quit
>
> is related to the upgrade. I also got it when I retested the upgrade.
Indeed. "It should work"™.
Other things that come to mind are indeed PackageKit conflict, apparmor
or SELinux configurations; do you have something custom in these areas?
Could you also find the /var/log/cups/error_log lines from the upgrade
time, maybe?
Cheers,
OdyX
Reply to: