Hide Forgot
Description of problem: # dnf update Last metadata expiration check: 2:55:45 ago on Sun Jan 29 20:58:51 2017. Dependencies resolved. ============================================================================================================= Package Arch Version Repository Size ============================================================================================================= Skipping packages with broken dependencies: mesa-libEGL i686 13.0.3-4.fc25 updates 105 k mesa-libEGL x86_64 13.0.3-4.fc25 updates 103 k mesa-libEGL-devel x86_64 13.0.3-4.fc25 updates 38 k mesa-libGL i686 13.0.3-4.fc25 updates 181 k mesa-libGL x86_64 13.0.3-4.fc25 updates 164 k mesa-libGL-devel x86_64 13.0.3-4.fc25 updates 161 k mesa-libGLES x86_64 13.0.3-4.fc25 updates 21 k mesa-libGLES-devel x86_64 13.0.3-4.fc25 updates 62 k mesa-libglapi i686 13.0.3-4.fc25 updates 59 k mesa-libglapi x86_64 13.0.3-4.fc25 updates 49 k Transaction Summary ============================================================================================================= Skip 10 Packages Nothing to do. Complete! Because it came out # rpm -Fvh --nodeps mesa-lib[gEG]*.rpm After I ran the error, I got an error # dnf downgrade mesa-lib[gEG]*. rpm I returned to the original. Version-Release number of selected component: gnome-abrt-1.2.5-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/bin/gnome-abrt executable: /usr/bin/python3.5 global_pid: 6915 kernel: 4.9.5-200.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 call_init at dl-init.c:72 #3 _dl_init at dl-init.c:120 #4 dl_open_worker at dl-open.c:564 #5 _dl_catch_error at dl-error.c:187 #6 _dl_open at dl-open.c:649 #7 dlopen_doit at dlopen.c:66 #8 _dl_catch_error at dl-error.c:187 #9 _dlerror_run at dlerror.c:163 #10 __dlopen at dlopen.c:87
Created attachment 1245583 [details] File: backtrace
Created attachment 1245584 [details] File: cgroup
Created attachment 1245585 [details] File: core_backtrace
Created attachment 1245586 [details] File: dso_list
Created attachment 1245587 [details] File: environ
Created attachment 1245588 [details] File: limits
Created attachment 1245589 [details] File: maps
Created attachment 1245590 [details] File: mountinfo
Created attachment 1245591 [details] File: namespaces
Created attachment 1245592 [details] File: open_fds
Created attachment 1245593 [details] File: proc_pid_status
Created attachment 1245594 [details] File: var_log_messages
Created attachment 1245595 [details] File: exploitable
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.