brodeee Posted December 6, 2012 Share Posted December 6, 2012 Running Kubuntu 12.10 Linux I have tried over and over to install Firestorm. I have downloaded, extracted to my home and tried to run the install.sh and firestorm. I have dragged the install.sh to the terminal and it seemed to install but with no luck of opening the program. I have ran the 32bit kubuntu and the 64bit. Any luck on how to do this? Every post I have searched and searched for give the same answer.. download, extract, and you just simply click and your done. Link to comment Share on other sites More sharing options...
Qie Niangao Posted December 6, 2012 Share Posted December 6, 2012 Somebody who actually uses the install script may be able to help you with whatever may have gone wrong with that, but it's completely possible to run Firestorm without installing it, and I'd suggest starting there to see if there's something interfering with running it. So, open a terminal, cd down to the directory where the program was extracted, and type ./firestorm to run that executable shell script which launches the actual viewer binary. Let's see whether you get a viewer window and can login, or if not, whether the console leaves any hints about what went wrong. Link to comment Share on other sites More sharing options...
brodeee Posted December 6, 2012 Author Share Posted December 6, 2012 still no luck. Link to comment Share on other sites More sharing options...
Darren Scorpio Posted December 6, 2012 Share Posted December 6, 2012 Since you are running 12.10 I will bet anything you are simply running into the fontconfig problem. There is a way around it but I can't find the thread now maybe Qie can remember it better than I can. If I find it I will post back. Link to comment Share on other sites More sharing options...
Darren Scorpio Posted December 6, 2012 Share Posted December 6, 2012 Here you go. http://community.secondlife.com/t5/Second-Life-Viewer/Viewer-on-Kubuntu-12-10-beta-2-64bit-crash/m-p/1701283 Link to comment Share on other sites More sharing options...
brodeee Posted December 6, 2012 Author Share Posted December 6, 2012 looks like it was already fine on that.. shane@LinuxPC:~$ sudo apt-get install libfontconfig Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libfontconfig1' instead of 'libfontconfig' libfontconfig1 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 141 not upgraded. shane@LinuxPC:~$ Link to comment Share on other sites More sharing options...
Darren Scorpio Posted December 6, 2012 Share Posted December 6, 2012 No. Please follow the instructions on that thread. Ubuntu 12.10 uses a newer version while the SL viewer is built for an older version, so you need to follow what was said to do on that thread to get it working. Link to comment Share on other sites More sharing options...
Qie Niangao Posted December 6, 2012 Share Posted December 6, 2012 brodeee wrote: still no luck. Okay, but what happens? (The libfontconfig thing, by the way, is fixed in the latest Firestorm, 4.3.1.31155.... maybe in a previous version, too, although I never tested those. There's also a fix for that problem in the LL viewer that's currently in test, and worked fine for me, but I understand we're trying here to get Firestorm running instead.) Link to comment Share on other sites More sharing options...
Darren Scorpio Posted December 6, 2012 Share Posted December 6, 2012 Ah, good to know Qie, thanks. Link to comment Share on other sites More sharing options...
brodeee Posted December 6, 2012 Author Share Posted December 6, 2012 I'll play around with that and see what I can accomplish. Thank you for the quick replies.. Maybe one of you know a better linux OS that has all the steps in order to run Firestorm perfectly without the hassle, that would be great to know. I just need any kind of Linux.. even a older one and one that will work perfectly for Firestorm. Thanks Link to comment Share on other sites More sharing options...
Qie Niangao Posted December 6, 2012 Share Posted December 6, 2012 I wouldn't go shopping distros. There are plenty of us running Ubuntu 12.10, and enough running kubuntu 12.10, for us to know it's nothing special about the distribution. The libfontconfig thing isn't even relevant to the problem if you have the latest Firestorm, so to date, we have yet to try one single thing that has any bearing on the problem. We might eventually get around to that, if we had some idea what is actually happening when you try to run firestorm. (Just as wild speculation, still lacking any pertinent information, I might guess that proprietary drivers for the graphics card weren't installed. But that should be obvious from the errors when you try to run... and I believe recent Ubuntus make it pretty obvious during installation that you really want those drivers. And... bah: it could be anything. No point in trying to guess.) Link to comment Share on other sites More sharing options...
Storm Clarence Posted December 6, 2012 Share Posted December 6, 2012 Qie Niangao wrote: if you have the latest Firestorm, so to date, we have yet to try one single thing that has any bearing on the problem. We might eventually get around to that, if we had some idea what is actually happening when you try to run firestorm. Without any skillset a.k.a not bothering to RTFM, it is near impossible for the OP to articulate what the problem may be. A gander at the log files would probably help, but the OP needs to know where the logs are located, how to access, and know what they are reading. Toward this end, if the OP is running any flavor of Linux and the 3rd party viewer Firestorm don't you think referring him to the blogs, support, and forum of Firestorm would best serve the OP's purpose? How may threads, paragraphs, guesses, and "nope that didn't work" responses are needed before everyone gives up? This. Link to comment Share on other sites More sharing options...
Qie Niangao Posted December 6, 2012 Share Posted December 6, 2012 Using the Firestorm support channels is certainly a good option, but I rather suppose that the OP has been there already, given that the first post laments "Every post I have searched and searched for give the same answer" so it seems unsporting to just fob him off on somebody else he's probably already tried. Running the viewer from a terminal shell is going to produce enough output to at least give us (or Firestorm support) a hint as to what's going on. But yeah, he can see the same text that spews to the terminal window by looking at ~/.firestorm/logs/Firestorm.log -- assuming the program is starting at all, which so far we don't know. Link to comment Share on other sites More sharing options...
Storm Clarence Posted December 6, 2012 Share Posted December 6, 2012 Qie Niangao wrote: Using the Firestorm support channels is certainly a good option, but I rather suppose that the OP has been there already, given that the first post laments "Every post I have searched and searched for give the same answer" so it seems unsporting to just fob him off on somebody else he's probably already tried. Running the viewer from a terminal shell is going to produce enough output to at least give us (or Firestorm support) a hint as to what's going on. But yeah, he can see the same text that spews to the terminal window by looking at ~/.firestorm/logs/Firestorm.log -- assuming the program is starting at all, which so far we don't know. Qie, I have tons of respect for your knowledge and your ability and want to impart that knowledge on this forum. I, too, like to read what issues/challenges/bugs are encountered when deploying software in the Linux/Unix world. It has always helped me to better understand my environment. I did not assume the OP read the Firestorm support and blogs because I know NOT every post talks to the install being as easy as 1-2-3; or they would not have a support structure like they do. I read the Phoenix site, and often. It is chock-ful of information on what to do if sh1t breaks. But, you need to know where it is breaking... or, if you don't know then get yourself a new Linux flavor or a new viewer distro. My humble opinion. Link to comment Share on other sites More sharing options...
Darren Scorpio Posted December 6, 2012 Share Posted December 6, 2012 brodeee wrote: Running Kubuntu 12.10 Linux I have tried over and over to install Firestorm. I have downloaded, extracted to my home and tried to run the install.sh and firestorm. I have dragged the install.sh to the terminal and it seemed to install but with no luck of opening the program. I have ran the 32bit kubuntu and the 64bit. Any luck on how to do this? Every post I have searched and searched for give the same answer.. download, extract, and you just simply click and your done. Which one are you running now is the question. If you are running the 64bit then you need to have the 32 bit libraries installed to run SL. sudo apt-get install ia32-libs Also are you sure you downloaded the latest Firestorm that contains the fontconfig fix that Qie talked about? Did you install the proprietary drivers? Link to comment Share on other sites More sharing options...
brodeee Posted December 6, 2012 Author Share Posted December 6, 2012 I went with Ubuntu 12.10 32bit instead of kubuntu I downloaded firestorm 4.3.1.31155 from phoenixviewer.com extrated, ran, and it opened but I'm crashing after about 2 minutes. I am currently installing my amd graphics driver, its still loading which is taking the longest. Link to comment Share on other sites More sharing options...
brodeee Posted December 6, 2012 Author Share Posted December 6, 2012 still crashing. I did these instructions here http://freesoftwaredeveloper.blogspot.gr/2012/12/how-to-run-second-life-in.html I completed the ./configure did the make and i cant find fontconfig-2.8.0/src/.libs/libfontconfig.so fontconfig-2.8.0/src/.libs/libfontconfig.so.1 fontconfig-2.8.0/src/.libs/libfontconfig.so.1.4.4 I am looking in the correct directory. here is my terminal shane@shane:~$ cd /home/shane/fontconfig-2.8.0 shane@shane:~/fontconfig-2.8.0$ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for bash... /bin/bash checking if dolt supports this host... yes, replacing libtool checking whether make sets $(MAKE)... (cached) yes checking for a C compiler for build tools... gcc checking for suffix of executable build tools... checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for ANSI C header files... (cached) yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for pid_t... yes checking for vprintf... yes checking for _doprnt... no checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... yes checking for geteuid... yes checking for getuid... yes checking for link... yes checking for memmove... yes checking for memset... yes checking for mkstemp... yes checking for strchr... yes checking for strrchr... yes checking for strtol... yes checking for getopt... yes checking for getopt_long... yes checking for sysconf... yes checking for ftruncate... yes checking for chsize... no checking for rand... yes checking for random... yes checking for lrand48... yes checking for a usable iconv... libc checking for freetype-config... /usr/bin/freetype-config checking for FT_Get_Next_Char... yes checking for FT_Get_BDF_Property... yes checking for FT_Get_PS_Font_Info... yes checking for FT_Has_PS_Glyph_Names... yes checking for FT_Get_X11_Font_Format... yes checking for FT_Select_Size... yes checking for FT_Bitmap_Size.y_ppem... yes checking expat.h usability... no checking expat.h presence... no checking for expat.h... no checking xmlparse.h usability... no checking xmlparse.h presence... no checking for xmlparse.h... no configure: WARNING: Cannot find usable expat library. Trying to use libxml2 as fallback. checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for LIBXML2... yes checking for docbook2html... no DOCMAN3 FcAtomicCreate.3 FcAtomicLock.3 FcAtomicNewFile.3 FcAtomicOrigFile.3 FcAtomicReplaceOrig.3 FcAtomicDeleteNew.3 FcAtomicUnlock.3 FcAtomicDestroy.3 FcBlanksCreate.3 FcBlanksDestroy.3 FcBlanksAdd.3 FcBlanksIsMember.3 FcCacheDir.3 FcCacheCopySet.3 FcCacheSubdir.3 FcCacheNumSubdir.3 FcCacheNumFont.3 FcCharSetCreate.3 FcCharSetDestroy.3 FcCharSetAddChar.3 FcCharSetCopy.3 FcCharSetEqual.3 FcCharSetIntersect.3 FcCharSetUnion.3 FcCharSetSubtract.3 FcCharSetMerge.3 FcCharSetHasChar.3 FcCharSetCount.3 FcCharSetIntersectCount.3 FcCharSetSubtractCount.3 FcCharSetIsSubset.3 FcCharSetFirstPage.3 FcCharSetNextPage.3 FcCharSetCoverage.3 FcCharSetNew.3 FcConfigCreate.3 FcConfigReference.3 FcConfigDestroy.3 FcConfigSetCurrent.3 FcConfigGetCurrent.3 FcConfigUptoDate.3 FcConfigHome.3 FcConfigEnableHome.3 FcConfigBuildFonts.3 FcConfigGetConfigDirs.3 FcConfigGetFontDirs.3 FcConfigGetConfigFiles.3 FcConfigGetCache.3 FcConfigGetCacheDirs.3 FcConfigGetFonts.3 FcConfigGetBlanks.3 FcConfigGetRescanInterval.3 FcConfigSetRescanInterval.3 FcConfigAppFontAddFile.3 FcConfigAppFontAddDir.3 FcConfigAppFontClear.3 FcConfigSubstituteWithPat.3 FcConfigSubstitute.3 FcFontMatch.3 FcFontSort.3 FcFontRenderPrepare.3 FcFontList.3 FcConfigFilename.3 FcConfigParseAndLoad.3 FcNameRegisterConstants.3 FcNameUnregisterConstants.3 FcNameGetConstant.3 FcNameConstant.3 FcDirCacheUnlink.3 FcDirCacheValid.3 FcDirCacheLoad.3 FcDirCacheRead.3 FcDirCacheLoadFile.3 FcDirCacheUnload.3 FcFileScan.3 FcFileIsDir.3 FcDirScan.3 FcDirSave.3 FcFontSetCreate.3 FcFontSetDestroy.3 FcFontSetAdd.3 FcFontSetList.3 FcFontSetMatch.3 FcFontSetPrint.3 FcFontSetSort.3 FcFontSetSortDestroy.3 FcPatternFormat.3 FcFreeTypeCharIndex.3 FcFreeTypeCharSet.3 FcFreeTypeCharSetAndSpacing.3 FcFreeTypeQuery.3 FcFreeTypeQueryFace.3 FcInitLoadConfig.3 FcInitLoadConfigAndFonts.3 FcInit.3 FcFini.3 FcGetVersion.3 FcInitReinitialize.3 FcInitBringUptoDate.3 FcLangSetCreate.3 FcLangSetDestroy.3 FcLangSetCopy.3 FcLangSetAdd.3 FcLangSetCompare.3 FcLangSetContains.3 FcLangSetEqual.3 FcLangSetHash.3 FcLangSetHasLang.3 FcLangSetGetLangs.3 FcGetLangs.3 FcLangGetCharSet.3 FcMatrixInit.3 FcMatrixCopy.3 FcMatrixEqual.3 FcMatrixMultiply.3 FcMatrixRotate.3 FcMatrixScale.3 FcMatrixShear.3 FcObjectSetCreate.3 FcObjectSetAdd.3 FcObjectSetDestroy.3 FcObjectSetBuild.3 FcNameRegisterObjectTypes.3 FcNameUnregisterObjectTypes.3 FcNameGetObjectType.3 FcPatternCreate.3 FcPatternDuplicate.3 FcPatternReference.3 FcPatternDestroy.3 FcPatternEqual.3 FcPatternEqualSubset.3 FcPatternFilter.3 FcPatternHash.3 FcPatternAdd.3 FcPatternAddWeak.3 FcPatternAdd-Type.3 FcPatternGet.3 FcPatternGet-Type.3 FcPatternBuild.3 FcPatternDel.3 FcPatternRemove.3 FcPatternPrint.3 FcDefaultSubstitute.3 FcNameParse.3 FcNameUnparse.3 FcUtf8ToUcs4.3 FcUcs4ToUtf8.3 FcUtf8Len.3 FcUtf16ToUcs4.3 FcUtf16Len.3 FcIsLower.3 FcIsUpper.3 FcToLower.3 FcStrCopy.3 FcStrDowncase.3 FcStrCopyFilename.3 FcStrCmp.3 FcStrCmpIgnoreCase.3 FcStrStr.3 FcStrStrIgnoreCase.3 FcStrPlus.3 FcStrFree.3 FcStrDirname.3 FcStrBasename.3 FcStrSetCreate.3 FcStrSetMember.3 FcStrSetEqual.3 FcStrSetAdd.3 FcStrSetAddFilename.3 FcStrSetDel.3 FcStrSetDestroy.3 FcStrListCreate.3 FcStrListNext.3 FcStrListDone.3 FcValueDestroy.3 FcValueSave.3 FcValuePrint.3 FcValueEqual.3 configure: creating ./config.status config.status: creating Makefile config.status: creating fontconfig/Makefile config.status: creating fc-lang/Makefile config.status: creating fc-glyphname/Makefile config.status: creating fc-case/Makefile config.status: creating fc-arch/Makefile config.status: creating src/Makefile config.status: creating conf.d/Makefile config.status: creating fc-cache/Makefile config.status: creating fc-cat/Makefile config.status: creating fc-list/Makefile config.status: creating fc-match/Makefile config.status: creating fc-query/Makefile config.status: creating fc-scan/Makefile config.status: creating doc/Makefile config.status: creating doc/version.sgml config.status: creating test/Makefile config.status: creating fontconfig.spec config.status: creating fontconfig.pc config.status: creating fontconfig-zip config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands shane@shane:~/fontconfig-2.8.0$ make make all-recursive make[1]: Entering directory `/home/shane/fontconfig-2.8.0' Making all in fontconfig make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fontconfig' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fontconfig' Making all in fc-case make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fc-case' make all-am make[3]: Entering directory `/home/shane/fontconfig-2.8.0/fc-case' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-case' make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-case' Making all in fc-lang make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fc-lang' make all-am make[3]: Entering directory `/home/shane/fontconfig-2.8.0/fc-lang' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-lang' make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-lang' Making all in fc-glyphname make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fc-glyphname' make all-am make[3]: Entering directory `/home/shane/fontconfig-2.8.0/fc-glyphname' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-glyphname' make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-glyphname' Making all in fc-arch make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fc-arch' make all-am make[3]: Entering directory `/home/shane/fontconfig-2.8.0/fc-arch' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-arch' make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-arch' Making all in src make[2]: Entering directory `/home/shane/fontconfig-2.8.0/src' make all-am make[3]: Entering directory `/home/shane/fontconfig-2.8.0/src' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/shane/fontconfig-2.8.0/src' make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/src' Making all in fc-cache make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fc-cache' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-cache' Making all in fc-cat make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fc-cat' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-cat' Making all in fc-list make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fc-list' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-list' Making all in fc-match make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fc-match' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-match' Making all in fc-query make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fc-query' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-query' Making all in fc-scan make[2]: Entering directory `/home/shane/fontconfig-2.8.0/fc-scan' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/fc-scan' Making all in conf.d make[2]: Entering directory `/home/shane/fontconfig-2.8.0/conf.d' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/conf.d' Making all in doc make[2]: Entering directory `/home/shane/fontconfig-2.8.0/doc' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/doc' Making all in test make[2]: Entering directory `/home/shane/fontconfig-2.8.0/test' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/shane/fontconfig-2.8.0/test' make[2]: Entering directory `/home/shane/fontconfig-2.8.0' make[2]: Leaving directory `/home/shane/fontconfig-2.8.0' make[1]: Leaving directory `/home/shane/fontconfig-2.8.0' shane@shane:~/fontconfig-2.8.0$ Link to comment Share on other sites More sharing options...
Storm Clarence Posted December 6, 2012 Share Posted December 6, 2012 Your system log files will tell you why the application is crashing. The Firestorm log files will tell you why Firestorm is crashing. The output from *make* tells us nothing relevant as to why the application is crashing. PS However, if you did have success in building fontconfig why can you not find the three libs? Are they not in the directory as stated in the blog you were reading? Link to comment Share on other sites More sharing options...
Qie Niangao Posted December 7, 2012 Share Posted December 7, 2012 Sorry you went to all that trouble with fontconfig because I don't think there's any need to follow those instructions at all. The version of firestorm you're using does not have the libfontconfig problem that all that stuff was trying to work around. Anyway, we now know that firestorm runs for a couple minutes before crashing, and that helps, because now the firestorm console log (either in the terminal, or in ~/.firestorm/logs/Firestorm.log) should tell more about what's going wrong. And following Storm's suggestion, now that you have that log, you may want to take those details to the Firestorm support people. But we'll keep trying, if prefer. Either way, the logs are going to be necessary to make much headway. (It may be easiest to copy it into pastebin... maybe skim through it to make sure it doesn't reveal any personal info that could be in your directory path names or anything.) Link to comment Share on other sites More sharing options...
brodeee Posted December 7, 2012 Author Share Posted December 7, 2012 ERROR: apport (pid 1830) Thu Dec 6 15:48:31 2012: called for pid 1797, signal 11, core limit 0 ERROR: apport (pid 1830) Thu Dec 6 15:48:31 2012: executable: /usr/lib/udisks2/udisksd (command line "/usr/lib/udisks2/udisksd --no-debug") ERROR: apport (pid 1830) Thu Dec 6 15:48:31 2012: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 1830) Thu Dec 6 15:48:33 2012: wrote report /var/crash/_usr_lib_udisks2_udisksd.0.crash ERROR: apport (pid 3118) Thu Dec 6 16:33:15 2012: called for pid 2470, signal 5, core limit 0 ERROR: apport (pid 3118) Thu Dec 6 16:33:15 2012: executable: /usr/bin/gedit (command line "gedit /home/shane/amd-driver-installer-catalyst-12.11-beta11-x86.x86_64.run") ERROR: apport (pid 3118) Thu Dec 6 16:33:15 2012: debug: session gdbus call: (true,) ERROR: apport (pid 3118) Thu Dec 6 16:33:15 2012: wrote report /var/crash/_usr_bin_gedit.1000.crash Link to comment Share on other sites More sharing options...
brodeee Posted December 7, 2012 Author Share Posted December 7, 2012 shane@shane:~$ cd /home/shane/phoenix_firestorm shane@shane:~/phoenix_firestorm$ ~/.firestorm/logs/Firestorm.log bash: /home/shane/.firestorm/logs/Firestorm.log: Permission denied shane@shane:~/phoenix_firestorm$ Link to comment Share on other sites More sharing options...
Darren Scorpio Posted December 7, 2012 Share Posted December 7, 2012 Maybe not the cause, but why are you installing beta drivers instead of the stable ones? Have you tried installing the stable drivers and see if the result is the same? Link to comment Share on other sites More sharing options...
brodeee Posted December 7, 2012 Author Share Posted December 7, 2012 No reason on the beta, I'm downloading the regular one now. Link to comment Share on other sites More sharing options...
Darren Scorpio Posted December 7, 2012 Share Posted December 7, 2012 Make sure you uninstall all traces of the previous driver before installing the new one. Link to comment Share on other sites More sharing options...
Storm Clarence Posted December 7, 2012 Share Posted December 7, 2012 brodeee wrote: shane@shane:~$ cd /home/shane/phoenix_firestorm shane@shane:~/phoenix_firestorm$ ~/.firestorm/logs/Firestorm.log bash: /home/shane/.firestorm/logs/Firestorm.log: Permission denied shane@shane:~/phoenix_firestorm$ The second line shane@shane:~/phoenix_firestorm$ ~/.firestorm/logs/Firestorm.log The tilde is NOT a command in the Linux shell. A tilde is NOT how to print a file to the terminal; of course bash returned an error. Link to comment Share on other sites More sharing options...
Facebook
Instagram
Twitter
YouTube
Flickr
Recommended Posts
Please take a moment to consider if this thread is worth bumping.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now