Description of problem: If you want to rename a file on your harddrive, you klick on the file you want to rename with right mousebutton and select rename. Now you can enter the new name of the file and if you press enter if your done, then filezilla crash. This happens only if you want to rename a file on your drive. The renaming on the ftp works. ------- CONSOLEOUTPUT: Reading locale option from /home/jurgen/.filezilla/filezilla.xml Gtk-Message: Failed to load module "canberra-gtk-module" (filezilla:4053): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'width >= -1' failed (filezilla:4053): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (filezilla:4053): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'width >= -1' failed (filezilla:4053): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'width >= -1' failed (filezilla:4053): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (filezilla:4053): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'width >= -1' failed wxD-Bus: Signal from /org/freedesktop/DBus, member NameAcquired wxD-Bus: Reply with serial 2 wxD-Bus: Signal: Error: The name org.gnome.SessionManager was not provided by any .service files ./src/common/wincmn.cpp(1501): assert "Assert failure" failed in RemoveEventHandler(): where has the event handler gone? Trace/Breakpoint ausgelöst ------- ASSERT INFO: ./src/common/wincmn.cpp(1501): assert "Assert failure" failed in RemoveEventHandler(): where has the event handler gone? BACKTRACE: [1] wxWindowBase::RemoveEventHandler(wxEvtHandler*) [2] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const [3] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) [4] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) [5] wxEvtHandler::TryHereOnly(wxEvent&) [6] wxEvtHandler::ProcessEventLocally(wxEvent&) [7] wxEvtHandler::ProcessEvent(wxEvent&) [8] wxEvtHandler::SafelyProcessEvent(wxEvent&) [9] g_closure_invoke [10] g_signal_emit_valist [11] g_signal_emit [12] gtk_window_propagate_key_event [13] g_closure_invoke [14] g_signal_emit_valist [15] g_signal_emit [16] gtk_propagate_event [17] gtk_main_do_event [18] g_main_context_dispatch [19] g_main_loop_run [20] gtk_main [21] wxGUIEventLoop::DoRun() [22] wxEventLoopBase::Run() [23] wxAppConsoleBase::MainLoop() [24] wxEntry(int&, wchar_t**) [25] main [26] __libc_start_main [27] _start Reproducible: Steps to Reproduce:
Hardware: i586 => x86_64
Assignee: bugsquad => geiger.david68210
Oh yeah ! I've the same issue on my mga4 but not on Cauldron. So I think this issue comes from libwxgtku that filezilla-3.10.2 needs minimum 3.0.2 version while on mga4 we have only the maximum 2.9.5 version. @David Walser: what do you think about that?
Ok I confirm that this issue comes from wxgtk-2.9.5 provided by mga4. I've imported wxgtk-3.0.2 from Cauldron and rebuilt it on my mga4 to wxgtk3.0-3.0.2 then rebuilt filezilla-3.10.2 with this one. Installed and tested it, now the bug is fixed. So we have to import wxgtk3.0 in mga4? or is there another fix?
CC: (none) => luigiwalser
CC: (none) => oe
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Only Mageia 4 was affected. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD