Hello Mate Community,
While in a Caja’s maximized window, it can’t scroll down to the lowest bottom area of caja’s window where the last row of icons reside (Ctrl + 1). A workaround is to unmaximize the window, so it can fully scroll down thus revealing the last row of file icons.
Is this a known bug? Is there a solved status?
According to this it was fixed in 17.04 but I see otherwise. It’s tied directly to window width in both Caja and Control Center. Did the fix get lost? @Wimpy?
For awhile in 16.10 Control Center happened to open at a bad width. I hope the fix wasn’t default window size.
Caja or Control Center. Either does it (Caja in Icons).
The opening width of Control Center is no longer a "bad" width like it was in 16.10.
Set width to just below where it changes to next higher columns.
My VMs are not full of files so I'll use Control Center.
@Bill_MI Following your lead, I was able to exactly reproduce this behavior in 17.10 beta installed bare metal. Control panel just won’t finish a scroll if you set its’ width just below a 4 icon width or a 3 icon width. Otherwise, control panel scrolls as expected. Weird…
Hi @mdooley and thanks for the confirm. I used the 16.10 example in the bug report because it was so easy to reproduce as Control Center opened bad by default. But today it takes more effort to see the bug which never went away AFAIK.
@monsta and @ouroumov, Do you see this in Control Center? I ask because in two 17.10 VMs I find Caja is very intermittent and may involve disappearing scroll bars and other settings getting too complex to find a pattern. I definitely create modes I cannot create the bug.
That's it, I was able to reproduce it that way before, but forgot about it
Yes, m-c-c is still affected in 17.10.
But now we're talking about two apps here... and as for Caja, it had been fixed several months ago, and the fix is included in 1.18.2, so I don't know why it would happen in 17.10. For reference, upstream pull request with the fix: