Bug#251751: nautilus: Does not start - fails to pass its own checks

[Adam Majer]

Sebastien Bacher wrote:

>Le dim, 30/05/2004 à 12:22 -0500, Adam Majer a écrit :
>  
>
>>Package: nautilus
>>Version: 2.6.1-3
>>Severity: grave
>>Justification: renders package unusable
>>    
>>
>
>Hi,
>
>Nautilus is running, why this severity ? Just because some checks fail ?
>This bug is already reported : 
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241655
>
>I'm setting the severity to minor and merging the bugs.
>
>
>Thanks,
>
>Sebastien Bacher
>
>  
>
It is not running here. It doesn't fail tests, it doesn't run at all. It
gets stuck waiting for a futex,

gettimeofday({1085937180, 135434}, NULL) = 0
pipe([19, 20])                          = 0
pipe([21, 22])                          = 0
sched_get_priority_max(SCHED_OTHER)     = 0
sched_get_priority_min(SCHED_OTHER)     = 0
mmap2(NULL, 8388608, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x41105000
mprotect(0x41105000, 4096, PROT_NONE)   = 0
clone(child_stack=0x41904b48,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID|CLONE_DETACHED,
parent_tidptr=0x41904bf8, {entry_number:6,
base_addr:0x41904bb0, limit:1048575, seg_32bit:1, contents:0,
read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1},
child_tidptr=0x41904bf8) = 17730
futex(0x40af8e40, FUTEX_WAKE, 1)        = 1
brk(0)                                  = 0x820b000
brk(0x822c000)                          = 0x822c000
gettimeofday({1085937180, 136689}, NULL) = 0
gettimeofday({1085937180, 136971}, NULL) = 0
writev(18, [{"GIOP\1\2\1\0\275\2\0\0", 12}, {"
\360\377\277\3\0\0\0\0\0\0\0\34\0\0\0\0\0\0\0\2450\30"..., 701}], 2) = 713
futex(0x8117978, FUTEX_WAIT, 0, NULL <unfinished ...>


This happens *always* since two days ago after Gnome 1.6 went into Sid.
I don't think that has anything to do with the other bug. The 'nautilus
-c' is just one way to trigger it. Another is just to run nautilus.
Gnome starts nautilus but nothing shows up and strace reveils the same
problem - nautlius gets stuck in futex(...) syscall.

I'm using kernel 2.6.6 from Sid so I don't know if that is related or not.

Maybe I titled the report wrong somewhat wrong, but it appears that you
have not even read the report. This bug has nothing to do with failure
of checks, it fails to *run* the checks. It fails to *run* at all.

- Adam