You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, the problem is very weird, the first time I open the app on a fresh config, it all works fine. On the first launch it asks for telemetry, whether I click on yes or no, doesn't matter, and I can open the settings without a problem. When I close albert and then open it again, I can still use it fine, but if I open the settings, I now get a segmentation fault (I get zsh: segmentation fault (core dumped) albert -n on the terminal).
On my config, when I select either yes or no for the telemetry question, a section gets added to the config file:
[General]
telemetry=false
If I then remove this section and start albert again, it will ask the telemetry question, I can answer whatever, and then until albert gets restarted again I can open the settings section with no problem.
I also noticed that, strangely enough, if I remove the telemetry section from the config, start albert, and then answer the telemetry question without using the mouse (using e.g. the left/right arrow and then enter, or if I press ESC to cancel it), then it also core dumps when I open the settings, so I need to select an option with my mouse for it to work.
This happens also when I run albert with -n, to avoid loading plugins, and also happens on a fresh config
On the video below I show this happening:
2025-02-09_20-59-33.mp4
1st, I open it with a config with no telemetry config, click on no when it asks, and open the settings, it all works fine.
I then kill albert and open it again, then go to the settings and it segfaults.
Remove the telemetry section and open albert again, open settings, it works fine again
I then remove the telemetry section again from the settings, open albert, and select an option with the keyboard. I then open the settings and it segfaults.
So in the end, the only way for me to get to the settings is for me to manually go to the config, remove that telemetry section, restart albert, answer the telemetry section with the mouse, and it should work until it gets restarted
Expected Behavior
should not segfault when I open the settings
Anything else?
I'm on hyprland (0.47.0-57-gf7fcbe32 (Wayland)), using arch with cachyos (kernel 6.13.1-2-cachyos)
I can provide more info if needed
coredumpctl info:
$ coredumpctl info
PID: 348013 (albert)
UID: 1000 (gabe)
GID: 1000 (gabe)
Signal: 11 (SEGV)
Timestamp: Sun 2025-02-09 21:13:46 CET (7min ago)
Command Line: albert
Executable: /usr/bin/albert
Control Group: /user.slice/user-1000.slice/[email protected]/app.slice/app-graphical.slice/tmux-spawn-7dee75d8-40ee-4cfe-bcd8-b8f74253f3f9.scope
Unit: [email protected]
User Unit: tmux-spawn-7dee75d8-40ee-4cfe-bcd8-b8f74253f3f9.scope
Slice: user-1000.slice
Owner UID: 1000 (gabe)
Boot ID: 0cdafbd3854a419eb8116cbe330e46c6
Machine ID: 8cccdbdfe5984c519b4d8e7beb4dfbf8
Hostname: gabe-arch
Storage: /var/lib/systemd/coredump/core.albert.1000.0cdafbd3854a419eb8116cbe330e46c6.348013.1739132026000000.zst (present)
Size on Disk: 4.7M
Message: Process 348013 (albert) of user 1000 dumped core.
Stack trace of thread 348013:
#0 0x000079964c9e3714 n/a (n/a + 0x0)#1 0x000079964dfe3c73 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64
gdb -ex run --args albert -n:
$ gdb -ex run --args albert -n
GNU gdb (GDB) 16.2
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty"for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration"for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type"help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from albert...
This GDB supports auto-downloading debuginfo from the following URLs:
<https://debuginfod.archlinux.org><https://debuginfod.cachyos.org>
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
(No debugging symbols found in albert)
Starting program: /usr/bin/albert -n
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffeb90b6c0 (LWP 351781)]
[New Thread 0x7fffeaeed6c0 (LWP 351782)]
[New Thread 0x7fffea6ec6c0 (LWP 351783)]
21:22:18 [crit:albert] Albert has not been terminated properly. Please check your logs and report an issue.
21:22:18 [info:albert] Searching native plugins in /usr/lib/albert
[New Thread 0x7fffe908e6c0 (LWP 351800)]
21:22:18 [info:albert] Hotkeys are not supported on this platform.
[New Thread 0x7fffdbfff6c0 (LWP 351802)]
[New Thread 0x7fffdb7fe6c0 (LWP 351803)]
[New Thread 0x7fffdaffd6c0 (LWP 351804)]
21:22:26 [warn:albert.wbm] Could not retrieve screen for cursor position. Using primary screen.
[New Thread 0x7fffda7fc6c0 (LWP 351851)]
[New Thread 0x7fffd9ffb6c0 (LWP 351852)]
[New Thread 0x7fffd97fa6c0 (LWP 351853)]
[New Thread 0x7fffd8ff96c0 (LWP 351854)]
[New Thread 0x7fffbffff6c0 (LWP 351855)]
[New Thread 0x7fffbf7fe6c0 (LWP 351856)]
[New Thread 0x7fffbeffd6c0 (LWP 351857)]
[New Thread 0x7fffbe7fc6c0 (LWP 351858)]
[New Thread 0x7fffbdffb6c0 (LWP 351859)]
[New Thread 0x7fffbd7fa6c0 (LWP 351860)]
[New Thread 0x7fffbcff96c0 (LWP 351861)]
[New Thread 0x7fff9bfff6c0 (LWP 351862)]
[New Thread 0x7fff9b7fe6c0 (LWP 351863)]
[New Thread 0x7fff9affd6c0 (LWP 351864)]
[New Thread 0x7fff9a7fc6c0 (LWP 351865)]
[New Thread 0x7fff99ffb6c0 (LWP 351866)]
[New Thread 0x7fff997fa6c0 (LWP 351867)]
[New Thread 0x7fff98ff96c0 (LWP 351868)]
[New Thread 0x7fff77fff6c0 (LWP 351869)]
[New Thread 0x7fff6ffff6c0 (LWP 351870)]
[New Thread 0x7fff777fe6c0 (LWP 351871)]
[New Thread 0x7fff76ffd6c0 (LWP 351872)]
[New Thread 0x7fff767fc6c0 (LWP 351875)]
[New Thread 0x7fff75ffb6c0 (LWP 351878)]
[New Thread 0x7fff757fa6c0 (LWP 351879)]
[New Thread 0x7fff74ff96c0 (LWP 351880)]
[New Thread 0x7fff6f7fe6c0 (LWP 351881)]
[New Thread 0x7fff6effd6c0 (LWP 351882)]
Thread 1 "albert" received signal SIGSEGV, Segmentation fault.
0x00007ffff69e3714 inQScreen::geometry() const () from /usr/lib/libQt6Gui.so.6
libQt6Gui.so.6 seems suspicious here, since the settings seems related to qt.
I also tried reinstalling albert with --rebuild, but that didn't help
The text was updated successfully, but these errors were encountered:
Source
AUR
App logs
Current Behavior
So, the problem is very weird, the first time I open the app on a fresh config, it all works fine. On the first launch it asks for telemetry, whether I click on yes or no, doesn't matter, and I can open the settings without a problem. When I close albert and then open it again, I can still use it fine, but if I open the settings, I now get a segmentation fault (I get
zsh: segmentation fault (core dumped) albert -n
on the terminal).On my config, when I select either yes or no for the telemetry question, a section gets added to the config file:
If I then remove this section and start albert again, it will ask the telemetry question, I can answer whatever, and then until albert gets restarted again I can open the settings section with no problem.
I also noticed that, strangely enough, if I remove the telemetry section from the config, start albert, and then answer the telemetry question without using the mouse (using e.g. the left/right arrow and then enter, or if I press ESC to cancel it), then it also core dumps when I open the settings, so I need to select an option with my mouse for it to work.
This happens also when I run albert with -n, to avoid loading plugins, and also happens on a fresh config
On the video below I show this happening:
2025-02-09_20-59-33.mp4
So in the end, the only way for me to get to the settings is for me to manually go to the config, remove that telemetry section, restart albert, answer the telemetry section with the mouse, and it should work until it gets restarted
Expected Behavior
should not segfault when I open the settings
Anything else?
I'm on hyprland (0.47.0-57-gf7fcbe32 (Wayland)), using arch with cachyos (kernel 6.13.1-2-cachyos)
I can provide more info if needed
coredumpctl info
:gdb -ex run --args albert -n
:libQt6Gui.so.6 seems suspicious here, since the settings seems related to qt.
I also tried reinstalling albert with
--rebuild
, but that didn't helpThe text was updated successfully, but these errors were encountered: