"Albert has not been terminated properly" message on Startup #1311

Glint-Eye · 2023-10-04T09:02:48Z

Note that this is a general notification that something went wrong in the former run. To find out what happened see the logs. Use journalctl -t albert.desktop if the crash happened while using an instance that has been autostarted by your session manager otherwise run it in terminal and see stdout. Use albert -d to find issues or Q_LOGGING_RULES='*=true' albert to include Qt internal details.

Original post:

Description

On startup with autostart activated I get the following Popup:
"Albert has not been terminated properly. Please check your crash reports and report an issue"
I don't know where the crash reports are beeing saved.
It started happening for me with installing 0.22.10. I am now on 0.22.12.

Source

xUbuntu 22.04 Repository
on Pop OS 22.4

Debug output

[debg:albert] Albert version: 0.22.12
[debg:albert] Build date: Oct  3 2023 20:29:39
[debg:albert] Qt version: 6.2.4
[debg:albert] Build ABI: x86_64-little_endian-lp64
[debg:albert] Arch (build/current): x86_64/x86_64
[debg:albert] Kernel (type/version): linux/6.5.4-76060504-generic
[debg:albert] OS: Pop!_OS 22.04 LTS
[debg:albert] OS (type/version): pop/22.04
[debg:albert] Platform name: xcb
[debg:albert] Binary location: /usr/bin/albert
[debg:albert] Current dir: ****
[debg:albert] Font: Fira Sans Semi-Light,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1
[debg:albert] Language: English
[debg:albert] Locale: en_US
[debg:albert] $LANG: en_US.UTF-8
[debg:albert] $QT_QPA_PLATFORMTHEME: 
[debg:albert] $PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
[debg:albert] $PWD: ****
[debg:albert] $SHELL: /bin/bash
[debg:albert] $XDG_SESSION_TYPE: x11
[debg:albert] $XDG_CURRENT_DESKTOP: pop:GNOME
[debg:albert] $DESKTOP_SESSION: pop
[debg:albert] $XDG_SESSION_DESKTOP: pop
[debg:albert] Icon theme: Pop
[warn:albert] Albert has not been terminated properly. Please check your crash reports and report an issue.
[debg:albert] Checking for a running instance…
[info:albert] There is another instance of albert running.

The text was updated successfully, but these errors were encountered:

henrikgit · 2023-10-04T09:26:50Z

Same here, as of this morning (Oct. 4, 2023).

albert did not start anymore.

Uninstalling and reinstalling helped insofar that it now starts again, but the same warning appears:

$ albert -d
11:25:28 [debg:albert]         Albert version: 0.22.10
11:25:28 [debg:albert]             Build date: Oct  4 2023 09:19:11
11:25:28 [debg:albert]             Qt version: 6.5.3
11:25:28 [debg:albert]              Build ABI: x86_64-little_endian-lp64
11:25:28 [debg:albert]   Arch (build/current): x86_64/x86_64
11:25:28 [debg:albert]  Kernel (type/version): linux/6.5.5-arch1-1
11:25:28 [debg:albert]                     OS: Arch Linux
11:25:28 [debg:albert]      OS (type/version): arch/unknown
11:25:28 [debg:albert]          Platform name: xcb
11:25:28 [debg:albert]        Binary location: /usr/bin/albert
11:25:28 [debg:albert]            Current dir: /home/john
11:25:28 [debg:albert]                   Font: Liberation Sans,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1,Regular
11:25:28 [debg:albert]               Language: German
11:25:28 [debg:albert]                 Locale: de_DE
11:25:28 [debg:albert]                  $LANG: de_DE.UTF-8
11:25:28 [debg:albert]  $QT_QPA_PLATFORMTHEME: qt5ct
11:25:28 [debg:albert]                  $PATH: /usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/home/john/.dotnet/tools:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
11:25:28 [debg:albert]                   $PWD: /home/john
11:25:28 [debg:albert]                 $SHELL: /bin/bash
11:25:28 [debg:albert]      $XDG_SESSION_TYPE: x11
11:25:28 [debg:albert]   $XDG_CURRENT_DESKTOP: XFCE
11:25:28 [debg:albert]       $DESKTOP_SESSION: xfce
11:25:28 [debg:albert]   $XDG_SESSION_DESKTOP: xfce
11:25:28 [debg:albert]             Icon theme: gnome
11:25:28 [warn:albert] Albert has not been terminated properly. Please check your crash reports and report an issue.
11:25:30 [debg:albert] Checking for a running instance…
11:25:30 [debg:albert] Creating local socket /home/john/.cache/albert/ipc_socket
11:25:30 [debg:albert] Database: Connecting…

ManuelSchneid3r · 2023-10-04T09:47:36Z

there are two logfiles in .cache/albert. the current and the past log. please post the past log. the one of the crashed process if you just received this messagebox.

Glint-Eye · 2023-10-04T10:36:04Z

okay so albert.last.log says the following:

12:25:34 WARN Albert has not been terminated properly. Please check your crash reports and report an issue.
12:25:37 INFO There is another instance of albert running.

albert.log says:

12:28:56 WARN Albert has not been terminated properly. Please check your crash reports and report an issue.
12:29:04 INFO Hotkey set to Ctrl+Space
12:29:05 INFO Indexing ****
12:29:05 INFO Python version: 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0]

Btw, I get the same popup message when I start albert while an instance is already running.

stasadev · 2023-10-04T11:37:33Z

I have the same problem, ~/.cache/albert/running just doesn't get deleted on shutdown/reboot.

~/.cache/albert/albert.last.log and ~/.cache/albert/albert.log are always empty.

ManuelSchneid3r · 2023-10-04T13:36:36Z

shutdown/reboot

does this issue occur only on reboot? Which desktop environment?

stasadev · 2023-10-04T13:47:48Z

KDE. I tested it again a few times and this time there was no problem, maybe it was on my end.

Currently, I only see this warning if I try to run Albert from Albert.

Glint-Eye · 2023-10-04T13:51:31Z

Pop OS 22.04.
For me it happens on reboot and shutdown. Only when I end the "albert" process manually before shutdown/reboot it doesn't occur.

tomporter518 · 2023-10-04T23:48:42Z

I can corroborate that this is also happening for me in Gnome 44 on Fedora 38. Manual exit of Albert removes the file but a full machine shutdown does not.

henrikgit · 2023-10-05T08:10:22Z

New day, new startup.

I can report that I actually got 2 of these windows (I already OK-ed the 1st one):

ManuelSchneid3r · 2023-10-05T08:24:33Z

Looks like this issue appears only on reboot. I assume that either session management is not handled correctly or the DE does not implement it correctly. Can you please add QT_LOGGING_RULES="*.debug=true" to the exec line in the desktop entry at /usr/share/applications/albert.desktop, such that it look like this:

#!/usr/bin/env xdg-open
[Desktop Entry]
Categories=Utility;
Comment=A desktop agnostic launcher
Exec=/usr/bin/env QT_LOGGING_RULES="*.debug=true" QT_QPA_PLATFORM=xcb albert
GenericName=Launcher
Icon=albert
Name=Albert
StartupNotify=false
Type=Application
Version=1.0

Then do two restarts (one to actually get this desktop file started using the autostart mechanism and the second to get this instance terminated by a restart) and then post the albert.last.log in a pastebin?

henrikgit · 2023-10-05T15:12:34Z

Edited the albert.desktop-file to this:

$ cat  /usr/share/applications/albert.desktop
#!/usr/bin/env xdg-open
[Desktop Entry]
Categories=Utility;
Comment=A desktop agnostic launcher
Exec=/usr/bin/env QT_LOGGING_RULES="*.debug=true" QT_QPA_PLATFORM=xcb albert
GenericName=Launcher
Icon=albert
Name=Albert
StartupNotify=false
Type=Application
Version=1.0

So, as requested `albert.last.log` (which is quite minimal :/) after 2 restarts:

$ cat ~/.cache/albert/albert.last.log 
17:08:32 WARN Albert has not been terminated properly. Please check your crash reports and report an issue.
17:08:36 INFO There is another instance of albert running.

Here's also albert.log:

$ cat ~/.cache/albert/albert.log 
17:08:32 WARN Albert has not been terminated properly. Please check your crash reports and report an issue.
17:08:35 INFO Hotkey set to Ctrl+Space
17:08:36 INFO Indexing /home/john

DirkFi · 2023-10-05T21:51:09Z

Same issue here. I am using KDE neon 5.27 Release 22.04.

I do add the QT_LOGGING_RULES="*.debug=true". And after 2 restarts, and the 2 logs look as follows:

albert.log

  16:29:15 WARN Albert has not been terminated properly. Please check your crash reports and report an issue.
  16:29:27 INFO There is another instance of albert running.

albert.last.log

16:29:15 INFO There is another instance of albert running.
hecking directory path "/usr/lib/x86_64-linux-gnu/qt6/plugins/networkaccess" ...
16:29:15 DEBG checking directory path "/usr/bin/networkaccess" ...
16:29:15 DEBG Checking for a running instance…
16:29:15 DEBG Creating local socket /home/dirk/.cache/albert/ipc_socket
16:29:15 DEBG checking directory path "/usr/lib/x86_64-linux-gnu/qt6/plugins/sqldrivers" ...
16:29:15 DEBG looking at "/usr/lib/x86_64-linux-gnu/qt6/plugins/sqldrivers/libqsqlmysql.so"
16:29:15 DEBG Found metadata in lib /usr/lib/x86_64-linux-gnu/qt6/plugins/sqldrivers/libqsqlmysql.so, metadata=
{
    "IID": "org.qt-project.Qt.QSqlDriverFactoryInterface",
    "MetaData": {
        "Keys": [
            "QMYSQL",
            "QMARIADB"
        ]
    },
    "archlevel": 1,
    "className": "QMYSQLDriverPlugin",
    "debug": false,
    "version": 394496
}

And similar text repeated a lot of times for the log:

repeated log

16:29:15 DEBG Found metadata in lib /usr/lib/x86_64-linux-gnu/qt6/plugins/sqldrivers/libqsqlmysql.so, metadata=
{
    "IID": "org.qt-project.Qt.QSqlDriverFactoryInterface",
    "MetaData": {
        "Keys": [
            "QMYSQL",
            "QMARIADB"
        ]
    },
    "archlevel": 1,
    "className": "QMYSQLDriverPlugin",
    "debug": false,
    "version": 394496
}

I uploaded the full log in my forked repo, link here: full log.

bashopman · 2023-10-06T06:15:57Z

Looks like this issue appears only on reboot.

FYI: I experience the same when logging out and back in.

ManuelSchneid3r · 2023-10-06T09:21:57Z

I think i found the problem. Session managers on some systems restore the session including albert. But also you probably have albert set to autostart on login. Thus albert is run twice. Can you confirm?

Well the obvious thing is not to report a crash if the app is running atm…

bashopman · 2023-10-06T09:29:16Z

Albert is set to autostart, yes. I don't remember setting it up like that, so I assume it is done on installation?
FYI: I'm using Gnome 44 on Ubuntu 23.04.

ManuelSchneid3r · 2023-10-06T09:30:41Z

@bashopman iirc no. there is a checkbox in the settings for it. maybe you checked it once.

bashopman · 2023-10-06T09:35:43Z

@ManuelSchneid3r that is likely, yes. I tend to check settings menu's and that sounds like a convenient option. ;)
The "autostart" checkbox was set. Unchecked it now.

ManuelSchneid3r · 2023-10-06T09:39:14Z

@bashopman this should not be necessary. ill try to move the crash indicator into the rpc server. i am not sure though how particular systems handle leftover local sockets on reboot. hopefully they remain such that crashes can be recognized.

ManuelSchneid3r · 2023-10-06T10:22:45Z

fdf1954

ManuelSchneid3r · 2023-10-06T10:37:51Z

in 0.22.14. let me know how it works out.

bashopman · 2023-10-06T11:25:54Z

Hi @ManuelSchneid3r
Executed the following steps to test:

I had checked-out the autostart option earlier.
I then installed your update 0.22.14.
Logged out and then back in.
No error message!
ALT-Space (my hotkey combination) didn't work though.
Started Albert from the app menu
Got same error message as before.
Removing the error window, ALT-Space works again.
Checked auto-start again
Logged out and then back in.
Albert shows error message that it wasn't properly shutdown.
Logged out and then back in.
No error message!
Rebooted the machine and logged in.
Albert shows error message that it wasn't properly shutdown.
ALT-Space does work again

Not sure what I can do more...

ManuelSchneid3r · 2023-10-06T11:33:09Z

5. ALT-Space (my hotkey combination) didn't work though.

do you use the internal hotkey or some sort of external hotkey firing albert show or toggle?

ManuelSchneid3r · 2023-10-06T12:21:17Z

gave it a testrun on Kubuntu 20.04. everything is fine there. what are the others experiencing? @henrikgit @tomporter518 @stasadev @Glint-Eye @DirkFi

bashopman · 2023-10-06T12:40:14Z

@ManuelSchneid3r I'm using the hotkey defined from the Albert settings.
Note that I'm using Gnome 44 and not KDE.
And, not sure if relevant, I'm using X.org. When using Wayland, I don't get Albert to work at all.

stasadev · 2023-10-06T12:56:35Z

KDE 5.27.8
Albert v0.22.14

All good when I reboot via KDE menu > restart.
But I see a warning every time if I reboot with /usr/bin/reboot (for me it's a part of systemd-sysvcompat).

ManuelSchneid3r · 2023-10-06T13:07:41Z

This reminds me of an issue which is years old (#197). reboot does not reboot session friendly. It SIGTERMs all processes, notably the XServer as well, which causes QT programs to fail with ICE errors (whatever this is). Also posted a qt bug on this.

Glint-Eye · 2023-10-06T13:54:12Z

I think i found the problem. Session managers on some systems restore the session including albert. But also you probably have albert set to autostart on login. Thus albert is run twice. Can you confirm?

Well the obvious thing is not to report a crash if the app is running atm…

Just installed 0.22.14. did 1 shutdown, then 2 reboots. Everytime still got the message.
Tried then to deactivate autostart in albert options. Process is not being restored after reboot. Had to start albert manually again. And then, after starting manually without any prior instance running i got the message aswell.

DirkFi · 2023-10-06T14:08:20Z

I think i found the problem. Session managers on some systems restore the session including albert. But also you probably have albert set to autostart on login. Thus albert is run twice. Can you confirm?

Well the obvious thing is not to report a crash if the app is running atm…

@ManuelSchneid3r In my case for Albert 0.22.14, you are right! I deactivated the autostart in albert. After I do a restart, albert started automatically without any errors! I tested several times and it all behaved as expected! Seems like my case is different from Glint-Eye.

skelly37 · 2023-11-01T10:17:36Z

Segfaults should not be handled but actually fixed.

Correct, that is why I said it is not a great idea. Segfaults can also happen by invalid shutdown that cannot be fixed from the app side, though.

Why do you think it stems from a broken socket?

Well, because the app is force-killed by the OS, it cannot close the socket correctly and it results in a broken socket left behind. And the message we see is caused exactly by invalidated socket.

The socket is closed on regular teardown. Removing it from the outside just removes the hint that something went wrong and is therefore nor proper solution.

How about some toggle to disable this pop-up? The socket will remain in ~/.cache/albert, the pop-up will appear by default but it would be simply possible to say I do not care about previous errors, just give me my launcher back

ManuelSchneid3r · 2023-11-01T11:27:26Z

I mean did you just read the above or do have reasons for your suspicion? Like logs etc

Segfaults can also happen by invalid shutdown

No (assuming you are talking of a system shutdown), if this is the issue above, the qt ICE error calls exit() which should not result in a segfault. However the left over socket indicates any crash. That's why I am curious why you think there has been a segfault. There are possibly other issues we indeed can fix.

The improper shutdown of a session is a thing desktop environments have to fix or users have to stop using shutdown/reboot cli tools.

skelly37 · 2023-11-01T12:11:28Z

I mean did you just read the above or do have reasons for your suspicion? Like logs etc

Segfaults can also happen by invalid shutdown

No (assuming you are talking of a system shutdown), if this is the issue above, the qt ICE error calls exit() which should not result in a segfault. However the left over socket indicates any crash. That's why I am curious why you think there has been a segfault. There are possibly other issues we indeed can fix.

The improper shutdown of a session is a thing desktop environments have to fix or users have to stop using shutdown/reboot cli tools.

My reasoning for SEGV is that I have got errno 11 in my logs

ICE default IO error handler doing an exit(), pid = 9616, errno = 11
23:12:37 [warn:QHotkey] QHotkeyPrivate destroyed with registered shortcuts!

But now I see that the error above was 2, so seems like a false lead

ManuelSchneid3r · 2023-11-01T12:59:32Z

Can you all please post the version of your desktop environment and if this bug is appearing if you use the session tools to quit the session? I am trying to get a table of desktop environments to consider and track the issues (we should report there).

javism · 2023-11-02T09:30:45Z

I can confirm this issue in Linux Mint 21.2 (Ubuntu) both in Cinnamon (5.8.4+victoria) and Mate (1.26.0-1)

cbanack · 2023-11-03T04:21:25Z

Yup, I've seen this error dialog every morning for a couple weeks, each time I boot into Linux.

I'm Pop!OS_22.04 (the latest LTS) with vanilla Gnome 42.9 running in X11 mode.

Happens if I just logout of Gnome and log back in, or if I fully shutdown and reboot. I can use the Gnome menu to do the shutdown or logoff, or I can use the shutdown or logout commands in Albert. Still happens every time.

JStyle21 · 2023-11-04T05:10:08Z

I"m on Arch with KDE, same here, error has been happening for weeks now on every boot.

ManuelSchneid3r · 2023-11-04T07:41:06Z

@JStyle21 how do you reboot?

JStyle21 · 2023-11-04T09:24:13Z

@ManuelSchneid3r
Mostly i have a shortcut for the poweroff command and then i just poweron the computer
But if i need to restart i usually use the KDE Plasma reboot option

ManuelSchneid3r · 2023-11-04T10:23:18Z

@JStyle21 does it really happen when you use the KDE logout tools? reboot does not shutdown a session properly.

JStyle21 · 2023-11-04T12:36:04Z

@ManuelSchneid3r
Just tested, it doesn't

I use the shortcut i mentioned most of the time, i changed it from poweroff to qdbus org.kde.ksmserver /KSMServer logout 0 2 -1

But i consider this a workaround not a fix, this is an application level problem not an OS so at the very least you should be able to suppress warning messages if needed, no one wants them in the foreground like that.

ManuelSchneid3r · 2023-11-04T13:14:11Z

Don't use cli reboot. It is not intended to quit x sessions.

This is neither a workaround nor a fix. It is the proper usage of the cli to end a kde session (at least until xorg or systemd care about each other's mechanisms).

This is not an application level issue. Not even a toolkit level issue. Simply killing the Xserver is not an option if you want to end your session.

Obviously the process tree should be hierarchical and the processes terminated bottom up. But I'd rather let a committee of systemd, desktop environment and toolkit devs decide on what is the correct way to go.

From the app dev point of view I can't do anything but teach users how to use their system correctly.

JStyle21 · 2023-11-04T13:29:01Z

I appreciate your perspective, but I must respectfully disagree. While it's true that there might not always be a clear right or wrong in the context of system operations, it is crucial for application developers to consider the user experience and provide solutions that are intuitive and user-friendly.

It's worth noting that no other application, including earlier versions of this one, has encountered a similar issue. Currently, the system logs are inundated with warnings, errors, and other messages. If these messages don't present critical obstacles to the user interface, then they should be confined to the log files.

While it is beneficial to educate users about proper system usage, it is equally critical to design applications that proactively mitigate the risk of users encountering such issues. The absence of problems in other applications or earlier versions does not inherently validate the current approach. As technology evolves, so do user expectations, and it is imperative for software to adapt accordingly.

As a developer, even though systemic changes may be on the horizon, you have the capacity to enhance the user experience by making your application more user-friendly and resilient. The objective is not to assign blame to system dependencies but to take ownership of the user experience and ensure that your application seamlessly operates within the broader technology ecosystem.

douglasthiel · 2023-11-09T18:48:25Z

Can you all please post the version of your desktop environment and if this bug is appearing if you use the session tools to quit the session? I am trying to get a table of desktop environments to consider and track the issues (we should report there).

System Details Report

Report details

Date generated: 2023-11-09 12:48:02

Hardware Information:

Hardware Model: Apple Inc. Macmini7,1
Memory: 16.0 GiB
Processor: Intel® Core™ i7-4578U × 4
Graphics: Intel® Iris® Graphics 5100 (HSW GT3)
Disk Capacity: 1.0 TB

Software Information:

Firmware Version: 481.0.0.0.0
OS Name: Fedora Linux 39 (Workstation Edition)
OS Build: (null)
OS Type: 64-bit
GNOME Version: 45.1
Windowing System: Wayland
Kernel Version: Linux 6.5.10-300.fc39.x86_64

graue70 · 2023-11-09T21:28:30Z

Can you all please post the version of your desktop environment and if this bug is appearing if you use the session tools to quit the session?

Can you please explain what you mean by session tools? You're previous comments seem to suggest that I can circumvent the error message by behaving differently. If that's the case, I don't know how.

ManuelSchneid3r · 2023-11-10T09:22:29Z

Still debugging. I guess I am on the track now. Atm I suspect it to be some qt quirks with dynamic library (un)loading at teardown (i.e. still runtime).

@graue70 I just assumed that this stems from the usage of systemd to shut down the system. But atm I don't know for sure if it causes this issue. What I do know for sure is that it skips session shutdown scripts. So I can say it is generally not a good idea.

KingofHubGit · 2023-11-11T04:47:34Z

I have seen three commits to resolve this problem.
When will the fixed version be?

ManuelSchneid3r · 2023-11-11T10:32:54Z

I appreciate your perspective, but I must respectfully disagree. While it's true that there might not always be a clear right or wrong in the context of system operations, it is crucial for application developers to consider the user experience and provide solutions that are intuitive and user-friendly.

Sure but i cant help. This issue is there and extremely hard to track. Why would I not want to give a intuitive an user-friendly solution if I could?

It's worth noting that no other application, including earlier versions of this one, has encountered a similar issue. Currently, the system logs are inundated with warnings, errors, and other messages. If these messages don't present critical obstacles to the user interface, then they should be confined to the log files.

This problem has been there for a long time (#197). I just recently made the warning visible because it is a problem if settings are not saved. And yes, I also wonder why other applications like e.g. CopyQ dont suffer this issue (or do they just accept crashes?).

As a developer, even though systemic changes may be on the horizon, you have the capacity to enhance the user experience by making your application more user-friendly and resilient. The objective is not to assign blame to system dependencies but to take ownership of the user experience and ensure that your application seamlessly operates within the broader technology ecosystem.

I totally agree with that, but as said, there is no solution yet. I spent tons of hours finding this issue, no luck yet. I dont like strategies like that:

ManuelSchneid3r · 2023-11-11T10:36:16Z

I have seen three commits to resolve this problem.
When will the fixed version be?

Which commits? The root issue (ICE error) is not solved yet.

ManuelSchneid3r · 2023-11-11T10:38:45Z

Can you please explain what you mean by session tools?

using the session tools. something like that:

ManuelSchneid3r · 2023-11-11T10:40:20Z

This issue is cluttered but has some important information. I opened a new issue #1333 which is only about the ICE error. Please watch it.

JStyle21 · 2023-11-11T22:53:47Z

I appreciate your perspective, but I must respectfully disagree. While it's true that there might not always be a clear right or wrong in the context of system operations, it is crucial for application developers to consider the user experience and provide solutions that are intuitive and user-friendly.

Sure but i cant help. This issue is there and extremely hard to track. Why would I not want to give a intuitive an user-friendly solution if I could?

Just to clarify, I never meant to suggest that you're not interested in an intuitive solution.

It's worth noting that no other application, including earlier versions of this one, has encountered a similar issue. Currently, the system logs are inundated with warnings, errors, and other messages. If these messages don't present critical obstacles to the user interface, then they should be confined to the log files.

This problem has been there for a long time (#197). I just recently made the warning visible because it is a problem if settings are not saved. And yes, I also wonder why other applications like e.g. CopyQ dont suffer this issue (or do they just accept crashes?).

Thanks for highlighting the history of issue #197 and your recent decision to make the warning visible. Exploring how other applications handle similar challenges could provide valuable insights.

Since you've mentioned CopyQ, how about we ask them to reply here and share their insights?

As a developer, even though systemic changes may be on the horizon, you have the capacity to enhance the user experience by making your application more user-friendly and resilient. The objective is not to assign blame to system dependencies but to take ownership of the user experience and ensure that your application seamlessly operates within the broader technology ecosystem.

I totally agree with that, but as said, there is no solution yet. I spent tons of hours finding this issue, no luck yet. I dont like strategies like that:

I understand your POV now and the difficulties you're facing and I appreciate the time and effort you've invested.
Also the the meme in on point :)

ManuelSchneid3r · 2024-07-30T09:25:22Z

Do you guys still experience this issue? In 0.23 I changed the core structure that may be related to this issue.

AdamPS · 2024-08-02T11:02:22Z

I've not seen this problem recently thanks

Glint-Eye assigned ManuelSchneid3r Oct 4, 2023

ManuelSchneid3r closed this as completed Oct 6, 2023

ManuelSchneid3r added Bug P3 Medium Fix, but can wait if there's more import stuff to do. C: App Issue related to the core application/library labels Nov 8, 2023

ManuelSchneid3r closed this as completed Nov 11, 2023

ManuelSchneid3r mentioned this issue Nov 11, 2023

QTBUG-53678 ICE default IO error handler doing an exit(), pid = ..., errno = 11 #1333

Open

albertlauncher deleted a comment from KingofHubGit Nov 11, 2023

albertlauncher deleted a comment from KingofHubGit Jul 30, 2024

"Albert has not been terminated properly" message on Startup #1311

"Albert has not been terminated properly" message on Startup #1311

Comments

Glint-Eye commented Oct 4, 2023 • edited by ManuelSchneid3r Loading

Description

Source

Debug output

henrikgit commented Oct 4, 2023

ManuelSchneid3r commented Oct 4, 2023

Glint-Eye commented Oct 4, 2023

stasadev commented Oct 4, 2023

ManuelSchneid3r commented Oct 4, 2023

stasadev commented Oct 4, 2023

Glint-Eye commented Oct 4, 2023

tomporter518 commented Oct 4, 2023

henrikgit commented Oct 5, 2023

ManuelSchneid3r commented Oct 5, 2023

henrikgit commented Oct 5, 2023 • edited Loading

DirkFi commented Oct 5, 2023

bashopman commented Oct 6, 2023

ManuelSchneid3r commented Oct 6, 2023

bashopman commented Oct 6, 2023

ManuelSchneid3r commented Oct 6, 2023

bashopman commented Oct 6, 2023 • edited Loading

ManuelSchneid3r commented Oct 6, 2023

ManuelSchneid3r commented Oct 6, 2023

ManuelSchneid3r commented Oct 6, 2023

bashopman commented Oct 6, 2023

ManuelSchneid3r commented Oct 6, 2023

ManuelSchneid3r commented Oct 6, 2023

bashopman commented Oct 6, 2023 • edited Loading

stasadev commented Oct 6, 2023

ManuelSchneid3r commented Oct 6, 2023 • edited Loading

Glint-Eye commented Oct 6, 2023

DirkFi commented Oct 6, 2023

skelly37 commented Nov 1, 2023

ManuelSchneid3r commented Nov 1, 2023

skelly37 commented Nov 1, 2023

ManuelSchneid3r commented Nov 1, 2023

javism commented Nov 2, 2023

cbanack commented Nov 3, 2023 • edited Loading

JStyle21 commented Nov 4, 2023

ManuelSchneid3r commented Nov 4, 2023

JStyle21 commented Nov 4, 2023 • edited Loading

ManuelSchneid3r commented Nov 4, 2023 • edited Loading

JStyle21 commented Nov 4, 2023 • edited Loading

ManuelSchneid3r commented Nov 4, 2023

JStyle21 commented Nov 4, 2023

douglasthiel commented Nov 9, 2023

System Details Report

Report details

Hardware Information:

Software Information:

graue70 commented Nov 9, 2023

ManuelSchneid3r commented Nov 10, 2023

KingofHubGit commented Nov 11, 2023

ManuelSchneid3r commented Nov 11, 2023

ManuelSchneid3r commented Nov 11, 2023

ManuelSchneid3r commented Nov 11, 2023

ManuelSchneid3r commented Nov 11, 2023

JStyle21 commented Nov 11, 2023

ManuelSchneid3r commented Jul 30, 2024

AdamPS commented Aug 2, 2024

Glint-Eye commented Oct 4, 2023 •

edited by ManuelSchneid3r

Loading

henrikgit commented Oct 5, 2023 •

edited

Loading

bashopman commented Oct 6, 2023 •

edited

Loading

bashopman commented Oct 6, 2023 •

edited

Loading

ManuelSchneid3r commented Oct 6, 2023 •

edited

Loading

cbanack commented Nov 3, 2023 •

edited

Loading

JStyle21 commented Nov 4, 2023 •

edited

Loading

ManuelSchneid3r commented Nov 4, 2023 •

edited

Loading

JStyle21 commented Nov 4, 2023 •

edited

Loading