[{"content":" Last week I planned a small coworking session with friends at a restaurant.\nI run Omarchy on my laptop (with Hyprland), and at home I usually work only with my external monitor.\nSo, in my infinite wisdom, I disabled the laptop screen in ~/.config/hyprland/monitors.conf.\nAt home it looked like a great fucking idea.\n☕ The setup At the restaurant, life was good. I had a latte, then a flat white, and even ordered a slice of carrot cake (highly recommended).\nThen I opened my laptop to start working.\nThe screen stayed black.\nNo problem, I thought. I’ll just rent a monitor.\nFive minutes later: no luck, the shop said no.\nSo I tried Google, ChatGPT, random searches — nothing worked. I was about to give up and just watch my friends type on their glowing screens when one of them said:\n“Can I try?”\n🖥️ The emergency shell In five minutes he had managed to enter the emergency shell (just by smashing Ctrl+C during boot).\nFrom there, I finally had hope.\nHere’s what we did, step by step:\nDecrypted the disk with cryptsetup (because my home partition is encrypted). Mounted the disk and found the Hyprland config. Edited the file (no nano, but luckily vi was available). Removed the line that disabled the laptop monitor. Saved, rebooted… and it worked. It felt like being back in college, fighting with Wi-Fi drivers for hours — frustrating but oddly fun.\n🍲 Happy ending After fixing the issue, I shut down the laptop, enjoyed the rest of the remote day, and ended up at a vegetarian buffet with friends.\nA chaotic afternoon turned into a pretty good story (and a learning session).\n💡 Thoughts / Lessons Learned how to access the emergency shell (Ctrl+C during boot). Confirmed that cryptsetup is the tool for decrypting LUKS partitions. Emergency shell doesn’t have all your usual tools, but vi is almost always there. Linux troubleshooting is always try → fail → learn. It’s frustrating, but that’s how you grow. And of course: “If it doesn’t work, you forgot to compile the kernel.” (old Linux joke). 🛠️ Technical Notes: Editing a Config in Emergency Shell 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 # Check partitions cat /proc/partitions # Example: open encrypted device cryptsetup luksOpen /dev/nvme0n1p3 cryptroot # (enter passphrase) # Mount the device mount /dev/mapper/cryptroot /mnt # Navigate and edit the config vi /mnt/home/\u0026lt;your-user\u0026gt;/.config/hypr/monitors.conf # Remove the line disabling the monitor, e.g.: # monitor=eDP-1,disable # Save and reboot ","permalink":"https://blog.pazth.org/posts/a-friday-lunch-fix/","summary":"\u003cfigure\u003e\n    \u003cimg loading=\"lazy\" src=\"me-at-coding.jpg\"\n         alt=\"Working through laptop repairs at a cafe\"/\u003e \n\u003c/figure\u003e\n\n\u003cp\u003eLast week I planned a small coworking session with friends at a restaurant.\u003cbr\u003e\nI run \u003cstrong\u003eOmarchy\u003c/strong\u003e on my laptop (with Hyprland), and at home I usually work only with my external monitor.\u003cbr\u003e\nSo, in my infinite wisdom, I disabled the laptop screen in \u003ccode\u003e~/.config/hyprland/monitors.conf\u003c/code\u003e.\u003cbr\u003e\nAt home it looked like a \u003cem\u003egreat fucking idea\u003c/em\u003e.\u003c/p\u003e\n\u003chr\u003e\n\u003ch3 id=\"-the-setup\"\u003e☕ The setup\u003c/h3\u003e\n\u003cp\u003eAt the restaurant, life was good. I had a latte, then a flat white, and even ordered a slice of carrot cake (highly recommended).\u003cbr\u003e\nThen I opened my laptop to start working.\u003c/p\u003e","title":"A Friday Lunch Fix: How I Broke My Omarchy Laptop Screen (and Repaired It in Emergency Shell)"},{"content":"Hi, I\u0026rsquo;m Pazthor 👋 I\u0026rsquo;m a developer who enjoys tinkering with Linux systems, exploring new tools, and occasionally breaking things in the process (see: that time I disabled my laptop screen).\nWhat I do I work with various technologies and enjoy sharing what I learn along the way. This blog is my space for documenting experiments, troubleshooting adventures, and technical notes that might help others (or future me) avoid the same pitfalls.\nWhat you\u0026rsquo;ll find here Technical notes on Linux, system configuration, and development tools Troubleshooting stories from real-world problems and their solutions Setup guides for workflows and infrastructure Anecdotes from the developer life My setup OS: Omarchy Linux with Hyprland Tools: Hugo, Docker, Git, and whatever gets the job done Philosophy: Try → fail → learn → document Connect Feel free to explore the posts or check out the repository on GitHub. If you\u0026rsquo;ve had similar experiences or have questions, I\u0026rsquo;d love to hear about them.\nThis blog is built with Hugo and hosted on GitHub Pages.\n","permalink":"https://blog.pazth.org/about/","summary":"\u003ch2 id=\"hi-im-pazthor-\"\u003eHi, I\u0026rsquo;m Pazthor 👋\u003c/h2\u003e\n\u003cp\u003eI\u0026rsquo;m a developer who enjoys tinkering with Linux systems, exploring new tools, and occasionally breaking things in the process (see: \u003ca href=\"/posts/a-friday-lunch-fix/\"\u003ethat time I disabled my laptop screen\u003c/a\u003e).\u003c/p\u003e\n\u003ch3 id=\"what-i-do\"\u003eWhat I do\u003c/h3\u003e\n\u003cp\u003eI work with various technologies and enjoy sharing what I learn along the way. This blog is my space for documenting experiments, troubleshooting adventures, and technical notes that might help others (or future me) avoid the same pitfalls.\u003c/p\u003e","title":"About"},{"content":"This site now runs on Hugo. The source lives in this repository and publishes automatically through GitHub Pages. Explore the repo structure, update config.toml with your preferences, and create new posts with hugo new posts/my-next-post.md.\nWhen you\u0026rsquo;re ready to preview, run hugo server for live reload. The deployment workflow builds the site on main and publishes it to the gh-pages branch.\n","permalink":"https://blog.pazth.org/posts/hello-hugo/","summary":"\u003cp\u003eThis site now runs on \u003ca href=\"https://gohugo.io/\"\u003eHugo\u003c/a\u003e. The source lives in this repository and publishes automatically through GitHub Pages. Explore the repo structure, update \u003ccode\u003econfig.toml\u003c/code\u003e with your preferences, and create new posts with \u003ccode\u003ehugo new posts/my-next-post.md\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eWhen you\u0026rsquo;re ready to preview, run \u003ccode\u003ehugo server\u003c/code\u003e for live reload. The deployment workflow builds the site on \u003ccode\u003emain\u003c/code\u003e and publishes it to the \u003ccode\u003egh-pages\u003c/code\u003e branch.\u003c/p\u003e","title":"Hello Hugo"}]