Am 2017-03-05 09:32, schrieb René J. V. Bertin:
Kai Uwe Broulik wrote:
Turn the screen off. Problem solved.
Sure, that's why I use computers, to have to remember myself to do
everything by
hand... I'd suggest to remove all current hooks into power management
too if
that's the prevalent mind
> to have to remember myself to do everything by hand...
It does that automatically by default...
Kai Uwe Broulik wrote:
> Turn the screen off. Problem solved.
Sure, that's why I use computers, to have to remember myself to do everything
by
hand... I'd suggest to remove all current hooks into power management too if
that's the prevalent mindset - just turn the computer off. Problem solved.
Am 2017-03-04 16:34, schrieb Kai Uwe Broulik:
I know, but the checkbox next to "ask password after" is gone so you
can no longer disable locking while keeping a screensaver feature.
Ah, yes, that is gone. There's no screen "saver" anymore but just a
lock screen that happens to have a fancy wall
> I know, but the checkbox next to "ask password after" is gone so you can no
> longer disable locking while keeping a screensaver feature.
Ah, yes, that is gone. There's no screen "saver" anymore but just a lock screen
that happens to have a fancy wallpaper architecture.
> As if no one would
Kai Uwe Broulik wrote:
> You can disable automatic locking in System Settings -> Workspace Behavior ->
> Lock Screen
I know, but the checkbox next to "ask password after" is gone so you can no
longer disable locking while keeping a screensaver feature. As if no one would
want to prevent scree
> Was it also decided by popular vote that locking should no longer be optional
> (I cannot find an option to turn it off)?
You can disable automatic locking in System Settings -> Workspace Behavior ->
Lock Screen
> is it possible to port that part to the KF5 kscreenlocker API
I doubt it. Th
Luca Beltrame wrote:
> Support for screensavers has been removed even in 4.x times when the new lock
> screen architecture was introduced.
? It's still there in 4.14 and not as the result of patching it back in (and
I'm
running the most recent kde-workspace code).
> That said, the screenlocker
In data venerdì 3 marzo 2017 10:59:03 CET, René J.V. Bertin ha scritto:
> @plasma-devel : Can anyone tell me if a screensaver exists for
> Plasma5 that puts up a simple, CPU-cheap clock like kclock does or if not,
Support for screensavers has been removed even in 4.x times when the new lock
scr
To come back to the original topic: I have been tinkering with other display
managers, and think now that the claim that kscreenlocker_greet uses the DM
greeter for unlocking (on Plasma4) is unsubstantiated. When I switch to
Ubuntu's LightDM I still get the same unlock dialog. I've built and ins
On Thursday March 2 2017 10:31:54 Duncan wrote:
>others will still have those one or two X-based apps they want/need to
>continue to run on a modern Linux/Wayland-based desktop a decade, even
>two, from now.
If you have picked up the clamour not so long ago when a rumour made the rounds
that r
Am 2017-03-01 15:50, schrieb Luca Beltrame:
In data mercoledì 1 marzo 2017 15:44:48 CET, René J. V. Bertin ha
scritto:
And is that loginctl command supposed to work only on systems that use
Only with systemd.
Actually no. We interact with the DBus interface and don't care who owns
the int
In data mercoledì 1 marzo 2017 15:44:48 CET, René J. V. Bertin ha scritto:
> And is that loginctl command supposed to work only on systems that use
Only with systemd. IIRC FreeBSD has a patch to make it work with ConsoleKit.
> systemd throughout or elsewhere too? `loginctl kill-session X` works
Luca Beltrame wrote:
> With the exception of "loginctl unlock-sessions" as root or "loginctl unlock-
> session" as the same user, none. It's the whole point of the screenlocker
> architecture (that is, you can't just kill it and unlock the screen).
And is that loginctl command supposed to work on
On Wednesday March 1 2017 06:32:45 Duncan wrote:
>Without kdm or similar installed, kde4/plasma4 didn't have a greeter
>available and I had to be careful not to lock the screen, etc, because
>there was no way to unlock it as I had no greeter.
So you are saying that despite what the resident exp
In data martedì 28 febbraio 2017 23:16:42 CET, René J.V. Bertin ha scritto:
> 3) suppose something like this happens on a Plasma5 desktop, what backdoors
> are there to unlock the session without killing it, from a virtual console?
With the exception of "loginctl unlock-sessions" as root or "logi
Please allow me a few follow-up questions
Given that apparently the KDE4 screensaving/locking mechanism is too old to
work correctly with whatever component is now too new:
1) can I prevent locking entirely, including at suspend/wake? I thought I'd
seen an option that controls this in systemset
Am 2017-02-28 19:47, schrieb René J.V. Bertin:
On Tuesday February 28 2017 18:35:59 Martin Gräßlin wrote:
Erm you count translations as commits? If not then trust the
maintainer
Please, I can read:
commit 46f1055ffdcd2e068296576a7824012f42e9b9a8
Author: Wolfgang Bauer
Date: Tue Aug 4 19:5
On Tuesday February 28 2017 18:35:59 Martin Gräßlin wrote:
> Erm you count translations as commits? If not then trust the maintainer
Please, I can read:
> commit 46f1055ffdcd2e068296576a7824012f42e9b9a8
> Author: Wolfgang Bauer
> Date: Tue Aug 4 19:51:05 2015 +0200
>
> Fix input focus fo
Am 2017-02-28 18:08, schrieb René J.V. Bertin:
On Tuesday February 28 2017 16:48:25 Martin Gräßlin wrote:
As you should be aware of: kde4 has been unmaintained for years and is
EOL.
Yeah, I know that KDE no longer maintains most of KDE4.
why in the name of Konqui are you asking questions ab
In data martedì 28 febbraio 2017 18:08:40 CET, René J.V. Bertin ha scritto:
> Yeah, I know that KDE no longer maintains most of KDE4. Fortunately some
> distributions have a slightly different take on concepts like continuity
I would like if you stopped doing such blanket statements. Plasma 4 *wa
On Tuesday February 28 2017 16:48:25 Martin Gräßlin wrote:
>As you should be aware of: kde4 has been unmaintained for years and is
>EOL.
Yeah, I know that KDE no longer maintains most of KDE4. Fortunately some
distributions have a slightly different take on concepts like continuity and
long-te
Am 2017-02-28 10:20, schrieb René J.V. Bertin:
What component(s) might be involved? Who's responsible for the
screensaver and screen/session locking? Is there a way to get an
on-screen keyboard in the session unlock screen?
As you should be aware of: kde4 has been unmaintained for years and is
Hi,
Sorry for cross-posting, I'm hoping it'll increase my chances of reaching
someone who has an answer to the following.
After upgrading my hardware to an N3150-based notebook, my KUbuntu 14.04
install has developed an annoying quirk. From time to time, the screensaver
fails to start (= I get
24 matches
Mail list logo
