milind 2017-01-31 16:46:05
Noob here. Is this the right channel to ask for support re display resolutions?
hattrick99 2017-01-31 16:46:34
milind its better to just ask your question and see if anyone has any ideas.
darkhack 2017-01-31 16:46:40
what the best server os Debian or Ubuntu?
hiexpo 2017-01-31 16:46:58
!best
milind 2017-01-31 16:47:09
My PC is an Ubuntu 16.10/Win 10 dual boot machine.
milind 2017-01-31 16:47:10
Processor:Intel® Core™2 Duo CPU E7400 @ 2.80GHz × 2
milind 2017-01-31 16:47:12
Graphics: Intel® G33
milind 2017-01-31 16:47:13
2GB Ram
milind 2017-01-31 16:47:15
A few days ago the display started turning weird shades of green, though I could still use the computer. The VGA cable seemed to be loose & at fault, so I changed it. After changing, though the colours were back to normal, in both Ubuntu & Windows 10 the maximum resolution shown was 1024*768 @60 Hz, though the Dell LCD monitor's maximum is 1600*900 @60 Hz. In Windows, I could find the higher...
cfhowlett 2017-01-31 16:47:16
darkhack, are you trolling us?
milind 2017-01-31 16:47:16
...settings in Advanced Display Settings and get things back to normal. But Ubuntu Settings do not show any resolutions except 800*600, & 1024*768. How can I get the higher resolutions back?
xangua 2017-01-31 16:47:31
darkhack: for asking support in the #Ubuntu channel? Ubuntu
rmviewer 2017-01-31 16:47:37
@darkhack the one that meets your needs. I'm not trying to be combative. It's really personal preference.
pc_ 2017-01-31 16:48:21
any experts on different distros? please pm me. thanks.
xangua 2017-01-31 16:48:42
pc_: you want ##linux
pc_ 2017-01-31 16:48:48
Thank you
_28_ria 2017-01-31 16:49:31
milind: I am not very pro about it, but command line utility xandr should be able to dig into display guts
rmviewer 2017-01-31 16:49:46
wedgie: everything looks legit on the connection attempt. Box 1 connects, matches the known host key. The only auth method that can continue is publickey. The server has no public keys so that fails. I don't see any attempt to use ssh-agent in the output. Should there be?
milind 2017-01-31 16:50:28
_28_ria: Thanks.Will check that.
wedgie 2017-01-31 16:51:02
rmviewer: ... is that on the connection that is working or the connection that is not?
rmviewer 2017-01-31 16:52:32
wedgie: that's the connection that's not working. I'm currently ssh'ed into Box 1. I can't use that ssh session to get into Box 2.
wedgie 2017-01-31 16:53:14
rmviewer: if the server has not public keys.... I must be misunderstanding something
hattrick99 2017-01-31 16:55:41
rmviewer really sounds like you need agent forwarding on.
rmviewer 2017-01-31 16:56:03
wedgie: both server have the same authorized_keys list. The entire point of this is that I only opened up a single port on my home network which goes to box 1. I used to use that ssh session to then do "ssh user@192.168.1.222" in order to use my open session to get into multiple boxes at home. For some reason this stopped working recently. Neit
rmviewer 2017-01-31 16:56:04
her server has any id_rsa file.
hattrick99 2017-01-31 16:56:08
you have your keys on your local computer, yes? and no keys on server 1, and want to go local -> server 1 -> server 2
rmviewer 2017-01-31 16:56:58
hattrick99: correct. Used to work. Stopped working recently without any change from me. I've been doing it for over a year.
wedgie 2017-01-31 16:57:08
rmviewer: given that it should work with agent forwarding (-A). You aren't using screen or tmux, are you?
rmviewer 2017-01-31 16:57:12
I guess I could just open up multiple ports, but it still doesn't explain why it stopped working.
wedgie 2017-01-31 16:57:25
cause if you are that will mess with the agent forwarding
rmviewer 2017-01-31 16:58:15
No, just a normal session.
rmviewer 2017-01-31 16:58:36
I'm wondering if something auto-updated.
wedgie 2017-01-31 16:58:57
rmviewer: out of curiosity, what happens if you do this: ssh -A -L 2222:box2ip:22 box1user@box1 and then from another terminal (on the local machine) ssh -p 2222 box2user@localhost
hattrick99 2017-01-31 16:59:50
or just ssh -A box1 then ssh box2 from box1
pc_ 2017-01-31 16:59:57
no response there, is there an ubuntu free talk room?
wedgie 2017-01-31 17:00:02
hattrick99: that's what he'e been trying
wedgie 2017-01-31 17:00:09
!ot
ubottu 2017-01-31 17:00:09
#ubuntu is the Ubuntu support channel, for all Ubuntu-related support questions. Please register with NickServ (see /msg ubottu !register) and use #ubuntu-offtopic for other topics (though our !guidelines apply there too). Thanks!
pc_ 2017-01-31 17:00:56
unable to join the other channel.
wedgie 2017-01-31 17:01:10
!register
ubottu 2017-01-31 17:01:11
For information on registering your IRC nick, see https://help.ubuntu.com/community/InternetRelayChat/Registration - For any further help, ask in #freenode.
pc_ 2017-01-31 17:01:33
Thanks
rmviewer 2017-01-31 17:04:09
wedgie: ssh: connect to host 192.168.1.106 port 2222: Connection refused
wedgie 2017-01-31 17:04:57
rmviewer: that was ssh -p 2222 localhost (note that localhost should be taken literally here, not substituted)
wedgie 2017-01-31 17:05:30
only with the first connection already opened
_28_ria 2017-01-31 17:06:11
milind: I've made a typo. It's xrandr, not xandr.
rmviewer 2017-01-31 17:07:02
wedgie: Yeah, oops. Same public key error: Permission denied (publickey).
rmviewer 2017-01-31 17:07:30
I would have expected the same. I'm guessing that ssh-agent is messed up on Box 1
rmviewer 2017-01-31 17:07:37
Or not auto starting
wedgie 2017-01-31 17:08:28
rmviewer: add the key manually with ssh-add
wedgie 2017-01-31 17:08:38
ssh-add .ssh/id_rsa
wedgie 2017-01-31 17:09:00
but i assume that you use the key to log into box1, so that probably isn't it
rmviewer 2017-01-31 17:11:44
wedgie: yes, same key on both. The sane thing to do is to just open another port directly to Box 2.
hattrick99 2017-01-31 17:12:26
is box 2 up?
rmviewer 2017-01-31 17:12:53
hattrick99: yeah, I can ssh into it directly right now. Just not from Box 1 anymore.
wedgie 2017-01-31 17:14:09
rmviewer: very odd. Something must be up with the agent forwarding. Not sure what to suggest beyond that
rmviewer 2017-01-31 17:15:51
wedgie: thanks for the suggestions. That's all I can come up with too. I don't know what could have happened to the automatic agent forwarding, but it's obviously not working anymore. At least I have a very solid workaround.
rmviewer 2017-01-31 17:21:53
It's definitely messed up. 'ssh-add -k' followed by 'ssh-add -l' shows the agent has no identities