|
Bugzilla – Full Text Bug Listing |
| Summary: | In gnome update applet have not funtion stop of checking for updates | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Andrey Gankov <gankov> |
| Component: | Update Problems | Assignee: | Christian Kornacker <ckornacker> |
| Status: | RESOLVED NORESPONSE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | tgoettlicher |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 340505 | ||
| Bug Blocks: | |||
|
Description
Andrey Gankov
2007-11-05 10:11:48 UTC
That would be really useful. Josh, Thomas i guess i have to provide a means for this in zypper first (similarly also for bug 227086 and bug 334268). Right, it would be great if zypper could be interrupted. We should design a zypper control protocol that includes stopping zypper. (In reply to comment #2 from Thomas Göttlicher) > Right, it would be great if zypper could be interrupted. We should design a > zypper control protocol that includes stopping zypper. Designing such a protocol is not a problem, of course. But we must decide how to do the communication itself. Should zypper use dbus, or something else? First thing that came to my mind is to properly handle SIGINT in zypper. That needs to be done anyway. So as a first approach, we can achieve the stopping by sending SIGINT to zypper from the applets. In the meantime we can think about other means and eventually discuss them on mailing lists or irc. I filed a new request for SIGINT handling (bug 340505) which blocks this bug. Sending signals isn't that easy. Zypper has to run with root privileges, therefore it is stared via a suid-wrapper. I don't know any (secure) solution to send signals to a application owned by another user. The version with which you had the bug is now obsolete. I'll close this as NORESPONSE. If you can still reproduce it in current 11.4, please reopen the bug and move it to the appropriate version. Thanks! |