Bug 4449

Summary: shell scripts won't work with strict POSIX shells (e.g. dash)
Product: xprint Reporter: Sandor Geller <wildy>
Component: Server: Config: startup scriptsAssignee: Roland Mainz <roland.mainz>
Severity: normal    
Priority: high CC: MostAwesomedude
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 5799    

Description Sandor Geller 2005-09-14 02:35:31 UTC
I checked out and installed X.org CVS ( version. X won't start

1. the startx script contains a non POSIX-compliant arithmetic evaluation
2. the installed xprint init script uses arrays, which aren't present in
 strictly POSIX-compliant shells

My /bin/sh is dash.

The first problem can be solved by a trivial patch:

--- programs/xinit/startx.cpp.orig      2005-07-26 01:19:06.000000000 +0200
+++ programs/xinit/startx.cpp   2005-09-14 11:27:09.000000000 +0200
@@ -183,7 +183,7 @@
        removelist="$displayname $removelist"
-        dummy=$((dummy+1));
+        dummy=$(($dummy+1));
         xauth -q -f $xserverauthfile << EOF
 add :$dummy . $authcookie

The second problem can be solved by specifying /bin/bash instead of
/bin/sh - however this assumes that bash is installed into the /bin
directory which might be false on non-Linux platforms.
Comment 1 Sebastien Bacher 2006-02-17 23:36:43 UTC
Ubuntu bug about the first point:
Comment 2 Jeremy C. Reed 2006-02-26 02:21:52 UTC
I committed the fix to app/xinit/startx.cpp (but not monolithic
programs/xinit/startx.cpp) for the first problem.
Comment 3 Adam Jackson 2006-04-15 05:56:57 UTC
remaining bug is against xprint
Comment 4 mar77i 2010-03-23 15:35:37 UTC
same for xdm scripts! :)
Comment 5 Corbin Simpson 2011-09-13 15:52:50 UTC
Closing WONTFIX because nobody cares about Xprint. Reopen if you plan to address this bug.

Additionally, if this is a problem with xdm, please refile against xdm. Thank you.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.