VehiclesFashionRecipesBlogsHuntTravelsSportFunHandmadeITEducation
Mini-Games
x

x
zakruti.com » IT - Software » IT, programs, coding
Things To Consider When Filing Bug Reports DistroTube

Things To Consider When Filing Bug Reports DistroTube

FBTwitterReddit

video description

Rating: 4.0; Vote: 1
Things To Consider When Filing Bug Reports DistroTube In today's boomer vlog, I talk a bit about filing bug reports or opening support requests. What is the proper venue for opening support requests? What information should you include in your post? And why is it important to do it right!
Date: 2022-03-30

Comments and reviews: 10


Has a dev myself, I have this problem with some of my clients (tbh some of them dont give two rats ass and just say -fix it-). To put it simply if we cant replicate we gonna waste 1h pursuing some bug that could be easily fix 10minutes.
And some bug related websites and such even have templates to fill a bug report. In order to be even more efficient and less time consuming.
Also, Im using on my personal machine (not a production one) and Im looking on the xmonad config files to use my keybindings as I prefer, there are some things I would do different but I think is mostly -taste- of my own, for example on the xmonad config you have two keybindings one for recompiling and other to start xmonad. Im assuming this is because of emacs that after the recompile it gives errors, im assuming since I didnt try it out, I here would do a keybinding for both, something of the sort of 'xmonad --recompile && xmonad --restart' in this case if the recompile fails it wont start xmonad. But again this is one of those things that everyone can do it differently and a tangent on my part, in terms of the config files and scripts, everything is very readeable and easy to understand why you did it.

reply

As a developer I hate bug reports from end users from UAT (User Acceptance Test). As a developer I get requirements for a change and/or enhancement. I follow it to a tee and make everything is work right. Then to TEST and QA servers by our test team signing off on it. Then in UAT the user says -Oh this should be different-... even though it wasn't in the specs given by the user. My boss is cool and sticks up for us and tells them to open another ticket because this is done to spec and what the user is talking about has nothing to do with the changes they wanted. Luckily my team at a major global bank from New York is all remote as well as the business people are from all over (India, Belgium, Poland, and US (Pittsburgh and NY)). Some of these business people if I saw them face to face I'd probably beat them :) LOL
reply

As someone who has been moving all their machines and workflows to Linux, the most annying thing when having an issue is when you use a search engine to look for something, and the first result is a 2 or 3 year old reddit or other forum thread where all the replies are just -you should google this- -.
Don't do that, if you know the up to date answer and have the time to share it (or link to it), do so. Otherwise don't respond as more posts = more clicks = higher search enging ranking, even if the posts themselves are not useful to answer the querry.

reply

I understand why you don't want to answer questions past 1-2 days, but alot of people won't follow through on messing with this until a week or two down the road... That's when they will have their questions. Yes it would be hard to follow up if you had 1-2k comments but on most of these vids there is less than 300 total comments. I have responded to comments months later...but then again I'm not as busy as most people, so I do understand.
reply

Interesting video. For myself, if I can't find others with the same issue and a posted fix, at the stage I'm at now, I'll take a backup and try different things till I find something that works. If I break it, restore it and keep on trying. This is actually the best way to learn things and move to higher levels. What I like about watching Linux videos is learning new things I never thought of, or never knew I wanted. Good video DT.
reply

Thank you for the commentary, us developers find it extremely disrespectful when people demand we try to fix an issue that they are having without being willing to spend the 5 minutes needed to fill out the template. It makes it so much harder to actually figure out the problem if we aren-t even given the steps needed to witness the issue that we CLEARLY haven-t seen yet.
reply

I think you should really consider this from a different angle. Having answers to support questions in YT is probably the most helpful place they can be. If I saw the DTOS video and tried the script and got an error message, the first place I am looking is the comments of that video.
reply

Bug Report:
User: I am having a problem
Developers: what kind of problem?
User: it doesn't work!
Developers: what doesn't work?
User: my coffee maker makes my coffee taste bad! Should I restart my computer?
Developers: no just change your coffee shop!
Lmao!

reply

If a particular piece of software or distro have it's own user forum, it's often a good idea to post potential bugs over there instead. It tend to beople on those forums that can confirm there are a bug and if the bug is already reported.
reply

Take Care Derek! Your eyes do look a bit strained. Are you using some kind of eye-saver software/display settings on your main production machine? I am looking for some.
Thanks for the video! Take care & rest well!

reply
Add a review, comment






Other channel videos