Kopete crashes upon successful connection to Jabber #39

Basic information

TDE version: R14.0.11
Distribution: Devuan Chimaera
Hardware: amd64

Description

A few seconds after "going online" on Jabber (The jabb.im homeserver specifically) it crashes completely.

Steps to reproduce

Add your jabb.im account on Kopete
Click light bulb and go online with any status

Screenshots

I attached the gdb .kcrash log.

kopete.kcrash.txt

25 KiB

Please, you can install the tdenetwork-trinity-dbg package and generate more detailed backtrace?

Please, you can install the tdenetwork-trinity-dbg package and generate more detailed backtrace?

Yes, sorry, I didn't think of having this before. Tthis was an install with most core metapackages except tdemultimedia and tdenetwork (since I don't use but a few apps included with those).

Well, I installed tde-network-trinity-dbg as you said and this time the window froze before crashing again after about 10 seconds. But here is the crash info for that (I can't tell if its any more detailed, but I assume this is what you meant)

kopete.kcrash.txt

54 KiB

@hunter0one can you also tell us your settings for the jabb account? For example do you have "use SSL encryption" checkbox enabled? If so, try disabling it. I remember having crashes at some point long ago but now I use it daily without any issue

@hunter0one can you also tell us your settings for the jabb account? For example do you have "use SSL encryption" checkbox enabled? If so, try disabling it. I remember having crashes at some point long ago but now I use it daily without any issue

I don't have this enabled. Plain text password authentication is enabled, if I disable this it says it's unable to connect (but thankfully doesn't crash). Its pretty much the defaults.

In "File Transfer" and "Privacy" I have not touched the settings at all, so nothing is entered into "File Transfer". In Privacy "Always send notifications" is checked and "Hide system and client info" is unchecked.

@MicheleC I was actually connecting to join the developer room. I took a hiatus the past few weeks since I started a new, much rougher job but I am back now. 😃

I've discovered a memory leak.. It seems while pilfering the settings and going into "Appearance" it causes Kopete to continuously start consuming more RAM and then takes Swap space.

Edit: Turns out it was also doing the same when it successfully connects to jabb.im.

Edit again: Entering the Trinity Control Center does the same now.. 🤔 But if you give the Control Center a minute, it levels out and loads fine.

Edit again: Entering the Trinity Control Center does the same now.. 🤔 But if you give the Control Center a minute, it levels out and loads fine.

that's weird. Is DCOP server doing fine?

that's weird. Is DCOP server doing fine?

On Devuan/Debian specifically, I always get DCOP issues in TDE. It will say something about "Check if DCOP server is running" despite it running anyways, but as a matter of fact since I've had these quirks with Kopete I haven't gotten any DCOP errors.

yeah it seems to be fine. Dcopserver is running in the background and I have no issues running KDCOP to browse everything in it.

@hunter0one
can you share more info on how to reproduce this issue? I use Kopete on Jabber every day and have no crashes. Maybe different config?

@hunter0one
can you share more info on how to reproduce this issue? I use Kopete on Jabber every day and have no crashes. Maybe different config?

The only thing I guess I did was I had problems setting up my password in it (and using kwallet as the password manager). I kept entering the wrong one and then had to manually delete the kwallet entry for it and retry. I finally got it right and it connects but crashes.

Speaking of which, I tried this again on a clean installation of Trinity (albeit R14.0.12) but it still crashes even with getting the password right the first time. No memory leakage thankfully.

Can you share the settings you are using? I will try the same here.
Do you have the password saved or do you input it manually?

Can you share the settings you are using? I will try the same here.
Do you have the password saved or do you input it manually?

The password is saved (and I have it set to remember password). Jabber settings are pretty much default but here just in case:

Basic Setup

Remember password

Connection

Allow plain-text password authentication

Location Settings:
** Resource: Kopete
** Priority: 5

File Transfer
(Nothing entered)

Privacy

Always send notifications
Always send displayed notifications
Always send typing notifications
Always send gone notifications (closing the window*

Thanks, will give it a go

I tried the same settings here, no crashes... Have you tried from a new clean linux account?

I tried the same settings here, no crashes... Have you tried from a new clean linux account?

This last try was on a clean linux account.

I managed to fix my DCOP issues by running chmod 7777to universally allow read/write permissions to the ICEauthority files, and Kopete still crashes, so now I know for sure it's unrelated to that issue.

Based on the crash log, it seems the problem is on a signal/slot call.
Could you try to launch kopete from command line and see if there is any message about signal/slots not found at start up?

Based on the crash log, it seems the problem is on a signal/slot call.
Could you try to launch kopete from command line and see if there is any message about signal/slots not found at start up?

Launching "kopete" in Terminal doesn't output anything. Just starts Kopete.

ok, thanks for the info. It's a very weird bug because it crashes on activating a signal. Looking at code and backtrace it seems the receiver is not a valid object.
I am unable to reproduce it though, so you need to add some debug info in tqt3 and try to catch why the SEGV comes out. Or launch kopete in gdb and go from there.

Michele and Slavek,
Thanks for the support. I have finally gotten around to trying this again and run into the same error. The profile settings are the same and I have debug symbols for tdenetwork installed. I did as Michele suggested and ran kopete in gdb from Konsole which generates the following:

Reading symbols from kopete...
Reading symbols from /usr/lib/debug/.build-id/79/fcfb7446420755225a859c8914fcba2b24b45c.debug...

warning: Loadable section ".note.gnu.build-id" outside of ELF segments

warning: Loadable section ".note.ABI-tag" outside of ELF segments
(gdb) run
Starting program: /opt/trinity/bin/kopete
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 24464]
[2022/07/10 09:26:32.953] TQSettings::sync: failed to open '/etc/tqt3/tqt_plugins_3.5rc.tmp' for writing
[Inferior 1 (process 24458) exited normally]
(gdb) [2022/07/10 09:26:40.943] TQFont::setPointSize: Point size <= 0 (-1)
[2022/07/10 09:26:40.943] TQFont::setPointSize: Point size <= 0 (-1)
[kcrash] TDECrash: Application 'kopete' crashing...

I would be lying if I said I know what's going on but I see an error with TQSettings failing to open a tqt_plugins temp file?

The jabb.im website has the following notice: "From September 30 2021 maybe you have problem with validation of our certificate. Please, update your client software".

Hi @hunter0one,
did you save the crash backtrace in gdb?
It looks like the crash is different from the one reported in the first crash dump you attached long ago...

Hello @MicheleC

did you save the crash backtrace in gdb?

I assume you mean the full log? I just copied and pasted that from Konsole in my last comment. I've attached the full log of the process recorded with script if it helps.

It looks like the crash is different from the one reported in the first crash dump you attached long ago...

Sorry if it was no help, but to be clear the bug was reproduced in the same way on the same computer (except now its TDE R14.0.12). I wasn't sure how to "add some debug info to tqt3" so I went with your previous instruction to launch kopete in gdb. DCOP is doing fine, but I came back to try Kopete again (Ive been using Matrix more than XMPP) and ran into the same issue.

kopete.txt

2.1 KiB

whne the crash happens inside gdb, you need to run a bt command to print the backtrace. Even better bt full that prints the backtrace of any thread.

whne the crash happens inside gdb, you need to run a bt command to print the backtrace. Even better bt full that prints the backtrace of any thread.

I tried this when Kopete crashed, but it prints "No stack".

you may need to run kopete with "--nofork" argument maybe. Notee, you have to pass the argument when already inside gdb, before running the actual program.

There was quite a lot more happened from this going online within Kopete. The whole window froze and I had to ctrl+alt+esc to exit it. As you wish, I've attached the full backtrace. Is this supposed to be different than what the TDE Crash Handler generates?

backtrace.txt

30 KiB

I had some freezing a couple of years ago, but no more since then. Even more mysterious.