[Stable Update] 2024-09-02 - Kernels, Pipewire, Systemd, LibreOffice, OGUI, Inputplumber, Firefox

Hello community, here we have another set of package updates.

Current Promotions

  • Find out all about our current Gaming Laptop the Hero with Manjaro pre-installed from Spain!
  • Protect your personal data, keep yourself safe with Surfshark VPN: Get 3 months extra

Recent News

Previous News
Finding information easier about Manjaro

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

image

Notable Package Updates

Additional Info

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:

555 release feedback & discussion - Linux - NVIDIA Developer Forums
550.78 release feedback & discussion thread - Linux - NVIDIA Developer Forums

Python 3.12 info

:information_source: You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.11.so. :information_source:

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

:warning: 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.

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.


Our current supported kernels

  • linux419 4.19.320
  • linux54 5.4.282
  • linux510 5.10.224
  • linux515 5.15.165
  • linux61 6.1.106
  • linux66 6.6.47
  • linux69 6.9.12 [EOL]
  • linux610 6.10.6
  • linux611 6.11.0 rc4
  • linux61-rt 6.1.105_rt38
  • linux66-rt 6.6.44_rt39
  • linux69-rt 6.9_rt5
  • linux610-rt 6.10.2_rt14

Package Changes (Sun Aug 25 2024 11:54:16 GMT+0000)

  • stable core x86_64: 33 new and 33 removed package(s)
  • stable extra x86_64: 1228 new and 1188 removed package(s)
  • stable multilib x86_64: 15 new and 16 removed package(s)

A list of all package changes can be found here

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)
0 voters

Check if your mirror has already synced:

11 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable Updates Announcements RSS feed


Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

Note: Do not forget to review your .pacnew files:

:information_source: 2024-09-09

Added by @linux-arhus

System freeze on suspend

A feature in systemd 256 freezing a user session when suspending may freeze the system.

The issue is most prominent with Nvidia systems but reports exist that it may affect other systems as well.

A workaround for this is to create a override config

/etc/systemd/system/systemd-suspend.service.d/disable_freeze_user_session.conf

containing

[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"

:warning: Linux 6.9 is EOL

Linux 6.9 is EOL and will - at some point - be removed from the repo.

Please ensure your system use a supported kernel mhwd-kernel -l

:zap: KERNELS REMOVED

Linux 6.8 has been removed from repo.

:arrow_right: 2024-09-02

2024-08-20

Some GTK apps on Gnome suddenly changed to other (bright) theme

The adw-gtk3 package is now called adw-gtk-theme which replaces the old adw-gtk-theme.
With that change, you may need to set Legacy Applications to Adw-gtk3-dark in the Tweaks application under Appearance. It may have been set to the now removed Adw-dark previously.

2024-08-08

pipewire-pulse conflicts with pulseaudio-ctl

pulseaudio-ctl is not compatible with PipeWire and should be removed:

pamac remove pulseaudio-ctl
Noisetorch from Extra repository cannot be updated

noisetorch on AUR has been updated to change pulseaudio dependency to pulse-native-provider
A similar change has not been implemented for repository package yet, so pipewire-pulse users may need to remove package before update

pamac remove noisetorch

Noisetorch 0.12.2-4 with pulse-native-provider dependency has been released to all Manjaro branches - Branch compare for Manjaro - noisetorch

2024-07-29

2024-07-01

The sshd service needs to be restarted after upgrading to openssh-9.8p1

2024-07-01 - Robin Candau

After upgrading to openssh-9.8p1, the existing SSH daemon will be unable to accept new connections (see Can't login after openssh 9.8p1-1 upgrade, MUST restart sshd (#5) · Issues · Arch Linux / Packaging / Packages / openssh · GitLab).
When upgrading remote hosts, please make sure to restart the sshd service using systemctl try-restart sshd right after upgrading.

We are evaluating the possibility to automatically apply a restart of the sshd service on upgrade in a future release of the openssh-9.8p1 package.

– Arch Linux - News: The sshd service needs to be restarted after upgrading to openssh-9.8p1

Virtual machines using libvirt have no internet if the host uses UFW

This is a known bug. “Workaround” is to change the firewall with firewalld or to disable UFW.
Another easier workaround is to edit /etc/libvirt/network.conf, and add

firewall_backend = "iptables"

2024-05-14

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 :

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

If it was not present, then run sudo mkinitcpio -P after adding it.

2024-05-13

Python interpreter upgrade

If you have a lot of pip/AUR packages to upgrade to Python 3.12, read this.

If you installed python312 from the AUR, you need to uninstall it before running this update.

Qemu: MacOS is not bootable with 9.0

Due to a bug MacOS is not bootable with 9.0: [9.0.0] qemu breaks mac os vm (#2334) · Issues · QEMU / QEMU · GitLab
Workaround: remove virtio-serial and org.qemu.guest_agent.0 from libvirt XML until bug will be fixed.

If you use KDE you better logout of your session and do the update via Pacman or Pamac in tty.

Helper script to reset plasma Manjaro-Plasma-Reset/manjaro-plasma-reset.sh at main - wonky/Manjaro-Plasma-Reset - Codeberg.org @liinux-aarhus
Also I would, before the update:

  • make a Timeshift snapshot if you ain’t got no recent one.
  • ( export content of widgets like your radio stations in Advanced Radio Player or your Podcasts in Kasts or any podcatcher as a backup )
  • make a fresh boot, but before that even:
  • System Settings > Appearance > Global Theme > set to Breath and tick both options for defaults
  • You might go to the hamburger menu in System Settings and look what changes you made away from default by selecting: Highlight Changed Settings and see if you want to make the effort to get back more defaults
  • System Settings > Workspace > Startup and Shutdown: SDDM defaults and Desktop Session: Start with empty session
  • disable all user-installed widgets that are still on your desktop, panels and even lock screen or wallpaper (e.g. Active Blur)
  • Export your custom shortcuts or mouse gestures in SS> Workspace > Shortcuts
  • Reboot, Timeshift snapshot, reboot
  • then do not log in, do the update via tty (CTRL+ALT+F3, same with F2 gets you back)
  • reboot, login, check through System Settings
  • reboot again
  • enjoy 8)

post-install:

  • look for Plasma 6 replacements for your widgets after the install
  • in case you have Github-installed theming: uninstall the KDE5-version of klassy, install the Plasma 6 version of klassy, maybe reinstall lightly

(greetings, @1efaf7d71a8637c6800a , PS: these are just my thoughts; I didn’t do this update yet!)

How to fix `plasma-firewall` error in System Settings GUI when running `ufw`

Open /usr/lib/kde_ufw_plugin_helper.py and change the first line from #!/usr/bin/python3.11 to #!/usr/bin/python3.12. This fixed the issue for me immediately and makes sense since Manjaro is currently on Python 3.12.

Xfce has inconsistent themes for Qt applications

Qt 6 is now default but some apps are still using Qt 5
To restore the look of QT apps after this update

pamac install kvantum-qt5

Manjaro-settings-manager has light theme instead of dark

2024-04-04

DKMS fails for v4l2loopback on 6.8 kernel

DKMS fails for v4l2loopback on 6.8 kernel (#2) · Issues · Arch Linux / Packaging / Packages / v4l2loopback · GitLab

issues with auto-mount of ntfs filesystem using Kernel 6.8

The kernel changed default ntfs driver from FUSE one to ntfs3.
These two are not fully compatible, mainly as far as mount options go. If you have custom mount options in the fstab (or any other application, such as VeraCrypt) they need to be changed.

Symptoms:
Mount fails with: Device or resource busy
DMesg reports: Can't open blockdev

Solution:
Migrate your mount options. For me the changes were:

  • allow_other → umask=000
  • default_permissions → [drop]
  • user_id=1000 → uid=1000
  • group_id=1000 → gid=1000

2024-03-06

gnome-keyring: ssh component is not included

ssh component is not included (#3) · Issues · Arch Linux / Packaging / Packages / gnome-keyring · GitLab

2024-02-21

plymouth update may cause black screens

With a newer version of plymouth than 22.02.122 you may experience an unbootable system with a black screen. This might be due to not having early KMS enabled. If you have an Nvidia GPU you could set nvidia_drm.modeset=1 nvidia_drm.fbdev=1 to the kernel parameters in your bootloader config to avoid the need of KMS. However, with Wayland around the corner, KMS will be needed.

To “fix” the current problem, we have downgraded plymouth once again to have more time to find a proper solution to migrate most of your installations to a working state with newer plymouth versions.

sudo pacman -Syuu

Those who don’t have issues can enjoy the newer version of plymouth.

Directions for adding kms to your system configuration and how you can help troubleshooting by providing some sysinfo, read more → Black Screen with Plymouth - Cause and Solution

polkit update might remove your local modified config

With polkit 124-1 there were changes made to etc/pam.d/polkit-1. So check if you made local changes to the file. See also: https://www.reddit.com/r/archlinux/comments/19bnj0i/comment/kit2v33/

bashrc-manjaro is now merged into bash
  • Yes, replace bashrc-manjaro with bash
  • Please also compare your:
    /etc/bash.bashrc
    with the generated
    /etc/bash.bashrc.pacsave
    and retrofit all of your customisations as there was no .pacnew file generated.
  • Same goes for /etc/skel/.bashrc
pacman and pacman-contrib changes

pacman-contrib is now split out from pacman. If you have anything installed that depends on pacman-contrib, update (after you finished the Release Update) with:

sudo pacman -Syu pacman-contrib

2024-01-13

Initramfs image can be bigger on 6.7 kernel due to Nvidia GSP Boot firmware

We all known that kernel 6.7 is very feature rich. One of the features is the inclusion of Nvidia’s GSP Boot firmware into Initramfs. However this will increase your image by 150 MB and the fallback image might be 240 MB in size. A way would be to remove kms from mkinitcpio.conf and redo your initramfs images. A discussion regarding that can be found at Arch Gitlab: kms hook increases the initramfs size heavily starting with 6.7 kernel (#238) · Issues · Arch Linux / Mkinitcpio / mkinitcpio · GitLab

To reduce size add fallback_options="-S autodetect -S kms" to /etc/mkinitcpio.d/linux67.preset

Making dbus-broker our default D-Bus daemon

2024-01-09 - Jan Alexander Steffens

We are making dbus-broker our default implementation of D-Bus, for improved performance, reliability and integration with systemd.

For the foreseeable future we will still support the use of dbus-daemon, the previous implementation. Pacman will ask you whether to install dbus-broker-units or dbus-daemon-units. We recommend picking the default.

For a more detailed rationale, please see our RFC 25.

– Arch Linux - News: Making dbus-broker our default D-Bus daemon

In some cases, however it is better to keep the legacy way. Here are some examples: Dbus-broker warnings

Previous stable update threads:

2 Likes

Well might be coincidence … reboot after update greeted me with console tty and an fschk error asking me to do fschk on my NVMe SSD manually. Doing that and fixing A LOT of errors, after a reboot now everything seems to be OK for now. At least KDE is starting again and firefox and Steam are running.

1 Like

I have a new AUR file (after this update) the file called rest and its required by lib32-rest… is lib32-rest needed for something special?

I would like to remove them both.

lib32-libsoup is also required lib32-rest btw, thats strange because lib32-rest is listed as orphan now, while lib32-libsoup not shown up under orphan :man_shrugging:

Edit:
Spoiler Alert i removed all 3 packages, i edit later if everything is fine :slight_smile:

Edit2:
Everything is fine after removing lib32-rest, lib32-libsoup, rest

3 Likes

Upgrading now; no reported conflicts.

Edit: reboot whilst I was sorting Roobarb’s next meal (I’d say he’d eat a horse, but he probably is), opening a bag of crisps, got back to the machine in less than a minute with the browser already open with this tab and my partial reply.

Tested some basic stuff and all seems to be working fine. (VirtualBox hasn’t complained, for example).

Nothing shows up for that package when I search for it. I guess it’s now redundant? (Please start a thread for this!).

EDIT 2:
@Kobold Updating in response to your edit. Probably best that you removed those packages because they don’t seem to be referenced by anything and this is an install with over 6 years’ vintage.

1 Like

got just one orphan

pacman -Qdt
mbedtls2 2.28.8-3
LC_ALL=C pacman -Qi mbedtls2
Name            : mbedtls2
Version         : 2.28.8-3
Description     : An open source, portable, easy to use, readable and flexible TLS library
Architecture    : x86_64
URL             : https://tls.mbed.org
Licenses        : Apache-2.0
Groups          : None
Provides        : libmbedcrypto.so=7-64  libmbedtls.so=14-64  libmbedx509.so=1-64
Depends On      : glibc
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 2.93 MiB
Packager        : Maxime Gauduin <alucryd@archlinux.org>
Build Date      : Tue May 28 11:58:47 2024
Install Date    : Wed Jul 31 15:22:49 2024
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

A quick and simple update, thanks team.

One important message that may have whizzed past without being noticed if Mariadb is installed:

run
systemctl restart mariadb && mariadb-upgrade -u root -p

1 Like

The first link is from the previous update.

rest and lib32-rest have been dropped from Manjaro repositories

https://gitlab.manjaro.org/-/snippets/1043/raw

:: Different sync package(s) in repository extra x86_64

--------------------------------------------------------------------
           PACKAGE             2024-08-20           2024-09-02
--------------------------------------------------------------------
              rest    0.8.1+r4+ge5ee6ef-1                    -

:: Different sync package(s) in repository multilib x86_64
--------------------------------------------------------------------
           PACKAGE             2024-08-20           2024-09-02
--------------------------------------------------------------------
        lib32-rest                0.8.1-4                    - 
3 Likes

If you want to know what previously depended on an orphan package you can use pacsift from the pacutils package to search pacman cache (obviously requires that whatever package depended on it is still in the cache).

pacsift --cache --depends=lib32-rest 2>/dev/null

or to also check for optional dependencies

pacsift --cache --any --depends=lib32-rest --optdepends=lib32-rest 2>/dev/null
8 Likes

Useful. Though if, like me, you habitually remove deleted packages from the cache, you’ll have to run it without the “–cache” option and rely on recognising one or more packages you once had from the bigger list you’ll get.

1 Like

I had problems starting intellij-idea-community-edition. After some failed attempts, I switched to the previous version and now everything’s fine.

Error message:
java.lang.RuntimeException: Could not find installation home path. Please make sure bin/idea.properties is present in the installation directory.

XFCE desktop and PAMAC gui does not run.
seeing this in gnome-logs:

14:58:00 systemd-coredump: Process 15055 (pamac-manager) of user 1000 dumped core.

CORRECTION - it is working again.
Sequence of events:
- install updates
- reboot == pamac then fails to launch
- reboot == pamac working
- reboot == pamac working

Stack trace of thread 15063:
#0  0x000075756659c0dc pamac_app_get_id (libpamac.so.11 + 0x6a0dc)
#1  0x0000757567348534 n/a (libpamac-appstream.so + 0x4534)
#2  0x0000757566570552 n/a (libpamac.so.11 + 0x3e552)
#3  0x0000757566712266 n/a (libglib-2.0.so.0 + 0x8c266)
#4  0x00007575663d539d n/a (libc.so.6 + 0x9439d)
#5  0x000075756645a49c n/a (libc.so.6 + 0x11949c)

Stack trace of thread 15055:
#0  0x0000757566c95142 n/a (libgtk-3.so.0 + 0x295142)
#1  0x0000757566b31918 n/a (libgtk-3.so.0 + 0x131918)
#2  0x0000757566b1a76b n/a (libgtk-3.so.0 + 0x11a76b)
#3  0x0000757566b153ab n/a (libgtk-3.so.0 + 0x1153ab)
#4  0x0000757566b15648 n/a (libgtk-3.so.0 + 0x115648)
#5  0x0000757566b1569b n/a (libgtk-3.so.0 + 0x11569b)
#6  0x0000757566d67da7 n/a (libgtk-3.so.0 + 0x367da7)
#7  0x00007575667e564a g_closure_invoke (libgobject-2.0.so.0 + 0x1164a)
#8  0x0000757566815e22 n/a (libgobject-2.0.so.0 + 0x41e22)
#9  0x00007575668065dc n/a (libgobject-2.0.so.0 + 0x325dc)
#10 0x0000757566806842 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32842)
#11 0x0000757566806904 g_signal_emit (libgobject-2.0.so.0 + 0x32904)
#12 0x0000757566d46953 gtk_widget_show (libgtk-3.so.0 + 0x346953)
#13 0x0000757566d69230 gtk_window_present_with_time (libgtk-3.so.0 + 0x369230)
#14 0x00005a5c44300e11 n/a (pamac-manager + 0x2be11)
#15 0x0000757566806732 n/a (libgobject-2.0.so.0 + 0x32732)
#16 0x0000757566806842 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32842)
#17 0x0000757566806904 g_signal_emit (libgobject-2.0.so.0 + 0x32904)
#18 0x00007575669109d1 n/a (libgio-2.0.so.0 + 0xdd9d1)
#19 0x0000757566910b77 g_application_run (libgio-2.0.so.0 + 0xddb77)
#20 0x00005a5c442e1416 n/a (pamac-manager + 0xc416)
#21 0x0000757566366e08 n/a (libc.so.6 + 0x25e08)
#22 0x0000757566366ecc __libc_start_main (libc.so.6 + 0x25ecc)
#23 0x00005a5c442e1545 n/a (pamac-manager + 0xc545)

Stack trace of thread 15056:
#0  0x00007575664581fd syscall (libc.so.6 + 0x1171fd)
#1  0x000075756673da10 g_cond_wait (libglib-2.0.so.0 + 0xb7a10)
#2  0x00007575666ab90c n/a (libglib-2.0.so.0 + 0x2590c)
#3  0x00007575667176b7 n/a (libglib-2.0.so.0 + 0x916b7)
#4  0x0000757566712266 n/a (libglib-2.0.so.0 + 0x8c266)
#5  0x00007575663d539d n/a (libc.so.6 + 0x9439d)
#6  0x000075756645a49c n/a (libc.so.6 + 0x11949c)

Stack trace of thread 15061:
#0  0x00007575664581fd syscall (libc.so.6 + 0x1171fd)
#1  0x000075756673da10 g_cond_wait (libglib-2.0.so.0 + 0xb7a10)
#2  0x00007575666ab90c n/a (libglib-2.0.so.0 + 0x2590c)
#3  0x00007575666ab97d g_async_queue_pop (libglib-2.0.so.0 + 0x2597d)
#4  0x000075756607b5fc n/a (libpangoft2-1.0.so.0 + 0xc5fc)
#5  0x0000757566712266 n/a (libglib-2.0.so.0 + 0x8c266)
#6  0x00007575663d539d n/a (libc.so.6 + 0x9439d)
#7  0x000075756645a49c n/a (libc.so.6 + 0x11949c)

Stack trace of thread 15058:
#0  0x000075756644c63d __poll (libc.so.6 + 0x10b63d)
#1  0x000075756674492d n/a (libglib-2.0.so.0 + 0xbe92d)
#2  0x00007575666e37b7 g_main_loop_run (libglib-2.0.so.0 + 0x5d7b7)
#3  0x0000757566945574 n/a (libgio-2.0.so.0 + 0x112574)
#4  0x0000757566712266 n/a (libglib-2.0.so.0 + 0x8c266)
#5  0x00007575663d539d n/a (libc.so.6 + 0x9439d)
#6  0x000075756645a49c n/a (libc.so.6 + 0x11949c)

Stack trace of thread 15057:
#0  0x000075756644c63d __poll (libc.so.6 + 0x10b63d)
#1  0x000075756674492d n/a (libglib-2.0.so.0 + 0xbe92d)
#2  0x00007575666e1fc5 g_main_context_iteration (libglib-2.0.so.0 + 0x5bfc5)
#3  0x00007575666e201a n/a (libglib-2.0.so.0 + 0x5c01a)
#4  0x0000757566712266 n/a (libglib-2.0.so.0 + 0x8c266)
#5  0x00007575663d539d n/a (libc.so.6 + 0x9439d)
#6  0x000075756645a49c n/a (libc.so.6 + 0x11949c)

Stack trace of thread 15062:
#0  0x00007575664581fd syscall (libc.so.6 + 0x1171fd)
#1  0x000075756673e367 g_cond_wait_until (libglib-2.0.so.0 + 0xb8367)
#2  0x00007575666ab8d5 n/a (libglib-2.0.so.0 + 0x258d5)
#3  0x000075756671827b n/a (libglib-2.0.so.0 + 0x9227b)
#4  0x0000757566712266 n/a (libglib-2.0.so.0 + 0x8c266)
#5  0x00007575663d539d n/a (libc.so.6 + 0x9439d)
#6  0x000075756645a49c n/a (libc.so.6 + 0x11949c)
ELF object binary architecture: AMD x86-64

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

I just did the 2024-09-02 update on my MSI GT72 6Q2 (Manjaro KDE) with Intel i7 6700HQ and nVidia 970M and it appears flawless. Thank you to the dev team. You guys are amazing!

Same. This was fixed a week ago in Arch, would be nice if 4:2024.2.0.1-2 could be fast-tracked. @philm

:bangbang: Tip :bangbang:

When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:

```
pasted text
```

Or three (3) tilde signs, like this:

~~~
pasted text
~~~

This will just cause it to be rendered like this:

Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.

Instead of like this:

Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby increasing legibility thus making it easier for those trying to provide assistance.

For more information, please see:

1 Like

You might want to do a SMART extended self-test, just to be on the safe side.
I’ve had a failing SSD (corrupted sectors) with the same symptom.

1 Like

Hello, before the update my computer was running normally. I did the updated and restarted and now my computer will post to bios and then gets stuck on a black screen. I tried seeing if it was a gui problem and tried switching tty to CRL+ALT +F2/F1 but its also is a black screen. I’ve tried restarting multiple times to no avail. I can’t access a terminal so I don’t know exactly what logs or anything I can get to be helpful. Let me know if you need anything or if there might be a way to fix this. Thank you!
I have
amd GPU and CPU
kernel 6.10
Nvme SSD
Ddr5 expo ram
Gnome for my desktop

Edit: I can access the menu by hitting shift on boot
I’m on kernel 6.10 I’m gonna try booting to 6.9 and see if that helps… Did not help going to try plugging my monitor into my motherboard instead and use integrated graphics…uh it did something, now instead of a black screen it get stuck at just showing the Manjaro boot w/ Mobo logo instead of black screen and I can switch w/ CRL alt f2 but instead of being a black screen it stops input to the monitor and monitor goes into standby. I think I may be approaching the issue? A problem w/ amd gpu integrated or discrete graphics? Going to restart and see if problem persists… Yup now consistently doing the same thing. Flashes Mobo/Manjaro logo goes black then switched to loading version, three loading dots all flash then go into done loading version of three dots and gets stuck there. Versus would finish loading and then go to black screen when it was plugged into discrete amd GPU…

Ill go make a separate topic.

I recommend to create your own Topic, if you need assistants.

This announcement topic is mainly for a good overview, who has bugs and in which direction.

You can still link your own topic to your posting above me.

If we all help you here, the overview is getting lost for the other’s.

3 Likes

Will do, thank you!

1 Like