Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

First thing in the morning I started Ubuntu, and the Chrome browser. In the browser I visited a page with a password-field on it. So the password-ring popped up. Then a dialog popped up asking for a password in order to send a bug report about the system. Then the ususal bug-report dialog showed up. (Something about Gud & color)

I am not sure about the exact order of dialogs.

Is the extra question for a password for a bug report normal behaviour?

share|improve this question
    
Here is a previous post that talks about this: askubuntu.com/questions/47675/why-should-i-trust-this –  jpetersen Jun 13 '12 at 5:40
    
@JPbuntu so this Q is a duplicate of that one. –  Ashu Jun 13 '12 at 6:46
    
@Ashu That question is asking if it's safe to assume the password dialog for reporting bugs in system processes is genuine. This question is about whether or not it's normal behavior to see one, and this question is not asked specifically about bugs in system processes. (You'll see that my answer to this question is a good fit here but would be a totally inappropriate answer for that question.) For these reasons, I don't think this question should be considered a duplicate of that one. –  Eliah Kagan Jun 13 '12 at 6:50
    
@EliahKagan yeah ur right. srry. –  Ashu Jun 13 '12 at 6:52
    
@Ashu No apology is necessary! Sometimes it's a close call, if something is a duplicate. And reasonable people might disagree with my belief that this question isn't a duplicate of that one. (Where it's unclear, this is the sort of thing that can be asked about on meta.) –  Eliah Kagan Jun 13 '12 at 6:54
add comment

2 Answers

Sometimes, but not usually.

Reporting Crashes in System Processes

Most of the time when an application crashes or you report a bug manually, you don't have to put in a password for information to be automatically gathered and sent to Launchpad.

However, when a program or service that runs as root crashes, collecting data about that crash requires accessing data that is only accessible as root. In Ubuntu, you can perform actions as root by authenticating with your password, provided that your account has administrative capabilities. (This is facilitated by sudo or one of its graphical frontends, or by PolicyKit.) If your account does not have administrative capabilities, then you will not be prompted to report a crash in a root-owned process until you log in with an account that has administrative capabilities.

When you're logged in as an administrator and you're prompted to report a crash in a root-owned process, you see a password dialog like this:

"Please enter your password to access problem reports of system programs"

This is one of the two situations where you may have to enter a password to report a bug in Ubuntu.

Once you've authenticated, then the crash-reporting process continues the same way as for regular non-root processes.

Filing Bug Reports for Crashes

Before Ubuntu 12.04 LTS, when Apport crash reporting was enabled, you would be asked to submit a bug report to contain the data gathered automatically. This is still what happens in alpha and beta versions of Ubuntu (and versions before 12.04 LTS). But starting with Ubuntu 12.04 LTS, Apport is set up by default so that, if you are running a stable version of Ubuntu and a crash occurs, it will automatically (with your permission) submit the information to a database that doesn't require you to fill out a bug report. This is potentially less useful than having a bug report, but it means that information can effectively be gathered from many more users--plus, bug reports are often most valuable for alpha and beta releases where the bugs are more likely to be fixed as a result of the report.

However, if you re-enable bug filing for crashes, or you report a bug by invoking ubuntu-bug manually with a package name or process ID, then you will be given the opportunity to file a bug report. Bug reports in Ubuntu are filed on Launchpad. So once data for the bug are collected and submitted to Launchpad, a Launchpad page to file the bug report with those data automatically attached will appear in a web browser. (Unless your default web browser doesn't work and that's what the bug is about, of course.)

If you're not logged in to Launchpad, then you'll be brought to the Launchpad sign-in page in your web browser, to report the bug. This is the second of the two situations where you may have to enter a password, to report a bug in Ubuntu.

Screenshot showing the Launchpad sign-in page

share|improve this answer
    
+1 Great answer! –  Ashu Jun 13 '12 at 6:53
add comment

(cannot contribute as a comment, as don't have enough rep...)

My problem was solved by comment #2 here: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1033295

In summary: sudo gksu-properties
change su --> sudo

Edit: below this line was my original "comment," which did not work
=========
I personally can't get past this dialogue, as my user password appears to not be accepted (despite having "all" sudoers permissions) and there is no root user to enter the password of. However, I noticed that the "offending" entry in /var/crash was (with permissions)
drwxrwsrwt 2 root whoopsie 4096 Apr 15 16:47 .
-rw-r----- 1 root whoopsie 8906061 Apr 13 17:33 _usr_lib_virtualbox_VirtualBox.0.crash

So, the root user, which doesn't exist as a login user, owns the file, with whoopsie as the only valid group with read permissions. However, whoopsie has no users (other than whoopsie itself).

So, I've done a sudo usermod -a -G whoopsie myloginname, which presumably should allow me to access this report, as I am now in the whoopsie group.

(note sudo nautilus /var/crash also allows me to access the reports, but hopefully this will allow me to access the reports as part of the apport behavior)

share|improve this answer
    
Welcome to Askubuntu! Thank you for your post. However, to say that another solution works is not really an answer. –  Jacob Vlijm 6 hours ago
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.