Description of problem: If nextcloud-client-nautilus is installed, renaming a file causes nautilus to become unresponsive once the file rename pop-up is rendered. It somehow steals mouse and keyboard focus too so I cannot just click to another window. Requires a pkill -9 from a virtual TTY to regain control. Version-Release number of selected component (if applicable): nautilus-43.0-2.fc37.x86_64 nextcloud-client-nautilus-3.6.0-1.fc37.x86_64 How reproducible: Always Steps to Reproduce: 1. Install nextcloud-client-nautilus 2. Run nautilus from the terminal so we can observe its stderr 3. Try renaming a file in Nautilus (even in a folder not managed by Nextcloud) Actual results: - nautilus becomes unresponsive once the pop-up to type in the new filename is rendered - clicking to other windows don't work - after 'pkill -9 nautilus' everything is back working again. -9 is required ❯ nautilus Initializing Nextcloud-client-nautilus extension Using python version sys.version_info(major=3, minor=11, micro=0, releaselevel='candidate', serial=2) TypeError: MenuExtension_ownCloud.get_file_items() missing 1 required positional argument: 'files' TypeError: MenuExtension_ownCloud.get_file_items() missing 1 required positional argument: 'files' TypeError: MenuExtension_ownCloud.get_file_items() missing 1 required positional argument: 'files' TypeError: MenuExtension_ownCloud.get_file_items() missing 1 required positional argument: 'files' Expected results: No issue Additional info:
Proposed as a Blocker for 37-final by Fedora user salimma using the blocker tracking app because: While this bug is triggered by a package that's not part of the default install (nextcloud-client-nautilus), it's a bit worrying to me that a Nautilus extension can cause Nautilus to lock up so badly - and worse, take away keyboard and mouse focus. A technical user can work around this, but for a non-technical user this seems like it would be a horrible experience. Not sure if it's blocker-worthy (or if I should split off the underlying Nautilus issue to a separate bug). Probably worth at least a 'known issue' entry though.
Adding an explicit freeze exception nomination because I don't think this is likely to be granted blocker status.
https://github.com/nextcloud/desktop/pull/5001 has patches for nautilus 43 support.
-5 blocker +5 freeze exception vote in https://pagure.io/fedora-qa/blocker-review/issue/947 , rejecting as a blocker and accepting as a freeze exception
I will add the patch from upstream PR in the next few days.
FEDORA-2022-ca34507271 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ca34507271
please test the above update and provide feedback.
FEDORA-2022-ca34507271 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-ca34507271` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ca34507271 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I don't have a Nextcloud account,but without the update,I see the TypeError mentioned in the description,while the Error will be gone after the update is installed.So,I guess we can call the bug is fixed?
> I don't have a Nextcloud account And I saw this bug when I try to create one: https://bugzilla.redhat.com/show_bug.cgi?id=2134035
Michel, can you please test the update and provide karma in Bodhi? Thanks!
FEDORA-2022-ca34507271 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.