Bug 24423 - rpmdrake: Cancel button does not react
Summary: rpmdrake: Cancel button does not react
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-25 09:31 CET by pavel heimlich
Modified: 2020-08-26 11:36 CEST (History)
4 users (show)

See Also:
Source RPM: rpmdrake-6.27-1.mga6
CVE:
Status comment:


Attachments

Description pavel heimlich 2019-02-25 09:31:19 CET
Theme name: Adwaita
Kernel version = 4.14.100-desktop-1.mga6
Distribution=Mageia release 6 (Official) for x86_64
CPU=Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz


When I turn vpn on, obviously rpmdrake isn't able to download packages as it doesn't know it has to use proxy.
However the 'Packages installation' window with 'Downloading package  ...' cannot be closed, the Cancel button does not react until curl times out. This is annoying.

To reproduce:
Connect to vpn that requires a proxy to access the web or otherwise restrict internet access.
Open rpmdrake and select a package to install
Click Apply
Click Yes, ot's ok to continue
Try to click the Cancel button  or the close (x) widget
Jani Välimaa 2019-02-25 12:27:59 CET

Summary: Cancel button does not react => rpmdrake: Cancel button does not react

Marja Van Waes 2019-02-26 13:38:20 CET

Assignee: bugsquad => mageiatools
CC: (none) => marja11, thierry.vignaud

Comment 1 Aurelien Oudelet 2020-08-16 22:42:35 CEST
Is this still valid in Mageia 7 or Cauldron ?

CC: (none) => ouaurelien

Comment 2 Morgan Leijström 2020-08-17 08:27:51 CEST
I seem to remember the timeout have been lowered some months ago, to ease problems like this.  Think read that on Mageia dev or qa mailing list.

CC: (none) => fri

Comment 3 Aurelien Oudelet 2020-08-23 14:41:52 CEST Comment hidden (obsolete)

Resolution: (none) => OLD
Status: NEW => RESOLVED

Comment 4 Aurelien Oudelet 2020-08-26 11:36:34 CEST
We will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Note You need to log in before you can comment on or make changes to this bug.