[01:12] <Hilikus> i don't know if this is a mythbuntu or mythtv issue, but why can't i use "service mythtv-backend start|stop.." anymore?
[01:12] <Hilikus> to start and stop the backend
[03:26] <jya> is there an official way to configure ntp in mythbuntu ?
[03:26] <jya> like a fancy little graphical widget or should I just modify some text file?
[13:17] <Riddell> how do I actually test a mythbuntu install?
[13:18] <Riddell> I'm a bit lost in the frontend/backend stuff
[13:46] <Kwisher_wrk> the b/e is what does the recordings, f/e is for watching your content
[13:48] <Kwisher_wrk> what type of tuners do you have?


[03:38] <micahg> so, initially, I think the hope with packaging mozjs185 was that there would be a community around it to support keeping it updated with the various Mozilla releases
[03:38] <micahg> this really didn't happen
[03:38] <darkxst> micahg, there will be more regular updates now (from upstream side atleast)
[03:39] <micahg> ISTR hearing that before...
[03:39] <darkxst> I got all the versioning code mainlined
[03:39] <darkxst> so no doing a release is basically just spinning a tarball
[03:39] <darkxst> now
[03:39] <micahg> unfortunantely, I'm a little out of touch at the moment with upstream Mozilla
[03:39] <micahg> that's good at least
[03:40] <darkxst> the idea being that with mozjs24, there should be regular point releases
[03:40] <micahg> just in time for the LTS, that's another good thing :)
[03:41] <micahg> now, will there be some type of migration from mozjs24 to mozjs31 so the LTS isn't abandoned 9 months or so in :)
[03:45] <micahg> darkxst: if couchdb is the only holdout, I'd be for enabling the internal code copy and be done with it
[03:45] <darkxst> I don't know jsapi is still a bit unstable
[03:45] <micahg> right, that's the problem :)
[03:45] <darkxst> hopefully it will stabilise by 31 and after
[03:46] <darkxst> micahg, from what I have seen, most other projects would be trivial to port, its just a lot of work and results in big diffs
[03:47] <micahg> I've done a round of this before :)
[03:50] <micahg> darkxst: BTW, is there an Ubuntu GNOME channel?
[03:51] <darkxst> #ubuntu-gnome
[03:51] <darkxst> porting gjs was a pain, since nothing was documented ;(
[03:51] <micahg> that sounds familiar
[03:52] <darkxst> a number of changes werent picked up by the compiler
[03:52] <darkxst> so ended up chasing down random crashing tests
[03:54] <darkxst> mozjs24 will be fun also since the C api is completely removed!
[04:09] <micahg> right, in the long term good, but short term really painful
[04:25] <darkxst> yes basically, they do plan to stabilise things, once they are finished ripping it apart
[06:58] <dholbach> good morning
[07:18] <iulian> Morning dholbach.
[07:18] <dholbach> hi iulian


[00:02] <jbicha> fes_: did you used to be able to use GNOME on Wayland on this computer with nouveau?
[00:05] <fes_> With earlier versions of Ubuntu, for example 16.10? Yes I was.
[00:06] <jbicha> I looked at the journal errors that ubuntu-bug added to your bug report
[00:07] <jbicha> it says that GDM is using X
[00:07] <jbicha> but it normally uses Wayland by default, so whatever is causing it to use X is probably the same thing that isn't giving you a Wayland option
[00:09] <jbicha> do you want to try using Intel by default instead of nouveau?
[00:09] <jbicha> if so, see what happens if you install the amd64 deb from https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+sourcepub/7541961/+listing-archive-extra
[00:09] <jbicha> (I'm hoping to get switcheroo-control into Ubuntu before 17.04 is released)
[00:10] <jbicha> reboot after installing that
[00:18] <fes_> how do I use intel instead of nouveau? This is a hybrid graphics laptop with both intel GPU and nvidia GPU.
[00:20] <fes_> I will install that package you mentioned. Is there anything I should take notice of to use that package to its full potential or just to get it to make a difference?
[00:21] <fes_> Do you want me to install both the debug package and the ordinary package or is the ordinary (switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb) enough?
[00:24] <fes_> I have installed it and I will restart not to see if it makes a difference.
[00:28] <fes> it did not make a difference. I am still not able to use wayland session.
[00:28] <jbicha> so switcheroo-control is supposed to default you to using the integrated graphics card
[00:29] <jbicha> but if you right-click on an app launcher in GNOME Shell, you can launch it using the dedicated, more powerful graphics card
[00:30] <jbicha> you don't need the dbgsym package
[00:33] <jbicha> could you open Settings>Details and paste what you see in the Graphics line?
[00:33] <fes> that works!
[00:33] <fes> sure...
[00:33] <fes> Graphics: Intel® Sandybridge Mobile / Intel® Sandybridge Mobile
[00:34] <fes> Weird that it mentions intel twice, right?
[00:34] <jbicha> hmm
[00:34] <jbicha> I don't think it's supposed to mention the same thing twice
[00:35] <jbicha> I have a simple Intel-only laptop
[00:37] <fes> would you like to use teamviewer or some other remote service to check out my system? I am open to letting you do that so that thiscan be solved.
[00:43] <fes> what is also weird is that if I execute "DRI_PRIME=1 glxinfo" I get intel's GPU information when I in earlier Ubuntu's got the NVIDIA information.
[00:45] <fes> I am updating the package right now and I see that there's drivers updates. I will restart when the upgrade has finished and see if it makes a difference.
[00:46] <jbicha> it might be suggesting that you install the NVIDIA proprietary drivers
[00:49] <fes> among the files where libdrm packages fror nouveau2, intel, etc.
[00:54] <jbicha> ok, could you try rebooting?
[00:54] <fes> Will reboot soon and come back here...
[00:59] <fes> the upgrade made no difference.
[01:01] <jbicha> I don't really know then, I commented on your bug and asked if you could report this to GNOME
[01:08] <fes> I have asked in #gnome over at GIMPNet and hope that someone will reply.
[01:08] <fes> Thanks for helping out, jbicha
[02:14] <fes> jbicha, there was wayland and mesa updates five minutes and now when I restarted.. IT WORKED! I AM NOW USING WAYLAND :D
[02:14] <fes> Did you have something to do with this? ;)
[02:18] <jbicha> lol, I didn't touch anything!
[02:19] <fes> :D
[02:21] <jbicha> does the Launch using Dedicated Graphics Card option work? http://www.hadess.net/2016/10/dual-gpu-integration-in-gnome.html
[02:22] <jbicha> you can close your bug by setting the Status to Fix Released
[05:00] <gnubuntu> why is scrolling so terrible in firefox
[05:09] <darkxst> gnubuntu, what do you mean? its fine here
[05:09] <darkxst> tearing? lagging?
[05:11] <gnubuntu> both
[05:11] <darkxst> what gpu/drivers?
[05:12] <gnubuntu> radeon free
[05:12] <gnubuntu> 16.10 btw
[05:13] <darkxst> I don't have radeon, but generally tearing seems worst with nvidia proprietry under X
[05:13] <darkxst> is it only firefox?
[05:13] <gnubuntu> i think so
[05:14] <darkxst> file a bug
[05:15] <gnubuntu> on launchpad?
[05:15] <darkxst> yep
[05:16] <gnubuntu> i noticed 2 other things - firefox scrollbars are 1px away from the edge of the screen when maximised or fullscreen
[05:17] <gnubuntu> makes it hard and tiring to grab it - you cant just move the pointer to the right
[05:20] <gnubuntu> 2/ i wanted to use ub-gn on a c2d laptop but the fan was kicking too much so i echo'd the conservative governor to replace ondemand
[05:20] <darkxst> you mean the actual scrollbar is only 1px wide?
[05:20] <gnubuntu> no
[05:21] <gnubuntu> the scrollbar is double in wide size i think this is intentional, i saw a bug about this iirc
[05:21] <gnubuntu> there is 1px space between the scrollbar and the screen edge / end of window on the right or bottom
[05:22] <gnubuntu> so if you move your pointer right to grab it you cant - its just empty scroll space
[05:24] <gnubuntu> about the cpu governor - something kept one of the cpu cores obove min frequency which prevented the fan from going quiet, for no visible reason - no task active
[05:24] <gnubuntu> as if it was stuck on a higher freq
[05:53] <gnubuntu>


[00:39] <jose> mhall119: hey, I believe design only takes care of the design and we have to manage the printing ourselves
[00:40] <jose> at least that's what they told me
[01:00] <mhall119> jose: we can find someone in Canonical to get the printing done. I'll try and find who did it for me last time
[01:00] <jose> yay!
[01:00] <jose> I'll be staying at the Hilton, feel free to ship them to me there. I'll be receiving a lot of packages anyways
[17:03] <czajkowski> mhall119: see over there ---------->
[17:28] <popey>                                                    hmm?


[05:33] <cobradevil> hello all
[05:33] <cobradevil> is there someone around which is responsible for the kernel config options?
[05:42] <cobradevil> i have a question about the kernel config cachefs which is enabled but not for nfs and afs
[05:42] <hyperair> apw: ^^
[05:45] <cobradevil> i thought cachefs was primarily designed for the network filesystems (at least that was the big hype)
[05:48] <cobradevil> hyperair: i'm not an irc guru ;) was that apw ^^ for my question?
[05:50] <hyperair> cobradevil: apw's probably the guy you should be asking. i was just pinging him
[05:50] <cobradevil> hyperair: ah okay thanx!
[11:20] <GobiTheGoblin> hi there. Are you guys involved with karmic dev?
[11:23] <GobiTheGoblin> k, seen the topic now =) The question is this: If I have understood correctly this should be somewhat correct dir/file structure of 2.6.31 http://kernel.ubuntu.com/git-repos/ubuntu/linux-2.6/drivers/hid/
[11:23] <GobiTheGoblin> Still, when i install sources from repos, those files are not there
[16:51] <rquarles> Pete, I want to get involved in the kernel, I am sitting in your talk at Atlanta Linux Fest
[16:57] <rquarles> 1
[16:57] <rquarles> !
[16:58] <rquarles> 1
[16:58] <rquarles> please disregard above lines, laggy wireless


[01:50] <teward> well I passed out.  Guess my travel lag was far more than i expected.
[01:50] <teward> wxl: incoming DM as soon as synapse-admin reloads.
[02:17] <wxl> neither apparently
[02:17] <wxl> Matrix is preferable though @teward001
[02:21] <teward> wxl: E:NOACCESS at the moment
[02:21] <teward> but since you're here on IRC I'll send you the reg code for our matrix.
[02:23] <teward> wxl: had issues getting synapse-admin up :p
[02:28] <teward> once you're registered have fun.  we DO need to make international support chans if we're hunting that
[02:28] <teward> but we restricted registration on matrix for Lubuntu to lubuntu.me addresses so.
[02:28] <teward> i.e. we control who can reg with the code.
[02:28] <teward> *consumes homemade tomato soup*
[15:28] <wxl> where's the old cdimage crontab? i can't find it for the life of me. or when do our isos build again?
[15:29] <wxl> well judging by logs it looks like i have at least 90 minutes so i guess that answers that
[15:30] <wxl> @teward001 how's that sandbox? or are you still on vacation? if the latter, when do you return?
[16:32] <wxl> huh that reply didn't came through but i was referring to lyn's comment re: lxqt-appearance
[17:40] <wxl> ^ there's our answer. it's just an image
[17:47] <wxl> should be a simple fix in lubuntu-artwork
[18:36] <teward> wxl: got a specific OS version you want installed?  It wasn't intended to be a GUI btw
[18:38] <teward> *loads up 23.10 daily from the daily images loud*
[18:38] <teward> s/loud/cloud
[18:48] <teward> wxl: details in your IRC because I don't have matrix working at the moment for me
[23:41] <wxl> so are we going to see ubuntu-classic-fonts in mantic then?
[23:42] <wxl> seed i mean
[23:43] <wxl> might be a good thing for a poll
[23:44] <wxl> maybe take screenshots
[23:44] <guiverc> i don't care... if we can document change I'll be happy...   myself it'll just be another package I add (along with nfs-common, aptitude etc) as its different & i don't usually get 'miffed' with aesthetics
[23:46] <wxl> i don't care too much either but some folks get really wound up about it
[23:46] <wxl> thus this gives the most vocal folks a chance to feel like they've been given an option to feel heard… and we're educating quietly in the process
[23:48] <wxl> i'm just still laughing over here that i could have corrected myself with s/\(see\)/\1d/ but that's a rather long way to do so XD
[23:52] <guiverc> :)