Bug#539154: I can reproduce this - Please reopen
Hi, I seem to have the same problem on my system. I have copy-pasted all information I think relevant (sorry, long paste), and I also have some time to tinker with it if necessary. Thanks, -kurt -- mdadm --version --- Nasqueron:/home/oberon# mdadm --version mdadm - v3.1.1 - 19th November 2009 Nasqueron:/home/oberon# -- daemon.log --- Nasqueron:/home/oberon# grep md /var/log/daemon.log Mar 22 20:51:02 Nasqueron mdadm[3204]: DegradedArray event detected on md device /dev/md3 Mar 22 20:51:02 Nasqueron mdadm[3204]: NewArray event detected on md device /dev/md1 Mar 22 20:51:02 Nasqueron mdadm[3204]: NewArray event detected on md device /dev/md1 Mar 22 20:51:03 Nasqueron mdadm[3204]: NewArray event detected on md device /dev/md1 Mar 22 20:51:07 Nasqueron mdadm[3204]: NewArray event detected on md device /dev/md1 Mar 22 20:52:43 Nasqueron mdadm[3204]: NewArray event detected on md device /dev/md1 Mar 22 20:52:51 Nasqueron mdadm[3204]: NewArray event detected on md device /dev/md1 Mar 22 20:55:39 Nasqueron mdadm[3204]: NewArray event detected on md device /dev/md1 Mar 22 21:00:39 Nasqueron mdadm[3204]: NewArray event detected on md device /dev/md1 Mar 22 21:00:40 Nasqueron mdadm[3204]: NewArray event detected on md device /dev/md1 Mar 22 21:05:40 Nasqueron mdadm[3204]: NewArray event detected on md device /dev/md1 Mar 23 06:31:17 Nasqueron mdadm[12306]: DegradedArray event detected on md device /dev/md3 Mar 23 06:31:17 Nasqueron mdadm[12306]: NewArray event detected on md device /dev/md1 Mar 23 06:31:25 Nasqueron mdadm[12306]: NewArray event detected on md device /dev/md1 Mar 23 06:31:37 Nasqueron mdadm[12306]: NewArray event detected on md device /dev/md1 Mar 23 06:33:03 Nasqueron mdadm[16824]: DegradedArray event detected on md device /dev/md3 Mar 23 06:33:03 Nasqueron mdadm[16824]: NewArray event detected on md -- mdstat --- Nasqueron:/home/oberon# cat /proc/mdstat Personalities : [raid0] [raid1] md2 : active raid1 sdb1[0] sdd1[1] 488386432 blocks [2/2] [UU] md3 : active (auto-read-only) raid1 sdc7[1] 1951744 blocks [2/1] [_U] md1 : inactive sdc6[1] 85939584 blocks md0 : active raid1 sda1[0] sdc5[1] 29294400 blocks [2/2] [UU] unused devices: none -- mdadm --detail --- Nasqueron:/home/oberon# mdadm --detail /dev/md1 /dev/md1: Version : 0.90 Creation Time : Thu Sep 25 01:10:51 2008 Raid Level : raid0 Raid Devices : 2 Total Devices : 1 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Tue May 12 21:50:23 2009 State : active, degraded, Not Started Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Chunk Size : 64K UUID : 12a57a1a:bb75e74a:e6dc959d:b20685c9 (local to host Nasqueron.wattstrasse.ch) Events : 0.13 Number Major Minor RaidDevice State 0 000 removed 1 8 381 active sync /dev/sdc6 -- fdisk --- Nasqueron:/home/oberon# fdisk /dev/sdc The number of cylinders for this disk is set to 19457. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): p Disk /dev/sdc: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/sdc1 1 14589 1171861115 Extended /dev/sdc2 14590 1945739102210 83 Linux /dev/sdc5 1364729294464+ fd Linux raid autodetect /dev/sdc63648 1434685939686 83 Linux /dev/sdc7 14347 14589 1951866 83 Linux Command (m for help): q -- mdadm.conf --- Nasqueron:/home/oberon# cat /etc/mdadm/mdadm.conf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST system # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md0 level=raid1 num-devices=2 UUID=10871c4b:9ce84f01:e6dc959d:b20685c9 #ARRAY /dev/md1 level=raid0 num-devices=2 UUID=12a57a1a:bb75e74a:e6dc959d:b20685c9 ARRAY
Bug#450851: Fixed
Hi all, This bug seems to be fixed with the newest version of evdev (unstable). NOT OK with 1:1.2.0-1 OK with 1:2.0.8-1 Commit Log for Sat Dec 13 07:29:11 2008 Die folgenden Pakete wurden aktualisiert: xserver-xorg-input-evdev (1:1.2.0-1) to 1:2.0.8-1 Thanks for your work! -kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#486101: freehdl.pc missing in package freehdl
Hi, The error is because the freehdl.pc file is not included in the package. Adding the line usr/lib/pkgconfig/freehdl.pc to libfreehdl0.install (in the package source) and re-building the package should solve that issue. I also had to adapt the script qucsdigi (/usr/bin/qucsdigi) and add --tag CXX otherwise I would get a compile error: libtool --quiet --mode=link $CXX $NAME._main_.o $NAME.o $LIBS $IEEELIBS -o $NAME libtool --quiet --mode=link --tag CXX $CXX $NAME._main_.o $NAME.o $LIBS $IEEELIBS -o $NAME Both changes are quite trivial (and I am not sure if freehdl.pc really belongs to the libraries, or if the second fix is the correct response here), so I am not attaching patches. I can still do so if required, of cours. Best wishes, Kurt Gysin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481083: Same Problem
I can reproduce the exact same problem - Thanks for pointing out the core-problem! My local cups-server was configured to forward printer-definitions found on other cups-servers. As this was my laptop, it could not access them while undocked, and vym would not start... Changing the cups configuration helped: http://localhost:631/admin Show printers from other systems (or similar - it is in German on my machine) = OFF And yes, the vym files are all accessible as .xml once you open the containing zip-file... :-) -kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#450851: Reproduced also in latest unstable...
Hi all, I have the same problem with the latest unstable... Regards, -kurt -- Section InputDevice Identifier MX1000 Driver evdev Option CorePointer #Option Name Logitech USB Receiver Option Device /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse Option ZAxisMapping 4 5 7 6 Option Buttons 12 EndSection -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-1-amd64 (SMP w/1 CPU core) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-input-evdev depends on: ii libc6 2.6.1-1 GNU C Library: Shared libraries ii xserver-xorg-core 2:1.4.1~git20071119-1 Xorg X server - core server xserver-xorg-input-evdev recommends no packages. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-1-amd64 (SMP w/1 CPU core) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-input-evdev depends on: ii libc6 2.6.1-1 GNU C Library: Shared libraries ii xserver-xorg-core 2:1.4.1~git20071119-1 Xorg X server - core server xserver-xorg-input-evdev recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315598: rekall: crashes on inserting link
Hi Am Freitag, den 08.07.2005, 11:18 +0200 schrieb Peter Eisentraut: Am Donnerstag, 23. Juni 2005 22:40 schrieb Kurt Gysin: rekall crashes immediately upon selecting any of the New-Link-* selections in the context menu. I cannot reproduce that. Which is somewhat strange.. it really does happen on two different machines. I am not sure if this is the same issue as in http://www.totalrekall.co.uk/pipermail/rekall_totalrekall.co.uk/2005-Februa ry/88.html but it sure looks the same. Unfortunately the thread there died away Perhaps you want to follow up there. That might be more effective than me relaying information that I cannot reproduce. Yes, did that.. no answer up to now. What is strange: I get the problem with _any_ version of rekall I can get my hands on (debian, tarball from upstream, cvs), so it probably is not a problem with _this_ package... I just tried sid again, still happens. I will try again to play with it later... I guess some library problem. Regards -kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
