Trinity 14.0.6 preliminary.
Don't know if it is a feature of ksnapshot or a misconfiguration
somewhere from me, but it is getting absolutely annoying what happens.
I have a website, a document or whatsoever on my screen in full
A4-papersize. Now I want a printout of a small part of it. Call
ksnapshot, choose "region" "new snapshot" and then draw a border around
the desired part. Press "print" and then print it. Bull... I get a
print in landscape, useless and even worse not even the original layout
reappears.
Stop ksnapshot, restart it and same procedure with again the same
miserable result.
Stop, restart, same procedure but no actual printing, instead I look
into the printer properties. And there, big surprise, landscape was
marked as to be printed BUT all 4 orientations were grayed out, so I
couldn't change that.
Checked in tdeprint the printersettings, nothing wrong, in "instances"
"settings" all 4 orientations were available and portrait was marked as
to be applied in the default printer.
Checked kprinter and of course the settings of tdeprint were there also
valid.
But then I had an idea. If I selected in ksnapshot a larger part of the
screen, say more than half A4, what would happen?
Yes, some ugly words from me and there it was: portrait was marked but
still all 4 possibilities grayed out.
So ksnapshot decides how it wants to print and doesn't leave the user a
chance to get a result, that he wants. Utterly bull....
Any suggestion, where I could look to alter this behaviour?
Phiebie.
Hi all,
we would like to inform you that the DEB packages for Superkaramba in PSB
and PTB repositories have been updated to use Python3 instead of Python2.
Please, if you are using Superkaramba and using PSB or PTB, please test
that the sensors work with Python3 as they did with Python2. If you
experience problems, please report it.
Thank you!
Cheers
--
Slávek
Hi all;
Maybe somebody can reproduce this: opening the attached pdf in kpdf only shows the formulas, but not the text. Opening the same pdf in xpdf works flawless.
kpdf-trinity 4:14.1.0~s218-0debian12.0.0+13~b1
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
I don't know if this is or is not significant to the TDE community, but I found it
interesting.
Linux Foundation launches European division
https://www.theregister.com/2022/09/20/linux_foundation_europe/
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
Anyone know how to turn off the touchpad on my newish HP laptop? The X synaptics tool
doesn't do it.
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
In the OpenSuSE version of kcontrol, the first item in the TDE Components group is
Autostart Manager, but this item does not appear in the Debian version of kcontrol.
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
I've been doing a lot of customizing on my new Devuan machine from the root account.
When I tried to switch users to my unprivileged account I was unable to login because of
a DCOP:
| 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/leslie/.DCOPserver_palomino__1
|
| Please check that the "dcopserver" program is running!
ps aux|grep -i dcop shows
|root 15175 0.0 0.1 49316 10244 ? S 04:42 0:00 dcopserver [tdeinit] --nosid --suicide
I also see that root has .DCOPserver_<HOST>__0 and a symlink, .DCOPserver_<HOST>_:0
pointing to it; these are missing in account leslie.
Is there a way to recover from this, or do I have to recreate the account?
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
I have acquired a used HP Probook 440 G5, on which I have installed Devuan Chimaera. The
Chimaera installer balked at adding
| deb http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
| deb-src http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
which continue to fail to work after the install completed; I'm not sure just what they
provide and if they are really necessary; I couldn't find any useful information about
them in a web search.
Perhaps these need to be working before installing Trinity? I followed the install
instructions in the Trinity Wiki page
<https://wiki.trinitydesktop.org/Devuan_Trinity_Repository_Installation_Inst…>,
but
| apt-get update
fails with 'E: The repository ... does not have a Release file.' (see attached command
output, etc.).
Since all of my experience with Linux has been with openSUSE and RedHat, I'm not sure
what to do to resolve these issues. Help!? :-)
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.12
tde-config: 1.0
Hi Gianluca,
On Thu, Sep 8, 2022 at 20:31 (-0700), Gianluca Interlandi wrote:
>> are you able to attach the actual dvi file (or one showing that
>> problem, alo)? Or, if you want to send it directly to me, that is fine
>> too. I am curious as to what the issue is.
> I will send it to you separately.
Got it, see below.
On Thu, Sep 8, 2022 at 20:44 (-0700), Gianluca Interlandi wrote:
> I attach here the .tex, .dvi, .pdf files along with the EPS graphics. You
> need to have the EPS file in the same firectory as the .dvi file. The .pdf
> shows the full page with the figure. When I open the .dvi in an older
> OpenSUSE (<=13.2) distribution, then the figure appears. But in OpenSUSE
> 15.3 the figure is not there but the text is.
It worked fine for me.
I am using Slackware64 15.0. However, rather than using Slackware's
TeX packages, I just install texlive and get it over with.
Are you using texlive, or OpenSUSE's TeX packages? And, in either
case, if you copy xdvi from a working system and try it out on your
system, does it work?
You might consider submitting a bug report to the OpenSUSE people
(assuming you are using their package, and not texlive).
Jim
Hi Gianluca,
On Fri, Sep 9, 2022 at 11:41 (-0700), Gianluca Interlandi wrote:
> On Fri, 9 Sep 2022, Jim wrote:
>> On Fri, Sep 9, 2022 at 09:56 (-0700), Gianluca Interlandi wrote:
>>> https://bugs.mageia.org/show_bug.cgi?id=24941
>> This suggests that ghostscript is your problem. Did you try copying
>> that from an old system and putting it somewhere in your $PATH before
>> the system ghostscript (on your updated system)?
>> If that doesn't help, I guess you are stuck with okular. As I think I
>> said, it seems as fast as xdvi on my system. If yours is noticeably
>> slower I wonder what strange things are happening on your system.
>> (Assuming you aren't using some very old, slow computer.)
> No, okular is not slow on my system. I never implied that.
Sorry, when you said "I can use okular to display the .dvi document,
but I miss how fast xdvi is." I took it to mean that you thought
okular was slow.
> I just think that xdvi is generally more lightweight than okular,
> but okular runs well. So okular is an option if I can't figure out
> ghostscript.
It is always nice to have a Plan B.
> What exactly would I copy of ghostscript from the older system? In a
> OpenSUSE 13.2 installation I have for example:
> /usr/lib64/ghostscript/9.15/X11.so
> Would that be enough?
I'd guess not. That library provides gs the ability to output to X11
devices, and (in my tests) it is needed to display .eps images in
xdvi, but I speculate you need the ghostscript executable (which is
/usr/bin/gs on my system). If you copy that over from your old system
to your new system, don't forget it needs to be found before the
system one vis-a-vis your $PATH setting.
My version of gs has the path name for that directory hard-coded into
the executable. (On my system the path name for ghostscript's X11.so
library is '/usr/lib64/ghostscript/9.55.0', but on your system that
will be something different.)
Consequently, if you try copying the gs from your old system to your
new one, and they are different versions of gs (which is presumably
the case) you will have to create the correctly-named directory on
your new system and put the library in that directory.
With luck, the old version of gs will play nicely with the
(presumably) newer versions of all the libraries on your new system.
If it doesn't, you can go deeper down the rabbit hole in a number of
ways, but at that point you might want to accept defeat and use
okular. (I could suggest some ways to proceed, but I really doubt you
will find the spending of the required time productive. Much better
to get on with blood clotting research. My vet tells me dog blood
clots many times faster than human blood, but I didn't have the
presence of mind to ask her if she knew why that is so. Maybe you
know.)
> I also realized that my subject line should have read "OpenSUSE 15.2", not
> 15.3, but that may not be as relevant now.
Only, I suppose, if you were submitting a bug report or talking to
another OpenSUSE person about this issue.
Jim