@honoriscreed: type 'stamp' into the search box in Options, turn off the last matching option. Come to the support group fb.com/groups/SocialFixerUserSupport

@leocg It had an editable 'post a comment here' box, which failed when I tried to submit. If it isn't intended to allow comments, please don't offer a comment box?

@coder-256 According to the git history, Tampermonkey went closed-source after version 2.9, in early 2013. So it has been that way for 6 years.

Opera's blacklisting of it was far more recent. I would like to hear their reason for doing so; especially as they did not blacklist the ID of the TM version found in their own 'store'.

I reported the listing to the Tampermonkey folks at https://github.com/Tampermonkey/tampermonkey/issues/635

Opera's blacklist of extensions is at https://extension-updates.opera.com/static/omaha/blacklist.txt and appears to be in chronological order of addition to the list. TM is the 2nd last entry; they must have added the last two at the same moment.

@burnout426: that was fixed in a way that should self-repair successfully on package update.

Since this was reawakened: the file I previously pointed to (https://extension-updates.opera.com/static/omaha/blacklist.txt) no longer exists; but TM is still blacklisted by Opera. It appears in my Preferences file -- certainly not by my preference, but injected there by Opera.

Opera! There is no reason to be blacklisting Tampermonkey non-beta.

@derjanb got some sort of response from them a long time ago, some sort of guff about TM being force-installed into people's Opera installations by some sort of malware, then used to run the malware's browser extension. Great. That is a bug, misfeature, attack, however you want to characterize it, ON THE PART OF THE MALWARE, not Tampermonkey!

And whatever that malware was, years ago, it is surely handled by people's antivirus etc. these days.

Please un-blacklist TamperMonkey non-beta, ID 'dhdgffkkebhmkfjojejmpbldmpobfkfo', from the Chrome 'store'. And the one from Opera 'store', but I don't know its non-beta ID as you've hidden it in the web UI.

See also DNAWIZ-49270; github.com/Tampermonkey/tampermonkey/issues/635

There were also comments about it on some of the beta blog posts, but those posts now have zero comments at all (https://blogs.opera.com/desktop/2019/01/opera-59-0-3187-0-developer-update/#comment-4270524260) -- ???

@kilian01: no, you are misusing the packaging system. dpkg -i will install any package regardless of whether its dependencies are met. That is its role. apt et al are in charge of the higher level, including paying attention to dependencies. It is like... dpkg -i is you with a screwdriver and some random memory DIMMs, clicking then into your motherboard without checking for compatibility. While apt is you using a tool like pcpartspicker or paying a store to install RAM they've selected as compatible with your system. You can download any .deb from your OS's repo with apt download name-of-package, then install it with dpkg -i name-of-package_version_you_received.deb -- and the resulting installed package will fail in similar ways if you didn't grab its dependencies. The OS's packages -- and Opera -- have met their responsibility by recording those dependencies in the .deb metadata. apt implements paying attention to them. dpkg is a more internal tool and it has to allow installing packages without their dependencies (otherwise some early stages of system install could not work, as the most basic packages circularly depend on each other).

BTW @derjanb you said the Opera 'store' edition would update alongside the Firefox edition, about every 3mo. https://addons.opera.com/en/extensions/details/tampermonkey-beta/ is on 4.13.6138, updated 2021-06-22, while FF is on 4.16.6160, updated 2022-04-05.

An ongoing issue with how Opera is framed on my desktop. First, I'm running Debian 'sid' with what I believe is its most default windowing environment: Gnome (49.1) with its Mutter window manager, a Wayland session, and 'adwaita' theme.

Long ago, Opera offered to frame its windows with the operating system / window manager's widgets, or Opera's own; but I can no longer find this option, so the only choice is 'Opera's own'; which means the window lacks normal widgets like 'close', 'minimize', etc. But it still has a drag handle area in the top bar (small bits of it, away from the various browser widgets).

The problem: subwindows also lack these widgets, and do not have a drag area. I am thinking particularly of the Inspector window, when it is detached from the browser window. It has no place to grab and drag.

So in sum: Linux:Gnome:Mutter:Wayland:Opera, detached Inspector window has no window manager widgets, particularly no drag area.

Image of truncated top bar situation

@filbo aaaand... confirmed the crash bug. Steps:

1. messages.google.com -- then do whatever setup is required for them to mirror your phone's SMS/RCS onto that site (might work without that -- not tested)

2. '⋮' menu on per-chat-top-bar of site > Send feedback

3. enter any text into 'Description' box

4. 'Capture screenshot'

5. dialog pops up, 'Allow messages.google.com to see this tab?'

6. click [Allow]

7. Opera crashes instantly

Starting with this release (but potentially a bit earlier as I may not have restarted between a couple earlier opera-developer builds): when Opera first starts up, the address bar is truncated. I see something like 30-35 chars worth, then a slight fade, then just empty background (as if the URL were only that long, but it is not).

This is visible on multiple tabs. As soon as I click inside the address bar, the full contents become visible, and this 'sticks' and fixes the address bar appearance on all tabs, for the rest of the session.

(Also: learned this because a web site crashed Opera. The site was messages.google.com, their web-access-to-SMS/RCS site. I had operated its '...' menu > Send feedback, wrote them a bug report, clicked on their 'take screenshot' button, got as far as telling it to actually take the screenshot -- and Opera restarted. Have not tried to reproduce this since then, not particularly enjoying sudden browser restarts...

Obviously these are two separate bugs for you to look into... : )

@sopronman: they're phasing out the beta build, leaving only 'stable' and 'dev' builds (but adding an 'early bird' setting to the stable build). Not sure why none of the Opera employees have mentioned it. Here is the blog post: https://blogs.opera.com/desktop/2025/12/opera-presents-early-bird-mode/

@kilian01: no, you are misusing the packaging system. dpkg -i will install any package regardless of whether its dependencies are met. That is its role. apt et al are in charge of the higher level, including paying attention to dependencies. It is like... dpkg -i is you with a screwdriver and some random memory DIMMs, clicking then into your motherboard without checking for compatibility. While apt is you using a tool like pcpartspicker or paying a store to install RAM they've selected as compatible with your system. You can download any .deb from your OS's repo with apt download name-of-package, then install it with dpkg -i name-of-package_version_you_received.deb -- and the resulting installed package will fail in similar ways if you didn't grab its dependencies. The OS's packages -- and Opera -- have met their responsibility by recording those dependencies in the .deb metadata. apt implements paying attention to them. dpkg is a more internal tool and it has to allow installing packages without their dependencies (otherwise some early stages of system install could not work, as the most basic packages circularly depend on each other).

@filbo: argh, I failed at formatting the setuid instructions. But, you shouldn't really do that anyway. Just install properly with apt install and the postinst script will handle the setuid.

@kilian01: I see 3 separate sets of issues in your log, unclear which of them might be relevant. First, easiest to fix, the sandbox binary has wrong permissions:

$ cd /usr/lib/x86_64-linux-gnu/opera-stable
$ sudo chown root opera_sandbox
$ sudo chmod 4755 opera_sandbox

Try after that.

But that is probably actually caused by the 2nd problem: the deb you're installing depends on 4 others, parts of your distro, which are not installed. Because of that it never finished installing, never ran /var/lib/dpkg/info/opera-stable.postinst which would have set up that setuid.

Package libqt5core5a is not installed.
Package libqt5gui5 is not installed.
Package libqt5gui5-gles is not installed.
Package libqt5widgets5 is not installed.
dpkg: error processing package opera-stable (--install):
dependency problems - leaving unconfigured

This not only leaves Opera unconfigured, but also missing libraries it depends on.

dpkg -i is the lowest level package installer. It is not meant to handle package dependencies; those belong to the higher APT subsystem. Try running instead: sudo apt install opera-stable_125.0.5729.21_amd64.deb. This will automatically pull in the packages it depends on.

The 3rd issue is a crash:

Trace/breakpoint trap (core dumped)

but that might be caused by the other two issues, so ignore it for now.

@burnout426: that was fixed in a way that should self-repair successfully on package update.

(and no, there was not a second window, I checked pretty carefully. Just one window with 14x FB + 1x Opera has been updated, counted as 26 tabs being closed.)

Whee, 'You can only post once every 120 second(s) - please wait before posting again'