Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#78323 - [home-assistant] Missing Text Labels (Frontend)
Attached to Project:
Community Packages
Opened by Yu Tendo (YuTendo) - Friday, 28 April 2023, 20:34 GMT
Last edited by Maxime Gauduin (Alucryd) - Sunday, 14 May 2023, 20:29 GMT
Opened by Yu Tendo (YuTendo) - Friday, 28 April 2023, 20:34 GMT
Last edited by Maxime Gauduin (Alucryd) - Sunday, 14 May 2023, 20:29 GMT
|
DetailsDescription:
The configuration dialog of the MQTT integration (no third party) has no text labels. The input fields are there and the dialog is fully functional. I do not use any third party themes. Example 1 / Steps to reproduce Settings -> Devices & Services -> Add Integration -> Search for "MQTT" -> Select "MQTT" -> The dialog has no text labels. Example 2 / Steps to reproduce After the integration is completed (by guessing the meaning of the input fields), also the "Re-Configure MQTT" Dialog has no text labels (see attached image as an example). Further Details: - The issue occurs with Firefox, Chrome, and also using the Android App - I first asked about this issue in the official forum and on Discord but without any result (https://community.home-assistant.io/t/the-text-labels-are-missing-in-the-mqtt-configuration-dialog/563808) - I did inspect the frontend with the Web Developer Tools in Firefox but couldn't find any error - I checked the logfiles on server side -no errors I literally have no idea what is causing this issue. I am happy about any thoughts! Thank you :) 
no_text_labels_mqtt.png
(46.7 KiB)
|
This task depends upon
Closed by Maxime Gauduin (Alucryd)
Sunday, 14 May 2023, 20:29 GMT
Reason for closing: Fixed
Additional comments about closing: 2023.5.2-2
Sunday, 14 May 2023, 20:29 GMT
Reason for closing: Fixed
Additional comments about closing: 2023.5.2-2
Update: I installed the most recent version directly using PIP, and this bug doesn't occur there. So it seems like the Arch Linux specific package is missing something. I even built the most recent version using this PKGBUILD, just changed version numbers and git-tags, and the same bug occurs even though it doesn't when installed via pip.
Maybe we should convert this into a meta-package that actually installs directly via pip?
The following command needs to be added to the PKGBUILD:
python -m script.translations develop --all
I added it to the build() function, before calling python -m build and that fixed the bug, but I suppose it might make more sense to call it in prepare()?
Also I'm not sure what the parameter "develop" does, I just copied this from the pip-installer. There might be a production-replacement for it. Either way, this fixes the bug.