I just installed F13 on my netbook (Toshiba NB205). Whenever the screensaver locks the screen (manually or due to a timeout), the unlocking of the screensaver causes my account to logout and I'm left at the GDM login screen. I've been seeing that the "work around" is to turn off the screensaver lock.
View 2 RepliesI have an account where a user has no password. And the tickbox is ticked where it doesn't ask her to enter one at login.When her screen gets locked though, I can't access it again.. i.e. a password is required. And entering nothing doesn't work.
View 1 Replies View RelatedRecently I've been having an issue where every now and then, all of a sudden fedora logs me out and takes me to the login screen.
All my unsaved work is lost and I have to log back in again.
Is there any way to diagnose this problem and figure out how to solve it?
If I try to logout or switch user, I end up with a black screen and a blinking cursor. I can type and the letters show up on the screen but don't do anything. I can do Ctrl-Alt-F1 and then "sudo service kdm restart", but I'd rather fix the underlying problem..Google gives several pages with similar problems but they all seem pretty old (2007), and they don't seem to apply to 10.10.
View 8 Replies View RelatedDell Latitude D610 Laptop on a docking station running Ubuntu 10.04 Have 2 monitors, monitor 1 using DVI, monitor 2 using VGA. Extended desktop working as intended out of the box...was not successful getting the ATI Catalyst Control Center to work, but no big deal.The big deal is, when I log out, my screen on the DVI monitor scrambles, and you cannot see the login prompt at all. I get the little drumbeat SFX, and attempt to press enter and blindly enter password, but no login. The VGA monitor remains blank
View 1 Replies View RelatedIf I logout on terminal, old contents are still possible to be read. I was trying to get it to work using pam_exec, by adding
Code:
Code:
This however didn't do antyhing. How to make it work using pam? I know that i can simply add some control codes to /etc/issue to get basically the same effect, but i wanted to do it using pam.
After updating my Slackware-Current (there was kernel and glibc package updates), I just get a black screen with a blinking "_" in the top-left corner when I logout.
I checked /var/log/kdm.log and found these errors:
Code:
I've found a workaround: uncommenting "TerminateServer=true" in kdmrc.
As a normal user I have activated the functions of the Quit applet, i.e. Logout, Shutdown and Restart are active buttons. I am able to restart or shutdown, no problems. But when I use the Logout button I don't get logged out, just returned to the login shell & I am still logged in as my user. I don't have a display manager installed and I do NOT want to use a display manager such as XDM or GDM. How do I get the Logout button to actually logout the user? It appears I am only getting logged out of the x-session, but I want complete logout.
View 6 Replies View RelatedEvery time me or another user uses the "log out" option were faced with a black screen that does not go away, unless the computer is restarted. i've left it for an hour thinking it might have just slowed down or something but that was a no go, and it happens each time you try to use it. the strange thing is if the black screen is up programs still run. i have a media server running most of the time and i have no problem accessing it while the black screen is showing.
Another problem im having is that sometimes when a user logs in they have no sound. the sound icon is showing that no sound is installed, but when another user logs in there is no problem and sound works fine.
Lastly i dont know if this is a feature or a problem. the first user to log in will always have control over the network connection. for example if my mother logs in first the icon to switch connections will show up on the top of her screen and she has full access to what connections she wants to use, also her account is just a basic user account. now when i log in i wont have the network icon on the top of my screen, and my account is the main admin account.
I'm trying to run Slackware 13.37 64-bit in a VirtualBox virtual machine. My VirtualBox version is 3.2.12. I had to disable compositing to keep the X-Server from reporting a segfault.Now the problem is that on logout from KDE I get a completely black screen. I can switch to a console session and type commands to get the login screen again.
telinit 3
telinit 4
I tried editing "kdmrc" to add the line "TerminateServer=true" but it had no effect on the problem.I had this working with Slackware 13.1 at one time, but I can't seem to get it working properly now even without desktop effects.I'm trying to avoid changing my VirtualBox software since each version seems to just introduce new and different bugs. The 4.X versions are not yet very stable.
So I have Ubuntu Lucid machines about 20 of them. Configured via ldap authentication. I seem to be running into a rather strange logout problem. Whenever users click logout they're logged out, however after that all i get is the background screen with the cursor. The cursor is able to move, but no login screen.If i go to a terminal window alt+f1 and do a service gdm restart, then the login screen goes back to normal.
View 3 Replies View RelatedHowever, there are one or two stability issues. In particular, over the last couple of days, I have seen two occasions where my screen suddenly goes blank, and after about 3 seconds I am presented with the login manager. I can then log in, and the desktop works fine again. Of course, everything I was doing is gone... So, where do I look to find what is causing the problem? I'd like to find out and either fix this here or submit a useful bug.
View 9 Replies View RelatedI'm using Slackware 13.1.
Whenever I logout of KDE and go back into console mode, the characters at the console screen become unreadable gibberish. Is anyone else having this problem?
I can ctl+alt+F? to work at another console screen, but the ctl+alt+F1 screen remains unreadable until I reboot.
I have a problem with garbled graphics after resuming from hibernate or logging out (when the screen blinks and goes back to the display manager). It only occurs when I do either, about half the time. What happens is the edges of everything "bleed" horizontally (left to right) in red and green colors and black text on a white background becomes entirely unreadable (but white text on a black background is readable and just looks a little bolder). If I shut down or restart the computer (softly) when the screen has garbled, then it will freeze and not even the SysRq keys work (I have enabled it in /etc/sysctl.conf). Then the only thing left is to do a hard restart (in which case there's a voice saying "System failed VGA test" before BIOS/GRUB loads) or poweroff. Powering it off and then starting it again works fine. I did a google image search and this is sort of how it looks when it freezes: link
Once the screen has garbled (but only if it hasn't frozen) I can use SysRq to issue S E S I S U O to shut it off and then power it on, and that works: then I get a non-garbled command line after sigterm and it shuts off and starts up properly. If I issue B instead of O (to restart) I get the "System failed VGA test" on boot (but it doesn't freeze when shutting down). Hibernation is easy enough to fix by just turning it off (it's not a laptop so I don't need it anyway), but it still happens sometimes when I log out. So as long as I never change users the system works perfectly and this never happens. I've tried GNOME, Xfce4, OpenBox without any DE, gdm3 and SLiM and the problem persists in all of them.
Some system details:
Debian Squeeze i386 (using only software from the stable main repository)
Kernel: 2.6.32-5-686
Video card: ATI Radeon 9600SE (using the preinstalled open source drivers)
Motherboard: ASUS P4P 800-E
By the way: sometimes when it's in the process of shutting off (when the display hasn't been corrupted), after it kills all graphical applications, I can see that the CLI text gets the garbled look, but at that point the poweroff works without freezing. This is the most similar sounding bug that I could find: [URL]. Unfortunately I can't find a solution to it, and most people who have similar problems seem to get either the garbled graphics or the freezes, but not both. Also: how safe is it to keep shutting off with SysRq to recover from this? Can I get disk errors?
i installed Xubuntu desktop and decided i didn't like and uninstalled it.. but it hijacked my boot screen and login/logout screen. i restored the boot screen but i can't find out how to restore the login/logout screen.
View 9 Replies View RelatedI have Lucid setup for multi user. Whenever 2 users are logged in and one logs off, it freezes on a black screen. It looks like it logs off OK and is on its way to the main login screen but never gets there. I found some older posts describing this problem but no solution. I tried to post to that thread but got a message saying I was not permitted. I am new to Linux and am struggling to figure out how to problem solve issues in Ubuntu.
View 1 Replies View RelatedI am using KDE4 on 10.10 64-bit.
Only ever use the KDE desktop so completely removed XFE and the rudimentary Gnome left behind on the install.
Not a desperate problem just an annoyance.
Everything works fine, except if I logout the next login screen is using a really tiny font and I can't seem to find anywhere to change it.
The DPI must be about 10, as I can't even read it when blown up on my projector.
When trying to "Leave" the system (either via the small button on the lower right of the taskbar or by right clicking on the Desktop and selecting "Leave") the logout / shutdown / restart screen comes up. I have the "Logout" desktop effect activated, which is supposed to desaturated the background when the Leave screen appears. However, instead of simply greying out the background, the image on the desktop and the rest of the screen also gets slightly distorted, with seemingly random distortion effects cropping up all over the place (e.g. horizontal lines or large blurs).
These distortions are different every time the Leave screen comes up. The Leave screen itself is displayed fine, and apart from the dodgy background I have no other issues with the whole process (the system shuts down or restarts properly according to my choice). I am using the Radeon drivers, and all other desktop effects I have on (Magic lamb, cover switch, present windows, etc) work fine and without a hitch. It's only the Logout effect that seems to glitch. Are the distortions intentionally created by the effect in order to emphasize the focus on the Leave screen?
When there is one user, and that person "Logs Out" instead of going to a screen where another user can choose to Log In - the computer goes to a blank screen; No mouse movements, mouse clicks or keys will reactivate. I have to reboot the whole computer.
Is there a way to get the computer to go to a 'switch user screen' when one user chooses to log out?
When I click logout under the user menu (top right), the confirmation dialogue appears, and I can click Logout. the dialogue disappears and it starts to logout normally... then it just stops. it freezes once the top toolbar disappears. my tint2 bar stays visable, as well as my desktop background, and i can move my cursor around, but it wont respond to my keyboard. After just letting it stay like that for a few minutes, nothing changes, it doesn't even dim the screen or go to sleep, it just sits there.
I can shutdown and switch users just fine, just not logout.
How doI change the time interval for auto-logout in gnome? Changing the TMOUT environmental variable only works for bash shell.
View 1 Replies View RelatedI am using Fedora 11 + kde 4.3.1 + compiz. for several times now my session ended unexpected, I can't reproduce that behavior and so I am looking for a log or someplace to look after such logout to find out what caused or triggered it.
I saw another thread about unexpected logout while browsing, its not the same although it happens to me so far while using firefox / mplayer / Kontact (kmail) .
tow simply looking problems, but I don't know how to do it1. Run a script as root after a users login. (not on startup)2. Run a script as root when the user logout.
View 7 Replies View Relatedi performed an upgrade from fedora 13 to 14 on my test fedora virtual machine (vmware player 3) and i have this incredible problem: I normally boot in runlevel 3 and i start X only when needed with the startx command.When I want to exit from the X environment I use the "log out <username>" command on the System menu (gnome is the desktop manager). After upgrading to fedora 14 and applying all the available upgrade, this won't work anymore! I'm able to start the X environment but when I try to logout the window/desktop manager got killed but X remain active, the background image is visible on the screen, no mouse or keyboard interaction is possible.
The system is stiil alive, i can login through ssh, but i was not able to do anything. manually switching the runlevel from 3 to 5 and viceversa with telinit doesn't solve the situation: switching to runlevel 5 cause the login screen to be visualized and i' can login in the gnome desktop environment but when i logout o when a try to switch to runlevel 3 I always obtain the same result: X remain active and unusable, it's impossible to go back to a text console. what can i do ? any of you has experienced a similar issue ?
i want to clear the /tmp directory when logout.how can it be set in bash_logout
View 1 Replies View RelatedI have three folders on my desktop that I want to delete and they are locked. They have the "X" and "Padlock" symbols. How do I unlock them to delete. They are there from bad installs of the ATI driver.
View 3 Replies View RelatedI am running the x64 version of Ubuntu 9.10. For the past 2 days(haven't installed any new programs within the same time frame). I've started to encounter problems after I lock my computer, (ctrl+alt+l), then come back and unlock it. After unlocking, I am unable to open any programs.
Attempts to open programs include: panel icon buttons, application menu buttons(including opening nautilus through the places menu), alt+F2, and using gnome-do. I also can't use any of the buttons in the user menu to the far right to log off or shut down the computer and am forced to hold the power button to restart my laptop. I am able to use programs that are already open with no problems.
Also, If i lock the laptop again, the screen darkens as expected, except, when i move the mouse to bring up the login dialog all i see is short flickers of my mouse as it moves around a black screen.
My most recent synaptic log includes:
Quote:
Commit Log for Sat Feb 27 17:09:49 2010
Upgraded the following packages:
foomatic-filters (4.0.3-0ubuntu2.1) to 4.0.3-0ubuntu2.2
google-chrome-unstable (5.0.322.2-r38810) to 5.0.335.0-r39561
lernid (0.5) to 0.6
sudo (1.7.0-1ubuntu2) to 1.7.0-1ubuntu2.1
So I just completed a clean install of Fedora 11 from the live CD. The only thing I've done to it thus far was to run the update manager once. Next item on the agenda was to configure my display to correctly handle my two monitors, but if I open up the controls and select 'Display' both my monitors instantly go blank. The only way to restore them is to use ctr-alt-backspace to logout. My graphics card is an ATI Radeon x800L, and right now I'm using the default ati driver that came with the system.
View 1 Replies View RelatedI've read some past issues with this and was wondering if anyone else has issues with F12 / F13.
When I logout of gnome or kde on a fresh install of Fedora 13 the panels disapear but I never receive the log on window. I cannot switch to command either the screen is locked completely.
I havn't run updates or anything, the install is nearly out of box except for the installation of kde.. The issue existed before I installed kde, I was hoping it didn't have this issue lol. fat chance of that..
Anyone aware of any fix's? Or what the issue is?
For some reason in the last few days I can no longer logout of KDE, nor will it let me shutdown the system. The only way out is to Ctrl+Alt+Backspace and then shutdown from there. Weird thing is other users can. For me the logout box just disappears and I carry on working or if effects are enabled, the screen blurs and I carry on working. After this the logout box doesn't come back up until I have restarted X (logged out).
I have tried disabling the desktop effects to no availe and I have looked in the messages / kdm logs. So far the only thing I can find is in KDM.log
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86TouchpadOn
> Internal error: Could not resolve keysym XF86TouchpadOff
I have no idea if this is at all relevant but there are several threads from Google relating to this and GDM, although no cures as far as I can tell.
I would rather not delete my ~/.kde folder again if at all possible as it takes ages to reset everything back to normal.