eog fails to open png: Failed to register: Timeout was reached

Bug #1721401 reported by Gerrit Holl
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
eog (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

eog fails to open PNG file. After about 25 seconds, it gives up and says:

Failed to register: Timeout was reached

You can find the relevant image at:

https://www.dropbox.com/s/psrm3wj1n480ocx/FIDUCEO_FCDR_L1C_HIRS2_noaa14_20000101144729_20000101162929_easy_v0.7_fv0.4.png?dl=0

Ubuntu 16.04.2 LTS, GNOME Image Viewer 3.18.2.

I expect it to display the image. Instead it fails with the above message.

Image Magicks "display" utility shows the image fine.

Revision history for this message
tomdean (tomdean) wrote :

I have this problem.

Ubuntu 18.04.3
4.15.0-58-generic kernel
X and TWM. Some gnome things are running...

eog image1.jpg takes 27 seconds to open a window.

Sometimes, I get 'Failed to register: Timeout was reached' message and eog is terminated.

This happens when I have TWM as the desktop. With gdm3, this does not seem to happen.

Revision history for this message
tomdean (tomdean) wrote :

I have another 18.04.3 installation on this computer, on a WD5000, that also uses TWM. The 27 second display does not happen. On that system, I notice a difference in time for the very first execution of eog to the next. The shared libs seem to have stayed loaded inbetween.

Changed in eog (Ubuntu):
status: New → Confirmed
Revision history for this message
tomdean (tomdean) wrote :

The problems appears to be arts of gnome left over from ahanging to TWM. The following eliminated the problem.

[code]
   sudo apt remove --purge gnome-calendar
    sudo apt remove --purge libgnome-todo
    sudo apt remove --purge gnome-mahjongg gnome-mines gnome-sudoku
    sudo apt purge gnome-weather
    sudo apt remove --purge gnome-accessibility-themes gnome-themes-extra:amd64 gnome-themes-extra-data
    sudo apt remove --purge language-pack-gnome-en language-pack-gnome-en-base language-selector-gnome
    sudo apt remove --purge gnome-session-bin gnome-session-canberra gnome-session-common
    sudo apt remove --purge thunderbird-gnome-support pinentry-gnome3 network-manager-pptp-gnome network-manager-gnome
    sudo apt remove --purge libreoffice-gnome libsoup-gnome2.4-1:amd64 nautilus-extension-gnome-terminal policykit-1-gnome
    sudo apt remove --purge libgnome-autoar-0-0:amd64 libgnome-games-support-common libgnome-menu-3-0:amd64 \
             libgnomekbd-common libpam-gnome-keyring:amd64
    sudo apt remove --purge gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-initial-setup
    sudo apt remove --purge gnome-keyring-pkcs11:amd64 gnome-menus gnome-settings-daemon-schemas gnome-video-effects
    sudo apt remove --purge gnome-shell-common gnome-shell-extension-appindicator gnome-shell-extension-ubuntu-dock
    sudo apt remove --purge gnome-software gnome-software-common gnome-terminal-data gnome-todo-common

    The above remove eog
    sudo apt install eog
[/code]

Revision history for this message
dan hitt (dan-hitt) wrote :

I have this problem as well, and it just started tonight (2021-05-25) on my xubuntu 20.04 system. I have another xubuntu 20.04 machine on which the problem does not occur. So, this may be transient, or mostly unrelated to eog.

Revision history for this message
dan hitt (dan-hitt) wrote :

Just for reference, i ran into this problem once again tonight (2021-07-30) on one of my xubuntu 20.04 systems. In this particular case it was due to running another copy of eog under gdb (which somehow made it out-of-reach to killall, and which i had forgotten about). I don't think this is what happened on 2021-05-25, because i didn't have the need to really hack into eog at that time.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.