I did my weekly patches (dnf upgrade), rebooted, and logged in as a regular user. A problem popped-up. The top part of the details is below. I'm not (yet) seeing any other problems. Is this a false alarm? If not, what should I do?
---------------
not-reportable The backtrace does not contain enough meaningful function frames to be reported. It is annoying but it does not necessarily signalize a problem with your computer. ABRT will not allow you to create a report in a bug tracking system but you can contact kernel maintainers via e-mail.
reason traps: fwupd[130814] general protection fault ip:7f6c8fea2122 sp:7fffe5746b60 error:0 in libglib-2.0.so.0.6600.8[7f6c8fe80000+8b000]
backtrace traps: fwupd[130814] general protection fault ip:7f6c8fea2122 sp:7fffe5746b60 error:0 in libglib-2.0.so.0.6600.8[7f6c8fe80000+8b000]
cmdline BOOT_IMAGE=(hd0,msdos3)/vmlinuz-5.11.15-200.fc33.x86_64 root=UUID=45e553d2-fa0c-4eae-95f6-7bf9086ab74c ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=us rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:on modprobe.blacklist=nouveau
package kernel-core-5.11.15-200.fc33
component kernel
hostname coyote
count 1
first occurence 2021-04-22 11:03:20
last occurence 2021-04-22 11:03:20
user unknown user
type/analyzer Kerneloops/abrt-oops
pkg-fingerprint 49FD 7749 9570 FF31
kernel 5.11.15-200.fc33.x86_64
pkg_vendor Fedora Project
runlevel N 5
os_release Fedora release 33 (Thirty Three)
duphash 913d3ca671c62c4a2304f3f1ea8bded67351e0c0
uuid 913d3ca671c62c4a2304f3f1ea8bded67351e0c0
architecture x86_64
abrt_version 2.14.5
data directory /var/spool/abrt/oops-2021-04-22-11:03:20-875-0
在 2021-04-22星期四的 11:25 -0600，home user写道：
I did my weekly patches (dnf upgrade), rebooted, and logged in as a regular user. A problem popped-up. The top part of the details is below. I'm not (yet) seeing any other problems. Is this a false alarm? If not, what should I do?
The error seems like an error seen on fedora 34: https://bugzilla.redhat.com/show_bug.cgi?id=1949491 but since you are on Fedora 33, I don't know if it is related. You may want to report this in bugzilla, along with a traceback.
No need to worry so much, fwupd error won't break important things.
not-reportable The backtrace does not contain enough meaningful function frames to be reported. It is annoying but it does not necessarily signalize a problem with your computer. ABRT will not allow you to create a report in a bug tracking system but you can contact kernel maintainers via e-mail.
reason traps: fwupd[130814] general protection fault ip:7f6c8fea2122 sp:7fffe5746b60 error:0 in libglib-2.0.so.0.6600.8[7f6c8fe80000+8b000]
backtrace traps: fwupd[130814] general protection fault ip:7f6c8fea2122 sp:7fffe5746b60 error:0 in libglib-2.0.so.0.6600.8[7f6c8fe80000+8b000]
cmdline BOOT_IMAGE=(hd0,msdos3)/vmlinuz-5.11.15-200.fc33.x86_64 root=UUID=45e553d2-fa0c-4eae-95f6-7bf9086ab74c ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=us rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:on modprobe.blacklist=nouveau
package kernel-core-5.11.15-200.fc33
component kernel
hostname coyote
count 1
first occurence 2021-04-22 11:03:20
last occurence 2021-04-22 11:03:20
user unknown user
type/analyzer Kerneloops/abrt-oops
pkg-fingerprint 49FD 7749 9570 FF31
kernel 5.11.15-200.fc33.x86_64
pkg_vendor Fedora Project
runlevel N 5
os_release Fedora release 33 (Thirty Three)
duphash 913d3ca671c62c4a2304f3f1ea8bded67351e0c0
uuid 913d3ca671c62c4a2304f3f1ea8bded67351e0c0
architecture x86_64
abrt_version 2.14.5
data directory /var/spool/abrt/oops-2021-04-22-11:03:20-875-0 _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en- US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject .org Do not reply to spam on the list, report it: https://pagure.io/fedora- infrastructure
On 4/22/21 9:59 PM, Qiyu Yan wrote:
在 2021-04-22星期四的 11:25 -0600，home user写道：
I did my weekly patches (dnf upgrade), rebooted, and logged in as a regular user. A problem popped-up. The top part of the details is below. I'm not (yet) seeing any other problems. Is this a false alarm? If not, what should I do?
The error seems like an error seen on fedora 34: https://bugzilla.redhat.com/show_bug.cgi?id=1949491 but since you are on Fedora 33, I don't know if it is related. You may want to report this in bugzilla, along with a traceback.
No need to worry so much, fwupd error won't break important things.
The problem report implies that a bug should not be submitted because the backtrace does not contain enough meaningful function frames to be reported.
On 2021-04-24 12:37 p.m., home user wrote:
The problem report implies that a bug should not be submitted because the backtrace does not contain enough meaningful function frames to be reported.
Not really. What it said is that it can't be automatically submitted, but you can still file a bug report yourself.
On 4/24/21 4:01 PM, Samuel Sieb wrote:
On 2021-04-24 12:37 p.m., home user wrote:
The problem report implies that a bug should not be submitted because the backtrace does not contain enough meaningful function frames to be reported.
Not really. What it said is that it can't be automatically submitted, but you can still file a bug report yourself.
It also implies to me that submitting a bug would be useless because the backtrace does not contain enough meaningful function frames to the problem be reported.
Qiyu reported that a bug was already submitted for this problem. But I've been getting others. Once the "wayward wayland" thread is solved, I'll submit bugs on those other problems, if someone else hasn't already done so.
By the way, if I don't know what to submit the bug against, what do I put in the component field? It's a required field, but I didn't see an option for unknown when I submitted the 2 bugs I submitted this week. Also, what do I put in the component field if it seems the problem could be two things? A selinux alert could be a selinux problem, or it could be a problem with whatever was trying to do something when the alert was triggered. Example: the caja problem dealt with in this list earlier this month.
On 4/24/21 7:26 PM, home user wrote:
On 4/24/21 4:01 PM, Samuel Sieb wrote:
On 2021-04-24 12:37 p.m., home user wrote:
The problem report implies that a bug should not be submitted because the backtrace does not contain enough meaningful function frames to be reported.
Not really. What it said is that it can't be automatically submitted, but you can still file a bug report yourself.
It also implies to me that submitting a bug would be useless because the backtrace does not contain enough meaningful function frames to the problem be reported.
You don't need a backtrace to report a bug. "This program crashed and I don't know why" is still a valid bug report.
By the way, if I don't know what to submit the bug against, what do I put in the component field? It's a required field, but I didn't see an option for unknown when I submitted the 2 bugs I submitted this week. Also, what do I put in the component field if it seems the problem could be two things? A selinux alert could be a selinux problem, or it could be a problem with whatever was trying to do something when the alert was triggered. Example: the caja problem dealt with in this list earlier this month.
If you don't know for sure, then file it against wherever you see it. If further investigations indicate the cause is elsewhere, then it can be re-assigned to that other component.
On 4/24/21 10:04 PM, Samuel Sieb wrote:
You don't need a backtrace to report a bug. "This program crashed and I don't know why" is still a valid bug report.
Also, be sure to include as much detail about what you were doing when it crashed because if/when somebody's going to need it and it's best to do it while your memory's fresh instead of weeks or even months later.
On 4/24/21 10:04 PM, Samuel Sieb wrote:
On 4/24/21 7:26 PM, home user wrote:
On 4/24/21 4:01 PM, Samuel Sieb wrote:
On 2021-04-24 12:37 p.m., home user wrote:
The problem report implies that a bug should not be submitted because the backtrace does not contain enough meaningful function frames to be reported.
Not really. What it said is that it can't be automatically submitted, but you can still file a bug report yourself.
It also implies to me that submitting a bug would be useless because the backtrace does not contain enough meaningful function frames to the problem be reported.
You don't need a backtrace to report a bug. "This program crashed and I don't know why" is still a valid bug report.
By the way, if I don't know what to submit the bug against, what do I put in the component field? It's a required field, but I didn't see an option for unknown when I submitted the 2 bugs I submitted this week. Also, what do I put in the component field if it seems the problem could be two things? A selinux alert could be a selinux problem, or it could be a problem with whatever was trying to do something when the alert was triggered. Example: the caja problem dealt with in this list earlier this month.
If you don't know for sure, then file it against wherever you see it. If further investigations indicate the cause is elsewhere, then it can be re-assigned to that other component.
ok.
one more question about filing bugs... After filling in the required fields and any optional fields that I think are helpful, is there something more I should do before clicking the submit button? The past few bugs I've submitted seem to just stay in the new state.
On 4/24/21 10:36 PM, Joe Zeff wrote:
On 4/24/21 10:04 PM, Samuel Sieb wrote:
You don't need a backtrace to report a bug. "This program crashed and I don't know why" is still a valid bug report.
Also, be sure to include as much detail about what you were doing when it crashed because if/when somebody's going to need it and it's best to do it while your memory's fresh instead of weeks or even months later.
That's what I try to do. But good reminder. Thank-you, Joe.
On 4/25/21 7:14 PM, home user wrote:
one more question about filing bugs... After filling in the required fields and any optional fields that I think are helpful, is there something more I should do before clicking the submit button? The past few bugs I've submitted seem to just stay in the new state.
No, it's up to the maintainer or other interested users to follow up on it. This might not happen right away and might even be a very long time. In many cases, it can be better to take the issue to the upstream project instead.
On 4/25/21 8:23 PM, Samuel Sieb wrote:
On 4/25/21 7:14 PM, home user wrote:
one more question about filing bugs... After filling in the required fields and any optional fields that I think are helpful, is there something more I should do before clicking the submit button? The past few bugs I've submitted seem to just stay in the new state.
No, it's up to the maintainer or other interested users to follow up on it. This might not happen right away and might even be a very long time. In many cases, it can be better to take the issue to the upstream project instead.
ok. Thank-you, Samuel.
On Sun, 25 Apr 2021 at 23:14, home user mattisonw@comcast.net wrote:
one more question about filing bugs... After filling in the required fields and any optional fields that I think are helpful, is there something more I should do before clicking the submit button? The past few bugs I've submitted seem to just stay in the new state.
Some bugs are only triggered by a rare combination of events. A bug that isn't reproducible or doesn't leave evidence behind won't get attention until there are enough reports to define a pattern. It is important to highlight anything that could help other victims of the same bug recognize that from your report so patterns can be identified.
Such bugs are generally better handled upstream -- otherwise reports of the same problem are scattered across different bug databases and patterns aren't easy to recognize.
On 4/26/21 4:32 AM, George N. White III wrote:
Some bugs are only triggered by a rare combination of events. A bug that isn't reproducible or doesn't leave evidence behind won't get attention until there are enough reports to define a pattern. It is important to highlight anything that could help other victims of the same bug recognize that from your report so patterns can be identified.
Such bugs are generally better handled upstream -- otherwise reports of the same problem are scattered across different bug databases and patterns aren't easy to recognize.
-- George N. White III
That makes sense. Thank-you, George.
The problem alerts stopped appearing on Thursday, April 29. SELinux alerts discussed in a separate thread stopped at the same time. That would have been when I did weekly patches ("dnf upgrade"). I also did weekly patches on Thursday, May 06. Since the problems did not start showing up again, I'm now confident they're really fixed.
So no bug has been submitted. I don't know what in the patches fixed things, but this workstation is fixed.
I thank everyone who tried to help and/or give bug-writing tips. I've marked this thread SOLVED. I will hunt down the SELinux alert thread to close it too, if not already done.
Bill.
-
George N. White III -
home user -
Joe Zeff -
Qiyu Yan -
Samuel Sieb