blurt icon indicating copy to clipboard operation
blurt copied to clipboard

Unknown error!

Open accforgithubtest opened this issue 2 months ago • 2 comments

I installed blurt from gnome extensions website, on Ubuntu 22.04.5 LTS, on a micro (SFF) desktop, no gpu, only an intel 8500T cpu, with 32G ram.

When I press ctrl+alt+a, the icon color changes to yellow. When I press ctrl+alt+z, the icon color changes to red. If I press ctrl+alt+a and leave it for about 10 seconds, the icon color changes to red automatically.

I see this error in notification area. Image

Please let me know if I have missed anything, or suggestions to debug this further please.

In blurt settings, Location of wsi is set to .local/bin/ Use Server API is turned off.

the .local/bin/ file tree is

.local/bin/
  |_ wsi
  |_ whisper-tiny.en.llamafile
  |_ whisper-small.en.llamafile

I ran

chmod +x ~/.local/bin/wsi
chmod +x ~/.local/bin/whisper-tiny.en.llamafile
chmod +x ~/.local/bin/whisper-small.en.llamafile

I downloaded the wsi file, and changed below lines -

# Commented these 3 lines as I want to use llamafile. Uncommenting them also did not make any difference.

#model="$HOME/CHANGE_PATH_TO/WHISPER_CPP/MODELS/HERE/ggml-base.en.bin"
#WHOST="127.0.0.1"
#WPORT="58080"  


# None of the below worked either -

WHISPERFILE="$HOME/.local/bin/whisper-tiny.en.llamafile"
# WHISPERFILE=".local/bin/whisper-tiny.en.llamafile"
# WHISPERFILE="whisper-tiny.en.llamafile"
# WHISPERFILE="$HOME/.local/bin/whisper-small.en.llamafile"
# WHISPERFILE=".local/bin/whisper-small.en.llamafile"
# WHISPERFILE="whisper-small.en.llamafile"

accforgithubtest avatar Oct 21 '25 08:10 accforgithubtest

Hi @accforgithubtest. Sorry for late reply.

First, it would really help if you tried to run wsi or wsi -c directly from the terminal. That will help identify the source of the problem. When you run it from the terminal, CTRL+C can be used to stop recording and send the audio to your executable whisperfile, which should output the transcribed text to the standard output. BTW, are you sure the notification originated from blurt? I do not remember, but the blurt notifications should all be displaying the source (blurt). In any case, let us start with the output of wsi.

QuantiusBenignus avatar Nov 05 '25 15:11 QuantiusBenignus

Thank for your reply @QuantiusBenignus .

When trying to run wsi directly from terminal, nothing happens.

Once I run wsi, I see the microphone icon show up next to the clock. I speak a few words and use ctrl+c, the program basically just cuts out. nothing else happens.

$ wsi
^C
$

I also noticed that if I run wsi and leave it for about 10 seconds, the program cuts out automatically. Whether I speak or not, it cuts out after approx 10 seconds.

exact same behaviour with wsi -c` as well.

Is there any way for me to get the wsi to print more logs of what exactly happened ?

accforgithubtest avatar Nov 14 '25 00:11 accforgithubtest

Hi @accforgithubtest,

It sounds like you are recording audio but your microphone signal is too low so wsi takes it for silence. Check the audio file in /dev/shm (wfile) and try to play it play wfile. See what it sounds like. Increase the microphone signal level from the system audio settings. If I am right, this will make the extension work OK because it will be receiving valid signal.

If you want to see the error output from the extension, check the GNOME logs (press the Command/Windows key and start typing log.., the Logs Gnome app icon will pop up as a valid search result, click on it and inspect the logs for wsi/blurt related errors).

To get to see the errors of wsi executed from the cli, you must remove the error redirection in the script temporarily (the 2>/dev/null segment in the whisper inference command for example).

QuantiusBenignus avatar Dec 06 '25 15:12 QuantiusBenignus