On 5 September 2010 10:30, Yves-Alexis Perez wrote:
> I've uploaded a fixed version, could you check that it indeed fix the
> problem? I'm waiting for it to pass some days in unstable before asking
> a freeze exception.
It does, thank you.
Cheers,
Luca
--
To UNSUBSCRIBE, email to debian-bu
On mar., 2010-08-31 at 23:13 +0200, Luca Niccoli wrote:
> Are you planning to upload a patched version in squeeze?
> I feel gnome-keyring has become quite an important part for many GTK
> programs, so it would be a pity if people using xfce couldn't use it
> properly.
> As you can see the patches a
On 1 September 2010 12:23, Yves-Alexis Perez wrote:
> dbus is usually started using 75dbus_dbus-launch. On my system it's
> gpg-agent -> dbus-launch -> startxfce4.
>
> It might depend on how you start Xfce (if dbus isn't started when
> startxfce4 is run, it will start it itself), but in any case,
On 01/09/2010 11:38, Luca Niccoli wrote:
> On 1 September 2010 07:31, Yves-Alexis Perez wrote
>
>> I'm not using an older version, I'm using a more recent version :)
>>
>> ii gnome-keyring 2.30.3-1 GNOME keyring services (daemon and
>> tools)
>
> I'm using that too. Probably the version
On 1 September 2010 07:31, Yves-Alexis Perez wrote
> I'm not using an older version, I'm using a more recent version :)
>
> ii gnome-keyring 2.30.3-1 GNOME keyring services (daemon and
> tools)
I'm using that too. Probably the version of Xfce you're using has the bug fixed
> That's beca
On mar., 2010-08-31 at 23:52 +0200, Luca Niccoli wrote:
> On 31 August 2010 23:24, Yves-Alexis Perez wrote:
>
> > Hmh, to be honest, gnome-keyring is started properly here (though I'm
> > not using 4.6 on that box and can't check on another one).
>
> Maybe if you're not using 4.6 you have an old
On 31 August 2010 23:52, Luca Niccoli wrote:
> It doesn't work; "SSH Key Agent" doesn't even show up as an option
> among the autostarted applications in xfce4-session-settings .
Mmm, it just needed to be copied to /etc/xdg/autostart; it doesn't
work anyway (the variables are not exported)
Cheer
On 31 August 2010 23:24, Yves-Alexis Perez wrote:
> Hmh, to be honest, gnome-keyring is started properly here (though I'm
> not using 4.6 on that box and can't check on another one).
Maybe if you're not using 4.6 you have an old version of gnome-keyring
as well? The way it was supposed to be sta
On mar., 2010-08-31 at 23:24 +0200, Yves-Alexis Perez wrote:
> Btw, I can see that:
>
> /usr/share/gnome/autostart/gnome-keyring-ssh.desktop
>
> contains OnlyShowIn=GNOME;LXDE;
>
> If gnome-keyring-ssh is what you need, wouldn't it be simpler to add
> Xfce to that list?
And same thing for /us
On mar., 2010-08-31 at 23:13 +0200, Luca Niccoli wrote:
> Hi,
>
> I've been using an xfce4-session package patched with the two patches
> linked in the previous mail, and I've not had problems in the last
> three months.
Sorry for not replying sooner, I'll try to give the patches an eye, but
I do
Hi,
I've been using an xfce4-session package patched with the two patches
linked in the previous mail, and I've not had problems in the last
three months.
Are you planning to upload a patched version in squeeze?
I feel gnome-keyring has become quite an important part for many GTK
programs, so it w
reassign 523322 xfce4-session
retitle 523322 add support for newer versions of gnome-keyring
forwarded 523322 http://bugzilla.xfce.org/show_bug.cgi?id=5912
tags 523322 + patch
thank you
I think this bug can be most properly fixed by changing the way
xfce4-session starts gnome-keyring.
With the tw
I have this bug since upgrading gnome-desktop-environment to 2.28+1
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (501, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC
reopen 523322
thank you
On an other system I still get the old behaviour (i.e. gnome-keyring
doesn't act as a ssh agent);
I realized that in the computer in which I got it working it could
have been because of a saved session...
Sorry,
Luca
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...
Josselin Mouette wrote:
> Indeed, but GDM (and especially the PAM stack) has no idea that
> gnome-keyring won’t be used at that time.
>
> Maybe a timeout could be added to make the daemon exit when it is not
> initialized.
I guess it's started by gdm for the login password and thus it can't be ju
Le dimanche 30 août 2009 à 21:05 +0200, Tanguy Ortolo a écrit :
> I think this is the same bug as Ubuntu's #377467. To sum up:
> - GDM, according to PAM settings, spawns gnome-keyring-daemon;
> - gnome-keyring-daemon is now running, but not initialized, so it does not do
> SSH-agent yet;
> - if
Package: gnome-keyring
Version: 2.26.1-1
Severity: normal
I think this is the same bug as Ubuntu's #377467. To sum up:
- GDM, according to PAM settings, spawns gnome-keyring-daemon;
- gnome-keyring-daemon is now running, but not initialized, so it does not do
SSH-agent yet;
- if you are running
The forwarded bug at GNOME bugzilla is a completely different bug from
the one I am hitting. Additionally, #524018 is not this bug, in my
opinion.
The regression, for me, is because gnome-keyring sets its environment
variables using gnome-session's Setenv(s,s) D-Bus method[0]. In the
gnome-session
This bug has been forward to
http://bugzilla.gnome.org/show_bug.cgi?id=576700, but that bug report
appears to have actually been interpreted by upstream as being related
to a separate issue. Looking over the bug, I'm not at all convinced
that it has actually corrected the problem reported here.
I just wanted to mention in this bug report that I am seeing the
behavior on my i386 (686, actually) 32-bit Intel system. The upstream
bug report seems to be going in the direction of this being amd64
specific, but it is not. I also updated the upstream bug report with
those comments and will ma
I also experience this. Downgrading to 2.24.1-2 also fixes the problem
for me. I just tried looking at a diff of 2.24.1-2 and 2.26.0-4 but
it's huge:
603 files changed, 119903 insertions(+), 67373 deletions(-)
gnome-keyring is started and even sets some environment
variables. Here are all the SSH
Le samedi 11 avril 2009 à 13:29 +0200, Noèl Köthe a écrit :
> Hello,
>
> JFYI:
> I can confirm this problem on amd64 sid with gnome-keyring. downgrading
> the keyring packages to 2.24 give me the needed agent function back.
>
> Tell me if you need more infos/details which are not mentioned by
> L
Hello,
JFYI:
I can confirm this problem on amd64 sid with gnome-keyring. downgrading
the keyring packages to 2.24 give me the needed agent function back.
Tell me if you need more infos/details which are not mentioned by
Luca/the report.
--
Noèl Köthe
Debian GNU/Linux, www.debian.org
signatur
Package: gnome-keyring
Version: 2.26.0-3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The symptoms are pretty much the same as the ones described at:
http://bugs.archlinux.org/task/13986
I use Xfce and gdm, gnome-keyring-daemon is started at login time (from pam
I guess).
Cheer
24 matches
Mail list logo
