Now OK (Re: cvs commit: ports/net/linuxigd Makefile ports/net/linuxigd/files patch-gatedevice.c patch-main.c patch-pmlist.c)
net/linuxigd, which was previously failing is OK after this commit. Thanks for fixing it! A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- QAT - your friendly neighborhood Daemon, preparing a heck of an error trapping system: - "HMC and EOI?" - "Halt, Melt and Catch fire or Execute Operator Immediately." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
gconf error
I got this error with the last version of gnome, and the current one: seahorse-agent[88595]: GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Error connecting: Connection refused) Any suggestions? Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gconf error
On 11/26/10 7:07 PM, Doug Barton wrote: > I got this error with the last version of gnome, and the current one: > > seahorse-agent[88595]: GConf error: Failed to contact configuration > server; some possible causes are that you need to enable TCP/IP > networking for ORBit, or you have stale NFS locks due to a system crash. > See http://projects.gnome.org/gconf/ for information. (Details - 1: > Failed to get connection to session: Error connecting: Connection refused) > > Any suggestions? When do you see this? This message typically occurs when logging out of GNOME, and does not cause any functionality loss. If you see this when starting X, make sure you start your session with dbus-launch. If you use gnome-session, you do not need to use dbus-launch as that is done automatically. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gconf error
On 11/26/2010 16:29, Joe Marcus Clarke wrote: On 11/26/10 7:07 PM, Doug Barton wrote: I got this error with the last version of gnome, and the current one: seahorse-agent[88595]: GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Error connecting: Connection refused) Any suggestions? When do you see this? This message typically occurs when logging out of GNOME, and does not cause any functionality loss. Ok, I'll pay more attention to when it happens, thanks. If you see this when starting X, make sure you start your session with dbus-launch. If you use gnome-session, you do not need to use dbus-launch as that is done automatically. I'm doing straight up gnome using gdm, with gnome_enable=yes and dbus_enable=yes. Hopefully that should cover it? Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gconf error
On 11/26/10 8:01 PM, Doug Barton wrote: > On 11/26/2010 16:29, Joe Marcus Clarke wrote: >> On 11/26/10 7:07 PM, Doug Barton wrote: >>> I got this error with the last version of gnome, and the current one: >>> >>> seahorse-agent[88595]: GConf error: Failed to contact configuration >>> server; some possible causes are that you need to enable TCP/IP >>> networking for ORBit, or you have stale NFS locks due to a system crash. >>> See http://projects.gnome.org/gconf/ for information. (Details - 1: >>> Failed to get connection to session: Error connecting: Connection >>> refused) >>> >>> Any suggestions? >> >> When do you see this? This message typically occurs when logging out of >> GNOME, and does not cause any functionality loss. > > Ok, I'll pay more attention to when it happens, thanks. > >> If you see this when >> starting X, make sure you start your session with dbus-launch. If you >> use gnome-session, you do not need to use dbus-launch as that is done >> automatically. > > I'm doing straight up gnome using gdm, with gnome_enable=yes and > dbus_enable=yes. Hopefully that should cover it? Yes. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
