[15:09] <MoPac> Hello. I'm wondering if the patch for timing-induced data corruption with TRIM on Samsung SSDs is incorporated into the latest 3.19.0-XX release kernels in 15.04. I have an 840 EVO and am not sure whether it's safe to upgrade the firmware
[15:39] <apw> 8m ... thats not long to wait
[15:39] <apw> MoPac (N,BFTL), if you know the specific patch you are talking about ... then ... we can check
[15:40] <apw> henrix_, kamal, does the above description ring a bell ...
[15:40] <apw> is that the "turn off trim for a family of drives" fix i wonder
[15:42] <kamal> apw, what above description?  (I just reconnected to irc -- no backscroll)
[15:43] <henrix_> apw: yes, it does ring a bell... checking
[15:44] <henrix> apw: kamal: it's commit 9a9324d39696 ("libata: Blacklist queued TRIM on all Samsung 800-series") which is already in vivid
[15:44] <henrix> kamal: there was a user asking if 3.19 had the fix for the 840 EVO SSD
[15:53] <apw> henrix, thanks, the logs are complete even if they anr't here to appreciate it
[15:54] <henrix> :)
[20:01] <TJ-> Hopefully we can get this SSD TRIM fix backported: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f3f5da624e0a891c34d8cd513c57f1d9b0c7dadc
[20:38] <FourFire> Greetings, which is the latest kernel version which I can manually install on ubuntu 15.04 and expect it not to crash/have drivber problems?
[20:39] <FourFire> I suppose that last qualifier complicated things a bit, just ignore it (drivers) if that's the case
[20:40] <FourFire> from what I can see in the mainline repo, 4.0.9 looks like the best candidate, but I don't really know anything about kernel development so I've come here for a second opinion
[20:56] <FourFire> ok, since noone has answered me in 15 minutes I'm going to go ahead and install 4.0.9


[02:52] <manchicken> Tonio2: Howdy
[02:59] <manchicken> Has anybody had a chance to review the merge request I put in?
[09:24] <Mamarok> dear Kubuntu devs, any news about my Konsole ignoring I am using English as the system language and insisting on showing everything in German? This is highly annoying, just because I installed additional langauges
[09:34] <Noskcaj> Mamarok, Have you filed a bug?
[09:36] <Mamarok> Noskcaj: yofel knows about
[09:37] <yofel> it should be fixed with the patch that harald dropped being gone. That's in the RC1 packages that I'm still working on
[09:38] <yofel> so, fixed *soon*
[09:45] <Mamarok> yofel: cool, thank for the heads up
[09:51] <apachelogger> yofel: no it wouldn't
[09:51] <yofel> oh? :/
[09:51] <apachelogger> the patch only set the KDE country setting, that has nothing to do with language
[11:25] <BluesKaj> Hiyas all
[11:49] <Quintasan> \o
[11:49] <Riddell> it's..  I don't see how this is Kubuntu specific.
[17:39]  * ScottK neither.
[18:44] <ahoneybun> hey valorie Riddell
[20:14] <ScottK> Releasng 4.10.5 to updates
[21:01]  * ScottK started a calligra armhf build to check out the FTBFS.
[21:18] <yofel> Quintasan: http://paste.kde.org/p17af0185
[21:22] <Riddell> debfx: we looked through the medibuntu archive and libdvdcss was the only thing we wanted/could to keep from it
[21:22] <Riddell> the rest are non-free, can go in ubuntu or are no use
[21:22] <Riddell> see my post to kubuntu-devel
[21:34] <Riddell> http://fridge.ubuntu.com/2013/07/11/ubuntu-developer-summit-27-29-august-2013/  Ubuntu Developer Summit: 27-29 August 2013
[23:35]  * ScottK gives Riddell a slap for not pushing the last calligra upload to bzr. (fixed)
[23:54] <Riddell> ScottK: oh doh, sorry
[23:58] <ScottK> No worries.


[11:39] <apw> stgraber, https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1517426 ... seems lxc is failing its autotests for what looks like a bad dep
[11:52] <caribou> can someone ping my nick again, please ?
[11:58] <apw> caribou, ?
[12:01] <caribou> apw: thanks!
[14:33] <gpiccoli> Hello, I don't know if this is the right place for asking help on this, but I'm having trouble in saving logs of kernel crashes on Ubuntu 14.04.3. Sorry to bother with this
[14:33] <gpiccoli> I have the linux-crashdump and the following parameter on my cmdline: "crashkernel=384M-2G:64M,2G-:128M"
[14:34] <gpiccoli> Even so, nothing shows up on /var/crash after a crash (I'm using sysrq for testing)
[14:34] <gpiccoli> Any clue?
[14:37] <apw> gpiccoli, is crash dumping enabled, i don't think it is by default when the package is installed
[14:37] <apw> caribou, ^
[14:38] <gpiccoli> apw, I followed some procedures of wiki page - I notice the following line on my dmesg: "Reserving 128MB of memory at 128MB for crashkernel (System RAM: 4096MB)"
[14:38] <caribou> apw: yes, it needs to be enabled in /etc/default/kdump-tools :
[14:38] <caribou> gpiccoli: ^
[14:38] <gpiccoli> wow, nice! thanks caribou and apw !
[14:38] <caribou> gpiccoli: USE_KDUMP=1 and then sudo kdump-config load (assuming that you have rebooted & crashkernel= is present)
[14:38] <apw> gpiccoli, do fix the wiki if it isn't correctly indicated in there
[14:38] <gpiccoli> Should I document this on wiki? OR is it already there, and I missed?
[14:39] <apw> gpiccoli, that you missed it implies it is not well enough presented even if it is there
[14:39] <caribou> gpiccoli: let me check. Which wiki are you looking at ?
[14:39] <gpiccoli> this one caribou: https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html
[14:40] <gpiccoli> apw, good point hehehe
[14:40] <caribou> gpiccoli: apw: it is under "Configuratino"
[14:40] <caribou> well "Configuration"
[14:40] <gpiccoli> wow, sorry caribou and apw
[14:40] <caribou> but I keep being asked to have it enabled by default
[14:41] <gpiccoli> My bad =//
[14:41] <caribou> gpiccoli: no worry
[14:41] <gpiccoli> caribou, what is the con in having this enabled by default?
[14:41] <apw> yeah np, documentation is lik that
[14:41] <caribou> apw: we talked about it in Austin, remember
[14:41] <caribou> gpiccoli: nothing really, it is mostly historical
[14:41] <apw> caribou, indeed, it does seem odd to install something which has no other purpose and not enable it by default
[14:41] <caribou> apw: agree
[14:42] <apw> if it needs configuration before enabling it makes sense, yes fine
[14:42] <gpiccoli> Is there a way to enable this flag automatically on linux-crashdump install ?
[14:42] <gpiccoli> Would be nifty
[14:42] <apw> gpiccoli, could be done, but it is i a change, and so needs discussing publically first
[14:42] <apw> in case there is a compelling reason not to that we are not htought of
[14:42] <caribou> apw: I just had a chat with bwh in #debian-kernel and he's fine with having the small initrd fix in Debian as well
[14:43] <gpiccoli> sure apw, I agree! I think it makes sense...for airheads like me heh
[14:43] <apw> caribou, nice, i thnk i  saw you chatting
[14:43] <caribou> apw: so I'm thinking of pairing this change with defaulting to Yes
[14:43] <apw> gpiccoli, for the casual user you want it to work as best it can without config, even if power users will want to change things
[14:43] <caribou> apw: with the option of setting it to False if needed
[14:43] <gpiccoli> Great caribou and apw!!!
[14:44] <apw> caribou, might be woth sending out some kind of rfc on that if you havent, to ubuntu-devel or something
[14:44] <caribou> then I'll push both changes to Debian/Sid so it syncs to Xenial
[14:44] <apw> something more focused if there is one
[14:44] <caribou> apw: ubuntu-devel & ubuntu-kernel maybe ?
[14:44] <apw> works for me
[14:44] <caribou> k
[14:44] <apw> i can't see you getting any responses at all :)
[14:45] <caribou> apw: that's what happened with my post to debian-kernel :-)
[14:46] <apw> caribou, :)
[14:47] <caribou> apw: the kernel ML is<EMAIL_ADDRESS>right ?
[14:49] <apw> caribou, ack
[14:53] <apw> caribou, approved your post
[15:17] <gpiccoli> apw, caribou: I'm still with no luck
[15:17] <caribou> gpiccoli: let me run a  quick test
[15:17] <gpiccoli> Even with those modifications, only a file named kexec_cmd is created
[15:17] <gpiccoli> I'm on PPC64 kvm _guest_
[15:17] <caribou> oh, ppc64
[15:18] <gpiccoli> What I need is only the log, I don't even need the vmcore
[15:18] <caribou> gpiccoli: any chance I can access it remotely ?
[15:19] <gpiccoli> Unfortunately no caribou, I'm very sorry
[15:19] <gpiccoli> It's private network only
[15:19] <caribou> gpiccoli: np
[15:19] <gpiccoli> I can perform any test you want although
[15:19] <gpiccoli> Note: I already could generate those dumps in the past days
[15:19] <gpiccoli> Reinstalled the system and now, it does not work
[15:20] <apw> gpiccoli, big or little endian (powerpc or ppc64el debian arch)
[15:21] <gpiccoli> ppc64el
[15:21] <gpiccoli> apw ^
[15:22] <caribou> gpiccoli: would you be able to capture the console output during one of your test ?
[15:22] <gpiccoli> ok,
[15:22] <gpiccoli> what dfo you need to see?
[15:22] <gpiccoli> *do
[15:22] <caribou> gpiccoli: well, the portion between the kernel panic & the reboot
[15:23] <gpiccoli> ok, I can put here, but we have not too much output there
[15:23] <apw> gpiccoli, i would pastebinit, rather than putting it in ir
[15:23] <apw> irc
[15:24] <gpiccoli> good idea apw! I'll paste some more info too =)
[15:30] <gpiccoli> apw, caribou: http://pastebin.ca/3259739
[15:30] <gpiccoli> Do you need after QEMU boot logs?
[15:30] <gpiccoli> I sttoped on QEMU first line, can past the rest here if you want
[15:31] <gpiccoli> I should check my loglevel too...
[15:32] <caribou> gpiccoli: well, there's nothing after the sysrq-trigger, you should have the panic backtrace, etc
[15:33] <gpiccoli> There you go!
[15:33] <gpiccoli> What do you think that can be happening?
[15:34] <gpiccoli> It's like if crashes are not being even dumpeed
[15:34] <gpiccoli> *dumped
[15:34] <caribou> gpiccoli: ? same pastebin ?
[15:35] <apw> caribou, well you see it starting to do osmething, as it emits what looks like half of the first line of a kernel boot ?
[15:35] <gpiccoli> caribou, I'm sorry - I didn't understand your question marks hehe
[15:35] <caribou> apw: it should start by displaying the panic() msg
[15:36] <apw> caribou, he is saying that is all he gets, "there you go you are seeing what i see" not "there you go some more information"
[15:36] <caribou> gpiccoli: I thought you had pasted more information somewhere else
[15:36] <apw> english, sooooo unambigious
[15:36] <gpiccoli> yes apw, thanks!!!
[15:36] <gpiccoli> your got right my expression. Sorry caribou
[15:36] <caribou> gpiccoli: can you paste the result of "sudo kdump-config show" pls ?
[15:36] <gpiccoli> I'm not so good in english, so it can be entirely my bad - sorry
[15:37] <gpiccoli> sure!
[15:37] <caribou> gpiccoli: no worry:)
[15:37] <apw> the SLOF line is the indicator that we are booting a new right, after the crash would have been completed if it had occured
[15:38] <gpiccoli> caribou, apw: http://pastebin.ca/3259751
[15:42] <caribou> gpiccoli: what's the result of cat /sys/kernel/fadump_enabled ?
[15:42] <caribou> long shot
[15:43] <gpiccoli> caribou:
[15:43] <gpiccoli> root@ubuntu:~# cat /sys/kernel/fadump_enabled
[15:43] <gpiccoli> cat: /sys/kernel/fadump_enabled: No such file or directory
[15:43] <gpiccoli> =0
[15:43] <caribou> gpiccoli: ok, just wanted to check, this is a PPC specific dump mode
[15:44] <gpiccoli> ok, great!
[15:44] <gpiccoli> BTW, thanks verym uch for your help
[15:46] <apw> slangasek, i think it was you who asked why our testing depended on exim4.  I think i have just found out (well cking did), it seems the aslr test in QRT uses starting/stopping exim as part of its payload
[15:47] <cking> namely because of bug https://bugs.launchpad.net/bugs/504164
[15:49] <caribou> gpiccoli: I'm going to fetch a PPC64 iso & try to test it locally. May take a little while
[15:50] <gpiccoli> Thanks very very much caribou, I'm really appreciate your help =)
[15:50] <gpiccoli> I'll turn my guest off [some more people need the machine]
[15:51] <caribou> gpiccoli: well, I maintain that code so I would highly prefer to see it work ;-)
[15:52] <gpiccoli> hehehe =)
[15:52] <gpiccoli> Great to hear!
[15:53] <gpiccoli> Your are a very nice maintainer, it's good to see such interest and effort
[15:53] <gpiccoli> Not all maintainers are as you, we all know heh
[15:58] <caribou> gpiccoli: Is using PPC64 as the VM architecture correct ?
[15:59] <gpiccoli> Hmmm..I don't know
[15:59] <gpiccoli> What are the possibilities?
[15:59] <gpiccoli> caribou ^
[15:59] <gpiccoli> I can check my VM here
[16:00] <caribou> gpiccoli: If I select ppc64le, it asks me for an existing image
[16:00] <gpiccoli> in libvirt sml we have:     <type arch='ppc64' machine='pseries-2.4'>hvm</type>
[16:00] <gpiccoli> *xml
[16:09] <caribou> gpiccoli: I'm getting near end of day. Can you email me the .xml description of your VM ?
[16:11] <slangasek> apw: ah, heh.  exim still seems a strange choice of mta then :)
[16:11] <apw> slangasek, its not as an mta, it is because that specific binary was a reproducer
[16:12] <slangasek> ahhh ok
[16:13] <gpiccoli> Sure caribou, thanks!!
[16:13] <gpiccoli> PM me your email
[17:28] <jderose> When is 4.2.0-19.23 expected to land in Wily updates?
[17:31] <apw> jderose, iirc we are about 2 weeks out
[17:33] <apw> jderose, assuming not kitten killers it is slated to release by the 28th
[17:34] <jderose> apw: much thanks! i wasn't sure whether I was reading the kernel newsletter correctly or not :)
[17:34] <apw> jderose, yep, the dates are intentionally vague to let things move around for emergencies and regressions
[19:56] <cristian_c> jsalisbury: hello


[09:58] <gry> hi, what is the correct channel supporting users in making their own new ubuntu spin or flavour?
[13:20] <guiverc> gry, I'd try a linux channel as flavors are applications made after minimum of two releases (ie. one year+) with a team etc.. as per https://wiki.ubuntu.com/RecognizedFlavors which isn't what you appear to be seeking or capable of (flavor has a specific meaning); you're wanting to create a linux system as I see it.  (my 2c)
[13:22] <guiverc> maybe intersting; https://ubuntuunity.org/posts/ubuntu-unity-becomes-an-official-flavor/    I'd start by reading blogs by people who've done it (eg. the creator of Makulu Linux blogged about the Makulu respin when Ubuntu based; it's not a flavor.. but respin unrelated to Ubuntu, just Ubuntu based)


[00:00] <a|wen> neversfelde: ask away while i'm here :) ... though atm i'm all to busy with other stuff; so i'm less around than i would like to
[00:02] <a|wen> gah, i'm totally failing at googling ... how hard can it be to find any .bin cd image; no matter what it contains
[00:05] <neversfelde> yay, Kubuntu community is really great. Every question I have is answered within seconds, but I need more infos about tha tasks a MOTU has and I would really like to be better in bug triaging, Launchpad is really not self-explanatory
[00:14] <a|wen> :)
[00:15] <a|wen> it takes a little time getting good friends with LP
[00:15] <neversfelde> hehe
[00:15] <neversfelde> yes
[00:18] <neversfelde> we might have a problem with amarok and ipods. It is recognized and shown, but you cannot copy any song to it
[00:18] <neversfelde> Nightrose: is that a known problem?
[00:20] <Nightrose> neversfelde: sorry - no idea - nad day - can't think straight
[00:20] <Nightrose> *bad
[00:21] <neversfelde> mhh, I'll have another test with the rc
[00:21] <neversfelde> and probably file a bug report then
[00:22] <neversfelde> and hope your day will get better :)
[00:22] <Nightrose> not much hope :( but thanks
[00:22]  * Nightrose goes to bed
[00:22] <neversfelde> gn8
[00:29] <a|wen> nn neversfelde
[00:29]  * a|wen runs for bed as well ... need to get up early tomorrow
[00:30] <neversfelde> n8 a|wen
[04:29] <nixternal> Nightrose: one module complete, one more to go...phew this is a lot of tedious work
[04:33] <rgreening> ScottK: is it possible to download Alpha5? or one of the dailies prior to Alpha6? Im trying to track down an Acer specific bug...
[04:33] <ScottK> rgreening: I think so.  Look at the release announcement for a like to the ISO for Alpha 5.
[04:33] <ScottK> Dailies, I'm pretty sure, get purged regularly.
[04:33] <rgreening> http://cdimage.ubuntu.com/kubuntu/releases/karmic/alpha-5 doesn't exist...
[04:34] <ScottK> Hmmm
[04:35] <ScottK> I guess hunt for stale mirrors.
[04:35] <rgreening> damn
[04:36] <rgreening> I go tthis Acer bug with USB (I think it's either kernel acer-wmi or HAL/DBUS at fault
[04:36] <rgreening> but I have no way to track
[04:37] <ScottK> LP has previous package revisions.
[04:38] <rgreening> ScottK: I dont know which packages, only that it worked 2-3 days prior to Alpha 6
[04:39] <ScottK> I'd start with an older kernel, myself.
[04:39] <rgreening> hmm. I don't recall if kernel had changed in that time, but maybe....
[04:50] <nixternal> rgreening: you might find alpha5 isos via torrent
[04:51] <ScottK> \o/ amarok built on armel.
[04:53] <rgreening> ScottK: I can't seem to find an older kernel ( circa Sept 10-14th )
[04:53] <ScottK> OK. Not sure then.
[04:54]  * ScottK heads to bed.
[07:27] <Nightrose> nixternal: thanks for doing it
[07:35] <nixternal> it has made me realize just how horrible Office Suites are for doing anything that is supposed to look good
[07:36] <nixternal> it has made me hate openoffice.org even more as well
[07:36] <nixternal> which I didn't think was possible
[07:41] <glick> excuse me, is anyone here familier with MPC and or CMAKE?
[07:42] <jussi01> glick: best to just ask your question and see.
[07:47] <glick> on my top level directory i have a CmakeLists.txt file, and then i have a folder that makes libraries, in that CmakeLists.txt file do I need another PROJECT() command?
[07:48] <jussi01> glick: TBH, I dont know the answer, but its kind of quiet here usually fgor about another hour or 2.
[07:49] <glick> god MPC is such a piece of crap, and figuring out how it works is giving me brain hemorage
[08:38] <dany_21a_> hello, is someone here who maintains kubuntu-ppa? Would be great if someone could backport this: https://bugs.launchpad.net/ubuntu/+source/eric/+bug/380701
[08:40] <dany_21a_> And how is this with paperKuts? how can i specifiy papercuts for kubuntu?
[08:44] <jussi01> dany_21a_: see /topic :)
[08:56] <dany_21a_> jussi01: yes, because of that i asked... I am not sure if its okay to report a kde-related cut to the ubuntu-papercuts - or if there is a special launchpad for paperkuts
[09:09] <dany_21a_> Anyhow, i reported that (in my opinion) papercut: https://bugs.launchpad.net/hundredpapercuts/+bug/435090  (hope thats the correct location)
[11:09] <serzholino> Hi! Will there be amarok 2.2 packages for jaunty, please?
[11:10] <Riddelll> unlikely, the amarok packaging in jaunty was very complex due to its use of mysql
[11:12] <serzholino> :( anyways, thanks for your hard work on kubuntu. Will upgrade to karmic beta then? when it will be out :)
[11:16] <Riddelll> only a week away!
[11:18] <davmor2> Riddelll: still an optimist I see ;)
[13:14] <Riddelll> AMD64 DVD now 4MB oversized!
[13:16] <Riddelll> CDs back to plenty of free space, I guess I should fill that up with languages for beta
[13:27] <Tonio__> Riddelll: just to let you know I'm starting a new fork now kdesudo seems not to require so much work...
[13:28] <Tonio__> Riddelll: powerdevil doesn't obey to xf86keys and doesn't have osd notification
[13:28] <Tonio__> Riddelll: basically we have klaptopdaemon but not kmilo
[13:28] <Tonio__> Riddelll: I'll fork kosd to act like kmilo did
[13:29] <Tonio__> Riddelll: I have a proof of concept that works here, but it won't be ready for karmic :/
[13:30] <Tonio__> will be there for Lucid, including, sound up/down, brightness up/down, suspend to disk/ram, show battery level and any xfree86 event I'm able to catch
[13:30] <Riddelll> Tonio__: I'd much rather that was done as part of powerdevil and not something separate, that's where the functionality belongs
[13:30] <Riddelll> sound up/down is already done by kmix
[13:30] <Tonio_> Riddelll: but no nice notification
[13:31] <Riddelll> the missing slickness is that visual notification should support a progress bar
[13:31] <Tonio_> Riddelll: sure I'd like that too, but powerdevil with solid is way more complicated code base, so I'll go the way I can do things
[13:31] <Tonio_> and maybe propose a code merge upstream when done
[13:31] <Tonio_> Riddelll: http://kde-apps.org/content/show.php/KOSD?content=81457
[13:32] <Tonio_> Riddelll: this is kosd notification, it supports native themes and is nice
[13:32] <Tonio_> Riddelll: the thing is that there are opened bugs at kde for a loooooooong time on that point
[13:32] <Tonio_> Riddelll: I can make it in a coupleof days, since most of the code is there, I just need to bind to dbus-xlibs...
[13:33] <Tonio_> Riddelll: once done we can discuss upstream for powerdevil/kmix inclusion, right ?
[13:33] <Tonio_> Riddelll: but technically the frontend/backend side of kde4 components is making it too complicated for me to code into :-(
[13:34] <Riddelll> well no, if you do it as a separate app unrelated to powerdevil, kmix or the KDE notifications then it can't be merged upstream into them
[13:34] <Riddelll> there's no backend/frontend, it's no harder to add a global shortcut to powerdevil than it is to a separate app
[13:34] <Riddelll> and the code is already in kmix as i SAY
[13:34] <Riddelll> the hard part is getting KDE notifications to have a progress bar
[13:35] <Tonio_> Riddelll: why not merging this OSD thing into ?
[13:35] <Tonio_> Riddelll: you don't want osd on that point, but notification ?
[13:35] <Riddelll> I want the normal KDE notifications to be used yes
[13:36] <Tonio_> Riddelll: my thing will use powerdevil and kmix from within dbus, the existing code already has this
[13:36] <Riddelll> I agree this is something that's missing/incomplete and if you do code it this way and it's the best solution at the time then we'll go with it, but it's not the final solution and it's unlikely to go upstream
[13:37] <Tonio_> sure that :)
[13:37] <Tonio_> Riddelll: let's say if it only is a couple of days to get something that works, then we can go with it to start, and then think of the long term...
[13:37] <Tonio_> Riddelll: thinking on the long term is nice, but getting things to work is better :)
[13:39] <Tonio_> Riddelll: but I agree it should be done in powerdevil/kmix directly with an osd class in kdelibs, that's true, let's call this step 2
[13:40] <agateau> I thought about this, I think for KMix the simplest solution is to use Plasma theme to decorate the existing progressbar
[13:40] <Tonio_> Riddelll: it looks like the missing functionnality is related to Qt bugs listening to xf86 keys
[13:40] <Tonio_> there are lots of reports on that point
[13:40] <agateau> simpler than gettting the xdg guys to accept a new version of the spec to support progress bars
[13:40] <Tonio_> and powerdevil only binds to keys within Qt
[13:41] <Riddelll> didn't we patch qt for some of that?
[13:41] <Tonio_> that's why I want to listen to key events from within dbus-xlib directly
[13:41] <Tonio_> Riddelll: well we did, yes
[13:41] <Tonio_> but there are still reports on that point all over the web
[13:42] <Tonio_> Riddelll: see kde bug 181444
[13:42] <agateau> looks like kosd is using Plasma theme as well
[13:42] <Tonio_> agateau: yep, plasma theme, and talking to powerdevil and kmix from within dbus
[13:42] <Tonio_> agateau: that's why I want to use this as a first step, because of little code base and pretty decent design
[13:43] <Riddelll> but it's the wrong way around!
[13:43] <Tonio_> agateau: when, at least for me, getting into kdelibs/powerdevil code is a lot more complex
[13:43] <Tonio_> Riddelll: sure it is, but I'll first do something that works :)
[13:43] <agateau> I believe getting the code in KMix should be simple
[13:43] <Riddelll> powerdevil and kmix are where the intelligence is, it should be them listening to it and calling the notification
[13:43] <Riddelll> the code is already in kmix
[13:43] <Tonio_> Riddelll: and about the osd thing ?
[13:44] <agateau> Yes, it just need to be pimped a bit with Plasma goodness
[13:44] <Tonio_> Riddelll: I'm not sure notification is the good way to get kmix/powerdevil infos to work on that point
[13:44] <Tonio_> I might be wrong :)
[13:44] <Tonio_> Riddelll: basically if I code this that way, then the code could be merged in plasma easilly right ?
[13:45] <Tonio_> since it'll use dbus and so on
nothing can be merged easily in Plasma </troll>
[13:45] <Tonio_> agateau: s/plasma/whatever
[13:46] <Tonio_> agateau: let's say that the code for listening to xf86 key and bind an event to powerdevil/kmix can be merged pretty easilly in kmix/powerdevil I think
[13:46] <agateau> but kmix already listens to xf86 keys, doesn't it?
[13:46] <Tonio_> agateau: so I'll do the "old way" with a standalone app, and once it's proven to work, I can ask for help to merge
[13:47] <Tonio_> agateau: yes it does, but imho it should do osd or anything else nicer
[13:47] <agateau> Tonio_: it already shows a plain progressbar,
[13:47] <Riddelll> this is the patch we have for qt https://bazaar.launchpad.net/%7Ekubuntu-members/qt/ubuntu/annotate/head%3A/debian/patches/0288-more-x-keycodes
[13:47] <agateau> you just need to use a plasma background behind it and you are done
[13:47] <Riddelll> lots of extra keys in there
[13:47] <Tonio_> Riddelll: kk
[13:48] <Tonio_> Riddelll: we can discuss this later, eventually in the uds or during ucid cycle
[13:48] <agateau> and I guess Riddelll knows kmix code ;)
[13:48] <agateau> (since he added the progressbar iirc)
[13:49] <Riddelll> it could do with showing something on mute too, that's currently missing
[13:49] <agateau> true
[13:49] <agateau> should be easy to add
[13:52] <Riddelll> Tonio_: so I think you should get the code for kosd, turn the widget into a library and get kmix using that instead of plain qprogressbar.  add in mute support.  do the same in powerdevil.  et voila
[13:52] <Riddelll> and maybe one day someone will add progress support to the normal KDE notification system
[13:52]  * agateau agrees with Riddelll
[13:56] <txwikinger_work> Hi Riddelll
[13:56] <txwikinger_work> Is ScottK around?
[13:56] <JontheEchinda> Riddelll: KDE is still oblivious to the extra keys, even if Qt sees them
[13:57] <JontheEchinda> there's a mirror of the keymaps somewhere in kde4libs that needs updating
[13:57] <JontheEchinda> bug 293213
[13:57] <JontheEchinda> otherwise those keys do nothing when assigned as shortcut keys
[13:58] <JontheEchinda> or hotkeys, etc
[13:58] <txwikinger_work> Where in Dallas is the UDS?
[13:58] <Riddelll> txwikinger_work: not seem him active today
[13:58] <Riddelll> txwikinger_work: where they wear big hats
[13:58] <Riddelll> JontheEchinda: hmm.  meh.
[13:59] <txwikinger_work> hahaha... you know very well that I wear one of those ;P
[14:00]  * txwikinger_work lived in Dallas for 7 years and knows it like the back of his hand
[14:08] <Riddelll> Tonio_: is kblueplugd needed with the new kdebluetooth?
[14:40] <Tonio_> Riddelll: afaik yes
[14:40] <rgreening> good day all
[14:40] <Tonio_> Riddelll: on that point it would be nice that someone with a bluetooth dongle gives feedback
[14:41] <Tonio_> Riddelll: I can't disable my bluetooth chip so I can't confirm...
[14:41] <Tonio_> Riddelll: the idea is just that the icon doesn't show up when no chipset is detected...
[14:42] <Tonio_> call for feedback, anyone here with a bluetooth key !!! just kill kblueplugd and start kbluetooth
[14:42] <Tonio_> then unplug the key...
[14:45]  * rgreening thinks I should go buy a bluetooth dongle to assist :P
[14:47] <Tonio_> rgreening: hum interesting
[14:47] <Tonio_> rgreening: can you start kbluetooth without a dongle ?
[14:47] <rgreening> :)
[14:47] <rgreening> good question...
[14:47] <Tonio_> and tell me if you have a bluetooth icon in the tray
[14:48] <Tonio_> we don't want this, that's why allee and I wrote kblueplugd
[14:48] <Tonio_> Riddelll: on the long term we should get that done in kbluetooth directly...
[14:48] <Tonio_> Riddelll: I'll ping ifiestas on that point
[14:49] <rgreening> Tonio_: it starts.. with a file open dialog  (for what I don't know) and then the icon appears after I close the dialog
[14:49] <Tonio_> ok
[14:49] <Tonio_> Riddelll: kblueplugs still required :)
[14:49] <rgreening> whats the dialog for?
[14:49] <Tonio_> rgreening: I'll patch kdebluetooth to use the Documents XDG folder by default
[14:49] <rgreening> ah
[14:49] <Tonio_> rgreening: otherwise we'll be prompted on the cd
[14:49] <Tonio_> that's bad :)
[14:49] <rgreening> and the About box doesn't bring up anything
[14:50] <Tonio_> rgreening: and I have no easy way to set this dynamically from within kds
[14:50] <Tonio_> rgreening: yeah it's broken but that's not a big deal for the moment
[14:50] <rgreening> why does it need a folder Tonio_?
[14:50] <Tonio_> rgreening: the obex server, to know where to put the remotelly oploaded files
[14:50] <rgreening> oh
[14:50] <Tonio_> rgreening: it won't ask everytime
[14:51] <rgreening> yeah, pick a sane default...
[14:51] <Tonio_> I would prefer this way (did that before)
[14:51] <rgreening> like Documents...
[14:51] <Tonio_> rgreening: bah XDG should make it I guess
[14:51] <rgreening> otherwise user wont realize why the file dialo is open (It stumped me)
[14:51] <Tonio_> download folder.... I'll write the patch this WE, when I'm back in Paris
[14:51] <rgreening> cool
[14:51] <Tonio_> rgreening: well when you enable the obex server, it opens, and then it makes sense
[14:52] <Tonio_> rgreening: but if obex server is enabled by default, this is confusing, yes
[14:52] <rgreening> basically opening a dialog without explanation is not a good thing :)
[14:52] <rgreening> I clicked my temp dir
[14:52] <Tonio_> another thing I'll do this we is shortcuts unification for tabs in kde apps
[14:52] <rgreening> lo
[14:53] <Tonio_> not changing the default, but provide a list of alternative shortcuts for all apps
[14:53] <Tonio_> that would be firefox compliant
[14:54] <Tonio_> kopete tab switching is a joke... ctrl + ] for next tab.... who can use this ?
[14:54]  * rgreening never knew that short cut :)
[14:54] <Tonio_> bah it's nice to be able to switch within tabs with a standard shortcut
[14:55] <Tonio_> rgreening: I unified this for kde3, but it's still  todo for kde4
[15:19] <Quintasan> Riddell: I'm uploading Dooble to REVU, sorry for the delay but I have serious problem with my connection (uploading from 13, it's 16 here now :/)
[15:20] <Riddelll> Quintasan: ok let me know when it's there and I'll take a look
[15:20] <Quintasan> I'm going out for 2h so I expect it will be uploaded by then
[15:20] <Riddelll> groovy
[15:27] <rgreening> Riddelll: bug 435275 - should the status be wont fix or invalid or ... thoughts
[15:27]  * rgreening went with invalid
[15:27] <Riddelll> rgreening: I beleive upstream is adding that for 0.9.1
[15:28] <Riddelll> rgreening: but yes, invalid is fine
[15:28] <rgreening> Riddelll: yes.. but the current request is asking to add it back in 0.9 as it was missing
[15:28] <rgreening> ok
[15:29] <rgreening> icefox said next wednesday btw for a new release. So, I'll package and test and then let you know so you can upload after beta
[15:29] <rgreening> Riddelll: ^
[15:36] <ScottK> txwikinger_work: I'll be around later tonight.  Offline most/all of today.
[15:36] <txwikinger_work> ScottK: cool.. I worked on the ichthux stuff
[15:37] <txwikinger_work> I will talk to you later then
[15:37] <ScottK> txwikinger_work: OK.  If you have something you need sponsored, I can do that, probably tonight.
[15:37] <txwikinger_work> ScottK: cool
[15:47] <davmor2> ScottK: you might want to make the power switch bigger so it can be seen by those with poorer eyesight ;)
[16:11] <davmor2> ScottK: any idea why NM shows up in utilities as well as internet ans system on KNE
[16:13] <rgreening> agateau: hey. just replied to your post on plasma-devel :)
[16:14] <agateau> rgreening: huhu, going to read it
[16:14] <agateau> I must confess I am a bit afraid of the replies
[16:14] <agateau> especially with the flamewar i started on the powerdevil dialog
[16:14] <rgreening> asiego will be the most vocal
[16:14] <agateau> on kde-core-devel
[16:14] <agateau> I guess so
[16:14] <rgreening> lol
[16:15] <rgreening> I re-enforced you (hopefully)
[16:15] <agateau> thanks!
[16:15] <rgreening> np
[16:15] <agateau> wow,
[16:16] <agateau> you dragged the indicators in this
[16:16] <rgreening> agateau: as hard a time as you get form us, it's only to ensure it works as best as it can... and therefore speaks for itself.. and maybe that will help acceptance with upstream
[16:16] <agateau> more flames!
[16:16] <rgreening> agateau: haha
[16:16] <rgreening> oops
[16:16] <rgreening> :)
[16:16] <rgreening> lol
[16:16] <rgreening> didn't realize that was a no-no
[16:16]  * agateau grabs a thicker bulletproof vest
[16:16]  * rgreening wishes he could retract the post
[16:17] <agateau> no problem,
[16:17] <agateau> will handle this
[16:17] <rgreening> agateau: well, the idea is that this is an "experiment" and not forced on the KDE user.
[16:17] <agateau> yes,
[16:17] <rgreening> agateau: and they shouldn't take issue with experiments.
[16:17] <agateau> I believe I explained this clearly and you reinforced this
[16:17] <rgreening> experiments are meant for learning
[16:18] <rgreening> yep
[16:18] <agateau> hopefully
[16:18] <rgreening> maybe Riddelll will weigh in
[16:18] <rgreening> :P
[16:18]  * rgreening thinks not
[16:18] <rgreening> lol
[16:19] <rgreening> agateau: any progress on the indicator being able to re-hide the window :) or any progress on getting kmail to open?
[16:19]  * rgreening would like akregator support in the indicator too
[16:19] <agateau> i have been a bit side-tracked with powerdevil stuff, but I hope to fix kmail bug this evening,
[16:19] <agateau> or tomorrow morning
[16:19]  * rgreening would like the re-size handle to work too
[16:19] <rgreening> cool
[16:20] <agateau> hehe, don't worry, I noted all your reports
[16:20] <rgreening> :)
[16:20] <rgreening> you are the man
[16:20] <agateau> thanks!
[16:20] <rgreening> agateau: going to UDS?
[16:20] <agateau> rgreening: it's my duty to go :)
[16:20] <agateau> sure will be there
[16:20] <rgreening> cool. karaoke :P
[16:21] <agateau> was thinking the same thing
[16:21] <rgreening> no barbie girl though..
[16:21] <rgreening> haha
[16:21] <agateau> need to train a bit this time :)
[16:21] <rgreening> lol
[16:21] <rgreening> I think we need guitar hero
[16:21]  * rgreening is tempted to bring mime
[16:22]  * rgreening starts practicing with "Ring of Fire" by Johnny Cash
[16:23] <agateau> I am afraid my prefered songs aren't available as karaoke titles
[16:51] <nixternal> hola kubuntu
[16:52] <nixternal> i must say, power devil has been impressive thus far on my laptop...first time I went to battery on this thing in a long time, and the uptime is actually impressive
[16:52] <maco> nixternal: does suspend from it work?
[16:53] <nixternal> I am afraid to test that :)
[16:53] <nixternal> after my debian svn checkout completes I will give it a try
[16:53] <maco> i can only suspend using "sudo pm-suspend --auto-quirks"  if i try to use the kubuntu gui, it just locks the screen without suspending
[16:53] <nixternal> Intel chipset, so I don't see why it wouldn't
[16:53] <maco> so is mine
[16:53] <nixternal> well then
[16:53] <maco> suspend works just fine
[16:53] <maco> but not by pressing the "suspend" button in kde
[16:54] <nixternal> just logged into my linkedin account that I haven't touched ina  while...and accepted you, my first boss from when I got out of the navy, and a bunch of other people
[16:55] <nixternal> ok, let me try this suspend button
[16:55] <nixternal> brb
[16:55] <maco> yeah just got the email
[16:56] <nixternal> 'Suspend to disk' seems to have suspended just fine
[16:56]  * nixternal tries to turn it back on
[16:57] <nixternal> Waking up. Please wait...
[16:57] <nixternal> it's alive! though I don't think it is going to work as it didn't ask for my encryption password
[16:58] <nixternal> whoa, it does work
[17:09] <ScottK> davmor2: Re Bigger.  Talk to Riddelll.
[17:10] <Riddelll> hmm?
[17:10] <davmor2> Riddelll: power button needs to be bigger than it is for those with less than perfect eyesight
[17:10] <Riddelll> which power button?
[17:10] <davmor2> Riddelll: kne
[17:10] <Riddelll> which power button in kne?
[17:11] <maco> nixternal: i was doing suspend to ram
[17:11] <Riddelll> the logout/turnoff applet?
[17:11] <davmor2> Riddelll: both really
[17:11] <davmor2> 4 pixels isn't good for bad eyes honest
[17:11] <Riddelll> no easy answer for that, it needs a patch or something to make it have a horizontal layout option I think
[17:13] <yuriy> is this the lock/logout applet or a different one?
[17:13] <yuriy> that one does adapt to the height it's in
[17:14] <Riddelll> yuriy: that's the problem, the panel is only 16 pixels high so the buttons are only 8 pixels high
[17:14] <Riddelll> which is far too small to see what they are
[17:15] <yuriy> but it should be using the horizontal layout at that height
[17:16] <yuriy> oh nevermind, it doesn't do it. coulda sworn i saw it do that before
[17:16]  * rgreening likes it small like that haha
[17:16] <yuriy> there's definitely a bug about it on b.k.o
[17:20] <davmor2> yuriy, Riddelll, ScottK: http://www.davmor2.co.uk/knedesk.png to give you an idea
[17:21] <ScottK> davmor2: I get the problem, just don't know that to do to solve it.  Honestly I usually just touch the actual power button on my netbook.
[17:21] <davmor2> ScottK: that fine I only added you so we were all on the same page :)
[17:24] <davmor2> Riddell, yuriy: also that image is actually slighty bigger than it is on the screen by about a 1/3
[19:13] <nixternal> maco: suspend to ram just worked as well, as I forgot my lappy was on battery and it kicked in
[19:18] <Quintasan> Riddell: took long enough, up on REVU
[22:10] <yuriy> just saw the pre-kdm splash screen for the first time. wasn't the least bit helpful
[22:11] <yuriy> fun part is without usplash, i see the shell login prompt for several seconds and think something failed badly
[23:24] <neversfelde> I need some help with bug 432775
[23:25] <neversfelde> I do not know, which solution is the best, probably another MIR?
[23:34] <a|wen> oh my, launchpad is really under maintenance now
[23:35] <a|wen> half the buttons disappear on mouse-over ... makes it kind of hard navigating
[23:37] <a|wen> neversfelde: i take that it simply builds against the libepub? and that epub-utils isn't needed for anything in regards to kdegraphics
[23:38] <neversfelde> yes, so leave the binary in universe?
[23:39] <a|wen> i would say so
[23:40] <neversfelde> ok, sounds good, I will test, if okular works with epub files, without ebook-utils installed
[23:44] <a|wen> it should ... it should just depend on libepub0 (automatically from the shlibs expansion) after building againgst libepub-dev
[23:49] <neversfelde> a|wen: thanks
[23:50] <a|wen> yw


[02:34] <pleia2> anyone around who wants to have a go at a couple articles left in the UWN google doc?
[02:34] <pleia2> in "canonical news" and blogosphere
[02:34]  * smartboyhw helps pleia2
[02:34]  * pleia2 works on the remaining planet articles
[02:34] <pleia2> thanks smartboyhw
[02:34] <smartboyhw> You're lucky today, storm kept me in home:P
[02:35] <pleia2> haha
[02:38] <smartboyhw> Otherwise, I'll now be at school. (Probably taking a break)
[02:38] <pleia2> yeah, I thought it was unusual to see you on my sunday evening
[02:47] <pleia2> haha
[02:47] <pleia2> this is #ubuntu-doc!
[02:47] <pleia2> how did this window get in the wrong spot...
[02:48] <smartboyhw> LOL
[02:48] <smartboyhw> Sorry Doc folks:)