[01:11] <ryanakca> Errr... Is OO.o calc supposed to freeze when someone tries to save for the first time?
[01:18]  * ryanakca tries to figure out how to get a backtrace
[02:12] <echidnaman> Riddell: bug 451915, looks a bit serious
[02:12]  * JontheEchidna 's internet is crappy tonight
[02:42] <shtylman> ryanakca: yes... its a feature (seriously...no...sounds like a bug)
[03:03] <shtylman> anyone read this? http://www.itnewstoday.com/?p=1032
[03:03] <shtylman> thoughts?
[03:03] <shtylman> mindless rants?
[03:07] <JontheEchidna> "Version 9.10 is definitely good so far, but still far from perfect." <- so not much of a downward spiral, then :/
[03:07] <yuriy> downward spiral? a little bit, but you gotta fall a bit to get momentum for the ramp : )
[03:09] <JontheEchidna> some points are good, but a lot of it is: "I don't like KDE's default artwork which nobody else uses plus my wireless has been busted for two releases"
[03:11] <JontheEchidna> comments are much more informative than the actual article imo
[03:13] <yuriy> some people screaming too much patching, others screaming too vanilla...
[03:13]  * yuriy does agree on the wallpaper and (unmentioned) KDM theme though
[03:13] <JontheEchidna> The upstream KDM theme could be improved usability-wise
[03:14] <yuriy> maybe that too, but I think we've got to get a Kubuntu logo on there
[03:14] <JontheEchidna> with the proper branding maybe upstream art would be sufficient
[03:14] <yuriy> pretty much
[03:14] <JontheEchidna> we can never please the haters, but who cares?
[03:22] <JontheEchidna> vorian: ping
[03:29] <shtylman> I think the little things make a big impression (thus the papercut stuff we have)
[04:21] <lex79> kamoso 1.0.4 is still broken :(
[04:31] <yuriy> " the instructions for filing bugs on Launchpad ignored Kubuntu altogether, I had to add a link to the Kubuntu instructions myself." interesting. I though bdmurray had done that on my request
[04:39] <yuriy> ooh purty http://www.kde-look.org/content/show.php/KubuntuVision?content=113319 though too dark for my tastes. maybe he could make a more mainstream version
[05:53] <ScottK> Anyone else having trouble with lid open events not being recognized?
[08:54] <sourcemaker> I have a kernel panic with the message: fixing recursive fault but reboot needed"... I think it is nepomuk related... can I find the root course of this problem?
[10:42] <Riddell> jtechidna: hmm, python really shouldn't give a segfault (bug 451915) I wonder if he hasn't updated all the new sip/pyqt bits
[10:42] <Riddell> I'll try today's CD and see if it's a problem there
[10:59] <hettar> Silly question perhaps, but in 9.10 is it possible to have network manager NOT login to the wifi automatically when connected via cable ? It keeps messing up my routing
[11:02] <Riddell> in my experience it doesn't login to wifi automatically
[11:03] <Riddell> but that's mainly an upstream request
[11:04] <hettar> hmm ok
[11:34] <ryanakca> shtylman: Can you reproduce it? I can't seem to manage to find out how to get a backtrace for something that hangs but doesn't crash... Or would I not need one?
[11:43] <debfx> where do kded services log to? ~/.xsession-errors?
[12:02] <Riddell> debfx: if you killall kded4; kded4 it'll put debug output in the terminal
[12:02] <Riddell> debfx: and you have to turn it on in kdebugdialog first
[12:11] <davmor2> Riddell: thanks for the update on the bug :)
[12:14] <EagleScreen> is ipv6 enabled in Kubuntu 9.10?
[13:20] <tsimpson> EagleScreen: it's enabled in the kernel, and so available to everything IPv6 aware, including KDE
[13:21] <EagleScreen> oh thnaks
[13:27] <ScottK> agateau: Thanks for the quassel patch.  Worked great and Sput applied it before 0.5 was released.
[13:28] <agateau> ScottK: good news
[13:28] <Sput> agateau: I did miss your other patch though and couldn't get it into 0.5.0 :/
[13:28] <ScottK> agateau: Yes.
[13:28] <ScottK> Sput: Which one was that?
[13:28] <agateau> Sput: the one about toggling the main window?
[13:28] <Sput> yeha via indicator
[13:28] <Sput> the one you sent by mail... I didn't check mail before tagging
[13:28] <agateau> It may not need to be applied
[13:29] <Sput> well, I did apply it post-tag :)
[13:29] <agateau> I realized this morning that it would make kde apps behave differently than gnome apps with regard to indicators
[13:30] <agateau> I started a discussion on this on kubuntu-devel ML,
[13:30] <agateau> if everybody agree, I'll post patch to switch back to "switch to app" behavior, rather than "toggle"
[13:31] <ScottK> I guess I better go read the mail, because I'm not sure I understand the difference.
[13:31] <agateau> Sput: I'll let you know if we agree on the "switch to app" behavior
[13:31] <agateau> ScottK: yes please :)
[13:31] <agateau> ScottK: but the difference is simple: when the app is in front,
[13:31] <agateau> right now clicking the indicator app entry hides it,
[13:32] <ScottK> Ah, I see.
[13:32] <agateau> while for gnome apps, it just ensure the app window is focused
[13:32] <Sput> agateau: ok, just so you know, your patch is applied but not in 0.5.0, but it'll be in 0.5.1 unless you send another patch disabling it (or tell me to revert) :)
[13:32] <agateau> Sput: ok, will do so if the "switch to app" behavior is decided to be the right noe
[13:32] <agateau> *one
[13:32] <ScottK> agateau: If I click on the quassel icon when I have a pending highlight, it swtiches me to the right channel.
[13:32] <ScottK> Is that what your patch does?
[13:33] <agateau> ScottK: if quassel was already visible, clicking on the quassel entry (not a channel entry) currently hides quassel,
[13:33] <ScottK> agateau: Not if there's a pending highlight.
[13:33] <Sput> that only affects the indicator bubble though, doesn't it?
[13:33] <ScottK> Just did it.
[13:33] <Sput> I mean, the patch in question
[13:34] <agateau> Sput: yes,
[13:34] <Sput> it didn't touch anything outside the inidicator backend
[13:34] <agateau> Sput: absolutely
[13:34] <Sput> the tray behavior just now should be consistent with the rest of KDE
[13:34] <agateau> Sput: yes, the tray behavior is not affected
[13:34] <Sput> k
[13:34] <Sput> thought so :)
[13:34] <ScottK> If I understand what the patch does, it sounds like it makes the indicator consistent with the way the app works.
[13:36] <agateau> The question is: do we think app windows should hide when they are in front and their app entry is clicked?
[13:36] <agateau> ScottK: hiding when in front is the way systray icon works
[13:36] <agateau> ScottK: not hiding when in front is the way gnome indicate-enabled app work
[13:37] <agateau> ScottK: understand that I am talking about app entry, not indicator entry
[13:37] <agateau> (app entry == appname, indicator entry == child of app entry)
[13:38] <ScottK> Yes.
[13:38] <ScottK> Ping me please.
[13:38] <agateau> ScottK: ping
[13:39] <ScottK> Right, so I was in a different channel, clicked on the Quassel icon and I came straight here.
[13:39] <agateau> ScottK: if you have the 0.5.0 release, you get GNOME behavior
[13:40] <agateau> the "hide when on front behavior" is implemented by the patch I sent to Sput, but which did not make it in 0.5.0
[13:40] <agateau> so for Quassel it's already ok
[13:40] <agateau> but Konversation, Kopete and KMail patches need to be updated
[13:41] <agateau> because they implement "hide when on front" behavior
[13:41] <ScottK> agateau: I see.
[13:41] <Sput> what is the "app entry"?
[13:41] <ScottK> So it sounds like your patch makes the indicator consistent with the upstream icon behavior.
[13:41]  * ScottK needs to run.
[13:42] <ScottK> We can chat more later
[13:42] <agateau> ScottK: ok
[13:42] <agateau> Sput: for each application, the indicator shows an app entry
[13:42] <agateau> and every app indicators are shown as children entries of the app entry
[13:43] <agateau> so Quassel part of the indicator menu may look like this:
[13:43] <agateau> Quassel
[13:43] <agateau> - #chan1
[13:43] <agateau> - #chan2
[13:43] <agateau> Clicking #chan1 or #chan2 brings Quassel window to front and switch to the right channel
[13:44] <agateau> in 0.5.0, clicking Quassel brings Quassel window to front
[13:44] <agateau> but with the patch you integrated after 0.5.0, clicking Quassel will toggle the window:
[13:44] <agateau> hide it if it's already on front, show it otherwise
[13:49] <Sput> ok
[13:49] <Sput> so it behaves like the taskbar then
[14:25] <jjesse> morning
[14:46] <jjesse> intersting on my VM's for Karmic (both netbook edition and regular) after installing the beta release and updating, i see the kubuntu boot screen and then it flickers to a black screen any ideas what channged?
[14:48] <jjesse> running VMWare Workstation 6.5.3
[14:49] <jtechidna> It seems that ubuntu makes usplash kick in until it can start X for usplash/ksplashx
[14:50] <jtechidna> *xsplash/ksplashx
[14:50] <jtechidna> in which case the half-a-second ksplashx seems unecessary
[14:51] <jjesse> jtechidna was that in response to me?
[14:51] <jtechidna> yeah, I get that too
[14:52] <jjesse> maco: send me a private message when you get a second
[14:52] <jjesse> after an install of the beta version i'm able to login, etc but once i update and restart... bam black screen, no login
[15:43] <Riddell> dpm: did desktop-kdepim-runtime get sorted?
[15:44] <dpm> Riddell, not yet, sorry, let me ask danilo again what the best way to handle this is
[15:48] <Riddell> ArneGoetje: last cycle you had a list of translation templates that weren't assigned to packages, do you know if there are any like that is cycle?
[15:50] <ArneGoetje> Riddell: let me see...
[15:53] <ArneGoetje> Riddell: don't have any list right now. we will get a new translation export soon (should be available tomorrow. I will scan the langpack-o-matic logs for such templates then.
[15:55] <JontheEchidna> Riddell: could you ack bug 452715 please?
[15:55] <Riddell> JontheEchidna: ooh, what's it worth?
[15:56] <Riddell> a shoulder massage wouldbe nice, I could be bribed with one of them
[15:56] <JontheEchidna> 3.5 internets? :P
[15:56] <JontheEchidna> it does get harder to upload stuff after freeze, lol
[15:56]  * jjesse looks up a local messager in edinburgh for Riddell
[15:57] <Riddell> JontheEchidna: a debdiff and pointer to upstream bug would be handy
[15:57] <JontheEchidna> Riddell: upstream has no bug tracker, but I can get the debdiff
[15:57] <JontheEchidna> debdiff attached
[15:58] <JontheEchidna> oh, that's actually a source-diff, not a debdiff
[15:58] <Riddell> JontheEchidna: although this is universe so it shouldn't need any ack
[15:58] <Riddell> universe is only in feature freeze, bug fixing is all good
[15:59] <JontheEchidna> oh, the freeze email said that universe should get motu-release or your ack
[16:00] <JontheEchidna> well, your ack for KDE packages
[16:00] <Riddell> JontheEchidna: which e-mail?  scotts?
[16:00] <JontheEchidna> Riddell: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-October/000633.html
[16:01] <Riddell> sistpoty's does suggest an ack is needed for all uplaods but I trust ScottK more in https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-October/000634.html that only FFe needs an ack
[16:03] <JontheEchidna> kk
[16:05] <freeflying> anyone can tell me why I leave kubuntu-bugs team, but still got bug notifications? I just prefer to use gmane to read bug mails
[16:06] <freeflying> s/leave/left
[16:06] <JontheEchidna> subscriptions are separate from team affiliations
[16:07] <tsimpson> https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[16:35] <ScottK> JontheEchidna and Riddell: Does the mail to u-d-a clear this up?
[16:35] <ScottK> After Universe final freeze, a motu-release ack will be needed, but we aren't there yet.
[16:35] <Riddell> I'm clear, it's just sistpoty's older e-mail which was wrong/unclear
[16:36] <ScottK> OK.
[16:40] <Riddell> new kopete-facebook http://duncan.mac-vicar.com/blog/archives/597
[16:40] <Riddell> wish that had come out a week ago
[16:41] <ScottK> It sounds though like it still has enough open questions that we did the right thing.
[16:44] <Riddell> yes I think so
[17:00] <dany_21a> is this a known bug: the alternative installer stops after "installing base system" and requests to insert medium "Kubuntu 9.10 _Karmic Koala_ - Beta i386 (20090929.3)" into /cdrom/ - which sould be there... but refuses to continue
[17:00] <ScottK> davmor2: ^^^ ?
[17:01] <dany_21a> is this checked against README.diskdefines on the root of the cdrom... because this states: #define DISKNAME  Kubuntu 9.10 "Karmic Koala" - Beta i386
[17:01] <davmor2> dany_21a: man that's old
[17:01] <dany_21a> uh?
[17:02] <dany_21a> is it fixable for me?
[17:02] <davmor2> I think it was a general issue that got resolved in latter iso's.
[17:02] <dany_21a> hm... ive downloaded the most recent beta torrent (i hope so)
[17:03] <davmor2> oh hang on on beta there were no issues with the iso's sorry
[17:03] <davmor2> dany_21a: have you run the cd checker to makes sure the burn is good?
[17:04] <dany_21a> checking the md5... md5 of the iso is correct
[17:04] <dany_21a> will check the medium
[17:06] <asraniel> final freeze in effect, does that mean that i can install a daily CD now and i have +- the final version?
[17:06] <tsimpson> not really, it's not final until it's final
[17:10] <dany_21a> davmor2: checker said CD is okay
[17:48] <davmor2> meh pass then I'm afraid.  No issues here with beta at all.
[17:52] <fabo> Riddell: Qt 4.5.3 fixed in -4
[18:01] <ScottK> It looks like we need a newer python-qt3 to go with the new sip.
[18:56] <Riddell> fabo: what needed changing?
[18:58] <lex79>  lp bug 449862
[18:58] <fabo> Riddell: add patch 08
[18:58] <lex79> Riddell: ^^ fixed in bzr
[19:00] <fabo> Riddell: http://git.debian.org/?p=pkg-kde/qt4-x11.git;a=commitdiff;h=2f8c91155f7061185c5bd01c53f41695d54d8778
[19:01] <Riddell> fabo: have I ever said you're a genius?
[19:01] <Riddell> so, question is do we want to risk uploading it now
[19:02] <fabo> Riddell: you risk nothing. it's already built on kfreebsd ;)
[19:02] <Riddell> ScottK: what's wrong with python-qt3?
[19:03] <Riddell> I need to stop running hardy, it's difficult to do much useful from here, time to burn a daily CD
[19:04] <fabo> I'll probably upload Qt 4.6.0 beta 1 to experimental today
[19:21] <ScottK> Riddell: I saw a bug about it, but it may be from before it was updated. Let me ifnd it.
[19:35] <jjesse> so i went to download the current live cd from cdimages and it was screamin' at 300k/sec up until the last 100mb of the cd now i'm at 3Kb/sec, any thoughts?
[19:36] <ScottK> Patience
[19:38] <jjesse> ha
[19:41] <ScottK> Wasn't actually kidding
[19:41] <jjesse> i know just was curious why it dropped so slow
[19:42] <ScottK> #canonical-sysadmin if you want to talk to someone that might actually know.  The odds of gettting an answer are low.
[20:12]  * JontheEchidna is responsible for 12% of the current archive admin queue \o/
[20:21] <dany_21a> is it possible to setup a LVM system via the graphical installer (kubuntu karmic) - the alternate version fails for me
[20:23] <dany_21a> i have already managed to reuse my old lvm-schema and activate the lvm disks, so that the installer completes... but when i start the fresh installed system, it fails to boot and says it cant find my lvm partitions
[20:24] <dany_21a> the initram disk need lvm support... i tried to chroot into the new system and install lvm2 (via apt-get) - which runs update-initramfs and completes without failure... but on reboot it fails again and drops me to an shell
[20:24] <dany_21a> (chroot from an live boot cd-rom)
[20:31] <dany_21a> ah... nevermind - i forgot to mount /boot into my chroot... - it boots now
[20:53] <debfx> Riddell: Caching the brightness value in order to make the fn keys working isn't easily possible, as changing the brightness isn't handled by powerdevil but by libsolid
[20:55] <debfx> Riddell: either libsolid has to notify powerdevil or all setBrightness calls have to go through powerdevil
[20:56] <Riddell> debfx: I suspect they all do go through powerdevil, although that's not a sensible assumption
[20:56] <debfx> Riddell: no, currently powerdevil doesn't have such a function
[20:57] <Riddell> sounds like a patch to libsolid is needed though
[20:58] <ScottK> Riddell: Since wednesday I've had a problem where my laptop lid open's are not recognized by KDE, resume from suspend works, so I know it isn't hardware.  pitti has the same laptop and his works.  Suggestions on where I should look?
[20:58] <debfx> I could add a dbus method to powerdevil and make libsolid call it on every brightness change
[20:59] <ScottK> debfx: What is it you are trying to fix?
[20:59] <debfx> ScottK: making the fn brightness keys work if they aren't handled by the hardware
[21:00] <ScottK> I see, so since mine work now, it's done in hardware?
[21:00] <Riddell> ScottK: karmic-changes for wednesday?  we've had changes to kdebase-workspace which works in that area
[21:00] <ScottK> Riddell: OK.  Which binary is powerdevil in?
[21:01] <ScottK> I already tried downgrading the kernel and acpi-support with no help
[21:01] <debfx> ScottK: probably, if you don't have another power manager installed
[21:01] <ScottK> I don't
[21:04] <Riddell> Sime: ping ping
[21:04] <Sime> Riddell: pong pong
[21:04] <Riddell> Sime: we what a crash in sip that appeared in 4.9, would you have any thoughts on bug 451915 ?
[21:04] <Riddell> s/what/have/
[21:06] <debfx> am I the only one whose fn keys aren't handley on the hardware side? :(
[21:07] <Sime> Riddell: are you sure your test core generates the same error?
[21:08] <Riddell> Sime: pretty sure yes
[21:13] <Sime> Riddell: it doesn't crash on jaunty
[21:14] <Riddell> Sime: no it's an issue with the sip 4.9/pyqt 4.6 update
[21:14] <Sime> Riddell: I've got a hand compiled sip 4.9 / pyqt 4.6, and doesn't crash.
[21:15] <Riddell> fooey
[21:17] <Sime> yep, just checked the version numbers in the modules. it sip 4.9 and 4.6.
[21:18] <Sime> dvd time with wife...
[21:18] <Riddell> thanks i'll keep player
[21:18] <Riddell> playing
[21:20] <Sime> I might be using a week old snapshot BTW. dunno exactly..
[21:21] <Riddell> well it could be something in our packaging bringing out the bug
[21:25] <lex79> I have no crash if I run "python sip-segfault.py"
[21:26] <Riddell> lex79: what about printer-applet?
[21:26] <lex79> how to test?
[21:26] <Riddell> lex79: run "printer-applet"
[21:29] <lex79> weird, I don't see anything..the applet doesn' appear and I haven't crash
[21:29] <Riddell> that means it's running in the background
[21:29] <Riddell> which it will until you print something
[21:30] <Riddell> lex79: what version of python-qt4 do you have?
[21:30] <lex79> 4.6-1
[21:30] <ScottK> That's no help
[21:30] <ScottK> Oh, wait, nevermnd
[21:31] <Riddell> lex79: and python-sip4 ?
[21:31] <debfx> so what do you think of a notifyOfBrightnessChange() dbus method in powerdevil that would called by solid?
[21:31] <lex79> Riddell: 4.9-1
[21:32] <Riddell> debfx: that makes sense to me
[21:32] <lex79> now I launched a print and TWO printer applet appears in systray
[21:32] <lex79> and print works
[21:34] <Riddell> lex79: well that's annoying, the least the bug could do is have the decency to crash for everyone
[21:35] <Riddell> lex79: did you say our qt4 bzr packaging has fabo's fix in it?
[21:36] <lex79> this fabo's patch fix qt4 http://git.debian.org/?p=pkg-kde/qt4-x11.git;a=commit;h=2f8c91155f7061185c5bd01c53f41695d54d8778
[21:36] <lex79> I can push in bzr if you want
[21:37] <Riddell> lex79: oh it was bug 449862 that was fixed in bzr ?
[21:37] <lex79> Riddell: yes
[21:37] <Riddell> the conversations got confused
[21:38] <lex79> I uploaded in bzr the fix for ktimetracker
[21:38] <Riddell> lex79: I'll upload the ktimetracker fix if you push fabo's patch to bzr then :)
[21:38] <lex79> Riddell: ok
[21:40] <lex79> btw, in my system there isn't crash with printer-applet, and the printer print...but printer-applet doesn't appear in systray
[21:40] <lex79> that is all
[21:41] <Riddell> lex79: you just said "TWO printer applet appears in systray"
[21:43] <lex79> Riddell: because I launched printer-applet in konsole, and after  I launched a print
[21:52] <Riddell> seele: facebook ping
[21:53] <seele> Riddell: you went away!
[21:53] <seele> you didnt even give me a chance to respond!
[21:54] <Riddell> seele: hmm, I'm not convinced this new kopete-facebook works
[21:56] <seele> it shows you offline
[21:56] <seele> try again?
[22:00] <Riddell> trynow
[22:01] <seele> still not working
[22:01] <seele> i get your message but when i send one it says youre offline
[22:01] <Riddell> mm, one sided conversations have limited use
[22:01] <Riddell> shame
[22:02] <Riddell> I'll upload it anyway, can't be any worse than the current and it's in universe
[22:17] <ScottK> Riddell: kopete-facebook accepted
[22:18] <Riddell> ScottK: thanks
[22:18] <Riddell> ScottK: python-qt3 seems to work for me
[22:18] <ScottK> Riddell: OK, it was probably a transient after the sip upload
[22:18] <JontheEchidna> Have we decided on what to do about python-kde3 yet?
[22:19] <ScottK> It's already removed, isn't it?
[22:19] <JontheEchidna> oh, I guess so
[22:20] <Riddell> yes I killed it
[22:20] <ScottK> \o/
[22:20] <JontheEchidna> one less kde3 rdepend
[22:20] <JontheEchidna> Found a total of 196 reverse build-depend(s) for kdelibs4-dev.
[22:21] <JontheEchidna> oh, universe only
[22:21] <JontheEchidna> only 6 more elsewhere though
[22:23] <JontheEchidna> I have a few more kde3 and general kde cruft removals if any archive admins feel bored (ha ha)
[22:23] <JontheEchidna> https://bugs.launchpad.net/~echidnaman/+reportedbugs?field.searchtext=request+for+removal
[22:25] <lex79> version of qt4 4.5.3 should be 4.5.3-0ubuntu1 ?  in archive it's 4.5.3really4.5.2-0ubuntu1
[22:26] <JontheEchidna> 4.5.3-0ubuntu is lower than 4.5.3really4.5.2
[22:26] <Riddell> lex79: needs to be 4.5.3really4.5.3-0ubuntu1
[22:26] <lex79> ok thanks
[22:27] <Riddell> and if this gets uploaded and fails then we're into horribly stupid version numbers
[22:27] <JontheEchidna> 4.5.3really4.5.2noreally4.5.3-0ubuntu1
[22:27] <JontheEchidna> :D
[22:27] <lex79> LoL
[22:27] <Riddell> lex79: I just synced the changelog in qt bzr
[22:27] <lex79> great
[22:58] <lex79> I upload to bzr qt4
[22:59] <lex79> *uploaded
[23:01] <lex79> the fabo's configure in rules is a bit different from ours, if will be ftbs again we know where we can look
[23:19] <apachelogger> JontheEchidna: for reference bug 452883 might very well caused by us, I removed the uglyish default_blue or whatever it is called wallpaper at all levels which might eventually cause the selection to be broken
[23:19] <apachelogger> which would be weird but technically possible given the weirdness of all kdm related stuff
[23:19] <JontheEchidna> then it'd be debian, not us :P
[23:19] <apachelogger> nah
[23:19] <apachelogger> I removed it
[23:19] <apachelogger> me
[23:19] <JontheEchidna> oh, right
[23:20] <apachelogger> because it was showing up in the plasma wallpaper selection dialog as well
[23:20] <apachelogger> which was quite the PITA
[23:21] <apachelogger> so Id also like to add... if this is caused by our change to the kdm defaults, then I freaking give a crap whether wallpaper setting is working because it is a minor use case that is only meant to make kdm look ugly and I rather have no default_blue wallpaper than a working wallpaper selection
[23:21] <lex79> have you seen this: http://websvn.kde.org/?revision=1034475&view=revision
[23:21] <lex79> ?
[23:21] <lex79> http://bugs.kde.org/show_bug.cgi?id=202799
[23:22] <JontheEchidna> that just fixes the preview widget itself
[23:22] <JontheEchidna> a user-set wallpaper still wont' work in KDM
[23:23] <apachelogger> well, just set the wally manually in the kdmrc and see how the kcm behaves then
[23:23] <apachelogger> if it starts working then my enhancement to the kdm defaults is causing the issue
[23:23] <apachelogger> which might be worked around by setting the default wally to air
[23:24]  * apachelogger goes to bed though
[23:24] <apachelogger> nini
[23:26] <JontheEchidna> hmm... does backgroundrc look for an explicit filename?
[23:26] <JontheEchidna> the kcm isn't writing anything to backgroundrc
[23:26] <JontheEchidna> prob. the bug right there
[23:31] <JontheEchidna> setting it manually works. The bug is that the kcm isn't writing to the background config file
[23:31] <JontheEchidna> themed mode doesn't use backgroundrc, so it's unaffected
[23:36] <debfx> Riddell: I have an experimental patch: http://paste.ubuntu.com/295015/
[23:37] <debfx> it works for me but I can't test if it causes trouble on laptops with hardware based brightness fn keys
[23:47] <Riddell> debfx: looks sensible at a glace but the change to updateSlider breaks API
[23:51] <Riddell> testers needed for k3b! http://kubuntu.org/~jriddell/tmp/k3b/
[23:52] <JontheEchidna> whoa, new alpha?
[23:52] <debfx> Riddell: updateSlider() is a private slot, does changing it cause an issue?
[23:53]  * JontheEchidna would be worried if a battery applet was an exported library
[23:55] <JontheEchidna> I don't think that'd cause any issues, imo
[23:57] <Riddell> debfx: I'd hope not, although c++ binary compatibility rules are so random I couldn't say for sure
[23:57] <Riddell> but right, that's not in the library, my mistake, should be fine then
[23:58] <Riddell> debfx: I'd recommend throwing a packaging into your PPA, I presume you know how?