TechHub

A Cubed Business Solutions🚀 A³ GIMP Docs v1.1.0 is live! We’ve refined the visual structure, tuned the cursor alignment for HiDPI, and tightened the walkthrough timing. This quick tour shows how fast and clear our new GIMP documentation experience really is.Explore it here: <a href="https://aaabscom.github.io/a3bs-public/" rel="nofollow noopener" translate="no" target="_blank">https://aaabscom.github.io/a3bs-public/</a><a href="https://mastodon.social/tags/GIMP" class="mention hashtag" rel="nofollow noopener" target="_blank">#GIMP</a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://mastodon.social/tags/Docs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docs</a> <a href="https://mastodon.social/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a> <a href="https://mastodon.social/tags/a3bs" class="mention hashtag" rel="nofollow noopener" target="_blank">#a3bs</a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/DesignTools" class="mention hashtag" rel="nofollow noopener" target="_blank">#DesignTools</a>

Christian GudrianTrying to get started building a desktop application with a <a href="https://social.tchncs.de/tags/3D" class="mention hashtag" rel="nofollow noopener" target="_blank">#3D</a> viewport using <a href="https://social.tchncs.de/tags/Vulkan" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vulkan</a> and <a href="https://social.tchncs.de/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> on <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>.What. A. Frustrating. Mess.Fast moving (and breaking) APIs. Outdated examples. Missing features (looking at you, <a href="https://social.tchncs.de/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a> support).I guess I'm coming back later.Currently, the most stable approach seems to be <a href="https://social.tchncs.de/tags/GTK4" class="mention hashtag" rel="nofollow noopener" target="_blank">#GTK4</a>'s GLArea and plain old <a href="https://social.tchncs.de/tags/OpenGL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenGL</a>.

Ramin Honary<a class="u-url mention" href="https://social.linux.pizza/@theDuesentrieb" rel="nofollow noopener" target="_blank">@theDuesentrieb</a> I asked for the highest-spec computer the company would buy me (which turned out to be an Apple MacBook M2). I then promptly installed a QEMU-based emulator and installed Debian Linux into the emulator. The emulated disk is fully encrypted. I allow the VM full use of all CPU cores and 100% of all memory and disk space.If you do get a Apple computer, I highly recommend you buy <a href="https://mac.getutm.app/" rel="nofollow noopener" target="_blank">UTM</a> from the app store, it is by far the most cost-effective option, and works extremely well with Debian Aarch64. Once you install the <code>qemu-guest-agent</code> package onto Linux, the Linux screen resolution will automatically match the <a class="hashtag" href="https://fe.disroot.org/tag/macbook" rel="nofollow noopener" target="_blank">#MacBook</a>, copy-paste works seamlessly between <a class="hashtag" href="https://fe.disroot.org/tag/linux" rel="nofollow noopener" target="_blank">#Linux</a> and <a class="hashtag" href="https://fe.disroot.org/tag/macos" rel="nofollow noopener" target="_blank">#MacOS</a>. Desktop environments like <a class="hashtag" href="https://fe.disroot.org/tag/cinnamon" rel="nofollow noopener" target="_blank">#Cinnamon</a>, <a class="hashtag" href="https://fe.disroot.org/tag/xfce" rel="nofollow noopener" target="_blank">#Xfce</a>, <a class="hashtag" href="https://fe.disroot.org/tag/gnome" rel="nofollow noopener" target="_blank">#Gnome</a>, and <a class="hashtag" href="https://fe.disroot.org/tag/kdeplasma" rel="nofollow noopener" target="_blank">#KDEPlasma</a> all allow you to select <a class="hashtag" href="https://fe.disroot.org/tag/hidpi" rel="nofollow noopener" target="_blank">#HiDPI</a> scaling which allows Linux to take full advantage of the <a class="hashtag" href="https://fe.disroot.org/tag/apple" rel="nofollow noopener" target="_blank">#Apple</a> “retina” display (it looks beautiful). The one and only drawback is that <a class="hashtag" href="https://fe.disroot.org/tag/qemu" rel="nofollow noopener" target="_blank">#QEMU</a> cannot use Apple’s hardware multimedia codecs, so it falls back to software codecs, and the CPU just can’t keep up with things like video conferencing, or often even ordinary 720p video playback. I use Mac OS for only multimedia applications and video conferencing. For everything else, I continue to use Linux.I recommend the bridge networking adapter so you can have two-way network communications between Linux and MacOS, this allows for file transfer between Mac and Linux via <code>rsync</code>. The trade-off is that every time your Apple computer switches computers networks (e.g. between home and office), you must reset the networking services in Linux. If you choose the NAT network option Linux will always have network access directly via the MacOS interface, but you will not be able to easily transfer files between Mac and Linux.The keyboard is the hardest thing to get used to, mostly that “super” and “alt” are swapped. Be sure to transpose those keys in the <a class="hashtag" href="https://fe.disroot.org/tag/utm" rel="nofollow noopener" target="_blank">#UTM</a> configuration. It is easy to configure the Apple keyboard to (for example) make caps-lock another control key.<a class="hashtag" href="https://fe.disroot.org/tag/tech" rel="nofollow noopener" target="_blank">#tech</a> <a class="hashtag" href="https://fe.disroot.org/tag/computers" rel="nofollow noopener" target="_blank">#computers</a>

hansenerd2025, the year I switch from wayland to Xorg.Why? Because I bought a new screen. Huh? Well, I don't know either. Plasma 6 on wayland worked fine with my fullhd-screen. Yesterday, I powered the box down, switched to my new hi(gher)dpi screen, powered it on, got the bios post, boot messages, and a black screen instead of sddm. An hour later I found that sddms wayland support is experimental still, so I switched it to X, and got a black screen when my plasma-wayland session was to start. So, switched to plasma-x11 and everything is fine. Other compositor (tested sway) are fine. 🤷Don't know if it's nixos or plasma, I'll probably try a live usb later. So yeah, it's the year 2025 and I'm on X. Well, could be worse, could be the other X.<a href="https://gts.zknt.org/tags/nixos" class="mention hashtag" rel="nofollow noopener" target="_blank">#nixos</a> <a href="https://gts.zknt.org/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayland</a> <a href="https://gts.zknt.org/tags/plasma" class="mention hashtag" rel="nofollow noopener" target="_blank">#plasma</a> <a href="https://gts.zknt.org/tags/hidpi" class="mention hashtag" rel="nofollow noopener" target="_blank">#hidpi</a>

RavenGIMP 3.0 is finally out with GTK 3 user interface, better UI scaling on HiDPI, Wayland support, non-destructive layer effects, color space management, improved file format support, and usability improvements<a href="https://testing.gimp.org/release-notes/gimp-3.0.html#updated-gtk3-user-interface" rel="nofollow noopener" translate="no" target="_blank">https://testing.gimp.org/release-notes/gimp-3.0.html#updated-gtk3-user-interface</a><a href="https://mastodon.bsd.cafe/tags/gimp" class="mention hashtag" rel="nofollow noopener" target="_blank">#gimp</a> <a href="https://mastodon.bsd.cafe/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.bsd.cafe/tags/imageeditor" class="mention hashtag" rel="nofollow noopener" target="_blank">#imageeditor</a> <a href="https://mastodon.bsd.cafe/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayland</a> <a href="https://mastodon.bsd.cafe/tags/hidpi" class="mention hashtag" rel="nofollow noopener" target="_blank">#hidpi</a> <a href="https://mastodon.bsd.cafe/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#freesoftware</a> <a href="https://mastodon.bsd.cafe/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

Kevin Karhan :verified:<a href="https://wetdry.world/@nerm_nelly" class="u-url mention" rel="nofollow noopener" target="_blank">@nerm_nelly</a> ni, and most shut doesn't scale on non-<a href="https://infosec.space/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a> or <a href="https://infosec.space/tags/PortraitMode" class="mention hashtag" rel="nofollow noopener" target="_blank">#PortraitMode</a>!

Firepal3DI officially have a usable Arch Linux with <a href="https://tilde.zone/tags/KDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDE</a> on my desktop. KDE looks great on a <a href="https://tilde.zone/tags/hidpi" class="mention hashtag" rel="nofollow noopener" target="_blank">#hidpi</a> display.Slowly adding back things I used to use on Windows. Installing and configuring stuff is a bit of work, and there are some bumps, but settling after feels nice.<a href="https://tilde.zone/tags/archlinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#archlinux</a>

Kevin Karhan :verified:<a href="https://piou.foolbazar.eu/@joel" class="u-url mention" rel="nofollow noopener" target="_blank">@joel</a> I mean, <a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener" target="_blank">#SystemD</a> wasn't done by <a href="https://infosec.space/tags/Poettering" class="mention hashtag" rel="nofollow noopener" target="_blank">#Poettering</a> because he had no hobbies - far from it.<ul><li><a href="https://infosec.space/tags/SysVinit" class="mention hashtag" rel="nofollow noopener" target="_blank">#SysVinit</a> sucks and <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> needs to modernize and change solely because many components like <a href="https://infosec.space/tags/Xorg" class="mention hashtag" rel="nofollow noopener" target="_blank">#Xorg</a>, <a href="https://infosec.space/tags/OSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OSS</a> / <a href="https://infosec.space/tags/ALSA" class="mention hashtag" rel="nofollow noopener" target="_blank">#ALSA</a> and <a href="https://infosec.space/tags/OpenGL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenGL</a> are to be retired or are already only on life support.</li></ul>SystemD, like <a href="https://infosec.space/tags/Wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wayland</a> and <a href="https://infosec.space/tags/PipeWire" class="mention hashtag" rel="nofollow noopener" target="_blank">#PipeWire</a> is a "necessary evil" because the preexisting solutions are slow, not adaptive, cumbersome or just don't work well at all (i.e. mixed (<a href="https://infosec.space/tags/DPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#DPI</a> & <a href="https://infosec.space/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a>) screens with <a href="https://infosec.space/tags/X11" class="mention hashtag" rel="nofollow noopener" target="_blank">#X11</a> are just broken!<ul><li>People had years if not over a decade to fix those but they didn't and it's clear that a new & clean slate was necessary...</li></ul>

The Peter Pan of Nerdery™ 🇦🇺🏜️Was playing around with the <a href="https://mastodon.social/tags/MacMini" class="mention hashtag" rel="nofollow noopener" target="_blank">#MacMini</a>. Hooked up <a href="https://mastodon.social/tags/HDMI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HDMI</a> to my <a href="https://mastodon.social/tags/4K" class="mention hashtag" rel="nofollow noopener" target="_blank">#4K</a> monitor expecting to be able to use a scaled resolution (in my case, 3072x1728 <a href="https://mastodon.social/tags/HIDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HIDPI</a>). Wouldn't work. Only worked in <a href="https://mastodon.social/tags/LODPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#LODPI</a>. Then I read this article - a little disturbing. Apparently the M4 can't run HIDPI 4K across HDMI. But I CAN run it with a dumb TB -> dongle -> HDMI setup like I was forced to do on the Macbook Air (due to no HDMI port). For real?! That is fucking STUPID. <a href="https://forums.macrumors.com/threads/for-lg-oled-users-mac-mini-m4-does-not-support-hidpi-4k-over-hdmi-2-1.2442797/" rel="nofollow noopener" translate="no" target="_blank">https://forums.macrumors.com/threads/for-lg-oled-users-mac-mini-m4-does-not-support-hidpi-4k-over-hdmi-2-1.2442797/</a>

Matthieu<a href="https://fosstodon.org/@thelinuxcast" class="u-url mention" rel="nofollow noopener" target="_blank">@thelinuxcast</a> I'd be interested to know how you made i3wm/Xorg work with your strange <a href="https://mamot.fr/tags/monitor" class="mention hashtag" rel="nofollow noopener" target="_blank">#monitor</a> 🖥️ With <a href="https://mamot.fr/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a> and various scaling changes, I can only work with <a href="https://mamot.fr/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayland</a> and <a href="https://mamot.fr/tags/wlroots" class="mention hashtag" rel="nofollow noopener" target="_blank">#wlroots</a> or <a href="https://mamot.fr/tags/plasma" class="mention hashtag" rel="nofollow noopener" target="_blank">#plasma</a>

Y⃒̸̷̝̜̙ͥͥͥngmarHacker bunny at work. Bunnies prefer 10" with mushy keyboards and can handle tiny fonts on <a href="https://social.tchncs.de/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a> displays.I offered carrots but she's hacking just for fun.<a href="https://social.tchncs.de/tags/Hacker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hacker</a> <a href="https://social.tchncs.de/tags/Bunny" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bunny</a> <a href="https://social.tchncs.de/tags/Plush" class="mention hashtag" rel="nofollow noopener" target="_blank">#Plush</a> <a href="https://social.tchncs.de/tags/Laptop" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laptop</a> <a href="https://social.tchncs.de/tags/MrRobot" class="mention hashtag" rel="nofollow noopener" target="_blank">#MrRobot</a> <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://social.tchncs.de/tags/MXLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#MXLinux</a>

Kevin Karhan :verified:<a href="https://appdot.net/@tewha" class="u-url mention" rel="nofollow noopener" target="_blank">@tewha</a> Yeah, <a href="https://infosec.space/tags/DPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#DPI</a> and handling mixed-DPI / size setups is something neither <a href="https://infosec.space/tags/Xorg" class="mention hashtag" rel="nofollow noopener" target="_blank">#Xorg</a> nor <a href="https://infosec.space/tags/Wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wayland</a> nor <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a>'s not Xorg system do very well if not at all...<ul><li>I had this issue years back on <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener" target="_blank">#UbuntuLTS</a> wirh a <a href="https://infosec.space/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a> (UHD @ 15,6") <a href="https://infosec.space/tags/ThinkPad" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThinkPad</a> <a href="https://infosec.space/tags/P15v" class="mention hashtag" rel="nofollow noopener" target="_blank">#P15v</a> and several medium-DPI 1080p Monitors...</li></ul>

robotalienWhat does it mean when someone says they can "see the pixels on the font" when it comes to a low PPI monitor? They're anti-aliased. That literally does not make any sense. I'm now under the impression every pro <a href="https://mastodon.social/tags/hidpi" class="mention hashtag" rel="nofollow noopener" target="_blank">#hidpi</a> comment on the internet was paid for and pushed by big <a href="https://mastodon.social/tags/monitor" class="mention hashtag" rel="nofollow noopener" target="_blank">#monitor</a>.

robotalienI'm not sure ANYONE has a <a href="https://mastodon.social/tags/hidpi" class="mention hashtag" rel="nofollow noopener" target="_blank">#hidpi</a> <a href="https://mastodon.social/tags/monitor" class="mention hashtag" rel="nofollow noopener" target="_blank">#monitor</a> anymore. I can find stats on screen resolution on Google, but not if it's 1x, 1.5x, or 2x. As far as I'm concerned 2x users do not actually exist. 1px = 1px.Also to be completely honest, I don't know why would anyone want 2x for desktop? Like, pixels are the best thing in the computer?<a href="https://mastodon.social/tags/webdesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdesign</a> <a href="https://mastodon.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a>

robotalienI was wondering how to design for web with hidpi displays because mine is 1x, and I just learned 1.5x is a lie.Alright, then, one less thing to worry about. If my site looks ugly for 1.5x users, it's their fault, not mine. Now I only need to know if I need to care about 2x users...<a href="https://blog.elementary.io/what-is-hidpi/" rel="nofollow noopener" translate="no" target="_blank">https://blog.elementary.io/what-is-hidpi/</a><a href="https://mastodon.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mastodon.social/tags/webdesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdesign</a> <a href="https://mastodon.social/tags/hidpi" class="mention hashtag" rel="nofollow noopener" target="_blank">#hidpi</a>

Thor A. HoplandBut, seeing as my issue is one of <a href="https://snabelen.no/tags/acessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#acessibility</a>, you need only turn on "Accessibility > Seeings > Large Text" under <a href="https://snabelen.no/tags/GNOME" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNOME</a> settings, which does give you the same 1x scaling UI elements, but with bigger text - which... takes some getting used to.I dunno, guys. Larger text, or fractional scaling. Which is best? Mind you, I have a 1080p screen with high pixel density - which is like having the <a href="https://snabelen.no/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a> equivilant of an honourable mention.

PurpleJillybeans :PrideDisk:Early versions of <a href="https://kind.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> (up through the 9x series) had an option for "Large Fonts" in order to make text more legible on <a href="https://kind.social/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a> displays (which, at the time, meant >72 dpi or so), but applications were rarely optimized for it. You'd often end up with labels larger than buttons or text spilling out of controls. Many readme files included a note telling you to use Small Fonts to avoid problems.When it *did* work, though, it looked pretty good.<a href="https://kind.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Rick Wong – Tech & code <a href="https://fosstodon.org/tags/Retina" class="mention hashtag" rel="nofollow noopener" target="_blank">#Retina</a> <a href="https://fosstodon.org/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a> <a href="https://fosstodon.org/tags/P3" class="mention hashtag" rel="nofollow noopener" target="_blank">#P3</a> <a href="https://fosstodon.org/tags/WideGamut" class="mention hashtag" rel="nofollow noopener" target="_blank">#WideGamut</a> screens transformed the way we perceive digital content forever. Crisp texts, vivid colors, deep blacks.I do miss the years when I could look at a screen, and deeply appreciate how artists designed the way their pixels bridged the gap between an imagined world and the real world. Elegant pixel fonts, smooth dithering, skeuomorphic art. Ah the <a href="https://fosstodon.org/tags/nostalgia" class="mention hashtag" rel="nofollow noopener" target="_blank">#nostalgia</a>

aaron ~# :blinkingcursor:Nvm, <a href="https://infosec.exchange/tags/kali" class="mention hashtag" rel="nofollow noopener" target="_blank">#kali</a> has a <a href="https://infosec.exchange/tags/hidpi" class="mention hashtag" rel="nofollow noopener" target="_blank">#hidpi</a> mode. Now it's perfect. Gonna setup my laptop later to be able to connect to it.

John GoerzenIn "A Maze of Twisty Little Pixels, All Tiny" I discuss the state of <a href="https://floss.social/tags/HiDPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HiDPI</a> support in <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>, <a href="https://floss.social/tags/X11" class="mention hashtag" rel="nofollow noopener" target="_blank">#X11</a>, <a href="https://floss.social/tags/Wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wayland</a>, <a href="https://floss.social/tags/Gnome" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gnome</a>, and <a href="https://floss.social/tags/KDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDE</a> <a href="https://floss.social/tags/Plasma" class="mention hashtag" rel="nofollow noopener" target="_blank">#Plasma</a>. I note some bugs in both <a href="https://floss.social/tags/KDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDE</a> and <a href="https://floss.social/tags/Gnome" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gnome</a>, with the more serious ones in <a href="https://floss.social/tags/Gnome" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gnome</a>, and discuss my eventual decision to use <a href="https://floss.social/tags/KDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDE</a> on my HiDPI <a href="https://floss.social/tags/Framework" class="mention hashtag" rel="nofollow noopener" target="_blank">#Framework</a> <a href="https://floss.social/tags/laptop" class="mention hashtag" rel="nofollow noopener" target="_blank">#laptop</a>. I also link to some patches that clear up the little bugs in KDE in this scenario.

Recent searches

Search options

Administered by:

Server stats:

#hidpi