| Summary: | Crash in gsm-modemmanager when entering pincode | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | Allan Sandfeld <kde> |
| Component: | networkmanagement-mobile | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | lamarque, marcus |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Allan Sandfeld
2012-01-16 17:41:47 UTC
I think you hit this bug https://bugs.kde.org/show_bug.cgi?id=279649 , read comment #9 I cannot reproduce this bug here. Acknowledged. I am using Debian packages on this machine Kde-workspace 4.7.4-1 and plasma-widget-networkmanagement 0.9~git20111126.1ef1677-1, but the plasma-widget-networkmanagement package only depend on kde 4.6 libraries. But where is the ABI change? If it is in the runtime API, should it really crash then? The changes are in Solid's ModemManager backend (kde-workspace package). It is a ABI *and* API change. The changes is source compatible but not binary compatible. The same Plasma NM binary cannot run on both kde-workspace 4.6.x and 4.7.x, you have to recompile Plasma NM against each kde-workspace version. Can you recompile Plasma NM against the kde-workspace you plan to run it with and test if that solves your problem? Even if it does work around the problem for me, it does not in any way solve the underlying problem, please see the corresponding bug for Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656197 The fact is that the change is there for almost a year and I am not going to revert it. The change was added to fix the PIN handling for 3G modems, without this change there is chance the user locks in the sim card. This bug is minor problem compared to that. Okay, that sounds good. Can I get you to explain that to the distro guys? Because it makes it their bug, and it is important they set the correct conflicts. Btw. Recompiling the debian package with a newer kdebase-dev packages solved the problem. Replying through mobile broadband ;) One other suggestion though: Maybe it should have been possible to hide the popup asking for pin on every reboot, and only show it next time the user tries to enable mobile broandband in the plasma widget? Open a bug report in your distro's bug tracking system and make it point to this bug entry. I do not have an account in every distro's bug tracking system, I cannot to that alone. I am starting to think it is a good idea to make CMakeLists.txt refuse to compile against KDE SC < 4.7.0 (including 4.7.0 release candidates). That would also solve the problem. It's not possible to enable a modem when it is locked by the PIN. The "Enable Mobile Broadband" would fail, that is why we ask for the PIN as soon as possible. I have already opened a bug and have provided links in both directions, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656197 My point was more something like the configure check or information with the source so the packagers find this important information. A cmake check is not possible since the problem happens in runtime, not in compilation time. I do not think a runtime check is also possible. I do can check the kdelibs version (I do not know if I can check the kde-workspace version), but after that the best I can do is disabling the modem to prevent the crash. I cannot make PIN unlock work with a non-suitable kde-workspace. *** Bug 293203 has been marked as a duplicate of this bug. *** |