[00:08] <odla> is it a known bug that firefox 3.5 in karmic has enormous fonts with qtcurve by default?
[00:10] <JontheEchidna> looks fine here
[00:11] <odla> hmm ... for raleigh the fonts look fine just not for qtcurve
[00:11] <lex79> odla: on fresh install?
[00:11] <odla> lex79: on live cd
[00:12] <lex79> yes, JontheEchidna I remember now, there was that problem on a fresh install
[00:12] <odla> lex79: so it should be resolved if i install it and get my box current?
[00:12] <lex79> but looks fine here too
[00:13] <odla> maybe wrong dpi?
[00:14] <lex79> odla: try to change the kde font in system settings and back to default again
[00:14] <odla> ok
[00:15] <lex79> and try to change the size of fonts, I remember something like this...
[00:17] <odla> ok it looks better ... still not the same size font but at least it's not like 16 pt
[00:18] <odla> also ... related perhaps ... the name of my location on the weather plasmoid is too big for the plasmoid ... i.e. i can't read the location as the fonts overlap one another
[00:19] <Tscheesy_> Hi - after Jaunty Backports-ppa update yesterday - Hal did not find my Monitor anymore - there also was an icon-Package damaged.. running a new Karmic-Desktop now
[00:20] <Tscheesy_> i810 - running fine though
[00:20] <odla> lex79: nevermind ... fonts look great now .. thanks for your help ...
[00:21] <Tscheesy_> there was a kernel-massage about missing kernel-module capacity or something alike
[00:21] <lex79> odla: have you defult fonts in systemsettings now?
[00:21] <odla> lex79: yes
[00:22] <odla> but the weather plasmoid fonts still run over one another
[00:23] <lex79> JontheEchidna: seems related to startkde script, qtcurve doesn't read the size of kde fonts. Maybe
[00:25] <Tscheesy_> btw - i do have Fonts Problem in the fresh Karmic-Daly-Konsole - i modified the prompt earlier
[00:25] <Tscheesy_> i have some blanks following the prompt
[00:47] <JontheEchidna> ~np
[00:47] <kubotu> dualscreenman is listening to "Explosive" by Bond [Classified, 2004]; see http://www.last.fm/user/dualscreenman for more
[02:18] <jjesse> what's the do-release-upgrade command for upgrading from jaunty to karma while still in beta?
[02:19] <ScottK> jjesse: sudo do-release-upgrade -d
[02:27] <jjesse> ScottK thanks
[02:44] <ScottK> Nothing like getting to download ~20mb of KDE3 libs because it's the first KDE 3 app I've put on this machine and do it with airport wifi...
[02:46] <claydoh> which app?
[02:46] <jjesse> ouch
[02:46] <jjesse> some airports actually have decent wifi in them believe it or not
[02:46] <claydoh> non-updates apps must be getting fewer and fewer
[02:47] <ScottK> kivio
[02:47] <DarkwingDuck> there are slights from LA to San Fransisco have WiFi in the airplane itself :D
[02:47] <DarkwingDuck> *flights
[02:53] <ScottK> Yah.  Airplane fixed.  We get to board ....
[02:56] <jjesse> most of the longer flights on delta have wifi
[02:56] <jjesse> in fact delta has more wifi enbled planes then any other
[10:31]  * micmord wonders if it's normal having "/.kde" and "/.config"
[10:33] <Sput> well, .config is XDG standard
[10:33] <Sput> but some programs and most of KDE prefer otherwise :)
[10:34]  * Sput thinks .kde should move to .config/kde.org
[10:34] <micmord> I have /.config/Trolltech.conf
[10:36] <Sput> actually, I do have .config/kde.org
[10:36] <Sput> phonon and systemsettings store their config there
[11:19] <Riddell> JontheEchidna: aw fooey, I entirely failed to do konversation
[11:33] <Riddell> JontheEchidna: uploaded
[11:34]  * smarter waves
[11:34]  * smarter just reinstalled his OS on a shiny new SSD
[11:34] <Riddell> Sput: canonical has had customers who wonder why not all apps follow the xdg spec in using .config, and of course we point out that those are almost all apps which existed long before anyone thought of .config and it would be a troublesome hassle to move them for no real gain
[11:34] <Riddell> smarter: SSD?
[11:35] <smarter> Solid State Drive: http://en.wikipedia.org/wiki/Solid-state_drive
[11:35] <smarter> these things are fast, grub->kdm takes between 5 and 10 seconds
[11:36] <Riddell> at last, the fabled under 10 second boot!
[11:36] <Riddell> although really it should be 10 seconds to working desktop
[11:37] <smarter> I'll have to make better measurement, but my bios is probably responsible for a third of the boot time
[12:05] <valgaav> untransalted parts of systemsettings in polish language is a bug to report ?
[12:32] <Sput> Riddell: we used to have .quassel, but switched shortly before the 0.4 release (including some migration code... which I should probably remove at some point ;-))
[13:51] <blueyed> How does KDE interfere with mouse buttons? when using an xterm session (or gnome), the middle mouse button works, with kde it won't (button 2 and 3 both trigger 9), pointer = 1 9 2 4 5 6 7 3 8
[13:54] <blueyed> is "Button Order" meant to be grayed out in "Mouse settings" btw?
[14:08] <blueyed> This happens with using "xinput set-button-map" in the same way: as long as I map the 2nd physical button to something greater than the third one, the third gets the same mapping as the second.
[14:09] <blueyed> as said: this is kde specific.. what interferes here?
[14:23] <blueyed> ok, grayed out, if you have a different xmodmap
[14:23] <blueyed> will file a bug about this.. kdebase?
[14:33] <blueyed> bug 448021
[16:19] <astromme_> Hey I have a question about adding a patch to kdeplasma-addons to bugfix the rememberthemilk widget
[16:20] <astromme_> rememberthemilk.com wasn't happy with how I was using their api key (specifically allowing users to log in without using the website to auth)
[16:20] <astromme_> So I made the necessary changes in kde trunk. But there are some string changes so it didn't get backported to 4.3.2
[16:21] <astromme_> As of now the applet is broken in 4.3.x, but I have patches to make it work. Is there a chance to get these into Karmic?
[16:24] <Nightrose> astromme_: if you give me commit numbers I can post it to the devel list for you
[16:24] <Nightrose> weekend is usually slow here
[16:24] <astromme_> Nightrose: devel list as in kubuntu-devel?
[16:25] <Nightrose> yes
[16:25] <astromme_> Nightrose: the changes were spread across a number of commits. Would patches be better? (I have them ready)
[16:25] <Nightrose> that's probably even better yea
[16:26] <astromme_> Nightrose: ok, give me a sec to get them on the web.
[16:26] <Nightrose> sure
[16:31] <Nightrose> astromme_: i'll go and take a nap - not feeling too well - just post the link here and I'll send an email later
[16:32] <astromme_> Nightrose: no problem, it'll take me a bit
[16:32]  * astromme_ discovered some not-so-good formatting with his diff/patch output
[16:46] <astromme_> Nightrose: oh boy, that's way bigger than I thought. Hmm.... well, here it is. *should* apply cleanly. http://pastebin.ubuntu.com/290177/
[16:49] <Sime> sebas: I'm enjoying The Big Bang Theory a lot BTW. :-)
[18:19] <Nightrose> astromme: posted - thanks :)
[19:27] <Vistaus> hello :)
[19:29] <Vistaus> you're doing a great job with 9.10, since the release of 9.04 Kubuntu has improved so much! I'm already doing a lot of things foor the *buntu community and help out with KMess, and now I decided I want to help out 9.10 too. but I don't know any programming andI can't test 9.10 right now due to a  little problem with VB. Is there anything else I can doto help with 9.10?
[19:56] <grifis87> Hello to everybody
[19:57] <grifis87> will opensuse firefox kde integration be in karmic too?
[19:58] <grifis87> is it at least planned in karmicé*
[19:58] <grifis87> in karmic+1?
[19:58] <apachelogger> no, no
[19:59] <apachelogger> ubuntu-mozilla's team leader thinks that stuff should go into firefox itself rather than patched in I got told
[20:00] <grifis87> oh, I understand :) ...well, thank you apachelogger for your answer
[20:01] <grifis87> I thought about a firefox-kde integration deb, like the firefox gnome one...well we'll see...thank you again
[20:03] <Vistaus> @apachelogger: If the ubuntu-mozilla team thinks that way, than you can also say that kde integration for OpenOffice.org should be patched in OOo
[20:05] <Vistaus> also, I want to leave a note for the developers ;) twitter support for the microblogging plasmoid is broken upstream (upstream in KDE) so I don't know if it's a good idea to put it n the default desktop in 9.10 (althoug I am a big fan ofthat plasmoid and the social desktop)
[20:06] <Vistaus> https://bugs.kde.org/show_bug.cgi?id=200475
[20:10] <Vistaus> there is enough info, the developer just hasn't responded yet
[20:10] <Vistaus> or looked into the issue
[20:10] <Vistaus> but even then, twitter support is broken
[20:11] <apachelogger> ehm
[20:11] <Vistaus> so is it a smart idea to put the plasmoid on the default desktop then?
[20:11] <Vistaus> you can alsways add it via add widgets anyways
[20:11] <apachelogger> Vistaus: you mean we should make an upstream implementation a patch for the sake of argument?
[20:12] <Vistaus> I'm a fan of the social desktop, but it's not so good to put a half wortking widget on a default desktop
[20:13] <Vistaus> apachelogger: if you guys can fix the problem, that would be awesome. but if you cannot,  it's not such a good idea to put a half working widget on a default desktop
[20:13] <Vistaus> but that's just my opinion
[20:13] <apachelogger> I was refering to you statement about ooo really
[20:13] <apachelogger> and I doubt we have the resources to fix the micro blog plasmoid
[20:13] <Vistaus> ow im sorry i misunderstoon you
[20:14] <Vistaus> well then it should be considered again if the mb widget is on the default desktop
[20:14] <apachelogger> yeah, just sent a mail
[20:14] <apachelogger> Vistaus: btw, for reference ... http://svn.services.openoffice.org/ooo/trunk/vcl/unx/kde4/
[20:15] <apachelogger> we actually do stuff upstream, unlike opensuse :P
[20:19] <Vistaus> actually, mozilla doesn't want the integration
[20:20] <Vistaus> they want to "only support the desktops that they have intrest in"
[20:23] <apachelogger> dont tell me :P
[20:23]  * apachelogger does not exactly bother about mozillas weird policies
[20:29] <grifis87> if mozilla doesn't want to integrate kde integration upstream, then a separate patch seems like the only way to go. Is the ubuntu mozilla team aware of this issue with upstream mozilla?
[20:34] <Vistaus> grifis87: yes
[20:34] <Vistaus> they are aware of it