http://bugs.winehq.org/show_bug.cgi?id=15211
Summary: Inserting objects in Word 97 always trigger an ole error Product: Wine Version: 1.1.4 Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole AssignedTo: wine-bugs@winehq.org ReportedBy: Ronny.Standtke@gmx.net CC: dsh@linux.ucla.edu
+++ This bug was initially created as a clone of Bug #7026 +++
I am using Office 97 with Wine. Whenever I try inserting an object (Insert -> Object...) I only get an error message in Office and the following wine console output: -------------- err:ole:apartment_getclassobject DllGetClassObject returned error 0x80040111 err:ole:CoGetClassObject no class object {00020821-0000-0000-c000-000000000046} could be created for context 0x3 --------------
http://bugs.winehq.org/show_bug.cgi?id=15211
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2008-09-10 02:37:39 --- Don't create the clones, if that's the same problem reopen an existing bug instead.
*** This bug has been marked as a duplicate of bug 7026 ***
http://bugs.winehq.org/show_bug.cgi?id=15211
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2008-09-10 02:37:50 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=15211
Ronny Standtke Ronny.Standtke@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|DUPLICATE |
--- Comment #3 from Ronny Standtke Ronny.Standtke@gmx.net 2008-09-10 02:48:51 --- I think, this is not really a duplicate of Bug#7026 where I initially reported that Wine is crashing. Now Wine is not crashing any more but generating an ole error. Bug#7026 was set to RESOLVED FIXED because Wine is no longer crashing. But inserting objects still does not work. So what am I suppoded to do here without stepping on someone's toes?
I was told that I should open new bugs if the remaining problem is to far away from the initial bug report. See here: http://bugs.winehq.org/show_bug.cgi?id=9537#c34
Feel free to establish any bug reporting/closing/cloning policy as long as it is consistent and makes sense.
http://bugs.winehq.org/show_bug.cgi?id=15211
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2008-09-10 03:06:06 --- If that's a different problem why do you start with the "+++ This bug was initially created as a clone..." claim? Don't do that.
http://bugs.winehq.org/show_bug.cgi?id=15211
--- Comment #5 from Ronny Standtke Ronny.Standtke@gmx.net 2008-09-10 03:33:13 --- (In reply to comment #4)
If that's a different problem why do you start with the "+++ This bug was initially created as a clone..." claim? Don't do that.
Why shouldn't I do that (honest question)?! To quote http://www.bugzilla.org/docs/tip/en/html/bugreports.html#cloningbugs "This allows you to track more easily similar concerns in a new bug." This is a valid reason IMHO.
http://bugs.winehq.org/show_bug.cgi?id=15211
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2008-09-10 05:45:38 --- (In reply to comment #5)
If that's a different problem why do you start with the "+++ This bug was initially created as a clone..." claim? Don't do that.
Why shouldn't I do that (honest question)?! To quote http://www.bugzilla.org/docs/tip/en/html/bugreports.html#cloningbugs "This allows you to track more easily similar concerns in a new bug." This is a valid reason IMHO.
The word "clone" means the same thing. In bugzilla terms this means a duplicate bug. If the bug you are adding somehow depends on an existing (possibly fixed) bug just explain how. Explaining clearly your intentions always helps better understand what is going on.
http://bugs.winehq.org/show_bug.cgi?id=15211
--- Comment #7 from Ronny Standtke Ronny.Standtke@gmx.net 2008-09-10 06:38:45 --- (In reply to comment #6)
The word "clone" means the same thing. In bugzilla terms this means a duplicate bug.
Sorry, but I am very surprised to hear such bold statements from someone who is supposedly a long-term developer, but that statement above is just not true. Clones and duplicates are different concepts in bugzilla. Read the documentation.
If the bug you are adding somehow depends on an existing (possibly fixed) bug just explain how. Explaining clearly your intentions always helps better understand what is going on.
I thought that everybody here is familiar with the concept of bug clones and what they intend. Looks like this is not true. I will try to be more verbose next time.
http://bugs.winehq.org/show_bug.cgi?id=15211
--- Comment #8 from Dmitry Timoshkov dmitry@codeweavers.com 2008-09-10 07:55:36 --- (In reply to comment #7)
Sorry, but I am very surprised to hear such bold statements from someone who is supposedly a long-term developer, but that statement above is just not true. Clones and duplicates are different concepts in bugzilla. Read the documentation.
In Wine bugzilla we don't use all the full blown bugzilla features, some of them are confusing, some are redundant, some are buggy. It's always a good idea to provide as much context as possible to avoid any confusion.
http://bugs.winehq.org/show_bug.cgi?id=15211
Rob Shearman robertshearman@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #9 from Rob Shearman robertshearman@gmail.com 2008-10-06 09:33:58 --- DllGetClassObject in ole32 should handle the case of being called with an unknown CLSID that is registered with the InProcHandler32 key being "ole32.dll" in the registry and in this case call OleCreateDefaultHandler or the equivalent.
http://bugs.winehq.org/show_bug.cgi?id=15211
--- Comment #10 from Austin English austinenglish@gmail.com 2009-04-17 12:19:21 --- Is this still an issue in current (1.1.19 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=15211
--- Comment #11 from Ronny Standtke Ronny.Standtke@gmx.net 2009-04-20 02:42:37 --- (In reply to comment #10)
Is this still an issue in current (1.1.19 or newer) wine?
I just tested with wine 1.1.19 and the issue is still there.
http://bugs.winehq.org/show_bug.cgi?id=15211
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio@earthlink.net
--- Comment #12 from Rosanne DiMesio dimesio@earthlink.net 2009-08-16 09:45:27 --- Still present in 1.1.27.
http://bugs.winehq.org/show_bug.cgi?id=15211
--- Comment #13 from Austin English austinenglish@gmail.com 2010-09-07 16:49:03 CDT --- This is your friendly reminder that there has been no bug activity for a year. Is this still an issue in current (1.3.2 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=15211
Ronny Standtke Ronny.Standtke@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #14 from Ronny Standtke Ronny.Standtke@gmx.net 2010-10-13 08:00:51 CDT --- I just tested with wine 1.3.4 and the ole error is no longer triggered. Inserting objects now seems to work. Thank you all very much!
http://bugs.winehq.org/show_bug.cgi?id=15211
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Alexandre Julliard julliard@winehq.org 2010-10-15 12:53:13 CDT --- Closing bugs fixed in 1.3.5.
https://bugs.winehq.org/show_bug.cgi?id=15211
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|ole |-unknown
-
wine-bugs＠winehq.org