[14:59] <slashd> o/
[15:00] <sil2100> o/
[15:00] <rbasak> o/
[15:02] <sil2100> Not much on the agenda I guess, I removed the item regarding TB actions for the new DMB members
[15:03] <rbasak> I'd like comment on https://lists.ubuntu.com/archives/devel-permissions/2018-April/001275.html please
[15:03] <sil2100> I guess we also have all the ML and IRC permissions set up?
[15:03] <rbasak> I started writing up https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Checklist_after_a_DMB_election
[15:04] <sil2100> Good idea!
[15:04] <slashd> rbasak, good idea indeed
[15:04] <sil2100> rbasak: are you still editing it or can I add something?
[15:04] <rbasak> I'm not editing it. Please take the lock.
[15:08] <micahg> o/
[15:09] <sil2100> Does it make sense to start a formal meeting if there's no actions for the meeting?
[15:09] <micahg> rbasak: you want feedback on the ML?
[15:09] <micahg> not realy
[15:11] <rbasak> micahg: I like to reach consensus on landing the changes, or a modified version of it. I think we have quorum here now so we could just do it here perhaps?
[15:11] <rbasak> Or the ML is also fine.
[15:11] <rbasak> I don't mind if we use meetingology or not
[15:11] <sil2100> Feedback on what?
[15:12] <rbasak> My ML archive URL above
[15:12] <sil2100> Ah, missed that one
[15:12] <sil2100> Thanks
[15:13] <micahg> rbasak: we've generally avoided checklists, I'm wondering if people will glance at the bullet points and think those are the only reasons for applying
[15:13] <sil2100> Let me see how the template looks now, since I last looked at it quite some time ago
[15:17] <sil2100> I guess there is risk that would happen - maybe we should put those bullet-points as examples in the template, not as finished points?
[15:18] <sil2100> Sure, some might copy-paste those as well, but yeah
[15:18] <sil2100> It's the same when we ask them the same thing on meetings
[15:19] <micahg> right, but there isn't not a guide for new applicants :)
[15:19] <micahg> s/isn't/it's/
[15:22] <rbasak> I tried to keep it clear that it isn't rigid
[15:23] <rbasak> micahg: I don't see anything I've proposed as a checklist. Which part in particular do you think is one?
[15:23] <micahg> reasons for applying
[15:29] <micahg> I have to run, I'll check the backlog when I get home
[15:29] <slashd> I don't see it as a checklist too, it's just guidelines to help evaluate when one should apply and to also show what are DMB expectations when applying.
[15:31] <rbasak> It's why I said "Remove any reasons that don't apply, add any extra reasons and edit as
[15:31] <rbasak> needed"
[15:31] <rbasak> I wanted it to be clear that they can change it.
[15:32] <rbasak> micahg: how about I add a sentence to that, saying "These examples are the common and expected case, but are not a hard requirement for applications" or similar?
[15:41] <slashd> rbasak, that might be a good idea in case others see it as a checklist too.
[15:47] <sil2100> I'm fine with both versions - the one proposed now or the first one
[15:51] <slashd> same here
[15:52] <rbasak> Thanks. I'll see what micahg says when he gets back.
[16:30] <mdeslaur> \o
[16:31] <ratliff> #startmeeting
[16:31] <meetingology> Meeting started Mon Jun  4 16:31:59 2018 UTC.  The chair is ratliff. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:31] <meetingology> Available commands: action commands idea info link nick
[16:32] <ratliff> The meeting agenda can be found at:
[16:32] <ratliff> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:32] <ratliff> [TOPIC] Announcements
[16:32] <ratliff> There are no announcements this week.
[16:33] <ratliff> [TOPIC] Weekly stand-up report
[16:33] <ratliff> jdstrand: you're up
[16:33] <jdstrand> hi!
[16:33] <jdstrand> This week I plan to:
[16:33] <jdstrand> - hopefully turn on resquashfs tests. electron upstream is now fixed. A bit of review-tools work is needed to add an override mechanism
[16:33] <jdstrand> - iterate on various PRs I submitted last week related to udev
[16:33] <jdstrand> - adjust snap-confine to always use a device cgroup
[16:33] <jdstrand> - work through design considerations with niemeyer wrt update-alternatives (or something similar) snapd interface
[16:33] <jdstrand> - go through the anbox design and think through what proper confinment might look like
[16:33] <jdstrand> - pick up review-tools snap USNs phase1/part ii work as have time
[16:33] <jdstrand> that's it from me. mdeslaur, you're up
[16:34] <mdeslaur> I'm still in the happy place
[16:34] <mdeslaur> I published exempi updates this morning
[16:34] <mdeslaur> and am in the process of publishing an apport update for 14.04
[16:34] <mdeslaur> after that, I'll work on more updates
[16:34] <mdeslaur> that's about it, sbeattie, you're up
[16:34] <sbeattie> I'm in the happy place this week
[16:35] <sbeattie> I'm working on the git update, it's kind of gnarly.
[16:35] <sbeattie> I have some internal things to look at
[16:36] <sbeattie> I have the usual kernel cve triage bits to work on
[16:36] <sbeattie> That's probably it for me. jjohansen, over to you
[16:37] <jjohansen> I am working on finishing getting together the apparmor pull request for 4.18.
[16:37] <jjohansen> kernel ompatibility networking patches for the apparmor 2.x series
[16:37] <jjohansen> reviewing mjg's networking patches
[16:37] <jjohansen> and also working on the apparmor 3.0 release
[16:38] <jjohansen> we still have some caching bugs to working out, subset of features support, and uhmm something else that is slipping my mind atm
[16:38] <jjohansen> sarnold: you are up
[16:38] <sarnold> I'm on bug triage this week
[16:38] <sarnold> happy to review any apparmor patches that fall out of ^^
[16:38] <sarnold> and will finish the google gce .. something .. MIR this week
[16:39] <sarnold> hopefully make good progress on the next one on the list, bug triage is usually not terrible
[16:39] <sarnold> that's it for me, chrisccoulson?
[16:39] <chrisccoulson> I'm expecting a chromium update this week. I'm still expecting thunderbird too
[16:40] <chrisccoulson> I also need to spend some time getting ready for the next thunderbird update (from 52.x to 60.x)
[16:40] <chrisccoulson> I'm not expecting to have to spend time on rust, so other than that I'll be free to work on other things :)
[16:40] <chrisccoulson> that's me done
[16:41] <ratliff> I'm on community this week.
[16:41] <jdstrand> chrisccoulson: re rust> yay!
[16:41] <ratliff> I have internal work relating to https://grnh.se/b2d0bf371 (Ubuntu Security Engineer job posting) and other internal tasks.
[16:41] <ratliff> leosilva: on to you
[16:41] <leosilva> I'm on CVE-triage this week
[16:42] <leosilva> I have procps update to USN for precise-esm
[16:42] <leosilva> and I'm working on liblouis update
[16:42] <leosilva> I also plan to get other updates to do.
[16:42] <leosilva> that's it from me.
[16:42] <leosilva> ratliff: it's back to you
[16:43] <ratliff> thanks, leosilva
[16:43] <ratliff> [TOPIC] Highlighted packages
[16:43] <ratliff> The Ubuntu Security team suggests that contributors look into merging Debian security updates in community-supported packages. If you would like to help Ubuntu but are not sure where to start, this is a great way to do so.
[16:43] <ratliff> See http://people.canonical.com/~ubuntu-security/d2u/ for available merges and https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details on preparing Ubuntu security updates. If you have any questions, feel free to ask in #ubuntu-hardened. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:43] <ratliff> [TOPIC] Miscellaneous and Questions
[16:43] <ratliff> Does anyone have any other questions or items to discuss?
[16:45] <ratliff> jdstrand, mdeslaur, sbeattie, jjohansen, sarnold, chrisccoulson, leosilva: Thanks!
[16:46] <ratliff> #endmeeting
[16:46] <meetingology> Meeting ended Mon Jun  4 16:46:03 2018 UTC.
[16:46] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-06-04-16.31.moin.txt
[16:46] <leosilva> thanks ratliff!
[16:46] <jdstrand> thanks ratliff :)
[16:46] <mdeslaur> thanks ratliff!
[16:46] <sarnold> thanks ratliff!
[16:48] <jjohansen> thanks ratliff
[16:51] <sbeattie> ratliff: thanks!
[16:51] <mdeslaur> thanks ratliff!
[16:52] <mdeslaur> ratliff: thanks!


[02:24] <wgrant> superm1: gsd is screaming at me a lot now.
[02:24] <wgrant> Warning:          No symbols defined for <AB11> (keycode 97)
[02:24] <wgrant> And a few dozen related.
[02:49] <bryce> refreshed Ubuntu-X wiki a bit - https://wiki.ubuntu.com/X/
[06:41] <tjaalton> morning
[06:41] <tjaalton> ooh, pictures
[07:15] <tjaalton> sigh, can't find a reason why -intel doesn't pick the libdrm-intel1 dependency
[07:16] <tjaalton> unless it's the difference in compat between libdrm and drm-snapshot
[07:16] <tjaalton> other than that the diff is irrelevant
[08:15] <crevette> hello
[08:28] <tjaalton> hi
[08:39] <tjaalton> need to decide if we want to move XInput.h back in inputproto or not
[08:39] <tjaalton> 1.5 didn't move it, master did
[08:41] <crevette> I have a question about the consoles on tty1-6, it is displayed with a low resolution which is blurry on my laptop screen, it is possible to have it displayed in the native resolution?
[08:42] <crevette> this is not I use it everyday, but it would be better
[08:42] <tjaalton> which graphics hw?
[08:53] <crevette> Intel on thinkpad T61
[08:53] <crevette> which is funny it is worked one time when my xorg was broken :)
[08:54] <tjaalton> well, it might support kernel modesetting when 9.04 is out
[08:57] <crevette> and without mosetting is it possible to have it working or not ?
[08:59] <tjaalton> I don't know what blurry means in this case
[08:59] <tjaalton> it's low-res by default
[09:00] <tjaalton> and using vesafb-tricks bring other problems
[09:14] <crevette> okay
[09:14] <crevette> salut seb128
[09:14] <seb128> lut crevette
[09:14] <crevette> tjaalton, I'll wait for a sane method to come up and I'll see
[09:15] <crevette> tjaalton, this is a TTM that make the Fedora 10 performance better on intel than ubuntu? I've seem some people stating the performance on F10 was back to a good framerate
[09:16] <tjaalton> crevette: GEM
[09:16] <crevette> ah GEM sorry
[09:16] <tjaalton> it's just a requisite for KMS
[09:16] <tjaalton> and other things
[09:17] <tjaalton> well, helps performance too
[10:23] <seb128> hey tseliot
[10:23] <seb128> tseliot: no hurry for the gnome-desktop changes, the new version has a soname change too and that requires a transition, since I'm travelling tomorrow I'll probably not start on that today
[10:24] <crevette> seb128, you're moving to an ubuntu meeting ?
[10:24] <tseliot> seb128: ok, thanks
[10:24] <seb128> crevette: uds
[10:24] <tseliot> seb128: we'll meet at the uds then ;)
[10:25] <seb128> tseliot: right ;-)
[10:26]  * tseliot logs out to try driver 180.11
[11:20] <tseliot> tjaalton: are you (too) busy today?
[11:21] <tjaalton> tseliot: depends :)
[11:21] <tjaalton> I'll have lunch in a minute
[11:21] <tseliot> tjaalton: there's a new version of 180 for Jaunty: http://albertomilone.com/ubuntu/newlrm/pitti/jaunty/destination_jaunty1.txt
[11:22] <tseliot> which fixes a rather annoying problem
[11:22] <tjaalton> ok, I'll have a look after lunch
[11:22] <tseliot> thanks
[12:00] <crevette> bryce, around ?
[12:03] <tjaalton> rather late for him
[12:15] <crevette> tx tjaalton, I didn't if he was US or UK based
[12:21] <tjaalton> UTC-8 :)
[15:04] <tseliot1> tjaalton: I have updated my http://albertomilone.com/ubuntu/newlrm/pitti/jaunty/destination_jaunty1.txt so as to include a patch for Jaunty's kernel for driver 177
[15:05] <tjaalton> tseliot1: right, I forgot about that.. downloading now
[15:06] <tseliot1> tjaalton: thanks
[15:11] <tjaalton> tseliot1: done
[15:11] <tseliot1> tjaalton: great, thanks a lot :-)
[15:13] <tjaalton> np
[15:13] <tjaalton> now lets see if mesa master builds
[15:22] <tseliot1> tjaalton: ah, I almost forgot, can you copy 177, 173, 96 to intrepid-proposed? I guess I'll have to modify the changelog for 180 to put it in intrepid-proposed too, right?
[15:24] <tjaalton> well it's the same for all of them
[15:25] <tjaalton> I can't copy packages from a pocket to another
[15:25] <tseliot1> tjaalton: ok, I'll change them all
[15:32] <tseliot1> tjaalton: shall I do a "debuild -S -sa" for 180?
[15:32] <tseliot1> or would a -S be enough?
[15:33] <tjaalton> I don't know..
[15:34] <tseliot1> tjaalton: the orig.tar.gz is already in the archive since you used it for Jaunty
[15:35] <tjaalton> ok then
[15:35] <tseliot1> tjaalton: -S then?
[15:35] <tjaalton> I guess
[15:36] <tseliot1> ok, let's try with -S
[15:40] <tseliot1> tjaalton: here you go: http://albertomilone.com/ubuntu/newlrm/pitti/destination.txt
[15:41] <tseliot1> tjaalton: as discussed with superm1 I think 180 can get into -proposed without using the backports since it won't be installed by default without the modaliases package
[15:46] <tjaalton> tseliot1: I'm not the release-manager.. they can drop it if it's not suitable there
[15:51] <tseliot1> tjaalton: right
[15:52] <tseliot1> let me know when you're done
[15:52] <tjaalton> um, you used the same version numbers?
[15:53] <tjaalton> I believe this should be dealt with a RM..
[15:54] <tseliot1> tjaalton: aah, does dput refuse to upload the source?
[15:55] <tjaalton> tseliot1: no, but -updates should not have same versions as the devel version, I think
[15:55] <tjaalton> besides, you should have a permission to upload stuff to -proposed first
[15:56] <tseliot1> tjaalton: actually I think this happens from time to time. pitti copied the packages from -proposed to jaunty with the same version
[15:56] <tseliot1> (in the past)
[15:56] <tjaalton> that's different
[15:56] <tseliot1> tjaalton: hmm
[15:56] <tjaalton> I'm sure he bumped the version too
[15:56] <tjaalton> it doesn't work the other way around
[15:57] <tjaalton> and he's an archive admin too
[15:59] <tseliot1> ok, I think I can ask slangasek about this
[16:00] <seb128> intrepid updates are copied to jaunty when the intrepid and jaunty version are identic
[16:00] <seb128> you can't upload the same version twice to intrepid and jaunty though
[16:00] <tseliot1> seb128: and would it be possible to copy from jaunty to intrepid?
[16:01] <seb128> either you have to use different versions or get the source copied on soyuz
[16:01] <seb128> no
[16:01] <seb128> because binaries are built on jaunty this way
[16:01] <seb128> and depends could change a lot
[16:01] <seb128> the copy is a source and binary one
[16:01] <seb128> copying the intrepid binaries to jaunty is no issue
[16:02] <seb128> but it wouldn't work the other way around due to shlibs changes, etc
[16:02] <tseliot1> ah, ok this makes sense
[16:04] <tseliot1> tjaalton: I guess I'll just bump the version then
[17:50] <solarion> anyone know why the MS optical mouse I got would middle-click when I right click and right click when I middle click?
[17:50] <solarion> seems rather bizarre and very highly annoying
[22:08] <solarion> nobody?
[22:08] <jcristau> solarion: try evtest on it, see what it reports
[22:09] <solarion> I don't see an evtest
[22:13] <solarion> yeah, pushing the button and listing state gives button[2,3]=down
[23:15] <solarion> nm, I just got a less crappy mouse.  :)
[23:15] <solarion> side scrolling even just worked right ootb


[08:27] <Riddell> happy monday
[08:32] <Riddell> Quintasan_: you asked for your new flight dates?
[09:49] <Riddell> JontheEchidna: I can't believe amy died with Rory, I always said she'd do so much better with her life if she dumped him and went out with me
[09:54] <Riddell> Blizzz: I presume there's no patch to owncloud 3.0 for the various security issues?
[09:59] <Blizzz> Riddell: ownCloud 3 isn't supported any more
[10:01] <ovidiu-florin_> Hello,
[10:01] <ovidiu-florin_> I have a project and I need to develop in C++ an application to monitor CPU and memory usage of itself.
[10:01] <ovidiu-florin_> I would like to look over the source code of the Ksysguard application, but I can't seem to find it. Maybe I just don't know where to look.
[10:01] <ovidiu-florin_> On this page the code presented I think it's for the website: http://userbase.kde.org/index.php?title=KSysGuard&action=edit
[10:01] <ovidiu-florin_> Can anybody help me?
[10:12] <Riddell> ovidiu-florin_: apt-get source ksysguard
[10:14] <ovidiu-florin_> I'm guessing this was downloaded in ~/ ?
[10:14] <Riddell> ovidiu-florin_: into current directory
[10:15] <ovidiu-florin_> thank you
[10:19] <Riddell> good luck
[10:40] <vprints> Any progress with Precise https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1055967 ?
[10:40] <vprints> :)
[10:41] <xnox> vprints: it's commited to the branch but there was no upload yet.
[10:41] <xnox> vprints: plus even if we do a precise upload you would either have to manually update ubiquity or use precise-daily image as 12.04.2 is not due soon yet.
[10:44] <vprints> xnox: that is not a problem
[10:45] <vprints> i am from downstream, we generate our own isos :)
[10:45] <xnox> vprints: so... cherry pick the patch then.
[10:45] <vprints> but it would be good if the package would come from the official repo
[10:45] <xnox> vprints: as in you'd have no work to do ?! I see....
[10:46] <vprints> :D
[10:46] <xnox> that didn't convince me to do an upload now. I still have another bug to solve for precise.
[10:47] <vprints> I think i was just asking
[10:47] <vprints> and plitely
[10:47] <vprints> politely*
[10:47] <vprints> not demanding
[10:47] <xnox> well, I gave you the status update =) not happening soon as far as I can see. But there will be one for 12.04.2
[10:48] <vprints> Ok
[10:52] <Quintasan_> Riddell: Yes, I did. Awaiting response. Im also looking for a way to get to Berlin
[11:20] <Riddell> oh I remember the kubuntu automation script's issue, it stops when it has a problem building package like a patch that no longer applies and you have to start all over again
[11:20]  * Riddell doing 4.9.2
[11:21] <debfx> there is still the issue of all our branches not being in sync with the archive
[11:21] <debfx> so the script won't do anything
[11:25]  * tsdgeos shakes fist at clementine package
[11:26] <tsdgeos> apt-get source + apt-get builddep + dpkg-buildpackage → fail
[11:26] <tsdgeos> Riddell: be aware there might be a kde-workspace respin
[11:27] <Riddell> tsdgeos: yeah I read that
[11:27] <tsdgeos> oki
[11:27] <debfx> hm why is qt4-x11 in quantal-proposed?
[11:29] <apol> https://bugs.launchpad.net/ubuntu/+source/kde-gtk-config/+bug/1058464 << anybody knows what changed?
[11:29] <apol> (on the gtk configs in quantal)
[11:31] <Riddell> hum
[11:32] <Riddell> I keep forgetting the details, if only gtk did things consistently
[11:32] <Riddell> but we switched from having it set somewhere in gtk2 and xsettings-kde trying to give the same thing to gtk3
[11:32] <Riddell> to your kcm and setting it somewhere else one for gtk2 and again for gtk 3
[11:39] <apol> Riddell: i haven't seen a patch in the kcm...
[11:41] <Riddell> apol: here's what it has http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/quantal/kde-gtk-config/quantal/files/head:/debian/patches/
[11:41] <apol> ......
[11:41] <apol> dude!
[11:42] <apol> Riddell: why aren't I aware of this?
[11:42] <Riddell> good question, I'm not sure
[11:43] <Riddell> I think partly it comes from debian and partly I blame my poor broken brain, sorry
[11:43] <apol> Riddell: kubuntu needs a no-patch policy against KDE
[11:46] <Riddell> we do, but an exception is that stuff from debian we tend to assume has already been handled properly, assuming you're looking at the mirgation-from-package-src\:kcm-gtk patch
[11:51] <apol> Riddell: ok, I'll get in touch with him
[11:52] <Riddell> apol: it is causing a problem?
[11:53] <apol> Riddell: well, for starters i'm not happy to see there's patches removing features and such > http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/quantal/kde-gtk-config/quantal/view/head:/debian/patches/kubuntu_01_no_gtk.diff
[11:54] <apol> also there are patches that won't work
[11:55] <Riddell> apol: hmm I seem to remember you saying at some point we could compile it without the gtk dependency
[11:56] <apol> yes definitely
[11:56] <apol> but the solution isn't a distro patch
[12:07] <apol> Riddell: do you know what's the default ~/.gtkrc-2.0 file in quantal?
[12:08] <yofel> apol: ~/.gtkrc-2.0
[12:10] <Riddell> /usr/share/kubuntu-default-settings/dot-gtkrc-2.0-kde4  it should be
[12:10] <Riddell> yes
[12:11] <Riddell> http://paste.kde.org/560540/
[12:13] <pkt> vprints: you could use https://github.com/squibbylinux/ubiquity.squibby.git
[12:14] <pkt> I 'm also from downstream and I have done the patching
[12:14] <pkt> it also has fixes for the other issues I reported
[12:14] <pkt> maybe the code is not so great but I hope it is too simple to mess it up :P
[12:14] <pkt> at least it is tested :)
[12:14] <apol> hm
[12:15] <apol> noted
[12:15] <apol> i'll have to review some stuff then...
[12:15] <pkt> apol: In general I think what is there is also upstream in branches
[12:15] <pkt> but feel free :)
[12:16] <apol> no i mean i'll have to look into the kcm again
[12:16] <pkt> oh sorry :)
[12:48] <vprints> pkt: great, thanks!
[12:49] <BluesKaj> Hey all
[12:51] <pkt> vprints: you are welcome
[12:52] <pkt> vprints: btw, which downstream are you from? Is it public?
[12:57] <vprints> estobuntu.org
[12:59] <pkt> cool :)
[13:01] <pkt> vprints: I 'm trying to do the same for Greek language :)
[13:01] <pkt> so hopefully we will be able to exchange ideas :)
[13:03] <vprints> good :)
[13:04] <vprints> you are using PPAs or Your own system for repos?
[14:14] <kubotu> ::qt-bugs:: [1059602] Default buttons for close, minimize and maximize do not show in dialog windows @ https://bugs.launchpad.net/bugs/1059602 (by drMerry)
[15:41] <soee> so tomorrow kde 4.9.2 is released ?
[18:06] <Riddell> http://starsky.19inch.net/~jr/tmp/kubuntu-ppa-build-status.html
[18:18] <Riddell> hi sheytan
[18:19] <sheytan> Riddell: hey
[18:31] <debfx> that looks wrong: http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/audiocd-kio/view/head:/debian/changelog
[18:31]  * yofel_ goes rebuilding 4.9.2
[18:32] <debfx> same in all the other packages
[18:32] <yofel_> o.O
[18:32] <sheytan> Riddell what's up? I'm only for a while ;)
[18:32]  * yofel_ won't rebuild 4.9.2 for now...
[18:32] <Riddell> debfx: it's a sign of how many times I had to run it before it would work :)
[18:32] <kubotu> ::qt-bugs:: [1028283] package libqt4-help 4:4.8.1-0ubuntu4.2 failed to install/upgrade: package libqt4-help is a... @ https://bugs.launchpad.net/bugs/1028283 (by Isaac)
[18:32] <Riddell> I'll tidy it up
[18:33] <shadeslayer> haha
[18:33] <Riddell> sheytan: nothing in paticular, we got an image for the 12.10 release, you can see it on kubuntu.org and critique if you like
[18:33] <yofel_> Riddell: reupload things while you're at it. It seems like stuff was built with kdelibs 4.9.1, so the libs are names *.so.4.9.1 not 4.9.2
[18:33] <yofel_> *named
[18:33] <shadeslayer> Quintasan: ping
[18:34] <Riddell> yofel: mm yes that's more important, I failed to do the build-dep version updates which is my failure
[18:34] <yofel> well, the scripts should do that
[18:34]  * yofel -> dinner, bbiab
[18:35] <Riddell> kubuntu-initial-upload?  I don't think it does
[18:36] <shadeslayer> grep-dctrl and set are your friends :P
[18:36] <shadeslayer> s/set/sed
[18:36] <debfx> maybe we should reset the bzr branches with every release, would certainly make the history more readable than it is now
[18:36] <debfx> it does update the build-deps
[18:37] <Riddell> debfx: oh?  it doesn't seem to have done so
[18:37] <debfx> maybe you are using an old version?
[18:38] <debfx> (it would be a very good idea to update the tools before doing such packaging changes next time)
[18:39] <sheytan> Riddell i follow all the stuff in silent mode,  all good for now. Finally good software in default, still missing the KDE Web accounts, which is going to be cool, hope you fix lightDM theme the way i mocked it up, and hope for packageing kio-mtp just released :) That's it so far :D
[19:04] <Riddell> sheytan: afiestas says webaccounts isn't ready yet
[19:04] <Riddell> apachelogger has lightdm theme on his todo
[19:04] <sheytan> Riddell: thought that, but anyway, it will come with one of the KDE upgrades ;)
[19:35] <Peace-> hi there
[19:36] <Peace-> i have bad feedback to report upgrading to 4.9.1 from 12,04
[19:36] <Peace-> plasma crashs a lots
[19:36] <Peace-> anyone knows this stuff ?
[19:36] <Peace-> or some else has the same issue?
[20:45] <shadeslayer> Peace-: works fine for me
[20:48] <BluesKaj> Peace-, I had to reinstall the nvidia-current driver after 4.9.1
[20:57] <Peace-> i dunno alexzion was reporting an ultra unstable system
[20:57] <Peace-> with 30 crash of plasma
[20:57] <Peace-> hahah pooor guy
[22:05] <shadeslayer> Quintasan: http://forum.xda-developers.com/showthread.php?t=1852702 < have you seen that?
[22:49] <SteveRiley_> hiyall. https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1059297
[22:50] <SteveRiley_> already fixed in KDE SVN, according to https://bugs.kde.org/show_bug.cgi?id=307643
[22:59] <shadeslayer> SteveRiley_: too late in the cycle :(
[23:00] <SteveRiley_> yes, i figured that. just prodding, hoping for 13.04 :)
[23:00] <SteveRiley_> i wasn't sure if you guys saw the bug or not
[23:00] <shadeslayer> probably missed it
[23:01] <SteveRiley_> speaking of which... in cases like that, where there exists a ubuntu package but it's pretty much for us kubuntu guys, where's the better place to file?
[23:01] <SteveRiley_> against the package, or against kubuntu?
[23:01] <shadeslayer> what you need to do is to tag bugs with kubuntu and needs-packaging
[23:01] <SteveRiley_> ah, okie.
[23:01] <SteveRiley_> so much to learn
[23:01] <shadeslayer> against ubuntu, but if it concerns kubuntu, tag with kubuntu :)
[23:01] <shadeslayer> well ... against the package
[23:01] <SteveRiley_> got it
[23:02] <SteveRiley_> thanks for the tip
[23:02] <shadeslayer> np
[23:02] <shadeslayer> good god this source is completely busted
[23:02] <SteveRiley_> what source?
[23:02] <shadeslayer> has a top level src dir, but no CMakeLists.txt
[23:03] <shadeslayer> http://kde-apps.org/content/show.php?content=98808
[23:03] <SteveRiley_> oh, i thought maybe you were looking at partitionmanager
[23:03] <shadeslayer> nah :)
[23:13] <shadeslayer> !find qfile.h:
[23:13] <shadeslayer> !find qfile.h


[03:48] <gemclip> Does anyone have a recommended CBT, Book, or website for setting up Ubuntu Server specifically in reguard to creating an inhouse Apache web server
[03:50] <tomreyn> here's your book: install ubuntu server, boot it and login, then run this command: sudo apt update && sudo apt install apache2
[04:07] <andol> gemclip: See also https://ubuntu.com/server/docs/web-servers-apache
[04:09] <gemclip> Thank you
[04:10] <andol> Looks like it still primarily covers Ubuntu 20.04, but a lot of it will still be applicable to Ubuntu 22.04.
[06:10] <yurtesen> good morning
[08:03] <mirespace> good morning
[10:45] <athos> good morning :)
[11:05] <mirespace> :)
[12:29] <ahasenack> morning
[15:16] <lucasmoura> @rbasak, version 27.8 was released into Jammy. I think we can start the process for the older Ubuntu versions as well. Let us know if you can provide the review for those releases as well
[16:14] <rbasak> lucasmoura: OK, added to my todo.
[16:14] <lucasmoura> thanks rbasak
[20:21] <Beret> å/b 9


[13:19] <soren> What's the magic I need to do to get my git branch to show up on gitweb?
[13:42] <amitk> soren: Put it under /srv/kernel.ubuntu.com/git/soren on zinc and twiddle your fingers till the next run the script that publishes it
[13:43] <soren> Oh!
[13:43] <soren> I forgot to twiddle my thumbs.
[13:43] <amitk> should happen withing the hour, IIRC
[13:43] <soren> That's why you're the one who's on the kernel team, and not me.
[13:43] <soren> Oh, it's there now. \o/
[13:44] <amitk> i know.. we're good at twiddling ;)
[13:44] <soren> amitk: By the way: Do you happen to know if it's cool for me to use zinc for hosting non-kernel git trees?
[13:47] <amitk> soren: I don't think we are going to bitch about non-kernel git trees in the short term, but if you (and others) are going to require it over the longer term it might makes sense to talk to IS. Afterall, zinc == kernel.ubuntu.com
[13:48] <soren> Cool, that's what I thought. Thanks.
[13:49] <rtg> soren: zinc is so underutilized right now that I doubt anyone would even notice.
[13:49] <soren> rtg: Heh :)
[13:49] <amitk> soren: these kernel git trees you published, are they for the virtual flavours?
[13:49] <soren> amitk: No.
[13:50] <soren> amitk: I want to get the packaging sorted out first. that's on my list for the sprint next week.
[13:51] <amitk> soren: are you going to have a different source pacakge or are you planning to build-dep on linux?
[13:51] <soren> b-d on linux-source.
[13:51] <amitk> rtg: any idea what is wrong here:
[13:51] <amitk> II: Checking ABI for lpia...
[13:51] <amitk> WW: Explicitly asked to ignore ABI, running in no-fail mode
[13:51] <amitk> EE: Previous or current ABI file missing!
[13:52] <amitk> soren: so you will maintain everything as patches?
[13:52] <soren> amitk: I think so.
[13:52] <rtg> amitk: I think I broke current git build last night , I'm working on it
[13:52] <soren> amitk: There are a few options... Neither appeal to me very much.
[13:53] <amitk> rtg: No.. this in in my lpia tree that is based off the main tree
[13:53] <smb_tp> amitk, might be at least the modules list and maybe the abi files for the last release are not there. Fatal even if abi changes are ignored
[13:53] <amitk> soren: same here. I am building an lpia tree and I don't want to maintain it as patches.
[13:53] <soren> amitk: I can either maintain a completely separate tree, and rebase off of your now and then... That's probably the easiest, but will force me to move around *huge* source packages.
[13:54] <soren> or
[13:54] <amitk> smb_tp: but I explicitly asked for abi to be ignored by adding debian/abi/ignore
[13:54] <rtg> amitk: you have to add it in each arch
[13:54] <soren> I can try to maintain patches and separate configs.... That gives me small source packages, but if you rebase, and my stuff fails to apply, I have to work that out rather manually, AFAICT.
[13:54] <amitk> soren: I am leaning towards the same solution
[13:54] <rtg> debian/abi/lpia/ignore
[13:54] <smb_tp> amitk, It seemed to me changes are ignored but the files must be there
[13:56] <smb_tp> amitk, I tend to just create the files by copying some older directory to the name it wants for the old abi
[13:56] <soren> amitk: The idea solution would be to have a separate git tree, and make it able to generate the needed patches on the fly, but... I don't know.. It's just a hassle.
[13:56] <soren> I'd hate to have to maintain a completely new kernel build system for this.
[13:57] <rtg> soren: in essence, that is what amitk is doing for lpia
[13:57] <amitk> soren: I should have lpia done this week. I'll try to whip up scripts to automate the rebasing. We should collaborate...
[13:58] <soren> amitk: Totally. I didn't know you were in the same boat.
[13:58] <amitk> smb_tp: I have ignore and module.ignore files in every orifice of debian/abi/<version>/lpia :-/
[13:58] <soren> amitk: How are you dealing with ABI checks?
[13:58] <soren> Just ignoring them?
[13:59] <amitk> soren: currently planning to have a different abi for lpia. Need to discuss with rest of the kernel-team though...
[13:59] <soren> That's my intent as well.
[14:00] <soren> If I have to maintain my own kernel, I want to actually have the freedom to mess it up any way I please (including changing core ABI stuff).
[14:01] <smb_tp> amitk, I also thought this should be enough but recently I was force to just put the files with the modversions there as well until the abi checker was happy. :(
[14:01] <rtg> soren: which is why lpia went to its own tree, freedom to release on their schedule with changes of their choosing.
[14:01] <amitk> rtg: smb_tp: I have reset the abi to -1 in debian/changelog, renamed the source package to linux-lpia, regenerated contro.stub. So it is as good as the first upload. But ABI is failing...
[14:01] <amitk> smb_tp: then something is broken....
[14:01] <soren> rtg: I see.
[14:02] <amitk> soren: exactly. the lpia kernel will be rebased occassionally (2-3 times during the release cycle). So we won't see too many abi bumps.
[14:03] <smb_tp> amitk, the message itself is also a bit unclear. it would be more helpful if it would state whether ther old or new files are thought to be missing.
[14:03] <soren> amitk: Cool.
[14:03] <rtg> amitk: debian/scripts/abi-check is pretty straightforward. instrument it to see why its bitching.
[14:03] <soren> amitk: Well, if you've almost got it worked out, I won't spend any time on it until next week.
[14:03] <soren> amitk: Oh.... You're in... London?
[14:03] <soren> Yes, there was the visa thing. I remember.
[14:03] <soren> I
[14:04] <amitk> soren: I hope to push out the git tree before the week is out
[14:04] <soren> 'm in Lexington, but at least there's some overlap in working hours anyway.
[14:04] <soren> amitk: Cool!
[14:05] <rtg> soren: know anything about file systems? Is there any file system faster at removing lots of small files then ext3?
[14:06] <soren> rtg: I though ext3 was supposed to be really fast at that?
[14:07] <amitk> rtg: IIRC, xfs and jfs are better at smaller files.
[14:07] <smb_tp> soren, no ext3 is slow ext4 should get better
[14:07] <smb_tp> xfs is what I heard too
[14:07] <rtg> soren: deleting a fully built kernel directory takes minutes.
[14:07] <smb_tp> rtg, did you mount that with noatime?
[14:08] <soren> xfs is slow at deletes.
[14:08] <smb_tp> rtg, got the feeling it is faster now...
[14:08] <rtg> smb_tp: relatime,errors=remount-ro
[14:08] <rtg> smb_tp: standard mount magic
[14:09] <amitk> rtg: 'rm -rf linux-dir &' :-p
[14:09] <rtg> amitk: yeah - but my scripts want to reuse the directory. maybe I should rename, then 'rm -rf'
[14:10] <smb_tp> rtg, I recently made myself a seperate fs for compiling (ok, its striped as well) and use notatime for that
[14:10] <amitk> rtg: mv linux-dir linux-foo; rm -rf linux-foo &
[14:10] <rtg> smb_tp: what does noatime do?
[14:10] <smb_tp> rtg, does not put an access time to a file. which is otherwise updated everytime you access a file
[14:11] <alex_joni> rtg: http://tldp.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/chap6sec73.html
[14:11] <smb_tp> rtg, modification time is updated though
[14:11] <soren> rtg: reiserfs is quite fast at deletes, too, but that sort of has maintainability issues now..
[14:12] <rtg> soren: I have a reiserfs partition that I use daily for several years, in fact I created it using SuSE 6.x
[14:13] <soren> rtg: So that's reiser... 3?
[14:14] <soren> rtg: Oh, tmpfs is also rather fast at deletes.
[14:14] <soren> !
[14:14] <rtg> soren: whatever is current in Hardy must be backward compatible.
[14:14] <soren> Certainly, but if the metadata format is ancient, the benchmarks, I'm looking at might be completely wrong.
[14:14] <soren> (remove commas as needed)
[14:15] <smb_tp> rtg, when we are at the real "good" advices why not ry ext2. who needs a journal for compiling... ;-)
[14:15] <rtg> soren: well, the real performance issue is on this screaming fast server I got from Intel. It must havea _really_ slow disk.
[14:16] <soren> smb_tp: Good point. ext2 is much faster than ext3 in this respect.
[14:17] <cking> rtg: I use ext3 with noatime,nodiratime,reservation,relatime
[14:17] <rtg> cking: on /home ? or a separate partition?
[14:18] <cking> rtg: on nearly everthing except boot
[14:18] <amitk> ohhh all your geeks :)
[14:18] <rtg> cking: the default install doesn't create  a /boot partition
[14:18] <cking> amitk: seriously, it makes 2.347 nanoseconds difference :-)
[14:19] <cking> rtg: yeah - I do my own custom kind of thing
[14:19] <amitk> cking: now that _would_ be noticeable :)
[14:20] <alex_joni> hardy does realatime by default afaik
[14:20] <rtg> cking: how do I figure out what kind of hard drive is in this server, and how fast it is (relative to other hard drives) ?
[14:20] <alex_joni> rtg: hdparm -tT /dev/foo is your friend
[14:20] <cking> rtg: and dd is a quick way of benchmarking file I/O
[14:21] <alex_joni> works on software RAID too: root@main:~# hdparm -tT /dev/md0
[14:21] <alex_joni>  Timing cached reads:   8770 MB in  2.00 seconds = 4390.51 MB/sec :-)
[14:21] <cking> rtg: ..don't twiddle hdparm -X unless you are prepared to screw up your data.
[14:21] <rtg> /dev/sda1:
[14:21] <rtg>  Timing cached reads:   13124 MB in  1.99 seconds = 6578.94 MB/sec
[14:21] <rtg>  Timing buffered disk reads:  314 MB in  3.00 seconds = 104.56 MB/sec
[14:22] <rtg> alex_joni: that doesn't look nearly as good as yours.
[14:22] <cking> rtg: That's twice than what I get
[14:23] <rtg> cking: actually, its twice what I get on my dev box as well.
[14:23] <rtg> cking: alex_joni must be doing it against a tmpfs :)
[14:25] <cking> rtg: This is where having 64Gb of 800Mhz DDR2 and the whole of the git source cached in there is a good thing
[14:26] <rtg> cking: this box has 18GB. you would think that's almost enough.
[14:26] <amitk> rtg: thats twice what I get
[14:26] <smb_tp> rtg, maybe you should really use tmpfs for compiles...
[14:27] <rtg> amitk: it literally takes 4-5 minutes to delete these directories. I think I'll reformat for ext2 with noatime.
[14:28] <cking> rtg: ..I have some runes that I use:
[14:28] <smb_tp> rtg, maybe first try noatime only. thats just a reboot/remount
[14:30] <cking> I use tune2fs -O dir_index /dev/sdaX, e2fsck -D -f /dev/sdaX and mount /dev/sdaX with noatime,nodiratim,reservation
[14:32] <cking> make that nodiratime
[14:38] <soren> I haven't been paying much attention to the kernel during intrepid yet... How often do you roll new releases? Weekly-ish?
[14:40] <rtg> cking: what are the relative merits of tmpfs? google has some entries where folks are mounting /tmp to tmpfs.
[14:40] <Tophat> has the new DNS security vulnerability been patched ?
[14:40] <smb_tp> It's a ram-disk...
[14:41] <rtg> smb_tp: I know that, but will it grow as large as it needs to?
[14:41] <cking> rtg: It's fast - and if you have lots of memory it's useful. I suggest doing a build in a tmpfs mounted directory and it should fly..
[14:41] <smb_tp> rtg, yes it should grow
[14:42] <amitk> rtg: you still have the lag of copying the whole kernel tree to tmpfs
[14:42] <cking> amitk: yeah.. how long will that take? 80 seconds?
[14:43] <smb_tp> rtg, http://en.wikipedia.org/wiki/TMPFS
[14:43] <rtg> cking: drat, it appears that its burned in. now I'm gonna have to haul that noisy thing in here where I can get at it. it least its not in my attic.
[14:44] <amitk> cking: I've never felt a kernel compile to be very IO-bound, except for the final linking.
[14:46] <smb_tp> amitk, there seem to be times in between when cpu usage goes down...
[14:46] <cking> amitk: vmstat 1 seems to show a lot of I/O activity - I suppose with -j 4 or more, then it will be more CPU bound and any waits on I/O will be filled by CPU activity in the build
[14:47] <soren> Tophat: http://www.ubuntu.com/usn/usn-622-1
[14:47] <cking> amitk: at the end of the day it's either memory, CPU or disk I/O bottlenecking somewhere.. :-)
[14:49] <amitk> cking: true..
[14:50] <Tophat> soren - have you seen any POC on this attack?
[14:51] <soren> no
[14:51] <soren> Besides, this is off-topic here.
[14:51] <soren> Try in #ubuntu
[15:39] <Ng> is alsa 1.0.17 likely to be in intrepid?
[15:39] <Ng> the kernel drivery bits, I mean
[15:41] <rtg> Ng: if not in the kernel, then we'll likely backport it in LBM
[15:43] <Ng> where "in the kernel" means in LUM? or is it moving to linux-image?
[15:43] <Ng> not that that really matters, so long as it's available, my fellow x300 users will be spared having to worry about getting sound support. thanks :)
[15:44] <amitk> Ng: LUM is no more, everything is in the main git tree now
[15:44] <rtg> Ng: ALSA is part of the core kernel. Actually, when we backport 1.0.17 (if its a superset of core kernel) it will end up in the Intrepid equivalent of LUM.
[15:45] <Ng> aha
[15:46] <Ng> atm my x300 specific LUM with an rc of 1.0.17 is a horrific mess that happens to just about work ;)
[20:29] <pgraner> rtg: who is the v4l driver SME?
[20:30] <rtg> pgraner: dunno. whats an SME?
[20:30] <rtg> souce maintainer extraordinaore?
[20:30] <pgraner> rtg: Subject Matter Expert
[20:31] <rtg> pgraner: ah, a new TLA
[20:31] <pgraner> rtg: specifically the em28xx driver
[20:31] <rtg> pgraner: maybe talk to jono and find out who did the filming at UDS?
[20:32] <rtg> em28xx being what your handy cam supports?
[20:32] <pgraner> rtg: no its a tv tuner....
[20:33] <smb_tp> maybe mkrufky might be of help
[20:33] <pgraner> rtg: I'm using a Mac for the video at the sprint just for speed.
[20:33] <rtg> smb_tp: yeah - mkrufky is trhe hauppage dude.
[20:33] <mkrufky> i am back
[20:34]  * mkrufky catching up on backlog
[20:34] <mkrufky> ok, yeah i am the guy
[20:34] <mkrufky> what is the question?
[20:34] <pgraner> smb_tp: cool.... I have a Bus 005 Device 038: ID 2040:6513 Hauppauge and I can't get hardy to recognize it
[20:34] <mkrufky> btw, i am moreso "the guy" because of my linuxtv affiliation rather than my hauppauge affiliation
[20:34] <mkrufky> hary does not support 2040:6513 out of the box
[20:35] <mkrufky> but it will be supported in intrepid
[20:35] <mkrufky> ... but you will need to grab the xc3028-v27.fw image
[20:35] <mkrufky> if you want to run it in hardy, you may use the mercurial repository hosted at http://linuxtv.org
[20:35] <pgraner> mkrufky: cool. Is the support in the alpha1/2?
[20:35] <mkrufky> i do not plan on backporting this one to hardy LUM
[20:35] <rtg> pgraner: I thought you were expressing intrepid upgrade woes the other day.
[20:36] <mkrufky> pgraner: it's in the 2.6.26 kernel...  i have not been tracking interpid, but intrepid has 2.6.26, so thats what u need
[20:36] <pgraner> pgraner: I got the sound fixed, which was the big issue other than no changelog
[20:36] <mkrufky> TLA ?
[20:37] <smb_tp> three letter acronym
[20:37] <mkrufky> :-) ok cool
[20:37] <pgraner> rtg: I had to blacklist the snd_pcsp module and the cracking went bye bye
[20:38] <rtg> pgraner: my somewhat oblique point being, support for your device is already in Intrepid
[20:41] <mkrufky> ironically, however, the next gen version of the 950 is in hardy LUM
[21:19] <pgraner> mkrufky: what does a *** unknown tvp3e04 chip detected *** Rom ver is 12.0 mean?
[21:20] <mkrufky> that depends on the context
[21:20] <mkrufky> where did you see said message?
[21:20] <mkrufky> i'll assume you saw it in dmesg log
[21:20] <mkrufky> if so, can you paste it with some context on a pastebin somewhere ?
[21:21] <pgraner> mkrufky: /var/log/messages after loading the module em28xx tells me that if found a Hauppague WinTV HVR 950
[21:21] <mkrufky> context ... pastebin ...
[21:22] <mkrufky> please show me dmesg | tail -n100
[21:22] <pgraner> mkrufky: one sec different box
[21:22] <mkrufky> k
[21:23] <mkrufky> pgraner: if you do " lsmod | grep tvp " and you do NOT see tvp5150, then thats your problem
[21:24] <pgraner> mkrufky: its there
[21:24] <mkrufky> how many users ,... 1 or 0 ?
[21:27] <pgraner> mkrufky: http://pastebin.com/m7750bdbf
[21:32] <mkrufky> pgraner: tvp5150 0-005c: tvp5150am1 detected.
[21:32] <mkrufky> pgraner: please try a different usb port
[21:33] <pgraner> mkrufky: just did
[21:34] <pgraner> mkrufky: dmesg is still telling me the tvp3e04 is unknown with i2c i/o errors
[21:35] <mkrufky> did you try it?  does it work?
[21:37] <pgraner> mkrufky: its channel scanning now
[21:38] <mkrufky> the error message is coming from the analog video decoder driver
[21:38] <mkrufky> it looks like its complaining, then attaching correctly
[21:38] <mkrufky> i have not seen this before
[21:38] <pgraner> mkrufky: ok working now, I'm seeing channels during the scan
[21:38] <mkrufky> it might work anyway
[21:38] <mkrufky> but seems strange
[21:39] <mkrufky> yeah, the tvp thing would not affect digital tv
[21:39] <mkrufky> only analog
[21:41] <pgraner> mkrufky: no audio as of yet
[21:45] <mkrufky> what do you mean , no audio?
[21:45] <mkrufky> if you're watching digital TV, then the audio is part of the mpeg2 stream
[21:46] <pgraner> mkrufky: no audio, I can play mp3s, hear the lovely login music, but nothing from the tv tuner. I'm messing with alsa settings now
[21:48] <mkrufky> are you watching digital tv or no?
[21:48] <mkrufky> if you're watching analog tv and have no audio, then i can tell you what to do
[21:48] <pgraner> mkrufky: I'm watching tv, don't know how to tell if its digital or not.
[21:48] <mkrufky> HOW are you watching tv?
[21:49] <mkrufky> what app?  what channel?
[21:49] <pgraner> mkrufky: tvtime channel 5 (CSPAN)
[21:49] <mkrufky> ok
[21:49] <mkrufky> you're watching analog tv
[21:49] <mkrufky> in order to get audio, google "arecord aplay tvtime"
[21:49] <mkrufky> or google, "sox tvtime"
[21:50] <mkrufky> there is no TV application that does this right, unfortunately, except for mythtv
[21:50] <mkrufky> note: ANALOG
[21:50] <mkrufky> digital tv "JustWorks(tm)"
[21:50] <pgraner> mkrufky: ok the aplay trick worked
[21:50] <pgraner> mkrufky: how do I get the digital then?
[21:51] <mkrufky> we are sooooo off topic
[21:51] <pgraner> mkrufky: yea, I'll google
[21:51] <mkrufky> just real quick:
[21:51] <mkrufky> first, scan for channels using scan from dvb-apps
[21:51] <mkrufky> (dvb-utils from apt)
[21:51] <mkrufky> then azap CHANN_EL -r    (-r is important)  ...  leave that running
[21:52] <mkrufky> open a new shell, run: mplayer /dev/dvb/adapter0/dvr0
[21:52] <mkrufky> thats is for a basic test
[21:52] <mkrufky> google will give you more detailed info
[21:52] <mkrufky> oh, you need to drop that channels.conf file (from your scan) into ~/.azap
[21:53] <pgraner> mkrufky: got it thanks
[21:54] <mkrufky> you're welcome
[21:54] <mkrufky> for future reference, #linuxtv is a better venue for these questions
[21:54] <mkrufky> im usually in there, but i am not right now


[01:00] <pfifo> Hello everyone
[01:01] <pfifo> what is a good way to be notified when its released?
[01:02] <pfifo> Id like to begin my upgrade on release day
[01:02] <pfifo> ( I have not formatted or reinstalled since release day 14.04 :D )
[01:03] <bitshifter> Hi, I have a question about the new install option to "disable secure boot" to allow the installation of 3rd party drivers.
[01:03] <bitshifter>  Is this only available at install time?
[01:03] <bitshifter>  Once installed if you haven't checked this option there's no way to install 3rd party stuff ever again?
[01:33] <jonathan_zz> pfifo: release date is already known but I guess you could subscribe to some ubuntu-announce list.
[01:34] <pfifo> ohh, I didnt see it anywhere
[01:37] <jonathan_zz> april 21st
[02:19] <AlecTaylor> Hold up, does `ls -alR` no longer show the contents of a symbolic linked directory?
[02:27] <flocculant> pfifo: if you did decide to upgrade on the day - it's likely to take some time to grab packages, after waiting for things to propogate, then the upgrade starts and it is 2 am and you miss the call to answer - then wake up and assume all went well and it just hung - and rebooted and you shouldn't have
[02:28] <flocculant> much much better to not panic and wait a day or two - or if you *can* do so early and actually test that the upgrade is working as expected :)
[02:28] <flocculant> then you just need to apt update/upgrade
[02:29] <pfifo> flocculant: i use debootstrap, and really take ubuntu in my own direction.
[02:29] <pfifo> :)
[02:30] <flocculant> cool
[02:30] <flocculant> not sure why you'd ask then  ;)
[02:35] <pfifo> ahh, back in '14 I was asking and waiting and asking, then all of a sudden it caught me by suprise
[02:36] <pfifo> just happend to look on release day after giving it a break for a week or so
[02:45] <flocculant> oic
[02:46] <flocculant> so - yea sometime on release *day* it will release
[02:47] <flocculant> ofc the day can be longer than a random normal person's day :)
[03:39] <snadge> version of heimdall that comes wtih 16.04 sucks :p
[03:40] <snadge> had to build it from source.. the repo for it complains because apt sign changes
[04:55] <Madhumper69> is   4.4.6-040406-generic latest kernel? where can i go to see what is latests kernel? i cant seem to find any hits on google?
[04:55] <Madhumper69> for 16.04LTS
[05:00] <lotuspsychje> !info linux-image-generic
[05:00] <lotuspsychje> Madhumper69: ^
[05:04] <Madhumper69> then why do i ahve 4.4.6?
[05:04] <Madhumper69> thank you btw
[05:06] <lotuspsychje> Madhumper69: upgraded or clean install?
[05:07] <Madhumper69> i did upgrade i know i installed 4.4.6 but it said it was latests ubuntu kernel for 16.04lts i guess its not really accurate? im new to ubuntu so im not an expert but am getting alot better with time.
[05:08] <lotuspsychje> Madhumper69: i mean did you upgrade from a previous ubuntu version?
[05:09] <Madhumper69> no fresh install of 16.04 and upgraded manually the kernel few days ago
[05:09] <lotuspsychje> Madhumper69: try a sudo dist-upgrade ?
[05:10] <Madhumper69> yeah, no updates available all good
[05:11] <lotuspsychje> Madhumper69: downloaded the daily or beta2 ?
[05:11] <Madhumper69> i dont recall i installed few days or weeks ago... its fully updated i believe and i installed a kernel manually but all is workign fine
[05:12] <lotuspsychje> Madhumper69: why did you upgrade kernel manually?
[05:12] <lotuspsychje> Madhumper69: paste uname -a plz?
[05:13] <Madhumper69> Linux server-OptiPlex-390 4.4.6-040406-generic #201603161231 SMP Wed Mar 16 16:33:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[05:14] <Madhumper69> Distributor ID: Ubuntu / Description:    Ubuntu Xenial Xerus (development branch) / Release:        16.04 / Codename:       xenial
[05:14] <lotuspsychje> weird, your on ubuntu server?
[05:15] <Madhumper69> no
[05:16] <Madhumper69> is this kernel from 15.10 or 15.04 lol? wouldnt it go crazy with errors on 16.04lts i know this is 16.04 for sure
[05:16] <lotuspsychje> Madhumper69: you sure you didnt upgrade from 15.10?
[05:16] <Madhumper69> im pretty sure
[05:16] <Madhumper69> i installed a kernel manually not through ppa
[05:17] <lotuspsychje> Madhumper69: any reason you installed kernel manually?
[05:17] <Madhumper69> cuase when i did dist-upgrade nothing would happen i had 0 updates upgrades etc..
[05:17] <lotuspsychje> Madhumper69: from where did you grab iso?
[05:18] <Madhumper69> and from a google search i knew i could get updated kernel maybe it was 4.4.0 at its latests and all was good
[05:18] <lotuspsychje> lotuspsychje@R00TBOOK:~$ uname -a
[05:18] <lotuspsychje> Linux R00TBOOK 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:17:28 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[05:18] <lotuspsychje> this is what kernel should look like on daily
[05:19] <Madhumper69> i grabbed iso from http://releases.ubuntu.com/16.04/
[05:19] <lotuspsychje> ah beta2
[05:19] <lotuspsychje> Madhumper69: i would suggest daily
[05:19] <Madhumper69> yes 16.04lts
[05:20] <lotuspsychje> Madhumper69: look at the topic for daily iso's
[05:20] <lotuspsychje> Madhumper69: or wait on your beta2 for final release
[05:20] <lotuspsychje> like you wish
[05:20] <lotuspsychje> !final
[05:21] <Madhumper69> im confused... so basicly u have 16.04lts and i to but you have 4.0 and i am 4.4.6 ? where is daily iso's topic?
[05:22] <lotuspsychje> Madhumper69: type /topic
[05:22] <lotuspsychje> daily builds:..
[05:22] <Madhumper69> ohh ok
[05:22] <Madhumper69> so whats the difference with daily builds and beta 2
[05:23] <lotuspsychje> Madhumper69: daily builds get daily iso latest
[05:23] <Madhumper69> are you trying to tell me to reinstall?
[05:24] <lotuspsychje> Madhumper69: i would try to reinstall a daily yes, depending of what you need of course
[05:24] <lotuspsychje> Madhumper69: we are still in developing phase right
[05:24] <Madhumper69> right, well all i did is install this kernel nothing is broke...
[05:25] <lotuspsychje> Madhumper69: well regular updates/upgrades should get you to latest kernel, no need for manual
[05:25] <Madhumper69> i dont think i want to reinstall everything to much work , my apache plex and ntfs sharing samba confs and networking was a nightmare lol
[05:25] <Madhumper69> ok so with this kernel if i have no issues im ok? is it bad?
[05:25] <lotuspsychje> Madhumper69: ok wait until final then, see what happens
[05:26] <Madhumper69> ok
[05:26] <lotuspsychje> Madhumper69: tried a sudo apt-get update && sudo apt-get upgrade ?
[05:35] <Madhumper69> yeah all is updated no more updates all 0;s
[05:35] <Madhumper69> 0's
[05:35] <Madhumper69> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[05:36] <lotuspsychje> strange
[05:36] <lotuspsychje> Madhumper69: you could try to enter grub, see what other kernels showup your list
[05:37] <Madhumper69> i manually installed a kernel i could always install another and remove the one... but my question is wouldnt a different kernel make my unit go crazy with errors?
[05:37] <Madhumper69> i removed them once i knew this one worked lol
[06:34] <ubuntu022> Trying to apt update xenial is throwing a lot of errors. Any pointers on how to fix this? (Behind a proxy btw)
[06:36] <lotuspsychje> ubuntu022: disable your proxy?
[06:37] <ubuntu022> Can't. Thats the only path to the internet.
[06:38] <lotuspsychje> ubuntu022: well its not ubuntu's fault your behind a proxy right?
[06:39] <ubuntu022> Oh ok then.
[07:23] <jushur> ubuntu022: cant see why a proxy should give you troubles? you are properly setting (glbaly) it before you run the apt commands?
[08:07] <Xard> seems like in xenial the "systemctl enable/disable sshd" doesn' quite work as expected
[08:08] <Xard> it should act as redirection to ssh, I get that but trying to enable or disable the redirection removes permanently the link files and stops working completely wihtout manual fixing of symlinks ;<
[08:39] <uebera||> Hi! There's no mariadb-galera-server package for Xenial (it's said that only starting with v10.1 the server package includes this functionality, but Xenial only has v10.0) and "/usr/sbin/mysqld: unknown variable 'wsrep_provider=/usr/lib/galera/libgalera_smm.so'" tells me something is missing. What to install? Wily packages?
[09:11] <freaj> Xard: perhaps the packages should be upgraded to systemd..
[09:20] <Xard> freaj: that might be it as "systemctl enable/disable ssh" doesn't seem to work as expected either, though it doesn't seem to remove permanently anything
[09:21] <freaj> Xard: I've been on arch for years, and it's sad to see that, even in 2016 now, when you systemctl enable something, it uses sysv in the background
[09:21] <freaj> though I dunno if ssh on ubuntu is providing a .service or not
[09:22] <Xard> i've used years of rhel and fedora systems with systemd so I kind of expected things to work as they do usually with systemd :\
[09:22] <freaj> but on arch everything was using systemd :P
[09:22] <freaj> Yeah me too
[09:22] <Xard> though now fedora is such a mess in desktop I just had to leave :<
[09:22] <freaj> But I can't complain, I'm using ubuntu
[09:22] <freaj> I've never used fedora for desktop (or anything), I only tried in a VM
[09:23] <freaj> I was tired of playing bob the builder with my system (arch) so I wanted a stable distro, but fedora seems to have a tiny package list compared to ubuntu
[09:23] <Xard> fedora has been very awesome as desktop but lately the hostility towards nvidia binary users just got unbearable
[09:23] <freaj> + the LTS release cycle
[09:24] <freaj> Well, it is understandable, fedora has only free/open source software except for the kernel
[09:25] <Xard> rpm fusion has been the source of nvidia support but lately the support and updates have been sparse
[09:25] <Xard> also I maintain centos / rhel servers and thanks to my fedora experience the transition to the systemd wasn't that painful
[09:25] <freaj> but regarding systemd, even debian is shitty on that part
[09:26] <freaj> I maintain debian servers
[09:26] <freaj> And I was used to systemd (like.. a lot)
[09:26] <Xard> debian is largely unknown to me :<
[09:26] <freaj> So I wanted systemd on my servers as well, writing unit files is cool and easy
[09:26] <Xard> but that doesn't mean i'm unwilling to learn
[09:26] <freaj> but when I saw the systemd integration in debian, I wanted to cry
[09:27] <ratrace> freaj: what's wrong with it, other than the fact that logging out of SSH leaves you hangin'
[09:27] <Xard> I got to confess that the state beta of the xenial lts on the desktop has been miles above what i expected
[09:27] <ratrace> (which was fixed upstream like years ago)
[09:27] <freaj> ratrace: with what?
[09:27] <ratrace> systemd on debian
[09:27] <freaj> ratrace: oh, systemctl wasn't responding, the API timeouted many many times
[09:28] <freaj> It was fixed after some time in debian tho
[09:28] <ratrace> ah.
[09:28] <Xard> only snag i had is with installing first time to a GPT partition as I didn't know about the efi partition and the installer wasn't that helpful either as i needed a custom partition layout
[09:28] <freaj> I had to run a lot of services and systemd was hanging
[09:28] <ratrace> speaking of which, I'm missing menus in some apps, like Libre Office Calc, in 16.04. Anyone else has that issue?
[09:29] <freaj> Xard: I'm mostly an old school person heh, I'm struggling with silly issues as well
[09:29] <Xard> this is the first time i'm using something else than MBR
[09:29] <freaj> ratrace: I'm using ubuntu gnome but I'll tell you
[09:29] <freaj> Xard: wow
[09:29] <Xard> but MBR only supports disks to was it 2TB or so
[09:29] <freaj> np for me ratrace :/
[09:30] <Xard> ratrace: do you mean the top bar menus?
[09:30] <freaj> I'm using linux on a macbook, I have to deal with EFI
[09:30] <freaj> But it's surprising because it works out of the box now
[09:30] <ratrace> freaj: I had that few days ago for almost all the app as well but an update came and fixed it... except for Libre Office it seems.
[09:30] <ratrace> Xard: yeah
[09:30] <freaj> (just have to install grub in efi and it magically works)
[09:30] <ratrace> *all the apps
[09:31] <Xard> I'm using osx on my macbook but it hides all the details so i wasn't aware of the gpt boot requirements
[09:31] <Xard> ratrace: I had that for some applications, had to log out to fix it :/
[09:31] <freaj> I don't know how to use osx
[09:32] <Xard> freaj: actually i got to the unix world with osx back in 2003
[09:32] <ratrace> Xard: logout login eh.... thanks I'll try
[09:32] <freaj> ratrace: maybe you will have another update soon? :P
[09:32] <Xard> ratrace: sorry i don't have any more specific help as i haven't encountered it again since
[09:32] <freaj> Xard: heh, I got to the unix world with windows! windows were blocked at boot (vista) and I didn't have enough money to fix that, a friend told me to try mandriva
[09:33] <ratrace> freaj: yeah, hopefully .)
[09:33] <freaj> windows was blocked*
[09:33] <Xard> freaj: but bash in osx works quite the same x)
[09:34] <Xard> freaj: mandriva was my first linux distrubution and oh boy I had some issues with it
[09:34] <freaj> I'd use osx if I wasn't doubting regarding all these proprietary softwares
[09:34] <freaj> I still have my 8.10 ubuntu disk!
[09:35] <Xard> i'm using osx on laptops now as they are solid rock stable systems with vendor hardware support, can't say the same for generic x86 laptops especially when using linux sadly :(
[09:35] <Xard> I still have my ppc macbook from 2003 and it works
[09:35] <freaj> Once you know how to deal with some issues with linux on macbooks, you're good to go
[09:35] <Xard> even the batter hasn't died
[09:35] <freaj> macbooks are really one of the bests machine to work with
[09:36] <Xard> at work I have a new generation mac pro and oh boy is it unstable :<
[09:36] <Xard> couple of crashes every week
[09:36] <freaj> I only have one machine tho
[09:36] <Xard> thanks ati / amd ;<
[09:36] <freaj> from 2012
[09:36] <freaj> with the retina displays, you can't repair your computer anymore, you can't change the ram etc :(
[09:37] <Xard> the newer macbooks have really bad keyboards though :(
[09:37] <freaj> the slim buttons keyboard?
[09:37] <Xard> yeah
[09:37] <freaj> I wonder how you can type fast with that, I'd be annoyed
[09:38] <Xard> the older macbook pro I used back in 2006 had exceptionally good flat keyboard
[09:38] <freaj> My only current issue is that when I close my macbook's lid, the screen stays on
[09:38] <freaj> oh! the fancy white keyboards <3
[09:39] <Xard> on regular pc it's either buckling springs or mx-blue or gtfo when it comes to keyboards x)
[09:39] <Xard> i'm really glad that the mechanical keyboards have made a comeback
[09:39] <freaj> Actually, before the macbook, I had an "awesome" laptop, like, it was easy to repair, the keyboard/screen was nice
[09:40] <freaj> But there is always something bad, bad battery, noisy, etc
[09:40] <freaj> I have to confess
[09:40] <freaj> I don't like mechanical keyboards
[09:41] <freaj> :(
[09:41] <Xard> no problem :D
[09:41] <Xard> they are heavy and need a proper wrist rest or are pretty much unusable
[09:42] <Xard> also these clicky keyboards make some noise and the clicky switches can have some durability issues
[09:43] <Xard> and the broken switches can cause furiously annoying random key repeats
[09:44] <freaj> I really don't understand how people can type fast with emchanical keyboards
[09:44] <freaj> I'm like "ew you have to press deep!"
[09:44] <Xard> buckling spring switches seem to be virtually indestructible though x)
[09:45] <freaj> Xard: why be on a linux desktop btw?
[09:45] <freaj> why not stay with osx?
[09:46] <Xard> I have multiple reasons
[09:46] <freaj> I'm really concerned about privacy :/
[09:46] <Xard> but a technical one is that with nvidia i can have 10 performance with single budget card in blender compared really expensive top of the line I7
[09:47] <Xard> and apple doesn't offer nvidia solutions on desktops anymore
[09:48] <Xard> which means tha with linux desktop i have the freedom of choosing my hardware
[09:48] <Xard> for older mac pro desktops where you can install custom display cards they can cost up to 1500 euros
[09:49] <freaj> oh, right
[09:50] <Xard> http://xard.mbnet.fi/r2014-4k.jpg :3
[09:50] <freaj> so you draw?
[09:51] <Xard> no, that's 3d model
[09:51] <freaj> oh okay
[09:51] <freaj> that's.. creative
[09:52] <Xard> i just mentioned that the cuda acceleration in blender makes things quite much faster in blender x)
[09:56] <Xard> besides programming, server maintenance I do bit this and that as computer hobby and linux desktop has actually suited for my needs quite well
[10:02] <Xard> i guess i have to *knock on wood* so far with the 16.04 lts
[10:08] <Xard> freaj: yeah, you mentioned about privacy and sadly that's a very good reason nowadays :<
[10:14] <ratrace> yay, updates! rebooty time!
[10:15] <Xard> when it comes to backups is there a sure way to tar root and only root without filesystem mounts and such to package which can be extracted to another drive / partition and and can be used after tweaking /etc/fstab and installing grub with chroot again?
[10:16] <Xard> findmnt gives quite good picture of what to not include
[10:17] <freaj> Xard: usually you can ignore /sys and /dev
[10:17] <Xard> when it comes to /sys /dev /proc and /run the directories still need to be there as they serve as mounting points and have to have proper rights (and context?)
[10:18] <Xard> i'm used working with selinux enabled :>
[10:19] <Xard> can i just include the folder/path without any content from it using tar?
[10:25] <freaj> Xard: I guess you can add exclude folders :P
[10:25] <freaj> Anyway I'm out for the day, have a nice day!
[10:25] <Xard> see ya
[10:39] <varaindemian> Can we talk about something similar to Arch's AUR in the next ubuntu release (16.04)?
[10:39] <ratrace> varaindemian: you mean like PPAs?
[10:40] <varaindemian> yeah, will they make things somehow "easier"?
[10:40] <ratrace> your question is too vague. easier for what and whom?
[10:41] <varaindemian> to create and share your own packages
[10:41] <ratrace> well PPAs have existed for very long time, it's nothing novel for 16.04.
[10:44] <varaindemian> why would I pick PPAs over AUR?
[10:44] <Xard> ratrace: by the way did reboot/relog fix the menu issue?
[10:44] <ratrace> Xard: did so.
[10:45] <ratrace> Xard: so I wonder if it's something that appears on first application start, a config gets written somewhere, and then on next login the menus are normally available. If so, perhaps it's a bug to be reported.
[10:45] <Xard> ratrace: did you enable the "always show menus" option?
[10:45] <ratrace> Yeah.
[10:45] <Xard> so did i
[10:46] <Xard> that might be a good bug report target
[10:46] <ratrace> Had that from the first installation.
[10:46] <ratrace> I'll report it. Worst case, it'll be closed as notabug :)
[10:46] <Xard> It makes things almost like in osx so i'm familiar with showing the menus
[10:46] <Xard> sure, thanks for the effort :3
[10:47] <Xard> though it's bit awkward that the application names get faded out and the file menus isn't just concatenated after the application name :/
[10:47] <ratrace> Xard: the only problem is, I don't know which fixed it. re-login or updates. Because I log out only to reboot after updates. I suspend the machine when I'm away.
[10:48] <Xard> I guess fading the application name creates some consistency but it looks bad
[10:49] <Xard> ratrace: from my experience i'd bet on restarting unity which also happens when relogging
[10:49] <ratrace> Xard: probably, since this wave of updates was about the boost lib and new kernel, nothing related directly to unity.
[10:50] <Xard> I don't know how unity can be restarted yet, but I think the common thing in here is that the menus start not appearing after the "always show menus is enabled"
[10:50] <Xard> I don't know about ubuntu yet, but at least on fedora the updates also had links to descriptions what actually was fixed
[10:51] <Xard> i understand that the ubuntu is more consumer oriented and doesn't bother user with such details but still
[10:51] <ratrace> there are descriptions in the updater window/gui, but in this case I used command line apt-get so I didn't pay attention.
[10:52] <ratrace> oh wait, there was something qt related so it's still possible the update fixed it.
[10:56] <ratrace> https://dpaste.de/hUnN
[11:01] <Xard> only thing i could find with a quick glance was: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1561781
[11:01] <Xard> and it's not directly related though is similiar issue
[11:01] <Xard> so i think it's safe to report it
[12:05] <BluesKaj> Hey folks
[12:15] <thunfisch> hey, build my own preseed iso for xenial server. only hangup left is the question if i want to continue with a incomplete installer language - how do i supress that?
[12:23] <thunfisch> ah, needed to pass localechooser/translation/warn-light=true and warn-severe=true in bootloader append.
[14:51] <bjornar> How do I reload apparmor profiles after dropping a /etc/apparmor.d file?
[16:03] <Oderus> hi. having a couple of problems with SDDM in Kubuntu 16.04; firstly, my mouse theme does not show up in SDDM only the default, despite being on and customized, although it used to work. Also, in keyboard settings I had it set to have numblock on automatically but this also never happens which is frustrating.
[16:04] <Oderus> Thirdly, when i boot up and log in, my volume meter is a blank space in the task bar, unless i log out and re log in, then it appears. Any help with these issues is appreciated. thanks!
[16:13] <Oderus1> sorry i had to restart my network, questions still stand
[16:14] <ChibaPet> Oderus1: Can you restate? I can in to get the release schedule link, but I'll be here for a bit.
[16:14] <ChibaPet> Came in*
[16:15] <Oderus1> hi. having a couple of problems with SDDM in Kubuntu 16.04; firstly, my mouse theme does not show up in SDDM only the default, despite being on and customized, although it used to work. Also, in keyboard settings I had it set to have numblock on automatically but this also never happens which is frustrating.
[16:15] <Oderus1> Thirdly, when i boot up and log in, my volume meter is a blank space in the task bar, unless i log out and re log in, then it appears. Any help with these issues is appreciated. thanks!
[16:18] <ChibaPet> Hrm. Unfortunately, this is all software I don't use - I'd strongly recommend asking on one of the mailing lists. There's less luck of the draw involved with who sees the question, and there are some very smart people on the lists.
[16:18] <ChibaPet> And now is the time, with release imminent.
[17:35] <marus> on daily, the network interfaces have new names?
[17:38] <jonathan_zz> marus: the systemd thing you mean right.
[17:38] <jonathan_zz> marus: enp0_s25 or whatever
[17:38] <marus> system is new to 16.04
[17:38] <marus> yes
[17:38] <marus> systemd
[17:38] <jonathan_zz> you can turn it off somewhere
[17:39] <jonathan_zz> but it's a bit troublesome to remember
[17:40] <marus> it will still with this names, or will the normal names (eth0, wlan0) be back after final?
[17:41] <jonathan_zz> this should do it:   ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
[17:41] <jonathan_zz> will stay
[17:41] <jonathan_zz> it is for servers that have multiple nics
[17:42] <jonathan_zz> the kernel is not always reliable in giving it the same names always
[17:42] <jonathan_zz> so on some systems eth0 and eth1 would swap ocassionally
[17:42] <jonathan_zz> but if that is no issue you it you can turn it off this way
[17:43] <marus> jonathan_z: so the symbolic link will only show off old names?
[17:43] <marus> and all new ubuntu version will have the new names
[17:43] <marus> thats awsome
[17:43] <jonathan_zz> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
[17:44] <jonathan_zz> yes
[17:44] <marus> okay thanks jonathan_z ;-)
[17:44] <jonathan_zz> I'm zz, I'm sleeping ;-).
[17:45] <jonathan_zz> I don't like the thing at all and feel it should be off by default.
[17:45] <jonathan_zz> there is a provision though to map it to names you like
[17:46] <jonathan_zz> but at the very least a default mapping to eth0 should exist
[17:47] <Xard> hmm, seems like by default firewall ufw isn't enabled
[17:47] <marus> that's would be better
[17:47] <marus> because my wlan0 new name is like wlx00259c96cafb
[17:47] <marus> for a desktop, that doesn't help to much
[17:49] <ratrace> marus: systemd was introduced in Ubuntu with 15.04, not 16.04
[18:02] <marus> ratrace: thanks, i havn't had time to try 15.04
[18:03] <marus> but good to know that it was already at 15.04
[18:04] <marus> and i thing i should always use systemctl rather then service ..?
[18:04] <ratrace> marus: well it's native, and service is wrapped by systemctl, so...
[19:07] <jonathan_zz> I would always prefer service
[19:08] <jonathan_zz> systemctl makes no sensen
[19:08] <jonathan_zz> sense
[19:10] <jonathan_zz> https://lists.freedesktop.org/archives/systemd-devel/2016-April/036172.html ;-).
[19:10] <jonathan_zz> My message on systemd predictable network names :p.
[20:19] <bjornar> How is xenial loading the apparmor profile?
[20:20] <bjornar> I mean, no apparmor tools are installed, but profiles are, so what tools are used and from where? is this kernel handleing this?
[21:55] <marcony> hello, i have a problem.in my country some of betting sites like bet365.com is blocking.maybe somebody can help me? how i can to enter in? maybe there is something like pirat browsers?
[21:57] <k1l> marcony: please dont crosspost in all ubuntu channels. in here its for the 16.04 ubuntu version
[21:59] <marcony> k1l, copy that
[23:23] <nauticalnexus> Hello, I'm having issues upgrading from 14.04 to 16.04. I keep getting an error that won't allow me to upgrade.
[23:23] <k1l> nauticalnexus: which error?
[23:24] <nauticalnexus> k1l: I'll paste it somewhere please hold on
[23:24] <k1l> paste.ubuntu.com
[23:25] <nauticalnexus> k1l: https://paste.ubuntu.com/15725661/
[23:26] <braderhart> In Ubuntu 16.04 Beta 2 my external display shows as disconnected. Doesn't happen in earlier versions... can someone please help me gather the necessary information for a bug report?
[23:26] <k1l> nauticalnexus: does it stop after that?
[23:27] <nauticalnexus> k1l: yes.
[23:27] <k1l> nauticalnexus: you could try to change to the main servers. in your system settings
[23:27] <nauticalnexus> k1l: how so? Should I also mention I'm using GNOME?
[23:28] <k1l> nauticalnexus: software-properties-gtk
[23:29] <nauticalnexus> k1l: then what
[23:30] <k1l> "change to main servers"
[23:30] <nauticalnexus> oh yeah, sorry.
[23:30] <nauticalnexus> I'll try that. Hopefully it'll work
[23:32] <nauticalnexus> k1l: same error
[23:33] <nauticalnexus> is it not available for those that use English GB?
[23:34] <k1l> sure it is. but there seems to be an synciing issue with some packages.
[23:34] <k1l> but i am going to bed now. bye
[23:35] <nauticalnexus> oh okay, bye


[00:38] <OvenWerks> I must be odd I have never had the screen blanking fail. But then I don't use the locking part.
[00:46] <Eickmeyer> Yeah, it was apparently a problem since several bugs were found and never even acknowleged. Unmaintained code like that, especially when desktop security is involved, is kinda dodgy.
[02:39] <OvenWerks> Eickmeyer: I have my machine set to never go to sleep, blank screen only
[02:50] <Eickmeyer> OvenWerks: Mine is a laptop.
[14:21] <OvenWerks> Eickmeyer: With regaurd to the plymouth theme. I don't think it can be in /usr/share/* it has to be in /lib/plymouth? or has this changed?
[14:23] <OvenWerks> usr/share is not a part of initrd so unless plymouth is forced to start after root is mounted it won't work... except it does right now.
[14:24] <OvenWerks> So when did they move that? /usr is not guaranteed to be mounted at boot even.
[14:25] <OvenWerks> (from days of old and small drives)
[15:02]  * OvenWerks probably doesn't know what he is talking about...
[15:42] <Eickmeyer> OvenWerks: Steve Langasek told us not to worry about it, and that he's confident that our grub/plymouth themes simply revealed a bug in livecd-rootfs that needs to be addressed. He has code up for review now: https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/364206
[15:48] <Eickmeyer> OvenWerks: It's /usr/share. If you look at the code for the default Ubuntu theme, that's where it goes.
[15:49] <Eickmeyer> Steve said it's completley correct, just the reason it's causing problems is because livecd-rootfs isn't handling it gracefully.
[16:24] <OvenWerks> Eickmeyer: it has changed since 16.04 then. No problem.
[16:25] <OvenWerks> Probably a systemd change
[16:26] <Eickmeyer> Something. I honestly don't know, but that's likely since plymouth, systemd, etc. came from Red Hat/Fedora.
[20:04] <OvenWerks> Eickmeyer: I have 18.04, adding backports... install -menu fails because "trying to overwrite '/usr/share/ubuntustudio/applications/hdspmixer.desktop'" - which is also in package ubuntustudio-default-settings 0.65
[20:05] <Eickmeyer> OvenWerks: Eek! Lemme see what needs to happen there.
[20:05] <OvenWerks> I am not sure if that is because I have _settings from auto or not.
[20:06] <OvenWerks> Anyway we should make sure That file is not in both packages.
[20:06] <Eickmeyer> Doing that right now, I'll be pinging someone to reupload that.
[20:07] <Eickmeyer> Might mean a version bump.
[20:07] <OvenWerks> Well, like I say it may be a mixup in auto which I have now turned off
[20:07] <Eickmeyer> It's not in -default-settings, at least not in my local git.
[20:08] <OvenWerks> Right so maybe I have ano old -settings
[20:08] <Eickmeyer> Probably.
[20:10] <Eickmeyer> OvenWerks: Yeah, not good to mix autobuild and backports.
[20:10] <OvenWerks> backports is a new thing...
[20:10] <Eickmeyer> Yeah. Autobuild is for our testing, backports is for users.
[20:12] <Eickmeyer> That said, I need to delete everything in backport and rebuild without the date numbers, since we're at a stable build right now in prep for disco. I might have to branch for that purpose since the debhelper version is causing nothing to build.
[20:13] <OvenWerks> That can wait till april
[20:14] <Eickmeyer> Yeah. Not urgent.
[20:14] <OvenWerks> Probably the best thing to do is remove everything in there, make a new recipe then build
[20:14] <Eickmeyer> Yeah, that's the plan.
[20:14] <Eickmeyer> Should I remove everything now, you think?
[20:15] <OvenWerks> Sure.
[20:18] <OvenWerks> I down graded -settings then -menu worked.
[20:19] <OvenWerks> (and settings doesn't even show up)
[20:19] <Eickmeyer> Weird.
[20:19] <Eickmeyer> Are you pulling settings from autobuild?
[20:20] <OvenWerks> I am pretty sure the -settings I had came from auto which is now truned off
[20:20] <Eickmeyer> Ah, that explains it then.
[20:21] <OvenWerks> And the version that was causing problems no longer shows up as available either
[20:22] <OvenWerks> backports should have the same version as a release would have.
[20:22] <Eickmeyer> Okay, backports is empty. I'll be working on branching and redoing the recipes.
[20:24] <OvenWerks> That of course means backports should only get built when there is a new version number released. So that the version number is greater than what is in the repos for that cycle.
[20:24] <OvenWerks> Yup, it's all clean
[20:25] <Eickmeyer> Yes. Backports is set to only build on command, and I'll be modifying the build recipes to keep them from showing a date in the version. Right now is the perfect time to do it since everything is uploaded to Disco. I'll be making a branch for Cosmic and Bionic to build from since it requires a lower debhelper verison.
[20:25] <OvenWerks> Oh, ok.
[20:26] <Eickmeyer> Back later
[20:42] <OvenWerks> Eickmeyer: so B & C will require their own recipe... D will have a new recipe when we actually need it
[21:53] <Eickmeyer> OvenWerks: Correct. As it stands, B & C just need a minor modification, D can build from that as well, even though it wouldn't pass the Lintian tests if it were in the actual repo.
[22:55] <Eickmeyer> OvenWerks: Backports are all rebuilding with actual release versions.
[22:56] <Eickmeyer> I'll just have to merge the master branch into the backport branch for each package every 6 months.
[22:56] <Eickmeyer> I'll probably delete Cosmic from the PPA after July.
[22:59] <Eickmeyer> Once Disco releases we should change the compat & debhelper back to >=11 so that the autobuilds will start working again, but I want to proceed with caution.
[22:59]  * Eickmeyer is considering getting calf & lmms pulled from Debian and backported as well
[23:23] <OvenWerks> Cosmic is 18.04? Lots of people will still use that for LTS length. This is very true for those who do Studio over <other flavour>
[23:23] <Eickmeyer> Cosmic is 18.10
[23:23] <Eickmeyer> Bionic is 18.04
[23:23] <OvenWerks> Ah, so you would keep B and loose C, OK
[23:23] <Eickmeyer> Yes.
[23:24]  * OvenWerks needs more sleep...
[23:24] <Eickmeyer> OvenWerks: HAHAHAHA! I was just about to ask if you needed more sleep!
[23:25] <OvenWerks> My YF has not been sleeping well at night and has been waking me up to tell me so... frequently
[23:25] <OvenWerks> So it is less of a joke than normal...
[23:26]  * OvenWerks checks to see what the new PPA does to his system ;)
[23:26] <Eickmeyer> Yeah, my YF and I do that but only when one of us is tossing & turning.
[23:26] <Eickmeyer> OvenWerks: You might have to do a PPA Purge first, but it won't matter if you have autobuilds.
[23:27] <OvenWerks> The following packages will be upgraded:
[23:27] <OvenWerks>   numix-blue-gtk-theme plymouth-theme-ubuntustudio ubuntustudio-look
[23:27] <OvenWerks>   ubuntustudio-wallpapers
[23:27] <Eickmeyer> Ah, that's because vorlon (Steve) and I had to force a new version number.
[23:27] <OvenWerks> Thats not bad then
[23:28] <Eickmeyer> Nah. I would revert the debhelper version in master for all of those packages, but that's not a good idea if we're about to hit beta freeze.
[23:28] <OvenWerks> It seems to be updating with no error anyway.
[23:29] <Eickmeyer> Which, I believe, is the 25th. Probably just need minimal changes from here until then.
[23:30]  * OvenWerks was taking a quick look through Cadence...
[23:30] <OvenWerks> It does not look easy to modify/fix
[23:30] <Eickmeyer> Cadence isn't being actively developed right now.
[23:31] <Eickmeyer> He's put all of his effort into Carla.
[23:31] <OvenWerks> Eickmeyer: we have for 19.04 what we should have had for 18.04
[23:31] <OvenWerks> Carla is well worth while
[23:31] <Eickmeyer> OvenWerks: This is true.
[23:32] <OvenWerks> I think he is thinking about removing ladish from kxstudio/cadence
[23:32] <OvenWerks> For bit rot
[23:32] <Eickmeyer> Yeah. I think he's taking the code and integrating it directly into Claudia.
[23:33] <Eickmeyer> But he has that on hold for now. He's been telling people in bug reports that the entire Cadence suite isn't in his sights at this time, but perhaps mid-year he'll look at it again.
[23:33] <OvenWerks> Linux audio is changing, unless someone uses non-stuff jack is not really needed. Plugins have taken over
[23:34] <Eickmeyer> Right. Session management has gone into the DAWs themselves for the most part.
[23:34] <OvenWerks> Jack is only needed for those who need more than one audio device or more than one program...
[23:35] <OvenWerks> usb devices are a thing, but multi-applications less so any more
[23:35] <Eickmeyer> Right. When I'm doing live production and round-tripping audio through my DAW, I typically also need something to playback spotify or amazon music, which is when I have to use the Pulse bridge, which, unfortunately, introduces latency due to buffer requirements.
[23:36] <OvenWerks> Eickmeyer: if I feel energetic, I may play more with the pulse-jack bridge.
[23:37] <OvenWerks> I think jack should look like a pulse device and use the same kind of code.
[23:38] <Eickmeyer> Jack completely taking-over and using Pulse as a device is backwards indeed.
[23:38] <Eickmeyer> Of course, then pipewire is supposed to solve everything. /meme
[23:38] <OvenWerks> I think with the right buffering in the bridge, jackd could run at any latency without dragging pulse along for the ride
[23:39] <OvenWerks> pipewire is a long way from there. More likely is pipewire replacing pulse and still needing a bridge for jack.
[23:40] <Eickmeyer> Right now, the lowest latency I can get with a USB device and Pulse is about 128/3, and even then get about an xrun/hour. WIthout pulse? 64/3.
[23:40] <OvenWerks> -controls should allow for driver = forewire
[23:40] <OvenWerks> *firewire
[23:41] <Eickmeyer> Yeah. I think that's where people have run into issues.
[23:41] <Eickmeyer> Unfortunately, I don't have a firewire device to test with, nor do I have a computer with firewire.
[23:41] <OvenWerks> Odd, I can get below that here... but pci device
[23:42] <OvenWerks> Generally the same thing applies for both firewire and USB... use a dedicated card for it. Hard to do with a laptop
[23:43] <Eickmeyer> Exactly. All I have are laptops. I have an old Mac Mini that I use as a server, but I'm not about to reformat that to use as a guinea pig.
[23:43]  * Eickmeyer might be able to repurpose an old MacBook Pro at the end of this month
[23:43] <Eickmeyer> But then I still don't have a Firewire audio device.
[23:44] <OvenWerks> It depends where the computer audio world goes in the next while, AVB or aes67 could take over the whole works from USB...
[23:45] <OvenWerks> It would be cheaper to add a better enet chip than just about anything else.
[23:45] <Eickmeyer> I can see AES67 being huge. I mean, we can already drive audio over a network with NetJack, but to standardize on AES67 would be awesome. I can even see that taking out Dante.
[23:46] <OvenWerks> the car manufatures seem to be going AVB... that could make HW cheap.
[23:46] <OvenWerks> For Linux both aes67 and avb need the same thing... an intel i210.
[23:47] <OvenWerks> (or the equiv Broadcom that apple uses)
[23:48]  * OvenWerks wanders off for a nap (feeling old)
[23:48] <Eickmeyer> Do it. :)