FS#26648 - [conky] Segmentation fault when executing python-script

Attached to Project: Arch Linux
Opened by H.pferd (stosch) - Thursday, 27 October 2011, 17:01 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 02 November 2011, 11:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Since the conky update to conky 1.8.2git20111026-1 I get a segmentation fault caused by the following line:
${execpi 300 /path/to/pythonscript.py}
I never experienced similar problems before.
There are some people in the forum with similar problems:
https://bbs.archlinux.org/viewtopic.php?id=118486
Downgrading to conky 1.8.1-3 solves it for me.


Additional info:
conky 1.8.2git20111026-1
error message from dmesg: conky[3259]: segfault at 0 ip b72aadb8 sp bfee28d8 error 4 in libc-2.14.so[b7235000+162000]


Steps to reproduce:
Execute a script via ${execpi 300 /path/to/pythonscript.py}
This task depends upon

Closed by  Gaetan Bisson (vesath)
Wednesday, 02 November 2011, 11:29 GMT
Reason for closing:  Works for me
Comment by Gaetan Bisson (vesath) - Thursday, 27 October 2011, 21:40 GMT
Executing a simple python script that computes 1+2 works for me. Do segfaults occur after some time? Can you reduce that time?
Can you also give me a minimal example of conkyrc and python script that reproduce this bug?
Comment by H.pferd (stosch) - Sunday, 30 October 2011, 17:50 GMT
Conky is in autostart an crashes immediately.
I attached the important part of my conkyrc and the python-script.
   conkyrcpublic (0.6 KiB)
   update.py (6.6 KiB)
Comment by Gaetan Bisson (vesath) - Monday, 31 October 2011, 03:36 GMT
That is not what I call a *minimal* example; besides, this script is incompatible with recent pacman versions: it assumes the path /var/lib/pacman/sync/repo/package/desc while all that information is now stored in a tarball named /var/lib/pacman/sync/repo.db instead. Is your system fully up-to-date?
Comment by H.pferd (stosch) - Wednesday, 02 November 2011, 11:16 GMT
Yes, of course my system is up to date. But the python script is pretty old and I haven't looked into it. As there were no problems with previous conkyversions I thought it might be worth reporting a bug, especially because some people in the forum reported similar issues. Well as nobody else seems to have problems I suggest closing this report as I won't have time to look into the python script and detecting the failure in the next weeks.
Comment by Gaetan Bisson (vesath) - Wednesday, 02 November 2011, 11:29 GMT
Alright. Do not hesitate to create a new bug report if you manage to isolate that bug in the future.

Loading...