Ubuntu Version: 25.04
Desktop Environment GNOME
Problem Description: post about screen keyboard is closed so i can’t comment.
I submitted the bug to launchpad and now the bug is fixed:
1 Like
It seems to me that the place for discussing the bug is the bug itself. It’s useful to mention here so that people having problems can find it, but it’s not necessarily the place for discussion.
Also, all topics in this category automatically close in a month, so if it’s not resolved before then, it will necessarily get closed. We can change that, but we can’t guarantee the post will otherwise stay open by itself.
Adding the extra maintenance of managing this post in some special way when discussion on the subject isn’t even relevant here doesn’t make a lot of sense to me at all.
So if I find a fix for a problem discussed in a closed post I must ignore it or open a new post?
Moving to the Site Feedback category, as this seems a question of policy (should the site do X or Y?), with an example cited.
My opinion (not policy) is that closing the loop on some of these might be helpful to future help-seekers.
- The format you have introduced (link to topic, statement of closure, link to bug) is good.
- If I run across new topics so formatted, I will simply merge them into the linked (closed) topic.
- Go ahead and open a new topic, and thank you for doing that research.
I am not suggesting folks run off to match bug reports with old (closed) posts here as a form of widespread contribution. I see somewhat limited benefit to the community from that kind of effort, as those bugs should indeed be discussed on the bug tracker.
Another option is to ping a moderator and ask them to reopen the original topic. This option takes longer and requires more work by both you and the moderator. It is available for cases where discussion about the fixed issue (explanations, usage, etc.) might be useful.
1 Like
Generally speaking…
The original topic was closed because it was essentially a bug report. I don’t think we have a policy on this, but I think we should have a policy that this is not a place to report bugs. In discussions here, we can reveal bugs, but once we do, we should report them to the correct places (not here).
I do think it’s a good practice (not policy) that relevant bug reports are linked to the discussion. At that point, one can easily figure out whether or not the bug is fixed simply by going to the linked bug report.
It’s not a bad idea to include a message in the discussion that the bug has actually been fixed. It’s not necessary if the bug is linked, like I said, but it just makes things more obviously clear.
In the event that the topic is closed, I think @ian-weisser 's suggestions are good ones. But again, note that this causes more work for both the user and the moderator. And that it’s not necessary, like I said above. So I would in general suggest we avoid this.
More specifically…
I missed a rather important detail because I had kind of honed in on the subject. I read it to mean “the closed post which I’ve linked to should not be closed until the problem it mentions is fixed.” Within that context, I read an implication that the problem was not fixed.
Because of that, I didn’t even notice the text “now the bug is fixed.” Had I seen that, I probably would have merged the topics, too.
1 Like
Hey everyone,
I noticed this topic has managed to fix screen-keyboard issues, it looks a bit different and looks updated.
In fact and FWIW, I will give @corradoventu a thanks for giving me a support by helping me like a team especially using Launchpad.net as a relate. The problem for tablet users when it comes to screen keyboard is now fixed. 
For this reason, as the user has expressed that the problem was fixed, I’m setting this topic to close.
1 Like
Which I’m appreciate that. 
1 Like
This topic was automatically closed after 3 days. New replies are no longer allowed.