Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the 
problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

** Changed in: gwibber (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/1153165

Title:
  gwibber-service crashed with SIGSEGV in g_type_check_instance_is_a()

Status in “gwibber” package in Ubuntu:
  Incomplete

Bug description:
  I don't know, why this crash occurred, but everything working normally. I 
didn't opened/tried to open gwibber in this instance.
  Opened tools in this instance: Home Folder, Chromium [with 3 profiles], 
gedit, virtualbox [windows 7]...

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gwibber-service 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic i686
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Sun Mar 10 13:09:03 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gwibber-service
  InstallationDate: Installed on 2012-03-30 (344 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
  SegvAnalysis:
   Segfault happened at: 0xb72051f7 <g_type_check_instance_is_a+87>:    testb  
$0x4,0xe(%ecx)
   PC (0xb72051f7) ok
   source "$0x4" ok
   destination "0xe(%ecx)" (0x006e6576) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gwibber
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libsignon-glib.so.1
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gwibber-service crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to raring on 2013-01-16 (52 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare 
vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/1153165/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to