@Adam, Please have a look at bug 916295 and see if your access violation goes away if you start tuxcmd with LIBOVERLAY_SCROLLBAR=0
e.g. LIBOVERLAY_SCROLLBAR=0 tuxcmd or export LIBOVERLAY_SCROLLBAR=0 tuxcmd If that does not help, please start tuxcmd with --debug and attach the output. I still say that you hijacked this bug report. Unfortunately, I can not reproduce the bug myself anymore as I moved on from Lucid and it seems that in the dependency tree something got changed and the exception is not created anymore if I run the i386 package from lucid [1] in my current environment (Debian Wheezy). Anyway I think my original bug should be closed as 0.6.70+dfsg-2 entered the current Ubuntu development tree. [1] https://launchpad.net/ubuntu/+source/tuxcmd/0.6.70+dfsg-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/577728 Title: tuxcmd - Tux Commander does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tuxcmd/+bug/577728/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
