Bug#362229: xserver-xorg-core: symlink does not fix
Package: xserver-xorg-core Version: 1:1.0.2-3 Followup-For: Bug #362229 I am also seeing XKB problems. The server logs this: (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap and xdm logs this: sh: /usr/bin/xkbcomp: No such file or directory Thu Apr 13 21:50:13 2006 xdm error (pid 29059): failed to open input method I tried creating the symlink, and restarting the server, but it's no good. (Note that xdm is looking in the wrong place for xkbcomp.) I notice that xbase-clients (source xorg-x11), which contains xkbcomp and setxkbmap, is still at 6.9.0. Is the xorg-x11 source package going to be updated, or is it to be phased out somehow? This causes me some rather serious problems - besides my "ctrl:nocaps" not being honored, I am entirely unable to switch TTYs (I get some odd output when I type Ctrl-Alt-F1 instead, even though xev shows normal events). -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg-core depends on: ii libc62.3.6-6 GNU C Library: Shared libraries ii libfontenc1 1:1.0.1-2 X11 font encoding library ii libxau6 1:1.0.0-2 X11 authorisation library ii libxdmcp61:1.0.0-3 X11 Display Manager Control Protoc ii libxfont11:1.0.0-3 X11 font rasterisation library ii x11-common 1:7.0.10X Window System (X.Org) infrastruc ii xserver-xorg-input-all 1:7.0.10the X.Org X server -- input driver ii xserver-xorg-input-evdev [xs 1:1.0.0.5-2 X.Org X server -- evdev input driv ii xserver-xorg-input-kbd [xser 1:1.0.1.3-2 X.Org X server -- keyboard input d ii xserver-xorg-input-mouse [xs 1:1.0.4-2 X.Org X server -- mouse input driv ii xserver-xorg-video-ati [xser 1:6.5.7.3-3 X.Org X server -- ATI display driv ii zlib1g 1:1.2.3-11 compression library - runtime Versions of packages xserver-xorg-core recommends: pn xkeyboard-config (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#365948: x11-common: broken depends on compat package xfree86-common
Package: x11-common Version: 1:7.0.16 Severity: grave Justification: renders package unusable Version 7.0.16 of x11-common depends on xfree86-common, which is a "useless" compatibility package. Making things worse is that xfree86-common conflicts with x11-common. This prevents x11-common from being installed at all. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.5.0 Debian configuration management sy ii debianutils 2.16 Miscellaneous utilities specific t ii lsb-base 3.1-5 Linux Standard Base 3.1 init scrip x11-common recommends no packages. -- debconf information: * x11-common/xwrapper/nice_value: 0 * x11-common/xwrapper/allowed_users: Anybody x11-common/experimental_packages: x11-common/xwrapper/actual_allowed_users: anybody x11-common/xwrapper/nice_value/error: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#365948: x11-common: broken depends on compat package xfree86-common
I screwed this up. It installs fine if I do it right. smime.p7s Description: S/MIME Cryptographic Signature
Bug#365948: x11-common: broken depends on compat package xfree86-common
Steve Langasek wrote: On Wed, May 03, 2006 at 06:35:56PM -0400, Ray Kohler wrote: Package: x11-common Version: 1:7.0.16 Severity: grave Justification: renders package unusable Version 7.0.16 of x11-common depends on xfree86-common, which is a "useless" compatibility package. Making things worse is that xfree86-common conflicts with x11-common. This prevents x11-common from being installed at all. I screwed this up. It installs fine if I do it right. So your assessment is that there's no bug here? What way did you do it first that was "wrong", btw? Right, I don't think there's really a bug here. What I did wrong, was to try to install them "by hand" with dpkg, and not to notice that I was dealing with a Pre-Depends rather than an ordinary Depends. In any case, I can't reproduce it at all installing it with apt-get. smime.p7s Description: S/MIME Cryptographic Signature
