Your message dated Mon, 19 Feb 2018 11:16:17 +0100
with message-id 
<20180219111617.horde.therflsvigwlubw-xllt...@webmail.in-berlin.de>
and subject line mcabber: Segmentation fault when connecting to prosody server
has caused the Debian Bug report #598820,
regarding mcabber: Segmentation fault when connecting to prosody server
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
598820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mcabber
Version: 0.10.0-1
Severity: serious

Hi all,

mcabber dies with a segmentation fault as soon as it tries to connect to a
prosody server.

I'm not sure what exactly causes the bug, at least connecting to jabber.org
(with invalid auth data) does not make mcabber segfault, but connecting to
this specific server (which is running prosody) always results in a
segmentation fault.  It should also be noted that an mcabber running on Debian
squeeze is not affected, only the one in sid.
The segfault happens regardless of whether the jabber password was valid or
not.

mcabberrc:
> set jid             = d...@example.org
> set server          = jabber.wouldyoubuythis.net
> set port            = 5222
>
> set ssl             = 0
>
> set nickname        = derf
> set resource        = remnant
> set disable_random_resource = 1
> set priority        = 7
> set priority_away   = 1
>
> set logging         = 0
> set load_logs       = 0
> set beep_on_message = 1
>
> set aspell_enable   = 0

(yes, the @example.org is wrong, but the bug is reproducible with that, too)

mcabber output:

>      Special buffer: [status]
> 
> [13:38:50] Connecting to server: jabber.wouldyoubuythis.net
> [13:38:50]  using port 5222
> [13:38:50]  resource remnant
> 
>  [_]
> zsh: segmentation fault  mcabber


backtrace:

#0  lm_socket_ref (socket=0x62617422) at lm-socket.c:1208
#1  0x4004b332 in socket_connect_cb (source=0x9957a20, condition=G_IO_OUT, 
connect_data=0x9955900) at lm-socket.c:518
#2  0x400d46db in ?? () from /lib/libglib-2.0.so.0
#3  0x40090305 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#4  0x40093fe8 in ?? () from /lib/libglib-2.0.so.0
#5  0x400941c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#6  0x080535f6 in main ()

If there's any other information I can supply to help track down the bug, let
me know.

--Daniel


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mcabber depends on:
ii  libaspell15               0.60.6-4       GNU Aspell spell-checker runtime l
ii  libc6                     2.11.2-6       Embedded GNU C Library: Shared lib
ii  libglib2.0-0              2.24.2-1       The GLib library of C routines
ii  libgpg-error0             1.6-1          library for common error values an
ii  libgpgme11                1.2.0-1.2      GPGME - GnuPG Made Easy
ii  libidn11                  1.18-1         GNU Libidn library, implementation
ii  libloudmouth1-0           1.4.3-5        Lightweight C Jabber library
ii  libncursesw5              5.7+20100313-4 shared libraries for terminal hand
ii  libotr2                   3.2.0-2        Off-the-Record Messaging library

mcabber recommends no packages.

mcabber suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
I cannot reproduce the problem, therefore closing, sorry!
Feel free to reopen, if you can reproduce the problem with
recent mcabber (1.1.0-1) and prosody (0.10.0-1). Thanks!

--- End Message ---

Reply via email to