[Lenovo Thinkpad T440S] frequent nm crashes and problems

Bug #1319653 reported by WishMaster
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Hello there,

since I have freshly installed Ubuntu 14.04, Network Manager seems to have more problems handling 3G connections than under 13.10:

1) The PIN code is not remembered. Even when I tick the "Unlock automatically" option and also input the PIN in the connection settings, the system asks me for the PIN on every startup. It is especially annoying because the dialog for the PIN also appears on the login screen and takes the focus away from when you are typing the password.

2) Malfunctioning connection interface. After the PIN has been entered, "Enable Mobile Broadband" has to be ticked in the nm-Applet. However, I always have to do this twice before the check-icon actually appears and I can connect.
When connecting, there is no indicator that the connection is being set up, instead the applet's icon shows the "not connected" empty triangle.

3) Connecting after suspend/resume does not work reliably. However, as there are more problems with suspend/resume on the T440S with 14.04, this will probably have to be dealt with separately.

As mentioned above, I have installed Ubuntu 14.04. I am using Unity and network-manager-gnome in version 0.9.8.8-0ubuntu4.

I realize that you will need further information. Please let me know what you need to know in order to investigate the problems I have described.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: philipp 1957 F.... pulseaudio
 /dev/snd/controlC1: philipp 1957 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=9b549385-ebae-46ed-b802-68ea9dc55d81
InstallationDate: Installed on 2014-05-03 (12 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 20ARS0BH00
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=78a231e4-b323-481e-9a0f-36f4055c01e2 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET75WW (2.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ARS0BH00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGJET75WW(2.25):bd03/28/2014:svnLENOVO:pn20ARS0BH00:pvrThinkPadT440s:rvnLENOVO:rn20ARS0BH00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20ARS0BH00
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

Revision history for this message
WishMaster (jude1733) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1319653

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
WishMaster (jude1733) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
WishMaster (jude1733) wrote : BootDmesg.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : CRDA.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : CurrentDmesg.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : IwConfig.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : Lspci.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : Lsusb.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : ProcEnviron.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : ProcInterrupts.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : ProcModules.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : PulseList.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : RfKill.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : UdevDb.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : UdevLog.txt

apport information

Revision history for this message
WishMaster (jude1733) wrote : WifiSyslog.txt

apport information

WishMaster (jude1733)
tags: added: confirmed mobile
WishMaster (jude1733)
Changed in linux (Ubuntu):
status: Incomplete → Opinion
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 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/v3.15-rc5-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Opinion → Incomplete
Revision history for this message
WishMaster (jude1733) wrote :

I have testet it with the 3.14 mainstream kernel and there is no difference there. I also don't think remembering the PIN is a kernel issue.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Test with newer development kernel (3.13.0-24.46)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.13.0-24.46
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.