[00:03] <Riddell> shtylman: sudo stuff is in bin/ubiquity-wrapper
[00:06] <shtylman> Riddell: .... hm... I havn't touched that...
[00:06] <shtylman> is there a bug associated with it?
[00:06] <shtylman> or is it realted to that bug...
[00:08] <Riddell> well here's a thing, turns out it's my change and it was done a year ago
[00:10] <shtylman> interesting...
[00:17] <shtylman> Riddell: so would you like me to investigate something? is the installer not working?
[00:19] <Riddell> shtylman: well if you fancy it you could see what breaks if you remove the "temporary force" bit
[00:19] <Riddell> but I don't suppose it's very important
[00:19] <Riddell> shtylman: more important is what's the status of the slideshow?
[00:31] <shtylman> Riddell: k..will check... slideshow status is the same...still waiting on nixternal (or anyone willing) to give feedback on the slides
[00:31] <shtylman> then it can be merged in
[00:38] <Riddell> shtylman: just merge it in now so we can check it works for the alpha next week, we can fix up the slides themselves after
[00:38] <shtylman> Riddell: basically, the slideshow is there, I just need the content verified or changed...
[00:39] <shtylman> Riddell: alrighty...I will do that
[00:39]  * Riddell snoozes
[00:39] <shtylman> enjoy
[04:24] <yuriy> huh in konqi 4.3.1 on jaunty all i have is adblock in the tools menu
[04:24] <yuriy> i can't change the user agent
[07:20] <nixternal> shtylman: uploading my bzr branch for the updated slides...version 0.1 :)  they can get refined up until string freeze, which is soon
[08:22] <spstarr> hmm
[08:22] <spstarr> do we have PPAs for the new r6xx stuff coming?
[08:45] <apachelogger> ScottK: there is always my extragear-release script
[08:45] <apachelogger> of course it happens to work with playground as well :)
[08:46] <apachelogger> knm might need some code enhancements though, since it doesn't follow the $component/$area/$app structure
[08:46] <apachelogger> lemme take a look
[09:28] <apachelogger> uh
[09:29] <apachelogger> Nightrose: I thik I just came up with a way more efficient way of obtaining the right po files
[09:29] <apachelogger> not particularly interesting for amarok, but for example for kipi :)
[09:45] <Sput> apachelogger: make Quassel work with gettext!
[10:02] <apachelogger> Sput: make quassel use ki18n :P
[10:04] <apachelogger> Sput: you could always use lowlevel gettext I suppose
[10:11]  * apachelogger goes digging
[10:29] <apachelogger> Sput: well, it does not look good at all, even though gettext can extract qt strings and put them in a pot, Qt will not wanna read them from a mo
[10:35] <apachelogger> ScottK: https://code.edge.launchpad.net/~apachelogger/+junk/release-script-refactor ./networkmanager.rb -b trunk --no-stat --no-doc --no-tag
[10:36] <apachelogger> will query version and access type to kde svn
[10:36] <apachelogger> spits out tar
[10:39] <apachelogger> Sput: you could access it via klocale though :P
[13:04] <apachelogger> http://aplg.kollide.net/images/android/notificationbar.png poor notification bar is all filled up :S
[13:09]  * apachelogger notes that he had enough bitching from apport for this cycle
[13:09] <apachelogger> nixternal: I certainly hope that thing is not going to be aggregating data in the final
[13:20] <ScottK> apachelogger: Thanks.  One of us should tell Tonio when next he appears.
[13:26] <apachelogger> ScottK: btw, kamoso is still waiting in new :P
[13:26] <ScottK> OK.  Probably later today.  Didn't get home until nearly 2AM and I think it's time for a nap.
[13:28] <apachelogger> hehe
[13:40] <apachelogger> fabo: ping
[14:41] <shtylman> nixternal: branch location?
[14:48] <shtylman> nvm... found it :)
[15:15] <fabo> apachelogger: pong
[15:27] <Nightrose> can someone help me with finding the kubuntu logo without the text? so just the gear
[15:27] <Nightrose> i need it for the kubuntu account on identi.ca and I can't find a version without text
[15:27] <Nightrose> apachelogger: ^ you had one no?
[16:09] <a|wen> Nightrose: https://wiki.kubuntu.org/KubuntuArtwork ... download as .svg and use eg. inkscape to delete the text before exporting to .png
[16:09] <Nightrose> a|wen: doh! should have thought of that...
[16:09] <Nightrose> thx
[16:09] <a|wen> np :)
[16:33] <yuriy> nice free day.. what kubuntu stuff needs doing
[16:37] <yuriy> hmm help -> report a bug is broken in jaunty packages
[16:38] <yuriy> is there some doc on how kubuntu packaging works now that we use bzr?
[16:46] <yuriy> don't see any patches in kdebase that would kill the tools menu
[17:01] <ScottK> yuriy: It's not so different.  Just check in bzr for changes someone already made, but didn't upload and push your changes there when you're done.  i can give you a quick run through if you want.
[17:01] <yuriy> ScottK: well for starters do i need to check something out of somewhere instead of using apt-get source?
[17:01] <ScottK> You actually need to do both since we just put /debian in bzr
[17:03] <yuriy> is there some tool that takes care of that? otherwise what do i do, so the .bzr doesn't get in the source package and such
[17:03] <ScottK> yuriy: You can find the bzr branchs at https://code.launchpad.net/{sourcepackage}
[17:04] <ScottK> It'll be the ~kubuntu-members branch
[17:04] <ScottK> If you go to the branch page, e.g. https://code.launchpad.net/~kubuntu-members/kdelibs/ubuntu it'll give you the bzr command to pull a branch.
[17:05] <ScottK> bzr branch lp:~kubuntu-members/kdelibs/ubuntu
[17:05] <ScottK> It's just copy/paste.
[17:05] <ScottK> There are tools to make it easy to build the package straight from that.  I don't use them.
[17:06] <ScottK> Personally, I use diff and patch to update the source package from bzr and the reverse.  This is, no doubt, the hard way to do it.
[17:06] <ScottK> Once you have your bzr branch updated, you do bzr ci -m "useful commit message here", and then push the branch.
[17:07] <ScottK> The branch page gives you the push command, but if you are just pushing it back where you got it, you can just use bzr push :parent.
[17:07] <yuriy> yeah i know how to use bzr. it's those tools i'm wondering about so i dont' have to copy/paste/patch manually
[17:07] <ScottK> OK.
[17:07] <ScottK> I think bzr-buildpackage or bzr-builddeb.
[17:07] <ScottK> apachelogger would know.
[17:08] <yuriy> hmm kpackagekit notifications need to go away when you upgrade using aptitude
[17:12] <a|wen> yuriy: bzr-buildpackage should be the one you want afaik ... and debcommit for committing the changes
[17:20] <apachelogger> a|wen is right
[17:20] <apachelogger> though you can also use bzr builddeb
[17:20] <apachelogger> also take note of the debcommit arguments ;)
[17:21] <apachelogger> fabo: where would I commit in debian SVN? trunk?
[17:21] <apachelogger> Nightrose: I have all sorts of logos of any project I am working on :P
[17:22] <Nightrose> apachelogger: ;-) all fixed in about a minute hopefully
[17:31] <Nightrose> Riddell: kubuntu account on identi.ca now has an avatar
[17:31] <Nightrose> looks way less meh ;-)
[17:33]  * apachelogger agrees
[19:13] <yuriy> nixternal: you did the report bug apport stuff?
[19:14] <yuriy> finally got to trying it, and it tries to report against kdelibs in any application
[19:15] <ScottK> apachelogger: Talk to me about this embedded code copy from kipi-plugins.  Why do I think that's OK?
[19:18] <nixternal> yuriy: which application?
[19:18] <yuriy> nixternal: i tried konsole and konqueror
[19:18]  * nixternal thinks the issues we are seeing is because we are using PID and not Program Name
[19:19] <yuriy> haven't tried actually submitting, but window title says kdelibs-bin, source package kdelibs, package kdelibs-bin, and executable path /usr/bin/kdeinit4
[19:19] <yuriy> maybe you need to parse what kdeinit is actually starting there?
[19:20] <nixternal> hrmm, that is weird..just tried it in konqi and it did it
[19:22] <yuriy> nixternal: if i start the app from the command line, it works correctly
[19:22] <nixternal> if you look at procstatus in apport, it is correct, but the rest is wrong :/
[19:23] <yuriy> also the progress bar on collecting information doesn't show any progress
[19:23] <yuriy> yes procstatus seems correct
[19:23] <nixternal> even if I do it via cli I get the same
[19:23] <ScottK> yuriy: kamosa (it's in New)
[19:23] <ScottK> Nevermind.
[19:23] <ScottK> Misread the scrollback
[19:25] <nixternal> even apport-cli is wrong
[19:30] <apachelogger> ScottK: barable for now
[19:30] <apachelogger> not ok
[19:30] <ScottK> apachelogger: You going to fix it before release?
[19:31] <apachelogger> I hope upstream does
[19:31] <apachelogger> otherwise I will probably jump in
[19:31] <ScottK> Does upstream feel more motivated if I say it doesn't get into Kubuntu with a code copy?
[19:31] <apachelogger> shouldn't be too difficult, I suppose they are plugins after all :D
[19:31] <yuriy> nixternal: where is the patch that changes that menu item?
[19:31] <yuriy> need to make sure it's not applied for jaunty, but i didn't see anything in kdelibs there
[19:32] <yuriy> bug 400209
[19:32] <nixternal> kdelibs
[19:32] <nixternal> kubuntu_50
[19:32] <apachelogger> ScottK: doubt it, though I could claim that it will get removed before release :P
[19:32] <apachelogger> getting dropped is worse than not getting in
[19:32] <ScottK> apachelogger: Well I can make that happen.  It wouldn't just be a claim.
[19:32] <nixternal> it shouldn't be in jaunty unless someone backported the patch
[19:32] <apachelogger> also makes it more urgent IMHO
[19:32] <apachelogger> ScottK: well, Id fix it though :P
[19:34] <ScottK> OK.  I think I can live with the rest.
[19:34] <apachelogger> anyway, it is not particularly evil since that stuff is almost impossible to abuse security wise
[19:34] <ScottK> (run lintian i the binaries and then work out what to do please)
[19:36]  * ScottK holds his nose and accepts.
[19:38] <yuriy> oh right i looked for the patch in kdebase. d'oh.
[19:38] <yuriy> nixternal: jaunty package has kubuntu_51
[19:38] <apachelogger> ScottK: lol
[19:38]  * apachelogger made a codeswarm of kubuntu bzr branches
[19:39] <ScottK> Can see plz?
[19:39] <apachelogger> poking kamoso upstream first
[19:40] <yuriy> nixternal: though that patch seems to disable the item altogether
[19:44] <ScottK> apachelogger: OK.  You got two bugs.  I added extra humour to the title of the second one, just for you.
[19:46] <apachelogger> uh
[19:46] <apachelogger> already triaged
[19:46] <apachelogger> nice
[19:47] <apachelogger> ScottK: want lintian overrides for the lib?
[19:48] <ScottK> apachelogger: It's meant to be a private lib, right?
[19:48] <ScottK> I vaguely recall something about shoving those out of the path somehow.
[19:50] <apachelogger> well, amarok's libamarok is also kinda private :P
[19:51] <apachelogger> seems to be common practise to have any lib other than plugins in prefix/lib/
[19:51] <apachelogger> kcms and real pluings go prefix/lib/kde4/ afaik
[19:54] <apachelogger> ScottK: http://aplg.kollide.net/kubuntu/swarm-09-09-12.avi
[19:54] <ScottK> apachelogger: OK.  Either fix it or override as you think best.
[19:55]  * apachelogger checks the kde cmake macros before override
[19:58]  * apachelogger finds it quite funny that one exactly sees when apachelogger went low profile in the swarm
[20:01] <apachelogger> ScottK: needs override, only shared or static libs are allowed to be linked into another target (i.e. the kamoso bin)
[20:01] <ScottK> OK
[20:01] <apachelogger> so same situation as with amarok and friends, just that amarok got a proper soname
[20:07] <apachelogger> ScottK: why do we even care about the kipi plugin?
[20:07] <ScottK> Code duplication is bad.
[20:07] <apachelogger> well, yeah
[20:08] <apachelogger> but we are not the police :P
[20:08] <apachelogger> anyway
[20:08] <ScottK> Since I'm the archive admin, I am the police.
[20:08] <apachelogger> the kipi API doesn't fit their needs
[20:08] <apachelogger> so they duplicate the backend code and stack their own API ontop of that
[20:09] <ScottK> Sounds weak.
[20:09] <apachelogger> well
[20:09] <apachelogger> kipi plugins aint are no shared lib
[20:10] <apachelogger> so they could not even stack a reimplementation ontop of the base classes
[20:10] <ScottK> OK.  Some maybe we ask Lure_ what he thinks.
[20:11] <apachelogger> ScottK: upstream suggests that the only solution would be to have the facebook backend turned into a shared lib
[20:11] <apachelogger> which of course goes with major refactoring et all
[20:11] <ScottK> Right.
[20:11] <ScottK> I'm curious what Lure_ has to say then.
[20:12]  * apachelogger pokes Lure_ into saying something :P
[20:13] <ScottK> We have some time to decide what to do about it.
[20:15] <apachelogger> well, since only facebook is affected we might drop that
[20:15] <apachelogger> Riddell might not like that though :P
[20:16] <ScottK> I heard a funny facebook story on the radio today.
[20:16] <ScottK> Two girls (iirc aged 11 and 12) got lost exploring the storm drains in Adelaide, AU.
[20:17] <ScottK> They had a cel phone with them, so they (obviously) updated their facebook status and waited for someone to send help.
[20:17] <ScottK> It didn't occur to them they could just call.
[20:17] <apachelogger> ROFL
[20:17] <ScottK> They waited 7 hours.
[20:17] <apachelogger> facebook ftw!
[20:17] <spstarr> second life ftw! :)
[20:18] <apachelogger> got a second life mail today
[20:18] <apachelogger> made me realize that sl is so 90's
[20:19]  * apachelogger is wondering why lp:ubuntu/karmic/amarok is so darn big
[20:19] <apachelogger> are those full source branches?
[20:19] <apachelogger> ScottK: thinking about it, though probably should have tweeted
[20:20] <apachelogger> much more public, so someone would have sent help earlier
[20:20] <ScottK> No doubt.
[20:20] <ScottK> At least it wasn't myspace.  They'd have starved.
[20:20] <apachelogger> *nod*
[20:20]  * apachelogger needs to update his ohloh profile
[20:21] <apachelogger> that bzr branch takes ages
[20:21] <ScottK> apachelogger: That or apply some of your godlike powers to fix http://revu.ubuntuwire.com/p/searchandrescue
[20:21] <apachelogger> would give better history for the swarm though
[20:21] <apachelogger> booohooo
[20:21] <apachelogger> C
[20:22] <ScottK> Yeah.
[20:22]  * ScottK doesn't do C.
[20:22] <apachelogger> I'd rather continue hacking away with java on my android :P
[20:22] <ScottK> nor C++ for that matter.
[20:22] <ScottK> Ouch
[20:22] <apachelogger> I'd rather reimplement all my ruby magic in python
[20:22] <apachelogger> or port dpkg to python
[20:23] <apachelogger> actually the latter might make sense for ubuntu :P
[20:23] <apachelogger> srsly, one day mvo will reimplement dpkg
[20:23] <apachelogger> he's a machine
[20:27]  * yuriy hopes ubuntu doesn't go reimplementing C things in python
[20:27] <apachelogger> with the amount of money spent on disk space for the ubuntu bzr branches one could probably finance the whole kubuntu team
[20:27] <apachelogger> amarok branching at 270MiB
[20:28] <ScottK> What's that cost?  a quarter Euro?
[20:28] <apachelogger> well
[20:29] <apachelogger> ScottK: *20000packages*6release
[20:29] <ScottK> shtylman: Any good ideas yet on the 480 pixel display height problem (even something ugly, but workable)?
[20:29] <ScottK> Right, well that does add up after a while.
[20:29] <apachelogger> 330MiB... still counting
[20:31] <apachelogger> just imagine kdebase-workspace :S
[20:31] <apachelogger> or openoffice
[20:31] <apachelogger> oh dear, openoffice
[20:31] <apachelogger> must take one week to branch :P
[20:32] <apachelogger> 400
[20:34] <apachelogger> ScottK: lintian overrides for kamoso pushed to bzr branch
[20:37] <apachelogger> https://code.launchpad.net/~ubuntu-branches/ubuntu/karmic/amarok/karmic
[20:37] <apachelogger> 97 commits yet 510MiB
[20:47] <yuriy> ok this AJAXy stuff on LP is annoying
[20:48] <yuriy> clicking on the status changes it to won't fix
[20:48] <apachelogger> doesn't work half the time for me
[20:48] <apachelogger> yuriy: bug with konqueror
[20:49] <ScottK> Half the time I click it and it 'works', but not with the change I intended.
[20:50] <apachelogger> hehe
[20:50] <yuriy> but most of the time i want to leave a comment with the status change, so I don't think it's a useful feature anyway, it just gets in the way
[20:50] <Lure_> ScottK. apachelogger: you rang, my lord?
[20:50] <apachelogger> ScottK can explain
[20:50] <apachelogger> gotta take care of something
[20:51] <ScottK> Lure_: We have this new package called kamosa that has a code copy of the facebook plugin from kipi-plugins.
[20:51] <ScottK> Kamosa upstream says "they didn't like the API" or something so they added their own on top.
[20:51] <Lure_> ScottK: nice ;-)
[20:52] <Lure_> ScottK: which api?
[20:52] <ScottK> So I was wondering if there was some way we could make it so they could use the one from kipi-plugins and not ship a copy?
[20:52]  * Lure_ searches to see what kamosa is
[20:52] <shtylman> ScottK: yea... I have an idea but I havn't been able to do it yet...the idea is to have two style files select between them depending on the resolution
[20:52] <shtylman> the style file for smaller displays would probly just use smaller fonts
[20:52] <ScottK> Lure_: You've now exhausted my knowledge on the subject.
[20:53] <shtylman> cause that is really the biggest thing making the display grow past 480px vertically
[20:53] <ScottK> shtylman: That'd be really cool if we could get it.  That'd let us hit larger MID devices too.
[20:53] <Lure_> ScottK: facebook specific code in kipi-plugins is not wrapped in real api, but there is a class to talk with facbook
[20:53] <Lure_> you could call it API, but it is very photo focused
[20:53] <shtylman> I would say that we do need to maybe draw the line at some point for this release but for next release I could see about handling different resolutions/mid devices or maybe even a different form factor for MID devices and untra low res
[20:55] <Lure_> ScottK: where is this kamosa package?
[20:58] <yuriy> hmm can't remember my kde forums username.. I *think* i registered when they first started it
[21:03] <Lure_> btw, did something change with login splash lately? I use auto-login and now it flashes for several seconds during login... ugly...
[21:03] <Lure_> before I just got my locked session (password to unlock dialog)
[21:03] <yuriy> Lure_: maybe xksplashx? Riddell is that in?
[21:04] <Lure_> yuriy: what is that?
[21:04] <shtylman> ScottK: maybe something to discuss at uds? :)
[21:07] <ScottK> shtylman: I was sort of hoping you could sneak it in still, but OK.
[21:07] <yuriy> Lure_: a splash screen when kdm loads. if you have autologin on, it should theoretically take you from X starting to a full desktop
[21:07] <ScottK> Lure_: Just accepted into Karmic, so it may not be on your local mirror yet.
[21:08] <shtylman> ScottK: I can probly sneak in the different stylesheet, but I was referring to the support for even smaller resolutions
[21:08] <Lure_> yuriy: before, I did not see any splash during auto-login, now I get splash and it seems it gets constantly replaced with black screen, therefore flashung...
[21:08] <yuriy> Lure_: that's probably it then, and buggy
[21:08] <ScottK> shtylman: OK.  Sounds good then.
[21:08] <Lure_> yuriy: to which package should I report the problem?
[21:09] <yuriy> dunno. maybe kdm
[21:09]  * Lure_ also hopes that somebody looks into bug 405378
[21:10] <yuriy> me too, that one's important
[21:10]  * yuriy checked out apport source and got distracted
[21:10] <ScottK> It works here (using apport-cli)
[21:11] <Lure_> ScottK: it fails with apport-kde
[21:11] <Lure_> ScottK: and this is the default called by crash manager
[21:12] <ScottK> Ah.
[21:12] <ScottK> Lure_: I misspelled it.  It's Kamoso
[21:16] <Lure_> yuriy: submitted bug 428579 - it seems it was Riddell causing this flashes to me ;-)
[21:42] <Lure> ScottK, apachelogger: it seems kamoso copied as-is half of kipi plugin :-(
[21:42] <Lure> I can understad why, as they do not need UI complexity of KIPI
[21:43] <Lure> I think it is something to discuss with other kipi developers
[21:43] <Lure> but nothing much we can do now I think
[21:43] <ScottK> OK.  Well some longer term solution is needed.
[21:44] <ScottK> Thanks for looking into it.
[21:47] <ScottK> apachelogger: Accepted the binaries for Kamoso too.
[21:48] <Lure> ScottK: I plan to attend digikam/kipi developer gathering in Nov and we plan to redesign import/export plugins, so we can try to take kamoso needs into account
[21:48] <Lure> ScottK: will talk with Kamoso developer
[21:48] <Lure> ScottK: thanks for letting me know about code duplication
[21:48] <ScottK> Lure: Excellent.  I know apachelogger has talked to them some.
[21:49] <Lure> ScottK: yep, we need to make it more kde-like (libraries/plugins -> reuse)
[21:50] <Lure> ScottK: do I need FFe for beta3->beta4 upload (digikam)
[21:50] <ScottK> Feature changes or just bug fixes?
[21:50] <Lure> ScottK: we expect to have final release ready just in time for karmic
[21:50] <Lure> ScottK: both
[21:51] <Lure> ScottK: but having old beta does not make sense at all
[21:51] <ScottK> Then yes.  I'd file one FFe for all the updates to final.
[21:51] <ScottK> You need to ask, but I'd imagine the answer is yes (since it's in Main, subscribe ubuntu-release)
[21:51] <Lure> ScottK: ok, so FFe and request approval for all versions up to final
[21:51] <ScottK> Something like that.
[21:51] <Lure> ScottK: thanks, will do
[22:05] <Czessi> Hi, in karmic python-qt4-common is missing and i think this is the problem why the gmail plasmoid is not runnig. is there an alternate package available?
[22:09] <NCommander> Czessi, we should have python-qt4-common available
[22:09] <NCommander> (I'm one of the Debian maintainers of this package)
[22:10] <ScottK> NCommander: rmadison says we don't.
[22:11] <Czessi> http://packages.ubuntu.com/python-qt4-common
[22:11] <NCommander> correction, no,its gone in Debian and Ubuntu
[22:11] <ScottK> NCommander: I read some bug it seems like it's not getting removed on upgrade.
[22:12]  * ScottK wonders if some conflicts/replaces is missing.
[22:12] <NCommander> ScottK, bah, I fixed that in Debian, the version in ubuntu must never have gotten merged
[22:12] <NCommander> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536595
[22:12] <ScottK> NCommander: Please fix.
[22:15] <NCommander> ScottK, where's our python-qt4 bzr branch?
[22:15] <ScottK> I don't think we have one.
[22:15]  * ScottK looks
[22:16] <ScottK> Nope
[22:16] <ScottK> NCommander: We mostly just put the core KDE stuff in bzr.
[22:17] <NCommander> ScottK, can you find the bug number for me :-)
[22:17] <ScottK> Sure
[22:19] <ScottK> NCommander: Bug #407418
[22:19] <NCommander> ScottK, python-qt4-common has NBS'ed out, I think I just need a conflicts, no replaces
[22:19] <ScottK> NCommander: For upgraders is needs replaces.
[22:19] <NCommander> Then why'd Debian only run w/ Replaces
[22:20] <NCommander> (I didn't make that specific change when I looked at the changelog)
[22:20] <ScottK> Out of the archive doesn't also mean off someone's hard drive.
[22:20] <NCommander> ScottK, if its just a Conflicts and there are no rdepends, dpkg will remove it
[22:21] <ScottK> You sure?
[22:21] <NCommander> Replaces is only if you have a true super-set, theres an ABI break between common and mainline
[22:21] <NCommander> Fairly
[22:21] <ScottK> OK.
[22:21] <NCommander> I can stage an upgrade from jaunty in a VM to confirm/deny this theory
[22:21] <ScottK> That'd be handy.  It'd getting late in the game to be wrong.
[22:22] <NCommander> Replaces: python-qt4-dev (<< 4.4.4-3~), python-qt4-common
[22:22] <NCommander> *sigh*
[22:22]  * NCommander whacks Riddell hard
[22:22] <NCommander> bbiab, fire alarm
[22:57] <dtchen> yesterday's upgrade of amarok required a kde session logout-login cycle. i was bitten by a bug where starting the upgraded amarok was unable to display the playlist.
[23:19] <yuriy> nixternal: apport-kde is copyright canonical? didn't you write it?
[23:24] <yuriy> nixternal, Lure: I think the issue (bug 405378) may have something to do with the full/reduced report radio buttons not being there
[23:28] <Lure> yuriy: I suspect they require copyright assignment
[23:28]  * Lure checks and compare with apport-gtk
[23:30] <yuriy> don't understand why it hangs, but the radio buttons certainly have something to do with it