Bug#905454: php-common: Update to php-common (1:62) stuck in php.common-post at systemd-tty-ask

2018-08-05 Thread Michael Biebl
Ondřej, please always CC the maintainers of the package you are
reassigning a bug to.

On Sun, 5 Aug 2018 06:56:38 +0200 =?utf-8?B?T25kxZllaiBTdXLDvQ==?=
 wrote:
> Control: reassign -1 systemd
> 
> I’ve seen this few times in the past, but there’s nothing I can do from 
> php-common.  The units are pretty standard.
> 
> Reassigning this to systemd.
> 
> Thanks
> Ondrej
> --
> Ondřej Surý
> ond...@sury.org
> 
> 
> 
> > On 4 Aug 2018, at 22:00, Jaap Keuter  wrote:
> > 
> > Package: php-common
> > Version: 1:62
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > While updating to php-common 1:62 the update gets stuck at:
> > 
> > ...
> > Unpacking mesa-va-drivers:amd64 (18.1.5-1) over (18.1.4-1) ...
> > Preparing to unpack .../17-php-common_1%3a62_all.deb ...
> > Unpacking php-common (1:62) over (1:61) ...
> > Preparing to unpack .../18-php7.2-xml_7.2.8-2_amd64.deb ...
> > Unpacking php7.2-xml (7.2.8-2) over (7.2.4-1) ...
> > ...
> > Processing triggers for libc-bin (2.27-5) ...
> > Setting up mesa-va-drivers:amd64 (18.1.5-1) ...
> > Setting up php-common (1:62) ...
> > 
> > 
> > Looking at the process tree reveils the following:
> > 
> >  |   |-konsole -session 
> > 10dd616e7500015331903250014310008_1533191244_922307 
> > 
> > 
> >  |   |   |-bash 
> > 
> > 
> >  |   |   |   `-update-debian.s /home/jaap/bin/update-debian.sh  
> > 
> > 
> >  |   |   |   `-sudo aptitude
> > 
> > 
> >  |   |   |   `-aptitude 
> > 
> > 
> >  |   |   |   |-dpkg --status-fd 96 --configure --pending
> > 
> > 
> >  |   |   |   |   `-php-common.post 
> > /var/lib/dpkg/info/php-common.postinst configure 1:61   
> >  
> >  |   |   |   |   `-systemctl start phpsessionclean.timer
> > 
> > 
> >  |   |   |   |   `-systemd-tty-ask --watch  
> > 
> > 
> >  |   |   |   `-{aptitude} 
> > 

hm, update-debian.s /home/jaap/bin/update-debian.sh
/home/jaap/bin/update-debian.sh...
How exactly do you trigger the update?
Is system fully booted at this point?
Can you provide us with steps how to reproduce the issue?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#905454: php-common: Update to php-common (1:62) stuck in php.common-post at systemd-tty-ask

2018-08-05 Thread Michael Biebl
Am 05.08.2018 um 09:12 schrieb Michael Biebl:

> hm, update-debian.s /home/jaap/bin/update-debian.sh
> /home/jaap/bin/update-debian.sh...
> How exactly do you trigger the update?
> Is system fully booted at this point?
> Can you provide us with steps how to reproduce the issue?

Please also attach the output of "reportbug --template systemd" to this
bug report,
Assuming you haven't rebooted the system, please also include the output
of "journalctl -alb" and dmesg.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#905454: php-common: Update to php-common (1:62) stuck in php.common-post at systemd-tty-ask

2018-08-05 Thread Jaap Keuter
On 05-08-18 09:29, Michael Biebl wrote:
> Am 05.08.2018 um 09:12 schrieb Michael Biebl:
> 
>> hm, update-debian.s /home/jaap/bin/update-debian.sh
>> /home/jaap/bin/update-debian.sh...
>> How exactly do you trigger the update?
>> Is system fully booted at this point?
>> Can you provide us with steps how to reproduce the issue?

Sure, the process tree shows what's going on. let me elaborate.

konsole -session 10dd616e7500015331903250014310008_1533191244_922307
Booted into a KDE plasma session, which gives me konsole.

  |   |   |-bash
Konsole runs bash as the shell.

  |   |   |   `-update-debian.s /home/jaap/bin/update-debian.sh
In the shell I manually run a script
(https://gitlab.com/JaapKeuter/update-debian) that supports me in updating 
Debian.

  |   |   |   `-sudo aptitude
The script runs sudo aptitude to do the updates. I have typed in my password for
sudo.

  |   |   |   `-aptitude
It runs aptitude to do the work.

  |   |   |   |-dpkg --status-fd 96 --configure --pending
It runs dpkg to work with the package.

  |   |   |   |   `-php-common.post
/var/lib/dpkg/info/php-common.postinst configure 1:61
It runs the package script to finish up the update of the package.

  |   |   |   |   `-systemctl start phpsessionclean.timer
It runs systemctl to start a systemd timer.

  |   |   |   |   `-systemd-tty-ask --watch

It runs systemd-tty-ask-password-agent to ask for permission.


As a further experiment I've entered the following in a bash shell to see what
would happen:

$ systemctl start phpsessionclean.timer

It pops up a dialog "Authentication Required - PolicyKit1 KDE Agent"
which says "Authentication is required to start 'phpsessionclean.timer".
It sits there for 25 seconds, after which it disappears outputting on the shell:
"Failed to start phpsessionclean.timer: Connection timed out
See system logs and 'systemctl status phpsessionclean.timer' for details."

So this is what might be happening on the update as well. As I was doing other
things at the time, the dialog must have long since disappeared during the 
update.

> 
> Please also attach the output of "reportbug --template systemd" to this
> bug report,

Done, see reportbug-systemd-backup-20180805-3946-zyzamfhh.gz


> Assuming you haven't rebooted the system, please also include the output
> of "journalctl -alb" and dmesg.
> 

The system is normally switched off, so that info isn't available anymore.




reportbug-systemd-backup-20180805-3946-zyzamfhh.gz
Description: application/gzip
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#905454: php-common: Update to php-common (1:62) stuck in php.common-post at systemd-tty-ask

2018-08-05 Thread Michael Biebl
Am 05.08.2018 um 18:14 schrieb Jaap Keuter:

> As a further experiment I've entered the following in a bash shell to see what
> would happen:
> 
> $ systemctl start phpsessionclean.timer
> 
> It pops up a dialog "Authentication Required - PolicyKit1 KDE Agent"
> which says "Authentication is required to start 'phpsessionclean.timer".
> It sits there for 25 seconds, after which it disappears outputting on the 
> shell:
> "Failed to start phpsessionclean.timer: Connection timed out
> See system logs and 'systemctl status phpsessionclean.timer' for details."
> 
> So this is what might be happening on the update as well. As I was doing other
> things at the time, the dialog must have long since disappeared during the 
> update.


"$" indicates, that you were running the above command as unprivileged
user. In that case it is expected that you are prompted for authentication.

dpkg/apt must be run with root privileges, in which case no separate
authentication is required.
"sudo systemctl start phpsessionclean.timer" will/should not trigger a
polkit authentication dialog.

>> Assuming you haven't rebooted the system, please also include the output
>> of "journalctl -alb" and dmesg.

If you have persistent journal enabled, you might still have the logs
from the previous boot.

Now that you've rebooted, does "sudo apt install --reinstall php-common"
trigger this issue again, ie. do you have a way to reproduce it?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#905454: php-common: Update to php-common (1:62) stuck in php.common-post at systemd-tty-ask

2018-08-07 Thread Jaap Keuter
On 05-08-18 18:32, Michael Biebl wrote:
> Am 05.08.2018 um 18:14 schrieb Jaap Keuter:
> 
>> As a further experiment I've entered the following in a bash shell to see 
>> what
>> would happen:
>>
>> $ systemctl start phpsessionclean.timer
>>
>> It pops up a dialog "Authentication Required - PolicyKit1 KDE Agent"
>> which says "Authentication is required to start 'phpsessionclean.timer".
>> It sits there for 25 seconds, after which it disappears outputting on the 
>> shell:
>> "Failed to start phpsessionclean.timer: Connection timed out
>> See system logs and 'systemctl status phpsessionclean.timer' for details."
>>
>> So this is what might be happening on the update as well. As I was doing 
>> other
>> things at the time, the dialog must have long since disappeared during the 
>> update.
> 
> 
> "$" indicates, that you were running the above command as unprivileged
> user. In that case it is expected that you are prompted for authentication.
> 

That is correct. The experiment was to see what would happen in that case, how
the authentication action would proceed.


> dpkg/apt must be run with root privileges, in which case no separate
> authentication is required.

That is what I am expecting from running 'sudo aptitude'.


> "sudo systemctl start phpsessionclean.timer" will/should not trigger a
> polkit authentication dialog.
> 

Indeed it does not.

>>> Assuming you haven't rebooted the system, please also include the output
>>> of "journalctl -alb" and dmesg.
> 
> If you have persistent journal enabled, you might still have the logs
> from the previous boot.
> 

Unfortunately I do not.


> Now that you've rebooted, does "sudo apt install --reinstall php-common"
> trigger this issue again, ie. do you have a way to reproduce it?
> 

Running this command does not trigger the issue again. It finishes normally.
Note that in this case the phpsessionclean.timer is already started.
Stopping the timer and then running the command also does not trigger the issue.

Further testing was performed by downgrading php-common to 1:49 (stable) and
stopping the phpsessionclean.timer. From there the same update-debian.sh script
was used to start an update. Still this did not trigger the issue.

I'm not sure what else we can do to reproduce this observation.

Thanks,
Jaap

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Re: Bug#905454: php-common: Update to php-common (1:62) stuck in php.common-post at systemd-tty-ask

2018-08-04 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 systemd
Bug #905454 [php-common] php-common: Update to php-common (1:62) stuck in 
php.common-post at systemd-tty-ask
Bug reassigned from package 'php-common' to 'systemd'.
No longer marked as found in versions php-defaults/62.
Ignoring request to alter fixed versions of bug #905454 to the same values 
previously set

-- 
905454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers