I have a two part question regarding ctrl+alt+Fl
1)The Gnome Desktop Froze on me and I would like to c+a+F1 then kill GNOME, there are alot of pid associated with gnome, what is the easiest way to kill or reset GNOME from tty1
2)Just for kix, is there a way to open a new tty8 session from tty1 or tty8 from tty7
I installed karmic on a dell vostro 1000 - all went well until I installed updates and restarted. Ubuntu booted to tty1 instead of tty7. I'm not entirely sure what changed, but I could do one of 2 things. at the login prompt on tty1 I could wait about 2+ minutes and it would boot to tty7 w/o my network card (but keeping the wireless) or I could ctrl+alt+f7 and get to the normal tty7 with everything working.After a bit of looking around, i found a few solutions, but the problems were not exactly like mine.- I could reinstall gdm (I did this and it had no effect)- I could install minigetty and do something else (not to sure what they wanted here)- I could remove usplashIt turned out that removing usplash did the trick...I dont get the cool little white logo over a black screen
View 1 Replies View RelatedI installed Ubuntu with the netboot. I only installed the packages I needed. Concerning X, I installed xdm as login manager and fluxbox as window manager. All is working fine except that whatever I type under X (under xdm or, after logging in, under fluxbox) appears in tty1! The keyboard inputs appear under X and under tty1 (so usually after "login:", or hidden after "password:").
Let me provide you with more details. Starting from xdm, I cannot access to the other ttys. "ctrl+alt+F[1-6]" do not work. Actually, this is not entirely true: after I type "ctrl+alt+F2", all my keyboard inputs under X will be appear in tty2 (and not anymore in tty1). I can see that from /var/log/auth.log which has a lot of lines like this:
Quote:
May 13 10:15:45 data login[2182]: pam_unix(login:auth): check pass; user unknown
May 13 10:15:45 data login[2182]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/tty1 ruser= rhost=
May 13 10:15:48 data login[2182]: FAILED LOGIN (2) on '/dev/tty1' FOR 'UNKNOWN', Authentication failure
These errors are due to the fact that tty1 receives a wrong login (something I typed under X, before pressing RET). BTW: If I connect to xdm using my password (instead of my passphrase, thanks to pam_ssh), then I login into tty1 at the same time.
I checked that X is running under tty7. "ck-list-sessions" returns:
Quote:
Session1:
(...)
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
(...)
Under X, if I type "ctrl+alt+F7" and "RET", then X crashes and it is launched again. After this, all is working fine: the tty[1-6] can be accessed and the keyboard inputs do not go anymore to them when I am under X.
I face the same problem on two different computers (a desktop computer and a laptop). Notice that I face the problem even with pam_ssh not installed (I mentioned pam_ssh earlier).
The following message comes up when I boot up: Logging in user Warning: Cannot open ConsoleKit session: Unable to open session: Launch helper exited with unknown return code 0. When I press OK, the system completes the start up and everything looks normal. But when I try to connect to internet, I get the following message:
KNetworkManager cannot start because the installation is misconfigured. System DBUS policy does not allow it to provide user settings; contact your system administrator or distribution. KNetworkManager will not start automatically in future. If I reboot the system, I logg in successfully. So far the problem has appeared approximately upon every second time I boot up. Rebooting the system seems to take care of it.
Don't know what info is of interest. I'm using
Opensuse 11.2
KDE 4.4.2 (Factory)
After upgrade from 4.4.1 to 4.4.2 it worked fine for a week or so.
I do a clean install of slackware64 13.1 beta1 with KDE and switch default runlevel to 4 in /etc/inittab.
I try to login in kdm, I always come back to the login....
I try this with default runlevel 3 and an .xinitrc with "ck-launch-session startkde" .. works without problems, so I switch back to default runlevel 4, now i can login and only get the error "Cannot open ConsoleKit session: Unable to open session..."
Here are some logs
syslog
Code:
Code:
I have configured a squid proxy; it's running, but there was a problem: it does not provide service to client side.
The error was: "could not connect to session manager" "cannot open the network socket"
I could not solve examining the start and stop scripts. When I boot (default runlevel 5) my system all log messages are displayed on /dev/tty1. After the boot process has finished and kdm is started no more console messages are displayed on /dev/tty1. Instead all console output is redirected to /dev/tty7. When I change the runlevel from 5 to 3 boot.msg shows
Code:
Changing back to runlevel 5 gives
Code:
Why kdm redirects console output to /dev/tty7 instead of /dev/tty1?
Since doing an update (Kubuntu 10.04), this message appears when attempting to log in;
Quote:
Warning: cannot open ConsoleKit session: Unable to open session: the permission of the setuid helper is not correct.
After clicking ok on the above warning, the system logs in, but gives 2 error messages;
- removed sound devices
- KNetworkManager cannot start because the installation is misconfigured. System DBUS policy does not allow it to provide user settings. contact your system administrator or distribution. KNetworkManager will not start automatically in future.
I stream my local police station dispatch on the web using an icecast/darkice configuration [URL]. The downside of using this software is that once you initiate darkice, a terminal has to be open - the process does not run in the background.
I tried placing a monitor on my server (ouch, that hurt) and keeping darkice alive that way, but my mail server kicks the process. Now, I set the KeepAlive variable to something outrageous and keep an ssh session open on my desktop box to keep the stream going. Screen does not work as Postfix boots that as well.
keeping the process going indefinately?
To try another windows manager, I have to open a new display without a windows manager. The problem is that when I run
Code:
startx -- :1
kde runs automatically on it. How can I open a graphic session without a window manager?
Just installed Fedora 12 on a P4 IBM. Everything installed fine. Then, I rebooted, installed updates, and installed a few simple programs (emacs, ssh server). I rebooted since some kernel updates had been made. I can't login anymore. I get a brief message at GDM that says "unable to open session" after I enter my password. Root also doesn't work, but I figured out that root logins are disabled. I found something that recommended disabling selinux, so I reboot with selinux=0 parameter. That still didn't fix the problem, but did initiate selinux to re-label everything on the next boot.
My next thought was that maybe my password got corrupted, so I went into single usermode. I ran passwd justin, so I know that my password is correct. I still can't login via GDM or on a tty.
EDIT: I was also thinking I might need to uninstall something that I did; however, networking is disabled in single usermode, and if I init 3, then I get a login prompt that I can't open. Is there a way that I can enable root login? That might be a starting point to see if it's my user account or a general login problem.
My Fedora 12 box got that error after some updates on it.
I can login but it's prompting that error and everything will be a black space.
But still no good.
According to the log messages, the ConsoleKit session isn't initializing. I can't paste the logs here coz it's on another laptop.
I could think of just upgrading it to Fedora 13 but there's no way I can backup all of my files on it. Is it just safe to upgrade it?
when I type:
Code:
After the command has run (verified with atq) I cannot attach to screen using "screen -r" and ps shows screen is not running:
Code:
why the 'at' command can't start screen in the background for me to attach to later?
Noticed screen is actually returning "Must be connected to a terminal." to logs. Does 'at' not provide a terminal?
i wanna use the x11-forwarding feature to connect me to an open session. is that possible? i have a linux-machine on which runs the jdownloader. the jdownloader is only as java-gui-only-tools available. so it runs always on a open x11-session on the linux-machine. i wanna configure this tool from everywhere. how can i make this? (if it is possible i wanna use x11-forwarding).
View 1 Replies View RelatedMy server (CentOS 5.5) is a ldap client authenticate to LDAP server (Successfully authenticate) I use pam for ssh. I can ssh successfully with any users on system. But I cannot su - from ssh. It display the error: Could not open session. I look to log file and it shows: # tail -f /var/log/secure
View 5 Replies View RelatedAfter following a tutorial to install a pxe server for debian network install I can't log in my user session on gnome anymore
I got an error saying : /$home/.dmrc was ignored, can't save session and language the file must belong to the user and has persmission 644
I remember on my last session i got some icons on my home folder with a little lock icon on them i tried to remove them successfully using the command line but i still can't login. however i can successfully login with another user.
I'm using wmctrl on an Ubuntu machine to manage windows from a script, that I run inside a (gnu) screen.
If I start the screen session from the local machine, wmctrl works fine, including if I completely close the terminal window and issue the wmctrl commands when connecting to the screen remotely via ssh.
Conversely, if I connect remotely with ssh and start a screen, wmctrl doesn't work (returns "Cannot open display") even if I attach that screen session locally from the Ubuntu Terminal.
I guess there is some hidden screen parameter that doesn't get set in a way that allows accessing the display when it's launched remotely -- any ideas what it is and how to modify it from within a remote ssh-screen session so that that the script can access the windows?
I coundn't log in fedora anymore. Everytime i try, i receive the report "unable to open session".
View 6 Replies View RelatedI have some typical issue while trying to connect to my root or other users from my terminal.
like su - asking for password and after that it displyed a message like $su -
Password: could not open session
I tried connect using ssh then I am getting the following $ssh root@localhost Last login: Sun Nov 1 14:13:45 2009 from localhost Connection to localhost closed.
Background: Before this happended, I was tryied modify sshd_config in /etc/ssh/ folder to allow passwords less than 2 words.
I am trying to install Fedora 14 or 15 into a 2008 R2 Hyper-V environment. I can successfully run the install and log into the system as a user. I need to install the integration components so the mouse works. However, I can't find a way to get a terminal window open so I can mount an .iso with the installers.
View 2 Replies View RelatedI am currently running Suse 11.3. I continue to get the following error when logging into the KDE login manager with my user account
"Warning: Cannot open ConsoleKit session: Unable to open session. The name
org.freedesktop.ConsoleKit was not provided by any .service files."
After acknowledging the error, it resets back to the login manager screen. If I login with root, I get the same message, but it continues on and logins into the session
On my ubuntu 9.10 pc i am not running a GUI.
Every thing is run from command line.
How do i start a second telnet session from command line.
Plus can i have 4 telnet session open and move from one to the next and back again.
I am trying to write a bash script to open 1 screen session with multiple windows... each one running a different service. Is this possible? I tried several things, and I can start up multiple sessions really easy.. but not 1 session with multiple windows...
I want this so I can attach to that session and quickly move between the different windows.
I have installed virtualbox on opensuse 11.2 64bit.
When I go to open a machine it says
"Failed to open a session for the virtual machine Windows XP. The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1."
"
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
[Code].....
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary."
I'am using gentoo linux. After some system's updates VirtualBox stoped loading any virtual machine with error:
Code: Failed to open a session for the virtual machine. Virtual machine has terminated unexpectedly during startup.
Details:
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Machine
Interface: IMachine {99404f50-dd10-40d3-889b-dd2f79f1e95e} Kernel log
Code:
So, i've rebuilded all VirtualBox dependencies with safe flags, then i've recompiled most of the sys-* packages also with safe flags. However VirtualBox still doesn't work.
UPD: virtualbox-bin-3.1.4
UPD2: 3.1.6 and ose-versions crashes with same errors
I just tried FreeNX. I work great. I am thinking about uninstalling the vino/vnc on my machine.
However, I'd like to know if FreeNX can access the session that open locally on the server. I tried session 0 and 1, none of them can access the local session.
For default vnc, the connection will let you access the local session on the server. Can FreeNX do that?
I have a question regarding runlevels, shutdown procedure and KDM. I am on a freshly installed Slackware64 13.37 multilib system. The default runlevel in /etc/inittab is set to 3: multiuser w/o X.
Now, I log in as root and issue the command:
Code:
As expected, KDM starts up, and I log in to KDE (or another WM/DE) as a normal users. When I am finished, I either issues
Code:
In Konsole or click on Shutdown in the KDE menu. The shutdown process is initiated, as expected, but then it stops, and a window alerts me, that there is a session open by user 'root'. If I click OK, the machine is finally shut down.
Now, if I interpret this correctly, the behaviour of Slackware64 13.37 has changed here, compared to 13.1. In previous versions, the root seesion was closed, when I changed the runlevel to 4 with the telinit command. Now, the session remains open, obviously.
My question is: Is this the correct behaviour, and isn't this a security whole? An unnoticed (!) open root session while I am surfing the web as an unprivileged user in KDE could be dangerous, I think...
Is it misconfiguration in my system, or is this the way it should be?
I would love to auto-start tomboy at startup. How can I do this ? [Moderator edit: fixed Subject so nobody would expect an automatic Lunch. Is that the same as a free one? ]
View 2 Replies View RelatedI'm ssh'ed into a machine and logged in as a different user. Is it possible to open a few new windows that will still be ssh'ed into that same machine, still logged in as that user?
View 2 Replies View RelatedI am using SLES 10 SP3(x86_64). I was trying to install gtk/wxwidget through yast.
After that i rebooted my system, now system is failing to load in GUI mode.
If i can give the log of last few lines are as follows
Then it asks for login, only shell is available for me. How to login to gui mode..
I tried using the command gnome-session it gives error (gnome-session: 4101): Gtk-Warning **: cannot open display:
Also i tried using init 5, but again it prompts the my servername.