Bug#302304: hddtemp isn't restarted after update
tag 302304 + unreproducible thanks Andreas Schmidt a écrit : Package: hddtemp Version: 0.3-beta13-3 Severity: normal After update, the demon should be restarted. Currenly hddtemp is stopped before the upgrade and restarted just after. Wasn't it the case for you? Have you seen any error? A copy and paste of the upgrade would be nice. Bye, Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#299726: libusb-0.1-4: latest version breaks gphoto2
Luke Q a écrit : Package: libusb-0.1-4 Version: 2:0.1.10a-6 Severity: important After upgrading to the most recent version of libusb, gphoto2 fails (usually in the middle of downloading the third photo or so) with the following errors: gp_port_read: Resource temporarily unavailable *** Error *** PTP I/O error *** Error (-1: 'Unspecified error') *** I noticed this problem on another machine, so just to be sure, I did a full download from my camera, then upgraded libusb, then tried the download again and saw the error. Could you please tell me which gphoto2 backend are you using? It would also be nice to run gphoto2 with the environement variable USB_DEBUG set to 255 and to send me the log. BTW, any message in /var/log/messages? Bye, Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged
Julien BLACHE a écrit : Greg Kochanski <[EMAIL PROTECTED]> wrote: Here is /var/log/messages. The scanner got wedged twice, once around 00:33:50 and again around 00:38:00. Then, it worked nicely until I turned it off, around 01:09. Mar 16 00:13:52 gpk -- MARK -- Mar 16 00:29:41 gpk kernel: usb 2-2.1: new full speed USB device using address 4Mar 16 00:29:42 gpk usb.agent[8271]: libusbscanner: loaded successfully Mar 16 00:33:42 gpk kernel: usb 2-2.1: usbfs: interface 0 claimed while 'xsane' sets config #1 Mar 16 00:33:52 gpk kernel: usb 2-2.1: USB disconnect, address 4 Mar 16 00:33:54 gpk kernel: usb 2-2.1: new full speed USB device using address 5 Interesting, although I don't know what I should think about that :/ Aurélien may have an idea. Not really. Could you please run USB_DEBUG=255 xsane and send us the output log ? Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#298041: i2c: use a different ABI than the kernel one
reassign 298041 i2c retitle 298041 i2c: use a different ABI than the kernel one severity 298041 grave tag 298041 + sarge tag 298041 + sid thanks Benoit Hamet a écrit : Hope that you get it :] I think that perhaps if struct semaphore is the same size of int client_count, then perhaps the size are the same, but I would be really You're totally right, I have looked to quickly, sorry. Actually, I was biased by the fact the upstream announce with this new version that the compatibility has been restored, which is false. The bad thing is that this bug is more serious than I thought initially. There is no need to warn the user to use a different i2c.h, as the structure i2c_adapter *shall* be identical in both files. I am currently working with the upstream on a patch. I already have one, but as I am not familiar with i2c core code and semaphores, I prefer to discuss it before applying it to the Debian package. For the RM team reading this mail (if you are reading it), I think it will be possible to close this bug in 1 to 3 days (+ 2 days to propagate to testing), as the upstream is usally very reactive, and also present on IRC during the evening (CET time). Bye, Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
On Sat, Feb 26, 2005 at 03:54:02PM +0100, Milan Zamazal wrote: > test3 (please note this one doesn't segfault and produces expected > output): Nice ! The only difference between test2 and test3 version is the size of blocks that are requested to the device. 16kB in test2 and 4kB in test3. It seems you camera get confused by too big datablocks. However, I think there is still a bug in gphoto2. It should not blindly assume that the size of the data returned is the same as requested, and exit gracefully in that case. I'll upload a new version soon. Thanks for your help while debugging. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
On Sat, Feb 26, 2005 at 02:52:26PM +0100, Milan Zamazal wrote: > AJ> BTW, the original bug report mentions you are using a kernel > AJ> 2.6.9. Are you still using the same kernel? > > Yes. (And don't forget libusb-0.1-4 1:0.1.8-17 still works perfectly.) The way libusb communicate with the kernel with the kernel has changed (thus your problem), and the problem appears only with the newest way. BTW, the bug has just been fixed in 2.6.11-rc5-bk1. I have just produced two new test versions (test2 and test3), which should output some more debugging infos (that I hope useful). Could you please test them (no need to use a debug mode) and send me the output? http://temp.aurel32.net/libusb/test/ Thanks, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
On Sat, Feb 26, 2005 at 02:13:42PM +0100, Milan Zamazal wrote: > Unfortunately it still segfaults. Here is the log: That's strange, that doesn't seems to correspond to what gphoto2 says. Could you please send me the log of both libusb (the test version) and gphoto2 in debug mode? BTW, the original bug report mentions you are using a kernel 2.6.9. Are you still using the same kernel? Kernel version 2.6.11-rc1 and newer are buggy, and it is also the case of some series such as -ac, -mm, ... And sorry to ask you a lot of thing, I don't have the hardware to debug the problem. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
Hi! After looking at the logs you send me and at the code, I may have found a problem. It seems to be possible that the kernel returns less data than expected, but returns some data. This is currently not handle in libusb. Could you please test this version with USB_DEBUG=255 ? http://temp.aurel32.net/libusb/test/ I hope this would fix your problem. Either it works or not, could you please send me the log? Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
On Fri, Feb 25, 2005 at 07:34:49PM +0100, Milan Zamazal wrote: > >>>>> "AJ" == Aurélien Jarno <[EMAIL PROTECTED]> writes: > > AJ> Next step, could you please run gphoto2 in debugging mode to see > AJ> if there is something interesting in the output. For that, just > AJ> run gphoto2 --debug put_your_args_here > > Here's the output: 3.188609 sierra/library.c(2): Reading packet... 3.188661 gphoto2-port(2): Clear halt... 3.193595 gphoto2-port(2): Reading 32774=0x8006 bytes from port... 3.284674 gphoto2-port(2): Could only read 10 out of 32774 byte(s) That sounds strange 3.284731 gphoto2-port(3): Hexdump of 10 = 0xa bytes follows: 03 00 04 00 0a 00 00 00-0a 00.. 3.284751 gphoto2-port(2): Clear halt... 3.285657 sierra/library.c(2): Packet successfully read. 3.285697 sierra/library.c(2): Successfully read packet. Interpreting result (0x03) ^^ Actually the read is not successfull (10 of 32774 bytes) Ok, I think there is a bug somewhere in libusb, that makes it returning less data than asked. Then there is another bug in gphoto2. It should not interpret the data in that case. -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
On Fri, Feb 25, 2005 at 06:22:11PM +0100, Aurélien Jarno wrote: > Milan Zamazal a écrit : > >AJ> Milan, could you please run USBDEBUG=255 gphoto2 > >AJ> put_your_args_here, and send me the result? > > > >This doesn't output anything. > Ok, I need to understand why. I given the wrong variable, sorry. Could you please try with USB_DEBUG=255 ? Thanks, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
Milan Zamazal a écrit : AJ> Milan, could you please run USBDEBUG=255 gphoto2 AJ> put_your_args_here, and send me the result? This doesn't output anything. Ok, I need to understand why. AJ> Also, doing an strace (just run strace gphoto2 AJ> put_your_args_here,) would be useful. I'll send it to you. I have looked at it, everything seems to be normal until the segfault. Next step, could you please run gphoto2 in debugging mode to see if there is something interesting in the output. For that, just run gphoto2 --debug put_your_args_here Thanks, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
Frederic Peters a écrit : Hi Aurelien Hi! Did the new libusb break ABI ? I can rebuild libgphoto2 against the new version but this won't fix other packages using libusb. No, the ABI is still the same. What has changed is the way to communicate with the kernel, the newer version allow bigger packets and increased transfer rate. What is your take on this ? I don't know what is the problem. libusb 0.1.9 is known to have problem with big transfers, but libusb 0.1.10 fixed the problem. Has somebody reported the same problem with an other backend? Milan, could you please run USBDEBUG=255 gphoto2 put_your_args_here, and send me the result? Also, doing an strace (just run strace gphoto2 put_your_args_here,) would be useful. Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#235422: hddtemp: Not sure if this helps..
[EMAIL PROTECTED] a écrit : Package: hddtemp Version: 0.3-beta12-12 Followup-For: Bug #235422 ahrairah:/home/admin/hddtemp-0.3-beta12/src# gdb hddtemp GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) run /dev/sda Starting program: /home/admin/hddtemp-0.3-beta12/src/hddtemp /dev/sda Program received signal SIGSEGV, Segmentation fault. 0x40095cef in memcpy () from /lib/tls/libc.so.6 (gdb) bt #0 0x40095cef in memcpy () from /lib/tls/libc.so.6 #1 0x0804b567 in modeselect (device=-13, pagenum=6 '\006', pBuf=0xb72c "") at scsicmds.c:137 #2 0x4058 in ?? () ... Actually I think this bug would be fix (the fact that hddtemp crashes, not the fact that it can't read temperature of 3ware card) soon. I have a working version of hddtemp using SG_IO on my hard disk, and it seems that fixes the problem. This version needs some more work to be distributable (currently the code is ugly), I think it'll take 1 or 2 weeks. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#295400: /usr/sbin/fancontrol: please add option to avoid calling restorefans() on exit
[EMAIL PROTECTED] wrote: I'd better say "(e.g. to go to single user mode, boot solaris/x86, boot freebsd...)" that is: I need to control my fan speed, fullstop. fancontrol do that job, when it is running. It don't has to do its job when it is not running! the only ways I found are: 1. send fancontrol SIGKILL manually. 2. hand-edit fancontrol. (which I did: but my changes will be overwritten at next package upgrade.) To stop your fan, you can also do an: echo "0" > /sys/bus/i2c/device/.../.../pwmX what about a non documented, deeply buried option to restore fans to a configurable percentage of full speed? If you want such a function you can write you on script, but again this is not the job of fancontrol. -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#295400: /usr/sbin/fancontrol: please add option to avoid calling restorefans() on exit
giuseppe bonacci wrote: Package: lm-sensors Version: 1:2.9.0-12 Severity: wishlist the buggy BIOS of my motherboard sets the cpu fan to full speed on power-on, but leaves it alone on reboot. I must use fancontrol to avoid getting mad for the noise. but when I reboot (e.g. to boot windows) fancontrol gets killed and restores fan to full speed. This is necessary to restore the speed of the fan, because there is too much risk of burning your CPU if you leave the fan speed low and uncontroled, which is the case when fancontrol is killed. If you need to control your fan speed under Windows, use a software under Windows to do that. I wish there was a way to disable that behaviour. There is a way, but it won't be supported by Debian and by the upstream for the reason explained above, even as an option. Please also note that your request is very specific, so I suggest you either to use a Windows software to control the fan speed, or to modify fancontrol by yourself. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#295519: Shouldn't the package remove lm-sensors from /etc/blacklist.d ?
Shaul Karl wrote: Package: lm-sensors Version: 1:2.9.0-13 Severity: minor When upgrading TO 2.9.0-12, dpkg announces that /etc/blacklist.d is not removed because it is populated with lm-sensors. Doesn't lm-sensors assumes responsibility for /etc/blacklist.d/lm-sensors? Yes, that's true. However, as it is a conffile, it is not removed automatically. Now that I have 2.9.0-13, can I safely remove the lm-sensors from /etc/blacklist.d? Can I safely delete the blacklist.d directory afterwards? Yes you can for both. I'll upload a new version to fix that. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294139: [brian@ristuccia.com: libusb broken on arm?]
reopen 294139
tags 294139 - sid
thanks
Brian Ristuccia wrote:
At any rate, your experimental code seems to allow interoperability with
kernels that don't pass back all of the descriptor info. The lsusb -v output
is now plausible and rudimentary testing with various userspace programs
requiring libusb is successful.
Well done.
Good that it work. I have just uploaded a new version with the patch. In
case you need it, please find it below. It should apply to CVS, version
0.1.9 and version 0.1.8 (with maybe a few lines offset). I have also
send it to the upstream author.
Steve, is it possible to upload a fixed version directly to Sarge? The
current version in Sid is affected by another RC bug (#294368), and thus
this fix can't propagate to Sarge until #294368 is fixed. I hope it will
be fixed soon, it is in the first position of my TODO list.
Bye,
Aurelien
Index: linux.c
===
RCS file: /cvsroot/libusb/libusb/linux.c,v
retrieving revision 1.66
diff -u -d -p -r1.66 linux.c
--- linux.c 3 Feb 2005 19:11:25 - 1.66
+++ linux.c 9 Feb 2005 15:10:04 -
@@ -452,7 +452,8 @@ int usb_os_find_devices(struct usb_bus *
else
fprintf(stderr, "Config descriptor too short (expected %d,
got %d)\n", 8, ret);
}
-
+free(dev->config);
+dev->config = NULL;
goto err;
}
@@ -462,6 +463,8 @@ int usb_os_find_devices(struct usb_bus *
if (!bigbuffer) {
if (usb_debug >= 1)
fprintf(stderr, "Unable to allocate memory for descriptors\n");
+free(dev->config);
+dev->config = NULL;
goto err;
}
@@ -476,8 +479,9 @@ int usb_os_find_devices(struct usb_bus *
else
fprintf(stderr, "Config descriptor too short (expected %d,
got %d)\n", desc->wTotalLength, ret);
}
-
free(bigbuffer);
+free(dev->config);
+dev->config = NULL;
goto err;
}
--
.''`. Aurelien Jarno GPG: 1024D/F1BCDB73
: :' : Debian GNU/Linux developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`-people.debian.org/~aurel32 | www.aurel32.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294139: [brian@ristuccia.com: libusb broken on arm?]
tag 294139 + sarge tag 294139 + sid thanks Brian Ristuccia wrote: On Tue, Feb 08, 2005 at 08:38:22PM -0500, Brian Ristuccia wrote: After some testing, I determined that the combination of usbutils (0.70-1) and libusb-0.1-4 (0.1.9-1) on arm results in bogus zero values for bNumInterfaces and the associated *interface pointer winds up null. This On further inspection, the entire Configuration Descriptor is zero/empty on arm. Retitled the bug to better summarize the problem. Since libusb is pretty much useless on arm as a result, I'm adjusting the severity also. Thanks for your very good work, I think I have identified the problem: When an USB device is plugged, the kernel parses all the descriptors of the device, and make them available in /proc/bus/usb/xxx/xxx. When parsing all the USB devices, libusb first parses this file in /proc and then, if some information are missing, is asking the device directly. The problem is that in some cases with partial information (ie between no information and full information), libusb doesn't ask the device. It is not working on your arm computer because the kernel, for an unknown reason, returns partial descriptor. To answer Steve, the problem it's also in Sarge as this part hasn't changed since version 0.1.7 (sarge has 0.1.8 and sid 0.1.9). To confirm all what I said, I have produced a test version, which is available on http://temp.aurel32.net/libusb . Could you please test it? Note that the -dev package for arm doesn't include the doc as jade was not available on the host where I built libusb. Anyway that should not be a problem for the test. Thanks, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294171: idem
Joshua Dunamis wrote: Excuse for my english, I'm italian. I noticed the same thing. After I click on Prewies the Xsane locks up. But I tried with kooka and it' the same thing. So I thing is sane and not xsane affected by this bug. I use an USB scanner HP 3400C. Before I upgraded to the last version in Sid, it worked fine. It's seems to be a little different than the bug reported by Anthony Campbell. In your case, it may be due to a bug in libusb. Could you please try to switch back to the version of libusb that is in Sarge ? -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294285: mozilla-thunderbird-locale-fr: 80 caracters ligne problem
retitle 294285 mozilla-thunderbird: wrapping doesn't work as expected reassign 294285 mozilla-thunderbird thanks Arno wrote: Hello, You reported the problem on the French translation. Is it specific to it? I was asking the question to myself. I'm using the french version of thunderbird. I don't know if this bug can be found in the original version too but if the package of the french translation is only a translation ... it should be better to reassign this bug report to the mozilla-thunderbird package. :-) ok, reassigning the bug to mozilla-thunderbird. -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294139: [brian@ristuccia.com: libusb broken on arm?]
Brian Ristuccia wrote: On Tue, Feb 08, 2005 at 10:13:51AM +0100, Aurelien Jarno wrote: Do you get also the problem with 'lsusb -v' (for the usbutils packages). As it cycle through all possible values of the libusb structures, it think it is a good test. lsusb -v seems to work OK. But it's not linked against the libusb shared library on this system. Which system are you using? lsusb is linked to libusb in both sarge and sid. -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293542: hddtemp: does not show all disks
Daniel J. Priem wrote: Package: hddtemp Version: 0.3-beta12-9 Severity: normal > If i run /etc/init.d/hddtemp restart Stopping disk temperature monitoring daemon: done. Starting disk temperature monitoring daemon: /dev/hda /dev/hde /dev/hdg. telnet localhost 7634 2. ok. edited /etc/default/hddtemp added DISKS="/dev/hda /dev/hdc /dev/hde /dev/hdg" /etc/init.d/hddtemp restart Stopping disk temperature monitoring daemon: done. Starting disk temperature monitoring daemon: /dev/hda /dev/hde /dev/hdg. (still missing drive hdc :( In both case /dev/hdc seems to be ignored because it is considered as a CDROM drive. This is the case because you have a symlink /dev/cdrom -> /dev/hdc. Removing it should fix your problem. hddtemp refuses to monitor a CDROM drive, as it can cause system hangs on some cheap drive that are not 100% ATA compliant. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292718: xsane: Upgrading package, attempts to remove a directory that is not empty.
Scott M. Likens wrote: desolation:/var/log/cups# dpkg -S /usr/share/doc/xsane/html/sane-problems-doc.html dpkg: /usr/share/doc/xsane/html/sane-problems-doc.html not found. desolation:/var/log/cups# ls /usr/share/doc/xsane changelog.Debian.gz xsane.ACCELKEYS xsane.BUGS xsane.TODO changelog.gz xsane.AUTHOR xsane.LOGO xsane.VENDOR-STRINGS copyrightxsane.BACKENDSxsane.PROBLEMS.gz html xsane.BEGINNERS-INFO xsane.ROOT desolation:/var/log/cups# ls /usr/share/doc/xsane/html/sane-problems-doc.html /usr/share/doc/xsane/html/sane-problems-doc.html desolation:/var/log/cups# Ok, I should admit that I still don't understand what happened, but I'll upload a new version which should fix your problem soon. Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292718: xsane: Upgrading package, attempts to remove a directory that is not empty.
On Mon, Jan 31, 2005 at 04:14:18PM -0800, Scott M. Likens wrote: > Nay, only installed from deb's. Ok, coud you please run dpkg -S /usr/share/doc/xsane/html/sane-problems-doc.html and send me the result? I would like to know if the files in /usr/share/doc/xsane/html/ are owned by a package or not. -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293082: Hotplug string for Epson CX6600 scanner.
severity 293082 wishlist tag 293082 + pending thanks Hi! Nathan R. Valentine wrote: Package: libsane Version: 1.0.15-6 Please include the following hotplug device string for the Epson CX6600. #EPSON Corp.|Stylus CX6600 libusbscanner 0x0003 0x04b8 0x08130x 0x 0x00 0x000x000x00 0x00 0x00 0x It has been added to the SVN repository, and thus will be included in the next upload. Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292718: xsane: Upgrading package, attempts to remove a directory that is not empty.
Scott M. Likens wrote: Hope that helps. [code] html xsane-negative.jpg sane-problems-doc.html xsane-new.jpg sane-scantips-doc.html xsane-ocr.jpg sane-xsane-advanced-doc.html xsane-open.jpg sane-xsane-batch-scan-doc.html xsane-paper-landscape-bottom-left.jpg sane-xsane-color-correction-doc.html xsane-paper-landscape-bottom-right.jpg sane-xsane-copy-doc.html xsane-paper-landscape-center.jpg sane-xsane-doc.htmlxsane-paper-landscape-top-left.jpg sane-xsane-empty-doc.html xsane-paper-landscape-top-right.jpg sane-xsane-fax-doc.htmlxsane-paper-portrait-bottom-left.jpg sane-xsane-gimp-doc.html xsane-paper-portrait-bottom-right.jpg sane-xsane-histogram-doc.html xsane-paper-portrait-center.jpg sane-xsane-mail-doc.html xsane-paper-portrait-top-left.jpg sane-xsane-main-doc.html xsane-paper-portrait-top-right.jpg sane-xsane-preview-doc.htmlxsane-pipette-black.jpg sane-xsane-save-doc.html xsane-pipette-gray.jpg sane-xsane-setup-copy-doc.html xsane-pipette-white.jpg sane-xsane-setup-display-doc.html xsane-preferences.jpg sane-xsane-setup-enhancement-doc.html xsane-preset-area.jpg sane-xsane-setup-fax-doc.html xsane-preview.jpg sane-xsane-setup-image-doc.htmlxsane-printer.jpg sane-xsane-setup-mail-doc.html xsane-rename.jpg sane-xsane-setup-save-doc.html xsane-resolution.jpg sane-xsane-standard-doc.html xsane-restore.jpg sane-xsane-viewer-doc.html xsane-rgb-default.jpg xsane-advanced.jpg xsane-rgb-values.jpg xsane-aspect-ratio.jpg xsane-rotate-180.jpg xsane-autoenhance.jpg xsane-rotate-270.jpg xsane-autoraise_scanarea.jpg xsane-rotate-90.jpg xsane-autoselect.jpg xsane-rotation.jpg xsane-batch-scan-add.jpg xsane-save.jpg xsane-batch-scan-delete.jpgxsane-save2.jpg xsane-batch-scan.jpg xsane-scale.jpg xsane-blur.jpg xsane-scansource.jpg xsane-brightness.jpg xsane-setup-copy.jpg xsane-clone.jpgxsane-setup-display.jpg xsane-colormode.jpgxsane-setup-enhancement.jpg xsane-contrast.jpg xsane-setup-fax.jpg xsane-copy.jpg xsane-setup-image.jpg xsane-default.jpg xsane-setup-mail.jpg xsane-delete-preview-cache.jpg xsane-setup-ocr.jpg xsane-despeckle.jpgxsane-setup-save.jpg xsane-disk.jpg xsane-standard.jpg xsane-fax-project.jpg xsane-store.jpg xsane-fax.jpg xsane-threshold.jpg xsane-gamma.jpgxsane-viewer-window.jpg xsane-gimp.jpg xsane-viewer.jpg xsane-histogram.jpgxsane-visible-area.jpg xsane-logo2.jpgxsane-zoom-in.jpg xsane-mail-project.jpg xsane-zoom-not.jpg xsane-mail.jpg xsane-zoom-out.jpg xsane-medium.jpg xsane-zoom-undo.jpg xsane-mirror-x.jpg xsane-zoom.jpg xsane-mirror-y.jpg xsane.jpg [/code] Oops, that's not what I expected. I still don't understand how these files appeared there. Did you once installed xsane from source? -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256517: Pcmcia bug with preemptive patch
zze-Beta Testeur LABROSSE A ext RD-CSRD-GRE wrote: Hi, A little mistake in a copy paste. You may read : kernel-patch-2.4-preempt 20040321-2 In place of kernel-patch-2.4-lowlatency 20040516 Ok, so it's seems to corresponds to what google says, ie there is no problem with the kernel-patch-2.4-preempt. Christian, could you please confirm that you still have the problem? Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256517: Pcmcia bug with preemptive patch
zze-Beta Testeur LABROSSE A ext RD-CSRD-GRE wrote: Hi list, Hi Aurélien, I try to reproduce the bug with: kernel-source-2.4.24 2.4.24-3 kernel-patch-2.4-lowlatency 20040516 and a Cisco wifi PC-Card. Thanks for this test, however, it seems that the problem was caused byt the kernel-patch-2.4-preempt. Did you also added this patch? Kernel was builded with make-kpkg --initrd --config menuconfig --added_patch preempt The card was recognised by the system, even if the drivers needs third party firmare, and i get no ready network interface. I used the 'cardctl status' command to show if the card was listed, and it was. Ok Aurélien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#290477: Breaks after mozilla updates
Aurélien Jarno wrote: I am tagging the package sid, as mozilla-locale-fr is still installable in sid and will still be installable in sarge (mozilla won't migrate to sarge if some packages become uninstallable in sarge). Oops, I meant ...mozilla-locale-fr is uninstallable in sid but is and will still be installable ... -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#290477: Breaks after mozilla updates
tag 290477 + sid severity 29047 grave thanks Loïc Minier wrote: Package: mozilla-locale-fr Severity: normal Hi, Sorry for the obvious report, but mozilla-locale-fr is uninstallable in sid, and soon to be uninstallable in sarge (hence I'm not tagging sid). I am tagging the package sid, as mozilla-locale-fr is still installable in sid and will still be installable in sarge (mozilla won't migrate to sarge if some packages become uninstallable in sarge). This is because this package depends of a specific version of Mozilla. Please request/make the necessary changes in your build system so that it doesn't prevent users from updating their mozilla-browser package. I can't. The French translation is not available for this version, I can't create it! Galeon suffers of the very same problem, and it is not acceptable to have packages lagging behind mozilla versions since this causes breakage when users need to "hold" packages (such as the reopening of #288875). I agree but I don't have a magic solution for that. If you have one, please tell me. Meanwhile, you can remove the French translation. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#288418: lm-sensors: unrecognized via686a chip
Romain Riviere wrote: Well I tried both : my old sensors.conf for the same machine, and the latest Debian version. With the Debian file I get such nonsensical max settings as : P/S Fan: 2220 RPM (min = 56250 RPM, div = 8) ALARM > Yep, that's fifty-six thousand RPM, no wonder the ALARM goes off. Anyways, setting manual max RPM worked fine, but as opposed to what is said in the sensors.conf, the defaults are NOT fine :) Actually, the defaults value (ie when not set by lm-sensors) are provided by the bios. It means that your bios doesn't set the min value for this fan. Also some of the readings are still offset by quite a bit, but I know there's not much to do about it except trial and error with various compute lines until the value is in the expected range, since the mobo manufacturers won't provide much data (especially for VIA)... The offset may be due rounding that was not done correctly done in kernel previous than 2.6.6 (in fact the exact version depends on the chip) and lm-sensors 2.8.8. I think this bug can now be closed, as it is now separate from the other bug report about the shuttle mainboard. Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#288418: lm-sensors: unrecognized via686a chip
Romain Riviere wrote: Sure. Btw, the chip module itself is called via686a, no such thing as i2c-via686 ;) Yes, sorry I meant via686a, only bus drivers has i2c- as prefix. marla:/home/smokey# lsmod | grep i2c i2c_isa 1856 0 i2c_sensor 3456 1 via686a i2c_dev10208 0 i2c_core 22736 4 via686a,i2c_isa,i2c_sensor,i2c_dev It s worth noting that I had no idea that via686a was incompatible with the i2c-viapro, to the point where it would render the chip unreadable until the next reboot. The fact that sensors-detect thinks it can read via686a readings over SMBus is slightly misleading. I should admit I also only know that for very few time. Actually 2.6 kernels refuse to let two modules accessing the same chip. It's a new feature that was not present in 2.4 kernels. The lm-sensors team thought that they can add a fix for that but it seems to be a little tricky, that's why the sensors-detect script has not been modified. They are still working on a fix. Anyway the latest lm-sensors includes: - An entry about that into the FAQ - A warning in sensors-detect - An hotplug blacklist for i2c-viapro, so that modules won't get loaded automatically. Long story short, as long as I don't load i2c-viapro, I'm safe. However, I am not sure about that (I don't have such a system), but I think you don't need to reboot to get your sensors working. Removing both i2c-viapro and via686a modules and reloading only via686a should work. with the same sensors.conf as in my old config, I get completely different min/max settings, which is a bit weird. That's strange. Was your configuration file for a very old version of lm-sensors? Did you get it from Debian or from another distribution. And did you run sensors -s to set the min/max values? Thanks for your time et très bonne année ;) Bonne année ! Aurélien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#206691: ITP: python-matplotlib -- A python based gtk plotting system in a style similar to matlab, aiming for publication quality plots.
Hi, What is the current state of the packages? If you don't have any news from your sponsor, I think it's time to bypass it. I can sponsor you if you want, unless Jochen, one of the upstream, wanted to do so. I use python-matplotlib at work, and I really want to see it in Debian, in order to not have to install it from sources. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#289846: pdftk: new action to generate stencil fdf file for fill_form
On Tue, Jan 11, 2005 at 08:23:23PM +0100, Aurélien Jarno wrote: > forwarded 289846 [EMAIL PROTECTED] > thanks > > On Tue, Jan 11, 2005 at 05:49:48PM +0100, Bernhard R. Link wrote: > > On Tue, Jan 11, 2005 at 12:15:15PM +0100, Aurélien Jarno wrote: > > > >The attached patch adds a new generate_fdf action to generate a FDF > > > >out of a PDF file. (As the format is to ugly to write it directly > > > >by hand). As I'm neighter fluently in java nor in C++, I guess it > > > >could use some review. The upstream author has reviewed your patch and will include it in the next release. However, it doesn't a lot of time by now, so I have directly included your patch into the Debian package. BTW, what is the answer of the upstream :) > I am impressed that somebody went to the trouble of figuring out both > the iText code as well as my own code to add a feature to pdftk! Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#289846: pdftk: new action to generate stencil fdf file for fill_form
forwarded 289846 [EMAIL PROTECTED] thanks On Tue, Jan 11, 2005 at 05:49:48PM +0100, Bernhard R. Link wrote: > On Tue, Jan 11, 2005 at 12:15:15PM +0100, Aurélien Jarno wrote: > > >The attached patch adds a new generate_fdf action to generate a FDF > > >out of a PDF file. (As the format is to ugly to write it directly > > >by hand). As I'm neighter fluently in java nor in C++, I guess it > > >could use some review. > > There is no attached file. Could you please send it again? > > Ups, sorry. Someday I have to configure mutt to warn me if I talk > about attached patches and do not attach them I often make the same mistake :) > So, this time it should be attached. Ok, I forwaded it to the upstream author. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#289846: pdftk: new action to generate stencil fdf file for fill_form
Bernhard R. Link wrote: Package: pdftk Version: 1.12-1 Severity: wishlist The attached patch adds a new generate_fdf action to generate a FDF out of a PDF file. (As the format is to ugly to write it directly by hand). As I'm neighter fluently in java nor in C++, I guess it could use some review. There is no attached file. Could you please send it again? Thanks, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#289555: Still dpkg-divert problems
On Mon, Jan 10, 2005 at 08:08:27PM +0100, Svante Signell wrote: > On Mon, 2005-01-10 at 15:55 +0100, Aurélien Jarno wrote: > > Svante Signell wrote: > > > diversion of /lib/modules/2.4.27-1-686/kernel/drivers/i2c/i2c-algo-bit.o > > > to /lib/modules/2.4.27-1-686/old-i2c/i2c-algo-bit.o by i2c-2.4.27-1-686 > > > > Everything seems to be normal, so I don't know what happens exactly. I > > tried a lot of installation and upgrade sequences (even 2.7.0-16 -> > > 2.9.0-1 -> 2.9.0-2 ... -> 2.9.0-8), and I can't reproduce your problem. > > The 2.9.0-1 through 2.9.0-7 version fails to install, but 2.9.0-8 works > > correctly. > > > > I made some test packages that have debug information printed in the > > preinst script, could you please try to install them: > > http://temp.aurel32.net/i2c > > #> dpkg -i i2c-2.4.27-1-686_2.9.0-8+test_i386.deb > (Reading database ... 152717 files and directories currently installed.) > Preparing to replace i2c-2.4.27-1-686 1:2.7.0-16 (using > i2c-2.4.27-1-686_2.9.0-8+test_i386.deb) ... > Removing old diversion > dpkg-divert: rename involves overwriting > `/lib/modules/2.4.27-1-686/kernel/drivers/i2c/i2c-algo-bit.o' with > different file `/lib/modules/2.4.27-1-686/old-i2c/i2c-algo-bit.o', not > allowed > dpkg: error processing i2c-2.4.27-1-686_2.9.0-8+test_i386.deb > (--install): > subprocess pre-installation script returned error exit status 2 > Errors were encountered while processing: > i2c-2.4.27-1-686_2.9.0-8+test_i386.deb > > > Also, would it be possible to give me the output of dpkg -S > > /lib/modules/2.4.27-1-686/kernel/drivers/i2c/i2c-algo-bit.o > > #> dpkg -S /lib/modules/2.4.27-1-686/kernel/drivers/i2c/i2c-algo-bit.o > diversion by i2c-2.4.27-1-686 > from: /lib/modules/2.4.27-1-686/kernel/drivers/i2c/i2c-algo-bit.o > diversion by i2c-2.4.27-1-686 > to: /lib/modules/2.4.27-1-686/old-i2c/i2c-algo-bit.o > kernel-image-2.4.27-1-686: > /lib/modules/2.4.27-1-686/kernel/drivers/i2c/i2c-algo-bit.o > Thanks, now I have to think a lot to find the problem and to found a fix. I hope to have a new package during the night. -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#288418: lm-sensors: unrecognized via686a chip
Hi, Sorry, I forgot about the second part of your bug report, ie, the machine B. I split the bug report in two, so we can speak of each machine in a different thread. Concerning the machine B, ie the machine, with the via686a, could you please tell me the kernel you are using (2.4 or 2.6). It has a great difference on the modules version. Then could you please tell me which modules have you loaded? Theoretically, you should have i2c-core, i2c-dev, i2c-isa, i2c-sensor and i2c-via686. Please make sure you also don't have i2c-viapro loaded (or built into the kernel), as they are not compatible with i2c-via686. Note that this module could be loaded by sensors-detect if you answer yes to all questions. In short, it would be nice to have the output of lsmod, so I could verify if everything is ok. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#289555: Still dpkg-divert problems
Svante Signell wrote: diversion of /lib/modules/2.4.27-1-686/kernel/drivers/i2c/i2c-algo-bit.o to /lib/modules/2.4.27-1-686/old-i2c/i2c-algo-bit.o by i2c-2.4.27-1-686 Everything seems to be normal, so I don't know what happens exactly. I tried a lot of installation and upgrade sequences (even 2.7.0-16 -> 2.9.0-1 -> 2.9.0-2 ... -> 2.9.0-8), and I can't reproduce your problem. The 2.9.0-1 through 2.9.0-7 version fails to install, but 2.9.0-8 works correctly. I made some test packages that have debug information printed in the preinst script, could you please try to install them: http://temp.aurel32.net/i2c Also, would it be possible to give me the output of dpkg -S /lib/modules/2.4.27-1-686/kernel/drivers/i2c/i2c-algo-bit.o ? Bye Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
