liferea-bin crashed with SIGSEGV in _nss_wins_gethostbyname_r()

Bug #214192 reported by Bálint Magyar
14
Affects Status Importance Assigned to Milestone
base-files (Ubuntu)
New
Undecided
Unassigned
liferea (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: liferea

Ubuntu Gutsy updated to Ubuntu Hardy Beta, installed all updates available as of this post.

ProblemType: Crash
Architecture: i386
Date: Tue Apr 8 22:37:36 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/liferea-bin
Package: liferea 1.4.14-0ubuntu4
PackageArchitecture: i386
ProcCmdline: /usr/bin/liferea-bin
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: liferea
StacktraceTop:
 _nss_wins_gethostbyname_r () from /lib/libnss_wins.so.2
 gethostbyname_r () from /lib/tls/i686/cmov/libc.so.6
 PR_GetHostByName () from /usr/lib/libnspr4.so.0d
 ?? () from /usr/lib/xulrunner-1.9b5/libxul.so
 ?? ()
Title: liferea-bin crashed with SIGSEGV in _nss_wins_gethostbyname_r()
Uname: Linux 2.6.24-15-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner vboxusers video

Tags: apport-crash
Revision history for this message
Bálint Magyar (balintm) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_nss_wins_gethostbyname_r (hostname=0xbfc802d8 "amphetamine", he=0xbfc7f91c, buffer=0xbfc7f938 "",
gethostbyname_r@@GLIBC_2.1.2 () from /lib/tls/i686/cmov/libc.so.6
PR_GetHostByName (name=0xbfc802d8 "amphetamine", buf=0xbfc7fed8 "", bufsize=0, hp=0xbfc7feb0) at prnetdb.c:706
nsProfileLock::LockWithSymlink (this=0x812c89c, lockFilePath=@0xbfc80440, aHaveFcntlLock=1)
nsProfileLock::Lock (this=0x812c89c, aProfileDir=0x812c810, aUnlocker=0x0) at nsProfileLock.cpp:551

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in liferea:
importance: Undecided → Medium
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

How did this crash happen? Is it reproducible? If so, how?

Changed in liferea:
status: New → Incomplete
Revision history for this message
Bálint Magyar (balintm) wrote :

It happens on start 100% of the time; its window doesn't even show up for a second. It's not because of my configuration, the same thing happens if I delete my old settings.

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Does this still happen in Hardy final?

Revision history for this message
Bálint Magyar (balintm) wrote :

Yes, it does. In fact, I haven't been able to launch Liferea ONCE ever since upgrading to Hardy. I have not tried a clean Hardy install or the live CD. Would that help?

Revision history for this message
discont (discont) wrote :

Workaround: remove 'wins' from /etc/nsswitch.conf

was: "hosts: files wins mdns4_minimal [NOTFOUND=return] dns mdns4"
became: "hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4"

Revision history for this message
Bálint Magyar (balintm) wrote :

vivo, that works. So is this a libnss bug? I can confirm that having "wins" in the hosts list also makes mplayer crash with the attached output when trying to play a video stream through HTTP.

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Could someone verify if this is fixed with xulrunner-1.9 rc1 from hardy-proposed?

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

...and libnss3-1d from hardy-proposed

Revision history for this message
discont (discont) wrote :

Fixed! Thanx to developers!

Revision history for this message
discont (discont) wrote :

..but crash when I choose some posts in the feed. Removing 'wins' from /etc/nsswitch.conf resolve problem.

this is console output:
=============================================================
anton@antonio:~$ liferea
Registering '@mozilla.org/module-loader/python;1' (libpyloader.so)
Registering '@mozilla.org/network/protocol/about;1?what=python' (pyabout.py)

Liferea did receive signal 11 (Segmentation fault).
=============================================================

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

I don't have that file, what's the output of the following command? This is clearly not a Liferea bug
dpkg -S /etc/nsswitch.conf

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Looks like /etc/nsswitch.conf is copied from /usr/share/base-files/nsswitch.conf in base-files postinst.

Closing Liferea task as it's not a bug in Liferea, and reopening a base-files task for further investigation.

I don't have /etc/nsswitch.conf on this Hardy system (possibly due to bug #205750), but /usr/share/base-files/nsswitch.conf doesn't have 'wins' on it (and I have no clue what it means). Probably investigating why it's there and what it does is a good idea ;)

Changed in liferea:
status: Incomplete → Invalid
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

The crash is happening in:

#0 0xb45e97c5 in _nss_wins_gethostbyname_r (hostname=0xbfc802d8 "amphetamine", he=0xbfc7f91c, buffer=0xbfc7f938 "",
    buflen=1024, h_errnop=0xb707a6fc) at nsswitch/wins.c:83

Revision history for this message
discont (discont) wrote :

dpkg -S nsswitch.conf
manpages: /usr/share/man/man5/nsswitch.conf.5.gz
base-files: /usr/share/base-files/nsswitch.conf

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Does Liferea work if you launch it with sudo?

Revision history for this message
Roshan George (roshan-george) wrote :

Emilio, wins (Windows Internet Name Service) is necessary in nsswitch.conf if one is to get Windows-like Name Resolution. Since I have a Windows computer on this network, and I wish to connect to it by hostname, it requires wins in nsswitch.conf.

I, apparently, have this very problem. No, Liferea does not start if launched with sudo either. The error remains the same.

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Oh yeah! This looks like a duplicate of bug 286119, which is being fixed in Jaunty and Intrepid! Enjoy!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.