All,
While waiting on the rebuild of tdelibs and tdebase with full symbols, I was
poking around in kate and came up with another couple of fixes that are needed.
The first is a simple khelpcenter name change for Settings > Application >
File Selector. The khelpcenter name for this section is 'The Filesystem Browser
Page' instead of being the 'The File Selector Page'.
It looks like there was a name change somewhere along the way that was never
implemented in the help files. Looking at the other entries in the help file,
they correspond fairly closely to the settings dialog. Here are some other
changes for the help file needed just to dot [i]s and cross [t]s:
General - Meta-Data -> Meta-Information (who knew..)
crap - that's as far as I got - first time that happened - the whole desktop
locked. It had been running in virtualbox since April 17 without any issue:
18:03 alchemy:~/tde/tmp/tdebasep/patches> ps aux | grep -i virtual
david 14521 0.0 0.0 7788 828 pts/1 S+ 18:04 0:00 grep -i virtual
david 31843 0.0 0.5 458276 20300 ? Sl Apr17 2:13
/usr/lib/virtualbox/VirtualBox
david 31858 0.1 0.1 71364 4148 ? S Apr17 14:22
/usr/lib/virtualbox/VBoxXPCOMIPCD
david 31863 0.2 0.1 270528 6764 ? Sl Apr17 23:31
/usr/lib/virtualbox/VBoxSVC --auto-shutdown
david 31985 5.2 22.4 1502648 883052 ? Sl Apr17 609:27
/usr/lib/virtualbox/VirtualBox --comment Archlinux x86_64 --startvm
b0896a45-eafe-4029-8268-a0fd89cd7b4b --no-startvm-errormsgbox
The hard drive on virtualbox is thrashing away -- looks like I'll have to kill
something hard. Will report back...
--
David C. Rankin, J.D.,P.E.
Tim, All,
I've started a new thread to specifically look at the problem with sftp_kio
not obtaining the port number to open the connection for sftp without the user
manually providing it in the url. (eg: sftp://myhost:nonStdPort). This is part
of bug http://bugs.pearsoncomputing.net/show_bug.cgi?id=897
Tim's commit of GIT hash e72f492 fixed the ability of sftp to connect to
remote hosts, but if the remote host ssh runs on a port other than 22, the
connection fails due to sftp no longer getting the correct host/port pair from
either the system-wide config /etc/ssh/ssh_config or the user's ~/.ssh/config.
This worked correctly before the sftp bug was introduced and it continues to
work for fish://, but I cannot find where the config files are read. It appears
to be something read during ssh startup from the system-wide or user .ssh/config
file. That is hinted to in the fish/README file:
NOTE: From version 1.1.3 on, compression is no longer turned on auto-
matically. You have to specify it via ~/.ssh/config or wherever
your local ssh client reads its settings. The same goes for all other
connection parameters. OpenSSH for example has a powerful configuration
file syntax which lets you configure access differently for each host,
something I do not intend to duplicate. Read the ssh_config(5) man page
for details.
The variable in sftp associated with the port is 'mPort', but I cannot tell
where this could be set (yes, I know, just grep it, but somehow I'm getting lost
in whether this is piped or cached and read somewhere rather than just declared
and assigned) It appears to begin in ksshprocess.cpp with:
bool KSshProcess::setOptions(const SshOptList& opts) {
kdDebug(KSSHPROC) << "KSshProcess::setOptions()" << endl;
mArgs.clear();
SshOptListConstIterator it;
TQString cmd, subsystem;
mPassword = mUsername = mHost = TQString::null;
TQCString tmp;
for(it = opts.begin(); it != opts.end(); ++it) {
switch( (*it).opt ) {
<snip>
case SSH_PORT:
mArgs.append("-p");
tmp.setNum((*it).num);
mArgs.append(tmp);
mPort = (*it).num;
break;
<snip>
Also, both sftp:// and fish:// make use of an AuthInfo struct that references
a port, but I cannot figure out how to tell what this contains:
kio_sftp.cpp: // Setup AuthInfo for use with password caching and the
kio_sftp.cpp: AuthInfo info;
kio_sftp.cpp: info.url.setPort(mPort);
fish/fish.h: /** AuthInfo object used for logging in */
fish/fish.h: KIO::AuthInfo connectionAuth;
It is frustrating because it still works fine in fish, so we should just be
able to look there and find it, but it is apparently not that easy either...
Now regardless of how you look at it, the port information must be read from
either /etc/ssh/ssh_config or ~/.ssh/config before the ssh connection is opened
because that is the only place this information exists and it is imperative that
you have that connection before attempting to open a connection -- or the
connection will simply be refused and fail. So this is taking place in fish
somewhere and it was taking place in sftp somewhere as well -- the questions is
where??
What say the experts?? I've grepped and looked until I'm blue in the face and
I've exhausted what I can do.
--
David C. Rankin, J.D.,P.E.
Hello, Fedora 17 is about to be released, so I'm trying to build the
stable 3.5.13 version of TDE.
Fedora 17 ships with GCC 4.7.
I keep an eye on the ML and bugtracker to check the compiler-specific
issues.
Alas, I still have a FTBFS:
In file included from /opt/trinity/include/dcoptypes.h:25:0,
from
/home/albator/rpmbuild/BUILD/BUILD.fc17.x86_64/kdebase/tqt3integration/libqtkde/qtkde.cpp:25:
/opt/trinity/include/dcopref.h: In instantiation of
'DCOPArg::DCOPArg(const T&) [with T = long unsigned int]':
/opt/trinity/include/dcopref.h:459:2: required from 'DCOPReply
DCOPRef::call(const QCString&, const T1&) [with T1 = long unsigned int]'
/home/albator/rpmbuild/BUILD/BUILD.fc17.x86_64/kdebase/build/tqt3integration/utils/tqtkde_functions.cpp:30:95:
required from here
/opt/trinity/include/dcopref.h:145:27: error: 'dcopTypeName' was not
declared in this scope, and no declarations were found by
argument-dependent lookup at the point of instantiation [-fpermissive]
In file included from
/home/albator/rpmbuild/BUILD/BUILD.fc17.x86_64/kdebase/tqt3integration/libqtkde/qtkde.cpp:25:0:
/opt/trinity/include/dcoptypes.h:74:39: note: 'template<class T> const
char* dcopTypeName(const T&)' declared here, later in the translation unit
cd /home/albator/rpmbuild/BUILD/BUILD.fc17.x86_64/kdebase/build/kate/app
&& /usr/lib64/ccache/c++ -DHAVE_CONFIG_H -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -DQT_NO_ASCII_CAST
-DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h
-I/home/albator/rpmbuild/BUILD/BUILD.fc17.x86_64/kdebase/build/kate/app
-I/home/albator/rpmbuild/BUILD/BUILD.fc17.x86_64/kdebase/build
-I/opt/trinity/include -I/usr/lib64/qt-3.3/include
-I/opt/trinity/include/tqt -include tqt.h -o
CMakeFiles/kwrite.dir/kwrite_kdeinit_executable.cpp.o -c
/home/albator/rpmbuild/BUILD/BUILD.fc17.x86_64/kdebase/build/kate/app/kwrite_kdeinit_executable.cpp
make[2]: ***
[tqt3integration/libqtkde/CMakeFiles/qtkde-shared.dir/qtkde.cpp.o] Error 1
make[2]: Leaving directory
`/home/albator/rpmbuild/BUILD/BUILD.fc17.x86_64/kdebase/build'
make[1]: *** [tqt3integration/libqtkde/CMakeFiles/qtkde-shared.dir/all]
Error 2
Do you have any clue ?
(I repeat: this is on 3.5.13, not latest GIT)
Thanks
Francois
All,
When viewing a man page in konqueror (eg: man:/ssh_config) what controls
the default size of the font displayed?? Each time I view a man page, I end up
having to shrink the font size twice with:
View->Shrink Font (Ctrl+-)
I have compared the files in .trinity/share/config and I cannot find a
persistent change. (kdeglobals, konquerorrc, etc..). Is there are setting for
this that can be save in Settings->Save View Profile?
--
David C. Rankin, J.D.,P.E.
hello,
I'm back with a cleaned up version of the mac switching patch. It
incorporates problems noticed by Martin, as well as some cleaned up
code (aka the first time around I did things poorly :-P ). I have
attached it to this email and to the bug report.
Please test and let me know.
Also there is no longer a required patch for tdecore.
Calvin
Hello, I've noticed that the Debian/Ubuntu packaging for TDE
applications often adds a man page and a XPM icon.
Would'nt it be
better if these files were included with the source code, and
automatically installed by "make install" ?
It would avoid the effort
for each distribution packaging to deal with these files ...
Francois
I started TDM with useSAK=false, uinput not loaded:
* No Ctrl-Alt-Delete dialog
* Warning message in KControl to enable evdev/uinput
* Check box ghosted/disabled
I logged out. Loaded uinput. Restarted with init 4.
* No warning message in KControl
Enabling the check box (and Apply):
* tsak and tsak.lock appeared in /tmp/tdesocket-global/
Without logging out, disabling TSAK in KControl:
* tsak and tsak.lock disappeared
During this time I never closed the TDM module.
I re-enabled TSAK through KControl and logged out. Upon logging in:
* KControl check box was not enabled
* tdmrc showed useSAK=true
* tsak and tsak.lock appeared in /tmp/tdesocket-global/
After toggling the check box and selecting Apply, with the check box enabled, I toggled from the KControl TDM module to another KControl module and then immediately returned to the TDM module. The check box was not enabled.
To actually disable tsak I have to toggle the check box: "enable" and "disable" and then useSAK=false and the tsak and tsak.lock files disappeared.
I logged out with TSAK enabled (despite no check box). From a terminal I successfully killed all three tsak processes. Upon toggling back to TDM (Alt-F7) there was no Ctrl-Alt-Delete dialog. I logged in without no resistance. The tsak and tsak.lock files existed in /tmp/tdesocket-global because I did not delete them. The three tsak processes returned. I logged out and was greeted with the Ctrl-Alt-Delete dialog.
I repeated the process, but this time deleted the tsak and tsak.lock files too. I again logged in without resistance. This time there were no tsak processes running after I logged in. Apparently then tsak restarts if the FIFO files exist but does not restart if the FIFO files are deleted. useSAK=true the whole time. Upon logging out I was greeted with the Ctrl-Alt-Delete dialog. Therefore TDM must be restarting tsak.
I repeated this process including deleting the two FIFO files. I again logged in with no resistance. Then from the TDE menu I selected "Switch User." I was greeted with the Ctrl-Alt-Delete dialog.
Seems then whenever useSAK=true AND TDM receives direct focus that tsak is checked or restarted. TDM does not restart tsak with indirect focus as I accomplished.
This latest patch looks great. Much better housekeeping and when tsak is disabled in KControl, the effect is immediate and the housekeeping is immediate. Nice. :)
Summary:
* Glitch: KControl is not displaying the check box as enabled despite useSAK=true. Probably a forgotten or misplaced readEntry?
* Possible glitch: Seems TDM should restart tsak as soon as I logged in, despite my "malevolent" effort to disable tsak. However, as shown by the Switch User test, TDM immediately restarted tsak, and that probably is sufficient. Within the intent of how tsak should function (I don't know the specs), I'm unsure whether TDM should be polling the process list to immediately restart tsak when disabled as I circumvented. Seems to me that a user should not be able to do what I did. Even if I did not have a free console open, I could have accomplished the same with through SSH. Seems to me that as long as useSAK=true tsak should be a persistent little b-stard. :)
The desktop lockout bug remains (desktop icons and context menu disappear, can't logout), and the profile directories accrue like rabbits copulating, but this patch did not address those issues. :)
Darrell
While troubleshooting the various lock desktop bugs I noticed this message in my xsession log:
kded: KDE4 is running
Um, nope, not true.
The message is from tdelibs/kded/kded.cpp.
Some time back I updated a bunch of TDE environment variables. One of which was KDE_SESSION_VERSION -> TDE_SESSION_VERSION. Because of this incorrect message in my xsession log, I am wondering whether that variable should have been changed.
I grepped the entire source tree and found TDE_SESSION_VERSION referenced in only five apps:
applications/konversation/konversation/scripts/sysinfo:20
applications/kgtk-qt3/README:23
applications/tde-style-qtcurve/CMakeLists.txt.orig:105
applications/tde-style-qtcurve/CMakeLists.txt.orig:107
applications/tde-style-qtcurve/README:22
applications/tde-style-qtcurve/ChangeLog:176
applications/tde-style-qtcurve/ChangeLog:239
applications/tde-style-qtcurve/ChangeLog:274
applications/tde-style-qtcurve/ChangeLog:732
applications/tde-style-qtcurve/style/qtcurve.cpp:193
tdelibs/kded/kded.cpp:165
tdelibs/tdecore/kapplication.cpp:1337
tdelibs/tdecore/kapplication.cpp:1338
Should these references be KDE_SESSION_VERSION or TDE_SESSION_VERSION?
Tim, would you look and let me know?
Darrell
Tim, All,
Rebuilding tdebase today to check the ksshprocess fix, I ran into a build
failure I haven't seen before:
[ 29%] Building CXX object
kcontrol/hwmanager/CMakeFiles/kcm_hwmanager-module.dir/hwmanager.cpp.o
In file included from /build/src/tdebase/kcontrol/hwmanager/hwmanager.h:34:0,
from /build/src/tdebase/kcontrol/hwmanager/hwmanager.cpp:50:
/build/src/tdebase/kcontrol/hwmanager/devicepropsdlg.h:158:15: error:
'TDESystemHibernationMethod' was not declared in this scope
/build/src/tdebase/kcontrol/hwmanager/devicepropsdlg.h:158:74: error: wrong
number of template arguments (1, should be 2)
In file included from /opt/tqt3/include/ntqmime.h:46:0,
from /opt/tqt3/include/ntqevent.h:48,
from /opt/tqt3/include/ntqobject.h:48,
from /opt/tqt3/include/ntqwidget.h:46,
from /opt/tqt3/include/ntqbutton.h:45,
from /opt/tqt3/include/ntqcheckbox.h:45,
from /usr/include/tqt/tqcheckbox.h:32,
from /build/src/tdebase/kcontrol/hwmanager/hwmanager.cpp:21:
/opt/tqt3/include/ntqmap.h:594:7: error: provided for 'template<class Key,
class T> class TQMap'
In file included from /build/src/tdebase/kcontrol/hwmanager/hwmanager.h:34:0,
from /build/src/tdebase/kcontrol/hwmanager/hwmanager.cpp:50:
/build/src/tdebase/kcontrol/hwmanager/devicepropsdlg.h:158:95: error: invalid
type in declaration before ';' token
/build/src/tdebase/kcontrol/hwmanager/hwmanager.cpp: In member function 'void
TDEHWManager::populateTreeView()':
/build/src/tdebase/kcontrol/hwmanager/hwmanager.cpp:143:64: error:
'RootSystem' is not a member of 'TDEGenericDeviceType'
make[2]: ***
[kcontrol/hwmanager/CMakeFiles/kcm_hwmanager-module.dir/hwmanager.cpp.o] Error 1
make[1]: *** [kcontrol/hwmanager/CMakeFiles/kcm_hwmanager-module.dir/all] Error 2
make: *** [all] Error 2
Anybody mess with hwmanager lately??
--
David C. Rankin, J.D.,P.E.