Ticket #279 (closed defect: fixed)
Appmanager crush when install packages
| Reported by: | songcw@… | Owned by: | buglog@… |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | openmoko-applicationmanager | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: | buglog@… | Blocked By: | |
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | PatchReviewResult: | ||
| Reproducible: |
Description
Launch the openmoko-appmanager by the matchbox-desktop, it crushed when install
package from single ".ipk" file.
If run the openmoko-appmanager from the console, it can install package
successfully.
Attachments
Change History
Changed 6 years ago by songcw@…
- Attachment is-processing.patch added
The new is-processing.patch, it resolve the bug 279.
comment:2 Changed 6 years ago by songcw@…
- Status changed from new to closed
- Resolution set to fixed
Ken_Zhao has updated the is-processing.patch file to resolve it.
It will check whether the process is available before sending "SIGTERM" signal
to a process. Because we can't update this file by our accounts. So he email the
patch file to the devel list. The attachment file is the new is-processing.patch.
Note: See
TracTickets for help on using
tickets.
After more test with Ken_Zhao, we found that the libipkg will fork some new
processes to complete the installing. And the libipkg will send them a "SIGTERM"
signal to terminal them.
If run the openmoko-appmanager from the console, the processes that libipkg
forked remain at memory after they complete their jobs, and the status of them
is "Z"(use the ps).
If launch the openmoko-appmanager from the matchbox-desktop, the processes that
libipkg forked will automatically terminate after they complete their jobs. So
the process id of them will be invailid. Send a "SIGTERM" signal to an invailid
process cause the openmoko-appmanager crush.