Page 1 of 4 123 ... LastLast
Results 1 to 10 of 35

Thread: Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-2021

  1. #1
    Join Date
    Nov 2009
    Location
    Bucharest, Romania
    Posts
    91

    Default Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-2021

    HI,
    after this morning updates that the applet suggested, I found out that suddenly I can't "Save As.." for any files on any web page, or even simple/general Save (CTRL-S) on any web page using my default browser, Chrome (version 96.0.4664.110 - must be the latest available); the exact same thing happened in Chromium; and even in Opera.
    Only Firefox continued to work OK.

    To be a little more specific, the dialog window where I needed to chose the file name to be saved, and the location, appears for a fraction of a second, and disappears. And nothing is saved.
    Turning ON or OFF options like "Use hardware acceleration when available" did not influence anything.

    After a lot of cursing, eventually I found the culprit(s): packages xorg-x11-server-1.20.3-22.5.42.1 , xorg-x11-server-extra and xorg-x11-wayland (same versions); probably the first is the one with the main problem.
    Unfortunately, trying to switch to Plasma Wayland solved only partially the problem -- option to Save As worked, but other programs seem to stop working all together, for instance Spotify Desktop app refused to start under Wayland.

    So, I had to revert all 3 packages of xorg-x11-server to previous versions (that is version 1.20.3-22-5.39.1) and now things are back to normal behaviour.

    Am I, by any chance, solo in this behaviour ?
    Or, perhaps other people faces the same problem ?

    Maybe someone has a clue about what change in the xorg-x11-server packages triggered this abnormal behaviour ?

    Thanks for any hint.

    P.S. For now I have to mark all those 3 packages with "Protect - do not modify" in Yast2, in order to keep them from trying again to upgrade.
    Just a Linux enthusiast, formatted as an OpenSuse user

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    30,509

    Default Re: Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-20

    When it is so clear that a problem is in the new, but not in the old version, you may wait for a few confirmations first, but IMHO in the end please file a bug report.
    Henk van Velden

  3. #3

    Default Re: Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-20

    I'm experiencing the same (Brave and Chrome). However, rolling back the xorg-x11-server packges one or even two versions makes no difference.

    System journal is showing following message when this occurs, but this isn't an area i've played with much. Won't have time to play around with this either unfortunately:

    Code:
    Dec xx xx:xx:xx xxxxxxxxx xdg-desktop-por[4394]: Backend call failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying

  4. #4
    Join Date
    Nov 2009
    Location
    Bucharest, Romania
    Posts
    91

    Red face Re: Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-20

    Quote Originally Posted by MrPendulum View Post
    I'm experiencing the same (Brave and Chrome). However, rolling back the xorg-x11-server packges one or even two versions makes no difference.

    System journal is showing following message when this occurs, but this isn't an area i've played with much. Won't have time to play around with this either unfortunately:

    Code:
    Dec xx xx:xx:xx xxxxxxxxx xdg-desktop-por[4394]: Backend call failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
    Sounds too bad that in your situation things are not back to normal after downgrading packages of xorg-x11-server mentioned above.
    I also had that error in my /var/log/messages file.
    Errr, at some point, after the downgrade of xorg-x11-server packages, I did also a remove of all xdg-desktop-* packages - so maybe that's why I don't have this error anymore

    Previous versions of the /var/log/messages file did not contain this error, so I assume it's safe to assume it was "introduced" with that update.

    Aside from this, now, when trying to upload file from local computer to some website, the chose file dialog is back at "old" style, which is a side effect very welcomed to me, because previously I had to navigate always to my preferred folder and pick up files. Could this be a side-effect of removing those xdg-desktop-* packages ? If so, I'm really very happy with this outcome.

    Sorry, since this computer is used at work, I'm not very keen to investigate if a new upgrade of xorg-x11-server packages (without xdg-desktop-* packages) will trigger again that behaviour related to Save As, or upload/chose file. At least not in the immediate future.
    Just a Linux enthusiast, formatted as an OpenSuse user

  5. #5

    Default Re: Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-20

    Same error with Vivaldi browser v. 5.0.2497.32.

  6. #6
    Join Date
    Jan 2009
    Location
    San Jose, CA, USA
    Posts
    29

    Default Re: Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-20

    Quote Originally Posted by corneld View Post
    I did also a remove of all xdg-desktop-* packages - so maybe that's why I don't have this error anymore
    Thanks for your tip! To get google-chrome-stable and chromium to display the file chooser dialogs under i3wm, I only had to explicitly remove the xdg-desktop-portal-gtk and -lang packages.

    This affected me because I only recently switched from KDE to i3wm for window management.
    Last edited by chestnet; 27-Dec-2021 at 00:13. Reason: Update to use correct terminology.

  7. #7
    Join Date
    Nov 2009
    Location
    Bucharest, Romania
    Posts
    91

    Default Re: Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-20

    HI,
    after this morning updates of systemd-* packages (from older version (246.16-7.21.1 to newer 246.16-7.28.1), and udev, libudev1 (exact same version numbers as in systemd), and some other extra packages (snapd was one of them, but can;t imagine what influence could snapd have over this issue), things got again into the same status as in my initial post.
    I did even found installed again xdg-desktop-* packages, and can't figure out now who triggered them into install.

    Sadly, this time a downgrade of systemd* and udev* to previous versions did not help.
    So now I am into constant frustration with crippled Chrome and all other Chromium browsers !! Only Firefox still work OK at this aspect (save as window, and upload window); but even this could not convince me to go back to using Firefox - it's too much of a mess otherwise (memory consumption, among the most important).

    Thus now I have all packages (xorg-x11-*, systemd* and udev*) updated to their latest available versions from the repositories (Main repository, Update repository, whichever each package is extracted from). And Chrome not functioning.

    The only constant is that system log *always* have these lines every time I try an "Save" option in Chrome (or in Chromium, or in Opera):
    27/12/2021 13:08 user@1000.service Backend call failed: GDBus.Errorrg.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
    27/12/2021 13:08 kwin_x11 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 18434, resource id: 136314883, major code: 15 (QueryTree), minor code: 0
    27/12/2021 13:08 kwin_x11 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 18439, resource id: 136314883, major code: 18 (ChangeProperty), minor code: 0

    These 3 lines appear invariably at each Save (ctrl-s) action I try.

    Ah, maybe it's worth to also mention that when I remove xdgb-desktop* packages, not even this happens, there is no dialog at all (not even that very-very short one); after I install them back, it stabilises on this abnormal behaviour.

    So, probably xdg-desktop have something to do with the bug, but it's hard to isolate the problem only to them.

    Frankly, I wouldn't know now where should I open a bug report !
    To xorg-x11-server ?
    To systemd + udev ?
    To xdg-* ?

    P.S. At least "Print" option works (dialog to print opens normally)
    Just a Linux enthusiast, formatted as an OpenSuse user

  8. #8
    Join Date
    Nov 2009
    Location
    Bucharest, Romania
    Posts
    91

    Default Re: Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-20

    I think it may be a bit more clear if I extend a bit the warnings/error in the system journal on every Save action I try in the browser:

    Dec 27 19:45:49 cornel systemd[1]: Started Hostname Service.
    Dec 27 19:45:49 cornel dbus-daemon[977]: [system] Successfully activated service 'org.freedesktop.hostname1'
    Dec 27 19:45:48 cornel kwin_x11[30386]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50933, resource id: 163577859, major code: 18 (Ch>
    Dec 27 19:45:48 cornel kwin_x11[30386]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50928, resource id: 163577859, major code: 15 (Qu>
    Dec 27 19:45:48 cornel xdg-desktop-por[3877]: Backend call failed: GDBus.Errorrg.freedesktop.DBus.Error.NoReply: Message recipient disconnected from me>
    Dec 27 19:45:48 cornel systemd[1628]: xdg-desktop-portal-gtk.service: Succeeded.
    Dec 27 19:45:48 cornel systemd[1]: Starting Hostname Service...
    [for what is worth, the above were thrown when trying to Save in Opera]


    And the following were thrown when tried the same in Chrome (the one I'm using even now when writing this):
    Dec 27 19:47:15 cornel systemd[1]: Started Hostname Service.
    Dec 27 19:47:15 cornel dbus-daemon[977]: [system] Successfully activated service 'org.freedesktop.hostname1'
    Dec 27 19:47:14 cornel kwin_x11[30386]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 53988, resource id: 163577859, major code: 18 (Ch>
    Dec 27 19:47:14 cornel kwin_x11[30386]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 53983, resource id: 163577859, major code: 15 (Qu>
    Dec 27 19:47:14 cornel xdg-desktop-por[3877]: Backend call failed: GDBus.Errorrg.freedesktop.DBus.Error.NoReply: Message recipient disconnected from me>
    Dec 27 19:47:14 cornel systemd[1628]: xdg-desktop-portal-gtk.service: Succeeded.
    Dec 27 19:47:14 cornel systemd[1]: Starting Hostname Service...

    Just a Linux enthusiast, formatted as an OpenSuse user

  9. #9

    Default Re: Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-20

    Bug 1194102 filed.

  10. #10
    Join Date
    Nov 2009
    Location
    Bucharest, Romania
    Posts
    91

    Default Re: Save As options in Chrome/Chromium based browsers not working after X-ORG-X11 update on 22-12-20

    Maybe this could help with anything ?
    I did try to login with any graphic interface I could find available: Gnome, Gnome on XOrg, ICeWM, Enlightment -- in all of these I see the exacgt same behaviour when trying to save, or open file.

    Trying also to login into Plasma Wayland, seems to work OK (as I already mentioned in my first post.)
    Also in Plasma Full Wayland.

    Sadly, in Plasma Wayland I have this other problem with Spotify Desktop app (installed via snap, with internal snap command, like snap install spotify);
    I have this error:
    [1228/181108.071851:FATAL:gpu_data_manager_impl_private.cc(417)] GPU process isn't usable. Goodbye.
    Trace/breakpoint trap (core dumped)

    Interestingly enough, in Plasma Full Wayland even Spotify app does start OK (it gives some worning about not finding something of GPU, which may have it's roots, since the video card is a pretty low level Intel HD Graphics 2000 "card" inside.

    I'd prefer, though, to use plain Plasma further, and thus this bug identified and solved.
    Just a Linux enthusiast, formatted as an OpenSuse user

Page 1 of 4 123 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •