Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File manager window not scrollable to bottom, mostly, in Sway tiled window #1796

Open
scott092707 opened this issue Dec 11, 2024 · 5 comments

Comments

@scott092707
Copy link

Expected behaviour

I should be able to scroll down to the end of a large number of icons, that do not all fit in the window.

Actual behaviour

I mostly can only scroll down ~70% (guesstimate, based on two of my tabs)

Steps to reproduce the behaviour

open location that has many icons

MATE general version

running Sway 1.9-2 (Wayland), not MATE

Package version

1.26.3-1+b1

Linux Distribution

Debian Testing

Link to bugreport of your Distribution (requirement)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089672

From my Debian bug report:

#######################################################################################
`I use the Sway Wayland compositor, and have my system set up to always have my
text editor in the left tile of workspace 2, and Caja in the right tile with 9 tabs
(or more). (Each then occupies 1/2 the screen.)
(Caja comes up as handled by xwayland)
I use a 49" TV as a monitor, and do not scale the display.
Several of the Caja tabs that I always open have more icons than will fit in
the window without scrolling.
The contents of these tabs will not scroll all the way to the bottom of the
window with the scroll-bar, nor can be reached with the "End" key,
nor can I highlight the right-most icon and press "down" and have it scroll
(the highlighting disappears, and probably actually does highlight the last
icon on the right, but I cannot see it.)
To see and be able to use the icons that are out of view, I have to instruct
Sway to send Caja's window to an empty workspace - then, all icons are visible.

I say "mostly" in the title, because this does not occur in certain
circumstances:
If I do a screen-record with wf-recorder and try to demonstrate the
problem, the problem is not there, and I can scroll each tab's contents all
the way to the bottom.

Also, if I move the window to an empty workspace and turn it into a floating
window while a certain tab is focused, and then turn it back into a tiling
window, and move the window back to the original workspace (where it shares
the workspace with my text editor), it is able to scroll to the bottom.
A different tab's contents still do not scroll to the bottom, until I repeat
the above work-around with that tab.

The following link shows two tabs in Caja's window, each is shown from the
original workspace, at maximum scroll, and also after moving to an empty
workspace, showing all icons.
Thus: 4 images, the first and third show one of the window tabs in the original
workspace, the second and fourth show the same window tab in the empty workspace.
https://imgur.com/a/aVY7cCi

-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9.7-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages caja depends on:
ii caja-common 1.26.3-1
ii desktop-file-utils 0.27-2
ii gvfs 1.54.2-1
ii libatk1.0-0t64 2.54.0-1
ii libc6 2.40-2
ii libcairo-gobject2 1.18.2-2
ii libcairo2 1.18.2-2
ii libcaja-extension1 1.26.3-1+b1
ii libexempi8 2.6.5-1
ii libexif12 0.6.24-1+b1
ii libgail-3-0t64 3.24.43-4
ii libgdk-pixbuf-2.0-0 2.42.12+dfsg-1
ii libglib2.0-0t64 2.80.3-1
ii libglib2.0-bin 2.80.3-1
ii libglib2.0-data 2.82.1-1
ii libgtk-3-0t64 3.24.43-4
ii libice6 2:1.0.10-1+b1
ii libmate-desktop-2-17t64 1.26.2-1.1+b1
ii libnotify4 0.8.3-1+b1
ii libpango-1.0-0 1.54.0+ds-2
ii libpangocairo-1.0-0 1.54.0+ds-2
ii libselinux1 3.7-3
ii libsm6 2:1.2.3-1+b1
ii libx11-6 2:1.8.7-1+b1
ii libxml2 2.12.7+dfsg+really2.9.14-0.1
ii mate-desktop 1.26.2-1.1+b1
ii shared-mime-info 2.4-5

Versions of packages caja recommends:
ii gvfs-backends 1.54.2-1
ii gvfs-fuse 1.54.2-1

Versions of packages caja suggests:
ii engrampa 1.26.2-4
pn gstreamer1.0-tools
pn meld

-- no debconf information`
#######################################################################################

@lukefromdc
Copy link
Member

lukefromdc commented Dec 11, 2024 via email

@sekelsta
Copy link

sekelsta commented Dec 22, 2024

I am seeing the same or similar. Happens reliably for certain folders at certain window sizes, though not often overall.
Here is an example of where it got stuck. I was unable to scroll down any farther than this:
Screenshot at 2024-12-22 08-03-39
If the window loses focus I become able to scroll again, even if it regains focus after. Then if I view the parent folder and then go back to the problem folder again, ability to scroll all the way down is again lost.
I am on standard Ubuntu MATE 22.04.5.

@lukefromdc
Copy link
Member

Again that's MATE 1.26 with very limited wayland support. Current version is 1.28 and we don't have the resources to backport all the 1.28 wayland work to 1.26 and then chase down any resulting issues. If you can locally build and install mate-desktop 1.28 and then caja 1.28 you will get native wayland support, this problem should be gone (I've never seen it and it's probably xWayland only), and you can even have icons on the desktop again.

For some reason Ubuntu has chosen not to pick up 1.28 even for their newest development release.

@sekelsta
Copy link

It's strange because this never used to happen before. It started maybe a couple weeks or a month ago.

@lukefromdc
Copy link
Member

lukefromdc commented Dec 24, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants