abrt 1.0.0 detected a crash. How to reproduce ----- 1. Type "xlock -mode juggle -nolock" Comment: Crashes every time. Also crashes without -nolock, and (naturally) with "-mode random" if this mode happens to be selected. Attached file: backtrace cmdline: xlock -mode juggle -nolock component: xlockmore executable: /usr/bin/xlock kernel: 2.6.31.6-162.fc12.x86_64 package: xlockmore-5.28-1.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 377470 [details] File: backtrace
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still crashes on xlockmore-5.28-2.fc14.x86_64 - same line numbers in the traceback.
The critical piece of info here would be that I have two logical screens. I believe the crash is because although init_juggle recognises the possibility of multiple screens and allocates them accordingly, it only initialises the data for the current screen. So when draw_juggle tries to draw the other screen, the info is still blank: (gdb) print *mi $1 = {windowinfo = {display = 0xa42180, screenptr = 0xa56780, screen = 1, real_screen = 1, num_screens = 2, max_screens = 2, window = 85983246, width = 1600, height = 1200, flags = 8289, delta3d = 1.5, is_drawn = 1}, screeninfo = 0xa5c498, runinfo = {pause = 0, delay = 10000, count = 200, cycles = 1000, size = 1, ncolors = 64, saturation = 1, bitmap = 0x0}, lockstruct = 0x7a0480} (gdb) print *sp $2 = {scale = 2.5, wander = 0x0, cx = 0, Gr = 0, head = 0x0, arm = {{{{x = 0, y = 0}, {x = 0, y = 0}, {x = 0, y = 0}}, {{x = 0, y = 0}, {x = 0, y = 0}, {x = 0, y = 0}}}, {{{x = 0, y = 0}, {x = 0, y = 0}, {x = 0, y = 0}}, {{x = 0, y = 0}, {x = 0, y = 0}, {x = 0, y = 0}}}}, pattern = 0x0, count = 0, num_balls = 0, begintime = 0, time = 1950980977, objtypes = BALL, objects = 0x0}
I am updating xlockmore to the latest upstream version. Can you please test it (once it appears in the testing repository) to see if that fixes your bug.
xlockmore-5.31-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/xlockmore-5.31-1.fc14
Does not seem to be fixed in xlockmore-5.31-1.fc14, I'm afraid.
xlockmore-5.31-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xlockmore'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/xlockmore-5.31-1.fc14
xlockmore-5.31-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
Updated to xlockmore-5.38-1.fc18. Cannot get it to crash with "xlock -mode juggle -nolock" with one or two monitors attached. Thanks for the report. Closing it again and hoping this time it is really fixed.