Bug 1634038

Summary: [abrt] Thunar: poll_for_event(): thunar killed by SIGABRT
Product: [Fedora] Fedora Reporter: deadgnom32
Component: ThunarAssignee: Mukundan Ragavan <nonamedotc>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: dhiru, kevin, nonamedotc, oleg-sz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b781a622e04638dfce3b69c4918b7a7cc7e718c9
Whiteboard: abrt_hash:6f5866322e403f1b244fe8b3dffd55141b6d9fb4;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:31:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description deadgnom32 2018-09-28 14:07:40 UTC 
Description of problem:
I Dragged some *.pdf and *.pptx files from one thunar window into another, then I tried to create a new folder using the "another" window, at this point the application crashed.

Version-Release number of selected component:
Thunar-1.6.15-1.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        Thunar --daemon
crash_function: poll_for_event
executable:     /usr/bin/thunar
journald_cursor: s=7a58bd34b4d54ced98e241216ba1c0b3;i=159a;b=4001b8bbdd534be999ee7f1e928bc8ed;m=626cc5b0f;t=576eecce6a326;x=eca93301f56a3f2e
kernel:         4.18.9-200.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 deadgnom32 2018-09-28 14:07:45 UTC 
Created attachment 1488094 [details]
File: backtrace
Comment 2 deadgnom32 2018-09-28 14:07:47 UTC 
Created attachment 1488095 [details]
File: cgroup
Comment 3 deadgnom32 2018-09-28 14:07:48 UTC 
Created attachment 1488096 [details]
File: core_backtrace
Comment 4 deadgnom32 2018-09-28 14:07:49 UTC 
Created attachment 1488097 [details]
File: cpuinfo
Comment 5 deadgnom32 2018-09-28 14:07:51 UTC 
Created attachment 1488098 [details]
File: dso_list
Comment 6 deadgnom32 2018-09-28 14:07:52 UTC 
Created attachment 1488099 [details]
File: environ
Comment 7 deadgnom32 2018-09-28 14:07:53 UTC 
Created attachment 1488100 [details]
File: limits
Comment 8 deadgnom32 2018-09-28 14:07:55 UTC 
Created attachment 1488101 [details]
File: maps
Comment 9 deadgnom32 2018-09-28 14:07:56 UTC 
Created attachment 1488102 [details]
File: mountinfo
Comment 10 deadgnom32 2018-09-28 14:07:58 UTC 
Created attachment 1488103 [details]
File: open_fds
Comment 11 deadgnom32 2018-09-28 14:07:59 UTC 
Created attachment 1488104 [details]
File: proc_pid_status
Comment 12 Mukundan Ragavan 2018-09-29 00:38:20 UTC 
Did you notice the application crash or was it only a ABRT prompt?
Comment 13 deadgnom32 2019-01-02 15:36:59 UTC 
(In reply to Mukundan Ragavan from comment #12)
> Did you notice the application crash or was it only a ABRT prompt?

It was long ago. but as I remember, there was no prompt. all thunar windows just vanished and then, yes there was a prompt from the system stating that the application has crashed.
Comment 14 Ben Cotton 2019-05-02 20:05:01 UTC 
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.
Comment 15 Ben Cotton 2019-05-28 23:31:12 UTC 
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.