DisplayLink Forum - View Single Post - 1: eval: ./displaylink-installer.sh: Permission denied

Jim2220 · 11-30-2015, 01:49 AM

This is additional output using bash -x to obtain more info:

+ MS_Printf ' 100%% '
+ printf ' 100%% '
100% + test xy = xy
+ PATH=/usr/xpg4/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
+ cd /tmp/selfgz1274024900
++ id -u
+ chown -R 1000 .
++ id -g
+ chgrp -R 1000 .
++ expr 12083 + 6017747
+ offset=6029830
+ test n = n
+ echo

+ cd /tmp/selfgz1274024900
+ res=0
+ test x./displaylink-installer.sh '!=' x
+ test xn = xy
+ eval ./displaylink-installer.sh install
++ ./displaylink-installer.sh install
./displaylink-driver-1.0.138.run: line 489: ./displaylink-installer.sh: Permission denied
+ res=126
+ test 126 -ne 0
+ test xn = xy
+ test n = n
+ cd /tmp
+ /bin/rm -rf /tmp/selfgz1274024900
+ eval true
++ true
+ exit 126

It appears as though the .run file is using a script to do some preliminary work before it unsuccessfully attempts to invoke displaylink-installer.sh. How can it be that the .run file has insufficient permissions to invoke something contained within itself?

11-30-2015, 01:49 AM	#2
Jim2220 Junior Member Join Date: Nov 2015 Posts: 11	More output from bash debug This is additional output using bash -x to obtain more info: + MS_Printf ' 100%% ' + printf ' 100%% ' 100% + test xy = xy + PATH=/usr/xpg4/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games + cd /tmp/selfgz1274024900 ++ id -u + chown -R 1000 . ++ id -g + chgrp -R 1000 . ++ expr 12083 + 6017747 + offset=6029830 + test n = n + echo + cd /tmp/selfgz1274024900 + res=0 + test x./displaylink-installer.sh '!=' x + test xn = xy + eval ./displaylink-installer.sh install ++ ./displaylink-installer.sh install ./displaylink-driver-1.0.138.run: line 489: ./displaylink-installer.sh: Permission denied + res=126 + test 126 -ne 0 + test xn = xy + test n = n + cd /tmp + /bin/rm -rf /tmp/selfgz1274024900 + eval true ++ true + exit 126 It appears as though the .run file is using a script to do some preliminary work before it unsuccessfully attempts to invoke displaylink-installer.sh. How can it be that the .run file has insufficient permissions to invoke something contained within itself?