"find-dbgsym-packages /usr/bin/gio" command outputs errors

Bug #2009526 reported by Stephen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debian-goodies (Ubuntu)
New
Undecided
Unassigned

Bug Description

I am not sure if this problem is caused by my not doing this right, a bug in gdb, a bug in gio, or a fault in the source libraries server. But after four days no one has an answer to this problem at my thread at: https://stackoverflow.com/questions/75620624/find-dbgsym-packages-usr-bin-gio-command-gets-errors . No one at the #ubuntu IRC channel responded. And so my strong suspicion this is actually a bug.

The goal is the ability to step through gio's source code to follow its execution to find out why it is not working for me in my main account (account ID 1000), but does work in other accounts created susequently for testing. To get symbols, and source code, I followed the directions at:

https://wiki.ubuntu.com/Debug%20Symbol%20Packages

duginfod did not work on my Ubuntu 22.04 system. It was therefore necessary to do a manual download. I followed the directions under the heading "Getting -dbgsym.ddeb packages", and then "Automatic Resolution / Installation of necessary packages", on that page. All went well until the find-dbgsym-packages command. Here is the complete command, and the response I got:

stephen@stephen:~$ find-dbgsym-packages /usr/bin/gio
dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libgmodule-2.0.so.0
W: Cannot find debug package for /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (991a9f61e69c30ef8ab73761c300ae51249ede63)
dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libglib-2.0.so.0
W: Cannot find debug package for /lib/x86_64-linux-gnu/libglib-2.0.so.0 (137458a0f7846a084270bf5bb03df075a578db6d)
dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libgobject-2.0.so.0
W: Cannot find debug package for /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (44f60e584780daaeb1880ead5dd00f12ffd423d2)
dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libgio-2.0.so.0
W: Cannot find debug package for /lib/x86_64-linux-gnu/libgio-2.0.so.0 (9b52271b63917542ba10ffb8a82b97befd2c238f)
dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libpcre2-8.so.0
W: Cannot find debug package for /lib/x86_64-linux-gnu/libpcre2-8.so.0 (184a841c55fb7fe5e3873fcda8368c71016cd54c)
libblkid1-dbgsym libffi8-dbgsym libglib2.0-bin-dbgsym libmount1-dbgsym libpcre3-dbg libselinux1-dbgsym zlib1g-dbgsym

I interpret these errors to mean that the packages the find-dbgsym-packages command is seeking are not found, I think now, due to a bug somewhere.
For the details regarding my need to step through code see this thread of mine:
https://askubuntu.com/questions/1427431/how-to-set-a-launcher-as-trusted

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2009526/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Stephen (artist-wavenet) wrote :

The package name was looked up with this command sequence:

stephen@stephen:~$ which gio
/usr/bin/gio
stephen@stephen:~$ dpkg -S /usr/bin/gio
libglib2.0-bin: /usr/bin/gio
stephen@stephen:~$

affects: ubuntu → glib2.0 (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

unsure what find-dbgsym-packages is doing but seems an issue with it so reassigning there

affects: glib2.0 (Ubuntu) → debian-goodies (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.