Screen sharing in video conferencing software (bbb, webex, meetme etc). It just doesn't work consistently. Sometimes (rarely) it just works as expected. Sometimes everybody sees a "black screen with a mouse pointer". Sometimes your screenshare is tiny and squeezed into a quarter of the virtual screen. Sometimes it's enlarged instead and doesn't fit into the virtual screen. Sometimes the popup (Wayland recording bridge???) doesn't show up. It's russian roulette basically, this shit definitely needs more eyeballs.
Most of these are not about the Linux kernel, but about distro / personal choice. Android tracks you and doesn't make you use the command-line a lot. Fedora / Ubuntu (and others?) like to reboot for every little update.
I'm not using grub anymore, but from my time when I did, I remember there's a "settings" file /etc/default/grub.
Carefully change some timeout-related settings there (for example, add GRUB_TIMEOUT=5). Your change in the settings file becomes effective (on next boot) after you re-generate the grub "config" using the following command: grub2-mkconfig -o /boot/grub2/grub.cfg. Then check if it the problem still persists.
Can you please post that file here? It should not contain any sensitive information.
Now look carefully at the output (or dump it to a file first, by appending something like > /tmp/files.txt). Does it look good to you? Maybe it's empty? See any spaces in filenames or directories?
Here's a sed stub that finds lines with whitespace:
echo -e "line with space\nline_without_space" | sed -E -n '/\s/p'
Get rid of the echo "'$dir'/'$base'", thats's too much to read. Instead, add sanity checks in your loop, like this:
Very useful for renaming a variable: * to search "word" under cursor. Try this with hlsearch on::set hlsearch. Then cw to change a match. Alternate n and . to quickly rename more occurrences of the word. Do a :noh to get rid of the highlighting. Maybe try :set noinc, some people prefer the traditional "non-incremental" search.
Do all this in normal mode. Vim experts leave insert mode as soon as possible. Almost forgot: Pressing C-c takes you back to normal mode without leaving home row.
Most important advice: Never touch arrow keys. Keep your fingers on the home row. Learn hjkl movement (focus on j and k, they are more important). Then get faster by using b, w, f, o, O, A, I, C-d and all the rest. Learn about J, it's cool. You won't get far without u and C-r though.
Critically important advice for fellow Europeans: If you care about vim, consider learning the US keyboard layout. Default bindings are not convenient in other layouts like qwertz (where is forward slash on qwertz? Hello?), and learning US layout might be easier than learning to customize vim. On a typical modern Linux system, there are US layout variants that still allow typing Umlauts, like EurKey or "DE-US", where you type ä by pressing RightAlt+a, for example.
Ergebnis: https://www.nuernberg.de/datenwahlen/be2026/index.html
Screen sharing in video conferencing software (bbb, webex, meetme etc). It just doesn't work consistently. Sometimes (rarely) it just works as expected. Sometimes everybody sees a "black screen with a mouse pointer". Sometimes your screenshare is tiny and squeezed into a quarter of the virtual screen. Sometimes it's enlarged instead and doesn't fit into the virtual screen. Sometimes the popup (Wayland recording bridge???) doesn't show up. It's russian roulette basically, this shit definitely needs more eyeballs.
Could this be.. a script sharing thread? Anyway, here's a fedora updater and a fedora installer
I like to press"Control-c" instead of ESC. It is more convenient to type and mostly does the same thing.
Red car is on the passenger side first, then suddenly on the drivers side.
My pain points with Fedora: signed sdboot and anaconda. Anaconda in particular looks like an unmaintainable mess that needs to be replaced.
Gibt es einen wichtigen Grund wieso man morgens kein Koffein zu sich nehmen sollte?
problem with password expiry https://github.com/sddm/sddm/issues/472
tl;dr yes there are parking garages nearby, at least in my city
Most of these are not about the Linux kernel, but about distro / personal choice. Android tracks you and doesn't make you use the command-line a lot. Fedora / Ubuntu (and others?) like to reboot for every little update.
I don't know man. It seems you have an nvidia card. Have you asked on fedora discussion yet? Here's someone who might have had a similar issue: https://discussion.fedoraproject.org/t/grub-freeze-with-direct-uefi-boot-on-hp-but-works-with-boot-menu/73072
I'm not using grub anymore, but from my time when I did, I remember there's a "settings" file
/etc/default/grub.Carefully change some timeout-related settings there (for example, add GRUB_TIMEOUT=5). Your change in the settings file becomes effective (on next boot) after you re-generate the grub "config" using the following command: grub2-mkconfig -o /boot/grub2/grub.cfg. Then check if it the problem still persists.Can you please post that file here? It should not contain any sensitive information.
Start your analysis by doing only the "detection" part:
Now look carefully at the output (or dump it to a file first, by appending something like
> /tmp/files.txt). Does it look good to you? Maybe it's empty? See any spaces in filenames or directories?Here's a sed stub that finds lines with whitespace:
Get rid of the
echo "'$dir'/'$base'", thats's too much to read. Instead, add sanity checks in your loop, like this:or this:
There may be other issues, but to handle whitespace in file names correctly, you need more quoting at least here:
Bookmarked 😜 Mind adding a dark mode?
Very useful for renaming a variable:
*to search "word" under cursor. Try this with hlsearch on::set hlsearch. Thencwto change a match. Alternatenand.to quickly rename more occurrences of the word. Do a:nohto get rid of the highlighting. Maybe try:set noinc, some people prefer the traditional "non-incremental" search.Do all this in normal mode. Vim experts leave insert mode as soon as possible. Almost forgot: Pressing
C-ctakes you back to normal mode without leaving home row.Most important advice: Never touch arrow keys. Keep your fingers on the home row. Learn
hjklmovement (focus onjandk, they are more important). Then get faster by usingb,w,f,o,O,A,I,C-dand all the rest. Learn aboutJ, it's cool. You won't get far withoutuandC-rthough.Critically important advice for fellow Europeans: If you care about vim, consider learning the US keyboard layout. Default bindings are not convenient in other layouts like qwertz (where is forward slash on qwertz? Hello?), and learning US layout might be easier than learning to customize vim. On a typical modern Linux system, there are US layout variants that still allow typing Umlauts, like EurKey or "DE-US", where you type
äby pressing RightAlt+a, for example.I use cat (as root) to write ISO to flash drive. Anything wrong with that?
in
[[there is generally no need for quoting, except the right hand side of an=comparisonin
[[, empty strings are falsy, so this also works:The variables need a dollar sign:
$VARIABLE1help testshows what-nand-zdo.Never use
a && b || c. It is not the same asif a; then b; else c; fi: whenasucceeds butbfails, it will run bothbandc.I would not bother with
[unless you absolutely need compatibility with non-bash shells.