Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exit the program when using menus under raspbian #158

Closed
nlebellier opened this issue Jul 10, 2019 · 15 comments
Closed

Exit the program when using menus under raspbian #158

nlebellier opened this issue Jul 10, 2019 · 15 comments
Labels

Comments

@nlebellier
Copy link
Contributor

@nlebellier nlebellier commented Jul 10, 2019

hi,

When i use the menus under raspbian, Orca closes suddenly. Same issue with Pilot.

maybe this message could be the reason why.

Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
ATTENTION: default value of option force_s3tc_enable overridden by environment.
pi@pi02:~/audio/Orca/desktop $ node --version
v12.6.0
pi@pi02:~/audio/Orca/desktop $ npm --version
6.9.0
pi@pi02:~/audio/Orca/desktop $ 

@nlebellier nlebellier changed the title violent quit when using menus under raspbian Exit the program when using menus under raspbian Jul 10, 2019
@neauoire
Copy link
Member

@neauoire neauoire commented Jul 12, 2019

Not sure : /

@martinberlin
Copy link
Contributor

@martinberlin martinberlin commented Jul 12, 2019

I must say I'm not an experienced Raspian user to start with. But I also had problems to do an npm install in the small PC:
Error: Cannot find module 'mkdirp'
at Function.Module._resolveFilename (module.js:536:15)

pi@raspberrypi:~/Orca/desktop $ nodejs -v
v12.6.0
pi@raspberrypi:~/Orca/desktop $ npm -v
5.5.1

So I decided to use the Orca-C instead of this version. But I guess there is an easy way to fix it as in my laptop works perfectly with an older version of nodejs (8.10)
If I can help in any way testing this just tell me and I will follow @neauoire

@kroppian
Copy link

@kroppian kroppian commented Jul 26, 2019

I'm able to reproduce the bug on 32 bit Debian 9. Getting the exact same warnings as you do as well.

@neauoire
Copy link
Member

@neauoire neauoire commented Jul 26, 2019

I think it has to do with the icon that displays on quit, does the error also happens on save?

@nlebellier
Copy link
Contributor Author

@nlebellier nlebellier commented Jul 26, 2019

For me it was for all menus not a specific one. may it helps.

@ChrisPhillips222
Copy link

@ChrisPhillips222 ChrisPhillips222 commented Aug 2, 2019

Hi, I’ve installed Orca on an old netbook running lubuntu 18.10 and I’m getting the following error whenever I try to select anything in the menu:

Glib-GIO-CRITICAL **: (timestamp): g_dbus_proxy_new: assertion ‘G_IS_DBUS_CONNECTION (connection)’ failed

based on some things I've read after furious googling I purged fcitx-module-dbus. Now it doesn't give the error but will still exit the program if I try to use the menu.

@ryanramage
Copy link
Contributor

@ryanramage ryanramage commented Sep 12, 2019

I was having this problem, but today I updated from git, did an npm install, and now orca runs fine on the pi! No more menu crashing!

@ChrisPhillips222
Copy link

@ChrisPhillips222 ChrisPhillips222 commented Sep 12, 2019

I was having this problem, but today I updated from git, did an npm install, and now orca runs fine on the pi! No more menu crashing!

Same on Lubuntu. Still gives the error at the console but doesn't halt the program. Everything seems to work now.

@neauoire
Copy link
Member

@neauoire neauoire commented Sep 12, 2019

very happy about this :)

@martinberlin
Copy link
Contributor

@martinberlin martinberlin commented Sep 13, 2019

The only problem I have with the menu's and it's very frustrating is like this: (Ubuntu 18 desktop Gnome)
File -> Open
It opens normally the File Manager. Most of the times it's hang in a way I cannot select an Orca file to open but I cannot also "Save as..."
Basically up to this point Orca keeps working but File opening or saved is disrupted. I can only save to the same file I've already open. Is there any way I can help solving this issue?

@koshimazaki
Copy link

@koshimazaki koshimazaki commented Sep 21, 2019

I was having this problem, but today I updated from git, did an npm install, and now orca runs fine on the pi! No more menu crashing!

@ryanramage are you using ORCA or orca-c ?

@koshimazaki
Copy link

@koshimazaki koshimazaki commented Sep 21, 2019

I managed to get to work both ORCA and orca-c on PI4.
ORCA needs node.js and electron installing. It needs newer one to run npm. Might be worth adding that in the installation guide.

I also experience crashes with menus but while using key combinations to get to menu it seem to work fine. ORCA is lagging a bit once injecting files or while more operators are present on screen. No problem with saving and loading the files tho.

@neauoire
Copy link
Member

@neauoire neauoire commented Nov 7, 2019

Could someone pull the latest changes and test orca on RPi, and tell me if that works for you?

@martinberlin
Copy link
Contributor

@martinberlin martinberlin commented Nov 7, 2019

On my Raspberry 4 the electron post install hook is failing.

$ npm install

> electron@7.1.0 postinstall /home/pi/Programs/Orca/desktop/node_modules/electron
> node install.js

(node:1750) UnhandledPromiseRejectionWarning: HTTPError: Response code 404 (Not Found)
    at EventEmitter.<anonymous> (/home/pi/Programs/Orca/desktop/node_modules/got/source/as-stream.js:35:24)
    at EventEmitter.emit (events.js:210:5)
    at module.exports (/home/pi/Programs/Orca/desktop/node_modules/got/source/get-response.js:22:10)
    at ClientRequest.handleResponse (/home/pi/Programs/Orca/desktop/node_modules/got/source/request-as-event-emitter.js:155:5)
    at Object.onceWrapper (events.js:300:26)
    at ClientRequest.emit (events.js:215:7)
    at ClientRequest.origin.emit (/home/pi/Programs/Orca/desktop/node_modules/@szmarczak/http-timer/source/index.js:37:11)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:583:27)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:115:17)
    at TLSSocket.socketOnData (_http_client.js:456:22)
(node:1750) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1750) 
[DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Maybe because I'm connected with my phone to the internet? Strange, don't undestand why a 404 error.

@neauoire
Copy link
Member

@neauoire neauoire commented Nov 17, 2019

I've added a little --gpu_disabled command to the start command, maybe that will fix the menu issues?

@neauoire neauoire closed this Sep 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants