** Description changed:

- I have selected 2 cells, right clicked and selected Paragraph Settings,
- clicked on "Left" to get them left aligned. LyX crashed. This is always
- reproducible.
+ I have selected 2 consecutive table cells, right clicked and selected
+ Paragraph Settings, clicked on "Left" to get them left aligned. LyX
+ crashed. This is always reproducible.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: lyx 2.0.6-1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 29 16:34:18 2013
  ExecutablePath: /usr/bin/lyx
  InstallationDate: Installed on 2013-03-28 (184 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130324)
  MarkForUpload: True
  ProcCmdline: lyx
  Signal: 6
  SourcePackage: lyx
  StacktraceTop:
-  ?? ()
-  ?? ()
-  ?? ()
-  ?? ()
-  ?? ()
+  ?? ()
+  ?? ()
+  ?? ()
+  ?? ()
+  ?? ()
  Title: lyx crashed with SIGABRT
  UpgradeStatus: Upgraded to saucy on 2013-05-09 (142 days ago)
  UserGroups: adm bluetooth cdrom colord condor dialout dip disk fax floppy 
games lp lpadmin plugdev pulse sambashare sudo syslog tape tty users video

** Summary changed:

- lyx crashed with SIGABRT when 2 consecutive table cells are configured as 
left aligned
+ lyx crashed with SIGABRT  in std::basic_string<char, std::char_traits<char>, 
std::allocator<char> >::basic_string()

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232749

Title:
  lyx crashed with SIGABRT  in std::basic_string<char,
  std::char_traits<char>, std::allocator<char> >::basic_string()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/1232749/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to