<![CDATA[.deb versions of Opera 124.0.5705.* do not provide application ID]]>The deb version of Opera - tested both 124.0.5705.42 and the recently released 124.0.5705.65 - do not provide an application ID. Therefore GNOME can't assign the icon as seen in this screenshot:
screenshot_ubuntu.png

What's interesting is that the snap version actually provides an app ID. Therefore the correct icon is assigned as can be seen in this screenshot:
screenshot_snap.png
Then again, the snap version seems to be at version 124.0.5705.70, so I hope they fixed the issue already in the .deb version.

Old versions up to v123.* did actually provide an app ID so the icon worked as expected. Kind of strange.

]]>https://forums.opera.com/topic/87300/deb-versions-of-opera-124-0-5705-do-not-provide-application-idRSS for NodeTue, 17 Mar 2026 04:36:21 GMTThu, 27 Nov 2025 13:57:44 GMT60<![CDATA[Reply to .deb versions of Opera 124.0.5705.* do not provide application ID on Wed, 10 Dec 2025 11:03:48 GMT]]>@vittucci The solution is to run as x11. Just run opera --ozone-platform=x11

Before we were able to set flags by going into opera://flags. But it's removed now.

So run with the provided command -> update the .desktop file to use the command

]]>https://forums.opera.com/post/396881https://forums.opera.com/post/396881Wed, 10 Dec 2025 11:03:48 GMT<![CDATA[Reply to .deb versions of Opera 124.0.5705.* do not provide application ID on Wed, 10 Dec 2025 05:30:08 GMT]]>@aswinsanthosh Same issue.

Before they look into it, is there any workaround we can apply?

]]>https://forums.opera.com/post/396873https://forums.opera.com/post/396873Wed, 10 Dec 2025 05:30:08 GMT<![CDATA[Reply to .deb versions of Opera 124.0.5705.* do not provide application ID on Wed, 10 Dec 2025 05:30:08 GMT]]>@aswinsanthosh Same issue.

Before they look into it, is there any workaround we can apply?

]]>https://forums.opera.com/post/396874https://forums.opera.com/post/396874Wed, 10 Dec 2025 05:30:08 GMT<![CDATA[Reply to .deb versions of Opera 124.0.5705.* do not provide application ID on Sun, 30 Nov 2025 15:39:14 GMT]]>@ijpet This isnt a new issue, it existed for years now i think. Its due to wayland, when opera is set to run on wayland by setting ozone platform to auto or wayland this happens. Opera team haven't look into it, even me myself reported it in the forums.

why now its happening?
Well as far as i know Chrome made wayland default with v140. thereby opera now run on wayland by default

Its a good thing that it runs on wayland. I hope opera fixes it.

]]>https://forums.opera.com/post/396357https://forums.opera.com/post/396357Sun, 30 Nov 2025 15:39:14 GMT