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

[BUG] Wrong link to qmlscene using "axolotl -e me" #291

Closed
nuehm-arno opened this issue Dec 16, 2020 · 10 comments
Closed

[BUG] Wrong link to qmlscene using "axolotl -e me" #291

nuehm-arno opened this issue Dec 16, 2020 · 10 comments

Comments

@nuehm-arno
Copy link
Collaborator

nuehm-arno commented Dec 16, 2020

Description

Hello there,
following the descriptions from the Mobian Wiki to build Axolotl and starting the desktop file (axolotl -e me) with gtk-launch in a terminal, I stumbled over the following error message:

"FATA[0000] cmd.Start() failed with 'fork/exec /home/nanu/Qt/5.13.0/gcc_64/bin/qmlscene: no such file or directory''"

Code

I found one code reference in the file app/ui/gui.go in line 111. But there may be more.

Expected behavior: link to "qmlscene"

Versions

0.9.0.1

Device

Mobian on PinePhone CE 3gb

@olof-nord
Copy link
Collaborator

olof-nord commented Dec 18, 2020

I suspect you mean the page here? https://wiki.mobian-project.org/doku.php?id=axolotl

Giving it a quick look, some steps seems to be a bit outdated.

Have you had a look at the documentation in this repository instead?
https://github.com/nanu-c/axolotl/blob/main/docs/INSTALL.md

We have clickable, snap, flatpak and appimage installs documented with a step-by-step guide for each install method.

@joshbowyer
Copy link
Contributor

Hey, author of that wiki page here. That page has seen a lot of activity over the past few days; I made an edit yesterday, but so far it should be correct, and you should not be using the me flag. Launch it with qt for standalone, or see the "daemonized server" method for the two-part method.

@nanu-c
Copy link
Owner

nanu-c commented Dec 18, 2020

Indeed this is wrong. We should either drop it or make it work
https://github.com/nanu-c/axolotl/blob/main/app/ui/gui.go#L111

} else if config.Gui == "me" {
		cmd = exec.Command("/home/nanu/Qt/5.13.0/gcc_64/bin/qmlscene", "--scaling", "guis/qml/Main.qml")

@joshbowyer
Copy link
Contributor

Is there any real difference between me and qt ? Or is it redundant now?

@nanu-c
Copy link
Owner

nanu-c commented Dec 18, 2020

I think it's redundant now, because this switch was only working on my Computer

@nuehm-arno
Copy link
Collaborator Author

Thank you all for the answers. Maybe the redundancy should be mentioned somewhere.

And since we are in this topic: Which .qml file should be used by qmlscene / -e qt? Is it

[...]/guis/qml/qml/MainQML.qml
or
[...]/guis/qml/Main.qml

Having Axolotl as deamon (-e server) and starting qmlscene via terminal with one of the .qml files should start the UI, right?

MainQML.qml (which I think is used with "-e qt") is resulting in a white screen and some error messages:

file://[...]/MainQML.qml:20: TypeError: Cannot read property 'left' of null
Continuing with line 21 to 23 (top, right, bottom)
In addition, Axolotl is not starting the UI with "axolotl -e qt". There is only the white screen, too.

Main.qml is starting the UI correctly, only showing some errors like

[[...]ERROR:gles2_cmd_decoder.cc(2843)] [GroupMarkerNotSet(crbug.com/242999)! [...]]

Or am I just fiddling around to much?

I'd like to get Axolotl running smoothly without the need of a flatpak build.

@Flaburgan
Copy link
Collaborator

@olof-nord maybe you could have a look at this?

@olof-nord
Copy link
Collaborator

I have read along, but I must say that I am also a bit confused what the purpose, and difference, is between the three different QML files.

  • guis/qml/qml/MainQML.qml
  • guis/qml/ut/MainUt.qml
  • guis/qml/Main.qml

I understand that the thee possible options to not use Axolotl with Electron are ut, lorca and qt.
All other -e values starts with electron.

@nuehm-arno, I am not sure I understand what you want to achieve, or what the problem is.
Could you describe it with other words?

@nuehm-arno
Copy link
Collaborator Author

I'm opening a new issue for the qml errors with -e qt for better understanding.

@nanu-c
Copy link
Owner

nanu-c commented Feb 11, 2021

axolotl -e me was removed, so i close this

@nanu-c nanu-c closed this as completed Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants