This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1750232

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

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Linux Mint/Ubuntu is taking modem off-hook during logon

Status in linux package in Ubuntu:

Bug description:
  As of 15 February 2018 (and possibly earlier) the following bug has
  been reintroduced:

  When Linux Mint (Cinnamon OR Mate) OR UBUNTU starts up (_after_ the
  login screen), the Smartlink internal modem is taken off hook, and
  remains off hook (disabling the telephone line) until such time as the
  system is shut down or rebooted (in which case it goes off hook again
  after login).

  This annoying bug was introduced with Linux Mint 17.0 Trusty, and also
  occurs with Ubuntu 14.04. It disappeared with Linux Mint 18.0 Xenial
  (which is based on Ubuntu 16.04). Now it is back, possibly as a result
  of the latest updates, possibly earlier.

  Yes, since Linux no longer supports the Smartlink modem, even with the
  modifications to the kernel that previously worked, I could simply
  disconnect the internal modem. But I dual-boot to Windoze, and DO use
  it without problem in Windoze, so it is more than an annoyance.

  I can understand Linux not supporting hardware, but it is unacceptable
  that Linux is sending commands to unsupported hardware whihc cause it
  to malfunction.

  As a Linux USER, I have no way of isolating the component causing the
  bug. It will require a trace of what is written to the COM port(s)
  during login. But, since it was fixed before, there should be some
  record of the cause and solution.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to