On Tuesday 30 April 2019 15:06:22 Gene Heskett wrote:
> On Tuesday 30 April 2019 17:27:42 E. Liddell wrote:
> > On Tue, 30 Apr 2019 09:27:25 -0400
> >
> > Gene Heskett <gheskett@...> 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?
>
> > E. Liddell
> >
> >

> Cheers, Gene Heskett

Comes with new KDE, etc., not sure what else. It's not TDE.

Bill