[00:25] <eric> hello
[00:25] <eric> hi
[00:25] <Guest96763> hello??
[00:26] <Guest96763> hi
[00:27] <eric_> Anybody here?
[00:28] <eric_> All right
[00:28] <eric_> I'm leaving
[00:32] <eric_> bye
[02:53] <rock64> hi all have no question yet it just booted
[04:04] <rock64> im back so far it ran almost 10 mins not have any luck
[04:35] <Techman> I'm running into an issue while testing this 17.10 image
[04:35] <Techman> Whenever I click on the keyboard in the indicator area the whole thing just locks up
[04:36] <Techman> Literally dead-on-arrival for a desktop experience
[04:40] <rock64> ok back again maybe better luck before something go wrong
[04:43] <kaption> two try ok now lets see if i can stay online for 10 mins
[06:29] <alkisg> lostMeUbuntu: from your linuxmint grub, type "c" to get a command line, then "insmod btrfs", "set root=(hd0,msdos2)" (or wherever your other install is), and finally "configfile /boot/grub/grub.cfg", so that it loads your linux mate grub
[06:32] <alkisg> Techman: yeah I'm seeing that in 18.04, something's terribly wrong
[06:32] <Techman> Can someone get a hold of Wimpy about this
[06:33] <alkisg> I pinged flexiondotorg a few weeks ago, no response yet
[06:33] <Techman> I held off on installing it on my desktop for now
[06:34] <alkisg> Techman: btw, does alt+ctrl+f2 work for you at that point?
[06:34] <Techman> I use F1, but yeah I guess
[06:34] <Techman> I can use that to get out of the desktop
[06:34] <Techman> But I return to the desktop and it's all hung
[06:34] <alkisg> I started suggesting f2 because now with wayland, it goes in f
[06:34] <alkisg> *f1
[06:34] <Techman> I don't know anything about Wayland tbh
[06:35] <alkisg> So pressing alt+ctrl+f1 in wayland does nothing at all
[06:35] <Techman> why would they do that
[06:35] <Techman> That's like an antifeature
[06:35] <alkisg> It actually makes more sense, why would graphics go in vt7 instead of starting normally from vt1
[06:35] <alkisg> It was xorg that was bad there
[06:35] <Techman> oh
[06:36] <alkisg> And the other vts are only started when the user switches to them, saving ram
[06:36] <Techman> Isn't Wayland still buggy though
[06:36] <alkisg> Not by itself buggy, it's just the apps aren't ready for it yet
[06:38] <alkisg> Techman: what's your keyboard layout? mine is us,gr
[06:38] <Techman> I'm guessing it's just US, because it's a US keyboard
[06:39] <alkisg> Techman: eh, if you're only using us and not some other language, why do you have a keyboard applet?
[06:39] <Techman> It's a G.Skill KM780 MX (red backlit, not RGB)
[06:39] <Techman> I have no idea, that's why I clicked on it to see why it was there
[06:39] <Techman> And then...rip
[06:42] <alkisg> If you still have that installation, it would be nice to see the output of `setxkbmap -query`, before clicking on the applet...
[07:59] <Techman> alkisg: it was a livecd
[07:59] <Techman> I didn't actually install it because of this
[08:00] <Techman> Do you want me to restart into it again to test it out
[08:01] <alkisg> Techman: nah, not important, I don't think the keyboard is the issue
[08:01] <alkisg> it's only one of the ways to hang the session
[08:02] <Techman> There are other ways to bork the session?
[08:03] <alkisg> Oh sure, for me in 18.04 it hangs after a few clicks anyway
[08:03] <alkisg> Although inside the live cd there's fcitx running, which is not running later in the installed session
[08:03] <alkisg> So there's a possibility that what you saw in 17.10 was different to what I see in 18.04
[08:04] <Techman> Well
[08:04] <alkisg> (fcitx was what was showing the keyboard applet in your case, afaik)
[08:04] <Techman> Could this fcitx stuff be what is causing the issue
[08:04] <alkisg> That's for chinese users, I had a lot of issues with that, I never use it in the installed system anyway
[08:04] <alkisg> I didn't have hanging issues with it though so far
[08:05] <alkisg> Only "not being able to to properly" issues
[08:06] <alkisg> *to type
[08:07] <Techman> Oh ok
[08:09] <Techman> I guess I'll hold off on this for a little bit then
[08:09] <Techman> I could install 16.04 but honestly I think the improvements in MATE and all of these panel options has made it kinda obsolete in a sense
[08:11]  * alkisg is only using LTS releases, the non-LTS ones aren't worth the debugging
[09:29] <sacarde> hi
[09:29] <t0ssp0t> hello
[09:32] <sacarde> what do I have to enable to auto-mount usb ?
[09:32] <sacarde> udisks2.service ?
[09:34] <diogenes_> sacarde, I don't know about mate, but in other DE, it's afaik goa service (gnome online account service)
[09:35] <kernal_> like a usb flash drive?
[09:36] <sacarde> y
[09:40] <kernal_> never had a problem getting a usb flash drive to show up on mate?
[09:58] <alkisg> sacarde: usbs get automatically mounted in ubuntu mate
[09:58] <alkisg> Are you using some other distribution or flavor?
[10:02] <sacarde> ubuntu mate
[10:02] <sacarde> is there a service that make this?
[10:03] <sacarde> or a udev rule?
[10:03] <alkisg> sacarde: sure, udev notifies udisks which notifies the desktop environment
[10:03] <alkisg> It's all preconfigured
[10:03] <alkisg> Did you do something to break it?
[10:03] <sacarde> maybe
[10:04] <sacarde> udisks2.service ?
[10:04] <alkisg> Yes; but what are you planning to do with that? It's not a matter of starting a service
[10:05] <alkisg> If you want help in troubleshooting it, it's best to start with other commands
[14:09] <ubuntu-mate> helo
[14:09] <ubuntu-mate> mname is jeff
[17:04] <guest-bvqrq8_> erzlzioi
[17:04] <guest-bvqrq8_> gfhgg-
[17:04] <guest-bvqrq8_> jktpilkoö
[17:04] <guest-bvqrq8_> lkl,koöpjijkgjukifm,9j67876588lgfhllom,clö pzi.-hklhkluil.lkö-öjklöölöä ö#ä
[17:04] <guest-bvqrq8_> li8i-bvgirhmklot-gk
[17:05] <guest-bvqrq8_> nhk.lm n8zjlö if.ll
[17:05] <guest-bvqrq8_> 687o
[17:05] <guest-bvqrq8_> l
[17:05] <guest-bvqrq8_> o
[17:05] <guest-bvqrq8_> jk
[17:10] <alkisg> Don't run this it will wipe your hard disk
[17:24] <acer> hi
[17:24] <diogenes_> hi
[17:24] <acer> my wireless networks wont show up
[17:24] <acer> i am not an expert
[17:24] <acer> a windows user
[17:24] <acer> recently got ubuntu
[17:25] <acer> in my acer laptop
[17:25] <acer> and its a qualcom atheros 9565 devic
[17:25] <acer> device
[17:25] <acer> any suggestions
[17:25] <acer> ?
[17:26] <acer> tried some steps by downloading package etc
[17:26] <acer> but not all commands would work as it is
[21:44] <Guest29695> hi everyone
[21:45] <diogenes_> hi
[21:46] <Joche> hello