[01:00] <Hobbsee> bug 300257
[03:13] <dwg> I'm told this is the place I should mention this
[03:14] <dwg> I found and fixed a bug in libopal - packaged fix in my ppa
[03:14] <dwg> but the bug report (https://bugs.launchpad.net/ubuntu/+source/opal/+bug/297123) has had no response at all
[03:18] <RAOF> dwg: Is your debdiff attached to that bug?
[03:20] <dwg> RAOF: uh.. not as such
[03:20] <dwg> RAOF: just a pointer to the PPA, and a link to where the same bug has been fixed upstream
[03:23] <RAOF> https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff?action=show&redirect=MOTU%2FRecipes%2FDebdiff might be useful to you then.
[03:28] <dwg> RAOF: alrighty, I'll make one of those and attach once launchpad is up again
[03:29] <RAOF> dwg: If you've pulled the patch from upstream then it's likely there'll be a fixed package in Jaunty anyway, since we'll likely have a new release in there.  It's probably worth checking that, too.
[03:29] <dwg> RAOF: well, quite possibly
[03:30] <dwg> RAOF: it's a one-liner, though, so just folding in the patch seemed as easy
[03:32] <dwg> RAOF: I came up with the fix independently while debugging; the upstream link came after when I went to check if upstream needed fixing as well
[03:35] <RAOF> I suspect I'd need to actually see the bug to be more help at this point.
[03:36] <greg-g> and getting the fixed package into Debian is also a good way to get it in Ubuntu "automatically"
[03:41] <dwg> greg-g: hrm.. this is a "main" package, not "universe"
[03:43] <greg-g> dwg: generally the same thing applies to main, I think. (I am not a core-dev or motu, so I could be wrong)
[03:43] <dwg> greg-g: well, not doubt it helps, but this is a reasonably serious bug, ubuntu ought to be able to fix it without having to wait for someone else to do it first
[03:44] <dwg> (I don't actually know if the bug is fixed in Debian yet)
[03:45] <greg-g> dwg: well yes, for a serious bug it is good to get the patch in UBuntu quickly, but it is also good to then get it in Debian so we don't have to maintain a diff  (I obviously haven't looked at your bug report, just stating generalized good practices)
[03:46] <greg-g> anyways, it seems you know what you're doing, so, carry on :)
[06:34] <dholbach> good morning
[06:52] <maco> dholbach: morning
[06:52] <dholbach> hi mac
[06:52] <dholbach> maco
[07:28] <maco> dholbach: re bug 278418 icon-naming-utils? so apparently there are *many* ways to go after that one then
[07:34] <dholbach> maco: icon-naming-utils includes a mapping of file names and {gnome,tango,tangerine,human,...}-icon-theme make use of it to generate myriads of symlinks
[07:35] <dholbach> maco: it might make sense to forward the change to upstream and include it in Ubuntu and rebuild the icon themes with it
[07:45] <maco> ah ok
[09:46] <Hew> Hey guys. pidgin-musictracker has been renamed from just musictracker in Debian, which has now been synced to Jaunty. However, it now FTBFS. Two questions: Should I report the FTBFS as a bug against pidgin-musictracker? and what happens with the bugs listed under musictracker, do they need to be moved? Thanks.
[10:18] <Hobbsee> Hew: the source package is the same, isn't it?
[10:19]  * Hobbsee is also somewhat unconvinced that the package has been renamed, so far
[10:19] <Hobbsee> ah.  so it is.
[10:21] <dwg> RAOF_:  I've now attached a debdiff for the bug I mentioned earlier today
[10:21] <Hobbsee> Hew: move bugs:  yes.  report FTBFS: no, we have other ways to track it.  if you were reporting it, it would be against p-m
[10:27] <Hobbsee> oh, and the one i just filed shouldn't be moved ;)
[10:58] <Hew> Hobbsee: Thanks, I'll deal with those other bugs then :-)
[11:01] <Hobbsee> Hew: you're welcome :)
[11:50] <Hobbsee> !ping
[11:50] <BUGabundo_work> can some one give me a pointer on this
[11:50] <BUGabundo_work> https://bugs.edge.launchpad.net/ubuntu/+source/alsa-driver/+bug/296738
[11:50] <maco> Hobbsee: hazzing fun?
[11:50] <Hobbsee> maco: indeed - studying.  Noticed this was very quiet though, and wondered what was happening
[11:51] <BUGabundo_work> is there anything I can do to manually make alsamixer remember its volume?
[11:51] <maco> BUGabundo_work: yeah, it should Affects: linux
[11:51] <BUGabundo_work> really?
[11:51] <maco> alsa-driver is only if you manually compile the alsa-source
[11:51] <BUGabundo_work> kernel? why?
[11:51] <BUGabundo_work> it was triaged
[11:52] <maco> obviously not by crimsun or me
[11:52] <BUGabundo_work> yeah
[11:52] <BUGabundo_work> just saw the activity log
[11:52] <BUGabundo_work> just a plain (forum) user
[11:52] <BUGabundo_work> can you triage it now?
[11:53] <BUGabundo_work> it sucks to have to increase 2 or 3 levers everytime I rebbot
[11:53] <maco> BUGabundo_work: crimsun had me change this page to reflect that most should be linux by default https://wiki.ubuntu.com/DebuggingSoundProblems
[11:54] <maco> i can try
[11:54] <maco> i dont have his expertness though :P
[11:56] <maco> BUGabundo_work: what device options do you have under Default Mixer Tracks?
[11:58] <afflux> I'm having issues understanding bug 301597. python3.0 depends on python3.0-minimal = 3.0~rc3-0ubuntu3. Why is python3.0 processed before python3.0-minimal then?
[11:58] <maco> afflux: the order they are processed is non-deterministic. if one *needs* to be processed first, use pre-depends in the package's dependency list
[11:59] <afflux> alright. Should I add a debdiff for a pre-depends then?
[11:59] <maco> so python3.0 pre-depends on python3.0-minimal
[11:59] <maco> i think so
[11:59] <afflux> will do
[11:59] <afflux> thanks
[12:26] <BUGabundo_work> back maco... sorry
[12:26] <BUGabundo_work> let me check the device
[12:26] <BUGabundo_work> HAD Intel Alsa Mixer is the one selected
[12:28] <BUGabundo_work> maco one thing I noticed is that ever since I upgrade to jaunty
[12:29] <BUGabundo_work> console alsamixer will only show me PA and not alsa controls
[12:29] <BUGabundo_work> is this the expected behaviour?
[12:29] <maco> BUGabundo_work: im not on jaunty, but are you running "alsamixer" or "alsamixer -c0"?
[12:30] <BUGabundo_work> ahhh -c0 show more stuff
[12:30] <BUGabundo_work> why is that?
[12:30] <maco> BUGabundo_work: since the pc speaker is now separated out, you have to specify which card you're talking about
[12:31] <BUGabundo_work> the cat of proc/asound/cards show me just one
[12:31] <BUGabundo_work> the zero one
[12:31] <BUGabundo_work> but why does plain "alsamixer" just show PA?
[12:32] <maco> i dont know the reasoning, but i assume so that it has something to show at all
[12:33] <BUGabundo_work> ok
[12:33] <maco> i just know you have to do -c0
[12:33] <maco> crimsun drilled it in :P
[12:33] <BUGabundo_work> due you know the origin of sound clipping on PA?
[12:34] <BUGabundo_work> vlc, gnome-sound-recorder
[12:34] <maco> you mean where large files don't play all the way?
[12:34] <BUGabundo_work> all leave serious gaps between every 2 secs of playback/recording
[12:34] <BUGabundo_work> no need for large files
[12:34] <BUGabundo_work> I recorded 5 sec of mic audio and it sucks...
[12:34] <maco> no, i don't. id guess something to do with buffering...
[12:35] <maco> but as for that bug you mentioned before
[12:35] <BUGabundo_work> had to use audacity to work
[12:35] <maco> your issue is that your sound all went *poof*, right?
[12:35] <BUGabundo_work> but then audacity doesn't playback
[12:35] <BUGabundo_work> lol
[12:35] <BUGabundo_work> gets muted, yes
[12:35] <BUGabundo_work> on every boot
[12:35] <BUGabundo_work> if I hibernate (most) of the times its okay
[12:36] <maco> oh...are you sure you have the same bug as the reporter?
[12:36] <BUGabundo_work> okay
[12:36] <BUGabundo_work> lets start from the begginnig
[12:36] <BUGabundo_work> is this it https://bugs.edge.launchpad.net/ubuntu/+source/alsa-driver/+bug/296738?
[12:36] <maco> oh, ok read further
[12:36] <maco> the summary at the top isnt descriptive
[12:37] <BUGabundo_work> humm
[12:37] <BUGabundo_work> maybe I should have opened a new bug ....
[12:37] <BUGabundo_work> that bug is getting too confused
[12:37] <BUGabundo_work> mine is very simple
[12:37] <BUGabundo_work> sound muted after reboot!
[12:38] <maco> reading the part where Kevin talks *other* than the top part, you make sense there
[12:38] <BUGabundo_work> yeah
[12:38] <BUGabundo_work> that's why I subsc to that bug
[12:38] <maco> the part that is in desperate need of linebreaks didn't make sense ;)
[12:38] <BUGabundo_work> eheh
[12:38] <BUGabundo_work> edit the desc as you see fit
[12:39] <BUGabundo_work> maco: I'll have to go have lunch or won't be back on time for work
[12:39] <BUGabundo_work> see you in 50 min!
[12:39] <BUGabundo_work> we'll discuss other sound bugs latter, okay?
[12:39] <maco> BUGabundo_work: im going to bed soon. ill talk to you about this in the eastern us afternoon, k?
[12:40] <BUGabundo_work> I'm here until 5pm GMT
[12:42] <maco> ok
[12:45] <maco> BUGabundo_work: i commented on the bug
[13:20] <BUGabundo_work> I'll take a look maco
[13:37] <BUGabundo_work> maco I added the debug info and a comment
[14:40] <afflux> james_w: hi, just read your mail for the python3.0-predepends-issue
[14:43] <afflux> james_w: is this an issue for -devel or for -motu? I'm not quite sure of the difference between these two lists ;)
[14:45] <james_w> I would say -devel for this one
[14:45] <james_w> while the package is in universe it will be in main sometime soon
[14:45] <james_w> and this issue feels more like a -devel one anyway
[14:45] <afflux> okay
[14:47] <james_w> thanks afflux
[14:47] <afflux> thank you
[15:23] <bddebian> Boo
[15:30] <BUGabundo_work> autch
[15:30] <BUGabundo_work> ei bddebian don't give us scares like that!
[15:32] <bddebian> :)
[16:17] <BUGabundo_work> afinal kal era o pro aris?
[16:34] <samuraipenguin> Hi guys.  question on bug 109289, which diff is being asked for?
[20:49] <chrisccoulson> james_w - do you have a few minutes to talk about system-tools-backends?
[20:49] <james_w> chrisccoulson: for you, anything :-)
[20:50] <chrisccoulson> thanks ;) i've tried to catch seb128 on here too but i'm always on here too late i think
[20:50] <chrisccoulson> i tried running it without an init script for a little while to see if it is something that could be considered for jaunty
[20:51] <chrisccoulson> i tried constantly rebooting and then firing up one of the gnome-system-tools apps to see how reliable it was
[20:51] <chrisccoulson> and i did get an error once unfortunately, although i can't repeat it now
[20:52] <chrisccoulson> but the upgrade bug is actually fixed in jaunty by some other means, assuming the theory about it being started by the system bus is correct
[20:52] <chrisccoulson> i thin you know which bug i'm talking about (sorry, i can't remember the bug number now)
[20:53] <james_w> yeah, I remember
[20:53] <chrisccoulson> bug 294389 is the one
[20:53] <james_w> if it's fixed, that's a good start
[20:54] <james_w> and so we might as well keep the init script I guess, especially if you think it may cause a bug
[20:54] <chrisccoulson> yeah, i've proposed a patch for intrepid SRU. i just wanted to make sure you're aware that dropping the init script might not be a good idea straight away
[20:55] <james_w> cool, thanks
[20:55] <james_w> good to know
[20:56] <chrisccoulson> although, i still think that shipping an init script and a DBUS service should be unnecessary. i don't think both are needed, and if gnome-system-tools fails when the backend doesn't exist, even when it gets started by DBUS, then that's probably a bug in g-s-t
[21:07] <chrisccoulson> just looking at bug 301811
[21:07] <chrisccoulson> very odd. i'm failry sure it's not actually a gnome-power-manager bug
[21:07] <chrisccoulson> does anyone have any idea what might cause a locale-specific bug like that?
[21:14] <james_w> chrisccoulson: isn't that from just having mammoth labels for those sliders?
[21:14] <chrisccoulson> i've just tried it on my machine actually. there are 2 issues. issue 1 is the length of the labels. issue 2 is the length of the sliders also doubles with hungarian locale
[21:15] <chrisccoulson> issue 2 might actually be a g-p-m bug, but i'm not sure
[21:19] <james_w> ah, they double? odd
[21:23] <chrisccoulson> it is a little odd. i think someone reported a similar locale specific issue against firefox a little while ago (all the input dialogs were really long with one locale), but i'm sure that bug was triaged against firefox itself
[23:23] <BUGabundo> I'm at #pidgin trying to debug a memory leak
[23:23] <BUGabundo> anybody here using pidgin (preferebly on 64bits) can check its memory usage on ubuntu?
[23:23] <BUGabundo> VM and Resident Memory