-
Notifications
You must be signed in to change notification settings - Fork 154
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
Bug reports on extensions.gnome.org #76
Comments
The link can be added in description such that the description becomes 'Shows CPU temperature, HDD temperature, voltage and fan RPM. Report issues here: https://github.com/xtranophilist/gnome-shell-extension-sensors/issues'. The same would also appear in the extensions listing page. Also, the url won't be linkified/clickable. |
Hmm, both ideas don't look too good to me. I will poke one of the gnome server administrators to get an idea what they suggest for solving this issue. |
Has there been any progress on the actual bugs that the users are reporting? It seems that it crashes GNOME Shell when installed now, and one user says it leaves the system unusable. What further information do you need to help fix the issue? |
The report "thingies don't work" is of no value and there is no sane way to gather informations via the comments because there is no notification for me if someone writes a comment or even the most primitive support of formatting, read paragraphs, so it's a pain to properly respond on peoples question. So yeah, I won't watch the comments for reports.
See for example #79. I need some responsive issue reporter and a sane way to ask questions to the reporter. Both of those things can't be provided by the extensions.gnome.org homepage so I won't use it. |
Is there any way of switching off the "Report Bugs" on the Gnome extension page. I entered an issue there but given the above, it is a "black hole". I will create an issue here. |
It seems like the users are trying to report issues in the comments of the extension installation page.
I would like to fix the issues, but to be honest I'm not willing to handle those issues within the limited capabilities of the comments section. Is there a way to tell them by an additional link or some text that issues should be reported here?
The text was updated successfully, but these errors were encountered: