After zypper dup in TW for 2082 packages today, machine does not revive from suspend?

[non_space]

No worries . . . this is now an “open chat” . . . so it’s just for “background” discussion. Your post is indicating that “the problem” is also hitting newer hardware, not just my “legacy” unit . . . . So that was useful information . . . not trolling . . . .

[kinu]

@non_space

So you said, “WM” . . . but do you really mean “DM”??? It is fairly easy in TW to add DEs, but then apparently they can’t be removed . . . . I added perhaps GNOME or KDE to get another DM option, but in my case the only one to work . . . after the apparent changes to SDDM were made . . . is LightDM.

No no, I’m exploring if is it possible to change kwin for another windows manager, like openbox or something, and continue using Plasma Desktop… because maybe es kwin as compositor who is causing the black screen + mouse error after suspend.

I’d like to know if this is possible.

By the way, I’m using X11 Plasma in an Arch Linux installation and the bug is not hitting this computer, but I don’t have Nvidia here, so …

EDIT: It is possible! KDE - ArchWiki

I will try it tonight.

[non_space]

Feature request for “Debian-like” notifications for changes in packages while running zypper dup has been filed. There was no option to select for filing against zypper . . . so I picked YaST2 as the option.

https://bugzilla.opensuse.org/show_bug.cgi?id=1241118

[non_space]

Zypper dup brings new 6.14.1-1 kernel this morning, rebooted into it . . . suspended it. On resuming from suspend this kernel provided the fastest response of any of the recent kernels, even back to the 6.12.6 that is now the default kernel for TW.

I was hopeful. However on suspending a second time, resume brought no display function.

Some of the recent iterations would bring two or three revivals . . . but not so much in the 6.14 xxx series.

[mrmazda]

Lotsa hits on Google with following search:

suspend fails forums linux -windows
in "search tools" *past month*

You may be looking for a solution that will never come except via a fresh installation. Likely in your particular hardware/software combination there is a unique bug that may never be identified, much less fixed.

From private email I got the following from a developer:

basically all x server development has stopped, but all x11 development now goes into xwayland server.

originally x.org and xwayland had very similar version numbers, now they are drifting apart, which is what is going to push people in the end to wayland, too many unfixed bugs in xorg, aka, bit rot.

… since wayland detection is very fragile, and fails totally out of gui, or in root, inxi can never know it’s wayland beyond a compositor being active.

For most desktop users it will get this right most of the time.

Note that because distros have despite their pretending, not actually switched to wayland, they are shipping with:

x.org server (plus possible x11 compositor) AND xwayland plus wayland compositor

It was not supported to be AND, it was supposed to be OR, but wayland has been fumbled so badly over years that distros just gave up and now ship both possible combinations.

[karlmistelberger]

@non_space

I was hopeful. However on suspending a second time, resume brought no display function.

Intel WiFi (ax210) not coming out of deep sleep state

Problems related to sleep/resume regularly occur with any hardware at any time. Users are indeed best off with unloading and loading again modules causing the trouble. A “Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a)” worked fine until upgrading to kernel 6.11. No scripting needed. The following lines in the dropin file fix the issue: # /etc/systemd/system/systemd-suspend.service.d/override.conf [Service] ExecStartPre=/usr/sbin/rmmod iwlmvm iwlwifi ExecStartPo…

[non_space]

@mrmazda

You may be looking for a solution that will never come except via a fresh installation. Likely in your particular hardware/software combination there is a unique bug that may never be identified, much less fixed.

Indeed. Well, I did a fresh install of TW a few weeks back . . . did not provide the avenue for running newer kernels in TW . . . .

[non_space]

Looks like Launchpad is doing housecleaning on old bug reports, here’s one I filed in 2019, looks like at that time TW was ahead of the curve on it:

You received this bug notification because you are subscribed to the bug
report.

Bug #1890211 “5.8 kernel appears to break video in two groovy in...” : Bugs :...

Title:
5.8 kernel appears to break video in two groovy installs

Status in linux package in Ubuntu:
Expired

Bug description:
Ran apt to update/upgrade in both of my groovy distros, Lubuntu &
U-MATE 20.10 . . . on reboot not only was my grub list broken in both
cases but seemingly the update to the new 5.8.0-12 kernel shows splash
logo, but “logs” to a black screen. Display power light is “on” but
screen is black.

I repeated this several times in both systems . . . having to boot
using SG2 to another distro to repair grub . . . then after I did that
I got to grub list and went to “advanced options” and rolled back to
the prior 5.4.0-42 kernel . . . and GUI is operational.

I believe in TW I am running 5.7 kernel and that system has video. I
have an Nvidia card and I’m using “nouveau” as my driver.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu43
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: non-space2 1665 F… pulseaudio
/dev/snd/controlC0: non-space2 1665 F… pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: LXQt
Date: Mon Aug 3 15:45:08 2020
InstallationDate: Installed on 2019-06-17 (413 days ago)
InstallationMedia: Lubuntu 19.04 “Disco Dingo” - Release amd64 (20190416)

[non_space]

Late in the day yesterday I did find the everymac graphics card page that listed an upgrade option for the Mac Pro 5,1 back in the day that is a Radeon card. I’ll have to check it today to see if that card is “metal” friendly . . . and if so, try to find one that is “Mac” friendly . . . .

I’m not quite ready to buy or build a new desktop just yet, so a card will punt that decision down the road a bit . . . hopefully.