Bug#507382: gourmet: Crashes just after starting

2008-11-30 Thread Mattia Monga
Package: gourmet Version: 0.14.2-1 Severity: grave Justification: renders package unusable The program crashes before showing the main window. Attached you can find the error trace. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'te

Bug#507382: gourmet: Crashes just after starting

2008-11-30 Thread Rolf Leggewie
Mattia Monga wrote: Package: gourmet Version: 0.14.2-1 Severity: grave Justification: renders package unusable The program crashes before showing the main window. Attached you can find the error trace. Mattia, thank you for your report. Sorry to hear you are experiencing trouble. FWIW,

Bug#507382: gourmet: Crashes just after starting

2008-11-30 Thread Mattia Monga
On Sun, Nov 30, 2008 at 8:37 PM, Rolf Leggewie <[EMAIL PROTECTED]> wrote: > Mattia Monga wrote: >> >> Package: gourmet >> Version: 0.14.2-1 >> Severity: grave >> Justification: renders package unusable >> >> The program crashes before showing the main window. Attached you can find >> the error trac

Bug#507382: gourmet: Crashes just after starting

2008-11-30 Thread Rolf Leggewie
Mattia, thank you for the quick response. I apologize if my terminology was misleading. I was not suggesting that this is a problem with environment settings. Can you please include the information I requested in my earlier mail in your next reply? Thank you. Regards Rolf -- To UNSUB

Bug#507382: gourmet: Crashes just after starting

2008-11-30 Thread Mattia Monga
> May I ask you to let me know if you just installed this program, upgraded > from the previous debian version 0.14.0 or from another version supplied by > upstream? I could have tried a previous version (0.13.7, not in the official Debian repository) some time ago. I still get an error after a $

Bug#507382: gourmet: Crashes just after starting

2008-12-24 Thread Jonathan Wiltshire
I also see this behaviour, and it is because the intial data imported has the Spanish ~n character in it. A patch is attached that fixes this for my locales, en and en_GB, by replacing the character with a regular 'n'. -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA