Bug 8922 - can't login after display goes to sleep
Summary: can't login after display goes to sleep
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-31 23:27 CET by mat ali
Modified: 2016-06-07 14:30 CEST (History)
2 users (show)

See Also:
Source RPM: dbus ?
CVE:
Status comment:


Attachments

Description mat ali 2013-01-31 23:27:42 CET
Description of problem:

after some minutes, display goes into energy saving mode and moving mouse wake it up, asking for password (awaited). But entering password here (root or user) doesn't work. Only hitting change user, choose the user you were logged with and then entering password works, but it is slow.

Version-Release number of selected component (if applicable):

french keyboard (trying to type password in qwerty didn't help but it may be the source of problem ?)

How reproducible:

1) configure your display to enter energy saving mode after one minute
2) wait until it triggers
3) move mouse
4) enter password (it doesn't work)

Solve :
5) click change user
6) select currently used username
7) enter password (it works)
Comment 1 Manuel Hiebel 2013-02-01 00:55:57 CET
what desktop do you use ? (and dm)

Keywords: (none) => NEEDINFO

Comment 2 mat ali 2013-02-01 11:03:44 CET
Oups sorry, I use Gnome 3 classic. I didn't change anything in the configuration. Driver is ATI Radeon HD 6400 a... in option are transparency(composite) and hardware cursor activated (it was the default). NO 3D Effects. That's all.
It's a fresh install from liveDVD Gnome with updates and fglrx driver and gnome classic (as proposed in "sessions" in login screen) nothing fancy.
Comment 3 mat ali 2013-02-01 11:05:27 CET
oh yes, the dm is kdm, maybe the problem. I guess it changed automatically as i installed KDE meta package...
Comment 4 mat ali 2013-02-01 11:19:50 CET
Switching to GDM didn't change anything, I still have to click change user first to get my password accepted
Comment 5 mat ali 2013-02-01 18:23:03 CET
hiting ctrl+alt+F2 bring the right login screen.
Not sure at the moment that it is the source this other problem :
after hiting change user and loging in i can't start gnome-terminal, i had to start Konsole to get a terminal. Trying to launch gnome terminal there give the following message (in french sorry):

gnome-terminal 
Erreur GConf : Le serveur de configuration ne peut être contacté: Erreur D-BUS : Le service GConf est en cours d'arrêt.
Erreur GConf : Le serveur de configuration ne peut être contacté: Erreur D-BUS : Le service GConf est en cours d'arrêt.
Erreur GConf : Le serveur de configuration ne peut être contacté: Erreur D-BUS : Le service GConf est en cours d'arrêt.
Erreur GConf : Le serveur de configuration ne peut être contacté: Erreur D-BUS : Le service GConf est en cours d'arrêt.
Erreur GConf : Le serveur de configuration ne peut être contacté: Erreur D-BUS : Le service GConf est en cours d'arrêt.
Erreur GConf : Le serveur de configuration ne peut être contacté: Erreur D-BUS : Le service GConf est en cours d'arrêt.
**
ERROR:terminal-app.c:1449:terminal_app_init: assertion failed: (app->default_profile_id != NULL)
Abandon

Firefox gives about the same error about DBUS and Gconf too.

It only happens after such resume from sleep mode.
claire robinson 2013-02-01 19:12:01 CET

CC: (none) => mageia

Manuel Hiebel 2013-02-03 13:42:11 CET

Keywords: NEEDINFO => (none)
Source RPM: (none) => dbus ?
Severity: normal => major

Comment 6 mat ali 2013-04-15 18:28:19 CEST
bug is still there. Every time my computer resume from sleep, I've to choose "change user" first, choose the user I was logged with and enter password. Otherwise, password is not recognized.
Comment 7 Morgan Leijström 2014-05-08 19:59:55 CEST
still valid?
-if so, on what version(s?)

CC: (none) => fri

Comment 8 Morgan Leijström 2016-06-07 14:30:39 CEST
Closing... this is so old, so please open a fresh bug if you still see this problem.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.