1 May
2019
1 May
'19
2:22 a.m.
On Tue, 30 Apr 2019 21:47:41 -0400
Gene Heskett <gheskett(a)shentel.net> wrote:
On Tuesday 30 April 2019 20:34:09 E. Liddell wrote:
kpdf is on the menu under "Office" for me. No idea why it doesn't
show up for you--it's probably a packaging boondoggle.
On Tue, 30 Apr 2019 18:06:22 -0400
Gene Heskett <gheskett(a)shentel.net> wrote:
Thats a bit odd, this is an R14.0.6 install, but its not in either office
or graphics sections of the menu. Xpdf is there, but its yet to do a
print job anywhere near complete or correct. Reinstalled it, still can't
be found. Does run by cli. On Tuesday 30 April 2019 17:27:42 E. Liddell
wrote:
Um, no. Note that your error messages above refer to kdeui and
kdelibs, not tdeui and tdelibs, even though these modules were renamed
in TDE.
On Tue, 30 Apr 2019 09:27:25 -0400
Gene Heskett <gheskett(a)shentel.net> wrote:
> okular seems to run ok most of the time, but when run from the
> cli logs this:
>
> gene@coyote:~/linuxcnc/nc_files$ okular
> okular(1985)/kdecore (KConfigSkeleton)
> KCoreConfigSkeleton::writeConfig: okular(1985)/kdecore
> (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
> okular(1985)/kdecore (KConfigSkeleton)
> KCoreConfigSkeleton::writeConfig: okular(1985)/kdecore
> (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
> okular(1985)/kdecore (KConfigSkeleton)
> KCoreConfigSkeleton::writeConfig: okular(1985)/kdeui (kdelibs)
> KXMLGUIClient::~KXMLGUIClient: 0x8cef5b0 deleted without having
> been removed from the factory first. This will leak standalone
> popupmenus and could lead to crashes.
>
> This is my fav pdf reader, and I get 3 to 4 weeks uptime before
> something goes to pot and I need to reboot this old wheezy
> install.
>
> Connected? IDK, maybe... I have a stretch testing image from
> the LCNC folks that I put on an old Dell out in the garage as
> the sacrificial goat, and its running quite well so far, so this
> wheezy may get retired finally. Sometime in the next week or two
> if the creek doesn't get too high. :)
okular is kde5/qt5, so it's a moving target. A quick search
suggests that this is a known bug (possibly two separate bugs),
it's been fixed, and you're running a very old version.
So, yeah, you might want to update to something a little more
modern.
Huh? I thought it was part of the kde fork? If not, then what am I supposed to be using?
The default TDE program for viewing PDFs is kpdf, in tdegraphics.
That doesn't mean you have to use it if it doesn't suit your needs, of
course.
E. Liddell But whats all this?
gene@coyote:~/linuxcnc/nc_files$ kpdf
/etc/magic, 4: Warning: using regular magic file
`/etc/trinity/magic/tdeio.magic'
/etc/magic, 4: Warning: using regular magic file
`/etc/trinity/magic/tdeio.magic'
/etc/trinity/magic/tdeio.magic, 17: Warning: using regular magic file
`/etc/trinity/magic/drgeo.magic'
/etc/magic, 4: Warning: using regular magic file
`/etc/trinity/magic/tdeio.magic'
/etc/trinity/magic/tdeio.magic, 17: Warning: using regular magic file
`/etc/trinity/magic/drgeo.magic'
/etc/trinity/magic/drgeo.magic, 2: Warning: using regular magic file
`/etc/trinity/magic/cabri.magic'
/etc/magic, 4: Warning: using regular magic file
`/etc/trinity/magic/tdeio.magic'
/etc/trinity/magic/tdeio.magic, 17: Warning: using regular magic file
`/etc/trinity/magic/drgeo.magic'
/etc/trinity/magic/drgeo.magic, 2: Warning: using regular magic file
`/etc/trinity/magic/cabri.magic'
/etc/trinity/magic/cabri.magic, 2: Warning: using regular magic file
`/etc/trinity/magic/kolf.magic'
It doesn't like the format of some magic number files, it looks like.
Should be harmless.
I loaded up a 750 page linuxcnc documentation pdf, and
while its all
there, it doesn't quite have the pretty print pizzazz that evince or
okular gives.
It all depends on what you need. My needs in terms of PDF viewing
are pretty basic.
You might think 50 u-secs is quick, but I have 2
machines here that can
respond to a scheduled IRQ with a worst case wobble in the 4 to 6 u-sec
range. Intel Atoms of course. Amd lost that fight years ago.
Ah, well there we will have to disagree. I've always bought AMD CPUs,
and I'm quite pleased with my current Threadripper. Mind you, I'm not
using it for CNC or other realtime-sensitive applications.
E. Liddell