emeraldsnorlax/manjarno

Why you shouldn't use Manjaro

manjarno

#39 (comment)

manjarno's Issues

project future

Incorrect date: Month is off by one

Thanks for raising awareness of Manjaro's flub-ups! One is a mistake, four times is chronic. 😞 People should be able to trust their distribution, whichever one they use — so thanks for pointing this out.

---

The certificate expired yesterday... while the counting timer shows the right information, the date is off by a month. Most likely: Thanks, JavaScript!

Screenshot:

However: Today's date is 2022-08-18.

It's probably related to Date.getMonth returning current month as a number between 0 and 11, instead of 1 - 12.

EndeavourOS Installer

Hi,
It may be worth reconsidering the short summary about EndeavourOS as an Arch alternative. Compared to archinstall, Calamares - which is Endeavour's installer - offers many more options. These include package selection, handcrafted package groups, automatic partitioning, hardware detection, and timezone mapping. These make the install process quite a bit easier for newer Arch users.

In my view, Calamares is a much more moderate experience that more users can understand. A good way to put it is in terms of the Windows power-user. Most of them couldn't use a CLI installer to save their lives, but they can usually make their way through a GUI installer like Calamares... or Windows 10. For this reason, I believe a slight revision of the Endeavour section may better reach the goals of the project. It also helps to meet Manjaro's original goal of making Arch easier. Please let me know if this is agreeable or not - I may look like a bit of a shill. Thanks!

spelling error

Maintaing a distro is commendable, and that alone takes credit. should be Maintaining

Dropdowns arent obviously clickable

Style them to look like buttons

Funding problem is false claims

On the page you have the following statement:

Funding

Manjaro has had a controversy with their treasurer. Phillip Muller (Manjaro team lead) had purchased a laptop for €2000, and the treasurer asked to clarify his purchase. This ultimately led to the treasurer being removed. Isn’t the whole point of a treasurer to ensure fair and efficient use of donation funds?

Maybe recheck the claims that I purchased a 2000 € laptop and see who actually did: https://opencollective.com/manjaro/expenses/22477 Also it was not approved by me in the end, rather by another member of the financial committee from the Manjaro Linux project.

The original post by Jonathon can be found here: https://redd.it/hwo33h

Also, Jonathon was just the initial admin of the groups he created on the fiscal hosts. The actual treasurer is on the fiscal host side to finally approve any spending based on the policies a project has.

# Expense Policy (v. 0.10) 17.Aug.2020
1. The goal of the Manjaro project is to provide a Linux distribution free of charge.
2. Expenses will be covered for costs which support and progress the Manjaro project, for example and non-exhaustively:

* Travel and subsistence costs for conferences and related activities;
* Hardware purchases and upgrades which support the development of Manjaro;
* Software purchases, upgrades, and licenses which support the development of Manjaro;
* Hosting and SaaS/PaaS etc. charges related to the project.
* Setting bounties on bugs or features for Manjaro software 

3. Expenses should be discussed with members of the Manjaro Team to determine that expenses are for approriate purpose and that enough funds remain to sustain the distribution infrastructure for at least five following years. 
4. An internal financial committee of three Manjaro Team members who will rotate on yearly basis is responsible for facilitating the discussion, informing about the vote, assuring a valid vote process, fixating the validity of the vote, executing the vote decisions as fund admins on fund management platforms.
5. Depending on the amount, expenses must be approved by a vote of a certain number of members of the Manjaro Team.
For expenses < 400€ no vote is needed, fund admins will question in suspicious cases,
for expenses >= 400€ and < 1000€ three Manjaro Team members must vote,
for expenses >= 1000€ five Manjaro Team members must vote, 
in order to make the vote valid. When the number of team members changes, these numbers are adjusted accordingly.
6. When a team member notices that the minimum amount of voters have voted and the vote was in favour of the expense, the team member should make a screenshot, add a time stamp, notify the financial committee and after 12 hours the vote is declared valid by at least one of the members of the financial committee, the expense filed and approved on a fund management platform.
7. A valid vote with a simple majority in favour of the expense results in an approval of the expense.
8. The invoice for the expense should be filed at a fund management platform either by the applicant or a Manjaro Team member on behalf of the applicant, but not by any of the current internal financial committee members.
9. Normally a vote should be organized prior to any purchases being made, before being submitted to the fund management platform. If an expense is submitted before vote has been organized, internal financial committee is responsible for organizing the vote prior to approving the expense.
10. The expenses are transparent by design on the chosen fund management platform.
11. This policy can be revised and changed at any time by a simple majority of the Manjaro team. The vote for a change of the policy should be left open for 3 days.

Since expenses are transparent on OpenCollective and LFX each process can be verified ...

Some News about PINE64 and Manjaro

I think this article doesn't have anything to do with manjarno web page, but just for good read: https://blog.brixit.nl/why-i-left-pine64/

Partial quote:

In some cases the Manjaro involvement actually causes extra workload for the developers by shipping known broken versions of software and pointing to the developers for support. Which is why https://dont-ship.it/ was started.

Manjaro is for the Experienced, not for Beginner

Perhaps an addition that Manjaro isn't for beginner and their beginner-friendly claim is questionable ...

Manjaro claimed and promoted the distro to be beginner-friendly and community-driven. I tried Manjaro last year December because of this. But, I noticed that the distro wasn't beginner-friendly at all. It's for more experienced users. So their claim feels like marketing claim; I didn't notice before that Manjaro is a company though given their org domain :(

Many youtube videos or websites recommend Manjaro as a beginner-friendly distro other than Ubuntu. But, I believe new GNU/Linux users should be strongly warned that Manjaro isn't for newbie; you need to know Linux kernel, how to interface with tty or use live media chroot when the system is unbootable after an update, etc.

For your latest info that Manjaro really isn't for beginner:
https://forum.manjaro.org/t/kernel-updates-keep-breaking-nvidia-driver/98548
https://forum.manjaro.org/t/black-screen-of-death-after-update-515-rt-nvidia-drivers/101429/52
https://forum.manjaro.org/t/linux-kernel-5-15-18-2-rt28-manjaro-broke-nvidia-drivers/101549

About Manjaro and the AUR, and updates

It's important to recognize that any distribution can break, especially in the hands of those who enjoy tinkering with their systems. Damn, even my first Ubuntu installation was destroyed when I was first starting out with desktop Linux.

One of the most common complaints is that Manjaro delays packages for two weeks, but what people fail to mention is that this only applies to specific branches. It's important to take this into consideration before jumping to conclusions. For people that doesn't use the AUR, or just for an old AUR package, Stable branch is great!

The criticisms surrounding the AUR breakage problem have been blown out of proportion and lack context. In fact, problems are typically isolated to a single package, and only occur if you use core system components from AUR.

Manjaro is a good starting point for beginners who want to explore an Arch based like distro. Even if you, or me, use vanilla Arch or Arch-based.

It's crucial to exercise caution when using any Linux distribution and to avoid jumping to conclusions based on dispersed anecdotal evidence.

Thank you, and sorry for diving once again in the topic.

Since this website 25d 20h !$%&?*# up

Manjaro DDoSing the AUR second time part is falsely described

It wasn't because of any bugs in pamac it was because so many manjaro users were using pamac at the same time so they had to remove some features like sending requests on every key press . If you think sending requests on every key press is a bug then www.aur.archlinux.org has that bug.

Broke LUKS full disk encryption with "stable" update

https://forum.manjaro.org/t/stable-update-2023-03-31-kernels-plasma-5-27-lts-pamac-phosh-mesa-libreoffice/137405/2#arrow_right-2023-03-31-2

https://forum.manjaro.org/t/stable-update-2023-03-31-kernels-plasma-5-27-lts-pamac-phosh-mesa-libreoffice/137405/162

https://forum.manjaro.org/t/after-latest-update-reboot-error-no-such-cryptodisk-found/137793

they did it again

https://gitlab.manjaro.org/applications/pamac/-/issues/1135
kek

WIP asahi stuff (again)

https://social.treehouse.systems/@marcan/110049540523616625

the change was requested by the project lead from the manjaro-arm team, presumably to get the change downstream in their project so it's arguably manjaro fucking up again. It's up to you if that counts though.

Missed breakage in December 2022

On December 22nd, Manjaro's pacman mirrors were getting overwritten due to an AUR package being preferred over their own repo's because someone over at the MSYS2 team pushed a (now renamed) package with a colliding name. This was reported publicly and the subsequent fix was asking the MSYS2 people to change the package name, as well as changing the Manjaro package's name and subsequently reverting the name change when the msys2 package was renamed.

I'm tempted to make a new pacman-mirrorlist package, but I'll refrain from doing so for now

Website moving

Snorlax.cc is moving, you might want to change the link.

Add garuda to What should I use instead?

Garuda linux seems like a great distribution. why isnt it in the list?

Shipping custom (broken) Firefox theme on Manjaro GNOME

This might look minor at a first glance, but it is genuinely a problem, as it is a massive accessibility regression.

References:

• https://floss.social/@rafaelmardojai/109532714277650579
• https://www.reddit.com/r/firefox/comments/zn589n/firefox_updates_it_self_and_now_my_tab_bar_looks

Manjaro accidentally removed packages like iputils, filesystem and etc from iso

yesterday and today we had someone in our discord telling us ping was not found on manjaro about 4 hours later he linked to https://forum.manjaro.org/t/why-is-iputils-not-installed-by-default/98160
where it was found out that base packages got removed in one of the iso releases and had to be restored via this commit https://gitlab.manjaro.org/profiles-and-settings/iso-profiles/-/commit/07ffbb081ba4f38af5b73908d27afcd5c6906e9d

Another Expired TLS Certificate 2022-11-05

FYI:
https://forum.manjaro.org/t/expired-ssl-certificate-on-archived-forum-manjaro-org/126131

Rushing Asahi out the door - background story

The following text is found on your website:

Rushing Asahi out the door

In their attempt to get Asahi Linux out (and support Apple Silicon) as soon as possible, they ended pulling the latest PKGBUILD without talking to the devs. This has resulted in them shipping potentially broken kernels to end users.

Still though, that’s besides the main problem. It was only about 3 days ago this video came out, in which a DE is working for the first time. Not only is it still in a state far from prime-time, but compounded with the tweet above they didn’t even bother trying to speak with the devs of the project about its current state.

First of all I'm not in the mood to rush out things. It took me some time and 3 image builds to get the OS working on my M1 Air.

How did it happend

Using the latest Version of the PKGBUILD is more or less common if you deal with Arch Linux based software. Also the released version of the image had a disclaimer:

DISCLAIMER: THESE ARE EXPERIMENTAL IMAGES ON WHICH WE TEST ON HOW TO BUILD FOR APPLE SILICON. THESE IMAGES ARE BASED ON ASAHI 6.0 KERNEL SERIES. USE THIS AT YOUR OWN RISK!

These are initial images for Apple Silicon devices starting
with the 2020 M1 MacBook Air.

A huge thank you goes to the Asahi Linux project of which we use
their tools slightly modified to support Manjaro Linux ARM.

All Apple M1 Macs are in scope, as well as future generations as
development time permits. The first target will be the 2020 M1 MacBook Air.

As soon as the Twitter post was out I reacted and pulled the images and installer from sourceforge. They are now stored at an unlisted storage server for internal usage after rebuilding the image with the packages available that time of asahi repo. Before I update my PKGBUILDs I check if those changes also match the binary repos of Asahi. Also the issue with the M1 Ultra was given by our first public release, but was never our target to begin with, as we only list devices we actually have tested on our end with Manjaro ARM.

Additionally Asahi upstream started a while ago to branch their git repos for development, similar to Arch. This helps distros to adopt much easier and follow on what might coming up next.

Sure establishing a connection with Asahi to begin with would have been better. The email I had sent to Marcan on the day I pulled the initial images and explained what had happened was never answered.

On 02.10.22 21:13, Philip Müller wrote:
Hello Hector,

seems the initial image release of Manjaro on Apple Silicon wasn't as
attended to be. There were some issues with it introduced by me on our end.

Kernel

I pulled all images which were public available. Based on the statistics
around 200 people seem to have downloaded them till the moment I deleted
them.

The first image had some issue with init and Calamares branding and was
therefore not bootable for a normal user. The second image fixed that
and booted fine on my M1 Air. So I decided to tweet about it. That might
have been to early, though.

Thx for pointing out that there are issues on the M1 Ultra on the 6.0
kernel series, which we can't test from our end. I pulled the kernel
from our repos and replaced it by the working 5.19 rev5 kernel.

I'll try to connect with you on when a kernel can be updated.

Internal Images

I moved the current internal images to our SCRUBBED FOR LEGAL REASONS, which doesn't
list the server folder structure. Here the links to important files:

SCRUBBED FOR LEGAL REASONS

I'll test the image from scratch again on my end. So far only I have an
Apple Silicon device within the Manjaro ARM project. Therefore I'll only
been able to test on the Air for now.

Is there an easy way to just flash the new images to the SSD or is the
remote installer approach the only way for now? Any documentation on
that would be highly appreciated.

Collaboration

Our ARM developers what to connect with and collaborate to the Asahi
project. We will create PRs to related projects as soon as we think to
have an improvement for those. Here is one example I added on our end:

AsahiLinux/asahi-alarm-builder#5

We respect the work from you and your whole team of Asahi project.

Hopefully we can press Stop, Pause, Rewind and start the Apple Silicon
support via Manjaro ARM on a better approach after more internal
discussions and testing between both FOSS projects.

On a personal note: I like to apologize for any issues caused by too
early tweeting from our end on the official Manjaro Twitter handle.

MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING

Date: 20230216
Time checked: 17.50 CET
https://aur.manjaro.org/packages-meta-ext-v1.json.gz

MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING

Image 404

The new SSL expiry images lead to 404 - https://manjarno.snorlax.sh/expiry-2022-08-17-cert.png

Manjaros "stance" on "patent encumbered" codecs

• Exact date this sh*tshow began: 2022-12-06
• disabling of "patent encumbered" codecs
• reenabling of aforementioned code
• redisabling of aforementioned code
• This explanation is all about copyright, which is not the same thing and has nothing to do with this stupidity.
• Manjaro team member recommending migration to Arch.
• They clearly don't know what they're doing.
• Even Debian still ships them.
• Video by Brodie Robertson. TL;DR: if you don't know why you're doing something, stop doing it.

time to reset the timer

https://twitter.com/AsahiLinux/status/1576356115746459648?t=MDFPzS3AQfU-qcoe4V9RnQ&s=19

https://twitter.com/marcan42/status/1576414477272387584?t=lnI2ypCUSMZLDaYYyaa4cg&s=19

Deleted Manjaro Archived Forum

The archived.forum.manjarno.org has been deleted. I believe the section with the TLS certificate expiry for this archived forum domain should be consolidated with this new information, or just removed.

The reason why it is removed can be found in:
https://forum.manjaro.org/t/am-i-the-only-one-getting-expired-certificate-warning-on-archived-forum-manjaro-org/126049