Yeah, device support is the biggest issue. But the OS as a whole is pretty good. I used it with a OnePlus 6T and a Nothing Phone 1, both of which have pretty decent support. Some things about it were broken, and I didn’t try putting in a SIM card and making calls or texts, but the overall experience was good. I have high hopes for when we eventually get good “flagship” linux mobile phones that have full PostmarketOS compatibility.

Out of curiosity, what about PostmarketOS is not daily driveable? Postmarket is a vague umbrella OS with a lot of DE options, all of which have vastly different user experiences. KDE mobile, phosh, and GNOME mobile have all come a long way and provide everything a smartphone OS needs. The only thing I’d argue that could prevent daily driving is lack of app support and lack of good mobile Linux hardware, but that’s not PostmarketOS’s problem.

And they’re gonna sell to consumers right? And not cash in on the data center bubble right? …right?

Reminds me of the Magi from Neon Genesis Evangelion

I’m highly suspicious that this entire project and even these responses are all AI-generated. Something about the grammar and use of em dashes that really seems fishy to me. And in their first (almost identical) post to this one, someone said that hiding the source code could make people suspicious it’s been authored by AI, and OP responded “what counts as ‘AI-authored’ to you?”. Veeeery sus

As if speaking English would make a difference in them understanding the title

Image reading this title to some 16th century farmer

Yes. Here’s the contents I currently have in /var/lib/gdm/.config/monitors.xml:

<monitors version="2">
  <configuration>
    <layoutmode>physical</layoutmode>
    <logicalmonitor>
      <x>0</x>
      <y>0</y>
      <scale>1</scale>
      <primary>yes</primary>
      <monitor>
        <monitorspec>
          <connector>DP-1</connector>
          <vendor>SAM</vendor>
          <product>Odyssey G93SC</product>
          <serial>HNTW700164</serial>
        </monitorspec>
        <mode>
          <width>5120</width>
          <height>1440</height>
          <rate>239.997</rate>
        </mode>
        <colormode>bt2100</colormode>
      </monitor>
    </logicalmonitor>
    <disabled>
      <monitorspec>
        <connector>HDMI-1</connector>
        <vendor>FUN</vendor>
        <product>Evanlak8K V2</product>
        <serial>0x00006410</serial>
      </monitorspec>
    </disabled>
  </configuration>
</monitors>

The disabled dummy plug is the “Evanlak8K V2” device while my functional monitor is my Samsung Odyssey OLED G9. This config is the same as the one currently running on my GNOME desktop config, but in GDM still defaults to the enabled dummy plug, even with the fixed ownership.

At this point, do you think I should issue a report on GDM’s repository? Maybe the devs there would have more insight

Just checked the ownership of the monitor config, it was gdm:root, so I changed the ownership to gdm:gdm and rebooted. Still facing the same issue.

Didn’t see any error messages in the logs about not being able to load wayland, but just to confirm, I ran loginctl show-session {gdm session id} -p Type which returns Type=wayland, so it’s definitely running under wayland. I have an AMD GPU though so I wouldn’t expect there to be any problems there.

Not seeing anything else weird in the logs that are jumping out as strange to me either, so a bit at a loss here. Any other suggestions?

I had a few Raspberry Pis and some Libre Computer boards a while back, but I recently decided to just build a beefy small form factor PC and put Proxmox on it, and honestly couldn’t be happier with the results. The ability to allocate resources for services and containers on the fly is a game changer. I can spin up a fresh container running whatever service I want in a matter of minutes without the hassle of flashing to a device and setting up networking, etc.