Le Thu, 22 Nov 2007 18:39:18 -0600, Javier Vasquez <[EMAIL PROTECTED]> a écrit :
> What do you recommend me to do in oreder to get /usr/bin/X running
> properly? Do you know if I'm the only one reporting this?
Hi,
I had the same problem and X works fine if I set /usr/bin/Xorg
setuid as Samue
Le Fri, 23 Nov 2007 16:37:49 +0100, Michael Banck <[EMAIL PROTECTED]> a écrit :
> On Thu, Nov 22, 2007 at 07:13:15PM -0600, Javier Vasquez wrote:
>> The message actually indicates "/usr/bin/dpkg" as you pointed out...
>
> OK, then note down which packages are about to be installed, and try to
> ins
Le Fri, 23 Nov 2007 16:49:16 +, Samuel Thibault
<[EMAIL PROTECTED]> a écrit :
> That's not the proper fix.
> We need to know the error message so as to correct this.
If X is not a link to Xorg, nothing happens if I try to start X
(directly X, not startx), I immediately get a new shell prom
Le Fri, 23 Nov 2007 18:29:34 +0100, Michael Banck <[EMAIL PROTECTED]> a écrit :
> Did you configure x11-common to allow anybody to start the X server?
Yes, without that the error message says clearly that it's
impossible to determine whether we are using a console or not.
I have searched w
Hi,
All the information I've found about the hardware supported by
Debian GNU/Hurd say that there is no USB support at all, but my USB
keyboard and mouse seem to work, has there been progress recently? I
found nothing about that in the last months'archives of the bug-hurd,
hurd-devel-readers
Le Wed, 28 Nov 2007 20:41:21 -0600, Javier Vasquez <[EMAIL PROTECTED]> a écrit :
> With Today's upgrade, including xorg's and xserver-xorg's ones, it
> seems that the problem is gone. I removed the link after the upgrade,
> and removed the setuid/setgid bits, and things work now...
>
> BTW, seems
Le Wed, 28 Nov 2007 15:06:30 +, Samuel Thibault
<[EMAIL PROTECTED]> a écrit :
> Thank your BIOS ;)
>
> (look for keywords like USB legacy support in setup)
OK, I did not remember that there were things about USB in the BIOS setup
:) Thanks to you and Michael Banck for your replies.
--
Fabien
Le Thu, 13 Dec 2007 21:34:35 +0100, Fabienne Ducroquet
<[EMAIL PROTECTED]> a écrit :
> [ CC'ed to
> [EMAIL PROTECTED]
messages from non-suscribers need are moderated
> and [EMAIL PROTECTED] ]
... which rejects automatically all messages from non-suscribers.
> All the key
Le Fri, 14 Dec 2007 19:56:33 +0100, Fabienne Ducroquet
<[EMAIL PROTECTED]> a écrit :
> Le Thu, 13 Dec 2007 21:34:35 +0100, Fabienne Ducroquet
The message to which I was replying is in the gmane archive but not
in the web archive of debian-hurd, so I resend its content, sorry for
the
On Sat, 15 Dec 2007 22:36:21 +0200, Kalle Olavi Niemitalo <[EMAIL PROTECTED]>
wrote:
> This suggests ELinks has failed to disable echoing at the terminal.
> Please verify this by looking up the tty that ELinks is using and
> checking the modes with a command like this:
>
> stty -F /dev/pts/1 -a
>
Le Tue, 18 Dec 2007 20:46:03 +0100, Fabienne Ducroquet
<[EMAIL PROTECTED]> a écrit :
> I've found that the function free_itrm is called later and it unsets
> these modes. It is called by select_loop line 305 while i = 7 and n = 1.
The same happens with Links 1.00p
Le Wed, 19 Dec 2007 00:44:46 +0100, Fabienne Ducroquet
<[EMAIL PROTECTED]> a écrit :
> and more precisely, that seems to happen after
> set_handlers has been called with read_func = 0, write_func = 0 and
> error_func = &free_itrm (or &free_trm). After that, all the cal
On Thu, Dec 20, 2007 at 12:40:10AM +0200, Kalle Olavi Niemitalo wrote:
> free_itrm should be called only if an error or EOF occurs in
> terminal handling, or when ELinks is exiting.
Did you receive all my replies? I sent 3 successive replies through
gmane during my investigation but I see only
On Thu, Dec 20, 2007 at 06:29:51AM +0200, Kalle Olavi Niemitalo wrote:
> > 114 if (!len) return;
> > (gdb) n
> > 116 if (!itrm->out.queue.len && can_write(itrm->out.sock)) {
> > (gdb) n
> > 119 register_bottom_half(free_itrm, itrm);
> > (gdb) n
> > 124
14 matches
Mail list logo
