You are not logged in.

#1 2022-01-30 16:33:26

stabwound
Member
Registered: 2015-07-24
Posts: 48

How to diagnose freeze on resume from suspend?

Thinkpad X1E G3 - it has a discrete Nvidia 1650ti GPU.  I originally installed PopOS on this machine because I was driving myself crazy trying to get it to function properly with the Nvidia graphics, but eventually caved and came back to Arch to make it work because I just prefer it.

So far so good in most ways, but still have some niggling problems.

I'm running BTRFS on LUKS, I have 16GB RAM and have setup a 32GB swap file (overkill I know). I believe it's properly setup in fstab.

Sometimes I can resume from suspend, but I estimate about 90% of the time I'm greeted with a non-blinking underscore on a black background in the upper left corner of the screen.

How can I diagnose this problem?

Offline

#2 2022-01-30 16:46:35

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 6,350

Re: How to diagnose freeze on resume from suspend?

Check the journal and X.Org log (if you use X) for clues.

Do you still suffer this problem if you use nouveau? If in doubt blame the blob big_smile

Offline

#3 2022-02-04 16:35:36

stabwound
Member
Registered: 2015-07-24
Posts: 48

Re: How to diagnose freeze on resume from suspend?

These freezes happen even when I'm using the intel modesetting driver and have the nvidia driver disabled.

I don't see much of anything in the logs. It seems to me like it suspends properly, but when trying to wake up it just hard hangs, not even putting anything in the log. Nothing stands out in the Xorg log either.

Honestly the Linux experience on this machine has been nothing short of infuriating and I am never buying a laptop with an Nvidia GPU ever again.

Journal:

Feb 03 23:03:01 leptop systemd[1]: Reached target Sleep.
Feb 03 23:03:01 leptop systemd[1]: Starting NVIDIA system suspend actions...
Feb 03 23:03:01 leptop suspend[225128]: nvidia-suspend.service
Feb 03 23:03:01 leptop logger[225128]: <13>Feb  3 23:03:01 suspend: nvidia-suspend.service
Feb 03 23:03:03 leptop bluetoothd[854]: Endpoint unregistered: sender=:1.97 path=/MediaEndpoint/A2DPSource/ldac
Feb 03 23:03:03 leptop bluetoothd[854]: Endpoint unregistered: sender=:1.97 path=/MediaEndpoint/A2DPSink/aptx_hd
Feb 03 23:03:03 leptop bluetoothd[854]: Endpoint unregistered: sender=:1.97 path=/MediaEndpoint/A2DPSource/aptx_hd
Feb 03 23:03:03 leptop bluetoothd[854]: Endpoint unregistered: sender=:1.97 path=/MediaEndpoint/A2DPSink/aptx
Feb 03 23:03:03 leptop bluetoothd[854]: Endpoint unregistered: sender=:1.97 path=/MediaEndpoint/A2DPSource/aptx
Feb 03 23:03:03 leptop bluetoothd[854]: Endpoint unregistered: sender=:1.97 path=/MediaEndpoint/A2DPSource/aac
Feb 03 23:03:03 leptop bluetoothd[854]: Endpoint unregistered: sender=:1.97 path=/MediaEndpoint/A2DPSink/sbc
Feb 03 23:03:03 leptop bluetoothd[854]: Endpoint unregistered: sender=:1.97 path=/MediaEndpoint/A2DPSource/sbc
Feb 03 23:03:03 leptop systemd[1]: nvidia-suspend.service: Deactivated successfully.
Feb 03 23:03:03 leptop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 23:03:03 leptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 23:03:03 leptop systemd[1]: Finished NVIDIA system suspend actions.
Feb 03 23:03:03 leptop systemd[1]: Starting System Suspend...
Feb 03 23:03:03 leptop kernel: audit: type=1130 audit(1643947383.395:135): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 23:03:03 leptop kernel: audit: type=1131 audit(1643947383.395:136): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 23:03:03 leptop systemd-sleep[225175]: [17] INFO: # Pre-suspend hook
Feb 03 23:03:03 leptop systemd-sleep[225175]: [17] INFO: Previous state was: {'type': 'done', 'switch_id': '20220203T195903', 'current_mode': 'nvidia'}
Feb 03 23:03:03 leptop systemd-sleep[225175]: [19] INFO: Switching option: none
Feb 03 23:03:03 leptop systemd-sleep[225175]: [19] INFO: Nothing to do
Feb 03 23:03:03 leptop systemd-sleep[225175]: [19] INFO: Writing state {'type': 'pending_post_resume', 'switch_id': '20220203T195903', 'current_mode': 'nvidia'}
Feb 03 23:03:03 leptop systemd-sleep[225175]: [19] INFO: Pre-suspend hook completed successfully.
Feb 03 23:03:03 leptop systemd-sleep[225172]: Entering sleep state 'suspend'...
Feb 03 23:03:03 leptop kernel: PM: suspend entry (deep)
-- Boot 018777b747274286affc08dacda92669 --
Feb 04 10:43:40 leptop kernel: Linux version 5.15.19-1-lts (linux-lts@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Tue, 01 Feb 2022 17:37:22 +0000
Feb 04 10:43:40 leptop kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts root=UUID=aa429bb2-82b6-47f5-be1d-28e04a003500 rw rootflags=subvol=@ quiet cryptdevice=UUID=aab1ff91-f7eb-4ffc-a06d-d5f9543a5186:luks-aab1ff91-f7eb-4ffc-a06d-d5f9543a5186 root=/dev/mapper/luks-aab1ff91-f7eb-4ffc-a06d-d5f9543a5186 resume=/dev/mapper/luks-aab1ff91-f7eb-4ffc-a06d-d5f9543a5186 loglevel=3 resume_offset=22434304 nowatchdog nvme_load=YES nvidia-drm.modeset=1

Offline

#4 2022-02-04 16:36:57

kik4444
Member
Registered: 2022-02-04
Posts: 9

Re: How to diagnose freeze on resume from suspend?

I believe I have been facing this exact problem ever since I updated my system in mid-to-late December.

  • My laptop has an Intel i5-8250U + Nvidia MX 150, 12GB Ram

  • I'm currently on linux-lts 5.15.18-1 with the driver nvidia-lts (but before I used nvidia-dkms and it made no difference).

  • I'm running Xorg + KDE + SDDM.

  • My root partition is BTRFS + LUKS. Only /efi is a separate FAT32 partition. / and /home are different subvolumes, but I always snapshot and restore them together. I have no swap.

  • I additionally use xf86-video-intel, bbswitch-dkms, tlp and optimus-manager for power management and GPU switching.

  • /etc/tlp.conf also has an additional parameter SATA_LINKPWR_ON_BAT=max_performance because I read a year ago that this prevented BTRFS corruption, but this is no longer mentioned in the wiki pages of BTRFS or TLP so idk if it's still needed

Like OP, when I put my laptop to sleep, it has a good chance to freeze on resume. It happens perhaps 50% of the time. When I wake it up I only see a black screen with a non-blinking underscore in the top-left corner, occasionally my cursor shows up too, but otherwise it is frozen. Ctrl+Alt+F2 is not able to switch to another TTY. I am forced to do a hard reboot to recover every time. However, Alt+Sysrq+b is able to force a reboot. Afterwards nothing is recorded in the systemd journal between putting it to sleep and the next reboot.

This problem only started happening after an update in mid-to-late December. Before that I never had problems with suspend and resume and I never touched any configs around the time of that update.

I tried uninstalling xf86-video-intel, bbswitch-dkms, tlp and optimus-manager and cleaning them up, but that didn't fix anything. Instead, my laptop appeared to be using both GPUs like it does when optimus manager sets it in Hybrid mode (only Xorg would run on the Nvidia GPU). So I restored a prior snapshot to get the packages back.

As for nouveau, I don't think it's an option because it seems it breaks a dependency for Steam and as far as I know it's not generally recommended if you want to run most games.

I have also noticed that whenever my laptop does successfully wake from sleep, often mpv and ungoogled-chromium start taking up to 15 seconds longer to start up and become visible on the screen. Though I have not noticed this behavior with other programs so far. This began happening after the wake problem appeared.

This may be related, I'm not sure, but around the same time I also started having problems with wine like in this thread https://bbs.archlinux.org/viewtopic.php?id=272856. After a reboot, starting a game through wine would work the first time, but subsequent runs would result in errors and the wine process would need to be forcibly killed. Rebooting fixes it, but then again it works only once. Like the other thread suggested, switching to the Nvidia GPU or to Hybrid mode with optimus manager fixes this problem indefinitely until the next reboot, even if I then switch back to Integrated mode. Again, I'm not sure if this is related or not, but this problem appeared around the same time as my sleep/resume problem and is still present.

Also, staying on the Nvidia GPU or in Hybrid mode full time does not solve the occasional freeze when resuming from sleep.

I was starting to lose hope this would get fixed on its own after over a month had passed so I came to look for help. It looks like I may not be alone in this. To be fair, my laptop is still perfectly usable and stable, but it's really annoying that sleep has turned into an uncertain gamble (plus the other 2 problems which may or may not be related).

Any suggestions to find out what has started causing this?

Last edited by kik4444 (2022-02-05 09:01:38)

Offline

#5 2022-02-04 17:15:14

stabwound
Member
Registered: 2015-07-24
Posts: 48

Re: How to diagnose freeze on resume from suspend?

We have a similar setup and the same problem: nothing is shown in the logs, making it extremely difficult to diagnose. Which kernel are you using? I'm on the LTS kernel because bluetooth seems to be broken in the mainline kernel for this laptop.

Offline

#6 2022-02-06 00:00:14

stabwound
Member
Registered: 2015-07-24
Posts: 48

Re: How to diagnose freeze on resume from suspend?

So I was running XFCE + i3wm and the freeze issue was happening. Looking at the logs, the whole machine was freezing during suspend, not on resume. I tried switching to just i3wm and lo and behold, suspend now seems to be working perfectly. I followed a tutorial to setup i3 + XFCE but I guess there was some conflict with the setup. Hibernation still doesn't work, but that's another story.

Offline

#7 2022-02-06 08:33:47

kik4444
Member
Registered: 2022-02-04
Posts: 9

Re: How to diagnose freeze on resume from suspend?

stabwound wrote:

So I was running XFCE + i3wm and the freeze issue was happening. Looking at the logs, the whole machine was freezing during suspend, not on resume. I tried switching to just i3wm and lo and behold, suspend now seems to be working perfectly. I followed a tutorial to setup i3 + XFCE but I guess there was some conflict with the setup. Hibernation still doesn't work, but that's another story.

Our setups are not that similar imo.

Still though, through some trial and error, I discovered that disabling KDE's compositor with Alt + Shift + F12 before suspending decreased the probability of freezing on resume. I was able to get through a whole day with multiple suspensions without problems. Today however it froze on the second resume of the day.

However, with the compositor disabled, when it freezes, it doesn't show a black screen. Instead it shows my entire login screen like normal and the clock is stuck on the time of the suspension. No buttons work except the kernel SysRq shortcuts. And of course, nothing is added to the journal.

EDIT: Nevermind, the above was just a coincidence this time. Whether the compositor is on or off before suspend is irrelevent. It also does not matter whether the discrete Nvidia GPU is used by default, or is in a Hybrid stand-by mode and nvidia-smi produces the following

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 510.47.03    Driver Version: 510.47.03    CUDA Version: 11.6     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   35C    P8    N/A /  N/A |      0MiB /  2048MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

or it is completely off and produces the following

NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

None of it affects whether the laptop will reliably resume from suspend. It appears the last time was just a lucky coincidence.

Last edited by kik4444 (2022-02-07 11:20:12)

Offline

#8 2022-02-06 15:45:50

stabwound
Member
Registered: 2015-07-24
Posts: 48

Re: How to diagnose freeze on resume from suspend?

I was wrong about disabling XFCE fixing the problem. I was able to suspend/resume 4-5 times in a row, but now it's not working again. Joy.

Offline

#9 2022-02-07 14:59:48

stabwound
Member
Registered: 2015-07-24
Posts: 48

Re: How to diagnose freeze on resume from suspend?

I did the atomic method and did a BTRFS snapshot rollback to the initial install, suspend seems to work perfectly. I believe my freezes have something to do with optimus-manager or TLP, most likely optimus-manager. You could try disabling optimus-manager completely and see if it fixes the problem.

Offline

#10 2022-02-07 15:44:24

kik4444
Member
Registered: 2022-02-04
Posts: 9

Re: How to diagnose freeze on resume from suspend?

stabwound wrote:

I did the atomic method and did a BTRFS snapshot rollback to the initial install, suspend seems to work perfectly. I believe my freezes have something to do with optimus-manager or TLP, most likely optimus-manager. You could try disabling optimus-manager completely and see if it fixes the problem.

I already tried uninstalling bbswitch-dkms, tlp and optimus-manager after running "optimus-manager --cleanup" and disabling their services. But it didn't fix anything. Admittedly, some of their conf files were left in /etc, but I didn't bother deleting them cause I figured they didn't matter since the programs that read them were removed. You should try suspending/resuming for at least a day to check if it's really fixed.

Offline

#11 2022-02-09 15:53:00

kik4444
Member
Registered: 2022-02-04
Posts: 9

Re: How to diagnose freeze on resume from suspend?

Well I have some good and some bad news. I completely uninstalled optimus-manager, its .conf files and the xorg .conf files it generated (they were auto-removed by the uninstallation).

The good news is that the problem with Wine that I mentioned in my first post (which is also the subject of this thread https://bbs.archlinux.org/viewtopic.php?id=272856) is fully fixed now as far as I can tell. optimus-manager was likely to blame.
The bad (?) news is that removing optimus manager did not fix my freeze on resume problem. This means that this problem is almost certainly not related to optimus-manager.

Furthermore, I have reason to believe that this freezing problem is related to how long the laptop stays asleep. Today I installed lib32-mesa-utils (I noticed I was missing it) and did 29 suspends and resumes before the removal of optimus-manager. Every time, I woke up the laptop within 1-3 minutes of putting it to sleep, and every time it resumed without problems. However, when I waited 3 hours before resuming it, it froze. Later, even after removing optimus-manager, when I waited 2 hours before resuming it, it froze again.

Therefore, statistically speaking, the freeze is likely caused only when the laptop has been asleep for a long period of time. This also suggests that the freeze happens at the moment of resuming and not suspending.

Last edited by kik4444 (2022-02-09 16:01:54)

Offline

#12 2022-02-10 00:40:45

slip
Member
Registered: 2019-09-09
Posts: 10

Re: How to diagnose freeze on resume from suspend?

I'd like to chime in and say that I might be experience the same issues, however, I'm 100% AMD and on a desktop. My resuming from sleep takes around 10 to 20 seconds. It varies.

Ryzen 3950x
rx 5700xt
btrfs on nvme
bspwm.
It has been happening on the last few zen kernel revisions.

Here's a paste of the complete journal from suspend to wake

So if these symptoms seem to match up, which they seem to be close, then it might not be hardware specific. This paste was without any lock screen as well. When I run my typical betterlockscreen setup, it will resume and say `locking failed`, even though it is locked. It acts like it was cut short and resumed its locking function after resuming. Lastly, this is on a fresh install as I have installed a new drive and wanted to build in a different arrangement.

Edit - Additionally, I have just arbitrarily tried an older kernel, and the issue persists, however, are these suspend targets out of order? I've never paid attention to them before so I don't know if this is common

Feb 09 16:44:18 europa systemd-networkd[846]: enp6s0: DHCPv6 lease lost
Feb 09 16:44:18 europa systemd-resolved[1132]: Clock change detected. Flushing caches.
Feb 09 16:44:18 europa systemd-logind[1402]: Operation 'sleep' finished.
Feb 09 16:44:18 europa systemd[1]: Stopped target Suspend.
Feb 09 16:44:18 europa systemd[1]: Reached target Suspend.
Feb 09 16:44:18 europa systemd[1]: Stopped target Sleep.
Feb 09 16:44:18 europa systemd-networkd[846]: enp7s0: Gained carrier
Feb 09 16:44:18 europa systemd[1]: Finished System Suspend.
Feb 09 16:44:18 europa systemd[1]: systemd-suspend.service: Deactivated successfully.
Feb 09 16:44:18 europa systemd-networkd[846]: enp7s0: DHCPv6 lease lost
Feb 09 16:44:18 europa systemd-sleep[4215]: System returned from sleep state.
Feb 09 16:44:18 europa systemd-networkd[846]: enp7s0: DHCP lease lost
Feb 09 16:44:18 europa systemd-networkd[846]: enp7s0: Lost carrier

Last edited by slip (2022-02-11 00:08:07)

Offline

#13 2022-02-11 06:42:33

kik4444
Member
Registered: 2022-02-04
Posts: 9

Re: How to diagnose freeze on resume from suspend?

Yesterday I updated my system and along with it came KDE 5.24. At the same time, I tried switching to Wayland cause I was curious to see how far along it's come, especially on Nvidia Optimus hardware. I use KDE anyway so switching was super simple and there was almost nothing I had to change to accomodate Wayland. As far as I've tested, most things seem to work better than Xorg, except for a few cosmetic things.

However, Wayland did not fix my freeze on resume problem. Am I correct in assuming that this means that Xorg is not causing this problem then?

P.S. A few programs like conky still work in Xorg under XWayland, and /usr/lib/Xorg still works full time under my Nvidia GPU in the Hybrid mode of my laptop which is the default after removing optimus-manager. Because of all this I'm not sure if it's safe to rule out Xorg as the cause of the problem, assuming it's related at all.

Offline

#14 2022-02-11 23:00:21

slip
Member
Registered: 2019-09-09
Posts: 10

Re: How to diagnose freeze on resume from suspend?

I have narrowed my issue down to an HDD I use for automated backups. I guess it spinning up on resume is enough to cause the entire system to hault until it is ready. I verified after multiple reboots with it plugged in and unplugged. Do you have anything like that?

Offline

#15 2022-02-11 23:36:56

kik4444
Member
Registered: 2022-02-04
Posts: 9

Re: How to diagnose freeze on resume from suspend?

slip wrote:

I have narrowed my issue down to an HDD I use for automated backups. I guess it spinning up on resume is enough to cause the entire system to hault until it is ready. I verified after multiple reboots with it plugged in and unplugged. Do you have anything like that?

Are you implying that your system eventually unfreezes?

I do have an HDD on my laptop too, but I've had it for years and this freezing problem only started happening in December. And when the system freezes on resume, it doesn't unfreeze, Ctrl + Alt + F2-6 cannot change the TTY, and I'm only left with the option to reboot by holding the power button or pressing Alt + SysRq + b.

Offline

#16 2022-02-12 00:01:26

slip
Member
Registered: 2019-09-09
Posts: 10

Re: How to diagnose freeze on resume from suspend?

Oh, okay. I read the comment -

I have also noticed that whenever my laptop does successfully wake from sleep, often mpv and ungoogled-chromium start taking up to 15 seconds longer to start up and become visible on the screen. Though I have not noticed this behavior with other programs so far. This began happening after the wake problem appeared.

And based my experience on that, as it seemed possibly similar. Mine doesn't ever fail to resume.

Offline

#17 2022-02-16 02:13:24

stabwound
Member
Registered: 2015-07-24
Posts: 48

Re: How to diagnose freeze on resume from suspend?

I've been running for over a week now and I'm positive that my optimus-manager setup was causing the issues with suspend/wakeup. I've done so 20+ times and its worked flawlessly other than one time where the machine seems to have woken up on its own with the lid closed.

Offline

#18 2022-03-19 21:04:13

falko17
Member
Registered: 2022-03-19
Posts: 1

Re: How to diagnose freeze on resume from suspend?

kik4444 wrote:

Furthermore, I have reason to believe that this freezing problem is related to how long the laptop stays asleep. [...] Every time, I woke up the laptop within 1-3 minutes of putting it to sleep, and every time it resumed without problems. However, when I waited 3 hours before resuming it, it froze. Later, even after removing optimus-manager, when I waited 2 hours before resuming it, it froze again.

Therefore, statistically speaking, the freeze is likely caused only when the laptop has been asleep for a long period of time. This also suggests that the freeze happens at the moment of resuming and not suspending.

Yes, I can confirm this behavior (freeze is more likely on longer sleeps) on my machine, which also appears to have the same issue. However, I'm using an AMD graphics card (RX 570) and CPU (Ryzen 5 5600X), so possibly this issue isn't related to Nvidia.
I'm also using sway on Wayland (with kernel version 5.16.14), which should lower the possibility of Xorg being the culprit.

When the issue occurs and the system freezes, the logs seem to cut out during suspend, not resume. These are the last few lines from the journal:

Mar 19 19:15:46 machine systemd[1]: Reached target Sleep.
Mar 19 19:15:46 machine systemd[1]: Starting System Suspend...
Mar 19 19:15:46 machine wpa_supplicant[608]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 19 19:15:46 machine systemd-sleep[84139]: Entering sleep state 'suspend'...
Mar 19 19:15:46 machine kernel: PM: suspend entry (deep)
Mar 19 19:15:46 machine wpa_supplicant[608]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 19 19:15:46 machine wpa_supplicant[608]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Mar 19 19:15:46 machine kernel: Filesystems sync: 0.052 seconds

As the log messages themselves imply, the timestamps are from the time I suspended the system. Nothing was written to the log after I resumed the system and the freeze occurred.

Offline

#19 2022-05-02 07:46:53

kik4444
Member
Registered: 2022-02-04
Posts: 9

Re: How to diagnose freeze on resume from suspend?

I have no idea how it happened, but my problem recently got fixed all on its own. It's been several days now and I haven't had any problems resuming from suspend, no matter the duration. All I can say is that it got fixed after an update which updated all of these packages:

2022-04-24 18:04:23     freetype2
2022-04-24 18:04:23     fribidi
2022-04-24 18:04:23     glib2
2022-04-24 18:04:23     gtk-update-icon-cache
2022-04-24 18:04:23     iana-etc
2022-04-24 18:04:23     icu
2022-04-24 18:04:23     librsvg
2022-04-24 18:04:23     libxml2
2022-04-24 18:04:23     xorgproto
2022-04-24 18:04:23     zlib
2022-04-24 18:04:24     adwaita-icon-theme
2022-04-24 18:04:24     boost-libs
2022-04-24 18:04:24     coreutils
2022-04-24 18:04:24     jack2
2022-04-24 18:04:24     json-c
2022-04-24 18:04:24     libcap
2022-04-24 18:04:24     libcap-ng
2022-04-24 18:04:24     libmnl
2022-04-24 18:04:24     libnfnetlink
2022-04-24 18:04:24     libnl
2022-04-24 18:04:25     aegisub
2022-04-24 18:04:25     appstream
2022-04-24 18:04:25     at-spi2-core
2022-04-24 18:04:25     libinput
2022-04-24 18:04:25     tracker3
2022-04-24 18:04:27     appstream-qt
2022-04-24 18:04:27     qt5-base
2022-04-24 18:04:31     ark
2022-04-24 18:04:31     gptfdisk
2022-04-24 18:04:31     libaio
2022-04-24 18:04:31     parted
2022-04-24 18:04:31     qt5-wayland
2022-04-24 18:04:31     xfsprogs
2022-04-24 18:04:32     baloo-widgets
2022-04-24 18:04:32     blas
2022-04-24 18:04:32     exiv2
2022-04-24 18:04:32     jasper
2022-04-24 18:04:32     minizip
2022-04-24 18:04:32     python-py7zr
2022-04-24 18:04:32     python-pyqt5-sip
2022-04-24 18:04:32     qt5-webengine
2022-04-24 18:04:34     calibre
2022-04-24 18:04:35     conky
2022-04-24 18:04:35     dialog
2022-04-24 18:04:35     dolphin
2022-04-24 18:04:35     enchant
2022-04-24 18:04:35     kio-extras
2022-04-24 18:04:35     libbsd
2022-04-24 18:04:35     smbclient
2022-04-24 18:04:36     fcitx5-mozc
2022-04-24 18:04:36     ffmpegthumbs
2022-04-24 18:04:36     filelight
2022-04-24 18:04:36     git
2022-04-24 18:04:37     glslang
2022-04-24 18:04:37     gspell
2022-04-24 18:04:37     gvfs
2022-04-24 18:04:37     gwenview
2022-04-24 18:04:37     imagemagick
2022-04-24 18:04:37     intel-ucode
2022-04-24 18:04:37     kaccounts-integration
2022-04-24 18:04:37     libkdcraw
2022-04-24 18:04:37     signon-kwallet-extension
2022-04-24 18:04:38     jdk-openjdk
2022-04-24 18:04:38     jre-openjdk
2022-04-24 18:04:38     jre-openjdk-headless
2022-04-24 18:04:38     kamoso
2022-04-24 18:04:38     openexr
2022-04-24 18:04:38     raptor
2022-04-24 18:04:39     kate
2022-04-24 18:04:39     kcharselect
2022-04-24 18:04:39     kdeconnect
2022-04-24 18:04:39     kdesdk-thumbnailers
2022-04-24 18:04:39     kdialog
2022-04-24 18:04:39     kdiskmark
2022-04-24 18:04:39     konsole
2022-04-24 18:04:39     kwayland
2022-04-24 18:04:40     kpmcore
2022-04-24 18:04:40     ksystemlog
2022-04-24 18:04:40     kwalletmanager
2022-04-24 18:04:40     lapack
2022-04-24 18:04:43     lib32-at-spi2-core
2022-04-24 18:04:43     lib32-freetype2
2022-04-24 18:04:43     lib32-fribidi
2022-04-24 18:04:43     lib32-glib2
2022-04-24 18:04:43     lib32-icu
2022-04-24 18:04:43     lib32-libcap
2022-04-24 18:04:43     lib32-librsvg
2022-04-24 18:04:43     lib32-libxml2
2022-04-24 18:04:43     lib32-zlib
2022-04-24 18:04:43     libcdr
2022-04-24 18:04:43     libe-book
2022-04-24 18:04:44     libical
2022-04-24 18:04:44     libkexiv2
2022-04-24 18:04:44     libksane
2022-04-24 18:04:44     libmspub
2022-04-24 18:04:44     libpgm
2022-04-24 18:04:44     libqalculate
2022-04-24 18:04:44     libqxp
2022-04-24 18:04:44     libvisio
2022-04-24 18:04:44     libzmf
2022-04-24 18:04:48     libreoffice-fresh
2022-04-24 18:04:51     linux
2022-04-24 18:04:56     linux-headers
2022-04-24 18:04:58     linux-lts
2022-04-24 18:05:03     linux-lts-headers
2022-04-24 18:05:03     nodejs
2022-04-24 18:05:04     nvidia
2022-04-24 18:05:04     nvidia-lts
2022-04-24 18:05:04     okular
2022-04-24 18:05:04     partitionmanager
2022-04-24 18:05:04     perl-file-listing
2022-04-24 18:05:04     php
2022-04-24 18:05:04     plasma-framework
2022-04-24 18:05:05     print-manager
2022-04-24 18:05:05     python-gobject
2022-04-24 18:05:05     python-importlib_resources
2022-04-24 18:05:05     python-pikepdf
2022-04-24 18:05:07     qbittorrent
2022-04-24 18:05:07     qt5-webkit
2022-04-24 18:05:07     qt6-base
2022-04-24 18:05:07     rsync
2022-04-24 18:05:08     shaderc
2022-04-24 18:05:08     skanlite
2022-04-24 18:05:08     spectacle
2022-04-24 18:05:08     suitesparse
2022-04-24 18:05:08     tesseract
2022-04-24 18:05:08     vhba-module-dkms
2022-04-24 18:05:08     webkit2gtk
2022-04-24 18:05:11     wine-staging
2022-04-24 18:05:11     winetricks
2022-04-24 18:05:11     xdg-desktop-portal
2022-04-24 18:05:11     xorg-xauth
2022-04-24 18:05:11     yakuake
2022-04-24 18:05:11     zsh
2022-04-24 18:09:39     vscodium-bin
2022-04-24 18:09:49     vscodium-marketplace
2022-04-24 18:10:03     ocrmypdf
2022-04-24 18:10:36     ungoogled-chromium

Offline

Board footer

Powered by FluxBB