Description of problem: Trying lxqt for the first time. I've got this crash on startup. Not sure it's a valid bug, as lxqt is not part of Fedora. But maybe somebody would want to see the debug information anyway. The applet is actually working now, I guess it was restarted automatically. Version-Release number of selected component: network-manager-applet-0.9.9.0-9.git20140123.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/nm-applet crash_function: _gdk_x11_display_error_event executable: /usr/bin/nm-applet kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2557 #5 handle_error at xcb_io.c:213 #6 handle_response at xcb_io.c:325 #7 _XEventsQueued at xcb_io.c:364 #8 XPending at Pending.c:55 #9 gdk_check_xpending at gdkeventsource.c:266 #10 gdk_event_source_check at gdkeventsource.c:303 #11 g_main_context_check at gmain.c:3557 Potential duplicate: bug 913370
Created attachment 902383 [details] File: backtrace
Created attachment 902384 [details] File: cgroup
Created attachment 902385 [details] File: core_backtrace
Created attachment 902386 [details] File: dso_list
Created attachment 902387 [details] File: environ
Created attachment 902388 [details] File: limits
Created attachment 902389 [details] File: maps
Created attachment 902390 [details] File: open_fds
Created attachment 902391 [details] File: proc_pid_status
Created attachment 902392 [details] File: var_log_messages
Another user experienced a similar problem: I suppose this is related to Cinnamon crash which happens several times reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: nm-applet crash_function: _gdk_x11_display_error_event executable: /usr/bin/nm-applet kernel: 3.14.4-200.fc20.x86_64 package: network-manager-applet-0.9.9.0-10.git20140123.fc20 reason: nm-applet killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.