​

So most of my life, for the past 23 years or so, I have been using Windows. And it has worked fine for me. Most of the programs, most of the things I was familiar with, work on Windows.

But as I later learned, Linux though is quite hard to learn for a Windows user, is *super customisable* and there are several features which are just not available on Windows. 💻

Windows time by time uses more RAM, more resources, and more processes on each login compared to Linux which barely uses anything. ⚡

I first used *Linux Mint* some 1-2 years ago. Before that, I had installed *Ubuntu* from a free CD that came with my UPS back in 2009 😅 - and that completely wiped out my system. That was not a good experience at all.

Now, I bought a new refurbished laptop, a *Lenovo T14 Gen 1* and Windows 11 came with it. Even the LTSC experience was not that compatible because I only had 8GB single channel RAM and it was not working that well with my Ryzen CPU. I am in the process of buying RAM but it's quite pricey these days.

So I started thinking about installing some version of Linux. I started with Android distros like *Prime OS, Fyde OS*, even *Chrome OS Flex*... but none of them were compatible with my system. Sometimes Wi-Fi didn't work, sometimes the mic settings were off - actually the microphone didn't work on any of them. 🎙️❌

As I searched, even with AI and ChatGPT, it told me there were certain reports that *Manjaro worked completely fine* with my system and even the microphone was working perfectly. So I took the risk and installed Manjaro.

I had several problems at first. I was not able to configure how to use a file manager, the toolbar was not that great in Dolphin, even on PCMan File Manager - I tried so many of them but none worked quite well. As I had a habit of using the *GUI rather than Command Line*, I was having some issues. 🤯

I tried and tried and almost 15-16 days passed with me trying daily and messing things up and then recovering them. But eventually, I started to like it!

The processes are very few on startup, the battery life is quite good 🔋 and after installing things, I am thinking of using CPU or TLP to further boost the battery life. And I think Linux is quite capable, Manjaro is quite capable of doing that.

*So I am loving it. I just love my Manjaro desktop!* ❤️🐧

Hope you will also have a great experience with it. So welcome, congrats - I am also now a part of the Manjaro family! 🙌

I dont know if its KDE or manjaro, but I noticed that some processes like kioworker, discover and even sometimes dolphin taking like 4GB of ram. My 16GB seem to run out with just VS Code and a few brave tabs and dolphin. Anyone else? Is there a fix?

As of today the last stable update was Sept. the 7th. Comparing to my long-run observations it is quite long time period of silence in terms of stable updates. I am not used to this pattern of Manjaro stable branch behavior. Is my feeling right, if yes where are the reasons?

Latest PHP updates is quite separate story.

I don't really follow what's going on, but there hasn't been even security updates in a long time. Meanwhile we're in the bugpocalypse and every day there's some major new vulnerability announced in pretty core libraries.

I've loved Manjaro for years, even through all their weirdness. But I'm getting worried that maybe it's over now?

I've been using it to install NVIDIA drivers on NVIDIA-equipped machines for years, and somehow I still never know which driver version I’m going to end up with.

Yes, I know mhwd works with hardware profiles, not individual drivers. I get the concept. But surely it wouldn’t hurt to tell users which actual driver version is hiding under the hood of a profile?

Case in point: I've got an old GTX 970 lying around (bless its 3.5GB+0.5GB heart). I run mhwd -l and get a list of profile names - video-nvidia, video-nvidia-470xx, etc. - and absolutely zero indication of:

• which one actually targets Maxwell-era cards properly,
• what driver version number I’ll end up with once it’s done,
• or whether “the latest profile” is even still appropriate for a card this old (spoiler: NVIDIA's own 580.x branch is the last one that supports Maxwell/Pascal/Volta at all — after that it’s legacy-only forever).

So I'm sitting there doing the actual detective work myself — checking NVIDIA's support matrix on the side, then crossing my fingers that mhwd’s profile mapping agrees with what I just read — instead of the tool just telling me "hey, for this GPU, here’s profile X, which installs driver version Y, and by the way it's EOL in N releases." A simple mhwd -li with the resolved package/driver version next to each profile name would save me this little ritual I’ve apparently been doing for over a decade without ever questioning it.

The graphical panel doesn’t give you much more either — the video-nvidia profile entry is just as sparse there. So: how do you all deal with this when installing on your own NVIDIA cards? Have you just gotten used to mhwd’s minimalist way of telling you (almost) nothing, do you handle it differently (manual pacman, checking NVIDIA’s site first, something else entirely), or is it maybe time to throw a few ideas at the devs?

Am I missing something obvious here, or have I been using mhwd wrong for 12 years straight?

I was feeling bored and had wanted to try something new for a long time, especially since my HTPC had a setup architected with LLM assistance and I was afraid to mess with it, which I needed to overcome with autonomous and unassisted recreation.

I've always been fascinated by CachyOS's reputation and its optimizations. But I didn't want to immerse my HTPC in it, so I tested it on my laptop. The installation was manual, as I always do with any distro. My laptop has an x86v4 CPU and I enabled those repositories with the official script, finished the installation and had a terrible day. I tried to keep it running, but Plasma was slow, clicking on various configuration windows took 3 to 5 seconds to open, and there were a few other bugs here and there. In the end, I didn't have a better experience and went back to Manjaro Testing with a manual installation (as always) and things went well again. So I just wanted to say a big thank you to everyone who makes Manjaro possible.

NOTE: This post is in appreciation of Manjaro; my bad experience with CachyOS is entirely my own responsibility. I believe the CachyOS team did an excellent job, which is why I appreciate their efforts and why I wanted to try CachyOS.

GNOME daily ISOs are back! There was testing update a few days ago.

As for Stable, we're still like…

I need to create a local repository on the Majaro distribution, and I need to make the commands and help understandable. How do I do this step by step? Please help.

sorry for the image i couldnt copy it its running in weston but not launching

Recently I visited my family and found they are still using computer with Manjaro on it. No big surprise, since I installed it a couple of years ago. The box had been sitting untouched for about a year, so as you can imagine, the list of updates was huge.

I didn't have enough time to start update, but usually big updates don't scary me. I click here, click there, fix the package signing keys if something goes wrong. I generally don't pay much attention to it. It's just routine. But I wonder, maybe there's another way to do it?

• Do you update straight away with pacman -Syyu, or do you do something first? I've heard whispers about refreshing the keyring (manjaro-keyring, archlinux-keyring) before anything else.
• Mirrors: do you run pacman-mirrors --fasttrack first, or just trust the defaults?
• Update announcements: is it worth going through the stable update threads from the last six months to check for manual interventions I might have missed?
• Safety net: I'm planning a Timeshift snapshot (maybe a Btrfs one) first. Anything else you'd back up?
• GUI vs terminal: Pamac or the terminal for a monster update like this? I suspect the terminal, but maybe I'm living under the rock. 😉

And the fun part: what's the longest gap you've ever had between updates, and did Manjaro survive it? Extra points for dramatic "black screen after reboot" stories with a happy ending. 🏆

It's getting a bit confusing to keep track of what's going on with the distro, so i would appreciate some info from people who know more than me.

- The last stable update had this note in the forum post:

This also sets Manjaro Linux into a frozen state for a while until we have finished migrating our Gitlab Instance over to a new Forgejo Instance.

Anyone knows how this is going? There have been no new package updates on the Stable and Testing branches for almost a month now. I assume this is connected to the migration. Is there any ETA on that? I haven't been able to find any more info.

- Phil M. has been posting this on all the recent update posts:

Note: I’ve super limited time to do Manjaro these days. So expect delayed response from me or none at all …

Is that a reason for concern? I mean, is it even safe to use Manjaro right now? A declaration like this coming from (who I suppose is) the lead developer doesn't exactly inspire confidence.

- A couple of days ago, there was some new development on the Manjaro 2.0 Manifesto thread. It looks promising, but I'm still not sure what exactly it means for the distro and if/how it's connected with the previous two points.

Posting here in case someone else searching might find it more easily and with less troubleshooting than it took me.

The current version of krfb (KDE's built-in Desktop Sharing VNC server application) is broken. It refuses to bind to ports. Any clients attempting to connect will be rejected because the destination will not be listening.

Here's a thread about it I found: https://discuss.kde.org/t/krfb-on-wayland-never-opens-a-vnc-listening-port/50054/5

Which below links to bug reports: https://bugs.kde.org/show_bug.cgi?id=524610

You can downgrade the package to the previous version from your local package cache:

pacman -U /var/cache/pacman/pkg/krfb-26.04.3-1-x86_64.pkg.tar.zst

You can ignore the 26.8.0 version that has this bug. Reportedly 26.8.1 (which Manjaro repos don't have yet) still has this bug.

EDIT: It's not just with the Wayland binding. It's also (as in my case) while in an x11 session.

So I run an MSI thin gf63, currently my speakers don't work, but I should have the drivers for it as my headphones jack works, I don't dual boot, so I only have Linux.

The thing happened when I had to force shutdown bc my pc froze and now my speakers have no output, and I'm forced to use external accessories to hear.

I have tried installing drivers in VM, didn't work (IDK, I just hoped). McontrolCentre has no settings related to this issue. I have KDE plasma and Hyprland environments. I haven't updated my bios sense I got the laptop (2023) bc I'm too scared to do so bc I never did it and scared to do it. Ask if you need any other information,

Does anybody have an idea how to fox it or investigate a solution pls. Thank you everybody that helps.

SOLVED, thank you to everyone who helped.

I got a new HD (for storage, not for an OS), but after using GParted to format it and partition it (ext4), it's still not working.

It's detected as a regular volume on my system. And when I go into it and check Properties, the system shows the correct Capacity. So it's at least being recognized.

I cannot create folders, documents, or copy anything onto it.

For both "Size" and "Size on disk" it just shows "0 bytes (some contents unreadable)"

Edit: when formatted to btrfs, it just shows "0 bytes" for both. It is currently in btrfs.
Edit2: SMART basic health test says PASSED
Edit3: The HD is hot, so it's doing something.
Edit4: GParted now shows me a Lock icon next to the partition name. Apparently that's normal. Edit5: Two "short" self-tests have yielded "Completed without error" results.

Edit6: after using "sudo chown -R $USER:$USER /mnt/path/to/drive" on both the drive and the partition to change ownership from "root" to myself, "ls -la" tells me both the drive and the partition belong to me, the user. But when I check Properties on the drive, it says it belongs to "root"! Which tracks, because the "lost+found" folder that is visible on it when it's formatted to ext4 cannot be accessed: when I check it via Properties, it says "Error opening directory: Permission denied". It looks like the drive (or the partition) belongs to "root", and I don't know how to make it mine.

Literally every test I'm running on this disk tells me it works... but my OS insists it's got 0 bytes of usable space on it.

Or did I just forget something elementary? I don't think I did. I just formatted the disk and partitioned it. As far as I remember (it's been many years) that's always what I've done with new storage disks.

Heya, so Ive been running manjaro without any major issues, but this appeared randomly.

When Im in wine application it just randomly like double clicks (When i click instead of doing the clicking action it does the double click one).

I can always temporary fix it with wineserver -k but it gets back in some time, it looks it does this randomly but i cant tell.

Any help will be appreciated thank you.

Hi fellow Manjaro enjoyers. I stumbled upon an issue regarding my root partition. It seems like my file system being btrfs, I'll need to realocate space. But since I tried running btrfs balance and nothing seems to happen even if is display that chunks has been relocated, I'm asking for you daring help to solve this issue.

Here you can find btrfs status, Filelight screenshot with only like 105GiB used and root saying it almost full. Hope someone ever met this issue.

Thanks a lot.

[UPDATE]

So it seems like I created one way or another snapshot on the volume. Using Timeshif I was able to find these snapshot and delete it.

Hi guys i have been trying to connect my laptop to a network printer but I'm getting filter errors i have tried the KDPL driver version and ppd still nothing it worked once and disappeared. The printer is a kyocera model and it has those job accounting settings. I tried using AI but it was not quite helpful.

When my Dell Inspiron 15 7750 hard drive died, I replaced it with another Dell Inspiron, model 15 3535, a windows 11 machine. I chose not to use Windows 11, and installed Manjaro Linux along side it. From the beginning I couldn't configure the display to conform to my cataracts from 1920x1020 to 1600x900, and I couldn't get Wayland to work at all. When I installed KDE Neon, both problems went away. Another thing that I found was that, since Neon is based on Ubuntu, Dell firmware updates are made as part of the regular Neon updates.

My system is a Dell Inspiron 15 3535 with a 500gb SSD, using an AMD Ryzen 7 7730 with Radeon graphics, 16gb ram.

I've been thinking about giving another crack at running it on my manjaro install, being it's the last thing that keeps me dual booting.

I've seen a few guides but they are mostly years old, and not very detailed. I'd appreciate any first hand knowledge.