Bug#943729: lvcreate -Z y does not imply -W y contrary to manual ?
Looks similar to: https://bugzilla.redhat.com/show_bug.cgi?id=2163568 Purpose of -Z y|n -W y|n is to control whether the action will be made - but you still get confimation promp for proceeding with wipe. If you want to automatically answer 'yes' to prompts - there is '--yes' option. Regards Zdenke
Bug#966524: lvm2: "lvconvert --merge" does not remove the snapshot fter completing
When the machine is rebooted and old thick snapshot merging is started, it may take some time. So there need to be something 'monitoring' progress of the merge and react when merge is finished. For this purpose the 'default' logic in lvm2 is 'lvmpolld' service - that should be present in the system, so lvchange activation command can connect lvmpolld service that would monitor progress of the merge. Once finished, lvmpolld will basically --refresh VG and update metadata and drop 'empty/merged' snapshot. There is also option to avoid using 'lvmpolld' and use the implicit monitoring with 'lvchange --background' that would need to be used with activation. As such there is most likely no bug on lvm2 here - but likely some configuration troubles. Also note lvmetad is 'gone' for 2.03 version of lvm2 - so there should be no connection with lvmetad udev rules.
Bug#953185: ^C should cancel whole operation, not be treated as "no"
There is opened lvm2 upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1806563 Which should resolve this bug for upstream lvm2 package. Zdenek
Bug#865463: lvm2: VG with thin pool LV can be created without thin-provisioning-tools
Hi If thin/cache tools are not installed (or user wish to not use them), user can configure lvm.conf to be using "" empty strings. While this is surely not recommended way how to use thin-p, technically it's possibly to bypass presence of these tools on a system. Regards Zdenek
Bug#773734: Fixed upstream
On Sat, 04 Jul 2015 15:53:18 +0200 Jan Lentferwrote: According to this link, this error has already been fixed upstream. https://bugzilla.redhat.com/show_bug.cgi?id=1135639 I also consider this bug "serious", as the default mode should be "writethrough" according to the man page, but due to this bug it defaults to "writeback" and it stays "writeback" even if you specify it differently. Also it is not easy to find out what the actual mode is. So users might end up with writeback caches on non-redundant cache-storage, which is going to lead to disaster. Please upgrade to an upstream version that has the fix. Thanks!! Yes cache support was new at 111 age - so purely experimental. For cache usage - newer version of lvm2 is basically mandatory. No one is going to backport cache fixes in 2.02.111. Close bug as problem is fixed in newer releases. Regards Zdenek
Bug#773731: cache_check should be on root
On Sat, 21 Mar 2015 17:11:32 +0200 Timo Korvolawrote: On 21.03.2015 13:28, Bastian Blank wrote: > The binaries from thin-provisioning-tools depends on libstdc++, so they > must reside in /usr. Ditto for cache_check. This seems to be getting complicated. In order to support cached root, cache_check and hence libstdc++ need to be on initrd. The boot scripts could be modified to activate all volume groups before mounting root. Then it should not matter if cache_check is not on the actual root. Another possibility would be to do fsck and mounting in three phases instead of two: first fsck and mount root, then /usr and other non-cached volumes and finally cached volumes. Root and /usr could not be cached then. Or maybe just link statically to libstdc++. Upstream thinprovtools now DO support static linkage for libstdc++. Please fix packaging and close BZ. Regards Zdenek
Bug#761676: lvm2: lvs output format too long wraps on standard sized terminals
On Mon, 15 Sep 2014 11:12:17 -0600 Bob Proulxwrote: Package: lvm2 Version: 2.02.111-1 Severity: normal Since the latest update the "lvs" command now emits output lines that are so long that they wrap on standard sized terminals. For example previously: # lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert audio v1 -wi-ao 100.00g bak1 v1 -wi-ao 140.00g chrt v1 -wi-ao 30.00g home v1 -wi-ao 202.26g lcl v1 -wi-ao 93.13g lcl2 v1 -wi-ao 123.83g root v1 -wi-ao 16.00g srv v1 -wi-ao 18.62g swap v1 -wi-ao 7.45g test v1 -wi-a- 100.00m var v1 -wi-ao 5.59g Now with 2.02.111-1 this output includes trailing whitespace out to column 83 causing each line to wrap in an unpleasant way. # lvs LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert audio v1 -wi-ao 100.00g bak1 v1 -wi-ao 140.00g chrt v1 -wi-ao 30.00g home v1 -wi-ao 202.26g lcl v1 -wi-ao 93.13g lcl2 v1 -wi-ao 123.83g root v1 -wi-ao 16.00g srv v1 -wi-ao 18.62g swap v1 -wi-ao 7.45g test v1 -wi-a- 100.00m var v1 -wi-ao 5.59g This makes the output more difficult to read than before. see the 'lvm.conf'report { compact_output = 1 } I'd consider the problem as solved... Please close Regards Zdenek
Bug#756560: lvm2: cache_dir /run/lvm doesn't exist, ENOENT /run/lvm/.cache
On Wed, 30 Jul 2014 15:54:32 -0600 Jacob Anawaltwrote: Package: lvm2 Version: 2.02.95-8 Severity: normal Dear Maintainer, I have installed fresh Debian 7 systems to do some testing with and found that the default configured cache_dir of "/run/lvm" does not exist under /run. When I strace vgscan, it gives the ENOENT error because it cannot open /run/lvm/.cache. The system us using tmpfs for /run as per the Debian defaults. I don't know what is suppose to create the lvm directory under /run on reboot, but it seems that something, perhaps /etc/init.d/lvm2, should to enable caching. Upstream (original) lvm2 stores .cache within /etc/lvm dir which is persistent across reboots. Debian for unknown reason relocated this 'persistent' place to /run which is cleared on every reboot - so losing the original purpose. On the other hand on any modern distro which is using 'udev' scan, this .cache file is actually not used - since the list of devices is obtained from udev - so no big harm as the cache file is not even created... Regards Zdenek
Bug#814644: [lvm2] Stupid changes in /etc/lvm/lvm.conf again and again
On Sat, 13 Feb 2016 17:52:36 +0100 Philipp Klaus Krausewrote: Package: lvm2 Version: 2.02.141-2 Severity: normal --- Please enter the report below this line. --- When I upgrade the lvm2 package through synaptic, it comes with a /etc/lvm/lvm.conf. Since lvm2 changes the file all the time and I have set issue_discards=1 in my /etc/lvm/lvm.conf I always get the dialog about the changed config file, and get a list of changes. I have seen this multiple times recently; basically on each lvm2 upgrade. And when I see the list of changes it is just or mostly indentation or linebreaks. Sometimes some real change is hidden in there, too. But lvm2 should stop making pointless changes that just put additional maintanance burden on the user. Just as I'm typing this I am doing an lvm2 upgrade; most of the changes in the file are bullshit like this: - # is not defined, a default single-entry list containing '@*' is - # assumed. + # is not defined, a default single-entry list containing '@*' + # is assumed. Philipp lvm2 package now provides internal support for diffing or showing new options in differnt releases... See 'man lvmconfig' for large variety of options. It may easily generate new config file from scratch. User may just keep his changes in small file and let other things at defaults. IMHO much bigger issue is in fact your mentioned 'issue_discard' used - this option is often misunderstood. It has nothing in common with TRIM on exiting LV. It only 'TRIM' space in VG AFTER LV is lvremoved - this makes mostly sense only in case VG is on some 'provisioned' device. When such option is 'enabled' user cannot recover LV with 'vgcfgrestore' if he makes a mistake - while with disabled - data would be still there - and I've already seen some disappointed users (as Ubuntu even set this to 1 on default) So if anyone is using this option with hope it helps sending discard to activated LVs - then this is not the case - such LVs are passing discard through if the underlaying PV has discard support. Regards Zdenek
Bug#717313: lvm2: Enable issue_discards = 1 automatically on non-rotational (SSD) disks?
On Sun, 20 Dec 2015 12:50:55 -0800 Matt Taggartwrote: I agree that "issue_discards = 1" should become the default in lvm on Debian. There is a case where you might not want TRIM/discards, there are security implications to enabling it with dm-crypt. In the commit message which added this support, the author states: Note that discard will be never enabled by default because of security consequences, it is up to administrator to enable it for encrypted devices. Please CLOSE this BZ as not BUG - it's really a feature. Using 'issue_discards=1' makes any lvremove operation 'irreversible' on SSD - so using 'vgcfgretore' cannot then fix the mistake of admin when he removes LV and he would like to get it back - since restoring TRIMED space is just pointless. So 'default' being 0 is carefully chosen! If admin does know what he is doing he may switch it to 1 - but that's mostly usable only if the provided storage is kind of 'provisioned' one. On typical OS - if you release LV space in your VG and your next command allocates this space for a new LV - then this LV is supposed to be discarded!. The initial BZ comment is misleading - as any new LV user - which typically is the filesystem - runs blkdiscard on such LV (as might be checked by looking at 'strace' of e.g. mkfs.ext4) Also there is no shortage of SSD performance nor SSD lifespan as the firmware in SSD is smarter and does the load balancing across whole device (so its relocating blocks that are used too often...) Regards Zdenek
Bug#508461: tries to open/close /dev/cdrom during vgscan
On Tue, 17 Feb 2009 19:37:00 -0500 "Daniel Richard G."wrote: The lvm2 package in Ubuntu Intrepid has an identical config file (only the "accept every block device" filter is uncommented), yet vgscan(8) does not exhibit this behavior. # vgscan Reading all physical volumes. This may take a while... # The fact something is not 'printed' doesn't really mean it's not happing. You would need to check - trace. Verbosity of lvm2 is increased over the time - so users are informed better about potential issues. Use lvm.conf filter to exclude device you do not want to check for presence of PV. Regards Zdenek
Bug#787555: lvm2: Unmount of invalid (full) snapshot unmounts main device too
On Tue, 02 Jun 2015 14:02:37 -0400 Matthew Gabeler-Leewrote: Package: lvm2 Version: 2.02.111-2.2 Severity: important Last night lvm2 tried to murder my server. OK, exaggerating a little bit, but it did something that seems not only wrong, but quite bad. The system was running a backup tool, using LVM snapshots to get coherent views of the filesystem. The snapshot for /var filled up. LVM decided to forcibly unmount the snapshot, which I guess is OK based on the information I've found on why this behavior was introduced, but it also forcibly unmounted the main device, resulting in the sudden and unceremonious loss of /var on the server, which had many unpleasant effects. Jun 2 01:32:32 cheetah kernel: [5957103.322426] device-mapper: snapshots: Invalidating snapshot: Unable to allocate exception. Jun 2 01:32:33 cheetah lvm[9693]: Unmounting invalid snapshot raid5-var--snap from /mnt/runbackup.8194.28259/var. Jun 2 01:32:33 cheetah lvm[9693]: Unmounting invalid snapshot raid5-var--snap from /var. It looks like something got quite confused as to what device was backing /var. This doesn't look to me like lvm2 bug. Unless raid5-var/snap was not the volume mounted on /var ?? But lvm2 does umount based on major:minor pair - so wasn't /var incorrectly mounted from a snapshot instead of an /var origin device ? The BZ then needs to show the table & mount state before and after. Old snapshots are invalidated when they get full. Such INVALID device cannot be used anymore - it's simply lost. So whoever uses something there (.e.g. mounted fs) it is already doomed at this moment. If users wants to continue to use origin & snapshots - I'd probably recommend to use thin-provisioning - which is designed for such use case much better. If user still want to use the old snapshot for this let him configure dmeventd monitoring of used space in snapshot - so there is some chance the system may resize COW space in case the used space there gets above configured threshold as the COW size is resized (when there is some free space in VG of course). Regards Zdenek
Bug#713852: (no subject)
Hi From lvm2 team - we made light overview of the proposed patches replacing semaphores with udev monitor and we are quite surprised it's being released as an lvm2 package - since it's quite major deviation from upstream behaviour and contains some bug which needs to be fixed before considering them for upstream inclusion. Please consider removal of those extra patches until they are properly fixed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673000: lvm2: enabling dm-thin is currently dangerous
Thin provisioning is still 'experimental' but users should try to use and report bugs and problems. As for thin_check tool - user could elimitnate it's usage by setting: /etc/lvm/lvm.confglobal { thin_check_executable= } # empty string But in general checks should not be skipped! Currently are being done before activation and after deactivation of thin pool. thin utils should be probably packaged as separate package - They are usable with dmsetup, they do not depend on lvm2. Unsure about lvm2 dependency - since thin utils are only needed if user plans to use thin provisioning - and they have C++ deps - thus it adds some extra libs to the core system. Zdenek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590290: Cron job and script
As far as the output of this script is concerned, I have no complaints. The only problem is the fd leak error. As Milan mentioned in message #20 - cron probably internally uses some descriptors for other things - and forgets to close it after fork and exec of a new cron jobs - these descriptors are seen by your cron shell script job and then are 'forwarded' to lvdislay. I would suggest to reassign this bug to cron package. Zdenek k...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585786: lvm2: libdevmapper and dmsetup should have versioned dependencies
Dne 14.6.2010 00:44, Bastian Blank napsal(a): On Sun, Jun 13, 2010 at 11:29:06PM +0100, Alasdair G Kergon wrote: On Sun, Jun 13, 2010 at 10:42:14PM +0200, Thomas Koch wrote: I've updated by accident (lack of better knowledge...) only libdevmapper, but not dmsetup. Afterwards my system didn't boot anymore: The package manager should enforce updating the packages together. It makes no sense to have a system with dmsetup older that libdevmapper. No, this is not how an ABI works. This means that libdevmapper have a broken interface with its users. There are few problems - however in this case the only possible fix at this moment is to setup stronger Dependency from dmsetup to the same 'libdevmapper' version. libdevmapper library is now working with udev- however Debian provides udev rules inside dmsetup package. Best solution for now is to add 'libdevmapper1.02.1 (= ${binary:Version})' to dmsetup package. Also questionable is the existence of libdevmapper library without udev rules from same package version. In the current situation there are on going udev changes and it may cause troubles to have multiple different libdevmapper libs and same udev rules. This may result into the situation that all application which are using libdevmapper in effect need dmsetup - simply because dmsetup usage is required through udev rules - so unless user explicitly requests to not use udev in lvm.conf - any lvm need libdevmapper and dmsetup from the same release. k...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575640: lvm2: readline support is gone
It's worth to note that current upstream version has further modification of Makefiles. It should allow to eventually skip some patches from Debian patch-set. Namely --enable-write_install should create 'default' user writable files after make install. Zdenek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575640: lvm2: readline support is gone
lvm2 configure script tries to detect which library provides termcap support it needs to link. For some unknown reason Debian package contains patch, which removes original libreadline check and replaces it with much simpler check AC_CHECK_LIB([readline]... which sets LIBS_READLINE - while there should be READLINE_LIBS - as being author of original code for this check - I'd like to know for curisity why there is need for this patch at all? Zdenek k...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#553940: FTBFS with binutils-gold
2009/11/2 Peter Fritzsche peter.fritzs...@gmx.de: Yavor Doganov wrote: forcemerge 526536 553940 thanks Tried to build your package and it fails to build with GNU binutils-gold. It fails to build with the default linker as well. This is fixed in a new upload, waiting for a sponsor. I haven't tested it with the gold linker, though, but I suspect I'd work. The package is at mentors.d.n, in case you'd wish to give it a try. I tried it and got following failure. /bin/bash ../../libtool --tag=CXX --mode=link g++ -Wall -g -O2 -ffast-math -fomit-frame-pointer -pipe -o avibench benchmark.o ../../lib/libaviplay.la libtool: link: g++ -Wall -g -O2 -ffast-math -fomit-frame-pointer -pipe -o .libs/avibench benchmark.o ../../lib/.libs/libaviplay.so /usr/bin/ld: benchmark.o: in function main:benchmark.cpp:179: error: undefined reference to 'XOpenDisplay' /usr/bin/ld: benchmark.o: in function main:benchmark.cpp:362: error: undefined reference to 'XCloseDisplay' This means that benchmark.cpp uses symbols from libX11.so, but doesn't inform the linker that it wants to link to it. I would guess that libaviplay.so currently links to it - which makes it work with the old GNU linker. I have added more information about that problem at http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking Is this problem with CVS version ? Zdenek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540906: and avifile maintenance
2009/10/24 Yavor Doganov ya...@gnu.org: Simon McVittie wrote: Do you intend to adopt this package and become its Debian maintainer? No, I have no interest in maintaining this package. But there's a good chance that Zdenek adopts it again, I think. I've made current update for unstable Debian - and I'm trying to get the package in some releasable product. Zdenek. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540906: O: avifile -- XviD video encoding plugin for libavifile
Well I still plan to make an update Unfortunately for now my code tree is somewhat broken :( - adding new filtering code which is somewhat complex. And there is certainly not a lot of time to move forward these days. I assume it should get much better within couple months - (i.e mid october - as there is a lot of other more advanced players around here I do not take as priority) Zdenek If there is someone who has a lot of free time to package newer version - CVS code on sf should be compilable and approximately fix all major bugs. 2009/8/10 Sandro Tosi mo...@debian.org: Package: wnpp Severity: normal The current maintainer of avifile, Zdenek Kabelac k...@debian.org, is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: avifile Binary: avifile-xvid-plugin, avifile-mjpeg-plugin, avifile-utils, avifile-win32-plugin, avifile-mad-plugin, avifile-divx-plugin, avifile-vorbis-plugin, libavifile-0.7c2, libavifile-0.7-dev, avifile-player Version: 1:0.7.47.20070718-1.2 Priority: optional Section: libs Maintainer: Zdenek Kabelac k...@debian.org Build-Depends: debhelper (= 2.0), libqt3-mt-dev (= 3:3.1.1-2), libsdl1.2-dev, libaudiofile-dev, libjpeg62-dev, libvorbis-dev, libogg-dev, libmad0-dev, libdts-dev, libxft-dev, autoconf (= 2.13-1), automake1.9, libtool, gettext, patch, netpbm | pnmtopng, liba52-dev Architecture: any Standards-Version: 3.5.8 Format: 1.0 Directory: pool/main/a/avifile Files: 56312472d0a0826930ba9cac9ff48bea 941 avifile_0.7.47.20070718-1.2.dsc 651cbe172ac7e297f162ba440f9cde78 4406332 avifile_0.7.47.20070718-1.2.tar.gz Package: avifile Binary: avifile-xvid-plugin, avifile-mjpeg-plugin, avifile-utils, avifile-win32-plugin, avifile-mad-plugin, avifile-divx-plugin, avifile-vorbis-plugin, libavifile-0.7c2, libavifile-0.7-dev, avifile-player Version: 1:0.7.47.20070718-1.2 Priority: optional Section: libs Maintainer: Zdenek Kabelac k...@debian.org Build-Depends: debhelper (= 2.0), libqt3-mt-dev (= 3:3.1.1-2), libsdl1.2-dev, libaudiofile-dev, libjpeg62-dev, libvorbis-dev, libogg-dev, libmad0-dev, libdts-dev, libxft-dev, autoconf (= 2.13-1), automake1.9, libtool, gettext, patch, netpbm | pnmtopng, liba52-dev Architecture: any Standards-Version: 3.5.8 Format: 1.0 Directory: pool/main/a/avifile Files: 56312472d0a0826930ba9cac9ff48bea 941 avifile_0.7.47.20070718-1.2.dsc 651cbe172ac7e297f162ba440f9cde78 4406332 avifile_0.7.47.20070718-1.2.tar.gz Package: avifile-xvid-plugin Priority: optional Section: contrib/video Installed-Size: 28 Maintainer: Zdenek Kabelac k...@debian.org Architecture: amd64 Source: avifile Version: 1:0.7.47.20070718-1.2 Depends: libavifile-0.7c2 (= 1:0.7.43.20050224-1), libc6 Filename: pool/contrib/a/avifile/avifile-xvid-plugin_0.7.47.20070718-1.2_amd64.deb Size: 926 MD5sum: 79aaf1fda5b731023863decd69b53e97 SHA1: c4ae51b9624816eb3a34ad8ce3096d1d6a4da220 SHA256: ad28dc408c1057e677a60ccd171ab4870db299fba194a40266ab60ee4b0619e9 Description: XviD video encoding plugin for libavifile Plugin for encoding DivX4 video. NOTICE: This plugin requires separate installation of libxvidcore 1.0 library which is not a part of this package nor official Debian itself. See documentation for more details. In general you do not need this plugin. Tag: role::plugin Package: avifile-mjpeg-plugin Priority: optional Section: video Installed-Size: 56 Maintainer: Zdenek Kabelac k...@debian.org Architecture: amd64 Source: avifile Version: 1:0.7.47.20070718-1.2 Depends: libavifile-0.7c2 (= 1:0.7.47.20070718), libc6 (= 2.6.1-1), libgcc1 (= 1:4.2.1), libjpeg62, libstdc++6 (= 4.2.1) Filename: pool/main/a/avifile/avifile-mjpeg-plugin_0.7.47.20070718-1.2_amd64.deb Size: 11720 MD5sum: 60530aa77cc852e3c3e42439fb0dd791 SHA1: 940af0f3d60bfc86ac4b2c72bcc71238db281c46 SHA256: b2e2fd033f77120e4ba069de0a9529b9e160050a21cda7e382186f46363ac24d Description: MJPEG video plugin for libavifile This package provides a plugin for the avifile library to de/encode MJPEG video streams - this implementation is rather slower and serves just as a sample plugin implementation. Usage of ffmpeg or win32 codecs is a better choice. . In general you do not need this plugin - . Homepage: http://avifile.sourceforge.net Tag: role::plugin Package: avifile-utils Priority: extra Section: video Installed-Size: 920 Maintainer: Zdenek Kabelac k...@debian.org Architecture: amd64 Source: avifile Version: 1:0.7.47.20070718-1.2 Replaces: avifile-samples Depends: avifile-player (= 1:0.7.47.20070718), libavifile-0.7c2 (= 1:0.7.47.20070718), libc6 (= 2.6.1
Bug#440805: Unable to boot with faulty harddrive
Package: udev Version: 0.114-2 Severity: wishlist Hello I'm not sure how to mark this bug/problem - so I've used wishlist. However I would have said it's not that unimportant issue as it might be seen. So the problem goes like this - recently one of my harddrive crashed very badly - actually so bad it's been unable to read begining of some partitions - thus udev label scanning actually caused mostly endless loop (ok I've waited only for about 10 minutes... - the system was booting vry slowly - and as the permanent disk read error basicaly stoped all IDE trafic the computer was still in unusable state) I'm not sure about the solution - but maybe as soon as UDEV detects there are some problems with reading from the device - it should immediatly stop reading it (my drive has had some 2MB stripes unreadable - though I've managed to retrieve about 9/10 of data from this drive to get some of those, which where without backup) I'd to remove the faulty drive - disable udev - and put drive back and start 'the rescue' operation - unpleasent was, that many other devices were not working in this case (i.e. Wifi network) So - I'm not sure how to deal with this case - of course the drive was nearly dead - but the linux shall be able to handle such devices (hmmm even Windows could boot this machine with buggy drive without problems, but my latest unstable Debian cannot) I'll be happy to see some proposals for this - and even that buggy drive is still with me :) thus I could check potentional solutions. -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: celkem 10 lrwxrwxrwx 1 root root 20 2007-03-06 00:03 020_permissions.rules - ../permissions.rules lrwxrwxrwx 1 root root 13 2007-03-06 00:03 025_gpsd.rules - ../gpsd.rules lrwxrwxrwx 1 root root 19 2007-03-06 00:03 025_libgphoto2.rules - ../libgphoto2.rules lrwxrwxrwx 1 root root 16 2007-08-01 16:15 025_libsane.rules - ../libsane.rules lrwxrwxrwx 1 root root 22 2007-03-06 00:03 025_logitechmouse.rules - ../logitechmouse.rules lrwxrwxrwx 1 root root 16 2007-03-06 00:03 038-phantom.rules - ../phantom.rules lrwxrwxrwx 1 root root 15 2007-03-06 00:03 85-pcmcia.rules - ../pcmcia.rules lrwxrwxrwx 1 root root 13 2007-03-06 00:03 udev.rules - ../udev.rules lrwxrwxrwx 1 root root 25 2007-03-06 00:03 z20_persistent-input.rules - ../persistent-input.rules lrwxrwxrwx 1 root root 19 2007-03-06 00:03 z20_persistent.rules - ../persistent.rules -rw-r--r-- 1 root root 517 2000-01-01 00:20 z25_persistent-net.rules lrwxrwxrwx 1 root root 33 2007-03-06 00:03 z45_persistent-net-generator.rules - ../persistent-net-generator.rules lrwxrwxrwx 1 root root 12 2007-03-06 00:03 z50_run.rules - ../run.rules lrwxrwxrwx 1 root root 16 2007-03-06 00:03 z55_hotplug.rules - ../hotplug.rules lrwxrwxrwx 1 root root 19 2007-03-06 00:03 z60_alsa-utils.rules - ../alsa-utils.rules lrwxrwxrwx 1 root root 15 2007-03-06 00:03 z60_hdparm.rules - ../hdparm.rules -rw-r--r-- 1 root root 1829 2007-06-02 21:15 z60_libccid.rules lrwxrwxrwx 1 root root 20 2007-07-03 13:24 z60_xen-backend.rules - ../xen-backend.rules -rw-r--r-- 1 root root 5716 2007-06-08 19:11 z60_xserver-xorg-input-wacom.rules lrwxrwxrwx 1 root root 29 2007-03-06 00:03 z75_cd-aliases-generator.rules - ../cd-aliases-generator.rules -rw-r--r-- 1 root root 34 2007-04-27 10:53 z80-clocal.rules lrwxrwxrwx 1 root root 12 2007-08-24 11:32 z99_hal.rules - ../hal.rules -- /sys/: /sys/block/dm-0/dev /sys/block/dm-1/dev /sys/block/dm-2/dev /sys/block/dm-3/dev /sys/block/dm-4/dev /sys/block/dm-5/dev /sys/block/fd0/dev /sys/block/hda/dev /sys/block/hda/hda1/dev /sys/block/hda/hda2/dev /sys/block/hda/hda4/dev /sys/block/hda/hda5/dev /sys/block/hda/hda6/dev /sys/block/hda/hda7/dev /sys/block/hdc/dev /sys/block/hdc/hdc1/dev /sys/block/hdc/hdc2/dev /sys/block/md0/dev /sys/class/input/input0/event0/dev /sys/class/input/input1/event1/dev /sys/class/input/input2/event2/dev /sys/class/input/mice/dev /sys/class/printer/lp0/dev /sys/class/usb_device/usbdev1.1/dev /sys/class/usb_device/usbdev1.2/dev /sys/class/usb_device/usbdev2.1/dev /sys/class/usb_device/usbdev3.1/dev /sys/class/usb/lp0/dev /sys/devices/pci:00/:00:05.0/card0/adsp/dev /sys/devices/pci:00/:00:05.0/card0/audio/dev /sys/devices/pci:00/:00:05.0/card0/controlC0/dev /sys/devices/pci:00/:00:05.0/card0/dmfm/dev /sys/devices/pci:00/:00:05.0/card0/dsp/dev /sys/devices/pci:00/:00:05.0/card0/hwC0D0/dev /sys/devices/pci:00/:00:05.0/card0/mixer/dev /sys/devices/pci:00/:00:05.0/card0/pcmC0D0c/dev /sys/devices/pci:00/:00:05.0/card0/pcmC0D0p/dev /sys/devices/pci:00/:00:05.0/card0/pcmC0D1p/dev /sys/devices/pci:00/:00:05.0/card0/pcmC0D2c/dev /sys/devices/pci:00/:00:05.0/card0/pcmC0D2p/dev /sys/devices/pci:00/:00:11.2/usb1/1-0:1.0/usbdev1.1_ep81/dev /sys/devices/pci:00/:00:11.2/usb1/1-2/1-2:1.0/usbdev1.2_ep01/dev
Bug#440805: Unable to boot with faulty harddrive
2007/9/4, Marco d'Itri [EMAIL PROTECTED]: On Sep 04, Zdenek Kabelac [EMAIL PROTECTED] wrote: However I'm not sure why it reads more then one disk block (I've rebooted after it has tried 100th sector read failure and disabled udev in the /etc/init.d/) Because it needs to know which filesystem is in each partition. What a surprise :) I basically believe udev now made the system unusable in the case of this kind of crash and the question is - is everybody happy with it ? Yes Well I'm not - and my proposed solution isn't very hard to implement. Just immediately stop reading partitions - eventually whole drive when reading of the first sector fails - what's hard about implement? Also how do you want to discover the filesystem type if it fails to read the first sector - what is the point in the read continuation - is the UDEV advanced to guess filesystem type from the first 1MB of readed sectors?? BTW - I'm also the Debian developer - and I'd really like to see this issue fixed and please try to be a little bit more constructive with your next answer. Bye [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438106: avifile: FTBFS: No longer builds on amd64.
Hi How about some patch ? Would it be possible to help me with this ? thnx kabi 2007/8/15, Kurt Roeckx [EMAIL PROTECTED]: Package: avifile Version: 1:0.7.47.20070718-1.1 Severity: serious Hi, Your package is failing to build on amd64 with the following error: dh_gencontrol dpkg-gencontrol: error: current build architecture amd64 does not appear in package's list (i386 kfreebsd-i386) dh_gencontrol: command returned error code 65280 make: *** [binary-arch] Error 1 Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434372: [Pkg-samba-maint] Bug#434372: pam_smbpass.so cause segfault for 'root' user
First thanks for the hint with 'optional' - I was not an expert in pam setting - I've only seen the crash of 'su' and tried to solve it ;) As a side effect of that discussion, do you think that adding libpam-smbpass to samba-dbg would be a good idea? I did so in my test package which I pointed Zdenek to (which is useless...). Also, maybe building -dbg versions of the login and passwd packages would be a good idea, then. I happen to know the shadow package maintainer..:-) I'm not sure if especially in this case the -dbg version would have helped, but in general I guess it might be helpful for some special occasions. bye kabi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434372: pam_smbpass.so cause segfault for 'root' user
Hmm I've installed samba-dbg - but pam_smbpass.so is not there as I can see. I'm not 100% sure the complete setup of my /etc/pam.d is correct but even if not - I suppose it should not coredump and give some normal exit code right ? Is there any way how could I help with debugging - i.e. can you build some debug version of pam_smbpass.so Could I get some debug log what's going on somehow with some option ? Zdenek 2007/7/27, Christian Perrier [EMAIL PROTECTED]: Probably not that much, I'm afraid but thanks for trying. IN woder whether adding libpam-smbpass to the samba-dbg package could help. Anyway, I can reproduce that bug. Well, after some trial and error (using an unstripped pam_smbpass.so file), I got no result. Steve, can you look at this bug? I can send you (privately) my unstripped pam_smbpass.so file -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGqZCA1OXtrMAUPS0RAnAKAJ4+GOZOIJMpHpm3MAd4vHPYoQwmCQCghjGt xJ+Ix7SxmQ22tbH36q5husU= =a1QJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434372: pam_smbpass.so cause segfault for 'root' user
Package: libpam-smbpass Version: 3.0.25b-1+b1 Severity: normal Hello On my system I'm using this line in my common-auth pam module: authoptionalpam_smbpass.so migrate and when I try tu use 'su' command to become root and I do not insert correct root password - then su cause segfaul (with correct password - there are no problems) I'm adding gdb output - though I'm not sure how usable this could be. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1210750080 (LWP 5526)] 0xb7dcaf5b in strlen () from /lib/libc.so.6 (gdb) bt #0 0xb7dcaf5b in strlen () from /lib/libc.so.6 #1 0xb7dbd0b8 in fputs_unlocked () from /lib/libc.so.6 #2 0xb7e2a178 in __vsyslog_chk () from /lib/libc.so.6 #3 0xb7e2a68a in syslog () from /lib/libc.so.6 #4 0x0804c522 in ?? () #5 0x0005 in ?? () #6 0x0804db99 in ?? () #7 0x0804e520 in ?? () #8 0x08050520 in ?? () #9 0xb7edb2a0 in ?? () #10 0xb7e9dff4 in ?? () from /lib/libc.so.6 #11 0xb7e9f120 in ?? () from /lib/libc.so.6 #12 0x08056448 in ?? () #13 0xbfd2fc28 in ?? () #14 0xb7dc7e90 in free () from /lib/libc.so.6 #15 0x08049afa in ?? () #16 0x0805389d in ?? () #17 0x in ?? () (gdb) q -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.20.1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages libpam-smbpass depends on: ii libc6 2.6-2GNU C Library: Shared libraries ii libcomerr2 1.40.2-1 common error description library ii libkrb531.6.dfsg.1-6 MIT Kerberos runtime libraries ii libldap22.1.30-13.4 OpenLDAP libraries ii libpam0g0.79-4 Pluggable Authentication Modules l ii samba-common3.0.25b-1+b1 Samba common files used by both th libpam-smbpass recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392745: Missing /usr/lib/X11/locale/common/xiiimp.so.2
Package: libx11-6 Version: 2:1.0.3-1 Followup-For: Bug #392745 Hi The latest update of Xorg result of failing opening of input method in most localized programs. The library /usr/lib/X11/locale/common/xiiimp.so.2 cannot be opened. Also I assume it causes some delays in program startup. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc5 Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2) Versions of packages libx11-6 depends on: ii libc62.3.6.ds1-6 GNU C Library: Shared libraries ii libx11-data 2:1.0.3-1 X11 client-side library ii libxau6 1:1.0.1-2 X11 authorisation library ii libxdmcp61:1.0.1-2 X11 Display Manager Control Protoc ii x11-common 1:7.1.0-3 X Window System (X.Org) infrastruc libx11-6 recommends no packages. -- debconf information: libx11-6/migrate_xkb_dir: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#206467: libavcodec powerpc
On Thu, Apr 14, 2005 at 12:36:56PM -0700, [EMAIL PROTECTED] wrote: Anyone working on avifile on powerpc - or building against ffmpeg packages in Debian? I just tried building avifile from CVS on powerpc got the attached error - though libavcodec-dev is already available in Debian - Well the basic problem is - that each new version of libavcodec has slightly different API then the previous or next version. Thus for now the only usable solution for now is to keep the version within libavifile project - as the API has to be adapted over and over. Many thanks for your work on free AV tools! Well I guess this will be some simple problem with some missing header - I've not tried to build avifile on PPC for a long time - and noone is really working on this AFAIK (well you know the famous mplayer I guess ;) thus why anyone should bother with aviplay) I'm just keeping it working on i386 and from time to time I fix/add some bug/feature which I see usefull for me :) If you want to make it compilable on PPC - either you will have to help with you knowledge - or give me a temporal SSH account on a machine which could compile avifile (contains needed packages for this) -- .''`. Litigation: The Business Model of the Future! (TM) : :' :http://www.microsoft.com/mscorp/ip/tech/fat.asp `. `'Zdenek Kabelac [EMAIL PROTECTED], users.sf.net, fi.muni.cz} `- Debian GNU/Linux maintainer - www.debian.{org,cz} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#206467: build against libavcodec-dev libavformat-dev
On Thu, Apr 14, 2005 at 11:14:17PM -0700, [EMAIL PROTECTED] wrote: I built avifile on powerpc against libavcodec-dev libavformat-dev with only a few changes - see attached patch I'm scarcely familiar with gnu maketools, but it works : ) Ok I may try to add configure option for this to use external ffmpeg library - however the usability of such solution is really limited by the stability off ffmpeg API - (meassurable in months ;)) -- .''`. Litigation: The Business Model of the Future! (TM) : :' :http://www.microsoft.com/mscorp/ip/tech/fat.asp `. `'Zdenek Kabelac [EMAIL PROTECTED], users.sf.net, fi.muni.cz} `- Debian GNU/Linux maintainer - www.debian.{org,cz} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300179: avifile: FTBFS (amd64/gcc-4.0): array type has incomplete element type
@@ -1813,6 +1813,14 @@ #define FF_OPT_MAX_DEPTH 10 } AVOption; +#ifdef HAVE_MMX +extern const struct AVOption avoptions_common[3 + 5]; +#else +extern const struct AVOption avoptions_common[3]; +#endif +extern const struct AVOption avoptions_workaround_bug[11]; + I understand this one - (moreover it's been removed from original ffmpeg source - howver this will require I'll add options into my code :( -#ifndef HAVE_LRINTF -/* XXX: add ISOC specific test to avoid specific BSD testing. */ -/* better than nothing implementation. */ -/* btw, rintf() is existing on fbsd too -- alex */ -static always_inline long int lrintf(float x) -{ -#ifdef CONFIG_WIN32 -# ifdef ARCH_X86 -int32_t i; -asm volatile( -fistpl %0\n\t -: =m (i) : t (x) : st -); -return i; -# else -/* XXX: incorrect, but make it compile */ -return (int)(x + (x 0 ? -0.5 : 0.5)); -# endif -#else -return (int)(rint(x)); -#endif -} -#else -#ifndef _ISOC9X_SOURCE -#define _ISOC9X_SOURCE -#endif #include math.h -#endif What's wrong with this one ??? +#define MAX_BUFFER_TIME 1.0; + class AudioQueue { public: -static const double MAX_BUFFER_TIME = 1.0; Wow - gcc-4.0 does not support const doubles - that would be something new to me Are you sure about this ? -static const float m_fDropLimit = -0.015; - static const int PRIORITY_ADD_AUDIO = 0; +static const float m_fDropLimit = -0.015; What's wrong with class static variables in gcc-4.0 ?? -avm::IReadFile* avm::CreateReadFile(const char* name, unsigned int flags) +IReadFile* CreateReadFile(const char* name, unsigned int flags) ok if (set_base != NULL) - fbuf.base = (void*)((unsigned int)set_base+(unsigned int)shift); + fbuf.base = (void*)((unsigned long)set_base+(unsigned long)shift); ok - though I've used (char*) type instead of (unsigned long) avml(AVML_WARN, - v4l1: can not allocate frame buffer base: 0x%x\n,(int)base); + v4l1: can not allocate frame buffer base: 0x%lx\n,(long)base); Ok - using %p for priting pointer Please explain me what's wrong with const doubles so you have replaced them with macros (which aren't obviously vissible in debugger) -- .''`. Litigation: The Business Model of the Future! (TM) : :' :http://www.microsoft.com/mscorp/ip/tech/fat.asp `. `'Zdenek Kabelac [EMAIL PROTECTED], users.sf.net, fi.muni.cz} `- Debian GNU/Linux maintainer - www.debian.{org,cz} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300179: avifile: FTBFS (amd64/gcc-4.0): array type has incomplete element type
+ class AudioQueue { public: -static const double MAX_BUFFER_TIME = 1.0; Ok - there is really something seriously wrong with gcc-4.0 so I've applied this patch - if you have some spare free time you may try to check if CVS version for now compiles on your box. -- .''`. Litigation: The Business Model of the Future! (TM) : :' :http://www.microsoft.com/mscorp/ip/tech/fat.asp `. `'Zdenek Kabelac [EMAIL PROTECTED], users.sf.net, fi.muni.cz} `- Debian GNU/Linux maintainer - www.debian.{org,cz} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#260808: reopening bug
On Fri, Feb 25, 2005 at 07:12:45PM -0800, Erich Schubert wrote: reopen 260808 thanks Reopening this bug report. You must not close bugs in changelogs if you did not *change* anything. Please handle this bug report correclty. w I see you are some 'bug search' fanatic - Obviously you haven't read any folowing responces to this bugreport - you MUST know that crash of Xserver is crash of Xserver - and not fault of a player using Xserver (as these are two different processes in a system) as this bug is almost 2 years old and from that time the Xserver has been updated several times (and myself I'm already using Xorg server as it's faster and has less amount of bugs on my laptop i855 (especially in XV part...) Surelly I could reassing this bug to Xserver package, but hardly doubt that maintainer of this package ever reads this horribly long list of bug reports. The other solution is to close this bug - as noone is able to reproduce it - so obviously it has got fixed over the time. Most probably by updates in XV driver - and this is what I propose The bug is unrelated to aviplay - I do not want to see it on my bug list - and I'm mostly 99% sure it's been fixed from that time in Xserver. So it's up to you - either reasing it - or close it with this knowledge... -- .''`. Litigation: The Business Model of the Future! (TM) : :' :http://www.microsoft.com/mscorp/ip/tech/fat.asp `. `'Zdenek Kabelac [EMAIL PROTECTED], users.sf.net, fi.muni.cz} `- Debian GNU/Linux maintainer - www.debian.{org,cz} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295486: libavifile-0.7c102: depends on unavailable libxvidcore4
On Tue, Feb 15, 2005 at 10:39:43PM -0500, Aaron M. Ucko wrote: Package: libavifile-0.7c102 Version: 1:0.7.38.20030710-1.2 Severity: grave Justification: renders package unusable The following packages have unmet dependencies: libavifile-0.7c102: Depends: libxvidcore4 (= 1:1.0.0-0.0) which is a virtual package. This library is not (and cannot be?) available in the main archive; please properly isolate its use to avifile-xvid-plugin. yep - will be fixed soon... -- .''`. Litigation: The Business Model of the Future! (TM) : :' :http://www.microsoft.com/mscorp/ip/tech/fat.asp `. `'Zdenek Kabelac [EMAIL PROTECTED], users.sf.net, fi.muni.cz} `- Debian GNU/Linux maintainer - www.debian.{org,cz} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]