Bug 302293 - dolphin doesnt go to the top/bottom when scrolling
Summary: dolphin doesnt go to the top/bottom when scrolling
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: panels: folders (other bugs)
Version First Reported In: 2.0.95
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-21 11:02 UTC by Zé
Modified: 2013-09-02 21:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Dolphin does not show all contents of dir /usr and the scrollbar acts like it has reached the bottom (97.87 KB, image/png)
2012-06-21 11:06 UTC, Zé 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Zé 2012-06-21 11:02:45 UTC 
Sometimes dolphin does not scroll to the op or to the bottom and remain files/folders without appear.
Im attaching a screen-shot for a better understanding. 

Reproducible: Always

Steps to Reproduce:
Dont know how to reproduce, it happens randomly. 
Actual Results:  
Currently dolphin hides files/folders.

Expected Results:  
Dolphin should be able to show all files when scrolling to top/bottom.
Comment 1 Zé 2012-06-21 11:06:58 UTC 
Created attachment 72010 [details]
Dolphin does not show all contents of dir /usr and the scrollbar acts like it has reached the bottom
Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:50 UTC 
Resetting assignee to default as per bug #305719
Comment 3 Frank Reininghaus 2012-08-26 08:23:27 UTC 
Thanks for the report! I was not able to reproduce so far. If you find steps to reproduce this bug reliably, please let us know.
Comment 4 Frank Reininghaus 2013-08-28 15:33:18 UTC 
Is this problem still  reproducible in Dolphin 4.11.0 or later?
Comment 5 Emmanuel Pescosta 2013-08-29 15:42:26 UTC 
I can't reproduce it anymore.

Maybe fixed by commit ba2c5c71
Comment 6 Emmanuel Pescosta 2013-08-29 15:43:04 UTC 
Or maybe 02e41237
Comment 7 Frank Reininghaus 2013-09-02 21:17:45 UTC 
I agree with Emmanuel that these commits look like they might be related to the problem.

Feel free to reopen if you still see this in 4.11.0 or later. Thanks!