[01:22] <mcm_> can i see why a package has been removed since 17.10 ?
[01:22] <mcm_> in this case: https://packages.ubuntu.com/source/artful/pygpgme
[01:23] <mcm_> that delivers the package python-gpgme.
[01:23] <mcm_> and is suggested from nautilus-dropbox and python-samba packages
[01:24] <mcm_> but does not have an installation candidate: 'Package python-gpgme is not available, but is referred to by another package'
[01:25] <dax> https://launchpad.net/ubuntu/+source/pygpgme/+publishinghistory => "(From Debian) RoQA; obsolete, abandoned upstream; Debian bug #876844"
[01:32] <mcm_> dax, thanks. 
[01:34] <mcm_> ok. then will open a bug for nautilus-dropbox, so it suggest python-gpg. however it seems that python-gpg does not satify the dependency of dropbox installer.
[01:34] <mcm_> the dropbox installer still gives me the python-gpgme is not installed, after installing the package 'python-gpg'
[01:59] <tomreyn> maybe "python-gpg" is not the same as "python-gpgme"?
[03:41] <FurretUber> Should gnome-software warn me when a package failed to install?
[03:53] <lotuspsychje> FurretUber: what did you install?
[03:54] <FurretUber> I tried to install megasync from https://mega.nz
[03:54] <FurretUber> I tried to install the deb package from 16.04 and it failed
[03:55] <FurretUber> https://paste.ubuntu.com/p/wqh8chG8Cx/
[03:55] <FurretUber> This is from trying to install using terminal
[03:57] <FurretUber> gnome-software gave no feedback, so I was wondering if it installed instantly at the first moment. It looks like similar to this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1694076
[04:02] <lotuspsychje> !info megasync
[04:04] <FurretUber> This is right, megasync is not in the repositories, but I suppose gnome-software should give feedback the installation went wrong, even for packages not in the repositories
[04:05] <lotuspsychje> FurretUber: we dont support external software/ppa's so that mean you cant officially bug against this
[04:05] <lotuspsychje> FurretUber: what you can do, is a wish bug with your idea
[04:13] <krytarik> FurretUber, lotuspsychje: LP bug 1619791
[04:15] <FurretUber> Thank you, this is exactly what is happening
[04:17] <lotuspsychje> nice find krytarik 
[05:40] <lotuspsychje> hey alkisg ; )
[05:40] <alkisg> Hey lotuspsychje, long time no see :)
[05:41] <alkisg> Hope you're doing well
[05:41] <lotuspsychje> yeah im fine mate what about you?
[05:41] <alkisg> All well here!
[05:41] <lotuspsychje> testing bionic heavy here :p
[05:41] <lotuspsychje> lets hope this results in great experience at final
[05:42] <alkisg> Same.. I installed bionic/ubuntu-mate-desktop in a raspberry starting with debootstrap, as there's no installer yet
[05:42] <lotuspsychje> aha
[05:42] <lotuspsychje> readed an article bout that recently
[05:42] <alkisg> My problem is that network manager says "device unmanaged" for the NIC, while I can connect fine if I use dhclient
[05:42] <alkisg> And I can't figure out how to tell it to actually manage it :)
[05:42] <katnip> anyone have inxi installed and used in irc?
[05:43] <lotuspsychje> katnip: sudo apt install inxi
[05:43] <alkisg> lotuspsychje: do you have ifupdown installed? I thought it wouldn't be installed by default in 18.04, yet it is...
[05:45] <lotuspsychje> alkisg: ifupdown:
[05:45] <lotuspsychje>   Geïnstalleerd: 0.8.17ubuntu1
[05:46] <lotuspsychje> katnip: use in irc is not reccomended
[05:46] <lotuspsychje> !paste | katnip 
[05:49] <lotuspsychje> alkisg: server got netplan now right?
[06:03] <alkisg> lotuspsychje: netplan isn't installed here
[06:03] <alkisg> (desktop)
[06:07] <lotuspsychje> kk
[06:09] <lotuspsychje> alkisg: see this? http://news.softpedia.com/news/you-can-now-install-ubuntu-18-04-lts-on-your-raspberry-pi-3-model-b-plus-with-raspex-520450.shtml
[06:09] <lotuspsychje> bbl
[06:10] <alkisg> Cool; although I prefer stock distributions rather than customized...
[06:19] <alkisg> Ah netplan.io is installed, I was looking for netplan
[06:28] <alkisg> Yeah that was it, /etc/netplan/01-network-manager-all.yaml missing in debootstrapped installation
[06:28] <alkisg> I'll file a bug report
[07:17] <auctus> not sure if this is an ubuntu or a 18.04 issue, but im using 18.04 -- i sometimes use an external display with my laptop, and when i unplug it, sometimes itll switch back to the laptop display
[07:17] <auctus> but sometimes it wont
[07:17] <auctus> and i dont know how to turn the laptop display back on other than 1] power down 2] plug it back into external
[07:17] <auctus> any ideas as to how to switch back to laptop display without being able to see the displays dialog
[12:18] <MrKeuner> Hi, is rkhunter broken in 18.04? sudo rkhunter --update -> Invalid WEB_CMD configuration option: Relative pathname: "/bin/false"
[12:19] <MrKeuner> is it disabled until a release? 
[12:19] <Faux> Unlikely. Much more likely it's broken.
[12:20] <MrKeuner> Also noticed, rkhunter: Please inspect this machine, because it may be infected. on my 18.04 boxes 
[12:22] <Faux> https://sources.debian.org/src/rkhunter/1.4.6-2/debian/patches/06_disable-updates.diff/?hl=41#L41 looks like --update has been intentionally crippled.
[12:26] <tomreyn> Pissbily related: Rootkit Hunter release 1.4.6 (February 20th 2018) [..]  Rootkit Hunter release 1.4.6 obsoletes all previous releases.
[12:26] <tomreyn> http://rkhunter.sourceforge.net/
[12:29] <MrKeuner> What does obsoleting all prev. releases mean? they break backward compatibility? does that mean do a remove --purge and reinstall? That does not explain the /bin/false flag...
[12:32] <tomreyn> maybe i jumped to conclusions, and they did not actually break backward compatibility
[12:34] <tomreyn> but the debian patch which Faux pointed out surely disables data updates (my assumption was that it does so as the new data is not compatible to this rkhunter release, or wont be in the future) and causes the /bin/false WEB_CMD message you got to read.
[12:34] <tomreyn> MrKeuner: ^
[12:35] <MrKeuner> Okay. I guess I'll have to sit on this for a while. Is there a way to subscribe to ubuntu rkhunter maintainers mailing list?
[12:35] <tomreyn> MrKeuner: a better patch would probably have been to disable the data(base) update functionality altogether and just respond with a user friendly message stating so.
[12:36] <tomreyn> (i guess you could file a bug requsting this)
[12:37] <tomreyn> rkhunter is apparently synced directly from debian so you'd better subscribe to their matching mailing lists, if any. but i don't expect this to change in bionic unless bugs are filed.
[12:38] <tomreyn> (and even then it's not guaranteed)
[12:38] <MrKeuner> sure. I'll do the right thing and report on both bug trackers
[12:38] <MrKeuner> thanks
[12:38] <katnip> what is friendly recovery?
[12:39] <tomreyn> MrKeuner: thanks. once you did, for the meantime, maybe just use the upstream release. it's just a bunch of perl and shell scripts anywas.
[12:39] <tomreyn> *anyways
[12:41] <tomreyn> !info friendly-recovery | katnip
[12:42] <katnip> ok ty
[12:42] <tomreyn> i guess it's the text based menu (ncurses?) which shows up when you select the recovery option during boot.
[12:42] <tomreyn> i mean at the grub menu, not during boot.
[12:44] <MrKeuner> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893169 is referencing itself for the details?
[12:45] <MrKeuner> Nevermind I'll take it to #debian
[13:01] <mifritscher> hi...
[13:02] <mifritscher> why the hell does ubuntu 18.04 go into suspend automatically?!
[13:02] <mifritscher> and why this behavior is even activated during upgrade 16.04->18.04?!
[13:03] <mifritscher> this is very, very bad
[13:05] <mifritscher> luckily this is only a test installation and I do have an ipmi, else I would be screw up now
[13:05] <MrKeuner> mifritscher, I noticed that too. In my case it only happens if no users is logged in. Probably there is a gdm setting you can change for that
[13:06] <mifritscher> so I can't even set it system wide via the normal GUI?!
[13:07] <mifritscher> (I just set it back in my account)
[13:08] <mifritscher> it is very, VERY bad for me as the system is used as a qemu host - and there isn't even a warning in the upgrade process
[13:09] <MrKeuner> Sure, I'd suggest reporting it 
[13:10] <mifritscher> yes
[13:21] <mifritscher> done
[13:21] <mifritscher> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1760102
[13:21] <MrKeuner> Thank you
[14:22] <tomreyn> mifritscher: i'm sure you're aware that 18.04 is not released, yet, and thus cannot have the same level of maturity that e.g. 16.04.4 has by now.
[14:23] <mifritscher> yes - as I've written in the bug report (alpha/beta)
[14:23] <tomreyn> (and thanks for reporting this bug)
[14:23] <tomreyn> hadnt read it yet, justthe chat here
[14:55] <AuroraAvenue> Soz, which one is this chap, again ? https://plus.google.com/+WillCooke
[14:56] <AuroraAvenue> My question was where are we up-to with the tour.ubuntu.com part of Bionic beaver ? and its expo thereof....
[16:12] <enyc> hehehe
[16:12] <enyc> my 18.04 test on btrfs, has broken itself on update lol ;p
[18:15] <donofrio> why would updated gnupg and friend's packages cause apt-add-repository issues with ipc talking to dirmngt?
[19:04] <albert23> donofrio: is dirmngr actually running? If not, maybe it works if you start it manually like this: dirmngr --daemon --homedir /home/ubuntu/.gnupg (with you username of course)
[19:36] <donofrio> albert23, yes I started manuallay but its not talking to it
[19:36] <donofrio> oh I'll try the switches
[20:36] <terminalator> Which kernel does 18.04 ship?
[20:37] <powersj> terminalator: 4.15
[20:38] <terminalator> I see, great. Thanks for clearing things up powersj 
[20:38] <powersj> https://packages.ubuntu.com/source/bionic/linux
[20:38] <terminalator> Thanks, bookmarked it ;)