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 590640 - empathy is not working under fvwm2
empathy is not working under fvwm2
Status: RESOLVED DUPLICATE of bug 467829
Product: empathy
Classification: Core
Component: General
2.27.x
Other All
: Normal major
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2009-08-03 15:32 UTC by Arie Skliarouk
Modified: 2009-12-03 18:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Arie Skliarouk 2009-08-03 15:32:14 UTC
Please describe the problem:
I am (probably one of the last) user of venerable fvwm 2.5.26 window manager.
As such there are no gnome specific daemons running. The system does have gnome
installed, as my wife uses it.

My machine is ubuntu 9.04 32bit with following sources in sources.list:
deb http://ppa.launchpad.net/telepathy/ubuntu jaunty main

When I try to run empathy (the latests one, of version
2.27.3-2ubuntu1~ppa9.04+1), I get no windows at all. I tried to cleanup the
environment using following shell script, to no avail:

#!/bin/sh
cd
rm -rf .gstreamer-0.* /tmp/empathy.arie* /tmp/orbit* \
    /home/arie/.gnome2/Empathy /home/arie/.cache/Empathy 

killall gconfd-2
killall gconf-helper
killall mission-control
killall telepathy-gabble


Steps to reproduce:
1. Login using fvwm2 window manager
2. Make sure no gnome daemons are running:

#!/bin/sh
cd
rm -rf .gstreamer-0.* /tmp/empathy.arie* /tmp/orbit* \
    /home/arie/.gnome2/Empathy /home/arie/.cache/Empathy 

killall gconfd-2
killall gconf-helper
killall mission-control
killall telepathy-gabble

3. Start empathy


Actual results:
No windows appear.

Expected results:
To get empathy window.

Does this happen every time?
Yes.

Other information:
Here are the error messages I get from terminal when starting empathy:

(empathy:30511): GLib-GObject-WARNING **: cannot register existing type
`GstValve'

(empathy:30511): GLib-CRITICAL **: g_once_init_leave: assertion
`initialization_value != 0' failed

(empathy:30511): GStreamer-CRITICAL **: gst_element_register: assertion
`g_type_is_a (type, GST_TYPE_ELEMENT)' failed

(empathy:30511): GLib-GObject-WARNING **: cannot register existing type
`GstRTPMux'

(empathy:30511): GStreamer-CRITICAL **: gst_element_register: assertion
`g_type_is_a (type, GST_TYPE_ELEMENT)' failed

(empathy:30510): ClutterGLX-CRITICAL **: Unable to find suitable GL visual.
** (empathy:30510): DEBUG: mission_control_get_presence_actual: MC not running.
** (empathy:30510): DEBUG: mission_control_get_presence_message_actual: MC not
running.
** (empathy:30510): DEBUG: _parse_parameter: param "fallback-socks5-proxies"
has invalid signature
** (empathy:30510): DEBUG: mission_control_get_presence_actual: MC not running.
** (empathy:30510): DEBUG: mission_control_get_connection_status: MC not
running.
** (empathy:30510): DEBUG: mission_control_get_connection_status: MC not
running.
** (empathy:30510): DEBUG: mission_control_get_tpconnection: MC not running.
** (empathy:30510): DEBUG: mission_control_get_presence_actual: MC not running.
** (empathy:30510): DEBUG: mission_control_get_connection_status: MC not
running.
** (empathy:30510): DEBUG: mission_control_get_connection_status: MC not
running.
** (empathy:30510): DEBUG: mission_control_get_tpconnection: MC not running.
Comment 1 Xavier Claessens 2009-08-03 17:08:04 UTC
Does your desktop have a notification area to show GtkStatusIcon? You'll have problems if it doesn't.
Comment 2 Arie Skliarouk 2009-08-03 18:15:02 UTC
fvwm2 is not a desktop, it is window manager. As such it does not have any notification area at all.

Can't empathy work without notification area?
Comment 3 Guillaume Desmottes 2009-12-03 18:08:02 UTC
Unfortunatelly not : bug #467829

Closing this bug as a dup of this one as Empathy is basically unusable atm without status icon.

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