Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#2092 - gnomemeeting doesn't work

Attached to Project: Arch Linux
Opened by Dale Blount (dale) - Friday, 28 January 2005, 13:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jason Chu (jason)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

It appears that you do not have gnomemeeting.server installed in a valid location. Factory mode disabled.
[assert] error: 111 (Connection refused)
[assert] where: "socket.c", "sw_socket_tcp_connect", line: 720

[assert] error: 111 (Connection refused)
[assert] where: "socket.c", "sw_socket_tcp_connect", line: 720


plus there's errors thrown in a GUI window about gconf.
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 03 March 2005, 22:11 GMT
Reason for closing:  Fixed
Comment by Jason Chu (jason) - Friday, 28 January 2005, 14:43 GMT
Try running 'gnomemeeting-config-tool --fix-permissions' as root.
Comment by Dale Blount (dale) - Friday, 28 January 2005, 15:41 GMT
yup.. fixed it... shouldn't the install file do that?
Comment by Jason Chu (jason) - Friday, 28 January 2005, 15:53 GMT
It doesn't always have to. That script is only for fixing permissions, the actual installing of schemas already happens.

If you have to run --fix-permissions, something was wrong on your system side ;)
Comment by Dale Blount (dale) - Friday, 28 January 2005, 16:04 GMT
This was a fresh gnomemeeting install, I just got the camera hooked up today.

Are you saying my global conf is broke then?
Comment by Jason Chu (jason) - Friday, 28 January 2005, 16:42 GMT
http://www.gnomemeeting.org/index.php?rub=3&pos=0&faqpage=x304.html#AEN380

This is what --fix-permissions does. It looks more like bad gconf permissions that are manifesting themselves in gnomemeeting.

I don't pretend to know how gconf/gnome work. I just know how to fix most of the problems I run into.
Comment by Dale Blount (dale) - Friday, 28 January 2005, 16:49 GMT
That page also says gconftool-2 --get "/apps/gnomemeeting/general/gconf_test_age" should return 0... which it doesn't, even after gnomemeeting-config-tool --fix-permissions is ran.
Comment by Jason Chu (jason) - Friday, 28 January 2005, 18:01 GMT
'That key is "/apps/gnomemeeting/general/gconf_test_age", and gconftool-2 --get "/apps/gnomemeeting/general/gconf_test_age" should always return a value different of 0.'

'Different of 0'. I think he means 'other than 0'.
Comment by Dale Blount (dale) - Friday, 28 January 2005, 18:23 GMT
yup, wording through me off..
Comment by Dale Blount (dale) - Friday, 28 January 2005, 18:25 GMT
err, threw :)
Comment by Dale Blount (dale) - Friday, 28 January 2005, 18:41 GMT
also: from the person trying to gnome-meet with me...

gnomemeeting: error while loading shared libraries: libdbus-glib-1.so.0: cannot open shared object file: No such file or directory

dbus is missing from depends i guess.
Comment by Jan de Groot (JGC) - Thursday, 03 March 2005, 22:11 GMT
Some explanations:
- the --disable-dbus enables dbus and has a hard dependency on dbus 0.22, so it broke after I upgraded dbus to 0.23.2.
- The connection refused thing is from howl. gnomemeeting tries to use zeroconf, but when howl is not running, both publishing and retrieving via zeroconf isn't possible and throws 2 error messages.

Leaving the --disable-dbus out will fix the problem, since our dbus is not compatible with gnomemeeting and thus not detected. dbus is considered unstable by the authors of gnomemeeting too.

Fixed packages are uploaded to extra and testing.

Loading...