16 Mar
2021
16 Mar
'21
1:40 a.m.
Hi Michele.
sorry for delay in sending this. problem with using gdb but got there in the
end and it's attached.
perhaps means nothing but when I start konquerorsu the pid only shows for 3 or
4 seconds in "top" before it is dropped.
by the way the xubuntu 16.04.7 is i386 32bit
All the best
Nigel.
Hi Nigel,
here is a section from the log you sent thruogh:
[2021/03/15 13:46:06.884] [konqueror] WARNING: Profile Loading Error: Less than two
children in Container0
ASSERT: debug output not ended with \n
[
#0 0xb71c5423 in kdBacktrace(int) from /opt/trinity/lib/libtdecore.so.14:0x000a7423
#1 0xb71c6db5 in kdbgstream::~kdbgstream() from
/opt/trinity/lib/libtdecore.so.14:0x000a8db5
#2 0xb7f0e87b in ?? from /opt/trinity/lib/libtdeinit_konqueror.so:0x0005787b
#3 0xb7f0dfad in ?? from /opt/trinity/lib/libtdeinit_konqueror.so:0x00056fad
#4 0xb7f0bb64 in ?? from /opt/trinity/lib/libtdeinit_konqueror.so:0x00054b64
#5 0xb7f146e5 in ?? from /opt/trinity/lib/libtdeinit_konqueror.so:0x0005d6e5
#6 0xb7ee271a in kdemain from /opt/trinity/lib/libtdeinit_konqueror.so:0x0002b71a
Few notes/questions.
1) you can see an ASSERT message there. That is likely a bug in TDE code, but the missing
symbols are making it
difficult to know where it is. You need tdelibs debug symbols installed for that, my bad I
assumed it was the tdebase
symbols at first. If you can retest, it will help to identify that spot. Note that it is
not a true ASSERT failure, it
is just a message.
2) I guess the SIGINT is something you manually generated with CTRL-C, so nothing to worry
about. It wasn't there in you
original trace as well.
A few questions to gather question.
1) is it a default TDE installation? or a partial package-limited installation?
2) have you tried deleting your konquerorrc config file and test again?
3) have you tried with a new user to see if there is any difference? And if allowed, can
you try as root as well, only
for comparison
4) are you building TDE with debug enabled yourself? AFAICT, kdDebug() does nothing in
standard DEB builds.
5) if you are doing 4), run tdedebugdialog from CLI. In the dialog that opens type konq
and then select 1201-1202-1203.
This will print a lot more info in your .xsession-errors file, which will allow to follow
through the code being
executed in konqueror. Please share that if you don't mind
Overall, it is a strange issue, there must be some specific things going on in your
installation. It will probably take
time to track it down.
Cheers
Michele