Sype wont't open

Sype wont't open

[Peter H.]

Hi,

in slackware10 trying to open skype a program
for Internet telephony I get the following error:

relocation error: /usr/lib/qt/lib/libqt-mt.so.3: undefined symbol: 
XkbSetPerClientControls

and the program aborts.

How to resolve?

Thanks & regards
-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Sype wont't open

[Ray Olszewski]

At 01:50 PM 3/1/2005 +0800, Peter H. wrote:
>Hi,
>
>in slackware10 trying to open skype a program
>for Internet telephony I get the following error:
>
>relocation error: /usr/lib/qt/lib/libqt-mt.so.3: undefined symbol:
>XkbSetPerClientControls
>
>and the program aborts.
>
>How to resolve?
>
>Thanks & regards

Probably by getting a newer version of libqt-mt.so.3 . An undefined symbol 
usually means you have an older version of a library than the app was 
compiled against. (If you have the library's -dev package installed ... or 
whatever Slackware calls the packages with the headers files for various 
libraries ... you could check the headers for this function call, as a way 
of confirming my guess.)

In Debian-Sid, the current version of this package is 3.2.3-4 . The 
installed copy I have on a system here is timestamped last July, but I 
doubt my version is the current package. The Skype site says you need at 
least version 3.2 of this library.

I'm guessing that you got Skype from the Skype site, not as part of 
Slackware, probably the dynamic binary the site offers for download. The 
Skype site does also  list a version that has QT 3.2 compiled statically. I 
imagine that includes the libqt-mt part, so using that might be an 
effective workaround.

PS - Just to avoid misunderstanding ... libqt-mt.so.3 is normally a 
symlink, to something like this:

         /usr/lib/libqt-mt.so.3 -> libqt-mt.so.3.2.3

  You need to check the underlying library it is a symlink to to determine 
the version.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Sype wont't open

[Richard Adams]

On Tuesday 01 March 2005 07:21, Ray Olszewski wrote:
> PS - Just to avoid misunderstanding ... libqt-mt.so.3 is normally a
> symlink, to something like this:
>
>          /usr/lib/libqt-mt.so.3 -> libqt-mt.so.3.2.3
>
>   You need to check the underlying library it is a symlink to to determine
> the version.

Standard slack-10 has 3.3.2 installed in/

/usr/lib/qt which should be linked to qt-3.3.2
My slack-10 /etc/ld.so.conf looks like;

/usr/local/lib
/usr/X11R6/lib
/usr/i486-slackware-linux/lib
/opt/kde/lib
/usr/lib/qt/lib
/usr/lib/xine
/usr/lib
/lib

I found many questions about this error on www.google.com/linux.
A few answers all saying the same as i pointed Peter to in my other reply.

Regards Richard.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[Peter]

Thanks Ray

> At 01:50 PM 3/1/2005 +0800, Peter H. wrote:
> >Hi,
> >
> >in slackware10 trying to open skype a program
> >for Internet telephony I get the following error:
> >
> >relocation error: /usr/lib/qt/lib/libqt-mt.so.3: undefined symbol:
> >XkbSetPerClientControls
> >
> >and the program aborts.
> >
> >How to resolve?
> >
> >Thanks & regards

On Mon, 28 Feb 2005 22:21:39 -0800
Ray Olszewski <ray@comarre.com> wrote:
> 
> Probably by getting a newer version of libqt-mt.so.3 . An undefined symbol 
> usually means you have an older version of a library than the app was 
> compiled against. (If you have the library's -dev package installed ... or 
> whatever Slackware calls the packages with the headers files for various 
> libraries ... you could check the headers for this function call, as a way 
> of confirming my guess.)
> 
> In Debian-Sid, the current version of this package is 3.2.3-4 . The 
> installed copy I have on a system here is timestamped last July, but I 
> doubt my version is the current package. The Skype site says you need at 
> least version 3.2 of this library.

The version I have is 3.3.2 which I took from a Fedora 3 CD. In Fedora 2
Skype opens with this version which I copied to slackware.

> 
> I'm guessing that you got Skype from the Skype site, not as part of 
> Slackware, probably the dynamic binary the site offers for download. The 
> Skype site does also  list a version that has QT 3.2 compiled statically. I 
> imagine that includes the libqt-mt part, so using that might be an 
> effective workaround.

I tried both the dynamic and static version and I am getting the same error.

::$ ls -l  /usr/lib/qt/lib/libqt-mt.so.3
lrwxrwxrwx  1 root root 17 2004-10-29 09:24 /usr/lib/qt/lib/libqt-mt.so.3 ->
libqt-mt.so.3.3.2

> PS - Just to avoid misunderstanding ... libqt-mt.so.3 is normally a 
> symlink, to something like this:
> 
>          /usr/lib/libqt-mt.so.3 -> libqt-mt.so.3.2.3
> 
>   You need to check the underlying library it is a symlink to to determine 
> the version.
> 



-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Some users locked out of ssh and sftp?

[Eve Emshoff]

This isn't making sense to me. I have users logging in
via SSH to a redhat linux box using their network
username/password. I'm able to do it as are most
others, either locally or remotely. ie:

ssh -l eve <ipaddress>
or 
sftp eve@<ipaddress>

Thus far, I've run across 1 user who can't sftp OR
SSH. He's entirely locked out, despite having the
correct username and password. He appears to be set up
the same as well the others.

Is there a file or some such I should edit and/or
check to ensure he can get access? Anything to point
me to in terms of what I can check in that he may
*not* be set up the same as everyone else?

Thanks,
Eve

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Some users locked out of ssh and sftp?

[Ray Olszewski]

At 08:22 AM 3/1/2005 -0800, Eve Emshoff wrote:

>This isn't making sense to me. I have users logging in
>via SSH to a redhat linux box using their network
>username/password. I'm able to do it as are most
>others, either locally or remotely. ie:
>
>ssh -l eve <ipaddress>
>or
>sftp eve@<ipaddress>
>
>Thus far, I've run across 1 user who can't sftp OR
>SSH. He's entirely locked out, despite having the
>correct username and password. He appears to be set up
>the same as well the others.
>
>Is there a file or some such I should edit and/or
>check to ensure he can get access? Anything to point
>me to in terms of what I can check in that he may
>*not* be set up the same as everyone else?


Ok. First thing to do is get his password and make sure that *you* can ssh 
in using the same userid and password he is using. If you can, then you are 
either seeing some sort of user error or a problem associated with the site 
he is trying to connect *from*. (It's hard to come up with an example of 
the second, but I can imagine that an ISP might block traffic to port 22 
for some reason that does not occur to me ... although if "entirely locked 
out" means he is prompted for a password, then rejected, that example does 
not apply.)

(BTW, what do you mean by "network" username/password? Does this host use 
something other than the standard files /etc/passwd and /etc/shadow for 
userid and password? For example, is NIS involved somehow, or some LDAP 
gimmickry? If so, and if you decide to post a followup, please clarify this 
part.)

(Also, you say "most others" can log in. Is this just caution in reporting, 
or do you have other reports of unexplained failures?)

If you can log in and you want to explore the possibility that the problem 
is NOT user error, then to get help here you'll need to say more about the 
failure he is seeing.

Once you've verified for yourself that the userid/password combo does not 
work for you either, first check that this userid/password combo can do a 
normal shell login. If it can't, try (as root) chainging the password, to 
see if the problem is nothing more than the user having misremembered his 
password. Also check his entry in /etc/passwd to make sure a valid shell 
(/bin/bash, usually) is provided ... it has to be something listed in 
/etc/shells .

If the ssh problem remains after a password change (but the local login 
problem is fixed, or if local logins always worked so you skipped this 
step), the check the sshd config file (not sure where Red Hat keeps this, 
but maybe /etc/ssh/sshd_config ... that's where Debian puts it, anyway) and 
see if something there is interfering. For example, the entry

         PermitRootLogin no

blocks root logins via ssh. More generally, the entries

         AllowUsers

and

         DenyUsers

followed by a pattern or list can restrict which userids are allowed or 
forbidden to ssh in.

These are the easy examples. There is too much more to say ... read the man 
page for sshd_config if you want a general intro ... without a more 
specific indication of what the problem actually looks like (more than 
"entirely locked out", I mean), which could narrow the possibilities.

I've focused on ssh here because it is a bit easier to troubleshoot. But 
all the same considerations should apply to sftp as well ... that is, once 
you get ssh logins working, sftp should also work ... they use the same 
authentication mechanism and tunneling.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Some users locked out of ssh and sftp?

[Eric Bambach]

On Tuesday 01 March 2005 10:59 am, Ray Olszewski wrote:
> At 08:22 AM 3/1/2005 -0800, Eve Emshoff wrote:
> >This isn't making sense to me. I have users logging in
> >via SSH to a redhat linux box using their network
> >username/password. I'm able to do it as are most
> >others, either locally or remotely. ie:
> >
> >ssh -l eve <ipaddress>
> >or
> >sftp eve@<ipaddress>
> >
> >Thus far, I've run across 1 user who can't sftp OR
> >SSH. He's entirely locked out, despite having the
> >correct username and password. He appears to be set up
> >the same as well the others.
> >
> >Is there a file or some such I should edit and/or
> >check to ensure he can get access? Anything to point
> >me to in terms of what I can check in that he may
> >*not* be set up the same as everyone else?
>
> Ok. First thing to do is get his password and make sure that *you* can ssh
> in using the same userid and password he is using. If you can, then you are
> either seeing some sort of user error or a problem associated with the site
> he is trying to connect *from*. (It's hard to come up with an example of
> the second, but I can imagine that an ISP might block traffic to port 22
> for some reason that does not occur to me ... although if "entirely locked
> out" means he is prompted for a password, then rejected, that example does
> not apply.)
>
> (BTW, what do you mean by "network" username/password? Does this host use
> something other than the standard files /etc/passwd and /etc/shadow for
> userid and password? For example, is NIS involved somehow, or some LDAP
> gimmickry? If so, and if you decide to post a followup, please clarify this
> part.)
>
> (Also, you say "most others" can log in. Is this just caution in reporting,
> or do you have other reports of unexplained failures?)
>
> If you can log in and you want to explore the possibility that the problem
> is NOT user error, then to get help here you'll need to say more about the
> failure he is seeing.
>
> Once you've verified for yourself that the userid/password combo does not
> work for you either, first check that this userid/password combo can do a
> normal shell login. If it can't, try (as root) chainging the password, to
> see if the problem is nothing more than the user having misremembered his
> password. Also check his entry in /etc/passwd to make sure a valid shell
> (/bin/bash, usually) is provided ... it has to be something listed in
> /etc/shells .
>
> If the ssh problem remains after a password change (but the local login
> problem is fixed, or if local logins always worked so you skipped this
> step), the check the sshd config file (not sure where Red Hat keeps this,
> but maybe /etc/ssh/sshd_config ... that's where Debian puts it, anyway) and
> see if something there is interfering. For example, the entry
>
>          PermitRootLogin no
>
> blocks root logins via ssh. More generally, the entries
>
>          AllowUsers
>
> and
>
>          DenyUsers
>
> followed by a pattern or list can restrict which userids are allowed or
> forbidden to ssh in.
>
> These are the easy examples. There is too much more to say ... read the man
> page for sshd_config if you want a general intro ... without a more
> specific indication of what the problem actually looks like (more than
> "entirely locked out", I mean), which could narrow the possibilities.
>
> I've focused on ssh here because it is a bit easier to troubleshoot. But
> all the same considerations should apply to sftp as well ... that is, once
> you get ssh logins working, sftp should also work ... they use the same
> authentication mechanism and tunneling.

Besides all of Ray's perfectly good suggestions I have something to add.

Check the permissions on his/her ~/.ssh directory. If the permissions somehow 
became world write/readable ssh will refuse to log that person in. Check the 
log files too! If ssh is logging its failures it can tell you a whole lot!

If you can, try running ssh on an alternate port in debugging mode and logging 
in as that user. That way you can see where/why ssh is failing.

However, try to log the user in locally first because if its a local problem 
then fiddling with SSH wont do anything. Also if its a local problem and you 
fix it then SSH should work itself out.

-- 
----------------------------------------
--EB

> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?

The latitude and longtitude of the bios writers current position, and
a ballistic missile.

                --Alan Cox LKML-December 08,2000 

----------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Thought I was mounting drive correctly, but backup failed

[Eve Atley]

My setup: 
1 Linux RedHat 9 kernel
1 Windows 2000 backup machine with 2 firewire hot-swap drives attached
(named 'backup')
	- firewire drives have been partitioned and ready to roll
	- drives are lettered/named, respectively, e/Granite1, and
f/Granite2
	- linuxadmin/password set up on system to allow for the following...

My procedure:
mount -t smbfs -o username=linuxadmin,password=password,workgroup=wowcorp
//backup/e /mnt/backup

/mnt/backup directory's definitely created. When I use the above command, I
return no errors, and the drive is empty so I thought it was mounting.
However, when I checked the backup logs, the logs were empty...and remount
shows no files were copied over from the script I've set up.

It doesn't appear to be the backup script that is the issue. Is there
something amiss in my setup? Let me know if you need more info (I'm sure you
will!).

Thanks,
Eve


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Thought I was mounting drive correctly, but backup failed

[Ray Olszewski]

At 02:20 PM 3/11/2005 -0500, Eve Atley wrote:

>My setup:
>1 Linux RedHat 9 kernel

I don't know if this part of the info matters, but identifying a kernel 
this way is almost useless. More useful is to report the output of "uname 
-a" and mention if you are using a stock or locally-compiled version of the 
kernel.

>1 Windows 2000 backup machine with 2 firewire hot-swap drives attached
>(named 'backup')
>         - firewire drives have been partitioned and ready to roll
>         - drives are lettered/named, respectively, e/Granite1, and
>f/Granite2
>         - linuxadmin/password set up on system to allow for the following...
>
>My procedure:
>mount -t smbfs -o username=linuxadmin,password=password,workgroup=wowcorp
>//backup/e /mnt/backup
>
>/mnt/backup directory's definitely created.

This looks right, at least from the Linux end of it (I don't know if 
Windows properly maps //backup/e to e/Granite1 or not, but I'd expect to 
see an error message from the Linux end if not.)

>When I use the above command, I
>return no errors, and the drive is empty so I thought it was mounting.

What does "df" think? (It knows more than you do about these things.) Does 
the drive show up there and is it the right size to be the intended target 
filesystem?

>However, when I checked the backup logs, the logs were empty...and remount
>shows no files were copied over from the script I've set up.

I wonder if there is a permissions problem of some sort. After you smbmount 
the filesystem this way, are you able to cp one or more files to it 
manually? If yes, can you do so as whatever userid the script runs from? If 
no, can you do so as root?

>It doesn't appear to be the backup script that is the issue.

We've discussed this style point before, I think, but whenever I read a 
phrasing like "doesn't appear to be" in a trouble report, I see 
uncertainty, not assurance, and my suspiciousness gene kicks in. How did 
you form this belief?

>Is there
>something amiss in my setup?

If cp'ing by hand works, then you need to examine your script with a bit 
more skepticism. (BTW, does the script detect and log cp'ing failures? Or 
are its STDOUT and STDERR routed to /dev/null or someplace equally useless?)

If it doesn't work, then you need to check both the permissions on the 
local mount point ("ls -l /mnt/backup" and on the remote system (not sure 
how to do this, since that's a Windows host) to see that you have 
("linuxadmin" has, that is) write permission.

>Let me know if you need more info (I'm sure you
>will!).

My comments above should serve to tell you what we need to see, with the 
exact choices depending on how you answer the questions I asked. As always, 
never summarize results, report them word for word.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: Thought I was mounting drive correctly, but backup failed

[Eve Atley]

Hi Ray, thanks for your usual excellent tips. Here's what I've done...

1. mount -t smbfs -o username=linuxadmin,password=password,workgroup=wowcorp
//backup/e /mnt/backup
Result: no errors

2. df shows:
/dev/hda2             37334192   5252668  30185052  15% /
/dev/hda1               101089     29129     66741  31% /boot
/dev/hdb1             57669728  42343604  12396676  78% /home
none                    256800         0    256800   0% /dev/shm
//backup/e           120623104     69632 120553472   1% /mnt/backup

So, it appears to be mounting...with correct partition size.

3. cp mount_test.txt /mnt/backup
Result: mount_test.txt resides on /mnt/backup

>If yes, can you do so as whatever userid the script runs from? If 
>no, can you do so as root?

Well, I logged in via ssh as root, mounted the drive, and copied the file.

>If cp'ing by hand works, then you need to examine your script with a bit 
>more skepticism. (BTW, does the script detect and log cp'ing failures? Or 
>are its STDOUT and STDERR routed to /dev/null or someplace equally
useless?)

Well, I say it's not the script's fault because it all worked previously. :)
Linuxadmin is set up as an administrator, so should have full read/write
capabilities. At this point, the backup script shows:

mount -t smbfs -o username=linuxadmin,password=password,workgroup=wowcorp
//backup/e /mnt/backup &>/root/backup_scripts/logs/`date
+"MOUNT-%y-%m-%d.log"`
if [ -f /mnt/backup/connected ]; then
        rm -rf /mnt/backup/`date +"%A/"`
        mkdir /mnt/backup/`date +"%A/"`
        cp -r /home/shared/* /mnt/backup/`date +"%A/"`
1>/mnt/backup/logs/`date
+"DAILY-%y-%m-%d.log"` 2>/mnt/backup/logs/`date +"DAILY-%y-%m-%d.err"`
        umount /mnt/backup  &>/root/backup_scripts/logs/`date
+"MOUNT-%y-%m-%d.log"`
fi


----------------

The generated log appears completely empty, whereas the day before it
indicated:
SMB connection failed
15538: session setup failed: ERRDOS - ERRnoaccess (Access denied.)
...since I had nothing set up at that time.


- Eve


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: Thought I was mounting drive correctly, but backup failed

[Ray Olszewski]

I've made several suggestions inline. But skip to the last one first, since 
it's my best guess about what your actual problem is.

At 05:35 PM 3/11/2005 -0500, Eve Atley wrote:

>Hi Ray, thanks for your usual excellent tips. Here's what I've done...
>
>1. mount -t smbfs -o username=linuxadmin,password=password,workgroup=wowcorp
>//backup/e /mnt/backup
>Result: no errors
>
>2. df shows:
>/dev/hda2             37334192   5252668  30185052  15% /
>/dev/hda1               101089     29129     66741  31% /boot
>/dev/hdb1             57669728  42343604  12396676  78% /home
>none                    256800         0    256800   0% /dev/shm
>//backup/e           120623104     69632 120553472   1% /mnt/backup
>
>So, it appears to be mounting...with correct partition size.

I agree. This part looks good.

>3. cp mount_test.txt /mnt/backup
>Result: mount_test.txt resides on /mnt/backup
>
> >If yes, can you do so as whatever userid the script runs from? If
> >no, can you do so as root?
>
>Well, I logged in via ssh as root, mounted the drive, and copied the file.

I don't know if you answered the question or not, since I don't know what 
userid the script runs under (I'm guessing that it is a daily cron job, but 
I can't guess the uid). But if the script runs under a userid other than 
root, it could still be a problem at the Linux end. So please check --

         (a) permissions on this mounted directory as Linux sees them. That 
is, what does "ls -l /mnt/backup" report?

         (b) if you can cp a file to this directory as the userid that runs 
the script.
> >If cp'ing by hand works, then you need to examine your script with a bit
> >more skepticism. (BTW, does the script detect and log cp'ing failures? Or
> >are its STDOUT and STDERR routed to /dev/null or someplace equally
>useless?)
>
>Well, I say it's not the script's fault because it all worked previously. :)
>Linuxadmin is set up as an administrator, so should have full read/write
>capabilities.

Since the term "administrator" is not used on Linux and Unix systems, I 
assume you refer here to privileges on the Windows end. I'll have to take 
your word for that part. But whether permissions are OK on the Linux end is 
not sorted out by this.

>  At this point, the backup script shows:

>mount -t smbfs -o username=linuxadmin,password=password,workgroup=wowcorp
>//backup/e /mnt/backup &>/root/backup_scripts/logs/`date
>+"MOUNT-%y-%m-%d.log"`
>if [ -f /mnt/backup/connected ]; then
>         rm -rf /mnt/backup/`date +"%A/"`
>         mkdir /mnt/backup/`date +"%A/"`
>         cp -r /home/shared/* /mnt/backup/`date +"%A/"`
>1>/mnt/backup/logs/`date
>+"DAILY-%y-%m-%d.log"` 2>/mnt/backup/logs/`date +"DAILY-%y-%m-%d.err"`
>         umount /mnt/backup  &>/root/backup_scripts/logs/`date
>+"MOUNT-%y-%m-%d.log"`
>fi

Hmmm ... have you created (touch'ed) the file /mnt/backup/connected on the 
backup drive? If not, the script is failing to perform the backup because 
the conditional in its if statement  (if [ -f /mnt/backup/connected ];) 
fails. And the script has no instructions for what to do if the if test 
fails (no "else", that is), so nothing would get logged in this case.

>----------------
>
>The generated log appears completely empty, whereas the day before it
>indicated:
>SMB connection failed
>15538: session setup failed: ERRDOS - ERRnoaccess (Access denied.)
>...since I had nothing set up at that time.
>
>
>- Eve

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: Thought I was mounting drive correctly, but backup failed

[Eve Atley]

>Hmmm ... have you created (touch'ed) the file /mnt/backup/connected on the 
>backup drive? If not, the script is failing to perform the backup because 
>the conditional in its if statement  (if [ -f /mnt/backup/connected ];) 
>fails. And the script has no instructions for what to do if the if test 
>fails (no "else", that is), so nothing would get logged in this case.

Oh my! Let's go with this one first. :) I copied the connected file over
from the old machine and I'll see if that solves my problems. :)

- Eve


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: Some users locked out of ssh and sftp?

[Eve Atley]

Ok, let me see if I can narrow the problem down a bit. Using the GUI panel,
I first create a user and password combination - let's use jean / password1.
This autocreates a user home directory (jean) and gives them a bash shell
(in this case). 

Then, via terminal, I 'useradd jean'. Following this, I 'smbpasswd -a jean'
and enter the password as prompted (twice). I return to the GUI and uncheck
all account expiration, just in case. I then set the user up with access to
the groups she should be permitted to (via the GUI).

Now, I'm set up this way (eve), as is user Keyur (keyur) and Gagan (gagan).
I just set up Jean (jean) this way. Gagan and I can log in; neither of us
have a .ssh file located anywhere that we know of, for ourselves. Keyur and
Jean cannot, they are prompted for a session password. Gagan and I never are
prompted for such.

We log in using Winscp3. Locally, as an example, we put in address
192.168.10.x, port 22, username: jean, password: password1. For most of us
(I give only 3 examples here), the login is successful. No session password
needed.

> (BTW, what do you mean by "network" username/password? Does this host 

We have it set up so that once the user is logged into his computer with
his/her user/pass combo, then accessing the network via samba uses the same
credentials. Therefore, user/pass combo is same on Windows logon as well as
Samba.

> (Also, you say "most others" can log in. Is this just caution in 
> reporting, or do you have other reports of unexplained failures?)

See above.

>Check the permissions on his/her ~/.ssh directory. If the permissions
somehow 

Again, I see no .ssh directory, at least not for /home/keyur, /home/gagan,
/home/jean or /home/eve.


- Eve

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Some users locked out of ssh and sftp?

[SOTL]

Had the same problem. My problem was solved when I install all the packages 
required for log in in all the computers. Suggest you check upor packages.

PS All packages REQUIRED for login DO NOT have SSH as part of their name. 
Sorry can not remember what the additional names are.

Frank

On Friday 11 March 2005 17:56, Eve Atley wrote:
> Ok, let me see if I can narrow the problem down a bit. Using the GUI panel,
> I first create a user and password combination - let's use jean /
> password1. This autocreates a user home directory (jean) and gives them a
> bash shell (in this case).
>
> Then, via terminal, I 'useradd jean'. Following this, I 'smbpasswd -a jean'
> and enter the password as prompted (twice). I return to the GUI and uncheck
> all account expiration, just in case. I then set the user up with access to
> the groups she should be permitted to (via the GUI).
>
> Now, I'm set up this way (eve), as is user Keyur (keyur) and Gagan (gagan).
> I just set up Jean (jean) this way. Gagan and I can log in; neither of us
> have a .ssh file located anywhere that we know of, for ourselves. Keyur and
> Jean cannot, they are prompted for a session password. Gagan and I never
> are prompted for such.
>
> We log in using Winscp3. Locally, as an example, we put in address
> 192.168.10.x, port 22, username: jean, password: password1. For most of us
> (I give only 3 examples here), the login is successful. No session password
> needed.
>
> > (BTW, what do you mean by "network" username/password? Does this host
>
> We have it set up so that once the user is logged into his computer with
> his/her user/pass combo, then accessing the network via samba uses the same
> credentials. Therefore, user/pass combo is same on Windows logon as well as
> Samba.
>
> > (Also, you say "most others" can log in. Is this just caution in
> > reporting, or do you have other reports of unexplained failures?)
>
> See above.
>
> >Check the permissions on his/her ~/.ssh directory. If the permissions
>
> somehow
>
> Again, I see no .ssh directory, at least not for /home/keyur, /home/gagan,
> /home/jean or /home/eve.
>
>
> - Eve
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Some users locked out of ssh and sftp?

[SOTL]

Hi All

I just spent half a day trying to fix this problem on the wrong computer. In 
justification of the time I was not using SSH directly but fish which uses 
SSH so I was not getting the error messages. Once I tried it connecting using 
SSH I fixed the problem in 5 minutes

In Linux SSH has a computer verification file for computers that have 
permission to log in at /home/<user>/.ssh/known_hosts:2

Explanation. I trashed the HD in one box [a test box with no data in it]. 
After re installation of HD, & configuration I found that I could SSH from 
the  new system but could not SSH from computers which had previously 
connected to the box with the new HD and system. 

I removed contents of above fine saved and was able to immediately log-in.

Hope this helps.

Frank

On Friday 11 March 2005 18:27, SOTL wrote:
> Had the same problem. My problem was solved when I install all the packages
> required for log in in all the computers. Suggest you check upor packages.
>
> PS All packages REQUIRED for login DO NOT have SSH as part of their name.
> Sorry can not remember what the additional names are.
>
> Frank
>
> On Friday 11 March 2005 17:56, Eve Atley wrote:
> > Ok, let me see if I can narrow the problem down a bit. Using the GUI
> > panel, I first create a user and password combination - let's use jean /
> > password1. This autocreates a user home directory (jean) and gives them a
> > bash shell (in this case).
> >
> > Then, via terminal, I 'useradd jean'. Following this, I 'smbpasswd -a
> > jean' and enter the password as prompted (twice). I return to the GUI and
> > uncheck all account expiration, just in case. I then set the user up with
> > access to the groups she should be permitted to (via the GUI).
> >
> > Now, I'm set up this way (eve), as is user Keyur (keyur) and Gagan
> > (gagan). I just set up Jean (jean) this way. Gagan and I can log in;
> > neither of us have a .ssh file located anywhere that we know of, for
> > ourselves. Keyur and Jean cannot, they are prompted for a session
> > password. Gagan and I never are prompted for such.
> >
> > We log in using Winscp3. Locally, as an example, we put in address
> > 192.168.10.x, port 22, username: jean, password: password1. For most of
> > us (I give only 3 examples here), the login is successful. No session
> > password needed.
> >
> > > (BTW, what do you mean by "network" username/password? Does this host
> >
> > We have it set up so that once the user is logged into his computer with
> > his/her user/pass combo, then accessing the network via samba uses the
> > same credentials. Therefore, user/pass combo is same on Windows logon as
> > well as Samba.
> >
> > > (Also, you say "most others" can log in. Is this just caution in
> > > reporting, or do you have other reports of unexplained failures?)
> >
> > See above.
> >
> > >Check the permissions on his/her ~/.ssh directory. If the permissions
> >
> > somehow
> >
> > Again, I see no .ssh directory, at least not for /home/keyur,
> > /home/gagan, /home/jean or /home/eve.
> >
> >
> > - Eve
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-newbie"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.linux-learn.org/faqs
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: Some users locked out of ssh and sftp?

[Ray Olszewski]

Yeah, Eve, details help a lot. My memory of your earlier postings on this 
is a bit hazy, so I may be dragging you through something you've already 
tried. If so, I'm sorry. But based on the fresh info, I have a couple of 
suggestions, provided below.

At 05:56 PM 3/11/2005 -0500, Eve Atley wrote:

>Ok, let me see if I can narrow the problem down a bit. Using the GUI panel,
>I first create a user and password combination - let's use jean / password1.
>This autocreates a user home directory (jean) and gives them a bash shell
>(in this case).
>
>Then, via terminal, I 'useradd jean'. Following this, I 'smbpasswd -a jean'
>and enter the password as prompted (twice). I return to the GUI and uncheck
>all account expiration, just in case. I then set the user up with access to
>the groups she should be permitted to (via the GUI).
>
>Now, I'm set up this way (eve), as is user Keyur (keyur) and Gagan (gagan).
>I just set up Jean (jean) this way. Gagan and I can log in; neither of us
>have a .ssh file located anywhere that we know of, for ourselves.

See the end of the message on this bit.

>Keyur and
>Jean cannot, they are prompted for a session password. Gagan and I never are
>prompted for such.

OK. Now though you call it a "session" password, this is just the same 
password that the user has already entered in as "password1" (from below). 
Right?

As you've described the test, it sounds like a different client-side host 
(Windows workstation) is uniquely associated with each userid. So you want 
to figure out if the problem is associated with a subset of userids or with 
a subset of hosts. See if you can, from a workstation that logs in eve 
without a password request, log in as jean without getting a follow-on 
password prompt. If yes, the problem is with client configuration, not 
server configuration or account creation.

I just downloaded Winscp3 and tested it out. (Nice app, BTW ... nicer 
interface than the putty scp app I've occasionally used.) What I found is ...

         ... if I enter the correct password in the password box, then it 
logs me on without any fuss.

         ... if I enter the wrong password in the password box, then it 
prompts me for a password (probably what you call the "session" password).

So the first thing to do is verify that the passwords entered into the 
Winscp3 "Session" dialog is correct, not mistyped. Windows users sometimes 
forget, for example, that Unix-style passwords are case-sensitive ... since 
so much on Windows systems is not case sensitive.

Second, still in Winscp3, check in Advanced Options->Authentication and 
make sure "Attempt keyboard-active authentication" and "Respond with 
password to the first prompt" are both checked.

Third, still in Winscp3, check in SSH to make sure SSH2 is the only, or at 
least the preferred, connection method.

Furth, check for any other differences in Winscp3 setup. I didn't see any 
other promising candidates when I looked at the app, but you never know (at 
least not when you've used the app only for 10 minutes, as I have).

Last, I've assumed we are in all cases talking about connecting to the same 
server. You certainly seem to be saying that.  But if I've misunderstood 
you ... might there be differences in the sshd implementations between 
servers that do and do not prompt for the password? This could be an SSH1 
versus SSH2 issue, for example.

>We log in using Winscp3. Locally, as an example, we put in address
>192.168.10.x, port 22, username: jean, password: password1. For most of us
>(I give only 3 examples here), the login is successful. No session password
>needed.
>
> > (BTW, what do you mean by "network" username/password? Does this host
>
>We have it set up so that once the user is logged into his computer with
>his/her user/pass combo, then accessing the network via samba uses the same
>credentials. Therefore, user/pass combo is same on Windows logon as well as
>Samba.
>
> > (Also, you say "most others" can log in. Is this just caution in
> > reporting, or do you have other reports of unexplained failures?)
>
>See above.
>
> >Check the permissions on his/her ~/.ssh directory. If the permissions
>somehow
>
>Again, I see no .ssh directory, at least not for /home/keyur, /home/gagan,
>/home/jean or /home/eve.

To see directories that begin with a . character (other than . and ..), you 
have to use the -a flag with ls. But on my systems, these directories only 
hold host keys for systems the account connects to (not from), so you may 
not have them (I don't know, since I don't use user keys to authenticate, 
and I don''t recall where sshd puts them, though the man page seems to say 
they go in  $HOME/.ssh/authorized_keys).


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: Some users locked out of ssh and sftp?

[Eve Atley]

>>OK. Now though you call it a "session" password, this is just the same 
>>password that the user has already entered in as "password1" (from below).

>>Right?

In this case, they should be able to log in as, say, jean/password1, as you
say. This is entered in the winscp fields, ie. testing locally:

Host name: 192.168.10.57
Port number: 22
User name: jean
Password: password1

>         ... if I enter the correct password in the password box, then it 
>logs me on without any fuss.

Yeah, that's how it *should* work. :)

>         ... if I enter the wrong password in the password box, then it 
>prompts me for a password (probably what you call the "session" password).

Still prompts me, no matter what I enter, right or wrong. I have reset the
password on jean several times from the Linux box; then tried reentering the
password each time and it still prompts me and denies jean access.

>Second, still in Winscp3, check in Advanced Options->Authentication and 
>make sure "Attempt keyboard-active authentication" and "Respond with 
>password to the first prompt" are both checked.

Checked.

>Third, still in Winscp3, check in SSH to make sure SSH2 is the only, or at 
>least the preferred, connection method.

Done.

>Last, I've assumed we are in all cases talking about connecting to the same

>server. You certainly seem to be saying that.  But if I've misunderstood 
>you ... might there be differences in the sshd implementations between 
>servers that do and do not prompt for the password? This could be an SSH1 
>versus SSH2 issue, for example.

My test environment is simply this. I try connecting to a variety of users
from my own machine, to the same machine in all cases. So, whereas
credentials for 'eve' work, credentials for 'jean' do not. So it's not a
client setup issue that I can see...quite possibly the way the user is set
up, though how so I can't place.

Now, I wondered if the known_hosts problem may clue me into something, but
here's my return when I locate known_hosts:
/root/.ssh/known_hosts
/home/kolt/.ssh/known_hosts
/home/eve/.ssh/known_hosts
/home/edwin/.ssh/known_hosts
/home/navneet/.ssh/known_hosts
/home/vaibhav/.ssh/known_hosts

This translates to: eve can log in as well as all the others shown
here...but so can Gagan, who has no such known_hosts file.

So I tried copying one of these known_hosts to /home/keyur/.ssh/known_hosts.
When I next try a locate for known_hosts, keyur never actually appears in
the listing.
/root/.ssh/known_hosts
/home/kolt/.ssh/known_hosts
/home/eve/.ssh/known_hosts
/home/edwin/.ssh/known_hosts
/home/navneet/.ssh/known_hosts
/home/vaibhav/.ssh/known_hosts
...even when ensuring permissions are set the same as Gagan.


- Eve




-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: Some users locked out of ssh and sftp?

[Ray Olszewski]

I have to think about the message in general, but I wanted to correct one 
small error in your procedure right away.

At 02:17 PM 3/14/2005 -0500, Eve Atley wrote:
[...]
>So I tried copying one of these known_hosts to /home/keyur/.ssh/known_hosts.
>When I next try a locate for known_hosts, keyur never actually appears in
>the listing.

The command "locate" checks a database on the system and, by taking that 
approach, can respond VERY quickly. But the database is updated as a batch 
job ("updatedb") run through cron, usually whenever cron.daily runs 
(between 6 and 7 AM local time is typical ... mine runs at 6:25). So right 
after you make a change, it will not show up in "locate" searches.

To detect new files immediately after creation, use the "find" command 
instead. It actually walks the filesystem tree to find matches (so is 
slower but more current). Example usage:

         find / -name known_hosts

The man page is pretty clear on usage options; the only tricky thing is the 
need, sometimes, to enclose wildcarded filespecs in quotes.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: Some users locked out of ssh and sftp?

[Eve Atley]

Thanks for the info on locate; I didn't realize it was database-driven.
More details on the SSH issue here. I checked the session log for WinSCP and
here are the results. 
I will include here a non-working session (keyur@local) as well as a working
session (gagan@local).


NON-WORKING
--------------------------------

. 2005-03-14 16:48:22.233
--------------------------------------------------------------------------
. 2005-03-14 16:48:22.233 WinSCP Version 3.7.3 (Build 265) (OS 5.0.2195
Service Pack 4)
. 2005-03-14 16:48:22.233 Login time: Monday, March 14, 2005 4:48:22 PM
. 2005-03-14 16:48:22.233
--------------------------------------------------------------------------
. 2005-03-14 16:48:22.233 Session name: keyur@local
. 2005-03-14 16:48:22.233 Host name: 192.168.10.57 (Port: 22)
. 2005-03-14 16:48:22.233 User name: keyur (Password: Yes, Key file: No)
. 2005-03-14 16:48:22.233 Transfer Protocol: SFTP (SCP)
. 2005-03-14 16:48:22.233 SSH protocol version: 2; Compression: No
. 2005-03-14 16:48:22.233 Agent forwarding: No; TIS/CryptoCard: No; KI: Yes;
GSSAPI: No
. 2005-03-14 16:48:22.233 Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. 2005-03-14 16:48:22.233 Ping type: -, Ping interval: 30 sec; Timeout: 15
sec
. 2005-03-14 16:48:22.233 SSH Bugs: -,-,-,-,-,-,-,-
. 2005-03-14 16:48:22.243 SFTP Bugs: -,-
. 2005-03-14 16:48:22.243 Proxy: none
. 2005-03-14 16:48:22.243 Return code variable: Autodetect; Lookup user
groups: Yes
. 2005-03-14 16:48:22.243 Shell: default, EOL: 0
. 2005-03-14 16:48:22.243 Local directory: default, Remote directory: home,
Update: No, Cache: Yes
. 2005-03-14 16:48:22.243 Cache directory changes: Yes, Permanent: Yes
. 2005-03-14 16:48:22.243 Clear aliases: Yes, Unset nat.vars: Yes, Resolve
symlinks: Yes
. 2005-03-14 16:48:22.243 Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. 2005-03-14 16:48:22.243
--------------------------------------------------------------------------
. 2005-03-14 16:48:22.243 Looking up host "192.168.10.57"
. 2005-03-14 16:48:22.243 Connecting to 192.168.10.57 port 22
. 2005-03-14 16:48:22.253 Server version: SSH-1.99-OpenSSH_3.5p1
. 2005-03-14 16:48:22.253 We claim version: SSH-2.0-WinSCP_release_3.7.3
. 2005-03-14 16:48:22.253 Using SSH protocol version 2
. 2005-03-14 16:48:22.263 Doing Diffie-Hellman group exchange
. 2005-03-14 16:48:22.303 Doing Diffie-Hellman key exchange
. 2005-03-14 16:48:25.127 Host key fingerprint is:
. 2005-03-14 16:48:25.127 ssh-rsa 1024
70:ea:61:3a:cb:96:f9:02:3b:99:4f:81:da:93:a1:06
. 2005-03-14 16:48:25.137 Initialised AES-256 client->server encryption
. 2005-03-14 16:48:25.137 Initialised HMAC-SHA1 client->server MAC algorithm
. 2005-03-14 16:48:25.137 Initialised AES-256 server->client encryption
. 2005-03-14 16:48:25.137 Initialised HMAC-SHA1 server->client MAC algorithm
! 2005-03-14 16:48:25.137 Using username "keyur".
. 2005-03-14 16:48:25.147 Keyboard-interactive authentication refused
. 2005-03-14 16:48:25.147 Session password prompt (keyur@192.168.10.57's
password: )
. 2005-03-14 16:48:25.147 Using stored password.
. 2005-03-14 16:48:25.147 Sent password
! 2005-03-14 16:48:27.501 Access denied
. 2005-03-14 16:48:27.501 Access denied
. 2005-03-14 16:48:27.501 Session password prompt (keyur@192.168.10.57's
password: )
. 2005-03-14 16:48:27.501 Asking user for password.
. 2005-03-14 16:48:28.462 Sent password
! 2005-03-14 16:48:30.816 Access denied
. 2005-03-14 16:48:30.816 Access denied
. 2005-03-14 16:48:30.816 Session password prompt (keyur@192.168.10.57's
password: )
. 2005-03-14 16:48:30.816 Asking user for password.
. 2005-03-14 16:48:31.527 Unable to authenticate
. 2005-03-14 16:48:31.527 Attempt to close connection due to fatal
exception:
* 2005-03-14 16:48:31.527 Unable to authenticate
. 2005-03-14 16:48:31.527 Closing connection.
* 2005-03-14 16:48:31.537 (ESshFatal) Authentication failed.
* 2005-03-14 16:48:31.537 Authentication log (see session log for details):
* 2005-03-14 16:48:31.537 Using username "keyur".
* 2005-03-14 16:48:31.537 Access denied
* 2005-03-14 16:48:31.537 Access denied
* 2005-03-14 16:48:31.537 
* 2005-03-14 16:48:31.537 Unable to authenticate

WORKING
--------------

. 2005-03-14 16:52:19.965
--------------------------------------------------------------------------
. 2005-03-14 16:52:20.005 WinSCP Version 3.7.3 (Build 265) (OS 5.0.2195
Service Pack 4)
. 2005-03-14 16:52:20.005 Login time: Monday, March 14, 2005 4:52:20 PM
. 2005-03-14 16:52:20.005
--------------------------------------------------------------------------
. 2005-03-14 16:52:20.005 Session name: gagan@local
. 2005-03-14 16:52:20.005 Host name: 192.168.10.57 (Port: 22)
. 2005-03-14 16:52:20.005 User name: gagan (Password: Yes, Key file: No)
. 2005-03-14 16:52:20.005 Transfer Protocol: SFTP (SCP)
. 2005-03-14 16:52:20.005 SSH protocol version: 2; Compression: No
. 2005-03-14 16:52:20.005 Agent forwarding: No; TIS/CryptoCard: No; KI: Yes;
GSSAPI: No
. 2005-03-14 16:52:20.005 Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. 2005-03-14 16:52:20.005 Ping type: -, Ping interval: 30 sec; Timeout: 15
sec
. 2005-03-14 16:52:20.005 SSH Bugs: -,-,-,-,-,-,-,-
. 2005-03-14 16:52:20.005 SFTP Bugs: -,-
. 2005-03-14 16:52:20.005 Proxy: none
. 2005-03-14 16:52:20.005 Return code variable: Autodetect; Lookup user
groups: Yes
. 2005-03-14 16:52:20.005 Shell: default, EOL: 0
. 2005-03-14 16:52:20.005 Local directory: default, Remote directory: home,
Update: No, Cache: Yes
. 2005-03-14 16:52:20.005 Cache directory changes: Yes, Permanent: Yes
. 2005-03-14 16:52:20.005 Clear aliases: Yes, Unset nat.vars: Yes, Resolve
symlinks: Yes
. 2005-03-14 16:52:20.005 Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. 2005-03-14 16:52:20.005
--------------------------------------------------------------------------
. 2005-03-14 16:52:20.005 Looking up host "192.168.10.57"
. 2005-03-14 16:52:20.005 Connecting to 192.168.10.57 port 22
. 2005-03-14 16:52:20.055 Server version: SSH-1.99-OpenSSH_3.5p1
. 2005-03-14 16:52:20.055 We claim version: SSH-2.0-WinSCP_release_3.7.3
. 2005-03-14 16:52:20.055 Using SSH protocol version 2
. 2005-03-14 16:52:20.055 Doing Diffie-Hellman group exchange
. 2005-03-14 16:52:20.105 Doing Diffie-Hellman key exchange
. 2005-03-14 16:52:22.979 Host key fingerprint is:
. 2005-03-14 16:52:22.979 ssh-rsa 1024
70:ea:61:3a:cb:96:f9:02:3b:99:4f:81:da:93:a1:06
. 2005-03-14 16:52:22.979 Initialised AES-256 client->server encryption
. 2005-03-14 16:52:22.979 Initialised HMAC-SHA1 client->server MAC algorithm
. 2005-03-14 16:52:22.989 Initialised AES-256 server->client encryption
. 2005-03-14 16:52:22.989 Initialised HMAC-SHA1 server->client MAC algorithm
! 2005-03-14 16:52:22.989 Using username "gagan".
. 2005-03-14 16:52:22.999 Keyboard-interactive authentication refused
. 2005-03-14 16:52:22.999 Session password prompt (gagan@192.168.10.57's
password: )
. 2005-03-14 16:52:22.999 Using stored password.
. 2005-03-14 16:52:22.999 Sent password
. 2005-03-14 16:52:23.009 Access granted
. 2005-03-14 16:52:23.009 Opened channel for session
. 2005-03-14 16:52:23.029 Started a shell/command
. 2005-03-14 16:52:23.029
--------------------------------------------------------------------------
. 2005-03-14 16:52:23.029 Using SFTP protocol.
. 2005-03-14 16:52:23.029 Doing startup conversation with host.
> 2005-03-14 16:52:23.029 Type: SSH_FXP_INIT, Size: 5, Number: -1
< 2005-03-14 16:52:23.029 Type: SSH_FXP_VERSION, Size: 5, Number: -1
. 2005-03-14 16:52:23.029 SFTP version 3 negotiated.
> 2005-03-14 16:52:23.029 Type: SSH_FXP_EXTENDED, Size: 38, Number: 200
< 2005-03-14 16:52:23.029 Type: SSH_FXP_STATUS, Size: 38, Number: 200
< 2005-03-14 16:52:23.029 Status/error code: 8
. 2005-03-14 16:52:23.029 Server does not recognise WinSCP.
. 2005-03-14 16:52:23.039 Getting current directory name.
. 2005-03-14 16:52:23.039 Getting real path for '.'
> 2005-03-14 16:52:23.039 Type: SSH_FXP_REALPATH, Size: 10, Number: 528
< 2005-03-14 16:52:23.039 Type: SSH_FXP_NAME, Size: 43, Number: 528
. 2005-03-14 16:52:23.039 Real path is '/home/gagan'
. 2005-03-14 16:52:23.039 Listing directory "/home/gagan".
> 2005-03-14 16:52:23.039 Type: SSH_FXP_OPENDIR, Size: 20, Number: 779
< 2005-03-14 16:52:23.039 Type: SSH_FXP_HANDLE, Size: 13, Number: 779
> 2005-03-14 16:52:23.039 Type: SSH_FXP_READDIR, Size: 13, Number: 1036
< 2005-03-14 16:52:23.049 Type: SSH_FXP_NAME, Size: 783, Number: 1036
> 2005-03-14 16:52:23.049 Type: SSH_FXP_READDIR, Size: 13, Number: 1292
. 2005-03-14 16:52:23.049 Reading symlink "marketing".
> 2005-03-14 16:52:23.049 Type: SSH_FXP_READLINK, Size: 30, Number: 1555
> 2005-03-14 16:52:23.049 Type: SSH_FXP_STAT, Size: 30, Number: 1809
< 2005-03-14 16:52:23.049 Type: SSH_FXP_STATUS, Size: 28, Number: 1292
. 2005-03-14 16:52:23.049 Storing reserved response
< 2005-03-14 16:52:23.059 Type: SSH_FXP_NAME, Size: 65, Number: 1555
< 2005-03-14 16:52:23.180 Type: SSH_FXP_ATTRS, Size: 37, Number: 1809
. 2005-03-14 16:52:23.180 Reading symlink "public".
> 2005-03-14 16:52:23.180 Type: SSH_FXP_READLINK, Size: 27, Number: 2067
> 2005-03-14 16:52:23.180 Type: SSH_FXP_STAT, Size: 27, Number: 2321
< 2005-03-14 16:52:23.190 Type: SSH_FXP_NAME, Size: 59, Number: 2067
< 2005-03-14 16:52:23.190 Type: SSH_FXP_ATTRS, Size: 37, Number: 2321
. 2005-03-14 16:52:23.190 Reading symlink "wowerpresumes".
> 2005-03-14 16:52:23.190 Type: SSH_FXP_READLINK, Size: 34, Number: 2579
> 2005-03-14 16:52:23.190 Type: SSH_FXP_STAT, Size: 34, Number: 2833
< 2005-03-14 16:52:23.190 Type: SSH_FXP_NAME, Size: 73, Number: 2579
< 2005-03-14 16:52:23.200 Type: SSH_FXP_ATTRS, Size: 37, Number: 2833
. 2005-03-14 16:52:23.200 Reading symlink "wow_resumes".
> 2005-03-14 16:52:23.200 Type: SSH_FXP_READLINK, Size: 32, Number: 3091
> 2005-03-14 16:52:23.200 Type: SSH_FXP_STAT, Size: 32, Number: 3345
< 2005-03-14 16:52:23.200 Type: SSH_FXP_NAME, Size: 69, Number: 3091
< 2005-03-14 16:52:23.200 Type: SSH_FXP_ATTRS, Size: 37, Number: 3345
. 2005-03-14 16:52:23.200 Reading symlink "technical".
> 2005-03-14 16:52:23.200 Type: SSH_FXP_READLINK, Size: 30, Number: 3603
> 2005-03-14 16:52:23.200 Type: SSH_FXP_STAT, Size: 30, Number: 3857
< 2005-03-14 16:52:23.210 Type: SSH_FXP_NAME, Size: 65, Number: 3603
< 2005-03-14 16:52:23.210 Type: SSH_FXP_ATTRS, Size: 37, Number: 3857
< 2005-03-14 16:52:23.210 Status/error code: 1
> 2005-03-14 16:52:23.210 Type: SSH_FXP_CLOSE, Size: 13, Number: 4100
. 2005-03-14 16:52:23.210 Startup conversation with host finished.
. 2005-03-14 16:52:26.304 Closing connection.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

SOLVED: Some users locked out of ssh and sftp?

[Eve Atley]

First, I had 'user account is locked'.

Second, once I logged in via the linux box, using 'ssh -l manik
192.168.10.57', it created a new .Xauthority file, apparently.

And they're in.

- Eve


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: SOLVED: Some users locked out of ssh and sftp?

[Ray Olszewski]

At 07:01 PM 3/14/2005 -0500, Eve Atley wrote:

>First, I had 'user account is locked'.
>
>Second, once I logged in via the linux box, using 'ssh -l manik
>192.168.10.57', it created a new .Xauthority file, apparently.
>
>And they're in.

I hope your problem is solved ... but I'd encourage you to keep an eye on 
this, at the least.

.Xauthority should have no connection with ssh logins ... and I just 
verified that the one host where I have an account but no .Xauthority file 
(this file derives from running X sessions, as you might guess from the 
name, so is present on my workstations) connects just fine with Winscp.

I don't know what "user account is locked"  means, possibly hecause I don't 
know the context in which you got that message.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: SOLVED: Some users locked out of ssh and sftp?

[Eve Atley]

>I don't know what "user account is locked"  means, possibly hecause I don't

>know the context in which you got that message.

In the RedHat User Manager, you can choose the Properties of each user and
edit things like what shell they use, change password, enable/disable
account expiration. Also included is a simple checkbox: "User account is
locked." On a whim, I unchecked this and things started working for me.

Which seems somehow too simple...

- Eve


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: Some users locked out of ssh and sftp?

[Eve Atley]

As a side note, it as if most of the 'older' users can login, but the newer
users cannot! I just tried with another user...michele, who was one of the
earliest users but has previously never logged in via SSH...and she had no
issues whatsoever.

- Eve

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Some users locked out of ssh and sftp?

[Marcus Furlong]

Eve Emshoff wrote:

> Thus far, I've run across 1 user who can't sftp OR
> SSH. He's entirely locked out, despite having the
> correct username and password. He appears to be set up
> the same as well the others.
> 
> Is there a file or some such I should edit and/or
> check to ensure he can get access? Anything to point
> me to in terms of what I can check in that he may
> *not* be set up the same as everyone else?

Check if there is something like 

. ~/.bashrc

or

source .bashrc

in his .bash_profile, and if there is, then comment it out.

If that doesn't work, try temporarily renaming or deleting .bashrc
and .bash_profile, and then try to ssh again.

Marcus.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Sype wont't open

[Richard Adams]

On Tuesday 01 March 2005 06:50, Peter H. wrote:
> Hi,
>
> in slackware10 trying to open skype a program
> for Internet telephony I get the following error:
>
> relocation error: /usr/lib/qt/lib/libqt-mt.so.3: undefined symbol:
> XkbSetPerClientControls

I did not get confronted with this problem when i tryed skype with 
slackware-10, i found all sorts of problems tho'.

The following URL may well help you;

https://www.redhat.com/archives/fedora-list/2004-May/msg04589.html

If that helps then your problems are not over as you will meet many problems 
with skype and slackware-10. I may well be able to help you tho´.

I did manage to get skype started but performance was lousy and to be honest i 
was very dissapointed with it.

I have it running under fedora 3, performance is fine and it was not to much 
hassel to get going.

> and the program aborts.
>
> How to resolve?
>
> Thanks & regards
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[Peter]

Thanks,

so when using Skype I will just boot into Fedora 2 instead of Slackware 10.
In Fedora 2 Skype opened and run well as soon as I had a library from Fedora3 
installed. I can't install fedora 3 since the 2nd install disk I got is 
damaged and no replacement yet from the company I bought it.

Regards
-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[Peter]

Is it possible that the kernel has something to do that skype will not open in 
slackware10 instead aborts with:

skype: relocation error: /usr/lib/qt/lib/libqt-mt.so.3: undefined symbol: 
XkbSetPerClientControls

My kernel in slackware10 is 2.4.26 whereas in Fedora2 where skype works 
flawlessly the kernel is 2.6....

What is that anyhow XkbSetPerClientControls ?

Besides having tried the static and dynamic version I tried as well the rpm 
version which I have in Fedora, made a tgz file with rpm2tgz and trying to run 
it I get the identical error message.

Regards

-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[Ray Olszewski]

At 10:07 AM 3/2/2005 +0800, Peter wrote:
>Is it possible that the kernel has something to do that skype will not 
>open in
>slackware10 instead aborts with:
>
>skype: relocation error: /usr/lib/qt/lib/libqt-mt.so.3: undefined symbol:
>XkbSetPerClientControls
>
>My kernel in slackware10 is 2.4.26 whereas in Fedora2 where skype works
>flawlessly the kernel is 2.6....
>
>What is that anyhow XkbSetPerClientControls ?
>
>Besides having tried the static and dynamic version I tried as well the rpm
>version which I have in Fedora, made a tgz file with rpm2tgz and trying to 
>run
>it I get the identical error message.

This result is somewhat puzzling, especially coming from the static version.

So I did a bit of checking, though, and apparently this message means that 
libqt-mt.so.3 is unable to find one of its symbols. In this case, the 
symbol should resolve to a call to libX11.so, so the problem is likely a 
version incompatibility between the libqt-mt.so.3 you are using and 
Slackware's libX11.so.

Probably the best workaround is to stop using the libqt-mt.so.3 you copied 
over from SuSE and find a version of libqt-mt.so.3 that is compiled for, 
and works with, Slackware 10. Then use the dynamic version of Skype with it.

In any case, it is all but surely not a kernel issue. It is some sort of X 
issue.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[Peter]

> At 10:07 AM 3/2/2005 +0800, Peter wrote:
> >Is it possible that the kernel has something to do that skype will not 
> >open in
> >slackware10 instead aborts with:
> >
> >skype: relocation error: /usr/lib/qt/lib/libqt-mt.so.3: undefined symbol:
> >XkbSetPerClientControls
> >
> >My kernel in slackware10 is 2.4.26 whereas in Fedora2 where skype works
> >flawlessly the kernel is 2.6....
> >
> >What is that anyhow XkbSetPerClientControls ?
> >
> >Besides having tried the static and dynamic version I tried as well the rpm
> >version which I have in Fedora, made a tgz file with rpm2tgz and trying to 
> >run
> >it I get the identical error message.
> 
> This result is somewhat puzzling, especially coming from the static version.

> 
On Tue, 01 Mar 2005 19:00:42 -0800
Ray Olszewski <ray@comarre.com> wrote:

> So I did a bit of checking, though, and apparently this message means that 
> libqt-mt.so.3 is unable to find one of its symbols. In this case, the 
> symbol should resolve to a call to libX11.so, so the problem is likely a 
> version incompatibility between the libqt-mt.so.3 you are using and 
> Slackware's libX11.so.
> 
> Probably the best workaround is to stop using the libqt-mt.so.3 you copied 
> over from SuSE and find a version of libqt-mt.so.3 that is compiled for, 
> and works with, Slackware 10. Then use the dynamic version of Skype with it.
> 
> In any case, it is all but surely not a kernel issue. It is some sort of X 
> issue.

Thanks Ray!

I downloaded and installed the latest qt-3.3.3-i486-3.tgz from slackware.
There is no change, all installed skype won't open,  sames error message.
I checked the libX11 and the latest version is installed.

Regards

-- 
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[Richard Adams]

On Wednesday 02 March 2005 03:07, Peter wrote:
> Is it possible that the kernel has something to do that skype will not open
> in slackware10 instead aborts with:
>
> skype: relocation error: /usr/lib/qt/lib/libqt-mt.so.3: undefined symbol:
> XkbSetPerClientControls
>
> My kernel in slackware10 is 2.4.26 whereas in Fedora2 where skype works
> flawlessly the kernel is 2.6....
>
> What is that anyhow XkbSetPerClientControls ?
>
> Besides having tried the static and dynamic version I tried as well the rpm
> version which I have in Fedora, made a tgz file with rpm2tgz and trying to
> run it I get the identical error message.

When i searched google for your error message some said it is a bug in qt, 
others say its because one has installed another version of qt and now has 
two versions installed.
I pointed you to an URL which menioned a spesific order of directory´s in the 
file /etc/ld.so.conf. here is what i used on my slack-10 system when i tryed 
skype.

/usr/local/lib
/usr/X11R6/lib
/usr/i486-slackware-linux/lib
/opt/kde/lib
/usr/lib/qt/lib
/usr/lib/xine
/usr/lib
/lib

I noticed in another message of your that what ls -al /usr/lib/qt retured, it 
was different to my origanal slack-10 install, i get;
/usr/lib/qt -> qt-3.3.2

I belive if you installed an rpm from fedora 2 then that could well be your 
problem.

> Regards
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[Peter]

Thanks Adam!

My /etc/ld.so.conf is practically the same:

/usr/local/lib
/usr/X11R6/lib
/usr/i486-slackware-linux/lib
/opt/kde/lib
/usr/lib/qt/lib
/usr/local/tmake/lib
/usr/lib
/usr/local/ActiveTcl/lib
/usr/include
/usr/local/lib/sigc++-1.2
/lib

and ls -al /usr/lib/qt
/usr/lib/qt -> qt-3.3.3

After this installation of qt-3.3.3 I did ldconfig.

I have no other version qt installed.

ls /usr/lib/qt*
/usr/lib/qt:
README-QT.TXT  examples    lib      plugins
bin            extensions  mkspecs  tutorial
doc            include     pics

/usr/lib/qt-3.3.3:
README-QT.TXT  examples    lib      plugins
bin            extensions  mkspecs  tutorial
doc            include     pics

Regards
-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[Richard Adams]

On Wednesday 02 March 2005 08:33, Peter wrote:
> Thanks Adam!

I presume you meant Richard Adams...

> My /etc/ld.so.conf is practically the same:
>
> /usr/local/lib
> /usr/X11R6/lib
> /usr/i486-slackware-linux/lib
> /opt/kde/lib
> /usr/lib/qt/lib

There should be no need to define qt at all as you define /usr/lib, futher 
more its the define order that matters according to others who have the same 
problem as you.

Ray mentioned dependancies that quite possably backs up the need to define 
libs in a spesific order to aviod such problems. 

> /usr/local/tmake/lib
> /usr/lib
> /usr/local/ActiveTcl/lib
> /usr/include
> /usr/local/lib/sigc++-1.2
> /lib
>
> and ls -al /usr/lib/qt
> /usr/lib/qt -> qt-3.3.3

Ok but are you sure qt3.3.2 is deleted,?? 
>
> After this installation of qt-3.3.3 I did ldconfig.
>
> I have no other version qt installed.
>
> ls /usr/lib/qt*
> /usr/lib/qt:
> README-QT.TXT  examples    lib      plugins
> bin            extensions  mkspecs  tutorial
> doc            include     pics
>
> /usr/lib/qt-3.3.3:
> README-QT.TXT  examples    lib      plugins
> bin            extensions  mkspecs  tutorial
> doc            include     pics
>
> Regards
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[Peter]

pa3gcu@zeelandnet.nl said:
> I presume you meant Richard Adams...

Actually Richards

pa3gcu@zeelandnet.nl said:
> Ok but are you sure qt3.3.2 is deleted,?? 

heisspf@~:$ locate qt-3.3.2
heisspf@~:$

Not a trace left. Updated daily.

I put this now into ld.so.conf only with no change of the error message after 
doing ldconfig. This is anyhow the sequence put-in by slackware I think.

/usr/local/lib
/usr/X11R6/lib
/usr/i486-slackware-linux/lib
/opt/kde/lib
/usr/lib
/lib

and leaving /usr/lib/qt out I get:

error while loading shared libraries: libqt-mt.so.3: cannot open shared object 
file: No such file or directory


I have the strong suspicion the problem is in those libs in /usr/X11R6/libs.
Are they different from distro to distro?

This is the end of strace dynamic skype:

read(4, "&\0\0\0\1\1\22\t\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0"..., 604) = 604
writev(2, [{"./skype", 7}, {": ", 2}, {"symbol lookup error", 19}, {": ", 2}, 
{"./skype", 7}, {": ", 2}, {"undefined symbol: XkbSetPerClien"..., 41}, {"", 
0}, {"", 0}, {"\n", 1}], 10./skype: symbol lookup error: ./skype: undefined 
symbol: XkbSetPerClientControls
) = 81
exit_group(127) 

Regards
-- 
Peter


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[chuck gelm]

Hi, Peter:

  This 'skype' is rather new to me and I only have it working
well using Windows 2000 & Windows XP.  It 'works' with
Slackware v9.1, but the audio is not good.

I am suggesting that you try with a fresh install of
Slackware so that it will not be confused with a 'rpm'
install of libraries from another distribution.

  Skype 'works' for me when invoked from a Xwindow terminal.
My Xwindow environment is Gnome (Slackware v9.1 default).
I guess I installed (or it defaulted to) Skype binary into
/usr/local/bin.  I run Gnome in Xwindows, open a terminal
windows and enter 'skype'.  Viola! it runs.

OBTW, my brother has Skype running on at least one
desktop and one laptop under Slackware.  I'll BC:
him and maybe he can offer some help or hints.
John: This is 'linux-newbie'.
http://vger.kernel.org/majordomo-info.html

Are there archives of linux-newbie?

HTH, Chuck


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Skype wont't open

[Richard Adams]

On Thursday 03 March 2005 10:56, Peter wrote:
> pa3gcu@zeelandnet.nl said:
> > I presume you meant Richard Adams...
>
> Actually Richards
>
> pa3gcu@zeelandnet.nl said:
> > Ok but are you sure qt3.3.2 is deleted,??
>
> heisspf@~:$ locate qt-3.3.2
> heisspf@~:$
>
> Not a trace left. Updated daily.
>
> I put this now into ld.so.conf only with no change of the error message
> after doing ldconfig. This is anyhow the sequence put-in by slackware I
> think.
>
> /usr/local/lib
> /usr/X11R6/lib
> /usr/i486-slackware-linux/lib
> /opt/kde/lib
> /usr/lib
> /lib
>
> and leaving /usr/lib/qt out I get:
>
> error while loading shared libraries: libqt-mt.so.3: cannot open shared
> object file: No such file or directory

I was seemingly missleading on saying that /usr/lib should have been enought, 
iḿ sorry to say but i seem to be wrong.

It is defined here as

/usr/lib/qt/lib
Once again i have qt-3.3.2.
I have tryed skype on another box with a clean slack-10 install and i do not 
get that message.

Anyway like i mentioned slackware-10 and skype do not really like each other, 
even if skype starts you need to tune things a lot to get it to even think of 
working.


>
> I have the strong suspicion the problem is in those libs in
> /usr/X11R6/libs. Are they different from distro to distro?
>
> This is the end of strace dynamic skype:
>
> read(4, "&\0\0\0\1\1\22\t\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0"..., 604) =
> 604 writev(2, [{"./skype", 7}, {": ", 2}, {"symbol lookup error", 19}, {":
> ", 2}, {"./skype", 7}, {": ", 2}, {"undefined symbol: XkbSetPerClien"...,
> 41}, {"", 0}, {"", 0}, {"\n", 1}], 10./skype: symbol lookup error: ./skype:
> undefined symbol: XkbSetPerClientControls
> ) = 81
> exit_group(127)


I am quite sure someone on the skype site mailing list(s) would appricate that 
as a problem report Peter.
All it says to me is that an undefined symbol was discoverd-;)


>
> Regards
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Sype wont't open

[chuck gelm]

Peter H. wrote:
> Hi,
> 
> in slackware10 trying to open skype a program
> for Internet telephony I get the following error:
> 
> relocation error: /usr/lib/qt/lib/libqt-mt.so.3: undefined symbol: 
> XkbSetPerClientControls
> 
> and the program aborts.
> 
> How to resolve?
> 
> Thanks & regards

Dear Peter:

  Get the 'static' version.
http://www.skype.com/products/skype/linux/
"Static binary tar.bz2 with Qt 3.2 compiled in (8.0 MB)"

HTH, Chuck


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Sype wont't open

[Richard Adams]

On Tuesday 01 March 2005 10:46, chuck gelm wrote:
> Dear Peter:
>
>   Get the 'static' version.
> http://www.skype.com/products/skype/linux/
> "Static binary tar.bz2 with Qt 3.2 compiled in (8.0 MB)"
>
> HTH, Chuck

Chuck, do you have it running on slack-10.?? if so what is your impression and 
what things did you need to configure to get it to run.??

Regards Richard.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: SOLVED: Some users locked out of ssh and sftp?

[Donald Duckie]

I got this error message as shown below  . . . 
How do I change the /root/.ssh/known_hosts file?
It seems encrypted . . .


@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! 
   @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now
(man-in-the-middle attack)!
It is also possible that the RSA host key has just
been changed.
The fingerprint for the RSA key sent by the remote
host is
23:52:d4:e8:6a:75:72:ed:78:cb:31:1f:6a:ff:b4:ea.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get
rid of this message.
Offending key in /root/.ssh/known_hosts:7
RSA host key for 192.168.0.1 has changed and you have
requested strict checking.
Host key verification failed.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: SOLVED: Some users locked out of ssh and sftp?

[SOTL]

On Tuesday 15 March 2005 04:23, Donald Duckie wrote:
> I got this error message as shown below  . . .
> How do I change the /root/.ssh/known_hosts file?
> It seems encrypted . . .
>
>
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
>    @
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> Someone could be eavesdropping on you right now
> (man-in-the-middle attack)!
> It is also possible that the RSA host key has just
> been changed.
> The fingerprint for the RSA key sent by the remote
> host is
> 23:52:d4:e8:6a:75:72:ed:78:cb:31:1f:6a:ff:b4:ea.
> Please contact your system administrator.
> Add correct host key in /root/.ssh/known_hosts to get
> rid of this message.
> Offending key in /root/.ssh/known_hosts:7
> RSA host key for 192.168.0.1 has changed and you have
> requested strict checking.
> Host key verification failed.
>
I posted this to you several days ago.

The file you are seeking is located in the computer you are loging in FROM not 
the server.

Look at my previous message:

Hi All

I just spent half a day trying to fix this problem on the wrong computer. In 
justification of the time I was not using SSH directly but fish which uses 
SSH so I was not getting the error messages. Once I tried it connecting using 
SSH I fixed the problem in 5 minutes

In Linux SSH has a computer verification file for computers that have 
permission to log in at /home/<user>/.ssh/known_hosts:2

Explanation. I trashed the HD in one box [a test box with no data in it]. 
After re installation of HD, & configuration I found that I could SSH from 
the  new system but could not SSH from computers which had previously 
connected to the box with the new HD and system. 

I removed contents of above fine saved and was able to immediately log-in.

Hope this helps.

Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: SOLVED: Some users locked out of ssh and sftp?

[chuck gelm]

Donald Duckie wrote:
> I got this error message as shown below  . . . 
> How do I change the /root/.ssh/known_hosts file?
> It seems encrypted . . .

Hi, Donald:

  The file is not encripted, but it contains an encription key for
each remote hostname.  There is a line for each 'ssh' host that
you have sucessfully connected.  If the remote 'host' has changed
its encription key and you already have a line with the old
encription key, 'ssh' will fail with that message.

Solution:

  Use a 'text' editor and open /root/.ssh/known_hosts.
Delete the line that starts with the remote hostname.
Save and exit.  (or 'rm known_hosts')

'ssh' to that hostname.
Answer 'yes' when prompted.

HTH, Chuck

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: SOLVED: Some users locked out of ssh and sftp?

[Ray Olszewski]

If this still you, Eve, just from a different e-mail address? Or is this 
someone new with (almost) the same problem as Eve?

At 01:23 AM 3/15/2005 -0800, Donald Duckie wrote:

>I got this error message as shown below  . . .
>How do I change the /root/.ssh/known_hosts file?
>It seems encrypted . . .

Chuck identified the right first-pass fix here. To expand a bit: go into 
the known_hosts file (on the client end, NOT the server end), find the 
entry for the target sshd server's system (at the START of each long entry 
is one or more identifiers, which could be hostnames, FQDNs, or IP 
addresses ... look for 192.168.0.1) and simply delete it. Then your ssh 
client will see the connection attempt as a first connection to a new host 
and ask you to confirm it manually ... at which point it will do the 
required update to known_hosts for you.

The above may not work in your setup, though; as I read the man page, it is 
unclear how ssh handles new connections when set to "StrictHostKeyChecking 
Yes". If this does NOT work, I suggest a second approach below.


>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
>    @
>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
>Someone could be eavesdropping on you right now
>(man-in-the-middle attack)!
>It is also possible that the RSA host key has just
>been changed.
>The fingerprint for the RSA key sent by the remote
>host is
>23:52:d4:e8:6a:75:72:ed:78:cb:31:1f:6a:ff:b4:ea.
>Please contact your system administrator.
>Add correct host key in /root/.ssh/known_hosts to get
>rid of this message.
>Offending key in /root/.ssh/known_hosts:7
>RSA host key for 192.168.0.1 has changed and you have
>requested strict checking.
>Host key verification failed.

What is causing your problem is that you (probably) have

         StrictHostKeyChecking Yes

in your ssh **client's** config file (/etc/ssh/ssh_config for systemwide 
settings,  $HOME/.ssh/config for user-specific setting). Change this 
setting to

         StrictHostKeyChecking Ask

and ssh will ask you if you want to update the key when it sees this sort 
of thing, which occurred either because you reinstalled sshd on the host in 
question (thereby generating a new server key in 
/etc/ssh/ssh_host_rsa_key), or you replaced the host at that hostname, 
FQDN, or IP address (whichever way you attempted to connect to it ... 
probably IP address, since the message refers to 192.168.0.1).


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: SOLVED: Some users locked out of ssh and sftp?

[Eve Atley]

It's not me! :)

- Eve

-----Original Message-----
From: linux-newbie-owner@vger.kernel.org
[mailto:linux-newbie-owner@vger.kernel.org] On Behalf Of Ray Olszewski
Sent: Tuesday, March 15, 2005 11:03 AM
To: linux-newbie@vger.kernel.org
Subject: Re: SOLVED: Some users locked out of ssh and sftp?


If this still you, Eve, just from a different e-mail address? Or is this 
someone new with (almost) the same problem as Eve?

At 01:23 AM 3/15/2005 -0800, Donald Duckie wrote:

>I got this error message as shown below  . . .
>How do I change the /root/.ssh/known_hosts file?
>It seems encrypted . . .

Chuck identified the right first-pass fix here. To expand a bit: go into 
the known_hosts file (on the client end, NOT the server end), find the 
entry for the target sshd server's system (at the START of each long entry 
is one or more identifiers, which could be hostnames, FQDNs, or IP 
addresses ... look for 192.168.0.1) and simply delete it. Then your ssh 
client will see the connection attempt as a first connection to a new host 
and ask you to confirm it manually ... at which point it will do the 
required update to known_hosts for you.

The above may not work in your setup, though; as I read the man page, it is 
unclear how ssh handles new connections when set to "StrictHostKeyChecking 
Yes". If this does NOT work, I suggest a second approach below.


>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
>    @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
>Someone could be eavesdropping on you right now
>(man-in-the-middle attack)!
>It is also possible that the RSA host key has just
>been changed.
>The fingerprint for the RSA key sent by the remote
>host is
>23:52:d4:e8:6a:75:72:ed:78:cb:31:1f:6a:ff:b4:ea.
>Please contact your system administrator.
>Add correct host key in /root/.ssh/known_hosts to get
>rid of this message.
>Offending key in /root/.ssh/known_hosts:7
>RSA host key for 192.168.0.1 has changed and you have
>requested strict checking.
>Host key verification failed.

What is causing your problem is that you (probably) have

         StrictHostKeyChecking Yes

in your ssh **client's** config file (/etc/ssh/ssh_config for systemwide 
settings,  $HOME/.ssh/config for user-specific setting). Change this 
setting to

         StrictHostKeyChecking Ask

and ssh will ask you if you want to update the key when it sees this sort 
of thing, which occurred either because you reinstalled sshd on the host in 
question (thereby generating a new server key in 
/etc/ssh/ssh_host_rsa_key), or you replaced the host at that hostname, 
FQDN, or IP address (whichever way you attempted to connect to it ... 
probably IP address, since the message refers to 192.168.0.1).


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: SOLVED: Some users locked out of ssh and sftp?

[Donald Duckie]

hi chuck,

thanks for your information.
i was quite hesistant to delete that line, that was
why i wanted some confirmation.
it is already ok now.

this is not eve.
sorry eve :)
it just happen that i have the same problem that
moment, and while taking some break, i happen to read
this thread. that was why i asked as to how i would
modify the known_hosts file.

donald

--- chuck gelm <chuck@gelm.net> wrote:
> Donald Duckie wrote:
> > I got this error message as shown below  . . . 
> > How do I change the /root/.ssh/known_hosts file?
> > It seems encrypted . . .
> 
> Hi, Donald:
> 
>   The file is not encripted, but it contains an
> encription key for
> each remote hostname.  There is a line for each
> 'ssh' host that
> you have sucessfully connected.  If the remote
> 'host' has changed
> its encription key and you already have a line with
> the old
> encription key, 'ssh' will fail with that message.
> 
> Solution:
> 
>   Use a 'text' editor and open
> /root/.ssh/known_hosts.
> Delete the line that starts with the remote
> hostname.
> Save and exit.  (or 'rm known_hosts')
> 
> 'ssh' to that hostname.
> Answer 'yes' when prompted.
> 
> HTH, Chuck
> 
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at
> http://www.linux-learn.org/faqs
> 


		
__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo 
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs