/srv/irclogs.ubuntu.com/2018/10/23/#kubuntu.txt

balsaqok here it is00:04
balsaqlet me know what you think valorie00:07
valorieI did!00:08
balsaqit kinda looks like ubuntu doesnt it?00:14
valorienot sure what you mean? Plasma is designed so you can make it look however you want00:15
balsaqhmm i dont know plasma00:18
balsaqi just found a pic and put the words on it w/ gimp00:18
valoriethat is the desktop Kubuntu provides00:18
valorieplasma by KDE00:18
balsaqoh cool00:19
balsaqsounds beautiful00:19
valorie'tis00:19
balsaqis amaro kthe browser00:24
valorieAmarok was our music player for many years00:29
valorieit is now awaiting some final porting details to make it into the modern world00:29
valorieour browser is called Falkon and it's generally the only browser I use now00:29
valorielove it00:29
balsaqi have been using firefox lately01:26
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.601: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 Backports01:30
Kon-Don't mean to be rude but it almost seems like an oversight01:32
balsaqthats bordeline Kon-01:42
Kon-Honest question as it's currently not clear to me what the roadmap is for point releases01:42
Kon-If it's a testing issue, I can grab 5.12.7 from Backports and try to replicate problem areas01:43
balsaqthat goes w/o saying01:44
Kon-Heh, does it?01:44
balsaqi for one would like to know the result of you testing01:45
balsaqyour*01:45
balsaqone moment01:48
valorieKon-: the kubuntu team doesn't package FF03:11
valoriethat is done by the mainline devels03:11
valoriewhy they don't chose the latest I don't know, but probably based on all the dependencies03:12
Kon-Thanks valorie, but are you talking about Firefox? I was asking about the Plasma 5.12 point releases03:22
valorieoh sorry, I got confused by what the person right above you said03:23
valorieWe couldn't get the newest plasma in the release because of feature freeze03:23
valorieso we did the best we could with a zero-day backport03:23
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 on03:25
valoriewell, the calendar for Plasma releases and Ubuntu releases sometimes works for us, and sometimes don't03:26
valorieerr, doesn't03:26
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 around03:29
valoriegood to hear, Kon-03:30
IrcsomeBot<kusuma_loka> Hi, now my kubuntu work like ussual after reinstall... Thanks all04:36
acheronukKon-: 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=3006:23
acheronukwaiting for SRU admins to approve06:23
acheronukfor https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/179449406:24
ubottuLaunchpad bug 1794494 in xdg-desktop-portal-kde (Ubuntu) "SRU tracking bug for KDE's Plasma 5.12.7 for bionic" [Undecided,Confirmed]06:24
acheronukKon-: SRU team are not many people in Ubuntu, and will get to it when they can06:24
=== ichoquo0Aigh9ie is now known as jalcine
=== jalcine is now known as jacky
=== ichoquo0Aigh9ie is now known as jalcine
=== jalcine is now known as jacky
=== himcesjf_ is now known as him-cesjf
draikHello, 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
draikTTY1 is GUI, TTY2 is CLI08:04
hateballdraik: any errors in ~/.xsession-errors when you try to log in?08:04
draikChecking now...08:05
hateballand the usual things like... have you run any X apps with sudo, making ~/.Xauthority owned by root rather than your user08:06
draikhateball: it says >>> $DISPLAY is not set or cannot connect to the X server08:06
draikhateball: not that I'm aware, but looking at it, my ~/.Xauthority is root:root08:07
draikchown'd it.08:07
hateballdraik: yeah, you dont want it to be that :p08:07
draikI did a recursive chown on my home directory to be draik:draik08:08
hateballonly that file should affect X08:08
hateballtypically there's no harm in recursive either unless you have some strange setup08:08
draikThat's the only thing I saw with root:root, but safer > sorry.08:08
draikHow do I "unlock" TTY1 now?08:09
hateballa reboot should do it, or restart sddm08:09
draikTrying the latter08:10
draikRestarted, and I was able to login. Still seems to hold at the login screen.08:11
hateballwhat do you mean being able to login, as well as hold?08:11
hateballthat it accepts your password, but does not load the desktop?08:12
draikCorrect.08:12
draikI can move my mouse around the screen, but that's about it. Everything else is as good as a wallpaper.08:12
hateballright08:12
hateballdraik: can you by any chance launch a terminal with ctrl+alt+T, or start krunner with alt+space ?08:13
draikInteresting. I re-checked, it was root:root again.08:14
draikThe ~/.Xauthority file, I mean.08:14
draikhateball: no to either CTRL+ALT+T and ALT+SPACE08:15
hateballmake sure you sudo chown it to your user, and check the permissions after. then try a "sudo service sddm restart"08:15
draikDoes nothing.08:15
draikRight. I sudo'd the chown, and I restarted the sddm service.08:16
hateballtry logging in again then08:17
draikOK. I chown'd, restarted sddm, and ensured ~/.Xauthority is not root:root. Trying again.08:17
draikLooks like I'm in now :D08:17
draikSo, what would have caused me to get a root:root file?08:18
draikThank you, hateball08:18
hateballdraik: Typically "sudo kate" or some other X application08:18
draikDon't recall doing that at all, but good to know.08:18
hateballbecause it wont set up the environment properly, and so it breaks the permissions on that file08:18
draikLast "sudo" was for the upgrade >>> 'sudo do-release-upgrade'08:19
draikI noticed that it did "mode=server" if that matters.08:19
hateballcould just have been some other thing, who knows with computers. it's a wonder they barely work at all08:19
hateballdraik: anyhow now you know what to look for if it happens again :p08:19
draikHoping it doesn't, but this was a good lesson.08:21
draikWhen 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:21
draikThank you for the help and resolution, hateball08:22
hateballdraik: no worries :)08:23
hateballhappy computing08:23
IrcsomeBot<Anarchotaoist> Is there a fix in for Cosmic to get Electon apps working?10:12
IrcsomeBot<acheronuk> what doesn't work?10:15
IrcsomeBot<Anarchotaoist> 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?10:30
IrcsomeBot<Anarchotaoist> Although, I just checked Auryo and Brave which suppose to be electron and they work!10:30
IrcsomeBot<acheronuk> Not a system thing that I've heard (I could have missed it though)10:31
IrcsomeBot<acheronuk> mailspring was an incompatability with new glibc IIRC, which may not be anything specific to electron10:32
IrcsomeBot<Anarchotaoist> ok10:32
IrcsomeBot<acheronuk> each new ubuntu release includes new version of a lot of libraries. sometime app developers have to catch up to keep things working10:33
IrcsomeBot<Anarchotaoist> Ok, thanks Rik.10:33
IrcsomeBot<acheronuk> for example, the official slack app did not work for a while on 18.04, as they needed to make it compatible with new libcurl10:34
IrcsomeBot<acheronuk> these things happen10:34
IrcsomeBot<Anarchotaoist> 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☺️10:37
IrcsomeBot<acheronuk> @Anarchotaoist, No problem at all. As said, even the slack developers screwed up!10:38
IrcsomeBot<acheronuk> they should no better ;)10:38
IrcsomeBot<Anarchotaoist> 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. ??10:41
IrcsomeBot<acheronuk> Not heard of input issues like that so far. I'll keep an eye on bug reports though.10:42
IrcsomeBot<Anarchotaoist> ok10:43
IrcsomeBot<DrKineticPie> 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:03
IrcsomeBotwith www.DeepL.com/Translator11:03
BluesKajHey folks11:37
=== wodencafe is now known as WodenCafe
Nomad_ok, need to update my client to autojoin here after FreeNode registration goes through16:20
=== msalvatore_ is now known as msalvatore
IrcsomeBotlulzx was added by: lulzx18:06
ZeZu18.04.1 -> 18.10 : do-release-upgrade crapped out on me and apparently packages are broken ...18:20
ZeZudpkg: 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.118:21
IrcsomeBotabhishek_0 was added by: abhishek_020:38

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!