Re: qt5-core not building

[Schaich Alonso]

On Fri, 26 Oct 2018 20:37:24 +
Andrew Hamilton-Wright  wrote:

> 
> As it happens, I do use synth for port management.  That does not solve the 
> problem.  In fact, it was problems in synth build that let me to look into 
> this issue in the first place.
> 
> What is clear to me is that the port installation of qt5 as it exists on my 
> machine is broken, as it cannot be built from the port itself, which is, I 
> note the recommended way of doing things as described in the FreeBSD manual.
> 
> The machine is up to date.  When building, I see the 5.11.2 version number 
> for QT being reported at multiple points, however the build itself is getting 
> the old version information from somewhere.
> 
> Where are these “hidden” data pieces stored?  It would be helpful to know 
> where the clearly incorrect version numbering is coming from.
> 
> If, to do this, I do need to completely remove QT, a pointer to some 
> instructions on how to do that would be helpful.  It does not seem to simply 
> be the case that either port based “make deinstall” or package based delete 
> has any effect on the problem.  Wherever the corruption is, it is not touched 
> by these methods.
> 
> Is there a clear statement somewhere about where this information is stored?  
> Or additionally how to ensure that the entirety of QT is removed in order 
> that it can be reinstalled from scratch?
> 
> Best regards,
> AHW
> 

Hi

The Qt version macros are set by qmake's makespec files, namely

> /usr/local/lib/qt5/mkspecs/modules/qt_lib_bootstrap_private.pri

which is installed as part of the qt5-buildtools package these days, but it 
might have been installed by qt5-qmake on historic ports.

A possible scenario would be having Qt-5.9.4's qt5-buildtools package installed 
while trying to compile Qt-5.11.2 packages that _should_ depend on 
qt5-buildtools (potentially indirectly by depending on other ports that depend 
on it) in order to prevent the old buildtools to be installed at the point a 
non-buildsystem Qt port is compiled.



Can you check

> make -V QT5_VERSION

in the devel/qt5-buildtools subdirectory of your ports repository prints 
5.11.2, and

> pkg info qt5-buildtools

confirms the package system "thinks" 5.11.2 is installed?



Another potential scenario would be having attempted to perform a manual 
update, i.e. using "make" rather than some ports-management tool (portmaster 
and the likes), and having forgotten to run "make clean" before updating the 
ports tree. AFAIK, ports would reinstall the already built content of the 
stagedir because it has "learned" that "make build" / "make stage" has already 
sucessfully completed before the ports tree was updated and still has this 
"knowledge" after the update.



Alonso

Re: qt5-core not building

[Schaich Alonso]

On Fri, 26 Oct 2018 12:02:51 +0200
"Tobias C. Berner"  wrote:

> Moin moin
> 
> Your Qt5 seems way out of date. As the version string is 5.9.4.
> Please update your ports tree and packages to be up to date.
> 
> 
> Mfg Tobias

Hi

There is also indication that both Qt-5.9.4 and 5.11.2 are being used
at the same time.

There used to be issues when updating Qt using ports rather than pkgng,
the workaround back then (last year) was to uninstall the old Qt and
installing the new one so the build process wouldn't mix the versions
when building the "new" Qt.

I'm still removing my old Qt installations before building the new ones
these days, which is a pain since removing Qt also removes KDE and
other Qt consumers.

Am I wasting time rebuilding half the system rebuilding half my system
on updates that don't even break ABI, or do we still suffer from qmake
messing up the include paths?

Alonso

Re: configure script failed unexpectedly (digikam)

[Schaich Alonso]

> any hints?
> 

Hi

We introduced the gold blacklisting to workaround a bug in the linker,
when working with qt5 ports.

Currently, the blacklisting is implemented by line 152 of Mk/bsd.qt.mk
of the ports collection, however it's unclear to me why it affects your
Qt4 port (qt4-moc).

Alonso

Re: Digikam update

[Schaich Alonso]

On Thu, 22 Jun 2017 22:20:03 +0200
"Tobias C. Berner"  wrote:

> btw, there is also a kipiplugins update to 5.6.0 :)
> 

graphics/{lib}gphoto2 has a new version, too, though that port is not 
maintained by kde@

I've updated kipiplugins and just posted the pull request.

Alonso

Re: Digikam update

[Schaich Alonso]

On Thu, 22 Jun 2017 23:13:34 +0200
Adriaan de Groot <gr...@kde.org> wrote:

> On Thursday 22 June 2017 21:47:01 Schaich Alonso wrote:
> > and updated digikam, though the guidelines posted on our github project
> > page ask me not to make a pull request and commit to SVN instead, which
> > has been down for months now. Is the guideline outdated, or do we have
> > a new SVN repository?
> 
> I .. don't see that anywhere? Where are you looking?
> 
> If anything, "SVN" here means the official ports tree, for FreeBSD. The 
> Area51 
> SVN ports tree, with merge-scripts and the whole shebang, is no more 
> (although 
> the machine has come back up, we've basically nuked the repo).
> 
> So go ahead, do a pull request, that's the easiest way to work together on 
> this ports tree (short of just committing to freebsd-ports-kde directly). 
> Swills does it all the time.
> 
> [ade]

Hi

This is the page that states SVN was prefered:
https://github.com/freebsd/freebsd-ports-kde/blob/plasma5/CONTRIBUTING.md

Alonso

Re: kwin_x11 crashes immediately after starting kde session

[Schaich Alonso]

On Tue, 13 Jun 2017 16:04:09 -0400
Dwayne MacKinnon  wrote:

> I was just wondering if there's any update on this? I don't want to
> upgrade my ports until this issue is settled.
> 
> Cheers,
> DMK
> 

It's also happening over here. I've workarounded it by using
openbox-kde-session (of x11-wm/openbox) instead of startkde
in .xinitrc, which is good enough for the basic stuff, however most of
the kwin features are missing.

Alonso

Re: New development repository location.

[Schaich Alonso]

On Wed, 31 May 2017 10:10:21 +0200
"Tobias C. Berner"  wrote:

> Hi there
> 
> The development repository that the KDE-FreeBSD team uses to work on the KDE
> ports for FreeBSD is moving to github. For a long time we have been using
> 'area51', an SVN repository kindly hosted by PC-BSD and iX Systems. At this
> point in time, we believe that moving to github will make the ports a bit
> more accessible for users and align our ports-development effort better with
> the the way upstream (that is, with official FreeBSD ports) works. We
> would like to express our thanks to PC-BSD for hosting us all this time,
> in particular Josh Paetzel for administering the repository. In the coming
> days we will be updating documentation to reflect the new source of
> KDE-FreeBSD ports.
> 
> 
> The repository can now be found at
> https://github.com/freebsd/freebsd-ports-kde
> where the plasma5 branch is a ports tree with all the updates from the
> old svn repository.
> 
> 
> The main difference between the old svn repository and the new one is, that
> like gnome@ and xorg@, we now have a complete portstree. So the kdemerge 
> script
> previously used is obsolete -- however, this also mean, that we will lag 
> behind
> ports-master, which we will try to sync with every weekend.
> 
> 
> 
> 
> mfg Adriaan, Raphael, Tobias

Hi and thanks for doing this.

>From my understanding, rather than updating the official PORTS and
running our kdemerge script, we now merge/rebase the current HEAD of
the PORTS into the "master" branch of our new repository to
collection, then merge/rebase our master into the "plasma5" branch?

Alonso

Re: The state of KDE on FreeBSD / root vulnerability...

[Schaich Alonso]

On Fri, 19 May 2017 17:17:02 +0200
Hannes Hauswedell  wrote:

> Hi everyone,
> 
> my main question is whether KDE on FreeBSD is affected by the infamous KDE 
> root vulnerability.
> 
> I don't want to complain or anything, and I know it's all volunteer work (I 
> did lot's testing back in the KDE4 porting efforts), but the current state of 
> KDE on FreeBSD seems to be rather desolate to me right now. I have stopped 
> reporting bugs years ago, because upstream wouldn't take them, because our 
> versions are so outdated. Besides the annoyances of bugs, there now seem to 
> be 
> serious security problems and I wonder everyday whether KDE5 (or at least 
> KDE4's app packages) are around the corner, or whether I need to migrate all 
> my work away from KDE software as fast as possible.
> And yes, I have looked at area51, but it doesn't seems to contain packages 
> for 
> any of the relevant apps (kmail, kate, kile, kdevelop...) and also I don't 
> want to risk mixing packages on my work computers.
> 
> Of course I would love to stick with the KDE apps, but it would be really 
> helpful right now to know if there is a plan/timeline for updates, or whether 
> this is completely unknown right now.
> 
> Thank you,
> Hannes
> 
> 

Hi

I can't tell you about the schedule of KF5 for FreeBSD. The KF5 library
components that are currenlty in the ports collection will likely see
an update soon, as the exp-run required for such a large commit
completed yesterday. Note that these components are just the libs and
not the desktop and front end applications themselves.

The "relevant" apps are all in area51's plasma5 branch. Although I
cannot say anything about kmail, the others "work" here. Which means
the desktop itself and kate work better than their KDE4 counterparts,
but kdevelop segfaults every 2 minutes on my installation :D

Make sure to switch to the plasma5 branch of area51 if you want/need
kde5, as the default branch is still on KDE-4.14 and Qt-4.8.

Alonso

Re: [kde-freebsd] PR 210053

[Schaich Alonso]

On Sun, 05 Jun 2016 16:49:20 +0200
Ralf Nolden  wrote:
> 
> Hi Alonso,
> 
> thanks for the info. On the Qt side (where it appears as a problem in 
> QtNetwork) we've added now a patch to only support openssl. The usability of 
> libressl and the support for that can be argued about, however, I think we 
> should at least write up some advisory what is used where so people know how 
> to treat problems with Qt-related software in case of security advisories.
> 
> If the use of libressl instead of openssl can be made optional by an option 
> and keep the defaults at openssl, I'm fine with any patch as long as it is up 
> to the user to build that with qca. (on Qt, I wouldn't do that on qt5-network 
> because it is not officially supported by Qt).
> 

libressl is already an option, defaulting on base's openssl. [1]

> Until that is given, I wouldn't use the patch. How is upstream handling the 
> use of libressl ?
> -- 
> Kind regards,
> 
> Ralf Nolden
> 

Hi

Upstream has the same approach that we have for handling SHA-0[2], and
a different one for SSL3: They don't provide a fallback if there's no
SSLv3 support [3], while the FreeBSD wiki proposes to do SSLv23 [4]

References:
[1] https://wiki.freebsd.org/LibreSSL
[2] 
https://quickgit.kde.org/?p=qca.git=commit=0dbed8eb38afd1561907a52283091c37e7b85156
[3] 
https://quickgit.kde.org/?p=qca.git=commit=20a587d77636186edb044cd2b71d6d90fe98d232
[4] 
https://wiki.freebsd.org/LibreSSL/PatchingPorts#SSLv2.2FSSLv3_method_failures



Alonso



pgp0F7EYJewjD.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

[kde-freebsd] PR 210053

[Schaich Alonso]

I forgot my bugzilla password and "The system is not configured to allow 
password change requests." ...

I've got this review ticket for the libressl issue. Somehow kde@ was not CC-ed.

https://reviews.freebsd.org/D6685

Given it took me one month to open the ticket, I didn't expect the PR to me 
made so quickly after it.

Rakuco is AFK for the time being, so anyone with PORTS commit bit just send it 
in.

Alonso


pgpzYc_WPvnBP.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/QT/devel/qt5-assistant

[Schaich Alonso]

On Wed, 23 Mar 2016 07:56:55 +0100
Ralf Nolden  wrote:

> Am Mittwoch, 23. März 2016, 07:05:21 schrieb Ralf Nolden:
>  
> > > Hi
> > > 
> > > Sorry it took me so long to reply.
> > > 
> > > Wouldn't it be more straightforward to add a dependency on qt5-help for
> > > assistant?
> > 
> Looking at the HEAD Makefile, there is already a dependency on qt5-help, so 
> nothing to do here. You'd just need to revert on your area51 commit.
> 
> -- 
> Kind regards,
> 
> Ralf Nolden
> 

Done in r12162

Alonso


pgpUCXe6ukKHh.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] qtcreator 3.6.1 svn diff

[Schaich Alonso]

On Thu, 17 Mar 2016 21:56:19 +0100
Ralf Nolden  wrote:

> Hi,
> 
> appended the diff for qtcreator 3.6.1.
> 
> I did a quick check for the docs of qtcreator. We can't build them unless we 
> have the docs for Qt installed (which unfortunately aren't in the svn tree 
> yet). 
> 
> -- 
> Kind regards,
> 
> Ralf Nolden

Hi

Can you explain why you want to link against dl (only) on OpenBSD?

Alonso


pgptmifbmPZjB.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Things in trunk that seem to be a downgrade

[Schaich Alonso]

On Sun, 28 Feb 2016 12:54:46 +0100
Adriaan de Groot  wrote:

> Having rebuilt everything using area51 trunk (KDE4), I was about to upgrade 
> my 
> system using all the packages built from area51 trunk. Most of it seems 
> sensible:
> 
> Installed packages to be UPGRADED:
> telepathy-qt4: 0.9.4 -> 0.9.5
>   ...
> automoc4: 0.9.88_4 -> 0.9.88_5
> attica: 0.4.2,2 -> 0.4.2_1,2
> 
> But there's also cases where ports are actually unchanged in trunk, but are 
> missing a PORTREVISION that matches official ports. This makes it seem like a 
> downgrade:
> 
> Installed packages to be DOWNGRADED:
> soprano: 2.9.4_1 -> 2.9.4
> raptor2: 2.0.15_1 -> 2.0.15
> qt4-corelib: 4.8.7_2 -> 4.8.7
> nepomuk-core: 4.14.3_3 -> 4.14.3_1
> libstreams: 0.7.8_1 -> 0.7.8
> libstreamanalyzer: 0.7.8_5 -> 0.7.8_2
> libkfbapi: 1.0_3 -> 1.0   
>   
> kfilemetadata: 4.14.3_3 -> 4.14.3 
>   
> ebook-tools: 0.2.2_3 -> 0.2.2 
>   
> 
> I'm wondering what to do with these. I would expect this to complicate a 
> merge 
> into ports a little. Here's what seems to be the differences:
> 
> soprano: 2.9.4_1 -> 2.9.4
> Only PORTREVISION and USES=tar:bz2 vs USES=tar:bzip2. Portrevision was bumped 
> in ports r353029; that change is incorporated in trunk.
> 
> raptor2: 2.0.15_1 -> 2.0.15
> Only PORTREVISION. Bumped for an ICU update in april 2015.
> 
> qt4-corelib: 4.8.7_2 -> 4.8.7
> PORTREVISION bumped twice. r402613 and r408855. Both changes are also in 
> trunk 
> (except for the bump).
> 
> nepomuk-core: 4.14.3_3 -> 4.14.3_1
> Bumped for libzip update in r395464 and poppler in r406872.
> 
> libstreams: 0.7.8_1 -> 0.7.8
> Bumped in r344139 and then most of that change reverted in 395972.
> 
> libstreamanalyzer: 0.7.8_5 -> 0.7.8_2
> Most recently bumped for NEW XORG in r351411
> 
> libkfbapi: 1.0_3 -> 1.0   
>   
> Bumped for gcc update in 2014.
> 
> kfilemetadata: 4.14.3_3 -> 4.14.3 
>   
> Bumped for libzip and poppler.
> 
> ebook-tools: 0.2.2_3 -> 0.2.2 
>   
> Bumped for libzip.
> 
> 
> So I'd like to reintroduce the PORTREVISIONS for these ports -- which are all 
> essentially unchanged from official ports -- so that they don't seem like a 
> downgrade.
> 
> But there's an underlying question here: should trunk follow ports closely 
> except for the-ports-that-are-being-prepared-for-update, or not? 
> 
> [ade]

Go ahead. Most of those ports in area51's lack of PORTREVISION is
likely my doing, as I strip them of the PORTREVISION bits because
area51 used to have newer versions of those ports than FreeBSD PORTS.

In fact, the lack of PORTREVISION breaks area51-based installations
quite often, because the neccessity to rebuild a port becomes hidden.

Alonso


pgpQ28H0Wu3Ak.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] area51 trunk + KDE4

[Schaich Alonso]

On Sat, 27 Feb 2016 10:58:19 +0100
Adriaan de Groot  wrote:

> Hey all,
> 
> I think I've (*) updated area51 trunk to "the latest". Which means kdelibs 
> 4.14.9, workspace to 4.11.20, KDevelop to 4.7.3. So what would the next step 
> be? There's a tiny bit of KF5 prep work done in there, so it might be 
> complicated to push to ports -- but probably worth it, to update all the KDE4 
> stuff which was last bumped by alonso in march 2015.
> 
> [ade]
> 
> 
> (*) as in "I did the last commit so that port deve/kde4 compiles for me", not 
> that I did all the work, because TCB and Rakuco did all the heavy lifting.

Hi

Thanks for doing the update. I think the next step would be to open a
commit review ticket and get some reviews before having the changeset
commited to ports, as the number of affected ports is quite large.
AFAIK a freebsd-account is not needed in order to get a phabricator
account at this time, but I could be wrong.

This page explains how to use phabricator:

https://wiki.freebsd.org/CodeReview

Also, because of the number of affected ports, it might be
recommendable to create a CFT bug tracking ticket to have all KDE ports
be build on all primary target systems (x86/amd64 and FreeBSD-8/9/10).

Alonso


pgpGarNbyZoKf.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] kwin and GL_OUT_OF_MEMORY

[Schaich Alonso]

On Sun, 24 Jan 2016 20:13:46 -0500
"Mikhail T." <mi+t...@aldan.algebra.com> wrote:

> On 24.01.2016 17:16, Schaich Alonso wrote:
> >> cc $(pkg-config --cflags --libs gl glu x11) NVX_gpu_memory_info.c
> > on a box with kde and it's dependencies installed.
> Ok, here it is:
> 
> NVIDIA: API mismatch: this NVIDIA driver component has version
> 304.128, but the NVIDIA kernel module's version does not match.
> Please make sure that the kernel module and all NVIDIA driver
> components have the same version.
> GPU_MEMORY_INFO_DEDICATED_VIDMEM_NVX=0
> GPU_MEMORY_INFO_CURRENT_AVAILABLE_VIDMEM_NVX=0
> GPU_MEMORY_INFO_EVICTION_COUNT_NVX=0
> GPU_MEMORY_INFO_EVICTED_MEMORY_NVX=895
> 
> This is an older video card (Quadro FX 1400), so the kernel-part has to
> be older... Everything worked, though -- and even OpenGL screensavers
> are /fast/ -- except for this problem...
> > Do you have any custom xorg.conf tuning?
> The above qualifies, does not it?.. Thank you very much. Yours,
> 
> -mi
> 
> 

All those numbers are supposed to be kilobytes, to
GPU_MEMORY_INFO_DEDICATED_VIDMEM_NVX=0 should hint your video card
has no video memory at all, or at least applications using
GL_NVX_gpu_memory_info would get the impression thereof, however a
quadro fx1400 card should have 128MB of dedicated memory.

I'm having the x11/nvidia-driver-340 on one of my boxes, and it
doesn't cause that version mismatch warning to be emited.

Are you sure the driver is properly installed? The kernel module's
version is printed when the module is loaded which can later be queried
by reviewed using dmesg, while the userspace version can be seen using
kinfocenter at Graphical Information->OpenGL->[right side]->Direct
Rendering->Driver->OpenGL/ES Version.

Poor installations of the driver can occur when /boot is a dedicated
partition and it's not mounted while the port is being installed, or
it's mounted during installation but the driver is manually loaded
(instead of a nvidia_load at loader.conf) after booting without /boot
being mounted (so the module is loaded from the rootfs' /boot copy
where there is still the previous nvidia driver). I.e. when the mount
state of /boot is different during driver installation and module load
time.

Alonso


pgpy5zDo7L_TJ.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] kwin and GL_OUT_OF_MEMORY

[Schaich Alonso]

On Sun, 24 Jan 2016 03:27:51 -0500
"Mikhail T."  wrote:

> The .xsession-errors here is being spammed with the lines like this:
> 
> kwin(18477) KWin::checkGLError: GL error ( PostPaint ): 
> "GL_OUT_OF_MEMORY"
> 
> The machine uses an NVidia card with two large displays -- a setup
> which, probably, does use more than average amounts of memory.
> 
> Is there a way to increase the amount available to OpenGL? The box has
> 8Gb of RAM... Thanks! Yours,
> 
> -mi
> 

Hi

There's a number of reasons why GL_OUT_OF_MEMORY could be emitted,
however the usual advise is to update drivers.

I've attached the source of an application that will output video
memory information using nvidia's opengl extention. It should build with

> cc $(pkg-config --cflags --libs gl glu x11) NVX_gpu_memory_info.c

on a box with kde and it's dependencies installed.

Do you have any custom xorg.conf tuning?

Alonso


pgptOMNJAPms1.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] kwin and GL_OUT_OF_MEMORY

[Schaich Alonso]

On Sun, 24 Jan 2016 23:16:03 +0100
Schaich Alonso <alonsoscha...@fastmail.fm> wrote:

> [...]
> I've attached [...]

Erm... Another try...

Alonso

#include 
#include 
#include 
#include 

#include 
#include 
#include 
#include 

static int xvisual_attribs[] = { GLX_RGBA, None };

int main (int argc, char **argv)
{
Display *display;
Window   window;
XSetWindowAttributes win_attribs;
XVisualInfo *info;
Colormap map;
GLXContext context;

display = XOpenDisplay(NULL);
assert (display != NULL);

info = glXChooseVisual (display, DefaultScreen(display), xvisual_attribs);
assert (info != NULL);

context = glXCreateContext (display, info, NULL, GL_TRUE);
assert (context != NULL);

map = XCreateColormap (display, 
   RootWindow(display, info->screen), 
   info->visual, 
   AllocNone);

win_attribs.colormap = map;

window = XCreateWindow (display, 
RootWindow(display, info->screen), 
0, 0,
320, 240,
0,
info->depth,
InputOutput,
info->visual,
CWColormap,
_attribs);

XSetStandardProperties (display,
window,
"NVX_gpu_memory_info",
"NVX_gpu_memory_info",
None,
argv,
argc,
NULL);

glXMakeCurrent (display, window, context);

XMapWindow (display, window);

int total, current, evict_cnt, evicted;

glGetIntegerv(GL_GPU_MEMORY_INFO_DEDICATED_VIDMEM_NVX, );
glGetIntegerv(GL_GPU_MEMORY_INFO_CURRENT_AVAILABLE_VIDMEM_NVX, );
glGetIntegerv(GL_GPU_MEMORY_INFO_EVICTION_COUNT_NVX, _cnt);
glGetIntegerv(GL_GPU_MEMORY_INFO_EVICTED_MEMORY_NVX, );

printf ("GPU_MEMORY_INFO_DEDICATED_VIDMEM_NVX=%d\n", total);
printf ("GPU_MEMORY_INFO_CURRENT_AVAILABLE_VIDMEM_NVX=%d\n", current);
printf ("GPU_MEMORY_INFO_EVICTION_COUNT_NVX=%d\n", evict_cnt);
printf ("GPU_MEMORY_INFO_EVICTED_MEMORY_NVX=%d\n", evicted);

return (EXIT_SUCCESS);
}



pgpCGq0IUZXjl.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] problem with https after upgrading

[Schaich Alonso]

On Thu, 3 Dec 2015 19:24:05 +0200
Andriy Gapon  wrote:

> On 03/12/2015 18:36, Andriy Gapon wrote:
> > On 03/12/2015 18:31, Andriy Gapon wrote:
> >> It seems that the problem happens here:
> >>
> >> Program received signal SIGSEGV, Segmentation fault.
> >> 0x0008180738d9 in sk_deep_copy () from /usr/local/lib/libcrypto.so.8
> >> (kgdb) bt
> >> #0  0x0008180738d9 in sk_deep_copy () from 
> >> /usr/local/lib/libcrypto.so.8
> >> #1  0x0008180b7552 in X509_VERIFY_PARAM_inherit () from
> >> /usr/local/lib/libcrypto.so.8
> >> #2  0x000818f5f96e in X509_VERIFY_PARAM_set1 (to=0x819924240, 
> >> from=0x0) at
> >> /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/x509/x509_vpm.c:209
> >> #3  0x0008194ad8da in ssl_verify_cert_chain (s=0x8093dee80, 
> >> sk= >> out>) at 
> >> /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_cert.c:495
> > 
> > Hmm, it seems like between frames #2 and #1 the control flow jumps from the 
> > base
> > libcrypto to the libcrypto from packages.  Not sure why that happens and 
> > what
> > changed...
> > 
> 
> More analysis:
> $ ldd /usr/local/lib/kde4/kio_http.so | fgrep libcrypto
> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x802d8c000)
> libcrypto.so.7 => /lib/libcrypto.so.7 (0x809ce2000)
> 
> It seems that kio_http.so is directly linked to libcrypto.so.8.
> It is also directly linked to libhx509.so.11 (from /usr/lib) which, in turn, 
> is
> linked to libcrypto.so.7.
> 
> Hmm, so, it seems that the problem is in my local environment.  My system has
> fallen a bit behind head / CURRENT, so my OpenSSL libraries are still at 
> version
> 7 while on the latest head they are at 8.  So, apparently kio_http has been
> linked with libcrypto.so.8 from the base on the package building machine.  But
> in my environment the base has libcrypto.so.7, so the wrong libcrypto.so.8 is
> picked up.
> 
> Sorry for the noise.
> -- 
> Andriy Gapon
> ___
> kde-freebsd mailing list
> kde-freebsd@kde.org
> https://mail.kde.org/mailman/listinfo/kde-freebsd
> See also http://freebsd.kde.org/ for latest information

It also seems your QtNetwork library is invoking ssl3 stuff, which
IIRC was patched out. The ports build of libQtNetwork.so over here does
not reference ssl23_connect at all. Do we have differing crypto support
depending on the openssl/libressl version in use?

Alonso


pgptmYwwqMRVd.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Request for www/otter-browser port upgrade

[Schaich Alonso]

On Tue, 22 Sep 2015 21:38:43 +0500
??   wrote:

> Good day!
> 
> Please update that port for latest available beta.
> 
> Thanks!
> ___
> kde-freebsd mailing list
> kde-freebsd@kde.org
> https://mail.kde.org/mailman/listinfo/kde-freebsd
> See also http://freebsd.kde.org/ for latest information


Hi

I've commited a port for otter's most recent beta to the kde testing
repository, and that port works fine for me. I'll ask for it to be
reviewed later or tomorrow, feel free to use and feedback on the
testing port (attached diff against current PORTS root path) until that.

Alonso
Index: www/otter-browser/Makefile
===
--- www/otter-browser/Makefile	(revision 397663)
+++ www/otter-browser/Makefile	(working copy)
@@ -1,7 +1,7 @@
 # $FreeBSD$
 
 PORTNAME=	otter
-PORTVERSION=	0.9.05
+PORTVERSION=	0.9.07
 DISTVERSIONPREFIX=	v
 CATEGORIES=	www
 # Avoid pkgname conflict with misc/otter
@@ -10,8 +10,8 @@
 MAINTAINER=	k...@freebsd.org
 COMMENT=	Browser based on Qt 5
 
-USE_QT5=	concurrent core gui multimedia network printsupport \
-		script sql webkit widgets \
+USE_QT5=	concurrent core dbus gui multimedia network printsupport \
+		script sql sql-sqlite3 webkit widgets \
 		buildtools_build qmake_build
 USES=		cmake:outsource desktop-file-utils
 
Index: www/otter-browser/distinfo
===
--- www/otter-browser/distinfo	(revision 397663)
+++ www/otter-browser/distinfo	(working copy)
@@ -1,2 +1,2 @@
-SHA256 (OtterBrowser-otter-browser-v0.9.05_GH0.tar.gz) = 78db7ea09720b3196b1fb04714b139cc4bfa66cb2974ed18852be024686683fe
-SIZE (OtterBrowser-otter-browser-v0.9.05_GH0.tar.gz) = 2302624
+SHA256 (OtterBrowser-otter-browser-v0.9.07_GH0.tar.gz) = 1c27509f9736a9c99e12a3ef23b08cc41548ad7f6d7481bf07020fb471788da9
+SIZE (OtterBrowser-otter-browser-v0.9.07_GH0.tar.gz) = 2634317
Index: www/otter-browser/files/patch-CMakeLists.txt
===
--- www/otter-browser/files/patch-CMakeLists.txt	(revision 397663)
+++ www/otter-browser/files/patch-CMakeLists.txt	(working copy)
@@ -1,21 +1,21 @@
 CMakeLists.txt.orig	2015-04-01 19:43:12 UTC
-+++ CMakeLists.txt
-@@ -71,9 +71,9 @@ endif (MSVC)
- option(EnableQtwebengine "Enable QtWebEngine backend (requires Qt 5.4)" OFF)
+--- CMakeLists.txt.orig	2015-09-01 21:59:51.0 +0200
 CMakeLists.txt	2015-09-14 12:05:37.104556120 +0200
+@@ -68,9 +68,9 @@
+ option(EnableQtwebengine "Enable QtWebEngine backend (requires Qt 5.5)" OFF)
  
- if (${EnableQtwebengine})
--	find_package(Qt5 5.4.0 REQUIRED COMPONENTS Core Gui Multimedia Network PrintSupport Script Sql WebEngine WebEngineWidgets WebKit WebKitWidgets Widgets)
-+	find_package(Qt5 5.4.0 REQUIRED COMPONENTS Concurrent Core Gui Multimedia Network PrintSupport Script Sql WebEngine WebEngineWidgets WebKit WebKitWidgets Widgets)
- else (${EnableQtwebengine})
--	find_package(Qt5 5.2.0 REQUIRED COMPONENTS Core Gui Multimedia Network PrintSupport Script Sql WebKit WebKitWidgets Widgets)
-+	find_package(Qt5 5.2.0 REQUIRED COMPONENTS Concurrent Core Gui Multimedia Network PrintSupport Script Sql WebKit WebKitWidgets Widgets)
- endif (${EnableQtwebengine})
+ if (EnableQtwebengine)
+-	find_package(Qt5 5.5.0 REQUIRED COMPONENTS Core DBus Gui Multimedia Network PrintSupport Script Sql WebEngine WebEngineWidgets WebKit WebKitWidgets Widgets)
++	find_package(Qt5 5.5.0 REQUIRED COMPONENTS Concurrent Core DBus Gui Multimedia Network PrintSupport Script Sql WebEngine WebEngineWidgets WebKit WebKitWidgets Widgets)
+ else (EnableQtwebengine)
+-	find_package(Qt5 5.2.0 REQUIRED COMPONENTS Core DBus Gui Multimedia Network PrintSupport Script Sql WebKit WebKitWidgets Widgets)
++	find_package(Qt5 5.2.0 REQUIRED COMPONENTS Concurrent Core DBus Gui Multimedia Network PrintSupport Script Sql WebKit WebKitWidgets Widgets)
+ endif (EnableQtwebengine)
  
  set(otter_src
-@@ -311,5 +311,5 @@ install(FILES resources/icons/otter-brow
+@@ -381,5 +381,5 @@
  install(FILES resources/icons/otter-browser-128.png DESTINATION ${CMAKE_INSTALL_PREFIX}/share/icons/hicolor/128x128/apps/ RENAME otter-browser.png)
  install(FILES resources/icons/otter-browser-256.png DESTINATION ${CMAKE_INSTALL_PREFIX}/share/icons/hicolor/256x256/apps/ RENAME otter-browser.png)
  install(FILES otter-browser.desktop DESTINATION ${XDG_APPS_INSTALL_DIR})
--install(FILES man/otter-browser.1 DESTINATION share/man/man1/)
+-install(FILES man/otter-browser.1 DESTINATION ${CMAKE_INSTALL_MANDIR}/man1/)
 +install(FILES man/otter-browser.1 DESTINATION man/man1/)
  install(TARGETS otter-browser DESTINATION bin/)
Index: www/otter-browser/pkg-plist
===
--- www/otter-browser/pkg-plist	(revision 397663)
+++ www/otter-browser/pkg-plist	(working copy)
@@ -7,7 +7,6 @@
 

Re: [kde-freebsd] [SVN Commit] area51/KDE/x11/kdelibs4

[Schaich Alonso]

On Tue, Sep 1, 2015, at 12:22, Max Brazhnikov wrote:
> On Fri, 28 Aug 2015 13:42:06 -0700 (PDT) Alonso Schaich wrote:
> > SVN commit 11418 by aschai:
> > 
> > Disable JASPER usage
> > 
> > JASPER was blacklisted due to it's security issues two weeks ago, and cannot
> > be installed unless explicitly whitelisted by the user. Tell kdelibs not to
> > use JASPER for the time being.
> > 
> > The corresponding jasper issues are CVE-2015-5221 and CVE-2015-5203.
> 
> Alonso! This commit changes nothing from the user perspective: the
> packages are build from the official portstree, not area51! Please commit
> security fixed to the ports directly and then to area51 if needed. Btw,
> jasper port has been fixed already.
> 
> Max

Hi

This commit does not fix a security issue, it work arounds the fact that
jasper could not be installed last week. I commited this to area51
because I had to reinstall multiple installations (hardware failure
caused loss of all my build VMs).

I'll revert this commit later, or turn JASPER into an option.
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Trying to write qt5 applications on freebsd fails - qmake-qt5 doesn't include /usr/local/lib

[Schaich, Alonso]

On Sat, 8 Aug 2015 19:10:23 -0700
Adrian Chadd adr...@freebsd.org wrote:

 Ok, so what's the real solution?
 
 Adrian

Mine is to use cmake, but the real solution is in the hands of the qt
upstream, as the issue affects not only FreeBSD, but any other platform,
too.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Trying to write qt5 applications on freebsd fails - qmake-qt5 doesn't include /usr/local/lib

[Schaich, Alonso]

On Sat, 8 Aug 2015 12:59:15 -0700
Adrian Chadd adr...@freebsd.org wrote:

 Hi,
 
 I'm trying to write QT applications on freebsd. qtcreator works (dri
 bugs aside) and can generate qt4 applications fine. But, there are
 some things that don't exist in qt4 (like the qt4 opengl integration)
 - there's just stuff missing.
 
 Firstly - qt5 isn't autodetected by qtcreator. I think it's because
 qmake isn't in /usr/local/bin/ . Sigh.
 
 The stuff is there in qt5, but since qt5-qmake isn't including
 -L/usr/local/lib, things just fail to link. This means I can't build
 anything from source that I write locally. I've modified the Makefile
 to include /usr/local/lib and things compile/run, so at least the
 pieces are there.
 
 So - what's the deal? This makes FreeBSD wholly unsuited for doing GUI
 development on, and that kinda sucks.
 
 Thanks,
 
 
 
 -adrian

This commit tries to workaround the issue
http://src.mouf.net/area51/revision/?rev=10691

However we reverted it in
http://src.mouf.net/area51/revision/?rev=10838
because it broke PORTS. QMake is messing up the linker path orders and
ends up referencing the ${PREFIX} libraries instead of the build path
ones when upgrading Qt ports, which causes the upgrade process to fail.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] update of devel/py-sip to 4.16.8 in area51 ?

[Schaich, Alonso]

On Sun, 26 Jul 2015 22:50:32 +0200
Kurt Jaeger p...@freebsd.org wrote:

 Hi!
 
 Right now devel/py-sip is at 4.16.7 in area51, as far as I can see.
 
 As I'm trying to update emulators/gns3, I'd like to have it at 4.16.8,
 if possible. What type of patch/check does it take to update it ?
 

Hi,

If you already have written ports to update it to 4.16.8, you can send
the
 svn diff
output against area51/ports to the mailing list.

If you want to write ports, the version of py-sip is written in
${AREA51-CVSROOT}/PYQT/devel/py-qt4/bsd.pyqt.mk, and all ports
depending on py-sip should be checked to still build/package well.

Otherwise I can attempt doing that, though I'd skip 4.16.8 and go
straightly for 4.16.9, unless that one has regressions.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] qmake5 fails to link

[Schaich, Alonso]

On Fri, 26 Jun 2015 10:02:55 -0300
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Schaich, Alonso alonsoscha...@fastmail.fm writes:
 
  Hi
 
  Over here, qt5's qmake fails to link even the trival qt5 projects
  (attached), when invoked via
 
  # /usr/local/lib/qt5/bin/qmake -makefile  make
 
  as it doesn't add /usr/local/lib to the library path used by the linker
  on a FreeBSD-10 system where qmakespec defaults to freebsd-clang.
 
  I traced this to r10442 of area51 which removed the QMAKE_LIBDIR
  extension from the freebsd qmakespec - inverting the
  devel/qmake5/files/patch-mkspecs__common__freebsd.conf part of r10442
  fixes the linker invokation.
 
  While a fix would be easy, rather than manual qmake invokation
  being broken on FreeBSD-10/WITH_CLANG_IS_CC for almost half a year
  unnoticed, I rather like to think that I'm invoking qmake poorly.
 
  What's the right way of invoking qmake5?
 
 Sorry for not answering this earlier.
 
 r10442 is just the merge commit. The actual change was done with a
 fairly long explanation in r10435: the point is that if we pass
 -L/usr/local/lib like that we break the upgrade process to anyone
 building the ports from sources, as the build process often ends up
 linking against, say, your installed Qt 5.3 when you are trying to build
 Qt 5.4. See ports/194088 as well as QTBUG-40825 for more information.
 
 And it hasn't gone really unnotice: ports/195105 is precisely abot this
 sort of issue, where manual invocations of qmake5 break when people do
 not explicitly set LIBDIR at least.
 
 The problem is that upstream hasn't really welcomed any efforts to fix
 the situation, and fixing 194088 is more important than fixing 195105,
 so until we figure out a solution to both I'd like to revert your
 r10691.

Go ahead.

However, the upgrade process traverses the package tree in dependency
order AFAIK, so at any point during the update, a qt-old version
library was either already overwritten by its qt-new counterpart, or
should not be referenced by the linker anyway, unless the ports
dependencies do not reflect the linker dependencies, or qmake is
messing up the library search paths for it's build/stage-dir libs with
the system path's ones.

Alonso


pgpmMPHm4MBmh.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] FreeBSD Port: devel/qtcreator

[Schaich, Alonso]

On Thu, 25 Jun 2015 09:50:34 +0100
Jose Alvarez jalva...@spamtitan.com wrote:

 
 Thanks,
 Can you tell me when qt-creator-3.4 will be released for FreeBSD?
 At SpamTitan we are trying to make a decision about standardising our 
 development environment, and remote debugging is a very desirable feature.
 Thanks,
 
 Jose
 LEGAL NOTICE This email and any files transmitted with it are confidential 
 and intended solely for the use of the individual to whom they are addressed. 
 If you have received this email in error please notify the originator of the 
 message. This footer also confirms that this email message has been scanned 
 for the presence of computer viruses. Any views expressed in this message are 
 those of the individual sender.

Hi again

It turns out I was wrong earlier. We have qt-creator-3.3.1 in the
experimental KDE/QT branch which usually has no older packages than
PORTS, and PORTS has qt-creator-3.4.0 instead.

The commit you linked in your earlier mail is part of 3.4.0.

Alonso


pgpRUei9z03yv.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] FreeBSD Port: devel/qtcreator

[Schaich, Alonso]

On Wed, 24 Jun 2015 09:48:57 +0100
Jose Alvarez jalva...@spamtitan.com wrote:

 Hello,
 I am having trouble with QTCREATOR when I try to do remote debugging 
 between two FreeBSD machines.
 The error I get is:
 
 /Initial setup failed: Connection error: SSH Protocol error: Server
 Identification string SSH-2.0-OpenSSH_6.6.1p1-hpn14v2
 FreeBSD-openssh-portable-base-6.6.p1_4,1 is invalid.//
 /
 
 
 I do believe it is related to this bug/patch:
 
 https://codereview.qt-project.org/#/c/109525/
 
 Can you confirm if it has been applied to the port?
 
 Thank you very much,
 
 Jose
 
 LEGAL NOTICE This email and any files transmitted with it are confidential 
 and intended solely for the use of the individual to whom they are addressed. 
 If you have received this email in error please notify the originator of the 
 message. This footer also confirms that this email message has been scanned 
 for the presence of computer viruses. Any views expressed in this message are 
 those of the individual sender.

We currently have qt-creator-3.3.1 in PORTS, and the patch you refered
was commited to qtcreator-3.4. Patches applied by the PORTS developers
reside in the ``files'' subdirectory of each port (if there are any
patches), so, no, we did not add this patch to the qtcreator port.

Alonso


pgp3XCM40ZwxF.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/KDE/graphics/libkdcraw-kde4

[Schaich, Alonso]

On Mon, 15 Jun 2015 08:06:44 -0700 (PDT)
Alonso Schaich alonsoscha...@fastmail.fm wrote:

 SVN commit 10788 by aschai:
 
 Enable exceptions for libkdraw
 
 This fixes the build process using gcc. The patch is derived from [1], which
 was found by racuko@ and obsoletes the kdelibs patching done in r10784.
 
 PR:   200734
 
 
 
  A files (directory)  
  A files/patch-libkdcraw__CMakeLists.txt  
 
 

... and [1] is 
http://quickgit.kde.org/?p=libkdcraw.gita=commitdiffh=46898ec97a0462eb08a5b6d0450a86b27aae

Alonso


pgpUtC6eelRYO.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Qt 5 and GCC4.9.3

[Schaich Alonso]

On Wed, 20 May 2015 08:03:40 + (UTC)
Dirk Niebelus dirkniebe...@yahoo.de wrote:

 Hello,
 I'm using Freebsd 9 (current FreeNAS) and my goal is to compile the qt5 port 
 with gcc493 and the std=c++11 switch enabled.The emphasis is here on the 
 c++11 switch, i figure if c++11 works i can use c++14 as well.
 
 Tried different things like modified the CXXFLAGS in make.conf. But it still 
 uses c++98
 I'm searching for a rock solid way to this.
 
 Thank you for the Qt Port!Dirk
 


You can have qmake5-built ports use some custom c++ flags by
modifying the qmakespecs which are by default installed into
/usr/local/lib/qt5/mkspecs by the devel/qmake5 port. The name to
be set is called QMAKE_CXXFLAGS, and there's no specific place for it,
though you will likely have to put it somewhere referenced by
freebsd-g++.conf. To build devel/qmake5 itself using c++11/14 support,
adding

.if (!empty(.CURDIR:M*devel/qmake5*))
CXXFLAGS+=  -std=c++1y
.endif

to /etc/make.conf works over here - of cause, you can just extend
CXXFLAGS in make.conf for your qmake5 consumers instead of using the
makespecs, too.

AFAIK - unlike on Windows OS, or rather, Visual C++ - FreeBSD's c++98
binaries are ABI compatible to their c++11 built counterparts, and even
linked to the same STL implementation, so I don't think there's a point
of using c++11 compiler mode unless the code actually uses c++11.

If some consumer port specifies pedantic compilation mode, requesting
c++11 or 14 might even break the build.

Alonso


pgpybdbmNtx6I.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/QT/devel/qmake5/files

[Schaich, Alonso]

On Tue, 19 May 2015 13:20:43 +0200
Tobias Berner tcber...@gmail.com wrote:

 Hi,
 
 Won't this introduce problems of qt ports linking against older installed 
 versions when being upgraded?
 
 
 mfg Tobias
 
 

Older installed versions of ... Qt? Qt4 is installed in a different
path and we don't support installing 2 different versions of Qt5 at the
same time AFAIK.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

[kde-freebsd] qmake5 fails to link

[Schaich, Alonso]

Hi

Over here, qt5's qmake fails to link even the trival qt5 projects
(attached), when invoked via

# /usr/local/lib/qt5/bin/qmake -makefile  make

as it doesn't add /usr/local/lib to the library path used by the linker
on a FreeBSD-10 system where qmakespec defaults to freebsd-clang.

I traced this to r10442 of area51 which removed the QMAKE_LIBDIR
extension from the freebsd qmakespec - inverting the
devel/qmake5/files/patch-mkspecs__common__freebsd.conf part of r10442
fixes the linker invokation.

While a fix would be easy, rather than manual qmake invokation
being broken on FreeBSD-10/WITH_CLANG_IS_CC for almost half a year
unnoticed, I rather like to think that I'm invoking qmake poorly.

What's the right way of invoking qmake5?

Alonso


pgpRp2EHMs1RJ.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] qmake5 fails to link

[Schaich Alonso]

On Thu, 23 Apr 2015 17:15:57 +0200
Schaich, Alonso alonsoscha...@fastmail.fm wrote:

 Hi
 
 Over here, qt5's qmake fails to link even the trival qt5 projects
 (attached), when invoked via
 
 # /usr/local/lib/qt5/bin/qmake -makefile  make
 
 as it doesn't add /usr/local/lib to the library path used by the linker
 on a FreeBSD-10 system where qmakespec defaults to freebsd-clang.
 
 I traced this to r10442 of area51 which removed the QMAKE_LIBDIR
 extension from the freebsd qmakespec - inverting the
 devel/qmake5/files/patch-mkspecs__common__freebsd.conf part of r10442
 fixes the linker invokation.
 
 While a fix would be easy, rather than manual qmake invokation
 being broken on FreeBSD-10/WITH_CLANG_IS_CC for almost half a year
 unnoticed, I rather like to think that I'm invoking qmake poorly.
 
 What's the right way of invoking qmake5?
 
 Alonso

+attachments
#include QCoreApplication

int
main (int argsc, char **argsv)
{
  QCoreApplication app (argsc, argsv);

  return (app.exec ());
}



test.pro
Description: Binary data


pgpd1NWdo1DKJ.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/PORTS/www/otter-browser-devel

[Schaich, Alonso]

On Thu, 16 Apr 2015 11:16:46 +
Max Brazhnikov m...@freebsd.org wrote:

 On Tue, 14 Apr 2015 08:21:40 -0700 (PDT) Alonso Schaich wrote:
  SVN commit 10668 by aschai:
  
  Update otter-browser-devel to yesterday's weekly snapshot
 
 Hey, why do you do this in area51? Qt 5 framework is already in ports, just
 commit otter ports to the portstree and work on them there for the benefit of 
 all users.
 

Hi,

I commit them to area51 so I can reference those commits when I ask you
for reviewing. Let me ask herewith then :D

Also, given the lot of discussion I recently saw on svn-ports about
them, are the GH_* settings ok? (CHANGES only mentions MASTER_SITE
changes)

Alonso


pgpAfL86mnqXI.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/PORTS/www/otter-browser-devel

[Schaich, Alonso]

On Wed,  8 Apr 2015 04:01:01 -0700 (PDT)
Alonso Schaich alonsoscha...@fastmail.fm wrote:

 SVN commit 10667 by aschai:
 
 Update otter devel to monday's snapshot
 
 Changelog:
   Weekly report #66 (06-04-2015)
 
   Yet another week:
* 58 commits by two authors
* two proposed pull requests
* nine new issues (23 closed)
* 114 issues still open (including 3 bugs)
 
   Highlights:
* various bug fixes (if you are using beta 5 then you should update to
  this release)
 
 
 
 
  M  +2 -11 Makefile  
  M  +2 -2  distinfo  
  A pkg-plist  
 

...
And fix incomplete installation issues as in the non-devel version, see
r10666.


pgp5MnAO0frzC.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Phonon-vlc crashing

[Schaich Alonso]

On Mon, 23 Mar 2015 20:38:09 +0200
David Naylor d...@freebsd.org wrote:

 Hi,
 
 I always seem to be complaining about Phonon :-(.  My latest issue has been 
 crashes in phonon-vlc (phonon-gstreamer still doesn't work).  
 

Hi,

while it seemed not to have been useful to someone else contacting the
mailing list yesterday, I found either

* uninstalling multimedia/phonon-vlc and reinstalling
x11/kde4-workspace with gstreamer instead of vlc OPTION set,

or

* reinstalling multimedia/vlc without it's QT5 ports OPTION

workarounds the issue for me.

Both are probably not generaly good though, because gstreamer AFAIK
lacks flac support and disabling QT5 support in vlc on the other hand
also disables it's GUI, which makes it useless as a jukebox.

Alonso


pgpwePTYa3LE6.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Systemsettings critical bug in KDE 4.14.3

[Schaich Alonso]

On Sun, 22 Mar 2015 13:41:05 -0300
brunomaxi...@openmailbox.org wrote:

 Hi, critical bug in systemsettings. Everytime shows kcrash window with 
 systemsettings PID: 15388 Sinal: Segmentation fault (11) when I go to 
 audio and video configuration. More info:
 

Hi

This is an artifact of the recent VLC version bump. KDE defaults to use
VLC for it's multimedia playback, which can be configured at the
x11/kde4-workspace port.

Recently, VLC was updated and now uses QT5, which is ABI incompatible to
QT4 used by KDE. The segmentation fault is an outcome thereof.

To workaround the issue, either rebuild kde4-workspace with gstreamer
instead of VLC support or rebuild multimedia/vlc without the QT5 option
(this will disable the VLC GUI though).

Alonso


pgpH1NtJ9et0g.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] 4.14.3?

[Schaich Alonso]

On Thu, 26 Feb 2015 17:25:07 -0500
ajtiM lum...@gmail.com wrote:

 Hi!
 
 Just a curiosity...
 I use KDE 4.14.3 from early December from area51 and it works very good (for 
 me better than previous version) but it is not in the ports still (outside is 
 4.14.5). Is it something wrong, please?
 
 Thank you.
 -- 
 ajtiM

Hi,

It got delayed considerably because I generated an defunct patchset
around christmas and was rather busy IRL in January.

area51's KDE 4.14.3 (or rather, last week's version of it) passed an
exp-run last week and is currently under review for PORTS merging at
https://reviews.freebsd.org/D1950 .

Alonso


pgpctvAbBGoXe.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] KDE4 and x11/xrandr

[Schaich, Alonso]

On Wed, 18 Feb 2015 08:57:00 -0600
Adam Vande More amvandem...@gmail.com wrote:

 Shouldn't x11/xrandr be installed by default when installing x11/kde4?
 
 Modifying the display settings requires it.
 
 -- 
 Adam

Hi,

It's currently required by the x11/kde4-workspace port.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/QT/x11-toolkits/qt5-gui

[Schaich Alonso]

On Tue, 17 Feb 2015 00:27:52 +0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Alonso Schaich alonsoscha...@fastmail.fm writes:
 
  SVN commit 10580 by aschai:
 
  Fix QSystemTray
 
  Add a patch found by PCBSD's Kris Moore k...@pcbsd.org that fixes
  QSystemTrayIcons on Desktops other than KDE.
 
  Provided by Kris yesterday via mailing list.
 
   A files (directory)
   A files/patch-src_plugins_platforms_xcb_qxcbwindow.cpp
 
 Are you going to commit this to the ports tree?


I forgot about this one :D

Copy  Paste the commit message and add approved by rakuco?

Alonso


pgpO85QtINu2Y.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] kopete tls issue

[Schaich, Alonso]

On Thu, 29 Jan 2015 16:49:49 +0100
Schaich, Alonso alonsoscha...@fastmail.fm wrote:

 On Wed, 28 Jan 2015 19:57:14 +0200
 Oleg Nauman oleg.nau...@gmail.com wrote:
 
  On Mon, Jan 26, 2015 at 10:29 PM, Adam Vande More amvandem...@gmail.com
  wrote:
  
   On Sun, Jan 25, 2015 at 2:36 PM, Oleg Nauman oleg.nau...@gmail.com
   wrote:
  
  
   On Fri, Jan 23, 2015 at 9:15 PM, Adam Vande More amvandem...@gmail.com
   wrote:
  
   When trying to connect to an xmpp openfire server, I keep getting the
   following error w/ kopete:
  
   There was a Transport Layer Security (TLS) error: Failed to establish a
   secure connection.
  
  
   The psi client from pkg repo allows me to accept the cert after a
   warning and connect successfully.  kopete in CentOS 7 also does the 
   same.
  
  
   How do I fix this?
  
  
I have faced the same issue with kopete so switched to kde-telepathy ;
   it is working fine. It seems kopete refuses connection to some xmpp
   services after attempts to ( incorrectly? ) fix the issue with POODLE in
   SSLv3. Well it possible that it is just coincidence.
  
  
  
   Thanks works well enough.
  
  
   The only thing concerned me with kde-telepathy it is poor recovery
  strategy after disconnection - usually it stays offline without
  reconnection attempts.
  Kopete behaves much better if link appears again - it reconnects
  automatically.
  
  Are there experimental builds of .9 available yet?  I'd like to try out the
 
 I'll try making some. Probably not today any more though.

Commited to area51. Report feedback please.

 
 Alosno

Ah, misspelling my own name ...

Alonso


pgpmWkf49TNQd.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] kopete tls issue

[Schaich, Alonso]

On Wed, 28 Jan 2015 19:57:14 +0200
Oleg Nauman oleg.nau...@gmail.com wrote:

 On Mon, Jan 26, 2015 at 10:29 PM, Adam Vande More amvandem...@gmail.com
 wrote:
 
  On Sun, Jan 25, 2015 at 2:36 PM, Oleg Nauman oleg.nau...@gmail.com
  wrote:
 
 
  On Fri, Jan 23, 2015 at 9:15 PM, Adam Vande More amvandem...@gmail.com
  wrote:
 
  When trying to connect to an xmpp openfire server, I keep getting the
  following error w/ kopete:
 
  There was a Transport Layer Security (TLS) error: Failed to establish a
  secure connection.
 
 
  The psi client from pkg repo allows me to accept the cert after a
  warning and connect successfully.  kopete in CentOS 7 also does the same.
 
 
  How do I fix this?
 
 
   I have faced the same issue with kopete so switched to kde-telepathy ;
  it is working fine. It seems kopete refuses connection to some xmpp
  services after attempts to ( incorrectly? ) fix the issue with POODLE in
  SSLv3. Well it possible that it is just coincidence.
 
 
 
  Thanks works well enough.
 
 
  The only thing concerned me with kde-telepathy it is poor recovery
 strategy after disconnection - usually it stays offline without
 reconnection attempts.
 Kopete behaves much better if link appears again - it reconnects
 automatically.
 
 Are there experimental builds of .9 available yet?  I'd like to try out the

I'll try making some. Probably not today any more though.

Alosno


pgpdqqjEtokfY.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/KDE/net-im/kopete-kde4

[Schaich, Alonso]

On Thu, 15 Jan 2015 07:18:02 -0800 (PST)
Alonso Schaich alonsoscha...@fastmail.fm wrote:

 Found by antoine@, see
 http://lists.freebsd.org/pipermail/svn-ports-all/2015-January/083174.html
 

It was Aleksander Matveev ti...@timon.net.nz who found it.

Alonso


pgpJ7U3zUqB9D.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/PORTS/www/otter-browser

[Schaich, Alonso]

On Thu, 18 Dec 2014 12:21:59 -0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Alonso Schaich alonsoscha...@fastmail.fm writes:
 
  SVN commit 10514 by aschai:
 
  Fix build of www/otter-browser
 
  The qmake port is required to be installed when compiling otter. While this
  requirement is usually met due to it's dependencies on qt5 elements which
  depend on qmake, in case someone uninstalled qmake which is not a runtime
  dependency on any qt5* port, otter would not build any more.
 
  Resolve this introducing a dependency on qmake.
 
  Reported by a build cluster, log:
  http://beefy2.isc.freebsd.org/data/10amd64-default/2014-12-17_04h21m21s/logs/otter-browser-0.9.03.log
 
 I think you only need qmake_build here, otherwise you also introduce an
 unnecessary runtime dependency on qmake.

Indeed, qmake_build might be enough. I was wondering how the build-time
only version was called but could only find qmake in the _USE_QT_ALL
and _USE_QT5_ONLY, and thought qmake_build was a qt-ports internal
thing. I'll give it a try later.
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] 4.14.3 and KMail

[Schaich, Alonso]

On Wed, 10 Dec 2014 16:53:45 -0500
Ajtim lum...@gmail.com wrote:

 Hi!
 
 The KDE 4.14.3 installed from area51 works fine but KMail has the same 
 problem 
 as it had after update of kdepim4 for KDE 4.14.2,
 

That's sad. Does the workaround Oleg Nauman wrote about here work for you?
http://mail.kde.org/pipermail/kde-freebsd/2014-November/018472.html

 Thank you.
 
 BTW: Is the area51 down?
 
 -- 
 ajtiM

It was down for some days last week, but it's up again.

Alonso


pgp68gcybxGcy.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/PORTS/devel

[Schaich Alonso]

On Sat,  6 Dec 2014 11:07:38 -0800 (PST)
Alonso Schaich alonsoscha...@fastmail.fm wrote:

 SVN commit 10505 by aschai:
 
 Fix build on FreeBSD-8
 
 KDevplatform requires a C++ 11 standard library. Force the build process to
 use a more recent compiler and library, and also do so for KDevelop because
 it includes KDevplatform's headers and also will share it's runtime
 requirements.
 
 PR:   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195742
 
 

... and use cmake:outsource.


pgpfhJOy2cecp.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/PORTS/net-im

[Schaich Alonso]

On Fri,  5 Dec 2014 16:48:53 -0800 (PST)
Alonso Schaich alonsoscha...@fastmail.fm wrote:

 SVN commit 10503 by aschai:
 
 Confusion++
 
 Hard code the one into the WRKSRC because it's a suffix to the path in the
 distribution tarball of ktp-text-ui.
 
 Also, use the normal MASTER_SITES and fix the path using SUBDIR instead.
 

... in telepathy-qt4. Without any telepathy-qt5 being around on
upstream either, I don't see a point of calling this point
telepathy-qt4 with emphasis on the 4 just to field string replacement
magic in area51 and hard coded strings in PORTS, though. Renaming this
port to telepathy-qt would likely obsolete these hacks.



pgpFazKiywKZm.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

[kde-freebsd] KDE~4.6 translations

[Schaich, Alonso]

Hello

Currently, we are having the following translation packages in
PORTS/area51 which have not seen any updated by upstream for a
considerable time:


Language Most recent KDE version
Cassubian (csb)  4.4.5
Frisian (fy) 4.5.5
Gujarati (gu)4.6.5
Kannada (kn) 4.7.4
Maithili (mai)   4.6.5
Macedonian (mk)  4.4.5
Malayalam (ml)   4.5.5
Sinhalese (si)   4.10.5
Tajik (tg)   4.11.5
Thai (th)4.10.5

While the 4.10 and 4.11 ports might still work these days I guess the
historic packages have broken (by not corresponding to any strings in
the binaries any more)

Is there any user who can comment on the listed translation's state?

Also, I'd like to drop these all together from area51 because they are
irrelevant for the kde PORTS development, unless there are objections
of cause.

Alonso


pgpvRwrfl9rwd.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] 4.14.3

[Schaich Alonso]

On Sun, 23 Nov 2014 06:50:01 -0500
Ajtim lum...@gmail.com wrote:

 Hi!
 
 I have installed KDE 4.14.2 and I did update Kdepim4 because of the problem 
 with KMail but it is not so much better now - it works few days than stopped. 
 After rebuilding again it work again but complain that cannot move files but 
 it 
 moved/sort correct than after day or two it stopped work again...
 
 Is it KDE 4.14.3 from area51 ready to install, please? As I red the problem 
 should be solved with 4.14.3 version.
 
 Thank you.
 
 -- 
 ajtiM

I wanted to CFT for it but then decided to check up kdevelop,
otter, ... and ultimately forgot about the CFT... to answer your
question it should be ready for testing.

Alonso


pgp3JuH_JaylG.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/KDE/devel/py-pykde4

[Schaich, Alonso]

On Thu, 13 Nov 2014 10:33:40 -0800 (PST)
Alonso Schaich alonsoscha...@fastmail.fm wrote:

 SVN commit 10467 by aschai:
 
 Track usage of nepomuk
 
 Nepomuk dependency came in, probably long ago (can't git blame it but it was
 around in 4.13.3). While here, fix the EXAMPLES option.

Rather than fix it should be don't waste effort.

Alonso



pgpnTBqtL0daH.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] coreutils

[Schaich, Alonso]

On Wed, 05 Nov 2014 03:09:06 -0200
brunomaxi...@openmailbox.org wrote:

 Hi folks,
 
 I notice coreutils is a dependency for kde, specifically kdepim. But I 
 tried to build kdepim removing the coreutils from Makefile and it builds 
 fine. Which are the needs to depend on coreutils? Could coreutils be 
 removed from KDE?
 And what about gcc and bash? Are they necessary too? I have tried to 
 change my default shell to /bin/sh on Debian + KDE and KDE stopped to 
 log in, but here FreeBSD I use /bin/sh as default and KDE works 
 perfectly. So why bash dependency? KDE cannot work with native FreeBSD 
 components, besides FreeBSD has its own coreutils and shell?
 
 Thanks for answer.

Hi,

KDE doesnot depend on GCC. A component of it, namely kactivitymanagerd
needs C++11 support to build a working binary (it could build but
failed at runtime), and C++11 support was originally only availible
with ports gcc or WITH_CLANG_IS_CC - however the later became the
default in FreeBSD 10, so there's no direct GCC dependency any more.
Packages used by KDE could be depending on it though.

Bash is depended on by KDE components that install bash scripts, i.e.
have bash as a runtime requirement.

Coreutils was commented on by Tobias in his reply.

Alonso


pgp6qraum4jpE.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51

[Schaich Alonso]

On Mon, 03 Nov 2014 09:54:18 +
Max Brazhnikov m...@freebsd.org wrote:

 On Wed, 16 Jul 2014 08:41:22 -0700 Alonso Schaich wrote:
  SVN commit 10180 by aschai:
  
  Update telepathy to 0.8.0.
  
  Ports provided by T.C.Berner via Mailing List. I remove PORTREVISION as 
  this is
  a version bump.
 
 
 Hi Alonso,
 
 What the status of these ports? are they ready for merging to the portstree?
 
 Max

Hi

While I don't use telepathy myself, I heard no complaints about those
ports and they've been in area51 for quite some time, so I guess they
are.

Alonso


pgp5PIUnAQDEv.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] after update to KDE 4.14.2: Virtual desktops Cube Animation not working

[Schaich, Alonso]

On Wed, 29 Oct 2014 10:54:29 +0100
Matthias Apitz g...@unixarea.de wrote:

 El día Tuesday, October 28, 2014 a las 10:16:49PM +0100, Schaich Alonso 
 escribió:
 
  You can check for OpenGL runtime support with kinfocenter (graphical
  information - opengl), you need at least OpenGL 2 for kwin AFAIK (there
  were some issues with old MESA a year ago).
 
 Here you can see the state of OpenGL in kinfocenter and the error
 messages: http://www.unixarea.de/opengl-vmware.png

KDE runs the /usr/local/lib/kde4/libexec/kwin_opengl_test application
to determine wether or not OpenGL support is sufficient, which crashes
over here [and creates a core dump called kwin_opengl_test.core in
${HOME} if the kern.coredump sysctl is set to 1]

I'll rebuild the relevant apps with debug symbols and try to analyze
this later

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] after update to KDE 4.14.2: Virtual desktops Cube Animation not working

[Schaich Alonso]

On Tue, 28 Oct 2014 22:01:30 +0100
Matthias Apitz g...@unixarea.de wrote:

 El día Tuesday, October 28, 2014 a las 10:28:07AM -0400, Dwayne MacKinnon 
 escribió:
 
  Hi Matthias,
  
  In System Settings-Desktop Effects under Simple effect setup is a 
  pulldown 
  menu for Effect for desktop switching. You can select Desktop Cube 
  Animation 
  there.
  
  I'm running 4.14.2 myself on FreeBSD 10.0-RELEASE with Desktop Cube.
 
 Hi Dwayne,
 
 Thanks for your feedback. I checked this menu too and played around
 there with values. This raises error messages like
 
 Desktop Cube Animation requires OpenGL
 (same for some other two forms, forgot the names, ...blur???)
 
 I checked the installed package for 'opengl' and I do have:
 
 # pkg-static info | fgrep -i opengl
 dri-9.1.7_6,2  OpenGL hardware acceleration drivers for the 
 DRI
 freeglut-2.8.1_3   Alternative to the OpenGL Utility Toolkit 
 (GLUT) library
 glew-1.11.0_2  The OpenGL Extension Wrangler Library
 libGL-9.1.7_3  OpenGL library that renders using GLX or DRI
 libGLU-9.0.0_2 OpenGL utility library
 libglesv2-9.1.7_3  OpenGL ES v2 library
 py27-qt4-opengl-4.11.1_1,1 Python bindings for the Qt4 toolkit, QtOpenGL 
 module
 qt4-opengl-4.8.6_2 Qt OpenGL support module
 
 The same set as on the 4.12.5 laptop (where Deskto Cube works). Any
 idea?
 

You can check for OpenGL runtime support with kinfocenter (graphical
information - opengl), you need at least OpenGL 2 for kwin AFAIK (there
were some issues with old MESA a year ago).

If you have OpenGL available on the system you can enable it's use in
systemsettings - desktop effects - advanced - compositing type.

Alonso


pgppKAO18p694.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Problems after latest upgrade

[Schaich Alonso]

On Mon, 27 Oct 2014 16:06:50 -0400
Dwayne MacKinnon d...@ncf.ca wrote:

 Update:
 
 I've been able to fix the sftp problem. I tracked it down to kio_sftp.cpp, in 
 the sftpProtocol::sftpOpenConnection method.
 
 From the error message, the problem was from this section of code (I wasn't 
 able to figure out which one. Probably the first one.)
 
  int timeout_sec = 30, timeout_usec = 0;
  
   kDebug(KIO_SFTP_DB)  Creating the SSH session and setting options;
   
   // Set timeout
   int rc = ssh_options_set(mSession, SSH_OPTIONS_TIMEOUT, timeout_sec);
   if (rc  0) {
 error(KIO::ERR_INTERNAL, i18n(Could not set a timeout.));
 return false;
   }
   rc = ssh_options_set(mSession, SSH_OPTIONS_TIMEOUT_USEC, timeout_usec);
   if (rc  0) {
 error(KIO::ERR_INTERNAL, i18n(Could not set a timeout.));
 return false;
   }
 
 
 So, apparently the problem was in the ssh_options_set call to libssh.so . I 
 went looking at the libssh API docs. 
 
 According to the libssh docs, the timeout values are supposed to be of type 
 long. As you can see above, the values are type int. 
 
 I looked at the history of the kio_sftp.cpp file on KDE's git repository. The 
 code has always been of type int. On top of that, the author of the code is 
 one of the creators of libssh.
 

In src/options.c of security/libssh, line 587 however it is clearly
hard-casted to a long integer.

Very nice spot though.

 So what I'm wondering is this: is there something about how we're compiling 
 the code now that is causing this problem? Could this be a clang vs gcc thing?
 
 Cheers,
 DMK
 

It's clearly relying on platform and compiler- (and compiler-option-)
specific behaviour. Some lines below the poor reading access that
happens to read buffer space or a prefix of the register it is not
supposed to read (depending on calling conventions in use) the code
binary ANDs away the poor prefix, however the constant is of type
signed int which AFAIK should be value-correctly promoted to it's long
counterpart, which means all bits of a long type on all supported
architectures, so there's some space for compiler specific behaviour

Anyway, this inconsistency is a bug and should be reported.

Alonso


pgpLgV3mWTsYv.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] x11/kde4-runtime

[Schaich, Alonso]

On Tue, 21 Oct 2014 23:34:09 +0200
lore...@piangatello.it lore...@piangatello.it wrote:

 I've forgot to read UPDATING and no longer have the list of files
 contained in the old package...
 
 Any hint?
 

If you are refering to the contents installed by an old version of a
port/package, it is maintained by pkg and independend of the ports tree
state, thus should find all package contents nevertheless

If you're refering to pkg-plist files themselves, you can check an old
ports tree revision (web http://svn.freebsd.org or use svnlite update
--revision old-version)

Alonso


pgpiB0WPnpkco.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/PYQT/devel/py-qt4

[Schaich Alonso]

On Wed, 22 Oct 2014 21:44:43 +0300
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Max Brazhnikov m...@freebsd.org writes:
 
  On Sun, 05 Oct 2014 12:20:38 -0700 Alonso Schaich wrote:
  SVN commit 10358 by aschai:
 
  Remove USES.
 
  devel/py-qt4 redundandly adds python USES as it's also added in the 
  included
  bsd.pyqt.mk, so it should be safe to remove it from the devel/py-qt4 
  metaport.
 
  No, it's not. USES in bsd.pyqt.mk is hidden behind PYQT4_DIST, which
  is not set in devel/py-qt4.
 
 This still needs to be fixed, right?

Yes, and no ;)

Yes, as in I did not reintroduce it, and no as in it's not broken, as
the metaport has itself no dependency on python but on packages that
depend on python instead.



pgpvDyUzlxpjJ.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] avogadro

[Schaich Alonso]

On Thu, 11 Sep 2014 19:01:38 -0400
Ajtim lum...@gmail.com wrote:

 Hi!
 
 I try to update my system FreeBSD 10.0-RELEASE-p7 #0: Tue Jul  8 06:37:44 UTC 
 2014 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  
 amd64
 
 and I got an error:
 
 === Creating a backup package for old version avogadro-1.1.1_2
 Creating package for avogadro-1.1.1_2
 Updating database digests format: 100%
 Checking integrity... done (0 conflicting)
 Deinstallation has been requested for the following 1 packages (of 0 packages 
 in the universe):
 
 Installed packages to be REMOVED:
 avogadro-1.1.1_2
 
 The operation will free 17 MB.
 [1/1] Deleting avogadro-1.1.1_2: 100%
 
 === Starting check for runtime dependencies
 === Gathering dependency list for science/avogadro from ports
 === Dependency check complete for science/avogadro
 
 === All  avogadro-1.1.1_2 (26/344)
 
 ===  Installing for avogadro-1.1.1_3
 ===  Checking if avogadro already installed
 ===   Registering installation for avogadro-1.1.1_3 as automatic
 pkg-static: 
 lstat(/usr/ports/science/avogadro/work/stage/usr/local/include/avogadro/pythonerror.h):
  
 No such file or directory
 pkg-static: 
 lstat(/usr/ports/science/avogadro/work/stage/usr/local/include/avogadro/pythoninterpreter.h):
  
 No such file or directory
 pkg-static: 
 lstat(/usr/ports/science/avogadro/work/stage/usr/local/include/avogadro/pythonscript.h):
  
 No such file or directory
 pkg-static: 
 lstat(/usr/ports/science/avogadro/work/stage/usr/local/lib/avogadro/1_1/extensions/pythonterminal.so):
  
 No such file or directory
 pkg-static: 
 lstat(/usr/ports/science/avogadro/work/stage/usr/local/lib/python2.7/site-
 packages/Avogadro.so): No such file or directory
 pkg-static: 
 lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/engineScripts/wireframe.py):
  
 No such file or directory
 pkg-static: 
 lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/extensionScripts/example.py):
  
 No such file or directory
 pkg-static: 
 lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/extensionScripts/):
  
 No such file or directory
 pkg-static: 
 lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/engineScripts/):
  
 No such file or directory
 pkg-static: 
 lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/): 
 No 
 such file or directory
 *** Error code 74
 
 Stop.
 make[1]: stopped in /usr/ports/science/avogadro
 *** Error code 1
 
 Stop.
 make: stopped in /usr/ports/science/avogadro
 
 === A backup package for avogadro-1.1.1_2 should
be located in /usr/ports/packages/portmaster-backup
 
 === Installation of avogadro-1.1.1_3 (science/avogadro) failed
 === Aborting update
 
 === Update for science/avogadro failed
 === Aborting update
 
 Thanks in advance.
 
 -- 
 ajtiM


Hi

Is this still occuring?

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] kio-mtp port

[Schaich Alonso]

On Thu, 11 Sep 2014 09:10:46 +0200
Schaich Alonso alonsoscha...@fastmail.fm wrote:

 On Thu, 11 Sep 2014 09:55:33 +0300
 Andriy Gapon a...@freebsd.org wrote:
 
  
  Is anyone up to creating a port of kio-mtp?
  https://projects.kde.org/projects/playground/base/kio-mtp
  git://anongit.kde.org/kio-mtp
  It should be a rather simple port with CMake based build and dependencies 
  for
  Qt, KDE and libmtp.
  
  I guess many people of android phones would find that useful.
  Thanks! :-)
  -- 
  Andriy Gapon
 
 I'll write it later.
 
 Alonso

... so I said eagerly, and failed. The attached port is for kio-mtp
0.75 beta 2 (most recent version as far as i could find) but does a
rather poor job at fetching/storing the distfile.

I used quickgit.kde.org over anongit.kde.org because the latter provided
empty (only .git) tarballs.

Someone with more clue than me about ports' git integration might have
to revise this.

Alonso


audio__kio-mtp.tar.xz
Description: Binary data


pgpbEOwzplAyD.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] kio-mtp port

[Schaich Alonso]

On Thu, 11 Sep 2014 09:55:33 +0300
Andriy Gapon a...@freebsd.org wrote:

 
 Is anyone up to creating a port of kio-mtp?
 https://projects.kde.org/projects/playground/base/kio-mtp
 git://anongit.kde.org/kio-mtp
 It should be a rather simple port with CMake based build and dependencies for
 Qt, KDE and libmtp.
 
 I guess many people of android phones would find that useful.
 Thanks! :-)
 -- 
 Andriy Gapon

I'll write it later.

Alonso


pgp6x8AP06hWu.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/KDE/multimedia/kdemultimedia4

[Schaich Alonso]

On Wed, 10 Sep 2014 06:16:58 +
Max Brazhnikov m...@freebsd.org wrote:

 On Tue, 09 Sep 2014 13:59:30 -0700 Alonso Schaich wrote:
  SVN commit 10271 by aschai:
  
  Link new audio/simon to the kdemultimedia metaport.
 
 simon is not a part of KDE SC, so it shouldn't be here, but in PORTS.
 Don't use KDE4_BRANCH in MASTER_SITES (it's for KDE SC ports only) and
 drop KDE4_VERSION from DIST_SUBDIR (make it similar to phonon ports)
 
 Max

Done ;)


pgphquntJTmJL.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Does Simon come bundled somewhere in KDE4?

[Schaich Alonso]

On Mon, 08 Sep 2014 11:16:13 -0400
Paul Pathiakis ppathia...@atlantisservices.net wrote:

 Hi,
 
 FreeBSD 10.
 
 I found out a lot about Simon.  I was wondering if it's already part of 
 one of the packages for KDE.  If now, when will it be?
 
 I have a log of clients that are looking to have this that are, 
 presently, using Dragon Naturally Speaking.  Is this a decent replacement?
 
 Thank you,
 
 Paul Pathiakis
 Atlantis Services
 Owner

I'll write audio/simon.

Alonso


pgpZomsX7TfdJ.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Does Simon come bundled somewhere in KDE4?

[Schaich Alonso]

On Tue, 09 Sep 2014 16:33:36 -0400
Paul Pathiakis ppathia...@atlantisservices.net wrote:

 Thank deity.  Alonso, thank you so much.
 
 The medical field uses it quite a bit so doctor's can read their notes.  
 (I'd laugh but I'm serious)
 
 So, this is for a medical research facility who are very interested.
 
 Thank you,
 
 P.

Port commited to the kde-testing repository in revision 10273, and attached
a tarball of the modified ports.

Builds and packages on my machine (TM).

Also, on your original question I don't think there's any good alternative to
dragon unless you consider non-KDE ports, where VLC might do the job.

Alonso


audio__simon.tar.xz
Description: Binary data


pgplHpRoppkH7.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

[kde-freebsd] XDG_* make environment variables

[Schaich Alonso]

Hello

About a year ago several area51 ports introduced an explicit XDG_CONFIG_HOME
and/or XDG_DATA_DIRS assignment to /dev/null, iirc in order to prevent the
build process to create paths in the home directory of the building user.

Earlier today I was browsing some ${PORTSDIR}/Mk/... files and noticed
Mk/bsd.port.mk sets both variables to WRKDIR. The way I see this, it
should therefore be safe to remove the explicit value overloads in the
area51 ports, but I haven't tried doing so yet.

Is there anything that still needs them?

Alonso


pgp_bHh1vNMwb.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/KDE

[Schaich, Alonso]

On Sun, 6 Jul 2014 13:50:34 +0800
Alex V. Petrov alexvpet...@gmail.com wrote:

 Error build analitza:
 
 /usr/ports/math/analitza/work/analitza-4.13.2/analitzaplot/plotter2d.cpp:376:50:
 error: call to 'abs' is ambiguous
 s += computeAngleLabelByStep(std::abs(i), bigstep);
  ^~~~
 /usr/include/c++/v1/cmath:660:1: note: candidate function
 abs(float __x) _NOEXCEPT {return fabsf(__x);}
 ^
 /usr/include/c++/v1/cmath:664:1: note: candidate function
 abs(double __x) _NOEXCEPT {return fabs(__x);}
 ^
 /usr/include/c++/v1/cmath:668:1: note: candidate function
 abs(long double __x) _NOEXCEPT {return fabsl(__x);}
 ^
 [...]

Should be fixed in area51 revision 10168. Thanks for reporting.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

[kde-freebsd] qt-4.8.6

[Schaich Alonso]

Hello

I've updated area51's qt ports to version 4.8.6, which hopefuly work now.
Feel free to join testing.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Weird KDE VirtualBox problem

[Schaich Alonso]

On 2014-02-28 19:01 Dwayne MacKinnon wrote:
 Hi all,
 
 I recently upgraded my amd64 box to FreeBSD 10.0-RELEASE so that I could
 get 
 the new amd kms drivers and move up to KDE 4.11/4.12. 
 
 I've discovered an odd bug when running VirtualBox
 (emulators/virtualbox-ose) 
 under the current KDE. Namely, it won't work.
 
 When I attempt to launch VirtualBox while running KDE VirtualBox
 complains 
 that it isn't setuid root, and promptly segmentation faults. 
 
 If I run VirtualBox under twm, this problem does not occur. If I ssh -Y
 into 
 my own box from KDE, and run VirtualBox in the ssh session, the problem 
 doesn't occur.
 
 Do any of the KDE gurus here have any idea how KDE could be interfering
 with 
 VirtualBox's being setuid to root?
 
 Cheers,
 DMK

Hi,

AFAIK the segfault thing originates in the fact VirtualBox is linked
against gcc's c++ libraries while the Qt ports used by VirtualBox link
against clang's libraries by default on FreeBSD-10 which causes
undesirable side-effects. Someone posted instructions on how to build an
alternate/inofficial VirtualBox port with clang to avoid the issue to
emulation@:
http://lists.freebsd.org/pipermail/freebsd-emulation/2014-January/011224.html

Hope that helps. VirtualBox doesn't need root over here, though I need
to load the vboxdrv kernel module and start the vboxnet service both as
root in order for VirtualBox to work.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] kde update - confused

[Schaich Alonso]

On Thu, 20 Feb 2014 11:21:08 -0500
Ajtim lum...@gmail.com wrote:

 Hi!
 
 I am running KDE 4.11.4 and I like to update to 4.12 but as I
 read /usr/ports/UPDATING I am confised:
  KDE SC ports have been updated to 4.12.2. kdeadmin, kdenetwork, kdesdk,
   and kdetoys ports have been split due to upstream changes.
 
   KDE Workspace port has been updated to 4.11.6. It requires modern
   Mesa libraries, provided by WITH_NEW_XORG knob. To update Xorg ports
   to newer version follow instructions at
   https://wiki.freebsd.org/Graphics
 
 Do I need delete kdeadmin, kdenetwork, kdesdk, kdetoys? Why is KDE
 Wokspace not updated to 4.12?
 
 Thank you.
 
 
 Mitja
 ---
 http://www.redbubble.com/people/lumiwa
 ___
 kde-freebsd mailing list
 kde-freebsd@kde.org
 https://mail.kde.org/mailman/listinfo/kde-freebsd
 See also http://freebsd.kde.org/ for latest information

Hi,

The mentioned packages were split in the transition from KDE 4.10 to 4.11,
while 4.11 was either never commited to FreeBSD ports (it was an area51
only thing) or was commited there only very recently. If you're updating from
4.11 to 4.12 you don't have to bother about those packages.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Upgrade Instructions

[Schaich Alonso]

On Tue, 18 Feb 2014 12:07:42 -0600
Rusty Nejdl rne...@ringofsaturn.com wrote:

  
 
 Are there any special instructions (UPDATING is kind of sparse) about
 upgrading to the latest KDE? My first attempt ran into: 
 
 === The misc/kde4-shared-mime-info port has been deleted: Removed,
 the port not needed anymore
 === Aborting update
 
 Thanks!
 Rusty Nejdl 
  

Hi,

Removing the installed kde4-share-mime-info should allow continuing the
update process. To do so, run pkg delete kde4-shared-mime-info
if you use pkgng, or
pkg_delete kde4-shared-mime-info\*
if you use the old package tools from FreeBSD-8 and 9.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] KDE SC 4.12

[Schaich Alonso]

On Fri, 31 Jan 2014 08:46:44 +
Max Brazhnikov m...@freebsd.org wrote:

 Folks,
 
 We definitely need exp-run for 4.12 (at least due to new KDE4_PREFIX)
 before it could be committed to ports. I'm going to create patch for
 4.12.1, but later we can update area51 to 4.12.2 and commit the later.
 
 Max
 
 ___
 kde-freebsd mailing list
 kde-freebsd@kde.org
 https://mail.kde.org/mailman/listinfo/kde-freebsd
 See also http://freebsd.kde.org/ for latest information

I've installed the foundamental 4.12.1 ports on a clean 10-STABLE system, and
the only issue I ran into was textproc/raptor not building if it's BDB option
is set.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] KDE 4.12 and WITH_NEW_XORG=no

[Schaich Alonso]

On Tue, 28 Jan 2014 07:11:32 -0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 As we're finally close to getting the 4.12.1 ports into a reasonable
 stable where everything builds, I'd like to start discussing merging
 area51 back into ports -- we've already skipped the whole 4.11 release
 cycle.
 
 As I see it, the biggest question is what to do with WITH_NEW_XORG=no:
 kde4-workspace will not build with the ancient version of Mesa that gets
 build when WITH_NEW_XORG is disabled. And FreeBSD's pkg building cluster
 does not enable this variable on its 8- and 9- builds, which mean we
 wouldn't get part of the KDE packages built for those releases at all.
 ___
 kde-freebsd mailing list
 kde-freebsd@kde.org
 https://mail.kde.org/mailman/listinfo/kde-freebsd
 See also http://freebsd.kde.org/ for latest information

Hi

In a mail to stable@ which was not replied so far, ama...@li.ru reported on
2014-01-22 that he can't build even cairo (poppler) without WITH_NEW_XORG,
which both are dependecies to KDE4. I have no setup to verify this breakage at
the moment, though should this be true it means we have a broken default
setup on FreeBSD 8, 9 and 10.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] qt-everywhere-opensource-src-4.8.5.tar.gz file size mismatch

[Schaich Alonso]

On Fri, 24 Jan 2014 08:02:29 -0800
Steve Robertson srobert...@gmail.com wrote:

 Hello,
 
 I was attempting to install multimedia/vlc from ports using portmaster.
 In the process, a fetch was attempted for
 qt-everywhere-opensource-src-4.8.5.tar.gz which ended in file size
 mismatch. This was attempted 3 times from 3 different sites with the
 same error each time. I also noticed that the actual file size was
 reported as different from each of the three sites. I'm building on
 FreeBSD 10.0-RELEASE. A subsequent attempt resulted in a SHA256 Checksum
 mismatch.
 Is there a site where I can fetch the uncorrupted distfile?
 
 Thank You,
 Steve Robertson
 
 
 ___
 kde-freebsd mailing list
 kde-freebsd@kde.org
 https://mail.kde.org/mailman/listinfo/kde-freebsd
 See also http://freebsd.kde.org/ for latest information

My tarball has 241491467 bytes in size reported by stat(1) and the sha256(1)
checksum eb728f8268831dc4373be6403b7dd5d5dde03c169ad6882f9a8cb560df6aa138.

This is conforming to the distfile content. I downloaded it from the ports
default, but you should be able to download it from any of the mirrors
listed on the official qt site:

http://download.qt-project.org/official_releases/qt/4.8/4.8.5/qt-everywhere-opensource-src-4.8.5.tar.gz.mirrorlist

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] kdelibs 4.12.1

[Schaich Alonso]

On Sat, Jan 18, 2014, at 23:15, Adriaan de Groot wrote:
 On Saturday 18 January 2014 00:47:31 Adriaan de Groot wrote:
  Well, now that 4.11.5 is near, what about 4.12.1? kdelibs, at least, builds
  with only a change to x11/kdelibs4/files/patch-KDE4Defaults.cmake (since
  upstream now says 4.12.1 instead of 4.11.4).
 
 This is the patch I applied to area51 trunk to get kdelibs 4.12.1 to
 build and 
 install. I don't know if the lib-version bumps are necessary.
 
 [ade]

Hi,

The library version bumps are not neccessary, I think.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] [SVN Commit] area51/KDE/games/kdegames4

[Schaich Alonso]

On Wed, 15 Jan 2014 12:00:00 +
Max Brazhnikov m...@freebsd.org wrote:

 On Wed, 15 Jan 2014 02:08:07 -0800 Alonso Schaich wrote:
  SVN commit 9846 by aschai:
  
  Link khangman and pairs into the kdegames4 metaport.
 
 They both belong to kdeedu
 
 Max

I even checked the commit log of kdegames because it smelled fishy, but
didn't check kdeedu _

Thanks for notice.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] KDE 4.11.5

[Schaich Alonso]

On Wed, 15 Jan 2014 13:33:50 +0100
Adriaan de Groot gr...@kde.org wrote:

 So 4.11.4 is in area51 and is being polished up so it can be committed to 
 ports (I picked that up from other messages on the list recently). I have
 no ports-fu to speak of, but I could grind away on the KDE side of the
 equation by starting to build 4.11.5 or, heck, 4.12.2 which is just out.
 
 What's a good way to do that? I'd like to stick close to ports + area51 if 
 posslble. Is the following list-of-things-to-do a good start?
 
  1 bump the KDE version in KDE/Mk/bsd.Mk.kde
  2 fetch kdelibs  update distinfo
  3 try building that with the existing ports Makefile
  4 futz around till it compiles
  5 update plist from stage
  6 go to 2 with a port higher up the stack
 
 [ade] 
 ___
 kde-freebsd mailing list
 kde-freebsd@kde.org
 https://mail.kde.org/mailman/listinfo/kde-freebsd
 See also http://freebsd.kde.org/ for latest information

I have kde-4.11.5 ports here, so far I don't see any new issues but alot of
ports still need plist checking, especially the minor translation
 (KDE/misc/*) ones.

I can commit 4.11.5 which I am using as desktop over here into area51 so
others (or bots) can help with reworking the plists.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] KDE 4.11.4 and QT5

[Schaich Alonso]

On Mon, 13 Jan 2014 09:51:27 -0500
Ajtim lum...@gmail.com wrote:

 Hi!
 
 I am using KDE 4.11.3 from area51 and I have QT4 installed.
 Is it possible to install QT5 (upgrade qt4) and KDE 4.11.4 from area51,
 please. In are51 is nothing in update what I am asking for.
 
 Thank you.

You should be able to safely update to 4.11.4 without any breakages (that were
not present in 4.11.3 too), therefore there's no UPDATING notice. I'm playing
around with ports for 4.11.5 right now though it will take me some time
to build/pkg everything.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] kdesdk-poxml uses java?

[Schaich Alonso]

On Sun, 12 Jan 2014 23:13:08 +0100
Adriaan de Groot gr...@kde.org wrote:

 Since java is currently switched off (in 9-STABLE at least) I was worried
 about this line in the devel/kdesdk4 Makefile:
 
 POXML_DESC= Install po2xml and swappo (needs Java)
 
 However, I can't find any mention of java in the kdesdk4-poxml port. Why is 
 that comment there? (It was added in r9397)
 
 [ade]

Hi

I added that Java comment because, while kdesdk4-poxml doesn't need Java
itself, it requires devel/antlr, which is a Java written port.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] area51 some problems

[Schaich Alonso]

On Mon, 9 Dec 2013 23:20:51 +0800
Alex V. Petrov alexvpet...@gmail.com wrote:

 KDE 4.11.4
 
 root@alex:/home/alex # ps -ax| grep nepom
  1972  -  I   0:00,02 kdeinit4: kdeinit4: nepomukserver (kdeinit4)
 38626  -  I   0:01,11 /usr/local/kde4/bin/akonadi_nepomuk_feeder
 --identifier akonadi_nepomuk_feeder
 
 root@alex:/home/alex # ps -ax | grep virt
 27342  2  S+  0:00,00 grep virt
 
 root@alex:/home/alex # pkg info | grep virtuoso
 virtuoso-6.1.6_1   Universal SQL/Application Server
 
 In Config Nepomuk all enabled, but:
 Desktop search services are active,
 Detail shows:
 Files and Emails Calculating, but shows nothing
 
 File indexing service not running
 
 Email Indexing service is suspended
 
 Manual Backup says:
 Nepomuk does not seem to be running. Backups cannot be handled without it.
 
 
 

Am I right to assume you are using FreeBSD-10? lum...@gmail.com reported this
about a month ago and I was able reproduce crashes running
# nepomukctl status
on 10 but not on 9. IIRC this was related to C++ global instance destruction
order or something like that.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] area51 some problems

[Schaich Alonso]

On Tue, 10 Dec 2013 00:27:02 +0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Schaich Alonso alonsoscha...@fastmail.fm writes:
 
  Am I right to assume you are using FreeBSD-10? lum...@gmail.com reported
  this about a month ago and I was able reproduce crashes running
  # nepomukctl status
  on 10 but not on 9. IIRC this was related to C++ global instance
  destruction order or something like that.
 
 Interesting, I'm also able to reproduce the crash on my 11-CURRENT
 system with KDE from git master. It really looks related to libcxxrt
 being used instead of libstdc++ (which explains why it works on anything
  10).
 
 The backtrace looks like this:
 
 #0  0x0008023c6a2a in thr_kill () from /lib/libc.so.7
 #1  0x00080248d359 in abort () from /lib/libc.so.7
 #2  0x000801d158e9 in __cxa_pure_virtual () from /lib/libcxxrt.so.1
 #3  0x00080095b898 in QTextCodec::fromUnicode (this=0x8044181f0,
 #in=0x8044a099a, length=27, state=0x8044a2160)
 #at 
 /s/kde/src/build/qt4/src/corelib/../../include/QtCore/../../../../qt4/src/corelib/codecs/qtextcodec.h:118
 #4  0x0008009ca468 in QTextStreamPrivate::flushWriteBuffer
 #(this=0x8044a2100) at /s/kde/src/qt4/src/corelib/io/qtextstream.cpp:674 5
 #0x0008009cb716 in QTextStream::~QTextStream (this=0x60b5e0 out)
 #at /s/kde/src/qt4/src/corelib/io/qtextstream.cpp:1149 6
 #0x000802469b4b in __cxa_finalize () from /lib/libc.so.7 7
 #0x00080241133c in exit () from /lib/libc.so.7 8  0x004028c6 in
 #_start ()
 
 Some quick investigation shows that QIconvCodec ends up being destroyed
 before all the objects that use it, and at the point of the crash
 there's a call to a pointer that used to be a QIconvCodec and is now
 just a QTextCodec, and the method call goes to a pure virtual method.
 
 To be honest, I'm not sure if this is related to the lots of iconv
 changes that went into HEAD during the past few months or if it's just
 libcxxrt-related (or even if it's a bug on FreeBSD at all, for that
 matter).
 
 Alonso, do you have a link to the thread you mentioned?

http://mail.kde.org/pipermail/kde-freebsd/2013-November/016355.html
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] soprano

[Schaich Alonso]

On Wed, 27 Nov 2013 08:33:38 -0500
Ajtim lum...@gmail.com wrote:

 Update Soprano from area51, FreeBSD 10.0-BETA3, KDE 4.11.3:
 
  Compressing man pages (compress-man)
 ===  Installing for soprano-2.9.4
 ===  Checking if textproc/soprano already installed
 ===   Registering installation for soprano-2.9.4 as automatic
 pkg-static:
 (soprano-2.9.4) 
 /usr/ports/textproc/soprano/work/stage//usr/local/bin/onto2vocabularyclass
 - shared library libsoprano.so.4 not found pkg-static:
 (soprano-2.9.4) 
 /usr/ports/textproc/soprano/work/stage//usr/local/bin/sopranocmd
 - shared library libsoprano.so.4 not found pkg-static:
 (soprano-2.9.4) 
 /usr/ports/textproc/soprano/work/stage//usr/local/bin/sopranocmd
 - shared library libsopranoclient.so.1 not found pkg-static:
 (soprano-2.9.4) 
 /usr/ports/textproc/soprano/work/stage//usr/local/bin/sopranocmd
 - shared library libsopranoindex.so.1 not found pkg-static:
 (soprano-2.9.4) /usr/ports/textproc/soprano/work/stage//usr/local/bin/sopranod
 - shared library libsoprano.so.4 not found pkg-static:
 (soprano-2.9.4) /usr/ports/textproc/soprano/work/stage//usr/local/bin/sopranod
 - shared library libsopranoserver.so.1 not found pkg-static:
 (soprano-2.9.4) /usr/ports/textproc/soprano/work/stage//usr/local/bin/sopranod
 - shared library libsopranoindex.so.1 not found Installing soprano-2.9.4...
 done ==
 
 You'll have to install databases/virtuoso to use Soprano's Virtuoso
 backend.
 
 ==
 
 
 === pkg-message for soprano-2.9.4
 ==
 
 You'll have to install databases/virtuoso to use Soprano's Virtuoso
 backend.
 
 ==
 
 === Done displaying pkg-message files
 
 === Re-installation of soprano-2.9.4 complete
 
 Thank you.
 
 -- 
 Mitja

I *think* those warnings can be ignored (probably originate in the fact bin/*
is installed prior to lib/*) and are produced only with pkg-1.2 which hit
ports yesterday. Soprano works here after reinstallation.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Missing startx on FreeBSD-10 with KDE4

[Schaich Alonso]

On 2013-11-19 2013 07:05:19 -0500
Gerard Seibert je...@seibercom.net wrote:

 I recently did a fresh install of FreeBSD-10 BETA3 amd64. I have now done
 an install via the ports system of KDE4 , x11/kde4. Now I find I cannot
 start the program. There is no startx or startkde program on my PC. Has
 something changed in the latest version of KDE4 or with FreeBSD-10? Is
 there a new recommended way of starting this application?
 

Hi,

The startx application is not part of KDE, but of Xorg instead. It is
installed by selecting the XINIT option of x11/xorg-apps or by hand with
the x11/xinit port.

The startkde4 script is in /usr/local/kde4/bin by default, as Matthias Apitz
already stated in his reply. That path is not added to your user's PATH by
the ports system, however, the KDM login manager will extend that path to any
sessions started by it.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Qt4 ports are too bloated: part 1 (devel/qt4-designer)

[Schaich Alonso]

On 2013-11-19 14:43:27 +0100
Schaich Alonso alonsoscha...@fastmail.fm wrote:
 [...]

And for the second time, my mail to Alexey Dokuchaev was rejected with

 da...@nsu.ru: host mail.nsu.ru[84.237.50.3] said: 550-sender IP address
 66.111.4.27 is locally blacklisted here. If you think 550 this is wrong,
 get in touch with postmaster (in reply to RCPT TO command)

Maybe someone else can relay him it's already in.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] run command

[Schaich Alonso]

On Wed, 13 Nov 2013 15:29:10 +0100
Bengt Ahlgren ben...@sics.se wrote:

 Ajtim lum...@gmail.com writes:
 
  OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013
  r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
  KDE 4.11.3 from area51
 
  ALT-F2 or Run Command from Application Launcher Menu open but when I
  want to write a command it closed. It is not usable.
  Is it related to almost everything built with clang, please?

Interesting, I have 10-BETA3 r257917 and kde-4.11.3 built completely with
clang (that is, all of KDE that builds with clang), and the launcher works
fine - it also worked with all versions of KDE=4.11.1 and FreeBSD-10 since
ALPHA1. I had that issue with FreeBSD9-STABLE and KDE-4.10.x in the past
though (thought it was fixed upstream).

 
 A me too - I get the same with kde-4.10.5_1 built on 9.1 with default
 compiler (gcc?).  When crashing it says:
 
 Null pointer in call to GeoDataTreeModel::addFeature (parent 0x82ccac048  -
 feature 0x0 )
 
 Another observation: I often get one or two core files after exiting
 KDE.  One kdeinit4.core, and often also an kactivitymanagerd.core.
 Things seem to work, however.
 
 Bengt

GeoDataTreeModel is from marble, as was written by Adriaan de Groot in the
other reply.

kactivitymanagerd needed to be built either with gcc=4.6 (not the base one)
or clang-devel for some time, though that should be done by the port itself
in the meantime (it was back in the clang-3.2 times, 3.3 builds it fine).

FreeBSD-9.1 ships with clang-3.1 IIRC, so the base clang won't build a working
kactivitymanagerd. Can you rebuild and retry it with WITH_GCC=any?

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] 4.11.2 sanity

[Schaich Alonso]

On Wed, 13 Nov 2013 13:51:07 -0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Schaich Alonso alonsoscha...@fastmail.fm writes:
 
  *** science/kalzium (science/openbabel)
 
 I've just fixed openbabel in ports (r333701), can you check if it solves
 your problems?

Builds and works over here now.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] run command

[Schaich Alonso]

On Wed, 13 Nov 2013 14:20:39 -0500
Ajtim lum...@gmail.com wrote:

 On Wednesday 13 November 2013 18:48:08 Schaich Alonso wrote:
  On Wed, 13 Nov 2013 15:29:10 +0100
  Bengt Ahlgren ben...@sics.se wrote:
  
   Ajtim lum...@gmail.com writes:
   
OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
KDE 4.11.3 from area51
   
ALT-F2 or Run Command from Application Launcher Menu open but when I
want to write a command it closed. It is not usable.
Is it related to almost everything built with clang, please?
  
  Interesting, I have 10-BETA3 r257917 and kde-4.11.3 built completely with
  clang (that is, all of KDE that builds with clang), and the launcher works
  fine - it also worked with all versions of KDE=4.11.1 and FreeBSD-10
  since ALPHA1. I had that issue with FreeBSD9-STABLE and KDE-4.10.x in the
  past though (thought it was fixed upstream).
  
 
 Yes, it is interesting because my installation was so smooth with clang
 except kalzium and avogadro. I am not sure if I had more problems. But now
 I have.
 

avogadro was fixed earlier today, kalzium works fine since that.

does klauncher work if you remove marble?
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] 4.11.2 sanity

[Schaich Alonso]

On Tue, 12 Nov 2013 22:13:52 +0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Schaich Alonso alonsoscha...@fastmail.fm writes:
 
  *** net-im/kopete-kde4 doesn't support staging
 
 USES=webplugin has recently been added to the ports tree, and it
 probably solves the Kopete problem. Willing to give it a try? :-)

I adapted it and well it compiles now (and packages with staging enabled),
so I've commited it :D

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] something is wrong - forgot

[Schaich Alonso]

On Fri, 08 Nov 2013 16:24:42 -0500
Ajtim lum...@gmail.com wrote:

 On Thursday 07 November 2013 16:05:15 you wrote:
  On Thu, 07 Nov 2013 09:53:21 -0500
  Ajtim lum...@gmail.com wrote:
  
   
   ajtim@lumiwa:~% qdbus org.kde.NepomukServer /nepomukserver quit
   
   ajtim@lumiwa:~% /usr/local/kde4/bin/nepomukserver 
   [1] 1728
   ajtim@lumiwa:~% QDBusConnection: session D-Bus connection created before
   QCoreApplication. Application may misbehave. Application
   '/usr/local/kde4/bin/nepomukstorage ' exited normally...
   
   
  
  exited normally... sounds good. The QApplication diagnostic can be
  ignored.
  
  On your other mail, root user cannot see the DBUS session because
  root's shell does not know the DBUS environment variables.
  
  Is it still crashing on your nepomukstorage activity?
  
  Alonso
 
 I am searching but I didn't found anything.
 But when  I try to check status I got Abort (core dump- nepomukctl.core)
 ajtim@lumiwa:~% ps aux | grep nepomuk
 ajtim 41736  2.5  0.5 14  38488  2  S 4:20PM
 0:00.40 /usr/local/kde4/bin/nepomukserver ajtim 41715  0.0  0.6 323288
 54068  -  I 4:14PM 0:00.47 /usr/local/kde4/bin/akonadi_nepomuk_feeder
 --identifier akona ajtim 41739  0.0  0.0  18732   2152  2  S+4:20PM
 0:00.00 grep nepomuk ajtim@lumiwa:~% /usr/local/kde4/bin/nepomukctl status
 Abort (core dumped)
 
 Thanks.
 -- 
 Mitja
 

Also, this works fine on FreeBSD-9 STABLE (WITH_CLANG_IS_CC).

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] something is wrong - forgot

[Schaich Alonso]

On Fri, 08 Nov 2013 16:24:42 -0500
Ajtim lum...@gmail.com wrote:

 On Thursday 07 November 2013 16:05:15 you wrote:
  On Thu, 07 Nov 2013 09:53:21 -0500
  Ajtim lum...@gmail.com wrote:
  
   
   ajtim@lumiwa:~% qdbus org.kde.NepomukServer /nepomukserver quit
   
   ajtim@lumiwa:~% /usr/local/kde4/bin/nepomukserver 
   [1] 1728
   ajtim@lumiwa:~% QDBusConnection: session D-Bus connection created before
   QCoreApplication. Application may misbehave. Application
   '/usr/local/kde4/bin/nepomukstorage ' exited normally...
   
   
  
  exited normally... sounds good. The QApplication diagnostic can be
  ignored.
  
  On your other mail, root user cannot see the DBUS session because
  root's shell does not know the DBUS environment variables.
  
  Is it still crashing on your nepomukstorage activity?
  
  Alonso
 
 I am searching but I didn't found anything.
 But when  I try to check status I got Abort (core dump- nepomukctl.core)
 ajtim@lumiwa:~% ps aux | grep nepomuk
 ajtim 41736  2.5  0.5 14  38488  2  S 4:20PM
 0:00.40 /usr/local/kde4/bin/nepomukserver ajtim 41715  0.0  0.6 323288
 54068  -  I 4:14PM 0:00.47 /usr/local/kde4/bin/akonadi_nepomuk_feeder
 --identifier akona ajtim 41739  0.0  0.0  18732   2152  2  S+4:20PM
 0:00.00 grep nepomuk ajtim@lumiwa:~% /usr/local/kde4/bin/nepomukctl status
 Abort (core dumped)
 
 Thanks.
 -- 
 Mitja

I can reproduce this one over here. Adding back kde@ and also a backtrace of
the crash. It indicates a poor dynamic_cast in kconfig, which is also causing
trouble in marble IIRC.

Also, can anyone else not build x11/kdelibs4 with USE_GCC=any on FreeBSD-10?
I'm getting meinproc4 segfaults at parallel build and undefined symbols at
linking with MAKE_JOBS_UNSAFE over here.

Alonso
alonso@harmony /tmp % gdb761 $(which nepomukctl)
GNU gdb (GDB) 7.6.1 [GDB v7.6.1 for FreeBSD]
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-portbld-freebsd10.0.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/local/kde4/bin/nepomukctl...done.
(gdb) run status
Starting program: /usr/local/kde4/bin/nepomukctl status
[New LWP 101705]
[New Thread 804406400 (LWP 101705)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 804406400 (LWP 101705)]
0x in ?? ()
(gdb) backtrace
#0  0x in ?? ()
#1  0x00080151b072 in __cxxabiv1::__dynamic_cast (src_ptr=0x80441aca0, 
src_type=0x8014523d8 typeinfo for KConfigBase, 
dst_type=0x801452470 typeinfo for KConfigGroup, src2dst=0) at 
../../.././../gcc-4.6.4/libstdc++-v3/libsupc++/dyncast.cc:61
#2  0x000801066789 in KConfigGroupPrivate::create (master=0x80441aca0, 
name=..., isImmutable=false, isConst=false)
at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/config/kconfiggroup.cpp:112
#3  0x0008010607cd in KConfigGroup::KConfigGroup (this=optimized out, 
master=0x80441aca0, _group=...)
at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/config/kconfiggroup.cpp:468
#4  0x0008010fb245 in KStandardDirs::addCustomized (this=0x804418430, 
config=0x80441aca0)
at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/kernel/kstandarddirs.cpp:1964
#5  0x0008010f23d6 in KComponentDataPrivate::lazyInit (this=0x80441bee0, 
component=...)
at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/kernel/kcomponentdata.cpp:142
#6  0x0008010f2295 in KComponentData::KComponentData (this=0x804418420, 
name=..., catalog=..., 
registerAsMain=KComponentData::SkipMainComponentRegistration)
at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/kernel/kcomponentdata.cpp:82
#7  0x0008010f1f03 in KGlobalPrivate::initFakeComponent () at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/kernel/kglobal.cpp:116
#8  0x0008010f13bb in $_1::operator- (this=optimized out) at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/kernel/kglobal.cpp:128
#9  0x0008010f1470 in KGlobal::config () at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/kernel/kglobal.cpp:141
#10 0x00080119d209 in KSycocaPrivate::KSycocaPrivate (this=0x80446b500)
at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/sycoca/ksycoca.cpp:106
#11 0x00080119d5bf in KSycoca::KSycoca (this=0x80441a900) at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/sycoca/ksycoca.cpp:182
#12 0x00080119f369 in KSycocaSingleton::sycoca (this=0x804419348) at 
/usr/obj/usr/ports/x11/kdelibs4/work/kdelibs-4.11.3/kdecore/sycoca/ksycoca.cpp:166
#13 0x00080119e723 in KSycoca::self () at 

[kde-freebsd] QTextCodec issues - was something is wrong - forgot

[Schaich Alonso]

On Sat, 9 Nov 2013 00:02:45 +0100
Schaich Alonso alonsoscha...@fastmail.fm wrote:
 
 I can reproduce this one over here. Adding back kde@ and also a backtrace of
 the crash. It indicates a poor dynamic_cast in kconfig, which is also
 causing trouble in marble IIRC.
 
 Also, can anyone else not build x11/kdelibs4 with USE_GCC=any on FreeBSD-10?
 I'm getting meinproc4 segfaults at parallel build and undefined symbols at
 linking with MAKE_JOBS_UNSAFE over here.
 
 Alonso

Having built sysutils/nepomuk-core with base clang now, it shows up a bug in
qt4-corelib, where QTextCodec::codecForLocale () returns an invalid
QIconvCodec instance to QTextStream's flushWriteBuffer member procedure which
is called by the destructor on application's termination.

Most probably this happens because the QIconvCodec instance has already been
destroyed at this point.

Btw, even if I define my language settings (LANG, LC_ALL, ...) accordingly and
have chinese/qt4-codecs-zh, japanese/qt4-codecs-jp, ... installed, I still
get the QIconvCodec from QTextCodec::codecForLocale(), which makes me wonder
whether these ports are good for FreeBSD-8/9 only or maybe not required at all
any more?

Alonso
Program received signal SIGABRT, Aborted.
[Switching to Thread 804006400 (LWP 101686)]
0x000801f30dfa in thr_kill () from /lib/libc.so.7
(gdb) backtrace
#0  0x000801f30dfa in thr_kill () from /lib/libc.so.7
#1  0x000801ff8659 in abort () from /lib/libc.so.7
#2  0x0008018688e9 in __cxa_pure_virtual () from /lib/libcxxrt.so.1
#3  0x0008009bdbb5 in QTextStreamPrivate::flushWriteBuffer 
(this=0x80407c100) at io/qtextstream.cpp:670
#4  0x0008009bef66 in QTextStream::~QTextStream (this=0x6059a0 out) at 
io/qtextstream.cpp:1149
#5  0x000801fd4e4b in __cxa_finalize () from /lib/libc.so.7
#6  0x000801f7c63c in exit () from /lib/libc.so.7
#7  0x00402646 in _start ()___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Axing devel/kdevelop-custom-buildsystem?

[Schaich Alonso]

On Wed, 06 Nov 2013 20:04:24 +0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 kdevelop-custom-buildsystem is incompatible with the whole 4.5/1.5
 KDevelop series, and was last updated upstream a year and a half ago.
 
 Can I svn rm it from trunk/area51/PORT/devel?

Ok for me too.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] 4.11.2 sanity

[Schaich Alonso]

On Wed, 06 Nov 2013 17:21:17 +0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Schaich Alonso alonsoscha...@fastmail.fm writes:
 
  Hello,
 
  So far, I have localy updated all are51/KDE ports to 4.11.3 and
  packaged/installed them. Doing so, I ran into the following issues:
 
  * dependencies cannot be built
  *** astro/kstar (astro/wcslib)
 
 Does http://www.freebsd.org/cgi/query-pr.cgi?pr=183718 solve your
 problem with wcslib or is it something else?

As it didn't stage I've played around with wcslib for a bit now and found it
additionally needs MAKE_JOBS_UNSAFE in order to build over here. Otherwise it
will drop the -fPIC at some point, fail to link (the make process ignores it
though) and create a defunct package (over here).
Build logs attached, grep for undefined reference ;)

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] 4.11.2 sanity

[Schaich Alonso]

On Wed, 6 Nov 2013 20:45:08 +0100
Schaich Alonso alonsoscha...@fastmail.fm wrote:

 On Wed, 06 Nov 2013 17:21:17 +0200
 Raphael Kubo da Costa rak...@freebsd.org wrote:
 
  Schaich Alonso alonsoscha...@fastmail.fm writes:
  
   Hello,
  
   So far, I have localy updated all are51/KDE ports to 4.11.3 and
   packaged/installed them. Doing so, I ran into the following issues:
  
   * dependencies cannot be built
   *** astro/kstar (astro/wcslib)
  
  Does http://www.freebsd.org/cgi/query-pr.cgi?pr=183718 solve your
  problem with wcslib or is it something else?
 
 As it didn't stage I've played around with wcslib for a bit now and found it
 additionally needs MAKE_JOBS_UNSAFE in order to build over here. Otherwise
 it will drop the -fPIC at some point, fail to link (the make process
 ignores it though) and create a defunct package (over here).
 Build logs attached, grep for undefined reference ;)
 
 Alonso

ehhhm... attached.
root@harmony:/usr/ports/astro/wcslib # make stage
===  Found saved configuration for wcslib-4.13.4
===   wcslib-4.13.4 depends on file: /usr/local/sbin/pkg - found
=== Fetching all distfiles required by wcslib-4.13.4 for building
===  Extracting for wcslib-4.13.4
= SHA256 Checksum OK for wcslib-4.13.4.tar.bz2.
===  Patching for wcslib-4.13.4
===  Applying FreeBSD patches for wcslib-4.13.4
===   Ignoring patchfile /usr/ports/astro/wcslib/files/patch-GNUmakefile.orig
===   wcslib-4.13.4 depends on executable: gmake - found
===   wcslib-4.13.4 depends on shared library: cfitsio - found
===  Configuring for wcslib-4.13.4
===   FreeBSD 10 autotools fix applied to 
/usr/obj/usr/ports/astro/wcslib/work/wcslib-4.13.4/configure
configure: loading site script /usr/ports/Templates/config.site
checking build system type... amd64-portbld-freebsd10.0
checking for flex... flex
configure: Using Flex version 2.5.37.
checking for gcc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking how to run the C preprocessor... cpp
checking for gcc... (cached) cc
checking whether we are using the GNU C compiler... (cached) yes
checking whether cc accepts -g... (cached) yes
checking for cc option to accept ISO C89... (cached) none needed
checking for cc option to accept ISO C99... none needed
checking for cc option to accept ISO Standard C... (cached) none needed
checking for an ANSI C-conforming const... yes
checking for grep that handles long lines and -e... (cached) /usr/bin/grep
checking for egrep... (cached) /usr/bin/egrep
checking for ANSI C header files... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for memory.h... (cached) yes
checking for strings.h... (cached) yes
checking for inttypes.h... (cached) yes
checking for stdint.h... (cached) yes
checking for unistd.h... (cached) yes
checking for size_t... (cached) yes
checking for off_t... (cached) yes
checking for int8_t... (cached) yes
checking for int16_t... (cached) yes
checking for int32_t... (cached) yes
checking for uint8_t... (cached) yes
checking for uint16_t... (cached) yes
checking for uint32_t... (cached) yes
checking for ANSI C header files... (cached) yes
checking for ctype.h... (cached) yes
checking for errno.h... (cached) yes
checking for limits.h... (cached) yes
checking for math.h... (cached) yes
checking setjmp.h usability... yes
checking setjmp.h presence... yes
checking for setjmp.h... yes
checking for stdarg.h... (cached) yes
checking for stdio.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for floor in -lm... yes
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking for function prototypes... yes
checking whether setvbuf arguments are reversed... no
checking whether lstat dereferences a symlink specified with a trailing 
slash... (cached) yes
checking whether stat accepts an empty string... no
checking for vprintf... (cached) yes
checking for _doprnt... no
checking for floor... yes
checking for memset... (cached) yes
checking for pow... yes
checking for sqrt... yes
checking for strchr... yes
checking for strstr... yes
checking for cosd in -lsunmath... no
checking for sincos... no
checking for int... (cached) yes
checking size of int... 4
checking for long int... yes
checking size of long int... 8
checking for long long int... (cached) yes
checking size of long long int... 8
checking for printf z format modifier

Re: [kde-freebsd] 4.11.2 sanity

[Schaich Alonso]

On Tue, 05 Nov 2013 08:15:22 -0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Alberto Villa avi...@freebsd.org writes:
 
  On Tue, Nov 5, 2013 at 2:48 AM, Schaich Alonso
  alonsoscha...@fastmail.fm wrote:
  I have merged the umbrello patches and can build it with clang/libc++
  now. Step however still fails even with the patch added. I have attached
  the build outputs of step and also telepathy-qt4.
 
  The telepathy-qt4 one is already on my schedule, and I've got some
  more debug output by Atjim. Unless someone fixes it in the next hours,
  I should be able to take care of it.
 
 Oops. telepathy-qt4 is failing because you're probably using devel/cmake
 2.8.12 from area51.
 
 If so, you need
 http://people.freebsd.org/~rakuco/cmake-2.8.12-fix-ports.diff to fix
 some ports that relied on an internal CMake macro that had its arguments
 changed in this release.
 
 I'm probably going to commit the CMake update to ports later today and
 this should be fixed.

Applying that patches, I can build telepathy-qt4 over here. krdc and krfb
which both depend on it don't cause any trouble either any more.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

[kde-freebsd] 4.11.2 sanity

[Schaich Alonso]

Hello,

So far, I have localy updated all are51/KDE ports to 4.11.3 and
packaged/installed them. Doing so, I ran into the following issues:

* dependencies cannot be built
*** astro/kstar (astro/wcslib)
*** net/krdc (net-im/telepathy-qt4)
*** net/krfb (net-im/telepathy-qt4)
*** science/kalzium (science/openbabel)

* fails to compile (with either clang and gcc46)
*** science/step
*** science/rocs

* fails to run
*** astro/marble

* sub-optimal, but works
*** devel/kdesdk4-umbrello now needs gcc - or rather gcc's libstdc++
*** net-im/kopete-kde4 doesn't support staging
*** x11/kde4-workspace doesn't support staging

All on FreeBSD10-BETA3, I didn't test FreeBSD-9.2 or 8.4 yet, nor the base
gcc build. Can anyone using these from area51's KDE-4.11.2 tell me whether
some of the mentioned ports work there?

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] 4.11.2 sanity

[Schaich Alonso]

On Tue, 05 Nov 2013 01:02:59 +0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Schaich Alonso alonsoscha...@fastmail.fm writes:
 
  Hello,
 
  So far, I have localy updated all are51/KDE ports to 4.11.3 and
  packaged/installed them. Doing so, I ran into the following issues:
 
  * dependencies cannot be built
  *** astro/kstar (astro/wcslib)
  *** net/krdc (net-im/telepathy-qt4)
  *** net/krfb (net-im/telepathy-qt4)
  *** science/kalzium (science/openbabel)
 
  * fails to compile (with either clang and gcc46)
  *** science/step
  *** science/rocs
 
  * fails to run
  *** astro/marble
 
  * sub-optimal, but works
  *** devel/kdesdk4-umbrello now needs gcc - or rather gcc's libstdc++
  *** net-im/kopete-kde4 doesn't support staging
  *** x11/kde4-workspace doesn't support staging
 
 Thanks for working on this.
 
 I fixed science/step in ports today, the same commit can be backported
 to area51.
 
 kdesdk4-umbrello has fixes up for review upstream, but you can already
 take the first 2 commits in
 http://article.gmane.org/gmane.linux.umbrello.devel/11419 to test.
 
 I'm not aware of telepathy-qt4 failing on any FreeBSD release, and I
 haven't checked the other problems yet.

Hi

Thanks for the hint on the patches.

I have merged the umbrello patches and can build it with clang/libc++ now.
Step however still fails even with the patch added. I have attached the
build outputs of step and also telepathy-qt4.

Alonso
root@harmony:/usr/ports # make MAKE_JOBS_UNSAFE=yes -C net-im/telepathy-qt4 
===   telepathy-qt4-0.9.3 depends on file: /usr/local/bin/python2.7 - found
===   telepathy-qt4-0.9.3 depends on executable: python - found
===   telepathy-qt4-0.9.3 depends on file: /usr/local/bin/cmake - found
===   telepathy-qt4-0.9.3 depends on executable: pkgconf - found
===   telepathy-qt4-0.9.3 depends on package: gstreamer-plugins=0.10.0 - found
===   telepathy-qt4-0.9.3 depends on file: /usr/local/lib/qt4/libQtDBus.so - 
found
===   telepathy-qt4-0.9.3 depends on file: /usr/local/lib/qt4/libQtGui.so - 
found
===   telepathy-qt4-0.9.3 depends on file: /usr/local/bin/moc-qt4 - found
===   telepathy-qt4-0.9.3 depends on file: /usr/local/lib/qt4/libQtNetwork.so 
- found
===   telepathy-qt4-0.9.3 depends on file: /usr/local/bin/qmake-qt4 - found
===   telepathy-qt4-0.9.3 depends on file: /usr/local/lib/qt4/libQtTest.so - 
found
===   telepathy-qt4-0.9.3 depends on file: /usr/local/bin/rcc - found
===   telepathy-qt4-0.9.3 depends on file: /usr/local/bin/uic-qt4 - found
===   telepathy-qt4-0.9.3 depends on file: /usr/local/lib/qt4/libQtXml.so - 
found
===   telepathy-qt4-0.9.3 depends on executable: xsltproc - found
===   telepathy-qt4-0.9.3 depends on shared library: telepathy-farsight - found
===   telepathy-qt4-0.9.3 depends on shared library: telepathy-glib - found
===   telepathy-qt4-0.9.3 depends on shared library: xml2.5 - found
===  Configuring for telepathy-qt4-0.9.3
/usr/bin/sed -i.bak -e '/FIND_PROGRAM/ s/qmake //'  
/usr/obj/usr/ports/net-im/telepathy-qt4/work/telepathy-qt-0.9.3/cmake/modules/FindQt.cmake
/usr/bin/sed -i.bak -e '/^add_dependencies(doxygen-doc / d'  
/usr/obj/usr/ports/net-im/telepathy-qt4/work/telepathy-qt-0.9.3/TelepathyQt/CMakeLists.txt
/usr/bin/sed -i.bak -e '/TelepathyQt.*\.pc/ s|pkgconfig|../libdata/pkgconfig|'  
/usr/obj/usr/ports/net-im/telepathy-qt4/work/telepathy-qt-0.9.3/TelepathyQt/CMakeLists.txt
  
/usr/obj/usr/ports/net-im/telepathy-qt4/work/telepathy-qt-0.9.3/TelepathyQt/Farsight/CMakeLists.txt
/usr/bin/sed -i.bak -e '/${LIBXML2_INCLUDE_DIR}/ s|$| /usr/local/include|'  
/usr/obj/usr/ports/net-im/telepathy-qt4/work/telepathy-qt-0.9.3/TelepathyQt/Farsight/CMakeLists.txt
===  Performing in-source build
/bin/mkdir -p /usr/obj/usr/ports/net-im/telepathy-qt4/work/telepathy-qt-0.9.3
-- Could NOT find QHELPGENERATOR (missing:  QHELPGENERATOR_EXECUTABLE) 
-- Found Python executable: /usr/local/bin/python2.7
-- Found Python version: 2.7.5
-- Python 2.7 found
-- Found GObject libraries: gobject-2.0;glib-2.0;intl
-- Found GObject includes : /usr/local/include/glib-2.0
-- checking for module 'farstream-0.1=0.1.0'
--   package 'farstream-0.1=0.1.0' not found
-- Could NOT find Farstream (missing:  FARSTREAM_LIBRARIES 
FARSTREAM_INCLUDE_DIR) 
-- checking for module 'telepathy-farstream=0.2.2'
--   package 'telepathy-farstream=0.2.2' not found
-- Could NOT find TelepathyFarstream (missing:  TELEPATHY_FARSTREAM_LIBRARIES 
TELEPATHY_FARSTREAM_INCLUDE_DIR) 
CMake Error at cmake/modules/FindQt.cmake:77 (QT4_CREATE_MOC_COMMAND):
  QT4_CREATE_MOC_COMMAND Macro invoked with incorrect arguments for macro
  named: QT4_CREATE_MOC_COMMAND
Call Stack (most recent call first):
  cmake/modules/TpQtMacros.cmake:181 (qt_create_moc_command)
  cmake/modules/TpQtMacros.cmake:198 (tpqt_generate_moc_i)
  examples/accounts/CMakeLists.txt:12 (tpqt_generate_mocs)


CMake Error at cmake/modules/FindQt.cmake:77 (QT4_CREATE_MOC_COMMAND):
  QT4_CREATE_MOC_COMMAND Macro invoked with incorrect arguments for macro

Re: [kde-freebsd] something is wrong

[Schaich Alonso]

On Sun, 03 Nov 2013 07:34:35 -0500
Ajtim lum...@gmail.com wrote:
 
  
  Identifier: akonadi_nepomuk_feeder
  Type: Akonadi Nepomuk Feeder
  Status: Offline, Broken
  Status Message: Waiting for the Nepomuk to start
  Capabilities: Unique, Autostart
  Mimetypes: text/directory
  
  If I restart nothing happened.
  
  
  
 
 I forgot to wrote that I have nepomukstorage.core in home directory.
 Thank you.
 
 -- 
 Mitja

Hi,

I think I've readt somewhere that ffmpeg2 is causing nepomuk issues. Can you
check the coredump where it crashed?

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] something is wrong

[Schaich Alonso]

On Sun, 03 Nov 2013 14:48:19 -0500
Ajtim lum...@gmail.com wrote:

 On Sunday 03 November 2013 19:14:41 Schaich Alonso wrote:
  On Sun, 03 Nov 2013 07:34:35 -0500
  Ajtim lum...@gmail.com wrote:
   

Identifier: akonadi_nepomuk_feeder
Type: Akonadi Nepomuk Feeder
Status: Offline, Broken
Status Message: Waiting for the Nepomuk to start
Capabilities: Unique, Autostart
Mimetypes: text/directory

If I restart nothing happened.



   
   I forgot to wrote that I have nepomukstorage.core in home directory.
   Thank you.
   
  
  Hi,
  
  I think I've readt somewhere that ffmpeg2 is causing nepomuk issues. Can
  you check the coredump where it crashed?
  
  Alonso
 
 (gdb) core nepomukstorage.core
 Core was generated by `nepomukstorage'.
 Program terminated with signal 11, Segmentation fault.
 #0  0x in ?? ()
 (gdb) bt
 #0  0x in ?? ()
 #1  0x0008040d2072 in ?? ()
 #2  0x00080b41bf40 in ?? ()
 #3  0x7fffc510 in ?? ()
 #4  0x in ?? ()
 
 I don't know if I doing correct?
 
 Thank you.
 
 -- 
 Mitja

Probably you are, however the output is useless :D

Can you reinstall nepomuk-core with debug symbols and recreate the backtrace?

i.e.

sh# make -C ${PORTSDIR}/sysutils/nepomuk-core deinstall
sh# make WITH_DEBUG=yes -C ${PORTSDIR}/sysutils/nepomuk-core clean reinstall

where PORTSDIR is your ports tree path, /usr/ports by default.
Emphasis on clean reinstall instead of reinstall clean as gdb needs the
source files to be present at debug time, or at least it does over here. Then
rerun akonadi launch until it coredumps and then gdb

sh# gdb --core=nepomukstorage.core $(which nepomukstorage)
gdb# backtrace

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] rebooting laptop when KDE4 is down

[Schaich Alonso]

On Mon, 4 Nov 2013 08:28:37 +0100
Matthias Apitz g...@unixarea.de wrote:

 
 Hello,
 
 Due to a bug/problem in the new Xorg wit KMS, the X-server does not
 switch back to alpha console on termination. To power-down the laptop
 you only can user the power-off button to initiate with a short press
 the shutdown sequence. Ofc you do not see any messages of it and you
 have to hope that the machine goes to power-off state. Last day it
 happened that it did not went down and was sitting around two hours in
 my backpack in run level until the battery was finally empty :-(
 
 In short, is there a way to reboot the machine after
 /usr/local/kde4/bin/startkde terminates, something like in .xinitrc:
 
 ...
 /usr/local/kde4/bin/startkde
 /sbin/reboot
 
 but as a normal user, not as root. /sbin/reboot only works as root. Such
 a reboot would bring the machine down, reset it and you may power-off
 while going through the boot menue screen.
 
 Any ideas?
 
 Thanks
 
   matthias
 

Hi,

This isn't even KDE specific, at least XFCE will also __sometimes__ cause the
shutdown sequence to hang/crash/abort. I workaround this by using the kdm
service instead of startx to start kde, and also logging out of the kdesktop
session before shutting down the box (i.e. using kdm's shutdown option
instead of kdesktop launcher's).

Alternatively, of cause, you can install sysutils/sudo,
configure a password-free /sbin/reboot policy for your user and prefix sudo
to the reboot call in your .xinitrc.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Qt4 ports are too bloated: part 1 (devel/qt4-designer)

[Schaich Alonso]

On 2013-11-1, at 17:34, Alexey Dokuchaev wrote:
 Hi there dear KDE people,
 
 Most of Qt4 ports allow to selectively disable some heavy parts, e.g.
 phonon, webkit, gstreamer, etc.  However, our Qt4 framework does not
 allow
 to optionally disable those bits.  Previously, I've already raised this
 bug about qt4-webkit, now it's time for other Qt4 ports.
 
 Please consider attached patch to make phonon optional in qt4-designer,
 yet still on by default.  Qt4 is nice framework, but lots of people do
 not need any of its multimedia features.  Please allow us to disable
 them.
 
 ./danfe

Looks nice, and seems to work on this 9-STABLE/KDE-4.11.2 installation.
I've commited it into area51.

Thanks for the patch,
 Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] callibra

[Schaich Alonso]

On Mon, 28 Oct 2013 16:24:54 -0400
Ajtim lum...@gmail.com wrote:

 I like to install Calligra from area51 on FreeBSD 10.0-BETA1. It needs
 to install llwm 3.2. I have on my system llwm 3.3. Is it possible yto
 have two versions of llwm, please?
 
 Thank you.
 
 
 Mitja

Yes, it's perfectly possible, as the ports llvm installs into /usr/local
while the base one is in /usr. Just like you can have base and ports gcc at
the same time in FreeBSD-9.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] Fix 4.10 ports?

[Schaich Alonso]

On Sun, 27 Oct 2013 23:39:30 +0200
Raphael Kubo da Costa rak...@freebsd.org wrote:

 Tijl Coosemans t...@freebsd.org writes:
 
  On Sat, 26 Oct 2013 23:53:24 +0300 Raphael Kubo da Costa wrote:
  Tijl Coosemans t...@coosemans.org writes:
  Is it worth spending time fixing KDE 4.10 ports for FreeBSD 10.0 or will
  KDE 4.11 hit the tree soon?
  
  What kind of fixes do you have in mind?
 
  http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2013-10-24_13h53m31s/
  Search for kde under Failed ports and Skipped ports.
  The kde meta port currently doesn't package because of failures in
  step-4.10.5_1, kdesdk-4.10.5 and kopete-4.10.5.
 
 I've somewhat started ignoring the pkg-fallout errors for KDE ports
 because a lot of them are just random segmentation faults in the build
 process.
 
 In any case: if the failures are still present in 4.11.x (or git
 master), I'd say it makes sense to fix the versions in ports as the
 fixes are still valid for future versions. Otherwise (ie. it's a failure
 only in 4.10.5) backporting the fixes should be easy.

I think area51 commit r9387 should be applyable to ports to fix the broken
libmsn dependency. kdesdk was split into smaller packages for 4.11 so
there's no compatible patches. step fails with clang on area51. And last but
not least marble (4.11.2) builds fine with either compiler but segfaults on
invalid memory reads at startup.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: [kde-freebsd] marble

[Schaich Alonso]

On Thu, 24 Oct 2013 19:19:21 -0400
Ajtim lum...@gmail.com wrote:

 Hi!
 
 I built marble with clang on FreeBSD 10.0-BETA1 and when I start it
 it crashed:
 
 Application: Marble Virtual Globe (marble), signal: Segmentation fault
 [...]
 
 Do I need to use gcc instead, please?
 
 Thank you.
 
 
 Mitja

If it's built with gcc it segfaults nevertheless. Over here I get

 Null pointer in call to GeoDataTreeModel::addFeature (parent  0x810288d38  -
 feature 0x0 ) 
 KCrash: Application 'marble' crashing...

printed on the terminal before the application crashes though. It's probably
the lack of some optional dependencies which aren't in ports yet. I'll try
to investigate this.

Alonso
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information