You are not logged in.

#1 2013-02-08 14:23:25

Vortex375
Member
Registered: 2009-02-24
Posts: 59

KDE 4.10: unable to unlock screen

Since upgrading to 4.10 I cannot unlock the screen once the screen locker starts (either manually via Ctrl+Alt+L or via timeout). The screen just turns black and no matter what I do I can't get to a password prompt. The only option is to kill X.

This happens with all locker types. Also, if you set the locker type to "screen saver" the screen saver does not start but a black screen is displayed instead.

I get the following log output in .xsession-errors (seems like something goes wrong):

ksmserver(13180) ScreenLocker::KSldApp::lock: lock called
ksmserver(13180) ScreenLocker::LockWindow::showLockWindow: Lock window Id:  29360145
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 29360145
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400322
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400324
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400330
ksmserver(13180) ScreenLocker::LockWindow::x11Event: Already existing toplevel for ReparentNotify
ksmserver(13180) ScreenLocker::LockWindow::x11Event: Already existing toplevel for ReparentNotify
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400338
ksmserver(13180) ScreenLocker::LockWindow::x11Event: Already existing toplevel for ReparentNotify
ksmserver(13180) ScreenLocker::LockWindow::x11Event: Already existing toplevel for ReparentNotify
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400351
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400364
kscreenlocker_greet(13448)/kwin ScreenLocker::Greeter::loadGreetPlugin: GreeterPlugin  "classic"  ( classic ,  Username + password (classic) ) loaded
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400373
kscreenlocker_greet(13448) KeyboardConfig::load: configuring layouts true configuring options false
kscreenlocker_greet(13448) X11Helper::getGroupNames: Fetched layout groups from X server: 	layouts: ("de", "us") 	variants: ("nodeadkeys", "")
kscreenlocker_greet(13448) X11Helper::getGroupNames: Fetched layout groups from X server: 	layouts: ("de", "us") 	variants: ("nodeadkeys", "")
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400381
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QDeclarativeExpression: Expression "(function $model() { return sessions.model })" depends on non-NOTIFYable properties: 
    ScreenLocker::SessionSwitching::model
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
file:///usr/lib/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: Possible anchor loop detected on fill.
file:///usr/lib/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: Possible anchor loop detected on fill.
QPainter::begin: Paint device returned engine == 0, type: 2
file:///usr/lib/kde4/imports/org/kde/plasma/extras/ScrollArea.qml:96: TypeError: Result of expression 'verticalScrollBar' [null] is not an object.
file:///usr/lib/kde4/imports/org/kde/plasma/extras/ScrollArea.qml:120: TypeError: Result of expression 'horizontalScrollBar' [null] is not an object.
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: UnmapNotify: 73400373
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: UnmapNotify: 73400381
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400389
ksmserver(13180) ScreenLocker::LockWindow::x11Event: Already existing toplevel for ReparentNotify
ksmserver(13180) ScreenLocker::LockWindow::x11Event: Already existing toplevel for ReparentNotify
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400397
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: MapNotify: 73400397
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 56 (X_ChangeGC)
  Resource id:  0x0
kwin(13185) KWin::Toplevel::updateUnredirectedState: Unredirecting: 'ID: 29360145 '
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: MapNotify: 29360145
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 29360159
ksmserver(13180) ScreenLocker::LockWindow::x11Event: Already existing toplevel for ReparentNotify
ksmserver(13180) ScreenLocker::LockWindow::x11Event: Already existing toplevel for ReparentNotify
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 73400408
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: UnmapNotify: 214
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: Unknown toplevel for MapNotify
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: UnmapNotify: 37749668
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 37750075
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: UnmapNotify: 37750075
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 37750083
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: UnmapNotify: 37750083
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: UnmapNotify: 37750075
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:189:21: QML TextEdit: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
file:///usr/lib/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
file:///usr/lib/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 37750316
ksmserver(13180) ScreenLocker::LockWindow::x11Event: Already existing toplevel for ReparentNotify
ksmserver(13180) ScreenLocker::LockWindow::x11Event: Already existing toplevel for ReparentNotify
ksmserver(13180) ScreenLocker::LockWindow::x11Event: CreateNotify: 37750324
plasma-desktop(13197)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: UnmapNotify: 37750324
kio_http(13411)/kio (TCPSlaveBase) KIO::TCPSlaveBase::disconnectFromHost:
kio_http(13413)/kio (TCPSlaveBase) KIO::TCPSlaveBase::disconnectFromHost:
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:189:21: QML TextEdit: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
ksmserver(13180)/plasma ScreenLocker::LockWindow::x11Event: UnmapNotify: 37750324
[/usr/bin/nepomukservicestub] nepomukfilewatch(13332)/nepomuk (filewatch service) Nepomuk2::FileWatch::watchFolder: "/home/ich"
[/usr/bin/nepomukservicestub] nepomukfileindexer(13333)/nepomuk (strigi service) Nepomuk2::IndexScheduler::slotScheduleIndexing: Idle

Offline

#2 2013-02-08 14:52:21

koyote
Member
From: spain
Registered: 2012-10-10
Posts: 31

Re: KDE 4.10: unable to unlock screen

Same here, can't unlock screen and I must kill X server. Using privative nvidia driver and x86_64.


Desktop: ASUS P5Q · Intel Core2Duo E7400 2.8 Ghz (Asus V72) · nVidia GeForce GT 440 · 8 GB (4x 2GB) Corsair XMS2 DDR2/800 + Kingston KVR800 DDR2/800 · WD RE4 500 GB + WD Green 1 TB · Pioneer DVR-109 · Samsung SyncMaster BX2231

Laptop: Asus F554L - Intel Core i3 4005U 1.7 Ghz · 4 GB Hynix/Hyundai DDR3/1600 · Intel HD Graphics 4400 · HGST Travelstar Z5K500 · HL-DT-ST DVDRAM GUE1N

Offline

#3 2013-02-08 14:55:15

headkase
Member
From: Canada
Registered: 2011-12-06
Posts: 1,586
Website

Re: KDE 4.10: unable to unlock screen

I upgraded to KDE 4.10 as well.  The oddness I'm noticing is different: the screen will always lock instead of just go the the blank screensaver with no lock that I want.  I've just disabled the locking and screensaver completely for now.  The only thing that stood out for myself during the upgrade is that there was a .pacnew file for kdmrc.  Did you take care of that?

/usr/share/config/kdm/

with the files being "kdmrc" and "kdmrc.pacnew"

I just replaced my modified kdmrc with the pacnew and reconfigured it again through system settings.


We all make choices, but in the end, our choices make us.

Offline

#4 2013-02-08 15:58:53

Vortex375
Member
Registered: 2009-02-24
Posts: 59

Re: KDE 4.10: unable to unlock screen

I just tried with a fresh user account and it WORKS. I can lock and unlock the screen without problems.

So, there's definitely a configuration problem but I'd rather not reset my whole KDE settings. I already tried removing ~/.kde4/share/config/kscreensaverrc but that didn't help. Any other ideas? :-)

Offline

#5 2013-02-08 16:00:24

Xabre
Member
From: Serbia
Registered: 2009-03-19
Posts: 618

Re: KDE 4.10: unable to unlock screen

Isn't screen locking moved out of kscreensaver into kwin now?

Last edited by Xabre (2013-02-08 16:04:29)

Offline

#6 2013-02-09 17:33:27

Vortex375
Member
Registered: 2009-02-24
Posts: 59

Re: KDE 4.10: unable to unlock screen

In the meantime, does anyone know if it is possible to unlock the screen from the console?

I tried everything to kill the screenlocker but apparently it was really well made. Once you kill it it immediately gets restarted by ksmserver. And if you kill ksmserver your session is closed, so it has the same effect as Ctrl+Alt+Backspace.

This is really enfuriating. KDE is locking me out of my system and it is doing it really well.

Is there maybe a way to send the unlock signal via DBUS or something?

Offline

#7 2013-02-09 22:06:38

fpilee
Member
From: Windows 7
Registered: 2011-10-06
Posts: 104
Website

Re: KDE 4.10: unable to unlock screen

I get a related issue, can't lock the screen with "CTRL+ALT+L". And the AIR plasma theme sucks!!! Why have modified it?

Last edited by fpilee (2013-02-09 22:07:03)

Offline

#8 2013-02-10 04:44:23

AdrianTM
Member
Registered: 2008-04-01
Posts: 18

Re: KDE 4.10: unable to unlock screen

fpilee wrote:

I get a related issue, can't lock the screen with "CTRL+ALT+L". And the AIR plasma theme sucks!!! Why have modified it?

Same here, and I hate that the password box doesn't have the focus when I try to unlock it.

Offline

#9 2013-02-10 11:46:48

Vortex375
Member
Registered: 2009-02-24
Posts: 59

Re: KDE 4.10: unable to unlock screen

fpilee wrote:

I get a related issue, can't lock the screen with "CTRL+ALT+L".

Open "Global Keyboard Shortcuts" in System Settings and choose "The KDE Session Manager". Change the shortcut for Lock Session to something else, then reset it to Ctrl+Alt+L. Test if that works.

If it doesn't, log out and remove ~/.kde4/share/config/kglobalshortcutsrc. That will reset all your custom global shortcuts, unfortunately, but made the shortcut working again, for me. Except, of course that I still can't unlock the screen, so it's useless.

And the AIR plasma theme sucks!!! Why have modified it?

You can always choose another theme if you don't like it. I think it looks much better now, especially the popups.

Last edited by Vortex375 (2013-02-10 11:48:14)

Offline

#10 2013-02-10 11:57:37

Vortex375
Member
Registered: 2009-02-24
Posts: 59

Re: KDE 4.10: unable to unlock screen

Oh, I can unlock again. It was the widget style I was using (Oxygen Transparent) that caused the problems. I switched back to Oxygen and the unlocker is working again.

And the AIR plasma theme sucks!!!

You might also be experiencing a bug. If your panel displays as just a opaque white block, log out and delete the directories /tmp/kde-<username> and /var/tmp/kdecache-<username>. That should fix your graphical issues.

Last edited by Vortex375 (2013-02-10 12:01:41)

Offline

#11 2013-02-13 15:43:09

Ethefor
Member
Registered: 2012-03-12
Posts: 4

Re: KDE 4.10: unable to unlock screen

Oh, that's right. I was also using Oxygen Transparent, and when I switch to normal Oxygen, unlocker works. But I really like Oxygen Transparent, any idea how to fix unlocker with Oxygen Transparent?

Offline

#12 2013-02-13 16:18:23

Vortex375
Member
Registered: 2009-02-24
Posts: 59

Re: KDE 4.10: unable to unlock screen

Yes!

Open the Oxygen Transparent settings (click "Configure..." next to the widget style). Click "Exceptions..." and add an exception for "kscreenlocker_greet". Make sure you spell it exactly like this (without the quotes).

Offline

#13 2013-02-13 17:24:17

AdrianTM
Member
Registered: 2008-04-01
Posts: 18

Re: KDE 4.10: unable to unlock screen

Thanks about the info about kscreenlocker_greet, that helped me find a solution to the CTRL-ALT-L shortcut, I created a new shortcut and made it execute /usr/lib/kde4/libexec/kscreenlocker_greet now the shortcut works just fine.

Offline

#14 2013-02-13 17:31:34

benny_kenobi
Member
From: poland
Registered: 2011-04-15
Posts: 17

Re: KDE 4.10: unable to unlock screen

headkase wrote:

The oddness I'm noticing is different: the screen will always lock instead of just go the the blank screensaver with no lock that I want.  I've just disabled the locking and screensaver completely for now.

I'm experiencing the same thing -- the screen always locks itself, no matter what combination of settings I choose. Have you by any chance come across any solution for that problem?

[update] found something that pertains to that little annoyance: https://git.reviewboard.kde.org/r/108425/

Last edited by benny_kenobi (2013-02-13 17:47:11)

Offline

#15 2013-02-13 19:29:55

Ethefor
Member
Registered: 2012-03-12
Posts: 4

Re: KDE 4.10: unable to unlock screen

Vortex375 wrote:

Yes!

Open the Oxygen Transparent settings (click "Configure..." next to the widget style). Click "Exceptions..." and add an exception for "kscreenlocker_greet". Make sure you spell it exactly like this (without the quotes).

Thank you! This works perfectly smile

Offline

#16 2013-02-16 12:15:55

OdinEidolon
Member
From: Belluno - Italy
Registered: 2011-01-31
Posts: 397

Re: KDE 4.10: unable to unlock screen

I also have this problem but I use the standard Oxygen style.
- Using the simple locker the locker appears and I can unlock, but password input will not look as highlighted. I have to insert the password and press enter, even though it does not seem to do anything
- Using the custom locking screen the system seems to freeze


Hardware: 2016 Dell XPS15 - FullHD - i5-6300HQ - 8GB DDR4 - Nvidia GTX960M - Samsung 840EVO 250GB SSD - 56Wh
Software: Plasma 5 - rEFInd - linux-ck - preload - prelink - verynice - psd - bumblebee

Offline

#17 2013-03-02 23:11:10

Vash63
Member
Registered: 2012-09-22
Posts: 19

Re: KDE 4.10: unable to unlock screen

I'm also having this issue... whenever the screen locks, whether from time or using the keyboard command, from that point on all input devices do nothing within X. I can still ctrl+alt-F1 and if I restart kdm everything is fine. Using latest nvidia drivers on KDE4.10.

Has anyone managed to find a solution to this?

Edit: I should note that switching "Screen Locker" to simple seems to avoid the issue... but that's not really a fix.

Last edited by Vash63 (2013-03-02 23:13:32)

Offline

#18 2013-08-06 19:52:45

int_ua
Member
Registered: 2011-10-15
Posts: 2

Re: KDE 4.10: unable to unlock screen

In my case killing plasma-overlay helped

Offline

#19 2013-12-29 17:10:51

OdinEidolon
Member
From: Belluno - Italy
Registered: 2011-01-31
Posts: 397

Re: KDE 4.10: unable to unlock screen

Anyone knows a fix for this problem? I have this problem with KDEsince 4.10 and still have it now. System up to date, using Oxygen style.

The simple locker works really well while the configurable one freezes the system (it does not even appear).

Last edited by OdinEidolon (2013-12-29 17:11:12)


Hardware: 2016 Dell XPS15 - FullHD - i5-6300HQ - 8GB DDR4 - Nvidia GTX960M - Samsung 840EVO 250GB SSD - 56Wh
Software: Plasma 5 - rEFInd - linux-ck - preload - prelink - verynice - psd - bumblebee

Offline

Board footer

Powered by FluxBB