Re: Loss of Administrative Privileges on Only Account
by Stephen Morris
On 12/1/20 04:18, Doug H. wrote:
> On Sat, 2020-01-11 at 23:54 +1100, Stephen Morris wrote:
>> Hi,
>> By mistake I removed administration privileges from my
>> account
>> under kde, which is the only account that had it. Removing the
>> privilege
>> has removed my account from sudoers. Is the only course of action I
>> have
>> to get it back to reinstall F29 and then upgrage to F31?
> Nope, lots of simpler methods...
>
> 1. Of course, if you have the root password you can give your user
> sudo.
>
> 2. Boot to a maintenance CD and set a root password.
>
I don't have the root account enabled and I don't have a maintenance CD
for F31 as it was an upgrade from F30, which was an upgrade from F29.
regards,
Steve
>
>
>> regards,
>> Steve
>> _______________________________________________
>> users mailing list -- users(a)lists.fedoraproject.org
>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines:
>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
4 years, 3 months
Re: OT: recommendations for a low-volume, ,> cheap-to-use/maintain
home printer for use with Fedora 31
by R. G. Newbury
On Sat, Jan 11, 2020 at 7:15
> PM Samuel Sieb <samuel(a)sieb.net> wrote:
>> On 1/11/20 9:14 AM, Patrick O'Callaghan wrote:
>>> On Sat, 2020-01-11 at 23:18 +1030, Tim via users wrote:
>>>> On Fri, 2020-01-10 at 09:25 -0600, Ranjan Maitra wrote:
>>>>> the printing is largely of documents, but the printer sits for a
>>>>> while doing nothing. I guess laser is the way to go then? What are
>>>>> goog suggestions then?
Look around for a used HP laser printer. I am using an HP1320 which I
bought in May, 2005 for about $550 including an extra cartridge and tax.
HP cartridges are expensive! I have no idea how many cartridges I have
gone through, probably over a dozen, and it is as good as the day I
bought it. Drivers are included with cups or hplip. The bare HP1320
needs a ~$30 network print server if you want to network it, otherwise a
parallel port!
If you want print/fax/scan, then one of the all in ones or 'MFP'. I have
an HP3055 which I purchased in 2006 (to replace the fax machine which
had died). I mainly use it for scanning now. It has builtin network
capability. Again, the drivers are included in your basic install of
cups or hplip.
A good one will probably cost you $50-$75. Off-brand cartridges cost
about that. ATM there is an HP P2015d for sale used on kijiji.ca in the
Toronto area for $80Cdn. Physically it looks exactly like the HP1320 and
has duplex capability. So... $60US???
I happen to like HP printers, but Brother printers do the same thing and
are just about as dependable and long-lived. I've had Brother printers
too. The best scanner I have ever used is a Brother ADS-1000. Once did
over 650 pages in one continuous pass!
Geoff
--
4 years, 3 months
Completely replacing F31 Ethernet package(s)?
by Robert G (Doc) Savage
It would seem that "something" happened to the file(s) that provide
RJ45 Ethernet connectivity maybe as far back as F29. I can get a WiFi
connection, but not an RJ45 eth0 DHCP connection. This happens in my
home and at a nearby computer store, so it's not my DHCP server.
When booted up to WiFi, connecting an RJ45 Ethernet cable shuts down
the existing WiFi port (normal), but never comes up with a DHCP address
for the eth0 port. The network icon just loops forever. When I
disconnect the RJ45 cable, WiFi connectivity resumes after 5-10
seconds.
The problem has persisted since upgrades to both F30 and F31. I'm
guessing the best way to fix the problem is a fresh install of whatever
packages provide eth0 connectivity. I'm at a loss to know what those
packages are, and if there are any hidden potholes/landmines with
simply using dnf to first remove then to install them from scratch.
If it matters, I'm using the mate v1.22.2 desktop. Here are all the
*mate* packages I have installed:
# rpm -qa | grep mate | sort
classmate-1.3.1-7.fc31.noarch
f29-backgrounds-extras-mate-29.1.3-3.fc31.noarch
f29-backgrounds-mate-29.1.3-3.fc31.noarch
f30-backgrounds-extras-mate-30.1.2-2.fc31.noarch
f30-backgrounds-mate-30.1.2-2.fc31.noarch
f31-backgrounds-mate-31.0.4-1.fc31.noarch
fedora-release-matecompiz-31-2.noarch
imsettings-mate-1.8.1-2.fc31.x86_64
libmatekbd-1.22.0-2.fc31.x86_64
libmatemixer-1.22.0-2.fc31.x86_64
libmateweather-1.22.1-1.fc31.x86_64
libmateweather-data-1.22.1-1.fc31.noarch
mate-applet-softupd-0.4.7-4.fc31.x86_64
mate-applets-1.22.2-1.fc31.x86_64
mate-backgrounds-1.22.0-2.fc31.noarch
mate-calc-1.22.2-1.fc31.x86_64
mate-control-center-1.22.2-2.fc31.x86_64
mate-control-center-filesystem-1.22.2-2.fc31.x86_64
mate-desktop-1.22.2-1.fc31.x86_64
mate-desktop-libs-1.22.2-1.fc31.x86_64
mate-dictionary-1.22.2-2.fc31.x86_64
mate-disk-usage-analyzer-1.22.2-2.fc31.x86_64
mate-icon-theme-1.22.2-1.fc31.noarch
mate-media-1.22.2-1.fc31.x86_64
mate-menu-19.04.0-2.fc31.noarch
mate-menus-1.22.1-1.fc31.x86_64
mate-menus-libs-1.22.1-1.fc31.x86_64
mate-menus-preferences-category-menu-1.22.1-1.fc31.x86_64
mate-notification-daemon-1.22.1-1.fc31.x86_64
mate-panel-1.22.2-1.fc31.x86_64
mate-panel-libs-1.22.2-1.fc31.x86_64
mate-polkit-1.22.0-2.fc31.x86_64
mate-power-manager-1.22.2-1.fc31.x86_64
mate-screensaver-1.22.2-1.fc31.x86_64
mate-screenshot-1.22.2-2.fc31.x86_64
mate-search-tool-1.22.2-2.fc31.x86_64
mate-sensors-applet-1.22.1-2.fc31.x86_64
mate-session-manager-1.22.3-1.fc31.x86_64
mate-settings-daemon-1.22.1-1.fc31.x86_64
mate-system-log-1.22.2-2.fc31.x86_64
mate-system-monitor-1.22.2-1.fc31.x86_64
mate-terminal-1.22.1-3.fc31.x86_64
mate-themes-3.22.20-2.fc31.noarch
mate-user-admin-1.5.1-1.fc31.x86_64
mate-user-guide-1.22.3-1.fc31.noarch
mate-utils-1.22.2-2.fc31.x86_64
mate-utils-common-1.22.2-2.fc31.noarch
slick-greeter-mate-1.3.1-1.fc31.noarch
Some detailed guideance would be much appreciated.
Incidentally, I have appended " net.ifnames=0" to the
GRUB_CMDLINE_LINUX= line and rebuilt the initramfs to revert back to
classic eth0 nomenclature for the RJ45 Ethernet port. I can't stand the
new naming convention. :-)
--Doc Savage
Fairview Heights, IL
4 years, 3 months
How do I disable obfuscation of my email addresss on Fedora lists?
by Benjamin Lowry
Currently, the From: field on any emails I send to Fedora lists gets
obfuscated, like:
"Benjamin Lowry via users <users(a)lists.fedoraproject.org>"
How do I turn this behavior off? I'm fine with my real address getting
scraped by spambots or whatever. -ben
4 years, 3 months
Best way I've found to clone an OS.
by linux guy
I recently purchased a new computer. My old computer had Fedora 31
installed on an M.SATA drive. My new computer did not have an M.SATA
slot. I could have added one via a PCIe card, but decided against it.
I've been using Linux since RH8 days as my sole workstation. I've migrated
OSes from hard drive to hard drive many times. In the old days I'd do a
fresh install and then copy /home and try to reinstall all the apps I had
installed. It was a big PITA.
Even updates used to be problematic in the early days of Fedora... ;)
I hate migrating to a new computer. It can take a long time to get
everything set up just the way you want it. I've done migrations with dd
before, but there are always little issues with getting the new drive to
boot properly, copying directories that shouldn't be, etc. It works, but
it takes a bit of tweaking to make it work.
Today I had my best OS migration ever. It appears that everything came
across to the new drive perfectly, with just about zero hassle. In fact,
tonight I am forgetting that I'm operating on a new machine, except it is
twice as fast... :)
Here is how I did the migration:
Step #1 Create a Live USB of the same version as the old (source) machine.
Step #2 Boot the Live USB on the new (target) machine and install Fedora.
Step #3 Boot the newly installed OS on the target machine and run dnf
update. If you install a user, make it different from any on the source
machine.
Step #4 Run dnf update on the old (source) machine.
Both machines should now have the same OS vintage. You can double check
this by making sure both are running the same kernel.
Step #5 cp /etc/fstab on the target machine to somewhere safe, just in
case.
Step #6 Reboot the target machine with the Live USB.
Step #7 The target machine is now running the LiveUSB OS. Find the drive
partitions for swap, root (/), boot (/boot) and home (/home) for the new
drive on the new machine. Nautilus displays them as "Other locations..."
or something like that. They probably won't be mounted.
You'll need device handles for each partition on the new drive so that they
can be mounted. Ie /dev/sda1, etc.
The new OS drive on my new machine was an M.2 NVMe drive. It was
formatted into 4 partitions /dev/dm-0 (swap), /dev/dm-1 (home), /dev/dm-2
(root) and /dev/dm-3 (boot) by the live install process.
Step #8 create a mount point and mount the root partition on the new machine
#cd /mnt
#mkdir drive
# mount /dev/<root partition device>... drive
Step #9 mount the home partition to drive/home so that it looks like it
does on a regular Linux system.
#cd /mnt/drive
mount /dev/<home partition> home
At this point /mnt/drive should look like the root of a regular Linux
system, ie home, usr, bin, var... etc. The home partition on the new
drive will be mounted to /mnt/drive/home. You should cd into it just to
make sure.
DO NOT MOUNT THE ROOT PARTITION !
Step #9 use rsync to copy all the relevant files from the source computer
to the mounted directory structure.
From /mnt/drive, issue the following command:
sudo rsync -aHxv --numeric-ids --progress root@<sourceComputerIP>:/*
/mnt/drive --exclude=/dev --exclude=/proc --exclude=/sys --exclude=/tmp
--exclude=/boot --exclude=/etc/fstab
This command will copy all the relevant files from the source machine to
the directory structure we just made on the target hard drive.
Depending on how much you have installed on the source computer, this will
take a while. Make sure that both the network interfaces are operating as
fast as they can.
I saw file transfer speeds of 100 MB/sec for large files on 2 machines
networked with 1000 Mb/sec NICs. Small files don't reach that speed. The
CPU usage on the source machine ran at 25-30% on a quad core i7.
BTW, the source machine must be set up to allow root logins to ssh for this
to work. The commands on the source machine to enable this are:
#nano /etc/ssh/sshd_config
Find the commented like for PermitRoot and set it to: PermitRootLogin yes
#systemctl restart sshd.service
If you forget to run rsync from /mnt/drive and do it from / or specify the
target directory as /, you'll install the files on the Live USB file
structure instead of the target drive, thus messing it up ! No biggie,
just rebuild the Live USB and do this step over.
Step #10 Verify that /mnt/drive/etc/fstab is still in tact and the same as
what it was prior to the rsync operation. If not, replace
/mnt/drive/etc/fstab with the fstab file that was set aside. Do not copy
the backup fstab file to /etc/fstab as that points to the Live USB OS ! It
must be copied to /mnt/drive/etc/fstab.
(It took me several times to complete my clone drive because I kept
forgetting that the root of my target fs was /mnt/drive and thus I messed
up my Live USB drive a couple times.)
Step #11. Reboot the target computer using the new drive OS. We didn't
touch the /boot partition, so it should boot right up. However, the drive
partitions got written to outside of the OS, so they will be checked. This
can take a bit of time. Press ESC to watch this go on.
Once the boot process is complete, SELinux won't be happy and some of the
partitions will probably mount as read only.
To fix this problem, open a console session and issue the following
statement and reboot the computer.
#fixfiles onboot
#shutdown -r now
When the target computer reboots, a message will appear:
"Warning - SELinux targeted policy relabel is required....
It will start relabelling things. When it is done you should have an exact
clone of the install you had on the source computer.
The only potential issue I know of with this method is that the grub kernel
list doesn't match the kernels installed. Thus if you look in /boot there
will only be the kernels that were installed during the live install
process. But if you use dnf list kernel, you'll see the kernels that were
installed on the source machine. If this bothers you, use dnf to
uninstall and reinstall the kernels you want. Reinstalling the kernels
will enter them into grub properly. This problem will also take care of
itself over time as new kernels are installed via dnf update.
The only thing that didn't work exactly as it did on my source computer was
Eclipse and I"m not sure that had anything to do with the cloning.
I hope this helps someone.
4 years, 3 months
Wifi and sound broken after kernel upgrade 5.3.16 -> 5.4.7
by Benjamin Lowry
Hey everyone, I'm on Fedora 31 and recently upgraded my kernel from
5.3.16 to 5.4.7, and now my sound (via snd_hda_intel) and wifi doesn't
work; the wifi options in GNOME are missing, and my only sound device
is the default PulseAudio "Dummy Output". Everything works fine if I
manually select the old kernel in GRUB. Is this a known issue, and
should I file a bug about this?
# dmidecode -s system-version
ThinkPad X1 Carbon 7th
Here's the relevant log sections:
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: warning: No matching ASoC machine driver found
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: use msi interrupt mode
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Collecting data: trigger 15 fired.
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Status: 0x00000000, count: 1540278722
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Loaded firmware version: 48.4fa0041f.0
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xEDF689F1 | ADVANCED_SYSASSERT
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x64CB54DD | trm_hw_status0
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xF8687609 | trm_hw_status1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x308D2DCD | branchlink2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x6ADDA111 | interruptlink1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x1543DD43 | interruptlink2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x64802E76 | data1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x1DD12EFE | data2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x7716D38D | data3
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xDBC00F86 | beacon time
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xADE83137 | tsf low
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x33E55AED | tsf hi
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x8AC5F930 | time gp1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x71C94C4C | time gp2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xFEDB56F5 | uCode revision type
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xB1AC2681 | uCode version major
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xAF3B9842 | uCode version minor
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xFDAE5B60 | hw version
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x871997F8 | board version
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x4B1BD676 | hcmd
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x0E6EC2AE | isr0
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x88516878 | isr1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x1995D970 | isr2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xE6F00ADB | isr3
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xEADDC224 | isr4
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x6C9914F9 | last cmd Id
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x9A278D81 | wait_event
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x351FD4F6 | l2p_control
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x46D8FCD1 | l2p_duration
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x5DEA2927 | l2p_mhvalid
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x7DC7B996 | l2p_addr_match
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xD0C0BC2F | lmpm_pmg_sel
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x8B9718C9 | timestamp
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xBF827979 | flow_handler
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Status: 0x00000000, count: 7
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x201013F1 | ADVANCED_SYSASSERT
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xC008CF5C | umac branchlink2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000003 | umac data1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x20000302 | umac data2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x01300202 | umac data3
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000030 | umac major
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x4FA0041F | umac minor
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00005D11 | frame pointer
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xC0887F58 | stack pointer
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | last host cmd
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Fseq Registers:
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_ERROR_CODE
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | FSEQ_TOP_INIT_VERSION
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x2E66E477 | FSEQ_CNVIO_INIT_VERSION
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x11C5D9CE | FSEQ_TOP_CONTENT_VERSION
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xE02CC5D2 | FSEQ_ALIVE_TOKEN
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xDD1880B9 | FSEQ_CNVI_ID
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x5562D073 | FSEQ_CNVR_ID
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x20000302 | CNVI_AUX_MISC_CHIP
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x5c84, CPU2 Status: 0x3
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Failed to start RT ucode: -110
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Firmware not running - cannot dump error
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110
4 years, 3 months
Access to cbs.com failing with error 2002 or 2004??
by Michael D. Setzer II
Using Firefox was able to use it the other day with no problem, but then
yesterday started getting the 2002 or 2004 error message. Mentioned turning
off the new firefox tracker, but made no difference.
Rebooted the same machine to the old Windows 7 partition, and got the
same error with latest Firefox, but with windows, turning off the new tracking
made it go thru with no error. Contacted CBS, but no response yet..
Anyone else seen this, or have a solution..
Thanks.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned: 19,471
Processing time: 32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)
BOINC@HOME CREDITS
ROSETTA 66311323.990119 | ABC 16613838.513356
SETI 109804121.703177 | EINSTEIN 141859222.999240
4 years, 3 months