Bug#756519: Toggling session with F1 key does not work anymore

2014-07-30 Thread gator_ml
Package: slim Version: 1.3.6-3 Severity: normal It seems like toggling the session with F1 does not work anymore - pressing the F1 key yields no reaction at all (no message on the screen, after login the default session is started). The keyboard setup is o.k. (F1 otherwise works normally ;-).

Bug#754722: Security upgrade causes severe network packet loss

2014-07-14 Thread gator_ml
On Sun, 13 Jul 2014 18:06:16 +0100, Ben Hutchings wrote: See https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=44;bug=754173. Thanks - I can confirm that my problem is indeed caused by the same issue and is gone with the kernel you supplied :-) Regards, Peter -- To

Bug#754722: Security upgrade causes severe network packet loss

2014-07-13 Thread gator_ml
Package: linux-image-3.2.0-4-amd64 Version: 3.2.60-1+deb7u1 Severity: important After installing security upgrade 3.2.60-1+deb7u1 on my machines, a pool of machines providing virtual desktop to end users turned pretty much unusable. To explain the situation, here's a little picture:

Bug#729480: SSL connections with client certificates no longer working

2013-11-15 Thread gator_ml
On 2013-11-13 18:39, Stefan Bühler wrote: I updated our advisory at [...] with the diff from revision 2925: http://redmine.lighttpd.net/projects/lighttpd/repository/revisions/2925/diff/ Thanks a lot for the quick reaction! I can confirm that with your patch added to the debian package

Bug#729480: SSL connections with client certificates no longer working

2013-11-13 Thread gator_ml
Package: lighttpd Version: 1.4.31-4+deb7u1 Severity: important I am running a webserver that only offers https and normally requires client certificates. When I install the security upgrade 1.4.31-4+deb7u1 and restart lighttpd, with some delay (when I keep hitting reload in a client, it works

Bug#696988: live-build 3.x: --chroot-filesystem plain/none ?

2012-12-30 Thread gator_ml
Package: live-build Version: 3.0~a51-1 Severity: normal I have been using live-build to generate a NFS-root system to be booted via PXE: lb config --architecture i386 \ --linux-flavours 686 \ --distribution wheezy \ --chroot-filesystem plain --binary-images net \ --net-root-path

Bug#686776: cdrom image files should be opened read-only

2012-09-05 Thread gator_ml
Package: qemu-kvm Version: 1.0+dfsg-11 Severity: important qemu tries to open cdrom images read-write, so loading a cd will only work if the qemu process could write the file. It does not matter, if the readonly flag is set on the command line (I usually use: -drive

Bug#624754: AF_INET6 sockets even if not specified nor available

2011-05-01 Thread gator_ml
Package: libio-socket-inet6-perl Version: 2.65-1 Severity: important Prior versions of IO::Socket::INET6 used domain AF_UNSPEC unless a domain was explicitly provided. This lead many other libraries (e.g. libnet-dns-perl, libio-socket-ssl-perl, probably more) to use IO::Socket::INET6 instead of

Bug#613052: hisax: Elsa QuickStep 1000 not working

2011-02-12 Thread gator_ml
Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-30 After upgrading to kernel 2.6.32, my ISDN card is not working anymore. It looks like the driver can't get the io ports. The same system with kernel 2.6.26 works alright. lspci says: 06:01.0 Network controller: Elsa AG QuickStep 1000 (rev 02)

Bug#593087: xinput buttons not recognized correctly

2010-08-16 Thread gator_ml
I investigated the issue further and found, that this problem is obviously not restricted to debian, but affecting all recent gtk+ versions, so I also submitted a bug report to the gtk maintainers, see: https://bugzilla.gnome.org/show_bug.cgi?id=627022 -- To UNSUBSCRIBE, email to

Bug#593087: xinput buttons not recognized correctly

2010-08-15 Thread gator_ml
Package: libgtk2.0-0 Version: 2.20.1 In recent gtk2 versions, xinput button events (in my case from a wacom tablet, other devices probably as well) do not work correctly any more. Normal GUI usage is ok, only programs that actually handle extended input devices (gimp/inkscape) are affected:

Bug#573054: packages in config/chroot_local-packages have lowest priority

2010-03-08 Thread gator_ml
Package: live-helper Version: 2.0~a8-1 When a package is put into config/chroot_local-packages for installation, but an equivalent package is also available from the default package sources, apt will always install the package from the default source and not the one in

Bug#479585: (no subject)

2009-09-30 Thread gator_ml
There still is a whole bunch of repositories out there that don't have Contents file, so I also think that some way of suppressing messages about missing files (and the resulting emails if used in a cron job) would be good. Actually, the annoying message is not produced by the programm code, but

Bug#548338: regular syslog messages error writing to client

2009-09-25 Thread gator_ml
package: libnss-ldapd version: 0.6.7.1 severity: normal I have several server that get their user base from a ldap directory. Particularly on one of them, I regularly get error messages in the syslog saying error writing to client. Usually, there are short burst of messages (several messages send

Bug#529060: Hook scripts (Pre/Post-Invoke ..) should be able to know their context

2009-05-17 Thread gator_ml
package: apt severity: wishlist I spent quite some time searching how to find out the package on behalf of which a hook script configured via DPkg::Post-Invoke is being run: I was sure, I must have overlooked something, until I eventually looked into the sources ... Hooks like

Bug#505204: perlpanel: unhandled exception clicking Configure...

2009-02-17 Thread gator_ml
Package: perlpanel Tags: patch *** Failed to open file '': No such file or directory at /usr/share/perlpanel//PerlPanel/Applet/Configurator.pm line 167. ... The corresponding ubuntu packages differs in 1 tiny, but effective detail: diff -ruN debian/DEBIAN/postinst ubuntu/DEBIAN/postinst

Bug#514234: allow export of local repositories

2009-02-05 Thread gator_ml
On Thu, Feb 05, 2009, Eric Cooper wrote: This should already be possible. Note that the syntax for file URLs requires 3 leading slashes (2 for the URL syntax, and 1 for the root of the pathname): Oops -shame on me! I didn't see anything about this scenario in the documentation, so I