I simply put it to my home profile and that one fixed having back buttons and titlebar on the customize toolbar.

export MOZ_GTK_TITLEBAR_DECORATION=client

Also Archi Wiki have a page about many Firefox Tweaks.
https://wiki.archlinux.org/title/Talk:Firefox/Tweaks

I should have googled early about it, but have ignored it until today decide to check it up.
Also, as it was clearly seen, my issue was different from OP, which I apologize for putting my nose on his thread.

chimaera-updates only holds "point release to be" packages for chimaera

Yes and my point was that Debian have now released v11.2 of bullseye so there should be corresponding packages in https://pkgmaster.devuan.org/merged/dis … ates/main/ but it seems to be empty.

Compare the sizes of Packages.xz in Debian (2.5K) to Devuan (32 bytes: it is an empty file). That doesn't look right to me. But perhaps I'm missing something obvious, in which case my apologies for the noise.

@OP: sorry for the off-topic diversion.

Before firefox esr 91 I had to use

in order to have firefox usable to play videos and yes since esr 91 firefox was completly unusable. So I installed a fresh virtual machine with chimaera and chromium and the video playing was a way better than firefox on physical host (such a shame).

But this worked for me and firefox is usable again!

Worked for me.

BTW: There is no upload integrated in DG, right? So upload elsewhere and link hiere?

Ive not used fluxbox much before, i always found it cumbersome to edit and modify and has ugly ui.

Anything I can do solve the problem ?
Or is this even a problem? (the ff is, but I mean the "empty chimaera -updates")

Note that the pkgmaster:devuan/ directory tree comprises the forked packages only, and it is input to amprolla, for being used as "overlay" over Debian's package collection(s) into the Devuan distribution at http://deb.devuan.org/merged/, including the meta information at pkgmaster:merged/ which is amprolla's output.

I'm not totally on top of the intricacies with how the pkgmaster:devuan/ directory tree comes about and is managed; I believe it in general involves "someone" instructing "ci" to build a forked package, whose artifacts then get digested by "dak" into the initial publishing place (usually ceres). And then "britney" applies its time logic to propagate new packages from ceres into the upcoming release distribution, currently daedalus.

In my somewhat cloudy mind, chimaera-updates only holds "point release to be" packages for chimaera. Such packages has a precursor publishing point in chimaera-proposed-updates for confidence building before becoming chimaera-update packages.

Or, something like that. Someone with better insight would also be able to refer to Debian's applicable documentation regarding this.

In other words, when browsing https://pkgmaster.devuan.org/devuan you are browsing the forked packages only, and you'll need to browse https://pkgmaster.devuan.org/merged to see the meta-information (only) for the Devuan distribution repositories.

A full Devuan distribution repository is only available by browsing http://deb.devuan.org/merged, because it's a virtual directory tree that (through Devuan's web wizardry) consists of a combination of the meta information at pkgmaster:merged/, the forked packages at pkgmaster:devuan/ and (some of) the packages at http://deb.debian.org/debian/pool/... (via Debian's web wizardry applying load balancing and whatnot before landing at a stream of bytes)

Yes indeed, sorry Ralph I was getting confused there.

If I navigate to https://pkgmaster.devuan.org/devuan/dis … ates/main/ I can't see any Contents-* files and the Packages.{gz,xz} files at https://pkgmaster.devuan.org/devuan/dis … ary-amd64/ are completely empty.

Is there a problem with Amprolla?

Short answer from my mobile:

https://pkgmaster.devuan.org/merged/dis … ates/main/

If I navigate to https://pkgmaster.devuan.org/devuan/dis … ates/main/ I can't see any Contents-* files and the Packages.{gz,xz} files at https://pkgmaster.devuan.org/devuan/dis … ary-amd64/ are completely empty.

Is there a problem with Amprolla?

deb.devuan.org is the mirror round-robin, which ultimately resolves to any one of the package mirror hosts.

There is no devuan SSL access for those but they of course provide whatever services they want in addition to the package mirror service for "http://deb.devuan.org".

Regarding Firefox from @op thread.

I run Firefox Nightly on a stack CWM for months, CWM as a Window Manager doesn't have toolbar like Openbox, Fluxbox rather it is like a DWM or HLWM, but have mouse click feature.

Used to drag with left-click the firefox toolbar to move root window everywhere the mouse directed, but i can't do it anymore since a month. Also i have lost the top buttons on toolbar, i mean close, maximize, minimize.
Because "Title bar" from Customize that enabled it isn't available anymore from bottom left of the custom.

This is from Nightly 97.0a1 (2021-12-31) nightly/daily updated - Devuan Testing

It used to be like this
This is from Firefox 95.0.2 - Windows

While the F11 (Firefox Full screen) buttons are shown, but seems messed up without icons and a bit higher extended over mouse point.

I never reported this issues to reddit
https://old.reddit.com/r/firefox/

thinking that 1) they have either removed them as a function, 2) or will fix them later since the browser is experimental.

When i fire nightly from terminal doesn't show any log, i tried with new clean profile .mozilla without success.

So, i have a bit similar symptoms as @op or perhaps mine is different concern.

As CWM doesn't have toolbar i close dialogs with ESC or WM keybind if toolbar buttons aren't present, but losing the clickable and buttons to Firefox for me is a miss. Perhaps i may return them with a userChrome modification, but never bothered, i'm became a little lazy even to report