SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
when i used the original gaim on slack 10.1 when I send a message the windows all close and its gone. So I upgraded to 1.3.1 package and in that package there is no AIM protocal, just napster and a few others????????????? any one know whats up with that
I also tried it from source with 1.4.0 and it killed all the windows again when I send a message.
just tried adding the tray icon plugin to make sure it was going away completly and it is, the whole thing shuts down when you send a message, you can check peoples away messages and info and all that stuff just cant send messages
Is there something in need to intall some support package?????????/
I used to have a problem like the one you describe. I ran gaim from the command line. And it showed a permission denied error on I think.:
/tmp/mcop-$USERNAME
To fix it all I did was rm -rf /tmp/mcop-$USERNAME
Seemed to do the trick for me.
Mirari, I don't dislike your method to get rid of the usual
/tmp/mcop-$USERNAME permission denied problem, but
you could fix it gently with :
chown -R $USERNAME:users /tmp/mcop-$USERNAME
Hmmm I did what you guys said and loaded it from the prompt and you were right!!!!
it was the mcop thing, but removing the directory didnt do anyting, becuase when I tried again it still did the same thing just made the directory again with a new secret cookie file. but still says
/tmp/mcop-root is accessible owned by user
Do u think maybe I need to add new permissions to this directory
I'd seriously reccomend you using a non-superuser account for anything other than admin, and then only as a su session from another user, or using su -c 'command'.
Oh that would be becuase its not my computer and i am sopose to be logged in as root, dont ask me I just do what the job tells me.. Even though you know you shouldnt be doing something doesnt mean that your employer cares to hear about best practices in security policy
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.