Re: after upgrade to squeeze keyboard does no longer work with X (solved)
Hi, >>> after an upgrade to squeeze I have the problem that my keyboard is no >>> longer recognized by X (the mouse works). If I kill gdm/kdm from >>> another >>> machine via ssh, I get a console where the keyboard works. Xorg.0.log >>> does not show any errors (and the keyboard is mentioned there). >>> >>> It does not matter whether the keyboard is connected via USB or PS/2. >>> Removing my xorg.conf (to use the defaults/autodetection) does not >>> help >>> either. >>> >>> Any ideas how to debug the problem? > >> Upload "/var/log/Xorg.0.log", "/etc/X11/xorg.conf" (if any) and "/etc/ >> defaults/keyboard" to www.pastebin.com > > /etc/X11/xorg.conf is empty (well, actually I want to add something > there, but that's not relevant for this bug, see below). > > /etc/default/keyboard contains > > XKBMODEL="pc105" > # XKBLAYOUT="us" > XKBLAYOUT="de" > XKBVARIANT="nodeadkeys" > XKBOPTIONS="" > > Xorg.0.log for "de" layout is at http://pastebin.com/1L0yTgEx and for > "us" layout at http://pastebin.com/XtjcCMiW. For "de" layout it works, > but not for "us" layout. > > The only problem is, I have a "us" layout keyboard! With the "de" > keyboard some keys are obviously wrong, but at least I am able to input > something at all. I found the problem. A few years ago I had a "de" keyboard. When I switched to an "us" keyboard I changed the layout, but forgot about the "nodeadkeys" variant. X in lenny simply ignored the wrong variant. But X in squeeze silently fails. The model is wrong too (should be "pc104" for a "us" layout), but that does not seem to a problem. I'll leave a comment in bug 571636. Ironically, the "nodeadkeys" had exactly the opposite effect, it rendered *all* keys dead ;-) Joachim -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cf6b450.1030...@gmx.de
Re: Re: after upgrade to squeeze keyboard does no longer work with X
Hi, >> after an upgrade to squeeze I have the problem that my keyboard is no >> longer recognized by X (the mouse works). If I kill gdm/kdm from >> another >> machine via ssh, I get a console where the keyboard works. Xorg.0.log >> does not show any errors (and the keyboard is mentioned there). >> >> It does not matter whether the keyboard is connected via USB or PS/2. >> Removing my xorg.conf (to use the defaults/autodetection) does not >> help >> either. >> >> Any ideas how to debug the problem? > Upload "/var/log/Xorg.0.log", "/etc/X11/xorg.conf" (if any) and "/etc/ > defaults/keyboard" to www.pastebin.com /etc/X11/xorg.conf is empty (well, actually I want to add something there, but that's not relevant for this bug, see below). /etc/default/keyboard contains XKBMODEL="pc105" # XKBLAYOUT="us" XKBLAYOUT="de" XKBVARIANT="nodeadkeys" XKBOPTIONS="" Xorg.0.log for "de" layout is at http://pastebin.com/1L0yTgEx and for "us" layout at http://pastebin.com/XtjcCMiW. For "de" layout it works, but not for "us" layout. The only problem is, I have a "us" layout keyboard! With the "de" keyboard some keys are obviously wrong, but at least I am able to input something at all. Comparing both log files (ignoring "de" vs. "us" and different /dev/input/eventX numbers for power buttons and PC speaker) I only see that the log for the "de" layout has at the end (II) Power Button: Close (II) UnloadModule: "evdev" (II) Power Button: Close (II) UnloadModule: "evdev" (II) HID 046a:0011: Close (II) UnloadModule: "evdev" (II) Logitech USB-PS/2 Optical Mouse: Close (II) UnloadModule: "evdev" (II) Macintosh mouse button emulation: Close (II) UnloadModule: "evdev" (II) i2c IR (HVR 1110): Close (II) UnloadModule: "evdev" which is not the case for the failing "us" layout. I guess that's because for the "de" layout I properly shut down X, which I didn't do for the failing "us" layout. Note that I always rebooted between changes to /etc/default/keyboard. I also checked that /usr/share/X11/xkb/symbols/us exists and it looks good. > Have you tried to create a new user account and test from there? No, I don't think that would help (I can't even enter a user name in the kdm/gdm login window). Joachim -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cf6ad8a.40...@gmx.de
after upgrade to squeeze keyboard does no longer work with X
Hi, after an upgrade to squeeze I have the problem that my keyboard is no longer recognized by X (the mouse works). If I kill gdm/kdm from another machine via ssh, I get a console where the keyboard works. Xorg.0.log does not show any errors (and the keyboard is mentioned there). It does not matter whether the keyboard is connected via USB or PS/2. Removing my xorg.conf (to use the defaults/autodetection) does not help either. Any ideas how to debug the problem? Thanks, Joachim -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cf2a3c1.9050...@gmx.de
Re: mp3 player with adjustable speed and pitch correction
Michael Shuler worte: > What you are looking for is really not just a player, but an audio editor. > Give audacity a try - works well for me. >From a user's point of view there is no difference between adjusting volume, speed or pitch. Hence, I consider adjustable speed as a basic feature of a music player. Anyway, audacity doesn't suit my needs (stop playback, preprocessing). Andrei Popescu wrote: > mplayer can adjust the speed on-the-fly. A quick search through the man > page does find a filter which compensates for the pitch as well, but I > didn't test it. Unfortunately, (g)mplayer does not display the current speed (imagine that you press [ or ] several times during playback), 10% steps are too large, also. Cédric Lucantis wrote: > alsaplayer does it too, even allowing negative speeds for your satanic > parties :) alsaplayer is fine. Thanks for all suggestions. Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
mp3 player with adjustable speed and pitch correction
Hi, I'm looking for an mp3 player that allows to adjust the speed, but haven't been successful so far. audacity: requires preprocessing (and is not really a music player) amarok: the developers tagged #103895 as wontfix vlc: allows only fixed multipliers (like 0.5x/1x/2x) noatun: restarts song from beginning on every change Is there any music player that allows to adjust the speed by any factor between half and double speed, at any point during playback, without preprocessing, without restarting playback from beginning, and with pitch correction? Joachim P.S.: Please CC: me on replies. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Who is altering my hostname?
Hi,
> Is is possible that this change of hostnames is somehow enfored by the
> virtualization? (Virtuozzo)
Yes, Virtuozzo is known to do such things. I use the attached script in
/etc/init.d with appropriate links in /etc/rc*.d (run the script very
early in the boot process).
Regards,
Joachim
#!/bin/sh
. /lib/init/vars.sh
. /lib/lsb/init-functions
case "$1" in
start)
[ "$VERBOSE" != no ] && log_action_begin_msg "local workarounds"
if [ -f /etc/hostname.real ]; then
cp -a /etc/hostname.real /etc/hostname
hostname `cat /etc/hostname`
uname -snrvm > /var/run/motd
[ -f /etc/motd.tail ] && cat /etc/motd.tail >>
/var/run/motd
fi
[ "$VERBOSE" != no ] && log_action_end_msg 0
;;
stop)
[ "$VERBOSE" != no ] && log_action_begin_msg "local workarounds"
cp -a /etc/hostname /etc/hostname.real
[ "$VERBOSE" != no ] && log_action_end_msg 0
;;
restart|force-reload)
;;
*)
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
exit 3
;;
esac
Re: Re: problems with / on LVM/RAID1
> > Using mkinitramfs-kpkg to build the ramdisk.
> > I: mdadm: RAID support installed to mount all RAID arrays during boot.
> > I: mdadm: use `dpkg-reconfigure -plow mdadm` to change this.
> Don't you need to bring up raid and lvm in the initramfs rather than
> in the boot sequence?
Yes, sure. The message just says that the raid support is included in
the initial ramdisk ("during boot" might be misleading ...).
Meanwhile I found out that everything is fine if I compile 2.6.16-18
myself. On the other, the same errors occurs with a self-compiled
2.6.17-8. (I just copied the config file from the linux-image package.)
So it works with 2.6.16 but not with 2.6.17. Should I file a bug on
linux-source or initramfs-tools?
Regards,
Joachim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
problems with / on LVM/RAID1
Hi, I'm having some problems with / on LVM/RAID1. The situations is as follows: /dev/sda1 ext3 /boot /dev/sda3 and /dev/sdb3 are used for /dev/md0 (raid1) /dev/md0 is a single PV for a VG "raid" this volume group contains three LVs, one of them being /dev/mapper/raid-slash with ext3 mounted on / This layout was created with the Etch beta 3 installer, and the installation worked fine. The kernel is linux-image-2.6.17-2-amd64-generic 2.6.16-17. Now I want to run linux-image-2.6.17-2-amd64 2.6.17-8. However, the raid device is not started, no LV are available and / cannot be mounted. The exact error message is: Begin: Mounting root file system... ... Begin: Running /scripts/local-top ... mdadm: No devices listed in partitions device-mapper: 4.6.0-ioctl (2006-02-17) initialised: [EMAIL PROTECTED] Volume group "raid" not found Done. Begin: Waiting for root file system... ... This does not happen for the old kernel. mdadm is configured to bring up all raid devices early in the boot sequence. When I install the new kernel package, there is the following message: Using mkinitramfs-kpkg to build the ramdisk. I: mdadm: RAID support installed to mount all RAID arrays during boot. I: mdadm: use `dpkg-reconfigure -plow mdadm` to change this. So, everything should be fine. And I use /dev/mapper/X-Y, not /dev/X/Y (see #378332). I have no idea what's going wrong. I compared the two initrd's: Only in 2.6.17-2/etc/modprobe.d: nvidia-kernel-nkc Only in 2.6.17-2/etc/udev: libnjb.rules Only in 2.6.17-2/etc/udev: logitechmouse.rules Only in 2.6.17-2/etc/udev/rules.d: 025_logitechmouse.rules Only in 2.6.17-2/etc/udev/rules.d: libnjb.rules Only in 2.6.17-2/etc/udev/rules.d: z60_xserver-xorg-input-wacom.rules Only in 2.6.17-2/etc/udev: xserver-xorg-input-wacom.rules Binary files 2.6.16-2/lib/libc.so.6 and 2.6.17-2/lib/libc.so.6 differ Binary files 2.6.16-2/lib/libcrypt.so.1 and 2.6.17-2/lib/libcrypt.so.1 differ Binary files 2.6.16-2/lib/libdevmapper.so.1.02 and 2.6.17-2/lib/libdevmapper.so.1.02 differ Binary files 2.6.16-2/lib/libdl.so.2 and 2.6.17-2/lib/libdl.so.2 differ Binary files 2.6.16-2/lib/libm.so.6 and 2.6.17-2/lib/libm.so.6 differ Binary files 2.6.16-2/lib/libselinux.so.1 and 2.6.17-2/lib/libselinux.so.1 differ Binary files 2.6.16-2/lib/libsepol.so.1 and 2.6.17-2/lib/libsepol.so.1 differ Only in 2.6.16-2/lib/modules: 2.6.16-2-amd64-generic Only in 2.6.17-2/lib/modules: 2.6.17-2-amd64 Binary files 2.6.16-2/lib64/ld-linux-x86-64.so.2 and 2.6.17-2/lib64/ld-linux-x86-64.so.2 differ Of course, some binary files differ, but no obvious changes in the configuration files that could be responsible for the problem. Google shows only one hit for "mdadm: No devices listed in partitions" ... Thanks for any hints, Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
mouse wheel doesn't work any longer
Hi, I recently upgraded my Thinkpad A30p and now the mouse wheel doesn't work any longer. It has a built-in "mouse" (more a pen/trackball, no wheel) and a external USB mouse with mouse wheel. "cat /dev/input/mice | hexdump" does not show any events for the mouse wheel, same for /dev/psaux and /dev/gpmdata. Before the pgrade, "grep -i 'usb\|mouse' /var/log/messages" reported Jun 1 09:39:32 mpino1203 kernel: usb 2-1: USB disconnect, address 3 Jun 1 09:39:36 mpino1203 kernel: usb 2-1: new low speed USB device using address 4 Jun 1 09:39:36 mpino1203 kernel: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.1-1 Jun 1 09:39:36 mpino1203 usb.agent[26820]: usbhid: already loaded Jun 1 09:39:37 mpino1203 input.agent[26875]: mousedev: already loaded Jun 1 09:39:37 mpino1203 usb.agent[26820]: usbmouse: blacklisted but now I just have Jun 5 16:18:03 mpino1203 kernel: input: PS/2 Generic Mouse on isa0060/serio1 Jun 5 16:18:03 mpino1203 input.agent[1470]: mousedev: loaded successfully Jun 5 16:18:03 mpino1203 kernel: mice: PS/2 mouse device common for all mice "lsmod | grep 'usb\|mouse'" reports mousedev 10476 1 psmouse20360 0 Note that usbhid is not loaded, but loading doesn't solve the problem. I don't have any clue how to track this down. Any ideas? Regards, Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Ugly (xemacs) font
Hi, Another idea is to put the 100dpi and 75dpi unscaled fonts near the beginning of the font path. Uuups, I misread your message. After moving 100dpi and 75dpi to the front, it worked! After some searching I fount that the font in question was from the ttf-arphic-bsmi00lp package. Simply removing the package did not help, since now I had another TTF font in xemacs (much better readable, but still not what I want). But it works if 100dpi and 75dpi are the first entries. Thanks to all for their help, Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Ugly (xemacs) font
Hi, Another idea is to put the 100dpi and 75dpi unscaled fonts near the beginning of the font path. That did not help. The font you're seeing looks like some fancy font that tries to be cute. Hm. So perhaps try to find the font and remove it from your system ;-) I looked through all font families with xfontsel, but couldn't spot the font in question. Is there a better way to do this? Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Ugly (xemacs) font
Hi, catalogue = /var/lib/defoma/x-ttcidfont-conf.d/dirs/CID, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, /usr/lib/X11/fonts/TrueType/, /usr/lib/X11/fonts/misc/:unscaled, /usr/lib/X11/fonts/75dpi/:unscaled, /usr/lib/X11/fonts/100dpi/:unscaled, /usr/lib/X11/fonts/cyrillic/:unscaled, /usr/lib/X11/fonts/Speedo/, /usr/lib/X11/fonts/misc/, /usr/lib/X11/fonts/75dpi/, /usr/lib/X11/fonts/100dpi/, /usr/lib/X11/fonts/cyrillic/, /usr/lib/X11/fonts/Type1/ This does not look like an entry in /etc/X11/XF86Config. No, it is from xfs-xtt's config file. Anyway, I have the same order of directories in XF86Config, after 'FontPath "unix/:7110"'. Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Ugly (xemacs) font
Hi, the menu font in my xemacs is really ugly (I've uploaded a screenshot to http://www.joachim-reichel.de/tmp/xemacs.png). I know how to set the fonts for the editor window, but not for the menu. I do not notice font problems in other applications (KDE, Gnome, Mozilla, ...). But xfontsel shows the same ugly font as default. I don't care about xfontsel, but it seems that the problem is not xemacs-related. X packages: 4.3.0.dfsg.1-1 xfs-xtt:1.4.1.xf430-5 I don't know how to change the menu font directly (at least I don't remember) but IIRC a workaround is to change the order of the fonts paths in XF86Config since they are search in order until an appropriate font is found. You should make sure TrueType fonts are on top if they are available and Type1 fonts are last as they don't render to well to screen. That is already the case, here is my search order: catalogue = /var/lib/defoma/x-ttcidfont-conf.d/dirs/CID, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, /usr/lib/X11/fonts/TrueType/, /usr/lib/X11/fonts/misc/:unscaled, /usr/lib/X11/fonts/75dpi/:unscaled, /usr/lib/X11/fonts/100dpi/:unscaled, /usr/lib/X11/fonts/cyrillic/:unscaled, /usr/lib/X11/fonts/Speedo/, /usr/lib/X11/fonts/misc/, /usr/lib/X11/fonts/75dpi/, /usr/lib/X11/fonts/100dpi/, /usr/lib/X11/fonts/cyrillic/, /usr/lib/X11/fonts/Type1/ Changing the order does not seem to help (at least it doesn't improve things). On a different machine with almost identical setup, the fonts are fine (same search order). The following packages with 'font' in their name are installed: fontconfig 2.2.2-1 fonty1.0-15 freefont 0.10-11 gsfonts 6.0-2 gsfonts-x11 0.16 libfontconfig1 2.2.2-1 libfontconfig1-dev 2.2.2-1 msttcorefonts1.0.2 psfontmgr0.11.0 x-ttcidfont-conf 13 xfonts-100dpi4.3.0.dfsg.1-1 xfonts-100dpi-transcoded 4.3.0.dfsg.1-1 xfonts-75dpi 4.3.0.dfsg.1-1 xfonts-75dpi-transcoded 4.3.0.dfsg.1-1 xfonts-base 4.3.0.dfsg.1-1 xfonts-base-transcoded 4.3.0.dfsg.1-1 xfonts-cyrillic 4.3.0.dfsg.1-1 xfonts-scalable 4.3.0.dfsg.1-1 Regards, Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Ugly (xemacs) font
Hi, the menu font in my xemacs is really ugly (I've uploaded a screenshot to http://www.joachim-reichel.de/tmp/xemacs.png). I know how to set the fonts for the editor window, but not for the menu. I do not notice font problems in other applications (KDE, Gnome, Mozilla, ...). But xfontsel shows the same ugly font as default. I don't care about xfontsel, but it seems that the problem is not xemacs-related. X packages: 4.3.0.dfsg.1-1 xfs-xtt:1.4.1.xf430-5 I don't know where to start searching. The problem persists for some time now, so I don't know what change lead to it. Any ideas? Thanks in advance, Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gcc-3.3: two version strings 1:3.3.3ds5-1 and 1:3.3.3-1
Hi, the version 1:3.3.3ds5-1 is used in the changelog and in the name of the tarball and diff, whereas 1:3.3.3-1 is the version displayed by apt-get. Where does this discrepancy come from and why? Regards, Joachim -- "[...] Do not ask what your country can do for you, ask what you can do for your country." (John F. Kennedy) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
