[00:05] <rosco_y> what's the easiest way to insall the latest version of adobe flash-player in 12.04 LTS?
[00:06] <rosco_y> I just recently installed some recommended upgrades, and now websites are complaining that I don't have the flaash-player plugin
[00:15] <genii> rosco_y: If you put in URL bar of browser:   about:plugins     ...what version does it say you have?
[00:19] <genii> ( because 11.2 is the last version Adobe released for Linux, but some websites want a later version, which is for Windows. The only later version than 11.2 which is for Linux is hardcoded into the Chrome browser)
[00:26] <rosco_y> genii: I'm surprised, because there isn't any flash-player plugins listed at all when I followed your "about:plugins" recommendation
[00:27] <genii> rosco_y: Perhaps then to install package kubuntu-restricted-extras
[00:27] <genii> That will pull in the flash player
[00:28] <rosco_y> genii: , thank you :)
[00:29] <genii> rosco_y: You're welcome
[05:43] <rosco_y> can I install 13.04 alongside my 12.04, so that I can choose which one I want to boot?
[06:47] <SorenHolm> Hi
[06:48] <SorenHolm> How does KDE figure out the system capabillities in relation to power (suspend to ram/disk etc.). My system does not recognize that suspend to ram is actually possible.
[07:35] <pram> hi
[10:46] <BluesKaj> 'Morning folks
[11:39] <jap_> bjr ici
[12:55] <ManDurphy> hello
[14:18] <therazr> so 12.04 + PPAs becomes more or less the same as 13.04?
[14:19] <Pici> therazr: I'm not sure what you're asking exactly, but you shouldn't use PPAs designed for other releases.
[14:19] <therazr> Pici: kubuntu backports ppas for 12.04 lts
[14:21] <Pici> therazr: oh. I misread.  Someone else may need to correct me, but I think that the KDE PPA will bring you up to a more recent KDE version, the other distro packages will not have the same benefit though.  KDE is a special case.
[14:21] <therazr> Pici: Is the upgrade from 12.04 lts to 14.04 lts (when it comes out) a safe procedure?
[14:22] <Pici> therazr: Yes. LTS to LTS upgrades are always supported and should be safe.
[14:23] <therazr> Pici: It's 4 months now until 13.10. And 13.04 is only supported until January 2014. So maybe I should choose Kubuntu 12.04 lts don't you think? And then upgrade to 14.04 when it's out
[14:24] <Pici> therazr: If you want to minimize upgrades, then yes, that might be a better path.
[14:25] <therazr> Pici: don't you think Mir will break the upgrades to 14.04 lts?
[14:25] <Pici> therazr: I don't expect to see Mir introduced in an LTS.
[14:26] <therazr> Pici: I think they expect to achieve that full convergence between form factors, including Mir, by 14.04. They are providing an experimental Mir experience with 13.10 already
[14:27] <Pici> therazr: In any case, there will be an upgrade path provided.
[14:27] <therazr> good
[14:27] <therazr> Is KDE5.0 coming with 14.04?
[14:27] <Esokrates> hi, when i change a boot parameter in /etc/default/grub is it necessary to run update-initramfs -u too?
[14:28] <Esokrates> @therazr, not for sure
[14:29] <Esokrates> therazr, it depends on how fast things develop, as kde is completely independend from kubuntu as you may know
[14:29] <BluesKaj> is kubuntu actually going to use mir ?
[14:29] <therazr> Esokrates: I know I know :). But I think they are not making major changes like they did in KDE3->4 transition
[14:29] <smartboyhw_> BluesKaj: NO :P
[14:30] <Esokrates> BluesKaj, if you ask martin gräßlin, then no
[14:30] <BluesKaj> then why the discussion ?
[14:30] <Esokrates> because shuttleworth promised it would work
[14:31] <Esokrates> but kde upstream refuses to support distribution specific code
[14:31] <BluesKaj> i read that kubuntu wasn't going to touch mir with a 10ft pole :)
[14:32] <BluesKaj> Esokrates, shuttleworth isn't supporting kubuntu so we can't expect anything from him realistically no matter what canonical does withg the ubuntu-core
[14:33] <Torch> http://blog.martin-graesslin.com/blog/2013/05/mir-in-kubuntu/
[14:33] <therazr> BluesKaj: That doesn't mean he is interested in losing the Ubuntu derivatives he accepted Ubuntu GNOME just 2 months ago
[14:34] <BluesKaj> therazr, well , methinks Blue Systems may ahve a thing or 2 to say about that
[14:34] <smartboyhw_> therazr: But it doesn't mean he will make their lifes better…
[14:36] <BluesKaj> the kubuntu is no longer suported by canonical , derivative or not
[14:36] <BluesKaj> therazr,6
[14:37] <therazr> BluesKaj: I know, but I think canonical is interested in having them anyway. Because they know many people use those derivatives don't you think? And since they have the same release cycles for the supported (Unity) edition and derivatives, don't think they will drop that
[14:39] <smartboyhw_> therazr: They won't "drop" alternatives, but em Mark doesn't want them to sell better than Ubuntu itself…
[14:40] <BluesKaj> therazr, somehow I doubt that , canonical is going in a different direction with Unity etc , so if the change in direction and philosophy continues , the responsoibility will be left up to the derivatives to keep up[
[14:40] <therazr> smartboyhw_: They never sold better than the Ubuntu derivatives. So that is not relevant
[14:40] <therazr> And Ubuntu is not going to sell much more than what it sells now, I think that is being realistic
[14:41] <therazr> BluesKaj: I don't doubt that. But they will provide Wayland or X11 as an alternative don't you think? So the derivatives can use them
[14:44] <BluesKaj> kubuntu is also going it's own by default due to canonical dropping support so the other derivatives are on their own except for kubuntu which has solid support so far.
[14:44] <therazr> BluesKaj: Xubuntu and Kubuntu users also count for the current Ubuntu market share
[14:47] <BluesKaj> whoever's polling the market share better qualify their findings , but inclusion doesn't make it real , just helps inflate ubuntu's rating
[14:50] <therazr> BluesKaj: I think having the derivatives is interesting for Canonical and Ubuntu. They just don't support them officially because probably they don't have the resources for that
[14:54] <BluesKaj> Blue Syatms hired 2 devs from Canonical , one of which was doing exclusive kubuntu support , which Canonical dropped,  , so Suttleworth's intentions were very clear about ubuntu's new direction
[14:58] <therazr> BluesKaj: Canonical never "supported" Kubuntu seriously, even when it was considered part of Canonical. So it never was a priority, I don't think they showed less interest in Kubuntu after giving it to Blue Systems than what they showed previously
[15:01] <BluesKaj> therazr, I beg to differ, they had a developer working on it exclusively up until shuttleworth decided to change direction with Unity ... go ask in kubuntu-devel
[15:03] <therazr> BluesKaj: well, Unity has more than one developer though
[15:03] <BluesKaj> the unity change challenged their resources and the derivatives like kubuntu suffered a lack of attention when the kubuntu dev(s) had to take on more work
[15:04] <therazr> BluesKaj: I mean, you really can't notice the differences unless you knew about the change. Kubuntu is more or less the same it was with Canonical. I might add I think it is better now
[15:05] <therazr> Remember when Kubuntu was considered a 2nd class citizen in the realm of KDE distros?
[15:05] <BluesKaj> yes it is  , definitely
[15:06] <therazr> BluesKaj: Together with Ubuntu, Kubuntu 12.04 LTS is the only derivative supported for 5 years too
[15:08] <therazr> BluesKaj: And I might add Netrunner is an excellent distro run by Blue Systems
[15:08] <BluesKaj> therazr, once mir is default on ubuntu , i think we can trully classify kubuntu hardly derivative :)
[15:10] <therazr> BluesKaj: That is not the point. Using Mir or Wayland is irrelevant for that statement I think. What matters is what Canonical considers as their official derivatives, e.g., what follows the same release cycles. As long as they keep true to the ubuntu toolchain, there is nothing wrong if they don't use Mir at all probably
[15:12] <muddles17> Many errors with xorg have been temporarily fixed for now. kde will be using wayland, so mir shouldn't effect kde.
[15:13] <BluesKaj> hardly irrelavant , semantics aside the reality is kubuntu is seriously on it's own however you want to define derivative
[15:14] <therazr> BluesKaj: That's the way Canonical defines derivate from my pov. It doesn't mean they support them financially of course
[15:14] <BluesKaj> okj now , back to support ...this disussion should have been in OT
[15:14] <therazr> lol
[15:47] <FloodBotK1> !netsplit
[16:48] <javier___> Hi
[16:49] <alan_o> So is anyone aware of some pretty serious issues with printing in kubuntu?
[16:50] <alan_o> For example, I'm completely unable to figure out how to even add a printer.
[16:50] <alan_o> and apologies up front if I sound a bit frustrated
[16:50] <alan_o> I've been using normal ubuntu for a long time and never had an issue with this
[16:51] <alan_o> 1. press the K, type printers, click "Printers: Configure your printers"
[16:51] <alan_o> press "click here to add a new printer"
[16:51] <javier___> yep
[16:51] <alan_o> see a dialog: "Password -Add Printer"
[16:51] <alan_o> username is filled in as "root"
[16:52] <alan_o> I change it to my logged in username and password (which has sudo permissions)
[16:52] <alan_o> I see "failed to get a list of devices: 'forbidden'"
[16:52] <javier___> mmm... with your user and pass...
[16:52] <alan_o> yes, with my user and pass that I use for everything else that pops up such a box on this login.
[16:52] <javier___> hey... see in the web browser: http://localhost:631
[16:53] <alan_o> yes
[16:53] <alan_o> I'm getting to that :)
[16:53] <alan_o> Well, let's get to it now....: http://localhost:631/help/network.html
[16:53] <javier___> ok... is the cups server...
[16:54] <alan_o> cupsd seems to be running
[16:54] <javier___> ok...
[16:54] <alan_o> I'm curious why it's seeming to want a root password there
[16:55] <javier___> for the root password... Open a windows terminal, write sudo -s and input your password
[16:55] <alan_o> ok, you want me to set a root password?
[16:55] <javier___> yep
[16:56] <alan_o> ok, so now that seems to work.
[16:56] <javier___> passwd root...  enter the unix password... and etc!
[16:56] <alan_o> should I file a bug? I can't be the first to have run into this....
[16:57] <alan_o> got that, typed it in the box, and I now see a list of printer types
[16:57] <Quintasan> Wait there
[16:57] <Quintasan> Wait wait wait, why on earth are you trying to log in into CUPS as root
[16:58] <javier___> mmmm... em... qhat printer have you??
[16:58] <alan_o> it even discovered my network printer, which is nice (older Ubuntus did that, and then newer ones didn't, for some reason and I had to type the IP, but tahts' neither here nor there)
[16:58] <alan_o> HP TN2100N: JetDirect
[16:58] <javier___> what printer have you??
[16:58] <javier___> for USB conect??
[16:58] <alan_o> no
[16:58] <alan_o> It's a network printer
[16:58] <javier___> for ip...
[16:58] <javier___> ok,
[16:58] <alan_o> yes
[16:58] <alan_o> :9100
[16:59] <therazr> Quintasan: root isn't needed to administrate CUPS?
[16:59] <alan_o> Quintasan: I'm doing what it's telling me to do. I don't like it either. I don't know why it wants a root login
[16:59] <Quintasan> alan_o: It's a network printer, alright, what is the host system?
[16:59] <alan_o> Quintasan: host system?
[16:59] <Quintasan> therazr: You should be able to access cups with YOUR username and password, not root
[16:59] <alan_o> It's an HP JetDirect printer directly on the network
[16:59] <alan_o> Quintasan: it says no
[16:59] <Quintasan> alan_o: Ahh, okay, I see.
[17:00] <Quintasan> alan_o: I presume you tired adding it directly by IP address, right?
[17:00] <alan_o> yes, that's the 2nd part of my frustration
[17:00] <alan_o> as soon as I put the address in, it printed 4 pages of junk, twice
[17:00] <alan_o> before I could even select the driver type
[17:01] <Quintasan> alan_o: Can you access localhost:631 with your username and password?
[17:01] <alan_o> Quintasan: no password necessary even
[17:01] <Quintasan> alan_o: Go to Administartion -> Add printer
[17:01] <Quintasan> It should ask for username and password now
[17:02] <javier___> hey... kubuntu have a KDE-PRINTER.. or kde-printermanagment
[17:02] <alan_o> Quintasan: my username and pw comes up with "unable to add printer: forbidden"
[17:02] <alan_o> oh wait
[17:02] <alan_o> I think this may be my fault
[17:02] <Quintasan> That means you are probably not in the lpadmin group alan_o
[17:02] <alan_o> I blew away my groups accidentally the otherday (usermod and forgot to add -a)
[17:03] <alan_o> dang it.
[17:03] <alan_o> yeah, I bet that's the problem
[17:03] <Quintasan> That's probably part of the problem.
[17:03] <javier___> see this page
[17:03] <javier___> http://www.kubuntu.org/doc/7.10/printing/C/print.html
[17:03] <alan_o> arrgh. I thought I restored all the groups, but I gutess I missed one
[17:03] <javier___> or... http://userbase.kde.org/Printer_Config
[17:03] <alan_o> javier___: 7.10 ?
[17:04] <Quintasan> javier___: That document is kind of OLD, we are currently at 13.04
[17:04] <alan_o> yes. Either way, I'll fix my group. I'm sure I can figure it out once that's fixed.
[17:05] <javier___> there are things that have not changed
[17:05] <alan_o> *sigh* sorry for the noise, I went ballistic when something basic seemed so fundamentally broken.
[17:05] <alan_o> I'll need to re-logout
[17:05] <therazr> Quintasan: Its regarding ibus and Kubuntu. Can you write characters such as á é ã ô in libreoffice? thanks
[17:05] <Quintasan> alan_o: Good luck, I think you might have better luck adding that through webui
[17:06] <Quintasan> therazr: I do not think you need ibus for that
[17:06] <Guest96044> hi
[17:06] <alan_o> Quintasan: I like to try to do things the more desktop-integrated ways, just to exercise them. Failing that, yeah, I'll try on the cups web interface.
[17:06] <Quintasan> alan_o: Hmm
[17:07] <Quintasan> alan_o: Try doing that via the GUI once you fix your groups maybe
[17:07] <Quintasan> if not then use the webui
[17:07] <Quintasan> Guest96044: hi
[17:07] <Quintasan> therazr: http://wstaw.org/m/2013/06/14/plasma-desktopNA2481.png
[17:07] <therazr> Quintasan: I need ibus to write japanese though. And I can't have 2 input methods at the same time, Xorg doesn't like that xD
[17:07] <Quintasan> Ah yes
[17:07] <Guest96044> how can i get sholarship
[17:07] <Guest96044> ?
[17:07] <Quintasan> Guest96044: That's probably not the right channel
[17:07] <Quintasan> therazr: Do you have anthy installed?
[17:08] <Quintasan> therazr: ibus-anthy is the package
[17:08] <therazr> Quintasan: yes. The problem is not anthy. It's ibus, because I can use mozc too to write japanese.
[17:08] <therazr> ibus-mozc
[17:08]  * Quintasan looks
[17:09] <therazr> and ibus-anthy. Both work fine. The problem is the characters with accents áãẽéẽónñ etc. in GTK apps. This problem doesn't happen in GTK-based DEs though
[17:10] <Quintasan> therazr: You can't type those in GTK apps under KDE but it works in say GNOME or XFCE?
[17:10] <therazr> indeed :P
[17:11] <Quintasan> Well, I could either blame GTK integration OR the backend itself or LibreOffice
[17:12] <therazr> Quintasan: Guess what, it also works on other KDE distros like Fedora or Mageia. It's just Kubuntu lol, every version
[17:12] <Quintasan> Hmm
[17:13] <Quintasan> therazr: At the same time I'm wondering how the hell do you input the accent characters with mozc since it's made for Japanese input and I'm pretty sure there are no such symbols in Japanese
[17:13] <Guest96044> sandra
[17:14] <Quintasan> therazr: Truth be told I'd force the switch to fcitx because I find ibus damn buggy
[17:14] <therazr> Quintasan: Yes, that's what I was going to wask. Among scim, fcitx and uim which one is better alternative?
[17:15] <Quintasan> Since you are using mozc as backend I'd say you can go with fcitx
[17:15] <Quintasan> scim I think has had no development for quite a while
[17:15] <therazr> Quintasan: Whenever I want to write these characters I just disable the IME with ctrl+space.
[17:15] <alan_o> Quintasan: javier___ : Thanks. Works great now. Sorry for my frustration.
[17:15] <Quintasan> alan_o: Great.
[17:16] <Quintasan> therazr: Hah, lol I can type them just fine here
[17:16] <Quintasan> therazr: I'd say you broke something then
[17:16] <therazr> Quintasan: Also, mozc or anthy?
[17:16] <Quintasan> I'm not sure what though
[17:17] <Quintasan> therazr: I have been using anthy for quite a while but mozc seems also good
[17:17] <Quintasan> therazr: I'd give both a go but now I'm supposted to be studying for exams :P
[17:18] <therazr> I can write in Romaji here with the IME enabled too, but I need to disable the IME to write the characters with the accents.
[17:19] <therazr> Since the IME assumes the English keyboard as the fallback I think
[17:19] <Quintasan> therazr: Look, if the backend doesn't have support for those characters there is no way you should be able to input those symbols with the IME enabled
[17:19] <Quintasan> at least there should be no way
[17:19] <therazr> But that's ok, do you know about uim?
[17:19] <Quintasan> I know about it but I have mixed feeling about it
[17:20] <Quintasan> therazr: I'd rather use fcitx with mozc
[17:20] <Quintasan> I think it also has anthy backend but it's not in the repositories yet
[17:21] <therazr> I found uim-anthy
[17:21] <therazr> ups
[17:21] <therazr> fcitx
[17:21] <therazr> fcitx-anthy too
[17:21] <Quintasan> The problem with input methods is that there are multiple backends and god knows which one is better
[17:22] <Quintasan> therazr: Saucy or Raring?
[17:22] <therazr> Quintasan: isnt mozc provided by Google?
[17:22] <Quintasan> >This open-source project originates from Google Japanese Input.
[17:23] <therazr> Quintasan: I'm on saucy, its only there like you said (fcitx-anthy). Maybe it's buggy, so I might prefer mozc
[17:23] <Quintasan> Ohhhhh
[17:23] <Quintasan> wait
[17:23] <Quintasan> I never said anything about it being buggy
[17:24] <Quintasan> ibus is buggy as hell
[17:24] <Quintasan> at least when it comes to QT
[17:24] <Quintasan> Qt integration.
[17:24] <Quintasan> Try fcitx-anthy and let me know how it works
[17:25] <therazr> I think the version of ibus in kubuntu is old, or something. Because it's very different than what you get in Fedora or Mageia. I mean, the Graphical Interface to configure it has many more options in the latter distros
[17:25] <Quintasan> therazr: fcitx, scim, uim, ibus and hime and whatnot are frontends, while anthy and mozc are backends
[17:26] <Quintasan> therazr: the default frontend in *buntu is IBus
[17:26] <therazr> Quintasan: I know I know. Which one has smarter guessing for Japanese words (the kanji equivalents to the romaji), anthy or mozc?
[17:27] <Quintasan> therazr: You have to try both, I'd say mozc since I used the Google Japanese Input on Android and it was great
[17:27] <Quintasan> therazr: But I only used anthy on my desktop
[17:27] <therazr> Yea, since you are a native it should be mostly the same with either :)
[17:28] <Quintasan> therazr: Ha ha, not, I'm from Poland :P
[17:28] <Quintasan> If that's what you were reffering to by native
[17:29] <therazr> LOL. Ok then, you are still knowledgeable on the language
[17:29] <Quintasan> therazr: That said, if you decide to give FCITX a go, be sure to let me know how that work in KDE, I'm assuming you are using that
[17:30] <Quintasan> therazr: I'd like to think that but I can barely put sentences together :P
[17:30] <therazr> I am on KDE. If I weren't, ibus would be enough
[17:31] <Quintasan> ああああああああああ
[17:31] <Quintasan> well
[17:31] <therazr> So are you learning the language? I know this should be offtopic :P
[17:31] <Quintasan> When you pull ibus-anthy it should work without any magic
[17:31] <Quintasan> yeah, let's move it to offtopic
[18:50] <KeanuR_> hello together.. freshly installed 13.04 (used 12.04 before) now i cant open my crypted harddrives with luksopen even the password is 100% correct... any ideas?
[18:53] <KeanuR_> hmm better to ask in a real linux channel?
[20:01] <tumor130> xxxxxxxxxx
[20:02] <genii> Hm.
[21:24] <hellslinger> anyone know how to get blur working for konsole in 4.10?
[21:24] <marcosnt1177> tem alguem ae
[21:25] <marcosnt1177> have brazilian user here


[10:38] <andrew_46> Is this a bad place to ask about a problem logging on to the Ubuntu wiki? I am trying to associate andrew.46 with https://launchpad.net/~andrew.46 via OpenID so I can continue work on https://help.ubuntu.com/community/slrn


[04:06] <smartboyhw> Probably my best blog post ever: http://smartboyhwubuntu.wordpress.com/2013/08/07/ubuntu-edge-target-too-high-but-a-phone-that-one-will-want/ (LOL)
[05:49] <valorie> gah, I wish wordstar would allow me to make comments, etc.!
[05:49] <valorie> good one, smartboyhw
[05:49] <valorie> and your meeting is on my calendar, so if I can wake so early, I'll listen in at least
[05:50] <valorie> I do have a KDE devel account....
[06:12] <soee> good morning
[08:13] <smartboyhw> valorie, thank you:)
[08:19] <yofel> smartboyhw: could you please look at the libgphoto issue in backports? What did you backport it for?
[08:19] <yofel> and nice blog post :)
[08:24] <smartboyhw> yofel, I forgotten, for sure it's one of the 4.10.97 quantal things
[08:24] <smartboyhw> I probably should have put it into staging, sigh
[08:24] <smartboyhw> My damn fault, sorry.
[08:24] <yofel> even then it's a bad idea as I wrote on the bug
[08:24] <yofel> well, don't worry about it too much, I've seen worse happen ^^
[08:25] <yofel> I wrote a backport rule that uses the old libgphoto on << saucy
[08:25] <yofel> so it won't be needed for 4.11.00
[08:26] <shadeslayer> yofel: can we move precise backports to the beta backports repo?
[08:26] <yofel> considering the rdepends list of libgphoto2-2 isn't really long, we *could* do a transition in the backports, but I don't think it's worth it unless we really need it
[08:27] <yofel> shadeslayer: no, I just hit
[08:27] <yofel> Unpacking replacement plasma-widget-kimpanel ...
[08:27] <yofel> dpkg: error processing /var/cache/apt/archives/plasma-widget-kimpanel_4%3a4.10.97-0ubuntu1~ubuntu12.04.1~ppa1_amd64.deb (--unpack):
[08:27] <yofel>  trying to overwrite '/usr/share/kde4/services/plasma-dataengine-kimpanel.desktop', which is also in package plasma-dataengines-addons 4:4.8.5-0ubuntu0.1
[08:27] <yofel> on 4.8 -> 4.11
[08:27] <shadeslayer> ( assuming it has been tested ... right )
[08:27]  * shadeslayer will have a look in the evening
[08:27] <yofel> I'll try to fix what I find till then, at least stuff like ^
[08:29] <shadeslayer> cool
[08:34] <smartboyhw> Yawn
[08:35] <smartboyhw> I'm a bit tired with packaging stuff today:P
[08:36] <shadeslayer> then do QA :D
[08:36] <smartboyhw> shadeslayer, hey, when are you going to review ktp 0.6.3?
[08:36] <shadeslayer> oh drat
[08:36] <smartboyhw> LO
[08:36] <smartboyhw> LOL
[08:36] <shadeslayer> so much to do
[08:37] <yofel> on that topic, let me look at PMC ^^
[08:49] <smartboyhw> LOL thanks shadeslayer yofel :)
[08:50] <shadeslayer> smartboyhw: we can drop set_cmp_policy.patch in ktp-common-internals now
[08:51] <shadeslayer> it was upstreamed
[08:51] <shadeslayer> and we have cdbs-*-list in there 0.o
[08:52] <shadeslayer> yofel: ^ we can drop cdbs-install-list and cdbs-package-list right?
[08:53] <yofel> sure, unless you still use cdbs ^^
[08:55] <yofel> shadeslayer: actually, those are supposed to be temporary files, no?
[08:55] <shadeslayer> yofel: yeah, however dh_clean didn't remove them
[08:55] <shadeslayer> which is why I thought best to ask :)
[08:55] <yofel> build system stuff I guess, as I have here dhmk-install-list and dhmk-package-list in a build
[08:56] <yofel> maybe got left over in the buildsystem transition
[08:56] <shadeslayer> not sure, I wonder if ktp was ever cdbs
[09:00] <yofel> smartboyhw: PMC: as you're shipping the headers, please make a libplasmamediacenter1.1 package and add a symbols file
[09:01] <shadeslayer> smartboyhw: ktp contact list and common internals uploaded
[09:05] <yofel> wow, PMC licensing can give you a headache http://paste.kde.org/p0c59d2c0
[09:05] <yofel> I think someone didn't  understand licensing if I see that random mix of GPL and LGPL
[09:07] <smartboyhw> yofel, licensing?:O
[09:07] <smartboyhw> shadeslayer, thank you
[09:07] <yofel> not sure if it's worth to update, the copyright file is wrong though
[09:08] <smartboyhw> yofel, OK
[09:08] <shadeslayer> accounts KCM up as well
[09:14] <shadeslayer> smartboyhw: you forget to package ktp-approver
[09:14] <smartboyhw> shadeslayer, oy, sorry:P
[09:14] <shadeslayer> plz do that
[09:14] <shadeslayer> while I do the rest
[09:18] <smartboyhw> yofel, which package should I move those usr/lib/kde4/*.so to?
[09:18] <smartboyhw> And no need for the symbols files for these right?
[09:18] <yofel> you can only make symbols files for libs that have a SOVERSION, and only needed if there's headers and the dev symlink shipped
[09:18] <yofel> leave the usr/lib/kde4/ stuff where it is
[09:19] <smartboyhw> yofel, OK
[09:21] <smartboyhw> yofel, wait, the package should be named libplasmamediacenter1 or libplasmamediacenter1.1?
[09:21] <yofel> SOVERSION is 1.1, so latter
[09:24] <smartboyhw> shadeslayer, ktp-approver uploaded to ppa
[09:24] <shadeslayer> ok
[09:25] <smartboyhw> yofel, uh I'm facing the debug-file-with-no-debug-symbols again
[09:25] <yofel> can't help you with that
[09:26] <smartboyhw> Cry :(
[09:27] <smartboyhw> yofel, actually 1 thing
[09:33] <yofel> hm?
[09:34] <shadeslayer> ufff
[09:35] <shadeslayer> I'm tired of uploading ktp
[09:35] <smartboyhw> shadeslayer, LOL
[09:35] <smartboyhw> yofel, I'm doing an experiment
[09:35] <yofel> uh... of what kind? ^^
[09:35] <smartboyhw> Because I suddenly remember something
[09:36] <smartboyhw> yofel, if I update dh from 8 to 9 and update symbols, the debug-file-has-no-debug-symbols lintian warning should disappear....
[09:36] <yofel> well, try it
[09:36] <shadeslayer> booorrreeddd
[09:36] <yofel> go rewrite some copyright files
[09:37] <smartboyhw> yofel, it does:P
[09:37] <smartboyhw> Now, the copyright
[09:38] <smartboyhw> yofel, the lintian warning debug-file-has-no-debug-symbols does disappear after the things I did as above
[09:38] <yofel> ya
[09:38] <yofel> y
[09:39] <smartboyhw> yofel, so you want me to retain the changes or undo it back?
[09:39] <yofel> what changes?
[09:40] <smartboyhw> yofel, a.k.a yofel, if I update dh from 8 to 9 and update symbols, the debug-file-has-no-debug-symbols lintian warning should disappear....
[09:40] <smartboyhw> yofel, what the
[09:40] <smartboyhw> yofel, if I update dh from 8 to 9 and update symbols, the debug-file-has-no-debug-symbols lintian warning should disappear....
[09:41] <smartboyhw> Oops
[09:41] <smartboyhw> libs/mediacenter/pmccoverartprovider.cpp: BSD (2 clause) LGPL (v2.1 or later)
[09:41] <smartboyhw> A file with two licenses!?
[09:41] <yofel> yeah, can happen, check the header
[09:41] <yofel> and just use dh9 if it works better
[09:41] <smartboyhw> yofel, sure:)
[09:42] <yofel> this is a great copyright...
[09:42] <yofel> Copyright (C) <year>  <name of author>
[09:42] <smartboyhw> yofel, um, I checked the header and two licenses exist
[09:43] <smartboyhw> One is from 2004
[09:43] <smartboyhw> One is from 2011 and 2012
[09:43] <smartboyhw> BSD -> 2004, LGPL-> 2011-2012
[09:44] <yofel> hm, I would have to look up what to do here...
[09:44] <yofel> shadeslayer:  ^ ?
[09:44] <shadeslayer> uhm, too long, and I'm slightly busy with something else
[09:44] <yofel> is that a simple 'or' then? because the file simply has 2 copyrights in it...
[09:45] <yofel> anyway, lunch
[09:45]  * yofel runs :P
[09:46] <smartboyhw> yofel, duh
[09:46] <smartboyhw> No "or"
[09:46] <smartboyhw> I should ask upstream to fix it next time....
[10:02] <smartboyhw> kubotu: newversion plasma-mediacenter 1.0.90
[10:02] <kubotu> https://bugs.launchpad.net/bugs/1209159
[10:02] <smartboyhw> Hmm, obviously I didn't report such a bug:P
[10:08] <shadeslayer> hmm
[10:08] <shadeslayer> smartboyhw: I don't think it's required to bump the version on meta-kde-telepathy
[10:08] <smartboyhw> shadeslayer, hey, you told me to do that.
[10:08] <shadeslayer> I did?
[10:09] <shadeslayer> actually, I don't think it's useful to update the meta-ktp package
[10:09] <shadeslayer> sorry if I told you otherwise
[10:11] <shadeslayer> smartboyhw: everything uploaded
[10:12] <smartboyhw> shadeslayer, great
[10:12] <shadeslayer> plz double check that everything is uploaded
[10:13] <smartboyhw> shadeslayer, sure
[10:15] <smartboyhw> shadeslayer, yes, everything is uploaded
[10:15] <shadeslayer> aweswome \o/
[10:24] <smartboyhw> yofel, is there any command to check on the names and the authors of the files?
[10:28] <shadeslayer> licensecheck
[10:29] <jussi> poor Aaron, wrting to a free software list with a signature of "Sent from Windows Mail" :P
[10:30] <shadeslayer> ^^
[10:31] <smartboyhw> jussi, LOL
[10:31] <Tm_T> jussi: UDS session with Windows user can also happen in this community
[10:38] <yofel> smartboyhw: to get the copyright holder for a specific license I use something like:
[10:38] <yofel> licensecheck -r * | grep LGPL | grep \(v2\) | cut -f 1 -d \: | xargs grep Copyright
[10:38] <yofel> extend as needed
[10:44] <smartboyhw> yofel, what if a copyright holder has no year attached?
[11:31] <smartboyhw> Meh, can anybody tell me the solution to that? ^
[11:32] <shadeslayer> smartboyhw: then don't mention it ?
[11:32] <smartboyhw> shadeslayer, really?
[11:32] <shadeslayer> though I suppose ScottK can advise better
[12:00]  * yofel just got some rather curious mails from bdmurray: e.g. http://paste.kde.org/padb4d067
[12:01] <yofel> we get regression reports from errors.u.c now o.O?
[12:03] <smartboyhw> yofel, a new thing I heard from #ubuntu-release
[12:04] <smartboyhw> yofel, what's your point of view of the copyright stuff?
[12:05] <yofel> uh, not sure. I don't think a copyright without a year is even valid. Then again, the copyright field in dep5 is formless, so just leave the year away for now
[12:06] <smartboyhw> yofel, alright
[12:06] <smartboyhw> Uh, the changelog is really packed now...
[12:08] <yofel> hm, one mail was about an increase of crash rate in the last 2 weeks for nepomuk-core
[12:08] <yofel> the graph on https://errors.ubuntu.com/?release=Ubuntu%2013.04&package=nepomuk-core&version=4:4.10.5-0ubuntu0.1 doesn't tell me a thing though :(
[12:08] <smartboyhw> yofel, LOL
[12:11] <smartboyhw> yofel, https://launchpad.net/~smartboyhw/+archive/packaging-staging-1/+files/plasma-mediacenter_1.0.90-0ubuntu1.dsc for you:)
[12:11] <smartboyhw> i386 	5 	70 jobs (41 minutes)
[12:12] <smartboyhw> That's the official distribution machines:O
[12:18] <shadeslayer> yofel: that looks like fun
[12:19] <shadeslayer> and kdeartwork? :D
[12:19]  * smartboyhw wonders how many of these emails did ScottK, Riddell and shadeslayer receive:P
[12:19] <shadeslayer> none
[12:19] <shadeslayer> because we're awesome and don't introduce regressions :P
[12:19] <yofel> well, I got mails for kdeartwork, kde-runtime, kde-workspace, kactivites, konsole and nepomuk-core. nepomuk-core got an additional one about increase in crash rate
[12:20] <yofel> I think only the *uploader* gets them
[12:20] <shadeslayer> yofel clearly works for openSUSE and wants to destroy kubuntu
[12:20] <shadeslayer> :>
[12:20] <yofel> which is kinda useless for us
[12:20] <yofel> well, it would save me from having to learn politics to develop a distro
[12:20] <smartboyhw> yofel, LOL
[12:20] <smartboyhw> shadeslayer, LOL
[12:20] <yofel> anyway, topic change
[12:20] <shadeslayer> :P
[12:21] <shadeslayer> I can't find my yubikey
[12:21]  * smartboyhw wonders should he play with something in http://techbase.kde.org/Projects/Edu/ProjectSuggestions
[12:21] <shadeslayer> so no backtraces for me
[12:25]  * yofel wonders if he should hack on kinfocenter
[12:25] <yofel> or does someone know a gui way to access the stuff from 'upower --dump' ?
[12:32] <smartboyhw> Hmm, I will probably play with Komputer:P
[12:56] <d_ed_> hey, I joined to thank Howard Chan for packaging the latest KDE-Telepathy
[12:56] <d_ed_> cheers dude (if you're here)
[12:58] <shadeslayer> smartboyhw: ^^
[13:01] <ScottK> shadeslayer: If copyright is listed without year, I'd go ahead and put it in debian/copyright as is.
[13:06] <shadeslayer> thought so
[13:24] <smartboyhw> shadeslayer, :)
[13:24] <smartboyhw> d_ed_, :)
[13:24] <smartboyhw> shadeslayer, I've put it in anyway, no worries:0
[13:30] <smartboyhw> yofel, you reviewed plasma-mediacenter yet?
[13:30] <smartboyhw> New one at https://launchpad.net/~smartboyhw/+archive/packaging-staging-1/+files/plasma-mediacenter_1.0.90-0ubuntu1.dsc
[13:38] <smartboyhw> Rebooting, see ya
[13:41] <smartboyhw> Back into nice KDE.
[13:45] <yofel> smartboyhw: got pulled to a meeting at work, so nope
[13:46] <yofel> won't do it for another 4h either
[14:05] <yofel> vHanda: in nepomuk-core you have a file without copyright: autotests/test/resourcetests.h:    Copyright (C) <year>  <name of author>
[14:05] <yofel> looking at the cpp I think your name was supposed to be there
[14:11] <smartboyhw> yofel, alright
[14:52] <debfx> apt-get is not happy about the libkscreen0 libkscreen1 conflict
[14:53] <smartboyhw> debfx, uh oh, my fault then:P
[14:53] <smartboyhw> debfx, how?
[14:53] <debfx> it hold back the kscreen upgrade because it would have to remove libkscreen0
[14:53] <smartboyhw> Paste it plz
[14:54] <smartboyhw> debfx, ah OK, should have added Breaks, Conflicts, that sort of thing dumb
[14:54] <smartboyhw> Wait me a minute plz
[14:54] <debfx> well the problem is that libkscreen0 and libkscreen1 share some files
[14:54] <smartboyhw> debfx, I know howto fix
[14:55] <smartboyhw> debfx, but you will have to sponsor the fix:P
[14:55] <debfx> how?
[14:55] <smartboyhw> debfx, hmm, libkscreen1 already breaks/replaces libkscreen0
[14:55] <smartboyhw> Weird weird, maybe a conflicts
[14:56] <ScottK> If you apt-get install kscreen it will work.
[14:56] <debfx> yes, but that's not how upgrades are supposed to work
[14:57] <smartboyhw> debfx, I think it should be a conflict more than a break then, sigh
[14:57] <debfx> smartboyhw: I don't think that will change anything
[14:57] <ScottK> debfx: If you figure it out, I'll push it right through SRU.
[14:57] <smartboyhw> debfx, I think it would.
[14:57] <smartboyhw> This is a stronger restriction than Breaks, which prevents the broken package from being configured while the breaking package is in the "Unpacked" state but allows both packages to be unpacked at the same time.
[14:58] <smartboyhw>  Conflicts should be used
[14:58] <smartboyhw>     when two packages provide the same file and will continue to do so,
[14:58] <smartboyhw> ........
[14:58] <smartboyhw> So, probably conflict will work
[14:58] <debfx> the problem is that apt doesn't consider removing libkscreen0 a valid option to upgrade kscreen
[14:59] <smartboyhw> debfx, ah so in the kscreen session OK
[15:04] <smartboyhw> debfx, I will probably make kscreen 1.0 conflict libkscreen (<< 1.0)
[15:04] <smartboyhw> That makes more sense doesn't it?>
[15:05] <smartboyhw> ScottK, ^
[15:05] <debfx> there is no libkscreen package
[15:05] <smartboyhw> debfx, what?
[15:05] <smartboyhw> debfx, I mean, conflict libkscreen0 sorry:P
[15:05]  * ScottK is doing $work, so just let me know when you have it figured out and I'll push it through
[15:06] <debfx> I don't see why that's necessary or how it would improve the situation
[15:06] <smartboyhw> debfx, well why not?
[15:06] <smartboyhw> It is not allowing removing libkscreen0 as an option
[15:06] <smartboyhw> So, that helps.
[15:07] <ScottK> smartboyhw: Did you test it or are you guessing?
[15:08] <yofel> smartboyhw: the issue isn't that you *cannot* upgrade kscreen, it's that in some cases it won't happen automatically
[15:08] <yofel> in an ideal world, a user should never have to run 'dist-upgrade' to install things from -updates
[15:08] <smartboyhw> ScottK, guessing.....
[15:09] <smartboyhw> yofel, so what's the solution
[15:09] <yofel> but as the libkscreen packaging isn't really proper, it doesn't work like that
[15:09] <yofel> for the SRU? I don't know if there is an easy one
[15:09] <debfx> yofel: actually dist-upgrade also doesn't work
[15:09] <debfx> at least for me
[15:09] <yofel> debfx: I know, happened to me too, but I really don't understand the resolver here :/
[15:10] <yofel> I would've expected this to work, but in some cases it doesn't
[15:10] <debfx> yep
[15:10] <ScottK> That's why I suggest testing, not guessing.
[15:10] <yofel> same actually applies for the kdevelop backport I tried for precise, that's stuck in the same situation (kdevplatform5-libs -> kdevplatform7-libs)
[15:11] <debfx> afiestas: are the libkscreen backends tight to the same libkscreen version?
[15:12] <debfx> for example do the 1.0 backends work with libkscreen 0.0.81?
[15:13] <yofel> hm, good idea, that could work
[15:18] <debfx> if not the plugins should have a namespaced path, e.g. /usr/lib/kde4/plugins/kscreen1/
[15:22] <afiestas> debfx: please, don't split the backend from the lib
[15:24] <debfx> afiestas: would it be possible to put the soname somewhere in the path of the backends?
[15:25] <debfx> that way libkscreen0, libkscreen1 etc could be made co-installable
[15:25] <smartboyhw> Let me see if I can ring 97870010 (what a phone no. and actually that's JontheEchidna's OpenPGP key;P)
[20:20] <ahoneybun>  Hello all


[14:26] <georgios> i see in snap-store that all my apps are not confined. however apparmor is installed and blocks hello-world.evil as expected. so what is the truth?
[14:29] <georgios> in practice, firefox for example, follows the rules  that i set
[15:12]  * zyga-mbp georgios which OS are you on?
[15:12] <zyga-mbp> try
[15:12] <zyga-mbp> snap debug confinement
[15:13] <zyga-mbp> you can also try thi:
[15:13] <zyga-mbp> snap debug sandbox-features
[16:43] <georgios> hi zyga. i am on archlinux
[16:50] <zyga-mbp> georgios hi
[16:50] <zyga-mbp> what did the two debug command say?
[16:54] <georgios> [root@wizy ~]# snap debug confinement
[16:54] <georgios> partial
[16:54] <georgios> [root@wizy ~]# snap debug sandbox-features
[16:54] <georgios> apparmor:             kernel:caps kernel:domain kernel:file kernel:mount kernel:namespaces kernel:network_v8 kernel:policy kernel:ptrace kernel:query kernel:rlimit kernel:signal parser:unsafe policy:default support-level:partial
[16:54] <georgios> confinement-options:  classic devmode
[16:54] <georgios> dbus:                 mediated-bus-access
[16:54] <georgios> kmod:                 mediated-modprobe
[16:54] <georgios> mount:                layouts mount-namespace per-snap-persistency per-snap-profiles per-snap-updates per-snap-user-profiles stale-base-invalidation
[16:54] <georgios> seccomp:              bpf-actlog bpf-argument-filtering kernel:allow kernel:errno kernel:kill_process kernel:kill_thread kernel:log kernel:trace kernel:trap kernel:user_notif
[16:54] <georgios> udev:                 tagging
[16:54] <georgios> oooooooooooooops
[16:54] <georgios> i was going to paste this
[16:54] <georgios> [root@wizy ~]# snap debug confinement
[16:54] <georgios> partial
[16:54] <georgios> [root@wizy ~]# snap debug sandbox-features
[16:54] <georgios> apparmor:             kernel:caps kernel:domain kernel:file kernel:mount kernel:namespaces kernel:network_v8 kernel:policy kernel:ptrace kernel:query kernel:rlimit kernel:signal parser:unsafe policy:default support-level:partial
[16:54] <georgios> confinement-options:  classic devmode
[16:54] <georgios> dbus:                 mediated-bus-access
[16:54] <georgios> kmod:                 mediated-modprobe
[16:54] <georgios> mount:                layouts mount-namespace per-snap-persistency per-snap-profiles per-snap-updates per-snap-user-profiles stale-base-invalidation
[16:54] <georgios> seccomp:              bpf-actlog bpf-argument-filtering kernel:allow kernel:errno kernel:kill_process kernel:kill_thread kernel:log kernel:trace kernel:trap kernel:user_notif
[16:54] <georgios> udev:                 tagging
[16:54] <georgios> WTF
[16:55] <georgios> i am very sorry for polluting the channel
[16:55] <georgios> http://paste.debian.net/1216498/
[16:55] <georgios> this is what i intended to paste
[16:55] <georgios> let me see if my client has anti-spam protection
[17:00] <georgios> ok, set
[17:06] <zyga-mbp> no worries
[17:07] <zyga-mbp> georgios this tells you that confinement is partial, many things are supported but some things are not
[17:07] <zyga-mbp> most notably, I beileve, your kernel doesn't have apparmor unix mediation, so dbus is not protected
[17:07] <zyga-mbp> dbus is confusing here because there are two parts of snapd that interact with it
[17:08] <zyga-mbp> dbus as in host's dbus configuration (that's always supported)
[17:08] <zyga-mbp> and apparmor's parsing of unix socket messages on dbus
[17:08] <zyga-mbp> that's not universally supported yet AFAIK
[17:08] <zyga-mbp> that's that
[17:08] <georgios> is it tewakable by rebuilding?
[17:10] <georgios> i wanted to rebuild the kernel anyway
[17:37] <zyga-mbp> georgios perhaps, but I'm not an expert on Arch
[17:37] <zyga-mbp> you may want to ask mborzecki next week, he is running arch
[18:02] <georgios> it has been some years that i am not building my own kernels. it feels nice to do it once again!
[19:14] <georgios> it seems a patch is needed
[19:14] <georgios> i shall wait