On Sun January 29 2023 10:45:46 ajh-valmer via tde-users wrote:

On Friday 27 January 2023 18:40:21 ajh-valmer via tde-users wrote:

...

The french encoding "West European 8859-15" in Kmail, is not memorized. So, I have to put it again at each mail sending, otherwise, Kmail refuses to send the mail. How to break free the encoding ?

No answer to my question... ?

Hi André,

In KMail / Settings / Configure Kmail / Composer / / Charset you can specify a list of character sets which will be checked in order and the first which contains all of the characters in the message will be used.

So try putting iso-8859-15 first in that list.

--Mike

On Monday 30 January 2023 13:36:34 deloptes via tde-users wrote:

Mike Bird via tde-users wrote:

...

So try putting iso-8859-15 first in that list.

And why not UTF8? This iso encoding is outdated but can be used as fall back in such cases where the sender still uses it.

Hello,

Proposed encoding in Kmail are : automatic , iso-8859-1X , us-ascii , unicode utf8...

Regardless of the choosen encoding, it is not memorized and comes back to "automatic".

Bye, cheers,

André

Anno domini 2023 Mon, 30 Jan 16:27:30 +0100 Thierry de Coulon via tde-users scripsit:

On Monday 30 January 2023 15.56:30 ajh-valmer via tde-users wrote:

...

Regardless of the choosen encoding, it is not memorized and comes back to "automatic".

Bye, cheers,

André

I'm afraid this is a local problem. My kmail proposes UTF-8,iso-8859-1,us-ascii. If I move one to the first place and click "Apply", next time I start kmail it's still set as first.

Thierry

I'd suggest to change the file ownership for all files in the home directory, e.g.:

$ chown andre:andre ~ -R

Might be that this solves your dcop problem, too.

Nik

On Monday 30 January 2023 15:56:30 André wrote:

On Monday 30 January 2023 13:36:34 deloptes via tde-users wrote:

...

Mike Bird via tde-users wrote:

...

So try putting iso-8859-15 first in that list.

...

And why not UTF8? This iso encoding is outdated but can be used as fall back in such cases where the sender still uses it.

Proposed encoding in Kmail are : automatic , iso-8859-1X , us-ascii , unicode utf8... Regardless of the choosen encoding, it is not memorized and comes back to "automatic". André

...

chown andre:andre ~ -R

Sorry, problem not solved, Regardless of the choosen encoding, it is not memorized and comes back to "automatic" and I'm invited to declare the encoding in kmail, otherwise the mail is not sended. Cheers André

On Monday 13 February 2023 18:24:42 Mike Bird via tde-users wrote:

On Mon February 13 2023 02:22:32 ajh-valmer via tde-users wrote:

...

Sorry, problem not solved, Regardless of the choosen encoding, it is not memorized and comes back to "automatic" and I'm invited to declare the encoding in kmail, otherwise the mail is not sended.

Could you please provide a screen grab of this invitation?

See the screenshot attachment.

Translation in english : "No right encoding has been found for your message Please choose an encoding in the Options menu"

Impossible to fix an encoding.

Thank you, cheers.

André

On Monday 13 February 2023 19:59:03 Mike Bird via tde-users wrote:

On Mon February 13 2023 10:51:04 ajh-valmer via tde-users wrote:

...

Translation in english : "No right encoding has been found for your message Please choose an encoding in the Options menu" Impossible to fix an encoding.

Does this happen with an empty message? If not, can you figure out - perhaps by bisection - which character in the message is causing this?

This message appears as soon as I open kmail, and begin to write, the first letter... Or when I want to send tne mail by the menu "Message", it depends.

On Monday 13 February 2023 23:15:27 Mike Bird via tde-users wrote:

What please do you have under Settings / Configure KMail / Composer / / Charset ? I have attached mine for comparison.

With the encoding charset indicated in your Composer, now it seems ok, no error messages... Thanks Mike, Cheers, André

On Monday 30 January 2023 13:39:31 deloptes via tde-users wrote:

regarding this, you should do exactly what is asked for. Then try find out why is this message coming. I mean you have two options dcopserver is working dcopserver is not working How can we know what is going on there. Describe what you are doing. If it is happening out of nowhere while working or when you start the system, or when you resume ...

I post again my first message :

I receive many times the attached message about DCOP in a window, when I click on an icon.

# ps aux|grep dcop andre 988 0.0 0.1 52660 10536 ? S 10:38 0:00 dcopserver [tdeinit] --nosid --suicide

What to do ?

I'm on Debian Bullseye 64 bits

Cheers

On Wednesday 01 February 2023 05:29:57 Michele Calgaro via tde-users wrote:

On 2023/01/31 12:02 AM, ajh-valmer via tde-users wrote:

...

On Monday 30 January 2023 13:39:31 deloptes via tde-users wrote:

...

Then try find out why is this message coming. I mean you have two options dcopserver is working dcopserver is not working How can we know what is going on there. Describe what you are doing. If it is happening out of nowhere while working or when you start the system, or when you resume ...

Hi Andre', difficult to say for sure. Is dcopserver functional? i.e. can you interact with it using the CLI dcop client or KDCOP?

Hello Michele, # apt-cache search KDCOP (no answer) What do you mean by "the CLI dcop client" ?

Is the problem happening when you click "any" icon? Or just a specific icon? What program is being run by the icon? Is it being run as a different user? Have you tried creating a new user and test after a reboot and logging in as the new clean user? Any strange message in .xsession-errors? Hope this gives some pointers to further investigate the issue. Michele

It's sometimes and on any icons?

# ps aux|grep dcopserver andre 974 0.0 0.1 52548 9212 ? S 17:28 0:00 dcopserver [tdeinit] --nosid --suicide root 1300 0.0 0.1 52416 9124 ? S 17:410:00 dcopserver [tdeinit] --nosid --suicide

So, dcopserver seems working but in a strange mode "suicide". and two times : What it means ?

# cat .xsession-errors|grep dcopserver [2023/02/01 17:05:41.833] [dcopserver] DCOP Cleaning up dead connections. [dcopserver] It looks like dcopserver is already running. If you are sure and start dcopserver again. [2023/02/01 17:05:43.402] [dcopserver] DCOP Cleaning up dead connections. [2023/02/01 17:05:45.588] [dcopserver] DCOP Cleaning up dead connections.

Thanks, Cheers Andre

On Wednesday 01 February 2023 18:32:26 Michael via tde-users wrote:

Lauch KDCOP. Menu > System > KDCOP (DCOP Browser)

I don't see any KDCOP (DCOP Browser) in the Menu > System...

ajh-valmer via tde-users wrote:

A window opens with many k....... programs (kdcop.png attached), but no kdcop in the menu.

I was thinking I have posted a reply, but I do not see it - may be I did not post it at all.

It is hard to say for sure as Michele said, but this error message is coming from a function in tdelibs/dcop/KDE-ICE/process.c at line 985

if ((*iceConn->listen_obj->host_based_auth_proc) (hostname)) ... else { _IceErrorAuthenticationRejected (iceConn, ICE_ConnectionSetup, "None of the authentication protocols specified are supported and host-based authentication failed");

iceConn->connection_status = IceConnectRejected; }

so IMO it must be something hostname related (assuming everything else is kosher). Could be of course ICE related too.

BR

ajh-valmer via tde-users wrote:

Yes, but it doesn't help me and no answer about :

Should I check your internet configuration to say if you have DNS issues?

# ps aux|grep dcop andre 974  0.0  0.1  52680 10248 ? S 17:28 0:00 dcopserver [tdeinit] --nosid --suicide Why this process has "--suicide" ?

man dcopserver

should I read the man for you? it means run single instance, so it is ok. basically it looks ok. there is obviously communication problem and it points to hostname or somehow the protocol - or whatever

I think you should force your brain cells a little bit more on your own. (And I do not mean it in negative way - it is your computer system that is having issues)

BR

On Thursday 02 February 2023 16:47:19 deloptes wrote:

...

...

[tdeinit] --nosid --suicide :

--nosid Do not create a new session for the program. --suicide Tell dcopserver to automatically terminate if no transactions are made within 10 seconds.

Ok, good, thanks.

On Wednesday 01 February 2023 18:37:44 Michael via tde-users wrote:

On Wednesday 01 February 2023 10:44:41 am ajh-valmer via tde-users wrote:

...

# apt-cache search KDCOP (no answer)

Also you need to search for the right thing... michael@local [~]# which dcop /opt/trinity/bin/dcop michael@local [~]# dpkg -S /opt/trinity/bin/kdcop tdebase-trinity-bin: /opt/trinity/bin/kdcop michael@local [~]# apt-cache search tdebase-trinity-bin tdebase-trinity-bin - core binaries for the TDE base module

dcop seems correctly installed.

# ps aux|grep dcop andre 974 0.0 0.1 52680 10248 ? S 17:28 0:00 dcopserver [tdeinit] --nosid --suicide : Why this strange process "--suicide" ?

# kill -9 974 the session is stopped and restarted, with the same processus "--suicide" .

Bye, cheers, Andre

On Wednesday 01 February 2023 23:30:28 E. Liddell wrote:

The --suicide option appears to be normal: ryu ~ # ps -ef | grep dcop eliddell 3391 1 0 2022 ? 00:00:03 dcopserver [tdeinit] --nosid --suicide Apparently I didn't install the manpage, but https://manpages.org/dcopserver says: --suicide : Tell dcopserver to automatically terminate if no transactions are made within 10 seconds. So it's unlikely that that is the source of your issue. A web search on the text of your full error suggests that the problem is with (t)qt session management. Most straightforward remedy suggested is to issue this at the command line: unset SESSION_MANAGER You may also (judging from other hits) have a broken dbus, iceauth, or some other messaging or auth problem. E. Liddell

This was the first GOOD action to do. Well done, now I am reassured, this processus was not dangerous. Thank you Mister Liddle.

André