Re: KDE 4.8 - ALT-F2 gives black window

Heino Tiedemann <rotkaps_spam_trap <at> gmx.de> writes:

> Hi,
>
> With ALT+F2 (run command) I got this black window:
>
> http://rotkap.tsdh.org/kde4-run-command.png
>
> How can I switch it back to grey, like it was in KDE 4.7?

Hmm, this looks like the result of bad support for desktop effects. Are
they enabled on your machine? What style is that?
_______________________________________________
kde-freebsd mailing list
kde-freebsd <at> kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: ports/168319: graphics/qiviewer: Not displaying image jpeg

Mel Flynn <rflynn <at> acsalaska.net> writes:

> When graphics/qiviewer is installed without having a full KDE desktop,
> in my case a trimmed down x11-wm/xfce4 (no PRINT, no MIXER, no GDM) then
> qiviewer will not display JPEG images.
> It will successfully show PNG images, which leads me to believe that the
> root cause is that the program relies on QtGUI providing the image support.
>
> Since the FreeBSD QtGUI only links with png, no other image formats are
> available to it. Jpeg is available at compile and runtime.
<snip>
> Possible fix that should be examined if linking QtGui with jpeg makes this
> work.

Hmm. We already pass -system-libpng, -system-libjpeg and friends to Qt's
configure program. Do you have graphics/qt4-imageformats installed?
_______________________________________________
kde-freebsd mailing list
kde-freebsd <at> kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: ports/168319: graphics/qiviewer: Not displaying image jpeg

On 1-6-2012 4:10, Raphael Kubo da Costa wrote:
> Mel Flynn <rflynn <at> acsalaska.net> writes:
> 
>> When graphics/qiviewer is installed without having a full KDE desktop,
>> in my case a trimmed down x11-wm/xfce4 (no PRINT, no MIXER, no GDM) then
>> qiviewer will not display JPEG images.
>> It will successfully show PNG images, which leads me to believe that the
>> root cause is that the program relies on QtGUI providing the image support.
>>
>> Since the FreeBSD QtGUI only links with png, no other image formats are
>> available to it. Jpeg is available at compile and runtime.
> <snip>
>> Possible fix that should be examined if linking QtGui with jpeg makes this
>> work.
> 
> Hmm. We already pass -system-libpng, -system-libjpeg and friends to Qt's
> configure program. Do you have graphics/qt4-imageformats installed?

Negative.
Also not marked in that port's dependencies.

Qt4 related ports on the build host:
qt4-assistant-4.7.4_1
qt4-clucene-4.7.4
qt4-corelib-4.7.4
qt4-dbus-4.7.4
qt4-declarative-4.7.4
qt4-designer-4.7.4_1
qt4-doc-4.7.4
qt4-gui-4.7.4_1

Re: status of build on 9.0 CURRENT

On 31-5-2012 21:36, Schaich Alonso wrote:

> Though the real solution to this was, if I remember correctly (which might not 
> be the case given it's been in the kde-4.4 times), to reinstall perl with 
> USE_PERL ports option set.

Which means the proper fix is to replace /usr/bin/perl with ${PERL} in
post-patch target of hebrew/hspell port.

--

-- 
Mel
Proud member of the WITHOUT_USE_PERL society.
_______________________________________________
kde-freebsd mailing list
kde-freebsd <at> kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Re: ports/168319: graphics/qiviewer: Not displaying image jpeg

Mel Flynn <rflynn <at> acsalaska.net> writes:

> On 1-6-2012 4:10, Raphael Kubo da Costa wrote:
>> Mel Flynn <rflynn <at> acsalaska.net> writes:
>> 
>>> When graphics/qiviewer is installed without having a full KDE desktop,
>>> in my case a trimmed down x11-wm/xfce4 (no PRINT, no MIXER, no GDM) then
>>> qiviewer will not display JPEG images.
>>> It will successfully show PNG images, which leads me to believe that the
>>> root cause is that the program relies on QtGUI providing the image support.
>>>
>>> Since the FreeBSD QtGUI only links with png, no other image formats are
>>> available to it. Jpeg is available at compile and runtime.
>> <snip>
>>> Possible fix that should be examined if linking QtGui with jpeg makes this
>>> work.
>> 
>> Hmm. We already pass -system-libpng, -system-libjpeg and friends to Qt's
>> configure program. Do you have graphics/qt4-imageformats installed?
>
> Negative.
> Also not marked in that port's dependencies.

Please try installing it and checking if things work fine. If they do,
the port's dependencies need to be adjusted.
_______________________________________________
kde-freebsd mailing list
kde-freebsd <at> kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

calligra

First, thank you for Calligra 2.4.2. It works excellent and Krita is much much 
faster than before in KOffice.

And the second I did try to build Calligra with clang on FreeBSD 9.0 Release 
but it didn't work. I don't have any logs. I was not at home and when I came 
home I just remove clang from make.conf and it works without problems. And I 
have Clang 3.0.

Thanks.

Mitja
--------
http://jpgmag.com/people/lumiwa
_______________________________________________
kde-freebsd mailing list
kde-freebsd <at> kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

[SVN Commit] area51/QT/Mk

SVN commit 8266 by rakuco:

bsd.qt.mk: Sync MASTER_SITES with the version in ports

 M  +1 -2      bsd.qt.mk  

_______________________________________________
kde-freebsd mailing list
kde-freebsd <at> kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

[SVN Commit] area51/QT

SVN commit 8267 by rakuco:

qt4: Sync the libpng dependency with ports.

Depend on `png15' instead of `png' now that graphics/png has been upgraded to
1.5.0.

 M  +1 -1      graphics/qt4-imageformats/Makefile  
 M  +1 -1      x11-toolkits/qt4-gui/Makefile  

_______________________________________________
kde-freebsd mailing list
kde-freebsd <at> kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

bsd.qt.mk vs bsd.gcc.mk: USE_GCC -> CXX -> QMAKESPEC

bsd.qt.mk sets QMAKESPEC based on CXX.  This is done in the "early" stage of
bsd.port.mk processing (!_POSTMKINCLUDED).
bsd.gcc.mk may change CXX value based on USE_GCC (or WITH_GCC/WANT_CC in the
future).  But this is done in the "main" stage (_POSTMKINCLUDED).

Thus, QMAKESPEC may fail to honor USE_GCC.
Is there a good reason that QMAKESPEC is derived that early?
Could that logic be moved to the "main" stage?

Alternatively, maybe USE_GCC -> CXX logic should be moved to the "early" stage?

--

-- 
Andriy Gapon

_______________________________________________
kde-freebsd mailing list
kde-freebsd <at> kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

kde4 related bug

Hello,

I'm not sure if this is the correct place to report bugs (this is my 1st 
time reporting an issue relating to FreeBSD) so feel free to direct me 
to the correct place.

I'm seeing an issue where if I drag entries from the Applications menu 
to the desktop in KDE 4.8.3 (I've seen this issue with KDE 4.7.x in 
FreeBSD too), I get an icon with an exclamation point. If I double click 
on the icon, it attempts to run the application directly from my home 
directory and I get 2 popup windows.

The 1st window states:
"This will start the program:
/home/username/pidgin
If you do not trust this program, click Cancel"

Then when I click continue I get:
"Unable to make the service Pidgin executable, aborting execution"

Note that the exclamation point remains.

I did some digging and the issue is that the icons are being created in 
/home/username/Desktop with 444 permissions (and sometimes 644). To fix 
the issue, the permissions need to be 755 (presumably 555 would work too).

I found that the permissions are being copied along with the icons from 
/usr/local/share/applications/ (so my umask of 022 is ignored). All the 
icons in /usr/local/share/applications/ are 444 (except for 2 which were 
644). I "fixed" the issue by setting the permissions of