Using Fedora 36, when selecting a business or creating a new one, the app immediately crashes. No error message appears; the app just closes.
I gather you did not get a response to this - I found earlier Fedora35 solutions by deprecating some software - it kind of worked for a while - I am now looking to go through the process again on a new Fedora spin (Aquamarine) in case that works better.
Haven’t heard anything yet, no. A bit discouraging because Fedora is one of the supported distros according to the download page
1 Like
You do not provide enough information supported by screenshots . Frankly we do not know where things are not working. Even log-files may be helpful. In the absence of the required information, your hardware (system), the Manager version you downloaded and tried to install, Any GDK you may have added to Fedora or firewall systems, it will be impossible to help you, except if you do a clean/fresh install on a fedora 33 and above system and then report back.
We can help you if you provide much more details but just saying it does not work does not encourage anyone to help you.
1 Like
I agree log files would be helpful, but did not know where they are stored. Do you know where those are located?
As far as screenshots… it’s there until you click on a Business. It just quits without error. Nothing to see or screenshot.
Running a fairly standard install of Fedora, not a highly customized system here. I am using KDE. So you are aware, the current version of Fedora is 36. Version 33 went end of life 9 months ago.
If the only method of troubleshooting available is to completely reformat my system with an EOL operating system… then I don’t think this is going to work out for me.
1 Like
These would be log files created by your operating system, i.e. Fedora. Searching for fedora log files in your web browser will tell you how and where.
That would be your choice.
Found the below entry in /var/log/messages - does this imply plasma crashed, or that it detected something in the AppImage?
Aug 22 09:42:47 thinkpad systemd[3995]: Started app-appimagekit_d0b0f828c6cd555b9df4feb01951ecf9\x2dManager-ccc054344d95486e9694155603e7b33d.scope - Manager.
Aug 22 09:42:47 thinkpad kwin_x11[4299]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41741, resource id: 29364030, major code: 18 (ChangeProperty), minor code: 0
Aug 22 09:42:47 thinkpad systemd[3995]: Reloading.
Aug 22 09:42:49 thinkpad kwin_x11[4299]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 43238, resource id: 18282117, major code: 3 (GetWindowAttributes), minor code: 0
Aug 22 09:42:49 thinkpad kwin_x11[4299]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 43239, resource id: 18282117, major code: 14 (GetGeometry), minor code: 0
Aug 22 09:42:49 thinkpad rtkit-daemon[1473]: Successfully made thread 488487 of process 488467 (/usr/libexec/webkit2gtk-4.0/WebKitWebProcess) owned by ‘1000’ RT at priority 5.
Aug 22 09:42:49 thinkpad rtkit-daemon[1473]: Successfully made thread 488514 of process 488467 (/usr/libexec/webkit2gtk-4.0/WebKitWebProcess) owned by ‘1000’ RT at priority 5.
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 1 0x7f5a70281129
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 2 0x7f5a6ee4bfdf
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 3 0x7f5a7089860d
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 4 0x7f5a6ee2fec1
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 5 0x7f5a6ef81177
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 6 0x7f5a6ef81bf5
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 7 0x7f5a6db65795
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 8 0x7f5a6db7c0e3
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 9 0x7f5a6e14bfaf g_main_context_dispatch
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 10 0x7f5a6e1a12c8
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 11 0x7f5a6e14b6cf g_main_loop_run
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 12 0x7f5a6db6db60 WTF::RunLoop::run()
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 13 0x7f5a6ef4bb55 WebKit::NetworkProcessMain(int, char**)
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 14 0x7f5a6e508550
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 15 0x7f5a6e508609 __libc_start_main
Aug 22 09:43:02 thinkpad WebKitNetworkProcess[488466]: 16 0x5602926860a5
Aug 22 09:43:02 thinkpad plasmashell[488447]: *** stack smashing detected ***: terminated
Look at Appimage does not work, crashes Even though it is not Fedora it is a similar problem and the same solution may apply.
The problem is with
I guess you’d better ask in the Fedora user forum?
I haven’t asked in the Fedora forum because we haven’t yet confirmed this is an OS issue. eko identified in the log that webkit2gtk is being called here, can I provide more logs or information that would help determine the fault is truly because of gtk?
The post with the other user offered a ‘fix’ to downgrade the installed gtk version, but I don’t really accept that as permanent solution, to remain stuck at that same version for eternity. If there’s a code issue, whether it be with the gtk or manager.io devs, it would be nice to see it get resolved rather than band-aided.
1 Like
James did you try the solution provided, i.e. deal with the Webkit2gtk version, install what they recommended on the link I gave you. You may post even in the topic I gave you so the people that helped resolve it there could help you.
I haven’t tried the fix on my main device, but was able to successfully run Manager on another test device with webkit2gtk 2.36.6-1 and unknown version of gtk.
1 Like
I also just created a new Fedora 36 VM, and had the same result (app crashes when attempting to open a Business). Manager.io may want to address this on the downloads page where it states the app is compatible with Fedora 33 and newer - I haven’t tried 34 or 35 so unsure when the breaking change was made, but it appears this does not work with an out-of-the-box Fedora install.
1 Like
I was able to open Manager by downgrading gtk3 using sudo dnf downgrade --releasever=34 gtk3 - but as mentioned here and in other threads, it is not recommended to freeze packages at any specific version. Any thoughts on identifying and implementing a proper fix?
You applied the proper fix yourself by