[07:28] <mandel> morning all!
[07:32] <mmcc> hi mandel :)
[07:33] <mandel> mmcc, what are you doing here!
[07:33] <mmcc> mandel, I left you some nice long reviews, feel free to send me angry emails while I go sleep
[07:33] <mandel> mmcc, you could have sent me an email instead of waiting, you know that right?
[07:33] <mandel> hehehe
[07:34] <mmcc> it's only just past midnight here, so I'm just up late catching up. don't get used to it :)
[07:34] <mmcc> heh
[07:34] <mmcc> ok, actually going now. cheers
[07:35] <mandel> mmcc, good night!
[08:41] <JamesTait> Morning all! :)
[09:19] <mandel> tea break :)
[09:52]  * mandel back
[11:42] <ralsina> good morning!
[12:33] <mandel> ralsina, welcome back!
[12:33] <mandel> ralsina, I'm off to have lunch, wanna catch up later?
[12:33] <ralsina> mandel: yes please
[12:33] <ralsina> mandel: buen provecho
[12:34] <mandel> ralsina, thx, I'll be fast = heat food, eat and let the dog pee :)
[12:34] <ralsina> mandel: no rush, don't fall on things, take care ;-)
[12:42] <ralsina> mandel: take your time, I forgot I have a call now for about 30 minutes
[13:21] <mandel> ralsina, I'm back let me know whenever you are free
[13:21] <ralsina> mandel: now is good
[13:21] <ralsina> mandel: mumble?
[13:21] <mandel> ralsina, sure, launching the thing
[13:22] <mandel> ralsina, can you hear me?
[13:22] <ralsina> mandel: no, and no red lips
[13:23] <mandel> ralsina, wierd, I hear you, I see my red lips, see yours.. etc..
[13:23] <mandel> ralsina, ok
[13:28] <dobey> hmm
[13:30] <ralsina> dobey, hi!
[13:31] <dobey> hi
[13:33] <alecu> hello all!
[13:47] <ralsina> hola alecu!
[13:47] <ralsina> alecu: thought you were on vacations!
[13:48] <alecu> ralsina: no, I only took yesterday off since Amelia is on winter vacations and nobody could babysit her.
[13:49] <ralsina> alecu: cool!
[14:00] <ralsina> alecu: I am in catchup mode, can we have our 1-1 in about 30'?
[14:01] <alecu> ralsina: sure
[14:57] <briancurtin> are we doing mumble or hangout?
[14:58] <ralsina> I think I may have to skipit
[14:58]  * alecu readies his pirate captain hat
[14:58] <alecu> oh :-(
[14:58] <ralsina> let's schedule it for tomorrow same bat-time, same bat-channel
[14:58] <briancurtin> sounds good. text standup for now?
[14:59] <dobey> oh, ok then
[15:03] <dobey> if not i'm just going to lunch then :)
[15:03] <briancurtin> me
[15:03] <mmcc> Can't connect to mumble here, is it going on?
[15:04] <briancurtin> mmcc: doing it tomorrow
[15:04] <briancurtin> mmcc: so you have the next 24 hours to figure it out...or else
[15:04] <mmcc> briancurtin: Aha, thx.
[15:04] <dobey> i guess that means we're skipping standup too then
[15:05] <dobey> since nobody else is saying anything?
[15:08] <briancurtin> dobey: EOM before it even started, i guess. enjoy lunch
[15:08] <briancurtin> :)
[15:12] <rye> erm
[15:12] <dobey> ok, lunch time
[15:15] <mandel> briancurtin, ralsina, alecu, dobey, stop porting things to python3 and port the to ChinesePython: http://www.chinesepython.org/home.html
[15:15] <mandel> if you are lazy, someone is translating python in chinese, as 'import sys' is '載入 系統'
[15:19] <diogobaeder> WTF (it would be a WTF in any language other than english)
[15:20] <diogobaeder> mandel, this reminds me of a portuguese version I got for Martin Fowler's "Refactoring" book
[15:20] <diogobaeder> instead of "getPrice", for example, it was "lerPreço". Pretty crappy.
[15:20] <briancurtin> i like that they're still using the super old python.org website look
[15:21] <mandel> diogobaeder, yes, they should not translate IT books.. ins spain is very common, horrible, horrible..
[15:22] <diogobaeder> mandel, +1
[15:24] <diogobaeder> mandel, everytime someone asks me if there's a portuguese version for an IT book originally in english: http://is.gd/MB9tic
[15:25] <diogobaeder> lunch time
[15:38] <alecu> mandel: the "latests news" are from Feb 2004
[15:38] <alecu> mandel: and the latest release is based on python 2.1.3...
[15:39] <alecu> mandel: so, we should keep porting to python3, that already supports all kinds of unicode identifiers
[15:40] <mandel> alecu, but but.. we could get so many community contributions from china! I know is the only reason why they are holding back..
[15:40] <alecu> (and for mandel and diogo's happiness, non-english books with translated identifiers won't be exclusive to Java)!
[15:42] <alecu> "cinco de mayo".índice(3)
[16:05] <mandel> mmcc, I updated https://code.launchpad.net/~mandel/ubuntuone-fsevents-daemon/remove-arc-dispatcher/+merge/116434 and https://code.launchpad.net/~mandel/ubuntuone-fsevents-daemon/remove-arc-commsocket/+merge/116439
[16:06] <mandel> mmcc, will get https://code.launchpad.net/~mandel/ubuntuone-fsevents-daemon/remove-arc-commsocket-server/+merge/116440 done later
[16:06] <mandel> ralsina, alecu, did we completely forget about the stand up?
[16:07] <mmcc> mandel: ok, looking at dispatcher and commsocket now
[16:08] <mandel> herb, i just read the backlog, no standup :P
[16:11] <mmcc> mandel: not important but for future reference, -retain returns self, so you can do foo = [inFoo retain];
[16:12] <mmcc> and interestingly, they've now marked all those ref counting methods as "Obsolete"
[16:13] <mandel> mmcc, since when?
[16:13] <mandel> mmcc, oh, and one question, you still have the 10.6 machine around, right?
[16:14] <mmcc> mandel yes I have it around, why?
[16:14] <mmcc> mandel: I'm not sure when they changed the docs. Might even have been yesterday
[16:14] <mandel> mmcc, because is the only one we have to test it work in 10,6 :)
[16:15] <mmcc> anyway, obsolete != deprecated, just discouraged
[16:15] <briancurtin> crap. LP is still showing prerequisite changes in this diff. that's helpful...
[16:15] <mmcc> mandel: right. for arc removal, I'll have to test with the last branch though since the test bundle doesn't link unless everything is non-arc
[16:15] <mandel> mmcc, yeah, lets keep moving this way but not in a rush, ralsina will talk in the techleads meeting about if we should ignore 10.6 or not
[16:16] <mandel> mmcc, yes, I know, but I though doing all these mini branches was better for the reviewers :)
[16:16] <mmcc> mandel: no, it's good - I'm not complaining
[16:17] <mandel> :)
[16:17] <mandel> herb, we are old schoole, look what twisted has now: from twisted.internet import inotify
[16:18] <mandel> sorry herb, ignore the last message
[16:18]  * mandel curses at his tab
[16:19] <mmcc> mandel: do you just hit tab after every word?
[16:20] <mandel> mmcc, no, but in this case I did for some reason, I wanted just to do 'he'
[16:20] <mandel> I don't understand how I work sometimes..
[16:20] <mmcc> heh.
[16:21] <alecu> mandel, mmcc: I'm thinking of updating to 10.8. Any reasons I shouldn't?
[16:22] <mandel> alecu, bugs, but it would be nice to have an intrepid soul so that we run our tests there :)
[16:22] <mandel> alecu, I might wait 'til 10.8.1
[16:22] <mmcc> alecu: fear of the unknown?
[16:22] <mmcc> but mandel pointed out you can do dual boot if you want
[16:23] <mmcc> so far I've been hearing that 10.8 is reasonably stable, compared to 10.7.0
[16:23] <alecu> ok, here I go.
[16:23] <alecu> btw: this is just awesome:
[16:23] <alecu> Twitter is currently down for <%= reason %>.
[16:23] <alecu> We expect to be back in <%= deadline %>
[16:23] <alecu> https://twitter.com
[16:23] <mmcc> heh, I saw that too.
[16:24] <mandel> alecu, maybe the use gtalk as a backend..
[16:24] <alecu> mandel: lolz
[16:27] <mandel> if youtube and reddit go down the internet might be as productive as it has never been before..
[16:35] <mmcc> mandel: just read your comment in remove-arc-commsocket about self.sockRef being a property. You're right of course, sorry about the confusion. Another reason I don't like properties and dot syntax in ObjC - it confuses old timers like me :)
[16:35] <mandel> mmcc, no problem, I had to think several times about it
[16:36] <mandel> mmcc, lets remove them as a design decision in a later step :)
[16:36] <mmcc> yeah, my complaint is that there's no way to know when you're looking at an assignment if it's going to call a method somewhere or not. You have to go poke at the header file to see if it's a property and what kind of property it is
[16:36] <mmcc> the code looks nice like python but you can't assume it does what you think it should:\
[16:37] <mandel> mmcc, well in python you could also have a property, but having properties with side effects are not good and with arc they do
[16:38] <mandel> mmcc, as in, var is retained etc..
[16:39] <mmcc> right. in python you don't have to worry about what a property call is doing to memory management
[16:41] <mandel> yep yep
[16:42] <mandel> ok, EOD for me I have started rugby training already :-/
[16:42] <mandel> mmcc, see you tonight if you are still up :)
[16:43] <mmcc> heh alright mandel, don't count on it :\
[17:01] <mmcc> hmm, no way to just poke at what certs pyOpenSSL sees by default? I can get_cert_store but the X509Store object it gives me only lets me add
[17:05] <mmcc> context - we are currently just shipping PEM files and loading them from somewhere (/etc/ssl on linux, Common AppData on windows). dobey says I shouldn't just put them in XDG_CONFIG_HOME, which makes sense since we're putting them in a global place on other platforms, but we can't write to the osx global config location without escalating privileges, which isn't OK in a sandbox…
[17:06] <mmcc> we can add certs programmatically, but I wanted to have a way to see which ones we need to install that way
[17:07] <mmcc> in the above, adding programmatically means saving them to the system keychain.
[17:09] <dobey> can we not just load them from the .app internally?
[17:11] <mmcc> dobey: hmm. yes, I guess so. Why don't we do that on Windows?
[17:13] <ralsina> mmcc: on windows we put them inside our app, more or less
[17:14] <mmcc> ralsina: ok, I guess that's what Common AppData means, even though it's not actually with the other files? Definitely still catching up here on windows distribution :)
[17:15] <ralsina> mmcc: I suspect we were following some convention of other. That part was not done by a real windows developer :-)
[17:15] <ralsina> (meaning, I did it)
[17:16] <mmcc> ralsina: heh, ok. So if just loading the cert files from within the app's Resources file is OK, that's a nice easy fix
[17:16] <ralsina> mmcc: yes, it's not meant for general usage anyway, so whatever works
[17:21] <dobey> it would be nice to use the standard system conventions though, and avoid shipping any certs at all
[17:21] <dobey> but, yay cross-platform is pain
[17:21] <mmcc> ralsina: not meant for general usage?
[17:21] <ralsina> mmcc: not for other apps
[17:21] <mmcc> ralsina: oh, ok
[17:41]  * briancurtin pharmacy/lunch
[18:22]  * briancurtin back
[19:29] <dobey> bbiab, gotta run an errand
[19:30] <mmcc> just noticed that the recent filesystem_notifications refactoring is installing the default reactor too soon again. so I'm going for lunch now…
[19:31] <mmcc> going to try to make it a working lunch
[19:31] <mmcc> but will be ask for a bit getting there
[19:31] <mmcc> s/ask/afk
[19:58] <ralsina> mmcc argh
[19:58] <ralsina> that bug will never die
[20:10] <mmcc> ralsina: yep.. the design decision that keeps on givin'
[20:59] <dobey> ralsina: if only we could just drop twisted. et voila, no more default reactor :)
[20:59]  * dobey is having plenty of not-fun at the moment with twisted :-/
[21:01]  * mmcc is right there with you
[21:01] <dobey> thanks to the fun of __import__
[21:01] <ralsina> dobey: if wishes were candy and nuts, we'd all have a merry christmas!
[21:01]  * ralsina knows that's not how that goes
[21:02] <dobey> if wishes were candy and nuts, there wouldn't be a christmas
[21:02] <ralsina> dobey: it seems like you need to get in touch with a guy in korea: http://www.codinghorror.com/blog/2012/07/the-ips-lcd-revolution.html
[21:03] <dobey> yeah i know, right
[21:03] <dobey> oh wait
[21:03] <ralsina> also, looks like I need to go parenting
[21:03] <dobey> those are 27"
[21:03] <ralsina> dobey: but this is what you really really want: http://news.ycombinator.com/item?id=4298415
[21:05] <dobey> well, on something that doesn't suck so much power, weigh 35 lbs, or be so thick
[21:05] <dobey> i want the new panasonic display, really
[21:05] <mmcc> I knew someone who had one of those IBM suckers. He said it was hard to use anything else after he got used to it
[21:06] <dobey> it is
[21:06] <dobey> same reason i kept my SGI 1600SW for so long
[21:06] <dobey> and it's still sitting in the closet. totally need to sell it
[21:10] <dobey> give me OLED
[21:12] <dobey> anyone know how to make __import__ not break the world?
[21:20] <mmcc> dobey: what's the symptom?
[21:20]  * mmcc promises nothing
[21:21] <dobey> http://pastebin.ubuntu.com/1112654/
[21:21] <dobey> twisted imports not working from something which i'm __import__()ing
[21:24] <mmcc> dobey: am I missing something or should that be globals(), locals() ?
[21:24] <dobey> mmcc: i don't know; but same error happens either way, or if they are None
[21:25] <mmcc> hrm ok…
[21:27] <mmcc> wild guess: is it a relative import name clash? is it looking for twisted.scripts in devtools.runners.twisted.py?
[21:27] <dobey> oh, maybe; but i changed level to 0 and still failed :(
[21:28] <mmcc> hmm
[21:29] <dobey> indeed, renaming got past that issue
[21:31] <dobey> mmcc: thanks
[21:31] <mmcc> dobey: hey, sure. always glad to help with some wild guessing
[21:36] <dobey> :)
[21:37] <dobey> alright, off for now. have a good evening all
[21:45] <mmcc> for the u1client tests, does trial just run each test in a thread? is there a thread pool with a set size?
[21:47] <mmcc> I ask because I'm running the full test suite and it's dying with 'too many open files' right around when it's launched about 250 threads, which makes me very suspicious of a number of things
[21:49] <mmcc> that is, many hundreds of the tests fail because of errno 24, too many open files.
[21:55] <mmcc> in other news this confused me:  from ubuntuone.platform.filesystem_notifications.monitor import (
[21:55] <mmcc>     linux as filesystem_notifications
[21:55] <mmcc> )
[21:55] <mmcc> because I first saw filesystem_notifications.FilesystemMonitor in the code and couldn't figure out where that was coming from.
[22:05] <mmcc> ok, I've fixed that reactor issue, need to test it on windows to be sure, then I'll propose it
[22:05] <mmcc> time to go for now


[00:14] <hggdh> bdmurray: something must have gone wrong on this install, check-new-release-gtk simply sits on a timeout
[00:28] <bdmurray> hggdh: with -d or not?
[00:32] <mac_> I want to report a "bug" that has been happening on Ubuntu since 12.04 and Is still happening on 13.04, it is a suspend/resume "bug"
[00:36] <hggdh> bdmurray: with -d
[01:42] <bdmurray> mac_: you'd want to use ubuntu-bug linux
[01:42] <bdmurray> hggdh: hunh
[02:11] <idproc> I'm new to ubuntu, is there anything I can do. I do not know programming.
[02:12] <idproc> Is this chat working?
[03:08] <robru> no response in 12 minutes, clearly the chat is broken.
[14:14] <njin> hggdh, hallo I'm writing testcase for JeOS on KVM, do you think that I can remove the verification step for the dimesion of the filesystem (actually it is 795 MB) but the test asks to verify that it has to be less that 500 MB
[14:15] <njin> *795/768
[14:18] <njin> aslo the verification for tha kernel return a generic instead -server, it is right ?
[14:18] <njin> aslo/also
[15:04] <hggdh> njin: yes, take it out. It has been worng for so long, that it is better to take it out
[15:05] <njin> hggdh, thanks with jibel and balloons have decided to lift up to 800
[15:06] <hggdh> OK
[15:06] <jibel> Hey hggdh , how are you?
[15:07] <hggdh> jibel: yo, ça va bien, et toi?
[15:07] <hggdh> jibel: already missing you all...
[15:07] <jibel> hggdh, bien bien :)
[15:09] <jibel> hggdh, we miss you too, but it's good to see you're still around
[15:11] <hggdh> jibel: and I plan to keep on being around :-)
[15:22] <bdmurray> hggdh: where did that upgrade timeout?
[15:22] <hggdh> bdmurray: when starting c-n-r-gtk. Weird
[15:22] <bdmurray> so you didn't even see the release notes?
[15:22] <hggdh> I did not even get the window
[15:23] <hggdh> but that happend with and without the upgrade, so I guess something went bad in the install
[17:17] <bdmurray> njin: in bug 1084854 they were surely performing a dist-upgrade so asking for the log files seems like a more appropriate response.
[17:17] <ubot2> Launchpad bug 1084854 in ubuntu-release-upgrader (Ubuntu) "upgrade crashes on code 1." [Undecided,Incomplete] https://launchpad.net/bugs/1084854
[17:34] <njin> bdmurray.ok


[19:31] <netritious> howdy
[19:36] <wrst> hello netritious
[19:36] <netritious> howdy wrst
[19:37] <wrst> how are you doing?
[19:37] <netritious> how are things?
[19:37] <netritious> doing well :)
[19:37] <netritious> brb
[19:38] <wrst> ha ha going well here also
[20:22]  * cyberanger is tired beyond belief
[20:23] <cyberanger> Afternoon
[21:17] <netritious> back
[21:17] <netritious> hey cyberanger
[21:19] <Unit193> Howdy, netritious.
[21:22] <netritious> howdy Unit193
[22:12] <netritious> forgot all the hoops you have to jump through to get wifi to work on an older laptop after installing ubuntu heh
[22:12] <Unit193> What card?
[22:41] <netritious> Unit193: it's an atheros 242x/542x
[23:35] <Unit193> Thought those had better support...


[00:33] <nixternal> lots of users have contributed highly useful and quality bug reports. this is not one of them. maybe you were looking for gripes.kde.org rather than bugs.kde.org. the former redirects directly to /dev/null rather than requiring manual intervention to accomplish that.
[00:34] <DaSkreech> nixternal: Ha ha :) that's classic geek
[00:35] <nixternal> right now I am trying to figure out how/where to install a plasmoid I made
[00:37] <DaSkreech> What X is shipping with Hardy?
[00:38] <stdin> we have <IP_ADDRESS> (2:1.4.1~git20080105-1ubuntu1) right now
[00:39] <DaSkreech> Hopefully that one doesn't crash all the time :-x
[00:40] <stdin> no, not all the time :)
[00:40] <DaSkreech> thank goodness
[00:41] <DaSkreech> I'm averaging like 5 crashes a day in Gutsy
[00:41] <hads> odd
[00:41] <DaSkreech> possibly
[00:42] <DaSkreech> but it's something about the taskbar
[00:57] <tlayton> for me in hardy, my X crashes seem to be around kaffeine and .wmv files that don't decode properly
[00:59]  * DaSkreech uses niether
[00:59] <DaSkreech> In Gutsy if I mouse over the taskbar it freezes
[01:02] <yuriy> ouch
[01:02] <DaSkreech> Yeah
[01:02] <yuriy> the whole x session does?
[01:02] <DaSkreech> no
[01:02] <DaSkreech> the whole machine
[01:02] <DaSkreech> I have to hard reset
[01:03] <DaSkreech> I've changed all the drivers
[01:03] <DaSkreech> I'm on vesa now
[01:03] <DaSkreech> I've changed kernels
[01:14] <ryanakca> wow, incredible how sluggish KDE gets after an upgrade if you don't log out/in
[01:14] <ryanakca> ooh, 4.0 is out :D
[01:14] <DaSkreech> Ha ha
[01:15] <yuriy> ryanakca: under a rock and a couple planets the last couple of days?
[01:15] <ryanakca> yep :)
[01:15] <yuriy> no planets would tell you that with 4 dozen blog posts..
[01:17] <ryanakca> yuriy: feel like joining in on the mockup contet?
[01:17] <ryanakca> *contest?
[01:17] <yuriy> don't really have any ideas
[01:17] <ryanakca> crud
[01:17] <yuriy> other than make it the ubuntu site in blue
[01:18] <ryanakca> :)
[01:18] <yuriy> are you offering ubuntu messenger bags? :D
[01:18] <DaSkreech> yuriy: I went on planetkde.org yessiday
[01:18] <ryanakca> If canonical wants to supply two of them (one for me, the other for the winner), sure :D
[01:19] <DaSkreech> I swear you paged down to the bottom it looked like the same post over and over again
[01:19] <DaSkreech> the KDE4 banner was on every post
[01:19] <DaSkreech> it was hilarious So wish I had made a screencast of it
[01:19] <yuriy> i was looking at it in akregator, must look really ridiculous on the actual site
[01:20] <yuriy> ...still there, partly
[01:20] <ryanakca> lol, every single post has the banner
[01:20] <ryanakca> they must've modified their planet to subsitute the heads with the banner
[01:21]  * ryanakca just marks all as read
[01:21] <yuriy> wow there are really no heads on teh banner posts
[01:23]  * yuriy kicks ld
[01:30] <yuriy> mornfall: have you figured out (or run into..) the issue with linking shared libraries? (I wasn't able to build until i changed ept to STATIC just now)
[02:14] <stdin> Riddell: did you upload a fix for meta-kde4 yet?
[02:41]  * stdin points Riddell to bug 182423 if he hasn't done it already
[02:41] <ubotu> Launchpad bug 182423 in meta-kde4 "reports dependency on KDE4-core version 5:47" [Undecided,New] https://launchpad.net/bugs/182423
[06:19]  * Hobbsee downloads the rest of kde4
[06:33] <Hobbsee> heya manchicken!
[06:33] <Hobbsee> oooh, marble
[06:33] <manchicken> Hiya :)
[06:34] <manchicken> I'll be a daddy in as soon as four days.
[06:34] <Hobbsee> yay!
[06:35] <manchicken> The doctor said that they'll induce labor if the baby doesn't come by Wednesday.
[06:36] <crimsun> well, congrats!
[06:41] <manchicken> Thanks :)
[06:47] <Hobbsee> new kde is strange...
[09:23]  * Hobbsee is back on kde4
[09:24] <Hobbsee> mhb: where's the kde4 polyester?
[09:26] <mornfall> yuriy: Yeah, I fixed that some time ago.
[09:26] <mornfall> yuriy: Needed -fvisibility=default.
[09:27] <mornfall> yuriy: Hm, but I forgot to commit that.
[09:30] <mornfall> yuriy: Pushed.
[10:45] <Hobbsee> who wants to take responsiblity for d3lphin?
[10:47] <toma> d3lphin?
[10:48] <Hobbsee> kde3 variant of dolphin
[10:48] <Hobbsee> we've got multiple versions in the archive
[10:49] <toma> is it stupid to ask why the o is replaced by a 3 ?
[10:51] <Hobbsee> because dolphin is the kde4 variant
[11:00] <Jucato> toma: d3lphin is a KDE 3 "fork" of Dolphin. they agreed to rename it D3lphin to distance it from Dolphin and emphasize its KDE 3'ness :)
[11:10] <toma> aha
[11:10] <toma> that explains
[11:12] <jpatrick> go Hobbsee!
[11:12] <Hobbsee> jpatrick: hm?
[11:13] <jpatrick> Hobbsee: the -ops thing
[11:13] <Hobbsee> jpatrick: ah yes.
[11:13] <Hobbsee> will probably need to have nalioth wake up again for that, though
[11:14] <Hobbsee> stdin: jussi01, Jucato, any other support people:  ping
[11:21] <jussi01> Hobbsee: ?
[11:21] <Hobbsee> jussi01: attempting to get #kubuntu-kde4 reopened.
[11:21] <Hobbsee> jussi01: the plan is to:
[11:22] <Hobbsee> have kde3 support in kubuntu, kde4 support in kubuntu-kde4, and non-GUI-specific support for the development release in #ubuntu+1
[11:22] <Hobbsee> sound reasonable?  (and checking that we're all planning on the same thing here)
[11:22] <jussi01> Hobbsee: ok, thats great imho
[11:22] <jpatrick> jussi01: we'll get it done! \o)
[11:23] <jussi01> Ok, so what do I need to do to the channel?
[11:23] <jpatrick> can you join?
[11:24] <jussi01> yes
[11:24] <jpatrick> removing the banforward might put them of...
[11:25] <Hobbsee> would probably be a reasonable idea to wait for nalioth to respond first, as he's probably just going to shut it down again if he finds out
[11:25] <Hobbsee> jussi01: can i get registered as the alternate channel contact please?
[11:25] <jussi01> Hobbsee: sure
[11:25] <Hobbsee> thanks
[11:26]  * jussi01 goes to look up chanserv to remind himself how to do that...
[11:27] <jussi01> Hobbsee: done
[11:29] <Hobbsee> jussi01: thanks
[11:29] <jussi01> Hobbsee: do I need to add you to the access list also?
[11:29] <Hobbsee> jussi01: that would be nice (level 30 would be good)
[11:31] <jussi01> Hobbsee: done. I assume we leave pricey with access?
[11:32] <Hobbsee> yeah, that's fine
[11:32] <Hobbsee> he's not about to do anythign foolish with it
[11:32] <Hobbsee> technically, they can (and are supposed) to get access anyway
[11:32] <Hobbsee> due to the namespace
[11:33] <jussi01> Hobbsee: Just fyi, I said to pricey last night to do what the irc council decides (as I thought that would include consulting you)
[11:33]  * Hobbsee won't go into a discussion about irc politics, and namespaces, and who can act, where, and how far.
[11:33]  * jussi01 hugs Hobbsee
[11:33] <Hobbsee> jussi01: council hasn't decided anything - nalioth moved on his own.  this is the problem - it's an abuse of power.
[11:33] <jussi01> ahhh
[11:34] <Hobbsee> had the council discussed, and made a decision, and consulted me about it,that would have been fine
[11:34] <jpatrick> Hobbsee: could you get nalioth to get me as contact/alternative for #kubuntu-es?
[11:34] <Hobbsee> but because a rogue staffer did it, without consulting the other group contacts...
[11:34] <jussi01> Hobbsee: ok.
[11:34] <Hobbsee> jpatrick: not really - i don't exactly have privs to do that.  as in, i think you asking and me asking will do the same thing there.
[11:34] <Hobbsee> jpatrick: (as i don't speak spanish)
[11:36] <jpatrick> Hobbsee: that TiMiDo guy's never around, and since your part of K Council, you could possibly push him over :)
[11:36] <jpatrick> I'm already at level 49 there tho
[11:36] <Hobbsee> jpatrick: tbh, i'm yet to see the channel contact having much use
[11:37] <jpatrick> yeah...
[11:49] <Riddell> Hobbsee: why did he shut it down?
[11:49] <jussi01> Hobbsee: ok, so what now? is it the plan we reopen the channel?
[11:50] <jpatrick> Riddell: "no need"
[11:50] <luca_b> Hello. I hope I'm not disturbing, but I'd like to report (if it makes sense) a likely packaging bug for the KDE 4 packages (I have filed a bug on LP as well)
[11:50] <Hobbsee> jussi01: yes
[11:50] <jussi01> Hobbsee: will you do that?
[11:50] <Hobbsee> Riddell: he didn't think we needed it, and i think he decided to go on a bit of a power trip
[11:51] <Hobbsee> jussi01: we'll see what nalioth says first, i think
[11:51] <Riddell> it's not for him to decide
[11:51] <Hobbsee> Riddell: exactly
[11:51] <Hobbsee> Riddell: it didn't even go to agreement for the council.
[11:51] <Riddell> no freenode staffers around for me to ask to fix it
[11:52] <jussi01> Hobbsee: ok then :)
[11:53] <Hobbsee> Riddell: i'm of the opinion that it would be just as bad to go and reopen it without actually speaking to the closer first.
[11:53] <Hobbsee> while jussi01 and myself now have privs (afaik)
[11:54] <jussi01> and pricey
[11:56] <Hobbsee> that being said, i just unlocked it anyway
[11:58] <blizzzek> hi
[12:01] <Hobbsee> hiya
[12:06] <k8> HAY all
[12:06] <k8> i need help
[12:06] <Hobbsee> !ask
[12:06] <ubotu> Please don't ask to ask a question, ask the question -- All On One Line, so others can read it and follow it easily --. and if anyone knows the answer they will most likely answer. :-)
[12:07] <Hobbsee> and #kubuntu is for support
[12:07] <k8> how install wine
[12:07] <k8> kubuntu amd64
[12:07] <Hobbsee> k8: you want #kubuntu
[12:07] <jpatrick> !wine > k8
[12:07] <k8> yea
[12:07] <k8> s
[12:08] <k8> how install wine
[12:08] <k8> in kubuntu
[12:08] <jpatrick> k8: please ask in #kubuntu
[12:08] <k8> ok
[12:10] <Hobbsee> interesting.  asking user support questions in a development channel, using windows and opera.
[12:10] <Hobbsee> and he goes and asks exactly the same question again.
[12:16] <jpatrick> ahoy apachelogger
[12:19] <apachelogger> Guten Morgen jpatrick
[12:20] <jpatrick> oh, das auch
[12:22] <danimo> hi
[12:22] <jpatrick> morning danimo
[12:23] <apachelogger> Hallo danimo, gibts schon nen Termin für 4.0.1? ;-)
[12:30] <luca_b> Apparently there is a bug in packaging for KDE 4 (unsure if it affects hardy) - Dolphin and other applications cannot find servicemenus/plugins therefore even basic operations are unavailable - LP https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/182501 . Sorry for the repeated message and if it is known, please disregard it. I can help trying to find the root cause if needed.
[12:30] <ubotu> Launchpad bug 182501 in kde4libs "KDE4 applications cannot load their plugins" [Undecided,New]
[12:33] <toma> i can confirm it works ok on a 4.0.0 svn kde4, so it is a kubuntu bug
[12:35] <toma> danimo, Riddell: ^
[12:37] <fabo> not the rpath issue on k-c-d ? (Urs)
[12:39] <fabo> "KPluginLoader: LD_LIBRARY_PATH Issues"
[12:59] <Hobbsee> ah, goody, my kde4 bug is listed as fixed in 4.0.1
[13:26] <sebastian^> hi folks :)
[13:34] <luca_b> fabio: AFAICS LD_LIBRARY_PATH is set in the Kubuntu startkde for KDE4
[13:35] <luca_b> if is there anything I can do to track what a KDE app does to locate plugins et al, let me know
[13:38] <nosrednaekim> heh... anyone seen the Tuxmachine KDE4 poll?
[13:49] <danimo> apachelogger: packetier mal lieber branch :)
[13:49] <danimo> apachelogger: lohnt immer
[13:50] <apachelogger> danimo: ich bin noch daran die issues in den .0 paketen zu beseitigen :S ... dann werde ich patches aus plasma reinpacken, das ding crashed fürchterlich oft
[13:50] <apachelogger> bzw. wüsste ich garnicht wohin mit den branch paketen ;-)
[13:50] <danimo> apachelogger: bitte nimm die suse patches für kickoff rein, das sieht ja scheusslich aus im default
[13:52] <apachelogger> danimo: da wirft schon jemand ein auge drauf, soweit ich das aus den meeting log von gestern rausgelesen habe
[13:53] <mhb> is there anything besides the branding what is in the suse kickoff patches and not in upstream?
[13:53] <mhb> if so, why?
[13:54] <apachelogger> mhb: because suse loves to patch stuff ;-)
[13:54] <mhb> can't they post it upstream?
[13:54]  * apachelogger adds yet another todo item: have a look at suse packages
[13:54] <danimo> mhb: well, "upstream" made it ugly in the first place
[13:55] <danimo> mhb: suse just restored what they had in the original kickoff
[13:55] <danimo> mhb: which imho looks a lot better
[13:55]  * apachelogger is hoping plasma is becoming a lot better in 4.1
[13:55] <luca_b> Is there a way to see how plugin loading is going on in a KDE app? I'm trying to track down the cause of the bug I posted earlier
[13:56] <mhb> danimo: frankly, I would not want KDE4 packages to become so patched like KDE3 was
[13:56] <danimo> mhb: well, KDE 3 was a bit overpatched indeed
[13:56] <danimo> mhb: we can try to talk it over with aseigo
[13:56]  * apachelogger doesn't like patching at all
[13:57] <apachelogger> only good reason to patch is bugfixes or branding
[13:58] <mhb> danimo: I'd vote for talking it over
[13:58]  * apachelogger prepares to upload kde-workspace 4:4.0.0-0ubuntu2
[14:01]  * jussi01 hugs apachelogger
[14:01] <apachelogger> huh
[14:01] <apachelogger> jussi01: what for?
[14:02] <danimo> mhb: let's try tonight, aseigo is asleep
[14:03] <jussi01> apachelogger: the upload :)
[14:03] <apachelogger> jussi01: hehe, do you even know what it contains? ;-)
[14:04] <jussi01> apachelogger: nope, but all uploads are genereally good :D
[14:04] <apachelogger> indeed :D
[14:05] <emonkey> *g*
[14:07] <apachelogger> stdin: I don't think we should have libqca2-plugin-ossl in recommends for kopete-kde4
[14:07] <apachelogger> should go depends
[14:07] <apachelogger> you can't use any encrypted jabber connection without it
[14:07] <apachelogger> which makes it impossible to use google talk for example
[14:08] <jpatrick> apachelogger: that package does not exist
[14:08] <apachelogger> jpatrick: in gutsy it doesn't
[14:08] <apachelogger> needs backport, btw... if you want to have a look at it ;-)
[14:08] <jpatrick> that explains it
[14:09] <apachelogger> libqca2 needs backport, current in gutsy is ~beta7, needs final
[14:09] <apachelogger> and the plugin-ossl needs backport as well
[14:09] <jpatrick> well, the rdepends don't look like it will cause a probably
[14:09] <jpatrick> problem*
[14:10] <jpatrick> file a request and I'll ack ;)
[14:11] <apachelogger> jpatrick: do a testbuild first :P
[14:11]  * apachelogger doesn't do backport requests without testing
[14:12]  * jpatrick uploads to ppa
[14:13] <apachelogger> jpatrick: btw, do we spell it KDE 4 or KDE4?
[14:14] <jpatrick> apachelogger: KDE 4
[14:14] <apachelogger> ok
[14:14]  * apachelogger fixes kdenetwork
[14:15]  * jpatrick prepares backports
[14:16] <jpatrick> libqca2 and libqca2-plugin-ossl it is?
[14:16] <apachelogger> jpatrick: from looking at the deps, yeah ;-)
[14:16] <jpatrick> ok
[14:21] <jpatrick> apachelogger: http://pastebin.ubuntu.com/3523/
[14:23] <apachelogger> jpatrick: line41?
[14:28] <jpatrick> apachelogger: uploading to PPA
[14:28] <jpatrick> (mine)
[14:28]  * apachelogger is testbuilding kdenetwork with fixed icon paths
[14:30] <apachelogger> jpatrick: is there any policy on how to handle upstream bugs which got reported in lp?
[14:30]  * apachelogger tends to close them as invalid and send the reporter upstream
[14:34] <jpatrick> apachelogger: forward them upstream
[14:35] <jpatrick> apachelogger: and link it on the LP one
[14:38] <apachelogger> god is that useless -.-
[14:43]  * jpatrick wonders where the upload went...
[14:46] <apachelogger> cool, launchpad now also eats uploads? :P
[14:48] <Hobbsee> apachelogger: soyuz gets hungry, yes
[14:48] <apachelogger> hrrhrr :D
[14:48] <apachelogger> we have the hungriest systems ever
[14:53] <Hobbsee> yup
[14:53]  * Hobbsee sacrifices a goat
[14:55] <jpatrick> Hobbsee: can you add me to ~k-members-kde4?
[14:56]  * apachelogger notes that building kdenetwork takes way too long
[14:56] <Hobbsee> done
[14:56] <jpatrick> thank you
[14:56] <Hobbsee> wow, nice archive size there!
[14:57] <apachelogger> hehe
[14:57] <apachelogger> Hobbsee: any idea when one can remove packages from ppa?
[14:57] <jpatrick> es ist nicht unsere Schuld...
[14:57] <Hobbsee> apachelogger: sometime when the planets all align, the mountains fall into the sea, and openoffice builds on all arches, without fail.
[14:57] <Hobbsee> every time
[14:58] <apachelogger> omg :D
[14:59] <apachelogger> jpatrick: naja, meine.... ein kleines bisschen zumindest, ich habe geholfen die 50Mib wallpapers in das KDE SVN hochzuladen ;-)
[14:59] <apachelogger> now that is a sentence :D
[14:59] <apachelogger> woohoooo
[14:59] <apachelogger> kdentwork is already running debhelpers
[15:00] <jpatrick> apachelogger: seems PPA won't accept this package..
[15:01] <Hobbsee> jpatrick: seems it's fallen over, yes
[15:01] <apachelogger> jpatrick: any reason for rejection?
[15:01] <apachelogger> cool
[15:01] <jpatrick> apachelogger: no, no reject, just disappeared..
[15:01] <apachelogger> very nice
[15:01] <apachelogger> so it's really hungry today
[15:06] <jpatrick> apachelogger: I'm installing prevu on the family computer, hopefully it won't eat it there
[15:07]  * apachelogger prepares for kdenetwork 4:4.0.0-0ubuntu2 upload
[15:42] <LjL> 7msg ubotu logs
[15:42] <jpatrick> apachelogger_: ok, qca2 pbuilding..
[15:42] <apachelogger_> hooray
[15:43] <apachelogger_> LjL: you should try a slash instead of a 7 :P
[15:43] <jpatrick> (just started)
[15:43] <apachelogger_> qca shouldn't take that long
[15:47] <stdin> apachelogger_: I thought qca was already backported for RC2...
[15:48] <apachelogger_> dunno, I haven't had a look into that issue
[15:48] <apachelogger_> http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=qca&searchon=names&subword=1&version=gutsy-backports&release=all
[15:48] <apachelogger_> stdin: doesn't look like it
[15:49] <jpatrick> in process now
[15:50] <apachelogger_> my pc is lagging -.-
[15:58] <jpatrick> apachelogger_: qca2 => done
[15:58] <apachelogger_> jpatrick: build? backport? or ppa? ;-)
[15:59] <jpatrick> build
[16:00] <apachelogger_> jpatrick: got a log for the backport request?
[16:00] <jpatrick> ops
[16:01] <jpatrick> meh
[16:01] <apachelogger_> oioi
[16:01] <jpatrick> I'm part of backports team ;P
[16:01] <apachelogger_> well, just backport, then :P
[16:01] <jpatrick> what to skip ppa then?
[16:02] <jpatrick> want*
[16:02] <apachelogger_> jpatrick: well, do both
[16:03] <apachelogger_> argh
[16:03]  * apachelogger_ kills dolphin
[16:03] <apachelogger_> where does that thing get the create*'s from
[16:06] <jpatrick> apachelogger_: bug #182605
[16:06] <ubotu> Launchpad bug 182605 in gutsy-backports "Please backport qca2 (2.0.0-3) from Hardy" [Undecided,In progress] https://launchpad.net/bugs/182605
[16:07] <apachelogger_> hm
[16:07] <apachelogger_> karma
[16:07] <apachelogger_> I say karma!
[16:07] <apachelogger_> jpatrick++
[16:07] <apachelogger_> ~part
[16:08]  * jpatrick uploads to ppa
[16:09] <apachelogger_> ha!
[16:09] <apachelogger_> I got it
[16:10] <jpatrick> "Checking for QCA 2.0 ... yes"
[16:10]  * apachelogger_ starts dancing on the table
[16:11] <jpatrick> http://pastebin.ubuntu.com/3526/
[16:18] <jpatrick> apachelogger_: ARG, ppa is still eating uploads...
[16:20] <apachelogger_> jpatrick: well, screw it for now, we will have to do an almost complte update to ppa when I'm done with the icon fixing
[16:20]  * apachelogger_ tries getting some rbm->create entries for dolphin
[16:23] <jpatrick> apachelogger_: bug #182610
[16:23] <ubotu> Launchpad bug 182610 in gutsy-backports "Please backport qca2-plugin-ossl (0.1~20070904-3) from Hardy" [Undecided,In progress] https://launchpad.net/bugs/182610
[16:23] <apachelogger_> jpatrick: should I comment on these?
[16:24] <apachelogger_> stdin: ping
[16:24] <stdin> apachelogger_: pong
[16:25] <apachelogger_> stdin: why does libkonq5 depend on libkonq5-tempaltes | kdesktop?
[16:25]  * apachelogger_ is wondering about the kdesktop part
[16:26] <jpatrick> apachelogger_: dunno, just so you know they're there tho ;)
[16:26] <stdin> maybe because it can be installed along side kdebase-bin-kde3? not sure
[16:26]  * apachelogger_ doesn't think so
[16:26] <apachelogger_> actually it's kinda bad
[16:27] <apachelogger_> libkonq5-templates provides the rbm menu create_new stuff
[16:27] <apachelogger_> which is not going to be installed if kdesktop is already available
[16:27] <apachelogger_> and then you have no items in the create_new menu
[16:27] <stdin> apachelogger_: you'll have to poke Riddell about that one, I can't see why it's like tha
[16:27] <apachelogger_> Riddell: pling pling
[16:28] <Riddell> hmm?
[16:28] <apachelogger_> Riddell: why does libkonq5 depend on libkonq5-templates | kdesktop?
[16:29] <apachelogger_> kdesktop's are located in /usr/share/templates, while libkonq5 stores them in /usr/lib/kde4/share/templates
[16:29] <Riddell> as stdin says, which is taken from debian but should indeed be changed for us
[16:29] <apachelogger_> k
[16:29]  * apachelogger_ fixes
[16:40] <apachelogger_> Riddell: btw, there is an inconsistency in the maintainer tag ... is it Kubuntu Developers, or the MOTU?
[16:42] <Riddell> apachelogger: I don't care
[16:42] <apachelogger> will change to Kubuntu Developers then
[16:42] <apachelogger> seems more appropriate IMO
[16:42] <Riddell> maintainer tags are essentially unused in ubuntu
[16:42] <apachelogger> k
[16:42] <Riddell> anywhere that does use them is a bug in my opinion
[16:56] <jjesse> morning :)
[16:58] <jpatrick> morning jjesse
[17:07] <jjesse> hello jpatrick
[17:07] <jjesse> sorry notifications aren't working in kde4 and konverstation (the on screen display)
[17:08] <Nightrose> jjesse: yea same here - but amarok´s osd is working - which is strange since it should be about the same code
[17:09] <apachelogger> hmmmmmmm
[17:09] <jjesse> yeah i noticed that.... wonder why
[17:09] <apachelogger> so maybe I should investigate on this now
[17:09] <apachelogger> that's a no-go that jjesse doesn't get mornings
[17:10] <stdin> apachelogger: if I'd had known (ie been here when) you uploaded kdebase-workspace I'd have shown you bug 182093
[17:10] <ubotu> Launchpad bug 182093 in kdebase-workspace "Patch to prevent GTK+ applications with system tray icons from crashing in KDE 4.0" [Undecided,Confirmed] https://launchpad.net/bugs/182093
[17:10] <jjesse> some people would say i don't get evenings either :0
[17:10] <apachelogger> stdin: yeah, I saw that earlier today and smashed my head on the table ;-)
[17:10] <apachelogger> but I think there will be other issues I have to fix in -workspace
[17:12] <stdin> the GTK issue is a real problem for a lot of people (or so I've heard)
[17:12] <stdin> I tested pidgin (after installing it) and it went boom! :P
[17:12] <apachelogger> hm
[17:12] <apachelogger> ok
[17:12] <apachelogger> will do asap
[17:12] <apachelogger> I think I'll include a mega patch for plasma stuff
[17:13] <stdin> yeah, mega patches are good :)
[17:13] <apachelogger> aaron fixed quite some stuff while kde was frozen and uploaded everything at once
[17:13] <apachelogger> well, I prefer them small and handy :P
[17:13] <apachelogger> but better to have a mega patch in .0 than a totally b0rked plasma
[17:13] <apachelogger> Nightrose: right? ;-)
[17:13] <Nightrose> right ;-)
[17:14] <apachelogger> muhahahaha: ping
[17:15] <muhahahaha> hm
[17:15] <Nightrose> oO apachelogger´s alter ego arrived ;-)
[17:15] <muhahahaha> this is a konversation bug
[17:15] <muhahahaha> from what I see, it can't detect whether a screensaver is active
[17:15] <muhahahaha> and in this case it just assumes the screensaver is active
[17:15] <muhahahaha> hence doesn't show the OSD
[17:16] <muhahahaha> only possible solution would be to patch konversation so it assumes the saver is inactive unless it can detect it
[17:18] <muhahahaha> Nightrose, jjesse: do you think this issue is worth overriding konversation's default behaviour?
[17:18] <Nightrose> hmm it is annoying for me to get a beeb but no osd on hili
[17:18] <Nightrose> but changing the default... hmm
[17:19] <Nightrose> would it do any harm?
[17:20] <muhahahaha> well
[17:20] <muhahahaha> I don't know
[17:20] <muhahahaha> honestly
[17:20] <jjesse> does not detect the screensaver because of plasma?
[17:20] <jjesse> is that what is happening?
[17:20] <muhahahaha> yes
[17:20] <muhahahaha> it queries kdesktop
[17:20] <muhahahaha> via dcop
[17:20] <muhahahaha> neither of them is running
[17:20] <jjesse> ah
[17:20]  * jjesse learns something
[17:20] <muhahahaha> so, basically patching konversation to use the osd when it can't detect activity would even have an advantage ;-)
[17:21] <muhahahaha> you can get an osd on gnome and xfce and fluxbox and $desktop
[17:22] <jjesse> ah that owuld be on gnome i don't get the osd that i do on kde
[17:22] <jjesse> things are making sense
[17:23] <muhahahaha> the problem is, I think konversation doesn't show the OSD for secruity reasons
[17:23]  * muhahahaha dgets konversation and takes a look in the code
[17:24] <jjesse> by default it doesn't show osd for security reasons?
[17:24] <muhahahaha> I think so
[17:24] <muhahahaha> well
[17:24] <muhahahaha> the thing is
[17:24] <muhahahaha> if it can't detect whether a screensaver is running
[17:25] <muhahahaha> it will always show the OSD
[17:25] <jjesse> it shouldn't show osd when a screensaver is running
[17:25] <muhahahaha> any maybe one can workaround a lock using the OSD
[17:25] <muhahahaha> or at least one can read messages
[17:25] <muhahahaha> jjesse: that's the point
[17:26] <jjesse> it makes sense slowly
[17:26] <muhahahaha> comment in src says: "err on the side of safety."
[17:27] <muhahahaha> well
[17:27] <muhahahaha> I personally think... we shouldn't do anything
[17:27] <nixternal> isn't Sho_ currently working on a KDE 4 Konversation?
[17:27] <Jucato> I think Sho_ would be interested in knowing about this, since he intends to have a 1.1 release before we release hardy
[17:27] <Jucato> nixternal: not yet I think
[17:27] <Jucato> #konversation
[17:27] <nixternal> hrmm, wonder why
[17:28] <Jucato> he just finished porting yakuake :)
[17:28] <muhahahaha> Jucato: he would have to implement a check for krunner
[17:28] <muhahahaha> not worth IMO
[17:28] <Jucato> which was almost a rewrite according to him... and konvi is probably going to go worse :/
[17:28] <nixternal> no doubt
[17:29]  * Jucato isn't familiar with konvi innards... just enjoys using it :)
[17:29] <stdin> Jucato: in svn? (yakuake)
[17:29] <Jucato> of course :)
[17:29] <nixternal> irssi ftw :p
[17:29]  * stdin gets it
[17:30] <blueyed> "kfmclient exec http://example.com" does not work for me in KDE3 on Hardy anymore.. it seems to try using konqueror4, which fails to start.
[17:30] <blueyed> Additionally I cannot enable debug output (using kdebugdialog) for kfmclient.
[17:31] <blueyed> It appears to be the same method as used for "alt-f2, url", which really sucks to be broken.
[17:32] <muhahahaha> Nightrose: can you please check whether amarok shows the OSD even if a screensaver is on?
[17:32] <Nightrose> muhahahaha: will do - give me a sec
[17:33] <stdin> blueyed: does konqueror-kde4 start?
[17:34] <muhahahaha> nixternal: quassel ftw!
[17:34] <blueyed> stdin: yes, konqueror-kde4 starts, but it fails to do so through kfmclient/alt-f2
[17:35] <Nightrose> muhahahaha: it does not
[17:35] <muhahahaha> Nightrose: it doesn't show the OSD when the screensaver is on????
[17:35] <Nightrose> right
[17:35] <muhahahaha> rather strange
[17:36]  * muhahahaha dgets amarok and diggs in it's src
[17:36] <stdin> blueyed: hmm, "kfmclient exec http://google.com" opens konqueror kde4 here (but I'm in a kde4 session)
[17:36]  * Nightrose gets a coffee
[17:37] <muhahahaha> blueyed: I think your env vars are mixed
[17:37] <blueyed> stdin: I'm getting the bumping icon, but nothing happens.. "kfmclient-kde4 exec" however works..
[17:37] <blueyed> (starts firefox, as configured)
[17:38] <blueyed> muhahahaha: does kfmclient in KDE3 work for you?
[17:38] <iRon> blueyed: same for me.. i've installed hardy alpha 3, and kfmclient exec doesn't works.
[17:38] <muhahahaha> blueyed: I don't have a kde3 to test
[17:38] <muhahahaha> iRon: strange thing
[17:38] <muhahahaha> really strange thing
[17:38] <blueyed> iRon: thanks for confirming.
[17:38] <muhahahaha> so
[17:39] <muhahahaha> please someone paste the output of `export`
[17:39] <fdoving> blueyed: do you have any other konquerors running?
[17:39] <stdin> what about "kfmclient openURL" ?
[17:39] <yuriy> port of yakuake? yay!
[17:39] <iRon> stdin: Syntax Error: Unknown command 'http://google.com'
[17:40] <iRon> stdin: on `kfmclient http://google.com'
[17:40] <muhahahaha> kfmclient exec http://kde.org
[17:40] <muhahahaha> _exec_
[17:40] <stdin> iRon: no "kfmclient openURL http://google.com/"
[17:40] <muhahahaha> try both :P
[17:40] <blueyed> muhahahaha: my env: http://pastebin.com/m56d1b5ff
[17:40] <iRon> stdin: !! openURL works just fine
[17:41] <iRon> stdin: `exec' does not
[17:41] <muhahahaha> cool
[17:41] <blueyed> same for me.
[17:41] <muhahahaha> blueyed: plz also `cat ~/.kde/share/config/kdeglobals && cat ~/.kde4/share/config/kdeglobals`
[17:41] <blueyed> fdoving: no other konquerors running.
[17:42] <fdoving> blueyed: not even preloaded?
[17:42] <blueyed> fdoving: not in "ps aux" at least
[17:42] <muhahahaha> meh
[17:42] <muhahahaha> Nightrose: now I have to write a mail because of you :P
[17:42] <Nightrose> muhahahaha: ? why? ;-)
[17:43] <muhahahaha> either we deactivate the check and live with the security issue
[17:43] <muhahahaha> or we don't and live with a br0ken osd
[17:44] <blueyed> muhahahaha: www.codeprobe.de/tmp/kdeglobals.tmp
[17:44] <Nightrose> hmmm - muhahahaha can´t you add a check for kde4´s screensaver stuff?
[17:45] <muhahahaha> Nightrose: are you going to hack something reliable up?
[17:45] <pdenapo> HI, I've been testing the kdelibskdebase 3.5.8 /packages por Hardy alpha3 and the have a change that I don't like: they create a lot of icons in the desktop for all the folders in the filesystem, I think this will be rather confusing for non technical users. I think it would be better to keep the desktop clean
[17:46] <muhahahaha> blueyed: very strange
[17:46] <Nightrose> muhahahaha: don´t think so :P
[17:46] <muhahahaha> Nightrose: get someone to do it, and I'll go with that solution :P
[17:46]  * Nightrose looks at apachelogger and nixternal ;-)
[17:47] <muhahahaha> I has no time for c++ hacking
[17:47] <blueyed> Is there a way to debug kfmclient? kdebugdialog (from kde4 it seems) does not enable output of kddebug output..
[17:47] <muhahahaha> I already has a lot of work with debian :P
[17:47] <Nightrose> ;-)
[17:47] <muhahahaha> blueyed: what does `kfmclient --version` say?
[17:48] <blueyed> muhahahaha: qt 3.3.7, kde 3.5.8, kfmclient 2.0
[17:48] <muhahahaha> cool
[17:49] <muhahahaha> so why does it try to launch konqueror4 -.-
[17:49] <muhahahaha> blueyed: well, openURL is working?
[17:49] <iRon> muhahahaha: i've no installed kde4.. but `kfmclient exec URL' doesn't works though
[17:50] <blueyed> muhahahaha: yes
[17:50] <muhahahaha> so
[17:50] <muhahahaha> kfmclient in kde3 just doesn't support exec :P
[17:50] <iRon> :)
[17:50] <blueyed> muhahahaha: ..anymore. It worked before.. and it's what alt-f2 seems to use..
[17:50] <fdoving> here is the source of kfmclient http://websvn.kde.org/branches/KDE/3.5/kdebase/konqueror/client/kfmclient.cc?revision=569345&view=markup
[17:51] <muhahahaha> blueyed: so alt-f2 -> http://kde.org doesn't work anymore?
[17:51] <blueyed> muhahahaha: exactly.
[17:51] <fdoving> that's basically what kfmclient exec does
[17:51] <fdoving> kfmclient exec uses krun.
[17:51] <iRon> muhahahaha: i guess it does.. and i think something is wrong with MIME or something like this.. for me `kfmclient exec URL' starts `kate' :)
[17:51] <fdoving> while openUrl does not.
[17:51] <blueyed> also clicking URLs here in konvi does not work anymore
[17:51] <muhahahaha> iRon: depends on the url ;-)
[17:52] <iRon> muhahahaha: any http://..
[17:52] <muhahahaha> doesn't depends on the protocol
[17:52] <muhahahaha> but the server sent mime
[17:52] <muhahahaha> at least it should ;-)
[17:53] <blueyed> fdoving: I have the source already through "apt-get source" or are you referring to something specific?
[17:54] <fdoving> blueyed: i'm referring to the kfmclient.cc file. you can read from it what exec does, and what openUrl does.
[17:55] <blueyed> fdoving: so krun is broken?
[17:55] <fdoving> probably not.
[17:56] <fdoving> if you installed konqueror-kde4 it could be that it tries to be the default browser for http and https things, or that it tries to be the default for html pages. for example.
[17:56] <fdoving> i'd check the mime-settings first.
[17:56] <fdoving> its very unlikely that anything in kde 3.5.x suddenly breaks like that.
[17:57] <fdoving> code-wise anyway.
[17:57] <blueyed> fdoving: ok, but starting konqueror-kde4 itself works under kde3. will check mime stuff.
[17:57] <fdoving> kfmclient kde3 won't be able to communicate with konqueror4 properly.
[17:58] <fdoving> as kfmclient3 speaks dcop and konqueror4 speaks dbus.
[17:59] <blueyed> Ok, that explains it then. Configuring "konqueror" as default browser for http(s) in "default application" works.
[18:01] <fdoving> bbl, kid screams.
[18:15] <blueyed> The problem is caused by /usr/share/applications/kde4-kfmclient_html.desktop (from the konqueror-kde4 package). Removing just this file fixes it: konqueror3 then gets used instead
[18:16] <stdin> that file just runs "kfmclient-kde4 openURL %u text/html" where "%u" us the URL
[18:23] <blueyed> stdin: which fails with "ASSERT failure in KAuthorizedPrivate(): "There has to be an application name set (See QCoreApplication::instance()->setApplicationName)", file /build/buildd/kde4libs-4.0.0/kdecore/kernel/kauthorized.cpp, line 195"
[18:26] <jpatrick> apachelogger: jabber on kopete-kde4 now works
[18:26] <apachelogger> jpatrick: without rebuilding of kdenetwork?
[18:26] <jpatrick> apachelogger: no..
[18:26] <apachelogger> ok, we have to backport for the icon fixes anway
[18:27] <jpatrick> "Login failed with unknown reason."
[18:27] <apachelogger> cool :S
[18:27] <jpatrick> better than qca tcl failed to load
[18:28] <apachelogger> well, unknown < known ;-)
[18:28] <jpatrick> wait...
[18:28] <jpatrick> I'm online on jabber! :D
[18:29] <apachelogger> Oo
[18:29] <apachelogger> jpatrick: login succeeded with unknown reason? ;-)
[18:29] <jpatrick> apachelogger: wrong passwd
[18:30] <apachelogger> ic
[18:30] <jpatrick> yep, it works tm
[18:30] <ryanakca> Hmm.. who's the usability person for Kubuntu? seele ?
[18:32] <mornfall> Evening.
[18:33] <ryanakca> hey mornfall
[18:34]  * apachelogger is testbuilding a mega patch for plasma
[18:35] <blueyed_> "kfmclient openURL http://kde.org text/html" also fails in a kde4 session for me..
[18:36] <stdin> try kfmclient4 ?
[18:36] <blueyed-kde4> I've meant that one, yes.
[18:37] <stdin> hmm, "kfmclient openURL http://kde.org text/html" open konqueror fine in my kde4 session
[18:52] <blueyed-kde4> stdin: I bet it won't anymore, if you configure it to use "firefox" as default browser.. that's the code path which causes the ASSERT
[19:08] <apachelogger> blueyed-kde4: didn't you do that?
[19:08]  * apachelogger remembers that firefox was default for kde4
[19:09] <blueyed-kde4> apachelogger: it does not matter what you set in "in the following browser", as long as you do not use the default "in an application based on the contents of the URL".  Do you think the assertion is caused because a script is executed?
[19:12] <apachelogger> blueyed-kde4: I wouldn't be surprised
[19:12] <blueyed-kde4> but then it should fail with konqueror..
[19:13]  * blueyed-kde4 wonders what qApp is about?!
[19:14] <blueyed-kde4> Is this an instance of the current application?
[19:14] <apachelogger> stdin: I can't apply the plasma patch, breaks icon aligning
[19:15] <stdin> apachelogger: we'll have to wait until .1 for that then, but we should get the gtk patch in (and probably work on the kdesu issue)
[19:17] <apachelogger> oh
[19:17] <apachelogger> stdin: kdesu is in workspace?
[19:17] <apachelogger> mhh
[19:17] <apachelogger> kdelibs
[19:17] <apachelogger> well
[19:18] <apachelogger> stdin: I think for now linking kdesu to kdesudo should do the trick
[19:18] <apachelogger> unless we find someone who wants to port it to sudo, or port kdesudo to qt4
[19:18] <stdin> it's in libs, but it should be a higher priority than getting extra patches in probably
[19:18] <stdin> (and  I many be making some headway)
[19:19] <stdin> it will at least get it to use sudo for now, until kdesudo is ported
[19:19] <stdin> WOOT! found it :)
[19:20] <stdin> we need to pass "-DKDESU_USE_SUDO_DEFAULT" to cmake
[19:20] <nosrednaekim> yes!
[19:20] <nosrednaekim> :)
[19:20]  * apachelogger opens konsole
[19:20] <stdin> or -DKDESU_USE_SUDO_DEFAULT=true anyway
[19:21] <apachelogger> *fixing*
[19:21]  * stdin does a little victory dance (and hopes that it's not in vain)
[19:24]  * apachelogger testbuilds
[19:31] <stdin> when you upload (if it works) have it close bug #182319
[19:32] <ubotu> Launchpad bug 182319 in kdebase-runtime "kdesu asks for root password" [Undecided,New] https://launchpad.net/bugs/182319
[19:35] <apachelogger> stdin: yep
[19:36] <jjesse> nixternal: did you see the proposed schedule mdke created on the mailing list?
[19:52] <apachelogger> stdin: what to do with bug 173364 and bug 181470
[19:52] <ubotu> Launchpad bug 173364 in kdegraphics-kde4 "package kscan-kde4 4:3.96.0-1ubuntu1 failed to install/upgrade: trying to overwrite `/usr/lib/kde4/lib/kde4/kscanplugin.so', which is also in package kde4graphics" [Undecided,New] https://launchpad.net/bugs/173364
[19:52] <ubotu> Launchpad bug 181470 in kdegraphics-kde4 "[kde4-gutsy]bug in installation of some application" [Undecided,New] https://launchpad.net/bugs/181470
[19:52]  * stdin looks
[19:52] <apachelogger> stdin: do you think we should conflict with the old packages?... the problem then would be that _every_ package has to conflict with the old package
[19:52] <apachelogger> since we only had big monster packages in gutsy
[19:53] <stdin> I see #182452 is invalid right now, kde4graphics = old pre-RC package
[19:53] <apachelogger> stdin: yeah
[19:53] <apachelogger> but I think it is in the archive
[19:53] <apachelogger> stdin: http://packages.ubuntu.com/gutsy/kde/kde4graphics
[19:54] <apachelogger> Riddell: what do you think?
[19:54] <stdin> conflicting/replacing may be a way, but that's a mighty 'ol headache to do
[19:54] <apachelogger> exactly -.-
[19:55] <apachelogger> well
[19:55] <apachelogger> I still have to touch most of the packages for icon fixes
[19:55] <apachelogger> -workspace needs the gtk fix
[19:55] <stdin> and it may not be worth it, to make everyone download the packages again just for a small amount of people
[19:55] <apachelogger> libs needs sudo
[19:55] <stdin> for the packages you're working on, go for it :)
[19:55] <apachelogger> ok
[19:56] <stdin> if you already have to upload a fix, may as well fix some small issues too
[19:56] <apachelogger> true
[19:58] <stdin> thing is that the pre-packages weren't really meant to be upgradable, or rather, we didn't take any special steps to avoid clashing (instructions were always "Remove old packages first...."
[20:08] <stdin> wooh, my karma has gone up 383 since yesterday :p
[20:09] <jjesse> i never understand how karma is calcuated
[20:10] <stdin> jjesse:  https://help.launchpad.net/KarmaCalculation
[20:11] <toma> stdin: just don't think you are ready for your reincarnation now ;-)
[20:12] <jjesse> hrmm i wonder if that normalization is the reason mine never seems to change
[20:12] <jjesse> cause i have some points in all but mostly in bug tracking
[20:16] <jjesse> hrm why does nothing that require admin rights work under kde4?  keeps giving me invalid password
[20:16] <stdin> see bug #182319
[20:16] <ubotu> Launchpad bug 182319 in kdebase-runtime "kdesu asks for root password" [Undecided,In progress] https://launchpad.net/bugs/182319
[20:17] <jjesse> ah you've been talking about that all day havne't you?
[20:17] <stdin> yeah ;)
[20:19] <stdin> actually, I should change that to be in kde4libs...
[21:18] <apachelogger> ~professor
[21:18] <insanity> Good news everyone!
[21:18] <apachelogger> I have a working kdesu with sudo :D
[21:18] <apachelogger> hrrhrr
[21:19] <stdin> all it took was searching through tens of files of code to finally see that "su.h" was where it was set :/
[21:19] <apachelogger> :S
[21:20] <apachelogger> stdin: I actually read it once when running ccmake
[21:20] <apachelogger> totally forgot about it
[21:20] <stdin> it was one of those "I'm a moron, and I know it" moments :p
[21:20] <apachelogger> I know them... too well ....
[21:31] <apachelogger> stdin: uploading right now
[21:31] <nixternal> writing plasmoids are fun :p
[21:32] <stdin> apachelogger: great :)
[21:32] <nixternal> who will be the first to write the python engine for plasma?
[21:32] <apachelogger> nixternal: a python engine?
[21:33] <nixternal> ya, you can't write pythonized plasmoids yet that I know of
[21:33] <apachelogger> Oo
[21:33] <apachelogger> nixternal: using kross?
[21:33] <nixternal> no
[21:33] <nixternal> qtscript
[21:33] <nixternal> which blows kross out of the water
[21:33] <apachelogger> hm
[21:33] <apachelogger> *shrug*
[21:33] <nixternal> speed wise
[21:33] <apachelogger> there is a ruby plasmoid, ruby is better anyway, so :P
[21:34] <nixternal> kross definitely has more scripting languages, but I am sure plasma/qtscript will soon enough
[21:34] <nixternal> aseigo said they are fairly easy to write so I am sure someone will do so son
[21:34] <nixternal> s/son/soon
[21:34] <apachelogger> cool
[21:34] <nixternal> where is the ruby plasmoid?
[21:34] <Tm_T> hi kids
[21:34] <nixternal> I created a playground-plasma package that has all of the script plasmoids and they are all javascript
[21:35] <nixternal> ahh, ruby-clock
[21:35] <nixternal> wonder why it isn't under scripts
[21:36] <apachelogger> Tm_T: hey mom
[21:36] <nixternal> haha
[21:36] <apachelogger> woah
[21:36] <apachelogger> https://edge.launchpad.net/ubuntu/+source/kde4libs/
[21:36] <apachelogger> welcome to the wonderful world of sudo
[21:36] <apachelogger> muhahahahaa
[21:37] <nixternal> kdesudo hasn't been ported yet?
[21:37] <apachelogger> nope
[21:37] <nixternal> ahh
[21:37]  * nixternal goes out for a bit
[21:37] <nixternal> have fun!
[21:38]  * apachelogger doesn't even think it needs to be ported, just get upstream to add an icon to kdesu with sudo and everything is fine
[21:39]  * apachelogger testbuilds kdegraphics
[21:40] <vorian> afternoon :)
[21:41] <seezer> are all hardy-releases of kde4 packages going to be backported to gutsy?
[21:42] <stdin> seezer: until work on hardy+1 begins, probably they will
[21:42] <apachelogger> of course it doesn't make sense to backport every release, but I think at the end of this week we gonna make a complete backport again
[21:43] <seezer> ah ok
[22:09] <vorian> how in cmake would i call this " freetype-config --cflags"  ?
[22:56] <apachelogger> stdin: anything else I can fix in kdegraphics?
[22:56] <stdin> apachelogger: nothing I know of
[22:57] <apachelogger> *uploading*
[23:00] <apachelogger> stdin: https://edge.launchpad.net/ubuntu/+source/kdegraphics-kde4/
[23:01]  * apachelogger likes how all the stuff is coming together :D
[23:02] <stdin> lovely jubbely
[23:04] <apachelogger> hm
[23:04] <apachelogger> Oo
[23:04] <apachelogger> oi
[23:04] <apachelogger> stdin: really, I think creating a seperated XDG desktop config directory for the wrappers is the only good solution
[23:05] <apachelogger> search in kickoff for konqueror offers ~8 konquerors
[23:05] <Nightrose> 10 here
[23:05] <Nightrose> ;-)
[23:06] <apachelogger> well
[23:06] <apachelogger> would be half in a kde4 only env I think
[23:06]  * apachelogger checks
[23:06] <Nightrose> k
[23:06] <apachelogger> I get 5
[23:06] <apachelogger> though
[23:06] <apachelogger> actually
[23:06] <apachelogger> I think 4 are actually profiles
[23:06] <apachelogger> as seen in the applications directory
[23:07] <apachelogger> but this still doesn't explain why the packaged KDE popups up with twice as many
[23:07] <apachelogger> hm
[23:07] <apachelogger> Nightrose: the lost&founds are KDE3 kcms I think
[23:07] <apachelogger> mostly at least
[23:08] <Nightrose> jep
[23:08]  * apachelogger is wondering what to do about this
[23:08]  * Nightrose too
[23:08] <Nightrose> they should go away ;-)
[23:08] <apachelogger> yeah
[23:08] <apachelogger> but
[23:08] <apachelogger> hm
[23:08] <apachelogger> well
[23:08] <apachelogger> the problem is
[23:08] <apachelogger> even if we use 2 directories for KDE4 and KDE4AppsOnKDE3
[23:09] <apachelogger> KDE4 would still have to search the default XDG path
[23:09] <apachelogger> /usr/share/applications
[23:09] <Nightrose> hmm
[23:09] <apachelogger> and I think it does this recursive
[23:09] <apachelogger> kde3 desktop files reside in applications/kde
[23:09] <Nightrose> ah
[23:09] <Nightrose> yea seen it yesterday
[23:09] <apachelogger> so KDE4 will have to catch them
[23:10] <apachelogger> or it also doesn't finde openoffice and such stuff
[23:10] <apachelogger> which resides in the default XDG dir
[23:10] <Nightrose> can one make kickoff not search in lost and found somehow?
[23:10] <apachelogger> we can't move that stuff to /usr/share/applications-kde3 either, because then we have to patch gnome and xfce to find the apps as well -.-
[23:10] <apachelogger> Nightrose: well, I think we can make it not show the l'n'f
[23:10] <apachelogger> but
[23:11] <apachelogger> that is no option
[23:11] <Nightrose> hmm
[23:11] <apachelogger> because if a desktop file isn't spec'd but otherwise correct it will show up there
[23:11] <apachelogger> and $user can't find it because lnf isnt shown
[23:11] <Nightrose> right... so not a solution
[23:11] <apachelogger> well
[23:12] <apachelogger> maybe we can patch ksycoca somehow, so it doesn't search catch up *kcm*desktop files in the XDG search path
[23:12] <apachelogger> so these would disappear
[23:12] <apachelogger> actually
[23:12] <apachelogger> can one run kde3 apps in kde4?
[23:13] <apachelogger> oh, one can
[23:13] <apachelogger> always a good thing to know ^_^
[23:14] <Nightrose> hehe sure - how do you think I am running konversation and amarok right now.. ;-)
[23:14] <apachelogger> *shrug*
[23:14] <apachelogger> some wrapper magic
[23:16] <apachelogger> Nightrose: do you get a plasma crash when you search for something in kickoff and start it with a mouseclick?
[23:16] <Nightrose> nope
[23:16] <apachelogger> hm, can't reproduce it either, but a1ex saied it crashes his plasma all the time
[23:17] <apachelogger> might be some configuration stuff
[23:17] <Nightrose> plasma has only crashed once for me so far and not within the last 48 hours
[23:17] <apachelogger> or a desktop file collision
[23:17] <apachelogger> everything is somehow a collision :P
[23:17] <apachelogger> <-- wicked minded
[23:17] <Nightrose> ;-)
[23:17] <apachelogger> Nightrose: did you start off with a fresh profileß
[23:17] <apachelogger> ?
[23:17] <Nightrose> empty .kde4 that is? yes
[23:18] <apachelogger> well
[23:18] <apachelogger> no
[23:18] <apachelogger> completely
[23:18] <Nightrose> nope
[23:18] <apachelogger> the thing is
[23:18] <apachelogger> it doesn't necessarily have to be an issue with .kde*
[23:18] <apachelogger> could also be some xdg configuration in $home
[23:19] <Nightrose> same profile as for kde3 and I copied a few important settings over to .kde4 when I needed them
[23:19] <Nightrose> hmm that was not empty for me then
[23:21] <apachelogger> stdin: we should upload the latest versions of libs, pimlibs, base and workspace... there were some dependency issues in the debug packages, and without them it's hard to catch some of the weird issues like in bug 182077
[23:21] <ubotu> Launchpad bug 182077 in meta-kde4 "multiple desktop-icons in kde4" [Undecided,Invalid] https://launchpad.net/bugs/182077
[23:21] <apachelogger> Nightrose: ok
[23:22] <stdin> apachelogger: yeah, probably a good idea
[23:24] <apachelogger> stdin: I'll publish workspace with gtk fix and dep fix for ksysguard tomorrow morning, maybe you can upload libs, pimlibs and base to the ppa until then?
[23:25]  * DaSkreech breathes threat and vengance
[23:25] <stdin> apachelogger: yeah, I'll do that before bed :)
[23:30] <apachelogger> stdin: thx
[23:31] <apachelogger> stdin++
[23:31] <apachelogger> Nightrose: one round karma for stdin :)
[23:31] <Nightrose> stdin++
[23:31] <Nightrose> ;-)
[23:31] <apachelogger> insanity: bye :P
[23:31] <apachelogger> ~part
[23:31] <stdin> heh
[23:31] <DaSkreech> stdin++
[23:31] <Nightrose> DaSkreech: too late ;-)
[23:31] <apachelogger> DaSkreech: do in #amarok plz
[23:31] <DaSkreech> I sure hope he's able to fit in the bed by the time we are done
[23:32] <apachelogger> lol
[23:33]  * apachelogger scuttles off to bed
[23:33] <apachelogger> nini
[23:33] <Nightrose> nini honey
[23:35] <blueyed> I've reported the kfmclient-issue (ASSERT failure) at bug 182718 - there's also a proposed fix for this.
[23:35] <ubotu> Launchpad bug 182718 in kde4libs "KRun.init can trigger assertion failure in KAuthorizedPrivate()" [Undecided,New] https://launchpad.net/bugs/182718
[23:39] <blueyed> stdin: please look at the above bug and patch - would be nice to have this in your libs upload.
[23:54] <DaSkreech> 11grub
[23:54] <DaSkreech> !grub
[23:54] <ubotu> grub is the default Ubuntu boot manager. Lost grub after installing windows: https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows - Making GRUB floppies & other GRUB howtos: https://help.ubuntu.com/community/GrubHowto
[23:59] <wesley> guys i got some bugs or problems found in kde4 1 in plasma translation is a bug its most like a translation fault and of the translation in dutch


[12:23] <BluesKaj> Howdy all
[14:19] <crutchcorn> Hey guys, is anyone on who could help me out with an issue with Mir?
[15:04] <crutchcorn> Anyone on know anything about Mir?
[15:09] <crutchcorn> Getting an issue about not being able to load library libuinityapplicationplugin.so (libqpa-mirserver.so no file/directory) when running unity8
[15:10] <TheNumb> crutchcorn: have yo tried reporting a bug?
[15:11] <crutchcorn> Not yet because I am A) stupid B) Not sure where to find it (I'll take a look now)
[15:11] <crutchcorn> :P
[15:22] <crutchcorn> TheNumb: Did so now
[15:22] <crutchcorn> https://www.google.com/url?q=https%3A%2F%2Fbugs.launchpad.net%2Fubuntu%2F%2Bsource%2Funity8%2F%2Bbug%2F1426713&sa=D&sntz=1&usg=AFQjCNGnRGzmg4wFFz_Bj8R4TToLyW6qVw
[15:23] <crutchcorn> Sorry, stupid Google links.
[15:23] <crutchcorn> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1426713
[16:16] <crutchcorn> Added more to the bug report
[18:47] <Daekdroom> Can anyone here confirm that Unity doesn't use ~/.xinitrc by default?
[19:01] <TheNumb> why would a desktop environment use .xinitrc?
[19:06] <Daekdroom> Hm.. good point, but I thought it was possible to use it regardless, if it was present in ~/
[19:07] <TheNumb> Daekdroom: what are you trying to do?
[19:08] <bcowan> what kernel is in 15.04
[19:14] <TheNumb> bcowan: 3.18 afair
[19:14] <TheNumb> it will be upgraded to 3.19
[19:15] <bcowan> thanks
[19:17] <bcowan> just wish they would include a 32 bit efi in the 64 bit version


 This message comes when I turn my laptop on or off. How can I solve this? : https://irc-attachments.kde.org/09dd3ab1/file_57650.jpg
[03:13] <arraybolt3[m]> @Abu: Is your laptop still working otherwise?
 Yes , same happenes with me , some error show ,but boots up normally
 But i want to remove it
 It dont looks good (re @IrcsomeBot: <arraybolt3[m]> @Abu: Is your laptop still working otherwise?)
 Yes.... (re @IrcsomeBot: <arraybolt3[m]> @Abu: Is your laptop still working otherwise?)
 But i want to remove this.....
[03:48] <arraybolt3[m]> @Abu: You may be able to append "loglevel=0" to your kernel command line.
[03:48] <arraybolt3[m]> !kernelparm | @Abu
[03:49] <arraybolt3[m]> @Abu: Use the instructions to add the parameter permanently, but do "sudo kate /etc/default/grub" rather than "sudo gedit".
 Ok i will try
 This is long process and maybe i can't do it alone.... (re @IrcsomeBot: <ubottu> @Abu: To add a one-time or permanent kernel boot parameter see https://wiki.ubuntu.com/Kernel/KernelBootParameters)
 8Z48
 76EY
 🎉🎉🎉 Do you know the most lucrative part-time jobs in 2022?  Diligent
 2. Learn about cryptocurrencies
 3. Good expression skills
 You can easily earn 100 to 1000 USDT per day. 🎁🎁🎁 Joining AISUSDT is free, AISUSDT works online! Do you need this opportunity? For more details, please contact my 👉👉 WhatsApp: +44<PHONE_NUMBER>
[05:30] <arraybolt3[m]> !ops | Some user over IrcsomeBot is posting spam/scam material.
[12:33] <BluesKaj> Hi all
[12:38] <user|61> Hello i need help with kubuntu 22.04
[12:40] <user|61> I installed it on my notebook. But it cant find my amd soundcard and it cant find firmware for the amdgpu , when i try to install amdgpu drivers they are not installed
[12:40] <user|61> Its a matebook 14 amd 2021
[12:41] <user|61> Need advice how to install the drivers properly so that i can make use of it
 Q5AF
 O5AF
 Hello, this messages are from me (re @IrcsomeBot: <user|61> Need advice how to install the drivers properly so that i can make use of it)
 Amd support says its a community tasl to solve this
 Task*
[13:00] <tecttecttect> Hi, tell me can you see me or do I need registration
[13:01] <BluesKaj> you're seen
[13:02] <tecttecttect> thanks
[13:02] <BluesKaj> yw
 Do we get support here?
[13:11] <BluesKaj> @Oskar, tes
[13:11] <BluesKaj> yes
[13:11] <BluesKaj> :-)
 Ok cool  so how can i use drivers for my new notebook?
 All that i have tried failed
 Need amdgpu drivers and for the amd sounddevice
 Did not find a bugtracker or something else where i can ask for
 😊
[14:59] <BluesKaj> @Oskar, are you sure it's the driver?
[15:01] <BluesKaj> one thing to check for no audio is to disable automute in alsamixer
[15:04] <BluesKaj> after new install or kernel upgrade the default automute is on to prevent audio from blasting users on the first boot
[17:41] <cbreak> hmm... I keep getting notifications that I have X days to restart firefox for updates
[17:41] <cbreak> despite restarting firefox
[17:42] <arraybolt3[m]> cbreak: Close it, open a terminal with Ctrl+Alt+T, then run "sudo snap refresh firefox", enter your password, wait for it to update (you'll see clearly when it's done), then start it back up.
[17:44] <cbreak> arraybolt3[m]: yeah, I know I could do that, but ... really, why doesn't it update automatically?
[17:45] <cbreak> this worked just fine wouthout snap around firefox
[17:45] <cbreak> in 20.04, in 21.10, in macos, everywhere other than ubuntu 22.04 :(
[17:46] <cbreak> requiring terminal intervention for something as basic as updates isn't good user experience I think
[17:48] <arraybolt3[m]> cbreak: I don't think it requires terminal intervention, I think if you leave it closed for long enough it will figure it out, but I agree, this is a really rough spot in Ubuntu 22.04.
[17:48] <cbreak> also fun: if I just run "snap refresh" , it tells me "All snaps up to date."
[17:49] <cbreak> arraybolt3[m]: long-enough must be longer than 10 seconds then :P
[17:51] <arraybolt3[m]> cbreak: Yup, guessing so. I get why they made Firefox a Snap, but... there are some things to be fixed, that's for sure. In the mean time, https://support.mozilla.org/en-US/kb/install-firefox-linux This has instructions for how to install Firefox from a binary tarball down at the bottom, that will give you an auto-updating Firefox straight from Mozilla.
[17:51] <cbreak> interesting
[17:52] <cbreak> wonder why they gave up on normal deb packages then when they make tars
[17:52] <cbreak> creating one from the other should be more or less mechanical, once infrastructure is set up
[17:53] <arraybolt3[m]> cbreak: Security. Web browsers are very complex systems and are a good way to hack a system. Snap adds a shield around Firefox so that even if something does hack your browser, it can't (or at least has a much harder time trying to) break into the rest of your system.
[17:53] <arraybolt3[m]> It's that shield and the mechanisms behind it that causes all the problems.
[17:54] <cbreak> snap isn't the only way for process isolation though
[17:54] <cbreak> wonder if flatpack or appimage firefox have the same problems...
[17:54] <arraybolt3[m]> cbreak: Flatpak, unsure. AppImage, probably not I would guess, since I don't believe they're containerized.
[17:55] <cbreak> I do have a fully isolated 20.04 firefox in an lxc, which can update itself just fine :D (well, apt updates it...)
[17:55] <arraybolt3[m]> cbreak: Process isolation might keep one process from accessing another if something like a Spectre attack tried to steal data, but I don't think it would help with a buffer overflow remote code execution vulnerability. Snap containerization can even defend against those.
[17:56] <cbreak> buffer overflows only give access to the vulnerable process
[17:57] <arraybolt3[m]> cbreak: But if that vulnerable process can read from/write to your disk...
[17:57] <cbreak> then that's because the process has the permission to do that
[17:57] <cbreak> on macos, process isolation also limits syscalls, like file open / close
[17:58] <cbreak> it's a bit similar to how snaps work, just less ... binary
[17:58] <cbreak> I think selinux can do the same on linux
[17:58] <cbreak> but probably too annoying to configure...
[17:59] <cbreak> well, either way, the big problem in this case is that snap is not updating firefox while it's running
[17:59] <cbreak> it could trivially do so, after all, snaps are all isolated images
[18:00] <cbreak> and just swap it out as soon as it terminates.
[18:14] <gary48> hello
[18:14] <gary48> anyone here
[18:15] <gary48> since yesterdays systemd update there are all kinds of things broke help please
[18:16] <tomreyn> gary48: hi. what seems to be broken, and which version of kubuntu and systemd are you running?
[18:16] <gary48> the discover store comes up with an error that says invalid number of concurrent streams
[18:16] <gary48> it will download some things from discvover and others come up with that error
[18:17] <gary48> and also krdc is broken and will not connect
[18:18] <gary48> kubuntu 22.04
[18:18] <gary48> how do i find out systemd version
[18:18] <gary48> what command do i use
[18:20] <tomreyn> apt list --installed systemd
[18:20] <gary48> can not get into system log either its asking for a password i put in my password says wrong password i put the root password in
[18:21] <tomreyn> you have a root password?
[18:21] <gary48> ystemd/jammy-updates,now 249.11-0ubuntu3.3 amd64 [installed,automatic]
[18:21] <gary48> N: There is 1 additional version. Please use the '-a' switch to see it
[18:22] <tomreyn> this systemd version is fine on 22.04. i assume there is a different issue.
[18:22] <gary48> no it ask for one when i try to open system log
 can not get into system log either its asking for a password i put in my password says wrong password i put the root password in
[18:23] <gary48> it pops up xterm also asking for a sudo password
[18:23] <tomreyn> the sudo password is your user's password
[18:24] <gary48> right i input my sudo and it does not work
[18:24] <tomreyn> what you just said sounds a lot like you do have a root password set
[18:24] <tomreyn> what does "it does not work" mean? is there an error message?
[18:25] <gary48> just the normal password it ask for when i install software everything worked fine till yesterdays system updates
[18:25] <tomreyn> what's the output of    lscb_release -ds    ?
[18:25] <tomreyn> what's the output of    lsb_release -ds    ?
[18:25] <tomreyn> the latter, please
[18:26] <gary48> lsb_release -ds
[18:26] <gary48> Ubuntu 22.04 LTS
[18:27] <tomreyn> what's the output of     sudo id
[18:27] <gary48> is there a system restore or roll back on kubuntu
[18:28] <tomreyn> only if you set it up this way
[18:28] <gary48> sudo id
[18:28] <gary48> [sudo] password for gary:
[18:28] <tomreyn> and when you type your password there it says?
[18:29] <gary48> id=0(root) gid=0(root) groups=0(root)
[18:29] <tomreyn> so you can run commands as sudo fine
[18:29] <tomreyn> as root, i mean, through sudo
[18:29] <gary48> yes
[18:29] <tomreyn> https://bugs.kde.org/show_bug.cgi?id=455540 is a recent bug report against kde, which produces the error message you reported here first.
[18:30] <gary48> but not when i try to open edit sources or open system log
[18:31] <gary48> oh so there is a bug ok well how do i get this to update now that it will not install anything in discover
[18:31] <tomreyn> i'm not familiar with kde plasma and how kubuntu manages updates to it. if you are running the latest kde plasma this bug may be affecting your system
[18:32] <gary48> i have the  terminal muon and synaptic on this pc
[18:32] <tomreyn> debian package updates can be installed using the "apt" command, snap updates can be installed using the "snap" command
[18:32] <alkisg> Try to run a full update from the command line in case something was interrupted:
[18:32] <alkisg> sudo apt update; sudo apt full-upgrade
[18:33] <gary48> ok thanks
[18:33] <tomreyn> alkisg: in case you know, is ppa:kubuntu-ppa/backports enabled by default on kubuntu?
[18:34] <alkisg> tomreyn: hmm not sure but I think "no"
[18:34] <gary48> ok that fetchs updates so atleast when they fix it i can get it that way
[18:34] <tomreyn> thanks
[18:35] <alkisg> gary48: also upload the output of this: grep -r . /etc/apt/sources.list* | nc termbin.com 9999
[18:35] <alkisg> This will show us if you have any PPAs etc enabled
[18:35] <gary48> i will check
[18:36] <tomreyn> or use    sudo grep -hEv '^([ ]*#.*)?$' /etc/apt/sources.list{,.d/*.list} 2>&1 | nc termbin.com 9999
[18:38] <gary48> https://termbin.com/7nup
[18:40] <gary48> well i can get into sources now that i did the upgrade command
[18:41] <gary48> so it fixed that the xterm opens i put my sudo password in and it works now
[18:41] <tomreyn> i assume "get into sources" refers to accessing some graphical user interface?
[18:43] <gary48> Permission denied.
[18:43] <gary48> Possibly incorrect password, please try again.
[18:43] <gary48> On some systems, you need to be in a special group (often: wheel) to use this program.
[18:43] <gary48> thats what i get when i try to get into kysystem log
[18:44] <tomreyn> what does this print?   echo $XDG_SESSION_TYPE
[18:45] <tomreyn> and this:   groups
[18:45] <gary48> i found a backdoor sytemsetting hit drivers then i can open it to see my sources meaning repos
[18:47] <gary48> x11 groups
[18:48] <tomreyn> "groups" is a command i suggested to run
[18:48] <tomreyn> (and post the output of)
[18:50] <gary48> ary adm cdrom sudo dip plugdev lpadmin lxd sambashare
[18:50] <aleksey> ))
[18:50] <aleksey> i am admin
[18:51] <aleksey> close time
[18:52] <aleksey> user root hacking noobs xd
[18:52] <gary48> i will check for updates tomorrow i guess atleast i can update through the terminal now
[18:52] <aleksey> fack all
[18:52] <aleksey> monkey ) moon key
[18:56] <gary48> how do you follow bugs and report for kubuntu
[18:57] <gary48> they say they fixed the bug and im fully updated and obviously its not fixed and is affectting alot more then just downloading icons from discover on my system
[19:00] <gary48> tomreyn you still there
[19:00] <arraybolt3[m]> gary48: https://launchpad.net/. Create an account, then you can find the bug, and there should be a link near the top that says "This bug affects X users. Does this bug affect you too?" Click it, and confirm that you're affected.
[19:00] <gary48> thank you
[19:03] <arraybolt3[m]> gary48: In relation to not being able to view the logs, this is a known bug in Kubuntu, due to a CVE fix in the sudo program. They're actively working on getting it fixed (I was there when they discovered the fix and was actually helping to find it). In the mean time, try "sudo ksystemlog" in a terminal.
[19:05] <arraybolt3[m]> (Essentially, there's some weird attack you can do on sudo in some instances, but the way they plugged the attack hole also threw a wrench in the works of kdesu, the KDE component that allows you to open applications as root through the GUI. The attack is sufficiently low-risk that they've decided to simply disable the fix to make things work again IIRC, but until then, this is the error you get, even when you give the right password.)
[19:05] <arraybolt3[m]> (You can disable it yourself by running "sudo nano /etc/sudoers", then find the line that says "use_pty" and comment it out.)
[19:08] <arraybolt3[m]> (And you can comment out a line in /etc/sudoers by simply typing a "#" character at the start of the line you want to comment out.)
[19:14] <tomreyn> gary48: i'm back for a while. ihave little experience with current kubuntu, could only really help with all the underlying things which are the same in ubuntu
[19:14] <aleksey> update it is virus admin panel secrets  update virus !!!!! live usb usage speet test
[19:18] <tomreyn> try ignoring aleksey
[19:26] <gary48> so my other laptop with kubuntu is doing the same thing so it must be a bug
[19:28] <gary48> im so tired of ubuntu breaking that past couple years whats a good kde distro that works well has a good uefi support cause i think after using ubuntu for 10 years it might be time for a change
[19:29] <gary48> mint these days even breaks cause i use that on my desktop
[19:31] <gary48> any suggestions
 How to disable automute (re @IrcsomeBot: <BluesKaj> after new install or kernel upgrade the default automute is on to prevent audio from blasting users on the first boot)
 The notebook says, no audio device fpund that why i think its the driver
 It loads a hd driver for intel but not for the amd device. I know its an amd sound device and in alsamixer it is shown as acp
 And in alsamixer my amd sound device shows no sound controls
 And now i dont know how to activate my sound device
 I dont want to use all the time a headset
 With USB
[20:40] <Iamthehuman1> Hello there and thanks for the Kubuntu. I am on Ubuntu Studio, but I think this is vanilla Kubuntu behavior I would like to suggest a change: "how about not mentioning the username in the wifi hotspot default name?". If there is anyone else who finds this annoying and needing tinkering with settings to get the username away from the wifi hotspot name
[20:42] <Eickmeyer[m]> Iamthehuman1: I'm here too! o/ Actually, that's not even a Kubuntu thing but a KDE Plasma thing, so even further upstream.
[20:42] <Iamthehuman1> Bless you Eickmeyer[m]-Meister
[20:42] <Eickmeyer[m]> hehe
[20:43] <Eickmeyer[m]> Your best best is bugs.kde.org
[20:43] <Eickmeyer[m]> *best bet
[20:44] <Iamthehuman1> someone should really build that system that will do 3 things well: #1 tell whose bug something likely is and give links #2 send small amounts of money to FLOSS devels and most importantly #3 ability to attach small messages of support to keep on going to the small droplet of money sent


[14:45] <charlie-tca> *Gm
[14:45] <charlie-tca> Good morning
[20:54] <Unit193> Good afternoon!
[22:02] <charlie-tca> Maybe I will start going by UTC instead of Mountain time
[22:06] <Unit193> I just go by my time... Do you happen to know where the recordings of UDS are? (I can look, I just don't know offhand)
[22:06] <Unit193> Sat May 21 17:06:19 EDT 2011   Local
[22:10] <charlie-tca> I don't know offhand
[22:10] <charlie-tca> I could go search them out if you want
[22:20] <Unit193> I didn't find them (Maybe I'm blind...)
[22:22] <charlie-tca> http://www.youtube.com/user/ubuntudevelopers
[22:22] <charlie-tca> has the videos
[22:23] <Unit193> Ah! I didn't look at YT... (And I thought it would be audio...) /me fails
[22:24] <charlie-tca> There are audio streams of all the sessions too, the videos are only plenaries and some sessions
[22:29] <charlie-tca> Unit193: here are most of the session streams - http://mirrors.tumbleweed.org.za/uds-o/
[22:29] <Unit193> charlie-tca: Thanks! Sorry for the bug!
[22:29] <charlie-tca> huh?
[22:30] <charlie-tca> bug?
[22:30] <Unit193> s/bug/bugging/
[22:30] <charlie-tca> no problem
[22:30] <charlie-tca> That mirror page takes a while to load


[02:25] <doko> fabbione: you can find the gcc-3.4 build for sparc in my home on chinstrap. did build properly in a fresh breeeezy chroot


[22:05] <Zer0Glitch> Hello all
[22:43] <BobJonkman> Is it the Frankenstorm that's causing connection flakiness?