Comment 0 for bug 1297872

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