Have they fixed the copy+paste problem from the Firefox address bar under Wayland in KDE plasma yet? I’ve been holding off switching to Wayland in my Plasma desktop because of that one Firefox issue.
The messages you’re getting sound like they’re from the bootloader, so I think secure boot is not causing the problem… Linux should print some stuff right away when it loads, maybe check the architecture of the kernel you’re trying to boot, even an error immediately after loading the kernel should print something unless the architecture is so different that it’s just feeding the CPU bad instructions… Not sure how the bootloader would get installed correctly in that situation though. Is this after installation? Does the system boot from a live USB or cdrom?
You’ve already gotten great answers on what Wayland is, but as far as who should care:
Mainly developers and users with niche workflows. People with NVIDIA cards should care a little as initially NVIDIA did not support Wayland, but NVIDIA drivers are catching up so this should continue to improve. Most users should just switch when their DE switches.
This is great!! I use macOS for work but I’m sure I can get 90% of the work done on Linux now! Just wondering about GPU perfomance? Video editing is crazy fast on macOS, anyone tried on Asahi?
On top of what other said, the wayland project also maintains the wayland protocols repository which includes additional protocols that are approved by a “committee” that includes representatives from wayland protocol implementations (wlroots, kde , gnome , smithay etc). for example now they are working on color management.
There appears to be a consensus among people working on window manager implementations that X has to go and wayland is the future.
Wayland has technical benefits, if you want the nitty gritty details see this.
Basically X11 is bad IPC at this point.
Also be careful with what you read online, I see misinformation about it relatively often.
My freind got me into PC in early 2019 me and my friend built a gaming pc. Ran windows then I orginally got a raspi in late 2019 for my 3d printer to run octo-print. Later that year i saw a video about sombody using this Os called Manjaro.
Swaped out my sd card for manjaro arm, gave it a try. Few months go by its 2020. Everything locks down, i have alot of freetime. Decides to install manjaro on seprate sdd. Realize i wrote over winboot. Reinstall windows on 1st ssd. Dualboot manjaro and windows, enjoy using manjaro. Breaks multible time because I used the AUR and didnt know shit. Reinstall manjaro, uses it for a week and didnt Use the AUR. New kernal comes out bricks my install. I didnt know how to fix.
Realationship ended with manjaro, Kbuntu is new freind. Use kbuntu and really enjoy it, use it for e-learning and schooling. Learns about KVM and virt-manager Unistall windows. Use a vm for e-learning (get out of needing to turn on camera for rollcall for class because Vm has no camera for microsoft teams and teams doesnt find a camera) Uses kbuntu religously, 2 months go by arch-install script comes out. Goes back to arch, enjoys arch uses AUR breaks system again :Q. Finds out about fedora, uses fedora for a while. First time using gnome. Falls in love with the simplicy. Installs fedora silverblue on lenovo t450. Trys fedora sodalight, loves the imutablillity. Cant find a package for silverblue trys nix-env. 2021 apears i buy a lenovo w540 cant get shit to run on it (fuck you nvidia and your shitty k110m gpu) decides to try a distrobution called NixOS. Legit crack, addictive better thansex.mp3 . installs every package delcartivly (i figured out how to blacklist nvidia) install nix 23.5 soat. On main rig has a steep learning curve lots of youtube videos help. Just upgraded to 23.11 it works great only thing i cant install is W-okia Rvc voice changer for screwing with my freinds and Lightburn. Because its read only filesystem :(. Other than that everythings been great and i dont have any reason to switch from nix. I bought a t440p and installed skulls libreboot last week and Last night i was dipping my toes into gentoo. Thats neat that we had a simlar journey with manjaro LMAO.
I use Ubuntu for work and have no issues with it to be honest. I install everything via apt, I think a few things are via snap but nothing that I’ve installed directly. It’s stable and I can get on with stuff. I definitely am not a fan of the move towards snap and the app store: if I was to choose I’d go vanilla Debian.
I’m daily driving Ubuntu and my experience aligns with this.
My only gripe is snaps can break copy/paste and prevent me from saving files where I want. This might make Ubuntu unusable for people using Linux for the first time and makes no sense if you dont understand how snaps are sandboxed and how permissions work. The solution is install with apt.
The installer, system configuration programs and UI experience is really good. I argue it is a much superior experience to Windows and arguably better than OS/X. A lot less garbage being shoved down customers throats.
I checked on my machine, and out of all the packages I had on snap, only Inkscape, VLC and Slack were also available on apt. Spotify, Whatsdesk (a WhatsApp client) and Signal were among the most commonly used missing.
is this community the Peertube channel? through Newpipe i can see peertube comments (even lemmy accounts!) but on that community i see none. also the lammy client might be an issue…?
i’m really exited about this, now i’ll be able to correct people wrong on the internet like i can’t do on youtube videos!!
Lemmy “communities”, PeerTube “channels”, Mobilizon “Groups”, Kbin “magazines”, and Mastodon “Groups” are all functionally the same thing in the Fedi.
You can follow Lemmy communities on Mastodon as well, it just has a different (bad) UI. That’s why you’ll occasionally see users on Lemmy annoyingly @ 12 people in a reply.
yes i’ve interacted with mastodon users here through lemmy, but am still figuring out how i get on the other platforms from here
thanks for the clarification!
now i’ll get a mastoson client to follow communities on lemmy, hop on peertube comments from here and hopefully lurk on mastodon from newpipe muAHAHaHahHahah
am still figuring out how i get on the other platforms from here
Not sure what you mean by that. You can’t log into a Mastodon server with a Lemmy account. And I don’t think you can follow a Mastodon user from Lemmy. They’re just designed to be separate, for good reason.
Now this is what I am talking about! Just get lemmy/kbin/etc to support embedded video from peertube at least and we are getting closer to the decentralized everything app!
I love how musk is trying to make X the everything app all on his centralized network, and here we are building a decentralized everything network with dozens of open platforms and good 3rd party clients outpacing whatever musk is trying to cook.
Other integration point, but I’m less sure. Syncing peertube accounts with other instances, so my subscriptions can follow me and my comment/threads can too!
Also, the comments don’t seem to be syncing correctly between the peertube video and the community post. Peertube apparently supports using accounts from other fediverse instances, but it failed for this account I am using now.
All Canonical contributions have been relicensed and are now under AGPLv3. Community contributions remain under Apache 2.0.
So they can happily port over code from the Incus fork but Incus cannot import the code without changing the license first. It’s meant to be a one-way street. Typical Canonical.
In short incus has Apache 2.0 copyright licene that states:
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole
While AGPL v3.0 that Canonical just adopted states:
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
. . .
You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy …
Meaning if incus uses any part of Canonicals source their code can’t be licenced under Apache but rather AGPL v3.0, which pulls any other derivative of incus.
Projects which choose BSD/Apache type licences do so fully in the knowledge that their code may be incorporated into projects with different licences. That’s literally the point: it’s considered a feature of the licence. These projects are explicitly OK with their code going proprietary, for example. If they weren’t OK with it, they’d use a GPL-type copyleft licence instead, as that’s conversely the literal point of those licences.
Being mad about your Apache code being incorporated into a GPL project would make no sense, and certainly wouldn’t garner any sympathy from most people in the FOSS community.
Its not a one way street but this makes more libre thing. Canonical didnt make it proprietary to create a one way street but made it more libre by adopting AGPL license which gives users more rights to the code
Its not a one way street but this makes more libre thing. Canonical didnt make it proprietary to create a one way street but made it more libre by adopting AGPL license which gives users more rights to the code
Why is there still a CLA that allows them and only them to sell proprietary versions then? Don’t fall for Canonical’s PR bullshit.
Look, I’m usually first in line to shit on Canonical, but I can’t get mad at them adopting AGPL. This is objectively the best license for server software. Incus should also switch to AGPL for all Canonical code, and seek to have contributors license their code as AGPL as well.
I will however point out the hypocrisy and inconsistency of it, because the Snap server is still proprietary after all of this time. If this is their “standard for server-side code” then apply it to Snaps or quit lying to us.
They would have used a license like SSPL or the newer BSL for that. AGPL keeps it open.
No, the copyright owner can sell proprietary versions however they like. Outside contributions are required to sign Canonical’s CLA. Read github.com/canonical/lxd/blob/…/CONTRIBUTING.md#l… before making claims.
I don’t understand how AGPL allows Canonical to make and sell proprietary copies of this software without violating their license. That’s the only way your scenario could happen. If you’re aware of a situation where a company can do this, I’d love to learn.
I don’t understand how AGPL allows Canonical to make and sell proprietary copies of this software without violating their license. That’s the only way your scenario could happen.
“To release a nonfree program is always ethically tainted, but legally there is no obstacle to your doing this. If you are the copyright holder for the code, you can release it under various different non-exclusive licenses at various times. […] the GPL is a license from the developer for others to use, distribute and change the program. The developer itself is not bound by it, so no matter what the developer does, this is not a “violation” of the GPL.”
It requires that you make available the full source code to anyone who you give binaries too (like the GPL), but also requires you make available that source to users of the software over a network. So, someone could not make a proprietary fork of AGPL software to sell exclusively as a service. In order to provide that service you have to also be willing to provide the source, including changes, which would allow users to then choose to run that service themselves instead of being forced to pay the provider.
The full details are complex but I’ll give you the basic gist. The original GPL licenses essentially say that if you give somebody the compiled binary, they are legally entitled to have the source code as well, along with the rights to modify and redistribute it so long as they too follow the same rules. It creates a system where code flows down freely like water.
However, this doesn’t apply if you don’t give them the binary. For example, taking an open source GPL-licensed project and running it on a server instead. The GPL doesn’t apply, so you can modify it and do whatever, and you aren’t required to share the source code if other people access it because that’s not specified in the GPL.
The AGPL was created to address this. It adds a stipulation that if you give people access to the software on a remote system, they are still entitled to the source code and all the same rights to modify and redistribute it. Code now flows freely again, and all is well.
The only “issue” is that the GPL/AGPL are only one-way compatible with the Apache/MIT/BSD/etc licenses. These licenses put minimal requirements on code sharing, so it’s completely fine to add their code to GPL projects. But themselves, they aren’t up to GPL requirements, so GPL code can’t be added to Apache projects.
Great answers here. I’d just like to add that X and Wayland are not completing. In fact, most of the Xorg devs are the ones working on Wayland. You can find Wayland mentioned in the Xorg Foundation Website.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.