Bug#372564: kwalletmanager very often crashes at KDE Logout

Package: kwalletmanager Version: 4:3.5.3-1 Severity: important After upgrading to kdeutils 3.5.3-1 I experience frequently - something like every second time - that a KDE logout hangs with a message that kdewalletmanager has experienced a SIGSEGV. This is pretty bad: not only is the logout

Processed: [bts-link] source package kdenetwork

Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package kdenetwork # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). # remote status report for

Processed: [bts-link] source package koffice

Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package koffice # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). # remote status report for

[bts-link] source package kdenetwork

# # bts-link upstream status pull for source package kdenetwork # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #360820 # * http://bugs.kde.org/show_bug.cgi?id=124936 # * remote status changed: UNCONFIRMED - RESOLVED

[bts-link] source package koffice

# # bts-link upstream status pull for source package koffice # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #367059 # * http://bugs.kde.org/show_bug.cgi?id=125944 # * remote status changed: RESOLVED - REOPENED # *

[bts-link] source package kdelibs

# # bts-link upstream status pull for source package kdelibs # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #295928 # * http://bugs.kde.org/show_bug.cgi?id=19446 # * remote status changed: (?) - UNCONFIRMED usertags

[bts-link] source package kdepim

# # bts-link upstream status pull for source package kdepim # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #369830 # * http://bugs.kde.org/show_bug.cgi?id=115426 # * remote status changed: (?) - NEW usertags 369830

[bts-link] source package kdegraphics

# # bts-link upstream status pull for source package kdegraphics # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #255583 # * http://bugs.kde.org/show_bug.cgi?id=91626 # * remote status changed: (?) - UNCONFIRMED

Kaffeine annoyance

(please CC me on reply) Hi, I usually upgrade my Debian unstable system once a week. Right after I have done so, Kaffeine very often crashes on reading files (I do use it to read .asx streams). I realized I have to leave my KDE session and open a new one in order to make Kaffeine work again.

Bug#334116: marked as done (might it possible to get a higher zoom)

Your message dated Sat, 10 Jun 2006 17:36:49 +0200 with message-id [EMAIL PROTECTED] and subject line might it possible to get a higher zoom has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Processed: your mail

Processing commands for [EMAIL PROTECTED]: # wishlist bug open for 4 years... tags 134363 wontfix Bug#134363: contigously scroll over a range of pages Tags were: upstream Tags added: wontfix # forwarded 317984 http://bugs.kde.org/show_bug.cgi?id=91809 Bug#317984: kpdf: Cannot enter data into

Bug#372614: kugar: Example docs are broken symlinks

Package: kugar Version: 1:1.5.1-1 Severity: minor The example doc symlinks installed into /usr/share/doc/kugar/examples are broken. They use the .kud and .kut extensions rather than .kdf and ..ktf, which is how the files are actually named: lrwxrwxrwx 1 root root 41 2006-05-23 08:40

Bug#372638: kscreensaver: screensavers don't start automatically

Package: kscreensaver Version: 4:3.5.3-1 Severity: normal Although screensavers are launched when the button test is pressed in the KDE control center, they dont start automatically after a given time. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy:

qt4-x11 4.1.3-2 MIGRATED to testing

FYI: The status of the qt4-x11 source package in Debian's testing distribution has changed. Previous version: 4.1.2-2 Current version: 4.1.3-2 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information.

Bug#372564: kwalletmanager: I have the same problem

Package: kwalletmanager Version: 4:3.5.3-1 Followup-For: Bug #372564 Just a me too. I am experiencing the exact same problem. Regards, Thue -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh

knode doesn't strip signatures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've filed a bug against knode. http://bugs.kde.org/show_bug.cgi?id=128848 I've looked into all the options in the Posting News section but while replying to a message the signatures aren't stripped off. Can people using knode please confirm

Re: knode doesn't strip signatures

Le Samedi 10 Juin 2006 22:32, Ritesh Raj Sarraf [EMAIL PROTECTED] a écrit : Hi, I've filed a bug against knode. http://bugs.kde.org/show_bug.cgi?id=128848 I've looked into all the options in the Posting News section but while replying to a message the signatures aren't stripped off. Have

Re: knode doesn't strip signatures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 posted mailed Olivier Trichet on Sunday 11 Jun 2006 04:54 wrote: Le Samedi 10 Juin 2006 22:32, Ritesh Raj Sarraf [EMAIL PROTECTED] a écrit : Hi, I've filed a bug against knode. http://bugs.kde.org/show_bug.cgi?id=128848 I've looked into all

X-system and KDE problems

My debian etcg 32bit has experienced twice an X-system failure to start following #apt-get upgrade In both cases recovered, though error messages are presented. The X-system is first started alone with $startx with /home/me/.Xsession #!/bin/sh xrdb -load $HOME/.Xresources exec xterm