Bug 1194102

Addition: same problem with "Open file" Ctrl+O dialogue: https://forums.opensuse.org/showthread.php/564433-Using-i3wm-with-google-chrome-and-chromium-shows-quickly-disappearing-File-Open-and-Save-As-dialogs

ILL temporary solution is in deleting xdg-desktop-portal-gtk package: https://forums.opensuse.org/showthread.php/564433-Using-i3wm-with-google-chrome-and-chromium-shows-quickly-disappearing-File-Open-and-Save-As-dialogs?p=3094372#post3094372

Opening html files via Dolphin works OK.

I'm experiencing the same attempting to retrieve files from my computer with the open file dialog on Google Drive and CPanel.

For some reason in Plasma Wayland and Plasma Full Wayland this bug does not manifest itself.

All other graphic interfaces that I tried (IceWM, Enlightnment, Gnome and Gnome on Xorg) do have this bug.

15.2 is also affected.


Looking at the zypp history this update may have caused the problem 

2021-12-24 08:52:35|install|xdg-desktop-portal-gtk|1.8.0-lp152.2.6.1|x86_64||repo-update|b8df460884262d7c40ccf5f6b2390812b805bf3f47580642b57530e93affaf34|

2021-12-24 08:52:35|install|xdg-desktop-portal-gtk-lang|1.8.0-lp152.2.6.1|noarch||repo-update|1e7e6c7b0c5a7974a97c6d21d34ff25ca94e8291f103c30e25acd4698d4301be|


reverted back to:

2021-12-28 19:47:08|install|xdg-desktop-portal-gtk|1.8.0-lp152.2.3.1|x86_64|root@snowpa.invalid|repo-update|92e85b6c5b866aa54792f85ddc4f11831c1c4c4178fe88aeb15d002997cb4f7c|
2021-12-28 19:47:09|install|xdg-desktop-portal-gtk-lang|1.8.0-lp152.2.6.1|noarch||repo-update|1e7e6c7b0c5a7974a97c6d21d34ff25ca94e8291f103c30e25acd4698d4301be|


and restarted -- all works. 

again - this is with 15.2 but am pretty confident that reverting to the previous version on 15,3 works too.

*** Bug 1194121 has been marked as a duplicate of this bug. ***

Vasilis, this regression was reported against your L3 update for bug 1179465

> - Fix xdg-desktop-portal-gtk process hanging the logout. Make the process exit 
>   after one second unless it has active sessions (bsc#1179465)

Assigning to you.

*** Bug 1194095 has been marked as a duplicate of this bug. ***

Offending patch/update:

https://build.opensuse.org/package/view_file/openSUSE:Leap:15.2:Update/xdg-desktop-portal-gtk.17299/xdg-desktop-portal-gtk-idle-timeout.patch?expand=1
https://build.opensuse.org/package/rdiff/openSUSE:Maintenance:17299/xdg-desktop-portal-gtk.openSUSE_Leap_15.2_Update?linkrev=base&rev=2

(In reply to Roeland Jansen from comment #4)
> 15.2 is also affected.
> 
> Looking at the zypp history this update may have caused the problem 
> 
> 2021-12-24
> 08:52:35|install|xdg-desktop-portal-gtk|1.8.0-lp152.2.6.1|x86_64||repo-
> update|b8df460884262d7c40ccf5f6b2390812b805bf3f47580642b57530e93affaf34|
> 
> 2021-12-24
> 08:52:35|install|xdg-desktop-portal-gtk-lang|1.8.0-lp152.2.6.1|noarch||repo-
> update|1e7e6c7b0c5a7974a97c6d21d34ff25ca94e8291f103c30e25acd4698d4301be|
> 
> reverted back to:
> 
> 2021-12-28
> 19:47:08|install|xdg-desktop-portal-gtk|1.8.0-lp152.2.3.1|x86_64|root@snowpa.
> invalid|repo-
> update|92e85b6c5b866aa54792f85ddc4f11831c1c4c4178fe88aeb15d002997cb4f7c|
> 2021-12-28
> 19:47:09|install|xdg-desktop-portal-gtk-lang|1.8.0-lp152.2.6.1|noarch||repo-
> update|1e7e6c7b0c5a7974a97c6d21d34ff25ca94e8291f103c30e25acd4698d4301be|
> 
> and restarted -- all works. 
> 
> again - this is with 15.2 but am pretty confident that reverting to the
> previous version on 15,3 works too.

I confirm for Leap 15.3: downgrading packages xdg-desktop-portal-gtk and xdg-desktop-portal-gtk-lang from v. 1.8.0-3.6.1 to 1.8.0-3.3.1 solves this issue.

*** Bug 1194236 has been marked as a duplicate of this bug. ***

(In reply to Roeland Jansen from comment #4)
> 15.2 is also affected.
> 
> reverted back to:
> 
> xdg-desktop-portal-gtk         1.8.0-lp152.2.3.1
> xdg-desktop-portal-gtk-lang    1.8.0-lp152.2.6.1
> 
> and restarted -- all works. 

I can confirm this "fix" as well, and a restart wasn't even needed.

I can confirm that this workaround works for me in Leap 15.3 (upgraded just yesterday). Thanks.

*** Bug 1194101 has been marked as a duplicate of this bug. ***

Taking this bug, as I wrote the bad patch. I'm currently testing an updated patch.

Is only 15.2 and 15.3 affected?

Repos with tentative fix are here:

home:hpjansson:branches:SUSE:SLE-15-SP2:Update/xdg-desktop-portal-gtk (Leap 15.3)
home:hpjansson:branches:openSUSE:Leap:15.2:Update/xdg-desktop-portal-gtk

Looks like identical sources, so probably interchangeable.

(In reply to Hans Petter Jansson from comment #15)
> home:hpjansson:branches:SUSE:SLE-15-SP2:Update/xdg-desktop-portal-gtk (Leap
> 15.3)

Thanks! Tested my use case from bug 1194101, no issue encountered.

Downgrading xdg-desktop-portal-gtk to  xdg-desktop-portal-gtk-1.8.0-3.3.1.x86_64 helps for the moment.

See Discussion on 

https://support.google.com/chrome/thread/143041953/cant-open-save-or-do-anything-related-with-the-file-open-save-dialog?hl=en

and 

https://support.google.com/chrome/thread/143041953/cant-open-save-or-do-anything-related-with-the-file-open-save-dialog?hl=en 

linked therein.

Thanks a lot for testing, Martin. I've submitted the update.

SUSE-RU-2022:0098-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1194102
CVE References: 
JIRA References: 
Sources used:
SUSE Manager Server 4.1 (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1
SUSE Manager Retail Branch Server 4.1 (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1
SUSE Manager Proxy 4.1 (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1
SUSE Linux Enterprise Server for SAP 15-SP2 (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1
SUSE Linux Enterprise Server 15-SP2-LTSS (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1
SUSE Linux Enterprise Server 15-SP2-BCL (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1
SUSE Linux Enterprise Module for Desktop Applications 15-SP3 (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1
SUSE Linux Enterprise High Performance Computing 15-SP2-LTSS (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1
SUSE Linux Enterprise High Performance Computing 15-SP2-ESPOS (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1
SUSE Enterprise Storage 7 (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1
SUSE CaaS Platform 4.5 (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

openSUSE-RU-2022:0098-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1194102
CVE References: 
JIRA References: 
Sources used:
openSUSE Leap 15.3 (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1

I've just installed latest patches on 15.3 and I can confirm the fix works. No need to restart browsers.

Thanks!!

Yes, after installing xdg-desktop-portal version 1.8.0-3.9.1 in my Opensuse 15.3, the bug no longer manifests, so I also confirm it's fixed.
Thanks.

I confirm: 1.8.0-3.9.1 works after in opensuse 15.3


Thank you!

as 15.2 was flagged as a duplicate --

is there an update for 15.2 too? 

(Maybe I've overlooked it or the duplicate bug dismissal may left 15.2 in the dark?)

(In reply to Roeland Jansen from comment #30)
> is there an update for 15.2 too? 

No, 15.2 is EOL.
https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/DKIXTCVYQEKZ2ANWGLWL5Q77ZMIOTQJ2/

1.8.0-3.9.1 works in openSUSE 15.3 for me. Thanks!

I also confirm 1.8.0-3.9.1 working for 15.3, and rolled it out to the machines in our business.
However, on my own computer I removed all xdg-desktop-portal packages, and chromium works even better.
Finally, it shows the native KDialog for KDE/Plasma again, that disappeared some time ago mysteriously.

15.2 being EOL -- fair enough. However the ackage was broken within the window of support.

Now,you get every day the broken package so I'd suggest either fix it or take away the broken updates. We don't want to become a different well known company that releases broken stuff and keep that forever?

(In reply to Roeland Jansen from comment #35)
> 15.2 being EOL -- fair enough. However the ackage was broken within the
> window of support.
> 
> Now,you get every day the broken package so I'd suggest either fix it or
> take away the broken updates. We don't want to become a different well known
> company that releases broken stuff and keep that forever?

Simply upgrade to 15.3: because it ain't broke forever. 

EOL will always be EOL

Affected Leap 15.2 users could add a libzypp lock to stick with xdg-desktop-portal-gtk-1.8.0-3.3.1.

I'm still wondering whether we can't simply remove the broken version from the update repo. It seems to cause more pain than good.

(In reply to Martin Wilck from comment #37)
> Affected Leap 15.2 users could add a libzypp lock to stick with
> xdg-desktop-portal-gtk-1.8.0-3.3.1.
> 
> I'm still wondering whether we can't simply remove the broken version from
> the update repo. It seems to cause more pain than good.

I fully agree. A lock does help in not installing the offending version, however, desktop users will have still te pop-up.

I would also argue to remove the package instead or fix.

The error was reported inside of the maintenance window and let's be honest; one commercial linux make that f*cks up stuff on a weekly basis is more than enough; "we" don't want to do that too I guess. One of the strenghts of SUSE and it's related products is that you almost blindly can install, reboot and such without issues (copared to that other one I am referring to; not being debian based)

Note for Leap 15.3 users: I had set a lock on xdg-desktop-portal-gtk:

# zypper ll 

# | Name                   | Type    | Repository | Comment
--+------------------------+---------+------------+--------
1 | xdg-desktop-portal-gtk | package | (any)      | 

This would cause errors during "zypper patch". zypper would offer the conflict resolution to remove the lock, but still not find the correct solution.

Only releasing the lock _before_ calling "zypper patch" would fix the issue.

Roeland what kind of guilt trip are you trying to pitch here? 15.2 is EOL and should have been migrated away from. There was plenty of notice, plenty of overlap time. The lifetime of 15.2 while 15.3 was for migration, not for hold-outs. For Chromium you are at least missing security fixes from Chromium 97.0.4692.99 (bug 1194919) If you are putting this particular thing over what distribution security and maintenance actually mean, I am not sure if you can be helped to be honest.

(In reply to Andreas Stieger from comment #40)
> Roeland what kind of guilt trip are you trying to pitch here? 15.2 is EOL
> and should have been migrated away from. There was plenty of notice, plenty
> of overlap time. The lifetime of 15.2 while 15.3 was for migration, not for
> hold-outs. For Chromium you are at least missing security fixes from
> Chromium 97.0.4692.99 (bug 1194919) If you are putting this particular thing
> over what distribution security and maintenance actually mean, I am not sure
> if you can be helped to be honest.

I have a car, has issues with the engine which is covered in the warranty period. 
So a week before that expires, I bring it to the dealer and two weeks after the expiry the dealer says: oh you are out of luck. Deal with it.

Above is exacly the same issue. Also, the update breaks something so fixing would have been better.

Now I know of a specific company that releases kernels thar are broken. They internally know and they just say "oh well" and they deal with the damage. (if you have a support contract that is).

So at the end, you just say : oh who cares. It's fine. 

It's not that nobody wants or needs to upgrade or whatever, it's just that the decision does not make any sense. It was IN the support window mentioned and a WONTFIX or not withdrawing, to me is something that belongs to that other company. "We" should not have this happen here. We/you are too good for that>

And - that's my personal opinion. No matter what reason there is for something running on 15.2 for this moment. 

All the systems I own were already updated before the end, it's just that releasing known broken issues within a timeframe of support/"warranty" should not happen and if it would, should imho be fixed outside of that window too. Especially if you KNOW this.

No need to react. Just think about the car and warranty.

This narrative is factually wrong. The update was not known to cause this, claiming otherwise or suggesting negligence is just stupid or worse. If you check comment #6, I traced back the regression to that change after it was released as an update.

Andreas, I don't quite agree.

"The update was not known to cause this" - of course not, QA didn't find the issue, otherwise the update wouldn't have been published. You traced the regression back to the update on Dec 28th. There was also bug 1194101, which I'd tracked down to this update on Dec 27th. That was only 5 days after the update had hit the repos, with holidays in between. In just a couple of days, the bug was reported 4 times.

Leap 15.2 EOL was officially on Jan 4th (https://en.opensuse.org/Lifetime). That's a week after we figured out that the xdg-desktop-portal-gtk update was broken. Even if no proper fix was available until 2 days later (comment 15), it would have been possible to remove the broken update from repositories before the EOL date was reached. I know maintenance can do that, even if I don't remember exactly how it works.

You're of course right when you say that users must update to 15.3 if they want to receive fixes. But we recommend that users install the latest 15.2 updates before they do the dup to 15.3. Thus it's not unlikely that users will stumble into this problem _while they are trying to update to 15.3_. It might happen if a user wants to use the Chromium browser to double-check some information on our wiki before she updates, and hits this issue. IMHO this would warrant an exception, at least by blocking or retracting the broken update package.

How exactly are the Chromium open/save file dialogs blocking the upgrade to 15.3?

(In reply to Andreas Stieger from comment #44)
> How exactly are the Chromium open/save file dialogs blocking the upgrade to
> 15.3?

I didn't say that. Just that people might run into this problem because / while they are updating. I won't argue any further. I just think that removing that broken update from the repos would probably have taken less time than this discussion here.

SUSE-RU-2022:0098-2: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1194102
CVE References: 
JIRA References: 
Sources used:
SUSE Linux Enterprise Realtime Extension 15-SP2 (src):    xdg-desktop-portal-gtk-1.8.0-3.9.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.