[Bug 272907] www/firefox: 116.0 no longer uses native notifications in KDE, and crashes often when displaying built-in ones

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272907

Graham Perrin ◐  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com,
   ||k...@freebsd.org
  Flags||maintainer-feedback?(kde@Fr
   ||eeBSD.org)

--- Comment #4 from Graham Perrin ◐  ---
Crashes should probably be a separate bug report (not reproducible here). 

>From what I see, with multiple applications: this BR is more broadly

- with, or affecting, devel/kf5-knotifications

- not limited to www/firefox. 



At a glance, I see nothing related upstream.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

maintainer-feedback requested: [Bug 272907] www/firefox: 116.0 no longer uses native notifications in KDE, and crashes often when displaying built-in ones

[bugzilla-noreply]

Graham Perrin ◐  has asked freebsd-kde (Team)
 for maintainer-feedback:
Bug 272907: www/firefox: 116.0 no longer uses native notifications in KDE, and
crashes often when displaying built-in ones
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272907



--- Comment #4 from Graham Perrin ◐  ---
Crashes should probably be a separate bug report (not reproducible here). 

>From what I see, with multiple applications: this BR is more broadly

- with, or affecting, devel/kf5-knotifications

- not limited to www/firefox. 



At a glance, I see nothing related upstream.

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/k...@freebsd.org.html


Port| Current version | New version
+-+
devel/libphonenumber| 8.13.17 | v8.13.18
+-+
devel/qtcreator | 11.0.0  | 11.0.1
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Reported by:portscout!

[Bug 272895] devel/cmake-core: Could NOT find LibUV: Found unsuitable version "1.18.0", but r equired is at least "1.28.0" (found /usr/local/lib/libuv.so)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272895

Marcin Cieślak  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Not A Bug

--- Comment #7 from Marcin Cieślak  ---
This was it! Thank you very much!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 272895] devel/cmake-core: Could NOT find LibUV: Found unsuitable version "1.18.0", but r equired is at least "1.28.0" (found /usr/local/lib/libuv.so)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272895

Jason E. Hale  changed:

   What|Removed |Added

 Status|New |Open
 CC||jh...@freebsd.org

--- Comment #6 from Jason E. Hale  ---
You might have some leftover bits of an ancient libuv installation.
FindLibUV.cmake first checks for ${LibUV_INCLUDE_DIR}/uv-version.h and then for
${LibUV_INCLUDE_DIR}/uv/version.h. The former is the older format.

I suspect you at least still have a /usr/local/include/uv-version.h which is
confusing the version check. This file should be removed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 272843] multimedia/mlt7: add option to allow build with audio/libebur128 instead audio/ebur128 if PLUS module enabled

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272843

Li-Wen Hsu  changed:

   What|Removed |Added

 Resolution|Not Accepted|---
 Status|Closed  |Open
 CC||lw...@freebsd.org
   Assignee|ports-b...@freebsd.org  |k...@freebsd.org

--- Comment #4 from Li-Wen Hsu  ---
I think this should be decided by the maintainer.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.