[04:02] <Victolabs> Hi, how can i change themes in 16.04 LTS?
[04:06] <Victolabs> Apologies for the sudden leave, did anyone answer my question or?
[07:53] <zzarr> hello! I get a message dialog telling me that I have "Insufficient privileges" when trying to connect to a WiFi network from lightdm
[07:54] <zzarr> I have a bootstraped install on a ARM system, I have the correct drivers installed
[09:23] <lordievader> Good morning.
[09:41] <damascene> Good morning lordievader
[09:42] <lordievader> Hey damascene
[09:42] <damascene> Hey ☺
[11:55] <BluesKaj> HI folks
[12:27] <marlinc> Hello!
[12:43] <stephanbuys> hi all, I'm experimenting with 16.04 and I was wondering if someone could point me to the udev rule thats naming all my wireless adapters to wlxXXXXXXXXXX (where XXXXXXXX is the Mac address), I'd like to revert to more traditional wlan0, or something
[12:45] <BluesKaj> stephanbuys, that's the systemd udev naming system at work here
[12:46] <stephanbuys> BluesKaj: yeah, I'm just wondering where to start looking, currently looking at https://www.freedesktop.org/software/systemd/man/systemd.link.html to maybe override it
[12:49] <BluesKaj> stephanbuys, well. I'm living with it since it doesn't interfere with any processes so far.
[12:52] <lordievader> stephanbuys: This is the document you are looking for: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
[12:52] <stephanbuys> BluesKaj: found it I think the culprit is /lib/systemd/network/90-mac-for-usb.link
[12:53] <lordievader> Hmm, on second read, you might have a different problem indeed.
[12:55] <stephanbuys> lordievader: the issue is the file's naming priority uses 'mac' as a last option, its very unpredictable, I've overridden it an now at least I can predict the names, which is a big deal for us (testing for future appliance based on 16.04)
[12:57] <stephanbuys> 'NamePolicy=kernel database onboard mac' (the default) is very unfriendly to our usecase, but 'NamePolicy=kernel database onboard slot path' mac fixes it
[13:29] <soee> anyone had this problem:
[13:29] <soee> Segmentation fault (core dumped)
[13:29] <soee> Czytanie list pakietów... Gotowe
[13:29] <soee> E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -e /usr/bin/appstreamcli; then appstreamcli refresh > /dev/null; fi'
[13:29] <soee> E: Sub-process returned an error code
[13:29] <soee> uh, sorry for direct paste
[13:29] <lotuspsychje> soee: did you add ppa's of any kind?
[13:30] <soee> lotuspsychje: i have few but nothing new since few weeks and all worked just fine so far
[13:31] <lotuspsychje> soee: wich packagename is this, that segmentation faults?
[13:31] <soee> lotuspsychje: don't kow, i have this error whe executing: apt update
[13:32] <lotuspsychje> soee: please uninstall all ppa's first before you apt-get update
[13:32] <lotuspsychje> soee: your on 16.04?
[13:32] <soee> yes
[13:32] <lotuspsychje> ok
[13:32] <lotuspsychje> !ppapurge | soee
[13:32] <lotuspsychje> soee: we cant make you file a bug, if you have external ppa's added..
[13:33] <soee> sure thing, ill play with those ppa
[14:14] <lotuspsychje> !info linux-image-generic xenial
[15:39] <bumbar_> i'm using ubuntu 16.04, can i follow this guide to encrypt home? https://help.ubuntu.com/community/PostInstallationEncryption
[15:47] <genii> Yes
[15:50] <tmartins> Any plans to fix this: https://bugs.launchpad.net/ecryptfs/+bug/1328689 ?
[15:50] <tmartins> ;-)
[15:53] <bumbar_> so it should work with a workaround? also, if it doesn't, i won't lose data right? like a partial encryption
[15:53] <lotuspsychje> tmartins: thats for 14.04, you got the same on xenial?
[15:54] <tmartins> It is still present on 15.10... I'll try it on Xenial today...
[15:54] <tmartins> and update the bug report...
[15:54] <lotuspsychje> tmartins: ok great
[15:55] <lotuspsychje> tmartins: maybe a fresh install could also help
[15:55] <lotuspsychje> tmartins: i had kernel issues on do-release-upgrade -d from wily to xenial
[15:55] <tmartins> sure, I have fresh install from daily server ISO
[15:55] <tmartins> =)
[15:56] <lotuspsychje> cool
[15:58] <tmartins> Still a BUG on Xenial!
[16:07] <lotuspsychje> tmartins: ok update that bug, or file a new one
[16:07] <tmartins> Already did... Bug report updated
[16:07] <lotuspsychje> teward: whats do you suggest on this one?^ new or update the old
[16:09] <teward> hm?
[16:09]  * teward reads up
[16:12] <teward> lotuspsychje: if it's the same exact bug, then updating the older bug, and indicating that they're affected in comments (as well as marking it as affecting them - https://bugs.launchpad.net/ecryptfs/+bug/1328689/+affectsmetoo) is likely the correct way to approach it
[16:12] <teward> thank you ubottu for being weird
[16:12]  * teward glares at the bot
[16:12] <lotuspsychje> teward: hehe, ok tnx mate
[16:13] <lotuspsychje> tmartins: ^
[16:15] <tmartins> :-)
[16:15] <lotuspsychje> tmartins: lets hope it gets cleaned out in april
[16:18] <tmartins> Yes! Otherwise I'll mail Mark...   =P
[16:18] <lotuspsychje> lol