[00:00] <hggdh> bdmurray, May 2008 -- bug 225978
[00:00] <Hamra> the reporter sends that an output containing an error with some file, can i do "apt-file search file" to know to which package this culprit belongs to?
[00:00] <crimsun> roughly, anything that is "no sound", "speakers don't mute when I plug in headphones", "too loud", or "too quiet" belongs as affecting linux.
[00:00] <crimsun> Hamra: which file?
[00:01] <crimsun> Hamra: and generally, no, you shouldn't use apt-file to decide which source package to choose as affects
[00:01] <maco> crimsun: sometimes 2 packages provide the same, right?
[00:01] <maco> like if you compile alsa-source or if you get it from the kernel, sometimes they'll be the same name?
[00:01] <crimsun> maco: it's nearly never an issue with what file is mentioned in the message
[00:02] <maco> oh
[00:02] <crimsun> and as we go deeper into the rabbit hole with Phonon and PulseAudio, it will be slightly more confusing initially
[00:03] <Hamra> for example this bug 273578, claims an error with libasound_module_conf_pulse.so, and apt-file search libasound_module_conf_pulse.so , points to libasound2-plugins
[00:10] <crimsun> Hamra: no, that's a prime example of alsa-plugins _not_ being the affected source package.  What should be asked in that case would include pasting the contents of /etc/asound.conf or ~/.asoundrc* (if either/both exist)
[00:11] <crimsun> Hamra: the rationale is that 1) we cannot conclude that there is a user-misconfigured asoundrc, and 2) that the codec is even supported in patch_realtek.c (which is owned by the 'linux' source package)
[00:12] <Hamra> ah ok, thanks for the info
[00:12] <bdmurray> Hamra: Have you seen the debugging procedures pages?
[00:13] <Hamra> yes
[00:14] <maco> crimsun: tonight, can you teach me more about how to read codec output / help me practice reading codec output?
[00:14] <crimsun> Hamra: granted, that particular bug is one of the aforementioned "nuanced" requiring a working familiarity with ALSA
[00:14] <crimsun> maco: sure, and I think we've discussed the essentials
[00:15] <bdmurray> maco: I'd modify the debugging sound page, the note, to have the general case "linux" at the top and the exception below it
[00:15] <maco> bdmurray: ok
[02:59] <RAOF> I'm looking at https://wiki.ubuntu.com/Bugs/Importance, which seems out of date - didn't we agree that bug severities should be per-package, rather than against Ubuntu as a whole?
[03:00] <RAOF> (For example, under those guidelines there doesn't appear to be a way a Universe bug can be higher than 'Medium')
[03:35] <hggdh> RAOF, if it has -- say -- a severe impact on a small portion of users, it would fit in
[03:36] <hggdh> although the medium definition would, ah, state otherwise...
[03:37] <greg-g> hggdh: I do remember the agreement that bug importance should be set as relative to the package, not the distro as a whole.
[03:41] <hggdh> yes, so do I. Perhaps we need to update the wiki, but I would defer to Brian on that (I *do* remember, by I am old, and memory is not what it was...)
[03:44] <hggdh> greg-g, BTW -- bug 251416 -- I think the reporter had an alias to 'rm -f', since there is no response so far. How about to close it?
[03:45] <greg-g> hggdh: :)  I'm relatively young but I like deferring to brian as well.  I should take a look at the wiki before I go to bed to see if I could change it quickly, if I do I'll email brian.
[03:46] <greg-g> hggdh: well since you just asked another question we have to wait another 60 days! ;)
[03:46] <greg-g> but honestly, I'd wait another week and close it, just because you effectively "pinged" the submitter
[03:46] <greg-g> they might return
[03:53] <hggdh> greg-g, roj
[05:46] <dholbach> good morning
[05:47] <lifeless> ah its the daily dholbach spam :P
[05:56] <maco> dholbach: hello
[05:56] <maco> dholbach: i'm listening to the Ubuntu UK Podcast talk about 5-a-day
[05:57] <dholbach> nice
[05:58] <maco> dholbach: your stats page was mentioned.  "so if it's so easy, why have only 35 people done anything in the last 7 days" "where are you getting that information?" "well, from daniel holbach's 5-a-day stats page"
[05:58] <dholbach> yeah, I listened to it yesterday :)
[05:59] <dholbach> we should definitely pimp it some more
[05:59] <dholbach> I'm about to blog about our Bug Jam yesterday as well and mention how everybody started 5-a-day'ing
[05:59] <lifeless> dholbach: btw
[05:59] <dholbach> not a lot of bugs, but still it was great
[05:59] <dholbach> hi lifeless :)
[05:59] <lifeless> dholbach: why don't you infer 5-a-day from launchpad's API's ?
[06:00] <lifeless> dholbach: get the rss feed of ubuntu bugs, and process that
[06:00] <dholbach> lifeless: err?
[06:00] <lifeless> dholbach: isn't the 5-a-day thing where you say what bugs you touched?
[06:00] <dholbach> yeah
[06:00] <lifeless> dholbach: I'm just saying, LP knows that already
[06:01] <dholbach> it should, let me see
[06:01] <lifeless> you could tell if I've done 5-a-day
[06:01] <lifeless> and not need people to do extra-work :)
[06:04] <dholbach> I'll see what needs doing there
[06:09]  * Hobbsee looks for something to kick.
[06:09]  * maco hides
[06:13] <dholbach> hi ara
[06:14] <ara> hello dholbach
[06:14] <ara> dholbach: how are you doing today?
[06:14] <dholbach> good good, still waking up, but good - how 'bout you? :)
[06:15] <dholbach> we had a great Bug Jam in Berlin yesterday - around 15 people showed up - we didn't get much bugs done, but everybody got set up with 5-a-day and stuff and everybody was looking forward to the next Bug Jam
[06:16] <ara> dholbach: that's great!
[06:16] <dholbach> yeah :)
[06:16] <ara> dholbach: mmm, Berlin, I love your city, mate. I was there in 2007 and fell in love with it :-)
[06:17] <dholbach> yeah, it's amazing - especially in summer
[06:17] <dholbach> we should have a few sprints or UDSes there :)))
[06:18] <ara> dholbach: pleeeeaase ;-)
[06:20] <dholbach> ara: the closest I've been to your city was Sevilla - my parents did a trip through lots of South of Spain though - the pictures looked beautiful
[06:20] <ara> dholbach: :-)
[06:22] <dholbach> your city among them :)
[06:25] <lifeless> Hobbsee: slugging?
[06:25] <Hobbsee> lifeless: no, working :(
[06:25] <Hobbsee> lifeless: and prior to that, trying to sort mail out.
[06:55] <maco> dholbach: blogged
[06:59] <dholbach> maco: the "last guy" is Mr Alan "popey" Pope :)
[07:00] <dholbach> maco: good work! great blog post!
[07:02] <maco> dholbach: i cant recognize the voices.  do you know who the other is?
[07:03] <dholbach> popey: was that Tony Whitmore?
[07:05] <maco> dholbach: is it just two of them talkin? I'm not sure
[07:05] <dholbach> no, there are more of them
[07:05] <maco> dholbach: ah, well that's extra confusion, then
[07:05] <dholbach> Dave Walker as well
[07:06] <maco> dholbach: was popey the one that mentioned your stats page?
[07:07] <dholbach> for that I'd need to download the podcast again - best to wait for popey to say who's who
[07:07] <dholbach> he'll know best
[07:07] <maco> kk
[07:09] <maco> thinking about it, it's 7AM there, so he's probably asleep
[07:29] <popey> i am
[07:29] <popey> :)
[07:30] <popey> maco / dholbach, I am the one saying 5-a-day is easy, dave pointed out the stats page, ciemon says its too hard, and tony said he doesn't have time when he gets home.
[07:31] <maco> popey: thanks
[07:31] <dholbach> thanks popey
[07:31]  * dholbach hugs popey
[07:32] <maco> popey: who asked dave where he found the stats?
[07:32] <popey> me
[07:32] <popey> i knew where the stats page was really :)
[07:32] <popey> but didn't interpret them the same way he did
[07:33] <maco> popey: ah ok
[07:33] <maco> popey: well, blogged about the podcast...as funny as that sounds
[07:33] <popey> so i see :)
[07:33] <popey> thank you!
[07:33] <maco> popey: good lead-in to another "hey go do 5-a-day!" post ;)
[07:35] <popey> i didnt necessarily argue the point well having been in the pub for about 5 hours before we recorded
[07:37] <maco> popey: wait so were you the one saying they didnt do 5-a-day that day because they were in the pub?
[07:38] <dholbach> hey Daviey
[07:38] <dholbach> we're just talking about the 5-a-day portion of the last UK podcast :-)
[07:39] <dholbach> popey: for 5h in the pub, the podcast is great - really :)
[07:39] <popey> :)
[07:39] <Daviey> dholbach: Hey!!
[07:40] <maco> popey: take a look and let me know if i got the names right now
[07:40] <popey> Tony: "Well, I haven't done any today because I spent most of the day in the pub."
[07:41] <popey> that should be Alan:
[07:41] <popey> other than that it's correct
[07:42] <maco> popey: ok
[07:42] <maco> thank you
[08:23] <maco> bdmurray: how are the package status images generated?
[09:01] <XiXaQ> could someone have a look at this one? https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/261789
[09:01] <XiXaQ> I'd really love it if that fix could be made available in Hardy too.
[09:04] <maco> can someone please mark bug 164192 wishlist?
[09:05] <mvo> thanks maco, done
[09:06] <maco> mvo: thanks
[09:07] <maco> mvo: do you remember the joining-bugsquad process?
[09:08] <thekorn> ups, I think I clicked the change button at the same time as mvo, this reverted the changes
[09:08] <maco> bug 177487 should be low as well
[09:09] <maco> and i just got a wonderful evolution bug O_o ...though this could be caused by third party PPAs....hrm
[09:09] <thekorn> mvo: sorry, can you please do your changes on this bug again,
[09:09] <mvo> thekorn: heh :) sure
[09:10] <thekorn> gracias
[09:11] <maco> ok no, the package it's reporting on is in hardy-updates well isn't that a lovely bug -_-
[09:13] <maco> hey, can someone using evolution reproduce the bug where attempting to compose a message throws an error about libgtkhtml and gtkhtml?
[09:13] <maco> and then clicking the error away crashes evolution
[09:20] <maco> dholbach: what does "bugs have been added but not committed. already committed 55 minutes ago" mean?
[09:21] <dholbach> maco: it commits them locally and pushes them every hour
[09:21] <dholbach> you can force it by using -f
[09:21] <maco> ah ok. that's new then
[09:21] <maco> ?
[09:21] <dholbach> no
[09:21] <dholbach> it was just disabled by a bug in the code
[09:21] <dholbach> I cleaned up a few things yesterday
[09:22] <maco> ah ok. i saw the bugmail about the --add-team and crimsun's --local request
[09:22] <dholbach> yeah
[09:31] <maco> what do you do when there's no backtrace?
[09:32] <dholbach> hm?
[09:32] <maco> https://wiki.ubuntu.com/Backtrace
[09:32] <maco> already running program section
[09:32] <maco> got to the part where i reproduce the crash
[09:32] <maco> then gdb says the program no longer exists, segfault
[09:33] <dholbach> so the crash does not occurs?
[09:33] <dholbach> occur?
[09:33] <maco> and at that point, getting the backtrace, stack, registers...gdb says there's no data
[09:33] <dholbach> does the program crash without gdb?
[09:33] <maco> oh the crash happened, gdb just doesn't have any information
[09:33] <maco> yes
[09:33] <dholbach> weird
[09:34] <dholbach> pitti and seb128 are some of our crash experts maybe they have an idea
[09:34] <maco> after it finishes loading the debugging symbols, it goes thusly: http://pastebin.ca/1211313
[09:35] <dholbach> mh
[09:36] <maco> trying the valgrind thing now
[09:37] <maco> wow valgrind makes the cpu go nuts
[12:35] <murdok> What should I do with this bug? https://bugs.launchpad.net/ubuntu/+bug/239733
[12:35] <murdok> It has patch attached for the kernel
[12:35] <murdok> Shall I report it to bugzilla.kernel.org?
[12:36] <persia> murdok: The kernel is kinda special: upstream likes people to check against current upstream when reporting a bug.  If you're up for that, it would be great.
[12:50] <murdok> Okay, but in my opinion in bugzilla.kernel.org it would be confirmed before and applied before
[12:54] <murdok> Because the casuality of "someone _using ubuntu_, that has the _same card_, that _tries the remote_ and that understands a bit about reporting bugs" is not very probable:P.
[12:54] <murdok> Then he should want spend 5 minutes reporting the bug and finally confirming the old one
[12:54] <murdok> persia:
[12:54] <murdok> i leave it as is
[12:55] <persia> murdok: Good point.  I don't know what to do with those.
[13:43] <Hamra> are these 2 bugs dups? 274766 and 269652
[14:19] <chrisccoulson> ping seb128 - would you object to me closing bug 193897, in light of the upstream response (they're not going to fix it)
[14:19] <seb128> chrisccoulson: right, it should be closed since there is no such locations since gvfs
[14:20] <chrisccoulson> thanks, i'll do that
[14:46] <bddebian> Boo
[14:46] <jjesse> don't cry i didn't mean to scare you :)
[14:47] <jjesse> good morning bddebian
[14:47] <bddebian> Hi jjesse :)
[15:10] <chrisccoulson> ping mvo - just looking at bug 105644 from the hug day list yesterday
[15:10] <chrisccoulson> that's not an update-manager bug is it? i think it is update-notifier
[15:18] <Hamra> chrisccoulson:but the reporter also claims that update manager is showing one package in the list of updates
[15:19] <Hamra> it should have showed 2 packages, just like apt-get shows
[15:22] <chrisccoulson> i suppose you're right actually if you look at it that way. update-manager should probably list new packages that are going to be pulled in as well as upgraded packages, otherwise the user never knows of them
[15:22] <chrisccoulson> i was looking at it from the basis that update-manager was behaving correctly by only listing one package, which would make update-notifier wrong for saying there are 2 packages
[15:25] <Hamra> you have a point. but does update notifier rely on update manager to get the number? in which case, you're right to say that update notifier is misbehaving, but if update-notifier gets the number somewhere else... :S
[15:26] <chrisccoulson> update-notifer uses it's own scripts for getting the number of updates AFAICT
[15:27] <Hamra> in which case, it's doing it's job well. it's update manager's fault that it's not showing dependencies properly
[15:30] <chrisccoulson> yeah, i think i agree. it's quite an old bug now, so I don't know whether update-manager still behaves like this
[15:30] <chrisccoulson> i need to think of a way to test it really
[15:49] <bdmurray> maco: with gnuplot
[15:55] <bdmurray> mvo: just to confirm 'short read in buffer_copy' and 'error in buffer_read' are likely hardware issues if someone is using a cd-rom upgrade?
[16:05] <mvo> bdmurray: yes, that is the most likely explaination - I haven't seen that many of them though
[16:06] <bdmurray> mvo: okay, I saw one in a log yesterday and was just testing a clue file
[16:06] <mvo> thanks
[16:11] <Hamra> hi, are the errors in the end of this file enough to set  this bug as confirmed? http://launchpadlibrarian.net/17981386/Xorg.0.log
[16:12] <Hamra> bug 274102 btw
[16:13] <chrisccoulson> yeah, i think so. especially seeing as it is reproducible from the live CD
[16:15] <chrisccoulson> Hamra - You might also want to take a look at bug 259808. they look similar
[16:19] <Hamra> they both have the same error msgs, but in different times.
[16:20] <Hamra> in 274102, the reporter can't even start X
[16:20] <Hamra> weirdly though, by choosing from the LiveCD to go directly to installer, everything worked fine
[16:22] <chrisccoulson> i'm not familiar with that option on the liveCD? I assume that it opens up a X server?
[16:25] <Hamra> yes, it does open an X server, but without any bars on top and bottom, or icons or anything, just ubiquity in the middle of the screen
[16:27] <Hamra> anyways, i noticed he haven't even configured his X server, so asked him/her to do so in recovery mode, we'll see after that
[16:27] <chrisccoulson> it shouldn't need any configuring though
[16:27] <Hamra> what do you mean?
[16:29] <chrisccoulson> there should be no need to configure the X server in Intrepid
[16:30] <Hamra> i use intrepid with nvidia, X did work before configuring, but in a 640x480 resolution!
[16:31] <Hamra> actually, the lack of kcontrol (i use KDE) forced me to manually edit most of my xorg.conf
[16:31] <chrisccoulson> i don't know whether you still need to specify the NVIDIA driver in your xorg.conf in order to get the X server to load the proprietary driver, but you shouldn't need to specify any more than that in there
[16:32] <chrisccoulson> even on my hardy machine, i can run the NVIDIA drivers at full resolution with virtually nothing specified in my xorg.conf
[16:32] <chrisccoulson> if you can't, then that is a bug
[16:40] <thekorn_> hi!
[17:12] <bdmurray> thekorn_: hello!
[17:12] <bdmurray> james_w: what model of dell do you have in bug 251482?
[17:13] <james_w> bdmurray: 6400n
[17:13] <james_w> bdmurray: 1505n in the US I believe
[17:13] <bdmurray> hmm, I've a 530 (desktop) that doesn't have that bug
[17:15] <james_w> yeah, it's an odd one, I've no idea where it came from
[17:16] <bdmurray> you must just be special ;)
[17:16] <thekorn_> bdmurray, good news - I'm able to run bugnumbers and bughelper with a wrapped launchpadlib as backend,
[17:16] <thekorn_> hi james_w
[17:17] <bdmurray> thekorn_: wow, that's fantastic!
[17:17] <thekorn_> bdmurray, this is the py-lp-bugs branch: lp:~thekorn/python-launchpad-bugs/launchpadlib.connector
[17:17] <james_w> hey thekorn_
[17:17] <james_w> thekorn_: python-httplib2 was updated today, so we can seek pushing an updated launchpadlib snapshot in, with support for things like attachments I believe
[17:18] <thekorn_> great
[17:19] <thekorn_> bdmurray, bughelper and bugnumbers both only need a one-line change to be ready for the api
[17:20] <bdmurray> thekorn_: and everything works?
[17:21] <thekorn_> bdmurray, yes, I tested a lot of bugnumbers options, and it is looking good,
[17:21] <thekorn_> the only problem is that searching for bugs is slower in the api mode than in text mode,
[17:22] <bdmurray> bug lists or individual bugs?
[17:22] <thekorn_> bug lists
[17:23] <thekorn_> I will try to debug this over the weekend, and file some bugs against malone/launchpadlib
[17:29] <bdmurray> thekorn_: what is the one line change for testing?
[17:29] <thekorn_> in bugnumbers/bughelper:
[17:30] <thekorn_> -    if cl.options.parsemode not in ("text","html"):
[17:30] <thekorn_> +    if cl.options.parsemode not in ("text","html", "api"):
[17:30] <thekorn_> and then run:    ./bugnumbers -p bughelper --parsemode api --cookie <path-to-credentials-file>
[17:30] <thekorn_> as an example
[17:31] <bdmurray> and for testing py-lp-b ConnectBug("api") should work?
[17:31] <thekorn_> yes
[17:32] <thekorn_> and you always need Bug.authentication = <cred.txt>
[17:32] <thekorn_> as the api always needs an authentication token
[17:33] <bdmurray> right, and it is using edge because it has the most features correct?
[17:34] <thekorn_> this branch is using staging per default
[17:34] <bdmurray> so its read only then?
[17:34] <thekorn_> no, staging is writable, it depends on your configuration
[17:35] <thekorn_> but you can change the server with:
[17:35] <bdmurray> Doesn't staging use a separate database?
[17:35] <thekorn_> Bug.connection.set_mode(EDGE_SERVICE_ROOT)
[17:36] <thekorn_> ah ok, yes, but you can change things on staging temporary
[17:36] <bdmurray> okay, that might have been confusing ;)
[17:56] <dfuentesh> hi there
[17:57] <dfuentesh> who knows if there's a bug in the 2.6.24-19-generic kernel with the intel 3945   wireless adapter?
[17:58] <dfuentesh> i can't connecto
[17:58] <dfuentesh> connect*
[18:06] <chrisccoulson> dfuentesh - you might need to be a little less vague :)
[18:07] <chrisccoulson> do you know if your card is detected? How are you trying to connect? Encryption? (WEP/WPA) Do you have any errors in your log files etc
[18:24] <chrisccoulson> james_w - i'm just looking at bug 274080 (misleading title - the reporter can hibernate, but suspend is not available). i'm not sure if it is caused by the uswsusp problem you brought up on the mailing list, because HAL says that suspend is still available
[18:25] <chrisccoulson> what do you think?
[18:26] <james_w> chrisccoulson: yeah, that's a confused report
[18:27] <chrisccoulson> just a bit;)
[18:27] <james_w> chrisccoulson: I think you are right though, I think it's a different issue
[18:27] <chrisccoulson> thanks. i'll look in to it further
[18:27] <james_w> chrisccoulson: if suspend isn't offered in the menu then these three commands will probably narrow down why
[18:28] <james_w> chrisccoulson: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/267331/comments/6
[18:28] <bdmurray> pedro_: I uploaded a video to bug 257349
[18:29] <pedro_> bdmurray: ok will have a look
[18:29] <chrisccoulson> james_w - thanks for those. i hadn't thought of looking at gconf or policykit actually
[18:29] <bdmurray> pedro_: it might just be me or istanbul recorded videos
[18:29] <james_w> chrisccoulson: I'll put them on the wiki page
[18:30] <pedro_> bdmurray: ok i'll try it and comment there
[18:30] <chrisccoulson> that's probably a good idea
[18:31] <bdmurray> pedro_: thanks
[18:38] <james_w> chrisccoulson: https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#Finding out why suspend isn't offered
[18:39] <chrisccoulson> that looks good. it might be good to point out that you can follow a similar procedure for hibernate too.
[18:39] <james_w> yeah, I hadn't checked the code, but I imagine it is parallel
[18:44] <james_w> done
[18:47] <bdmurray> pedro_: by the way yesterday we were talking about the system beep changing in Preferences -> Sound in Intrepid yesterday
[19:13] <TonyP> Hi all.  I answer questions on launchpad - mainly for OpenOffice.org.  I answered question #44845 about corruption of documents saved on Samba shares and found that bug #267371 had already been posted for this problem.  That was on 7 Sept 2008.  It is still shown a New with no importance assigned yet.  Is there anyway of getting it looked at?  I have verified the bug with my own testing.
[19:20] <bdmurray> TonyP: looking / reading
[19:22] <bdmurray> TonyP: you've recreated the issue is that correct?
[19:30] <TonyP> bdmurray: I haven't created a new issue, if that's what you mean
[19:30] <bdmurray> TonyP: I meant you've experienced / recreated the bug
[19:31] <TonyP> bdmurray: yes, I have recreated the bug
[19:31] <bdmurray> TonyP: using OpenOffice from which release?
[19:33] <TonyP> bdmurray. OOo 2.4.1 with Ubuntu 8.04.1.  BTW one of the people reporting the problem says it didn't happen in 7.10.
[19:34] <bdmurray> TonyP: Can you update the bug then and include the specific information I asked for?
[19:36] <pedro_> bdmurray: may you attach your ~/-xsession-errors to the totem bug?
[19:37] <bdmurray> pedro_: the whole thing?
[19:38] <pedro_> well just the relevant part, i'd like to see if there's anything related to the crash
[19:41] <TonyP> bdmurray: I have updated the bug. I see it now has High importance - thanks!
[19:42] <bdmurray> TonyP: the specific package version you've been able to recreate this with would really help
[19:47] <bdmurray> pedro_: I inserted a string in my .xsession-errors file then recreated the crash and nothing showed up after the crash
[19:48] <pedro_> bdmurray: ok, thanks
[19:48] <bdmurray> other videos play fine too fwiw
[19:50] <TonyP> bdmurray: In the OOo About box it says openoffice.org-core 1:2.4.1-1ubuntu2
[19:50] <pedro_> bdmurray: ok, it works fine the video here i'll ask you if upstream needs more info :-)
[19:50] <bdmurray> yeah, it works fine on my laptop too
[19:51] <bdmurray> TonyP: great, can you put that in the bug too?
[19:58] <bdmurray> TonyP: also how are the shares mounted / used?
[20:06] <hggdh> where do I find what Ubuntu versions are still supported?
[20:06] <bdmurray> hggdh: releases?
[20:07] <hggdh> yes
[20:07] <hggdh> sorry
[20:07] <bdmurray> more than 1 time?
[20:07] <bdmurray> or do you just want to know right now?
[20:07] <hggdh> more than one time would be good
[20:07] <bdmurray> rmadison is one way
[20:08] <hggdh> I thought it would be under the support page on ubuntu.com
[20:08] <hggdh> ah, cool
[20:08] <hggdh> bdmurray, is dapper LTS?
[20:08] <bdmurray> yes
[20:09] <hggdh> kees, thanks... one more debdiff for dapper ;-)
[20:09] <hggdh> dammit
[20:09] <hggdh> OK
[20:10] <TonyP> bdmurray: I have put some more info on the bug.  Is it OK?
[20:11] <bdmurray> TonyP: it helps.  A sample document would be neat, but or I can try and find one.  Also how are the shares mounted?
[20:22] <josh_what> Anyone familiar with this bug?  Some newly opened applications come to the foreground and take focus when others go to the background and not take focus.  I'm not using Compiz Fuzion.  I am using Hardy.
[20:24] <chrisccoulson> TonyP - re bug 267371
[20:24] <chrisccoulson> it might be good for you to include the server-side samba logs and server side dmesg
[20:25] <chrisccoulson> and perhaps a description of your network configuration, including samba server settings
[20:25] <josh_what> Is this channel mostly for the discussing of bugs or the troubleshooting of bugs?
[20:26] <chrisccoulson> josh_what - this channel is mainly for discussing the triaging of bugs. if you want help with a particular problem, then you could try #ubuntu
[20:26] <chrisccoulson> which apps are you having focus problems with btw?
[20:26] <chrisccoulson> not firefox is it?
[20:29] <hggdh> bug 141168
[20:29] <josh_what> Well it doesn't work in Firefox, but it is not specific to Firefox.  When I click on the Keyboard Indicator I added to the panel, it doesn't change for gedit or terminal either.
[20:29] <hggdh> how should we act on this bug?
[20:31] <chrisccoulson> hggdh - what are the behavioural differences?
[20:31] <josh_what> Thanks for your help, chrisccoulson.
[20:31] <hggdh> different set of options; on one hand we get to be compatible with SUSE and RH; on the other hand we break back compatibility with Ubuntu
[20:32] <hggdh> I tend to set it triaged for the package maintainers to explain
[20:33] <hggdh> (and... bash has its own embedded kill also...)
[20:33] <chrisccoulson> thats a tough one
[20:34] <chrisccoulson> i'm not sure what else to suggest;)
[20:34] <hggdh> :-)
[20:35] <hggdh> I will setit as triaged for the maintainer. Personally, I would not do it -- more important than being compatible with other distributions is being compatible with ourselves
[20:37] <chrisccoulson> yeah, i agree. i don't think it is a big issue really (I didn't even know there were so many variants of kill until just now) ;)
[20:37] <hggdh> add in KDE's own ;-)
[20:41] <chrisccoulson> lol
[20:41] <chrisccoulson> the phrase 're-inventing the wheel' springs to mind;)
[20:41] <chrisccoulson> it seems bizarre to have so many variations of such a basic utility!
[20:42] <hggdh> agree... one of the side benefits of FLOSS, I guess
[21:25] <TonyP> bdmurray: The share I was using on the Ubuntu 8.04.1 server was a directory I created (/home/shared) and shared using the Properties > Sharing Options. /home is an ext3 filesystem.  The documents I was given by Mark O'Brien are only semi-anonymised so I was asked not to make them public (i.e. I cannot attach them to the bug report).  I am doing some more testing now with somewhat mixed results.  I will put my results on launchpad, but i
[21:26] <bdmurray> TonyP: you got cut off there
[21:29] <TonyP> ﻿bdmurray: (Repeated) The share I was using on the Ubuntu 8.04.1 server was a directory I created (/home/shared) and shared using the Properties > Sharing Options. /home is an ext3 filesystem.  The documents I was given by Mark O'Brien are only semi-anonymised so I was asked not to make them public (i.e. I cannot attach them to the bug report).  I am doing some more testing now with somewhat mixed results.  I will put my results on la
[21:30] <bdmurray> TonyP: How is the share mounted on the client system?
[21:33] <maco> TonyP: you get cut off after ", but i"
[21:33] <maco> TonyP: the message is too long
[21:34] <TonyP> bdmurray: Just accessed through Places > Network > POLLY > shared (polly is the server, of course)
[21:34] <Nafallo> polly polly polly!
[21:34] <james_w> chrisccoulson: good catch on that gnome-screensaver/consolekit bug
[21:35] <chrisccoulson> thanks. i've just had a look at his Consolekit.conf
[21:35] <chrisccoulson> there's no permission for SetIdleHint
[21:35] <chrisccoulson> i thought there was another bug report for this issue, but I can't find it
[21:35] <james_w> http://cgit.freedesktop.org/ConsoleKit/commit/?id=f0fb2d1cfd0f0ea3ad922175e895a9e751498a03
[21:35] <james_w> that's only in git so far
[21:35] <TonyP> maco: Sorry, I'm a IRC newbie!  the last bit is "﻿but it may not be until tomorrow now."
[21:35] <james_w> I'm just going to dig a little and then propose a patch
[21:36] <chrisccoulson> thanks for spotting that
[21:36] <maco> TonyP: i'm talkative, so i do it too ;)
[21:36] <chrisccoulson> i take it that gnome-screensaver must be broken for everyone then?
[21:37] <james_w> yeah, I guess so, I'm going to grab the package now, I wonder if it's just been updated
[21:39] <bdmurray> calc: have you heard anything about openoffice, samba and file corruption?
[21:40] <chrisccoulson> james_w - this problem has been around a little while by the sounds of it. it's also mentioned in bug 256586, which described two problems, but no-one opened a consolekit task
[21:42] <james_w> chrisccoulson: good spot
[21:42] <james_w> there appear to be two bugs there
[21:43] <james_w> 159263 doesn't mention the problem in the log files
[21:43] <chrisccoulson> it's a good job the reporter ran gnome-screensaver in debug mode, otherwise I might not have spotted it straight away!
[21:45] <calc> bdmurray: i've heard a user report it, but i couldn't reproduce it locally
[21:45] <bdmurray> calc: yeah, I think I saw that bug.  They are saying it takes a "large" file.
[21:46] <bdmurray> I haven't been able to recreate it with Hardy or Intrepid
[21:46] <calc> bdmurray: hmm
[21:47] <calc> i'm pretty sure OOo doesn't do anything wrt samba itself so if it is really a software issue (instead of a network hardware issue) then it probably is somewhere in the stack under OOo
[21:51] <bdmurray> I looked around for an upstream bug report and couldn't find anything
[21:52] <james_w> chrisccoulson: oh wow, SetIdleHint has been called since 2007-02 according to gnome-screensaver's changelog
[21:52] <chrisccoulson> hmmmm, thats strange
[21:53] <chrisccoulson> maybe that isn't the reporters issue?
[21:54] <james_w> well, it would seem to be a problem to me, but it may not be the main problem
[21:54] <james_w> and I wonder why it's a problem for some and not others
[21:57] <chrisccoulson> i'm not sure why thats the case
[21:57] <chrisccoulson> i havent noticed whether it's been working or not, as i'm only using intrepid in a virtual machine at the moment
[22:03] <chrisccoulson> james_w - i can't explain why its an issue for some and not for others in intrepid, but i can see why it's not an issue pre-intrepid
[22:03] <chrisccoulson> the dbus policy in hardy opens up all consolekit interfaces and then explicitly denies a handful of methods
[22:03] <chrisccoulson> which is the opposite to how it is defined in intrepid
[22:04] <james_w> chrisccoulson: nice spot
[22:04] <james_w> I would say that patching consolekit to allow the method as in the upstream patch is something we should do regardless of what is going on here, do you agree?
[22:04] <chrisccoulson> yeah, i definately agree with that
[22:07] <chrisccoulson> right, i've got to go and eat!
[23:05] <Hamra> some ppl use the crash reports by apport to report some other bugs happening with them, other than the package apport is reporting about, how do we handle these?
[23:06] <hggdh> Hamra, what bug is this?
[23:06] <maco> Hamra: ask them to file separate bugs for separate issues
[23:07] <Hamra> 274848 for example. apport is reporting a firefox crash, but they used it to report something else
[23:07] <hggdh> bug 274848
[23:08] <hggdh> Hamra, in this case the reporter used the Firefox option to report a bug
[23:08] <hggdh> Help/Report a Problem
[23:09] <hggdh> so the bug got primed by firefox, but this is not really a firefox bug
[23:09] <Hamra> ah i see, i never noticed this button, i thought he had a firefox crash or something. thanks for the info
[23:10] <hggdh> so no problem here (apart from potentially confused triagers -- i.e. us ;-)
[23:10] <hggdh> it was actually good, because the reporter stated Ubuntu 8.08 (non-existent), and firefox nicely told us it is 8.04
[23:12] <hggdh> anyways, the package is wrong, and I have no idea what is nvidia-glx-config
[23:12] <Hamra> i'm not using ubuntu 8.08 now? but i downed it in august? lmao
[23:12] <hggdh> :-)
[23:12] <Hamra> he's probably confused with the way terminals handle passwords
[23:13] <hggdh> perhaps. We still need to find out what exactly he was trying to install. Perhaps one of us with nvidia can state that
[23:15] <Hamra> no nvidia-glx-config here, i have nvidia
[23:15] <Hamra> there is a nvidia-xconfig program which is the closest i can find
[23:17] <Hamra> looks at this bug 274920, i can confirm it straight away here, but seriously, for a dot?
[23:17] <Nafallo> Hamra: unknown distro. should be invalid. (and no, I'm not serious)
[23:17] <Nafallo> :-P
[23:18] <Hamra> i mean really! was he just bored or have nothing to do in his life other than to file a bug report about a single pixel!
[23:19] <hggdh> well, it seems to be a rendering issue. One pixel here, one pixel there, etc, etc
[23:19] <Hamra> it's only 1 pixel, clicking another file, removes the pixel from the 1st one
[23:20] <hggdh> but it is still wrong, methinks
[23:20] <hggdh> it is certainly not a critical issue -- but it is, nevertheless, an issue...
[23:22] <Hamra> is my evidence enough to confirm it?
[23:22] <hggdh> if you can repeat it, yes
[23:23] <hggdh> the remaining question is which package is responsible for that. Since I do not use KDE anymore, I do not know, mostly on KDE4
[23:25] <Hamra> that's what i'm looking for. i know that the whole desktop, taskbar, menus, widgets, all belong to the plasma workspace
[23:25] <hggdh> finally -- correcting the bug title (Intrepid spelling) is also a good idea
[23:25] <Hamra> and killing the process plasma, removes them all
[23:25] <Hamra> now, where does plasma comefrom?
[23:26] <Hamra> and yes, the spelling needs correcting
[23:26] <hggdh> if you have the program name, you can 'dpkg -S' on it, or apt-file search on it
[23:29] <hggdh> for /usr/bin/plasma, the package is kdebase-workspace-bin
[23:30] <Hamra> kdebase-workspace-bin
[23:30] <Hamra> damn, you beat me at it :P
[23:34] <hggdh> Hamra, I marked it triaged. Thank you for your work there
[23:36] <Hamra> you're welcome