I am unable to send my emails to this group on Kmail due to the following error:
"Authorization failed, Authentication support is not compiled into tdeio_smtp. authentication not supported"
I've had this problem on FreeBSD and Devuan before where my emails wouldn't send but never got an error message. Usually it would start to work after some time. But here I get this error consistently, I even tried to rebuild tdepim and tdelibs. I don't know which package has tdeio_smtp but the Slackbuild seems to build without this support.
--
~ Hunter
Sent from my Android device with K9 Mail
Dear all,
I am a long-time and happy user of the Trinity desktop, which is a
wonderful continuation to KDE 3.x.
I am try to sep up my laptop to automatically "Suspend to RAM" after a
given time without user activity, but i can't figure out the setting.
Could you please give me some pointers?
The configuration:
Thinkpad T400 (RAM 4go)
Q4OS 3.15.2-n1 (Debian 10 Buster-based, 64bit distribution)
The following interactive commands work:
sudo systemctl suspend
sudo bash && echo -n "mem" > /sys/power/state
Best regards
On Wednesday 22 December 2021 17:28:23 awaco(a)free.fr wrote:
> On 2021/12/13 07:09 PM, ajh-valmer wrote:
> > Hello Michele,
> > What does it mean, the messages above ?
> > When I boot Bullseye, I'm in command-line mode (no Xorg, no graphic),
> > invited to connect in root (and password).
> > I have to type "killall tdm" to be connected on the trinity desktop.
> > So, what to do to be directly on the trinity desktop ?
> > André
> Hi André,
> not sure of the details of the error message, would have to check them out.
> But it's the rest that caught my attention.
> Normally a TDE system should boot up and present you the tdm login screen.
> But you mentioned you are in command prompted
> and "invited" to login as root. Do you have some errors and a message
> asking you to provide the root password to login to rectify the issue or
> pressing Ctrl+D to continue ?
I have Ctrl+D to continue in recovery mode or type root passwd.
Only one solution, type "killall tdm" to connect to tde-desktop.
> If you see this message, give it a Ctrl+D first (without logging in) and
> see what happens and if you get the tdm login screen afterwards
> or not. Cheers Michele
Hi Michele,
/var/log/tdm.log exists but empty.
/var/log/tdm.1.log :
"info: Cannot open master configuration file /etc/trinity/tdm/tdmdistrc".
tdmdistrc doesn't exist in this folder.
I can login to tde-desktop with lightdm, not with tdm-trinity.
(even after a dpkg-reconfigure tdm-trinity).
Now I have a clear understanding what happens without to be able to repair.
The file /run/user/1000/ICEauthority is :
-rw------- 1 andre andre 205 22 déc. 17:18 ICEauthority
It becomes automatically quickly :
-rw------- 1 root root 205 22 déc. 17:18 ICEauthority,
after I receive the error messages allready indicated,
DCOPserver and /home/andre./.Xauthority not writable :
-rw------- 1 andre andre 59 22 déc. 17:18 .Xauthority
It seems that there is a conflict between two users, root and andre.
Thanks. Bye, cheers, André
In Slackware and also on FreeBSD (the latter if I recall), TDM has a different look than when I install it on something like Devuan for example. Particularly it has a rounded and transparent KDE4 "Oxygen" look to it, and the options in the Display Manager module do not work when this kind of TDM is installed, like adding a clock, the logo, or changing the widget style.
Tdmtheme is not installed. I thought it was tdmtheme that changed it to look like this out of the box but it doesn't seem to be related. It looks to be the default in certain TDE ports.
Secondly to keep from posting twice I also can't access the Display Manager module. If I click on it the window does not open, and I'm not sure what it depends on that I may be missing since this is on Slack.
--
~ Hunter
Sent from my Android device with K9 Mail
Version: KMAIL 1.9.10
To backup my emails, I only need to back up what is in:
/home/chris/.trinity/share/apps/kmail/mail
What about config files? Accounts that are set up currently, rules, etc.
Thanks,
Chris
Fresh install of Debian 11 ( as of yesterday)
Trinity Desktop 14
My screen is not going to sleep.... Sometimes it will and sometimes it won't.
For instance:
I took a nap earlier... The password box said the session was locked at 2:01
PM CST. At 3:00 the screen was still on!!
Also when the screen does turn off, it takes WAYYYYYYYYY over the time that I
have it set for to blank off and turn off the screen. I have it set for:
25 for screensaver
26 for display standby
26 for display suspend
26 min to power off the screen.
Sometimes its almost or right at an hour before the screen blanks off.
I didn't have this problem with Gnome DE on Debian.
Thanks,
Chris
Hi,
There's is one more thing that I need to ask about:
I am needing something simular to the likes of Gparted, to where I can
reformat USB sticks etc.
What app is the TDE equivalent of Gparted?
Thanks,
Chris
Sorry for possible double posting but that message got rejected somehow, it seems:
Hi
A friend of mine has Ubuntu 20.04 running (the installation is a year
old and so is the corresponding trinity version, if necessary I can
provide the precise version).
In any case my friend has problem of copying files to USB sticks using
konqeror. (The copying works from the command line, most sticks have
vfat.), by problem with copying I mean the following.
In konqueror: The file is marked to be copied, then the USB stick is
opened, but the menu entry for pasting is in grey and cannot be used.
I had a look at it and found out that deleting the cache helped, but it
seems only for a while.
Is there any alternative to konqueror available?
Nautilus works, but is very very ugly and not that intuitive.
Regards
Uwe Brauer
Very soon after I started to use the TDE 14.0.11 version I began
receiving DCOP error messages, having the effect of preventing use of
various applications like Firefox and LibreOffice. After online research
and experimentation on my part I discovered that I could solve such
preventions if before opening TDE I ran in a tty as root the following
three commands:
'dcopserver -- serverid', which returned nothing, then 'dropserver' and
finally again 'dcopserver -- serverid'. This time however that command
returned something like the following:
'[dcopserver] local/Morcom:/tmp/.ICE-unix/dcop5698-1636014592'
>From this point on there were no longer any more DCOP error messages. I
had full use of the TDE and various applications until when I next
closed completely the computer.
It is consequently my understanding that running the 'dcopserver'
command is presumably required as part of the initial boot-up. If such
is usually the case I would appreciate knowing what I need to do to have
my computer, named Morcom, do so as well. Can anyone tell me?
Regards, Ken
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting