lite-xl : A lightweight text editor written in Lua https://lite-xl.com
gambas3-gb-highlight : A syntax highlighter based on definition files http://gambas.sourceforge.net/
Deleted packages :
haskell-random-source : Generic basis for random number generators https://github.com/mokus0/random-fu
yuzu : Nintendo Switch emulator https://yuzu-emu.org/
haskell-hls-tactics-plugin : Wingman plugin for Haskell Language Server https://haskellwingman.dev
haskell-record-hasfield : A version of GHC.Records as available in future GHCs. https://github.com/ndmitchell/record-hasfield#readme
python-ansicolors : ANSI colors for Python https://github.com/jonathaneunice/colors
haskell-hls-brittany-plugin : Integration with the Brittany code formatter https://haskellwingman.dev
electron29 : Build cross platform desktop apps with web technologies https://electronjs.org
haskell-bytestring-show : Efficient conversion of values into readable byte strin… https://hackage.haskell.org/package/bytestring-show
haskell-hls-haddock-comments-plugin : Haddock comments plugin for Haskell Language Server https://github.com/haskell/haskell-language-server
haskell-record-dot-preprocessor : Preprocessor to allow record.field syntax https://github.com/ndmitchell/record-dot-preprocessor#readme
haskell-brittany : Haskell source code formatter https://github.com/lspitzner/brittany/
python-lru-dict : A fast and memory efficient LRU cache for Python https://github.com/amitdev/lru-dict
Replaced packages
libblockdev-tools : A library for manipulating block devices - tools https://github.com/storaged-project/libblockdev -> libblockdev-fs
libblockdev-utils : A library for manipulating block devices - utility func… https://github.com/storaged-project/libblockdev -> libblockdev
libblockdev-lvm-dbus : A library for manipulating block devices - LVM D-Bus AP… https://github.com/storaged-project/libblockdev -> libblockdev-lvm
cargo-espflash : Cargo subcommand for flashing Espressif devices over se… https://github.com/esp-rs/espflash -> espflash
Its just cosmetical i know. Just wanted to report it.
sddm-greeter still has the bug with nouveau and nvidia geforce 210 plus kernel greater then 6.1, but i wont bother you anymore because i know its old hardware. But why throwing away if it is ok.
[ 82.902509] sddm-greeter[992]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
[ 89.866468] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 4 [sddm-greeter[992]] get 000021e000 put 000021e088 ib_get 00000007 ib_put 00000008 state 80000024 (err: INVALID_CMD) push 00400040
[ 93.432563] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 4 [sddm-greeter[992]] get 000021e008 put 000021e088 ib_get 0000000b ib_put 0000000c state 80000000 (err: INVALID_CMD) push 00400040
[ 93.519264] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 4 [sddm-greeter[992]] get 000021e088 put 000021f6d8 ib_get 0000000d ib_put 0000000e state 80000024 (err: INVALID_CMD) push 00400040
[ 93.569194] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 4 [sddm-greeter[992]] get 000021f708 put 000021f760 ib_get 00000013 ib_put 00000014 state 80000000 (err: INVALID_CMD) push 00400040
[ 93.571752] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 4 [sddm-greeter[992]] get 000021f764 put 0000220f74 ib_get 00000015 ib_put 00000016 state 80000000 (err: INVALID_CMD) push 00400040
[ 102.904475] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 4 [ksplashqml[1083]] get 000021e004 put 000021e088 ib_get 0000000b ib_put 0000000c state 800081a4 (err: INVALID_CMD) push 00400040
As far as I can see that’s an unofficial PPA, there is no official support. If you’d be happy to trust that on Ubuntu/Mint then 340.xx and 390.xx drivers are available with patches for later kernels on the AUR;
I haven’t updated in about two months because I’ve been moving out of Japan and stuff, so I focused on getting the most out of my time here… anyways, I’m running Manjaro GNOME on btrfs due to my (future, not yet realised) NAS running on btrfs. Today I update the package lists and saw that there is about 2.2GBs of packages to install, around 9GB of total Install size. I made some cleanup recently and had 15.6GiBs of free space on disk, so I figured all should fit with some 3GBs overhead… yeah, famous last words.
I checked all the known issues as posted in the wiki post, and I ran the update with pacman -Syyu pacman-contrib due to that 2-16 update which split them. I replaced bashrc-manjaro with /core/bash, downloaded all the packages, the sufficient space check passed, everything was going well until I started getting write errors while updating papirus-icons… This was confusing since df -h and gnome-nautilus both showed 6GB of free space still left on root partition and some sensible values on all others.
Well, I ran paccache -rvk 2 to clear out some 2.1GB more space from old packages. To make sure the filesystems get cleared or maybe SSD trimmed, I rebooted the PC only to find out that all the Linux kernels have been wiped from the boot partition! XD
I’m writing this post from a live-booted Manjaro GNOME from a Ventoy ssd-pendrive I always carry for such occasions. Now I have to remember how it was done the Arch way (I installed Arch once back in 2013), hopefully chrooting into the existing Manjaro install, checking that free space situation, mounting all the partitions and running mkinitcpio should be enogh, but please let me know if you have any better ideas getting out of this predicament.
P.S. this is not the first time I’m getting silly errors due to running out of free disk space (I guess my sence of “enough free space” has gotten deprecated). What’s outrageous is that pacman always passes the free disk space check! I think this might be a bug… one more time this happens and I’m setting up a VM for testing just that, and file a bug report (question to readers: Should I file it here with Manjaro or to upstream (Arch))?
Update went fine on X11 and stable. Still have the random freezing issue when testing Wayland, but I understand that may not come right for multi-monitor setups with Nvidia proprietary driver until v6.
Hey @MrLavender .
Thank you for the suggestions. I like Manjaro and will use it on this Machine in future, and yes you are right, it is an unsupportet PPA and not trustworthy.
AUR is unsupported from Manjaro because Manjaro does not officially support AUR. The 340.xx Branch is in AUR. (Yes i can try) but i like the nouveau drivers because they are FOSS.
390.xx Branch does not include the old Geforce 210 Hardware. @pheiduck
So … Geforce 210 is not longer supported in Manjaro with kernels higher then 6.1.xx because Manjaro has no support for AUR.
Not sure if this is just me or if others are experiencing this but my discord version still has not been updated from 0.0.44-1 to 0.0.45-1. I was wondering what the process is for updating one of the packages and would have thought that when it was updated on arch that it would have also been updated for the Manjaro Official Repositories. If anybody knows of the process and if there is any way to help in that process I’d be interested in learning. Thanks!
0.0.45-1 is on unstable branch. It takes longer for new Arch packages to get to stable branch because they go through unstable and testing first. That’s the whole point of stable.
You can always manually update it by using the “downgrade” package (unironically).
$ downgrade discord
It will give you a list of versions to chose from (Arch repo, not manjaro), including the lastest version.
Do keep in mind this is a “hack” and kind of and “advanced users only” thing.
This will NOT update package dependencies and can cause a “partial upgrade” situation where packages stop being compatible with each other and fail to work.
With that warning out of the way, for discord, this usually causes no issues
(and since old versions of discord always fail to open anyway, you dont lose anything really).
