Ok, this worked last week. Now it doesn't work. Debian Bullseye.
Konqueror, "sftp://other-machine/" doesn't work anymore. I have one
machine still using TDE 14.0.13, which I expected to work when the
machines I updated to TDE 14.1.0 started acting this way, but no. Now
none of them are able to sftp to each other in Konqueror.
Ssh works just fine between the machines. I'm using shared keys,
rather than passwords. Could that be the problem?
The error is occurring instead of the pinentry dialog opening up. NB,
the pinentry dialog opens just fine for kmail when signing this
email.
Suggestions?
Curt-
--
You may my glories and my state dispose,
But not my griefs; still am I king of those.
--- William Shakespeare, "Richard II"
Hi all,
after R14.1.0 was released, the development windows were open. This time
there are two windows - one for the upcoming R14.1.1, the other for the
future R14.2.0. The first pull-requests have already been merged and the
packages are already waiting in the queue for publishing...
If you use a stable R14.0.x series, you should consider performing tests
and switching to R14.1.x series, because R14.0.x is now closed and there
will be no further releases in this series.
If you used to use the Preliminary Testing Builds only temporarily and
prefer a little quieter Preliminary Stable Builds, it is time to switch
the repository. Likewise, if you used the Preliminary Stable Build only
temporarily and prefer quiet waters of stable releases, it is time to
switch to repository of official releases R14.1.x.
Currently, all repositors are the same - the stable releases R14.1.x, PSB
and PTB, so it is a good time to switch between repositories. At the end
of this week (May 7) it is planned to restart builds for PTB repository -
se there will be the first packages for R14.2.0~pre. At the end of the
following week (May 14) it is planned to restart builds for PSB
repository - so there will be the first packages for R14.1.1~pre.
Thank you for your support!
Cheers
--
Slávek
Hello,
This window is in english.
How to make it in french.
It is the only element that is in english.
The TDE chosen language is French.
I don't mind, it's just to know.
Cheers
André
Okay, so now dig me. :-]
I played round with ksystraycmd. It shows how long it's been since I thought
about this thing, because after mulling it over a bit, I figured out how to
make my own trick.
alt-F2
smplayer %f | --pkill ksystraycmd
Whatever applies to smplayer here, ought to work with other programs, too.
That kills the ghost icon from the start, if I open it from alt-F2, but now I
get a plain white vanilla gui interface. I believe I can figure out how to
force my own background, and probably how to get all this stuff into
the "open with" menu. There's probably an easier way, but at least I can get
this to work for me.
So I think I'm halfway there. Now for the messier problem: I have all these
leftover shortcuts in my "open with" menus. It worst in my oldest folders, of
course.
Now I'm wondering, Is there's an easy way of getting rid of those unused
shortcuts?
Bill
I recently compiled 14.1.0, and just like my 14.0.13 before it, the TDE
"identify" program does not work on much of anything for me. For example,
running it on a fairly innocuous JPEG, I get
Cannot decode /home/zsd/cyclone-copper.jpg: Unsupported file format or not RAW file
whereas the identify that comes with my distro's (Slackware64 15.0, fwiw)
imagemagick says
cyclone-copper.jpg JPEG 3840x1776 3840x1776+0+0 8-bit sRGB 1.49897MiB 0.000u 0:00.000
I'm trying to track down whether this is
(a) a TDE problem,
(b) a Slackware64 problem, or
(c) a me problem.
Would someone mind taking a minute to tell me if trinity's identify works
correctly on your system (and what distro you are using)?
Thanks.
Jim
Hi All,
Most of the time Lock Session works. But once it fails even manually running
the command:
dcop kdesktop KScreensaverIface lock
does nothing. And then I have to logout and log back in for it to work again.
.xsession-errors shows no errors. Both
dcop kdesktop KScreensaverIface isEnabled
dcop kdesktop KScreensaverIface isBlanked
return 'true.' If I understand it right they should both show false when the
session is not locked?
Anyone know how to use dcop to reset Lock Session so it works again?
Thanks,
Michael
Some of this post may be off-topic, in that it started with a security alert
for Devuan; this led me to run some scans of my own system, just to make sure
something bad hasn't crept in while I was relaxing, and staying offline most
of the time.
That Devuan alert is here:
https://linuxiac.com/devuan-users-are-at-risk/https://web.archive.org/web/20230429000520/https://linuxiac.com/devuan-user…
I did check my system, and login as root is disabled. At present, I am the
only user on any of my machines or devices, and this is usually how it goes
for me. If others want to get on the internet or whatever, let them bring
their own box. So anyway, I believe that I am probably okay there.
But then I decided to run a full scan of my system (still running). When I ran
klamav, I got some surprising hits, and some of these look like they ought to
be important enough for TDE users to know about. Thus my justification for
including the off-topic stuff as well.
I am not worried about the OpenOffice/LibreOffice extension, as it is
quarantined and I don't use it, but I am curious about what it is, and if it
is not perhaps a false positive. Also, I don't care about old emails that are
marked as having a spoofed domain. They're archived; someday I'll dig out
what they are and why I kept them.
What I am most concerned about are those .deb files that I downloaded. The
clamav testfiles are supposed to ring the bell, I will guess, because they
are made to test the program. But the other files are the boot image, so I
wonder if that's normal for the boot image to set off the alarms in my
antivirus program?
Bill
P.S. By the way: thanks to developers for adding klamav back to the great
tools available from the old KDE3. I have been missing klamav, because it is
much more customizable than other frontends for clamav. There is one called
clamtk that sorta worked, but I didn't like it.
I'm getting this strange situation again with DCOP:
| @22:01:36,leslie@pinto rc=0
| ~
| $ dcop --user leslie
| ERROR: Multiple available TDE sessions!
| Please specify the correct session to use with --session or use the
| --all-sessions option to broadcast to all sessions.
| @22:02:03,leslie@pinto rc=255
| ~
| $ dcop --user leslie --list-sessions
| Active sessions for user /home/leslie :
| .DCOPserver_pinto__0
| .DCOPserver_pinto__1
|
| @22:02:13,leslie@pinto rc=0
| ~
| $ px dcop
| leslie 26431 1 0 Apr29 ? 00:00:01 dcopserver [tdeinit] --nosid --suicide
| @22:02:20,leslie@pinto rc=0
| ~
| $ dcopserver --help-all
| Usage: dcopserver [--nofork] [--nosid] [--help]
| dcopserver --serverid
|
| DCOP is TDE's Desktop Communications Protocol. It is a lightweight IPC/RPC
| mechanism built on top of the X Consortium's Inter Client Exchange protocol.
| It enables desktop applications to communicate reliably with low overhead.
|
| Copyright (C) 1999-2001, The KDE Developers <http://www.kde.org>
For some reason DCOP says I have two DCOP sessions. .DCOPserver_pinto__0 does not
respond to queries, so apparently it's dead or a ghost. .DCOPserver_pinto__1 works
normally.
I notice also that the output from dcop --help does not include the --suicide option? Is
this a clue to what's going on?
How do I get rid of the one that doesn't respond?
Leslie
--
Platform: Linux
Distribution: openSUSE Leap 15.4 (x86_64)
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.13
tde-config: 1.0
I haven't tried archiving a folder yet, and there isn't any information in the Handbook
about archiving folders.
If I archive a folder, how can its content be accessed afterward?
Leslie
--
Platform: Linux
Distribution: openSUSE Leap 15.4 (x86_64)
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.13
tde-config: 1.0
Hello all,
I'm setting up a laptop with a 4K screen (it's a Thinkpad P51). This 4K screen
will be used to manipulate Photos (with programs that require Windows...).
I have installed Linux as well (for everything that does not require M$ stuff)
with MX-Linux and TDE.
I want to run TDE (and mostly all Linux programs) at 1920x1080. I've managed
to do this with xrandr, running from a script that is in /usr/local/share.
The last "problem" (with which I can live, just nags me) is that this script
visibly is run relatively late, after the login screen, which is then tiny.
I first set it up for xfce/lightdm and the scripts are triggered from
*.desktop files in ~/.config/autostart.
I found an /opt/trinity/share/autostart and hoped it might run thing before
login but it does not seem to (or more probably my syntax is not the right
one).
So the question is: is it possible to set resolution before login, if so how.
I'd prefet to continue working with xrandr than hardwiring something in the X
configuration file.
Thierry
