[00:01] <trond-> hi room. I have a dell e4310 and it can get into suspension mode, but it can't get out... kernel: 2.6.32-22 (as I'm having trouble with newer kernels. This makes the screen flicker like mad!)
[00:07] <SpamapS> trond-: you may have better luck asking in #ubuntu
[00:07] <SpamapS> trond-: this is more for discussing specific bugs and bug management.
[00:09] <trond-> ok. thanks.
[00:50] <rusivi> Is it outrageous to attach The Dell Project to bug 629117?
[00:50] <ubot2> Launchpad bug 629117 in linux (Ubuntu) "Suspend failing on Dell Latitude E4310 (affects: 3) (heat: 14)" [Undecided,Confirmed] https://launchpad.net/bugs/629117
[00:51] <rusivi> Seemed part and parcel...
[00:54] <hggdh> rusivi: the dell project is not Ubuntu, is it?
[00:54] <rusivi> Thought they would find interest in it
[00:54] <rusivi> :D
[00:55] <hggdh> not enough... we cannot open tasks for unrelated projects
[00:56] <rusivi> The Dell Project's bugs have (Ubuntu) in them
[00:56] <rusivi> Seems highly related.
[01:02] <hggdh> rusivi: correlation is not causation
[01:03] <hggdh> the bug already had a linux task, which, BTW, is correct
[01:03] <hggdh> why add another one, for a project you do NOT know what is about?
[01:03] <hggdh> actually, why _did_ you add another one?
[01:04] <hggdh> worse still, I had just told you not to do it :-(
[01:04] <rusivi> hggdh: Not trying to tangle with you, I felt and feel I did the right thing. Worst case they "Invalid" it.
[01:05] <hggdh> rusivi: you did NOT do the right thing.
[01:06] <rusivi> hggdh: As I respect your opinion as fellow community member, may I please have more information on why my actions were not the best way to go?
[01:08] <persia> rusivi, if there is uncertainty, always err on the side of sending fewest notifications.
[01:08] <rusivi> I felt no uncertainty in my actions.
[01:08] <persia> Adding tasks on random projects tends to err on the other side (as you end up notifying all the bug contacts for that other project).
[01:09] <persia> OK.  What is the Dell project about?
[01:09] <rusivi> https://bugs.launchpad.net/dell/+bug/550028
[01:09] <ubot2> Launchpad bug 550028 in linux (Ubuntu) (and 1 other project) "Dell Mini 9 Hibernate does not work (affects: 3) (heat: 25)" [Undecided,Expired]
[01:09] <persia> That doesn't answer my question.
[01:10] <rusivi> Well in the comments of that bug it mentions information not on the front page of the project.
[01:10] <rusivi> Persia: The answer to your question is, it depends on where you look.
[01:10] <hggdh> and? What is the project about?
[01:11] <persia> rusivi, No.  the project is definitely about something.  if you have to look, you don't know yet.
[01:11] <persia> It may be that this bug is interesting to them, but it is *their* responsibility to find out about it, if it is.
[01:11] <persia> It may be that "The Dell Project" is intended only to support some small number of specific devices.
[01:11] <rusivi> persia: np I'll refrain from adding them in the future.
[01:12] <persia> It may be that "The Dell Project" is someone's commercial support project.
[01:12] <persia> We usually don't know.
[01:12] <hggdh> rusivi: please do so. Consider this a warning
[01:12] <rusivi> hggdh: No offense was intended, my apologies.
[01:13] <persia> rusivi, It's not about that specific project: the key is to focus on the bugs *in Ubuntu*.  If you *know* that some specific package is affected, and you *know* that this package belongs to some specific upstream proejct, and you *tested* to confirm the bug also exists upstream, then (and only then) is it is appropriate to file the bug in their project.
[01:13] <hggdh> rusivi: no offense received. I am just despairing of telling you one thing, and seeing you disregard it
[01:13] <rusivi> hggdh: I already did it before you said not too.
[01:13] <persia> Most of the time it's *lots* easier to just work with the bug in Ubuntu and track down the problem in Ubuntu, and once a solution is fairly obvious, leave it for a developer.
[01:14] <persia> (or someone who has a close interest in the specific package, and is working closely with developers)
[01:14] <rusivi> persia / hggdh: lesson learned. Won't do so moving forward.
[01:14] <persia> rusivi, Excellent :)
[02:30] <rusivi> Trying to follow Comment #4 bug 120569 leads to ... print "lang is None"
[02:30] <rusivi>   File "<stdin>", line 2
[02:30] <rusivi>     print "lang is None"
[02:30] <rusivi>         ^
[02:30] <rusivi> IndentationError: expected an indented block
[02:30] <ubot2> Launchpad bug 120569 in gtkspell (Ubuntu) (and 3 other projects) "[gutsy] gtkspell segfaults when trying to set the language on gtk.TextView (dups: 3) (heat: 2)" [Medium,Triaged] https://launchpad.net/bugs/120569
[02:30] <rusivi> I'm a baby-python so idk what I am missing
[02:31] <rusivi> I'm doing this in the Terminal
[02:42] <yofel> because python uses indentation to specify functional blocks, press 'tab' at the beginning of every line that has a '...' in the post
[02:44] <yofel> except for the line where it says 'else:'
[03:01] <rusivi> yofel ty
[04:53] <intrader> Anyone, I am looking into inconsistencies of the manner in which 10.10 is treating shells scripts (like Pharo.sh).  I have just tried OpenSolaris, Fedora, Mandriva, ubuntu 9.04 and mint. They all show a context menu of 'Open' for this script file. Ubuntu 10.10 does not - Further all those distributions load the Pharo IDE without problem. When I change the property of the file to executable, then the context menu shows 'Open',
[04:53] <intrader> but
[04:53] <intrader>   the execution does not open the IDE.
[04:54] <intrader> #ubuntu+1 tells me that the reason is changes in gnome.
[04:55] <intrader> By the way, the latest update to 10.04 make it work the same as 10.10.
[05:28] <skeeby> hey all
[05:33] <mrand> Howdy skeeby
[06:52] <JanC> intrader: sounds like this might be related to the new security policy (non-executable files should be non-executable)
[06:58] <skeeby> when marking a new bug as a dupe, should i change the status to reflect the parent bug?
[07:00] <persia> skeeby, We generally don't bother.
[07:00] <skeeby> kk
[07:04] <mrand> skeeby: minimizing bug mail is always one of my goals.  So I try to think through all the actions I'll be doing to a bug and get them done in as short a time period as I can in hopes of them landing in a single email.
[07:04] <mrand> Not the question you asked, but related... and just popped into my head
[07:06] <skeeby> thank you
[07:08] <skeeby> in bug 651782 the reporter marked the bug back from incomplete -> new. is there any reason why that should be necessary?
[07:08] <ubot2> Launchpad bug 651782 in friendly-recovery (Ubuntu) "booting into recovery mode and selecting resume normal boot brings you to a text login (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/651782
[07:12] <skeeby> komputes, are you there?
[07:12] <persia> skeeby, It's often done when someone provides requested information, especially by people who were working with bugs before LP had "Incomplete with response" vs. "Incomplete without response"
[07:14] <skeeby> yeah i dont wanna have a status war with someone within the first handful of bugs i started triaging =X
[07:14] <persia> And especially not with someone with that history of bug reporting :)
[07:15] <persia> My recommendation would be to try to reproduce with the steps komputes provided.  If you can or can't, share your experience on the bug.
[07:15] <skeeby> well im running 10.10 atm, so my results may be irrelevant
[07:15] <persia> No, they would be very relevant.  If it happens for komputes in 10.04 but doesn't happen for you in 10.10, then it's only a Lucid bug, and fixed in Maverick.
[07:16] <persia> (and, technically, 10.10 doesn't exist yet)
[07:16] <skeeby> good point
[07:16] <persia> komputes tends to be a good bug reporter, so this makes a good opportunity to work deep triage with someone cooperative :)
[07:17] <skeeby> excellent
[07:38] <skeeby> yeah i def reproduced computes problem
[07:39] <skeeby> komputes*
[07:41] <persia> skeeby, Excellent.  What ought you do next to the bug?
[07:41] <skeeby> confirm it
[07:41] <skeeby> mark importance to probably med?
[07:41] <persia> !importance
[07:41] <ubot2> You can learn about setting bug importance at https://wiki.ubuntu.com/Bugs/Importance
[07:42] <skeeby> aye im reading it atm
[07:42] <persia> So, based on those definitions, why "Medium"?
[07:43] <skeeby> well it effects the recovery console
[07:43] <persia> OK.
[07:43] <skeeby> however a reboot is a the workaround
[07:44] <skeeby> which could be considered easy
[07:44] <skeeby> maybe low...
[07:44] <skeeby> *facepalm*
[07:45] <persia> next, imagine why a user might be in the recovery consoe.
[07:45] <skeeby> i would lean toward low would you agree with that assessment?
[07:46] <skeeby> problem with hw
[07:46] <skeeby> or core packages
[07:46] <persia> Perhaps described as "cannot boot"?  if so, would a reboot work?
[07:47] <skeeby> ah
[07:49] <persia> skeeby, Anyway, I'd probably agree with "Medium", but wanted to go through the exercise of why that makes a good choice :)
[07:50] <skeeby> oh definitely
[07:50] <skeeby> im new to the process too so it definitely helps
[07:50] <skeeby> i appreciate it
[07:50] <persia> So go ahead and set those values.
[07:52] <skeeby> gotchya
[07:54] <skeeby> i need to set status to "triaged" to set importance
[07:55] <skeeby> id say it could still use a little more feedback before taking it to the next step
[07:56] <persia> I'd say "confirmed", rather than "triaged".  You don't yet know why it does that, just that it does on two different installs (so it's probably an Ubuntu issue rather than just being komputes' computer)
[07:57] <skeeby> yup
[07:58] <skeeby> kompute seems to know what hes doin so ill follow his lead =p
[07:58] <persia> OK.  Don't forget to set the Importance.
[08:01] <persia> skeeby, ?
[08:01] <skeeby> i cant modify it
[08:01] <persia> OK.  So what does the wiki suggest folk who can't (yet) modify importance do?
[08:03] <skeeby> ah i thought i had permission as a bugsquad member
[08:03] <persia> Nope.  permission to modify importance is bugcontrol
[08:03] <skeeby> i guess someone from bugcontrol will need to set the importance for bug 651782 to medium please =)
[08:03] <ubot2> Launchpad bug 651782 in friendly-recovery (Ubuntu) "booting into recovery mode and selecting resume normal boot brings you to a text login (affects: 2) (heat: 10)" [Undecided,Confirmed] https://launchpad.net/bugs/651782
[08:04]  * persia does so
[08:04] <persia> OK.  Now the bug is confirmed, and importance is set.
[08:04] <persia> next step: dig in and find a cause.
[08:05] <persia> You asked komputes for error logs or similar.  Since you can replicate it, maybe you can generate some yourself?
[08:05] <skeeby> thank you
[08:05] <skeeby> yup gonna dig through them right now
[08:05] <persia> Just always remember to ask folk to set Importance if you know the right value.  Once you've triaged some bugs (with help from bugcontrol members), you can apply to bugcontrol :)
[08:06] <skeeby> gotchay
[08:06] <persia> Good luck :)
[08:06] <skeeby> haha thx
[08:07] <skeeby> gotta scroll through all the errors i generated after i ran startx from root shell in recovery mode >_<
[08:24] <vish> ah, bcurtiswx aint here..
[08:25] <vish> persia: usually its just people asking here for some BC to set the importance..  maybe we need to mention it on the wiki as well.. [it might already be there though, need to check]
[08:25] <persia> vish, It used to be on the wiki: if it isn't, please restore it.
[08:25] <vish> skeeby: which wiki page were you following?
[08:27] <vish> no mention of this channel here » https://wiki.ubuntu.com/Bugs/Importance
[08:32] <skeeby> vish: i was following  https://wiki.ubuntu.com/Bugs/HowToTriage
[08:34] <skeeby> i suppose adding it to that wiki wouldnt be a bad idea
[08:34] <vish> hidden quite well under Feature Requests section "Only the members of the Ubuntu Bug Control  team can do so. If you're not a member you'll have to ask someone who is to do it for you. Paste the bug number in #ubuntu-bugs and say you think the bug should be set to 'Wishlist'. Someone will notice and set it for you, although not necessarily immediately. "
[08:34] <vish> that needs to be on the importance page as well, and somewhere more generic
[08:36] <persia> Indeed.  All new bugsquad members should be pointed on the path to bug control, with clear guidance that causes them to get involved with us to review their work as they do it.
[08:37]  * vish edits importance page..
[08:48] <vish> persia: done, could you check the wiki now? » https://wiki.ubuntu.com/Bugs/Importance
[08:51] <persia> vish, That renders *horridly* for me, in multiple font sizes, seemingly randomly, indented, and in hard-to-read italics.
[08:52] <vish> persia: weird.. screenshot pls? i see monospaced fonts there.. i dint want to use bold
[08:52] <persia> vish, also, I'd suggest putting that at the bottom of the page: most folk would do well to read about importances before setting them (as most users of that page are likely to be bug submitters wondering what we meant or bug control members trying to determine the right Importance)
[08:52]  * persia waits longer for gimp
[08:56] <persia> vish, http://people.ubuntu.com/~persia/importance.png
[08:57] <vish> hrm.. that is indeed not what i intended.. :)
[08:57] <persia> I figured :)
[08:57] <vish> let me try something different
[09:58] <vish> persia: i think its fixed now..
[09:58] <vish> btw, what size fonts do you use?
[09:58] <vish> seems to me 8pt or smaller
[09:58] <vish> be*
[09:59] <persia> I use the default.
[09:59] <persia> But I have a 1400x1050 screen, and adjusted the DPI correctly, to match the screen size.
[10:00] <persia> Looks a bit better, but still wild variation in font sizing.
[10:01] <persia> I don't think it's worth fixing though, as you do want the font family change.
[10:04] <vish> :D
[10:39] <AbhiJit> Membership renewed until 2011-10-06.
[10:39] <AbhiJit> is this a yyyy-mm-dd?
[10:39] <AbhiJit> or yyyy-dd-mm?
[10:40] <AbhiJit> hi
[10:51] <jibel> AbhiJit, Hi, yyyy-mm-dd
[10:51] <AbhiJit> jibel, ok
[14:42] <charlie-tca> hggdh: does server have it's own docs source package?
[14:44] <charlie-tca> never mind, I found it
[15:20] <charlie-tca> Let's not forget that on this release day for maverick RC, we have a great BugDay - https://wiki.ubuntu.com/UbuntuBugDay/20100930
[15:39] <xelister> my terminus font is uglified in recent versions. a known problem?
[15:39] <xelister> national characters like ą ę ż look like crap
[15:41] <xelister> it is because I can not set font size 14 in some applicatiosn - they force font size 15 that looks fugyl
[16:00] <charlie-tca> hmm, quitting isn't working, may as well work on BugDay! https://wiki.ubuntu.com/UbuntuBugDay/20100930
[16:23] <jcastro> bdmurray: are you still "random guy who can scrape launchpad data for me to find something useful?"
[16:27] <bdmurray> jcastro: yeah, I'm really rather stuck at the moment but should have some time later today
[16:27] <jcastro> oh it's no rush, just one of those "I have a theory, I wonder what the data really says"
[17:11] <vish> bcurtiswx_ : nah, dint miss one, twas just bad formatting ;)  missed a "]]" in between
[17:31] <rusivi> sysvinit webpage maintainer, minor syntax error, missing a t at the end of management, just bringing to your attention ty ->
[17:31] <rusivi> Upstream
[17:31] <rusivi> sysvinit
[17:31] <rusivi> programs required for booting a Debian system and doing basic process managemen
[17:31] <rusivi>  https://launchpad.net/ubuntu/+source/sysvinit
[18:00] <bcurtiswx_> vish, ah ok.. didn't see
[18:01] <vish> bcurtiswx_: nice catch btw, i should have checked it :)
[18:01] <bcurtiswx_> :
[18:01] <bcurtiswx_> :)
[18:04] <Tiibiidii> hello
[18:04] <Tiibiidii> a bug that obiouvsly hasn't been fixed has been marked as fix released by the launchpad janitor
[18:05] <devildante> what bug number, please? :)
[18:06] <Tiibiidii> it happened that a branch with a workaround (that doesn't fix the problem but makes the program usable) has been loaded, then a packager linked the bug in the debdiff... so the janitor decided to flag it as released... is it correct to but it back to the previous status?
[18:06] <Tiibiidii> #606470
[18:06] <Tiibiidii> bug #606470
[18:06] <ubot2> Launchpad bug 606470 in monodevelop (Ubuntu) (and 1 other project) "Monodevelop doesn't show its menu in the panel (affects: 9) (dups: 3) (heat: 46)" [Undecided,Fix released] https://launchpad.net/bugs/606470
[18:08] <devildante> it was fixed in monodevelop only
[18:08] <devildante> the true fix will be in appmenu-gtk ;)
[18:13] <Tiibiidii> devildante: actually, it's not fixed in monodevelop
[18:13] <devildante> ah
[18:13] <Tiibiidii> it would've been fixed if the bug was titled:
[18:14] <Tiibiidii> "monodevelop doesn't show its menu"
[18:14] <Tiibiidii> that is: monodevelop doesn't have a menu and it's unusable
[18:14] <AlexzAK> Hi Everyone! I'am trying to understeand bug statuses used at launchpad. What bug status "triaged" mean? Whan next action to be done on such bugs?
[18:14] <Tiibiidii> but the bug is about the monodevelop integration with the menu panel (and thus unity)
[18:14] <Tiibiidii> do you think it's fine to change status?
[18:15] <devildante> Tiibiidii: the thing which is supposed to implement the fix is appmenu-gtk
 do you think it's fine to change status? <-- i think i'll change the status... at the very least it will let other future people see this bug, and avoid duplicates before filing a new bug against monodevelop
[18:17] <devildante> Tiibiidii: as you wish... but please leave a comment stating why you did that
[18:17] <Tiibiidii> unless there's some other reason i'm not aware of for avoiding changing a bug status
[18:17] <Tiibiidii> ok
[18:17] <vish> AlexzAK: once a bug is set to "triaged" is means that it has all info needed and is ready for a developer to start working on a fix
[18:17] <Tiibiidii> thank you for the suggestions
[18:17] <devildante> np ;)
[18:17] <vish> AlexzAK: info from the user that is, but the developer can ask new questions later too
[18:18] <vish> !status » AlexzAK
[18:18] <ubot2> vish: Error: I am only a bot, please don't think I'm intelligent :)
[18:18] <vish> !status | AlexzAK
[18:18] <ubot2> Factoid 'status' not found
[18:18] <vish> huh!
[18:19] <vish> AlexzAK: https://wiki.ubuntu.com/Bugs/Status
[18:20] <vish> !bugstatus
[18:20] <ubot2> You can find out about how Ubuntu uses bug statuses here: https://wiki.ubuntu.com/Bugs/Status
[18:20] <vish> ah ha!
[18:25] <AlexzAK> vish: Thanks for link! Just what i needed.
[18:27] <Tiibiidii> i think i'll change the status... at the very least it will let other future people see this bug, and avoid duplicates before filing a new bug against monodevelop <-- uhoh, now that i think better, the automatic duplicate search, also fetches results from "fix released" bugs... it's missing from searched bugs, but...
[18:28] <Tiibiidii> whatever, i shouldn't spend so much time thinking about it...
[18:43] <intrader_> I am following up on a possible deficiency of 10.10 RC - in this distribution shell scripts must be set to executable before the context menu offers the 'Open' (with dialog to confirm that you want to execute a script). This is contrary to normal ubuntu and unix practice
[18:44] <intrader_> I must be logged in at home as well - pardon the '_'
[18:45] <devildante> intrader_: maybe it's a developer decision?
[18:45] <intrader_> devildante: how so?
[18:46] <devildante> I mean, maybe the devs decided to remove that dialog when the script is not executable?
[18:47] <intrader_> devildante: 10.10 RC does not offer the 'Open' if the script does not have the executable bit on. The new version does offer the 'Open' and the dialog if the script file is flagged as executable.
[18:48] <devildante> ah
[18:48] <devildante> then it's a bug, report it
[18:48] <devildante> :)
[18:48] <intrader_> devildante: under what project or module?
[18:48] <devildante> intrader_: nautilus
[18:51] <intrader_> devildante: if you don't mind what is the url where I report the bug?
[18:52] <AlexzAK> devildante: Should intrader_ run 'ubuntu-bug nautilus' command?
[18:54] <intrader_> devildante: I found it, it is https://bugs/launchpad/ubuntu
[18:58] <hggdh> yes, ideally 'ubuntu-bug nautilus' should be used
[19:15] <intrader_> I have reported bug https://bugs.launchpad.net/ubuntu/+bug/652283
[19:15] <ubot2> intrader_: Error: Bug #652283 is private.
[19:16] <intrader_> The bug should be visible as I changed it in launchpad. It is a security related bug as it affects execution of .EXE, .BAT,. .COM and shell scripts. I suggest that the dialog to confirm execution should ask for root permission.
[19:17] <AlexzAK> hggdh: Hi! Can you check my recent actions on bug #49800 ?
[19:17] <ubot2> Launchpad bug 49800 in mascyma (Debian) (and 1 other project) "No .desktop (heat: 4)" [Unknown,Fix released] https://launchpad.net/bugs/49800
[19:17] <charlie-tca> intrader: security bugs are always private
[19:18] <intrader_> charlie-tca: uhm, what can I do to make it public - I have reported most of the behavior here, but I have more details in the bug.
[19:19] <charlie-tca> If you mark it security, you can not make it public. It will stay private as a security issue
[19:19] <hggdh> AlexzAK: so it is (it seems) a regression
[19:20] <intrader_> charlie-tca: maybe that way it will be fixed pronto!
[19:20] <intrader_> charlie-tca: good to see you here again; you help me before
[19:20] <AlexzAK> hggdh: yes it is... It is valid in this case?
[19:20] <charlie-tca> No, but the security team will look at it and decide if it is a security issue or not
[19:21] <hggdh> AlexzAK: ideally, we would open a new bug on that, and link back to this one -- *this* bug is indeed fix released, the problem resurfaced o Maverick
[19:21] <hggdh> AlexzAK: can you do that? Open a new bug on macsyma, and refer to this one?
[19:22] <intrader_> charlie-tca: image if you will that someone brings in an .EXE file that does not use libraries, and executes it in 10.10
[19:22] <intrader_> charlie-tca: a perfect rootkit
[19:22] <rusivi> I've heard they have one for Android
[19:23] <AlexzAK> hggdh: I see... PeterPall reopened it.... No, i have no ubuntu 10.10 installed at my current machine :( So ubuntu-bug command will not work :(
[19:24] <AlexzAK> hggdh: So i must reset bug #49800 status to old "Fix released"?
[19:24] <ubot2> Launchpad bug 49800 in mascyma (Debian) (and 1 other project) "No .desktop (heat: 4)" [Unknown,Fix released] https://launchpad.net/bugs/49800
[19:24] <AlexzAK> hggdh: Can you file new one?
[19:25] <hggdh> AlexzAK: yes, it should be fix released
[19:26] <hggdh> AlexzAK: you yourself can open the new bug and refer to this -- it would be a good exercice for you ;-)
[19:26] <AlexzAK> hggdh: Ok, i'll try...
[19:27] <hggdh> AlexzAK: thank you! And I will be here to verify the new bug with you :-)
[19:31] <hggdh> AlexzAK: I declined the Maverick nomination on 49800, and added a comment explaining why we moved it back to FixReleased.
[19:32] <hggdh> AlexzAK: ideally, all changes in status should also have an explanation for the change
[19:36] <hggdh> hum. I downloaded the source, and I do see a ./debian/mascyma.desktop
[19:41] <AlexzAK> hggdh: What? How can it be... I don't see mascyma.desktop in binary
[19:42] <hggdh> because it seems it is not being packaged... the file is there
[19:43] <AlexzAK> hggdh: my new bug is bug  #652299
[19:43] <ubot2> Launchpad bug 652299 in mascyma (Ubuntu) "Package does not contain .desktop file, so dont displayed in menu (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/652299
[19:43] <hggdh> AlexzAK: thanks. Now can you add a link to it from 49800?
[19:44] <AlexzAK> hggdh: How can i do it? I dont see link for that :(
[19:45] <hggdh> AlexzAK: in a comment; currently LP does not support linking bugs
[19:45] <AlexzAK> hggdh: Their dev brunch indeed contains desktop file
[19:47] <AlexzAK> hggdh: Question: Can i set bug status to Confirmed or New ?
[19:47] <AlexzAK> hggdh: Me is bug author, so i should not to set status to confirmed. right?
[19:48] <hggdh> AlexzAK: usually you should not confirm your own bugs
[19:48] <hggdh> AlexzAK: I am installing mascyma now, and will confirm
[19:49] <AlexzAK> hggdh: But that bug not New. It should be "Triaged"? right?
[19:49] <hggdh> AlexzAK: right now it is new, until we can explicitly confirm it (which I should do in a few)
[19:50] <AlexzAK> hggdh: ok
[19:50] <hggdh> it will be triaged when we add an upstream (in this case, debian) bug #
[19:50]  * charlie-tca done all the bugs he can today. He will be leaving now. Keep hitting the Bugday, please!
[19:51]  * devildante hugs charlie-tca
[19:51] <hggdh> pfui! 47Mbytes of download, 167Mbytes of new installed stuff!
[19:51] <devildante> hggdh: still better than open/libreoffice :p
[19:51]  * devildante needs to stop ranting :p
[19:52] <hggdh> devildante: heh. There is that, yes. But nothing beats Latex/Texlive...
[19:52] <devildante> really?
[19:52] <devildante> (genuine question)
[19:56] <vish> "Thanks again (and despite hiccups, I am sold on Linux and Ubuntu!)"  :)
[19:56] <devildante> yay! :)
[19:56] <vish> from » https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/348914/comments/5
[19:56] <ubot2> Launchpad bug 348914 in xserver-xorg-video-intel (Ubuntu) "Display intermittently fails on login with Samsung 205BW (heat: 5)" [Undecided,Incomplete]
[19:58] <hggdh> AlexzAK: confirmed
[19:59] <hggdh> devildante: run synaptix, and search on texlive -- change the columns to also have used space
[19:59] <hggdh> synaptic
[20:02] <AlexzAK> hggdh: Good! Yep! So this bug will be "Triaged" when bug-report to upstream maintainers will be commited?
[20:07] <hggdh> AlexzAK: yex, this is the idea
[20:10] <AlexzAK> hggdh: page https://wiki.ubuntu.com/Bugs/Status says "should be looked at by a developer and has enough  information", so i thinked "Triaged" is when bug is ready, but not when developer alerted...
[20:12] <AlexzAK> hggdh: I thinked first set-to-triaged, second alert-developers...
[20:12] <hggdh> AlexzAK: indeed, it could go to triaged
[20:13] <hggdh> AlexzAK: but the maintainers of mascyma are at Debian, not here -- so I would rather only set it triaged when we have a debian bug on it
[20:13] <pjk> Hello
[20:14] <AlexzAK> hggdh: ok. I understand it. Thanx!
[20:14] <pjk> is i2c kernel errors known for usb dvb devices ?
[20:14] <hggdh> AlexzAK: mascyma is sync-ed from Debian, we did not make any local changes. So... the developer, or rather, maintainer, is in Debian
[20:15] <pjk> kernel is :  2.6.35-22-generic #33-Ubuntu
[20:16] <AlexzAK> hggdh: I agree with you. Just cleared it. I'll go to sleep now. See ya.
[20:16] <hggdh> AlexzAK: see you, and thank you for helping
[20:16] <AlexzAK> np
[20:17] <hggdh> pjk: I do not know, sorry
[20:17] <pjk> [132292.805217] tda18271_read_regs: [3-00c0|M] ERROR: i2c_transfer returned: -1
[20:17] <pjk> i2c errors started after upgrade to maverick
[20:18] <pjk> [132292.805229] tda18271_ir_cal_init: [3-00c0|M] error -1 on line 811
[20:20] <pjk> well maybe file a bug... cheers
[20:47] <intrader> devildante, charlie-tca: should I submit a report for the buggy part of same bug report?
[21:00] <drizztbsd> Hi, I'm the leader of an embedded development team. We use ubuntu as our development platform, the problem is that ubuntu maverick has a SERIOUS bug in tar ( https://bugs.launchpad.net/ubuntu/+source/tar/+bug/652183 ) that does not allow us to do the migration to 10.10. Should you fix it before the release?
[21:00] <ubot2> Launchpad bug 652183 in tar (Ubuntu) "tar 1.23-2 enters dead loop on extracting symlinks with -k option (affects: 1) (heat: 6)" [Undecided,New]
[21:05] <yofel> debian bug 576876
[21:05] <ubot2> Debian bug 576876 in tar "tar: infinite loop in case of existing symlink" [Important,Fixed] http://bugs.debian.org/576876
[21:06] <bcurtiswx_> gnome bug 345434
[21:06] <ubot2> Gnome bug 345434 in general "GDM needs to start at-spi's registryd" [Enhancement,Resolved: fixed] http://bugzilla.gnome.org/show_bug.cgi?id=345434
[21:06]  * bcurtiswx_ 's jaw drops
[21:06]  * bcurtiswx_ hugs ubot
[21:07] <drizztbsd> yofel: I written it in my bug
[21:07] <yofel> drizztbsd: right, I was curious what the debian bug with the fix discussion whas
[21:07] <yofel> *was
[21:07] <drizztbsd> oh sorry
[21:13] <yofel> agreed, this should be fixed
[21:13] <hggdh> drizztbsd: I marked it Triaged/Medium; I am afraid it may be too late for Maverick, but it should be considered for a SRU
[21:13] <hggdh> perhaps even a 0-day one
[21:14] <drizztbsd> ok thanks
[21:14] <yofel> hggdh: we got in each others way again :P
[21:15] <hggdh> yeee! /me marks another goal on concurrent work without critical sections
[21:15] <yofel> .D
[21:20] <hggdh> yofel: but, actually, you won :-)
[21:27] <intrader> Question about duplicates - how to remove duplicate classification 6311030 and 636970 - I am afraid it hides 631130
[21:28] <intrader> Sorry 631130
[21:28] <yofel> bug 631130
[21:28] <ubot2> Launchpad bug 631130 in opensuse (and 3 other projects) "In all apps, slow UI since 10.04 install (affects: 2) (dups: 1) (heat: 20)" [Undecided,Invalid] https://launchpad.net/bugs/631130
[21:34] <intrader> I have commented into bug 636970.
[21:34] <ubot2> Launchpad bug 636970 in ubuntu "Overall poor performance in Maverick (dup-of: 631130)" [Undecided,New] https://launchpad.net/bugs/636970
[21:34] <ubot2> Launchpad bug 631130 in opensuse (and 3 other projects) "In all apps, slow UI since 10.04 install (affects: 2) (dups: 1) (heat: 20)" [Undecided,Invalid] https://launchpad.net/bugs/631130
[21:35] <intrader> re bug 636970 - its title is misleading as I have not experienced maverick performance problems - only in 10.04
[21:35] <ubot2> Launchpad bug 636970 in ubuntu "Overall poor performance in Maverick (dup-of: 631130)" [Undecided,New] https://launchpad.net/bugs/636970
[21:35] <ubot2> Launchpad bug 631130 in opensuse (and 3 other projects) "In all apps, slow UI since 10.04 install (affects: 2) (dups: 1) (heat: 20)" [Undecided,Invalid] https://launchpad.net/bugs/631130
[21:37] <yofel> hm, 631130 is the master bug so it's not hidden, the other one is hidden, but the other one indeed doesn't show anything specific about nvidia
[21:37] <yofel> and njin isn't here currently
[21:38] <intrader> yofel, its title is misleading as it implied that maverick has performance problems
[21:38] <yofel> hm, actually... that bug says that maverick is slower than lucid, while you say that lucid is slower than before
[21:39] <yofel> well, wait for an answer or ping njin when he's here as he marked that bug as a dup
[21:39] <intrader> yofel, I see how the master bug relationship. So 631130 is not hidden as I feared. Maverick is not slower than lucid, the reverse is true for me
[21:42] <intrader> yofel, so far maverick is much, much better than 10.04 - has a problem which I reported in bug 652283.
[21:42] <ubot2> intrader: Bug 652283 on http://launchpad.net/bugs/652283 is private
[21:43] <yofel> can't see that one, leave it private. (unretraced crash?)
[21:44] <intrader> yofel, related to the execution of scripts including classification of .EXE, .BAT, and .COM as executable scripts
[21:45] <yofel> ah, that one
[21:45] <intrader> yofel, the .EXE 'capability' would immediately enable attacks on maverick
[21:45] <yofel> I remember the discussion we had now
[21:46] <intrader> yofel, yeah - good that you are around!
[21:47] <yofel> intrader: did you post any private information on that bug?
[21:48] <intrader> yofel, do you know how I can review 652283 - I would like to remove the security component from that bug report and make a new report from it.
[21:48] <skeeby> if its marked as dupe the master bug may be private?
[21:48] <skeeby> i may also be jumping into the conversation at a bad time >_<
[21:49] <yofel> skeeby: the dup and this bug have nothing to do with each other
[21:49] <yofel> (and bugs may be marked as duplicates of private bugs, the retracer does that all the time)
[21:49] <intrader> skeeby, np - it is related to two bug reports 631130 and 652283
[21:49] <skeeby> yeah
[21:51] <intrader> yofel, I don't see a way in launchpad to search to bring up a bug report back
[21:52] <ojap> @hggdh hello
[21:52] <meetingology`> ojap: Error: "hggdh" is not a valid command.
[21:52] <hggdh> hi ojap
[21:54] <ojap> :hggdh hello, just trying to work out how to send a direct message
[21:54] <intrader> yofel, by the way how do I upgrade from beta to RC?
[21:55] <yofel> ojap: '/msg hggdh ...' for a private message, if you're searching from there
[21:55] <skeeby> intrade, do u get artifacting when viewing images in webpages as part of your slow performance?
[21:55] <yofel> intrader: if you have installed all updates you're already running the beta
[21:56] <skeeby> maybe artifacting isnt the word im looking for, "image scroll lag" maybe?
[21:56] <yofel> beta and rc are nothing more than daily snapshots with milestone names
[21:56] <yofel> *already running the rc
[21:56] <intrader> skeeby, on 10.04 yes (slight jittering - and the 'encouragement' to drag event when mouse is not down)
[21:57] <skeeby> i was noticing this problem when i updated to 10.10 and had to disable my visual effects, but as an overall performance decrease i cant really say
[21:57] <skeeby> i havent ran anything previous to 10.04
[21:58] <intrader> yofel, 10.10 has not informed me of any updates - the version I running is beta - there is a RC available
[21:59] <skeeby> if theres no updates for the beta
[21:59] <intrader> skeeby, misleading title on duplicate of 631130 - maverick is much better compared to 10.04 - no problems except bug 652283
[21:59] <ubot2> intrader: Bug 652283 on http://launchpad.net/bugs/652283 is private
[21:59] <skeeby> then u have the current RC as far as i know, thats how i understand it
[21:59] <yofel> intrader: you're running today's maverick with all updates? then that's the RC
[21:59] <skeeby> ill have to wait till that one gets looked over to check out that bug
[22:00] <intrader> yofel, I have not noticed any updates since a couple of days ago - so I assume I am running 10.10 beta
[22:00] <yofel> people always think the milestones are something exceptional, but they're only names for the maverick archive on the specific date, so iso testing and stuff can be handled easier
[22:01] <intrader> yofel, should I run `sudo apt-get upgrade`?
[22:02] <yofel> intrader: if you want to make sure, run 'sudo apt-get update; sudo apt-get dist-upgrade'
[22:03] <skeeby> intrader, lol u broke your mouse
[22:03] <intrader> yofel, I will do that now. It should not hurt. Except it may take time
[22:04] <intrader> skeeby, I still have it running around the room!
[22:04] <skeeby> rofl
[22:06] <intrader> skeeby, what is rofl - I am a newbie to these terms
[22:06] <yofel> rolling on the floor laughing
[22:06] <intrader> yofel, skeeby: rofl
[22:07] <intrader> yofel, update of eclipse taking its time!
[22:08] <yofel> I can imaging that
[22:10] <intrader> yofel, it is still light out here!
[22:10] <skeeby> can someone take a look at bug 651782 for me? im attempting to find relevant log data to post, but im not really sure what sort of errors i am looking for
[22:10] <ubot2> Launchpad bug 651782 in friendly-recovery (Ubuntu) "booting into recovery mode and selecting resume normal boot brings you to a text login (affects: 2) (heat: 12)" [Medium,Confirmed] https://launchpad.net/bugs/651782
[22:24] <intrader> yofel, still busy, but I found a way to bring up bug - https://bugs.launchpad.net/ubuntu/+bug/652283
[22:24] <ubot2> intrader: Error: Bug #652283 is private.
[22:32] <intrader> I have reported bug 652470 which has the working of bug 652283, but is not classified as private.
[22:32] <ubot2> Launchpad bug 652470 in nautilus (Ubuntu) "Shell scripts require execute permission to execute (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/652470
[22:32] <ubot2> intrader: Bug 652283 on http://launchpad.net/bugs/652283 is private
[22:32] <intrader> yofel, all updated
[22:36] <skeeby> ive been reading the wiki and came across https://wiki.ubuntu.com/DebuggingProcedures, but i dont see much that would help debugging the recovery mode problems described. any feedback is appreciated
[22:40] <skeeby> intrader, in your new bug you mention that you dont have to check the "executable" option for .exe files. is that correct?
[22:40] <mrand> skeeby: I believe every bootup (not just recovery mode) results in a text login - it's just that when a graphical window manager is enabled, it switches to that at some point.  Have you already verified the linux bootline is correct for recovery mode (compare it against non-recovery mode)?
[22:44] <skeeby> well this bug is an actual regression.  persia was helping me with it last night.
[22:44] <kklimonda> skeeby: you can't open .exe files by double clicking them by default - even if they have +x bit set
[22:45] <kklimonda> intrader: skeeby: also, as I've mentioned yesterday the change mentioned in 652470 has most likely be done by the upstream
[22:46] <kklimonda> and, as it' fits our Security Policy, the chance to change that on our own is pretty slim.
[22:47] <kklimonda> (when I right-click on .exe I get "open with archive manager" and today has been the first time I've tried that so it;s probably the default behaviour)
[22:49] <hggdh> intrader: do you have wine installed?
[22:50] <kklimonda> (for the reference check https://wiki.ubuntu.com/SecurityTeam/Policies#Execute-Permission%20Bit%20Required)
[22:51] <hggdh> kklimonda: it is expected -- .bat, .exe, etc are worked on by wine
[22:51] <skeeby> mrand, the bug is actually a regression beginning with 10.04.  unless the functionality was purposefully removed for some reason (which i do not know), GDM should still be able to start
[22:51] <hggdh> if you have wine, double-clicking should work
[22:51] <kklimonda> hggdh: they are applications, just as any othe rapplications they should follow the policy
[22:52] <kklimonda> hggdh: a malicious wine application can do as much a damage as a native one
[22:52] <skeeby> mrand, i was working with persia on this last night, reproduced it myself before i confirmed it. i havent been able to work with kompute yet though, just tryin to get mroe info on it
[22:52] <kklimonda> hggdh: by default wine prefix has a z: drive symlinked to /
[22:52] <mrand> skeeby: yeah, I saw.  Just trying to give you some ideas on where to look.
[22:53] <skeeby> mrand, what are u refering to when u say the bootline?
[22:53] <kklimonda> hggdh: also /usr/bin/cautious-launcher has been made for wine explicitly :)
[22:53] <skeeby> im not familiar with that, or im having a brainfart
[22:54] <kklimonda> (it checks if .exe has a +x bit set and refuses to launch it otherwise)
[22:55] <mrand> skeeby: I guess it is more properly "boot option configuration line", according to this: https://help.ubuntu.com/community/BootOptions
[22:55] <hggdh> kklimonda: yes
[22:56] <hggdh> skeeby: I have the same behaviour, just never bothered about it. It is a bug, indeed
[22:56] <hggdh> please open (right now) against linux, this will collect all necessary data
[22:58] <skeeby> mrand, so youre say it may be a problem with the default boot options for recovery mode?
[22:59] <mrand> skeeby: yep.  I'm saying I would check there first, since I believe that may be one control point for that behavior.
[23:00] <BUGabundo> evening everyone
[23:00] <kees> 21:44 < kklimonda> skeeby: you can't open .exe files by double clicking them by default - even if they have +x bit set
[23:00] <kees> ^^ that's not true.
[23:00] <kees> you can only double-click IF they have +x
[23:01] <kees> (only yeah, you need wine installed)
[23:01] <skeeby> mrand, /boot/grub/menu.lst , so would u suggest making that an attachment for the bug?
[23:01] <kklimonda> kees: hmm, so I have something broken :)
[23:01] <skeeby> yeah mine dont open by default either
[23:01] <skeeby> unless i check the executable part
[23:02] <kklimonda> well, it doesn't work for me anyway
[23:02] <kklimonda> which is weird - I haven't had wine installed till now
[23:03] <kklimonda> interesting - I have this in /usr/share/applications/mimeinfo.cache:
[23:03] <kklimonda> application/x-ms-dos-executable=file-roller.desktop;wine.desktop;
[23:03] <mrand> skeeby: I don't know if you need to blindly attach it... I'm guessing it is the same as other users if this problem is reproducible.  if you have time, I was suggesting studying the options to see if that is perhaps the cause.
[23:04] <kklimonda> and file-roller does associate itself with application/x-ms-dos-executable mimetype..
[23:04] <skeeby> ok im not too familiar with those options myself
[23:05] <hggdh> skeeby: did you change your Grub2 configuration? If not, don't worry about it
[23:05] <skeeby> and i cant even copy a backup for it for some reason... trying to copy it to a backup file produces "cannot stat /boot/grub/menu.lst"
[23:05] <skeeby> no i havent messed with it
[23:05] <hggdh> skeeby: what version of Ubuntu?
[23:05] <skeeby> its the default config, an dim in 10.10
[23:06] <hggdh> skeeby: OK. I have the same thing (as I said earlier)
[23:07] <hggdh> so, right now, (1) boot into recoevery mode; (2) exit recovery mode -- you should eventually get either the GDM screen or a login prompt;
[23:08] <hggdh> (3) if GDM, no problems, done; (4) if console login, login as you, and then 'sudo start gdm' <- this will give you GDM;
[23:08] <hggdh> (5) on a terminal (under GDM) run 'ubuntu-bug linux'
[23:09] <hggdh> and open the bug. I doubt this is a linux issue, but it will collect all possible data
[23:09] <skeeby> is that gonna creat a new bug report?
[23:09] <hggdh> skeeby: yes
[23:10] <skeeby> is there a way to just append the info to the current, or will i have to mark it as a dupe
[23:10] <mrand> according to that bootoptions page, "-s or s or single" diables gdm
[23:10] <hggdh> if you already have one, then run on a terminal 'ubuntu-bug xxxxx' where xxxxx is your bug number
[23:10] <hggdh> skeeby: but you MUST have booted in recovery mode
[23:10] <skeeby> kk, do i need to be the reporter of the parent bug to do that?
[23:10] <hggdh> skeeby: what parent bug?
[23:11] <skeeby> bug 651782
[23:11] <ubot2> Launchpad bug 651782 in friendly-recovery (Ubuntu) "booting into recovery mode and selecting resume normal boot brings you to a text login (affects: 2) (heat: 12)" [Medium,Confirmed] https://launchpad.net/bugs/651782
[23:11] <skeeby> i want to add the data that this is going to collect to that report
[23:12] <hggdh> skeeby: the bug is already confirmed, why do you want more data there?
[23:12] <skeeby> to determine the cause
[23:13] <skeeby> i mean, determining the cause is the next step right? lol
[23:14] <hggdh> skeeby: indeed. But collecting data will not help it any -- unless *you* are working to find out what it is
[23:14] <skeeby> well *trying* to
[23:15] <hggdh> we know how to reproduce -- and (at least for me) it is very easy: boot in recovery mode, exit recovery mode
[23:15] <skeeby> pretty new to debugging linux though
[23:15] <skeeby> yup
[23:15] <hggdh> skeeby: so, it is possible init is not running gdm when exiting recovery
[23:16] <hggdh> or an init state is not set
[23:16] <skeeby> trying to set init state manually does not work either
[23:16] <hggdh> one chance is to boot setting init to debug, and -- then, I agree -- saving the data
[23:17] <hggdh> but saving data now will not help much, a developer can easily reproduce it
[23:17] <skeeby> oh ok i get what you are saying
[23:17] <skeeby> so if its easily reproduced like that no additional info is needed?
[23:18] <hggdh> right now, no additional info. There *might* be a need for more data later, after someone starts working on it; but then the request will be much more directed
[23:19] <hggdh> skeeby: even more, the bug is already Confirmed
[23:19] <skeeby> yeah
[23:19] <skeeby> so pretty much someone from bug control just needs to mark as triage and send it away?
[23:22] <hggdh> yes, but there is no need here -- friendly-recovery is a package created by us
[23:22] <hggdh> (which is to say, upstream is Ubuntu)
[23:23] <skeeby> ah ok
[23:27] <skeeby> hggdh, thanks for goin over this with me
[23:27] <hggdh> skeeby: you are welcome. Thank YOU for helping
[23:27] <skeeby> just doin my best to make sure my contributions dont make things worse =p
[23:43] <persia> hggdh, Just in case the background was missing: skeeby is the person who confirmed 651782 and was digging towards triage at my suggestion (although, yes, it's hard)
[23:43] <hggdh> persia: oh. I did not know
[23:44] <hggdh> persia: I think a good start would be to set 'init=/sbin/init --debug' on grub, and boot to recovery
[23:44] <persia> skeeby, ^^