<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Opera 136 crashes on startup on Linux due to old rich_wallpapers preference]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">after updating Opera to <strong>136.0.6008.52</strong>, Opera stopped starting with my existing profile on <strong>Pop!_OS 24.04 LTS</strong>.</p>
<p dir="auto">Starting Opera from a terminal resulted in:</p>
<pre><code>Illegal instruction (core dumped)
</code></pre>
<p dir="auto">and no Opera window appeared.</p>
<p dir="auto"><strong>System Information</strong><br />
Opera: 136.0.6008.52<br />
OS: Pop!_OS 24.04 LTS<br />
Kernel: 7.1.5-76070105-generic<br />
CPU: Intel Core i7-14650HX</p>
<p dir="auto"><strong>What I tested</strong><br />
A completely clean profile works normally:</p>
<pre><code>opera --user-data-dir=/tmp/opera-test
</code></pre>
<p dir="auto">I then found that renaming:</p>
<pre><code>~/.config/opera/Default/Preferences
</code></pre>
<p dir="auto">also allowed Opera to start normally. Opera generated a new <code>Preferences</code> file by itself.</p>
<p dir="auto">This showed that the problem was somewhere in the old Preferences rather than in Opera itself or the entire profile directory.</p>
<p dir="auto">I compared the old and newly generated Preferences files and tested individual top-level JSON sections by transferring them between a working and non-working configuration.</p>
<p dir="auto">After narrowing the problem down, I was able to reproduce the startup crash with the old <code>rich_wallpapers</code> section.</p>
<p dir="auto">In particular, my old Preferences contained:</p>
<pre><code class="language-json">"rich_wallpapers": {
    "revert_wallpaper_time": "0",
    "selected_id": "mods/mcidbianigdmjfmianaeckfdfpgihncn/default",
    "takeover_wallpaper_id": ""
}
</code></pre>
<p dir="auto">The newly generated working Preferences instead used:</p>
<pre><code class="language-json">"rich_wallpapers": {
    "revert_wallpaper_time": "0",
    "selected_id": "bundled/default"
}
</code></pre>
<p dir="auto">Replacing the old rich-wallpaper selection with:</p>
<pre><code class="language-json">"selected_id": "bundled/default"
</code></pre>
<p dir="auto">allows <strong>my original Preferences file to work again</strong>, while keeping the rest of my previous configuration, including my sidebar and UI settings.</p>
<p dir="auto">Restoring the old <code>rich_wallpapers</code> setting reproduces the startup crash.</p>
<p dir="auto"><strong>Steps to reproduce in my profile</strong></p>
<ol>
<li>Use the old Preferences file with:</li>
</ol>
<pre><code>rich_wallpapers.selected_id = mods/mcidbianigdmjfmianaeckfdfpgihncn/default
</code></pre>
<ol start="2">
<li>Start Opera 136.0.6008.52.</li>
<li>Opera terminates during startup with:</li>
</ol>
<pre><code>Illegal instruction (core dumped)
</code></pre>
<p dir="auto">and no browser window opens.</p>
<p dir="auto"><strong>Expected behavior</strong><br />
If an old Mod wallpaper is no longer valid or compatible, Opera should ignore it or fall back to the default wallpaper.<br />
<strong>Actual behavior</strong><br />
Opera crashes during startup and the browser cannot be opened until the <code>rich_wallpapers</code> preference is changed.<br />
<strong>Workaround</strong><br />
With Opera completely closed, changing:<br />
<code>rich_wallpapers.selected_id</code><br />
from:<br />
<code>mods/mcidbianigdmjfmianaeckfdfpgihncn/default</code><br />
to:<br />
<code>bundled/default</code><br />
in:<br />
<code>~/.config/opera/Default/Preferences</code><br />
makes Opera start again.</p>
<p dir="auto">I have also submitted this crash through Opera's crash-report form.</p>
<p dir="auto"><strong>Additional observation:</strong> after recovering the profile, Opera starts normally, but several pre-installed Mod wallpapers no longer work. The terminal shows repeated <code>content_verify_job.cc:489</code> errors for Mod resources, including <code>wallpaper/dark.jpg</code>, <code>wallpaper/light.jpg</code>, <code>music/music.ogg</code> and multiple files under <code>sounds/</code>. This suggests that the startup crash may be related to an old selected rich wallpaper whose Mod contents no longer pass Opera's extension content verification after the update.</p>
]]></description><link>https://forums.opera.com/topic/89684/opera-136-crashes-on-startup-on-linux-due-to-old-rich_wallpapers-preference</link><generator>RSS for Node</generator><lastBuildDate>Fri, 02 Oct 2026 00:51:18 GMT</lastBuildDate><atom:link href="https://forums.opera.com/topic/89684.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 29 Sep 2026 13:33:02 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Opera 136 crashes on startup on Linux due to old rich_wallpapers preference on Tue, 29 Sep 2026 17:52:37 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forums.opera.com/uid/1060682">@VitPavelka</a> That’s some seriously good troubleshooting. Since you can reproduce the crash just by restoring that rich_wallpapers.selected_id, I’d say you’ve isolated the problem pretty well.</p>
<p dir="auto">I’d definitely include those exact steps and the before/after selected_id values in the bug report. Opera’s 136.0.6008.52 release did include crash fixes, but the published changelog doesn’t mention this wallpaper/profile issue, so your reproduction case could be really useful to them.</p>
<p dir="auto">For now, changing it back to bundled/default sounds like the sensible workaround.</p>
]]></description><link>https://forums.opera.com/post/410513</link><guid isPermaLink="true">https://forums.opera.com/post/410513</guid><dc:creator><![CDATA[malcolmparkedhere]]></dc:creator><pubDate>Tue, 29 Sep 2026 17:52:37 GMT</pubDate></item></channel></rss>