=== bdefreese2 is now known as bddebian [01:58] ohmy, broken kio_smtp causes a lot of ML drama [03:21] A user is requesting assistant with: [Its shtylman. I'm testing live assistant.. .someone help me :)]. Please join #shtylman_2_222200 if you can help them. === yofel_ is now known as yofel [03:41] claydoh: http://68.173.99.55/live/chat1.png [03:41] thats what I see on my end [03:41] needs some touchup... but the goal was to be simple for anyone [03:42] and a pretty icon [03:42] allways need a pretty icon [03:42] always [03:43] and the timestamps might need to go on the users' end, if I am being picky :) [03:43] and make it a plasma widget too :) [03:44] just kidding on that one [03:45] haha [03:45] users' end? [03:45] like after the name? [03:45] im always used to them being before [03:46] but I do wanna shorten it [03:46] might even remove it [03:46] or take the seconds off [03:47] well, the timestamps might look to 'geeky', maybe more , um intimidating, perhaps tho I am no design person [03:47] hi shtylman [03:47] txwikinger: hey [03:47] * txwikinger was tempted to say hi NY :D [03:47] intimidating is too strong a word rather [03:47] claydoh: I see what you mean [03:47] txwikinger: hahah [03:52] http://castrojo.wordpress.com/2009/11/28/attack-of-the-killer-bs/ we need k-sides :) [06:00] launchpad down? [06:16] seems to be [10:45] where is the automatic start of plasma-desktop configured? [10:45] built from trunk today, and somehow plasma-desktop is gone (running it via krunner still works) [10:46] binarylooks: you built it and installed it to where? [10:47] binarylooks: oh and look what pinotree is about to say [10:51] Tm_T: thanks for your help, pinotree in kde-devel suggested removing plasma-desktop.desktop from autrun, and now it works [10:52] at last my build environment is fully functional [10:52] binarylooks: aye, that's the usual thing [11:07] JontheEchidna: its not like anyone else had broken kmail :P [11:08] hence there were plenty of peeps to send mails [11:09] Grrrrr [11:09] I want bigger res than 800x600 in KVM :/ [11:13] I want plasma-desktop to take up less than 785M of memory and 31 hours of cpu in 17 days [11:18] moin [11:18] Kubuntu still randomly forgets to see some USB devices on boot [11:18] not good :) [11:19] doesn't only happen here, but on another computer too [11:19] could be a bug [12:20] Mamarok: I think I've found the cause of the plasma memory leak I stumbled upon yesterday when u were helpling me out [12:20] not sure yet, but it appears to be in thumbnail previews of tasks on the taskbar [12:21] by just moving back and forth between two tasks and showing their thumbnails (changing content, e.g. htop in konsole and konversation) - plasma-desktop gains 1MB in 20 seconds or so [12:22] lart aseigo for not having conceived plasma widgets as individual tasks... [12:22] they should really rework that, it is a major annoyance [12:22] Mamarok: any chance u can confirm this? [12:23] amichair: nope, no plasma problems here, but there are many, many, mayn bug reports for that on bko IIRC [12:25] if u run htop in konsole and then repeatedly show/hide the task thumbnail (just move on the button for a sec, then off for a sec), do u see plasma-desktop RES++ after half a minute? [12:26] ScottK: btw, I do not think that you are at fault at all ... at best we are all responsible for not establishing a clear policy in regards to meeting organization, also, as I already told JontheEchidna, it's not like anyone who actually did get to vote, couldnt have noticed the lack of announcement on the ml and send such a mail [12:31] Mamarok: I've just played around with this for a few minutes, and got plasma-desktop to rise from 785M to 801M RES... so that's definitely bad [12:33] well, it's inhereent to the plasma architecture, as I said, a single process for everything is not a good idea [12:33] they should start a migration to individual processes for KDE 4.5 ASAP, since we will run into even bigger problems over time [12:39] I'm not sure a separate process for taskbar thumbnails would help... I think proper memory management would :-) [12:42] 50 bucks that the leak is neither in plasma nor the taskbar applet [13:17] so, out of the blue (didn't touch anything), KDE just told me: "New Device Detected (NewMedia)!" [13:17] something is not quite right there... :) [13:18] HAL borked, udev borked, Solid borked? [13:18] I can only guess [13:24] ah, did the new brainwave interface go online? [13:24] so maybe it picked up your brain cinema :) [13:28] hah === emma_ is now known as emma [14:06] apachelogger: Since no one else was doing it, I asked JontheEchidna to make the doodle poll and then I decided to talk to the people that needed to be there on IRC. Since that's not an acceptable method to the community, I'm just not going to do it anymore. [14:33] ScottK: I do appreciate the organizational work you did for the meeting, and I'm sorry it got you put in the hot seat. :( [14:33] I do appreciate/understand your decision to not do such organizational work in the future, however. [14:36] JontheEchidna: http://revu.ubuntuwire.com/details.py?upid=7092 please review if you have time [14:37] revuing now [14:37] ScottK: Please do not blow misunderstandings out of proportion [14:37] I think it is very good when you take initiative [14:37] far better than when nothing is done [14:42] Quintasan: Overall a very good package. Just a few nitpicks: [14:43] -The cmake build-dep isn't required since kdelibs5-dev depends on cmake [14:43] -The short description of a package usually does not have a period at the end [14:43] JontheEchidna: I'm working some more on notifier, let me know if u'r gonna too so we don't do duplicate work [14:43] -The long description of a package usually *does* have a period at the end ;-) [14:44] Quintasan: so that I don't waste Riddell's ack I can, with your permission, just change these little things myself and sponsor your upload [14:44] amichair: I've not touched it; figured you were up to neat stuff with hooks ;-) [14:47] JontheEchidna: I didn't mean to take over or anything, it's still ur baby, I'm just babysitting for a bit :-) [14:47] oh, don't worry. I don't see it that way and I very much appreciate your experience/contributions [14:49] http://lifehacker.com/5414288/top-10-apps-you-can-use-just-about-anywhere <- Number one is a Qt app, which says somethin about Qt's cross-platformness [14:50] are there QT phones around yet? [14:53] Quick Time phones? ;) [14:53] * amichair runs away in horror [14:55] No Qt phones in the public, though that's what Nokia's working on next [14:55] * amichair crawls back hesitantly [14:56] so cross platfrom on desktops, for the time being? [14:59] yeah [14:59] though you'll see from time to time blogs showing the random KDE app running on a mobile device [15:01] amichair: the post N900 will use Qt [15:01] JontheEchidna: should the 'seen' hooks be written in the notifierhelper configuration (where the other settings go)? or is it supposed to be system-wide unique? [15:01] and some of the N900 apps are done with Qt already [15:02] Mamarok: cool. wonder how much phone marketshare Qt will gain... [15:02] all of it I hope ;) [15:03] JontheEchidna: sure if you can please fix them and upload, sorry for taking time, was playing stepmania :P [15:03] well it's a good thing I'm learning a bit Qt, I guess :-) [15:04] amichair: I would say global. update-notifier-kde did it that way [15:05] Quintasan: ok, I'll get to it right after I get back from walking the dog (which I am doing right now, bbiab) [15:08] there is something I must have missed, but did you folks shove KDE 4.4 into proposed? [15:08] tsimpson: that's what that guy in #k is talking about, right? [15:10] Mamarok: not exactly, he's just talking about the option to enable "pre-release updates", which is how -proposed is described in the GUI [15:10] asking if it's a good idea or not [15:10] ok, but there are no pre-release stuff in there really? [15:11] it mostly what goes into -updates, after testing [15:11] that repo description is a bit misleading IMHO [15:11] pre-released in what regard? [15:12] testing should not be available elsewhere than in PPAs I think, but again, MHO [15:12] is's software-properties-kde descriptions [15:12] it can mean pre-released for kubuntu i.e. it is moved into proper repo when released in kubuntu [15:12] or it can mean pre-release in KDE [15:13] it means [15:13] "pre-released updates" [15:13] it's -proposed, so it's ubuntu (not gnome/kde/whatever) [15:13] in the context of a kubuntu application, since policy suggest that no ubuntu app should handle updates independelty of apt [15:13] *not specifically... [15:13] never understood the point of actually having that repo if it's not targeted at end-users anyway [15:14] for testing packages before going into -updates [15:14] Mamarok: why not... I often put packages in my ppa ony for testing purposes [15:14] tsimpson: which is clearly not for end users, so why is it available there? Should be a PPA instead [15:14] apachelogger: who the is setting invites for bunker? [15:14] Mamarok: it existed long before PPAs did [15:14] Quintasan: vorian, I happened to forget how to set a permanent invite [15:15] apachelogger: +I [15:15] hmm, okay, I changed my isp and I'm not longer invited [15:15] * Mamarok would like to know what that bunker is btw [15:15] our super duper ultra sectet channel [15:15] apachelogger: or just use chanservs flags [15:15] invite? [15:16] Quintasan: for what purpose? [15:16] hidden for membres apparently too [15:16] why are there secret channels in open source? [15:16] members* [15:16] Mamarok: we could tell you, but then we'd have to kill you ;) [15:16] :D [15:16] tsimpson: very funny [15:16] open source lives on transparency... secrecy is for freemasons [15:16] and even they are very open nowadays [15:17] illuminaty :D [15:17] i have known apachelogger isnt an normal guy [15:17] tsimpson: I really don't see why Kubuntu members hear about secret channels and are not informed what it is [15:17] * Mamarok wonders what that membership is there for then, if contributors are kept in secret [15:18] right [15:18] that channel is where I happen to do orgies [15:18] nothing of general interest [15:18] O_o [15:18] we just meet there have fun time and thats it [15:19] so I am excluded from the fun? How very nice of you... [15:19] Lex79: are you an uber-fast kde packaging machine or you have over 9000 machines to do multipe compilations at once? :D [15:20] he just doesnt do QA :P [15:20] that is how I did it :P [15:21] lol [15:23] apachelogger: hmm if all ninjas are going to be you, then we will have not QA :P [15:24] apachelogger: I'm refering to https://wiki.kubuntu.org/Kubuntu/GettingInvolved/Development ofc :P [15:24] that is why it is impossible that all ninjas end up being me :P [15:27] communication #fail apparently... [15:29] apachelogger: Is there a list of things tobe done? [15:29] where is the config file for KGlobal::config() stored? [15:30] * txwikinger found an error in his pcb design on ktechlab [15:31] amichair: ~/.kde/share/config/kdeglobal [15:31] Quintasan: was it you who wanted to look into getting neon to karmic? [15:31] Nightrose: yes [15:31] apachelogger said something about it being dead [15:31] Quintasan: ah cool - any progress? [15:31] JontheEchidna: that's per-user... how do I get to the global? [15:31] noooooo [15:31] * Quintasan pokes apachelogger [15:31] really we need it back [15:31] it is important [15:31] amichair: that's as global as it gets, I think [15:32] txwikinger: If I was going to organize such a meeting again, I would do it the same way. Clearly this isn't acceptable to people so really the only possibility is I don't do it. [15:33] txwikinger: to be done in what regards? [15:33] ScottK: what is the problem than someone must not be you also puts it on the mailing list? [15:33] txwikinger: IMO the people who are complaining about a situation where everyone who needed to be scheduled for the meeting is there are the ones blowing stuff out of proportion. [15:33] this is not a big issue, but doesn't hurt either [15:33] txwikinger: Then they can schedule it. [15:33] Quintasan: huh?? [15:33] For a small meeting that needs just 6 people, I'd rather just ask them. [15:33] ScottK: Yes.. I think the issue is hotter than it needs to be [15:34] txwikinger: I agree, but I'm not the one that started complaining about non-issues. [15:34] apachelogger: it regards to development for Kubuntu needed [15:34] [sobota 28 listopada 2009] [14:22:08] project neon is dead [15:34] apachelogger: ^ [15:34] * apachelogger thinks the only issue there is an issue of communication fail in that people didnt know who would be involved in the meeting [15:35] which is more of a documentation sort anyway [15:35] ScottK: I did not say you did. I just said that I would find it a loss of for everybody if you feel stopped to do good things because of it [15:35] also... I would only have strived for a quorum to begin with, thus being even less organizingly :D [15:35] txwikinger: I understand. [15:35] txwikinger: not yet, though there should be [15:35] apachelogger: cool [15:36] you could create one :P [15:36] though I always wanted to have some decent software for that [15:36] nothing in sight [15:36] apachelogger: I probably could :D [15:36] which keeps my personal motivation for maintaing a todo rather low :S [15:36] Quintasan: well yes, what was the poke for? [15:36] Project Neon, Nightrose was asking how's the progress [15:37] Nightrose knows that I am not maintaining any longer :P [15:37] though I actually uploaded the tools package the other day [15:37] apachelogger: yes which is why i want someone else to take over - for example Quintasan [15:37] ah [15:37] I quickly got turned off by the horrible file structure I mastered up there [15:37] clearly not a very efficient design [15:38] in fact a very crappy one [15:38] * apachelogger is ashamed of it anyhow :S [15:38] Quintasan: well, did you get started? :P [15:38] apachelogger: ./amarok.rb fails to grab the source [15:39] I propably need some sort of account to connect to ftp.kde.org don't I? [15:40] ftp? shouldn't the connect be to a revision system? [15:40] svn+ssh://sitter@svn.kde.org/#{branch}/#{path} [15:40] :D [15:40] well... pull should be available for anon [15:41] svn+ssh isn't for anon [15:41] well.. svn is [15:42] hmm changed to svn://anonsvn.kde.org [15:42] and it works [15:42] apachelogger: what do I need to do expect running amarok.rb? :P [15:43] there are some publisher scripts but hell, dunno wth they do [15:43] another example why svn should be retired for bzr :D [15:44] bzr has similar issues [15:44] git pwns them both :P [15:44] but it is easier to branch and merge [15:44] Quintasan: publisher do nothing at all [15:44] for distributed env [15:44] BTW, anon svn (or bzr) pulls are potentially exploitable using DNS cache poisoing. [15:44] you want to look at distros/ubuntu.rb [15:45] Quintasan: though, you probably just want to look at amarok.rb itself [15:45] well.. with a launchpad account that is not a problem because you don't need anon [15:45] Quintasan: depend on the arguments it will try to fetch the source of qt, kdesupport and amarok, then invoke the distros/ubuntu.rb stuff which is trying to create pacakges with those sources [15:46] Quintasan: the fun part here is that qt now must come from git, so you probably need to hack into fetcher.rb and port the qt code to git [15:46] which should be only copynpaste from the amarok stuff, which I hopefully ported to git at some point :D [15:46] txwikinger: with kde svn account you dont need anon either :P [15:46] txwikinger: that logic is flawed [15:47] well.. is it as easy to get a kde svn account as a launchpad account? [15:47] furthermore, you cannot create a svn branch without write access [15:47] depends on time of day [15:48] nixternal: i have made the changes in the source of 'about kubuntu' page, but having permissions problem in validating it. Can I send the diff file. The page looks good. [15:48] I can always create a bzr branch on launchpad without being a committer to the main branch [15:48] txwikinger: that is an architectural paradigm of centralized version control [15:48] what you are arguing is centralized vs decentralized [15:48] exactly... that's why I said svn should be retired [15:48] which is WIP anyway :P [15:48] I like decentralized a lot better [15:49] bzr is just no better if you take away the paradigms [15:49] I would hell want to know where comp variable is defined [15:49] * txwikinger did not argue qqaulity of any revision system [15:49] * txwikinger cannot type [15:49] another example why svn should be retired for bzr :D [15:50] well.. lauchpad uses bzr... that was the initiator [15:50] ~order cookies for Quintasan [15:50] * kubotu slides a whole bunch of world's finest cookies down the bar to Quintasan. [15:50] txwikinger: kde does not use launchpad though :P [15:50] we use launchpad at *buntu [15:50] well.. use git bzr whatever... was just an example [15:51] * txwikinger uses git and bzr a lot [15:51] * txwikinger is more interested to reduce the on-ramp for potential contributors than any religious wars [15:54] Quintasan: comp? [15:54] in fetcher.rb IIRC [15:54] urgh this is a mess [15:54] I can't find the line which tells the git adress [15:54] if not defined by that, libfetch.rb will probably apply magic [15:54] Quintasan: I told you that it is dirty :P [15:55] Quintasan: checkOutGit(comp, "git://gitorious.org/amarok/amarok.git", "amarok-nightly") [15:55] that's the line for amarok [15:55] yeah [15:55] I need to get Qt from git not svn, right? [15:55] but where is the problem? [15:55] comp = "qt" [15:56] checkOutGit(comp, "git://FANCYURL", "qt") [15:57] createTar("qt") [15:57] that is all you should need to do in fetchQtCopy() [15:57] since patches are applied in the kde-qt branch AFAIK [15:58] so the whole patch applying magic becomes obsolete [15:59] well still pulling kdesupport :P [15:59] urgh, oxygen [16:00] Quintasan: might want to comment out kdesupport and amarok for now [16:00] first get qt done, then work your way up [16:00] IDC if it syncs now or later :P [16:01] better sync now then fight with code [16:04] hehe [16:10] is there a preferred md5 utility function for cpp/kde/qt somewhere? [16:11] amichair: I think there is an own md5 class [16:11] api.kde.org will know more [16:12] Nightrose: I probably won't finish it sooner than Thursady, school etc. [16:12] Quintasan: that's ok - as long as it gets done at some point and not in 100 years ;-) [16:12] as long as someone is working on it i'm happy [16:12] apachelogger: Would you be interested in sponsoring bangarang to Lucid? It was uploaded to Debian unstable a few days ago. [16:13] if revu is up again [16:13] apachelogger: it is [16:14] apachelogger: Lemme check that the one on REVU is the most up to date (packaging is stored in the Debian Multimedia Maintainer Team's git repo) [16:14] watch file is missing! [16:14] omg! [16:15] Riddell: please ping me when you are around for a PM [16:18] ryanakca: Jani Huhtanen does not really claim copyright on anything [16:18] or Andrew just removed his copyright :P [16:19] aye got removed [16:19] * txwikinger found that the most frustrating part of packaging new packages... when authors do not put proper copyright and licensing into the sources [16:20] * apachelogger supports that observation [16:20] apachelogger: Diff between Debian and Ubuntu (assuming siretart didn't change anything when he uploaded): http://paste.ubuntu.com/331162/ [16:20] ryanakca: what is with the manual deps for the binary package? [16:22] * apachelogger needs to leave for train [16:22] ryanakca: package should be fine otherwise [16:23] apachelogger: As in the justification for them? [16:23] justify + document [16:23] and fix copyright file [16:23] and add watch file [16:23] apachelogger: Watch file not possible because it comes from kde-apps and upstream doesn't have anywhere else to host the tarballs [16:24] also on less important matter.. it probably would be nice if you'd provide a xpm for the menu file [16:24] apachelogger: OK... justify in the changelog? [16:25] also, as to hosting ... upstream could probably use the google code project he uses anyway :P [16:25] ryanakca: yes, unregular stuff needs to be documented in the changelog, well, you dont need to document the watchfileyness [16:26] * ryanakca will email Andrew about removing Jani's copyright :) [16:26] no [16:26] why? [16:26] or wait. Jani, that's the blur.cpp person... they don't use that anymore. [16:26] Jani had copyright on blur.cpp/h which was conflicting with gpl [16:26] * ryanakca thought it was another upstream author [16:27] you just need to update the copyright :P [16:27] really need to leave now [16:27] However, Andrew has two or three other heavy contributors, but I don't see their copyright anywhere. Oh well. [16:27] apachelogger: OK, cheers :) [16:29] apachelogger: urgh, I need to launch kde.rb first [16:29] :P [16:29] apachelogger: and where I should publish the packages? [16:30] http://ppa.launchpad.net/project-neon/ubuntu/pool/main/a/amarok-nightly doesnt work [16:30] argh, I've set to publish to my PPA [16:31] * txwikinger should maybe get some breakfast [16:34] apachelogger: hmmm building of amarok-nightly fails at clear phase but that's ignored, it should be like this? [16:41] JontheEchidna: taking md5 of file content + filename + modification time will do? any change to them should popup a new notification? [16:42] Yeah, sounds right [16:44] well, the kdirwatch should pick up any changes. We just have to check if the md5sum really did change [16:47] but hten that is what is triggering the whole new notification irst place [16:48] maybe we could create a new class doing our md5+config stuff that we could replace the KDirWatch in NotificationHelperModule with? [16:51] man, this is all getting a little complicated [16:52] the devil's in the details... [16:52] and in my fridge too. scary. [16:53] JontheEchidna: also we need to pick things up after reboot, if the notifier was down and then started, etc [16:54] last but not least - preserve backward compatibility with update-notification-kde so we don't show things that it already marked as finished [16:54] about gnome/kde, nothing simple to do - the spec is broken. a dual-desktop will receive notifications in both, and run everything twice... [16:55] It's a 4 year old spec written with a single desktop in mind [16:57] also this config is not systemwide within kde, so two users will both see the notifications and run them twice [16:58] luckily upgrade hooks aren't all that common [16:59] yeah... that would have forced us to do things right :-P [17:56] JontheEchidna: updates waiting for u in branch :-) [18:00] huh, KMD5. Who knew? :P [18:01] apachelogger! he knew! :-) [18:02] who likes star trek ? [18:02] who doesn't? [18:02] http://www.youtube.com/watch?v=xMBtRoTPrJw [18:02] watch this [18:02] :D [18:03] evening [18:03] hi [18:03] Good evening Riddell. [18:03] Mamarok: what's up? [18:03] Quintasan: how do I add you to invites? [18:03] evening Riddell [18:03] Riddell: Any chance you could approve https://blueprints.launchpad.net/ubuntu/+spec/kubuntu-lucid-netbook-packaging [18:04] hi amichair [18:04] Riddell: beats me, it turns out I need to poke vorian. [18:04] because only he know how to do this [18:05] I always find IRC commands obscure [18:05] Mamarok: I filed the memory leak bug in kde - hope they fix it by 4.4 [18:05] maybe I should use one of these fancy new GUI clients :) [18:05] Riddell: nvm, I need to rethink first [18:05] Howdy Riddell [18:06] JontheEchidna: do we have all notification basics covered, enough for it to be usable? was there something else? [18:07] for hooks or in general? [18:07] ScottK: I think I'll just approve all our specs [18:07] Riddell: I'm good with that. [18:07] JontheEchidna: umm.... both? [18:08] Yeah, I think everything's usable. Now it just needs a good bit of testing done [18:12] amichair: you should add your name to the copyright headers for the hook classes. A lot of that stuff is your code [18:23] amichair: Everything's merged now. Works great. [18:23] JontheEchidna: I'm looking at the installevent now. looks pretty straightforward. [18:24] Glad to hear it. I'm proud of that one; my first experience with (Qt)DBus [18:25] JontheEchidna: how did u test it? what scenario pops it up? [18:25] uninstall libxine1-ffmpeg, run dragonplayer [18:27] The long-term plan is that PackageKit gets batch install via DBus and we can depreciate InstallEvent once the apps can communicate directly with KPK [18:27] The short-term plan is to implement the DBus spec as it was in update-notifier-kde until long-term can be implemented [18:27] minimal changes since this is an LTS, etc [18:28] you must mean deprecate... it's a common typo that almost makes sense :-) [18:30] JontheEchidna: in that case, I won't bother with semantic fixes [18:31] semantic fixes? [18:31] JontheEchidna: like reducing the duplicate code in installevent::getinfo [18:31] oh, I was talking more about the actual DBus spec [18:31] JontheEchidna: or getting rid of the packageToggled event which is not needed [18:32] oh, so this code will continue to live on? [18:32] well, it'll be in service for at least 10.04 [18:33] Or at least we should plan on it being in service for 10.04, since I don't know exactly when the PackageKit goodness is coming [18:35] JontheEchidna: I see only one real (small) bug - if u deselect all packages and click ok [18:35] ok, I'll give it just a bit of work, and u can take whatever changes u like [18:35] Oh, does that invoke install-package with nothign to install? [18:35] yep [18:35] heh [18:38] which is the proper copyright form, "(c) 2009 by x" or "(c) 2009 x" (u and apache have it different) [18:39] oh yeah... I forgot to make that consistent [18:40] Copyright

[18:40] or so sez the almighty KDE licensing policy [18:41] I'll consistify everything except the install classes to prevent merge conflicts [18:41] no conflicts, don't worry. go for it. [18:43] anyone knows if there's going to be an updated package for glibc to fix the malloc_check crashes? http://www.purinchu.net/wp/2009/11/16/malloc_check_-crashes/ [18:45] ^I did file a bug against the eglibc package about that. No response yet [18:46] thanks [18:48] amichair: ok, I'm all done with license headers [18:49] AFAIK it is already solved upstream, and theer are patches available (the glibc problem I mean) [18:50] we are hit regularly with that on Amarok [18:50] like, an average 10 bugs a week I have to close as dupes because of it [19:01] JontheEchidna: do you by chance still have the bug #? [19:02] bug 425723 [19:02] Launchpad bug 425723 in glibc "kdevelop assert failure: *** glibc detected *** kdevelop: free(): invalid pointer: 0xbfc22c44 ***" [Unknown,Fix released] https://launchpad.net/bugs/425723 [19:03] thanks [19:31]