[00:04] <balsaq> ok here it is
[00:07] <balsaq> let me know what you think valorie
[00:08] <valorie> I did!
[00:14] <balsaq> it kinda looks like ubuntu doesnt it?
[00:15] <valorie> not sure what you mean? Plasma is designed so you can make it look however you want
[00:18] <balsaq> hmm i dont know plasma
[00:18] <balsaq> i just found a pic and put the words on it w/ gimp
[00:18] <valorie> that is the desktop Kubuntu provides
[00:18] <valorie> plasma by KDE
[00:19] <balsaq> oh cool
[00:19] <balsaq> sounds beautiful
[00:19] <valorie> 'tis
[00:24] <balsaq> is amaro kthe browser
[00:29] <valorie> Amarok was our music player for many years
[00:29] <valorie> it is now awaiting some final porting details to make it into the modern world
[00:29] <valorie> our browser is called Falkon and it's generally the only browser I use now
[00:29] <valorie> love it
[01:26] <balsaq> i have been using firefox lately
[01:30] <Kon-> I'm a little bit confused as to why Bionic Backports PPA is on 5.12.7 and the main release is on 5.12.6
[01:30] <Kon-> Is it just lack of time?
[01:30] <Kon-> I'd think at this point, Bionic would have 5.12.7 and the team would be working on getting 5.14 into Backports
[01:32] <Kon-> Don't mean to be rude but it almost seems like an oversight
[01:42] <balsaq> thats bordeline Kon-
[01:42] <Kon-> Honest question as it's currently not clear to me what the roadmap is for point releases
[01:43] <Kon-> If it's a testing issue, I can grab 5.12.7 from Backports and try to replicate problem areas
[01:44] <balsaq> that goes w/o saying
[01:44] <Kon-> Heh, does it?
[01:45] <balsaq> i for one would like to know the result of you testing
[01:45] <balsaq> your*
[01:48] <balsaq> one moment
[03:11] <valorie> Kon-: the kubuntu team doesn't package FF
[03:11] <valorie> that is done by the mainline devels
[03:12] <valorie> why they don't chose the latest I don't know, but probably based on all the dependencies
[03:22] <Kon-> Thanks valorie, but are you talking about Firefox? I was asking about the Plasma 5.12 point releases
[03:23] <valorie> oh sorry, I got confused by what the person right above you said
[03:23] <valorie> We couldn't get the newest plasma in the release because of feature freeze
[03:23] <valorie> so we did the best we could with a zero-day backport
[03:25] <Kon-> Ahh, gotcha. Thanks for the heads up. I can see how that was a busy time for the team, what with Cosmic stuff going on
[03:26] <valorie> well, the calendar for Plasma releases and Ubuntu releases sometimes works for us, and sometimes don't
[03:26] <valorie> err, doesn't
[03:29] <Kon-> Yep, last time nailed it so well that I'm staying on Bionic for now :) Point releases are always nice, but there have been so few bugs with the setup thus far that I can safely live until 5.12.8 rolls around
[03:30] <valorie> good to hear, Kon-
 Hi, now my kubuntu work like ussual after reinstall... Thanks all
[06:23] <acheronuk> Kon-: 5.12.7 is uploaded in the Bionic unapproved queue https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=&direction=backwards&memo=60&start=30
[06:23] <acheronuk> waiting for SRU admins to approve
[06:24] <acheronuk> for https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1794494
[06:24] <acheronuk> Kon-: SRU team are not many people in Ubuntu, and will get to it when they can
[08:04] <draik> Hello, all. I upgraded from 18.04 to 18.10, and I can't login. I enter my password, and the login screen appears to be frozen. That's locked on TTY1, and I'm on TTY2 now. I've reinstalled the plasma-dekstop and kubuntu-desktop packages, to no success.
[08:04] <draik> TTY1 is GUI, TTY2 is CLI
[08:04] <hateball> draik: any errors in ~/.xsession-errors when you try to log in?
[08:05] <draik> Checking now...
[08:06] <hateball> and the usual things like... have you run any X apps with sudo, making ~/.Xauthority owned by root rather than your user
[08:06] <draik> hateball: it says >>> $DISPLAY is not set or cannot connect to the X server
[08:07] <draik> hateball: not that I'm aware, but looking at it, my ~/.Xauthority is root:root
[08:07] <draik> chown'd it.
[08:07] <hateball> draik: yeah, you dont want it to be that :p
[08:08] <draik> I did a recursive chown on my home directory to be draik:draik
[08:08] <hateball> only that file should affect X
[08:08] <hateball> typically there's no harm in recursive either unless you have some strange setup
[08:08] <draik> That's the only thing I saw with root:root, but safer > sorry.
[08:09] <draik> How do I "unlock" TTY1 now?
[08:09] <hateball> a reboot should do it, or restart sddm
[08:10] <draik> Trying the latter
[08:11] <draik> Restarted, and I was able to login. Still seems to hold at the login screen.
[08:11] <hateball> what do you mean being able to login, as well as hold?
[08:12] <hateball> that it accepts your password, but does not load the desktop?
[08:12] <draik> Correct.
[08:12] <draik> I can move my mouse around the screen, but that's about it. Everything else is as good as a wallpaper.
[08:12] <hateball> right
[08:13] <hateball> draik: can you by any chance launch a terminal with ctrl+alt+T, or start krunner with alt+space ?
[08:14] <draik> Interesting. I re-checked, it was root:root again.
[08:14] <draik> The ~/.Xauthority file, I mean.
[08:15] <draik> hateball: no to either CTRL+ALT+T and ALT+SPACE
[08:15] <hateball> make sure you sudo chown it to your user, and check the permissions after. then try a "sudo service sddm restart"
[08:15] <draik> Does nothing.
[08:16] <draik> Right. I sudo'd the chown, and I restarted the sddm service.
[08:17] <hateball> try logging in again then
[08:17] <draik> OK. I chown'd, restarted sddm, and ensured ~/.Xauthority is not root:root. Trying again.
[08:17] <draik> Looks like I'm in now :D
[08:18] <draik> So, what would have caused me to get a root:root file?
[08:18] <draik> Thank you, hateball
[08:18] <hateball> draik: Typically "sudo kate" or some other X application
[08:18] <draik> Don't recall doing that at all, but good to know.
[08:18] <hateball> because it wont set up the environment properly, and so it breaks the permissions on that file
[08:19] <draik> Last "sudo" was for the upgrade >>> 'sudo do-release-upgrade'
[08:19] <draik> I noticed that it did "mode=server" if that matters.
[08:19] <hateball> could just have been some other thing, who knows with computers. it's a wonder they barely work at all
[08:19] <hateball> draik: anyhow now you know what to look for if it happens again :p
[08:21] <draik> Hoping it doesn't, but this was a good lesson.
[08:21] <draik> When login issues happen, first thing I check is the disk space on /. Learned that one early on, when I was playing with a 20GB partition that I gave a fresh install (all on one partition).
[08:22] <draik> Thank you for the help and resolution, hateball
[08:23] <hateball> draik: no worries :)
[08:23] <hateball> happy computing
 Is there a fix in for Cosmic to get Electon apps working?
 what doesn't work?
 Well, there was Mailspring - you did direct me to a deb that worked -thanks! cpod is also an Electron app. I heard Electron apps as a whole were not working. Is that a system thing or will app devs need to release compatible versions for 18.10?
 Although, I just checked Auryo and Brave which suppose to be electron and they work!
 Not a system thing that I've heard (I could have missed it though)
 mailspring was an incompatability with new glibc IIRC, which may not be anything specific to electron
 ok
 each new ubuntu release includes new version of a lot of libraries. sometime app developers have to catch up to keep things working
 Ok, thanks Rik.
 for example, the official slack app did not work for a while on 18.04, as they needed to make it compatible with new libcurl
 these things happen
 I see. Sorry, I am not technically savy with the ins and outs of it all. Seeing some electron apps did not work I thought it may be all electron apps☺️
 @Anarchotaoist, No problem at all. As said, even the slack developers screwed up!
 they should no better ;)
 The other problem I have started experiencing however after upgrade is that typing input stopped working in the menu launcher and login from sleep. It even stopped working for Telegram yesterday. Rebooting fixed it every time. No issues today though. ??
 Not heard of input issues like that so far. I'll keep an eye on bug reports though.
 ok
 Hello, there, … I use two monitors on my computer. … Unfortunately it's like this, that open programs I can simply move to the second monitor, but unfortunately, shortcuts from programs on the desktop can't be moved to so easily on the second monitor. … He either wants to copy them or replace them, but then the files are gone... … Can I solve the problem that the desktop runs reasonably on 2 monitors like on Windows? … 
[11:37] <BluesKaj> Hey folks
[16:20] <Nomad_> ok, need to update my client to autojoin here after FreeNode registration goes through
[18:20] <ZeZu> 18.04.1 -> 18.10 : do-release-upgrade crapped out on me and apparently packages are broken ...
[18:21] <ZeZu> dpkg: error processing archive /var/cache/apt/archives/breeze_4%3a5.13.5-0ubuntu2_amd64.deb (--unpack):
[18:21] <ZeZu>  trying to overwrite '/usr/share/metainfo/org.kde.breezedark.desktop.appdata.xml', which is also in package plasma-look-and-feel-org-kde-breezedark-desktop 4:5.12.6-0ubuntu0.1