Proactive & Constructive Problem Reporting (Advice)

Here is where you can post tips and tricks to share with other users of MX. Do not ask for help in this Forum.
Message
Author
Vektor
Posts: 118
Joined: Fri Jul 30, 2021 8:00 pm

Re: Proactive & Constructive Problem Reporting (Advice)

#21 Post 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
You do not have the required permissions to view the files attached to this post.

User avatar
fehlix
Developer
Posts: 12996
Joined: Wed Apr 11, 2018 5:09 pm

Re: Proactive & Constructive Problem Reporting (Advice)

#22 Post 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.

User avatar
richb
Administrator
Posts: 11044
Joined: Wed Jul 12, 2006 2:17 pm

Re: Proactive & Constructive Problem Reporting (Advice)

#23 Post by richb »

I have to say it confuses me.( And I am not a new user). The current instructions do NOT confuse me.
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB

User avatar
Eadwine Rose
Administrator
Posts: 15405
Joined: Wed Jul 12, 2006 2:10 am

Re: Proactive & Constructive Problem Reporting (Advice)

#24 Post by Eadwine Rose »

Would 'QSI copied for the forum, click paste in a reply' be sufficient?
MX-23.6_x64 July 31 2023 * 6.1.0-40amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

Vektor
Posts: 118
Joined: Fri Jul 30, 2021 8:00 pm

Re: Proactive & Constructive Problem Reporting (Advice)

#25 Post 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

Vektor
Posts: 118
Joined: Fri Jul 30, 2021 8:00 pm

Re: Proactive & Constructive Problem Reporting (Advice)

#26 Post 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

User avatar
fehlix
Developer
Posts: 12996
Joined: Wed Apr 11, 2018 5:09 pm

Re: Proactive & Constructive Problem Reporting (Advice)

#27 Post 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.

Vektor
Posts: 118
Joined: Fri Jul 30, 2021 8:00 pm

Re: Proactive & Constructive Problem Reporting (Advice)

#28 Post 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

Vektor
Posts: 118
Joined: Fri Jul 30, 2021 8:00 pm

Re: Proactive & Constructive Problem Reporting (Advice)

#29 Post 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

MXRobo
Posts: 1844
Joined: Thu Nov 14, 2019 12:09 pm

Re: Proactive & Constructive Problem Reporting (Advice)

#30 Post 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. :p

Post Reply

Return to “Tips & Tricks by users (not for help)”