[05:39] <KubuntuMan> Hello! Please I lost my Ethernet connection after upgrading from Kubuntu 17.04 to Kubuntu 17.10. Your help will be greatly appreciated.
[06:23] <LinuxFan> Hello Everyone! ~ Please I need your help with the following question: https://www.kubuntuforums.net/showthread.php/72621-No-Ethernet-Internet-Connection-After-Upgrading-To-Kubuntu-17-10
[07:54] <keithzg[m]> Well drat, just finally upgraded my main PC at home to 17.10 and now I can't actually log in via SDDM.
[07:54] <Unit193> What happens?
[07:55] <keithzg[m]> Brief black screen, then I'm back at the login screen as if nothing happened. Happens if I try Plasma or Openbox (don't have anything else installed there at the moment)
[07:57] <hateball> keithzg[m]: are you the owner of ~/.Xauthority ?
[07:57] <keithzg[m]> hateball: yup, solely owned by my user, rw
[07:58] <hateball> Hmmm
[07:58] <hateball> keithzg[m]: anything in ~/.xsession-errors after you try loggin in?
[07:59] <Unit193> Yeah I thought of iceauthority and xauthority too, had some problems in that with artful myself.
[08:00] <keithzg[m]> hateball: Yeah I was looking at .xsession-errors, tailing it as I tried  logging in, nothing seemed immediately helpful; https://paste.kde.org/psgi55hak
[08:01] <keithzg[m]> Next up I suppose I should quickly create a new user to make sure whether or not it's my user configs somehow nonetheless
[08:03] <hateball> keithzg[m]: probably the quickest way to test at any rate
[08:05] <keithzg[m]> Well well well, testuser waltzed into a Plasma session just fine
[08:07] <hateball> afraid I don't know how to debug a plasma session
[08:11] <keithzg[m]> Well there's a clue in that Openbox can't log in either. Hrmmm.
[08:12] <keithzg[m]> Haha wait I restarted SDDM and now the theme is broken? Weird
[08:12] <hateball> it did show X errors tho
[08:12] <hateball> keithzg[m]: what driver/gpu ?
[08:13] <hateball> was thinking if you have nvidia-blob for instance, and some automatic settings with nvidia-settings that might break the session
[08:14] <keithzg[m]> AMD, using amdgpu—in theory, I wouldn't be surprised if things are screwy post-upgrade
[08:15] <hateball> I am unfamiliar with AMD so no idea there
[08:15] <hateball> But if it works with a fresh user...
[08:15] <keithzg[m]> That SDDM is visibly complaining that it can't find /usr/share/sddm/themes/breeze/Main.qml feels like it might be more the key here though . . .
[08:15] <keithzg[m]> Yeah the fresh user can't login now either after my sddm restart, oddly enough
[08:16] <keithzg[m]> I'm just gonna hit it with a hammer called kubuntu-desktop^ and see if that solves anything, heh, then dig in deeper if not
[08:17] <acheronuk> sddm-theme-breeze installed?
[08:17] <keithzg[m]> heh yeah that was far too many packages being installed right now that shouldn't have needed installation
[08:17] <keithzg[m]> acheronuk: it is now! (or will be momentarily, at least)
[08:18] <keithzg[m]> harrumph, well that fixed the SDDM theming issue but my login remains barred
[08:20] <keithzg[m]> Current .xsession-errors: http://paste.ubuntu.com/25909251/
[08:23] <keithzg[m]> The test user can't log in either now, even though SDDM seems to be working, bizarre.
[08:23] <hateball> hmmm, XDG_SESSION_DESKTOP shouldnt be blank should it
[08:24] <hateball> pretty sure that XDG_SESSION_DESKTOP and XDG_CURRENT_DESKTOP should be =KDE
[08:27] <keithzg[m]> Interesting
[08:28] <keithzg[m]> Back in the day, now is when I would have temporarily moved my .kde folder, heh
[08:28] <hateball> and that should be set by SDDM when you pick your session
[08:31] <hateball> keithzg[m]: suppose you could try the solution here even if it is for 16.04 https://askubuntu.com/questions/813544/graphical-components-stuck-on-kubuntu-16-04
[08:33] <keithzg[m]> hateball: sadly that appears to have changed nothing :(
[08:34] <hateball> hmmm
[08:35] <keithzg[m]> Probably worth me poking around and commenting out some things in .profile and such, though, since it's clearly some sort of user config that's at issue here
[08:38] <keithzg[m]> Okay, so I moved my entire ~/.config folder and then plasma logged in. So it's something in there
[08:40] <keithzg[m]> I'm just going to go ahead and blame baloo here, even though that's probably entirely unfair ;)
[08:43] <keithzg[m]> hahaha wait if I try and launch firefox I get logged out?
[08:44] <hateball> That'll teach you
[08:44] <hateball> But it sure sounds like something got messed with your install
[08:46] <keithzg[m]> Yeah no kidding----happens with testuser too, so I think it's not so much that my old config was bad as it must be that my old config was doing extra stuff that happens to trigger whatever is failing
[08:58] <keithzg[m]> Hmm yaknow there are a ton of old amdgpu-pro packages still installed. I think it's time for a purge.
[09:02] <keithzg[m]> Yup, that did it! Everything appears to work fine now. I can even start up Firefox,  if for some reason I wanted to :P
[09:03] <keithzg[m]> The lesson here is, as always, the problem is definitely whatever packages weren't installed from the repos :D
[09:05] <hateball> Hehe
[12:41] <BluesKaj> Hi folks
[13:48] <ForceRecon> Morning BluesKaj
[13:49] <BluesKaj> 'Morning ForceRecon
[13:50] <ForceRecon> I got some sleep
[13:50] <ForceRecon> woohoo
[13:50] <BluesKaj> :-0
[13:50] <BluesKaj> err :-)
[13:56] <ForceRecon> well that blows.. one of my remote machines updated teamviewer to the beta13 and now v12x won't connect to it and there will NOT be a Beta Outgoing only host for linux until final release..
[13:56] <ForceRecon> sugar plums!
[14:09] <ForceRecon> https://whoer.net/ - my anonymity is 100%  ;) LOL
[17:29] <Prashant> facing a issue with high cpu usage on ubuntu server.
[17:30] <Prashant> md process is utilizing max cpu.
[18:29] <o_a> Hello, all. I've been noticing for a while now that the loading spinning wheels on my installation spin super fast. I've no idea why this is happenning. Does anyone have a suggestion?
[18:30] <o_a> I mean the wheel that appears during Plasma's splash screen, or in the taskbar while an application is loading
[18:34] <RedHackIT> Heyy
[18:58] <alesan> hello I have installed kubuntu
[18:58] <alesan> what is the GUI application to install packages?
[18:58] <alesan> used to be "muon" but
[18:58] <alesan> it says it is not installed
[18:58] <alesan> I have not found anything in the K menu or in the settings
[18:58] <alesan> what is the GUI app to install more packages?
[19:01] <krytarik> alesan: Discover.
[19:02] <krytarik> (Literally.)
[19:06] <alesan> krytarik, is there any reason in the past several years they have changed the name of this central piece of software three times?
[19:07] <alesan> I do not have "Discover" installed apparently.
[19:07] <krytarik> What version are you on?
[19:07] <alesan> hm
[19:07] <alesan> how do I find out for sure?
[19:08] <krytarik> !version
[19:08] <alesan> 17.04
[19:08] <alesan> oh maybe it's not the latest?
[19:08] <krytarik> It's not, no.
[19:09] <alesan> well it's not ancient either
[19:09] <alesan> however, what was the GUI package manager in 17.04
[19:11] <krytarik> Huh, apparently Discover is not the default one in either, and while Muon is in 17.10, there seems to be none in 17.04 - iirc there was some issue with it during that cycle.
[19:19] <alesan> ok so what do you suggest?
[19:22] <krytarik> Actually, the package name of Discover is "plasma-discover", and it's there by default in both versions.
[19:25] <krytarik> alesan: If you don't see it for some reason, just do: "sudo apt install plasma-discover"
[19:25] <clivejo> we have to use plasma-discover as there is already a package called discover in the archives - https://packages.ubuntu.com/artful/discover
[19:25] <krytarik> Yes, just noticed that too. :D
[19:27] <alesan> why not "kdiscover" or "kpackagemanager" so that normal users can figure this out?
[19:28] <krytarik> Plasma is the desktop, so I guess it's fine.
[19:28] <clivejo> we closely work with Debian and they have a naming policy
[19:29] <clivejo> the application and project name is discover
[19:29] <clivejo> https://cgit.kde.org/discover.git/
[19:30] <alesan> I never quite understood what "plasma" is and why it's necessary. I wish I could go back to "base" KDE :)
[19:30] <clivejo> plasma is the desktop environment
[19:30] <alesan> but with the dual-monitor autodetection :D
[19:31] <clivejo> base KDE is what we call Frameworks or KF5
[19:31] <clivejo> so we have different tiers
[19:32] <clivejo> Qt > Frameworks > Plasma > KDE Applications
[19:32] <clivejo> on top of Ubuntu system
[19:33] <clivejo> kinfocenter will tell you what you have installed currently
[23:48] <ForceRecon> systemd[1]: apt-daily.timer: Adding 7h 52min 6.288137s random time.
[23:48] <ForceRecon> solved!