[kde-freebsd] Desktop Effects not working with nvidia-driver
Hi,
For the last few months my desktop effects have not been working with OpenGL
due to kwin_opengl_test core dumping. I have found two possible workarounds:
1) Switch to XRENDER (performance is still good however Blur and other effects
may not work)
2) Override the kwin_opengl_test with the following script:
cat > /usr/local/lib/kde4/libexec/kwin_opengl_test
#!/bin/sh
exit 0
^D
The cause of the crash appears to be during linking, before main() even starts:
# gdb /usr/local/lib/kde4/libexec/kwin_opengl_test kwin_opengl_test.core
GNU gdb 6.1.1 [FreeBSD]
#0 0x00080060c2a2 in _rtld_is_dlopened () from /libexec/ld-elf.so.1
[New LWP 100463]
(gdb) bt
#0 0x00080060c2a2 in _rtld_is_dlopened () from /libexec/ld-elf.so.1
#1 0x000800605c8d in _r_debug_postinit () from /libexec/ld-elf.so.1
#2 0x00080060346d in .text () from /libexec/ld-elf.so.1
#3 0x000804f3a365 in _nv003glcore () from
/usr/local/lib/libnvidia-glcore.so.1
#4 0x000804b9e690 in _nv023glcore () from
/usr/local/lib/libnvidia-glcore.so.1
#5 0x000804f1effc in _nv015glcore () from
/usr/local/lib/libnvidia-glcore.so.1
#6 0x000801a414eb in glXCreateNewContext () from /usr/local/lib/libGL.so.1
#7 0x000801a09e5a in .init () from /usr/local/lib/libGL.so.1
#8 0x000800605a9f in r_debug_state () from /libexec/ld-elf.so.1
#9 0x0008006050ee in __tls_get_addr () from /libexec/ld-elf.so.1
#10 0x000800603439 in .text () from /libexec/ld-elf.so.1
#11 0x in ?? ()
I have no idea how or why this is happening but a solution exists:
1) CMake is linking kwin_opengl_test to too many libraries (it only needs
libGL and libX11).
2) The error above appears to be because of libXft linking before libGL.
Placing libGL before libXft in the linking order fixes the crash (or
removing libXft).
See attached for a patch that fixes the linking order. I'll commit this patch
to ports and area51, and submit a bug report against ld-elf this evening.
Regards,
David--- kwin/opengltest/CMakeLists.txt.orig 2016-01-18 06:47:15 UTC
+++ kwin/opengltest/CMakeLists.txt
@@ -4,7 +4,7 @@ set(kwin_opengl_test_SRCS opengltest.cpp
kde4_add_executable(kwin_opengl_test ${kwin_opengl_test_SRCS})
-target_link_libraries(kwin_opengl_test ${X11_LIBRARIES} ${OPENGL_gl_LIBRARY})
+target_link_libraries(kwin_opengl_test ${OPENGL_gl_LIBRARY} ${X11_LIBRARIES})
install(TARGETS kwin_opengl_test DESTINATION ${LIBEXEC_INSTALL_DIR} )
signature.asc
Description: This is a digitally signed message part.
___
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
On Saturday, 28 March 2015 22:42:52 Juergen Lock wrote: On Sat, Mar 28, 2015 at 07:03:52PM +, Max Brazhnikov wrote: Could you also switch multimedia/phonon-vlc to vlc-qt4 once it committed to the portstree? Done. Thanks for looking at this, Thank you all for all the effort, much appreciated :-D. dbn (enjoying some good tunes) signature.asc Description: This is a digitally signed message part. ___ 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
On Tuesday, 24 March 2015 00:47:30 Schaich Alonso wrote: 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, I am currently on a binary package based system so I did: # pkg install phonon-gstreamer gstreamer1-plugins-all # pkg delete -f phonon-vlc (or is important as the `pkg install` step will reinstall phonon-vlc if it is not present). This fixes the crash for me however phonon-gstreamer does not play any audio (although gstreamer does). 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. Have you tried installing gstreamer1-plugins-flac? This should add flac support to gstreamer for you. I would prefer the gstreamer option except I cannot actually get phonon-gstreamer to work for me :-(. Regards signature.asc Description: This is a digitally signed message part. ___ 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] Phonon-vlc crashing
Hi, I always seem to be complaining about Phonon :-(. My latest issue has been crashes in phonon-vlc (phonon-gstreamer still doesn't work). The crash report says: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #8 0x000804e6d3c0 in strcmp () from /lib/libc.so.7 #9 0x000825506e15 in QMetaType::registerNormalizedType () from /usr/local/lib/libQt5Core.so.5 #10 0x000824f38998 in operator () from /usr/local/lib/libQt5Gui.so.5 #11 0x000824f36cea in operator () from /usr/local/lib/libQt5Gui.so.5 #12 0x000825006232 in QOpenGLTimeMonitor::qt_metacall () from /usr/local/lib/libQt5Gui.so.5 #13 0x000824cee24e in _init () from /usr/local/lib/libQt5Gui.so.5 #14 0x7fff9d30 in ?? () #15 0x00080061e6bf in r_debug_state () from /libexec/ld-elf.so.1 #16 0x000800622d87 in _rtld_get_stack_prot () from /libexec/ld-elf.so.1 #17 0x00080061fad3 in dlopen () from /libexec/ld-elf.so.1 #18 0x00082368d091 in vlc_timer_getoverrun () from /usr/local/lib/libvlccore.so.8 #19 0x00082367759c in module_list_free () from /usr/local/lib/libvlccore.so.8 #20 0x0008236779dd in module_list_free () from /usr/local/lib/libvlccore.so.8 #21 0x00082367790e in module_list_free () from /usr/local/lib/libvlccore.so.8 #22 0x000823677716 in module_list_free () from /usr/local/lib/libvlccore.so.8 #23 0x0008236771af in module_config_free () from /usr/local/lib/libvlccore.so.8 #24 0x00082361f36f in libvlc_InternalInit () from /usr/local/lib/libvlccore.so.8 #25 0x0008238e1139 in libvlc_new () from /usr/local/lib/libvlc.so.5 #26 0x0008233ec76f in qt_plugin_instance () from /usr/local/lib/kde4/plugins/phonon_backend/phonon_vlc.so #27 0x0008233d1a66 in qt_plugin_instance () from /usr/local/lib/kde4/plugins/phonon_backend/phonon_vlc.so #28 0x0008233d1694 in qt_plugin_instance () from /usr/local/lib/kde4/plugins/phonon_backend/phonon_vlc.so #29 0x000803e60d2c in QPluginLoader::instance () from /usr/local/lib/qt4/libQtCore.so.4 #30 0x000809a14f7e in Phonon::Factory::setBackend () from /usr/local/lib/libphonon.so.4 #31 0x000809a153cf in Phonon::Factory::setBackend () from /usr/local/lib/libphonon.so.4 #32 0x000809a1634e in Phonon::Factory::backend () from /usr/local/lib/libphonon.so.4 #33 0x000809a18a56 in Phonon::GlobalConfig::audioOutputDeviceListFor () from /usr/local/lib/libphonon.so.4 #34 0x0008231a6ade in qt_plugin_instance () from /usr/local/lib/kde4/kcm_phonon.so #35 0x0008231a913d in qt_plugin_instance () from /usr/local/lib/kde4/kcm_phonon.so #36 0x0008231aa1a8 in qt_plugin_instance () from /usr/local/lib/kde4/kcm_phonon.so #37 0x000803e950e6 in QMetaObject::activate () from /usr/local/lib/qt4/libQtCore.so.4 #38 0x000802fea961 in QAbstractButton::toggled () from /usr/local/lib/qt4/libQtGui.so.4 #39 0x000802d3a1e9 in QAbstractButton::setChecked () from /usr/local/lib/qt4/libQtGui.so.4 #40 0x0008231a6a25 in qt_plugin_instance () from /usr/local/lib/kde4/kcm_phonon.so #41 0x0008231a2632 in qt_plugin_instance () from /usr/local/lib/kde4/kcm_phonon.so #42 0x0008231a22c5 in qt_plugin_instance () from /usr/local/lib/kde4/kcm_phonon.so #43 0x0008231a2840 in qt_plugin_instance () from /usr/local/lib/kde4/kcm_phonon.so #44 0x00080374356e in KPluginFactory::create () from /usr/local/lib/libkdecore.so.5 #45 0x000801b6e5bc in KCModuleLoader::showLastLoaderError () from /usr/local/lib/libkcmutils.so.4 #46 0x000801b6d21e in KCModuleLoader::loadModule () from /usr/local/lib/libkcmutils.so.4 #47 0x000801b73d62 in KCModuleProxy::realModule () from /usr/local/lib/libkcmutils.so.4 #48 0x000801b73b32 in KCModuleProxy::realModule () from /usr/local/lib/libkcmutils.so.4 #49 0x000801b74a89 in KCModuleProxy::showEvent () from /usr/local/lib/libkcmutils.so.4 #50 0x0008029dba2f in QWidget::event () from /usr/local/lib/qt4/libQtGui.so.4 #51 0x00080298f4bd in QApplicationPrivate::notify_helper () from /usr/local/lib/qt4/libQtGui.so.4 #52 0x000802992549 in QApplication::notify () from /usr/local/lib/qt4/libQtGui.so.4 #53 0x000802014a17 in KApplication::notify () from /usr/local/lib/libkdeui.so.5 #54 0x000803e7dd15 in QCoreApplication::notifyInternal () from /usr/local/lib/qt4/libQtCore.so.4 #55 0x0008029da53a in QWidgetPrivate::show_helper () from /usr/local/lib/qt4/libQtGui.so.4 #56 0x0008029da77b in QWidgetPrivate::showChildren () from /usr/local/lib/qt4/libQtGui.so.4 #57 0x0008029da3a9 in QWidgetPrivate::show_helper () from /usr/local/lib/qt4/libQtGui.so.4 #58 0x0008029db054 in QWidget::setVisible () from /usr/local/lib/qt4/libQtGui.so.4 #59 0x0008029da774 in QWidgetPrivate::showChildren () from /usr/local/lib/qt4/libQtGui.so.4 #60 0x0008029da3a9 in QWidgetPrivate::show_helper () from /usr/local/lib/qt4/libQtGui.so.4 #61 0x0008029db054 in QWidget::setVisible () from
Re: [kde-freebsd] [SVN Commit] area51/PORTS/multimedia/phonon-gstreamer/files
On Tuesday, 10 February 2015 11:20:47 Max Brazhnikov wrote: On Mon, 09 Feb 2015 19:23:08 +0200 David Naylor wrote: Does anyone consider this critical enough push to ports before the next big update? Use different logic: trivial and safe changes should go to the portstree first for the benefit of users who use official ports and packages. and then to area51 for us. Thanks for the advise. Have pushes these changes into Ports. signature.asc Description: This is a digitally signed message part. ___ 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/multimedia/phonon-gstreamer/files
Does anyone consider this critical enough push to ports before the next big update? On Sunday, 8 February 2015 06:39:17 David Bruce Naylor wrote: SVN commit 10582 by DragonSA: phonon-gstreamer: fix pkg-message to reference correct gstreamer port. phonon-gstreamer depends on multimedia/gstreamer1 however the pkg-message incorrectly referred to the multimedia/gstreamer-plugins-all port. M +2 -2 pkg-message.in signature.asc Description: This is a digitally signed message part. ___ 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] Sound issues with a fresh installation
Hi list, I recently did a clean installation of KDE however sound did not work. The details follow. Fix: To fix the issue I did the following: # pkg delete -f phonon-gstreamer # pkg install phonon-vlc Note: If a command like `ogg123` or a application like `vlc` does not work then your problem is not with KDE but with a lower level on the FreeBSD sound stack. Explanation: Initially gstreamer comes installed with two sinks: pulseaudio and oss. However, pulseaudio does not work and that is selected as the default sink by autoaudiosink. Uninstalling the gstreamer pulseaudio packages fixes this issue. GStreamer was then capable of actually playing audio (see [1] for the command to use). The issue was phonon-gstreamer was not working itself. My attempts to debug phonon haven't yielded any clues [1]. I then tried to use a different phonon backend by installing the vlc and xine backend however KDE did not honour my ordering of preferred backends (even after a logout/login). The only way I could get phonon to use vlc was to make it the only option. Questions: - Can anyone else verify: - phonon-gstreamer failes to play audio? - phonon fails to honour backend preference? - audio does not work out of the box? - Any hints on getting gstreamer to work? - Is this a new development (I think the latest update [2] caused this issue)? Please note that sound via OSS worked out of the box. Regards, [1] https://techbase.kde.org/Development/Tutorials/Debugging/Phonon [2] All the above is on a binary only system by installing (and updating) from the pkgng repository. signature.asc Description: This is a digitally signed message part. ___ 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] Error using CMake similar to error from earlier list post
Hi Joe, Apologies for taking so long to get back to you. Work got really, really busy. The underlying issue is that gcc pulls in the pthread headers by default while clang does not. I believe clang is following the more correct approach. The files you attached are for traverso however I do not see it in the Port's Collection. Are you building it directly from source? On Wednesday, 11 December 2013 21:02:27 Joe Nosay wrote: I'm attaching files. 1. Undeclared identifier pthread_self:: Does this mean I need to add the pthread.h before every declaration of pthread_self? No, you only need to add it once. Normally there will be a header file. I'm guessing either to src/engine/AudioDeviceThread.cpp or to a header file included by src/engine/AudioDeviceThread.cpp 2. How do I declare an identifier? I don't know what you are referring to, could you please elaborate? 3. CLang crashed somewhat at the beginning. Files are attached. I see. Can you please try with a newer version of clang/traverso. If that does not fix the issue, then please report that upstream to the LLVM developers, this is well beyond my capabilities to fix. The files will probably be too big for the mailing lists. Now, those errors which have references in section 2 of the man pages, do I replace as suggested with cpusetid_t. For others, do I introduce a patch similar to the pthread.h from the kopete patch? Yes, patches similar to pthread.h should work. Once you get the patches working please submit them upstream. It makes our lives easier if those developers maintain the patches, instead of us. Regards signature.asc Description: This is a digitally signed message part. ___ 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] Error using CMake similar to error from earlier list post
Hi Joe,
I'm listening!
I've read through your thread on KDE-FreeBSD and Ports-FreeBSD however I am a
bit fuzzy as to the issues.
Are these specific to clang, FreeBSD = 10 or some other trigger? How would I
go about reproducing these errors?
I'm happy to work with you to resolve these issues.
Regards
On Tuesday, 10 December 2013 04:25:58 Joe Nosay wrote:
On Mon, Dec 9, 2013 at 11:18 PM, Joe Nosay superbisq...@gmail.com wrote:
-- Forwarded message --
From: Joe Nosay superbisq...@gmail.com
Date: Sun, Dec 8, 2013 at 6:38 PM
Subject: Re: Error using CMake similar to error from earlier list post
To: kde-freebsd kde-freebsd@kde.org
On Sat, Dec 7, 2013 at 3:45 PM, Joe Nosay superbisq...@gmail.com wrote:
On Fri, Dec 6, 2013 at 7:50 PM, Joe Nosay superbisq...@gmail.com wrote:
https://www.mail-archive.com/kde-freebsd@kde.org/msg15778.html
Is there a similar fix for this?
Thanks.
Now would
+Build fix for clang.
+
+ error: use of undeclared identifier 'pthread_mutex_lock'
+ error: use of undeclared identifier 'pthread_mutex_unlock'
+ error: use of undeclared identifier 'pthread_self'
+ error: use of undeclared identifier 'pthread_mutex_init'
+ error: use of undeclared identifier 'pthread_mutex_destroy'
+
+---
kopete/protocols/jabber/googletalk/libjingle/talk/base/ssladapter.cc.or
ig
2013-11-04 01:20:09.0 +0200
kopete/protocols/jabber/googletalk/libjingle/talk/base/ssladapter.cc
2013-11-04 01:20:20.0 +0200
+@@ -29,6 +29,7 @@
+
+ #ifdef POSIX
+ extern C {
++#include pthread.h
+ #include unistd.h
+ }
+ #endif
Be the appropriate fix for
/usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/AudioDeviceTh
read.cpp:58:30: error: use of undeclared identifier 'pthread_self'
if (pthread_setschedparam (pthread_self(), SCHED_FIFO,
param) != 0) {}
^
/usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/AudioDeviceTh
read.cpp:131:30: error: use of undeclared identifier 'pthread_self'
if (pthread_setschedparam (pthread_self(), SCHED_FIFO,
param) != 0) {
I need to write a patch and then apply it to the script in question.
1. Will I need to add the patch to each part that is listed?
Since it is suggested to build an application natively - or at least try
to - on FreeBSD before making a port, I am trying to do such.
The errors seems to be the same CLang type as the others.
Included is the file which was modified according to the patch from the
hyperlink stated earlier in this thread.
Since this a CLang problem which has occurred and will occur in software
with the same or similar type of instructions, it may be of use to make a
patch for all qtX software and others with the same problem.
Me Did I do the patch right?
KDE FreeBSD Did you hear something?
Ports FreeBSD Nope, not at all.
GCC patchiness popping up here and there. I can see it and so can others.
KDE FreeBSD What was that?
Ports FreeBSD Nothing, nothing at all.
These problems also show up on Debian and other systems transitioning to
CLang for the compiler. Errors of the same type happen on software not in
ports or natively part of kde3/4.
KDE FreeBSD There goes that noise again.
Ports FreeBSD Just ignore it.
signature.asc
Description: This is a digitally signed message part.
___
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] [SOLVED] sound distorted with phonon-gstreamer
Hi, If you have experienced sound distortion when using phonon-gstreamer try the following (which fixed the problem for me): # pkg delete -fy gstreamer-plugins-pulse gstreamer-plugins-esound The issue is with either PulseAudio or ESD. Regards signature.asc Description: This is a digitally signed message part. ___ 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] plasma-desktop does not display jpegs (and other errors)
Hi, I've updated to KDE SC 4.10.5 however the wallpaper slideshow (and image) is showing black when requested to display a jpeg image. png images display without issue. I've confirmed that jpegs otherwise works using dolpin preview and gwenview (and for good measure I reinstalled libjpeg). Any suggestions as to the problem? I also notice that the l10n ports are no longer detecting the respective spelling packages (and that en_GB has always failed to detect en-aspell), and that KDE is also no longer installing any spelling packages (even for American English). This issue I can fix (and commit) although it may mean undoing commit r322586. Regards P.S. Didn't we ask the maintainer of aspell to include at least the default dictionary with the installation? P.P.S. Subversion broke my area51 checkout (svn: E17: Unrecognized URL scheme for) how can I fix it? signature.asc Description: This is a digitally signed message part. ___ 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 Mobility?
Hi Kris, Oliver On Thursday, 4 April 2013 20:58:32 Oliver Heesakkers wrote: Op do 04 apr 2013 08:00:08 schreef Kris Moore: We have a developer who is asking about Qt Mobility support on FreeBSD. Is anybody interested in trying to make a port out of this? I have built qt-mobility (1.2.0) in the past, as a dependency of MoNav. According to my notes this was a pretty painless experience. Unfortunately, as the MoNav project now seems dormant, I don't have a real use for it these days, which makes me less interested in maintaining a port. So yes, I'll happily (help to) make one, but someone else should maintain it. I'm willing to create and maintain a qtmobility port however I do not have time for it this week. Oliver, if you have the time you are welcome to create the port (which I can commit for you), just put me as maintainer (d...@freebsd.org). I can help you starting next week sometime. Regards David signature.asc Description: This is a digitally signed message part. ___ 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
On Saturday, 27 October 2012 20:08:37 Max Brazhnikov wrote: SVN commit 8683 by makc: Autodetect aspell and huspell ports for particular KDE4_L10N and provide options to install dictionaries. Thank you for completing what I started, much appreciated. signature.asc Description: This is a digitally signed message part. ___ 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
On Tuesday, 16 October 2012 19:20:11 Max Brazhnikov wrote:
On Tue, 16 Oct 2012 14:20:12 GMT, David Bruce Naylor wrote:
SVN commit 8679 by DragonSA:
Make l10n ports depend on their respective aspell dictionaries.
Good idea! However, kde doesn't use aspell directly, but via enchant,
x11/kdelibs4 does depend on aspell directly, see LIB_DEPENDS. Is it possible
kdelibs actually requires aspell somewhere, and enchant?
which can be complied with support for other spellcheckers.
hunspell has a plenty of dictionaries in ports. We probably need a global
switch for spellchecking.
I had a look at enchant and there is no global way to determine which spell
checkers are being used.
I can see four ways to fix this:
1) modify textproc/enchant to require a global (in make.conf) variable be set
2) some dynamic method of detecting which spell checkers are used
3) installing all the dictionaries, regardless of what enchant uses
4) just install aspell (aka: ignore the problem)
My thoughts on the options:
1) This is, in my opinion, the closest to optimal however this makes the
user's life difficult as enchant will no longer use options (effectively). An
alternative is for a KDE specific global option?
2) I would avoid this, not enough deterministic behaviour
3) This, I think, is the most flexible as a user could recompile *just*
enchant and KDE will work without having to (re)install anything else,
although many prefer less to more packages installed
4) Makes my life easy ;-)
I think a combination of option 1 and 3 should be implemented: have a KDE
specific option to control which dictionaries are installed and default to
installing everything, that way those who want less can get it. Also I
propose contacting the enchant maintainer to see if we could make it global
(surely gnome and others have the same issue?).
But maybe this should be kept as a KDE specific solution?
Thoughts please!!!
This will provide spell checking for locales in addition to the
translations. Those ports without aspell counterparts have been marked
as such.
some spell dictionaries are under ${lang} category, e.g arabic, russian.
complainI find the ${lang} categories confusing, why not put everything in
one place (like all the ${lang} without categories)./complain
I'll fix this...
The following variables are introduced:
ASPELL_CODE?= ${KDE4_L10N}# The aspell language code
ASPELL_FILE?= ${ASPELL_CODE}.multi# The aspell file for
RUN_DEPENDS
NO_ASPELL= # Indicate no aspell is available
signature.asc
Description: This is a digitally signed message part.
___
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 won't play mp3
On Sunday, 8 July 2012 16:28:31 Raphael Kubo da Costa wrote: David Naylor naylor.b.da...@gmail.com writes: I have tried both vlc and gstreamer backends as preferred and neither work (also, the gstreamer backend causes amarok to crash [sig 11] on exit). I have checked that the mimetype is audio/mpeg for the mp3 file and that both phononbackends/(gstreamer|vlc).desktop support it. Hmm. Do you get any useful console output when trying to play MP3 files? No, nor in ~/.xsession-errors. I also enabled all messages via kdebugdialog. I did get something with: # cat play.py import gst, sys bin = gst.element_factory_make(playbin) bin.set_property(uri, file:// + sys.argv[1]) bin.set_state(gst.STATE_PLAYING) # python play.py ~/preview.mp3 ** Message: pygobject_register_sinkfunc is deprecated (GstObject) ** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, layer=(int)3, rate=(int)44100, channels=(int)2, parsed=(boolean)true Which looked very suspicious: # pkg info -l gstreamer-plugins-mp3 gstreamer-plugins-mp3-0.10.0_1 owns the following files: So, the package is empty!!! But it turns out it is a meta package that points to gstreamer-plugins-mad-mp3 and gstreamer-plugins-fluendo-mp3 which were not installed. Upon investigation I have determined that it was due to the changeover to the new options framework: many of my port options files are still in the old format and it appears things got mixed up. Thanks for your help. I'll do a rebuild soonish (of all ports) that should fix things. Regards signature.asc Description: This is a digitally signed message part. ___ 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] Phonon won't play mp3
Hi, I cannot get Amarok, or any other phonon-based player, to play MP3s. Amarok declares that Phonon claims it *cannot* play MP3 files. You may want to examine the installation that phonon uses. Ogg files play without a problem and VLC media player can play MP3 files. I have the following installed: # pkg info -q amarok gstreamer gstreamer-plugins-all gstreamer-plugins-mp3 \ ... kde phonon phonon-gstreamer phonon-vlc amarok-2.5.0_3 gstreamer-0.10.36 gstreamer-plugins-all-1.3.0.10.1_13 gstreamer-plugins-mp3-0.10.0_1 kde-4.8.4 phonon-4.6.0_1 phonon-gstreamer-4.6.0_1 phonon-vlc-0.5.0_1 I have tried both vlc and gstreamer backends as preferred and neither work (also, the gstreamer backend causes amarok to crash [sig 11] on exit). I have checked that the mimetype is audio/mpeg for the mp3 file and that both phononbackends/(gstreamer|vlc).desktop support it. Please help. Regards signature.asc Description: This is a digitally signed message part. ___ 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 won't play mp3
On Sunday, 8 July 2012 15:50:59 Dwayne MacKinnon wrote: Hi, I don't have amarok installed, but Dragon Player plays mp3s for me just fine. I have Phonon using the gstreamer backend on kde-4.8.4 with up-to-date ports. (FreeBSD 9.0-RELEASE i386). Dragon Player doesn't work either (nor Juk). Have you tried forcing a re-install of all the gstreamer stuff? I have reinstalled phonon and phonon-gstreamer and gstreamer itself recently had an update. With KDE 4.9 I will do a full reinstall... Regards On July 8, 2012 10:53:33 AM David Naylor wrote: Hi, I cannot get Amarok, or any other phonon-based player, to play MP3s. Amarok declares that Phonon claims it *cannot* play MP3 files. You may want to examine the installation that phonon uses. Ogg files play without a problem and VLC media player can play MP3 files. I have the following installed: # pkg info -q amarok gstreamer gstreamer-plugins-all gstreamer-plugins-mp3 \ ... kde phonon phonon-gstreamer phonon-vlc amarok-2.5.0_3 gstreamer-0.10.36 gstreamer-plugins-all-1.3.0.10.1_13 gstreamer-plugins-mp3-0.10.0_1 kde-4.8.4 phonon-4.6.0_1 phonon-gstreamer-4.6.0_1 phonon-vlc-0.5.0_1 I have tried both vlc and gstreamer backends as preferred and neither work (also, the gstreamer backend causes amarok to crash [sig 11] on exit). I have checked that the mimetype is audio/mpeg for the mp3 file and that both phononbackends/(gstreamer|vlc).desktop support it. Please help. Regards signature.asc Description: This is a digitally signed message part. ___ 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] attempt to compile kdelibs-4.7.3 with clang.
On Sunday, 18 December 2011 04:26:40 Chuck Burns wrote: In file included from /usr/ports/x11/kdelibs4/work/kdelibs-4.7.3/kjs/lookup.cpp:23: /usr/ports/x11/kdelibs4/work/kdelibs-4.7.3/kjs/lookup.h:324:33: error: static_cast from 'KJS::JSGlobalObject *' to 'KJS::JSObject *' is not allowed KJS::JSObject *globalObject = static_castKJS::JSObject *(exec-lexicalInterpreter()-globalObject()); ^~~~ 1 error generated. *** Error code 1 1 error *** Error code 2 The code compiles fine with gcc.. but I wonder if this is a clang bug, or a bug in kde ? Hi, Clang aims to be compatible with gcc and if gcc can compile the file then it is quite possible a clang bug although clang will not support everything gcc does. The bug database [1] for llvm/clang lists all the bugs affecting compilation of Qt [2] and possibly KDE. Regards [1] http://llvm.org/bugs/ [2] http://llvm.org/bugs/show_bug.cgi?id=5881 signature.asc Description: This is a digitally signed message part. ___ 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] automoc or gcc
On Monday, 28 November 2011 02:32:00 Lawrence Stewart wrote: On 11/26/11 10:19, ajtiM wrote: Is it a bug on automoc or gcc still alive, please?, It happened three times on my new installed FreeBSD 9.0 RC-2 during building KDE 4. Two times stopped when I built kde4-workspace and once in kdelibs4. https://bugs.kde.org/show_bug.cgi?id=276461 I'm still hitting this problem on my 8-STABLE work desktop with a ports tree csuped on 25 Nov. root@lstewart# uname -a FreeBSD lstewart.caia.swin.edu.au 8.2-STABLE FreeBSD 8.2-STABLE #9: Sat Nov 26 11:49:29 EST 2011 root@lstewart:/usr/obj/usr/src/sys/DESKTOP amd64 I decided to pkg_delete -af ; rm -rf /usr/local/* and rebuild ports over the weekend. portmaster -d x11/kde4 will just randomly hang running automoc4 while building kde ports. This is an old, intermittent, problem. There is a deadlock somewhere (kernel, libc, qt, automoc). One way to (potentially) avoid this is to run with DISABLE_MAKE_JOBS=yes for the affected ports. The patch at the above mentioned bug report has solved the problem for me (for reference: https://bugs.kde.org/attachment.cgi?id=61311). A fix is in the works and will come in the form of automoc being integrated into cmake. Regards signature.asc Description: This is a digitally signed message part. ___ 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] [CODE] Multithreaded SIGSEGV signal handling, please examine
Hi Michael,
I'm not sure if you have received results for FreeBSD but on my system I get:
# uname -a
FreeBSD dragon.dg 9.0-BETA2 FreeBSD 9.0-BETA2 #0: Wed Sep 21 06:45:41 SAST
2011 root@:/usr/obj/home/freebsd9/src/sys/MODULAR amd64
# g++ -pthread -o sigcatcher sigcatcher.cpp
# ./sigcatcher
Hello, World!
Got a result of 1
Exited thread
# clang++ -pthread -o sigcatcher sigcatcher.cpp
# ./sigcatcher
Hello, World!
Got a result of 1
Exited thread
Of note: library `rt' does exist on FreeBSD but does not change the results
above, nor does using optimisations of 2 or 3.
Thank you for your work.
David
On Sunday, 25 September 2011 01:37:12 Michael Pyne wrote:
Hi,
I writing with a kind of sneak preview of a change I would like to make to
KSharedDataCache (kdelibs/kdecore/util) in KDE 5.
The idea is to use a separate thread to perform the operations that
actually access shared memory, since a good majority of KSharedDataCache
bugs are reported as resolved by the user when they remove the cache file
and allow it to be regenerated.
While it is best to ensure there's absolutely no logic errors in the cache,
that's not the only source of cache corruption (BleachBit being run in a
naïve mode of operation being the other popular source). With this change
KSharedDataCache will be able to unlink the corrupted cache *and* prevent
application crashes.
It utilizes several nuances of what I believe to be fully POSIX/SUSv3-
compliant code:
* The idea that SIG{SEGV,FPE,ILL,BUS} signals are directed to a specific
thread (i.e. the thread that was running the code that invoked those
signals).
* The idea that signal masks are per-thread (so that only the signals
listed above would be delivered to the canary thread).
* Oh, and that sigsetjmp/siglongjmp actually work correctly. ;)
With that said I don't think the code uses as many POSIX options as the
rest of KSharedDataCache (e.g. process-shared mutexes as unimplemented on
Mac OS X) but I wanted to give a chance for you guys to test the prototype
code beforehand and let me know if there's problems.
You'll want to compile with something like this:
$CXX -O2 -o sigcatcher -lrt -pthread sigcatcher.cpp
Make sure optimization is enabled to ensure volatile is used where it's
needed. Assuming everything works right you should get output like:
$ ./sigcatcher
Hello, World!
Got a result of 1
Exited thread
$
If you want to see the signal handler in action there's a couple of lines
you can uncomment (just grep for uncomment to find where).
Obviously any other feedback on possible issues is appreciated as well, but
basically I'd like to catch any portability issues early this time instead
of after-the-fact.
Please CC me on any replies as I'm not subscribed.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
___
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] [RFC] KDE startup time and kbuildsycoca4
On Saturday, 3 September 2011 22:10:24 David Naylor wrote: On Saturday, 3 September 2011 04:10:34 Axel Gonzalez wrote: If you take out kbuildsycoca4 from /usr/local/kde4/env/xdg-env.sh KDE starts faster for 10-15 secs Can someone else confirm this actually speeds up KDE startup? (tested on 4.6.5 from ports) I can investigate this tomorrow... Based on manual testing I also get a speed up of between 11 and 15 seconds (depending on which measure is used). Assuming there are no side affects I vote kbuildsycoca4 gets removed from /usr/local/kde4/env/xdg-env.sh. signature.asc Description: This is a digitally signed message part. ___ 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] [RFC] KDE startup time and kbuildsycoca4
On Saturday, 3 September 2011 04:10:34 Axel Gonzalez wrote: If you take out kbuildsycoca4 from /usr/local/kde4/env/xdg-env.sh KDE starts faster for 10-15 secs My boot was like 45 secs, with that line removed is 30. kbuildsycoca4 in this file is not necessary, because is run by KDE at startup anyways. Looking at xdg-env.sh it sets XDG_DATA_DIRS and XDG_CONFIG_DIRS which I suspect changes how kbuildsycoca4 behaves. Are those environment variables carried over to when kbuildsycoca4 is run later on? Can someone else confirm this actually speeds up KDE startup? (tested on 4.6.5 from ports) I can investigate this tomorrow... signature.asc Description: This is a digitally signed message part. ___ 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] Re: [SVN Commit] area51/Tools/scripts
On Thursday, 28 July 2011 19:44:45 David Bruce Naylor wrote: SVN commit 7362 by DragonSA: Add a script to export area51 svn repository to a git repository. NOTE: area51 is NOT moving to git. Please read and customise 2git.sh before using it. This script is for those who wish to have a git mirror of area51. A first run of the script initialises the mirror while subsequent runs synchronise the mirror. A gitmirror (directory) AMgitmirror/2git.sh A gitmirror/authors.txt A gitmirror/rules.txt Currently there is a github repository that uses these scripts (at github.com/DragonSA/area51). Please let me know if you want access to that repository, if no one speak up I will remove it within a few weeks. signature.asc Description: This is a digitally signed message part. ___ 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] [regression] No printers listed in Print dialog
Hi, I am unable to see any printers listed in the Print Dialog, such as from KWrite or Okula. I am able to print from LibreOffice and Printer Configuration kconfig module does see the printers. My google searches have not yielded any results. Printing has worked on prior versions of KDE (currently 4.6.4). Please help. David signature.asc Description: This is a digitally signed message part. ___ 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] Re: Amarok crashes on close
On Sunday 22 May 2011 23:55:11 Raphael Kubo da Costa wrote: On Sunday 22 May 2011 15:57:20 David Naylor wrote: Hi, Whenever amarok closes (such as logout) it is dumping core. See attached for a traceback. Amarok (and all its dependencies were build with -DWITH_DEBUG). Weird, it looks like Amarok has no debug symbols at all. Can you rebuild it or somehow make sure it is built with CMAKE_BUILD_TYPE=DebugFull? I compiled amarok with `-DWITH_DEBUG and CMAKE_BUILD_TYPE=DebugFull` and confirmed '-g' was being passed to gcc. The traceback is (I think) essentially the same. Please see attached. Application: Amarok (amarok), signal: Bus error: 10 [Switching to Thread 82b2b6000 (LWP 100494/amarok)] [Current thread is 1 (Thread 82b2b6000 (LWP 100494/amarok))] Thread 6 (Thread 81b007400 (LWP 100149/amarok)): #0 0x00080531a80c in nanosleep () from /lib/libc.so.7 #1 0x000805286858 in sleep () from /lib/libc.so.7 #2 0x000805024438 in sleep () from /lib/libthr.so.3 #3 0x000800bbee48 in startProcessInternal (argc=17, argv=0x7fffc850, waitAndExit=true, directly=false) at /tmp/usr/ports/x11/kdelibs4/work/kdelibs-4.6.3/kdeui/util/kcrash.cpp:558 #4 0x000800bbeecd in KCrash::startProcess (argc=17, argv=0x7fffc850, waitAndExit=true) at /tmp/usr/ports/x11/kdelibs4/work/kdelibs-4.6.3/kdeui/util/kcrash.cpp:524 #5 0x000800bbf7c7 in KCrash::defaultCrashHandler (sig=10) at /tmp/usr/ports/x11/kdelibs4/work/kdelibs-4.6.3/kdeui/util/kcrash.cpp:435 #6 0x0008050265d6 in pthread_sigmask () from /lib/libthr.so.3 #7 0x0008050266bc in pthread_sigmask () from /lib/libthr.so.3 #8 0x7003 in ?? () #9 0x0008050265e0 in pthread_sigmask () from /lib/libthr.so.3 #10 0x in ?? () #11 0x in ?? () #12 0x in ?? () #13 0x in ?? () #14 0x5a5a5a5a5a5a5a5a in ?? () #15 0x in ?? () #16 0x00081b937ae8 in ?? () #17 0x in ?? () #18 0x0040 in ?? () #19 0x0002 in ?? () #20 0xffc0 in ?? () #21 0x5a5a5a5a5a5a5a5a in ?? () #22 0x7fffd3f0 in ?? () #23 0x0001 in ?? () #24 0x00081b07a480 in ?? () #25 0x5a5a5a5a5a40 in ?? () #26 0x5a5a5a5a5a5a5a5a in ?? () #27 0x in ?? () #28 0x000805570800 in __des_crypt_LOCAL () from /lib/libc.so.7 #29 0x001b00130009 in ?? () #30 0x in ?? () #31 0x003b003b0001 in ?? () #32 0x in ?? () #33 0x0008052ba47b in malloc_usable_size () from /lib/libc.so.7 #34 0xa000 in ?? () #35 0x4016 in ?? () #36 0xdfcd in ?? () #37 0x3ffd in ?? () #38 0x0073005f3f80 in ?? () #39 0x0069007300730065 in ?? () #40 0x437f in ?? () #41 0x in ?? () #42 0x in ?? () #43 0x in ?? () #44 0x402a in ?? () #45 0x in ?? () #46 0x in ?? () #47 0x in ?? () #48 0x4052c000 in ?? () #49 0x in ?? () #50 0x3ff0 in ?? () #51 0x in ?? () #52 0x3ff0 in ?? () #53 0x in ?? () #54 0x3fe3 in ?? () #55 0x in ?? () #56 0x3fe6db6db6db6dc1 in ?? () #57 0x in ?? () #58 0x4005b6db6db6db70 in ?? () #59 0x in ?? () #60 0x3fd40346e000 in ?? () #61 0x in ?? () #62 0x in ?? () #63 0x in ?? () #64 0x in ?? () #65 0x in ?? () #66 0x in ?? () #67 0x in ?? () #68 0x in ?? () #69 0x in ?? () #70 0x in ?? () #71 0x in ?? () #72 0x in ?? () #73 0x in ?? () #74 0x in ?? () #75 0x in ?? () #76 0x in ?? () #77 0x in ?? () #78 0x in ?? () #79 0x in ?? () #80 0x in ?? () #81 0x in ?? () #82 0x0008006831d8 in ?? () #83 0x in ?? () #84 0x in ?? () #85 0x in ?? () #86 0x in ?? () #87 0x in ?? () #88 0x in ?? () #89 0x in ?? () #90 0x in ?? () #91 0x in ?? () #92 0x in ?? () #93 0x0004 in ?? () #94 0x in ?? () #95 0x in ?? () #96 0x in ?? () #97 0x in ?? () #98 0x000a in ?? () #99 0x0003 in ?? () #100 0x in ?? () #101 0x0008052ba47b in malloc_usable_size () from /lib/libc.so.7 #102 0x0008052ba50d in malloc_usable_size () from /lib/libc.so.7 #103 0x0008052bb325 in free () from /lib/libc.so.7 #104 0x00080440a3c9 in ~QMutexPrivate (this=) at thread/qmutex_unix.cpp
[kde-freebsd] Amarok crashes on close
Hi, Whenever amarok closes (such as logout) it is dumping core. See attached for a traceback. Amarok (and all its dependencies were build with -DWITH_DEBUG). Also, amarok reports on the console: snip/ amarok(4014)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: amarok(4014)/kio (KDirListerCache) KDirListerCache::stopListingUrl: KDirLister(0x82437fd00) url= KUrl(file:///home/DragonSA) amarok(4014)/kio (KDirListerCache) KDirListerCache::forgetDirs: KDirLister(0x82437fd00) item moved into cache: KUrl(file:///home/DragonSA) amarok(4014)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: amarok(4014)/kio (Slave) KIO::Slave::kill: killing slave pid 4016 ( file:// ) KCrash: crashing... crashRecursionCounter = 2 snip/ It is being killed with SIGBUS. This happens when using the gstreamer and vlc backend. Xine backend works fine. Is this FreeBSD specific, or should I report this upstream? Regards, David amarok-20110522-110551.kcrash Description: Binary data ___ 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] Re: [SVN Commit] area51/KDE/sysutils/ksysguardd
On Saturday 23 April 2011 17:28:03 Raphael Kubo da Costa wrote: David Naylor naylor.b.da...@gmail.com writes: On Saturday 23 April 2011 01:40:24 Raphael Kubo da Costa wrote: David Bruce Naylor naylor.b.da...@gmail.com writes: SVN commit 7200 by DragonSA: Update ksysguardd and fix bug (causes segfault). ksysguardd no longer uses libkvm so does not need g+s or grp=kmem and ksysguardd can now run as a regular (unprivileged) user. An error in calculating MSI offsets resulted in the last regular interrupt being included as a MSI interrupt and a buffer underrun, causing a segfault. This has been fixed. @avilla: please push this commit to ports. Is this upstream too? I have not upstreamed the patch yet, but will contact John Tapsell soon with the fix. Given that it's in a FreeBSD-only file, I think you can just commit and cherry-pick it to the appropriate stable branch there. I agree, except I do not have commit access to KDE. signature.asc Description: This is a digitally signed message part. ___ 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] Re: [SVN Commit] area51/KDE/sysutils/ksysguardd
On Saturday 23 April 2011 01:40:24 Raphael Kubo da Costa wrote: David Bruce Naylor naylor.b.da...@gmail.com writes: SVN commit 7200 by DragonSA: Update ksysguardd and fix bug (causes segfault). ksysguardd no longer uses libkvm so does not need g+s or grp=kmem and ksysguardd can now run as a regular (unprivileged) user. An error in calculating MSI offsets resulted in the last regular interrupt being included as a MSI interrupt and a buffer underrun, causing a segfault. This has been fixed. @avilla: please push this commit to ports. Is this upstream too? I have not upstreamed the patch yet, but will contact John Tapsell soon with the fix. signature.asc Description: This is a digitally signed message part. ___ 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] KSysGuard and KDE 4.6.2
Hi All, With the release of KDE 4.6.2 many improvements have been made to KSysGuard, however some of them are POLA violation. Although legacy monitors are in place, so existing configurations should work fine, the location of some sensors have been moved. If your existing setup does not work or you take exception to the new layout of the sensors (or there are bugs) please contact me. Special thanks to John Tapsell who merged the changes at the last moment (or we would be waiting till 4.6.3 or 4.7.0). Regards, David P.S. Any requests for improvement to KSysGuard are welcome. signature.asc Description: This is a digitally signed message part. ___ 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] Re: [SVN Commit] area51/KDE/sysutils/ksysguardd/files
On Tuesday 05 April 2011 20:13:06 Raphael Kubo da Costa wrote: SVN commit 7096 by rakuco: ksysguardd: Remove patch to fix the 4.6.2 build. David, can you check kde-workspace commit cb2cf1ca and see if this is the appropriate thing to do? D patch-ksysguardd.c This looks okay to me. The #ifdef was introduced to fix builds with -Wall -Werror. Since the CMake build is not that pedantic we should be fine. signature.asc Description: This is a digitally signed message part. ___ 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] Re: Testing KDE 4.6.1
On Thursday 10 March 2011 23:33:57 Raphael Kubo da Costa wrote:
David Naylor naylor.b.da...@gmail.com writes:
I've compiled KDE 4.6.1 (from about Tuesday) and have the following
problems:
- Nepomuk (with strigi?) still get stuck on some PDFs and consume 100%
resources
- Nepomuk crashes when it exits (will get around to producing proper
tracebacks for that)
I've never used Nepomuk for anything useful here (and it didn't work
properly until recently here), but you may try removing the strigi
and/or nepomuk directories and starting over -- it did help here after I
had accumulated enough cruft from several months of trunk and releases.
Strigi puts stuff in ~/.strigi, nepomuk has things in
$KDEHOME/share/{apps,config}/nepomuk* (there are some configuration
files that might be worth keeping).
I don't have a ~/.strigi directory. I cleared out most nepomuk related stuff
but strigi still choked on one of my PDFs. Also I have been getting some
nepomukservicestub crashes.
Once a few things have been released to ports I will be doing a complete
system reinstall (wipe everything out). That may fix this issue?
If that does not help and you are not in the mood for tracking down the
issue, you can try simply disabling Strigi or making it not index any
directory by default.
I'll give it a try, move all PDFs into their own directory and see which one
it is.
signature.asc
Description: This is a digitally signed message part.
___
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] Testing KDE 4.6.1
Hi, I've compiled KDE 4.6.1 (from about Tuesday) and have the following problems: - Nepomuk (with strigi?) still get stuck on some PDFs and consume 100% resources - Nepomuk crashes when it exits (will get around to producing proper tracebacks for that) - kmail exits after report about nepomuk searching service not available - ksysguardd did not install properly first time (maybe something wrong with my system). A `make deinstall reinstall` fixed that. - amarok crashed once, don't know why Regards, David signature.asc Description: This is a digitally signed message part. ___ 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] Re: KDE 4.6.0
On Sunday 06 March 2011 14:49:43 Alberto Villa wrote: hello! i took some time to answer to you on this :) On Sunday 20 February 2011 06:34:10 David Naylor wrote: * kdm lost my kde session. I had to manually select KDE Plasma Workspace your kde session? you have manually created sessions? i'm not sure i understood this point This is the term kdm used. I assume that my KDE 4.5.4 KDE session did not have the same name as the KDE 4.6.0 one. It was a one time thing (and may be specific to my setup). * KDE informed me that some of my sound devices were detached and wanted to know if it should forget about them. Sound still works perfectly... it's probably due to gstreamer being the new default phonon backend in place of xine. actually, we need to write some instructions on how to make sound work correctly with it (it's material for freebsd.kde.org, just need time to write it) if you could share a screenshot of the sound cards detected by phonon, it would help us in generalising the howto I would like to point out that my sound never stopped working. Just a message about lost sound cards. * Strigi gets stuck on some PDF files (busy loop with nepomukservicestub) you mean while indexing? did you cleanup your strigi files from kde 4.5? does it happen always with the same files? my experience with nepomuk and strigi has been awesome after the upgrade from 4.6.0 rc1 to 4.6.0 Yes, always the same files (PDF). I saw on the comments on dot.kde.org for the KDE 4.6.1 release that this was a known issue and has been fixed :-). * Okular still does not print out-of-the-box (doing `cd /usr/local/bin; ln -s lpr lpr.cups` works well) this was fixed a couple of weeks ago Yes I saw, my update was before then. * The KDE resources kconfig module freezes when opened (a kdepim-4.6.0 problem, not present with old in-ports kdepim). * I had a few problems with KMail2, which I reported upstream. Old KMail is working fine. eh... kdepim 4.6... :) Yes, I know... Other than two initial problems, strigi (which I do not use) and those relating to the upcoming kdepim everything is running better :-) cool! Thank you for all the work. thank you for reporting back and for your work as well I have also been having crashes with plasma-desktop, related to kevent (or kevent was in traceback). Alas I don't have debug information compiled in and thus do not have a proper traceback (or even the cause of the crash). I see KDE 4.6.1 is in area51, I'll start an update and see how that goes. signature.asc Description: This is a digitally signed message part. ___ 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] Re: [REVIEW] ksysguard (aka System Monitor) improvements (take 1)
On Saturday 05 March 2011 02:22:00 Alberto Villa wrote: On Tuesday 04 January 2011 16:20:06 David Naylor wrote: I have been working on improving the coverage of ksysguard's sensors. There is still lots of work to be done but I would like feedback for what has already been coded. wonderful job! i've finally found some time to test it and it works perfectly. i'll attach this to 4.6.1! only one thing: is this output at ksysguardd startup expected? http://pastebin.com/6nX0MHfW Those are debug messages that were left in accidently. The new patch should not have that problem (just like the previous patch should not have had ;-) ) I have added sensors for: - cpu temperature (as reported by coretemp and amdtemp) whoohoo! I would like to create a port for just ksysguardd. This will allow remote monitoring of computers without requiring the installation of kdebase4- workspace (a very big port with many dependancies). i'll do this Thanks thanks a lot! we'll try to let users know this when 4.6.1 hits the tree, so that any problems will hopefully come out I've updated the patch, see my previous email to you (and the list). signature.asc Description: This is a digitally signed message part. ___ 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] [REVIEW] ksysguard (aka System Monitor) improvements (take 2)
Hi All, I have an updated ksysguard patch, the changes since the last patch are: * ACPI thermal and battery sensors * Support for MSI interrupts * Rewrite of ProcessList (untestable at the moment) * Last used PID (like top) * Display disk stats in sizes (KiB, MiB, GiB, TiB) instead of blocks * Right align numbers in Partition Usage Table * Fix description for root partition * Inode (or is it Vnode) information for partition usage There is currently a (pre-existing) bug in ksysguard that prevents one seeing remote process lists (ksysguard crashes). Is anyone interested in Last PID or would a launched processes count (i.e current Last PID - previous Last PID) be more useful, or both? See previous email on how to test patch (http://mail.kde.org/pipermail/kde- freebsd/2011-January/010016.html) [after running unxz ksysguard.diff.xz] Regards, David P.S. Thanks to avilla@ for reviewing a patch that didn't make it to the list. ksysguard.diff.xz Description: application/xz signature.asc Description: This is a digitally signed message part. ___ 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] Re: [RFC] fix okular printing
On Thursday 27 January 2011 11:47:04 Alberto Villa wrote: On Thu, Jan 27, 2011 at 2:34 AM, Raphael Kubo da Costa kub...@gmail.com wrote: I see. With my upstream hat on, I don't feel very comfortable with the patch in its current form -- do you intend to send it to the Okular developers? well, that patch is absolutely wrong for upstream imho too I agree. The patch is a very specific workaround based on the FreeBSD ports environment and is probably not applicable to anyone else. Do you all think it makes sense to contact the cups-base maintainer to see if it's possible to add a lpr.cups or lpr-cups symlink? That way Okular wouldn't need to be patched at all. is okular searching for those binaries too? then i'm ok with this solution. a quick search on google seems to suggest that lpr-cups is more standard, so if we have to choose i vote for this, btu dinoex@ might be comfortable with adding both, of course waiting for other's opinion That is certainly a good option, it may very well benefit other ports as well. I second. Who will bring this up with dinoex@? signature.asc Description: This is a digitally signed message part. ___ 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] Re: [RFC] fix okular printing
On Wednesday 26 January 2011 12:08:25 Alberto Villa wrote: On Wed, Jan 26, 2011 at 5:27 AM, Raphael Kubo da Costa kub...@gmail.com wrote: Shouldn't it work if you put /usr/local before /usr in your $PATH? but that's not the default on freebsd One work around is the CUPS_OVERWRITE_BASE knob however that is not a default option. What port is it in? print/cups-base. it will replace /usr/bin/lpr with (a link to) cups lpr. i don't think we should depend on this I agree. My intention was to create a patch that will fix okular on any setup and without requiring user intervention. It should Just Work. signature.asc Description: This is a digitally signed message part. ___ 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] [REVIEW] ksysguard (aka System Monitor) improvements (take 1)
Hi, I have been working on improving the coverage of ksysguard's sensors. There is still lots of work to be done but I would like feedback for what has already been coded. I have added sensors for: - context switches - cpu load (per cpu) - cpu interrupt load (ports patch) - cpu temperature (as reported by coretemp and amdtemp) - interrupts (irqs 0-23, sortware and hardware) - memory (active, inactive and wired) - swap (swapped in and out) - syscalls - traps - uptime (ports patch) I have improved sensors: - DiskStatUsed (upper bound) - DiskStatFree (upper bound) Of the interrupts stray irqs and cpu timers are not reported (any suggestions?). I would like to expose sysctl to ksysguardd (the relevant parts, i.e. no strings). I would like to create a port for just ksysguardd. This will allow remote monitoring of computers without requiring the installation of kdebase4- workspace (a very big port with many dependancies). There is a Makefile in the attached patch that does all the heavy lifting. To test the patch, extract it and: # cd /usr/ports/x11/kdebase4-workspace # rm files/patch-ksysguard* # cp /path/to/patch files/patch-ksysguard # make all deinstall reinstall Alternatively, if all you want is to install ksysguardd (the important part): (repeat above steps expect for make, then) # make -C `make -V WRKSRC`/ksysguard/ksysguardd install (note, the deinstall target is uninstall) however not all the sensors in ksysguard will have proper labels. If there are any problems please let me know. Regards, David ksysguard-1.diff.gz Description: GNU Zip compressed data signature.asc Description: This is a digitally signed message part. ___ 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] Re: Desktop effects suspended -- KDE4-4.5.1
On Monday 01 November 2010 09:17:04 Mike Barnard wrote: Hi, On Mon, Oct 25, 2010 at 2:05 PM, Mike Barnard mike.barna...@gmail.comwrote: as mentioned above, I think my PIM not working well is due to akonadi crashing... I'll pay more attention to it next time it acts up and check what is not running and what has dumped core. OK.. I had some time to take a look at this and try and figure out what was going on. Akonadi consumes almost all my 2GB of memory and eating about 36% of CPU when things get slowed down, Xorg is spiraling out of control, eating about 60% of CPU and some 1GB of memory. I only use KMail (without Kontact) and I've never seen akonadi use so much resources. It does look like akonadi is misbehaving, perhaps upstream can help with that. If I kill kontact, the 2GB memory is released and Xorg drops to about 16% of CPU, but still eats up about 1GB of memory. I updated my ports collection and updated all out-of-date ports and still the same behaviour. I notice that there have been a few patches, I am updating my ports collection again this morning and will get any ports out of date back up-to-date and check again. Recompiling everything may fix it. It is possible some dependency is not ABI forward compatible. PS: Akonadi is not crashing this time round, it just consumes lots of resources. Any one with ideas on what to check for, I'll get on it. You can also try cleaning out akonadi resources, such as: # rm -rf ~/.local/share/akonadi # rm -rf ~/.config/akonadi (make sure you back up, may eat your data) signature.asc Description: This is a digitally signed message part. ___ 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] Re: Desktop effects suspended -- KDE4-4.5.1
On Saturday 23 October 2010 18:48:26 Adam Vande More wrote: 2010/10/23 David Naylor naylor.b.da...@gmail.com I sometimes have firefox freeze on me because nsviewer.bin crashes (aka flash). It does a core dump and firefox freezes until that finishes. http://lists.freebsd.org/pipermail/freebsd-emulation/2010-September/008065. html Also in regards to linux flash freezes, using flashblock stops 95%(made up stats) of the freezing. Using this method with the regular player, not debug + flashblock gives me about as good of flash experience on FreeBSD as a Windows system. I mostly use Chromium, which I find is more stable (and doesn't freeze when flash goes down). I still need to use Firefox for some flash that Chromium doesn't handle. Thanks for the flashblock tip. It works like a charm. http://lists.freebsd.org/pipermail/freebsd-emulation/2010-September/008103. html Interesting, I missed that email. Thanks signature.asc Description: This is a digitally signed message part. ___ 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] Re: Desktop effects suspended -- KDE4-4.5.1
On Saturday 23 October 2010 09:30:48 Mike Barnard wrote: On Fri, Oct 22, 2010 at 7:21 PM, Rusty Nejdl rne...@ringofsaturn.comwrote: Are you using the flash plugin and nspluginwrapper by any chance? If so, try disabling it. I am still testing things but I was good for a few days and then reinstalled that and found my cpu leaked again. I have removed it and reinstalled gnash and my cpu is back to normal. I do have the linux-flash plugin installed and nspluginwrapper. I'll get it uninstalled and try out gnash. Although when KDE goes to sleep, my CPU is not chocking at all. I sometimes have firefox freeze on me because nsviewer.bin crashes (aka flash). It does a core dump and firefox freezes until that finishes. Do you have any .core files in your home directory? Also look at IO activity when firefox freezes next. With regards to PIM, I had KMail refusing to type sometimes, I found `akonadictl restart` or if akonadi isn't running `akonadictl start` fixes the problem. Regards, David signature.asc Description: This is a digitally signed message part. ___ 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] Fwd: kdelibs4 build failed
On Friday 17 September 2010 09:40:30 N V wrote: Hi again. There is build log of kdelibs4 in attachment. Command was make -DDISABLE-MAKE-JOBS -DCMAKE-VERBOSE. Your command is wrong, it should be: # make clean all -DDISABLE_MAKE_JOBS -DCMAKE_VERBOSE (Note the underscores). The ``clean all'' is to make sure there is nothing strange going on. Please resend me the build logs using the above command. I couldn't see what went wrong in the previous log FYI, setting -DBATCH implies -DCMAKE_VERBOSE. Regarding a clean environment or tinderbox/sandbox environment, it is possible for extra packages that are installed to break the build of a port. A clean environment is where only the ports dependencies are installed (and all other packages are uninstalled). It may help in exceptional circumstances. Regards 16.09.10, 15:27, David Naylor : On Thursday 16 September 2010 10:40:55 N V wrote: Hi all. Build of kdelibs4 from ports failed. All required ports are up to date. FreeBSD 8.1-RELEASE i386. Here are last lines of CMakeError.log: Hi, Please include the output from `make configure` (which is where I assume it is failing). It is curious in that it fails with pstat yet the function pstat does not exist on my system (-current). Only a utility. Furthermore the logs you posted do not include the source code it was trying to compile. If possible could you try building in a clean environment? I've got a few scripts that will be able to set one up for you. Regards signature.asc Description: This is a digitally signed message part. ___ 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] Fwd: kdelibs4 build failed
On Thursday 16 September 2010 10:40:55 N V wrote: Hi all. Build of kdelibs4 from ports failed. All required ports are up to date. FreeBSD 8.1-RELEASE i386. Here are last lines of CMakeError.log: Hi, snip/ Please include the output from `make configure` (which is where I assume it is failing). It is curious in that it fails with pstat yet the function pstat does not exist on my system (-current). Only a utility. Furthermore the logs you posted do not include the source code it was trying to compile. If possible could you try building in a clean environment? I've got a few scripts that will be able to set one up for you. Regards signature.asc Description: This is a digitally signed message part. ___ 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] [RFC] fix defaults on kcontrol/kdm
Hi,
Attached is a patch that fixes the defaults for shutdown and reboot commands.
This only affects the kcontrol module. The implicit defaults for the config
file
are correct.
I've filed a bug report (https://bugs.kde.org/show_bug.cgi?id=250989).
If appropriate please commit to ports/area51.
Regards,
David
--- kcontrol/kdm/kdm-shut.cpp~ 2010-09-14 18:48:33.0 +0200
+++ kcontrol/kdm/kdm-shut.cpp 2010-09-14 18:50:05.0 +0200
@@ -76,7 +76,7 @@
shutdown_label-setBuddy(shutdown_lined);
connect(shutdown_lined, SIGNAL(textChanged(const QString )),
SIGNAL(changed()));
-wtstr = i18n(Command to initiate the system halt. Typical value: /sbin/halt);
+wtstr = i18n(Command to initiate the system halt. Typical value: /sbin/shutdown -p now);
shutdown_label-setWhatsThis(wtstr);
shutdown_lined-setWhatsThis(wtstr);
@@ -85,7 +85,7 @@
restart_label-setBuddy(restart_lined);
connect(restart_lined, SIGNAL(textChanged(const QString )),
SIGNAL(changed()));
-wtstr = i18n(Command to initiate the system reboot. Typical value: /sbin/reboot);
+wtstr = i18n(Command to initiate the system reboot. Typical value: /sbin/shutdown -r now);
restart_label-setWhatsThis(wtstr);
restart_lined-setWhatsThis(wtstr);
@@ -187,16 +187,16 @@
readSD(sdrcombo, Root, config-group(X-*-Core));
KConfigGroup configGrp = config-group(Shutdown);
-restart_lined-setUrl(configGrp.readEntry(RebootCmd, /sbin/reboot));
-shutdown_lined-setUrl(configGrp.readEntry(HaltCmd, /sbin/halt));
+restart_lined-setUrl(configGrp.readEntry(RebootCmd, /sbin/shutdown -r now));
+shutdown_lined-setUrl(configGrp.readEntry(HaltCmd, /sbin/shutdown -p now));
bm_combo-setCurrentId(configGrp.readEntry(BootManager, None));
}
void KDMSessionsWidget::defaults()
{
-restart_lined-setUrl(KUrl(/sbin/reboot));
-shutdown_lined-setUrl(KUrl(/sbin/halt));
+restart_lined-setUrl(KUrl(/sbin/shutdown -r now));
+shutdown_lined-setUrl(KUrl(/sbin/shutdown -p now));
sdlcombo-setCurrentIndex(SdAll);
sdrcombo-setCurrentIndex(SdRoot);
signature.asc
Description: This is a digitally signed message part.
___
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] FreeBSD branded artwork?
Hi, Ivan Cukic posted [1] a FreeBSD branded wallpaper. Could this be included in the KDE ports? Apologies if this is already (quietly) in the works. Regards, David [1] http://ivan.fomentgroup.org/blog/2010/09/05/stripes-kde-be-free-freebsd/ signature.asc Description: This is a digitally signed message part. ___ 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] k3b-kde4 crashes after audio rip
On Saturday 07 August 2010 04:30:35 Raphael Kubo da Costa wrote: On Friday 06 August 2010 09:07:42 David Naylor wrote: On Thursday 05 August 2010 19:45:56 Raphael Kubo da Costa wrote: On Thursday 05 August 2010 13:53:26 David Naylor wrote: Hi, k3b-kde4 is crashing when closing the Audio rip dialog (after ripping has started). This happens if ripping is cancelled or finished. See attached for the traceback. Removing the ``delete d-paranoiaLib'' line from k3baudioripjob.cpp fixes the problem. Regards Do you know if this is FreeBSD-specific? At first glance it looks like it's better to report it on bugs.kde.org so Michal can fix it upstream. Another two items that I have found: - k3b does not rip the tracks in order - track 1 doesn't get ripped unless done individually I will be surprised if it wasn't FreeBSD specific as surely someone picked up this problem before? Is there a good KDE4 based debugger, I'll try track down the problem (and provide patches)? Regards The only debugger I know of is gdb, were you looking for something GUI-based? It'd be good to at least open the reports on bugs.kde.org and see if the upstream developers can provide any guidance on how to solve those problems in case they're FreeBSD-specific. Any way to watch a variable in gdb? Kdbg was very useful but I'm running a KDE4 only system. I've reported the bug as # 247233 (https://bugs.kde.org/show_bug.cgi?id=247233) signature.asc Description: This is a digitally signed message part. ___ 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] k3b-kde4 crashes after audio rip
On Thursday 05 August 2010 19:45:56 Raphael Kubo da Costa wrote: On Thursday 05 August 2010 13:53:26 David Naylor wrote: Hi, k3b-kde4 is crashing when closing the Audio rip dialog (after ripping has started). This happens if ripping is cancelled or finished. See attached for the traceback. Removing the ``delete d-paranoiaLib'' line from k3baudioripjob.cpp fixes the problem. Regards Do you know if this is FreeBSD-specific? At first glance it looks like it's better to report it on bugs.kde.org so Michal can fix it upstream. Another two items that I have found: - k3b does not rip the tracks in order - track 1 doesn't get ripped unless done individually I will be surprised if it wasn't FreeBSD specific as surely someone picked up this problem before? Is there a good KDE4 based debugger, I'll try track down the problem (and provide patches)? Regards signature.asc Description: This is a digitally signed message part. ___ 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] k3b-kde4 crashes after audio rip
Hi, k3b-kde4 is crashing when closing the Audio rip dialog (after ripping has started). This happens if ripping is cancelled or finished. See attached for the traceback. Removing the ``delete d-paranoiaLib'' line from k3baudioripjob.cpp fixes the problem. Regards Application: K3b (k3b), signal: Bus error: 10 [Switching to Thread 80a40b980 (LWP 100515)] [Current thread is 1 (Thread 80a40b980 (LWP 100515))] Thread 3 (Thread 80a4071c0 (LWP 100275)): [KCrash Handler] #6 qDeleteAllQMapK3b::Device::Device*, K3b::CdparanoiaLibData*::const_iterator (begin=) at qalgorithms.h:322 #7 0x000800a2 in ~CdparanoiaLib (this=) at qalgorithms.h:330 #8 0x005131cf in ~AudioRipJob (this=0x81374cbb0) at /tmp/usr/ports/sysutils/k3b-kde4/work/k3b-2.0.0/src/rip/k3baudioripjob.cpp:101 #9 0x0051fadb in K3b::AudioRippingDialog::slotStartClicked (this=0x7fffc4b0) at /tmp/usr/ports/sysutils/k3b-kde4/work/k3b-2.0.0/src/rip/k3baudiorippingdialog.cpp:307 #10 0x0059bf00 in K3b::InteractionDialog::slotStartClickedInternal (this=0x7fffc4b0) at /tmp/usr/ports/sysutils/k3b-kde4/work/k3b-2.0.0/src/k3binteractiondialog.cpp:312 #11 0x0059c94d in K3b::InteractionDialog::qt_metacall (this=0x7fffc4b0, _c=QMetaObject::InvokeMetaMethod, _id=) at k3binteractiondialog.moc:161 #12 0x0051efe4 in K3b::AudioRippingDialog::qt_metacall (this=0x7fffc4b0, _c=QMetaObject::InvokeMetaMethod, _id=) at k3baudiorippingdialog.moc:70 #13 0x0008056859e7 in QMetaObject::activate () from /usr/local/lib/qt4/libQtCore.so.4 #14 0x00080630fe1a in QAbstractButton::clicked () from /usr/local/lib/qt4/libQtGui.so.4 #15 0x00080604e522 in QAbstractButtonPrivate::emitClicked () from /usr/local/lib/qt4/libQtGui.so.4 #16 0x00080604f4da in QAbstractButtonPrivate::click () from /usr/local/lib/qt4/libQtGui.so.4 #17 0x00080604f6b0 in QAbstractButton::mouseReleaseEvent () from /usr/local/lib/qt4/libQtGui.so.4 #18 0x000805d0ab94 in QWidget::event () from /usr/local/lib/qt4/libQtGui.so.4 #19 0x00080604e9ce in QAbstractButton::event () from /usr/local/lib/qt4/libQtGui.so.4 #20 0x0008060e0125 in QPushButton::event () from /usr/local/lib/qt4/libQtGui.so.4 #21 0x000805cb63ef in QApplicationPrivate::notify_helper () from /usr/local/lib/qt4/libQtGui.so.4 #22 0x000805cbe718 in QApplication::notify () from /usr/local/lib/qt4/libQtGui.so.4 #23 0x0008047f83a6 in KApplication::notify () from /usr/local/lib/libkdeui.so.7 #24 0x00080567480e in QCoreApplication::notifyInternal () from /usr/local/lib/qt4/libQtCore.so.4 #25 0x000805cb9729 in QApplicationPrivate::sendMouseEvent () from /usr/local/lib/qt4/libQtGui.so.4 #26 0x000805d33f77 in QETWidget::translateMouseEvent () from /usr/local/lib/qt4/libQtGui.so.4 #27 0x000805d33124 in QApplication::x11ProcessEvent () from /usr/local/lib/qt4/libQtGui.so.4 #28 0x000805d5a4a8 in x11EventSourceDispatch () from /usr/local/lib/qt4/libQtGui.so.4 #29 0x0008091ebf2e in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0 #30 0x0008091ef230 in g_main_context_check () from /usr/local/lib/libglib-2.0.so.0 #31 0x0008091ef812 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0 #32 0x00080569cd9c in QEventDispatcherGlib::processEvents () from /usr/local/lib/qt4/libQtCore.so.4 #33 0x000805d5a2fe in QGuiEventDispatcherGlib::processEvents () from /usr/local/lib/qt4/libQtGui.so.4 #34 0x000805673bab in QEventLoop::processEvents () from /usr/local/lib/qt4/libQtCore.so.4 #35 0x000805673e85 in QEventLoop::exec () from /usr/local/lib/qt4/libQtCore.so.4 #36 0x00080615573c in QDialog::exec () from /usr/local/lib/qt4/libQtGui.so.4 #37 0x0059f579 in K3b::InteractionDialog::exec (this=0x7fffc4b0) at /tmp/usr/ports/sysutils/k3b-kde4/work/k3b-2.0.0/src/k3binteractiondialog.cpp:526 #38 0x00523d2a in K3b::AudioCdView::startRip (this=0x80e3af380) at /tmp/usr/ports/sysutils/k3b-kde4/work/k3b-2.0.0/src/rip/k3baudiocdview.cpp:313 #39 0x00527e2a in K3b::AudioCdView::qt_metacall (this=0x80e3af380, _c=QMetaObject::InvokeMetaMethod, _id=) at k3baudiocdview.moc:93 #40 0x0008056859e7 in QMetaObject::activate () from /usr/local/lib/qt4/libQtCore.so.4 #41 0x000805cb05c4 in QAction::triggered () from /usr/local/lib/qt4/libQtGui.so.4 #42 0x000805cb17c2 in QAction::activate () from /usr/local/lib/qt4/libQtGui.so.4 #43 0x00080604f497 in QAbstractButtonPrivate::click () from /usr/local/lib/qt4/libQtGui.so.4 #44 0x00080604f6b0 in QAbstractButton::mouseReleaseEvent () from /usr/local/lib/qt4/libQtGui.so.4 #45 0x00080610fbbc in QToolButton::mouseReleaseEvent () from /usr/local/lib/qt4/libQtGui.so.4 #46 0x000805d0ab94 in QWidget::event () from /usr/local/lib/qt4/libQtGui.so.4 #47 0x00080604e9ce in QAbstractButton::event () from /usr/local/lib/qt4/libQtGui.so.4 #48 0x000806111d91 in QToolButton::event ()
[kde-freebsd] k3b causing kernel panic
Hi, K3b is causing FreeBSD to panic with a recent amd64 custom kernel from current. The kernel is from ~ 1 July) and does include the changes from r209590. Some of the changes I made include: options ATA_CAM and I have one DVD-RW installed: # dmesg | grep 'cd[0-9]' cd0 at ata0 bus 0 scbus0 target 0 lun 0 cd0: ASUS DRW-1814BL 1.13 Removable CD-ROM SCSI-0 device cd0: 66.700MB/s transfers (UDMA4, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed The backtrace from the panic: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x7fffca10 fault code = supervisor write data, page not present instruction pointer = 0x20:0x801deffb stack pointer = 0x28:0xff80ae07ab00 frame pointer = 0x28:0xff80ae07ab30 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (irq14: ata0) [ thread pid 12 tid 100039 ] Stopped at ata_pio_read+0x10a: repe insw %dx,%es:(%rdi) db bt Tracing pid 12 tid 100039 td 0xff0002a013d0 ata_pio_read() at ata_pio_read+0x10a ata_end_transaction() at ata_end_transaction+0x45f ata_interrupt_locked() at ata_interrupt_locked+0x54 ata_interrupt() at ata_interrupt+0x34 intr_event_execute_handlers() at intr_event_execute_handlers+0xf9 ithread_loop() at ithread_loop+0x8e fork_exit() at fork_exit+0x118 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xff80ae07ad30, rbp = 0 --- Is there anything I can do to assist diagnostics? Regards, David signature.asc Description: This is a digitally signed message part. ___ 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] can't configure printer
On Wednesday 23 December 2009 01:08:09 Mark Moellering wrote: Whenever I try to configure the printer, I get an error: system-config-printer Traceback (most recent call last): File /usr/local/share/system-config-printer/system-config-printer.py, line 38, in module import gnome ImportError: No module named gnome I can't believe I am the only one having this problem. I compiled kde-4.3.4 from ports a few days ago. I get the same problem if I run `system-config-printer` however the KDE version is a systemsettings module (under Computer Administration). signature.asc Description: This is a digitally signed message part. ___ 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] Accidental panel deletion kde4.3.3
On Sunday 29 November 2009 21:17:40 David Southwell wrote: I accidentally deleted the panels from kde4.3.3 screen. The fact I cannot honestly blame the cat whom I was shooing away from the keyboard whilst wielding my mouse adds to the frustration of not being able to use the panels, change screens, launch applications or see the clock!! Can anyone tell me how I might rebuild the default panels and application links? You could always do it manually (right click on desktop and add panel then add widgets). Alternatively you could remove ~/.kde4/share/config/plasma-desktop-appletsrc, this will wipe the plasma setting clean and *should* restore the defaults. If all else fails remove ~/.kde4 (wiping all KDE settings, this will restore all defaults when you next log in). Regards signature.asc Description: This is a digitally signed message part. ___ 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] Fixing kdm defaults
On Sunday 22 November 2009 21:00:17 Raphael Kubo da Costa wrote: On Tuesday 17 November 2009 15:07:09 Raphael Kubo da Costa wrote: On Tuesday 17 November 2009 09:56:19 David Bruce Naylor wrote: Hi, Although kdm reports the correct shutdown commands in the comments for the kdmrc file, these 'defaults' are not actually adhered to. This is due to a few missing includes resulting in the correct system not being detected (sys/param.h is missing, which means BSD never gets defined and thus kdm defaults to linux). It appears that the only place sys/param is included properly is in genkdmconf which is enough for the comments about the default to be correct but nothing more. See attached for a patch that fixes this. It might be considered a bit of a hack but it fits in nicely with all the other 'hacks'. Regards, David P.S. I've submitted a bug report: Patches in Bugzilla have a high chance of being forgotten for ages. I suggest you either contact Oswald Buddenhagen, KDM's maintainer, post it via ReviewBoard or send it to the kde-devel or kde-core-devel mailing lists. Cheers, Raphael Hi, David, Were you able to contact ossi? Yes, I have. He is aware of the bug report (I assume he will merge it as he didn't voice any objections to it). signature.asc Description: This is a digitally signed message part. ___ 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 + KDE + GRUB = Happy family
On Wednesday 18 November 2009 16:42:14 Raphael Kubo da Costa wrote:
On Wednesday 18 November 2009 12:27:27 David Bruce Naylor wrote:
Hi,
I've managed to get kdm to work nicely with our grub. See attached for
the patch. This requires a 'special' menu.lst to support selecting next
boot OS and the BootManager option in kdmrc to be set to GRUB.
Sample file:
# Important line, tells grub to use saved option to boot from
default saved
timeout 3
title FreeBSD 8.0-i386
root (hd1,0,a)
kernel /boot/loader
# Set the default, for next boot, to 1
savedefault 1
title FreeBSD 8.0-amd64
root (hd0,0,a)
kernel /boot/loader
# No need to set default as we are it
#savedefault
# Windows Vista
title Windows Vista
root (hd1,1)
makeactive
chainloader +1
# Set the default, for next boot, to 1
savedefault 1
Make sure you run `grub-set-default 1` otherwise grub will bork when it
hits the savedefault line (since it cannot create files and expects one
to be there).
Most of the linux distributions have a patched version of grub that
allows a difference (and easier) setup. (The patch is called
grub-0.97-once.) We could integrate that patch (and eliminate the need
for this patch) but I feel this way allows for greater flexibility.
Outstanding task: teach kdm to read the defaults file to correctly get
the next booting option (vs assuming the first one is the default).
For those on amd64 an easy way to get grub to work is to install the i386
grub package (it doesn't have any dependencies beyond the base system).
I'm currently running grub on amd64.
Regards,
David
Do you think you can make the patch flexible enough so that it still works
on Linux? Could it be pushed upstream?
See attached for the 'flexible' patch. This *should* handle both the standard
and patched versions of grub. There is no way for me to check if the original
behaviour works.
Is there anyone on list who can push these patches upstream (including the one
to use the correct shutdown options)? If not I'll send an e-mail to kdm's
maintainer.
Regards
--- kdm/backend/bootman.c~ 2009-02-04 20:19:06.0 +0200
+++ kdm/backend/bootman.c 2009-11-19 12:25:38.0 +0200
@@ -40,6 +40,7 @@
#include string.h
#include unistd.h
#include stdio.h
+#include stdlib.h
#include ctype.h
static int
@@ -68,20 +69,30 @@
return buf;
}
-#define GRUB_MENU /boot/grub/menu.lst
+#define GRUB_MENU/boot/grub/menu.lst
+#define GRUB_DEFAULT /boot/grub/default
-static char *grub;
+#define GRUB_SET_DEFAULT grub-set-default
+#define GRUB grub
+
+static char *grub = NULL;
+static int grub_set_default;
static int
getGrub( char ***opts, int *def, int *cur )
{
FILE *f;
- char *ptr, *linp;
- int len;
+ char *ptr, *endptr, *linp;
+ int len, no_default = 1;
char line[1000];
- if (!grub !(grub = locate( grub )))
- return BO_NOMAN;
+ if (!grub)
+ if (grub = locate( GRUB_SET_DEFAULT ))
+ grub_set_default = 1;
+ else if (grub = locate( GRUB ))
+ grub_set_default = 0;
+ else
+ return BO_NOMAN;
*def = 0;
*cur = -1;
@@ -91,8 +102,11 @@
return errno == ENOENT ? BO_NOMAN : BO_IO;
while ((len = fGets( line, sizeof(line), f )) != -1) {
for (linp = line; isspace( *linp ); linp++, len--);
- if ((ptr = match( linp, len, default, 7 )))
- *def = atoi( ptr );
+ if ((ptr = match( linp, len, default, 7 ))) {
+ *def = strtol( ptr, endptr, 10 );
+ if (ptr != endptr)
+no_default = 0;
+ }
else if ((ptr = match( linp, len, title, 5 ))) {
for (; isspace( ptr[len - 1] ); len--);
*opts = addStrArr( *opts, ptr, len );
@@ -100,6 +114,17 @@
}
fclose( f );
+ if (no_default (f = fopen( GRUB_DEFAULT, r ))) {
+ if (fGets( line, sizeof(line), f ) != -1) {
+ *def = strtol(line, NULL, 10);
+ no_default = 0;
+ }
+ fclose( f );
+ }
+
+ if ( no_default )
+ *def = -1;
+
return BO_OK;
}
@@ -130,18 +155,28 @@
static void
commitGrub( void )
{
- FILE *f;
- int pid;
- static const char *args[] = { 0, --batch, --no-floppy, 0 };
-
if (sdRec.bmstamp != mTime( GRUB_MENU )
setGrub( sdRec.osname, sdRec ) != BO_OK)
return;
- args[0] = grub;
- if ((f = pOpen( (char **)args, 'w', pid ))) {
- fprintf( f, savedefault --default=%d --once\n, sdRec.osindex );
- pClose( f, pid );
+ if (grub_set_default) {
+ static char idx[3];
+ static char *args[] = { 0, 0, 0 };
+
+ args[0] = grub;
+ args[1] = idx;
+ snprintf( idx, 2, %i, sdRec.osindex );
+ runAndWait( args, NULL );
+ } else {
+ FILE *f;
+ int pid;
+ static const char *args[] = { 0, --batch, --no-floppy, 0 };
+
+ args[0] = grub;
+ if ((f = pOpen( (char **)args, 'w', pid ))) {
+ fprintf( f, savedefault --default=%d --once\n, sdRec.osindex );
+ pClose( f, pid );
+ }
}
}
signature.asc
Description: This is a digitally signed message part.
Re: [kde-freebsd] [Call for Help] kpythonpluginfactory (Printer Configuration)
On Friday, 30 October 2009 18:25:17 Kris Moore wrote: On Fri, 30 Oct 2009, David Naylor wrote: Hi, It appears that kpythonpluginfactory does not work when the python script calls a lib-dynload object (such as 'import time'). A typical message is: ImportError: /usr/local/lib/python2.6/lib-dynload/time.so: Undefined symbol PyExc_IOError This stops system-settings-printer-kde from working (and, I think plasma- python scripting). I know this worked in KDE 4.2.0. A tentative speculation to the cause leads me to conclude something happened to FreeBSD (I still needs to do an upgrade to RC2)*. I did, however, find a work around: get kpythonpluginfactory to link statically to python. This obviously leads to a bigger file. Does anyone have KDE 4.2.2 running, if so please install print/system-config- printer-kde and see if you can load the Printer Configuration in systemsettings. Please report if the config module loads and what version of KDE and FreeBSD you are running. Thanks, David *I'm also having problems with cups-smb and this may be related David, I did some investigation with this issue a while back. I think its a bug in the python port itself, none of the lib-dynload libraries are linked to the main python library. For example, if you run this: setenv LD_PRELOAD /usr/local/lib/libpython2.6.so ; systemsettings You should now be able to bring up the KDE printer interface. If you do this, you can see what those libs are linked to: # cd /usr/local/lib/python2.6/lib-dynload # setenv LD_LIBRARY_PATH `pwd` # ldd time.so time.so: libm.so.5 = /lib/libm.so.5 libthr.so.3 - /lib/libthr.so.3 libc.so.7 = /lib/libc.so.7 I'm thinking that if we fix the python port to link these lib-dynload/* libaries to /usr/local/lib/libpython2.6.so the problem will go away. Investigating this now actually, but if somebody else had ideas on this, please let us know :) This is actually a design feature of python. If those libraries are linked to libpython then it will break the case where one links statically to libpython. See http://bugs.python.org/issue4434 for the PR at python that discusses it. The way to get around this is to dlopen libpython with RTLD_GLOBAL. I've checked the code in kpythonpluginfactory and that is exactly what it does. That behaviour has never changed. I do remember this working for me a while back and stopped after I did a system wide upgrade. This, I presume, also works for Linux. I'm planning on upgrading to RC2 and if the issue is still present I'll write a simple test program that should exhibit the same behaviour and check to see if it works on older versions of FreeBSD. David signature.asc Description: This is a digitally signed message part. ___ 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] [SOLVED] [Call for Help] kpythonpluginfactory (Printer Configuration)
On Saturday, 31 October 2009 10:26:55 David Naylor wrote:
On Friday, 30 October 2009 18:25:17 Kris Moore wrote:
On Fri, 30 Oct 2009, David Naylor wrote:
Hi,
It appears that kpythonpluginfactory does not work when the python
script calls a lib-dynload object (such as 'import time'). A typical
message is:
ImportError: /usr/local/lib/python2.6/lib-dynload/time.so: Undefined
symbol PyExc_IOError
This stops system-settings-printer-kde from working (and, I think
plasma- python scripting). I know this worked in KDE 4.2.0. A
tentative speculation to the cause leads me to conclude something
happened to FreeBSD (I still needs to do an upgrade to RC2)*.
I did, however, find a work around: get kpythonpluginfactory to link
statically to python. This obviously leads to a bigger file.
Does anyone have KDE 4.2.2 running, if so please install
print/system-config- printer-kde and see if you can load the Printer
Configuration in systemsettings. Please report if the config module
loads and what version of KDE and FreeBSD you are running.
Thanks,
David
*I'm also having problems with cups-smb and this may be related
David,
I did some investigation with this issue a while back. I think its a bug
in the python port itself, none of the lib-dynload libraries are linked
to the main python library. For example, if you run this:
setenv LD_PRELOAD /usr/local/lib/libpython2.6.so ; systemsettings
You should now be able to bring up the KDE printer interface. If you do
this, you can see what those libs are linked to:
# cd /usr/local/lib/python2.6/lib-dynload
# setenv LD_LIBRARY_PATH `pwd`
# ldd time.so
time.so:
libm.so.5 = /lib/libm.so.5
libthr.so.3 - /lib/libthr.so.3
libc.so.7 = /lib/libc.so.7
I'm thinking that if we fix the python port to link these lib-dynload/*
libaries to /usr/local/lib/libpython2.6.so the problem will go away.
Investigating this now actually, but if somebody else had ideas on this,
please let us know :)
This is actually a design feature of python. If those libraries are linked
to libpython then it will break the case where one links statically to
libpython. See http://bugs.python.org/issue4434 for the PR at python that
discusses it.
The way to get around this is to dlopen libpython with RTLD_GLOBAL. I've
checked the code in kpythonpluginfactory and that is exactly what it does.
That behaviour has never changed.
I do remember this working for me a while back and stopped after I did a
system wide upgrade. This, I presume, also works for Linux.
I'm planning on upgrading to RC2 and if the issue is still present I'll
write a simple test program that should exhibit the same behaviour and
check to see if it works on older versions of FreeBSD.
It still does not work under RC2. I am now doubting this is a regression and
it was planetary alignments that had it working for me previously :-)
I wrote a test program that *should* trigger the same problem. See
rtld_global.shar for the program. The default behaviour is my fix, to trigger
the problem run `make -DTRIGGER`. It is a small program and should be easy to
figure out.
See attached for the fix. Add the patch to devel/kdebindings4-python-pykde4
and reinstall.
If you encounter any problems please let me know.
Regards
# This is a shell archive. Save it in a file, remove anything before
# this line, and then unpack it by entering sh file. Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
# rtld_global
# rtld_global/Makefile
# rtld_global/libmaster.c
# rtld_global/main.c
# rtld_global/libslave.c
# rtld_global/common.h
# rtld_global/libplugin.c
#
echo c - rtld_global
mkdir -p rtld_global /dev/null 21
echo x - rtld_global/Makefile
sed 's/^X//' rtld_global/Makefile '54185eeffb995a36288ad17f38c2bdc0'
X.SUFFIXES: .a .c .o .so .so.1
X.SILENT:
X
XCFLAGS=-Wall -rdynamic
X
X.if defined(TRIGGER)
XCFLAGS+=-DTRIGGER
X.endif
X
XCC=cc
XAR=ar
XLN=ln
X
Xall:
X echo Running test without linking:
X make clean test # /dev/null
X echo done
X echo
X echo Running test with linking:
X make clean test -DLINKED # /dev/null
X echo done
X
Xclean:
X rm -f *.a *.o *.so* main
X
Xtest: main libmaster.so libslave.so
X env LD_LIBRARY_PATH=${PWD} ./main
X
X.c.o:
X ${CC} ${CFLAGS} -c -fPIC -o $@ $
X
X.c.so:
X ${CC} ${CFLAGS} -fPIC -shared -Wl,-soname,$@ -o $@ $
X
X.if defined(LINKED)
Xlibplugin.so: libplugin.c libmaster.so
X ${CC} ${CFLAGS} -DLINKED -fPIC -L. -lmaster -shared -Wl,-soname,$@ -o
$@ $
X.endif
X
Xmain: main.o libplugin.so
X cc ${CFLAGS} -o main main.o
54185eeffb995a36288ad17f38c2bdc0
echo x - rtld_global/libmaster.c
sed 's/^X//' rtld_global/libmaster.c '4c7e49ccff36dd33ab5357b611fe5d83'
X
[kde-freebsd] [Call for Help] kpythonpluginfactory (Printer Configuration)
Hi, It appears that kpythonpluginfactory does not work when the python script calls a lib-dynload object (such as 'import time'). A typical message is: ImportError: /usr/local/lib/python2.6/lib-dynload/time.so: Undefined symbol PyExc_IOError This stops system-settings-printer-kde from working (and, I think plasma- python scripting). I know this worked in KDE 4.2.0. A tentative speculation to the cause leads me to conclude something happened to FreeBSD (I still needs to do an upgrade to RC2)*. I did, however, find a work around: get kpythonpluginfactory to link statically to python. This obviously leads to a bigger file. Does anyone have KDE 4.2.2 running, if so please install print/system-config- printer-kde and see if you can load the Printer Configuration in systemsettings. Please report if the config module loads and what version of KDE and FreeBSD you are running. Thanks, David *I'm also having problems with cups-smb and this may be related signature.asc Description: This is a digitally signed message part. ___ 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] plasma-desktop and gdb crash
Hi, On logout I have been experiencing crashes of plasma-desktop. This happens on KDE 4.3.[12]. This is using FreeBSD 8.0rc1. I am unable to get a backtrace due to gdb also crashing. Here is the backtrace from the gdb.core file: (gdb) bt #0 0x2840f857 in kill () from /lib/libc.so.7 #1 0x2840f7b6 in raise () from /lib/libc.so.7 #2 0x2840e514 in abort () from /lib/libc.so.7 #3 0x080c5875 in safe_strerror () #4 0x080c59f3 in internal_verror () #5 0x080c5a28 in internal_error () #6 0x08166910 in _initialize_svr4_solib () #7 0x08166bb6 in _initialize_svr4_solib () #8 0x080d4661 in throw_exception () #9 0x080d46b5 in catch_errors () #10 0x080b891d in no_shared_libraries () #11 0x080b8b2d in solib_add () #12 0x0816b539 in ps_plog () #13 0x08077484 in attach_command () #14 0x080d3d72 in command_line_input () #15 0x080d4661 in throw_exception () #16 0x080d46b5 in catch_errors () #17 0x080d47ad in catch_command_errors () #18 0x08074322 in gdb_main () #19 0x080d4661 in throw_exception () #20 0x080d46b5 in catch_errors () #21 0x08073aa1 in gdb_main () #22 0x08073a5d in main () (gdb) info thre * 1 process 100076 0x2840f857 in kill () from /lib/libc.so.7 Is there anyway to get a backtrace of plasma-desktop upon crash and whats up with gdb? Regards signature.asc Description: This is a digitally signed message part. ___ 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] Printer Configuring
Hi, I can't get my printer configured under KDE 4.3. It did work under 4.2.*. I have kdeutils-printer-applet04.3.0 and system-config-printer-kde-4.3.0 installed and I do get Systemsettings-Computer Administration-Printer Configuration but it doesn't load: ``The service 'Printer Configuration' does not provide an interface 'KCModule' with keyword 'system-config-printer-kde/system-config-printer-kde.py'The factory does not support creating components of specified type.'' Any hints? Regards, David signature.asc Description: This is a digitally signed message part. ___ 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] Some windows in kde4 sometimes become black after resize/maximize
On Thursday 11 June 2009 22:18:34 Yuri wrote: David Naylor wrote: Have you tried: - The latest nvidia-driver? Yes, still a problem. - Toggling Enable direct rendering? This fixes it, but w/out direct rendering performance suffers a lot. That is strange, my indirect rendering doesn't change the performance. Ok, give these changes a try (in xorg.conf [please backup xorg.conf first]). This should fix your indirect rendering performance: (Only these options should be present under section Screen) Section Screen ... Option RenderAccel True Option AllowGLXWithComposite True Option DamageEvents True #Option SLI Auto ... EndSection (NOTE: No options should be present under sections Device or ServerLayout) (( I assume you have compositing enabled, if not add this to the end of xorg.conf Section Extensions Option Composite Enable EndSection )) If this doesn't fix your problem could you please send me your xorg.conf and /var/log/Xorg.0.log. Regards, signature.asc Description: This is a digitally signed message part. ___ 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] Some windows in kde4 sometimes become black after resize/maximize
On Sunday 07 June 2009 02:20:18 Yuri wrote: I use current kde4 on 7.2-PRERELEASE with NVidia 9400GT card, nvidia driver and with compositing type=OpenGL. Sometimes after window is maximized or resized it becomes black. Changing compositing type to XRender and back fixes the problem for a while. And then it happens again. Yuri Have you tried: - The latest nvidia-driver? - Toggling Enable direct rendering? - Toggling Use VSync? - Changing the OpenGL mode? - Changing the Texture filter? Disabling direct rendering fixed some rendering glitches for me (on a 7600GT). Now it runs without flaw. David signature.asc Description: This is a digitally signed message part. ___ 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/kdelibs3 won't build.....................[Fwd: Re: pkgdb -F problem]
On Monday 25 May 2009 21:50:52 Leslie Jensen wrote: Hello Will you Please comment on my problem? I'm sure I did not move any KDE related stuff . The ports I've updated are compiling as they should but not x11/kdelibs3! I would personally wipe the system and start afresh... But practically: It does look like some of your base libraries have gone walking. In the output below (for kdelibs3) libc is under /usr/lib, which is never a good place for it to be. Can you check that the correct libraries are under /lib? Have a look at ldconfig(8), it may be unset if you've moved libraries from underneath it. Try moving all libraries back to their original resting place... If that fails: To get the base libraries installed again try: # cd /usr/src/lib # make obj depend all install if that fails then reinstall the complete system: # cd /usr/src # make world DESTDIR= P.S. Make sure all your data is backed up!!! This may eat your system alive (although never happened personally). Tim Judd skrev: On Thu, May 21, 2009 at 10:20 AM, Frederique Rijsdijk frederi...@isafeelin.org wrote: Leslie Jensen wrote: I've just updated my 7.1-RELEASE to 7.2-RELEASE using freebsd-update. Everything went ok but I've got a problem when I do pkgdb -F /libexec/ld-elf.so.1: /usr/lib/libcrypt.so.4: unsupported file layout I might have goofed before I updated when moving files around to make space, so I need some advice on how to get rid of the error. I cannot find out what port I need to reinstall in order to get libcrypt healty again :-) Probably everything related to portupgrade/portinstall/ruby etc. -- Frederique My 7.1R-p4 system doesn't have a /usr/lib/libcrypt.so.4 it has a /lib/libcrypt.so.4 though so if you're moving stuff around -- and it's in the wrong directory, maybe that's why? In either case, libcrypt.so.4 is part of world, so you'd have to rebuild that piece if relocating the file itself doesn't fix it. And if you move libraries around, you need to update the linker helper file. ldconfig(8) Good luck. Hello again. I've some digging work and probaly there's something with compiling C programs that is not working as it should. I've one port that I was not able to upgrade so I tried to deinstall but it won't reinstall. I've included the /usr/ports/x11/kdelibs3/work/kdelibs-3.5.10/config.log Any hints are greatly appreciated :-) /Leslie -- snip - checking for gawk... gawk checking whether gmake sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for style of include used by gmake... GNU checking for gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. === Script configure failed unexpectedly. Please report the problem to k...@freebsd.org [maintainer] and attach the /usr/ports/x11/kdelibs3/work/kdelibs-3.5.10/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 - snip --- /usr/ports/x11/kdelibs3/work/kdelibs-3.5.10/config.log - snip --- This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by configure, which was generated by GNU Autoconf 2.61. Invocation command line was $ ./configure --disable-ltdl-install --disable-as-needed --enable-mt --x-libraries=/usr/local/lib --x-includes=/usr/local/include --with-libthai=yes --with-lua=no --with-ssl-dir=/usr --disable-debug --with-xinerama --with-qt-includes=/usr/local/include --with-qt-libraries=/usr/local/lib --with-extra-libs=/usr/local/lib --with-extra-includes=/usr/local/include --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=i386-portbld-freebsd7.2 ## - ## ## Platform. ## ## - ## hostname = blj01.no-ip.org uname -m = i386 uname -r = 7.2-RELEASE uname -s = FreeBSD uname -v = FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC /usr/bin/uname -p = i386 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /usr/lib PATH: /usr/games PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/X11R6/bin PATH: /root/bin ## --- ## ## Core tests. ## ##
Re: [kde-freebsd] Konqueror Unusable
On Wednesday 20 May 2009 23:28:50 Mel Flynn wrote: On Wednesday 20 May 2009 22:15:13 David Naylor wrote: On Wednesday 20 May 2009 21:37:58 Mel Flynn wrote: On Wednesday 20 May 2009 20:02:55 David Naylor wrote: This will fix the middle click problem. If it were easy to downgrade to Xserver-1.5 then that might confirm the hypothesis. I should resurrect my Xorg jail using Alexander Leidinger's patches, unfortunately ENOTIME at the moment. I made an important discover [for me at least] (just before sending in a bug report to KDE). The text boxes work fine! They just do not respond to left-mouse-click (or right-mouse-click if using left-handed mouse). I can get a cursor if I tab to the textbox. Once tabbed in the mouse works as expected (I'm able to relocate the cursor via clicking). Keyboard inputs also work as expected. Wow, confirmed. Totally weird and nothing in log either. Started via Konsole and once actually in the textarea using click on then tab: konqueror(42652) Sonnet::Loader::loadPlugin: Successfully loaded plugin: kspell_enchant.desktop konqueror(42652) Sonnet::Loader::loadPlugin: Successfully loaded plugin: kspell_aspell.desktop konqueror(42652) Sonnet::Loader::loadPlugin: Successfully loaded plugin: kspell_hspell.desktop Enchant dict for en_US 0x2fc60140 konqueror(42652) KHTMLView::focusNextPrevChild: focusNode.name: TEXTAREA konqueror(42652) Sonnet::Highlighter::slotRehighlight: Highlighter::slotRehighlight() This doesn't fire when clicking on the control. Since google doesn't show me anything useful, I'm enclined to think that it's FreeBSD specific :/ Some bad news (depending on your perceptive). I've recompiled KDE4 on my 7.1 system. I used startx-startkde4 (in chroot), then in konsole: kill twm; kwin. With both twm and kwin I didn't have any problems... This is looking to be FreeBSD -current specific. I also tried replacing kwin with twm in -current and the middle click problem goes away but the texbox one doesn't. The difference between the depslists (from -current to 7.1): +libgcrypt-1.4.4 +libgpg-error-1.7 -pth-2.0.7 signature.asc Description: This is a digitally signed message part. ___ 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] Konqueror Unusable
On Tuesday 19 May 2009 19:58:09 Dwayne MacKinnon wrote: On May 19, 2009 12:50:25 pm David Naylor wrote: Hi, I've installed KDE4 from ports over the weekend and strangely Konqueror doesn't work properly. First was that the mouse middle click didn't open the link in a new tab (or do anything). I solved that by disabling gestures for Konqueror. Second is I cannot type in text boxes within Konqueror, the location bar at the top works however after making a search at www.google.com the text box at the top doesn't respond (i.e. to refine the search). This problem also appears then visiting bugs.kde.org, I'm unable to type in the text boxes there. Any suggestions? Much appreciated David Hi David, I'm unable to reproduce this. I'm running KDE 4.2.3 on FreeBSD 7.1-RELEASE. Could you please send me your package list (pkg_info) [off list] or more specifically, which versions of Xorg do you have (pkg_info -r xorg-7'*'). Thanks signature.asc Description: This is a digitally signed message part. ___ 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] Konqueror Unusable
On Wednesday 20 May 2009 14:18:05 Mel Flynn wrote: On Tuesday 19 May 2009 18:50:25 David Naylor wrote: Second is I cannot type in text boxes within Konqueror, the location bar at the top works however after making a search at www.google.com the text box at the top doesn't respond (i.e. to refine the search). This problem also appears then visiting bugs.kde.org, I'm unable to type in the text boxes there. You're not alone, running -current +4.2.3, let's compare deplist for kdebase: % sed -ne 's/^...@pkgdep //p' /var/db/pkg/kdebase-4.2.3/+CONTENTS |sort *snip* - save some electrons... There are a few differences between our deplists: +pth-2.0.7 -raptop-1.4.18 +raptop-1.4.16_1 Otherwise the same (see attached for my output). I read a claim that it was Xserver-1.6 and Hotkey Gestures that is causing the problem, perhaps this has something to do with it? Also, if I disable Java and Javascript then Google's home page doesn't work either. I reenabled and selected debugging, Konqueror doesn't like Google's javascript. A bug also appeared on bugs.kde.org (what an irony). Could this be related to javascript? Regards, David OpenEXR-1.6.1_1 aspell-0.60.6_2 avahi-app-0.6.25_1 ca_root_nss-3.11.9_2 clucene-0.9.21 compositeproto-0.4 consolekit-0.3.0_8 curl-7.19.4 damageproto-1.1.0_2 db46-4.6.21.4 dbus-1.2.4.6 dbus-glib-0.80 dmidecode-2.10 dmxproto-2.2.2 dri2proto-2.0 enchant-1.4.2 exiv2-0.18,1 expat-2.0.1 fixesproto-4.0 fontcacheproto-0.1.2 fontconfig-2.6.0,1 fontsproto-2.0.2 freetype2-2.3.9_1 gamin-0.1.10_2 gdbm-1.8.3_3 gettext-0.17_1 gio-fam-backend-2.20.1 glib-2.20.1 gnome_subr-1.0 hal-0.5.11_23 hicolor-icon-theme-0.10_2 iceauth-1.0.2 ilmbase-1.0.1_1 inputproto-1.5.0 jasper-1.900.1_7 jpeg-6b_7 kbproto-1.0.3 kde4-shared-mime-info-1.0 kdehier4-1.0.3 kdelibs-4.2.3 lcms-1.18,1 libFS-1.0.1 libGL-7.4.1_1 libGLU-7.4.1_1 libICE-1.0.4_1,1 libSM-1.1.0_1,1 libX11-1.2.1,1 libXScrnSaver-1.1.3 libXTrap-1.0.0 libXau-1.0.4 libXaw-1.0.5_1,1 libXcomposite-0.4.0,1 libXcursor-1.1.9_1 libXdamage-1.1.1 libXdmcp-1.0.2_1 libXevie-1.0.2 libXext-1.0.5,1 libXfixes-4.0.3_1 libXfont-1.3.4,1 libXfontcache-1.0.4 libXft-2.1.13 libXi-1.2.1,1 libXinerama-1.0.3,1 libXmu-1.0.4,1 libXp-1.0.0,1 libXpm-3.5.7 libXrandr-1.3.0 libXrender-0.9.4_1 libXres-1.0.3_3 libXt-1.0.5_1 libXtst-1.0.3_1 libXv-1.0.4,1 libXvMC-1.0.4_1 libXxf86dga-1.0.2 libXxf86misc-1.0.1 libXxf86vm-1.0.2 libdaemon-0.12 libdmx-1.0.2_1 libdrm-2.4.9 libfontenc-1.0.4 libiconv-1.11_1 libidn-1.13 libmng-1.0.10 liboldX-1.0.1 libpci-2.2.8_1 libpthread-stubs-0.1 libungif-4.1.4_5 libvolume_id-0.81.1 libxcb-1.2_1 libxkbfile-1.0.5 libxkbui-1.0.2_1 libxml2-2.7.3 libxslt-1.1.24_2 mDNSResponder-108 pciids-20090224 pcre-7.9 perl-threaded-5.10.0_2 phonon-4.3.1_1 pixman-0.15.2 pkg-config-0.23_1 png-1.2.35 policykit-0.9_4 printproto-1.0.4 pth-2.0.7 python26-2.6.1_2 qimageblitz-0.0.4_2 qt4-assistant-4.4.3 qt4-clucene-4.4.3 qt4-corelib-4.4.3 qt4-dbus-4.4.3 qt4-designer-4.4.3 qt4-doc-4.4.3 qt4-gui-4.4.3_2 qt4-help-4.4.3 qt4-imageformats-4.4.3 qt4-makeqpf-4.4.3 qt4-network-4.4.3 qt4-opengl-4.4.3 qt4-qdbusviewer-4.4.3 qt4-qt3support-4.4.3 qt4-qtestlib-4.4.3 qt4-script-4.4.3 qt4-sql-4.4.3 qt4-sqlite-plugin-4.4.3 qt4-svg-4.4.3 qt4-webkit-4.4.3 qt4-xml-4.4.3 randrproto-1.3.0 raptor-1.4.16_1 recordproto-1.13.2 redland-1.0.7_1 renderproto-0.9.3 samba-libsmbclient-3.0.34_1 scrnsaverproto-1.1.0 shared-mime-info-0.60_1 soprano-2.2.3_1 sqlite3-3.6.13 strigi-0.6.4 tiff-3.8.2_3 trapproto-3.4.3 videoproto-2.2.2 xauth-1.0.3 xcb-proto-1.4 xextproto-7.0.5 xf86dgaproto-2.0.3 xf86miscproto-0.9.2 xf86vidmodeproto-2.2.2 xineramaproto-1.1.2 xorg-libraries-7.4 xproto-7.0.15 xtrans-1.2.3 signature.asc Description: This is a digitally signed message part. ___ 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] Konqueror Unusable
On Wednesday 20 May 2009 18:55:31 Mel Flynn wrote: On Wednesday 20 May 2009 18:14:51 David Naylor wrote: On Wednesday 20 May 2009 14:18:05 Mel Flynn wrote: On Tuesday 19 May 2009 18:50:25 David Naylor wrote: Second is I cannot type in text boxes within Konqueror, the location bar at the top works however after making a search at www.google.com the text box at the top doesn't respond (i.e. to refine the search). This problem also appears then visiting bugs.kde.org, I'm unable to type in the text boxes there. You're not alone, running -current +4.2.3, let's compare deplist for kdebase: % sed -ne 's/^...@pkgdep //p' /var/db/pkg/kdebase-4.2.3/+CONTENTS |sort *snip* - save some electrons... There are a few differences between our deplists: +pth-2.0.7 /me has gpgme with native threads. -raptop-1.4.18 +raptop-1.4.16_1 Saves me an update to see if it's working then. Actually its my system that has the lower version... I read a claim that it was Xserver-1.6 and Hotkey Gestures that is causing the problem, perhaps this has something to do with it? Dunno? Can I disable Hotkey Gestures somewhere? In the 4.2.2 4.2.3 update Xorg server was collateral damage, so it makes sense as it started since then. System Settings - Input Actions (Use the right hand pane, at the bottom). This will fix the middle click problem. If it were easy to downgrade to Xserver-1.5 then that might confirm the hypothesis. No other textboxes are affected for me, it's confined to konqueror and embedded versions of it (like ktorrent's search). Nothing in ~/.xsession- errors. I'll try compile Konqueror from KDE 4.2.0 and see if it has the problem there... signature.asc Description: This is a digitally signed message part. ___ 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] Konqueror Unusable
On Tuesday 19 May 2009 20:30:35 Kent Stewart wrote: On Tuesday 19 May 2009 09:50:25 am David Naylor wrote: Hi, I've installed KDE4 from ports over the weekend and strangely Konqueror doesn't work properly. First was that the mouse middle click didn't open the link in a new tab (or do anything). I solved that by disabling gestures for Konqueror. Second is I cannot type in text boxes within Konqueror, the location bar at the top works however after making a search at www.google.com the text box at the top doesn't respond (i.e. to refine the search). This problem also appears then visiting bugs.kde.org, I'm unable to type in the text boxes there. I had problems with text not appearing for 8-10 seconds. I usually had 2 or 3 konsole sessions on my desktop and one would be really sluggish and the other wouldn't. The big problem for me was after a few hours I couldn't select k-menu to logoff. This is not the case for me since some text boxes work, even in a different tab when this symptom appears. Any suggestions? I dropped back to kde-3 because I had to know if it was kde-4, x-windows, or my new hardware. After dropping back to kde-3 everything worked and has continued to work. With the exception of the kde-3 packages, which were built using another system that had problems with kde-4, the system was reinstalled using the packages built by the system while kde-4 was installed. FWIW, dbus and hald were left running after kde-3 was installed. Hopefully KDE 4.3 will do right by you. I know KDE 4 can reveal many bugs... Thanks for the reply signature.asc Description: This is a digitally signed message part. ___ 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 and Grub
On Monday 11 May 2009 18:44:41 David Johnson wrote: On Monday 11 May 2009 07:26:51 am David Naylor wrote: Also, since FreeBSD does support suspending [S3?] (and standby [S1?]) why are these options not shown and where can they be enabled. Taking a quick look at the sources, the shutdown dialog gets this info from Solid (the hardware manager) which in turn gets its info from HAL. So I would look at HAL to see why it's not as FreeBSD friendly as it should be. I had a look and it appears HAL should detect suspend states perfectly fine. My desktop doesn't support either so not suprising it isn't visible. I didn't find anything in kdelibs to suggest discrimination against FreeBSD. HAL and KDE do not support standby (S1) states. Can anyone confirm they have suspend options available in KDE4? On the grub topic, I could only find commented references to grub in kdelib (nothing in HAL) and the comments are not about reboot options. Looking further into grub it appears to have only limited support for specifying the OS for next reboot. This requires having the default saved line in menu.lst and (depending on your setup) savedefault [0-9] at the end of each boot option. One could then use grub-set-default to change the next boot target (please make sure grub-set-default is called at least once before rebooting, after installing grub otherwise grub fails to boot anything). This leads me to believe 'OS on next boot' options are a distro specific extra and can be achieved by alternative means. If anyone would like an example of how to do this just ask and I'll post an example. Regards signature.asc Description: This is a digitally signed message part. ___ 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 Commit] Qt 4.5 Build Fixes (with Qt33 installed)
On Sunday 19 April 2009 07:43:22 David Johnson wrote: On Monday 13 April 2009 06:48:02 pm David Johnson wrote: I'm still working in this area. It seems from your list that other ports besides qt5-gui are having this problem. Have you identified their differences from 4.4.3 that cause this? I've discovered that I can eliminate the qt3/qt4 conflict by adding the following line to the problem makefiles, before bsd.port.pre.mk: CONFIGURE_ARGS+=-I../../include/Qt -I../../include Assuming you are going to add this to bsd.qt.mk: Not all source files are compiled two directories away from ./include, this shouldn't be a problem in practise since all the problem files are two directories away. Unless gcc fails when -I points to an invalid directory? This puts the source dir's Qt include before anything else, so that a qt33 installed to /usr/local will not interfere. Assuming you are going to add this to bsd.qt.mk: This works for all include files (common between qt33 and qt4*) except qassistantclient.h that is under ./include/QtAssistant and not ./include/Qt, again this shouldn't be a problem in practise. So far I have made changes to qt4-gui, qt4-opengl and qt4-qvfb. I'm still going through all the ports though. If this fix is acceptable, I can commit tomorrow evening. The other port I had a problem with when compiling with qt33 is www/qt4-webkit (and I didn't have any problems with x11-toolkit/qt4-gui). This fix appears to be better and cleaner than mine. Look forward to your commits, David signature.asc Description: This is a digitally signed message part. ___ 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 Commit] Qt 4.5 Build Fixes (with Qt33 installed)
On Tuesday 14 April 2009 03:48:02 David Johnson wrote:
On Sunday 12 April 2009 11:57:20 pm David Naylor wrote:
devel/qt4-corelib:
- Remove port revision
- Remove hack to hard-code the features of qconfig.h. The hack now
appears to do more damage that good. Attached is the qconfig.h generated
by configure (as apposed to the files/qconfig.h.in that has been
removed). - P.S. Please add USE_ICONV when the fix is committed
I committed a fix for corelib yesterday (in the qt-4.5 branch). It does
essentially the same as yours.
I saw. I thought FreeBSD had a monotonic clock? (The only option left in the
qconfig.h.in file)
The fixes for build with qt33 are a result from -I{LOCALBASE} being
included way to early. How it gets there I do not know. It appears to
be included after the specific .pro file has been read and before some
extra .prf files are read (such as
mkspecs/features/unix/hide_symbols.prf). Any idea as to the root cause?
The only place I ran across problems was with QtGui. The core problem is
with the new QGTKStyle. I was able to fix this in a non-port build by
changing src/gui/Makefile. Alternatively, once could patch
src/gui/styles/styles.pri to totally disable QGTKStyle. (And make it a
separate port).
Currently QGTKStyle is disabled in area51. Is it even possible to make it a
separate port? It looks small enough that we can just include it with
qt4-gui?
I'm still working in this area. It seems from your list that other ports
besides qt5-gui are having this problem. Have you identified their
differences from 4.4.3 that cause this?
Yes, I had a look and found the problem. QMAKE_CFLAGS_X11 now gets included
into QMAKE_CXXFLAGS. This is a problem since QMAKE_CFLAGS_X11 gets add
QMAKE_CFLAGS_FONTCONFIG (from pkgconfig) that includes -I/usr/local/include.
The culprit. There does not appear to be a proper away around this (i.e. get
QMAKE_CFLAGS_X11 added to the end of QMAKE_CXXFLAGS *after* other includes
have been added).
See attached that should fix this. It forces Qt fallback config option
regarding fontconfig. It just removes the fontconfig cflags (which is
just -I/usr/local/include).
Currently qt4 (in area51) only supports installing the ports into the
same prefix as qmake4. This is since the install prefix is hard coded
into qmake4. I have found only one way to override this hard-code, that
is to recompile qmake4. configure does this by default so I intend to
restore this behaviour (when installing into a different PREFIX as to
that by the system qmake). This however will result in quite some growth
in the Makefiles so I propose to refractor the common code between the
Makefiles (such as the do-not-extract stuff). This would hopefully
simplify maintenance.
How big of a problem is this? Are there use cases where different PREFIXes
would be desirable? Couldn't these use cases take advantage of a qmake.conf
file instead?
I use port test for pkg-plist so it is a big problem for me, otherwise a
tinderbox could do that? Qt wouldn't be the first port that has limited
support for PREFIX. It works well enough if someone uses a single PREFIX for
all of Qt :-).
I tried adding the variables to .qmake.vars (which I think does the same as
qmake.conf) to no effect. I think it is just hard coded into qmake. (bug?
or just don't know how to make qmake work?).
I would still like to implement a common makefile to reduce duplicate makefile
code? It will make switching from copying the complete configure file to
applying the diff easier... and other areas as well... Thoughts?
p.s. My time is limited this week and next, but if I find some I'll look
over your other patches closer. Some of them look good at first glance.
Thanks, no problem. You could ignore the devel/qt4-qvfb, www/qt4-webkit and
x11/qt4-opengl patches since the attached patch now fixes it all :-).
Is there any area I could help out with?
Regards
Index: devel/qt4/files/configure
===
--- devel/qt4/files/configure (revision 4704)
+++ devel/qt4/files/configure (working copy)
@@ -4827,7 +4827,7 @@
# auto-detect FontConfig support
if [ $CFG_FONTCONFIG != no ]; then
-if [ -n $PKG_CONFIG ] $PKG_CONFIG --exists fontconfig 2/dev/null; then
+if false; then #[ -n $PKG_CONFIG ] $PKG_CONFIG --exists fontconfig 2/dev/null
QT_CFLAGS_FONTCONFIG=`$PKG_CONFIG --cflags fontconfig 2/dev/null`
QT_LIBS_FONTCONFIG=`$PKG_CONFIG --libs fontconfig 2/dev/null`
else
signature.asc
Description: This is a digitally signed message part.
___
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 Commit] Qt 4.5 Build Fixes (with Qt33 installed)
On Wednesday 15 April 2009 06:11:16 David Johnson wrote: On Tuesday 14 April 2009 08:34:54 am David Naylor wrote: Yes, I had a look and found the problem. QMAKE_CFLAGS_X11 now gets included into QMAKE_CXXFLAGS. This is a problem since QMAKE_CFLAGS_X11 gets add QMAKE_CFLAGS_FONTCONFIG (from pkgconfig) that includes -I/usr/local/include. The culprit. There does not appear to be a proper away around this (i.e. get QMAKE_CFLAGS_X11 added to the end of QMAKE_CXXFLAGS *after* other includes have been added). I wonder why it is not a problem for me? In any case, the patch turns off fontconfig support. Don't we need that for decent looking fonts? It shouldn't turn off fontconfig support, it should force the script to use the default values (i.e. not use pkgconfig). That was the intent. Anyways, to fix it make sure QMAKE_CFLAGS_FONTCONFIG is assigned with . Hopefully I can take a look this weekend at more of this. signature.asc Description: This is a digitally signed message part. ___ 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] [Request For Commit] Qt 4.5 Build Fixes (with Qt33 installed)
Hi,
Could someone please commit the attached patches. The pkg-plist's has not
been checked since Qt4.5 has very limited support for installing into a
custom PREFIX (more about that later). Below are the details for each patch
file (according to port):
databases/qt4-odbc-plugin:
- Add missing include to custom Makefile
devel/dbus-qt4:
- Mark MAKE_JOBS_UNSAFE [see below]
devel/qt4-corelib:
- Remove port revision
- Remove hack to hard-code the features of qconfig.h. The hack now appears
to do more damage that good. Attached is the qconfig.h generated by
configure (as apposed to the files/qconfig.h.in that has been removed).
- P.S. Please add USE_ICONV when the fix is committed
devel/qt4-linguist:
- Remove files/patch-0185-fix-format-strings.diff, API change, no longer
relevant.
- Re-role patch (with filename change):
files/patch-tools__linguist__linguist__trwindow.cpp =
files/patch-tools__linguist__linguist__mainwindow.cpp
devel/qt4-scripttools:
- Add new port, required by misc/qt4-qtdemo. Based on qt4-script. pkg-plist
needs to be generated, will be done once installing into custom PREFIX has
been implemented.
devel/qt4-qvfb:
- Fix build with qt33 installed (remove stray -I${LOCALBASE}) [see below]
misc/qt4-qtdemo:
- Add missing dependency
multimedia_qt4-phonon:
- Have the final Makefile generated before patching it
www/qt4-webkit:
- Fix build with qt33 installed (remove stray -I${LOCALBASE}) [see below]
x11/qt4-opengl:
- Fix build with qt33 installed (remove stray -I${LOCALBASE}) [see below]
All ports have been build with FORCE_MAKE_JOBS as set, so MAKE_JOBS_SAFE could
be set for all ports (done on a quad-core system), except for dbus-qt4.
The fixes for build with qt33 are a result from -I{LOCALBASE} being included
way to early. How it gets there I do not know. It appears to be included
after the specific .pro file has been read and before some extra .prf files
are read (such as mkspecs/features/unix/hide_symbols.prf). Any idea as to
the root cause?
Currently qt4 (in area51) only supports installing the ports into the same
prefix as qmake4. This is since the install prefix is hard coded into
qmake4. I have found only one way to override this hard-code, that is to
recompile qmake4. configure does this by default so I intend to restore this
behaviour (when installing into a different PREFIX as to that by the system
qmake). This however will result in quite some growth in the Makefiles so I
propose to refractor the common code between the Makefiles (such as the
do-not-extract stuff). This would hopefully simplify maintenance.
I propose to add the file devel/qt4/Makefile.common and have the other ports
(such as devel/qt4-corelib) include it. If anyone has any objections or
alternative suggestions please let me know.
Regards,
David
/* Everything */
/* Qt Edition */
#ifndef QT_EDITION
# define QT_EDITION QT_EDITION_OPENSOURCE
#endif
/* Machine byte-order */
#define Q_BIG_ENDIAN 4321
#define Q_LITTLE_ENDIAN 1234
#define QT_BUILD_KEY i386 usr/local/share/qt4/mkspecs/freebsd g++-4 full-config
#define QT_BUILD_KEY_COMPAT i386 FreeBSD g++-4 full-config
#ifdef QT_BOOTSTRAPPED
#define Q_BYTE_ORDER Q_LITTLE_ENDIAN
#else
#define Q_BYTE_ORDER Q_LITTLE_ENDIAN
#endif
/* Machine Architecture */
#ifndef QT_BOOTSTRAPPED
# define QT_ARCH_I386
#else
# define QT_ARCH_I386
#endif
/* Compile time features */
#define QT_LARGEFILE_SUPPORT 64
#define QT_POINTER_SIZE 4
#if defined(QT_BUILTIN_GIF_READER) defined(QT_NO_BUILTIN_GIF_READER)
# undef QT_BUILTIN_GIF_READER
#elif !defined(QT_BUILTIN_GIF_READER) !defined(QT_NO_BUILTIN_GIF_READER)
# define QT_BUILTIN_GIF_READER 1
#endif
#if defined(QT_NO_DBUS) defined(QT_DBUS)
# undef QT_NO_DBUS
#elif !defined(QT_NO_DBUS) !defined(QT_DBUS)
# define QT_NO_DBUS
#endif
#if defined(QT_NO_EXCEPTIONS) defined(QT_EXCEPTIONS)
# undef QT_NO_EXCEPTIONS
#elif !defined(QT_NO_EXCEPTIONS) !defined(QT_EXCEPTIONS)
# define QT_NO_EXCEPTIONS
#endif
#if defined(QT_NO_GSTREAMER) defined(QT_GSTREAMER)
# undef QT_NO_GSTREAMER
#elif !defined(QT_NO_GSTREAMER) !defined(QT_GSTREAMER)
# define QT_NO_GSTREAMER
#endif
#if defined(QT_NO_ICONV) defined(QT_ICONV)
# undef QT_NO_ICONV
#elif !defined(QT_NO_ICONV) !defined(QT_ICONV)
# define QT_NO_ICONV
#endif
#if defined(QT_NO_IMAGEFORMAT_JPEG) defined(QT_IMAGEFORMAT_JPEG)
# undef QT_NO_IMAGEFORMAT_JPEG
#elif !defined(QT_NO_IMAGEFORMAT_JPEG) !defined(QT_IMAGEFORMAT_JPEG)
# define QT_NO_IMAGEFORMAT_JPEG
#endif
#if defined(QT_NO_IMAGEFORMAT_MNG) defined(QT_IMAGEFORMAT_MNG)
# undef QT_NO_IMAGEFORMAT_MNG
#elif !defined(QT_NO_IMAGEFORMAT_MNG) !defined(QT_IMAGEFORMAT_MNG)
# define QT_NO_IMAGEFORMAT_MNG
#endif
#if defined(QT_NO_IMAGEFORMAT_TIFF) defined(QT_IMAGEFORMAT_TIFF)
# undef QT_NO_IMAGEFORMAT_TIFF
#elif !defined(QT_NO_IMAGEFORMAT_TIFF) !defined(QT_IMAGEFORMAT_TIFF)
# define QT_NO_IMAGEFORMAT_TIFF
#endif
#if defined(QT_NO_INOTIFY) defined(QT_INOTIFY)
# undef QT_NO_INOTIFY
[kde-freebsd] Qt 4.5 Port Progress
Hi, Some quick questions about Qt.4.5 and FreeBSD: - Is anyone actively working on porting Qt 4.5? - Who should I contact about getting patches for Qt 4.5 committed to area51? - Should the patches be posted on the mailing list [or just sent to the correct person(s)] - Is there a progress page for the Qt 4.5 Port (i.e. on wiki.freebsd)? Regards, David signature.asc Description: This is a digitally signed message part. ___ 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 4.5 and GNU iconv [SOLUTION]
On Tuesday 07 April 2009 07:25:16 David Johnson wrote:
I played around with this, rebuilding libiconv after gettext, but to no
effect. Oh well, it was worth a shot...
I've managed to get Qt 4.5 to behave well with libiconv. It was a bit of a
cheat though. There is also another solution.
SOLUTION 1:
Disable libiconv support altogether. This, I believe, is a viable solution
since Windows does not have iconv and we should be using whatever fallback it
does. This should result in no loss of functionality.
SOLUTION 2:
qt4-corelib is the only part that is affected by libiconv (under
src/corelib/codec/). It appears that the changes introduces since Qt4.4.3
are of an optimising nature and have some kind of state caching. This
caching is somehow breaking libiconv under FreeBSD.
Even with the new libiconv port from ports/131769 it still does not work.
The attached files restore the behaviour of the previous code. This probably
will result in a performance loss (but remain par with Qt4.4.3). Since the
changes are isolated to those two files and the API has not changed (for
QTextCodec) this should not negatively affect anything. I've tested this
with qtdemo and everything works fine.
Are either of these solutions (and if so which one) satisfactory?
Regards,
David
P.S. It will result in a smaller 'patch' if the files are copied across
verbatim.
--- src/corelib/codecs/qiconvcodec.cpp 2009-04-07 18:47:19.0 +
+++ src/corelib/codecs/qiconvcodec.cpp 2009-04-07 18:46:27.0 +
@@ -1,49 +1,43 @@
/
**
-** Copyright (C) 2009 Nokia Corporation and/or its subsidiary(-ies).
+** Copyright (C) 2008 Nokia Corporation and/or its subsidiary(-ies).
** Contact: Qt Software Information (qt-i...@nokia.com)
**
** This file is part of the QtCore module of the Qt Toolkit.
**
-** $QT_BEGIN_LICENSE:LGPL$
** Commercial Usage
** Licensees holding valid Qt Commercial licenses may use this file in
** accordance with the Qt Commercial License Agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and Nokia.
**
-** GNU Lesser General Public License Usage
-** Alternatively, this file may be used under the terms of the GNU Lesser
-** General Public License version 2.1 as published by the Free Software
-** Foundation and appearing in the file LICENSE.LGPL included in the
-** packaging of this file. Please review the following information to
-** ensure the GNU Lesser General Public License version 2.1 requirements
-** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
-**
-** In addition, as a special exception, Nokia gives you certain
-** additional rights. These rights are described in the Nokia Qt LGPL
-** Exception version 1.0, included in the file LGPL_EXCEPTION.txt in this
-** package.
**
** GNU General Public License Usage
** Alternatively, this file may be used under the terms of the GNU
-** General Public License version 3.0 as published by the Free Software
-** Foundation and appearing in the file LICENSE.GPL included in the
-** packaging of this file. Please review the following information to
-** ensure the GNU General Public License version 3.0 requirements will be
-** met: http://www.gnu.org/copyleft/gpl.html.
+** General Public License versions 2.0 or 3.0 as published by the Free
+** Software Foundation and appearing in the file LICENSE.GPL included in
+** the packaging of this file. Please review the following information
+** to ensure GNU General Public Licensing requirements will be met:
+** http://www.fsf.org/licensing/licenses/info/GPLv2.html and
+** http://www.gnu.org/copyleft/gpl.html. In addition, as a special
+** exception, Nokia gives you certain additional rights. These rights
+** are described in the Nokia Qt GPL Exception version 1.3, included in
+** the file GPL_EXCEPTION.txt in this package.
+**
+** Qt for Windows(R) Licensees
+** As a special exception, Nokia, as the sole copyright holder for Qt
+** Designer, grants users of the Qt/Eclipse Integration plug-in the
+** right for the Qt/Eclipse Integration to link to functionality
+** provided by Qt Designer and its related libraries.
**
** If you are unsure which license is appropriate for your use, please
** contact the sales department at qt-sa...@nokia.com.
-** $QT_END_LICENSE$
**
/
#include qiconvcodec_p.h
-#include qtextcodec_p.h
#include qlibrary.h
#include qdebug.h
-#include qthreadstorage.h
#include errno.h
#include locale.h
@@ -73,7 +67,7 @@
# define UTF16 UTF-16
#endif
-#if defined(Q_OS_MAC)
+#ifdef Q_OS_MAC
#ifndef GNU_LIBICONV
#define GNU_LIBICONV
#endif
@@ -88,8 +82,6 @@
QT_BEGIN_NAMESPACE
-extern bool qt_locale_initialized;
-
QIconvCodec::QIconvCodec()
: utf16Codec(0)
{
@@ -101,20 +93,20 @@
Re: [kde-freebsd] Qt 4.5 and GNU iconv
On Monday 06 April 2009 10:06:11 Adriaan de Groot wrote: On Thursday 02 April 2009 10:46:24 pm David Naylor wrote: I've been trying to get Qt4.5 to behave properly with libiconv and it just doesn't. My best understanding is that, under linux, glibc provides all the iconv functionality and that, somehow, libiconv and glibc differ in their implementation and thus it breaks Qt (or Qt handles them differently). At least in Qt 4.4 -- the last I studied extensively, as someone else has done the Solaris 4.5 port this week -- it would go looking for GNU iconv or other iconv and the difference is hidden in QTextCodec. If there's iconv, an additional .so is produced and codecs behave as plugins; otherwise a number of codecs are compiled in to QtCore. This is about what I have found out from my research. I see little difference in the treatment between glibc and gnu iconv in QIconvCodec though... From what I can see Qt 4.4 (in FreeBSD ports) does use gnu iconv. So up until recently it did work. You don't say what the nature of behave is though -- does it not compile? Not run? With Qt 4.5 (with gnu iconv) everything does compile fine except instead of rendering text everything is in square. i.e. instead of showing text a square is rendered (the same thing kwrite does when the font doesn't support the given glyph?, except for all texts). Sorry but I didn't take a screenshot of it but can do should you require one :-) Do you have Qt 4.5 working with gnu iconv (aka libiconv) under solaris? signature.asc Description: This is a digitally signed message part. ___ 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 4.5 and GNU iconv
On Friday 03 April 2009 18:08:06 David Johnson wrote: On Thursday 02 April 2009 01:46:24 pm David Naylor wrote: I configure Qt with --no-iconv for exactly this reason. Is there any functionality lost? Do you see *any* square blocks after doing this? I'm not seeing any squares. But I don't have a lot of documents in non-latin1 codecs. I had a closer look and it appears that Qt does distinguish between glibc and GNU libiconv. I didn't see anywhere it treats them differently (but didn't look either). What I did see is that Qt has a fall back for systems that don't have iconv (such as Windows, and since it doesn't work for us, FreeBSD). This should mean, functionality wise, there will be no difference with and without libiconv. What is the course of action from here? Complain to Qt Software, hope someone sorts it out or ignore the problem? Oh and how does one file a bug with Qt Software? I've almost finished the build from area51/qt-4.5 and will post the diff required to get it to work :-). signature.asc Description: This is a digitally signed message part. ___ 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 4.5 and GNU iconv
On Friday 03 April 2009 20:32:30 David Johnson wrote: On Friday 03 April 2009 11:02:20 am David Naylor wrote: What is the course of action from here? Complain to Qt Software, hope someone sorts it out or ignore the problem? Oh and how does one file a bug with Qt Software? A new bug reporting system is being setup, as Qt transitions to a more community oriented project. Currently you can report bugs at http://www.qtsoftware.com/bugreport-form and them track them at http://qtsoftware.com/developer/task-tracker. But mention FreeBSD only obliquely. It is not an officially supported platform, and the Nokia policy is to reject all FreeBSD bugs that do not include a patch. Seriously. So write the bug to sound generic. They will accept our patches (if they don't break other platforms), but they won't fix any FreeBSD-only bugs. I think we could get away with claiming qt doesn't work with libiconv. Since I cannot find a single Linux distribution that doesn't use glibc (and does support qt4.5) I think it could fly? In any case I would like to try isolate the problem but I cannot find any regression tests. Surely Qt has some sort of regression testing. signature.asc Description: This is a digitally signed message part. ___ 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.5 Build Fix [on area51]
Hi,
Please see attached for the diff required for area51/qt-4.5 to compile on my
system. devel/qt4 with SQL plugins compiles cleanly.
I'll check the integrity of the programs tomorrow.
Regards,
David
Index: databases/qt4-odbc-plugin/files/Makefile.bsd
===
--- databases/qt4-odbc-plugin/files/Makefile.bsd (revision 4703)
+++ databases/qt4-odbc-plugin/files/Makefile.bsd (working copy)
@@ -4,6 +4,7 @@
CXXFLAGS+= -I${DRIVER} \
-I${PREFIX}/include/qt4 \
-I${PREFIX}/include/qt4/Qt \
+ -I${PREFIX}/include/qt4/QtCore \
-I${LOCALBASE}/include \
${PTHREAD_CFLAGS} -DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_FROM_ASCII \
-DQT_PLUGIN -DQT_SQL_LIB -DQT_CORE_LIB -D_LARGEFILE64_SOURCE \
Index: devel/qt4-corelib/files/qconfig.h.in
===
--- devel/qt4-corelib/files/qconfig.h.in (revision 4703)
+++ devel/qt4-corelib/files/qconfig.h.in (working copy)
@@ -1,42 +0,0 @@
-#if defined(QT_NO_CLOCK_MONOTONIC) defined(QT_CLOCK_MONOTONIC)
-# undef QT_NO_CLOCK_MONOTONIC
-#elif !defined(QT_NO_CLOCK_MONOTONIC) !defined(QT_CLOCK_MONOTONIC)
-# define QT_NO_CLOCK_MONOTONIC
-#endif
-
-#if defined(QT_NO_EXCEPTIONS) defined(QT_EXCEPTIONS)
-# undef QT_NO_EXCEPTIONS
-#elif !defined(QT_NO_EXCEPTIONS) !defined(QT_EXCEPTIONS)
-# define QT_NO_EXCEPTIONS
-#endif
-
-#if defined(QT_NO_INOTIFY) defined(QT_INOTIFY)
-# undef QT_NO_INOTIFY
-#elif !defined(QT_NO_INOTIFY) !defined(QT_INOTIFY)
-# define QT_NO_INOTIFY
-#endif
-
-#if defined(QT_NO_MREMAP) defined(QT_MREMAP)
-# undef QT_NO_MREMAP
-#elif !defined(QT_NO_MREMAP) !defined(QT_MREMAP)
-# define QT_NO_MREMAP
-#endif
-
-#if defined(QT_NO_NAS) defined(QT_NAS)
-# undef QT_NO_NAS
-#elif !defined(QT_NO_NAS) !defined(QT_NAS)
-# define QT_NO_NAS
-#endif
-
-#if defined(QT_NO_SXE) defined(QT_SXE)
-# undef QT_NO_SXE
-#elif !defined(QT_NO_SXE) !defined(QT_SXE)
-# define QT_NO_SXE
-#endif
-
-#if defined(QT_USE_MATH_H_FLOATS) defined(QT_NO_USE_MATH_H_FLOATS)
-# undef QT_USE_MATH_H_FLOATS
-#elif !defined(QT_USE_MATH_H_FLOATS) !defined(QT_NO_USE_MATH_H_FLOATS)
-# define QT_USE_MATH_H_FLOATS
-#endif
-
Index: devel/qt4-corelib/Makefile
===
--- devel/qt4-corelib/Makefile (revision 4703)
+++ devel/qt4-corelib/Makefile (working copy)
@@ -62,10 +62,6 @@
-E -e 's|(.*location=).*moc|\1${PREFIX}/bin/moc-qt4|g' \
-E -e 's|(.*location=).*uic|\1${PREFIX}/bin/uic-qt4|g' \
${WRKSRC}/../../lib/pkgconfig/QtCore.pc
- #hack to hard-code the feature part of qconfig.h
- ${HEAD} -n 27 ${WRKSRC}/global/qconfig.h ${WRKDIR}/qconfig.tmp
- ${CHMOD} 644 ${WRKSRC}/global/qconfig.h
- ${CAT} ${WRKDIR}/qconfig.tmp ${FILESDIR}/qconfig.h.in ${WRKSRC}/global/qconfig.h
.if ${OSVERSION} = 700042
${ECHO_CMD} #define QT_VISIBILITY_AVAILABLE ${WRKSRC}/global/qconfig.h
.endif
Index: devel/qt4-linguist/files/patch-0185-fix-format-strings.diff
===
--- devel/qt4-linguist/files/patch-0185-fix-format-strings.diff (revision 4703)
+++ devel/qt4-linguist/files/patch-0185-fix-format-strings.diff (working copy)
@@ -1,16 +0,0 @@
tools/linguist/shared/profileevaluator.h.orig 2008-04-28 09:11:21.0 -0400
-+++ tools/linguist/shared/profileevaluator.h 2008-05-09 10:50:40.0 -0400
-@@ -112,7 +112,12 @@
- private:
- QStringList expandPattern(const QString pattern);
- void logMessage(const QString msg, MessageType mt = MT_DebugLevel2);
--void logMessage(MessageType mt, const char *msg, ...);
-+void logMessage(MessageType mt, const char *msg, ...)
-+#if defined(Q_CC_GNU) !defined(__INSURE__)
-+__attribute__ ((format (printf, 3, 4)))
-+#endif
-+;
-+
- QStringList expandVariableReferences(const QString value);
- QStringList evaluateExpandFunction(const QByteArray func, const QString arguments);
-
Index: devel/qt4-linguist/files/patch-tools__linguist__linguist__mainwindow.cpp
===
--- devel/qt4-linguist/files/patch-tools__linguist__linguist__mainwindow.cpp (revision 0)
+++ devel/qt4-linguist/files/patch-tools__linguist__linguist__mainwindow.cpp (revision 0)
@@ -0,0 +1,11 @@
+--- tools/linguist/linguist/mainwindow.cpp~ 2009-04-02 12:17:18.0 +0200
tools/linguist/linguist/mainwindow.cpp 2009-04-02 12:17:36.0 +0200
+@@ -1314,7 +1314,7 @@
+ if (m_assistantProcess-state() != QProcess::Running) {
+ QString app = QLibraryInfo::location(QLibraryInfo::BinariesPath) + QDir::separator();
+ #if !defined(Q_OS_MAC)
+-app += QLatin1String(assistant);
++app += QLatin1String(assistant-qt4);
+ #else
+ app += QLatin1String(Assistant.app/Contents/MacOS/Assistant);
+ #endif
Index: devel/qt4-linguist/files/patch-tools__linguist__linguist__trwindow.cpp
===
---
[kde-freebsd] Qt 4.5 and GNU iconv
Hi, I've been trying to get Qt4.5 to behave properly with libiconv and it just doesn't. My best understanding is that, under linux, glibc provides all the iconv functionality and that, somehow, libiconv and glibc differ in their implementation and thus it breaks Qt (or Qt handles them differently). I cannot find anyone who has tried to compile Qt without glibc under linux (or if Gentoo has managed to get Qt working under their version of FreeBSD). I don't know if, or by how much, libiconv and glibc differ, perhaps converters/iconv would work better than libiconv in replacing glibc? Does anyone know why Qt is failing to behave with libiconv? Regards, David P.S. I updated libiconv to 1.13 (after compiling Qt) and still same issue signature.asc Description: This is a digitally signed message part. ___ 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 4.5 and GNU iconv
On Thursday 02 April 2009 21:10:04 David Johnson wrote: On Thursday 02 April 2009 07:00:38 am David Naylor wrote: Hi, I've been trying to get Qt4.5 to behave properly with libiconv and it just doesn't. My best understanding is that, under linux, glibc provides all the iconv functionality and that, somehow, libiconv and glibc differ in their implementation and thus it breaks Qt (or Qt handles them differently). So which one is implemented incorrectly, libiconv or glibc? If Qt assumes glibc, which almost by definition means Linux only, then a bug should be filed with Nokia to turn off iconv support for all non-Linux systems. I agree, any volunteers to file the bug? (Or get them to support libiconv) I configure Qt with --no-iconv for exactly this reason. Is there any functionality lost? Do you see *any* square blocks after doing this? I cannot find anyone who has tried to compile Qt without glibc under linux (or if Gentoo has managed to get Qt working under their version of FreeBSD). I don't know if, or by how much, libiconv and glibc differ, perhaps converters/iconv would work better than libiconv in replacing glibc? Does anyone know why Qt is failing to behave with libiconv? Dunno. I did spend some time looking at the source code, but didn't find anything noteworthy. Do we need iconv support? It seems that Qt is using it as a source of codecs rather than using its own. Are the Qt's supplied codecs sufficient that we don't need iconv? I read somewhere that Qt switched over to using iconv somewhere around 4.3. Do they have a fallback (and what do they do under OSX and Windows). Perhaps we should corner someone who does have the answers for us... Other than PCH not working (couldn't find out why but not critical) Qt 4.5 compiled fine for me. I'll try again tomorrow with a stock area51/qt-4.5. I had one problem with qt4-linguest, patches not working properly, but that I can manage :-). Once KDE 4.2.2 hits ports I'll see how that goes with Qt 4.5. signature.asc Description: This is a digitally signed message part. ___ 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.2.0 and older soprano aren't compatible
On Sunday 01 March 2009 11:30:32 Yuri wrote: I have latest kde-4.2.0 and it doesn't start properly, I get errors like these: This thread http://forum.kde.org/nepomuk-on-kde-4-2-rc-t-26334.html suggests that it's very likely that updating soprano helps. Currently ports have soprano-2.1.67 and the latest is soprano-2.2.2. The current ports version was release for KDE 4.2.0 and does work on my machine. If you want to try the latest soprano then please have a look at http://www.freebsd.org/cgi/query-pr.cgi?pr=132221 and if you have any problems with this port I'll be happy to help. Good luck signature.asc Description: This is a digitally signed message part. ___ 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] Call for Testing KDE 4.2 for FreeBSD
On Tuesday 03 February 2009 15:05:19 Max Brazhnikov wrote:
On Tue, 3 Feb 2009 08:31:10 +0200, David Naylor wrote:
On Monday 02 February 2009 12:01:10 David Naylor wrote:
Just finished compiling on FreeBSD 7.1 and have found the following
problems: 1. The fonts are not being anti-aliased? (Using default fonts
and Use anti-aliasing: Enabled {with sub-pixel rendering [RGB]}).
man fonts-conf? Never had problems with fonts, can't help here :(
I suspect this has something to do with nvidia driver. If one changes the
fonts to bitstream then anti-aliasing does work (but not with the default
fonts).
2. Network Settings doesn't detect anything to do with FreeBSD (it
probably still needs to be told about FreeBSD).
This part surely requires someone who can add support for FreeBSD.
Btw, k...@freebsd team are seeking for developers who would like to improve
KDE4 support for FreeBSD.
Should I file a PR for this, considering there probably isn't enough man-power
to actually resolve it?
3. ksudo does not install?
${KDE$_PREFIX}/lib/kde4/libexec/kdesu
Ask kde devs why kdesu is there.
Please ignore. It appears ksudo or kdesudo is a Kubuntu specific program (why
haven't they pushed the changes upstream?)
4. Samba config module doesn't find smb.conf by default. It should look
in multiple places?
This could be fixed easily I believe.
One the correct place in the code is found, yes it is. See attached. Patch
does compile cleanly and samba config module does not find smb.conf.
Makefile should probably be extended to change the lookup patch if
${LOCALBASE} isn't /usr/local? If so just
# sed -e s|/usr/local/etc/smb.conf|${LOCALBASE}/etc/smb.conf|'
$WRKSRC/kio/kio/ksambashare.cpp
I have also filed a PR (bug #183006) with an improved patch.
5. When I was changing desktop effects X froze. It was a once off
thing...
If it reappears I will file a PR.
I'll ping Alex about the status of mysql_embedded. Meantime you can try
ports/128757 for mysql_embedded and ports/130634 for amarok port.
I already have :-). I had a problem with downloading the patch... But once
that was done amarok2 installed fine :-)
The only app now that is really missing is k3b. Grrr... :-(
Regards,
David
--- ../kio/kio/ksambashare.cpp 2009-02-03 15:24:57.0 +0200
+++ ../kio/kio/ksambashare.cpp 2009-02-03 15:23:35.0 +0200
@@ -83,6 +83,9 @@
if ( QFile::exists(/etc/smb.conf) )
smbConf = /etc/smb.conf;
else
+ if ( QFile::exists(/usr/local/etc/smb.conf) )
+smbConf = /usr/local/etc/smb.conf;
+ else
if ( QFile::exists(/usr/local/samba/lib/smb.conf) )
smbConf = /usr/local/samba/lib/smb.conf;
else
signature.asc
Description: This is a digitally signed message part.
___
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] PulseAudio and KDEBase-Runtime
On Tuesday 03 February 2009 23:28:29 Max Brazhnikov wrote: On Tue, 3 Feb 2009 22:34:53 +0200, David Naylor wrote: Hi, I've found a rather nasty, reproducible, bug. When kdebase-runtime is compiled with pulseaudio support then KDE fails to login on the first attempt. X/KDE appears to freeze, after a Ctrl-Alt-Backspace then logins work. Do you have configured pulseaudio daemon? No, I didn't do anything besides setting the options on kdebase-runtime. This may be relevent: I am running Desktop Effects on a nvidia driver? If anyone else can confirm this bug I suggest pulseaudio gets removed as an option. (Oh, is this FreeBSD specific or a general problem) Option is off by default. Non-pulseaudio users are not affected. True, very true. ;-) signature.asc Description: This is a digitally signed message part. ___ 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] Call for Testing KDE 4.2 for FreeBSD
On Sunday 01 February 2009 23:02:28 Martin Wilke wrote: Howdy Guys, The KDE FreeBSD team is happy to announce the first public Call for Testing for KDE 4.2. Over the past weeks we have focused on the complex and very time consuming task to get KDE 4.2 running. Please read UPDATING-area51 before you start your update. To get KDE 4.2: try svn co https://kf.athame.co.uk/kde-freebsd/trunk/area51/ /path/to/area51 More info here: https://kf.athame.co.uk/access.php - Martin (on behalf of the KDE FreeBSD team) Hi, I'll get started on testing today. I however have this strange desire to use USB2 (the new USB stack introduced to FreeBSD-Current). Is KDE4 happy with USB2 (or to be more precise, is hald happy with USB2 yet)? Is there anything special required to compile KDE4 (and all other ports) to support USB2? I assume installing with KERNCONF=USB2 is a requirement :-) Thanks for the great work, much appreciated. Regards, David signature.asc Description: This is a digitally signed message part. ___ 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] Call for Testing KDE 4.2 for FreeBSD
On Monday 02 February 2009 12:01:10 David Naylor wrote:
On Sunday 01 February 2009 23:02:28 Martin Wilke wrote:
Howdy Guys,
The KDE FreeBSD team is happy to announce the first public
Call for Testing for KDE 4.2. Over the past weeks we have
focused on the complex and very time consuming task to get
KDE 4.2 running.
Please read UPDATING-area51 before you start your update.
To get KDE 4.2:
try
svn co https://kf.athame.co.uk/kde-freebsd/trunk/area51/
/path/to/area51
More info here:
https://kf.athame.co.uk/access.php
- Martin (on behalf of the KDE FreeBSD team)
Hi,
I'll get started on testing today. I however have this strange desire to
use USB2 (the new USB stack introduced to FreeBSD-Current).
Just finished compiling on FreeBSD 7.1 and have found the following problems:
1. The fonts are not being anti-aliased? (Using default fonts and Use
anti-aliasing: Enabled {with sub-pixel rendering [RGB]}).
2. Network Settings doesn't detect anything to do with FreeBSD (it probably
still needs to be told about FreeBSD).
3. ksudo does not install?
4. Samba config module doesn't find smb.conf by default. It should look in
multiple places?
5. When I was changing desktop effects X froze. It was a once off thing...
Items 1,2, 4, (5) probably qualify for a PR, can anyone confirm these?
Item 3 probably has something to do with our ports. I really prefer to use
(k)sudo (since ksu doesn't like root without a password). Item 4 should be
fixed with a patch (until upstream comes with a proper solution).
If you wait a few hours I'll see what I can do about providing patches for
items 3, 4.
Is KDE4 happy with USB2 (or to be more precise, is hald happy with USB2
yet)?
I'll try compile hald with USB2. If that doesn't work (i.e. starts taking
100% CPU on a core) then I will not persue the issue. I'm not sure ports has
been converted to handle the base system's libusb20 in -current?
Oh and I am still having problems with HTTPS and proxy. I am going to try put
up a Squid proxy and see if Squid behaves better then WinGate. And I am
hoping Qt 4.5 will fix this proxy/socks problem (if it will hurry up and get
released :-)).
Everything else is looking good :-) and working on the FreeBSD side.
Thanks
David
P.S. Any hope in getting Amarok 2 into ports with KDE 4.2. Last I saw it was
pending on a PR to fix mysql_embedded?
signature.asc
Description: This is a digitally signed message part.
___
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 LiveCD
Hi, Is anyone interested in producing a KDE Live CD? I have been tinkering with some scripts and have produced a CD image that includes the full FreeBSD base system (installworld, installkernel), xorg-7.3, kdebase*-4.1.85 and kdeartwork-4.1.85. I had to strip the debugging info from /usr/local/bin and /usr/local/lib however I am sure there are many more tweaks one can do (remove built in .ko, strip further info from bin/libs, remove unneeded graphics (especially icons), compile with CFLAGS=-Os). If anyone is interested in such a production (there is also a Live USB version) please let me know. Regards, David signature.asc Description: This is a digitally signed message part. ___ 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.1.96 and area51?
Hi, Is KDE 4.1.96 ready in area51 and if so are you looking for any testers? Regards, David signature.asc Description: This is a digitally signed message part. ___ 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] [CFT] KDE 4.2 BETA 2 testers wanted
On Wednesday 07 January 2009 18:40:39 you wrote: On Wed, Jan 07, 2009 at 06:10:43PM +0200, David Naylor wrote: On Wednesday 07 January 2009 00:06:42 you wrote: We are happy to announce the first public Call for Testing with KDE 4.2. The past weeks we focused on the complex and very time consuming task to get the KDE4.2 BETA2 ports into a much better shape so we can now go on to the next step: much wider public testing. The experimental KDE ports are currently pulled from KDE 4.2 BETA 2 (4.1.85). Some of you may believe beta testing is not worth it, but we want to get KDE 4.2 better then 4.1. At the moment we would actually benefit from wider testing the well prepared KDE 4.2 BETA 2 FreeBSD builds. We would have much more opportunity and time to identify and eventually correct FreeBSD specific problems with those. We added the file UPDATING-area51. _PLEASE_ read this before you start your update. To get KDE 4.2: try svn co https://kf.athame.co.uk/kde-freebsd/tags/kde-4.1.85/ /path/to/area51 More infos here: https://kf.athame.co.uk/access.php I like to say Thanks to all Helpers and Submitters on the kde-freebsd@ mailinglist. That's all for the moment. Happy Testing! - Martin (on behalf of the FreeBSD KDE team) PS: Don't forget to read the UPDATING-area51 :P Hi, I've notices 4.1.87 has been released. I assume this is an 'unofficial' release and area51 will be leap-frogging to RC1? (And thus we should not wait for 4.1.87 to be tagged and test 4.1.85?). Onto something more pressing: I see there is not the equivalent KDE4 version of kdeaddons! Is there a particular story regarding this? I'll start downloading the source files tonight and inform you how it goes. Thanks for the great work, David RC1 is 4.1.97 which come out in the next days. - Martin Hi, I had a single problem in downloading the source files. It appears kde4-l10n-en_GB is not happy (and I assume all the other kde4-l10n-*): - distinfo was incorrect with version 4.1.3 - the MASTER_SITES didn't work: unable to fetch file I assume the first point is related to the second and I am hoping the second is related to this being a beta release? Anywayz... There were no problems in compiling KDE4 (and konq-plugins) with python26 and db46 as defaults. The following were are things that didn't work: - strigi doesn't start: (Failed to contact Strigi indexer (No such method currentF..gi at object path '/nepomukstrigiservice' (signature '')) - displayed in 'Desktop Search - System Settings' - Power Management (following doesn't work - that should): + Scaling: not supported, + CPU Policies: no methods found, + suspend methods: no methods found - Samba doesn't know about the default location for smb.conf - There is a marked slowdown in rendering widgets on screen (with the same compositing options as 4.1). Best example is System Settings - Desktop - Desktop Effects - All Effects - HTTPS proxy doesn't work (have no idea why) - SOCKS proxy doesn't work (does not even have a config option) - krunner crashed once (no bt :-() Unfortunately the proxy issues are very critical for me. Otherwise, everything works and I can see a marked polishing of KDE4. Great work :-) David signature.asc Description: This is a digitally signed message part. ___ 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] KDE4 and nspluginwrapper
Hi, I have KDE 4.1.3 installed from area51 (tag kde_4_1?) and I am unable to get flash7/9 to work under Konqueror. Instead of seeing an area where the flash should be displayed it is void (does not even display a holder for the flash). I can confirm that flash does work under firefox3 and Konqueror 3.5.10. This is the first time under KDE4 that I am trying this so I do not know if it is a regression. Is this a genuine problem or have I missed something in setting up Konqueror. Konqueror does (under about:plugins and plugins under settings) show that it has found flash. Also, an aside, should KDE 4.1.3 have https proxy and socks support? Regards, David signature.asc Description: This is a digitally signed message part. ___ 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] [CFT] KDE 4.1.3 Ready for Testing
On Saturday 08 November 2008 23:03:12 Martin Wilke wrote: Hiho, A few days ago Max made KDE-4.1.3 ready for FreeBSD, We can't commit KDE-4.1.3 to the Ports tree because we are still on the ports slush :(. But I'd like to invite you to test KDE-4.1.3 from area51. Of course feedback is welcome. Warning: PLEASE use: svn co https://kf.athame.co.uk/kde-freebsd/tags/kde_4_1 to get KDE 4.1.3 In the next days we start our work with Qt 4.5 and KDE 4.2. The official KDE 4.1.3 release notes can be found here. http://kde.org/announcements/announce-4.1.3.php Thanks, - Martin Hi, Thanks for all the hard work. I've updated the ports and everything went well. No obvious regressions with compiling or during runtime (even with running nvidia :-) I did encounter two problems (both, I think, are related to using tmpfs): - gpgme: failed to build - ocaml: failed to install (properly?) Anyway I think these problems are specific to my system (with tmpfs...). As a note about these 'FAQ'. I find that running the following script solves the problem with patches 'showing' through the unionfs: cd $AREA51 for i in `find . -type d -depth 2` do rm -rf /usr/ports/$i done mount -t unionfs $AREA51 /usr/ports Of course this mitigates the reason for using unionfs... An alternative would be to delete all files that 'show' through unionfs once it has been mounted (whiteout I believe it is called). The following script might work but I have never tried it: cd $AREA51 area51_ports=`find . -type d -depth 2` mount -t unionfs $AREA51 /usr/ports cd /usr/ports for i in $area51_ports do for j in `find -d $i` do if [ ! -e $AREA51/$j ] then rm -rf $AREA51/$j fi done done But then I have no idea on how to undelete the files (if, for example, another file is created post- with the same name). Thanks again for the good work. David P.S. Anyone getting kde4 working with https and proxying (no auth)? GMail is proving illusive for me :- signature.asc Description: This is a digitally signed message part. ___ 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] Amarok 2 Beta 3
Hi all,
I've downloaded the amarok 2 beta 3 (aka 1.94) source codes and compiled the
program. It compiles fine (with the same problems as before, with gpod and
such not being recognised, and of-course the mysql-embedded). In addition,
libmtp needs to be updated (it compiles with 0.3.3 but I suspect any 0.3
release will work?).
I however discovered an interesting problem. When qt-3 is installed (and
KDE4_PREFIX=${LOCALDIR}???) then the build fails, because qfileinfo.h is
included by amarok? Rather strange since it only happens around ~60%
completion.
Amarok runs however I have experienced a few crashes. I am not sure if they
are specific to FreeBSD or a general problem with Amarok. I will investigate
further (after updating to KDE 4.1.3).
Regards,
David
P.S. Is there an easy way to handle pkg-plist (or to check it?).
signature.asc
Description: This is a digitally signed message part.
___
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] KDE4 and the Default Fonts
Hi,
I have KDE 4.1.1 installed with the default fonts however Sans Serif does not
appear to be rendering properly. It is not anti-aliasing. The strange thing
is that Luki Sans and the Bitstream * Family do anti-alias in addition KDE
3.5.10 is rendering Sans Serif with anti-aliasing.
Both systems are running updated ports from 7_1_0_RELEASE (with KDE4 running
FreeBSD 7.1-Prerelease and KDE3 running FreeBSD 8-Current) and anti-aliasing
enabled with a hinting style of slight [is there a way to enable
anti-aliasing in Xorg.conf?].
Also I have looked but cannot find the Sans Serif TTF file (it does not appear
to be under ${LOCALBASE}/lib/X11/fonts), if someone could please point me in
the right direction.
Is this a problem with KDE4 or is there something wrong with my setup?
Thanks for your assistance,
David
signature.asc
Description: This is a digitally signed message part.
___
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] [kdesdk3] Compile error
Hi, While doing a portupgrade -R kde3 I came upon the following error. This is on -current (from ~ last Tuesday). Of note: flex-2.5.35 is installed. Regards David gmake[4]: Entering directory `/tmp/usr/ports/devel/kdesdk3/work/kdesdk-3.5.10/kbabel/common/libgettext' flex -+ -opofiles.cc ./pofiles.ll /bin/sh /usr/local/bin/libtool --silent --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I../../.. -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -fno-strict-aliasing -pipe -march=nocona -fconserve-space -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT pofiles.lo -MD -MP -MF .deps/pofiles.Tpo -c -o pofiles.lo pofiles.cc pofiles.cc:451:5: warning: YY_STACK_USED is not defined pofiles.cc:1519:5: warning: YY_MAIN is not defined In file included from pofiles.cc:250: /usr/local/include/FlexLexer.h:130: error: expected unqualified-id before numeric constant pofiles.cc: In member function 'virtual int GettextBaseFlexLexer::yylex()': pofiles.cc:576: error: 'yy_current_buffer' was not declared in this scope pofiles.cc:732: error: 'yy_current_buffer' was not declared in this scope pofiles.cc:755: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In constructor 'GettextBaseFlexLexer::GettextBaseFlexLexer(std::istream*, std::ostream*)': pofiles.cc:872: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In destructor 'virtual GettextBaseFlexLexer::~GettextBaseFlexLexer()': pofiles.cc:884: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'virtual void GettextBaseFlexLexer::switch_streams(std::istream*, std::ostream*)': pofiles.cc:891: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'int GettextBaseFlexLexer::yy_get_next_buffer()': pofiles.cc:944: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'void GettextBaseFlexLexer::yyunput(int, char*)': pofiles.cc:1139: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'int GettextBaseFlexLexer::yyinput()': pofiles.cc:1181: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'virtual void GettextBaseFlexLexer::yyrestart(std::istream*)': pofiles.cc:1240: error: 'yy_current_buffer' was not declared in this scope pofiles.cc:1243: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'virtual void GettextBaseFlexLexer::yy_switch_to_buffer(yy_buffer_state*)': pofiles.cc:1250: error: 'yy_current_buffer' was not declared in this scope pofiles.cc:1253: error: 'yy_current_buffer' was not declared in this scope pofiles.cc:1261: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'void GettextBaseFlexLexer::yy_load_buffer_state()': pofiles.cc:1275: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'virtual void GettextBaseFlexLexer::yy_delete_buffer(yy_buffer_state*)': pofiles.cc:1312: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'void GettextBaseFlexLexer::yy_flush_buffer(yy_buffer_state*)': pofiles.cc:1354: error: 'yy_current_buffer' was not declared in this scope gmake[4]: *** [pofiles.lo] Error 1 gmake[4]: Leaving directory `/tmp/usr/ports/devel/kdesdk3/work/kdesdk-3.5.10/kbabel/common/libgettext' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/tmp/usr/ports/devel/kdesdk3/work/kdesdk-3.5.10/kbabel/common' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/tmp/usr/ports/devel/kdesdk3/work/kdesdk-3.5.10/kbabel' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/tmp/usr/ports/devel/kdesdk3/work/kdesdk-3.5.10' gmake: *** [all] Error 2 *** Error code 2 signature.asc Description: This is a digitally signed message part. ___ 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] [kdesdk3] Compile error [SOLVED] [PATCH]
Hi, The problem is easily solved using the patch provided here: http://mail.kde.org/pipermail/kde-freebsd/2007-August/001441.html Can anyone comfirm that this port builds without the above patch? If not could an accredited person please commit the patch. Regards David On Sunday 21 September 2008 13:26:33 David Naylor wrote: Hi, While doing a portupgrade -R kde3 I came upon the following error. This is on -current (from ~ last Tuesday). Of note: flex-2.5.35 is installed. Regards David gmake[4]: Entering directory `/tmp/usr/ports/devel/kdesdk3/work/kdesdk-3.5.10/kbabel/common/libgettext' flex -+ -opofiles.cc ./pofiles.ll /bin/sh /usr/local/bin/libtool --silent --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I../../.. -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -fno-strict-aliasing -pipe -march=nocona -fconserve-space -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT pofiles.lo -MD -MP -MF .deps/pofiles.Tpo -c -o pofiles.lo pofiles.cc pofiles.cc:451:5: warning: YY_STACK_USED is not defined pofiles.cc:1519:5: warning: YY_MAIN is not defined In file included from pofiles.cc:250: /usr/local/include/FlexLexer.h:130: error: expected unqualified-id before numeric constant pofiles.cc: In member function 'virtual int GettextBaseFlexLexer::yylex()': pofiles.cc:576: error: 'yy_current_buffer' was not declared in this scope pofiles.cc:732: error: 'yy_current_buffer' was not declared in this scope pofiles.cc:755: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In constructor 'GettextBaseFlexLexer::GettextBaseFlexLexer(std::istream*, std::ostream*)': pofiles.cc:872: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In destructor 'virtual GettextBaseFlexLexer::~GettextBaseFlexLexer()': pofiles.cc:884: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'virtual void GettextBaseFlexLexer::switch_streams(std::istream*, std::ostream*)': pofiles.cc:891: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'int GettextBaseFlexLexer::yy_get_next_buffer()': pofiles.cc:944: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'void GettextBaseFlexLexer::yyunput(int, char*)': pofiles.cc:1139: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'int GettextBaseFlexLexer::yyinput()': pofiles.cc:1181: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'virtual void GettextBaseFlexLexer::yyrestart(std::istream*)': pofiles.cc:1240: error: 'yy_current_buffer' was not declared in this scope pofiles.cc:1243: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'virtual void GettextBaseFlexLexer::yy_switch_to_buffer(yy_buffer_state*)': pofiles.cc:1250: error: 'yy_current_buffer' was not declared in this scope pofiles.cc:1253: error: 'yy_current_buffer' was not declared in this scope pofiles.cc:1261: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'void GettextBaseFlexLexer::yy_load_buffer_state()': pofiles.cc:1275: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'virtual void GettextBaseFlexLexer::yy_delete_buffer(yy_buffer_state*)': pofiles.cc:1312: error: 'yy_current_buffer' was not declared in this scope pofiles.cc: In member function 'void GettextBaseFlexLexer::yy_flush_buffer(yy_buffer_state*)': pofiles.cc:1354: error: 'yy_current_buffer' was not declared in this scope gmake[4]: *** [pofiles.lo] Error 1 gmake[4]: Leaving directory `/tmp/usr/ports/devel/kdesdk3/work/kdesdk-3.5.10/kbabel/common/libgettext' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/tmp/usr/ports/devel/kdesdk3/work/kdesdk-3.5.10/kbabel/common' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/tmp/usr/ports/devel/kdesdk3/work/kdesdk-3.5.10/kbabel' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/tmp/usr/ports/devel/kdesdk3/work/kdesdk-3.5.10' gmake: *** [all] Error 2 *** Error code 2 signature.asc Description: This is a digitally signed message part. ___ 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] Proposed patch
On Tuesday 08 July 2008 19:14:07 David Johnson wrote:
On Tuesday 08 July 2008 02:13:15 am Max Brazhnikov wrote:
On Tue, 8 Jul 2008 00:17:00 -0700, David Johnson wrote:
I'm attaching a patch that should fix the problems building KDE4 when
KDE3 is already installed. The problem is that cmake will sometimes
generate build files will will attempt to link to the KDE3 libraries in
/usr/local/lib.
Is it right that with this patch we have no need to move kde3 libs and
includes from ${LOCALBASE}?
I'll do some more testing this evening, but so far ldd does not show any
KDE4 binaries trying to link with KDE3 libs. So I think the answer is that
we don't have to move them.
But I think in the long term we should move KDE3.
I had been working on a script that should do 95%+ of the work in moving KDE3
into its own subprefix (lib/kde3, bin/kde3). I ran into a problem with
building kdelibs.
The problem was that after running:
#sed -i '' -e 's/foo/bar/g' `find . -name '*.cpp' -or -name '*.h'`
The build failed. After that I ran out of time and patience to work on the
problem but if anyone has a suggestion on how to fix it or wishes to see the
work that I have done please let me know.
VERY IMPORTANT, it will be MUCH easier to move the whole of KDE3 into its own
prefix (${LOCALBASE}/kde3, or equivalent).
Good programming
David
signature.asc
Description: This is a digitally signed message part.
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] kde4 and firebase
On Saturday 28 June 2008 08:22:00 Ernst W. Winter wrote: Hello, cleaned everything up and done a new /usr/ports and area51 and wanted to restart all needed apps for kde4 but then this happen: [---Snip] ===Verifying install for /usr/local/lib/qt4/plugins/sqldrivers/libqsqlibase .so in /usr/ports/databases/qt4-ibase-plugin === qt4-ibase-plugin-4.4.0 depends on package: qt4-moc=4.4.0 - found === qt4-ibase-plugin-4.4.0 depends on package: qt4-sql=4.4.0 - found === qt4-ibase-plugin-4.4.0 depends on shared library: fbclient.2 - not found ===Verifying install for fbclient.2 in /usr/ports/databases/firebird2-clien t === Building for firebird-client-2.0.3_2 == Please do not build firebird as 'root' because this may cause conflicts with SysV semaphores of running services. *** Error code 1 Stop in /usr/ports/databases/firebird2-client. *** Error code 1 Stop in /usr/ports/databases/qt4-ibase-plugin. *** Error code 1 Stop in /usr/ports/devel/qt4. *** Error code 1 Stop in /usr/ports/devel/qt4. /usr/ports/devel/qt4 [---Snip] well how can it be compiled? This can be painful, especially when builds are set to 'auto'... You could either edit the Makefile to remove the requirement (and hope it does not mess up you computer) or you could compile it using a non root account. The easiest way to do this is: o) Create a user account that is in the wheel group # su ``user in wheel group'' # cd /usr/ports/databases/firebird2-client # make install clean WRKDIRPREFIX=/tmp # exit Ports automatically uses su if the user is not root and thus will allow you to install the problem without too much complication. Normally the default location for building ports are not writable by non root accounts so you need to change the building location (via WRKDIRPREFIX) Ernst David signature.asc Description: This is a digitally signed message part. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
[kde-freebsd] [QUESTION] KDE3 and its own prefix
Hi,
I see that currently with the porting efforts of KDE4 that it gets
stuck into its own prefix (i.e. ${PREFIX}/kde4). As I understand KDE4
is going to be the default (of KDE3/4) since it will (hopefully by
4.1) be a superset of KDE3. Of course some kde3 programs will not
make it to kde/qt 4 and will need to be supported.
I have looked through kdelibs and I think I have found a way to
cleanly install kde3 into its own subprefix's: i.e
${PREFIX}/bin/kde3
${PREFIX}/sbin/kde3
${PREFIX}/lib/kde3
${PREFIX}/share/kde3
This involves adding the appropriate --datadir, --bindir and --libdirs
to CONFIGURE_ARGS and hacking kstandarddir.cpp in kdelibs/kdecore to
support the change. With those changes it should handle 99% of all
cases.
Just two minor issues: 1) since everything will be installed under
${PREFIX}/share/kde3 the menu entries will not be shared between KDE3
and KDE4/gnome. This should not be an issue with kde but could cause
problems with 3rd party ports as a user may wish to use it with KDE4
(it could be solved, but not simply?) 2) ${PREFIX}/bin/kde3 will need
to be added to the search path for KDE4, I do not know how to do it
(any hints :)
What if we made kdelib3 live nicely with kde4 and had the rest of the
components conflict? Since KDE4 should (hopefully) have feature and
program parity with KDE3 this would allow missing, unported, 3rd party
ports to work in KDE4. And/or could we have all 3rd party ports
conflict with their relevant pairs (between KDE3 versions and KDE4
versions). This will just make life much easier [but may tern out as
being unnecessary).
If the first part (about having kde3 in its own subprefix) is a
desired outcome then I can create a patch and have it (mostly) tested
by weekout??? [Just don't hold your breath]
Regards
David
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
[kde-freebsd] KDE3 not running
Hi, Today I tried installing kde3 from area51. No problems with compiling however it appears the dynamic library system appears to be broken. For example: konqueror complains that a lot of the konq_*.la have not been found. (I have checked and they are installed, under /usr/local/lib/kde3/kde3) [konq_iconview.la for a specific item, from memory] Another thing I have noticed is that kdm does not work. The script appears to be looking for kde4, since it was installed with kde3 I am not sure what is going on. I think a good solution would be for it to check for both kdm's and favor the kde4/kdm? Are there any automated (regression) checks that I can execute? If you need further details please let me know (or any clues on how to solved this). Regards David P.S. Is it desired, at some stage, to split up the kde4 ports, as openSUSE has done. Of course to have the relevant meta ports [so nothing changes except extra fine tuning available] (i.e. kdebase into kdebase-kwrite, kdebase-konqueror, etc) P.P.S. Are we going to follow the gnome route and have kdm start as an rc.d script? ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
[kde-freebsd] KDE4 Porting Coordinator
Hi, Who is the porting coordinator for porting kde4 to freebsd and who should one speak to if one has some contributions to make? Ragards David signature.asc Description: This is a digitally signed message part. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] KDE4 Porting Coordinator
On Sunday 18 May 2008 13:48:29 Adriaan de Groot wrote: On Sunday 18 May 2008 12:41, David Naylor wrote: Who is the porting coordinator for porting kde4 to freebsd and who should one speak to if one has some contributions to make? Based on who's doing the work those would be miwi, david johnson and lofi. Generally posting things to this list is enough -- constructive things, that is. Patches, etc. There's a separate cvs repo (I can never remember where it is, I think it's documented on the freebsd.kde.org website) with KDE4 ports experiments. Patches for the fbsd.k.o website can be sent here or to [EMAIL PROTECTED] Thank you for your quick responce. When some patches emerge I'll post them here :-). [ade] David signature.asc Description: This is a digitally signed message part. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] [HEADS UP] QT4.4 RC and KDE4.1 Alpha
On Friday 02 May 2008 23:12:43 Danny Pansters wrote: Hi folks, On Wednesday 30 April 2008 17:02:47 Thomas Abthorpe wrote: On Wednesday 30 April 2008 05:33:40 Martin Wilke wrote: And another problem (not really serious but should be discussed) is that I want to rename some ports: kdepimlibs - kdepimlibs4 kdebase-runtime - kdebase4-runtime kdebase-workspace - kdebase4-workspace kdenetwork - kdenetwork4 kdeartwork - kdeartwork4 kdeadmin - kdeadmin4 kdeutils - kdeutils4 kdemultimedia - kdemultimedia4 kdeedu - kdeedu4 kdetoys- kdetoys4 kdegraphics- kdegraphics4 kdesdk - kdesdk4 kdewebdev - kdewebdev4 kdegames - kdegames4 The rename makes more sense for the future with KDE5. (Hopefully not in the next 5 years) Does anyone have anything against it? I'm with Miwi on this one, I would like to see the respective kde ports postfixed with the major rev number, it is wa-y less confusing, and as he says, poises us well for the future with kde5 et al. Thomas I agree too, it's the lesser evil. The same question is coming with 3rd party apps: Seconded I've been looking a little bit at kmplayer and gtk-qt-engine for kde4, and there too I pretty much already reached the conclusion that there will be no other option than to start calling them kmplayer4 etc, if they are to coexist with their kde3 older versions for a significant time (and let's not kid ourselves, we're still looking at ~ a year in that respect). I think ideally it would be nice if we could say that kde4 and kde3 just conflict (which they do!) however we should be realistic. Where is an alternative approach... Scenario 1 -- Have kde3 and kde4 conflict. This makes life really easy and those who do not depend on or require kde3 do not have to put up with all the horrible suffixes. Straight and simple (the way to go :-) Scenario 2 -- Put kde4 in its own suffix (i.e. /usr/local/kde4). This avoids a lot of problems with kde3. (A possible alternative is to have kde4 in subprefixes, such as /usr/local/bin/kde4, /usr/local/lib/kde4, etc). Either case I think CMake will be able to do it with ease. The great thing is we could have both scenarios in ports and one could switch between them with a knob (i.e. WITH_KDE3 or WITHOUT_KDE3?). With a bit of genius it would happen seamlessly :-) I'm afraid that later on at one point in time (when qt3/kde3 go EOL in ports) we're probably going to have the repocopy fest of the decade, because then probably everyone and their sister are going to want to rename the foo4 back to just foo. I think something like this is going to be unavoidable (it could be nicely synch'd with the start of a ports freeze as the time to do the repofest arrives). One option (which I doubt is feasible) is to have both kde3 and kde4 suffixed with sym-links to the `proper' name of the binary, that way a switch from kde3 to kde4 results in a change of sym-links. Or alternative leave kde3 and when it goes EOL replace the binaries with sym-links to their kde4 equivalents. Comments? What are people's thoughts about this, 3rd party apps/libs that will have to coexist in different versions for kde3/4 for (quite) a while? It may be a good time now to establish some guidelines for porters. CMake may just have some magic that will ease this whole process, I can investigate this after my exams (about a month and a half away :-( ) Has anyone spoken to other packages (Gentoo?) and the CMake/KDE developers. They might have already have solved this problem for us, or at least have good suggestions on which direction to travel (and possibly good hints on how to implement it...) Regards David signature.asc Description: This is a digitally signed message part. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
