Ubuntu 15.04: Unable to use Huawei E3131 USB 3G modem

[aljosa]

Hello,
in order to contribute to quality improvement of the new Ubuntu 15.04, I'm reporting problems I found in this "beta" version - related to 'Huawei E3131 USB 3G modem' and pastebinit command:

lsusb
Bus 004 Device 002: ID 8087:8000 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8008 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 13d3:5188 IMC Networks
Bus 001 Device 004: ID 062a:3633 Creative Labs
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 002: ID 12d1:14fe Huawei Technologies Co., Ltd.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

When I was on Ubuntu 14.04, the only possible way to use 'Huawei E3131 USB 3G modem' was to turn off my notebook, insert usb modem and then turn the notebook on again.
Now, on Ubuntu 15.04, if I insert usb modem while notebook is turned on, I see a new icon that appears in launcher, and that's all. Nothing happens later, even if I try to turn the notebook off and on again.

Asus optimus notebook N750JVT-4069H (Intel® Core™ i7-4700HQ; RAM 16GB; Nvidia GeForce GT750M)
dmesg output:
http://paste.ubuntu.com/10658886
(Nothing has been logged yet.)

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-9-generic 3.19.0-9.9 [modified: boot/vmlinuz-3.19.0-9-generic]
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: aljosa 1824 F.... pulseaudio
 /dev/snd/controlC0: aljosa 1824 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Mar 23 09:46:58 2015
HibernationDevice: RESUME=UUID=df42f272-c519-4323-977d-bb1fe697e7f0
InstallationDate: Installed on 2015-03-19 (3 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150318)
MachineType: ASUSTeK COMPUTER INC. N750JV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic.efi.signed root=UUID=da571e57-f1af-49b1-95ba-206e95c86cec ro quiet splash ipv6.disable=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-9-generic N/A
 linux-backports-modules-3.19.0-9-generic N/A
 linux-firmware 1.143
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N750JV.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N750JV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN750JV.210:bd04/11/2014:svnASUSTeKCOMPUTERINC.:pnN750JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN750JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N750JV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc5-vivid/

[aljosa (aljosa-p)]

As suggested, I have just installed the latest 4.0-rc5 kernel. Unfortunately, the problem is still here :(