[00:00] ah it is http://ubuntuforums.org/ [00:00] Monika|K: I don't know, it looks like an email notifier, but I don't have a karmic install atm [00:01] neversfelde: from whios, I had also assumed canonical hosted kubuntu-de, but that was just the nameservers iirc [00:02] oh kubuntu-de, it is hosted by amu and he is a little bit weird. So we had to move to kubuntu-de.org and that is hosted by me. [00:03] I think kubuntu-de points at kubuntu.org now [00:03] neversfelde you mean kubuntu.de [00:03] yes [00:15] oh koffice 2.1 beta seems to be mauch faster [00:15] how can I force an overwrite of a file which was installed in 2.02 with kchart-kde4.install and now is installed with koffice-kde [00:15] meh [00:16] koffice-data-kde4.install? [00:18] anyway, brave testers can upgrade koffice to 2.1 beta1, it is in the staging ppa. Kformula seems not to work, probably my fault [00:28] and kplatowork should probably be a separate package [00:51] neversfelde: make the koffice-data-kde4 package do a Replaces: kchart-kde (<< 2.1beta1) (or whatever the version is for the beta) [00:51] JontheEchidna: k, thanks [01:01] ScottK: i already pbuilder'd it === seele_ is now known as seele === seele__ is now known as seele_ [03:00] OK. [03:00] ScottK: does feature freeze mean that if i wanted to fix https://bugs.launchpad.net/ubuntu/+source/jhbuild/+bug/419363 id need to package, post to REVU, and get 2 advocates in the next 24 hours? [03:00] Launchpad bug 419363 in jhbuild "jhbuild is heavily outdated, update it" [Undecided,New] [03:04] maco: No. It means that it's already past Feature Freeze (see u-d-a), so you need an approved FFe. [03:05] chriscoulson just told me in u-devel [03:05] so i guess that means it freezes at the *start* of thursday, not the end of it [03:05] Yep. [03:06] FFe for a sane upgrade probably isn't really hard to get at the moment. [03:12] FFe's are super easy to get right now...I used to get them all of the time for smb4k [03:13] And if they gave them to nixternal, it should be a snap for you to get one. [03:13] ;-) [03:13] so true :) [03:19] meh. he probably danced on a bus for them. [03:19] * maco ducks === santiago-pgsql is now known as santiago-ve [04:46] paypal works too [04:58] ooh, there is a new Kubuntu derivitive!!! ScottK this one is for you [04:58] http://hannahmontana.sourceforge.net/Site/Home.html [04:58] nixternal: Not new. [04:59] it is for me, so don't ruin that! [04:59] * ScottK considered it already for the 6 year old, but I have enough trouble with her letting her sisters use the box already. [05:01] NCommander: I just uploaded kde4libs for lzma support (you may not see it yet, I just uploaded it). Would you please rescore it so I don't have to sit through all 124 pending ia64 uploads before I upload kdebase for lzma support? [05:43] NCommander: Thank you or nevermind as appropriate. [05:45] nixternal: ping [05:47] seele: pong [09:11] hmmm quassel update for jaunty today... - will that break protocoll? [09:21] Nightrose: yes. [09:24] thx Sput [09:24] * Nightrose thinks people should be more careful with this then === Quintasan_ is now known as Quintasan === xerosis_ is now known as xerosis === zorael__ is now known as Zorael [10:52] oh rosetta, why doth thou spam me so [10:55] Riddell: cause you deserve it :) [11:33] _Sime: rdieter http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543730 ! [11:33] Debian bug 543730 in unknown "SIP 4.8 has a new (non-free?) license" [Serious,Open] [11:33] _Sime: any chance you could port pykde to pyside in the next five minutes say? :-/ [11:53] someone tested koffice 2.0.81? [11:53] neversfelde: where is it? [11:54] Riddell: in the staging ppa [12:01] neversfelde: installs perfectly [12:01] as an upgrade from previous koffice [12:01] runs great too [12:01] krita crashed on close [12:01] we need to create a Beta ppa for this [12:01] there are a few problems, kformula is not working and kplatowork is not correctly placed in the menu [12:02] I am not sure, if this is my fault because both is new [12:06] Riddell: isn't the experimental ppa for such packages? [12:06] neversfelde: no experimental is more anything we want to chuck in to try [12:07] beta should be released versions of KDE, KOffice, Amarok betas [12:07] ok, another ppa then :) [12:08] I will create Jaunty packages if there are no problems with installing koffice [12:09] neversfelde: please do [12:12] ook, markey did an upgrade to the 185 nvidia driver and can't start x anymore (Karimc that is), any pointers on how to help him? [12:13] Mamarok: remove xorg.conf, start X again, do an nvidia-xconfig, restart X [12:14] at least that is the first thing I would do [12:14] ok, will tell him to do so :) [12:15] seems to work, thx neversfelde :) [12:15] :) [12:16] yeah, his on again :) [12:16] markey: say thx to neversfelde [12:16] and report a bug :) [12:16] probably the module was not build correctly, if the problem happens again, reinstall nvidia-glx-185 [12:16] hehe, yes that too [12:17] thx :) [12:17] someone stole the kopete tray icon [12:18] * Mamarok hides it but will not tell where [12:18] neversfelde: trying the message indicator in its place [12:18] which for some reason is called Indicator Displya [12:18] which for some reason is called Indicator Display [12:18] is it a widget? [12:19] plasmoid [12:19] we should work out how to get it added to the panel on upgrade [12:23] question is if kpresenter is good enough for the talk I'm doing this evening :) [12:24] /msg nickserv register 123456 goufra@gmail.com [12:25] Riddell: at least you can report some bugs :) [12:26] fox___: do be careful with that [12:27] alright, all is good again [12:27] :) [12:27] that indicator display is very confusing at the moment [12:28] i don't speak english [12:28] neversfelde: agateau is waiting for your feedback :) [12:36] I think I have to find out how to use it before :) [12:36] well it lights up when you get a message and the app isn't in the forground [12:36] assuming you have the latest kopete [12:37] and assuing the indicator plugin is turned on (which k-d-s should do) [12:37] but if there is no kopete tray icon, how to start the main app? And why is it the only application that lost it, kontact is still in the tray [12:38] so is choqok, akregator and quassel. I guess the user will be very confused, if that is not consistent [12:39] neversfelde: the v2 api of indicators should let you start applications from the plasmoid [12:39] but it's not ready yet [12:40] there are two notification systems now, kde's own and the indicator display, more confusing. So I could not follow the notification discussion as close as I should to give a good feedback [12:40] neversfelde: what do you mean with "kde's own"? [12:41] agateau: the kde notification system [12:41] hi [12:41] neversfelde: this is different: notifications are about instantaneous feedback, indicators give you permanent information [12:43] agateau: so all permanent information should go to the indicator? [12:43] neversfelde: they can overlap [12:44] neversfelde: an app can decide to fire a notification to let you know that something is happening, [12:44] neversfelde: and also show an indicator so that if you are away/busy and the notification goes away, you don't miss anything [12:46] ok, I think I understand and what was the reason for removing the kopete icon from tray? [12:47] it serves the same purpose as the message indicator, but without useful stuff like telling you who has pinged you [12:48] wasn't it possible to for example change the online status from this icon? I can't remember :) [12:50] neversfelde: yes, IIRC [12:50] neversfelde: it's now a bit more hidden, since you have to switch to the application (but you can do so from the indicator) [12:51] neversfelde: I think we miss a global status plasmoid, similar to what is done on the GNOME side [12:51] is it planned that quassel use the indicator display, too? [12:52] neversfelde: the patch is done yes [12:52] nice [12:52] our users will protest^^ but the idea is good. [12:53] neversfelde: I guess there will be protests :) but at worst you can turn things off and go back to the previous behavior [12:53] hehe [12:53] agateau: thanks for the info [12:54] neversfelde: part of my job to spread the word :) [12:54] :) [13:10] Nightrose: You're running backports. So yes, you should be careful. [13:12] agateau: It has to be off by default. That was the agreement. [13:13] agateau: I can also revert the patch and let everyone go back to the previous behaviour. [13:13] ScottK: It's up to you packagers, I was just under the impression that k-d-s put it on by default for Kopete [13:13] based on what Riddell said [13:14] Riddell: The agreement at UDS was that this would not be enabled by default. [13:15] ScottK: it's on for testing, I think it's a vast improvement and we should keep it on but we should have a discussion and vote about that [13:15] ScottK: Unfortunately, I do not have time until FF to implement an Ayatana switcher :/ [13:15] Riddell: We're at FF. Things should be configured the way we want to release. [13:16] you can always turn off features after FF [13:17] We should be testing what was spec'ed. [13:18] None of this is upstream yet and our clear agreement was that we would follow upstream in our default configuration. [13:20] In happier news, ark with lzma support should be available in my PPA. Testing appreciated. [13:22] upstreaming is on my todo for first thing next week [13:23] Mamarok: is there a solution for the not working lyrics script in amarok somewhere? [13:26] apachelogger: We ought to look at packaging for quassel-core now that it can support a pg backend too. === javi_ is now known as javi [14:09] neversfelde: there should be a patch available indeed, ask lfranchi in #amarok.dev [14:27] Mamarok: already found it thanks [14:28] ok :) [14:29] I got lzma support uploaded in kde4libs and ready to go in kdebase-runtime and kdeutils (for ark). It'd be handy if someone could check and see if any other KDE packages want lzma. It'll be something like this in the build log if it does: -- Could NOT find LIBLZMA (missing: LIBLZMA_INCLUDE_DIR LIBLZMA_LIBRARY LIBLZMA_HAS_AUTO_DECODER LIBLZMA_HAS_EASY_ENCODER LIBLZMA_HAS_LZMA_PRESET) [14:29] JontheEchidna: You might want to take another look at Quassel now. It's grown up quite a bit last night. === yuriy changed the topic of #kubuntu-devel to: Feature Freeze today | apachelogger loves you all | http://www.kubuntu.org/news/karmic-alpha-4 | https://wiki.kubuntu.org/Kubuntu/Todo | We need paperKuts! https://launchpad.net/hundredpapercuts [14:49] my quassel-core is borked now :) [14:50] How so? [14:50] I cannot connect anymore, although /etc/init.d/quassel-core status says it is running [14:51] probably it needs some time to restore the sessions [14:51] Did you just upgrade from jaunty-backports? [14:51] yes [14:51] You'll need to upgrade your clients too. [14:51] they are karmic [14:51] and 0.5.0-rc1 [14:51] OK. That should work. [14:52] agateau: ping [14:52] My Jaunty core that I tested it on upgraded fine. [14:53] rgreening: pong [14:54] agateau: some thoughts/questions on indicator app [14:54] rgreening: go on, but I have a call in 5 minutes [14:55] agateau: when I have awaiting messages (like kopete/Kontact(kmail)) shouldn't it allow me to click the listed app in the message indicator and allow me to raise/open the app [14:55] agateau: otherwise it is kind of useless (IMO) [14:55] rgreening: if it does not, it's a bug [14:55] :) [14:55] it does not [14:55] :P [14:55] which app? [14:55] oh.. let me qualify that [14:56] 1) Kopete doesnt [14:56] is it when clicking on app or on indicator? [14:56] 2) kontact - raises to front only if window was open and in the background. does not if it was closed (but running in the background via the kmail icon in systray) [14:57] agateau: for kopete, if I click the message indicator and it shows me kopete, and I click it there, nothing... [14:57] rgreening: Doesn't turning off focus stealing prevention help? [14:58] ScottK: ? [14:58] ScottK: it should not, I am using the same API as taskbar [14:59] agateau: well the kopete issue could be something else. my kopete icon doesn't even show in system tray anymore... since yesterdays updates... [14:59] (call time) [14:59] rgreening: Focus tab in Window Behavior in systemsettings. [14:59] agateau: however the kontact/kmail not opening when minimized to tray is a bug [15:01] ScottK: that does nothing [15:01] the issue is not raising/opening when minimized to system tray [15:02] the app is running, but the window is hidden. should be a way to open the window (i.e. unhide it) again [15:02] s/not//g [15:03] the kopete issue may be something else. need to test something... [15:06] agateau: If I disable the kopete indicator integration, I get my kopete Icon back in system tray. something is broken with the support in Kopete for the indicator. [15:06] rgreening: OK. Just a thought. [15:08] agateau: and it seems that the change to enable the indicator caused all my settings to get lost in kopete. Well I assume that was the culprit.... [15:11] ScottK: quassel 0.5.0 is in your ppa? [15:11] seele: It's 0.5 rc1 and yes. It's also in jaunty-backports. [15:17] agateau: also, I can disable integration in Kopete, which is awesome. What about Kontact/Kmail? I couldn't see a way to enable/disable it.. it just seems to be on regardless :) [15:17] or does it matter? [15:19] It does matter. [15:19] It's supposed to be cofigurable and off by default. [15:20] agateau: hmm.. and now I cannot get into my akregator (which was integrated in Kontact). It just crashes... I am guessing related to the indicator thing. Is there a rc file I can edit to disable the indicator message stuff in kontact/akregator so I can test the theory? [15:21] ScottK: it was on and not via a choice I made [15:21] rgreening: Yes. I was kvetching at Riddell about that earlier. He says it's on for 'testing'. [15:21] and doesn't seem to be configuarble in Kontact. Kopete it was turned on and it may have wiped my account config [15:21] ScottK: i am - that's why i noticed ;-) the thing is other people might not and get locked out of their quassel [15:22] ok... but we need a "on/off" switch [15:22] I can't get me feeds now :( [15:22] Nightrose: True, but there are plenty of people who run karmic desktop and jaunty server so I think I really had to put it in backports. [15:22] Nightrose: I did the same thing with 0.4 and intrepid/jaunty. [15:22] agateau: Object::connect: No such signal Akregator::SubscriptionListView::signalDropped (KUrl::List &, Akregator::TreeNode*, Akregator::Folder*) [15:22] and then crash [15:23] ScottK: *nod* [15:25] ScottK: ok really confused. so 0.5.0-rc1 is installed but i got a package error because libqt4-phonon isn't installed [15:26] but i cant install libqt4-phonon for some reason [15:26] Hmmm. [15:26] I'm running it on Jaunty here. [15:26] oh.. quassel-data installed [15:26] Ah. [15:26] would that change the about version text? [15:26] but not actually quassel? [15:26] You need to update quassel-data too. [15:26] i did [15:26] Oh. [15:27] i installed quassel-data first then quassel [15:27] agateau: so, in further testing... when I disable Kopete integration and then readd it, the system tray icon seems to be available again. this is bizarre. [15:27] and quassel is what failed [15:27] i have jaunty-backports enabled [15:27] agateau: maybe it was a symptom of having it enabled by default with a previously configured and working kopete.. [15:30] weird [15:31] seele: What was the exact error? [15:31] rgreening: /me reads the backlog [15:31] ty agateau [15:32] ScottK: quassel: Depends: libqt4-phonon (>= 4.5.1) but it is not installable [15:32] -f install doesnt help [15:32] rgreening: how do you " disable the kopete indicator integration"? unchecking the plugin? [15:32] agateau: yep [15:32] seele: Looking [15:32] Here the systray icon presence is independent of this [15:33] I don't see how it could wipe your configuration, given the fact that it has no configuration [15:34] agateau: it's weird. I disabled the integration and exited and restarted kopete and got my icon back. I re-enabled the plugin and restarted kopete and the icon stayed... seems something broke in the default "enabled" plugin state of the rc file... [15:34] agateau: I lost some configuration like meta contacts, too [15:34] seele: Are you sure you don't have some karmic repose listed in sources.list? According to LP, the jaunty backport doesn't depend on that. [15:34] Im not the only then :) [15:34] seele: Did you install from my PPA or jaunty backports? [15:35] Also, logs seem to br broken since the update . Kopete doesn't show me my chat history anymore... but they are still written and saved to disk. [15:35] never_web: rgreening: I would be interested in a scenario to reproduce that [15:35] ScottK: first i downloaded the two packages from your ppa, when quassel install failed, i enabled jaunty-backports which didnt help [15:35] * rgreening doesn't have time machie.. haha [15:36] never_web: do you use kopete chat logs? and can you see if yours work? [15:36] ScottK: uhm.. well i'm in karmic? [15:36] er no i'm not [15:36] wrong machine [15:36] this is definitely jaunty [15:36] OK. [15:37] ah here they are :) [15:37] rgreening: next item, kmail configuration [15:37] rgreening: I added a configuration option to enable/disable indicators in KMail [15:38] rgreening: let me dig in the vast pile of sh*t that is kmail configuration dialog [15:38] agateau: bwahahahahah! [15:38] seele: I'm confused. I've checked the Jaunty packages in my PPA and backports and neither depends on libqt4-phonon. Only the karmic ones do. [15:38] agateau: yeah. I couldn't find it [15:38] needle meet haystack [15:39] ScottK: argh, i wonder if i downloaded the wrong packages (even after checking to make sure i clicked on the jaunty ones..) [15:39] rgreening: Go to "Accounts" [15:39] rgreening: then in the "New Mail Notification" group [15:39] seele: Please do less /etc/apt/sources.list and make sure there's no karmic references in the file. Also any files in /etc/apt/sources.list.d. [15:39] rgreening: there is a "Use message indicator" checkbox [15:40] not here [15:40] rgreening: oh [15:40] seems that piece isn't patched in [15:40] :) [15:41] did you provide patch to someone to upload? [15:41] rgreening: this may have been lost when I backported the patch from trunk to 4.3.0 [15:41] ah [15:41] we need :) [15:41] hehe [15:41] rgreening: all patches are at http://people.canonical.com/~agateau/indicate/ [15:42] ok, will this piece be in one of those patches? [15:42] rgreening: it's in the kmail patch, at least the trunk one [15:43] ok. and for the last item... akregator bombs.... [15:43] rgreening: I am 99% sure I messed up when backporting [15:43] rgreening: I didn't touch akregator [15:43] rgreening: what happens if you run it alone? [15:43] 1 sec... [15:44] Object::connect: No such signal Akregator::SubscriptionListView::signalDropped (KUrl::List &, Akregator::TreeNode*, Akregator::Folder*) [15:44] Object::connect: (sender name: 'feedtree') [15:44] Object::connect: (receiver name: 'akregator_view') [15:44] agateau: I have it integrated in Kontact... [15:45] rgreening: I know, but I was wondering if the behavior was different in this case [15:45] so I assumed the "indicator" should also work with it as it does with Kontact/Kmail... [15:45] rgreening: no, it only works with kmail ATM [15:45] agateau: running seperate causes crash [15:45] ok [15:45] does the error above point to anything specific? [15:46] it's a bad connect() between a signal and a slot [15:46] It worked last night.. today, after reboot it bombs [15:46] this should not cause a crash [15:46] window just closes [15:46] you updated between, didn't you? [15:47] last thing was the kde updates [15:47] and then a reboot this am [15:47] ScottK: ok think i got it now [15:47] although i thought they changed "Buffers" to a different label... [15:48] agateau: is there an rc entry I can make to disable the indicator in Kontact/Kmail? [15:48] rgreening: yes, let me get it [15:48] kk [15:49] rgreening: General/UseMessageIndicator [15:49] set it to false [15:51] seele: it should be labeled "All chats" [15:51] or at least it is here [15:52] do i need to remove my quassel data for that to change? [15:52] agateau: is that in kontactrc or kmailrc [15:52] I wouldn't think that you'd need to [15:52] though I did wipe the quassel config (~/.config/quassel-irc.org) [15:52] rgreening: kmailrc [15:52] kk. thought so [15:54] agateau: doesn't seem to do anything [15:54] still indicates when set to false [15:54] rgreening: yet another bug, then :/ [15:55] hehe [15:55] thats what devel is for [15:55] producing bugs to be solved [15:55] indeed :) and testers [15:55] ginuea pigs [15:56] so.. the akregator thing may be a seperate issue... [15:56] I'll just zap my config and try again :) [15:56] I think so [15:57] In regards to Konversation 1.2: [Wednesday 26 August 2009] [4:06:21 pm] Well, ok, so the deadline is Sept 10th. If the ircview is not in by Sept 10th, we'll have to wire up marker lines the old-fashioned way, fix bidi, string-freeze, release. [15:58] On a related subject, I am starting to get a bit worried about K3b [15:59] k3b upstream seems to have died again :( [15:59] agateau and Riddell: I'm just reading my Ubuntu mail and discover that publishing the API for the messaging menu is deferred. Is it really suitable to be patching in KDE svn KDE core packages to operate with some private API? [16:00] oh, there's a little bit of svn activity for k3b [16:00] ScottK: what do you mean with "deferred"? libindicate is an upstream project, with standard releases [16:01] agateau: The latest change in dx-karmic-messaging-menu spec from davidbarth says document/publish API: POSTPONED (xdg process). [16:02] So I'm just reading what's been published. [16:02] ScottK: oh ok [16:02] ScottK: this does not make it "private" [16:03] agateau: The difference between private and unpublished is pretty narrow. [16:03] ScottK: I don't know how to create an unpublished api in opensource [16:04] agateau: I don't think "Here's a pile of code" is the same as publishing an API. [16:04] ScottK: at the very least you have the headers files [16:04] ScottK: it would not be the first library without formal documentation [16:04] and at least the headers are commented so documentation can be generated with gtk-doc on the gtk side [16:05] and doxygen on the qt side [16:05] If it's trivial to publish documenation, then I don't see what it's being avoided then. [16:05] ScottK: what's non trivial is getting the spec approved by FD.o [16:06] that's probably what davidbarth meant with publishing [16:06] Could be. Is the API documentation in the package? [16:07] IIRC you can generate it with "make gtk-doc" or something like that [16:07] OK. Well then at best it's poorly packaged at this point. [16:09] facebook plamoid defaults to french for me... weird... [16:10] ScottK: it's in libindicate-doc [16:11] rgreening: facebook plasmoid is just a webview. maybe facebook is detecting you live near Quebec? [16:11] Riddell: it's detecting Canada and defaulting toFrench. wtf... English is the first language and french is second. grr [16:11] ScottK: yes, sorry; the doc is actually in the .h files and available of course [16:12] ScottK: it was only meant to say that we'd like that to go through a good xdg process now; and that may bring us to something later than the karmic milestones [16:12] rgreening: I think the Qubecois may disagree with your ordering :) [16:13] rgreening: it's part of the French conspiracy };> [16:13] only the seperatists.. and they can seperate if they want :) [16:13] heheh [16:14] but they only get quebec city and "Juste pour Rire" [16:14] :P [16:14] oh my [16:14] davidbarth: OK. Thanks for clarifying. [16:14] seriously though... it shouldn't default to french... odd. My profile has english set... [16:15] Riddell: Thanks. [16:18] Riddell: who do I talk to about the Power Management / Battey Applet not detecting my battery? [16:19] rgreening: the relevant developers of linux, udev, hal, solid, powerdevil depending on where the problem is [16:20] or your hardware for that matter [16:23] just added ibus-qt4 plasma-widget-kimpanel plasma-widget-facebook plasma-widget-googlecalendar plasma-widget-kubuntu-qa-feedback to the seeds [16:27] * JontheEchidna updates QtCurve [16:28] lucky they made their feature release the day of feature freeze [16:33] JontheEchidna: We're past FF now. [16:33] Would have been better if they did it yesterday. [16:33] crap [16:33] think I could sneak it in w/o a FFe? [16:34] It'd be your sponsor that gets spanked in any case. Just claim it's bugfixes. [16:35] also, what's the policy on sync requests filed before feature freeze, but that still need synced? [16:35] I still recon we're on the edge of feature freeze [16:36] (for example, bug 419210) [16:36] Launchpad bug 419210 in strigi "Sync strigi 0.7.0-1 (main) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/419210 [16:36] it has a bugfix for a quite visible crash, so we definitely want it [16:37] If it was filed before FF, I thin kit should get in. [16:37] ..k.. [16:37] * Riddell makes it so [16:39] done [16:39] yay [16:39] * ScottK whistles innocently. [16:51] looks like we can sync kde-style-qtcurve now that debian updated it to KDE4 [16:53] nevermind, we have a few conflicts/replaces that need keeping [16:53] means we can't sync until 10.10 :( [17:17] where did my kopete icon go? [17:17] nixternal: It went to the Ayatana project. Talk to agateau. [17:18] how do I open up my contact list then? [17:18] ScottK: I didn't touch the systray icon [17:18] ScottK: I only added a new plugin! [17:18] Dunno then. [17:19] * ScottK doesn't IM very often at all. [17:19] I went into Kopetes config, and I noticed that "Show system tray icon" was unchecked after update...so I checked it, clicked apply...but nothing happened :/ [17:23] ok...just needed to uncheck/apply both the system tray icon and the message indicator plugin, and then restart kopete [17:24] nixternal: I would not be surprised if, [17:25] 1: systray icon had been removed from u-d-s, [17:25] 2: toggling the plugin on and off required a Kopete restart [17:26] agateau: also note that this could be just me, because this system has been dist-upgraded since Dapper :) [17:26] nixternal: wow! [17:26] * agateau does not do dinosaurs [17:26] no reformat/reinstall in almost 4 years now...because it started in 2005 with one of the Dapper Flights :) [17:26] Riddell: new patches, to make KDE apps integrate better with notify-osd: http://people.canonical.com/~agateau/capabilities [17:26] agateau: u-d-s as opposed to uds. what is this? [17:27] from time-to-time I have to clean up some stuff to get speed back, but I want to keep doing it to this machine until the machine dies, just to see how long it can go before it is borked [17:27] maco: I meant k-d-s: kubuntu-desktop-settings package [17:27] ah ok [17:27] ya, should have been kds or k-d-s :) [17:27] nixternal: how's fragmentation doing? [17:28]