Hi, everybody
Recently, a guy noticed that I was using it and asked why?
For me it because in Linux many things are done through the terminal because Linux has many different desktop environments

He also compared terminal commands with cheat codes in GTA and other games, he understands what benefits you take from them, but not from terminal commands

For me it must be kde plasma 6 and the wayland driver for wine.

Edit: I made the question gendered by using the word guys. I've fixed my mistake.

Sensitive content Reveal/hide

Hi all,

I'm in the market for a new big desktop replacement gaming laptop, and looking at the market there are almost exclusively Nvidia powered.

I was wondering about the state of their new open-source driver. Can I run a plain vanilla kernel with only open source / upstream packages and drivers and expect to get a good experience? How is battery life, performance? Does DRI Prime and Vulkan based GPU selection "just work"?

The only alternative new for my market is a device with an Intel Arc A730M, which I currently think is going to be the one I end up buying.

Edit 19/11: Thanks for all the feedback everyone! Since the reactions were quite mixed - "it works perfectly for me" vs "it's a unmaintainable mess that breaks all the time", I'm going to err on the side of caution and look elsewhere. I found a used laptop with an AMD Radeon RX 6700M, which I'm going to check out the coming days. If not, I've also found Alienware sells their m16 laptop with an RX 7600M XT, which might be a good buy for me (I currently still rock an Alienware 17R1 from 2013 with an MXM card from a decomissioned industrial computer in it).

Link to article: gist.github.com/probonopd/9feb…

This OUTDATED article gets posted all the time. The full story is the guy is a massive FreeBSD fan so he is trying to convince more people to keep on using Xorg because he wants to make sure it isn't abandoned. Reason for that being that Wayland is built with Linux in mind and would not work under FreeBSD without a lot of effort bwing put in as it uses some Linux-specific components or libraries.

Let's go through the article point by point:

Wayland is broken by design:

• A crash in the window manager takes down all running applications: Yes, because the compositor IS the server, window manager AND compositor at the same time.
• You cannot do a lot of things: What, like allowing Windows to see your keystrokes, which makes developing a keylogger absolutely trivial?
• There is not /usr/bin/wayland: Yes, because Wayland is a set of protocols, which a bunch of projects can implement as few or as many of, as they see fit, thus avoiding the issue of "unmaintainable mess" that has plagued Xorg for years.
• It offloads work to the window manager: Again, yes, that's a part of its structure: do the protocols, then let the compositor implement them. That way, you have multiple implementations running simultaneously that are well integrated with their window managers and thus more efficient and performant. It also means that when a compositor suffers from too much cruft, we can just make a new one, while application developers wouldn't really have anything to change because if their application works on Wayland, then it works on different compositors (unless it is made specifically for GNOME, or specifically for wlroots, like wlr-randr)

....so what works on DE 1, doesn't necessarily work on DE 2: True, because oftentimes, it doesn't need to. Not implementing features can lead to a more lean and streamlined software solution. However, sometimes features are necessary and only implemented in some compositors. This usually happens because the universal solution is not ready. KDE are often known to do this with Plasma and KWin.

• Wayland breaks screen recording applications: Correction: The following screen recording applications were not built to support Wayland (because Wayland is new to them or they just decided not to, or they were either too busy or too irresponsible enough to realise Wayland is coming, and has been for over 10 years. In defence of the devs, they probably wanted to make sure Wayland will become stable enough, but it has been the default even on Debian for many years now, so....

In terms of the applications, I'm not aware of many of them, and for this sort of application, I'm sire alot of work is required to change the graphical backend, so I understood that some smaller projects gave up, but OBS has been working on Wayland for quite a while. Is it perfect? I don't think so, but back when Brodie Robertson was using Hyprland, he was recording his videos using OBS. This article is quite outdated.

• Wayland breaks screen sharing applications:

As the update shows, Jitsi now does work on Wayland.

Zoom only seemed to work on gnome, BUT if you open up the Link to the zoom issue and read through the comments, there is clearly a person that clearly states that they changed /etc/os-release from PureOS to debian and it worked for them, all because of some pointless limitations enforced by the Zoom developers. As the person posting the issue states "Currently, the zoom application has put an arbirtrary restriction on screensharing so it ONLY works on GNOME, when the api being used works on all wayland desktops." Read that again. It's a pointless restriction put there by the Zoom team because they couldn't be bothered to test anything non-GNOME.

And the last issue is a problem with the article writer's own appimage. I don't know about that one.

• Wayland breaks automation software

As stated IN YOUR FACE, it is an application that works on X11 only. Yes, Wayland is not made to use such applications, but it doesn't mean they can't exist. Every heard of ydotool (remember that name)? Now you have.

Next up, we have 3 issues about GNOME and KDE global menus (1 for GNOME, 2 for KDE). From the little I know about global menus and using these projects, as well as considering that they are both incredibly stable on Wayland and Fedora KDE will be dropping Xorg completely, I think it's safe to assume these issues have probably been fixed. Please correct me if I'm wrong.

• Wayland breaks AppImages that don't ship a special QT plugin: Great! Just ship the plugins then! Problem solved! Also, quote from the article: "However, there is a workaround: "AppImages which ship just the XCB plugin will automatically fallback to running in xwayland mode" (see below)."
• Wayland breaks Redshift: Once again, a program built for Xorg doesn't always work on Wayland. Especially if it works with the compositor, like a colour temperature control application, or a wallpaper setter. The article quotes that "Redshift does not support Wayland since it offers no way to adjust the color temperature" which is not true, as proven by Redshift alternatives like Gammastep.
• Wayland breaks global hotkeys: I present to you: Hyprland (where you can get global hotkeys). Now, it is normally not allowed by design, as a security measure, but Hyprland has not allowed that to stop them from implementing a solution where you can choose keys that will be passed on to the application. Boom, problem solved. Unfortunately, it doesn't seem to be implemented anywhere else, as far as I know.
• Wayland does not work for XFCE: Come back to me in late 2024 after XFCE 4.20, which will introduce Wayland support, has been released. Also, wiki.xfce.org/releng/wayland_r…
• Wayland does not work properly on Nvidia Hardware: It keeps on getting closer but is not there yet, or so I've heard. Apparently, the issue is with the proprietary drivers, as noveau works well. But I use AMD, so I'm only working off rumours and opinions here.
• Wayland does not work properly on Intel hardware: Again, I'm using AMD, so I can't confirm or deny this, but considering the Intel drivers are open source, and I've heard about many, many improvements made on the Intel side of things, I think it would be reasonable to assume it has been fixed.

Edit: As multiple Intel users have pointed out in the comments, there seem to be no issues on Wayland with Intel hardware.

• Wayland prevents GUI applications from running as root: This one has been crossed out as the article writer admits there is a solution
• Wayland is biased towards Linux and breaks BSD: Arguments seem valid, and I'm guessing, are correct. This one is likely true and will remain so for the foreseeable future.

Edit: And yet, it seems that there are Wayland compositors for FreeBSD, so the above might only be true for OpenBSD and others.

• Wayland complicates server side decorations: From what I've heard, this is true, mainly something to do with some GNOME agenda, as the article states. I think that one is true.
• Wayland breaks windows raising/activating themselves: The linked issue is closed and seems to be resolved. There is a mention of a WIP protocol at the time (2019) that woukd fix this. I had difficulty following the discussion, but I think this has been fixed.
• Wayland breaks RescueTime: Because RescueTime depends on X11-only tools like xprop.
• Wayland breaks window manager: What you're describing is Wayland breaking X11-only tools for doing various tasks in a window manager. They are X11 tools, so of course they don't work on Wayland. I'm not sure if there are alternatives, but I'd guess there probably are. I know for a fact that Xrandr has alternatives like wlr-randr and kanshi for wlroots.
• Wayland requires {instert WM here} to implement Xorg-like functionality:Yes, it does.

Quote from article: "As it currently stands minor WMs and DEs do not even intend to support Wayland given the sheer complexity of writing all the code required to support the above features. "

DEs: GNOME, KDE, MATE, XFCE, Cinnamon, Budgie, Enlightenment, and recently even Pantheon have either announced to start work on, have started work on, or already support Wayland.

Window managers: Qtile is doing it. Xmonad wants to hire a dev to do it. Dwm has a spiritual successor called dwl. i3 has a drop-in replacement called sway. Openbox has 2 spiritual successors called labwc and waybox. Now you might notice one of the biggest WMs is missing on here: AwesomeWM, which is such a shame. The Awesome devs have said they would be okay with someone taking on that challenge (which has already been attempted, as evidenced by the existence of way-cooler), but it seems that they wouldn't do it themselves.

As for the projects mentioned in the article, (JWM, TWM, XDM, IceWM) they are too small and obscure, and will likely fade away with Xorg.

• Wayland breaks _NET_WM_STATE_SKIP_TASKBAR protocol I don't know about that one, ao I'll assume it is still the case. Edit: Ignoring the fact that the link is broken, it basically just links to a docs change where skipTaskbar is marked as unsupported on Linux. Link: github.com/electron/electron/p…
• Wayland breaks NoMachine NX The link points to a page that has this marked as "SOLVED, Released in version 8" so I'm guessing it has been solved.
• Wayland breaks Xclip: As you said it yourself, Xclip is an X11 application, so it doesn't work on Wayland. Of course it wouldn't work on Wayland. With Wayland, we're trying to prevent what happened with Xorg from happening again, or am I wrong?

Edit: As pointed out by some people in the comments, there are also alternatives to xclip like wl-clipboard.

• Wayland breaks SUDO_ASKPASS: That link seems to point to the way this issue has been resolved so I don't see your point.
• Wayland breaks X11 atoms: I lack knowledge on the topic so will assume this to be a valid argument
• Wayland break games: I'm 99% sure you can disable Vsync??? But I'm not a gamer. Also, WINE on Wayland is getting better and better. Soon enough, I hope the subpar performance will become better performance (when compared to Xorg)
• Wayland breaks xdotool: Well, yes. There is ydotool, but you're looking for a 1-to-1 replacement and I'm not sure if ydotool fits the bill for that.
• Wayland breaks xkill: Well, yes. Again. It is an X application, so of course it does. Though for some reason I remember it working once on wayland. Must have been an xwayland app, or maybe I'm just misremembering this.
• Wayland breaks screensavers: Yeah, that seems to be the case.
• Wayland breaks setting the window position: That is a WIP for Plasma, not sure about any other projects, so assume true for anything else.
• Wayland breaks color management: Not anymore. That is being actively worked on.
• Wayland breaks DRM leasing: While not rhat familiar with the issue, my understanding of the topic is the article is correct: not all compositors support it.
• Wayland breaks in-home streaming: Not familiar with this, so will assume true.
• Wayland breaks NetWM/EWMH: Yeah, that seems to be the case.
• Wayland breaks window icons: Yeah, that seems to be the case, as said in the article, when no .desktop files are used.

And that concludes my response to this article based on my fairly limited knowledge on the topic. If I got anything wrong, please, please let me know. As you can see my knowledge is quite limited, and as such, any corrections (preferably backed up with evidence) would be appreciated

Think twice about Wayland. It breaks everything!

Think twice about Wayland. It breaks everything! GitHub Gist: instantly share code, notes, and snippets.

^Gist

Sensitive content Reveal/hide

PipeWire 0.3.81 (2023-10-06)
This is the first 1.0 release candidate that is API and ABI compatible
with previous 0.3.x releases.

Highlights

• jackdbus support is now enabled by default.
• IRQ based scheduling in ALSA was improved and enabled by default for
  Pro-Audio profile. It will also link the pcms together to get lower
  latency. This now matches what JACK does and results in equal latency
  for Pro-Audio profiles.
• Support both old and new versions of webrtc-audio-processing to make
  the transition easier.
• Forced quantum changes by nodes or metadata will now also force a
  suspend and resume of the graph, like the rate changes to make sure all
  nodes adapt to the new quantum. This is important for Pro-Audio nodes
  that need to reconfigure the hardware to a new period in IRQ based
  scheduling.
• Fix a regression in regex parsing.
• Many bugfixes and improvements.

PipeWire

• Jackdbus is by default enabled now. The idea is that when jackdbus is
  installed, the real libjack.so is in the path and we can become a
  real JACK client.
• Forces quantum changes by nodes or metadata will now also force a
  suspend and resume in the graph, like the rate changes to make sure all
  nodes adapt to the new quantum. This is important for Pro-Audio nodes
  that need to reconfigure the hardware to a new period.
• The stream now has an EARLY_PROCESS option that can be used to implement custom buffer fill levels. (#3480)
• Fix a regression in regex parsing. (#3528)
• Fix a bug in position reporting in the driver node. (#3189) (#3544)
• Destroying a link will now recalculate the graph correctly.
• Fix the rate comparison for finding the best rate in the graph.
• Use malloc_trim() when available to release memory. (#1840)

Tools

• pw-cat now supports DFF DSD files.
• pw-cli avoid some NULL derefs in some cases.

Modules

• The RAOP sink has seen some cleanups and improvements. It will now ask
  for feedback every 2 seconds to keep some devices alive.
• A bug in filter-chain was fixed where it would fail to apply the gain
  when mixing just one source.
• The filter-chain can now pass the stream volume to a control in the
  filter-chain graph. (#3434)
• Improve volume handling in RAOP sink.

Pulse-server

• Some cleanup in the pending_stream handling.
• Fix a regression in the event emission code where it failed to emit
  a changed event when a node was linked. (#3522)
• Lower the realtime priority of pulseaudio clients.
• Set pulse.module.id on the echo-cancel streams. (#3541)

SPA

• Support both old and new versions of webrtc-audio-processing to make
  the transition easier.
• The ALSA driver now does the sync of all followers directly from the
  wakeup event. This results in more stable rate matching.
• IRQ based scheduling in ALSA was improved and enabled by default for
  Pro-Audio profile. It will also link the pcms together to get lower
  latency. This now matches what JACK does and gives equal latency for
  Pro-Audio profiles.
• GNU/Hurd support was added.
• Some improvements to passthrough handling.

Bluetooth

• Improvements to the codec handling when PipeWire is used as Audio
  Gateway.
• Adapt to new Bluez API for BAP devices.

JACK

• When the jack library is set in the default library path, avoid using
  LD_LIBRARY_PATH because this can cause confusion.
• Handle clearing the latency on a port.
• jack_property now always manages to actually change the metadata because it waits for a roundtrip before exiting.

0.3.81 · PipeWire / pipewire · GitLab

PipeWire 0.3.81 (2023-10-06) This is the first 1.0 release candidate that is API and ABI compatible with previous 0.3.x releases.

^GitLab

Conceptually I can understand that Termux cant take a photo or video from a camera device because it doesnt have access to the camera drivers that Android has....

...except that the Termux API does allow you to take a photo. So why is video off limits?

The full error for anyone having issues with the screenshot is:
Installation Failed
Bootloader installation error
The bootloader could not be installed. The installationc ommand
grub2-install -target=i386-pc -recheck -force /dev/nvme0n1
returned error code 1.

Context:
I've had a hell of a rough time trying to install linux on my system, I've tried Pop, 2 versions of Ubuntu, Mint, and now I'm trying Nobara, and it's the first one that failed to install (I've mostly had video driver issues with the others.) My current disk situation is kind of a mess, I have 4 in the system:
1. ~15 year old OCZ SATA 128GB SSD (windows/boot)
2. ~10 year old WD SATA 512GB SSD (windows libraries like pictures, documents, downloads, etc)
3. ~6 month old Samsung 990 EVO 2TB M.2 NVMe SSD (games installed from windows)
4. ~5 year old BPXPro 1TB M.2 NVMe SSD (previous Ubuntu install that I had other issues with)

#1 is my boot drive and has the bootloader on it (when I want to boot ubuntu I hit F11 and select the second entry for that drive in the menu.) Previous distro installs have had no problem installing right over top of that and disk #4, but for whatever reason Nobara has failed to install the boot loader and I have no idea how to even begin to resolve this. I've done some searching and only found results with similar situations that aren't quite the same, it seems this is commonly an issue with linux installs into partitions of a drive that is shared with windows, but that's not what I'm doing (at least not for the main install, I guess that is kind of what it's doing with the bootloader?)

I can manually erase disk #4 if that would help, but is there some way I can manually go in and clear out the old bootloader (without messing up the windows install/boot)?

Other specs in case it's relevant:
* Ryzen 7 3800X 3.9GHz 8-core CPU
* 32GB DDR4-3200 RAM
* Gigabite Vision OC 12 RTX3060 GPU

As the title says I am trying to get my handbrake to recognize as a joystick so I can use it.

Running Arch.

This is the device in question.
amazon.com/dp/B07SPVY2WL

It shows up with lsusb as the following.
Bus 001 Device 006: ID 1021:1888 ZSC ODDOR-HANDBRAKE

Device info from cat /sys/kernel/debug/usb/devices
T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=04 Dev#= 6 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=1021 ProdID=1888 Rev= 1.14
S: Manufacturer=ZSC
S: Product=ODDOR-HANDBRAKE
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=01 Prot=05 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=10ms
E: Ad=01(O) Atr=03(Int.) MxPS= 64 Ivl=10ms

I found this bit of information but it's related to openSUSE and is quite old but I'm hoping it might help.
spinics.net/lists//linux-input…

It doesn't show up in /dev/input/...

Any ideas on how I could get this thing recognized so I can use it?

Update 1:

I got connected with someone at the Simracing space on matrix per the advice from @lemonuri@lemmy.ml and they helped me to get it working. Here is what we did.

Create the file 99-handbrake.rules in /etc/udev/rules.d and add the two following lines to it.

SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="1021", ENV{ID_MODEL_ID}=="1888", RUN+="/bin/sh -c 'echo 1021 1888 > /sys/bus/usb/drivers/usbhid/new_id'"

SUBSYSTEM=="input", ATTRS{idVendor}=="1021", ATTRS{idProduct}=="1888", ENV{ID_INPUT_JOYSTICK}="1"

This forces the device to usbhid as a joystick whenever it is plugged in and recognized.

Run the following command to reload the device rules if you don't want to reboot. Otherwise you can omit the command and reboot.

sudo udevadm control --reload

It now shows up and is working.

So the device was registering a button at the end of the pull and showing up as an Xbox controller while not recognizing the axis being moved so it was all or nothing.

I installed protopedal and following advice created a dummy device which remapped the inputs so that it registers the analog input only which worked.

protopedal --name "handbrake" -b JOYSTICK -a THROTTLE -s 0:THROTTLE -a Y --no-auto-buttons --no-auto-axes /dev/input/by-id/usb-ZSC_ODDOR-HANDBRAKE-event-joystick

Update 2:

All credit goes to JacKeTUs for his work on helping me out. He is making/made the driver for this. It may go into AUR for Arch users, so if anyone ends up looking for support for this handbrake you can find the source at the below link.

github.com/JacKeTUs/hid-oddor-…

This will install the driver (currently it needs to be loaded after running sudo make) and the udev rule. It eliminates the need for protopedal but does require launch options to be set.

SDL_JOYSTICK_WHEEL_DEVICES=0x1021/0x1888 %command%

Update 3:

Latest push eliminates the need for steam launch option and removes the button from the device.

Any website that implements ActivityPub APIs properly can federate with other sites as part of the fediverse.

In the light of the above ☝️ statement and in the context of the given lemmy post, l am presenting three websites as an example :

zessa.in/

urthy.in/

1ness.in/

Can such websites be created and made to federate as a part of the fediverse ?

1ness.in

Discover guilt-free flavor with our vegan dairy alternatives! Creamy milk, decadent cheeses, and rich yogurts redefine delicious!

^{1NESS - Come Together.}

EDIT

So anything I said below was all a lie, it turns out that the issue was kde and my monitors, which are 240hz. I swapped to gnome and the issue disappeared, and then I installed bazzite kde on a second drive and the issue reappeared. Setting my refresh rate to 120hz stopped the flickering and upon setting it back to 240hz I do notice an appreciable decrease in artifacting. I have no idea what to do with this information, but if anyone is experiencing this try just decreasing your refresh rate for your monitors.

Howdy,

Just installed Nobara again and am trying to figure out why this is happening. I think it's a firefox thing since I haven't seen it happen in any other application; basically anytime I do a lot of scrolling, the firefox window breaks down and I can see my desktop background behind it. It always happens in the bottom right cornerish part of the window. I'm up to date on all updates as far as I'm aware. I did some googling and checking out the nobara discord but I couldn't find anything related. I tried recording my screen via spectacle to show the issue, but it wouldn't capture the issue.

Any help would be appreciated; I am a linux beginner so dumbing down any info you have would be nice. Thanks!

I recently wiped Windows in favor of CachyOS, and it's been lovely! However, I have one outstanding issue that I can't seem to figure out.

To start, I have a Gigabyte B550I Aorus Pro AX motherboard. I followed the guide on the Arch Wiki for my particular chipset.

I still can't seem to control my cooling fans.
* I have lm_sensors installed
* I installed CoolerControl
* I used modprobe it87 force_id=0x8628
* I tried adding the .conf files to /etc/modprobe.d/ and /etc/modules-load.d/
* When the steps above didn't work, I installed the it87-dkms-git package

No matter what I've tried, the only time the fan sensors get detected is when I also specify acpi_enforce_resources=lax in GRUB. From what I barely understand, that's not an option you want to leave on permanently, but perhaps y'all know better or have other ideas.

If it helps:
* Motherboard: Gigabyte B550I Aorus Pro AX
* Latest CachyOS kernel
* Boot: GRUB

Edit: I have a semi-solution.

sudo modprobe it87 force_id=0x8688 ignore_resource_conflict=1

Also note that it should have been 0x8688 in my case, as revealed by sensors-detect.

Edit 2: Added

/etc/modules-load.d/it87.conf
it87

And

/etc/modprobe.d/it87.conf
options it87 force_id=0x8688 ignore_resource_conflict=1

I think this is the way we should communicate, when presented with the question on how to get on Mastodon:

Copy paste from the link:

How do I use Mastodon?

• Download the Mastodon app from the Apple app store or Play store.
• Create an account (just like Twitter or any other social media)
• Follow people, and get posting.

Why do tech journalists say it’s too confusing to catch on?

I have no fucking idea.

EDIT for clarification, don't take this too seriously:

This “guide” is a bit of a joke made out of frustration. If you actually want to know more, including why I feel it has potential to free us from the dystopian hellscape that is modern social media, here is the “real” guide to Mastodon. It still uses simple language (and has lots of pictures!):

Please share widely

An EXTREMELY Simple Guide to Mastodon

Did somebody tell you it's too confusing?

^{Justin (Stay Grounded)}