Bug 690248

Summary: InstallPackageNames uses default dbus 25s timeout, should be higher?
Product: Red Hat Enterprise Linux 6 Reporter: Cole Robinson <crobinso>
Component: gnome-packagekitAssignee: Richard Hughes <rhughes>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-15 14:02:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Cole Robinson 2011-03-23 17:30:54 UTC 
InstallPackageNames uses the default dbus timeout of 25s, which seems pretty low for depsolving, prompting user for dep install, auth, and actually installing the packages. For example, virt-manager offers to install 'libvirt' and 'qemu' which doesn't seem possible in less than 25 seconds (we now manually set the timeout higher).

I spoke to Richard on IRC, he indicated this is probably a bug:

Mar 23 11:45:40 <hughsie>>......crobinso, i've not looked at the python bindings in months, but the timeout should really be above 25 sconds

This can be easily triggered using the example python code in the PackageKit faq: http://www.packagekit.org/pk-faq.html#session-methods

Manually trying to set the timeout to -1 doesn't seem to work either and just uses the default 25 second timeout. Not sure if it has any relation
Comment 2 RHEL Program Management 2011-03-23 17:47:37 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3 RHEL Program Management 2011-07-06 01:33:37 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 4 Cole Robinson 2012-07-15 14:02:32 UTC 
Since this bug is just limping along and it's not that important, I'm closing.