mirror of
https://github.com/mumble-voip/mumble.git
synced 2026-03-03 00:46:56 -05:00
Render Glyph failed after all monitors disconnect on sway/wlroots #2322
Labels
No labels
GlobalShortcuts
Hacktoberfest
accessibility
acl
asio
audio
bonjour
bsd
bug
build
certificate
ci
client
code
documentation
external-bug
feature-request
gRPC
github
good first issue
help wanted
help-needed
ice
installer
linux
macOS
needs-ckeck-with-latest-version
needs-more-input
overlay
positional audio
priority/P0 - Blocker
priority/P1 - Critical
priority/P2 - Important
priority/P3 - Somewhat important
priority/P4 - Low
public-server-registration
qt
recording
release-management
server
stale-no-response
stale-support
support
task
test
theme
translation
triage
ui
windows
wontfix
x64
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mumble-mumble-voip#2322
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 @mweinelt on GitHub (Nov 16, 2021).
Describe the bug
I'm on sway/wlroots and by powering off my monitor it disconnects the last graphical output device. When i come back to power it on again the mumble font face becomes instantly garbled and hardly readable.
Steps to Reproduce
Steps to reproduce the behavior:
Expected behavior
The font face should still be intact after a monitor has been disconnected.
Screenshots
TODO: next time I'll hit the problem
Desktop (please complete the following information):
Additional context
@Krzmbrzl commented on GitHub (Nov 16, 2021):
Do other Qt-based applications work after this procedure? 'cause I am suspecting that this might be a Qt bug rather than a Mumble bug, since we don't do any font rendering ourselves (afaik) 🤔
@mweinelt commented on GitHub (Nov 16, 2021):
Mumble is unfortunately the only Qt application I'm using. More of a terminal person. But I agree that this sounds like a Qt problem.
@Krzmbrzl commented on GitHub (Nov 16, 2021):
This entire paragraph looks like there are some deeper issues within Qt in this case.
I also don't find much about the encountered errors online. There are a few mentions here and there, but nobody seems to know why this would happen and what that means.
For the time being though, I am like 90% certain that this is not an issue related to Mumble (directly) but is instead related to Qt and/or some font rendering primitives (or a combination thereof). As such I'll close this issue.
I think it would probably be worth it to create a minimal Qt GUI example (just copy&paste one of their examples (e.g. https://doc.qt.io/qt-5/qtwidgets-mainwindows-application-example.html) and see if the issue persists. If it does, please file a bug report for Qt and if it doesn't, get back here (in that case we might have to rethink blaming Qt) 🤔