Fix caja crash during startup #101
Conversation
Closed #100 Signed-off-by: Willy Sudiarto Raharjo <willysr@gmail.com>
|
@willysr : from documentation, Can you try if '-n' fixes the issue for you, instead? It was suggested in the past, and also GNOME does the same |
|
No, -n doesn't work |
|
multiple instances -> how many instances you get? |
a lot, because when it failed to open an instance, it tries to open Willy Sudiarto Raharjo |
|
so now I understand your issue it's different from the issue fixed with -n |
Here's the result willysr@desktop: warning: unable to open /proc file '/proc/22084/status' warning: unable to open /proc file '/proc/22084/status' Temporary breakpoint 1, 0x080840f5 in main () Willy Sudiarto Raharjo |
Another information from dmesg [81367.304352] caja[20509]: segfault at 4 ip b6c77354 sp bfa25480 FYI, i'm using cairo-1.12.14 Willy Sudiarto Raharjo |
|
|
|
More info on the console after logging out MATE (caja:24802): Gdk-CRITICAL **: IA__gdk_cairo_create: assertion Willy Sudiarto Raharjo |
|
uhm, where do you create this entry with --sync ? |
/usr/share/applications/caja.desktop Willy Sudiarto Raharjo |
|
Worked like a charm, many thnx, ive been struggling for days to fix this :) |
|
@willysr is this issue always reproducible on slackware? |
Not always Willy Sudiarto Raharjo |
|
@willysr did you try to enable caja debug log? |
I did and i had posted them before on this bug report as well Willy Sudiarto Raharjo |
|
@willysr uhm, I dont see ~/caja-debug-log.txt up. Am I wrong? |
Well, i tried making caja-debug-log.conf with these values [debug log] and when i restarted my MATE without using --sync, caja instances are Willy Sudiarto Raharjo |
|
Does this info gives you more debug information? Initializing caja-open-terminal extension Willy Sudiarto Raharjo |
|
Today it happend again after session start with one caja window, i use caja -n in desktop file. Some days ago it happend during the session with tons of windows and unstoppable. |
|
how about changing it to --sync instead of -n ? |
|
The fix for this should be to delete the nautilus.desktop file on That is how i fixed it previously, an update may have replaced that file. On Sat, May 18, 2013 at 9:48 AM, Willy Sudiarto Raharjo <
Regards*
Banking Details : |
|
i don't have nautilus.desktop on /usr/share/applications here |
|
i add -n in /usr/share/applications/caja.desktop, exec line |
|
the problem previously was that both caja and nautilus were starting up On Sat, May 18, 2013 at 10:08 AM, Wolfgang Ulbrich <notifications@github.com
Regards*
Banking Details : |
|
You can read about the issue here as well : mate-desktop/mate-session-manager#19 if one of the methods work for you, please let me know so i can update the On Sat, May 18, 2013 at 10:43 AM, Jacque Raymer raymerjacque@gmail.comwrote:
Regards*
Banking Details : |
|
removing /usr/share/applications/caja.desktop was a bad idea because than Mate session starts without 'caja hande the desktop', no desktop background and right click menu. "the problem previously was that both caja and nautilus were starting up together, removing nautilus startup entry fixed the problem"
[Desktop Entry] |
|
first restart of session works well, i will observe this further. |
|
ok, please explain step by step what you did to fix the problem. On Sat, May 18, 2013 at 11:10 AM, Wolfgang Ulbrich <notifications@github.com
Regards*
Banking Details : |
|
I tested the above suggestion, but still no joy |
|
Ok.
-- pluma /etc/xdg/autostart/caja-autostart.desktop Now you will see this entry in autostart. In result /etc/xdg/autostart/caja-autostart.desktop starts now caja and not mate-session-daemon. It seems there is another positiv effect, imo the desktop starts faster. |
|
@willysr |
|
No wonder i have no effect when testing the previous solution |
|
@NiceandGently with your solution, caja is not autorestarted if it crashes |
|
@stefano-k |
|
@willysr issue is different from multiple x-caja-desktop windows at login. this issue is related to a caja crash on startup. mate-session restarts caja and it crashes again, causing an infinite loop. |
|
@willysr btw, a backtrace would be really useful |
|
@stefano-k : I tried to make a backtrace using the information you gave me, but it didn't produce any backtrace |
|
@willysr , @stefano-k |
|
Closing, as this is not the right solution but only an hack |
Closed #100
Signed-off-by: Willy Sudiarto Raharjo willysr@gmail.com