On 2025-09-24 14:18, phil(a)pricom.com.au wrote:
> bdju,
>
>
> On 2025-09-24 14:02, Philip Rhoades via Sway wrote:
>> bdju,
>>
>>
>> On 2025-09-23 23:22, bdju wrote:
>>> On Tue Sep 23, 2025 at 6:57 AM CDT, Philip Rhoades via Sway wrote:
>>>> People,
>>>>
>>>> At first I thought this problem was specific to Brave (my work-horse
>>>> browser) but then I found the problem was the same for Chrome and FF
>>>> . .
>>>>
>>>> BTW, I tried a LOT of different extensions so it is common to all of
>>>> the
>>>> browsers and extensions . .
>>>>
>>>> Any ideas what is going on? - otherwise the clean install of F43 on
>>>> three desktops and one laptop have gone pretty well . . but it was
>>>> other
>>>> issues that prompted a major re-organisation and house cleaning of
>>>> all
>>>> the stuff on all the machines so it is quite possible I have stuffed
>>>> something up . .
>>>>
>>>> Thanks,
>>>>
>>>> Phil.
>>>
>>>
>>> Hey Phil,
>>>
>>> Just some things that come to mind here in case they help figure this
>>> out. Are all browsers using a GTK file picker?
>>
>>
>> I presume so - how would I check? -strace or something?
>>
>>
>>> Could that be something
>>> in common?
>>
>>
>> Maybe . .
>>
>>
>>> Also, do you notice the same issue when uploading a file to
>>> an image host
>>
>>
>> What do you mean "image host" - where you upload images? not VM
>> images?
>>
>>
>>> and/or saving a file with "save as"?
>>
>>
>> That works on FF at least.
>>
>>
>>> Another train of thought, are any/all of these browsers installed via
>>> Flatpak?
>>
>>
>> No, I avoid flatpak unless I really can't get the app rpm installed
>> and I really need it . .
>>
>>
>>> Perhaps it's an issue with xdg-desktop-portal-wlr or similar if
>>> so. Also, can you verify if these browsers are running natively with
>>> Wayland or if they're using XWayland? You can check by doing:
>>> swaymsg -t get_tree | less
>>>
>>> Then search for the relevant program and check if it uses a "class"
>>> or
>>> an "app_id".
>>
>>
>> "xwayland" is mentioned twice in that output and:
>>
>> "app_id": "google-chrome",
>> "app_id": "chrome-hbajjpcdbninabigakflkhiogmmjaakm-Default",
>> "app_id": "google-chrome",
>> "class": "org.mozilla.firefox",
>> "class": "org.mozilla.firefox",
>> "app_id": "brave-hbajjpcdbninabigakflkhiogmmjaakm-Default",
>> "app_id": "brave-browser",
>> "app_id": "brave-browser",
>>
>> It was brave that I first discovered the problem, then chrome and then
>> FF if I remember correctly . .
>>
>>
>>> XWayland uses "class" while Wayland uses "app_id". I would
>>> then see if everything with the problem is using native Wayland if it
>>> still happens when running one in XWayland (or perhaps another
>>> compositor/WM entirely).
>>
>>
>> Hmm . . well it was def happening with Brave and Chrome - I will check
>> FF again . .
>
>
> Ah! - I reinstalled the first FF chat add-on I found and exporting did
> actually work! - so it looks like it may be an XWayland issue?
I also found that I can't export setups from other extensions like
TabFern . .
However, after continuing to search for stuff and following your hints,
I thought if I tried to run Brave natively in Wayland that that might
fix the problem so I added this:
--ozone-platform=wayland
to my CLI startup . . unfortunately it didn't fix the problem . . dammit
. . I make VERY heavy use of TabFern but it is not available for FF . .
Phil.