-
Notifications
You must be signed in to change notification settings - Fork 104
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(startup): 1.0.3 core dump in Xorg session #383
Comments
This comment was marked as outdated.
This comment was marked as outdated.
@edgy-b I honestly have no idea how a two year old issue is related. In this case, the GUI never opens. Also, please don't quote the issue in your reply. |
Seesh didnt noticed that its so old. |
Also using the AUR package, won't launch on Plasma 6 wayland with amd gpu. Errors on launching from CLI:
|
@phoropter Please open a separate issue @yochananmarqos could you try updating the lockfile to latest and build to see if it got fixed in the meantime? I opened an issue at winit because they were modifying a lot, but iced could also be at fault. |
@Frigyes06 The |
@yochananmarqos Can you run uad with xtrace and upload the logs? |
I'm guessing you mean xtrace as in the Debian package? All I have is |
I love it when people name things the exact same. I think it'd be best if you talked directly to the winit guys over at rust-windowing/winit#3616 |
Closing this as it's stale. Try v1.1.0. |
With 1.1.0:
|
@yochananmarqos |
@edgy-b No difference. |
@yochananmarqos |
|
@yochananmarqos what if you try running on wayland |
|
This comment has been minimized.
This comment has been minimized.
@yochananmarqos @phoropter Sorry that it took this long. Could you try with one of these artifacts? https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/actions/runs/12749084042 |
@AnonymousWP No worries. Thing is, I'm now using Wayland. I've lost interest in pursuing this issue. Feel free to close it if you feel the same. |
Describe the bug
AUR package maintainer here. 1.0.3 fails to start while 1.0.2 launches fine. Log is attached.
EDIT: This only happens on my NVIDIA machine running a GNOME Xorg session . I cannot reproduce on my AMD machine running a GNOME Wayland session.
Expected behavior
N/A
You have a solution?
No response
Provide logs
UAD_20240326.log
Acknowledgements
The text was updated successfully, but these errors were encountered: