Description of problem: 1. launched filezilla 2. clicked site manager button 3. selected a site on left side 4. clicked on CONNECT button result: - does not connect to the selected server - right frame continue to show up "not connected to any server" - pop up the abrt report resulted expected: - connect to selected server. The same happen with the quick connect drop down or filling the data in the top fields. Connecting to the same(s) FTP with other applications, in the same OS, work as expected. ------------------------------------------------------------------------------------------------------------------- Version-Release number of selected component: filezilla-3.9.0.6-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/filezilla crash_function: CCommandQueue::Idle executable: /usr/bin/filezilla kernel: 3.17.7-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 CCommandQueue::Idle at commandqueue.cpp:33 #1 CContextControl::CloseTab at context_control.cpp:343 #2 wxAppConsoleBase::CallEventHandler at src/common/appbase.cpp:623 #3 wxEvtHandler::ProcessEventIfMatchesId at src/common/event.cpp:1392 #4 wxEventHashTable::HandleEvent at src/common/event.cpp:998 #5 wxEvtHandler::TryHereOnly at src/common/event.cpp:1589 #6 TryBeforeAndHere at include/wx/event.h:3671 #7 wxEvtHandler::ProcessEventLocally at src/common/event.cpp:1522 #8 wxEvtHandler::ProcessEvent at src/common/event.cpp:1495 #9 wxEvtHandler::ProcessPendingEvents at src/common/event.cpp:1359
Created attachment 974087 [details] File: backtrace
Created attachment 974088 [details] File: build_ids
Created attachment 974089 [details] File: cgroup
Created attachment 974090 [details] File: core_backtrace
Created attachment 974091 [details] File: dso_list
Created attachment 974092 [details] File: environ
Created attachment 974093 [details] File: exploitable
Created attachment 974094 [details] File: limits
Created attachment 974095 [details] File: maps
Created attachment 974096 [details] File: open_fds
Created attachment 974097 [details] File: proc_pid_status
Created attachment 974098 [details] File: var_log_messages
The graphic interface is not responding as expected. the dmesg show clearly some problem with the graph system: [97782.219961] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! [97848.925464] radeon 0000:00:01.0: evergreen_cs_track_validate_texture:850 texture bo too small (layer size 119552, offset 0, max layer 1, depth 1, bo size 4096) (64 467) The message happen at EACH launch of the filezilla If I open the filezilla, choose a server from the site manager and connect nothing happen. the window rest blank except the locals dirs. If I double click the Filezilla title bar in order to reduce the window the windows loose any label and keep just the border outsight and insight When I double click again the title bar it go up and there, the log show "connected" and some data of the dirs appears. double click again on to the title bar , blank again. Try to click on to the directory in order to CD, it do not dive into the dir. click to close on the X top right. It close. But I NEVER seen filezilla closing s quicly, --------------------------------------------- /var/log/messages show: 05:17:53 kernel: [97848.925464] radeon 0000:00:01.0: evergreen_cs_track_validate_texture:850 texture bo too small (layer size 119552, offset 0, max layer 1, depth 1, bo size 4096) (64 467) 05:17:53 kernel: [97848.925476] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! 05:17:53 kernel: radeon 0000:00:01.0: evergreen_cs_track_validate_texture:850 texture bo too small (layer size 119552, offset 0, max layer 1, depth 1, bo size 4096) (64 467) 05:17:53 kernel: [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! 05:18:01 systemd: Starting Paths. 05:18:01 systemd: Reached target Paths. 05:18:01 systemd: Starting Timers. 05:18:01 systemd: Reached target Timers. 05:18:01 systemd: Starting Sockets. 05:18:01 systemd: Reached target Sockets. 05:18:01 systemd: Starting Basic System. 05:18:01 systemd: Reached target Basic System. 05:18:01 systemd: Starting Default. 05:18:01 systemd: Reached target Default. 05:18:01 systemd: Startup finished in 63ms. 05:20:09 systemd: Stopping Default. 05:20:09 systemd: Stopped target Default. 05:20:09 systemd: Stopping Basic System. 05:20:09 systemd: Stopped target Basic System. 05:20:09 systemd: Stopping Paths. 05:20:09 systemd: Stopped target Paths. 05:20:09 systemd: Stopping Timers. 05:20:09 systemd: Stopped target Timers. 05:20:09 systemd: Stopping Sockets. 05:20:09 systemd: Stopped target Sockets. 05:20:09 systemd: Starting Shutdown. 05:20:09 systemd: Reached target Shutdown. 05:20:09 systemd: Starting Exit the Session... 05:20:09 systemd: Received SIGRTMIN+24 from PID 26131 (kill). 05:21:02 systemd: Starting Paths. 05:21:02 systemd: Reached target Paths. 05:21:02 systemd: Starting Timers. 05:21:02 systemd: Reached target Timers. 05:21:02 systemd: Starting Sockets. 05:21:02 systemd: Reached target Sockets. 05:21:02 systemd: Starting Basic System. 05:21:02 systemd: Reached target Basic System. 05:21:02 systemd: Starting Default. 05:21:02 systemd: Reached target Default. 05:21:02 systemd: Startup finished in 71ms. 05:21:02 dnf: cachedir: /var/cache/dnf/x86_64/21 05:21:03 dnf: DNF version: 0.6.3 05:21:03 dnf: Making cache files for all metadata files. 05:21:03 dnf: Metadata cache refreshed recently. 05:23:10 systemd: Stopping Default. 05:23:10 systemd: Stopped target Default. 05:23:10 systemd: Stopping Basic System. 05:23:10 systemd: Stopped target Basic System. 05:23:10 systemd: Stopping Paths. 05:23:10 systemd: Stopped target Paths. 05:23:10 systemd: Stopping Timers. 05:23:10 systemd: Stopped target Timers. 05:23:10 systemd: Stopping Sockets. 05:23:10 systemd: Stopped target Sockets. 05:23:10 systemd: Starting Shutdown. 05:23:10 systemd: Reached target Shutdown. 05:23:10 systemd: Starting Exit the Session... 05:23:10 systemd: Received SIGRTMIN+24 from PID 26931 (kill). 05:24:01 systemd: Starting Paths. 05:24:01 systemd: Reached target Paths. 05:24:01 systemd: Starting Timers. 05:24:01 systemd: Reached target Timers. 05:24:01 systemd: Starting Sockets. 05:24:01 systemd: Reached target Sockets. 05:24:01 systemd: Starting Basic System. 05:24:01 systemd: Reached target Basic System. 05:24:01 systemd: Starting Default. 05:24:01 systemd: Reached target Default. 05:24:01 systemd: Startup finished in 33ms. 05:26:09 systemd: Stopping Default. 05:26:09 systemd: Stopped target Default. 05:26:09 systemd: Stopping Basic System. 05:26:09 systemd: Stopped target Basic System. 05:26:09 systemd: Stopping Paths. 05:26:09 systemd: Stopped target Paths. 05:26:09 systemd: Stopping Timers. 05:26:09 systemd: Stopped target Timers. 05:26:09 systemd: Stopping Sockets. 05:26:09 systemd: Stopped target Sockets. 05:26:09 systemd: Starting Shutdown. 05:26:09 systemd: Reached target Shutdown. 05:26:09 systemd: Starting Exit the Session... 05:26:09 systemd: Received SIGRTMIN+24 from PID 27761 (kill). 05:27:01 systemd: Starting Paths. 05:27:01 systemd: Reached target Paths. 05:27:01 systemd: Starting Timers. 05:27:01 systemd: Reached target Timers. 05:27:01 systemd: Starting Sockets. 05:27:01 systemd: Reached target Sockets. 05:27:01 systemd: Starting Basic System. 05:27:01 systemd: Reached target Basic System. 05:27:01 systemd: Starting Default. 05:27:01 systemd: Reached target Default. 05:27:01 systemd: Startup finished in 42ms. 05:29:09 systemd: Stopping Default. 05:29:09 systemd: Stopped target Default. 05:29:09 systemd: Stopping Basic System. 05:29:09 systemd: Stopped target Basic System. 05:29:09 systemd: Stopping Paths. 05:29:09 systemd: Stopped target Paths. 05:29:09 systemd: Stopping Timers. 05:29:09 systemd: Stopped target Timers. 05:29:09 systemd: Stopping Sockets. 05:29:09 systemd: Stopped target Sockets. 05:29:09 systemd: Starting Shutdown. 05:29:09 systemd: Reached target Shutdown. 05:29:09 systemd: Starting Exit the Session... 05:29:09 systemd: Received SIGRTMIN+24 from PID 28598 (kill). ------------------------------- .xsession-error show a te start of the following info a line of 498 000 to 508 000 NULL chars and the following: Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. please move it to /home/lorenzo/.config/fontconfig/fonts.conf manually (filezilla:365): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed (filezilla:365): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'height >= -1' failed (filezilla:365): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed (filezilla:365): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed (filezilla:365): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'height >= -1' failed (filezilla:365): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed (filezilla:365): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'height >= -1' failed (filezilla:365): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'height >= -1' failed (filezilla:365): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'height >= -1' failed plasma-desktop(1685)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application virtual void NetworkManager::Device::propertyChanged(const QString&, const QVariant&) Unhandled property "AccessPoints" virtual void NetworkManager::Device::propertyChanged(const QString&, const QVariant&) Unhandled property "AccessPoints" Reading locale option from /home/lorenzo/.filezilla/filezilla.xml 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 wxD-Bus: CPowerManagementInhibitor: Requesting busy wxD-Bus: Reply with serial 3 wxD-Bus: CPowerManagementInhibitor: Request successful, cookie is 6 wxD-Bus: CPowerManagementInhibitor: Requesting idle =========================================================================== later i will strace it Thank you for your time and attention. cheers.
Another user experienced a similar problem: Tried to connect to a server. FileZilla hung for a while and when I clicked the "x" to close a tab with the hanging connection, the error appeared. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: filezilla crash_function: CCommandQueue::Idle executable: /usr/bin/filezilla kernel: 4.0.7-200.fc21.x86_64 package: filezilla-3.10.2-0.1.fc21 reason: filezilla killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.