[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
Hi, just want to update that the problem still exists under 19.10 live system. I couldn't test whether the 77-mm-huawei-net-port-types.rules fix works, since I only have a live-USB system where I can't add the file early enough. How do we get the Modem Manager people to decide whether the above described workaround is a proper fix that should be upstreamed ? Anything how we can help ? Yours, Steffen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735981 Title: Huawei ME936 mobile broadband can't connect Status in modemmanager package in Ubuntu: Confirmed Bug description: Hi, I have an Acer Travelmate P648 with a Huawei ME936 internal USB mobile broadband card, and can't connect. This didn't work in 17.04, and still does not work in 17.10. The USB device is successfully connected, ModemManager gets as far as "Simple connect state (8/8): All done" During the setup ModemManager complains with "Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2'" DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed out". IP6 is set to "automatically" in the network settings for this configuration. and finally connection fails with "device (ttyUSB0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')" I checked that there are enough credits left in my account with the provider. Any ideas what else to check ? Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 11:27:49 2017 InstallationDate: Installed on 2017-04-24 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: modemmanager UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
And then I changed the file below and now have a working connection:
sneumann@msbi-corei:/lib/udev/rules.d$ rcsdiff -u
./77-mm-huawei-net-port-types.rules
===
RCS file: ./77-mm-huawei-net-port-types.rules,v
retrieving revision 1.1
diff -u -r1.1 ./77-mm-huawei-net-port-types.rules
--- ./77-mm-huawei-net-port-types.rules 2018/09/06 05:09:56 1.1
+++ ./77-mm-huawei-net-port-types.rules 2018/09/06 05:37:49
@@ -24,4 +24,7 @@
# Airtel branded E3372h-607, using huawei-cdc-ncm driver but with unresponsive
cdc-wdm port
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1506",
ENV{ID_MM_HUAWEI_NDISDUP_SUPPORTED}="1"
+# https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981
+ACTION=="add|change", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTR{idVendor}=="12d1", ATTR{idProduct}=="15bb", ATTR{bNumConfigurations}=="3",
ATTR{bConfigurationValue}!="3" ATTR{bConfigurationValue}="3"
+
LABEL="mm_huawei_port_types_end"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1735981
Title:
Huawei ME936 mobile broadband can't connect
Status in modemmanager package in Ubuntu:
Confirmed
Bug description:
Hi, I have an Acer Travelmate P648 with a Huawei ME936
internal USB mobile broadband card, and can't connect.
This didn't work in 17.04, and still does not work in 17.10.
The USB device is successfully connected,
ModemManager gets as far as "Simple connect state (8/8): All done"
During the setup ModemManager complains with "Couldn't find associated
cdc-wdm port for 'net/wwp0s20f0u9c2'"
DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed
out".
IP6 is set to "automatically" in the network settings for this configuration.
and finally connection fails with
"device (ttyUSB0): state change: ip-config -> failed (reason
'ip-config-unavailable', internal state 'managed')"
I checked that there are enough credits left in my account with the
provider.
Any ideas what else to check ?
Yours,
Steffen
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: modemmanager 1.6.8-1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 3 11:27:49 2017
InstallationDate: Installed on 2017-04-24 (222 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: modemmanager
UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
And then I changed the file below and now have a working connection:
sneumann@msbi-corei:/lib/udev/rules.d$ rcsdiff -u
./77-mm-huawei-net-port-types.rules
===
RCS file: ./77-mm-huawei-net-port-types.rules,v
retrieving revision 1.1
diff -u -r1.1 ./77-mm-huawei-net-port-types.rules
--- ./77-mm-huawei-net-port-types.rules 2018/09/06 05:09:56 1.1
+++ ./77-mm-huawei-net-port-types.rules 2018/09/06 05:37:49
@@ -24,4 +24,7 @@
# Airtel branded E3372h-607, using huawei-cdc-ncm driver but with unresponsive
cdc-wdm port
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1506",
ENV{ID_MM_HUAWEI_NDISDUP_SUPPORTED}="1"
+# https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981
+ACTION=="add|change", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTR{idVendor}=="12d1", ATTR{idProduct}=="15bb", ATTR{bNumConfigurations}=="3",
ATTR{bConfigurationValue}!="3" ATTR{bConfigurationValue}="3"
+
LABEL="mm_huawei_port_types_end"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1735981
Title:
Huawei ME936 mobile broadband can't connect
Status in modemmanager package in Ubuntu:
Confirmed
Bug description:
Hi, I have an Acer Travelmate P648 with a Huawei ME936
internal USB mobile broadband card, and can't connect.
This didn't work in 17.04, and still does not work in 17.10.
The USB device is successfully connected,
ModemManager gets as far as "Simple connect state (8/8): All done"
During the setup ModemManager complains with "Couldn't find associated
cdc-wdm port for 'net/wwp0s20f0u9c2'"
DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed
out".
IP6 is set to "automatically" in the network settings for this configuration.
and finally connection fails with
"device (ttyUSB0): state change: ip-config -> failed (reason
'ip-config-unavailable', internal state 'managed')"
I checked that there are enough credits left in my account with the
provider.
Any ideas what else to check ?
Yours,
Steffen
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: modemmanager 1.6.8-1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 3 11:27:49 2017
InstallationDate: Installed on 2017-04-24 (222 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: modemmanager
UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
Hi, just an update, no connectivity out-of-the-box with 18.04: Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6615] device (ttyUSB0): Activation: starting connection 'E-Plus connection' (bfe0f53f--cafebf693838) Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6624] audit: op="connection-activate" uuid="bfe0f53f-ccd2-45b6-b35b-cafebf693838" name="E-Plus connection" pid=17739 uid=1000 result="success" Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6637] device (ttyUSB0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6673] device (ttyUSB0): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6774] device (ttyUSB0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:09 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:09 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (locked -> initializing) Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: couldn't load Operator name: 'Operation not supported' Sep 06 07:02:13 msbi-corei ModemManager[1205]: couldn't load current Bands: 'Unknown error' Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (initializing -> disabled) Sep 06 07:02:13 msbi-corei NetworkManager[1299]: [1536210133.8852] modem["ttyUSB0"]: modem state changed, 'locked' --> 'disabled' (reason: unknown) Sep 06 07:02:13 msbi-corei NetworkManager[1299]: [1536210133.8856] modem["ttyUSB0"]: modem state changed, 'disabled' --> 'enabling' (reason: user preference) Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (disabled -> enabling) Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB2): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: Simple connect started... Sep 06 07:02:13 msbi-corei ModemManager[1205]: Simple connect state (4/8): Wait to get fully enabled Sep 06 07:02:14 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (unknown -> idle) Sep 06 07:02:14 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (enabling -> enabled) Sep 06 07:02:14 msbi-corei ModemManager[1205]: Simple connect state (5/8): Register Sep 06 07:02:14 msbi-corei NetworkManager[1299]: [1536210134.5790] modem["ttyUSB0"]: modem state changed, 'enabling' --> 'enabled' (reason: user-requested) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (idle -> registering) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (registering -> home) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (enabled -> registered) Sep 06 07:02:15 msbi-corei NetworkManager[1299]: [1536210135.7173] modem["ttyUSB0"]: modem state changed, 'enabled' --> 'registered' (reason: unknown) Sep 06 07:02:18 msbi-corei ModemManager[1205]: Simple connect state (6/8): Bearer Sep 06 07:02:18 msbi-corei ModemManager[1205]: Simple connect state (7/8): Connect Sep 06 07:02:18 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (registered -> connecting) Sep 06 07:02:18 msbi-corei ModemManager[1205]: Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2' Sep 06 07:02:18 msbi-corei NetworkManager[1299]: [1536210138.1869] modem["ttyUSB0"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested) Sep 06 07:03:19 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (connecting -> registered) Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1425] modem["ttyUSB0"]: modem state changed, 'connecting' --> 'registered' (reason: user-requested) Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1428] modem-broadband[ttyUSB0]: failed to connect modem: Connection attempt timed out Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1430] device (ttyUSB0): state change: prepare -> failed (reason 'gsm-registration-timeout', sys-iface-state: 'managed') Sep 06 07:03:19 msbi-corei NetworkManager[1299]:
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
Hi, just an update, no connectivity out-of-the-box with 18.04: Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6615] device (ttyUSB0): Activation: starting connection 'E-Plus connection' (bfe0f53f--cafebf693838) Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6624] audit: op="connection-activate" uuid="bfe0f53f-ccd2-45b6-b35b-cafebf693838" name="E-Plus connection" pid=17739 uid=1000 result="success" Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6637] device (ttyUSB0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6673] device (ttyUSB0): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6774] device (ttyUSB0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:09 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:09 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (locked -> initializing) Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: couldn't load Operator name: 'Operation not supported' Sep 06 07:02:13 msbi-corei ModemManager[1205]: couldn't load current Bands: 'Unknown error' Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (initializing -> disabled) Sep 06 07:02:13 msbi-corei NetworkManager[1299]: [1536210133.8852] modem["ttyUSB0"]: modem state changed, 'locked' --> 'disabled' (reason: unknown) Sep 06 07:02:13 msbi-corei NetworkManager[1299]: [1536210133.8856] modem["ttyUSB0"]: modem state changed, 'disabled' --> 'enabling' (reason: user preference) Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (disabled -> enabling) Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB2): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: Simple connect started... Sep 06 07:02:13 msbi-corei ModemManager[1205]: Simple connect state (4/8): Wait to get fully enabled Sep 06 07:02:14 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (unknown -> idle) Sep 06 07:02:14 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (enabling -> enabled) Sep 06 07:02:14 msbi-corei ModemManager[1205]: Simple connect state (5/8): Register Sep 06 07:02:14 msbi-corei NetworkManager[1299]: [1536210134.5790] modem["ttyUSB0"]: modem state changed, 'enabling' --> 'enabled' (reason: user-requested) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (idle -> registering) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (registering -> home) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (enabled -> registered) Sep 06 07:02:15 msbi-corei NetworkManager[1299]: [1536210135.7173] modem["ttyUSB0"]: modem state changed, 'enabled' --> 'registered' (reason: unknown) Sep 06 07:02:18 msbi-corei ModemManager[1205]: Simple connect state (6/8): Bearer Sep 06 07:02:18 msbi-corei ModemManager[1205]: Simple connect state (7/8): Connect Sep 06 07:02:18 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (registered -> connecting) Sep 06 07:02:18 msbi-corei ModemManager[1205]: Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2' Sep 06 07:02:18 msbi-corei NetworkManager[1299]: [1536210138.1869] modem["ttyUSB0"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested) Sep 06 07:03:19 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (connecting -> registered) Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1425] modem["ttyUSB0"]: modem state changed, 'connecting' --> 'registered' (reason: user-requested) Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1428] modem-broadband[ttyUSB0]: failed to connect modem: Connection attempt timed out Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1430] device (ttyUSB0): state change: prepare -> failed (reason 'gsm-registration-timeout', sys-iface-state: 'managed') Sep 06 07:03:19 msbi-corei NetworkManager[1299]:
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
I can confirm that the workaround above by Philipp Hufnagl indeed does the job. I am writing this comment from aboard a train ;-) The connction setup is not very robust, and sometimes fails at Simple connect state (4/8): Wait to get fully enabled How to get a proper fix upstream now ? Yours, Steffen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735981 Title: Huawei ME936 mobile broadband can't connect Status in modemmanager package in Ubuntu: Confirmed Bug description: Hi, I have an Acer Travelmate P648 with a Huawei ME936 internal USB mobile broadband card, and can't connect. This didn't work in 17.04, and still does not work in 17.10. The USB device is successfully connected, ModemManager gets as far as "Simple connect state (8/8): All done" During the setup ModemManager complains with "Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2'" DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed out". IP6 is set to "automatically" in the network settings for this configuration. and finally connection fails with "device (ttyUSB0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')" I checked that there are enough credits left in my account with the provider. Any ideas what else to check ? Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 11:27:49 2017 InstallationDate: Installed on 2017-04-24 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: modemmanager UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
Even after a few apt dist-upgrades over time, no change. dmesg has as last two lines [ 3427.065250] cdc_ncm 1-9:2.0 wwp0s20f0u9c2: 5 mbit/s downlink 43 mbit/s uplink [ 3443.039348] cdc_ncm 1-9:2.0 wwp0s20f0u9c2: network connection: disconnected and journalctl has Jan 17 07:12:03 msbi-corei NetworkManager[1294]: [1516169523.3293] (ttyUSB0): modem state changed, 'registered' --> 'connecting' (reason: user-requested) Jan 17 07:12:03 msbi-corei NetworkManager[1294]: [1516169523.3306] (ttyUSB0): modem state changed, 'connecting' --> 'registered' (reason: user-requested) Jan 17 07:12:03 msbi-corei NetworkManager[1294]: [1516169523.3310] modem-broadband[ttyUSB0]: failed to connect modem: Only IPv4 is supported by this modem Jan 17 07:12:03 msbi-corei NetworkManager[1294]: [1516169523.3310] device (ttyUSB0): state change: prepare -> failed (reason 'unknown', internal state 'mana Jan 17 07:12:03 msbi-corei NetworkManager[1294]: [1516169523.3318] device (ttyUSB0): Activation: failed for connection 'FONIC Default' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735981 Title: Huawei ME936 mobile broadband can't connect Status in modemmanager package in Ubuntu: New Bug description: Hi, I have an Acer Travelmate P648 with a Huawei ME936 internal USB mobile broadband card, and can't connect. This didn't work in 17.04, and still does not work in 17.10. The USB device is successfully connected, ModemManager gets as far as "Simple connect state (8/8): All done" During the setup ModemManager complains with "Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2'" DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed out". IP6 is set to "automatically" in the network settings for this configuration. and finally connection fails with "device (ttyUSB0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')" I checked that there are enough credits left in my account with the provider. Any ideas what else to check ? Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 11:27:49 2017 InstallationDate: Installed on 2017-04-24 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: modemmanager UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
I also have no success with nmcli con up id "FONIC Default" Error: Connection activation failed: Unknown error -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735981 Title: Huawei ME936 mobile broadband can't connect Status in modemmanager package in Ubuntu: New Bug description: Hi, I have an Acer Travelmate P648 with a Huawei ME936 internal USB mobile broadband card, and can't connect. This didn't work in 17.04, and still does not work in 17.10. The USB device is successfully connected, ModemManager gets as far as "Simple connect state (8/8): All done" During the setup ModemManager complains with "Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2'" DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed out". IP6 is set to "automatically" in the network settings for this configuration. and finally connection fails with "device (ttyUSB0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')" I checked that there are enough credits left in my account with the provider. Any ideas what else to check ? Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 11:27:49 2017 InstallationDate: Installed on 2017-04-24 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: modemmanager UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
So mmcli will show me that the modem is alive, but still the issue that I don't get an IP. Thoughts ? mmcli -m 0 /org/freedesktop/ModemManager1/Modem/0 (device id '0ea...129') - Hardware | manufacturer: 'Huawei Technologies Co., Ltd.' | model: 'ME936' | revision: '11.350.24.00.00' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '86...88' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-9' |drivers: 'option1, cdc_ncm' | plugin: 'Huawei' | primary port: 'ttyUSB0' | ports: 'ttyUSB0 (at), wwp0s20f0u9c2 (net), ttyUSB2 (at)' - Numbers | own : '+49176...7' - Status | lock: 'none' | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)' | state: 'registered' |power state: 'on' |access tech: 'umts' | signal quality: '25' (recent) - Modes| supported: 'allowed: 2g; preferred: none | allowed: 3g; preferred: none | allowed: 4g; preferred: none | allowed: 2g, 3g, 4g; preferred: none' |current: 'allowed: 2g, 3g, 4g; preferred: none' - Bands| supported: 'unknown' |current: 'unknown' - IP | supported: 'ipv4, ipv6, ipv4v6' - 3GPP | imei: '86...88' | enabled locks: 'sim' |operator id: '26203' | operator name: 'FONIC+' | subscription: 'unknown' | registration: 'home' - SIM | path: '/org/freedesktop/ModemManager1/SIM/0' - Bearers | paths: '/org/freedesktop/ModemManager1/Bearer/3' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735981 Title: Huawei ME936 mobile broadband can't connect Status in modemmanager package in Ubuntu: New Bug description: Hi, I have an Acer Travelmate P648 with a Huawei ME936 internal USB mobile broadband card, and can't connect. This didn't work in 17.04, and still does not work in 17.10. The USB device is successfully connected, ModemManager gets as far as "Simple connect state (8/8): All done" During the setup ModemManager complains with "Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2'" DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed out". IP6 is set to "automatically" in the network settings for this configuration. and finally connection fails with "device (ttyUSB0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')" I checked that there are enough credits left in my account with the provider. Any ideas what else to check ? Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 11:27:49 2017 InstallationDate: Installed on 2017-04-24 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: modemmanager UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
And just double-checked, works under Windows. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735981 Title: Huawei ME936 mobile broadband can't connect Status in modemmanager package in Ubuntu: New Bug description: Hi, I have an Acer Travelmate P648 with a Huawei ME936 internal USB mobile broadband card, and can't connect. This didn't work in 17.04, and still does not work in 17.10. The USB device is successfully connected, ModemManager gets as far as "Simple connect state (8/8): All done" During the setup ModemManager complains with "Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2'" DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed out". IP6 is set to "automatically" in the network settings for this configuration. and finally connection fails with "device (ttyUSB0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')" I checked that there are enough credits left in my account with the provider. Any ideas what else to check ? Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 11:27:49 2017 InstallationDate: Installed on 2017-04-24 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: modemmanager UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
Hi, this is the excerpt from the journal from ModemManager and NetworkManager ** Attachment added: "Output of journalctl -u system.slice" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+attachment/5017697/+files/network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735981 Title: Huawei ME936 mobile broadband can't connect Status in modemmanager package in Ubuntu: New Bug description: Hi, I have an Acer Travelmate P648 with a Huawei ME936 internal USB mobile broadband card, and can't connect. This didn't work in 17.04, and still does not work in 17.10. The USB device is successfully connected, ModemManager gets as far as "Simple connect state (8/8): All done" During the setup ModemManager complains with "Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2'" DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed out". IP6 is set to "automatically" in the network settings for this configuration. and finally connection fails with "device (ttyUSB0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')" I checked that there are enough credits left in my account with the provider. Any ideas what else to check ? Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 11:27:49 2017 InstallationDate: Installed on 2017-04-24 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: modemmanager UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] [NEW] Huawei ME936 mobile broadband can't connect
Public bug reported: Hi, I have an Acer Travelmate P648 with a Huawei ME936 internal USB mobile broadband card, and can't connect. This didn't work in 17.04, and still does not work in 17.10. The USB device is successfully connected, ModemManager gets as far as "Simple connect state (8/8): All done" During the setup ModemManager complains with "Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2'" DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed out". IP6 is set to "automatically" in the network settings for this configuration. and finally connection fails with "device (ttyUSB0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')" I checked that there are enough credits left in my account with the provider. Any ideas what else to check ? Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 11:27:49 2017 InstallationDate: Installed on 2017-04-24 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: modemmanager UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735981 Title: Huawei ME936 mobile broadband can't connect Status in modemmanager package in Ubuntu: New Bug description: Hi, I have an Acer Travelmate P648 with a Huawei ME936 internal USB mobile broadband card, and can't connect. This didn't work in 17.04, and still does not work in 17.10. The USB device is successfully connected, ModemManager gets as far as "Simple connect state (8/8): All done" During the setup ModemManager complains with "Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2'" DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed out". IP6 is set to "automatically" in the network settings for this configuration. and finally connection fails with "device (ttyUSB0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')" I checked that there are enough credits left in my account with the provider. Any ideas what else to check ? Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 11:27:49 2017 InstallationDate: Installed on 2017-04-24 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: modemmanager UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565420] Re: [TMP645-M, Realtek ALC282, Pink Mic, Left] No sound at all
Hi Raymond, thanks for that blazingly fast answer. I created a file /etc/asound.conf with the content for contro.l23/25/26/14 you posted above, was that the right thing to do ? This solved my other problem with automagically switching to headphones when they are inserted, that's great! I can now also use alsamixer to get good quality from the headset microphone! Will every user have to do this, or can these Acer P645-M specific settings in asound.conf go into the appropriate ubuntu package ? Yours, Steffen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1565420 Title: [TMP645-M, Realtek ALC282, Pink Mic, Left] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hi, I have an issue using the headset microphone. hdajacksensetest will happily report the insertion and presence of the headset (with two separate 3.5mm for input and output): Pin 0x18 (Pink Mic, Left side): present = Yes If I use alsamixer to increase the levels, and enable the "loopback", I can hear the input in the headphones, but no levels are visible running "SoundRecorder". Happy to test whatever can help here. System is an Acer TravelMate P645-M V4DA2 running 16.04 current as of 2nd of April. Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sneumann 2087 F pulseaudio /dev/snd/controlC1: sneumann 2087 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 3 10:48:58 2016 InstallationDate: Installed on 2016-03-20 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sneumann 2087 F pulseaudio /dev/snd/controlC1: sneumann 2087 F pulseaudio Symptom_Jack: Pink Mic, Left Symptom_Type: No sound at all Title: [TMP645-M, Realtek ALC282, Pink Mic, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BAD40_HW dmi.board.vendor: Acer dmi.board.version: V2.07 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.07:bd01/14/2014:svnAcer:pnTMP645-M:pvrV2.07:rvnAcer:rnBAD40_HW:rvrV2.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: TMP645-M dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1565420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565420] [NEW] [TMP645-M, Realtek ALC282, Pink Mic, Left] No sound at all
Public bug reported: Hi, I have an issue using the headset microphone. hdajacksensetest will happily report the insertion and presence of the headset (with two separate 3.5mm for input and output): Pin 0x18 (Pink Mic, Left side): present = Yes If I use alsamixer to increase the levels, and enable the "loopback", I can hear the input in the headphones, but no levels are visible running "SoundRecorder". Happy to test whatever can help here. System is an Acer TravelMate P645-M V4DA2 running 16.04 current as of 2nd of April. Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sneumann 2087 F pulseaudio /dev/snd/controlC1: sneumann 2087 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 3 10:48:58 2016 InstallationDate: Installed on 2016-03-20 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sneumann 2087 F pulseaudio /dev/snd/controlC1: sneumann 2087 F pulseaudio Symptom_Jack: Pink Mic, Left Symptom_Type: No sound at all Title: [TMP645-M, Realtek ALC282, Pink Mic, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BAD40_HW dmi.board.vendor: Acer dmi.board.version: V2.07 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.07:bd01/14/2014:svnAcer:pnTMP645-M:pvrV2.07:rvnAcer:rnBAD40_HW:rvrV2.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: TMP645-M dmi.product.version: V2.07 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1565420 Title: [TMP645-M, Realtek ALC282, Pink Mic, Left] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi, I have an issue using the headset microphone. hdajacksensetest will happily report the insertion and presence of the headset (with two separate 3.5mm for input and output): Pin 0x18 (Pink Mic, Left side): present = Yes If I use alsamixer to increase the levels, and enable the "loopback", I can hear the input in the headphones, but no levels are visible running "SoundRecorder". Happy to test whatever can help here. System is an Acer TravelMate P645-M V4DA2 running 16.04 current as of 2nd of April. Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sneumann 2087 F pulseaudio /dev/snd/controlC1: sneumann 2087 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 3 10:48:58 2016 InstallationDate: Installed on 2016-03-20 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sneumann 2087 F pulseaudio /dev/snd/controlC1: sneumann 2087 F pulseaudio Symptom_Jack: Pink Mic, Left Symptom_Type: No sound at all Title: [TMP645-M, Realtek ALC282, Pink Mic, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BAD40_HW dmi.board.vendor: Acer dmi.board.version: V2.07 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.07:bd01/14/2014:svnAcer:pnTMP645-M:pvrV2.07:rvnAcer:rnBAD40_HW:rvrV2.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: TMP645-M dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to:
[Touch-packages] [Bug 1050422] Re: CUPS hangs when remote CUPS server defined in client.conf is inaccessible
Hi, I can confirm the hanging on both a laptop running 14.04 and a freshly installed 14.04, the cups client is on a Ubuntu 10.04.4 LTS running cups 1.4.3-1ubuntu1.13 But in our case the cups server IS perfectly accessible with ping, and nmap shows an open port 631/tcp open ipp Removing ServerName fixes the hanging. Can I do other checks to see where e.g. lpq hang ? Yours, Steffen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1050422 Title: CUPS hangs when remote CUPS server defined in client.conf is inaccessible Status in cups package in Ubuntu: Confirmed Bug description: When a remote CUPS server is defined in /etc/cups/client.conf like this: ServerName print.mpia-hd.mpg.de and the server is not accessible (e.g., it is on a company's internal net and you take your laptop home), then CUPS applications hang for up to several minutes, and then timeout. The gnome printing dialog, for example, hangs Firefox and Chromium, and the lpr, lpq, lpoptions, lpstat, etc. programs also hang and then error out. The localhost:631 interface does NOT hang, and in fact can print test pages on locally accessible printers. Note that this problem only affects remote SERVERS, not individual remote printers that are inaccessible. Those do not cause a problem. Expected behavior: missing printers of any sort should not hang programs for any reason. A short delay of a few seconds is ok. Description: Ubuntu 11.10 Release: 11.10 cups: Installed: 1.5.0-8ubuntu6 Candidate: 1.5.0-8ubuntu6 Version table: *** 1.5.0-8ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.5.0-8 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages The server cited above serves 72 printers, and timeouts ranged from 3 minutes, 9 seconds, to 6 minutes, 19 seconds (I believe but I am not certain that in the longer case, the default printer was on the missing server). It does not matter whether the default printer is one of the missing ones or not, you get a long timeout either way (the duration may matter, as noted above). If you want to change the default printer with lpoptions, you can't, because it hangs, times out, and quits. If you know the printer you want to print to and say lpr -P foo bar.pdf, it still hangs. Removing the client.conf file and restarting CUPS fixes the problem immediately. So, a workaround is to manually create and remove that file every time you enter/leave the network with the print server. This is not a viable workaround for most normal users. SPECULATION: The timeout may depend on how many printers were served on the missing server, and most servers don't have that many. I very much hope this will be fixed! There do appear to be others experiencing this, but there is little clarity on the web about it (some scattered complaints but few solutions that are practical). Possibly related: Note that there is a related bug #264333. It is old and didn't get much response. It may or may not be the same problem. Some there reported it fixed long ago, but others said they still had a problem. http://askubuntu.com/questions/16726/cant-print-cups-package-corrupted-and-hangs-on-re-install http://forums.gentoo.org/viewtopic-t-878487-start-0.html Thanks, --jh-- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1050422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
Affected here too after creating a new key in ~/.ssh, this is 14.04 with all updates as of today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 Status in openssh package in Ubuntu: Confirmed Bug description: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
