[5.0.0.68] Work-Around - Cannot re-create General Email account

rob_kouw · 20 July 2025 15:10

REPRODUCIBILITY: 100%, although a specific situation perhaps
OS VERSION: 5.0.0.68
HARDWARE: Xperia 10 iii
UI LANGUAGE:English
REGRESSION:

DESCRIPTION:

I cannot re-create a General Email account, which was previously working. For years, I had two accounts working at provider DDS (dds.nl), on every SailfishOS phone I owned. A couple of days ago, my business account stopped syncing. In the Telegram channel I was advised to delete the account and re-create it. Unfortunately, it won’t re-create.

Tried it for several days. Today, I could easily add another General Email account at a different provider. So, the functionality is working. The cause of my problem could be with DDS, or with the fact that traces of my old account prohibit a re-creation.

Just to be clear: my private account at DDS is still working. And no, I don’t dare to delete it and try to re-create it again for testing purposes. I just have one phone for daily business.

I contacted DDS, all is well at their end, or so they claim. I thought it was some DNS problem, but their servers never respond to ping or traceroute. Their page https://dds.nl/ip/ checks out fine, both on mobile and wifi connection,.

PRECONDITIONS:

Create an account, delete it

STEPS TO REPRODUCE:

Try to re-create the account

EXPECTED RESULT:

A working account

ACTUAL RESULT:

A message that the incoming mailserver could not be reached:
BTW I could connect (Android) Thunderbird to the account.

MODIFICATIONS:

Not really. Many apps from Chum, OpenRepos or Aurora (Android) but no patches or WayDroid.

ADDITIONAL INFORMATION:

I wish it was possible to get detailed information when things go wrong.

Edz · 20 July 2025 15:27

same problem, same OS version, different device: Xperia 10ii

I gave up after many tries, having set up 4 other existing accounts without a problem.

rob_kouw · 20 July 2025 15:37

Some other provider, I guess?

amaretzek · 20 July 2025 17:01

You managed to create other accounts, but this one fails.
So, the process of creating this account doesn’t reach the end, if I got it right.
There was a time, when one had to kill the mail app (reboot) to have a working account.
As described in Setting up General Email (IMAP, SMTP) fails .
I see the differences, but just in case you missed something…

leon · 20 July 2025 21:39

Incredible

dcaliste · 21 July 2025 08:28

Would you be eager to gather logs ? If so, you can do the following:

make the mail daemon log its actions to a file, edit ~/.config/QtProject/Messageserver.conf so [FileLog] entry is enabled and provide a writable path, like

[FileLog]
Enabled=1
Path=~/qmf.log

then restart it with systemctl --user restart messageserver5.

not necessary, but in a terminal you can follow live what is written in the log file with tail -f ~/qmf.log. When you don’t want to observe the log anymore, you can abort the tail command with Ctrl+C.
try to recreate the account in the setting application. It will trigger a communication with the mail server to validate your credentials and retrieve the basic structure of your mail box.

Don’t hesitate to copy-paste here parts of the log you feel are relevant to understand your issue (I don’t remember if username is anonymised, but password surely is hidden in the log).

rob_kouw · 21 July 2025 19:09

The logging worked fine. I sent the link to the file to you, Damien.

rob_kouw · 21 July 2025 19:13

I tried rebooting several times, while updating, or when the error message was shown but before skipping. Didn’t work.

Thanks for showing the old thread. It was kind of confusing to find my own name in there with a similar problem 5 years ago. I’d forgotten all about it.

dcaliste · 22 July 2025 07:28

Yep, thank you for that. Hopefully we can iron out this annoying initial creation bug. From the log, it seems to be caused by the mailer daemon that segfaults when initially fetching the email box structure. This segfault has already been reported and I’ve fixed it upstream, see Handle accountsUpdated signal better · Issue #21 · sailfishos/messagingframework · GitHub

Let’s continue debugging the issue after the account creation while not fetching mails…

rob_kouw · 23 July 2025 20:31

So, small recap. Damien suggested I should debug the messageserver to find out where the mailer daemon segfaulted. I never debugged, and received some errors straightaway. But others may be handier with this, so let’s do it together here.

rob_kouw · 23 July 2025 20:34

My message on the contents of the config file:
The config file was:

[FileLog]
Enabled=1
Path=~/qmf.log

[LogCategories]
IMAP=1
Messaging=1
POP=1
SMTP=1

[StdStreamLog]
Enabled=0

[Syslog]
Enabled=0

So I guess it should have been logging IMAP and SMTP. Or would you need the other Logs enabled?

Damien’s answer and debugging instructions:

Ok, noted that, so it may crash at a place before starting the IMAP dialog with the server. So let’s try now to see why the mailer daemon keeps crashing (from the log you already sent, it keeps happening all along, see the PID in front of each line changing regularly). Besides, you can enable [StdStreamLog] to get the log output in the terminal if you run it from the command line.

To investigate further, you’ll have to run the daemon inside gdb and get a backtrace. Here is the procedure if you’re not familiar with it:

stop the daemon systemctl --user stop messageserver5,
become a privileged user to get account access devel-su -p,
start the debugger gdb messageserver5,
run the daemon from the debugger prompt r,
make it crash again through the UI,
inside the debugger get the backtrace bt.

Later you can quit the debugger with Ctrl+D and restart the daemon (as privileged user or not) systemctl --user restart messageserver5.

dcaliste · 24 July 2025 07:35

Don’t hesitate to post your issues, PM me if you prefer, or we can even try to do it live on IRC if it suits you better.

pawel.spoon · 24 July 2025 14:52

Have same issue since 4 days
Recreate did solve the issue, but now the other one of the in total 3 accounts is failing

rob_kouw · 24 July 2025 16:48

run the daemon from the debugger prompt r,

@dcaliste How to do this exactly?

dcaliste · 25 July 2025 07:54

I’m sorry, I was too concise for users without knowledge of gdb, my bad.

Just type r and press return at gdb prompt. It will run the program (it’s a shortcut for run, the same as step 6. where bt command is a shortcut for backtrace).

When you start gdb like in step 3., the program is actually not started yet. Like that, you can set up breakpoints and adjust debugger parameters before actually running the program inside the debugger. So step 3. start the debugger and tell that it will work on messageserver5. Then step 4. actually run the program inside the debugger.

rob_kouw · 27 July 2025 15:14

Thread 1 "messageserver5" received signal SIGINT, Interrupt.
0x0000007ff6f96e14 in poll () from /lib64/libc.so.6
(gdb) bt
#0  0x0000007ff6f96e14 in poll () from /lib64/libc.so.6
#1  0x0000007ff63ef5f0 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x0000007ff63efe34 in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#3  0x0000007ff753067c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4  0x0000007ff74daf84 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5  0x0000007ff74e29e4 in QCoreApplication::exec() ()
   from /usr/lib64/libQt5Core.so.5
#6  0x0000005555560924 in main (argc=<optimized out>, argv=<optimized out>)
    at main.cpp:62

Hi Damien,
Is this what you were looking for? Before, I got a whole lot of error messages:

Starting program: /usr/bin/messageserver5
Missing separate debuginfo for /lib/ld-linux-aarch64.so.1
Try: zypper install -C "debuginfo(build-id)=dbf98f8b9d93c252db9ed5bbc9d764b8cfecc7ab"
Missing separate debuginfo for /usr/lib64/libQt5DBus.so.5
Try: zypper install -C "debuginfo(build-id)=57bbb5485f1a9200f6c6ee3e7f4e665b05086a58"
Missing separate debuginfo for /usr/lib64/libQt5Gui.so.5
Try: zypper install -C "debuginfo(build-id)=3973060214c9865e6f2d0bb3ddaaaa38271916fd"
Missing separate debuginfo for /usr/lib64/libQt5Core.so.5
Try: zypper install -C "debuginfo(build-id)=f0e057825a75a4b7aa8503973a94454537a33e45"
Missing separate debuginfo for /lib64/libpthread.so.0
Try: zypper install -C "debuginfo(build-id)=fcab4580f252ad6aca6eb60e3caa641e4354ebbf"
warning: File "/lib64/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
        add-auto-load-safe-path /lib64/libthread_db-1.0.so
line to your configuration file "/root/.config/gdb/gdbinit".
To completely disable this security protection add
        set auto-load safe-path /
line to your configuration file "/root/.config/gdb/gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
        info "(gdb)Auto-loading safe path"
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
Missing separate debuginfo for /usr/lib64/libstdc++.so.6
Try: zypper install -C "debuginfo(build-id)=ff79f3b809f4f1a51fbcd2dd9fde90ade46cc622"
Missing separate debuginfo for /lib64/libc.so.6
Try: zypper install -C "debuginfo(build-id)=52733dec9aede726b93e39d1bf6c40ab30309bc5"
Missing separate debuginfo for /usr/lib64/libQt5Network.so.5
Try: zypper install -C "debuginfo(build-id)=cc34c4fe0c202e0857ed206cf53147e62c7011f8"
Missing separate debuginfo for /usr/lib64/libaccounts-qt5.so.1
Try: zypper install -C "debuginfo(build-id)=aca271f5daec1b93a933b3fedaba7aa4f83de883"
Missing separate debuginfo for /usr/lib64/libsignon-qt5.so.1
Try: zypper install -C "debuginfo(build-id)=ab689663f6b1d70028acbaf93ee909a5381109d9"
Missing separate debuginfo for /usr/lib64/libQt5Sql.so.5
Try: zypper install -C "debuginfo(build-id)=d83d70f6d6e1741540a491884efbf2d2c82197d9"
Missing separate debuginfo for /usr/lib64/libicui18n.so.70
Try: zypper install -C "debuginfo(build-id)=7f5c408b7e10b1211f92a90b0631b0cb3d72ba14"
Missing separate debuginfo for /usr/lib64/libicuuc.so.70
Try: zypper install -C "debuginfo(build-id)=0681462439b28818f16ec404b855e12c4541e787"
Missing separate debuginfo for /usr/lib64/libdbus-1.so.3
Try: zypper install -C "debuginfo(build-id)=73f7a4821faea20cb46162c9a73058f950a9d363"
Missing separate debuginfo for /usr/lib64/libz.so.1
Try: zypper install -C "debuginfo(build-id)=edb7d54c7f3027b48c7f38cde7bcd6c327de9cf7"
Missing separate debuginfo for /usr/lib64/libGLESv2.so.2
Try: zypper install -C "debuginfo(build-id)=9ead5df9b5050766a1b64e9d778b33ddf59e340c"
Missing separate debuginfo for /usr/lib64/libpng16.so.16
Try: zypper install -C "debuginfo(build-id)=080ede02625edaadc75eb43a7de41af0e8157e10"
Missing separate debuginfo for /lib64/libm.so.6
Try: zypper install -C "debuginfo(build-id)=8b3715c4a9ce8f0ac314247c43f21bc5e271b8a8"
Missing separate debuginfo for /usr/lib64/libpcre16.so.0
Try: zypper install -C "debuginfo(build-id)=669b2165df19a54d12ea1a94fa2ade2815a766d4"
Missing separate debuginfo for /lib64/libdl.so.2
Try: zypper install -C "debuginfo(build-id)=11ecd588a0b2750fa81118a2df2be8f5a0624765"
Missing separate debuginfo for /usr/lib64/libglib-2.0.so.0
Try: zypper install -C "debuginfo(build-id)=860173a707c71b4cec983b04fc81eeb74a8f6ca0"
Missing separate debuginfo for /usr/lib64/libsystemd.so.0
Try: zypper install -C "debuginfo(build-id)=288e089f6a249ace7012483a056b89f5121fe9b7"
Missing separate debuginfo for /lib64/libgcc_s.so.1
Try: zypper install -C "debuginfo(build-id)=a1f379ed205454bbf84bf9fdc9283bddac9351ea"
Missing separate debuginfo for /usr/lib64/libproxy.so.1
Try: zypper install -C "debuginfo(build-id)=b656f82a77bd0e68f66b4fe8e34f565960a45a47"
Missing separate debuginfo for /usr/lib64/libssl.so.1.1
Try: zypper install -C "debuginfo(build-id)=e41b0adf361cabe419c6d8d51dfe3a59544ee457"
Missing separate debuginfo for /usr/lib64/libcrypto.so.1.1
Try: zypper install -C "debuginfo(build-id)=b92fac19ee6447264606897d4ba0fb54590d7348"
Missing separate debuginfo for /usr/lib64/libaccounts-glib.so.1
Try: zypper install -C "debuginfo(build-id)=f4805eca7feb627411075626da30b121d23a504d"
Missing separate debuginfo for /usr/lib64/libgio-2.0.so.0
Try: zypper install -C "debuginfo(build-id)=2663f799524f19383b670a021449306123e0b928"
Missing separate debuginfo for /usr/lib64/libgobject-2.0.so.0
Try: zypper install -C "debuginfo(build-id)=1abe555f1c274d79d6297e10b02bbe6fa521ac9c"
Missing separate debuginfo for /usr/lib64/libQt5Xml.so.5
Try: zypper install -C "debuginfo(build-id)=c6dbcbe7d8395c814cdcf24ac991b3c87bebdd91"
Missing separate debuginfo for /usr/lib64/libhybris-common.so.1
Try: zypper install -C "debuginfo(build-id)=0bd0a50173c6817d36fc8adbebadd9f6be611dc3"
Missing separate debuginfo for /lib64/librt.so.1
Try: zypper install -C "debuginfo(build-id)=f16541dd64e3318221b60cf6f22a8c931032d584"
Missing separate debuginfo for /usr/lib64/libpcre2-8.so.0
Try: zypper install -C "debuginfo(build-id)=e20cadbe8653f428a84f1e8f29a2110fbe2db906"
Missing separate debuginfo for /usr/lib64/liblzma.so.5
Try: zypper install -C "debuginfo(build-id)=ee87e6a957a1a31e5cb48e4ef9aa689fb8b4cbc8"
Missing separate debuginfo for /usr/lib64/libcap.so.2
Try: zypper install -C "debuginfo(build-id)=bec7dbf9328d6a493a7de0dd12bb7482c3c7e65e"
Missing separate debuginfo for /usr/lib64/libmount.so.1
Try: zypper install -C "debuginfo(build-id)=9e197048093ccd33e45125c827ba6cc946df891a"
Missing separate debuginfo for /usr/lib64/libgcrypt.so.20
Try: zypper install -C "debuginfo(build-id)=503065d0682d53a301e319a9438e8332b2d4ca48"
Missing separate debuginfo for /usr/lib64/libxml2.so.2
Try: zypper install -C "debuginfo(build-id)=ae7b62dc3d5e6076cbbf56406f567c42eef6ca1d"
Missing separate debuginfo for /usr/lib64/libsqlite3.so.0
Try: zypper install -C "debuginfo(build-id)=47514c552f1327537f776b235e8e3f843feacb6f"
Missing separate debuginfo for /usr/lib64/libgmodule-2.0.so.0
Try: zypper install -C "debuginfo(build-id)=e06f7d4c60dc1f041491a95fcb1b01a94351941d"
Missing separate debuginfo for /usr/lib64/libselinux.so.1
Try: zypper install -C "debuginfo(build-id)=a1388055c76f9456b8f7f29afd0bd464021df8e2"
Missing separate debuginfo for /lib64/libresolv.so.2
Try: zypper install -C "debuginfo(build-id)=f982ed2964cd916222e693baa07caf7e5e3667d5"
Missing separate debuginfo for /usr/lib64/libffi.so.8
Try: zypper install -C "debuginfo(build-id)=02c42daa2e50a1105605b0e0567e0a6733a6ce3f"
Missing separate debuginfo for /usr/lib64/libblkid.so.1
Try: zypper install -C "debuginfo(build-id)=181c39e9c9d01dadf44be5bc79cbf3afe0409ae8"
Missing separate debuginfo for /usr/lib64/libgpg-error.so.0
Try: zypper install -C "debuginfo(build-id)=760ed76fbeeec5ad23ee0f217780bccdcdb345a0"
Missing separate debuginfo for /usr/lib64/libpcre.so.1
Try: zypper install -C "debuginfo(build-id)=2506670b009ccf18a165bc237aba310ea5c55632"
Missing separate debuginfo for /usr/lib64/qt5/plugins/platforms/libqminimal.so
Try: zypper install -C "debuginfo(build-id)=e1c47102c5641e29c290e2e5cb6219da7b424ebb"
Missing separate debuginfo for /usr/lib64/libfreetype.so.6
Try: zypper install -C "debuginfo(build-id)=406ca85627daaced6f5481e6b96f7c527ffda8c4"
Missing separate debuginfo for /usr/lib64/libfontconfig.so.1
Try: zypper install -C "debuginfo(build-id)=33d6ffdb533d1e8862a78e7d4f233bd2b83b5a54"
Missing separate debuginfo for /usr/lib64/libbz2.so.1
Try: zypper install -C "debuginfo(build-id)=121200fd6f6ac9421e349296482309af47179dc3"
Missing separate debuginfo for /usr/lib64/libexpat.so.1
Try: zypper install -C "debuginfo(build-id)=3981bce167f0a362a35b6584f5fedf351840f3c6"
[New LWP 52899]
Missing separate debuginfo for /lib64/libnss_db.so.2
Try: zypper install -C "debuginfo(build-id)=93c0e50e1164d084fd87ec8f11d23dea2f685084"
Missing separate debuginfo for /lib64/libnss_files.so.2
Try: zypper install -C "debuginfo(build-id)=df8c620c7c779ae9975131ed1f60056765d2f9ad"

** (process:52896): WARNING **: 17:04:37.672: Could not stat accounts privilege directory

** (process:52896): CRITICAL **: 17:04:37.672: ag_manager_set_abort_on_db_timeout: assertion 'AG_IS_MANAGER (manager)' failed
Missing separate debuginfo for /usr/lib64/qt5/plugins/sqldrivers/libqsqlite.so
Try: zypper install -C "debuginfo(build-id)=5dcf9cb252a1b5a6bcaf38c1606cb98df58167a9"

** (process:52896): CRITICAL **: 17:04:37.822: ag_manager_list_by_service_type: assertion 'AG_IS_MANAGER (manager)' failed

** (process:52896): CRITICAL **: 17:04:37.867: ag_manager_list_by_service_type: assertion 'AG_IS_MANAGER (manager)' failed
Missing separate debuginfo for /usr/lib64/qt5/plugins/messageserverplugins/libattachmentdownloader.so
Try: zypper install -C "debuginfo(build-id)=a69b32749207ea761c97b98fc8156a36a46a59c7"
Missing separate debuginfo for /usr/lib64/qt5/plugins/messageserverplugins/libnotifications.so
Try: zypper install -C "debuginfo(build-id)=0d920b5094b1dc34e6882c686cb078731673b5ad"
Missing separate debuginfo for /usr/lib64/libnemotransferengine-qt5.so.2
Try: zypper install -C "debuginfo(build-id)=4918213e9f88d01f970c7399e08d16ce8db06e30"
Missing separate debuginfo for /usr/lib64/libnemonotifications-qt5.so.1
Try: zypper install -C "debuginfo(build-id)=b073df43aa3c66ab22b1dbeaf0243d8919e66fac"
Missing separate debuginfo for /usr/lib64/libnemoemail-qt5.so.0
Try: zypper install -C "debuginfo(build-id)=14592af4d80971a1af8d8f9aa762b232226dcb5e"
Missing separate debuginfo for /usr/lib64/libquillmetadata-qt5.so.2
Try: zypper install -C "debuginfo(build-id)=f73fc724357ac84d633cedb81e562a48363c1555"
Missing separate debuginfo for /usr/lib64/libexif.so.12
Try: zypper install -C "debuginfo(build-id)=d15ad2b35dade879d2d718bfe954b71dc2d43d82"
Missing separate debuginfo for /usr/lib64/libexempi.so.8
Try: zypper install -C "debuginfo(build-id)=73d25ddc2835e5231b572e7422020aead5f61c95"
Missing separate debuginfo for /usr/lib64/libjpeg.so.62
Try: zypper install -C "debuginfo(build-id)=268e16c28e9f7f269b71705a4760402bfbdd4a18"

** (process:52896): CRITICAL **: 17:04:37.930: ag_manager_list_by_service_type: assertion 'AG_IS_MANAGER (manager)' failed

** (process:52896): CRITICAL **: 17:04:37.935: ag_manager_list_by_service_type: assertion 'AG_IS_MANAGER (manager)' failed

rob_kouw · 27 July 2025 15:25

After installing some debuginfo (how much is there anyway?), I tried again. This is the result:

#0  0x0000007ff6f96e14 in __GI___poll (fds=0x55555f4720, nfds=4, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:41
#1  0x0000007ff63ef5f0 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x0000007ff63efe34 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x0000007ff753067c in QEventDispatcherGlib::processEvents (this=0x55555e9cb0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#4  0x0000007ff74daf84 in QEventLoop::exec (this=this@entry=0x7ffffff550, flags=..., flags@entry=...)
    at ../../include/QtCore/../../src/corelib/global/qflags.h:53
#5  0x0000007ff74e29e4 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:111
#6  0x0000007ff78420e0 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1617
#7  0x0000005555560924 in main (argc=<optimized out>, argv=<optimized out>) at main.cpp:62

rob_kouw · 27 July 2025 15:44

@dcaliste After installing some debugging packages, the backtrace showed this:

(gdb) bt
#0  0x0000007ff6f96e14 in __GI___poll (fds=0x55555f4720, nfds=4, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:41
#1  0x0000007ff63ef5f0 in g_main_context_poll_unlocked (priority=<optimized out>, n_fds=4, fds=0x55555f4720, timeout=<optimized out>, context=0x55555eba20)
    at ../glib/gmain.c:4653
#2  g_main_context_iterate_unlocked (context=context@entry=0x55555eba20, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at ../glib/gmain.c:4344
#3  0x0000007ff63efe34 in g_main_context_iteration (context=0x55555eba20, may_block=1) at ../glib/gmain.c:4414
#4  0x0000007ff753067c in QEventDispatcherGlib::processEvents (this=0x55555e9cb0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#5  0x0000007ff74daf84 in QEventLoop::exec (this=this@entry=0x7ffffff550, flags=..., flags@entry=...)
    at ../../include/QtCore/../../src/corelib/global/qflags.h:53
#6  0x0000007ff74e29e4 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:111
#7  0x0000007ff78420e0 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1617
#8  0x0000005555560924 in main (argc=<optimized out>, argv=<optimized out>) at main.cpp:62

And one final try:

Thread 1 "messageserver5" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50        return ret;
(gdb) Quit
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x0000007ff6edcd20 in __GI_abort () at abort.c:79
#2  0x0000007ff7eca198 in LogSystem::debugMsgFwd (type=<optimized out>, ctxt=..., msg=...) at support/qlogsystem.cpp:110
#3  0x0000007ff7308f28 in qt_message_print (msgType=msgType@entry=QtFatalMsg, context=..., message=...) at global/qlogging.cpp:1631
#4  0x0000007ff73090fc in qt_message (msgType=msgType@entry=QtFatalMsg, context=..., msg=<optimized out>,
    ap=<error reading variable: Cannot access memory at address 0x8>) at global/qlogging.cpp:292
#5  0x0000007ff72f5b30 in QMessageLogger::fatal (this=<optimized out>, msg=<optimized out>) at global/qlogging.cpp:804
#6  0x0000005555562428 in MessageServer::MessageServer (this=this@entry=0x7ffffff5d0, parent=parent@entry=0x0) at messageserver.cpp:133
#7  0x0000005555560920 in main (argc=<optimized out>, argv=<optimized out>) at main.cpp:60

By the way: I could not install two more debugging packages.

[root@XIII defaultuser]# zypper install -C "debuginfo(build-id)=9ead5df9b5050766a1b64e9d778b33ddf59e340c"
Loading repository data...
Reading installed packages...
No provider of 'debuginfo(build-id)=9ead5df9b5050766a1b64e9d778b33ddf59e340c' found. ['--plus-content debug'?]
Resolving package dependencies...
Nothing to do.
[root@XIII defaultuser]# zypper install -C "debuginfo(build-id)=0bd0a50173c6817d36fc8adbebadd9f6be611dc3"
Loading repository data...
Reading installed packages...
No provider of 'debuginfo(build-id)=0bd0a50173c6817d36fc8adbebadd9f6be611dc3' found. ['--plus-content debug'?]
Resolving package dependencies...
Nothing to do.

dcaliste · 28 July 2025 07:09

Thanks for the debug symbols, I forgot about them. It’s fine with what you installed.

The problem with the backtrace you obtained is that it’s the one of the daemon starting (and immediately stopping) while another instance of it is already running. I guess you had run step 1. at one point and arrive to actually running the daemon inside the debugger a while later. Maybe the email client, or the automatic synchronisation daemon kicked in and ask for the daemon running. Resulting with systemd starting the daemon in the background before you arrive to step 4.

May I ask you to retry, maybe with the email application stopped, so you can obtained a backtrace of a running daemon ? I’m sorry if this procedure seems long and annoying…

rob_kouw · 15 August 2025 16:15

Hi Damien,
What about this?
Kind regards, Rob

Thread 1 "messageserver5" received signal SIGSEGV, Segmentation fault.
0x0000007fef19f1f0 in quoteIMAPString (input=...) at passwordplugin.cpp:68
68          while (it != result.end()) {
(gdb) bt
#0  0x0000007fef19f1f0 in quoteIMAPString (input=...) at passwordplugin.cpp:68
#1  0x0000007fef19f36c in quoteIMAPString (input=...) at passwordplugin.cpp:83
#2  0x0000007fef1a01a4 in SSOPasswordPlugin::getIMAPAuthentication (this=this@entry=0x55558c99c0, password=..., username=...) at passwordplugin.cpp:112
#3  0x0000007fef1a1ff8 in SSOPasswordPlugin::authentication (this=0x55558c99c0, sessionData=..., serviceType=..., userName=...) at passwordplugin.cpp:195
#4  0x0000007ff7da3ed0 in SSOSessionManager::sessionResponse (this=0x5555b6b500, sessionData=...) at ssosessionmanager.cpp:376
#5  0x0000007ff7508cdc in QMetaObject::activate (sender=sender@entry=0x5555b6f620, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=2,
    argv=argv@entry=0x7fffffed50) at kernel/qobject.cpp:3730
#6  0x0000007ff7509354 in QMetaObject::activate (sender=sender@entry=0x5555b6f620, m=<optimized out>, local_signal_index=local_signal_index@entry=2,
    argv=argv@entry=0x7fffffed50) at kernel/qobject.cpp:3595
#7  0x0000007ff6cdb1b4 in SignOn::AuthSession::response (this=this@entry=0x5555b6f620, _t1=...) at moc_authsession.cpp:202
#8  0x0000007ff6cce014 in SignOn::AuthSessionImpl::responseSlot (this=0x5555b4afb0, call=<optimized out>) at authsessionimpl.cpp:293
#9  0x0000007ff7508cdc in QMetaObject::activate (sender=sender@entry=0x5555b73600, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=1,
    argv=argv@entry=0x7fffffef20) at kernel/qobject.cpp:3730
#10 0x0000007ff7509354 in QMetaObject::activate (sender=sender@entry=0x5555b73600, m=m@entry=0x7ff6d029f0 <SignOn::PendingCall::staticMetaObject>,
    local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fffffef20) at kernel/qobject.cpp:3595
#11 0x0000007ff6cdb948 in SignOn::PendingCall::success (this=this@entry=0x5555b73600, _t1=<optimized out>, _t1@entry=0x5555b815f0) at moc_async-dbus-proxy.cpp:205
#12 0x0000007ff6cc4928 in SignOn::PendingCall::onFinished (this=0x5555b73600, watcher=0x5555b815f0) at async-dbus-proxy.cpp:126
#13 0x0000007ff7508cdc in QMetaObject::activate (sender=0x5555b815f0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0,
    argv=argv@entry=0x7ffffff0b0) at kernel/qobject.cpp:3730
#14 0x0000007ff7509354 in QMetaObject::activate (sender=<optimized out>, m=<optimized out>, local_signal_index=local_signal_index@entry=0,
    argv=argv@entry=0x7ffffff0b0) at kernel/qobject.cpp:3595
#15 0x0000007ff7d027d8 in QDBusPendingCallWatcher::finished (this=<optimized out>, _t1=<optimized out>) at .moc/moc_qdbuspendingcall.cpp:152
#16 0x0000007ff75098cc in QObject::event (this=0x5555b815f0, e=<optimized out>) at kernel/qobject.cpp:1256
#17 0x0000007ff74dcb98 in QCoreApplication::notifyInternal2 (receiver=receiver@entry=0x5555b815f0, event=event@entry=0x5555b54d10) at kernel/qcoreapplication.cpp:1015
#18 0x0000007ff74defcc in QCoreApplication::sendEvent (event=0x5555b54d10, receiver=0x5555b815f0) at kernel/qcoreapplication.h:225
#19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55555e5750) at kernel/qcoreapplication.cpp:1650
#20 0x0000007ff74df504 in QCoreApplication::sendPostedEvents (receiver=<optimized out>, event_type=<optimized out>) at kernel/qcoreapplication.cpp:1508
#21 0x0000007ff7530208 in postEventSourceDispatch (s=0x55555ebc70) at kernel/qeventdispatcher_glib.cpp:275
#22 0x0000007ff63ec4dc in g_main_dispatch (context=context@entry=0x55555ebb00) at ../glib/gmain.c:3476
#23 0x0000007ff63ef648 in g_main_context_dispatch_unlocked (context=0x55555ebb00) at ../glib/gmain.c:4284
#24 g_main_context_iterate_unlocked (context=context@entry=0x55555ebb00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4349
#25 0x0000007ff63efe34 in g_main_context_iteration (context=0x55555ebb00, may_block=1) at ../glib/gmain.c:4414
#26 0x0000007ff753067c in QEventDispatcherGlib::processEvents (this=0x55555dd800, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#27 0x0000007ff74daf84 in QEventLoop::exec (this=this@entry=0x7ffffff4e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:53
#28 0x0000007ff74e29e4 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:111
#29 0x0000007ff78420e0 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1617
#30 0x0000005555560924 in main (argc=<optimized out>, argv=<optimized out>) at main.cpp:62