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

localsend: goes black after sending a file #354044

Closed
0n-s opened this issue Nov 6, 2024 · 4 comments · Fixed by #353481
Closed

localsend: goes black after sending a file #354044

0n-s opened this issue Nov 6, 2024 · 4 comments · Fixed by #353481
Labels
0.kind: bug Something is broken

Comments

@0n-s
Copy link

0n-s commented Nov 6, 2024

Describe the bug

LocalSend's window fades to black after a file is sent.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Go into the Send menu.
  2. Pick a file & send it to another device.
  3. Click Done.

Expected behavior

I should be sent back to the Send menu.

Screenshots

A screenshot of the LocalSend window, all black

Additional context

Not reproducible with Flatpak (tested).

Notify maintainers

@sikmir
@linsui
@Pandapip1

Metadata


Add a 👍 reaction to issues you find important.

@0n-s 0n-s added the 0.kind: bug Something is broken label Nov 6, 2024
@0n-s
Copy link
Author

0n-s commented Nov 6, 2024

Nothing in the changelog seems to indicate that's the case…

But if it is, linking that PR here: #353481

@0n-s
Copy link
Author

0n-s commented Nov 6, 2024

Tested the PR on my end. It is indeed fixed with that version.

@Pandapip1
Copy link
Contributor

This is because we had to move to unstable version because the version of Flutter that localsend was using was dropped from nixpkgs. It's likely that at some point a commit was introduced that caused this bug and a later commit fixed it. But no tag actually had said bug.

@0n-s
Copy link
Author

0n-s commented Nov 6, 2024

This is because we had to move to unstable version because the version of Flutter that localsend was using was dropped from nixpkgs. It's likely that at some point a commit was introduced that caused this bug and a later commit fixed it. But no tag actually had said bug.

Ah, that would make sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants