Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: the previous version of fedora 34 stopped updating and i could not run the kernel regression tests with the -performance option so i have just upgraded to fedora 34 again after reinstalling it on this acer Aspire 4720 laptop. when i installed fedora 34 i reboted and logged in, shortly after that i knoticed applications would close soon after being opened, i may have tryed to do killall -w -ABRT -u, i have no w ran updates with dnf in the comandline and rebooted to find these error reports have now appeared inder the abrt-cli program (they werent before) Version-Release number of selected component: dbus-broker-26-2.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/dbus-broker.service cmdline: dbus-broker --log 4 --controller 10 --machine-id 9187c23bf2944f14ad8be4c200b11c4c --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000 crash_function: epoll_wait executable: /usr/bin/dbus-broker journald_cursor: s=1bf2d8b6c5714115b60721045e8ddc9c;i=16696;b=db676971097a48529f4ab34d0e354ce2;m=f799cbeb7;t=5bba704af8908;x=b2ce771f948a926d kernel: 5.11.0-0.rc7.20210210gite0756cfc7d7c.150.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 epoll_wait at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 dispatch_context_poll at ../src/util/dispatch.c:279 #2 dispatch_context_dispatch at ../src/util/dispatch.c:320 #3 broker_run at ../src/broker/broker.c:219 #4 run at ../src/broker/main.c:242 Potential duplicate: bug 1907568
Created attachment 1758014 [details] File: backtrace
Created attachment 1758015 [details] File: core_backtrace
Created attachment 1758016 [details] File: cpuinfo
Created attachment 1758017 [details] File: dso_list
Created attachment 1758018 [details] File: environ
Created attachment 1758019 [details] File: limits
Created attachment 1758020 [details] File: maps
Created attachment 1758021 [details] File: mountinfo
Created attachment 1758022 [details] File: open_fds
Created attachment 1758023 [details] File: proc_pid_status
*** Bug 1930579 has been marked as a duplicate of this bug. ***
*** Bug 1920789 has been marked as a duplicate of this bug. ***
*** Bug 1907568 has been marked as a duplicate of this bug. ***
(In reply to robert fairbrother from comment #0) > Description of problem: > the previous version of fedora 34 stopped updating and i could not run the > kernel regression tests with the -performance option so i have just upgraded > to fedora 34 again > after reinstalling it on this acer Aspire 4720 laptop. > when i installed fedora 34 i reboted and logged in, shortly after that i > knoticed applications would close soon after being opened, i may have tryed > to do killall -w -ABRT -u, i have no w ran updates with dnf in the > comandline and rebooted to find these error reports have now appeared inder > the abrt-cli program (they werent before) Am I understanding correctly that you typed this: killall -w -ABRT -u In this case, you just sent `SIGABRT` to all processes of this user, thus including the dbus-broker processes running under this user. So this bug-report just states that dbus-broker exited due to `SIGABRT`, which is exactly what you wanted it to do? `SIGABRT` is not used by any dbus-broker infrastructure, so the coredump you posted indicates the signal was sent from another processes. In this case, you really need to report this bug to whatever sent this signal. If you did not sent it yourself, and you have problems identifying which process sent the signal, we can try to work this out together.
(In reply to David Rheinsberg from comment #14) > (In reply to robert fairbrother from comment #0) > > Description of problem: > > the previous version of fedora 34 stopped updating and i could not run the > > kernel regression tests with the -performance option so i have just upgraded > > to fedora 34 again > > after reinstalling it on this acer Aspire 4720 laptop. > > when i installed fedora 34 i reboted and logged in, shortly after that i > > knoticed applications would close soon after being opened, i may have tryed > > to do killall -w -ABRT -u, i have no w ran updates with dnf in the > > comandline and rebooted to find these error reports have now appeared inder > > the abrt-cli program (they werent before) > > Am I understanding correctly that you typed this: > > killall -w -ABRT -u > > In this case, you just sent `SIGABRT` to all processes of this user, thus > including the dbus-broker processes running under this user. So this > bug-report just states that dbus-broker exited due to `SIGABRT`, which is > exactly what you wanted it to do? > > `SIGABRT` is not used by any dbus-broker infrastructure, so the coredump you > posted indicates the signal was sent from another processes. In this case, > you really need to report this bug to whatever sent this signal. If you did > not sent it yourself, and you have problems identifying which process sent > the signal, we can try to work this out together. yes i used killall -w -ABRT -u my entire uses session was unusable so i didnt kn ow where to send it im thinking it might help to login to my account and then run startx with the &> option to append the terminal output to a text file and upload that to someone? what really gets me is that more often thain not now when something is broken and my computer becomes unusable abrt dosent detectc any problem or the problems it detects are not reportable for some reason or another like incomplete problem data
(In reply to robert fairbrother from comment #15) > (In reply to David Rheinsberg from comment #14) > > (In reply to robert fairbrother from comment #0) > > > Description of problem: > > > the previous version of fedora 34 stopped updating and i could not run the > > > kernel regression tests with the -performance option so i have just upgraded > > > to fedora 34 again > > > after reinstalling it on this acer Aspire 4720 laptop. > > > when i installed fedora 34 i reboted and logged in, shortly after that i > > > knoticed applications would close soon after being opened, i may have tryed > > > to do killall -w -ABRT -u, i have no w ran updates with dnf in the > > > comandline and rebooted to find these error reports have now appeared inder > > > the abrt-cli program (they werent before) > > > > Am I understanding correctly that you typed this: > > > > killall -w -ABRT -u > > > > In this case, you just sent `SIGABRT` to all processes of this user, thus > > including the dbus-broker processes running under this user. So this > > bug-report just states that dbus-broker exited due to `SIGABRT`, which is > > exactly what you wanted it to do? > > > > `SIGABRT` is not used by any dbus-broker infrastructure, so the coredump you > > posted indicates the signal was sent from another processes. In this case, > > you really need to report this bug to whatever sent this signal. If you did > > not sent it yourself, and you have problems identifying which process sent > > the signal, we can try to work this out together. > > yes i used killall -w -ABRT -u > my entire uses session was unusable so i didnt kn ow where to send it > im thinking it might help to login to my account and then run startx with > the &> option to append the terminal output to a text file and upload that > to someone? > > what really gets me is that more often thain not now when something is > broken and my computer becomes unusable abrt dosent detectc any problem or > the problems it detects are not reportable for some reason or another like > incomplete problem data This is quite unfortunate. Though `killall -w ABRT` just causes all your session processes to dump core, and thus trigger `abrt` to send those as bug-reports. However, in this case those processes were not necessarily involved in whatever problems you experienced. If you have particular issues, I recommend filing these as individual bug-reports with a full description of the issue. Unfortunately, the core-dump you provided in this report is not suitable to debug anything but the message broker on your system (which in this case did not behave abnormally, iiuc).
Similar problem has been detected: left the computer on for several days, dont know what caused the crash reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1003.slice/user/dbus-broker.service cmdline: dbus-broker --log 4 --controller 11 --machine-id 35643391f483434d8c9d7dfd0800a590 --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000 crash_function: epoll_wait executable: /usr/bin/dbus-broker journald_cursor: s=509ae05e07e14a02acec9c7664909a41;i=38df3;b=f2d0ecc4dad244da9c047e08aea54590;m=f78b5c2b;t=5c14bfef3dace;x=49f93cce0ad407a kernel: 5.11.16-200.fc33.x86_64 package: dbus-broker-28-3.fc33 reason: dbus-broker killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1003
Similar problem has been detected: dont know what caused the problem reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1003.slice/user/dbus-broker.service cmdline: /usr/bin/dbus-broker-launch --scope user crash_function: epoll_wait executable: /usr/bin/dbus-broker-launch journald_cursor: s=509ae05e07e14a02acec9c7664909a41;i=38e1e;b=f2d0ecc4dad244da9c047e08aea54590;m=f7a7446c;t=5c14bff0fc30f;x=f3d99525447c6363 kernel: 5.11.16-200.fc33.x86_64 package: dbus-broker-28-3.fc33 reason: dbus-broker-launch killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1003