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#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#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#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#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#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#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#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#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#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?]
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#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. snip #EPSON Corp.|Stylus CX6600 libusbscanner 0x0003 0x04b8 0x08130x 0x 0x00 0x000x000x00 0x00 0x00 0x /snip 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#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
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]
