[00:16] <hggdh> epikvision: I have heard of an issue on today's image, that should be resolved tomorrow
[00:17] <hggdh> end result is what you described, so it is probably the same issue (some kernel settings/images have to be updated on the ISO)
=== rsalveti` is now known as rsalveti
=== zyga is now known as zyga-afk
=== zyga-afk is now known as zyga
=== io-non-esisto is now known as mapreri
=== LordOfTime is now known as Guest62140
=== zyga is now known as zyga-food
=== Ursinha` is now known as Ursinha
[15:24] <njin> can someone set bug 1023932 to critical (loss of data) for me ? (screencast attached)
[15:24] <ubot2> Launchpad bug 1023932 in simple-scan "Simple Scan overwrite already saved files without advice (dup-of: 842076)" [Undecided,New] https://launchpad.net/bugs/1023932
[15:24] <ubot2> Launchpad bug 842076 in simple-scan "Save button doesn't warn before overwriting existing file" [Medium,Triaged] https://launchpad.net/bugs/842076
[15:25] <micahg> njin: that's an upstream bug that we don't control
[15:25] <njin> ok thanks
=== zyga-food is now known as zyga
=== seb128_ is now known as seb128
[16:50] <LoT> this doesnt look like a bug to me... micahg, what do you think?  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1023978
[16:50] <ubot2> Ubuntu bug 1023978 in firefox "brouser no found site mail.ru" [Undecided,New]
[16:50] <LoT> looks more like a support request and not a bug
=== hggdh changed the topic of #ubuntu-bugs to: Ubuntu Bug Squad | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | New bugs announced on #ubuntu-bugs-announce | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu
[16:53] <LoT> hggdh: what do you think on that bug, support request or not?
[16:53] <hggdh> LoT: looking
[16:54] <hggdh> LoT: certainly. Please close invalid, and redirect to askubuntu or ubuntuforums
[16:54] <LoT> <offtopiccomment> why is it though that when something doesnt load inside of ffox they assume its an ffox bug... i've seen at least a billion similar things like this.
[16:54] <LoT> </offtopiccomment>
[16:54] <LoT> hggdh: i plan to :)
[16:58] <hggdh> LoT: that happens a lot, mostly with casual users: it does not work, it is a bug...
[16:58] <LoT> mhm
[16:59] <LoT> you'd be surprised how on AskUbuntu we've actually got questions saying "How to determine if $issue is a bug?"
[16:59] <LoT> and how often i'm having to resort to the bugsquad docs :P
[16:59] <hggdh> this was one of the reasons we started making it more difficult to open a bug. You can use apport to open a bug, but must know the road to open one manually
[16:59] <hggdh> perhaps it is time for me to be more active on askubuntu as well
[17:06] <LoT> hggdh: hehe, i wrote two canonical bugs questions
[17:06] <LoT> about statuses/lifecycles and about importance
[17:06] <LoT> there's already one about how to file a bug
[17:06] <LoT> and dupes of one about how to identify a bug
[17:07] <LoT> all of them link to the bugsquad docs :P
[17:07] <LoT> SPEAKING OF WHICH
[17:07] <LoT> we need to explicitly define the difference between core and non-core
[17:07] <LoT> i think i started a mini email chain about it a few months ago...
[17:07] <hggdh> ah
[17:07] <LoT> but it never went anywhere
[17:08] <hggdh> this is a good question: core as related to Ubuntu itself? Then we should have such a list;
[17:08] <LoT> because if you look at https://wiki.ubuntu.com/Bugs/Importance you'll see core and non-core mentioned
[17:08] <LoT> but no list of what is considered core
[17:08]  * LoT therefore bases bug importances off of other criterion
[17:08] <hggdh> now, by the user's perspective, there is also "core" -- whatever the user needs at this moment. So yes, we need to show what is what
[17:08] <LoT> agreed
[17:09] <LoT> first things first, are we defining core as what the core devs work on
[17:09] <LoT> secondly, if not, are we considering anything that ubuntu-desktop links to as core
[17:09] <LoT> thirdly, if not the 2nd one, what *is* core?
[17:10]  * LoT sees recommendations sometimes to get things marked for medium that dont count because of non-core vs. core
[17:10] <hggdh> I think we could for a start. But I am pretty sure we will have disagreements, so it is probably better to fire off an email to ubuntu-devel
[17:10] <hggdh> oops
[17:10] <hggdh> now that is a different issue
[17:10] <hggdh> importance is relative to the package itself
[17:10] <LoT> hggdh: true, *BUT*
[17:11] <LoT> .Medium: Most bugs are of medium importance, examples are:
[17:11] <LoT> .A bug that has a moderate impact on a core application. .A bug that has a severe impact on a non-core application.
[17:11] <LoT> how do you define core and noncore in this instance?
[17:11] <LoT> as a moderate impact on non-core is Low
[17:11] <LoT> according to the docs
[17:11] <LoT> same page, under "low": .Bugs that have a moderate impact on a non-core application
[17:11] <hggdh> humph
[17:11] <hggdh> yeah, we really have to review this
[17:12] <LoT> 95% of what I see and act on is in nginx, and is usually low
[17:12] <LoT> or notABug
[17:12] <LoT> but we really need to define the core vs. noncore
[17:13] <hggdh> I agree
[17:13] <LoT> <offtopic> LOL someone made a playlist called "The Evil", and it contains my epic music xD </offtopic>
[17:13]  * hggdh got called in to get a hack done fast
=== zyga is now known as zyga-afk
[18:49] <LoT> how do we handle "freeze" bugs again?  like these https://bugs.launchpad.net/ubuntu/+bug/1023995
[18:49] <ubot2> Ubuntu bug 1023995 in ubuntu "ubuntu 12.04 freezes up very frequently" [Undecided,New]
[19:49] <LoT> hggdh: still around?