gwibber crashed with SIGSEGV in g_str_hash()

Bug #919704 reported by Craig Magina on 2012-01-21
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Ken VanDine
gwibber (Ubuntu)

Bug Description

This occured when I added a facebook account right after successfully adding a twitter account.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gwibber 3.3.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Jan 20 16:57:04 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120117)
ProcCmdline: gwibber
 Segfault happened at: 0x7fbb763ed200 <g_str_hash>: movzbl (%rdi),%edx
 PC (0x7fbb763ed200) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gwibber
 g_str_hash () from /lib/x86_64-linux-gnu/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/
Title: gwibber crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Craig Magina (craig.magina) wrote :
visibility: private → public

 g_str_hash (v=0x0) at /build/buildd/glib2.0-2.31.10/./glib/ghash.c:1709
 gee_hash_map_lookup_node (self=0x1da8be0, key=0x0) at hashmap.c:928
 gee_hash_map_real_has_key (base=<optimized out>, key=<optimized out>) at hashmap.c:967
 gwibber_gtk_account_target_bar_account_created (account=0x1daa530, accounts_buttons_map=0x1da8be0, self=0x1e28050) at /home/ken/src/gwibber/trunk/libgwibber-gtk/entry.vala:451
 _gwibber_gtk_account_target_bar___lambda10_ (source=0x1daa530, self=0x1e28050) at /home/ken/src/gwibber/trunk/libgwibber-gtk/entry.vala:377

Changed in gwibber (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gwibber (Ubuntu):
status: New → Confirmed
Bilal Shahid (s9iper1) on 2012-02-10
Changed in gwibber:
importance: Undecided → Medium
Bilal Shahid (s9iper1) wrote :

thanks for the bug report.. assigning to kenvandine as we have talked about it.

Changed in gwibber (Ubuntu):
status: Confirmed → Triaged
Changed in gwibber:
assignee: nobody → Ken VanDine (ken-vandine)
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