https://bugs.kde.org/show_bug.cgi?id=523824
--- Comment #17 from [email protected] --- Sorry! Somehow missed seeing that when getting the previous info. Also sorry about not initially posting journalctl output inline in comments. I misread "4000 KB" as "4 Kilobytes" lol. Built and installed 2.2.8-dev, then ran the commands again. The new attachments should now reflect this. The journalctl output now shows 2.2.8-DEV as libddcutil version, and this does appear to resolve the crashing! I'm not very familiar with compiling and installing a utility like this over a version already on my system, but I think I eventually figured it out. I did have some trouble at first and ended up running into a lot of problems trying to learn to build an Arch package, but eventually just resorted to editing the **./configure** command during building to mirror what is done by the official PKGBUILD for 2.2.7. To my understanding, this process just directly replaced the files from `ddcutil 2.2.7` under my /usr directory. Would appreciate any confirmation that this is what you intended for me to do, or if I was to go about it differently. Without the **--prefix=/usr** option, 2.2.8-DEV would be installed to /usr/local, and powerdevil would fail to actually use it over the installed 2.2.7 package. Once again, this does appear to no longer result in the crash, so if that is the case then the changes have resolved the issue and we can probably mark this report as such! (Though I would guess that's better to be done after a 2.2.8 release is available, rather than still in development.) For thoroughness, here were the commands issued: ``` git clone https://github.com/rockowitz/ddcutil cd ddcutil ./autogen.sh ./configure --prefix=/usr make sudo make install systemctl restart --user plasma-powerdevil systemctl status --user plasma-powerdevil cd $HOME # Then, after fully connecting the tablet journalctl -b -t org_kde_powerdevil | tee journal-powerdevil-trace-aug21.txt sudo ddcutil interrogate | tee ddcutil-interrogate-aug21.txt ``` One last observation as well is that the tablet display now flickers to a black screen *twice* briefly after being fully connected, as opposed to only flickering *once* as it was doing prior when connected. This is only notable though due to the slight change, and because a different drawing tablet we have doesnt exhibit this behaviour. It doesnt actually cause any noticeable issues or last very long as far as we can tell. The screen flickering also occurs during `sudo ddcutil interrogate`, so I would guess this is normal and expected when connecting and querying certain displays. Felt this is worth mentioning just in case it helps indicates anything more about changes made to the code. -- You are receiving this mail because: You are watching all bug changes.
