run at the second attempt and does not connect to msn

[asmanao]

Binary package hint: empathy

ubuntu 9.10 rc

ProblemType: Bug
Architecture: i386
CheckboxSubmission: 1e66e7ed8d51b265a5181746d0a0349d
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Thu Oct 29 23:12:23 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
Package: empathy 2.28.1-1ubuntu1
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.152-rt
SourcePackage: empathy
Uname: Linux 2.6.31-9-rt i686
XsessionErrors:
 (gnome-settings-daemon:2316): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2316): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-panel:2420): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
 (polkit-gnome-authentication-agent-1:2469): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2436): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

[asmanao (asmanao)]

I tried to run it from terminal and gives the following error : (empathy:3366): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'

(empathy:3366): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

[Sebastien Bacher (seb128)]

The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[Omer Akram (om26er)]

@asmanao Do you still face this? I tried this in lucid (empathy 2.29.5) and was not able to reproduce.

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!