=== m4v_ is now known as m4v === freeflyi1g is now known as freeflying [01:58] oi it is freezing outside tonight [02:59] is it acutally freezing? [03:00] my temp shows 36 here so not actually freezing :) [03:23] It seemed pretty cold there yesterday. [03:24] * ScottK was in Chicago for a wedding yesterday (jam packed schedule with no time for visiting, unfortunately) [03:24] ScottK: i thought you were running the marathon today :) [03:25] The groom (and thus his family) was from New Zealand. They were all very postitively impressed with the architecture and beauty of Chicago (obviously some parts of the city went unvisited) [03:25] lol [03:29] i like chicago it is a nice city [03:30] It is. [04:01] chicago is the best city...none on earth like it [04:01] we can rig political elections, but we can't rig olympic ones [04:02] obviously the priorities are inverted. someone didn't learn from the mars rover! [04:02] haha [04:03] hey, at least we bombed the moon this week! [04:03] true enough [04:03] I figure the US blew up enough stuff on earth, we had to take our wars elsewhere [04:03] little kids around the world were devestated, the United States shot the man in the moon! [04:04] I can already see the commercials about 'Happy Cows on the Moon' [04:19] * ScottK did read some comment on a news article from someone claiming they could feel the pain and outrage of 'brother Moon'. [04:19] nixternal: Just sent you some kairmode bugs [04:29] i thought knetworkmangler was doing this stuff now. [04:30] Riddell: I'm pretty stumped on the netbook application launcher problem. notmart suggested that plasma/runners/services/servicerunner.cpp would be the key. I've tried both updating the file to trunk and back to 4.3.1 with no luck. Help. === txwikinger2 is now known as txwikinger [04:41] Is launchpad down? [04:47] txwikinger: No [04:47] I cannot file a bug [04:47] Did you try ubuntu-bug [04:49] no [04:50] The good news is that the brothers of the moon should keel over dead in pain the next time the Moon gets hit by an asteroid [04:52] didn't they already get bombed? [04:53] bug 432725 [04:54] Launchpad bug 432725 in kmymoney2 "[FFe] New upstream release (kmymoney2 1.0.2)" [Wishlist,New] https://launchpad.net/bugs/432725 [04:56] hi vorian [04:57] hola [04:58] claydoh: ^Know anybody who'd want to test that? [05:00] JontheEchinda: why is it not english? [05:04] So did we change how we are finding out about updates being available in Karmic? [05:05] It seems to me we have somehow managed to start following the broken idea that users only should be notified about updates every now and then. [05:07] you mean like for the latest and greatest 4.3.2? [05:08] Not sure when it would have changed, but it would have been something kpackagekit related and not KDE core. [05:09] vorian: KDE was set to spanish for l10n testing [05:10] ah [05:10] spanish is the only other language I can navigate around in KDE in [05:11] i do well with klingon [06:00] * rgreening ponders navigating in klingon [06:02] +1 rgreening [06:02] :D [06:23] nixternal: redmine pls! kthxbai. [06:36] well...another set of OO patches sent along...thats a wrap for tonight [07:34] jussi01: redmine? [07:34] nixternal: bug tracker... [07:34] oh [09:46] Riddell: fyi, I have uploaded digikam 1.0.0beta5 and kipi-plugins to kubuntu-ppa/backports in order to be able to to better bug triage with jaunty users [10:01] lubyou: groovy [10:01] Lure: groovy [12:23] someone able to test koffice beta3 from the experimental ppa [12:23] neversfelde: karmic? if so, hit me up with a url [12:24] jussi01: https://edge.launchpad.net/~kubuntu-ppa/+archive/experimental [12:24] I am not sure, if the packages install correctly, but I cannot test it atm [12:25] neversfelde: I cant test. i386 didnt build... [12:27] hmpf [12:32] so why are they in experimental? [12:32] * apachelogger notes that experimental != broken [12:33] hm, is jockey-kde supposed to work? [12:34] when I click on Activate to activate the proprietary driver nothing happens [12:35] * Mamarok restarts to check === steveire_ is now known as steveire [12:52] so apparently jockey doesn't work at all :( [12:57] Mamarok: are you running it as root? [13:00] yes [13:01] Mamarok: I guess you could try installing the jockey-gtk frontend and seeing if that works [13:01] yep, will try that [13:07] anyway, I activated the fglrx driver by hand, and it's a disaster [13:08] * Mamarok goes back to radeon and is utterly disapointed at Karmic not being able to support her graphic card that is not even a year old [13:08] same problem as Jaunty, this really sucks [13:16] Riddell: and jockey-gtk works, it's the kde client that doesn't [13:16] humph [13:17] Mamarok: if you run jockey-kde from terminal do you get any errors [13:17] let me see... [13:18] no, it doesn't mention any if I start it as a user, and starting it with kdesudo neither [13:19] it just doesn't activate the driver when I click on it [13:19] anyway, restarting to make sure I can enable OpenGL... [14:06] * Riddell fixes microblog applet [14:07] s/fixes/upbreaks/ to be fair [14:12] Riddell: close enough :) [14:20] * Riddell pokes nixternal for not committing kdeplasma-addons changes to bzr === dendro-afk is now known as dendrobates [14:44] Hi there all of you. [14:44] My name is Pedro. [14:45] And I want to contribute to the development of Karmic Koala. [14:45] I read this note a few minutes ago: Kubuntu 9.10 Karmic Koala Beta Released: Everyone Needed! [14:46] Now I am wondering how to get involved as fast as possible??? [14:46] Anyone out there has an idea? [14:47] PedroLeKoi1: what do you want to help with? [14:47] packaging? bug triage? documentation? marketing? [14:47] something else? [14:47] support? [14:48] testing? [14:48] That's part of the question I ask myself to. [14:48] Testing is possible. [14:48] hehe ok [14:48] Because I worked as a software tester. [14:48] ok great [14:48] I tested ecus at bmw in Germany. [14:48] Riddell probably knows what needs testing at the moment [14:48] So: The problem is to focus on a certain part of software. [14:49] Riddell? Is that anohter person here in the channel or... [14:49] yes [14:50] PedroLeKoi1: we could do with jockey being tested if you have any hardware that would use it [14:51] I have a laptop - Karmic is already running on it... [14:53] @Riddell: The app you are talking about is probably 'jockey-kde', isn't it? [14:53] aha, so KDE bug 182870 explains why KDM became plastique in KDE 4.3 [14:53] KDE bug 182870 in general "In kdmrc ignore GUIStyle param" [Normal,Resolved: fixed] http://bugs.kde.org/show_bug.cgi?id=182870 [14:53] * JontheEchidna makes a list of things to patch later [15:09] JontheEchidna: re kmymoney2 [15:09] JontheEchidna: I use it regularly [15:09] JontheEchidna: I have it in my ppa [15:10] PedroLeKoi1: yes [15:10] claydoh: mind commenting on 1.0.2's readiness in the bug I mentioned? [15:11] im there now [15:11] ;) [15:11] I'll be back in a bit [15:11] thanks claydoh [15:14] JontheEchidna: do you have a deb package available? sometimes the debian packages converted to ubuntu's sometimes have broken help and/or broken ofx [15:14] sometimes :/ [15:17] Riddell: oops, sorry about that...totally forgot [15:34] JontheEchidna: comment added [15:35] JontheEchidna: kmymoney acked [15:54] JontheEchidna: and Riddell thanks :) [15:54] * JontheEchidna will upload once other family members are done using the internet [15:55] something tells me they won't appreciate a 17MB upload while they're trying to use facebook ;-) [15:57] priorities.. === Tscheesy_ is now known as Tscheesy [16:13] Hi there all of you. [16:13] My name is Pedro and I want to contribute to the development of Karmic Koala. [16:13] I read this note a few minutes ago: Kubuntu 9.10 Karmic Koala Beta Released: Everyone Needed! [16:13] Now I am wondering how to get involved as fast as possible??? [16:13] Testing would be a good thing because I did this kind of work for more than three years. [16:13] To be more specific: I tested the software running on AirbagControlUnits at BMW in Germany. [16:13] Debugging is another possibility, because I developed software while working for BMW too. [16:13] Surly many programmers in the world are higher skilled and have more experiences but at I am [16:13] highly motivated to support the development of (K)ubuntu and have plenty of time. [16:13] It would be nice if somebody would/could assign me to a certain team or a application. [16:13] And to say it right away: I will need a little bit of guidance. [16:14] hi PedroLeKoi1, nice of you to join us [16:14] PedroLeKoi1: I did suggest you testing jockey-kde, there are other things I can suggest if you don't want to or can't do that [16:15] Riddell I don't mind. [16:16] Riddell So: I have a running system. [16:16] I already worked with jockey. [16:17] PedroLeKoi1: what did you do with jockey? [16:17] Riddell Do I need to download the source code? Or is there a kind of testplan? Or a list with open issues where I can think about... [16:17] Riddell I have a lenovo notebook with a broadcom wireless card. [16:17] I tried to install the proper dirver for the wlan card via jockey. [16:18] That didn't work out to well. === chrisina1ar is now known as chrisinajar [16:18] It seems to me that one has to stick to a certain order... [16:19] jockey-kde cause my system to crash in karmic [16:20] PedroLeKoi1: we need to know if it can install and enable drivers, what happened when you tried to install the broadcom driver? [16:20] That meens: I had to install 'b43-fwcutter'. [16:20] After that I installed 'bcmwl-kernel-source'. [16:21] when I try to install broadcom driver "wl" it causes kernel to hangs [16:21] After doing so 'jockey-kde' shows me that the broadcom driver is active. [16:21] you can see Bug #448753 [16:21] Launchpad bug 448753 in linux "System hangs when I use jockey for first time to enable "wl" module" [Undecided,New] https://launchpad.net/bugs/448753 [16:22] Moreover I could establish a connection to my private wlan. [16:22] jussi01: ping [16:22] Finally. [16:24] PedroLeKoi1: so it worked? [16:28] That didn't work out to well. [16:28] That meens: I had to install 'b43-fwcutter'. [16:28] After that I installed 'bcmwl-kernel-source'. [16:28] After doing so 'jockey-kde' shows me that the broadcom driver is active. [16:30] PedroLeKoi1: but these things were not installed by jockey itself? [16:34] Now I try to remove the bcmwl driver with jockey and it does nothing [16:41] ok i am going to tets now jockey-kde to install and enable bcmwl [16:44] first i remove bcmwl-source and I reboot the system [16:45] now i have the problem that jockey only give me the option to install b43-fwcutter [16:45] bcmwl-modalises is installed [16:50] okay, I reboot after having bcmwl-modalises installed and now jockey give me the option to install Broadcom STA [16:50] I install it and I think my system is going to hangs [16:52] EagleScreen: say it ain't so [16:54] @EagleScreen, Riddell I made exactly the same experiences [16:54] PedroLeKoi1: so it lets you install but freezes at the end of the process? [16:54] EagleScreen: no luck? [16:54] That happens to me as well. [16:54] here again [16:54] me system hanged [16:54] EagleScreen: so it lets you install but freezes at the end of the process? [16:54] But after the reboot the driver still didn't work. [16:55] it finish to install it and just after it, X freezed [16:55] X frozen [16:55] I could go to ttys [16:55] So I would rather guess that the installation procedure didn't terminate as it should [16:55] that sounds like a different problem from what Mamarok was having earlier today where it didn't let her even click Activate [16:56] but when I went back to tty7 (to X tty), kernel freezes too [16:56] Same in my case: I couldn't click those buttons [16:56] EagleScreen: ho hum. could you report a bug "ubuntu-bug jockey-kde" ? [16:57] i aready reportted this in Bug #448753 shoud I use apport-collect? [16:57] Launchpad bug 448753 in linux "System hangs when I use jockey for first time to enable "wl" module" [Undecided,New] https://launchpad.net/bugs/448753 [17:00] attached to 448753 by appoert-collect, review the bug [17:02] thanks EagleScreen, PedroLeKoi1 [17:04] all you need, you are welcome [17:37] I am off for today. Coming back tomorrow morning. Bye everybody. [17:41] hmm, could be a useful chap but seems not to be a great communicator [18:24] hm, is somebody aware of will Stephenson's comment here: https://bugs.kde.org/show_bug.cgi?id=209834 [18:24] KDE bug 209834 in general "crash in handleUpdate method after wakeup out of hibernation" [Crash,Resolved: duplicate] [18:24] came in through the kubuntu-users ML... [18:25] strange bug description for a network-manager problem... [18:25] We've updated in the last month [18:26] would be great if they told us how to reproduce [18:27] Wouldn't hurt to update again before Thursday. [18:28] Riddell: The last issue blocking quassel's final release looks to have just been fixed, so I expect to have 0.5 final tomorrow or wed. [18:29] ScottK: the guy in the mailing list still uses Jaunty, so it might well be solved in Karmic, no? [18:29] Yes. [18:29] ScottK: just in time [18:30] Riddell: Yeah, EgS, who does the database stuff had taken a bit of a sabbatical, but just reappeared in time. [18:30] Riddell: I'm dieing for ideas on the netbook launcher problem. I ping'ed notmart on #kubuntu-netbook, but got no more suggestions yet. [18:31] ScottK, Mamarok, Riddell: FYI, that NM bug, I can't reproduce...suspend to ram and back works just fine, I am on IRC right now aren't I? :) [18:32] It's been working for me too. [18:32] nixternal: well, network works for me since ever, even on Jaunty, so... [18:32] wait, has it been fixed in the stuff for jaunty? [18:32] i am wondering if that person is running jaunty or karmic [18:33] he is running Junaty with KDE 4.3.2 from the PPA apparently [18:33] suspend to and from ram is whicked fast now I might add as well [18:33] right, I doubt networkmangler was backported for jaunty, though I don't know for sure [18:34] it was, I did it [18:34] but only the frontend, it's still the old backend from jaunty [18:34] right, wonder if that is where the problem lies [18:35] I'd expect so [18:36] this is why we should make it difficult for user to report bugs upstream [18:36] it gets on the project owners nerves to get flooded with bug reports that aren't there === txwikinger2 is now known as txwikinger === jjesse_ is now known as jjesse [18:43] I did comment in the bug we had a later revision than that in Karmic. [18:48] Any have seen a problem in karmic where ifup does not setup the wireless configuration right? [18:49] I thought if NM was controlling the connection, ifup was supposed to leave it alone? [18:50] hmm.. knetwork manager did not work for me in jaunty, I set the stuff up in interfaces file [18:52] That's a non-standard config then. [18:52] Well.. nm does not work either.. I guess I need to do some troubleshooting [18:54] Riddell: Is it on purpose you aren't in #kubuntu-netbook anymore? [20:38] Riddell, nixternal: I believe the issue with NM was that we had an outdated version of the frontend until 3 days ago [20:39] A much bigger problem for wstephenson than upstream NM bugs was us shipping the plasma widget for jaunty [20:39] upstream bugs comes with the territory when you're messing with NM [20:40] having them go through us first is unproductive because users have to go through another layer-- us-- to get to the developer, who usually has a better idea of how to gain useful debug information [20:41] if they ever reach the developer at all (which I am trying hard to make happen in the case of the network management applet) [20:42] but I think the former knetworkmanager source package with it's mostly-new 100+ bugs (before they got closed unmaintained) shows what happens when hard-to-debug NM bugs come to us first [20:45] JontheEchidna: it doesn't help us if they file upstream and not LP though, and pissing off the upstream isn't a good idea...especially when they can backport a fix for us if needed [20:47] if we didn't want to piss off upstream we shouldn't have shipped the plasma widget in jaunty. He got 100x more bugs from that than upstream bugs [20:47] not much we can do about that now though, but... [20:48] when upstream bugs come in at B.K.O they are usually feature requests for crap that NM needs to do first [20:54] right [21:48] Riddell: do we include fix for kde bug 209960 - it seems that crashes digikam/geolocation [21:48] KDE bug 209960 in khtml part "Kopete crashed when closing history window [QWidget::hide, ~KHTMLPart, KParts::Part::slotWidgetDestroyed]" [Crash,Resolved: fixed] http://bugs.kde.org/show_bug.cgi?id=209960 [21:55] Nightrose: btw, the reply to kobby was that "I want to have more testing before I release." and that if there is someone with more expertise regarding gitorious, that he would appreciate a hand. [21:55] ryanakca: doh! how is he ever going to get more testing without asking for it... [21:56] Nightrose: of course, that was not a quote. [21:56] and wrt hand moving to gitorious: send him my way i can get him in touch with people [21:56] Nightrose: I figure that UDS-L will be a great time / place for it to get extensive testing? [21:56] jep excellent [21:57] Of course, he said he wanted testing by non-developers... but I'm not sure how many non-developers even use gobby. Unless he wanted non-Kobby devs, but oh well. Feel like /msg'ing me your email so that I can forward him to you? [21:58] lydia @ kde.org [21:58] Thanks [21:59] Lure: we have like 6 duplicates against that already, so I'd go for it [21:59] bug 447823 [21:59] Launchpad bug 447823 in kdenetwork "kopete crashed with SIGSEGV in KHTMLPart::~KHTMLPart()" [Medium,Confirmed] https://launchpad.net/bugs/447823 [21:59] needs reassigning to kdelibs I suppose [22:00] thanks for finding the upstream bug; I had looked for it [22:00] eek, 10 dupes by now [22:00] JontheEchidna: can you do me a favour? [22:01] depends on the favor of course :P [22:01] JontheEchidna: fix typo in package dooble - should be "in" instead of "is" :P [22:02] yeah, sure thing [22:02] thanks :) [22:02] yw [22:03] JontheEchidna: I found it by triaging upstream digikam bugs ;-) [22:03] * Lure adds milestone to 9.10 just to put it on radar screen ;-) [22:04] was this a 4.3.2 regression? [22:05] looks like it to me [22:06] ah, yeah. dfaure's post-4.3.2 fix caused that [22:06] Nightrose: sent [22:06] Lure: we include something like it http://bazaar.launchpad.net/%7Ekubuntu-members/kdelibs/ubuntu/annotate/head%3A/debian/patches/kubuntu_74_hide_khtml_widgets.diff [22:07] ryanakca: thx :) [22:07] fabo: waa, qt4 still not compiling in the buildds even though it compiled in my PPA === dorins_ is now known as dorins [22:09] Riddell: right, and this patch is root cause for the patch - see http://websvn.kde.org/?revision=1033984&view=revision [22:10] Lure: ah so the patch needs a patch [22:10] Riddell: right [22:11] Riddell: will you take care for this - I can only look into this tommorow night, need to get to bed now [22:12] Lure: yes I'll fix it now [22:12] Riddell: great [22:50] fcks, anyone tried to recover deleted files from ext4 [22:50] looks like I managed to delete my home [22:50] grrr === kubotu_ is now known as kubotu