Version: 1.60 (using KDE 3.5.9) Installed from: Compiled From Sources Compiler: gcc version 4.1.2 20070925 (Red Hat 4.1.2-33) running on Fedora Core 8, x86_64, Dell D830 Latitude notebook OS: Linux have been running the FC8 packaged version of kst (1.5.0) on multi-column ascii data files with no trouble. removed the packaged FC8 kst with rpm -e. downloaded source for kst and compiled it, no errors, installed to /usr/local, created /etc/ld.so.conf.d config files, ran ldconfig. kst datasource files appear in /usr/local/lib64/kde3, including kstdata_ascii.{so,la}, various kst libraries in /usr/local/lib64 When I run kst-1.6.0 with the same command line options as before on the same data files (e.g. kst -x 1 -y 3 -y 5 data3&), kst comes up and paints x-y axes with both ranges 0.0 to 1.0 but plots no curves. I get the red alert icon at the lower right-hand portion of the screen. I click on it, and see this (log tab): (blue disc)2008-04-30 20:06 Scanning for data-source plugins. (blue disc)2008-04-30 20:06 Scanning for data-object plugins. (blue disc)2008-04-30 20:06 Scanning for data-source plugins. (blue disc)2008-04-30 20:06 Failed to load file 'data3'. The "data sources" tab display is empty. The "Build Information" tab shows Kst version 1.6.0(EV) If I click the "Email debugging information" button, the application hangs. (I don't have Kmail installed, but I do have an alternative mail client selected under Kcontrol->KDE Components->Component Chooser->Email Client. Dunno what that's about, but it's a *different* problem, I assume. The first few lines of the data3 file above are: 1 1 1 1 1 2 1 2 1 2 3 1 3 1 3 4 1 4 1 4 5 1 5 1 5 6 1 6 1 6 7 1 7 1 7 8 1 8 1 8 9 1 9 1 9 10 1 10 1 10 _____________________________________________________ I now mv the kst-1.6.0 binaries and libraries out of the way, reinstall the x86_64 kst-1.5.0 package from the FC8 repository, and run (FC8) kst-1.5.0. Kst displays the data as I expect. When I go to the kst debug panel, I see in the log tab: 2008-04-30 20:21 Scanning for data-source plugins. 2008-04-30 20:21 Scanning for data-object plugins. 2008-04-30 20:21 Loaded data-object plugin Periodogram. 2008-04-30 20:21 Loaded data-object plugin Cross Power Spectrum. 2008-04-30 20:21 Loaded data-object plugin Chop. 2008-04-30 20:21 Loaded data-object plugin Bin. 2008-04-30 20:21 Loaded data-object plugin Syncbin. 2008-04-30 20:21 Loaded data-object plugin Cumulative sum (integral). 2008-04-30 20:21 Loaded data-object plugin Effective Bandwidth. 2008-04-30 20:21 Loaded data-object plugin Binned Map. 2008-04-30 20:21 Loaded data-object plugin Statistics. 2008-04-30 20:21 Loaded data-object plugin Generic filter. 2008-04-30 20:21 Loaded data-object plugin Phase. 2008-04-30 20:21 Loaded data-object plugin Fixed-step differentiation. 2008-04-30 20:21 Loaded data-object plugin Shift. (all lines preceded by blue discs) and in the Data Sources directory I see: ASCII File Reader DirFile Reader Frame Reader Indirect File Reader qimagesource __________________________________________________________________________ I've googled for similar problems online, no joy. Haven't been able to find a forum or users' group dedicated to kst, so here I am. Any tips, pointers to fora or user groups, whatever would be appreciated. I imagine this is something *really* simple, but I haven't been able to find any guidance that would tell me how to debug the problem.
Huh. Not that this invalidates this bug, but is there a specific reason you want kst 1.6.0 over 1.5.0? That said, I am the Fedora rpm packager, and 1.6.0 is in the buildsystem and will get pushed out in a week or so (should be pushed to -testing tomorrow; stable in a week). If you don't want to wait, you could test out the rpms now (just download and install the appropriate rpms): http://koji.fedoraproject.org/koji/buildinfo?buildID=47190 If you do that, please post your success or failure here.
1.7.0 has now been released. Assuming, there are no complaints for the new version I'll withdraw this bug report.
without any further complaints or information i'll withdraw this bug report. please reopen if this is still an issue for 1.7.0