Visitar URL original
Cannot open text file · Issue #3939 · ControlSystemStudio/phoebus · GitHub
Skip to content

Cannot open text file #3939

Open
Open

Description

@sifriede

Dear CSS developer,

I've set

org.phoebus.framework.workbench/external_app_text=Text Editor,txt|dat|py|ini|db|xml|xsl|css|cmd|sh|st|log|out|md|shp,gedit

and Ihave verified (via Help->About->Show Details) that the setting was applied correctly, but it shows:

Image

The "Error Log" does not show anything concerning this matter.

CS Studio Version: 5.0.2
OS: Debian 13 - Cinnamon (gedit is installed and fully functional)

/usr/bin/gedit did not change anything.

Best regards
Simon

Activity

  1. georgweiss commented on Sep 28, 2026

    @georgweiss
    Collaborator

    @sifriede, how did you trigger the open action?

  2. sifriede commented on Sep 28, 2026

    @sifriede
    Author

    Dear Georg,

    Inside the file browser app I've double clicked on test.txt

    Image

    Best regards
    Simon

    P.S: But I see what your question could be refering to. Using an action button it perfectly opens the text file with gedit.
    I thought this setting would also apply to the file browser.

    Image
  3. kasemir commented on Sep 28, 2026

    @kasemir
    Collaborator

    Is there no message on the console?
    When gedit is not available, it should look like this:

    2026-09-28 10:06:37 WARNING [org.phoebus.framework.jobs] Job 'gedit' failed
    java.io.IOException: Cannot run program "gedit" (in directory "/Users/xxx"): Exec failed, error: 2 (No such file or directory) 
    	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1112)
    	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1046)
    	at org.phoebus.framework.jobs.CommandExecutor.call(CommandExecutor.java:116)
    	at org.phoebus.framework.workbench.ExternalApplication.lambda$create$1(ExternalApplication.java:87)
    
  4. georgweiss commented on Sep 28, 2026

    @georgweiss
    Collaborator

    From the error dialog it looks like there's a blank char prepended to the file name, but would need to investigate more to confirm. Can test only on Ubuntu and Mac OS (where it works).

  5. sifriede commented on Sep 28, 2026

    @sifriede
    Author

    No, really, there is nothing appearing on the Error log:
    (Here I've cleared the log, before clicking)

    Image
  6. kasemir commented on Sep 28, 2026

    @kasemir
    Collaborator

    I think the space is from the format in messages.properties that has a space after the Cannot open\n'

    OpenAlert1=Cannot open\n  
    OpenAlert2=,\nsee log for details
    
  7. kasemir commented on Sep 28, 2026

    @kasemir
    Collaborator

    There's actually no such space (pas d'espace) in the French version:

    OpenAlert1=Impossible d'ouvrir\n
    OpenAlert2=,\nvoir le journal pour plus de détails
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions