Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 2 days, 9 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 4 days, 6 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 5 days, 3 hrs ago - more...
|
2012-01-24
, 06:19
|
|
Posts: 1,067 |
Thanked: 2,383 times |
Joined on Jan 2012
@ Finland
|
#2
|
Well if you unset DISPLAY then its your own fault, as its expected that things start to break after that one.
|
|
2012-01-24
, 08:05
|
|
Posts: 986 |
Thanked: 1,526 times |
Joined on Jul 2010
|
#3
|
Originally Posted by rainisto
well, i certainly expect things to break NOW, but i couldnt imagine why i should have supposed that they would break BEFORE i saw it happen.
Well if you unset DISPLAY then its your own fault, as its expected that things start to break after that one.
.profile is read on ALL logins, including shell logins. shell logins have no business having an x client display if theyre running headless, and i do this all the time. theres no reason NOT to set the DISPLAY variable, except that i use this to see whether im in a gui {meego-terminal on the device} or a terminal {ssh-ing in}.
i personally think its bad that:
1) ANY file in /home is read early in the boot cycle
2) x client display is set at all in a user's login shell profile
{they clearly dont anticipate any headless logins, which is silly}
3) that there is no way to get a tty session
4) user is hardcoded and there is no root gui {e.g.: GDM, LXDM}
|
|
2012-01-24
, 09:30
|
|
Posts: 1,067 |
Thanked: 2,383 times |
Joined on Jan 2012
@ Finland
|
#4
|
Originally Posted by wolke
1) most of the apps that end user sees in dispay is runned as user thus .profile is read.
well, i certainly expect things to break NOW, but i couldnt imagine why i should have supposed that they would break BEFORE i saw it happen.
.profile is read on ALL logins, including shell logins. shell logins have no business having an x client display if theyre running headless, and i do this all the time. theres no reason NOT to set the DISPLAY variable, except that i use this to see whether im in a gui {meego-terminal on the device} or a terminal {ssh-ing in}.
i personally think its bad that:
1) ANY file in /home is read early in the boot cycle
2) x client display is set at all in a user's login shell profile
{they clearly dont anticipate any headless logins, which is silly}
3) that there is no way to get a tty session
4) user is hardcoded and there is no root gui {e.g.: GDM, LXDM}
2) people that login headless using ssh, usually do want to start some applications that are seen on the screen so its easier to have DISPLAY always set. If you want headless without DISPLAY, you can always add different username to filesystem that doesn't has DISPLAY set and run headless apps under that user.
3) there is a way, but its not documented to end users ;-)
4) Its a phone and not desktop Linux.
{changing /root/.profile does not}
adding the line 'unset DISPLAY', or removing export DISPLAY=':0', is what kills it.
if you modify it as above, and reboot, it throws it into a boot loop. flashing was still possible, but i had to flash the EMMC; you lose all pictures, contacts, maps, conversations, etc.
i tested a buncha times when trying to find the culprit in my build script, and here ya go:
smallest steps to brick your phone:
1) flash firmware+emmc, then flash an open kernel
2) boot up
3) enable dev mode, boot up again
4) meego-terminal: vi /home/user/.profile
5) remove all lines
6) add line: "unset DISPLAY"
7) switch off, turn on {wont boot}
dohn do eet, bra!