Anonymous wrote:

> On 3/13/23 14:12, Retro Guy wrote:
>> Anonymous wrote:
>>
>> I use sylpheed as a client, and have tested quite a few others without
>> problems.
>>

> Is sylpheed stable for you? I tested claws and I like the interface but
> it crashes. On occasion it randomly crashes and exits when I click to
> open a message.

> I know the clients are related. I need to find something that does not
> crash.

I use both at times. I find claws-mail blocks doing anything while it's
checking for messages and can sometimes (seem to) hang if there's a problem
connecting. The pop up window telling me what's wrong does not pop up, just
ends up in the task bar with the main icon.

sylpheed seems to work a bit better, so I stick with it for now.

I still miss the old OS/2 News Reader!

--
Retro Guy

On 3/14/23 8:46 AM, Anonymous wrote:
> I've been down this road many times. I don't waste my time reporting
> bugs when the software doesn't have atomic crash reporting output.

It's up to you, but I encourage people to still report such issues as it
provides a data point. Once enough similar data points are collected,
hopefully someone will think "there's a problem here, we should dig
deeper even though we don't have as much data as we want".

--
Grant. . . .
unix || die

On 3/14/23 12:59, Grant Taylor wrote:
> On 3/14/23 8:46 AM, Anonymous wrote:
>> I've been down this road many times. I don't waste my time reporting
>> bugs when the software doesn't have atomic crash reporting output.
>
> It's up to you, but I encourage people to still report such issues as it
> provides a data point.  Once enough similar data points are collected,
> hopefully someone will think "there's a problem here, we should dig
> deeper even though we don't have as much data as we want".

You tend to look on the bright side of things and hold out a hopeful
outlook. I like your positivity. More of it should abound.

On the topic, perhaps Thunderbird is a good option. It is quite stable.
The maintainers have ramped up new development initiatives to modernize
it from the ground up.

--
NightBulb | https://blog.nightbulb.net | Flip the night switch.
How to get ahead in life:
Judaism: circumcision; Christianism: lobotomy; Islam: scimitar;
Democracy: guillotine; Evolution: brainwash; Atheism: K-12.

On 3/14/2023 10:46 AM, Anonymous wrote:
> On 3/14/23 02:24, Marco Moock wrote:
>> Am 13.03.2023 um 18:26:34 Uhr schrieb Anonymous:
>>
>>> Is sylpheed stable for you? I tested claws and I like the interface
>>> but it crashes. On occasion it randomly crashes and exits when I
>>> click to open a message.
>>
>> Please report such bugs.
>> https://www.thewildbeast.co.uk/claws-mail/bugzilla/index.cgi
>>
>> This is the only way they can be fixed.
>>
>
> There is no error output to report. It just crashes with no output and writes nothing to the log. The maintainer will say:
>
> "not enough information to troubleshoot"
>
> "not able to replicate"
>
> "ticket closed"
>
> I've been down this road many times. I don't waste my time reporting bugs when the software doesn't have atomic crash reporting output.

Do they provide a "recipe for debug" ?
Like how to attach gdb and collect output ?

https://users.claws-mail.narkive.com/rsb4HqOS/bug-2361-new-claws-crashes-after-pgp-check

A package in a distro, may be compiled -O2 or -O3 and not have
symbols in it. It needs to be compiled -g so that it has subroutine names
and line numbers in crashes. (If you make shit software like I do,
then you should always package -g so the environment is ready for the
crashes :-) )

1) Use the command in your package manager, to "pull source".
Ubuntu is a good place to do this, because there is the
release tarball, two patch files, and the automation applies
the patches to the tarball for you. Debian might not have the patches
in theirs.

You are left with a build directory that is ready to go.
It might be as simple as

./configure and then "make".

None of these require "sudo", unless you "make install" and you are NOT doing that.

apt search claws # Get the package name

cd ~/Downloads
apt-get source claws-mail # Use the package name, automation prepares your meal for you

cd claws-mail # Enter your new build directory ~/Downloads/claws-mail

./configure # There are a million ways to make stuff. This is just one way.
make -n # Make, dry run, see what it plans to do.
make # Compile the software.

To compile software, things like

sudo apt install build-essential # GNU tool chain

may provide some of the tools needed. Again, there are lots of
tool flows, and build-essential does not grease every rail for you.
Build-essential may have already been installed, the last time your
kernel got updated.

2) The compiler flags should be changed from -O2 or -O3 ("highly optimized")
to -g (add debug symbols, subroutine names, line numbers). The code is
slower, but the crash dump is richer. This is, after all, why you are building
this package for yourself, to make it debuggable.

3) As long as the version of the software, is not much different
than the /usr/bin/progname you're currently using, you can just
launch the debug version, right from your build tree. You don't have to
"sudo make install" as that will just make a mess.

There are endless issues with debug, and I'm not all that good at it.
And this is just a very basic description of a start at it. You can then
use gdb (GNU debugger) and attach to the executable and collect
some info.

If you open a Terminal, and do

cd builddir/bin
./claws-mail

then the stdout and stderr of the program, dump to terminal. If
the program has anything to say, now it has a place to say it.

Not many modern programs benefit from a "Terminal launch",
but we can always hope for a cookie for ourselves for trying :-)

When a program is launched from your Desktop menu, the stderr and
stdout go into "outer space" and are useless. When you terminal-launch
an executable, there is a small chance it will write some output for you.

You can also terminal-launch gdb, or, you can fork the executable
and attach gdb

cd builddir/bin
./claws-mail & # non-blocking startup

ps aguwwwx | grep claws # determine the process ID or PID value

gdb -p <pidnumber> # attach to a running process
# Now, do the graphical operation that crashes it.

*******

These are the kind of topics a good development team will
write up for you, so that you can help them, and they can help you.

I only wrote the above, so you can use bits if it in Google Searches.

# Oh, my

https://www.claws-mail.org/faq/index.php/Debugging_Claws

Debug reports have a "high bar" and the developers can be quite
demanding. But don't give up. If you expect to have software,
SOMEBODY has to contribute to the effort.

Paul

On 3/14/23 12:34 PM, NightBulb wrote:
> You tend to look on the bright side of things and hold out a hopeful
> outlook. I like your positivity. More of it should abound.

It's not always easy.

I learned a long time ago that if I strive for better, I likely won't
reach what I'm striving for, but I will end up somewhere better than I
am now. So, I strive for better and am grateful for some better.

I encourage others to do similar.

> On the topic, perhaps Thunderbird is a good option. It is quite stable.
> The maintainers have ramped up new development initiatives to modernize
> it from the ground up.

I'm still running an old version of Thunderbird. Text is text and old
things still display text just fine.

I have concerns and unknowns about contemporary Thunderbird.

--
Grant. . . .
unix || die

Am 14.03.2023 um 09:46:18 Uhr schrieb Anonymous:

> There is no error output to report. It just crashes with no output
> and writes nothing to the log. The maintainer will say:

Does it write to stdout?
Maybe use debug symbols and backtrace. The developer will instruct you
how to do this. He also did that when I reported a bug.

On 14 Mar 2023, Anonymous <anonymous@anonymous.invalid> posted some
news:tuq1bh$76h$1@news.cyber23.de:

> On 3/14/23 02:24, Marco Moock wrote:
>> Am 13.03.2023 um 18:26:34 Uhr schrieb Anonymous:
>>
>>> Is sylpheed stable for you? I tested claws and I like the interface
>>> but it crashes. On occasion it randomly crashes and exits when I
>>> click to open a message.
>>
>> Please report such bugs.
>> https://www.thewildbeast.co.uk/claws-mail/bugzilla/index.cgi
>>
>> This is the only way they can be fixed.
>>
>
> There is no error output to report. It just crashes with no output and
> writes nothing to the log. The maintainer will say:
>
> "not enough information to troubleshoot"
>
> "not able to replicate"
>
> "ticket closed"
>
> I've been down this road many times. I don't waste my time reporting
> bugs when the software doesn't have atomic crash reporting output.

Go into the .ini file and add the following:

CaptureDefectiveUserData=Yes

On 3/13/23 16:23, Jack wrote:
>
>> On 12/03/2023 17:35, Marco Moock wrote:
>>> Am 11.03.2023 um 21:57:51 Uhr schrieb Retro Guy:
>>>
>>>> To answer your other questions, news.novabbs.com:119 carries most if
>>>> not all text newsgroups, which you can check with 'list' command.
>>> No, not all.
>>> Foreign hierarchies like de.* don't seem to be available.
>>>
>> Some of us don't speak nor understand Germans so we have not paid much
>> attention to foreign hierarchy. All we know is that Uwe Seeler was a
>> German Footballer who died in July 2022 at the age of 85.
>>
>> Have you tried this link:
>>
>> <http://www.open-news-network.org/>
>>
>> You can register for a free account if you can read German.
>>
>> https://contact.mainsite.tk
>
> WE DON'T NEED SERVERS REQUIRING REGISTRATION. PERIOD.

WELL WE DO. SO THERE. EXCLAMATION MARK!

--

nerd suprema.c

Am 08.01.2024 um 09:21:13 Uhr schrieb a a:

> Ho to visit rocksolid.* groups ?

Either us an NNTP-Server like i2pn2.org with a newsreader or:

https://news.novabbs.org/rocksolid/
https://news.novabbs.org/rocksolid/thread.php?group=rocksolid.shared.encryption
Those groups are the rocksolid groups.

On Mon, 8 Jan 2024 13:44:26 -0800 (PST), a a <manta103g@gmail.com> wrote:
>Every time I send a new message via Usenet Google Grops
>and click
>Post message
>Google redirects to Captcha

45 days and problem solved . . .

On Mon, 8 Jan 2024 15:50:57 -0800 (PST), a a <manta103g@gmail.com> wrote:
>On Monday 8 January 2024 at 23:15:04 UTC+1, D wrote:
>> On Mon, 8 Jan 2024 13:44:26 -0800 (PST), a a <mant...@gmail.com> wrote:
>> >Every time I send a new message via Usenet Google Grops
>> >and click
>> >Post message
>> >Google redirects to Captcha
>> 45 days and problem solved . . .
>
>Captcha is not a problem
>but you need to wait 5-10 sec after you press
>Post message
>before clicking Captcha
>since otherwise Captcha enters never ending mode
>and message is lost forever
>There is another problem and test messages
>from
>https://www.novabbs.com/interests/overboard.php?thisgroup=soc.culture.polish
>don't get delivered to
>https://groups.google.com/g/soc.culture.polish/
>and otherwise
>I was asked to help my friends but cannot find a solution to the above problem
>Are Usenet Google Groups really cut off from the Usenet servers ?

45 days until 22 february . . .

Am 08.01.2024 um 13:44:26 Uhr schrieb a a:

> If I visit
> https://news.novabbs.org/rocksolid/
> and select the first newsgroup:
> "Encryption

Those are just descriptions.
It seems that there is no hierarchy-based list, only topic-based.

https://news.novabbs.org/computers/

Is the same, but the names are the group names.

> I sent test message from
> https://www.novabbs.com
>
> not delivered to Usenet Google Groups

Which group?
In rocksolid you can tick the box left of the subject to see all
headers.
Tell use the content of Message-ID.

Google doesn't provide rocksolid.*, so that group won't show up there,
but is available on eternal-september.

> and my message from Usenet Google Group gets not delivered to
>
> https://www.novabbs.com
>
> so there are communication problems between the 2 systems

Because of the amount of spam, many server block all messages
originating from Google.

Please also specify the group you posted.

Am 08.01.2024 um 17:00:01 Uhr schrieb a a:

> comp.lang.python
>
> newsgroup not supported by
>
> https://www.novabbs.com/computers/

Is available in "devel".

https://news.novabbs.org/devel/