[SOLVED] Slackware64-current multilib: Pan-0.146 error sending posts (pan issue 103) PATCH FIX

kingbeowulf · 06-25-2020, 01:29 AM

As a user or pan for newsgroups for many years on Slackware, this one took me by suprise today.

Code:

Wed Jun 24 22:48:51 2020 - Posting of “Re: too much network traffic after -current upgrade” failed: 441 Duplicate Content-Type: header

This posting bug has already been reported to and noticed upstream:
https://gitlab.gnome.org/GNOME/pan/-/issues/103
https://gitlab.gnome.org/GNOME/pan/-/merge_requests/10

fix here:

https://gitlab.gnome.org/GNOME/pan/-...fec51b23820467

Code:

diff --git a/pan/gui/post-ui.cc b/pan/gui/post-ui.cc
index 8769ec54815132c40d9c5908eb6c801c6368c07d..861ebec53f1e58fa583598971e8571e923da1e5a 100644
--- a/pan/gui/post-ui.cc
+++ b/pan/gui/post-ui.cc
@@ -1604,11 +1604,11 @@ PostUI :: new_message_from_ui (Mode mode, bool copy_body)
 
   // headers from the ui: From
   const Profile profile (get_current_profile ());
-  std::string s;
-  profile.get_from_header (s);
 #ifdef HAVE_GMIME_30
-  g_mime_message_add_mailbox (msg, GMIME_ADDRESS_TYPE_SENDER, NULL, s.c_str());
+  g_mime_message_add_mailbox (msg, GMIME_ADDRESS_TYPE_SENDER, profile.username.c_str(), profile.address.c_str());
 #else
+  std::string s;
+  profile.get_from_header (s);
   g_mime_message_set_sender (msg, s.c_str());
 #endif

HOWEVER, I'm not able to get this patch to work. I must be missing something.

chrisretusn · 06-27-2020, 05:40 AM

I doubt you are doing anything wrong. The patch doesn't work.

I'm getting the same issue. When I try to post is says "Error: Bad email address." The Event Log shows "Posting of “test” failed: 441 Duplicate Content-Type: header"

I rebuilt pan with the patch, the patch is successfully applied, yet it changes nothing with pan. The comments refer to compiled with gtk3 on debian. So I tried that, compiling with gtk3. That didn't change anything. Still cannot post. The merge request for this patch is 2 weeks old.

I've added a comment to https://gitlab.gnome.org/GNOME/pan/-/issues/103 on this issue.

kingbeowulf · 06-27-2020, 02:31 PM

Thanks! I wanted to confirm before I run off and post on the issue. Those gnomes can be a bit testy.

kingbeowulf · 06-27-2020, 03:26 PM

Well I tried the patch edit here: https://gitlab.gnome.org/GNOME/pan/-/issues/103

Quote:

Detlef Graef @dgraef · 2 hours ago

It works, but the string GMIME_ADDRESS_TYPE_SENDER has to be replaced with GMIME_ADDRESS_TYPE_FROM.

Also tried recompiling gmime-3.2.7 (just in case).
No joy.

It seems the patch(s) just removed the pop up error message. Error still shows up in File -> Event Log and message stuck queued in File -> Task Manager.

chrisretusn · 06-28-2020, 01:38 AM

In your first post above you noted the event log entry "Wed Jun 24 22:48:51 2020 " is this the first time you noticed this?

I replaced gmime 3 with that last version of gmime 2.6.23 and I am able to send.

That that segmentation fault you described in your post here still exist too.

chrisretusn · 06-28-2020, 02:07 AM

I just tried modifying the patch. Yup, it gets rid of the popup message, but the problem still exist as shown in the log.

kingbeowulf · 06-29-2020, 11:15 AM

Quote:

Originally Posted by chrisretusn

In your first post above you noted the event log entry "Wed Jun 24 22:48:51 2020 " is this the first time you noticed this?

I replaced gmime 3 with that last version of gmime 2.6.23 and I am able to send.

...

Posting had always worked fine in 14.2 and earlier. I had just lurked on usenet since upgrading every box here to current (Dec 2019-Jan 2020) and thus do not know when the issue may have started. I was thinking to start with a clean profile, but given your downgrade to gmime-2.6.23 that doesn't seem like the issue.

I wonder if anything else in current uses gmime?

I do not recall now when a switched to pan, probably sometime prior to 2011, based on some profile date stamps. Pan did occasional segfault on send and some other operations, but never often enough to do anything about it.

chrisretusn · 06-30-2020, 08:04 AM

Quote:

Originally Posted by kingbeowulf

Posting had always worked fine in 14.2 and earlier. I had just lurked on usenet since upgrading every box here to current (Dec 2019-Jan 2020) and thus do not know when the issue may have started. I was thinking to start with a clean profile, but given your downgrade to gmime-2.6.23 that doesn't seem like the issue.

I wonder if anything else in current uses gmime?

I do not recall now when a switched to pan, probably sometime prior to 2011, based on some profile date stamps. Pan did occasional segfault on send and some other operations, but never often enough to do anything about it.

Oh, okay, switched over to -current from 14.2, went from lurker to poster. Hehe, been there done that. Since you turned me back on to usenet I am 100% a lurker for now. Except for a few test post. Back in the day I was fairly active in some groups. Here are a couple from ChangeLog.txt in -current that may be of interest and also answers your question.

Code:

Thu Jul 25 22:48:09 UTC 2019
l/gmime-3.2.3-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
xap/pan-0.145-x86_64-2.txz:  Rebuilt.
  Recompiled against gmime-3.2.3.

Wed Dec 20 03:05:58 UTC 2017
l/gmime-2.6.23-x86_64-2.txz:  Upgraded.
  Revert to gmime-2 until the issues with pan are worked out. Nothing else in
  Slackware is using this library.
xap/pan-0.143-x86_64-3.txz:  Rebuilt.
  Recompiled against gmime-2.

Wed Dec  6 14:13:48 UTC 2017
l/gmime-3.0.5-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
xap/pan-0.143-x86_64-2.txz:  Rebuilt.
  Recompiled against gmime-3.0.5.

I am guessing that Pat upgraded to gmime 3 in 2019 along with pan and no complaints, until you shifted over to -current and I started to use pan.

The question I am wondering about, who else in Slackware uses pan? Could it be just the two of us? LOL I doubt it though.

At any rate, this issue has gotten the attention of the developers. Hopefully they will have a fix soon.

slackerDude · 06-30-2020, 02:01 PM

I use pan on and off.. Would be nice to know when a fix is available..

kingbeowulf · 06-30-2020, 08:55 PM

I hope so. I had just switched to Eternal September from Albasani.net news servers after Albasani went down. I hadn't posted in ages - a year? - used to be active on sci.chem, sci.chem.anayltical, physics, astronomy/space, a.o.l.slackware and nvdia / 3dfx groups and a few other technobabble groups under various monikers.

Sucks that I was itching to post recently and couldn't. By the time I configured Thunderbird I had lost the thought.

chrisretusn · 07-06-2020, 08:09 AM

A fix is in. At least it works for me. I am now able to post to usenet.

Here is a link to the post on the bug issue for the fix:
https://gitlab.gnome.org/GNOME/pan/-...03#note_858738

The two needed patches are located here:
https://gitlab.gnome.org/dgraef/pan/...db5496f2.patch

And here:
https://gitlab.gnome.org/dgraef/pan/...e4b473f8.patch

I added the patches to the stock pan.SlackBuild from the slackware64-current/source/xap/pan tree and rebuilt the package, reinstalled it and now can post to usenet. (Actually I copied to my package tree and built from there)

Test is see if they work for you.

kingbeowulf · 07-15-2020, 01:36 AM

nope. no such luck. I thought I could just download the patches and insert:

Code:

cd ${PKGNAM}-$VERSION || exit 1

# fix not being able to post
# https://gitlab.gnome.org/GNOME/pan/-/issues/103#note_858738
patch -p1 < $CWD/0d775547f0e7cf7529538704814469e1db5496f2.patch
patch -p1 < $CWD/495bfb2eb9228b5b5cef8b50e11af577e4b473f8.patch

# Make sure ownerships and permissions are sane:
chown -R root:root .

But post still stuck in queue with error

Code:

Tue Jul 14 22:21:26 2020 - Posting of “patch pan to restore posting on Slackware (current 15.0)” failed: 441 Invalid syntax encountered in headers (unexpected byte, no colon-space, or empty content line)

Update: removed the XFACE code from header and now I can post. weird.

kingbeowulf · 07-15-2020, 02:34 AM

ffs. X-face worked if I post to eternal-september.test group. why not to a.o.l.slackware?

chrisretusn · 07-15-2020, 04:18 AM

Quote:

Originally Posted by kingbeowulf

nope. no such luck. I thought I could just download the patches and insert:

That is what I did. Only difference is I renamed the patches.

Code:

cd ${PKGNAM}-$VERSION || exit 1

# https://gitlab.gnome.org/GNOME/pan/-/issues/103#note_858738
patch -p1 --verbose < $CWD/Fix-for-GMime3-build.patch
patch -p1 --verbose < $CWD/Remove-empty-line-from-file-posting.patch

# Make sure ownerships and permissions are sane:

Quote:

But post still stuck in queue with error

Posted fine here. I replied to one of your test in alt.os.linux.slackware

Quote:

Update: removed the XFACE code from header and now I can post. weird.

I don't use XFACE.

Perhaps you should post an update to the bug report about this problem with XFACE.
https://gitlab.gnome.org/GNOME/pan/-...03#note_858738

kingbeowulf · 07-16-2020, 12:55 PM

I added a profile to use aioe.org as the news server. No issues posting with the X-face in any newsgroup. Switched back to eternal-september and posting with X-Face works sometimes in some groups, but never in a.o.l.slackwware. So, ES must be doing something weird when it receives the header.

I kinda got used to my besotted avatar over the years. I guess I can switch to posting via aioe.org or retire the wee drunkard. Either way, I'll mark this thread as solved. Thanks so much for your assistance, chrisretusn.