In random intervals, okular will hang for minutes. I found that it's
due to it waiting on a socket:
poll([{fd=15, events=POLLIN|POLLOUT}], 1, 250) = 0 (Timeout)
which goes on for a long time.
According to lsof, it's trying to talk to the print server:
okular 27987 madduck 15u IPv4 3586963 0t0 TCP 192.168.43.164:35068->192.168.14.2:ipp (SYN_SENT)
which is unreachable, for obvious reasons (different RFC1918 net).
It may be that this only happens when I start okular in the
192.168.14.0/24 network, then suspend the laptop and move elsewhere.
I have not really had the chance to isolate this.
However, I don't think okular should be talking to the print server
anyway, that's cups' job, and cups properly handles disconnections
and roaming between network, unreachable printers and other
exceptions. Okular should not try to do itself what others are
already doing, especially not if it doesn't end up doing it
properly.
tags 740707 upstream confirmed thanks Martin: I'm sending the standard reply template for this cases, but I'll possibly get to report it upstream myself in some time, but I don't know how much time it will take me, as I can only reproduce this on $job. If you can report it yourself upstream, the better. Thanks, Lisandro. Hello, the bug you reported is a KDE bug. Please report it via Help -> Report bug... menu item of the respective application or by visiting https://bugs.kde.org/ and following instructions to report a new bug. Debian Qt/KDE maintainers do not have resources to deal with non Debian-specific bugs and therefore it is unlikely that your bug will be solved if you do not report it to KDE developers directly (unless it is/has been reported by somebody else). Whenever you open a bug report on the KDE bug tracking system, or you find that the bug has been already reported on it, you can couple both this Debian bug and the KDE bug together by sending the mail with the text below to control@bugs.debian.org (replace KDE-BUG-URL with the address of the bug report on https://bugs.kde.org/)------------[ copy this ]------------ forwarded 740707 KDE-BUG-URL thanks ------------[ copy this ]------------ Thank you, -- 11: En Word, como se hace para pasar al proximo renglon si se alcanzo el extramo derecho de la hoja. * Se reinicia la maquina, se abre el Guord, se va a archivo, Nuevo renglon, Preferencias, Abajo del otro renglon, Poner el cursor al proncipio del nuevo renglon, Elegir misma letra que el anterior, respetar la pagina anterior, respetar el margen anterior, respetar numeracion de pagina, comenzar a escribir, click en "Ok deseo comenzar a escribir", click en "Esta seguro que desea comenzar a Escribir", click en "Ultima advertencia", click en "Comience a escribir" Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
tags 740707 upstream confirmed thanks Martin: I'm sending the standard reply template for this cases, but I'll possibly get to report it upstream myself in some time, but I don't know how much time it will take me, as I can only reproduce this on $job. If you can report it yourself upstream, the better. Thanks, Lisandro. Hello, the bug you reported is a KDE bug. Please report it via Help -> Report bug... menu item of the respective application or by visiting https://bugs.kde.org/ and following instructions to report a new bug. Debian Qt/KDE maintainers do not have resources to deal with non Debian-specific bugs and therefore it is unlikely that your bug will be solved if you do not report it to KDE developers directly (unless it is/has been reported by somebody else). Whenever you open a bug report on the KDE bug tracking system, or you find that the bug has been already reported on it, you can couple both this Debian bug and the KDE bug together by sending the mail with the text below to control@bugs.debian.org (replace KDE-BUG-URL with the address of the bug report on https://bugs.kde.org/)------------[ copy this ]------------ forwarded 740707 KDE-BUG-URL thanks ------------[ copy this ]------------ Thank you, -- 11: En Word, como se hace para pasar al proximo renglon si se alcanzo el extramo derecho de la hoja. * Se reinicia la maquina, se abre el Guord, se va a archivo, Nuevo renglon, Preferencias, Abajo del otro renglon, Poner el cursor al proncipio del nuevo renglon, Elegir misma letra que el anterior, respetar la pagina anterior, respetar el margen anterior, respetar numeracion de pagina, comenzar a escribir, click en "Ok deseo comenzar a escribir", click en "Esta seguro que desea comenzar a Escribir", click en "Ultima advertencia", click en "Comience a escribir" Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
also sprach Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com> [2014-03-04 15:58 +0100]: Thanks. My account seems to be gone, which is a shame. I have signed up for a new one, but the confirmation is getting greylisted somewhere, it seems. We'll see. I would prefer if you filed it upstream, not because I don't want to do the work, but because you know KDE much better. I only use okular, nothing else.
also sprach Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com> [2014-03-04 15:58 +0100]: Thanks. My account seems to be gone, which is a shame. I have signed up for a new one, but the confirmation is getting greylisted somewhere, it seems. We'll see. I would prefer if you filed it upstream, not because I don't want to do the work, but because you know KDE much better. I only use okular, nothing else.
also sprach Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com> [2014-03-04 15:58 +0100]: I assume you didn't have time to do this. I can report this upstream, but I would really like to know which package is at fault. Should I file this against okular? Isn't it much more likely that the problem is deep down in a KDE or Qt library?
[2014-03-04 15:58 +0100]: You assumption is right :( I saw that you found an already filled bug and moreover upstream seems to know the cause. Now I wonder if this will ever get solved or just left out until okular is ported to qt5 :-/
Dear Maintainer, In my case, okular did not really freeze, but it showed me a grey screen for a long time (> 15 seconds) when I entered full-screen mode. This depends on the printer configuration. When the network is disabled, it does not occur, i.e. okular enters full-screen model quickly. It seems this behaviour started when some printers were automatically configured that are now unavailable. Now I discovered another case (different default network printer) where it showed me the grey screen for more than 1 minute, so I assume it would never return. Okular stopped to disbehave in this way when I selected a certain printer as default that is also not available. However, this "good" printer differs from the other unavailable printers, as its configuration opens immediately in the CUPS configuration, so CUPS obviously knows it's not available and does not try to talk to it. Hope this is helpful for someone in a similar situation... Cheers, Johannes