Re: Xterm and GNU/kFreeBSD
Hi,
I installed a fresh kfreebsd-i386 squeeze last night and I also tested xorg.
I used,
apt-get install xserver-xorg-video-via xterm openbox xinit
Ofcourse a lot of more stuff went in..
Anyways, My x works flawless and so does xterm, I had no problems
using openbox to launch a working xterm.
On Tue, Dec 7, 2010 at 21:33, Mats Erik Andersson
<mats.andersson@gisladisker.se> wrote:
> (Repeating this seemingly lost message, with an important addition.)
>
> tisdag den 7 december 2010 klockan 19:59 skrev Cyril Brulebois detta:
>> Hi,
>>
>> Mats Erik Andersson <mats.andersson@gisladisker.se> (07/12/2010):
>> > Dear all,
>> >
>> > with the risk of making a fool of myself, I need to address an issue.
>> > Is Xorg/Xterm really working impeccably within GNU/kFreeBSD? Are all
>> > dependencies brought in as needed?
>> >
>> > In essence, I started with
>> >
>> > # apt-get install xserver-xorg-video-vesa twm xterm
>> >
>> > Still it is not possible to access Xterm, neither from Twm, nor after
>> >
>> > $ startx xterm
>> >
>> > The terminal window is created, but no user input is possible.
>> > In another effort I have patched Xvt for GNU/kFreeBSD. Originally,
>> > it was was able to complain on the lack of controlling terminal,
>> > but after patching which amends this, this complaint disappears.
>> > Thus I know that Xorg/startx cat execute applications, but there
>> > seems to be deficiencies on the event level. Or?
>>
>> You installed a video driver, and clients. You probably want to
>> install xserver-xorg-input-{mouse,kbd} as well. If those are installed
>> as well, please run the X bug script, and attach its output:
>> /usr/share/bug/xorg/script 3>/tmp/script.log
>>
>> That's why we have metapackages like xorg and xserver-xorg.
>
> The packages x-x-input-all, x-x-input-kbd, and x-x-input-mouse
> were brought in without my interaction (As far as I recall now).
> That is not the problem. In contrast, I imported "xinit" myself.
>
> A most remarkable behaviour is this:
>
> $ startx xterm
>
> produces a display with a rapidly blinking/glimmering and only
> outlines cursor, no prompt. Then the X server is shutting itself
> down after a few seconds. The call
>
> $ startx /usr/bin/xterm
>
> arrives at a rock solid terminal window, displaying a prompt,
> and a steady, outlined cursor. It does not accept any input.
>
> These are the available phenomena. Neither is expected. Right?
>
> Once I reconfigure hal, the call
>
> $ startx /usr/bin/xterm
>
> reproducibly leads to success with functional keyboard and mouse.
> Equally reproducible, the call with implied path
>
> $ startx xterm
>
> fails to produce a functional terminal window. Afterwards,
>
> xorg-vesa-aborted-with-restarted-hal.txt
>
> is recorded using the debug script.
>
>
> Best regards,
> Mats E A
>
--
Lars @ lansink.se powered by gmail.com
Reply to: