You are not logged in.
Hello all. My desktop immediately freezes when I open some apps.
I can open Google Chrome or Chromium, but not both at the same time or the desktop will freeze. If I open Zoom, it freezes 100% of the time. By freezing I mean immediate freezing, cursor won't move, TTYs becomes inaccessible and I can only reboot by pressing the button.
This is the output of
journalctl -b-1Maybe this is unrelated, but my
cat /etc/fstab# /dev/nvme0n1p7
UUID=5dc19f68-0fc8-4eaa-ab21-92dc668f7eda / ext4 rw,relatime,data=ordered 0 1
# /dev/nvme0n1p8
UUID=60aa1e5a-d947-4eee-a96b-c981d74a003f /home ext4 rw,relatime,data=ordered 0 2
# /dev/nvme0n1p5
UUID=5dc19f68-0fc8-4eaa-ab21-92dc668f7eda / ext4 rw,relatime 0 1
# /dev/nvme0n1p6 LABEL=Linux\134x20Swap
UUID=e7e3115a-c763-4817-b20e-f33d97ec6f30 none swap defaults 0 0
# /dev/nvme0n1p1
UUID=BB0B-7A60 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2... shows two / partitions, of which /dev/nvme0n1p7 and says /dev/nvme0n1p8 is my home partition, but
df Filesystem Size Used Avail Use% Mounted on
dev 7.8G 0 7.8G 0% /dev
run 7.8G 1.5M 7.8G 1% /run
/dev/nvme0n1p5 75G 54G 18G 76% /
tmpfs 7.8G 0 7.8G 0% /dev/shm
tmpfs 7.8G 184K 7.8G 1% /tmp
/dev/nvme0n1p1 500M 100M 400M 21% /boot
/dev/nvme0n1p7 147G 123G 17G 89% /home
tmpfs 1.6G 52K 1.6G 1% /run/user/1000...shows /dev/nvme0n1p7 is my /home partition.
This whole problem started happening when the bootloader was messed up by the laptop turning off mid boot and my having to reinstall the bootloader, so that's why I mentioned it. Any help is appreciated. Thanks!
Last edited by Trvzn (2023-07-19 14:12:54)
Offline
A couple other issues with that fstab. First, the UUID is mounted twice on '/' using different options.
Second, the comments indicate both /dev/nvme0n1p7 and /dev/nvme0n1p5 have the same UUID. Is that an error in the comments? Or have you two partitions with the same UUID? Yes, that is possible. But, p7 seems to be mounted at /home.
What is the output of lsblk -f ?
However, this all seem like we are chasing the wrong thing. What desktop environment / window manager are you using?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Thanks for replying, ewaller!
What is the output of lsblk -f ?
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1 vfat FAT32 BB0B-7A60 399.1M 20% /boot
├─nvme0n1p2
├─nvme0n1p3 ntfs OS E4AC9478AC944748
├─nvme0n1p4 ntfs C660002A60002431
├─nvme0n1p5 ext4 1.0 5dc19f68-0fc8-4eaa-ab21-92dc668f7eda 16.6G 73% /
├─nvme0n1p6 swap 1 Linux Swap e7e3115a-c763-4817-b20e-f33d97ec6f30 [SWAP]
├─nvme0n1p7 ext4 1.0 60aa1e5a-d947-4eee-a96b-c981d74a003f 16.6G 84% /home
├─nvme0n1p8 ntfs WINRETOOLS F29C6A459C6A0507
├─nvme0n1p9 ntfs Image 22D26A6DD26A455F
└─nvme0n1p10 ntfs DELLSUPPORT 62C4EF12C4EEE76F I'm using openbox on an openbox-session, no destop environment.
Offline
It looks like you should remove line number 2-4 from your fstab (the first UUID, a blank line, and the incorrect comment line).
But 1) systemd is - for better or worse - likely ignoring that fstab, and 2) it's almost certainly unrelated to the freezing issue. Given that zoom is a consistent / predictable cause of this freeze, it might be better to focus diagnostics there first. Which zoom package are you using? And how do you launch it? Can you start it from a terminal and redirect *all* output to a file? If so, does that file exist after the reboot (and if so what's in it)?:
# for example:
zoom & > ~/zoom.logLast edited by Trilby (2023-07-19 17:39:36)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Thanks for the help, Tribly! I'm using this AUR package
aur/zoom 5.15.3-1 (+610 10.49) (Installed)
Video Conferencing and Web Conferencing ServiceI tried running it from the terminal using the command you suggested. Zoom freezes the desktop, as expected. The output file is created, but it's empty.
EDIT:
It looks like you should remove line number 2-4 from your fstab (the first UUID, a blank line, and the incorrect comment line).
Done, but to no avail as you suspected.
Last edited by Trvzn (2023-07-19 18:48:23)
Offline