tde-devels October 2013

devels@trinitydesktop.org

6 participants
23 discussions

by Slávek Banko

Hello all, Tim, in a recent test of upgrade from TDE 3.5.13.2 to R14 smooth update was thwarted by conflicts in packages qt3 × tqt3. How should they be treated? Rename files to prevent conflicts? Or mark packages as conflicting / replacement to allow smooth upgrade? qt-x11-free-dbg: /usr/lib/debug/usr/bin/qm2ts qt-x11-free-dbg: /usr/lib/debug/usr/bin/mergetr qt-x11-free-dbg: /usr/lib/debug/usr/bin/msg2qm qt-x11-free-dbg: /usr/lib/debug/usr/bin/makeqpf qt-x11-free-dbg: /usr/lib/debug/usr/bin/qvfb qt-x11-free-dbg: /usr/lib/debug/usr/bin/createcw qt-x11-free-dbg: /usr/lib/debug/usr/bin/conv2ui qt3-apps-dev: /usr/lib/libeditor.a qt3-apps-dev: /usr/lib/libdesignercore.a qt3-apps-dev: /usr/lib/libqassistantclient.a qt3-apps-dev: /usr/lib/libqassistantclient.prl qt3-apps-dev: /usr/lib/libdesignercore.prl qt3-apps-dev: /usr/lib/libeditor.prl qt3-designer: /usr/bin/createcw qt3-designer: /usr/bin/conv2ui qt3-dev-tools-compat: /usr/bin/qm2ts qt3-dev-tools-compat: /usr/bin/mergetr qt3-dev-tools-compat: /usr/bin/msg2qm qt3-dev-tools-compat: /usr/bin/findtr qt3-dev-tools-compat: /usr/bin/qtrename140 qt3-dev-tools-compat: /usr/bin/qt20fix qt3-dev-tools-embedded: /usr/share/qvfb/pda_up.png qt3-dev-tools-embedded: /usr/share/qvfb/pda_down.png qt3-dev-tools-embedded: /usr/bin/makeqpf qt3-dev-tools-embedded: /usr/bin/qvfb qt3-doc: /usr/share/man/man3/QAccel.3qt.gz qt3-doc: /usr/share/man/man3/QAccessible.3qt.gz qt3-doc: /usr/share/man/man3/QAccessibleInterface.3qt.gz qt3-doc: /usr/share/man/man3/QAccessibleObject.3qt.gz qt3-doc: /usr/share/man/man3/QAction.3qt.gz ... -- Slavek

10 years, 4 months

Re: [trinity-devel] Compiling qt4-tqt-theme-engine

by Darrell Anderson

>you can check here (the log from the automated build system) >https://quickbuild.pearsoncomputing.net/~trinity/+archive/trinity- >nightly-builds/+build/133347 then click on the buildlog link. I need a sample build script, not a build log. :-) Darrell

10 years, 5 months

Still having problems with get-update and the nightly builds

by Keith Daniels

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

10 years, 5 months

Debian Nightly builds.

by Keith Daniels

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

10 years, 5 months

Re: [trinity-devel] Can't compile gtk3-tqt-engine

by Darrell Anderson

>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

10 years, 5 months

Compiling qt4-tqt-theme-engine

by Darrell Anderson

Would somebody please post a build script for qt4-tqt-theme-engine? Thanks. :-) Darrell

10 years, 5 months

Can't compile gtk3-tqt-engine

by Darrell Anderson

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

10 years, 5 months

Re: [trinity-devel] Fixed reaching fully activated state in screen saver

by Darrell Anderson

>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

10 years, 5 months

Re: [trinity-devel] Fixed reaching fully activated state in screen saver

by Darrell Anderson

>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

10 years, 5 months

Re: [trinity-devel] Fixed reaching fully activated state in screen saver

by Darrell Anderson

>>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? > >To test, I believe we have to rebuild tdebase with commit cbbc7ad0 > >and rebuild tdelibs with commits 9d76cb9 reversed and possibly >ba6b2079 reversed. > >That is, to test whether commit cbbc7ad0 resolves the NFS problem >as well, we need to restore the ability to autosuspend in >tdepowersave when $HOME is an NFS mount. Currently that ability is > >disabled in tdepowersave through commit 9d76cb9. > >What do you think? > >If, after testing NFS $HOME with commit cbbc7ad0, bug report 1623 >still exists to address the NFS mount problem. The proposed >solution in 1623 is to study the KDE powerdevil code, which uses >upower. I tried for a few hours trying to rebuild packages with reversed patches, in the hopes of restoring autosuspend when $HOME is a network mount. I gave up as there are too many changes for my C++ skills to overcome. We can't test whether commit cbbc7ad0 resolves the problem until the autosuspend feature is restored to tdepowersave when $HOME is a network mount. I really want to see autosuspend work with tdepowersave when $HOME is a network mount. If you can restore autosuspend when $HOME is a network mount, then I'd be happy to retest tdepowersave with commit cbbc7ad0. Darrell

10 years, 5 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels October 2013