Bug 2437 - Claws mail crash when i create a IMAP+SSL account
Summary: Claws mail crash when i create a IMAP+SSL account
Status: RESOLVED DUPLICATE of bug 2414
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Other (show other bugs)
Version: 3.7.9
Hardware: PC Linux
: P3 blocker
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2011-05-25 09:50 UTC by dstanzani
Modified: 2011-05-26 08:34 UTC (History)
0 users

See Also:


Attachments

Description dstanzani 2011-05-25 09:50:46 UTC
Claws Mail version 3.7.9
GTK+ version 2.24.4 / GLib 2.28.7
Locale: en_US.UTF-8 (charset: UTF-8)
Features: IPv6 iconv compface GnuTLS LDAP JPilot GNU/aspell libetpan libSM
Operating system: Linux 2.6.38-ARCH (x86_64)
C Library: GNU libc 2.13
--
[Thread debugging using libthread_db enabled]
[New Thread 0x7f5e861fb700 (LWP 6226)]
0x00007f5e9136b32d in waitpid () from /lib/libpthread.so.0
#0  0x00007f5e9136b32d in waitpid () from /lib/libpthread.so.0
No symbol table info available.
#1  0x000000000049835b in ?? ()
No symbol table info available.
#2  <signal handler called>
No symbol table info available.
#3  0x00007f5e8b9cd547 in XGetXCBConnection () from /usr/lib/libX11-xcb.so.1
No symbol table info available.
#4  0x00007f5e917a22f1 in sn_display_new () from /usr/lib/libstartup-notification-1.so.0
No symbol table info available.
#5  0x00000000004443de in ?? ()
No symbol table info available.
#6  0x000000000044662c in main ()
No symbol table info available.
Kill the program being debugged? (y or n) [answered Y; input not from terminal]




Program received signal SIGSEGV, Segmentation fault.
0x00007fffef843547 in XGetXCBConnection () from /usr/lib/libX11-xcb.so.1
(gdb) backtrace
#0  0x00007fffef843547 in XGetXCBConnection () from /usr/lib/libX11-xcb.so.1
#1  0x00007ffff56182f1 in sn_display_new ()
   from /usr/lib/libstartup-notification-1.so.0
#2  0x00000000004443de in ?? ()
#3  0x000000000044662c in main ()
(gdb)
Comment 1 Paul 2011-05-26 08:34:12 UTC

*** This bug has been marked as a duplicate of bug 2414 ***

Note You need to log in before you can comment on or make changes to this bug.