Re: Weird virtualbox... [SOLVED]
A very drastic workaround that got you by your problem. I'm not sure it is solved until someone understands WHAT happened and WHY so you can be confident it won't happen again or know a less drastic resolution. On Sat, Jul 14, 2012 at 9:50 PM, kitepi...@kitepilot.com kitepi...@kitepilot.com wrote: Well, I wiped out Mint and installed Debian squeeze. All good now... :) ET kitepi...@kitepilot.com writes: Well, the Gnomes are at work (again) in my box and I could certainly use some help to evict them... This is what's happening: I use: 'ssh -fCXY user@remotebox run-something' a lot. Works every time. Or 'mostly' every time... Now when I run (ONLY from *MY* box): ssh -fCXY turboviking virtualbox I get: *** glibc detected *** /usr/lib/virtualbox/**VirtualBox: malloc(): memory corruption: 0x099c5e48 *** And a long trace. This is the quick rundown of how it broke: My desktop was having hiccups and I decided to replace whatever I had (can't remember what) with the latest Xubuntu. After that, the problem started. This problem, coupled with other issues, led me to scrap Xubuntu and install the latest Mint/Mate. Problem didn't go away... The Xubuntu and Mint installations were fresh from-scratch installs, the only thing I preserved was my home directory. So the conclusion was evident: there is something in my /home/directory causing the problem. Nope... Created another user, rebooted the box and logged in with the new user. Same $#!T... :( Now, ANYTHING else that I have fired up works just fine. And If I run the exact same instruction from other of my local boxes, it works fine too! It is ONLY 'vitualbox in my box' that fails. But it used to work just fine... Now the (unsolvable and incomprehensible to me) question is: What could possibly be breaking the whole 'remote SSH run' mechanism (ONLY for Virtualbox) in my box, which used to work fine before, and works fine from everywhere else. Other than sacrificing another goat and burying some transistors and garlic wrapped on anti-static paper at midnite with no Moon, I don't know what to do... I have seen Virtualbox do weird things before when ran it remotely under X/SSH, but this blows my (little) mind. :( Any ideas? Sight... ET --**- PLUG-discuss mailing list - plug-disc...@lists.plug.**phoenix.az.usPLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.**us/mailman/listinfo/plug-**discusshttp://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --**- PLUG-discuss mailing list - plug-disc...@lists.plug.**phoenix.az.usPLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.**us/mailman/listinfo/plug-**discusshttp://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss -- Dazed_75 a.k.a. Larry Please protect my address like I protect yours. When sending messages to multiple recipients, always use the BCC: (Blind carbon copy) and not To: or CC:. Remove all addresses from the message body before sending a Forwarded message. This can prevent spy programs capturing addresses from the recipient list and message body. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Weird virtualbox... [SOLVED]
For what I have seen, I believe it to be a combination of problems from the chipset/kernel/drivers interaction. Xubuntu and Mint came from the same Ubuntu base and that's why they shared the problem. Of course this is only my speculation and what you say is very well valid, and the issue could rear its ugly head again when Debian updates any of the factors to its breaking point. While it doesn't happen, I'll tug along with Debian... :) ET Dazed_75 writes: A very drastic workaround that got you by your problem. I'm not sure it is solved until someone understands WHAT happened and WHY so you can be confident it won't happen again or know a less drastic resolution. On Sat, Jul 14, 2012 at 9:50 PM, kitepi...@kitepilot.com kitepi...@kitepilot.com wrote: Well, I wiped out Mint and installed Debian squeeze. All good now... :) ET kitepi...@kitepilot.com writes: Well, the Gnomes are at work (again) in my box and I could certainly use some help to evict them... This is what's happening: I use: 'ssh -fCXY user@remotebox run-something' a lot. Works every time. Or 'mostly' every time... Now when I run (ONLY from *MY* box): ssh -fCXY turboviking virtualbox I get: *** glibc detected *** /usr/lib/virtualbox/**VirtualBox: malloc(): memory corruption: 0x099c5e48 *** And a long trace. This is the quick rundown of how it broke: My desktop was having hiccups and I decided to replace whatever I had (can't remember what) with the latest Xubuntu. After that, the problem started. This problem, coupled with other issues, led me to scrap Xubuntu and install the latest Mint/Mate. Problem didn't go away... The Xubuntu and Mint installations were fresh from-scratch installs, the only thing I preserved was my home directory. So the conclusion was evident: there is something in my /home/directory causing the problem. Nope... Created another user, rebooted the box and logged in with the new user. Same $#!T... :( Now, ANYTHING else that I have fired up works just fine. And If I run the exact same instruction from other of my local boxes, it works fine too! It is ONLY 'vitualbox in my box' that fails. But it used to work just fine... Now the (unsolvable and incomprehensible to me) question is: What could possibly be breaking the whole 'remote SSH run' mechanism (ONLY for Virtualbox) in my box, which used to work fine before, and works fine from everywhere else. Other than sacrificing another goat and burying some transistors and garlic wrapped on anti-static paper at midnite with no Moon, I don't know what to do... I have seen Virtualbox do weird things before when ran it remotely under X/SSH, but this blows my (little) mind. :( Any ideas? Sight... ET --**- PLUG-discuss mailing list - plug-disc...@lists.plug.**phoenix.az.usPLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.**us/mailman/listinfo/plug-**discusshttp://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --**- PLUG-discuss mailing list - plug-disc...@lists.plug.**phoenix.az.usPLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.**us/mailman/listinfo/plug-**discusshttp://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss -- Dazed_75 a.k.a. Larry Please protect my address like I protect yours. When sending messages to multiple recipients, always use the BCC: (Blind carbon copy) and not To: or CC:. Remove all addresses from the message body before sending a Forwarded message. This can prevent spy programs capturing addresses from the recipient list and message body. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Weird virtualbox... [SOLVED]
Well, I wiped out Mint and installed Debian squeeze. All good now... :) ET kitepi...@kitepilot.com writes: Well, the Gnomes are at work (again) in my box and I could certainly use some help to evict them... This is what's happening: I use: 'ssh -fCXY user@remotebox run-something' a lot. Works every time. Or 'mostly' every time... Now when I run (ONLY from *MY* box): ssh -fCXY turboviking virtualbox I get: *** glibc detected *** /usr/lib/virtualbox/VirtualBox: malloc(): memory corruption: 0x099c5e48 *** And a long trace. This is the quick rundown of how it broke: My desktop was having hiccups and I decided to replace whatever I had (can't remember what) with the latest Xubuntu. After that, the problem started. This problem, coupled with other issues, led me to scrap Xubuntu and install the latest Mint/Mate. Problem didn't go away... The Xubuntu and Mint installations were fresh from-scratch installs, the only thing I preserved was my home directory. So the conclusion was evident: there is something in my /home/directory causing the problem. Nope... Created another user, rebooted the box and logged in with the new user. Same $#!T... :( Now, ANYTHING else that I have fired up works just fine. And If I run the exact same instruction from other of my local boxes, it works fine too! It is ONLY 'vitualbox in my box' that fails. But it used to work just fine... Now the (unsolvable and incomprehensible to me) question is: What could possibly be breaking the whole 'remote SSH run' mechanism (ONLY for Virtualbox) in my box, which used to work fine before, and works fine from everywhere else. Other than sacrificing another goat and burying some transistors and garlic wrapped on anti-static paper at midnite with no Moon, I don't know what to do... I have seen Virtualbox do weird things before when ran it remotely under X/SSH, but this blows my (little) mind. :( Any ideas? Sight... ET --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
