Hi,
I've just found out about the Trinity DE project. I haven't tested it
yet, though I'm wondering - do you need any Polish translators for
your project? I might be of help, provided it won't be too much work.
Yours,
d33tah
This is a Qt3-based Compiz-Fusion icon that allows to setup Compiz from KDE3.
https://build.opensuse.org/package/files?package=fusion-icon-qt3&project=ho…
It works well except it fails to secure place in system tray on start which
leads to appearance of the icon randomly on the screen.
Can anybody suggest a patch that fixes the behavior? Adding a delay does not
help in this case.
Tim, All;
I have noticed this with Trinity throughout 3.5.13 development, but it never
bubbled up in priority over CMake and build issues. The problem:
If you use one of the "Super User Mode" apps like konqueror file manager. The
desktop can no longer launch applications as a normal user until Trinity is
restarted. You get a Klauncher error message that "Klauncher could not be
reached via dcop".
It looks like after a super user app is run - the dcop is stuck in super user
mode or something similar. I don't know how to go about chasing this down, but
wanted to bring it to the lists attention. I also want to know if someone else
can confirm this behavior.
Just open System->Super User->File Manager-Super User Mode
It will work fine. Then close it. No go try and open any other app as a
normal user (i.e. kwrite). It won' work. You will get the error:
"Klauncher could not be reached via dcop"
So what every gets changed when dcop runs a Super User mode app -- doesn't
get undone when the app exits.
--
David C. Rankin, J.D.,P.E.
It seems that libexiv2-10 is not compatible with KDE3. After update of
libexiv2 from libexiv2-9 to libexiv2-10 in openSUSE:Factory all KDE3 packages
that require libexiv2 became broken.
Any thoughts of how to mitigate this?
Hello,
The upstream tqtinterface uses by default a qt library path of
$QTDIR/lib$LIBDIRSUFFIX, but Qt uses lib instead of lib64 within its
"private" directory:
-with the default build options, both for qt3 and qt4
-in the Debian Squeeze qt3 package.
The patch attached to this e-mail solves this inconsistency and makes
TQt3 build successfully with default options on Slackware, without
specifying the Qt libdir.
i finish the qt3 work by my own, if interesting, can view the complete work
on http://www.shutendouji.net/massenkoh/projects/qt3/ this are tested on
debian etch, lenny, squeeze, and geento & funtoo, on x86, and some amd64
atom laptops, also tested on hurd (over virtual machine)
theres a compiled qt 3.3.8c-1 package folow stric debian policy also.
the debian source list entry its " deb
http://www.shutendouji.net/massenkoh/projects/qt3/ ./ " for the pqt3 3.3.8c
package entry only, with support for build under amd_64, x86 and hurd,
geento ebuild its on work progress on msktoo.blogspot.com
i will post a blog and info entry in few days explain with better english
all work in deep!
On Tue, May 24, 2011 at 7:43 PM, /dev/ammo42 <mickeytintincolle(a)yahoo.fr>wrote:
> Hello,
> Here is (attached to this e-mail) the patch that enabled me to build
> the Qt3 SVN tree with only Slackware-specific patches and the libpng14
> patch as supplementary patch, on my Slackware64 13.37 with Qt4 and KDE4
> installed alongside, and with /opt/kde3 prefix.
> The patch:
> —adds include/ symlinks which were present in qt-3.3.8b but not in SVN.
> Especially, there was no symlink in include/private.
> —but removes the include/png.h symlink, since nobody in their right
> mind would use the included libpng 1.2.5, and the build system puts the
> internal -I before -I/usr/include, making the build fail on
> libpng-1.4-only systems because it uses the libpng-1.2.5 include instead
> of the 1.4.5 one. Let's just let the user specify the libpng include if
> it is nonstandard (BTW, I have some doubts regarding qt3's abilities to
> detect libpng, since it didn't -I/usr/include/libpng14, the latter
> being the include path specified in my libpng.pc).
> —adds a missing #include <cstdlib> in qdesktopwidget_x11.c.
> Did someone build the SVN version of Qt3 on distributions other than
> Debian/Ubuntu or Slackware ?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
> For additional commands, e-mail:
> trinity-devel-help(a)lists.pearsoncomputing.net
> Read list messsages on the Web archive:
> http://trinity-devel.pearsoncomputing.net/
> Please remember not to top-post:
> http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux; debian based multimedia alike free only zealots
users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date
support on stable brand, including non-free soft.
Hello,
Here is (attached to this e-mail) the patch that enabled me to build
the Qt3 SVN tree with only Slackware-specific patches and the libpng14
patch as supplementary patch, on my Slackware64 13.37 with Qt4 and KDE4
installed alongside, and with /opt/kde3 prefix.
The patch:
—adds include/ symlinks which were present in qt-3.3.8b but not in SVN.
Especially, there was no symlink in include/private.
—but removes the include/png.h symlink, since nobody in their right
mind would use the included libpng 1.2.5, and the build system puts the
internal -I before -I/usr/include, making the build fail on
libpng-1.4-only systems because it uses the libpng-1.2.5 include instead
of the 1.4.5 one. Let's just let the user specify the libpng include if
it is nonstandard (BTW, I have some doubts regarding qt3's abilities to
detect libpng, since it didn't -I/usr/include/libpng14, the latter
being the include path specified in my libpng.pc).
—adds a missing #include <cstdlib> in qdesktopwidget_x11.c.
Did someone build the SVN version of Qt3 on distributions other than
Debian/Ubuntu or Slackware ?
Hi,
On Monday 23 May 2011 12:15:11 Robert Xu wrote:
> On May 22, 2011, at 23:01, Calvin Morrison <mutantturkey(a)gmail.com> wrote:
> > Tim, All,
> >
> > I recently got my hands on a VPS that I don't have much use for.
> >
> > It has 300Gb / Month bandwidth, and I certainly won't be using it that
> > extensively.
> >
> > Would it be suitable as an mirror?
>
> Mirrors take up a hell of a lot of bandwidth...
maybe someone could provide some statistics on that... if it is not too much i
might also be able to help out..
greetings,
Roman
--
--
Don't hit me!! I'm in the Twilight Zone!!!