[06:07] <ScottK> FYI, Kubuntu livefs builds will fail to build until Gnome is fixed thanks to telepathy (see ubuntu-devel for details)
[06:14] <ScottK> qtwebkit-source still building.
[06:56] <j2_> ScottK: I don't understand. Gnome is Broken because of a sharedlib so KDE is also broken?
[08:07] <Riddell> j2_: yes
[08:51] <brestows> how in kde get current keyboard layout
[08:51] <brestows> HI
[08:56] <bulldog98> brestows: for support please ask in #kubuntu
[09:00] <brestows> bulldog98: i need determine in my application 
[09:00] <bulldog98> brestows: ok than it would be good to ask in #kde-devel ,since there are more developers in that channel
[09:01] <bulldog98> and maybe state in your question that you want to know that in your application (code wise)
[09:01] <bulldog98> since I got your question wrong
[09:01] <brestows> bulldog98: this channel (№kde-devel) sleep :)
[09:02] <bulldog98> brestows: it can take sometime until someone sees your question
[09:03] <brestows> bulldog98: when my app start it must be determine keyboard layout 
[09:04] <brestows> bulldog98: sorry my english very bad :( will wait answer
[09:08] <bulldog98> brestows: what is your app supposed to do? Why do you need the keyboard layout?
[09:08] <bulldog98> mgraesslin: hi
[09:09] <mgraesslin> bulldog98: hi
[09:10] <brestows> bulldog98: know about xneur ? 
[09:11] <bulldog98> brestows: after I read about it in wp yes
[09:11] <bulldog98> brestows: maybe as mgraesslin since he has the best knowlegde about Xorg
[09:12] <brestows> ok will try 
[09:14] <Riddell> brestows: you can also browse existing applications to see how they do it, e.g. ubiquity or kvkbd
[09:32] <brestows> Riddell: dbus can give current keyboard layout ? 
[09:47] <Riddell> brestows: I don't know,  browse existing applications to see how they do it
[09:47] <Riddell> I expect there's an API for it
[09:47] <brestows> Riddell: ok
[10:45] <shadeslayer> ScottK: cool, my investigations uncovered a bug in multistrap ... so atleast it wasn't a complete waste of time
[10:56] <bulldog98> Riddell: time for a look at my installer mockup?
[10:58] <Riddell> bulldog98: yeah, what have you got?
[10:59] <bulldog98> Riddell: git clone kde:scratch/kolberg/ubiquity-mockup
[10:59] <bulldog98> qmlviewer -I /usr/lib/kde4/imports Ubiquity-mockup.qml
[11:02]  * Riddell clones
[11:03] <Riddell> bulldog98: ah sweet
[11:04] <Riddell> bulldog98: so starting by porting the current design to QML?
[11:04] <Riddell> bulldog98: what are you using for the buttons?
[11:04] <bulldog98> Riddell: org.kde.plasma.components
[11:04] <Riddell> there's various ways to do that in QML and I don't know if they're all reliable, lightdm has bugs on the input fields
[11:04] <Riddell> and it did have bugs on the buttons but looking at network-management now that's fine
[11:05] <bulldog98> Riddell: only the default theme has the other input fields work for me TM
[11:05] <Riddell> bulldog98: the circles in the bottom left are from the old wallpaper so can be replaced with something appropriate for this one or removed
[11:05] <bulldog98> Riddell: ok was just for having something there
[11:06]  * bulldog98 will finish the rest of the mockup first before he goes into details
[11:06] <Riddell> bulldog98: I think I'd like the central area to be a bit lighter than the wallpaper, many wallpapers are more distracting than the current one so they won't all work as background straight
[11:06] <Riddell> bulldog98: is this what sheytan came up with?
[11:07] <bulldog98> Riddell: all you see is done by me
[11:07] <Riddell> bulldog98: I didn't know you were a talented artist too :)
[11:07] <Riddell> bulldog98: did sheytan not come up with some design or did I imagine that?
[11:07] <bulldog98> Riddell: neighter did I :)
[11:08] <bulldog98> Riddell: I asked him to look at it, but he hasn’t done yet
[11:08] <Riddell> bulldog98: do you have an idea of what's needed to program this and get it working?
[11:10] <bulldog98> Riddell: we need a few model to fill the menus, we need a string provider QObject, a timezone Provider, and we need a few other object to be filled from qml, so we get all the data in python. The rest should be quite easy, cause you only have to get the data back out of the objects
[11:10] <bulldog98> atleast that’s my hope :)
[11:13] <Riddell> bulldog98: it would help people to look at it if you just to put a .png on a web server, minimal effort for people to help is a good thing to do
[11:13] <Riddell> bulldog98: sounds like you know what you're doing, excellent
[11:13] <Riddell> bulldog98: done Python and PyQt/PyKDE before?
[11:13] <bulldog98> Riddell: I’ve got an Video of it (without popups) on my people.ubuntu.com site
[11:13] <Riddell> oh lovely, URL?
[11:14] <bulldog98> Riddell: not really done Python and PyQt/PyKDE before
[11:14] <bulldog98> Riddell: people.ubuntu.com/~bulldog98/ubiquity/ubiquity-mockup.avi
[11:14] <Riddell> bulldog98: conceivably Ubuntu desktop will be into this, they are already into QML and PyQt and this would stop the need of having to maintain two frontends
[11:15] <Riddell> mmm, slide bling!
[11:15] <Riddell> call it Ubiquity Active and you have all the buzz words :)
[11:15] <bulldog98> Riddell: problem is we need kde-runtime for get it working
[11:15] <Riddell> bulldog98: yeah they'll want to use a pure Qt way to do buttons, but there are ways to do that (as shown by unity-2d)
[11:16] <Riddell> so definately an idea to bring up at UDS
[11:16] <bulldog98> Riddell: I won’t be at UDS, cause I have university then :(
[11:16] <Riddell> bulldog98: sure but I can organise a session and maybe you can join by IRC and voice stream
[11:17] <bulldog98> Riddell: sounds interessting
[11:17] <Riddell> you'd be a good example to canonical and other ubuntu teams in starting development 6 weeks before the cycle even begins :)
[11:17] <Riddell> bulldog98: could you start a Kubuntu UDS Q series page and put this on it?
[11:17] <Riddell> wiki page
[11:18] <bulldog98> Riddell: if you tell me which namespace to put it in?
[11:18] <bulldog98> s/?//
[11:19] <Riddell> Kubuntu/UDSQSeries ?
[11:19] <bulldog98> sounds ok
[11:22] <bulldog98> Riddell: created
[11:23] <Riddell> lovely, thanks
[12:22] <bulldog98> Riddell: should I blog about the ubiquity installer mockup?
[12:23] <BluesKaj> Hi all
[12:23] <bulldog98> hi
[12:32] <Riddell> bulldog98: you're on planet ubuntu?
[12:32] <bulldog98> Riddell: yes
[12:32] <Riddell> "Jonathan Raphael Joachim Kolberg"  I can see why you go with bulldog :)
[12:33] <bulldog98> Riddell: yep
[12:33] <bulldog98> Riddell: where by most guys just call me Jonathan
[12:33] <Riddell> bulldog98: yeah go ahead, highlight "same design for now but better effects and easier to make more bling design"  "would be great for the whole ubuntu project to stop having to maintain 2 front ends"
[12:33] <Riddell> "Jonathan" is a confusing label in Kubuntu land :)
[12:34] <Riddell> bulldog98: and include a PNG and a link to the video
[12:34] <bulldog98> Riddell: will blog after I eat my meal
[12:34] <Riddell> maybe <video> works for planet but I suspect it gets filtered out
[12:39] <bulldog98> Riddell: otherwise I can link to it
[12:42] <Riddell> yes you'll need to link to it anyway cos <video> won't work for all especially with a .avi
[12:42] <bulldog98> Riddell: qmlviewer can record in any format ffmpeg knows
[12:42] <bulldog98> also ogv
[12:43] <Riddell> bulldog98: I've had trouble with ffmpeg recently just trying to convert a series of photos into a video, it's too complex for me I think!
[12:43] <Riddell> or avconv as it is now
[12:44] <bulldog98> Riddell: there is a shortcut for recording in qmlviewer and that uses ffmpeg -> you can record in ogv or avi or…
[12:46] <Riddell> ah right, well I guess ogv is best for <video> working but no great answer there
[13:36] <Riddell> drkonqi works again, all hail KDE sysadmin
[15:35] <j2_> Riddell: RE: Kubuntu being fixed isn't that the same as saying that Kubuntu will be fixed once telepathy is fixed ?
[15:36] <Riddell> j2_: I don't know what context you are refering to
[15:36] <j2_> Riddell: the comment that Kubuntu will be fixed once GNOME is fixed because telepathy is broken
[15:37] <j2_> It's a shared part of the stack so once telepathy is fixed both Ubuntu and Kubuntu will be working. Not really a matter of one before the other
[15:37] <j2_> Kubuntu livefs builds will fail to build until Gnome is  fixed thanks to telepathy
[16:09] <Riddell> j2_: yes
[16:39] <j2_> Riddell: ok
[16:48] <ScottK> shadeslayer: qtwebkit-source build finished successfully.
[16:53] <shadeslayer> \o/
[16:53] <shadeslayer> ScottK: could you please upload it?
[16:53] <ScottK> OK
[16:53] <Riddell> yay!
[16:54] <Riddell> good work shadeslayer, ScottK 
[16:54] <Riddell> well assuming it builds in the buildds :)
[16:54] <shadeslayer> well, digikam still needs investigating 
[16:59] <ScottK> shadeslayer: Uploaded.  Thank you for your contribution to Kubuntu.
[16:59] <shadeslayer> :)
[17:01] <Riddell> calligra and kdevelop also need updating I think
[17:01] <Riddell> but stay on the build failures if you're on a roll
[17:02] <shadeslayer> I'm doing KDevelop as we speak ;)
[17:03] <shadeslayer> iirc I put kdevplatform in my PPA
[17:58] <shadeslayer> ffffuuuuuu
[17:58] <shadeslayer> ScottK: what happened to qtwebkit? 
[17:58] <shadeslayer> It failed
[17:58] <shadeslayer> on armhf ... not armel
[18:00] <shadeslayer> runtime/WriteBarrier.h:70:43: warning: cast from 'JSC::JSCell*' to 'JSC::Structure*' increases required alignment of target type [-Wcast-align]
[18:01]  * shadeslayer goes off to #qtwebkit to ask
[18:03] <debfx> why did you expect that it builds on armhf? it didn't work before
[18:04] <shadeslayer> debfx: I thought ScottK tested it in armhf ...
[18:04] <shadeslayer> debfx: plus, earlier the builder ran out of memory for the linker
[18:04] <shadeslayer> "/usr/bin/ld: final link failed: Memory exhausted"
[18:05] <debfx> and now they have "fixed" the compiler to segfault ;)
[18:05] <shadeslayer> lol
[18:05] <shadeslayer> really?
[18:05] <shadeslayer> "g++: internal compiler error: Segmentation fault (program as)"
[18:06]  * shadeslayer cries
[18:07]  * debfx retries the build
[18:07] <shadeslayer> somehow I missed that ...
[18:07] <debfx> let's see what bug we trigger next
[18:07] <shadeslayer> :D
[18:19] <karen> hi, is there anyone who manage the chromium package under kubuntu?
[18:20] <ScottK> karen: It's the same as Ubuntu.
[18:21] <ScottK> karen: What's your question, we can help you figure out who to ask.
[18:40] <ScottK> shadeslayer: It was tested on armel.  I intend to switch our boxes over to Debian armhf, but didn't manage it yet.
[20:23] <shadeslayer> ScottK: ahhh ...
[20:23] <shadeslayer> also
[20:23] <shadeslayer> KDevelop Packages : https://launchpad.net/~rohangarg/+archive/experimental/+packages
[20:27] <ScottK> shadeslayer: Does it need FFe?
[20:27] <shadeslayer> ScottK: Nope, only bug fix release I believe
[20:27] <ScottK> Please check (all three)
[20:27] <shadeslayer> !info kdevelop
[20:28] <shadeslayer> ScottK: we have 4.2.81 in precise
[20:28] <ScottK> kdevelop | 4:4.2.81-0ubuntu2 |
[20:28] <shadeslayer> yeah, and this is 4.2.90
[20:28] <ScottK> So that's from an Alpha to a Beta, right?
[20:28] <shadeslayer> yes
[20:29] <ScottK> So it would not be unusual to see feature changes between the last alpha and the first beta.  Please check.
[20:29] <shadeslayer> okay, will do
[20:29] <ScottK> I can give FFe or I can sponsor, but not both.
[20:34] <shadeslayer> I'll need some time, will get back to you in a bit
[20:34] <ScottK> OK.
[20:46] <shadeslayer> ScottK: everything looks good, no new features from what I can see
[20:47] <ScottK> OK.  Thanks.
[21:07] <Riddell> guten abend
[21:56] <bulldog98> shadeslayer: isn’t the final out? (kdevelop)
[21:57] <shadeslayer> afaik no
[21:58] <shadeslayer> bulldog98: final will be out around April 5
[21:58] <bulldog98> shadeslayer: ah ok
[21:58] <shadeslayer> Most likely it should be out *before* April 5
[21:58] <shadeslayer> I'm guessing last week of March
[23:00] <bulldog98> Riddell: time for an other try of the mockup? (just git pull)
[23:22] <Riddell> bulldog98: looks much the same, what's changed?
[23:23] <bulldog98> Riddell: I desinged the rest of the sites
[23:23] <bulldog98> and moved the buttons out of the view to the bottom
[23:24] <bulldog98> and I made the timezone stuff
[23:24] <Riddell> oh cool, it's interactive
[23:24] <Riddell> bulldog98: for the bit marked "here comes the other stuff" do you know how to code that?
[23:25] <bulldog98> only problem atm is that I don’t know how I should react to different screen sices
[23:25] <bulldog98> Riddell: in which file?
[23:25] <Riddell> partitioner
[23:25] <Riddell> presumably QML can do SVG fine?  (for the timezone map)
[23:25] <bulldog98> Riddell: yes
[23:25] <Riddell> currently ubiquity is fixed size I think
[23:26] <bulldog98> Riddell: partitioner I think I could manage that, but it would need some time
[23:26] <Riddell> for the "who are you page" that's the design we came up with 5 years ago in a basement in london, the gtk ubiquity has a nicer design now so it might be worth looking at that
[23:27] <Riddell> looking lovely
[23:27] <bulldog98> Riddell: pic of it?
[23:27] <bulldog98> Riddell: blog post text: http://paste.kde.org/436994
[23:28] <Riddell> I can't find one but this reminds me it needs to include the boot splash stuff
[23:28] <Riddell> http://www.kereltis.com/wp-content/uploads/2011/01/ubuntu-install-2.png
[23:29] <Riddell> which is shown on first use of CD
[23:29] <Riddell> ubiquity also has different modes, running standalone, running in a desktop session and oem-config
[23:30] <Riddell> bulldog98: http://www.kereltis.com/wp-content/uploads/2011/01/ubuntu-install-7.png
[23:30] <Riddell> this shows the full range http://www.kereltis.com/2011/01/05/a-simple-guide-to-installing-ubuntu-10-10/
[23:30] <bulldog98> Riddell: different modes is doable (needs different qmls I’d say)
[23:31] <Riddell> slide show is a bit nicer but very ubuntu designed, the progress bar is at the bottom
[23:46]  * ScottK got distracted.  Uploading kdevelop stuff now.
[23:54] <ScottK> shadeslayer: I think all the kdevelop stuff is uploaded now.
[23:59] <ScottK> shadeslayer and Riddell: qtwebkit-source built on armel, but not armhf (linker memory exhaustion again).