Sylpheed Segmentation Fault

LeoSolaris · 2009-09-01 15:15:26

I am not sure what to give you guys.

Here is the general run down of the issue:
Updated sylpheed yesterday from a mirror.
It will open, get all of my mail, and even allow me to read my mail and delete them. However, if I click reply or compose it segfaults. When I run it from terminal, that is all it says, "Segmentation Fault."

[zeddicus ~]$sylpheed #I clicked Compose
Segmentation fault
[zeddicus ~]$sylpheed #I clicked Reply
Segmentation fault

I have uninstalled it, reinstalled it, and yes, I cleaned out my package cache first, just to be safe. I know that it works Saturday, because I had been emailing my brother all afternoon. (His wife just had my nephew.) I have even uninstalled it along with all of it's dependencies, then reinstalled.

Edit: I went into the common preferences and changed it to automatically open an external editor for new messages and replies. It opens gvim, then segfaults anyways. Now I am even more confused.

I have no idea what to do next... report it upstream?

Last edited by LeoSolaris (2009-09-01 15:21:50)

forest76 · 2009-09-01 18:32:54

The same behaviour sylpheed give me; on i686 and x86_64 architectures.
When I run it with --debug parm I get message about no existing
/usr/bin/sylpheed directory. (seems it realy not exist)
I tried to recompile sylpheed on 2.7.1 and 2.7.0 versions, with
any positive results.

Greetings, Miroslaw

Xyne · 2009-09-01 23:59:20

I have the same issue here on x86_64 with version 2.7.1-1. I've tried rebuilding the package and downgrading to 2.6.0-1 but neither resolves the issue.

Here's the relevant output of "sylpheed --debug":

Creating compose window...
addressbook_load_completion
addressbook_load_completion... done
start_address_completion ref count 1
template.c:123 reading templates dir /home/foo/.sylpheed-2.0/templates
Segmentation fault

The templates directory is empty but it always has been.

I'd send an email to the maintainer but I can't right now.
*heads off to look for a replace/backup email client*

Pox · 2009-09-02 00:12:30

Same issue here on i686:

Creating compose window...
addressbook_load_completion
addressbook_load_completion... done
start_address_completion ref count 1
template.c:123 reading templates dir /home/pox/.sylpheed-2.0/templates
compose_exec_ext_editor(): pid: 23480 file: /home/pox/.sylpheed-2.0/tmp/tmpmsg-0x8b08e00.txt
zsh: segmentation fault  sylpheed --debug

Xyne · 2009-09-02 01:53:43

After unsuccessfully trying to locate the problem by adding debugging messages to the source code*, I tried changing the configuration options and managed to get a working build with this PKGBUILD:

# $Id: PKGBUILD 50642 2009-08-30 06:55:44Z allan $
# Maintainer: Alexander Fehr <pizzapunk gmail com>
# Contributor: dorphell <dorphell@archlinux.org>

pkgname=sylpheed
pkgver=2.7.1
pkgrel=1
pkgdesc="Lightweight and user-friendly e-mail client"
arch=('i686' 'x86_64')
url="http://sylpheed.sraoss.jp/en/"
license=('GPL')
depends=('gpgme' 'gtkspell')
makedepends=('compface')
source=(http://sylpheed.sraoss.jp/sylpheed/v2.7/sylpheed-$pkgver.tar.bz2)
md5sums=('1f470525c1fbe53253813a0978c18228')

build() {
  cd "$srcdir/sylpheed-$pkgver"

  ./configure --prefix=/usr --enable-ldap --disable-gtkspell || return 1
  make || return 1
  make DESTDIR="$pkgdir" install || return 1
}

It seems that the problem is due to gtkspell. I've tried rebuilding gtkspell but that did not resolve the issue either.

*misses the bugtracker*

*The function which creates the composition window returns successfully.

Last edited by Xyne (2009-09-02 01:54:16)

LeoSolaris · 2009-09-02 02:20:56

Smooth work Xyne

I am about to give your pkgbuild a shot.

I did get the same --debug message, and ya, it does happen right after the spell checker kicks in. Didn't sylpheed use aspell? For some reason I remember having to manually configure aspell so it would work with something... thought it was sylpheed anyways.

edit: So should we report this to the maintainers of gtkspell as well? And if this is just an issue with gtkspell, why does sylpheed die when opening an external editor rather than it's internal one? Why would it call gtkspell when it would not even be possible to use? That just flat out doesn't make a bit of sense, unless something about the way it is called in the source code demands it or the way gtkspell works, but even still, it should be initiated last, not first...

I will report back after I rebuild the package.

By the way Xyne, would you send me the debuging code to slipped into the sylpheed source code and a note about where it was placed? I am learning coding, and I am simply curious.

Last edited by LeoSolaris (2009-09-02 02:29:52)

Xyne · 2009-09-02 02:44:07

LeoSolaris wrote:

By the way Xyne, would you send me the debuging code to slipped into the sylpheed source code and a note about where it was placed? I am learning coding, and I am simply curious.

I've already overwritten the modified files. What I did though was download the sources with makepkg and then grep for the debugging messages starting with the last one before the segfault. The code uses a function called "debug_print" so I inserted several of those in various places following (in order of code execution) the last debug statement before the segfault. Each time I would get to the end of a function successfully, I would try to find the part of the code which had called that function and then continue from there. I stopped after the fifth compilation though.

LeoSolaris · 2009-09-02 04:36:10

Easy enough, thanks for the pointer!

By the way, I can confirm that it works with the --disable-gtkspell The lack of a spellchecker is slightly annoying though....

It is also not exactly gtkspell.... pidgin works fine and it uses gtkspell.

Last edited by LeoSolaris (2009-09-02 04:39:38)

Xyne · 2009-09-02 04:53:07

LeoSolaris wrote:

By the way, I can confirm that it works with the --disable-gtkspell The lack of a spellchecker is slightly annoying though....

I agree, but it's less annoying than not being able to compose messages at all.

Hopefully someone with more insight will take a look at this soon. I've emailed the maintainer via the forum so hopefully he'll see this and reply.

Allan · 2009-09-02 04:57:53

Hmmm.... I wonder who updated sylpheed....

Can someone try compiling it without CFLAGS set to see if this is an optimisation issue (add export CFLAGS="" to the PKGBUILD and same for CXXFLAGS). Otherwise I could rebuild with --disable-gtkspell for the meantime.

Edit: Fedora have the same version in rawhide without any real patches so it has to be something like this...

LeoSolaris · 2009-09-02 13:59:22

Allan wrote:

(add export CFLAGS="" to the PKGBUILD and same for CXXFLAGS).

I'll give it a whirl. Give me a few and I will report back.

REPORT: I tried it with sylpheed-svn (and provided I added the exports porperly) it did not work. When the spellcheck came on it segfaulted once again. Sorry Allen... (ya know... strangely enough, dropping back to the old one that worked on Saturday no longer works. Well, at least the iconmod version doesn't, which is the only old version available.)

# Contributor: Tim Yang <tdy@gmx.com>
pkgname=sylpheed-svn
pkgver=2081
pkgrel=1
pkgdesc="A lightweight and intuitive mail client"
arch=('i686' 'x86_64')
url="http://sylpheed.sraoss.jp/en/"
license=('GPL' 'LGPL')
depends=('gpgme' 'gtkspell')
makedepends=('compface' 'svn')
provides=('sylpheed')
conflicts=('sylpheed' 'sylpheed-iconmod')
source=()
md5sums=()

_svntrunk="svn://sylpheed.sraoss.jp/sylpheed/trunk"
_svnmod="sylpheed"

#Here is what I added, sans the extra spaces and commentary
export CFLAGS=""
export CXXFLAGS=""
###

build() {
  cd "$srcdir"

  msg "Connecting to the $_svnmod SVN server..."
  if [ -d "$_svnmod/.svn" ]; then
    cd $_svnmod && svn up -r $pkgver
    msg2 "Local files updated"
  else
    svn co $_svntrunk --config-dir ./ -r $pkgver $_svnmod
    msg2 "SVN checkout done"
  fi

  rm -rf "$srcdir/$_svnmod-build"
  cp -r "$srcdir/$_svnmod" "$srcdir/$_svnmod-build"
  cd "$srcdir/$_svnmod-build"

  msg "Starting make..."
  ./autogen.sh --prefix=/usr --enable-ldap || return 1
  make || return 1
  make DESTDIR="$pkgdir" install || return 1

  rm -rf "$srcdir/$_svnmod-build"
}

Last edited by LeoSolaris (2009-09-02 14:22:59)

murr · 2009-09-02 16:40:03

Having noticed that enchant was updated on Sunday, I downgraded it to version 1.4.2 and ... sylpheed seems to work again.

mykey · 2009-09-02 17:31:32

I downgraded enchant too - so meanwhile - any hints on what's the scoop?

LeoSolaris · 2009-09-02 18:08:58

So far, nadda. Unfortunately I do not have an old copy of enchant, so for now, I will just deal with the lack of spellcheck on my email.

Dang, that means I need to read all of those long emails over again... hmm... grammar wise, this might actually make an improvement in my email-fu...

Allan · 2009-09-02 23:33:50

So this is an enchant bug and not a sylpheed bug... hmm.... seems I wonder who updated enchant....

So, does someone want to try compiling enchant with no C{XX}FLAGS?

Xyne · 2009-09-03 00:03:40

I had no success recompiling enchant without C{XX}FLAGS. I've downgraded for now.

Admit it... you're just trying to advertise this shirt.

Allan · 2009-09-03 01:48:50

Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+sour … bug/413994

Edit: The dep tree goes sylpheed->gtkspell->enchant. Anyone tried rebuilding gtkspell?

Xyne · 2009-09-03 02:48:47

I've tried rebuilding enchant, gtkspell and sylpheed, in that order, both with and without C{XX}FLAGS. Sylpheed still segfaults.

LeoSolaris · 2009-09-03 11:01:22

So then it sounds like this is an upstream issue entirely, huh? Since other gtkspell dependent programs do not crash, it has to be something in the way sylpheed invokes gtkspell. (Tested that with pidgin)

Well, I will drop the sylpheed devs a note about it.

NOTE SENT:

Greetings Mr. Yamamoto,
I would like to say that I have enjoyed your email client. It is exceptionally lightweight, and very easy to use.
Unfortunately, something in the way sylpheed invokes gtkspell is causing a Segmentation Fault with the recently updated gtkspell/enchant. We over at Arch Linux Forums have resorted to either disabling spellcheck, or downgrading gtkspell. For a better understanding of our attempt to get sylpheed to play nicely with gtkspell/enchant, please visit this thread in our forums:
http://bbs.archlinux.org/viewtopic.php?id=79222

Thank you for all of your hard work, sylpheed is an excellent email program!
Kevin Eldridge
A.K.A LeoSolaris

Last edited by LeoSolaris (2009-09-03 11:23:43)

Cheifchimp · 2009-09-05 04:07:32

murr wrote:

Having noticed that enchant was updated on Sunday, I downgraded it to version 1.4.2 and ... sylpheed seems to work again.

Can you give me a 'complete idiots guide to' downgrade enchant to version 1.4.2, man pacman left it out
mik

bangkok_manouel · 2009-09-05 04:25:18

Cheifchimp wrote:

murr wrote:
Having noticed that enchant was updated on Sunday, I downgraded it to version 1.4.2 and ... sylpheed seems to work again.
Can you give me a 'complete idiots guide to' downgrade enchant to version 1.4.2, man pacman left it out
mik

http://wiki.archlinux.org/index.php/Downgrade_packages

Cheifchimp · 2009-09-05 05:04:52

thank you kind sir/madam

Mik

Cheifchimp · 2009-09-17 05:36:20

WTF can't we get the borked enchant-1.5.x ripped out of the repo until it is fit for purpose and of merchantable quality

Xyne · 2009-09-17 08:28:52

Cheifchimp wrote:

WTF can't we get the borked enchant-1.5.x ripped out of the repo until it is fit for purpose and of merchantable quality

Yeah, I'm sure that someone will get right on that when you ask like that. I agree that this is annoying but downgrading isn't that big of an issue.

Anyway, vote this up on the bugtracker.

Last edited by Xyne (2009-09-17 21:03:51)

LeoSolaris · 2009-09-17 17:17:31

That and almost all open source programs are distributed with the acknowledgment that there it is not guaranteed to be fit for any particular purpose or merchantability.

Besides, other programs that use enchant are not effected, so it may not be enchant. It may be a change in enchant (feature, not a bug) or the way slypheed calls enchant.

Arch Linux

#1 2009-09-01 15:15:26

Sylpheed Segmentation Fault

#2 2009-09-01 18:32:54

Re: Sylpheed Segmentation Fault

#3 2009-09-01 23:59:20

Re: Sylpheed Segmentation Fault

#4 2009-09-02 00:12:30

Re: Sylpheed Segmentation Fault

#5 2009-09-02 01:53:43

Re: Sylpheed Segmentation Fault

#6 2009-09-02 02:20:56

Re: Sylpheed Segmentation Fault

#7 2009-09-02 02:44:07

Re: Sylpheed Segmentation Fault

#8 2009-09-02 04:36:10

Re: Sylpheed Segmentation Fault

#9 2009-09-02 04:53:07

Re: Sylpheed Segmentation Fault

#10 2009-09-02 04:57:53

Re: Sylpheed Segmentation Fault

#11 2009-09-02 13:59:22

Re: Sylpheed Segmentation Fault

#12 2009-09-02 16:40:03

Re: Sylpheed Segmentation Fault

#13 2009-09-02 17:31:32

Re: Sylpheed Segmentation Fault

#14 2009-09-02 18:08:58

Re: Sylpheed Segmentation Fault

#15 2009-09-02 23:33:50

Re: Sylpheed Segmentation Fault

#16 2009-09-03 00:03:40

Re: Sylpheed Segmentation Fault

#17 2009-09-03 01:48:50

Re: Sylpheed Segmentation Fault

#18 2009-09-03 02:48:47

Re: Sylpheed Segmentation Fault

#19 2009-09-03 11:01:22

Re: Sylpheed Segmentation Fault

#20 2009-09-05 04:07:32

Re: Sylpheed Segmentation Fault

#21 2009-09-05 04:25:18

Re: Sylpheed Segmentation Fault

#22 2009-09-05 05:04:52

Re: Sylpheed Segmentation Fault

#23 2009-09-17 05:36:20

Re: Sylpheed Segmentation Fault

#24 2009-09-17 08:28:52

Re: Sylpheed Segmentation Fault

#25 2009-09-17 17:17:31

Re: Sylpheed Segmentation Fault

Board footer