All,
After resolving bug report 1704 I searched the Trinity source tree
for additional occurrences of 'kde-'. I found several instances of
some XDG mimetype references that have not been converted to TDE
nomenclature. The list:
x-kde-internaluid
x-kde-type
x-kde-cutselection
x-kde-urilist
A short list, yet I'm curious whether any of these instances could
be causing or are related to reported problems in Trinity.
To see these instances in context, grep tdebase, tdelibs, tdepim,
krusader, basket.
Should these instances be converted to x-tde-*?
Darrell
Hi all,
after commit 99b03be6 I have on a test machine in .xsession-errors many
such reports. Note that it is the testing machine, on which is now the
only active screen saver.
TQThreadInstance::finish: In TQThreadInstance::finish for thread 0x1508ad0
TQThreadInstance::finish: In TQThreadInstance::finish for thread 0x150b400
TQThreadInstance::finish: In TQThreadInstance::finish for thread 0x150afb0
TQThreadInstance::finish: In TQThreadInstance::finish for thread 0x1508af0
TQThreadInstance::finish: In TQThreadInstance::finish for thread 0x150b420
To this I have two questions:
1) How can such a report be useful when there is no knowing what
applications are affected?
2) Tim, why you use in such reports, a new lines with "\r"?
Thanks
Slavek
I had to shut down because of storms and just got back online where I could
test things again. I also accidentally deleted the previous email about
the problem. duh...
When I try to use "apt-get update" for the nightly build for Debian
wheezy--it still gives me this error message:
-----------------
Err http://ppa.quickbuild.pearsoncomputing.net wheezy/main Sources
404 Not Found
Fetched 127 kB in 8s (14.9 kB/s)
W: Failed to fetch http://ppa.quickbuild.pearsoncomuting
.net/trinity/trinity-nightly-build/debian/dists/wheezy/main/source/Sources
404 Not Found
-----------------
and dumps me out of apt-get.
I did some checking, and the "mirrorservice.org" link (which is where
"http://ppa.quickbuild.pearsoncomuting.net/trinity/" takes me):
http://www.mirrorservice.org/sites/trinitydesktop
.org/trinity/trinity-nightly-build-dependencies/ubuntu/dists
/wheezy/main/source/Source
Seems to be the link needed for Debian wheezy.
Keith
I am trying to install and test the nightly build.
I used these lines in my sources.list file:
-----------------
deb
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-de…
main
deb-src
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-de…
main
-----------------
and yes the other two lines are in there as well but I get dumped out
before apt-get runs them.
When I run apt-get update, everything runs fine until I get to the deb-src
line. At that point I get this error message:
-----------------
Err http://ppa.quickbuild.pearsoncomputing.net wheezy/main Sources
404 Not found
-----------------
and yes there is a space after .net above, which looks wrong to me.
The error message immediately dumps me out of apt.
Suggestions?
Keith
>I can send you my build log when I am on a TDE machine.
I need a sample build script more than a build log.
>Anyhow have you tried to remove that /tde from the command line
>and check if the package compiles?
I have no idea how to do that because I don't from where this
"/tde" is being defined.
Darrell
I need help compiling gtk3-tqt-engine. I run into the following
error:
gcc: error: /tde: No such file or directory
Here are my configuration options:
CFLAGS="$CPUOPT" \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QT_INCLUDE_DIR} \
--with-qt-libraries=${QT_LIB_DIR} \
$DEBUG_AUTOTOOL_OPT || exit 1
Here is the build log:
http://humanreadable.nfshost.com/misc/trinity-gtk3-tqt-engine-
pre_R14.0.0-i486-14.0_32_git_2763_1-build.log
The top of the build log shows the configuration variable
assignments.
I get the impression the build is looking for something like
/opt/trinity/include/tde, which does not exist on my system, nor
does /opt/trinity/include/trinity.
Thanks much. :-)
Darrell
>As I now noticed a problem with the necessity of user input (for
>interrupt the
>screen saver) you reported also in the bug report 1615. It is
>possible that
>bug fixed in commit cbbc7ad0 could be related also with NFS on
>/home?
>
>Can you try it?
I created a test patch to restore autosupend in tdepowersave when
$HOME is a network mount. I attached the patch to bug report 1623.
After rebuilding tdelibs with the test patch, commit cbbc7ad0 does
not resolve the problem of trying to autosuspend when $HOME is a
network mount.
Darrell
>To test the problem, which was fixed, it is simple:
>1) Make sure that you have enabled lock screen before suspend or
>standby.
>2) Set the screen saver run after a short time.
>3) Once the screensaver is activated, press button to go into
>suspend mode. Or
>set in tdepowersave autosuspend for a short time => a little
>longer than time
>to activate screen saver.
>4) Look, that nothing happens (for any length of time), until you
>cause an
>activity that will lead to stop screen saver.
>5) Only after stopping screen saver follows immediately switch
>into desired
>suspend mode.
I tested tdepowersave before applying the patch. In tdepowersave I
set the screensaver to 1 minute and autosuspend to 2 minutes.
Without the patch the following happens:
* After 1 minute the screensaver starts.
* After 2 minutes the suspend-to-ram 30 second timeout dialog does
not appear.
* Thereafter the laptop never automatically goes into suspend-to-
ram mode by itself.
* Any user action interrupts the screensaver.
* The laptop then goes into suspend-to-ram mode and the suspend-to-
ram 30 second timeout dialog never appears.
With the patch:
* After 1 minute the screensaver starts.
* After 2 minutes the suspend-to-ram 30 second timeout dialog
appears.
* After 30 seconds the laptop automatically goes into suspend-to-
ram mode by itself.
* Upon restoring from suspend-to-ram, the screensaver lock dialog
appears.
Well done!
Darrell