On 28.08.2012 14:07, Reinhard Tartler wrote: > On Tue, Aug 28, 2012 at 1:16 PM, Didier 'OdyX' Raboud <firstname.lastname@example.org> wrote: >> (Dropping -devel) >> >> Hi Reinhard, >> >> Le mardi, 28 août 2012 12.18:31, Reinhard Tartler a écrit : >>> Package: modemmanager >>> Version: 0.5.2.0-1 >>> >>> On Tue, Oct 18, 2011 at 10:58 PM, Michael Biebl <email@example.com> wrote: >>>> Am 18.10.2011 21:16, schrieb Tollef Fog Heen: >>>>> >>>>> modemmanager shouldn't recommend usb-modeswitch, but suggest it. >>>> >>>> The problem then is, that users get failures which are extremely hard to >>>> debug. The hardware simply won't work for them and we don't have a good >>>> way to detect such cases and forward a error message to the user session >>>> asking them to install usb-modeswitch. >>> >>> If that is the problem, then the current implementation seems more >>> like a workaround than a fix for this. >> >> In that case, what would be the fix? > > I'd suggest to signal the situation properly to the user. This would > make the situation less hard to identify. > > Ideally, the user is presented some dialog box that instructs him to > install the missing usb-modeswitch pacakge if necessary when he plugs > in his 3g dongle. > We don't have the infrastructure though, to do such hardware based installation requests, i.e. a system service which constantly monitors newly plugged in devices, has a database of devices mapping to packages, and a service running in the user session which can be signaled via the system service (e.g. via D-Bus) when such a hardware has been plugged in, and presents that to the user. This would certainly be a neat idea and once we have that and is widely used, we can adjust the package relation ship between modemmanager and usb-modeswitch. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Description: OpenPGP digital signature