Is there an official list archive somewhere? I'd like to read through the
old messages and get up to speed on things.
Uh... by "archive" I mean the old style "a file containing messages in mbox
or maildir format", not the new style "a web portal into a mail database."
Not trying to be picky, but when it's most convenient for me to read it, I'll
be at a secure site with no internet access.
On my build system I built kdepim while krb5 was installed. I installed the final packages on a different system.
Now Akregator refuses to fetch feeds unless krb5 is installed.
I understand the cause and effect, but seems to me this might be a bug. Even when built with krb5 present, apps should still run when krb5 is not installed or found. The app loses some authentication security, but that would be the same result as when kdepim is compiled without krb5 present during the build.
Can others confirm this behavior? If so then I'll file a bug.
Thanks.
Darrell
Some things I noticed when using kdesu to open Kate.
1. In the password dialog box there was no check box to remember the password.
2. For my root user I have Kate configured to use a pink background rather than white. That serves as a simple reminder I am working as root and not as a normal user. Yet in Trinity, after launching through kdesu, Kate did not display the background as pink but white. Superficially that seems to indicate Kate inherited the normal user's properties rather than root's.
3. After running kdesu to open Kate, I continually received DCOP error messages of the effect that KLauncher could not be reached via DCOP. Basically I had to restart my desktop session thereafter to launch apps.
Comments? Confirmations?
Darrell
Hi,
Pardus is a Linux distribution funded and developed by the Turkish Government.
We're planning to release a Corporate version - Pardus Corporate 2 - which is
based on KDE 3.5.
We've been maintaining KDE 3.5 for a very long time so we have a lot of
bugfix/feature patches in our base packages.
I want to push those patches to trinity after doing a review with trinity
contributors about their upstreamability.
And then I really want to switch to Trinity KDE in Pardus Corporate 2 as this
will be a long-term supported release which should a have a maintained desktop
environment.
Right now I started to prepare packages for the dependencies.
I'm waiting for your co-operation to make things better.
---
Ozan Çağlayan
TUBITAK/UEKAE - Pardus Linux
http://www.pardus.org.tr/eng
Hi,
When I was searching a way to autostart KMix, I've found a patch by
Chakra that's merged into trinity sources which adds X-KDE-Autostart-*
keywords to kmix.desktop file but the relevant kmix.desktop file is not
installed under the global autostart directory so it doesn't autostart
KMix on my vanilla 3.5.10.
Are there patches in Trinity which provides autostarting even if the
desktop file doesn't reside in the autostart directory?
Also there's this X-KDE-Autostart-Condition:* thing in KMix desktop for
checking autostart= value in kmixrc but apparently KMix doesn't even
know about the autostart= configuration key.
It's quite possible that the desktop file patch from Chakra is adopted
directly from KDE 4.x.
Regards,
Ozan Caglayan
In KDE 3.5.10, with floppy drive polling explicitly disabled with HAL, the Unmounted Floppy icon appears on my desktop. This provides me a means to manually mount floppy disks. Yeah, once in a blue moon I still use floppies (I have some old computers with no USB support).
BTW, disabling polling stops the clicking sound.
With Trinity, the Unmounted Floppy desktop icon no longer appears. I presume this has something to do with polling being disabled.
I can get the Unmounted Floppy icon to appear by inserting a USB flash drive. This seems to refresh the desktop. But this lasts only for that session. Next restart of Trinity and the Unmounted Floppy desktop icon is gone.
Is this different behavior a bug or a "feature"?
Thanks.
Darrell
I notice when enabling any of the Desktop device Icons such as My Documents, My Network, Printers, etc., that the icon always first appears on the left side of the desktop (expected) but always in the second row of the icon grid (not expected).
Looks slap-happy.
Is there an option to force the icons to appear in the first column of the icon grid?
Darrell
Hi all,
I'm getting the following errors and since I'm no C++ expert, I need some
mentoring to figure this out. I know C and PHP but C++ is not usually my
thing.
Here it is:
In file included from qiomanager.cc:23:
qiomanager.h:33:22: error: tqobject.h: No such file or directory
qiomanager.h:34:21: error: tqtimer.h: No such file or directory
qiomanager.h:35:30: error: tqsocketnotifier.h: No such file or directory
qiomanager.cc:26:27: error: tqapplication.h: No such file or directory
qiomanager_p.h:41: error: expected class-name before ‘{’ token
qiomanager_p.h:42: error: ISO C++ forbids declaration of ‘Q_OBJECT’ with no
type
qiomanager_p.h:43: error: expected ‘;’ before ‘protected’
qiomanager_p.h:51: error: ‘TQSocketNotifier’ has not been declared
qiomanager_p.h:51: error: expected ‘,’ or ‘...’ before ‘qtype’
qiomanager_p.h:58: error: expected `:' before ‘slots’
qiomanager_p.h:59: error: expected primary-expression before ‘void’
qiomanager_p.h:59: error: ISO C++ forbids declaration of ‘slots’ with no
type
qiomanager_p.h:59: error: expected ‘;’ before ‘void’
qiomanager_p.h:62: error: expected class-name before ‘{’ token
qiomanager_p.h:63: error: ISO C++ forbids declaration of ‘Q_OBJECT’ with no
type
qiomanager_p.h:64: error: expected ‘;’ before ‘protected’
qiomanager_p.h:71: error: expected `:' before ‘slots’
qiomanager_p.h:72: error: expected primary-expression before ‘void’
qiomanager_p.h:72: error: ISO C++ forbids declaration of ‘slots’ with no
type
qiomanager_p.h:72: error: expected ‘;’ before ‘void’
qiomanager.cc:69: error: ‘TQSocketNotifier’ has not been declared
qiomanager.cc:69: error: expected ‘,’ or ‘...’ before ‘qtype’
qiomanager.cc: In constructor ‘Arts::QIOWatch::QIOWatch(int, int,
Arts::IONotify*, int)’:
qiomanager.cc:70: error: argument of type ‘bool (Arts::QIOWatch::)()’ does
not match ‘bool’
qiomanager.cc:72: error: ‘qsocketnotify’ was not declared in this scope
qiomanager.cc:72: error: expected type-specifier before ‘TQSocketNotifier’
qiomanager.cc:72: error: expected `;' before ‘TQSocketNotifier’
qiomanager.cc:73: error: expected primary-expression before ‘int’
qiomanager.cc:73: error: ‘activated’ was not declared in this scope
qiomanager.cc:73: error: ‘TQT_SIGNAL’ was not declared in this scope
qiomanager.cc:73: error: expected primary-expression before ‘int’
qiomanager.cc:73: error: ‘notify’ cannot be used as a function
qiomanager.cc:73: error: ‘TQT_SLOT’ was not declared in this scope
qiomanager.cc: At global scope:
qiomanager.cc:69: warning: unused parameter ‘Type’
qiomanager.cc:76: error: no ‘void Arts::QIOWatch::notify(int)’ member
function declared in class ‘Arts::QIOWatch’
qiomanager.cc: In constructor ‘Arts::QTimeWatch::QTimeWatch(int,
Arts::TimeNotify*)’:
qiomanager.cc:87: error: ‘timer’ was not declared in this scope
qiomanager.cc:87: error: expected type-specifier before ‘TQTimer’
qiomanager.cc:87: error: expected `;' before ‘TQTimer’
qiomanager.cc:88: error: ‘timeout’ was not declared in this scope
qiomanager.cc:88: error: ‘TQT_SIGNAL’ was not declared in this scope
qiomanager.cc:88: error: ‘notify’ cannot be used as a function
qiomanager.cc:88: error: ‘TQT_SLOT’ was not declared in this scope
qiomanager.cc: At global scope:
qiomanager.cc:93: error: no ‘void Arts::QTimeWatch::notify()’ member
function declared in class ‘Arts::QTimeWatch’
qiomanager.cc: In member function ‘virtual void
Arts::QIOManager::processOneEvent(bool)’:
qiomanager.cc:159: error: ‘qApp’ was not declared in this scope
qiomanager.cc:161: error: ‘qApp’ was not declared in this scope
qiomanager.cc: In member function ‘virtual void
Arts::QIOManager::watchFD(int, int, Arts::IONotify*)’:
qiomanager.cc:182: error: ‘TQSocketNotifier’ has not been declared
qiomanager.cc:188: error: ‘TQSocketNotifier’ has not been declared
qiomanager.cc:194: error: ‘TQSocketNotifier’ has not been declared
qiomanager_p.moc: At global scope:
qiomanager_p.moc:22: error: no ‘const char* Arts::QIOWatch::className()
const’ member function declared in class ‘Arts::QIOWatch’
qiomanager_p.moc:27: error: ‘QMetaObject* Arts::QIOWatch::metaObj’ is not a
static member of ‘class Arts::QIOWatch’
qiomanager_p.moc:28: error: ‘staticMetaObject’ is not a member of
‘Arts::QIOWatch’
qiomanager_p.moc:31: error: no ‘QString Arts::QIOWatch::tr(const char*,
const char*)’ member function declared in class ‘Arts::QIOWatch’
qiomanager_p.moc:39: error: no ‘QString Arts::QIOWatch::trUtf8(const char*,
const char*)’ member function declared in class ‘Arts::QIOWatch’
qiomanager_p.moc:50: error: no ‘QMetaObject*
Arts::QIOWatch::staticMetaObject()’ member function declared in class
‘Arts::QIOWatch’
qiomanager_p.moc: In member function ‘QMetaObject*
Arts::QIOWatch::staticMetaObject()’:
qiomanager_p.moc:52: error: ‘metaObj’ was not declared in this scope
qiomanager_p.moc:54: error: ‘TQObject’ has not been declared
qiomanager_p.moc:62: error: ‘metaObj’ was not declared in this scope
qiomanager_p.moc: At global scope:
qiomanager_p.moc:75: error: no ‘void* Arts::QIOWatch::qt_cast(const char*)’
member function declared in class ‘Arts::QIOWatch’
qiomanager_p.moc: In member function ‘void* Arts::QIOWatch::qt_cast(const
char*)’:
qiomanager_p.moc:79: error: ‘TQObject’ has not been declared
qiomanager_p.moc: At global scope:
qiomanager_p.moc:82: error: no ‘bool Arts::QIOWatch::qt_invoke(int,
QUObject*)’ member function declared in class ‘Arts::QIOWatch’
qiomanager_p.moc: In member function ‘bool Arts::QIOWatch::qt_invoke(int,
QUObject*)’:
qiomanager_p.moc:87: error: ‘TQObject’ has not been declared
qiomanager_p.moc: At global scope:
qiomanager_p.moc:92: error: no ‘bool Arts::QIOWatch::qt_emit(int,
QUObject*)’ member function declared in class ‘Arts::QIOWatch’
qiomanager_p.moc: In member function ‘bool Arts::QIOWatch::qt_emit(int,
QUObject*)’:
qiomanager_p.moc:94: error: ‘TQObject’ has not been declared
qiomanager_p.moc: At global scope:
qiomanager_p.moc:98: error: no ‘bool Arts::QIOWatch::qt_property(int, int,
QVariant*)’ member function declared in class ‘Arts::QIOWatch’
qiomanager_p.moc: In member function ‘bool Arts::QIOWatch::qt_property(int,
int, QVariant*)’:
qiomanager_p.moc:100: error: ‘TQObject’ has not been declared
qiomanager_p.moc: At global scope:
qiomanager_p.moc:103: error: no ‘bool
Arts::QIOWatch::qt_static_property(QObject*, int, int, QVariant*)’ member
function declared in class ‘Arts::QIOWatch’
qiomanager_p.moc:107: error: no ‘const char* Arts::QTimeWatch::className()
const’ member function declared in class ‘Arts::QTimeWatch’
qiomanager_p.moc:112: error: ‘QMetaObject* Arts::QTimeWatch::metaObj’ is not
a static member of ‘class Arts::QTimeWatch’
qiomanager_p.moc:113: error: ‘staticMetaObject’ is not a member of
‘Arts::QTimeWatch’
qiomanager_p.moc:116: error: no ‘QString Arts::QTimeWatch::tr(const char*,
const char*)’ member function declared in class ‘Arts::QTimeWatch’
qiomanager_p.moc:124: error: no ‘QString Arts::QTimeWatch::trUtf8(const
char*, const char*)’ member function declared in class ‘Arts::QTimeWatch’
qiomanager_p.moc:135: error: no ‘QMetaObject*
Arts::QTimeWatch::staticMetaObject()’ member function declared in class
‘Arts::QTimeWatch’
qiomanager_p.moc: In member function ‘QMetaObject*
Arts::QTimeWatch::staticMetaObject()’:
qiomanager_p.moc:137: error: ‘metaObj’ was not declared in this scope
qiomanager_p.moc:139: error: ‘TQObject’ has not been declared
qiomanager_p.moc:144: error: ‘metaObj’ was not declared in this scope
qiomanager_p.moc: At global scope:
qiomanager_p.moc:157: error: no ‘void* Arts::QTimeWatch::qt_cast(const
char*)’ member function declared in class ‘Arts::QTimeWatch’
qiomanager_p.moc: In member function ‘void* Arts::QTimeWatch::qt_cast(const
char*)’:
qiomanager_p.moc:161: error: ‘TQObject’ has not been declared
qiomanager_p.moc: At global scope:
qiomanager_p.moc:164: error: no ‘bool Arts::QTimeWatch::qt_invoke(int,
QUObject*)’ member function declared in class ‘Arts::QTimeWatch’
qiomanager_p.moc: In member function ‘bool Arts::QTimeWatch::qt_invoke(int,
QUObject*)’:
qiomanager_p.moc:169: error: ‘TQObject’ has not been declared
qiomanager_p.moc: At global scope:
qiomanager_p.moc:174: error: no ‘bool Arts::QTimeWatch::qt_emit(int,
QUObject*)’ member function declared in class ‘Arts::QTimeWatch’
qiomanager_p.moc: In member function ‘bool Arts::QTimeWatch::qt_emit(int,
QUObject*)’:
qiomanager_p.moc:176: error: ‘TQObject’ has not been declared
qiomanager_p.moc: At global scope:
qiomanager_p.moc:180: error: no ‘bool Arts::QTimeWatch::qt_property(int,
int, QVariant*)’ member function declared in class ‘Arts::QTimeWatch’
qiomanager_p.moc: In member function ‘bool
Arts::QTimeWatch::qt_property(int, int, QVariant*)’:
qiomanager_p.moc:182: error: ‘TQObject’ has not been declared
qiomanager_p.moc: At global scope:
qiomanager_p.moc:185: error: no ‘bool
Arts::QTimeWatch::qt_static_property(QObject*, int, int, QVariant*)’ member
function declared in class ‘Arts::QTimeWatch’
make[2]: *** [qiomanager.lo] Error 1
make[2]: Leaving directory
`/home/tmarques/trinity/build/dependencies/arts/qtmcop'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/tmarques/trinity/build/dependencies/arts'
make: *** [all] Error 2
This is in a Gentoo based system where I'm trying to get some ebuilds done
to send to the kde-sunset overlay, where only 3.5.10 only resides now.
Best regards,
Tiago
What is the status of Trinity development? Other than an occasional cmake update in svn, I am seeing no movement anywhere, especially with the bugzilla.
Darrell
Hi all,
Just a quick update on the building of RPMs:
+ Removed Mandriva from the list of build targets. Matthew Dawkins
from Unity can take care of that :)
+ Removed Fedora 12 from the list of build targets. End of Life.
+ Removed openSUSE Factory Snapshot from the list of build targets.
Updates too often and that doesn't help development.
+ Building at standstill after autoconf263: Apparently the project
configuration isn't working very well.
I'm just waiting for the configuration to work again.
That way, I can get the newer autoconf out of the way for this older
but working one.
--
later, Robert Xu
