main window empty

Bug #487468 reported by yvan
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: empathy

when empathy is started the contact list is empty

ProblemType: Bug
Architecture: amd64
Date: Tue Nov 24 09:13:50 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
Package: empathy 2.28.1.1-0ubuntu1
ProcEnviron:
 LANGUAGE=en_AU.UTF-8
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: empathy
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
yvan (yvan-strahm) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

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?
 * Are you connected to any account? Is there any error in the debug dialog?

 This will help us to find and resolve the problem.

Changed in empathy (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
yvan (yvan-strahm) wrote : Re: [Bug 487468] Re: main window empty

Sebastien Bacher wrote:
> Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
>
> * Is this reproducible?
>
it appens rnadomly
> * If so, what specific steps should we take to recreate this bug?
>
start empathy via application launcher in the gnome panel
> * Are you connected to any account? Is there any error in the debug dialog?
>
No sure what you are talking about
>
> This will help us to find and resolve the problem.
>
> ** Changed in: empathy (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: empathy (Ubuntu)
> Status: New => Incomplete
>
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

> No sure what you are talking about

To use an im client you need to have accounts on servers, jabber, msn, yahoo, ... and to configure those in empathy, without that it's normal that you have no contact listed it's like not giving your phone number and complaining that your friends can't call you..

Revision history for this message
yvan (yvan-strahm) wrote :

Sebastien Bacher wrote:
>> No sure what you are talking about
>>
>
> To use an im client you need to have accounts on servers, jabber, msn,
> yahoo, ... and to configure those in empathy, without that it's normal
> that you have no contact listed it's like not giving your phone number
> and complaining that your friends can't call you..
>
>
Yes I have two account and both are using jabber one is gmail and the
other is used on our intranet.
Thanks for the clarification, I thought you were asking for a debugging
account!?!
Cheers
yvan

Revision history for this message
Sebastien Bacher (seb128) wrote :

ok, could you open the help menu and select debug there and select the gabble option in the debug dialog and copy the log there? be careful it might have account infos you want to replace before adding the log the bug

Revision history for this message
yvan (yvan-strahm) wrote :

Sebastien Bacher wrote:
> ok, could you open the help menu and select debug there and select the
> gabble option in the debug dialog and copy the log there? be careful it
> might have account infos you want to replace before adding the log the
> bug
>
>
Does the log could be restricted for the time with the empty contact list?
What is the time format in the Time column?
Now empathy works, so I don't now if the log will be helpful?

Revision history for this message
Sebastien Bacher (seb128) wrote :

you should look for errors in the log next time you get the issue

Revision history for this message
yvan (yvan-strahm) wrote :
Download full text (3.8 KiB)

Sebastien Bacher wrote:
> ok, could you open the help menu and select debug there and select the
> gabble option in the debug dialog and copy the log there? be careful it
> might have account infos you want to replace before adding the log the
> bug
>
>
Hello,

It happens again and when I open the debug window, only empathy appears
as an option, no gabble.
Here the log:

empathy/ImportMc4Accounts-DEBUG: 1.259565e+09:
connectivity_nm_state_change_cb: New NetworkManager network state 3
(connected: 1
empathy/Other-DEBUG: 1.259565e+09: empathy_idle_set_presence: Changing
presence to (null) (2)
empathy/Account-DEBUG: 1.259565e+09:
empathy_account_manager_request_global_presence: request global
presence, type: 2, status: available, message: (null)
empathy/Dispatcher-DEBUG: 1.259565e+09: handler_constructor: Registered
at '/org/freedesktop/Telepathy/Client/Empathy'
empathy/Dispatcher-DEBUG: 1.259565e+09: handler_constructor: Registered
at '/org/freedesktop/Telepathy/Client/EmpathyMoreThanMeetsTheEye'
empathy/Other-DEBUG: 1.259565e+09: builder_get_file_valist: Loading file
/usr/share/empathy/empathy-main-window.ui
empathy/Other-DEBUG: 1.259565e+09: presence_chooser_is_preset:
is_preset(0, (null)) = 0
empathy/Other-DEBUG: 1.259565e+09: empathy_signal_connect_weak:
connecting to 0x18878d0:account-created with context 0x1b21900
empathy/Other-DEBUG: 1.259565e+09: empathy_signal_connect_weak:
connecting to 0x18878d0:account-deleted with context 0x1acf940
empathy/Other-DEBUG: 1.259565e+09: empathy_signal_connect_weak:
connecting to 0x18878d0:account-enabled with context 0x1b21a00
empathy/Other-DEBUG: 1.259565e+09: empathy_signal_connect_weak:
connecting to 0x18878d0:account-disabled with context 0x1b218c0
empathy/Other-DEBUG: 1.259565e+09: empathy_signal_connect_weak:
connecting to 0x1a4e100:state-change with context 0x1b21a40
empathy/Contact-DEBUG: 1.259565e+09: contact_groups_file_parse:
Attempting to parse file:'/home/yvan/.config/Empathy/contact-groups.xml'...
empathy/Other-DEBUG: 1.259565e+09: empathy_xml_validate: Loading dtd
file /usr/share/empathy/empathy-contact-groups.dtd
empathy/Contact-DEBUG: 1.259565e+09: contact_groups_file_parse: Parsed 2
contact groups
empathy/Other-DEBUG: 1.259565e+09: empathy_geometry_load: Loading window
geometry: x:821, y:240, w:243, h:523
empathy/Other-DEBUG: 1.259565e+09: empathy_main_window_show: Configuring
window default size w:243, h:523
empathy/Other-DEBUG: 1.259565e+09: empathy_main_window_show: Configuring
window default position x:821, y:240
empathy/Other-DEBUG: 1.259565e+09: builder_get_file_valist: Loading file
/usr/share/empathy/empathy-status-icon.ui
empathy/Other-DEBUG: 1.259565e+09:
empathy_indicator_manager_set_server_visible: Show indicator
empathy/Account-DEBUG: 1.259565e+09: account_manager_name_owner_cb: Name
owner changed for org.freedesktop.Telepathy.AccountManager, new name:
empathy/Other-DEBUG: 1.259566e+09: unique_app_message_cb: Other instance
launched, presenting the main window. Command=-1, timestamp 1259566221
empathy/Other-DEBUG: 1.259566e+09: empathy_geometry_save: Saving window
geometry: name:main-window x:821, y:240, w:243, h:523
empathy/Other-DEBUG: 1.25956...

Read more...

Revision history for this message
Alex Mayorga (alex-mayorga) wrote :

I encountered the clean window right after adding my accounts in Lucid for the first time. Contacts load OK after I closed and reopened empathy.
I went through Help > Debug log when the contact list was empty, I only found errors under "butterfly" as below:
stderr-ERROR: 12/30/2009 08:01:59.661528: /usr/lib/python2.6/dist-packages/butterfly/handle.py:56: DeprecationWarning: object.__new__() takes no parameters
stderr-ERROR: 12/30/2009 08:01:59.661528: instance = object.__new__(cls, connection, *args)

Revision history for this message
Omer Akram (om26er) wrote :

@Alex Mayorga Adame what you faced was a know but that is now fixed.

Revision history for this message
Omer Akram (om26er) wrote :

Does this bug still exist?

Revision history for this message
yvan (yvan-strahm) wrote :

so far so good, I guess you can close the bug

Revision history for this message
Omer Akram (om26er) wrote :

marking invalid as per previous comment. I would have marked it fix released but there has been no change in the empathy version in karmic after 2.28.1.1-0ubuntu1

Changed in empathy (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Nick Demou (ndemou) wrote :

Same symptoms for me today with Empathy ver 2.30.1. It seems to happen randomly. I restarted empathy several times and at one point (a few hours later) it opened with all contacts listed.

Some details:

1) When somebody was IMing me I was getting the message.

2) Trying to send an IM by hitting ctrl-N also didn't work.

3) A funny thing for which I'm not 100% sure: I was executing empathy from the terminal (to check for possible messages) and if I remember correctly those times that it was opening with a clean list I was getting a prompt immediately after issuing the command (the empathy window was left open). Now that it opens with my contacts shown I execute it and it doesn't return (as is normal for most programs when run from the terminal).

4) if it happens again I will check the debug log (didn't know about it)

Revision history for this message
imago (imago54) wrote :
Download full text (3.4 KiB)

Same issue: empty contact list view. Empathy 2.32.0.1 Ubuntu 10.10

empathy/Dispatcher-DEBUG: 11/03/2010 18:30:54.728193: empathy_indicator_interest_status_icon: Hiding the icon, we are shown in the indicator
empathy/Other-DEBUG: 11/03/2010 18:31:01.604167: account_manager_ready_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
empathy/Other-DEBUG: 11/03/2010 18:31:01.606077: account_manager_ready_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
empathy/Dispatcher-DEBUG: 11/03/2010 18:31:01.606105: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
empathy/Other-DEBUG: 11/03/2010 18:31:01.606125: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
empathy/Other-DEBUG: 11/03/2010 18:31:01.606147: account_manager_ready_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
empathy/Other-DEBUG: 11/03/2010 18:31:01.606168: update_sensitivity_am_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
empathy/Contact-DEBUG: 11/03/2010 18:31:01.606189: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
empathy/Dispatcher-DEBUG: 11/03/2010 18:31:01.606209: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
empathy/Other-DEBUG: 11/03/2010 18:31:01.606228: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Core-WARNING: 11/03/2010 18:31:01.606441: individual-aggregator.va...

Read more...

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.