Re: Hulu and 64 bit linux firefox
by Patrick Bartek
--- On Wed, 4/28/10, Henry Wyatt <hewjr1000(a)gmail.com> wrote:
> Has anyone experienced problems playing videos in Hulu with 64 bit Firefox
>
> I get the following message:
>
> “Were sorry but we are unable to stream video to your system, this may
> be due to a limitation of Adobe software on 64 bit Linux”
Yes. The "problem" appeared about 6 to 8 weeks ago. It's specific only to 64-bit Flash, it seems, and not just Firefox. And the "problem" appears with any other video streaming sight that uses Hulu to get its content like Fancast and AOL's SlashControl. Plus, it's not specific to Linux. 64-bit Windows and OSX users are experiencing it, too, last time I checked about 6 weeks ago.
There's no problem with 32-bit systems running 32-bit Flash. Streams just fine. Some 64-bit Linux users are "wrapping" 32-bit Flash with their 64-bit browsers, but that "fix" doesn't always work. Others are just using a 32-bit browser with 32-bit Flash on their 64-bit systems, which seems to work well. Or you can run 32-bit Linux in a VM, which works pretty much 100% of the time. (I tried several "lightweight" distros, but the LiveCD or "minimal" versions of Scientific Linux (installed) were the smoothest on my Athlon64 X2 2.9 GHZ, 4 GB RAM system.) Or you can install the Beta of Hulu's Desktop player (They have a Linux version, 32 and 64-bit) which works fine on my 64-bit Fedora 12 system, but navigating to get to the video you want to watch is a pain in the butt. Takes 3 times longer than the stock Hulu site to do the same thing. (Hulu spent too much effort on the "coolness", and not enough on "ease of use".) Because of that last thing, I've,
of late, been streaming what TV shows I can directly from the network web sites.
No word from Hulu about why the problem or if they are trying to fix it. And believe me a lot of Hulu users asked, including me. I just got a "canned" reply. My guess is they aren't doing anything. Why not, I don't know.
B
14 years
Re: recent network breakage on f12?
by Michael McConnell
users-request(a)lists.fedoraproject.org wrote:
> From: wolfgang.rupprecht(a)gmail.com (Wolfgang S. Rupprecht)
>
> I'm seeing several of my laptops fail to get a dhcp lease after the
> April-23 yum update for f12. The server sees the dhcp request and
> issues the correct IP address, but the client never seems to act upon
> it. Both eth0 and wlan0 never have IPv4 addresses assigned. Strangely
> IPv6 addresses do get assigned correctly (bith link-local and global) so
> it isn't a case of the ethernet or wlan being down. Those requests do
> go out and the reply gets acted upon.
>
> Both NetowrkManager and dhclient were updated within the last two days.
> I wonder if something is broken there. Are other folks seeing the same
> breakage?
I'm seeing network - and bluetooth - breakage. I did a 'yum update' on
Saturday, and I've been unable to connect to the internet using
bluetooth since. Connecting my phone also no longer shows up in the
Mobile Broadband section of NetworkManager.
It's now also prompting me for the root password when I change the CPU
speed setting. All very strange.
From my log when I try to connect to my Nokia phone with PANU:
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) starting connection 'Honami - PANU'
Apr 26 22:22:59 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A):
device state change: 3 -> 4 (reason 0)
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 1 of 5 (Device Prepare) scheduled...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 1 of 5 (Device Prepare) started...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 2 of 5 (Device Configure) scheduled...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 1 of 5 (Device Prepare) complete.
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 2 of 5 (Device Configure) starting...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A):
device state change: 4 -> 5 (reason 0)
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 2 of 5 (Device Configure) complete.
Apr 26 22:22:59 Sonozaki bluetoothd[1139]: link_key_request
(sba=00:15:83:07:CD:17, dba=00:26:69:63:4E:0A)
Apr 26 22:22:59 Sonozaki bluetoothd[1139]: bnep0 connected
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A bnep0/bluetooth) Stage 2 of 5 (Device Configure)
successful. Will connect via PAN.
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 3 of 5 (IP Configure Start) started...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A):
device state change: 5 -> 7 (reason 0)
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation (bnep0)
Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 26 22:22:59 Sonozaki NetworkManager: <info> dhclient started with
pid 3344
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 4 of 5 (IP6 Configure Get) scheduled...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 3 of 5 (IP Configure Start) complete.
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 4 of 5 (IP6 Configure Get) started...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 4 of 5 (IP6 Configure Get) complete.
Apr 26 22:22:59 Sonozaki dhclient[3344]: Internet Systems Consortium
DHCP Client 4.1.1
Apr 26 22:22:59 Sonozaki dhclient[3344]: Copyright 2004-2010 Internet
Systems Consortium.
Apr 26 22:22:59 Sonozaki dhclient[3344]: All rights reserved.
Apr 26 22:22:59 Sonozaki dhclient[3344]: For info, please visit
https://www.isc.org/software/dhcp/
Apr 26 22:22:59 Sonozaki dhclient[3344]:
Apr 26 22:22:59 Sonozaki dhclient[3344]: Listening on
LPF/bnep0/00:15:83:07:cd:17
Apr 26 22:22:59 Sonozaki dhclient[3344]: Sending on
LPF/bnep0/00:15:83:07:cd:17
Apr 26 22:22:59 Sonozaki dhclient[3344]: Sending on Socket/fallback
Apr 26 22:22:59 Sonozaki dhclient[3344]: DHCPDISCOVER on bnep0 to
255.255.255.255 port 67 interval 8
Apr 26 22:22:59 Sonozaki NetworkManager: <info> (bnep0): DHCPv4 state
changed nbi -> preinit
Apr 26 22:23:01 Sonozaki avahi-daemon[887]: Registering new address
record for fe80::215:83ff:fe07:cd17 on bnep0.*.
Apr 26 22:23:07 Sonozaki dhclient[3344]: DHCPDISCOVER on bnep0 to
255.255.255.255 port 67 interval 19
Apr 26 22:23:07 Sonozaki dhclient[3344]: DHCPOFFER from 192.168.66.1
Apr 26 22:23:07 Sonozaki dhclient[3344]: DHCPREQUEST on bnep0 to
255.255.255.255 port 67
Apr 26 22:23:07 Sonozaki dhclient[3344]: DHCPACK from 192.168.66.1
Apr 26 22:23:07 Sonozaki dhclient[3344]: bound to 192.168.66.2 --
renewal in 1375 seconds.
Apr 26 22:23:07 Sonozaki NetworkManager: <info> (bnep0): DHCPv4 state
changed preinit -> bound
Apr 26 22:23:07 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 4 of 5 (IP4 Configure Get) scheduled...
Apr 26 22:23:07 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 4 of 5 (IP4 Configure Get) started...
Apr 26 22:23:07 Sonozaki NetworkManager: <info> address 192.168.66.2
Apr 26 22:23:07 Sonozaki NetworkManager: <info> prefix 28
(255.255.255.240)
Apr 26 22:23:07 Sonozaki NetworkManager: <info> gateway 192.168.66.1
Apr 26 22:23:07 Sonozaki NetworkManager: <info> nameserver
'193.35.132.165'
Apr 26 22:23:07 Sonozaki NetworkManager: <info> nameserver
'193.35.132.164'
Apr 26 22:23:07 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 5 of 5 (IP Configure Commit) scheduled...
Apr 26 22:23:07 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 4 of 5 (IP4 Configure Get) complete.
Apr 26 22:23:07 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 5 of 5 (IP Configure Commit) started...
Apr 26 22:23:07 Sonozaki avahi-daemon[887]: Joining mDNS multicast group
on interface bnep0.IPv4 with address 192.168.66.2.
Apr 26 22:23:07 Sonozaki avahi-daemon[887]: New relevant interface
bnep0.IPv4 for mDNS.
Apr 26 22:23:07 Sonozaki avahi-daemon[887]: Registering new address
record for 192.168.66.2 on bnep0.IPv4.
Apr 26 22:23:08 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A):
device state change: 7 -> 8 (reason 0)
Apr 26 22:23:08 Sonozaki NetworkManager: <info> Policy set 'Honami -
PANU' (bnep0) as default for routing and DNS.
Apr 26 22:23:08 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) successful, device activated.
Apr 26 22:23:08 Sonozaki NetworkManager: <info> Activation
(00:26:69:63:4E:0A) Stage 5 of 5 (IP Configure Commit) complete.
Apr 26 22:23:29 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A):
device state change: 8 -> 9 (reason 44)
Apr 26 22:23:30 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A):
device state change: 9 -> 3 (reason 0)
Apr 26 22:23:30 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A):
deactivating device (reason: 0).
Apr 26 22:23:30 Sonozaki NetworkManager: <info> (bnep0): canceled DHCP
transaction, DHCP client pid 3344
Apr 26 22:23:30 Sonozaki avahi-daemon[887]: Withdrawing address record
for 192.168.66.2 on bnep0.
Apr 26 22:23:30 Sonozaki avahi-daemon[887]: Leaving mDNS multicast group
on interface bnep0.IPv4 with address 192.168.66.2.
Apr 26 22:23:30 Sonozaki avahi-daemon[887]: Interface bnep0.IPv4 no
longer relevant for mDNS.
Apr 26 22:23:30 Sonozaki avahi-daemon[887]: Withdrawing address record
for fe80::215:83ff:fe07:cd17 on bnep0.
Apr 26 22:23:30 Sonozaki dbus-daemon: Rejected send message, 2 matched
rules; type="method_return", sender=":1.12" (uid=0 pid=1124
comm="/usr/sbin/bluetoothd) interface="(unset)" member="(unset)" error
name="(unset)" requested_reply=0 destination=":1.0" (uid=0 pid=876
comm="NetworkManager))
Apr 26 22:23:30 Sonozaki bluetoothd[1139]: bnep0 disconnected
It appears to connect, then a few seconds later it gets pulled down again.
How do I get my machine back to the state it was pre Saturday's updates?
-- Michael "Soruk" McConnell
14 years
Epiphany slow to load some sites ?!? -- Repost
by Bill Case
Hi;
Epiphany, which used to be my fastest browser, has slowed right down
when loading some sites. About 50% of them.
I filed a bug a couple of months ago. The report back was that "Can't
fix. An Adobe Flash problem." Is this then the final answer for me?
Can I no longer use epiphany? Is there a new Flash package I can
download from Adobe Systems Incorporated? I didn't see one.
Can anyone expand on what is happening to Epiphany. The Gnome mail list
and forum are useless.
Original sent: 04/26/2010 01:55:10 PM
This has been re-posted because it is an important issue to me.
--
Regards Bill
Fedora 12, Gnome 2.28
Evo.2.28, Emacs 23.1.1
14 years
cifs mount returns random garbage
by Neal Becker
I'm trying to do cifs mount to some kind of networked storage we have here
at my job. I don't know what kind of box it is, but it doesn't play nice
with samba, apparently.
Sometimes (maybe the 1st time?) I mount, it seems normal. I can do ls and
it looks fine.
Other times, I mount and ls returns random results. Repeating ls gives
different random characters and messages.
Any ideas?
14 years
F12 Firefox pwd trouble
by Beartooth
Firefox insists, whenever I let it change a password, on
making those for two lists on the same domain (one that I run, and one
that I help run) the same. There are actually four different passwords,
what with owner and moderator for each list. Is there a fix for this??
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.
14 years
Movie Player
by Henry Wyatt
have a dvd with 2 movies on each side (Abbott and Costello) when i attempt
to play I get the following message
“An error occurred could not read from resource”
The menu does come up the error occurs when I click on the movie I wish to
see. I flipped dvd voer and tried again same results.
Have not tried with a single movie dvd yet.
--
Henry E. Wyatt, Jr.
14 years
Java no longer works in Konqueror
by Patrick O'Callaghan
[Apologies to those who already saw this on the Fedora-KDE list. I
posted there 24 hours ago and got not a single reply, so I hope this
doesn't count as cross-posting]
I don't use Java much (basically just for the New York Times Acrostic
puzzle every two week) but it seems to have stopped working in
Konqueror. It definitely did work 2 weeks ago, and I'm not aware of
changing anything in either Java or the configuration of Konq. In fact
the config looks fine, the Java binary exists, Java is enabled on all
pages, I cleaned the Konq cache and reloaded, and nothing works. Not
even the Java test page at http://java.com/en/download/help/testvm.xml
kdebase-4.4.2-1.fc12.x86_64, F12 fully updated
"Path to Java executable": java-1.6.0-openjdk-1.6.0.0-37.b17.fc12.x86_64
Opening the same page in Firefox works. FF uses the same Java rpm, but
with the
plugin /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/IcedTeaPlugin.so
poc
14 years
OT: Installing non-RHEL packages during kickstart
by Jamie Bohr
Hello,
I have searched around and found no reference to installing a custom RPM
during kickstart installation from a Red Hat Satellite server.
The unsigned RPM is associated with the channel and activation key yet does
not get installed during my kickstart. Can someone give me some advice or
a pointer on how to install an unsigned custom RPM package during an
kickstart from a Red Hat Satellite server?
Thank you,
--
Jamie Bohr
14 years
Re: System hang on reboot after FC12 upgrade
by philbrog
> Hi,
>
> I upgraded from FC11 to FC12 and system hangs during reboot. I removed RHGB from the boot command line and I see 4 occurrences of this error message:
>
> Missing /etc/sysconfig/network-scripts/network-functions, exiting.
This suggests a severely corrupted system.
> Then this message:
>
> /etc/sysconfig/network-scripts/ifup-eth: line 298: 858 segmentation fault /sbin/dhclient ${DHCLIENTARGS} ${DEVICE} failed. [FAILED]
This too.
>
> Then these error messages:
>
> Starting NFS daemon: rpc.nfsd: unable to resolve ANYADDR:nfs to inet address: Name or service not known
> Rpc.nfsd: unable to set any sockets for nfsd [FAILED]
This, and the remaining error messages are a consequence of the first two,
and are immaterial.
> System hangs at this point. Any help is appreciated, thank you.
You have major system corruption. First, review your installation/upgrade
process, if you remember for any hint as to what went wrong. If there's any
hint of a problem with an upgrade, it should be cancelled immediately,
rather than forging ahead, blindly.
Next, boot and append "1 forcefsck" to your kernel boot command, resulting
in a full fsck and a boot into run level 1. This checks your filesystems to
verify that they're in a consistent state, then throws you into a root
shell, skipping most of the initialization.
Then, run "rpm --rebuilddb" to check and make any necessary repairs to your
RPM database. Afterwards, you'll have to use some elbow grease to identify
which packages weren't properly installed, and reinstall them via yum or
rpm. The missing network-functions script is from the initscripts package,
for example, so at the bare minimum you'll need to reinstall initscripts.
It's almost a certainty that you have a long list of broken packages to
reinstall, not just initscripts. Like dhclient. And probably many others.
-----------------
The FC12 install went fine, no error messages were reported. I would have stopped it if I had seen any errors.
I booted and forced an fsck (successful), and then to runlevel 1. I ran rpm --rebuilddb successfully.
I don't have time for the remaining steps you suggest, I just want to copy some files from it, and then install net-new. Given the current state of my system, will I be able to copy files to a USB drive or CD-ROM?
Thanks again for your time and help.
Sent via BlackBerry by AT&T
14 years
bittorent-error display
by Paolo Galtieri
Sometimes when I run bittorent-curses to download an iso image it will
display an error message. This error shows up in bold just below the
"peers: 0 seen now" line. The problem is that only the first 80
characters of the message are visible. In order to see the full text of the
error I have to stretch the gnome-terminal window. I don't know if this is
a bittorent curses error or a gnome-terminal error, but it seems strange
that which ever of the two is at fault is unable to make the full error
message fit in the 24x80 window.
Has anyone else seen this?
Paolo
14 years