Problem reports for k...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|239108 | databases/akonadi: Builds and links against datab New |237423 | www/qt5-webengine: enable video capture device im 2 problems total for which you should take action.
Re: switching users
On Mon, 2019-07-08 at 11:55 +0300, Andriy Gapon wrote: > Does user switching work for anybody? > Is there any additional configuration needed to get it working? > > It does not work for me at all. When I click "Start New Session" I > am taken > back to the unlock screen for a current user. > This is with the latest plasma 5.16.2. I haven't tried to reproduce this myself, but I've filed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241231 to keep track of this.
maintainer-feedback requested: [Bug 241231] security/plasma5-kscreenlocker: "Start New Session" does not work
Bugzilla Automation has asked k...@freebsd.org for maintainer-feedback: Bug 241231: security/plasma5-kscreenlocker: "Start New Session" does not work https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241231 --- Description --- avg@ reports to the mailing list (https://mail.kde.org/pipermail/kde-freebsd/2019-July/031951.html): > Does user switching work for anybody? > Is there any additional configuration needed to get it working? > > It does not work for me at all. When I click "Start New Session" I am taken back to the unlock screen for a current user. > This is with the latest plasma 5.16.2. I haven't tested this with 5.16.5, but I guess it's still broken.
[Bug 241231] security/plasma5-kscreenlocker: "Start New Session" does not work
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241231 Bug ID: 241231 Summary: security/plasma5-kscreenlocker: "Start New Session" does not work Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: k...@freebsd.org Reporter: rak...@freebsd.org Flags: maintainer-feedback?(k...@freebsd.org) avg@ reports to the mailing list (https://mail.kde.org/pipermail/kde-freebsd/2019-July/031951.html): > Does user switching work for anybody? > Is there any additional configuration needed to get it working? > > It does not work for me at all. When I click "Start New Session" I am taken back to the unlock screen for a current user. > This is with the latest plasma 5.16.2. I haven't tested this with 5.16.5, but I guess it's still broken. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 241227] ports-mgmt/portmaster: When installing/reinstalling/upgrading devel/cmake portmaster always reinstall textproc/py-sphinx even if it is up to date
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241227 Raphael Kubo da Costa changed: What|Removed |Added Assignee|ports-b...@freebsd.org |s...@freebsd.org --- Comment #1 from Raphael Kubo da Costa --- This looks like an issue in portmaster, tentatively assigning to the port maintainer. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 240343] x11-themes/plasma5-breeze-gtk: Fails to build if lang/python37 is installed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240343 --- Comment #15 from Raphael Kubo da Costa --- (In reply to Kubilay Kocak from comment #13) > This issue is very likely going to hit other ports that use cmake. In this case, isn't it better to always add this to CMAKE_ARGS in Uses/python.mk? I see that there's something there that seems to attempt to work around the same issue. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 241227] ports-mgmt/portmaster: When installing/reinstalling/upgrading devel/cmake portmaster always reinstall textproc/py-sphinx even if it is up to date
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241227 Bug ID: 241227 Summary: ports-mgmt/portmaster: When installing/reinstalling/upgrading devel/cmake portmaster always reinstall textproc/py-sphinx even if it is up to date Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-b...@freebsd.org Reporter: y...@utahime.org CC: k...@freebsd.org, pyt...@freebsd.org, s...@freebsd.org CC: k...@freebsd.org, pyt...@freebsd.org, s...@freebsd.org When installing/reinstalling/upgrading devel/cmake portmaster always reinstall textproc/py-sphinx even if it is up to date. -- root@rolling-vm-freebsd1[2001]# portmaster cmake-3.15.4 ~ ===>>> Currently installed version: cmake-3.15.4 ===>>> Port directory: /net/freebsd/ports/head/devel/cmake ===>>> Launching 'make checksum' for devel/cmake in background ===>>> Gathering dependency list for devel/cmake from ports ===>>> Launching child to install textproc/py-sphinx ===>>> cmake-3.15.4 >> textproc/py-sphinx (1/1) ===>>> Currently installed version: py37-sphinx-1.6.5_2,1 ===>>> Port directory: /net/freebsd/ports/head/textproc/py-sphinx ===>>> Launching 'make checksum' for textproc/py-sphinx in background ===>>> Gathering dependency list for textproc/py-sphinx from ports ===>>> Initial dependency check complete for textproc/py-sphinx ===>>> Continuing initial dependency check for devel/cmake ===>>> Initial dependency check complete for devel/cmake ===>>> cmake-3.15.4 >> (1) ===>>> The following actions will be taken if you choose to proceed: Re-install cmake-3.15.4 Re-install py37-sphinx-1.6.5_2,1 ===>>> Proceed? y/n [y] n ===>>> If you would like to upgrade or install some, but not all of the above try adding '-i' to the command line. root@rolling-vm-freebsd1[2002]# -- -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 240343] x11-themes/plasma5-breeze-gtk: Fails to build if lang/python37 is installed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240343 --- Comment #14 from commit-h...@freebsd.org --- A commit references this bug: Author: rakuco Date: Sun Oct 13 15:08:32 UTC 2019 New revision: 514401 URL: https://svnweb.freebsd.org/changeset/ports/514401 Log: Add USES=gnome. Fix a DEV_WARNING, we were setting USE_GNOME without setting USES=gnome. This is part of the patch in bug 240343. PR: 240343 Submitted by: Ting-Wei Lan Changes: head/x11-themes/plasma5-breeze-gtk/Makefile -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 237934] [patch] astro/libkgeomap remove dependency to graphics/opencv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237934 Raphael Kubo da Costa changed: What|Removed |Added Resolution|--- |FIXED Status|New |Closed --- Comment #2 from Raphael Kubo da Costa --- Committed, thank you very much for the patch. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 237934] [patch] astro/libkgeomap remove dependency to graphics/opencv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237934 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: rakuco Date: Sun Oct 13 14:18:07 UTC 2019 New revision: 514393 URL: https://svnweb.freebsd.org/changeset/ports/514393 Log: Drop dependency on graphics/opencv. The source code does not use OpenCV anywhere, and apparently never has. PR: 237934 Submitted by: Hiroo Ono Changes: head/astro/libkgeomap/Makefile -- You are receiving this mail because: You are the assignee for the bug.
[Bug 237934] [patch] astro/libkgeomap remove dependency to graphics/opencv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237934 Raphael Kubo da Costa changed: What|Removed |Added Assignee|ports-b...@freebsd.org |k...@freebsd.org CC|k...@freebsd.org | -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 228640] net-im/kopete fails to build with lld as the system linker due to duplicate symbols
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228640 --- Comment #8 from commit-h...@freebsd.org --- A commit references this bug: Author: rakuco Date: Sun Oct 13 14:04:02 UTC 2019 New revision: 514392 URL: https://svnweb.freebsd.org/changeset/ports/514392 Log: Drop LLD_UNSAFE=yes. The port is building fine on 12.0 and HEAD without setting this. The port's build system is still wrong (i.e. the port still builds the same moc-generate code in duplicate files), but lld seems to handle this case well. A proper fix was sent upstream in https://phabricator.kde.org/D24609. I am not bumping PORTREVISION because this only changes build dependencies. PR: 228640 Changes: head/net-im/kopete/Makefile -- You are receiving this mail because: You are the assignee for the bug.
[Bug 228640] net-im/kopete fails to build with lld as the system linker due to duplicate symbols
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228640 Raphael Kubo da Costa changed: What|Removed |Added CC||rak...@freebsd.org --- Comment #7 from Raphael Kubo da Costa --- I've sent https://phabricator.kde.org/D24609 upstream, and will just remove LLD_UNSAFE=yes in the port for now. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 228640] net-im/kopete fails to build with lld as the system linker due to duplicate symbols
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228640 --- Comment #6 from Ed Maste --- (In reply to Raphael Kubo da Costa from comment #5) > I guess lld has gotten smarter since this bug was filed? Or the original problem was just lld being more strict about a bug which has since been fixed upstream. In any case if it now builds with lld the LLD_UNSAFE can be removed. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 228640] net-im/kopete fails to build with lld as the system linker due to duplicate symbols
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228640 --- Comment #5 from Raphael Kubo da Costa --- Kopete's build system is still "broken" in the sense that some files rely on automated moc processing by including "foo.moc" in the source code, and some do not, so the build system also relies on QT_WRAP_CPP() to process some additional files, so we end up with the moc-generated code in both moc_foo.cxx and mocs_compilation.cpp (which contains moc-generate code not included directly by any source files). However, I've just tried building without LLD_UNSAFE=yes on 12.0 and HEAD and both worked fine. I guess lld has gotten smarter since this bug was filed? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 239023] [exp-run] Update pyqt to 5.13.0 (with it sip to 4.19.18 and qscintilla to 2.11.2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239023 --- Comment #3 from Antoine Brodin --- Failure log on 12.0 amd64: http://package18.nyi.freebsd.org/data/120amd64-default-PR238988/2019-10-12_19h22m07s/logs/messagelib-19.08.1_1.log -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 240466] graphics/digikam: Segmentation fault on startup
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240466 --- Comment #7 from commit-h...@freebsd.org --- A commit references this bug: Author: adridg Date: Sun Oct 13 08:41:23 UTC 2019 New revision: 514373 URL: https://svnweb.freebsd.org/changeset/ports/514373 Log: Try to fix runtime graphics/digikam. With this patch applied to git master, digikam starts and seems to work. It still crashes on exit, though. That's an improvement on crashes-before-startup. The problem is described in the patch and in the PR: digikam bundles all kinds of stuff (which packagers have been complaining about for years) which breaks -- in this case, bundling internals of Exiv2. If this works (leaving the PR open) it will need an MFH. PR: 240466 Changes: head/graphics/digikam/Makefile head/graphics/digikam/files/patch-remove-libxmp -- You are receiving this mail because: You are the assignee for the bug.
Re: FreeBSD Port: graphics/digikam
Hi Tobias, dear committer of kde-freebsd, thanks for your efforts. My mail should not to be a rant, more a question, how to avoid such trouble in thew future and how to get help. I'm patient, maybe the segfault of digikam has to do with further broken stuff and fixing that needs time, and I know, you spend your leisure time. Today I'll set up a further FreeBSD installation with latest repo and head branch. And if I can help you fixing such stuff, please let me know which info you need. Kind regards, Holger Am 09.10.19 um 19:52 schrieb Tobias C. Berner: Hi Holger Sorry for the breakage. Due to a lack of free time, I could not yet investigate the breakage.I will, as soon as I can :) The quarterly branch gives you no guarantees at all -- it is cut at a given time, and if you are lucky the tree was in a good state at the time. Afterwards it just mostly gets older :D -- so there is no process of choosing "stable" staff for the quarterly (so it's purely timing based -- quarterly, literally). I think this time it was just bad luck, I assume, I did some testing and found it working, but apparently it wasn't, or I didn't :) -- totally my bad here. I hope to have time to fix it by this or the next weekend -- no promises, patches are welcome :D. If you really require it to be working right now, you can just grab the port from the revision prior to its upgrade and built the old one -- that should work. mfg Tobias On Wed, 9 Oct 2019 at 07:29, Holger Wagemann mailto:holger.wagem...@posteo.de>> wrote: Dear maintainer, I'm a desktop user, like the work of kde-freebsd team to have a current plasma5 desktop and other applications like digikam. I use pkg and latest stuff, sometimes head branch and ports and apart from some instabilities, which were fixed in the past in a short time, I'm satisfied with combination of FreeBSD and plasma5 and further desktop stuff. After switching from digikam 6.0.0 to a newer version some weeks ago in "latest" this software is broken, it starts reproducible with a segfault. This bug is reported since 2019-09-10. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240466 Okay, in quarterly branch 2019Q3 there was digikam in version 6.0.0 and this version works. So some days ago I've switched from head to quarterly, to reduce such issues. But yesterday you switched to new quarterly branch 2019Q4 and with a pkg upgrade I get new binaries, also digikam, and now in version 6.3.0. And it starts with a segfault. My question: Why putting broken stuff from head in a new quarterly branch? I thought, that quarterly protects user from such issues and only working stuff from head was putting into a new quarterly branch (like manjaro: stuff from testing repo was putting to stable repo, when it is stable). But it seems, that a new quartely branch only get a snapshot of binaries from head without any inspection, if this stuff works or not. What can I do to get a working version of digikam in combination with FreeBSD? And how can I avoid such issues in the future? Still using quarterly seems not to be enough. Please keep in mind, that I'm a user and not a developer. Kind regards Holger
