Difference between revisions of "User talk:Lahwaacz"

From ArchWiki
Jump to navigation Jump to search
 
(51 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 +
 
== bot checking links after move  ==
 
== bot checking links after move  ==
  
Line 184: Line 185:
 
::::Well, extracting static archives sounds much more recommended than running pip with like 7 options to make it behave. I added a talk item: [[Talk:Python package guidelines#Remove_pip_section_in_favor_of_wheels_section?]] – [[User:Flying_sheep|flying sheep]]
 
::::Well, extracting static archives sounds much more recommended than running pip with like 7 options to make it behave. I added a talk item: [[Talk:Python package guidelines#Remove_pip_section_in_favor_of_wheels_section?]] – [[User:Flying_sheep|flying sheep]]
  
== <s>re: [[Fonts]]</s> ==
+
== Google error messages and [[GnuPG]] ==
 +
 
 +
Hi, with regard to your removal of my edit of the Troubleshooting section of [[GnuPG]], I understand that it shouldn't just be TL;DR, but I'm wondering if there's a way to at least mention the error message, `sign_and_send_pubkey: signing failed: agent refused operation`, somewhere on the page, since I ran into that error with my smartcard (NitroKey) and googled the error message all across the web, before finally realizing the problem wasn't NitroKey-related at all, but [https://wiki.archlinux.org/index.php/GnuPG#Configure_pinentry_to_use_the_correct_TTY related to not pointing to the right TTY]. So I wanted to mention the error in some way on the page to enable others googling it to easier find what the problem is.
 +
 
 +
Is there a smarter way to do that? --[[User:Madpet|Madpet]] ([[User talk:Madpet|talk]]) 11:31, 22 April 2019 (UTC)
 +
 
 +
:You can't sensibly describe a catch-all error message for which there are at least a dozen of causes, most of them resulting from bad configuration. It should be clear that the whole configuration should be checked, no section is needed for that. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 11:47, 22 April 2019 (UTC)
 +
 
 +
== wpa_supplicant ==
 +
 
 +
Regarding https://wiki.archlinux.org/index.php?title=WPA_supplicant&diff=577215&oldid=577167, one person ran into this problem in March of this year and spent too much time diagnosing it:
  
"there is no reason to install *all* fonts" this is hilariously stupid, because I specifically put the note "This is useful with #List installed fonts for a particular Unicode character." I didn't contribute to wiki for a long time because the signup process was broken for long time, and now I shall return to not contributing because the admins are broken for long time. [[User:Hello71|Hello71]] ([[User talk:Hello71|talk]]) 12:45, 7 April 2019 (UTC)
+
https://bbs.archlinux.org/viewtopic.php?id=244950
  
:[[Special:Diff/570679]] - I don't get why are you responding so rude if you can make (or not) sane argument why this should not have been reverted. If you are not familiar with wikis reverts are usual process and content is added based on consensus. As for admins being broken I could not agree more, unfortunately they can't be fixed or replaced by AI yet, maybe next century but by that time ArchWiki surely will become obsolete ;) -- [[User:Svito|Svito]] ([[User talk:Svito|talk]]) 01:24, 9 April 2019 (UTC)
+
It took me a few days to find the problem.  I want to make sure the next time someone encounters it, they easily find relevant information about what the cause is. Since you've reverted my edits to both netctl and wpa_supplicant, what do you suggest?
  
::This has nothing to do with admins, but my personal dislike of how the info was presented. As for your rants about broken admins, they are in no way more useful than the OP's pleasant response - if you have a problem, find and discuss a solution instead of making rants. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 19:48, 10 April 2019 (UTC)
+
--
  
:::P.S.: I was trying to make lighthearted joke rather than sarcastic complaint (also I added diff to the front and made it look like I was responding to your revert, when actual response is to Hello71 and his comment). I'm not an admin and this is not my page, so I guess this was not my call and responsibility anyway. It just seemed ridiculous that after single revert on single edit and no apparent previous or later discussion, first reaction is "admins are broken for long time". I see no problem with admins as they are fellow humans to me, therefore can make mistake. If humans are broken and can't be fixed, then only way is to not have human admins, this leads to having AI work. I have no reason to believe that is happening as this depends on human resource that is unpredictable, so having my hopes on this would be wrong. -- [[User:Svito|Svito]] ([[User talk:Svito|talk]]) 01:18, 11 April 2019 (UTC)
+
[[User:Pooryorick|Pooryorick]] ([[User talk:Pooryorick|talk]]) 08:24, 18 July 2019 (UTC)
  
::::OK, understood. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 06:21, 11 April 2019 (UTC)
+
== <s>Regarding your edit in [[Silent boot#Retaining the vendor logo from BIOS]]</s> ==
  
== Google error messages and [[GnuPG]] ==
+
The vendor logo was already set by default to be retained and visible during bootup for me, but I wanted to manually configure it to disable the vendor logo. I searched wiki for instruction to turn it off, however it took me a few to find the correct section, even from googling the problem. My edit was to make it easier to be searched for, and to make it more clear that it was the section for disabling the vendor logo. It is quite possible that more people have it retained by default and want to disable it like I have.
  
Hi, with regard to your removal of my edit of the Troubleshooting section of [[GnuPG]], I understand that it shouldn't just be TL;DR, but I'm wondering if there's a way to at least mention the error message, `sign_and_send_pubkey: signing failed: agent refused operation`, somewhere on the page, since I ran into that error with my smartcard (NitroKey) and googled the error message all across the web, before finally realizing the problem wasn't NitroKey-related at all, but [https://wiki.archlinux.org/index.php/GnuPG#Configure_pinentry_to_use_the_correct_TTY related to not pointing to the right TTY]. So I wanted to mention the error in some way on the page to enable others googling it to easier find what the problem is.
+
[[User:Jmarmstrong1207|Jmarmstrong1207]] ([[User talk:Jmarmstrong1207|talk]]) 17:15, 1 August 2019 (UTC)
  
Is there a smarter way to do that? --[[User:Madpet|Madpet]] ([[User talk:Madpet|talk]]) 11:31, 22 April 2019 (UTC)
+
:Set by default where? The section already describes everything related, so maybe it should be just renamed to "Retaining or disabling the vendor logo from BIOS" to make it more discoverable. The subsection should be still "Disabling deferred takeover" though, because that's what it does. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 19:52, 1 August 2019 (UTC)
  
:You can't sensibly describe a catch-all error message for which there are at least a dozen of causes, most of them resulting from bad configuration. It should be clear that the whole configuration should be checked, no section is needed for that. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 11:47, 22 April 2019 (UTC)
+
My bad, it is set default as mentioned in the section, though some users may want it disabled. I agree that it should be renamed to that. [[User:Jmarmstrong1207|Jmarmstrong1207]] ([[User talk:Jmarmstrong1207|talk]]) 02:06, 11 August 2019 (UTC)
  
== NVIDIA Optimus ==
+
:OK, thanks. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 06:12, 11 August 2019 (UTC)
  
About [https://wiki.archlinux.org/index.php?title=NVIDIA_Optimus&type=revision&diff=572893&oldid=572789 your revert]: Uninstalling bumblebee is not an obvious step, only deactivating it is. Since one need to start the bumblebee service to activate it, users may think that stopping the service (and maybe a reboot) is enough to deactivate it. But it is not true since it installs a blacklist. This issue took me several hours to figure out why I got mysterious errors the second time I want to use my nvidia card to run xorg until I googled that someone with Manjaro got the same issue and solved by uninstalling bumblebee. (The first time I succeeded because I was switching so I manually modprobed necessary modules (among other adjustments). I thought it'd configured fine.) [[User:Lilydjwg|Lilydjwg]] ([[User talk:Lilydjwg|talk]]) 08:25, 11 May 2019 (UTC)
+
== F2FS and GRUB ==
  
Hi Lahwaacz, I'm still waiting for your reply. Lack of this information may disappoint users switching between several methods to see which suits them better. I think ArchWiki should provide Arch users helpful information rather than buggy instructions fail them again and again. This was the only second time but I don't want anymore so I'm trying to help here. [[User:Lilydjwg|Lilydjwg]] ([[User talk:Lilydjwg|talk]]) 16:50, 18 May 2019 (UTC)
+
Hello. :) I'm here to address a recent disagreement. I noticed a reversion of my edit regarding the F2FS filesystem, in particular regarding the configuration file to edit (with you representing /boot/grub/grub.cfg and me representing /etc/default/grub). I run F2FS on my daily driver with an encrypted root filesystem and encrypted boot on a separate partition, and have never had to touch grub.cfg. I only automatically generate it. It's possible to use either, but /etc/default/grub would make more sense as a recommendation in my mind because grub.cfg has the potential to be overwritten during updates, whereas /etc/default/grub doesn't.
  
:Hi, sorry for the late response, I'm quite busy these days. I'm convinced that the note is appropriate, but maybe somewhere on the [[Bumblebee]] page would be a better place to note about the blacklist? The [[NVIDIA Optimus]] page is not the first place everyone would go to after disabling bumblebee so they would have the same problem. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 21:50, 18 May 2019 (UTC)
+
If there's a compelling reason to use grub.cfg over /etc/default/grub, please let me know. ^^ I'm always eager to learn more about Arch. I don't want to get in a reversion war so I've left your change untouched for the time being.
  
::That's reasonable. I'll update [[Bumblebee]] instead. [[User:Lilydjwg|Lilydjwg]] ([[User talk:Lilydjwg|talk]]) 15:26, 19 May 2019 (UTC)
+
[[User:Eurydice|Eurydice]] ([[User talk:Eurydice|talk]]) 00:17, 8 September 2019 (UTC)
  
== systemd-boot....boot a LV ==
+
:The reason is explained in the section: "If GRUB is used with an unsupported filesystem it is not able to extract the UUID of your drive so it uses classic non-persistent /dev/sdXx names instead." If it does not apply to F2FS, it should be made clear. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 06:29, 8 September 2019 (UTC)
On the [https://wiki.archlinux.org/index.php?title=Systemd-boot&action=history/ Systemd-boot page] I made an example of a loader file which boot a LV.
 
It took me a long time to figure out.....was not able to find the information anywhere, not on the Archwiki neither, and neither on the LVM page, as you refer too.
 
I find this information very usefull for other readers.
 
Why do you disagree? If the example is wrong, please correct it instead of deleting it?
 
And I think the systemd-boot page is the rigth place for this information, not the LVM.
 
In my view people would first search here, and not the LVM page. And in my view it is more related to systemd-boot than LVM ;-)
 
  
{{unsigned|14:46, 15 May 2019‎|MrCalvin}}
+
::You can specify UUID's in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, so my proposed solution would work for F2FS and other unsupported filesystems, without the burden of manually editing grub.cfg. If there's anything I need to clarify or something else I'm missing, just let me know. :) [[User:Eurydice|Eurydice]] ([[User talk:Eurydice|talk]]) 19:37, 8 September 2019 (UTC)
  
:The [[LVM]] page has a section on the required [[LVM#Kernel options|kernel options]] and both [[systemd-boot]] and [[Kernel parameters]] (which is linked from [[LVM#Kernel options]]) pages have examples where to configure the {{ic|1=root=}} parameter. Hence, I don't see a point in showing dozens of different combinations for {{ic|1=root=}} on the [[systemd-boot]] page. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 17:19, 17 May 2019 (UTC)
+
:::The {{ic|1=root=}} parameter is not supposed to be in GRUB_CMDLINE_LINUX_DEFAULT, regardless if UUID is used or not. ''grub-mkconfig'' automatically detects the root filesystem and adds the appropriate {{ic|1=root=}} parameter based on GRUB_DISABLE_LINUX_UUID. In any case, your change to the paragraph does not make sense. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 20:02, 8 September 2019 (UTC)
  
First of all, if you need info on how to configure the systemd-boot loader file you'll go to the systemd-boot page.
+
::::It could simply be because I use full disk encryption, and adding a kernel parameter for the encrypted disk's UUID is correct in that situation. You're more experienced with contributing to the wiki, so I guess I'll defer to your judgment. It felt like a reasonable edit and solution to me and I don't see the downside to including it in GRUB_CMDLINE_LINUX_DEFAULT. [[User:Eurydice|Eurydice]] ([[User talk:Eurydice|talk]]) 05:38, 9 September 2019 (UTC)
Secondly if you really would end up on the LVM page you would never end up at the "Kernel options"?? section. It might theoretically be correct to call it "Kernal options" but it's not very help- or usefull.
 
Third....take a look at my example that was just removed and compare it to this "kernel options" one-liner section and ask yourself which one has the best readability and easy-to-understand level?
 
Well, I don't need the info anymore myself, so it has no value for me. Just sorry for the users who seek this information and will never find.
 
It's all about being pragmatic ;-) [[User:MrCalvin|MrCalvin]] ([[User talk:MrCalvin|talk]]) 20:43, 17 May 2019 (UTC)
 
  
:If you have [[LVM]], I really expect you would end up on that page. I hope you're not expecting the [[systemd-boot]] page to contain explicit examples for [[LVM]], [[RAID]], [[dm-crypt]], and even more, which would have to be duplicated for every other boot loader like [[GRUB]], [[syslinux]], [[refind]] etc. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 20:53, 17 May 2019 (UTC)
+
== <s>Personal subpage links in the main articles</s> ==
  
== <s>EFISTUB</s> ==
+
Ahoj, Jakub! There was a bit of the discussion about content of the [[Pacman (Русский)/Restore local database (Русский)]] article, but long story short, it ended with [[User:Xolst]] moving his way of the database backup/restore to [[User:Xolst/Restore local database 2.0 (Русский)|his own subpage]] and leaving link to it in the 'Related articles' section. So the question is, is it appropriate to have links in articles to personal subpages? I'm just curious as I don't recall such cases.
  
Please note that [https://bbs.archlinux.org/viewtopic.php?id=151410 PARTUUID does not boot]. -[[User:Mys_721tx|Mys_721tx]] ([[User_talk:Mys_721tx|talk]]) 14:32, 20 May 2019 (UTC)
+
Oh, and since I'm writing to you, there is an empty page [[InOut]] that I think can be deleted straight away.
  
:There is no reason why PARTUUID would not work, the thread you linked discusses just [https://bbs.archlinux.org/viewtopic.php?pid=1181576#p1181576 user readability] and [https://bbs.archlinux.org/viewtopic.php?pid=1182601#p1182601 user error]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 16:53, 20 May 2019 (UTC)
+
[[User:SlavMetal|SlavMetal]] ([[User talk:SlavMetal|talk]]) 21:46, 11 September 2019 (UTC)
::I noticed that my UUID and PARTUUID were mixed up. I added a note on how to find them. -[[User:Mys_721tx|Mys_721tx]] ([[User_talk:Mys_721tx|talk]]) 17:20, 20 May 2019 (UTC)
 
  
:::OK, thanks for doing that. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 19:20, 20 May 2019 (UTC)
+
:Hi, user pages should not be linked from the main namespace, see [[Help:Style#User_pages]]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 08:16, 14 September 2019 (UTC)
  
== Collapsible elements ==
+
::Oh, there it was, my bad. Thank you! -- [[User:SlavMetal|SlavMetal]] ([[User talk:SlavMetal|talk]]) 13:43, 15 September 2019 (UTC)
Collapsible elements are specified [https://www.mediawiki.org/wiki/Manual:Collapsible_elements here]. They are used on Wikipedia as templates. Since these templates are not available here, collapsible elements with HTML tags could be done. And, yes, sometimes they are necessary, especially for [[Pulseaudio]] page that is very bad written in some sections. But if you do not want them, let the page stay as it is, very difficult to read, not my issue. [[User:Digitalone|Digitalone]] ([[User talk:Digitalone|talk]]) 21:36, 25 May 2019 (UTC)
 
  
:Hiding information by default is not a universal solution to readability problems, it just moves the problem aside. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 22:54, 25 May 2019 (UTC)
+
== TSHARC touchscreen ==
  
== Rsync ==
+
"Workaround if default touchscreen driver xf86-input-evdev + xinput_calibrator does not cover whole screen for touch."
  
Regarding your comment that the leading '/' is needed in front of the excluded directories below, otherwise 'tmp/*' would exclude '/var/tmp/*' etc.:
+
14:43, 14 September 2019‎ -> https://wiki.archlinux.org/index.php?title=Touchscreen&oldid=582312
  
# rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} / ''/path/to/backup/folder''
+
undo due: unacceptable format and not tested on Arch
  
In that case, I think that you need to cd to / and run the command with '.' as the source directory, rather than '/'. Running the command as written above from outside of / did not work correctly for me, it didn't exclude the directories. Doing instead as I wrote worked.
+
-> unacceptable format: my first wiki entry at archlinux.org - tried to be as close as possible to other entries on that page -> any hints how to format right?
  
== [[special:diff/576712]] ==
+
-> not tested on Arch: got a NCR SelfServ 60 (7409) running Kernel 5.2.11-1 MANJARO Linux (x86_64).
  
1. it makes clear connection to the title text
+
"Manjaro - enjoy the simplicity
 +
https://manjaro.org
 +
Manjaro is an accessible, friendly, open-source Linux distribution and community. Based on Arch Linux [..]" -> Desktop Environment based on arch - headless or console does not make sense for touchscreens.
  
2. it didn't shorten anything
+
[[User:Everloop|Everloop]] ([[User talk:Everloop|talk]]) 13:38, 17 September 2019 (UTC)
  
[[User:Ubone|Ubone]] ([[User talk:Ubone|talk]]) 06:21, 2 July 2019 (UTC)
+
:See [[Help:Style]] and related pages for proper formatting. However, "based on Arch Linux" is not the same as "'''is''' Arch Linux". They even have their own wiki: https://wiki.manjaro.org/index.php?title=Main_Page -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:44, 17 September 2019 (UTC)
  
:All connections between MTA, MDA, MUA and other acronyms are already explained in the introduction so repeating them is just useless. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:43, 2 July 2019 (UTC)
+
[[User:Everloop|Everloop]] ([[User talk:Everloop|talk]]) 08:14, 21 September 2019 (UTC)
  
::it's not useless because you don't know what software you're reading about -- [[User:Ubone|Ubone]] ([[User talk:Ubone|talk]]) 09:28, 3 July 2019 (UTC)
+
Ok, so i stick to Manjaro Wiki.

Latest revision as of 08:14, 21 September 2019

bot checking links after move

Hi, re Talk:Touchpad Synaptics#adding libinput alternative. Touchpad Synaptics has 100+ backlinks and the more important ones - a bit tedious task. I was just glancing over your clever github bot scripts. It would be handy to have a script after such moves: walk over the backlinks of Touchpad Synaptics and just replace "[[Touchpad Synaptics" with "[[Synaptics" from the links. That would leave all links to subsections intact. Leaving out the translations to handle manually, there would not be much to go wrong, or? --Indigo (talk) 07:36, 26 September 2015 (UTC)

Hi, thanks for the suggestion. It would be indeed handy in this case, but most likely not generally. Imagine that there was a UUID page, which was later generalized and renamed to Persistent block device naming and content about UUID is now only a section on the page. In this case using the naive replacement would likely change the meaning of many sentences, and using shorter redirects for convenience is actually encouraged. There would have to be a list of whitelisted "harmless" replacements, which could even help to replace [[pacman|Install]] with [[Install]] etc. -- Lahwaacz (talk) 08:01, 26 September 2015 (UTC)
Yes, good examples, but you are thinking universal already :) I did not mean it could be that. For example, if you take the time when the bulk of the title case moves were done. With such a script one could avoid a lot of internal redirects as well. E.g. [1]. But it's ok, just an idea. Please close this, if you think it's too singular cases with a simple enough replacement where it could be applied. --Indigo (talk) 10:02, 26 September 2015 (UTC)

aur-mirror

Hi Lahwaacz,

It seems that aur-mirror has been down for a while. I'm not sure if this is intentional or not, but if it is, could you have Lahwaacz.bot remove Template:Aur-mirror from pages? At least where they are in a Template:Broken package link like {{Broken package link|{{aur-mirror|foobar}}}}.

If there is anything I can do to help, let me know.

Thanks! Lonaowna (talk) 14:56, 19 October 2016 (UTC)

Maybe drifting a bit offtopic... but I'm in favor to finally remove any and all packages that are not on AUR4 from the wiki. Users have had over a year time to migrate, which is a century in Arch standards. -- Alad (talk) 16:21, 19 October 2016 (UTC)
I agree, especially on pages like List of games (already took care of that), and List of Applications (see Talk:List of applications#AUR3 packages). On other pages, where the non-existing packages are mentioned inline, it requires some more knowledge and effort to remove them. -- Lonaowna (talk) 16:34, 19 October 2016 (UTC)
Hmm... For the moment I just updated the template to point to Github instead. What would be the alternative "hint" without the link? It should still be different from just "package not found". -- Lahwaacz (talk) 18:08, 19 October 2016 (UTC)
The GitHub repository is fine as well. I think we can keep that one while we (carefully) remove/update all broken links. Thanks! Lonaowna (talk) 06:52, 20 October 2016 (UTC)

mkosi

Hi, about your revert: You can use mkosi also to create a container/directory tree (-t directory). So it can do the same and more. -- Nudin (talk) 11:33, 1 October 2017 (UTC)

Alright, how is the "more" relevant to systemd-nspawn though? -- Lahwaacz (talk) 17:30, 3 October 2017 (UTC)
Hi, mkosi let's you create images (or directory trees) of various different distributions and allows you to do things like setting the root-password or installing additional packages. systemd-nspawn alows you to boot such images/directory trees. So I thought mentioning mkosi as alternative to manually creating a container with pacstrap or debootstrap would be worth it. -- Nudin (talk) 22:23, 5 October 2017 (UTC)

GRUB/Tips and Tricks

You reverted an edit I made to the /etc/grub.d/40_custom example at GRUB/Tips and tricks#Password_protection_of_GRUB_menu, and your comment for doing so has me thinking you believe I put the heredoc syntax in to show someone how to cat mulitple lines from the command line. If that was my intent, I would agree with you that my change should be reverted. That's not what I was doing.

The file contents as they are now produce an error upon running grub-mkconfig. I know because I tried this. The file contents need to include the heredoc syntax.

In other words, if the file contents are the following, grub-mkconfig produces an error:

set superusers="username"
password_pbkdf2 username <password>

I was able to resolve this by adding the heredoc syntax, upon which everything worked. Again, the file contents need the heredoc syntax, as follows:

cat << EOF
set superusers="username"
password_pbkdf2 username <password>
EOF

With that in mind, I hope you'll agree that my edit was worthwhile.

By the way, this isn't uncommon syntax for grub.d conf files. There are other examples of it, for instance section 3 of this AskUbuntu answer for Mac users to activate their discrete video cards.

Djmoch (talk) 12:13, 1 December 2017 (UTC)

Waking from suspend with USB device

Hi Lahwaacz, thanks for your input on this topic. Can you help me a bit further, I know the USB host controller and the USB device are different things but I thought that enabling the host controller was not necessary anymore, see [2]. In my case all the driver/*/power/wakeup are all enabled by default and the /proc/acpi/wakeup as well. Anyway I have added a step in my explanations to identify the path awaiting for more clarity.

Kewl (talk) 21:57, 16 January 2018 (UTC)

Hi, thanks for the link, it's entirely possible that something changed since the section was written. However, in my case only the keyboard device has wakeup enabled by default:
$ for f in /sys/bus/usb/drivers/usb/*/power/wakeup; do echo "$f: $(cat $f)"; done
/sys/bus/usb/drivers/usb/1-1/power/wakeup: disabled
/sys/bus/usb/drivers/usb/2-1/power/wakeup: disabled
/sys/bus/usb/drivers/usb/3-11/power/wakeup: disabled
/sys/bus/usb/drivers/usb/3-12/power/wakeup: enabled
/sys/bus/usb/drivers/usb/3-13/power/wakeup: disabled
/sys/bus/usb/drivers/usb/4-3/power/wakeup: disabled
/sys/bus/usb/drivers/usb/4-4/power/wakeup: disabled
/sys/bus/usb/drivers/usb/usb1/power/wakeup: disabled
/sys/bus/usb/drivers/usb/usb2/power/wakeup: disabled
/sys/bus/usb/drivers/usb/usb3/power/wakeup: disabled
/sys/bus/usb/drivers/usb/usb4/power/wakeup: disabled
But in practice it seems to wake up the system even without the host controllers enabled for wakeup... It might also depend on some BIOS/firmware settings but if it works by default on most systems then I think the host controller settings could be removed again.
-- Lahwaacz (talk) 19:14, 19 January 2018 (UTC)

Page titles

Hi, i need help. I didn't find answer on my question in archwiki. Is "Title (Language)/Sub-page (Language)" correct? It is logically. But in archwiki says only: "Also note that in case of sub-pages, the language tag still goes at the end, so "Title (Language)/Sub-page" is wrong, while "Title/Sub-page (Language)" is correct." -- ArchLinuxUser (talk) 16:08, 21 January 2018 (UTC)

Help:I18n#Page titles is pretty clear on that "Title/Sub-page (Language)" is correct. It seems to me that "Title (Language)/Sub-page (Language)" would be superfluous.
The "(Language)" suffix applies to the entire "Title/Sub-page" bit as a whole. It can't be that the first (Language) is different from the second (Language), so why would you put it there twice?
-- Lonaowna (talk) 16:48, 21 January 2018 (UTC)
Also see Help talk:Style#Slashes in titles. Seems like there was some discussion on this. -- Lonaowna (talk) 16:58, 21 January 2018 (UTC)
If you use "Title/Sub-page (Language)", then you return to "Title", not to "Title (Language)". For examle, if you go to List of applications/Internet (Русский), and you want to go back through the "< List of applications", you will be taken to the English version of the page. -- ArchLinuxUser (talk) 17:11, 21 January 2018 (UTC)
How about my variant? It is logically (for example, the Russian sub-page is part of Russian page. Schematically it look like this: Title (Language)/Subpage (Language)). -- ArchLinuxUser (talk) 18:00, 21 January 2018 (UTC)
Hi, the Title (Language)/Sub-page and Title (Language)/Sub-page (Language) formats don't work, because the English page is Title/Sub-page and the interlanguage links (shown in the left navigation column of each page) lead to Title/Sub-page (Language). Unfortunately, as I mentioned in Help_talk:Style#Localized_subpages, there is no way to configure the interlanguage links to have the language in the middle of the page title. -- Lahwaacz (talk) 21:11, 21 January 2018 (UTC)
We can do another format of Interlanguage links for sub-page. For examle,
[[en:Title/Sub-page]]
[[es:Title (Español)/Sub-page]]
[[ru:Title (Русский)/Sub-page]]
See also CUPS (Русский)/Troubleshooting (Русский) and CUPS/Troubleshooting. Do i understand everything true? Must i fix this page? -- ArchLinuxUser (talk) 05:00, 22 January 2018 (UTC)
Well, technically the Title (Language)/Subpage (Language) format + lang:Title (Language)/Subpage link would work, but repeating the language does not look nice (and I think there are even some pages like Title/Subpage/Subsubpage). I think the ultimate goal is to use language namespaces as discussed in Help_talk:I18n#Language_namespace.28s.29_in_place_of_suffixes.3F, but it's still a long way ahead so until then let's use what we have for consistency. -- Lahwaacz (talk) 22:08, 23 January 2018 (UTC)

Are supported local/remote destinations important for choosing a backup program?

You reverted my edit adding supported backup destinations to Synchronization_and_backup_programs. This is puzzling to me. Here are some thoughts:

  • if choosing any backup program, the ability to send the backup off-site vs only on a local disk is a key feature consideration. Perhaps *the* key feature: one helps me recover in case my house gets burglarized or burns down, and the other does not. This is a much more important feature consideration than, say, whether the program is written in Go or Mono (something that has a full column). I think it's hard to disagree on that.
  • Given this, I am very puzzled you would use the term "useless" in the revert message.
  • I assume you didn't like that the table got even bigger (it didn't fit into the layout even before). I don't like it either, but perhaps the revert should have said "can you put this somewhere else, not in this already-too-big table?"
  • On a personal note, when I provide feedback or give opinion on somebody else's work, I'd like to be constructive and kind, instead of aggressive and putting people down. Just a thought. Thanks for listening.

Jernst (talk) 17:38, 11 June 2018 (UTC)

No because you can use any remote back-end with any backup application by just running one command / writing the backups to a FUSE (if available).--Larivact (talk) 04:39, 12 June 2018 (UTC)
Hmm, by that reasoning we don't need the Arch package repository, as long as we have source code and makepkg. Or Perl, if we have bash and awk. But even then, and if all the fuse backends existed (I doubt they do), and if it were easy to set all of them up (another thing I doubt), do you indeed believe that running something written to read/write local files will be just as efficient backing up gigabytes of data to a remote repository as something that is specifically optimized for that use case? Note that backing up, say, daily, a typical hard drive via tpyical consumer broadband is still quite a bandwidth challenge in many places today. What about we add this info, and remove (or merge) some other columns to make the table smaller? —This unsigned comment is by Jernst (talk) 18:08, 12 June 2018‎. Please sign your posts with ~~~~!
Your comparisons don't make sense. Mind the slash in my response, you do not need a FUSE implementation, a simple CLI suffices. You do not need to "set all of them up", you only need one. --Larivact (talk) 18:47, 12 June 2018 (UTC)
If you ever attempt to help a normal user set up a reliably-working off-site backup strategy, think of this discussion. In the meantime, this is all the time I'm going to spend on a discussion that has such repeated gems in it as "makes no sense" without explaining why you think so. Have a nice day. Jernst (talk) 18:54, 12 June 2018 (UTC)

Archive (Español)

Sorry for giving you some work today. I didn't know there should be only one "Archive" for all languages. You could have warned me and I would have corrected it for you. Best regards and sorry again. --AlonsoLP (talk) 11:38, 15 September 2018 (UTC)

Being in the vboxsf group does not automatically give you access to mount points

Hi -

Regarding revision #565457 of the VirtualBox Wiki page. I'm aware of what upstream says and hesitated before making this change, but I tested it myself (current non-dkms VirtualBox, fairly generic Arch client with the virtualbox-host-modules-arch package installed), and it just does not work. Perhaps this is because automatic mounting is currently broken? (See https://bbs.archlinux.org/viewtopic.php?id=243871 which references a couple of bug reports.)

In any case, on the Arch client, user pgoetz is in the vboxsf group. I set up a shared folder using the hypervisor GUI like this:

Folder Path: /home/pgoetz
Folder Name: pgoetz
Mount Point: /home/share/pgoetz
Read-only: no
Auto-mount: yes
Make Permanent: yes
VBoxManage showvminfo {VM Name}

shows the mount:

Shared folders:
Name: 'pgoetz', Host path: '/home/pgoetz' (machine mapping), writable, auto-mount, mount-point: '/home/share/pgoetz'

but nothing is actually mounted there. Maybe this is the issue; if the folder were actually mounted there it would be write-accessible by any member of the vboxsf group

However, the only way to get the mount to happen is to either mount it manually or create an entry in /etc/fstab.

If I use this entry in /etc/fstab:

 pgoetz  /home/share/pgoetz  vboxsf  rw,noauto,x-systemd.automount  0  0

the folder is definitely not accessible by user pgoetz. In order to facilitate that, I have to use this /etc/fstab entry:

 pgoetz  /home/share/pgoetz  vboxsf  uid=1000,gid=1000,rw,noauto,x-systemd.automount  0  0


In any case, as stated currently on the VB Wiki page, it does not work, which is why I changed it, thinking that what is there will confuse people. We can leave it as is for now, and I'll test again if and when the hypervisor initiated automount starts working again.

Pgoetz (talk) 14:18, 2 February 2019 (UTC)

There are other places which mention the vboxsf group (e.g. the previous section), so I found your edit more confusing than the original state. Lahwaacz (talk) 15:27, 2 February 2019 (UTC)
Understood. I'll revisit this if and when the hypervisor automount works again. If it still doesn't work, I'll make sure I update it everywhere. Thanks. Pgoetz (talk) 16:00, 2 February 2019 (UTC)

The pip section in Python package guidelines

Hi, you wanted the warning about using pip or wheels restored but accidentally(?) reverted my whole set of changes. I redid them, leaving the warning in place. – flying sheep 08:17, 8 March 2019 (UTC)

Full revert was intentional, because the "wheel" section is not a full replacement for "pip" because there are packages which don't provide wheel files. As I said in the edit summary, there is no reason to recommend one or the other due to the warning. -- Lahwaacz (talk) 19:21, 8 March 2019 (UTC)
That still doesn’t explain why you reverted the first part, that had nothing to do with the pip/wheel section and simple improves the files.pythonhosted.org URLs. I restored that one while we’re discussing the pip/wheel section. And about that: There’s no reason to use pip for anything else, and pip is only used because some people (me included) didn’t understand that you can install most wheels by just extracting them to the correct location. So what do you think is missing from my wheels section that the former pip section had? – flying sheep 11:41, 11 March 2019 (UTC)
If you didn't notice, the page includes "guidelines" in the title. So the page should contain only common and recommended ways to do things, not everything that is possible to do. If you think that your way to install "wheels" should be followed by everybody, feel free to discuss it on the talk page. -- Lahwaacz (talk) 13:26, 11 March 2019 (UTC)
Well, extracting static archives sounds much more recommended than running pip with like 7 options to make it behave. I added a talk item: Talk:Python package guidelines#Remove_pip_section_in_favor_of_wheels_section?flying sheep

Google error messages and GnuPG

Hi, with regard to your removal of my edit of the Troubleshooting section of GnuPG, I understand that it shouldn't just be TL;DR, but I'm wondering if there's a way to at least mention the error message, `sign_and_send_pubkey: signing failed: agent refused operation`, somewhere on the page, since I ran into that error with my smartcard (NitroKey) and googled the error message all across the web, before finally realizing the problem wasn't NitroKey-related at all, but related to not pointing to the right TTY. So I wanted to mention the error in some way on the page to enable others googling it to easier find what the problem is.

Is there a smarter way to do that? --Madpet (talk) 11:31, 22 April 2019 (UTC)

You can't sensibly describe a catch-all error message for which there are at least a dozen of causes, most of them resulting from bad configuration. It should be clear that the whole configuration should be checked, no section is needed for that. -- Lahwaacz (talk) 11:47, 22 April 2019 (UTC)

wpa_supplicant

Regarding https://wiki.archlinux.org/index.php?title=WPA_supplicant&diff=577215&oldid=577167, one person ran into this problem in March of this year and spent too much time diagnosing it:

https://bbs.archlinux.org/viewtopic.php?id=244950

It took me a few days to find the problem. I want to make sure the next time someone encounters it, they easily find relevant information about what the cause is. Since you've reverted my edits to both netctl and wpa_supplicant, what do you suggest?

--

Pooryorick (talk) 08:24, 18 July 2019 (UTC)

Regarding your edit in Silent boot#Retaining the vendor logo from BIOS

The vendor logo was already set by default to be retained and visible during bootup for me, but I wanted to manually configure it to disable the vendor logo. I searched wiki for instruction to turn it off, however it took me a few to find the correct section, even from googling the problem. My edit was to make it easier to be searched for, and to make it more clear that it was the section for disabling the vendor logo. It is quite possible that more people have it retained by default and want to disable it like I have.

Jmarmstrong1207 (talk) 17:15, 1 August 2019 (UTC)

Set by default where? The section already describes everything related, so maybe it should be just renamed to "Retaining or disabling the vendor logo from BIOS" to make it more discoverable. The subsection should be still "Disabling deferred takeover" though, because that's what it does. -- Lahwaacz (talk) 19:52, 1 August 2019 (UTC)

My bad, it is set default as mentioned in the section, though some users may want it disabled. I agree that it should be renamed to that. Jmarmstrong1207 (talk) 02:06, 11 August 2019 (UTC)

OK, thanks. -- Lahwaacz (talk) 06:12, 11 August 2019 (UTC)

F2FS and GRUB

Hello. :) I'm here to address a recent disagreement. I noticed a reversion of my edit regarding the F2FS filesystem, in particular regarding the configuration file to edit (with you representing /boot/grub/grub.cfg and me representing /etc/default/grub). I run F2FS on my daily driver with an encrypted root filesystem and encrypted boot on a separate partition, and have never had to touch grub.cfg. I only automatically generate it. It's possible to use either, but /etc/default/grub would make more sense as a recommendation in my mind because grub.cfg has the potential to be overwritten during updates, whereas /etc/default/grub doesn't.

If there's a compelling reason to use grub.cfg over /etc/default/grub, please let me know. ^^ I'm always eager to learn more about Arch. I don't want to get in a reversion war so I've left your change untouched for the time being.

Eurydice (talk) 00:17, 8 September 2019 (UTC)

The reason is explained in the section: "If GRUB is used with an unsupported filesystem it is not able to extract the UUID of your drive so it uses classic non-persistent /dev/sdXx names instead." If it does not apply to F2FS, it should be made clear. -- Lahwaacz (talk) 06:29, 8 September 2019 (UTC)
You can specify UUID's in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, so my proposed solution would work for F2FS and other unsupported filesystems, without the burden of manually editing grub.cfg. If there's anything I need to clarify or something else I'm missing, just let me know. :) Eurydice (talk) 19:37, 8 September 2019 (UTC)
The root= parameter is not supposed to be in GRUB_CMDLINE_LINUX_DEFAULT, regardless if UUID is used or not. grub-mkconfig automatically detects the root filesystem and adds the appropriate root= parameter based on GRUB_DISABLE_LINUX_UUID. In any case, your change to the paragraph does not make sense. -- Lahwaacz (talk) 20:02, 8 September 2019 (UTC)
It could simply be because I use full disk encryption, and adding a kernel parameter for the encrypted disk's UUID is correct in that situation. You're more experienced with contributing to the wiki, so I guess I'll defer to your judgment. It felt like a reasonable edit and solution to me and I don't see the downside to including it in GRUB_CMDLINE_LINUX_DEFAULT. Eurydice (talk) 05:38, 9 September 2019 (UTC)

Personal subpage links in the main articles

Ahoj, Jakub! There was a bit of the discussion about content of the Pacman (Русский)/Restore local database (Русский) article, but long story short, it ended with User:Xolst moving his way of the database backup/restore to his own subpage and leaving link to it in the 'Related articles' section. So the question is, is it appropriate to have links in articles to personal subpages? I'm just curious as I don't recall such cases.

Oh, and since I'm writing to you, there is an empty page InOut that I think can be deleted straight away.

SlavMetal (talk) 21:46, 11 September 2019 (UTC)

Hi, user pages should not be linked from the main namespace, see Help:Style#User_pages. -- Lahwaacz (talk) 08:16, 14 September 2019 (UTC)
Oh, there it was, my bad. Thank you! -- SlavMetal (talk) 13:43, 15 September 2019 (UTC)

TSHARC touchscreen

"Workaround if default touchscreen driver xf86-input-evdev + xinput_calibrator does not cover whole screen for touch."

14:43, 14 September 2019‎ -> https://wiki.archlinux.org/index.php?title=Touchscreen&oldid=582312

undo due: unacceptable format and not tested on Arch

-> unacceptable format: my first wiki entry at archlinux.org - tried to be as close as possible to other entries on that page -> any hints how to format right?

-> not tested on Arch: got a NCR SelfServ 60 (7409) running Kernel 5.2.11-1 MANJARO Linux (x86_64).

"Manjaro - enjoy the simplicity https://manjaro.org Manjaro is an accessible, friendly, open-source Linux distribution and community. Based on Arch Linux [..]" -> Desktop Environment based on arch - headless or console does not make sense for touchscreens.

Everloop (talk) 13:38, 17 September 2019 (UTC)

See Help:Style and related pages for proper formatting. However, "based on Arch Linux" is not the same as "is Arch Linux". They even have their own wiki: https://wiki.manjaro.org/index.php?title=Main_Page -- Lahwaacz (talk) 13:44, 17 September 2019 (UTC)

Everloop (talk) 08:14, 21 September 2019 (UTC)

Ok, so i stick to Manjaro Wiki.