Hi, Werner. Take a look at <URL: http://bugs.debian.org/580564 >. I've verified this with our test suite, and insserv no longer understand the X-Interactive: true header. This test suite function fail:
test_x_interactive() { echo echo "info: Check if X-Interactive header work" echo "BTS #458224" echo initdir_purge # Insert a few scripts to flesh out $initdir insertscript first <<EOF || true ### BEGIN INIT INFO # Provides: first # Required-Start: # Required-Stop: # Default-Start: 2 # Default-Stop: 0 ### END INIT INFO EOF # This test if X-Interactive work with existing scripts when a new # script is inserted. insertscript alone1 <<'EOF' || true ### BEGIN INIT INFO # Provides: alone1 # Required-Start: first # Required-Stop: first # Default-Start: 2 # Default-Stop: 0 # X-Interactive: true ### END INIT INFO EOF insertscript after <<'EOF' || true ### BEGIN INIT INFO # Provides: after # Required-Start: first # Required-Stop: first # Default-Start: 2 # Default-Stop: 0 ### END INIT INFO EOF # This test if X-Interactive work with new scripts too. The code # paths in insserv are different for the two cases. insertscript alone2 <<'EOF' || true ### BEGIN INIT INFO # Provides: alone2 # Required-Start: first # Required-Stop: first # Default-Start: 2 # Default-Stop: 0 # X-Interactive: true ### END INIT INFO EOF list_rclinks check_script_present 2 first check_script_present 2 after check_script_present 2 alone1 check_script_present 2 alone2 check_order 2 first after check_order 2 first alone1 check_order 2 first alone2 # This ordering is not guaranteed, but currently interactive scripts # are put after the others on the same level. check_order 2 alone1 after check_order 2 alone2 after if grep INTERACTIVE ${initddir}/.depend.start | grep -q alone1 && grep INTERACTIVE ${initddir}/.depend.start | grep -q alone1 ; then counttest else error "scripts alone1 and alone2 are not flagged as interactive" fi } Any clue what is wrong? Happy hacking, -- Petter Reinholdtsen