Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Today I was customizing my desktop and I had to use su in a terminal to start nautilus so I could copy some icon files to /usr/share/pixmaps. That way I can select them for launchers using custom icons under properties. After I closed the nautilus session that I opened using su from a terminal, I got the following message at the command prompt:
(nautilus:4704): Bonobo-WARNING **: Leaked a total of 14 refs to 14 bonobo object(s)
Anyone know what this is all about? Nothing bad happened and everything continued to work properly. It seems bash didn't like me using su to open nautilus, or, it didn't appreciate me using bash to open nautilus in a gui and copy and paste files from various folders that way. I thought Linux was suppose to let me do whatever I wanted with my computer...even if it ends up borking the system. Well, actually, it did let me do what I wanted, it just let me know what the result was...14 leaks to bonobo objects...huh!?
Originally posted by sharkzf6 Anyone know what this is all about? Nothing bad happened and everything continued to work properly. It seems bash didn't like me using su to open nautilus, or, it didn't appreciate me using bash to open nautilus in a gui and copy and paste files from various folders that way. I thought Linux was suppose to let me do whatever I wanted with my computer...even if it ends up borking the system. Well, actually, it did let me do what I wanted, it just let me know what the result was...14 leaks to bonobo objects...huh!?
Ha ha, scratch that! My Gnome sounds quit working. I could play .wav files from a terminal using aplay and Doom 3 still had sound, but the system sounds quit. I logged out and back in, no help. I restarted X without rebooting the computer, no help. I ended up rebooting the computer and everything went back to normal, all system sounds restored. Guess this bonobo thing is pretty important although when I checked synaptic (using Debian) bonobo is not installed though some of its libraries are...weird.
Nope, I can tell you it had nothing to do with your sound dying because I get that all the time when I open nautilus from a console. I sorta worried at first but then when nothing went wrong I stopped caring, figured if something was gonna break it would've done so by now
Originally posted by DJ P@CkMaN Nope, I can tell you it had nothing to do with your sound dying because I get that all the time when I open nautilus from a console. I sorta worried at first but then when nothing went wrong I stopped caring, figured if something was gonna break it would've done so by now
Thanks for the feedback, I'm sure you're right about the sound dying when opening nautilus from the console.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.