<?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[Scaling issues with MM 2.35 using NPM Run Start:x11]]></title><description><![CDATA[<p dir="auto">I am having to use NPM Run Start:x11 to get MM 2.35 to run.  NPM start was working in 2.34.  Now I am having scaling and text issues  and would greatly appreciate some help with troubleshooting this.  Here is some info about my machine:<br />
[2026-04-11 21:12:18.020] [INFO]  [systeminformation]</p>
<h4>System Information</h4>
<ul>
<li>SYSTEM:   manufacturer: libre-computer; model: aml-s905x-cc-v2; virtual: false; MM: v2.35.0</li>
<li>OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.1.92-15907-gf36fd2695db3</li>
<li>VERSIONS: electron: 41.1.0; used node: 22.21.1; installed node: 22.21.1; npm: 10.9.4; pm2: 6.0.14</li>
<li>ENV:      XDG_SESSION_TYPE: x11; MM_CONFIG_FILE: undefined<br />
WAYLAND_DISPLAY:  undefined; DISPLAY: :0; ELECTRON_ENABLE_GPU: undefined</li>
<li>RAM:      total: 1944.19 MB; free: 969.87 MB; used: 974.32 MB<br />
I posted pictures comparing 2.34 and 2.35.  Please let me know if I can provide additional info that would be helpful.  Thanks!<img src="/assets/uploads/files/1775957718293-2.34.png" alt="2.34.png" class=" img-fluid img-markdown" /> <img src="/assets/uploads/files/1775957724557-2.35.png" alt="2.35.png" class=" img-fluid img-markdown" /></li>
</ul>
]]></description><link>https://forum.magicmirror.builders/topic/20210/scaling-issues-with-mm-2.35-using-npm-run-start-x11</link><generator>RSS for Node</generator><lastBuildDate>Sun, 12 Apr 2026 23:09:43 GMT</lastBuildDate><atom:link href="https://forum.magicmirror.builders/topic/20210.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 12 Apr 2026 01:35:59 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Scaling issues with MM 2.35 using NPM Run Start:x11 on Sun, 12 Apr 2026 02:20:47 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/dde12" aria-label="Profile: DDE12">@<bdi>DDE12</bdi></a> we changed the default for npm start to be Wayland as we documented in the release notes</p>
<p dir="auto">That is why you have to use npm run start:x11</p>
<p dir="auto">We also moved user files to the config folder<br />
And moved the default modules to their own folder away from the modules folder</p>
<p dir="auto">As I posted about a month ago.</p>
<p dir="auto">How did you upgrade? git pull or my scripted upgrade?</p>
]]></description><link>https://forum.magicmirror.builders/post/130767</link><guid isPermaLink="true">https://forum.magicmirror.builders/post/130767</guid><dc:creator><![CDATA[sdetweil]]></dc:creator><pubDate>Sun, 12 Apr 2026 02:20:47 GMT</pubDate></item><item><title><![CDATA[Reply to Scaling issues with MM 2.35 using NPM Run Start:x11 on Sun, 12 Apr 2026 02:17:22 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/dde12" aria-label="Profile: DDE12">@<bdi>DDE12</bdi></a> did your css/custom.css file get moved to the config folder?</p>
]]></description><link>https://forum.magicmirror.builders/post/130766</link><guid isPermaLink="true">https://forum.magicmirror.builders/post/130766</guid><dc:creator><![CDATA[sdetweil]]></dc:creator><pubDate>Sun, 12 Apr 2026 02:17:22 GMT</pubDate></item></channel></rss>