Pixelated Fish

 Ask Ubuntu General Room

Normally: General discussion around Ask Ubuntu, Ubuntu & offic...
Jan 2, 2021 21:19
@TheXed forgot to ping
Jan 2, 2021 21:18
Dupes of what then?
Jan 2, 2021 17:36
0
Q: Should we have a canon dupe for microphone problems?

Pixelated FishRecently there have been a large number of questions related to microphones not being recognized or not working in some way, most of them liekly due to COVID-19 making people work from home. While the answer could largely vary from mic to mic and install to install, it seems to me like it would b...

Jan 2, 2021 17:23
I guess I should just ask meta actually
Jan 2, 2021 17:16
Should microphone not working questions be marked as dupes, even though they're all about different hardware? Seems to me like we should have a canonical dupe as a community wiki or something with what to do when it doesn't work
Dec 2, 2020 02:23
So as someone who has only ever used chat on imported comment discussions, what does it mean to be "in" a room, as I can apparently be "in" one without actually having it open?
 

 Raiders of the Lost Downboat

Place to sail the open sea, and search out boats to take down....
Dec 2, 2020 02:45
(questions that never got answered or accepted answers)
Dec 2, 2020 02:44
What should be done about questions regrading an old version of Ubuntu (EOLed) that may still be a useful question but only on topic for a new version?
Dec 2, 2020 02:43
So judging based on the recent meta post about this room I would think this belongs here:
 
Oct 16, 2020 20:47
What happened with the primary?
Oct 16, 2020 03:42
I gtg, I'll check back tomorrow
Oct 16, 2020 03:42
10
Q: What do the tags in `monitors.xml` do?

JeroenI have a GNOME 3 desktop environment installed on my Arch Linux box, and I would like to manually configure my desktop settings. I understand there is a file ~/.config/monitors.xml but I am quite puzzled about what the tags in the file actually do. I am particularly interested in the presenta...

Oct 16, 2020 03:42
also see here
Oct 16, 2020 03:40
the edit on the first answer
Oct 16, 2020 03:40
apparently ther's a primary tag in the xml file for each monitor
Oct 16, 2020 03:39
What's in it?
Oct 16, 2020 03:36
do you have a ~/.config/monitors.xml?
Oct 16, 2020 03:34
I think you'd have to set it to always be the primary
Oct 16, 2020 03:29
I guess try DVI as primary
Oct 16, 2020 03:28
I'm thinking it might fully activate the HDMI first, and therefore, when the startup script runs, it can't yet change the brightness, which would explain why it works in terminal.
Oct 16, 2020 03:27
maybe because HDMI is the primary?
Oct 16, 2020 03:26
I'm still thinking maybe it hasn't been fully setup
Oct 16, 2020 03:25
And that didn't work in either?
Oct 16, 2020 03:25
in a terminal? or a desktop file?
Oct 16, 2020 03:23
But I suppose your's does make more sense
Oct 16, 2020 03:23
The man page is kind of unclear. Maybe it means xrandr --output DVI-0 HDMI-0 -brightness .7?
Oct 16, 2020 03:20
So did you try xrandr --output DVI-0 --output HDMI-0 --brightness .7
Oct 16, 2020 03:19
Multiple outputs may be modified at the same time by passing multiple --output options followed immediately by their corresponding modifying options.
Oct 16, 2020 03:19
The xrandr man page says
Oct 16, 2020 03:14
What about with HDMI?
Oct 16, 2020 03:13
oh, sorry again, I just assumed -v was verbose. try --verbose
Oct 16, 2020 03:12
that one
Oct 16, 2020 03:11
What if you execute the command with -v in a terminal? Does it give any output?
Oct 16, 2020 03:08
I am so confused at this point. Down to last resorts, what happens if you remove the stuff for HDMI from the command, and put it back in Exec=
Oct 16, 2020 03:06
But you said that exact command to change the brightness will work from a console?
Oct 16, 2020 03:06
Sorry I made that take so long.
Oct 16, 2020 03:05
Ok, so the DVI monitor is connected by the time that command is run
Oct 16, 2020 03:04
They should be
Oct 16, 2020 03:03
what does /tmp/monitors say?
Oct 16, 2020 03:03
ok
Oct 16, 2020 03:03
You have execute permssions on the file?
Oct 16, 2020 03:01
Again just to be safe, put #!/bin/bash at the top of the file
Oct 16, 2020 02:59
Just to be safe, you should put the absolute path to the file instead of just test.sh
Oct 16, 2020 02:59
Sorry I haven't been working on this myself; I'm not on Ubuntu right now.
Oct 16, 2020 02:54
or, better yet, just xrandr >> /tmp/monitors
Oct 16, 2020 02:54
Alright, bad solution: try putting xrandr | grep " connected " | awk '{ print$1 }' >> /tmp/monitors into a file (/home/user/test.sh), and running chmod +x on it. Then just set the exec line to execute that file.
Oct 16, 2020 02:50
Wow... I chopped off the same single quote again. Try bash -c '$(xrandr | grep " connected " | awk '{ print$1 }')'
Oct 16, 2020 02:47
oops again. bash -c '$(xrandr | grep " connected " | awk '{ print$1 })' Sorry I'm making so many errors
Oct 16, 2020 02:44
oh, that would be because I lost a single quote. Should probably be bash -c '$(xrandr | grep " connected " | awk '{ print$1 }') >> /tmp/monitors'