[05:33] <xuxubu> morning
[08:29] <jarnos> hexchat started without menus. Any idea how to get them back?
[08:30] <cfhowlett> jarnos, close it and restart from terminal.  catch any errors
[08:33] <jarnos> cfhowlett, no messages in terminal
[08:34] <cfhowlett> jarnos, so no menus means ... it goes straight to channel?
[08:35] <jarnos> cfhowlett, it goes to autojoined channels automatically
[08:35] <cfhowlett> jarnos, right.  OK, you can rename your hexchat config file and it will default to factory fresh behavior
[08:42] <jarnos> cfhowlett, ok, I had to change a line to "gui_hide_menu = 0". I can then switch it off again in View menu, but the advertised key combo Ctrl+F9 does not work.
[08:42] <cfhowlett> jarnos, sorry, can't help you there.
[08:48] <jarnos> cfhowlett, maybe it is because Ctrl-F9 is the key shortcut for "Workspace 9" in Xfce Window Manager.
[08:49] <cfhowlett> jarnos, yes, they could very easily be in conflict
[08:54] <jarnos> cfhowlett, is that shortcut used in Xfce general or is it specific to Xubuntu?
[08:55] <cfhowlett> well, it should be specific to xfce I would think
[08:55] <cfhowlett> but changeable
[08:56] <jarnos> cfhowlett, so which package should the bug report be done against?
[08:57] <cfhowlett> jarnos, well, is that really a bug, though?
[08:57] <cfhowlett> xfce did what xfce does.  sadly, hexchat used the came keybinding
[09:05] <jarnos> cfhowlett, sadly I can not report a bug against hexchat now. (Timeout error in Launchpad)
[09:56] <Furkiepurkie> I got the minimal version of xubuntu but I'm missing the printing options. Google tells me I need xfprint but I'm unable to locate that package
[10:12] <jarnos> Furkiepurkie, what is minimal version of Xubuntu?
[10:13] <Furkiepurkie> jarnos: https://xubuntu.org/news/introducing-xubuntu-core/
[10:18] <jarnos> Furkiepurkie, would installing system-config-printer-gnome and using system-config-printer to configure?
[10:18] <jarnos> do
[10:27] <Furkiepurkie> I'll try that
[10:32] <Furkiepurkie> nice, works perfectly
[10:32] <Furkiepurkie> thanks jarnos
[10:34] <czwolf> Hello still solving this situation - 3 scripts. I may not be able to do it without a simple example, please look:
[10:34] <czwolf> A) terminal.sh starts a xfce4-terminal window. I want to start the execution of
[10:34] <czwolf> B) myscript.sh in that terminal window any later. (Can be simple or complicated, e. g. just: echo test in it. It will end or crash.)
[10:34] <czwolf> C) starter.sh is my 3rd script which triggers the execution of myscript.sh
[10:34] <czwolf> What I need: 1. terminal window will NOT close & 2. terminal will keeps accepting inputs from starter.sh. Possible, how?
[10:41] <knome> 'xfce4-terminal -H' keeps the terminal open even after the child process has ended
[10:42] <knome> i don't understand why you are complicating this with three scripts
[10:42] <knome> why do you need starter.sh?
[10:45] <czwolf> knome yes but the original terminal will do nothing more. Starter.sh is triggered by some monitor, but that is another story. That monitor keeps an eye on a running process. Yes, it is the code run by myscript.sh and it is a mono application. So what I am presenting is the most simplified scenario, because I need all 3.
[10:47] <knome> ok, so you want to have two terminals open, right?
[10:47] <knome> the other runs myscript.sh, and if the script ends or crashes, you want to keep that terminal window opwn
[10:47] <knome> *open
[10:47] <knome> and the other terminal does what?
[10:48] <knome> you run starter.sh in it?
[10:49] <knome> for the terminal that runs myscript, just run 'xfce4-terminal -H -x myscript.sh'
[10:49] <knome> you don't need another script to run the terminal
[10:49] <czwolf> knome One is enough. But when the process in it stops or fails, I would like to open in the same window a new process by that 3rd script. What happens now is when I come to pc I see empty console with crashed program and a new console I know nothing about how it performed. So the idea is I would scrooll the console simply and see how many times it crashed, what were the reasons and how many times it was restarted. Cos I have more such consoles would be
[10:49] <czwolf> nice to see that in one window
[10:49] <knome> ok... the -H parameter lets you do that
[10:50] <knome> is the idea of starter.sh to simply run myscript.sh again when it ends or crashes?
[10:50] <knome> eg. you want to loop running myscript.sh?
[10:52] <czwolf> knome that is solved. myscript.sh is being monitored and restarted. But not in the same console. if I want it in the same console and keep all outputs in front of my eyes I must be present when it crashes and start it there manually. Otherwise it statrs in a new console which, after being killed or crashes, leaves without trace. The program may need to be killed when it gets irresponsible so that my watchdog also does
[10:52] <czwolf> So the whole idea is to alter my manual input by script input
[10:53] <czwolf> script which represents my hands should be starter.sh
[10:54] <czwolf> So that one console I would like to see always running
[10:54] <knome> so what you basically want is to run myscript.sh on the same terminal even after it crashed?
[10:54] <czwolf> the terminal did not crash, the code in it yes
[10:54] <knome> yes, the script.
[10:54] <czwolf> mono application in that console sometimes crashes yes
[10:56] <knome> it sounds like you want a while loop in starter.sh
[10:57] <czwolf> well what it does now is this:
[10:58] <czwolf> mono /home/user/path/app/bin/OpenSim.exe
[10:58] <czwolf> that is all
[10:58] <czwolf> It opens new window
[10:58] <czwolf> when it crashes, it again opens new window .... etc.
[11:00] <knome> ok, so you need to figure out how to run a mono application in the same terminal you run it from.
[11:00] <czwolf> exactly
[11:00] <czwolf> I can do it manually but not by a script - I do not know how
[11:00] <knome> how do you do it manually then?
[11:01] <czwolf> I can only type it by my fingers into that console. (I can do it before my starter.sh notices that the program does not run)
[11:02] <knome> so it's the exact same command you run?
[11:02] <czwolf> yes, in ideal case it would be the same comand
[11:02] <czwolf> now scripts starts new
[11:02] <knome> i'm not talking ideal; which command are you typing when you run the script manually?
[11:03] <czwolf> mono /home/user/path/app/bin/OpenSim.exe
[11:03] <knome> do you compile the exe yourself?
[11:04] <czwolf> no it is opensimserver
[11:04] <czwolf> so manually I start directly that mono exe file
[11:05] <knome> i would look in the mono documentation
[11:06] <knome> but what you really want is this:
[11:06] <czwolf> Well, you think I can find there info how to start a process in a sconsole with a given name?
[11:06] <knome> when you run the terminal that starts your script, simply run:
[11:06] <knome> xfce4-terminal -H -x starter.sh
[11:06] <knome> in starter.sh, you want this:
[11:06] <knome> while true; do
[11:06] <knome>   # run script here
[11:06] <knome> done
[11:07] <knome> you need to read the mono documentation; mono starts the new terminal
[11:07] <czwolf> Oh that may do the thing knome - that run script here = which script?
[11:08] <knome> myscript.sh, or to be exact, just put the mono line there.
[11:08] <czwolf> mono /home/user/path/app/bin/OpenSim.exe
[11:08] <czwolf> this
[11:08] <knome> considering myscript.sh doesn't have anything else than that line
[11:08] <knome> yes, that
[11:08] <czwolf> oh ... OK knome, that may solve my months of searching :) Looking if it will do. Ty
[11:09] <knome> (and see, you actually only need one script, not three...)
[11:31] <czwolf> knome this generates "syntax error: inexpected end of file" The content of the file is just as you said: while true; do
[11:31] <czwolf> run mono /home/user/path/app/bin/OpenSim.exe
[11:32] <knome> why "run"?
[11:32] <knome> and you are missing the last line; "done"
[11:33] <knome> (without the quotes)
[11:33] <czwolf> oh ok, changing that, I thought I need to copy it whole
[11:33] <knome> nope. just as you would run it in a terminal
[13:49] <ircnode0> Where is default audios files in Xubuntu system?
[13:49] <ircnode0> I tried to find mp3 from the root, but couldn't find any.
[13:51] <ircnode0> Nevermind, found two ogg-files in Xubuntu.
[14:37] <babs> hello I was wondering if I'm the only one having an issue with a non matching icon size on the elementary-xfce theme ?
[14:39] <babs> specificly the gtk-disconnect.png in 32x32
[15:14] <DrunkenDwarf> Hi all. The live USB for "Try Xubuntu" is formatted for testing the system, is there an easy way to get a standard install of Xubuntu (without installer and Grub "try" menu) on to a bootable usb?
[16:10] <xubuntu36w> hola? :c
[19:33] <leta> Hi all!
[19:33] <knome> hello
[19:34] <leta> I am running Xubuntu 16.04.1 and couple of things are bothering me...
[19:35] <leta> First, connecting to hidden networks does not work. I have to delete it and then create it to connect again.
[19:35] <leta> Second, how can I turn off bluetooth by default?
[19:53] <leta> Anyone???
[19:55] <Furkiepurkie> leta: bluetooth off
[19:55] <Furkiepurkie> although I dont know if it makes it default as well, but I think it does
[19:55] <leta> Nope, it does not..
[19:55] <leta> Every time I turn the computer on, the bluetooth is on...
[20:15] <knob> leta, did you google?    I remember same BT thing happening to me, and I quickly found the answer on how to turn it off on every restart.
[20:16] <leta> What I found was disabling the whole bt module
[20:16] <leta> In that case I could not easily enable it when I need it...
[20:16] <leta> I will google it tomorrow.
[20:16] <leta> Any ideas for WiFi?
[20:17] <ondondil> leta: Maybe turning blueman off by default will help? https://wiki.archlinux.org/index.php/Blueman#Configuration
[20:17] <ondondil> Don't mind me if I'm wrong. I'm just a casual user ;)