Bug#985688: [Debian-on-mobile-maintainers] Bug#985688: chatty: segfault when syncing history with certain accounts

2021-03-23 Thread Guido Günther
control: forwarded -1 https://source.puri.sm/Librem5/chatty/-/issues/490

Hi Vagrant,
On Mon, Mar 22, 2021 at 01:46:24PM -0700, Vagrant Cascadian wrote:
> On 2021-03-22, Guido Günther wrote:
> > Could you provide a gdb backtrace with debugging symbols?
> 
> Thanks for the quick response.
> 
> Hopefully this is what you were looking for (swapped out my client with
> USERNAME@EXAMPLE and the connection to a multi-user-chat with
> MUC@EXAMPLE):

That's it. Forwarded to

https://source.puri.sm/Librem5/chatty/-/issues/490

Thanks,
 -- Guido



Bug#985688: chatty: segfault when syncing history with certain accounts

2021-03-22 Thread Vagrant Cascadian
On 2021-03-22, Vagrant Cascadian wrote:
> On 2021-03-22, Guido Günther wrote:
>> Could you provide a gdb backtrace with debugging symbols?
>
> Thanks for the quick response.
>
> Hopefully this is what you were looking for (swapped out my client with
> USERNAME@EXAMPLE and the connection to a multi-user-chat with
> MUC@EXAMPLE):

The MUC is disc...@conference.soprani.ca, and someone else on that MUC
was unable to add it in chatty, so maybe there's some safeguard in
chatty to prevent incompatible JID/MUC? Since I had added the MUC with
another client chatty is blindly trying to sync when MAM is enabled?



live well,
  vagrant


signature.asc
Description: PGP signature


Bug#985688: chatty: segfault when syncing history with certain accounts

2021-03-22 Thread Vagrant Cascadian
On 2021-03-22, Guido Günther wrote:
> Could you provide a gdb backtrace with debugging symbols?

Thanks for the quick response.

Hopefully this is what you were looking for (swapped out my client with
USERNAME@EXAMPLE and the connection to a multi-user-chat with
MUC@EXAMPLE):

(gdb) r
Starting program: /usr/bin/chatty
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x71272700 (LWP 3560323)]
[New Thread 0x70a71700 (LWP 3560324)]
[New Thread 0x7fffebfff700 (LWP 3560325)]
[New Thread 0x7fffeb7fe700 (LWP 3560326)]
[New Thread 0x7fffeaffd700 (LWP 3560327)]
[New Thread 0x7fffea7fc700 (LWP 3560328)]
[New Thread 0x7fffe9ffb700 (LWP 3560329)]

(sm.puri.Chatty:3560301): chatty-folks-WARNING **: 13:38:26.372: Error:
Error calling StartServiceByName for
org.gnome.evolution.dataserver.Sources5: Unit
evolution-source-registry.service not found.
[Thread 0x7fffeaffd700 (LWP 3560327) exited]
[Thread 0x7fffea7fc700 (LWP 3560328) exited]
[New Thread 0x7fffea7fc700 (LWP 3560330)]
[New Thread 0x7fffeaffd700 (LWP 3560331)]
[New Thread 0x7fffbfe85700 (LWP 3560332)]

** (sm.puri.Chatty:3560301): CRITICAL **: 13:38:27.041:
   purple_presence_get_active_status: assertion 'presence != NULL'
   failed

** (sm.puri.Chatty:3560301): CRITICAL **: 13:38:27.041:
   purple_status_is_available: assertion 'status != NULL' failed
[Detaching after fork from child process 3560333]

** (sm.puri.Chatty:3560301): CRITICAL **: 13:38:27.043:
   purple_presence_get_active_status: assertion 'presence != NULL'
   failed

** (sm.puri.Chatty:3560301): CRITICAL **: 13:38:27.047:
   purple_presence_is_online: assertion 'presence != NULL' failed

** (sm.puri.Chatty:3560301): CRITICAL **: 13:38:27.054:
   purple_presence_is_online: assertion 'presence != NULL' failed
[Detaching after fork from child process 3560334]
[Detaching after fork from child process 3560353]

** (sm.puri.Chatty:3560301): CRITICAL **: 13:38:28.063:
   xmlnode_set_attrib_full: assertion 'value != NULL' failed

** (sm.puri.Chatty:3560301): CRITICAL **: 13:38:28.063:
   purple_find_conversation_with_account: assertion 'name != NULL'
   failed

** (sm.puri.Chatty:3560301): CRITICAL **: 13:38:28.063:
   purple_conversation_new: assertion 'name != NULL' failed

Thread 1 "chatty" received signal SIGSEGV, Segmentation fault.
cb_chatty_mam_msg_received (pc=, type=,
id=, from=,
to=, msg=) at
../src/xeps/chatty-xep-0313.c:800
800 ../src/xeps/chatty-xep-0313.c: No such file or directory.
(gdb) bt
#0  cb_chatty_mam_msg_received (pc=, type=, id=, from=,
to=, msg=) at
../src/xeps/chatty-xep-0313.c:800
#1  0x771351b4 in
purple_marshal_BOOLEAN__POINTER_POINTER_POINTER_POINTER_POINTER_POINTER
(
cb=, args=, data=,
return_val=0x7fffdb28)
at ././libpurple/signals.c:1019
#2  0x77133e05 in purple_signal_emit_vargs_return_1
(instance=, signal=0x7fffdb28 "",
signal@entry=0x770818c2 "jabber-receiving-message",
args=args@entry=0x7fffdb80)
at ././libpurple/signals.c:563
#3  0x77133f6e in purple_signal_emit_return_1
(instance=,
signal=signal@entry=0x770818c2 "jabber-receiving-message") at
././libpurple/signals.c:506
#4  0x7706f1f4 in jabber_message_parse (js=0x55c97ee0,
packet=0x556a34b0)
at ././libpurple/protocols/jabber/message.c:530
#5  0x77071794 in jabber_parser_element_end_libxml
(user_data=0x55c97ee0, element_name=,
prefix=, namespace=) at
././libpurple/protocols/jabber/parser.c:169
#6  0x759174d7 in xmlParseEndTag2 (ctxt=0x55d8e3d0,
prefix=0x0, URI=0x55d8fe14 "jabber:client",
nsNr=0, tlen=0, line=) at ../../parser.c:9690
#7  0x75921ed9 in xmlParseTryOrFinish
(ctxt=ctxt@entry=0x55d8e3d0, terminate=terminate@entry=0)
at ../../parser.c:11568
#8  0x75923138 in xmlParseChunk__internal_alias
(ctxt=0x55d8e3d0,
chunk=0x77098b00  "rplebfa0ca76'>, terminate=terminate@entry=0) at
../../parser.c:12281
#9  0x77071c5e in jabber_parser_process (js=0x55c97ee0,
buf=, len=)
at ././libpurple/protocols/jabber/parser.c:279
#10 0x77060a3a in jabber_recv_cb_ssl (data=0x55c979f0,
gsc=0x55d39190, cond=)
at ././libpurple/protocols/jabber/jabber.c:694
#11 0x5556f502 in purple_glib_io_invoke (source=,
condition=,
data=0x55699940) at ../src/chatty-manager.c:299
#12 0x77c9bd6f in g_main_dispatch (context=0x556375d0) at
../../../glib/gmain.c:3325
#13 g_main_context_dispatch (context=0x556375d0) at
../../../glib/gmain.c:4043
--Type  for more, q to quit, c to continue without paging--
#14 0x77c9c118 in g_main_context_iterate
(context=context@entry=0x556375d0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
../../../glib/gmain.c:4119
#15 0x77c9c1cf in g_main_context_iteration
(context=context@entry=0x556375d0, may_block=may_block@entry=1)
at 

Bug#985688: [Debian-on-mobile-maintainers] Bug#985688: chatty: segfault when syncing history with certain accounts

2021-03-22 Thread Guido Günther
Hi,
On Sun, Mar 21, 2021 at 11:06:53PM -0700, Vagrant Cascadian wrote:
> (sm.puri.Chatty:3457658): chatty-folks-WARNING **: 22:40:08.405: Error:
> Error calling StartServiceByName for
> org.gnome.evolution.dataserver.Sources5: Unit
> evolution-source-registry.service not found.
> 
> ** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:08.523:
>purple_presence_is_online: assertion 'presence != NULL' failed
> 
> ** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:08.526:
>purple_presence_is_online: assertion 'presence != NULL' failed
> 
> ** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:08.526:
>purple_presence_get_active_status: assertion 'presence != NULL'
>failed
> 
> ** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:08.526:
>purple_status_is_available: assertion 'status != NULL' failed
> 
> ** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:08.576:
>purple_presence_get_active_status: assertion 'presence != NULL'
>failed
> 
> ** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:09.450:
>xmlnode_set_attrib_full: assertion 'value != NULL' failed
> 
> ** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:09.451:
>purple_find_conversation_with_account: assertion 'name != NULL'
>failed
> 
> ** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:09.451:
>purple_conversation_new: assertion 'name != NULL' failed
> Segmentation fault

Could you provide a gdb backtrace with debugging symbols?

Cheers,
 -- Guido

> 
> 
> Thanks for maintaining chatty!
> 
> 
> live well,
>   vagrant
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing-security
>   APT policy: (500, 'testing-security'), (500, 'testing'), (12, 'unstable'), 
> (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: armhf, arm64
> 
> Kernel: Linux 5.10.0-4-amd64 (SMP w/4 CPU threads)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages chatty depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
> ii  libc62.31-9
> ii  libcairo21.16.0-5
> ii  libebook-1.2-20  3.38.3-1
> ii  libebook-contacts-1.2-3  3.38.3-1
> ii  libedataserver-1.2-253.38.3-1
> ii  libfeedback-0.0-00.0.0+git20210125-1
> ii  libgcc-s110.2.1-6
> ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
> ii  libglib2.0-0 2.66.7-2
> ii  libgtk-3-0   3.24.24-3
> ii  libhandy-1-0 1.0.3-2
> ii  libpango-1.0-0   1.46.2-3
> ii  libpangocairo-1.0-0  1.46.2-3
> ii  libphonenumber8  8.12.16-4
> ii  libpurple0   2.14.1-1
> ii  libsqlite3-0 3.34.1-3
> ii  libstdc++6   10.2.1-6
> 
> Versions of packages chatty recommends:
> ii  purple-lurch 0.6.8+git20200527.388605-3
> pn  purple-mm-sms
> ii  purple-xmpp-carbons  0.2.3-1
> ii  purple-xmpp-http-upload  0.2.2-1
> 
> Versions of packages chatty suggests:
> pn  gnome-calls  
> 
> -- no debconf information



> ___
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers



signature.asc
Description: PGP signature


Bug#985688: chatty: segfault when syncing history with certain accounts

2021-03-22 Thread Vagrant Cascadian
Package: chatty
Version: 0.2.0-1+b1
Severity: normal

I used chatty for a bit with a newly created xmpp account, and it seemed
to work nicely with some basic testing.

When I added an xmpp account I had used with other clients (e.g. gajim
and conversations), chatty started crashing, unless I disable "Message
Archive Management". Then everything seems to mostly work fine, other
than the full history obviously being missing...

However, another similar account on the same server works fine. A
notable difference between the accounts is that the working account
doesn't have much (if any) history of using omemo, and the failing
account is using omemo almost exclusively. Another difference is the
failing account is subscribed to a MUC.

I don't know how to reproduce this with a newly created account; e.g. so
far it only fails on one specific account with all my history. History
that would be impractical to share...



$ chatty

(sm.puri.Chatty:3457658): chatty-folks-WARNING **: 22:40:08.405: Error:
Error calling StartServiceByName for
org.gnome.evolution.dataserver.Sources5: Unit
evolution-source-registry.service not found.

** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:08.523:
   purple_presence_is_online: assertion 'presence != NULL' failed

** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:08.526:
   purple_presence_is_online: assertion 'presence != NULL' failed

** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:08.526:
   purple_presence_get_active_status: assertion 'presence != NULL'
   failed

** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:08.526:
   purple_status_is_available: assertion 'status != NULL' failed

** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:08.576:
   purple_presence_get_active_status: assertion 'presence != NULL'
   failed

** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:09.450:
   xmlnode_set_attrib_full: assertion 'value != NULL' failed

** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:09.451:
   purple_find_conversation_with_account: assertion 'name != NULL'
   failed

** (sm.puri.Chatty:3457658): CRITICAL **: 22:40:09.451:
   purple_conversation_new: assertion 'name != NULL' failed
Segmentation fault


Thanks for maintaining chatty!


live well,
  vagrant


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (12, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, arm64

Kernel: Linux 5.10.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chatty depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libebook-1.2-20  3.38.3-1
ii  libebook-contacts-1.2-3  3.38.3-1
ii  libedataserver-1.2-253.38.3-1
ii  libfeedback-0.0-00.0.0+git20210125-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.7-2
ii  libgtk-3-0   3.24.24-3
ii  libhandy-1-0 1.0.3-2
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libphonenumber8  8.12.16-4
ii  libpurple0   2.14.1-1
ii  libsqlite3-0 3.34.1-3
ii  libstdc++6   10.2.1-6

Versions of packages chatty recommends:
ii  purple-lurch 0.6.8+git20200527.388605-3
pn  purple-mm-sms
ii  purple-xmpp-carbons  0.2.3-1
ii  purple-xmpp-http-upload  0.2.2-1

Versions of packages chatty suggests:
pn  gnome-calls  

-- no debconf information


signature.asc
Description: PGP signature