How do you change the second password (user password) on the Tuxedo GEN1 17-inch notebook running QubesOS 4.2.4 when the keyboard sometimes works and sometimes doesn’t? I was told that the keyboard was defective, but then it worked again for 1.5 weeks (why should I buy a new keyboard and install it if nothing will change in a few days? I suspect it must be a QubesCode error. But unfortunately, if I want to look into it further, QubesOS leaves me on my own. Especially when I need help changing the password, because how quickly can you make a mistake and then later be unable to access your files, or enter the wrong command in the Dom0 terminal. Which later turns out to be negative.
1 Like
Use passwd command in dom0 terminal to change the user password.
3 Likes
If you were told that the keyboard was defective, that is a call to action to take it seriously, especially if the adversaries of your threat model are capable of keyboard-based attacks.
Use the passwd command in the Dom0 terminal to change the user password.
- Yes, I would very much like to use the passwd command in the Dom0 terminal. However, the QubesOS operating system sometimes stores the appropriate software code in the notebook and sometimes does not.
The keyboard worked for 1.5 weeks last week, and then suddenly several keys stopped working the next day.
==================
If you were told that the keyboard was defective, that’s a reason to
-
Thank you—yes, that’s how I see it too.
-
But you have to look at a defective keyboard from two different angles.
=> A defective keyboard is mechanically defective, but this keyboard was not.
- To my knowledge, there is no point in replacing this keyboard if it would have to be replaced again in two days because the Qubes OS software code is missing again.
=> A defective keyboard is defective in terms of software code.
- I suspect that the QubesOS programmers removed or commented out/deactivated the code that was previously stored.
Take the matter seriously.
- Yes, I would do that, but such an error must be clear and unambiguous.
Especially if the opponents of your threat model are capable of keyboard-based attacks.
- I don’t have the relevant knowledge about the Tuxedo notebook, so I can’t comment on that.
1 Like
Is it this model?
Who informed you of this, and what evidence did he/she/it have to support it? Is it just a guess? Have any tests been done?
Why? Is it because it’s intermittent? Well … there are several factors, that could cause this:
- Loose data cable connection
- fluctuating temperatures in the housing
- electrical contact impaired by humidity
- etc., etc., etc.
But first things first: I don’t get what you mean exactly by “second password (user password)”. Please describe a bit more in detail like the following:
My laptop keyboard works fine when I enter the BIOS/UEFI settings or the LUKS passphrase during startup. However, it sometimes stops working once X11 is up when I try to log in to the graphical user interface. I have no idea how to access the console or inspect some logs. I have already tried booting a Linux distribution from a USB stick (something like knoppix), and everything is fine with that setup. Therefore, I’m inclined to say the cause must be some recent changes to QubesOS. What is the best way to address this issue?
1 Like
This is my notebook:
TUXEDO Gemini 17 - Gen1
Fast graphics workstation in a sleek business design
17.3-inch display with 2 panel options:
- WQHD (2560 x 1440 pixels) | 165 Hz | G-SYNC | Advanced Optimus
- 4K UHD (3840 x 2160 pixels) | 60 Hz | 100% Adobe RGB | 400 cd/m2
Simple and robust business case
High-end CPUs from Intel: Core i7-12700H or i9-12900H (14 cores each | 20 threads)
Up to NVIDIA GeForce RTX 3080 Ti (up to 135 watts)
3x DisplayPort 1.4 (2x USB-C, 1x Mini DP) (VR headset ready)
Single-key illuminated keyboard with TUX super key
80 Wh for up to 7 hours of runtime
Up to 64 GB DDR4-3200 MHz RAM
2x M.2 SSD PCIe / NVMe
Thunderbolt 4, Mini DisplayPort, 2x USB-C, 1x HDMI 2.1 and much more.
TPM 2.0 (Windows 11 ready)
Who informed you about this and
- Telegram group - QubesOS users German-speaking
What evidence do they have?
- Statement
Is this just a guess?
- Yes, it could be
Have tests been carried out?
-
No, the keyboard started working again about a week later.
-
Now several keys are not working again.
Why?
Is it because it only happens occasionally?
- I don’t know the reason either.
Well… there are several factors that could cause this:
Loose data cable connection
- No
Fluctuating temperatures in the housing
- No
Electrical contact impaired by moisture
- No
But first things first: I don’t quite understand what you mean by “second password (user password).”
- I am supposed to change the user password in order to remove the allegedly defective key.
Please describe it in more detail, for example as follows:
=> I have no idea how to access the console or view logs. I have already tried booting a Linux distribution from a USB stick (such as Knoppix), and everything works fine with this setup.
- Unfortunately, I don’t know how to do this.
Therefore, I suspect that the cause must be some recent changes to QubesOS.
- I am not aware of any such changes.
What is the best way to fix this problem?
- Yes, I’m wondering that too!
1 Like
I gave you an example of how to present your problem. There’s no need to answer that. Anyway…
So, the diagnosis is all guesswork. Nobody tested your keyboard hardware and the diagnosis was given via internet/social media/telegram.
What do you mean by
I am supposed to change the user password in order to remove the allegedly defective key
Who told you that? What key?
If I were you, I wouldn’t mess with things too much. Indeed, there is a risk of locking yourself out if your keyboard is defective or not functioning properly. I would try to find the root cause in a “non destructive” and rather safe way. Consider this:
- If it’s a hardware failure, it should fail with any software or operating system. Get a USB thumb drive and install a different operating system on that USB key, such as Tails. Boot from that flash drive and test your keyboard for a few days without tampering with your QubesOS installation. (Tails runs completely from the USB flash drive.)
- If you currently do have a functioning keyboard, you could log into QubesOS and post the output of the following commands:
In the dom0 terminal:
sudo dmesg | grep keyboard
This command outputs the kernel ring buffer log and pipes it to a text filter that reduces the content to keyboard-related information, hopefully.
In the sys-usb terminal:
lsusb -v
This command lists the USB attached devices.
Both commands don’t alter the system. (Please always verify this by searching for alternative sources that describe those commands, if you don’t know them.)
p.s.: Do you have backups of your data?
2 Likes
Was meinst du mit
Ich soll das Benutzerpasswort ändern,
- So das ich wieder ohne einen Fehler mein Benutzerpasswort eingeben kann.
um den angeblich defekten Schlüssel zu entfernen
Wer hat dir das gesagt?
- Telegram: QubesOS Benutzer Deutschsprachig
Welcher Schlüssel?
- Defekte Buchstaben / defekte Zeichen die sich angeblich in der Tastatur befinden zu ersetzen mit nur gute Buchstaben und gute Zahlen.
What do you mean by
I should change the user password,
- So that I can enter my user password again without an error.
to remove the allegedly defective key
Who told you that?
- Telegram: QubesOS German-speaking users
Which key?
- Replace defective letters/characters that are allegedly on the keyboard with only good letters and good numbers.
1 Like
Why would/should anyone with a broken keyboard change their user password? How does that “fix” the keyboard?
On the contrary. It poses a risk because you cannot be sure that the machine is correctly “reading” what you enter.
Concerning the root cause(s): See above.
1 Like
In which folder can you find this created
sudo dmesg | grep keyboard
file?
1 Like
That’s exactly how I see it too!
They banned me from the German Telegram group because the whole thing was very unclear to me and I asked about it.
1 Like
There is no folder. It is a terminal command. But please wait for now and please don’t misunderstand. I’m just trying to understand you and your problem, and I’m asking for your help so that we can help you.
- Why do you use QubesOS, and for what purpose?
- Where did you learn about it?
- When did you start to use it?
- Do you have experience with Unix-like operating systems? (Please elaborate a bit on this.)
It will be helpful to know that first. From a security perspective in particular, it makes no sense to offer someone solutions they don’t understand for problems we don’t understand.
1 Like
There is no folder.
It is a terminal command.
- Yes, I am aware of that.
- I just wanted to know where I can see the end result.
But please wait and don’t get me wrong.
- No, I don’t get you wrong.
- It’s better to clarify things like this beforehand.
I’m just trying to understand you and your problem and asking for your help so that we can help you.
Why do you use QubesOS and for what purpose?
- I have to create very important documents, which is why I use this operating system.
Where did you hear about it?
- I learned about it over 10 years ago.
When did you start using it?
- About 2 years ago.
Do you have experience with Unix-like operating systems?
(Please explain this a little.)
-
Yes, I’ve learned a little bit about Linux here and there.
-
I’ve been working with computers since 1986, DOS, Windows, Atari, MAC, Linux, QubesOS.
It’s helpful to know that first.
Especially from a security perspective, it doesn’t make sense to
offer someone solutions
they don’t understand
for problems
we don’t understand.
- Yes, I understand that.
If I get stuck, I’ll just have to buy a new SSD M2 4TB hard drive and then install the new QubesOS operating system 4.3 on it. I also had to start with a trial version back then, because the stable QubesOS version didn’t fit on my notebook. Even though it was and is a Linux notebook.
==================
Es gibt keinen Ordner.
Es handelt sich um einen Terminalbefehl.
- Ja, das ist mir bekannt.
- Ich wollte nur wissen, wo ich das Endergebnis sehen kann.
Aber bitte warten Sie noch und verstehen Sie mich bitte nicht falsch.
- Nein, ich verstehe Sie nicht falsch.
- Lieber sowas vorher abklären, ist besser.
Ich versuche nur, Sie und Ihr Problem zu verstehen und bitte Sie um Ihre Hilfe, damit wir Ihnen helfen können.
Warum verwenden Sie QubesOS und zu welchem Zweck?
- Ich habe sehr wichtige Domumente zu erstellen, darum verwende ich dieses Betriebssystem.
Wo haben Sie davon erfahren?
- Davon habe ich schon gut über 10 Jahren davon erfahren, das es sowas gibt.
Wann haben Sie angefangen, es zu verwenden?
- Vor ca. 2 Jahren
Haben Sie Erfahrung mit Unix-ähnlichen Betriebssystemen?
(Bitte erläutern Sie dies etwas.)
-
Ja, immer mal was zwischen durch habe ich mal mit Linux etwas dazugelernt.
-
Seit 1986 beschäfte ich mit der EDV, DOS, Windows, Atari, MAC, Linux, QubesOS
Es ist hilfreich, das zunächst einmal zu wissen.
Gerade aus Sicherheitssicht macht es keinen Sinn,
jemandem Lösungen anzubieten,
die er nicht versteht,
für Probleme,
die wir nicht verstehen.
- Ja, das verstehe ich.
Wenn ich nicht weiterkomme, muss ich mir halt eine neue SSD M2 4TB Festplatte kaufen und dann darauf das neue QubesOS Betriebssystem 4.3 installieren. Anfangen musste ich damals auch mit einer Testversion, da die Stabile QubesOS Version nicht auf mein Notebook gepasst hat. Obwohl es ein Linux Notebook war und ist.
1 Like
Alas… all this (new SSD, new installation) won’t repair your keyboard if it’s (physically) broken. I’d rather call tuxedo on that.
Anyway, if you know it’s a terminal command, please post the output shown in the dom0 terminal window.
- markup text with mouse → terminal menu → edit → copy
- Go to the clipboard icon → copy
dom0clipboard - switch to your browsers appVM → ctrl+shift+v → ctrl+v
The dom0 text should be copied over.
Frrom sys-usb it’s the usual procedure.
(And please, if you don’t mind, use the proper format / styling tags for posting the output(s). It’s hard to read otherwise. And please spare the German content for discussions in the German section “In your language”.)
1 Like
sudo dmesg | grep keyboard
-
Yes, as I said, unfortunately no result is displayed in the Dom0 terminal for me.
-
That’s why I asked you earlier where I can see or find the result.
1 Like
And sys-usb? (That’s why I recommended to do both, since I don’t know that laptop model and it’s internals.)
1 Like
user@sys-usb:~$ sudo dmesg | grep keyboard
[ 0.488330] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
user@sys-usb:~$
1 Like
I:2030966
E:ID_INPUT=1
E:ID_INPUT_KEY=1
E:ID_INPUT_KEYBOARD=1
E:ID_BUS=i8042
E:ID_SERIAL=noserial
E:ID_PATH=platform-i8042-serio-0
E:ID_PATH_TAG=platform-i8042-serio-0
E:ID_FOR_SEAT=input-platform-i8042-serio-0
G:seat
Q:seat
V:1
1 Like
In sys-usb
lsusb
and the ouput here, please.
1 Like
user@sys-usb:~$ lsusb
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 003: ID 5986:214c Bison Electronics Inc. BisonCam,NB Pro
Bus 004 Device 002: ID 048d:8910 Integrated Technology Express, Inc. ITE Device(829x)
Bus 004 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
user@sys-usb:~$
1 Like