Description of problem:
Version-Release number of selected component:
cmdline: evince /run/user/1000/gvfs/google-drive:host=redhat.com,user=hhan/0B2XP3rPZrWbnN1NSVEFqR3RleGs
runlevel: N 5
Thread no. 1 (4 frames)
#0 window_open_file_copy_progress_cb at ev-window.c:2029
#1 copy_async_progress_in_main at gfile.c:6241
#6 g_main_context_iteration at gmain.c:3990
#7 g_application_run at gapplication.c:2405
Potential duplicate: bug 1418810
Created attachment 1248333 [details]
Created attachment 1248334 [details]
Created attachment 1248335 [details]
Created attachment 1248336 [details]
Created attachment 1248337 [details]
Created attachment 1248338 [details]
Created attachment 1248339 [details]
Created attachment 1248340 [details]
Created attachment 1248341 [details]
Created attachment 1248342 [details]
Created attachment 1248343 [details]
Created attachment 1248344 [details]
Created attachment 1248345 [details]
1. Add google accounts in 'Gnome Online Accounts' and enable 'Use for files'. Then there will be your google drive locations in your gnome file browser.
2. Upload an big pdf file to google drive.
3. Open the pdf file in gnome file browser. Click the close button in pop-up window when loading the file, then close evince. It will reproduce the bug.
The full backtrace:
(gdb) bt full
#0 0x000055582de947b4 in window_open_file_copy_progress_cb (n_bytes=2965504, total_bytes=20599339, ev_window=0x55582fec01d0) at ev-window.c:2029
#1 0x00007f1dd6e696e6 in copy_async_progress_in_main (user_data=user_data@entry=0x7f1da8004a70) at gfile.c:6241
progress = 0x7f1da8004a70
data = <optimized out>
#2 0x00007f1dd69019c7 in g_idle_dispatch (source=0x7f1da8002c30, callback=0x7f1dd6e696d0 <copy_async_progress_in_main>, user_data=0x7f1da8004a70) at gmain.c:5545
again = <optimized out>
#3 0x00007f1dd6904f22 in g_main_dispatch (context=0x55582fe978c0) at gmain.c:3203
dispatch = 0x7f1dd69019b0 <g_idle_dispatch>
prev_source = 0x0
was_in_call = 0
user_data = 0x7f1da8004a70
callback = 0x7f1dd6e696d0 <copy_async_progress_in_main>
cb_funcs = 0x7f1dd6bcd280 <g_source_callback_funcs>
cb_data = 0x7f1da80010c0
need_destroy = <optimized out>
source = 0x7f1da8002c30
current = 0x55582ff05e00
i = 1
#4 0x00007f1dd6904f22 in g_main_context_dispatch (context=context@entry=0x55582fe978c0) at gmain.c:3856
#5 0x00007f1dd69052a0 in g_main_context_iterate (context=context@entry=0x55582fe978c0, block=block@entry=0, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3929
max_priority = 0
timeout = 0
some_ready = 1
nfds = 3
allocated_nfds = 3
fds = <optimized out>
#6 0x00007f1dd690534c in g_main_context_iteration (context=context@entry=0x55582fe978c0, may_block=may_block@entry=0) at gmain.c:3990
retval = <optimized out>
#7 0x00007f1dd6ec5690 in g_application_run (application=0x55582ff7b260 [EvApplication], argc=<optimized out>, argv=0x0) at gapplication.c:2405
arguments = 0x55582ff8ff40
status = 0
context = 0x55582fe978c0
acquired_context = <optimized out>
__func__ = "g_application_run"
#8 0x000055582de7fadb in main (argc=<optimized out>, argv=<optimized out>) at main.c:316
application = 0x55582ff7b260 [EvApplication]
context = <optimized out>
error = 0x0
status = <optimized out>
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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'
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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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
Thank you for reporting this bug and we are sorry it could not be fixed.