Bug#589206: Current version of lprof segfaults on loading image

Package: lprof Version: 1.11.4.dfsg+1.11.4.1-5 Severity: grave Justification: renders package unusable Lprof will segfault on loading an image. After rebuilding the package this was fixed. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500,

Bug#540040: backintime-kde4: backintime segfaults at startup

Package: backintime-kde4 Version: 0.9.26-1 Severity: grave Justification: renders package unusable This is what I get when I start backintime: :~$ backintime-kde4 /usr/bin/backintime-kde4: line 26: 4035 Segmentatiefout python ${APP_PATH}/app.py $* FWIW: the gnome front-end seems OK on

Bug#494007: linux-image-2.6.26-1-686: In my case adding pci=nomsi makes the system bootable, but ...

Package: linux-image-2.6.26-1-686 Version: 2.6.26-11 Followup-For: Bug #494007 I had exactly the same behaviour when upgrading to 2.6.26. I managed to make my system bootable by adding pci=nomsi to the kernel startup line. However I see the following messages in dmesg: [ 797.309745] +--

Bug#494007: Oops. I commented on the wrong bug....

I meant to provide additional information for bug #497692 Please excuse me and ignore my report! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#450767: security update to zope-cmfplone_2.5.1-4etch1 brakes plone product

Package: zope-cmfplone Version: 2.5.1-4etch1 Severity: grave Tags: security Justification: causes non-serious data loss After upgrding to 2.5.1-4etch1 all my plone instaces are borken. I had to revert to the previuos version, thus preventing a security update. I have included the event log

Bug#450767: The correct event log

Sorry, the event log I attached was not complete. This is what I intended. 2007-11-10T11:05:22 INFO ZServer HTTP server started at Sat Nov 10 11:05:22 2007 Hostname: foo.bar Port: 1235 -- 2007-11-10T11:05:22 INFO Zope Set effective user to foobar -- 2007-11-10T11:05:29 INFO

Bug#450767: I *can* use the hotfix directly from plone.org

Some additional info: If I install the hotfix directly from the plone.org site into the instance/Products directly, everything works fine. Yours, Gerrit Jan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#391758: plone-cms: No upgrade path for 2.1 to 2.5

Package: plone-cms Version: cmfplone Severity: grave Justification: causes non-serious data loss After upgrading to plone-2.5 all my 2.1 instaces are gone. The upgrade causes zope 2.9 to be installed, and updates plone packages in zope2.8 instances. This leaves a non-functional system. The