User talk:Lahwaacz

From ArchWiki
Jump to navigation Jump to search

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)


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 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)

Template:aur-mirror is going to be removed, closing. -- Lahwaacz (talk) 15:25, 26 May 2020 (UTC)


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>

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,
[[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)
This is now in Help:I18n#Page titles, closing. -- Lahwaacz (talk) 16:57, 26 May 2020 (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)

No problem. -- Lahwaacz (talk) 16:56, 26 May 2020 (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 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 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


Regarding, one person ran into this problem in March of this year and spent too much time diagnosing it:

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)


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)

dracut executable link

Hello, your last edit on the dracut page ( that undid my 'Link to direct "make executable" section for executable link' commit states: "the redirect executable points exactly to that section", but it doesn't. Following the executable link just points to the top of the Help:Reading page.

—This unsigned comment is by Krathalan (talk) 17:06, 28 January 2020‎. Please sign your posts with ~~~~!

In that case your browser probably does not work correctly, because the redirect really points to the section. Or MediaWiki, there was a bug several years ago... -- Lahwaacz (talk) 19:41, 28 January 2020 (UTC)
How strange... thanks for pointing that out. It does indeed appear to be some issue with my Firefox configuration. Krathalan (talk) 19:51, 28 January 2020 (UTC)

Getting install.php work in DokuWiki

Hi, than you for having undone my contribution and pointed to the right solution on Dokuwiki#Configuration. Indeed I had read this solution before, but I was misled by the condition "if you are using lighttpd or nginx and your PHP version is lower than 7": as I use Apache with php v. 7.4.3 I didn't take it into account. Do you know what a correct rephrasing could be? Maybe it should be deleted?

Also, I think that, at the end of this same section, one should add something like "verify that php-gd is installed and restart php-fpm.service".

Naturally I can do it myself, but I prefer to ask before. BDumont (talk) 17:31, 19 February 2020 (UTC)

Hi, apparently it depends on whether you had open_basedir set previously or not. I've changed the page, feel free to update the gd extension. -- Lahwaacz (talk) 21:16, 19 February 2020 (UTC)
Thank you! However, while, I didn't have open_basedir set previously, I couldn't access install.php. I suspect there is another thing to do, since the configuration editor in DokuWiki complains that it cannot modify the configuration files although ownership and permissions are correctly set for the relevant symlinks, directories and files, and so is open_basedir. However I can edit my pages. Maybe a return from a new user with a fresh installation would be more useful, though. BDumont (talk) 08:20, 20 February 2020 (UTC)

Dead link in Simple stateful firewall#See Also

Hi, Jakub. I am about this edit. I tried to follow that link one more time and it is not require entering captcha. I am not see any content limitations and my colleague (he uses Tor) does not see them too. I am not sure how it works, so I leave it on your descision. -- Duodai (talk) 14:29, 1 March 2020 (UTC)

Well, maybe it depends on the location from which the request comes. But I don't know how it works either... -- Lahwaacz (talk) 14:33, 1 March 2020 (UTC)
my guess is it returns captcha for crawlers only -- Ubone (talk) 01:59, 2 March 2020 (UTC)
I'm getting it in my browser... -- Lahwaacz (talk) 07:14, 2 March 2020 (UTC)

SystemD user units depending on graphical session

Hi, regarding reverting my addition to Systemd/User, could you please explain why? I referenced [[3]] which directly contradicts what you said in your summary.

—This unsigned comment is by Fuero (talk) 19:53, 5 May 2020‎. Please sign your posts with ~~~~!

The note in Systemd/User#How it works still applies - systemd services are never per-session, but per-user. The service does not magically get the correct DISPLAY or WAYLAND_DISPLAY variable, it does not work if you have multiple sessions per user, etc. -- Lahwaacz (talk) 12:45, 6 May 2020 (UTC)


Actually with just Plymouth it does not work properly. Even 0dd17y had the same issue in

The reason I did not file a bug report is that it is anyway fixed in the git version and the latest release (0.9.4) is around 2 years behind master

—This unsigned comment is by M.Srikanth (talk) 09:50, 6 May 2020‎. Please sign your posts with ~~~~!

So if you don't have to file a bug report, add a full troubleshooting entry or at least properly reference your inline note instead of resorting to plain "if that does not work, try this instead". -- Lahwaacz (talk) 12:15, 6 May 2020 (UTC)

[Bitcoin core] build the code and run the test suites


This week, I managed to build the Bitcoin code and run all the test suites with the help of this page:

Archlinux has two particularities:

  • being in rolling release, it takes to manually use the library Berkeley DB (BDB) v4.8
  • the /tmp directory is by default limited to half the size of the Ram

For these reason, maybe it could be interesting to have a page in the wiki to explain how to build the Bitcoin core?



Thomasb (talk) 20:29, 9 May 2020 (UTC)

I don't think that this is useful. There is the bitcoin-core-gitAUR package and nothing more should be needed. -- Lahwaacz (talk) 16:53, 26 May 2020 (UTC)

Double linefeed results in extra line

If you look at templates that end with double linefeed before noinclude this would result in extra line in resulting page.

It may be a minor point but since you are perfectionist about wikitext I should mention this is a tradeoff and it results in slightly worse result.

Removing just one linefeed removes the problem while still allowing it to not jumble all the tags into same line.

-- Svito (talk) 16:30, 11 May 2020 (UTC)

If this is about [4], the spaces I added back are not included when the template is used elsewhere, because the spaces are inside the noinclude tags. The extra space is only on the template page itself, but it does not result from template inclusion. -- Lahwaacz (talk) 20:41, 11 May 2020 (UTC)
OFC, I mean the template page render has extra line. -- Svito (talk) 21:21, 11 May 2020 (UTC)
I agree with Svito, isn't it good to delete the extra blank lines? -- Blackteahamburger (talk) 05:39, 12 May 2020 (UTC)
OK, let's do it. [5] -- Lahwaacz (talk) 16:47, 26 May 2020 (UTC)

Re: lighttpd: remove python2 version

Instead of removing the example we could as well add an example using a Python3 library like

—This unsigned comment is by Gruentee (talk) 15:23, 18 May 2020‎. Please sign your posts with ~~~~!

Feel free to add it if you find it useful. -- Lahwaacz (talk) 20:56, 18 May 2020 (UTC)

Wrong category

I accidentally moved Category:Disk encryption (Polski) to Category:Category:Data-at-rest encryption (Polski), please delete it for me, thank you. -- Blackteahamburger (talk) 15:20, 24 May 2020 (UTC)

Fixed, thanks. -- Lahwaacz (talk) 16:16, 24 May 2020 (UTC)

Useless redirects

The user used the wrong title: Fcitx5(简体中文) and Fcitx5 (简体中文), please delete these redirects, thank you! -- Blackteahamburger (talk) 07:34, 30 May 2020 (UTC)

Fixed. -- Lahwaacz (talk) 07:40, 30 May 2020 (UTC)

Xbindkeys removal

Hi, just wondering why you removed my edit from Xbindkeys? The xbindkeys page has a number of quick tips but no mention of how to bind anything to the Print Screen key so I thought it would be useful to add. -- Malvineous (talk) 02:27, 3 June 2020 (UTC)

Giving examples for all keys on the keyboard is useless, there is Xbindkeys#Identifying keycodes which teaches how to find the keycodes and keysyms of any key. -- Lahwaacz (talk) 06:37, 3 June 2020 (UTC)
So how come you left the examples for the volume up/down and brightness? What is different between those examples and a screenshot example? Aren't more examples better to save people from hunting all over the place trying to piece things together themselves? -- Malvineous (talk) 14:03, 4 June 2020 (UTC)

Bluetooth Headset removal

Hi, I disagree with your removal at Bluetooth Headset since adding the bluetooth group and adding the user to it makes a difference in permission see User talk:Werererer

Re: Revert for edit to XDG Base Directory page regarding python_history

I understand the justification for reverting the change I made, however I would like to point out that similar entries on the page (such as Maven) also have instructions for what contents to put in files (even though there is native documentation for those settings). Additionally, it took me a bit of re-reading on the linked Python documentation to reason out how the documentation's example needed to be modified, since it's not clear from the Python documentation whether placing such code in the PYTHONSTARTUP file will actually override the default behavior. Varriount (talk) 20:44, 20 June 2020 (UTC)

Re: Revert for Backlight page

Hi, you reverted my change to Backlight page that mentioned WIP patches for controlling OLED panel brightness. I don't really understand justification for reverting it since currently the page says that OLED brightness can be controlled only by changing gamma ramp. That is wrong - since it's not the only way - these panels can control brightness with a PWM. Moreover controlling brightness with gamma ramp is not optimal - it essentially reduces dynamic range, i.e. at 50% you have 7 bits per pixel, at 25% - 6 bit per pixel, etc. That results in banding artifacts at lower brightness level.

As far waiting for the patches to be merged before mentioning it there - it'll take ~3-6 months (yes, that's the process) and I haven't found *any* reference to these changes on the internet - everyone recommends using gamma ramp instead of fixing it properly. I'm absolutely sure that having information about these patches would not hurt Anarsoul (talk) 15:56, 30 June 2020 (UTC)