| Summary: | filezilla functions not working | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | William Kenney <wilcal.int> |
| Component: | RPM Packages | Assignee: | David GEIGER <geiger.david68210> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | geiger.david68210 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | filezilla-3.17.0.1-1.mga6.i586.rpm & filezilla-3.17.0.1-1.mga6.x86_64.rpm | CVE: | |
| Status comment: | |||
| Attachments: |
horizantal bars cannot be moved up or down
horizantal bars cannot be moved up or down text messed up |
||
|
Description
William Kenney
2016-05-24 19:11:48 CEST
Created attachment 7852 [details]
horizantal bars cannot be moved up or down
(In reply to William Kenney from comment #0) > The vertical bars cannot be moved up or down. s/b horizontal bars Created attachment 7853 [details]
horizantal bars cannot be moved up or down
Created attachment 7854 [details]
text messed up
Yes same issue here, certainly linked to GTK3 :( CC:
(none) =>
geiger.david68210
David GEIGER
2016-05-24 19:37:35 CEST
Assignee:
bugsquad =>
geiger.david68210 I think this is even more a wxgtk issue. Or perhaps comes also from the theme? can you try with another theme, please? In VirtualBox, M6, KDE, 64-bit (In reply to David GEIGER from comment #7) > Or perhaps comes also from the theme? > > can you try with another theme, please? Hmmmm..... this does not seem to be a problem when I use the Live-media. Theme does not make any difference. The platform I was testing on was a Vbox CI install. But, the Edit -> Settings is all screwed up. More testing here. William, could you report upstream to see what they think about this issue? https://trac.filezilla-project.org/ Thanks in advance! Well! I opened a bug upstream: https://trac.filezilla-project.org/ticket/10847#ticket Well! should be fixed now with filezilla-3.18.0-2.mga6 rebuilt against wxgtk compiled with gtk2. please test, thanks in advance! Tested here, I confirm this is issue is now fixed. Closing of this bug as it is fixed. Status:
NEW =>
RESOLVED |