Re: rsbac menu problems

Daniel Cegielka <[email protected]>
Newsgroups gmane.linux.rsbac
Message-ID <[email protected]>
THX for help Javier ;)

There is small problem with gpm.
rsbac_menu works fine on hardened gentoo if you start gpm
(/etc/init.d/gpm start) or you can recompile ncurses with USE="-gpm"


Javier J. Martínez Cabezón pisze:
> /tmp is not full, I have not configured gpm (I don't use the mouse, so
> had the default values) so it could be perfectly the second scenario
> you gave mention.
> 
> 2008/12/21 Amon Ott <[email protected]>:
>> Am Sonntag 21 Dezember 2008 schrieb Javier J. Martínez Cabezón:
>>> Hi folks, when using the dialog rsbac_menu interface (or another one)
>>> program if you switch any item it appears the following message error:
>>>       Main Menu: Selection Error!.
>>>
>>> I'm running one gentoo hardened linux under a VirtualBox environment,
>>> installed and updated from 2008 version (with not extra USE flags and
>>> only with a -D_FORTIFY_SOURCE=2 flag used to compile by default). It
>>> seems to be related with gpm (this gentoo version comes with
>>> 1.20.1-r6). I resolved it simply removing the gpm package. Have anyone
>>> in the mailing list had the same problem?
>>>
>>> I don't know yet what made it fail, but I send this feedback because
>>> is an silly and stupid problem enough to make you lose your time.
>> So far, I have only seen that error when the partition with /tmp was read-only
>> or full.
>>
>> Can it be that dialog spits out gpm errors on stderr, too, so that the real
>> dialog output gets corrupted?
>>
>> Amon.
>> --
>> http://www.rsbac.org - GnuPG: 2048g/5DEAAA30 2002-10-22
>> _______________________________________________
>> rsbac mailing list
>> [email protected]
>> http://www.rsbac.org/mailman/listinfo/rsbac
>>
> _______________________________________________
> rsbac mailing list
> [email protected]
> http://www.rsbac.org/mailman/listinfo/rsbac
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.