Insert image bug

[pauls]

I've finally been able to reliability replicate this.

Create a new document. Type a word, select it, and change its style to heading1. Press enter and try and insert an image. It shows an error saying there is something wrong this the image.

Can anyone confirm this?

 

[John McGhie]

Nope: Works fine here.

How have you defined heading1 style? What's in it? What kind of image?
Which version of Word? What kind of CPU? Which version of Mac OS?

Sorry, but if you create a guessing game, really there's nothing else we can
do except "guess". If you provide all the needed information, we have a
much better chance of helping you.

Cheers

I've finally been able to reliability replicate this.

Create a new document. Type a word, select it, and change its style to
heading1. Press enter and try and insert an image. It shows an error saying
there is something wrong this the image.

Can anyone confirm this?

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
+61 4 1209 1410, mailto:[email protected]
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Nhulunbuy, Northern Territory, Australia

 

[CyberTaz]

Yeah - This is a new one John - I'm able to repeatedly replicate it here.
Thought it might be memory leak related but continues to occur after
relaunching. Have not had an opportunity to dig into it & won't until
tonight, but here's the deal:

System: PMG5 Dual 2 GHz, 1.5 MB, 10.4.11, Word 2008 - no apps running other
than Word & E'rage

In a new document I can insert any of a half dozen images of various types
without any problem at all. As soon as I apply a Heading 1 style *anywhere*
in the document & attempt to insert one of the same images *anywhere* in the
file I get the message that:

"The application cannot open this file. This file is an unsupported graphic
format or may be damaged. Try opening the graphic in another application."

....Even though the same image has already been inserted into the doc prior
to the use of a H1 style. Save, close & reopen file but the problem
continues. If I quit Word then launch & open the file I *can* insert images
until the cows come home *until* I apply H1 somewhere - then the message
starts to get in my face again.

This one needs to be bugged

Regards |:>)
Bob Jones
[MVP] Office:Mac

 

[Daiya Mitchell]

The link to H1 style is new information, but that error message has been
linked to corrupt preferences, as here:
http://word.mvps.org/Mac/Word2008Issues.html#Graphics

If recreating prefs fixes it, the MacBU wants to see that prefs file.
Also, people reported that it happens on Insert but not on drag and drop
and I assume not the Object Palette browsers....

 

[pauls]

This is word 2008 on a macbook pro 2.4 / 4gb with the normal template (I've deleted it and the new one that's created does the same).

I've zapped the prefs to no avail. Type of image file makes no difference.

I've reported this as a bug but was only recently able to replicate it.

Another related issue is that when you drag a pdf image and drop it in a word form, the image is of low quality.

 

[John McGhie]

The PDF bug is not "related", it's a separate bug

Your Insert Image bug is fascinating.

Can you flip me a one-page document after the fault has appeared? I want to
have a look at the XML inside it.

Cheers

This is word 2008 on a macbook pro 2.4 / 4gb with the normal template (I've
deleted it and the new one that's created does the same).

I've zapped the prefs to no avail. Type of image file makes no difference.

I've reported this as a bug but was only recently able to replicate it.

Another related issue is that when you drag a pdf image and drop it in a word
form, the image is of low quality.

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
+61 4 1209 1410, mailto:[email protected]
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Nhulunbuy, Northern Territory, Australia

 

[CyberTaz]

Hi John -

I'm easily able to replicate this & am working up a package to post in the
mailing list.

 

[pauls]

Microsoft support say they can't replicate this, which is strange to say the least. A colleague at work can't replicate the problem either.

The difference between our machines is that mine has 256MB graphics memory. Be interesting to see other peoples configuration, both those that can replicate it and those that can't.

I've created a new user and have deleted office and reinstalled it - nothing fixes it.

 

[Jason Andersen [MSFT]]

I can replicate the issue, but I don't think it has anything to do with
applying Header 1 to text in Word.

I think you'll find that if you collapse (hide) the Styles pane in the
Formatting Palette, you'll be able to insert images again. Or you can hide
the entire Formatting Palette if that is easier. Please let me know if this
doesn't solve the problem.

Nice one, your narrowed steps allowed me to isolate the problem very
quickly! Thanks for the great feedback everyone, I'll go ahead and log this
one!

- Jason

 

[pauls]

It's been logged under:

SRX1058716380ID - WD2008: Inserting pictures in Word.

When I first found the problem. You might want to use the above number.

 

[CyberTaz]

Hi Jason -

Thanks for the quick pickup... Here's a little tidbit that may help if you
aren't aware of it:

I believe - based on your insight - that the problem stems from a conflict
between the displayed Styles Palette & the Quick Style & Effects Palette
that's trying to replace it when you attempt to insert an image - possible?

HTH |:>)
Bob Jones
[MVP] Office:Mac

 

[geishasboy]

I've finally been able to reliability replicate this.

Create a new document. Type a word, select it, and change its style to heading1. Press enter and try and insert an image. It shows an error saying there is something wrong this the image.

Can anyone confirm this?

I don't even have to change the style - I cannot use the INSERT ->
PICTURE -> from FILE command to enter ANY .tif or .pict graphic into a
Word document. It doesn't matter if it's a new Word 08 doc or an
opened template from Word 04, I get a dialogue box that tells me that
the application can't open the graphic. I can drag the graphic into
the document, but i can't use the insert command. This is very
annoying. All of these graphics worked just fine in Word 04.

 

[geishasboy]

I've finally been able to reliability replicate this.

Create a new document. Type a word, select it, and change its style to heading1. Press enter and try and insert an image. It shows an error saying there is something wrong this the image.

Can anyone confirm this?

All right, I was able to insert after reading all the other posts
below, by closing the "Styles" drop-down in the Formatting Palette.
Thanks to everyone for your amazing attention to detail. Who on earth
could even think these things were related???

 

[pauls]

Well, I have another!

I've come across another much more difficult to replicate 'feature' to do with the bibliography capability, one that is more serious but much more difficult to replicate - a message saying it can't save the backup file.

I've been very disappointed with MS support with this bug, I feel they didn't try hard enough to replicate it. Rather, they assumed I was imagining it.

After this, I hesitate to report the new one, especially because it is much more difficult for me to find a test case and why should I be testing MS (or anyone else's) software anyway? It should just work, and they should trust their users and not patronise them when they report a problem.

 

[CyberTaz]

Then you should post it as a *new* message - burying it deep in the bowels
of a thread having to do with a *graphics* issue makes it quite unlikely
that anyone who has suggestions to offer will ever see it.

--
Regards |:>)
Bob Jones
Office:Mac MVP

in message news:[email protected]...

 

[John McGhie]

Yeah, put this up as a new thread and let's have a look at it...

Microsoft Support doesn't have the time to go "looking" for bugs, that's not
their function. They do indeed start off with the presumption that the
software works the way it does, and they wil help you "use" it.

Give US as much detail as you can about the machine, the software versions,
what you are trying to do, etc and we'll go looking for you. In here, we're
much more interested in what is wrong with it and how to get it fixed

If WE can replicate it, we'll put a bug in for you!

Cheers

Well, I have another!

I've come across another much more difficult to replicate 'feature' to do with
the bibliography capability, one that is more serious but much more difficult
to replicate - a message saying it can't save the backup file.

I've been very disappointed with MS support with this bug, I feel they didn't
try hard enough to replicate it. Rather, they assumed I was imagining it.

After this, I hesitate to report the new one, especially because it is much
more difficult for me to find a test case and why should I be testing MS (or
anyone else's) software anyway? It should just work, and they should trust
their users and not patronise them when they report a problem.

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
+61 4 1209 1410, mailto:[email protected]
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Nhulunbuy, Northern Territory, Australia

 

[Jason Andersen [MSFT]]

Yes, that's a good thought, and basically what my initial guess was as to
the root cause of the issue. I don't think it's necessarily a conflict
between the two panes, but probably an error in the code when we go to
"remove" the pane, potentially because the modal dialog is still displayed.
I think if it were a conflict between the two panes, we'd see an issue just
switching back and forth between pictures and text, and not just on insert.
We'll let the developers have a look at it, though, since I can't say for
certain what the exact issue is without digging into the code. Right now
it's just speculation.

- Jason