After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 662874 - Unable to access Accounts preferences
Unable to access Accounts preferences
Status: RESOLVED OBSOLETE
Product: empathy
Classification: Core
Component: Accounts
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-27 18:19 UTC by Bilal Shahid
Modified: 2011-12-15 09:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bilal Shahid 2011-10-27 18:19:17 UTC
Originally reported at:
  https://bugs.launchpad.net/bugs/881978

Quite often I'm unable to access the Accounts preferences. If I click on "Edit - Accounts" no window will show up, nor do I get an error.

The file ~/.xsession-errors will contain the following errors for each attempt:

GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkWindow'
Gtk-CRITICAL **: gtk_window_present_with_time: assertion `GTK_IS_WINDOW (window)' failed

I can't reproduce it 100%, but it usually starts to occur when a connection error occurred for one of the accounts and this has been reported in the contact list accordingly.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: empathy 3.2.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Wed Oct 26 14:08:14 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
SourcePackage: empathy
UpgradeStatus: No upgrade log present (probably fresh install)
Comment 1 Guillaume Desmottes 2011-10-28 08:00:20 UTC
when you experience this issue could you please:
- Install empathy-dbg
- Open a terminal
- export G_DEBUG=fatal-warnings
- gdb /usr/bin/empathy-accounts
- Once it crash type 'thread apply all bt' to get a trace and attach it to this bug.
Comment 2 Age Bosma (IRC: Forage) 2011-10-28 17:21:36 UTC
I tried to perform your steps but I get no results.

Steps performed:
- Installed empathy-dbg
- Launch Empathy as the first action after logging in
- Open a terminal
- export G_DEBUG=fatal-warnings
- gdb /usr/bin/empathy-accounts (giving me a "(gdb)" prompt after some "Reading symbols" messages)
- Reproduced to issue by opening the accounts, closing it, and opening it again
- Executed "thread apply all bt" in the "(gdb)" prompt

The only thing happening is that I get a new line "(gdb)" prompt without any messages.
The ~/.xsession-errors file contains identical errors as mentioned in the initial post.

Am I doing something wrong or is the actual trace stored elsewhere?
Comment 3 Guillaume Desmottes 2011-11-02 08:36:57 UTC
Oh sorry, once you have loaded the app in gdb you have to type 'r' to start running it...
Comment 4 Guillaume Desmottes 2011-11-02 11:51:24 UTC
Your bug could be a side effect of bug #662504 let's see how it goes once you have an updated version.
Comment 5 Age Bosma (IRC: Forage) 2011-12-15 00:26:41 UTC
I finally took the liberty to put up Empathy 3.2.2 in a PPA instead of waiting for Ubuntu to apply to fix or update their release to 3.2.2.

I can confirm that the issue is resolved.
Comment 6 Guillaume Desmottes 2011-12-15 09:28:46 UTC
Cool, thanks for testing.