OS Name: Ubuntu Plucky Puffin (development branch)
OS Build: (null)
OS Type: 64-bit
GNOME Version: 48
Windowing System: Wayland
Kernel Version: Linux 6.14.0-10-generic
Problem Description:
I noticed that blue circle with i icon was replaced with a red box of unknown when after the process for making bootable USB was complete.
That’s interesting to see that topic was closed for 20 Minutes.
Hello @wxl, I noticed this topic was re-opened and edited (Replacing a vote to a link of relation), I wanna know is there a reason why this discourse is not a place for Bug reports but feedback?
I’ve said elsewhere I don’t think this is a place for bug reports in general. In that same discussion, I also agreed that referencing them here is not a bad idea. I guess I’m just getting used to that
Part of the reason for this is because the original post above had a teeny tiny mention of the bug report I missed at first glance. I made this front and center with a little more attention drawn to it. That way, it directs the discussion on the subject to the place where it belongs (the Launchpad bug report you created). I removed the poll because Launchpad has it’s own built in “affects me, too” function and I didn’t want users to think that answering the poll was sufficient to report that information.
In the end, I flipped your post upside down. I think if further bug reports are created here in that format, it would make a lot more sense.
Oh don’t you worry, I’ll make sure it won’t happen again, unless if it’s allowed.
I thought Technical Supports are welcome to this discourse, since November 2024, but I apologize for lack of understanding.
I appreciate for correcting this topic to make it more sense, not only you remove the poll list by replacing, but you also removed the “Related Topic” list, which make sense to me. Because of the direct link.
And with that being said, you welcome, and I indeed, apologized for lack of following a guidelines properly.
As in that referenced discussion, we have no documented policy on this, so there’s no need to apologize.
They most certainly are! I probably wouldn’t even be here if it weren’t for that (the only reason Lubuntu was hosting their own Discourse is because of this).
I think “technical support” is a little bit different for a release in development. There’s not necessary a guarantee that everything works correctly. This is an important distinction as it relates to expectations. If a released version isn’t working correctly, I would be surprised, as my expectation is that after all that testing, (at least most) of the bugs should have been worked out. A much lower expectation should be given to a development release. Given those expectations, I wouldn’t be surprised to see someone complaining about a released version, but I would expect someone dealing with a problem in a development version would instead be collaborating.
This isn’t technical support, though. This is different. This is a bug report. You say it in your title. Properly formed bug reports are crucial to ensure that developers get all the information they need to fix it. There are excellent tools within Launchpad to manage bugs, collaborate on them, aggregate data, etc. etc. etc. As someone who deals in development, I’d go so far as to argue that they’re practically a requirement. So you did the most important step to ensure the bug will get fixed: ubuntu-bug.
At least in the live Lubuntu environment, I see no issues in usb-creator-gtk or usb-creator-kde, which also originates from the usb-creator 0.4.0 package:
I’m still inclined to close this because bug reports belong on a bug tracker, not in technical support. That’s where the discussion needs to happen.
Technical support is markedly different in that it focuses on the micro level: the user. Technical support issues become bugs only when they are reproducible by multiple people, meaning the problem is at a macro level.
In a technical support forum, such as this, it’s meant to fix problems for an individual user. Bug reports are for issues and discussions fixing operating system components or applications, which fixes for everyone.
My inclination to close this is to keep the discussion on a confirmed bug in the bug report and to keep the discussion from being split. Split discussions are fragmentary and not useful.
Absolutely! It certainly seems to be valid! My point is that it doesn’t need to be posted here to draw attention. Those that get the bug reports can discuss and act on it.
It stays open for three days following a solution being marked. However, to keep the discussion in the bug report, let’s go ahead and close it.
