Description of problem: J'ai ouvert une archive contenant des fichiers de configuration openvn. File-roller quitte lorsque j'ouvre un sous-dossier. I opened an achive of openvpn configuration files. File-roller quit when I open any sub-folder. Lien vers l'archive / Link to the archive : https://downloads.nordcdn.com/configs/archives/servers/ovpn.zip Version-Release number of selected component: file-roller-3.28.0-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: file-roller /home/me/ovpn.zip crash_function: gdk_window_is_destroyed executable: /usr/bin/file-roller journald_cursor: s=9100fdc21dc44a1796d53a850a238b20;i=11ec9;b=606aba12c28f4b45b749c68ed2ab4226;m=95141754;t=56d3f232367ce;x=cc2505529adf75f kernel: 4.16.11-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 gdk_window_is_destroyed at gdkwindow.c:2320 #1 gtk_get_event_widget at gtkmain.c:2547 #2 gtk_widget_event_internal at gtkwidget.c:7628 #3 gtk_widget_event at gtkwidget.c:7314 #4 propagate_event_up at gtkmain.c:2582 #5 propagate_event at gtkmain.c:2685 #6 gtk_propagate_event at gtkmain.c:2719 #7 egg_tree_multi_drag_button_release_event at ../src/eggtreemultidnd.c:183 Potential duplicate: bug 1273428
Created attachment 1442809 [details] File: backtrace
Created attachment 1442810 [details] File: cgroup
Created attachment 1442811 [details] File: core_backtrace
Created attachment 1442812 [details] File: cpuinfo
Created attachment 1442813 [details] File: dso_list
Created attachment 1442814 [details] File: environ
Created attachment 1442815 [details] File: exploitable
Created attachment 1442816 [details] File: limits
Created attachment 1442817 [details] File: maps
Created attachment 1442818 [details] File: mountinfo
Created attachment 1442819 [details] File: open_fds
Created attachment 1442820 [details] File: proc_pid_status
Similar problem has been detected: Open (not unarchive) two big archives with firefox src code (around 400 MB). reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: file-roller /home/yaroslav/ /firefox_61.0.1+build1.orig.tar.xz crash_function: gdk_window_is_destroyed executable: /usr/bin/file-roller journald_cursor: s=0e76bfa8002b45b6acbe9c1835e4e272;i=46be;b=9258ebd19be04aad8b9d10046910be14;m=29f2cfa97;t=577424a279bbb;x=77a3bc0df1aedd84 kernel: 4.17.14-202.fc28.x86_64 package: file-roller-3.28.1-1.fc28 reason: file-roller killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.