[08:45] <lordievader> Good morning.
[11:40] <kdeuser56> shadeslayer: https://bugs.kde.org/show_bug.cgi?id=333360
[11:57] <ovidiu-florin> apachelogger: I guess we won't
[11:58] <ovidiu-florin> Riddell jose I've requeste al lthe files that give the current kubuntu website
[11:58] <ovidiu-florin> all I received were a bunch of pictures?
[11:58] <ovidiu-florin> sorry, no "?"
[11:59] <ovidiu-florin> I can't do the migration like this
[11:59] <ovidiu-florin> are the canonical sysadmins simply dumb?
[11:59] <ovidiu-florin> I asked for all that files
[11:59] <ovidiu-florin> what does all mean to them?
[11:59] <ovidiu-florin> pictures?
[12:17] <ovidiu-florin> jose: I'm very upset on this matter, can you please help me solve this?
[13:29] <BluesKaj> "Morning all
[13:39] <jose> ovidiu-florin: you requested a DB dump and I requested the files. The DB dump has been sent to you, and all the files have been put on a tarball and uploaded to my home folder in docs.kubuntu.org
[13:39] <jose> ovidiu-florin: if you have trouble locating them, create a folder with 775 access and I'll move them over there
[13:39] <jose> (well, not move, copy)
[13:40] <jose> sorry I didn't answer immediately, but I was asleep
[13:46] <jose> hello, BluesKaj :) how's it going?
[13:46] <jose> Riddell: I'll try to work out the problem, but I'm not pretty sure of what ovidiu exactly wants
[13:47] <BluesKaj> Hi  jose
[13:47] <BluesKaj> fine here and you?
[13:53] <jose> I'm good, just woken up and looks like it's going to be a good day :)
[14:07] <kdeuser56> anyone familiar with kernel compiling? :-(
[14:30] <ovidiu-florin> jose: I have access to your home folder on that server
[14:30] <ovidiu-florin> jose: please open that archive and look in it
[14:30] <ovidiu-florin> there are only pictures in there
[14:30] <jose> ovidiu-florin: those are *all* the files that were on the instance, what kind of files were you expecting?
[14:31] <ovidiu-florin> php files
[14:31] <ovidiu-florin> not pictures
[14:31] <ovidiu-florin> the drupal instance
[14:31] <jose> you mean, the contents of each page?
[14:31] <ovidiu-florin> no, that's in the DB
[14:31] <ovidiu-florin> I mean the Drupal instance
[14:32] <jose> may I ask why you need that?
[14:32] <ovidiu-florin> to migrate the site 
[14:32] <jose> we *could* technically get it, but it would have to go through a lot of security checks, and I really find it unpractical to do it
[14:32] <jose> can't you download drupal and deploy it and link to the DB you have
[14:33] <jose> also, I thought we were moving to Wordpress
[14:33] <ovidiu-florin> if we could
[14:33] <ovidiu-florin> in order to migrate I need access to eighter that drupal instance
[14:33] <ovidiu-florin> or to a copy of it
[14:33] <ovidiu-florin> I went for the copy ption
[14:33] <ovidiu-florin> opion
[14:34] <ovidiu-florin> option*
[14:34] <jose> ovidiu-florin: is there a chance we can have a google+ hangout to discuss it?
[14:34] <ovidiu-florin> The only security problem would be the DB connection details
[14:34] <ovidiu-florin> jose: now?
[14:34] <jose> yes, it'd be easier for me
[14:34] <ovidiu-florin> sure
[14:34] <jose> (if you want, of course)
[14:35] <ovidiu-florin> jose: https://plus.google.com/+OvidiuFlorinBogdan/posts
[16:29] <shadeslayer> kdeuser56: hi
[16:29] <shadeslayer> kdeuser56: that bug is invalid fwiw :P
[16:29] <shadeslayer> it should be filed in launchpad
[16:29] <shadeslayer> against software-properties
[16:30] <kdeuser56> shadeslayer: hi, I wanted to do so, but Scott recommended to file it on kde-bugs :-(
[16:30] <shadeslayer> kdeuser56: https://bugs.launchpad.net/ubuntu/+source/software-properties/+filebug
[16:32] <kdeuser56> shadeslayer: could you answer me a little question?
[16:32] <shadeslayer> sure
[16:33] <shadeslayer> I also might have a patch for that
[16:33] <kdeuser56> shadeslayer: is https://github.com/torvalds/linux what will become 3.15?
[16:33] <shadeslayer> looks quite alot like the sip destroy on exit bug
[16:33] <shadeslayer> kdeuser56: dunno, I'd hazard a guess at yes
[16:34] <kdeuser56> shadeslayer: why can't gdb handle the  sip stuff?
[16:35] <kdeuser56> shadeslayer: I do not know what debug symbols to install ... I wrote a script to install all dbgsym for every installed package and it still prints ?? ... very strange
[16:38] <kdeuser56> shadeslayer: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1307170
[16:39] <kdeuser56> shadeslayer: my script revealed a bunch of intersting packaging problems: 
[16:39] <kdeuser56> shadeslayer: marble-plugins-dbgsym installs marble-dbg which installs marble 
[16:41] <shadeslayer> I am not informed enough on sip stuff :)
[16:41] <shadeslayer> kdeuser56: and I don't see a problem marble-dbg installing marble
[16:41] <shadeslayer> I think it's a recommends, that you could turn off
[16:42] <kdeuser56> shadeslayer: no I do not think it's a recommend, because if I uninstall marble marble-dbg will also be removed
[16:42] <shadeslayer> I don't see how the plugins-dbg package will be useful without marble
[16:43] <kdeuser56> shadeslayer: the situation is the following: by default we do not have marble installed, but marble-plugins
[16:44] <kdeuser56> shadeslayer: now I want to install the -dbgsym for that ... I am not interested in installing marble
[16:45] <shadeslayer> bbiab, meeting time
[16:45] <kdeuser56> okay, can we continue, when you are back?
[16:51] <shadeslayer> kdeuser56: http://paste.kde.org/pthdgy7os
[16:51] <shadeslayer> kdeuser56: can you try that patch to software-properties-kde
[16:51] <shadeslayer> and see if you can reproduce the crash
[16:52] <kdeuser56> shadeslayer: meeting time over? yeah wait I'll reboot in a minute
[16:52] <shadeslayer> not reall
[16:52] <shadeslayer> multitasking :)
[16:53] <shadeslayer> *really
[16:53] <kdeuser56> shadeslayer: can we talk about my package questions later?
[16:53] <shadeslayer> sure
[16:53] <kdeuser56> thanks
[17:00] <kdeuser56> shadeslayer: could you relink ^^ stupid me
[17:02] <kdeuser56> shadeslayer: the patch
[17:07] <shadeslayer> kdeuser56: http://paste.kde.org/pthdgy7os
[17:08] <soee_> there is small issue with updates notification, if we run muon and do Check updates and some are found - we have notification. Than if we apply them and it is finished second notification show sup (with info what we have updates)
[17:09] <shadeslayer> soee_: known issue
[17:09] <shadeslayer> I'll have a looky with apol today
[17:09] <soee_> shadeslayer: ok :)
[17:27] <kdeuser56> shadeslayer: after applying your patch when going to "configure software sources" muon only updates software sources and return to normal view ...
[17:27] <kdeuser56> shadeslayer: it seems  "configure software sources" turned to a tigger for "apt-get update" 
[17:27] <kdeuser56> shadeslayer: had a similar issue after upgrading last time though ...
[17:28] <kdeuser56> shadeslayer: i have rebooted but the behavior does not change :-(
[17:31] <kdeuser56> shadeslayer: what i did: apt-get source software-properties-kde then apt-get build-dep software-properties-kde then applied your patch change into the folder software-properties-kde<version number> and run dpkg-buildpackage -rfakeroot -b
[17:35] <shadeslayer> kdeuser56: yeah, should work I guess
[17:36] <kdeuser56> shadeslayer: but directly modifying /usr/bin/software-properties-kde should work too, right?
[17:39] <kdeuser56> shadeslayer: directly reverting your patch in /usr/bin/software-properties-kde makes muon work again
[17:40] <kdeuser56> shadeslayer: with your patch i get the following error when starting muon from command line: 
[17:40] <kdeuser56>   File "/usr/bin/software-properties-kde", line 55
[17:40] <kdeuser56>     _ = gettext.gettext
[17:40] <kdeuser56>                       ^
[17:40] <kdeuser56> IndentationError: unindent does not match any outer indentation level
[17:41] <shadeslayer> hm
[17:43] <kdeuser56> shadeslayer: please ping me when you have suggestions, otherwise I wont notice it
[17:43] <shadeslayer> kdeuser56: right, thinking
[17:44] <shadeslayer> kdeuser56: it works for me here
[17:44] <kdeuser56> shadeslayer: on trusty fully updated?
[17:44] <shadeslayer> yep
[17:44] <kdeuser56> wtf?
[17:45] <kdeuser56> shadeslayer: have you restarted muon?
[17:45] <kdeuser56> shadeslayer: and when restarting start from another terminal
[17:45] <shadeslayer> kdeuser56: yep
[17:46] <shadeslayer> kdeuser56: can you pastebin /usr/bin/software-properties-kde
[17:48] <kdeuser56> shadeslayer: http://paste.kde.org/p5pmhwmw8
[17:49] <shadeslayer> kdeuser56: try removing the except and try lines
[17:49] <shadeslayer> as well as the 'pass' line
[17:49] <shadeslayer> and re indent sip.setdestroyonexit
[17:49] <shadeslayer> make sure you're using spaces
[17:49] <shadeslayer> not tabs
[17:51] <kdeuser56> shadeslayer: so only sip.setdestroyonexit(False) should be left of your patch?
[17:52] <shadeslayer> kdeuser56: yes, and the import sip line
[17:53] <kdeuser56> shadeslayer: works now ... wait trying to get it crashing
[17:53] <shadeslayer> awesome
[17:55] <shadeslayer> soee_: oh, do you still have the notification icon?
[17:55]  * shadeslayer needs to trigger a package update somehow
[17:57] <shadeslayer> soee_: poke poke
[18:01] <shadeslayer> nvm
[18:20] <shadeslayer> ScottK: I have a fix for muon
[18:20] <shadeslayer> ScottK: can you approve if I upload?
[18:22] <kdeuser56> shadeslayer: could not trigger a crash until now
[18:22] <shadeslayer> hm
[18:22] <shadeslayer> kdeuser56: please keep using it
[18:22] <kdeuser56> shadeslayer: could however trigger crashes when removing your patch
[18:22] <shadeslayer> kdeuser56: oh
[18:22] <shadeslayer> another pyqt issue then :/
[18:23] <shadeslayer> kdeuser56: I'll push the fix to software-properties-kde
[18:23] <shadeslayer> thanks for reporting
[18:23] <kdeuser56> shadeslayer: why hm? i was not sucessful triggering a crash
[18:23] <kdeuser56> shadeslayer: your patch works no crashes, what issues are you talking about?
[18:24] <shadeslayer> kdeuser56: that's a good thing, but I'd rather not push such intrusive patches the week before release
[18:24] <shadeslayer> intrusive because it's a workaround for the actual issue
[18:24] <kdeuser56> shadeslayer: I can't however reliably reproduce the issue ...
[18:24] <kdeuser56> shadeslayer: it happens rather spontaneously, sometimes the first time you try sometimes the 5th time
[18:25] <shadeslayer> *nod*
[18:27] <shadeslayer> ScottK: uploaded
[18:28] <soee_> shadeslayer: in the systray ?
[18:28] <shadeslayer> soee_: yeah, nvm, I have a patch
[18:28] <soee_> ok, tha icon is here for me
[18:29] <shadeslayer> ScottK: http://launchpadlibrarian.net/172744572/muon_2.2.0-0ubuntu2_2.2.0-0ubuntu3.diff.gz
[18:29] <shadeslayer> soee_: ^^
[18:30] <soee_> shadeslayer: is it already in updates ?
[18:30] <shadeslayer> soee_: no
[18:30] <shadeslayer> waiting for approval
[18:30] <soee_> ok
[18:34] <kdeuser56> shadeslayer: plasma-dataengines-addons-dbgsym installs "plasma-runners-addons plasma-wallpapers-addons plasma-widget-lancelot kde-wallpapers"
[18:35] <kdeuser56> shadeslayer: it obviously install unnecessary stuff I do not need for debugging
[18:35] <kdeuser56> shadeslayer: kde-wallpapers? why? removing them will also remove the debug symbols
[18:38] <kdeuser56> shadeslayer: dbgsym are autogenerated right? where are the scripts? I want to have a look at them
[18:45] <shadeslayer> kdeuser56: https://code.launchpad.net/~rohangarg/software-properties/fix-for-1307170/+merge/215580
[18:45] <shadeslayer> plz comment
[18:46] <shadeslayer> kdeuser56: that's correct
[18:47] <kdeuser56> shadeslayer: that is the version I could not get working ... 
[18:47] <shadeslayer> kdeuser56: yeah, it works fine for me here, not sure why it wouldn't work on your system, but that code is required
[18:47] <kdeuser56> shadeslayer: then I will confirm it works in the hope that it will do ;-)
[18:48] <shadeslayer> kdeuser56: as for your dbg question, plasma-wallpapers-addons depends on kde-wallpapers
[18:49] <shadeslayer> and the dbg package depends on the plasma-wallpapers-addons
[18:49] <shadeslayer> and probably the dbgsym package depends on the dbg package
[18:50] <kdeuser56> shadeslayer: no it installs exactly plasma-runners-addons plasma-wallpapers-addons plasma-widget-lancelot and kde-wallpapers
[18:51] <shadeslayer> read my reply again
[18:51] <shadeslayer> there's a dep chain
[18:51] <kdeuser56> shadeslayer: I do not want the wallpaper addons either 
[18:51] <shadeslayer> kdeuser56: too late for trusty I'm afraid
[18:52] <kdeuser56> shadeslayer: no problem I can manually edit the dpkg status file so that it works ;-), but could you solve the issue?
[18:52] <shadeslayer> heh
[18:53] <kdeuser56> shadeslayer: do you agree that is a packaging bug? 
[18:53] <shadeslayer> well
[18:53] <shadeslayer> I'd say that depends might be too strict
[18:53] <shadeslayer> yes
[18:53] <shadeslayer> kdeuser56: please report a bug in Debian
[18:53] <shadeslayer> http://anonscm.debian.org/gitweb/?p=pkg-kde/kde-sc/kdeplasma-addons.git;a=blob;f=debian/control;h=84233e03c228aa990655ed6993886128b853c48f;hb=HEAD#l229
[18:54] <shadeslayer> ^^ same issue in Debian
[18:54] <kdeuser56>  shadeslayer: I thought dbgsym packages are specific to ubuntu?
[18:54] <shadeslayer> I don't think this is a dbgsym package issue
[18:55] <shadeslayer> kdeuser56: what does apt-cache depends plasma-dataengines-addons-dbgsym  say
[18:55] <shadeslayer> my (calculated) guess is that it depends on kdeplasma-addons-dbg
[18:56] <kdeuser56> shadeslayer: your guess is right ^^
[18:56] <shadeslayer> kdeuser56: right, so it's dragged in by kdeplasma-addons-dbg and the dbgsym package probably doesn't directly depend on kde-wallpapers
[18:59] <kdeuser56> shadeslayer: why does the dbgsym depend on kdeplasma-addons-dbg anyway? I thought they could exist independent from -dbg?
[19:00] <shadeslayer> kdeuser56: they can be co installed, but not sure if you can uncouple them
[19:00] <shadeslayer> because dh_shlibs adds the deps IIRC
[19:00] <kdeuser56> shadeslayer: in the wiki says dbg and dbgsym of the same package should conflict ...
[19:02] <kdeuser56> shadeslayer: does not happen for all packages however ... muon-dbg and muon-dbgsym are coinstallable
[19:02] <kdeuser56> shadeslayer: somehow the whole -dbgsym / -dbg situation seems really messy 
[19:02] <kdeuser56> shadeslayer: normally they should both include similar files and should conflict ... 
[19:04] <shadeslayer> it is weird
[19:04] <kdeuser56> shadeslayer: all that problems with unnecessary stuff being pulled in is true for dbgsym packages that want to install dbg packages
[19:04] <shadeslayer> you'll need someone who knows more about the dbgsym packages, try #ubuntu-devel
[19:05] <kdeuser56> shadeslayer: I will consult with pitti maybe in the next days, he should know that, shoudln't he?
[19:05] <shadeslayer> dunno
[19:05] <shadeslayer> I'd ask generally in #ubuntu-devel
[19:05] <kdeuser56> shadeslayer: yeah I will do that ... first try would be to find out why some dbgsym install dbg stuff ...
[19:06] <apol> shadeslayer: https://bugs.kde.org/show_bug.cgi?id=333291
[19:06] <kdeuser56> shadeslayer: thanks for your enormous help! kudos!
[19:42] <shadeslayer> kdeuser56: np
[20:19] <Quintasan> upgrading to trusty on my machine
[20:20] <Quintasan> the virtual machines upgraded fine so it should work here too
[21:17] <Quintasan> Upgrade successful
[21:26] <soee__> :D
[21:39] <shadeslayer> mmm
[21:39] <shadeslayer> more kamoso issues kamoso(11767)/KIPI (loading) KIPI::PluginLoader::init: Plugin  "YouTube" has a SO version ( 0 ) which is different than libkipi ABI version ( 11 ).  Refusing to load.
[21:56] <vgezer> I just checked the daily iso, but it seems in the second step Turkish characters are seen strange: http://i.imgur.com/d4Kr6di.png
[21:59] <ScottK> shadeslayer: Thanks for the quick fix on Muon.
[22:01] <vgezer> can someone reproduce it in another languages?
[22:04] <Riddell> ook
[22:06] <Riddell> hi all, what's the craic?
[22:06] <apachelogger> what's a craic?
[22:06] <Riddell> yo dudes, what's going down?
[22:06] <Riddell> that easier to understand?
[22:07] <apachelogger> reckon
[22:07] <apachelogger> not that it sounds any better though
[22:07] <apachelogger> I hear stuff was broken in the muonesque department again
[22:08] <apachelogger> also I have a mail in my inbox titled "will pam-kwallet work in debian?"
[22:08] <apachelogger> Riddell: how was the boat thing of yours?
[22:09] <ScottK> apachelogger: shadeslayer did an upload he claims fixed the muon issue.  Still have software-properties stuffs though.
[22:10] <Riddell> boat thing was great, got a nice certificate for open canadians
[22:12] <soee__> guys do you have strange behaviour with batery indicator/applet ?
[22:12] <apachelogger> I have no idea what it means but sounds neat ^^
[22:14] <soee__> this is what i have: http://wstaw.org/m/2014/04/14/batery_monitor.jpeg :D
[22:16] <apachelogger> this is the new multi dimensional text mode
[22:17] <apachelogger> it's made for the wicked mind
[22:17] <apachelogger> soee__: bugs.kde.org
[22:17] <apachelogger> plasma apparently tries to textwrap because the translation is too long
[22:17] <apachelogger> alas, it does not adjust the actual element size, so qt just mushes the text together I reckon
[22:17] <soee__> apachelogger: there are 2 separate labels i think
[22:18] <apachelogger> ah, not that then
[22:18] <apachelogger> still a plasma bug
[22:18] <soee__> Battery monitor and Screen brightness
[22:18] <apachelogger> perhaps one of the two uses too big an icon
[22:18] <apachelogger> I see there is a screen that appears to be too big
[22:18] <apachelogger> looks 32x32, while it should be 16x16, so maybe it's a plasmoid bug
[22:19] <apachelogger> still wouldn't explain why two labels are on top of one another though
[22:19] <apachelogger> plasma layouting works in mysterious ways some times
[22:19] <soee__> if i turn off battery minitor all thi sis gone
[22:19] <apachelogger> soee__: well, file a bug
[22:19] <apachelogger> I can do bug guessing all day :P
[22:20] <soee__> ok will test a bit more and report than
[22:20] <vgezer> apachelogger Riddell what do you think we should do about this?
[22:20] <vgezer> > I just checked the daily iso, but it seems in the second step Turkish characters are seen strange: http://i.imgur.com/d4Kr6di.png
[22:20] <apachelogger> it could also be that they are making love to each other
[22:20] <apachelogger> who knows
[22:21] <apachelogger> kinky plasmoids, that's totally a thing
[22:21] <apachelogger> vgezer: bugs.launchpad.net/ubuntu 
[22:23] <apachelogger> it could be a) ubiquity-kde somehow turning the string into ISO encoding when it should be utf8 b) ubiquity-common doing that c) ubiquity-common reading the string in a bogus way d) the string somehow having been translated such that it either is incorrectly encoded or broken to begin with
[22:23] <apachelogger> something wrong with the translation seems most likely though, since it is contained to two lines
[22:24] <apachelogger> (random note: ubiquity is not translated into klingon :'<)
[22:25] <vgezer> i checked the strings on launchpad, but it seems it is translated correctly and hasn't changed since 2011
[22:25] <apachelogger> https://translations.launchpad.net/ubuntu/trusty/+source/ubiquity/+pots/ubiquity-debconf/tr/193/+translate
[22:25] <vgezer> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1299881
[22:26] <vgezer> yes, i resent the same string again.
[22:26] <vgezer> aah this one
[22:26] <apachelogger> maybe check the po file in the source
[22:27] <apachelogger> perhaps the export is broken
[22:27] <vgezer> but this is also new, though.
[22:27] <apachelogger> vgezer: well, not that new
[22:27] <vgezer> do you think sending this again can solve it, maybe?
[22:28] <apachelogger> no
[22:31] <vgezer> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/ubiquity/trusty/files
[22:31] <apachelogger> well, I do not have the slightest idea where exactly the pos are for that thing
[22:31] <vgezer> it redirects me here and there are only three strings in po file :)
[22:31] <vgezer> ahh ok, thanks :)
[22:31] <apachelogger> it may be in a language pack
[22:31] <apachelogger> who knows
[22:32] <apachelogger> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/ubiquity/trusty/view/head:/debian/real-po/tr.po
[22:32] <vgezer> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/ubiquity/trusty/view/head:/debian/real-po/tr.po#L1412
[22:32] <vgezer> haha, at the same time :)
[22:33] <vgezer> it seems the string is exported correct it seems
[22:33] <apachelogger> yes
[22:33] <apachelogger> so one can assume it is also compiled correctly
[22:33] <apachelogger> which leaves the possible problems in ubiquity's code
[22:34] <apachelogger> though I fail to see how the best results line woudl be any differently processed from the other ones
[22:35] <apachelogger> the header I could imagine the s/RELEASE/Kubuntu/ thing perhaps having an encoding problem, but the other line... makes no sense at all
[22:35] <apachelogger> anyway
[22:35]  * apachelogger is off to bed
[22:36] <vgezer> i see. i reopened the issue
[22:36] <vgezer> thanks a lot. let's see. but its too bad that will happen for LTS :/
[22:36] <vgezer> because it was ok for 13.10
[22:39] <vgezer> good night.