[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2021-06-21 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=419355

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #14 from Nate Graham  ---


*** This bug has been marked as a duplicate of bug 370676 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-05-26 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #12 from John Bennett  ---
Is this not worth investigating?
Have used many other Linux distros, and never had this issue. Don't believe it
is anything specific that I have done. If I don't LOCK the screen, and just let
it go blan, I don't have an issue.
HOW CAN I TROUBLESHOOT THIS
This is STILL happening.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-10-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=419355

Nate Graham  changed:

   What|Removed |Added

  Component|kcheckpass  |greeter
 CC||n...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-05-30 Thread The Feren OS Dev
https://bugs.kde.org/show_bug.cgi?id=419355

The Feren OS Dev  changed:

   What|Removed |Added

 CC||ferenos...@outlook.com

--- Comment #13 from The Feren OS Dev  ---
The only custom thing Feren OS does to the lock screen is have its own
Breeze-based lock screen theme that has very minimal code changes that should
not affect unlocking.


Everything else is all KDE neon.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-12-31 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=419355

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-04-07 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #3 from John Bennett  ---
Still having the issue.
Also, occasionally it keeps telling me my password is wrong (it's not!)
Last time Ctrl-Alt-F1 and logged in. Ran loginctl and tried to unlock the GUI
(How DOES this work?), then ran a loginctl session-status on the GUI:

c2 - john (1000)
   Since: Wed 2020-04-08 20:35:50 AEST; 8h left
  Leader: 1591 (lightdm)
Seat: seat0; vc7
 Display: :0
 Service: lightdm; type x11; class user
 Desktop: plasma
   State: online
Unit: session-c2.scope
  ├─  467 /opt/teamviewer/tv_bin/TeamViewer
  ├─ 1270 /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
--graceTime 15000 --ksldfd 32
  ├─ 1279 kcheckpass -m classic -S 7
  ├─ 1591 lightdm --session-child 12 19
  ├─ 1722 fingerprint-helper 5 6 :0 kde -d -user john dUmMy4
dUmMy5
  ├─ 2599 sleep 5
  ├─ 3141 /usr/bin/gnome-keyring-daemon --daemonize --login
  ├─ 3144 /usr/bin/startplasma-x11
  ├─ 3729 /usr/bin/ssh-agent /usr/bin/im-launch
/usr/bin/startplasma-x11
  ├─ 3752 /usr/lib/x86_64-linux-gnu/libexec/kf5/start_kdeinit
--kded +kcminit_startup
  ├─ 3753 kdeinit5: Running...
  ├─ 3755 /usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher
--fd=9
  ├─ 3759 kded5
  ├─ 3790 /usr/bin/kaccess
  ├─ 3794 /usr/bin/plasma_session
  ├─ 3813 /usr/bin/ksmserver
  ├─ 3816 /usr/bin/kwin_x11
  ├─ 3818 /usr/bin/xembedsniproxy
  ├─ 3820 /usr/bin/baloo_file
  ├─ 3822
/usr/lib/x86_64-linux-gnu/libexec/polkit-kde-authentication-agent-1
  ├─ 3824 /usr/bin/plasmashell
  ├─ 3826 /bin/bash /usr/bin/feren-latte-launch
  ├─ 3829 /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
  ├─ 3835 /usr/bin/gmenudbusmenuproxy
  ├─ 3836 /bin/bash /usr/bin/feren-latte-launch dbusmon
  ├─ 3837 latte-dock --replace
  ├─ 3838 dbus-monitor
type='method_call',destination='org.kde.Shutdown',interface='org.kde.Shutdown',path='/Shutdown',member=logout
interface='org.kde.Shutdown',path='/Shutdown',member='logoutAndReboot'
interface='org.kde.Shutdown',path='/Shutdown',member='logoutAndShutdown'
  ├─ 3839 /bin/bash /usr/bin/feren-latte-launch dbusmon
  ├─ 3858 /opt/vivaldi/vivaldi-bin
  ├─ 3864 /tmp/.mount_StrawbgpGybr/AppRun.wrapped
  ├─ 3867 /usr/bin/pulseaudio --start --log-target=syslog
  ├─ 3869 /usr/bin/perl /usr/bin/shutter --min_at_startup
  ├─ 3879 /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil
  ├─ 3893 /bin/bash /usr/bin/nemo-plasma-clicksync
  ├─ 3902 /usr/share/skypeforlinux/skypeforlinux
--executed-from=/home/john --pid=3874
  ├─ 3912 /usr/lib/at-spi2-core/at-spi-bus-launcher
--launch-immediately
  ├─ 3919 /usr/bin/dbus-daemon
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork
--print-address 3
  ├─ 3953 /usr/bin/python3 /usr/bin/onboard
  ├─ 3961 /usr/libexec/geoclue-2.0/demos/agent
  ├─ 3985 mintUpdate
  ├─ 3996 cat
  ├─ 3997 cat
  ├─ 4002 /usr/lib/at-spi2-core/at-spi2-registryd
--use-gnome-session
  ├─ 4045
/home/john/Applications/Strawberry-0.6.8_fee2e5f5d3b9913cb44badecf4ea3e41.AppImage
  ├─ 4073 /usr/bin/xsettingsd
  ├─ 4162 /usr/lib/x86_64-linux-gnu/pulse/gconf-helper
  ├─ 4172 /usr/share/skypeforlinux/skypeforlinux --type=zygote
  ├─ 4174 /usr/share/skypeforlinux/skypeforlinux --type=zygote
  ├─ 4216 /opt/vivaldi/vivaldi-bin --type=zygote
  ├─ 4232 /opt/vivaldi/vivaldi-bin --type=zygote
  ├─ 4379 /tmp/.mount_StrawbgpGybr/usr/bin/strawberry-tagreader
/tmp/strawberry_508288049
  ├─ 4380 /tmp/.mount_StrawbgpGybr/usr/bin/strawberry-tagreader
/tmp/strawberry_1150749259
  ├─ 4425 /usr/share/skypeforlinux/skypeforlinux
--type=gpu-process
--field-trial-handle=854271000521317683,13516305748316826786,131072
--disable-features=PictureInPicture,SpareRendererForSitePerProcess
--gpu-preferences=KAAgAAAgYAAAEAgA
--service-request-channel-token=15401314670283524777
  ├─ 4433 /usr/share/skypeforlinux/skypeforlinux --type=utility
--field-trial-handle=854271000521317683,13516305748316826786,131072
--disable-features=PictureInPicture,SpareRendererForSitePerProcess --lang=en-GB
--service-sandbox-type=network
--service-request-channel-tok

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-04-08 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #4 from David Edmundson  ---
Fingerprint wouldn't be invoked by the lockscreen unless the Pam files have
been changed.

That seems very relevant.

Did you do something to set that up? What's in your /etc/pam.d/KDE ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-04-08 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #5 from John Bennett  ---
I don't have a /etc/pam.d/KDE
Only recently changed files in that directory are:

common-account
common-auth
common-password
common-session
common-session-noninteractive

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-04-08 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #6 from John Bennett  ---
The only way I have managed to get back into the session is to start a terminal
session and kill kscreenlocker processes...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-04-14 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=419355

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #7 from Christoph Feck  ---
New information was added with comment 5 and comment 6; changing status for
inspection.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-04-22 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #8 from John Bennett  ---
Is there any way I can troubleshoot this?? Have tried remotely (ssh) using
loginctl to unlock the session - does nothing. Can kill the session, etc.
Would like to be able to use FerenOS, but currently can't, because the sessions
are being locked/losing data.
Using KDE/Plasma on opensuse15.1 + tumbleweed, on the same machine
(multi-booting Opensuse 15.1/Tumbleweed, FerenOS, and Winblows) and don't have
an issue.
I occasionally also get the issue where trying to log back in after the screen
saver kicks in, it tells me my password is incorrect, and won't let me back in.

How can I troubleshoot??

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-04-27 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #9 from John Bennett  ---
Created attachment 127935
  --> https://bugs.kde.org/attachment.cgi?id=127935&action=edit
LockedUp

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-04-27 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #10 from John Bennett  ---
Comment on attachment 127935
  --> https://bugs.kde.org/attachment.cgi?id=127935
LockedUp

Obviously is locking up while re-logging back in - see screenshot.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-04-28 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #11 from John Bennett  ---
Anything on this?
Would like to be able to use this, (and am still trying...), but need to make
sure there is nothing open if I leave it for a while.
Please?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-03-29 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

John Bennett  changed:

   What|Removed |Added

 CC||hornets...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-03-29 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419355

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from David Edmundson  ---
Is it reproducible with
/usr/lib64/libexec/kscreenlocker_greet --testing ?


Do you know if Feren OS has a customised lock screen compared to default
Plasma?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-03-29 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #2 from John Bennett  ---
:/$ /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing
OpenGL vendor string:   Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Desktop 
OpenGL version string:  3.0 Mesa 19.2.8
OpenGL shading language version string: 1.30
Driver: Intel
GPU class:  Haswell
OpenGL version: 3.0
GLSL version:   1.30
Mesa version:   19.2.8
Linux kernel version:   5.3
Requires strict binding:yes
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
"file:///usr/share/plasma/wallpapers/org.kde.plasma.worldmap/contents/ui/main.qml"
 
 "Error loading QML file.\n23: module \"org.kde.marble.private.plasma\" is not
installed\n"
Locked at 1585529631
UdevQt: unable to create udev monitor connection
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/WallpaperFader.qml:138:13:
QML PropertyChanges: Cannot assign to non-existent property "opacity"
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/WallpaperFader.qml:139:17:
Unable to assign [undefined] to QObject*
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/lockscreen/LockScreenUi.qml:158:
ReferenceError: wallpaper is not defined
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/SessionManagementScreen.qml:64:5:
Unable to assign [undefined] to int
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/ActionButton.qml:33:5:
Unable to assign [undefined] to int
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/KeyboardLayoutButton.qml:29:5:
Unable to assign [undefined] to int
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/Battery.qml:48:9:
Unable to assign [undefined] to double
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/UserDelegate.qml:41:5:
Unable to assign [undefined] to int
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/WallpaperFader.qml:120:17:
Unable to assign [undefined] to QObject*
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/WallpaperFader.qml:119:13:
QML PropertyChanges: Cannot assign to non-existent property "opacity"


Works OK. But, as I said, issue is intermittent...

*Do you know if Feren OS has a customised lock screen compared to default
Plasma?*
Not sure, but when invoked, these services run:
kscreenlocker_greet
kcheckpass

Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.