[00:23] <ball> If the installer doesn't offer me sda and I know the disk is good, is it likely there's a mainboard problem (SATA port etc.)?  I haven't tried a different SATA cable yet.
[03:09] <silkairways> Hello is anyone in at the moment?
[03:11] <ball> Yes.
[03:12] <ball> Sort of.
[03:12] <silkairways> I had a question
[03:12]  * ball waits for the question
[03:13] <silkairways> When i click save session and shut down.  I turn back on and only the web browser comes back open
[03:13] <silkairways> Other apps do not re open upon restart with saved session
[03:13] <silkairways> Is that normal?
[03:13]  * ball shrugs
[03:14] <silkairways> Normal?
[03:15] <ball> No idea.  I don't run Xubuntu.  I could test it on my daughter's PC.
[03:15] <ball> I did actually try installing Xubuntu today but it didn't work.
[03:15] <ball> (probably because of a hardware issue)
[03:16] <silkairways> Oh it was on ubuntu studio they said ppl here might know
[03:16] <ball> They're right.
[03:16] <ball> Other people though.
[03:17] <Unit193> I too do not use that feature, but you could possibly try clearing out old sessions and see if saving a new one helps.
[03:18] <Eickmeyer> silkairways: See https://paste.ubuntu.com/p/dzZcRF7dWQ/
[03:18] <Eickmeyer> We talked about it a bit after you left.
[03:20] <ball> Trying it again now...
[03:29] <silkairways> Okay cool thank you Eickmeyer
[03:30] <silkairways> I will check that out
[03:30] <silkairways> Is it safe to say the feature should be opening all the open programs upon reboot?
[03:30] <Eickmeyer> That I couldn't tell you.
[03:31] <ball> I might try I may try Dingo instead.  Perhaps that's what I did wrong.
[03:32] <silkairways> Anybody know how i could find the sessions to clear?
[03:33] <silkairways> Sorry ball im not sure what dingo is.  Part of the xubuntu install?
[03:34] <silkairways> I found it under setting sessions and startup
[03:35] <silkairways> I think this will clear up my issues. I thought it worked autonomously but as with everything linux it has a bunch of awesome features and settings of its own
[03:36] <Eickmeyer> silkairways: dingo (disco dingo) was the codename for 18.04.
[03:36] <ball> Eickmeyer: I thought that was 19.04?
[03:36] <silkairways> Oh right! Disco dingo
[03:36] <silkairways> That's what is installed on my hdd
[03:36] <Eickmeyer> ball: Typo. :P
[03:36] <ball> Eickmeyer: Those happen.
[03:37] <ball> Eickmeyer: ...just wanted to make sure I wasn't downloading something older than LTS
[03:37] <Eickmeyer> Usually we refer to the codename by the first part if being short. So, you'll hear Disco referred to more than Dingo.
[03:37] <ball> Sorry.  I'm not really a Linux person so I guessed. ;-)
[03:38] <silkairways> I thin 19.04 is disco dingo 18.10 cosmic cuttlefish 18.4 bionic beaver
[03:39] <Eickmeyer> That's correct, silkairways.
[03:39] <silkairways> I have bionic beaver on my hdd and disco dingo on my usb stick for my side business
[03:40] <ball> I'm downloading Disco Dingo now
[03:40] <ball> Didn't have any luck with Bionic Beaver.
[03:41] <silkairways> Where are you trying to install? In a vm? On a hdd?
[03:44] <ball> On a hard disk.
[03:44] <ball> On an i3 desktop
[03:45] <ball> ...for reasons ;-)
[03:47] <silkairways> Oh i see
[03:47] <ball> The installer boots but it can't see the hard disk to install to.
[03:47] <silkairways> I have 18.04 on an embarrassingly old laptop with the processor is probably much worse
[03:48] <silkairways> It have the machine new life and now it is my security cameras server
[03:48] <silkairways> *gave
[03:48] <silkairways> I hate this keyboard
[03:49] <ball> IP cameras?
[03:50] <ball> Perhaps I'm supposed to run some sort of partitioning tool prior to installation but ...I don't know
[03:50] <silkairways> Yes ip cameras
[03:52] <silkairways> Oh wow my processor actually comes out ahead vs i3 3217U on cpuboss.com
[03:55] <ball> Not sure that's a reliable site.  The folks in ##hardware would know.
[04:05] <silkairways> It's not very important
[04:06] <silkairways> Just surprised they even comparable
[04:08] <silkairways> And for my saved session questions those programs i was looking for are not in the list available to save the session so i will try to just add them to startup
[04:17] <silkairways> Gtg c y'all later
[04:18] <ball> Goodnight silkairways
[04:18] <silkairways> Goodnight ball
[04:20] <ball> Goodnight everyone!
[04:51] <ball> Well, I should have gone to bed but I didn't.
[04:52] <ball> ...and 19.04 is doing the same thing that 18.04 did (not offering sda as an installation target)
[04:56] <diogenes_> ball, what you trying to do?
[04:56] <ball> diogenes_: Install Xubuntu
[04:56] <ball> (onto a blank disk)
[04:57] <diogenes_> do you have multiple hdds?
[04:57] <ball> diogenes_: Not on this machine.
[04:59] <diogenes_> ball, new hdd? how old is it?
[05:00] <ball> Tested HD.  Under three years old.  Passes SMART and other tests.
[05:01] <diogenes_> tried to start with a new partition table in gparted?
[05:02] <diogenes_> pick gpt for efi
[05:02] <diogenes_> msdos for mbr
[05:03] <ball> diogenes_: I haven't seen that offered by the installer.  I suppose I could boot to the live image and look for it there.
[05:05] <ball> Shouldn't the installer be able to handle a blank disk though?
[05:06] <diogenes_> ball, try with gparted.
[05:06]  * ball lookds for it.
[05:07] <Unit193> `lsblk` find it, I presume?
[05:07] <diogenes_> ?
[05:13] <ball> diogenes_: That worked, though it called MBR "msdos"
[05:13] <ball> ...which is stupid.
[05:13] <ball> ...and didn't offer to create a partition in the installer.
[05:14] <diogenes_> ball, so everything's fine now?
[05:15] <ball> Appears so.
[05:15] <ball> We'll see whether it's bootable once the installation completes.
[05:16] <ball> Looks like it'll take a while to install. I'll test it in the morning before I go to work, hopefully.
[05:17] <ball> diogenes_: I appreciate the help. Thanks!
[05:17] <diogenes_> ball, you're welcome.
[05:20] <ball> Oh it's done!  That was quick.
[05:23] <ball> ...and it boots.
[05:24] <ball> ...with that, I'm off to bed. :-)
[05:34] <Unit193> gparted unmounts stuff, not sure if ubiquity does but I thought so.
[08:31] <cfhowlett> !xubuntu
[08:31] <cfhowlett> !16.04
[11:14] <xubuntu73w> Operating 18.04 from cd operated at 1024x748 on my Amilo-Pro V2030, so I downloaded it becayse Mint only worked at 640x480. But downloaded Xubunto also only worked at 640x480! Setting shows no other resolution. How do I get the downloaded version to use higher resolution like the CD version does?
[11:15] <bluesabre> xubuntu73w: Click on the apps menu, type in "display" and select it, then choose a higher resolution
[11:27] <xubuntu72w> Operating 18.04 from cd works on my Amilo-Pro v2030 at 1024x748 resolution. But when I downloaded it, it ran at 640x480 and the App/Display/Settings shows no other option. How do I get the downloaded version to have the same resolution as the CD version?
[14:18] <xubuntu56w> can anyone help me with setting properties using xfconf-query on xubuntu 18.04.2?
[14:21] <Spass> xubuntu56w, what do you want to change? did you see this wiki? https://docs.xfce.org/xfce/xfconf/xfconf-query
[14:24] <xubuntu56w> i want to change the properties lid-action-on-battery and lid-action-on-ac, i did see the wiki and it did not help. whenever i run the command it says that the property does not exist on the channel
[14:27] <Spass> you mean "xfce4-power-manager" channel? I don't see those properties on my machine in that channel, so if you need you may add them
[14:28] <Spass> create them
[14:30] <xubuntu56w> that's what i initially thought. i issued "xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/lid-action-on-ac -n -t int -s 1" yet the property remains unchanged
[14:32] <Spass> try "xfconf-query -c xfce4-power-manager -p /lid-action-on-ac -n -t bool -s true"
[14:32] <Spass> no, sorry
[14:32] <Spass> you need int for that
[14:32] <Spass> so "xfconf-query -c xfce4-power-manager -p /lid-action-on-ac -n -t int -s 1"
[14:33] <Spass> I think that "/xfce4-power-manager/" after -p was unnecessary in your command
[14:36] <Spass> well, to be sure I'm not really sure what type do you need for that property, where did you get info about adding that property?
[14:37] <Spass> (maybe it shows only on laptops, that's why I don't see it on my PC)
[14:37] <xubuntu56w> i ran xfconf-query in monitor mode and fiddled around with the settings and that's what i got if that's what you're asking
[14:39] <xubuntu56w> okay, i tried "xfconf-query -c xfce4-power-manager -p /lid-action-on-ac -n -t int -s 1" and the default action for closing the lid on ac is still "lock screen" and not "suspend"
[14:41] <Spass> does it change when you change 1 to 2? with this "xfconf-query -c xfce4-power-manager -p /lid-action-on-ac -s 2"
[14:41] <xubuntu56w> it does not
[14:42] <Spass> I'll take a look at that on my laptop, one moment
[14:42] <xubuntu56w> it does work if i manually open the power manager, change the settings there and then enter "xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/lid-action-on-ac -s 1" into the terminal
[14:49] <Spass_laptop> it works on my laptop "xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/lid-action-on-ac -s 3"
[14:49] <Spass_laptop> I can change it to 0. 1 or 3 (2 is blank on my laptop)
[14:49] <xubuntu56w> did you manually change the settings through xfce4-power-manager gui before?
[14:49] <Spass_laptop> and it makes change in GUI, but I need to reopne the settings window to see the changes
[14:51] <xubuntu56w> i noticed that changing the settings using the terminal does work, but you need to change them using the gui first
[14:51] <Spass_laptop> I've changed for AC in GUI, because the property wasn't present before
[14:51] <Spass_laptop> yeah, same observation
[14:51] <Spass_laptop> property wasn't there until I've changed in GUI to some other option, that created the property
[14:52] <xubuntu56w> and if you create it manually it doesn't do anything
[14:52] <Spass_laptop> and now I can see the property and change to whatever I want using xfconf-query (or in GUI)
[14:52] <Spass_laptop> ok, will try to delete it and create without GUI
[14:55] <Spass_laptop> yeah, when I created it using xfconf-query the property was added, but changes weren't visible in GUI
[14:55] <Spass_laptop> weird
[14:56] <Spass_laptop> and after one change in GUI it starts working
[14:58] <xubuntu56w> so i guess it's a bug
[14:59] <Spass> if you used my incorrect command I suggested on the beginning, you can delete that property using "xfconf-query -c xfce4-power-manager -p /lid-action-on-ac -r -R"
[15:00] <Spass> yeah, bug or some behaviour I don't really understand, maybe xfce devs would help with explaining that
[15:01] <xubuntu56w> should i file a bug report then?
[15:19] <Spass> not sure, but it would not hurt, maybe here? https://bugzilla.xfce.org/buglist.cgi?component=Xfconf-query&list_id=47041&product=Xfconf&resolution=---
[15:20] <Spass> or maybe it's strictly a Xfce Power Manager thing... another option is asking on #xfce-dev I suppose
[15:21] <xubuntu56w> the bugzilla already has a bug report that is similar in behavior to what i'm experiencing
[17:51] <nokiomanz> Hi, I have my desktop connected to a 4K TV via HDMI as my main monitor. I set the desktop to 1080p. But upon Closing/opening the television  on the next day or a few hours later it is as if the display is "redetected" and resolution is set to 4k. What can I do to make it stick to 1080p? If I close the television and open it a few minutes later it is still at 1080p.
[18:16] <kadiro> I lost the sound
[18:17] <kadiro> aplay -l said there is no card
[19:25] <mzeus98> Hey guys