Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering the various expenses incurred in the operations of the project such as server costs, software development tools, infrastructure expenses, training, flying people to events or conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate!
As you might have seen some of our team were able to attend FOSDEM 2023 and the conference proved to be incredibly productive for us. See our blog post for more.
Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: News – Manjaro
Nvidia drivers got downgraded to 550.100, therefore update with sudo pacman -Syuu. If you want to stay on the 555 driver series you may either switch to unstable or install nvidia-dkms via: sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/nvidia-dkms-555.58.02-1-x86_64.pkg.tar.zst. More info about Nvidia drivers here:
You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.11.so.
Print a list of of packages that have files in /usr/lib/python3.11/ :
pacman -Qoq /usr/lib/python3.11/
Rebuild them all at once:*
pamac build $(pacman -Qoq /usr/lib/python3.11)
* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.
Use rebuild-detector to see if anything else needs to be rebuilt:
checkrebuild
Info about AUR packages
AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements topics are off-topic and will be flagged, moved or removed without warning.
For help with AUR packages, please create a new topic in AUR and a helpful volunteer may be able to assist you.
Linux 6.9 is EOL and will - at some point - be removed from the repo.
Suggestion is to install latest LTS to be sure
sudo mhwd-kernel -i linux66
2024-07-14
Nvidia driver downgrade
Nvidia drivers got downgraded to 550.100, therefore update with sudo pacman -Syuu. If you want to stay on the 555 driver series you may either switch to unstable or install nvidia-dkms via: sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/nvidia-dkms-555.58.02-1-x86_64.pkg.tar.zst. More info about Nvidia drivers here:
No plasma interface with kernel 6.9 + Nvidia gpu + Wayland
If you encouter a black screen with no inteface after login in, it’s probably a problem with simpledrm loading.
To solve it add nvidia_drm.fbdev=1 to /etc/default/grub
in the line begining with GRUB_CMDLINE_LINUX=" .
Verify that you also have nvidia_drm.modeset=1 in the same line.
Then exec sudo update-grub
Also, verify that you have nvidia_drm in /etc/mkinitcpio.conf in the MODULES= or HOOKS= line.
Exemple :
The default KDE Plasma session has been changed to X11
As of Plasma 6, KDE decided to make Wayland the default. However, since issues were discovered, we have reverted the default to X11. Users are free to choose whichever works best for them.
Running gnome, update went well but when I rebooted no wifi adapter was detected. Rebooted for a second time and wifi adapter started working fine again. Hopefully just a gremlin but if it happens again I’ll grab some logs and post system info
As far I know, this is needed for scanner support. Is there an alternative?
I checked the AUR and it was dropped because it won’t build. In AUR, they added a patch for it to build. Then I checked gitlab, and it wasn’t updated since 2 years and seems to be abandoned.
Xsane always felt a vital and core part to make the scanner work, so maybe I’m missing something and it’s not needed anymore?
UPDATE: Ah, thanks for the link @linux-aarhus. So xsane is not really needed, it’s sane that is the backbone. I also use Scanpage, which is way better then original xsane, so in theory, I can remove it safely, with the exception of gimp-plugin. But I can scan something outside of Gimp and open it in Gimp. It should be a core part of Gimp (no plugin needed).
OK, thanks. I confused it for sane and thought to be a core component, but if it’s only a frontend, one of many, it’s not a big deal then. Case closed .
[alex@alex-b450aoruselite ~]$ pamac upgrade
Preparando...
Sincronización de bases de datos de paquetes...
Error: Error de GPGME: No hay datos
Error: Error de GPGME: No hay datos
Error: Error de GPGME: No hay datos
Actualizando core.db...
Actualizando extra.db...
Actualizando multilib.db...
Error: Error de GPGME: No hay datos
Error: Error de GPGME: No hay datos
Error: Error de GPGME: No hay datos
base de datos no válida o dañada (firma PGP)
Error al sincronizar las bases de datos
Can’t mount NTFS USB-SSD after update.
USB-SSD works fine on Windows11/Ubuntu20.04 machines.
Dolphin message.
Error mounting /dev/sdb2 at /run/media/furukawa/StableDiffusion: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error
Dmsg
[110201.435577] usb 3-1.4: new full-speed USB device number 31 using xhci_hcd
[110201.653627] usb 3-1.4: New USB device found, idVendor=1d5c, idProduct=7102, bcdDevice= 1.00
[110201.653643] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[110201.653644] usb 3-1.4: Product: Generic Billboard Device
[110201.653645] usb 3-1.4: Manufacturer: Fresco Logic, Inc
[110402.039854] usb 4-2: new SuperSpeed USB device number 7 using xhci_hcd
[110402.057369] usb 4-2: New USB device found, idVendor=04bb, idProduct=0196, bcdDevice= 2.03
[110402.057372] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[110402.057373] usb 4-2: Product: I-O DATA SSPS-US
[110402.057374] usb 4-2: Manufacturer: I-O DATA DEVICE, INC.
[110402.057375] usb 4-2: SerialNumber: 234320002678
[110402.062795] scsi host1: uas
[110402.063254] scsi 1:0:0:0: Direct-Access I-O DATA SSPS-US 0203 PQ: 0 ANSI: 6
[110404.544229] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[110404.544233] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[110404.544410] sd 1:0:0:0: [sdb] Write Protect is off
[110404.544411] sd 1:0:0:0: [sdb] Mode Sense: 5f 00 00 08
[110404.544735] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[110404.544922] sd 1:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
[110404.544923] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
[110404.547760] sdb: sdb1 sdb2
[110404.547936] sd 1:0:0:0: [sdb] Attached SCSI disk
[110404.605879] ntfs3: sdb2: It is recommened to use chkdsk.
[110404.610184] ntfs3: sdb2: volume is dirty and "force" flag is not set!
Please update to latest 6.6 or 6.10 kernels available at least in testing so we can fix the hdparm and lm_sensor errors. They’ve been fixed in latest kernel.
Thank you.