On Mon, Jul 7, 2008 at 9:52 PM, Lars Lindner <[EMAIL PROTECTED]> wrote: > This can be caused by the browser command returning an exit code != 0 > despite launching the URL. In such a case Liferea tries to rerun the > browser command again asynchronously. > > I think Liferea behaves correctly as the only way to know if the executed > command did work is the exit code and relying on it is the only way. > > If you want to see what happens run with --debug-gui and there will > be traces of the command launch. To further analyze this try > to run the "failed" command manually and check the exit code.
You are right, with --debug-gui and "new tab" mode Liferea outputs the following: GUI: launch URL: false true 0 GUI: Running the browser-remote sync command 'firefox -a firefox -remote openURL(http://rss.slashdot.org/~r/Slashdot/slashdot/~3/329092553/article.pl,new-tab)' GUI: Running the browser-remote async command 'firefox http://rss.slashdot.org/~r/Slashdot/slashdot/~3/329092553/article.pl' When the commands are run manually: $ firefox -a firefox -remote 'openURL(http://rss.slashdot.org/~r/Slashdot/slashdot/~3/329092553/article.pl,new-tab)' Error: Failed to send command: 500 command not parseable Segmentation fault $ firefox http://rss.slashdot.org/~r/Slashdot/slashdot/~3/329092553/article.pl Segmentation fault Obviously there is something wrong with Firefox. However, the first command does not open a tab when I run it manually, maybe I'm missing something? -- Heikki Hokkanen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
