-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
Linux AppImage not starting on Manjaro #919
Comments
If it works in briefcase dev, but not in briefcase run, it's almost certainly a briefcase related issue rather than a Toga issue. In this case, the error is one I've seen before. Two things to check:
If those two things are both covered, could I get you to delete the "linux" folder that was generated by Briefcase, and then run |
This
I added those 3 lines, ran briefcase creat, briefcase build, and briefcase run, and the app ran successfully, but with the following errors. `video$ briefcase run [rotate_video] Starting app... ` As a consequence the system Appearance Settings were ignored. |
That's troubling... are you able to provide the full log as I described in my previous post? |
I'll get onto that as soon as I recover from building our raised Gardens. |
Warning: This message has had one or more attachments removed
Warning: (briefcase.2022_10_13-15_17_39.run.log).
Warning: Please read the "INFOTECHWEB-Attachment-Warning.txt" attachment(s) for more information.
Here's the Log
Sent from Claws Mail on my Manjaro Linux Computer, where Free means Freedom,
and Privacy is.
On Wed, 12 Oct 2022 03:14:31 -0700 Russell Keith-Magee ***@***.***> wrote:
briefcase run --log
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "briefcase.2022_10_13-15_17_39.run.log"
is on the list of unacceptable attachments for this site and has been
replaced by this warning message.
If you wish to receive a copy of the original attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.
At Thu Oct 13 15:21:39 2022 the virus scanner said:
MailScanner: Attempt to hide real filename extension (briefcase.2022_10_13-15_17_39.run.log)
Note to Help Desk: Look on The INFOTECHWEB () MailScanner in /var/spool/MailScanner/quarantine/20221013 (message 1oiqeU-00009W-J1).
--
Postmaster
INFO TECH WEB
https://hostingoz.net/manage/terms-of-service.php
|
Log emailed to return address. |
The log has been stripped by a virus checker,. You can upload it directly by dragging it into a comment window on Github. |
How do I get the file to you? When I copy paste it's content it's too long. When I attempt to upload it, I get 'Something went really wrong, and we can't process that file. Try again' When I email it to you, I I get the above 'Warning: This message has had one or more attachments removed' |
Like I said in my last comment - drag it into the comment box in Github. It will be uploaded as an attachment to your comment. |
The file name ends with .run.log, the virus checker appears to believe this is an attempt to hide the real file extension. I've changed the name to end in _run.log, and will retry emailing it. |
Tray again.
Sent from Claws Mail on my Manjaro Linux Computer, where Free means Freedom,
and Privacy is.
…On Wed, 12 Oct 2022 22:23:35 -0700 Russell Keith-Magee ***@***.***> wrote:
The log has been stripped by a virus checker,. You can upload it directly by
dragging it into a comment window on Github.
|
Your email client is thing being "smart" here. Don't use it. Drag and drop the file from your file manager into the text box that you use to add a comment to this thread, and you'll get something that looks like this: |
Unless you received the file as an attachment in an email, I'm still getting the message.. 'Something went really wrong, and we can't process that file. Try again' When I attenpt to upload it via this comment system. |
Dragging and dropping the file, clicking on the bottom section of the editor and navigating to the file, makes no difference, I get the message.. 'Something went really wrong, and we can't process that file. Try again' |
Sounds like your browser might be "helping" with some virus checking of its own. My next suggestion would be to zip the log file, and upload the zipped version. That's sometimes enough to convince virus checkers they don't need to panic. |
Same error message, with Zipped File... and with pdf. The file is quite large, would that be a problem? |
Depends on what you mean by "Quite large". PDF won't make the document much smaller, but zipping it should - it's text content. How big is the raw and zip versions? |
the zip is only 20K, (the raw 383K), so I think size isn't the problem. Try this https://www.mediafire.com/file/he5o4xvhdjij2f0/briefcase.2022_10_13-15_17_39_run.zip/file |
Based on that log, I can confirm it's a Briefcase issue, not a Toga issue; I'll transfer the issue on that basis. The underlying problem is that Linux AppImages can be... a bit flaky. They're trying to do something that is very difficult - automatically identify all the binaries that an application uses, and relocate them so that the binary is redistributable. However,
I can't spot anything obviously wrong with the log - other than the fact that it's clearly not working. If you hunt around for the key phrases in the errors you're seeing ("libpango-1.0.so.0", "g_memdup2", "g_task_set_name"), you'll find a common them with Manjaro AppImage having the same problem. This suggests there's a problem with either linuxdeploy or the GTK plugin. |
Yes I noticed those. There may be a possibility that as GTK is installed to support GNOME apps on my KDE DE, my be causing a problem. The GNOME apps are not native to a KDE DE. What about debs and flatpak, I noticed they were either under development of projected? |
Flatpak has been implemented; We haven't got support for debs at this time. |
Is there any reason you chose to ignore KDE, or rather the Qt toolkit. Personally I think QT is much easier to work with. I've certainly found building QtPython apps much easier to write than GTK Python apps, and what the KDE devs have achieved leaves GNOME in the dust IMO. Although Toga does make wotking with GTK a doddle. I've installed a GNOME desktop (Ubuntu) on a VM, so GTK native, and am building the app on that, to see if there is any difference. |
We haven't "ignored" Qt and KDE. We've made a choice to focus our limited resources. Briefcase does provide support for Qt - it provides both PySide2 and Pyside6 templates for apps. When it comes to Toga, we've focused our development effort on the GUI framework on GTK, as it is the GUI toolkit that drives the default desktop option on most of the popular Linux distributions (Ubuntu, Debian, Fedora, CentOS, and Raspbian, amongst others). However, if you poke around the Toga repository, you'll find beeware/toga#1142, where we've confirmed that we'd be happy to provide native Qt support - we just need someone to contribute it. There is already a stub project in the Toga nursery. All that is missing is an implementation. If this is an area where you're interested in contributing, then I'd encourage you to start there. |
I was just wondering, thanks. OK here's the thing. I've been able to get libcanberra to install, and it loads, by adding a reference to it in the pyproject.toml file
I added the following lines...
However, while it appears that all three libraries are installed, I still get the error.
As far as i can tell the issue revolves around libxapp. I will hopefully narrow this down. I will also try to upload the log file. |
Sorry I haven't been in for a while. I've been trying to locate a second hand laptop that I could afford... I'm a pensioner and all that. So I installed Ubuntu 20.04 on the second Laptop, the app builds, and runs correctly on the GNOME desktop. But if the theme is changed, the app has to be restarted to reflect the changed desktop theme. The app also runs correctly on Manjaro KDE, but fails to follow the desktop theme. |
Ok. I've built the app on my Manjaro KDE system, transfered the resulting appimage to the Ubuntu system, the app runs correctly, and follows the desktop theme. If I run the app from a terminal on my Manjaro KDE system, it ignores the desktop Theme, and I get the errors, I had assumed were related to the build
This I now believe is related to running a GTK app on KDE, or possibly, specifically to Manjaro KDE. Recently a poster on the Manjaro Forum posted a similar set of errors, related to running a Flatpak on a Manjaro KDE system I will install KUbuntu on the spare laptop, to confirm if this is GTK/KDE related or specificaly Manjaro KDE |
It would also be helpful to confirm if the "ignoring desktop theme" problem is a bug or a "feature". I completely agree that it isn't what most users would expect - but based on what I know of how AppImage works, I can't see how it would be possible for an AppImage to reliably adopt the end-user's theme. AppImage works by bundling every binary needed to run an app, outside of a very small core set of libraries (essentially libc and not much else). The distributed app is very using a copy of any GUI libraries, on the basis that there's no way to guarantee that the end-user's computer will have the GUI framework that you require. If my understanding is correct, I don't see how it would be possible for an app to use a bundled version of GTK, but not use a bundled version of the GTK theme - if only because there's no way to guarantee the end-user's theme (assuming they have one) will be compatible with the bundled version of GTK. So - it would be helpful for you to confirm if this "theme ignoring" behavior is common to all AppImage apps. There's a collection of AppImage apps on this website - do those apps follow the system theme, or do you see the same problem? |
I'll check that out. |
Interesting... I just changed the GTK3 theme setting from Breeze to Adwaita-Dark... the KDE theme is Breath-Dark. The default Theme for Manjaro KDE is Breath, while the default Theme for GTK3 is Breeze. Now, on the Kubuntu system the default setting for KDE is Breeze, as is the default setting for GTK3 this means the GTK3 appimage is theming correctly, in spite of those errors. changing Kubuntu Theme to Breeze Dark for both KDE and GTK3 results in a correctly themed appimage. So, now I can theme both KDE and GTK3 apps to more or less the same theme on Manjaro KDE... KDE theme Breath-Dark, and GTK3 Adwaita-Dark, and the appimage picks up the GTK3 theme. and on the Kubuntu system I can set KDE to Breeze-Dark and GTK3 to Breeze-Dark, and the appimage correctly picks up the GTK3 theme. Sorry this appears to have been a bit of a wild Goose chase. The biggest problem seems to be there is no comparable Breath Theme for GTK apps on Manjaro KDE, whereas the older Breeze Theme is available on Kubuntu. |
No worries about the goose chase - app packaging issues are 99% goose by volume :-) To clarify where we are at, if I'm following correctly:
If that's the case, it sounds like there's not much we can do with 92); but for (1) we can add the extra required system libraries to the base briefcase-template so that every new project gets those installed by default. It would be preferable if we can narrow those packages down to specific versions, rather than wildcards; from a quick inspection of the packages installed by the wildcards, there's a lot of extra stuff being installed, not just 3 extra packages, and it's not immediately obvious to me why some of them are needed. If they are, that's fine - but I'd rather be explicit about those requirements. |
No I think one was solved by adding
Which was missing. Ensuring that that is indeed in the .toml means the app will build and run. The errors related to I've just installed snap that is built on GTK3, and it exhibits the same 'issues', and runs correctly, and with my GTK3 Theme choice fits my KDE theme. But yes (2) is basically DE and Theme dependant A lot of my running around in circles was related to my lack of understanding of how Appimage/Flatpak/Snaps work. |
Ok - in which case, can we close this issue as resolved? AFAICT, |
yes please close. I'll do some research, and probably look at the QT stub. |
My rotate_video app runs successfully in dev mode (briefcase dev),
it builds successfully (briefcase build), but fails to run (briefcase run)
I get the following message(s) I'm not even sure this is a Toga issue.
Operating System: Manjaro Linux
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.15.72-1-MANJARO (64-bit)
Graphics Platform: X11
GTK2 V2.24.33
GTK3 V3.24.34
The text was updated successfully, but these errors were encountered: