| 2014-03-26 14:06:26 |
Cliff Carson |
bug |
|
|
added bug |
| 2014-03-26 14:12:33 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for Ubuntu packages |
| 2014-03-26 14:12:36 |
Apport retracing service |
attachment added |
|
Stacktrace.txt https://bugs.launchpad.net/bugs/1297872/+attachment/4045021/+files/Stacktrace.txt |
|
| 2014-03-26 14:12:37 |
Apport retracing service |
attachment added |
|
StacktraceSource.txt https://bugs.launchpad.net/bugs/1297872/+attachment/4045022/+files/StacktraceSource.txt |
|
| 2014-03-26 14:12:39 |
Apport retracing service |
attachment added |
|
ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1297872/+attachment/4045023/+files/ThreadStacktrace.txt |
|
| 2014-03-26 14:12:42 |
Apport retracing service |
attachment removed |
CoreDump.gz https://bugs.launchpad.net/bugs/1297872/+attachment/4045013/+files/CoreDump.gz |
|
|
| 2014-03-26 14:12:43 |
Apport retracing service |
osmo (Ubuntu): importance |
Undecided |
Medium |
|
| 2014-03-26 14:12:46 |
Apport retracing service |
tags |
amd64 apport-crash need-amd64-retrace trusty |
amd64 apport-crash trusty |
|
| 2014-03-31 20:37:44 |
Cliff Carson |
description |
Updating a previously saved Note and got this error after saving then using the Quit button.
The Osmo window was "stuck" in maximized mode. Could not figure out how to get it into window mode. May not be an Osmo problem because the shortcut keys for maximize/minimize (alt-F9/alt-F10 or alt-F5)don't seem to work on any window.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: osmo 0.2.10+svn937-1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Mar 26 09:58:00 2014
ExecutablePath: /usr/bin/osmo
InstallationDate: Installed on 2014-02-13 (40 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140211)
ProcCmdline: osmo
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f341238a64d: lock xadd %edx,(%rax)
PC (0x7f341238a64d) ok
source "%edx" ok
destination "(%rax)" (0xfffffffffffffff8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: osmo
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
PluginConfig::~PluginConfig() () from /usr/lib/pipelight/libpipelight-silverlight5.1.so
__run_exit_handlers (status=0, listp=0x7f341aa476c8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
__GI_exit (status=<optimized out>) at exit.c:104
Title: osmo crashed with SIGSEGV in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
This bug report is trying to document a problem between Osmo and Pipelight.
Updating a previously saved Note and got this error after saving then using the Quit button.
The Osmo window was "stuck" in maximized mode. Could not figure out how to get it into window mode. May not be an Osmo problem because the shortcut keys for maximize/minimize (alt-F9/alt-F10 or alt-F5)don't seem to work on any window.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: osmo 0.2.10+svn937-1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Mar 26 09:58:00 2014
ExecutablePath: /usr/bin/osmo
InstallationDate: Installed on 2014-02-13 (40 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140211)
ProcCmdline: osmo
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f341238a64d: lock xadd %edx,(%rax)
PC (0x7f341238a64d) ok
source "%edx" ok
destination "(%rax)" (0xfffffffffffffff8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: osmo
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
PluginConfig::~PluginConfig() () from /usr/lib/pipelight/libpipelight-silverlight5.1.so
__run_exit_handlers (status=0, listp=0x7f341aa476c8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
__GI_exit (status=<optimized out>) at exit.c:104
Title: osmo crashed with SIGSEGV in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2014-03-31 21:58:38 |
Cliff Carson |
description |
This bug report is trying to document a problem between Osmo and Pipelight.
Updating a previously saved Note and got this error after saving then using the Quit button.
The Osmo window was "stuck" in maximized mode. Could not figure out how to get it into window mode. May not be an Osmo problem because the shortcut keys for maximize/minimize (alt-F9/alt-F10 or alt-F5)don't seem to work on any window.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: osmo 0.2.10+svn937-1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Mar 26 09:58:00 2014
ExecutablePath: /usr/bin/osmo
InstallationDate: Installed on 2014-02-13 (40 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140211)
ProcCmdline: osmo
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f341238a64d: lock xadd %edx,(%rax)
PC (0x7f341238a64d) ok
source "%edx" ok
destination "(%rax)" (0xfffffffffffffff8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: osmo
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
PluginConfig::~PluginConfig() () from /usr/lib/pipelight/libpipelight-silverlight5.1.so
__run_exit_handlers (status=0, listp=0x7f341aa476c8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
__GI_exit (status=<optimized out>) at exit.c:104
Title: osmo crashed with SIGSEGV in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
This bug report is trying to document a problem between Osmo and Pipelight.
After installation of Pipeline starting Osmo will result in an invalid window generated by gtk. The window is full screen, missing the banner line, and many components in the window generated incorrectly. The config.xml file is filled with invalid data causing the next start of Osmo to crash or allocate large chunks of memory. Removing Pipelight allows Osmo to function normally.
Updating a previously saved Note and got this error after saving then using the Quit button.
The Osmo window was "stuck" in maximized mode. Could not figure out how to get it into window mode. May not be an Osmo problem because the shortcut keys for maximize/minimize (alt-F9/alt-F10 or alt-F5)don't seem to work on any window.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: osmo 0.2.10+svn937-1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Mar 26 09:58:00 2014
ExecutablePath: /usr/bin/osmo
InstallationDate: Installed on 2014-02-13 (40 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140211)
ProcCmdline: osmo
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f341238a64d: lock xadd %edx,(%rax)
PC (0x7f341238a64d) ok
source "%edx" ok
destination "(%rax)" (0xfffffffffffffff8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: osmo
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
PluginConfig::~PluginConfig() () from /usr/lib/pipelight/libpipelight-silverlight5.1.so
__run_exit_handlers (status=0, listp=0x7f341aa476c8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
__GI_exit (status=<optimized out>) at exit.c:104
Title: osmo crashed with SIGSEGV in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2014-04-06 19:38:34 |
Cliff Carson |
information type |
Private |
Public |
|
| 2014-04-06 20:20:38 |
Sebastian Lackner |
bug task added |
|
pipelight |
|
| 2014-04-21 22:47:46 |
Cliff Carson |
attachment added |
|
BT_from_attach.txt https://bugs.launchpad.net/ubuntu/+source/osmo/+bug/1297872/+attachment/4091800/+files/BT_from_attach.txt |
|
