Hi,
Michal Semler (22/12/2007):
> > Still the same problem with latest xserver-xorg-core and driver sfrom
> > unstable? If not, can you catch a backtrace with gdb?
>
> I just tested latest Xorg in testing and git version of the driver,
> and it is still there. I also opened call with freedeskto
Brice Goglin writes:
tags 423090 +moreinfo
thank you
On Sat, May 12, 2007 at 09:54:28AM +0200, Brice Goglin wrote:
We need a nice backtrace of the crash (when evdev is used for the
keyboard). Could you install xserver-xorg-core-dbg and rebuild the evdev
driver with debugging enabled (you mi
tags 423090 +moreinfo
thank you
On Sat, May 12, 2007 at 09:54:28AM +0200, Brice Goglin wrote:
> We need a nice backtrace of the crash (when evdev is used for the
> keyboard). Could you install xserver-xorg-core-dbg and rebuild the evdev
> driver with debugging enabled (you might want to look at
>
We need a nice backtrace of the crash (when evdev is used for the
keyboard). Could you install xserver-xorg-core-dbg and rebuild the evdev
driver with debugging enabled (you might want to look at
http://wiki.debian.org/HowToGetABacktrace to do so, and replace "hello"
with "xserver-xorg-input-evdev"
Dne pátek 11 květen 2007 03:25 Brice Goglin napsal(a):
> severity 423090 important
> thank you
>
>
> Please don't use very very high severity without a good reason. Obviously,
> a crash of the X server does not break the whole system. A crash of the X
> server is generally considered "important".
>
severity 423090 important
thank you
Please don't use very very high severity without a good reason. Obviously,
a crash of the X server does not break the whole system. A crash of the X
server is generally considered "important".
See http://www.debian.org/Bugs/Developer#severities
> When selecti
6 matches
Mail list logo
