[systemsettings] [Bug 483396] System Settings crashes when "Appearance" clicked.
https://bugs.kde.org/show_bug.cgi?id=483396 --- Comment #4 from John Bennett --- Uninstalled! All working. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483396] System Settings crashes when "Appearance" clicked.
https://bugs.kde.org/show_bug.cgi?id=483396 John Bennett changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DOWNSTREAM |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483396] System Settings crashes when "Appearance" clicked.
https://bugs.kde.org/show_bug.cgi?id=483396 --- Comment #2 from John Bennett --- As far as I am aware, I have never selected a "Deepin Style"?? This is on 2x separate machines, certainly haven't selected "Deepin Style" on 2 machines?? Is this the default style? (Opensuse Tumbleweed...) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483396] New: System Settings crashes when "Appearance" clicked.
https://bugs.kde.org/show_bug.cgi?id=483396 Bug ID: 483396 Summary: System Settings crashes when "Appearance" clicked. Classification: Applications Product: systemsettings Version: 5.27.10 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hornets...@gmail.com Target Milestone: --- Application: systemsettings (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.7-1-default x86_64 Windowing System: Wayland Distribution: openSUSE Tumbleweed DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: As above. Crashes on clicking System Settings>Appearance. Has happened to me on 2x totallydifferent/unconnected devices. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f7c856657ee in ?? () from /usr/lib64/qt5/plugins/org.kde.kdecoration2/deepin_chameleon.so #5 0x7f7c8566870f in ?? () from /usr/lib64/qt5/plugins/org.kde.kdecoration2/deepin_chameleon.so #6 0x7f7c92954d56 in ?? () from /usr/lib64/qt5/qml/org/kde/kwin/private/kdecoration/libkdecorationprivatedeclarative.so #7 0x7f7cc3111b33 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib64/libQt5Qml.so.5 #8 0x7f7cc30a748a in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from /lib64/libQt5Qml.so.5 #9 0x7f7cc30a7f5d in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /lib64/libQt5Qml.so.5 #10 0x7f7cc222b23f in ?? () from /lib64/libQt5QmlModels.so.5 #11 0x7f7cc3748804 in ?? () from /lib64/libQt5Quick.so.5 #12 0x7f7cc373b0dd in ?? () from /lib64/libQt5Quick.so.5 #13 0x7f7cc37497db in ?? () from /lib64/libQt5Quick.so.5 #14 0x7f7cc374c899 in ?? () from /lib64/libQt5Quick.so.5 #15 0x7f7cc374cbca in QQuickItemView::modelUpdated(QQmlChangeSet const&, bool) () from /lib64/libQt5Quick.so.5 #16 0x7f7cc5525b83 in ?? () from /lib64/libQt5Core.so.5 #17 0x7f7cc21fe6c6 in QQmlInstanceModel::modelUpdated(QQmlChangeSet const&, bool) () from /lib64/libQt5QmlModels.so.5 #18 0x7f7cc221ed48 in ?? () from /lib64/libQt5QmlModels.so.5 #19 0x7f7cc2225bfa in ?? () from /lib64/libQt5QmlModels.so.5 #20 0x7f7cc2226018 in ?? () from /lib64/libQt5QmlModels.so.5 #21 0x7f7cc2230a88 in QQmlDelegateModel::_q_modelReset() () from /lib64/libQt5QmlModels.so.5 #22 0x7f7cc2231643 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libQt5QmlModels.so.5 #23 0x7f7cc5525ad4 in ?? () from /lib64/libQt5Core.so.5 #24 0x7f7cc5486b5d in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () from /lib64/libQt5Core.so.5 #25 0x7f7cc54c0676 in ?? () from /lib64/libQt5Core.so.5 #26 0x7f7cc5525b83 in ?? () from /lib64/libQt5Core.so.5 #27 0x7f7cc5486b5d in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () from /lib64/libQt5Core.so.5 #28 0x7f7c929bced1 in ?? () from /usr/lib64/qt5/plugins/kcms/deepin-kcm_kwindecoration.so #29 0x7f7cc55196f0 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #30 0x7f7cc61a51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #31 0x7f7cc54ed938 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #32 0x7f7cc54f0f31 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #33 0x7f7cc5547063 in ?? () from /lib64/libQt5Core.so.5 #34 0x7f7cc3d13f30 in ?? () from /lib64/libglib-2.0.so.0 #35 0x7f7cc3d15b58 in ?? () from /lib64/libglib-2.0.so.0 #36 0x7f7cc3d1620c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #37 0x7f7cc5546876 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #38 0x7f7cc54ec3cb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #39 0x7f7cc54f4860 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #40 0x55da9eb4605c in ?? () #41 0x7f7cc4a2a1f0 in __libc_start_call_main () from /lib64/libc.so.6 #42 0x7f7cc4a2a2b9 in __libc_start_main_impl () from /lib64/libc.so.6 #43 0x55da9eb469f5 in ?? () [Inferior 1 (process 2467) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 --- Comment #44 from John Bennett --- Whoops... Sort of relevant, just after a workaround until it's fixed... ;-) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 John Bennett changed: What|Removed |Added CC||hornets...@gmail.com --- Comment #42 from John Bennett --- Trying to change my Screenshot app in 5.27.9/Tumbleweed/Wayland. Can somebody please explain how to do this? No, I am NOT a developer, just a mere user... Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #44 from John Bennett --- (In reply to John Bennett from comment #43) > Yep, and another fresh install later > Works fine in Wayland. > Doesn't work on initial install to X11, but works (generally) on a > logout/login after... That should be "Doesn't work on initial boot to X11, ." Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting
https://bugs.kde.org/show_bug.cgi?id=440350 John Bennett changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #43 from John Bennett --- Yep, and another fresh install later Works fine in Wayland. Doesn't work on initial install to X11, but works (generally) on a logout/login after... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #42 from John Bennett --- (In reply to John Bennett from comment #41) > Complete fresh install of Tumbleweed > (openSUSE-Tumbleweed-DVD-x86_64-Snapshot20221209-Media.iso), no screenlock > enabled. > > Add the: > [Daemon] > Timeout=1 > > to the file, logout/in, working so far. Also (noticed this previously, as well), often (nearly always), after starting the computer, screenlock doesn't work, but after logging out/in, it does..? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #41 from John Bennett --- Complete fresh install of Tumbleweed (openSUSE-Tumbleweed-DVD-x86_64-Snapshot20221209-Media.iso), no screenlock enabled. Add the: [Daemon] Timeout=1 to the file, logout/in, working so far. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically due to something somewhere enforcing "never lock" as the default setting
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #40 from John Bennett --- Beginning to wonder what is going on here... On occasions (don't believe ALL the time), turn the computer on, no screenlock, log out/in, screenlock works. Files have not been changed, all looks good... Beginning to think I will do a full/clean reinstall... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #36 from John Bennett --- Back after being away. Don't recall playing with anything before going away, but on return, screen locking again not working. On checking the ~/.config/kscreenlockerrc file, contains: [$Version] update_info=kscreenlocker.upd:0.1-autolock [Daemon] LockGrace=10 * So, correcting things again, all is working, and, yes, clicking 'Defaults' does again break it... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #35 from John Bennett --- Sorry, away for the next 2 weeks. Will check when back home -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #33 from John Bennett --- Created attachment 153658 --> https://bugs.kde.org/attachment.cgi?id=153658=edit Settings>Screenlocking when working Pretty much the same... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically
https://bugs.kde.org/show_bug.cgi?id=440350 John Bennett changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #31 from John Bennett --- Fixed!!? How easy was that. If only I had known what a 'standard' config file looked like... But, asks the question, why did it break in the first place. Beleive it happened when I did a "fresh" install of Tumbleweed..? Anyway, am wrapped now that it's working. Thanks a heap, Nate. Will mark as resolved. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #29 from John Bennett --- Created attachment 153607 --> https://bugs.kde.org/attachment.cgi?id=153607=edit Screenshot of Setting>Screenlocking -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #28 from John Bennett --- Created attachment 153606 --> https://bugs.kde.org/attachment.cgi?id=153606=edit /etc/xdg/kscreenlockerrc -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #26 from John Bennett --- Created attachment 153580 --> https://bugs.kde.org/attachment.cgi?id=153580=edit kscreenlockerrc file -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically
https://bugs.kde.org/show_bug.cgi?id=440350 John Bennett changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #24 from John Bennett --- Now running Tumbleweed 20221029/KDE Plasma 5.26.2/Qt 5.15.6/Kernel 6.0.5-1-default/X11. Still having the issue. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screen never locks automatically
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #22 from John Bennett --- OK, will 'fess up here and say I am not completely convinced myself about the cause of this... and not sure how/if this could affect it at all, but: Over the last couple of days, after having completely disconnected my Thunderbird profile (removed config, and created new profile, copying old local mail folders to new profile, have changed from POP to IMAP), for a day or so, both screenlock + power save seemed to work, but after since not having changed anything, is now not working again... Thought I would mention this. Thunderbird 102.2.2 (64bit) Tumbleweed 20220916 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #20 from John Bennett --- No, standard Intel graphics. On Sat, 17 Sept 2022, 04:54 Nate Graham, wrote: > https://bugs.kde.org/show_bug.cgi?id=440350 > > --- Comment #19 from Nate Graham --- > Do you have an NVIDIA GPU, by any chance? > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #18 from John Bennett --- (In reply to Nate Graham from comment #17) > Apparently no one else is seeing it. > > Can you manually lock the screen with Meta+L? Yep, works fine. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #16 from John Bennett --- And this is STILL happening -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #15 from John Bennett --- Seriously? Is no-one else seeing this? Screensaver/power control not working at all, after login. If I leave on the login screen, works OK. Have installed MANY other distros, and never had an issue. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #14 from John Bennett --- New install of Tumbleweed (20220106 + KDE Plasma V5.23.4) on Dell Optiplex 9020 1TB ssd boot drive/16gb RAM Hardware. Still VERY intermittent - mostly (95%) not working. Have tried different settings in both Screensaver and Power. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357288] Setting "Screen Energy Saving" in "Energy Saving" config has no effect
https://bugs.kde.org/show_bug.cgi?id=357288 John Bennett changed: What|Removed |Added CC||hornets...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #13 from John Bennett --- Have done a total reinstall of Tumbleweed (currently 20220106; KDE Plasma V5.23.4), with new user, and still intermittent at best. Mostly not working. Hardware is Dell Optiplex 9020, with 1TB SSD, 16GB RAM. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448104] New: System settings crashes on opening Power menu
https://bugs.kde.org/show_bug.cgi?id=448104
Bug ID: 448104
Summary: System settings crashes on opening Power menu
Product: systemsettings
Version: 5.23.4
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: hornets...@gmail.com
Target Milestone: ---
Application: systemsettings5 (5.23.4)
Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.12-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Attempting to open Settings>System Settings>Power Management menu.
Immediately faults with "System Settings closed unexpectedly" message.
The crash can be reproduced every time.
-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fb212cfc506 in QComboBox::clear (this=0x556f74ade1b0) at
widgets/qcombobox.cpp:3049
#7 0x7fb1ff6f3714 in operator() (__closure=0x556f787011d0,
watcher=) at
/usr/src/debug/powerdevil5-5.23.4-1.2.x86_64/daemon/actions/bundled/powerprofileconfig.cpp:83
#8 0x7fb211f76393 in QtPrivate::QSlotObjectBase::call (a=0x7ffeb0de9440,
r=0x7fb200011460, this=0x556f787011c0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9 doActivate (sender=0x556f783e5750, signal_index=3,
argv=0x7ffeb0de9440) at kernel/qobject.cpp:3886
#10 0x7fb211f6f85f in QMetaObject::activate (sender=,
m=m@entry=0x7fb210aa25e0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeb0de9440)
at kernel/qobject.cpp:3946
#11 0x7fb210a8307f in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158
#12 0x7fb211f6c33e in QObject::event (this=0x556f783e5750,
e=0x556f79d12af0) at kernel/qobject.cpp:1314
#13 0x7fb212bf1a7f in QApplicationPrivate::notify_helper (this=, receiver=0x556f783e5750, e=0x556f79d12af0) at
kernel/qapplication.cpp:3632
#14 0x7fb211f3fd2a in QCoreApplication::notifyInternal2
(receiver=0x556f783e5750, event=0x556f79d12af0) at
kernel/qcoreapplication.cpp:1064
#15 0x7fb211f42d77 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x556f74830480) at
kernel/qcoreapplication.cpp:1821
#16 0x7fb211f97b83 in postEventSourceDispatch (s=s@entry=0x556f749336c0) at
kernel/qeventdispatcher_glib.cpp:277
#17 0x7fb20fa92d9f in g_main_dispatch (context=0x7fb208005000) at
../glib/gmain.c:3381
#18 g_main_context_dispatch (context=0x7fb208005000) at ../glib/gmain.c:4099
#19 0x7fb20fa93128 in g_main_context_iterate
(context=context@entry=0x7fb208005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#20 0x7fb20fa931df in g_main_context_iteration (context=0x7fb208005000,
may_block=1) at ../glib/gmain.c:4240
#21 0x7fb211f97204 in QEventDispatcherGlib::processEvents
(this=0x556f7493cf90, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x7fb211f3e72b in QEventLoop::exec (this=this@entry=0x7ffeb0de9830,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#23 0x7fb211f46a10 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x7fb21249319c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#25 0x7fb212bf19f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#26 0x556f73cb610b in main (argc=, argv=) at
/usr/src/debug/systemsettings5-5.23.4-1.2.x86_64/app/main.cpp:208
[Inferior 1 (process 26586) detached]
Possible duplicates by query: bug 447910, bug 447904, bug 447759, bug 447676,
bug 447282.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #12 from John Bennett --- Seems to have gone back to 'not working' again... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #10 from John Bennett --- Have there been any updates recently? Appears to be working 'mostly', at the moment, even the power...? Will do some checking. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 John Bennett changed: What|Removed |Added Attachment #140402|0 |1 is obsolete|| --- Comment #7 from John Bennett --- Created attachment 140404 --> https://bugs.kde.org/attachment.cgi?id=140404=edit Battery & Brightness #1 and if I select the Tools icon, get the previous shot...? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #5 from John Bennett --- Have attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 John Bennett changed: What|Removed |Added CC||hornets...@gmail.com --- Comment #4 from John Bennett --- Created attachment 140402 --> https://bugs.kde.org/attachment.cgi?id=140402=edit Battery & Brightness -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350
--- Comment #2 from John Bennett ---
Have checked that applet, but can't find specifically where it would tell me
re: inhibiting screen locking.
Nothing obvious
("Do not use special settings" selected.)
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 440350] New: Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 Bug ID: 440350 Summary: Screensaver never runs after logon. Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: library Assignee: plasma-b...@kde.org Reporter: hornets...@gmail.com CC: bhus...@gmail.com Target Milestone: --- Created attachment 140366 --> https://bugs.kde.org/attachment.cgi?id=140366=edit Screen lock settings #1 SUMMARY kscreenlocker Version 5.18.5 Have recently installed Opensuse Leap 15.3, and having problems trying to get the screen to lock/power off. If I don't log on, screen seems to power off ok, but after logging on, never seems to lock/power off automatically, even when no 'extra' programs are running (ie even just the standard system components.) Can Manually lock (Meta+L), but still doesn't go to power off. STEPS TO REPRODUCE 1. Boot system and logon 2. Wait for screensaver to kick in 3. Never does OBSERVED RESULT Screensaver NEVER works. EXPECTED RESULT Screensaver works. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.76.0 ?? Qt Version: 5.12.7 ?? ADDITIONAL INFORMATION Have tried various settings under: Settings>Workspace Behaviour>Screen Locking + Settings>Power Management -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 John Bennett changed: What|Removed |Added CC||hornets...@gmail.com --- Comment #167 from John Bennett --- Also irked at this issue! Trying to set default language to en_au, and use 24hr time -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 419355] Unable to log back in after screensaver
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
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
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
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=edit LockedUp -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 419355] Unable to log back in after screensaver
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
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
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
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
[kscreenlocker] [Bug 419355] Unable to log back in after screensaver
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.
[kscreenlocker] [Bug 419355] Unable to log back in after screensaver
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] New: Unable to log back in after screensaver
https://bugs.kde.org/show_bug.cgi?id=419355 Bug ID: 419355 Summary: Unable to log back in after screensaver Product: kscreenlocker Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcheckpass Assignee: plasma-b...@kde.org Reporter: hornets...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Using Feren OS, Plasma Desktop 4:5.18.3-0xneon + bionic+ build77 After logging in, when screensaver activates, and trying to log back in, intermittently it locks up. ie screen is locked, I type in the password STEPS TO REPRODUCE 1. Screensaver activates after login 2. Type in password, and nothing/very little happens. Usually the lock screen will reappear, but can't even see the password box - no response to any keys. 3. Ctrl-Backspace a couple of times, allows me to log back in, but to a totally new session. OBSERVED RESULT Screen locks up EXPECTED RESULT Should just log me back in SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Feren OS - Plasma Desktop 4:5.18.3-0xneon+18.04+bionic+build77 (available in About System) KDE Plasma Version: Latest Update KDE Frameworks Version: Latest Update Qt Version: Latest Update ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
