[02:00] <psusi> can someone tell me where Martin Farmer is in Ados City?  I was told to deliver him a pizza, but this town is huge and I can't find him
[02:01] <psusi> lol at Stichard Rallman
[09:56] <Luca1> Hi! I'm trying to use dual screen with Unity but as soon as the second screen is attached all the desktop result completely screwed up. I'm using ATI with opensource drivers (proprietary won't install). Is there anyone who knows of an already reported related bug? Should I report this myself?
[11:12] <c0nsaw> Hey people, I applied for a bug triage mentor during the week, is this facility still available, I haven't had any reply as of yet, thanks
[11:15] <yofel> vish: ^
[13:15] <Luca1> Hi! I'm trying to use dual screen with Unity but as soon as the second screen is attached all the desktop result completely screwed up. I'm using ATI with opensource drivers (proprietary won't install). Is there anyone who knows of an already reported related bug? Should I report this myself?
[13:15] <persia> Luca1, I suspect that nobody around knows the answer to that question.
[13:16] <persia> You might try searching for bugs on launchpad to see if you can find a similar one.
[13:16] <persia> If you can, check to make sure you have precisely the same issue before chiming in.
[13:16] <persia> If you have all the debug information collected, and are itching to post it, create a new bug, and then search: it's not hard to mark a bug as a duplicate if you discover it while searching.
[13:16] <Luca1> I already did that and found nothing. But I'm finding it quite difficult to find correct keywords for this issue.
[13:18] <Luca1> When I try to open the bugreport using ubuntu-bug I get a question that asks me if I was told precisely to report the bug. Should I say yes? Who should tell me I can report?
[13:18] <Luca1> Thanks for your help!
[13:18] <persia> I think you'll need to work on a more precise replacement for "completely screwed up".  While I don't know what is wrong, I do suspect that this phrase is unlikely to help someone else reproduce the issue.
[13:19] <persia> So, there's a tradeoff: if lots of folk file random bugs, people looking at bugs have less time to fix them (as they spend more time trying to understand them).  If nobody files bugs, then people don't know there are problems.
[13:20] <Luca1> In fact that is my problem. If I show you an image, could you be so kind to suggest a better definition?
[13:20] <persia> I generally only file bugs when I think I have a good description of the bug, can outline the expected and observed behaviour, and can describe how to reproduce it: I'm not sure that's the best model, but it's mine.
[13:22] <Luca1> I'm not native language, maybe someone could suggest a more correct description...
[13:22] <persia> Don't worry about the specific words, it's more about the level of detail.
[13:22] <Luca1> this is where I asked the first time, there is a screenshot: http://askubuntu.com/questions/44304/screen-completely-screwed-up-when-in-dual-screen-in-unity
[13:23] <persia> So, are there bands across the screen?  Do you have snow?  Are images rendering improperly?  Does the screen implode?
[13:24] <persia> Given the image you posted, I'd suggest describing the resolution of both monitors, and attempting to describe the black areas (can windows be moved there, or are they just wasted space), the overlap on the background, etc.
[13:25] <Luca1> It depends, sometimes I get only black lines alternated to white lines. Other times I have a situation like that I linked. More often a combination of the two. Almost always I get a combination of these effects.
[13:25] <persia> You also say "some other times only lines could be seen": it's important to describe the sorts of lines, whether they are moving, etc.
[13:25] <Luca1> Ok, so I'll state all of this in the report. Thank you very much.
[13:26] <persia> Right.  Describe the effects in detail.  I don't know that much about this particular area, but the more precise you can get about the observed issues (not just appearance, but also behaviour), the more likely someone familiar will understand the underlying issue.
[13:26] <persia> Good luck.
[13:27] <Luca1> Thanks for your help! Could you even be so kind as to suggest a possible subject for the report? As you said, screwed up is not quite descriptive and effective.
[13:28] <JoshuaL> Desktop results distored when attaching second screen?
[13:28] <JoshuaL> something like that
[13:28] <persia> I'm not sure.  "Apredictive rendering irregularities with ATI (whatever)" is the same as "screwed up" but looks different though.
[13:28] <JoshuaL> or garbled
[13:28] <JoshuaL> or that
[13:29] <persia> JoshuaL, Good suggestion!
[13:29] <Luca1> very good! Thanks for the assistance!
[13:31] <JoshuaL> Can someone confirm and/or set the importance of bug 771983 to low?
[13:31] <ubot4> Launchpad bug 771983 in indicator-me (Ubuntu) "Sometimes I am unable to type in the "Post to.." input field. (affects: 1) (heat: 158)" [Undecided,New] https://launchpad.net/bugs/771983
[13:31] <persia> JoshuaL, Why "Low"?
[13:33] <JoshuaL> persia, it has an easy work-around by just opening gwibber and posting the message there, its only a little usability issue
[13:33] <JoshuaL> persia, and it does not bother me that much (its my own bug report)
[13:36] <persia> JoshuaL, Set to "Low".  I always ask to just make sure folk have a shared understanding of "Importance".  I don't use gwibber, so I can't confirm.
[13:37] <JoshuaL> ok
[13:37] <JoshuaL> persia, thanks :)
[16:38] <penguin42> anyone know what to do with bugs that are oops's in ndiswrapper?
[17:53] <hggdh> penguin42: AFAIR you have to open a bug on the ndiswrapper ML
[17:54] <hggdh> since all that it does is wrap around Windows binaries
[17:55] <hggdh> http://sourceforge.net/tracker/?group_id=93482&atid=604450
[17:55] <penguin42> I guess it's difficult to know if the bug is in ndiswrapper itself or the windows driver
[17:56] <hggdh> it is, even more with the interfacing
[17:57] <hggdh> so -- when I was actually using ndiswrapper -- we would consider it a possible ndiswrapper emulation issue to star with
[17:57] <hggdh> then, if needed, a kernel bug would be opened
[17:57] <persia> If it is possible to OOPS ndiswrapper, that's a bug in ndiswrapper: note that it may be *caused* by a bug in the windows driver, but ndiswrapper should be trapping those and failing gracefully.
[17:57] <hggdh> yep
[17:58] <persia> The same logic applies to all "Is this a bug in the application or the library" questions: the answer is nearly always "both".
[18:24] <duncan-nz> I need someone running LibreOffice in Ubuntu 11.04 to check something for me. If you have the units under 'Options > Draw > General' set to cm, are your page dimensions under 'Format > Page' still set to inches?
[18:24] <duncan-nz> Please PM me if you also see this bug.
[18:48] <persia> duncan-nz, I don't seem to have an "Options" menu.  I'm happy to check, if you could provide a bit more guidance.
[18:51] <JoshuaL> question, a little while ago i reported bug 754825, someone from broadcom said that a fix for that problem had been submitted to Greg KH's staging-next tree. Shouldnt that bug be set to triaged instead of confirmed?
[18:51] <ubot4> Launchpad bug 754825 in linux (Ubuntu) (and 1 other project) "Kernel panic while using my system [brcm80211] [assertion "scb->magic == SCB_MAGIC"] (affects: 3) (heat: 91)" [Undecided,Confirmed] https://launchpad.net/bugs/754825
[18:51] <duncan-nz> Try under 'Tools > Options' it should be at the bottom.
[18:53] <JoshuaL> And can someone set the importance of bug 754840 to low please, it has a simple workaround and its only a little usability issue.
[18:53] <ubot4> Launchpad bug 754840 in linux (Ubuntu) "Have to switch manually between audio output connectors (affects: 3) (dups: 1) (heat: 101)" [Undecided,Confirmed] https://launchpad.net/bugs/754840
[18:54] <persia> duncan-nz, OK.  I found tools...Options.  I can't find Draw under that.
[18:56] <persia> JoshuaL, Bug 754840 set to "Low": you may want to note somewhere that this appears to be a "Jack detect" issue (assuming the problem is that it doesn't switch when you insert the plug for the speakers, and you are using audio cables for the speakers, rather than USB, etc.)
[18:56] <ubot4> Launchpad bug 754840 in linux (Ubuntu) "[HP Pavilion dv6 Notebook PCHave to switch manually between audio output connectors (affects: 3) (dups: 1) (heat: 24)" [Low,Confirmed] https://launchpad.net/bugs/754840
[18:57] <JoshuaL> persia, yeah I believe its an jack detect issue indeed, im indeed using speakers with a audio cabel.
[18:57] <JoshuaL> persia, i will change the description and say it is an jack detect issue
[18:57] <duncan-nz> There should be a section called LibreOffice Draw, open that and then click on the section 'General'.
[18:59] <persia> For 754825, I'm inclined to leave it alone: bjf set it to "Confirmed" after the note that it went upstream, and I trust his opinion about how to mark kernel bugs more than my own.
[19:00] <braiam> JoshuaL: you said that there is a workaround?
[19:00] <JoshuaL> braiam, yeah just change it manually
[19:00] <JoshuaL> persia, ok, was just wondering what should happen next.
[19:01] <persia> Wait for it to land :)
[19:02] <braiam> mm... I said that about a month ago but it doesn't resolve the issue, it's only with this laptop JoshuaL ?
[19:02] <persia> duncan-nz, OK.  I restarted LibreOffice, and ran Draw, and I found the unit of measurement.  I'm not seeing "Format > Page" anywhere.
[19:03] <JoshuaL> braiam, when I reported that bug it seemed to be a rare case.
[19:03] <duncan-nz> persia, one of the menu items: File, Edit, View, Insert, Format.
[19:03] <JoshuaL> spoke to someone at irc, cant remember who it was
[19:04] <braiam> nope JoshuaL
[19:04] <persia> duncan-nz, I get "Letter", which isn't ideal for my locale, but the units are in cm, as they were in the draw options.  I can't confirm the behaviour you describe (and thanks for walking me through it carefully)
[19:05] <braiam> persia: what locales are you using?
[19:05] <duncan-nz> persia, ok, looks like this is specific to my setup. Does your locale use cm or inch?
[19:05] <JoshuaL> braiam, sorry i thought you where talking about the kernel panic issue
[19:06] <duncan-nz> braiam, great minds think alike.
[19:06] <braiam> I have to patch my own, it use A4, persia
[19:07] <persia> duncan-nz, It should use "cm", but my environment isn't ideally clean.  You may want to launch a fresh image in a VM in a variety of locales to get useful data.
[19:07] <braiam> mine has about two weeks, and no issue duncan-nz
[19:08] <braiam> persia: and your locales are?
[19:08] <duncan-nz> persia, I'm staring to think the same. I remember that OpenOffice and Ubuntu haven't always been so good to do the right thing according to each locale. Mine is da_en (Denmark English) which hasn't always worked very well.
[19:09] <persia> My locale is a mix of en_IN and jp_JP: not precisely ideal for finding general cases.
[19:09] <persia> Wouldn't Denmark English be en_DA ?
[19:09] <duncan-nz> okay, thanks. I'll setup a VM before I report this as a problem.
[19:10] <duncan-nz> persia, probably, I couldn't remember how they are written.
[19:10] <braiam> persia: ty
[19:10] <braiam> persia: give me a sec to see...
[19:10] <JoshuaL> yet another bug which status can be set to low (bug 771720), i also hope i provided enough information.
[19:10] <ubot4> Launchpad bug 771720 in indicator-appmenu (Ubuntu) "Inbox counters sometimes don't show up in the indicator-appmenu (affects: 1) (heat: 158)" [Undecided,New] https://launchpad.net/bugs/771720
[19:11] <JoshuaL> sorry to bug you guys with my bug reports and its importance :p
[19:11] <JoshuaL> s/status/importance
[19:11] <persia> JoshuaL, I think 771720 needs more investigation.  Is it really an issue with indicator-appmenu?
[19:11] <persia> I suspect it's more likely to be indicator-messages.
[19:12] <persia> I further suspect that it's not that, but your email client (given that a manual send/receive fixes it)
[19:12] <braiam> persia: en_DK
[19:12] <persia> Or does the email client know about the messages although the indicator doesn't?
[19:12] <JoshuaL> persia, all those indicators are a bit confusing, thought it was the same as indicator-messages
[19:12] <persia> braiam, Ah, yeah, that looks better.  I was going merely on the "da_en" above.
[19:13] <persia> JoshuaL, I believe "indicator-appmenu" is the one with the menus from applications.
[19:13] <JoshuaL> ah
[19:13] <braiam> i have the entire locales branch to locate the clock bug...
[19:13] <persia> Anyway, that one needs more investigation: you can't confirm, but you *can* do a lot of the investigation to make sure that it's easy for the next person.
[19:14] <JoshuaL> persia, the client knows about the messages (and the inboxes) but the indicator does not, but its really random so i cant reproduce it with certain steps.. ill try to find more information which i can add
[19:15] <persia> Knowing which client an example of useful additional information :)  It would also be interesting to know if it can be reproduced with the release code, rather than just from Beta.
[19:16] <braiam> persia: yours and my locales are the same, but have different page size
[19:17] <persia> braiam, Considering that I've never connected this machine to my printer, or told it I like A4, I'm not that surprised my data is odd.
[19:17] <duncan-nz> Why is Virtual Box no longer in the repositories?
[19:18] <braiam> persia: yeah, but i want the letter size, and have A4 :$
[19:18] <persia> braiam, heh.
[19:19] <JoshuaL> persia, thanks :)
[19:20] <persia> duncan-nz, rmadison tells me it's in hardy, karmic, lucid, maverick, and oneiric.  Which repo are you checking?
[19:21] <JoshuaL> persia, i will change the affecting package aswel or do you advice to leave it for a while till i improve the bugreport itself?
[19:21] <stgraber> braiam: /etc/papersize ?
[19:21] <duncan-nz> persia, stupid synaptic can't see that 'virtual box' is the same as 'virtualbox' sorry for the fuss.
[19:21] <persia> JoshuaL, I think setting the correct affected package is the most important thing: otherwise the additional bug traffic you generate improving the report may not be directed to the correct people.
[19:22] <JoshuaL> persia, ill change it to indicator-messages then, thanks :)
[19:22] <persia> JoshuaL, You'll want to check to confirm that it is indicator-messages: I may be incorrect.
[19:23] <JoshuaL> persia, i will do