Can't get back to gnome from a "TTY terminal"
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Can't get back to gnome from a "TTY terminal"
No big deal, let's hope nothing serious lurks in the darkness here.
Ctrl+Alt+F1 (to F6) brings you to TTY1 (to 6)
To get back into gnome and your desktop you do Ctrl+Alt+F7
That brings me to a black screen with just a cursor - cursing my bad luck
I should see the desktop - right?
Ctrl+Alt+F1 (to F6) brings you to TTY1 (to 6)
To get back into gnome and your desktop you do Ctrl+Alt+F7
That brings me to a black screen with just a cursor - cursing my bad luck
I should see the desktop - right?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
- sanguinemoon
- Level 2
- Posts: 77
- Joined: Tue Mar 20, 2007 5:08 am
This appears to be another manifestation of a known bug in the current nVidia drivers, which can cause a black screen. I've experienced this glitch with Bianca running Beryl 0.2.0 Emerald, and also with PCLinuxOS 2007 TR3 running Beryl 0.1.9999 Emerald. In both cases, the nVidia driver is version 1.0-9755.
I had a text editor open in X when I did CTRL-ALT-F1 to go TTY. I then did CTRL-ALT-F7 and got a black screen with an I-beam cursor. So, on a hunch, I blindly tapped a few keys and then CTRL-S. After restarting X, I reopened the text file and saw the letters that I had blindly typed at the black screen. Evidently, the earlier X session context had indeed resumed after TTY, but it wasn't displayed because of the nVidia driver glitch.
This test went the same on Bianca (GNOME) and PCLinuxOS (KDE).
The Beryl Manager applet allows easy switching to the Metacity (or KWin) window manager, so the immediate solution is to right-click on the taskbar ruby icon and select Switch Window Manager to enable Metacity (or KWin) before going to TTY, then re-enable Beryl upon return to X.
------
I had a text editor open in X when I did CTRL-ALT-F1 to go TTY. I then did CTRL-ALT-F7 and got a black screen with an I-beam cursor. So, on a hunch, I blindly tapped a few keys and then CTRL-S. After restarting X, I reopened the text file and saw the letters that I had blindly typed at the black screen. Evidently, the earlier X session context had indeed resumed after TTY, but it wasn't displayed because of the nVidia driver glitch.
This test went the same on Bianca (GNOME) and PCLinuxOS (KDE).
The Beryl Manager applet allows easy switching to the Metacity (or KWin) window manager, so the immediate solution is to right-click on the taskbar ruby icon and select Switch Window Manager to enable Metacity (or KWin) before going to TTY, then re-enable Beryl upon return to X.
------
I also had problems with Beryl screwing up my keyboard... wasted some three weeks of forum surfing to get all the buttons working properly.... thought the problems were due to non standard (croatian) codepage...
In the end I realised that I lost the ability to control screensavers while beryl was on... i.e. I had them turned off but still the screensaver came on every 10 minutes or so... very annoying while you're watching a movie... that was the final straw so I removed beryl
In the end I realised that I lost the ability to control screensavers while beryl was on... i.e. I had them turned off but still the screensaver came on every 10 minutes or so... very annoying while you're watching a movie... that was the final straw so I removed beryl
Beryl can be twitchy, but it has me hooked on the glass (translucency) effect. It's a terrific visual enhancement for a stacked-windows multimedia GUI.
I don't play video games on my PC, so it's high time for the pixel-shader to get off of the pogey. And what a spiffy 3D-accelerated sight it is. Going back to a 2D desktop feels as maladroit as using a web browser that doesn't sport mouse-gestures.
Though I'm sure if my PC got as jiggered as yours had, I'd escort Beryl to the bit bucket.
-------
I don't play video games on my PC, so it's high time for the pixel-shader to get off of the pogey. And what a spiffy 3D-accelerated sight it is. Going back to a 2D desktop feels as maladroit as using a web browser that doesn't sport mouse-gestures.
Though I'm sure if my PC got as jiggered as yours had, I'd escort Beryl to the bit bucket.
-------
- sanguinemoon
- Level 2
- Posts: 77
- Joined: Tue Mar 20, 2007 5:08 am
- sanguinemoon
- Level 2
- Posts: 77
- Joined: Tue Mar 20, 2007 5:08 am
- sanguinemoon
- Level 2
- Posts: 77
- Joined: Tue Mar 20, 2007 5:08 am
Confirmed. It's the Nvidia driver. In my xorg.conf file, I changed to the nv driver, and now I can get consoles. But running like this means no 3D acceleration
Or if it's a bug just in the newest drivers, I could just remove the driver Envoy installed and use the driver the repositories. That means no Beryl without having to do some extra steps, but I can take or leave Beryl.
Or if it's a bug just in the newest drivers, I could just remove the driver Envoy installed and use the driver the repositories. That means no Beryl without having to do some extra steps, but I can take or leave Beryl.
- sanguinemoon
- Level 2
- Posts: 77
- Joined: Tue Mar 20, 2007 5:08 am