Manjaro will not reboot or shutdown if I click on the restart and shudown buttons

Hello everyone.
Long time no Linux!

How is everyone doing? I hope all is well.

Came back cuz I missed my Kvm setup, and compiz !

I would like to report a couple of bugs, sorry if this is the wrong section. This bug is present on stock manjaro, nothing else installed. Just a fresh installation.

Sorry about my linux ignorance and terminology.

Bug1: (fresh install + system full update)

If I click on the application launcher (do we call this start menu? lol) and click Restart or Shudown, the computer will hang for life.
But if I do it from the terminal, it works fine (at least reboot works fine).

Is there a simple way to fix this? I was blaming this bug on my ancient office machine. This bug appeared after one of the latest updates. But I installed manjaro on my main machine at home, and I noticed the same bug is present.
So it is a bug.

Bug2: (fresh install + system full update)
This is also a bug. It happens on my office computer too. But It has to be a bug because it is also happening on my main machine.

sometimes my sudo password stops working. I will just be doing my thing as normal… sudently sudo password is not recongnized by the terminal. No matter what I do, it is only good again after a system reboot.

Other than the 2 issues above, everything seems to be working fine !!!

I am posting a video to show off my pretty desktop :smiley: Sorry about the Arch wallpaper, I just love the logo.

I got Riot’s vangard working under the KVM. took 4 days to be able to hide the VM lol.

Anyways, Thanks alot guys.

Hi and welcome,

Same?


Please define ‘sometimes’?
Have you failed to enter your password a few times?
An automatic timed lockout can occur.
(You may try faillock to check.)


PS.

When asking for support it usually makes sense to include system information.

inxi -Farz

The following link will also include tips on how to format code, etc.

3 Likes

Thank you so much for the quick response.

Yeah randomly sometimes. No I don’t miss type the password ever, its literraly 123456 ish. I also did check faillock to make sure but nothing.

It happens more often when I am developing in c++ with VScode because I will test the app very often as I go, but It does happen even when not working with vscode.

I am making some simple automations cuz why not, but, when I use vscode terminal to launch the test app, sudo ./xkvm for testing, everything works like a charm…

But then suddently, sudo stops working. It will keep telling me the password is wrong. then I have to reboot.

I daily drive manjaro in the office for 3 computers, and after certain update, the restart issue started (i will try the empty session you provided). If the empty session fixes this, I will post it here to let you guys know.

The sudo isso though… Its not a huge deal, I jst a little annoying because sometimes I will be concentrated in coding, sudently I cant test the app anymore cuz the password doesnt work… but a reboot always fixes it.

–Edit.
Once this happens, sudo won’t work in any terminal. Not only vscode terminal. Don’t know if this would make a difference but just adding info.

Next time this happens, I will try TTY to see if it affects that also.

    ~  inxi -Farz                                                        ✔ 
System:
  Kernel: 6.10.13-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.10-x86_64
    root=UUID=9f24b2a4-ad4e-4f7b-84ae-02e814c37a01 rw quiet splash
    udev.log_priority=3 amd_iommu=on
  Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: SRD product: MS-0C36F v: N/A
    serial: <superuser required>
  Mobo: ASRock model: X670E Pro RS serial: <superuser required>
    part-nu: 49DD31713E uuid: <superuser required> UEFI: American Megatrends
    LLC. v: 3.06 date: 07/04/2021
CPU:
  Info: model: AMD Ryzen 9 7950X3D bits: 64 type: MT MCP arch: Zen 4 gen: 4
    level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
    model-id: 0x61 (97) stepping: 2 microcode: 0xA601206
  Topology: cpus: 1x dies: 2 clusters: 2x1 cores: 16 threads: 32 tpc: 2
    smt: enabled cache: L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 16 MiB
    desc: 16x1024 KiB L3: 128 MiB desc: 1x32 MiB, 1x96 MiB
  Speed (MHz): avg: 5040 min/max: 545/5759 scaling: driver: amd-pstate-epp
    governor: performance cores: 1: 5040 2: 5040 3: 5040 4: 5040 5: 5040 6: 5040
    7: 5040 8: 5040 9: 5040 10: 5040 11: 5040 12: 5040 13: 5040 14: 5040
    15: 5040 16: 5040 17: 5040 18: 5040 19: 5040 20: 5040 21: 5040 22: 5040
    23: 5040 24: 5040 25: 5040 26: 5040 27: 5040 28: 5040 29: 5040 30: 5040
    31: 5040 32: 5040 bogomips: 268387
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
    conditional; STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected;
    BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA AD102 [GeForce RTX 4090] vendor: ASUSTeK driver: vfio-pci
    v: N/A alternate: nouveau non-free: 550.xx+ status: current (as of 2024-09)
    arch: Lovelace code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2684
    class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: ASRock
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1
    empty: DP-2, DP-3, HDMI-A-1, Writeback-1 bus-ID: 7f:00.0
    chip-ID: 1002:164e class-ID: 0300 temp: 42.0 C
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
    s-diag: 777mm (30.58")
  Monitor-1: DP-1 mapped: DisplayPort-0 model: Samsung LC32G7xT
    serial: <filter> built: 2020 res: 2560x1440 dpi: 93 gamma: 1.2
    size: 698x393mm (27.48x15.47") diag: 806mm (31.7") ratio: 16:9 modes:
    max: 2560x1440 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.4-arch1.0.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
    raphael_mendocino LLVM 18.1.8 DRM 3.57 6.10.13-3-MANJARO)
    device-ID: 1002:164e memory: 500 MiB unified: no
  API: Vulkan v: 1.3.295 layers: 4 device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RAPHAEL_MENDOCINO) driver: mesa radv
    v: 24.2.4-arch1.0.1 device-ID: 1002:164e surfaces: xcb,xlib
Audio:
  Device-1: NVIDIA AD102 High Definition Audio vendor: ASUSTeK
    driver: vfio-pci alternate: snd_hda_intel pcie: speed: Unknown lanes: 63
    link-max: gen: 6 speed: 64 GT/s bus-ID: 01:00.1 chip-ID: 10de:22ba
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
    Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 7f:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
    vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 7f:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Device-4: HP HyperX SoloCast driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-5:2
    chip-ID: 03f0:078b class-ID: 0300
  API: ALSA v: k6.10.13-3-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Message: No PCI device data found.
  Device-1: Realtek USB 10/100/1G/2.5G LAN driver: r8152 type: USB rev: 3.2
    speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 8-1:2 chip-ID: 0bda:8156
    class-ID: 0000 serial: <filter>
  IF: enp127s0f4u1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-12:3 chip-ID: 0e8d:0616
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
RAID:
  Hardware-1: Advanced Micro Devices [AMD] Device driver: ahci v: 3.0
    port: N/A bus-ID: 7b:00.0 chip-ID: 1022:43bd rev: N/A class-ID: 0104
  Hardware-2: Advanced Micro Devices [AMD] Device driver: ahci v: 3.0
    port: N/A bus-ID: 7d:00.0 chip-ID: 1022:43bd rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 1.82 TiB used: 129.79 GiB (7.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:5 vendor: Samsung model: SSD 980 PRO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 35.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 44.9 C
    scheme: GPT
Partition:
  ID-1: / raw-size: 931.22 GiB size: 915.53 GiB (98.32%)
    used: 129.79 GiB (14.2%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:7
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:6
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 50.0 C mobo: N/A gpu: amdgpu temp: 43.0 C
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1448 libs: 395 tools: pamac,yay pm: flatpak
    pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    3: http://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
Info:
  Memory: total: 64 GiB note: est. available: 61.89 GiB used: 4.47 GiB (7.2%)
  Processes: 522 Power: uptime: 25m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 24.72 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.36

Okay so just a quick update.

This suggestion fixed the reboot bug hanging for ever. Thank you!

Welcome to the community.
6.10 is EOL already, recommend Kernel is 6.11 or 6.6 LTS… you can switch this under Manjaro Settings Manager>Kernel.

2 Likes

Thanks for having me

The secondary problem I was having. I think I found out what triggers it… visual studio code.

The application I am working on, doesnt work properly without elevation.

So what I usualy do is, I will build the solution, go into vscode’s terminal and go

sudo ./xkvm

Then it will ask for the password as normal…

But some times it will say the sudo password is incorrect. And once this happens, I can not use the sudo password in any terminal until I reboot.

This is so weird, but I think it’s safe to blame vscode, and not the OS.

I just wanted to post my findings. Please let me know if someone knows a solution, but until then, I have globalized my app, and I am runing it from a regular terminal for testing

Thanks again guys.

Search at the forum for a possible solution, if you can’t find anything then open another Topic.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.