I installed a program with Yast (Kmess), but when I try to run it, bash gives me back this message:
kmess: command not found
I checked into Yast and it seems to be installed correctly!
Somebody knows wich could be the problem?
Thanks
Did you type:
Kmess
or
kmess
kmess, but if I type Kmess is the same
result of
rpm -qi kmess
did you reboot?shouldn’t be needed but/…
Yes, I rebooted.
This is the result of the command
Name : kmess Relocations: (not relocatable)
Version : 2.0.60git20100801 Vendor: obs://build.opensuse.org/KDE:Unstable
Release : 9.6 Build Date: lun 27 set 2010 18:56:27 CEST
Install Date: gio 30 set 2010 20:40:54 CEST Build Host: build11
Group : Productivity/Networking/AOLInstantMessenger Source RPM: kmess-2.0.60git20100801-9.6.src.rpm
Size : 5390233 License: GPL
Signature : DSA/SHA1, lun 27 set 2010 18:57:20 CEST, Key ID 2e85baee9ebd09c4
URL : http://kmess.sourceforge.net/
Summary : MSN Messenger Client for KDE
Description :
KMess is a MSN Messenger client for Linux. It enables Linux
users to chat with friends online who are using MSN Messenger
in Windows or Mac OS. The strength of KMess is it's integration
with the KDE desktop environment, focus on MSN Messenger specific
features and an easy-to-use interface.
Authors:
--------
Mike K. Bennett <mkb137@hotmail.com>
Michael Curtis <mdcurtis@users.sourceforge.net>
Jan Tönjes <jan.toenjes@web.de>
Lin Haoxiang <linhaoxiang@hotmail.com>
Diederik van der Boor <vdboor@codingdomain.com>
Distribution: KDE:Unstable:Playground / openSUSE_11.3_KDE_Distro_Stable
Why are you using the unstable repo. I’m guessing you have no idea because anyone using those repos would know how to solve this
Please post result of
zypper lr -d
like this
https://www.youtube.com/watch?v=QL-CDbKxvx0)
Exactly, I have no idea.
I’m a opensuse user from just a few days.
This is the output:
# | Alias | Nome | abilitato | Attualizza | Priorità | Tipo | URI | Servizio
---+-------------------------------------------+-------------------------------------------+-----------+------------+----------+--------+------------------------------------------------------------------------------------------------------+---------
1 | Aggiornamenti per openSUSE 11.3 11.3-1.82 | Aggiornamenti per openSUSE 11.3 11.3-1.82 | Sì | Sì | 99 | rpm-md | http://download.opensuse.org/update/11.3/ |
2 | KDE_Core | KDE Core | Sì | Sì | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Distro:/Stable/openSUSE_11.3/ |
3 | KDE_Extra | KDE Extra | Sì | Sì | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_11.3/ |
4 | KDE_Playground | KDE Playground | Sì | Sì | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Unstable:/Playground/openSUSE_11.3_KDE_Distro_Stable/ |
5 | KDE_UpdatedApps | KDE UpdatedApps | Sì | Sì | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/UpdatedApps/openSUSE_11.3/ |
6 | NVIDIA Repository | NVIDIA Repository | Sì | Sì | 99 | rpm-md | ftp://download.nvidia.com/opensuse/11.3/ |
7 | google-chrome | google-chrome | Sì | Sì | 99 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/i386 |
8 | http://packman.iu-bremen.de/suse/11.3 | http://packman.iu-bremen.de/suse/11.3 | Sì | Sì | 99 | rpm-md | http://packman.iu-bremen.de/suse/11.3 |
9 | openSUSE-11.3 11.3-1.82 | openSUSE-11.3 11.3-1.82 | Sì | No | 99 | yast2 | cd:///?devices=/dev/sr0 |
10 | repo-debug | openSUSE-11.3-Debug | No | Sì | 99 | NONE | http://download.opensuse.org/debug/distribution/11.3/repo/oss/ |
11 | repo-non-oss | openSUSE-11.3-Non-Oss | Sì | Sì | 99 | yast2 | http://download.opensuse.org/distribution/11.3/repo/non-oss/ |
12 | repo-oss | openSUSE-11.3-Oss | Sì | Sì | 99 | yast2 | http://download.opensuse.org/distribution/11.3/repo/oss/ |
13 | repo-source | openSUSE-11.3-Source | No | Sì | 99 | yast2 | http://download.opensuse.org/source/distribution/11.3/repo/oss/
Become su - in a terminal
https://www.youtube.com/watch?v=5Wv-IaDsitA)
Do this
zypper rr 4
now close the terminal
go to Yast software management
search for kmess, and it will be in red
click it’s check box and it should update to a stable version
accept
On 2010-10-01 17:06, andrearro88 wrote:
> I checked into Yast and it seems to be installed correctly!
> Somebody knows wich could be the problem?
Look again, there is a tab listing the installed files for each selected package. In that list, find
what is the program name, something under “bin/”
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Ok, problem solved…thank you very much caf4926! 
No problem
At least I was of some little help
Grate, but now I have the same problem for another package: checkinstall.
This is the rpm -qi checkinstall output:
Name : checkinstall Relocations: (not relocatable)
Version : 1.6.2 Vendor: openSUSE
Release : 3.1 Build Date: lun 05 lug 2010 13:25:56 CEST
Install Date: ven 01 ott 2010 17:52:38 CEST Build Host: build35
Group : Development/Tools/Building Source RPM: checkinstall-1.6.2-3.1.src.rpm
Size : 367507 License: GPLv2+
Signature : RSA/8, lun 05 lug 2010 13:26:08 CEST, Key ID b88b2fd43dbdc284
Packager : http://bugs.opensuse.org
URL : http://asic-linux.com.mx/~izto/checkinstall/
Summary : "make install" Installation Tracker
Description :
Uses installwatch to keep track of all files created or modified during
the run of an installation script like "make install". The information
is used to create a rpm package that holds all files installed by the
tracked installation. This makes it possible, for example, to remove
all files later with rpm -e package or to install the package on
another system.
Authors:
--------
Felipe Eduardo Sánchez Díaz Durán
Distribution: openSUSE 11.3
On 2010-10-04 00:36, andrearro88 wrote:
>
> Grate, but now I have the same problem for another package:
> checkinstall.
> This is the rpm -qi checkinstall output:
It is “l”, lower case “L”, not “i”. Or yast, tab file list.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
I just did what caf4926 told me to do to get usefull informations.
This is the output of your command:
[wallace@linux-atnb ~]$ rpm -ql checkinstall
/etc/checkinstallrc
/etc/checkinstallrc-dist
/usr/bin/installwatch
/usr/lib/installwatch.so
/usr/sbin/checkinstall
/usr/sbin/makepak
/usr/share/locale/de/LC_MESSAGES/checkinstall.mo
/usr/share/locale/es/LC_MESSAGES/checkinstall.mo
/usr/share/locale/id/LC_MESSAGES/checkinstall.mo
/usr/share/locale/it/LC_MESSAGES/checkinstall.mo
/usr/share/locale/ja/LC_MESSAGES/checkinstall.mo
/usr/share/locale/nb/LC_MESSAGES/checkinstall.mo
/usr/share/locale/pt_BR/LC_MESSAGES/checkinstall.mo
/usr/share/locale/ru/LC_MESSAGES/checkinstall.mo
/usr/share/locale/zh_CN/LC_MESSAGES/checkinstall.mo
I tried to type the command “/usr/sbin/checkinstall” and it works.
Nothing still happen when I just type “checkinstall”!!!
On 2010-10-04 09:06, andrearro88 wrote:
> I tried to type the command “/usr/sbin/checkinstall” and it works.
> Nothing still happen when I just type “checkinstall”!!!
Obviously. Are you root? No. Then you have no right to use that command.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
No, that’s not the problem:
[wallace@linux-atnb ~]$ sudo checkinstall
root's password:
sudo: checkinstall: command not found
What about
su -
On 2010-10-04 15:36, andrearro88 wrote:
>
> No, that’s not the problem:
>
> Code:
> --------------------
>
> [wallace@linux-atnb ~]$ sudo checkinstall
> root’s password:
> sudo: checkinstall: command not found
>
> --------------------
But yes, it still is
When you issue the “sudo” command, you are still a plain user, so the command is not found. You have
to give the full path.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
All sbin directories are not in the user’s defined path. Using sudo or just su you still are using your user defined path. To get to those files without giving the full path you must full become root with roots defined path. This you do with the su - (note the minus sign)
1st: I doubt that calling ‘su’ instead of ‘su -’ does affect the $PATH, I can call any command either way.
2nd: The executionable file of ‘checkinstall’ is not in /sbin but in /usr/sbin, which is in any users $PATH.
Just for the record: ‘checkinstall’ does not work as good as it used to, I suppose because it is hardly maintained these days - I have checkinstalled many packages in the past, but these days it fails most of the times.