After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 332981 - Use udev for auto detection and setup of device
Use udev for auto detection and setup of device
Status: RESOLVED WONTFIX
Product: gnome-phone-manager
Classification: Other
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: none
none
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2006-03-01 11:17 UTC by Per Thomas Jahr
Modified: 2018-08-17 18:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Output from lshal with phone connected (145.57 KB, text/plain)
2006-03-29 18:52 UTC, Per Thomas Jahr
Details
gpm log when sending a long message. (31.25 KB, text/plain)
2008-11-16 12:08 UTC, Stéphane Maniaci
Details

Description Per Thomas Jahr 2006-03-01 11:17:04 UTC
Would it be possible for the gnome-phone-manager to automatically find the 
correct device to use (/dev/ttyUSB...)? This will greatly improve the setup 
part of using the program.

I guess one could use HAL for this.
Comment 1 Bastien Nocera 2006-03-27 22:34:17 UTC
It would be possible indeed. We would need to add a "phone" style property. Could you attach the output of lshal with the phone plugged in, and let me know how you usually access the device?
Comment 2 Per Thomas Jahr 2006-03-29 18:52:55 UTC
Created attachment 62319 [details]
Output from lshal with phone connected
Comment 3 Per Thomas Jahr 2006-03-29 18:53:35 UTC
Sure, my Sony Ericsson T300 is connected via a usb cable. It uses the driver
pl2303. I usally look in dmesg to see what device to use (this time it was
/dev/ttyUSB0). See the attachment for lshal output (and grep for pl2303)
Comment 4 Pawel Kot 2007-11-08 12:26:58 UTC
There's a problem with that. For DKU-2 and family cables you can recognize if it is feasible byt checking device class and subclass. For the serial port converters (all pl2303 family and similiar) it seems to be not possible. I am afraid the only way is to use (vendorid, productsid) list like it is done in the kernel drivers. 

It would be good not to duplicate this configuration all over the place and for example extend HAL configuration with the information that such device offers serial port access.

Remember also, that for usb2serial cables you will just detect the cable presence, not the phone presence. But that's acceptable I think.
Comment 5 Bastien Nocera 2007-11-14 18:51:04 UTC
Using HAL, we could detect:
- IrDA ports
- Serial ports
- USB devices such as the DKU2 cables.

Most of the changes would be in gnome-phone-manager's prefs, in ui.c
Comment 6 Stéphane Maniaci 2008-11-16 12:08:35 UTC
Created attachment 122785 [details]
gpm log when sending a long message.
Comment 7 Bastien Nocera 2009-09-01 16:52:21 UTC
Comment on attachment 122785 [details]
gpm log when sending a long message.

Not related to the bug in any way...
Comment 8 Bastien Nocera 2009-09-01 16:55:03 UTC
Updating summary for latest platform changes.
Comment 9 André Klapper 2018-08-17 18:47:56 UTC
gnome-phone-manager is not under active development anymore since 2013.
Its codebase has been archived:
https://gitlab.gnome.org/Archive/phonemgr/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.