After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343347 - Evince fails to open PDF files in FTP locations
Evince fails to open PDF files in FTP locations
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: general
0.5.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-30 00:27 UTC by Sebastien Bacher
Modified: 2006-06-01 14:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sebastien Bacher 2006-05-30 00:27:56 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/evince/+bug/47201

"I've tried to open a PDF file located on an FTP server and Evince stalls when opening the file. I can see that the file is never downloaded from the server.

I found a file to test with at ftp://www.tug.org//tex-archive/dviware/dvipdfm/dvipdfm.pdf

In my tests on Dapper, evince downloaded the file nearly every time out of the 20 - 30 I tried, but in about 3 cases it failed. It crashed once with a BadAtom message, another it just hung and needed to force quit and another time it never displayed a login dialog and ethereal showed me it never got past ACKing the 220 server message.

john@seiza:~$ evince ftp://www.tug.org//tex-archive/dviware/dvipdfm/dvipdfm.pdf
Xlib: unexpected async reply (sequence 0x114)!
The program 'evince' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 2408 error_code 5 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

I wouldn't consider this a confirmation myself. More people should test this.

just run: evince ftp://www.tug.org//tex-archive/dviware/dvipdfm/dvipdfm.pdf"
Comment 1 Nickolay V. Shmyrev 2006-06-01 06:00:21 UTC
Here is the part of stacktrace. It looks like some bug in libgnomeui is occured. We need to investigate if further.

  • #1 pthread_cond_wait
    from /lib/libpthread.so.0
  • #2 g_main_context_wait
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #2 g_main_context_wait
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #4 gtk_dialog_run
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gnome_password_dialog_run_and_block
    from /usr/lib/libgnomeui-2.so.0
  • #6 gnome_authentication_manager_push_sync
    from /usr/lib/libgnomeui-2.so.0
  • #7 gnome_vfs_module_callback_invoke
    from /usr/lib/libgnomevfs-2.so.0
  • #4 gtk_dialog_run
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gnome_password_dialog_run_and_block
    from /usr/lib/libgnomeui-2.so.0
  • #6 gnome_authentication_manager_push_sync
    from /usr/lib/libgnomeui-2.so.0
  • #7 gnome_vfs_module_callback_invoke
    from /usr/lib/libgnomevfs-2.so.0

Comment 2 Nickolay V. Shmyrev 2006-06-01 13:41:28 UTC
Looks like a duplicate

*** This bug has been marked as a duplicate of 335688 ***
Comment 3 Nickolay V. Shmyrev 2006-06-01 14:18:20 UTC
I found the problem - missing gdk_threads_init. Rather strange issue and it's unrelated to 335688. Reopening.
Comment 4 Nickolay V. Shmyrev 2006-06-01 14:45:19 UTC
This bug should be fixed, I've also filed bug 343601 gnome_authentication_manager_init should init gdk threads