I see many error messages like those in my ~/.xsession-errors file: [...] "\"fsrestore1\" - conversion of \"481,481,0,0\" to QRect failed" "\"fsrestore2\" - conversion of \"481,481,0,0\" to QRect failed" "\"fsrestore3\" - conversion of \"481,481,0,0\" to QRect failed" [...] This looks a lot like bug #306898 that was in KDE4. This is with neon packages as of today: Package: plasma-workspace Version: 4:5.5.4+git20160315.1136+15.10-0 Sorry for reporting this to a plasmashell/general, please reassign if necessary. Reproducible: Always
I can confirm this. It seems kwin_x11 is logging this. Next to the 481 one, I also have "\"fsrestore?\" - conversion of \"342,342,0,0\" to QRect failed" with ? in {1,...,9}.
SInce my inital report I upgraded my system to Ubuntu 16.04 and Neon packages: Package: kwin Version: 4:5.6.3+p16.04+git20160426.0359-0 and the error messages are still there.
> I can confirm this. It seems kwin_x11 is logging this. why do you think KWin is logging this? Can you please change the debug pattern to include the actual process?
Reassigning to KConfig. The warning messages are logged by KConfig. See for example: src/core/kconfiggroup.cpp case QMetaType::QRect: { const QList<int> list = asIntList(value); if (list.count() != 4) { qWarning() << errString(pKey, value, aDefault) << formatError(4, list.count()); return aDefault; } Due to the usage of qWarning instead of qCWarning the warnings cannot be silenced and clutter xsession-errors.
(In reply to Martin Gräßlin from comment #3) > > I can confirm this. It seems kwin_x11 is logging this. > > why do you think KWin is logging this? Can you please change the debug > pattern to include the actual process? Sorry, I seem to have missed this comment, but got alerted by comment #4. In any case, if it is still useful: okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed" okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"fsrestore2\" - conversion of \"481,481,0,0\" to QRect failed" okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"fsrestore3\" - conversion of \"481,481,0,0\" to QRect failed" okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"fsrestore4\" - conversion of \"481,481,0,0\" to QRect failed" okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"restore5\" - conversion of \"0,0,0,0\" to QRect failed" okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"fsrestore5\" - conversion of \"0,0,0,0\" to QRect failed" okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"fsrestore6\" - conversion of \"0,0,0,0\" to QRect failed" okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"restore7\" - conversion of \"-4,0,797,0\" to QRect failed" okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"fsrestore7\" - conversion of \"0,0,0,0\" to QRect failed" okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"restore8\" - conversion of \"1010,0,797,0\" to QRect failed" okt 27 18:36:13 <hostname> kwin_x11[2215]: "\"fsrestore8\" - conversion of \"0,0,0,0\" to QRect failed"
This bug is still in neon packages as of version 5.29.0+p16.04+git20161220.1217-0.
This bug still exists in Kubuntu 17.04 and this package version: Package: libkf5configcore5 Version: 5.31.0-0ubuntu1
This bug still exists in Kubuntu 19.04 and this package version: Package: libkf5configcore5 Version: 5.56.0-0ubuntu1