In that forum it says that you must edit the parameters of the command line with which Vivaldi is launched by your graphic desktop to get scrolling, if that is what you want.
I am pretty sure that the middle mouse button is not broken in Vivaldi on Linux.
It probably just has a different default behavior than what you expect, e.g. the middle button might have been allocated by default to mouse gestures, not to clipboard or scrolling or whatever you expect.
I am using Vivaldi, but I do not remember which was its default behavior, because I no longer use mice, but a stylus on a small graphic tablet, and I reconfigured Vivaldi for the buttons of my Wacom stylus.
In any case, if I had been using a mouse, I would have wanted to allocate the middle button to mouse gestures, because those are much more useful than the uses of the middle button for the X clipboard or for scrolling.
Subscriptions provide thousands of dollars' worth of tokens if measured at API prices. While the value was once absurd, it is now slightly lower but still much cheaper.
Grinding through abandoned source code in hopes of finding a vulnerability isn't exactly the most fulfilling work for many, perfect use case for AI which doesn't sleep.
Apparently both bugs had been reported previously, pre-AI, if so some important questions need to be asked about how those reports slipped through without a fix.
That report describes sending a 2^31 length filename, which is cast to a negative number, which leads to asking erealloc() to allocate a very large buffer, which fails, which leads to the symptoms of the bug we're discussing today (mid-request allocation failure becomes a partially initialised request)
The fix at the time wasn't to do proper cleanup on eralloc() failure, it was merely to avoid filename length being cast to a negative number.
reply