Bug 1916525 - is Fedora causing Firefox, gedit, & LibreOffice to lose bottom bar?
Summary: is Fedora causing Firefox, gedit, & LibreOffice to lose bottom bar?
Alias: None
Product: Fedora
Classification: Fedora
Component: general-purpose-preprocessor
Version: 33
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Zbigniew Jędrzejewski-Szmek
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-01-15 01:16 UTC by Nick Levinson
Modified: 2021-05-16 07:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-01-16 10:45:31 UTC
Type: Bug

Attachments (Terms of Use)

Description Nick Levinson 2021-01-15 01:16:36 UTC
Description of problem:
After using these apps for a while, Firefox may hide the Find bar, gedit may hide the statusbar, and LibreOffice Writermay  hide the status bar. Commenter suggests problem may be with distro, not apps.

Version-Release number of selected component (if applicable):

How reproducible:
Often but not always.

Steps to Reproduce:
1. Run F33 with Gnome 3.38.2.
2. Try one or more of the following apps:
2a. For Firefox, open it and a Web page, maximize the window if not already the default, issue ctrl-f to get the Find bar, and use it a while.
2b. For gedit, open it and a document, ensure Preferences has the statusbar on, maximize the window if not already the default, and use it a while.
2c. For LibreOffice Writer, open it and a document, ensure View menu > Status Bar is on, maximize the window if not already the default, and use it a while.

Actual results:

Sometimes, after a while of usage, the Find bar, statusbar, or status bar is no longer visible. Clicking the maximize/restore button once or twice makes it visible again.

The bar appears to reappear from behind the Gnome desktop environment's bottom panel, suggesting that the window had, at some moment, enlarged from maximum based on the presence of the panel to a larger size as if the panel didn't exist, although the panel remains in front.

Expected results:
The bar should stay visible, unless the user dismisses the Find bar or changes the preference.

Additional info:

Three apps in the distro have highly similar misbehaviors. I reported them as bugs in the bug trackers for the three apps. Because of the similarity, I suggested that one upstream source of code may be the problem. One commenter responded on all three threads that the problem is not with the apps but that I should report it to the distro. Unless the kernel is at fault, I doubt the distro is at fault, but in case he's right, I'm reporting the three apps' similar bugs here.

I do not know if other apps have the problem. I have not noticed it, but I don't use many other apps often enough and long enough to know.

The Fedora component is unknown.

The app bug reports:
Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1686364
gedit: https://gitlab.gnome.org/GNOME/gedit/-/issues/399
LibreOffice Writer: https://bugs.documentfoundation.org/show_bug.cgi?id=139572

Comment 1 Andre Klapper 2021-01-15 07:50:16 UTC
Nick, I asked you in all the other reports that you filed in random places to bring this up in a support forum of your distro. Why did you instead decide to create a fourth ticket about this in yet another issue tracker?

Comment 2 Nick Levinson 2021-01-15 23:36:13 UTC
I reported it in the bug tracker of my distro, which is this bug tracker. Fedora bugs are reported to Red Hat. When you have a few minutes, please look at bugzilla.redhat.com . It covers Red Hat and Fedora, which are closely related distros. In all three of my app bug reports, I said I was using Fedora. I assume you already knew that but you didn't realize that Red Hat and Fedora share the bug tracker.

I use support fora, too, but generally not to report bugs. Bug reporting is in bug reporting systems. If a Fedora component is causing a problem with all three apps, it’s more likely that someone on the bug reporting system will know which component it is than that someone on a support forum will know. Once it's clear that the issue is not a failure to use the app properly but a problem a user is not expected to solve, the issue becomes either a bug or a feature request and goes to the place suited to bugs or feature requests, respectively. Since support requests are not automatically exposed to a bug/feature website even by clicking something, once it's clear that these were bugs the proper place for each was a bug tracker, not a support forum as an extra step that takes up other people's time.

No, not "random". The problems occurred in precisely the apps I reported. I gave the information to show that that is where each problem occurred. You don't disagree. Your accusation is therefore erroneous.

No, not "lots". Three. If three is a lot, it's three because the problems occurred in three. Had I found it in only one, I would have reported it in just one. Had I found it in five, I should have reported it in five. If I had found it in five but not reported it in all five, any organization I did not report it to would probably not have known that their product had the problem, too, and it likely would have remained for nonreporters to experience, lowering the quality of their Linux experience. That's not good for FOSS.

An exception to multiple reporting is if we know a single cause that can be reported in a single place. That is why I raised the possibility of upstream sourcing. You raised the possibility of downstream sourcing and I acted accordingly. Apparently, neither of us knows the source of the problem and perhaps we'll learn that from someone else on one of these threads.

I use Gimp and have not seen the problem there but I use it only rarely and its user interface is different enough that it might not be relevant.

I have an Ubuntu platform but don't use it enough to determine if any or all three of the problems also occur there or if any other apps also have the problem.

Comment 3 Andre Klapper 2021-01-16 07:58:10 UTC
Let me repeat my (so far unanswered) question and stress some words: I asked you in all the other reports to bring this up in a **SUPPORT FORUM** of your distro. Why did you instead decide to create a fourth ticket in yet another **ISSUE TRACKER**? This isn't a good use of anyone's time, really. :-(

Comment 4 Zbigniew Jędrzejewski-Szmek 2021-01-16 10:45:31 UTC
Yep, there doesn't seem to have more than one bug open. Let's close this one.

Comment 5 Nick Levinson 2021-01-19 04:03:12 UTC
On comment 3 (@Andre Klapper):

Reminder: You said to report to either a "forum" or "an issue tracker of your distribution" (https://bugs.documentfoundation.org/show_bug.cgi?id=139572#c2) and said also "an issue tracker of your distribution" (https://bugzilla.mozilla.org/show_bug.cgi?id=1686364#c3). You were free to change your mind later (as you did at https://bugzilla.redhat.com/show_bug.cgi?id=1916525#c3), but stop blaming me for taking what was your acceptable advice, since Fedora could possibly have been at fault if there's a downstream issue.

I've raised a question about this issue at https://ask.fedoraproject.org/t/bring-bugs-here-before-bugzilla/11693 . Feel free to coomment.

Your question was answered in comment 2, above, especially in the first two paragraphs. If it wasn't clear, tell me what to clarify.

The Fedora organization further supports the division of tasks: They say (https://fedoraproject.org/wiki/Communicating_and_getting_help#Providing_Feedback_to_Developers), "If you believe you have found a bug or would like to suggest enhancements, use the Bugzilla . . . bug tracking system." They add (https://fedoraproject.org/wiki/Bugs_and_feature_requests#Do_I_need_to_file_a_bug.3F), "Unless you see a problem already reported in Bugzilla . . . [or other exceptions apply], you should file a bug. Don't assume that everyone else is also seeing the same problem you are; many bugs are specific to a particular hardware, configuration, or habits of use. Discussing a bug on IRC or the fedora-test-list mailing list can help you diagnose the exact source and co-ordinate with others experiencing the same issue, but it is not a sufficient way to report the bug. It must be reported to Bugzilla so the issue can be properly tracked and will not be lost among the noise of the mailing list."/"A common practice is to file a bug first, then e-mail the list with a link to the bug report, asking for further assistance. Many bugs are also filed with no e-mail to the mailing list, so be sure to search Bugzilla for your problem." I searched before filing any of the bug reports and I did not find any similar report. I think most reporters do not use IRC or a mailing list. Therefore, my reporting the bug when I did was right.

At least you seem to have stopped your other erroneous accusations. You could say so explicitly.

On comment 4 (@Zbigniew Jędrzejewski-Szmek): I don't understand "there doesn't seem to have more than one bug open." Three were opened. One was closed because of a request that I bring it elsewhere, and I brought it here to find whatever may be in common across all three; that leaves two that are open and the third hasn't been fixed and, given another commenter's response, likely should be reopened. The URLs of all three are given in the description (the opening post) above. The commenter wanted it brought to a support forum but support fora are not for bug reporting or bug cause analysis other than user misuse and no one is claiming user misuse or misunderstanding of use. But if you're saying that there's no need for this report because others are open and therefore that there isn't a common factor shared by the three that is a Fedora downstream issue, please give us your analysis, because that would help clarify where the problem lies, either in the three apps or upstream from them.

Comment 6 Andre Klapper 2021-01-19 07:50:38 UTC
> I've raised a question about this issue at https://ask.fedoraproject.org/t/bring-bugs-here-before-bugzilla/11693 . Feel free to coomment.

Thanks a lot.

Comment 7 Nick Levinson 2021-01-30 00:49:54 UTC
For a plausible explanation pending possible repair, see https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/285 .

Comment 8 Nick Levinson 2021-05-16 07:00:08 UTC
Resolved with a fix in Gnome 40. Probably relevant: https://gitlab.gnome.org/GNOME/mutter/-/issues/1627 .

Note You need to log in before you can comment on or make changes to this bug.