Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12268 - Imlib2 update broke pypanel
Attached to Project:
Community Packages
Opened by Florian Pritz (bluewind) - Friday, 28 November 2008, 13:04 GMT
Last edited by Ronald van Haren (pressh) - Tuesday, 02 December 2008, 10:16 GMT
Opened by Florian Pritz (bluewind) - Friday, 28 November 2008, 13:04 GMT
Last edited by Ronald van Haren (pressh) - Tuesday, 02 December 2008, 10:16 GMT
|
DetailsDescription:
Update from imlib2 1.4.1-2 to 1.4.2.-1 causes a general protection fault when starting pypanel. Downgrading fixed it. Message in dmesg: pypanel[26509] general protection ip:7f6f5bf6d3bf sp:7fff66263f48 error:0 in libImlib2.so.1.4.2[7f6f5bf21000+66000] Additional info: pypanel 2.4-4 imlib2 1.4.2.-1 Steps to reproduce: Install pypanel and imlib2. Start pypanel. |
This task depends upon
Closed by Ronald van Haren (pressh)
Tuesday, 02 December 2008, 10:16 GMT
Reason for closing: Fixed
Additional comments about closing: I think it should be fixed with imlib2 1.4.2-2. If not please re-open.
Tuesday, 02 December 2008, 10:16 GMT
Reason for closing: Fixed
Additional comments about closing: I think it should be fixed with imlib2 1.4.2-2. If not please re-open.
Immediate seg fault upon starting the program.
imlib2 version
pypanel working / non-working
CPU type & model
i686 / x86_64
Python version
If you did a full 'pacman -Syu' or selective upgrade
Either way, pypanel is not maintained upstream for some years now so things like this are bound to happen at some time.
someone can confirm the same issue on i686?