gnome-software updated gcc today, and now whenever I start gdb I get nasty warnings: warning: the debug information found in "/usr/lib/debug//lib64/libstdc++.so.6.0.19.debug" does not match "/lib64/libstdc++.so.6" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib64/libstdc++.so.6.0.19.debug" does not match "/lib64/libstdc++.so.6" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libstdc++.so.6.0.19.debug" does not match "/lib64/libstdc++.so.6" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib64//libstdc++.so.6.0.19.debug" does not match "/lib64/libstdc++.so.6" (CRC mismatch). But it can happen any time PackageKit updates a package you have debug info installed for. I think this is because Fedora's debug repos are not enabled by default, even if you install debug info using debuginfo-install, and a yum plugin handles updating it only if you use the command line for updates. This occurred in Fedora 20 with the yum backend, but I really only care that this gets fixed in the hif backend (if it hasn't been already, but I suspect not).
I think the proper thing to do would be to just enable the debuginfo repo, rather than rely on plugins to do semi-random auto-enabling of the repos.
(In reply to comment #1) > I think the proper thing to do would be to just enable the debuginfo repo, > rather than rely on plugins to do semi-random auto-enabling of the repos. Probably, but where do we file a bug for this? [1] http://yum.baseurl.org/wiki/YumUtils/DebugInfoInstall
We moved the upstream bugtracker to GitHub a long time ago. If this issue still affects you please re-create the issue here: https://github.com/hughsie/PackageKit/issues Sorry for the impersonal message, and fingers crossed your issue no longer happens. Thanks.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.