From: Christoph Pleger <christoph.pleger@cs.uni-dortmund.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Running an application on a new VT
Date: Wed, 18 Sep 2019 17:32:55 +0200 [thread overview]
Message-ID: <e7ed4b28070ef828902ebb6bd610da9a@cs.uni-dortmund.de> (raw)
In-Reply-To: <bbfcbea3f39a4a3689f4ffedf962fbbf@cs.uni-dortmund.de>
Hello,
On 2019-09-16 13:53, Christoph Pleger wrote:
> I am using the program openvt to run another program. openvt is used
> to open a new virtual terminal and then run the given program on the
> new VT. In my case, I want to start a KDE Plasma session on the new
> VT.
>
> Unfortunately, this did not work as expected: After entering the
> command 'openvt -s -w -- dbus-run-session startplasmacompositor', the
> KDE session did not start on the new VT, but on tty1, from where I had
> entered the openvt command. Then, I tried with 'openvt -s -w --
> /bin/bash', but though this ran bash on a new virtual terminal,
> entering 'dbus-run-session startplasmacompositor' on the new VT caused
> a switch back to tty1 and again, the desktop session started there.
>
> Does anybody know why not the new VT is used for the desktop session
> and how that behaviour can be changed?
This is totally crazy: Even when I omit the -w option to openvt, so that
I can log out from tty1, then switch to the new VT and enter
'dbus-run-session startplasmacompositor' there, the KDE session starts
on tty1, though of course logging out from /dev/tty1 changed its owner
to root. So, how can a process with real UID, effective UID and saved
UID (I checked that) change the ownership of a device that was owned by
root?
Still nobody who has an idea what is going on here with the virtual
terminals?
Regards
Christoph
prev parent reply other threads:[~2019-09-18 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 11:53 Christoph Pleger
2019-09-18 15:32 ` Christoph Pleger [this message]
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=e7ed4b28070ef828902ebb6bd610da9a@cs.uni-dortmund.de \
--to=christoph.pleger@cs.uni-dortmund.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®