[06:05] <JDStone> when a friend of mine unplugs his power adapter from his laptop, it goes into standby, any ideas?
[07:18] <pitti> Good morning
[07:51] <didrocks> pitti & mvo : morning o/
[07:51] <mvo> hey didrocks
[07:56] <pitti> hey didrocks
[08:12]  * Amaranth tries again here
[08:12] <Amaranth> $ ls -lh /var/log/syslog
[08:12] <Amaranth> -rw-r----- 1 syslog adm 329M 2009-03-11 02:50 /var/log/syslog
[08:12] <Amaranth> pulseaudio can stop DoS'ing me now
[08:12] <pitti> ^  see #ubuntu-devel
[08:25] <pitti> seb128: bonjour
[08:25] <seb128> hello pitti
[08:25] <pitti> seb128: I looked at the log for bug 340508
[08:25] <pitti> seb128: "Report is a duplicate of #329289 (not fixed yet)"
[08:26] <pitti> seb128: I guess marking as duplicate failed because the alleged master bug is also a duplicate
[08:26] <pitti> seb128: I thought I fixed that a while, but it seems that something broke there
[08:26] <seb128> pitti: wasn't it supposed to follow the chain of duplicates?
[08:26] <pitti> s/a while/& ago/
[08:27] <seb128> slomo: hey, let me know when you are around to talk about this gst bug ;-)
[08:38] <seb128> slomo: new bug for you
[08:38] <seb128> slomo: https://bugs.edge.launchpad.net/bugs/340800
[08:38] <seb128> ups
[08:38] <seb128> slomo: http://bugzilla.gnome.org/show_bug.cgi?id=574898
[08:39] <seb128> slomo: this one has a debug stacktrace with gst-ffmpeg rebuilt to not use the system copy
[08:40] <seb128> slomo: I'm looking at getting infos for the other one, you don't get the "WARNING **: Failed to retrieve channel layout from caps." either
[08:41] <slomo> i'll take a look
[08:41] <slomo> that warning is not a problem though
[08:41] <seb128> slomo: in fact those have the same stacktrace
[08:41] <seb128> slomo: http://bugzilla.gnome.org/show_bug.cgi?id=574870 updated too
[08:42] <seb128> slomo: we get a lot of similar crashers in jaunty, I reassigned 15 at least this week, sirestart says those are rather gst-ffmpeg bugs than ffmpeg since ffplay doesn't have the issue
[08:43] <slomo> yeah, looks familiar... could you retry with gst-ffmpeg from debian/unstable? at least the aac bug is fixed there, the memset() one probably too
[08:43] <seb128> slomo: the one uploaded yesterday? I synced whatever was current some days ago
[08:44] <seb128> slomo: trying
[08:44] <seb128> slomo: btw should be sync the new gst-plugins-ugly version? ;-)
[08:44] <slomo> yes, the one i've uploaded yesterday
[08:45] <seb128> slomo: building it locally to try right now
[08:45] <slomo> not sure... you should sync ugly/bad/ffmpeg if possible but there are new features and a million bugfixes ;)
[08:45] <seb128> slomo: we still have over a month before jaunty and those are in universe, seems rather a good deal to get the million bugfixes
[08:45] <seb128> what do you think?
[08:47] <seb128> slomo: ok, new gst-ffmpeg fixes those bugs, let me close them now ;-)
[08:47] <slomo> then sync it... there's a known regression with seeking in mpeg files in -bad but a patch is already in bugzilla and will be in next pre-release on friday
[08:47] <seb128> ok good
[08:49] <seb128> slomo: oh and did you read bugs about dvd playing in totem-gstreamer not working with current versions?
[08:51] <slomo> seb128: no... what are the symptoms?
[08:51] <seb128> slomo: let me look at the bugs
[08:52] <seb128> slomo: hum, http://launchpadlibrarian.net/23125176/gst-plugins-bad0.10_0.10.10-1_0.10.10-1ubuntu1.diff.gz, somebody uploaded that to ubuntu ... would it make sense to get into debian too?
[08:52] <seb128> the new celt is not in debian
[08:52] <slomo> seb128: oh, no but it should go upstream :)
[08:53] <seb128> right
[08:53] <slomo> damn, i've assigned myself to the bug with that patch and forgot about it
[08:53] <slomo> :=
[08:53] <slomo> :)
[08:54] <didrocks> hey seb128 o/
[08:54] <didrocks> and slomo too ;)
[08:54] <seb128> hey didrocks
[08:54] <seb128> didrocks: could you resync gst-plugins-bad0.10 on debian? it's in universe so you can upload
[08:54] <slomo> hi didrocks
[08:54] <seb128> didrocks: there is just the trivial change I pointed to apply over the new version
[08:55] <didrocks> seb128: no pb, will do it a little later. "trivial change I pointed to apply"?
[08:56] <seb128> didrocks: cf the diff.gz url I copied some lines ago
[08:56] <didrocks> seb128: ok, I'm backlogging :)
[08:59] <pitti> bonjour didrocks
[08:59] <seb128> slomo: bug #338321 is the dvd issue, I need to test there
[09:20] <seb128> pitti: you broke gnome-utils!
[09:20] <pitti> oh, uh, what?
[09:21] <seb128> pitti: the current version doesn't do schemas registration at all in its postinst -> gnome-system-log crash on start with fresh config
[09:21] <seb128> pitti: I'm looking into it
[09:22] <pitti> seb128: is that dh_gconf?
[09:22] <seb128> pitti: yes
[09:22] <pitti> darn, sorry
[09:22] <pitti> I did debdiff, but didn't compare postinst
[09:22] <pitti> seb128: want me to fix it?
[09:22] <seb128> pitti: that's ok, I'm on it ;-)
[09:22]  * pitti hugs seb128, merci
[09:23] <pitti> seb128: darn, then I need to go back putting together the new gnome-themes-extras and wrestle with autobreak
[09:23] <seb128> pitti: you're welcome
[09:23] <pitti> seb128: perhaps gnome.mk should add dh_gonf..
[09:23] <seb128> pitti: good luck with that
[09:23] <seb128> pitti: it does, I'm looking at why that doesn't work ...
[09:23] <pitti> seb128: I'll need it
[09:23] <lool> asac: help!
[09:23] <lool> asac: My wlan1 wifi card is now seen as unmanaged
[09:23] <lool> asac: And I can't get it to be managed by NM again
[09:24] <lool> asac: I had it in /etc/network/interfaces for some minutes this morning, but even with everything commented out in /e/n/i, NM still says it's unmanaged
[09:24] <seb128> pitti: I'm wondering if that's due to the cdbs rules order, I think gnome.mk needs to be after debhelper.mk
[09:24]  * seb128 tries
[09:24] <lool> asac: I thought it cached this somewhere, but can't find where
[09:24] <pitti> seb128: ah, good point
[09:25] <pitti> seb128: I'm used to put the class first, and then the rules, but indeed that might not work with current gnome.mk
[09:25] <asac> lool: sudo killall nm-system-settings
[09:26] <asac> and yes. NetworkManager init should get a "reload" command
[09:26] <pitti> seb128: gnome.mk should perhaps do them in binary-post-install then, but if flipping include order around, it's fine for now
[09:26] <pitti> seb128: binary-install calls dh_install
[09:27] <pitti> seb128: could you try changing binary-install/%: to binary-post-install/%: in /usr/share/cdbs/1/class/gnome.mk and a no-change rebuild of gnome-utils?
[09:27] <pitti> seb128: I'm just afraid that there might be other packages which have that trap
[09:27] <seb128> pitti: lemme try
[09:28] <lool> asac: THANKS!
[09:29] <lool> asac: I don't quite understand why restart doesn't do that though?
[09:30] <asac> lool: because thats how it is ;) ... its definitly a missing feature and should be done, yes.
[09:34] <lool> asac: Ok; thanks!
[09:36] <seb128> hum
[09:36] <seb128> didrocks, mvo, pitti:
[09:36] <seb128> bzr: ERROR: No module named bzrtools.upstream_import
[09:36] <seb128> You may need to install this Python library separately.
[09:37] <seb128> what do I do to fix that?
[09:37] <seb128> pitti: the cdbs change you suggested makes not difference
[09:38]  * pochu didn't know the "check for notifications" patches are not UI changes :-)
[09:38] <pitti> seb128: does dh_gconf get called in the build log at all?
[09:38] <pochu> so no UI freeze exception required
[09:38] <pitti> seb128: bzr error> what did you try?
[09:38] <seb128> pitti: bzr-buildpackage
[09:38] <seb128> pitti:
[09:38] <seb128> $ grep dh_gconf gnome-utils_2.25.92-0ubuntu2_i386.build
[09:39] <seb128> $
[09:39] <seb128> pitti: I did dist-upgrade yesterday, perhaps another python-* screwage
[09:41] <mvo> anyone familar with the latest pycentral ? it complains loudly that Python-Versions is not defined, yet I do define it in the debian/control file (trying to fix python-ropemacs)
[09:41] <seb128> mvo: don't talk to me about python, that's not good for my nerves ;-)
[09:42] <seb128> mvo: btw if you have any idea about the bzr-buildpackage error I just copied ...
[09:42] <seb128> james_w: ^
[09:42] <pitti> seb128: hm, works here..
[09:43] <mvo> seb128: you have the latest bzrtools installed I assume :) ?
[09:43] <seb128> $ python -c 'import bzrtools'
[09:43] <seb128> Traceback (most recent call last):
[09:43] <seb128>   File "<string>", line 1, in <module>
[09:43] <seb128> ImportError: No module named bzrtools
[09:43] <mvo> grrrrr python grrr
[09:43] <seb128> $ dpkg -l bzrtools | grep ^ii
[09:43] <seb128> ii  bzrtools
[09:43] <seb128> current version yes
[09:43] <mvo> heh :)
[09:43] <seb128> hate hate python
[09:43] <mvo> maybe its yet anohter python crazyness
[09:44] <mvo> what does ls -l /usr/lib/python2.6/dist-package/bzrtools show?
[09:44] <seb128> $ ls -l /usr/lib/python2.6/dist-package/bzrtools
[09:44] <seb128> ls: cannot access /usr/lib/python2.6/dist-package/bzrtools: No such file or directory
[09:44] <mvo> hm
[09:45] <mvo> try bzrlib ?
[09:45] <seb128> that works
[09:45] <mvo> and there plugins (in that
[09:45] <seb128> $ python -c "import bzrlib"
[09:45] <mvo> is there a dir for bzrtools ?
[09:45] <seb128> $
[09:45] <seb128> doh, typo in your line
[09:45] <mvo> oh, sorry
[09:46] <seb128> no bzrtools dir
[09:46] <seb128> are you interested to debug that or should I just reinstall the package?
[09:46] <seb128> I guess that will fix it
[09:47] <mvo> seb128: a moment of debugging would be nice
[09:47] <mvo> seb128: what is the output of dpkg -L bzrtools ? could you pastebin that?
[09:48] <seb128> $ ls /usr/lib/python2.6/dist-packages/bzrlib/plugins/bzr*
[09:48] <seb128> ls: cannot access /usr/lib/python2.6/dist-packages/bzrlib/plugins/bzr*: No such file or directory
[09:48] <mvo> ls -l /usr/lib/python2.6/dist-packages/bzrlib/plugins
[09:48] <mvo> woah
[09:48] <seb128> $ dpkg -L bzrtools | grep pyshared | grep bzrtools
[09:48] <seb128> /usr/share/pyshared/bzrlib/plugins/bzrtools
[09:48] <seb128> ...
[09:48] <mvo> so python did not create the symlinks for you
[09:49] <seb128> I did clean python2.4 yesterday
[09:49] <seb128> and he did a bunch of "refreshing symlinks" round
[09:49] <seb128> he -> it
[09:49] <seb128> I'm wondering if that broke those
[09:49] <mvo> heh
[09:49] <mvo> could you check /var/log/apt/term.log ?
[09:49] <seb128> clean = sudo apt-get autoremove
[09:49] <mvo> that would be fun indeed
[09:50] <seb128> Unlinking and removing bytecode for runtime python2.4
[09:50] <seb128> ...
[09:50] <seb128>     bzrtools: >= 2.4 (['install', 'ok', 'installed'])
[09:50] <seb128> but not details
[09:51] <mvo> let me try it here
[09:51] <mvo> just go ahead with the reinstall, but it might be worthwhile to report a bug
[09:52] <mvo> I don't think you are the only one who will run into it
[09:52] <seb128> mvo: I don't really need it right now so I can keep it broken for the day
[10:03] <mvo> I think I found the problem now, if there is a version installed with Python-version, pycentral is unable to recover *ever* it seems
[10:03] <seb128> what?
[10:03] <mvo> and bonus points for dpkg --remove --force-all python-ropemacs not work too
[10:03] <seb128> mvo: you get the bug too?
[10:03] <mvo> this is a different one
[10:03] <mvo> with python-ropemacs
[10:04] <mvo> that fails to install/remove everything for me
[10:04] <crevette> seb128, if you update gnome-icon-theme, it seems there is a bug where the spinner name has changed, and may broke for application using it
[10:04] <seb128> crevette: I'm not main is frozen for alpha6 mostly now
[10:04] <mvo> but like i said, not just "fail", break everything forever
[10:04] <seb128> urg
[10:05] <crevette> :)
[10:05] <seb128> mvo: if you open a bug can you give me the number please
[10:05] <seb128> crevette: can you let dobey know so it's fixed for 2.26?
[10:05] <crevette> we're still investagating on #gnomefr :)
[10:05] <mvo> seb128: its a different one from what you have
[10:05] <seb128> mvo: ok
[10:14] <mvo> its even better, the package can not even be upgraded to a fixed version
[10:14] <seb128> ...
[11:03] <crevette> seb128, about the g-icon-theme problem, the bug was on nemiver code
[11:04] <seb128> crevette: ok good
[12:06]  * kenvandine waves
[12:29] <pochu> +				if (strcmp ((char*)c->data, "actions")) {
[12:29] <pochu> +					supports_actions = TRUE;
[12:29] <pochu> I think I missed an "!" in that if...
[12:29] <pochu> I was getting crazy as to why Liferea keeped showing those weird dialogs :)
[12:35] <kenvandine_wk> pochu: hehe
[12:35] <kenvandine_wk> bryce: i see your intel driver build failed in  your ppa
[12:36] <kenvandine_wk> bryce: no rush... but is that something you are going to fix soon?
[12:36] <pochu> kenvandine_wk: btw slangasek has told me he doesn't things this changes need UI exceptions FWIW
[12:36]  * kenvandine_wk is trying to decide if he wants to edit his xorg.conf or not :)
[12:36] <kenvandine_wk> pochu: ok
[12:40] <pochu> kenvandine_wk: it was exactly that, works fine now :)
[12:45] <pochu> seb128, asac: hi, could you have a look at my liferea update? The new upstream release is bugfix-only, it works fine here, and the notifications patch seems to DTRT :) http://emilio.pozuelo.org/~deb/liferea_1.4.26-0ubuntu1.dsc
[12:47] <asac> pochu: i can look after lunch. waiting for someone to pick me up so not sure yet when that will be (hopefully soon ;))
[12:48]  * kenvandine_wk is happy that his new laptop is much faster than his desktop :)
[12:48]  * kenvandine_wk hugs the t400!
[12:50] <pochu> asac: no hurry, thanks!
[12:50] <asac> pochu: why didnt upstream include the patch?
[12:50] <pochu> asac: it's in trunk only
[12:51] <asac> pochu: k
[13:04] <kenvandine_wk> seb128: ping
[13:04] <seb128> kenvandine_wk: hi
[13:04] <kenvandine_wk> hey
[13:05] <kenvandine_wk> so libgda4.0, there are symbols removed without versioned sonames
[13:05] <kenvandine_wk> just for the providers
[13:05] <kenvandine_wk> -rw-r--r-- 1 0 0 146480 2009-03-10 16:11 libgda-mysql.so
[13:05] <kenvandine_wk> -rw-r--r-- 1 0 0 204020 2009-03-10 16:11 libgda-postgres.so
[13:05] <kenvandine_wk> -rw-r--r-- 1 0 0   5352 2009-03-10 16:11 libgda-sqlite.so
[13:06] <seb128> where are those installed?
[13:06] <seb128> if they are not public libraries that's ok
[13:06] <kenvandine_wk>  /usr/lib/libgda-4.0/providers/
[13:07] <seb128> ok, not an issue, they do what they want with their private code
[13:07] <kenvandine_wk> okie dokie
[13:07] <seb128> good that you are checking for such changes though ;-)
[13:07] <kenvandine_wk> :)
[13:07]  * kenvandine_wk attaches a diff
[13:07] <slomo> didrocks: if you merge gst-plugins-bad you also want to get http://bugzilla.gnome.org/show_bug.cgi?id=574009
[13:07] <slomo> seb128: you also might want to sync gnonlin :)
[13:08] <seb128> slomo: thanks
[13:10] <kenvandine_wk> seb128: what's the easiest way to see if something comes from main or universe?
[13:10] <kenvandine_wk> or from some ppa for that matter
[13:11] <seb128> kenvandine_wk: locally?
[13:11] <kenvandine_wk> yeah
[13:11] <seb128> kenvandine_wk: apt-cache madison source or apt-cache policy source
[13:11] <seb128> ups binary in the second case
[13:12] <kenvandine_wk> ah
[13:12] <kenvandine_wk> ok
[13:12] <kenvandine_wk> thx
[13:13] <seb128> you're welcome
[13:13] <kenvandine_wk> anyone know what the proper behavior is for the gnomecompat compiz plugin?
[13:14] <kenvandine_wk> it looks like it just implements some similar behavior
[13:14] <kenvandine_wk> but stores it's own keybindings and such
[13:14] <kenvandine_wk> as opposed to just reading the gnome gconf settings
[13:14] <kenvandine_wk> which seems sub-optimal
[13:16] <seb128> hey rickspencer3
[13:16] <kenvandine_wk> morning rickspencer3!
[13:16] <seb128> kenvandine_wk: mvo is the one who probably knows best about that
[13:16] <seb128> or Amaranth
[13:16] <kenvandine_wk> mvo: ping
[13:16] <didrocks> slomo: thanks, noted. I will do it this evening :)
[13:17]  * kenvandine_wk goes to refill the coffee... this time change is kicking my butt
[13:17] <mvo> kenvandine_wk: pong
[13:17] <rickspencer3> seb128: kenvandine_wk: mvo: good morning!
[13:18] <rickspencer3> kenvandine_wk: do you have virtualization set up on your desktop?
[13:18] <mvo> hey rickspencer3
[13:19] <rickspencer3> mvo: seb128: if kenvandine_wk sets up a VM with with Jaunty, can he use that to test various permutations of your upgrade script for notify-osd/indicator-applet?
[13:19] <kenvandine_wk> rickspencer3: i can now that i have my new laptop :)
[13:19] <didrocks> slomo: I will also try to get the harvest low hanging fruits, if applicable
[13:20] <kenvandine_wk> mvo: read back for my question about the gnomecompat compiz plugin please
[13:20]  * kenvandine_wk cries over an empty coffee pot
[13:20] <rickspencer3> kenvandine_wk: get some more coffee, you may need it
[13:20] <kenvandine_wk> rickspencer3: gonna be a rough day?
[13:20] <kenvandine_wk> hehe :)
[13:20] <seb128> rickspencer3: I guess he could yes but that would tedious work, ie having to get the old version, do random config, upgrade, clean everything back and try other combinaisons
[13:21] <mvo> kenvandine_wk: it should sync the settings back and forth
[13:21] <kenvandine_wk> mvo: oh  so it should read the settings from gnome?
[13:21] <kenvandine_wk> ok, that isn't working then :)
[13:22] <kenvandine_wk> seb128: not hard... just need to give me some use cases to test :)
[13:22] <rickspencer3> seb128: is there a better way to test it?
[13:22] <mvo> kenvandine_wk: but the plugin is enabled?
[13:22] <kenvandine_wk> "screw it up this way" and update
[13:22] <kenvandine_wk> mvo: yes
[13:22] <seb128> rickspencer3: push it early and wait for users to complain if it breaks? ;-)
[13:22] <kenvandine_wk> if i change the settings in the keyboard shortcuts, the plugin doesn't get them
[13:22] <rickspencer3> with a VM, he could take snapshots, so it's trivial to get back to a known state
[13:22] <rickspencer3> seb128: hmmm
[13:22] <seb128> rickspencer3: that's only a gnome-panel layout if it's messed up on upgrade for beta users that no big deal imho
[13:22] <kenvandine_wk> rickspencer3: i think we can test it a little before pushing it :)
[13:23] <mvo> where is the upgrade script currently living?
[13:23] <seb128> mvo: gnome-panel
[13:23] <rickspencer3> ok ... I'm putting it out there as an option
[13:23] <mvo> and you guys take care of it?
[13:23] <rickspencer3> but I would like to see some testing if it's feasible (don't know what else kenvandine_wk is booked in for)
[13:23] <seb128> mvo: I took over the task and said I would work on that with you today
[13:23] <mvo> heh :)
[13:23] <seb128> mvo: morning has been busy but see query
[13:24] <kenvandine_wk> rickspencer3: the keyboard shortcuts with compiz and the s-c-p patch making it upstreamable...
[13:24] <kenvandine_wk> are the main things
[13:24] <mvo> seb128: ok, we can work on it in a bit, need to finish some other stuff first
[13:24] <seb128> mvo: thanks
[13:24] <kenvandine_wk> i also need to fix a build for intrepid for the OLS guys
[13:24] <seb128> then we can organize for testing
[13:25] <kenvandine_wk> mvo: mind taking a quick look at the gnomecompat plugin to see if you can figure out what broke?
[13:27] <kenvandine_wk> rickspencer3: most of the time involved with that kind of testing is the setup time... which is mostly idle
[13:27] <kenvandine_wk> so i can be working on other things too
[13:28] <rickspencer3> kenvandine_wk: it's actually pretty handy to a VM set up anyway
[13:28] <kenvandine_wk> rickspencer3: i am big on VMs :)
[13:28] <kenvandine_wk> one of the reasons i wanted this new laptop :)
[13:29] <rickspencer3> also, I was hoping that maybe you could look ensuring the the indicator-applet works in various permutations and log bugs where it does not
[13:29] <kenvandine_wk> needed a box with VT support :)
[13:29] <kenvandine_wk> rickspencer3: i have already logged some bugs there :)
[13:31] <kenvandine_wk> unrelated question... on a fresh install, what should i have to do to get the codecs needed for mp3?
[13:31] <kenvandine_wk> on my last install i don't recall doing anything...
[13:31] <rickspencer3> kenvandine_wk: seb128: pitti: https://wiki.ubuntu.com/DesktopTeam/Meeting/JauntyIndictorAppletTestCases
[13:31] <kenvandine_wk> so figured we had some codec buddy kind of thing
[13:31] <seb128> rickspencer3: thanks
[13:31] <rickspencer3> kenvandine_wk: ubuntu-restricted-extras
[13:32] <soren> kenvandine_wk: We used to have something pop up and tell you that you needed extra stuff to do it.
[13:32] <seb128> kenvandine_wk: double click on a mp3, totem is started and should ask if you want to install whatever is required
[13:32] <soren> kenvandine_wk: ...in totem, at least.
[13:32] <kenvandine_wk> seb128: i just tried that
[13:32] <kenvandine_wk> got an error playing stream
[13:32] <kenvandine_wk> didn't trigger anything
[13:32]  * kenvandine_wk found a bug i guess
[13:33] <seb128> kenvandine_wk: anything printed on the command line?
[13:33] <kenvandine> ** Message: Error: Failed to connect stream: Invalid argument
[13:33] <kenvandine> pulsesink.c(836): gst_pulsesink_prepare (): /GstPlayBin:play/GstBin:visbin/GstBin:abin/GstBin:audiosinkbin/GstGConfAudioSink:audio-sink/GstBin:bin5/GstAutoAudioSink:autoaudiosink1/GstPulseSink:autoaudiosink1-actual-sink-pulse
[13:34] <seb128> that seems a pulseaudio issue and not a codec one
[13:34] <seb128> are you sure you lack the codecs?
[13:34] <kenvandine> no i am not
[13:34] <mvo> kenvandine: if you want to diagnose gnomecompat,that is fine with me :)
[13:34] <kenvandine> just installed this thing :)
[13:34] <seb128> kenvandine: is pulseaudio running?
[13:34] <kenvandine> yes
[13:35] <seb128> hum
[13:35] <seb128> can you paplay /usr/share/sounds/question.wav?
[13:36] <kenvandine> this is interesting... the login sound played when i logged in
[13:36] <kenvandine> but
[13:36] <kenvandine> canberra-gtk-play -i desktop-login
[13:36] <kenvandine> ALSA lib pcm_pulse.c:626:(pulse_prepare) PulseAudio: Unable to create stream: Invalid argument
[13:36] <kenvandine> Failed to play sound: IO error
[13:36] <seb128> iz pulse bog
[13:36] <kenvandine> ALSA lib pcm_pulse.c:626:(pulse_prepare) PulseAudio: Unable to create stream: Invalid argument
[13:36] <kenvandine> yeah
[13:36] <kenvandine> definately pulse
[13:36] <kenvandine> i got that from paplay
[13:37] <seb128> try restarting pulse and see what happens
[13:37] <kenvandine> ok
[13:37] <kenvandine> can i just HUP it?
[13:38] <kenvandine> ok
[13:38] <kenvandine> that worked
[13:38]  * kenvandine guesses there is no way to find out how it got in that statu
[13:38] <kenvandine> state
[13:38] <seb128> wait and see if that happens again
[13:39] <kenvandine> will do
[13:51] <ripps> Does anybody know where I can get some documentation on the Gnome dbus multimedia keys framework?
[13:55] <mvo_> seb128, hi, sorry. nm killed my network
[13:55] <mvo_> seb128, I have the migration stuff in front of me now, what exactly needs to be done?
[13:55] <mvo_> just adding the indicator applet? if so, where?
[13:56] <seb128> mvo_: re
[13:56] <seb128> mvo_: next to the notification area if I understood those guys correctly
[13:56] <seb128> pitti: ^ can confirm that?
[13:57] <seb128> davidbarth: ^ or you?
[13:57] <seb128> mvo_: bug #340777
[13:57] <kenvandine_wk> seb128: it is just to the right of the notification area on this clean install
[13:58] <seb128> mvo_:
[13:58] <seb128> "It should be inserted at the end of the applet stack as much as possible and aligned right. So, it should appear slightly to the left of the notification area. This isn't the default placement with a clean install, but it should make the insertion MUCH easier and has been deemed good for putting it on the panel."
[13:59]  * dobey wonders why the message indicator isn't just a notification area icon anyway :)
[14:00] <seb128> dobey: their design has no notification area I think
[14:00] <seb128> dobey: ie they are getting ride of it not adding new icons to it
[14:05] <dobey> nm-applet and gnome-power-manager are being replaced?
[14:05] <ripps> C'mon, does anybody know how to make a plugin that uses gnome multimedia keys?
[14:07] <seb128> dobey: not this cycle but they plan to rewrite a panel and might have different indicators for those
[14:08] <dobey> oh you mean gnome-shell, or something else?
[14:09] <seb128> dobey: I don't know the details of their plan, just somebody mentionned that they want less icons in the notification area over time and not add new ones there
[14:09] <dobey> *shrug*
[14:10]  * vuntz wonders who is "they"
[14:10] <seb128> vuntz: the canonical dxteam
[14:10] <dobey> vuntz: well it's apparently not a superset of 'me'
[14:11] <vuntz> seb128: so they plan to rewrite a panel. No joke?
[14:11] <seb128> vuntz: not sure what the plan are but I understood from the boston submit previous year that the gnome-shell etc idea was that no?
[14:11] <mvo_> rewriting seems to be en-vouge currently
[14:12] <vuntz> seb128: if it's gnome-shell, then okay. I was just afraid that it'd be something else
[14:12]  * mvo_ should rewrite something too
[14:12] <seb128> ok good ;-)
[14:12] <vuntz> mvo_: apt?
[14:12] <seb128> mvo_: update-manager in C? ;-)
[14:12] <mvo_> heh :)
[14:15] <mvo_> seb128, hm, I guess we need to keep the migrate fusa stuff around too because of lts->lts upagrdes?
[14:15] <mvo_> maybe we should just fold it into that ...
[14:17] <seb128> mvo_: yes
[14:26] <seb128> pitti: do you think we could speed up the proposed to updates delay for pidgin?
[14:29] <pitti> seb128: yes, absolutely
[14:29] <seb128> slomo: http://launchpadlibrarian.net/23748365/heineken_commercial.wmv not playing at the right speed do you know if that's a known bug?
[14:29] <pitti> seb128: got a call now, TTYL
[14:29] <seb128> slomo: ie if there is something about that in bugzilla, not easy to figure to what other bug that can correspond
[14:29] <seb128> pitti: ok, see you
[14:30] <slomo> seb128: works here
[14:31] <seb128> slomo: using debian versions or trunk?
[14:31] <slomo> seb128: debian versions and trunk
[14:32] <slomo> how fast does it play? is it only very slightly faster/slower?
[14:32] <seb128> slomo: bah, on the first try it looked twice the speed and now it works ...
[14:34] <seb128> slomo: ok, seems to be a totem buffering issue or something
[14:34] <seb128> slomo: I played from the website directly first time and it buffered for some seconds and played very fast the start of the video then
[14:35] <slomo> probably... i saw this for other files too when it has to buffer a lot in the beginning
[14:35] <slomo> but that's a gst bug then, no totem bug
[14:36] <seb128> slomo: right, "gst-launch playbin uri=http://launchpadlibrarian.net/23748365/heineken_commercial.wmv" behaves the same way
[14:43] <mvo_> asac, haha, n-m shows me a wirless network indicator in my kvm virtual machine. that is cute .) is that a known issue?
[14:43] <asac> mvo_: lol
[14:43] <mvo_> asac, signal strengh is zero (unsuprissingly)
[14:44] <asac> mvo_: see -devel-discuss thread
[14:44] <asac> mvo_: dx team found its much more intuitive to use that for no connnection
[14:44] <seb128> mvo_: design team decided that not connected == signal 0
[14:44] <asac> mvo_: so they updated the human theme
[14:44] <asac> mvo_: just use a different theme ;)
[14:44] <asac> i dont have this problem because i dont even have gnome-settings-daemon running to do font stuff ;)
[14:45] <seb128> I found it pretty confusing too
[14:45] <mvo_> really?
[14:45] <mvo_> thats a joke?
[14:45] <asac> mvo_: no.
[14:45] <seb128> mvo_: no, read the list discussion
[14:45] <mvo_> lol
[14:45] <asac> mvo_: thats what was found by dx folks
[14:45] <asac> mvo_: they said its clear for users: no signal == no connection
[14:45] <seb128> that's what you get when you let designer decide on technical things I guess ;-)
[14:46] <asac> i tried to prevent that since this idea came up
[14:46] <mvo_> geh, its better and better
[14:46] <asac> but they say it works on Mac OSX  .... even though i am not sure why they think that our previous icon doesnt work ;)
[14:46] <seb128> mvo_: they somewhat agreed that adding a red cross on the icon could make sense after the discussion on the list though
[14:46] <seb128> so let's see
[14:46] <mvo_> I see. if it is used on macosx it must be perfect
[14:46] <asac> actually i know how this started, but i wont go in details here
[14:46] <seb128> mvo_: ;-)
[14:46] <asac> mvo_: read the thread and comment
[14:47] <seb128> mvo_: we have never used macOS so we can't understand I guess
[14:47] <asac> i suggested to skip this step, and do the right solution instead of having a confusing icon for a full cycle
[14:47] <asac> i would be fine if this would be a final solution. but they agreed that there are better solutions, so i dont understand why its still done ;)
[14:48] <mvo_> so this is not what we will release?
[14:48] <mvo_> or is the plan to fix it in jaunty+1?
[14:48] <asac> mvo_: we will releasae and (i hope) agree on the better solution i suggested for karmic
[14:49] <asac> unless i find time and do a heroic act of doing the right solution this cycle i guess ;)
[14:50] <seb128> mvo: they agreed to add a red cross on the 0 signal icon I think
[14:50] <mvo> aha, ok
[14:50] <mvo> that would make it better (also at least to me it would still be confusing, but less so)
[14:51] <asac> yeah red cross is better.
[15:03] <pitti> kenvandine_wk: hey, good morning
[15:03] <kenvandine_wk> hey pitti
[15:04] <allquixotic> Can anyone hug a desktop-related bug me for please? I know it's not hug day, and this isn't the target of the next hug day, but it's a crasher bug in a popular app :) https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/341155
[15:05] <seb128> allquixotic: not a lot to do right now, the bug is not closed upstream yet
[15:06] <pitti> seb128: okay, we have several thumbs-up for pidgin, I copy now
[15:07]  * seb128 hugs pitti
[15:09] <allquixotic> seb128: True, we don't have the "real" fix, but we have a hotfix that fixes the crasher -- I get a few warning messages on Pidgin startup, but they aren't recurring. I think that beats a crasher. I'm not saying "commit the hotfix now!" but as a contingency -- worst case, Pidgin devs do nothing -- do we ship the code as-is in Jaunty, or would it be possible to commit the hotfix in that case?
[15:11] <seb128> allquixotic: we have time to wait for a proper fix, there is over a month before jaunty
[15:13] <allquixotic> seb128: True. I have no reason to believe upstream won't fix it in a month. I'll resurrect this issue if it's *not* fixed in a month, though :)
[15:26] <seb128> slomo: any idea what to ask on bug #330165?
[15:34] <seb128> slomo: and does http://launchpadlibrarian.net/23755516/PattieMaes_2009.mp4 play at normal speed for you?
[15:35] <seb128> slomo: sorry for all the questions today, trying to clean a bit all those gst bugs to see what needs to be done before jaunty ;-)
[15:35] <slomo> plays at normal speed, yes
[15:35]  * kenvandine_wk ->  lunch
[15:36] <seb128> slomo: using debian versions too? this mp4 plays way too slowly there
[15:36] <nick_> can someone point me towards a good reference on how udev-dbus-hald work in Ubuntu?
[15:36] <seb128> same issue using gst-launch playbin uri=
[15:37] <slomo> seb128: the realloc() thing was fixed by his restart, the wmv3_vdpau part is fixed in gst-ffmpeg git
[15:37] <seb128> nick_: as in any other distro?
[15:37] <nick_> distro agnostic i suppose
[15:37] <seb128> slomo: the git change will land to debian in the next month? ;-)
[15:37] <seb128> nick_: www.google.com, type dbus?
[15:38] <slomo> seb128: yes, friday or saturday :)
[15:38] <seb128> slomo: excellent thanks!
[15:38] <slomo> seb128: and that mp4 video plays fine using the debian versions
[15:38] <seb128> slomo: grum, weird, maybe that's the syncs from this morning, I didn't install that yet, thanks anyway
[15:52] <lapo> is there a jaunty lpia iso somewhere?
[15:55] <calc> rickspencer3: my new patch works! :-)
[15:56] <calc> rickspencer3: so i need to beat on it a bit and then upload it after alpha 6 release
[15:56]  * rickspencer3 ^5 calc
[15:57] <nick_> seb128: i thought maybe Ubuntu had something in the dev section on it
[15:57] <nick_> seb128: that doesn't get crawled by google.com
[15:57] <seb128> nick_: no
[16:07] <calc> rickspencer3-mtg: it fails to write to gvfs fuse ftp but that may just be a bug in gvfs fuse, i will track it down after i am done working with pitti on the java MIR bug
[16:07] <calc> actually i'm 99% certain it is a gvfs fuse bug since well i'm using gvfs as a regular fs now
[16:07] <calc> so its either a bug that should be fixed in gvfs or a workaround needed in OOo if it is impossible to fix the bug in gvfs
[16:08] <calc> some gvfs backends can't support certain posix features due to being not real filesystems
[16:08]  * calc just had a huge amount of stress lifted now that saving to network shares works again :)
[16:09] <dobey> calc: it could just be a bug in the ftp server too :)
[16:14] <mvo> why is the second counter thing back when I click on logout in jaunty? I liked the previous solution that said 60sec - 50 sec etc
[16:15] <calc> dobey: possibly, yea
[16:15] <calc> dobey: but there were bugs that i just had fixed in gvfs in the past couple weeks
[16:16]  * calc bets on it being a bug that can be fixed in gvfs fuse layer
[16:18] <calc> ccheney@x200:~/.gvfs/ftp as cheney on cheney.ws$ touch foo
[16:18] <calc> touch: cannot touch `foo': No such file or directory
[16:18] <calc> so it looks like it is below the OOo layer anyway
[16:18] <calc> ccheney@x200:~/.gvfs/ftp as cheney on cheney.ws$ ls -l foo
[16:18] <calc> -rwx------ 1 ccheney ccheney 0 2009-03-11 13:17 foo
[16:18] <calc> so it did create foo but didn't determine that it did
[16:18] <calc> so returned an error instead
[16:19] <calc> it seems it might be timeout related
[16:19] <calc> if you "ls -l foo" right after touch it isn't there but if you wait a second it is
[16:42] <calc> its a bug in the ftp caching in gvfs
[16:48] <seb128> calc: I've been unsetting the milestone for you openoffice shared-mime-info bugs
[16:48] <seb128> calc: openoffice 2007 formats are mostly recognized now
[16:48] <seb128> you have some corner case in the zillion of example in your tars which are still buggy though
[16:48] <seb128> but I think it's low importance
[16:52] <calc> seb128: ok thats fine
[16:56] <kenvandine_wk> mvo: is this update script ready to be tested?
[16:57] <mvo> kenvandine_wk: the one I attached to the bugreport? that can be tested, its just not integrated with the package yet, I was waiting for feedback if it should be folded into the fusa script or not
[16:57] <mvo> that depends on the plans for the next lts of the dx team
[16:57] <kenvandine_wk> mvo: ok, what bug is it again?
[16:57] <mvo> but it should be fine for running it by hand
[16:58] <mvo> give me a sec
[16:58] <kenvandine_wk> ok
[16:58] <mvo> I have it open *somewhere*
[16:58]  * mvo needs more brains
[16:58]  * kenvandine_wk needs a tab limit on firefox :)
[16:59] <mvo> bug #340777
[16:59] <kenvandine_wk> would keep the insanity level down
[16:59] <kenvandine_wk> thx
[16:59]  * kenvandine_wk opens another tab :)
[16:59] <mvo> right now, I just have ~100 open, that used to be ~350 :)
[17:01] <kenvandine_wk> mvo: did the right thing for me... in one test case :)
[17:01]  * kenvandine_wk will do it in a VM
[17:15]  * calc wonders if he can find a way to test the rest of the gvfs backends via fuse so he can beat on them as well
[18:05] <davidbarth> pitti: hi, btw, for the MI testcases, i think we should put that on the testcases wiki made by the QA team, ok?
[18:06] <pitti> davidbarth: sure, please feel free to move the wiki page
[18:06] <davidbarth> pitti: there is already a wiki page for that?
[18:06] <pitti> davidbarth: https://wiki.ubuntu.com/DesktopTeam/Meeting/JauntyIndicatorAppletTestCases
[18:06] <pitti> davidbarth: it didn't address my comments yet, though (reply to rickspencer3-mtg's mail)
[18:32] <asac> hmm. just added the indicator applet to my panel; interestingly enough it now reads "No indicators" ;) ... sounds confusing
[18:33]  * asac starts pidgin
[18:35] <asac> still "No indicators"
[18:45] <kenvandine_wk> asac: hey... i have seen that too, but only on foresight
[18:46] <kenvandine_wk> haven't had time to try to figure out why
[18:46] <kenvandine_wk> but i guess if it is happening on jaunty, it should be filed as a bug
[18:47] <asac> hmm
[18:47] <asac> i thought its because i never used any app that has libindicate support
[18:47] <asac> i will ask ted when he is back
[18:47] <kenvandine_wk> yeah... it happens with both evo and pidgin running
[18:48] <kenvandine_wk> but i have only seen it happen on my wife's foresight laptop :)
[18:48] <kenvandine_wk> asac: if she will let me use her laptop tonight, i will try to debug it there :)
[18:49] <asac> kenvandine_wk: i now installed "indicator-messages"
[18:49] <asac> after adding indicator applet again to panel its just empty ;)
[18:49] <asac> let me start pidgin again ;)
[18:49] <kenvandine_wk> oh
[18:49] <kenvandine_wk> humm
[18:50] <asac> heh
[18:50] <asac> yeah it works
[18:50] <asac> now i have a "letter" displayed there
[18:50] <asac> even even though i dont have any event
[18:51] <asac> cool ... now i have an applet that allows me to pop up pidgin ;)
[18:51] <kenvandine_wk> that is what you should get
[18:52] <asac> so same functions as the tray thing. let me see if i can get an event from somewhere
[18:52] <asac> good
[18:52] <asac> first message popped up the chat window ... which is annoying, but probably a pidgin setting
[18:53] <asac> second message indiciated that there are new messages in panel
[18:53] <asac> kenvandine_wk: can you send a /msg to asac_the_2nd ?
[18:54] <asac> kenvandine_wk: one more please
[18:54] <asac> (first messagte seems not to work)
[18:54] <asac> ok cool
[18:54] <asac> thanks
[18:54] <kenvandine> :)
[18:54] <kenvandine> some messages seem to go to /dev/null
[18:54] <kenvandine> i have a bug open about that
[18:54] <kenvandine> ted is looking at it
[18:54] <asac> i think its the first message that triggers a new chat window/tab
[18:55] <kenvandine> it is
[18:55] <asac> at least that is reproducible
[18:55] <kenvandine> that is a pidgin setting
[18:55] <asac> to not notify about first message?
[18:55] <kenvandine> no
[18:56] <kenvandine> to open that window
[18:56] <kenvandine> you don't get it in the indicator if it opens
[18:56] <asac> kenvandine_wk: yeah. still it should notify i guess because it opens in background
[18:56] <kenvandine> i think that default should be changed
[19:30] <asac> hmm. a python binding for libindicate would be useful now i guess ;)
[19:31] <kenvandine_wk> asac: ted is working on it :)
[19:41] <dobey> someone should update tango-icon-theme in jaunty ;)
[19:41] <dobey> probably in debian too i guess
[20:30] <nrg> how do i disable nautilus from launching on usb mass storage insertion
[21:46] <seb128> bryce: hey
[21:47] <seb128> bryce; about bug #67188, Sergey who wrote comment #62 is upstream for libxklavier libgnomekbd and the gnome keyboard capplets
[21:47] <seb128> bryce: I would advice trying what he asked there
[21:47] <davmor2> ah seb128: you might know.  On freesoftware only should jockey offer to install Nvidia binary driver?
[21:48] <seb128> davmor2: no clue, dunno what "freesoftware only" is and I've no nvidia boxes nor use jockey
[21:48] <davmor2> seb128: thanks :)
[21:48] <seb128> you're welcome ;-)
[21:48] <seb128> ask pitti tomorrow I would say
[21:48] <davmor2> seb128: that was my next resort :)