Bug#706822: default behavior of setting ulimit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: apache2.2-common Version: 2.2.22-13 Severity: wishlist Hello folks, during the apache2 upgrade from squeeze to wheezy I got the following message: usr/sbin/apache2ctl: line 87: ulimit: open files: cannot modify limit: Operation not permitted. This happens because the environment of this server does not allow to set a ulimit (it is a virtualized server). Because there are many vserver-hosts out there and since the message apparently shows up on every apache2 restart, I think the default behavior should be changed to not set the ulimit by default. My temporary dirty workaround is to change /etc/apache2/envvars to APACHE_ULIMIT_MAX_FILES='sleep 0.01' Regards, Kiro -BEGIN PGP SIGNATURE- Version: GnuPG (GNU/Linux) iEYEARECAAYFAlGGLGIACgkQYWOj0axvMcVpwwCdEYFHWezoKuKlRByrsXuzgKyG 40sAn0J/veXebbST4UkW2hPpnLmHHhyG =CnqP -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706822: default behavior of setting ulimit
Hi Arno, meanwhile the problem is now here documented, please feel free to close this bug. ;-) Thanks, Kiro signature.asc Description: This is a digitally signed message part.
Bug#574604: [tuxonice-userui] initramfs generated initrd misses tuxonice-userui
Package: tuxonice-userui
Version: 1.0-1
Severity: normal
Hello,
if the actual running kernel has no tuxonice-support and the kernel for
which the initrd should be generated has tuxonice static compiled in
(not as a module!) then the tuxonice-userui is not assembled into the
initrd.
As solution I suggest to drop the tuxonice detection in file
/usr/share/initramfs-tools/hooks/tuxonice_userui .
This should not harm any setup, because on boot just nothing happens if
the kernel has no tuxonice support.
The first part of the detection is wrong anyways, running a
tuxonice-capable kernel doesnt mean the new one is also capable.
regards, Kiro
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.31-amd64
--- tuxonice_userui_old 2010-03-19 11:25:05.0 +0100
+++ tuxonice_userui 2010-03-19 11:32:41.0 +0100
@@ -17,20 +17,6 @@
. /usr/share/initramfs-tools/hook-functions
-TUXONICE_ENABLED=/sys/power/tuxonice/user_interface/enabled
-
-# Don't do anything if the kernel does not support tuxonice_userui,
-# nor the module is there
-if [ -f ${TUXONICE_ENABLED} ]; then
-if [ `cat ${TUXONICE_ENABLED}` = 0 ]; then
- echo TuxOnIce user interface is disabled, skipping...
- exit 0
-fi
-elif [ ! -f ${MODULESDIR}/kernel/power/tuxonice_userui.ko ]; then
-echo This kernel does not seem to support TuxOnIce user interface, skipping...
-exit 0
-fi
-
# Add the module and its dependencies and load it automatically if it
# exists
force_load tuxonice_userui
signature.asc
Description: This is a digitally signed message part.
Bug#509257: [pcmanfm] depends on gamin
Package: pcmanfm Version: 0.5-3 Severity: normal Hello, pacmanfm depends on gamin, which is a subset of fam - instead it should depend on libgamin0|libfam0 like many other applications do. This would allow people to install lxde next to applications which need fam... Thank you, Kiro signature.asc Description: This is a digitally signed message part.
Bug#496178: [gdm] GraphicalTheme=sometheme in gdm.conf causes crash
Package: gdm Version: 2.20.7-1 I had the same problem (gdm crash after update) while using the graphical greeter. The issue seems to be caused by using the themes circles, happygnome and happygnome-list from the gdm package as well as with the industrial theme from the gdm-themes package. An easy workaround is to delete the line GraphicalTheme=xxx from the /etc/gdm/gdm.conf file, and then choose another theme... Regards, Kiro signature.asc Description: This is a digitally signed message part.
Bug#469221: python2.4 / db4.5 / apt-listchanges
I welcome all lenny users to the playground of vanity :-( http://packages.qa.debian.org/p/python2.4/news/20080322T223922Z.html diff -uNr python2.4-2.4.5/debian/changelog python2.4-2.4.5_old/debian/changelog --- python2.4-2.4.5/debian/changelog 2008-03-25 13:36:30.0 +0100 +++ python2.4-2.4.5_old/debian/changelog 2008-03-25 13:30:24.0 +0100 @@ -1,9 +1,3 @@ -python2.4 (2.4.5-1.1) unstable; urgency=high - - * Leave a note about #469221 #469342 #469634 and #471066 (no fix). - - -- Kiro Zimmer [EMAIL PROTECTED] Tue, 25 Mar 2008 13:31:31 +0100 - python2.4 (2.4.5-1) unstable; urgency=low * Python 2.4.5 release. diff -uNr python2.4-2.4.5/debian/NEWS python2.4-2.4.5_old/debian/NEWS --- python2.4-2.4.5/debian/NEWS 2008-03-25 13:33:15.0 +0100 +++ python2.4-2.4.5_old/debian/NEWS 1970-01-01 01:00:00.0 +0100 @@ -1,16 +0,0 @@ -python2.4 (2.4.5-1.1) unstable; urgency=high - - * WARNING! Upgrading this package will break some other packages -caused by backwards-incompatibility between db4.6 and db4.5. -. -affected packages: - apt-listchanges - - spambayes - - probably all packages which uses libdb -. -If you are already in this situation (you shouldnt see this note :-) -then a manual workaround can be found here: -http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=32;bug=469342 -. -see #469221 #469342 #469634 #471066 for more information. - - -- Kiro Zimmer [EMAIL PROTECTED] Tue, 25 Mar 2008 13:31:31 +0100 signature.asc Description: This is a digitally signed message part.
Bug#434308: fireflier-server: missing executable
Package: fireflier-server Version: 1.1.7-2 Severity: grave Hello, the binary /usr/sbin/fireflierd is missing, so that the package is not very usefull. ;-) Regards, Kiro signature.asc Description: This is a digitally signed message part.
Bug#429230: module-init-tools: do not delete /etc/modules
Hello Marco, just for the records: I think your procedure is wrong, because /etc/modules could have existed before m-i-t was installed. You check this during postinst, and leave the file as it is, which is recommended in chapter E2 of the debian policy. So far so good. But later during postrm the package nevertheless deletes the file, even if the file existed before. For this case I cant find a really relevant policy statement. Is there no general behavior prescribed? I prefer not to delete the file. a last question: If the file neither belongs to the package, nor is a conffile of that package, how can I be sure, to which package the file belongs? With your argumentation any package (for example yaird, ... ) could remove the file, just because the package thinks the file belongs to it!? Regards, Kiro signature.asc Description: This is a digitally signed message part.
Bug#431022: gdm: second login not possible for same user (gdmflexiserver)
retitle 431022 gdm: allow multiple logins by default (again) severity 431022 wishlist Hello, please add AlwaysLoginCurrentSession=false to the default gdm.conf. Or maybe leave a note in the debian/changelog that something changed. Sven Arvidsson wrote: This works for me. Are you sure multiple logins isn't disabled in gdmsetup? I think the option for this is new in 2.18. Thank you, that was the reason! ;-) But there were no changes made in gdm.conf, meanwhile the behavior changed from allow to forbid... Regards, Kiro signature.asc Description: This is a digitally signed message part.
Bug#431022: gdm: second login not possible for same user (gdmflexiserver)
Package: gdm Version: 2.18.2-1 Severity: important Hello! A user who is already logged in via gdm, can not login on a second session (anymore) with gdm. But for another user it is no problem. steps to reproduce: - start gdm, do a normal login - start another loginscreen (gdmflexiserver or use menu) - try to login as the SAME user - no login possible as the SAME user - but trying ANOTHER user is possible It is definitely a gdm problem, because normally it would ask after the password You are already logged in. Do you realy want to login? (my translation, I use german locale) Another interesting fact is that it depends if you are logged in on the first terminal an a physical way. Lets change the steps above: - start gdm, do a normal login as USER A - start a nested gdm, login as USER B (gdmflexiserver -n) - start another loginscreen (gdmflexiserver or menu) - try to login as USER B - the second login is possible, because the first was nested :-) Hope that helps to find the bug. Regards, Kiro - but for another user it is possible - not --- Package information. --- Depends (Version) | Installed ==-+-=== libart-2.0-2 (= 2.3.18) | 2.3.19-3 libatk1.0-0(= 1.13.2) | 1.18.0-2 libattr1 (= 2.4.4-1) | 1:2.4.32-1.1 libc6 (= 2.5-5) | 2.5-11 libcairo2 (= 1.4.0) | 1.4.8-1 libdbus-1-3 (= 0.94) | 1.1.1-3 libdbus-glib-1-2 (= 0.73) | 0.73-2 libdmx1| 1:1.0.2-2 libfontconfig1 (= 2.4.0) | 2.4.2-1.2 libglade2-0 (= 1:2.5.1) | 1:2.6.1-1 libglib2.0-0 (= 2.12.9) | 2.12.12-1 libgnomecanvas2-0 (= 2.11.1) | 2.14.0-3 libgtk2.0-0(= 2.10.3) | 2.10.13-1 libpam0g (= 0.76) | 0.79-4 libpango1.0-0 (= 1.16.4) | 1.16.4-1 libpopt0 (= 1.10) | 1.10-3 librsvg2-2 (= 2.16.1) | 2.16.1-2 libselinux1(= 2.0.15) | 2.0.15-2 libwrap0 | 7.6.dbs-13 libx11-6 | 2:1.1.2-1 libxau6| 1:1.0.3-2 libxcursor1 ( 1.1.2) | 1:1.1.8-2 libxdmcp6 | 1:1.0.2-2 libxext6 | 1:1.0.3-2 libxfixes3(= 1:4.0.1) | 1:4.0.3-2 libxi6 | 1:1.0.1-4 libxinerama1 | 1:1.0.2-1 libxml2(= 2.6.28) | 2.6.29.dfsg-1 libxrandr2(= 2:1.2.0) | 2:1.2.1-1 libxrender1| 1:0.9.2-1 debconf (= 0.5) | 1.5.13 OR debconf-2.0| adduser| 3.103 debconf (= 0.5) | 1.5.13 OR debconf-2.0| libpam-modules (= 0.72-1) | 0.79-4 libpam-runtime (= 0.76-13.1) | 0.79-4 gnome-session | 2.18.2-1 OR xterm | 226-1 OR x-window-manager | OR x-terminal-emulator| xbase-clients | 1:7.2.ds2-2 gksu(= 1.0.7) | 2.0.0-4 lsb-base (= 3.0-10) | 3.1-23.1 librsvg2-common| 2.16.1-2 signature.asc Description: This is a digitally signed message part.
Bug#428650: solved by hand - addition
Mike Hommey wrote: I could solve the problem by hand with a simpler procedure: rm /usr/share/man/man5/modules.5.gz apt-get -f install Then you have to install all forthcoming versions of module-init-tools with force, because there are the older entrys in the dpkg database /var/lib/dpkg/diversions left... Kiro signature.asc Description: This is a digitally signed message part.
Bug#428650: solved by hand - addition
Hello, maybe we should make a backup of /etc/modules bevore purging module-init-tools, and restore it afterwards. :-) (#429230) cp /etc/modules /etc/modules.backup_module-init-tools dpkg -P --force-all module-init-tools dpkg-divert --remove /usr/share/man/man5/modules.5.gz dpkg-divert --remove /usr/share/man/fr/man5/modules.5.gz rm /usr/share/man/man5/modules.5.gz rm /usr/share/man/man5/modules.modutils.5.gz rm /usr/share/man/fr/man5/modules.5.gz rm /usr/share/man/fr/man5/modules.modutils.5.gz apt-get install module-init-tools mv /etc/modules.backup_module-init-tools /etc/modules Regards, Kiro signature.asc Description: This is a digitally signed message part.
Bug#429230: module-init-tools: do not delete /etc/modules
Package: module-init-tools Severity: serious Hello, please do not delete /etc/modules on purging (postrm) the package. Otherwise mark it at least as a conffile. I know this happens very rarely on a normal systems, but it happens :-) (see #428650 why this happened on my, and maybe many more systems) Regards, Kiro signature.asc Description: This is a digitally signed message part.
Bug#428650: solved by hand
Package: module-init-tools Version: 3.3-pre11-3 I solved the problem by hand, which works for me. dpkg -P --force-all module-init-tools dpkg-divert --remove /usr/share/man/man5/modules.5.gz dpkg-divert --remove /usr/share/man/fr/man5/modules.5.gz rm /usr/share/man/man5/modules.5.gz rm /usr/share/man/man5/modules.modutils.5.gz rm /usr/share/man/fr/man5/modules.5.gz rm /usr/share/man/fr/man5/modules.modutils.5.gz apt-get install module-init-tools Regards, Kiro signature.asc Description: This is a digitally signed message part.
Bug#425693: Conflicts: nvidia-kernel-legacy-71xx-source
Package: nvidia-kernel-legacy-96xx-source Severity: minor Hello, please remove Conflicts: nvidia-kernel-legacy-71xx-source in nvidia-kernel-legacy-96xx-source and the other way round. The goal is to build the two different nvidia-kernel-legacy modules on one machine for the same kernel running later on different machines. Thank You. Kiro signature.asc Description: This is a digitally signed message part.
Bug#420002: bootsplash: initramfs-tools hook needs full path for /usr/sbin/splash
Package: bootsplash Version: 3.3-6 Severity: important Tags: patch Hello, generating of initrd-images using bootsplash with recent initramfs-tools does not work anymore, so please apply the appended patch, or reassign this bug to initramfs-tools if they should give a working environment again. Thanks, Kiro === $ dpkg -l initramfs* | grep ^ii ii initramfs-tools 0.87b tools for generating an initramfs $ update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-2.6.20 /usr/share/initramfs-tools/hooks/bootsplash: line 51: splash: command not found W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. --- System information. --- Architecture: i386 Kernel: Linux 2.6.20 Debian Release: lenny/sid 990 unstablewww.debian-multimedia.org 990 unstableftp.de.debian.org --- Package information. --- Depends(Version) | Installed -+-= libc6 (= 2.3.6-6) | 2.5-2 libfreetype6(= 2.2) | 2.2.1-5 libmng1 (= 1.0.3-1) | 1.0.9-1 zlib1g (= 1:1.2.1) | 1:1.2.3-13 debconf(= 0.5) | 1.5.13 OR debconf-2.0 | bootsplash-theme-debian | OR bootsplash-theme | initramfs-tools | 0.87b --- ./debian/patches/initramfs.dpatch.old 2007-04-19 13:00:29.0 +0200 +++ ./debian/patches/initramfs.dpatch 2007-04-19 13:01:04.0 +0200 @@ -59,4 +59,4 @@ + exit 0 +fi + -+splash -s -f $SPLASH_FILE $DESTDIR/bootsplash ++/usr/sbin/splash -s -f $SPLASH_FILE $DESTDIR/bootsplash pgpwwNnF6pGXz.pgp Description: PGP signature
Bug#403362: totem-mozilla: dont register mediatypes which cant be played
Package: totem-mozilla Version: 2.16.4-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello. Neither totem-xine nor totem-gstreamer are able to play the embedded streams on (at least) the famous german website www.tagesschau.de/video . Please remove the subscription for the embedded asx/wmv files, so that other plugins like mplayer-mozilla can handle it. See #403296 for previous dicussion.. Feel free to reassign this bug to either totem-xine and/or totem-gstreamer. Thank You, Kiro - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages totem-mozilla depends on: ii dbus 1.0.2-1simple interprocess messaging syst ii totem-gstreamer 2.16.4-2 A simple media player for the Gnom Versions of packages totem-mozilla recommends: ii dillo [www-browser]0.8.5-4.1 Small and fast web browser ii epiphany-browser [www- 2.14.3-3 Intuitive GNOME web browser ii iceape-browser [www-br 1.0.6-1 The Iceape Internet browser ii iceweasel [www-browser 2.0+dfsg-1lightweight web browser based on M ii konqueror [www-browser 4:3.5.5a.dfsg.1-3 KDE's advanced file manager, web b ii links2 [www-browser] 2.1pre26-4Web browser running in both graphi ii lynx [www-browser] 2.8.5-2sarge2.2 Text-mode WWW Browser ii opera [www-browser]9.02-20060919.6 The Opera Web Browser - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhBbKYWOj0axvMcURAvySAJ9ymnULlkyxTNDYcilTxzj6Y53x1wCgyaKf WtIRwSUTtzFOacE06CmH80k= =n4/y -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403296: gnome: please dont depend on totem-mozilla, use recommend instead
Package: gnome Version: 1:2.14.3.3 Severity: normal Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello! At First: Yes I know this is no real bug for the gnome metapackage, but its easy for the maintainers of gnome to solve this issue. ;-) Ive installed gnome, but this is not my standard desktop-environment. To play videos in firefox/iceweasel I want to use mozilla-mlayer. But because gnome is installed and it depends on totem-mozilla, the mozilla-mplayer plugin is not usable anymore, because totem-mozilla is now the default player for most mediatypes. Maybe this depends on the order in which the plugins are installed, but this order gets ramdomized the next time one plugin is replaced by a newer version. The simplest solution would be to replace the Depends:totem-mozilla with a Recommends or Suggests... Thanks, Kiro Versions of packages gnome depends on: ii totem-mozilla 2.16.4-2 Totem Mozilla plugin gnome recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFgzPqYWOj0axvMcURAtjpAJ4jmVHe/hzF6nLJlxeFx0LRi8aTlQCgoWcm 2H+9RzuUZnSLe638EzACcuw= =gKn8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401841: mount: -o remount,commit=value does strange things
Package: mount Version: 2.12r-15 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, at first this may be an error of loop-aes-utils... $ LANG=C dpkg -S /bin/mount diversion by loop-aes-utils from: /bin/mount diversion by loop-aes-utils to: /bin/mount.orig mount, loop-aes-utils: /bin/mount $ COLUMNS=80 dpkg -l | grep loop-aes-utils ii loop-aes-utils 2.12r-14 Tools for mounting and manipulating filesyst Let me describe the behavior with an example: $ grep hda7 /etc/fstab LABEL=WD300_SOURCE /mnt/hda7 ext3,ext2 defaults 0 3 $ mount /mnt/hda7 $ mount | grep hda7 /dev/hda7 on /mnt/hda7 type ext3 (rw) so far, so good... $ mount /dev/hda7 -o remount,commit=3600 $ mount | grep hda7 /dev/hda7 on /mnt/hda7 type ext3 (rw,commit=3600) $ mount /dev/hda7 -o remount,commit=7200 $ mount | grep hda7 /dev/hda7 on /mnt/hda7 type ext3 (rw,commit=3600,commit=7200) $ mount /dev/hda7 -o remount,commit=3600 $ mount | grep hda7 /dev/hda7 on /mnt/hda7 type ext3 (rw,commit=3600,commit=7200,commit=3600) ... to be contiuned Why are there different commit times? This goes endless until I use the mount-point instead of the device: $ mount /mnt/hda7 -o remount,commit=3600 $ mount | grep hda7 /dev/hda7 on /mnt/hda7 type ext3 (rw,commit=3600) This would be a usable workaround for this problem, but it does not work on devicemapper-devices like /dev/mapper/_dev_hda9 created by libpam_mount. The only solution is there to unmount the device and mount it again, which mean to logout and to relogin - because it is the home-direcory. The problem in the first example is also avoidable, if /etc/fstab is changed to the normal entry (without the LABEL) like this: $ grep hda7 /etc/fstab /dev/hda6 /mnt/hda7 ext3,ext2 defaults 0 3 But in the case with libpam_mount, there is neither a label used nor is there an entry in /etc/fstab. $ grep home /etc/security/pam_mount.conf volume * crypt - /home/.img ~ loop,exec,nodev,nosuid,cipher=aes-cbc-essiv:sha256,hash=sha512,keysize=256 aes-256-ecb /mnt/usb/.key How can this issue be solved? Thank You for reading this ;-) Kiro - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages mount depends on: ii libblkid 1.39+1.40-WIP-2006.11.14+dfsg-1 block device id library ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-1 universally unique id library mount recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFdqIfYWOj0axvMcURAkDeAKDR6AYbwEsv3VDJiZHKEMr5Jqh4WACeN6HZ D0e99JCw0YaIi/ddqiqkRVY= =iDX6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395297: gpsd: be more quiet on bootup
Package: gpsd Version: 2.33-4 Severity: minor Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, please avoid the colorful warning messages, on startup when START_DAEMON is set to false. Since during install the user gets prompted, if he wants to automatically start the daemon, he shouldnt be warned on every startup and shutdown again. Thanks, Kiro. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFQHBSYWOj0axvMcURArsbAKC4BFko8m6ljoLyvoSP6CAob6q0QwCfX+Or KjfiNtlY8rABnqEnCpJ3hOE= =W3q5 -END PGP SIGNATURE- diff -uNr gpsd-2.33_orig/debian/gpsd.init gpsd-2.33/debian/gpsd.init --- gpsd-2.33_orig/debian/gpsd.init 2006-10-26 09:33:44.0 +0200 +++ gpsd-2.33/debian/gpsd.init 2006-10-26 09:57:06.0 +0200 @@ -41,8 +41,7 @@ log_end_msg 0 \ || log_end_msg 1 else - log_warning_msg gpsd is configured not to start automatically at boot time. - log_warning_msg To change this, run 'dpkg-reconfigure gpsd'. + log_daemon_msg Not starting $DESC gpsd log_end_msg 0 fi ;; stop) @@ -52,8 +51,7 @@ log_end_msg 0 [ -n $WARN ] log_warning_msg $WARN else - log_warning_msg gpsd is configured not to start automatically at boot time. - log_warning_msg To change this, run 'dpkg-reconfigure gpsd'. + log_daemon_msg Not stopping $DESC gpsd log_end_msg 0 fi ;; reload|force-reload)
Bug#383877: bluez-utils: temporary solution for d-bus pin helpers
Package: bluez-utils Version: 3.1 Tags: patch Hello, even if bluez-passkey-gnome entered sid yesterday, I think the best solution should be a working kdebluetooth/kbluepin framework. The appended patch, found at http://www.kmobiletools.org/node/228 should solve the problem. Since there semms to be no better solution bevore kde4 hits debian, I think you should apply the patch, so that bluetooth is usable in kde again... just my 2 cents Kiro bluez-pin-exec-patch.diff.bz2 Description: BZip2 compressed data
Bug#365487: unionfs-source: fails to build with make_kpkg
Package: unionfs-source
Version: 1.1.4+20060417.0541+debian-2
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hello,
make_kpkg fails, because the source files are removed, bevore the modules are
build :)
consult the logfile for details. the attached patch solved the problem for me.
thanks kiro
- -- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages unionfs-source depends on:
ii bzip2 1.0.3-2high-quality block-sorting file co
ii debhelper 5.0.34 helper programs for debian/rules
ii dpatch2.0.19 patch maintenance system for Debia
ii module-assistant 0.10.3 tool to make module package creati
Versions of packages unionfs-source recommends:
ii unionfs-too 1.1.4+20060417.0541+debian-2 Tools to manage unionfs filesystem
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEVLVwYWOj0axvMcURAiXqAJ94mo/2Y+UuXEkQaLy3Zq8UOm3TKgCgoqrm
bF0BhjY0MPh3DgpUhfiQbcI=
=1mEf
-END PGP SIGNATURE-
--- /usr/src/modules/unionfs/debian/rules_old 2006-04-30 14:48:31.0
+0200
+++ /usr/src/modules/unionfs/debian/rules 2006-04-30 14:49:03.0
+0200
@@ -206,7 +206,6 @@
rm -f build-arch-stamp build-indep-stamp configure-stamp
-$(MAKE) clean
- rm -rf linux-2.6
-mv Makefile.upstream Makefile
dh_clean
[EMAIL PROTECTED]:/usr/src/linux-2.6.16.11$ fakeroot make-kpkg modules_image
exec debian/rules DEBIAN_REVISION=kiro1 modules_image
[...]
make[1]: Entering directory `/usr/src/modules/unionfs'
/usr/bin/make -w -f debian/rules kdist_clean kdist_config binary-modules
make[2]: Entering directory `/usr/src/modules/unionfs'
dh_testdir
#dh_testroot
rm -f build-arch-stamp build-indep-stamp configure-stamp
/usr/bin/make clean
make[3]: Entering directory `/usr/src/modules/unionfs'
find . \( -name '*.ko' -o -name '*.o' -o -name '.tmp_versions' -o -name '*~' -o
-name '.*.cmd' \
-o -name '*.mod.c' -o -name '*.tar.bz2' -o -name '*.rej' -o
-name '*.orig' \)\
-print | xargs rm -Rf
make[3]: Leaving directory `/usr/src/modules/unionfs'
rm -rf linux-2.6
mv Makefile.upstream Makefile
mv: Aufruf von stat für »Makefile.upstream« nicht möglich: Datei oder
Verzeichnis nicht gefunden
make[2]: [clean] Fehler 1 (ignoriert)
dh_clean
/usr/bin/make -w -f debian/rules clean
make[3]: Entering directory `/usr/src/modules/unionfs'
dh_testdir
#dh_testroot
rm -f build-arch-stamp build-indep-stamp configure-stamp
/usr/bin/make clean
make[4]: Entering directory `/usr/src/modules/unionfs'
find . \( -name '*.ko' -o -name '*.o' -o -name '.tmp_versions' -o -name '*~' -o
-name '.*.cmd' \
-o -name '*.mod.c' -o -name '*.tar.bz2' -o -name '*.rej' -o
-name '*.orig' \)\
-print | xargs rm -Rf
make[4]: Leaving directory `/usr/src/modules/unionfs'
rm -rf linux-2.6
mv Makefile.upstream Makefile
mv: Aufruf von stat für »Makefile.upstream« nicht möglich: Datei oder
Verzeichnis nicht gefunden
make[3]: [clean] Fehler 1 (ignoriert)
dh_clean
make[3]: Leaving directory `/usr/src/modules/unionfs'
/usr/bin/gcc-4.0
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.16.11/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modules.in}.backup 2/dev/null || true; \
sed -e 's/##KVERS##/2.6.16.11/g ;s/#KVERS#/2.6.16.11/g ;
s/_KVERS_/2.6.16.11/g ; s/##KDREV##/kiro1/g ; s/#KDREV#/kiro1/g ;
s/_KDREV_/kiro1/g' $templ ${templ%.modules.in}; \
done
dh_testroot
dh_clean -k
dh_installdirs
/usr/bin/make KDIR=/usr/src/linux-2.6.16.11 KVER=2.6.16.11
make[3]: Entering directory `/usr/src/modules/unionfs'
make -C /usr/src/linux-2.6.16.11 SUBDIRS=`pwd`/linux-2.6 CONFIG_UNION_FS=m
CC=gcc modules
make[4]: Entering directory `/usr/src/linux-2.6.16.11'
scripts/Makefile.build:15: /usr/src/modules/unionfs/linux-2.6/Makefile: Datei
oder Verzeichnis nicht gefunden
make[5]: *** Keine Regel, um »/usr/src/modules/unionfs/linux-2.6/Makefile« zu
erstellen. Schluss.
make[4]: *** [_module_/usr/src/modules/unionfs/linux-2.6] Fehler 2
make[4]: Leaving directory `/usr/src/linux-2.6.16.11'
make[3]: *** [modules] Fehler 2
make[3]: Leaving directory `/usr/src/modules/unionfs'
make[2]: *** [binary-modules] Fehler 2
make[2]: Leaving directory `/usr/src/modules/unionfs'
make[1]: *** [kdist_build] Fehler 2
make[1]: Leaving directory `/usr/src/modules/unionfs'
Module /usr/src/modules/unionfs failed.
Hit return to Continue
make: *** [modules_image] Unterbrechung
Bug#362235: nvidia-glx-legacy: dependency on old package xserver-common
Package: nvidia-glx-legacy Version: 1.0.7174-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hello, nvidia-glx-legacy depends on xserver-common which is obsolete. please rebuild against x11-common or sililar ;) ... thanks, kiro -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEPXzBYWOj0axvMcURAgItAKCctvuUJmRVFqoSh3977e4Ecty3AgCeOYgS yFM3IF0nAKIU2xwYcvSuGd8= =X/T/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#339137: checkinstall: new upstream version available
Package: checkinstall Version: 1.5.3-3 Followup-For: Bug #339137 The new version 1.6 of checkinstall seems to close this problem. Please update the package. http://asic-linux.com.mx/~izto/checkinstall/docs/RELNOTES Fixed the bug in installwatch that caused segfaults when running on newer glibc versions (And therefore newer distros like FC and SuSe 9.1) Kiro pgpUHCUU60qy4.pgp Description: PGP signature
Bug#345396: xserver-xorg: Conflicts nvidia-glx [Resolved]
Merge 345396 345455 Randall Donald [EMAIL PROTECTED] wrote: The upcoming nvidia-*-legacy packages will also have the diversion so I'll just reassign this bug over to me if you all don't mind. These Packages work fine . This Bug can be closed. Thank You, Kiro pgp9GMhxwSk4b.pgp Description: PGP signature
Bug#345396: xserver-xorg: Conflicts nvidia-glx ... in other words: older hardware isnt supported anymore
Package: xserver-xorg Version: 6.9.0.dfsg.1-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello. I've read #338715, and I know its nvidias fault, but conflicting with older nvidia-glx packages is NOT an acceptable solution for me. I use an older nvidia GeForce Graphics-Board, which is only supported up to driver version 7174. See http://www.nvidia.com/object/IO_18897.html Until now I had no problems with that. But now I have to decide if I want to use the old driver and so cant upgrade the xserver-xorg package, or to use the free nv driver for this card and miss the hardware- acceleration while upgrading xserver-xorg to 6.9.0.dfsg.1-1 and further. :( Please remove the Conflicts: nvidia-glx = 1.0.7174-4 and use the divert-solution as mentioned in #338715. Thanks. have a good start in 2006. Kiro ii nvidia-glx1.0.7174-4NVIDIA binary XFree86 4.x driver ii nvidia-kernel-2.6.14 1.0.7174-4+kiro1 NVIDIA binary kernel module for Linux 2.6.14 VGA-compatible devices on PCI bus: :01:00.0 VGA compatible controller: nVidia Corporation NV10 [GeForce 256 SDR] (rev 10) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDtfmoYWOj0axvMcURAhjLAJ4jlpg9kg0NqgnC3XBrkPg/edhqrgCeMiFo vG8SfmcEJJ6ThOgOpckyJik= =zQ0D -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335208: mount.crypt: cryptsetup has problem when reading password from stdin
Package: libpam-mount
Version: 0.9.27.62-1
Severity: important
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
An encrypted partition can't be mounted, because the device-mapper uses a
wrong (?) password to create the mapping. The problem seems to be inside
mount.crypt, where cryptsetup reads the decrypted passwort from stdin. I
appended a small fix, which works for me.
Please excuse this new report, if it's a cryptsetup bug. ;)
Kiro
- -- /etc/security/pam_mount.conf
volume kiro crypt - /dev/hdb5 /home/kiro
cipher=aes-cbc-essiv:sha256,exec,nodev,nosuid aes-256-ecb /mnt/usb/kiro.key
- -- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages libpam-mount depends on:
ii libc6 2.3.5-7GNU C Library: Shared libraries an
ii libglib2.0-0 2.8.3-1The GLib library of C routines
ii libssl0.9.8 0.9.8a-2 SSL shared libraries
ii mount 2.12p-8Tools for mounting and manipulatin
ii zlib1g1:1.2.3-6 compression library - runtime
libpam-mount recommends no packages.
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDWl+bYWOj0axvMcURAo76AJ0dW4eceFvOGeFozq0GIpy4WfLCRwCffBSW
5kSDZeHIpwuRr/wWOLgzAMw=
=zSYl
-END PGP SIGNATURE-
--- mount.crypt_orig2005-10-22 15:39:56.0 +0200
+++ mount.crypt 2005-10-22 16:37:31.0 +0200
@@ -151,12 +151,12 @@
LUKS=false;
if test -t 0; then
# interactive password input (the default in cryptsetup)
-KEYOPT=
+ $CRYPTSETUP -c ${CIPHER:-aes} -h ${HASH:-ripemd160} \
+ -s ${KEYSIZE:-256} create $DMDEVICE $DEVICE;
else
-KEYOPT=-d /dev/stdin
+ /bin/cat /dev/stdin | $CRYPTSETUP -c ${CIPHER:-aes} -h
${HASH:-ripemd160} \
+ -s ${KEYSIZE:-256} create $DMDEVICE $DEVICE;
fi
-$CRYPTSETUP -c ${CIPHER:-aes} -h ${HASH:-ripemd160} \
- -s ${KEYSIZE:-256} $KEYOPT create $DMDEVICE $DEVICE;
fi;
if [ $? -ne 0 ]; then
Bug#332869: libpam-mount doesn't work after last update
Package: libpam-mount Version: 0.9.27.49-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Bastian, the last update introduces a bug, that the encrypted partition is not mounted on login anymore. Appended are my config-settings and the debug output. thanks for your good work, Kiro - --- /etc/security/pam_mount.conf --- volume kiro crypt - /dev/hdb5 /home/kiro cipher=aes-cbc-essiv:sha256,exec,nodev,nosuid aes-256-ecb /mnt/usb/kiro.key - --- login --- pam_mount: reading options_allow... pam_mount: reading options_require... pam_mount: back from global readconfig pam_mount: per-user configurations not allowed by pam_mount.conf pam_mount: real and effective user ID are 0 and 0. pam_mount: checking sanity of volume record (/dev/hdb5) pam_mount: about to perform mount operations pam_mount: information for mount: pam_mount: -- pam_mount: (defined by globalconf) pam_mount: user: kiro pam_mount: server: pam_mount: volume:/dev/hdb5 pam_mount: mountpoint:/home/kiro pam_mount: options: cipher=aes-cbc-essiv:sha256,exec,nodev,nosuid pam_mount: fs_key_cipher: aes-256-ecb pam_mount: fs_key_path: /mnt/usb/kiro.key pam_mount: use_fstab: 0 pam_mount: -- pam_mount: realpath of volume (/home/kiro) is (/home/kiro) pam_mount: checking to see if /de is already mounted at /home/kiro pam_mount: checking for encrypted filesystem key configuration pam_mount: decrypting FS key using system auth. token and aes-256-ecb pam_mount: about to start building mount command pam_mount: command: /bin/mount [-t] [crypt] [-ocipher=aes-cbc-essiv:sha256,exec,nodev,nosuid] [/dev/hdb5] [/home/kiro] pam_mount: mount errors (should be empty): pam_mount: pam_mount: setting uid to 0 pam_mount: pam_mount: real user/group IDs are 0/1000, effective is 0/1000 pam_mount: Usage: mount -V : print version pam_mount:mount -h : print this help pam_mount:mount: list mounted filesystems pam_mount:mount -l : idem, including volume labels pam_mount: So far the informational part. Next the mounting. pam_mount: The command is `mount [-t fstype] something somewhere'. pam_mount: Details found in /etc/fstab may be omitted. pam_mount:mount -a [-t|-O] ... : mount all stuff from /etc/fstab pam_mount:mount device : mount device at the known place pam_mount:mount directory : mount known device here pam_mount:mount -t type dev dir: ordinary mount command pam_mount: Note that one does not really mount a device, one mounts pam_mount: a filesystem (of the given type) found on the device. pam_mount: One can also mount an already visible directory tree elsewhere: pam_mount:mount --bind olddir newdir pam_mount: A device can be given by name, say /dev/hda1 or /dev/cdrom, pam_mount: or by label, using -L label or by uuid, using -U uuid . pam_mount: Other options: [-nfFrsvw] [-o options] [-p passwdfd]. pam_mount: For many more details, say man 8 mount . pam_mount: mount.crypt: error mounting _dev_hdb5 pam_mount: waiting for mount pam_mount: mount of /dev/hdb5 failed pam_mount: clean system authtok (0) pam_mount: command: /usr/sbin/pmvarrun [-u] [kiro] [-d] [-o] [1] pam_mount: setting uid to 0 pam_mount: real user/group IDs are 0/1000, effective is 0/1000 pmvarrun: parsed count value 0 pam_mount: pmvarrun says login count is 1 pam_mount: done opening session - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libpam-mount depends on: ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libglib2.0-0 2.8.3-1The GLib library of C routines ii libssl0.9.8 0.9.8-1SSL shared libraries ii mount 2.12p-8Tools for mounting and manipulatin ii zlib1g1:1.2.3-4 compression library - runtime libpam-mount recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDSHIXYWOj0axvMcURApqkAJ9EjmSFpOEy67f/BvOno+LG3rfc3ACePkoz fxakLf17uthBR53FDfKzkP8= =bIW4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315863: ipw2100-source: fails to build with kernel 2.6.12
Package: ipw2100-source
Version: 1.1.0-1
Severity: important
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The package fails to build with kernel 2.6.12, but the patch is
appended...
regards, Kiro
- -- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages ipw2100-source depends on:
ii debconf [debconf-2.0] 1.4.51 Debian configuration management sy
ii debhelper 4.9.1 helper programs for debian/rules
ii module-assistant 0.9.2 tool to make module package creati
ipw2100-source recommends no packages.
- -- debconf information excluded
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCvsZrYWOj0axvMcURAj5kAJ9C8n4SH6GKF2LaPS3jt1wu+JmUSACgpLnQ
qKd6Y3cIiqvXQd5nQ/F/aZ0=
=U2mJ
-END PGP SIGNATURE-
diff --git a/ipw2100/ieee80211_tx.c b/ipw2100/ieee80211_tx.c
--- a/ipw2100/ieee80211_tx.c
+++ b/ipw2100/ieee80211_tx.c
@@ -336,8 +336,7 @@ int ieee80211_xmit(struct sk_buff *skb,
/* Determine fragmentation size based on destination (multicast
* and broadcast are not fragmented) */
- if (is_multicast_ether_addr(dest) ||
- is_broadcast_ether_addr(dest))
+ if (is_multicast_ether_addr(dest))
frag_size = MAX_FRAG_THRESHOLD;
else
frag_size = ieee-fts;
diff --git a/ipw2100/ieee80211.h b/ipw2100/ieee80211.h
--- a/ipw2100/ieee80211.h
+++ b/ipw2100/ieee80211.h
@@ -655,16 +655,12 @@ enum ieee80211_state {
#define MAC_ARG(x) ((u8*)(x))[0],((u8*)(x))[1],((u8*)(x))[2],((u8*)(x))[3],((u8*)(x))[4],((u8*)(x))[5]
+#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,12)
extern inline int is_multicast_ether_addr(const u8 *addr)
{
- return ((addr[0] != 0xff) (0x01 addr[0]));
-}
-
-extern inline int is_broadcast_ether_addr(const u8 *addr)
-{
- return ((addr[0] == 0xff) (addr[1] == 0xff) (addr[2] == 0xff)\
- (addr[3] == 0xff) (addr[4] == 0xff) (addr[5] == 0xff));
+ return addr[0] 0x01;
}
+#endif
#define CFG_IEEE80211_RESERVE_FCS (10)
#define CFG_IEEE80211_COMPUTE_FCS (11)
Bug#315766: kmail: crash after question for sending a receive notification
Package: kmail Version: 4:3.3.2-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 crash after question for sending a receive notification: steps to reproduce: - - select a new message which demands a receive notification (mail has a header with Disposition-Notification-To: [EMAIL PROTECTED]) - - a kmail popup apears, which asks if the user want to send or ignore this notification - do nothing - - select any other message, while the popup is still open - - now click ignore - crash thank you, Kiro - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kmail depends on: ii kdelibs4 4:3.3.2-6.1 KDE core libraries ii libc62.3.2.ds1-22GNU C Library: Shared libraries an ii libgcc1 1:4.0.0-11 GCC support library ii libice6 4.3.0.dfsg.1-14 Inter-Client Exchange library ii libkcal2a4:3.3.2-3 KDE calendaring library ii libkdenetwork2 4:3.3.2-3 KDE Network library ii libkdepim1 4:3.3.2-3 KDE PIM library ii libkleopatra0a 4:3.3.2-3 KDE GnuPG interface libraries ii libkpimidentities1 4:3.3.2-3 KDE PIM user identity information ii libksieve0 4:3.3.2-3 KDE mail/news message filtering li ii libmimelib1a 4:3.3.2-3 KDE mime library ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-14 X Window System Session Management ii libstdc++5 1:3.3.6-7 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14 X Window System miscellaneous exte ii perl 5.8.7-3 Larry Wall's Practical Extraction ii xlibs4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime Versions of packages kmail recommends: ii kdebase-kio-plugins 4:3.3.2-1 KDE I/O Slaves ii kdepim-kio-plugins4:3.3.2-3 KDE pim I/O Slaves pn procmail none (no description available) - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCvbPOYWOj0axvMcURArReAJ9ojv25aSc6kbPalw8SVfi51pRwCQCfbyA6 93TktMehVeFhsITwDX6rCbA= =mNS5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#314252: gnupg: failed to open driver `libpcsclite.so'
Package: gnupg Version: 1.4.1-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I use an Towitoko Chipdrive Reader on /dev/ttyS0 (not the USB-Version). GPG does not find libpcsclite.so. As a workaround, i made a symlink to the library. I could also install libpcsclite1-dev, wich contains the missing symlink, but i think this is a gpg problem, because other packages work fine without installing it. $ LANG=C_ALL gpg --disable-ccid --card-status gpg: apdu_open_reader: failed to open driver `libpcsclite.so': libpcsclite.so: cannot open shared object file: No such file or directory gpg: card reader not available gpg: OpenPGP card not available: general error $ ls -l /usr/lib/libpcsclite.so* lrwxrwxrwx 1 root root 20 Mar 24 22:42 /usr/lib/libpcsclite.so.1 - libpcsclite.so.1.0.0 - -rw-r--r-- 1 root root 48592 Mar 24 14:21 /usr/lib/libpcsclite.so.1.0.0 $ sudo ln -s libpcsclite.so.1 /usr/lib/libpcsclite.so $ LANG=C_ALL gpg --disable-ccid --card-status gpg: detected reader `Towitoko Chipdrive Reader 00 00' [..] some related packages: ii libpcsc-perl 1.4.2-1 ii libpcsclite1 1.2.9-beta7-5 ii pcsc-tools1.4.1-1 ii pcscd 1.2.9-beta7-5 ii libtowitoko2 2.0.7-4 thanks, Kiro - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-nitro2 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages gnupg depends on: ii libbz2-1.0 1.0.2-7 high-quality block-sorting file co ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libldap22.1.30-10OpenLDAP libraries ii libreadline55.0-10 GNU readline and history libraries ii libusb-0.1-42:0.1.10a-14 userspace USB programming library ii makedev 2.3.1-78 creates device files in /dev ii zlib1g 1:1.2.2-4compression library - runtime - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCsB8uYWOj0axvMcURAnj8AJ0bhvu1SoIzkWkDyMzjqhLCtFp/2wCfYAwK yF6GEKDGgWSKNWYYJYwMSLM= =iR1q -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#314252: gnupg: failed to open driver `libpcsclite.so'
Am Mittwoch, 15. Juni 2005 17:26 schrieb Werner Koch [EMAIL PROTECTED] No, it is not. gpg dlopens pscslite.so and provides an option to override the default name (--pcsc-driver). I searched inside the manual- and info-pages for an solution, but this option is nowhere explained. Now it works as expected ;) Thank you, Kiro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303369: kxdocker fails on initial startup
Package: kxdocker Version: 0.26-3 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 kxdocker fails to load on the initial startup. the same (?) error occured, if the initial config-files are copied from the global directory. ~$ kxdocker You may need to update or reinstall KXDocker resources, checkout http://www.xiaprojects.com/www/prodotti/kxdocker/main.php?action=download#resources loading xml... May be you have load a wrong kxdocker_conf.xml ERROR: Communication problem with kxdocker, it probably crashed. ~$ cp /usr/share/apps/kxdocker/kxdockerui.rc ~/.kde/share/config/kxdockerrc ~$ mkdir ~/.kde/share/apps/kxdocker ~$ cp /usr/share/apps/kxdocker/kxdocker_conf.xml ~/.kde/share/apps/kxdocker/ ~$ kxdocker Invalid entry (missing '=') at /home/kiro/.kde/share/config/kxdockerrc:1 Invalid entry (missing '=') at /home/kiro/.kde/share/config/kxdockerrc:3 Invalid entry (missing '=') at /home/kiro/.kde/share/config/kxdockerrc:6 Invalid entry (missing '=') at /home/kiro/.kde/share/config/kxdockerrc:7 Invalid entry (missing '=') at /home/kiro/.kde/share/config/kxdockerrc:8 You may need to update or reinstall KXDocker resources, checkout http://www.xiaprojects.com/www/prodotti/kxdocker/main.php?action=download#resources loading xml... May be you have load a wrong kxdocker_conf.xml ERROR: Communication problem with kxdocker, it probably crashed. - -- System Information: Debian Release: sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-nitro2 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kxdocker depends on: ii kdelibs4 4:3.3.2-4.0.2 KDE core libraries ii kxdocker-data0.8-1 resource files for kxdocker ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libfam0c102 2.7.0-6 client library to control the FAM ii libgcc1 1:3.4.3-12 GCC support library ii libice6 4.3.0.dfsg.1-12.0.1 Inter-Client Exchange library ii libidn11 0.5.13-1.0 GNU libidn library, implementation ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt3:3.3.4-2 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-12.0.1 X Window System Session Management ii libstdc++5 1:3.3.5-12 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte ii libxrender1 0.8.3-7 X Rendering Extension client libra ii xlibs4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCU8WlYWOj0axvMcURArzxAJ9lT51EibSRFmjErWlJs7/G5s3zxwCZARBX a9mHmg4xRoyMt0u88aA1jNQ= =ZLEb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#302006: libpam-mount doesn't work after update
Package: libpam-mount Version: 0.9.22-5 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, the encrypted partition is not mounted (and decrypted) on login. Up to version 0.9.22-4 there was no such problem. I attached my config and the (hopefully correct copy-n-wasted) debug output. Kiro - --- /etc/security/pam_mount.conf --- # i cutted the standard-statements volume kiro crypt - /dev/hdb5 /home/kiro cipher=aes,exec,nodev,nosuid aes-256-ecb /mnt/usb/kiro.key - --- login --- pam_mount: reading options_allow... pam_mount: reading options_require... pam_mount: back from global readconfig pam_mount: per-user configurations not allowed by pam_mount.conf pam_mount: real and effective user ID are 0 and 0. pam_mount: checking sanity of volume record (/dev/hdb5) pam_mount: about to perform mount operations pam_mount: information for mount: pam_mount: pam_mount: (defined by globalconf) pam_mount: user: kiro pam_mount: server: pam_mount: volume:/dev/hdb5 pam_mount: mountpoint:/home/kiro pam_mount: options: cipher=aes,exec,nodev,nosuid pam_mount: fs_key_cipher: aes-256-ecb pam_mount: fs_key_path: /mnt/usb/kiro.key pam_mount: use_fstab: 0 pam_mount: pam_mount: checking to see if /dev/mapper/_dev_hdb5 is already mounted at /home/kiro pam_mount: checking for encrypted filesystem key configuration pam_mount: decrypting FS key using system auth. token and aes-256-ecb pam_mount: about to start building mount command pam_mount: command: /bin/mount -t crypt -ocipher=aes,exec,nodev,nosuid /dev/hdb5 /home/kiro pam_mount: mount errors (should be empty): pam_mount: pam_mount: setting uid to 0 pam_mount: pam_mount: real and effective user ID are 0 and 0. pam_mount: pam_mount: real and effective group ID are 1000 and 1000. pam_mount: /sbin/mount.crypt: line 141: /sbi: No such file or directory pam_mount: mount.crypt: error creating _dev_hdb5 pam_mount: waiting for mount pam_mount: mount of /dev/hdb5 failed pam_mount: clean system authtok (0) pam_mount: command: /usr/sbin/pmvarrun -u kiro -d -o 1 pam_mount: setting uid to 0 pam_mount: real and effective user ID are 0 and 0. pam_mount: real and effective group ID are 1000 and 1000. pam_mount: pmvarrun says login count is 1 pam_mount: done opening session - --- logout --- pam_mount: received order to close things pam_mount: real and effective user ID are 0 and 0. pam_mount: user is kiro pam_mount: command: /usr/sbin/pmvarrun -u kiro -d -o -1 pam_mount: setting uid to 0 pam_mount: real and effective user ID are 0 and 0. pam_mount: real and effective group ID are 1000 and 1000. pam_mount: pmvarrun says login count is 0 pam_mount: going to unmount pam_mount: information for mount: pam_mount: pam_mount: (defined by globalconf) pam_mount: user: kiro pam_mount: server: pam_mount: volume:/dev/hdb5 pam_mount: mountpoint:/home/kiro pam_mount: options: cipher=aes,exec,nodev,nosuid pam_mount: fs_key_cipher: aes-256-ecb pam_mount: fs_key_path: /mnt/usb/kiro.key pam_mount: use_fstab: 0 pam_mount: pam_mount: command: /usr/sbin/lsof /home/kiro pam_mount: setting uid to 0 pam_mount: real and effective user ID are 0 and 0. pam_mount: real and effective group ID are 1000 and 1000. pam_mount: lsof output (should be empty)... pam_mount: COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME pam_mount: artsd 10021 kiro cwdDIR3,6 4096 33407 /home/kiro pam_mount: waiting for lsof pam_mount: command: /usr/bin/umount.crypt /home/kiro pam_mount: umount errors (should be empty): pam_mount: pam_mount: setting uid to 0 pam_mount: pam_mount: real and effective user ID are 0 and 0. pam_mount: pam_mount: real and effective group ID are 1000 and 1000. pam_mount: /usr/bin/umount.crypt: line 46: /bi: No such file or directory pam_mount: /usr/bin/umount.crypt: line 48: /sbi: No such file or directory pam_mount: /usr/bin/umount.crypt: line 50: /bi: No such file or directory pam_mount: umount.crypt: error unmounting /home/kiro pam_mount: waiting for umount pam_mount: unmount of /dev/hdb5 failed pam_mount: pam_mount execution complete pam_mount: clean system authtok (0) - -- System Information: Debian Release: sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-nitro2 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libpam-mount depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libglib2.0-02.6.3-1 The GLib library of C routines ii libssl0.9.7 0.9.7e-3 SSL shared libraries ii mount 2.12p-4 Tools for mounting and manipulatin ii zlib1g 1:1.2.2-4compression library - runtime - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux)
Bug#301407: quickcam: Unknown symbol remap_page_range
Package: qc-usb-source Version: 0.6.2-2 Module quickcam compiles well with latest Kernel 2.6.11, but is not loadable. With insmod the following error appeared: quickcam: Unknown symbol remap_page_range Possible Solution in Upstream Mailing-List: http://sourceforge.net/mailarchive/forum.php?thread_id=6576457forum_id=4334 Linux 2.6.11-nitro2 i686 GCC Version: 4:3.3.5-1 (SID) Kiro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301407:
Package: qc-usb-source
Version: 0.6.2-2
here the working patch ;)
--- qc-memory.c_old 2005-03-25 17:50:54.0 +0100
+++ qc-memory.c 2005-03-26 00:56:15.0 +0100
@@ -230,7 +230,7 @@
pos = (unsigned long)src;
while ((long)size 0) {
physaddr = kvirt_to_pa(pos);
- if (remap_page_range(vma, start, physaddr, PAGE_SIZE,
PAGE_SHARED))
+ if (remap_pfn_range(vma, start, physaddr PAGE_SHIFT,
PAGE_SIZE, PAGE_SHARED))
return -EAGAIN;
start += PAGE_SIZE;
pos += PAGE_SIZE;
Kiro
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
