Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Wed, 22 Apr 2009 10:22:41 +0400 (MSD), Dmitry Morozovsky wrote: > On Wed, 22 Apr 2009, Alexander Nedotsukov wrote: > > AN> > Well, then I suppose we should at least say something about this in release > AN> > notes, because in 7.2 one of *major* desktop application sets conflicts with > AN> > one of the *widest* server component. > AN> > AN> What do you propose to write in the release notes which could help Apache > AN> 1.3+ lovers? > > Something like > > Full GNOME 2.26 installation is incompatible with Apache HTTP Server 1.3 > due to user-share GNOME component dependency on apache22. To resolve the issue, > either install gnome2-lite package or upgrade apache13 to apache22. This seems to be almost obvious to me. But surely can be stressed out. Am I right to assume we are talking about entry in ports/UPDATING? > > > AN> And may I in turn quote a bit of another release notes: > AN> > AN> http://www.apache.org/dist/httpd/Announcement1.3.html > AN> > AN> "We strongly recommend that users of all earlier versions, including 1.3 > AN> family release, upgrade to to the current 2.2 version as soon as possible." > AN> > AN> :-^) > > Please note that this recommendation is not located on HTTP server home page, > and 1.3 releases are still listed there, and not marked as "legacy" http://httpd.apache.org/ "The Apache Group is pleased to announce the *legacy* release of the 1.3.41 version of the Apache HTTP Server." > > Also, there are still rather wide set of httpd modules which are written for > 1.3 only :( ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Wed, 22 Apr 2009, Alexander Nedotsukov wrote: AN> > Well, then I suppose we should at least say something about this in AN> release AN> > notes, because in 7.2 one of *major* desktop application sets conflicts AN> with AN> > one of the *widest* server component. AN> AN> What do you propose to write in the release notes which could help Apache AN> 1.3+ lovers? Something like Full GNOME 2.26 installation is incompatible with Apache HTTP Server 1.3 due to user-share GNOME component dependency on apache22. To resolve the issue, either install gnome2-lite package or upgrade apache13 to apache22. AN> And may I in turn quote a bit of another release notes: AN> AN> http://www.apache.org/dist/httpd/Announcement1.3.html AN> AN> "We strongly recommend that users of all earlier versions, including 1.3 AN> family release, upgrade to to the current 2.2 version as soon as possible." AN> AN> :-^) Please note that this recommendation is not located on HTTP server home page, and 1.3 releases are still listed there, and not marked as "legacy" Also, there are still rather wide set of httpd modules which are written for 1.3 only :( -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 21 Apr 2009 16:19:30 +0400 (MSD), Dmitry Morozovsky wrote: > JMC> Actually, I have always shied away from such things. We regularly get > JMC> requests to change the meta-port, but we long ago took the philosophy to > JMC> keep the Desktop meta-port as close to the official set of GNOME Desktop > JMC> components as possible. If we add an option for this, then we slide > JMC> down the slope of making everything optional. > JMC> > JMC> In the past I've simply prompted people to create their own local > JMC> meta-ports, or install x11/gnome2-lite (no user-share there), then build > JMC> on that for what they need. > > Well, then I suppose we should at least say something about this in release > notes, because in 7.2 one of *major* desktop application sets conflicts with > one of the *widest* server component. What do you propose to write in the release notes which could help Apache 1.3+ lovers? And may I in turn quote a bit of another release notes: http://www.apache.org/dist/httpd/Announcement1.3.html "We strongly recommend that users of all earlier versions, including 1.3 family release, upgrade to to the current 2.2 version as soon as possible." :-^) ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Sun, 19 Apr 2009, Joe Marcus Clarke wrote: JMC> > JMC> > Hmm, so currently there is no way to install gnome2 without requiring apache22? JMC> > JMC> JMC> > JMC> Correct. You could, of course, go through the meta-port, and remove JMC> > JMC> gnome-user-share on your own (i.e. build your own customized meta-port). JMC> > JMC> > Well, would you object to the following quick fix? JMC> JMC> Actually, I have always shied away from such things. We regularly get JMC> requests to change the meta-port, but we long ago took the philosophy to JMC> keep the Desktop meta-port as close to the official set of GNOME Desktop JMC> components as possible. If we add an option for this, then we slide JMC> down the slope of making everything optional. JMC> JMC> In the past I've simply prompted people to create their own local JMC> meta-ports, or install x11/gnome2-lite (no user-share there), then build JMC> on that for what they need. Well, then I suppose we should at least say something about this in release notes, because in 7.2 one of *major* desktop application sets conflicts with one of the *widest* server component. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 21:05 +0400, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Robert Noland wrote: > > [snip all] > > RN> > Yes, seahorse shows me two keyrings; however, deleting "login" one does > not fix > RN> > the situation: if in the Terminal I try to open tab which ssh's to > outer host, > RN> > I immediately got the popup with > RN> > > RN> > "There was an error creating the child process for this terminal" > RN> > > RN> > nothing in this tab is started, and tab is just hanging. > RN> > > RN> > "login" keyring sometimes got recreated, sometimes not, but the effect > above is > RN> > totally reproducible. > RN> > RN> If I am following this correctly, the functionality you are talking > RN> about is actually provided by seahorse-agent, which is installed with > RN> the seahorse-plugins port now. Unless something has changed with the > RN> default session (and I don't think it has, since my keyrings still work) > RN> we wrap the session with ssh-agent and seahorse-agent if they are found. > > Aha! Yes, and seahorse-plugins was not installed; moreover, one of its > dependencies (pth) conflicted with pth-hard installed previously. I'll try to > clean this up and report the results. I just discovered two serious bugs in seahorse and gnome-keyring that may be messing you up. I have committed fixes to the ports-stable module in MarcusCom CVS pending the ports thaw. You can access the report using the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi . Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Sat, 2009-04-18 at 13:47 +0400, Dmitry Morozovsky wrote:
> On Tue, 14 Apr 2009, Joe Marcus Clarke wrote:
>
> JMC> > JMC> > Another question: is there a way to avoid apache22 install (i
> have apache13
> JMC> > JMC> > installed and have no current plans to upgrade) ? I tried to
> chase
> JMC> > JMC> > options but failed.
> JMC> > JMC>
> JMC> > JMC> Not by using the meta-port. This is required for
> gnome-user-share which
> JMC> > JMC> is now part of the GNOME Desktop.
> JMC> >
> JMC> > Hmm, so currently there is no way to install gnome2 without requiring
> apache22?
> JMC>
> JMC> Correct. You could, of course, go through the meta-port, and remove
> JMC> gnome-user-share on your own (i.e. build your own customized meta-port).
>
> Well, would you object to the following quick fix?
Actually, I have always shied away from such things. We regularly get
requests to change the meta-port, but we long ago took the philosophy to
keep the Desktop meta-port as close to the official set of GNOME Desktop
components as possible. If we add an option for this, then we slide
down the slope of making everything optional.
In the past I've simply prompted people to create their own local
meta-ports, or install x11/gnome2-lite (no user-share there), then build
on that for what they need.
Joe
>
> Index: x11/gnome2/Makefile
> ===
> RCS file: /home/ncvs/ports/x11/gnome2/Makefile,v
> retrieving revision 1.154
> diff -u -r1.154 Makefile
> --- x11/gnome2/Makefile 10 Apr 2009 05:56:18 - 1.154
> +++ x11/gnome2/Makefile 18 Apr 2009 09:26:50 -
> @@ -68,7 +68,8 @@
> .endif
>
> .if !defined(GNOME_SLAVE) || ${.CURDIR:T}=="gnome2-lite"
> -OPTIONS= XSCREENSAVER "Use xscreensaver as screen saver app" off
> +OPTIONS= XSCREENSAVER "Use xscreensaver as screen saver app" off \
> + USER_SHARE "Use gnome-user-share for file sharing" on
> .endif
>
> do-install:# empty
> @@ -90,9 +91,11 @@
> swfdec-player:${PORTSDIR}/multimedia/swfdec-gnome \
> vinagre:${PORTSDIR}/net/vinagre \
> brasero:${PORTSDIR}/sysutils/brasero \
> - gnome-file-share-properties:${PORTSDIR}/www/gnome-user-share \
>
> ${LOCALBASE}/lib/deskbar-applet/deskbar-applet:${PORTSDIR}/deskutils/deskbar-applet
>
> \
>
> ${LOCALBASE}/lib/hamster-applet/hamster-applet:${PORTSDIR}/deskutils/hamster-applet
> +.if !defined(WITHOUT_USER_SHARE)
> +RUN_DEPENDS+= gnome-file-share-properties:${PORTSDIR}/www/gnome-user-share
> +.endif
> .if ${ARCH} == "i386"
> #RUN_DEPENDS+= tomboy:${PORTSDIR}/deskutils/tomboy
> .endif
>
>
--
Joe Marcus Clarke
FreeBSD GNOME Team :: gn...@freebsd.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
signature.asc
Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Sat, 18 Apr 2009 10:38:35 -0500, Jeremy Messenger wrote: On Sat, 18 Apr 2009 10:15:59 -0500, Dmitry Morozovsky wrote: On Sat, 18 Apr 2009, Jeremy Messenger wrote: JM> > JMC> > JMC> > Another question: is there a way to avoid apache22 install JM> > (i have apache13 JM> > JMC> > JMC> > installed and have no current plans to upgrade) ? I tried to JM> > chase JM> > JMC> > JMC> > options but failed. JM> > JMC> > JMC> JM> > JMC> > JMC> Not by using the meta-port. This is required for JM> > gnome-user-share which JM> > JMC> > JMC> is now part of the GNOME Desktop. JM> > JMC> > JM> > JMC> > Hmm, so currently there is no way to install gnome2 without JM> > requiring apache22? JM> > JMC> JM> > JMC> Correct. You could, of course, go through the meta-port, and remove JM> > JMC> gnome-user-share on your own (i.e. build your own customized JM> > meta-port). JM> > JM> > Well, would you object to the following quick fix? JM> JM> Wel.. I object. marcus also said that you only can do in your own system, so JM> it means we don't want to add any option in x11/gnome2. We always turn down JM> that kind of patch unless no choice for limit size to build packages in CD JM> for the release. I hope I understand your intentions, but this is not the first options for the metaport, heh? ;-) My main concern is that many my colleagues work on desktop systems which they are using as sorta "personal websevers" too, not too resource hungry, hence apache 1.3. From the last upgrade the only way to achieve it on a single machine is to split Gnome and apache to separate jails... I didn't exactly read previous thread, but you do have a good point. I am surpised about that gnome-user-share doesn't use gvfs. Isn't gvfs supposed to be already support WebDAV (gvfs-dav)? Nevermind about that gvfs part. Clearly wake up and type email is a bad idea. Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Sat, 18 Apr 2009 10:15:59 -0500, Dmitry Morozovsky wrote: On Sat, 18 Apr 2009, Jeremy Messenger wrote: JM> > JMC> > JMC> > Another question: is there a way to avoid apache22 install JM> > (i have apache13 JM> > JMC> > JMC> > installed and have no current plans to upgrade) ? I tried to JM> > chase JM> > JMC> > JMC> > options but failed. JM> > JMC> > JMC> JM> > JMC> > JMC> Not by using the meta-port. This is required for JM> > gnome-user-share which JM> > JMC> > JMC> is now part of the GNOME Desktop. JM> > JMC> > JM> > JMC> > Hmm, so currently there is no way to install gnome2 without JM> > requiring apache22? JM> > JMC> JM> > JMC> Correct. You could, of course, go through the meta-port, and remove JM> > JMC> gnome-user-share on your own (i.e. build your own customized JM> > meta-port). JM> > JM> > Well, would you object to the following quick fix? JM> JM> Wel.. I object. marcus also said that you only can do in your own system, so JM> it means we don't want to add any option in x11/gnome2. We always turn down JM> that kind of patch unless no choice for limit size to build packages in CD JM> for the release. I hope I understand your intentions, but this is not the first options for the metaport, heh? ;-) My main concern is that many my colleagues work on desktop systems which they are using as sorta "personal websevers" too, not too resource hungry, hence apache 1.3. From the last upgrade the only way to achieve it on a single machine is to split Gnome and apache to separate jails... I didn't exactly read previous thread, but you do have a good point. I am surpised about that gnome-user-share doesn't use gvfs. Isn't gvfs supposed to be already support WebDAV (gvfs-dav)? Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Sat, 18 Apr 2009, Jeremy Messenger wrote: JM> > JMC> > JMC> > Another question: is there a way to avoid apache22 install JM> > (i have apache13 JM> > JMC> > JMC> > installed and have no current plans to upgrade) ? I tried to JM> > chase JM> > JMC> > JMC> > options but failed. JM> > JMC> > JMC> JM> > JMC> > JMC> Not by using the meta-port. This is required for JM> > gnome-user-share which JM> > JMC> > JMC> is now part of the GNOME Desktop. JM> > JMC> > JM> > JMC> > Hmm, so currently there is no way to install gnome2 without JM> > requiring apache22? JM> > JMC> JM> > JMC> Correct. You could, of course, go through the meta-port, and remove JM> > JMC> gnome-user-share on your own (i.e. build your own customized JM> > meta-port). JM> > JM> > Well, would you object to the following quick fix? JM> JM> Wel.. I object. marcus also said that you only can do in your own system, so JM> it means we don't want to add any option in x11/gnome2. We always turn down JM> that kind of patch unless no choice for limit size to build packages in CD JM> for the release. I hope I understand your intentions, but this is not the first options for the metaport, heh? ;-) My main concern is that many my colleagues work on desktop systems which they are using as sorta "personal websevers" too, not too resource hungry, hence apache 1.3. From the last upgrade the only way to achieve it on a single machine is to split Gnome and apache to separate jails... -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Sat, 18 Apr 2009 04:47:33 -0500, Dmitry Morozovsky
wrote:
On Tue, 14 Apr 2009, Joe Marcus Clarke wrote:
JMC> > JMC> > Another question: is there a way to avoid apache22 install
(i have apache13
JMC> > JMC> > installed and have no current plans to upgrade) ? I tried
to chase
JMC> > JMC> > options but failed.
JMC> > JMC>
JMC> > JMC> Not by using the meta-port. This is required for
gnome-user-share which
JMC> > JMC> is now part of the GNOME Desktop.
JMC> >
JMC> > Hmm, so currently there is no way to install gnome2 without
requiring apache22?
JMC>
JMC> Correct. You could, of course, go through the meta-port, and remove
JMC> gnome-user-share on your own (i.e. build your own customized
meta-port).
Well, would you object to the following quick fix?
Wel.. I object. marcus also said that you only can do in your own system,
so it means we don't want to add any option in x11/gnome2. We always turn
down that kind of patch unless no choice for limit size to build packages
in CD for the release.
Cheers,
Mezz
Index: x11/gnome2/Makefile
===
RCS file: /home/ncvs/ports/x11/gnome2/Makefile,v
retrieving revision 1.154
diff -u -r1.154 Makefile
--- x11/gnome2/Makefile 10 Apr 2009 05:56:18 - 1.154
+++ x11/gnome2/Makefile 18 Apr 2009 09:26:50 -
@@ -68,7 +68,8 @@
.endif
.if !defined(GNOME_SLAVE) || ${.CURDIR:T}=="gnome2-lite"
-OPTIONS= XSCREENSAVER "Use xscreensaver as screen saver app" off
+OPTIONS= XSCREENSAVER "Use xscreensaver as screen saver app" off \
+ USER_SHARE "Use gnome-user-share for file sharing" on
.endif
do-install:# empty
@@ -90,9 +91,11 @@
swfdec-player:${PORTSDIR}/multimedia/swfdec-gnome \
vinagre:${PORTSDIR}/net/vinagre \
brasero:${PORTSDIR}/sysutils/brasero \
-
gnome-file-share-properties:${PORTSDIR}/www/gnome-user-share \
${LOCALBASE}/lib/deskbar-applet/deskbar-applet:${PORTSDIR}/deskutils/deskbar-applet
\
${LOCALBASE}/lib/hamster-applet/hamster-applet:${PORTSDIR}/deskutils/hamster-applet
+.if !defined(WITHOUT_USER_SHARE)
+RUN_DEPENDS+=
gnome-file-share-properties:${PORTSDIR}/www/gnome-user-share
+.endif
.if ${ARCH} == "i386"
#RUN_DEPENDS+= tomboy:${PORTSDIR}/deskutils/tomboy
.endif
--
me...@cox.net - m...@freebsd.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gn...@freebsd.org
___
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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Joe Marcus Clarke wrote:
JMC> > JMC> > Another question: is there a way to avoid apache22 install (i
have apache13
JMC> > JMC> > installed and have no current plans to upgrade) ? I tried to
chase
JMC> > JMC> > options but failed.
JMC> > JMC>
JMC> > JMC> Not by using the meta-port. This is required for gnome-user-share
which
JMC> > JMC> is now part of the GNOME Desktop.
JMC> >
JMC> > Hmm, so currently there is no way to install gnome2 without requiring
apache22?
JMC>
JMC> Correct. You could, of course, go through the meta-port, and remove
JMC> gnome-user-share on your own (i.e. build your own customized meta-port).
Well, would you object to the following quick fix?
Index: x11/gnome2/Makefile
===
RCS file: /home/ncvs/ports/x11/gnome2/Makefile,v
retrieving revision 1.154
diff -u -r1.154 Makefile
--- x11/gnome2/Makefile 10 Apr 2009 05:56:18 - 1.154
+++ x11/gnome2/Makefile 18 Apr 2009 09:26:50 -
@@ -68,7 +68,8 @@
.endif
.if !defined(GNOME_SLAVE) || ${.CURDIR:T}=="gnome2-lite"
-OPTIONS= XSCREENSAVER "Use xscreensaver as screen saver app" off
+OPTIONS= XSCREENSAVER "Use xscreensaver as screen saver app" off \
+ USER_SHARE "Use gnome-user-share for file sharing" on
.endif
do-install:# empty
@@ -90,9 +91,11 @@
swfdec-player:${PORTSDIR}/multimedia/swfdec-gnome \
vinagre:${PORTSDIR}/net/vinagre \
brasero:${PORTSDIR}/sysutils/brasero \
- gnome-file-share-properties:${PORTSDIR}/www/gnome-user-share \
${LOCALBASE}/lib/deskbar-applet/deskbar-applet:${PORTSDIR}/deskutils/deskbar-applet
\
${LOCALBASE}/lib/hamster-applet/hamster-applet:${PORTSDIR}/deskutils/hamster-applet
+.if !defined(WITHOUT_USER_SHARE)
+RUN_DEPENDS+= gnome-file-share-properties:${PORTSDIR}/www/gnome-user-share
+.endif
.if ${ARCH} == "i386"
#RUN_DEPENDS+= tomboy:${PORTSDIR}/deskutils/tomboy
.endif
--
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: ma...@freebsd.org ]
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru ***
___
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: HEADS UP: GNOME 2.26 available for FreeBSD
On Sat, 18 Apr 2009, Dmitry Morozovsky wrote: DM> SW> > Yes, seahorse shows me two keyrings; however, deleting "login" one does not fix DM> SW> > the situation: if in the Terminal I try to open tab which ssh's to outer host, DM> SW> > I immediately got the popup with DM> SW> > DM> SW> > "There was an error creating the child process for this terminal" DM> SW> > DM> SW> > nothing in this tab is started, and tab is just hanging. DM> SW> DM> SW> I believe this problem is fixed in gnome-keyring 2.26.1. FWIW, the GNOME DM> SW> SSH agent is part if gnome-keyring. DM> DM> Hmm, I just did portupgrade -f gnome-keyring gnome-terminal, and ensured there DM> is no additional keyrings. Still, gnome terminal can't start any tab which DM> executes ssh :( Well, the devil finally found somewhere in the settings: I just created new user from scratch, relogin into this account, and key-based ssh sessions in the Terminal work. So, I'll clean up my dot directories and try to start a bit over ;-) Thanks all. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Wed, 15 Apr 2009, Stef Walter wrote: SW> Dmitry Morozovsky wrote: SW> > Yes, seahorse shows me two keyrings; however, deleting "login" one does not fix SW> > the situation: if in the Terminal I try to open tab which ssh's to outer host, SW> > I immediately got the popup with SW> > SW> > "There was an error creating the child process for this terminal" SW> > SW> > nothing in this tab is started, and tab is just hanging. SW> SW> I believe this problem is fixed in gnome-keyring 2.26.1. FWIW, the GNOME SW> SSH agent is part if gnome-keyring. Hmm, I just did portupgrade -f gnome-keyring gnome-terminal, and ensured there is no additional keyrings. Still, gnome terminal can't start any tab which executes ssh :( -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
Dmitry Morozovsky wrote: > Yes, seahorse shows me two keyrings; however, deleting "login" one does not > fix > the situation: if in the Terminal I try to open tab which ssh's to outer > host, > I immediately got the popup with > > "There was an error creating the child process for this terminal" > > nothing in this tab is started, and tab is just hanging. I believe this problem is fixed in gnome-keyring 2.26.1. FWIW, the GNOME SSH agent is part if gnome-keyring. Cheers, Stef ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 23:22 +0400, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: > > JMC> > JMC> I had assumed you had x11/gnome2 installed which includes > JMC> > JMC> seahorse-plugins. I find people that expect to be using > seahorse-agent > JMC> > JMC> are using the entire GNOME Desktop. > JMC> > > JMC> > Another question: is there a way to avoid apache22 install (i have > apache13 > JMC> > installed and have no current plans to upgrade) ? I tried to chase > JMC> > options but failed. > JMC> > JMC> Not by using the meta-port. This is required for gnome-user-share which > JMC> is now part of the GNOME Desktop. > > Hmm, so currently there is no way to install gnome2 without requiring > apache22? Correct. You could, of course, go through the meta-port, and remove gnome-user-share on your own (i.e. build your own customized meta-port). Joe > -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: JMC> > JMC> I had assumed you had x11/gnome2 installed which includes JMC> > JMC> seahorse-plugins. I find people that expect to be using seahorse-agent JMC> > JMC> are using the entire GNOME Desktop. JMC> > JMC> > Another question: is there a way to avoid apache22 install (i have apache13 JMC> > installed and have no current plans to upgrade) ? I tried to chase JMC> > options but failed. JMC> JMC> Not by using the meta-port. This is required for gnome-user-share which JMC> is now part of the GNOME Desktop. Hmm, so currently there is no way to install gnome2 without requiring apache22? -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 22:20 +0400, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: > > JMC> I had assumed you had x11/gnome2 installed which includes > JMC> seahorse-plugins. I find people that expect to be using seahorse-agent > JMC> are using the entire GNOME Desktop. > > Another question: is there a way to avoid apache22 install (i have apache13 > installed and have no current plans to upgrade) ? I tried to chase > options but failed. Not by using the meta-port. This is required for gnome-user-share which is now part of the GNOME Desktop. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: JMC> I had assumed you had x11/gnome2 installed which includes JMC> seahorse-plugins. I find people that expect to be using seahorse-agent JMC> are using the entire GNOME Desktop. Another question: is there a way to avoid apache22 install (i have apache13 installed and have no current plans to upgrade) ? I tried to chase options but failed. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: JMC> > RN> If I am following this correctly, the functionality you are talking JMC> > RN> about is actually provided by seahorse-agent, which is installed with JMC> > RN> the seahorse-plugins port now. Unless something has changed with the JMC> > RN> default session (and I don't think it has, since my keyrings still work) JMC> > RN> we wrap the session with ssh-agent and seahorse-agent if they are found. JMC> > JMC> > Aha! Yes, and seahorse-plugins was not installed; moreover, one of its JMC> > dependencies (pth) conflicted with pth-hard installed previously. I'll try to JMC> > clean this up and report the results. JMC> JMC> I had assumed you had x11/gnome2 installed which includes JMC> seahorse-plugins. I find people that expect to be using seahorse-agent JMC> are using the entire GNOME Desktop. Well, I did ;-) Somehow during the upgrade gnome2 meta-port had been uninstalled, hence missing portupgrade -a. I'm now in progress of portupgrade -N gnome2, will report the results. Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 21:05 +0400, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Robert Noland wrote: > > [snip all] > > RN> > Yes, seahorse shows me two keyrings; however, deleting "login" one does > not fix > RN> > the situation: if in the Terminal I try to open tab which ssh's to > outer host, > RN> > I immediately got the popup with > RN> > > RN> > "There was an error creating the child process for this terminal" > RN> > > RN> > nothing in this tab is started, and tab is just hanging. > RN> > > RN> > "login" keyring sometimes got recreated, sometimes not, but the effect > above is > RN> > totally reproducible. > RN> > RN> If I am following this correctly, the functionality you are talking > RN> about is actually provided by seahorse-agent, which is installed with > RN> the seahorse-plugins port now. Unless something has changed with the > RN> default session (and I don't think it has, since my keyrings still work) > RN> we wrap the session with ssh-agent and seahorse-agent if they are found. > > Aha! Yes, and seahorse-plugins was not installed; moreover, one of its > dependencies (pth) conflicted with pth-hard installed previously. I'll try to > clean this up and report the results. I had assumed you had x11/gnome2 installed which includes seahorse-plugins. I find people that expect to be using seahorse-agent are using the entire GNOME Desktop. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
2009/4/14 Michal Varga : > On Tue, Apr 14, 2009 at 5:34 PM, Dmitry Morozovsky wrote: >> On Tue, 14 Apr 2009, Michal Varga wrote: > >> Yes, it's Gnome Terminal, see $SUBJ ;-) >> >> I just filled 'ssh -e none host' in execute command field. >> >> Before upgrade to 2.26 everything is worked like a charm -- on a first >> external >> connect, seahorse popup appears, asks me for a passphrase, and subsequent >> external sessions works automagically. >> > I'm still puzzled with that, by execute command field i guess you mean > "[x] run a custom command instead of my shell" in gnome-terminal > preferences. Bud where'd you get the ssh/seahorse functionality? > > Let's assume the 'ssh' will run the first ssh in path, that is by default > > $ which ssh > /usr/bin/ssh > > $ ssh -V > OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 > > But where does your seahorse powered ssh client come from? It's an ssh agent, not an ssh client. I think it defines some SSH_* env variables at session opening, which are used by /usr/bin/ssh. -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email & vCards X www: http://www.gid0.org- against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Robert Noland wrote: [snip all] RN> > Yes, seahorse shows me two keyrings; however, deleting "login" one does not fix RN> > the situation: if in the Terminal I try to open tab which ssh's to outer host, RN> > I immediately got the popup with RN> > RN> > "There was an error creating the child process for this terminal" RN> > RN> > nothing in this tab is started, and tab is just hanging. RN> > RN> > "login" keyring sometimes got recreated, sometimes not, but the effect above is RN> > totally reproducible. RN> RN> If I am following this correctly, the functionality you are talking RN> about is actually provided by seahorse-agent, which is installed with RN> the seahorse-plugins port now. Unless something has changed with the RN> default session (and I don't think it has, since my keyrings still work) RN> we wrap the session with ssh-agent and seahorse-agent if they are found. Aha! Yes, and seahorse-plugins was not installed; moreover, one of its dependencies (pth) conflicted with pth-hard installed previously. I'll try to clean this up and report the results. Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, Apr 14, 2009 at 5:34 PM, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Michal Varga wrote: > Yes, it's Gnome Terminal, see $SUBJ ;-) > > I just filled 'ssh -e none host' in execute command field. > > Before upgrade to 2.26 everything is worked like a charm -- on a first > external > connect, seahorse popup appears, asks me for a passphrase, and subsequent > external sessions works automagically. > I'm still puzzled with that, by execute command field i guess you mean "[x] run a custom command instead of my shell" in gnome-terminal preferences. Bud where'd you get the ssh/seahorse functionality? Let's assume the 'ssh' will run the first ssh in path, that is by default $ which ssh /usr/bin/ssh $ ssh -V OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 But where does your seahorse powered ssh client come from? m. ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Michal Varga wrote: MV> > Yes, seahorse shows me two keyrings; however, deleting "login" one does not fix MV> > the situation: if in the Terminal I try to open tab which ssh's to outer host, MV> > I immediately got the popup with MV> > MV> > "There was an error creating the child process for this terminal" MV> > MV> > nothing in this tab is started, and tab is just hanging. MV> > MV> Out of curiosity, unrelated to your issue - if this is about MV> interactive ssh [shell] session, do you mean Gnome Terminal? MV> MV> I wasn't aware it can do anything on its own with ssh, normally I run MV> the regular ssh client inside. How do you ssh directly from Gnome MV> Terminal (if that's the one you mean) with gnome-keyring/seahorse MV> capabilities? Yes, it's Gnome Terminal, see $SUBJ ;-) I just filled 'ssh -e none host' in execute command field. Before upgrade to 2.26 everything is worked like a charm -- on a first external connect, seahorse popup appears, asks me for a passphrase, and subsequent external sessions works automagically. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 14:24 +0400, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Michal Varga wrote: > > MV> On Tue, Apr 14, 2009 at 3:13 AM, Dmitry Morozovsky wrote: > MV> > Dear Joe Marcus, > MV> > > MV> > DM> JMC> What versions of gnome-keyring and seahorse do you have? > MV> > DM> > MV> > DM> ma...@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse' > MV> > DM> gnome-keyring-2.26.0 A program that keeps passwords and other > secrets > MV> > DM> seahorse-2.26.0 GNOME application for managing encryption keys > (PGP, SSH) > MV> > > MV> > After > MV> > > MV> > portupgrade -f seahorse gnome-keyring > MV> > > MV> > and reboot > MV> > > MV> > still the same effect... > MV> > > MV> > Of course, I can wipe packages installed and set it up from scratch, > but I > MV> > would prefer a bit safer way if at all possible ;-) > MV> > > MV> Well, I have no idea what a "Terminal remote login" in this particular > MV> context is, so this may not be of any help, but I've seen this issue > MV> before: > MV> > MV> "Before the upgrade, I had once pop-up asking for my key passphrase, then > MV> let me use this private key during my (home) session without further > asking.. > MV> Now, when I try to connect to the host which even possibly want to check > MV> whether I want to present some key there, I got the pop-up. I even > checked that > MV> I can connect to the host in question using plain xterm, and have usual > MV> password qiery." > MV> > MV> I've been in similiar situation some time ago, when new > MV> gnome-keyring/seahorse (it started with one of the recent versions, > MV> don't remember exactly when, but definitely before 2.26 was > MV> introduced) for some surely interesting reason insisted on creating a > MV> very own keyring every other reboot - while originally you were using > MV> one default keyring (let's call it "default") for storing your > MV> passwords, now gnome-keyring kept creating a new one named "login" and > MV> always set it as the default one. > MV> > MV> That "login" keyring was even more special in that that nothing stored > MV> in it ever worked, it still kept asking for passwords and even then > MV> was not able to use them (and lost them on the next reboot anyway.. > MV> Maybe that's a feature, don't know, don't care). I've run into this on > MV> a few different machines, every time I needed to open 'seahorse', get > MV> to Passwords tab, delete the "login" keyring, set the original > MV> "default" as the default keyring (first time I wiped them all and > MV> created a clean one to be sure, but as it turned out later, this > MV> wasn't needed), after that, passwords worked fine again. This > MV> procedure again and again for a few days/reboots, until seahorse > MV> miraculously stopped this madness and let my default keyring be, well, > MV> default (yes, just like that). > MV> > MV> Anyway, if you weren't there yet, check seahorse gui for what keyring > MV> are you really using, maybe you've hit the same issue with the "login" > MV> stupidity.. > > Yes, seahorse shows me two keyrings; however, deleting "login" one does not > fix > the situation: if in the Terminal I try to open tab which ssh's to outer > host, > I immediately got the popup with > > "There was an error creating the child process for this terminal" > > nothing in this tab is started, and tab is just hanging. > > "login" keyring sometimes got recreated, sometimes not, but the effect above > is > totally reproducible. If I am following this correctly, the functionality you are talking about is actually provided by seahorse-agent, which is installed with the seahorse-plugins port now. Unless something has changed with the default session (and I don't think it has, since my keyrings still work) we wrap the session with ssh-agent and seahorse-agent if they are found. robert. -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, Apr 14, 2009 at 12:24 PM, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Michal Varga wrote: > Yes, seahorse shows me two keyrings; however, deleting "login" one does not > fix > the situation: if in the Terminal I try to open tab which ssh's to outer host, > I immediately got the popup with > > "There was an error creating the child process for this terminal" > > nothing in this tab is started, and tab is just hanging. > Out of curiosity, unrelated to your issue - if this is about interactive ssh [shell] session, do you mean Gnome Terminal? I wasn't aware it can do anything on its own with ssh, normally I run the regular ssh client inside. How do you ssh directly from Gnome Terminal (if that's the one you mean) with gnome-keyring/seahorse capabilities? m. ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Michal Varga wrote: MV> On Tue, Apr 14, 2009 at 3:13 AM, Dmitry Morozovsky wrote: MV> > Dear Joe Marcus, MV> > MV> > DM> JMC> What versions of gnome-keyring and seahorse do you have? MV> > DM> MV> > DM> ma...@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse' MV> > DM> gnome-keyring-2.26.0 A program that keeps passwords and other secrets MV> > DM> seahorse-2.26.0 GNOME application for managing encryption keys (PGP, SSH) MV> > MV> > After MV> > MV> > portupgrade -f seahorse gnome-keyring MV> > MV> > and reboot MV> > MV> > still the same effect... MV> > MV> > Of course, I can wipe packages installed and set it up from scratch, but I MV> > would prefer a bit safer way if at all possible ;-) MV> > MV> Well, I have no idea what a "Terminal remote login" in this particular MV> context is, so this may not be of any help, but I've seen this issue MV> before: MV> MV> "Before the upgrade, I had once pop-up asking for my key passphrase, then MV> let me use this private key during my (home) session without further asking.. MV> Now, when I try to connect to the host which even possibly want to check MV> whether I want to present some key there, I got the pop-up. I even checked that MV> I can connect to the host in question using plain xterm, and have usual MV> password qiery." MV> MV> I've been in similiar situation some time ago, when new MV> gnome-keyring/seahorse (it started with one of the recent versions, MV> don't remember exactly when, but definitely before 2.26 was MV> introduced) for some surely interesting reason insisted on creating a MV> very own keyring every other reboot - while originally you were using MV> one default keyring (let's call it "default") for storing your MV> passwords, now gnome-keyring kept creating a new one named "login" and MV> always set it as the default one. MV> MV> That "login" keyring was even more special in that that nothing stored MV> in it ever worked, it still kept asking for passwords and even then MV> was not able to use them (and lost them on the next reboot anyway.. MV> Maybe that's a feature, don't know, don't care). I've run into this on MV> a few different machines, every time I needed to open 'seahorse', get MV> to Passwords tab, delete the "login" keyring, set the original MV> "default" as the default keyring (first time I wiped them all and MV> created a clean one to be sure, but as it turned out later, this MV> wasn't needed), after that, passwords worked fine again. This MV> procedure again and again for a few days/reboots, until seahorse MV> miraculously stopped this madness and let my default keyring be, well, MV> default (yes, just like that). MV> MV> Anyway, if you weren't there yet, check seahorse gui for what keyring MV> are you really using, maybe you've hit the same issue with the "login" MV> stupidity.. Yes, seahorse shows me two keyrings; however, deleting "login" one does not fix the situation: if in the Terminal I try to open tab which ssh's to outer host, I immediately got the popup with "There was an error creating the child process for this terminal" nothing in this tab is started, and tab is just hanging. "login" keyring sometimes got recreated, sometimes not, but the effect above is totally reproducible. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, Apr 14, 2009 at 3:13 AM, Dmitry Morozovsky wrote: > Dear Joe Marcus, > > DM> JMC> What versions of gnome-keyring and seahorse do you have? > DM> > DM> ma...@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse' > DM> gnome-keyring-2.26.0 A program that keeps passwords and other secrets > DM> seahorse-2.26.0 GNOME application for managing encryption keys (PGP, > SSH) > > After > > portupgrade -f seahorse gnome-keyring > > and reboot > > still the same effect... > > Of course, I can wipe packages installed and set it up from scratch, but I > would prefer a bit safer way if at all possible ;-) > Well, I have no idea what a "Terminal remote login" in this particular context is, so this may not be of any help, but I've seen this issue before: "Before the upgrade, I had once pop-up asking for my key passphrase, then let me use this private key during my (home) session without further asking.. Now, when I try to connect to the host which even possibly want to check whether I want to present some key there, I got the pop-up. I even checked that I can connect to the host in question using plain xterm, and have usual password qiery." I've been in similiar situation some time ago, when new gnome-keyring/seahorse (it started with one of the recent versions, don't remember exactly when, but definitely before 2.26 was introduced) for some surely interesting reason insisted on creating a very own keyring every other reboot - while originally you were using one default keyring (let's call it "default") for storing your passwords, now gnome-keyring kept creating a new one named "login" and always set it as the default one. That "login" keyring was even more special in that that nothing stored in it ever worked, it still kept asking for passwords and even then was not able to use them (and lost them on the next reboot anyway.. Maybe that's a feature, don't know, don't care). I've run into this on a few different machines, every time I needed to open 'seahorse', get to Passwords tab, delete the "login" keyring, set the original "default" as the default keyring (first time I wiped them all and created a clean one to be sure, but as it turned out later, this wasn't needed), after that, passwords worked fine again. This procedure again and again for a few days/reboots, until seahorse miraculously stopped this madness and let my default keyring be, well, default (yes, just like that). Anyway, if you weren't there yet, check seahorse gui for what keyring are you really using, maybe you've hit the same issue with the "login" stupidity.. m. ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 04:52 +0400, Dmitry Morozovsky wrote: > On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: > > JMC> > JMC> Then I guess I misunderstand the problem. Are you having a > problem with > JMC> > JMC> seahorse-agent acting as an SSH agent? > JMC> > > JMC> > It seems to be so. > JMC> > > JMC> > Let me explain the situation a bit: > JMC> > > JMC> > My home machine, RELENG_7/i386, with fresh source and fresh ports > tree, acts as > JMC> > my window to my work servers, some of them recognising my SSH key as > trusted. > JMC> > > JMC> > Before the upgrade, I had once pop-up asking for my key passphrase, > then > JMC> > let me use this private key during my (home) session without further > asking. > JMC> > > JMC> > Now, when I try to connect to the host which even possibly want to > check > JMC> > whether I want to present some key there, I got the pop-up. I even > checked that > JMC> > I can connect to the host in question using plain xterm, and have > usual > JMC> > password qiery. > JMC> > JMC> What versions of gnome-keyring and seahorse do you have? > > ma...@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse' > gnome-keyring-2.26.0 A program that keeps passwords and other secrets > seahorse-2.26.0 GNOME application for managing encryption keys (PGP, SSH) Go to 2.26.1 on both, and see if the problem persists. Joe > -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
Dear Joe Marcus, DM> JMC> What versions of gnome-keyring and seahorse do you have? DM> DM> ma...@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse' DM> gnome-keyring-2.26.0 A program that keeps passwords and other secrets DM> seahorse-2.26.0 GNOME application for managing encryption keys (PGP, SSH) After portupgrade -f seahorse gnome-keyring and reboot still the same effect... Of course, I can wipe packages installed and set it up from scratch, but I would prefer a bit safer way if at all possible ;-) Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC> > JMC> Then I guess I misunderstand the problem. Are you having a problem with JMC> > JMC> seahorse-agent acting as an SSH agent? JMC> > JMC> > It seems to be so. JMC> > JMC> > Let me explain the situation a bit: JMC> > JMC> > My home machine, RELENG_7/i386, with fresh source and fresh ports tree, acts as JMC> > my window to my work servers, some of them recognising my SSH key as trusted. JMC> > JMC> > Before the upgrade, I had once pop-up asking for my key passphrase, then JMC> > let me use this private key during my (home) session without further asking. JMC> > JMC> > Now, when I try to connect to the host which even possibly want to check JMC> > whether I want to present some key there, I got the pop-up. I even checked that JMC> > I can connect to the host in question using plain xterm, and have usual JMC> > password qiery. JMC> JMC> What versions of gnome-keyring and seahorse do you have? ma...@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse' gnome-keyring-2.26.0 A program that keeps passwords and other secrets seahorse-2.26.0 GNOME application for managing encryption keys (PGP, SSH) -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 04:46 +0400, Dmitry Morozovsky wrote: > On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: > > JMC> > JMC> > remote login using ssh keys with the following message in the > logs (sorry, > JMC> > JMC> > can't reproduce the message from Terminal popup window) > JMC> > JMC> > > JMC> > JMC> > Apr 12 11:54:37 revamp kernel: Apr 12 11:54:37 > > JMC> > JMC> > revamp gnome-keyring-ask: couldn't allocate secure memory to > keep passwords and > JMC> > JMC> > or keys from being written to the disk > JMC> > JMC> > > JMC> > JMC> > Any hints to fix this? RELENG_7/i386 > JMC> > JMC> > JMC> > JMC> This error is normal, and not fatal. How do you have PAM > configured for > JMC> > JMC> SSH? > JMC> > > JMC> > > JMC> > Hrrm, this is from client side, not from server, how can PAM intervent > with > JMC> > this? > JMC> > JMC> Then I guess I misunderstand the problem. Are you having a problem with > JMC> seahorse-agent acting as an SSH agent? > > It seems to be so. > > Let me explain the situation a bit: > > My home machine, RELENG_7/i386, with fresh source and fresh ports tree, acts > as > my window to my work servers, some of them recognising my SSH key as trusted. > > Before the upgrade, I had once pop-up asking for my key passphrase, then > let me use this private key during my (home) session without further asking. > > Now, when I try to connect to the host which even possibly want to check > whether I want to present some key there, I got the pop-up. I even checked > that > I can connect to the host in question using plain xterm, and have usual > password qiery. What versions of gnome-keyring and seahorse do you have? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC> > JMC> > remote login using ssh keys with the following message in the logs (sorry, JMC> > JMC> > can't reproduce the message from Terminal popup window) JMC> > JMC> > JMC> > JMC> > Apr 12 11:54:37 revamp kernel: Apr 12 11:54:37 JMC> > JMC> > revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and JMC> > JMC> > or keys from being written to the disk JMC> > JMC> > JMC> > JMC> > Any hints to fix this? RELENG_7/i386 JMC> > JMC> JMC> > JMC> This error is normal, and not fatal. How do you have PAM configured for JMC> > JMC> SSH? JMC> > JMC> > JMC> > Hrrm, this is from client side, not from server, how can PAM intervent with JMC> > this? JMC> JMC> Then I guess I misunderstand the problem. Are you having a problem with JMC> seahorse-agent acting as an SSH agent? It seems to be so. Let me explain the situation a bit: My home machine, RELENG_7/i386, with fresh source and fresh ports tree, acts as my window to my work servers, some of them recognising my SSH key as trusted. Before the upgrade, I had once pop-up asking for my key passphrase, then let me use this private key during my (home) session without further asking. Now, when I try to connect to the host which even possibly want to check whether I want to present some key there, I got the pop-up. I even checked that I can connect to the host in question using plain xterm, and have usual password qiery. Any other hints? Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 04:30 +0400, Dmitry Morozovsky wrote: > On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: > > JMC> > After upgrading via portupgrade -a my home machine I can no longer use > Treminal > JMC> > remote login using ssh keys with the following message in the logs > (sorry, > JMC> > can't reproduce the message from Terminal popup window) > JMC> > > JMC> > Apr 12 11:54:37 revamp kernel: Apr 12 11:54:37 > > JMC> > revamp gnome-keyring-ask: couldn't allocate secure memory to keep > passwords and > JMC> > or keys from being written to the disk > JMC> > > JMC> > Any hints to fix this? RELENG_7/i386 > JMC> > JMC> This error is normal, and not fatal. How do you have PAM configured for > JMC> SSH? > > > Hrrm, this is from client side, not from server, how can PAM intervent with > this? Then I guess I misunderstand the problem. Are you having a problem with seahorse-agent acting as an SSH agent? Joe > > BTW, I have > > There was an error creating the child process for this terminal > > as a modal dialog box when I tried to open stored Terminal window to the host > which requires authorized_keys authentication. > -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC> > After upgrading via portupgrade -a my home machine I can no longer use Treminal JMC> > remote login using ssh keys with the following message in the logs (sorry, JMC> > can't reproduce the message from Terminal popup window) JMC> > JMC> > Apr 12 11:54:37 revamp kernel: Apr 12 11:54:37 JMC> > revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and JMC> > or keys from being written to the disk JMC> > JMC> > Any hints to fix this? RELENG_7/i386 JMC> JMC> This error is normal, and not fatal. How do you have PAM configured for JMC> SSH? Hrrm, this is from client side, not from server, how can PAM intervent with this? BTW, I have There was an error creating the child process for this terminal as a modal dialog box when I tried to open stored Terminal window to the host which requires authorized_keys authentication. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 03:47 +0400, Dmitry Morozovsky wrote: > On Fri, 10 Apr 2009, Joe Marcus Clarke wrote: > > JMC> GNOME 2.26 has been merged into the ports tree. See > > [snip] > > After upgrading via portupgrade -a my home machine I can no longer use > Treminal > remote login using ssh keys with the following message in the logs (sorry, > can't reproduce the message from Terminal popup window) > > Apr 12 11:54:37 revamp kernel: Apr 12 11:54:37 > revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords > and > or keys from being written to the disk > > Any hints to fix this? RELENG_7/i386 This error is normal, and not fatal. How do you have PAM configured for SSH? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Fri, 10 Apr 2009, Joe Marcus Clarke wrote: JMC> GNOME 2.26 has been merged into the ports tree. See [snip] After upgrading via portupgrade -a my home machine I can no longer use Treminal remote login using ssh keys with the following message in the logs (sorry, can't reproduce the message from Terminal popup window) Apr 12 11:54:37 revamp kernel: Apr 12 11:54:37 revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and or keys from being written to the disk Any hints to fix this? RELENG_7/i386 Thanks in advance. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
Hi, Am Freitag, den 10.04.2009, 02:12 -0400 schrieb Joe Marcus Clarke: > GNOME 2.26 has been merged into the ports tree. See > http://library.gnome.org/misc/release-notes/2.26/ for a list of what's > new. On the FreeBSD front, we introduced a port of libxul 1.9 as an > alternative for Firefox 2.0 as a Gecko provider. Almost all of the > Gecko consumers can make use of this provider by setting: > > WITH_GECKO=libxul I see galeon-2.0.7 (via gnome2-fifth-toe) offers option "xulrunner" not "libxul". With your setting WITH_GECKO=libxul it will use firefox instead. Greeetings, Uli. > Joe > ___ 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"
HEADS UP: GNOME 2.26 available for FreeBSD
GNOME 2.26 has been merged into the ports tree. See http://library.gnome.org/misc/release-notes/2.26/ for a list of what's new. On the FreeBSD front, we introduced a port of libxul 1.9 as an alternative for Firefox 2.0 as a Gecko provider. Almost all of the Gecko consumers can make use of this provider by setting: WITH_GECKO=libxul The GNOME 2.26 port was done by ahze, kwm, marcus, and mezz with contributions by Joseph S. Atkinson, Peter Wemm, Eric L. Chen, Martin Matuska, Craig Butler, and Pawel Worach. Additionally, I'd like to thank pav for the pointyhat run. As for upgrades, we didn't see too many issues in testing. Of course, I'm not sure how many testers we had this go around. The number seems to get smaller each release. Stay tuned to UPDATING in case issues do arise. For porters, the includes system was consolidated in GNOME 2.26. You may see build failures saying that gnome.h cannot be found, or missing libgnomeui symbols. These can typically be fixed by adding the following to the port's Makefile: CONFIGURE_ENV= CPPFLAGs="`pkg-config --cflags libgnomeui-2.0`" \ LIBS="`pkg-config --libs libgnomeui-2.0`" Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
