Bug 1188490

Summary: gtk+ theme menu problem
Product: [Fedora] Fedora Reporter: Sergio Basto <sergio>
Component: oxygen-gtk3Assignee: Rex Dieter <rdieter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: alekcejk, rdieter
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-15 12:04:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sergio Basto 2015-02-03 03:14:20 UTC
Description of problem:
on menu of nm-connection-editor when click add , appears one menu if you expand that menu drop box , kde complete freeze . 
with other gtk+ theme that see this problem. 


Version-Release number of selected component (if applicable):
oxygen-gtk3-1.4.1-3.fc21.x86_64

How reproducible:
run nm-connection-editor 

Steps to Reproduce:
1.run nm-connection-editor  
2. click add 
3. expand menu 

Actual results:
freeze kde 

Expected results:
not freeze kde


Additional info:

Comment 1 Sergio Basto 2015-02-09 19:13:36 UTC
Somehow this is now fixed,  with kde-4.14.4  (update-testing) or kde-4.14.3 in stable.

Comment 2 Sergio Basto 2015-02-09 19:55:44 UTC
Sorry I test it with  Adwaita gtk+ appearance  with oxygen the issue still there. 
Reopen it .

Comment 3 Sergio Basto 2015-02-09 19:57:40 UTC
(In reply to Sergio Monteiro Basto from comment #0)
> Description of problem:
> on menu of nm-connection-editor when click add , appears one menu if you
> expand that menu drop box , kde complete freeze . 
> with other gtk+ theme that see this problem. 

Correction : 

with other gtk+ theme I don't see this problem

Comment 4 Sergio Basto 2015-05-15 12:04:43 UTC

*** This bug has been marked as a duplicate of bug 1188289 ***