After i wake up the machine when the gizmo was on standby (with Gnome driven by Kernel 5.15.8) the monitor stays black and the only way i figured out till now to get it to run again was to do a half reisub (at r-e, i think, the login interface comes back).
This has been fixed in version 390.147 of the Nvidia driver. I just tested this by downloading and installing libxnvctrl-390xx, nvidia-390xx-utils-390.147-2 from GitLab, and recompiling linux516-nvidia-390xx.147-0.5 against kernel 5.16-rc5 and its headers.
(One thing that looks weird in that process is that you will have to download and extract NVIDIA-Linux-x86_64-390.147-no-compat32.run twice, for both nvidia-390xx-utils-390.147-2, and linux516-nvidia-390xx.147-0.5.)
libxnvctrl-390xx appears to be a new dependency for nvidia-390xx-utils-390.147-2. If there is a conflict with libxnvctrl from a previous driver installation, you will have to remove it. That means answering y to the following question
warning: removing 'libxnvctrl' from target list because it conflicts with 'libxnvctrl-390xx'
:: libxnvctrl-390xx and libxnvctrl are in conflict. Remove libxnvctrl? [y/N]
You can add this to the known issues too.
X Server 21.1.2 breaks suspend/wake on systems with proprietry NVIDIA drivers.
Looks like there is some sort of a fix in the works here: gitlab[dot]freedesktop[dot]org[slash] xorg/xserver/-/merge_requests/829
On my machine, the system goes to sleep, but then wakes up to an unresponsive black screen.
Coincidentally I had the same reisub issueā¦ last week? Except I use KDE Plasma, and after sleep the screen was garbled. R-E recovered to a usable login screen.
However, I have not had issues since the last update or two.
Cannot reproduce here with Xfce under X11 and the 390.147 proprietary Nvidia driver. Looks like this might have something to do with Gnome and/or KDE.
KDE Plasma, by the way, seems to have issues in other distributions as well. For example, I get black squares instead of the icons in KDE Plasma under Q4OS. Changing themes / icon sets does not help.
One thing I notice for quite a while:
On X11, with xfce, the task bar appears on top of the first screen right after system start. It only moves to its configured position at the bottom of the screen when the mouse is hovered over it.
Does anybody experience the same behavior or is it something related to my specific configuration here?
KDE crashes frequently for me with these errors logged
Dec 21 14:02:43 pranay-2700x kwin_x11[1522]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 57928, resource id: 14940866, major code: 2 (ChangeWindowAttributes), minor code: 0
Dec 21 14:02:43 pranay-2700x kwin_x11[1522]: kwin_core: XCB error: 3 (BadWindow), sequence: 57927, resource id: 14940866, major code: 129 (SHAPE), minor code: 6 (Input)
Dec 21 14:02:43 pranay-2700x kwin_x11[1522]: kwin_core: XCB error: 152 (BadDamage), sequence: 57926, resource id: 14940996, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Dec 21 14:02:43 pranay-2700x plasmashell[1576]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:15:1: QML Panel: Binding loop detected for property "state"
Dec 21 14:02:43 pranay-2700x plasmashell[1576]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:15:1: QML Panel: Binding loop detected for property "state"
Dec 21 14:01:27 pranay-2700x kwin_x11[1522]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20361, resource id: 14938122, major code: 2 (ChangeWindowAttributes), minor code: 0
Dec 21 14:01:27 pranay-2700x kwin_x11[1522]: kwin_core: XCB error: 3 (BadWindow), sequence: 20360, resource id: 14938122, major code: 129 (SHAPE), minor code: 6 (Input)
Dec 21 14:01:27 pranay-2700x kwin_x11[1522]: kwin_core: XCB error: 152 (BadDamage), sequence: 20359, resource id: 14938124, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Dec 21 14:01:26 pranay-2700x plasmashell[1576]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:15:1: QML Panel: Binding loop detected for property "state"
Dec 21 14:01:26 pranay-2700x plasmashell[1576]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:15:1: QML Panel: Binding loop detected for property "state"
Dec 21 14:01:11 pranay-2700x plasmashell[1576]: libkcups: Renew-Subscription last error: 0 successful-ok
Dec 21 14:01:09 pranay-2700x kwin_x11[1522]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 18813, resource id: 14938030, major code: 2 (ChangeWindowAttributes), minor code: 0
Dec 21 14:01:09 pranay-2700x kwin_x11[1522]: kwin_core: XCB error: 3 (BadWindow), sequence: 18812, resource id: 14938030, major code: 129 (SHAPE), minor code: 6 (Input)
Dec 21 14:01:09 pranay-2700x kwin_x11[1522]: kwin_core: XCB error: 152 (BadDamage), sequence: 18811, resource id: 14938032, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Dec 21 14:01:09 pranay-2700x plasmashell[1576]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:15:1: QML Panel: Binding loop detected for property "state"
Dec 21 14:01:09 pranay-2700x plasmashell[1576]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:15:1: QML Panel: Binding loop detected for property "state"
Dec 21 14:01:07 pranay-2700x kwin_x11[1522]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 17815, resource id: 14936807, major code: 2 (ChangeWindowAttributes), minor code: 0
Dec 21 14:01:07 pranay-2700x kwin_x11[1522]: kwin_core: XCB error: 3 (BadWindow), sequence: 17814, resource id: 14936807, major code: 129 (SHAPE), minor code: 6 (Input)
Dec 21 14:01:07 pranay-2700x kwin_x11[1522]: kwin_core: XCB error: 152 (BadDamage), sequence: 17813, resource id: 14938005, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Dec 21 14:01:06 pranay-2700x plasmashell[1576]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:15:1: QML Panel: Binding loop detected for property "state"
Dec 21 14:01:06 pranay-2700x plasmashell[1576]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:15:1: QML Panel: Binding loop detected for property "state"
Also I am seeing following error for the first time
[Dec21 13:49] [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
[Dec21 13:50] [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
Maybe you were thinking of pikaur :
pikaur -S $(pacman -Qoq /usr/lib/python3.9) --rebuild
About 24 hours ago I added the following to the wiki post,
and now Iām thinking no-one will notice unless I make a regular post about it.
Itās intended for transfer to the stable update announcement.
Some of the info is from research
(i wonāt actually run all the commands until Python 3.10 is in stable)
so please check that it looks reasonable ā¦
Do 'pip freeze' *before* the update
If you might have installed something via pip,
get this info before the python upgrade,
as thereās no easy way to get it afterwards.
sudo pip freeze > pip_list_sudo.txt
pip freeze --user > pip_list_user.txt
/path/to/<venv_name>/python -m pip freeze -l > pip_list_<venv_name>.txt
After the upgrade, although they say to do something like
sudo pip install -r pip_list_sudo.txt,
look at the lists and consider whether you still want them all.
Itās generally not a good idea to install with pip in the system python,
so look for packages you could install from AUR instead,
and if you still want some pip installs, do: pip install --user
Also, the list from āpip freezeā includes version numbers,
so you might want to manually install afresh to get current versions.
pacman -Qoq /usr/lib/python3.9 is quite different.
If you use it before the update, it will list many packages
that pacman will soon re-install for python 3.10,
so use it after the update, when it will get only AUR packages.
To use it with pikaur:
pikaur -S $(pacman -Qoq /usr/lib/python3.9) --rebuild
1 Like