-
-
Notifications
You must be signed in to change notification settings - Fork 145
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
caja crashes, in loop until I just kill my whole mate-session #413
Comments
Oops. Was going to add more info accidentally closed it. |
Ok, so I installed some of the debuginfo packages so I could try to track this down. Stack trace is much more usefull. :>
|
Ok... I dug into this with gdb and worked through it. When it gets into find_best_size() it goes through both passes, never finding a best size. And in the end it best which is null. Looking at it a bit more.. no matter what the file was I was getting values for FileSize such as this (This was printing size from line on line 2336) from file mate-bg.c on May 4th,2014, which I ended up guessing was the version in this code). So maybe this should go under the mate-desktop bugs? $32 = {width = -1, height = -1, file = 0x1697cf0 "/usr/share/backgrounds/night.jpg"} The width/height were always -1, I'm not entirely sure what it is doing here. |
I'm going to close this out and open it as an issue on the mate-desktop repo. |
Using CentOS 7.1 64 bit
Linux testmach 3.10.0-229.1.2.el7.x86_64 #1 SMP Fri Mar 27 03:04:26 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
mate-desktop-1.8.2-2.el7.x86_64
caja-1.8.2-1.el7.x86_64
All MATE installed from the EPEL repo
So I have been building "workstation VMs" for a number of people over the last few months. All using the MATE desktop. Users have been loving them. However, I just built a few more this week(hadn't built ones in a few weeks) and all the users are having caja crash in a big way. I have the build of these machines scripted, so they should all be built the same, just probably new versions of stuff out of CentOS/EPEL repos.
I can reproduce this on any of the VMs I built. I setup a VNCserver for users to connect to the Desktop, "mate-session" is their default so that is what comes up.
When switching from full screen to windowed on the VNCViewer, caja crashes, generates a core file. It then continues on to do so, generating additional core files every 30-40 seconds until I kill the how mate-session.
I'm not sure if this is VNC or VM related or not, its just the only way I have right now of working with this.
The really odd part, is that its only happening to completly new VM builds now. Everyone that had had it running before is not having any issues. Even if they issue a yum update.
I'd be happy to go into more detail or test things out. I have about 10 people really chomping on the bit to get a VM desktop to play with.
The stack trace of the bad thread is (same in all core files) other threads are just wait/polls
get_pixbuf_for_size () from /lib64/libmate-desktop-2.so.17
mate_bg_draw () from /lib64/libmate-desktop-2.so.17
mate_bg_create_pixmap () from /lib64/libmate-desktop-2.so.17
eel_background_ensure_realized ()
eel_background_set_up_widget ()
g_closure_invoke () from /lib64/libgobject-2.0.so.0
signal_emit_unlocked_R () from /lib64/libgobject-2.0.so.0
g_signal_emit_valist () from /lib64/libgobject-2.0.so.0
g_signal_emit () from /lib64/libgobject-2.0.so.0
gtk_widget_realize () from /lib64/libgtk-x11-2.0.so.0
gtk_widget_map () from /lib64/libgtk-x11-2.0.so.0
gtk_scrolled_window_forall () from /lib64/libgtk-x11-2.0.so.0
gtk_container_map () from /lib64/libgtk-x11-2.0.so.0
_g_closure_invoke_va () from /lib64/libgobject-2.0.so.0
g_signal_emit_valist () from /lib64/libgobject-2.0.so.0
g_signal_emit () from /lib64/libgobject-2.0.so.0
gtk_widget_map () from /lib64/libgtk-x11-2.0.so.0
gtk_box_forall () from /lib64/libgtk-x11-2.0.so.0
gtk_container_map () from /lib64/libgtk-x11-2.0.so.0
_g_closure_invoke_va () from /lib64/libgobject-2.0.so.0
g_signal_emit_valist () from /lib64/libgobject-2.0.so.0
g_signal_emit () from /lib64/libgobject-2.0.so.0
gtk_widget_map () from /lib64/libgtk-x11-2.0.so.0
gtk_box_forall () from /lib64/libgtk-x11-2.0.so.0
gtk_container_map () from /lib64/libgtk-x11-2.0.so.0
_g_closure_invoke_va () from /lib64/libgobject-2.0.so.0
g_signal_emit_valist () from /lib64/libgobject-2.0.so.0
g_signal_emit () from /lib64/libgobject-2.0.so.0
gtk_widget_map () from /lib64/libgtk-x11-2.0.so.0
gtk_box_forall () from /lib64/libgtk-x11-2.0.so.0
gtk_container_map () from /lib64/libgtk-x11-2.0.so.0
_g_closure_invoke_va () from /lib64/libgobject-2.0.so.0
g_signal_emit_valist () from /lib64/libgobject-2.0.so.0
g_signal_emit () from /lib64/libgobject-2.0.so.0
gtk_widget_map () from /lib64/libgtk-x11-2.0.so.0
gtk_table_forall () from /lib64/libgtk-x11-2.0.so.0
gtk_container_map () from /lib64/libgtk-x11-2.0.so.0
_g_closure_invoke_va () from /lib64/libgobject-2.0.so.0
g_signal_emit_valist () from /lib64/libgobject-2.0.so.0
g_signal_emit () from /lib64/libgobject-2.0.so.0
gtk_widget_map () from /lib64/libgtk-x11-2.0.so.0
gtk_window_map () from /lib64/libgtk-x11-2.0.so.0
map ()
_g_closure_invoke_va () from /lib64/libgobject-2.0.so.0
g_signal_emit_valist () from /lib64/libgobject-2.0.so.0
g_signal_emit () from /lib64/libgobject-2.0.so.0
gtk_widget_map () from /lib64/libgtk-x11-2.0.so.0
gtk_window_show () from /lib64/libgtk-x11-2.0.so.0
caja_window_show ()
caja_spatial_window_show ()
_g_closure_invoke_va () from /lib64/libgobject-2.0.so.0
g_signal_emit_valist () from /lib64/libgobject-2.0.so.0
g_signal_emit () from /lib64/libgobject-2.0.so.0
gtk_widget_show () from /lib64/libgtk-x11-2.0.so.0
caja_window_show_window ()
finish_loading ()
directory_ready_callback ()
ready_callback_call ()
call_ready_callbacks_at_idle ()
g_main_context_dispatch () from /lib64/libglib-2.0.so.0
g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0
g_main_loop_run () from /lib64/libglib-2.0.so.0
gtk_main () from /lib64/libgtk-x11-2.0.so.0
main ()
The text was updated successfully, but these errors were encountered: