digifuzzy

Good catch. I wasn't aware of this "feature". I can already see where it was pulled out and re-installed. Must dig. Thx Tassie!

As reported above, no errors with SMART.

Futex - wikipedia

spectromas, NP! HTH :) I thought FF-bin was "precompiled". Suggest to me FF-bin may have issues with some local setup. Just a guess. Hope you sort it out. :D

waiting for ssl.gstatic Google search found this. Suggests DNS/routing problem. Not sure if it applies to you.

The Glib errors I see quiet frequently in other apps when start from the command line. Don't know the reason, but I don't think its related to your problem. And the output from pref.js doesn't look out of sorts. Have you rebuilt/updated OpenSSL before emerging firefox?

FYI... FF -> Help -> Troubleshooting Information will bring up the page about:support. Maybe that can give you some insight as to what is going on behind the scenes.

Have you set up FF to sync? When you say gmail, are you accessing gmail via a web interface? Or via a mail program (thunderbird?) From the brief description, I'm thinking ssl/https issues. But that's just a guess. More info, please?

Not a problem. Unstandable. I wasn't attentive enough during my emerging process to see what was being updated and/or removed. So reporting it "after the fact" without details doesn't help. The whole situation was just disturbing. THX for trying :)

Thinking this through, it feels similar to the recent issue experienced with another ebuild. An ebuild was not updated because of USE flags being changed.

Kind of shocking to emerge/reboot and not be able to find drive space. This shouldn't happen. Installed functionality shouldn't "normally" disappear. For the record: - smartd doesn't report drive errors with device storing /. - was root when I went to check mdadm Other than what I have posted in the forums/bugs in the past, not really. I just fixed and moved on as I was more worried about my system than diagnosing a possible portage/emerge issue. Sorry. Had to rant a little. My bad :(

Well that was disconcerting... I just finished an emerge on my file server and followed it up with a reboot. Strange, I couldn't find my raid device!?!?!?! I did an mdadm -D devicename only to be told that mdadm as command was not recognized. ????? o_O Sure enough, sys-fs/mdadm had disappeared from my system. But I didn't remove that ebuild... Re-emerged, etc-update, rc-update, rc-service and remount...back to normal. Its these surprises with emerge that are starting to wear on me.

I have systems set to use the desktop profile. But I just noticed during an emerge that the new ebuild "app-laptop/radeontool" was installed. From the ebuild: DESCRIPTION="Manage the backlight, external video output and registers of ATI Radeon graphics cards"I'm a little confused by the "app-laptop" part. Is this ebuild being installed/enabled by default now for desktop systems with ATI/Radeon cards?

One thing I've noticed with Xorg. After emerging, I had to reboot. Then drivers seemed to respond. Just a suggestion

A bit of a side track discussion to OP. But I had to ask. Not OP's problem. THX

General Question... If you have a ufei machine with secure boot enabled, what happens when you try to boot a live-cd OS?

Maybe I'm wrong, but I don't think we've hit seeing use flags yet. upc0d3 gets a kernel panic with System Rescue CD. Something is not good with the setup. Collectively we're missing something.

Or there is an aspect to cpu/hw you're missing. Like efi? Not sure. Not familiar with later intel's. A quick google search for "haswell kernel panic" didn't give me anything conclusive.

Daniel, Appreciate the thought. I saw some of the bug reports that came through in the aftermath after the upgrade. It probably put stress on those few devs. They work hard to put something out and then have to work harder in the aftermath. If I felt more confident about helping, I'd be right there with you folks digging into the code/ebuilds... THX :)

This speaks to the idea of planning upgrades rather than just surprising people with the aftermath. Yes, please.

If you follow the steps on kernel building on the wiki page, that's pretty much it. Cool, right?

Oleg, I very much appreciate your answer, but I'm confused as I think my question is not being addressed. To install icedtea -> emerge icedtea-bin then emerge icedtea. Got it. However, virtual/jdk will, by default, install oracle-jdk-bin. And from you suggestions above - this can't be changed as it is the default. So virtual/jdk is tied to the oracle-jdk-bin. So choices for java are... 1) install virtaul/jdk to get the default oracle-jdk 2) manually install icedtea-bin then icedtea. I hope you can see the confusion I'm having here about the purpose of the virtual ebuild if choices are limited.

A little confused. Maybe I'm misunderstanding how virtual ebuilds work. The web page suggest to emerge virtual/jdk which will pulling in oracle's jdk. So with a virtual ebuild, if a user wants to install icedtea, they would have to expressly install their jdk of choice afterwards? A user would have two jdk's installed? Yes?/No?

If the hardware is same/similar you might be okay. Rather than sending a HD, maybe use a USB/DVD drive? It may be safer and a means of support to image the harddrive, send the image (DVD etc) with a copy of the System Rescue CD and instructions to put the image on the drive. Just thinking out loud - HD could get damaged in shipping After install, you could also to restore the data on to the the newly imaged drive(Extract a tar.gz or tar.bz2). Just a suggestion.

A choice more than anything else. I haven't had problems using icedtea before. Also, it would seem incomplete to say in the wiki page "you can have these options" but not say how to enable those options.