Bug 168918 - There is some issue with listing
Summary: There is some issue with listing
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-17 11:56 UTC by Danat
Modified: 2025-10-24 07:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
for ref: what googledrive looks like (110.18 KB, image/png)
2025-10-18 03:42 UTC, fpy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Danat 2025-10-17 11:56:10 UTC
Description:
https://drive.google.com/drive/folders/1OPlZR2d8I9t3zjhg4smAQroEfe2khly4?usp=sharing

Actual Results:
In the video

Expected Results:
In the video


Reproducible: Always


User Profile Reset: No

Additional Info:
In the video
Comment 1 fpy 2025-10-18 03:42:08 UTC
Created attachment 203400 [details]
for ref: what googledrive looks like
Comment 2 fpy 2025-10-18 03:43:19 UTC
Please be more specific in filling in the form and attaching relevant files here.

see https://wiki.documentfoundation.org/QA/BugReport#Good_reports
Comment 3 Danat 2025-10-18 03:54:28 UTC
(In reply to fpy from comment #2)
> Please be more specific in filling in the form and attaching relevant files
> here.
> 
> see https://wiki.documentfoundation.org/QA/BugReport#Good_reports

Respectfully, there seems to be no way to file a bug in a way that would satisfy you. There is always something you don't like about it

Who do you think you are? I made a video and gave you the file. Is that not enough?

I gave you the video to watch and the file in case you might need it
Comment 4 Buovjaga 2025-10-23 20:09:23 UTC
(In reply to Danat from comment #3)
> (In reply to fpy from comment #2)
> > Please be more specific in filling in the form and attaching relevant files
> > here.
> > 
> > see https://wiki.documentfoundation.org/QA/BugReport#Good_reports
> 
> Respectfully, there seems to be no way to file a bug in a way that would
> satisfy you. There is always something you don't like about it
> 
> Who do you think you are? I made a video and gave you the file. Is that not
> enough?
> 
> I gave you the video to watch and the file in case you might need it

A video can provide an additional look at an issue, but you should describe enumerated steps to reproduce the problem.
Comment 5 Danat 2025-10-23 21:35:02 UTC
(In reply to Buovjaga from comment #4)
> (In reply to Danat from comment #3)
> > (In reply to fpy from comment #2)
> > > Please be more specific in filling in the form and attaching relevant files
> > > here.
> > > 
> > > see https://wiki.documentfoundation.org/QA/BugReport#Good_reports
> > 
> > Respectfully, there seems to be no way to file a bug in a way that would
> > satisfy you. There is always something you don't like about it
> > 
> > Who do you think you are? I made a video and gave you the file. Is that not
> > enough?
> > 
> > I gave you the video to watch and the file in case you might need it
> 
> A video can provide an additional look at an issue, but you should describe
> enumerated steps to reproduce the problem.

I gave those steps in other reports, and he still didn't approve them. In my opinion, those steps can sometimes create more confusion than understanding

If I read the steps, most of the times, I will have no clue about the issue. But if somebody showed me - that would give me much more understanding. Spoken language is not good at conveying software bugs
Comment 6 Buovjaga 2025-10-24 07:00:13 UTC
(In reply to Danat from comment #5)
> (In reply to Buovjaga from comment #4)
> > (In reply to Danat from comment #3)
> > > (In reply to fpy from comment #2)
> > > > Please be more specific in filling in the form and attaching relevant files
> > > > here.
> > > > 
> > > > see https://wiki.documentfoundation.org/QA/BugReport#Good_reports
> > > 
> > > Respectfully, there seems to be no way to file a bug in a way that would
> > > satisfy you. There is always something you don't like about it
> > > 
> > > Who do you think you are? I made a video and gave you the file. Is that not
> > > enough?
> > > 
> > > I gave you the video to watch and the file in case you might need it
> > 
> > A video can provide an additional look at an issue, but you should describe
> > enumerated steps to reproduce the problem.
> 
> I gave those steps in other reports, and he still didn't approve them. In my
> opinion, those steps can sometimes create more confusion than understanding
> 
> If I read the steps, most of the times, I will have no clue about the issue.
> But if somebody showed me - that would give me much more understanding.
> Spoken language is not good at conveying software bugs

I've triaged something like 15 thousand reports here and elsewhere and I disagree. Written steps are fine and don't create confusion, if written in a simplistic way. Long and rambling texts do create confusion, though. Images and videos may enrich reports, as I said. The point is how quickly others get the idea. An image will be quicker than a video. An image can show how something looks bad while a video can show how something behaves badly. A video can be like a long text, frustrating to go through while waiting to get to the point.