Ubuntu
mpqc package

mpqc crashes if no filename is assigned

Bug #428294 reported by Lödur on 2009-09-12

This bug report is a duplicate of: Bug #977393: mpqc crashed with SIGABRT in sc::MPQCIn::error(). Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	mpqc (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: mpqc

Open a gnome-terminal, type the following and press [Enter]
mpqc

Error message
---
mpqc: error: no molecule given
Aborted (core dumped)
---

ProblemType: Bug
Architecture: i386
Date: Sat Sep 12 10:03:33 2009
DistroRelease: Ubuntu 9.10
Package: mpqc 2.3.1-4
ProcEnviron:
SHELL=/bin/bash
LANG=en_GB.UTF-8
LANGUAGE=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SourcePackage: mpqc
Uname: Linux 2.6.31-10-generic i686

Tags:

Revision history for this message

Lödur (loedur) wrote on 2009-09-12:

Dependencies.txt Edit (522 bytes, text/plain; charset="utf-8")

Revision history for this message

Lödur (loedur) wrote on 2009-09-12:

_usr_bin_mpqc.1000.crash Edit (199.7 KiB, text/plain)

Because of this error message, I attached the crash-file from /var/crash
---
The problem cannot be reported:

The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes
---

Lödur (loedur) on 2009-10-10

summary:

- mpqc don't start
+ mpqc crashes if no filename is assigned

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-06-05:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mpqc (Ubuntu):
status:	New → Confirmed

Revision history for this message

Logan Rosen (logan) wrote on 2012-11-06:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 977393, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.