I recently installed OpenSuse 12.3 64bit and have been running for several weeks with no problems. However, in the recent round of updates there have been references to udev which fails to download… Other updates download and install normally… The same thing happens in Apper and Yast2 and in each case hangs the programme - will not abort or close - until I manually kill it. Today I tried the Zypper approach but with the same result. The download grinds to a halt after a minute or so leaving me as shown here
The following NEW patch is going to be installed:
openSUSE-2013-312
The following packages are going to be upgraded:
libgudev-1_0-0 libudev1 libudev1-32bit systemd systemd-32bit systemd-sysvinit
udev
7 packages to upgrade.
Overall download size: 2.0 MiB. After the operation, additional 4.0 KiB will be
used.
Continue? [y/n/?] (y): y
Retrieving package udev-195-13.18.1.x86_64 (1/7), 282.5 KiB (704.1 KiB unpacked)
Retrieving delta: ./x86_64/udev-195-13.14.1_13.18.1.x86_64.drpm, 124.1 KiB
Retrieving: udev-195-13.14.1_13.18.1.x86_64.drpm …<34%>===================/]
The system works fine without the update AFAIK but I would like to be able to resolve this.
I am a new to OpenSuse having been a Debian user up to now so it may be that I am missing something here.
I have not seen that in the last few years, but I have occasionally seen it in the past, where download attempts hang on a particular file.
Sometimes lowering the MTU for your network interface can help. If nothing else, that changes the way that the file is broken up into packets, and maybe that’s enough to get the file to download.
Use:
/sbin/ifconfig -a
and check the output to find the current MTU. You can change that (as root) with
# ifconfig eth0 mtu 1200
would set the MTU to 1200 for the “eth0” device. You would need to work out the correct device to use.
Any change you make that way will be temporary - until the next reboot.
If, by any chance you are on dialup, then this is unlikely to be the problem since dialup already uses a smaller MTU.
No guarantee this will help, but it is worth a try.
and check the output to find the current MTU. You can change that (as root) with
# ifconfig eth0 mtu 1200
would set the MTU to 1200 for the “eth0” device. You would need to work out the correct device to use.
Any change you make that way will be temporary - until the next reboot.
If, by any chance you are on dialup, then this is unlikely to be the problem since dialup already uses a smaller MTU.
No guarantee this will help, but it is worth a try.[/QUOTE]
Thanks for the suggestion although, as you feared it made no apparent difference.
I had wondered about network issues although it seems strange for it to be an problem for one specific file. My (rural) setup is a fixed wimax provider passed through a router to wlan0 on this box. As a user I sometimes find I need to do a reload on a browser window after the connection has been dropped/stalls. Is there a configuration of Yast2/Apper which would increase either the number of connection attempts or timing of them?
> I had wondered about network issues although it seems strange for it to
> be an problem for one specific file.
There was some time ago (version 11.4) a network bug that indeed
triggered on a certain file, or probably a pattern of bytes. It has not
been officially solved. It only affected certain hardware, or rather a
driver (“ethernet adapter 3C905CX-TX/TX-M Fast Etherlink for PC
running with driver 3c59x”)
There was some time ago (version 11.4) a network bug that indeed
triggered on a certain file, or probably a pattern of bytes. It has not
been officially solved. It only affected certain hardware, or rather a
driver (“ethernet adapter 3C905CX-TX/TX-M Fast Etherlink for PC
running with driver 3c59x”)
Thanks for that Carlos. It gets me no further but at least confirms that I am not alone with the issue.
The problem is remarkably inconsistent as what may work on one occasion fails later. Yesterday morning the original ‘problem file’ was willing to update but another update collection failed. In pursuit of solutions I checked the router configuration as routers had been fingered for a similar non OpenSuse issue and found an router software update which was duly installed. I also slowed down the transmission rate on the wireless side… I tried a Yast install (Wine) after this which ran quite well for a while,even with large files but eventually ground to a halt in the usual fashion on a large file…
I guess I’ll keep fiddling with it in case some other random ‘miracle’ occurs!