[02:27] <OvenWerks> mistaken ideas...
[02:47] <Jessedavid4> Hey is there a way to reset Studio controls? I tried to change some settings and seemed to lost audio.
[02:51] <OvenWerks> I think that feedback bit 0 needs to be set up to 5.12 (strip buttons) 6 will be separate (bit 13)
[02:52] <OvenWerks> Jessedavid4: which settings did you change?
[02:52] <OvenWerks> Jessedavid4: and lost audio from which application?
[02:53] <Jessedavid4> Well, lost audio from everything.
[02:54] <OvenWerks> Jessedavid4: start by choosing Stop Jack
[02:54] <Jessedavid4> I tried to change the Sample rate from 48 to 192. Honestly I thought my mobo has 192 support, but could be wrong. Anyways, I changed it back to 48 and have no audio anymore.
[02:54] <OvenWerks> why would anyone want 192? Pet bats?
[02:55] <Jessedavid4> Lol. Wanted to see if I noticed a difference in my music.
[02:55] <Jessedavid4> Like spotify's "high quality" streaming.
[02:55] <OvenWerks> anything higher than 48K will tend to introduce distortion in  the sound
[02:55] <OvenWerks> and noise
[02:56] <OvenWerks> anyway try stop jack in -controls and see if you have audio again
[02:56] <Jessedavid4> Yeah, but if the support is there. Ideally it should be better, no?
[02:56] <OvenWerks> no
[02:56] <OvenWerks> its called advertizing hype
[02:57] <Jessedavid4> Ooh? So where does 192 matter then? And it seems to have not fixed it.
[02:57] <OvenWerks> A good video on the subject: https://www.xiph.org/video/vid2.shtml
[02:58] <Jessedavid4> Oh wait, lol. It works on that link.
[02:58] <OvenWerks> he uses real analog scopes and signals.
[02:58] <OvenWerks> so desktop audio now works
[02:58] <Jessedavid4> Huh. That was weird. But it works again.
[02:59] <Jessedavid4> Yeah I thought I tried stop Jack to and then start/restart jack.
[03:00] <Jessedavid4> You know, come to think of it. I tried to use Spotify each time I tried to stop or reset. And I had to completely close it down for it to fix it.
[03:01] <Jessedavid4> This video actually looks super good. (picture wise)
[03:02] <OvenWerks> Monty is a codec designer for both audio and video
[03:03] <Jessedavid4> Honestly, if he wanted to. He could put youtube out of business lol
[03:03] <Jessedavid4> This is 720p on my 1080p monitor. I mean this is really really good.
[03:25] <paul_k_0123> I am using 16.04.5 and want to upgrade to the latest LTS (18.10.x). It looks like I have package problems that are hard to trace. Do logs exist?
[03:26] <paul_k_0123> I have had aptd crash on me numerous times for reasons that seem related to this, but, again, information is not in the usual places (like /var/log)
[04:12] <paul_k_0123> Output from an upgrading effort is at: https://paste.ubuntu.com/p/M3GwSdzjXW/
[05:58] <JEV_> Hi, i've been using this link: https://help.ubuntu.com/community/UbuntuStudio/ProAudioIntro
[05:59] <JEV_> I followed all the steps and guitarix is able to read my guitar input
[06:00] <JEV_> but the only thing left is my laptop doesn't produce any sound
[06:00] <JEV_> i'm currently using usb guitar cable as an input
[06:07] <Eickmeyer> JEV_: 16.04, 18.04, or 18.10?
[06:14] <JEV_> 18.10
[06:14] <Eickmeyer> Then ignore that Wiki article.
[06:14] <Eickmeyer> Use Ubuntu Studio Controls to start Jack, then any USB audio device should be automatically detected.
[06:14] <Eickmeyer> It's exponentially easier.
[06:15] <Eickmeyer> We have a lot of work to do on documentation, and that entire article can easily be replaced with a new article about Ubuntu Studio Controls.
[06:15] <JEV_> ah i see
[06:16] <JEV_> let me try it first
[06:17] <Eickmeyer> Use patchage to connect your guitar to guitarix, and then the output from guitarix to your laptop speakers.
[06:19] <JEV_> in Ubuntu Studio Controls, should i change anything?
[06:20] <Eickmeyer> Only if you want to change the master audio device or some other stuff to lower the latency. Buffers and periods per buffer can be explained best here: https://wiki.linuxaudio.org/wiki/list_of_jack_frame_period_settings_ideal_for_usb_interface
[06:21] <Eickmeyer> You're going to want 3 periods.
[06:21] <Eickmeyer> For Guitarix, read the very bottom paragraph, it's important.
[06:24] <JEV_> and about the patchage...
[06:25] <Eickmeyer> It's an app installed by default. It's buggy, so we're working on packaging a replacement.
[06:25] <Eickmeyer> Development on it has ceased.
[06:26] <JEV_> are guitarix output and my laptop speakers named PulseAudio JACK Source and system respectively?
[06:26] <Eickmeyer> No. Your laptop speakers are most likely system, and your USB-1/4" input likely has its own label.
[06:27] <Eickmeyer> PulseAudio Jack Source sends audio internally to PulseAudio, for non-JACK aware apps.
[06:40] <JEV_> in patchage, there re only gx_head_amp, gx_head_fx, system (Both capture and playback) and 2 Midi Trough
[06:42] <JEV_> I re-open everything and there are no more PulseAudio Jack Source nd Sink
[06:43] <JEV_> I'm new to linux... everything seems really hard
[06:43] <Eickmeyer> Don't worry about PulseAudio, you don't need it for guitarix.
[06:43] <Eickmeyer> gx_* is guitarix. system capture is your input, system playback is your output.
[06:44] <JEV_> yes, system playback_1 for the system playback
[06:44] <Eickmeyer> I have never used Guitarix myself, mut I can only imagine you'd connect your input to your fx and fx to your amp and then amp to system, but that's just based on my live audio engineering background.
[06:47] <JEV_> in my patchage from system -> amp -> fx -> system
[06:49] <JEV_> what are those 2 Midi Through blocks use for?
[06:49] <Eickmeyer> Those would be for MIDI controllers or keyboards or the like.
[06:49] <Eickmeyer> Safe to ignore.
[06:49] <JEV_> because 2 of them aren't connected to everything
[06:49] <JEV_> oh i see
[06:49] <Eickmeyer> You mentioned that your guitar is connected via USB?
[06:50] <JEV_> yes, usb cable... but the block is not exist since i open guitarix
[06:51] <Eickmeyer> Unplug your USB cable and plug it back in. It should show up in Patchage.
[06:51] <Eickmeyer> Of course, that's assuming you started Jack using Ubuntu Studio Controls and not elsewhere.
[06:52] <Eickmeyer> BTW, Guitarix needs to be started -after- starting Jack.
[06:56] <Jessedavid4> I read some documentation saying that using an AUX cable tends to work better than most anything for Guitarix.
[06:57] <Jessedavid4> Recommended to use a 3.5mm over a USB. Though you should still see the same results irregardless.
[06:58] <JEV_> I restart everything, unplug the usb
[06:58] <JEV_> how can I show you my patchage screenshot?
[06:58] <JEV_> there are another stange blocks appear
[06:59] <Eickmeyer> Well, you could always screencap it and send it to imgur, but I honestly need to be heading to bed, it's getting late here.
[07:00] <JEV_> okay, thank you. I'll figure it myself
[07:00] <Eickmeyer> Best thing I can tell you is to not be afraid to experiment.
[07:00] <Eickmeyer> I hope I've at least pointed you in the right direction.
[07:00] <JEV_> I think i just need a little more step, thanks for guiding me
[07:00] <Eickmeyer> You're welcome.
[07:03] <JEV_> if you're not sleeping yet... it's working!!
[19:01] <dave_> Hi - quick question I hope. I installed 14.04 and have upgraded to 16.04. I want themes but can't find out how to dertermine what my environment is - Gnome or Unity? Which environment if 16.04 please?
[19:01] <dave_> *is 16.04?
[19:03] <dave_> That's 32 bit btw
[19:05] <OvenWerks> If you have ubuntustudio it is xfce
[19:06] <OvenWerks> So neither gnome or unity
[19:07] <dave_> That works - thanks so much!
[19:07] <OvenWerks> no problem


[06:53] <RootChaos> morning all, i'm having a tuff time picking up new LUNs on Ubuntu 18.04 - Using the rescan-scsi-bus -a --largelun -w -c -d command is not picking up any new LUNs assigned to the host from the storage controller - I'm not sure what to try next... Hoping someone here might have some ideas?


[11:35] <tonyyarusso> @schedule toronto
[11:36] <tonyyarusso> okay....
[11:36] <Ubugtu> Schedule for America/Toronto: 30 Nov 16:00: Ubuntu Development Team | 06 Dec 15:00: Edubuntu | 07 Dec 03:00: Ubuntu Development Team | 13 Dec 07:00: Edubuntu | 14 Dec 11:00: Ubuntu Development Team | 20 Dec 15:00: Edubuntu
[11:36] <tonyyarusso> Oh, it's just slow
[11:37] <Hobbsee> @schedule sydney
[11:37] <Ubugtu> Schedule for Australia/Sydney: 01 Dec 08:00: Ubuntu Development Team | 07 Dec 07:00: Edubuntu | 07 Dec 19:00: Ubuntu Development Team | 13 Dec 23:00: Edubuntu | 15 Dec 03:00: Ubuntu Development Team | 21 Dec 07:00: Edubuntu
[09:50] <mdz> good day
[09:50] <dholbach> good evening :)
[09:50] <BenC> good afternoon
[09:50] <kylem> good coffee
[09:51] <fabbione> hmm nicotine...
[09:51] <fabbione> #include <linux/crack/nicotine.h>
[09:51] <fabbione> int main() {
[09:51] <fabbione>   inject();
[09:51] <fabbione>  exit 666;
[09:51] <fabbione> }
[09:51] <mdz> Syntax error near `exit'
[09:52] <zul> afternoon
[09:52] <BenC> not to mention including kernel headers from user space
[09:52] <BenC> for shame
[09:53] <cjwatson> mdz: disturbingly that implies you have such a header
[09:53] <ajmitch> hi
[09:54] <kylem> BenC, hehe.
[09:54] <seb128> mdz: pong ;)
[09:59] <fabbione> mdz: what would you expect after inject() :P
[10:01] <mdz> we're missing a few people but need to get started
[10:01] <heno> mdz: pong
[10:01] <mdz> welcome all
[10:01] <mdz> heno: you're up first
[10:02] <heno> * Approved: access-gdm, braille-support, color-filters, common-at-conf, orca-laptop-support
[10:02] <heno> * Drafting: multilingual-speech -- this will be taken forward by Gilles Casse from Oralux. I've also created orca-espeak as a prerequisite to this.
[10:02] <heno> feisty-speakup -- Depends on involvement from the speakup community. The next week or so will tell.
[10:02] <heno> * Abandoned: atspi-testing-by-default -- seb128 had issues with this and I see his point.
[10:02] <heno> (not sure about the format today)
[10:02] <cjwatson> atspi-testing-by-default> yeah, I wasn't all that keen either
[10:02] <cjwatson> (sorry etc.)
[10:02] <Simira> mdz: Tollef's here in five mins or so
[10:02] <heno> yeah, I can see why
[10:03] <mdz> heno: apart from atspi-*, are those targeted for feisty?
[10:03] <mdz> Simira: thanks
[10:03] <mdz> hmm, no
[10:03] <heno> oh, I don't think so. Need to look at how LP does that
[10:04] <mdz> heno: ok, please see that the ones which should be on the roadmap are targeted.  the link is labeled 'set release goal' I think
[10:04] <heno> I'll do that now, thanks
[10:04] <mdz> heno: are there assignees for all of those?
[10:05] <heno> all except the feisty speakup one
[10:05] <heno> which is still uncertain
[10:05] <heno> I'm assignee for most of them
[10:05] <mdz> ok; if you can find someone who will aim for feisty, then go ahead and target it, otherwise leave it off
[10:05] <cjwatson> ("Propose as goal"
[10:05] <cjwatson> )
[10:06] <heno> right
[10:06] <mdz> heno: thanks
[10:06] <mdz> fabbione: next
[10:06] <fabbione> feisty-toolchain (approved): fixed a couple of minor glibc things.
[10:06] <fabbione> sparc64-installer (approved): not started. Waiting Herd 1 to settle before starting on it.
[10:06] <fabbione> spart64-niagara-ssl-accelerator (approved): wrote down some pseudo code and read a few times the hw specs to understand how it is supposed to work. This should be object of real coding during sparc sprint in Seattle.
[10:06] <fabbione> integrity-check (approved): fixed the infrastructure to go https://. waiting Herd 1 and d-i merge before moving it in main/cd.
[10:06] <fabbione> ubuntu-feisty-ha-cluster (approved): extremely good progress here. Received even emails from IBM India that confused us as upstream. OCFS2 has been updated and needs testing. GFS1 has been updated to the new FS API but it's not working properly (needs fixing). GFS2 has been updated and it's working almost ok. It fixes a bunch of problems from edgy but it seems i am still one of the few that can crash it :)
[10:06] <fabbione> sparc64-64bit-apps and sparc64-desktop: left to the community. no progress.
[10:06] <fabbione> Done
[10:06] <fabbione>  * SRU for lvm2 completed.
[10:06] <fabbione>  * working on SRU for mdadm in edgy (almost ready).
[10:06] <mdz> fabbione: what are the dates for the sprint again?
[10:06] <cjwatson> fabbione: d-i merge is done
[10:07] <fabbione> mdz: one sec...
[10:07] <fabbione> mdz: 16 -> 23 Dec.
[10:07] <mdz> ok
[10:07] <fabbione> cjwatson: yes i saw it but it was too late today to start :)
[10:07] <cjwatson> right, just saying you aren't waiting for it any more :-)
[10:07] <cjwatson> got to defend my honour etc.
[10:07] <fabbione> mdz: 16 is fly out so nothing will happen other than sitting 12 hours on a plane ;)
[10:08] <fabbione> cjwatson: your honour is untouchable d-i god
[10:08] <mdz> what could be more fun?
[10:08] <mdz> fabbione: how does sparc look for herd 1?
[10:08] <fabbione> mdz: sex?
[10:08] <fabbione> mdz: i am running it on both my machines
[10:08] <mdz> fabbione: I mean installability
[10:08] <fabbione> mdz: i only need to test the installer tomorrow
[10:08] <cjwatson> sparc d-i FTBFS
[10:08] <cjwatson> I have a fix in hand
[10:08] <cjwatson> I'll upload it soonish so fabio can test
[10:08] <fabbione> mdz: i think it's blocked on d-i :P
[10:09] <cjwatson> (but Mithrandir had said he didn't care so I was skipping it in favour of more urgent things)
[10:09] <mdz> ok, we'll get a full herd 1 update from Mithrandir a bit later
[10:09] <mdz> fabbione: thanks
[10:09] <mdz> dholbach: next
[10:09] <dholbach> Done:
[10:09] <dholbach>  * merges
[10:09] <dholbach>  * started bug mailbox cleaning *whine*
[10:09] <dholbach>  * gnome updates
[10:09] <dholbach> Todo:
[10:09] <dholbach>  * implement top prio art builder goals
[10:10] <dholbach>  * more bug cleaning
[10:10] <dholbach>  * GNOME 2.17.3
[10:10] <dholbach>  * more merging
[10:10] <dholbach> Specs:
[10:10] <dholbach>  * art-builder-improvements: approved, started.
[10:10] <dholbach>  * feisty-telepathy: approved, started: landell and telepathy-wilde still need packaging.
[10:10] <dholbach>  * code-review: pending approval, needs one TB sign-off.
[10:10] <dholbach>  * motu: pending approval, needs one TB sign-off.
[10:10] <dholbach>
[10:10] <mdz> dholbach: is the art team actively using the art-builder repo now?
[10:10] <dholbach> mdz: no, they're not - Troy mailed on how to use bzr and I gave some instructions.
[10:11] <mdz> dholbach: please set me as approver on those TB specs so that I get email; I'll give them a second pass
[10:11] <dholbach> ok - thank you
[10:11] <mdz> dholbach: is there a wiki page for them which explains how to use it?
[10:11] <dholbach> mdz: no not yet, I'll do that.
[10:12] <dholbach> mdz: (done, set the approver of the specs)
[10:12] <mdz> ok
[10:12] <mdz> thanks dholbach
[10:12] <mdz> kylem: next
[10:12] <kylem> done:
[10:12] <kylem>  * ubuntu-dapper-security.git: up to date with kernel-sec svn
[10:12] <kylem>  * ubuntu-edgy-security.git: up to date with kernel-sec svn
[10:12] <kylem>  * ubuntu-{dapper,edgy}-updates.git: enable bnx2 in nic-modules
[10:12] <kylem>  * backported squashfs patch for dapper-security.git
[10:12] <kylem>  * backported ocfs2 patches for dapper-security.git
[10:12] <kylem>  * backported sky2 v1.9 for edgy-updates.git for #68338
[10:12] <kylem>  * fixed up hdaps for edgy-updates.git
[10:12] <kylem>  * looked into msi implications for #73815
[10:12] <kylem>  * trawled stable trees for patches
[10:12] <kylem>  * debugged why i can't push to rookery
[10:13] <kylem> todo:
[10:13] <kylem>  * get the 4 trees uploaded
[10:13] <kylem>  * look into getting git updated so i can push to rookery
[10:13] <fabbione> kylem: we will need ocfs2 also in edgy
[10:13] <Mithrandir> (pong)
[10:13] <kylem> fabbione, it's fixed in edgy, but i didn't have to do any work just apply it. in dapper i had to make sure it still worked because i had to hand apply.
[10:14] <fabbione> kylem: ah ok
[10:14] <fabbione> thanks
[10:14] <kylem> np
[10:14] <mdz> kylem: you're all set up with the access you need to do your work now, yes?
[10:14] <kylem> mdz, yup
[10:15] <mdz> kylem: ok, thanks
[10:15] <mdz> BenC: next
[10:15] <cjwatson> kylem: is bnx2 urgent? if so we need a d-i update
[10:15] <BenC> driver-device-manager: Approved, work in progress.
[10:15] <BenC> driver-backports: Pending Approval (just finished this last minute spec this morning).
[10:15] <BenC> Kernel work this past week:
[10:15] <BenC> * Lowlatency kernel/lrm added. Joy to the world.
[10:15] <BenC> * 2.6.19 released, our tree is moving on with 2.6.20 as planned.
[10:15] <BenC> * Merged some ubuntu kernel patches upstream.
[10:15] <BenC> Kernel work for next week:
[10:15] <BenC> * Initial 2.6.20 patches rolling into upstream. Will get out a new kernel based on this ASAP.
[10:15] <BenC> * Moving all linux-source-2.6.19 lp bugs to linux-source-2.6.20 after this upload. All traces of 2.6.19 will disappear.
[10:15] <BenC> * Revamp of the kernel-team git repository to enable better security patch handling (embargoed patches, etc), and better collaboration between myself and Kyle.
[10:15] <cjwatson> well, er, maybe, depending on the installation method
[10:15] <kylem> cjwatson, well, i'm sure elmo would appreciate it. :)
[10:15] <cjwatson> kylem: check with me tomorrow?
[10:16] <mdz> BenC: I'll have a look at driver-backports after the meeting
[10:16] <zul> heh dont forget me in the kernel-team git repository ;)
[10:17] <BenC> zul: likely it will be on a canonical machine, so might not get that
[10:17] <mdz> BenC: any kernel blockers for herd 1?
[10:17] <BenC> mdz: No, kernel is uploaded and stable for herd-1
[10:17] <mdz> and d-i up to date with it?
[10:17] <BenC> lrm and linux-meta synced as well
[10:17] <BenC> cjwatson: ^^
[10:17] <cjwatson> mdz: yes
[10:18] <cjwatson> done today
[10:18] <mdz> ok, thanks BenC
[10:18] <BenC> we have a few udeb quirks to work out, but colin says herd-1 is good
[10:18] <kylem> cjwatson, https://bugs.launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/73647 <- bnx2.
[10:18] <Ubugtu> Malone bug 73647 in linux-source-2.6.17 "Broadcom NetXtreme II BCM5708 not detected on install" [Undecided,Fix committed]
[10:18] <mdz> mvo: next
[10:18] <mvo> Did:
[10:18] <mvo> - specs
[10:18] <mvo> - merges
[10:18] <mvo> - work on the auto-dist-upgrade testing (better control scipt, most-of-main install profile
[10:18] <mvo> - release-upgrader for edgy->feisty uploaded
[10:18] <mvo> - prototype/experiments for apt mirror method
[10:18] <mvo> - SRU xorg uploaded to edgy-updates
[10:18] <mvo> Will do:
[10:18] <cjwatson> BenC: well, it builds anyway - haven't *tested* yet
[10:18] <mvo> - merges
[10:18] <mvo> - LSB face-to-face meeting berlin
[10:18] <mvo> Feisty specs approved:
[10:18] <mvo> - auto-dist-upgrade-testing, binary-driver-education, common-customizations, dist-upgrader-fixes, enabling-additional-components,   dynamic-mirror-decisions,   server-upgrade-tool, apt-sha256
[10:19] <mdz> mvo: auto-dist-upgrade-testisg doesn't seem to be targeted?
[10:19] <mdz> please target it to feisty
[10:19] <mvo> mdz: oh, I fix that
[10:20] <mdz> mvo: is the dist-upgrader ready for herd 1 testing?
[10:20] <mvo> mdz: yes, it should be fine
[10:21] <mdz> mvo: so we can include update-manager instructions in the announcement and start real world upgrade testing?
[10:21] <mvo> mdz: yes, I can update the announcement in the wiki
[10:21] <mdz> ok, great
[10:21] <mdz> thanks mvo
[10:21] <mdz> Mithrandir: next
[10:21] <Mithrandir> network-roaming: not started; will have to read up on this again, it seems to have changed a bit from the bof discussion
[10:21] <Mithrandir> changelog-closes-bugs: not started
[10:21] <Mithrandir> misc: herd 1 fixing, getting there slowly
[10:21] <Mithrandir> next week: herd 1 release, get changelog-closes-bugs done
[10:21] <Mithrandir> herd 1: getting there, was blocked on d-i stuff and some bits of cdimage not being updated to know that feisty is current.  I'll roll CDs and test them tomorrow.  Bug status isn't too good, I've tried to chase people up about the "later"-targetted bugs, but not being too successful about this.  Ideas for making this happen better welcome
[10:23] <cjwatson> IME "later" has been entirely snowed under by merges and getting the world working at all
[10:23] <seb128> Mithrandir: when you say "next week", that's tomorrow? ;)
[10:23] <cjwatson> I think first milestone may have been a bit ambitious for "later"
[10:23] <mdz> cjwatson: agreed
[10:23] <Mithrandir> seb128: next week is what happens from today until next distro team meeting.
[10:23] <mdz> we should figure a realistic date for closing them, but it should be soon
[10:23] <cjwatson> although obviously ambitious targets mean we're more likely to hit the realistic targets
[10:23] <Mithrandir> cjwatson: I've intentionally not chased you down due to you being ideal in too many places already.
[10:24] <mdz> Mithrandir: perhaps mail -devel-announce with a summary of 'later' in concert with herd 1 and aim for herd 2
[10:24] <Mithrandir> mdz: I'll do that.
[10:24] <mdz> Mithrandir: do you have a date for herd 2?
[10:25] <Mithrandir> mdz: hmm, I thought we put those on the release schedule, but apparently not.  I'll find some dates.
[10:25] <mdz> I thought so too, but they didn't make it into the version on the wiki
[10:25] <Mithrandir> dec 14th might work
[10:26] <mdz> I think we said every 2-3 weeks?
[10:26] <Mithrandir> yeah, but I'm on xmas vac from the 19th, and I suspect bits of the rest of the team will be starting their vacation that week too
[10:26] <mdz> at any rate, yes, please add milestone dates to the schedule
[10:26] <Mithrandir> I'll do that.
[10:26] <mdz> Mithrandir: please make notes about the edgy->feisty bits of cdimage etc. and add them to the checklist
[10:27] <Mithrandir> ReleaseProcess?
[10:27] <cjwatson> I think they're already there (just DIST=feisty)
[10:27] <cjwatson> but we'll check
[10:27] <mdz> Mithrandir: perhaps a new page linked from there, for opening a new release
[10:27] <cjwatson> hmm, no, perhaps not
[10:27] <cjwatson> I should probably write that; I know the guts of it
[10:27] <mdz> or on the page itself, I'm not fussed so long as they're not forgotten at the end of the  previous release
[10:27] <mdz> cjwatson: please do
[10:28] <mdz> thanks Mithrandir
[10:28] <Mithrandir> ok, I'll do the skeleton, Colin did most of the meat of it this time around so he should fill it in.
[10:28] <mdz> seb128: next
[10:28] <seb128> Done:
[10:28] <seb128>  * merges with Debian
[10:28] <seb128>  * GNOME updates
[10:28] <seb128>  * DesktopTeam talk for Ubuntu OpenWeek
[10:28] <seb128>  * catching up with mails
[10:28] <seb128>  * a bunch of edgy-proposed and edgy-updates updates
[10:28] <seb128>  * bug triage, bug triage, bug triage
[10:28] <seb128> .
[10:28] <seb128> To Do:
[10:28] <seb128>  * keep merges with Debian
[10:28] <seb128>  * bug triage, bug triage, bug triage, bug triage, you got the idea by now :p
[10:28] <seb128>  * GNOME 2.17.3
[10:28] <seb128>  * get tracker uploaded
[10:28] <seb128>  * updated desktop team
[10:28] <seb128> .
[10:28] <seb128> Specs:
[10:28] <seb128>  * easy-codec-installation: approved, waiting on gstreamer upstream changes
[10:28] <seb128>  * tab-consistency: pending approval, not started
[10:28] <seb128>  * desktop-slab: review, that's a "small" spec, basically getting promotion for the gnome-main-menu package and maybe looking at a panel profiles switcher
[10:28] <seb128> "updated desktop team" = "update wiki for desktop team"
[10:28] <mdz> seb128: I'm not keeping up with so many SRUs
[10:29] <cjwatson> I'm trying to do them about weekly, so tomorrow is the next round
[10:29] <seb128> mdz: you only have to approve them
[10:29] <seb128> think how much work it takes me filling them :p
[10:29] <mdz> seb128: I need to read and understand them first :-)
[10:29] <ogra> only ...
[10:29] <seb128> mdz: most of mine are fairly easy patches though ;)
[10:29] <mdz> seb128: we should only be doing these for critical issues, since they create work for others
[10:30] <mdz> I would like to do them for trivial fixes as well, but in reality it may not be worth it
[10:30] <seb128> right, I've adjusted for that
[10:30] <cjwatson> seb's have been pretty good in that regard from what I've seen
[10:30] <seb128> we got some not so cool bugs to edgy though due to the short cycle and the flood of bugs we didn't manage very well before edgy
[10:30] <cjwatson> they've all been "oh god, we released with that?" to one extent or another
[10:30] <mdz> it looks like it from the ones I've read, but as I said, I'm behind
[10:31] <mdz> cjwatson: I'd like for you to take primary responsibility for those for now; perhaps you and pitti can discuss sharing it
[10:31] <seb128> I should probably not have done the "libgnomeprintui has 2 strings not translatable", I noticed today, it's not worth the work
[10:31] <cjwatson> mdz: ok
[10:31] <mdz> it's not realistic for me at present
[10:31] <seb128> but that was in the pipe before I really think about it
[10:31] <cjwatson> I would like people to put more effort into writing descriptions of bug impacts
[10:31] <cjwatson> (for SRUs)
[10:32] <cjwatson> I've had several where that wasn't really there and I had to go back and distill one
[10:32] <mdz> does that need more emphasis in the documentation?
[10:32] <seb128> cjwatson: what sort of description?
[10:32] <mdz> it was explicitly part of the process
[10:32] <cjwatson> seb128: how the bug affects users. see the wiki page
[10:32] <mdz> to describe the impact of the bug on users, justifying the update
[10:32] <mdz> "this bug causes babies to be eaten"
[10:32] <dholbach> or 250 duplicates in gnome bugzilla (and counting)
[10:33] <mdz> right
[10:33] <seb128> cjwatson: I've read the wiki page, I'm not sure if you want "what the bug is doing" or "how many people it's annoying"
[10:33] <cjwatson> maybe just send out another reminder or something - I'll see what irritates me tomorrow
[10:33] <seb128> dholbach: I actually did some of those
[10:33] <seb128> "upstream has over 100 dups and asked us to push the crash fix"
[10:33] <cjwatson> seb128: I'd prefer its effect on end users; the latter doesn't hurt but the former is what we need to justify ourselves in the event that something goes wrong
[10:33] <mdz> seb128: both; "this bug causes foo to crash for many users"
[10:33] <dholbach> seb128: I know
[10:33] <cjwatson> "we chose to do this because ..."
[10:33] <seb128> cjwatson, mdz: ok, noted
[10:33] <mdz> it's not only for the benefit of the SRU team but to remind you to think about whether the work of an update is justified before you go further
[10:34] <mdz> seb128: we need to take a decision regarding beagle/tracker
[10:34] <mdz> seb128: what is upstream doing?
[10:34] <seb128> mdz: nothing
[10:34] <mdz> neither is going to be part of gnome?
[10:34] <seb128> beagle has not been proposed
[10:35] <seb128> and tracker will not be accepted since it has not being deployed by any distro yet and they are not sure about it neither
[10:35] <seb128> no, GNOME is pretty conservative
[10:35] <mdz> seb128: have CCed you on followup re: gstreamer
[10:36] <sfllaw> Can we update the SRU policy to get people to put this stuff in the Description?
[10:36] <seb128> ok
[10:36] <sfllaw> Reading long strings of comments is amusing, but inefficient.
[10:36] <mdz> sfllaw: that's fine with me
[10:36] <sfllaw> Especially for you.
[10:36] <cjwatson> sfllaw: please go ahead
[10:36] <seb128> mdz: why do we need to decide now for beagle or tracker, feature freeze is not good?
[10:37] <seb128> did you read my reply to your mail?
[10:37] <mdz> seb128: do you expect things to become clearer before then?
[10:37] <mdz> seb128: I did, but haven't replied yet
[10:37] <seb128> yes
[10:37] <cjwatson> sfllaw: that also makes it easier for users of stable releases to look up the bug and figure out why we changed it, which is a significant part of the point of the process too
[10:37] <mdz> it sounded indecisive :-)
[10:37] <seb128> I'm in contact with tracker upstream
[10:37] <seb128> and I think we will get tracker uploaded next week
[10:37] <seb128> I can't speak for tracker before getting user feedback on it
[10:37] <seb128> it looks a better choice on the paper
[10:37] <mdz> seb128: is it possible to use both in parallel?
[10:37] <seb128> C, smaller, extra features, good community
[10:38] <seb128> no
[10:38] <mdz> jdub said there was some discussion on desktop-devel-list
[10:38] <seb128> tracker has been proposed for GNOME 2.18
[10:38] <seb128> it's not likely to be accepted though
[10:38] <seb128> and beagle has not been proposed
[10:38] <mdz> ok, well the first step is to get them both in so that they can be tested, then send an announcement to -devel-announce to ask for testing and start a discussion about which works better for users
[10:39] <seb128> yeah that was my plan
[10:39] <mdz> will you do that?
[10:39] <mdz> ok ,thanks
[10:39] <seb128> yep, I'm on it
[10:39] <seb128> np
[10:39] <mdz> no word from doko?
[10:39] <mdz> (he was next)
[10:39] <mvo> I have tried to call him today without success
[10:39] <mvo> got the mailbox only on his mobile
[10:39] <mdz> mvo: will you try him tomorrow also?  I hope he is OK
[10:39] <mvo> mdz: yes
[10:40] <mdz> keep me updated
[10:40] <ogra> he joined for a short minute in #canonical on tuesday
[10:40] <dholbach> maybe I should do my morning run to his place tomorrow and bang on his door
[10:40] <mvo> ogra: I talked to him at the start of the weel
[10:40] <ogra> ah, right
[10:40] <mvo> week even
[10:40] <mdz> sfllaw: you're next then
[10:41] <sfllaw> Done:
[10:41] <sfllaw>  * Taught two classes for UbuntuOpenWeek
[10:41] <sfllaw>  * Verified many StableReleaseUpdates
[10:41] <sfllaw>  * Bug triage
[10:41] <sfllaw>  * Decided on two interns for the Montreal office
[10:41] <sfllaw>  * scalable-installation-testing spec is drafted
[10:41] <sfllaw> To do:
[10:41] <sfllaw>  * Interview more interns on Friday
[10:41] <sfllaw>  * Start getting thin clients for interns
[10:41] <sfllaw>  * Write documentation on Wiki about Ubuntu QA and TestPlans/TestCases.
[10:41] <sfllaw> Blocked:
[10:41] <sfllaw>  * synaptic SRU is waiting in the edgy-proposed NEW queue
[10:41] <sfllaw> Specs:
[10:41] <sfllaw>  * bug-reporting-tool (Approved)
[10:41] <sfllaw>  * scalable-installation-testing (Discussion)
[10:41] <sfllaw>   * We should probably implement some form of scalable-installation-testing, even if it isn't sufficiently general.  The Testing/Current wiki page must die.
[10:43] <mdz> sfllaw: was the decision positive or negative on the interns?
[10:43] <mdz> sfllaw: I talked with pitti this morning about scalable-installation-testing; I think it may need some revision
[10:44] <sfllaw> sfllaw: Ah.  Interviewed five interns.  Picked two.
[10:44] <sfllaw> mdz: ^^^
[10:44] <mdz> what I've proposed is a small but fundamental change
[10:44] <sfllaw> mdz: Can this change be done for the Feisty timeline?
[10:44] <mdz> it's essential that we be able to collect feedback from people outside of the formal testing framework
[10:44] <sfllaw> mdz: If so, I agree.
[10:45] <mdz> yes, I think it's not significantly more complex
[10:45] <sfllaw> mdz: OK.  Either talk to me or pitti after the meeting and we'll update the spec until you're happy.
[10:46] <mdz> ok
[10:46] <mdz> sfllaw: when do the interns start?
[10:46] <sfllaw> January.
[10:46] <seb128> what are they going to do? ;)
[10:46] <sfllaw> We have desks for them, but we'll need stations.
[10:46] <mdz> bugs!
[10:46] <seb128> new hands to help on bug triage? ;)
[10:46] <sfllaw> seb128: Yes.
[10:46] <seb128> WAOUH
[10:46] <ogra> YAY
[10:46] <dholbach> YEEEHAA
[10:46] <sfllaw> And verification if they can handle it.
[10:46] <mdz> their start should be a good opportunity to review and improve the bug documentation as well
[10:47] <sfllaw> Yeah.
[10:47] <mdz> so that it can be used to train future interns
[10:47] <sfllaw> We should be able to source free people from Jan-Apr.
[10:47] <mdz> sfllaw: great work
[10:47] <sfllaw> Some free people Sep-Dec.
[10:47] <sfllaw> But summer months will be lean.
[10:47] <sfllaw> Kids expect pay from summer jobs.
[10:47] <mdz> if someone has proven themselves in an internship, we can consider them for a summer arrangement
[10:47] <sfllaw> That'd be cool.
[10:47] <seb128> sfllaw: that's why we have SoC :p
[10:48] <ogra> hahaha
[10:48] <sfllaw> Let's talk about this in two or three months.
[10:48] <mdz> sfllaw: thanks
[10:48] <mdz> ogra: next
[10:48] <ogra> * last-week:
[10:48] <ogra>  - travelling the wild wild east
[10:48] <ogra>  - merging
[10:48] <ogra>  - prepared new ltsp feisty branch
[10:48] <ogra>  - prepared --workstation plugin for ltsp-fat-clients (running fine, only network auth bits are missing)
[10:48] <ogra>  - seed merge
[10:48] <ogra>  - OpenWeek edubuntu Q&A session
[10:48] <ogra> * next week:
[10:48] <ogra>  - herd1
[10:48] <ogra>  - merge debian ltsp patch backlog
[10:48] <ogra>  - finishing the parts of ltsp-fat-clients that work without network auth
[10:48] <ogra>  - start working on edubuntu-network-auth-server/client
[10:48] <ogra>
[10:48] <ogra> * approved specs:
[10:48] <ogra>  - ltsp-fat-clients - nearly implemented (a full ubuntu runs awesome in 196M/500Mhz, 32M nbd swap ;) )
[10:48] <ogra>  - edubuntu-network-auth-server - not started
[10:48] <ogra>  - edubuntu-network-auth-client - not started
[10:48] <ogra>  - edgy-plusone-thinclient-sound - started
[10:48] <ogra>  - ltsp-management-gui - started
[10:48] <ogra>  - student-control-panel-upgrade - not started
[10:48] <ogra>  - edubuntu-on-two-cds - not started
[10:49] <ogra>  - ltsp-persistent-home - started by sbalneav (actually implemented during MTV, just not merged yet)
[10:49] <mdz> ogra: your specs don't seem to be targeted for feisty yet
[10:49] <mdz> ogra: have you reviewed them with RichEd?
[10:49] <ogra> they are proposed for it ... anything else i need to do ?
[10:50] <ogra> yes
[10:50] <ajmitch> ogra: I'll try & find some time to talk to you tomorrow or so about e-n-a-c/s
[10:50] <mdz> ogra: and all 8 are feisty targets?  are their priorities set appropriately?
[10:50] <ogra> ajmitch, try to do it at a time where we can get moquist to attend (US time)
[10:50] <ajmitch> right, tomorrow is weekend for me, I'll track him down
[10:50] <ogra> mdz, the edubuntu-auth ones would be more appropriate with high status
[10:50] <finalbeta> mdz they are visible to me on the Feisty spec page.
[10:51] <mdz> ogra: they are not proposed for it; if you are in -core-dev they should go straight through anyway
[10:51] <ogra> weird
[10:51] <mdz> ah, there they are
[10:51] <mdz> ogra: you must have done them since the meeting started :-P
[10:51] <finalbeta> He did.
[10:51] <ogra> yeah
[10:51] <dholbach> just in time
[10:52] <mdz> ok, thanks ogra
[10:52] <mdz> anyone heard from Keybuk?
[10:52] <dholbach> hi pitti
[10:53] <mdz> iwj: next
[10:53] <iwj> Approved:
[10:53] <iwj>  gnome-app-install-codecs: Started looking at g-a-i database generation.
[10:53] <iwj>  udev-lvm, consistent-login-screen: Implementation not yet started.
[10:53] <iwj>  package-dependency-field-breaks: Beta Available.  Should be ready for full deployment now; I will rerun my search-for-candidates.
[10:53] <iwj>  automated-testing-deployment: parts of implementation deferred from edgy.  Work will continue.
[10:53] <pitti> hello
[10:53] <iwj> Approved but problem:
[10:53] <iwj>  usb-adsl-modems: lacking an Assignee.  It would be nice to assign this to someone who understands the subject.
[10:53] <iwj> Drafting:
[10:53] <iwj>  dbus-restarts: This needs discussion.  Ideally we could discuss it at the next UDS or perhaps at a sprint, to write a clear and correct spec for feisty+1.  Upstream disapprove but we all agree they're wrong.
[10:53] <iwj> New - needed (and still need) discussion, but not scheduled at uds-mtv:
[10:53] <iwj>  winmodem-support: IMO should be deferred to feisty+1.
[10:53] <iwj>  edgy-fontconfig: There is no spec.  IMO should be deferred (or rejected).
[10:54] <mdz> iwj: we don't have an expert on hand for usb-adsl-modems; you'll need to learn about it
[10:54] <mdz> iwj: hardware and service can be provided if needed
[10:54] <iwj> I'll see what I can do.
[10:54] <mdz> iwj: let me know what you need and how much it costs
[10:55] <mdz> iwj: same goes for winmodem-support.  there is no formal spec, but there is a wealth of information from the community
[10:55] <iwj> OK, I'll look into both of those.  I don't want to make any promises ...
[10:55] <mdz> it deserves a proper review to identify which bits can be automated, which are licensing issues, etc.
[10:55] <cjwatson> for winmodem-support I think we need to be careful to select what we do
[10:55] <cjwatson> it's in danger of being a bit of a rabbit-hole
[10:55] <iwj> It did look quite open ended.
[10:56] <cjwatson> I agree it should be reviewed, just would like the time to be spent wisely
[10:56] <mdz> we should make sure we're doing the best we can with the available software to enable the hardware
[10:56] <pitti> meeting is over already?
[10:56] <iwj> I'll see what I can do to improve the situation.  (I already have a winmodem in my laptop in fact ...)
[10:56] <cjwatson> pitti: no
[10:56] <mdz> it isn't more than a day's work to review what's out there, and that would be time well spent
[10:56] <mdz> pitti: no
[10:56] <iwj> review> OK, I'll do that.
[10:57] <pitti> ah, just my terrible initial lag
[10:57] <mdz> iwj: ok, let me know what you find out
[10:57] <mdz> iwj: edgy-fontconfig was a discussion placeholder for UDS; should be marked informational and not targeted
[10:57] <iwj> OK.
[10:58] <mdz> dbus-restarts sounds like something which needs discussion, especially with some upstreams
[10:58] <mdz> not urgent for feisty
[10:58] <iwj> mdz: I don't think discussing it with upstreams will get us anywhere.
[10:58] <iwj> not urgent for feisty> Indeed.
[10:58] <iwj> We just need to fix it.
[10:58] <mdz> it's a lot of work and a large delta for us to take on; we shouldn't do it without some buy-in elsewhere
[10:58] <iwj> So I'd like to actually talk to people about what would be a good thing to do so we have a clear plan.
[10:59] <iwj> Without that it's hard to get buy-in.
[10:59] <iwj> I think Debian would take sane changes at least.
[10:59] <cjwatson> iwj: not dbus upstream themselves, perhaps, but upstreams of packages using dbus
[10:59] <iwj> cjwatson: Mmmm.
[10:59] <mdz> ->ubuntu-devel then, CCing relevant upstreams for the packages we'd be modifying
[10:59] <iwj> marked informational> Err, how do I do that in LP ?
[10:59] <mdz> it's under 'title and summary' or such
[11:00] <iwj> Aha.
[11:00] <mdz> iwj: breaks isn't targeted for feisty; if it's ready to go then target it
[11:00] <iwj> mdz: Right.
[11:00] <mdz> automated-testing-deployment needs targeting also; I think it's still set to edgy
[11:00] <iwj> Willdo.
[11:01] <mdz> ok, thanks iwj
[11:01] <mdz> cjwatson: next
[11:01] <cjwatson> Specifications:
[11:01] <cjwatson>   setup-console-under-usplash: Approved, beta available; apparently broke though (#73955) so need to investigate.
[11:01] <cjwatson>   intel-mac-support, ubiquity-advanced-partitioner, ubiquity-automation, ubiquity-driver-updates, ubiquity-release-notes: Approved.
[11:01] <cjwatson>   feisty-ubiquity: Approved. Part bite-size tasks for new developers, and part stuff that I need to do; who should be the assignee?
[11:01] <cjwatson>   ubiquity-slideshow: Approved. Part artwork and part me; who should be the assignee?
[11:01] <cjwatson>   increase-hwdb-participation: Approved. Assignee probably shouldn't be me.
[11:01] <cjwatson>   ubiquity-more-user-config: Still drafting, but mostly there on the condition that it satisfies the requirements, which I'm not sure about; sent to sabdfl for review. Need to talk to sysadmin too.
[11:01] <cjwatson>   simplify-oem-installation: Still in requirements gathering. There are some fairly obvious things we can do listed at the bottom of the brain-dump, but I don't know how far we can take this without better commercial input.
[11:01] <cjwatson>   ubiquity-oem: Not written up, and probably not happening.
[11:01] <cjwatson> Other:
[11:01] <cjwatson>   Installer all merged, and more or less ready for Herd 1 bar the bug-fixing.
[11:01] <cjwatson>   Who volunteered to be distro->LP-meeting delegate? I thought it was sfllaw, but I don't remember for sure, and the LP meeting is not obviously conveniently timed for him.
[11:01] <cjwatson>   <SteveA> I like the idea of having a delegate from the distro team
[11:01] <cjwatson>   <SteveA> one way to manage this with simon is to have simon talk with me or kiko on wednesday
[11:01] <cjwatson>   <SteveA> and feed points / topics of concern to us for the meeting
[11:01] <cjwatson> (the bit at the end was because I chipped into the LP meeting with something random and SteveA /msged me to thank me for contributing)
[11:02] <mdz> cjwatson: feisty-ubiquity: primary assignee should be you, but please farm out the bite-size bits.  maybe talk to dholbach or jono if no one in the core team is interested
[11:02] <cjwatson> ok
[11:03] <sfllaw> As for the LP delegate, it should probably be me.  As I basically spend all day using LP.
[11:03] <cjwatson> I know sivang expressed interest
[11:03] <cjwatson> sfllaw: time sucks for you, doesn't it? it's always noon UTC
[11:03] <sfllaw> sivang: Ping?
[11:03] <mdz> cjwatson: ubiquity-slideshow is yours but low priority; would be great to find someone else to take it and be able to bump it up, but your others are more important
[11:03] <cjwatson> sfllaw: I mean in ubiquity work
[11:03] <sfllaw> Yeah, that time is terrible.
[11:04] <cjwatson> mdz: understood; shortly I'll be putting together some kind of guide for installer development and mailing it out in the hope of generating some interest
[11:04] <cjwatson> sfllaw: but, as SteveA says, if you want to feed info to him and kiko on Wednesday, and read the logs/summaries afterwards, that would work fine
[11:04] <sfllaw> When are their meetings?  Thursday?
[11:05] <cjwatson> yes
[11:05] <mdz> let's take that discussion to distro-team@
[11:05] <sfllaw> I might do that.
[11:05] <mdz> distro-team@ and launchpad@, even
[11:05] <mdz> it might be that that person doesn't need to attend the meetings
[11:05] <cjwatson> I mentioned increase-hwdb-participation at last week's meeting too. Mithrandir expressed some interest then, but I think he thought it was in casper, which it doesn't really seem to be
[11:06] <mdz> any volunteers for increase-hwdb-participation?
[11:07] <cjwatson> (it's basically a desktop notification plus a few other bits)
[11:07] <ogra> yeah, its only a notification bubble and a change of the .desktop file status ...
[11:07] <pitti> doesn't sound too scary, I can take a look at it, but I don't know the spec yet
[11:07] <mdz> pitti: please have a look and let me know
[11:07] <cjwatson> I think it's fairly trivial, if you have time.
[11:08] <mdz> cjwatson: does that cover all the non-limbo specs of yours?
[11:08] <pitti> the time is the problem here, but that applies to everyone
[11:08] <ogra> it mentions apport as well ;)
[11:08] <pitti> heh
[11:08] <cjwatson> mdz: I believe they're all covered above. ubiquity-more-user-config, simplify-oem-installation, ubiquity-oem are the only ones not targeted.
[11:09] <mdz> *oem* I think has to be targeted for feisty+1 after proper requirements definition
[11:09] <sladen> if increase-hwdb-participation is really that minor, I'll consider it
[11:09] <mdz> more-user-config is blocked on IS?
[11:09] <lifeless> I need to finish the hwdb client changes to - pitti can we coordinate please
[11:09] <lifeless> s/to/too
[11:09] <cjwatson> ubiquity-slideshow> I expect that my side of it will be pretty small, FWIW. I agree it's less important than the others
[11:09] <pitti> lifeless: of course
[11:09] <cjwatson> mdz: yes
[11:09] <cjwatson> will send mail about that
[11:10] <mdz> ok, should probably be in RT
[11:10] <mdz> cjwatson: thanks
[11:10] <Burgwork> cjwatson: email marketing team asking for content
[11:10] <lifeless> pitti: great. I have have it working, just needs to be made pretty.
[11:10] <mdz> pitti: next
[11:10] <pitti> Done:
[11:10] <pitti>  * lots of package merges
[11:10] <pitti>  * spec reviews, discussions, and approvals; my own (assignee/drafter) feisty specs are all approved; I approved most of the specs I'm approver for, except:
[11:10] <pitti>   - simple-x-mode-selection: still in drafting, pinged rodarvus yesterday
[11:10] <pitti>   - scalable-installation-testing: was approved this morning with our original design; mdz had a different idea which got discussed shortly this morning, but which requires more intrusive changes in ubiquity, the db design, and other components, so I set it back to discussion for now
[11:10] <cjwatson> Burgwork: art team too I think
[11:10] <cjwatson> Burgwork: but ok
[11:10] <pitti>   - ltsp-local-apps: utterly complex and a quick discussion with cjwatson revealed that this needs much more thought (this one is not marked for feisty)
[11:10] <pitti>  * Note: bug-reporting-tool is currently assigned to sfllaw, but since it's mainly apport work, I should probably the assignee.
[11:10] <pitti>  * cleanup-audio-jumble: tested pulseaudio and attempted to create the mentioned (in spec) patch to not hog the audio device; this failed due to the principal design of pulse; upstream works on a cleaner and more generic solution, but this will not be ready for feisty; since I do not want to break compatibility with commercial OSS apps and the multiuser case, I did not continue working on this for now
[11:10] <pitti>  * zero-configuration-networking:
[11:10] <pitti>   - did the required changes to base-files, avahi-autoipd, avahi, libnss-mdns, and ifupdown, so that the stuff works OOTB now when using dhclient
[11:10] <pitti>   - filed bug for zeroconf package removal
[11:10] <pitti>   - still missing: fix network-manager to not clobber the avahi-autoipd address (so that .local name resolution works with n-m), teach network-admin about the new ifupdown method (not that urgent, though, most people will not use the new /e/n/interfaces method and just rely on n-m or dhclient), and seed avahi-autoipd to ubuntu-desktop (after herd freeze)
[11:10] <pitti>  * apport-improvements: got apport bits in for intercepting Python crashes, discussed a battle plan for Mono with slomo
[11:10] <pitti>  * two OpenWeek talks
[11:10] <pitti>  * started discussion and coding for automated package tests (mainly to improve QA of securi
[11:10] <pitti> ty updates so far, but this topic seems to grow and grow)
[11:11] <pitti> Todo:
[11:11] <pitti>  * finish zero-configuration-networking implementation
[11:11] <mdz> pitti,sfllaw: happy for pitti to take bug-reporting-tool if you two agree
[11:11] <pitti>  * fix feisty's and edgy's gnome-system-tools authentication problem
[11:11] <pitti>  * change dapper's and edgy's ~/.xsession-errors rotation handling to new plan
[11:11] <pitti>  * dive into bug triage
[11:11] <mdz> consider cleanup-audio-jumble deferred for now
[11:11] <sfllaw> pitti: Agreed.
[11:11] <pitti> sfllaw: if you want to hack on apport, go ahead, of course; but I guess I'll give a hand with that anyway
[11:11] <cjwatson> pitti: ltsp-local-apps> do you mean the ssh Cipher=none thing?
[11:11] <pitti> mdz: audio> I agree
[11:11] <sfllaw> pitti: When I get not busy.  :)
[11:11] <sfllaw> In the meantime, you can hack on it.
[11:11] <pitti> cjwatson: yes, that still seems to be an issue, I didn't hear an update so far?
[11:11] <ogra> cjwatson,  ssh Cipher=none isnt in any spec
[11:12] <cjwatson> pitti: haven't looked at it yet, I didn't realise it was blocking this spec rather than just random would-be-nice-if
[11:12] <ogra> thats a whishlist thing from upstream ltsp ... to not having to switch to xdmcp
[11:12] <mdz> pitti: Mithrandir is going to be working on n-m, so coordinate with him re: zero-conf-net
[11:12] <pitti> cjwatson: well, it's not the only thing; the spec lacks verbosity in general
[11:12] <ogra> if it shouws up in that spec it needs to be taken out, it has nothing to do with local-apps
[11:12] <pitti> mdz: yes, we already had a quick talk
[11:12] <cjwatson> pitti: ok; if it's something else then I'm afraid I've entirely forgotten our discussion ;)
[11:13] <cjwatson> I need to look at scalable-installation-testing
[11:13] <mdz> pitti: automated package tests -> iwj's stuff or something different?
[11:13] <pitti> cjwatson: I mainly needed that
[11:13] <pitti> mdz: eventually it would merge with that, yes
[11:13] <pitti> mdz: keescook and I had a discussion on the allhands how to improve our security update QA process
[11:14] <mdz> lifeless: ^^
[11:14] <pitti> mdz: and we agreed to testing security updates at least by two people, and writing automated tests where appropriate
[11:14] <pitti> sfllaw, lifeless, keescook, iwj, and I had a small discussion recently
[11:14] <pitti> since it turned out that these tests should be applicable to QA team as well, and might be integrated into autopkgtest
[11:15] <lifeless> mdz: yup
[11:15] <iwj> There's a reasonably good fit; most of my stuff is infrastructure and there are quite a few actual tests there that it would be nice to glue in.
[11:15] <mdz> ok
[11:16] <mdz> tkamppeter: are you here?
[11:16] <tkamppeter> Yes.
[11:16] <mdz> tkamppeter: ok, you're next then
[11:16] <mdz> pitti: thanks
[11:16] <pitti> I didn't yet take a look at autopkgtest, I just wanted some initial bits to play with, but I definitively want to make it fit there
[11:16] <tkamppeter> ACCEPTED FEATURES (for Feisty):
[11:16] <tkamppeter> https://blueprints.launchpad.net/people/till-kamppeter/+specs
[11:16] <tkamppeter> UDS outcomes:
[11:16] <tkamppeter> - "Easy configuration of printer sharing"
[11:16] <tkamppeter> - "Replace gnome-cups-manager by printerdrake"
[11:16] <tkamppeter> - "Automatic download of printer drivers through the internet"
[11:16] <tkamppeter> - "Automatic hotplug printer configuration"
[11:17] <tkamppeter> - Answered to bug report
[11:17] <tkamppeter> - Re-submitted EDgy update for foo2zjs bug 65618
[11:17] <Ubugtu> Malone bug 65618 in foo2zjs "Firmware upload to LJ 1000/1005/1008/1020 broken (fix to be proposed as Edgy update)" [Medium,Fix committed]  http://launchpad.net/bugs/65618
[11:17] <mdz> pitti's concerns with printerdriverautodownload were addressed?
[11:17] <pitti> mdz: yes
[11:17] <pitti> (from my POV, that is)
[11:18] <tkamppeter> Also discussed how to save space with the PPDs bug 39847
[11:18] <Ubugtu> Malone bug 39847 in foomatic-db "Getting (more) manufacturer-supplied PostScript PPDs onto the Ubuntu desktop CDs" [Undecided,Confirmed]  http://launchpad.net/bugs/39847
[11:18] <mdz> tkamppeter: 65618 -> cjwatson
[11:19] <mdz> automatic hotplug printer configuration is not for feisty, correct?
[11:19] <cjwatson> the SRU team is subscribed to 65618, so I'll catch up on it tomorrow
[11:19] <cjwatson> sorry for the delay
[11:19] <tkamppeter> Yes, this I wanted to say, too.
[11:19] <mdz> ok
[11:19] <mdz> thanks tkamppeter
[11:20] <mdz> did I miss anyone, or is there any other business to discuss (briefly)?
[11:20] <zul> just me..
[11:20] <fabbione> distro sprint?
[11:20] <mdz> zul: go ahead
[11:20] <pitti> ^ any dates yet?
[11:20] <zul> this week
[11:20] <zul> ---------
[11:20] <zul> * xen kernel update
[11:20] <zul> * kernel security for breezy.
[11:20] <zul> * bug triaging
[11:20] <zul> next week
[11:20] <fabbione> we are about 7 weeks and no dates have been confirmed
[11:20] <zul> ---------
[11:20] <mdz> fabbione: please mail distro-team@
[11:20] <zul> * big xen/kernel push
[11:20] <ogra> ^ any places yet ?
[11:20] <zul> * bug triaging
[11:20] <zul> * merges
[11:20] <zul> Specs
[11:20] <zul> ----
[11:20] <mdz> fabbione: we do need to finalize that soon
[11:20] <zul> * xen-fesity spec apprvoed (approved), started
[11:21] <mdz> zul: are you comfortable with how xen-feisty turned out?
[11:22] <zul> yes i am
[11:22] <ajmitch> mdz: what do do with any other specs that may be stuck at needs review or pending approval?
[11:22] <mdz> zul: will xen support paravirt-ops?
[11:22] <mdz> ajmitch: review -> review team, approval -> technical-board
[11:22] <zul> it looks like it from what i been seeing ive asked the upstream developers
[11:23] <mdz> that would make it a candidate for main
[11:23] <zul> thats what im hoping for
[11:23] <mdz> we'll see what happens
[11:23] <ajmitch> mdz: right, thanks, wasn't sure if it was too late
[11:23] <mdz> we're well over time
[11:23] <zul> thanks everyone
[11:24] <mdz> yes, thanks all
[11:24] <pitti> zul, BenC, kylem: any remaining trouble for the kernel security update? any ETA?
[11:24] <mdz> until next week
[11:24] <cjwatson> not really for this meeting I suppose, but do we know the status of new TB appointments?
[11:24] <mdz> adjourned
[11:24] <seb128> thank you mdz
[11:24] <dholbach> thanks
[11:24] <mdz> cjwatson: that's all sabdfl as far as I know; will raise it with him the next time we speak
[11:24] <kylem> pitti, i've been building them today to make sure i don't brown paper bag my first piece of work...
[11:24] <dholbach> and a TB meeting? people have been asking me for that already
[11:24] <kylem> pitti, but afaict, it seems good.
[11:24] <zul> pitti: i think im almost ready i just have one patch to ask about
[11:25] <zul> but ill do that tonight when i get home (still at work)
[11:25] <zul> later
[11:26] <pitti> zul, kylem: thank you
[11:26] <pitti> thanks all!
[11:26] <kylem> cheers
[11:30] <sfllaw> Thanks.
[12:15] <tonyyarusso> @schedule toronto
[12:15] <Ubugtu> Schedule for America/Toronto: Current meeting: Ubuntu Development Team | 06 Dec 15:00: Edubuntu | 07 Dec 03:00: Ubuntu Development Team | 13 Dec 07:00: Edubuntu | 14 Dec 11:00: Ubuntu Development Team | 20 Dec 15:00: Edubuntu


[00:24] <Atheistics> installing now
[00:26] <[0gb_us]> Installing what? Xubuntu?
[00:26] <Atheistics> xubunt...trying to install flashplayer also
[00:40] <sketch_> hello all again... so id like the lil bit of compiz wobbaly windows and such can anyone tell me how to get it working?
[00:49] <Rakko> How can I make Xubuntu put my monitor in powersave mode when idle? I seem to be using Xscreensaver (standard with xubuntu?), which is set to blank the monitor only; it does blank it, but it's not in powersave mode.
[00:52] <[0gb_us]> I had that same issue. Here's how to fix it:
[00:53] <[0gb_us]> In the xscreensaver config window, choose turn on power managing and enable the setting that says to shut off the monitor imediently when in blank-only mode.
[00:54] <[0gb_us]> It has the unfortunate side effect of forcing power management to be enabled when you choose a non-black screensaver, but if you stick with just black, it will work.
[01:00] <Rakko> oh, I must have missed that
[01:03] <Rakko> thanks
[01:06] <Rakko> Out of curiosity, why isn't X just configured to do that?
[01:06] <[0gb_us]> It should be. And in GNOME screensaver, it is.
[01:07] <Rakko> Well I mean those are dependent on certain screensavers. I would think it would be dependent on something at a lower level.
[01:07] <[0gb_us]> I don't know. I'm still trying to figure out how to dim the screen in Xubuntu. It works fine in Ubuntu.
[01:08] <sketch_> ok so i followed this guide http://www.webupd8.org/2012/11/how-to-set-up-compiz-in-xubuntu-1210-or.html and i still have nothing any ideas?
[01:08] <[0gb_us]> Sorry, I don't know anything about Compiz.
[01:09] <sketch_> anyone else??? lol
[01:18] <sketch_> compiz on xubuntu is not working and i cant figure out why i looked around and its the same process and i.ve tried 4 times
[01:19] <[0gb_us]> Does it work on other variants? Such as Ubuntu?
[01:21] <sketch_> yeah i got it
[01:21] <sketch_> n/m
[01:44] <ntzrmtthihu777> hallo. odd issue here. while creating a symlink for ruby (it has stupidly placed .h files, lol) the resultant link is always broken, am I doing something wrong here?
[02:02] <Rakko> [0gb_us]: where does Xubuntu allow you to set whether the computer itself goes to sleep?
[02:02] <Rakko> mine seems to go to sleep after some amount of time, which is annoying when I'm trying to use it to back up
[02:03] <Rakko> I don't remember 10.x doing that
[02:03] <[0gb_us]> I think there's a way to set that in power management, but mine is set not to do that.
[02:04] <[0gb_us]> Menu > Settings > Settings Manager >  Power Manager
[02:04] <[0gb_us]> Rakko, ^
[02:05] <Rakko> d'oh
[02:05] <Rakko> thanks
[02:06] <[0gb_us]> Yeah, no problem.
[02:07] <Rakko> nice. terminal rickroll
[02:07] <[0gb_us]> Hmm? What?
[02:07] <Rakko> ntzrmtthih777's quit message
[05:19] <xubuntu135> folks good morning
[05:20] <xubuntu135> i just installed xubuntu 12.04
[05:20] <xubuntu135> I can ping any internet address
[05:20] <xubuntu135> no loss
[05:20] <xubuntu135> but I can't install anything thru apt-get
[05:20] <xubuntu135> neither browse the internet
[05:21] <[0gb_us]> THat's really odd.
[05:21] <xubuntu135> even when i run live
[05:21] <xubuntu135> same thing happens
[05:21] <[0gb_us]> I don't know how to help with that.
[05:22] <xubuntu135> ok thanks
[05:22] <[0gb_us]> I have an odd issue where I can't ping an address that I can connect to. It's sort of the opposite problem.
[05:22] <xubuntu135> kindaof
[05:22] <xubuntu135> lol
[05:23] <xubuntu135> maybe i'll try the latest release
[05:23] <xubuntu135> thanks anyway
[05:23] <xubuntu135> good luck
[06:34] <xubuntu164> hello
[06:35] <[0gb_us]> Hello!
[06:35] <xubuntu164> i need to ask
[06:35] <ObrienDave> just ask
[06:35] <xubuntu164> how to integrate calendar with outlook and webmail as i use postfix as a mail server
[06:36] <ObrienDave> outlook? isn't that a windows program?
[06:38] <[0gb_us]> Yeah, my mother uses that.
[06:39] <ObrienDave> i used to, before i found Linux ;)
[06:39] <[0gb_us]> I was a Mac user before I found Linux.
[06:39] <[0gb_us]> No Outlook there either.
[06:39] <ObrienDave> another convert :))
[06:41] <[0gb_us]> I've managed to convert my three siblings as well. ☺ I still haven't had any luck with our mother though. ☹
[06:42] <ObrienDave> i wouldn't even try to convert mine, my wife is bad enough LMAO
[06:42] <[0gb_us]> I only try to convert Windows people. My Mac-using brother was an accident.
[06:43] <ObrienDave> better late than never :D
[06:44] <ObrienDave> brb
[06:45] <[0gb_us]> Hmm. I still need to talk to some people from #gnu. Apparently, using commercial software is somehow morally wrong or something. Personally, I like a mix of open source and commercial software myself, so I want to understand what is so bad about that.
[06:50] <ObrienDave> nothing wrong with commercial software. it does, however, go against the grain of open source free software
[06:51] <[0gb_us]> The problem though is that open source software can't reliably fill some needs.
[06:52] <[0gb_us]> Anything that remains consistent can be handled by open source projects.
[06:52] <ObrienDave> true. but i can do 98% of what i need with open source
[06:52] <[0gb_us]> However, some things require constant and steady development.
[06:53] <[0gb_us]> I use commercial games and probably commercial drivers. The rest of my stuff is open source.
[06:53] <koegs> guys, that is an interesting topic, but could you please move over to #xubuntu-offtopic?
[06:53] <[0gb_us]> Hmm? Oh, sorry. I'll be quiet now.
[09:36] <foobar55> hi all - someone firm with harddisk -ide 2,5 fujitsu mht2040 - I lost 10MB from 40MB ??
[09:36] <foobar55> system freeze when i installed xubuntu 12.04 -  when formating hd may be after 10%
[09:37] <foobar55> partition magic from liveCD even freeze at 10% formatingi
[09:37] <foobar55> reconfigured the disk with testdisk CHS 16383,16,63 LBA 78.140.160
[09:37] <foobar55> but getgpart = dev(/dev/sdb) mss(512) chs(30517/64/32)(LBA) #s(62498816) size(30517mb) Warning: strange partition table magic 0x0000
[09:37] <foobar55> Partition table holds up to 128 entries First usable sector is 34, last usable sector is 62499966dmde
[09:37] <foobar55> found FAT32 32MB 0 - 62499999 ( i think primary sectors )  and (i think logical)  63 - 62499999dmde found patition 3,16MB<PHONE_NUMBER>05 and 6,29MB<PHONE_NUMBER>74 sectors - this are the lost 10MB
[09:37] <foobar55> i use the tools - DMDE,  gpart, testdisk to find my mistake
[09:37] <foobar55> i dont know a logical workflow to reconf this harddisk or find the failure because i tryed all normal ways
[09:37] <foobar55> I know the disk is dead, but its only for my anderstanding
[10:21] <testpil0t> Hello! I am using xubuntu 12.04. Since a few days, the volume indicator always pops up, once in a while. Without doing any change on the volume level. I did not find any bug description about this (or anything)... Did anyone experience similar problems ?
[10:31] <testpil0t> ... also xfce always restores my session :/
[10:34] <Sysi> you can select to not restore session in logout popup window, delete saved one with rm -rf ~/.cache/sessions
[10:45] <gatsu1000> hey all
[14:14] <Roxastry> Hello all. I have issues about window customization. I needed change titlebar color. How i can make it? Sorry of my bad English.
[14:15] <koegs> Roxastry: i think you have to edit the theme, you cannot simply change the color in settings
[14:15] <koegs> http://wiki.xfce.org/howto/xfwm4_theme
[14:19] <Roxastry> I need change it programmatically. I create application on Gtkmm library. I can use other library if it need.
[14:19] <Roxastry> I'm use c++.
[14:19] <Roxastry> *I use C++
[14:23] <GridCube> Roxastry, you want to override gtk configs?
[14:25] <Roxastry> GridCube, No. This should only be used in the same application, in which I write.
[14:25] <GridCube> so, you want your program to override global gtk?
[14:26] <GridCube> http://stackoverflow.com/questions/14887646/can-an-application-override-a-gtk-theme-for-one-property-of-one-widget
[14:28] <ochosi> Roxastry: that is impossible with xfwm4 at the moment, as far as i know
[14:29] <ochosi> Roxastry: when it is ported to gtk3 (at some point in the distant future) and support for dark themes gets added, you can tell the app to ask for a dark theme
[14:29] <ochosi> Roxastry: the only alternative is to make your app undecorated and add window-decorations yourself (check xfce4-notes as reference, it's written in vala though afaik)
[14:30] <Roxastry> I can create my theme and use he only my application?
[14:31] <ochosi> i don't know in detail how xfce4-notes does it, check the source-code ;)
[14:31] <GridCube> Roxastry, read the link i pasted you
[14:31] <Roxastry> thanks all :)
[14:31] <ochosi> np
[14:31] <Roxastry> i will try =)
[14:32] <ochosi> Roxastry: just out of curiosity, what app are you writing?
[14:33] <Roxastry> i can't say =( it's commerce=(
[14:34] <ochosi> how sad
[14:54] <_DomY-Dom> In 13.04 what is the valid path to the 16:40 < genec> well, it ONLY needs to be bastardized via CLI when you are doing an unsupported action
[14:54] <_DomY-Dom> damn
[14:54] <_DomY-Dom> sorry wrong copy paste
[14:55] <_DomY-Dom> In 13.04, what is the valid path to the 3.8.0-22-generci kernel headers?
[14:55]  * _DomY-Dom that's better
[14:58] <aiena> Does anyone know if 32 bit povray runs on 64 bit architecture (runnig xubuntu 12.04 precise - 64 bit)
[14:58] <knome> aiena, should be no problem running 32 bit stuff on 64 bit generally
[14:59] <genii-around> _DomY-Dom: All the headers get put in /usr/src/linux-headers-<KERNEL-VERSION-HERE>
[15:01] <genii-around> eg: /usr/src/linux-headers-3.8.0-22-generic/        ...in this case
[15:08] <xubuntu542> a chanel for cairo dock exists?
[15:10] <GridCube> #cairo-dock
[15:14] <aiena> knome: I had to install it with no architecture support for it to work now povray renders with a translucent background but it renders either way and does its job and nothing seems broken so I'm happy
[15:19] <_DomY-Dom> genii-around: "The path "/usr/src/linux-headers-3.8.0-22-generic/" is not a valid path to the 3.8.0-22-generic kernel headers" is the output I get from the VMware tools installation, I have Xubuntu 13.04 in a VM (VMWare Fusion).
[17:56] <xubuntu144> Hi there, i'm a bit green, wel actually I'm a total green....
[17:58] <xubuntu144> anyway I just installed xubuntu 13.04 on my old laptop, everything works just fine but no internet.
[18:02] <xubuntu144> when I plug the cable i got a nice windows telling me that I'm connected, but nothing else happens. No firefox, no nothing. If I open terminal and use "ifconfig" i get as follow:
[18:02] <xubuntu144>  amarco@marco-Laptop:~$ ifconfig eth0      Link encap:Ethernet  HWaddr 00:00:e2:7c:97:61             inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>           inet6 addr: fe80::200:e2ff:fe7c:9761/64 Scope:Link           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           RX packets:931 errors:0 dropped:0 overruns:0 frame:0           TX packets:1110 errors:0 dropped:0 overruns:0 carrier:0           collisio
[18:03] <xubuntu144> any idea what could be wrong?
[18:03] <bazhang> what about sudo dhclient eth0
[18:03] <bazhang> and then ping www.google.com
[18:06] <xubuntu144> marco@marco-Laptop:~$ sudo dhclient eth0 RTNETLINK answers: File exists marco@marco-Laptop:~$ ping -c3 www.google.com ping: unknown host www.google.com
[18:07] <Myrtti> how about if you ping <IP_ADDRESS>
[18:14] <xubuntu144> marco@marco-Laptop:~$ ping -c5 <IP_ADDRESS>  PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.  --- <IP_ADDRESS> ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4031ms
[18:14] <xubuntu144> marco@marco-Laptop:~$ ping <IP_ADDRESS> PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.  ^C --- <IP_ADDRESS> ping statistics --- 105 packets transmitted, 0 received, 100% packet loss, time 103999ms
[18:15] <koegs> can you ping the gateway ip?
[18:16] <xubuntu144> mmmmmhhhhh ..... gateway ip = ??????
[18:16] <xubuntu144> sorry !!!!
[18:20] <xubuntu144> ok, ok, I'm getting there....
[18:21] <koegs> xubuntu144: how do you connect to the internet?
[18:22] <xubuntu144> marco@marco-Laptop:~$ ping <IP_ADDRESS> PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data. ^C --- <IP_ADDRESS> ping statistics --- 53 packets transmitted, 0 received, 100% packet loss, time 52334ms
[18:22] <koegs> so you have the ip <IP_ADDRESS> and your default gateway is <IP_ADDRESS>, this is definitely not working
[18:23] <xubuntu144> cable - is working fine, I'm using the same connection now on another computer router
[18:23] <koegs> please put the output of "ifconfig -a" and "ip r s" in a nopaste
[18:23] <koegs> !paste
[18:26] <xubuntu144> http://paste.ubuntu.com/5711032/
[18:27] <xubuntu144> thanks 4 the tip. I'm already learning a lot!
[18:27] <koegs> so your default gateway is <IP_ADDRESS>, please try to ping it
[18:32] <xubuntu144> http://paste.ubuntu.com/5711055/
[18:36] <koegs> so, dhcp works, you can ping your router, but not <IP_ADDRESS> (which is the google dns server)?
[18:37] <xubuntu144> that seems indeed the case. and I dont have a clue what to do about it
[18:48] <xubuntu144> thanks anyway.... I'll figure something out..... tomorrow    : )
[20:04] <jtreminio> Hi all! Are there any special steps to be taken to install Xubuntu on a MBP 2013 model?
[20:04] <jtreminio> er, late 2012 model I guess
[20:09] <Sysi> if you boot from CD, no
[20:10] <Sysi> your machine will boot to xubuntu by default, you need to hold alt to get to osx
[20:11] <jtreminio> Sysi: thanks for that. Any other issues? I want to install the OS via USB
[20:14] <b3rz3rk3r> Does anyone know how to remove dead entries from the XFCE menu that don't show up in the editor?
[20:15] <Sysi> jtreminio: you need to create stick with some additional steps https://help.ubuntu.com/community/How%20to%20install%20Ubuntu%20on%20MacBook%20using%20USB%20Stick
[20:15] <Sysi> b3rz3rk3r: look into ~/.local/share/applications
[20:15] <b3rz3rk3r> Sysi, will do, thanks!
[20:18] <b3rz3rk3r> Sysi, worked perfectly, cheers! :D
[20:18] <Sysi> you're welcome
[20:19] <Sysi> jtreminio: in my experience on early '11 MBP, battery life was worse than on virtual machine
[20:27] <xubuntu267> i have encrypted my home foldder in xubuntu
[20:28] <xubuntu267> and i took some picts to a usb stick and i cant red them to window spc
[20:28] <xubuntu267> what can i do?


[02:18] <xenol> hello
[02:18] <xenol> i am interested in how does xubuntu deal with displaying battery state notifications
[02:19] <xenol> is there any patch for xfce4-power-manager?
[02:33] <cody-somerville> xenol, you just need to be running a libnotify compatible notification daemon I think
[02:35] <xenol> cody-somerville: when i insert battery or AC it sends notification. tho i am looking for something similar to this
[02:35] <xenol> https://wiki.ubuntu.com/Xubuntu/Specifications/Karmic/NotifyOsd?action=AttachFile&do=get&target=notify-osd-powerinfo-example.png
[02:36] <cody-somerville> that wasn't implemented
[02:36] <xenol> any patch?
[02:42] <xenol> cody-somerville: any patch for it which will implement that feature?
[02:43] <cody-somerville> not as far as i know
[02:43] <xenol> it works only in crappy ubuntu?
[02:43] <xenol> pardon my language though :)
[03:22] <sanubuntu> armageddon09: ok, i think i found what you're talking about, looks like the right thing .. i'll have to log out to the other user and try it
[03:22] <sanubuntu> thanks
[03:24] <pHro> hi
[03:27] <jhb1608> question, how do I install Java when I'm in Xubuntu 9.10?
[03:30] <jhb1608> well?
[03:31] <jhb1608> hello?
[03:32] <jhb1608> never mind
[03:37] <likemindead> >____<
[05:41] <dave99> anyone around I need help
[05:42] <dave99> 68 people and no one talks? what am I missing?
[07:45] <Balsaq> if i burn 9.10 onto cd, how may cd's will it take to copy the enitre OS?
[07:46] <Balsaq> these cd's are 700mb...so i am guessing 2...right?
[07:48] <xsteadfastx> Balsaq: about what iso's are you talking?
[07:48] <xsteadfastx> one iso is one cd
[08:04] <antonio_> hello
[08:05] <antonio_> bonjour
[08:05] <antonio_> comment allez vous?
[08:06] <antonio_> ??
[08:06] <antonio_> y a t'il quelqu'un svp
[08:06] <antonio_> i need help
[08:07] <Besogon> What's wrong?
[08:07] <antonio_> pleeeaaaaaase
[08:07] <antonio_> ouf
[08:07] <antonio_> well
[08:08] <antonio_> it's my screen resolution
[08:08] <antonio_> it's only 800x600 but under win its more than that
[08:08] <antonio_> how can change it
[08:08] <antonio_> dell C600 p3
[08:08] <antonio_> ram 128
[08:08] <antonio_> HD 10
[08:09] <antonio_> need smth more?
[08:09] <Besogon> Have you installed drivers?
[08:09] <antonio_> which ones?
[08:11] <antonio_> i've tried to update some but it(s still the same
[08:12] <antonio_> any idea?
[08:14] <antonio_> j'ai un dell latitude c6OO et je n'arrive pas a changer la resolution de mon ecran
[08:14] <antonio_> a l'aide svp!
[08:16] <antonio_> je suis toujours a l'ecoute hein!
[08:16] <Besogon> You use xfce4-display-settings for changing resolution don't you? So If your system has driver for graphics card and you are interested in another resolution you should make xorg.conf
[08:17] <antonio_> the pb is that my xorg.conf file is empty
[08:17] <antonio_> and when i change it
[08:18] <antonio_> it bugs
[08:18] <antonio_> when i restart
[08:20] <Besogon> antonio_, xorg.conf is easy to change.
[08:21] <antonio_> i know it is
[08:22] <Besogon> !paste
[08:23] <antonio_> and i 've even a file on a forum
[08:23] <antonio_> i copied it and pasted in my xorg.conf file
[08:23] <antonio_> but still nada
[08:23] <antonio_>  :(
[08:24] <Besogon> This is mine http://paste.ubuntu.com/316685/
[08:25] <Besogon> modelines should be only your own.
[08:26] <Besogon> !xorg.conf
[08:30] <antonio_> thbaks a lot
[08:30] <antonio_> i will check and tell you later guys
[08:34] <antonio_> sorry for being so slow my computer is a bit slow i got to add some memory ;D
[08:35] <Besogon> What graphic card you have got? (nvidia, ati, intel)
[08:39] <antonio_> intel i think
[08:40] <antonio_> but am not sure
[08:40] <antonio_> how do i check?
[08:41] <antonio_> VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02)
[08:41] <antonio_> isn't the graphic card line?
[08:42] <antonio_> so its NTI and not intel
[08:43] <Besogon> !ati
[08:44] <Besogon> See that link
[08:59] <antonio_> hello am back
[09:00] <antonio_> i type the command, my screen went black and i had to restart it manually
[09:00] <antonio_> is it normal?
[11:25] <xenol> what's the default xubuntu cursor theme?
[11:26] <Sysi> dmz?
[11:27] <xenol> i am asking you, don't expect answer from me. i am not using debian based distros
[11:28] <Sysi> fedoras mouse theme is best
[11:28] <Sysi> but my wifi works only in debian baseds
[11:31] <xenol> also any idea what gtk engine do i need to use for albatross?
[12:35] <antonio_> is besogon around ?
[12:39] <antonio_> am back with my problem
[12:39] <antonio_> any helper?
[12:39] <Sysi> what's up?
[12:44] <antonio_> hi sysi
[12:44] <antonio_> can u help?
[12:45] <antonio_> me
[12:45] <antonio_> with my screen pb?
[12:46] <messiah> hello, which are the packages i need to install from the terminal in order to listen mp3 and watch youtube videos? i mean the exact name
[12:49] <antonio_> you can download vlc
[12:49] <antonio_> it has all the codecs required
[12:50] <antonio_> i think it sudo apt-get install vlc-nox
[12:50] <antonio_> try this
[12:51] <antonio_> go on the site of VLC u will have the exact command
[12:58] <antonio_> my connexion is very baaaaaaaaaad!!!!
[13:27] <_YeahRight> messiah: the codecs are in xubuntu extras package or something
[14:33] <wrgb> messiah: the package you need in Synaptic package manager is xubuntu-restricted-extras , this will install mp3 and flash support
[15:11] <Carabas> I have the following issue: I set xubuntu to boot into commandline. Now when I start X using the "startx"-command I have no sound in X. When I swich to a tty I can hear what is being played back under X. - Stange.
[15:11] <Carabas> Strange.
[15:50] <Carabas> Does anyone know how the sound is started in Karmic? I.e.: What scripts, what loads the driver (pulse)?
[15:54] <vinnl> Xubuntu doesn't come with PulseAudio
[15:54] <vinnl> It uses Alsa I believe
[16:10] <Carabas> "sudo /etc/init.d/alsa restart" results in "command not found". I guess it's pulse.
[16:11] <vinnl> Probably because Upstart is used instead of init
[16:11] <Carabas> Nevertheless; How do I start it manually?
[16:11] <vinnl> And: sorry, don't know yet :(
[16:11] <Carabas> jop
[16:12] <Carabas> I'd like to read in detail about upstart.
[16:12] <vinnl> !upstart
[16:12] <cody-somerville> there is no daemon afaik for sound like there is with pulseaudio
[16:12] <cody-somerville> you can't "stop and start" sound
[16:13] <Carabas> Ah, o.k.
[16:14] <Carabas> Thanks ubottu
[16:15] <vinnl> He's a bot :)
[16:15] <vinnl> !ubottu
[16:16] <vinnl> Anyway, I'm off, bye :)
[17:46] <petsounds> hi.. i need help, java applet won't run. http://imagebin.org/71446  :(
[17:47] <stevensj> Hi, has anyone used the xserver-xorg-video-openchrome package?  Any advice?
[17:58] <genii> The advice would be to avoid getting a system with some Via Chrome card in it to begin with
[18:27] <rtX_mancer42> ??
[19:11] <dan_> Hey there. Can anyone help with my xubuntu laptop screen resolution problem? Resolution is smaller than screen so I have a big black border.
[19:11] <dan_> Only options in display properties are 800x600 and below
[19:12] <dan_> Apparently there's no xorg.conf anymore...?
[19:15] <TheSheep> you can still create it and it will be used
[19:17] <dan_> How can I auto generate a new one? tried sudo dpkg-reconfigure xserver-xorg but nothing happens
[19:17] <genii> You don't need a complete one. If you have some stanza set which includes whatever you want to specify for settings you can use just that excerpt
[19:19] <dan_> I need to figure that bit out yet. Really old laptop, intel graphics, not sure of exact model.  :\
[19:31] <genii> lspci | grep VGA should tell the model
[19:38] <maddonline4352> hello together.. I'm a xubuntu newbe and i have troubles installing my usb wlan driver... can someone probably help me?
[19:40] <_Techie_> what usb wifi module is it?
[19:41] <maddonline4352> http://www.sitecom.com/support-product/productid/710#drivers
[19:42] <maddonline4352> alternatively i have got a pcmcia card from us robotics USR5411 .. but i think this one is more difficult to install i suppose
[19:43] <maddonline4352> so the first module is WL-608 BL - Wireless USB Adapter 54g by sitecom
[19:44] <_Techie_> have you tried ndiswrapper?
[19:45] <madddd223> but as i am linux newbe... i am not sure if id did everything right
[19:45] <madddd223> :/
[19:46] <_Techie_> what steps have you tried so far?
[19:46] <madddd223> well i successfully installed the ndiswrapper
[19:46] <madddd223> windows wlan support
[19:47] <madddd223> then i loaded the .inf file
[19:47] <madddd223> which was successful
[19:47] <madddd223> but
[19:47] <madddd223> the device wasn't found
[19:47] <_Techie_> have you removed and re inserted the device?
[19:47] <madddd223> yes!
[19:48] <madddd223> and i also rebooted twice
[19:48] <_Techie_> that answers that question
[19:48] <madddd223> why?
[19:48] <_Techie_> i was about to ask if yuou had tried rebooting
[19:49] <madddd223> ah ok =)
[19:49] <madddd223> well first of all thank you for responding to my issue!!
[19:50] <_Techie_> no problem, unfortunately i cant really help too much as i have had no experience with ndiswrapper, i anything i suggest is just a stab
[19:50] <_Techie_> so*
[19:50] <madddd223> yepp thank u anyways... u are certainlky more experienced than me. as it is the first time i try a linux os
[19:51] <_Techie_> the other alternative is to install the chipset drivers
[19:51] <madddd223> difficult?
[19:51] <_Techie_> there should be guides
[19:52] <madddd223> ok. i just ask u directly, is there any chance of similar linux OS, that could find the wifi drivers automatically?
[19:53] <_Pete_> madddd223: sure, do your own distribution
[19:53] <madddd223> :D
[19:53] <_Techie_> madddd223, http://www.ralinktech.com/license_us.php?n=2&p=0&t=U0wyRnpjMlYwY3k4eU1EQTVMekE0THpJMEwyUnZkMjVzYjJGa01ERTFPVGs0TmpRMk1DNWllakk5UFQweU1EQTVYekE0TWpCZlVsUXlPRGN3WDB4cGJuVjRYMU5VUVY5V01pNHlMakF1TUM1MFlYST1D
[19:56] <madddd223> ok thank u so far... what will be further proceeding?
[19:56] <_Techie_> not sure, i havent bothered to go past that page
[19:58] <madddd223> i just downloaded "2009_0820_RT2870_Linux_STA_V<IP_ADDRESS>.tar.bz2"
[20:00] <_Techie_> you will want to unpack that file
[20:01] <madddd223> sure. but is it the right chipset?
[20:01] <madddd223> or should i just give it a try
[20:01] <_Techie_> it should be, i would normally check a lspci but i already know that sitecom have masked the chipset name
[20:01] <_Techie_> lsusb*
[20:02] <_Techie_> anyone wanna buy me one of these? http://www.einfo.co.nz/shop/product_info.php?products_id=10240
[20:02] <marten_> Is there a way to revert my computer to the state it was, say, yesterday? I cant find anything about it anywhere, strangely enough
[20:03] <_Techie_> marten_, as far as i know, *buntu doesnt have any time machine software or system restore
[20:03] <marten_> How sad
[20:04] <marten_> The update to 9.10 didn't go as smoothly as I hoped
[20:04] <_Techie_> haha, join the club
[20:04] <madddd223> techie.. thank you so far... i will give it a try
[20:05] <marten_> My laptop isn't a laptop anymore, since I need to use an external mouse. No sound either, for that matter
[20:05] <marten_> I could of course use Vista, but i rather not
[20:06] <_Techie_> marten_, sounds more like a brick
[20:06] <_Techie_> marten_, and if you install vista it will become a cement truck
[20:06] <marten_> I dualboot, so its already there
[20:07] <_Techie_> why not dualboot XP
[20:07] <marten_> The updater said something about a partial installation of upgrades. Is there any way to see if I got everything intended?
[20:08] <marten_> Great, the colors are wrong playing videos
[20:10] <marten_> I dont have XP on disc, unfortunately
[20:15] <marten_> Otherwise, is there a way to run the 9.10-update again?
[20:17] <_Techie_> marten_, im not entirely sure but perhaps sudo apt-get upgrade or sudo apt-get dist-upgrade might do the trick
[20:17] <marten_> Will try
[20:18] <marten_> No
[20:18] <marten_> It seems to think that everything is there
[20:18] <marten_> I will have to fix this another day
[20:18] <marten_> Thanks for everything
[20:48] <Balsaq> _Techie_wauup
[20:48] <Balsaq> wassup i meant
[20:49] <alienkid10> I followed the instructions here: https://help.ubuntu.com/community/LiveCDCustomizationFromScratch but I don't get a boot menu like on the offical liveCD how can I get a boot menu not a prompt?
[20:50] <Balsaq> same here!
[20:50] <Balsaq> i think we have to go into bios and change the boot order?
[20:50] <alienkid10> no
[20:50] <alienkid10> I can get the disc to boot
[20:50] <Balsaq> i cannot
[20:50] <alienkid10> but can't get a menu
[20:50] <alienkid10> then yes
[20:50] <alienkid10> you have to go to BIOS
[20:50] <alienkid10> I test in Vbox
[20:51] <Balsaq> hmmmm...didnt want to mess around in there, this particular computer has a nice xp install on it
[20:52] <Balsaq> when i go in, it tap f2 a lot to get a menu?
[20:52] <alienkid10> then boot off CD
[20:53] <Balsaq> can i boot off cd without messin round in bios?
[20:53] <alienkid10> depends
[20:53] <Balsaq> do i start by tapping f2 or f12
[20:53] <alienkid10> just change the boot order
[20:53] <alienkid10> I use Vbox to test CD before burn
[20:53] <alienkid10> depends
[20:53] <Balsaq> i already burned it so i got what i got now
[20:54] <alienkid10> I don't know your BIOS/computer so I can't help with BIOS specific problems
[20:55] <Balsaq> weel i have a few of these and they all booted ubuntu stuff before no prob
[20:55] <Balsaq> but they were clean before i booted buntu..the hd had been wiped clean
[20:55] <Balsaq> this has xp on it
[20:56] <alienkid10> wait
[20:56] <alienkid10> what exactly is your problem?
[20:57] <Balsaq> i put cd in  trey (one i just made of xubuntu) and am trying to run xubuntu fro the cd...in my xp computer and have not been able to get it going as of yet
[20:57] <Balsaq> want to run a live cd as they say without touching-harming xp
[20:57] <_Techie_> alienkid10, try re installing grub, i have had similar problems in persistant USB installs where grub defaults to its command line
[20:57] <alienkid10> how?
[20:58] <alienkid10> on the CD?
[20:58] <_Techie_> yeah
[20:58] <alienkid10> (.iso)
[20:58] <_Techie_> there should be a command grub-install
[20:58] <Guest20454> !it
[20:58] <alienkid10> in a chroot?
[20:58] <Guest20454> bene!!
[20:59] <_Techie_> Balsaq, run the wubi installer, install it inside of windows then you can remove it at your will
[21:00] <Balsaq> oh ok...thought i could just toss it in t here and run it
[21:00] <_Techie_> yeah you can, but the wubi install will give a faster system than a livecd
[21:00] <Balsaq> just wanted too see if i burned it correctly...made it for my sister
[21:01] <Balsaq> already have a nice xubu set up in the basement
[21:01] <Balsaq> when i burned it i chose ISO image and set my burn speed to 8x
[21:02] <Balsaq> so hopefully thats correct
[21:02] <alienkid10> I ran grub-install in chroot now resquash and iso?
[21:12] <alienkid10> _Techie_?
[21:12] <_Techie_> huh
[21:12] <alienkid10> I ran grub-install in chroot now resquash and iso?
[21:12] <_Techie_> i would think so
[21:12] <_Techie_> the other alternative is syslinux
[21:13] <alienkid10> whoops
[21:13] <_Techie_> http://syslinux.zytor.com/wiki/index.php/The_Syslinux_Project
[21:13] <alienkid10> I think I am using isolinux
[21:14] <_Techie_> then read up on this
[21:14] <_Techie_> http://syslinux.zytor.com/wiki/index.php/ISOLINUX
[21:14] <alienkid10> y tree is: casper install and isolinux
[21:14] <alienkid10> so yeah
[21:15] <alienkid10> where do I get isolinux.bin and .cfg?
[21:16] <_Techie_> no clue, never worked with isolinux other than booting livecd's
[21:16] <_Techie_> you might want to look for some more help in #syslinux
[21:17] <alienkid10> ok