Bug#324798: can't determine who's key to encrypt to

Hi! Alexander Sack - Debian Bugmail wrote: Maybe another information: When I use the OpenPGP - Key Management menu, only my own key is shown, but only with three out of the four UIDs shown by gpg. When I right-click one of these UIDs and select Key Properties, all fields are filled with ?. FWIW,

Bug#324798: can't determine who's key to encrypt to

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Alexander Sack - Debian Bugmail wrote: tru::0:1133273718:1166994384:3:1:5 pub:u:1024:17:D09580C78ABCAEF5:2004-11-05:::u:T* P* [EMAIL PROTECTED]::scESC: uid:u2005-01-08::36F1A*FBE32DD::Tobias Pfeiffer [EMAIL PROTECTED]: uid:u2005-01-05

Bug#324798: can't determine who's key to encrypt to

in enigmailUserSelection: enigmailUserSelLoad: 2005-12-17 00:50:50.726 userId=undefined expiry= Running the gpg command manually gives me: tru::0:1133273718:1166994384:3:1:5 pub:u:1024:17:D09580C78ABCAEF5:2004-11-05:::u:T* P* [EMAIL PROTECTED]::scESC: uid:u2005-01-08::36F1A*FBE32DD::Tobias Pfeiffer [EMAIL

Bug#305589: init file is read as wrong user

Hi! matt hope wrote: ( My re-phrasing of the above: - Config files werent getting read correctly when file mode 0600. - Worked when 0644 - You suspect that somehow XrmGetFileDatabase() gets called as a different userid to the running user. ) Yes. I must admit some suprise at

Bug#309228: Find a string including special chars fails

Package: scite Version: 1.63-1 Hi! I use scite with the German Umlauts ä. ö. ü and ß. I can type them the usual way (with the corresponding keys on a keyboard with a German layout). But when I try to find a certain string (with Search - Find or Ctrl+F, respectively) and search for a word

Bug#309228: Acknowledgement (Find a string including special chars fails)

Hi again! In addition to the described tings, I also noticed that when double-clicking on a normal word selects the whole word (until the nearest line break or space character), double-clicking on a word containing an Umlaut only selects until this Umlaut. I think this might be related to the

Bug#309129: ripperx does not support titles longer than 30 chars

Package: ripperx Version: 2.6.4-2 Hi! I have recently ripped a CD and then encoded into Ogg with ripperx. The title names of the songs are quite long, at least longer than 30 charactes. The filenames of the output files are correct, but in the ID3 tags of the ogg files, after 30 characters, the

Bug#305589: init file is read as wrong user

Package: fluxbox Version: 0.9.11-1 Hi! Some time ago I submitted a bug report about fbrun crashing the X-Server at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291672archive=yes. Somewhere in the mail traffic I mentioned that my .xsession-errors file was full of: Failed to read:

Bug#301265: glowing steel fails due to bad mblur call

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: libgimp-perl Version: 2.0.dfsg-3 Hi! It seems like the version of the Glowing Steel script that is contained in the above package is broken and so are all of the scripts that use it, too (e.g. Brushed Metal). The error message is |

Bug#296161: Enigmail is reported as outdated

Package: mozilla-thunderbird Version: 1.0-3 Severity: important Hi! I just did a dist-upgrade and the Enigmail plugin does not work any more. My program versions are as follows: [EMAIL PROTECTED] $ dpkg -l | grep thunderbird ii mozilla-thunderbird 1.0-3 ii

Bug#296161: Problem nominally solved

Hi! I had to deinstall mozilla-thunderbird-enigmail, then the user could deinstall the old Enigmail plugin manually and then I reinstalled the Debian package. Now everything works fine with the new plugin. Nevertheless, I think that this behaviour is not desired. Bye Tobias -- follow the

Bug#95246: Still --without-ldap?

Hi! I just wanted to ask whether there have been any reasons why [EMAIL PROTECTED]'s patch still has not been used for the normal Debian heimdal package. For me it was also only a question of changing --without-ldap to --with-ldap in debian/rules. I mean... I think this could go into the

Bug#291672: fbrun crashes the x-server

Hi! martin f krafft schrieb: Fatal server error: Caught signal 11. Server aborting This is a segmentation fault, which could be caused by anything, including bad memory. Does it only ever happen when you try fbrun? When exactly? fbrun is the only thing that behaves like this (since the upgrade to

Bug#291672: fbrun crashes the x-server

Hullo! martin f krafft schrieb: I cannot say for sure. because Restart from the fluxbox menu also brings me back to the login manager (kdm), not like the usual behaviour. Delete /var/log/XFree86.0.log from within X and reproduce the problem. DOes the file now exist, and does it list a complete X

Bug#291672: fbrun crashes the x-server

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Matt Hope wrote: | I think you mean fbrun kills your windowmanager - or are you sure it | kills the server? I cannot say for sure. because Restart from the fluxbox menu also brings me back to the login manager (kdm), not like the usual behaviour.

Bug#291672: fbrun crashes the x-server

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: fluxbox Version: 0.9.11-1 Severity: important Tags: sarge Hi! When I run fbrun, the X-Server crashes and goes back to my Display Manager (kdm). If I type $ fbrun -help in a shell and get the default help text, but as soon as fbrun is to open a