mirror of
https://github.com/jpochyla/psst.git
synced 2026-04-27 07:25:52 +03:00
[GH-ISSUE #619] Cannot play any song #366
Labels
No labels
api
bug
build
documentation
duplicate
enhancement
good first issue
help wanted
idea
invalid
linux
lowprio
macos
pull-request
upstream
windows
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/psst#366
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yjavaherian on GitHub (May 24, 2025).
Original GitHub issue: https://github.com/jpochyla/psst/issues/619
Describe the bug
The app opens, i click on a song, the app crashes
To Reproduce
Steps to reproduce the behavior.
download .deb file from release
install it
login
play a song
Environment
Additional context
the app output:
@SO9010 commented on GitHub (May 24, 2025):
Does this happen when you build it you're self?
@jacksongoode commented on GitHub (May 25, 2025):
Seems like an upstream bug with
souvlakiafter the package was upgraded?@SO9010 commented on GitHub (May 25, 2025):
Yeah it looks like an error in the initiation of the crate!
@SO9010 commented on GitHub (May 25, 2025):
I think I found the issue, in diffie_hellman.rs:11:46 we have the line
The problem is, when we get a negative it crashes the program. It should be a u32.
Edit: Never mind this just sped up the loading...
The issue is actually the fact that we are introducing numbers into our dbus name, we could change it to chars!
@SO9010 commented on GitHub (May 25, 2025):
This should be fixed now, just quickly put together a random string generator based off unix time and made that to be part of the id :P I pushed already as its quite an urgant change. Ill keep this issue open just a bit longer.
@SO9010 commented on GitHub (May 29, 2025):
Is this fixed now?
@samwh1te commented on GitHub (May 29, 2025):
I had the same issue, but seems fixed for me now. Thank you!!