Bug#381864: Workaround

2013-05-08 Thread Reto Galante
Hi Robert, Somehow the sa2 script is not being executed, although it has an cron.daily entry. A workaround for this issue is to create a cronjob for user root - then /usr/lib/sysstat/sa2 is executed. Regards, Reto

Bug#381864: Issue still present in version 9.0.6

2013-05-06 Thread Reto Galante
Hello This issue is still present in systat version 9.0.6: 756 -rw-r--r-- 1 root root 769596 May 2 00:00 sa01 756 -rw-r--r-- 1 root root 769548 May 3 00:00 sa02 756 -rw-r--r-- 1 root root 769548 May 4 00:00 sa03 756 -rw-r--r-- 1 root root 769548 May 5 00:00 sa04 756 -rw-r--r-- 1 root

Bug#618313: The unlock dialogue uses a different keyboard layout

2011-03-14 Thread Reto Galante
Package: gnome-screensaver Version: 2.30.0-2 Severity: important Tags: squeeze This causes the unlock to fail if the users password contains a character, which differs in the other keyboard layout. Workaround: if your password is for example GoldenBoy and you are using a german layout, you can

Bug#618313: AW: Bug#618313: The unlock dialogue uses a different keyboard layout

2011-03-14 Thread Reto Galante
There is no layout name displayed in this dialog (i have only one layout installed for the current user) -Ursprüngliche Nachricht- Von: Josselin Mouette [mailto:j...@debian.org] Gesendet: Montag, 14. März 2011 12:27 An: Reto Galante; 618...@bugs.debian.org Betreff: Re: Bug#618313

Bug#618313: AW: Bug#618313: AW: Bug#618313: The unlock dialogue uses a different keyboard layout

2011-03-14 Thread Reto Galante
-Ursprüngliche Nachricht- Von: Josselin Mouette [mailto:j...@debian.org] Gesendet: Montag, 14. März 2011 15:17 An: Reto Galante; 618...@bugs.debian.org Betreff: Re: Bug#618313: AW: Bug#618313: The unlock dialogue uses a different keyboard layout A: Because it breaks the flow

Bug#295420: Bug in Package K3b and/or sudo

2005-02-15 Thread Reto Galante
Package: K3b Version: 0.11.18 (sarge) Package: sudo Version: 1.6.8p5 (sarge) Description of the bug: whenever K3b is started by sudo (as a regular user foobar), the .ICEauthority file of foobar gets the ownership and group of root - the next time foobar logs into gdm, the session is rejected.