sakura -e and sakura -x does not work?

Asked by Ol on 2015-10-08


I cannot get sakura -h -x alsamixer or sakura -h -e alsamixer to work?

Is it broken?

Question information

English Edit question
Sakura Edit question
No assignee Edit question
Last query:
Last reply:
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

David Gómez (dabisu) said : #2

Hi, if you mean -x/-e options, i just tested and alsamixer is launched as expected. But if you mean the -h option, yes, is not working at all. It should be fixed so please open a bug in launchpad.

Mike Harvey (maharvey67) said : #3

This does not work for me either.

If I invoke sakura from a command line, it launches successfully (other than displaying garbage before the prompt: "notify; command completed")

If I invoke sakura with either -e or -x (example: "sakura -e ls") it fails to start at all, and this error is printed to the terminal:

** (sakura:2703): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

I can make this messages not appear with "export NO_AT_BRIDGE=1" but that still doesn't cause sakura to start. If I give a -e or -x option on the command line it silently does nothing at all, does not start, and does not print an error either.

Mike Harvey (maharvey67) said : #4

I happened upon the solution:

Programs like 'ls' were completing and exiting so fast that the terminal never even displayed on the screen. Testing with xlogo showed that the terminal is launching and is executing the child process. Also running "sakura -h -e ls" works correctly.

Can you help with this problem?

Provide an answer of your own, or ask Ol for more information if necessary.

To post a message you must log in.