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, what's your gnupg version? dpkg -l gnupg shows 1.4.2-2. Further, please try to uninstall the enigmail package and try the latest .xpi available from upstream (http://enigmail.mozdev.org). Take care that you choose the right version (for thunderbird 1.0.7). Let me know if it fixes the problem. Well, I think that everything is fixed now. The problem was probably that in my homedir, there were some relics left from enigmail-0.86. I removed all of them, reinstalled the default Debian enigmail package and now everything is fine; I can even send PGP/MIME messages again now. From my point of view, this bug could be closed. Bye Tobias -- I may disagree with what you have to say, but I shall defend to the death your right to say it. -- Voltaire signature.asc Description: OpenPGP digital signature
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::A697C*56F9601::Tobias Pfeiffer [EMAIL PROTECTED]: uid:u2005-01-05::FC6CC*A518E22::Tobias Pfeiffer [EMAIL PROTECTED]: sub:u:1024:16:202F67EC00AA8702:2004-11-05::e: sub:u:2048:16:934F2DC48BF90816:2005-01-05::e: pub:f:1024:17:A5150C15054BDD45:2004-12-13:2006-12-24::-:D* P* [EMAIL PROTECTED]::scESC: sub:f:2048:16:4236A9192FF2FD6E:2004-12-13:2006-12-24:e: pub:f:1024:17:75EFA28019A16E34:2005-01-08:::-:S* B* [EMAIL PROTECTED]::scESC: sub:f:4096:16:F6E5853CD4AC71D5:2005-01-08::e: pub:f:1024:17:83A13C8A1AB3934E:2005-01-30:::-:A* F* [EMAIL PROTECTED]::scESC: sub:f:2048:16:229C25AF3DA3B3AC:2005-01-30::e: pub:f:1024:17:A4E5CCA642713FBC:2005-10-26:::f:R* [EMAIL PROTECTED]::scESC: sub:f:4096:16:3C66685C8655BF0A:2005-10-26::e: So now it is to you to find out why enigmail has a problem with this output. I'd be happy to have this problem solved, since I cannot write any encrypted mails any more... Why are all those uids and email addresses messed up with '*'? Remove those keys that have an '*' in their uid/email and ask yourself, why your own key has such wildcard itself? The '*' are inserted from myself afterwards because a) I wanted to protect the identity of the ones saved in my keyring b) the lines don't get split on two lines for better overview. Sorry if that action was misleading; these stars are *not* there in the original output and the uid/email addresses are normal when printed out by gpg. 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 ?. Bye Tobias - -- I may disagree with what you have to say, but I shall defend to the death your right to say it. -- Voltaire -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDpABQ0JWAx4q8rvURAlADAJ9S77+lkWUE8NhqVo9omj3iic2ixgCePkuq szobx6oe5Nauo5/daciAVQ4= =shIh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324798: can't determine who's key to encrypt to
Hi! I've got a similar problem, too, since a while, but I think that I found out a bit more about it. I use Mozilla Thunderbird (1.0.7-3) with Enigmail (0.93-1). When I try to send an encrypted email, the window from which to select the recipient's key is empty and the console shows the following output: enigmail.js: getRulesData enigmail.js: Enigmail.encryptMessage: 12 bytes from 0x8ABCAEF5 to [EMAIL PROTECTED] (354) enigmail.js: Enigmail.encryptMessageStart: prompter=null, uiFlags=16, from 0x8ABCAEF5 to [EMAIL PROTECTED], hashAlgorithm= (0162) enigmail.js: Enigmail.execStart: command = /usr/bin/gpg --batch --no-tty --status-fd 2 -a -e --always-trust --encrypt-to 0x8ABCAEF5 -r [EMAIL PROTECTED] -u 0x8ABCAEF5, needPassphrase=0, domWindow=[object ChromeWindow], prompter=null, listener=[xpconnect wrapped nsIIPCBuffer], noProxy=true enigmail.js: Enigmail.execStart: copied command line/env to files ~/enigmail/enigcmd.txt/enigenv.txt enigmail /usr/bin/gpg --batch --no-tty --status-fd 2 -a -e --always-trust --encrypt-to 0x8ABCAEF5 -r [EMAIL PROTECTED] -u 0x8ABCAEF5 enigmail.js: Enigmail.execStart: pipetrans = [xpconnect wrapped nsIPipeTransport] enigmail.js: Enigmail.encryptMessageEnd: uiFlags=16, sendFlags=0162, outputLen=12, pipeTransport=[xpconnect wrapped (nsISupports, nsIPipeTransport, nsIRequest)] enigmail.js: Enigmail.execEnd: enigmail.js: Enigmail.execEnd: copied command err output to file ~/enigmail/enigerr.txt enigmail.js: Enigmail.execEnd: exitCode = 0 enigmail.js: Enigmail.execEnd: errOutput = [GNUPG:] BEGIN_ENCRYPTION 2 9 [GNUPG:] END_ENCRYPTION enigmail.js: Enigmail.execEnd: statusFlags = enigmail.js: Enigmail.stillActive: 2005-12-17 00:46:29.116 ERROR in enigmailUserSelection: enigmailUserSelLoad: 2005-12-17 00:46:29.117 userId=undefined expiry= So the problem is to determine why the userId is undefined. When clicking on Refresh Key List, the console shows: 2005-12-17 00:50:50.678 enigmailUserSelection.js: enigmailBuildList 2005-12-17 00:50:50.679 enigmailMessengerOverlay.js: enigGetUserList enigmail.js: Enigmail.execCmd: command = /usr/bin/gpg --batch --no-tty --status-fd 2 --with-colons --list-keys enigmail.js: Enigmail.execCmd: copied command line/env/input to files ~/enigmail/enigcmd.txt/enigenv.txt/enigi np.txt enigmail /usr/bin/gpg --batch --no-tty --status-fd 2 --with-colons --list-keys enigmail.js: Enigmail.execCmd: copied command out/err data to files ~/enigmail/enigout.txt/enigerr.txt enigmail.js: Enigmail.execCmd: exitCode = 0 enigmail.js: Enigmail.execCmd: errOutput = enigmail.js: Enigmail.execCmd: statusFlags = enigmail.js: Enigmail.stillActive: 2005-12-17 00:50:50.725 ERROR 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 PROTECTED]: uid:u2005-01-05::A697C*56F9601::Tobias Pfeiffer [EMAIL PROTECTED]: uid:u2005-01-05::FC6CC*A518E22::Tobias Pfeiffer [EMAIL PROTECTED]: sub:u:1024:16:202F67EC00AA8702:2004-11-05::e: sub:u:2048:16:934F2DC48BF90816:2005-01-05::e: pub:f:1024:17:A5150C15054BDD45:2004-12-13:2006-12-24::-:D* P* [EMAIL PROTECTED]::scESC: sub:f:2048:16:4236A9192FF2FD6E:2004-12-13:2006-12-24:e: pub:f:1024:17:75EFA28019A16E34:2005-01-08:::-:S* B* [EMAIL PROTECTED]::scESC: sub:f:4096:16:F6E5853CD4AC71D5:2005-01-08::e: pub:f:1024:17:83A13C8A1AB3934E:2005-01-30:::-:A* F* [EMAIL PROTECTED]::scESC: sub:f:2048:16:229C25AF3DA3B3AC:2005-01-30::e: pub:f:1024:17:A4E5CCA642713FBC:2005-10-26:::f:R* [EMAIL PROTECTED]::scESC: sub:f:4096:16:3C66685C8655BF0A:2005-10-26::e: So now it is to you to find out why enigmail has a problem with this output. I'd be happy to have this problem solved, since I cannot write any encrypted mails any more... Bye Tobias -- I may disagree with what you have to say, but I shall defend to the death your right to say it. -- Voltaire -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 this. OK, now *I* am the one who is surprised. Having another look at my .fluxbox directory, I see that everything is already at 0600 and working fine nevertheless. Strange. However, I think this bug is to be closed. Sorry for the additional work. Bye Tobias -- Debian GNU/Linux Sarge has been released as stable! -- http://www.debian.de/News/2005/20050606 signature.asc Description: OpenPGP digital signature
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 containing an Umlaut that is definitely in the text, the search fails with Can not find the string [word]. I have no idea where this might come from. Bye Tobias -- Ashes to ashes and clay to clay, if the enemy doesn't get you, your own folks may. signature.asc Description: OpenPGP digital signature
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 behaviour described above. Bye Tobias -- Ashes to ashes and clay to clay, if the enemy doesn't get you, your own folks may. signature.asc Description: OpenPGP digital signature
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 full name of the artist
is appendend instead of the remaining characters. I suppose the error
has its origin in the file id3.h that can be found at
http://cvs.sf.net/viewcvs.py/ripperx/ripperX/src/id3.h?rev=1.2view=markup
There the ID3 tag is defined:
typedef struct id3tag_s {
charmagic[ 3 ];
charsongname[ 30 ];
charartist[ 30 ];
charalbum[ 30 ];
charyear[ 4 ];
charnote[ 28 ];
unsigned char null;
unsigned char track;
unsigned char style;
} id3tag_t;
I don't know about C++ and neither about the rest of the source, but I
believe that at some point, the artist information overwrites all of the
things stored in the memory that should actually belong to the title
information. Somebody able to fix this?
Bye
Tobias
--
Ashes to ashes and clay to clay,
if the enemy doesn't get you, your own folks may.
signature.asc
Description: OpenPGP digital signature
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: session.screen0.followModel Setting default value Failed to read: session.screen0.window.focus.alpha Setting default value Failed to read: session.screen0.window.unfocus.alpha Setting default value Failed to read: session.screen0.menu.alpha Setting default value [...] In the same time, menu transparency did not work (just because the default value == non-transparent was taken), but also changing in the menu itself did not result in any change; after re-opening the menu, it was back at 255. I know resolved this issue and hope that someone who is close to the source can change it appropriately. The thing is that my ~/.fluxbox/init file had 0600 permissions, i.e. only myself could read and write that file. After changing it to 0644, everything - including the fbrun thingy and menu transparency, works fine. I think that somewhere in fluxbox.cc there needs to be a change made. I'm not really familiar with C++ or X programming, but I found the following: (I took the source files from the fluxbox.org-devdocs.) - line 00493: setupConfigFiles() is called which checks the existence of init, menu and keys (I think) with a stat call and creates them if they are non-existing - line 00503: some weird thing with m_fluxbox_pid = XInternAtom(disp, _BLACKBOX_PID, False) is done - line 00521: some more weird stuff happens (weird means that I don't understand it *grin*): pid_t bpid = getpid(); - line 01614: XrmGetFileDatabase() is called to get some kind of database out of the init file I think the last thing is the critical point. http://static.cray-cyber.org/Documentation/NEC_SX_R10_1/G1AE02E/CHAP15.HTML says about XrmGetFileDatabase(): If it cannot open the specified file, XrmGetFileDatabase returns NULL. So I don't exactly know what happens, but this function call seems to use a different user id than the user's one, which is quite a pity. I'd be happy to have that changed by someone :-) Bye Tobias -- Justice through Precision -- Inscription on the AI pyramid signature.asc Description: OpenPGP digital signature
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 | glowing_steel: not enough arguments for function 'plug_in_mblur' at | /usr/lib/gimp/2.0/plug-ins/glowing_steel line 199 (ERROR) This line 199 says: plug_in_mblur($image, $templ, 0, $length, $angle); Now the plug_in_mblur procedure in my version of the Gimp (2.2.4-1) seems to expect an integer value before the $image var that specifies Interactive, non-interactive. I tried fixing this in the script by just inserting an additional zero before $image, but failed with a more perlish error message that I didn't understand. Hope someone can fix this. Bye Tobias - -- I may disagree with what you have to say, but I shall defend to the death your right to say it. ~ -- Voltaire -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCQyGj0JWAx4q8rvURArs5AJ0TH1Xv7KxKXIjPwxiOXio3h2+9swCfbzc6 zzBnIdheUqUEQ81mgM9q7VI= =9lG6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 mozilla-thunderbird-enigmail0.90.0-1 ii mozilla-thunderbird-locale-de 1.0.debian1-1 I suppose the reason of the problem to be that I once upgraded the Enigmail plugin manually from the Extensions dialog. I'd love to remove it from there and use the correct plugin installed systemwide, but this dialog does not give me the option. The field for the Enigmail plugin is drawn in grey with the information: Enigmail 0.86.1 Deactivated - not compatible with Mozilla Thunderbird 1.0 The Deinstall and Update buttons are also drawn in grey, so not available. I manually tried to remove the plugin so the correct one can be used. To do so, I cd'ed to ~/.mozilla-thunderbird/rgt28scp.default/ extensions/ and commented out the part that described the Enigmail plugin in Extensions.rdf. After reloading Thunderbird, the Extensions window showed me 0.90-1 but the functionality was still not available. Since the major bug seems to me that a deactivated plugin cannot be deinstalled, I think this should be fixed. That's also the reason I didn't assign the bug to the mozilla-thunderbird-enigmail package. Bye Tobias -- follow the penguin... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 penguin... signature.asc Description: OpenPGP digital signature
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 normal .deb file. Bye Tobias -- follow the penguin... signature.asc Description: OpenPGP digital signature
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 fluxbox-0.9.11). Except for... well, as I wrote, restarting fluxbox from the RootMenu gives a similar result. At first, it looks like a usual restart, but then X crashes and leaves the end of .xsession-errors as follows: Failed to read: session.forcePseudoTransparency Setting default value Failed to read: session.tabPadding Setting default value Failed to read: session.focusTabMinWidth Setting default value Failed to read: session.appsFile Setting default value Failed to load groupfile: X connection to :0.0 broken (explicit kill or server shutdown). As one may notice, this is exactly what happens at the startup of fluxbox, just that in this case, the X server is killed after Failed to load groupfile. What is that groupfile? /etc/group? BTW, same thing happens when I used Openbox temporarily and then switched back to fluxbox. I don't know whether this problem is still related to fbrun's one, but I'd be happy to solve either one. Bye Tobias -- Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706 - 1790) signature.asc Description: OpenPGP digital signature
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 start? It does exist after deleting. But because it is overwritten each time X restarts, here are some lines from the XFree86.0.log.old that is created after the server shutdown: [EMAIL PROTECTED] $ grep WW /var/log/XFree86.0.log.old (WW) The directory /usr/lib/X11/fonts/cyrillic does not exist. (WW) The directory /usr/lib/X11/fonts/CID does not exist. (WW) Open APM failed (/dev/apm_bios) (No such device) (WW) Open APM failed (/dev/apm_bios) (No such device) (WW) Open APM failed (/dev/apm_bios) (No such device) [EMAIL PROTECTED] $ grep EE /var/log/XFree86.0.log.old (II) Loading extension MIT-SCREEN-SAVER [EMAIL PROTECTED] $ tail -15 /var/log/XFree86.0.log.old (II) NVIDIA(0): Setting mode 1024x768 (II) Configured Mouse: ps2EnableDataReporting: succeeded *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] If not, ~/.xsession-errors should document the crash of the window manager. It does. And unfortunately much other things... Xsession: X session started for tobi at Mo Jan 31 18:11:45 CET 2005 Failed to read: session.forcePseudoTransparency Setting default value Failed to read: session.tabPadding Setting default value Failed to read: session.focusTabMinWidth Setting default value Failed to read: session.appsFile Setting default value Failed to load groupfile: Failed to read: session.screen0.followModel Setting default value Failed to read: session.screen0.window.focus.alpha Setting default value Failed to read: session.screen0.window.unfocus.alpha Setting default value Failed to read: session.screen0.menu.alpha Setting default value BScreen::BScreen: managing screen 0 using visual 0x21, depth 24 Failed to read: session.forcePseudoTransparency Setting default value Failed to read: session.tabPadding Setting default value [... similar messages ...] Failed to read: session.screen0.iconbar.iconTextPadding Setting default value SystemTray::clientMessage(const XClientMessageEvent): SYSTEM_TRAY_REQUEST_DOCK window = event.data.l[2] = 10485787 selected locale: de-DE observe: nothing here: null observe called FILE: [xpconnect wrapped nsIFile]DOUBLE-CLICK: 250 -- -1 THRESHOLD: 8 -- -1 EnigmailAgentPath=/usr/bin/gpg [... enugmail-stuff ...] X connection to :0.0 broken (explicit kill or server shutdown). beep-media-player: Fatal IO error 104 (Die Verbindung wurde vom Kommunikationspartner zurückgesetzt) on X server :0.0. X connection to :0.0 broken (explicit kill or server shutdown). X connection to :0.0 broken (explicit kill or server shutdown). Try grun instead of fbrun. grun works fine. Bye Tobias -- Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706 - 1790) signature.asc Description: OpenPGP digital signature
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. Bye Tobias -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB/UND0JWAx4q8rvURAl7bAJ9qBrQ+ad4944xT+OcCLpt9X6E6mQCeLXk1 Ov/uPJsdsiVie4XVib4rwr0= =xHWU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 window, X crahes/restarts. I tried to run fbrun from a virtual console to be able to read a possible error message with $ fbrun -display :0.0 and get the following: X connection to :0.0 broken (explicit kill or server shutdown). Called without the display parameter from the virtual console gives only a (localized) Speicherzugriffsfehler (memory access error?). The components of my X-Server are of the following version: ii xserver-common4.3.0.dfsg.1-10 ii xserver-xfree86 4.3.0.dfsg.1-10 ii libx11-6 4.3.0.dfsg.1-8 ii libx11-dev4.3.0.dfsg.1-8 ii xlibs 4.3.0.dfsg.1-10 ii xlibs-data4.3.0.dfsg.1-10 Upgrading libx11-6 and libx11-dev to 4.3.0.dfsg.1-10 gives the same result for all described actions. Maybe this is an error of the X-Server however, but I'm not able to say. Bye Tobias -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB8iUw0JWAx4q8rvURAmtxAJ44Y88BDKsVsBDNT2F1FgwKMXJhkgCaAgBh 0thxKKP5AvCgtJsl761PES8= =SOQN -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
