Bug 1955926 - Problem report make issue that may because of diskspace issue
Summary: Problem report make issue that may because of diskspace issue
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-abrt
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Filak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-01 14:04 UTC by Lars Martin hambro
Modified: 2022-06-07 22:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-07 22:03:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lars Martin hambro 2021-05-01 14:04:42 UTC
Description of problem:
i think you should check that happed if home folder is full i think most of bug i get its because poor bug rapport system its can not report bug, also issue that only few bug can be reported to bugzilla, i get process failed because networks issue or config or invalid data corrupted problem data.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
--- Skipping collect_GConf ---
No matching actions found for this event.

--- Skipping collect_vimrc_system ---
No matching actions found for this event.

--- Skipping collect_xsession_errors ---
No matching actions found for this event.

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES'
Querying server settings
Preparing an archive to upload
Uploading 52.8 KiB
Upload successful
Retrace job started
Analyzing crash data
...
Retrace job failed
Retrace failed. Try again later and if the problem persists report this issue please.
[2021-05-01 13:57:55] [I] Analyzing crash data

Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace). 'YES'
Analyzing coredump 'coredump'
Cleaning cache...
Coredump references 11 debuginfo files
Initializing package manager
Setting up repositories
Looking for needed packages in repositories
Going to install 5 debuginfo packages
Can't find packages for 11 debuginfo files
Packages to download: 5
Downloading 21.89Mb, installed size: 140.75Mb. Continue? 'YES'
Downloading (1 of 5) SDL2_net-debuginfo-2.0.1-13.fc34.x86_64.rpm: 100%
Extracting cpio from /var/tmp/dnf-larsmartinhambro-dgd5ox3n/rawhide-debuginfo-b0297fcd3e236bd4/packages/SDL2_net-debuginfo-2.0.1-13.fc34.x86_64.rpm
Caching files from unpacked.cpio made from SDL2_net-debuginfo-2.0.1-13.fc34.x86_64.rpm
Can't extract files from '/var/tmp/abrt-tmp-debuginfo.FBDEfH/unpacked.cpio'. For more information see '/tmp/abrt-unpacking-wym6n_nh'
Unpacking failed, aborting download...
Can't download debuginfos: [Errno 1] Operation not permitted: '/var/cache/abrt-di/usr'

--- Skipping analyze_BodhiUpdates ---
No matching actions found for this event.

--- Skipping report_Bugzilla ---
No matching actions found for this event.

--- Running post_report ---
This problem has not been reported to Bugzilla.
('post_report' exited with 1)

Comment 1 Michal Srb 2021-05-04 14:27:42 UTC
Thanks for the bug report.

Could you please check permissions on the directory?

ls -la /var/cache/abrt-di/

And also check the version of ABRT on your system?

rpm -qa | grep abrt


Thanks!

Comment 2 Lars Martin hambro 2021-05-04 14:40:35 UTC
ls -la /var/cache/abrt-di/
total 12
drwxrwxr-x.  3 abrt abrt 4096 Jan 26 01:26 .
drwxr-xr-x. 21 root root 4096 May  2 09:16 ..
-rw-r--r--.  1 root root    0 Nov  1  2020 .migration-group-add
drwxrwxr-x.  4 abrt abrt 4096 Apr 12  2020 usr

rpm -qa | grep abrt
abrt-libs-2.14.5-2.fc34.x86_64
abrt-dbus-2.14.5-2.fc34.x86_64
abrt-2.14.5-2.fc34.x86_64
python3-abrt-2.14.5-2.fc34.x86_64
abrt-addon-kerneloops-2.14.5-2.fc34.x86_64
abrt-retrace-client-2.14.5-2.fc34.x86_64
abrt-addon-pstoreoops-2.14.5-2.fc34.x86_64
python3-abrt-addon-2.14.5-2.fc34.noarch
abrt-addon-xorg-2.14.5-2.fc34.x86_64
abrt-plugin-bodhi-2.14.5-2.fc34.x86_64
abrt-addon-ccpp-2.14.5-2.fc34.x86_64
abrt-tui-2.14.5-2.fc34.x86_64
abrt-addon-vmcore-2.14.5-2.fc34.x86_64
abrt-gui-libs-2.14.5-2.fc34.x86_64
abrt-gui-2.14.5-2.fc34.x86_64
abrt-desktop-2.14.5-2.fc34.x86_64
abrt-cli-2.14.5-2.fc34.x86_64
abrt-java-connector-1.2.0-5.fc34.x86_64
gnome-abrt-1.3.6-5.fc34.x86_64

i think https://bugzilla.redhat.com/show_bug.cgi?id=1956591 maybe can be issue with program itself. Because missing data.

Comment 3 Lars Martin hambro 2021-05-06 11:18:27 UTC
I find upgrade today:
rpm -qa | grep abrt
abrt-java-connector-1.2.0-5.fc34.x86_64
gnome-abrt-1.3.6-5.fc34.x86_64
abrt-libs-2.14.5-3.fc34.x86_64
abrt-dbus-2.14.5-3.fc34.x86_64
python3-abrt-2.14.5-3.fc34.x86_64
abrt-2.14.5-3.fc34.x86_64
abrt-retrace-client-2.14.5-3.fc34.x86_64
abrt-addon-ccpp-2.14.5-3.fc34.x86_64
abrt-addon-kerneloops-2.14.5-3.fc34.x86_64
abrt-addon-pstoreoops-2.14.5-3.fc34.x86_64
abrt-addon-vmcore-2.14.5-3.fc34.x86_64
abrt-addon-xorg-2.14.5-3.fc34.x86_64
abrt-plugin-bodhi-2.14.5-3.fc34.x86_64
python3-abrt-addon-2.14.5-3.fc34.noarch
abrt-tui-2.14.5-3.fc34.x86_64
abrt-gui-libs-2.14.5-3.fc34.x86_64
abrt-gui-2.14.5-3.fc34.x86_64
abrt-desktop-2.14.5-3.fc34.x86_64
abrt-cli-2.14.5-3.fc34.x86_64

Please confirm if that make its difference? because i still get kernel bugs but it can not be reported. So something is wrong.

Comment 4 Michal Srb 2021-05-11 14:16:52 UTC
Thanks for the additional information. After the upgrade, do you still see the error about the permissions?

> Can't download debuginfos: [Errno 1] Operation not permitted: '/var/cache/abrt-di/usr'

Or only the problem with reporting kernel bugs? Thanks!

Comment 5 Lars Martin hambro 2021-05-11 17:03:52 UTC
 ls -la /var/cache/abrt-di/
total 12
drwxrwxr-x.  3 abrt abrt 4096 May  2 09:37 .
drwxr-xr-x. 21 root root 4096 May  2 09:16 ..
-rw-r--r--.  1 root root    0 Nov  1  2020 .migration-group-add
drwxrwxr-x.  4 abrt abrt 4096 Apr 12  2020 usr

its issue that not everything be log correctly, i get default message This problem is rapported but bugzilla has not be opened developer may need more information to find fix the problem. Please consider to rapport it to bugzilla.

but issue here is software is to poor that did not make its easy to copy information (Needed to make bug) and may be better to login to account.
Because if that fail its impossible to get information 

https://retrace.fedoraproject.org/faf/reports/147144/
its can be used:
abrt-cli 
3afa491 1x webkit2gtk3 2021-05-04 04:03:13
f542d51 2x xorg-x11-server-Xwayland 2021-05-01 14:08:51
0584357 3x chocolate-doom 2021-05-01 15:47:53
167824c 1x totem 2021-04-25 21:07:59
e58801c 5x chocolate-doom 2021-05-01 15:46:01
7673359 1x xorg-x11-server-Xwayland 2021-04-25 13:36:06
a99d883 5x gnome-screenshot 2021-04-25 21:21:27
c3f06d5 3x irssi 2021-05-02 07:41:23
97ff9ff 1x mypaint 2021-05-01 15:30:14

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/ch-abrt

But did not find way to make bug from terminal to check if that works easy and faster?
I think software is poor made for less space and fast bug report. I know ubuntu its more easy with ubuntu-bug package in terminal.

Comment 6 Michal Srb 2021-05-18 14:21:28 UTC
I think the root cause is that you're not able to extract stacktrace from the coredump. There is a known issue with retrace server, and if you have some disk space issues on your laptop, even local retracing will fail. Until the underlying issue is fixed, reporting from command line would not help here.

Can we try one more thing? Could you please try to run

rm -Rf /var/cache/abrt-di/usr

as root? the /var/cache/abrt-di/usr directory is not owned by any package, it is later created by ABRT at runtime. This could help.

Sorry for the delays in responses. I will try to do better.

Thanks ;)

Comment 7 Lars Martin hambro 2021-05-25 04:38:21 UTC
So is not important to get better bugsystem like ubuntu 21.04?
Or what is plan for fedora 35?

Comment 8 Lars Martin hambro 2021-05-31 09:08:28 UTC
Please help me to make bug

firefox killed by SIGBUS
disk_cache_put_key
/usr/lib64/firefox/firefox https://retrace.fedoraproject.org/faf/reports/bthash/ae421182dbbc8d716589ac81da32cb821cb6e1fe
firefox-88.0.1-1.fc34
/var/spool/abrt/ccpp-2021-05-31-10:54:48.295503-24554

s=45ee37c46d884c82abc52974aa3c5198;i=9abc;b=84309f41dc7a45d4a995047c69077c62;m=31ea45e4;t=5c39c60aea8d9;x=52a73b72873002e1


https://pastebin.com/S2CtuPbJ

Did you find out why its crashes diskpace or empty home folder?

Comment 9 Ben Cotton 2022-05-12 15:32:16 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 10 Ben Cotton 2022-06-07 22:03:48 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.