| 1 |
On Mon, Dec 8, 2008 at 7:03 PM, Nikos Chantziaras <realnc@×××××.de> wrote: |
| 2 |
> Nikos Chantziaras wrote: |
| 3 |
>> |
| 4 |
>> Weird problem this one. I updated to sys-libs/glibc-2.9_p20081201 (from |
| 5 |
>> 2.8_p20080602) and everything appears to be just fine. With one exception: |
| 6 |
>> viewing files in Midnight Commander's built-in viewer doesn't work anymore. |
| 7 |
>> Pressing F3 (View) does nothing. Calling `mcview` or `mc -v file` also |
| 8 |
>> does nothing; the application simply exits with no error messages (or any |
| 9 |
>> other messages; just nothing). |
| 10 |
>> |
| 11 |
>> Anyone encountered this? I've rebuild mc of course and revdep-rebuild |
| 12 |
>> shows all is OK. |
| 13 |
> |
| 14 |
> I've solved it. I had to go ~arch on sys-kernel/linux-headers and rebuild |
| 15 |
> glibc. I was using stable headers before (2.6.23-r3). After I upgraded to |
| 16 |
> ~amd64 2.6.27-r2 and emerged glibc again, the bug went away. |
| 17 |
> |
| 18 |
> One more for the archive. Thanks anyone for trying to help :) |
| 19 |
|
| 20 |
Ah-ha. I didn't think about that, but every time I emerge kernel |
| 21 |
headers it suggests rebuilding glibc. I guess they added something new |
| 22 |
over the years :) |
| 23 |
|
| 24 |
Paul |
Archives