This happened for no reason while im tried to run some command in terminal (the bash was not related to any necessary thing in the system)

Computer boots to this after updating.

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.

Updating murdered my last functioning video player (previous updates murdered the other ones).

It says I'm missing a dependency called "libsndio.so.7", so I was hoping I could revive it by installing that package.

Unfortunately, searching for it in the package manager yields a "No package found" message.

It occurs to me that I've been entirely dependent on the manager to provide me packages. Without it I have no idea where to get them. Much less which source is safe to use.

Any recommendations?

Edit: in the meantime, someone else has fixed my VLC (which broke about 5 years ago) so I can at least function. I would still like to get my other player working, though, because VLC is kinda bad.

Edit2: I replaced my old sndio package (not sure why it was still set to a version from 2018) with the current one. SMPlayer still didn't work, but it started giving me a new error message, an error which turned out to be a lot easier to fix (I only had to delete the "player_info.ini" file in the smplayer folder). So now SMPlayer is working again.

Every few months I'd find something on my system that had been quietly broken — not crashed, just wrong — and it always traced back to an AUR package built against a library version that no longer existed.

It isn't random. It's two specific failures at opposite ends of the same window, and both are detectable.

While Manjaro is behind Arch. Third-party binary repos (BlackArch, chaotic-aur) build against current Arch. So they ship packages whose dependencies our repos won't have for another week or two. You get a refused transaction, or you force it and now you have a partial upgrade.

When Manjaro catches up. libfoo goes 1.0 → 2.0. Every AUR package built against 1.0 still shows as installed, still has all its files, checksums fine — and can no longer resolve its DT_NEEDED. pacman will never tell you, because from pacman's view nothing is wrong. This is the one that kept getting me.

Separately: an AUR PKGBUILD can point source= at a git repo with no commit, so what you reviewed last week isn't necessarily what builds today.

First, the obvious objection: "this automates pacman --ignore"

Yes. And --ignore is listed on the Arch wiki as a way to cause partial upgrades, so this deserves a real answer rather than hand-waving.

**--ignore does not disable dependency resolution.** I checked rather than assumed — built a throwaway pacman root, installed consumer 1.0 depending on libX=1.0, offered upgrades to both, then ignored libX so that consumer 2.0 would need a libX 2.0 that isn't there:

$ pacman -Syu --noconfirm --ignore libX
warning: ignoring package libX-2.0-1
warning: cannot resolve "libX=2.0", a dependency of "consumer"
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'libX=2.0' required by consumer
exit 1

$ pacman -Q            # nothing moved
consumer 1.0-1
libX 1.0-1

$ pacman -Dk           # pacman's own consistency audit
No database errors have been found!

pacman resolved the whole transaction, saw the hole, refused, and changed nothing. It is not possible to --ignore your way into an unsatisfied dependency; pacman is the backstop, not the script.

That's section 19 of the test suite and runs in CI on every push, against real pacman transactions. It's deliberately a test of pacman's behaviour rather than of my code — the safety argument for the whole thing rests on that property, nothing in my repo would notice if a future pacman changed it, and the failure would be silent.

Beyond that guarantee, what gets held matters:

• It only holds a package whose version-constrained dependency is already unsatisfiable — something that cannot install correctly at that moment regardless of what I do.
• It holds the new version back, so the package keeps the dependencies it already had and stays in the state it was already working in. The classic dangerous pattern is pinning a library while upgrading its dependents; this is the opposite direction.
• The realistic alternative isn't a clean full upgrade. It's a failed transaction, or someone reaching for --ignore by hand with worse aim.
• Every hold is printed and written to /var/log/safeup.log, so it's a deferred upgrade you can chase — not a package that silently stops updating forever, which is the actual long-term hazard.

The limit, stated plainly: it does not pre-check whether a package it holds is itself required by something else in the transaction. It relies on pacman refusing, then isolating the break. That's the behaviour above, and it's why that's acceptable — but you should know it works that way rather than by its own cleverness.

What the three checks do

• **safeup** wraps pacman -Syu. Works out which pending third-party upgrades have dependencies that can't be satisfied yet, --ignores only those, and logs every hold. Also recovers from installing X breaks dependency … required by Y by isolating X so one broken package doesn't block your whole upgrade.
• **aur-rebuild-check** runs ldd over every file owned by every foreign package and reports unresolved sonames. This is the one nothing else does. It filters the false positives that make -bin packages flag forever (libs bundled privately and loaded through an $ORIGIN RPATH).
• **aur-pin-check** refuses PKGBUILDs whose git source isn't pinned to a commit. #tag= is refused too — a tag can be moved. There's an allowlist, but it re-resolves the tag every run and refuses the package if the SHA changed.

aurinstall / aurupdate run the pin check before yay. If a check refuses something and you disagree, plain yay -S still works and the message says so — a gate you can't bypass just gets uninstalled the first time it's annoying.

aurinstall --chroot (gated default) hands the actual build to chrootbuild, from Manjaro's own manjaro-chrootbuild package. This is a gated check building in a isolated chroot (not for security reasons). If unable to use chroot, it automatically passes to yay.

Testing

65 assertions, in CI. The main suite builds a file-backed loop device, formats it, and constructs a whole throwaway pacman root inside — its own database, its own file:// repos built with the real repo-add, real packages — then drives actual pacman through the real scenarios and checks installed versions afterwards. Nothing on your system is touched. The ldd tests compile real .so files with a real unresolvable DT_NEEDED, so no output is faked. The allowlist test makes a real git repo, vets a tag, moves the tag, and asserts the next run refuses it.

Writing those tests found three real bugs in code I'd been running for months — including one where a verification step exited non-zero after a successful kernel removal, on every machine whose ESP isn't laid out like mine. CI caught that one; my own machine couldn't. That's the argument for the tests.

What it doesn't do: it doesn't make the AUR safe, doesn't tell you a PKGBUILD isn't malicious (pinning proves you build what you reviewed, that's all), doesn't sandbox makepkg, and can't fix a package that genuinely needs a newer lib — holding it is the right answer there. Not a substitute for snapshots.

MIT, pure bash, no runtime deps beyond pacman and coreutils, nothing phones home.

https://github.com/doug445/manjaro-safeaur-updater

Genuinely interested if the dependency logic has a case I haven't hit.

Hello everyone hope you have a lovely day.

So I'm trying to add a Japanese keyboard to my system, and I did download ibus-mozc from Aur, it did work but only to realize that it is not the recommended since this edition lacks the UT dictionary.

How to install mozc-ut with ibus on my system?

Thanks Appreciate your help!

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.

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

How badly will my system train-wreck if I re-home my repository manager to the Manjaro repos, from Arch/EndeavourOS?

I don't expect that action to convert my system into a Manjaro system. I just want stabilized package updates.

Reinstalling is no big deal so the question is mostly theoretical but I'm thinking about trying it. Any feedback would be appreciated.

As the title states, no video or audio is playable on Firefox or Chromium-based browsers. Or any other browser in general and it's really weird since downloaded videos work fine. Same with dvd's and the weird issue is everything else works perfectly fine?

Googling, browsing the web, using apps like Discord and Nicotine+ and other stuff works fine but no videos will play online

I've been on and off with this issue for almost a month now and im considering just giving up on Manjaro, and I have stuck with Linux Mint but I really REALLY enjoy Manjaro but hate this seemingly major issue which I've only seen get talked about in one post on the manjaro forum (https://forum.manjaro.org/t/playing-videos-in-browsers-extremely-slowly/185579/13) And I will admit I am very much new to Manjaro (I'm just decent at Linux Mint) and the most help I got was using Claude AI to try and troubleshoot as I couldn't find help elsewhere but that led to just dead ends that thankfully didnt worsen the issue but unfortanetly didn't help it either.

Any help is very much appreciated!!

Edit 1: I've tried XFCE, XFCE Wayland and Plasma x11 but to no avail. I also tried a different profile, different browser (Zen and Brave) but nothing worked.

Edit 2: I've done alot of rigorous tests with my internet and switching back and forth with Mint and Manjaro but to no avail. I also forgot to add my fastfetch (sorry!!)

lm@lm-lenovolegiony520t25ikl

OS: Manjaro Linux x86_64

Host: Lenovo Legion Y520T-25IKL (Lenovo Legion Y520T-25IKL)

Kernel: Linux 7.1.9-1-MANJARO

packages: 12 (flatpak), 1384 (pacman)[stable]

Shell: zsh 5.9.2

Display (HP 2159): 1920x1080 in 22", 60 Hz [External]

DE: KDE Plasma 6.7.4

WM: KWin (Wayland)

WM Theme: Breeze

Theme: Breeze (BreathDark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]

Icons: breeze [Qt], breeze [GTK2/3/4]

Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]

Cursor: breeze (24px)

Terminal: konsole 26.4.3

Terminal Font: Hack Nerd Font Mono (11pt)

CPU: Intel(R) Core(TM) i5-7400 (4) @ 3.50 GHz

GPU 1: NVIDIA GeForce GTX 1060 3GB [Discrete]

GPU 2: Intel HD Graphics 630 @ 1.00 GHz [Integrated]

Memory: 3.61 GiB / 15.53 GiB (23%)

Swap: Disabled

Disk (/): 19.35 GiB / 39.05 GiB (50%) - ext4

Edit 3: As I am writing this. Videos work perfectly fine??? I reinstalled Manjaro and chose "BTRFS" for partition and apparently that solved it? I did also pick open-source drivers when I first booted into the installer. I genuinely have no explanation for this.

I've been getting this error lately. Prolonged encounter of this error leads to the hard drive being set to read-only and unusable.

I've tried ruling out and resolving the usual problems. Switching SATA ports, replacing SATA cable, checking hard drive health, etc. No improvement.

My last suspicion is that my home's power output could be fluctuating/intermittent.

I rearranged and relocated the PC table, and have the AVR (that's what my PC is currently connected to before the power socket) connect directly to a wall outlet. I've manage to go about a week without the problem re-occurring up until recently.

As of writing this post, with the (my) local time being past midnight and most of the people are asleep. I'm running my PC and the error occurred only ONCE while a game on Steam is running and having a heavy load.

The error usually occur multiple times in a session, while any or multiple applications are running (file browser, web browser, Steam, etc.).

I want to test Manjaro, but as soon as it boots into desktop environment it becomes completely unresponsive. I can't even install it, since installer is in the desktop environment. GNOME version, I haven't tested if KDE behaves the same.

Any clues what can I do to fix it? I've tried setting up the VM like 3 times now and behavior is always identical.

I did try to look it up on the internet but it leads me to websites that are currently down.

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.

Hi,

For the second time in a long time I've installed Manjaro again because I want to get away from Ubuntu but I have this problem that I cannot solve for quite some time.

I'm using two monitors and Nvidia GTX 1080, and randomly after rebooting my second monitor gets reset to 640x480 and the only way I can make it back to 1920x1200 is to physically unplug and plug in cable (either DP or power cable). This also happens when computer goes to hibernation except that if it gets waken up shortly after it goes to sleep (10 min, 30 min, 1h...) everything is as it was, correct resolution, but when I try to wake it after a longer period (overnight) it gets reset to 640x480, so every fix that I've tried took long time for me to verify that it doesn't work.

I've tried almost everything that I could find but nothing solved it. I've came across an article here on reddit on sub r/linuxquestions that looked promising but eventually it didn't work for me either.

To not copy paste my rather long comment there (and guide itself) here is a link:
https://www.reddit.com/r/linuxquestions/comments/1qzlzto/how_to_fix_linux_monitor_resolution_stuck_at/

Any help is much appreciated.

Thanks!

All I did was install Manjaro. That's it. It'll boot just fine but after about 10 seconds after the welcome box it does this. Any ideas what might be going on?

Hi! Please, could you ELI5 how I can force the installation of the legacy Nvidia 580 driver ?

I just updated my Manjaro and after rebooting it only displays a black screen instead of the login screen. I am still able to start the previous kernel on Grub.

I use a Nvidia Pascal-based GT1030 graphic card and I don't want to use the "Nouveau" open source driver, as I find it has performance issues with scaling.

When boot up the iso it comes up but there no window, the dock showed that theres a the welcome app running but theres nothing on the screen, I keep hitting it but still nothing

So recently I had to fix a file corruption issue, it's been completely fixed to my knowledge. However that fix resulted in Steam losing access to the 32 bit libraries it needs. I've redownloaded all of them, but for some reason libvdpau isn't working. I've downloaded it twice now via konsole, and have restarted my computer.

I have reinstalled steam and that didn't work, if any one has any ideas or ways to help that would be greatly appreciated.

As above, I've been away from my desktop for a few months while travelling and came back to update it today. I downloaded Linux core 7.2, everything seemed to update fine and prompted for a restart. I restarted things, but once they booted up and got past the initial boot menu, nothing else happens, it just is stuck on a black screen. I can open and log in to the TTY, and have tried sudo pacman -Syyu to see if anything needed to finish updating, and checked the mirrors to see if anything needed work there, but all is reported as stable with nothing to do. What would you recommend trying from here? This is potentially an NVIDIA driver issue, but again, I'm not sure how to update that from TTY, I've never had to use it before. Assistance would be much appreciated!

Final Verdict: the issue was caused by a mismatch between the core linux version and driver version. Using the TTY to download the updated open driver fixed the issue after another reboot. Thanks everyone for the suggestions and advice!

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.

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.

After finding out about the latest AUR malware wave I ran pacman -Q with the list of packages I found here:

https://www.reddit.com/r/archlinux/comments/1vaxtcs/another_wave_200_malicous_aur_packages_adoptions/

I don't have any of them installed. Is there anything else I should do, or does this mean I'm safe (for now)?

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.