Kubuntu SDDM kills keyboard

[Xen]

Nils Kassube schreef op 30-11-2017 7:47:
> Xen wrote:
>> I stopped SDDM using systemctl stop sddm from within KDE this time and
>> expected to be returned to a TTY as usual.
>> 
>> It took away my keyboard and I had again no way to log in to a tty and
>> restart it.
> 
> Please write bug reports, like Oli suggested in his reply to your
> Ubiquity thread.

The bug on /var has existed since ancient days, was reported, and never 
fixed.

The bug on grub has been reported by myself, someone tried to look into 
it (not sure if it was anyone from Canonical or Ubuntu) but it was never 
fixed.

Reporting bugs doesn't help, they're not gonna get fixed anyway.

Raising awareness might help.

Please quit derailing stuff you know...

I don't have time to endlessly write bug reports and then follow up on 
them and provide data while there is zero outcome.

It is just one of these scams "If you do this your life will get 
better".

Meanwhile because you write a bug report only a few people will notice 
and if those people skip it, no one will know.

The only ones who do know, are the ones who run into the same bug.

That's all that happens.

> The right place for bug reports is
> <https://bugs.launchpad.net/>, not this list.

> You could also use the
> command ubuntu-bug, in this case "ubuntu-bug sddm"

The bug is not in sddm.

I have since verified that it also happens in lightdm.

I mean I have verified that it also happens in lightdm.

It also only happens with multi-monitor; both monitors are turned off; 
normally this doesn't happen.

I cannot attest yet if it is because of the KVM switch that is the first 
connection for the DVI-I port.

So you would have me waste, you are having me waste writing a bug for 
something that would be the wrong component, and then be days into it 
before I got further ahead because I spend my time writing the bug 
instead of researching the issue.

It is just a huge waste of time to write the bug but I had to talk to 
someone about it.

It's called communication.

I know you don't like that when it is about something that doesn't work.

You could also call it community.

> I thought you had complained already that there is no ssh server
> installed by default - then why didn't you install the ssh server 
> before
> doing anything important?

Because I'm on limited bandwidth, because the chances of recovering 
keyboard are nil, because I had no data to extract this time because I'm 
on persistent storage, and because I couldn't leave the computer running 
until my job was finished while not being able to use it.

And because I would have to boot up and hook up, in reverse order, 
another computer in order to access the system only to test if the error 
was recoverable while I have other stuff to do,

and because it is a job I could restart,

and because I'm bad at my feet,

and because I don't like the other system I guess,

but also because I didn't expect it to happen again while doing nothing 
fiddly with the KVM,

and turns out it has nothing to do with that. Or at least. Might happen 
during monitor standby as well.

So there's plenty of reasons why it wouldn't have helped me much now.

What is it to you?

Does that make it less annoying that it happens?

You just want to make sure the negative stuff get shoved into some 
cabinet where no one will see it.

Even on freaking YouTube people try to silence Linux users by telling 
them to write bug reports instead of videos.

Well sorry for being such a pest.

But no one responded to the idea to tell potential users of the pitfalls 
of certain laptops either (on discuss).

Meanwhile real people get hurt.

But all you want to do is hush.

I am just relating an experience to the crowd, it helps me.

I mean I can move forward after I have spoken about it. Find renewed 
vigor to investigate the matter.

Instead of wasting my momentum in a bottomless sink called...

I mean what you suggest doesn't work, for no one.

I mean it just doesn't work.