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

Rofi broken border after update to 1.7.7 #53897

Closed
ACR-Jeff opened this issue Jan 8, 2025 · 6 comments
Closed

Rofi broken border after update to 1.7.7 #53897

ACR-Jeff opened this issue Jan 8, 2025 · 6 comments
Labels
bug Something isn't working needs-testing Testing a PR or reproducing an issue needed

Comments

@ACR-Jeff
Copy link
Contributor

ACR-Jeff commented Jan 8, 2025

Is this a new report?

Yes

System Info

Void 6.12.8_1 x86_64 AuthenticAMD uptodate rmFFFFFFFFF

Package(s) Affected

rofi-1.7.7_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

davatorium/rofi#2076

Expected behaviour

Rofi-MyTheme

Actual behaviour

Border-Issues

Steps to reproduce

xbps-install -Su
Restart system
Open Rofi
Border theme is broken on execution

@ACR-Jeff ACR-Jeff added bug Something isn't working needs-testing Testing a PR or reproducing an issue needed labels Jan 8, 2025
@tranzystorekk
Copy link
Contributor

Upstream issue

@tranzystorekk tranzystorekk closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2025
@ACR-Jeff
Copy link
Contributor Author

ACR-Jeff commented Jan 9, 2025

Upstream issue

I know. I was reporting it as an issue because it's and issue, Rofi has been updated to 1.7.7_1 in void packages, With issues, Wouldn't that be considered an issue and need resolved or rolled back? I am not understanding this, Issues should be reported correct?

@tranzystorekk
Copy link
Contributor

This bug tracker is meant for issues caused by void-packaging itself, and the reported issue doesn't warrant a rollback or urgent fixup.

@ACR-Jeff
Copy link
Contributor Author

ACR-Jeff commented Jan 9, 2025

This bug tracker is meant for issues caused by void-packaging itself, and the reported issue doesn't warrant a rollback or urgent fixup.

Ok makes sense, Thank you

@sgn
Copy link
Member

sgn commented Jan 9, 2025

This bug tracker is meant for issues caused by void-packaging itself, and the reported issue doesn't warrant a rollback or urgent fixup.

Nah, I think functionality upstream issues should also be reported here.

@ACR-Jeff
Copy link
Contributor Author

This bug tracker is meant for issues caused by void-packaging itself, and the reported issue doesn't warrant a rollback or urgent fixup.

Nah, I think functionality upstream issues should also be reported here.

This is what I've thought as well and where I was coming from in my previous comment. I've seen others reporting upstream issues, So I figured it was good to go and get the issue at least report it to have it known as an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-testing Testing a PR or reproducing an issue needed
Projects
None yet
Development

No branches or pull requests

3 participants