[07:28] <Pcfr34k> hello
[07:39] <Pcfr34k> question: has someone tried ubuntu mobile on the Sony Ericsson XPERIA X1?
[07:39] <Pcfr34k> ubuntu mobile is new to me
[07:48] <persia> Pcfr34k, That's a nifty bit of hardware.  Can it boot off SD?
[07:48] <Pcfr34k> 256 MB RAM, 512 MB ROM, Qualcomm MSM7200 528MHz processor
[07:48] <persia> Or is there a hack to overwrite the flash?
[07:48] <Pcfr34k> microsd
[07:49] <persia> I'd expect you'd need to run Jaunty on it, if anything, because there isn't ARM support for any of the released versions.
[07:49] <persia> Mind you, I wouldn't expect the phone functions or FM radio to work.  Probably 20% chance for GPS.
[07:50] <Pcfr34k> i expected that yes
[07:50] <persia> For the GPS/FM Radio, the main issue is drivers.  For phone functions, there's two issues: drivers, and lack of a a software stack for actually dialing a phone.
[07:50] <persia> Otherwise, it ought work a charm.
[07:50] <playya> moin
[07:50] <Pcfr34k> is it possible to sual boot?
[07:50] <persia> Well, probably no accelerated X, but one doesn't really need GL on a device that size :)
[07:50] <Pcfr34k> dual*
[07:51] <persia> There's no reason you can't dual-boot Ubuntu.  I have *no* idea if that device supports dual boot, or how it boots, or anything.
[07:51] <persia> I'd recommend looking for a device-specific forum on dual-booting or booting from SD or reflashing, and once you know what the device can do, look at software.
[07:52] <persia> Based on what I see for other phones, there's probably a good bit of kernel hacking needs doing.
[07:53] <persia> I run Ubuntu on a Sharp D4, but it doesn't work as a phone, the WiFi drivers don't load properly, the power management is a bit wonky, etc.  There's a good bit of base work to get the kernel working, after which the OS is easy.
[07:53] <Pcfr34k> for what i know about the x1 is that is uses the HTC chipset
[07:53] <playya> Pcfr34k, do you know which GSM chip is in there?
[07:53] <Pcfr34k> for the network for calling?
[07:54] <playya> for calling, gprs, ...
[07:55] <Pcfr34k> lokking up...
[08:01] <Pcfr34k> found the whitepaper of the x1
[08:01] <Pcfr34k> http://developer.sonyericsson.com/site/global/docstools/phonespecs/p_phonespecs.jsp
[08:02] <Pcfr34k> loooking op hardware
[08:02] <persia> playya, Are there apps that support that, for some chips?
[08:03] <Pcfr34k> UART2 and USIM
[08:04] <Pcfr34k> GSM and UMTS chips
[08:04] <playya> persia, the fso stack
[08:04] <playya> http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/index.html;hb=HEAD
[08:09] <persia> Hrm.  Looks like good thought, but I'm a little unclear as to whether this provides generic support.  Ideally, I'd like audio to feed into general services (e.g. pulseaudio), and be able to use something like the sl-modem stack also as a backend.
[08:10] <persia> Most of these specs seem to be based on deep-embedded concepts.
[08:11] <playya> this is possible if you provide a alsa state file an chose it in fso.device.autdio
[08:13] <persia> So basically, ALSA or pulse audio interfaces would just be made available to the fso.device.audio implementation?
[08:14] <persia> And I suppose one would just define support for fso.Phone to handle an sl-modem backend.
[08:15] <playya> i never used it. not yet
[08:15] <persia> Still, looks interesting.  I'm mostly looking forward to the day when I don't have to tell people "Yes, it might work on that device, but not as a phone".
[08:17] <playya> http://wiki.openmoko.org/wiki/Neo1973_Audio_Subsystem#Call_recording if this will work you schould also be able to pass this to pulseaudio/gstreamer
[08:18] <playya> argh. wrong articel
[08:18] <playya> harald welte wrote sth about how this works
[08:18] <Pcfr34k> It seems the phone OS "Android" is succesfully ported to the X1
[08:18] <playya> :( FIXME: test this. There's currently a ASoC kernel driver bug preventing audio capture from working at all.
[08:20] <persia> Pcfr34k, If someone was able to boot Android, then there's a way to boot something else.  Next thing to investigate is which kernel flavour you need.  Once you have that, you could try to do something with an Ubuntu rootfs.
[08:20] <persia> Pcfr34k, I'd recommend hunting down for how to get Linux installed on it.  For questions about initial bring-up, #ubuntu-arm might be better.
[08:21] <persia> Once you have at least a CLI Ubuntu system working, installing ubuntu MID becomes relatively easy, and this becomes the right place to talk about issues with the apps, settings, etc.
[08:21] <Pcfr34k> ok, thanks very much
[08:22] <Pcfr34k> i use ubuntu in daily life on i386 and mobile version of linux was unknown to me
[08:22] <Pcfr34k> you guys helped me very much
[08:22] <persia> playya, Interesting.  I suspect we'll end up with an ALSA driver or pulse module at some point (depending on whether it needs to be in kernelspace) which handles that.
[08:23] <persia> Pcfr34k, You might want to try it in a virtual machine (qemu or kvm) first, just to make sure you like the interface before you get too involved in hacking your device.
[08:23] <playya> s/hacking/breaking
[08:24] <Pcfr34k> i tested the netbook packages, or what was it?
[08:24] <playya> have to go now. see you later
[08:24] <Pcfr34k> i like the interface
[08:24] <Pcfr34k> bye bye
[08:24] <Pcfr34k> but im someone who likes it al, or most, working
[08:25] <Pcfr34k> im using the Acer Aspire One, is UMPC good for that?
[08:26] <Pcfr34k> im using it now with Ubuntu i386
[08:28] <persia> Pcfr34k, Depends on how cramped you feel.  If you want the one-app-at-a-time experience, I'd say yes.  If not, I'd say no.
[08:29] <Pcfr34k> i stick to the ubuntu desktop then
[08:29] <persia> Pcfr34k, That said, it's just a matter of apt-get install ubuntu-mobile to find out (I think).  Pay attention to what gets installed, because if you don't like it, that's what you'll need to purge.
[08:29] <Pcfr34k> thank for the info
[08:30] <Pcfr34k> im out
[08:30] <Pcfr34k> bye bye
[10:14]  * ogra carefully pokes the datacenter
[10:14] <ogra> is it only me ?
[10:17] <ogra> hrm, looks like a routing prob at my provider :/
[10:20] <persia> Then it's you and a few thousand other people.  It's not me.
[10:20] <ogra> yeah, seems a router is borked
[10:20] <ogra> but  better now
[10:21]  * ogra always needs a moment to remember the new traceroute is called tracepath
[11:56] <persia> Team meeting in 5 minutes in #ubuntu-meeting
[11:58] <playya> may i join too?
[11:58]  * Hobbsee holds up the "community! community! community!" flag
[11:58] <persia> playya, Certainly.  It's open to anyone.
[11:59] <playya> ok. when i'm at home. last lesson !!
[11:59] <persia> playya, There's still a couple minutes to get something on the agenda, if you want to add it to https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090122
[11:59] <persia> (of course, you'd be expected to discuss the topic)
[11:59] <ogra> we'll chase you down if you dont ! :P
[12:00] <playya> bye
[12:00] <ogra> heh
[12:00] <ogra> run playya run
[13:05] <persia> ogra, Regarding Mer & moblin2 : I wouldn't expect significant clashes, because of the levels at which each group works.  If Moblin2 contains stuff derived from newer Maemo userspace, it would probably already include the Mer patches having been pushed through Maemo.
[13:05] <persia> If Moblin2 doesn't contain that stuff, then it's just different software libraries, and there's no impact at all.
[13:05] <ogra> well, moblin merges hildon and clutter
[13:05] <ogra> on a lib level ... at least as i undrestood it
[13:06] <persia> As a new library, or with lots of deep patches?
[13:06] <ogra> maemo might work differently on that layer
[13:06] <ogra> no idea, but i know they have different approaches on the lib level
[13:06] <persia> Or just an abstract "framework"?
[13:07] <ogra> but lool knows more, i know he took an actual look at moblin2
[13:07] <ogra> i can only talk about heresay
[13:07] <persia> And tends to hang out on #maemo where most of the Mer discussion happens :)
[13:07] <persia> I think I'll poke him for review of the spec once I get it drafted then.
[13:07] <ogra> that comment was totally based on assumption and lack of detailed knowledge
[13:08] <ogra> yeah, having lool take a look definately makes most sense


[11:27] <mamarley> ricotz: Hey, is there any reason why 415.13 hasn't been copied to the main PPA yet?
[14:16] <ricotz> mamarley, sorry, I wanted to run it first, but didn't got to it yet :(
[14:16] <mamarley> OK
[14:16] <ricotz> if you feel comfortable then copy it
[14:17] <mamarley> It works fine on my system and soee also tried it.  It also isn't like anyone will get automatically upgraded since it is a new major release, so I will go ahead and copy it.
[14:18] <mamarley> Oops, dang, wrong PPA.  Just a sec…
[14:20] <mamarley> Fixed.  Sorry, please ignore the build failures.


[01:24] <ScottK> maco: Because 1010 10 = 42.
[04:21] <maco> ScottK: but....that was last year
[04:21] <ScottK> Yes, but last year's schedule was cargo culted to this year.
[04:22] <ScottK> And at UDS when I tried to get it fixed, I was told it was too late.
[04:23] <maco> is final freeze in effect now too?
[04:42] <ScottK> Yep.
[04:42] <ScottK> For Main/Seeded stuff.
[04:43] <ScottK> Of course release team members can give exceptions.
[08:50] <bambee> morning
[08:59] <allee> bambee: hi, sorry. Read your comments right now.  I wasn't aware of the deadline, but I really had to leave.
[09:00] <allee> bambee cyphermox ScottK: the patch made vpnc work here again.  http://www.mpe.mpg.de/~ach/tmp/nm-plasmiod-fix-vpnc.diff
[09:00] <allee> whoever applies it please remove the ~test1 from version string and add to changelog:
[09:01] <allee> Thx a log to cyphermox bambee and ScottK for their help.
[09:01] <allee> ^^ don't be shy. please add it ;)
[09:01] <allee> s/log/lot/
[09:01] <kubotu> allee: You did something wrong... Try s/you/me/ or tell me "help sed"
[09:05] <bambee> allee: looks good
[09:05] <bambee> ScottK: can you approve this package ?
[09:14] <allee> FWIW: I had go to it's setup and save again. In the configfile was '2' and after the save 'dh2' .  In natty this value is not in the config file so a natty -> oneiric update is not affected
[09:16] <Riddell> grr, google calendar thinks rekonq is a mobile browser
[09:17] <fabo> Riddell: you might knwo :) how can I request a package rebuild, no changes needed?
[09:18] <Riddell> fabo: upload it with no changes
[09:18] <Riddell> I think there's a script somewhere to help that
[09:19] <Riddell> but I can't find it
[09:19] <Riddell> fabo: what's needing done?
[09:20] <fabo> Riddell: kile bug 772631
[09:21] <Riddell> fabo: well I can upload that but I'm unsure on the state of the freezes
[09:21] <allee> cyphermox, bambee: I found another problem ;)  For a new user that didn't use WLAN yet, I've now 2 times the same wlan ssid listed.  ( I use same SSID at two locations.)   lucid, ... natty didn't list them twice.   Upstream has a fix already AFAIR, but maybe it's better to ping lamarque to do a release together 4.7.2 and get all fixes instead of (endless?) cherry picking .
[09:22] <fabo> Riddell: ok, please try. otherwise, it could be fixed in oneiric-updates?
[09:38] <bambee> allee: you should poke the maintainer about this bug, I don't find the commit :\
[09:49] <allee> bambee: I keep it on my TODO list.  First I build a pkg with all patches.
[09:53] <allee> bambee: when you walked through upstream git log, did you have the impression that the all the changes would be okay to go into oneiric-updates like 4.7.2?
[09:58] <bambee> Only important fixes should go to oneiric-updates, imo. Like crashes fixes, rendering bugs, connections bugs etc... <-- also some of these commits fix bugs introduced by earlier commits, after our snapshot. We should only fix bugs found with our snapshot.
[09:59] <bambee> since there are no releases or tags... it does not help :\
[10:03] <bambee> Riddell: for the next cycle, if you want to improve your french you should go to #kde-fr :D
[10:03] <Riddell> ah oui
[10:04] <bambee> hehe ;)
[10:04] <Riddell> kile 1:2.1.0-1build1 (Waiting for approval)
[10:08] <allee> bambee: okay.
[10:31] <ScottK> bambee: I'll accept it, but someone else needs to upload it.
[10:32] <Riddell> fabo: kile 1:2.1.0-1build1 (Accepted)
[10:32] <ScottK> I just accepted another Qt upload, so if there's other stuff to go in, now's a good time.
[10:33] <fabo> Riddell: thanks!
[10:39] <ScottK> Riddell: Would you be around to approve an akonadi upload shortly?  I'm going to move us to the head of the 1.6 branch for more bug fixes.  For Akonadi/Kdepim we need all we can get.
[10:39] <Riddell> ScottK: sure
[10:39] <ScottK> Great.
[10:39] <Riddell> ScottK: does upstream approve?
[10:39] <ScottK> I think so.
[10:39] <ScottK> I honestly lost track.
[10:48] <ScottK> That and the current released state of akonadi/pim is such complete crap I doubt I'd trust their opinion much either way.
[11:01] <ScottK> Riddell: Uploaded.
[11:05] <allee> ScottK: as blogged trueg does nepomuk bug fixing at the moment.  Maybe it's worth that someone (shadeslayer?) has a look at nepomuk 4.7.* branch
[11:06] <ScottK> Certainly.
[11:06] <ScottK> Although unlike kmail, I've never gotten nepomuk to do anything useful for me, so personally, I think it's less critical.
[11:07] <Riddell> I'm using nepomuk quite a bit now for file searches
[11:07] <Riddell> I expect if I used kmail I'd use it for e-mail searches too
[11:10] <ScottK> I didn't manage to get it to work at all, but it admittedly hasn't been a priority.
[11:10] <ScottK> It's only recently I had a laptop that it was feasible to have it enabled.
[11:13] <allee> what an accident or not: we talked about nepomuk and now no kde app starts anymore.   I get soprano error msg :(
[11:21] <keffie_jayx> guys after upgrading a machine from 11.04 to 11.10, kontact won't start.
[11:22] <keffie_jayx> it starts but kmail doesn't seem to be configured properly with akonadi
[11:22] <keffie_jayx> Failed to fetch the resource collection
[11:23] <keffie_jayx> the migration did not give me any errors though
[11:27] <keffie_jayx> anyone had that same issue, I am unsure wether to report this as a bug...
[11:51] <shadeslayer> phew
[11:51] <shadeslayer> finally, interwebz is back
[11:58] <shadeslayer> ScottK: did you upload akonadi already? I looked at the 1.6 branch yesterday, seemed they pushed in a couple of bug fixes
[12:01] <shadeslayer> keffie_jayx: yeah, iirc ejat had the same issue
[12:01] <shadeslayer> but that was on unity
[12:15] <keffie_jayx> shadeslayer: nop, kde 4.7.1
[12:15] <keffie_jayx> desktop-plasma
[12:15] <keffie_jayx> shadeslayer: I failed to see a bug report, Should I file a bug in the KDE Bugzilla?
[12:16] <keffie_jayx> I believe there is a bug filed somewhere else and there is a workaround for this but It didn't work for me
[12:16] <shadeslayer> keffie_jayx: wait a day or two, ScottK is going to upload a new akonadi that might solve your issue
[12:16] <keffie_jayx> cool
[12:28] <ryanakca> Would everybody kindly give the new wiki theme a spin? Select kubuntu-light from the dropdown menu on https://wiki.kubuntu.org/Home?action=userprefs&sub=prefs
[12:32] <ScottK> shadeslayer: I did.
[12:32] <shadeslayer> cool
[12:32] <shadeslayer> keffie_jayx: ^ please test if updates fix your issue
[12:33] <ScottK> It's not accepted yet.
[12:33] <keffie_jayx> ok
[12:33] <keffie_jayx> There is a dependency issue today
[12:33] <ScottK> I'd ask claydoh if he's seen that issue and if he has any recommendations.
[12:33] <keffie_jayx> lib32asound2 : Depends: libasound2 (= <IP_ADDRESS>-0ubuntu9)
[12:35] <ScottK> Archive skew.  Just wait a bit.
[12:35] <allee> ryanakca: wiki.kubuntu.org gives Internal server error
[12:35] <allee> :)
[12:36] <shadeslayer> it's still saving stuff for me
[12:36] <ryanakca> allee: Oh no. Try refreshing.
[12:36]  * shadeslayer hits save again
[12:37] <ScottK> I get it too.
[12:37] <ScottK> (Internal server error)
[12:38] <ryanakca> Oh, I do too
[12:38] <shadeslayer> wohoo, works for me
[12:38] <shadeslayer> took some time to save, but works
[12:39] <shadeslayer> the wiki now fits my desktop xD
[12:39] <ryanakca> Works here too now.
[12:41] <ryanakca> allee: What URL were you after, just http://wiki.kubuntu.org/ ?
[12:41] <allee> ryanakca: yes.  And now works again
[12:43] <allee> ryanakca: FWIW: take me some time to find logout (I search it upper right  not in between the menu items
[12:44] <allee> ryanakca: I've a bigger default font in firefox.  Now the 'More Action' menu uses a bigger fond compared to the items on the left and right. the font even looks boldface
[12:45] <shadeslayer> ryanakca++
[12:46] <ryanakca> shadeslayer: Thanks, but newz2000++ mostly, I just switch around a few colours ;)
[12:46] <shadeslayer> well, you got it deployed, so thats no mean feat as well
[12:48] <allee> ryanakca: other than that: really nice layout!   Looks really fresh and, well, light ;)
[13:31] <ScottK> ryanakca: Looks very nice.
[15:31] <allee> agateau: reports due to globalmenu, go they bugs.kde  or to launchpad.   E.g. konsole: remove 'Show menu'  when globalmenu is active.  a) does not work, b) makes no sense.     Similar for rekonqs pseudo menu button in upper right corner:  Not needed with globalmenu.
[16:14]  * yofel hugs ryanakca for the wiki theme
[16:31] <dpm> debfx, all digikam and kipiplugins are now disabled in Launchpad
[18:46] <debfx> dpm: thanks!
[19:04] <dpm> debfx, no worries, thank you for the heads up :)
[19:15] <DarkwingDuck> jjesse: ping
[19:47] <yofel> fabo: kile is still broken
[19:52] <jjesse> DarkwingDuck pong
[19:52] <DarkwingDuck> jjesse: translated PO files have been merged to lp:kubuntu-docs and we just need to translate them with the translation script.
[19:53] <jjesse> ok
[19:53] <DarkwingDuck> jjesse: I have not tried the modified script yet.
[20:01] <DarkwingDuck> apachelogger: Hey mate, do you think a meeting prior to UDS to talk about what we want to meet about at UDS would be a good idea still?
[20:01] <apachelogger> meetings are always a good idea
[20:01] <apachelogger> if there are things to talk about
[20:02] <DarkwingDuck> apachelogger: Well, I remember from orlando last year that we were adding on lots of session at the last minute.
[20:03] <apachelogger> certainly not as many as in budapest
[20:04] <apachelogger> 50000 editions of the packaging blueprint ^^
[20:04] <DarkwingDuck> So, maybe coming to UDS with a better idea/plan might take some of that stress out of the equasion.
[20:05] <DarkwingDuck> Although, the fact that "P
[20:05] <DarkwingDuck> "P" will be a LTS.. that might help *some*
[20:05] <apachelogger> it might be a LTS
[20:05] <DarkwingDuck> might?
[20:05] <apachelogger> well, there is no official statement that it will
[20:06] <apachelogger> so until then I'd refrain from saying it will be LTS :P
[20:06] <apachelogger> anywho
[20:06] <DarkwingDuck> :P:P
[20:06] <apachelogger> DarkwingDuck: if people were adding ideas and whatnot to the wiki page that would certainly help with preperatin
[20:06] <DarkwingDuck> Aye, it would.
[20:07] <DarkwingDuck> Speaking of... I actually need to toss a few things on there.
[20:08] <DarkwingDuck> apachelogger: you have that link handy?
[20:24] <ScottK> apachelogger: There is an official statement from like two years ago.
[22:18] <fabo> yofel: that's really strange... I rebuilt the package and installed locally and it works for me...
[22:19] <yofel> it is a weird issue, if you read the full report you'll see that it was broken for me, then worked, then broke again
[22:19] <yofel> and I'm utterly clueless what's the problem
[22:19] <fabo> imo kile is out of the root cause
[22:20] <fabo> I still have the working package that I built
[22:20]  * yofel takes another attempt at finding the symbol table code
[22:22] <fabo> well, to be honest, I made a signle changes but it isn't supposed to affect the package...
[22:22] <fabo> I added a debug package, expecting to debug the issue ;)
[22:30]  * yofel wonders how to turn KILE_DEBUG() on
[22:33] <yofel> oh, fun: #define KILE_DEBUG kDebug
[22:58] <fabo> yofel: rebuilt again, worksforme. 1build1 doesn't work.
[22:58] <yofel> can you built kile from git and tell me what you get here with kdebugdialog for kile on?
[22:58] <yofel> kile(25447) KileWidget::SymbolView::mousePressEvent: math is  false , bracket is  false  and item->data(Qt::UserRole).toString() is  "6%%%%%%/usr/share/kde4/apps/kile/mathsymbols/arrows/img018arrows.png"
[22:58] <yofel> because that string with the % is wrong
[22:59] <yofel> should look about like this:
[22:59] <yofel> <1%\neq%≠%[utf8x,,]{inputenc,ucs,}%[fleqn,]{amsmath,}%This command gives nice weather!%/home/kdedev/.kde4/share/apps/kile/mathsymbols/user/img002math.png
[23:00] <apachelogger> %/%/%/%/%/%/%/|\%\%\%\%\%\%\%\|/%/%/%/%/%/%
[23:01] <apachelogger> latex people have a fetish for percents really
[23:01] <yofel> according to the spec that's too many %'s
[23:01] <yofel> :P
[23:01] <fabo> :)
[23:01] <yofel> oh fun, the key generation debug stuff is off
[23:01]  * yofel uncomments and rebuilds
[23:02] <apachelogger> / %% debug() %% //
[23:02] <apachelogger> oh IRC ate a forwards slash :(
[23:02] <yofel> ok, now to find out why image.text("Command"); returns an empty string
[23:02]  * apachelogger waves fist
[23:09]  * ScottK waves
[23:10] <yofel> uh........
[23:10]  * ScottK packages pimlibs/pim/pim-runtime snapshots again.
[23:11] <yofel> do the images get modified somehow?
[23:11] <yofel> /usr/share/kde4/apps/kile/mathsymbols/arrows/img001arrows.png !=
[23:11] <yofel> kile-2.1.0/src/data/symbols-ng/arrows/img001arrows.png
[23:11] <yofel> the whole metadata is missing
[23:11] <yofel> and thus breaks kile
[23:12] <yofel> fabo: fun bug ^
[23:13] <fabo> yep
[23:27] <yofel> *SIGH*
[23:27] <yofel> the archive buildds run optipng on the images -.-
[23:32] <apachelogger> I love it how stuff that messes with data is not optin but optout
[23:32] <apachelogger> total win
[23:33] <yofel> found the fix
[23:33] <yofel> export NO_PNG_PKG_MANGLE=1 in debian/rules
[23:34] <apachelogger> point proven
[23:34] <yofel> indeed
[23:35] <fabo> sigh
[23:36] <yofel> ScottK: can we get that into the archive *somehow* ? or will that have to wait for oneiric-updates ?
[23:36] <fabo> it was indeed buildd related
[23:36] <yofel> fabo: that explains why the PPA package worked
[23:36] <ScottK> I'll push for it to get in.
[23:36] <yofel> *and* the local builds
[23:36] <fabo> and my rebuild
[23:44] <yofel> apachelogger: can you upload this? http://people.ubuntu.com/~yofel/kile_2.1.0-1ubuntu1.debdiff
[23:44] <apachelogger> not at this time of day
[23:45] <yofel> you're the only one present that has upload rights for universe and isn't called scott -.-
[23:46] <apachelogger> great
[23:47] <apachelogger> dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address
[23:47] <apachelogger> all hail the bogus patches
[23:47] <yofel> oooops
[23:47] <yofel> I forgot this was synced in the meantime -.-
[23:47] <yofel> sorry
[23:48] <apachelogger> I am wondering
[23:48] <apachelogger> shouldn't the version be build1ubuntu1?
[23:49] <yofel> uh, don't we only use 'build' if we have no ubuntu changes and need a rebuild?
[23:50] <apachelogger> why yes
[23:50] <apachelogger> BUT
[23:50] <apachelogger> it is build from debian
[23:50] <apachelogger> and ontop of build1 we stuff our ubuntu changes
[23:51] <apachelogger> ScottK: opinion please?
[23:51]  * apachelogger wants to go to bed :/
[23:51] <ScottK> Drop the build.
[23:51] <apachelogger> kk
[23:51] <ScottK> Make it ubuntu1
[23:52] <apachelogger>   Uploading kile_2.1.0-1ubuntu1_source.changes: done.
[23:52] <apachelogger> Successfully uploaded packages.
[23:52] <yofel_> uh, no?
[23:52] <apachelogger> nini
[23:52] <yofel> build1 is from today/yesterday
[23:52] <yofel> gn
[23:52]  * yofel hugs apachelogger
[23:59] <ryanakca> So, any objections to turning kubuntu-light on as default wiki theme?


[02:07] <highvoltage> jbicha: btw, thanks a lot for taking care of https://bugs.launchpad.net/ubuntu/+source/gcompris/+bug/914137
[02:12] <jbicha> highvoltage: no problem, I got it into Debian too :)
[02:13] <jbicha> gcompris's too massive to really test but I figure it hopefully fixes more bugs than it causes
[02:32] <highvoltage> jbicha: yeah and getting it in early at least gave some chance for people to test it a bit (hopefully some people who are really familiar with it :))
[02:33] <highvoltage> jbicha: it's probably not to late to blog about it and call for testing on the edubuntu blog, is it?
[02:49] <jbicha> highvoltage: it looks like there's several fixes in git.gnome.org , maybe ask Bruno if he'll do another release soon
[21:32] <sheenzz> ah the educational os from linux that inspirer to leave my windsow os =
[21:36] <highvoltage> :)
[21:37] <sheenzz> i only wise the age range would be a little higher
[21:38] <highvoltage> that's a common request, we've started to include some more university level software like melting and lightspeed. we might include things like fritzing too in the future
[21:39] <highvoltage> (bbl)
[21:40] <sheenzz> yes i think they should have a edubuntu for any age group as a main learning os for persons in general =)
[21:44] <sheenzz> brb


[02:41] <InHisName> Does this cover q on fixing java installs to be better ?
[15:24] <biehl> hello - is there a list of junior jobs somewhere ? Eg. a list of programs that are probably easy to package, but haven't been packaged yet.
[15:38] <persia> Well, there's *heaps* of stuff that hasn't been packaged.
[15:39] <persia> Generally, we try to get new stuff packaged in Debian, and sync it.
[15:39] <persia> I'll see if there's a wishlist collected somewhere.
[15:42] <persia> biehl, http://wiki.debian.org/Java/RequestedPackages has a list of requests, of which some are already claimed.  Feel free to ask here, or in #debian-java on OFTC if you need help.
[16:34] <biehl> nice, I'll have a look
[20:12] <|aspire|> hello
[20:13] <|aspire|> I have an import problem
[20:13] <|aspire|> my basic java libs are not available
[20:14] <|aspire|> sorry ignore that
[20:30] <|aspire|> hi is any one here at all???
[20:30] <persia> Lots of people.  Most tend to ide a lot.
[20:34] <|aspire|> ok
[20:34] <|aspire|> I'm looking for a way to use this function
[20:34] <|aspire|> createImage((int)screen_w, (int)screen_h)
[20:35] <|aspire|> any suggestion for which lib I may need?
[20:35] <|aspire|> /
[20:35] <|aspire|> or is this a function that is only applicable with an applet???
[20:44] <|aspire|> is there an alternative function that I can use instead of createImage such that I can use this code in a regular java app rather than with an applet
[23:10] <|aspire|> hello
[23:15] <Nicke_> |aspire|: while not very ubuntu related, take a look at the BufferedImage class for example
[23:16] <|aspire|> yes I have checked the java doc
[23:16] <Nicke_> (also, java.awt.Toolkit can come handy when used to the methods provided by Applet)
[23:16] <|aspire|> http://java.sun.com/j2se/1.4.2/docs/api/java/awt/Component.html#createImage(int, int)
[23:17] <|aspire|> that is right and I have tried that, however what I am looking for is a way to use this method or any alternative such that I can use this code in a regular java app
[23:17] <|aspire|> any suggestions Nicke_?
[23:18] <Nicke_> |aspire|: Either use the one provided by Component if you have such a object at hand.. otherwise create a new BufferedImage
[23:19] <Nicke_> not it was some time ago I did work with Swing, so I have no better answers
[23:19] <Nicke_> now it*
[23:20] <|aspire|> hold on, I have some fundamental knowledge of programming with java, but I need a bit more on this
[23:20] <|aspire|> can you explain your suggestion?
[23:21] <|aspire|> is it correct that you are suggesting me to use the java swing class rather than the awt?
[23:21] <|aspire|> Nicke_: ???
[23:22] <Nicke_> no, was just saying that it was some time ago I  used swing (and awt).
[23:23] <|aspire|> so you are not sure how I could solve this or are not sure how to explain it
[23:23] <Nicke_> well, I think BufferedImage will do what you want
[23:23] <Nicke_> but I can't provide any more detailed answer than that
[23:24] <|aspire|> ok, I could try that, in which class could I locate it?
[23:25] <Nicke_> BufferedImage is a class :) (java.awt.BufferedImage)
[23:26] <Nicke_> java.awt.image.BufferedImage even.. oops
[23:26] <Nicke_> I suppose Google might have some examples on how to use it
[23:27] <|aspire|> yes looking for it
[23:27] <|aspire|> but my IDE does not find the BufferedImage class
[23:27] <|aspire|> import java.awt.Image.BufferedImage;
[23:28] <Nicke_> change Image to image
[23:28] <|aspire|> import java.awt.Image.BufferedImage; being underlined with a red line
[23:29] <|aspire|> that is better
[23:29] <|aspire|> but still
[23:29] <|aspire|> java.awt.image.BufferedImage((int)screen_w, (int)screen_h);
[23:29] <|aspire|> can't find the class
[23:30] <|aspire|> complaining that it cant find the image class
[23:30] <|aspire|> how starge
[23:30] <|aspire|> strange
[23:40] <|aspire|> Nicke_: are you still there?


[22:53] <starbrdtak> hello
[22:53] <starbrdtak> i have a compilation issue with this code
[22:53] <starbrdtak> http://pastebin.com/5jx5PKtc
[22:54] <starbrdtak>  javac crawl.java -cp .
[22:54] <starbrdtak> crawl.java:13: cannot find symbol
[22:54] <starbrdtak> can anyone help please


[16:12] <OvenWerks> anyone who is interested in adding the right way to set ubuntu to performance to our docs, I just put it in #ubuntustudio.
[16:13] <OvenWerks> this method works, does not get reset by upgrades, does not interfere with upgrades.
[16:13] <OvenWerks> two steps:
[16:13] <OvenWerks> sudo /usr/sbin/update-rc.d ondemand disable
[16:14] <OvenWerks> create a file  /etc/default/cpufrequtils with the line  GOVERNOR="performance" in it.
[16:14] <OvenWerks> using what other tutorials tell you will:
[16:15] <OvenWerks> a) switch you to performance only to have the system switch you back 60 seconds later.
[16:15] <OvenWerks> b) vanish in the next software upgrade or give an error in the next upgrade.


[00:05] <bluesabre> I'd like to announce tomorrow's meeting, but the Ubuntu Wiki won't login without timing out
[00:10] <bluesabre> There we go
[00:14] <bluesabre> ochosi: got any items for the meeting to add to the agenda?
[00:15] <bluesabre> Probably going to add a few things tonight
[00:15] <ochosi> hmm
[00:15] <ochosi> well there's the find-cursor thing you know about
[00:15] <ochosi> that i would really like to push in
[00:15] <ochosi> via a new settings release
[00:15] <ochosi> or if not in time for FF, we could put it in as a patch and i then do a release a little later and we get that in more easily afer FF
[00:22] <bluesabre> ochosi: once you get it ready, I'll merge and release
[00:23] <ochosi> almost there
[00:23] <bluesabre> great
[00:23] <ochosi> just some small fixes for the non-composited version missing
[00:23] <ochosi> feel free to test
[00:23] <bluesabre> I'll probably try to merge in some other recent fixes from 4.13 too
[00:23] <bluesabre> have a good night!
[00:23] <ochosi> yup
[00:23] <ochosi> you too!
[02:46] <bluesabre> Updated the meeting wiki page with latest updates I'm familiar with
[02:50] <Unit193> Got the recent uploads?
[14:26] <knome> flocculant, ta :)
[18:40] <pleia2> dev.xubuntu.org is hard to reach at the moment, known issue https://status.linode.com/
[18:56] <pleia2> (seems to be better now)
[22:40] <bluesabre> evening all
[22:40] <flocculant> hi bluesabre
[22:40] <bluesabre> !team | Xubuntu Community Meeting in 20 minutes
[22:41] <bluesabre> hi flocculant
[22:41] <flocculant> good day?
[22:42] <bluesabre> that's currently up in the air
[22:42] <bluesabre> may need to leave the meeting early
[22:42] <flocculant> oh dear
[22:43] <bluesabre> flocculant: refreshed my manifest diff for today's iso https://wiki.bluesabre.org/bionic_changes
[22:44] <flocculant> that's a handy list
[22:45] <bluesabre> :)
[22:45] <bluesabre> once I figure out how to nicely automate that (and improve on dokuwiki's poor table sorting) that page should stay up to date
[22:46] <flocculant> not sure what the crack is with bug 1644917 - ochosi believes it's long fixed ... it's not ;) just one of those visual things but ...
[22:47] <flocculant> right - that'd be even handier :p
[22:47] <bluesabre> The other day I saw it actually show the label correctly, and then didn't
[22:47] <flocculant> I've not seen it
[22:47] <Unit193> http://archive.unit193.net/debian/bionic/xfce4-indicator-plugin_2.3.3-1vanir1_amd64.deb you could try that.
[22:48] <flocculant> ever tbh - one of those things I don't do so wouldn't, but now I look every time I see that bug
[22:48] <flocculant> ugh
[22:49] <flocculant> gdebi just silently fails now apparently
[22:49] <bluesabre> that's pleasant
[22:49] <flocculant> bluesabre: yea - but ubuntu don't care about it I guess
[22:52] <flocculant> Unit193: yea - that one doesn't even give me to option to cancel or whatever is under the invisible label - it just went right ahead and cleared them :D
[22:53] <Unit193> That's Bionic+a few commits
[22:54] <flocculant> well one of the commits makes it jfdi then :D
[22:57] <Unit193>     - Make sure the "clear indicators" dialog works with libxfce4ui-4.13.x
[22:59] <flocculant> :)
[23:00] <pleia2> o/
[23:01] <bluesabre> Alrighty!
[23:01] <bluesabre> #startmeeting Xubuntu Community Meeting
[23:01] <meetingology> Meeting started Fri Feb 23 23:01:39 2018 UTC.  The chair is bluesabre. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[23:01] <meetingology> Available commands: action commands idea info link nick
[23:01] <bluesabre> !team | Meeeeeeting time :)
[23:02] <bluesabre> Who's around?
[23:02] <pleia2> o/
[23:02] <flocculant> yup
[23:02] <bluesabre> yay
[23:02] <slickymaster> o/
[23:02] <bluesabre> :D
[23:03] <bluesabre> We'll let the others roll in for a few
[23:03] <flocculant> hopeful then :p
[23:03] <bluesabre> I try to be
[23:03] <flocculant> I used to be like that
[23:04] <slickymaster> lol
[23:04] <bluesabre> That and I was wrapping up dinner
[23:05] <flocculant> ha ha
[23:05] <bluesabre> Now we'll start
[23:05] <bluesabre> #topic Open action items
[23:05] <slickymaster> that almost sounded as if you made a burrito out of your dinner bluesabre
[23:05] <bluesabre> slickymaster: not a bad idea
[23:05] <bluesabre> #done bluesabre and ochosi to get on with it and include xfpm 1.6
[23:05] <bluesabre> (thanks Unit193)
[23:06] <flocculant> :)
[23:06] <bluesabre> #info postponed for bionic+1: bluesabre to reach out to pidgin devs regarding system themes
[23:07] <bluesabre> Fairly certain that
[23:07] <bluesabre> #done flocculant to mail list(s) re 17.04 EOL and draft blog post
[23:07] <bluesabre> happened
[23:07] <flocculant> ye
[23:07] <bluesabre> #topic Updates and Announcements
[23:07] <bluesabre> #info Xubuntu Wallpaper Contest Open
[23:08] <pleia2> #link https://xubuntu.org/news/xubuntu-18-04-community-wallpaper-contest/
[23:08] <bluesabre> nice
[23:08] <bluesabre> #info Xubuntu 18.04 Default Wallpaper Uploaded
[23:08] <bluesabre> (looks fancy)
[23:08] <pleia2> need some submissions that aren't flowers :)
[23:08] <bluesabre> Or more flowers
[23:08] <bluesabre> and rocks
[23:08] <bluesabre> (ochosi)
[23:09] <genii> Are most of them photos so far?
[23:09] <pleia2> yeah
[23:09] <pleia2> (submissions are public)
[23:09] <bluesabre> https://contest.xubuntu.org/wallpaper_contest/xubuntu-18-04-community-wallpaper-contest/?action=view
[23:09] <flocculant> thought the rock one was the same as one from that site he liked last time
[23:09] <bluesabre> not sure
[23:10] <pleia2> there was a request on social media for more original art ones, not just photos
[23:10] <genii> I tried to do a watercolour thing in Gimp but it looks more like a blurry ball of rainbows
[23:11] <Unit193> Tell them we'd gladly accept such contribution?
[23:12] <pleia2> Unit193: "patches welcome" is not as friendly as you think it is ;)
[23:12] <bluesabre> #info lots of package updates since the beginning of bionic, a few recent ones: greybird-gtk-theme 3.22.6, xubuntu-icon-theme 18.04.1, catfish 1.4.4, lightdm-gtk-greeter 2.0.4, menulibre 2.1.5, xfce4-notifyd 0.4.1, xfce4-power-manager 1.6.1
[23:12] <bluesabre> pleia2: yes, every time I say that I don't get patches
[23:12] <bluesabre> :)
[23:12] <Unit193> That's because it's a polite brush off. :P
[23:12] <bluesabre> Woops
[23:13] <bluesabre> Any other updates/announcements?
[23:14] <bluesabre> Yes there are actually...
[23:14] <bluesabre> #info March 1: Feature Freeze, Debian Import Freeze
[23:15] <bluesabre> #info March 8: Beta 1
[23:15] <bluesabre> Pretty sure we are participating in that
[23:15] <flocculant> that's on my list of things to rabbit about
[23:15] <flocculant> as is 16.04.4
[23:15] <flocculant> next week ...
[23:16] <flocculant> which is why I'd not added them to the announcement bit :p
[23:16] <bluesabre> Good point
[23:16] <flocculant> :)
[23:17] <bluesabre> Let's hop on over to that then
[23:17] <bluesabre> #topic Discussion
[23:17] <bluesabre> (get it, hop?)
[23:17] <bluesabre> Sorry
[23:17] <flocculant> :)
[23:17] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 18.04 - i386 - i386 built.
[23:18] <bluesabre> Do we want to talk blueprints or general first?
[23:18] <flocculant> don't mind - depending on time - up at stupid o'clock tomorrow :(
[23:18] <bluesabre> :(
[23:19] <bluesabre> Blueprints first then, shouldn't take long
[23:19] <bluesabre> #subtopic Blueprints
[23:19] <bluesabre> https://dev.xubuntu.org/
[23:19] <bluesabre> We're looking a little rough this cycle
[23:19]  * flocculant wanders off for a bit as no qa bp \o/
[23:20] <flocculant> bluesabre: looks much the same as it did for the last cycle ;)
[23:20] <bluesabre> But there's probably more done than it appears
[23:20] <bluesabre> In fact, there definitely are
[23:20] <bluesabre> I need to update a few things
[23:21] <bluesabre> So if everybody just wants to poke around and refresh your BPs so we can target release day a bit better... ;)
[23:22] <bluesabre> I realize now that's not really a good discussion item
[23:23] <flocculant> :D
[23:23] <bluesabre> flocculant: your turn to #subtopic and rabbit
[23:23] <bluesabre> #chair flocculant
[23:23] <meetingology> Current chairs: bluesabre flocculant
[23:23] <bluesabre> #chair pleia2
[23:23] <meetingology> Current chairs: bluesabre flocculant pleia2
[23:23] <bluesabre> #chair slickymaster
[23:23] <meetingology> Current chairs: bluesabre flocculant pleia2 slickymaster
[23:23] <flocculant> bluesabre: did you not want to libinput?
[23:23] <bluesabre> flocculant: decided it's not something to worry about for this cycle
[23:24] <flocculant> ok
[23:24] <bluesabre> we'll probably have to go for it on bionic+1 so I think they are removing -synaptics
[23:24] <flocculant> #subtopic 16.04.4 / Beta 1 18.04
[23:24] <flocculant> this is just forewarning everyone - with job I have now I can't guarantee marking for release
[23:25] <flocculant> also not got much time to be testing each and every version and the tests
[23:26] <flocculant> I suspect 16.04 is more or less just install smoketests
[23:26] <flocculant> #subtopic numlockx
[23:26] <flocculant> bug 1746556
[23:27] <flocculant> someone else apparently gets annoyed at having to do this each time they install, so that's at least 2 of us ...
[23:27] <flocculant> thoughts on adding that and setting up the lightdm doodah to have it at login?
[23:28] <bluesabre> That seems reasonable to me
[23:28] <slickymaster> +1
[23:28] <bluesabre> !info numlockx bionic
[23:28] <bluesabre> That also seems agreeable
[23:28] <flocculant> though I tend to make my one a lot further on than 50-numlock.conf just in case :p
[23:29] <flocculant> yea not very big at all :p
[23:29] <bluesabre> flocculant: so you currently use this in your config?
[23:29] <flocculant> yup
[23:29] <bluesabre> neat
[23:29] <bluesabre> Sounds incredibly painless
[23:29] <flocculant> have done for years as it never works without
[23:29] <flocculant> yea - just a pita the first time :D
[23:31] <bluesabre> Will probably go ahead with that then, it seems like a value add and nothing more
[23:31] <bluesabre> thanks for bringing it up
[23:31] <flocculant> bluesabre: only time it went wrong was when lightdm changed and you needed the [Seat} bit
[23:31] <flocculant> no problem
[23:31]  * flocculant is done then
[23:31] <bluesabre> Anybody else got discussion items?
[23:32] <flocculant> I'm - as always - concerned about the testing levels we 'apparently' get
[23:32] <bluesabre> Yeah
[23:33] <flocculant> but bored by the discussion now tbf - as is everyone else I expect
[23:33] <bluesabre> #link http://iso.qa.ubuntu.com/
[23:33] <flocculant> #subtopic Testing
[23:33] <flocculant> then
[23:33] <bluesabre> to get some fresh views on that at least
[23:33] <bluesabre> :D
[23:33] <bluesabre> yay
[23:33] <Unit193> It's really just the install media though, I activly run Bionic.
[23:33] <flocculant> not sure what we can do about it though
[23:33] <flocculant> Unit193: I know :)
[23:34] <bluesabre> hi Unit193
[23:34] <flocculant> trouble is - unless someone actively tells us we have no idea at all
[23:34] <flocculant> and frankly someone could just go to the tracker on release day and mark it for release
[23:36] <flocculant> bluesabre: not sure we'll ever get fresh views from the few of us in a meeting
[23:36] <flocculant> because I'd have to assume we all want it done
[23:37] <Unit193> There's still that one guy that emails me about Core ISOs, but that's unofficial stuff still.
[23:37] <flocculant> yup
[23:37] <bluesabre> flocculant: let's plan for a call for testing and social media'ing everywhere
[23:37] <flocculant> I'm sure there are people out there - I see pings from the u+1 channel
[23:38] <flocculant> bluesabre: mmm
[23:38] <flocculant> bored doing those pointlessly as well
[23:40] <bluesabre> maybe a nice detailed blog post instead
[23:40] <bluesabre> happy to coordinate on that
[23:40] <flocculant> ok
[23:41] <bluesabre> pleia2, knome_: sound good to you?
[23:41] <pleia2> yep
[23:41] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 18.04 - amd64 - amd64 built.
[23:41] <flocculant> bluesabre: let me know when's good for you - but I need to afk now
[23:41] <bluesabre> #action flocculant and bluesabre to publish testing blogpost
[23:41] <meetingology> ACTION: flocculant and bluesabre to publish testing blogpost
[23:42] <bluesabre> flocculant: we can follow up when you're next available :)
[23:42] <bluesabre> thanks for hanging around for the meeting
[23:42] <flocculant> over weekend - later tomorrow, most of Sunday - evenings after 1900 utc
[23:43] <flocculant> no problem - night all :)
[23:43] <slickymaster> nighty night flocculant
[23:43] <bluesabre> anybody else got anything to discuss?
[23:43] <slickymaster> nothing here
[23:47] <bluesabre> pleia2 Unit193?
[23:47] <pleia2> nope, I'm good
[23:48] <Unit193> I hope not, but if there is I'll just give you repeated pokes.
[23:48] <bluesabre> Sounds... painful
[23:48] <bluesabre> #topic Schedule next meeting
[23:49] <bluesabre> !info knome is next on the list, but if anybody wants to schedule one, go for it
[23:49] <bluesabre> er
[23:49] <bluesabre> #info knome is next on the list, but if anybody wants to schedule one, go for it
[23:49] <bluesabre> #endmeeting
[23:49] <meetingology> Meeting ended Fri Feb 23 23:49:50 2018 UTC.
[23:49] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2018/xubuntu-devel.2018-02-23-23.01.moin.txt
[23:49] <bluesabre> Thanks everybody!
[23:50] <slickymaster> thanks bluesabre
[23:50] <Unit193> Sorry all about the build notifications, I started them before the meeting and only realized it was going to interrupt the meeting.
[23:51] <bluesabre> Unit193: no problem here, glad to see SwissBot alive and well
[23:51] <pleia2> hehe
[23:52] <Unit193> bluesabre: It doesn't ever stop in another channel, announcing all NEW packages in Debian. :3
[23:55] <bluesabre> shew
[23:55] <bluesabre> minutes are up
[23:56] <Unit193> Soo...Every time testing comes up, the tracker is brought up.  I always think "But I'm actually running it day to day, doesn't that count?"
[23:59] <bluesabre> knome_: "Fix Released" doesn't seem to change anything on the tracker for bugs https://dev.xubuntu.org