Bug 3841 - Drakx-net can't find /dev/ttyACM, but /dev/ttyACM0 exists.
Summary: Drakx-net can't find /dev/ttyACM, but /dev/ttyACM0 exists.
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2011-12-21 16:22 CET by Ramon Dantas
Modified: 2012-12-02 14:36 CET (History)
2 users (show)

See Also:
Source RPM: drakx-net-0.97.1-2.mga1.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Ramon Dantas 2011-12-21 16:22:46 CET 
Description of problem:
First, sorry for my bad English. I can't use my cellphone like a modem, because DrakNetCenter can't find /dev/ttyACM, but /dev/ttyACM0 exists.
Tested cellphones:
- Samsung STAR II GT-S5260.
- Motorola V3.

Version-Release number of selected component (if applicable):
drakxnet-0.97.1-2mga1

How reproducible:
Every time I try to configure my cellphone like a modem.

Steps to Reproduce:
1. Connect your cellphone.
2. Open draknetcenter.
3. Try to configure your cellphone.

Workaround:
In a root terminal, run:
# ln -s /dev/ttyACM0 /dev/ttyACM
Comment 1 Manuel Hiebel 2011-12-21 19:00:25 CET 
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => mageia
Summary: DrakNetCenter can't find /dev/ttyACM, but /dev/ttyACM0 exists. => Drakx-net can't find /dev/ttyACM, but /dev/ttyACM0 exists.

Ramon Dantas 2011-12-23 18:02:26 CET

Status: NEW => ASSIGNED

Comment 2 Thierry Vignaud 2012-09-06 12:31:30 CEST 
I've fixed the device path in the code instead

Status: ASSIGNED => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => FIXED

Comment 3 Olivier Blin 2012-10-12 23:53:51 CEST 
The fix is incorrect, the extra "0" is supposed to come from the tty_interface variable, which already defaults to "0".
We should instead fix the code resetting this variable.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Olivier Blin 2012-10-12 23:54:00 CEST

CC: (none) => mageia

Comment 4 Manuel Hiebel 2012-11-05 16:54:12 CET 
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 5 Manuel Hiebel 2012-12-02 14:36:33 CET 
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: REOPENED => RESOLVED
Resolution: (none) => WONTFIX
Note You need to log in before you can comment on or make changes to this bug.