Since I upgraded to this version sylpheed-claws crushes each morning if I open mails. I'm not sure how much this bug report helps, because I'm not able to really reproduce it or give some hints why this happens. The crash happen only if I start sylpheed-claws with the menu bar. If I start it with a terminal to get a usefull crash output sylpheed never crashes. I don't understand this! How could I enable sylpheed-claws to write a crash dump file if it crashs? Until this problem is fixed I returned back to 1.9.15 Sorry for this unprecise bug report :-(
emerge --info, please...
Also, could you possibly change the relevant menu command to "sylpheed --debug >/home/youruser/sylpheed-debug.log" and after the crash attach the last few hundred or so lines from resulting file here?
> emerge --info Portage 2.0.51.22-r3 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r2, 2.6.13-gentoo-r3-1 i686) ================================================================= System uname: 2.6.13-gentoo-r3-1 i686 AMD Duron(tm) Gentoo Base System version 1.6.13 ccache version 2.3 [enabled] dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distcc distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.easynet.nl/mirror/gentoo/ http://ftp.easynet.nl/mirror/gentoo/ http://gentoo.inode.at/ ftp://gentoo.inode.at/source/" LANG="de_DE@euro" LINGUAS="de" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X aalib acpi alsa apm athena avi berkdb bitmap-fonts bonobo cairo cdr crypt cups curl dga dmx dnd dv dvd eds emboss encode esd f77 faad fam fbcon foomaticdb fortran freetype gd gdbm ggi gif gnome gnomedb gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile hal imagemagick imlib ipv6 java joystick jpeg jpeg2k libcaca libg++ libsamplerate libwww mad maildir mbox mikmod mmx mozilla moznoirc moznomail mozp3p mozsvg mp3 mpeg mule nas ncurses neXt nls nvidia objc ogg oggvorbis opengl oss pam pdflib perl plotutils png povray python qt quicktime readline ruby sasl scanner sdk sdl slang spell sqlite sse ssl stencil-buffer svg tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts udev unicode vorbis wmf xface xine xinerama xml xml2 xmms xprint xrandr xv zlib linguas_de userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, MAKEOPTS
Hm, I changed back to sylpheed-claws-1.9.15, but it still crashs. Perhaps I used another version before... I don't remember. I send you the logfile the next time it crashs.
Ok, I tried --debug, but there's nothing written in a debug or log file. Not in my home and not in .sylpheed or .sylpheed-claws. Currently I'm possible to reproduce the problem. If I try to open the gentoo bug-report mail, then sylpheed-claws crash. Some other mails work without problems. I noticed before, that only some mails force sylpheed to crash. And I don't understand why only if I start it *not* from a terminal. Even if I use sylpheed-claws& it doesn't crash. Only if I start it from the menubar. Is there a way to get the stdout/stderr messages from a yet running process without using a terminal? Perhaps redirect systemwide stderr/stdout to a file. I don't know how I should send usefull information or do a strace or gdb.
The --debug option causes debug output to be sent to stdout, so if you redirect the output to a file, just like I suggested earlier, you should be able to get it in a file.
Ah, I found the problem! Sorry, I misunderstood your message before. The last line was: codeconv.c:1498:current locale: de_DE@UTF-8 So it doesn't crash from terminal, because in the terminal are this locales: > env | grep LANG LANG=de_DE@euro GDM_LANG=de_DE@euro LANGUAGE=de_DE@UTF-8 I use Enlightenment-0.17-CVS and the locale is set to de_DE@UTF-8. So I think if I start from the icon panel there's another LANG setting and sylpheed-claws crashs with some mails. So this problem is locale specific. A workaround is to start sylpheed-claws with "LANG=de_DE@euro sylpheed-claws" from E17 icon panel. But I think the locale problem should be fixed in sylpheed-claws.
Please check if it's still an issue in 2.0.0 and if so please file a bug upstream.
*** Bug 121315 has been marked as a duplicate of this bug. ***
Andreas: any news on this?
Sorry for answering so late. I use sylpheed-claws-2.0.0_rc4 for some time now and it doesn't crash. Even without changing the locale. So I set the bugreport state to fixed. I hope this is correct.
Yes, that is correct procedure. Thanks for your time!
Sorry, I was to early. The bug is back. :-( I made an E17 update and the locale was reset to de_DE@UTF-8 and sylpheed-claws crashs again. I set the locale to de_DE@euro and it works now, but sylpheed-clwas should really not crash with UTF-8. So we need to upstream it...
Is this correct with UPSTREAM? Or should I report this to the sylpheed-claws community?
Yes, please file a bug at http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/index.cgi . Thanks.
