![]() |
2013-04-25
, 17:55
|
Posts: 2,292 |
Thanked: 4,135 times |
Joined on Apr 2010
@ UK
|
#2
|
The Following User Says Thank You to sixwheeledbeast For This Useful Post: | ||
![]() |
2013-04-25
, 18:45
|
Posts: 669 |
Thanked: 433 times |
Joined on May 2010
|
#3
|
What is your "small utility" made with?
It looks like one is running as root and one isn't.
Why do you need root to run those commands anyway?
![]() |
2013-04-25
, 20:20
|
Posts: 2,102 |
Thanked: 1,937 times |
Joined on Sep 2008
@ Berlin, Germany
|
#4
|
![]() |
2013-04-25
, 20:30
|
Posts: 669 |
Thanked: 433 times |
Joined on May 2010
|
#5
|
And do you really use bash as your X-Terminal shell?
The default X-Terminal shell from busybox is ash.
![]() |
2013-04-26
, 07:15
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#6
|
It doesn't matter if i use root or user - i'm getting the same behavior which is different UI for the same user - this is what i do:
i'm executing the following command from a queen beecon widget:
bash /home/user/smart/scripts/Launchers/CarModeSelection
it runs as "user" - i verified that by adding this to the end of the "CarModeSelection" script:
id -un>/res.txt
when i execute the following from x-term:
su user -c "bash /home/user/smart/scripts/Launchers/CarModeSelection"
$ run-standalone.sh /home/user/smart/scripts/Launchers/CarModeSelection
The Following User Says Thank You to reinob For This Useful Post: | ||
![]() |
2013-04-26
, 08:27
|
|
Posts: 381 |
Thanked: 336 times |
Joined on Jan 2011
@ Stockholm, Sweden
|
#7
|
![]() |
2013-04-27
, 13:25
|
Posts: 669 |
Thanked: 433 times |
Joined on May 2010
|
#8
|
The Following User Says Thank You to impeham For This Useful Post: | ||
nevertheless, the UI seems and behaves differently - it's like 2 different themes (see attached pics).
Why is this happening? how can i control which "theme" to be used?