rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r()

Bug #545956 reported by chest069 on 2010-03-24
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

This happened when starting the program.

ProblemType: Crash
Architecture: amd64
Date: Wed Mar 24 08:21:55 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.7-0ubuntu8
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SegvAnalysis:
 Segfault happened at: 0x7f48cbbc4e4c <_nss_wins_gethostbyname_r+828>: movl $0x0,(%rax)
 PC (0x7f48cbbc4e4c) ok
 source "$0x0" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 _nss_wins_gethostbyname_r ()
 ?? () from /lib/libc.so.6
 getaddrinfo () from /lib/libc.so.6
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r()
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

chest069 (chest069) wrote :

StacktraceTop:
 _nss_wins_gethostbyname_r (
 gaih_inet (name=<value optimized out>,
 *__GI_getaddrinfo (name=0x1bf78f0 "one.ubuntu.com",
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0

Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Sergio Barjola (sbarjola) wrote :

Thank you for taking the time to report this bug. This particular bug has already been reported and is a duplicate of bug 529714, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.

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

Duplicates of this bug

Other bug subscribers