public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fernando Meira <fmeira@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] enlightenment 16 or 17
Date: Thu, 4 Aug 2005 18:26:18 +0000	[thread overview]
Message-ID: <a3c2e88b0508041126480d4fa0@mail.gmail.com> (raw)
In-Reply-To: <1123178617.8815.45.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]

Thanks anyway Luke!

This looks like a crazy mouse behaviour... suddenly jumps to another place 
and open the menu. 
I think E17 never crashed (as I said before), but, in fact, what happen (at 
least the last time) was that when the pointer jumped away, opened the menu 
and (because I was trying to move the mouse, looking for it, or always 
happens this) selected the "exit enlightenment" option. I already logged out 
3 times without being my intention. 
Everything else seems to be going ok, just this mouse is causing a mess in 
here... quite hard to do anything...

The mouse is connected to the PS2, and xorg.conf has:
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/input/mouse0"
Option "ZAxisMapping" "4 5"
EndSection

Cheers,
Fernando
On 8/4/05, Luke Albers <gtg940r@mail.gatech.edu> wrote:
> 
> On Thu, 2005-08-04 at 17:53 +0000, Fernando Meira wrote:
> > Ok, thanks Christoph.
> 
> > So, from these, does it look like a bug, mouse bad-config or something
> > else?
> 
> 
> I doubt its a big, since I haven't had this happen. I have had e17
> crash a few times, but not as often as it sounds like yours is.
> 
> Sorry I can't help more than that.
> 
> --
> gentoo-user@gentoo.org mailing list
> 
>

[-- Attachment #2: Type: text/html, Size: 2139 bytes --]

  reply	other threads:[~2005-08-04 18:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 12:45 [gentoo-user] enlightenment 16 or 17 Fernando Meira
2005-08-03 13:11 ` Luke Albers
2005-08-03 13:20 ` fire-eyes
2005-08-03 15:23   ` Luke Albers
2005-08-03 15:59     ` Christoph Gysin
2005-08-03 16:10       ` Luke Albers
2005-08-03 16:56         ` Fernando Meira
2005-08-03 17:31           ` Luke Albers
2005-08-03 16:51       ` Fernando Meira
2005-08-03 16:51         ` Fernando Meira
2005-08-03 17:33         ` Luke Albers
2005-08-04  8:57         ` Christoph Gysin
2005-08-03 17:28       ` Fernando Meira
2005-08-03 17:28         ` Fernando Meira
2005-08-03 18:33         ` Luke Albers
2005-08-03 18:55           ` Fernando Meira
2005-08-03 19:04             ` Luke Albers
2005-08-03 19:57               ` Fernando Meira
2005-08-03 22:37                 ` Justin Patrin
2005-08-04  8:08                   ` Fernando Meira
2005-08-04  9:16                     ` Christoph Gysin
2005-08-04 17:53                       ` Fernando Meira
2005-08-04 18:03                         ` Luke Albers
2005-08-04 18:26                           ` Fernando Meira [this message]
2005-08-04 18:36                             ` Luke Albers
2005-08-04 20:10                               ` Fernando Meira
2005-08-05 17:42                                 ` Fernando Meira
2005-08-05 18:03                                   ` Luke Albers
2005-08-07 23:23                                   ` Christoph Gysin
2005-08-04  9:00         ` Christoph Gysin
2005-08-03 13:58 ` Christoph Gysin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a3c2e88b0508041126480d4fa0@mail.gmail.com \
    --to=fmeira@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox