[13:52] hi, I have a grub issue since I've installed ubuntu-gnome. So as my problem isn't related to the DE should I ask my questions in #ubuntu channel? [13:57] hello there :) [14:04] this channel about a very popular system is so silent, I'm very surprised [14:05] maybe my IRC client is not working ;) [23:08] ubuntu gnome 16.04 updated fresh install, but same problem earlier on 15.10: gnome-keyring-daemon is auto-started in Startup Applications, but only occasionally does the gui pwd box come up when I ssh to a host. Usually, it asks me for the pwd each and every time in the terminal. [23:09] Any thoughts? [23:12] Also, I've got this problem which is new in 16.04. I have "mouse trails". The mouse leaves multiple images of the pointer as I move across the screen. They stay for a few seconds and then disappear. In 15.10 I was using the nvidia drivers, but I'm not doing that in 16.04. [23:16] (This is the command that is created on install for the "SSH Key Agent" on startup: /usr/bin/gnome-keyring-daemon --start --components=ssh [23:17] Diagon, I only get the keyring prompt once per boot. I'm not sure if I'm doing anything different than you though [23:18] I haven't done anything other than what the clean install creates for startup of the key agent. [23:18] Diagon, what do you want it to do? GUI prompt every time? CLI prompt every time? [23:18] When I do get the gui pwd box, I only have to put my pwd in once per session. Otherwise, it's each time I ssh. [23:19] I'd prefer the gui prompt so I don't have to do it repeatedly. [23:20] The gui prompt will only come up if your SSH_AUTH_SOCK environment variable is set (and correct) [23:20] so maybe check that env variable when you don't get a gui prompt? [23:21] Ok; but why is it set on some startups and not on others? [23:21] I've never messed with it. [23:21] Diagon, I don't know. I've never encountered any issue like this [23:21] Ok. Thoughts on where/who I might ask? [23:22] Or how I might look into it? [23:24] Ok, that's not working... SSH_AUTH_SOCK=/run/user/1000/keyring/ssh, but it's asking me for pwd on command line every time. [23:24] and your gnome-keyring-daemon is running? [23:24] srwxrwxr-x 1 dev dev 0 Jun 9 21:59 /run/user/1000/keyring/ssh [23:25] Yes, with --deamonize --login [23:28] Diagon, what command are you using that uses a ssh key? [23:29] ssh uname@host [23:29] various hosts [23:29] also sshuttle [23:32] I run those through various simple scripts, by the way, like the "sshhost" script will "ssh me@host" or something like that. [23:35] Diagon, hmm that should work, env variables do pass into scripts [23:36] What if you just type it manually? [23:36] Same problem (just checked) [23:37] Diagon, can you open a up new terminal using Ctrl + Alt + T, and try with that? [23:37] That's what I just did. [23:38] Oops, no. [23:38] I did it in tmux. Starting a new terminal does give me the gui. [23:38] ! [23:38] ??? [23:38] heh [23:39] wtf?!? [23:39] Using the script in the new terminal also give me the gui. [23:39] So it's not the script.... [23:40] First ssh on login is not through tmux, so that's not the issue [23:40] Ok, here's a clue ... [23:41] The terminal that I started works, but if I use a new terminal in the one that is auto-started for me when I boot up, it doesn't work. (That is, Ctl-Shift-T within that auto-started terminal.) [23:41] Something got cut off, let me try again. [23:42] When I boot up, a terminal is started for me (auto-start). Anything I do in that terminal is having a problem regarding the gnome-keyring [23:43] It seems that later terminals have no trouble. So perhaps it has some connection to the order or timing of terminal vs keyring startup? So that then, even when I ssh later, I have a problem with the keyring? [23:44] Diagon, do they have differences in env variables? [23:44] checking ... [23:44] I think it's either env varibles, or just timing [23:45] They do. The orginal terminal is: SSH_AUTH_SOCK=/tmp/ssh-ILwRTLvrrqyA/agent.1832 [23:45] srw------- 1 dev dev 0 Jun 9 21:59 /tmp/ssh-ILwRTLvrrqyA/agent.1832 [23:45] Notice the different permissions from the previous one ... [23:45] srwxrwxr-x 1 dev dev 0 Jun 9 21:59 /run/user/1000/keyring/ssh [23:46] That's on the new terminal [23:46] hmmm... So the correct SSH_AUTH_SOCK is /var/user/1000/keyring/ssh ? [23:46] Yes, that one works. [23:47] Why do I have two and why different permissions? [23:47] That I don't know [23:48] Ok, one thing I"ll try on next reboot ... [23:48] But to fix your issue, maybe just manually set SSH_AUTH_SOCK in bashrc or equivalent to get your startup terminal working [23:48] Oh, ok ... [23:48] So the socket isn't created each time I boot up, it's just there and I can point to it? [23:49] (I had a thought that I could make a command: "gnome-terminal; gnome-keyring-daemon" for startup and see if that fixes the issue. [23:50] It's created by the keyring daemon, but if it always places it in the same place, then setting SSH_AUTH_SOCK manually will fix the timing issues [23:50] I see, ok. [23:51] So, this seems a bug. Let me know where I should report it? [23:51] Ubuntu or directly to gnome? [23:53] I wouldn't say its a bug. It makes sense that Terminal needs to start after your keyring to be able to use it. And it makes sense that if your terminal starts before your gnome-keyring, it'll use something else [23:54] Alright. That'll do. As long as I've got a fix (and it looks like I do)... Unless there's some other thought on this, I'll ask if you have thoughts on the "mouse trails"? [23:54] The way you'd want to set it up is to either make sure your terminal starts after your keyring, or force your terminal to use gnome-keyring, regardless if it's there or not [23:55] Diagon, nothing on mouse trails unfortunately [23:55] And I force the terminal to use gnome-keyring by setting the env var, yes? Otherwise it's using something else. [23:55] Diagon, yes [23:56] mouse-trails: that's what you said about the keyring; but you did pretty well! :) [23:56] Alright man, thanks a lot. I'll see if I can put the touch on someone else for that.... Well, maybe one more thing if you've got a minute. It's a boot up issue. [23:57] Diagon, Sure ask it, maybe I know something, maybe someone else does [23:57] When I boot up ubuntu has to unlock my disk. The password screen comes up. If I wait about 10 seconds, it will appear on my second screen that is attached to my laptop. [23:58] So, that's a long delay, but more of a problem is this: [23:58] Once I unlock the disk, the (login) password prompt comes up. [23:58] That never appears on my attached screen no long how long I wait. [23:59] Since I'd like to do all this with my laptop closed and with the laptop screen off, that's an irritation.