Bug 1541842 - [abrt] gvfs: g_task_get_task_data(): gvfs-udisks2-volume-monitor killed by SIGSEGV
Summary: [abrt] gvfs: g_task_get_task_data(): gvfs-udisks2-volume-monitor killed by SI...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ondrej Holy
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:598a7273e01c78602fceb309c26...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-05 03:57 UTC by David Reddick
Modified: 2019-05-28 19:34 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 19:34:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (16.07 KB, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: cgroup (367 bytes, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: core_backtrace (8.81 KB, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: cpuinfo (1.45 KB, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: dso_list (5.03 KB, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: environ (1.55 KB, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: exploitable (82 bytes, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: limits (1.29 KB, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: maps (19.12 KB, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: mountinfo (3.72 KB, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: open_fds (850 bytes, text/plain)
2018-02-05 03:57 UTC, David Reddick
no flags Details
File: proc_pid_status (1.27 KB, text/plain)
2018-02-05 03:58 UTC, David Reddick
no flags Details

Description David Reddick 2018-02-05 03:57:43 UTC
Description of problem:
Trying to mount an encrypted drive.

Version-Release number of selected component:
gvfs-1.35.3-2.fc28

Additional info:
reporter:       libreport-2.9.3
backtrace_rating: 3
cmdline:        /usr/libexec/gvfs-udisks2-volume-monitor
crash_function: g_task_get_task_data
executable:     /usr/libexec/gvfs-udisks2-volume-monitor
journald_cursor: s=6c7b7214e2f14af7bcfc607b8a321908;i=8bf4;b=1a65dd48841d4c2482edd566dac0762c;m=56f41198;t=5646edbf0a37f;x=b08c82bce3867ab8
kernel:         4.15.0-1.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 g_task_get_task_data at gtask.c:1020
 #1 on_udisks_client_changed at gvfsudisks2volume.c:614
 #2 ffi_call_unix64 at ../src/x86/unix64.S:76
 #3 ffi_call at ../src/x86/ffi64.c:525
 #4 g_cclosure_marshal_generic at gclosure.c:1490
 #9 ??
 #10 ??
 #16 g_vfs_proxy_volume_monitor_daemon_main at gvfsproxyvolumemonitordaemon.c:2013
 #18 _start

Comment 1 David Reddick 2018-02-05 03:57:47 UTC
Created attachment 1391284 [details]
File: backtrace

Comment 2 David Reddick 2018-02-05 03:57:48 UTC
Created attachment 1391285 [details]
File: cgroup

Comment 3 David Reddick 2018-02-05 03:57:49 UTC
Created attachment 1391286 [details]
File: core_backtrace

Comment 4 David Reddick 2018-02-05 03:57:50 UTC
Created attachment 1391287 [details]
File: cpuinfo

Comment 5 David Reddick 2018-02-05 03:57:51 UTC
Created attachment 1391288 [details]
File: dso_list

Comment 6 David Reddick 2018-02-05 03:57:52 UTC
Created attachment 1391289 [details]
File: environ

Comment 7 David Reddick 2018-02-05 03:57:53 UTC
Created attachment 1391290 [details]
File: exploitable

Comment 8 David Reddick 2018-02-05 03:57:53 UTC
Created attachment 1391291 [details]
File: limits

Comment 9 David Reddick 2018-02-05 03:57:58 UTC
Created attachment 1391292 [details]
File: maps

Comment 10 David Reddick 2018-02-05 03:57:59 UTC
Created attachment 1391293 [details]
File: mountinfo

Comment 11 David Reddick 2018-02-05 03:57:59 UTC
Created attachment 1391294 [details]
File: open_fds

Comment 12 David Reddick 2018-02-05 03:58:03 UTC
Created attachment 1391295 [details]
File: proc_pid_status

Comment 13 Fedora End Of Life 2018-02-20 15:29:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 14 Ben Cotton 2019-05-02 22:05:03 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 19:34:16 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.


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