From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Unlocking Plasma desktop in Gentoo without systemd
Date: Mon, 11 Sep 2017 22:38:19 +0100 [thread overview]
Message-ID: <27894590.kG6dEgIW6K@dell_xps> (raw)
In-Reply-To: <dfcacabc-e0ab-ed45-3b7e-6353cef9da2d@dmj.nu>
[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]
On Monday, 11 September 2017 20:27:02 BST Dan Johansson wrote:
> On 11.09.2017 21:04, Mick wrote:
> > On Monday, 11 September 2017 19:27:02 BST Jigme Datse Yli-RAsku wrote:
> >> I had a similar (if not identical problem). This solution is a
> >> "difficult" solution, the reason I experienced this (if I understand)
> >> was that I was running KDE at the same time I was updating KDE.
> >
> > No the user started a Plasma session after booting up the PC and while no
> > updates were being performed.
> >
> >> I can't
> >> remember if I simply rebooted, or if all it took was logging out, and
> >> logging back in. Even if I had rebooted, the *most* that should be
> >> required is restarting X, which if you are running XDM may require
> >> restarting XDM, or as stated, simply logging out and logging back in
> >> (but that might not be possible from KDE running in this broken mode).
> >> It should happen relatively infrequently.
> >
> > I can login and restart xdm, but I fear the user may lose some the work
> > being performed at the time. I may end up doing this, but not if there
> > is a way to recover the session. Strangely, I can't see any relevant
> > screenlock process I could stop from the console. :-(
>
> Try this:
>
> # Get Session-ID
> sesid=$(ck-list-sessions | egrep "(Session[0-9]:|x11-display = ':0')" |
> grep -B 2 "x11-display = ':0'" | grep "Session" | cut -d":" -f1)
>
> # Unlock
> sudo dbus-send --system --print-reply
> --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/${sesid}
> org.freedesktop.ConsoleKit.Session.Unlock
Thank you All, the suggestion to unlock the sessionID worked!
So, KDE is now becoming good as Gnome in becoming entwined with systemd. I
can see myself ending up in working on VTs only soon! ;-p
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-11 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 17:49 [gentoo-user] Unlocking Plasma desktop in Gentoo without systemd Mick
2017-09-11 18:18 ` Stroller
2017-09-11 19:00 ` Mick
2017-09-11 18:27 ` Jigme Datse Yli-RAsku
2017-09-11 19:04 ` Mick
2017-09-11 19:27 ` Dan Johansson
2017-09-11 21:38 ` Mick [this message]
2017-09-11 19:04 ` Daniel Frey
2017-09-12 12:13 ` [gentoo-user] " Michael Palimaka
2017-09-12 13:04 ` Mick
2017-09-13 9:07 ` J. Roeleveld
2018-02-13 3:03 ` Daniel Frey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27894590.kG6dEgIW6K@dell_xps \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox