Version-Release number of selected component: eom-1.20.1-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: eom /run/media/yetoo/CD/Photos/alec.jpg crash_function: eom_image_real_load executable: /usr/bin/eom journald_cursor: s=f2689b68410444829bfb81552d600bc1;i=1a395d;b=42c0eebcae6149e79f4a6c242fd186fe;m=140a54b4ae;t=57329eeac4072;x=115e9526041346ea kernel: 4.17.11-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1475591 [details] File: backtrace
Created attachment 1475592 [details] File: cgroup
Created attachment 1475593 [details] File: core_backtrace
Created attachment 1475594 [details] File: cpuinfo
Created attachment 1475595 [details] File: dso_list
Created attachment 1475596 [details] File: environ
Created attachment 1475597 [details] File: limits
Created attachment 1475598 [details] File: maps
Created attachment 1475599 [details] File: mountinfo
Created attachment 1475600 [details] File: open_fds
Created attachment 1475601 [details] File: proc_pid_status
No description!
(In reply to Wolfgang Ulbrich from comment #12) > No description! What information you need? This was uploaded with gnome-abrt with the "I don't know what happened" button.
(In reply to Scott Cohen from comment #13) > (In reply to Wolfgang Ulbrich from comment #12) > > No description! > > What information you need? This was uploaded with gnome-abrt with the "I > don't know what happened" button. I don't agree with the decision from abrt guys to allow reports without important infos. Because they talking about my spare time. I am not paid by RedHat. For me a report without infos can be kicked in a ton. What did you do? Steps to reproduce?
(In reply to Wolfgang Ulbrich from comment #14) > I don't agree with the decision from abrt guys to allow reports without > important infos. > Because they talking about my spare time. No one asked you to choose and close this bug. This bug occurred randomly and the data sent is supposed to help either reconstruct the system or determine what errors occurred in the logs. > I am not paid by RedHat. Again, no one asked you to choose this bug and close this bug. > For me a report without infos can be kicked in a ton. It doesn't matter what you want, a report is a report. > What did you do? > Steps to reproduce? This probably occurred during a high swap time, but I don't remember exactly. What information can you extrapolate from the attachment data provided, assuming you know what to look for, and if you can't find anything worthwhile in the data, please say what would be helpful with more data from software components existing at the time of bug occurrence, then if you still need something from me, tag this with NEEDINFO via clicking the "Need additional information from" check box, choose reporter, and then wait. If the system data provided here truly doesn't provide anything then, keep the bug status as it is.
(In reply to Scott Cohen from comment #15) > (In reply to Wolfgang Ulbrich from comment #14) > > I don't agree with the decision from abrt guys to allow reports without > > important infos. > > Because they talking about my spare time. > No one asked you to choose and close this bug. This bug occurred randomly > and the data sent is supposed to help either reconstruct the system or > determine what errors occurred in the logs. > > I am not paid by RedHat. > Again, no one asked you to choose this bug and close this bug. Ok, ask some other for help ;) > > For me a report without infos can be kicked in a ton. > It doesn't matter what you want, a report is a report. > > What did you do? > > Steps to reproduce? > This probably occurred during a high swap time, but I don't remember > exactly. What information can you extrapolate from the attachment data > provided, assuming you know what to look for, and if you can't find anything > worthwhile in the data, please say what would be helpful with more data from > software components existing at the time of bug occurrence, then if you > still need something from me, tag this with NEEDINFO via clicking the "Need > additional information from" check box, choose reporter, and then wait. If > the system data provided here truly doesn't provide anything then, keep the > bug status as it is.