Last kernel breaks aMule's kad UDP Sockets

[XMouse]

The last kernel update: linux-image-3.13.0-63-generic:amd64 (3.13.0-63.103) makes aMule unable to connect to kad net. Neither UPnP nor manually assigned IP:Ports work.

Here is aMule's error message: MuleUDPSocket: Client UDP-SocketSocket died, recreating.
It is repeated in an infinite loop, always trying to connect to established kad UDP port.

It is not an aMule bug, it appeared when I rebooted the system after the last kernel upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-63-generic:amd64 (not installed)
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.16
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: diego 2395 F.... pulseaudio
 /dev/snd/controlC0: diego 2395 F.... pulseaudio
CurrentDesktop: XFCE
Date: Mon Oct 26 20:27:35 2015
HibernationDevice: RESUME=UUID=bbe06c01-6bcc-4c59-b165-6dca08ad6886
InstallationDate: Installed on 2015-01-09 (290 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723)
MachineType: System manufacturer System Product Name
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic root=UUID=48e0f8a2-b16d-4449-971a-21be22d6d7f0 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-66-generic N/A
 linux-backports-modules-3.13.0-66-generic N/A
 linux-firmware 1.127.15
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0308
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A58M-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0308:bd02/20/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Luis Henriques (henrix)]

This is likely a duplicate of bug #1508510. I'm marking it as such, please have a look at that bug and see if the test kernel or the kernel currently in -proposed fixes this issue for you. Thanks!

[XMouse (xface)]

I am not an expert user and I will not be playing with the system kernel. The previous kernel fixes the problem and the one thing i have to do to work with it is to choose it in the GRUB, so i will maintain it until a new bug-free one appears, but thanks for your tip.

[Ganton (ganton)]

Hi! The same happens there.

Each time the computer is rebooted with this kernel:
    $ uname -a
    Linux tp 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
then everything works correctly.

However, if the computer is rebooted with this kernel:
    $ uname -a
    Linux tp 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
then e.g. Amule is unable to connect to the Kad/Kademlia network, and a lot of those errors are seen:
    MuleUDPSocket: Client UDP-SocketSocket died, recreating.
every time.

[XMouse (xface)]

The new 3.13.0-67-generic kernel solves the problem.

Thanks for your help and sorry for not being a too technical user.

[Ganton (ganton)]

AFAIK the latest kernel
    $ uname -a
    Linux tp 3.13.0-67-generic #110-Ubuntu SMP Fri Oct 23 13:24:41 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
has solved it, good job!