[01:53] <jjesse> hrmm after updating my karmic vm i can't use the mouse or keyboard
[03:47] <seele> ScottK: there really isnt a better way of getting the attention of the user than a popup dialog
[03:47] <seele> ScottK: an "oh shit your computer is going to shut down NOW" message seems appropriate in that case
[03:47] <seele> and keep in mind that is completely different from a low battery "warning"
[03:48] <seele> which just says politely "btw, your battery is low.. you should do something like plug it in or shut it down"
[03:50] <ScottK> seele: I'd like to see you contribute to the upstream discussion then.
[03:51] <seele> ScottK: what mailing list was it on because i completely missed it
[03:51] <seele> i basically archived everything from last week because i couldnt keep up with it while on holiday
[03:51] <ScottK> seele: kde-core-devel
[03:51] <seele> who were the primary participants?
[03:52] <seele> actually, what was the subject so i can find it
[03:52] <ScottK> seele: The thread starts here:  http://lists.kde.org/?l=kde-core-devel&m=125362617220332&w=2
[03:52] <seele> ok
[03:52] <ScottK> It seemed primarily asiego and sebas from the people I know being strongly against.
[03:52] <seele> holy shit 68 responses
[03:53] <seele> well i dont have teh patience to argue with aseigo
[03:53] <ScottK> seele: I see your point, but I don't want to be stuck with a patch that we are going to have to maintain forever.
[03:53] <seele> ill say my bit and see what happens i guess
[03:53] <ScottK> The short version is dialogues come from applications, the system should use notifications.
[03:53] <ScottK> If the notification needs to be spiffied up to make it more obvious, fine.
[03:54] <ScottK> They were very against the idea of a dialogue appearing 'out of nowhere'.
[03:55] <seele> out of nowhere? the computer is going to shut down on it's own! i'd say that's a pretty responsible thing to do
[03:55] <ScottK> The computer is going to suspend, not shut down
[03:56] <seele> well. still. stuff will go away and you can't work anymore
[03:56] <seele> the computer is going to act on it's own in a major way
[03:56] <ScottK> That was another point of the discussion that if suspend is broken, fix suspend, don't work around the fact that it's broken.
[03:56] <ScottK> Thus willingness to have the notification be more obvious.
[03:57] <seele> i thought a high percent of hardware now works with suspend
[03:57] <ScottK> Although no one could find an example of someone not noticing the existing notification.
[03:57] <seele> and it is still going to suspend isnt it? regardless of what type of visual notification we make?
[03:57] <seele> i dont see how that would be relevant to that conversation
[03:57] <ScottK> Unless you cancel it.
[03:57] <seele> right, and in that case, having a popup dialot which provides you a way to cancel it seems more reasonable for cases where suspend might not work
[03:58] <seele> instead of it quietly counting to itself in the corner and then BOOM
[03:58] <ScottK> The only actual problems people reported were the timeout being too short and the button to hit to cancel being too small.
[03:58] <seele> that seems pretty easy to fix
[03:58] <ScottK> Yes
[03:58] <seele> argh
[03:58] <ScottK> So the conclusion on the list was that the actual problems were quite fixable without switching to a dialogue
[03:59] <seele> the problems have nothing to do with it
[03:59] <ScottK> The only actual reason to switch to a dialogue was if you think actions on notifications are evil.
[03:59] <seele> that also has nothing to do with it
[03:59] <seele> argh
[03:59] <ScottK> It has everything to do with it.
[03:59] <seele> no, it doesnt matter if there are actions on the notification because the information shouldnt be delivered in a notification
[03:59] <ScottK> This is the one OMG I must have an action case the agateau found in his review of KDE actions.
[04:00] <seele> a notification, actions or not, is too passive for that type of proactive action from the computer
[04:00] <seele> that is why a dialog is perfectly suited for that type of feedback
[04:00] <ScottK> Well review the thread then and reply.
[04:00] <seele> ok
[04:00] <ScottK> Just trying to give you the sense of it.
[04:01] <ScottK> Personally, I think the timeout should be longer and the action area ought to be bigger.  I don't see it makes a lot of difference between dialogue and notification.  What I really don't want is to be stuck with patch maintenance forever due to permanent upstream divergence.
[04:03] <ScottK> IME the notification is plenty noticable.
[04:19] <seele> it has to be more than noticable
[04:19] <seele> it can't be missed
[04:19] <seele> and notifications can be missed
[04:20] <seele> telling the user that the computer is going to go to sleep right now is not something that should be missed
[04:20] <seele> argh
[04:20] <seele> only through the first 5 emails
[04:28] <ScottK> Right, but no examples of it being missed were  provided.
[04:30] <rgreening> maybe we should file bugs against kde then submit patches for review against the bugs (assuming we havent already opened kde bugs)
[04:30] <ScottK> rgreening: For what?
[04:31] <rgreening> well if the powerdevil notification is in question, file a bug/wishlist against it upstream I guess
[04:31] <rgreening> then once filed it's easier to work with maybe
[04:32] <rgreening> of course I seem to be batting zero on suggestions this week...
[04:32] <ScottK> Did you miss the "hey I'm about to suspend" notification?
[04:32] <seele> ScottK: if someone gives me 5k then i can find out, but that seems like a waste of money for such a minor feature
[04:32] <rgreening> heh
[04:32] <seele> actually, might need 10k, it would have to be statistically significant
[04:33] <ScottK> seele: Right, well I don't care which one we use nearly as much as I care about not being stuck with a patch forever.
[04:34] <ScottK> "Ayatana will maintain it" doesn't much comfort me.
[04:41] <nixternal> i took a nap from 5pm until 9:30pm...I am ready for work!
[05:26] <ScottK> Riddell and ryanakca: I went ahead and announced the move of KDE 4.2.4 to jaunty-backports on kubuntu.org since we got bitched at for not doing so before.  Feel free to improve it.
[05:37] <ScottK> Crap.  Just upgraded my laptop to karmic and black screen after login (just the mouse).
[05:38] <ScottK> Suggestions welcome.
[05:47] <user321> http://tinyurl.com/yatepls
[05:49] <ScottK> Riddell: I'm going to bed, but any suggestions for black screen after login on upgrade from Jaunty are quite welcome.
[05:51] <jussi01> ScottK: I had a problem with settings after upgrade, moved .kde and all was fine
[05:52] <ScottK> jussi01: Thanks.  I'll try that after the "you've rebooted too many times" fsck gets done.
[05:52] <jussi01> hrm, Ive been running karmic for a while on this lappy, and sound has been a constant issue. It works ok, except for when a sound needs to be played, I get a "tick" sound (like a mike being plugged in?) and the mute light flashes. it then goes on to play the sound - however, if the sound is too short like a skype login or so, you get just the tick and mute flash
[05:53] <jussi01> any suggestions?
[05:59] <ScottK> jussi01: No luck with moving .kde.  Thanks for the suggestion.
[05:59] <jussi01> ScottK: hrm, curious.
[08:10] <jussi01> ok, I reported the phonon bug I mentioned before: bug 438556 maybe one for dtchen ?
[09:44] <ach> ScottK: about bug 432521
[09:46] <ach> ScottK: I agree with our comment in #4.    Bug in #3 is more important.   For whatever reason it looks like I can't change subject/desc too. I assume the reason is I'm too stupid to find the right button :(
[10:02] <Tonio_> Riddell: I have patched kdebluetooth as requested...
[10:02] <Tonio_> may I upload directly and you review as an archive admin ;)
[10:20] <neversfelde> mhh, kdepim is untranslated after upgrade of some language packs :/
[10:30] <markey> is there a way to disable apport completely?
[10:31] <markey> I've disabled it once, but it still tries to open
[11:06] <sebas> markey: there's an init script afaik
[11:06] <sebas> Not sure if that will disable apport, but it might break it enough so you don't see it
[11:35] <ScottK> ach: It's a but that the current LP doesn't work with Konqueror for changing bug descriptions.
[11:39] <ScottK> Riddell: My laptop is still dead after upgrade, so hints are welcome.
[11:43] <Riddell> ScottK: what's in .dmrc ?
[11:43] <Riddell> does startx work?
[11:43] <ScottK> Looking
[11:44] <Riddell> can you use a fallback session to get a terminal and start kde bits one by one to see what's not starting
[11:44] <Riddell> what's in .xsession-errors?
[11:44] <ScottK> Gotta boot it first
[11:46] <ScottK> .dmrc has [Desktop]
[11:46] <ScottK> Session=default
[11:49] <ScottK> Riddell: The only error in .xsession-errors is "/usr/bin/xmodmap: unable to open file '/usr/share/kubuntu-default-settings/kubuntu.xmodmap' for reading
[11:50] <ScottK> Then "/usr/bin/xmodmap: 1 error encountered, aborting."
[11:51] <ScottK> The rest is mostly stuff like "kdeinit4: preparing to launch /usr/lib/libkdeinit4_kconf_update.so
[11:52] <ScottK> Trying startx now
[11:53] <ScottK> Riddell: startx doesn't even get to the login screen.  It switches to a black screen with just a mouse.
[11:57] <ScottK> I can confirm that kubuntu.xmodmap is not there in k-d-s.
[12:01] <Nightrose> Riddell: hey :) Harald said you can add me to a google doc i might be interested in
[12:01] <Nightrose> or JontheEchidna
[12:08] <ScottK> Riddell: Fixed.  Somehow I had openbox installed on the box too.  Purging that fixed it.
[12:09] <Riddell> well that's just asking for trouble :)
[12:09] <Riddell> Nightrose: umm, did he give any clue as to which?
[12:10] <Nightrose> Riddell: future plans afaik
[12:10] <Riddell> maybe you'd like to join our monthly wholesale food order and buy a pallet of sweetcorn?
[12:10] <Nightrose> *lol*
[12:10] <Riddell> hmm, don't see any google doc about that
[12:10] <Nightrose> sure
[12:10] <Nightrose> ok
[12:11] <Nightrose> will have to wait until he is back at a proper computer then
[12:32] <ScottK> Riddell: All is not happy.  If I boot via the recovery session and manually sudo kdm start, it works.  Normal boot, I don't even get to the login screen.  Suggestions?
[12:34] <ScottK> I did move my .kde away and no help.
[12:59] <ach> ScottK: I did dist-upgrade and reboot and kdm starts file.  Try:   initclt list |grep kdm    Maybe kdm is  not started because of upstart thinks dependecies are missing?
[13:02] <rgreening> Riddell: is there a place we can start collecting ideas/todos for Lucid? Or do you have any suggestions? I have some ideas I'd like to start writing down and not forget them...
[13:02] <rgreening> or prefererence...
[13:04] <rgreening> Riddell: how about https://wiki.kubuntu.org/KubuntuLucidSpecs (like we did for Jaunty)
[13:07] <ScottK> ach: Thanks.
[13:07] <ach> uh, and now is wireless doesn't work anymore.  knetworkmanger does not react when I click in the wpa2 wlan
[13:08] <ScottK> ach: It says kdm stop/waiting.  Is that normal?
[13:08] <ScottK> No, it's not
[13:08] <ScottK> Good clue.
[13:09] <ScottK> Riddell: ^^^ Any suggestions?
[13:10] <ScottK> rgreening: Fix my laptop before you start worrying about the next release.
[13:11] <ach> ScottK: check you've ubuntu14 rev of kdm.  There was a fix to now conflict/Breaks with new usplash
[13:13] <ScottK> Looks like maybe i have 13
[13:13] <ScottK> agateau: How do I tell quassel to use the indicator?
[13:14] <agateau> ScottK: there should be an option somewhere
[13:14]  * agateau starts Karmic Quassel
[13:14] <ScottK> agateau: I didn't find it.
[13:15] <ach> konversation patched too for new indicator?
[13:15] <agateau> ach: yes
[13:15] <ScottK> Yes.
[13:15] <agateau> it's in Interface / Notifications
[13:15] <agateau> there is an ugly check box in the bottom
[13:15] <agateau> (shame on me)
[13:16] <Tonio_> ScottK: can you approve and let uploads to main go in ?
[13:16] <Tonio_> ScottK: I have a patched kdebluetooth waiting
[13:16] <ScottK> Tonio_: No.  That needs ubuntu-release approval.  Unless it's beta critical, it needs to wait
[13:17] <Tonio_> ScottK: kk
[13:17] <Tonio_> critical I'(d say no, but we'll receive compains about that :)
[13:17] <Sput> ScottK / agateau: actually, with KDE integration, there should be a checkbox in KDE's "Configure Notifications"
[13:17] <Tonio_> ScottK: any idea what's the status of boot splash ?
[13:18] <Sput> ah right, no, it's only in Interface /Notifications
[13:18]  * Sput confuzzled
[13:18] <ScottK> Which I don't see it.
[13:18] <ScottK> Tonio_: No.
[13:18] <Sput> it's *not* in "Configure Notifications"
[13:19] <ScottK> I don't see it at all.
[13:20] <Sput> hmmm, I can't test :)
[13:20] <neversfelde> I cannot see it either
[13:20] <Sput> sure it's built with ayatana support (check the configure messages)?
[13:21] <ScottK> agateau: Can you look into this?  I need to get my laptop fixed and get to $WORK.
[13:21] <agateau> It's here for me, did you look at Quassel configure dialog or at the generic "Configure notification" dialog
[13:21] <agateau> ?
[13:21] <agateau> ScottK: ^
[13:22] <ScottK> agateau: Both
[13:22] <rgreening> agateau: I dont see it here either. What version of quassel and are you running a local build or from the main archive
[13:22] <neversfelde> both here :)
[13:22] <agateau> rgreening: local build, need to distupgrade
[13:23]  * agateau tries installed package
[13:23] <agateau> ooooh
[13:23]  * rgreening think the patch isnt in
[13:23] <ScottK> ach: You called it.  I updated and it worked.
[13:23] <agateau> when built with KDE support, the page where I added my checkbox is not here
[13:24] <ScottK> Riddell: Looks like my upgrade problem was solved by the current kdm.  I guess I upgraded slightly too soon.
[13:24] <ScottK> So I can confirm that last upload was really needed.
[13:25] <rgreening> #IFDEF agateau #define PATCH=0 #ENDIF
[13:25]  * agateau adds an entry to his TODO list
[13:25] <ach> ScottK: good, but still same on logout: no greeter.  I can see kdm_greeter is started + 2 dbus instances but no login prompt.  So maybe dbus is blocking for whatever reason?
[13:25] <ScottK> There's an open bug on that.
[13:26] <ach> ScottK: yes, I filed this bug ;)
[13:27] <ScottK> I think Riddell had some ideas about it, but I'm not sure what.
[13:27] <rgreening> Riddell: I started this page for ... so we can keep track of ideas for upcoming UDS... https://wiki.kubuntu.org/KubuntuLucidSpecs
[13:27] <ScottK> It's on the list of stuff that we know has to get fixed before release.
[13:27] <ScottK> rgreening: Start with "Make translations no suck"
[13:28] <Sput> agateau: hmmm, from my cursory glance on the code it should be there, but maybe we do something fancy with KDE's native dialog :)
[13:28] <rgreening> ScottK: I thought that was addressed for Karmic
[13:28] <ScottK> rgreening: Only progress.  We don't appear to be all the way to "Not suck".
[13:28] <rgreening> ok
[13:28]  * rgreening adds translations to spec list to write
[13:28] <agateau> Sput: ok
[13:28] <ach> ScottK: good that Riddell has some ideas, I run out of them.  So I spend my time why I no longer can connect anymore to the wpa2 wireless here.
[13:29] <ScottK> ach: OK.  I'm connected to wpa2 right now.
[14:04] <Riddell> ach: try killall knetworkmanager; rm ~/.kde/share/config/network*; knetworkmanager
[14:04] <Riddell> rgreening: good idea
[15:03] <ScottK> Is KDE 4.3.2 scheduled?
[15:04] <JontheEchidna> It's due to be tagged October 1st
[15:04] <JontheEchidna> and released the 6th
[15:04] <JontheEchidna> leaving 9 days before final freeze
[15:05] <ScottK> No problem.
[15:07] <ScottK> Where do I find the option to turn the "Ayatana" notifications on?
[15:10] <JontheEchidna> ScottK: inside the system tray settings dialog
[15:11] <ScottK> That seems obscure.
[15:11] <ScottK> Thanks.
[15:15] <JontheEchidna> You're welcome.
[15:18] <txwikinger_work> Anybody an idea what the problem could be that cut&paste on kde apps doesn't work anymore, but on the other one it still does?
[15:19] <ScottK> agateau: It seems with your notifications enabled visual notifications get queued up, but audible ones don't so they get out of sync.
[15:20] <agateau> ScottK: wow
[15:20] <agateau> not sure i can do something for this
[15:20] <agateau> :/
[15:20] <ScottK> It does seem a bit odd since they don't relate.
[15:20] <ScottK> One is wondering what the ping was for.
[15:21] <agateau> I can see how it is a problem,
[15:22] <agateau> but right now a notification goes this way: app -> knotify,
[15:22] <agateau> if it's a sound knotify plays it
[15:22] <agateau> if it's a bubble it sends it to plasma
[15:22] <agateau> since my code is in plasma,
[15:22] <seele_> maco: ping
[15:23] <agateau> I do not have access to the sound part
[15:23] <ScottK> So this is a good piece of architectural feedback for KDE when they implement something to stop flooding
[15:23] <agateau> indeed
[15:24] <txwikinger_work> Isn't the Desktop experience team involved with such things?
[15:24] <ScottK> txwikinger_work: Who does agateau work for?
[15:24] <txwikinger_work> :D
[15:24] <agateau> quizz time!
[15:24] <ScottK> I think there is at most a zero percent chance of Ayatana notifications getting adopted by KDE as long as they are actionless, but there are still points of useful feedback that can and should be given to KDE.
[15:26] <maco> seele_: pong
[15:31] <ScottK> JontheEchidna: Is it on purpose that Konversation's systray icon is absent?
[15:32] <Riddell> that's the upstream default setting
[15:32] <ScottK> OK
[15:33] <ScottK> Last I used it, I remebered it being there.
[15:33] <ScottK> Thanks
[15:34] <Riddell> anyone tried encrypted home directory in karmic?
[15:37] <ScottK> I'll try it on my netbook if I get time to do a reinstall for beta testing.
[15:41]  * rgreening is expecting 2xmini10v oct12th
[15:44] <neversfelde> Riddell: I am currently installin kne with that option
[15:45] <Riddell> neversfelde: it crashed for me when using it with OEM install so let me know what happens
[15:51] <JontheEchidna> agateau: I think bug 437999 is another indicator crasher (this is with your fix from the other day)
[15:52] <agateau> JontheEchidna: oh
[15:52]  * agateau looks
[15:52] <JontheEchidna> thanks :)
[15:59] <neversfelde> Riddell: no problem here. I can install OEm in a vm, if that is needed (and it works in karmic)?
[15:59] <Riddell> it works otherwise
[16:05]  * hunger just reported a bug about powerdevil not being able to set backlight brightness.
[16:06] <hunger> It should work according to the kde bugtracker... so maybe it is something in the xorg or kernel layer instead of kdebase.
[16:06] <Riddell> mm that could be anywhere between linux, udev, hal, X, solid and powerdevil
[16:08] <ScottK> More love for the powerdevil patch: http://blog.martin-graesslin.com/blog/2009/09/why-distributions-shouldnt-ship-development-versions/
[16:09] <hunger> Riddell: I know:-) My hope was that someone had an idea on how to debug this.
[16:09] <Riddell> mm, that's painful, I wrote a response in a comment but he hasn't approved it
[16:09] <hunger> xbacklight does not work either, so it probably is not kdebase per se.
[16:13] <neversfelde> the translation on this system is in chaos, anyone ese having problems with this?
[16:13] <neversfelde> seems to happen after upgrading with the last language packs
[16:14] <Riddell> translations were mostly ok when I tested yesterday
[16:14] <Riddell> I'll test it when I do the alternate CDs
[16:14] <yuriy> if translations are severely broken in beta, we're gonna get a lot of crap
[16:15] <neversfelde> I'll try it on my netbook
[16:16] <davmor2> Riddell: just syncing the kub cd's now
[16:32] <hunger> How should a display backlight show up in HAL?
[16:32]  * hunger can not find anything containing back in hal-device output (except for network related stuff).
[16:32] <Riddell> I have.. udi = '/org/freedesktop/Hal/devices/computer_backlight' info.addons = {'hald-addon-generic-backlight'} (string list)
[16:34] <hunger> Nothing like that here... so it is hal or below.
[16:35] <ScottK> Riddell: I don't think comments are moderated on that blog.  Mine appeared immediately.
[16:40] <ScottK> Did the final IRC decision get made yet?
[16:41] <ScottK> I think we'll need to stick with Quassel on netbook as the Konversation config dialogue doesn't fit on 576 tall display
[16:41] <hunger> Ah, looks like I need a special kernel module for this:-/
[16:45] <seele_> ScottK: re martin's blog, with the way he wrote it he makes it sound like kubuntu ships that way, not that you are preparing a seperate installation for it
[16:45] <seele_> people can install regular kubuntu if they want
[16:46] <ScottK> seele_: True.  We had a decent dialgoue in the comments
[16:46] <ScottK> seele_: I think he's totally right on powerdevil though.
[16:52] <ScottK> agateau: Did you not implement the longer notification for longer text?  seele_'s message ^^^ was on a notification for me and I coulnd't read it all before it went away.
[16:53] <agateau> ScottK: I did, but maybe the algorithm needs some adjustment
[16:53] <ScottK> agateau: It didn't seem to last any longer than normal.
[16:54] <agateau> ScottK: could be a bug (I tend to produce those from time to time) :)
[16:54]  * agateau checks it's actually implemented
[16:57] <agateau> ScottK: oups, it's not
[16:57] <agateau> adding to my TODO
[16:57] <ScottK> OK
[16:58] <ScottK> agateau: Whatever opinions I have about notify-osd they will be based on having used it and not just theory.
[16:58]  * agateau likes this
[16:59] <ScottK> Please figure out getting the indicator stuff turned on in Quassel so I can try that too.
[17:00] <agateau> it's in my TODO, but I am busy with Kontact not starting at the moment,
[17:00] <agateau> which sounds a bit more critical :)
[17:00] <ScottK> That'd be a higher priority, yes.
[17:04]  * ach is working mode ignores lower right corner completely and is a fan of dialog in center of screen (helped on e.g. on mac os x several times already.)
[17:07] <Riddell> neversfelde: translations seem good for me installing from a CD, are you sure you have all the langpacks installed? what language are you looking at?
[17:07] <neversfelde> Riddell: german and everything is ok on my netbook
[17:07] <neversfelde> seems to be a problem with this machine
[17:20] <agateau> Riddell: JontheEchidna: uploaded a new patchset for kmail to fix  437999
[17:20] <agateau> http://people.canonical.com/~agateau/indicate/kmail-4.3.1-20090929.tar.bz2
[17:20] <agateau> have to go
[17:22] <ScottK> ach: Needs to be solved upstream (the powerdevel thing).
[17:38] <Guest50779> hello i am having keyboard problems in KDE, in  gnome it works, only in kde i can type nothing. even the virtual keyboard does not work
[17:42] <nixternal> Riddell: desktop meeting and your name was mentioned
[17:42] <rickspencer3> Riddell, desktop team meeting?
[17:46] <seele_> rickspencer3: are you still looking to move back to DC?
[17:46] <rickspencer3> seele, in team meeting atm, but not really, why?
[17:47] <seele_> rickspencer3: just wondering, you mentioned it a while ago
[17:47] <rickspencer3> seele, we did some serious house hunting, but then decided that moving is a pita, and we decided to wait for a sign
[17:50] <seele_> rickspencer3: oh well. maybe you'll get one some day :)
[17:50] <Daskreech> apachelogger: Which planet?
[17:50] <apachelogger> all o'em
[17:51] <Daskreech> Oooh there is akubuntu drama on planet gnome?
[17:51]  * Daskreech heads on over
[17:51]  * apachelogger puts on his ninja uwagi and goes on war path
[17:55] <apachelogger> http://news.cnet.com/8301-30684_3-10363025-265.html
[17:57] <pvandewyngaerde> how can i troubleshoot keyboard input issues ?? i have no X keyboard input in kde,   but it works in gnome
[18:07] <neversfelde> Riddell: a user in the german forum confirmed problems with the translations after the last upgrade
[18:08] <neversfelde> every test installation I did was ok, so probably a problem with upgraded systems
[18:11] <apachelogger> mhhh
[18:11] <apachelogger> translations
[18:16] <hunger> karmic does work pretty well for me today by the way.
[18:16] <hunger> All the important stuff works.
[18:16]  * hunger has not tried the netbook edition, that was to annoying the last time he tried it.
[18:17] <apachelogger> at least some nice words :)
[18:28] <apachelogger> kubotu: identica dent !kubuntu teaser: Project Timelord (name not approved yet)
[18:28] <kubotu> status updated
[18:34] <daskreech> apachelogger: other than the kwin kickup  What is the kubuntu blowup on the planet?
[18:35] <apachelogger> comments on nixternals blog
[18:35] <apachelogger> kubuntu not getting any attention blog
[18:35] <daskreech> ok
[18:35] <apachelogger> previous kubuntu translations sux blogs
[18:35] <daskreech> well how much  canonical attention is it getting
[18:35] <daskreech> Well they do
[18:36] <daskreech> Kubuntu gets attention just not vocally from the people who vocally say they officailly support it
[18:36] <apachelogger> as if anyone would care about that if the product was awesome enough
[18:36] <Sput> ScottK: you could try putting the following in quasselclient.conf:
[18:36] <Sput> [Notification]
[18:36] <Sput> Indicator\Enabled=true
[18:36] <Sput> maybe that works
[18:36] <Sput> (after restarting Quassel)
[18:37] <daskreech> apachelogger: Mindshare is the currency for FOSS projects
[18:37] <ScottK> Sure.
[18:37] <daskreech> That and participation.
[18:37] <daskreech> Being awesome will still get you left as dead after a while
[18:38]  * apachelogger does not see how kubuntu is awesome though :P
[18:38] <daskreech> :-)
[18:39] <ScottK> Sput: Does it matter where in the file it goes?
[18:39] <apachelogger> ScottK: no
[18:39] <ScottK> apachelogger: Thanks.
[18:39] <Sput> ScottK: no, but you should make sure you don't already have a [Notification] section
[18:39] <ScottK> OK
[18:39] <Sput> (and obviously it should be places in between/after other sections ;-))
[18:39] <Sput> *placed
[18:40] <daskreech> apachelogger: Ah and The Kubuntu is irresponsible post has been nearly retracted
[18:40] <apachelogger> daskreech: which one would that be?
[18:41] <daskreech> http://blog.martin-graesslin.com/blog/2009/09/why-distributions-shouldnt-ship-development-versions/
[18:42] <apachelogger> daskreech: there are larger things at works to get martin that pissed though
[18:42] <ScottK> Would someone ping me please....
[18:42] <JontheEchidna> ScottK: ping
[18:43] <Sput> ScottK:  sure
[18:43] <daskreech> ScottK: pung
[18:43] <ScottK> Thanks
[18:43] <daskreech> Does Kubuntu have a list of challenges facing Kubuntu ?
[18:44] <claydoh> sooo all distributions should only allow what upstream dictates?
[18:44] <daskreech> claydoh: I doubt he's saying that
[18:44] <claydoh> maybe a little
[18:44] <apachelogger> daskreech: Kubuntu's challenge numero uno: Kubuntu
[18:45] <daskreech> apachelogger: State it in terms of teh objectives of Kubuntu
[18:45] <daskreech> the
[18:45] <apachelogger> pardon?
[18:46] <apachelogger> ScottK: dropped you a mail
[18:47]  * ScottK is in a meeting, but will try to get a look at it.
[18:47] <ScottK> Sput: No luck.
[18:47] <Sput> ScottK: hmmm, well, I'm delegating this to agateau then :)
[18:47] <ScottK> OK.
[18:47] <ScottK> Fair enough.
[18:47] <Sput> notifications in KDE-mode get some special treatment to keep them consistent
[18:47] <apachelogger> ScottK: sure, nothing that needs immediate action
[18:48] <apachelogger> only somewhat immediate ;)
[18:48]  * Sput has plans to rewrite everything notification-related for 0.6 anyways
[18:51] <seele_> sebas: ping
[18:51] <sebas> seele_: pong
[18:53] <daskreech> apachelogger: If there are challenges facing kubuntu it has to be challeneges that prevent it from achieving it's directive as a distro
[18:54] <apachelogger> daskreech: well, what is the directive anyway?
[18:54] <daskreech> so have the challenges framed as an obstacle to acheiving that
[18:54] <daskreech> Note: We don't know our objective Challenge number one :)
[18:55] <seele_> what do you mean we dont know our objective? our objective is to deliver a user-friendly KDE distribution with a focus on home users more than corporate users
[18:55] <pgquiles> ScottK: ping
[18:56] <apachelogger> seele_: do we do that now?
[18:56]  * apachelogger coughs about konqueror being broken for all of $user websites
[18:56] <ScottK> pgquiles: Pong, but I'm in a meeting, so I can't give you much attention.
[18:56] <pgquiles> ScottK: ok, ping me back when you are done
[18:57]  * ScottK will endevour to remember
[18:58] <claydoh> heck, I first tried out Kubuntu because it was a single-cd, kde-only distro
[19:00] <daskreech> seele_: :-)
[19:00] <apachelogger> claydoh: I am merely suggesting that we are not true to our supposed objective at times
[19:00] <claydoh> so where can we find these objectives laid out? Or maybe we have too many of them?
[19:01] <daskreech> apachelogger: All websites is a strong statement but agreed teh Web browser solution is an issue what is the problem facing shipping a user friendly kde browser?
[19:01] <apachelogger> we cannot find them :)
[19:01] <apachelogger> here begins the fun
[19:01] <claydoh> do-over! :)
[19:01] <daskreech> claydoh: We have one objective. We are trying to see what issues we have in getting to that objective
[19:02]  * claydoh 's head spins
[19:02] <apachelogger> daskreech: well, does the user benefit from having a kde browser
[19:02] <apachelogger> meaning does it have to be a kde browser for the sake of being a kde-only distribution
[19:02] <claydoh> as a user, I happen to use Konqueror 99%
[19:02] <apachelogger> that is another thing
[19:02] <apachelogger> do we always make decissions on what is best for the target audience or what is best for us :P
[19:03] <daskreech> apachelogger: Yes
[19:03]  * apachelogger might remind that the amount of SRUs done on KDE packages is towards 0
[19:03] <daskreech> Why is that?
[19:04] <apachelogger> obviously not because we think that the target audience would benefit from a working product
[19:04] <apachelogger> ...it would seem
[19:04] <daskreech> Obviously :)
[19:05] <seele_> apachelogger: i dont knwo if we do that now, but afaik that is our goal
[19:05] <apachelogger> seele_: yeah, it is a pretty bad definition though, since it can be overriden at any given point
[19:06] <daskreech> how so?
[19:06] <apachelogger> as I tried to outline :)
[19:06] <seele_> you mean because it isn't written down or because there is a hand with control over what we do?
[19:06] <daskreech> SRU thing is a issue. Rather than saying it's obvious what the problem is maybe we can find out if tha's so?
[19:07] <apachelogger> seele_: because we do not control ourselfs what we do, and we cant do that because the objective is rather unprecise
[19:08] <apachelogger> no matter whether written down or not, there is a lot of interpretation available for the stated objective
[19:08] <daskreech> apachelogger: How would you differentiate what is good for the user and good for us?
[19:09] <daskreech> Where us is the distro of course :)
[19:10] <apachelogger> daskreech: I'd like to use the term target audience ... currently I am not sure target audience matches users though
[19:10] <apachelogger> anyway, since everything should be seen from a 'what use does it have for the target audience' POV
[19:10] <apachelogger> what use does having no KDE 3 apps on the CD have?
[19:11] <apachelogger> I mean, I am all for saving CD space for the sake of more translations, then again I look at the translations and rather have none on the CD at all, because some of them were quite embarassing at times
[19:11] <apachelogger> so I doubt translations could be used as an argument here
[19:13] <apachelogger> while I am at it, I might add that AFAIK lang-packs still ship KDE 3 translations as well...
[19:15] <daskreech> ok
[19:16] <ScottK> Jaunty has jad exactly two SRUs.  They are still in proposed, not accepted.
[19:17]  * ScottK checked every KDE core package when he backported KDE 4.2.4.
[19:18] <bbigras> :( policykit-kde crashed while testing the karmic test iso in oem mode. can't update with kpackagekit, I think it's the same bug as https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/438667
[19:20] <daskreech> apachelogger: well we have an inheritance to be available for as many languages as possible. Part of the Human thing from Ubuntu
[19:24] <daskreech> apachelogger: also what is your definition of target audience?
[19:25] <firephoto> as a user the biggest issue i see with the SRU process is that it is a process. if a kde x.y.2 is released to replace x.y.1 then it should just happen as an update.
[19:25] <apachelogger> daskreech: not defined ATM
[19:25] <apachelogger> part of the problem
[19:26] <firephoto> to not update it is to tell KDE upstream their work isn't good enough.
[19:26] <apachelogger> firephoto: working on that see, mailing list
[19:26] <firephoto> yea. i know. but this is a many year process of working on. ;)
[19:28] <apachelogger> tell me about it
[19:28] <apachelogger> also a many year process to get translations working ;)
[19:28] <daskreech> Is part of that problem that when something is slated as supported in a repo changes or new versions are viewed as suspect?
[19:29] <claydoh> all I need is a distro with kde and both wobbly windows and the slide-back effect :D
[19:29] <daskreech> Is part of that problem that when something is slated as supported in a repo, then changes or new versions are viewed as suspect?
[19:30] <apachelogger> yes, technically any new version could introduce regressions, which is generally not that much of an advantage to get it into the updates repo
[19:30] <ScottK> firephoto: We did deploy 4.1.x updates to intrepid-updates.  Due to KDE mistakenly aiming at Qt 4.4 for KDE 4.2, there was no way we could do it for Jaunty.  I'm working on a plan for Karmic.
[19:30] <daskreech> so what would we like for a KDE x.x.x+1 version ?
[19:30] <claydoh> isn't this something we have to inherit from Ubuntu? do they have SRU's for new Gnome versions?
[19:31] <daskreech> A fast track testing or a exception to the normal skepticism ?
[19:31] <ScottK> apachelogger: I do want the updates in -updates.  We can review and test in PPA -> proposed -> updates
[19:32] <apachelogger> aye, that is what I want too :)
[19:32] <ScottK> Now that KDE has a sane plan for Qt alignment, it should be achievable.
[19:32] <firephoto> I just think it takes more confidence and a willing to fix regressions even after the fact. obvious regressions usually have obvious fixes but the process slows the fixes from seeing the users.
[19:33] <ScottK> firephoto: We did that successfully for 3.5.10 and 4.1.3/4.  It just wasn't possible for 4.2 due to Qt version mismatch.
[19:36] <bbigras> In the installation process, when seeing the preview of my keyboard layout, some keys are shown with a square caracther instead of the real key. http://imagebin.ca/view/4ZAJbsF.html Should this be reported as a bug and added in my review?
[19:41] <davmor2> Riddell: kick back an relax for a bit dude I'll blitz alternate for you ;)
[19:43] <daskreech> ok so is there value in having this list of challenges somewhere public for  discussion?
[19:45] <apachelogger> no
[19:45] <apachelogger> working on it
[19:50] <cbr> hi
[19:50] <cbr> i can't see pidgin's icon in kde systray
[19:52] <cbr> who's to blame?
[19:52] <daskreech> Ronald Regan!
[19:53] <cbr> okay
[19:53] <cbr> let me at him
[19:53] <daskreech> which KDE and which pidgin?
[20:00] <cbr> karmic's latest
[20:01] <cbr> well, i dont have all the kde packages at highest revision prolly
[20:01] <daskreech> Probably pidgin
[20:02] <ScottK> I think it's on purpose.
[20:03] <JontheEchidna> yeah: https://edge.launchpad.net/ubuntu/+source/pidgin/1:2.6.1-2ubuntu1
[20:03] <ScottK> I think you're supposed to have a message indicator that means you don't  need it.
[20:03] <ScottK> BTW, why is Kmail MI stuff on by default?
[20:05] <neversfelde> mhh, I downloaded all missing language packs with qt-language-selector --mode install and set the system to german with qt-languagle-selector --mode select, I guess it should be german now :)
[20:05] <Quintasan> hmm I think bringing some copies of my GPG key to UDS would be a good idea
[20:05]  * Quintasan has lost several keys so far
[20:10] <neversfelde> meh, still a mixture of english and german :(
[20:14] <davmor2> Riddell: ScottK: are you having issues with kubuntu getting to kdm?
[20:14] <pgquiles> ScottK: still in the meeting?
[20:15] <ScottK> davmor2: Not anymore.  I was on one update previous to the current one.
[20:15] <ScottK> pgquiles: Yes.
[20:16] <davmor2> ah no just a slight delay weird
[20:17] <ScottK> The one before was broken, I just mistakenly upgraded off of a stale mirror.
[20:21] <tester_> Hello this is me this is from quassel just to see if it works
[20:21] <davmor2> yeap
[20:43] <JontheEchidna> Nightrose: fixing that grammar error in the doc. I started to write one thing then decided to write it another way
[20:43] <Nightrose> JontheEchidna: hehe ok - just delete my comment then
[20:52] <JontheEchidna> Nightrose: btw, in a list if you press enter then hit tab, the comment becomes a fancy second-level bullet point
[20:52] <Nightrose> JontheEchidna: ;-)
[20:52]  * JontheEchidna is a bit ocd about such things
[20:53] <JontheEchidna> watching the document update in front of you is pretty neat
[20:54] <Nightrose> hehe yea
[21:44] <a|wen> anybody else noticed kdm not starting with the login-screen, but with the kde-splash stuck at the first step? only happens on first start; after logout or restarting kdm it works fine
[21:46] <nixternal> yes I have
[21:47] <nixternal> been happening for a couple of weeks now
[21:49] <a|wen> i'm rarely restarting so haven't noticed before a few days ago, and wanted to verify that it happened regularly ... could it have anything to do with the upstart conversion of kdm? can't think of anything else
[21:49] <JontheEchidna> It's meant to be our equivalent of xsplash. the splash is supposed to turn on early in the boot process to replace usplash
[21:50] <JontheEchidna> I am not quite sure how much of it all is implemented, nor how well
[21:51] <neversfelde> I have to press Enter during the start 3 times, and I don't know why :)
[21:51] <a|wen> JontheEchidna: so the standard login-splash should also show prior to the login-screen?
[21:51] <neversfelde> screen is black and logs are quiet
[21:52] <JontheEchidna> a|wen: until we get a better theme, currently it is using "Default" which is the hard disk icon from the current login splash
[21:53] <a|wen> ahh, makes sense why it is there then ;) ... only problem is then, that it appears just after the login-screen has been show (overtaking its place) and not at the beginning of the boot process
[22:06] <neversfelde> bilbo was renamed to blogilo, because of some trademark problems. Should we rename it after beta freeze, too?
[22:14] <a|wen> neversfelde: it's in universe and not on any cd's afaik, so shouldn't collide with the freeze ... and we should probably rename it; but i'm no expert on that stuff
[22:15] <JontheEchidna> On one hand, we probably don't want legal trouble. But on the other hand it wouldn't be good to change the package name while the current release is still called Bilbo Blogger
[22:16] <neversfelde> I am not sure, because version 1.0 was released under the name bilbo and the tarball is still called bilbo-1.0
[22:16] <a|wen> but the content of the tarball changed?
[22:16] <neversfelde> no
[22:16] <neversfelde> I do not think so
[22:17] <a|wen> okay, so no official release with the new name yet... do we know if they have any plans to do that soon?
[22:18] <neversfelde> a|wen: I will ask, but I doubt that, because things are going to be merged to kdepim
[22:20] <a|wen> neversfelde: would be nice, if they did... do they have a VCS where the name-change is committed in one or a number of revisions; then we could probably grab from there
[22:22] <nixternal> a|wen: it was occurring before the kde->upstart conversion
[22:22] <neversfelde> oh, it is already in KDE svn
[22:23] <nixternal> neversfelde: either rename it or remove it
[22:23] <nixternal> this happened before, though I can't remember which app it was, and it had to be changed immediately
[22:24] <a|wen> nixternal: yeah ... seems the splash should be there; just occurs to late
[22:24] <neversfelde> nixternal: probably upstream can release a 1.0.1 under the new name, that would be the easiest solution?
[22:25] <nixternal> ya, they need to do so honestly
[22:25] <nixternal> don't know why they haven't yet
[22:25] <neversfelde> I'll ask the devs
[22:26] <ScottK> neversfelde: I wouldn't worry about renaming bilbo
[22:26] <ScottK> neversfelde: I think it's already been merged into kdepim
[22:26] <neversfelde> ScottK: seems so
[22:26] <ScottK> nixternal: It was gaim -> pidgin before.
[22:26] <ScottK> Unless someone complains to us, I think we shouldn't worry about it.
[22:27] <nixternal> oooh, I wasn't even thinking about that one, but you are right
[22:27] <neversfelde> yes, that's the same problem
[22:31] <ScottK> We are using the name upstream released it under.  If they do a release with a different name, then we might consider it.
[22:32] <neversfelde> sounds good for me
[22:48] <neversfelde> upstream said that it is ok, if we leave the name as it is. Next bilbo release will be with KDE 4.4., because it needs new kblog
[22:54] <neversfelde> we need a normalize-audio patch for k3b, it is in debian. Is it the better way to only import that one patch or do a whole merge? importing many patches would be risky, or not?
[23:01] <Riddell> neversfelde: post beta is a time for minimal changes only, so only that patch
[23:02] <neversfelde> Riddell: k
[23:22] <bbigras> oh crap, I just realised I reviewed the iso in the ubuntu section instead of kubuntu
[23:29] <davmor2> bbigras: that's a firing squad offence that ;)
[23:29] <ScottK> So that would explain the policykit-kde bug on the Ubuntu test result
[23:31] <bbigras> yes :( I'm updating my iso and going to test it a second time and report it at the right place.
[23:33] <ScottK> claydoh: Doing release notes for the beta?
[23:33] <bbigras> Should I contact someone about this or is any of you able to fix it?
[23:35] <ScottK> I mentioned it.
[23:35] <claydoh> ScottK: sure, its Oct1, correct?
[23:35] <ScottK> No need to worry about it.
[23:35] <ScottK> claydoh: If that's Thursday, yes.
[23:36] <claydoh> yup
[23:41] <neversfelde> what do we do with packages that do not build?
[23:42] <neversfelde> oh, I have many questions today :)
[23:42] <ScottK> neversfelde: Fix them
[23:43] <neversfelde> ScottK: I tried, but I did not have any success. I wrote a mail to the author, but did not get an answer so far. Probably someone else should have a look at kid3, it is an important application for some users.
[23:44] <ScottK> neversfelde: Send a mail to ubuntu-devel and explain the problem, what you tried, and ask for help.
[23:45] <neversfelde> ScottK: ok, will do after beta. I wrote the mail to upstream yesterday, so they probably need some time.
[23:47] <ScottK> OK
[23:47] <ScottK> neversfelde: Also check Debian BTS.
[23:47] <neversfelde> ScottK: already did, no fix there
[23:47] <neversfelde> I think it is a problem with taglib 1.6
[23:48] <neversfelde> and mp4 support enabled in kubuntu