apport-retrace sandbox can not be used with https mirrors in sources.list

Fix for https mirros in sources.list, tested successfully

The attached patch makes stacktraces a lot more informative in my case, tested with

apport-retrace -v -s -R -S system _usr_bin_texstudio.1000.crash

Without the patch I get:

--- stack trace ---
#0 0x00007fa95a8273eb in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
--- source code stack trace ---
#0 0x00007fa95a8273eb in ?? ()
#1 0x0000000000000000 in ?? ()

which is completely useless.

With the patch applied I get

--- stack trace ---
#0 0x00007fa95a8273eb in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1 0x00007fa95a806899 in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2 0x00007fa95adc5aaf in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1907
No locals.
#3 QMessageLogger::fatal (this=this@entry=0x7ffc551f5df0, msg=msg@entry=0x7fa95bc45d17 "%s") at global/qlogging.cpp:888
        message = <optimized out>
        ap = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7ffc551f5cf0, reg_save_area = 0x7ffc551f5c30}}
#4 0x00007fa95b8607c7 in init_platform (argv=<optimized out>, argc=@0x7ffc551f602c: 1, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208
        fatalMessage = {static null = {<No data fields>}, d = 0x565091eea860}
        plugins = {<QList<QString>> = {<QListSpecialMethods<QString>> = {<No data fields>}, {p = {static shared_null = {ref = {atomic = {_q_value = {<std::__atomic_base<int>> = {static _S_alignment = 4, _M_i = -1}, static is_always_lock_free = true}}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x565091ee9840}, d = 0x565091ee9840}}, <No data fields>}
        platformArguments = {<QList<QString>> = {<QListSpecialMethods<QString>> = {<No data fields>}, {p = {static shared_null = {ref = {atomic = {_q_value = {<std::__atomic_base<int>> = {static _S_alignment = 4, _M_i = -1}, static is_always_lock_free = true}}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x7fa95b0a8780 <QListData::shared_null>}, d = 0x7fa95b0a8780 <QListData::shared_null>}}, <No data fields>}
        availablePlugins = {<QList<QString>> = {<QListSpecialMethods<QString>> = {<No data fields>}, {p = {static shared_null = {ref = {atomic = {_q_value = {<std::__atomic_base<int>> = {static _S_alignment = 4, _M_i = -1}, static is_always_lock_free = true}}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x565091eeace0}, d = 0x565091eeace0}}, <No data fields>}
        themeNames = {<QList<QString>> = {<QListSpecialMethods<QString>> = {<No data fields>}, {p = {static shared_null = {ref = {atomic = {_q_value = {<std::__atomic_base<int>> = {static _S_alignment = 4, _M_i = -1}, static is_always_lock_free = true}}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x565091eea860}, d = 0x565091eea860}}, <No data fields>}
        plugins = <optimized out>
        platformArguments = <optimized out>
        availablePlugins = <optimized out>
        themeNames = <optimized out>
        pluginArgument = <optimized out>
        __for_range = <optimized out>
        __for_begin = <optimiz...

This is the crash file from comment #2.

Note that in the end the source code stack trace contained many errors such as "Error: qlogging.cpp was not found in source tree".

Also note that there are a lot "No symbol table info available." for files such as /lib/x86_64-linux-gnu/libc.so.6, lib/x86_64-linux-gnu/libglib-2.0.so.0, etc. so it seems everything located in /lib does not get debug symbols in the sandbox.

Thanks for using apport and finding / digging into these issues. I'd appreciate it if there were separate bugs for each issue that you've found so we can better track the fixing of them.

While your https patch looks good and makes sense I'm puzzled that I am not able to recreate the issue you are experiencing. As I understand it you are running 20.04, what version of apport are you using?

Lets go ahead and use this bug for the https issue.

Brian, if you use this issue for the https issue, why is it marked incomplete then?
But I guess the https issue does not need further discussion, could you just ship the patch?

I am using the latest version of apport in the focal repos. Did you try to retrace my texstudio crash and obtained a full backtrace?

I used your sources.list file and your texstudio crash and did not receive the "cannot determine default mirror" error message. Although I haven't been able to recreate the error which you received I'll go ahead and add the patch anyway.

The attachment "fix-https.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

@Brian: Thanks for merging the patch. As for reproducing the https issue: The issue happens if ALL entries in fstab are https mirrors, like

deb https://mirror.init7.net/ubuntu/ focal main restricted universe multiverse
deb-src https://mirror.init7.net/ubuntu/ focal main restricted universe multiverse

deb https://mirror.init7.net/ubuntu/ focal-updates main restricted universe multiverse
deb-src https://mirror.init7.net/ubuntu/ focal-updates main restricted universe multiverse

deb https://mirror.init7.net/ubuntu/ focal-backports main restricted universe multiverse
deb-src https://mirror.init7.net/ubuntu/ focal-backports main restricted universe multiverse

deb https://mirror.init7.net/ubuntu/ focal-security main restricted universe multiverse
deb-src https://mirror.init7.net/ubuntu/ focal-security main restricted universe multiverse

The you will be 100% able to reproduce the error.

As for the other issues
1. Did you try to retrace my texstudio crash on focal machine in sandbox mode?
2. Did you obtain a backtrace without missing symboles?

As I mentioned in comment #2 just retracing the crash file with
apport-retrace -v -s -R -S system _usr_bin_texstudio.1000.crash gives me the following useless stack trace:

--- stack trace ---
#0 0x00007fa95a8273eb in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
--- source code stack trace ---
#0 0x00007fa95a8273eb in ?? ()
#1 0x0000000000000000 in ?? ()

@Brian: I will open a separate bug for comment #9 soon, as this issue here is about the https issue.

Since you asked to reproduce please fully upgrade your focal installation and use the files as found in the attached tar archive.

Command to reproduce is:

apport-retrace -v -s -R -S system _usr_bin_gnome-shell.1000.crash

This bug was fixed in the package apport - 2.20.11-0ubuntu21

---------------
apport (2.20.11-0ubuntu21) focal; urgency=medium

  [ Brian Murray ]
  * backends/packaging-apt-dpkg.py: allow mirrors which are accessed via https
    in sources.list. Thanks to Launchpad user Esokrates for the fix.
    (LP: #1866996)
  * backends/packaging-apt-dpkg.py: when downloading packages from Launchpad
    do not require them to be authenticated.
  * test/test_backend_apt_dpkg.py: Fix check for connectivity and modify
    install from PPA test for a change in the PPA being tested.

  [ Matthieu Clemenceau ]
  * test/test_ui.py: Removed linux package version to fix autopkgtest with
    focal. Changed linux-5.4 and linux-signed-5.4 to linux and linux-signed

 -- Brian Murray <email address hidden> Thu, 12 Mar 2020 15:46:30 -0700