[05:33] <guiverc> my `chromium-browser` isn't accepting any text input into page/url/window... i've logged out, restarted but no difference. `snap refresh --beta chromium` to try a different version; no change. any clues appreciated
[11:23] <oerheks> guiverc, clear the cache of ~/.cache of chromium-browser
[11:24] <guiverc> thanks oerheks ... `rm`ing now...
[11:25] <oerheks> :-)
[11:27] <guiverc> that just increased disk space .5GB !  (2.2gb free increased to 2.7gb)
[11:29] <guiverc> alas starting chromium didn't fix issue  
[11:31] <oerheks> oh :-(
[11:32] <oerheks> one could clear the ~/.config folder too, but then you loose all settings/bookmarks/plugins/malware
[11:34] <guiverc> thanks, I'll give it a go (the malware sounds interesting...)
[11:34] <oerheks> :-D
[11:34] <guiverc> no change, and nothing lost - maybe cause it's a snap; it's stored elsewhere..
[11:35] <oerheks> i had this once .. https://www.dropbox.com/s/eakrho2sfpgdvbw/virusaanval.png?dl=0
[11:36] <guiverc> i do have a ~/snap/chromium/ folder so looking there.
[11:36] <oerheks> oops, yes, my bad, snaps store their malware there 
[11:36] <oerheks> err config
[11:37] <guiverc> yeah a windows security alert doesn't quite have the same effect when we're not using windoze
[11:38] <guiverc> :) on malware err ..
[11:39] <oerheks> still looking for my C: drive..
[11:40] <guiverc> my ~/snap/chromium/common/.cache/chromium/Default/Cache looks huge too, you've given me loads of disk space back here too
[11:41] <guiverc> what was 2.2gb free is now 3.3gb
[11:42] <oerheks> great
[11:42] <guiverc> no keybd yet with cache,  next is the malware i guess
[11:42] <oerheks> how about the logfiles?
[11:43] <oerheks> if they growing fast too..
[11:44] <guiverc> nope; (I omitted Code Cache)  .. no go, looking for config
[11:54] <guiverc> lost malware, but still no keyboard input :(  (but only plus site; 3.6gb of space in $HOME instead of 2.2)
[11:54] <guiverc> s/site/side
[11:58] <guiverc> oerheks, success !!!  (my continual re-load of chromium must have re-introduced issue whatever it was (into cache possibly), I redid some of prior commands (rm cache) & now it's working)...   Thanks HEAPS !!  (x2; problem solved & I have more disk space to fill!)
[12:00] <oerheks> great. still i like to find out what happens so often with chromium browser, is it because of the snap confinement?
[12:02] <guiverc> i have no idea, and too tired to look tonight..  (I'm adding back privacy.badger, ublock etc)
[12:03] <guiverc> I can't say I like snap; on reboot so often I find it reporting "Restore session?" & it returns to what it was a ~week prior  (and never as I close down with a single window; always 4-5 windows)
[12:03] <oerheks> "Privacy Badger blocks spying ads and invisible trackers. " nice
[12:12] <guiverc> thanks heaps oerheks, nice to have silence with box besides me now off (where I was browsing sites I use chromium with)
[16:53] <adrian_1908> Hello. Do I see it right that 20.04 LTS won't be defaulting to Wayland? I only found various news articles, so I wasn't sure how authoritative that is.
[17:10] <tomreyn> adrian_1908: (as already discussed on #ubuntu) it won't.
[17:12] <tomreyn> https://www.phoronix.com/scan.php?page=news_item&px=No-Wayland-Default-20.04-LTS is maybe not the best source, you *may* be able to find a better source on blog.ubuntu.com
[17:15] <adrian_1908> tomreyn: Sorry, the large response drowned out your early "no". Yeah, that's one of the articles I read. Was just looking for an informed opinion, as those tend to be more current than articles on some topics.
[17:19] <tomreyn> adrian_1908: FWIW, the daily builds don't default to wayland (except for gdm), and i've seen ubuntu developers confirming it won't be defaulting to wayland for gnome-shell.
[17:23] <adrian_1908> tomreyn: Nice. I have an Nvidia GPU and need to use proprietary drivers for feature/perf reasons. If the upcoming LTS defaults to- and support X, then I know I have a solid workhorse for the forseeable future. In a few years I can then consider new hardware or a different distro if need be.
[17:25] <tomreyn> nvidia'S driver situation is probably a major reason why the default isn't changing, yet. sooner or later X will die, though.
[17:25] <tomreyn> it's already pretty much in bugfix only mode upstream
[17:26] <tomreyn> where 'already'  is ~ 50 years ;)
[17:26] <tomreyn> actually more like 35#
[17:27] <tomreyn> 33 for X11
[17:28] <adrian_1908> :)
[20:49] <elhoir> hello folks, i have a trange behavior in Synaptic
[20:49] <elhoir> it doesnt let me to uninstal packages due to "broken packages"
[20:50] <elhoir> but i have no broken debs!
[20:50] <elhoir> uninstall*
[20:50] <elhoir> can anyone help me?
[20:52] <oerheks> try first: sudo apt install -f
[20:52] <oerheks> then run sudo apt update && sudo apt dist-upgrade
[20:52] <oerheks> then try again to remove? 
[20:53] <oerheks> else; run sudo apt update && sudo apt dist-upgrade
[20:53] <elhoir> oerheks, i did - system is clean
[20:53] <elhoir> wwell i run sudo apt full-upgrade
[20:53] <elhoir> its the same thing, isnt it?
[20:53] <oerheks> that is oke
[20:53] <oerheks> can you paste the output when you try to remoe?
[20:54] <oerheks> c/remove
[20:54] <oerheks> paste.ubuntu.com
[20:54] <elhoir> whth synaptic?
[20:54] <oerheks> try from terminal?
[20:55] <elhoir> ok, well i dont know theexact package name... i try to use * (wildcard) but terminal doesnt seem to allow them
[20:56] <elhoir> https://pastebin.com/4vkW3UiX (its in spanish)
[20:57] <oerheks> no visit pastebin, thanks
[20:57] <oerheks> it needs js
[20:57] <elhoir> oh sorry
[20:58] <elhoir> here you are - https://paste.ubuntu.com/p/5VTktysBhF/
[20:59] <oerheks> that is not the way to remove a kernel
[20:59] <elhoir> hm?
[20:59] <elhoir> well i did that with previous versions ans no  problem
[20:59] <elhoir> and*
[21:00] <oerheks> sudo apt-get purge linux-image-x.x.x-x-generic 
[21:00] <oerheks> then run update-grub
[21:01] <oerheks> after reboot, autoremove
[21:01] <elhoir> i have just made it, tried to remove 5.4.0-12 ... and kernel image is still in /boot
[21:01] <elhoir> O_O
[21:01] <elhoir> O_O
[21:02] <elhoir> wtf
[21:05] <elhoir> few days ago i triedreinstalling packages && purging, no success
[21:06]  * oerheks lost interest due to bad language
[21:09] <elhoir> few days ago i tried reinstalling packages && purging, no success
[21:09] <elhoir> sorry
[21:14] <elhoir> ok
[21:55] <nmrp3> hi
[21:55] <nmrp3> so because I love to try out new things I did an do-release-upgrade to 20.4
[21:56] <Bashing-om> nmrp3: Welcome :D
[21:56] <nmrp3> cheers :)
[21:56] <nmrp3> so essentially everything works so far except my kde plasma workspace didn't start up - I have a blank desktop with no task bar or anything
[21:57] <nmrp3> I can start processes with alt-f2, and tab through them, but windows have no borders
[21:57] <nmrp3> they can be dragged around though - so I have a functioning window manager I guess
[21:58] <nmrp3> the only other minor thing is that my wireless mouse stopped working, but the wireless keyboard it came with works - go figure
[22:03] <nmrp3> Running "kstart5 plasmashell" prints out a lot of warnings and errors
[22:08] <Bashing-om> nmrp3: Await here for one who has KDE experience - not me, see then :) 
[22:13] <nmrp3> I think "/usr/lib/gdm3/gdm-x-session" may perhaps be to blame? It's got a bunch of error/warning entries in systemctl
[22:16] <Bashing-om> nmrp3: the log file .xsession-errors on your /home may have some hints ?
[22:18] <nmrp3> mm, loads of "could not connect to relay relay://******" messages
[22:18] <nmrp3> I'm going to try sddm and see if things boot with that - back in a couple of minutes
[22:25] <nmrp3> back
[22:27] <nmrp3> going to try with clean .cache .confg .local and try again ...
[22:34] <nmrp3> ok - so that hasn't fixed things
[22:37] <nmrp3> I@m wondering if I should drop down to a terminal, uninstall everything gnome and kde, reboot, then re-install?
[22:38] <Bashing-om> !Info kubuntu-desktop
[22:39] <Bashing-om> !info kubuntu-desktop
[22:39] <nmrp3> ah ... that wasn't installed any more somehow
[22:40] <nmrp3> so let's try that then
[22:40] <Bashing-om> !info ssdm
[22:40] <Bashing-om> !info sddm
[22:43] <nmrp3> ok -- going to reboot after installing kubuntu-desktop -- fingers crossed
[22:49] <nmrp3> hi - that's fixed it I thinl
[22:49] <nmrp3> thanks
[22:49] <nmrp3> so the version upgrade somehow lost the desktop pacakge
[22:50] <Bashing-om> nmrp3: :D Strange things can happen.
[23:28] <nmrp3> ain't that the truth