Bug#977673: pan: Frequent freeze-ups when using SSL connections

2020-12-20 Thread Vincent Smeets
Hello,

I just got an hit again. I have attached the relevant part of the log
output. The log was generated by the following command to also have the
timestamps:
pan/gui/pan --debug --debug --debug-ssl |& ts '%.T' | tee pan.log

Until 13:50:15, pan was working normally. The window was minimized and
around 13:50:15, my computer was idle and went into suspended mode.

At 14:24:02, I reactivated my computer. It looks like pan wrote out some
QUIT commands to the servers.

At 14:24:09.44* pan is reading some "Bye!" answers.

>From 14:24:09.73* onwards, pan is in a loop and everything is freezing.

Every second, about 71000 lines of debug output is written to the log file.
$ fgrep -c 14:24:10 pan.log.full
71097
$

Regards,
Vincent


Op zo 20 dec. 2020 om 12:16 schreef Vincent Smeets <
vincent.vsme...@gmail.com>:

> Hallo,
>
> No, it doesn't resume. There is also no additional window open for which
> it is waiting.
>
> I don't know how to provoke this situation. I have noticed a couple of
> times after the following steps:
> - I normally read my news.
> - then minimized the window.
> - After an idle time, my computer goes to suspended mode.
> - When I am back and I wake my computer out of suspended mode again.
> - I open pan to read news
> - I click on "Get new headers of subscribed groups".
> - Then I see that pan is freezing and the debug logging constantly shows
> the messages from socket-impl-openssl.cc as shown.
>
> I have investigated socket-impl-openssl.cc a little bit, but I don't know
> how it should work. It looks like set_watch_mode is triggered every time
> for a read, but there is nothing (no data) to read. It sets a new watch and
> that gets triggered directly again.
>
> Regards.
>
> Op za 19 dec. 2020 om 17:40 schreef Dominique Dumont :
>
>> On vendredi 18 décembre 2020 16:30:11 CET you wrote:
>> > I am using pan to connect to the news servers of
>> > news*.open-news-network.org. Some of them are using NTTPS.  I have
>> started
>> > pan with the options "--debug --debug --debug-ssl". After some time,
>> > pan doesn't respond anymore. The output shows a continues stream of the
>> > following debug output. It looks like it is in some loop.
>>
>> Does pan resume after a while ?
>>
>> On my side, I use pan with ssl without problem. I thought it was stalled,
>> but
>> it had popped another windows asking whether the server's certificate
>> should be
>> trusted.
>>
>> HTH
>>
>>
>>


Bug#977673: pan: Frequent freeze-ups when using SSL connections

2020-12-20 Thread Vincent Smeets
And here is the missing attachment. (compressed)

Op zo 20 dec. 2020 om 15:00 schreef Vincent Smeets <
vincent.vsme...@gmail.com>:

> Hello,
>
> I just got an hit again. I have attached the relevant part of the log
> output. The log was generated by the following command to also have the
> timestamps:
> pan/gui/pan --debug --debug --debug-ssl |& ts '%.T' | tee pan.log
>
> Until 13:50:15, pan was working normally. The window was minimized and
> around 13:50:15, my computer was idle and went into suspended mode.
>
> At 14:24:02, I reactivated my computer. It looks like pan wrote out some
> QUIT commands to the servers.
>
> At 14:24:09.44* pan is reading some "Bye!" answers.
>
> From 14:24:09.73* onwards, pan is in a loop and everything is freezing.
>
> Every second, about 71000 lines of debug output is written to the log file.
> $ fgrep -c 14:24:10 pan.log.full
> 71097
> $
>
> Regards,
> Vincent
>
>
> Op zo 20 dec. 2020 om 12:16 schreef Vincent Smeets <
> vincent.vsme...@gmail.com>:
>
>> Hallo,
>>
>> No, it doesn't resume. There is also no additional window open for which
>> it is waiting.
>>
>> I don't know how to provoke this situation. I have noticed a couple of
>> times after the following steps:
>> - I normally read my news.
>> - then minimized the window.
>> - After an idle time, my computer goes to suspended mode.
>> - When I am back and I wake my computer out of suspended mode again.
>> - I open pan to read news
>> - I click on "Get new headers of subscribed groups".
>> - Then I see that pan is freezing and the debug logging constantly shows
>> the messages from socket-impl-openssl.cc as shown.
>>
>> I have investigated socket-impl-openssl.cc a little bit, but I don't know
>> how it should work. It looks like set_watch_mode is triggered every time
>> for a read, but there is nothing (no data) to read. It sets a new watch and
>> that gets triggered directly again.
>>
>> Regards.
>>
>> Op za 19 dec. 2020 om 17:40 schreef Dominique Dumont :
>>
>>> On vendredi 18 décembre 2020 16:30:11 CET you wrote:
>>> > I am using pan to connect to the news servers of
>>> > news*.open-news-network.org. Some of them are using NTTPS.  I have
>>> started
>>> > pan with the options "--debug --debug --debug-ssl". After some time,
>>> > pan doesn't respond anymore. The output shows a continues stream of the
>>> > following debug output. It looks like it is in some loop.
>>>
>>> Does pan resume after a while ?
>>>
>>> On my side, I use pan with ssl without problem. I thought it was
>>> stalled, but
>>> it had popped another windows asking whether the server's certificate
>>> should be
>>> trusted.
>>>
>>> HTH
>>>
>>>
>>>


pan.log.xz
Description: application/xz


Bug#977673: pan: Frequent freeze-ups when using SSL connections

2020-12-20 Thread Vincent Smeets
Hallo,

No, it doesn't resume. There is also no additional window open for which it
is waiting.

I don't know how to provoke this situation. I have noticed a couple of
times after the following steps:
- I normally read my news.
- then minimized the window.
- After an idle time, my computer goes to suspended mode.
- When I am back and I wake my computer out of suspended mode again.
- I open pan to read news
- I click on "Get new headers of subscribed groups".
- Then I see that pan is freezing and the debug logging constantly shows
the messages from socket-impl-openssl.cc as shown.

I have investigated socket-impl-openssl.cc a little bit, but I don't know
how it should work. It looks like set_watch_mode is triggered every time
for a read, but there is nothing (no data) to read. It sets a new watch and
that gets triggered directly again.

Regards.

Op za 19 dec. 2020 om 17:40 schreef Dominique Dumont :

> On vendredi 18 décembre 2020 16:30:11 CET you wrote:
> > I am using pan to connect to the news servers of
> > news*.open-news-network.org. Some of them are using NTTPS.  I have
> started
> > pan with the options "--debug --debug --debug-ssl". After some time,
> > pan doesn't respond anymore. The output shows a continues stream of the
> > following debug output. It looks like it is in some loop.
>
> Does pan resume after a while ?
>
> On my side, I use pan with ssl without problem. I thought it was stalled,
> but
> it had popped another windows asking whether the server's certificate
> should be
> trusted.
>
> HTH
>
>
>


Bug#977673: pan: Frequent freeze-ups when using SSL connections

2020-12-19 Thread Dominique Dumont
On vendredi 18 décembre 2020 16:30:11 CET you wrote:
> I am using pan to connect to the news servers of
> news*.open-news-network.org. Some of them are using NTTPS.  I have started
> pan with the options "--debug --debug --debug-ssl". After some time,
> pan doesn't respond anymore. The output shows a continues stream of the
> following debug output. It looks like it is in some loop.

Does pan resume after a while ?

On my side, I use pan with ssl without problem. I thought it was stalled, but 
it had popped another windows asking whether the server's certificate should be 
trusted.

HTH



Bug#977673: pan: Frequent freeze-ups when using SSL connections

2020-12-18 Thread Vincent Smeets
Package: pan
Version: 0.146-2
Severity: normal
Tags: upstream
X-Debbugs-Cc: vincent.vsme...@gmail.com

this bug is also reported upstream as 
https://gitlab.gnome.org/GNOME/pan/-/issues/30

I am using pan to connect to the news servers of
news*.open-news-network.org. Some of them are using NTTPS.  I have started
pan with the options "--debug --debug --debug-ssl". After some time,
pan doesn't respond anymore. The output shows a continues stream of the
following debug output. It looks like it is in some loop.

(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode READ: _tag_watch is 
now 869250
(socket-impl-openssl.cc:743:gio_func) gio_func: sock 0x7f55840051a0, channel 
0x7f5584006600, cond IN
(socket-impl-openssl.cc:757:set_watch_mode) socket 0x7f5594001360 calling 
set_watch_mode 2; _channel is 0x7f5594001e40
(socket-impl-openssl.cc:766:set_watch_mode) channel 0x7f5594001e40 setting mode 
**IGNORE**
(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode IGNORE: _tag_watch 
is now 0
(socket-impl-openssl.cc:757:set_watch_mode) socket 0x7f5594001360 calling 
set_watch_mode 0; _channel is 0x7f5594001e40
(socket-impl-openssl.cc:770:set_watch_mode) channel 0x7f5594001e40 setting mode 
read
(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode READ: _tag_watch is 
now 869252
(socket-impl-openssl.cc:743:gio_func) gio_func: sock 0x7f5594001360, channel 
0x7f5594001e40, cond IN
(socket-impl-openssl.cc:757:set_watch_mode) socket 0x7f558c018c40 calling 
set_watch_mode 2; _channel is 0x7f558c016020
(socket-impl-openssl.cc:766:set_watch_mode) channel 0x7f558c016020 setting mode 
**IGNORE**
(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode IGNORE: _tag_watch 
is now 0
(socket-impl-openssl.cc:757:set_watch_mode) socket 0x7f558c018c40 calling 
set_watch_mode 0; _channel is 0x7f558c016020
(socket-impl-openssl.cc:770:set_watch_mode) channel 0x7f558c016020 setting mode 
read
(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode READ: _tag_watch is 
now 869254
(socket-impl-openssl.cc:743:gio_func) gio_func: sock 0x7f558c018c40, channel 
0x7f558c016020, cond IN
(socket-impl-openssl.cc:757:set_watch_mode) socket 0x7f558c001360 calling 
set_watch_mode 2; _channel is 0x7f558c001820
(socket-impl-openssl.cc:766:set_watch_mode) channel 0x7f558c001820 setting mode 
**IGNORE**
(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode IGNORE: _tag_watch 
is now 0
(socket-impl-openssl.cc:757:set_watch_mode) socket 0x7f558c001360 calling 
set_watch_mode 0; _channel is 0x7f558c001820
(socket-impl-openssl.cc:770:set_watch_mode) channel 0x7f558c001820 setting mode 
read
(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode READ: _tag_watch is 
now 869256
(socket-impl-openssl.cc:743:gio_func) gio_func: sock 0x7f558c001360, channel 
0x7f558c001820, cond IN
(socket-impl-openssl.cc:757:set_watch_mode) socket 0x7f55840051a0 calling 
set_watch_mode 2; _channel is 0x7f5584006600
(socket-impl-openssl.cc:766:set_watch_mode) channel 0x7f5584006600 setting mode 
**IGNORE**
(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode IGNORE: _tag_watch 
is now 0
(socket-impl-openssl.cc:757:set_watch_mode) socket 0x7f55840051a0 calling 
set_watch_mode 0; _channel is 0x7f5584006600
(socket-impl-openssl.cc:770:set_watch_mode) channel 0x7f5584006600 setting mode 
read
(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode READ: _tag_watch is 
now 869258
(socket-impl-openssl.cc:743:gio_func) gio_func: sock 0x7f55840051a0, channel 
0x7f5584006600, cond IN
(socket-impl-openssl.cc:757:set_watch_mode) socket 0x7f5594001360 calling 
set_watch_mode 2; _channel is 0x7f5594001e40
(socket-impl-openssl.cc:766:set_watch_mode) channel 0x7f5594001e40 setting mode 
**IGNORE**
(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode IGNORE: _tag_watch 
is now 0
(socket-impl-openssl.cc:757:set_watch_mode) socket 0x7f5594001360 calling 
set_watch_mode 0; _channel is 0x7f5594001e40
(socket-impl-openssl.cc:770:set_watch_mode) channel 0x7f5594001e40 setting mode 
read
(socket-impl-openssl.cc:786:set_watch_mode) set_watch_mode READ: _tag_watch is 
now 869260



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pan depends on:
ii  gnome-keyring   3.36.0-1
ii  gnupg   2.2.20-1
ii  libc6   2.31-5
ii  libcairo2   1.16.0-4
ii  libgcc-s1   10.2.1-1
ii  libgcr-base-3-1 3.38.0-1
ii  libgdk-pixbuf2.0-0  2.40.2-2
ii  libglib2.0-02.66.3-2
ii  libgmime-3.0-0  3.2.7-1
ii  libgnutls30 3.6.15-4
ii  libgtk-3-0  3.24.24-1
ii  libnotify4  0.7.9-2
ii  libpango-1.0-0  1.46.2-3
ii  libsecre