gmane.linux.ubuntu.bugsquad

[Ubuntu Wiki] Update of "Chromium/Debugging" by uusijani

Ubuntu Wiki — 2012-05-21T16:01:58

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "Chromium/Debugging" page has been changed by uusijani:
http://wiki.ubuntu.com/Chromium/Debugging?action=diff&rev1=9&rev2=10

Comment:
restructuring, language

  ## page was renamed from Chromium/Debug
+ If Chromium crashes and you want to file a bug upstream, use their [[http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux|linux template]]. Always include the output from the following command:
- When you want to file a bug, it should be filed '''upstream''' using this '''[[http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux|linux template]]'''.
- Please always include the result of the following command:
- {{{
- dpkg -l | grep chromium-}}}
- 
- = Debugging Chromium crashes =
- 
- If chromium crashes and if you want to file a '''[[http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux|bug upstream]]''', you need to provide a pr

[Ubuntu Wiki] Update of "Chromium/Debugging" by uusijani

Ubuntu Wiki — 2012-05-21T16:02:45

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "Chromium/Debugging" page has been changed by uusijani:
http://wiki.ubuntu.com/Chromium/Debugging?action=diff&rev1=10&rev2=11

Comment:
typo: just +like any

  You'll need to provide a [[https://wiki.ubuntu.com/Backtrace|backtrace]]. It can be produced using gdb, with the help of debugging symbols.
  
  == Getting a backtrace ==
- Debugging symbols come in packages that can be [[InstallingSoftware|installed just any other software package]] in Ubuntu. The debugging symbols package for Chromium is called ''chromium-browser-dbg''. Once you've installed it, open a terminal and proceed as follows:
+ Debugging symbols come in packages that can be [[InstallingSoftware|installed just like any other software package]] in Ubuntu. The debugging symbols package for Chromium is called ''chromium-browser-dbg''. Once you've installed it, open a terminal and proceed as follows:
  
  {{{
  $ chromium-browser -

Re: [Ubuntu Wiki] Update of "Bugs/Responses" by veger

Tom Hill — 2012-05-21T16:34:45

True, but adding the meaning next to it would teach them the meaning.

On 21 May 2012, at 15:53, Brian Murray <brian-GeWIH/nMZzLQT0dZR+AlfA< at >public.gmane.org> wrote:

Re: [Ubuntu Wiki] Update of "Bugs/Responses" by veger

Brian Murray — 2012-05-21T14:53:22

Not everybody may know what EOL stands for, perhaps putting the words in
it or avoiding the acronym at all would be more informative.

--
Brian Murray
Ubuntu Bug Master

Re: apport: removing passwords from "modified.conffile..."

Nigel Babu — 2012-05-20T16:45:13

Hi Lars,

You could probably look at what I had done for the rhythmbox apport
hook.[1]  Take a look at the mask_values() function.

[1] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/rhythmbox/oneiric/view/head:/debian/source_rhythmbox.py

Regards
Nigel



On Sat, May 19, 2012 at 3:51 PM, Lars Duesing
<lars.duesing-7oc6RrGaw49LT8YB/y1Xvw< at >public.gmane.org> wrote:

Re: Adding a package special log file to apport

Lars Duesing — 2012-05-18T21:01:52

Hi Brian,


Thanks for your offer!
 If you want to have a look at 
https://code.launchpad.net/~lars.duesing/ubuntu/precise/aiccu/aiccu-apport-fix 
I would be pleased!

Lars

[Ubuntu Wiki] Update of "Bugs/Responses" by veger

Ubuntu Wiki — 2012-05-19T08:55:54

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "Bugs/Responses" page has been changed by veger:
http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=349&rev2=350

  
  If the specific release has reached EOL per https://wiki.ubuntu.com/Releases and there is not enough information to work on the bug, then you can set to '''Incomplete''' and use the following response (Note RELEASE and DATE are placeholders):
  
- ||<tablestyle="background-color: #eee">Thank you for reporting this bug to Ubuntu.  RELEASE reached EOL on DATE.<<BR>>Please see this document for currently supported Ubuntu releases:<<BR>>https://wiki.ubuntu.com/Releases <<BR>><<BR>>I've tried recreating this bug with RELEASE and was unable to, given the information you've provided.  Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.<<BR>><<BR>>Please feel free to report any other bugs you may find.||
+ ||<tablestyle="b

apport: removing passwords from "modified.conffile..."

Lars Duesing — 2012-05-19T07:17:35

Hi again,

I have another problem: How to remove passwords from apport-attachments 
which are automagically added?
I have searched for modified_conffile throughout the sources, but cannot 
find anything, except in test-scenarios...
In the file /etc/aiccu.conf and modified.conffile..etc.aiccu.conf.txt 
there are sensitive login-information:
 > username LxxxxxxE
 > password xxxxxxx
maybe even in comments :(

Lars

apport: removing passwords from "modified.conffile..."

Lars Duesing — 2012-05-19T10:21:48

Hi again,

I have another problem: How to remove passwords from apport-attachments 
which are automagically added?
I have searched for modified_conffile throughout the sources, but cannot 
find anything, except in test-scenarios...
In the file /etc/aiccu.conf and modified.conffile..etc.aiccu.conf.txt 
there are sensitive login-information:
 > username LxxxxxxE
 > password xxxxxxx
maybe even in comments :(

Lars

Re: New message for Bug/Responses#Release_has_reached_EOL

Maarten Bezemer — 2012-05-19T08:57:15

Hello,

I have updated the page with this text:


Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases 

I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducable, increase the verbosity of the steps to recreate it so we can try again.

Do feel free to report any other bugs you may find.


Thanks for your input.
Regards,
  Maarten

Re: Adding a package special log file to apport

Brian Murray — 2012-05-18T19:31:05

Well, if the aiccu package generates multiple binary packages then you'd
want to name it source_aiccu.py so the package hook would be run for
every binary package.

There are also lots of examples on most ubuntu systems in
/usr/share/apport/package-hooks.  Additionally, there are some
convenience functions for adding information in hookutils.py like
attach_file_if_exists which was mentioned in the code snippet.

Oh and you initially mentioned you only want this for crashes, so keepng
in mind that package hooks are also run when someone uses 'ubuntu-bug
aiccu', you'd probably want:

        if report['ProblemType'] == 'Crash':
            attach_file_if_exists(...)

Also if you need the changes to package sponsored or SRU'ed (you'd
probably want it in Precise), I am happy to help.

--
Brian Murray

Re: Adding a package special log file to apport

Daniel Manrique — 2012-05-18T19:09:52


Look here for information on how to add package hooks to do stuff like this:

https://wiki.ubuntu.com/Apport/DeveloperHowTo#Package_Hooks

In brief (and don't believe me too much, I've never done it, I'm just reading
the docs and comparing against what a package I know does this has):

- Add a Python script/file/hook to your package (say, aiccu.py) with something
like this:

from apport.hookutils import *

def add_info(report, ui=None):
    attach_file_if_exists(report, '/var/log/aiccu.log', key='aiccuLog')
    report['SecretMessage'] = 'my hook was here'


- Make sure your package installs it in /usr/share/apport/package-hooks/aiccu.py.

- Daniel

[Ubuntu Wiki] Update of "DebuggerTalk_it" by fabiomarconi

Ubuntu Wiki — 2012-05-18T16:22:09

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "DebuggerTalk_it" page has been changed by fabiomarconi:
http://wiki.ubuntu.com/DebuggerTalk_it?action=diff&rev1=1&rev2=2

  
  Nell'arena pratica, io posso mostrare come utilizzare per il debug un progetto GNU automake. Ad esempio, ci potrebbe essere un campo teorico su come strutturare la scrittura di un debugger. (There could be a theoretical area such as how to structure writing a debugger. (Quelli per ruby e Python sono interessanti qui).
  
- In passato, qualcuno mi chieset ''"cosa c'è di affascinante in un debugger?"'' Oppure un'osservazione fatta da un imprenditore fù "''Non ho mai usato un debugger, io '''scrivo''' codice''". As a systems administrator one is often confronted with lots of code that you didn't write. You suspect the code might not even be written all that well, but you are more sure that there isn't much in the way of documentation or comments in the code. And you've

Adding a package special log file to apport

Lars Düsing — 2012-05-18T17:39:58

Hi all,
Is there any way to add a log file to apport on crash of a specific  
package?
I need /var/log/aiccu.log on crash of aiccu...

Thanks,
Lars

[Ubuntu Wiki] Update of "DebuggerTalk_it" by fabiomarconi

Ubuntu Wiki — 2012-05-18T15:40:35

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "DebuggerTalk_it" page has been changed by fabiomarconi:
http://wiki.ubuntu.com/DebuggerTalk_it

Comment:
Italian translation started

New page:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

== Introduzione ==
Praticamente affronteremo una discussione sui debugger che ho scrittto o sui quali ho lavorato [[http://bashdb.sf.net|GNU bash]], [[http://bashdb.sf.net/remake|GNU make]], [[http://bashdb.sf.net/pydb|Python]],e [[http://rubyforge.org/projects/ruby-debug/|Ruby]]. Gli agomenti affrontati andranno dallo storico al pratico.

Nell'arena pratica, io posso mostrare come utilizzare per il debug un progetto GNU automake. Ad esempio, ci potrebbe essere un campo teorico su come strutturare la scrittura di un debugger. (There could be a theoretical area such as how to structure writing a debugger. (Quel

[Community Ubuntu Documentation] Update of "ReportingBugs" by penalvch

Help Ubuntu — 2012-05-18T05:56:03

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification.

The "ReportingBugs" page has been changed by penalvch:
http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=174&rev2=175

Comment:
Added note about how do not apport-collect unless O.R. or asked == Adding Apport Debug Information to an Existing Launchpad Bug ==

  
  == Adding Apport Debug Information to an Existing Launchpad Bug ==
  
- If you have already reported a bug directly via Launchpad, but want to add additional debugging information via ''Apport'' to the bug report, you can do this by running the command `apport-collect bug_number` via "Run Application" or terminal window.
+ If you have already reported a bug directly via Launchpad, but want to add additional debugging information via ''Apport'' to the bug report, you can do this by running the command `apport-collect bug_number` via "Run Application" or terminal window. If you are not the original reporter,

[Ubuntu Wiki] Update of "Bugs/Responses" by fabiomarconi

Ubuntu Wiki — 2012-05-17T10:33:20

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "Bugs/Responses" page has been changed by fabiomarconi:
http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=348&rev2=349

  
  Determining whether a bug report is actually a support request can be quite challenging, but if you decide the bug is a support request you can convert it to such by clicking "Convert to a question" at the top of the bug's web page. This will mark the bug as "Invalid", create a new question in the answer tracker and link it to the bug. In the comment dialog that you receive, post a comment to inform the reporter about your action, and advise them to use the support tracker for any future problems.
  
- ||<tablestyle="background-color: #eee"> Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in th

Re: New message for Bug/Responses#Release_has_reached_EOL

Andrea Corbellini — 2012-05-17T14:44:30

Hi,

On 17/05/12 11:57, Maarten Bezemer wrote:
 > and test or b) increase the verbosity of the steps to recreate
 > it so we can try again.

It looks good to me overall. There's just one thing that should be 
changed: I'd remove the "either" word and rephrase the sentence more or 
less in this way: "Please upgrade to the latest version and re-test. If 
the bug is still reproducible, increase the verbosity ..."

I would also include a link to an help page explaining how to perform 
the upgrade, i.e. https://help.ubuntu.com/community/PreciseUpgrades

Thanks,
Andrea C.

Re: New message for Bug/Responses#Release_has_reached_EOL

Maarten Bezemer — 2012-05-17T14:25:52

I agree with the requirement to update to a non-EOL version, I had been 
wondering about this earlier as well.
It was already in the original text and I did not want to modify it too much. 
How about this:



Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases 

I've tried recreating this bug with RELEASE and was unable to, given the 
information you've provided. Please upgrade, test again and if required 
increase the verbosity or update of the steps to reproduce it so we can try 
again.

Do feel free to report any other bugs you may find.



So it is (more) explicit that the OP should update to a non-EOL version before 
increasing the verbosity of the steps to reproduce.

Regards,
  Maarten

On Thursday 17 May 2012 23:19:52 George Patterson wrote:
given

Re: New message for Bug/Responses#Release_has_reached_EOL

George Patterson — 2012-05-17T13:19:52

I also agree with the idea except that it should be a requirement to
upgrade before re-testing otherwise those triaging will required to
run a now EOL install (even a VM) in order to confirm the steps
required to reproduce the bug and then do the same thing with the
current release to check if it has been fixed or no longer an issue.
The developers and other interested people will also need access to
the older version of the release.

This is assuming that I have read the proposed wording correctly.

Regards


George

On 17 May 2012 22:59, P.L. Francisco Javier <fco.plj-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: New message for Bug/Responses#Release_has_reached_EOL

P.L. Francisco Javier — 2012-05-17T12:59:28

It looks good for me, +1
On May 17, 2012 4:57 AM, "Maarten Bezemer" <maarten.bezemer-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>
wrote: