Version: (using KDE 4.1.0) Installed from: SuSE RPMs OS: Linux I'm trying to open a .vi (Labview) file with Dolphin (or even Konqueror). I can open it fine by passing the paths through the command line, e.g: anshul@sagarika:~> ls ate freetype2-2.3.7-999.subpixel.1.i586.rpm public_html ate.tar.gz freetype2-feature-subpixel-hinting-2.3.7-999.subpixel.1.i586.rpm Test Selector.vi bin internet Working Folder Desktop LabVIEW Data Working_Folder Documents Labview Presentation.odp anshul@sagarika:~> labview Test\ Selector.vi However, if I try to double click and open the same under Dolphin or Konqueror, the Labview application starts and reports an error saying that /home/anshul/Test is not a valid Labview file. It seems that while opening under Dolphin it dosen't pass the rest of the data after a space, i.e. Test Selector.vi has a space between Test and Selector. On KDE3 this has been working fine. -Anshul
Can you still reproduce this bug with a recent KDE version? (4.1.3 / 4.2beta1 / 4.2beta2 / 4.2svn) ? Thanks :)
Hi, Apologies for the late reply...I'm still suffering from this bug under Mandriva 2009.0 w/ 4.2.0 RPMs. However, I'm able to get past this issue by performing the following change :- Existing:- [root@sagarika anshul]# cat /usr/local/natinst/LabVIEW-8.6/etc/desktop/apps/ labview.applications natinst-labview86.desktop [root@sagarika anshul]# cat /usr/local/natinst/LabVIEW-8.6/etc/desktop/apps/labview.applications labview command=/bin/sh -c "`cat /etc/natinst/labview/labview.dir`/labview \$0 \$*" -launch name=LabVIEW can_open_multiple_files=true expects_uris=false requires_terminal=false mime_types=application/x-labview-* [root@sagarika anshul]# cat /usr/local/natinst/LabVIEW-8.6/etc/desktop/apps/labview.applications Changed the "command line" to:- command=labview
The original command line seemed to be a little complex. Had you tried opening .vi files under Gnome or another desktop. May be it was the launcher file fault.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!