From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on sa.local.altlinux.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 17 Sep 2019 13:18:25 +0200 From: Christoph Pleger To: kbd@lists.altlinux.org Message-ID: X-Sender: christoph.pleger@cs.uni-dortmund.de User-Agent: Roundcube Webmail/1.3.9 Subject: [kbd] openvt and virtual terminals X-BeenThere: kbd@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Linux console tools development discussion List-Id: Linux console tools development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Sep 2019 11:18:30 -0000 Archived-At: List-Archive: Hello, I want to use openvt from the kbd project to open a new virtual terminal and start a wayland session there. But after entering 'openvt -s -w -- dbus-run-session startplasmacompositor' on tty1, the KDE Wayland session did not start on a new virtual terminal, but on tty1. So, I tried to start a shell session first with 'openvt -s -w -- /bin/bash' and then, on the new virtual terminal, start the Wayland session with 'dbus-run-session startplasmacompositor'. Though the first of these commands successfully opened a shell session on a new virtual terminal, the second command caused a switch back to tty1 and again, the KDE session opened there, and the new VT was only used for textual stdout/stderr. So, my question is how to give all control for the new process to the new virtual terminal and let the process started on the new VT completely forget about the virtual terminal on which its parent process was started. Regards Christoph