mastodon.ie is one of the many independent Mastodon servers you can use to participate in the fediverse.
Irish Mastodon - run from Ireland, we welcome all who respect the community rules and members.

Administered by:

Server stats:

1.8K
active users

#techsupport

2 posts2 participants0 posts today

UGH... spent an hour trying to get my Ender5 to print properly. I don't know how to fix this.. I have an Ender 5 with a BLTouch. The nozzle is too high when it tries to print, so it's just air printing. Not very good.

Yes, I know about z-offset. I've set it. Over and over again. But it always seems to ignore it and I don't know why.

One further data point, I'm using Octoprint. So maybe I have to put the z-offset in there somewhere? Google hasn't been super helpful, so looking for suggestions.

Just posting this in case it helps somebody else: mastodon.nz refused to load for me today in two different browsers, each on two different machines. I could still access it in an app on my phone so I knew the server was fine.
In each browser, dev tools showed an empty document, but as soon as I clicked on the network tab in dev tools the page suddenly loaded.
Dunno what caused it, but that was the solution.
#TechSupport #mastodonNZ

Thinking of getting a refurbished Dell or Lenovo laptop to run linux on. Mostly to organise and process photos, but also some light CAD. I'll probably look for a laptop with 32gb ram.

The question is how much I should consider processor generation? Should I avoid laptops that are older than 11th gen intel processors?
Gen 9 and 10 are considerably cheaper, but I would like the computer to last a couple of years.

Trying to set up OpenMediaVault on my HP EliteDesk 800 G4 SFF, but my aftermarket NVMe isn’t detected during install (tested with Debian, OMV, TrueNAS, Arch). BIOS sees it, but no OS does. Even after installing the OS on another PC, the EliteDesk won’t boot from it. Only the original NVMe works. Secure Boot is off. Anyone solved this?

#OMV#Linux#Debian

So, I am stuck trying to apply the current #Mastodon update. Note that there may be many good reasons why, chief among them, that I am self-taught and very much in the "trying stuff out half-blindly while learning"-stage. Thankfully, nothing broke irreversably just yet.

If anyone here feels like helping a noob out, or just loves a conundrum, details can be found here:

lemmy.abnormalbeings.space/pos

lemmy.abnormalbeings.space[SUPPORT][Mastodon] Getting stuck on trying to apply the latest update - AbnormalLemmingscross-posted from: https://lemmy.abnormalbeings.space/post/804932 [https://lemmy.abnormalbeings.space/post/804932] I have searched around for answers to this, but so far, the solutions I found and tried have not been working for me. Thankfully, the update isn’t that critical, so time is not of the essence as of now. But I fear, the problem will only persist. So, bit of a headscratcher: I am following the guide to upgrade (no Docker) from here. [https://github.com/mastodon/mastodon/releases/tag/v4.3.7] Simple enough, right? Sadly, I keep getting: ~/live$ RAILS_ENV=production bundle exec rails assets:precompile I, [2025-04-03T20:30:30.072648 #981372] INFO -- : [dotenv] Loaded .env.production Mastodon and Webpacker requires Yarn ">=4 <5" and you are using 1.22.22 Exiting! So, the proposed solution? Using corepack as intended. That, at first, upon entering “corpack prepare” and “corepack enable” in succession, seemed to run silently and without errors/warnings. But it changed nothing at all for the error message. Prompting me to search around, haphazardly try to apply fixes, trying to remove and reinstall yarn, “the usual”. My last attempt was to globally remove yarn and corepack with npm and then re-install both. Since then, a new, exciting error is happening: ~/live$ corepack enable Internal Error: EACCES: permission denied, symlink '../lib/node_modules/corepack/dist/pnpm.js' -'/usr/bin/pnpm' at async Object.symlink (node:internal/fs/promises:1005:10) at async EnableCommand.generatePosixLink (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23156:5) at async Promise.all (index 0) at async EnableCommand.execute (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23143:5) at async EnableCommand.validateAndExecute (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:20258:22) at async _Cli.run (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21195:18) at async Object.runMain (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23642:19) Oh, and when trying to install yarn and corepack, now, I get: ~/live$ npm install yarn npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch npm error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log ~/live$ npm install corepack npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch npm error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log ::: spoiler the logs in question: $ cat /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log 0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@11.2.0 2 info using node@v22.14.0 3 silly config load:file:/usr/lib/node_modules/npm/npmrc 4 silly config load:file:/home/mastodon/live/.npmrc 5 silly config load:file:/home/mastodon/.npmrc 6 silly config load:file:/usr/etc/npmrc 7 verbose title npm install yarn 8 verbose argv "install" "yarn" 9 verbose logfile logs-max:10 dir:/home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z- 10 verbose logfile /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log 11 silly logfile start cleaning logs, removing 1 files 12 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368 13 silly logfile done cleaning log files 14 silly idealTree buildDeps 15 verbose stack Error: Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 15 verbose stack at unsupportedURLType (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:369:15) 15 verbose stack at fromURL (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:428:13) 15 verbose stack at Function.resolve (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:110:12) 15 verbose stack at #nodeFromEdge (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1039:22) 15 verbose stack at #buildDepStep (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:904:35) 15 verbose stack at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:181:7) 15 verbose stack at async Promise.all (index 1) 15 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5) 15 verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:149:5) 15 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9) 16 error code EUNSUPPORTEDPROTOCOL 17 error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 18 silly unfinished npm timer reify 1743710053061 19 silly unfinished npm timer reify:loadTrees 1743710053064 20 silly unfinished npm timer idealTree:buildDeps 1743710057205 21 silly unfinished npm timer idealTree:#root 1743710057206 22 verbose cwd /home/mastodon/live 23 verbose os Linux 6.1.0-31-amd64 24 verbose node v22.14.0 25 verbose npm v11.2.0 26 verbose exit 1 27 verbose code 1 28 error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log ~/live$ cat /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log 0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@11.2.0 2 info using node@v22.14.0 3 silly config load:file:/usr/lib/node_modules/npm/npmrc 4 silly config load:file:/home/mastodon/live/.npmrc 5 silly config load:file:/home/mastodon/.npmrc 6 silly config load:file:/usr/etc/npmrc 7 verbose title npm install corepack 8 verbose argv "install" "corepack" 9 verbose logfile logs-max:10 dir:/home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z- 10 verbose logfile /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log 11 silly logfile start cleaning logs, removing 1 files 12 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368 13 silly logfile done cleaning log files 14 silly idealTree buildDeps 15 verbose stack Error: Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 15 verbose stack at unsupportedURLType (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:369:15) 15 verbose stack at fromURL (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:428:13) 15 verbose stack at Function.resolve (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:110:12) 15 verbose stack at #nodeFromEdge (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1039:22) 15 verbose stack at #buildDepStep (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:904:35) 15 verbose stack at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:181:7) 15 verbose stack at async Promise.all (index 1) 15 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5) 15 verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:149:5) 15 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9) 16 error code EUNSUPPORTEDPROTOCOL 17 error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 18 silly unfinished npm timer reify 1743710065916 19 silly unfinished npm timer reify:loadTrees 1743710065919 20 silly unfinished npm timer idealTree:buildDeps 1743710070343 21 silly unfinished npm timer idealTree:#root 1743710070344 22 verbose cwd /home/mastodon/live 23 verbose os Linux 6.1.0-31-amd64 24 verbose node v22.14.0 25 verbose npm v11.2.0 26 verbose exit 1 27 verbose code 1 28 error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log ::: Thankfully, mastodon is still working, no database issues, nothing indicating I fucked up beyond repair yet. I am a bit at a loss, unfortunately, but eager to use my fuckup as a learning experience - am glad to hear any and all more experienced folk chiming in!

"Magic Help Line, my name is Lenore. How can I assist?" I addressed the mirror.

A turquoise cube materialized. "I'd like to leave feedback on a book I bought, Shapeshifting for the Uninitiated. I'm a math teacher and this is all very new to me."

"I'm so sorry, sir, but I'm afraid we don't submit third-party reviews. I should be able to fix your being a cube, though. Let me go ahead and prepare a counterspell to a Quadrilateral Curse."

"Oh, no, positive feedback! I've never been happier!" the cube shifted into a lavender dodecahedron. "A crone I met at the supermarket said she could tell I had natural shapeshifting talent and pulled the book straight out of her handbag."

"Ah, that's wonderful! I'm sure it's working wonderfully to teach your students geometry!"

"I teach calculus, miss," he shifted back into a human. "Teachers do have hobbies outside of work."

"Ah, my apologies. Let me bring up a list of review sites."

A 79 year-old man on the East Coast surprised me this weekend. He called me to work remotely on his Windows 7 computer. I think I talked him into upgrading to a new computer with Windows 11. He asked me for recommendations. I gave him the minimum specs I recommend and taught him how to read the specs in the ads at Best Buy. He said he knows a local computer shop, and he thinks he’ll just go in there with the list of specs I gave him and ask them to put one together.

That was the part that shocked me.

He’s in a state on the Atlantic Coast. He knows a local computer shop. Yet he calls me, in Washington State, for tech support.

Okay then. I’m honored, and happy to help.

#CallMeIfYouNeedMe #FIFONetworks

Anyone know why opening #IPv6 ports on #GoogleWifi might be failing for me? I have IPv6 service from my ISP (sonic.net - they're awesome!) and have a web server set up on my #RaspberryPi.

Requests from outside my network sent to the pi's IPv6 GUA keep failing, even though I have ports 80 and 443 open for the pi in the "Port Management" section of the google home app. Requests made to that same IPv6 GUA work fine within my network.

(I also have IPv4 port forwarding set up on that same page, and that seems to work fine to forward requests made to my router's external IPv4 address to the pi, so I could simply not set up an AAAA record and move forward with only IPv4 access to my server, but I'd prefer having a working dual-stack setup!)