Jim Higson <[EMAIL PROTECTED]> writes:
> On 13 Jan 2004 08:20:24 -0500, Johan Kullstam <[EMAIL PROTECTED]>
> wrote:
>
> > Jim Higson <[EMAIL PROTECTED]> writes:
> >
> >> I'm still having these problems, on my main machine, which has
> >> resisted XFree from the start.
> >> As sugested, I've updat
On Tue, 13 Jan 2004 09:03:00 -0600, Kent West <[EMAIL PROTECTED]> wrote:
Jim Higson wrote:
On Mon, 12 Jan 2004 23:27:40 -0600, Kent West <[EMAIL PROTECTED]> wrote:
Yea! However, I would still encourage you to post this solution on
your original thread, for the sake of future knowledge searchers
Jim Higson wrote:
On Mon, 12 Jan 2004 23:27:40 -0600, Kent West <[EMAIL PROTECTED]> wrote:
Yea! However, I would still encourage you to post this solution on
your original thread, for the sake of future knowledge searchers.
I will do when I finally get it sorted - the x server is still crashin
On Tue, Jan 13, 2004 at 01:43:35PM -, Jim Higson wrote:
> On Mon, 12 Jan 2004 23:27:40 -0600, Kent West <[EMAIL PROTECTED]> wrote:
> >Jim Higson wrote:
> >>but after a few seconds moment there is a fatal server error: caught
> >>signal 11. Server aborting.
> >>
> >>I rebooted. This time I get t
On 13 Jan 2004 08:20:24 -0500, Johan Kullstam <[EMAIL PROTECTED]>
wrote:
Jim Higson <[EMAIL PROTECTED]> writes:
I'm still having these problems, on my main machine, which has
resisted XFree from the start.
As sugested, I've updated the kernel to the prebuilt image 2.4.18-k7
from the woody isos a
On Mon, 12 Jan 2004 23:27:40 -0600, Kent West <[EMAIL PROTECTED]> wrote:
Jim Higson wrote:
On Mon, 12 Jan 2004 16:34:48 -0600, Kent West <[EMAIL PROTECTED]> wrote:
Ah, yes; you have not usb support. Try running "modconf" and select
such things as usb/uhci (assuming you have uhci controllers - "
Jim Higson <[EMAIL PROTECTED]> writes:
> I'm still having these problems, on my main machine, which has
> resisted XFree from the start.
> As sugested, I've updated the kernel to the prebuilt image 2.4.18-k7
> from the woody isos and confirmed the update with uname. It still
> won't recognise my u
On Mon, 12 Jan 2004 23:17:02 -0600, Kent West <[EMAIL PROTECTED]> wrote:
Jim Higson wrote:
The mouse is now sorted, so I don't think I need post this.
Do you mean your mouse is working as you want properly? If so, I suggest
you post the solution so others in the future who are searching for
a
Jim Higson wrote:
On Mon, 12 Jan 2004 16:34:48 -0600, Kent West <[EMAIL PROTECTED]> wrote:
Ah, yes; you have not usb support. Try running "modconf" and select
such things as usb/uhci (assuming you have uhci controllers - "lspci
-v" will tell you, or you may need ohci, or maybe even the
alterna
Kent West wrote:
Jim Higson wrote:
Still having other problems though. See my last post.
Sorry, I've already deleted it, and I'm too lazy to search the archives.
Oh, maybe you mean "see my other post which shows up in Kent's mailbox
after this one because he's sorting by threads", in which cas
Jim Higson wrote:
The mouse is now sorted, so I don't think I need post this.
Do you mean your mouse is working as you want properly? If so, I suggest
you post the solution so others in the future who are searching for
answers to the same problem can find the solution.
Still having other prob
On Mon, 12 Jan 2004 17:27:36 -0500, Johann Koenig <[EMAIL PROTECTED]>
wrote:
On Monday January 12 at 10:21pm
Jim Higson <[EMAIL PROTECTED]> wrote:
On Mon, 12 Jan 2004 14:59:18 -0500, Johann Koenig
<[EMAIL PROTECTED]> wrote:
>> As you can see I'm directing x to "/dev/input/mice". How can I be
>> s
On Mon, 12 Jan 2004 16:34:48 -0600, Kent West <[EMAIL PROTECTED]> wrote:
Ah, yes; you have not usb support. Try running "modconf" and select such
things as usb/uhci (assuming you have uhci controllers - "lspci -v" will
tell you, or you may need ohci, or maybe even the alternative uhci
module -
On Monday January 12 at 10:21pm
Jim Higson <[EMAIL PROTECTED]> wrote:
> On Mon, 12 Jan 2004 14:59:18 -0500, Johann Koenig
> <[EMAIL PROTECTED]> wrote:
>
> >> As you can see I'm directing x to "/dev/input/mice". How can I be
> >> sure> my kernel is using /dev/input/mice for the usb mouse?
>
> >>>
Jim Higson wrote:
On Mon, 12 Jan 2004 13:55:39 -0600, Kent West <[EMAIL PROTECTED]> wrote:
Jim Higson wrote:
On Mon, 12 Jan 2004 13:46:01 -0500, Johann Koenig
<[EMAIL PROTECTED]> wrote:
On Monday January 12 at 06:26pm
Jim Higson <[EMAIL PROTECTED]> wrote:
As you can see I'm directing x to "/de
On Mon, 12 Jan 2004 14:59:18 -0500, Johann Koenig <[EMAIL PROTECTED]>
wrote:
As you can see I'm directing x to "/dev/input/mice". How can I be
sure> my kernel is using /dev/input/mice for the usb mouse?
As root: cat /dev/input/mice
move the mouse around, and see if anything shows up on the scree
On Mon, 12 Jan 2004 13:55:39 -0600, Kent West <[EMAIL PROTECTED]> wrote:
Jim Higson wrote:
On Mon, 12 Jan 2004 13:46:01 -0500, Johann Koenig
<[EMAIL PROTECTED]> wrote:
On Monday January 12 at 06:26pm
Jim Higson <[EMAIL PROTECTED]> wrote:
As you can see I'm directing x to "/dev/input/mice". How
On Monday January 12 at 07:42pm
Jim Higson <[EMAIL PROTECTED]> wrote:
> On Mon, 12 Jan 2004 13:46:01 -0500, Johann Koenig
> <[EMAIL PROTECTED]> wrote:
>
> > On Monday January 12 at 06:26pm
> > Jim Higson <[EMAIL PROTECTED]> wrote:
> >
> >> As you can see I'm directing x to "/dev/input/mice". How
Jim Higson wrote:
On Mon, 12 Jan 2004 13:46:01 -0500, Johann Koenig
<[EMAIL PROTECTED]> wrote:
On Monday January 12 at 06:26pm
Jim Higson <[EMAIL PROTECTED]> wrote:
As you can see I'm directing x to "/dev/input/mice". How can I be sure
my kernel is using /dev/input/mice for the usb mouse?
As r
On Mon, 12 Jan 2004 13:46:01 -0500, Johann Koenig <[EMAIL PROTECTED]>
wrote:
On Monday January 12 at 06:26pm
Jim Higson <[EMAIL PROTECTED]> wrote:
As you can see I'm directing x to "/dev/input/mice". How can I be sure
my kernel is using /dev/input/mice for the usb mouse?
As root: cat /dev/input/m
Jim Higson wrote:
I'm still having these problems, on my main machine, which has
resisted XFree from the start.
As sugested, I've updated the kernel to the prebuilt image 2.4.18-k7
from the woody isos and confirmed the update with uname. It still
won't recognise my usb mouse.
The mouse in ques
On Monday January 12 at 06:26pm
Jim Higson <[EMAIL PROTECTED]> wrote:
> As you can see I'm directing x to "/dev/input/mice". How can I be sure
> my kernel is using /dev/input/mice for the usb mouse?
As root: cat /dev/input/mice
move the mouse around, and see if anything shows up on the screen. If
I'm still having these problems, on my main machine, which has resisted
XFree from the start.
As sugested, I've updated the kernel to the prebuilt image 2.4.18-k7 from
the woody isos and confirmed the update with uname. It still won't
recognise my usb mouse.
The mouse in question is a logitech
On Fri, 09 Jan 2004 16:36:57 -0600, Kent West <[EMAIL PROTECTED]> wrote:
[snip, X not working, been advised to try a newer precompiled kernel]
Just one point...
http://users.aber.ac.uk/jqh1/x/XF86Config-4
This address is incorrect; remove the "/x".
Oops, sorry. Just to make sure people see the
Hello
Jim Higson (<[EMAIL PROTECTED]>) wrote:
> [XFree doesn't work under Woody]
> I've also read this http://www.mindwarp.net/debian-usb.php and to be
> honest I'm a bit worried if I have to recompile the kernel just to use
> a usb mouse! Is everything at this page really necessary?
>
> Logitec
Jim Higson wrote:
I installed debian GNU/Linux on one of my machines about a fortnight
ago from woody(r2) cds 1-3. I can't get any graphics despite much
tinkering.
At this stage I'm pretty sure it's the mouse that isn't working. But
don't take my word for it, check the link to the latest log
Hi.
I installed debian GNU/Linux on one of my machines about a fortnight ago
from woody(r2) cds 1-3. I can't get any graphics despite much tinkering.
My level of experiance: windows geek for a long time, but been using sun
unix at university really like KDE. So I'm moving one of my main boxes
On Mon, Oct 20, 2003 at 01:33:34AM -0400, [EMAIL PROTECTED] wrote:
> Actually, thanks to people on IRC, I fixed the problem.
>
> It was because of fontconfig bug 216605. The solution was to uninstall
> gsfonts-other, and rebuild the font cache (I used dpkg-reconfigure fontconfig).
>
> (And sorry
On Sun, Oct 19, 2003 at 10:58:01PM -0500, Kevin C. Smith wrote:
> Anyone else experience this, or is it just me?
See recent BTS entries for fontconfig.
--
Marc Wilson | Oh, yeah, life goes on, long after the thrill of
[EMAIL PROTECTED] | livin' is gone. -- John Cougar, "Jack and Diane
Actually, thanks to people on IRC, I fixed the problem.
It was because of fontconfig bug 216605. The solution was to uninstall
gsfonts-other, and rebuild the font cache (I used dpkg-reconfigure fontconfig).
(And sorry about the long lines -- I was using w3m to send that.)
david
--
To UNSUBSCR
I have the same problem, most likely. At first, it seemed like it was only gtk2/gnome2
apps that didn't work, as I could start xinit manually and run kdesktop, kwin, etc
from there. KDM did not work, however. When executing a gnome2 program from the
command line, the program would exit without a
I just upgraded by Sid box and now 99% of my X apps no longer work.
Such as: KDM fails to start.
I can start fluxbox but the majority of the X appls fail.
I have not seen any errors in the logs or from the output of various
applications.
Anyone else experience this, or is it just me?
Kevin
--
In a message dated 4/12/99 10:34:17 AM Central Daylight Time,
[EMAIL PROTECTED] writes:
> 'Xlib: connection to ":0.0" refused by server
> Xlib: Invalid MIT-VALID-COOKIE-1 key
> Can't connect to X server :0.0'
>
Check the list archives - this was answered just a few days ago..
Basically, you
Hi!
I'm having trouble starting some programs under X,
amongst them wine and uae. I've got a fully functional
X setup but for some programs it just doesn't work.
I'm using Ice WM.
This is the output X gives me:
'Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-VALID-COOKIE-1 key
C
34 matches
Mail list logo
