Re: Re: QT target version for trixie
I appreciate the advice to target Qt 6 when possible. I'd like to switch Digikam from Qt5 to Qt6. Is there a guide to replacing package names? For example, Digikam builds with qtbase5-dev. I can't find qtbase6-dev in the archive. Am I overlooking something? Thanks, -Steve signature.asc Description: This is a digitally signed message part.
Re: akonadi database creating 300MB+ log message per day
On Saturday, July 1, 2023 1:17:56 P.M. CDT Steven Robbins wrote: > I'm seeing odd behaviour but not sure where the fault lies -- it is perhaps > some configuration issue on my part -- so asking here before filing a bug. > > The file ~/.local/share/akonadi/db_data/mysql.err is being spammed by error > logs many times per minute: I have since learned that it is kmail that is using the database: each time I click on a message, about 30 log lines are generated. Also, I should have specified that I'm running Debian unstable. -Steve signature.asc Description: This is a digitally signed message part.
akonadi database creating 300MB+ log message per day
I'm seeing odd behaviour but not sure where the fault lies -- it is perhaps
some configuration issue on my part -- so asking here before filing a bug.
The file ~/.local/share/akonadi/db_data/mysql.err is being spammed by error
logs many times per minute:
2023-07-01 13:06:27 256 [ERROR] Incorrect definition of table
mysql.column_stats: expected column 'histogram' at position 10 to have type
longblob, found type varbinary(255).
2023-07-01 13:06:27 256 [ERROR] Incorrect definition of table
mysql.column_stats: expected column 'hist_type' at position 9 to have type
enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type
enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
It's accruing at the rate of several hundred MB per day. I believe it's been
going on for quite some time, because the mysql.err.old file was 35 GB by the
time I caught it.
When I search this string in google, I get lots of hits from the recent past
to many years ago that all commonly suggest that an upgrade has gone wrong.
Most of these actually deal with docker containers, but since my log file is
under akonadi I think docker is not the problem. As a test, I did shut down
docker completely and the logs still kept coming.
A typical recommendation [1] is to run "mysql_upgrade" by hand. However,
doing so gives another interesting error:
$ mysql_upgrade
Reading datadir from the MariaDB server failed. Got the following error when
executing the 'mysql' command line client
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/
mysqld.sock' (2)
FATAL ERROR: Upgrade failed
In fact, the directory "/run/mysqld" doesn't even exist on the machine:
$ ls -l /run/mysqld
ls: cannot access '/run/mysqld': No such file or directory
Is this a broken config here??
Any advice gratefully accepted.
Thanks,
-Steve
[1]
https://techoverflow.net/2022/06/07/how-to-fix-docker-mariadb-correct-definition-of-table-mysql-column_stats-expected-column-hist_type-at-position-9/
signature.asc
Description: This is a digitally signed message part.
Bug#1031953: libkf5screen8: Second monitor issues with NVIDIA
On Saturday, February 25, 2023 3:57:45 P.M. CST you wrote: > Please don’t. I plan to upload the whole of Plasma 5.27.2 targeting > bookworm. Awesome, thanks! > But please do follow-up on this and if the patch doesn’t make into the > 5.27.2 upstream release you’re welcome to report it here so we can apply > the fix on top of that release. Yep, I'll re-test and update/close the bug once 5.27.2 hits me. Best -Steve signature.asc Description: This is a digitally signed message part.
Re: qtav: FTBFS with ffmpeg 5.0
Heads up for those following this bug: qtav appears to be unmaintained upstream. My only interest in the package was to enable video playback in digikam. Digikam upstream has taken most of the qtav code, incorporated into digikam source tree and fixed it up. The next release of digikam will not need qtav and therefore I will no longer be maintaining qtav. The only other usage in Debian I can find is "matrix-mirage" (which is itself orphaned). My suggestion is to simply remove qtav from Debian. If you do need qtav for some other purpose, please respond here and consider yourself the new maintainer. Best, -Steve signature.asc Description: This is a digitally signed message part.
kdevelop cannot run lldb-mi
Hello, I'm trying to debug within KDevelop. When I select to debug a binary, KDevelop shows a big error message "Could not start debugger. Could not run 'lldb-mi'. Make sure that the path name is specified correctly". I can manually configure to use GDB instead of LLDB. But supposing I want to use LLDB -- what do I need to do? Oddly: the llvm-toolchain-nn changelog states that "lldb-mi" was removed in August 2019. But if so: why does KDevelop continue to use it? Elsewhere on the web, I can see that others are still using lldb-mi [1] -- is the removal a Debian thing? If so, what is the Debian thing needed for kdevelop? Thanks! -Steve [1] https://www.reddit.com/r/kde/comments/rfiwh4/ kdevelop_debug_could_not_run_lldbmi/ - signature.asc Description: This is a digitally signed message part.
qtpaths -- is it expected to work?
Hi,
I'm maintaining digikam for Debian and -- due to ffmpeg issues -- trying to
help out with upstream development. The digikam setup script uses the
commands:
QT_INSTALL_PREFIX=`qtpaths --install-prefix`
QT_PLUGIN_INSTALL_DIR=`qtpaths --plugin-dir`
Currently both fail (on Debian unstable) with:
qtpaths: could not find a Qt installation of ''
In light of Bug #1011935 ("QtChooser is dead by choice upstream, no Qt6
Support"), I'm unsure if this is expected to work or not.
It looks like qtchooser does know about the versions installed:
$ qtchooser --list-versions
4
5
default
qt4-x86_64-linux-gnu
qt4
qt5-x86_64-linux-gnu
qt5
I thought I might be able to force a selection using the QT_SELECT variable,
but it just changes to a different error:
$ QT_SELECT=qt5 qtpaths --install-prefix
qtpaths: could not exec '/usr/lib/qt5/bin/qtpaths': No such file or directory
Thanks,
-Steve
P.S. Direct replies appreciated, not subscribed to debian-qt-kde.
signature.asc
Description: This is a digitally signed message part.
Handling symbols file
Hi, I've uploaded exiv2 to experimental and many builds failed due to changed symbols. Is this the up-to-date explanation for symbols files: https://qt-kde-team.pages.debian.net/symbolfiles.html ? I don't see explicit details on what to do with all the architecture-specific diff files. Help! Thanks, -Steve signature.asc Description: This is a digitally signed message part.
