1:05 p.m.
Is anybody else having a problem with kbuildsycoa crashing in FC5? If
so, has anybody found a solution?
FWIW here is the BT:
[tspdlp@lemix ~]$ uname -a
Linux lemix.tmcaz.com 2.6.16-1.2122_FC5smp #1 SMP Sun May 21 15:18:32
EDT 2006 i686 i686 i386 GNU/Linux
Using host libthread_db library "/lib/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1208387072 (LWP 4423)]
[KCrash handler]
#6 0x03bec459 in operator== () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#7 0x0011c5b1 in VFolderMenu::processMenu (this=0xa283568,
docElem=@0xbfdb7fdc, pass=1) at vfolder_menu.cpp:1231
#8 0x0011c726 in VFolderMenu::processMenu (this=0xa283568,
docElem=@0xbfdb824c, pass=1) at vfolder_menu.cpp:1375
#9 0x0011c726 in VFolderMenu::processMenu (this=0xa283568,
docElem=@0xbfdb84bc, pass=1) at vfolder_menu.cpp:1375
#10 0x0011c726 in VFolderMenu::processMenu (this=0xa283568,
docElem=@0xbfdb8660, pass=1) at vfolder_menu.cpp:1375
#11 0x001230d5 in VFolderMenu::parseMenu (this=0xa283568,
file=@0xbfdb8748,
forceLegacyLoad=true) at vfolder_menu.cpp:1611
#12 0x00126299 in KBuildSycoca::build (this=0x9ab6c40) at
kbuildsycoca.cpp:384
#13 0x00126802 in KBuildSycoca::recreate (this=0x9ab6c40)
at kbuildsycoca.cpp:519
#14 0x00127194 in kdemain (argc=1, argv=0xbfdb8c24) at
kbuildsycoca.cpp:924
#15 0x08048482 in main (argc=) at kbuildsycoca.la.cpp:2
#16 0x00a2d724 in __libc_start_main () from /lib/libc.so.6
#17 0x080483d1 in _start ()
Paul Lemmons
Lead Systems Software Engineer
TMC HealthCare
1:27 p.m.
Paul Lemmons wrote:
Is anybody else having a problem with kbuildsycoa crashing in FC5?
If
so, has anybody found a solution?
FWIW here is the BT:
[tspdlp@lemix ~]$ uname -a
Linux lemix.tmcaz.com 2.6.16-1.2122_FC5smp #1 SMP Sun May 21 15:18:32
EDT 2006 i686 i686 i386 GNU/Linux
Using host libthread_db library "/lib/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1208387072 (LWP 4423)]
[KCrash handler]
#6 0x03bec459 in operator== () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#7 0x0011c5b1 in VFolderMenu::processMenu (this=0xa283568,
docElem=@0xbfdb7fdc, pass=1) at vfolder_menu.cpp:1231
I was seeing pretty much the exact same backtrace. Are you on a system
that's been upgraded from FC4? I fixed the problem by copying
/etc/xdg/menus from another machine with a fresh FC5 install.
HTH,
Joe
1:36 p.m.
FWIW, I'm seeing the same crash on FC5 (x86) (and I had been seeing it
in FC4 until switching to the kde-redhat yum repo). I don't have any
fresh FC5 installs to get the contents of /etc/xdg/menus from. Can
someone possibly tar their's up and send it to me (off list)?
On 5/30/06, Joe Conway <mail(a)joeconway.com> wrote:
Paul Lemmons wrote:
> Is anybody else having a problem with kbuildsycoa crashing in FC5? If
> so, has anybody found a solution?
>
> FWIW here is the BT:
>
> [tspdlp@lemix ~]$ uname -a
> Linux lemix.tmcaz.com 2.6.16-1.2122_FC5smp #1 SMP Sun May 21 15:18:32
> EDT 2006 i686 i686 i386 GNU/Linux
>
> Using host libthread_db library "/lib/libthread_db.so.1".
> `shared object read from target memory' has disappeared; keeping its
> symbols.
> [Thread debugging using libthread_db enabled]
> [New Thread -1208387072 (LWP 4423)]
> [KCrash handler]
> #6 0x03bec459 in operator== () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #7 0x0011c5b1 in VFolderMenu::processMenu (this=0xa283568,
> docElem=@0xbfdb7fdc, pass=1) at vfolder_menu.cpp:1231
I was seeing pretty much the exact same backtrace. Are you on a system
that's been upgraded from FC4? I fixed the problem by copying
/etc/xdg/menus from another machine with a fresh FC5 install.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama(a)gmail.com
LlamaLand http://netllama.linux-sxs.org
3 p.m.
On Tue, 2006-05-30 at 11:36 -0700, Lonni J Friedman wrote:
FWIW, I'm seeing the same crash on FC5 (x86) (and I had been
seeing it
in FC4 until switching to the kde-redhat yum repo). I don't have any
fresh FC5 installs to get the contents of /etc/xdg/menus from. Can
someone possibly tar their's up and send it to me (off list)?
The tar file is on its way to you...
3:23 p.m.
On Tue, 2006-05-30 at 13:00 -0700, Paul Lemmons wrote:
On Tue, 2006-05-30 at 11:36 -0700, Lonni J Friedman wrote:
> FWIW, I'm seeing the same crash on FC5 (x86) (and I had been seeing it
> in FC4 until switching to the kde-redhat yum repo). I don't have any
> fresh FC5 installs to get the contents of /etc/xdg/menus from. Can
> someone possibly tar their's up and send it to me (off list)?
The tar file is on its way to you...
--
Can you send me the file as well?
Thanks,
James
1:42 p.m.
On Tue, 2006-05-30 at 11:27 -0700, Joe Conway wrote:
Paul Lemmons wrote:
> Is anybody else having a problem with kbuildsycoa crashing in FC5? If
> so, has anybody found a solution?
>
> FWIW here is the BT:
>
> [tspdlp@lemix ~]$ uname -a
> Linux lemix.tmcaz.com 2.6.16-1.2122_FC5smp #1 SMP Sun May 21 15:18:32
> EDT 2006 i686 i686 i386 GNU/Linux
>
> Using host libthread_db library "/lib/libthread_db.so.1".
> `shared object read from target memory' has disappeared; keeping its
> symbols.
> [Thread debugging using libthread_db enabled]
> [New Thread -1208387072 (LWP 4423)]
> [KCrash handler]
> #6 0x03bec459 in operator== () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #7 0x0011c5b1 in VFolderMenu::processMenu (this=0xa283568,
> docElem=@0xbfdb7fdc, pass=1) at vfolder_menu.cpp:1231
I was seeing pretty much the exact same backtrace. Are you on a system
that's been upgraded from FC4? I fixed the problem by copying
/etc/xdg/menus from another machine with a fresh FC5 install.
HTH,
Joe
I have the exact same problem, and I've even switched to gnome because
of it. Of course I still get the error when running a kde app like
klipper.
I backed up and removed FC4 and then installed a fresh FC5. BUT, I did
copy a a lot of my old home directory over from my FC4 install. So maybe
something in there is causing it?
Thanks,
James
1:52 p.m.
On 5/30/06, James Pifer <jep(a)obrien-pifer.com> wrote:
On Tue, 2006-05-30 at 11:27 -0700, Joe Conway wrote:
> Paul Lemmons wrote:
> > Is anybody else having a problem with kbuildsycoa crashing in FC5? If
> > so, has anybody found a solution?
> >
> > FWIW here is the BT:
> >
> > [tspdlp@lemix ~]$ uname -a
> > Linux lemix.tmcaz.com 2.6.16-1.2122_FC5smp #1 SMP Sun May 21 15:18:32
> > EDT 2006 i686 i686 i386 GNU/Linux
> >
> > Using host libthread_db library "/lib/libthread_db.so.1".
> > `shared object read from target memory' has disappeared; keeping its
> > symbols.
> > [Thread debugging using libthread_db enabled]
> > [New Thread -1208387072 (LWP 4423)]
> > [KCrash handler]
> > #6 0x03bec459 in operator== () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> > #7 0x0011c5b1 in VFolderMenu::processMenu (this=0xa283568,
> > docElem=@0xbfdb7fdc, pass=1) at vfolder_menu.cpp:1231
>
> I was seeing pretty much the exact same backtrace. Are you on a system
> that's been upgraded from FC4? I fixed the problem by copying
> /etc/xdg/menus from another machine with a fresh FC5 install.
>
> HTH,
>
> Joe
>
I have the exact same problem, and I've even switched to gnome because
of it. Of course I still get the error when running a kde app like
klipper.
I backed up and removed FC4 and then installed a fresh FC5. BUT, I did
copy a a lot of my old home directory over from my FC4 install. So maybe
something in there is causing it?
On my system, this is impacting all users (including newly created
users). I doubt its related to the contents of $HOME.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama(a)gmail.com
LlamaLand http://netllama.linux-sxs.org
1:58 p.m.
On Tue, 2006-05-30 at 14:42 -0400, James Pifer wrote:
On Tue, 2006-05-30 at 11:27 -0700, Joe Conway wrote:
> Paul Lemmons wrote:
> > Is anybody else having a problem with kbuildsycoa crashing in FC5? If
> > so, has anybody found a solution?
> >
> > FWIW here is the BT:
> >
> > [tspdlp@lemix ~]$ uname -a
> > Linux lemix.tmcaz.com 2.6.16-1.2122_FC5smp #1 SMP Sun May 21 15:18:32
> > EDT 2006 i686 i686 i386 GNU/Linux
> >
> > Using host libthread_db library "/lib/libthread_db.so.1".
> > `shared object read from target memory' has disappeared; keeping its
> > symbols.
> > [Thread debugging using libthread_db enabled]
> > [New Thread -1208387072 (LWP 4423)]
> > [KCrash handler]
> > #6 0x03bec459 in operator== () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> > #7 0x0011c5b1 in VFolderMenu::processMenu (this=0xa283568,
> > docElem=@0xbfdb7fdc, pass=1) at vfolder_menu.cpp:1231
>
> I was seeing pretty much the exact same backtrace. Are you on a system
> that's been upgraded from FC4? I fixed the problem by copying
> /etc/xdg/menus from another machine with a fresh FC5 install.
>
> HTH,
>
> Joe
>
I have the exact same problem, and I've even switched to gnome because
of it. Of course I still get the error when running a kde app like
klipper.
I backed up and removed FC4 and then installed a fresh FC5. BUT, I did
copy a a lot of my old home directory over from my FC4 install. So maybe
something in there is causing it?
Thanks,
James
It looks like I am not the only one to meet this problem. I have an
"official" bug opened. Maybe if we all added our experiences to the bug
it would get some attention?
http://bugs.kde.org/show_bug.cgi?id=125924
3:33 p.m.
On 5/30/06, Paul Lemmons <paul.lemmons(a)tmcaz.com> wrote:
On Tue, 2006-05-30 at 14:42 -0400, James Pifer wrote:
> On Tue, 2006-05-30 at 11:27 -0700, Joe Conway wrote:
> > Paul Lemmons wrote:
> > > Is anybody else having a problem with kbuildsycoa crashing in FC5? If
> > > so, has anybody found a solution?
> > >
> > > FWIW here is the BT:
> > >
> > > [tspdlp@lemix ~]$ uname -a
> > > Linux lemix.tmcaz.com 2.6.16-1.2122_FC5smp #1 SMP Sun May 21 15:18:32
> > > EDT 2006 i686 i686 i386 GNU/Linux
> > >
> > > Using host libthread_db library "/lib/libthread_db.so.1".
> > > `shared object read from target memory' has disappeared; keeping its
> > > symbols.
> > > [Thread debugging using libthread_db enabled]
> > > [New Thread -1208387072 (LWP 4423)]
> > > [KCrash handler]
> > > #6 0x03bec459 in operator== () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> > > #7 0x0011c5b1 in VFolderMenu::processMenu (this=0xa283568,
> > > docElem=@0xbfdb7fdc, pass=1) at vfolder_menu.cpp:1231
> >
> > I was seeing pretty much the exact same backtrace. Are you on a system
> > that's been upgraded from FC4? I fixed the problem by copying
> > /etc/xdg/menus from another machine with a fresh FC5 install.
> >
> > HTH,
> >
> > Joe
> >
>
> I have the exact same problem, and I've even switched to gnome because
> of it. Of course I still get the error when running a kde app like
> klipper.
>
> I backed up and removed FC4 and then installed a fresh FC5. BUT, I did
> copy a a lot of my old home directory over from my FC4 install. So maybe
> something in there is causing it?
>
> Thanks,
> James
>
It looks like I am not the only one to meet this problem. I have an
"official" bug opened. Maybe if we all added our experiences to the bug
it would get some attention?
http://bugs.kde.org/show_bug.cgi?id=125924
Wouldn't it have made more sense to open the bug in Redhats bugzilla?
I seriously doubt that this is a generic KDE bug, or it would have
been fixed long ago.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama(a)gmail.com
LlamaLand http://netllama.linux-sxs.org
6:15 p.m.
On Tue, 2006-05-30 at 11:58 -0700, Paul Lemmons wrote:
It looks like I am not the only one to meet this problem. I have an
"official" bug opened. Maybe if we all added our experiences to the bug
it would get some attention?
I have updated the bug report with our findings. Thank you everybody! It
is nice to see things working again!
Paul Lemmons
Lead Systems Software Engineer
TMC HealthCare
2:58 p.m.
On Tue, 2006-05-30 at 11:27 -0700, Joe Conway wrote:
I was seeing pretty much the exact same backtrace. Are you on a
system
that's been upgraded from FC4? I fixed the problem by copying
/etc/xdg/menus from another machine with a fresh FC5 install.
HTH,
Joe
This did indeed fix the problem. Thank you!
Paul Lemmons
Lead Systems Software Engineer
TMC HealthCare
3:18 p.m.
Just out of curiosity... do the people who have this problem have
crossover office installed? Just to see what the difference might be I
ran:
$ diff -r menus etc_xdg_menus/
Only in etc_xdg_menus/applications-merged: cxlegacy.menu
Only in menus: gnome-screensavers.menu
Only in etc_xdg_menus/kde-applications-merged: cxlegacy.menu
Only in menus/preferences-post-merged:
gnome-screensaver-hide-xscreensaver.menu
"menus" is from the clean FC5 install
and
"etc_xdg_menus" is a backup of the problem dir
It looks like the only differences appear to be in the inclusion of:
cxlegacy.menu
and
gnome-screensavers.menu
I would not expect the gnome stuff to be a problem as it is probably on
everybody's machine and more people would be complaining. But the cx
stuff may be unique...
3:36 p.m.
On Tue, 2006-05-30 at 13:18 -0700, Paul Lemmons wrote:
Just out of curiosity... do the people who have this problem have
crossover office installed? Just to see what the difference might be I
ran:
$ diff -r menus etc_xdg_menus/
Only in etc_xdg_menus/applications-merged: cxlegacy.menu
Only in menus: gnome-screensavers.menu
Only in etc_xdg_menus/kde-applications-merged: cxlegacy.menu
Only in menus/preferences-post-merged:
gnome-screensaver-hide-xscreensaver.menu
"menus" is from the clean FC5 install
and
"etc_xdg_menus" is a backup of the problem dir
It looks like the only differences appear to be in the inclusion of:
cxlegacy.menu
and
gnome-screensavers.menu
I would not expect the gnome stuff to be a problem as it is probably on
everybody's machine and more people would be complaining. But the cx
stuff may be unique...
--
Yes, I have crossover office installed.
James
3:38 p.m.
On 5/30/06, James Pifer <jep(a)obrien-pifer.com> wrote:
On Tue, 2006-05-30 at 13:18 -0700, Paul Lemmons wrote:
> Just out of curiosity... do the people who have this problem have
> crossover office installed? Just to see what the difference might be I
> ran:
>
> $ diff -r menus etc_xdg_menus/
> Only in etc_xdg_menus/applications-merged: cxlegacy.menu
> Only in menus: gnome-screensavers.menu
> Only in etc_xdg_menus/kde-applications-merged: cxlegacy.menu
> Only in menus/preferences-post-merged:
> gnome-screensaver-hide-xscreensaver.menu
>
>
> "menus" is from the clean FC5 install
> and
> "etc_xdg_menus" is a backup of the problem dir
>
> It looks like the only differences appear to be in the inclusion of:
>
> cxlegacy.menu
> and
> gnome-screensavers.menu
>
> I would not expect the gnome stuff to be a problem as it is probably on
> everybody's machine and more people would be complaining. But the cx
> stuff may be unique...
> --
Yes, I have crossover office installed.
Same here.
Wiping out /etc/xdg/menus and replacing it with a 'pristine' copy
works around the problem.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama(a)gmail.com
LlamaLand http://netllama.linux-sxs.org
4 p.m.
Paul Lemmons wrote:
Just out of curiosity... do the people who have this problem have
crossover office installed? Just to see what the difference might be I
ran:
$ diff -r menus etc_xdg_menus/
Only in etc_xdg_menus/applications-merged: cxlegacy.menu
Only in menus: gnome-screensavers.menu
Only in etc_xdg_menus/kde-applications-merged: cxlegacy.menu
Only in menus/preferences-post-merged:
gnome-screensaver-hide-xscreensaver.menu
"menus" is from the clean FC5 install
and
"etc_xdg_menus" is a backup of the problem dir
It looks like the only differences appear to be in the inclusion of:
cxlegacy.menu
and
gnome-screensavers.menu
I would not expect the gnome stuff to be a problem as it is probably on
everybody's machine and more people would be complaining. But the cx
stuff may be unique...
Yes, I do run crossover. Here is a snippet from the diff:
8<----------------------------------------------------------
diff -cNr menus.old/applications-merged/cxlegacy.menu
menus/applications-merged/cxlegacy.menu
*** menus.old/applications-merged/cxlegacy.menu Mon Aug 16 15:14:24 2004
--- menus/applications-merged/cxlegacy.menu Wed Dec 31 16:00:00 1969
***************
*** 1,5 ****
- <!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
"http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd">
- <!-- File Created by CrossOver Office cxmenu -->
- <Menu>
- <Name>Applications</Name>
- <LegacyDir>/opt/cxoffice/support/xdg-legacy-menus</LegacyDir></Menu>
--- 0 ----
diff -cNr menus.old/gnome-screensavers.menu menus/gnome-screensavers.menu
*** menus.old/gnome-screensavers.menu Wed Dec 31 16:00:00 1969
--- menus/gnome-screensavers.menu Mon Apr 10 15:41:03 2006
***************
*** 0 ****
--- 1,13 ----
+ <!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
+ "http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd">
+
+ <Menu>
+
+ <Name>Screensavers</Name>
+ <AppDir>/usr/share/gnome-screensaver/themes</AppDir>
+ <Directory>gnome-screensaver.directory</Directory>
+ <Include>
+ <Category>Screensaver</Category>
+ </Include>
+
+ </Menu>
8<----------------------------------------------------------
I'm not sure if this is the problem, but the crossover entry that is now
gone is missing some of the tags in that "Screensavers" section that
replaces it -- namely <AppDir>, <Directory>, and <Include>. I'd bet
one
or more of those nodes being missing is causing the crash.
Joe
4:27 p.m.
Joe Conway wrote:
Paul Lemmons wrote:
> Just out of curiosity... do the people who have this problem have
> crossover office installed? Just to see what the difference might be I
Just to follow up -- it seems the file
/etc/xdg/menus/applications-merged/cxlegacy.menu
is the culprit. It is apparently missing a <Menu> node wrapped around
the <LegacyDir> tags. The following patch fixes the problem for me:
8<-------------------------------
diff -cNr menus.old/applications-merged/cxlegacy.menu
menus/applications-merged/cxlegacy.menu
*** menus.old/applications-merged/cxlegacy.menu Tue May 30 14:19:47 2006
--- menus/applications-merged/cxlegacy.menu Tue May 30 14:19:54 2006
***************
*** 1,5 ****
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
"http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd">
<!-- File Created by CrossOver Office cxmenu -->
<Menu>
! <Name>Applications</Name>
! <LegacyDir>/opt/cxoffice/support/xdg-legacy-menus</LegacyDir></Menu>
--- 1,12 ----
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
"http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd">
<!-- File Created by CrossOver Office cxmenu -->
+ <!-- Modified by JEC to fix kbuildsycoca crash -->
+
<Menu>
! <Name>Applications</Name>
! <Menu>
!
<LegacyDir>/opt/cxoffice/support/xdg-legacy-menus</LegacyDir>
! </Menu>
! </Menu>
!
!
8<-------------------------------
So this is really a Crossover Office bug, more than likely.
BTW, I also found that kbuildsycoca crashes on FC5 if scim-qtimm is
installed (at least on x86_64).
HTH,
Joe
1:46 a.m.
Thanks for sharing this! I had the EXACT same problem and I also have
CrossOver Office. I did open a bug report at
kde-redhat.sourceforge.net, now I'll have to close it out with the
result.
Many thanks,
Brian
On Tue, 2006-05-30 at 14:27 -0700, Joe Conway wrote:
Joe Conway wrote:
> Paul Lemmons wrote:
>
>> Just out of curiosity... do the people who have this problem have
>> crossover office installed? Just to see what the difference might be I
Just to follow up -- it seems the file
/etc/xdg/menus/applications-merged/cxlegacy.menu
is the culprit. It is apparently missing a <Menu> node wrapped around
the <LegacyDir> tags. The following patch fixes the problem for me:
8<-------------------------------
diff -cNr menus.old/applications-merged/cxlegacy.menu
menus/applications-merged/cxlegacy.menu
*** menus.old/applications-merged/cxlegacy.menu Tue May 30 14:19:47 2006
--- menus/applications-merged/cxlegacy.menu Tue May 30 14:19:54 2006
***************
*** 1,5 ****
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
"http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd">
<!-- File Created by CrossOver Office cxmenu -->
<Menu>
! <Name>Applications</Name>
! <LegacyDir>/opt/cxoffice/support/xdg-legacy-menus</LegacyDir></Menu>
--- 1,12 ----
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
"http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd">
<!-- File Created by CrossOver Office cxmenu -->
+ <!-- Modified by JEC to fix kbuildsycoca crash -->
+
<Menu>
! <Name>Applications</Name>
! <Menu>
!
<LegacyDir>/opt/cxoffice/support/xdg-legacy-menus</LegacyDir>
! </Menu>
! </Menu>
!
!
8<-------------------------------
So this is really a Crossover Office bug, more than likely.
BTW, I also found that kbuildsycoca crashes on FC5 if scim-qtimm is
installed (at least on x86_64).
HTH,
Joe
6563
days inactive
6564
days old
16 comments
5 participants
participants (5)
-
Brian Wright -
James Pifer -
Joe Conway -
Lonni J Friedman -
Paul Lemmons