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

Immediate crash on opening #78

Open
MicahN44 opened this issue Dec 25, 2024 · 28 comments
Open

Immediate crash on opening #78

MicahN44 opened this issue Dec 25, 2024 · 28 comments

Comments

@MicahN44
Copy link

The title kind of sums it up, but with the flatpak version it crashes immediately no matter how I launch it. The window flashes up, and the icon appears on the dock, and then they both disappear. Does the same no matter how I launch it.

This could totally be something I have broken to be clear, I am new to this space, but if it is something I have done I am not sure what it is lol

I am using Pop 22.04 with the normal Gnome DE. I may try building it later when I have more time (especially because I should probably know how to do that anyways). thanks

Screencast.from.12-24-2024.07.59.29.PM.webm
@hepp3n
Copy link
Collaborator

hepp3n commented Dec 25, 2024

Hello,

It comes from winit directly. There must be something which causes this issue. You are using X11 on this version of PopOS. I had previously some problems with Xorg and libcosmic apps. Mostly because of winit but it does not mean it's not fixable. Could you please copy-pase this error message here? I can't see this very well. Also you don't need to build it yourself because the result should be the same.

Please paste full log here. So I will dig it.

@MicahN44
Copy link
Author

2024-12-25T14:19:33.239943Z INFO winit::platform_impl::linux::x11::window: Guessed window scale factor: 1
2024-12-25T14:19:34.293141Z INFO winit::platform_impl::linux::x11::window: Guessed window scale factor: 1
2024-12-25T14:19:34.305074Z ERROR winit::platform_impl::linux: X11 error: XError {
description: "BadMatch (invalid parameter attributes)",
error_code: 8,
request_code: 149,
minor_code: 4,
}
2024-12-25T14:19:34.305097Z ERROR winit::platform_impl::linux: X11 error: XError {
description: "BadMatch (invalid parameter attributes)",
error_code: 8,
request_code: 149,
minor_code: 4,
}
2024-12-25T14:19:34.305107Z ERROR winit::platform_impl::linux: X11 error: XError {
description: "BadMatch (invalid parameter attributes)",
error_code: 8,
request_code: 149,
minor_code: 4,
}
2024-12-25T14:19:34.363050Z ERROR winit::platform_impl::linux: X11 error: XError {
description: "BadMatch (invalid parameter attributes)",
error_code: 8,
request_code: 149,
minor_code: 4,
}
2024-12-25T14:19:34.363074Z ERROR winit::platform_impl::linux: X11 error: XError {
description: "BadMatch (invalid parameter attributes)",
error_code: 8,
request_code: 149,
minor_code: 4,
}
2024-12-25T14:19:34.363082Z ERROR winit::platform_impl::linux: X11 error: XError {
description: "BadMatch (invalid parameter attributes)",
error_code: 8,
request_code: 149,
minor_code: 4,
}
thread 'main' panicked at /run/build/quick-webapps/cargo/vendor/winit/src/platform_impl/linux/x11/event_processor.rs:1210:47:
Failed to focus input context: XError { description: "BadMatch (invalid parameter attributes)", error_code: 8, request_code: 149, minor_code: 4 }
stack backtrace:
0: 0x623ae34ef11a -
1: 0x623ae351cdf3 -
2: 0x623ae34ea5c3 -
3: 0x623ae34eef62 -
4: 0x623ae34f004c -
5: 0x623ae34efe92 -
6: 0x623ae34f0627 -
7: 0x623ae34f04ba -
8: 0x623ae34ef5f9 -
9: 0x623ae34f014c -
10: 0x623ae2131200 -
11: 0x623ae2131646 -
12: 0x623ae2316bf0 -
13: 0x623ae23159b6 -
14: 0x623ae2311283 -
15: 0x623ae225944c -
16: 0x623ae225dc1f -
17: 0x623ae2230dd1 -
18: 0x623ae247fd83 -
19: 0x623ae241f9fa -
20: 0x623ae23c89c6 -
21: 0x623ae226f055 -
22: 0x623ae34e255e -
23: 0x623ae241ff25 -
24: 0x77a3d7a2b188 -
25: 0x77a3d7a2b24b - __libc_start_main
26: 0x623ae2131c15 -
27: 0x0 -

Here is everything that was in that terminal, lmk if there is something else I should grab you. And good to know on building it

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 25, 2024

Thanks!

Are you using fcitx maybe?

@MicahN44
Copy link
Author

MicahN44 commented Dec 25, 2024

That is a good question! I don't know what that is. I don't think so. Checking online it doesn't seem to be built in to Pop

Edit: tried to run a fcitx command in my terminal, says I need to install it first. So no

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 25, 2024

I'm asking cuz found this: rust-windowing/winit#3761

@MicahN44
Copy link
Author

That certainly looks similar. though AFAIK I don't have fcitx. I will try to verify that

In case it may be helpful here is system info
Screenshot from 2024-12-25 15-16-14
Didn't think to include this before.

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 25, 2024

Thank you!

I will make a VM with this version of PopOS and try to reproduce it on my own.

Also, if it's possible, please try on Wayland. It's simple to enable on PopOS.

@MicahN44
Copy link
Author

Will give that a Google and try that. I was just looking into it, I had heard that Wayland wasn't friendly with Nvidia but that seems to not be so true anymore? Shows what I know. I will see about doing that real quick :) Thanks for your help btw!

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 25, 2024

It was not that good before. Now it kind of better. It's basically for test to make sure this issue happens only on X11. Later you can disable it again :)

Thank you again for your testing. Tomorrow I will fire up a VM and do something else :)

@MicahN44
Copy link
Author

Working on Wayland. I'll try some other stuff and see what happens lol. If worst comes to worst, could I potentially make PWAs in Wayland and then hop back over to X11?

And no rush for my sake :) and no problem. If there is anything I can help with I am more than happy to!

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 25, 2024

If worst comes to worst, could I potentially make PWAs in Wayland and then hop back over to X11?

Yes, it should works. But we will manage to make it working on X11 also :)
I noticed you are using cosmic-store which is also baked by libcosmic. So there is something related to Quick Web Apps, something on my end.

@MicahN44
Copy link
Author

I noticed you are using cosmic-store which is also baked by libcosmic. So there is something related to Quick Web Apps, something on my end.

Yeah I have been using that for a while because Pop Shop was giving me a ton of trouble. Good catch, I didn't even think about that. Not that that should be surprising to anyone ;)

@MicahN44
Copy link
Author

I played with Wayland for a while and didn't find any weirdness with other stuff yet, so I will probably stick with that for now, but let me know when you are working on this issue cause I'm happy to do some testing on X11

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 26, 2024

Hello again @MicahN44 ,

So I did some testing on virtual machine, Pop OS 22.04 and X11. Everything seems to works as expected. However, I did it on default settings.

After some digging, I found from where this error comes: https://github.com/pop-os/winit/blob/iced-0.13/src/platform_impl/linux/x11/event_processor.rs#L1210

It's basically something related to your input (?) settings? Could you please tell us your input settings? Also, do you using any of this: https://wiki.archlinux.org/title/Input_method#Input_method_framework
This is related to previous issue I mentioned, about fcitx.

@MicahN44
Copy link
Author

I don't use any of that, but I may have had KDE Plasma on this install at some point in the past (not sure if I've reinstalled since then). That thread says KDE uses fcitx5 so maybe that is still around somewhere and causing issues? I am at work rn so I can't try anything but I'll poke at it this evening and see what I find

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 26, 2024

That thread says KDE uses fcitx5 so maybe that is still around somewhere and causing issues?

I guess so :)

I am at work rn so I can't try anything but I'll poke at it this evening and see what I find

Sure, no rush! I appreciate your help :)

@MicahN44
Copy link
Author

OK so I am back on X11 this morning, I am still having issues. It looks like I have IBus from that Archwiki thread (Makes since because I use Gnome) But I think that would have been in your VM as well. I didn't find any commands or running processes for anything else there.

I apologize for my newbiness but what do you mean by my input settings?

I have a second drive with a Windows install I want to nuke anyways, I was gonna put 24.04 Cosmic on it but I may quickly do a fresh Pop 22.04 install on there and see if I still have issues. Will let you know what happens with that as well

@MicahN44
Copy link
Author

MicahN44 commented Dec 27, 2024

OK so I am on a fresh Pop install and I am still having this issue. Not sure what would be different between your VM and this. Both of my installs are encrypted but I don't think that should matter?

Edit: It appears to be the same problem (error code 8, request code 149, minor code 4)

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 27, 2024

Hello,

I apologize for my newbiness but what do you mean by my input settings?

Basically your language, keyboard settings etc. I'm using Polish, and pl keyboard layout.

OK so I am on a fresh Pop install and I am still having this issue. Not sure what would be different between your VM and this.

Ok, that one is weird. For me it worked. Also, many people using this app and nobody reported anything similar before. I'm not really sure what is going on, but will dig it.

@MicahN44
Copy link
Author

Keyboard is English US, Language is English US, at least on this second machine. I would assume that's what I did on my actual install as well lol.

LMK If you want me to try anything else :) idk where to go from here myself. I don't think it would be a hardware issue especially since it works on Wayland.

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 27, 2024

Keyboard is English US, Language is English US, at least on this second machine. I would assume that's what I did on my actual install as well lol.

nothing fancy then.

LMK If you want me to try anything else :) idk where to go from here myself. I don't think it would be a hardware issue especially since it works on Wayland.

Thanks. You did good. I will test it to reproduce and try to fix it. But not sure how if it's works ^^ Yeah, it's X11 issue for sure.

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 27, 2024

Well, if you are brave enough ^^

You can try to build it yourself. From source. Follow the readme instructions.

Then you can try with updated dependencies.

@MicahN44
Copy link
Author

I will give that a shot, that is something I would like to know how to do anyways. Thanks for your help!

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 27, 2024

Awesome. If you need assistance feel free to ask.

@MicahN44
Copy link
Author

Sorry to be a bother but I have messed up somewhere along the route lol. the just command didn't work properly I don't think (which probably means I did something wrong before that). Here is the error:
Screenshot from 2024-12-27 12-00-47
There was a lot more the first time I ran this, but I restarted my computer just in case that would have helped. this is all the stuff that went wrong the first time.

From what I can find online this has to do with refutable vs. irrefutable variables? Which is interesting but I wasn't sure where to go from there, or how to use "let else" as the error suggests.

In addition in the readme it says to build a binary file, I assumed I was doing that but maybe I wasn't? How do I do that and is that my problem?

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 27, 2024

Ah right. It might be old version of rustc I guess. I was suggesting in README to install rustc with cargo from PopOS repo. It can be problematic. It better for this purpose use rustup to install latest toolchain. Please remove first 2 dependencies as README suggest, so rustc and cargo and then follow this instruction:

https://rustup.rs/

Later, restart your shell and try to build again :)

Sorry, my bad. I will correct README :)

@MicahN44
Copy link
Author

MicahN44 commented Dec 27, 2024

That worked perfectly, thank you! And this is working on X11 as well now. If you want me to do more testing on the Flatpak let me know but I will stick with this for the moment :)

@hepp3n
Copy link
Collaborator

hepp3n commented Dec 27, 2024

Oh, well. That's interesting. So there is something on flatpak side. Thanks!

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

2 participants