[kde-freebsd] [SVN Commit] area51/KDE/misc/kde4-l10n-et
SVN commit 5537 by tabthorpe: - Fix plist M +1 -0 pkg-plist ___ 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] [SVN Commit] area51/KDE/deskutils/kdepim4
SVN commit 5536 by tabthorpe: - Fix plist M +1 -0 pkg-plist ___ 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] [SVN Commit] area51/KDE/misc/kde4-l10n-it
SVN commit 5535 by tabthorpe: - Fix plist M +3 -0 pkg-plist ___ 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] [SVN Commit] area51/KDE/german/kde4-l10n
SVN commit 5534 by tabthorpe: - Fix plist M +1 -0 pkg-plist ___ 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] [SVN Commit] area51/KDE/hungarian/kde4-l10n
SVN commit 5533 by tabthorpe: - Fix plist M +24 -0 pkg-plist ___ 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] Only few windows available when 3D is enabled?
Le Thu, 29 Oct 2009 01:45:06 +, Bartosz Fabianowski a écrit : > My guess would be your GPU is running out of resources. On a > composited desktop, each window is a texture map. The textures then > get composited onto an off-screen surface. All of this requires a lot > of memory. That could be, but it looks to be a known problem with the nvidia driver. It is called the "black window bug" on nvidia's forums. It's not a KDE problem, sorry for the noise. Thanks, regards. ___ 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] [SVN Commit] area51/KDE/graphics/kdegraphics4
SVN commit 5532 by tabthorpe: - Fix plist M +4 -2 pkg-plist ___ 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] [SVN Commit] area51/KDE/x11/kdelibs4/files
SVN commit 5531 by tabthorpe: - Remove back port patches D patch-1032185 D patch-1032787 D patch-1033984 ___ 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] [SVN Commit] area51/KDE/x11-themes/kde4-icons-oxygen
SVN commit 5530 by fluffy: - Fix plist M +76 -1 pkg-plist ___ 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 2>&1
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
[kde-freebsd] [SVN Commit] area51/QT/misc/py-qt4-demo
SVN commit 5529 by fluffy: - Fix build M +1 -0 Makefile A files/patch-examples__activeqt__webbrowser__webbrowser.py M +2 -2 pkg-plist ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde
El día Friday, October 30, 2009 a las 04:17:55PM +0100, Matthias Apitz escribió: > Hello, > > I have in a VM a 9-CURRENT and comiled/installed from the ports first > x11/kde3 (which worked fine) and now in addition x11/kde4 (which comes > up also fine). > > But, > > A start of KDE3 from ~/.xinitrc via exec /usr/local/bin/startkde > complains in the following code: > > # We set LD_BIND_NOW to increase the efficiency of kdeinit. > # kdeinit unsets this variable before loading applications. > LD_BIND_NOW=true start_kdeinit_wrapper --new-startup +kcminit_startup > if test $? -ne 0; then > # Startup error > echo 'startkde: Could not start kdeinit. Check your installation.' 1>&2 > xmessage -geometry 500x100 "Could not start kdeinit. Check your > installation." > fi > > i.e. it brings up this xmessage box and in the log files I can see that > 'start_kdeinit_wrapper' SIGABORT's. The KDE desktop itself comes up > fine. This is, as I said, after compiling the port x11/kde4. The file > /usr/local/bin/start_kdeinit_wrapper is not touched by the port x11/kde4 > and neither the shared libs it is depending: ... It's fully reproduceable. I have installed the packages, first kde-3.5.10_2.tbz and then kde4-4.3.1.tbz. Both are coming up fine via ~/.xinitrc but the KDE3 gives the above error message box. Will file a bug report. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu ___ 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 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
