0

I'm always experiencing freezes and slowdown in Awesome WM. You can't even go to the virtual terminal to investigate, so all i have to do is shutdown the laptop by holding the power button. The freezing has been happening more frequent than before.

How do i investigate what causes such problems?

Upon just investigating, i've stumbled upon this file ~/.xsession-errors The contents are posted below. I don't have much know-how to decipher those errors.

dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/chan-dev/.Xauthority
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting SHELL=/usr/bin/zsh
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-awesome:/etc/xdg
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting LANGUAGE=en_PH:en
dbus-update-activation-environment: setting DESKTOP_SESSION=awesome
dbus-update-activation-environment: setting PWD=/home/chan-dev
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=awesome
dbus-update-activation-environment: setting LOGNAME=chan-dev
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting XAUTHORITY=/home/chan-dev/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/chan-dev
dbus-update-activation-environment: setting GDM_LANG=en_US
dbus-update-activation-environment: setting HOME=/home/chan-dev
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting LANG=en_PH.UTF-8
dbus-update-activation-environment: setting _JAVA_AWT_WM_NONREPARENTING=1
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting USER=chan-dev
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting SHLVL=1
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/awesome:/usr/local/share:/usr/share:/var/lib/snapd/desktop
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
dbus-update-activation-environment: setting GDMSESSION=awesome
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
2021-08-11 20:14:11 W: awesome: spawn_child_exited:389: Unknown child 1184 exited with status 0
2021-08-11 20:14:12 W: awesome: a_glib_poll:438: Last main loop iteration took 0.717730 seconds! Increasing limit for this warning to that value.
[1239:1239:0811/201425.412126:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
2021-08-11 20:14:30 W: awesome: a_glib_poll:438: Last main loop iteration took 0.975546 seconds! Increasing limit for this warning to that value.
2021-08-11 20:14:44 W: awesome: a_glib_poll:438: Last main loop iteration took 1.511648 seconds! Increasing limit for this warning to that value.
Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
[1242:1245:0811/202233.794375:ERROR:ssl_client_socket_impl.cc(981)] handshake failed; returned -1, SSL error code 1, net_error -101
Fontconfig error: Cannot load default config file: No such file: (null)

Btw, i'm currently using awesome wm v4.3 under xubuntu 20.04.

The.Wolfgang.Grimmer
  • 131
  • 2
  • You need to use the power button? If SysRq commands don't allow a safe shutdown (closing *fs* to reboot/poweroff etc) then you have kernel issues and it's not related to a WM freeze, but more serious. Is there a reason why you're not safely shutting down & resorting to power button? (*or aren't aware of the SysRq key which allows you to command the linux kernel directly & safely*?) as that's useful detail on system health. – guiverc Aug 11 '21 at 12:49
  • @guiverc i'm pretty new to linux so i have minimal knowledge of some things. Yup, i'm not aware of SysRq, what does it actually do? Is it sort of similar to CTRL+ALT+DELETE in windows? – The.Wolfgang.Grimmer Aug 11 '21 at 12:54
  • 1
    No very different; REISUB is the most common command; but if you don't remember the commands, grab a phone and search "magic sysrq" and the wikipedia article is usually at or near top (https://en.wikipedia.org/wiki/Magic_SysRq_key) which is as good as any on what command choices you have (ie. saving you from remembering commands like resiub/reisuo etc). It allows you to directly command the linux kernel (would work on a android phones too if you had a real keyboard attached; and not on-screen keyboard that requires GUI to be operating!). You use letters to give commands; the REISUB is 6 cmds – guiverc Aug 11 '21 at 13:02
  • thanks a lot, i will first try to digest everything. It's pretty exciting and daunting to fully use Linux after coming from Windows. :) – The.Wolfgang.Grimmer Aug 11 '21 at 13:05
  • 1
    also fyi: SysRq is a key on keyboards; however many *modern smaller* keyboards don't have SysRq printed any longer (it was printed in color on the front of the PrintScreen key) and often requires an additional Fn & you to know where the key is positioned (eg. dell 2020 & 2021 models don't have it printed), but if you know where the key is on an older key; you'll find it still works even if printing isn't put on modern keyboards. – guiverc Aug 11 '21 at 13:06
  • yup, so far i've stumbled upon the combination required for Dell machines https://askubuntu.com/a/343750/1389504 and also in this tutorial about SysRq https://www.youtube.com/watch?v=ZiX327d8Ys0 – The.Wolfgang.Grimmer Aug 11 '21 at 13:17

0 Answers0