> * before today's update
> - 95% of "exit enlightenment" tries, I was welcomed by the e17 crash window.
> Don't know why. (this didn't happen again since the update (though I haven't
> use it enough yet))
get us some gdb backtraces! we need gdb info! and if that doesnt help -
valgrind! :)
Ok, I'll try to get you something you can work with.
> - I use a USB mouse. Works just fine. But when I need the usb port to other
> devices, I move the usb mouse to the PS2 port (using an adaptor). When I use
> it like this, the mouse behaves quite strangely. Jumps from one side to the
> other. Sometimes opens the menu and exits.
that's entirely out of e's domain. it doesn't read or touch a mouse driver. it
gets mouse events from x. x handles all the mouse driver/protocol stuff. this is
a matter of hw drivers, mouse protocols and mouse initialization - entirely out
of the domain of an x application. i repeat - it is NOT a bug or problem of e's.
it's entirely driver/xserver related.
As I said to Massimo, I cannot agree completely with you. I understand what you say and it's pretty logic. But I do use the same mouse on the same port and I have NO problem what-so-ever when running E16 and KDE. So, X handles it well in those cases and misbehaves when running E17? I might be wrong, but it seems something else...
I don't what to do to track the problem down, so that I could find the real reason, but I'll be glad to work it if someone bring me some light.. :)
Cheers,
Fernando
