Hide Forgot
Description of problem: vnc remote session see: https://bugzilla.redhat.com/show_bug.cgi?id=1368821 Version-Release number of selected component: lxqt-panel-0.10.0-5.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: lxqt-panel crash_function: _XDefaultIOError executable: /usr/bin/lxqt-panel global_pid: 1275 kernel: 4.6.7-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #31 _XDefaultIOError at XlibInt.c:1258 #32 ioErrorHandler at qxcbconnection.cpp:159 #35 _XSeqSyncFunction at XlibInt.c:199 #36 XDamageDestroy at Xdamage.c:341 #37 TrayIcon::~TrayIcon at /usr/src/debug/lxqt-panel-0.10.0/plugin-tray/trayicon.cpp:203 #39 qDeleteAll<QList<TrayIcon*>::const_iterator> at /usr/include/qt5/QtCore/qalgorithms.h:317 #40 qDeleteAll<QList<TrayIcon*> > at /usr/include/qt5/QtCore/qalgorithms.h:325 #41 LXQtTray::stopTray at /usr/src/debug/lxqt-panel-0.10.0/plugin-tray/lxqttray.cpp:362 #42 LXQtTray::~LXQtTray at /usr/src/debug/lxqt-panel-0.10.0/plugin-tray/lxqttray.cpp:93 #44 LXQtTrayPlugin::~LXQtTrayPlugin at /usr/src/debug/lxqt-panel-0.10.0/plugin-tray/lxqttrayplugin.cpp:41
Created attachment 1195306 [details] File: backtrace
Created attachment 1195307 [details] File: cgroup
Created attachment 1195308 [details] File: core_backtrace
Created attachment 1195309 [details] File: dso_list
Created attachment 1195310 [details] File: environ
Created attachment 1195311 [details] File: exploitable
Created attachment 1195312 [details] File: limits
Created attachment 1195313 [details] File: maps
Created attachment 1195314 [details] File: mountinfo
Created attachment 1195315 [details] File: namespaces
Created attachment 1195316 [details] File: open_fds
Created attachment 1195317 [details] File: proc_pid_status
Created attachment 1195318 [details] File: var_log_messages
As already said in bug #1368821 and can help, we need more information about what you do to get the crashes.
As i wrote today in reponse to "comment 14" to get the crashes. install lxqt-desktop and vnc-server on a fedora computer. (refer to the fedora documentation for the details ...). remote login in this computer with you favourite vnc client. First login is ok logout. Login one more time : you get the crash
I suppose you mean tigervnc-server instead of vnc-server. vnc and tightvnc are both orphaned in favor of tigervnc. Reassigning to ask for help there.
*** Bug 1368821 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.