this post was submitted on 26 Mar 2024
20 points (88.5% liked)

Linux

8053 readers
46 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
MigratingtoLemmy@lemmy.world
20
System keeps freezing UPDATE: It was Android Studio (lemmy.world)
submitted 7 months ago* (last edited 7 months ago) by qaz@lemmy.world to c/linux@lemmy.world
16 comments fedilink hide all child comments
 

I have been having a strange issue since a couple of days ago. Every so often, the following happens:

  1. The desktop and audio start lagging
  2. Audio cuts out
  3. Desktop becomes completely nonresponsive

I'm unable to SSH into the machine during this state. The only solution is cutting the power and rebooting.

Here are all the errors from the past 10 boots:

Boot AF7D271F5A114258BBA1A2795ED0BB2B (87 hours ago)
├─ Critical: 63
│  ├─ kded6: 27
│  │  │ 27 x "kde.dataengine.mpris: mpris:trackid from \"Spotify\" does not conform to the MPRIS2 standard. Please report the issue to the developer."
│  ├─ kscreenlocker_greet: 2
│  │  │ 2 x "pam_unix(kde-fingerprint:auth): auth could not identify password for [user]"
│  ├─ kwin_wayland: 6
│  │  │ 6 x "kwin_xkbcommon: XKB: /home/user/.XCompose:25:17: unrecognized keysym \"down\" on left-hand side"
│  ├─ plasmashell: 27
│  │  │ 27 x "kde.dataengine.mpris: mpris:trackid from \"Spotify\" does not conform to the MPRIS2 standard. Please report the issue to the developer."
│  ├─ systemd-coredump: 1
│  │  │ ""
├─ Error: 17
│  ├─ kscreenlocker_greet: 16
│  │  │ 16 x "PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory"
│  ├─ systemd: 1
│  │  │ "Failed to start Cloudflare Zero Trust Client Taskbar."
Boot A4A3B8B5C4B4429ADBBDD176C06F8BE (84 hours ago)
├─ Critical: 54
│  ├─ kded6: 24
│  │  │ 24 x "kde.dataengine.mpris: mpris:trackid from \"Spotify\" does not conform to the MPRIS2 standard. Please report the issue to the developer."
│  ├─ kwin_wayland: 6
│  │  │ 6 x "kwin_xkbcommon: XKB: /home/user/.XCompose:25:17: unrecognized keysym \"down\" on left-hand side"
│  ├─ plasmashell: 24
│  │  │ 24 x "kde.dataengine.mpris: mpris:trackid from \"Spotify\" does not conform to the MPRIS2 standard. Please report the issue to the developer."
├─ Error: 1
│  ├─ systemd: 1
│  │  │ "Failed to start Cloudflare Zero Trust Client Taskbar."
Boot 7664C5752DC414BBF1DB164AB9FDBC5 (59 hours ago)
├─ Critical: 291
│  ├─ kalendarac: 60
│  │  │ 60 x "\"No items found\""
│  ├─ kded6: 110
│  │  │ 110 x "kde.dataengine.mpris: mpris:trackid from \"Spotify\" does not conform to the MPRIS2 standard. Please report the issue to the developer."
│  ├─ kscreenlocker_greet: 7
│  │  │ 7 x "kde.dataengine.mpris: mpris:trackid from \"Spotify\" does not conform to the MPRIS2 standard. Please report the issue to the developer."
│  ├─ kwin_wayland: 4
│  │  │ 4 x "kwin_xkbcommon: XKB: /home/user/.XCompose:25:17: unrecognized keysym \"down\" on left-hand side"
│  ├─ plasmashell: 110
│  │  │ 110 x "kde.dataengine.mpris: mpris:trackid from \"Spotify\" does not conform to the MPRIS2 standard. Please report the issue to the developer."
├─ Error: 39
│  ├─ kscreenlocker_greet: 38
│  │  │ 38 x "PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory"
│  ├─ systemd: 1
│  │  │ "Failed to start Cloudflare Zero Trust Client Taskbar."
Boot F1D7401052124054BF46FBB6BB487F28 (34 hours ago)
├─ Critical: 226
│  ├─ kalendarac: 30
│  │  │ 30 x "\"No items found\""
│  ├─ kded6: 90
│  │  │ 90 x "kde.dataengine.mpris: mpris:trackid from \"Spotify\" does not conform to the MPRIS2 standard. Please report the issue to the developer."
│  ├─ kscreenlocker_greet: 10
│  │  │ 10 x "kde.dataengine.mpris: mpris:trackid from \"Spotify\" does not conform to the MPRIS2 standard. Please report the issue to the developer."
│  ├─ kwin_wayland: 6
│  │  │ 6 x "kwin_xkbcommon: XKB: /home/user/.XCompose:25:17: unrecognized keysym \"down\" on left-hand side"
│  ├─ plasmashell: 90
│  │  │ 90 x "kde.dataengine.mpris: mpris:trackid from \"Spotify\" does not conform to the MPRIS2 standard. Please report the issue to the developer."
├─ Error: 45
│  ├─ (sd-pam): 8
│  │  │ 8 x "pam_systemd(login:session): Failed to release session: Access denied"
│  ├─ kscreenlocker_greet: 32
│  │  │ 32 x "PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory"
│  ├─ pipewire: 2
│  │  │ 2 x "pw.node: (bluez_output.50_1A_A5_9D_00_36.1-95) running -> error (Received error event)"
│  ├─ systemd: 3
│  │  │ 3 x "Failed to start Cloudflare Zero Trust Client Taskbar."
Boot C2146EE3E7F644A08397C7F507B5CF75 (17 hours ago)
├─ Critical: 4
│  ├─ kwin_wayland: 4
│  │  │ 4 x "kwin_xkbcommon: XKB: /home/user/.XCompose:25:17: unrecognized keysym \"down\" on left-hand side"
├─ Error: 9
│  ├─ kscreenlocker_greet: 8
│  │  │ 8 x "PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory"
│  ├─ systemd: 1
│  │  │ "Failed to start Cloudflare Zero Trust Client Taskbar."
Boot CA2A66329A2142E481CAE7E0963A2CDB (14 hours ago)
├─ Critical: 4
│  ├─ kwin_wayland: 4
│  │  │ 4 x "kwin_xkbcommon: XKB: /home/user/.XCompose:25:17: unrecognized keysym \"down\" on left-hand side"
├─ Error: 5
│  ├─ kscreenlocker_greet: 4
│  │  │ 4 x "PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory"
│  ├─ systemd: 1
│  │  │ "Failed to start Cloudflare Zero Trust Client Taskbar."
Boot 92A27B0190FF4830931B74F351DCCBC3 (12 hours ago)
├─ Critical: 8
│  ├─ kwin_wayland: 8
│  │  │ 8 x "kwin_xkbcommon: XKB: /home/user/.XCompose:25:17: unrecognized keysym \"down\" on left-hand side"
├─ Error: 1
│  ├─ systemd: 1
│  │  │ "Failed to start Cloudflare Zero Trust Client Taskbar."
Boot 42E442362A494D9989170824C180B7D6 (12 hours ago)
├─ Critical: 2
│  ├─ kwin_x11: 2
│  │  │ 2 x "kwin_xkbcommon: XKB: /home/user/.XCompose:25:17: unrecognized keysym \"down\" on left-hand side"
├─ Error: 1
│  ├─ systemd: 1
│  │  │ "Failed to start Cloudflare Zero Trust Client Taskbar."
Boot 344510171595463697F2AA609028B920 (0 hours ago)
├─ Critical: 2
│  ├─ kwin_x11: 2
│  │  │ 2 x "kwin_xkbcommon: XKB: /home/user/.XCompose:25:17: unrecognized keysym \"down\" on left-hand side"
├─ Error: 1
│  ├─ systemd: 1
│  │  │ "Failed to start Cloudflare Zero Trust Client Taskbar."
Boot 9DC5C9C1506142A091B495CF3158E293 (0 hours ago)
├─ Critical: 2
│  ├─ kwin_x11: 2
│  │  │ 2 x "kwin_xkbcommon: XKB: /home/user/.XCompose:25:17: unrecognized keysym \"down\" on left-hand side"
├─ Error: 1
│  ├─ systemd: 1
│  │  │ "Failed to start Cloudflare Zero Trust Client Taskbar."

kinfo output:

Operating System: openSUSE Tumbleweed 20240321
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.1-1-default (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT

The problems seem to be correlated with when I'm looking through (not running) a certain Rust project with a lot of errors, but that might just be a coincidence.

UPDATE 2024-03-27:

It seems like Android Studio is responsible Full RAM and SWAP

After killing the process (terminate signal was ignored) Normal metrics after killing Android Studio

top 16 comments
sorted by: hot top controversial new old
[–] h3ndrik@feddit.de 9 points 7 months ago* (last edited 7 months ago) (2 children)

Sounds like maybe a memory leak and your RAM getting used up and the system then swapping and becoming unresponsive due to that?! I'd keep an eye on the RAM usage for a start.

[–] qaz@lemmy.world 3 points 7 months ago

I'll do that, thanks for the advice.

[–] qaz@lemmy.world 3 points 7 months ago (1 children)

It was exactly as you described, RAM was full, and the system started swapping itself to a crawl. I think Android Studio has a memory leak.

[–] h3ndrik@feddit.de 2 points 7 months ago (1 children)

Wow, 32GB + 32GB used up... Yeah, good guess 😅 Good luck fixing the issue.

[–] qaz@lemmy.world 2 points 7 months ago* (last edited 7 months ago)

I've updated it, and I'm just going to hope the issue goes away on its own.

[–] jazztickets@lemmy.world 3 points 7 months ago (1 children)

Does this output anything? journalctl -q -t kernel -g "gpu reset begin"

[–] qaz@lemmy.world 2 points 7 months ago

No, but it seems Android Studio was the cause.

[–] GravelPieceOfSword@lemmy.ca 3 points 7 months ago* (last edited 7 months ago) (1 children)

I run KDE on opensuse Slowroll - Intel i9 processor with plenty of RAM.

Check btrfs snapshots, and consider disabling them if you don't really need them.

Here's my story some time in the recent past:

Similar freezing issues that got more frequent. I have network and CPU monitor widgets on my desktop, and noticed my CPU usage peaking during freeze.

Ran top, saw #btrfs was doing a lot of processing. It was running snapshots.

I'd like snapshots, but a responsive system is more important to me: I have frequent backups of most of my stuff anyways.

Once I disabled btrfs snapshots, I stopped having the periodic freezes (which I also noticed were often some time after system/flatpak updates).

[–] qaz@lemmy.world 3 points 7 months ago

It turned out to be Android Studio

[–] lurch@sh.itjust.works 2 points 7 months ago (1 children)

Can you ctrl+alt+F3 or so to change to a text mode VT?

Also maybe check out magic sysrq.

I once used a cronjob that checked uptime and if a particular USB stick was present. If it was missing, it tried to save logs, process lists, kernel modules and other diagnostics and tried to chvt. So when that system crashed, I unplugged it and waited for the job to do its thing to get more info.

[–] qaz@lemmy.world 2 points 7 months ago (1 children)

CTRL + ALT + F3 also ceases to function when this occurs.

[–] anton@lemmy.blahaj.zone 2 points 7 months ago (1 children)

Can you reboot with ALT + Printscreen + B?

[–] qaz@lemmy.world 2 points 7 months ago

I have been unable to replicate the issue. I'll try it when it happens again.

[–] Rooki@lemmy.world 2 points 7 months ago* (last edited 7 months ago) (1 children)

The ide could crash in a weird way and thus crashing the whole system, had some crashes on some intellij IDE's but i never crashed.

Do you still use Cloudflare Zero Trust client? If not, best remove that, to at least remove that possibility. Check some logs of your IDE to check if they logged some errors. Check htop ocasionally too, could be something that is eating resources too.

What packages did you update recently? Do you have a backup to rollback to?

Otherwise i dont have the experience with wayland.

And i assume you use a ubuntu based distribution, can you tell us what exactly?

[–] qaz@lemmy.world 1 points 7 months ago

I don't use the zero trust client. I removed the package several months ago but there is still something left on my system trying to connect to it but I haven't been able to find it.

[–] Pantherina@feddit.de 2 points 7 months ago

You should report this to your distro, run journalctl -f on startup and for sure give the output of kinfo to give a usable bug report.