this post was submitted on 07 Jul 2026
10 points (91.7% liked)

Linux

18164 readers
92 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 3 years ago
MODERATORS
MigratingtoLemmy@lemmy.world
10
Zorin Blues (lemmy.world)
submitted 2 days ago by zanzo@lemmy.world to c/linux@lemmy.world
11 comments fedilink hide all child comments
 

Looking for advice on what I suspect is a driver issue with Zorin Linux.

For a few months, I've had issues with suspend, where the computer will wake, but the screen remains black. This happens both when the computer suspends on its own and when I suspend it manually.

Worse, when I force reboot the computer:

  1. only one of my monitors lights up
  2. my keyboard is unresponsive.
  3. Mouse still works.
  4. Internet also dies.

Both monitors are connected to an Nvidia GTX 1070 GPU. The keyboard and mouse are connected via USB.

What I've tired

  • I've used the Accessibility Keyboard (screen keyboard) to log in after a restart and revert to a previous state using Timeshift. This will get the keyboard, Internet and screen to work, but the moment I suspend, the problem returns.

  • I did notice this issue started once I updated my GPU drivers to Nvidia ones (I've tried a couple).

I tried reverting to the Nouveau driver, but the problem returned.

I should probably note that when I orginally tried to install Zorin with Nvidia drivers, the install failed.

Advice

I'm looking for ideas on how to proceed.

At this point, I could start over completely with a fresh install of Zorin.

I could revert to the earliest Timeshift image I have, which would put me back to a fresh install.

I could abandon Zorin for another distro.

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world 1 points 2 days ago (1 children)

What kernel and Nvidia driver versions are you on?

Also, just download any Live USB and see if you get the same suspend issues to test it out. Dmesg output would also be useful right after the problem happens.

[–] zanzo@lemmy.world 1 points 2 days ago (1 children)

Kernal 16.17x. I forget what driver is on there now, but it's around 580x.

I did a clean install early on after updating to the Nvidia drivers killed my Linux install the first time. I was fine for about a week and then things crashed again.

For some reason, I can't get dmesg to do anything. I did run journalctrl -b -p err and I got a few error messages. see below.

These look like they occurred during boot. I ran these through AI and it responded that Most likely causes:

GNOME/GDM packages are broken or partially installed Your user runtime/session is failing Bad permissions in your home folder Display driver issue causing GNOME session startup failure Leftover damage from previous repair/driver changes

Jul 07 13:58:14 host gdm3[3615]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISP> Jul 07 13:58:42 host gdm-password] [4192]: gkr-pam: unable to locate daemon control fi> Jul 07 13:58:42 host qdm3[3615]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISP> Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkc> Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-gnome\x2dkeyring\x2dsec> Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh> Jul 07 13:58:43 Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-user\x2ddirs\x2dupdate> Jul 07 13:59:14 host qdm3[3615]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DI>

Jul 07 13:57:52 host thermald[1110]: Thermal DTS or hwmon: No Zones present Need to c>

host systemd[4203]: Failed to start app-gnome-im\x2dlaunch-4737.scope>

[–] just_another_person@lemmy.world 1 points 1 day ago (1 children)

Let me make sure you performed the Nvidia driver install in this order:

  1. Uninstall clear any old drivers and modules
  2. Install drivers
  3. Blacklist nouveau driver to prevent race condition loading
  4. Reboot machine
  5. Run nvidia-smi to ensure everything loaded correctly

All of that sound about right?

[–] zanzo@lemmy.world 1 points 1 day ago

I can't recall but I may have followed a similar process before, but I'll go through that once again.