Zack Weinberg wrote:
> On Thu, Apr 9, 2009 at 9:45 PM, Gary Kramlich wrote:
>> $ which mtn; sudo which mtn
>> /usr/bin/mtn
>> /usr/bin/mtn
>>
>> But it does get weirder, it works fine for other users on my machine.
>> Just not me. So this is obviously some crazy config problem. However,
>> I did
Zack Weinberg wrote:
> On Thu, Apr 9, 2009 at 9:45 PM, Gary Kramlich wrote:
>> $ which mtn; sudo which mtn
>> /usr/bin/mtn
>> /usr/bin/mtn
>>
>> But it does get weirder, it works fine for other users on my machine.
>> Just not me. So this is obviously some crazy config problem. However,
>> I did
On Thu, Apr 9, 2009 at 9:45 PM, Gary Kramlich wrote:
> $ which mtn; sudo which mtn
> /usr/bin/mtn
> /usr/bin/mtn
>
> But it does get weirder, it works fine for other users on my machine.
> Just not me. So this is obviously some crazy config problem. However,
> I did move ~/.monotone out of the w
Zack Weinberg wrote:
> On Thu, Apr 9, 2009 at 8:11 PM, Gary Kramlich wrote:
>> Also, works fine as root under X.
>>
>> $ mtn --version
>> Segmentation fault
>> $ sudo mtn --version
>> monotone 0.43 (base revision: ddc6546051abf6475c40a3fdba272e2f82a40e94)
>
> That plus the other output you poste
On Thu, Apr 9, 2009 at 8:11 PM, Gary Kramlich wrote:
> Also, works fine as root under X.
>
> $ mtn --version
> Segmentation fault
> $ sudo mtn --version
> monotone 0.43 (base revision: ddc6546051abf6475c40a3fdba272e2f82a40e94)
That plus the other output you posted does suggest a path problem -
m
On Thu, Apr 9, 2009 at 6:57 PM, Gary Kramlich wrote:
>
> debsums found nothing. all my filesystems were in pretty bad shape,
> somehow the journals kept them alive. They're all clean now, problem
> persists.
Ok.
> g...@cloak:~$ LD_DEBUG=files mtn --version
> 8031:
> 8031: file=li
Zack Weinberg wrote:
> On Wed, Apr 8, 2009 at 9:09 PM, Gary Kramlich wrote:
>> any invocation of mtn is causing a segfault. I have a core, but contains a
>> single frame of:
>>
>> #0 0x in _start () from /lib64/ld-linux-x86-64.so.2
>>
>> Even a simple "mtn --version" outside of
Zack Weinberg wrote:
> On Wed, Apr 8, 2009 at 9:09 PM, Gary Kramlich wrote:
>> any invocation of mtn is causing a segfault. I have a core, but contains a
>> single frame of:
>>
>> #0 0x in _start () from /lib64/ld-linux-x86-64.so.2
>>
>> Even a simple "mtn --version" outside of
On Thu, Apr 9, 2009 at 5:25 AM, Ludovic Brenta
wrote:
> Zack, can you reproduce this bug? Should I wait for a resolution before I
> upload 0.43-2, or can I proceed? I plan to upload this evening (~7 hours from
> now) or tomorrow.
I cannot reproduce the bug, and to me it looks like a damaged shar
On Wed, Apr 8, 2009 at 9:09 PM, Gary Kramlich wrote:
> any invocation of mtn is causing a segfault. I have a core, but contains a
> single frame of:
>
> #0 0x in _start () from /lib64/ld-linux-x86-64.so.2
>
> Even a simple "mtn --version" outside of a working copy results in a s
10 matches
Mail list logo
