[00:15] <charlie-tca> USA - ?
[00:50] <Awsoonn> 10 minutes until it's bugday somewhere ^_^
[00:52] <james_w> mrooney: hi, is the bot reporting modified bugs instead of new bugs?
[00:59] <mrooney> james_w: it is a known issue, it is reporting bugs from launchpad.net/ubuntu, which now has both new and newly touched
[00:59] <mrooney> so it is combining the two
[00:59] <mrooney> I am working on a fix!
[01:00] <james_w> mrooney: great, thanks.
[01:15] <mrooney> james_w: is there any way for me to be able to edit the topic in #ubuntu-bugs-announce?
[01:16] <bdmurray> mrooney: I can do that for you
[01:16] <mrooney> bdmurray: okay, that could be useful! will it work between parts and joins if I am identified?
[01:18] <mrooney> james_w: alright, the fix appears to work nicely on this machine, let me pop it over
[01:19] <bdmurray> bdmurray: I meant I could set the topic. ;)
[01:24] <mrooney> bdmurray: oh, I see, fair enough :)
[01:24] <mrooney> bdmurray: would you mind just changing ubotu to EeeBotu for accuracy?
[01:26] <mrooney> bdmurray: thanks, what about the capital B? ;)
[01:26] <mrooney> bdmurray: thanks!!
[01:26] <bdmurray> mrooney: happy now?
[01:27] <mrooney> yes, quite
[01:27] <bdmurray> cool
[01:36] <ApOgEE-> hi all
[01:37] <mrooney> hi hi
[01:38] <ApOgEE-> i'm checking my xchat bug
[01:39] <ApOgEE-> i want to confirm something, could anybody please go to #ubuntu-my and type something from there? i can't see outgoing and incoming text. just to verify
[01:44] <hggdh> ApOgEE-, I can see your text there, and others
[01:44] <mrooney> yes me too, how interesting
[01:44] <ApOgEE-> hggdh, oko thanks
[01:45] <ApOgEE-> i can't see my text or other text
[01:45] <ApOgEE-> unless i click on other channel and get back to it
[01:45] <hggdh> its not a channel issue, may be your client issue
[01:45] <ApOgEE-> yes, it's xchat
[01:45] <hggdh> so am I...
[01:45] <ApOgEE-> i'm filing a bug report then
[01:46] <ApOgEE-> it happens quite regular on the last channel on my joined channel list
[01:46] <ApOgEE-> thanks all for your time
[01:46] <hggdh> welcome
[05:32] <Awsoonn> 243952 243965 seem to have the 'right' info attached, should they be set to triaged?
[06:19] <bliZZardz> does assignment of a bug to an appropriate package(in case if it was selected wrongly while creating the bug) require some privileges?
[06:19] <techno_freak> no
[06:21] <bliZZardz> ahh..got it. I need to invalidate the previous 'affected pkg' and add the new appropriate one.
[06:22] <Hobbsee> you can change the affected package
[06:22] <Hobbsee> as in, without invalidating
[06:22] <Hobbsee> (which works better)
[06:22] <Hobbsee> hit the status of the bug, and type in the new name in the dropdown
[06:23] <bliZZardz> Hobbsee : how ? It is a read only field for me
[06:23] <Hobbsee> which bug?
[06:23] <bliZZardz> bug #230853  is for python-subversion-dbg
[06:24] <persia> bliZZardz: That's filed against the "subversion" project, not the "subversion" package in the "ubuntu" project.
[06:24] <persia> You can't change it now, although you may be able to create an Ubuntu task.
[06:24] <bliZZardz> persia : pertinent observation.
[06:24] <Hobbsee> ah, yes
[09:25] <savvas> "X-Original-Maintainer:" is a valid debian package info line?
[09:27] <bliZZardz> svvas : was it already present there as 'X'?
[09:27] <bliZZardz> **savvas
[09:27] <savvas> err what do you mean?
[09:28] <savvas> there is Original-Maintainer and XSBC-Original-Maintainer, but I was wondering about X-Original-Maintainer
[09:28] <savvas> about 400 packages use it across the ubuntu archive
[09:28] <savvas> I wanted to know the difference of these three
[09:32] <persia> savvas: X-$(whatever) is a value entry in control files, indicating that the entry is experimental, and not yet approved for general use.
[09:33] <persia> XSBC-$(foo) indicates that $(foo) should additionally be copied to each of the produced Source package, Binary package, and Changes file.
[09:34] <savvas> persia: thanks! so X-Original-Maintainer should actually be Original-Maintainer? Is it approved? I'm asking to know whether I should file a bug to request the change from x-(blah) to blah
[09:37] <bliZZardz> directhex : you scare me .. this is my first attempt :P
[09:37] <savvas> e.g. in hardy apt-cache show python-pyme - X-Original-Maintainer: Arnaud Fontaine
[09:40] <persia> savvas: I'm not sure it's worth a bug against python-pyme.  You might look at the pkgbinarymangler code to see what it is doing.  I generally see "Original-Maintainer" for things that have the field from source modifications, but I don't know if the issue is with pkgbinarymangler or with the common procedure used by developers.
[09:42] <savvas> ok thanks persia :)
[12:56] <afflux> morning
[13:05] <thekorn> hoi afflux
[13:06] <afflux> heya thekorn
[13:06] <Iulian> Hello afflux, thekorn, pedro_!
[13:06] <afflux> ...et al ;)
[13:06] <pedro_> hey hey ;-)
[13:28] <mrooney> pedro_: hello!
[13:29] <pedro_> mrooney: hello :-)
[13:29] <mrooney> pedro_: any chance you would be able to renew my bugcontrol membership? I just got the 7 day email notice
[13:30] <pedro_> mrooney: sure, let me have a look
[13:30] <mrooney> great, thanks!
[13:30] <mrooney> pedro_: oh sorry I should have told you I am launchpad.net/~michael
[13:31] <Iulian> Don't forget about the hug day guys!
[13:32] <mrooney> Iulian: are there ever events like this later in the EST day? or is it still active later?
[13:32] <mrooney> I feel like I miss out on so many meetings and events by working full time :)
[13:38] <Iulian> mrooney: This hug day will be until tomorrow. But you can still have a look at the list even if it's not anymore.
[13:38] <pedro_> mrooney: membership renewed, thanks you
[13:38] <pedro_> bonjour seb128
[13:38] <mrooney> pedro_: thanks pedro! so that is good for a year, or is it 6 months?
[13:39] <pedro_> mrooney: second time is for a year
[13:39] <mrooney> great, thanks again! see you on launchpad ;)
[13:45] <seb128> hey hey pedro_
[16:41] <ogasawara> pedro_, bdmurray:  you guys okay if we overwrite the info at https://wiki.ubuntu.com/UbuntuBugDay/20080710 with a kernel hug day?
[16:41] <pedro_> ogasawara: yes, go for it :-)
[16:41] <bdmurray> hunh, voting for hug days
[16:42] <bdmurray> works for me too
[16:42] <persia> 486 beats 104 :)
[16:42] <pedro_> indeed :-P
[16:42] <ogasawara> heh
[16:42] <bdmurray> pedro_: did you ever sort your bughelper version?
[16:42] <pedro_> ogasawara: thanks for taking care of it :-)
[16:43] <pedro_> bdmurray: yep i'm totally sure it's 0.2.14
[16:43] <bdmurray> well, that's good
[16:54] <undadecor> I am interested in starting to confirm and triage bug reports.  I was wondering if someone would mentor me on a bug report.  I have one in mind:  https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/245220
[16:56] <persia> undadecor: That's a tricky one, as it's a request for a change.
[16:57] <persia> To determine the importance, you'd have to check to see if any of the python applications included by default in Hardy Kubuntu, or remaining after continous upgrade from default Kubuntu feisty require python-tk.
[16:57] <persia> If none of them do, it would be wishlist, as nothing is broken.
[16:57] <undadecor> persia:  Okay, that makes sense
[16:58] <persia> If some of them do, it's a bug in those packages for not depending on python-tk properly.
[16:58] <persia> In these cases, it's no longer wishlist.
[16:58] <undadecor> persia:  Would I need to get another person to verify the bug, or the reporter to repeat the problem?
[16:58] <persia> To confirm, you'd want to test the Feisty default Kubuntu install against the Hardy default Kubuntu install to see if python-tk is in one and not the other.
[16:59] <persia> I would expect the ultimate determination of this bug to be Won't Fix, as I presume the Kubuntu developers have made some choice, but first you'll want to confirm it (or mark it invalid explaining it was never default), and then try to get feedback from a Kubuntu developer.
[17:00] <undadecor> persia:  Okay, thanks
[17:00] <persia> What makes this extra tricky is that it's not a bug against a regular Kubuntu package, so the Kubuntu devs might not look at it by default.  There are usually a couple in this channel, so you might ask for an opinion from one once you confirm.
[17:03] <undadecor> persia:  So now would i change the Status to "Incomplete" until the rest of the information is figured out?
[17:04] <persia> undadecor: Only if you're waiting for information from the submitter.  While it's still you investigating, "New" is fine.
[17:04] <undadecor> persia:  Okay, thanks
[17:25] <thekorn> bdmurray, I updated the py-lp-bugs wiki pages today,
[17:25] <thekorn> https://wiki.ubuntu.com/BugHelper/Dev/python-launchpad-bugs/BugLis
[17:25] <thekorn> +t
[17:25] <thekorn> and https://wiki.ubuntu.com/BugHelper/Dev/python-launchpad-bugs/Bug
[17:26] <thekorn> will work on a doc about changes in py-lp-bugs 0.3 tomorrow morning
[17:28] <thekorn> and unfortunatly http://bazaar.launchpad.net/~bughelper-dev/python-launchpad-bugs/main/annotate/1000/basebuglistfilter.py does not work
[17:34] <thekorn> bdmurray, aha, 'head:' does the neccessary magic ;)
[17:34] <thekorn> http://bazaar.launchpad.net/~bughelper-dev/python-launchpad-bugs/main/annotate/head:/launchpadbugs/basebuglistfilter.py
[17:38] <bdmurray> thekorn: ah, that's cool
[17:46] <bddebian> Boo
[18:00] <Iulian> Boo to you too bddebian.
[18:20] <undadecor> persia:  After installing the images of Hardy and Feisty in a virtual machine, I confirmed that python-tk was not installed in either by default.  Is this enough verification to mark the bug as Invalid?
[18:21] <persia> undadecor: Not quite.  You also have to check if you can import the tk libraries by default: it may be that in feisty they were included in the python package (at least from my reading of the bug)
[18:23] <undadecor> persia:  You mean, run apt-get install python and then check to see if python-tk is installed?
[18:24] <persia> Not if it's installed, but if it works: remember that there is not always a tight association between package names and functionality,
[18:30] <undadecor> persia:  I tried to run a python script that imported Tkinter and received the error that I must install the package python-tk.  Does it now qualify as being Invalid?
[18:31] <persia> undadecor: If you got that on feisty, then yes.  When marking it invalid, be sure to report to the submitter that your investigations show that it wasn't default for feisty either, and how they can get the TK bindings.  Also, invite them to reset the bug to "new" with further information if they believe you have misunderstood the problem.
[18:48] <bryce> heya all
[19:37] <alex-weej> i have firefox-2 and firefox-3 both installed
[19:37] <alex-weej> but i don't need 2 anymore
[19:38] <alex-weej> if i try to remove 2, synaptic prompts me to also remove mozilla-firefox-locale-en-gb
[19:38] <alex-weej> bug?
[19:39] <persia> alex-weej: Do you need mozilla-firefox-locale-en-gb?
[19:39] <alex-weej> yes.
[19:40] <alex-weej> for firefox 3.
[19:40] <alex-weej> don't i?
[19:40] <seb128> alex-weej: aren't the firefox3 translations in language packs now?
[19:40] <alex-weej> maybe they are.
[19:40] <alex-weej> at least, Language Support isn't prompting me to install anything new. so maybe notabug.
[19:41] <persia> alex-weej: Try letting it be uninstalled and see if you've still localisation.
[19:41] <seb128> alex-weej: dpkg -L language-pack-base-en | grep firefox should give some indications
[19:50] <bryce> anyone here for the Xorg Hug day?  I'm available to answer triager questions
[19:52] <alex-weej> oooh bryce, i has questions about X
[19:52] <alex-weej> i dug into the synaptics driver yesterday
[19:53] <alex-weej> didn't have a clue what was going on, but i noticed that the HandleState function was simply calculating a number of vert/horiz scroll events and posting button down/up events in rapid succession
[19:54] <bryce> mm
[19:54] <alex-weej> the normal pointer movement is done with xf86PostMotionEvent(device, absolute = false, start valuator = 0, num valuators = 2, dx, dy)
[19:54] <alex-weej> i'd like to use something like that to somehow post delta-based scroll events to clients
[19:55] <alex-weej> i've no idea about the protocols or anything
[19:55] <alex-weej> you got any ideas?
[19:55] <alex-weej> i looked at the source for xf86PostMotionEvent, according to the comments above it's merely a convenience function for a very long routine of gore.
[19:56] <bryce> alex-weej: I would suggest talking to daniels on #xorg-devel about it; he's the input guru
[19:56] <alex-weej> fs. channel limit.
[19:57] <bryce> alex-weej: huh?
[19:57] <alex-weej> lol i'm in too many channels :P
[19:57]  * bryce rolls eyes
[19:58] <bryce> heh, anyway I'm not familiar with that particular routine myself offhand
[19:59] <bryce> you may want to try using the evdev driver, it seems to be getting more support from upstream
[19:59] <bryce> I'm not sure if it has all the functionality of synaptics yet, however if you can reproduce the problem with evdev it may be more interesting for upstream
[20:00] <alex-weej> bryce: interesting... i will investigate
[20:01] <bryce> daniels is in finland iirc; he could be at dinner.  You might want to just ask your question of him in the channel, and hopefully he'll spot it when he gets back in
[20:42] <LimCore> hello
[20:42] <LimCore> another day, another totall failure spoted in Ubuntu
[20:42] <LimCore> what the hell is "lgeneral"? Because in 2007 when I checked last, and also today, this program does NOTHING. wtf?
[20:45] <my_isp_sucks_c0c> hi again, my connection broken
[20:47] <my_isp_sucks_c0c> another day, another totall failure spoted in Ubuntu:
[20:47] <my_isp_sucks_c0c> what the hell is "lgeneral"? Because in 2007 when I checked last, and also today, this program does NOTHING. wtf?
[20:48] <snap-l> LimCore: For those of us playing along, what are you talking about?
[20:48] <LimCore> snap-l: about application "lgeneral". Can you install/run it, and tell me what it does? Because on my box it does nothing, which seems odd
[20:48] <LimCore> descrioption says it should be a game
[20:48] <bryce> LimCore: lgeneral is a game; I play it all the time
[20:49] <LimCore> well, how to run it exactly?
[20:49] <bryce> LimCore: it is a recreation of a proprietary game called PanzerGeneral, and you need to have the original game art and scenarios to make it run
[20:49] <LimCore> ok
[20:49] <bryce> LimCore: you can download them through the lgeneral website, but afaik not through apt (probably for legal reasons)
[20:49] <LimCore> doesnt this sounds like something someone might want PERHAPS to tell to the users?
[20:49] <afflux> we should add a hint in the description
[20:49] <LimCore> *something
[20:49] <bryce> it's a nice game if you like strategic turn-based wargames
[20:49] <afflux> right
[20:50] <bryce> LimCore: I would agree
[20:50] <greg-g> from the description: This is the game engine only - lgeneral requires scenarios that are available on http://lgames.sf.net/
[20:50]  * LimCore slaps nerdy developer with a big "User friendly, idiot!" book
[20:50]  * afflux looking for bugs
[20:50] <LaserJock> LimCore: it's in the description, as greg-g pointed out
[20:50] <snap-l> LimCore: Did you install the suggested package?
[20:50] <afflux> bug 90521
[20:50] <bryce> LimCore: in fact, I looked into this problem a bit, and I found that there are some user-crafted scenarios, and user-crafted art, which I think in theory could be integrated together and included in the packaging
[20:51] <LimCore> LaserJock: I daily read descriptions for around 1-2 hours, after I finish reading random man pages.  It should be in the application itself...
[20:51] <bryce> I suspect that wouldn't produce as fun of a game, but at least it'd work out of the box without licensing issues
[20:51] <LaserJock> LimCore: well, I don't disagree, but that's something to take  up with the authors
[20:51] <LimCore> ok I will
[20:51] <LaserJock> that's not particularly an Ubuntu issue
[20:53] <afflux> lgeneral was not updated since dapper
[20:53] <LimCore> why?
[20:54]  * bryce updates a bunch on https://wiki.ubuntu.com/UbuntuBugDay/20080703
[20:54] <afflux> upstream did not release new versions, as far as I can see
[20:54] <LaserJock> also, given that there are somthing like 14k packages and like 100 uploaders it can take a bit of time even if there were new versions
[20:55] <LimCore> I see
[20:55] <bryce> I've been playing the lgeneral pre-releases; they're pretty stable (only crashed once) and have a few new features, but no hugely drastic changes
[20:56] <LimCore> btw, I wonder how about changing a bit ubuntu philosophy
[20:56] <LimCore> like, making it easy to install packages from source, perhaps even support gentoos ebuilds
[20:56] <LimCore> that would rock
[20:57] <LimCore> and speed up deployment of opensource products too
[20:57] <LimCore> development
[20:58] <afflux> I'm afraid that the lgeneral upstream developer is not too active with maintaining lgeneral, since there were no further releases since at least 2006
[20:58] <bryce> LimCore: there was some discussion along those lines a month or two ago on ubuntu-devel-discuss
[21:00] <bryce> LimCore: being able to do something like, 'apt-get source <package>', hack hack, 'apt-get mkpatch', 'apt-get build', 'apt-get share' that wrapperizes all the pbuilder/bzr/quilt/etc. stuff for users would be slick
[21:00] <LimCore> indeed
[21:01] <LimCore> I would even get coding
[21:01] <LimCore> but also it would be good to stay in touch with developers, to not spend 50 hours to learn code layout and 1 hour for actuall patch
[21:04] <bryce> how do you mean?
[21:05] <LimCore> to be in contact with other people that know their way around code of given application; For example nice links and user friendly access to MLs of given project etc
[21:07] <bryce> heh, I'd just hit google for that
[21:09] <bryce> heya chrisccoulson
[21:09] <chrisccoulson> hi!
[21:11] <LimCore> btw I was thinking of a small project
[21:11] <chrisccoulson> bryce: Do you think this one is actually xorg related? https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/236210
[21:11] <chrisccoulson> i see this quite often on hardy, so i can confirm it
[21:11] <LimCore> STFUB - shut the fuck up, bitch; It would be aimed on ensuring that there is quick way to quickly MUTE different annoying things.
[21:12] <LimCore> for example, KDE does this nicelly by  "Turn off all sounds for all applications"  notifications option
[21:12] <greg-g> LimCore: could you please keep your language PG rated
[21:12] <LimCore> but other things, like say annoying xbell (bash, vim, etc) are not so easy to do
[21:12] <bryce> chrisccoulson: it doesn't seem like an xorg bug.  let me read more deeply
[21:13] <chrisccoulson> ok, thanks!
[21:13] <LimCore> btw, recently many my apps slow down incredibly at times and hand. Korganizer, OpenOffice.  I updated kernel recently to newest for 8.04 amd64. Im on Nvidia, SMP, glx-new. Anyone heared of that?
[21:13] <LimCore> *and hang
[21:14] <bryce> chrisccoulson: yeah I think comment #3 is spot on; that's exactly what I was thinking before I read it
[21:15] <LimCore> anyone had problems with some applications drawing slowly and "freezing" at times?
[21:15] <bryce> chrisccoulson: it *might* be a gdm bug, but I think comment #3 is correct that each of those processes should have bugs against them
[21:15]  * LaserJock wonders how bryce finds time to play games :-)
[21:16] <bryce> :-)
[21:16] <chrisccoulson> should i add each package to this report, or should it end up as multiple reports?
[21:16] <chrisccoulson> i see the same issue they describe with tomboy as well, and that has a pretty wierd side effect
[21:17] <bryce> chrisccoulson: yeah not sure...  I'm also wondering if it's a gdm bug
[21:18] <bryce> chrisccoulson: do you know seb128?  I would probably start by asking his opinion on the bug, and following his suggestion.
[21:18] <bryce> chrisccoulson: it appears these are all gnome-ish things that are breaking so perhaps he would know best how this bug should be handled
[21:19] <chrisccoulson> i know of sebastien. i'll subscribe him and see if we can get his opinion
[21:23] <awalton_1> bryce: if you don't mind the trouble, can I get your opinion on a stacktrace? I think it may be an X bug, but I'm not certain: http://launchpadlibrarian.net/15679573/gdb-nautilus.txt
[21:24] <bryce> awalton_1: sure, looking
[21:24] <awalton_1> orbit is where nautilus actually crashed, but it looks like it got there from X, which happened somewhere in cairo.. crazy trace
[21:25] <bryce> awalton_1: yep
[21:25] <bryce> awalton_1: btw having symbols and doing 'backtrace full' would provide more useful details (like local variable values and such)
[21:26] <bryce> without that info I'm not sure it's possible to pinpoint where the true error originated
[21:26] <awalton_1> yeah, I'm going to ask for that in a minute, but just looking at the stacktrace had me scratching my head.
[21:26] <bryce> offhand, the most interesting spot is right here:
[21:26] <bryce> #8  0xb74ce892 in _XIOError () from /usr/lib/libX11.so.6
[21:26] <bryce> No symbol table info available.
[21:26] <bryce> #9  0xb74d52f8 in _XGetXCBBuffer () from /usr/lib/libX11.so.6
[21:26] <bryce> No symbol table info available.
[21:27] <bryce> that's where it switches from a "normal" call (_XGetXCBBuffer) to an error handling call (XIOError)
[21:27] <bryce> so that's the point I'd like to see more details
[21:28] <awalton_1> are there any packages they'd need to install to see anything more from X? I noticed they're missing symbols from at least cairo and gdk..
[21:29] <bryce> well, obviously libX11 and libcairo, maybe libORBit too
[21:29] <bryce> may as well do xserver too, although I don't see calls against it
[21:30] <awalton_1> couldn't hurt I guess.. well thanks very much for the help
[21:31] <bryce> fwiw, I've seen a pattern with cairo bugs (confirmed in talking with cworth), that many "cairo" bugs are really general X bugs, that no one uncovered before cairo simply because there wasn't any library for getting at those particular functionalities
[21:31] <bryce> so this bug seems to fit with that pattern
[21:31] <bryce> awalton_1: sure!  good luck, and feel free to ping me once you have more info
[21:32] <awalton_1> will do :)
[21:44] <chrisccoulson> just looking at this bug https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/216411
[21:44] <chrisccoulson> i know it is well known that the refresh rate is incorrectly reported when using the nvidia binary drivers, so that's probably the issue here
[21:45] <chrisccoulson> you can't configure the refresh rate of an LCD can you? (I have a trusty old CRT at home!)
[21:48] <bryce> ah, depends on the LCD
[21:49] <bryce> some LCD's let you, most are fixed to e.g. 60 Hz
[21:50] <bryce> chrisccoulson: for that bug, I'd suggest asking for the missing Xorg.0.log and then reassigning the package to linux-restricted-modules-2.6.24, and update the title to begin with "[nvidia]"
[21:50] <bryce> chrisccoulson: honestly, there's probably zero we can do about the bug in any case
[21:51] <bryce> fwiw, some monitors are documented to run at 60 Hz, but for whatever reason they actually operate at a slightly different rate.  I have one that works at 57Hz for instance.  So that by itself is not that unusual.  It would be worthwhile to understand from the reporter what precisely they're experiencing as a problem
[21:52] <bryce> if there is no tangible issue aside from the rate not being exactly 60, I'd be tempted to call it a non-issue
[21:53] <chrisccoulson> I think it's just a case of the refresh rate being misreported as opposed to not being physically set correctly. it's well known that the NVIDIA drivers do this, and it is documented in /usr/share/doc/nvidia-glx-new/README.txt.gz. My CRT is reported as being 51Hz by the screen resolution tool with the nvidia drivers, when it's really refreshing at 75Hz. I'll ask for the Xorg.0.log, but I think this probably isn't really a bug
[21:53] <bryce> ah ok
[21:54] <bryce> ok, if you know it to be a known issue that's already documented, I guess just refer them to that file and close the bug.
[21:54] <bryce> in that case there's almost certainly zero we can do about it
[21:55] <bryce> or mark it as a dupe if that issue is already reported in linux-restricted-modules-2.6.24
[21:56] <joumetal> bug 238209 looks confirmed to me. see screenshots.
[21:57] <bryce> looking
[21:58] <bryce> ahh, that's a known issue.  one sec, I'll snag the bug to dupe against for you
[22:00] <bryce> joumetal: here you go https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/96991
[22:00] <bryce> joumetal: dupe to that bug
[22:03] <joumetal> bryce: marked it as dupe. bug 232026 looks still incomplete to me but there was a try to get a backtrace.
[22:07] <bryce> looking
[22:08] <bryce> hmm, sounding a bit like a kernel issue, if it kills the network
[22:09] <bryce> joumetal: yes you're right that it's still incomplete - the log attached doesn't actually have backtrace data in it
[22:09] <bryce> ahh
[22:10] <bryce> yeah in the description it says the network and caps lock freezes
[22:10] <bryce> so it's almost certainly a kernel bug
[22:10] <bryce> joumetal: please re-file that one against 'linux', and ping ogasawara to take it for further triaging
[22:18] <joumetal> ogasawara: bug 232026 seems to be a kernel bug.
[22:19] <ogasawara> joumetal: thanks, I'll take a look
[22:22] <chrisccoulson> i just closed bug 216411 as invalid, as the problem is a documented feature of the NVIDIA drivers. Out of curiosity, I did a search for similar bugs assigned to Xorg, and ended up closing another similar one. Then I found another one describing the same problem with 9 duplicates - and containing a big debate on whether the bug report should actually remain open or not: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-module
[22:23] <chrisccoulson> i'm not sure what to do with the 2 that i've closed now - whether to leave them as is, or re-open them and mark them as a duplicate of the other one i've found
[22:23] <joumetal> ogasawara: is it dupe of 223870?
[22:38] <bryce> chrisccoulson: your call.  You could also leave them closed and still mark them dupes
[22:39] <bryce> chrisccoulson: btw your link cut off, which bug was it again?
[22:43] <chrisccoulson> bryce - the master bug is 92599. the 2 bugs that i closed are 222516 and 216411
[22:45] <bryce> ok
[22:46] <bryce> wow, lrm 2.6.20
[22:46] <bryce> ancient :-)
[22:48] <bryce> hmm, sounds like a tradeoff between people wanting DynamicTwinView, and others wanting correct refresh rates
[22:49] <bryce> so it's sounding like maybe this is a WISHLIST item for Jockey
[22:50] <bryce> hmm
[22:50] <bryce> chrisccoulson: are you able to set WONTFIX?
[22:50] <bryce> chrisccoulson: I think for this bug what needs to be done is to mark it as also affect Jockey, set that task to Confirmed, and then mark the lrm task as WONTFIX
[22:51] <bryce> (or INVALID)
[22:51] <chrisccoulson> yeah, i agree with you
[22:51] <bryce> and set importance of the Jockey task to WISHLIST
[22:51] <chrisccoulson> i can't set the importance unfortunately...
[22:52] <bryce> ok, I can do that once you've finished your changes
[22:54] <chrisccoulson> i've added jockey now, confirmed, and set the lrm task as invalid. could you set the importance to wishlist now? thanks
[22:54] <bryce> sure thing
[22:54] <chrisccoulson> i'll add the 2 i've closed as dupe's as well
[22:55] <ogasawara> joumetal: sorry for the delay - I posted a comment to 232026 and marked it a dup
[22:56] <bryce> done
[22:57] <chrisccoulson> thanks!
[23:13] <joumetal> There is quite many xkeyboard duplicates. etc bug 222375. Is there already known parent bug?
[23:14] <joumetal> maybe bug 67188? it's old but have some new comments.
[23:17] <bryce> joumetal: that may be; xkeyboard doesn't get triaged too well so there are likely many dupes
[23:17] <bryce> let me look at these
[23:20] <joumetal> bryce: would it be useful if i create metabug about them?
[23:20] <bryce> joumetal: yes I think it probably would
[23:38] <joumetal> it's bug 245327.
[23:39] <bryce> needs  a more precise title
[23:40] <bdmurray> heh
[23:41] <bryce> heya bdmurray
[23:41] <Awsoonn> Bug 242984 looks as if it has the needed info, should it be set to 'triaged'?
[23:41] <joumetal> yep title is not good.
[23:42] <bryce> Awsoonn: yes, that is correct
[23:43] <Awsoonn> I am not a member of Bug Control, but would like to be. How can I fix that?
[23:44] <ikonia> Awsoonn: apply on launchpad.net
[23:46] <Awsoonn> awaiting approval
[23:46] <ikonia> there you go
[23:46] <ikonia> someone will review, approve or reject youi
[23:46] <ikonia> you
[23:46]  * Awsoonn presses an a oversized red button
[23:46] <Awsoonn> that was easy
[23:47] <bryce> :-)
[23:47] <chrisccoulson> i think i'm still awaiting approval (or rejection!) for ubuntu bug control
[23:48] <chrisccoulson> i tried to join sometime in may i think
[23:49] <Awsoonn> *nods* I also had applied before as well I thought, maybe I'm worthy now. :)