How should I correctly help developers with bug-reporting on development version?

Quality
1

I wonder why the contents of /etc/apport/crashdb.conf are changed to the values which make very difficult to report bugs interactively?
Usually user feedback may help to reproduce for example crashes.
On the 21.04 daily system you provide the following:

# map crash database names to CrashDatabase implementations and URLs

default = 'ubuntu'

def get_oem_project():
    '''Determine OEM project name from Distribution Channel Descriptor

    Return None if it cannot be determined or does not exist.
    '''
    try:
        dcd = open('/var/lib/ubuntu_dist_channel').read()
        if dcd.startswith('canonical-oem-'):
            return dcd.split('-')[2]
    except IOError:
        return None

databases = {
    'ubuntu': {
        'impl': 'launchpad',
        'bug_pattern_url': 'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
        'dupdb_url': 'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
        'distro': 'ubuntu',
        'escalation_tag': 'bugpattern-needed',
        'escalated_tag': 'bugpattern-written',
    },
    'canonical-oem': {
        'impl': 'launchpad',
        'bug_pattern_url': 'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
        'project': get_oem_project(),
    },
    'debug': {
        # for debugging
        'impl': 'memory',
        'bug_pattern_url': '/tmp/bugpatterns.xml',
        'distro': 'debug'
    },
}

The following values are missed (in context):

databases = {
    'ubuntu': {
         'problem_types': ['Bug', 'Package', 'Crash']
    }
}

Do you really need user feedback during development of 21.04?

Currently I see some *.crash files in /var/crash on 21.04 daily system, but Apport does not pop-up to ask me about bug-reporting and to open Firefox window for the actual bug-reporting.
Here is what I have:

$ head -n1 /etc/apt/sources.list
#deb cdrom:[Ubuntu-MATE 21.04 _Hirsute Hippo_ - Alpha amd64 (20210321)]/ hirsute main multiverse restricted universe

$ ls /var/crash/ -1
_usr_bin_marco.1000.crash
_usr_libexec_ayatana-indicator-keyboard_ayatana-indicator-keyboard-service.1000.crash
_usr_libexec_ayatana-indicator-keyboard_ayatana-indicator-keyboard-service.115.crash

Also I do not see *.upload and/or *.uploaded files in the above folder.
For marco I do not see any recent bug on https://bugs.launchpad.net/ubuntu/+source/marco/+bugs?orderby=-id&start=0 .

So I reported the bug manually:

$ apport-bug /var/crash/_usr_bin_marco.1000.crash 
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in _run_hook
    symb['add_info'](report, ui)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info
    apport.hookutils.attach_casper_md5check(report,
  File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in attach_casper_md5check
    with open(location) as json_file:
PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json'

Not user-friendly either. As the result this gave me the another private bug-report https://pad.lv/1920798 which surprisingly contains Segfault happened with reason - unknown VMA.

Am I misunderstood something here about bug-reporting procedures?

1 Like