-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xiccd[3214]: segfault at e4 ip 00005638ed3fd9a2 #40
Comments
Can you please compile xiccd with debug and get a stack trace? |
I tried earlier to download and compile the source code but met many obstacles and left it for a while. I've now successfully compiled the code with debug symbols, but it's not very helpful, or I'm doing things wrong. I thought To compile xiccd i did following:
The file I received the error a while, eventhough the service seemed to run though.
Lately I havent got the error, but I changed from Gnome to XFCE.
|
It seems the bug still persistent when running
|
Below is a copy of what I just wrote in this page of Launchpad bugtracker, and this seems related to what Am0rphous reports above. [BOF] I recompiled xiccd in debug version and could track the crash I experienced down to (inline) function setup_events(), where member dpy of argument conn was null :
Function setup_events() has the following code:
Macro ScreenCount() is defined as follows in /usr/include/X11/Xlib.h:
Therefore, using ScreenCount (conn->dpy) results in a null-pointer dereferencing. Now for the cause: AFAICS, it seems that despite xiccd is already running on the target system, a new instance of xiccd is launched everytime VNC server is killed/restarted, and this new instance is the one which crashes. This may result from the custom version of $HOME/.vnc/Xstartup which is necessary to run Xtightvnc server on Xubuntu. Mine is as follows:
Hope everything above makes sense, last time I performed some debugging is a long time ago... |
Thank you! Will look at this. |
Hi!
On Kali Linux i receive following error message. I don't know if every line is helpful. Running
sudo dmesg
givesSystem (fully up to date)
The text was updated successfully, but these errors were encountered: