Bug#478067: libcharles0-dev: fatal error: file charles.ali is incorrectly formatted

Package: libcharles0-dev Version: 0.0.20050217-3 Severity: grave Justification: renders package unusable When compiling a program with gcc-4.1 that uses libcharles I get: fatal error: file charles.ali is incorrectly formatted make sure you are using consistent versions of gcc-4.1/gnatbind 8.

Bug#477491: python-moinmoin: to users with migration problems

Package: python-moinmoin Followup-For: Bug #477491 To users that have problems migrating to 1.6.2 please read: http://moinmo.in/MoinMoinQuestions/Installing#head-4ec490413fb10319dba1cf9f511fc63c2ac69569 http://moinmo.in/ThomasWaldmann/AnotherWayToMigrateFrom1.5To1.6 the moinmoin mailinglist or

Bug#451405: sylpheed: Sylpheed crashes if you enter the Sent, Drafts or Queue folder

Package: sylpheed Version: 2.4.7-1 Followup-For: Bug #451405 There are still bugs with sylpheed even if you change the sylpheedrc file. Now sylpheed crashes every time I try to enter the following folders: Sent Drafts Queue -- System Information: Debian Release: lenn

Bug#451405: sylpheed: Found the bug

Package: sylpheed Version: 2.4.7-1 Followup-For: Bug #451405 Sylpheed does not segmentation faults if the .sylpheed-2.0/sylpheedrc file contains the following lines: summary_col_pos_mark=0 summary_col_pos_unread=1 summary_col_pos_mime=2 summary_col_pos_subject=3 summary_col_pos_from=4 summary_c

Bug#451405: sylpheed: Segmentation fault

Package: sylpheed Version: 2.4.7-1 Followup-For: Bug #451405 After upgrading yesterday sylpheed seg faults for me too. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22-1-k7 (S

Bug#377432: pida: Works when installing python-setuptools

Package: pida Version: 0.3.1-1 Followup-For: Bug #377432 It works now, so I guess the pida package must be upgraded for the right version of python-setuptools Thanks -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') A

Bug#377432: pida: Won't start

Package: pida Version: 0.3.1-1 Severity: grave Justification: renders package unusable When staring pida all I get is: Traceback (most recent call last): File "/usr/bin/pida", line 5, in ? from pkg_resources import load_entry_point ImportError: No module named pkg_resources -- System In

Bug#369828: inkscape: Same problem with futex

On Mon, 12 Jun 2006 21:50:00 +0200 Wolfram Quester <[EMAIL PROTECTED]> wrote: > Hi randhol, > > On Wed, Jun 07, 2006 at 05:39:53PM +0200, Wolfram Quester wrote: > > Hi, > > > > On Sat, Jun 03, 2006 at 06:09:38PM +0200, randhol wrote: > > > Package: ink

Bug#369828: inkscape: Same problem with futex

Package: inkscape Version: 0.43-4 Followup-For: Bug #369828 I have the same problem with both versions: 0.43-4 and 0.43-5. I tried to remove the content of the extension directory, but it didn't work. Got sigsevs then. I wish there was a way to rollback to the previous version that worked. Now I

Bug#362112: Problem solved

At least for the Norwegian keyboard layout. I had chosen to install the xkb-data package, but at the bugreport I saw that it wasn't for some reason. So I installed xkb-data again and now the keyboard seems to work for me. HTH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "un

Bug#362112: xserver-xorg: Same problem with Norwegian keyboard

Package: xserver-xorg Version: 1:7.0.10 Followup-For: Bug #362112 I have the exact same problem with the Norwegian keyboard. Is there a quick hack as I really need the Alt Gr to work... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable')