[05:11] <tjaalton> RAOF: so, 1.13 is not in -proposed yet?
[05:13] <RAOF> tjaalton: No; I got part-way through and then stalled on fixing up -ati. I didn't want to upload until I'd tested that it at least brings up a server on -ati, -intel, and -nouveau.
[05:14] <tjaalton> ok, cool. I have -intel to test on
[05:14] <tjaalton> though I bet you do as well :)
[05:14] <RAOF> And this morning someone wanted help fixing up pointer barriers for Fedora! I couldn't possibly go past helping them out a bit so I don't have to :)
[05:15] <tjaalton> magcius?-)
[05:15] <RAOF> Yeah
[05:16] <RAOF> Are you back from your holiday?
[05:16] <tjaalton> yup :( :)
[05:17] <tjaalton> just when it got hot
[05:18] <tjaalton> (lowest during the night was 22C)
[05:18] <RAOF> Oooh, urgh.
[05:18] <RAOF> That is incorrect.
[05:18] <RAOF> You should tell the weather to try again; this time, it failed.
[05:19] <tjaalton> hehe, yeah
[05:19] <tjaalton> well, there are still the weekends fully packed with activities, so there's time to get some of the "lost weather" back
[05:20] <tjaalton> it has been quite rainy and cool most of the july
[07:42] <mlankhorst> morning
[08:08] <mlankhorst> oh new intel drivers
[08:14] <mlankhorst> RAOF: how's uploading going? I just pushed intel 20.2 update
[08:14] <akheron> hey
[08:15] <akheron> I'm trying to find out why my X server crashes every now and then when waking from suspend
[08:15] <mlankhorst> heya
[08:15] <mlankhorst> f
[08:15] <mlankhorst> oops
[08:16] <akheron> I've got one crash dump that shows it segfaults on free() in Xi/xiproperty.c, in function XIDeleteAllDeviceProperties
[08:16] <mlankhorst> that usually means memory corruption, can you try running X with valgrind?
[08:16] <akheron> mlankhorst: sure, how?
[08:16] <mlankhorst> sec
[08:17] <mlankhorst> create a script /etc/X11/X2 with these contents
[08:17] <mlankhorst> #!/bin/bash
[08:17] <mlankhorst> exec /usr/bin/valgrind --track-origins=yes --leak-resolution=high --malloc-fill=ef --free-fill=df /usr/bin/Xorg "$@" -verbose 10 &>>/home/yourusername/xorg-valgrind.log
[08:17] <mlankhorst> make it executable
[08:18] <mlankhorst> then remake the /etc/X11/X symlink, point it to /etc/X11/X2
[08:18] <mlankhorst> then just restart lightdm :)
[08:18] <mlankhorst> to restore, sudo ln -sf /usr/bin/Xorg /etc/X11/X
[08:19] <akheron> ok, let's try
[08:23] <akheron> yeah, now running in valgrind
[08:24] <mlankhorst> it's more useful if you install xserver-xorg-core-dbg and xserver-xorg-input-(evdev,synaptics)-dbgsym
[08:25] <akheron> what apt source I need for the -dbgsym packages?
[08:25] <mlankhorst> https://wiki.ubuntu.com/DebuggingProgramCrash/ see Debug Symbol Packages
[08:26] <akheron> ah yeah, without those the stack traces show ???
[08:27] <mlankhorst> yeah for quantal I made -dbg packages so you would no longer need to enable that repo to debug most of X :)
[08:27] <akheron> heh
[08:28] <akheron> will I need a dbgsym package for the intel driver too?
[08:28] <akheron> intel_drv.so
[08:28] <mlankhorst> if it shows up it would help
[08:29] <mlankhorst> same for libdrm
[08:29] <akheron> yeah, both seem to show up
[08:30] <akheron> this will take some time, as the crahs doesn't occur every time when waking from suspend
[08:30] <akheron> usually once every two days
[08:30] <akheron> or so
[08:32] <tjaalton> what do you mean by a 'crash'?
[08:32] <tjaalton> you get the login screen?
[08:32] <akheron> tjaalton: yes
[08:32] <tjaalton> ok
[08:33] <akheron> actually I'm not sure if it's always when waking from suspend
[08:33] <akheron> sometimes the machine won't suspend and I get a login screen, so it happens when going to suspend
[08:40] <akheron> hmm, I still get ???'s from intel_drv.so
[08:41] <mlankhorst> xserver-xorg-video-intel-dbg ?
[08:51] <mlankhorst> and maybe libdrm.*-dbg
[09:53] <akheron> mlankhorst: nope, I still get ???'s
[10:41] <RAOF> mlankhorst: I'm a bit confused by -ati and -evdev, but mostly evdev. What happened to 0005-fix-horiz-scrolling.patch  0006-axis-label-overrun.patch? They got added to a commit? And the git log is confusing; it's not a pre-sync to debian-experimental - there are still significant differences.
[10:42] <mlankhorst> hm you're right, i wanted to sync evdev but they didn't want the patches, so no longer valid
[10:44] <RAOF> Yeah.
[10:44] <RAOF> It's probably also worth dropping the explicit depends on xserver-xorg-core; we don't need them.
[10:44] <mlankhorst> RAOF: well I mesed up on evdev, first patch has to be manually unapplied with patch -Rp1, then you get the stable release again, to build against
[10:44] <RAOF> mlankhorst: Hm, ok.
[10:44] <mlankhorst> build system will reapply the patch
[10:44] <mlankhorst> ati.. let me check
[10:45] <RAOF> Yeah.
[10:46] <RAOF> ati doesn't have an orig.tar.gz; there's no xf86-video-ati 6.99.99 release (right?), so it should have a ~git version so we can bump it if we want to grab a newer snapshot.
[10:46] <mlankhorst> yeah
[10:47] <RAOF> Also, I was also confused by the rationale; you said you grabbed a newer snapshot for some UMS fixes, but this is a kms-only release?
[10:48] <mlankhorst> erm I meant it removes UMS, but there were some X server fixes after that that we need for building against x1.13
[10:48] <RAOF> Aaah. Ok, that makes sense.
[10:50] <mlankhorst> but yeah I didn't know yet if I wanted to do another pull or not so I just set version to a stub
[10:51] <RAOF> HEh.
[10:52] <mlankhorst> everything more clear now? :)
[10:53] <RAOF> So, another general comment - when pre-merging from Debian, it's nice if you include the (possibly incomplete) Debian changelog (complete with UNRELEASED), then add the Ubuntu changelog on top.
[10:53] <RAOF> Yeah, everything more clear now. You could have committed the version number at the time you committed, though. There's no reason you can't change the version if you decide you need a newer pull ;)
[10:54] <mlankhorst> aye but at that time I still had to update 25-ish other drivers, decided it was more easier not to handle everything as special if I could
[10:54] <RAOF> Fair enough.
[10:55] <mlankhorst> it's different if I just update -ati or -all
[11:00] <mlankhorst> but I would rather have the new stack soon, I want to do a new push of the x-1.13 ppa, but for precise renamed, to test the mechanics I want to propose
[11:03] <RAOF> Yeah. Now that's cleared up, I'll punch through it (tomorrow)
[11:03] <mlankhorst> great :)
[11:06] <mlankhorst> oh looks like new libXrandr landed too
[11:45] <akheron> mlankhorst: now it crashed
[11:45] <akheron> valgrind: m_mallocfree.c:288 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed.
[11:45] <akheron> valgrind: Heap block lo/hi size mismatch: lo = 80, hi = 0.
[11:45] <akheron> This is probably caused by your program erroneously writing past the
[11:45] <akheron> end of a heap block and corrupting heap metadata.  If you fix any
[11:45] <akheron> invalid writes reported by Memcheck, this assertion failure will
[11:45] <akheron> probably go away.  Please try that before reporting this as a bug.
[11:46] <akheron> there are 52 invalid writes in the valgrind log :/
[11:55] <mlankhorst> Wow, you managed to crash valgrind with invalid memory access? Amazing!
[11:55] <mlankhorst> I genuinely didn't know you could do that :0
[11:56] <akheron> :)
[11:57] <akheron> the crash always happens after this log line:
[11:57] <akheron> (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[11:57] <mlankhorst> just dump the full log somewhere
[11:58] <akheron> mlankhorst: https://gist.github.com/3206429
[11:59] <mlankhorst> what version of synaptics are you using?
[12:01] <akheron> mlankhorst: xserver-xorg-input-synaptics      1.6.2-1ubuntu1~precise1
[12:02] <mlankhorst> cnd: Arghhhhh synaptics is corrupting in that log again, updatetouchstate out of bounds, this time in the other direction
[12:04] <akheron> so this is a somewhat known prob?
[12:04] <mlankhorst> I don't know, I can silence some warnings
[12:06] <mlankhorst> one of the valgrind warnings there is known at least but I didn't isolate it to causing a crash, give me a sec
[12:07] <akheron> mlankhorst: ok, no hurry
[12:07] <akheron> I've had this issue for a long time
[12:08] <akheron> only now it started irritating me enough to look at it :)
[12:09] <mlankhorst> ok how good are you with packaging? can send you a patch or updated package to test
[12:09] <akheron> dpkg-buildpackage :)
[12:10] <akheron> so yes, I believe I can build and install a package
[12:10] <akheron> if you send a patch
[12:10] <mlankhorst> ok sure
[12:11] <mlankhorst> http://people.canonical.com/~mlankhorst/229-strip-mode-pointer.patch this will shut up some warnings at least
[12:12] <mlankhorst> if I backported it correctly, but I suspect it will not fix things enough
[12:16] <akheron> I'll have a try
[12:16] <akheron> thanks
[12:18] <mlankhorst> how long has this been happening though, new breakage or old?
[12:18] <mlankhorst> well, before july or after?
[12:44] <akheron> mlankhorst: before
[12:44] <akheron> I got this machine on february, and first used debian with gnome 3
[12:45] <akheron> it had odd bugs (with synaptics) so I decided to try ubuntu
[12:45] <akheron> and ubuntu crashes :)
[12:45] <akheron> I installed it maybe two months ago, and the problem has been there all the time
[12:46] <mlankhorst> ok
[12:46] <akheron> the package is building now, btw
[12:46] <mlankhorst> else I was thinking the security update but I guess we could rule it out then
[12:52] <akheron> mlankhorst: yah, certainly not the last update
[12:52] <akheron> *yeah
[12:52] <mlankhorst> if it still crashes one more time, which is likely, please update synaptics http://people.canonical.com/~mlankhorst/synaptics-dbg.patch , but I want to rule this issue out first :)
[12:53] <akheron> mlankhorst: ok
[12:53] <mlankhorst> a lot of valgrind errors should be gone at least
[12:53] <akheron> too bad the only way to reproduce seems to be to suspend and resume 20 times...
[12:54] <mlankhorst> you're helping a lot of others, I can't seem to reproduce it :)
[13:04] <akheron> now running 2:1.11.4-0ubuntu10.7~ppa :)
[13:05] <mlankhorst> what if you touch keypad during suspend, ?
[13:05] <mlankhorst> well, during start or end of suspend
[13:20] <akheron> mlankhorst: that sometimes makes it crash
[13:20] <akheron> but I'm not sure
[13:20] <akheron> the last time, for example, it crashed about 5 sec after fully waking up
[13:21] <mlankhorst> akheron: can you give a valgrind log from that and then patch synaptics?
[13:22] <akheron> mlankhorst: that's the valgrind log I gave you
[13:24] <mlankhorst> erm I just want to see if other errors are gone now :)
[13:24] <akheron> mlankhorst: and now with the xserver-xorg patch, I still get the same invalid writes in UpdateTouchState
[13:24] <akheron> ah
[13:25] <akheron> I'll post a new log, though i didn't crash yet
[13:25] <akheron> a sec
[13:25] <mlankhorst> well the nice thing about the Xorg valgrind hook is that it records all attempts previously
[13:26] <mlankhorst> so it doesn't wipe the log on X server restart
[13:26] <cnd> mlankhorst: remember we reverted a patch in precise
[13:26] <cnd> without those patches we will get touch update corruption I think
[13:27] <mlankhorst> ok
[13:27] <akheron> mlankhorst: https://gist.github.com/3206891
[13:27] <akheron> in this one, I suspended & resumed once
[13:27] <mlankhorst> sigh looks like I have to figure out that failure, then
[13:27] <akheron> the errors are there but no crash yet
[13:28] <akheron> now I'll gotta go
[13:28] <akheron> will try the synaptics patch late today or tomorow
[13:28] <mlankhorst> cnd: Sigh so really the only way to fix it is to find out why the whole patch series crashes on the backported input stack?
[13:28] <cnd> yeah
[13:28] <mlankhorst> it's a simple null pointer dereference, but how it gets there makes no sense to me
[13:29] <cnd> hmm
[13:31] <mlankhorst> and upstream was unaffected, let me see if I can find the packages I was using again
[13:59] <mlankhorst> cnd: this was why it didn't make sense to me btw
[13:59] <mlankhorst> (0x009508d0 in ActivateKeyboardGrab (keybd=0x21d2fd10, grab=0x220cfd80, time=..., passive=0) at ../../dix/events.c:1616
[13:59] <mlankhorst> (gdb) print *keybd
[13:59] <mlankhorst> $1 = {public = {devicePrivate = 0x21c918a8, processInputProc = 0xa4cda0 <ProcessKeyboardEvent>, realInputProc = 0xa4cda0 <ProcessKeyboardEvent>,
[13:59] <mlankhorst>     enqueueInputProc = 0x947bf0 <EnqueueEvent>, on = 0}, next = 0x0, startup = 1, deviceProc = 0x649aa0, inited = 1, enabled = 0, coreEvents = 4,
[13:59] <mlankhorst>   deviceGrab = {grabTime = {months = 0, milliseconds = 1328245}, fromPassiveGrab = 0, implicitGrab = 0, activeGrab = 0x21d28ad8, grab = 0x0,
[13:59] <mlankhorst>     activatingKey = 0 '\000', ActivateGrab = 0x950750 <ActivateKeyboardGrab>, DeactivateGrab = 0x950570 <DeactivateKeyboardGrab>, sync = {frozen = 0,
[13:59] <mlankhorst>       state = 0, other = 0x0, event = 0x21d30270}}, type = 3, xinput_type = 96, name = 0x21d304a8 "SynPS/2 Synaptics TouchPad", id = 14, key = 0x0,
[13:59] <mlankhorst>   valuator = 0x21d30ad8, touch = 0x21d326c8, button = 0x21d30580, focus = 0x0, proximity = 0x0, kbdfeed = 0x0, ptrfeed = 0x21d32568, intfeed = 0x0,
[13:59] <mlankhorst>   stringfeed = 0x0, bell = 0x0, leds = 0x0, xkb_interest = 0x0, config_info = 0x21d304c8 "udev:/sys/devices/platform/i8042/serio1/input/input7/event7",
[13:59] <mlankhorst>   unused_classes = 0x0, saved_master_id = 0, devPrivates = 0x21d2ff78, unwrapProc = 0xa4ac50 <xkbUnwrapProc>, spriteInfo = 0x21d2ff5c, master = 0x21bbfed0,
[14:00] <mlankhorst>   lastSlave = 0x0, last = {valuators = {683, 384, 0 <repeats 34 times>}, numValuators = 4, slave = 0x0, scroll = 0x21d30bf0, num_touches = 2,
[14:00] <mlankhorst>     touches = 0x21d32c10}, properties = {properties = 0x21d34a10, handlers = 0x21d34a48}, transform = {m = {{0, 0, 0}, {0, 0, 0}, {0, 0, 0}}},
[14:01] <mlankhorst> why is it in processkeyboardevent for a touchpad?
[14:01] <cnd> don't know off the top of my head
[14:01] <cnd> but it may be correct
[14:01] <cnd> as odd as that sounds
[14:01] <mlankhorst> ok
[14:03] <mlankhorst> but spriteinfo was freed at that point, so that seems to be what it's dereferencing
[14:05] <mlankhorst> are grabs supposed to be possible on disabled devices?
[14:24] <cnd> seems odd
[14:27] <cnd> I wish I could help out more, but I'm fighting a huge fire elsewhere right now :(
[14:31] <mlankhorst> yeah it's the gimp crash
[14:46] <mlankhorst> blindly looking through diff, isfloating seems to have added a check for !IsMaster(dev) upstream
[14:50] <mlankhorst> other than that, tons of code churn from c99 initializers :/
[15:17] <mlankhorst> ok admitting defeat, I don't understand the input stack :)
[18:21] <akheron> mlankhorst: so I have no hope? :)
[18:21] <mlankhorst> akheron: you do, you could go back to previous server-xorg 10.5
[18:21] <mlankhorst> but there's a crash you can trigger in that case
[18:22] <akheron> what crash?
[18:22] <mlankhorst> bug #1021517
[18:24] <akheron> uh
[18:25] <mlankhorst> akheron: the fun of having a weird stack :/
[18:28] <akheron> well, if there's anything I can do... or should I switch to quantal? :)
[18:29] <akheron> would it help if I patched synaptics now?
[18:34] <mlankhorst> it might :)
[18:34] <mlankhorst> would at least enable more debug info
[18:46] <akheron> mlankhorst:
[18:47] <akheron> ../../src/synaptics.c: In function 'UpdateTouchState':
[18:47] <akheron> ../../src/synaptics.c:3126:35: error: 'struct SynapticsHwState' has no member named 'num_slots'
[18:47] <akheron> ../../src/synaptics.c:3127:69: error: 'struct SynapticsHwState' has no member named 'open_slots'
[18:48] <mlankhorst> probably wrong member then, it should be clear from the code which one shouldbe used there but its end of workday and I have a headache :)
[18:48] <akheron> heh
[18:53] <akheron> mlankhorst: ok, got it to work
[18:54] <akheron> but how to build the .ddeb now?
[18:54] <mlankhorst> -nc
[19:00] <akheron> now it crashes
[19:00] <akheron> (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[19:00] <akheron> BUG: triggered 'if (priv->num_active_touches >= hw->num_mt_mask)'
[19:00] <akheron> BUG: ../../src/synaptics.c:3120 in UpdateTouchState()
[19:00] <mlankhorst> thought BUG_WARN was meant to be non-fatal
[19:00] <akheron> and then a segfault without printing the "Dumping slot state" message or anything else
[19:01] <mlankhorst> ah well just remove that line
[19:08] <akheron> mlankhorst:
[19:08] <akheron> (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[19:08] <akheron> (EE) synaptics: SynPS/2 Synaptics TouchPad: Dumping slot state:
[19:08] <akheron> Backtrace:
[19:08] <akheron> ==24744==
[19:08] <akheron> ==24744== Process terminating with default action of signal 11 (SIGSEGV)
[19:08] <akheron> ==24744==  General Protection Fault
[19:08] <akheron> ==24744==    at 0x67BD801: __fprintf_chk (fprintf_chk.c:28)
[19:08] <akheron> :>
[19:08] <mlankhorst>  oh right
[19:09] <mlankhorst> valgrind doesn't like that kind of thing
[19:09] <mlankhorst> right just leave it be for now, I'll get back to you :)
[19:09] <akheron> ok


[00:08] <daker> bkerensa: thank you
[05:29] <bkerensa> how bizarre
[06:36] <jcastro_> bkerensa: heya
[06:36] <jcastro_> all 5 stars in every category?
[06:36] <bkerensa> jcastro_: wat
[06:36] <bkerensa> it should not have
[06:36] <bkerensa> :/
[06:37] <jcastro_> better hurry, the first comment is like "lol wut perfect score?"
[06:38] <jcastro_> maybe in the meantime leave a comment if the stars are busted?
[06:38] <bkerensa> jcastro_: yeah idk Joeys review thing is broken
[06:39] <jcastro_> might want to cut it out or maybe leave a clarifying comment
[06:39] <jcastro_> also, is it a real sputnik image? I want to ask a question about it but in the comments.
[06:39] <jcastro_> so it's all public and stuff
[06:41] <jcastro_> ok sort of seems to work now?
[06:41] <jcastro_> 4.8?
[06:43] <jcastro_> ok now it's bar charts
[06:43] <bkerensa> jcastro_: idk its bugging bad
[06:43] <bkerensa> lol
[06:43] <bkerensa> jcastro_: it doesnt appear to calcular half points properly
[06:44] <bkerensa> jcastro_: realk sputnik image? Yes I tested with the sputnik image they ship and also did final testing on 12.10
[06:44] <bkerensa> also some mythbuntu testing occurred :)
[07:40] <dholbach> good morning
[07:41] <bkerensa> Happy Turkey Eve :)
[07:44] <philipballew> morning bkerensa and dholbach
[09:15] <czajkowski> aloha
[09:17] <philipballew> hello czajkowski
[12:01] <dholbach> jcastro_, balloons, mhall119, dpm: maybe you guys would like to hop on any of the next ubuntudev hangouts to talk about something where people can get involved? https://wiki.ubuntu.com/UbuntuDevelopment/Hangouts :)
[12:03] <dpm> dholbach, sure, I'm happy to hop into any, just let me know which one you want me to be in
[12:04] <dholbach> dpm, just grab any of them :)
[12:04] <dpm> ok, give me a few mins and I can pick one
[12:05] <dholbach> sure
[12:05] <dholbach> great :)
[13:49] <cjohnston> happy ham day to those in the US
[14:55] <daker> hi
[14:57] <cjohnston> hey daker
[14:59] <daker> holiday ?
[15:05] <cjohnston> something like that
[15:19] <daker> ok have fun :)
[15:25] <jono> hey folks
[15:25] <jono> dpm, free for a catch up?
[15:26] <dholbach> hey jono
[15:26] <dholbach> jono, how are you doing?
[15:26] <jono> hey dholbach :-)
[15:26] <jono> dholbach, good thanks!
[15:26] <dholbach> how's everything?
[15:26] <jono> getting the hang of this whole parenting business :-)
[15:26] <jono> dholbach,  you free for a catch up too?
[15:26] <jono> maybe we can go first
[15:26] <dholbach> sure
[15:26] <dholbach> let's do it
[15:26] <jono> dholbach, I will set it up
[15:32] <dpm> jono, on a call with zoltan, in 30 min?
[15:32] <cjohnston> hey jono... get any sleep yet?
[15:32] <jono> dpm, yeah that should be fine
[15:32] <cjohnston> ;-)
[15:32] <jono> cjohnston, some :-)
[15:32] <cjohnston> lol
[15:33] <czajkowski> listadmin++
[15:54] <dpm> hey jono, done with the call, so I'm free for a catch up
[15:56] <jono> dpm, cool, will  be a few mins
[16:01] <jono> dpm, ok setting it up
[16:01] <dpm> ok!
[16:02] <jono> dpm, invite sent :-)
[16:31] <dpm> jono, I lost you again
[16:32] <jono> dpm, damn net
[17:19] <dholbach> alright my friends - I call it a day
[17:19] <dholbach> see you all tomorrow
[17:27] <pleia2> https://lists.ubuntu.com/mailman/listinfo/community-announce :)
[17:27] <czajkowski> cool
[17:28]  * popey sets an auto-forward when receiving mail from that list, forwarding to every<EMAIL_ADDRESS>address :)
[17:45] <AlanBell> reasonable idea
[17:46] <AlanBell> or, subscribe all the other lists to it, and moderate all emails to that announce list
[17:47] <AlanBell> and don't allow people to self-release mails (by policy)
[17:48] <pleia2> yeah, all emails to the announce list are moderated
[22:28] <mhall119> pleia2: who can moderate that list?
[22:28]  * mhall119 just realized the last message here was 5 hours ago :(
[22:53] <czajkowski> mhall119: I can
[22:53] <czajkowski> mhall119: why are you posting to it? it's only for certain things to go out on it
[23:30] <mhall119> czajkowski: no, just wondering who I'd need to ping if I did post to it
[23:34] <czajkowski> me or lyz or daniel


[02:40] <ronj_> hey ho
[02:41] <ronj_> long time... I'll do some testing on Sunday at Montreal's GlobalJam, are there specific areas to focus on for Studio?
[02:43] <Blank__> oh, 'elo ronj_... sorry i didn't reply to that email all those months ago
[02:43] <ronj_> I plan to do my usual JACK/FFADO/Ardour tests on my FA66, but haven't been checking the mailing list a lot, so if there is recent stuff to try or potential regressions to have a look at, feel free to tell me :)
[02:44] <ronj_> Blank__: no problem :)
[02:45] <Blank__> ronj_, things have been a bit crazy here and i've not had time to do any more mixes of your stuff, nor have i been able to cull together all the various mixes i've done in the past :(
[02:47] <ronj_> that's cool Blank__ , I'm already pleased to hear about what you did, and well, if you come back at it, drop me a line!
[02:48] <Blank__> ronj_, i certainly shall... I'm hoping to actually start recording people sometime this year, as i've got several people interested in it
[02:48] <ronj_> yay
[02:49] <Blank__> i haven't actually done any full recording+mixing sessions in ardour, and i'm eager to use ardour 3, so i'm looking forward to it
[02:50] <Blank__> this laptop, however, needs a reformat and a severe cleanup in the /home :P
[22:32] <dezine> Hi, I'm trying to get an Echo Audiofire4 working on my 10.10. I am pretty clueless at this point and would appreciate some help.
[22:33] <ailo> dezine, Have you had it working on other systems?
[22:34] <dezine> It was working on my windows system, yes.
[22:35] <ailo> dezine, I meant other LInux systems. Are you new to Linux in general?
[22:35] <dezine> Oh, I have not. No, but I'm definitely new to using an interface with it.
[22:36] <ailo> dezine, I see. Are you using qjackctl? Did you try using "firewire" as the driver. I would recommend other settings to remain at default
[22:37] <ailo> dezine, To make a quick check, run qjackctl as root. If it works, you'll just need to add realtime access for the user.
[22:37] <dezine> hm lemme see
[22:37] <ailo> dezine, You could try this too: sudo jackd -d firewire
[22:37] <ailo> In a terminal
[22:39] <dezine> So at this point I should be able to hear the mic?
[22:39] <ailo> dezine, Are you able to start jackd?
[22:40] <ailo> dezine, Can you do it as a normal user: jackd -d firewire ?
[22:41] <dezine> jackd -d firewir
[22:41] <dezine> oops
[22:41] <dezine> Cannot attach audio driver
[22:42] <dezine> http://paste.ubuntu.com/588414/
[22:43] <ailo> dezine, It looks like you don't have realtime privilege. Do: cat /etc/security/limits.d/audio.conf
[22:44] <ailo> Should look like this: http://paste.ubuntu.com/588415/
[22:44] <dezine> Yeah it's the same
[22:45] <ailo> dezine, The next step is to allow realtime operation with the firewire device.
[22:45] <ailo> http://git.debian.org/?p=pkg-multimedia/ffado.git;a=blob_plain;f=debian/60-ffado.rules
[22:46] <ailo> Should go into /etc/udev/rules.d/60-ffado.rules
[22:46] <dezine> ok
[22:47] <ailo> You'll need to reboot
[22:48] <ailo> dezine, No special kernel? Did you use ubuntustudio-controls(not up to date and should not be used)?
[22:48] <dezine> hm I see 60-raw1394.rules
[22:49] <ailo> dezine, You can remove that. It's for the old firewire stack
[22:49] <dezine> I don't think there's anything special I installed ubuntu then installed the audio package
[22:50] <ailo> dezine, Ok. I don't have a firewire device myself mind you, so I can only help you so far. I think this should be enough to get you going. Let me know if it works.
[22:51] <dezine> Ok man thanks a lot.
[22:51] <dezine> I'll hop back on to let you know either way


[04:33] <pschulz01> Hello all.. I am having an interesting with my powerpc (MacMini) and jaunty.
[04:34] <pschulz01> I'm trying to upgrade everything.. I'm using it as a workstation..
[04:34] <pschulz01> Whan I remove gdm, the font on the virtual terminals goes screwy.. looks like an endian issue as the characters are almost readable.
[04:35] <pschulz01> I put gdm back in.. and it comes good again.
[06:41] <NCommander> pschulz01, what are you trying to do specifically?
[07:36] <pschulz01> NCommander: Looks like it might have 'fixed' itself.
[07:36] <pschulz01> NC
[07:36] <pschulz01> NCommander: I'm upgrading to jaunty.. but the box has seen a lot of customisations..
[07:37] <pschulz01> NCommander: Really just wan tto get the desktop up so I can use it as a terminal.
[07:38] <pschulz01> NCommander: I just uninstalled (purge) x11-common.. and a whole lot of packages suddenly wanted to be installed.
[07:39] <pschulz01> NCommander: It's getting better :-)
[13:45] <pschulz02> ,gk


[01:52] <Omnifrog> KEEP IT DOWN IN HERE. IT'S TOO DAMN NOISY
[02:10] <Omnifrog> awwww yeahhhh, all new fresh coils
[04:42]  * cyberanger sets off firecrackers for Omnifrog
[13:11] <aedend> http://foreignpolicy.com/2016/08/15/shadow-brokers-claim-to-be-selling-nsa-malware-in-what-could-be-historic-hack/
[19:31] <netritious> back wrst :)
[19:31] <wrst> wow netritious, that was quick
[19:31] <netritious> Howdy everyone
[19:32] <netritious> breaking records today lol
[19:32] <wrst> how are things going?
[19:33] <netritious> ok, negotiating a raise today. waiting to hear back.
[19:33] <netritious> how about you wrst?
[19:33] <wrst> doing well, hopefully your afternoon will be full of $$$$$$$$
[19:33] <netritious> one can only hope.
[19:36] <netritious> everyday now I am having a lxd/lxc epiphany. like, just figured out what to do with the t2.medium reserved instance that's been just sitting there. maybe lol
[19:37]  * |Ubik| files a frivilous lawsuit against cyberanger
[19:38] <|Ubik|> reserved instances...  good or bad? lol
[19:47] <netritious> it's fine. i use it for utility work mostly. was there before I was.
[19:49] <netritious> the "primary" reserved instance is 24/7 t2.medium. it too works fine. runs 5, maybe 6 services using a container for each, wired as needed.
[19:49] <netritious> I quote primary becasue the second one might as well be "secondary."
[19:54] <netritious> someone purchased use of two t2.mediums for three years up front. still 1.5 years left.
[19:58] <netritious> between backups to s3 and volume snapshots, I really can't justify putting the second one to use for anything other than a hot standby. I mean, the resource is paid for, might as well be hot and ready like a little ceaser's pizza, right?
[20:02] <netritious> |Ubik|: why is something wrong with reserved instances I should know about?
[20:20] <|Ubik|> netritious: Guess it depends... can save money if you're running a lot
[20:20] <|Ubik|> but if you don't need it, and you're stuck with it... lol
[20:20] <|Ubik|> might as well turn it into an ircd? :P
[20:23] <netritious> according to aws reports that one instance with the containers stays at 100% utilization. I'm thinking maybe I could split the load though by distributing between the two. dns, backup mx maybe. idk lol
[20:25] <netritious> top never seems to think the host stays at 100% however, on cpu or ram. it'll peek for a while occassionally, but that's seems  normal.
[20:25] <netritious> *that
[20:26] <netritious> and there is only one S in occasionally :$
[20:27] <|Ubik|> yeah
[20:27] <|Ubik|> I think the two reports differ, not sure why, but I've seen that too
[20:27] <|Ubik|> chances are cyberanger is skewing up your stats
[20:27] <netritious> most likely
[20:32] <netritious> I guess deep down I know it's bad practice to put all your eggs in one basket and want to be proactive about it.
[21:49] <cyberanger> netritious some people love bad eggs
[21:49] <cyberanger> I don't
[22:56] <netritious> Not a fan myself cyberanger


[12:27] <mup> Issue operator#976 opened: Improve typing for RelationEvent.unit <Created by yanksyoon> <https://github.com/canonical/operator/issues/976>
[19:37] <mup> PR operator#977 opened: Support read charmcraft.yaml <Created by syu-w> <https://github.com/canonical/operator/pull/977>


[02:10] <Corey> Slow learner?
[02:14] <IdleOne> Corey: could you repeat that. i didn't understand it the first time
[02:15] <Corey> "Let me dumb it down for you" and other phrases you should never use at work. :-)
 marta: i can look at it if you give me an ssh login
[04:15] <bazhang> is that like *worse* than teamviewer?
[04:17] <IdleOne> yes
[04:18] <IdleOne> with team viewer you can limit what the user can can't do (with ssh also) but with ssh you can't see what is happening while it happens
[04:18] <IdleOne> can or can't*
[04:19] <bazhang> thats what I suspected
[04:23] <IdleOne> warning given, now the user can do what they like I suppose
[04:26] <IdleOne> As a sysadmin he should know better then to even ask for ssh access.
[04:26] <IdleOne> wonder how he would feel if someone on one of the system he admins gave ssh to a stranger
[06:08] <Tm_T> I'd be against allowing "give me ssh access" requests in our support channels in the first place