You are not logged in.
I recently made the switch to Arch Linux and performed a fresh install. I'm facing an issue regarding sudo users and would appreciate some guidance.
In my previous experience with Linux Mint, I only needed my user password for everything. However, in Arch, I encountered a situation where my user password didn't work when trying to open specific programs, such as Grub Customizer and the firewall configuration tool. The prompt closed, and nothing happened. After some troubleshooting, I found that using sudo through the terminal allowed me to open the programs without any issues.
To address this, I used removable media to chroot into Arch and created a root password, as I hadn't done so during the initial installation. Surprisingly, using the new root password resolved the problem, and the programs opened as expected.
During the Arch installation, I followed the wiki, a YouTube tutorial, and a forum post that provided additional insights into the wiki's steps. I distinctly remember both the YouTube tutorial and the forum post advising against creating a password for the root user, suggesting that adding a user with privileges was sufficient.
Consequently, I created a user, assigned a password, added the user to the groups wheel, storage, and power (although it seems the power group might not be necessary anymore). I also modified the sudoers file to allow users in the wheel group to execute any command.
I believe I may have misunderstood this aspect of the installation process. Should I have created a password for the root user? If so, is it acceptable for the root password to be the same as the user password, similar to what I experienced in Linux Mint?
If a root password isn't necessary, how do I handle situations where programs prompt for my password?
Last edited by Nik_Rian (2023-11-12 15:47:31)
Offline
I fail to see how you can 'misinterpret' this step, unless you weren't following the installation guide at all.
Youtube guides are not supported here.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I tried to open a program and my user password didn't work
I did some tests and discovered that if I opened the program with sudo through the terminal it opened normally.
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
In particular, *how* do you try "to open a program" when your user password is rejected? What program and what asks you for that password in the first place?
I remember that both on YouTube and on the forum to read so as not to create a password for root since would add a user with privileges.
That looks like english, but is meaningless jabber.
edited the look so that all users in the wheel group could execute any command
You edited *what*??
Edit, fwwi: V nffhzr gur BC gnyxf nobhg fbzr cbyxvg vaibpngvba naq erdhverf uggcf://jvxv.nepuyvahk.bet/gvgyr/Cbyxvg#Nqzvavfgengbe_vqragvgvrf
But we shall see…
Last edited by seth (2023-11-12 15:26:03)
Offline
Sorry for the poorly structured text, the translator made a lot of mistakes and i ended up not checking because i was in a hurry to do something else
Offline
After attempting for an extended period, I found no solution.
I conducted tests by attempting to open the programs in two desktop environments, Gnome and Plasma, while using the Ly display manager. In the Gnome environment, a small window prompts me to enter my password. However, upon entering and confirming the password, the window closes, and nothing happens.
On Plasma, the experience is slightly different. When trying to open Grub Customizer, it first asks for the root password. If I provide the root password, it opens normally. However, if I cancel, it then prompts for the user password, and the same issue occurs as in Gnome - the window closes without any further action. When attempting to open Grub Customizer through the terminal, it throws the following error:
localuser:root being added to access control list
(grub-customizer:22320): Gtk-WARNING **: 17:44:21.483: cannot open display:
localuser:root being removed from access control listNevertheless, it opens normally when executed with sudo.
As for Gufw, it provides the following error code:
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gdk-CRITICAL **: 17:42:43.981: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
(gufw.py:22267): Gtk-CRITICAL **: 17:42:43.981: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
/sbin/gufw-pkexec: line 2: 22267 Segmentation fault (core dumped) python3 /usr/lib/python3.11/site-packages/gufw/gufw.py "$@"Offline
while using the Ly display manager
First of all: don't use "ly", it's incomatible w/ logind and causes degraded sessions.
In the Gnome environment, a small window prompts me to enter my password.
…
When trying to open Grub Customize
I'll just infer a polkit situation, b/c it has "polkit (optional) - for authorization" in its dependencies.
I assume the OP talks about some polkit invocation and requires https://wiki.archlinux.org/title/Polkit … identities
Offline
After disabling the Ly service and switching to the SDDM service, the programs are now working. At first I chose ly because it had been recommended on several forums.
I was attracted to Ly due to its interface, which I find more appealing compared to the somewhat unattractive appearance of SDDM.
Now, I'm wondering if there's a way to make Ly work without causing issues with my programs. I liked its interface more, and I was initially drawn to the idea of testing multiple desktop environments to find the one that best suits my workflow.
If Ly isn't a viable option, are there alternative display managers that won't disrupt the functionality of my programs? Alternatively, should I consider settling on a specific desktop environment and use a display manager like SDDM or GDM?
Offline
https://wiki.archlinux.org/title/Display_manager
I was attracted to Ly due to its interface, which I find more appealing compared to the somewhat unattractive appearance of SDDM.
There're multiple TUI DMs and just fwwi, SDDM, as most of the GUI DMs, is fully themeable. "What it looks like" is the silliest possible factor to base this decision on.
If Ly isn't a viable option
https://github.com/fairyglade/ly/issues … 1282626049
This has been an issue w/ ly pretty much ever since, idk what state upstream considers this to be in right now, but apparently (and it frequently shows up in this forum), it's not fixed.
Technically you btw. don't need any DM; you can just boot straight into a locked GUI session if this is a de-facto single-user system.
Offline