How To Cleanly Close A Graphic Display Manager Started Through Startx?

I've just installed Arch, and Installed and configured openbox and gnome terminal. Openbox starts, firefox works, but when I try to start gnome terminal, I curser spins for a moment and then it doesnt load.

I've tried to find a resolution to this but I'm not seeing much relevant to this specific scenerio. Also, this is my first time ever installing Arch, or any distro without a graphic installer or a kickstart script. My experience is pretty basic. I've used ubuntu/mint/centos for quite a while but figured this will be a good way to get me learning.

After I post this I am going to reboot to get back to command line and look at the installation and maybe install another terminal and see if this makes much a difference.

Hey, I'm having a bit trouble getting this working right.

I'm using mate desktop and lightdm
my .xinitrc only contains exec "mate-session"

Xorg file
http://pastebin.com/ipBMwT38

I can login to another X session fine, and start mate desktop with startx. This defeats the purpose of running a seperate X for games though...

steam launches fine from terminal, but my keyboard or mouse doesn't work.

Also in Xorg I enabled coolbits = 24 still can't use NVclock to adjust anything even though it detects my video card details fine.

Hello,

I installed Mint 17 xfce onto a friend's HP netbook a few months ago. Up until now all has been working pretty perfectly.

From this evening, she tells me that after she types in her password the following message appears:

no exec. line in this session file [her password appears here in plain text!] running the GNOME failsafe session instead

The only option at this point is seemingly to click ok. After that, this message appears:

Could not find the GNOME installation will try running the failsafe xterm session

Again the only option is to click ok, then this appears for a few seconds:

Cannot find xterm start a failsafe session

Then it goes to a black screen (though you can see the mouse cursor) on which it stays indefinitely.

She tells me that she wasn't trying to do anything other than web browsing and email checking before this started happening so there doesn't seem to be any logical reason behind it. Does anybody have any idea what is happening and how to fix it?

Hi guys/gals.

I installed Debian Jessie with LXDE as my default desktop environment, no problems, except I can't play most games. So installed the Meta Package of the Gnome Desktop environment. Everything appeared to be ok, but when I went to reboot, all I get is a black screen.

I went to the Grub and typed in "nomodeset" to get me back to a desktop.
I uninstalled Gnome (not full removal), but still have the same problem.
When I restarted in safety mode, Gnome was still a desktop option that I could load, which I did. I'm confused. Do I need to do a complete removal?

I tried installing the nvidia graphic card driver as per the Debian manual, and that left me with only a root terminal and no GUI.

I've got about 2Gigs of ram and a 2.4 GHz Pentium 3 processor with an ASUS motherboard. (yes, it's a 12 year old computer, but not used for the past few years)

Any help would be great.

Thanks in advance,

Joe

I want to show keyboard layout and selection of language at login screen in RHEL 7.

I have modified the language menu to show "show keyboard layout" and "Region & Language settings".
On clicking above menu items, applications are launched but they are not visible at login screen.
I check the programs are running by taking a remote session.

gkbd-keyboard-display -l us
gnome-control-center region

above two applications are executing but none is displaying at login screen(gdm).

How can I bring the applications at top of display manager(gdm).

I have tried

i m running file following tcl script but terminal shows nothing no error no nam file nothing
whats wrong with this script??????


set ns [new Simulator]

set nf [open out.nam w]
$ns namtrace-all $nf

proc finish {} {
global ns nf
$ns flush-trace
close $nf
exec nam out.nam &
exit 0
}

for {set i 0} {$i < 7} {incr $i} {
set n($i) [$ns node]
}

for {set i 0} {$i < 7} {incr $i} {
$ns duplex-link n($i) n([expr ($i+1)%7]) 1mb 10ms dropTail

$ns at 5.0 "finish"

$ns run

i write ns example3.tcl on terminal but terminal shows nothing even after waiting for long. when choose to close terminal it shows msg something running want to kill terminal

hi,

what file manager is everybody using?
does it really matter...

cant find what the default file manager there is for centos 7
but it has dolphin installed as well but doesnt use it by default
im running gnome 3

i read that konqueror is good...is it mostly just preference

lastly

do most linux systems have components of kde and gnome installed by default...even if you arent using those desktops? cause i dont have kde desktop installed yet i read that dolphin uses kde.

When I bring up Linux Ubuntu I would like to get a login prompt and choose as whom to log in. Then I would like to say startX or something like that and to get into X-windows. As I am in X-windows I would like to, do a right mouse click or something and chose “open a new terminal” or something. I used to do that all back over decade ago. Then I haven’t used Linux for over a decade. Now I got a box with Ubuntu, but …

When I bring it up I automatically get logged in as “Owner” and I get into interface that limits what I can do. Specfically, I don’t see how to become a different user, how to get into command line mode, how to run X-windows and open multiple terminal windows. And I would like to decide myself when to invoke some fancy GUI interface, instead of being forced into it..

I found one way to do some of what I want: ctl-alt-functionkey. But when I log in and do startX from there the right mouse click does not give me “open new terminal” option.

Could somebody help me out? Thank you very much in advance.

Roman

I have SLES 11.3 (x86_64).
When I try to connect to this server via ssh or console without kde everything is OK.
But when I try to connect to this server through kde, in /var/log/messages I can see:

Mar 25 10:03:04 server1 kdm: :0[6560]: Cannot open ConsoleKit session: Unable to open session: Failed to execute program /lib64/dbus-1/dbus-daemon-launch-helper: Success
Mar 25 10:03:04 server1 kdm: :0[6560]: Client start failed
Mar 25 10:03:04 server1 kdm: :0[6560]: Cannot close ConsoleKit session: Unable to close session: no session open

# ls -l /lib64/dbus-1/dbus-daemon-launch-helper
-rwsr-x--- 1 root messagebus 47912 Oct 15 2012 /lib64/dbus-1/dbus-daemon-launch-helper

Can you help me to resolve my problem?

Hey guys. So I just went out and bought a Sager 8268-s (clevo p150sm-a) With an i7 4910mq and a Nvidia 980m gt. As I am a computer tech by trade, every time i see Windows i get horrible PTSD so i decided to try Linux instead. After many hours of trying to get a dual boot working finally got Linux Mint 17 Cinnamon installed on my computer, but when I went to install the Nvidia driver it landed me in fallback mode which I could not escape. So then I tried Ubuntu 14.04 LTS thinking maybe Mint was incompatible with the driver and the same thing happened.

So here is my method:

(sorry i don't know how to make a code box :/ )

First I log in to get root access:

$ su

Then I Update the xorg:

$ sudo apt-add-repository ppa:xorg-edgers/ppa

Then update my system:

$ sudo apt-get update && sudo apt-get dist-upgrade

Then i go into Virtual terminal (Ctrl+Alt+F1) and disable the display manager:

$ sudo service mdm (or lightdm for Ubuntu) stop

Then i install the drivers which i have done multiple ways:

$ sudo apt-get install nvidia-current nvidia-settings

or

$ sudo apt-get install nvidia-343 nvidia-settings

or by downloading the driver from Nvidia (first designating the file as executable)

$ sudo sh nvidia.run && sudo apt-get install nvidia-settings

Then after install, I create the config file:

$ sudo nvidia-xconfig

Then I reboot. After I get the low res mode in Ubuntu or fallback mode in Mint and Driver manager doesn't detect any proprietary drivers and I have to reinstall to get the OS working again. Any suggestions would be greatly appreciated.