Bug 295128

Summary:	no way to reach bottom area of window with vertical slider
Product:	[Applications] dolphin	Reporter:	Daniel Moyne <daniel.moyne>
Component:	general	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	frank78ac
Priority:	NOR
Version:	2.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Daniel Moyne 2012-03-01 13:06:53 UTC

Version:           2.0 (using KDE 4.8.0) 
OS:                Linux

In some instances when moving down the vertical slider of main window to disciver bottom area automatically the slider moves back where it was !

At this time when trying to move down with down arrow of keyboard the same phenomena occurs

Reproducible: Sometimes

Steps to Reproduce:
- try to move down the vertical slider of main window where there are file icons.

Actual Results:  
- the vertical slider moves back where it was positionned.

Expected Results:  
- the vertical slider stays where positionned by user

OS: Linux (x86_64) release 3.2.0-17-generic
Compiler: gcc

Comment 1 Frank Reininghaus 2012-03-04 11:15:40 UTC

Thanks for the bug report! I could not reproduce the problem.

Please provided more detailed information about how to get the buggy behaviour (like the view mode, grouping enabled/disabled, ...). A screenshot might also be helpful.

Comment 2 Peter Penz 2012-03-09 16:16:02 UTC

I guess this is a duplicate of bug 295584 - I've set it now as duplicate until Daniel responds...

*** This bug has been marked as a duplicate of bug 295584 ***

Comment 3 Daniel Moyne 2012-03-12 18:07:21 UTC

Unfortunately I experienced the problem few times without any logical explanation ;  now I have installed KDE 4.8.1 ; therefore the only thing I can do is use dolphin and report again if there is another occurence of this bug.
Thanks.

Comment 4 Peter Penz 2012-03-12 21:38:10 UTC

Please reopen the bug if you still are able to reproduce the issue in 4.8.2. But what we'd need then is really a detailed description like e.g. in bug 295584 how to reproduce the issue (but I hope this should not be necessary ;-)).