=== alexandr2 is now known as alexandros_c
[03:57] <Person> anyone on?
[03:57] <knome> ask your question and find out
[03:57] <Person> great
[03:57] <Person> I have kind of an unusual problem
[03:58] <Person> I set the screen resolution from the settings to a resolution not supported by my monitor
[03:58] <Person> and it's giving me a "resolution mismatch" error
[03:58] <knome> surprise :)
[03:58] <Person> I need to know how to set the screen resolution back without access to the screen
[03:58] <knome> xrandr is your friend
[03:59] <knome> 'xrandr -q' to get a list of the device names
[03:59] <knome> then i guess 'xrandr DEVICE --auto' should work
[03:59] <Person> a list is not helpful given I cannot see anything
[03:59] <knome> have you tried rebooting?
[03:59] <Person> yes
[03:59] <Person> I have
[03:59] <Person> still mismatched
[03:59] <knome> can you get to a TTY? (ctrl+alt+f1)
[04:00] <Person> I will try
[04:00] <Person> one sec
[04:01] <Person> awesome, the TTY is working
[04:01] <knome> yeah, so login with your credentials and work with the xrandr commands from there
[04:01] <knome> i'd imagine --auto should do what you want (get the optimum eg. best supported resolution)
[04:02] <Person> ok, I am going to try
[04:03] <Person> when I did xrandr -q it gave me "open display"
[04:03] <Person> However, it did not recognize that when I did xrandr DEVICE --auto
[04:03] <knome> DEVICE is a devicename
[04:03] <knome> on a laptop, it's often LVDS1 for the main screen
[04:04] <Person> ahhh
[04:04] <Person> I see
[04:04] <knome> but yeah, you might need to pass a screen name to xrandr ..
[04:04] <Person> On a desktop, how can I find what the device name is
[04:05] <knome> DVI or DVI-1 isn't a bad guess if you are using a DVI cable
[04:05] <knome> or HDMI1 for hdmi
[04:05] <Person> I'll try HDMI1
[04:05] <Unit193> Sometimes  DISPLAY=:0 xrandr -q  might work.
[04:07] <Person> I have tried what Unit193 said and it simply listed resolutions. It is not recognizing HDMI1, or HDMI
[04:07] <knome> Person, if it's listing resolutions, then see for which device name
[04:08] <knome> the device name is in the line that says "XXX connected ..." before the resolutions
[04:08] <knome> or i guess it might say disconnected in this case
[04:08] <Person> the screen seems to be cutting off anything before the resolutions
[04:09] <knome> xrandr -q | less
[04:11] <Person> uhh, I just tried that command and it just went to a black screen. I think I'm going to reboot
[04:16] <Person> does the | less command shift the screen?
[04:17] <Person> if so, does a | more command shift it in the opposite?
[04:18] <knome> they both work in a similar fashion
[04:20] <Person> | doesnt seem to be shifting my screen
[04:21] <Person> *| more
[04:21] <knome> you can also do "xrandr -q >output", which puts all of the output in the file named output
[04:22] <Person> ok
[05:48] <chuckmcm> knome do you know if anyone has tested Display port 1.2 chained screens? It kinda works on my NUC (second screen isn't stable) but I don't have a known good system to verify against
[16:50] <designbybeck> Xubuntu 16.04 works fine on a LiveUSB, and I can get on the internet via eth port. but after install, which seems to go just fine, I can't ge on eth
[16:50] <designbybeck> it doesn't even show up. This is an older Dell Inspirion 1721 AMD64 Athlonx2
[20:00] <ran> hi. in xubuntu 16.04 there is a problem with japanese letters. on many programs and the title bar they are "pushed down" a little, when they needs to be on center. (sorry about my english).
[20:37] <Sigolo> Hey
[23:03] <walkfar60> Any idea what the message playback volume 0 is already present means on boot?
=== G33kDude is now known as }{FISH}