Version-Release number of selected component: gnome-shell-3.6.2-6.fc18 Additional info: backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 10961ccf80f53df967135870076034179100000053180000 crash_function: js_ResumeThread executable: /usr/bin/gnome-shell kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 200 Truncated backtrace: Thread no. 1 (10 frames) #0 js_ResumeThread at jslock.cpp:619 #1 js_Dequeue at jslock.cpp:659 #2 ThinUnlock at jslock.cpp:690 #3 js_Unlock at jslock.cpp:708 #4 ~AutoLockAtomsCompartment at jscntxt.h:2646 #5 js_AtomizeString at jsatom.cpp:544 #6 js_Atomize at jsatom.cpp:580 #7 JS_GetProperty at jsapi.cpp:3824 #8 gjs_object_get_property at gjs/jsapi-util.c:391 #9 gjs_keep_alive_get_from_parent at gi/keep-alive.c:350
Created attachment 689149 [details] File: backtrace
Created attachment 689150 [details] File: cgroup
Created attachment 689151 [details] File: core_backtrace
Created attachment 689152 [details] File: dso_list
Created attachment 689153 [details] File: environ
Created attachment 689154 [details] File: limits
Created attachment 689155 [details] File: maps
Created attachment 689157 [details] File: open_fds
Created attachment 689158 [details] File: proc_pid_status
Created attachment 689159 [details] File: smolt_data
Created attachment 689160 [details] File: var_log_messages
This problem emerged when trying to configure a VNC server process using tigervnc. When another user tries to connect it is shown a message "ops something went wrong" and only the wallpapaer is shown. The remote connected user cannot actually do anything. I tried both with VNC viewer and ultravnc, same result. backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js_ResumeThread executable: /usr/bin/gnome-shell kernel: 3.8.4-202.fc18.x86_64 package: gnome-shell-3.6.3.1-1.fc18 reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1 xsession_errors: (gnome-shell:1664): Clutter-WARNING **: Actor '<searchEntry>[<StEntry>:0x1f11bb0]' should not be mapped if parent '<overview>[<StWidget>:0x1e1aa20]'is not visible
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.