Your message dated Sat, 12 Sep 2009 12:34:07 +0300
with message-id <ba4a6e220909120234t292046c9w7ab1bec9b555e...@mail.gmail.com>
and subject line Re: Bug#546262: kdm crash (due to a bug in libx11-6 o xserver
in unstable?)
has caused the Debian Bug report #546262,
regarding kdm crash (due to a bug in libx11-6 o xserver in unstable?)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
546262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: kdm crash (due to a bug in libx11-6 o xserver in unstable?)
Package: kdm
Version: 4:3.5.9.dfsg.1-6
Severity: grave
Justification: renders package unusable
I want to report a bug that makes kdm crash, though I believe that the bug
is not caused by kdm itself but probably by the xserver in unstable (that
have changed the way of handling input devices, in particular the keyboard).
[with the xserver-xorg in lenny (version 1.7.20) things work fine, with
the version in unstable (1.7.4+4) kdm crashes.
Here is the back trace generated by kcrash: as you can see the segfault
occurs in src/xkb/XKBBind.c (line 320) from libx11:
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ca6700 (LWP 1054)]
[KCrash handler]
#5 XkbTranslateKeyCode (xkb=0x99cbc30, key=<value optimized out>, mods=0,
mods_rtrn=0xbfe6b7c4, keysym_rtrn=0xbfe6b874)
at ../../../src/xkb/XKBBind.c:320
#6 0xb701570b in XkbLookupKeySym (dpy=0x9979720, key=<value optimized out>,
mods=0, mods_rtrn=0xbfe6b7c4, keysym_rtrn=0xbfe6b874)
at ../../../src/xkb/XKBBind.c:262
#7 0xb7015813 in XLookupString (event=0xbfe6b828, buffer=0x9a587d8 "",
nbytes=513, keysym=0xbfe6b874, status=0x0)
at ../../../src/xkb/XKBBind.c:668
#8 0xb726d392 in QETWidget::translateKeyEventInternal (this=0x9a10148,
event=0xbfe6bde8, cou...@0xbfe6bb2c, te...@0xbfe6bb20, sta...@0xbfe6bb28,
asc...@0xbfe6bb37, co...@0xbfe6bb30, ty...@0xbfe6bb24, willRepeat=false,
statefulTranslation=true) at kernel/qapplication_x11.cpp:5202
#9 0xb726dc08 in QETWidget::translateKeyEvent (this=0x9a10148,
event=0xbfe6bde8, grab=false) at kernel/qapplication_x11.cpp:5506
#10 0xb7275821 in QApplication::x11ProcessEvent (this=0xbfe6bf00,
event=0xbfe6bde8) at kernel/qapplication_x11.cpp:3539
#11 0xb7289e2c in QEventLoop::processEvents (this=0x9998868,
flags=<value optimized out>) at kernel/qeventloop_x11.cpp:195
#12 0xb72f81a0 in QEventLoop::enterLoop (this=0x9998868)
at kernel/qeventloop.cpp:201
#13 0xb72dfdcf in QApplication::enter_loop (this=0xbfe6bf00)
at kernel/qapplication.cpp:2796
#14 0xb74d715d in QDialog::exec (this=0x99a5178) at dialogs/qdialog.cpp:435
#15 0x08060c87 in FDialog::exec (this=0x99a5178)
at /tmp/buildd/kdebase-3.5.9.dfsg.1/./kdm/kfrontend/kfdialog.cpp:118
#16 0x0807b2a1 in kg_main (argv0=0xbfe6cf29 "/usr/bin/kdm_greet")
at /tmp/buildd/kdebase-3.5.9.dfsg.1/./kdm/kfrontend/kgapp.cpp:223
#17 0x0805d11d in main (argc=1735287144, argv=0xbfe6c154)
at /tmp/buildd/kdebase-3.5.9.dfsg.1/./kdm/kfrontend/kdm_greet.c:784
I'm using a serial mouse, thefore I'm using the xserver-xorg-input-mouse
(version 1:1.0.4-4) and xserver-xorg-input-kbd (version 1:1.3.2-4) drivers
(and not evdev). Here is my xorg.conf file:
# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
# Esto desactiva el uso de HAL y hace que la configuración
# de xorg.conf funcione
Option "AutoAddDevices" "Off"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection
Section "Module"
Load "extmod"
Load "record"
Load "GLcore"
Load "dbe"
Load "dri"
Load "glx"
Load "xtrap"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
#Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "es"
Option "XkbOptions" "lv3:ralt_switch"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
#Option "CorePointer"
Option "Device" "/dev/ttyS0"
Option "Protocol" "IntelliMouse"
Option "ZAxisMapping" "4 5"
Option "Buttons" "3"
Option "Emulate3Buttons" "no"
EndSection
Section "Device"
Identifier "S3 Inc. ProSavage KM133"
Driver "savage"
BusID "PCI:1:0:0"
EndSection
Section "Monitor"
Identifier "105E"
Option "DPMS"
EndSection
Section "Screen"
Identifier "Screen0"
Device "S3 Inc. ProSavage KM133"
Monitor "105E"
DefaultDepth 16
SubSection "Display"
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'),
(1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.31
Locale: LANG=es_AR, LC_CTYPE=es_AR (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages kdm depends on:
ii debconf [debconf 1.5.24 Debian configuration management sy
ii kdebase-bin 4:3.5.9.dfsg.1-6 core binaries for the KDE base mod
ii kdebase-data 4:3.5.9.dfsg.1-6 shared data files for the KDE base
ii kdelibs4c2a 4:3.5.10.dfsg.1-0lenny2 core libraries and binaries for al
ii libc6 2.9-26 GNU C Library: Shared libraries
ii libdbus-1-3 1.2.16-2 simple interprocess messaging syst
ii libgcc1 1:4.3.2-1.1 GCC support library
ii libpam-runtime 1.0.1-5+lenny1 Runtime support for the PAM librar
ii libpam0g 1.0.1-5+lenny1 Pluggable Authentication Modules l
ii libqt3-mt 3:3.3.8b-5+b1 Qt GUI Library (Threaded runtime v
ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3
ii libx11-6 2:1.2.2-1 X11 client-side library
ii libxau6 1:1.0.4-2 X11 authorisation library
ii libxdmcp6 1:1.0.2-3 X11 Display Manager Control Protoc
ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension
Versions of packages kdm recommends:
ii logrotate 3.7.1-5 Log rotation utility
ii xserver-xorg 1:7.4+4 the X.Org X server
Versions of packages kdm suggests:
ii kdepasswd 4:3.5.9.dfsg.1-6 password changer for KDE
ii khelpcente 4:4.0.0.really.3.5.9.dfsg.1-6 help center for KDE
ii ksmserver 4:3.5.9.dfsg.1-6 session manager for KDE
pn menu <none> (no description available)
-- debconf information:
kdm/stop_running_server_with_children: false
* shared/default-x-display-manager: kdm
kdm/daemon_name: /usr/bin/kdm
--- End Message ---
--- Begin Message ---
2009/9/12 Pablo De Napoli <pden...@gmail.com>:
> I want to report a bug that makes kdm crash, though I believe that the bug
> is not caused by kdm itself but probably by the xserver in unstable (that
> have changed the way of handling input devices, in particular the keyboard).
> [with the xserver-xorg in lenny (version 1.7.20) things work fine, with
> the version in unstable (1.7.4+4) kdm crashes.
Hi,
You are using an unsupported combination of packages (KDE 3 from lenny
and X 7.4 from unstable). KDE 3 is dead upstream and it is not going
to be fixed to support newer versions of libraries and other
components of the system, such as X. Since kdm from lenny works fine
with X from lenny, this is not a bug that concerns us. To solve this
problem, either downgrade X to the version from lenny or upgrade to
KDE 4. If the problem persists with KDE 4.3.1 that is now available in
testing and unstable, please reopen this bug.
Thank you,
George
--- End Message ---
