tuxcmd - Tux Commander does not start

[Paul Gevers]

!!! If the "LIBOVERLAY_SCROLLBAR=0 tuxcmd" workaround is working for you then please refer to bug #916295. This bug is about another issue. !!!

To get in compliance with https://wiki.ubuntu.com/StableReleaseUpdates#Procedure:

1) Currently tuxcmd does not run on i386, it gets an Access Violation (see below) ( I just asked on IRC and it DOES run on amd64).
2) The problem is NOT in tuxcmd source but was a bug in the compiler: see bug 529469 which was fixed in Lucid, but tuxcmd was not rebuild to incorporate the bugfix.
3) To fix this issue no patching is necessary, rebuilding should fix it, as confirmed by my PPA build.
4) Reproducing the bug is as easy as starting tuxcmd from command prompt on a i386.
5) As no code is changing for tuxcmd the chances of regression are small.

=======
Original bug report:

Binary package hint: tuxcmd

After installing tuxcmd I get the following when running tuxcmd from command line. I had a similar problem during the process of getting winff ready for Lucid (bug 521818), so recompiling might be all that is necessary. I will try to test and report back here.

paul@stromboli ~ $ tuxcmd
An unhandled exception occurred at $0012EE06 :
EAccessViolation : Access violation
  $0012EE06
  $00130DB4
  $00131256
  $0011F631
  $0011BF8F
  $00122C63
  $00513E28
  $001282D8
  $001198B9
  $0011B252
  $0012F5E6
  $00130DB4
  $00131256
  $00511C9B
  $00511DB7
  $00511ECA
  $0011D8BF

An unhandled exception occurred at $081117FF :
EAccessViolation : Access violation
  $081117FF
  $0811B9BF
  $08111802
  $08111C19

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: tuxcmd 0.6.70+dfsg-1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Sun May 9 10:07:54 2010
InstallationMedia: Kubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100112.2)
ProcEnviron:
 LC_TIME=nl_NL.UTF-8
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: tuxcmd

[Paul Gevers (paul-climbing)]

Rebuilding does solve the problem as can be seen with the .deb file from my testing ppa (https://launchpad.net/~paul-climbing/+archive/testing-area).

However, if you are using KDE with qtcurve theme, you will be suffering from bug 528872 and get an invalid floating point error, this is unrelated to the tuxcmd issue.

Please rebuild tuxcmd.

paul@stromboli ~ $ tuxcmd
An unhandled exception occurred at $00C61761 :
EInvalidOp : Invalid floating point operation
  $00C61761
  $00C7E3BC
  $0086BFA1
  $00900020
  $00901C29
  $007EA2F4
  $001AF8B9
  $001B1252
  $001C55E6
  $001C6C33
  $001C7256
  $00917306
  $007E3FEB
  $0014B80B
  $0014B7BA
  $0014B7BA
  $00174964

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[ssuuddoo (ssuuddoo)]

hmmm, thnx a lot. I've downloaded the deb file, reinstalled and the access violation is still present. sys ubuntu i386, 12.04

[Paul Gevers (paul-climbing)]

@ssuuddoo
where did you download the deb file from? You should hardly ever have to do that.

If you downloaded the deb file in the Ubuntu archive, you just confirm that this bug exists. If you want a fixed deb file, you can get it in my testing PPA [1] (build for Lucid, but also in Ubuntu it has not been rebuild which is why the problem is still there).

[1] https://launchpad.net/~paul-climbing/+archive/testing-area

[Kevin Williams (bthylafh)]

This bug (or one like it) exists for 12.04 AMD64. I have a fresh install in Virtualbox.

tuxcmd gives this error at launch:

(II) GVFS: is_active = 1
(II) GVFS: supported schemes: file;ftp;computer;obex;davs;dav;trash;smb;afp;cdda;archive;sftp;ssh;http;dns-sd;davs+sd;dav+sd;burn;afc;gphoto2;network;localtest
An unhandled exception occurred at $00007F7683190558 :
EAccessViolation : Access violation
  $00007F7683190558
  $00007F7683199242

An unhandled exception occurred at $0000000011580061 :
EAccessViolation : Access violation
  $0000000011580061
  $000000000054579D
  $0000000000536FD9

[Paul Gevers (paul-climbing)]

Could you try and install tuxcmd from my ppa as discussed in comment #2
and #5? If it runs, the bug is the same, but somehow I expect that it is
a different issue with the same error message.

Paul

[Bambitroll (juan-btcorp)]

Hi Paul,

Ref #7, I just downloaded tuxcmd from your ppa and installed it on my Ubuntu 12.04 64bit and I still get this when I start it:
~$ tuxcmd
/home/me/.gtkrc-2.0:7: error: invalid string constant "user-font", expected valid string constant
An unhandled exception occurred at $00007F542D094558 :
EAccessViolation : Access violation
  $00007F542D094558
  $00007F542D09D242

An unhandled exception occurred at $000000002C180061 :
EAccessViolation : Access violation
  $000000002C180061
  $0000000000540841
  $00000000005335C2

I also tried to compile it from source but I get the following error:
Compiling ./libgtk_kylix/GTKForms.pas
Fatal: Can't find unit gtk2 used by GTKForms
Fatal: Compilation aborted

Any idea what I am missing??

Thanks for your help!

JM.

[Bambitroll (juan-btcorp)]

Hi again,

I managed to compile tuxcmd from source but still get the same problem! :(

JM.

[Paul Gevers (paul-climbing)]

@ Bambitroll

Please fill a new bug for this, your issue is different. As clearly stated in the initial bug: "( I just asked on IRC and it DOES run on amd64)". So in the time of creation of this issue, 64 bit was running fine. And originally rebuilding fixed the problem.

[Adam Niedling (krychek)]

Tuxcmd on Ubuntu 13.04 64bit:

$ tuxcmd
An unhandled exception occurred at $00007FCFF22AE190 :
EAccessViolation : Access violation
  $00007FCFF22AE190

An unhandled exception occurred at $0000000011580061 :
EAccessViolation : Access violation
  $0000000011580061
  $000000000054579D
  $0000000000536FD9

Paul: I don't see why a separate bug report is needed for 64bit. Usually there is no need for reporting two bugs for the same faulty behavior.

[Paul Gevers (paul-climbing)]

On 30-07-13 21:27, Adam Niedling wrote:
> Paul: I don't see why a separate bug report is needed for 64bit. Usually
> there is no need for reporting two bugs for the same faulty behavior.

Because I believe that the bug is different. Maybe the error message is
the same, but I really expect the source code that caused the original
bug to be different. The original bug was not a bug in the tuxcmd
package and only manifested itself on i386, while later a bug on amd64
was reported. Nobody investigated that latter bug though, a proper
backtrace with debugging symbols would help.

Paul

[Adam Niedling (krychek)]

There is already a bug that was reported for x64 and it was set as duplicate of this bug. There is no point in issuing yet another report as it will be set as duplicate just like the other one.
Since no developer has looked into this issue since 2010 I really don't see why we can't treat this report as a general "tuxcmd won't even start" bug instead of fractioning it into tiny pieces.
The title of this bug should be "Tuxcmd does not start!!!". Maybe it would draw more attention.

[Adam Niedling (krychek)]

I'm changing the title of this bug. If it gets fixed for you but not for me THEN I will open a separate bug report.

[Paul Gevers (paul-climbing)]

@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

[Adam Niedling (krychek)]

I wasn't aware of bug #916295. You are right, "LIBOVERLAY_SCROLLBAR=0 tuxcmd" is working for me. It would have been worth indicating in the bug description that this bug exists. Also the duplicates of this bug might actually be the duplicates of bug #916295.

Hijacking is still an overstatement, I merely changed the title. The description and everything else remained the same.

But if this problem does not occur in any later version of Ubuntu then I think it should be closed as Fix Released.

[Merlinpilot (nigel-talbot)]

Still affecting me with 12.04 LTS. "LIBOVERLAY_SCROLLBAR=0 tuxcmd" works.

[Adam Niedling (krychek)]

Merlinpilot: Then you have a different problem. You are being affected by bug #916295.

[Merlinpilot (nigel-talbot)]

Adam: Thank you for the information - I'm not expert enough to add anything particularly worthwhile to the process, but will take a look at the other bug.