Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Albert is virtually unresponsive with LightlyShaders enabled (Plasma 6.0.2, Wayland, Arch w/ CachyOS packages) #1375

Closed
FezzedOne opened this issue Mar 14, 2024 · 15 comments
Assignees

Comments

@FezzedOne
Copy link

Package source

Chaotic-AUR repository

App report

Albert version: 0.23.0
           Build date: Mar  7 2024 10:20:44
           Qt version: 6.6.2
            Build ABI: x86_64-little_endian-lp64
   Build architecture: x86_64
     CPU architecture: x86_64
          Kernel type: linux
       Kernel version: 6.8.0-2-cachyos
                   OS: Arch Linux
              OS type: arch
           OS version: unknown
        Platform name: xcb
           Style name: breeze
     Available styles: Breeze, Oxygen, Windows, Fusion
           Icon theme: Cobalt-dark
                 Font: Segoe UI,10,-1,5,400,0,0,0,0,0,0,0,0,0,0,1
             Language: English
               Locale: en_GB
      Binary location: /usr/bin/albert
          Working dir: /home/renofezzedone
            Arguments: /usr/bin/albert
                $LANG: en_GB.UTF-8
$QT_QPA_PLATFORMTHEME: 
                $PATH: /usr/local/sbin:/usr/local/bin:/usr/bin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/lib/rustup/bin
               $SHELL: /bin/zsh
    $XDG_SESSION_TYPE: wayland
 $XDG_CURRENT_DESKTOP: KDE
     $DESKTOP_SESSION: plasma
 $XDG_SESSION_DESKTOP: KDE

Current Behavior

Whenever I attempt to invoke Albert with the Lightly shaders (and blur variant) enabled on Plasma 6.0.2 running on Wayland on freshly updated Arch (last update was only minutes ago, and I'm using CachyOS Plasma packages), Albert renders at around 0.5 FPS, which is (obviously) unusably slow. Even Albert's configuration dialogue is very sluggish (although it seems to render faster). No other application behaves this way — the rest of the desktop remains perfectly responsive. When I disable the Lightly effects and then restart Albert (and optionally also Plasma), Albert becomes fully responsive again, even when I re-enable the effects after Albert is restarted.

Expected Behavior

Albert should be fully responsive with the Lightly shaders enabled.

Anything else?

journalctl -b 0 | grep -i 'albert' (with everything from before the current login truncated):

Mar 14 04:05:43 fezzedone-MSI systemd[11684]: Starting Albert...
Mar 14 04:05:43 fezzedone-MSI systemd[11684]: Started Albert.
Mar 14 04:05:43 fezzedone-MSI systemd[11684]: Started Albert - Launcher.
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [crit:albert] Albert has not been terminated properly. Please check your logs and report an issue.
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Hotkey set to Meta+Space
Mar 14 04:05:43 fezzedone-MSI ksmserver[14331]: 04:05:43 [info:albert] There is another instance of albert running.
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'applications_xdg' at '/usr/lib/albert/libapplications_xdg.so' shadowed by '/usr/lib/albert/libapplications_xdg.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'calculator_qalculate' at '/usr/lib/albert/libcalculator_qalculate.so' shadowed by '/usr/lib/albert/libcalculator_qalculate.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'chromium' at '/usr/lib/albert/libchromium.so' shadowed by '/usr/lib/albert/libchromium.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'clipboard' at '/usr/lib/albert/libclipboard.so' shadowed by '/usr/lib/albert/libclipboard.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'datetime' at '/usr/lib/albert/libdatetime.so' shadowed by '/usr/lib/albert/libdatetime.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'docs' at '/usr/lib/albert/libdocs.so' shadowed by '/usr/lib/albert/libdocs.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'files' at '/usr/lib/albert/libfiles.so' shadowed by '/usr/lib/albert/libfiles.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'hash' at '/usr/lib/albert/libhash.so' shadowed by '/usr/lib/albert/libhash.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'mpris' at '/usr/lib/albert/libmpris.so' shadowed by '/usr/lib/albert/libmpris.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'python' at '/usr/lib/albert/libpython.so' shadowed by '/usr/lib/albert/libpython.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'snippets' at '/usr/lib/albert/libsnippets.so' shadowed by '/usr/lib/albert/libsnippets.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'ssh' at '/usr/lib/albert/libssh.so' shadowed by '/usr/lib/albert/libssh.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'system' at '/usr/lib/albert/libsystem.so' shadowed by '/usr/lib/albert/libsystem.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'terminal' at '/usr/lib/albert/libterminal.so' shadowed by '/usr/lib/albert/libterminal.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'urlhandler' at '/usr/lib/albert/liburlhandler.so' shadowed by '/usr/lib/albert/liburlhandler.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert] Plugin 'websearch' at '/usr/lib/albert/libwebsearch.so' shadowed by '/usr/lib/albert/libwebsearch.so'
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert.ssh] Found 0 ssh hosts.
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [warn:default] QFileSystemWatcher::addPaths: list is empty
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert.chromium] Indexed 0 bookmarks [0 ms]
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert.terminal] Indexed 5297 executables [10 ms]
Mar 14 04:05:43 fezzedone-MSI albert[14275]: 04:05:43 [info:albert.apps] Indexed 139 apps [28 ms]
Mar 14 04:07:05 fezzedone-MSI systemd[11684]: Started albert show.
Mar 14 04:07:06 fezzedone-MSI kwin_wayland_wrapper[15867]: Read timed out. Albert busy?
Mar 14 04:07:06 fezzedone-MSI systemd[11684]: Started albert show.
Mar 14 04:07:08 fezzedone-MSI kwin_wayland_wrapper[15893]: Read timed out. Albert busy?

journalctl -b 0 | grep -i 'lightly':

Mar 14 03:52:13 fezzedone-MSI sudo[4698]: renofezzedone : TTY=pts/1 ; PWD=/home/renofezzedone/.git/LightlyShaders/qt6build ; USER=root ; COMMAND=/usr/bin/make install
Mar 14 03:55:04 fezzedone-MSI sudo[7977]: renofezzedone : TTY=pts/1 ; PWD=/home/renofezzedone/.git/LightlyShaders/qt6build ; USER=root ; COMMAND=/usr/bin/make install
Mar 14 03:56:01 fezzedone-MSI kwin_wayland[8679]: kwin_effect_lightlyshaders: LightlyShaders loaded.
Mar 14 04:04:33 fezzedone-MSI kwin_wayland[11749]: kwin_effect_lightlyshaders: LightlyShaders loaded.
Mar 14 04:05:42 fezzedone-MSI kwin_wayland[13918]: kwin_effect_lightlyshaders: LightlyShaders loaded.

There's no other relevant log info.

@FezzedOne
Copy link
Author

FezzedOne commented Mar 14, 2024

Update: Albert just became fully responsive again after a few minutes of waiting. journalctl -b 0 | grep 'albert' (new log entries):

Mar 14 04:34:33 fezzedone-MSI systemd[11684]: Started albert show.
Mar 14 04:34:33 fezzedone-MSI kwin_wayland_wrapper[17820]: Albert set visible.

Nothing from Lightly though. This has happened before. Whenever I log in, Albert apparently ends up becoming very slow and unresponsive for a few minutes, then mysteriously becomes responsive after several minutes have passed, with no relevant log info explaining what happened. I didn't touch Albert's configuration at all, and I already had disabled Albert's file indexing before this login to rule that out.

@ManuelSchneid3r
Copy link
Member

ManuelSchneid3r commented Mar 14, 2024

Run it with QT_LOGGING_RULES='*.debug=true' albert

@FezzedOne
Copy link
Author

FezzedOne commented Mar 16, 2024

I just found out what caused the unresponsiveness — it's the NVIDIA driver, which also caused a seemingly unrelated kernel freeze (usually with no logs on my end) a few minutes after waking my laptop from sleep. The latest NVIDIA 550.x driver update apparently fixed both Albert's unresponsiveness and (most likely) the kernel freeze. I checked — Albert was immediately responsive as expected when I uninstalled the older, bugged NVIDIA 550.x driver for a test. This issue (as well as my system freezes) now seems to be resolved.

@FezzedOne
Copy link
Author

Looks like the Albert bug is still there, although testing reveals that the unrelated kernel freeze bug appears to be fixed.

@FezzedOne FezzedOne reopened this Mar 16, 2024
@FezzedOne
Copy link
Author

Here is my debug log, although Albert is apparently responsive when I restart it after the login freeze.
albert-debug.log

@FezzedOne
Copy link
Author

Oh, one more thing — Albert is unresponsive for several minutes whenever it's autostarted by Plasma or launched from a launcher in Plasma, but not when I run it from a terminal. I do pass --platform xcb to Albert whenever it's launched via Plasma though, something I don't do via the terminal.

@ManuelSchneid3r
Copy link
Member

Does it happen when run with xcb from terminal?

@FezzedOne
Copy link
Author

FezzedOne commented Mar 16, 2024

Managed to capture a debug log from an unresponsive instance of Albert. And no, it doesn't happen when invoked from a terminal with --platform xcb. It always happens when it's autostarted, and sometimes happens when it's manually started from a Plasma launcher.
albert-autostart-debug.log

@ManuelSchneid3r
Copy link
Member

nothing special in the logs. Can you please adjust the exec line in .config/autostart/albert… to run with -n or --no-load ? just to see if the core and frontend work as expected?

@FezzedOne
Copy link
Author

FezzedOne commented Mar 16, 2024

With -n, Albert is apparently fully and immediately responsive when autostarted. Debug log:
albert-autostart-debug-2.log

@FezzedOne
Copy link
Author

FezzedOne commented Mar 16, 2024

Here are my enabled plugins:

  • Applications
  • Calculator
  • Chromium
  • Clipboard
  • MPRIS
  • SSH
  • System
  • Terminal
  • URL Handler

Note that there was some unresponsiveness when I clicked «Applications» the first time, but not afterward.

@ManuelSchneid3r
Copy link
Member

With some sort of binary search you need about 3 reboots to find the plugin causing the issue. 😄 (assuming it is only one of them). reminds me of ddmin.

@ManuelSchneid3r
Copy link
Member

 step | delta | test case                | test
------------------------------------------------
   1   |   1   | [1, 2, 3, 4] .  .  .  .  | pass
   2   |   2   |  .  .  .  . [5, 6, 7, 8] | fail
------------------------------------------------
   3   |   1   |  .  .  .  . [5, 6] .  .  | pass
   4   |   2   |  .  .  .  .  .  . [7, 8] | fail
------------------------------------------------
   5   |   1   |  .  .  .  .  .  . [7] .  | fail  (minimal input)
------------------------------------------------
result |                           [7] 

like that src

@FezzedOne
Copy link
Author

FezzedOne commented Mar 20, 2024

Uh, I just got something relevant to the issue in KDE's autostart logs for Albert (link expires in 24 hours). Turns out I got a GPU (or GPU driver) error when I closed an unresponsive Albert instance this afternoon.

@FezzedOne
Copy link
Author

FezzedOne commented Mar 20, 2024

Okay, so updating the NVIDIA driver to 550.67 fixed this issue. Here's the relevant change from their changelog:

  • Fixed a bug that caused wgpu applications to hang on Wayland.

Which is weird because the Intel iGPU is what's being used for desktop rendering. Then again, the NVIDIA driver was causing a more serious issue (kernel page faults / panics) for me, even though every single time that issue happened, nothing was running on the NVIDIA dGPU.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants