Posts made by BruceHankins

This is the only reason I keep Chrome or Firefox around. It seems like there are no plans to implement PWA support in Opera, does anyone know if there's an extension that can be used to add PWAs?

@brucehankins bump bump....

Looking for some help. I've added the Opera .rpm repo to Fedora, and everything works perfectly, except no matter what I do, the browser won't see my printer. The same goes for Chrome browser also.

I've tried with a fresh clean install (no extensions, default flags, etc.) or with my flags and extension customized, doesn't matter.

Here is what' I've tried so far:
ensure that I ran

sudo systemctl enable --now cups.service

Checked to see if core/system apps can print. Yes, no issue seeing the printer in system settings, Gnome Document Viewer, or other core apps.

Installed Firefox from Opera repos, no issue finding the printer or printing from Firefox.

Installed Opera from flatpak - This version has no problem finding the printer or printing, but will not allow for playback of any DRM content. So no Spotify in the sidebar, bitmovin DRM test fails instantly, no streaming. Obviously some issue with Widevine/ffmpeg here.

Installed HPlip and added the printer through there (rather than just cups) and no change at all.

I'd really like to be able to print directly from the browser, and not have to download a document, picture, etc. and print it from the system apps....or use another browser entirely. Someone help please!

OS and hardware info

OS: Fedora Linux 39 (Workstation Edition) x86_64
Host: Latitude 5520
Kernel: 6.7.6-200.fc39.x86_64
WM: Mutter (Wayland)
CPU: 11th Gen Intel(R) Core(TM) i5-1145G7 (8) @ 4.40 GHz

Is there any plan to fix the changelog?

Link to the changelog is broken.

@burnout426 I just installed this on my distro and can confirm minimize behavior now works.
I wish the changelog would load so I could see if this was a known bug fix. Changelog for 83 just doesn't work.

What's going on with the 83 changelog? Every time I try to click the link and go to https://blogs.opera.com/desktop/changelog-for-83/ I get a not found error message. It makes it particularly difficult for package maintainers when there's no changelog available.

I'm having the same issue using Solus KDE and kwin scripts. Any plan to fix this? Don't have this issue with Firefox, Brave, etc.

@jferreira I agree, but I'm not leaving. Unfortunately for the users on my distro of choice, Opera will be held back on 79 until a fix is implemented and 80 truly is stable and not so much of a dev/beta release.

@styen it doesn't, I'm the maintainer responsible for updating the package. Hopefully the next release will work better.

@l33t4opera thanks for the reply. The opera-stable .deb package is licensed as distributable, and I'm making no changes to the software, just repackaging from a .deb to an .eopkg format.

@gmiazga this version has the same libffmpeg.so issue

@gmiazga I'll try installing locally and see if that works. They upgraded to chromium 94 with the opera-stable release but my understanding is it's still using the codecs from chromium 92. This seems like a pretty big oversight. It means as the package maintainer I now how to compile and add the new libffmpeg.so codecs as a build dependency when packaging opera-stable for it to run properly.

What about the issue with opera-stable 80 and libffmpeg.so? I'm getting error opera: symbol lookup error: opera: undefined symbol: av_stream_get_first_dts. Also posted a question about it lhere with all the build and system details.

Hello all,
I recently packaged opera-stable 80.0.4170.16 for my distro and the browser will not launch. When running from terminal, I receive this error

opera: symbol lookup error: opera: undefined symbol: av_stream_get_first_dts

From what I can find, this is a problem with the packaging to libffmpeg.so. I was able to find a coupe posts on the topic, but they were related to Opera 80 Beta this post and lthis one also. I would have expected that with Opera 80 being promoted to stable and the release of opera-stable 80.0.4170.16 this would have been fixed or the correct codecs included in the build. Is there something I'm missing or do I need to repackage this with the correct codecs from https://repo.herecura.eu/herecura/x86_64/opera-beta-ffmpeg-codecs-94.0.4606.31-1-x86_64.pkg.tar.zst?
Testing of all new packages is done in a clean VM to ensure proper operation before submitting for inclusion to the repos, So there's no .cache files or anything like that.

OS: Solus Plasma 4.3
Kernel Version: 5.14.7-198.current
KDE Plasma Version: 5.22.5
KDE Frameworks VersionL 5.85.0
Qt Version: 5.15.3
WM: X11
Packaged from: https://get.geo.opera.com/pub/opera/desktop/80.0.4170.16/linux/opera-stable_80.0.4170.16_amd64.deb

I too would love to see extensions come to Opera for Android. I use my tablet like a laptop and would love to have that access to Grammerly, Drive, and other extensions I use on desktop verions there too.