Page 1 of 1
Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 9:18 am
by manyroads
If you are new to Linux or just need a refresher, here are some pointers on obtaining excellent support.
Prepare your problem report(s) per the instructions on this site:
https://forum.mxlinux.org/viewtopic.php ... 62#p255062 
NEXT: If your problem is not just with this distro team's work (builds), it is, also, involving a software application & or desktop environment or window manager, etc., report your issue to those responsible for developing the actual software, as well. Examples of those you should report to, beyond MX, include the developers of:
-- xfce
-- KDE
-- Debian
-- Dropbox
-- LibreOffice
-- Firefox
-- Thunderbird, etc.
If you are experiencing difficulty with lesser know applications such as:
-- tint2
-- conky
-- dmenu
-- geany
-- timeshift, etc.
... you should, also, consider reporting your problem to the actual developer(s) such as you may find on Github, Gitlab, etc.
Remember the Linux system you are running is built of an array of components from many communities. Help is available to you in almost all of them. Most importantly, true resolution of your software bugs may only be fixable by the folks who performed the original software development.
One last reminder
....
If your problem involves a lack of understanding, confusion, or similar, READ the documentation manual (RTFM); and/or ,SEARCH these forums and the WIKI.
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 9:20 am
by Eadwine Rose
And now we have to get them to read this....
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 9:28 am
by manyroads
Eadwine Rose wrote: Tue Nov 02, 2021 9:20 am
And now we have to get them to read this....
Never happen.... :lipsrsealed:
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 9:30 am
by Eadwine Rose
Thank you for the effort to write this up though! I do hope some will take guidance from it :)
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 9:48 am
by richb
Eadwine Rose wrote: Tue Nov 02, 2021 9:30 am
Thank you for the effort to write this up though! I do hope some will take guidance from it :)
+1
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 9:49 am
by SwampRabbit
It might be worth "stealing" some of the above or appending it to linked thread. @richb what do you think?
edit: nvm I see he saw it now
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 10:04 am
by richb
SwampRabbit wrote: Tue Nov 02, 2021 9:49 am
It might be worth "stealing" some of the above or appending it to linked thread. @richb what do you think?
edit: nvm I see he saw it now
What linked thread?
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 10:17 am
by junoluna
richb wrote: Tue Nov 02, 2021 10:04 am
What linked thread?
from the OP
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 10:18 am
by SwampRabbit
richb wrote: Tue Nov 02, 2021 10:04 am
What linked thread?
The one Mark linked to in his first post.
https://forum.mxlinux.org/viewtopic.php ... 62#p255062
Edit: Grrr... seems like a minute too late with posts today
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 10:24 am
by richb
That would be a good addition. I will take the liberty of streamlining it and retain the point.
EDIT: You were not really late. The link in the other post was truncated and therefore cannot be reached.
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 10:36 am
by Adrian
Eadwine Rose wrote: Tue Nov 02, 2021 9:20 am
And now we have to get them to read this....
I'll believe it when I see it, like when people will figure out that the QSI copies the correct code for the forum (as it clearly says it in the message) or when they click the "Accept this answer" (checkmark) button instead of editing the post title by hand.
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 11:20 am
by manyroads
+1
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 11:49 am
by SwampRabbit
@richb I meant that it seems that as I typed something everyone beat me to the punch by one minute the last few posts... just interesting... or are you people spying on me?
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Tue Nov 02, 2021 11:50 am
by Eadwine Rose
Quick! Hide the stuff!!!
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 1:59 pm
by Vektor
I considered creating a new topic but this one seems appropriate.
I see many posters unable to post their QSI properly. I was scared to post mine until I knew it would be correctly done. Using the Preview feature helped alot.
The first time I tried was in the quick reply, but there are no buttons at all.
I eventually clicked the "Full Editor & Preview" and there the buttons were. So I clicked on the "</>" button. The icon is obscure as to function and the popup when hovering is equally obscure as a first time user. No mention of QSI at all.
The "code][/code" in brackets pops up with a flashy thingy in the middle but after a few seconds of mouse inactivity in the editor it stops flashing. If I am looking at the QSI terminal window and resulting popup I lose the flashing cursor and am confused as where to paste.
I typed something bold to show where to paste like this: code]PASTE HERE[/code and then clicked Preview. I right clicked in the middle of the bold text and pasted the info. Checked the Preview. The bold text showed in the QSI but was not interfering with it. Like this:
Code: Select all
PASTE
[code]
Snapshot created on: 20220425_2051
System:
Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: bdev=sda8 quiet splasht nosplash
Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-21.1_KDE_x64 Wildflower October 20 2021
base: Debian GNU/Linux 11 (bullseye)
Machine:
Type: Laptop System: Hewlett-Packard product: HP 2000 Notebook PC
v: 0886130003305910000620100 serial: <filter> Chassis: type: 10
serial: <filter>
Mobo: Hewlett-Packard model: 188B v: KBC Version 69.18 serial: <filter>
UEFI-[Legacy]: Insyde v: F.37 date: 06/26/2013
Battery:
ID-1: BAT0 charge: 34.7 Wh (92.0%) condition: 37.7/37.7 Wh (100.0%)
volts: 12.1 min: 10.8 model: Hewlett-Packard Primary type: Li-ion
serial: <filter> status: Unknown
CPU:
Info: Dual Core model: AMD E-300 APU with Radeon HD Graphics bits: 64
type: MCP arch: Bobcat family: 14 (20) model-id: 2 stepping: 0
microcode: 5000119 cache: L2: 512 KiB
flags: lm nx pae sse sse2 sse3 sse4a ssse3 svm bogomips: 5190
Speed: 1295 MHz min/max: 780/1300 MHz Core speeds (MHz): 1: 1295 2: 1296
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Wrestler [Radeon HD 6310] vendor: Hewlett-Packard
driver: radeon v: kernel bus-ID: 00:01.0 chip-ID: 1002:9802 class-ID: 0300
Device-2: Cheng Uei Precision Industry (Foxlink) HP Truevision HD type: USB
driver: uvcvideo bus-ID: 4-1:2 chip-ID: 05c8:0348 class-ID: 0e02
serial: <filter>
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver:
loaded: ati,radeon unloaded: fbdev,modesetting,vesa display-ID: :0
screens: 1
Screen-1: 0 s-res: 2732x768 s-dpi: 96 s-size: 722x203mm (28.4x8.0")
s-diag: 750mm (29.5")
Monitor-1: LVDS res: 1366x768 hz: 60 dpi: 101 size: 344x193mm (13.5x7.6")
diag: 394mm (15.5")
Monitor-2: VGA-0 res: 1366x768 hz: 60 dpi: 101 size: 344x194mm (13.5x7.6")
diag: 395mm (15.5")
OpenGL: renderer: AMD PALM (DRM 2.50.0 / 5.10.0-9-amd64 LLVM 12.0.1)
v: 3.3 Mesa 21.2.5 compat-v: 3.1 direct render: Yes
Audio:
Device-1: AMD Wrestler HDMI Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus-ID: 00:01.1 chip-ID: 1002:1314
class-ID: 0403
Device-2: AMD FCH Azalia vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel bus-ID: 00:14.2 chip-ID: 1022:780d class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-9-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network:
Device-1: Realtek RTL810xE PCI Express Fast Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 2000 bus-ID: 03:00.0
chip-ID: 10ec:8136 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter
vendor: Hewlett-Packard AR9485/HB125 802.11bgn 1×1 Wi-Fi driver: ath9k
v: kernel modules: wl port: 2000 bus-ID: 07:00.0 chip-ID: 168c:0032
class-ID: 0280
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 298.09 GiB used: 104.72 GiB (35.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: HGST (Hitachi) model: HTS545032A7E380
size: 298.09 GiB block-size: physical: 4096 B logical: 512 B
speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: ACA0 scheme: MBR
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.28 GiB used: 44 MiB (0.5%)
priority: -2 dev: /dev/sda10 maj-min: 8:10
Sensors:
System Temperatures: cpu: 71.1 C mobo: N/A gpu: radeon temp: 71.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: note: see --pkg apt: 2316 lib: 1242 flatpak: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Info:
Processes: 200 Uptime: 2h 7m wakeups: 2 Memory: 3.45 GiB
used: 2.31 GiB (67.1%) Init: SysVinit v: 2.96 runlevel: 5 default: 5
tool: systemctl Compilers: gcc: 10.2.1 alt: 10 Shell: bash
default: Bash v: 5.1.4 running-in: quick-system-info-mx inxi: 3.3.06
Boot Mode: BIOS (legacy, CSM, MBR)
HERE[/code]
I know how most people feel about CAPS but used in this way definitely got my attention.
My goal with this post is to maybe help reduce errors in posting and the resulting response of forum members.
Thanks for reading
Vektor
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 2:03 pm
by Eadwine Rose
We've been struggling with this for a LONG time. We even introduced a popup which contains instructions on how to use the QSI output. All people need to do is run it, and hit paste in a reply.
And not edit what comes out.
But a LOT of people don't follow instructions. *hands in the air*
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 2:11 pm
by Vektor
Yup. The popup contains this:
Code: Select all
Report copied to system clipboard
Report is already formatted for forum.
Paste directly into forum post.
The popup did not clarify the confusion for me. Without an obvious location to paste the QSI it is very easy to put it in the wrong spot.
Now that I know what to do it is easy.
Vektor
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 3:15 pm
by Vektor
So I modded the QSI to show where to paste. The end of the terminal output and the popup now show this:
Report copied to system clipboard
Report is already formatted for forum.
Paste code]HERE[/code into forum post.
Works for me.
Vektor
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 3:35 pm
by fehlix
Vektor wrote: Mon May 02, 2022 3:15 pm
So I modded the QSI to show where to paste. The end of the terminal output and the popup now show this:
Report copied to system clipboard
Report is already formatted for forum.
Paste code]HERE[/code into forum post.
Works for me.
Vektor
Hmm, perhaps to clarify (at least for other users reading this).
The Quick System Info (QSI) report does already contain the starting [
code] and ending code-tag [
/code].
The shown report on the terminal as well as the copied text into the Copy/Paste and the Select/Mark buffer does also contain those code tags. So imho, not need to add extra code tags into the forum post using the
[</>] button.
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 3:43 pm
by Vektor
The only text I added is "HERE" inside the code tags. I had to remove the outside brackets in the example because it made the code window, which I did not want.
Does that clarify?
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 4:23 pm
by Vektor
I hope this is better. My first picture in a post. Yay!
[img]file:///media/demo/63b4d169-b3af-403d-a155-43bc19b1e0a7/2-STORAGE/LINUX/OS/MX/SYSTEM-SETTINGS-FILES/QSI/QSI-result.png[/img]
Vektor
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 4:27 pm
by fehlix
Vektor wrote: Mon May 02, 2022 3:43 pm
The only text I added is "HERE" inside the code tags. I had to remove the outside brackets in the example because it made the code window, which I did not want.
Does that clarify?
The original text "Paste directly into forum post." tells what to do. The text you suggested, would potentially end up with having code-tags twice when pasted from Clipboard. OTOH, I see the idea, as new user may not know what those code-tags are ( like those [
code] here [/code] ) and how those magic is done of having the paste buffer filled by a report, b/c normally user do actively copy and afterwards paste. Now they get asked only paste, without having copied anything first - which may be confusing to new users.
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 4:30 pm
by richb
I have to say it confuses me.( And I am not a new user). The current instructions do NOT confuse me.
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 4:32 pm
by Eadwine Rose
Would 'QSI copied for the forum, click paste in a reply' be sufficient?
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 4:47 pm
by Vektor
The goal is to show where to click, nothing more. I experienced uncertainty the first time I did it. Trying to keep it simple.
Regardless, it works for me in my personal respin.
Thanks for your attention and a great os.
Vektor
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 5:02 pm
by Vektor
AHA! I have been using the "</>" button and pasting the QSI code in the middle instead of right clicking in the body of the post. Now I understand your responses. After I wiped the blood off my forehead from hitting the wall, I laughed.
Maybe it is too easy.
So the problem is that people are right clicking "select all" and "copy" in the QSI terminal before pasting in the body of the post. Is that right?
Just click "paste" and done.
Thanks for holding my hand,
Vektor
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 5:17 pm
by fehlix
Vektor wrote: Mon May 02, 2022 5:02 pm
AHA! I have been using the "</>" button and pasting the QSI code in the middle instead of right clicking in the body of the post. Now I understand your responses. After I wiped the blood off my forehead from hitting the wall, I laughed.
Maybe it is too easy.
So the problem is that people are right clicking "select all" and "copy" in the QSI terminal before pasting in the body of the post. Is that right?
Just click "paste" and done.
Either just "paste" (which what ever you use, e.g right-click and paste or just with keyboard Ctrl+v.
And in addition to normal "paste" you can use mouse middle-button "click to paste" from the select/mark buffer.
Both buffers - the normal clipboard "copy/paste" buffer and the "select/mark" buffer - may be emptied out, when the terminal get closed, which depends a bit on the settings and the terminal involved and on the DE in use (Kde, Xfce, Fluxbox or something else). In most cases user may have the clipboard manager running which captures a copy of one or both of the mentioned buffers, for re-use in case the paste-buffers get cleared. Or just simply don't close the terminal until they have pasted the report into the forums post or somewhere else.
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 5:38 pm
by Vektor
The problem is because I was looking at the three lines of the popup as unrelated pieces of info. I was seeing that:
1-info was copied to the clipboard (ok,thanks)
2-the QSI output in the terminal was formatted for the forum (whatever that means, website guru stuff)
3-paste directly into forum post (I thought I needed to hit that "</>" button first to avoid the really long post syndrome)
Maybe it IS too easy. I like to do things the hard way. Only then have I accomplished something.
Thanks again
Vektor
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 7:12 pm
by Vektor
In hindsight I should have started a new topic with post #15 ...
I have been analyzing why I was so confused about the QSI process. The terminal comes up with all that info, making me feel like I need to do something with it. In reality I did not even need to see it. The popup is probably enough for me.
I will try to shut up now.
Vektor
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 10:24 pm
by MXRobo
@Vektor No Vektor, please don't stop, you're making this newbie not feel so stupid after seeing your "Show off your bash - .rc, that is" post.
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Mon May 02, 2022 10:54 pm
by Vektor
If your life cannot serve as a shining example it can at least be a dire warning.
That is my life motto.
Vektor
Re: Proactive & Constructive Problem Reporting (Advice)
Posted: Sun May 08, 2022 3:33 pm
by seaken64
The problem is that many people do not understand the words and terms being used. Paste, QSI, Buffer, etc. It is ALL foreign to many new users. No matter how many instructions you write or how many times you suggest to read the instructions, many people do not understand the words. Some people will learn from watching a video. Maybe a link to a video can be added to that pop-up box? I don't know. Just spit-balling. I have no idea what the answer is.
Seaken64