I've encountered, and discovered a workaround for a very similar bug in
the Ubuntu (8.04) Firefox (3.0.3) Modification (0.5) add-on. The Ubuntu
Modification add-on is installed by default.
Several pages at www.newscientist.com would cause the browser to crash
and close suddenly. I disabled my
Public bug reported:
Binary package hint: thunderbird
With Thunderbird 2.0.0.18 running under Ubuntu 8.04, I received a
message with a large, attached MS Word file. I saved the attachment in
my Windows XP Documents directory with no problems, then decided to
save the email as well, using
This is a really old post, and I hadn't thought about this matter in a
very long time. For what it's worth, I later found that removing the
Ubuntu addon did not entirely eliminate the mysterious Firefox crashes
in 8.10, and this was one of the reasons I soon upgraded to 9.04. The
problem
Public bug reported:
Binary package hint: thunderbird
Under Ubuntu 9.04, kernel 2.6.28-13-generic 64-bit, Thunderbird version
2.0.0.21 (20090409) x86_64 will not assume date and time settings specified the
Environment file. With the 32-bit version, to have American English as the
default
This is a known issue in Thunderbird, and a script to fix the problem
has been included in the New Wave directory. If you'll copy
/usr/share/themes/New Wave/userChrome.css
to the directory
go to ~/.mozilla-thunderbird/x.default/chrome/
Thunderbird should now have white text on a gray
I just downloaded and installed the latest e1000e NIC driver from Intel.
This seems to help though it's still not perfect. Whereas it was taking
up to half a dozen reboots before I could finally get a connection, of
the last three reboots, two have resulted in a network connection.
--
Possible
This will be my last comment on this thread, because the new Intel
driver has essentially solved the problem. At most, there's now a
failure-to-connect only 1 out of 4 or 5 boots, which is good enough for
me. Seems to me that it would behove the Ubuntu developers at this point
to either take
Yes, sorry the info was so sketchy. I didn't mention that the NIC in
question was an Intel 82566DC, which might have been pertinent, and it
certainly didn't occur to me that I could save the output of apport to a
file. I've attached the saved apport output here.
** Attachment added: apport output
Whoops! Suddenly, the wired network seems to be connecting, though
nothing, as nearly as I can tell, has changed. Earlier, I had tried to
connect several times from the live CD, then I put system onto a USB
stick, so I could boot from that, again confirmed that the network still
remained
The issue is still with us following full install! I went ahead and
installed Maverick onto the hard drive. Sometimes it gets an IP number
and connects, sometimes not, and there doesn't seem to be any particular
thing that I can do during bootup to insure that it does or doesn't
connect. Attached
Public bug reported:
Binary package hint: network-manager
When running live-CD of AMD64 Maverick (Ubuntu 10.10), no IP number is
assigned, and no connection is made with wired router. A perusal of
Ubuntu forums reveals at least one other instance of a system using an
Intel PCI-e NIC with a
Regression! With the latest kernel update, 2.6.35.23, the network
doesn't connect at all. I had to boot 2.6.35.22 to even get online to
send this message. I suppose it's possible that by manually installing
the updated Intel driver with 2.6.35.22, I broke the update chain. I'll
try re-installing
Ok, on the off-chance that somebody, somewhere might actually be reading
these entries and following the thread, let me say that re-compiling and
installing the latest e1000e NIC driver from Intel fixes the problem
with kernel 2.6.35.23 just as it did with 2.6.35.22.
--
Possible issue with
--
Thunderbirds fails to write file to NTFS partition properly
https://bugs.launchpad.net/bugs/302762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
14 matches
Mail list logo
