I also experience this bug, but I'm glad I can contribute! I tried your packages. After installing them, I did System > Preferences > Screensaver > Molecule. Outcome was the same as reported above. Mouse is moveable and num-lock is changeable, but that's it. Xorg.2.log of this session is attached.
I was going to do another run and get a backtrace with gdm, but the screensaver started to work the second time (after a hard kill of Xorg). So I re-booted from the Live-CD, and went for the gdb-backtrace the first time the screensaver would run. This time, I enabled NoTrapSignals. Corresponding log is Xorg.1.log and the gdb backtrace is in gdb_backtrace_2:1.5.2-2ubuntu3.txt. Yes, I forgot to upgrade to your packages, so this backtrace is for 2:1.5.2-2ubuntu3.
So, in yet another live session (the screensaver is running fine the second time Xorg is run with 2:1.5.2-2ubuntu3 too (I tried to unload the kernel modules drm and r128 but I could not do that, something was still using it)), also with NoTrapSignals, the gdb backtrace was done with 2:1.5.3~git-1ubuntu0tormod4. Log attached als Xorg.0.log and the gdb backtrace as gdb_backtrace_2:1.5.3~git-1ubuntu0tormod4.txt
I also experience this bug, but I'm glad I can contribute! I tried your packages. After installing them, I did System > Preferences > Screensaver > Molecule. Outcome was the same as reported above. Mouse is moveable and num-lock is changeable, but that's it. Xorg.2.log of this session is attached.
I was going to do another run and get a backtrace with gdm, but the screensaver started to work the second time (after a hard kill of Xorg). So I re-booted from the Live-CD, and went for the gdb-backtrace the first time the screensaver would run. This time, I enabled NoTrapSignals. Corresponding log is Xorg.1.log and the gdb backtrace is in gdb_backtrace_ 2:1.5.2- 2ubuntu3. txt. Yes, I forgot to upgrade to your packages, so this backtrace is for 2:1.5.2-2ubuntu3.
So, in yet another live session (the screensaver is running fine the second time Xorg is run with 2:1.5.2-2ubuntu3 too (I tried to unload the kernel modules drm and r128 but I could not do that, something was still using it)), also with NoTrapSignals, the gdb backtrace was done with 2:1.5.3~ git-1ubuntu0tor mod4. Log attached als Xorg.0.log and the gdb backtrace as gdb_backtrace_ 2:1.5.3~ git-1ubuntu0tor mod4.txt
ubuntu@ubuntu:~$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS [1002:5046]
Hope this helps upstream find the bug!