Bug 75088 - Error on starting LibO Draw
Summary: Error on starting LibO Draw
Status: RESOLVED DUPLICATE of bug 74226
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
4.2.0.4 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-17 11:33 UTC by Wolfgang Koch
Modified: 2014-02-17 19:37 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Koch 2014-02-17 11:33:02 UTC 
While starting Libre Office Dram from Quick Starter, the system reply is" Libre Office is no longer working". All the other aplications like writer, impress etc seem not to be affected.
I've not seen this bug with versions before 4.2
OS: Win 7 prof. 16GB RAM, CPU AMD Phenom II X4
Comment 1 Maxim Monastirsky 2014-02-17 11:59:45 UTC 
Hi,

Does it happen only when you're starting Draw from the Quick Starter, or you can reproduce the same when starting from Start menu, or from Start Center?

Also I see that you filled this bug against 4.2.1.1rc version. Is that intentional or you actually meant 4.2.0.4 (which is the current release)?
Comment 2 Wolfgang Koch 2014-02-17 14:09:56 UTC 
(In reply to comment #1)
> Hi,
> 
> Does it happen only when you're starting Draw from the Quick Starter, or you
> can reproduce the same when starting from Start menu, or from Start Center?
> 
> Also I see that you filled this bug against 4.2.1.1rc version. Is that
> intentional or you actually meant 4.2.0.4 (which is the current release)?

Hi Maxim,
it doesn't matter where I start it from, it's always same message from Win 7: "LibO no longer working".
Sorry - I'm reffering to 4.2.0.4


rgds
Wolfgang
Comment 3 Maxim Monastirsky 2014-02-17 19:37:33 UTC 
(In reply to comment #2)
> Sorry - I'm reffering to 4.2.0.4
Thanks Wolfgang, it sounds much like Bug 74226, which fortunately already fixed for the next minor release (4.2.1).

*** This bug has been marked as a duplicate of bug 74226 ***