Closed Bug 1713175 Opened 3 years ago Closed 2 years ago

[Wayland] Gtk Dialog does not accepts text copied from external applications.

Categories

(Core :: Widget: Gtk, defect, P2)

78 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mwizard, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

I have a web page open in a tab.
I initiate the print request (CTL-P or perhaps the print button).
I select the Save as PDF printer.
I click save.
The dialog with a default file name is displayed.
I try to paste text from an external application into the file name area.

Actual results:

The clipboard text does not replace the text in the dialog

Expected results:

I expected the text from the clipboard to add or replace the text in the file name box.

The Bugbug bot thinks this bug should belong to the 'Core::Printing: Setup' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Printing: Setup
Product: Firefox → Core

This happened a year ago too and the bug was fixed: Bug 1635718
It worked fine since that time.
It has come back again, almost like the fix was backed out.

I can paste into the field on my Ubuntu 20.04 box.

MarkV, thanks for reporting this bug. If you are able to reproduce this issue reliably, can you please try to use mozregression to find out which commit regressed this? Thanks!

Flags: needinfo?(mwizard)

[mark@mark-fedora Downloads]$ mozregression-gui/mozregression-gui
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
GLib-GIO-Message: 13:39:33.710: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.

(mozregression-gui:27171): GLib-GIO-ERROR **: 13:39:33.711: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
Trace/breakpoint trap (core dumped)

I'm not sure what to do next. Any ideas?

Flags: needinfo?(mwizard)

MarkV, sorry to see mozregression didn't work for you. I don't know much about it but looks like it's an issue with the graphical interface, so if you're able to try running the command-line version of the tool (see the second option at https://mozilla.github.io/mozregression/install.html#mozregression), this might bypass that problem and allow you to identify the regression.

Flags: needinfo?(mwizard)

I was able to get the Python version working. I tried the narrow 5-1 thru 5-17 dates, but they were all good. Then I tried stretching the dates out to eventually 1-1 thru 6-21. The problem did not show up anywhere. All dates were good. I find this a little puzzling.

I can confirm that my locally installed FF 89 does indeed still exhibit the problem. I disabled all extensions again and confirmed the problem persists.

Is it possible that the problem resides only on the Fedora Repositories, but not outside of Fedora?

Any test you want to try next?

Flags: needinfo?(mwizard)

Hmm - is your "locally installed FF 89" a version packaged by Fedora and installed via their package manager? If so, it'd be interesting to try downloading a standard Mozilla build from https://www.mozilla.org/en-US/firefox/all/#product-desktop-release and see if that behaves the same.

It is a locally installed FF89 through Fedora 34 Workstation Edition, 64bit, Gnome 40.1.0, using Wayland. This is the basic FC34 system.

I try hard not to install software not from the Fedora package installer. As a result, I don't have much experience with doing those kinds of installs. How would you recommend that I perform the install so that I might keep the existing FF89 and run them parallel? And then how would I go about uninstalling that extra package when we are done? I'll do some internet searches to see what others have done.

Should I uninstall the FF89 from my system before installing the non fedora package version? I would like to keep all my settings intact if I can.

I'm game to try, but I just want to be comfortable about how to go about doing this safely and keep my settings if possible.

I installed the stand alone version along side my package version. It does not have the same problem my package version has. I've even used the same profile in both tests.

I suppose worst case, I can uninstall the package version and use the non package version.

If I do that, then I'm going to be interested in how this updates. I know how Windows handles it's updates. Does the non package version on Linux perform its updates the same way?

I certainly appreciate all your help on this.

Thanks for trying this. It seems, then, that the problem is somehow related to how Fedora is packaging the program; perhaps the best thing to do would be to report this as an issue in the Fedora bug tracker (see https://fedoraproject.org/wiki/Bugzilla), as it's outside of our control.

(Regarding updates, I believe the default behavior will be to automatically update to new versions when they are released by Mozilla; there should be a "Firefox Updates" section in about:preferences where you can confirm/alter this setting.)

CCing some RedHat folks, they might be able to reproduce this issue.

I have opened a bug with the Fedora bugzilla. It references this bug should they want to read more about what we've done here.

Red Hat Bugzilla – Bug 1977052

This affects any dialog provided by Gtk - File dialog, Print dialog etc.

Blocks: wayland
Priority: -- → P2
Summary: Print to File Dialog does not accepts text copied from external applications. → [Wayland] Gtk Dialog does not accepts text copied from external applications.
Component: Printing: Setup → Widget: Gtk

Can you try latest nightly with async clipboard enabled (https://bugzilla.mozilla.org/show_bug.cgi?id=1725149#c5)?
Thanks.

Flags: needinfo?(mwizard)

I will download that and let you know.

The nightly build does indeed solve the problem. I can now paste text from applications outside of FF into the file name text box of the save as pdf option.

Thanks very much.

Are we thinking I'll have to wait until Fedora deploys the 93 release, or do you have plans to move it to an earlier release?

Flags: needinfo?(mwizard)

Closing as reported as fixed in comment 16

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.