|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Novell Archives Archived content from Novell openSUSE support forums |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Hi!
Everytime I write a word and go to Tools->Language->Thesaurus... oowrite crashes. Does anybody have an idea why this might be. I think the problem started after I had installed other language localization files. But know I have uninstalled them. |
|
|||
|
M. Bugra Akin wrote:
> Hi! > > Everytime I write a word and go to Tools->Language->Thesaurus... oowrite > crashes. Does anybody have an idea why this might be. I think the > problem started after I had installed other language localization files. > But know I have uninstalled them. It may be a good idea to reinstall OpenOffice to reverse all changes done by language packages. -- Regards, Rajko. |
|
|||
|
> Hi!
> > Everytime I write a word and go to Tools->Language->Thesaurus... oowrite > crashes. Does anybody have an idea why this might be. I think the > problem started after I had installed other language localization files. > But know I have uninstalled them. I have the same problem with a fresh install from the same day. I tried uninstalling, reinstalling via Yast and it didn't work for me. I even removed all profile settings (~/.* files) from my home dir and when logging in fresh with a new profile Writer still crashes when trying to use the thesaurus with the application default en US. Anyone have any none "format and reinstall" advice on how I can fix this? Suse 9.3 Full install plus Media Packs 1-4 via online yast. Patched up to date via yast. Linux linux64 2.6.11.4-21.9-default #1 x86_64 x86_64 x86_64 GNU/Linux Thx, Paul |
|
|||
|
paulnmel@gmail.com wrote:
>> Hi! >> >> Everytime I write a word and go to Tools->Language->Thesaurus... oowrite >> crashes. Does anybody have an idea why this might be. I think the >> problem started after I had installed other language localization files. >> But know I have uninstalled them. > > I have the same problem with a fresh install from the same day. I tried > uninstalling, reinstalling via Yast and it didn't work for me. I even > removed all profile settings (~/.* files) from my home dir and when > logging in fresh with a new profile Writer still crashes when trying to > use the thesaurus with the application default en US. > > Anyone have any none "format and reinstall" advice on how I can fix this? > > Suse 9.3 > Full install plus Media Packs 1-4 via online yast. > Patched up to date via yast. > Linux linux64 2.6.11.4-21.9-default #1 x86_64 x86_64 x86_64 GNU/Linux > > Thx, > Paul "Format and reinstall" ![]() This time I tried harder, and yes it crashes faster than it was ever able to close, and as you described, it happens every time I touch Thesaurus. BTW option to send crash report doesn't work. This is the reason: Error - can't open /usr/lib/ooo-2.0/share/dict/ooo/th_en_US.idx or /usr/lib/ooo-2.0/share/dict/ooo/th_en_US.dat It should not crash if it doesn't find thesaurus files, but it does. It is bug, but where to report that, to Novell/SuSE or OpenOffice. I have th_en_US_v2.idx, and th_en_US_v2.dat and after renaming them to th_en_US.idx and th_en_US.dat thesaurus passed short test of few words without crashing. -- Regards, Rajko. |
|
|||
|
Rajko M. wrote:
> paulnmel@gmail.com wrote: > >>> Hi! >>> >>> Everytime I write a word and go to Tools->Language->Thesaurus... oowrite >>> crashes. Does anybody have an idea why this might be. I think the >>> problem started after I had installed other language localization files. >>> But know I have uninstalled them. >> >> I have the same problem with a fresh install from the same day. I tried >> uninstalling, reinstalling via Yast and it didn't work for me. I even >> removed all profile settings (~/.* files) from my home dir and when >> logging in fresh with a new profile Writer still crashes when trying to >> use the thesaurus with the application default en US. >> >> Anyone have any none "format and reinstall" advice on how I can fix this? >> >> Suse 9.3 >> Full install plus Media Packs 1-4 via online yast. >> Patched up to date via yast. >> Linux linux64 2.6.11.4-21.9-default #1 x86_64 x86_64 x86_64 GNU/Linux >> >> Thx, >> Paul > > "Format and reinstall" ![]() > > This time I tried harder, and yes it crashes faster than it was ever able > to close, and as you described, it happens every time I touch Thesaurus. > BTW option to send crash report doesn't work. > > This is the reason: > Error - can't open /usr/lib/ooo-2.0/share/dict/ooo/th_en_US.idx > or /usr/lib/ooo-2.0/share/dict/ooo/th_en_US.dat > It should not crash if it doesn't find thesaurus files, but it does. > It is bug, but where to report that, to Novell/SuSE or OpenOffice. > > I have th_en_US_v2.idx, and th_en_US_v2.dat and after renaming them to > th_en_US.idx and th_en_US.dat thesaurus passed short test of few words > without crashing. > Not renaming them, but making copies with names that OpenOffice is looking for ![]() -- Regards, Rajko. |
|
|||
|
On Wed, 05 Oct 2005 02:18:04 GMT
"Rajko M." <kakomo123@nospam.bazar> wrote: > > I have th_en_US_v2.idx, and th_en_US_v2.dat and after renaming them > > to th_en_US.idx and th_en_US.dat thesaurus passed short test of few > > words without crashing. > > > > Not renaming them, but making copies with names that OpenOffice is > looking for ![]() Instead of making copies try making symbolic links (might have to be root, depending on where these files are): cd /path/to/the/files ln -s th_en_US_v2.idx th_en_US.idx ln -s th_en_US_v2.dat th_en_US.dat -- Kevin Nathan (Arizona, USA) Linux Potpourri and a.o.l.s. FAQ -- http://www.project54.com/linux/ Open standards. Open source. Open minds. The command line is the front line. Linux 2.6.8-24.18-default 9:07pm up 26 days 21:54, 12 users, load average: 0.27, 0.31, 0.42 |
|
|||
|
> paulnmel@gmail.com wrote:
> > >> Hi! > >> > >> Everytime I write a word and go to Tools->Language->Thesaurus... oowrite > >> crashes. Does anybody have an idea why this might be. I think the > >> problem started after I had installed other language localization files. > >> But know I have uninstalled them. > > > > I have the same problem with a fresh install from the same day. I tried > > uninstalling, reinstalling via Yast and it didn't work for me. I even > > removed all profile settings (~/.* files) from my home dir and when > > logging in fresh with a new profile Writer still crashes when trying to > > use the thesaurus with the application default en US. > > > > Anyone have any none "format and reinstall" advice on how I can fix this? > > > > Suse 9.3 > > Full install plus Media Packs 1-4 via online yast. > > Patched up to date via yast. > > Linux linux64 2.6.11.4-21.9-default #1 x86_64 x86_64 x86_64 GNU/Linux > > > > Thx, > > Paul > > "Format and reinstall" ![]() > > This time I tried harder, and yes it crashes faster than it was ever able to > close, and as you described, it happens every time I touch Thesaurus. > BTW option to send crash report doesn't work. > > This is the reason: > Error - can't open /usr/lib/ooo-2.0/share/dict/ooo/th_en_US.idx > or /usr/lib/ooo-2.0/share/dict/ooo/th_en_US.dat > It should not crash if it doesn't find thesaurus files, but it does. > It is bug, but where to report that, to Novell/SuSE or OpenOffice. > > I have th_en_US_v2.idx, and th_en_US_v2.dat and after renaming them to > th_en_US.idx and th_en_US.dat thesaurus passed short test of few words > without crashing. > > -- > Regards, > Rajko. Thanks Rajko... ** su - cd /usr/lib/ooo-2.0/share/dict/ooo ln -sf /usr/lib/ooo-2.0/share/dict/ooo/th_en_US_v2.dat th_en_US.dat ln -sf /usr/lib/ooo-2.0/share/dict/ooo/th_en_US_v2.idx th_en_US.idx ** ...the thesaurus in Writer works fine for me now. Cheers, Paul |
|
|||
|
Kevin Nathan wrote:
> On Wed, 05 Oct 2005 02:18:04 GMT > "Rajko M." <kakomo123@nospam.bazar> wrote: > >> > I have th_en_US_v2.idx, and th_en_US_v2.dat and after renaming them >> > to th_en_US.idx and th_en_US.dat thesaurus passed short test of few >> > words without crashing. >> > >> >> Not renaming them, but making copies with names that OpenOffice is >> looking for ![]() > > Instead of making copies try making symbolic links (might have to be > root, depending on where these files are): > > cd /path/to/the/files > ln -s th_en_US_v2.idx th_en_US.idx > ln -s th_en_US_v2.dat th_en_US.dat > > Agree, but I wasn't sure what will happen with files. The bug can corrupt them and than I have more work to do ![]() Good is that bug is actually in error reporting part. Copy is reflex motion to make backup, before any experiment. In this case leave original as is. -- Regards, Rajko. |
|
|||
|
On Wed, 05 Oct 2005 23:05:35 GMT
"Rajko M." <kakomo123@nospam.bazar> wrote: > Agree, but I wasn't sure what will happen with files. > The bug can corrupt them and than I have more work to do ![]() > Good is that bug is actually in error reporting part. > > Copy is reflex motion to make backup, before any experiment. > In this case leave original as is. > Yes, that's a good point, too. ;-) -- Kevin Nathan (Arizona, USA) Linux Potpourri and a.o.l.s. FAQ -- http://www.project54.com/linux/ Open standards. Open source. Open minds. The command line is the front line. Linux 2.6.8-24.18-default 9:05pm up 27 days 21:52, 12 users, load average: 0.87, 0.86, 0.72 |
|
|||
|
Kevin Nathan wrote:
> On Wed, 05 Oct 2005 23:05:35 GMT > "Rajko M." <kakomo123@nospam.bazar> wrote: > >> Agree, but I wasn't sure what will happen with files. >> The bug can corrupt them and than I have more work to do ![]() >> Good is that bug is actually in error reporting part. >> >> Copy is reflex motion to make backup, before any experiment. >> In this case leave original as is. >> > > Yes, that's a good point, too. ;-) > > It's not excuse. That is why I posted to make copy, not rename. This was just plain wrong word for what I did. With link programs can access any of the names for the same file, but they access the same file. You do that if you are sure that the only problem is naming. I wasn't. For some reason SuSE changed filenames to *_v2.??? which could be in the worst case different file format. Thesaurus was asking for filenames without that extension. Was that old module looking for some previous version, able to corrupt existing file, or somebody has forgoten to change source before compilation? Safe way was to copy file and than test. I tested only few words, Openoffice didn't crashed, but that, in any way, wasn't enough to recommend using original. Many times I learned hard way that backup saves time. In this case it was normal to leave original untouched and play with copy. If something went wrong there will be original for second try, instead of reinstallation, or what I do, browse rpm using mc and copy corrupted files only. -- Regards, Rajko. |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|