Arch Linux BBS - Applications & Desktop Environments

I found a decent workaround.Configure adaptive sync to be adaptive and then open the app that is 'flickering' (in my case Spectacle). Press ALT+F3 --> More Actions --> Configure Special Window Settings... --> Add property adaptive sync and force off.For me this resolves the issue.

Got the same issue after a recent update.XFCE, element-desktop 1.12.24-1, electron43 43.4.0-1.Not sure if it's related, but at the same time i also started having a problem where clicking on any notification would open Viber (if it's already running) along with whatever program the notification was from.

Hi, I have some new test results.First, I also tested linux-lts (6.18.44-1-lts). The same ~40 secondplasma-plasmashell.service stop timeout can still be reproduced there,so the issue does not seem to be exclusive to the 7.1 kernel series.In my tests it appears to happen less frequently with linux-lts, but Ido not have enough samples to say that this is statistically meaningful.I also tested a systemd user drop-in to keep the audio services orderedbefore plasmashell during startup (and therefore after it during shutdown):[Unit] After=pipewire.service pipewire-media-session.service pulseaudio.serviceI verified that the dependencies were applied. During the next failedshutdown, PipeWire and pipewire-media-session did in fact remain runninguntil after plasmashell hit its 40 second timeout:Stopping KDE Plasma Workspace... ... about 40 seconds ... plasma-plasmashell.service: State 'stop-sigterm' timed out. Killing. plasma-plasmashell.service: Killing process (plasmashell) with signal SIGKILL. plasma-plasmashell.service: Failed with result 'timeout'. Stopped KDE Plasma Workspace. Stopping PipeWire Media Session Manager... Stopped PipeWire Media Session Manager. Stopping PipeWire Multimedia Service... Stopped PipeWire Multimedia Service.So keeping PipeWire alive until plasmashell exits was not enough toprevent the timeout.However, this failed shutdown had another important event which I hadnot noticed before: PulseAudio itself crashed during shutdown.During this ~5 hour session I had used a Bluetooth headset through a USBBluetooth adapter. Later I disconnected the Bluetooth adapter and wentback to using my HyperX headset, which has its own USB wireless receiver(the HyperX itself is not Bluetooth).At shutdown, bluetoothd started terminating and PulseAudio immediatelyaborted inside its BlueZ integration:bluetoothd: Terminating bluetoothd: Stopping SDP server bluetoothd: Exit pulseaudio: Assertion 'pa_atomic_load(&(y)->_ref) > 0' failed at ../pulseaudio/src/modules/bluetooth/bluez5-util.c:2207, function pa_bluetooth_discovery_hook(). Aborting. pulseaudio.service: Main process exited, code=dumped, status=6/ABRT pulseaudio.service: Failed with result 'core-dump'.Immediately after that, Plasma lost its audio objects:plasmashell: context kaput plasmashell: No object for name "alsa_output.usb-HP__Inc_HyperX_Cloud_II_Wireless_0-00.analog-stereo" plasmashell: No object for name "alsa_input.usb-HP__Inc_HyperX_Cloud_II_Wireless_0-00.mono-fallback" qrc:/qt/qml/plasma/applet/org/kde/plasma/volume/main.qml:117: TypeError: Cannot read property 'description' of undefinedThen plasmashell started stopping and remained stuck until systemd killedit 40 seconds later.This makes me wonder whether, at least in this particular occurrence,the "No object for name HyperX..." messages are a consequence of thePulseAudio server crashing rather than the HyperX USB device itself beingthe original cause.There is also a Bluetooth-related clue from earlier in that same session:when the Bluetooth device disappeared, both kded6 and plasmashell loggedthat a bluez_sink object no longer existed. The desktop continued workingnormally afterwards.As a control test, I then used the system for about 3 hours without usingBluetooth at all and ran:sudo rebootThat reboot completed normally with no 40 second delay.I need to repeat this several more times before drawing any conclusion,but Bluetooth / BlueZ / hot-unplug now looks like a possible trigger forat least some occurrences.One important caveat: I have previously reproduced the same 40 secondplasmashell timeout while using pipewire-pulse + WirePlumber instead ofthe real PulseAudio server. Therefore the PulseAudio assertion abovecannot by itself explain the entire history of the issue.At this point my observations are roughly:- the issue reproduces on both linux and linux-lts;- manually stopping plasma-plasmashell.service before shutdown is fast;- keeping PipeWire alive until after plasmashell stops does not eliminate  the timeout;- in this latest failed shutdown, PulseAudio crashed in  pa_bluetooth_discovery_hook() immediately before Plasma lost the audio  objects and plasmashell became stuck;- a subsequent ~3 hour session with no Bluetooth use rebooted normally.Would the PulseAudio assertion in bluez5-util.c be useful for narrowingthis down further?I can also post a sanitized clean journal from this failed boot if thatwould help.

kokoko3k wrote:I don't think hplip has manual duplex wizardsI doubt hplip supports that.However there are hp printers where a hardware duplex unit is optional and if it's absent the printer can switch to manual duplex.In order to activate that option you have to access the printer directly. Typically that's done by connecting with the printer admin interface over the network, but with an usb connected printer that can be done through the proprietary plugin.Cups / sane and similar support such connections IF the plugin is present. Windows tends to have the plugin integrated in the printer driver.

Welp just found out there is an update to firmware after this post (I literally just updated last night). Aaand it's solved after an update & reboot.

Minor update, I've found and fixed a bug with non-composite thermal meters.The problem was, when a thermal sensor went above the threshold all subsequent normal sensors showed the same alert as well. Now the alert icon is cleared in each iteration.

https://archlinux.org/packages/extra/x86_64/qt6-svg/ lists gambas3 as needing it as a makedepend .gambas3-gb-web-gui also lists qt6-svg as a makedepend , maybe that needs to be changed to a runtime depend ?

I have umask 077 as default umask. user can't read the folder and file after creating them. I had to give the right permissionssudo chmod 755 org.gnome.Shell@.service.d org.gnome.Shell@user.service.d sudo chmod 644 org.gnome.Shell@.service.d org.gnome.Shell@user.service.d/override.conf$ systemctl status --user 'org.gnome.Shell@user.service' ● org.gnome.Shell@user.service - GNOME Shell Loaded: loaded (/usr/lib/systemd/user/org.gnome.Shell@.service; static) Drop-In: /etc/systemd/user/org.gnome.Shell@user.service.d └─override.conf

This may help https://wiki.archlinux.org/title/Activa … _on_bootup

Run thunderbird via systemd user unit and use:TemporaryFileSystem=/home/username/Thunderbird

Thanks for the update.Is it actually fixed?I'm on 6.7.4 now and when trying to drag an icon around in the Quicklaunch popup menu/list no 'insert' line appears and letting the icon go it just stays where it was.

Moderator NoteClosing this thread now.If mt_arch_user wants to respond, they should use the report button on this post and request re-opening.

I has similar issue I solved by using sddm-conf-git aur packageI just filled the info as you write the autologin.conf file and after hitting save it was working again.

Ah dang, yes. I unfortunately didn't think of keeping it to inspect it. It's possible that some Qt app I ran did generate bogus entries in this file. Next time it happens, i'll think of keeping it. This file growing to 67 MB was definitely not normal.I just remember than I ran one Qt app that I don't run very often and that I noticed the issue some time after that, not sure it is related but it gives me something to investigate. This app is QCAD ( https://archlinux.org/packages/extra/x86_64/qcad/ ) and it tends to crash quite a bit, especially upon exit, so this is a suspect.

Just from the spots where it crashes reinstall minimally kirigami and libplasma.But to get a better view of the nature of the issue sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files' | grep -v backup > /tmp/howbadisit.txt cat /tmp/howbadisit.txt | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/' post the link you get.Since a new user is apparently fine, maybe also some config, that will be a bit harder to properly evaluate, if you're lucky just some cache in case removing .cache/plasmashell of the affected user might already help.In general try to avoid power buttoning, if the crash is just the GPU or so there are ways to fairly safely reboot, so if you potentially envision running into such a situation more often, consider https://wiki.archlinux.org/title/Keyboa … el_(SysRq) and the REISUB sequence (though this has to be explicitly enabled first)