Bug 339045 - In gnome update applet have not funtion stop of checking for updates
Summary: In gnome update applet have not funtion stop of checking for updates
Status: RESOLVED NORESPONSE
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 10.3
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Christian Kornacker
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on: 340505
Blocks:
  Show dependency tree / graph
 
Reported: 2007-11-05 10:11 UTC by Andrey Gankov
Modified: 2011-04-04 02:02 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Gankov 2007-11-05 10:11:48 UTC 
When i load OpenSuse, gnome update applet run checking for updates. it's very long, and i can not stop it operation. For example, after entering in graphic session i run Yast software manager and i have error "access denied for packets manager". I happen to very long wait until update applet complete to checking for updates. I can not stop it operation. May be need make to item of "stop checking" in pop-up menu of update applet.
Comment 1 Jan Kupec 2007-11-09 12:36:26 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).
Comment 2 Thomas Göttlicher 2007-11-09 12:46:12 UTC 
Right, it would be great if zypper could be interrupted. We should design a zypper control protocol that includes stopping zypper.
Comment 3 Jan Kupec 2007-11-09 12:51:57 UTC 
(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.
Comment 4 Thomas Göttlicher 2007-11-09 13:02:31 UTC 
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.
Comment 6 Larry Finger 2011-04-04 02:02:34 UTC 
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!