[ PARTIALLY SOLVED ] Cannot upgrade to gutsty gibbon, Almost there !!

[kalamari]

Hello all,

I have not been able to upgrade to gutsy gibbon.
I am current on Kubuntu Fiesty Fawn.

1. I have applied all the available updates using Adept Updater and currently it does not show any more new upgrades. No option to upgrade to gutsy.

2. I downloaded and burned the Kubuntu Alternate CD for gutsy and i get the following error while trying to run cdromupgrade.

:~# sh /media/k710/cdromupgrade
/var/lib/python-support/python2.5/gtk-2.0/gtk/__init__.py:69: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
/tmp/tmp.NHGPa15786/DistUpgradeViewGtk.py:347: GtkWarning: gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
icons = gtk.icon_theme_get_default()
Traceback (most recent call last):
File "/tmp/tmp.NHGPa15786/gutsy", line 57, in <module>
view = view_class(logdir=logdir)
File "/tmp/tmp.NHGPa15786/DistUpgradeViewGtk.py", line 349, in __init__
gtk.window_set_default_icon(icons.load_icon("update-manager", 32, 0))
AttributeError: 'NoneType' object has no attribute 'load_icon'


Can anyone please help ?

Thanks,

[integr8e]

Press Alt+F2 and type the command

kdesu "adept_manager --version-upgrade"

See if that helps any . . .

Note: the quotation (" ") marks are important in this case :)

[kalamari]

Works .. starting to upgrade ....

Will post back with results.

Thanks a lot.

[kalamari]

The upgrade tool launched .. and was proceeding until it stopped with the following error.

Failed to fetch http://archive.ubuntu.com/ubuntu/dists/feisty/universe/binary-amd64/Packages.gz Sub-process gzip returned an error code (1)
Failed to fetch http://archive.ubuntu.com/ubuntu/dists/feisty/main/binary-amd64/Packages.gz Sub-process gzip returned an error code (1)

Could be something trivial.. am searching .. haven't got anything yet.

[integr8e]

Let me know how it goes.

Note: If it begins installing Gutsy's packages, and you run into errors, don't click the OK button, that will return your computer to its previous state and you'll lose everything it has done so far; instead, press Ctrl+Alt+Esc and click the installer to close it. Doing this will allow you to keep the Gutsy repos. Open Konsole and type

sudo apt-get install -f

then,

sudo dpkg --configure -a

Followed by

sudo apt-get update

and

sudo apt-get upgrade

This should upgrade you to Gutsy (kinda' dirty, so make sure you backup all your important information, but you should do that anyway :P)

[kalamari]

The error i described above happened during

step 1 : Preparing the upgrade

I was searching for the error and some hits turned up on how similar issues could be resolved by changing the respository.

Changing the url from http://archive. to http://us.archive. that seems to have solved this particular problem. It completed step 1 and moving on.

I understood your comment on how to resume after errors once it starts installing gutsy upgrades .. will keep that in mind.


Step 2: Modifying the software Channels .. completed with a warning

It warned me that support for certain applications are not available anymore.

Does that mean i will have to say yes to removing those components ?

Thanks for the quick responses.

[integr8e]

You can choose yes, it won't hurt anything. You'll be prompted for your input several times during the upgrade, it's safe just to choose the default answers.

[kalamari]

Moving on ..

Step 3 Fetching the Upgrades .. in progress.

This is going to be a while from the looks of it.

Fetching file 4/ 1735 @ 31.1 kb/s ..

Eagerly waiting....

[kalamari]

I was able to successfully upgrade to gutsy gibbon.

Thanks integr8e for your help.

but now am left with no network.


I tried
ip route

result:



162.254.0.0/16 dev eth0 proto kernel scope link src 169.254.4.237
default dev eth0 scope link metric 1000

[integr8e]

Can you ping google?

ping -c 1 www.google.com

Also, check to see if you can enable your connection through System Settings -> Network Settings -> Administrator Mode... -> eth0 -> Enable Interface. If not, and eth0 does show, click it, and choose Configure Interfaces. Check the Automatic option and set it to dhcp; also, make sure the Activate when computer starts option is checked, and reboot.

[kalamari]

I cant ping google.
I cant ping my router either.
I did enable my connection through System Settings -> Network Settings -> Administrator Mode... -> eth0 -> Enable Interface. chose Configure Interfaces. Checked the Automatic option and set it to dhcp; also, made sure the Activate when computer starts option is checked, and rebooted the machine.

with no luck . ???

[integr8e]

What does the command

ifconfig

give you?

[kalamari]

This the output of ifconfig on my gutsy.


~$ ifconfig
eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:20 Base address:0xb400

eth0:avah Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:169.254.9.22 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:17 Base address:0xb400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:50 errors:0 dropped:0 overruns:0 frame:0
TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4172 (4.0 KiB) TX bytes:4172 (4.0 KiB)

[kalamari]

Here is the story. not much of an ending.

After a few days of relentless forum reading and typing


ifconfig
ifdown eth0
ifup eth0
lspci
vim /etc/network/interfaces
vim /etc/resolv.conf
vim /etc/modprobe.d/blacklist <- to add ipv6
ping 192.168.5.1
ping google
tail -f /var/log/syslog

over and over and over again ....

finally this is what worked and as the post pointed by the link below says only till i reboot.

the holy grail for now is


sudo ethtool -s eth0 speed 10 duplex full autoneg off

From the post http://kubuntuforums.net/forums/index.php?topic=3086810.0

A few added notes.
I am not using a crappy network cable
It worked fine on feisty ..
Have tried a number of cables.

But at least now i have network !!!!

Need some help, should i leave it be ?? ???