[PATCH] weston-launch: be more descriptive with output messages

Kristian Høgsberg krh at bitplanet.net
Tue Apr 17 11:08:41 PDT 2012

On Tue, Apr 17, 2012 at 1:54 PM, Pekka Paalanen <ppaalanen at gmail.com> wrote:
> On Tue, 17 Apr 2012 20:10:11 +0300
> Tiago Vignatti <tiago.vignatti at intel.com> wrote:
>> Specially the "either" word there is essential, so users don't
>> confuse thinking that both steps are needed.
> Good!
>> Signed-off-by: Tiago Vignatti <tiago.vignatti at intel.com>
>> ---
>> I started to implement udev based session support for
>> weston-launcher, after added myself to 'weston-launch' group and
>> mistakenly forgot to re-ran bash. Yes, really!
>> There's also the fact that if I'm using the non-systemd method,
>> then I'd explicit have to set input fd permissions. I've had to
>> reboot my system twice, thinking that Weston screwed it, while
>> actually it was successfully up, with the desktop shell
>> background showing up, and I couldn't VT switch away or do
>> anything because I didn't have input devices around. Should we
>> clarify it somewhere as well?
> Maybe. And for the future, couldn't you use a SysRq key to kill
> all processes on current tty: sysrq+k
> sysrq+e would be a bigger hammer, and sysrq+i the equivalent of a
> nuclear bomb.
> And perhaps sysrq+r would make the VT switching keys work.
> Of course all that assumes sysrq is enabled.

Yeah. On Fedora I have to edit /etc/sysctl.conf and set kernel.sysrq =
1.  And the key combination is: hold alt+sysrq then press the key.
Yes r makes vt switching work again, and v now resets back to the
console framebuffer.  That's typically all I need, then I can just vt
switch and attach gdb or kill it manually.


More information about the wayland-devel mailing list