http://bugzilla.novell.com/show_bug.cgi?id=969528 http://bugzilla.novell.com/show_bug.cgi?id=969528#c4 Stefan Schubert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rene.braeunling@yalwa.com Flags| |needinfo?(rene.braeunling@y | |alwa.com) --- Comment #4 from Stefan Schubert --- (In reply to René Bräunling from comment #0)

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Build Identifier:

root 7825 0.0 0.0 48988 9588 ? S Mar02 0:04 rpm --root / --dbpath /var/lib/rpm -U --percent --noglob --force --nodeps -- /var/cache/zypp/packages/http-dl.google.com-1e18239b/google-chrome-stable-48. 0.2564.116-1.x86_64.rpm

ps auxwww|fgrep 7827 root 7827 0.0 0.0 11752 2616 ? S Mar02 0:00 /bin/sh /var/tmp/rpm-tmp.NNB6Cy 1 less /var/tmp/rpm-tmp.NNB6Cy

root 8136 0.0 0.0 11748 2656 ? S Mar02 0:00 /bin/bash /sbin/service atd start root 8143 0.0 0.0 22972 2496 ? S Mar02 0:00 systemctl start --full atd.service

Reproducible: Always

Steps to Reproduce: 1. create an autoyast file 2. install chrome with zypper in google-chrome-stable in the scripts section Actual Results: zypper waits to finish chrome installation ... (182/189) Installing: google-chrome-stable-48.0.2564.116-1 [............

Expected Results: zypper should install chrome, system should reboot after autoyast has finished

<init-scripts config:type="list"> <script> <filename>google-chrome</filename> <source><![CDATA[ wget https://dl.google.com/linux/linux_signing_key.pub rpm --import linux_signing_key.pub zypper ref zypper -n in --auto-agree-with-licenses google-chrome-stable ]]></source> </script> </init-scripts>

I think Zypper is locked by the YaST installer which will be finished AFTER all init-scripts have been finished. A workaround would be to move /var/run/zypp.pid away before starting the zypper calls. Does this work for you ? -- You are receiving this mail because: You are on the CC list for the bug.