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 662518 - You can not start a conversation from the shell with Empathy
You can not start a conversation from the shell with Empathy
Status: RESOLVED DUPLICATE of bug 657715
Product: empathy
Classification: Core
Component: Chat
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-23 12:33 UTC by Bastián Díaz
Modified: 2011-10-25 07:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastián Díaz 2011-10-23 12:33:43 UTC
There is no convenient way to start a conversation from the shell. To do this you must open a conversation from the application, but when it closes, also closes the conversation bubble shell.

It would be a good idea to integrate a contextual menu button on the contacts that could start a conversation from the shell.
Comment 1 Guillaume Desmottes 2011-10-24 09:29:23 UTC
Since GNOME 3.2 you can search for a contact using the Shell overview and then start a conversation from Contact. Does it work for you?
Comment 2 Bastián Díaz 2011-10-24 20:24:02 UTC
If I work, but it is even more complicated due to the search for a contact in the shell overview, run gnome-contacts and from the need to open a conversation (which opens both the shell as in empathy) that mentioned the same thing happening before.

(In reply to comment #1)
> Since GNOME 3.2 you can search for a contact using the Shell overview and then
> start a conversation from Contact. Does it work for you?
Comment 3 Guillaume Desmottes 2011-10-25 07:40:21 UTC
Searching contacts through the overview is the way to go. You can still use Empathy if you prefer of course.

Closing as a dup of bug #657715 as it's about making the process more straightforward.

*** This bug has been marked as a duplicate of bug 657715 ***