| Summary: | Initial scrolling in Finder in a remote file directory is slow | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | joe |
| Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | buzea.bogdan, xiscofauli |
| Priority: | medium | Keywords: | perf |
| Version: | 6.1.2.1 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | macOS (All) | ||
| See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=112091 https://bugs.documentfoundation.org/show_bug.cgi?id=41987 |
||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 104742 | ||
|
Description
joe
2018-10-10 21:19:33 UTC
Pretty sure this is a duplicate. @Joe : please indicate how the remote share is mounted. In your description of Step 2 "Navigate to another computer on the same network", Finder lists all available network shares under "Shared" in the Finder sidebar - however, these shares can use various network protocols to provide the share from the other computers/machines on the network. Please indicate - the type of share (AFS, NFS, SMB, FTP, SSH, etc) - the access privileges on the share. > - the type of share (AFS, NFS, SMB, FTP, SSH, etc) Standard Finder mount. Finder says: Format: SMB (OS X) Server: smb://<name>._smb._tcp.local/<name> Kind: Volume > - the access privileges on the share. Read & Write If you need more details let me know. I can only reproduce this on the initial load of the first directory of a SMB mounted file share. Once the initial thumbnails have been produced, scrolling in any other subdirectory or other directory of the share appears to be normal. Testd against Version: 6.2.0.0.alpha0+ Build ID: a6032ff5418ad66cc8fec10c636e32b124ee7864 CPU threads: 4; OS: Mac OS X 10.14; UI render: default; VCL: osx; Locale: fr-FR (fr_FR.UTF-8); Calc: threaded Dear joe, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug Dear joe, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug |