I just upgraded to the Gutsy and it seems to be working fine.
--
Wireless no longer works after upgrade
https://bugs.launchpad.net/bugs/96532
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Last week, I was back at my friends place, where I happened to be when I
originally upgraded to Feisty and reported this bug. I was surprised
that Network-Manager immediately connected to the router there with no
problems (without nm-applet running). I happily used my laptop for
several days.
Well, I tried the orinoco drivers. I still can't connect. At least I
am not getting a keyboard lockup. I am tired of dealing with this bug.
It seems clear to me that NetworkManager is too buggy for a stable
release. I should have stuck with Edgy where wireless networking worked
fine. I have
Ok. That worked, partially. The NetworkManager applet now shows my
router and several other networks. However, it doesn't connect. The
applet spins for a while and then the laptop hangs. The keyboard is
unresponsive. I have to remove the battery in order to reboot. This
doesn't happen with a
I did all of those things already. to make things easier disabled encryption
on my linksys router.
However, there is not much I can do because of this keyboard lockup that
happens. It seems to be only the keyboard. I can navigate with the mouse but
am unable to do a shutdown. The keyboard
Yes, I was using update manager.
--
Edgy to Feisty: Kernel not updated - kernel panic
https://launchpad.net/bugs/96545
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have gotten it to work. Maybe it was working all along. However, the
Network Manager applet shows no network connection. I also have Wifi-
radar installed and it shows no signal. I saw in /etc/wlan wlan-
udev.sh, so I ran it to see if it would do anything. I also ran ifup
wlan0. Network
You are correct. Crash was caused by the firekeeper extension.
Removing it corrected the problem. I shouldn't run alpha software on a
beta Linux release.
I was running 2.0.0.2 when I originally reported.
I am now running 2.0.0.3.
--
Firefox segfaults in Feisty
https://launchpad.net/bugs/96534
** Attachment added: /etc/network/interfaces
http://librarian.launchpad.net/7036222/interfaces
--
Wireless no longer works after upgrade
https://launchpad.net/bugs/96532
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I removed /etc/network/interfaces and NetworkManager was able to detect
the network. However it would not connect. I had to re-enable
/etc/network/interfaces to be able to connect. Why does Ubuntu have two
different and conflicting ways of configuring a network? (I presume
that the Network
crash report file attached
** Attachment added: Firefox crash report
http://librarian.launchpad.net/6996162/_usr_lib_firefox_firefox-bin.1000.crash
--
Firefox segfaults in Feisty
https://launchpad.net/bugs/96534
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
After upgrading from Edgy to Feisty beta on my Thinkpad T30 laptop,
wireless no longer works. It seems like the wireless doesn't even turn
on, as it doesn't show any signal being detected. I have wifi-radar
installed. It shows nothing. Wireless was working under 6.10, in
Public bug reported:
Binary package hint: firefox
After upgrading to Feisty beta on my Thinkpad T30, Firefox segfaults on
startup.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Firefox segfaults in Feisty
https://launchpad.net/bugs/96534
--
Public bug reported:
When doing a dist-upgrade from Edgy to Feisty, it seems that the kernel
did not get upgraded in the process. When I tried to boot the maching
(Thinkpad T30), I got a kernel-panic. Fortunately, I had a Dapper CD
available to boot from, and after much searching of forums, I
*** This bug is a duplicate of bug 67028 ***
I got the same kernel panic. It seemed to be the result of the Kernel
not being upgraded to the latest. I was able to upgrade the kernel by
booting from an old Ubuntu CD and chrooting to the proper partition. I
also had the firestarter problem.
--
15 matches
Mail list logo
