| 2012-02-20 17:12:33 |
Dmitri Bachtin |
bug |
|
|
added bug |
| 2012-03-19 11:17:48 |
Launchpad Janitor |
gosmore (Ubuntu): status |
New |
Confirmed |
|
| 2012-05-01 14:01:17 |
walterav |
tags |
amd64 apport-bug precise |
amd64 apport-bug gosmore precise |
|
| 2012-05-30 14:44:50 |
Kees Klop |
bug |
|
|
added subscriber Kees Klop |
| 2012-06-06 08:29:24 |
Steffen Krumbholz |
bug |
|
|
added subscriber Steffen Krumbholz |
| 2012-06-16 22:48:01 |
Julian Taylor |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652084 |
|
| 2012-06-16 22:48:01 |
Julian Taylor |
bug task added |
|
gosmore (Debian) |
|
| 2012-06-16 23:31:15 |
Bug Watch Updater |
gosmore (Debian): status |
Unknown |
New |
|
| 2012-06-17 23:59:16 |
Bug Watch Updater |
gosmore (Debian): status |
New |
Confirmed |
|
| 2012-06-30 18:35:13 |
Launchpad Janitor |
gosmore (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2012-06-30 18:41:39 |
Julian Taylor |
bug |
|
|
added subscriber Julian Taylor |
| 2012-06-30 19:11:58 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/gosmore |
|
| 2012-06-30 19:21:34 |
Julian Taylor |
nominated for series |
|
Ubuntu Precise |
|
| 2012-06-30 19:21:34 |
Julian Taylor |
bug task added |
|
gosmore (Ubuntu Precise) |
|
| 2012-08-27 18:17:50 |
Launchpad Janitor |
gosmore (Ubuntu Precise): status |
New |
Confirmed |
|
| 2012-08-27 18:58:25 |
Julian Taylor |
description |
Installed gosmore on fresh 12.04 machine.
1. Started gosmore - nothing happened.
2. Checked ps - gosmore is inside the proc list. Killed it.
3. Started gosmore. Console output:
$ LC_ALL="C" gosmore
gosmore is in the public domain and comes without warranty
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
[END OF CONSOLE OUTPUT]
4. One can sigint gosmore from here.
4.a. Expected result: something should happen, I've never used this software before.
Will recompile it with symbols and return with more info.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gosmore 0.0.0.20100711-2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 20 18:08:36 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120220)
SourcePackage: gosmore
UpgradeStatus: No upgrade log present (probably fresh install) |
Impact:
gosmore goes into a busy loop when starting, just using 100% cpu and doing nothing
It is caused by a strict aliasing violation in the code, just disabling strict aliasing optimizations is the simplest solution until we get something better from upstream.
TEST CASE:
start gosmore
if a window shows up it works, if it just eats 100% not
regression potential:
only disable an optimization flag, fixes a completely broken package, should not cause issues besides maybe some minor performance regressions which are acceptable compared to the current state.
original report:
Installed gosmore on fresh 12.04 machine.
1. Started gosmore - nothing happened.
2. Checked ps - gosmore is inside the proc list. Killed it.
3. Started gosmore. Console output:
$ LC_ALL="C" gosmore
gosmore is in the public domain and comes without warranty
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
[END OF CONSOLE OUTPUT]
4. One can sigint gosmore from here.
4.a. Expected result: something should happen, I've never used this software before.
Will recompile it with symbols and return with more info.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gosmore 0.0.0.20100711-2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 20 18:08:36 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120220)
SourcePackage: gosmore
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2012-08-27 19:02:29 |
Julian Taylor |
description |
Impact:
gosmore goes into a busy loop when starting, just using 100% cpu and doing nothing
It is caused by a strict aliasing violation in the code, just disabling strict aliasing optimizations is the simplest solution until we get something better from upstream.
TEST CASE:
start gosmore
if a window shows up it works, if it just eats 100% not
regression potential:
only disable an optimization flag, fixes a completely broken package, should not cause issues besides maybe some minor performance regressions which are acceptable compared to the current state.
original report:
Installed gosmore on fresh 12.04 machine.
1. Started gosmore - nothing happened.
2. Checked ps - gosmore is inside the proc list. Killed it.
3. Started gosmore. Console output:
$ LC_ALL="C" gosmore
gosmore is in the public domain and comes without warranty
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
[END OF CONSOLE OUTPUT]
4. One can sigint gosmore from here.
4.a. Expected result: something should happen, I've never used this software before.
Will recompile it with symbols and return with more info.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gosmore 0.0.0.20100711-2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 20 18:08:36 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120220)
SourcePackage: gosmore
UpgradeStatus: No upgrade log present (probably fresh install) |
Impact:
gosmore goes into a busy loop when starting, just using 100% cpu and doing nothing
It is caused by a strict overflow violation in the code, just disabling strict overflow optimizations is the simplest solution until we get something better from upstream.
TEST CASE:
start gosmore
if a window shows up it works, if it just eats 100% not
regression potential:
only disable an optimization flag, fixes a completely broken package, should not cause issues besides maybe some minor performance regressions which are acceptable compared to the current state.
original report:
Installed gosmore on fresh 12.04 machine.
1. Started gosmore - nothing happened.
2. Checked ps - gosmore is inside the proc list. Killed it.
3. Started gosmore. Console output:
$ LC_ALL="C" gosmore
gosmore is in the public domain and comes without warranty
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
[END OF CONSOLE OUTPUT]
4. One can sigint gosmore from here.
4.a. Expected result: something should happen, I've never used this software before.
Will recompile it with symbols and return with more info.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gosmore 0.0.0.20100711-2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 20 18:08:36 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120220)
SourcePackage: gosmore
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2012-08-27 19:11:13 |
Julian Taylor |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-09-08 14:53:57 |
Scott Kitterman |
gosmore (Ubuntu Precise): status |
Confirmed |
Fix Committed |
|
| 2012-09-08 14:54:02 |
Scott Kitterman |
bug |
|
|
added subscriber SRU Verification |
| 2012-09-08 14:54:09 |
Scott Kitterman |
tags |
amd64 apport-bug gosmore precise |
amd64 apport-bug gosmore precise verification-needed |
|
| 2012-09-08 15:14:12 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/precise/gosmore/precise-proposed |
|
| 2012-09-18 22:29:54 |
Launchpad Janitor |
branch linked |
|
lp:debian/gosmore |
|
| 2012-09-19 11:58:41 |
Bug Watch Updater |
gosmore (Debian): status |
Confirmed |
Fix Released |
|
| 2012-09-22 12:46:45 |
Alan Pope 🍺🐧🐱 🦄 |
tags |
amd64 apport-bug gosmore precise verification-needed |
amd64 apport-bug gosmore precise verification-done |
|
| 2012-09-22 23:24:25 |
Colin Watson |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2012-09-22 23:25:16 |
Launchpad Janitor |
gosmore (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2012-09-29 04:48:13 |
Launchpad Janitor |
branch linked |
|
lp:debian/wheezy/gosmore |
|
