| 2010-05-09 08:20:16 |
Paul Gevers |
bug |
|
|
added bug |
| 2010-05-09 08:20:16 |
Paul Gevers |
attachment added |
|
Dependencies.txt http://launchpadlibrarian.net/48106401/Dependencies.txt |
|
| 2010-05-19 20:32:25 |
Paul Gevers |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-05-20 19:13:14 |
Paul Gevers |
description |
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, 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 |
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 29469 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
|
|
| 2012-04-14 08:10:06 |
Launchpad Janitor |
tuxcmd (Ubuntu): status |
New |
Confirmed |
|
| 2012-04-14 08:13:54 |
Benjamin Schmid |
tags |
apport-bug i386 lucid |
apport-bug i386 lucid patch precise |
|
| 2012-04-15 19:10:41 |
Hans Joachim Desserud |
summary |
[lucid] tuxcmd: Access violation on i386 |
tuxcmd: Access violation on i386 |
|
| 2012-04-15 19:10:56 |
Hans Joachim Desserud |
tags |
apport-bug i386 lucid patch precise |
apport-bug i386 lucid natty oneiric patch precise |
|
| 2012-05-03 16:10:12 |
Lorem |
bug |
|
|
added subscriber Lorem |
| 2012-07-08 20:00:41 |
Bambitroll |
bug |
|
|
added subscriber Bambitroll |
| 2012-07-09 10:42:20 |
Bambitroll |
removed subscriber Bambitroll |
|
|
|
| 2012-07-09 21:19:54 |
Paul Gevers |
description |
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 29469 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
|
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 |
|
| 2012-07-24 22:43:01 |
Merlinpilot |
bug |
|
|
added subscriber Merlinpilot |
| 2013-07-30 19:24:15 |
Adam Niedling |
bug |
|
|
added subscriber Adam Niedling |
| 2013-08-01 18:56:16 |
Adam Niedling |
summary |
tuxcmd: Access violation on i386 |
tuxcmd - Tux Commander does not start |
|
| 2013-08-04 17:05:40 |
Adam Niedling |
description |
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 |
!!! 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 |
|
| 2014-01-22 16:56:17 |
mahmoud |
bug |
|
|
added subscriber mahmoud |
