You are not logged in.

#1 2013-05-22 07:30:10

himodo
Member
Registered: 2013-05-22
Posts: 2

[Solved] Starting xterm causes "crash"

I have recently been trying to get into window managers, Awesome specifically and have come across a problem. Adding "startx" to ~/.bashrc and then pressing mod4+enter after you log in causes the system to kind of crash in a very weird way to the point where I can not even switch to a different "terminal thing" (ctrl+alt+f<#>, I'm so helpless..). The problem does not happen if I do "startx" manually after login. I apologize if this is already solved, but I have no idea what this type of crash is called, and I am unable to read what is on the screen because it is very distorted.

I am running all this inside VirtualBox on an Arch x86_64 host, the guest is also x86_64 if that matters.

Last edited by himodo (2013-05-22 08:00:59)

Offline

#2 2013-05-22 07:39:15

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [Solved] Starting xterm causes "crash"

Read the Wiki page on bash (or man bash): the invocation section describes how .bashrc is sourced every time a non-login interactive shell is started.

You want commands like startx in your .profile...

You should also look more carefully at ensuring you have an active session: the wiki also has details on that.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2013-05-22 08:00:12

himodo
Member
Registered: 2013-05-22
Posts: 2

Re: [Solved] Starting xterm causes "crash"

Oh, I get it, it did not phase me at all. Thanks, TIL about ~/.bash_profile.

Offline

Board footer

Powered by FluxBB