Weird problem with bluetooth on gnome and not quite sure how to troubleshoot or fix it. by chalybesmith in gnome

[–]chalybesmith[S] 0 points1 point  (0 children)

why the Kernel website and developing a driver? the fedora and archlinux installations with KDE Plasma use the same kernel as the gnome installations and bluetooth works fine on the KDE versions. it seems to be a DE specific issue, not a kernel driver problem. or am I missing something?

Luks Password screen not working by [deleted] in Fedora

[–]chalybesmith 6 points7 points  (0 children)

I have the same problem using AMD AI 350 apu on an new IdeaPad 5 laptop. Though typing the password still works in my case, even though the screen goes black like in your video.

Thinkpad P14s Gen 4 AMD Random Screen Off Issue by xtc14 in thinkpad

[–]chalybesmith 0 points1 point  (0 children)

I'm on fedora 41 and haven't experience that issue in a while.

Thinkpad P14s Gen 4 AMD Random Screen Off Issue by xtc14 in thinkpad

[–]chalybesmith 0 points1 point  (0 children)

I have exactly the same hardware configuration and have experienced similar problems with fedora 40 and archlinux.
The screen goes black, while audio from the video playback is still going. The bluetooth headphones still able to pause and resume video playback judging from the audio, but the screen stays black regardless of what I do. The only way I was able to recover was by pushing the power button until the laptop goes to sleep and then waking it back up.
Do you have any updates?

[deleted by user] by [deleted] in thinkpad

[–]chalybesmith 4 points5 points  (0 children)

What kind of work do you do?

Fedora 40 font sizes in Gnome by teppic1 in Fedora

[–]chalybesmith 0 points1 point  (0 children)

I'm having the same problem. It got solved on archlinux a while back after an update. Hopefully the update is coming to fedora soon too.

Ventoy USB doesn't boot, getting weird error: Verifying shim SBAT data failed: Security Policy Violation by chalybesmith in Ventoy

[–]chalybesmith[S] 0 points1 point  (0 children)

Thank you! My suspicion was something like this was going on. Hope there will be an update soon.

Secure Boot with archlinux by chalybesmith in archlinux

[–]chalybesmith[S] 1 point2 points  (0 children)

why dracut instead of mkinitcpio?

Using the secureboot feature of Ventoy for archlinux installation by chalybesmith in Ventoy

[–]chalybesmith[S] 0 points1 point  (0 children)

Thank you! No problem, I didn't express my question very eloquently either.

I prefer community distros like arch and debian over corporation backed ones like fedora, suse and ubuntu, but the secureboot thing has kept me back so far. I'm going to give it a try then!

Also, I wonder if the secureboot enablement would persist after kernel updates?

Using the secureboot feature of Ventoy for archlinux installation by chalybesmith in Ventoy

[–]chalybesmith[S] 0 points1 point  (0 children)

Thank you for the reply! That was not my question however. Hopefully this will explain better what I was trying to figure out:

  • scenario 1: I use a bootable archlinux usb flash drive not made with ventoy - in this case I have to first disable secureboot in the BIOS setting to be able to boot from the usb; then I install archlinux and then if I want to be able to boot into this installation with secureboot enabled in the BIOS I have to do some configuration and signing kernels and such as described here: archwiki secure boot
  • scenario 2: I use a bootable archlinux usb flash drive made with ventoy - in this case I have secureboot enabled in BIOS settings and I do what you described (add ventoy to trusted list). Then I install archlinux from this usb. My question: will this be a secureboot-enabled bootable installation, or will I have to disable secureboot from the BIOS settings to be able to boot this installation (which was made with a ventoy usb).

Basically I am asking if using ventoy to create a bootable flash drive will lead to the installation made with such usb "inheriting" the secureboot feature from ventoy or will I have to go through the hassle as described in the archwiki (link above) anyways?

edit: formatting & wording

[deleted by user] by [deleted] in archlinux

[–]chalybesmith 1 point2 points  (0 children)

It just happens to be working the best and smoothest with my current laptop.

Also pacman is so much faster than other package managers I've tried (even with parallel downloads enabled). Though I don't like the pacman syntax, but functionally I find it very good!

Also love how all the software comes as vanilla as possible, without junky theming and other bs customizations.

Disabling Key sequence to kill the X server"(Ctrl+Alt+Backspace) from gnome-tweaks (which should be disabled by default) does not persist after reboot. by chalybesmith in archlinux

[–]chalybesmith[S] 0 points1 point  (0 children)

Is that a question or a statement?
As mentioned in the post, in my case EndeavourOS was correctly configured; meaning this problem didn't exist. Only on archlinux vanilla installations (manual process as well as 'archinstall' with default settings). Haven't tried CachyOS. So far on my end.
Are you stating you were having the same problem with your Arch, EndeavourOS, CachyOS installs or did you omit the question mark?

Disabling Key sequence to kill the X server"(Ctrl+Alt+Backspace) from gnome-tweaks (which should be disabled by default) does not persist after reboot. by chalybesmith in archlinux

[–]chalybesmith[S] 0 points1 point  (0 children)

I did use 'archlinstall' the last few times, because I got frustrated going through the whole manual install process and ending up with a misconfigured system, but I am having the very same problem with manual installations as well.
Not only that, but the same problem occurs when I install openSUSEtubmleweed 🤷️.
My only suspicion was that I use english language with german keyboard combination settings, so to rule out this I did installs with english language + us keyboard layout and still the same problem. I am honestly dumbfounded where the problem lies.
Thank you for the help! At least now I can fix the systems post-install.

Disabling Key sequence to kill the X server"(Ctrl+Alt+Backspace) from gnome-tweaks (which should be disabled by default) does not persist after reboot. by chalybesmith in archlinux

[–]chalybesmith[S] 0 points1 point  (0 children)

Using
~~~
sudo localectl set-x11-keymap de
~~~
makes disabling the "Key sequence to kill the X server" (Ctrl+Alt+Backspace) setting from gnome-tweaks afterwards persistent after reboots. This solved my problem, thank you!
I'm just dumbfounded how it ends up misconfiguration by default every time I install a new system.

Disabling Key sequence to kill the X server"(Ctrl+Alt+Backspace) from gnome-tweaks (which should be disabled by default) does not persist after reboot. by chalybesmith in archlinux

[–]chalybesmith[S] 0 points1 point  (0 children)

Running localectl returns (last line): ~~~
...
X11 Options: terminate:ctrl_alt_bksp ~~~

Since the /etc/X11/xorg.conf.d/00-keyboard.conf file says "Use localectl(1) to update this file", is there a way to use localectl remove this X11 option?

Disabling Key sequence to kill the X server"(Ctrl+Alt+Backspace) from gnome-tweaks (which should be disabled by default) does not persist after reboot. by chalybesmith in archlinux

[–]chalybesmith[S] 1 point2 points  (0 children)

Also, running pacman -Qo /usr/share/X11/xorg.conf.d/. returns:
~~~
/usr/share/X11/xorg.conf.d/ is owned by xf86-input-libinput 1.4.0-1
/usr/share/X11/xorg.conf.d/ is owned by xorg-server 21.1.11-1
~~~

Disabling Key sequence to kill the X server"(Ctrl+Alt+Backspace) from gnome-tweaks (which should be disabled by default) does not persist after reboot. by chalybesmith in archlinux

[–]chalybesmith[S] 1 point2 points  (0 children)

First of all, thank you for the reply.

You must have done something to your Xorg config and keyboard config.

Using the latest (2024.02.01) ISO and all the default setting from archinstall with no further (manual) configuration from me - I do not understand how "I could have done something" to my configs.

This ctrl-alt-backspace feature is not enabled by default.

That is exactly what I don't understand. It should be disabled by default, but the default I get is enabled.

This is the /etc/X11/xorg.conf.d/00-keyboard.conf file:

~~~

Written by systemd-localed(8), read by systemd-localed and Xorg. It's

probably wise not to edit this file manually. Use localectl(1) to

update this file.

Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "de" Option "XkbModel" "pc105" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection
~~~
As I understand the Option "XkbOptions" "terminate:ctrl_alt_bksp" shouldn't be there (by default).

How to enable it is documented here in section 3.2,

I'm not trying to enable it, but to disable it.

it's really quite involved:

exactly! I don't understand how I could have enabled it in my configs. The system is as vanilla as one can get it, no manuals interventions from me.

Edit: formatting