[05:38] <pitti> Good morning
[06:48] <Sweet5hark> Moin!
[07:02] <didrocks> hey Sweet5hark!
[07:02] <Sweet5hark> didrocks: heya. ;)
[07:03] <didrocks> how are you? ready for Malta?
[07:04] <Sweet5hark> didrocks: all prepared and ready to go ;) -- are you already there?
[07:04] <didrocks> Sweet5hark: no, only coming the second week as well
[07:04] <didrocks> so no week-end on the sand!
[07:05] <Sweet5hark> didrocks: oh, one thing is still missing: some slides for my idea on how to make all Ubuntu an image for the win. ;)
[07:06] <didrocks> Sweet5hark: I'm finishing some juju investigation (hopefully today, maybe a little tomorrow), and then, I'll write some slides on what I think we should do to make ubuntu the rocking android and cloud dev platform!
[07:06]  * didrocks likes and is excited about the topic! :)
[07:07] <RAOF> Sweet5hark: Oooh, you're the system-image dudeikins?
[07:09] <didrocks> hey RAOF! you will be in Malta next week as well, right?
[07:09] <RAOF> Yes indeedy!
[07:10] <didrocks> will be nice to see you! :)
[07:10] <Sweet5hark> RAOF: well, "system image" sounds wrong to me as I wouldnt make a separation between "system" and "other" ;)
[07:10] <RAOF> didrocks: Likewise!
[07:11] <RAOF> Sweet5hark: Well, I do need to keep some non-image data around, too :)
[07:11] <didrocks> who needs those :)
[07:11] <didrocks> you just need a login and password
[07:11] <didrocks> and everything will be in the cloud :p
[07:12] <RAOF> Still needs the cloud configuration! :P
[07:12] <didrocks> oh my! ;-)
[07:12] <Sweet5hark> RAOF: sure, separating data out -- but I would separate between e.g. "base system" and "applications".
[07:13] <Sweet5hark> s/would/wouldnt/
[07:13] <Sweet5hark> gah
[07:13]  * Sweet5hark graps caffeine ...
[07:13]  * RAOF is not sure how that would work, but will be excited to find out!
[07:15] <Sweet5hark> didrocks: FWIW I think I have a build fixing bug 1296715 and bug 1219245 on trusty, so its likely SRU time soon ...
[07:16] <didrocks> I guess that's for RAOF? I'm happily not on the SRU team :p
[07:17]  * didrocks should drop his MIR duty as well
[07:20] <Sweet5hark> didrocks: 'soon' means likely around next week for LibreOffice ;) -- there is an upstream point release update in the mix too, and there was upstream work on -kde integration, which was why I dropped a revert on the broken -kde state. Unfortuneately, with the point release the upstream state is still worse for -kde than with the revert ...
[07:21] <didrocks> Sweet5hark: ahah, I did remember having some "fun" for the cycle I maintained OOo at the time with the -kde part :)
[07:21] <didrocks> do you know if people using the -kde flavor or just use bare LibreOffice, even on KDE?
[07:22]  * Sweet5hark mumbles "kill it with fire" ...
[07:22] <didrocks> oh, it's in that great state? :)
[07:23] <Sweet5hark> didrocks: people on kde use the kde plugin, not the bare libreoffice one (which would have a Windows 95 feel on pure X11)
[07:23] <Sweet5hark> didrocks: they _could_ use the -gtk plugin on kde though and it would look decent.
[07:24] <didrocks> Sweet5hark: and the -gtk -> -qt theming doesn't make it look even more kdeish?
[07:25] <didrocks> IIRC, they have quite a good support for gtk apps under kde look&feel
[07:25] <Sweet5hark> didrocks: anyway, there are two people with kde-knowhow doing work on it upstream now (jmux from Munich and llunak from Collabora), so this should improve -- but unlikely to do so much for libreoffice 4.2
[07:25] <didrocks> yeah…
[07:26] <Sweet5hark> didrocks: yeah, the look wouldnt be the issue IMHO. But does e.g. kubuntu ship gnome libs? I really dont know ...
[07:26] <didrocks> well, glib for sure :)
[08:02] <Laney> hallo
[08:02] <didrocks> hey Laney! how was your week-end?
[08:02] <pitti> hey Laney
[08:02] <pitti> bonjour didrocks
[08:02] <pitti> moin Sweet5hark
[08:03] <Laney> hey hey
[08:03] <Laney> it was extremely sunny (by my standards anyway)
[08:03] <Laney> → milkshakes in the sunshine
[08:03] <didrocks> guten morgen pitti!
[08:03] <didrocks> Laney: oh nice! :)
[08:04] <seb128> hey Laney didrocks pitti
[08:04] <seb128> how are you?
[08:04] <pitti> bonjour seb128
[08:04] <Sweet5hark> pitti: heya!
[08:04] <pitti> seb128: je vais bien, merci ! nous avons eu un bon week-end
[08:04] <Laney> then some climbing, one or two beers and a nice bike ride yesterday including a hill that i was too scared to go down at full speed
[08:04] <Laney> what about you (all)?
[08:04] <pitti> j'attends avec impatience à vous recontrer vendredi !
[08:04] <Laney> oh also I'm on crappy 3g because my broadband has a fault this morning
[08:04]  * Laney lags uot
[08:05] <didrocks> Laney: when to 2 museums this week-end (it was the european night of museum). Was ok, but not that exciting TBH :)
[08:07] <seb128> pitti, pareil !
[08:10] <Laney> didrocks: oh, that's a shame!
[08:10] <Laney> I didn't hear about that
[08:11] <didrocks> Laney: I saw that some days ago in the newspapers
[08:12] <Sweet5hark> seb128:  Hey, I think I have fixed bug 1296715!
[08:12] <seb128> Sweet5hark, hey, nice!
[09:44] <ogra_> seb128, do you know if/what could process  XDG dirs (like Downloads, Video etc ) on login ? we i have seen it a few times that these dirs are non-existent on a phone boot ... yet they are created at image build time
[09:45] <ogra_> (so i assume something touches them on session start=
[09:45] <ogra_> )
[09:45] <seb128> ogra_, xdg-user-dirs(-gtk)
[09:45] <ogra_> is that run regardless ?
[09:46] <seb128> regardless ov what?
[09:46] <seb128> http://freedesktop.org/wiki/Software/xdg-user-dirs/ for details
[09:46] <ogra_> well, we dont really run a standard session start on the phone
[09:46] <seb128> it's an autostart desktop entry
[09:46] <ogra_> right, which we dont process i think
[09:47] <seb128> k
[09:47] <seb128> so maybe some random apps create those
[09:47] <ogra_> (thats why i ask :) )
[09:47] <seb128> like gallery
[09:47] <seb128> but what you wrote doesn't make sense
[09:47] <ogra_> hmm, but that wouldnt remove all of them
[09:47] <seb128> they are on the image
[09:47] <seb128> but removed at boot?
[09:47] <ogra_> right
[09:47] <seb128> yeah, dunno about that, nothing deletes those dirs
[09:47] <Laney> Xsession.d runs xdg-user-dirs-update
[09:48] <ogra_> http://paste.ubuntu.com/7487744/
[09:48] <ogra_> thats what we run during build time
[09:48] <ogra_> and usually people still have these dirs
[09:48] <ogra_> but sometimes i get reports where they are gone
[09:48] <ogra_> with the same image where they exist for others
[09:49] <ogra_> so some race removes them i guess ...
[09:49] <seb128> gone or renamed?
[09:49] <seb128> xdg-user-dirs-update is supposed to rename those to their localized version
[09:49] <ogra_> gone
[09:49] <seb128> but it does prompt through a GTK UI iirc
[09:49] <seb128> so I would expect that to fail/do nothing on the phone
[09:50] <ogra_> right for the renaming we ship /usr/share/upstart/sessions/xdg-dirs.conf
[09:50] <seb128> k, no idea what is happening htne
[09:50] <seb128> then
[09:50] <ogra_> http://paste.ubuntu.com/7487754/
[09:50] <seb128> is anyone seeing those removed with content?
[09:51] <seb128> like having their photos or music wipped out at some random boot?
[09:51] <ogra_> on first boot
[09:51] <ogra_> so no, no content then
[09:51] <seb128> only on first boot?
[09:51] <ogra_> well, thats usually when people contact me :)
[09:52] <seb128> weird
[09:52] <ogra_> davmor2 is just opening a bug now ... he just saw it
[09:52] <seb128> well, at least we don't have cases of users having their datas erased after a random reboot
[09:52] <ogra_> nope, thats usually after a fresh install
[09:52] <ogra_> at least for now nobody complained to me about removed data  :)
[09:52] <seb128> do we have any log showing if those ever existed?
[09:52] <seb128> like are they missing
[09:52] <seb128> or is something deleting them on login?
[09:52] <ogra_> we know that others that flash the same image have them
[09:53] <ogra_> thats what i suspect
[09:53] <seb128> and it's first boot
[09:53] <seb128> like no special tweak
[09:53] <ogra_> right
[09:53] <seb128> so random behaviour
[09:53] <seb128> weird
[09:53] <ogra_> seems to also only be a small fraction of people
[09:54] <ogra_> but i hear about it once every two weeks or so
[09:55]  * ogra_ will put it in the heisenbug category for now ... and wait til someone sees it again
[09:55] <ogra_> i was just hoping you have an immediate idea or some such :)
[10:01] <seb128> yeah, I don't, sorry
[10:02] <ogra_> no worries
[15:54] <Laney> "<arch> build of …" emails are scary
[15:54] <Laney> just after doing a distro upload, but the relief when you see it's someone else's upload to a team ppa is nice
[16:07] <didrocks> ahah ;)
[16:07] <didrocks> I find the other way around worse
[16:08] <didrocks> like you upload some testing stuff to a ppa
[16:08] <didrocks> and you see the same source uploaded to the distro around the same time
[16:08] <didrocks> and just think "did I dput correctly?"
[16:10] <Laney> haha yes
[16:10] <Laney> fortunately both are pretty rare :P
[16:10] <didrocks> yep ;)
[19:06] <ry> ali1234, nothing that i'm aware of... a week or two ago i attempted to change the volume group name, and even though i updated fstab and i thought everything else relevant it rebooted to initramfs saying it couldn't find the ubuntu--vg-root, but i was able to use the lvm utility within initramfs and simply change the volume group back -- prior to this the system was still asking for my pw on boot though, which is why i was able
[19:06] <ry>  to change the volume group -- currently it's not asking for the pw and as a result there is nothing to se but a single encrypted sda3 (lvm is within the dmcrypted partition)
[19:06] <ali1234> ah...
[19:06] <ali1234> have you tried putting the vg name back?
[19:06] <ry> i changed itback originally, and have not attempted to change it again since
[19:07] <ali1234> hmm
[19:07] <ry> that was a good two weeks before this issue
[19:07] <ali1234> perhaps it is something to do with initrds
[19:08] <ali1234> it could be related to the vg stuff
[19:08] <ry> what controls the boot process on that level? -- when you have a full disk crypto ubuntu install and it prompts you for a pw during the boot, what prompts you for the pw? (becuse that is what -isn't- happening anymore)
[19:08] <ali1234> but the problem might not have happened until the next kernel update rebuilt the initrds
[19:08] <ry> ahh
[19:08] <ali1234> all that stuff is in the initrd afaik
[19:08] <ali1234> which is rebuilt on kernel update from various config files
[19:08] <ali1234> more than that i do not know
[19:08]  * ry searches for initrd_for_dummies.pdf
[19:09] <ali1234> the command is update-initramfs
[19:09] <ali1234> i've never used disk encryption though
[19:10] <ali1234> do yo have multiple kernels installed at the grub menu? try booting an older one if so?
[19:10] <ry> i think i just had the one it was using and a *-recovery one
[19:10] <ry> i tried all the options
[19:11] <ali1234> that's probably not it then
[19:11] <ry> i did try a live cd,and chrooting the sda3 after i decrypted it and then running update-initramfs (based on some reference articles/posts i found)
[19:11] <ry> but nothing worked
[19:11] <ry> i'm sure at this point it was in large part due to my lack of understanding of initramfs
[19:11] <ali1234> initramfs is a tiny root filesystem with just enough stuff to boot the real system
[19:12] <ali1234> it is the envorinment you are inside when it fails to boot
[19:12] <ali1234> that is all in ram
[19:12] <ry> i was unable to do anything useful from it, other than being able to change the lvm volume group in one occasion
[19:12] <ry> yeah
[19:12] <ali1234> you should be able to examine some log files at least... like dmesg
[19:12] <ry> i guessed that much by the lack of logs and read only filesystem
[19:12] <ry> lol
[19:12] <ry> shit
[19:13] <ry> the one thing i didn't think of was dmesg
[19:13] <ry> i looked for logs but couldn't find any under initramfs
[19:13] <ali1234> it should say something about being unable to mount the root partition...
[19:13] <ali1234> try different vts too
[19:13] <ali1234> (alt-f1 to 12)
[19:13] <ali1234> sometimes the log is written directly to the vt, but not the default one
[19:13] <ry> well vts?
[19:14] <ry> https://www.dropbox.com/s/nr0e0pyh1oh8lyt/2014-05-13%2001.12.16.jpg
[19:14] <ry> forgive the focus
[19:14] <ry> that is where i was left
[19:14] <ali1234> yeah, press alt-f1, alt-f2, alt-f3 etc up to alt-f12
[19:14] <ali1234> the real log can be hidden on a different one
[19:15] <ry> lol damn
[19:15]  * ry makes note
[19:15] <ry> (hopefully that is mentioned in initrd_for_dummies.pdf)
[19:17] <ali1234> oh, did you do anything like install virtualbox or nvidia drivers, or other drivers like that?
[19:18] <ali1234> those will all cause the initrd to be rebuilt
[19:18] <ali1234> i'm pretty sure this is caused by the wrong vg name being stuck somewhere
[19:19] <ry> it's very possible that is what happened... i'm using the latest nvidia drivers for the nvs5400m w/ bumblebee and i also have zfsonlniux and vmware workstation installed... so it's likely during an update one of the modules updated the kernel
[19:20] <ry> i have no experience with full disk crypto, even less with LUKS
[19:20] <ali1234> kernel modules live in the initrd too, so updating them updates the initrd
[19:20] <ali1234> neither do it
[19:20] <ali1234> *i
[19:21] <ry> other than blowing up my poor thinkpad t430's ubuntu 14.04 install i like it so far
[19:21] <ry> lol
[19:21] <ry> i never thought i'd see the day where i was almost ok with using unity
[19:22] <ry> after endless attempts at making gnome-fallback not suck on 14.04 i refused to switch back to 12.04 so i figured i'd try to make unity work
[19:22] <ry> also... once i noticed you could modify UI elements using CSS that definitely added weight to my decisino
[19:22] <ali1234> i heartily recommend xubuntu
[19:23] <ry> the only thing i really can't stand is the "top bar" or whatever the gnome-panel equivalent on unity is called that can't be hidden/window dodged or removed
[19:23] <ali1234> just don't try to install it at the same time as unity (tedg: hint hint)
[19:23] <ry> i also tried xubuntu but absolutely hated what they did with it
[19:23] <ali1234> you can easily configure it back to a standard panel
[19:23] <ry> though i installed the non-ubuntu corrupted xfce4 on a ubuntu 14.04 server i setup over the weekend and i'm fine with that over xrdp at least
[19:23] <ali1234> in fact i wrote a piece of software specifically for this purpose
[19:24] <ali1234> https://github.com/ali1234/panel-switch
[19:24] <ali1234> if you run it with my configuration, you get a gnome2-like config, instantly
[19:24] <ry> based on what i saw with xubuntu 14.04 i figured i could eventually make it work but this is literally days of trying to fight with getting gnome-fallback working again, and i just needed a usable system to get some other stuff done
[19:24] <ry> wow
[19:25] <ry> should of come in here during this time
[19:25] <ry> lol
[19:25] <ry> i star'ed it, i'll test this out asap
[19:26] <ali1234> the idea is this would eventually be run on first install of xubuntu, and you can then pick a panel type
[19:26] <ali1234> but we need someone to write a gui for it
[19:26] <ry> does compiz work alright on xfce4 under ubuntu 14.04?
[19:26] <ali1234> meh... not really
[19:27] <ali1234> xfwm has ezoom now, so why even try to use compiz?
[19:27] <ry> i still have a rather limited understanding of how all the gui-related components come together honestly
[19:27] <ry> ezoom, the equal to full desktop zoom?
[19:27] <ali1234> yes
[19:27] <ry> =)
[19:28] <ry> thats one of the primary things i care about lol
[19:28]  * ry adds to list
[19:28] <ali1234> tat's the only thing most people really miss from compiz... the rest of it is just eye candy... nobody *needs* desktop cube
[19:28] <ali1234> zooming is important accessibility feature though
[19:29] <ry> oh yeah, i use the 2x2 expo/wall
[19:29] <ry> cube was cool for like 5 seconds back when i think it was part of "beryl" or something like that
[19:29] <ry> i'm sure in my old age wobbly windows would give me motion sickness or something
[19:29] <ry> x_x
[19:29] <ali1234> we don't have expo unfortunately
[19:29] <ry> maybe i'm calling it the wrong thing
[19:30] <ali1234> no, i know what you mean - we don't have it
[19:30] <ali1234> windows-e right?
[19:30] <ali1234> like zooming out and showing all workspaces
[19:30] <ry> yeah i guess all the features related to that are nice but not absolutely essential
[19:31] <ry> i rarely use it
[19:31] <ry> as long as i can move windows around between a 2x2 panel i'm good
[19:32] <ry> alt+clicking on a window to be able to grab it anywhere and move it is nice too (though i'm not sure if thats related to compiz)
[19:33] <ry> going back several years i knew i'd have to give up gnome 2.x at some point, and xfce has always been the alternative, i was surprised when gnome-fallback started becoming usable
[19:33] <ry> gnome-flashback (the one that is part of the gnome-shell rather than unity) was pretty much worthless from what i remember
[19:33] <ali1234> alt+drag is in all window managers that i know of, it'sa standard
[19:33] <ry> cool
[19:33] <ali1234> gnome flashback isn't so bad, if you know how to use t... you have to hold alt and right click the panel to get the old menus
[19:34] <ali1234> then it's just like old times
[19:34] <ali1234> doesn't work too well with compiz though
[19:34] <ry> i tried that on the new one when i was first trying to get ubuntu 14.04 setup
[19:35] <ry> it still works on unity's gnome-fallback, but the one that installs with gnome-shell had no such features
[19:35] <ali1234> yeah, there's two different fallback options now
[19:35] <ali1234> flashback, which is gnome-panel, and fallback, which is gnome shell made up to look a bit like gnome-panel but with none of the features
[19:36] <ali1234> and all the drawbacks :(
[19:36] <ry> lol
[19:36] <ali1234> you can guess which one gnome officially supports
[19:36] <ry> the useless one i'm sure
[19:40] <YokoZar> Is it intended that the drums now sound when the screen locks due to inactivity?
[19:41] <ali1234> i would guess not, and it's a side effect of using the same code for the lock screen and the login screen
[19:41] <ali1234> but i don't really know
[19:44] <ali1234> ie that sounds very much like a side-effect of https://bugs.launchpad.net/ayatana-design/+bug/878836
[19:57] <robert_ancell> desrt, have you started any gtk-mir code? I started work on a branch yesterday
[20:00] <YokoZar> ali1234: I agree, filed https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1320999
[21:27] <desrt> robert_ancell: was double-long weekend here, but i managed to get mir going in jhbuild
[21:27] <desrt> robert_ancell: did you push your branch to gnome.org yet?
[21:27] <robert_ancell> desrt, no
[21:27] <robert_ancell> desrt, where is your branch?
[21:28] <desrt> nowhere yet
[21:29] <robert_ancell> desrt, whats the convention on pushing gnome branches? wip/mir?
[21:30] <desrt> ya.  that's fine.
[21:31] <desrt> i think i'm gonna need to do some gtkapplication plumbing
[21:31] <desrt> i'm on holiday today and in transit to malta tomorrow, but maybe i can do some plane hacking
[21:32] <robert_ancell> desrt, can you push your branch there?
[21:32] <desrt> on the plane?
[21:32] <robert_ancell> to gnome git
[21:32] <desrt> of what?
[21:33] <robert_ancell> desrt, oh, you got mir to build using jhbuild.
[21:33] <robert_ancell> So no GTK+ Mir branch right?
[21:34] <desrt> the jhbuild moduleset is not in a 'done' state... the tarball from launchpad needs a fair bit of fixing before its usable
[21:35] <desrt> and i can't reupload my fixed tarball.... i'm on extremely spotty train internet
[21:35] <robert_ancell> desrt, so what did you get done?
[21:36] <robert_ancell> desrt, I'm starting the Mir module from scratch, so it might be best to use that and merge in changes from the bzr branch / tarballs
[21:36] <desrt> hacked up the tarball, figured out which cmake options i need, worked around a lib vs. lib64 issue
[21:36] <desrt> a lot of the fedora packages aren't quite up to snuff with what we have on ubuntu (and expect from mir)
[21:37] <desrt> some missing features in our google libraries (particularly gflags) and uninstalled bits of the mocking framework for cmake integration
[21:38] <desrt> (which apparently is a no-no anyway from what i found search around the net -- depending on system versions of this thing is never how it was supposed to work)


[01:11] <Uhfgood> Is there a way to allow ubuntu to use ntfs drives?
[01:44] <wonko> OvenWerks: No more xruns, however jackd crashed again. :'(
[01:47] <wonko> 64/2 is definitely pushing it
[12:28] <wonko> OvenWerks: https://paste.ubuntu.com/p/prvDXXjCmv/
[12:28] <wonko> Sitting overnight, 128/2
[12:29] <wonko> We have made definite progress on the crashing issue though. Before there was a 100% chance it would have crashed by morning time and I would have to restart everything
[12:33] <wonko> The problem with this being an everything system (although its less everything that it was in the past) is it's hard to know exactly what else is going on. It's also hard to have control over everything else. A dedicated music computer might be something I'll have to consider at some point.
[14:53] <OvenWerks> wonko: that is likely to be system events in cron
[14:53] <wonko> That's what I was thinking
[14:53] <wonko> because it was really only at that one time
[14:53] <wonko> so something happened
[14:54] <OvenWerks> wonko: the log is clean except for those times
[14:54] <wonko> yep
[14:54] <wonko> nothing since then
[14:54] <wonko> So I think we can call 128/2 a success
[14:54] <wonko> 64/2 was instance xruns, so that's not likely to work
[14:56] <OvenWerks> 64/3?
[14:56] <wonko> I can try that
[14:58] <wonko> one PulseIn but so far nothing else
[14:58] <wonko> 64/2 was a bunch of constant ones so that's looking good
[15:08] <wonko> oh, a couple right there
[15:11] <OvenWerks> wonko: so set it to 64/3 if you wish to try more tuning of your system or run 128/2 for live (synth) kinds of things and for recording, 1024 may be just fine.
[15:12] <wonko> I'm going to leave it at 64/3 for a while and see how it does
[15:12] <wonko> and two more xruns as soon as I said that. :)
[15:13] <wonko> 128/2 may be the best I'm going to reasonably get
[15:13] <wonko> for solid xrun-less operation
[15:13] <OvenWerks> 128/2 has been quite usable for me
[15:14] <wonko> if my math is correct we're talking 4ms vs 5.3ms which is probably not going to be noticable
[15:14] <wonko> yeah, bunch more, so 128/2 it is
[15:15] <OvenWerks> I found guitar effects use to be the most picky for me... I have actually found 1024 is ok for playing a synth... but I am not a piano player :)
[15:16] <wonko> I'm supposed to be learning the guitar. Need to make time for that. :)
[15:16] <wonko> I really need to pick the piano back up though too
[15:16] <wonko> I've been not doing music for far too long
[15:17] <wonko> ok, next issue is I need to figure out this Calf Analyzer issue
[15:17] <OvenWerks> piano and keyboards are not the same.
[15:17] <OvenWerks> beware too many calf plugins in Ardour
[15:17] <wonko> in this case the term is interchangable because I haven't touched either in forever. :)
[15:17] <wonko> I'm doing the plugins in Carla
[15:17] <wonko> thought I'd give that a go
[15:18] <wonko> but I might switch back to running them in ardour
[15:18] <wonko> the issue is if I click on the GUI button in the rack for Anazlyser it crashes carla
[15:18] <wonko> none of the other calf stuff does that, they all work as intended
[15:19] <OvenWerks> in my case I haven't either, but I am not willing to even try to play piano in frront of people... keyboard pads and stuff I am ok with
[15:21] <wonko> I'm not willing to play anything in front of anyone at this point
[15:21] <wonko> I haven't touched an instrument in probably 20 years
[15:21] <OvenWerks> Ouch
[15:22] <wonko> yeah
[15:22] <wonko> I need to fix that
[15:22] <wonko> getting this computer setup is supposed to be the motivation for that. :)
[15:23] <wonko> Did you see my UE4 build temp results?
[15:23] <OvenWerks> I find leaving a guitar beside my desk helps... even a solid body not plugged in.
[15:24] <wonko> Yeah, the other part was (we just moved) getting this office setup properly
[15:24] <wonko> so now the computer/desk/etc part is mostly done (once I get the mic stand)
[15:24] <wonko> I just need to fix the one outlet that isn't working so I can put the printer where it belongs
[15:25] <wonko> and then find a reasonable place to put the guitar and shitty keyboard we have
[15:25] <wonko> The tiny midi keyboard sits on my desk for fiddling with
[15:45] <wonko> boo, jack crashed
[15:45] <wonko> so that's not gone
[15:45] <wonko> I *did* move it back to the longer cable because the short one was too short. I'll try the middle length one and see how that is
[16:29] <Uhfgood> https://www.youtube.com/watch?v=ItlldOmHhFE - The end of UFD Tech
[17:19] <Eickmeyer> Uhfgood: Please stay on-topic in here. That video link has nothing to do with Ubuntu Studio. Also, this is a support channel, that was completely off-topic.
[17:31] <wonko> OvenWerks: yeah, looks like 128/2 is the sweet spot on this system so looks like I'll stick with that. :)
[18:28] <Alton> HI!


[08:06] <elfy> good morning channel - can anyone tell me when the iso tracker will get updated so I can let people know the url for beta final ? thanks
[08:07] <infinity> elfy: Sometime tomorrow (well, tomorrow for me)...
[08:08] <elfy> I hope you're west of me then :p
[08:09] <infinity> elfy: Western Canadia.  I suppose it's technically "later today", but it's all tomorrow until I've slept. :P
[08:09] <elfy> infinity: indeed :)
[08:09] <elfy> thanks
[08:40] <doko> Mirv, is it intended that that "CI Train PPA Service Team" PPA's build on powerpc?
[08:41] <Mirv> doko: unless something has changed, yes. didrocks ^
[08:41] <Mirv> so that there is no builds needed after copying to archives
[08:41] <didrocks> doko: it does, right
[08:41] <doko> hmm, ok
[10:40] <doko> pitti, jibel: please overwrite the ubuntuone-client autopkg test, blocks the zope.interface migration
[10:40] <pitti> doko: I can't, that needs to be done by ~ubuntu-release
[10:41] <pitti> Laney: ^ mind adding a nudge?
[10:54] <doko> pitti: is there a tag for failing autopkg tests?
[10:55] <pitti> doko: there's some ~u-r bzr branch which has these hints
[10:55] <doko> pitti: no just wanted to add a tag for a bug report I just filed
[10:56] <pitti> doko: ah; I'm using<EMAIL_ADDRESS>for Debian
[10:56] <pitti> doko: for ubuntu, "qa-daily-testing" and "autopkgtest" will do
[10:59] <Laney> pitti: ok, can you file a bug about it?
[10:59] <pitti> Laney: ack
[11:01] <doko> Laney, pitti: lp: #1296656
[11:01] <ubot2> Launchpad bug 1296656 in ubuntuone-client (Ubuntu Trusty) "ubuntuone-client autopkg tests fail in trusty" [High,Confirmed] https://launchpad.net/bugs/1296656
[11:01] <Laney> nice, ty
[11:01] <pitti> ah, thanks; /me cancels the report he is filng
[11:03] <doko> and now reference this issue in update_excuses.html ...
[11:22] <doko> pitti, cjwatson: are update-excuses currently not updated?
[11:22] <pitti> indeed, apparently it's stuck
[11:24] <cjwatson> It's just very very very slow
[11:24] <cjwatson> The x264 update is blowing its mind
[11:27] <cjwatson> I could kill it, but I think it might be better to let it carry on and get the output
[11:32] <cjwatson> Since most of what the last run complained about seems to be fixed
[11:33] <pitti> cjwatson: ah, thanks for the heads-up
[11:34] <cjwatson> And then fix things as fast as we can so that we get past this transition
[11:46] <apw> cjwatson, by my "eye" measurement she is on the last couple of AYEEIs
[11:47] <cjwatson> I'll take your word for it :)
[11:48] <cjwatson> There've been more this time than last, though, so hard to say
[11:49] <apw> well she finished them for x264 sadly she now is unhappy about vlc
[12:42] <cjwatson> Good grief, it's still going
[12:49] <doko> all the "binNMUs" for x264 did succeed, at least all the ones I uploaded
[12:50] <cjwatson> Ah, it's into the copies now
[12:50] <cjwatson> Still lots of uninstallables here, let's see what excuses looks like when it finishes
[12:50] <Riddell> beta freeze happening today?
[12:51] <Riddell> infinity: ↑
[12:51] <elfy> Riddell: sometime later today he said earlier to me
[12:51] <Riddell> okay dokay
[12:59] <cjwatson> Ah, libav was waiting for autopkgtests
[12:59] <cjwatson> Hm, still is, wrongly
[13:00] <cjwatson> I'm going to kill this run and go through all the issues
[13:09] <cjwatson> At least libav is a valid candidate now, so that should help
[13:49] <cjwatson> phew, that managed to migrate x264
[13:50] <cjwatson> I've stopped p-m for a while so that it doesn't do anything else until the next publisher run has happened, otherwise the next run will take ages (probably much longer than the publisher)
[14:04] <doko> why did it take that much time to calculate the x264 update? these just about 10-15 binNMU's ...
[14:14] <cjwatson> doko: lots and lots of uninstallables when not everything was migrated together
[14:14] <cjwatson> that sort of thing hits pathological cases
[14:15] <cjwatson> I don't know the internals of britney well enough to be able to do much about it
[14:15] <cjwatson> there's some deep magic there
[15:02] <cjwatson> p-m should be back to normal now
[15:04] <jamespage> release team question: how does feature freeze cover seed changes? if I want to add something to the server-ship seed do I need a release team ack?
[15:40] <doko> Laney, stgraber, please overwrite the pytables autopkg test, blocking python3-defaults. filed lp: #1296798
[15:40] <ubot2> Launchpad bug 1296798 in pytables (Ubuntu Trusty) "pytables autopkg tests failing (never did succeed in trusty)" [High,Confirmed] https://launchpad.net/bugs/1296798
[16:37] <jibel> doko, done
[16:37] <Laney> oh sorry, I saw this and then forgot
[16:43] <infinity> Hrm, is the mysql-5.5 autopkgtest really still running, or is britney confused?
[16:44] <infinity> jibel / pitti: ^
[16:44] <Laney> Jenkins thinks it's still running, AFAICS
[16:44] <pitti> infinity: it's still running
[16:44] <Laney> It shows that if you click "private"
[16:44] <infinity> Kay.  Long test.
[16:44] <jibel> last time I checked it was still running
[16:44] <infinity> Laney: Yeah, I never bothered to get the right bits set up to see the private instance.
[16:44] <pitti> 7:30 hours ago *sigh*
[16:44] <infinity> Mostly as a protest vote against HAVING private infra that impacts community process.
[16:44] <pitti> it looks like it's  hanging
[16:44] <infinity> Also, lazy.
[16:45] <jibel> infinity, still running, Ill kill it
[16:45] <pitti> and also it seems it disabled autopkgtests's timeout
[16:45] <infinity> pitti: Hung on both amd64 and i386, or just one?
[16:45] <pitti> infinity: aside from that, the flood got drained surprisingly well (with a few retries)
[16:45] <Laney> Yah. It's the only way to retry tests though, so I keep it set up.
[16:45] <pitti> infinity: on both
[16:46] <pitti> and it hung on the same test apparently on both arches
[16:46] <infinity> pitti: Kay.  Can't really be a product of my glibc upload, then, so I'll just XFAIL it in britney.
[16:47]  * pitti doesn't follow that conclusion, but we'll just retry it and see if it looks any different then
[16:47] <pitti> back then the machines were still clogged
[16:47] <infinity> pitti: My upload didn't change anything for the amd64 build.  I'd be suspicious if it was hanging only on i386.
[16:47] <pitti> ah
[20:02] <stgraber> queuebot was moved to another box and from precise to trusty so let me know if it's acting up in any usual way
[20:03] <stgraber> (I had to fight with the LP credentials quite a bit, not entirely sure those actually work, we'll see when the next package hits the queue)
[20:07] <jdstrand> unless someone is looking at oxide-qt right now, I will do it
[21:03] <utlemming> stgraber: it looks like the SRU for walinuxagent went into the wrong proposed pocket...any chance you could move it?
[21:03] <utlemming> stgraber: it got dropped to precise-proposed/univerise instead of precise-proposed
[21:04] <utlemming> stgraber: and it didn't get built
[23:54] <jtaylor> hi, can pytables be forced into trusty? the adt tests never succeeded and seem to be specific to the adt environment, the tests work fine on my machine


[05:39] <micahg> rekonq is the default browser in maverick+, right?
[05:47] <ScottK> micahg: Yes.
[05:47] <micahg> :(
[05:47] <ScottK> Why?
[05:47] <micahg> well, just tested my qt4-x11 update on maverick and rekonq crashed
[05:47] <ScottK> Oh.
[05:47] <ScottK> It may have done that before.
[05:48] <ScottK> First set of Kubuntu candidate images up for Beta 2 testing http://cdimage.ubuntu.com/kubuntu/daily/20110920.6/
[05:48]  * micahg wonders how a default browser could be released with a segfault
[05:48] <ScottK> shadeslayer was busy with exams, IIRC.
[05:48] <ScottK> Actually, IDK, as I almost never use it.
[05:48]  * micahg downgrades to release version to see
[06:00] <micahg> dang, it does segfault with the release version :(
[06:00]  * micahg switches to konqueror
[06:06] <valorie> ScottK: I brought my netbook which was running beta, up to date last night
[06:07] <valorie> if I run another set up updates, is that the equiv. of the Beta 2/rc ?
[06:17] <ScottK> Yes
[06:20] <valorie> cool
[06:51] <bulldog98_> apachelogger: how to compile uds-qml for symbian on my mashine?
[08:04] <bambee> morning
[10:12] <apachelogger> bulldog98: qt creator
[10:12] <apachelogger> also you'll need to remote compile via nokia, as I do not think there is a symbian toolchain on linux
[10:13] <bulldog98> apachelogger: yes that’s what I found out until now, but how can I get an account to use that?
[10:13] <apachelogger> register at developer.nokia.com
[10:14] <bulldog98> apachelogger: where is the button to do so, or am I blind?
[10:15] <apachelogger> bulldog98: https://www.developer.nokia.com/Profile/Join.xhtml?locale=en
[10:15] <bulldog98> apachelogger: thx
[10:17] <venu> hi everyone.i want to create a new option in my kubuntu right-click menu.How shld i write a .desktop file to do this?
[10:19] <bulldog98> venu: this is the developer channel please ask questions for support in #kubuntu
[10:19] <venu> bulldog98: thanx
[10:25] <apachelogger> actually that belongs even less in there than in here :P
[10:26] <apachelogger> bulldog98: what I always find surprising is how much rekonq can crash with such a tiny code base
[10:28] <yofel> well, if you add qtwebkit to that you can enough crash potential ^^
[10:28] <yofel> *can get
[10:31] <apachelogger> ScottK: can you please accept https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-kubuntu-coding https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-kubuntu-postponeds https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-kubuntu-mobile
[10:34] <apachelogger> yofel: except most crashes I get are not in qtwebkit but rekonq
[10:35] <yofel> ah, mine are usually in qtwebkit
[10:35] <yofel> so I hope it becomes actually usable with the rc
[10:35] <apachelogger> oh
[10:35] <apachelogger> on oneiric?
[10:35] <apachelogger> maybe we should push a new rekonq in? :P
[10:35] <yofel> that too ^^
[10:36] <apachelogger> bulldog98: how are settings usually presented on symbian^3?
[10:38] <bulldog98> apachelogger: nokia apps use a popup list
[10:38] <apachelogger> video would be good
[10:39] <apachelogger> interestingly enough the harmattan components are not half bad compared to the symbian ones
[10:39] <apachelogger> on harmattan you can at least get a settings dialog that looks like the others ^^
[10:40] <bulldog98> apachelogger: but even the nokia one are not consitent, so simply do one
[10:41] <apachelogger> bulldog98: well, whatever seems most useful I want
[10:41] <apachelogger> that said... the symbian UX guidelines suggest a wizard like dialog
[10:41] <bulldog98> e.g. Store uses a tab for that, player uses a popup, …
[10:41] <apachelogger> except there is no such thing in the qt components
[10:41] <apachelogger> + it would be jolly ard to build such a wizard without cpp
[10:41] <apachelogger> utter fail
[10:42] <apachelogger> it is like statusbar notifications on harmattan .. you simply cannot trigger them
[10:42] <apachelogger> although for harmattan that is a design flaw from meego
[10:52] <Quintasan_> fml
[10:52] <Quintasan_> I'm ill :/
[10:59] <apachelogger> Quintasan: soft kitty warm kitty littel ball of fur sleepy kitty happy kitty purr purr purr
[11:00] <apachelogger> who wants to do the uds app for android?
[11:01] <nigelb> I thought there already was one.
[11:01] <apachelogger> as with so many things apacheloggerware is superior
[11:01] <nigelb> summit exposes a read-only API now, if it helps anyone who wants to build an app.
[11:01] <apachelogger> also it is written in qt
[11:01] <apachelogger> using throw away UIs
[11:01] <apachelogger> \o/
[11:01] <apachelogger> writing a ui takes like an hour or so
[11:01] <apachelogger> nigelb: oh oh oh
[11:01] <apachelogger> nigelb: tell me more pretty please
[11:01] <nigelb> apachelogger: sec, let me find docs :-)
[11:02] <nigelb> apachelogger: https://code.launchpad.net/~mhall119/summit/rest-api/+merge/75859
[11:02] <nigelb> If you want pretty docs, poke me ~4 hours and I'll sit down and write it :)
[11:05] <apachelogger> haha
[11:05] <apachelogger> shadeslayer: all the work for nothing :P
[11:06] <apachelogger> nigelb: if you had mentioned this last week ... shadeslayer wrote an ical parser :S
[11:14] <nigelb> apachelogger: haha
[11:14] <nigelb> apachelogger: Talk to us!
[11:14] <nigelb> Let us just help you folks :-)
[11:15] <apachelogger> lol
[11:15] <apachelogger> well
[11:15] <apachelogger> I do not think a full switch to the API is much to go for at this point
[11:15]  * apachelogger does not care to implement persistent storage using sql
[11:16] <apachelogger> every time someone writes a line of sql a kitten dies somewhere on planet earth :(
[11:19] <apachelogger> nigelb: something about the api feels fishy TBH
[11:19] <nigelb> apachelogger: what feels fishy?
[11:19] <apachelogger> not sure
[11:19] <nigelb> Its a thin wrapper
[11:19] <apachelogger> perhaps the fact that oen has to use query params
[11:20] <apachelogger> http://summit.ubuntu.com/api/room/?summit=6
[11:20] <nigelb> Yeah, its not a "solid" API
[11:20] <apachelogger> http://summit.ubuntu.com/api/summit/6/room would seem much intuitive
[11:20] <nigelb> Sure, slowly :-)
[11:21] <apachelogger> why? it does exactly the same internally
[11:21] <nigelb> Ther's going to be a summit session at UDS
[11:21] <nigelb> Go there and tell what you want
[11:21] <apachelogger> on http://summit.ubuntu.com/api/summit/6/room you'd then apply your query
[11:21] <nigelb> I'll try to be there remotely as well
[11:22] <apachelogger> so you drilled down from a list of summits to one specific summit's room and then only want rooms that host tracks of "foo"
[11:22] <apachelogger> nigelb: not coming to orlando? :(
[11:22] <nigelb> apachelogger: Nope :(
[11:22] <nigelb> Mostly because it in the US and the visa is a hassle.
[11:23] <apachelogger> yeah, stupid visas
[11:23]  * apachelogger is fortunate enough to not require a proper visa
[11:24] <apachelogger> oh, my new headset is in austria
[11:25] <apachelogger> nigelb: something that I can request right now ... it would be super awesome if summit provided a map of the venue
[11:27] <apachelogger> nigelb: http://people.ubuntu.com/~apachelogger/screencasts/uds-qml3.mp4
[11:27] <nigelb> apachelogger: let me open a bug. I understand how that can be helpful.
[11:29] <nigelb> apachelogger: We already have a bug :-) bug 668540
[11:33]  * apachelogger thinks about doing a blunt on-disk json cache
[11:33] <apachelogger> I do not think there is much benefit from throwing stuff into a database really
[11:34] <apachelogger> with a simple json cache we can transparently serve urls from cache
[12:36] <ScottK> apachelogger: Done.
[13:03] <shadeslayer> aw
[13:03] <shadeslayer> boo
[13:06] <shadeslayer> apachelogger: i condem you to use our parser, thou shall not use summit API :P
[13:07] <apachelogger> ok
[13:07] <apachelogger> :P
[13:07] <apachelogger> ScottK: thx
[13:07] <apachelogger> http://i.imgur.com/b0Aij.png
[13:07] <shadeslayer> apachelogger: android app? is that in QML?
[13:08] <apachelogger> yep
[13:08] <apachelogger> now pushed
[13:08] <apachelogger> someone should write android components
[13:18] <apachelogger> shadeslayer: you should totally port to ipone
[13:18] <apachelogger> you can actually reuse the main.qml from android it uses plain qtquick 1.0
[13:18] <shadeslayer> iphone? What a rubbish platform
[13:19] <apachelogger> http://labs.qt.nokia.com/2011/08/09/update-on-uikit-lighthouse-platform/
[13:19] <shadeslayer> apachelogger: my sister has a iPad and i got bored after 2 hours
[13:19] <shadeslayer> there's *nothing* to do
[13:19] <apachelogger> except run your uds app on it ^^
[13:19] <shadeslayer> it was designed to do one job and one job only, make money by selling apps
[13:19] <shadeslayer> heh
[13:20] <apachelogger> anywho, I would reall appreciate if you could try to deploy it there
[13:20] <apachelogger> should be relatively easy as you can just put everything into the binary
[13:20] <apachelogger> also see qml/android.qrc
[13:20] <shadeslayer> sure, i can try, if i manage to figure out how to do it
[13:21] <apachelogger> shadeslayer: the qt labs post explains how to get a lighthose setup and all that stuff
[13:21] <shadeslayer> yep, will try over the weekend
[13:21] <apachelogger> splendid
[13:21] <shadeslayer> my profs have loaded me up for the week right now
[13:23]  * apachelogger waves fist
[13:24] <shadeslayer> fooey, will have to clone Qt, and download the SDK
[13:24] <shadeslayer> that is like a ton of download right there
[13:31] <shadeslayer> apachelogger: on iOS side, what needs doing?
[13:32] <shadeslayer> i haz a iOS developer friend, i could probably ask him for help to set everything up
[13:32] <apachelogger> shadeslayer: nothing
[13:32] <apachelogger> that is what the blog post suggests
[13:32] <shadeslayer> oh, just testing stuff?
[13:32] <apachelogger> yeah, proof of concept
[13:33] <apachelogger> unless you actually want to do the development
[13:33] <shadeslayer> alright, i'll try it over the weekend
[13:33] <shadeslayer> no thanks :P
[13:33] <apachelogger> which probably involves writing ios qt components
[13:33] <shadeslayer> heh
[13:33] <apachelogger> which is surely a PITA
[13:33] <apachelogger> though not as much as on android I'd say
[13:33] <shadeslayer> cloning Qt will be a PITA
[13:33] <shadeslayer> i'm pretty sure i'll time out a couple of times
[13:33] <apachelogger> :D
[13:34] <shadeslayer> i tried to clone qtwebkit once
[13:34] <shadeslayer> on a 256kbp connection
[13:34] <shadeslayer> not pretty
[13:34] <apachelogger> well
[13:34] <apachelogger> bulldog98 is on 56k or something
[13:34] <apachelogger> so stop whining :P
[13:35] <shadeslayer> i know the feeling
[13:35] <shadeslayer> i had 56k 5 years back :P
[13:35] <shadeslayer> still have the US Robotics modem with me
[13:35] <shadeslayer> iirc i video called someone in the US with Yahoo + 56k modem
[13:47] <skfin> hmm...
[13:47] <skfin> a video call + 56k modem is not a possible combination
[13:48] <shadeslayer> in 2003 it was
[13:48] <skfin> Hmm
[13:48] <skfin> So you did listen to a 8-bit voice and two pixels?
[13:49] <shadeslayer> well, i had a VGA webcam back then, :P
[13:49] <shadeslayer> so something like, 1 frame every 10 seconds
[13:49] <skfin> VGA is 640x480 so its just too much for 56k modem itself :)
[13:49] <shadeslayer> and i used to go, OMG THAT GUY IS MOVING AND I CAN SEE HIM
[14:03] <apachelogger> !find pcre.h
[14:08] <shadeslayer> finally
[14:09] <shadeslayer> portal download
[14:09] <shadeslayer> started :D
[14:17] <apachelogger> http://paste.kde.org/124579/
[14:17] <apachelogger> weeh
[14:18] <apachelogger> shadeslayer: I thought you had work to do? :P
[14:33] <shadeslayer> apachelogger: sure, i'm doing that, but portal is downloading as well
[14:33]  * shadeslayer is studying about 8051 micro controller registers
[14:33] <apachelogger> gross
[14:35] <shadeslayer> gross for you, coursework for me
[14:57] <bulldog98> apachelogger: why can’t I use a paint(int, int, QPixmap) in an selfwritten QDeclarativeItem?
[15:00] <apachelogger> bulldog98: show me code
[15:00] <shadeslayer> apachelogger: what am i supposed to do in the workitem for neon?
[15:03] <apachelogger> I dunno
[15:03] <apachelogger> maybe it was Quintasan who added that
[15:03]  * apachelogger does not even know what it means
[15:04] <bulldog98> apachelogger: kde:scratch/kolberg/kardsloader
[15:04] <bulldog98> apachelogger: that’s the lib
[15:06] <bulldog98> apachelogger: kde:scratch/kolberg/doppelkopf-qml is a small test project
[15:06] <apachelogger> hm
[15:06] <apachelogger> should just work
[15:06] <apachelogger> as long as qpixmap is actually a valid one
[15:06] <bulldog98> apachelogger: problem is it says QPixmap: It is not safe to use pixmaps outside the GUI thread
[15:07] <bulldog98> but I consider QML a Gui thread
[15:07] <bulldog98> or an extend to that
[15:07]  * apachelogger points out that this assumption is not true for qtquick2
[15:08] <bulldog98> apachelogger: but how can I get the card out off that cache?
[15:12] <apachelogger> bulldog98: QPixmap: It is not safe to use pixmaps outside the GUI thread
[15:12] <apachelogger> that appears before paint is even called
[15:12] <bulldog98> I know that
[15:12] <bulldog98> I guess it’s somewhere in the cache
[15:13] <bulldog98> since I do not use QPixmap anywhere
[15:14] <bulldog98> it’s tiggerd in m_cache->loadTheme(…)
[15:15] <bulldog98> even if I move that into paint that error is thrown
[15:15] <fabo> debfx: bug 854330
[15:16] <apachelogger> bulldog98: that function is threaded
[15:16] <apachelogger> hence the warning
[15:16] <bulldog98> hm
[15:16] <bulldog98> it’s from the kdegames lib
[15:17] <bulldog98> maybe I should ask in #kdegames for help
[15:20] <bulldog98> still kpat and lskat should get the same error if they call that
[15:20] <bulldog98> but they get pixmaps and I don’t get pixmaps
[15:21] <Riddell> fabo: ah hah, that might explain why file search has stopped doing anything
[15:22] <bulldog98> apachelogger: now I managed to get rid of the QPixmap stuff
[15:23] <fabo> Riddell: :) it introduces also some new stream support using ffmpeg
[15:25] <apachelogger> bulldog98: how?
[15:25] <bulldog98> apachelogger: see the new commit
[15:25] <bulldog98> somehow it was due a missing ->set…Theme() call
[15:26] <bulldog98> but now I think my themename is wrong
[15:26] <apachelogger> I think you are using libkdegames wrong
[15:44] <Quintasan> apachelogger: Certainly it was not me
[15:45] <Quintasan> apachelogger: One of Polish users report brekage in packages
[15:45] <Quintasan> plasma-widget-metworkmanagement conflicts with network-manager-kde and network-manager-kde requires  plasma-widget-networkmanagement
[15:46] <bulldog98> apachelogger: maybe
[15:50] <bulldog98> apachelogger: but at least I managed to get the plugin build and installed with cmake :)
[15:51] <shadeslayer> btw
[15:51] <shadeslayer> apachelogger: Blueprint changed by Harald Sitter:
[15:51] <shadeslayer> - [kubuntu-members] Give Neon a public purpose: TODO
[15:51] <shadeslayer> + [shadeslayer] Give Neon a public purpose: TODO
[15:51] <apachelogger> someone was talking about that at UDS
[15:51] <apachelogger> or the item would not be there
[15:51] <shadeslayer> someone explain that to me
[15:51] <apachelogger> shadeslayer: listen to the uds discussion
[15:51] <shadeslayer> ah righto
[15:52] <apachelogger> or maybe the notes have more details
[15:52] <apachelogger> see wiki link or something on the blueprint
[15:52] <shadeslayer> will check
[15:52] <bulldog98> is already uds?
[15:52] <apachelogger> no
[15:52] <apachelogger> app is not finished :P
[15:52] <apachelogger> so it cannot be uds
[15:53] <apachelogger> bulldog98: did you deploy onto symbian yet?
[15:53] <shadeslayer> "This page does not exist. If you feel that this is an error, please file a bug"
[15:53] <bulldog98> apachelogger: no, I had my new account in spam folder
[15:53] <shadeslayer> awesome
[15:54] <bulldog98> shadeslayer: that’s good
[15:55] <shadeslayer> i'll have a look on the weeken
[15:55] <shadeslayer> s/weeken/weekend/
[15:55] <kubotu> shadeslayer meant: "i'll have a look on the weekend"
[15:56] <shadeslayer> hrm
[15:56] <shadeslayer> yofel: digikam still being worked upon?
[16:13] <apachelogger> bulldog98: lol
[16:14] <bulldog98> apachelogger: even better nokia warned that that could happen. I guess they setup their mail server wrong
[16:14] <apachelogger> *shrug*
[16:16] <bulldog98> fabo: is that fixed now?
[16:21] <bulldog98> apachelogger: what pass do I have to type in into the remote compiler setup?
[16:33] <apachelogger> bulldog98: the one from developer.nokia.com
[16:33] <allee> about nepomuk and strigi: in http://trueg.wordpress.com/2011/09/19/nepomuk-what-comes-next-revised/  in a comment   it's mentioned "..2. If it’s 0.7.2, FILE A BUG IN YOUR DISTRO..".    Oneiric and Project Neon still seem to use 0.7.2.
[16:43] <fabo> bulldog98: what's the context? :) "is that fixed now?"
[16:45] <fabo> allee: bug 854330
[16:45] <fabo> allee: oneiric need a sync request
[16:45] <shadeslayer> dcmtk won't make it into main
[16:45] <shadeslayer> was required for KOffice
[16:46] <shadeslayer> but since we won't be usnig KOffice anymore
[16:46] <shadeslayer> *using
[16:49] <allee> fabo: great!  Can you do a ppa build so 'we' can test it, like with bluedevil.  I assume as it's late in release cycle a simple sync request is not enough
[16:50] <allee> ScottK: ^^ libstrigi & co  ??
[16:53] <shadeslayer> omg
[16:53] <shadeslayer> apachelogger: http://googleplusplatform.blogspot.com/2011/09/introducing-google-hangouts-api.html
[17:00] <apachelogger> yay
[17:00] <apachelogger> more prn
[17:00] <ScottK> allee: Yes.  Please (testing)
[17:11] <apachelogger> Sput: ping
[17:11] <apachelogger> Sput: I said ping!!! :P
[17:17] <yofel> shadeslayer: not by me at least right now, someone still needs to fix the stuff debfx complained about
[17:21] <fabo> allee: uploaded to https://launchpad.net/~fboudra/+archive/kde
[17:22] <debfx> yofel, shadeslayer: I think putting the libraries into own packages and overriding their version might actually be the best option
[17:23] <yofel> I put them seperately to prevent file conflicts later, but I don't know how to override the versions (and have no time for at least the next 2 days to look it up)
[17:25] <bulldog98> fabo: exectly that bug 854330
[17:38] <bulldog98> has somebody an idea what https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/766145 is about?
[17:44] <debfx> bulldog98: looks like a duplicate of bug #798091
[17:45] <yofel> allee: thanks for mentioning it, I'll try to update it in neon (we can't built it from git since bzr-git doesn't support submodules)
[17:45] <bulldog98> debfx: should we fix that?
[17:45] <debfx> systemsettings reverts to kde default values ignoring kubuntu-default-settings
[17:45] <debfx> bulldog98: sure if you know how
[17:48] <bulldog98> debfx: I guess we need to patch the *.kcfgc files to include our defaults, but that would mean, that you can’t get default kde settings
[17:49] <bulldog98> in the kcms
[17:54] <debfx> bulldog98: the proper solution would be to teach the code to take config file cascading into account
[17:55] <bulldog98> debfx: that isn’t possible, cause the reset feature only uses the .kcfgc files, which is intended
[17:56] <bulldog98> it should only take .kcfgc files in account, since everything else is not default
[17:56] <debfx> bulldog98: so we need to change the reset feature
[17:57] <debfx> that's certainly not what users expect
[17:57] <bulldog98> debfx: should we teach it to also use our system config path?
[17:57] <bulldog98> debfx++
[18:02] <debfx> I guess it should take all config paths into account except the kde home dir
[18:05] <bulldog98> debfx: yes, we would need to do that upstream I guess
[18:23] <skfin> Hmm...either kcolorpicker hasnt been yet synced to finnish update mirror or it is strangely missing
[18:24] <skfin> apt-get returns 404
[18:24] <skfin> Well, doesnt actually return but the download process returns 404
[18:24] <apachelogger> I once had a 404
[18:24] <apachelogger> got it on ebay for 0.50 EUR
[18:24] <apachelogger> it broke after one week
[18:25] <skfin> Ok.
[18:25] <skfin> I can sell you this one
[18:26] <apachelogger> no, I don't want another one
[18:26] <apachelogger> I grew really close with my old one
[18:27] <apachelogger> https://launchpad.net/ubuntu/+source/kcolorchooser/4:4.7.1-0ubuntu2
[18:27] <apachelogger> skfin: mirror might be updating right now
[18:27] <skfin> Yea
[18:27] <apachelogger> it happens
[18:28] <apachelogger> hold on to your 404 while it lasts
[18:28] <skfin> But Trumpetti is my favourite server and my really close friend, I wont let it down for just one 404
[18:29] <skfin> And it's just 23km away and ping to there is 16ms
[18:30] <apachelogger> something tells me roundtrip with backbone server is kiling the speed there :P
[18:31] <skfin> Ah. Now it doesnt give me 404
[18:31] <apachelogger> :(
[18:31] <skfin> trumpetti.atm.tut.fi
[18:31] <apachelogger> another 404 scared away
[18:32] <skfin> Tampere University of Technologies :)
[18:32] <skfin> trumpetti <3
[18:32] <apachelogger> university, I have heared of this place, they have partees there
[18:34] <apachelogger> after all this rubbish talk I feel like champagne
[18:38] <yofel> bulldog98: anything blocking the soprano backport? or did you just not get to it yet?
[18:38] <bulldog98> yofel: shadeslayer said he was working on it
[18:41] <yofel> k
[19:07] <shadeslayer> something *was* blocking the soprano backport, but i don't remember what it was anymore
[19:08] <shadeslayer> some other package that needed backporting or sth
[19:08] <shadeslayer> and someone is trying to bruteforce their way in
[19:08] <shadeslayer> via ssh
[19:09] <yofel> lemme, guess, you have ssh listening on port 22 and 22 forwarded?
[19:10] <shadeslayer> ssh is running on 22 :P
[19:10] <shadeslayer> haven't put in a custom port yet
[19:11] <shadeslayer> i should probably do that
[19:15] <apachelogger> shadeslayer: pingpingping
[19:15] <apachelogger> shadeslayer: you coming to uds?
[19:15] <apachelogger> is Quintasan coming to uds?
[19:15]  * yofel isn't coming to UDS
[19:15]  * apachelogger waves fist
[19:15]  * bulldog98 neighter
[19:16] <apachelogger> y you people never come to the uds?
[19:16] <apachelogger> despite me writing cool apps
[19:16] <apachelogger> bulldog98: did you deploy on symbian yet?
[19:16] <shadeslayer> apachelogger: nope
[19:16] <bulldog98> apachelogger: nope, I don’t know which pass to tipe into the configuration of remote compiler
[19:16] <shadeslayer> apachelogger: i have my GRE exam during UDS
[19:18] <apachelogger> oh dear
[19:18] <apachelogger> bulldog98: your nokia developer account details
[19:18] <micahg> apachelogger: you coming to UDS?
[19:18]  * bulldog98 tries again last time I tried it didn’t work
[19:19] <apachelogger> micahg: yup
[19:19] <micahg> apachelogger: great!
[19:19] <apachelogger> \o/
[19:19] <apachelogger> bulldog98: http://i.imgur.com/8s56c.png
[19:20] <apachelogger> bulldog98: http://i.imgur.com/o5a42.png
[19:20] <bulldog98> apachelogger: me forgot to add the username to the lineedit :(
[19:20] <apachelogger> lol
[19:28] <bulldog98> apachelogger: how do I deploy to my device?
[19:28] <apachelogger> bulldog98: see documentation
[19:28] <apachelogger> help tab in qtcreator
[19:36] <bulldog98> apachelogger: http://paste.kde.org/125371/
[19:40] <Sput> apachelogger: wot.
[19:41] <maco> who from kubuntu will be at uds?
[19:41] <maco> obv i can safely assume scott & riddell
[19:42] <apachelogger> maco: no scott, busy with work he is
[19:42] <maco> mrow?
[19:42] <apachelogger> maco: jr, claydoh, DarkwingDuck and me from what I know thus far
[19:42] <maco> scott...ever...misses uds?
[19:42] <apachelogger> Quintasan if he can get a visa
[19:42] <apachelogger> maco: apparently so
[19:43] <maco> this has to be the first uds scott's missed in at least 3 years
[19:43] <apachelogger> incidentially enough I need to find a new drinking partner :(
[19:43] <apachelogger> maco: you coming? did you add yourself to the wiki yet? :P
[19:43] <maco> i dont know
[19:43] <claydoh> lol apachelogger I could take drinking up as a new hobby
[19:44] <claydoh> buy I am not good at it
[19:44] <apachelogger> bulldog98: and that is all? :O
[19:44] <apachelogger> Sput: nvm, markey seems to have fallen asleep
[19:44] <apachelogger> he wanted to do hangoutz
[19:44] <nigelb> g55
[19:44] <bulldog98> apachelogger: yes. I would say remote compiler has a bug
[19:44] <apachelogger> bulldog98: I'll try in a minute or two
[19:44] <maco> nigelb: having a fight with your irc client?
[19:45] <apachelogger> claydoh: about time then :P
[19:45] <nigelb> maco: nah
[19:52] <apachelogger> nigelb: btw, I wrote a simple app using the api earlier today
[19:52] <apachelogger> should be jolly easy to make the app use the api
[19:53] <apachelogger> qt quick is awesome like that
[19:53] <nigelb> apachelogger: \m/
[19:53] <nigelb> ROCK ON
[19:54] <Sput> apachelogger: as usual
[19:54] <Sput> awake?
[19:54] <ScottK> apachelogger is always awake.
[19:54] <ScottK> The question, is, is he sober enough to type.
[19:55] <apachelogger> Sput: :D :D :D :D
[19:55] <nigelb> ScottK: hahaha
[19:56] <apachelogger> ScottK: I think Sput was referring to a joke only elitist google hangouters understand :P
[19:56] <Sput> yes, I was indeed
[19:58] <BarkingFish> evening guys :)
[19:59] <BarkingFish> I'm pretty much back to full fitness and ready to get back on with some work.  Anyone got anything they need build testing, debugging or generally unborking?
[19:59] <apachelogger> bulldog98: oh, there is some weirdness with the remote compiler
[19:59] <bulldog98> BarkingFish: do you run oneiric?
[19:59] <bulldog98> apachelogger: yeah
[20:00] <apachelogger> Build Failed: Zipping failed: file to open is a directory (/home/me/src/git/uds/qml/core)
[20:00] <apachelogger> wtf
[20:00] <BarkingFish> bulldog98, no - natty, but I have pbuilder set up to work on both
[20:00] <bulldog98> BarkingFish: ok no problem
[20:00] <apachelogger> Sput: y ur company distributes broken software? :P
[20:01] <bulldog98> Sput: fix that :P
[20:01] <bulldog98> like now
[20:01] <BarkingFish> hi ScottK :)
[20:01] <apachelogger> really weird
[20:01] <yofel> shadeslayer: any ETA for soprano? If not I'll either do it myself or use the old one
[20:01] <ScottK> BarkingFish: Hello.
[20:02] <bulldog98> yofel: ETA?
[20:02] <Sput> apachelogger: what?
[20:02] <yofel> bulldog98: estimated time of arrival?
[20:02] <apachelogger> Sput: remote compiler in qtcreator is somewhat flimsy
[20:02] <bulldog98> yofel: k
[20:03] <Sput> apachelogger: not my realm :)
[20:03] <Sput> pester ossi!
[20:03]  * apachelogger is scared of ossi
[20:03]  * bulldog98 too
[20:03] <apachelogger> bulldog98: actually it works with a clean project, so there is something in the pro file that makes it fall over
[20:03] <apachelogger> I wonder what though
[20:03] <apachelogger> very weird
[20:03] <apachelogger> maybe it inspects the qml files, though that'd be weird
[20:04] <bulldog98> apachelogger: maybe you could get ossi interessted enought to fix that
[20:04] <bulldog98> apachelogger: the default project, does it have subfolder in the qml folder?
[20:04] <apachelogger> yes
[20:04] <apachelogger> but only one
[20:05] <apachelogger> what I do not understand... why does qt creator not simply zip up the entire tree and ship it off
[20:05] <apachelogger> very curious
[20:05] <apachelogger> bambee: ping
[20:05] <bulldog98> apachelogger: do you know who wrote that peace of software?
[20:06] <apachelogger> the berlin qt team
[20:06] <apachelogger> I guess, as they make all of qtcreator
[20:06] <apachelogger> oh
[20:06] <apachelogger> actually Mowhi
[20:07] <bulldog98> apachelogger: how did you find that out?
[20:07] <apachelogger> secret
[20:08] <apachelogger> well then
[20:09] <apachelogger> I do not think it has to do withthe sub dirs
[20:09] <apachelogger> I created a sub dir in a blank project and it did not trip over it
[20:10] <apachelogger> whoop whoop
[20:10] <shadeslayer> yofel: nope, i won't be able to look at it before tomorrow
[20:10] <bulldog98> apachelogger: I found it out too
[20:10] <apachelogger> something is broken with the pro file
[20:10] <apachelogger> which is actually surprising
[20:10] <apachelogger> eh
[20:10] <apachelogger> not
[20:10] <yofel> shadeslayer: k, I'll wait then, won't have much time tomorrow anyway
[20:11] <shadeslayer> sure
[20:11] <apachelogger> eh
[20:12] <apachelogger> bulldog98: it falls over my excessive if else stuff
[20:12] <apachelogger> very weird
[20:12] <apachelogger> also it fails to build for no apparent reason
[20:12] <shadeslayer> soprano will probably take some time as well because it doesn't have alot of the build deps satisfied iirc
[20:13] <yofel> there's redland etc. already in backports if you need it
[20:13] <yofel> just copy it over
[20:15] <shadeslayer> again, don't remember, will look tomorrow
[20:15] <apachelogger> http://paste.kde.org/125431/
[20:15] <apachelogger> completely weird
[20:15] <shadeslayer> i'm off to sleep now
[20:15] <shadeslayer> night
[20:15] <yofel> night
[20:20] <bulldog98> apachelogger: that paste is wired
[20:21] <apachelogger> I know
[20:21] <apachelogger> however... might have to do with linking
[20:21] <apachelogger> as it builds fine, but then apparently no sis comes out of it
[20:21] <bulldog98> apachelogger: maybe someone in #qtcreator knows why that fails
[20:22] <bulldog98> s/qtcreator/qt/
[20:22] <kubotu> bulldog98 meant: "apachelogger: maybe someone in #qt knows why that fails"
[20:23] <apachelogger> unlikely unless they wanna read all the code :P
[20:26] <bulldog98> apachelogger: force ossi to do so and be the might with you :P
[20:26] <apachelogger> hm
[20:26] <apachelogger> it might have to do with how we fake include libqcalparser into our source tree
[20:26] <apachelogger> oh yes
[20:26] <apachelogger> bingo
[20:27] <bulldog98> apachelogger: fixed it?
[20:27] <apachelogger> bulldog98: http://people.ubuntu.com/~apachelogger/tmp/uds_unsigned_qt-4_7_3_symbian3.sis
[20:27] <apachelogger> try that
[20:28] <apachelogger> well, since there is an api to be used in the future, I do not really have to worry much about qcalparser integration I suppose
[20:29] <bulldog98> apachelogger: problem is with only the sis deployment is not working
[20:29] <apachelogger> bulldog98: why?
[20:29] <apachelogger> you just need to install the sis on your file
[20:29] <bulldog98> apachelogger: ?
[20:30] <apachelogger> the sis is a symbian binary package
[20:30] <apachelogger> you should just be able to install it
[20:30] <bulldog98> apachelogger: including all libs and stuff?
[20:30] <apachelogger> there are no requirements
[20:30] <apachelogger> that sis contains everything you need
[20:30] <apachelogger> (except for Qt which is part of symbian^3 anyway)
[20:35] <apachelogger> oh noes, I thik I broke the builder ^^
[20:35] <bulldog98> apachelogger: I got a cert error
[20:36] <apachelogger> you probably have to allow installation of self-signed sis somehwere?
[20:37] <bulldog98> ~search symbian^3 allow installation of self-signed sis
[20:37] <kubotu> Results for symbian^3 allow installation of self-signed sis: 1. How to sign a .Sis file with Self-Sign Certificate - Nokia Developer Wiki: http://www.developer.nokia.com/Community/Wiki/How_to_sign_a_.Sis_file_with_Self-Sign_Certificate | 2. Qt Creator : Deploying Applications to Symbian Devices: http://doc.qt.nokia.com/qtcreator-2.3/creator-deployment-symbian.html
[20:37] <kubotu> 3. Qt 4.7: Installing Qt for the Symbian platform: http://doc.qt.nokia.com/stable/install-symbian.html
[20:38] <BarkingFish> apachelogger - is that S60 5th ed?
[20:38] <apachelogger> no
[20:38] <apachelogger> ^3
[20:39] <apachelogger> though we could get it on 5th edition too I think
[20:39]  * apachelogger looks
[20:39] <BarkingFish> I used to work on basic stuff for my old S60 3rd ed Nokia E71
[20:39] <apachelogger> hmmm
[20:39] <BarkingFish> 5th can't be much harder, I don't know what ^3 is like.
[20:40] <apachelogger> actually S60 5th would be tricky
[20:40] <apachelogger> it only has qt quick 1.0
[20:40] <apachelogger> and no components
[20:40] <BarkingFish> myxzptlk...
[20:40] <apachelogger> so we'd have to import those or something
[20:40] <apachelogger> whoever wants to do that
[20:40]  * apachelogger needs to get a symbian device
[20:40] <allee> ScottK, fabo: I've installed fabo's ppa strigi 0.7.6 libs: added new user.  Start indexing of ~ 750 mostly audio files.  Cpu and io usage was very log  (top and iotop)  indexed 1-2 file per sec). IMHO way to much cyptic debug output to .xsession-error.   So no obvious problem with the new libs.
[20:41] <apachelogger> when is the 701 hitting the shelfs?
[20:41] <BarkingFish> apachelogger, Nokia E72 is good, I upgraded to one of those.
[20:42] <apachelogger> hm, 701 in Q3 :S
[20:43] <ScottK> rbelem: Did you get your omap thing working for testing Kubuntu stuff?
[20:44] <allee> ibus fix: please choose:  a)  echo "mkdir -p $HOME/.config/ibus/bus" >> /usr/bin/startkde   b) mkdir -p /etc/skel/.config/ibus/bus      One inotify_add_watch per application start is really too much :(
[20:44] <rbelem> ScottK, lately not, but some weeks ago when i got the hole kubuntu-mobile stak running
[20:44] <rbelem> stack
[20:45] <ScottK> Can you check if you can test images for beta 2?
[20:46] <apachelogger> bulldog98: I think I'll get myself a symbian dev setup in windows and try to fix it up locally ... still if you could try the sis that would be cool
[20:46] <apachelogger> BarkingFish: I was more thinking in the direction of either N8 or 701
[20:46]  * apachelogger likes fastish devices for development so he can write crappy code ^^
[20:47] <rbelem> ScottK, oki
[20:47] <rbelem> :-)
[20:47] <ScottK> Thanks.  Let me know.
[20:48] <ScottK> BarkingFish: New plee-the-bear is in Debian.  You might see if you can build it in oneiric and request a sync if it does.
[20:48]  * ScottK is going out for the evening.
[20:57] <bulldog98> apachelogger: what have you done, to get it working, could you commit that to a branch, so I can build it myself?
[20:57] <apachelogger> nope
[20:57] <apachelogger> too messy
[20:57] <apachelogger> well
[20:58] <bulldog98> apachelogger: then send me a diff
[21:00] <apachelogger> bulldog98: checkout symbian branch
[21:00] <apachelogger> not sure if I replicated the changes properly
[21:00] <apachelogger> but I think it should be about the same
[21:04] <apachelogger> uh, my new headset is in upper austria
[21:04]  * apachelogger hopes for delivery tomorrow
[21:07] <bulldog98> apachelogger: it’s installing
[21:07] <apachelogger> yay
[21:08] <bambee> apachelogger: pong
[21:08] <apachelogger> bambee: touchegg 1.0?
[21:09] <bambee> I still wait review for touchegg-gui ^^
[21:09] <bulldog98> apachelogger: does it need network for building up the start ui?
[21:10] <apachelogger> bambee: screw that, get 1.0 packaged and on revu, get an exception and I'll upload
[21:10] <apachelogger> bambee: FWIW 0.3 apparenlty does not work with latest utouch, so we need that fixed
[21:10] <bambee> ok
[21:12] <bulldog98> apachelogger: uds only shows me a blank screen
[21:12] <apachelogger> it is broken!
[21:12] <apachelogger> god knows why
[21:13] <apachelogger> bulldog98: you might need to install the symbian qt components
[21:13] <apachelogger> however one does that
[21:13] <bulldog98> apachelogger: installed
[21:14] <apachelogger> and it does not work? :O
[21:14] <apachelogger> any chance of getting debug output somehow?
[21:15] <bulldog98> apachelogger: let me test
[21:15] <apachelogger> if you add CONFIG += debug in the pro file and deploy via qtcreator you should get debug output in creator
[21:15] <apachelogger> or at least on every other target it works like that
[21:16] <apachelogger> possible one cannot build with debug on remote compiler though *shrug*
[21:18] <bulldog98> apachelogger: only problem I have is that deployment does not work
[21:18] <apachelogger> why?
[21:18] <apachelogger> that does not make sense
[21:18] <apachelogger> see qt creator documentation :P
[21:22] <bulldog98> apachelogger: yep I miss the coda stuff on my N8
[21:24] <bulldog98> apachelogger: I even get an error with the simulater: http://paste.kde.org/125479/
[21:24] <apachelogger> with the simulator that is to be expected
[21:24] <apachelogger> it is a bit of a fishy thing
[21:25] <apachelogger> bulldog98: http://paste.kde.org/125485/
[21:37] <bulldog98> apachelogger: http://pastebin.com/NPmVBPTr
[21:37] <bulldog98> is that normal with the simulator?
[21:37] <apachelogger> screw the stupid simulator
[21:38] <apachelogger> and yes
[21:38] <apachelogger> that is what hte output should look like
[22:38] <JontheEchidna> apachelogger: yo
[22:38] <apachelogger> dont yo me, you lost
[22:38] <apachelogger> I think
[22:38] <apachelogger> also I am drunk
[22:39] <JontheEchidna> lol


[01:30] <qwebirc56482> I am having a problem installing my hauppauge TV tuners on Mythbuntu.  I followed the instructions at http://robotbeard.com but I ran into some errors on one of the steps that is supposed to compile I think.
[01:31] <qwebirc56482> The error is:  implicit declaration of function 'kzalloc' [-Werror=implicit-funciton-delcaration]
[01:34] <Shadow__X> qwebirc56482: which tuner
[01:34] <qwebirc56482> hauppauge 2250
[01:35] <qwebirc56482> ok, I just found out that I can skip that step.  I missed a line when reading.  But when continuing on the cards are not showing up.
[01:38] <Shadow__X> ok first which version of mythtbuntu are you using
[01:41] <Shadow__X> qwebirc56482: which version of mythbuntu are you using
[01:42] <Shadow__X> qwebirc56482: type lsb_release -a in terminal
[01:43] <qwebirc56482> 12.04
[01:43] <qwebirc56482> I just downloaded and installed today
[01:45] <Shadow__X> ok so what steps did you follow
[01:46] <qwebirc56482> for the install or the robot beard thing?
[01:46] <qwebirc56482> I followed steps 1-3b on the robot beard and Front and backend install on the mythbuntu
[01:47] <qwebirc56482> I rebooted and attempted step 4 on the robotbeard but the card didn't show up.
[01:47] <Shadow__X> when you install mythbuntu a frontend and backend are already installed
[01:47] <qwebirc56482> I followed the wizard and that was pretty much all it asked me other than a remote.
[01:48] <qwebirc56482> and username stuf
[01:48] <Shadow__X> ok well since you are using 12.04 the install is very easy
[01:49] <Shadow__X> http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2200#Making_it_Work_Easily
[01:49] <Zinn> [linuxtv.org] Hauppauge WinTV-HVR-2200 - LinuxTVWiki
[01:50] <Shadow__X> and if you want just below that there is a link to use a gui
[01:51] <qwebirc56482> gui would be good for me.  I have no idea what I am doing.  :)
[01:52] <Shadow__X> its ok just take your time and also it will be helpful to read the manual
[01:52] <Shadow__X> honestly, it will help alleviate many many new time installer mistakes
[01:58] <qwebirc56482> ok, noob question...  other than grabbing the files one by one how do I get the gui?
[01:59] <Shadow__X> ok go to the github site
[01:59] <Shadow__X> click zip and that will download all the files in a .zip
[02:00] <Shadow__X> once you have done that double click the .zip and that should extract it
[02:01] <Shadow__X> once you do that go to that folder in terminal and do sudo sh install.sh
[02:06] <qwebirc56482> thank you I am working on that now.
[02:18] <qwebirc56482> ok, I have the cards set up.  Now I am not able to connect to the backend  from the front end
[02:19] <qwebirc56482> how do I tell the front end where to look for the back end?
[02:30] <Shadow__X> ok well first we need to make sure you setup the backend correctly
[02:31] <qwebirc56482> ok, what do I need to do to verify?
[02:31] <qwebirc56482> Thank you again for your help.  I really do appreciate it.
[02:34] <qwebirc56482> I basically took the defaults thru the general setup
[02:34] <qwebirc56482> it had the <IP_ADDRESS> for the ip address but I changed that to my <IP_ADDRESS> address so I can connect another client to it.
[02:38] <Shadow__X> you should never put localhost or <IP_ADDRESS> for a backend that other machines will connect to
[02:41] <qwebirc56482> that is fine.  It is not set to that now.  what other settings do you need to know?
[02:42] <Shadow__X> well did you actually setup the graphics card?
[02:43] <Shadow__X> http://www.mythtv.org/docs/mythtv-HOWTO-9.html start at general
[02:43] <Zinn> [www.mythtv.org] MythTV, Open Source DVR
[02:45] <qwebirc56482> I installed the graphics driver
[02:46] <qwebirc56482> Thanks!  I didn't realize there was documentation on this.
[02:47] <Shadow__X> yes that is the mythtv site
[02:47] <Shadow__X> if you follow that it should have everything you need but if not ask here
[03:13] <qwebirc56896> I'm trying to install mythbuntu 12.04 with an nvidia graphics card and no on-board graphics and I'm running into problems.  All the help I've found online for this problem seems to revolve around using the on-board graphics instead of the nvidia card.  Is there any other way around the problem?
[03:34] <Shadow__X> what problem are you having
[03:37] <qwebirc56896> I get a half purple/half black screen if I try to do the default install.  I edited the options to noquiet nosplash nomodeset, then I got an error: Kernel panic - not syncing: VFS: Unable to mount
[04:07] <Shadow__X> could you try to just use nomodeset also make sure you have ahci for your drives
[04:35] <qwebirc56896> the nomodeset only seems to be working so far.  Thank you!!!
[04:35] <Shadow__X> glad i could help
[10:26] <mal> can I login to my mythbuntu backend via putty?
[14:43] <mdurkq> Free TV cards for anyone who can get this card - http://goo.gl/F7WBy - Working in Mythbuntu 12.04 - PM me if you're interested.
[14:43] <Zinn> [goo.gl] TerraTec Cinergy 2400i DVB-T - LinuxTVWiki
[23:05] <mdurkq> Free TV cards for anyone who can get this card - http://goo.gl/F7WBy - Working in Mythbuntu 12.04 - PM me if you're interested.
[23:05] <Zinn> [goo.gl] TerraTec Cinergy 2400i DVB-T - LinuxTVWiki