How Can I Drop Back To The Shell?

[SomeGuy99]

I accidentially did this while using a USB keyboard. The normal method of ctrl-alt-f* doesn't seem to do anything.

How can I do this from the Pandora (with or without external keyboard)? I can't seem to kill XFCE (it just restarts), and the Googles - they do nothing.

 

[GuSec]

So virtual terminals won't work on the Pandora, why is that? :huh:
Try and change runlevel in /etc/inittab to 3 and reboot!

If you want to stop XFCE, run the start/stop-script for the daemon, xdm:
/etc/init.d/xdm stop
The daemon xdm will keep resurrecting your XFCE until you stop it!

 

[paulguy]

If you want to enable this, look in the /etc/X11/xorg.conf file and see if there's a Section "ServerFlags", and in that section, there may be a line that says Option "DontVTSwitch" "true" (may also be "on", "yes" or "1"), just remove that line and it SHOULD work. If it WAS added, though, it's likely it was added for a reason. There might be some bug in the video driver or something so I suggest you do it at your own risk and expect crashes if that's the case.

If it's not there, then just add the same line to the same section (add the section if it doesn't exist) but put "false" for it's value.

It would look something like this:

# Some crap or nothing may be here

Section "ServerFlags"
	# maybe crap here
	Option "DontVTSwitch" "false"
EndSection

# more crap or nothing at all may be here

 

[Spirit]

If you want to stop XFCE, run the start/stop-script for the daemon, xdm:
/etc/init.d/xdm stop
The daemon xdm will keep resurrecting your XFCE until you stop it!

There is no /etc/init.d/xdm

If you want to enable this, look in the /etc/X11/xorg.conf file and see if there's a Section "ServerFlags" (...)

It is not there.

Also I noticed that no agetty instances are running. And /etc/securetty is huge (64 tty, 64 vc).
There are two getty instances running. One for ttyS0 and one on tty1.

I managed to open another tty with "openvt bash" but ctrl-alt-F3 does not work, maybe you cannot press 4 buttons at once?

"sudo chvt 2" works! "chmod +s" works without sudo of course.

 

[SomeGuy99]

If you want to stop XFCE, run the start/stop-script for the daemon, xdm:
/etc/init.d/xdm stop
The daemon xdm will keep resurrecting your XFCE until you stop it!

There is no /etc/init.d/xdm

If you want to enable this, look in the /etc/X11/xorg.conf file and see if there's a Section "ServerFlags" (...)

It is not there.

Also I noticed that no agetty instances are running. And /etc/securetty is huge (64 tty, 64 vc).
There are two getty instances running. One for ttyS0 and one on tty1.

I managed to open another tty with "openvt bash" but ctrl-alt-F3 does not work, maybe you cannot press 4 buttons at once?

"sudo chvt 2" works! "chmod +s" works without sudo of course.

You should be able to hit function then F1 (only using three buttons). Besides, the ctrl and alt buttons aren't on the same map as the keyboard keys and you can press them in addition to two keys.

It isn't mapped anyway - I tried on a usb keyboard.

So virtual terminals won't work on the Pandora, why is that? :huh:
Try and change runlevel in /etc/inittab to 3 and reboot!

If you want to stop XFCE, run the start/stop-script for the daemon, xdm:
/etc/init.d/xdm stop
The daemon xdm will keep resurrecting your XFCE until you stop it!

File doesn't seem to exist!

 

[EvilDragon]

sudo /etc/init.d/slim-init stop

 

[Sphinxter]

Those aren't standards, they're traditions.

 

[SomeGuy99]

sudo /etc/init.d/slim-init stop

Cheers! But when I do that I just get a blinking cursor (even when i'm in a vty).

 

[EvilDragon]

sudo /etc/init.d/slim-init stop

Cheers! But when I do that I just get a blinking cursor (even when i'm in a vty).

Hmm? No login screen? Has there something changed from one of the older images...?
Didn't use it that much.

But if you don't need to kill X, sudo chvt 1 should work.

 

[SomeGuy99]

sudo /etc/init.d/slim-init stop

Cheers! But when I do that I just get a blinking cursor (even when i'm in a vty).

Hmm? No login screen? Has there something changed from one of the older images...?
Didn't use it that much.

But if you don't need to kill X, sudo chvt 1 should work.

Yeah it does. I'd like to kill XFCE too if possible?

 

[EvilDragon]

sudo /etc/init.d/slim-init stop

Cheers! But when I do that I just get a blinking cursor (even when i'm in a vty).

Hmm? No login screen? Has there something changed from one of the older images...?
Didn't use it that much.

But if you don't need to kill X, sudo chvt 1 should work.

Yeah it does. I'd like to kill XFCE too if possible?

Well, after you switched to chvt 1, do sudo /etc/init.d/slim-init and that kills all of X

 

[SomeGuy99]

sudo /etc/init.d/slim-init stop

Cheers! But when I do that I just get a blinking cursor (even when i'm in a vty).

Hmm? No login screen? Has there something changed from one of the older images...?
Didn't use it that much.

But if you don't need to kill X, sudo chvt 1 should work.

Yeah it does. I'd like to kill XFCE too if possible?

Well, after you switched to chvt 1, do sudo /etc/init.d/slim-init and that kills all of X

When I do 'sudo killall xfce4-session' it starts up again.

 

[EvilDragon]

sudo /etc/init.d/slim-init stop

Cheers! But when I do that I just get a blinking cursor (even when i'm in a vty).

Hmm? No login screen? Has there something changed from one of the older images...?
Didn't use it that much.

But if you don't need to kill X, sudo chvt 1 should work.

Yeah it does. I'd like to kill XFCE too if possible?

Well, after you switched to chvt 1, do sudo /etc/init.d/slim-init and that kills all of X

When I do 'sudo killall xfce4-session' it starts up again.

Errmm... sudo /etc/init.d/slim-init stop

Forgot the stop here (posted it above though).

If you stop slim, now XFCE4-session will restart,

 

[SomeGuy99]

If you stop slim, now XFCE4-session will restart,

I want to kill XFCE. I want to start other window managers

 

[EvilDragon]

If you stop slim, now XFCE4-session will restart,

I want to kill XFCE. I want to start other window managers

Well - there is /etc/pandora/conf/gui.conf

Those are the GUIs that are available as default GUIs or for Switch GUI.
It's easy to add new GUIs or Window Managers!

This is what's currently in the file:

XFCE4;The full desktop Environment;startxfce4;xfce4-session-logout --logout
MiniMenu;A very simple but flexible menu;startmmenu;stopmmenu

Each line is one GUI, parameters are seperated by ;

The first block in each line is the name that appears in the Switch GUI or Set Default GUI dialogue.
The second is the description.
The third is the command to start that GUI.
The fourth is the command to stop that GUI.

If you add your desired Window Manager there, it will appear in the Startup-Settings as selectable Default GUI as well as in the Switch GUI dialogue - which means you can switch around between each GUIs

Before you use it as Default GUI, be sure to test it using Switch GUI first to make sure it works. Otherwise you won't be able to login anymore.

 

[SomeGuy99]

Thanks Ed. I actually came across this file earlier (I've been reverse engineering all your scripts!) but I couldn't get it to start Ubuntu Netbook Launcher?

When I get a firmware running off the Sd I want to experiment with all the other window managers available for Angstrom.

 

[Spirit]

Trying to get openbox to run I put

openbox;blah;openbox-session;something

in there with no success (XFCE came up after a blank screen with blinking cursor).

So I thought I should try "exec openbox-session" instead. Now nothing happens if I use the switch GUI tool.


sudo /etc/init.d/slim-init stop
gives the blank blinking cursor screen.

 

[EvilDragon]

Trying to get openbox to run I put

openbox;blah;openbox-session;something

in there with no success (XFCE came up after a blank screen with blinking cursor).

So I thought I should try "exec openbox-session" instead. Now nothing happens if I use the switch GUI tool.


sudo /etc/init.d/slim-init stop
gives the blank blinking cursor screen.

One thing you could do it put

xterm;Opens a simply X-Shell;xterm;killall xterm

into the file.
Then you can switch to a simply xterm (without anything else running) and run openbox from there to see if it spits out any error-messages when run.

 

[Spirit]

Nice! Thank you.