-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
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.
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
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
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
-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
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.
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
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
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
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
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
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
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
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
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.
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
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
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,
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
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
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
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
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
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:
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
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
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
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
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:
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,
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
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
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
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:
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 =
36 matches
Mail list logo
