Very occasionally, and for no reason I can think of, I get a pop-up with this message:
"Oops, it looks like a problem has ocurred in a component. The problem has been reported."
I assume it's from some part of KDE, mainly due to its appearance, but apart from that, there is NO useful information:
1) Who is telling me this? 2) What is the problem? 3) What is the component? 4) Who has it been reported to, and how? 5) What can I do about it?
poc
Patrick O'Callaghan wrote:
Very occasionally, and for no reason I can think of, I get a pop-up with this message:
"Oops, it looks like a problem has ocurred in a component. The problem has been reported."
I assume it's from some part of KDE, mainly due to its appearance, but apart from that, there is NO useful information:
- Who is telling me this?
- What is the problem?
- What is the component?
- Who has it been reported to, and how?
- What can I do about it?
1. abrt
can't answer the other items
-- Rex
On Fri, 2016-03-18 at 08:25 -0500, Rex Dieter wrote:
Patrick O'Callaghan wrote:
Very occasionally, and for no reason I can think of, I get a pop-up with this message:
"Oops, it looks like a problem has ocurred in a component. The problem has been reported."
I assume it's from some part of KDE, mainly due to its appearance, but apart from that, there is NO useful information:
- Who is telling me this?
- What is the problem?
- What is the component?
- Who has it been reported to, and how?
- What can I do about it?
1. abrt
can't answer the other items
I've seen messages from abrt and they don't look like this, plus they usually give more information.
poc
Rex Dieter wrote:
Patrick O'Callaghan wrote:
Very occasionally, and for no reason I can think of, I get a pop-up with this message:
"Oops, it looks like a problem has ocurred in a component. The problem has been reported."
I assume it's from some part of KDE, mainly due to its appearance, but apart from that, there is NO useful information:
- Who is telling me this?
- What is the problem?
- What is the component?
- Who has it been reported to, and how?
- What can I do about it?
- abrt
can't answer the other items
-- Rex
Regarding the other items, have a look at the ABRT GUI, which you can find in the KDE menu under
System > Problem Reporting (Icon with Exclamation Mark)
The tool shows a list of components that recently crashed and for each of these, among other things - Version : <component version> - Reported: {yes, no}
For each crash, you can - look at "Details" (detailed crash info) - select "Report" to generate a bug report, after configuring the tool through the "ABRT configuration" menu entry - select "Clear" to delete no longer needed crash info
Bug reporting via "Report" used to work for me (F22, some months ago), but you may need to install debug packages in order to generate/submit a complete bug report with stack trace etc.
IMO "Problem Reporting" is quite useful to get a quick overview of the most recent crashes, but I'm not sure whether the ABRT reports I submitted were ever looked at by anyone ...
Cheers, - Fredy
On Fri, 2016-03-18 at 15:07 +0100, Fredy Neeser wrote:
1. abrt
can't answer the other items
-- Rex
Regarding the other items, have a look at the ABRT GUI, which you can find in the KDE menu under
System > Problem Reporting (Icon with Exclamation Mark)
The tool shows a list of components that recently crashed and for each of these, among other things
- Version : <component version>
- Reported: {yes, no}
I checked that and the only problem reported today was with kde-cli- tools. Since I wasn't using the command line when the error message appeared, I'm still not convinced abrt has anything to do with this. The pop-up doesn't show the usual abrt icon but a sad face that looks like something from KDE. I could be wrong of course, but my point is that an error message the user cannot possibly understand is of no use to anyone.
poc
On Friday 18 of March 2016 16:51:02 Patrick O'Callaghan wrote:
On Fri, 2016-03-18 at 15:07 +0100, Fredy Neeser wrote:
- abrt
can't answer the other items
-- Rex
Regarding the other items, have a look at the ABRT GUI, which you can find in the KDE menu under
System > Problem Reporting (Icon with Exclamation Mark)
The tool shows a list of components that recently crashed and for each of these, among other things
- Version : <component version>
- Reported: {yes, no}
I checked that and the only problem reported today was with kde-cli- tools. Since I wasn't using the command line when the error message appeared, I'm still not convinced abrt has anything to do with this. The pop-up doesn't show the usual abrt icon but a sad face that looks like something from KDE. I could be wrong of course, but my point is that an error message the user cannot possibly understand is of no use to anyone.
This is perfectly reasonable and the message should be improved. The problem is that I can't find it. It was about kde-cli-tools, was the message different? Can you please take a screenshot when it happens again?
On Fri, 2016-03-18 at 17:59 +0100, Luigi Toscano wrote:
On Friday 18 of March 2016 16:51:02 Patrick O'Callaghan wrote:
On Fri, 2016-03-18 at 15:07 +0100, Fredy Neeser wrote:
1. abrt
can't answer the other items
-- Rex
Regarding the other items, have a look at the ABRT GUI, which you can find in the KDE menu under
System > Problem Reporting (Icon with Exclamation Mark)
The tool shows a list of components that recently crashed and for each of these, among other things
- Version : <component version>
- Reported: {yes, no}
I checked that and the only problem reported today was with kde- cli- tools. Since I wasn't using the command line when the error message appeared, I'm still not convinced abrt has anything to do with this. The pop-up doesn't show the usual abrt icon but a sad face that looks like something from KDE. I could be wrong of course, but my point is that an error message the user cannot possibly understand is of no use to anyone.
This is perfectly reasonable and the message should be improved. The problem is that I can't find it. It was about kde-cli-tools, was the message different? Can you please take a screenshot when it happens again?
I'll try, but the thing I neglected to mention is that IIRC it stays up for a few seconds, then disappears on its own, i.e. without waiting to be dismissed. That's why the text I quoted is an approximation from memory. It's close but may not be exact.
poc
On Fri, Mar 18, 2016 at 03:07:56PM +0100, Fredy Neeser wrote:
IMO "Problem Reporting" is quite useful to get a quick overview of the most recent crashes, but I'm not sure whether the ABRT reports I submitted were ever looked at by anyone ...
They are often not looked at individually, but they definitely are in aggregate. When there's little development time to go around, helps to focus the effort on bugs that are hitting a lot of people. Of course, ideally, _every_ report would get attention, but in the real world, it's not always possible.
See https://blogs.gnome.org/uraeus/2016/01/05/fedora-workstation-and-the-quest-f... for some related thoughts.
On 03/18/16 21:25, Rex Dieter wrote:
Patrick O'Callaghan wrote:
Very occasionally, and for no reason I can think of, I get a pop-up with this message:
"Oops, it looks like a problem has ocurred in a component. The problem has been reported."
I assume it's from some part of KDE, mainly due to its appearance, but apart from that, there is NO useful information:
- Who is telling me this?
- What is the problem?
- What is the component?
- Who has it been reported to, and how?
- What can I do about it?
- abrt
can't answer the other items
It seems possible that this error message is generated when kwin crashes.
I have a screenshot of the exact error message if anyone is interested. Also abrt tool shows kwin crashing about the right time and going to report it comes up with https://bugzilla.redhat.com/show_bug.cgi?id=1290248 being the same/similar.
On Saturday 19 March 2016 11:47 AM, Ed Greshko wrote:
It seems possible that this error message is generated when kwin crashes. I have a screenshot of the exact error message if anyone is interested. Also abrt tool shows kwin crashing about the right time and going to report it comes up with https://bugzilla.redhat.com/show_bug.cgi?id=1290248 being the same/similar.
Where is the screenshot? I think it's not related to KDE. I have seen similar pop-up with sad-face icon when something crashes or when my CPU temperature goes too high. The event will be listed in abrt 'Problem Reporting' tool.
Syam
On 03/19/16 14:36, Syam Krishnan wrote:
On Saturday 19 March 2016 11:47 AM, Ed Greshko wrote:
It seems possible that this error message is generated when kwin crashes. I have a screenshot of the exact error message if anyone is interested. Also abrt tool shows kwin crashing about the right time and going to report it comes up with https://bugzilla.redhat.com/show_bug.cgi?id=1290248 being the same/similar.
Where is the screenshot?
Since you asked.... https://ibin.co/2alO8UEJW1k2.jpg
I think it's not related to KDE. I have seen similar pop-up with sad-face icon when something crashes or when my CPU temperature goes too high. The event will be listed in abrt 'Problem Reporting' tool.
On Saturday 19 March 2016 01:17 PM, Ed Greshko wrote:
Since you asked.... https://ibin.co/2alO8UEJW1k2.jpg
Yes.. this is exactly what I get when my CPU temperature goes up.
When I open the 'Problem reporting' tool, it is listed as a "unexpected system error" : http://imgur.com/26UxuBR
Syam
On 03/19/16 18:48, Syam Krishnan wrote:
On Saturday 19 March 2016 01:17 PM, Ed Greshko wrote:
Since you asked.... https://ibin.co/2alO8UEJW1k2.jpg
Yes.. this is exactly what I get when my CPU temperature goes up.
When I open the 'Problem reporting' tool, it is listed as a "unexpected system error" : http://imgur.com/26UxuBR
Well, I know for sure my CPU's aren't overheating....
Core 0: +43.0°C (high = +82.0°C, crit = +98.0°C) Core 1: +42.0°C (high = +82.0°C, crit = +98.0°C) Core 2: +48.0°C (high = +82.0°C, crit = +98.0°C) Core 3: +41.0°C (high = +82.0°C, crit = +98.0°C)
On Saturday 19 March 2016 04:25 PM, Ed Greshko wrote:
Yes.. this is exactly what I get when my CPU temperature goes up.
When I open the 'Problem reporting' tool, it is listed as a "unexpected system error" : http://imgur.com/26UxuBR
Well, I know for sure my CPU's aren't overheating....
Core 0: +43.0°C (high = +82.0°C, crit = +98.0°C) Core 1: +42.0°C (high = +82.0°C, crit = +98.0°C) Core 2: +48.0°C (high = +82.0°C, crit = +98.0°C) Core 3: +41.0°C (high = +82.0°C, crit = +98.0°C)
What I meant was that it's not related to KDE and that the pop-ups can appear on crashes and even CPU core-temperature events.
Syam
On 03/19/16 19:22, Syam Krishnan wrote:
On Saturday 19 March 2016 04:25 PM, Ed Greshko wrote:
Yes.. this is exactly what I get when my CPU temperature goes up.
When I open the 'Problem reporting' tool, it is listed as a "unexpected system error" : http://imgur.com/26UxuBR
Well, I know for sure my CPU's aren't overheating....
Core 0: +43.0°C (high = +82.0°C, crit = +98.0°C) Core 1: +42.0°C (high = +82.0°C, crit = +98.0°C) Core 2: +48.0°C (high = +82.0°C, crit = +98.0°C) Core 3: +41.0°C (high = +82.0°C, crit = +98.0°C)
What I meant was that it's not related to KDE and that the pop-ups can appear on crashes and even CPU core-temperature events.
Yours may not be. But in my case it certainly tracks with a KDE component as I mentioned in the one case "kwin".
On 03/19/2016 09:09 AM, Ed Greshko wrote:
On 03/19/16 19:22, Syam Krishnan wrote:
On Saturday 19 March 2016 04:25 PM, Ed Greshko wrote:
Yes.. this is exactly what I get when my CPU temperature goes up.
When I open the 'Problem reporting' tool, it is listed as a "unexpected system error" : http://imgur.com/26UxuBR
Well, I know for sure my CPU's aren't overheating....
Core 0: +43.0°C (high = +82.0°C, crit = +98.0°C) Core 1: +42.0°C (high = +82.0°C, crit = +98.0°C) Core 2: +48.0°C (high = +82.0°C, crit = +98.0°C) Core 3: +41.0°C (high = +82.0°C, crit = +98.0°C)
What I meant was that it's not related to KDE and that the pop-ups can appear on crashes and even CPU core-temperature events.
Yours may not be. But in my case it certainly tracks with a KDE component as I mentioned in the one case "kwin".
Right. But the popup is an abrt one, not a KDE error message.
Am 19.03.2016 um 13:09 schrieb Ed Greshko:
On 03/19/16 19:22, Syam Krishnan wrote:
On Saturday 19 March 2016 04:25 PM, Ed Greshko wrote:
Yes.. this is exactly what I get when my CPU temperature goes up.
When I open the 'Problem reporting' tool, it is listed as a "unexpected system error" : http://imgur.com/26UxuBR
Well, I know for sure my CPU's aren't overheating....
Core 0: +43.0°C (high = +82.0°C, crit = +98.0°C) Core 1: +42.0°C (high = +82.0°C, crit = +98.0°C) Core 2: +48.0°C (high = +82.0°C, crit = +98.0°C) Core 3: +41.0°C (high = +82.0°C, crit = +98.0°C)
What I meant was that it's not related to KDE and that the pop-ups can appear on crashes and even CPU core-temperature events.
Yours may not be. But in my case it certainly tracks with a KDE component as I mentioned in the one case "kwin".
what about read what ABTR is (https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/htm...) before comment and consider disable and uninstall ABRT whne you can't see a usecase (as i did)
[harry@srv-rhsoft:~]$ rpm -qa | grep -i abrt [harry@srv-rhsoft:~]$
On Saturday 19 Mar 2016 4:18:43 PM Syam Krishnan wrote:
Yes.. this is exactly what I get when my CPU temperature goes up.
I had a huge a number of non-fatal kernel oops-es when my system temp goes up. These were non-reportable mce errors.
I was able to disable them by settings OnlyFatalMCE from no to yes.
cat /etc/abrt/plugins/oops.conf # Configuration file for Kernel oops hook
# If you want to see only reportable oopses, # set to "yes". # DropNotReportableOopses = yes
# Lot of Machine Check Exceptions are correctable and thus not interesting to # users. Moreover some hardware may produce plenty of MCEs by design. # # Setting the following option to 'yes' will configure ABRT to detect only # the fatal MCEs. # OnlyFatalMCE = yes
On Sat, 2016-03-19 at 15:47 +0800, Ed Greshko wrote:
On 03/19/16 14:36, Syam Krishnan wrote:
On Saturday 19 March 2016 11:47 AM, Ed Greshko wrote:
It seems possible that this error message is generated when kwin
crashes. I have a
screenshot of the exact error message if anyone is interested.
Also abrt tool shows
kwin crashing about the right time and going to report it comes up
with
https://bugzilla.redhat.com/show_bug.cgi?id=1290248%C2%A0being the
same/similar.
Where is the screenshot?
Since you asked.... https://ibin.co/2alO8UEJW1k2.jpg
Yes, that looks like it (modulo thematic elements). It's ironic that we should be discussing where it comes from, when that is precisely why we're discussing it.
poc
On Friday 18 of March 2016 13:21:09 Patrick O'Callaghan wrote:
Very occasionally, and for no reason I can think of, I get a pop-up with this message:
"Oops, it looks like a problem has ocurred in a component. The problem has been reported."
Is this the exact message?
I assume it's from some part of KDE, mainly due to its appearance, but apart from that, there is NO useful information:
- Who is telling me this?
I can't find the message among the sources hosted on kde.org (trying substrings with lxr.kde.org).
On 03/18/16 22:05, Luigi Toscano wrote:
On Friday 18 of March 2016 13:21:09 Patrick O'Callaghan wrote:
Very occasionally, and for no reason I can think of, I get a pop-up with this message:
"Oops, it looks like a problem has ocurred in a component. The problem has been reported."
Is this the exact message?
Yes, that is the exact message that pops up in the bottom right corner of the systray. For me it happens fairly consistently at login time. It only displays for several seconds. I've been ignoring it since I can't determine any ill effect.
I assume it's from some part of KDE, mainly due to its appearance, but apart from that, there is NO useful information:
- Who is telling me this?
I can't find the message among the sources hosted on kde.org (trying substrings with lxr.kde.org).
On Friday 18 March 2016 13:21:09 Patrick O'Callaghan wrote:
Very occasionally, and for no reason I can think of, I get a pop-up with this message:
"Oops, it looks like a problem has ocurred in a component. The problem has been reported."
I do too, and I completely agree, infuriating!
On Fri, 2016-03-18 at 13:21 +0000, Patrick O'Callaghan wrote:
Very occasionally, and for no reason I can think of, I get a pop-up with this message:
"Oops, it looks like a problem has ocurred in a component. The problem has been reported."
I assume it's from some part of KDE, mainly due to its appearance, but apart from that, there is NO useful information:
- Who is telling me this?
- What is the problem?
- What is the component?
- Who has it been reported to, and how?
- What can I do about it?
It looks like this is the culprit:
https://bugzilla.redhat.com/show_bug.cgi?id=1279446
However my point remains: the error message isn't telling me anything directly, not even that it comes from abrt.
poc
-
Ed Greshko -
Fredy Neeser -
Luigi Toscano -
Mark Stanton -
Matthew Miller -
Patrick Boutilier -
Patrick O'Callaghan -
Reindl Harald -
Rex Dieter -
Sudhir Khanger -
Syam Krishnan