[02:11] <donofrio> so what am I doing wrong https://apaste.info/8x5P
[02:28] <nacc> donofrio: something is messed up with your gpg config
[02:57] <donofrio> nacc, how to heal it?
[06:05] <lotuspsychje> http://news.softpedia.com/news/ubuntu-18-04-lts-bionic-beaver-beta-released-for-opt-in-flavors-download-now-520153.shtml
[07:12] <Peace-> anyone here for internet problems?
[07:20] <SwedeMike> Peace-: well, if you don't state your problem you'll never find out.
[07:23] <Peace-> SwedeMike: well i have a strange behavior here , i can't connect to internet with the network manager cuz it doesn't list my wifi i just investigated on the problem adn i get these errors : 
[07:23] <Peace-> systemctl status wpa_supplicant.service
[07:24] <Peace-> Failed to initialize control interface '/run/wpa_supplicant'.  You may have another wpa_supplicant p rocess already running or the file was  left by an unclean termination of wpa_supplicant in which case you will need  to manually remove this file before starting wpa_supplicant again.
[07:24] <Peace-> sudo systemctl status NetworkManager.service
[07:24] <Peace->  error>   sup-iface[0x56547f32d5b0,wlp7s0]: error adding interface: wpa_supplicant couldn't grab this interface.
[07:25] <Peace-> iwconfig recognize my atheros wifi card and it lists properly the wifi nets
[07:25] <Peace-> so the drivers is working fine 
[07:26] <Peace-> to get it on internet i have to do : sudo pkill wpa_supplicant  ; sudo systemctl  start wpa_supplicant.service sudo systemctl start NetworkManager.service
[07:26] <Peace-> btw i havet to do that everytime at the start it's quite boring i did a script but i mean it's not the normal way ...
[07:30] <Peace-> the script it's this sudo pkill  wpa_supplicant ; sudo systemctl stop NetworkManager.service ; sudo systemctl start NetworkManager.service 
[07:43] <Boyette> hi
[07:43] <Boyette> can someone help me?
[08:01] <Peace-> Boyette: ABOUYT WHAT
[08:01] <Peace-> sorry caps
[08:02] <Boyette> cant run vlc
[08:02] <Boyette> it wont start
[08:02] <Boyette> it only syas
[08:02] <Boyette> says
[08:02] <Boyette> VLC media player 4.0.0-dev Otto Chriek (revision 4.0.0~rc1~~git20180309+r74746+128~ubuntu18.04.1)
[08:02] <Boyette> thats it
[08:22] <Peace-> Boyette: WAUT A MOIMENT
[08:23] <Boyette> im waiting
[08:24] <Peace-> Boyette: start vlc from terminal           vlc --ignore-config
[08:24] <Peace-> with that command line
[08:24] <Boyette> ok j
[08:24] <Peace-> if doesn't start that mean it's a bug somewhere somehow 
[08:24] <Peace-> if starts you got the answer
[08:24] <Boyette> same result
[08:25] <Boyette> j@HQ:~$ vlc --ignore-config
[08:25] <Boyette> VLC media player 4.0.0-dev Otto Chriek (revision 4.0.0~rc1~~git20180309+r74746+128~ubuntu18.04.1)
[08:25] <Boyette> j@HQ:~$ 
[08:25] <Peace-> VERY bad bug
[08:25] <Peace-> you have to ask to #vlc  could be a video driver vlc incopatible stuff 
[08:25] <Peace-> or something like that 
[08:25] <Boyette> it worked until yesterday.. after some update i think this happened
[08:26] <Peace-> could be and upgrade on vlc version that has that bug ... 
[08:26] <Peace-> or maybe some libraries that are not fully upgraded
[08:26] <Peace-> have tried to sudo apt-get upgrade? if you are on 18.04 of course
[08:27] <Boyette> yes
[08:27] <Boyette> all up to date
[08:27] <Peace-> Boyette: but ou have a 4 version btw 
[08:27] <Boyette> 4 version?
[08:27] <Peace-> on 18.04 i have 3.0 which is workin fine 
[08:28] <Peace-> Boyette:  i ahve this  vlc --version VLC media player 3.0.0 Vetinari (revision 3.0.0-30-gef4c265336)
[08:29] <Peace-> Boyette: https://i.imgur.com/oZo3Odn.jpg
[08:32] <Peace-> Boyette: remove the videolan daily build repository form your sources.list remove vlc and reinstall it 
[08:33] <Peace-> infact yhe version of yours it's what you can find here https://launchpad.net/~videolan/+archive/ubuntu/master-daily
[08:35] <Boyette> yes
[08:36] <Boyette> or it will fix itself?
[08:38] <Peace-> well you have to wait untill the next release on videolan daily  but if you want use vlc today you have to do what i said
[08:39] <Boyette> ok can u guide me how to delete 
[08:39] <Peace-> for me vlc is workin fine even without the daily repo 
[08:39] <Peace-> which is unstable 
[08:40] <Peace-> Boyette: you ahve to open this file /etc/apt/sources.lis and put one # before the line that contains videolan
[08:40] <Boyette> ok
[08:40] <Peace-> of course being root ...
[08:41] <Peace-> then sudo apt-get update ; sudo apt-get purge vlc ; sudo apt-get install vlc 
[08:45] <Peace-> btw Boyette the file is /etc/apt/sources.list
[08:46] <flocculant> I prefer to use ppa-purge which does all that and downgrades packages to default that a ppa changes
[08:47] <Peace-> flocculant: nice point of view
[08:47] <Peace-> i ma not so used to ppa anymore on kubuntu i work fine just with repo-standards
[08:48] <Boyette> videolan is not in there
[08:49] <Peace-> Boyette: sudo apt-get install ppa-purge
[08:50] <Boyette> done
[08:52] <Boyette> then?
[08:52] <Peace-> Boyette:  ls /etc/apt/sources.list.d/
[08:56] <Boyette> thats a directory
[08:56] <Peace-> Boyette: right there is something called vlc ?
[08:56] <Peace-> inside
[08:57] <Peace-> Boyette:  ls /etc/apt/sources.list.d/ | grep -i vlc
[08:57] <Peace-> Boyette:  btw    sudo ppa-purge -o videolan  if the repo you added it's that 
[08:58] <Peace-> if you added another repo you must get the correct name seeing on that folder
[08:58] <Peace-> now i smoke a cigarette :D
[08:58] <flocculant> Peace-: good call :p
[08:59] <Boyette> /etc/apt/sources.list.d/ubuntu-mate-dev-ubuntu-welcome-bionic.list.save
[08:59] <Boyette> /etc/apt/sources.list.d/ubuntu-mate-dev-ubuntu-welcome-bionic.list
[08:59] <Boyette> sory
[08:59] <Boyette> /etc/apt/sources.list.d/videolan-ubuntu-master-daily-bionic.list
[08:59] <Boyette> /etc/apt/sources.list.d/videolan-ubuntu-master-daily-bionic.list.save
[08:59] <Boyette> huh
[08:59] <Boyette> yes that
[09:00] <flocculant> Boyette: I think you can tab complete in ppa-purge so sudo ppa-purge ppa:vid<tab> see what that gives you
[09:01] <Boyette> what do u mean by <tab>
[09:01] <flocculant> press the tab key ...
[09:01] <flocculant> are you sure you should be using a development version of *buntu?
[09:02] <Boyette> lol
[09:02] <Boyette> yes because i learn these things now 
[09:02] <Boyette> i would never discover otherwise
[09:02] <flocculant> :)
[09:02] <Boyette> this helps me to learn linux believe me :P
[09:02] <flocculant> he he he 
[09:03] <Boyette> https://pastebin.com/f2bq5sh0
[09:04] <Peace-> Boyette: YOU HAVE A MESS ON REPOS
[09:04] <Boyette> great
[09:04] <Peace-> hahaha dudeeee
[09:04] <Boyette> how do we fix it
[09:04] <Boyette> :P
[09:04] <Peace-> Boyette: you have a bad behavior to add weird ppa 
[09:05] <Peace-> like webupd8
[09:05] <Peace-> they are not official so it's not strange to get a crappys system 
[09:06] <Peace-> i use kubuntu so i can remove ppas with the package manager i guessubuntu has one too
[09:06] <Boyette> for sure i needed it for something
[09:06] <Boyette> but i dont remember why
[09:06] <Peace-> Boyette: open the package manager
[09:06] <Peace-> Boyette: and go on settings 
[09:08] <Peace-> Boyette: here how it is on kubuntu i guess you have another one btw https://i.imgur.com/A6gHcNT.jpg
[09:09] <Boyette> i think there is none yet
[09:10] <Peace-> remove even those ppas that give you erros 
[09:11] <Peace-> so xbmc ubuntu-mate-dev miro-releases nilarimogard
[09:11] <Peace-> then update , remove vlc , reinstall vlc
[09:12] <flocculant> after removing the vlc repo :D
[09:12] <Peace-> of course i hope :D
[09:12] <Peace-> i have deleted every aspect of ubuntu i justuse kubuntu since 10 years i guess
[09:13] <Peace-> xD i don't remember the package manager name of ubuntu 
[09:13] <Boyette> removed and reinstalled vlc
[09:13] <Boyette> same result
[09:13] <Peace-> Boyette: because you have the version 4.0
[09:13] <Peace-> Boyette: vlc --version what does it say?
[09:14] <Boyette> https://pastebin.com/wyt4Q2EK
[09:14] <Peace-> Boyette: so 4.0 is still there ...
[09:14] <Boyette> yes it keeps coming back
[09:14] <Peace-> Boyette: basically you have the repo 
[09:15] <Peace-> Boyette: can you do a screen shot of this folder /etc/apt/sources.list.d/
[09:15] <Boyette> yes
[09:16] <Peace-> Boyette: basically you have to put all the files you got there in another folder like your home so that folder then it's empty
[09:16] <Boyette> https://prnt.sc/ip8ffb
[09:16] <Peace-> Boyette: so take ALL THAT crap files and put them on another folder 
[09:17] <Peace-> Boyette: like $HOME/oldcrapppas
[09:17] <Peace-> THEN remove reinstall vlc
[09:18] <Boyette> ok
[09:18] <Peace-> Boyette: now that folder it's empty ?
[09:18] <Boyette> not allowed to cut
[09:18] <Peace-> xD 
[09:19] <Peace-> Boyette: of course you have to be root 
[09:19] <Boyette> hehe
[09:19] <Boyette> just a moment
[09:20] <Peace-> sudo rm /etc/apt/source.list.d/videolan-ubuntu-master-daily-bionic.list 
[09:20] <Peace-> coudl be typos on that line
[09:20] <Peace-> and sudo rm /etc/apt/source.list.d/videolan-ubuntu-master-daily-bionic.list.save
[09:20] <Peace-> LOL
[09:21] <Peace-> OMG i hope he doesnt' connect like root now xD
[09:22] <Boyette> back
[09:23] <Peace-> so have you removed those files?
[09:23] <Boyette> yes
[09:23] <Boyette> done
[09:23] <Peace-> sudo apt-get update ; sudo apt-get purge vlc ; sudo apt-get install vlc
[09:24] <Peace-> then vlc --version 
[09:24] <Peace-> should be 3.0 now
[09:24] <Boyette> so the folder is empty now
[09:25] <Peace-> i hope so :D
[09:25] <Peace-> Boyette: if yes do that : sudo apt-get update ; sudo apt-get purge vlc ; sudo apt-get install vlc
[09:25] <Boyette> now
[09:25] <Boyette> i cant install vlc
[09:25] <Peace-> hahahah why what it says 
[09:26] <Peace-> Boyette: you made a mess with repos ...
[09:26] <Peace-> just that 
[09:26] <Boyette> https://pastebin.com/V5486CY9
[09:27] <Peace-> Boyette: sudo apt-get purge vlc 
[09:28] <Peace-> what did it say 
[09:28] <Boyette> its not installed offcourse
[09:28] <Boyette> not installed so not removed
[09:28] <Boyette> offcourse it told me many more
[09:29] <Peace-> Boyette: inthat folder /etc/apt/sources.list.d/ there is no files?
[09:29] <Boyette> empty
[09:29] <Peace-> Boyette: screenshot
[09:30] <Boyette> https://prnt.sc/ip8iy2
[09:30] <flocculant> this is why I use ppa-purge :D
[09:30] <Peace-> Boyette: paste even this  files
[09:30] <flocculant> Boyette: try this 
[09:30] <Peace-> flocculant: did not worked with ppa-purge
[09:30] <Peace-> flocculant: we tried with tat before
[09:30] <flocculant> because other ppa's were knackered
[09:31] <Peace-> Boyette: paste even the contents of /etc/apt/source.list 
[09:31] <flocculant> re-add the videolan ppa, update, install vlc, ppa-purge the videolan ppa
[09:31] <Peace-> Boyette: i mean the file
[09:32] <Boyette> https://pastebin.com/CFiPgGLY
[09:33] <Peace-> ok the main repo file seems quite fine
[09:34] <Peace-> mmm this is strange 
[09:35] <Peace-> it should install the 3 version instead of the 4 so there sould be another file of videolan that does that error 
[09:35] <Boyette> ill give u full output
[09:36] <Boyette> https://pastebin.com/nUpfLyBf
[09:36] <Boyette> so flocculant is saying
[09:36] <Boyette> to use ppa-purge
[09:37] <Boyette> maybe we need to still do that?
[09:37] <Peace-> try that 
[09:37] <Peace-> Boyette: could be fine 
[09:37] <flocculant> what I'm saying is add the ppa again first
[09:38] <Peace-> Boyette: that it shoulkd not required btw 
[09:38] <Peace-> we have removed all the crap repos so it should just install the old version of vlc
[09:38]  * flocculant wanders off now - good luck Boyette ;)
[09:38] <Boyette> but it doesnt
[09:38] <Boyette> its still trying to install v4
[09:38] <Peace-> i suspect that there are other ppas 
[09:39] <Boyette> how to find out?
[09:39] <Peace-> Boyette: try what said from flocculant
[09:39] <acheronuk> paste the current error please
[09:40] <Boyette> https://pastebin.com/nUpfLyBf
[09:40] <Boyette> well the sources.d is not containing it now so how to remove what is not there
[09:41] <Peace-> acheronuk: has removed all ppas from /etc/apt/source.list.d
[09:42] <Peace-> acheronuk: but when he try to install it says still 4.0 so there should be another file somewhere on etc/apt/sources.list there are no videoolan repo so :S
[09:42] <flocculant> not seen the sources.list at all yet
[09:43] <acheronuk> Boyette: can we see output of: dpkg --list | grep vlc
[09:43] <Boyette> yes sir
[09:43] <Boyette> https://pastebin.com/s3jACBFn
[09:44] <Boyette> interesting
[09:44] <Peace-> it just read form the ppa repo..
[09:44] <Peace-> so ...
[09:44] <acheronuk> Boyette: so you still have 4.0.0 there
[09:44] <Boyette> its removed
[09:44] <Peace-> xD
[09:44] <Peace-> clean the cache i guess acheronuk?
[09:45] <Boyette> how to proceed?
[09:45] <acheronuk> Boyette: dpkg doesn't agree with you at the moment 
[09:45] <Boyette> how to let dpkg agree?
[09:45] <Peace-> sudo apt-get clean  Boyette 
[09:46] <Peace-> now dpkg --list | grep vlc what does it say
[09:47] <Peace-> ah doesnt matter 
[09:47] <Peace-> Boyette: you have vlc still installed
[09:47] <Boyette> still the same
[09:47] <Peace-> Boyette: sudo apt-get remove vlc 
[09:47]  * acheronuk composes an apt line
[09:47] <Boyette> huh
[09:47] <Boyette> yes its installed again
[09:47] <Boyette> but i removed it before
[09:48] <Peace-> Boyette: after remove dpkg --list | grep vlc
[09:48] <Boyette> if i type
[09:48] <Boyette> vlc
[09:48] <Boyette> i get vlc
[09:48] <Peace-> it's a simple prolbem 
[09:48] <Boyette> but if i type purge vlc its saying its not installed
[09:48] <Boyette> so its there but its not there
[09:48] <Peace-> xD you have a mess system  i guess
[09:49] <acheronuk> gimme a minute or 2. then we'll try something
[09:49] <flocculant> I'd just wait a minute now and think 
[09:49] <flocculant> heh
[09:50] <Peace-> Boyette: sudo dpkg -r vlc 
[09:50] <Boyette> https://pastebin.com/Qbm2eUfh
[09:50] <Boyette> dpkg: warning: ignoring request to remove vlc which isn't installed
[09:50] <Peace-> but you have vlc 
[09:50] <flocculant> Boyette: from the previous list you can see that vlc isn't installed - but all the dependencies you had still are
[09:50] <Peace-> Boyette: run this : type vlc
[09:51] <flocculant> that is what the issue is currently
[09:51] <Boyette> check my latest pastebin
[09:51] <Peace-> flocculant: uh xD
[09:51] <Boyette> so we need to remove the dependancies ?
[09:51] <Peace-> Boyette: yes
[09:52] <flocculant> Boyette: just wait for acheronuk 
[09:52] <Boyette> ok
 dpkg: warning: ignoring request to remove vlc which isn't installed
[09:52] <Boyette> sounds funny
[09:52] <Peace-> btw sudo apt-get remove vlc* should work 
[09:52] <Boyette> lots were removed now
[09:52] <Peace-> btw sudo apt-get remove vlc* libvlc*  should work 
[09:53] <Boyette> now its really removed
[09:53] <Boyette> vlc command unkown
[09:53] <Peace-> even the libvlc ?
[09:54] <Boyette> latest command also removed libvlc still
[09:54] <Peace-> so now you can install again vlc xD 
[09:54] <Boyette> i think vlc 3 is coming now
[09:54] <Peace-> finally :D
[09:54] <Boyette> yes
[09:54] <Boyette> done
[09:54] <Boyette> and it runs
[09:55] <Boyette> it worked out guys
[09:55] <Peace-> Boyette:  btw YOU HAVE A BAD BEHAVIOR 
[09:55] <Peace-> DO NOT USE PPA if you are not able to manage them well 
[09:55] <Boyette> now  i learned .. IF dependencies are higher then actual version
[09:55] <Boyette> it will match version to dependencies
[09:55] <Boyette> interesting right :P
[09:55] <Boyette> not the other way around
[09:56] <Boyette> peace what is PPA  :P :P :P
[09:56] <Peace-> Boyette: well it's quite simple ppa are stored on that folder you now know
[09:56] <flocculant> Boyette: install with a ppa, remove with ppa-purge - works everytime for me
[09:56] <Boyette> ok
[09:56] <Peace-> flocculant: well in theory removing vlc it should remove even dependecens with purge
[09:57] <Peace-> if it did not the job the package is not well packaged
[09:57] <flocculant> no it won't 
[09:57] <Peace-> mmm with purge?
[09:57] <Boyette> this vlc 4 is buggy too much
[09:57] <flocculant> purging a package purges it - you then have to apt autoremove to get rid of dependencies
[09:57] <Boyette> told the developers but they dont listen to me
[09:57] <Peace-> with remove you right but with purge it should
[09:58] <flocculant> nope
[09:58] <Peace-> flocculant: bad memory of mine then :D
[09:58] <Boyette> they keep closing my tickets and tell me its not reproducable
[09:58] <acheronuk> apt-get install libvlc-bin=3.0.1-2ubuntu1 libvlc5=3.0.1-2ubuntu1 libvlccore9=3.0.1-2ubuntu1 vlc-bin=3.0.1-2ubuntu1 vlc-data=3.0.1-2ubuntu1 vlc-l10n=3.0.1-2ubuntu1 vlc-plugin-base=3.0.1-2ubuntu1 vlc-plugin-notify=3.0.1-2ubuntu1 vlc-plugin-qt=3.0.1-2ubuntu1 vlc-plugin-samba=3.0.1-2ubuntu1 vlc-plugin-skins2=3.0.1-2ubuntu1 vlc-plugin-video-output=3.0.1-2ubuntu1 vlc-plugin-video-splitter=3.0.1-2ubuntu1 vlc-plugin-visualization=3.0.1-2ubuntu1
[09:58] <flocculant> purge removes package and IT'S conf files
[09:58] <acheronuk> try that. may or may not work
[09:58] <Peace-> acheronuk: so basd you write down that line LOL
[09:59] <acheronuk> basd?
[10:00] <Peace-> flocculant: so purge autoremove
[10:00] <flocculant> mmm
[10:00] <Boyette> thx a lot guys
[10:00] <flocculant> but ppa-purge does all the work for you ;)
[10:00] <acheronuk> it does.
[10:01] <flocculant> :)
[10:01] <acheronuk> which is manually what my apt line is doing :P
[10:01] <acheronuk> or would have
[10:01] <flocculant> acheronuk: yup :)
[10:02] <Peace-> acheronuk: poor guy so much work you did :(
[10:02] <flocculant> Boyette: so in summary - don't randomly add ppa's, if you do ppa-purge is your friend
[10:02] <Peace-> i was trying to do purge infact on vlc package
[10:02] <flocculant> anyway - off to the market goes me
[10:03] <Peace-> and it leaves still those libraries
[10:03] <acheronuk> Peace-: not that much. mostly some sed and find/replace in a text editor
[10:03] <Peace-> flocculant: bb
[10:03] <Peace-> acheronuk: sed :D awk love stuff
[10:04] <flocculant> Peace- Boyette for the record - I know for sure that ppa-purge worked to do it as I installed the crap vlc and purged it all ;)
[10:04] <flocculant> took about 3 minutes 
[10:04] <Peace-> flocculant: :D i am bored of ppa xD i used this sytem for 2 years without update :D
[10:05] <Peace-> now there are not update anymore so installed 18.04 and it did not boot
[10:05] <Peace-> xD
[10:05] <Boyette> well
[10:05] <flocculant> I'm in the xubuntu team - I use our officialish ppa's all the time 
[10:05] <Peace-> was a very silly problem with uuid and fstab
[10:05] <Boyette> sometimes there is no release version for my ubuntu version
[10:05] <Boyette> so i have to add ppa manualy
[10:05] <Peace-> installed the miniso then kubuntu-desktop
[10:05] <Boyette> otherwise i cant install at all
[10:05] <Boyette> or missing dependencies
[10:05] <Boyette> many trouble u know
[10:06] <Peace-> Boyette: nah you just add many ppas 
[10:06] <Boyette> really
[10:06] <Peace-> with are not update 
[10:06] <Peace-> for 18.04 i guess
[10:06] <Peace-> and vlc daily well it works most of time 
[10:06] <Boyette> do u guys have a usenet client i can use for ubuntu
[10:06] <Boyette> im also having troubles finding that
[10:07] <flocculant> Boyette: I assume you mean that you try to get the newest version of something that's not in the repos - that's the way it works 
[10:07] <Boyette> most release versions are not working on ubuntu 18.04 so i have to be creative thats what i mean
[10:08] <Boyette> sometimes dependencies have higher version .. release packages dont like that
[10:08] <flocculant> most not working on 18.04? 
[10:08] <Boyette> yes
[10:08] <flocculant> if that's the case I assume you've reported bugs then
[10:08] <Peace-> Boyette: you are not creative , you are breaking ubuntu xD
[10:09] <Boyette> hehe
[10:09] <flocculant> Boyette: got an example of something not working? 
[10:09] <Peace-> that's normal first years on ubuntu 
[10:09] <Boyette> usenet client for example
[10:09] <Peace-> Boyette: on kde we use knode for that if it's correct what i understood
[10:09] <Peace-> i mean usenet
[10:10] <Boyette> i was trying to install spotlite 
[10:11] <Boyette> Error: Dependency is not satisfable: libssl0.9.8
[10:11] <flocculant> neither usenet nor spotlite are in the repo's 
[10:12] <Boyette> i just try to install from .deb
[10:12] <flocculant> Boyette: so I assume what you're doing is finding random things on the internet and trying to get them to work? 
[10:12] <Boyette> thats not random
[10:12] <Boyette> offcourse i know the application
[10:12] <Peace-> flocculant: xD
[10:13] <Peace-> Boyette: you can't install deb from internet like windows dude...
[10:13] <Peace-> there are repos.
[10:13] <Peace-> it's not safe 
[10:13] <flocculant> Boyette: yes - but you're having to download packages from some place on the net - then trying to make it work
[10:13] <Boyette> ok how to find repo for spotlite
[10:13] <Peace-> and you can break your ubuntu 
[10:13] <Peace-> Boyette: age?
[10:13] <Boyette> because i have difficulties finding repos 
[10:13] <Boyette> 30+
[10:13] <Peace-> wtf dude you are man ;D
[10:14] <acheronuk> ok. official website for this app?
[10:14] <Peace-> Boyette: repos .... contains every dependeces you need to install the pacckage so 
[10:14] <flocculant> Boyette: yup - I understand that - perhaps you should be trying to find apps that ARE supported which do the same job
[10:15] <Peace-> Boyette: if you try to install a single package it wont install untill you don't install every dependeces
[10:15] <Peace-> flocculant: btw there is snap package now that i have not investigated 
[10:16]  * flocculant doesn't snap 
[10:16] <Peace-> flocculant: which shouild be like somehow a packaged that contains every dependences
[10:16] <flocculant> yea I believe that's the idea
[10:16] <Peace-> i used to install spotify
[10:17] <Boyette> spotify is windows i think
[10:17] <Boyette> spotlite is ubuntu
[10:17] <flocculant> Boyette: what actually is spotlite?
[10:17] <Peace-> Boyette: no you can install on linux there is a snap pacakge
[10:17] <Boyette> how to find
[10:18] <Peace-> Boyette: oyu have not to find , SPOTIFY that is a music player btw   can be installed with this :    snap install spotify
[10:19] <Boyette> i dont need spotify music player
[10:19] <acheronuk> Boyette: please give us a link to spotlite's official website
[10:19] <Peace->  xD
[10:19] <Boyette> i need spotlite usenet client to search on server and cache it
[10:19] <flocculant> is it https://sites.google.com/site/ubuntulinuxgebruiker/spotlite
[10:19] <Boyette> http://www.spot-net.nl/spotlite
[10:20] <Boyette> http://www.spot-net.nl.vfcdn.net/downloads/spotlite/SpotLite%28v2%29Ubuntu.zip
[10:21] <Peace-> MMM NOT UPGRADE PROJECT?
[10:21] <flocculant> changelog shows last work in 2011 - you shouldn't be using that - looks dead to me
[10:21] <flocculant> anyway - I'm off now
[10:21] <Peace-> Ubuntu Linux - Maverick:
[10:21] <ducasse> Boyette: if you're looking for a usenet client, try pan
[10:21] <Peace-> so ultra ULTRA ULTRA OLD
[10:22] <ducasse> Boyette: it's in the repos, so supported
[10:23] <Boyette> well its dead
[10:23] <Boyette> but the only thing i can find
[10:24] <Boyette> usenet is also still usenet nothing different in that aswell
[10:24] <Boyette> irc is also not having any new clients
[10:25] <ducasse> you can also use thunderbird, it supports nntp
[10:25] <Peace-> knode it's for kde btw
[10:25] <acheronuk> it hard depends on a libssl version no longer in ubuntu. it's not going to work, no matter what
[10:27] <Boyette> yeah i know but thunderbird is already under heavy weight
[10:27] <Boyette> cant use hit for that
[10:27] <Boyette> thunderbird is already busy enough as emailclient
[10:28] <ducasse> have you tried pan?
[10:31] <Boyette> pan?
[10:32] <ducasse> 'apt show pan' - it's a newsreader
[10:33] <Boyette> installing now
[10:33] <Boyette> omg this looks linuxlike
[10:39] <Boyette> however
[10:45] <Boyette> seems very basic
[10:45] <Boyette> functionality
[13:12] <guardian> hello, what's a way to follow what's changing until the release of 1804?
[13:14] <TJ-> guardian: how do you mean? other than reading the ubuntu-devel mailing lists and IRC channel you mean?
[13:14] <guardian> I mean an overview of what's left to do
[13:18] <flocculant> guardian: the desktop team use trello to track what they're doing if that helps https://trello.com/b/lsBmkzPY/ubuntu-desktop-1804-cycle
[13:18] <guardian> thanks
[13:19] <flocculant> don't ask me about any of it though as I use xubuntu
[13:31] <guardian> I just want to get a feel of how what I'm using is done / will change before the release
[15:25] <antgel> Hi all, hope I can get some help, I started in #ubuntu then read the /topic *blush*
[15:25] <antgel> I just successfully upgraded my desktop from Xenial to Bionic, and then tried on my laptop. My laptop is failing as it's timing out waiting for the /boot/efi partition, and / or the resume partition, which appears to be encrypted (not sure if it was on Xenial). This used to work fine. Screen images at https://photos.app.goo.gl/DZ5yVaJWLKHrGr2O2 - anyone got any clues what I should try next?
[15:25] <antgel> I really don't understand why things are timing out - I can mount /boot/efi from recovery mode, so I don't know why my initramfs can't
[15:37] <TJ-> antgel: the crypto part is for encrypted swap - discount that for now
[15:38] <TJ-> antgel: try using "blkid /dev/sda*" to check the initrd shell can see the partitions -- if it can compare the UUID it reports to that being reported in the timeout messages
[15:40] <antgel> TJ-: So happy that there's life here! I'll do what you said - from recovery mode, correct?
[15:41] <TJ-> antgel: yes, I'm looking at your screenshot showing the initrd shell
[15:42] <antgel> The funny thing is, when I installed the laptop, I don't remember what options I chose. I would have thought I'd be more likely to choose encrypted /home over swap...
[15:43] <antgel> TJ-: blkid /dev/sda* returns nothing. But I have an SSD
[15:43] <antgel> Going to upload a photo of the blkid output
[15:43] <TJ-> cryptswap is creasted by default so RAM data can't be easily exfiltrated
[15:44] <antgel> TJ-: Okay, I added the output to the Google Photos album ^^
[15:45] <TJ-> antgel: what device is the system booting from because in the other photos I don't see any sign of a regular fixed disk, only USB devices and MMC
[15:45] <antgel> TJ-: It boots from the SSD /dev/nvme0n1
[15:46] <TJ-> antgel: ahhh... nvme 
[15:46] <antgel> TJ-: There is an interesting warning when the initramfs is created, will upload a photo
[15:46] <TJ-> antgel: So, my guess is the failing  initrd.img doesn't contain the nvme module /or/ it's not being auto-loaded
[15:47] <antgel> TJ-: Right. If that's the case, how is it that boot does carry on quite far? In fact, if I don't enter recovery mode, I get as far as a lightdm login screen, then it hangs
[15:47] <TJ-> antgel: at this point in the root shell from recovery you have it though... is that booting from the same kernel version - and hence the same initrd ?
[15:47] <antgel> TJ-: Yes
[15:47] <antgel> Indeed it is
[15:48] <TJ-> antgel: OK, that answers that, so the problem here is a timing issue let's assume.
[15:48] <TJ-> antgel: can you check if there are multiple NVME kernel modules now loaded: "lsmod | grep nvme" so we can be sure what is required when it does work
[15:48] <antgel> TJ-: No output
[15:49] <antgel> I'm surprised that nvme isn't complied in, rather than being a module, although it is over ten years since I compiled a kernel ;)
[15:50] <TJ-> antgel: try "grep nvme /proc/modules" - I'm on 16.04 and the nvme module is separate
[15:50] <antgel> TJ-: No output
[15:50] <TJ-> antgel: so possibly built-in for 4.15 on 18.04... let me check that
[15:51] <antgel> TJ-: Check out the warning in https://photos.google.com/share/AF1QipPWGrCKwNIAUFhu8N_WMhpa6x9rce03B7qyfOMtFzQG0clSS9CnYqq8p9CPop1iVg/photo/AF1QipNjyasu55rMbqEVS3M94xb56a4cQZbt1QkwWVwF?key=aTJtUkhSQ3gyQl9hVGFaQVFjS3ZjbG9tVEVDd3dn. Possibly relevant? I don't have any partition with UUID=7a1a7... No idea where that came from
[15:52] <TJ-> antgel: it's built in
[15:52] <antgel> TJ-: I see it in /boot/config..., CONFIG_NVME_CORE=y
[15:52] <antgel> Snap :)
[15:53] <TJ-> antgel: no, that's not the one, CONFIG_BLK_DEV_NVME=y is the one that controls the generic blockdev
[15:54] <antgel> TJ-: Ah. Also a 'y'
[15:55] <TJ-> yup. The missing RESUME= UUID should be the /decrypted/ cryptswap so you'll need to ensure that's unlocked and then look at it's /dev/mapper/ node to check what it's UUID is
[15:55] <TJ-> as in "blkid /dev/mapper/cryptswap1"
[15:56] <TJ-> but you need to check where it's host device is too, so look in /etc/crypttab to find that
[15:57] <antgel> TJ-: It's plain wrong. In /dev/mapper/cryptswap1, the UUID starts with a470...
[15:58] <TJ-> Try: "grep -rn  RESUME /etc/initramfs-tools/"
[15:58] <antgel> TJ-: I'm going to update the initramfs config, although heaven knows where it got that UUID from, and everything was working well up until the Bionic upgrade. I'm concerned that there's a lurking serious bug
[15:59] <antgel> TJ-: Yes, the one in initramfs-tools is wrong, as per the kernel warning
[16:00] <antgel> I'm going to update the initramfs-tools config and report back. But no idea why this causes so many fails as seen in one of my screen photos. Why should it need swap to mount /boot/efi...
[16:02] <TJ-> antgel: aha! /etc/fstab has a commented-out entry for the UUID bdde... swap ... which is what one of the TIME messages refers to, which suggests the initrd was built when that was mounted /or/ there's a left-over systemd unit/job for that device saved somewhere
[16:04] <antgel> TJ-: Nice catch. I didn't comment that out, this machine is a pretty vanilla install. And it's still not the 7a1a7... referred to in the initramfs config
[16:04] <TJ-> antgel: so piecing it together; originally the swap was a plain device, which was then encrypted so the original entry is commented out and a new entry for  crytpswap1 is added but for some reason systemd maintains a reference for the original device
[16:04] <TJ-> antgel: can you find the RESUME= line in the initramfs-tools config ?
[16:04] <antgel> I wish I remembered more about it. It's a relatively new install, since August 2017
[16:04] <TJ-> antgel: the initramfs-tools hook scripts use that
[16:05] <antgel> TJ-: Sure, way back. Just changed it
[16:05] <antgel> Rebuilt the initramfs and got cryptsetup: WARNING: target cryptswap1 has a random key, skipped. Do I care?
[16:05] <antgel> https://askubuntu.com/questions/982583/warnings-about-cryptsetup-on-new-ubuntu-17-10-installation suggests it's good
[16:06] <TJ-> antgel: OK, I wonder if because the initrd was defaulting to RESUME=/dev/dm-0 and that presumably is the root-fs it couldn't be accessed and therefore brought everything to a halt since the swap couldn't be fsck-ed or mounted
[16:06] <antgel> I'm rebooting now, firstly trying normal mode
[16:06] <TJ-> I think it'll work 
[16:07] <antgel> Nope. Going back into recovery. Better make sure I regenerated the initramfs properly
[16:08] <TJ-> not a lot you can wrong aside from regenerating the wrong one... it does have enough free disk space I assume? It's not getting truncated?
[16:08] <antgel> TJ-: Loads
[16:12] <TJ-> your photos obviously miss a lot of messages (main log starts at 2.02 seconds) but I don't see any sign of the nvme driver being active yet at the bottom of the screen an SD/MMC device is activated as sda which tells us the nvme hasn't been found at that point
[16:12] <antgel> TJ-: Wow. Running update-initramfs -k all -u, and now I get "W: initramfs-tools configuration sets RESUME=UUID=a4702..." which is or rather *was* correct - the UUID in /dev/mapper/cryptswap1 has changed!!!
[16:15] <TJ-> Not sure this is directly related but it's a fun read! https://bbs.archlinux.org/viewtopic.php?id=234349
[16:17] <antgel> TJ-: I really don't think it's that. It doesn't seem to have any problem with other partitions
[16:19] <TJ-> antgel: there's also this https://lkml.org/lkml/2017/12/14/907
[16:19] <TJ-> for which a possible workaround is the kernel command-line param: pcie_aspm.policy=powersave
[16:20] <TJ-> that's easy to test
[16:21] <antgel> TJ-: I'll give it a go. I have three kernels installed here. 4.15.0, 4.13.2, 4.11.12
[16:21] <TJ-> antgel: I have to go out for a whle; try this param and report back
[16:21] <antgel> I'll try 4.11.12
[16:21] <TJ-> antgel: try it wth 4.15
[16:21] <TJ-> antgel: try the param with 4.15 I mean
[16:21] <antgel> TJ-: Will do. Thanks for helping out, I'm totally bamboozled
[16:26] <antgel> TJ-: That param made no difference. Apparently every time I boot, the UUID of my encrypted swap changes
[17:03] <TJ-> antgel: have you tried jus disabling swap?
[17:05] <antgel> TJ-: I'll give that a go. I commented out the RESUME line in initramfs, but that just made it default to dm-0. Will try now and report back
[17:06] <antgel> I'm also going to try and create a Bionic live USB install
[17:06] <antgel> Just to see if it is a Bionic thing, or something totally broken in my install
[17:08] <TJ-> disabling swap should solve all the crypto-related issues but it doesn't explain the dependency failed for /boot/efi - unless that does depend on the swap mount or depends on local-file-system which depends on swap
[17:09] <TJ-> We used to see this around 14.04/16.04 too
[17:09] <TJ-> The changing UUID of swap was due to the crypto-device and the initrd was not parsing it as LUKS first so kept on recreating a pure swap in that physical partition, which then of course broke the other config
[17:10] <antgel> Commented out swap in /etc/fstab, same behaviour. Feels like something deep-rooted. Gonna try booting from USB
[17:10] <antgel> Oh, *wow*
[17:10] <TJ-> did you comment it out crypttab
[17:11] <antgel> No, just fstab
[17:11] <TJ-> crypttab is what references the physical partition
[17:11] <TJ-> fstab references the /dev/mapper/ node that crypsetup open would create
[17:11] <antgel> Okay, let's see
[17:12] <TJ-> remember to rebuild initrd too
[17:12] <antgel> I just don't understand how nobody else sees this. I have no custom config in that area
[17:12] <antgel> Yes
[17:12] <TJ-> we do see this cryptswap issue from time to time, but it's quite rare recently
[17:13] <TJ-> originally the /boot/efi message suggested the nvme device is missing but that is likely a red herring due to that mount depending on local-file-system
[17:14] <antgel> TJ-: Can I /msg for a second?
[17:17] <antgel> TJ-: Well, that improved my boot, then I got to my lightdm login and it froze... Back to recovery mode
[17:19] <TJ-> antgel: well that's what I call successful boot! I don't care about GUI, that's just an application!
[17:20] <TJ-> Fixing a GUI issue is easy, don't use recovery mode, instead boot with "systemd.unit=multi-user.target" and that'll start up properly but not start the GUI, then you can log-in as your regular user and fix things will full system capabilities
[17:20] <antgel> TJ-: Not really, I had been getting there before. And still have the /boot/efi error. Trying to get a screen grab
[17:21] <TJ-> /boot/efi isn't /vital/ unless you want to redo grub-install so don't let that put you off multi-user mode
[17:23] <antgel> I'm going to try a Bionic boot from USB, if it succeeds I'll debug it more. If it doesn't I'll try a downgrade (I'm not afraid)
[17:24] <TJ-> I don't think a downgrade is needed; that'd only cause more issues unless you wipe. The remaining issues aren't that serious and should be findable and fixable quite easily.
[17:25] <TJ-> antgel: it might be "sudo apt -f install" could fix some broken packages for example
[17:26] <antgel> TJ-: You haven't seen them. ;)
[17:26] <TJ-> antgel: I do data-recovery and forensics; I've remotely recovered servers in much worse state than this working from initrd :)
[17:27] <antgel> TJ-: And I've down-and-sidegraded many Debian-based systems :P
[17:28] <TJ-> the point is an in-place downgrade of packages will definitely break things
[17:28] <TJ-> so you'll end up compounding the existing situation
[18:07] <enyc> Hrrm --  Ubuntu 18.04 LTS will introduce e2fsprogs 1.43, and seemingly  enable ext4  64bit,metadata_csum  in LTS by default...  This is annoying as it makes disks incompatible with 16.04 LTS fsck ...
[18:09] <enyc> imho it would be nice that somebody consider updahing e2fsprogs in xenial-updates,  for compatibility therein...  (as Trust and Xenial has always had the necessary kernel support, its just e2fsprogs needs to be >= 1.43 grr)
[18:09] <enyc> (personally, i'd have preferred that default metadata_csum,64bit  came only after [debian]stretch/[ubuntu]bionic
[18:13] <TJ-> Sounds like a candidate for -backport
[18:22] <enyc> TJ-: also possible, whose going todo it, who requests it where/how, etc?
[18:23] <enyc> debian  already put 1.43.x e2fsprogs into  jessie-backports...  which ifgures, for same reasons
[18:25] <TJ-> enyc: create a bug report requesting it
[18:37] <enyc> TJ-: hrrrrrrm spotting https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874
[18:45] <enyc> Ooooooooooooo
[18:45] <enyc> https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/comments/4
[18:45] <enyc> TSO made explicit comment here -- Have Ubuntu THOUGHT about this explicitly  rather than decision by default?
[18:52] <enyc> My personal opinion is that turning it off by default makes sense (espcially given xenial situattion)
[18:52] <TJ-> Yes, it ought to be opt-in 
[18:59] <enyc> TJ-: is there a way to "add" canonical to existing bugreport?  can you create a new bugreport getting canonical to review  tytso (ext4 _maintainer!!!_)'s comment?
[19:02] <TJ-> enyc: add a comment to the bug to report it affecting 18.04 etc, I'll get someone to look at it next week
[19:03] <TJ-> I've changed the status and importance
[19:03] <TJ-> I guess we should check whether Ted did go and disable it in the Debian release 
[19:04] <enyc> didn't, stretch enables by default
[19:04] <enyc> and debian jessie-backports  backported e2fsprogs
[19:05] <enyc> but as  Ted?(tytso)  points out Debian vs Ubuntu  different user-base-expectancy to an extent....
[19:05] <enyc> and there isn't much advantage in adding it tbh
[19:08] <TJ-> if you don't express your reasons for wanting it the package maintainers aren't going to have anything to consider. If there's an important use-case then report it
[19:08] <enyc> TJ-: can you set the importance on 1365874 too, and i'll put intelligent comment in there too when I'm ready / checked my facts (backport to 16.04 certainly warranted).
[19:09] <enyc> should be abli to do in hour or so, need to get F00D now =)
[19:09] <TJ-> enyc: I'd expect this could cause problems for dual/multi-boot systems
[19:18] <enyc> TJ-: thats a good point, ill think and sumbit to both shortly...
[19:19] <enyc> TJ-: have got into ubuntu,  please add any tay to bug 1365874 too,  i'll comment shortly,  off to dinner now =).
[19:40] <antgel> TJ-: I'm in xorg! That'll be 1) me forgetting I was using an xorg PPA, and not all of the packages upgrading cleanly 2) some weird thing with the resolv.conf symlink location in /run changing... Now to re-enable swap and pray
[19:41] <TJ-> antgel: self-inflicted wounds then?
[19:43] <antgel> TJ-: Well, at least some of them. No idea what's meant to change the resolv.conf symlink, but it didn't happen for me :)
[19:43] <TJ-> /etc/resolv.conf should point to /run/resolvconf/resolv.conf 
[19:44] <antgel> TJ-: Ugh. In the live ISO, it pointed to ../run/systemd/resolve/stub-resolv.conf. The path you mentioned wasn't there
[19:45] <TJ-> antgel: that is correct, I was about to say ... unless the system is using systemd-resolved
[19:46] <TJ-> antgel: it depends on which release of Ubuntu was first installed and what it used. Upgrades will continue using that so resolveconf is the usual one
[19:47] <antgel> Couple of takeaways. Having decided to "grow up" and stick with LTS after years on the bleeding edge of Debian, the PPAs can murder during an OS upgrade. Also, loads of new stuff happens that one doesn't know about. :)
[19:48] <antgel> TJ-: I'm really grateful to you for helping me here. I can open bugs on the other stuff, at least I have a workstation. Any donation I can make?
[19:50] <TJ-> antgel: help others when you can :)
[19:55] <antgel> TJ-: I used to spend a lot of time on IRC. Sadly, real life limits the time I have. I contribute open-source where I can
[19:57] <TJ-> You can teach people not to use random PPAs and forget about them at release-upgrade time :D
[20:00]  * antgel nods sagely, and vows to better-document his setup
[20:03] <antgel> In my defence (such as it is), I needed that ppa, as I'm lucky enough to have a Thinkpad T470, and the Xenial xorg didn't want to play ball. It was the "edgers" or something. Anyway 18.04 is looking super-awesome. Fixed some deprecated stuff in my tmux config, added the keyboard selector and pulseaudio plugins to xfce4-panel, and I'm away!
[20:10] <TJ-> yeah, XFCE is a much better environment that Gnome :)
[20:39] <enyc> TJ-: posted on both
[20:39] <enyc> TJ-: thankyou for intervening importance/tags etc.
[20:40] <TJ-> enyc: I'll get someone from -devel to look at it and provide feedback/rationale in the week if I can
[20:41] <enyc> TJ-: good =)
[21:58] <mcm_> where does wayland write its log? i can't find anything under /var/log. also the /var/log/gdm3 folder seems to be empty
[23:32] <enyc> TJ-: tytso responded one one bug report, very helpfully
[23:33] <enyc> TJ-: given what he's saying, it creates interesting questions about  applying to  -updates  rather than -backports