[01:46] <ding> hello
[03:03] <vivek__> I have just installed ubuntu mate and audio is not working
[03:03] <vivek__> vivek@vivek-VirtualBox:~$ lspci -v | grep Audio
[03:03] <vivek__> 00:05.0 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio Controller (rev 01)
[03:03] <vivek__> 	Subsystem: Dell 82801AA AC'97 Audio Controller
[03:05] <ouroumov_> Does the VM have access to the hardware?
[03:06] <vivek__> yep
[03:06] <vivek__> wait a min>
[03:06] <vivek__> audio enabled
[03:07] <vivek__> host pulse audio
[03:07] <vivek__> controller ich ac97
[03:09] <ouroumov_> have you checked the soud settings?
[03:09] <ouroumov_> sound *
[03:11] <vivek__> yep
[03:15] <ouroumov_> well, I don't know, maybe ask on our forums?
[03:16] <vivek__> alright cool no worries will live boot and check too
[03:16] <vivek__> brb
[03:41] <dudeman> is this thing on?
[03:45] <ouroumov_> hm?
[07:05] <guest-WwLItL> h
[07:05] <guest-WwLItL> opfer
[07:06] <guest-WwLItL> jn -ljkvcn-kygd
[07:06] <guest-WwLItL> dgnjdy
[07:06] <guest-WwLItL> ghzu4q+
[07:24] <guest-l1UmQJ> h
[07:25] <guest-EDIjlg> bg
[07:25] <guest-EDIjlg> hi
[09:33] <ozz> l
[09:43] <ouroumov> o
[11:29] <wacko> Test
[11:31] <wacko> Brave browser?
[11:37] <Fletch> Brave browser?
[12:02] <ouroumov> Fletch: what?
[12:04] <Fletch> ouroumov: have you tried brave web browser?
[12:12] <ouroumov> Fletch: no, never heard of it
[12:13] <ouroumov> Oh wait
[12:13] <ouroumov> The one developed by some ex-mozilla guy?
[12:13] <ouroumov> The one that block ads by default, except the ones it's been payed to clear?
[12:17] <Fletch> ouroumov: i just discovered it yesterday.
[12:18] <ouroumov> How's it looking?
[12:24] <Dartrek> Hi! I just got the Raspberry Pi 3 and put UM on it. I'm wondering one thing. With my Pi2 and OSMC, HD videos and HD youtube playback is perfect. However, in Ubuntu Mate, the playback on Youtube is quite slow. My question is, is there a way to optimize this? Or is it just caused by he large graphical interface running on Ubuntu Mate unlike OSMC?
[12:24] <Dartrek> (including web browsers, etc)
[12:24] <ouroumov> Hi Dartrek.
[12:25] <ouroumov> Dartrek, just to let you know there's a whole section of the Ubuntu MATE forum for RPi support requests. Maybe you'll have better luck getting an answer there. :]
[12:26] <Dartrek> Awesome possum ouroumov. I'll look in the forum.
[12:26] <ouroumov> ^^
[12:30] <Fletch> ouroumov: its pretty quick. It has this bubble feature on my android device which im not exactly a fan of.
[12:45] <Fletch> ouroumov: which browser do you use?
[12:45] <ouroumov> Firefox
[13:00] <allanViking> every random whole my Xorg starts taking 92% CPU on a 8 core i7 and everything starts acting really really slow. im using the default drivers (not nvidia closed source)
[13:02] <allanViking> only a reboot helps
[13:05] <ouroumov> allanViking, you sure it's xorg ?
[14:40] <nomic> allanviking
[14:40] <nomic> look at "top"
[14:41] <nomic> *gone*
[15:12] <allanViking> ouroumov: yes, taskmanager shows Xorg at 92% cpu
[15:15] <nomic> use top
[15:15] <nomic> to see what is using cpu
[15:15] <allanViking> will it show different numbers?
[15:15] <nomic> processes, useage
[15:15] <nomic> suppose thats 'taskmanager'
[15:16] <allanViking> sorry, I meant mate-system-monitor
[15:33] <Jelena28> spricht jemand deutsch?
[16:18] <Gallomimia> there seems to be a lack of understanding on my part as to who is responsible for the pretty graphical interface within GRUB on my ubuntu mate install. can someone shed some light on it? mine gives me some strange grief when unlocking full disk encryption. 100% of the time, i need to ctrl-alt-del the first time thru
[16:40] <pi3_> Hi all - Have you experienced power issues when updating 16.04 on a Pi3?
[16:49] <sixwheeledbeast> power issues?
[16:52] <pi3_> I got solid yellow then red boxes in the top right - I've been told this is due to the pi pulling too much power. It would then freeze the pi
[17:01] <sixwheeledbeast> is that after the update or during?
[17:04] <sixwheeledbeast> I would imagine it's USB cable or power supply related, I believe RPi3 needs about 3A?
[17:05] <pi3_> hi - i've got the official psu for the pi 3 - just seemed to hammer it whilst updating
[17:05] <pi3_> it's all good now but took several reboots and dpkg repairs etc
[17:06] <sixwheeledbeast> Do you have any stuff in the USB's, is it overheating?
[17:07] <pi3_> just an external sd card - i think it was getting a wee bit toasty but that's just a guess
[17:08] <pi3_> it was just a sunday afternoon experiment - it was created from a squashfs image - maybe that had something to do with it?
[18:14] <logical> hi, is it possible to set rhythmbox to reapeat one song?
[18:57] <dudeman> good afternoon
[21:57] <sixwheeledbeast> logical: put it in a play queue on repeat
[22:46] <john> red
[22:46] <john> hello
[22:47] <Guest17001> hello


[07:36] <mlankhorst> tjaalton: ping?
[07:38] <mlankhorst> oh nm I'll just send you a pull request, always wanted to do one of those
[07:52] <mlankhorst> RAOF: if you merge something please do it properly ;)
[07:52] <mlankhorst> try git diff c44dd5f11702cfc07f828d7f4716dc9cb7d257d0...ubuntu in libdrm
[08:28] <mlankhorst> tjaalton: I updated xf86-input-wacom in your tree
[09:41] <mlankhorst> bryceh/RAOF: evdev done, wacom done, synaptics done, xserver-xorg-video-all (minus geode) done. Xorg server ready, let her rip?
[09:42] <mlankhorst> I'll give the geode thing a shot first
[10:02] <RAOF> mlankhorst: Yeah, that was actually deliberate.
[10:02] <mlankhorst> RAOF: why?
[10:03] <RAOF> Because 2.4.37-0ubuntu1 was a pre-sync from debian-experimental; it wasn't actually a merge, so it doesn't need the previous changelog entries.
[10:04] <mlankhorst> ok
[10:04] <RAOF> When we sync we drop all the previous Ubuntu changelogs, partially because they no longer accurately describe the lineage of the package, partially because it's easier. :)
[10:05] <mlankhorst> shrug git-merge handles changelog entries for me automatically, but yeah
[10:05] <RAOF> Oh, yeah. It does for me, too.
[10:08] <mlankhorst> ok I'm just setting up my quantal-i386 changeroot again, I automated most of it now though
[10:25] <mlankhorst> RAOF: you could start uploading xorg-server to -proposed though with a note to keep it there for a bit, then prepare xserver-xorg-input-*
[10:28] <mlankhorst> for the video drivers, openchrome was updated to 0.3.0 but I couldn't find a binary package, and the real 0.3.0 name will conflict with openchrome from hardy so you need to change version probably
[10:28] <mlankhorst> ati and cirrus are git snapshots since they didn't post a release that worked in time
[10:29] <mlankhorst> and the rest of the *.orig.tar.gz I'll sell to you for a small price
[10:29] <mlankhorst> :P
[10:29] <jcristau> openchrome 0.3.0?
[10:30] <jcristau> ah.
[10:30] <jcristau> i was remembering the version wrong
[10:30] <mlankhorst> apm ark ati chips cirrus dummy fbdev glide glint i128 i740 intel mach64 mga modesetting neomagic nouveau openchrome qxl r128 rendition s3 savage siliconmotion sis sisusb tdfx trident vesa
[10:31] <mlankhorst> all the xorg video drivers that I had updated
[10:32] <mlankhorst> geode is going to need another fix but doesn't seem to use version control
[10:34] <mlankhorst> working on it though as soon as this apt-get dist-upgrade finishes
[11:00] <mlankhorst> ok early eod for me, still working on fixing up geode source
[11:00] <mlankhorst> will complete tomorrow :)
[12:25] <RAOF> mlankhorst: You know tomorrow's Saturday, right? :)
[12:26] <RAOF> mlankhorst: I'm trying my hand at robustifying the ‘get apport to catch Xserver crashes’ patch; I think I can do that before uploading 1.13 (ie: it'll be done Monday or Tuesday)
[12:26] <RAOF> Now, sleep
[12:27] <mlankhorst> RAOF: yeah just moving up this afternoon to play wtih a friend, and maybe visit him next week in afternoon :)
[19:10] <bryceh> tjaalton (and mlankhorst), I've moved the question you added at the end of https://wiki.ubuntu.com/X/Blueprints/LtsPointUpdatesForXorg up into the body proper.  What you listed as upgrade paths looks proper to me (and leann says it fits with foundation's recollection of the upgrade plan).
[19:11] <bryceh> apparently there's been some confusion about how we're going to handle the upgrades so hopefully this will help us nail things down.  Please take a look and make sure it's covering things correctly.
[19:20] <mlankhorst> bryceh: I would really want to sru libdrm if possible
[19:20] <mlankhorst> so that only packages pulled in by xorg would get updated
[19:23] <mlankhorst> this would make it possible to nuke the entire X stack and move back to the old one if needed :)
[19:23] <bryceh> mlankhorst, well good luck getting that by the sru admins...
[19:23] <mlankhorst> bryceh: I know, but it would make Xorg so much easier
[19:24] <bryceh> if there's specific patches in particular that would help, that might be doable.  but I don't know
[19:24] <mlankhorst> bryceh: it's specifically that having the new version shouldn't break existing functionality, and would make switching between new Xorg and old easier by a multitude
[19:26] <mlankhorst> same for libXrender, if things would mess up, apt-get remove .*lts-quantal could be made to work
[19:26] <mlankhorst> without leaving a severely broken system
[19:29] <mlankhorst> although maybe xrandr needs a different solution
[19:30] <mlankhorst> I think it makes sense to define the backported X stack as xorg package + xorg-server-core + all drivers + mesa
[19:31] <mlankhorst> and x11proto probably :)
[19:32] <mlankhorst> but if we would do that, there's no creepy magic going on any more, it would just be a different set of xorg packages
[19:34] <mlankhorst> just mesa+xorg+xorg-server-core+drivers under a different name
[19:36] <mlankhorst> if things mess up, we could create a script that uninstalls all the renamed xorg packages, the original xorg package names, and reinstall the original packages without leaving the system in a creepy halfbroken state because of libdrm
[19:37] <mlankhorst> that would also mean sru'ing the fix for plymouth on arm, but we should really aim for it :)
[19:38] <bryceh> mlankhorst, have you talked with RAOF about this?  what's his take?
[19:38] <mlankhorst> not sure yet
[19:39] <mlankhorst> I'm gonna pester him, and after x1.13 is uploaded do another renamed x stack for testing, but this time only including the packages I want to update unrenamed, and the x stack itself renamed
[19:39] <mlankhorst> to show you can switch between them without scary brokenness
[19:43] <mlankhorst> or at least, when it does break but it would leave your system in a state where it can still boot :)
[19:52] <jcristau> booting is overrated
[19:53] <mlankhorst> I already had a problem where I uninstalled libdrm-renamed, but the old libdrm was overwritten by it
[19:55] <jcristau> at which point no plymouth, and things get unhappy?
[19:56] <mlankhorst> erm plymouth package is fine, it was just libdrm*.so.* missing
[19:56] <mlankhorst> which plymouth didn't like very much
[19:57] <jcristau> yeah that's what i meant by no plymouth
[19:57] <jcristau> sorry
[19:59] <mlankhorst> :)
[20:59] <tjaalton> mlankhorst: oh you managed to update it, cool. the shared repo sometimes doesn't really work that well..
[21:00] <tjaalton> should probably push it to kernel.u.c or such..
[21:00] <tjaalton> bryceh: ok, thanks. I'll read it once it's nice and calm ;)
[21:00] <mlankhorst> it's fine though
[21:02] <tjaalton> great then, remember there were some issues with it earlier
[21:03] <tjaalton> ooh new upstream
[21:03] <tjaalton> 0.15 wasn't interesting
[21:49] <tjaalton> bryceh: yeah it looks fine
[21:49]  * bryceh nods
[21:50] <tjaalton> did update the 12.04.0 x stack column to 'no update' though (instead of 'none' :)
[21:51] <tjaalton> https://wiki.ubuntu.com/Kernel/Release/Rolling looks scary, for 14.04