|
||||||
| 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,
I posted a related (and now solved) issue on the "updates and patches" forum, but now I've encountered a new, small and odd problem. After updating to 1.5.0.7 via YOU ,if I launch Firefox from the firefox.sh -script as one is supposed to, Firefox does come up now, but every time I go to a page with .rm streams, I get the error message (thrice) "Could not find an appropriate hxplay or realplay in the system path to use as an embedded player." The weird thing is that if I use the "firefox-bin" -binary, realplayer works fine. I know the very basics of bash -scripting, but the firefox script is beyond my league, and I'm not sure if it is the real problem. Also, "firefox -h" creates the error message below. (as you can see the helps do emerge, but something goes horribly wrong in the middle) I'm using SUSE 9.3 on a 64bit AMD. I have updated firefox normally through YOU and it worked fine up and till 1.5.0.6; only the last update broke it. I've also reinstalled firefox, and renamed the ".mozilla/" directory to (almost) no avail. This is what I get from "firefox -h" Usage: /opt/MozillaFirefox/lib/firefox-bin [ options ... ] [URL] where options include: X11 options --display=DISPLAY X display to use --sync Make X calls synchronous --no-xshm Don't use X shared memory extension --xim-preedit=STYLE --xim-status=STYLE --g-fatal-warnings Make all warnings fatal Mozilla options -height <value> Set height of startup window to <value>. -h or -help Print this message. -width <value> Set width of startup window to <value>. -v or -version Print Firefox version. -P <profile> Start with <profile>. -ProfileManager Start with profile manager. -UILocale <locale> Start with <locale> resources as UI Locale. -contentLocale <locale> Start with <locale> resources as content Locale. No Persistent Registry Found. Type Manifest File: /opt/MozillaFirefox/lib/components/xpti.dat ###!!! ASSERTION: Failed to write xpti manifest!: 'Error', file xptiInterfaceInfoManager.cpp, line 1937 Break: at file xptiInterfaceInfoManager.cpp, line 1937 *** Registering xpcomObsoleteModule components (all right -- a generic module!) .... [truncated] .... break: at file xptiInterfaceInfoManager.cpp, line 1937 nsNativeComponentLoader: registering deferred (0) -jsconsole Open the JavaScript console. -browser Open a browser window. Usage: firefox [-flags] [<url>] WARNING: nsExceptionService ignoring thread destruction after shutdown, file nsExceptionService.cpp, line 191 Could not write out perisistant registry! nsStringStats => mAllocCount: 708 => mReallocCount: 221 => mFreeCount: 708 => mShareCount: 747 => mAdoptCount: 125 => mAdoptFreeCount: 124 -- LEAKED 1 !!! |
|
|||
|
Ludvikengelbrekt,
It appears that in the past few days you have not received a response to your posting. That concerns us, and has triggered this automated reply. Has your problem been resolved? If not, you might try one of the following options: - Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp - Check all of the other support tools and options available at http://support.novell.com. - You could also try posting your message again. Make sure it is posted in the correct newsgroup. (http://support.novell.com/forums) Be sure to read the forum FAQ about what to expect in the way of responses: http://support.novell.com/forums/faq_general.html If this is a reply to a duplicate posting, please ignore and accept our apologies and rest assured we will issue a stern reprimand to our posting bot. Good luck! Your Novell Product Support Forums Team http://support.novell.com/forums/ |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|