GNOME Bugzilla – Bug 524341
nautilus crashed with SIGSEGV in column_compare()
Last modified: 2009-04-21 13:52:05 UTC
The bug has been described on https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/201023 "Thread 3 (process 8111):
+ Trace 193302
Thread 1 (process 8110)
Created attachment 108003 [details] [review] patch I really don't understand how both |all_columns| and |column_order| can be NULL there, but adding a NULL check before using |column_order| is not harmful and should solve this crash.
I agree its quite weird, there is probably some gconf setup issue. However, checking for NULL is probably a good idea, even though it may just mean nautilus crashes in some other place due to the weird setup.
Fixed in master. commit 7da1601ba6288e48dc6ed3023de03fff04d20b2d Author: Cosimo Cecchi <cosimoc@gnome.org> Date: Tue Apr 21 15:49:31 2009 +0200 Check for NULL when sorting columns Check for a NULL value of the order array when sorting the columns. This might help when dealing with strange GConf setup issues (#524341).