[00:11] presumably UTC? [00:11] and 21 Jan 2010? [00:15] yes === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates [01:07] there are backport requests which haven't been acted on since last June! [01:07] someone should complain to the slacker archive admins [01:08] Definitely. [01:08] crimsun: you could just read the mailing list [01:24] ~ninjas [01:24] Hmmm. [01:24] !ninjas [01:24] Help! apachelogger, JontheEchidna, nhandler, Riddell, ScottK, Lex79, Quintasan, neversfelde, maco, rgreening [01:24] To the batcave .... [01:25] the batcave's not letting me in [01:25] Riddell: any word on newer sip? [01:25] JontheEchidna: "tomorrow" [01:25] the configure script changed quite a lot and debian's build out of source tree patch needs quite a bit of updating [01:25] ah, the ever-nebulous "tomorrow". ain't timezones the greatest? :) [01:26] Tomorrow, tomorrow, I love you, tomorrow .... [01:26] well since its wednesday in Riddellville... [01:27] JontheEchidna: what component does the touchpad kcm belong to? [01:27] I'm not sure where to file a bug about it [01:27] The kcm-touchpad package :) [01:28] there's no upstream bug tracker, except the kde-look.org webpage [01:28] ah, ok, then I'll file a bug on LP, thx [01:28] thanks for testing [02:20] Hello. rbelem and I are packaging plasma-mobile, and tried to include the debhelper snipped from plg-kde-tools to pass the right cmake arguments, but were advised this was deprecated. What's the current best practice? [02:22] persia: Debhelper 7 using --with kde is the BCP. [02:22] persia: that's fine to do if you're into cdbs, debhelper 7 is all the rage on the streets [02:22] ScottK: Thanks. Should one specify both --with quilt and --with kde, or is that implied? [02:22] quilt should be implied as I recall [02:22] Riddell: dh(1) is the only way I do new packaging :) [02:23] persia: IIRC it is implied, but I've also seen both listed. [02:23] Excellent. Thanks a lot. [02:23] persia: Since I doubt you need to worry about backports, you might consider v3 source package so you'll be able to use .bz2 tarballs once there is a release. [02:24] Then you definitely don't need --with quilt [02:24] Yeah, but I'm not fully versed on v3 yet :) Maybe for the next revision (as the first revision is expected to be a VCS snapshot) [02:25] I know how that is. [02:25] (svn snapshot all the to the last release with plasma-netbook) [02:26] In many ways, it makes sense to do it that way, as one can better collaborate with upstream and test agressively. On the other hand, it means lots more revisions. [02:28] Yep. [02:28] I assume plasma-mobile won't see a release until KDE 4.5? [02:29] One issue I ran into with plasma-netbook last cycle was that once they started depending on the next KDE release for features, it became very hard to continue to track their progress. [02:29] rbelem: Do you know the release schedule for plasma-mobile? [02:29] persia, yep... talked to arthur today [02:30] he said that we can work in the playground for now [02:30] BTW, one thing we did was have an IRC channel where they could hang out and only stuff specific to Kubuntu Netbook/Plasma Netbook would come up. It was handy. [02:31] rbelem: They key question is when will he start to rely on features that are not in KDE 4.4. Once that's done, then it gets tricky for Lucid. [02:32] that's true, but we can release as a technology preview [02:32] what do you think? [02:33] and for lucid+1 we release a "final" release [02:34] ScottK, persia ^ [02:34] * persia doesn't believe in the concept of "final" releases [02:34] rbelem: Yes. That's what we did in Karmic for Kubuntu Netbook and it worked out well. [02:34] final/production [02:35] For "production", it makes a lot of sense. [02:36] :-D [03:07] are there any screenshots of this mobile shell? [03:14] rbelem: ^^ [03:15] Riddell, yep [03:15] rbelem: able to tell me where? :) [03:15] Riddell, just one second :-) [03:16] Riddell, http://labs.trolltech.com/blogs/2009/10/27/qgraphicsview-is-a-hummer-plasma-is-the-luxury-version/ [03:23] Nice [04:09] Go Riddell go (super archive admin) [04:13] I do believe I've closed all the bugs which can be closed [04:13] must be time for bed :) [04:13] wowie [04:31] plasma-mobile tries to link against libplasmagenericshell, which appears to be in kdebase-workspace-bin. There's a build-dependency on kdebase-workspace-dev, which doesn't appear to install kdeworkspace-dev. Am I encountering a bug, or do I need to also build-dep on kdebase-workspace-bin (and should I be reading some specific wiki page rather than asking here)? [04:34] persia: The build-dep on kdebase-workspace-dev should be enough. plasmagenericshell is new in KDE 4.4. It's quite possible something needs to be in the -dev package that isn't. [04:36] persia: What specifically is it trying to link against? [04:36] libplasmagenericshelll ( -lplasmagenericshell) [04:37] I have kdebase-workspace-dev.install:usr/lib/libplasmagenericshell.so in the install file. [04:38] That would lead me to believe what you need should be there. [04:38] I see that. On my lucid install (amd64), I only see debian/doc/* in kdebase-workspace-dev [04:38] Hmmm. That doesn't sound right. [04:38] Err, nevermind. Wrong command. Now I'm confused. [04:38] OK [04:39] (dpkg -S vs dpkg -L) [04:41] It's in the .deb on Launchpad. [04:42] Indeed. I just failed completely in my investigation. [04:42] So I came to ask here, when I should have blamed the source I'm chasing. [04:43] No problem. It happens sometimes. [04:49] OK. Thit time I'm more sure. kdebase-workspace-bin contains usr/lib/libplasmagenericsheel.so.* and kdebase-workspace-dev contains usr/lib/libplasmagenericshell.so as a symlink, which doesn't get satisfied because kdebase-workspace-dev doesn't depend on kdebase-workspace-bin. [04:50] That I believe. [04:50] (because I just determined the same thing). [04:51] Should the library be split out, or should a dependency be introduced? May I be of assistance with either path? [04:51] Since plasma-netbook and plasma-desktop are built out of the same source package, this doesn't come up for those. [04:51] It should have the depends. [04:52] kdebase-workspace-dev on kdebase-workspace-bin ? [04:52] Yes [04:53] Seems heavy to have to install akonadi-server and phonon to build stuff, but it's the easiest way to fix it. [04:55] If we were going to split it out, I'd want to coordinate with Debian. We may do that, but not without coordination. [04:56] This makes a tremendous amount of sense :) [04:57] We're packaging KDE 4.4 rc 2 right now. I'll put this change in bzr for when we upload that. In the meantime, if you build-dep on -bin, that would be a workaround. [04:57] That was my plan. Thanks for the quick turn-around. [04:58] persia: Pushed. [08:58] * jussi01 wonders why there are like 3 different scribus's in the archive... scribus, scribus-svn, scribus-cvs hrrr === njpatel_ is now known as njpatel [10:41] Riddell, I'm looking at the translations imports queue and I've found two KDE templates I'm not sure what to do with. [10:41] * kscreensaver/kxsconfig/hacks.pot in kdeartwork - is this to be translated, shall I accept the template? [10:41] * debian/kdelibs4-dev/usr/include/kde/kde.pot in kdelibs - I believe I should block this one [10:58] Riddell: hmm, that's weird. If I add the propritary license for Qt, launchpad tells me I am not qualified for project hosting, even if I ddin't want to publish it there under said propritary license :) [11:00] Riddell, continuing with translations, could you please confirm the following: http://ubuntu.pastebin.com/d56491e2b [11:42] dpm: we don't want kde.pot [11:42] ok, I'll block that one [11:43] dpm: not hacks.pot [11:43] at least, it isn't in http://websvn.kde.org/trunk/l10n-kde4/templates/messages/kdeartwork/ [11:44] that hacks stuff should be in kxsconfig.pot [11:47] yes, I can see that the few msgids I've checked are at least in kdeartwork/kxsconfig.pot, so I'll block hacks.pot [11:50] po/akonadi_next.pot now moved to kdepim (before in kdepim-runtime) [11:50] 2. po/akonadi-kcal.pot now moved to kdepim (before in kdepim-runtime) [11:50] those are true [11:51] ok [11:53] dpm: kioexec.pot is still in kdebase-runtime [11:54] kabc_ldapkio.pot _file _dir _net are all still in kdepimlibs [11:55] so is kabcformat_binary.pot [11:55] libkscreensaver.pot is still in kdebase-workspace [11:55] and kcmshell.pot is still in kdebase-runtime [11:58] Riddell, weird, according to LP they seem to have been uploaded in kdelibs -> https://translations.edge.launchpad.net/ubuntu/lucid/+source/kdelibs/+imports?field.filter_status=NEEDS_REVIEW&field.filter_extension=pot [12:00] dpm: oh that's KDE 3 kdelibs [12:00] what a pain [12:01] dpm: that's due to be moved to universe [12:01] it's only being kept in main by koffice which nixternal is working to fix [12:01] maybe I should just move it to universe now [12:02] danimo_: pong, sorry for the late reply. i'm travelling these days so not very responsive [12:03] dpm: I moved kdelibs source to universe so this shouldn't come up again [12:04] Riddell, thanks! Re: the current entries on the list I gave you. Are they all from KDE 3 kdelibs, so that I can block them? [12:04] dpm: yes they are [12:04] dpm: oh no [12:04] dpm: they're all in KDE 4 kdepimlibs/kdebase-workspace/kdebase-runtime [12:05] they are also in KDE 3 kdelibs but we don't care about that now [12:05] JontheEchidna: can you remember where that list of obsolete kde-l10n packages was? [12:06] Riddell: I saved it in a txt file actually [12:06] "asktoremove.txt" [12:06] JontheEchidna, that would be quite useful to have, can you post it somewhere? [12:06] Google doesn't find it [12:06] dpm, Riddell: http://pastebin.com/f5a477496 [12:06] saved on my computer ;-) [12:07] what happens to packages once they are in https://launchpad.net/ubuntu/lucid/+queue [12:07] gosh, how old fashioned [12:07] there's a few things other than l10n files though [12:07] s/files/packages [12:07] dpm: do you have an opinion about removing those source packages? upstream doesn't ship them because they went below the threashold [12:07] dpm: presumably the strings will still be in launchpad [12:08] a few of them got removed because they were merged into their parent packages (e.g. the locale variants) [12:08] like sr-latin [12:09] freinhard: they stay there until reviewed manually for sanity by an archive admin, this only happens on the first upload [12:09] freinhard: it actually happens twice on the first upload, once for the source then again for the .debs [12:10] Riddell, I think I'd go for shipping them in Kubuntu, so that folks have got the opportunity to complete them, it's the same approach with GNOME (only that GNOME ships all translations, regardless of completion, IIRC) [12:10] and as JontheEchidna mentions, the variants should be integrated in the main language packages [12:10] I know at least ca-valencia should be in the same package as ca [12:10] dpm: well we don't ship kde-l10n packages, they're only there to feed launchpad (and for docs but I doubt any of those languages have much of them) [12:11] aren't the templates in the not-shipped packages already in launchpad? [12:12] Riddell, we do ship them, don't we? They contain other translated files other than PO files to feed to LP [12:12] JontheEchidna, the templates come from other packages than the kde-l10n ones [12:12] ups, meant .pos [12:13] * JontheEchidna woke up 12 mins ago [12:13] :-) [12:14] JontheEchidna, yes, some of the POs are in LP, since when you guys import some of the snapshots, the translations have not yet been removed from kde's svn if they are below the level (I believe they remove translations when tagging the release?) [12:15] brb [12:15] dpm: yeah the have docs and some translated resource files but if upstream doesn't ship them those files could be out of date [12:16] * JontheEchidna notes that KDE docs are outdated in general [12:16] It's quite a list of packages to maintain manually though [12:18] * freinhard needs a lot of money to enslave some dev to fix bugs in kopete [12:18] oh wait, enslave and money mutually exclude each other [12:19] so where's some dev? :) === ulysses_ is now known as ulysses === sebasje is now known as sebas === ulysses is now known as Guest98585 === Guest98585 is now known as ulysses [12:58] nice netsplits [13:00] JontheEchidna: arounds [13:00] for a bit anyways [13:02] JontheEchidna: i'm gonna split plasma-widget-kimpanel into 3 packages [13:03] the widget, the scim backend and the ibus backend? [13:03] (guessing here) [13:03] JontheEchidna: yes [13:03] there is IBUS agent for kim panel? [13:03] and also I need add conffile and postinst/prerm [13:04] Quintasan|Szel: yes [13:04] Quintasan|Szel: but hasn't been packaged yet [13:04] I don't think kdeplasma-addons installs it, actually [13:04] unless there's a hidden build-depend cmake doesn't inform us about [13:05] brb, we are going to have a problem, maybe [13:05] like plasma-widget-observatory had [13:06] JontheEchidna: Quintasan|Szel upstream dosen't provide CMake to make ibus backend installable by default, so we need include it manually [13:07] do you know why they don't? [13:08] JontheEchidna: no special reason, upstream author think its just a python scripts, could be put under anyplace depends on user's will [13:08] PROTIP: we will probably need to somehow make ibus start automagically if the kimpanel uses ibus [13:08] mmh, bad upstream attitude [13:09] freeflying: I guess we have to do what we have to do [13:09] fabo: still around? [13:09] and there is one more thing which is Qt. [13:09] Quintasan|Szel: to achieve this, we need patch language-selector-qt [13:10] freeflying: sound resonable [13:10] danimo_: yeah [13:10] okay the thing looks like this [13:11] fabo: We were talking about patches to Qt yesterday [13:11] fabo: kubuntu has one to make legacy 32 bit apps run on 64 bit using the debian file system structure [13:11] probably, I will push all the changes need in kdeplasma-addons in 1 day [13:12] fabo: is there a specific reason why you don't want it in debian? [13:12] Out Qt4 packages use XIM by default. if you want to use IBus you need to change that manually in the input field by right clicking and selecting it in Input method menu. [13:12] I've tried exporting different IM variables to use IBus but with no success and ppl on #qr are quiet. [13:12] Quintasan|Szel: qt/gtk both support xim and native immodule [13:13] Quintasan|Szel: saying if you wanna use ibus with qt native immodule, you need ibus-qt4 [13:15] danimo_: i don't have a strong opinion about it. i should really take a look at it and i don't have any reports wrt this issue, it's postponed. [13:15] fabo: anyway, thanks for the nighly build scripts [13:15] fabo: I haven't really made use of them, but it should be simple enough [13:16] danimo_: ia32 support is a bit different on debian (afaik), so i couldn't cherry-pick without looking seriously ;) [13:16] We need to set IBus to be used by default [13:16] Not XIM as it is now [13:16] fabo: sure, I was just wondering [13:17] danimo_: maybe i'm wrong and it's a non-issue [13:17] danimo_: btw, i'll raise this and put it on my sight :) [13:17] I bet we do not want to pull another package just to make a bridge between ibus and xim [13:17] Hm, I need to poke gluons upstream about CMake. [13:17] Quintasan|Szel: we can't, otherwise those users don't wanna IM will complain to you :) [13:18] LOL, no [13:18] XIM is also an IM and noone complains [13:19] and japanese/korean/chinese input doesnt work with XIM [13:19] at least for few users I asked [13:20] I've* [13:24] Quintasan|Szel: how come? [13:24] fabo: fine :) === yofel_ is now known as yofel [14:16] danimo_: do you know who maintains the IM module stuff in Qt to ask about whether we can/should set ibus as default? [14:17] Lex79: qt is still waiting on a phonon patch? [14:17] yes [14:17] Lex79: is it actually a new version of phonon? [14:17] or just rejigging the patch for new Qt? [14:17] just rejigging [14:18] it's a bit complicated refresh that patch [14:18] it's very big [14:18] yes it's a beast === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates === dendrobates is now known as dendro-afk [15:20] hm, Chromium Daily builds borked? [15:21] haven't got one in two days, and the current one is quite broken here [15:21] (doesn't load many pages) [15:21] markey: same problem here === dendro-afk is now known as dendrobates [15:24] 4.0.302.0~svn20100119r36505-0ubuntu1~ucd1 works here [15:31] 4.0.302.0~svn20100119r36505-0ubuntu1~ucd1~karmic doesn't work correct:| [15:33] ulysses: what do you mean correct here? some website won't work? [15:34] freeflying: yes, Chromium can't load many websites [15:34] ulysses: for example? [15:35] facebook.com [15:36] ulysses: interesting, it works as usual here [15:36] oh, I made a mistake, facebook works, but Farmville doesn't :/ [15:37] :) [15:52] woha new attacks on freenode ..... it gets really weird [16:04] awooga, sip4 and python-qt4 uploaded to ninjas [16:04] Riddell: python-qt3 is currently broken. Any updates for that? [16:05] ScottK: yeah that'll need recompiling for the new SIP, I'll take a look [16:14] how do i get the kde kpackagekit notification reminder back if i accidentally close kpackagekit without updating? [16:15] seele: just starting kpackagekit and check for updates isn't what you want? [16:16] it sometimes lives in the "i" notification thing in the system tray [16:16] freinhard: no, i'm trying to take a screenshot of the popup notification for a bug [16:16] Riddell: it goes away if you click "review and install packages" [16:16] which brings up kpackagekit that i closed before i took my screenshot [16:17] logout and login doesn't do the trick? [16:19] hmm btw: kpackagekit doesn't parse the dpkg.log, it does the logging on it's own? [16:19] huh.. i guess i could try that. dont want to close 20 aps, hehe [16:20] possibly it can be done through qdbus but I don't have kpackagekit installed just now (due to playing with pyqt) so I can't check [16:20] kill update-notifier-kde and start it again? [16:20] or isn't that update-notifier-kde anymore? [16:21] that isn't the package notifier [16:24] could try to start /etc/cron.daily/apt manually [16:27] it's kpackagekit, not apt [16:28] look in qdbus org.kde.kded and see if there's a /module/kpackagekit or something [16:28] see what methods it offers [16:29] saw some dbus magic in that file, so i guessed it might be worth trying [16:46] glatzor: yo, how's the packagekit update coming? [16:47] ulysses: iGoogle doesn't work here either, nor does Aaron's blog work [16:47] and some other sites [16:47] it is weird [16:47] Riddell, sorry, but I had to work at the weekend since nearly all my fellow workers are ill. So I haven't found much time. [16:47] maybe it only works on sites with correct sentence capitalisation :) [16:48] Riddell, I already packaged 0.5.4 last year and 0.5.6 should not be much different. but I would like to give it a good test before uploading [16:48] glatzor: yeah me or anyone could probably do it, but we'd trust you more :) [16:49] glatzor: what's the status of 0.6? that's the current packagekit stable? do you know if kpackagekit supports it? [16:50] Riddell, Currently 0.6 has got only some minor api changes [16:51] Riddell, but Richard recommends to ship 0.5.6 [16:51] Riddell, Kpackagekit already has been adapted to these changes in trunk [16:51] glatzor: so we should presumably go with 0.5.6 in lucid? [16:52] Riddell, right. 0.5.6 should fix a lot of the problems [16:53] Riddell, I don't expect that we will get support for debconf or configuration file changes in Lucid [16:54] glatzor: but that'll come in 0.6.x? [16:54] Riddell, not yet. [16:55] Riddell, cjwatson rejected the patches from dantti. But I don't know if he will find the time to implement his solution [16:55] right [16:56] when is package freeze? [16:56] glatzor: anyway you have the lock on updating to 0.5.6, if you feel you're not going to get to it soonish we're here to take over [16:56] daskreech: LucidReleaseSchedule [16:57] ScottK: python-qt3 compiles and runs fine but not with the builddir!=srcdir changes that our packaging has so we'll need to redo the packaging somewhat [16:57] Riddell, ok [16:57] Riddell, I have to talk now with a customer. see you [16:58] thanks glatzor [16:58] Riddell: If Virtuoso 6.0.1 comes out post feature freeze it can't be shipped correct? [16:58] Without an exception [16:59] daskreech: it would need an exception, that's not hard to get if there's a good reason for wanting it and good reason to believe it wouldn't cause problems [16:59] Though I honestly cannot see why it wouldn't [16:59] It's an LTS and 5.x series is dead [16:59] right now I'm just concerned with getting it into main [17:08] RIght :) one step at a time [17:08] seele: there's no qdbus interface for kpackagekit notifier, it seems to just work in its own time [17:09] hum.. so i'll just have to sit and wait [17:09] seele: we do actually patch that notifier, to remove the long list of packages which need updating which gets far too long and isn't very useful in a notification anyway [17:10] agreed, i was just trying to fix the icon [17:10] seele: this one? http://people.canonical.com/~jriddell/tmp/packagekit.png [17:11] icon could do with being smaller :) [17:11] yes, that's it! [17:11] thanks, i'll use that [17:11] although now i need to look up the standard size, i dont know what it is [17:12] i thought the notification class would take care of that on it's own [17:13] looking at printer-applet we have [17:13] KNotification.event(title, text, KIcon("konqueror").pixmap(QSize(22,22))) [17:13] so it does seem to be up to the app to specify the size, it's just a pixmap which is passed not an icon name [17:13] so 22x22 looks like the default size? [17:14] seele: well it's up to the application [17:14] that's the size I chose when writing printer-applet [17:14] oh, speaking of the printing [17:15] you make the PC-BSD guys very sad [17:15] uh oh [17:15] they're not python fans? [17:15] no, the problem is porting it i guess. they apparently had some trouble getting it all to work [17:16] they guy said it all sad-like and stuff.. it brought great shame to me during the camp talk ;) [17:16] ah, an audience comment [17:17] well it needs cups, python-cups some hal thing and pykde which are all hard to package so if you will insist on working on obscure platforms then they'll be even harder to package and get working [17:17] but as a coder I'm very happy to make use of other people's hard work so I don't have to repeat it [17:18] Riddell: no, it was during the PC-BSD talk [17:18] he said something about "KDE is easy on FreeBSD -- except for system config printer because it is in python and makes me sad" [17:20] high level language are the future, you can't fight it [17:20] if you're going to make a distro you'll have to get them packaged [17:21] next time just tell him how much happier it makes me, the karma is balanced [17:25] Riddell: Is someone doing the python-qt3 changes? [17:26] ScottK: I was going to ask shlomme for his thoughts [17:26] Ah. Good plan. or NCommander. [17:26] He seems to have been active on those packages recently in Debian. [17:26] ScottK: fyi CALUG meeting Feb 10, special guest speaker Jonathan Riddell [17:27] seele: Nice. [17:27] ooh, I'm famous :) [17:27] ScottK: KDE 4.4 release party Feb 12, probably piratz [17:27] or special anyway, I'll take that as a compliment [17:28] Riddell: special enough you don't need to take a bus to the talk :P [17:28] I'll pack my bike [17:53] Riddell: bug 510244 [17:53] Launchpad bug 510244 in choqok "Please sync choqok choqok_0.9.4+git20091230-1. (main) from Debian unstable" [Undecided,New] https://launchpad.net/bugs/510244 [17:55] neversfelde: sounds like a decision [17:55] Riddell: I explained at the bottom, why I created the sync request [17:56] yep [17:56] I use the alpha for 2 or 3 days now and it is very stable, so I think I would prefer having choqok 0.9.4 in Lucid [17:57] on the other side it is LTS ;) [17:57] neversfelde: Better to have useful code that upstream will support. [17:57] If upstream suggests we jump to it, then we should. [17:58] ScottK: upstream prefers the alpha version, too [17:59] Just get it in writing .... [18:00] he did [18:01] Good enough then I'd say. [18:11] Ubuntu shipped a pre release for LTS as I recall [18:54] markey: there's a new Chromium daily build, now it can load the websites correctly [19:20] ulysses: thanks, getting it now [19:22] ulysses: yay, it does indeed work :) [19:22] coolness [19:22] until it goes wrong again:/ [19:51] <_Groo_> hi/2 all === ggorgen is now known as gkmngrgn === flacoste is now known as flacoste_afk [23:42] <_Groo_> hi/2 all [23:55] <_Groo_> any motus alive? [23:55] * _Groo_ searches for MOTUS ... oO... jungle drums... [23:56] ¿qué? [23:57] i.e., yes there are. What's the /real/ question? [23:57] <_Groo_> i made a kdemultimedia 4.4 backport with latest master tree with support for PulseAudio... might be a good idea take a look at it... [23:57] <_Groo_> it integrates very well with ubuntu PA... and still has support for alsa if needed. [23:57] _Groo_: kmix patch or other things too? [23:58] <_Groo_> Riddell: hi jonathan... basically kmix, i pulled directly from the developer git branch [23:58] _Groo_: is the intent to land it in Lucid? [23:58] <_Groo_> Riddell: like he wrote on his blog he tried to be the least invasive as possible.. and i have to admit it works pretty well [23:58] _Groo_: put it in a PPA and we'll take a look [23:59] <_Groo_> crimsun: i would think it would be a good idea... its for the motus to decide... i think y package is very clean.. i can upload it to revu if you guys want [23:59] but as far as I've seen you have to start kmix with an environment variable if you don't want to use pulseaudio and that's not going to work [23:59] <_Groo_> Riddell: its already in my ppa :) [23:59] right, opting out of the PA view isn't as friendly as it could be