I think --rebuild option is needed in order to force rebuild packages with the same version, otherwise they are just reinstalled without rebuilding.
My wired mouse doesn’t work. It shows up in lsusb but there’s no input (movement or click).
I tested the mouse in another computer and it’s fine. Also tested a wireless mouse and that one works. I would appreciate any help since I can’t find anything.
I think I should add I’m on XFCE.
Edit: It’s only this mouse, it’s not the USB port.
See man yay:
--answerclean <All|None|Installed|NotInstalled|...> Set a predetermined answer for the clean build menu question. This answer will be used instead of reading from standard input but will be parsed exactly the same.
Kernel 5.16-rc5 seems to have some issues, apparently with memory management, on machines with only 8 GB RAM:
#2 0x00007f43050472ac _ZN4base17ConditionVariable9TimedWaitERKNS_9TimeDeltaE (libbase.so + 0x2272ac)
#3 0x00007f4305047c96 _ZN4base13WaitableEvent9TimedWaitERKNS_9TimeDeltaE (libbase.so + 0x227c96)
#4 0x00007f4305011cf4 _ZN4base8internal12WorkerThread8Delegate11WaitForWorkEPNS_13WaitableEventE (libbase.so + >
#5 0x00007f430501295a _ZN4base8internal12WorkerThread9RunWorkerEv (libbase.so + 0x1f295a)
#6 0x00007f430501249e _ZN4base8internal12WorkerThread15RunPooledWorkerEv (libbase.so + 0x1f249e)
#7 0x00007f430504b6dc n/a (libbase.so + 0x22b6dc)
#8 0x00007f42f5c8a259 start_thread (libpthread.so.0 + 0x9259)
#9 0x00007f42f56735e3 __clone (libc.so.6 + 0xfe5e3)
Stack trace of thread 9300:
#0 0x00007f42f5c968ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)
#1 0x00007f42f5c90574 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf574)
#2 0x00007f43050472ac _ZN4base17ConditionVariable9TimedWaitERKNS_9TimeDeltaE (libbase.so + 0x2272ac)
#3 0x00007f4305047c96 _ZN4base13WaitableEvent9TimedWaitERKNS_9TimeDeltaE (libbase.so + 0x227c96)
#4 0x00007f4305011cf4 _ZN4base8internal12WorkerThread8Delegate11WaitForWorkEPNS_13WaitableEventE (libbase.so + >
#5 0x00007f430501295a _ZN4base8internal12WorkerThread9RunWorkerEv (libbase.so + 0x1f295a)
#6 0x00007f430501249e _ZN4base8internal12WorkerThread15RunPooledWorkerEv (libbase.so + 0x1f249e)
#7 0x00007f430504b6dc n/a (libbase.so + 0x22b6dc)
#8 0x00007f42f5c8a259 start_thread (libpthread.so.0 + 0x9259)
#9 0x00007f42f56735e3 __clone (libc.so.6 + 0xfe5e3)
Stack trace of thread 9315:
#0 0x00007f42f567392e epoll_wait (libc.so.6 + 0xfe92e)
#1 0x00007f43050bfec6 n/a (libbase.so + 0x29fec6)
#2 0x00007f43050bd699 n/a (libbase.so + 0x29d699)
#3 0x00007f430508286c _ZN4base19MessagePumpLibevent3RunEPNS_11MessagePump8DelegateE (libbase.so + 0x26286c)
#4 0x00007f4304ffc142 _ZN4base16sequence_manager8internal35ThreadControllerWithMessagePumpImpl3RunEbNS_9TimeDel>
#5 0x00007f4304fb8a11 _ZN4base7RunLoop3RunERKNS_8LocationE (libbase.so + 0x198a11)
#6 0x00007f430501d52b _ZN4base6Thread3RunEPNS_7RunLoopE (libbase.so + 0x1fd52b)
#7 0x00007f430501d6e1 _ZN4base6Thread10ThreadMainEv (libbase.so + 0x1fd6e1)
#8 0x00007f430504b6dc n/a (libbase.so + 0x22b6dc)
#9 0x00007f42f5c8a259 start_thread (libpthread.so.0 + 0x9259)
#10 0x00007f42f56735e3 __clone (libc.so.6 + 0xfe5e3)
Stack trace of thread 9523:
#0 0x00007f42f566e18d syscall (libc.so.6 + 0xf918d)
#1 0x00007f42f5bedbbb g_cond_wait_until (libglib-2.0.so.0 + 0xa2bbb)
#2 0x00007f42f5b6e7d3 n/a (libglib-2.0.so.0 + 0x237d3)
#3 0x00007f42f5b6e964 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x23964)
#4 0x00007f42f5bd096a n/a (libglib-2.0.so.0 + 0x8596a)
#5 0x00007f42f5bcdce1 n/a (libglib-2.0.so.0 + 0x82ce1)
#6 0x00007f42f5c8a259 start_thread (libpthread.so.0 + 0x9259)
#7 0x00007f42f56735e3 __clone (libc.so.6 + 0xfe5e3)
As these errors do not seem to occur when using kernel 5.15.7, I assume that the 5.16-rc5 kernel is at fault here:
After having started chromium-dev the first time, it crashes as soon as it receives any keyboard input. Subsequent starts turn out to be successful (at least no immediate crashes upon keyboard input).
I think --rebuild forces yay to ignore previously built packages from cache. Without it cached package is installed. See man yay:
--rebuild
Always build target packages even when a copy is available in cache.
--norebuild
When building packages if the package is found in cache and is an equal version to the one wanted skip the package build and use the existing package.
update done , and nvidia drivers is ok
something wrong on side Archlinux
With the 2 latest updates CUPS is not working anymore. I can search and install network printers but the print job stops with “Der Drucker »EPSON-WF4830.local« kann nicht lokalisiert werden.” (Printer cannot be localized).
I found his resolved does not answer with NXDOMAIN to local queries when mDNS is disabled as a possible issue. My systemd version shows systemd 249 (249.7-2-manjaro) compared to systemd 249 (249.7-2-arch) from the bug report.
I’m still trying to get the printer back online.
After this python update, skype-web-jak does not launch anymore:
$ skype-web
JAK v3.5.6
PyQt5 Bindings
Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.
Production Mode On, use (--dev) for debugging
NVIDIA detected:Known bug - kernel rejected pushbuf
Falling back to Software Rendering
Attribute Qt::AA_UseSoftwareOpenGL must be set before QCoreApplication is created.
Engine online IPC and Bridge Disabled
Cookies PATH:/home/chainofflowers/.jak/microsoft
Use of deprecated not thread-safe setter, use setUrlRequestInterceptor instead.
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.15.7 Chrome/87.0.4280.144 Safari/537.36
Loading URL:https://web.skype.com
Registering ['view'] Instance
icon not found: None
loading default icon:
Registering and Retrieving ['win'] Instance
Traceback (most recent call last):
File "/usr/bin/skype-web", line 32, in <module>
skype().run()
File "/usr/lib/python3.10/site-packages/JAK/Application.py", line 137, in run
win.resize(win.default_size("width"), win.default_size("height"))
TypeError: arguments did not match any overloaded call:
resize(self, QSize): argument 1 has unexpected type 'float'
resize(self, int, int): argument 1 has unexpected type 'float'
I was able to get the printer online again with a manually configured IPP connection directly in CUPS:
ipp://192.168.0.11/ipp/print?waitjob=false&waitprinter=false
The connection with IPP over DNS-SD in the KDE control center is still not working.
1 Like
Received an update today with a new nsswitch.conf and now the printer also works with DNS-SD: dnssd://EPSON%20WF-4830%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4-a45f-50579ce0f7b6
Thanks for the bugfix!
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