13 Dec
2021
13 Dec
'21
11:13 a.m.
Sorry, me again,
Important precisions, I receive these two messages on boot TDE :
1) The following installation problem was detected while tryng to start TDE :
No write access to "/run/user/1000/ICEauthority".
TDE is unable to start.
2) There was an error setting up inter-process communications for TDE.
The message returned by the system was :
could not read network connection list :
"/home/andre/.DCOPserver_debian-room__0"
Please check that dcopserver program is running !
If I correct :
the write access for "/run/user/1000/ICEauthority",
and read access for "/home/andre/.DCOPserver_debian-room__0"
it works, but after the next boot, I receive the two same messages,
I make the correction again... and next boot, idem...
Thanks for your help. I'm sure that Slavek will give the solution :-)
Cheers, André
14 Dec
14 Dec
11:05 p.m.
Hello,
I'm surprised to not receive an answer about my TDE difficulties,
however, 100% linked to Trinity (dcopserver and ICEauthority).
Cheers, André
On Monday 13 December 2021 12:13:46 ajh-valmer wrote:
Important precisions, I receive these two messages on
boot TDE :
1) The following installation problem was detected while tryng to start TDE :
No write access to "/run/user/1000/ICEauthority".
TDE is unable to start.
2) There was an error setting up inter-process
communications for TDE.
The message returned by the system was :
could not read network connection list :
"/home/andre/.DCOPserver_debian-room__0"
Please check that dcopserver program is running !
If I correct :
the write access for "/run/user/1000/ICEauthority",
and read access for "/home/andre/.DCOPserver_debian-room__0"
it works, but after the next boot, I receive the two same messages,
I make the correction again... and next boot, idem...
> I'm sure that Slavek will give the solution :-)
15 Dec
15 Dec
1:23 a.m.
On 2021/12/15 08:05 AM, ajh-valmer wrote:
Hello,
I'm surprised to not receive an answer about my TDE difficulties,
however, 100% linked to Trinity (dcopserver and ICEauthority).
Cheers, André
On Monday 13 December 2021 12:13:46 ajh-valmer wrote:
Hi André,
apologies for the late reply, busy period these days.
Not sure what could be wrong on your system, but I would start from some basic checks:
1) do you have ownership and write access to "/run/user/1000/ICEauthority"?
2) is our user "andre" ok and id 1000?
3) did you try creating a new user and see if you can login with that?
4) do the write/read permits get messed up also if you don't launch tdm and simply
restart your system from CLI?
Also are you using systemd or sysvinit?
It is difficult to give more precise feedback, since we don't see the same issue here.
Some users reported some problems
on ICEauthority after trying to run TCC in root mode, but it seems here your problem is
before you even run a TDE session.
Cheers
Michele
Important precisions, I receive these two
messages on boot TDE :
1) The following installation problem was detected while tryng to start TDE :
No write access to "/run/user/1000/ICEauthority".
TDE is unable to start.
2) There was an error setting up inter-process
communications for TDE.
The message returned by the system was :
could not read network connection list :
"/home/andre/.DCOPserver_debian-room__0"
Please check that dcopserver program is running !
If I correct :
the write access for "/run/user/1000/ICEauthority",
and read access for "/home/andre/.DCOPserver_debian-room__0"
it works, but after the next boot, I receive the two same messages,
I make the correction again... and next boot, idem...
I'm sure that Slavek will give the solution
:-)
____________________________________________________
4:17 p.m.
On Wednesday 15 December 2021 02:23:58 Michele Calgaro via tde-users wrote:
> On Monday 13 December 2021 12:13:46 ajh-valmer
wrote:
>> Important precisions, I receive these two messages on boot TDE :
>> 1) The following installation problem was detected while tryng to start TDE :
>> No write access to "/run/user/1000/ICEauthority".
>> TDE is unable to start.
>> 2) There was an error setting up inter-process communications for TDE.
>> The message returned by the system was :
>> could not read network connection list :
>> "/home/andre/.DCOPserver_debian-room__0"
>> Please check that dcopserver program is running !
>> If I correct :
>> the write access for "/run/user/1000/ICEauthority",
>> and read access for "/home/andre/.DCOPserver_debian-room__0"
>> it works, but after the next boot, I receive the two same messages,
>> I make the correction again... and next boot, idem...
>> I'm sure that Slavek will give the solution :-)
Hi André,
apologies for the late reply, busy period these days :
Thanks Michele and don't
worry about that.
Not sure what could be wrong on your system, but I
would start from some basic checks:
1) do you have ownership and write access to
"/run/user/1000/ICEauthority"? :
Yes, ok for write access, but wich
ownership, andre or root (because it is in root) ?
2) is our user "andre" ok and id 1000 ? :
Yes, in /etc/group, and I see "autologin:x:998:andre"
3) did you try creating a new user and see if you can
login with that ? :
No, because see the point 4) below.
4) do the write/read permits get messed up also if you
don't launch tdm and simply
restart your system from CLI ? :
I cannot directly boot automatically to
trinity-desktop (TDE session).
I'm in TCC, after I log in root and must type : "killall tdm" and TDE
session starts
with user andre and with the messages above this mail.
Also are you using systemd or sysvinit ? :
I'm with systemd. If I boot from grub with sysvinit I have the same problem.
It is difficult to give more precise feedback, since
we don't see the same issue here.
Some users reported some problems on ICEauthority after trying to run TCC in
root mode, but it seems here your problem is before you even run a TDE session :
I
seem to have seen the same problem on this Mailing-List.
Thanks, cheers, André
16 Dec
16 Dec
1 p.m.
Hi André,
your user. if you login as root, you would have a file under
"/run/user/0/ICEauthority" I believe
Since you have autlogin, have you tried disabling autologin for a test?
uhm, this is also weird. How do you get to TCC if you can't get a normal boot to a TDE
session?
I would try installing a different dm (like sddm for example) and see if you can boot to a
DM screen and login in a TDE
session using that DM. If so and everything is fine, this will narrow the scope of the
problem at least.
Do you have the right tdm.service file installed for systemd?
Cheers
Michele
1) do you have ownership and write access to
"/run/user/1000/ICEauthority"? :
Yes, ok for write access, but wich ownership, andre or root (because it is in
root) ?
2) is our user "andre" ok and id 1000 ?
:
Yes, in /etc/group, and I see "autologin:x:998:andre"
4) do the
write/read permits get messed up also if you don't launch tdm and simply
restart your system from CLI ? :
I cannot directly boot automatically to trinity-desktop (TDE session).
I'm in TCC, after I log in root and must type : "killall tdm" and TDE
session starts
with user andre and with the messages above this mail.
Also are you using systemd or sysvinit ? :
I'm with systemd. If I boot from grub with sysvinit I have the same problem.
17 Dec
17 Dec
10:21 a.m.
On Thursday 16 December 2021 14:00:25 Michele Calgaro via tde-users wrote:
Hi André,
your user. if you login as root, you would have a file under
"/run/user/0/ICEauthority"
I believe :
Hi Michele,
Nice from you to help me.
Yes, I have this file, and "/run/user/1000/ICEauthority" too.
Since you have autlogin, have you tried disabling
autologin for a test ? :
Yes.
uhm, this is also weird. How do you get to TCC if you
can't get a normal boot to a TDE session?
I would try installing a different dm (like sddm for example) and see if you can boot to
a DM
screen and login in a TDE session using that DM. If so and everything is fine, this will
narrow
the scope of the problem at least.
I can only boot in TCC mode. After, I log in root and I type "killall tdm",
but I fall on error messages "DCOPserver" and "ICEauthority"
preventing a access to TDE-Trinity.
Sometimes the system boot tde-desktop.
When I click on an icon, I receive this message :
tde-init cannot launch kmail or another application a konqueror...
Do you have the right "tdm.service" file
installed for systemd ? :
"tdm.service" attached.
Thanks, cheers, André
18 Dec
18 Dec
3:08 a.m.
Hi André
This service file seems to have been modified (Conflict and After are empty). Can you try
with the "official" one? As a
note, there has been a recent update so make sure you get the latest one from TGW :-)
Cheers
Michele
I can only boot in TCC mode.
Maybe we are using the same term for different meanings.
TCC for me means TDE Control Center, that requires a TDE session.
Do you have
the right "tdm.service" file installed for systemd ? :
"tdm.service" attached.
4:57 p.m.
New subject: TDE, error messages
On Saturday 18 December 2021 04:08:38 Michele Calgaro via tde-users wrote:
Hi André
Can you try with the "official" one? As a note, there has been a recent
update so make sure you get the latest one from TGW :-)
Hello Michele,
What do you mean by "TGW" ?
The problem is the file with these rights and user :
/run/user/1000/ICEautorithy rw root root
I correct by :
/run/user/1000/ICEautorithy rw-rw-r andre andre
or I delete the file.
The error message, dcop_server-error-message.png attached
comes back again, the file rights are again as before :
/run/user/1000/ICEautorithy rw------ root root
Too, what happens with "dcopserver" not working ?
Why this error now with Debian Bullseye ?
I reinstalled tde-base-trinity, always idem,
I'm lost !
Has Slavek an idea ?
André
5:40 p.m.
New subject: TDE, error messages
Hi André,
Any time you start some part of TDE from root and other than via TDM you're
likely to be creating problems as files get owned by root.
Try to work through any problems from the beginning - first get TDM to start
then login as your non-root user then any applications you need to run.
--Mike
15 Dec
15 Dec
8:56 a.m.
On Wed, 15 Dec 2021 00:05:55 +0100
"ajh-valmer" <ajh.valmer(a)free.fr> wrote:
Hello,
I'm surprised to not receive an answer about my TDE difficulties,
however, 100% linked to Trinity (dcopserver and ICEauthority).
No, ICEauthority has nothing to do with Trinity per se, you will have the
same issue with almost any DE (there few which does not use ICEauthority)
On Monday 13 December 2021 12:13:46 ajh-valmer wrote:
I believe the most common reason for recurring wrong permissions on
ICEauthority and DCOPserver is having your home folder been owned by root.
--
Nick Koretsky (nick.koretsky(a)gmail.com)
Important precisions, I receive these two
messages on boot TDE :
1) The following installation problem was detected while tryng to start
TDE : No write access to "/run/user/1000/ICEauthority".
TDE is unable to start.
2) There was an error setting up inter-process
communications for TDE.
The message returned by the system was :
could not read network connection list :
"/home/andre/.DCOPserver_debian-room__0"
Please check that dcopserver program is running !
If I correct :
the write access for "/run/user/1000/ICEauthority",
and read access for "/home/andre/.DCOPserver_debian-room__0"
it works, but after the next boot, I receive the two same messages,
I make the correction again... and next boot, idem...
> I'm sure that Slavek will give the solution :-) 
9:59 a.m.
ajh-valmer wrote:
I'm surprised to not receive an answer about my
TDE difficulties,
however, 100% linked to Trinity (dcopserver and ICEauthority).
may be we go one step back and do the proper plan check fro installing TDE.
I don't know on which system you install (debian, ubuntu etc.), however what
I think is the best way to install for example on debian is to take a
minimal installation without GUI (just SSH and if you wish CUPS) then
install TDE.
You have to create a normal user with password.
Then all should work fine.
Having problems like described above, means to me you are doing something
wrong, but we do not know what exactly.
8 Jan
8 Jan
10:53 a.m.
Maybe we are using the same term for different meanings.
TCC for me means TDE Control Center, that requires a TDE session.
<a href="https://192168l254.com.mx/ES/>192.168.l.254</a>.
...
This service file seems to have been modified (Conflict and After are empty). Can you try
with the "official" one? As a
note, there has been a recent update so make sure you get the latest one from TGW
1087
days inactive
1113
days old
11 comments
6 participants
participants (6)
-
ajh-valmer -
deloptes -
Michele Calgaro -
Mike Bird -
Nick Koretsky -
sophiaab98＠gmail.com