=== wook is now known as Guest66984 === ubott2 is now known as ubottu [16:56] Hy, kann jemand deutsch hier? :D [16:58] can anyone help me? i had update to 15.xx from 14.xx now is the display max. 1024x786, but i need 1680x1050. [16:59] i doesn't found anyway :( about the terminal or about the nvidia x-server [17:18] Snap4x: what did you update from? [17:18] 14.10? to 15.04? [17:18] ja [17:18] what i would do is simply check the driver i am using, and try the proprietary driver [17:18] re-install it, if necessary [17:19] which? [17:19] btw how? [17:19] Snap4x: the one that fits your needs.. likely the nvidia one [17:19] :D [17:19] Snap4x: i use a package manager to do so [17:19] Snap4x: there is a GUI for checking which proprietary drivers are in use === wook is now known as Guest50446 === SonikkuAmerica is now known as Guest82178 === Guest82178 is now known as littlebunnyfufu === littlebunnyfufu is now known as SonikkuAmerica [18:39] avconv is great, it's just so poorly documented compared to ffmpeg.... [18:40] oh... i was scrolled way up sorry.. [18:41] i'm going crazy with ssh-add and gnome-keyring thing... [18:41] i made some temporary keys to learn, but now i can't find how to get rid of them.... gnome keyring loads them, but i don't know where from.. [18:42] ssh-add just wont remove them.. [18:42] i find dozens od threads in launchpad, as old as 2010... [18:43] but non of the "sollution" is clearly explained, they all link to threads that have a sollution in post with a link to another threads post links.. [18:45] and so forth... [18:47] sakrecoer_Z: anything like that, can be taken care of with the normal ubuntu documentation [18:47] thanks holstein, what and where is "normal" ubuntu doc? :) [18:47] http://askubuntu.com/questions/20865/is-it-possible-to-remove-a-particular-host-key-from-sshs-known-hosts-file [18:47] https://help.ubuntu.com/community/SSH/OpenSSH/Keys [18:48] im just saying, there is no "ubuntustudio ssh key" situation.. since, ubuntustudio is ubuntu [18:48] ah... ok.. yeah sorry [18:48] well that ask page i have read already, its not my case... [18:49] i'm trying to remove the old keypair from my computer... [18:49] local computer [18:49] sure. you locate the key you want to remove, and you can remove it [18:49] moved the file [18:49] i usualy just do it manually [18:49] sorry... how [18:49] ssh-add -d [18:49] sakrecoer_Z: i literally used a text editor.. [18:49] but then when i do ssh-add -l it is still there.. [18:49] but, im sure there are other more elegant ways.. [18:50] you don't understand my situation... [18:50] let me find a link that explains it.. [18:50] :) [18:50] sakrecoer_Z: cool.. feel free and elaborate for a volutneer here [18:50] sakrecoer_Z: or, you can also use #ubuntu since its not related to ubuntustudio specifically [18:50] or, maybe the server channel. [18:50] !server [18:50] Ubuntu Server Edition is a release of Ubuntu designed especially for server environments, including a server specific !kernel and no !GUI. The install CD contains many server applications. Current !LTS version is !Trusty (Trusty Tahr 14.04) - More info: http://www.ubuntu.com/products/whatisubuntu/serveredition - Guide: https://help.ubuntu.com/lts/serverguide - Support in #ubuntu-server [18:50] though, i think it can be slow as well.. [18:50] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472477 [18:51] Debian bug 472477 in gnome-keyring "ssh-add -D does not remove SSH key from gnome-keyring-daemon memory" [Important,Open] [18:51] and then this one: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/505278 [18:51] Launchpad bug 505278 in gnome-keyring (Ubuntu) "ssh-add -D deleting all identities does not work. Also, why are all identities auto-added?" [Low,Confirmed] [18:52] some people seem to find a sollution in that thread, i'm.... well barely hairless :D [18:53] i'll try in #ubuntu :) sorry i didn't understand you first holstein, ty for assisting me [18:54] For those that are winding up at this bug report from searches looking to resolve the problem - regardless of platform, here's a quick "fix": [18:54] * Move the keys out of ~/.ssh * gnome-keyring-daemon -r -d [18:54] It's certainly not an actual fix, but will at least resolve the immediate annoyance. [18:54] sakrecoer_Z: otherwise, i dont personally use gnome-keyring, so, i cant give you any first hand advice.. i konw, i have used ssh keys, and added and removed them, and had no issues [18:55] well.... i never used it either... i have no idea how my keys eneded up tehre... [18:55] the keys are not likely there.. but, referenced there [18:55] you can look and see.. [18:55] i moved the keys out of ~/.ssh [18:56] gnome-keyring-daemon -r -d gave me no result. [18:56] ah.. #26 is relevant. its not a bug, its a feature [18:56] rebooted... still nothing.. [18:56] https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1271591 [18:56] Launchpad bug 1271591 in gnome-keyring (Ubuntu Trusty) "upstart job race prevents gnome-keyring from being ssh agent" [High,Fix released] [18:56] i don't get it... the keys are fare away from my system, but ssh-add -l claims to still have a copy.. [18:56] sakrecoer_Z: are you up to date with updates? [18:57] what operating system are you using? [18:57] yes i think i'm up to date... [18:57] ubuntustudio 14.04.3 [18:57] in a terminal "sudo apt-get update && sudo apt-get dist-upgrade" will tell you [18:57] holstein: yeah... but.... i want to be on LTS... [18:58] maybe its not a good idea... [18:58] to be on LTS... [18:58] sakrecoer_Z: sure.. *stay* on the LTS, running, in the terminal, the command i gave, after researching it, and discovering that it *does* not upgrade you from the LTS [18:58] now i'm confused... [18:58] you remain on the LTS, but, you can *know* that you are up to date with upgrades [18:58] hehe [18:59] sakrecoer_Z: please, open a terminal, and run "sudo apt-get update && sudo apt-get dist-upgrade" which *does* *not* upgrade you from the LTS version you are running [18:59] ok [19:00] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [19:01] right. so, no upgrades will "fix" that [19:01] and, i havent personaly had that issue [19:01] so, maybe, since, you are not wantinng to use that gnome-keyring, you can simply stop using it [19:01] not sure.. [19:02] i would try upstream at #xubuntu or #ubuntu since we really dont deal with the plumbing on that, AFAIK [19:02] could be, a fix that didnt get specifically applied to ubuntustudio and i wouldnt know [19:02] ok. :) thank you for your precious time anyway holstein === sakrecoer_Z is now known as sakrecoer [19:10] hehe... bad timing i guess... #ubuntu is flooded with support requests. hehe [19:12] i would look in the config, and see if i can blow it out [19:12] i would look into not using the keyring, since, you seem to not want it [19:12] might mess up other things, though.. [19:12] i don't even know why it is in use haha [19:13] i would elaborate about what is not working from that "fix" in the post [19:13] i don't remember ever putting my keys there, i sure did add it to ssh-add [19:13] gnome-keyring-daemon -r -d [19:13] could be, its *not* the gnome keyring doing it.. [19:14] well.... ssh-add tells me it is using the key ~/.ssh/id_rsa but there is no sych file on my system ATM [19:15] and as for the "fix" in the post,,,, i can't even identify it, even less how it works... [19:15] whats the issue? [19:15] you added a key? and now you want to remove it? and its a "test key"? [19:16] i mean, if you just started learning about keys, maybe just leave it there.. and deal with it later.. try doing tests from VM, or, live iso's.. [19:16] there is a ghost key in my system... a key that is supposed to be gone, is not gone... [19:16] sakrecoer: its not a "ghost key", though, is it? i mean, you put it there, correct? [19:16] you are just trying to remove a key that you made, as a test, correct? [19:16] yes [19:17] well.... i tryed to remove it because it didn't work [19:18] first time it did... after i add it with ssh-add [19:18] but eversince, when i would try to invoke it, there would be a winodw poping up asking for the passphrase, but then i would have to use passwrod anywya.. [19:20] if its an ssh key with a passphrase, thats the way its supposed to work [19:21] yeah.. but... once you have given the passphrase to your key, the server to which you just uploaded the public key should NOT ask you for a passphrase... [19:21] and the server would ask me for passphrase.. [19:21] not the one of my key so to speak [19:23] sakrecoer: sounds normal.. if you have not "unlocked" the keyring [19:23] i have had that, in the past, when joining wifi networks.. [19:24] no.... thats not whats ahppening.. [19:24] i HAVE unlocked the keyring,... but it wouldn't do anything. [19:25] thats why i wanted to remove the keys... they didn't work like they should... [19:25] the problem is, i cant remove them [19:25] i can still unlock the keyring [19:25] but the keys are useless even tho they are in my servers ~/.ssh/authorized_keys [19:26] and i tried on 3 different servers... [19:26] sure [19:26] i say, stop trying like that, so randomly [19:26] since, its obiously more on the client end.. [19:26] i say, setup a scenario in VM, or, on a few local machines.. so you control the variables, and can work with the setup, and learn what you are missing [19:32] thank you holstein ... i'm sure it s a good idea. i just don't really know how to apply it. But don't worry i will eventualy find out... === sakrecoer is now known as sakreBlEU === sakreBlEU is now known as sakreBlEUZ === sakreBlEUZ is now known as sakreBlEU_Z === sakreBlEU_Z is now known as sakrecoer [20:37] ok... something is wrong with my client. i can't reproduce the problem. [20:38] ... reproduce it on another client [20:39] well, that sounds like a data point, to me [20:39] ssh-add has no identity until i add it. i was thinking that it was gigolo that messed up soemting for me, but it wont mess up anything on this one.. [20:39] when i remove identity it's gone liek it should [20:39] even if i use a gigolo bookmark... [20:40] so, something is broke in the other one. [20:40] yeah. gigolo shouldnt affect.. agreed [20:41] it's like the broken client started useing a diffrerent keymanager... the prompt gigolo presnts me is different on the broke client. [20:41] well, is anything "broken"? [20:41] except from that, no... [20:41] whats the difference in the machines? [20:41] i mean... not as far as i can see. [20:42] when i boot the broken, there is already an Identity attached to ssh-add [20:42] i think, i would just reset the keyring config, and, if all is well, not worry with it [20:42] but how do i reset the keyring config? i can't find it [20:43] in my startup-task gnome key-ring is not activated, but the deamion is there on ps aux [20:43] do you have a .local/share/keyrings ? [20:44] yes!!! [20:44] haha [20:44] i wouldnt just delete things.. either [20:44] i would just rename, or move.. and test.. [20:45] let me try that on the broken client.... and i'll brb... :) [20:48] hm... there are no default file on the broken client.. [20:49] moved the ~/.local/shared/keyring/ but the id is still in ssh-add --- [20:53] where is it stored (i did reboot) [20:56] on both clients both with latest upgrades, i have to different dialogs when the GUI asks med to unlock my key [20:56] one is entitled "pinentry" and ask me t unlock key with fingerprint "bl:ab:la:bla" in ~/.ssh/id_rsa (which is not present) [20:58] the other is entitled "unlock private key" and says apllication want s acces to private key "foo@domain" [20:58] gah... sorry holstein never mind, i thinking out loud. I really appreciate the little directions you could give me anyhow [21:00] oh... but i remember ticking that box: "automaticaly unlock this key whenever i'm logged in" [21:00] on the broken client... [21:02] right.. so, you can reset those settings, ideally [21:03] its probably just a simple config that you have agreed to somewhere along the way, that is doing something not expected [21:03] but, is it really breaking anything? [21:03] i mean, if its a test server, i say, just dont use it, anymore.. and, its not a security issue [21:04] its not like, its allowing access back into your machine from somewhere, and you are tyring to block it [21:04] then, as you get more familiar with the tools, i bet, you can knock it out, no problem [21:04] the problem is not the server. the prbolem is that these keys are stuck in my main machine... [21:04] right [21:04] but, the keys to what, friend? [21:05] a test server? that really doenst break anything for you? [21:05] something you can easily just ignore for a bit? [21:05] i mean sure, i cane remove the oublic key from my servers "authorized_keys".... but i'm still stuck with this identity on this box... [21:05] sure..and, is that a problem? [21:05] well... if i have to use keys at all, i wish i would know where they are stored, so that i can replace them if i have to... [21:06] sakrecoer: sure, but, do you really need to learn all that right now? [21:06] i don't know, it's kindof step 3 in the "set up dev environement"... [21:06] sakrecoer: where? === wook is now known as Guest93845 [21:07] here https://wiki.ubuntu.com/UbuntuStudio/SetupDeveloperEnvironment [21:08] and that is the step that is "broken" for you? [21:08] ye.. [21:08] creating that key still doesnt break anything, if an older one is around.. [21:09] those are quite different than the ssh keys we have been talking about [21:10] ok.. make it a point 4. i'm not strugling with gpg keys [21:10] but, whats the point? [21:10] ssh keys are just for you to have access to a server, if you need [21:10] you dont *have* to have that to help with development [21:11] if you need one, you can generate one. if you have one that you are trying to remove, and cant, its not posing a security threat [21:11] i realize, i deally, you want to understant the system.. and all i can say is, its always been as it is on the other machine for me. or, i just dont use the keyring tools like that [21:19] it's fine holstein, i'm not expecting you nor anyonw to be able to solve everything... but, maybe there should be another wiki page for n00b-devs like me... [21:19] sure.. start what you like [21:19] but, its just not needed.. the ssh key doesnt do any development [21:20] andm, if you are just learning, its not going to hurt anything to just give yourself some time, to see what has happened [21:20] ssh keys are handy if you are using them to connect to a server.. is that what you are doing? [21:23] yes i watned to connect to a server using those test keys. it works on one machine on the other, not.. but sure, who cares? just a bunch of useless keys. it would still have been nice to find out where they get stored on my system... [21:23] well, are they useless? [21:24] what i did was, i setup environments locally, and created keys, and tested.. in an environment where i have complete control of the network [21:24] otherwise, what about development are you not able to do? [21:24] well, for the sake of anyother person than me, at the moment,, absolutely useless... [21:31] holstein: otherwise, what i am not able to understand about devlopement is where to start. [21:31] sakrecoer: what are you trying to develop? [21:33] worldpeace? no ... ok...first i go eat something, then i will try to find an answer to that question........ [21:40] much better... :) [21:41] im not sure what i want to develop holstein, because i'm not sure what i can devlop. I'm trying to catch up with you guys and its super hard. [21:41] im not a developer, like that [21:41] i dont plan to be [21:42] but, you can do that, for sure.. but, as you know, you dont need ssh keys to develop.. thats just to connect [21:42] i suppose, all im saying is, if you want to develop something, lets talk about that, and not get too sidetracked here about ssh key management [21:43] you are so wise holstein. and a kickass supporter. [21:43] im not sure what has happened on one of your machines, but, im sure, its something that, if you give yourself time, you'll be able to sort it out. and you are not breaking anyting, or causing a problem with security,or preventing any development [21:43] sakrecoer: well, thanks.. i hope i can point you in the right direction.. [21:44] you see, that is the thing about this new dev dimesnio for me, i can't seem to find where things are going [21:44] to get someone to point me to a direction, i need to know where to go [21:44] sure.. but, keep in mind, one thing nice about linux is, noting is hiding from you [21:45] hehe.. when you know whre eot find them :) [21:46] well, ubuntu is not a distro that is really about that, necssarily.. its not a distro that says "come, and kick the tires.. customize and enjoy the open-ness".. [21:47] it *is* open.. but, it also has a lot of sane-defaults that are arguably forced on the user [21:47] but, those are what makes things "just work" too.. [21:51] yes. and they do just work in the box actualy. At least for me, most of the time. Especialy when it comes to its purpose. But the "software" to recruit freshmen like me, is pretty shitty :D [21:51] the software? [21:51] * sakrecoer missunderstands itself left [21:52] *all* of linux is completely open.. if *anyone* wants to release any software for linux, they can [21:52] if they dont, we cant make them.. [21:52] yes, i mean, the infrastucture is super chaotic to even grasp. [21:53] is it? [21:54] maybe i'm just not good at it... its frankly speaking a possible parameter. But yes. [21:55] you are not good at grasping the infrastructure? its a lot to take on [21:55] exaclty. there is so much to take on.... [21:55] what are you coming from? likely nothing on the scale of what we are talking about.. its a lot to think about.. developing for the entire OS.. all open.. etc [22:05] * sakrecoer is lost in translations :D [22:05] bottom line is like you wrote: 'lets not get sidetracked by SSH keys' [22:13] thanks for precious time holstein see you! [22:15] sakrecoer: cheers.. === sakrecoer is now known as SakreZZz