On 23/07/12 09:37, Christian Engwer wrote: > On Sun, Jul 22, 2012 at 11:16:39PM +0100, Ximin Luo wrote: >> It was clearly a typo to *you*, in your context with the bug being present. >> In >> my context, where everything is fine, *I* have no idea what "keyword" means. >> >> I am running gnome-keyring 3.4 and it works OK for me. >> >> Note that if your keyring is unlocked, gnome-keyring will prompt you to >> unlock >> your keyring. While this dialog box is open, firefox will indeed not respond >> to >> user input. If you think this is a bug, file it to the gnome-keyring >> developers, but I guess they would call it a "security feature". > > there is no reason treating users like idiots. If you would have read > my last mail properly you'd have seen that I corrected my typo and > explained that it is about storing the password. The keyring is > unlocked and works for all other applications. But never mind, I don't > care using this package anymore. And with this tone of correspondence > I also don't care about helping any further. >
Don't be arrogant. You were the one that initially implied I was stupid for not understanding your report. I explained to you why this is not a correct assumption to make. If you would have read my last mail correctly, you would have seen that I *did* read your last mail correctly. As it is, you still have not provided enough useful information to constitute a proper bug report. I repeat what I said in my very first email - I can't understand you at all. > I close the bug so that it doesn't distract you in your mailbox anymore. > > Christian > >> On 22/07/12 21:21, Christian Engwer wrote: >>> On Sat, Jul 21, 2012 at 01:37:20PM +0100, Ximin Luo wrote: >>>> ping? >>> >>> pong! >>> >>>>>> adding an iceweasel keyword to the gnome-keyring will freeze >>> >>> This was clearly a typo... I wanted to say that adding a password in >>> iceweasel (current from testing) results in a frozen iceweasel. I'd >>> don't know what the exact reason is. Storing passwords in the >>> traditional iceweasel vault works, just es the plugin did work some >>> time ago. I suspect that the problem origins from the >>> gnome-keyring. I used to have the 3.2 keyring and recently 3.4 entered >>> from unstable. >>> >>> If you have a particular question I can try to give more details. >>> >>> Christian >>> >>>>> Please elaborate - I don't understand this at all. >>>>> >>>>>> iceweasel. This extension used to work, but in newser versions it >>>>>> doesn't anymore. I assume it is an incompatiblity with the gnome 3.4 >>>>>> keyring. >>>>>> >>>>>> Christian >>>>>> >>>>>> -- System Information: >>>>>> Debian Release: wheezy/sid >>>>>> APT prefers proposed-updates >>>>>> APT policy: (500, 'proposed-updates'), (500, 'testing'), (400, >>>>>> 'stable'), (300, 'unstable'), (1, 'experimental') >>>>>> Architecture: amd64 (x86_64) >>>>>> >>>>>> Kernel: Linux 3.3.0-trunk-amd64 (SMP w/4 CPU cores) >>>>>> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) >>>>>> Shell: /bin/sh linked to /bin/dash >>>>>> >>>>>> Versions of packages xul-ext-gnome-keyring depends on: >>>>>> ii iceweasel 10.0.5esr-2 >>>>>> ii libc6 2.13-33 >>>>>> ii libgcc1 1:4.7.1-2 >>>>>> ii libglib2.0-0 2.32.3-1 >>>>>> ii libgnome-keyring0 3.4.1-1 >>>>>> ii libnspr4 2:4.9.1-1 >>>>>> ii libnspr4-0d 2:4.9.1-1 >>>>>> ii libstdc++6 4.7.1-2 >>>>>> >>>>>> xul-ext-gnome-keyring recommends no packages. >>>>>> >>>>>> xul-ext-gnome-keyring suggests no packages. >>>>>> >>>>>> -- no debconf information >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> GPG: 4096R/5FBBDBCE >>>> https://github.com/infinity0 >>>> https://bitbucket.org/infinity0 >>>> https://launchpad.net/~infinity0 >>>> >> >> >> -- >> GPG: 4096R/5FBBDBCE >> https://github.com/infinity0 >> https://bitbucket.org/infinity0 >> https://launchpad.net/~infinity0 >> > > > -- GPG: 4096R/5FBBDBCE https://github.com/infinity0 https://bitbucket.org/infinity0 https://launchpad.net/~infinity0
signature.asc
Description: OpenPGP digital signature
