beta release ~amd64, Intel GMA - G33, Gallium3D (x86) - Ok :) Reproducible: Always
Created attachment 300249 [details] sci-geosciences/googleearth-6.2.0.5905.ebuild
+1 6.2 should provide much better rendering http://googleblog.blogspot.com/2012/01/google-earth-62-its-beautiful-world.html
Created attachment 300501 [details] sci-geosciences/googleearth-6.2.0.5905 Fix QA TEXTREL
Created attachment 300503 [details, diff] decimal-separator.patch
Created attachment 300505 [details] googleearth-mimetypes.xml
~amd64, Nvidia 290, - Ok :))
unfortunately it crashes immediately after start here (~x86), seems qt releated (i have bundled qt useflag though).
(In reply to comment #7) > unfortunately it crashes immediately after start here (~x86), seems qt releated > (i have bundled qt useflag though). Please do, post "eselect mesa list"
!!! Error: Can't load module mesa exiting :) i use older mesa 7.8.2 and free radeon drivers (and i can't upgrade them since there is unfixed bug causing slowness on my box)
(In reply to comment #9) > !!! Error: Can't load module mesa > exiting > > :) i use older mesa 7.8.2 and free radeon drivers (and i can't upgrade them > since there is unfixed bug causing slowness on my box) I doubt that the latest version of Google Earth will work with the old Mesa, as the program according to tests focused on Gallium3D, but not Mesa3D
understood. perhaps to bump some requirements on the deps in the ebuild?
(In reply to comment #11) > understood. perhaps to bump some requirements on the deps in the ebuild? These requirements regarding Mesa3D vs Gallium3D still only at the stage of verification. Although preliminary results indicate it is in contact with Gallium3D. However, working with Mesa3D (Google Earth is only 32bit) leads to a crash when programm starting in almost all cases.
the backtrace from the crash doesn't look to be mesa related though: Stacktrace from glibc: ./libgoogleearth_free.so(+0xab953)[0xb7768953] ./libgoogleearth_free.so(+0xabad3)[0xb7768ad3] [0xb77d7400] /lib/libc.so.6(abort+0x18e)[0xb52aaaae] /lib/libc.so.6(+0x69c15)[0xb52e4c15] /lib/libc.so.6(+0x6fb92)[0xb52eab92] /lib/libc.so.6(+0x70dee)[0xb52ebdee] ./libQtCore.so.4(_Z5qFreePv+0x1d)[0xb742609d] ./libQtCore.so.4(+0x12496b)[0xb74e796b] ./libQtCore.so.4(_ZN4QUrlD1Ev+0x43)[0xb74dcbf3] /lib/libc.so.6(__cxa_finalize+0xb5)[0xb52ac5f5] ./libspatial.so(+0x38834)[0xb47f1834] ./libspatial.so(+0x1c0e60)[0xb4979e60] /lib/ld-linux.so.2(+0xfe31)[0xb77e7e31] /lib/libc.so.6(+0x31229)[0xb52ac229] /lib/libc.so.6(on_exit+0x0)[0xb52ac290] /lib/libc.so.6(__libc_start_main+0xee)[0xb52952ae] ./googleearth-bin[0x8048671]
(In reply to comment #13) > the backtrace from the crash doesn't look to be mesa related though: > Stacktrace from glibc: > ./libgoogleearth_free.so(+0xab953)[0xb7768953] > ./libgoogleearth_free.so(+0xabad3)[0xb7768ad3] > [0xb77d7400] > /lib/libc.so.6(abort+0x18e)[0xb52aaaae] > /lib/libc.so.6(+0x69c15)[0xb52e4c15] > /lib/libc.so.6(+0x6fb92)[0xb52eab92] > /lib/libc.so.6(+0x70dee)[0xb52ebdee] > ./libQtCore.so.4(_Z5qFreePv+0x1d)[0xb742609d] > ./libQtCore.so.4(+0x12496b)[0xb74e796b] > ./libQtCore.so.4(_ZN4QUrlD1Ev+0x43)[0xb74dcbf3] > /lib/libc.so.6(__cxa_finalize+0xb5)[0xb52ac5f5] > ./libspatial.so(+0x38834)[0xb47f1834] > ./libspatial.so(+0x1c0e60)[0xb4979e60] > /lib/ld-linux.so.2(+0xfe31)[0xb77e7e31] > /lib/libc.so.6(+0x31229)[0xb52ac229] > /lib/libc.so.6(on_exit+0x0)[0xb52ac290] > /lib/libc.so.6(__libc_start_main+0xee)[0xb52952ae] > ./googleearth-bin[0x8048671] It does not appear. The problem stems from the fact that early start of Google Earth is the collapse of the window. And it happens on a graphical level. We see in the backtrace Qt ..., but in reality, due to Mesa. Many times referred to the sentence "Disable all visual effects in the system before you start Google Earth". Alas, it no longer helps versions Google Earth 6x... :((
Created attachment 302519 [details] sci-geosciences/googleearth-6.2.1.6014.ebuild
>>> Emerging (1 of 1) sci-geosciences/googleearth-6.2.1.6014 from x-portage * GoogleEarthLnux-6.2.1.6014_i386.deb RMD160 SHA1 SHA256 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking GoogleEarthLnux-6.2.1.6014_i386.deb to /var/tmp/portage/sci-geosciences/googleearth-6.2.1.6014/work deb2targz: converting 'GoogleEarthLnux-6.2.1.6014_i386.deb' ... deb2targz: skipping section 'debian-binary' deb2targz: skipping section 'control.tar.gz' deb2targz: wrote 'GoogleEarthLnux-6.2.1.6014_i386.tar.lzma' mv: cannot stat `GoogleEarthLnux-6.2.1.6014_i386.tar.gz': No such file or directory * ERROR: sci-geosciences/googleearth-6.2.1.6014 failed (unpack phase): * failure unpacking GoogleEarthLnux-6.2.1.6014_i386.deb * * Call stack: * ebuild.sh, line 85: Called src_unpack * environment, line 2532: Called default * phase-functions.sh, line 798: Called _eapi2_src_unpack * phase-functions.sh, line 789: Called _eapi0_src_unpack * phase-helpers.sh, line 530: Called unpack 'GoogleEarthLnux-6.2.1.6014_i386.deb' * phase-helpers.sh, line 353: Called die * The specific snippet of code: * mv -f "${y%.deb}".tar.gz data.tar.gz || die "$myfail" * * If you need support, post the output of 'emerge --info =sci-geosciences/googleearth-6.2.1.6014', * the complete build log and the output of 'emerge -pqv =sci-geosciences/googleearth-6.2.1.6014'. * This ebuild is from an overlay named 'x-portage': '/usr/local/portage/' * The complete build log is located at '/var/log/portage/sci-geosciences:googleearth-6.2.1.6014:20120301-070805.log'. * The ebuild environment file is located at '/var/tmp/portage/sci-geosciences/googleearth-6.2.1.6014/temp/environment'. * S: '/var/tmp/portage/sci-geosciences/googleearth-6.2.1.6014/work'
Created attachment 303801 [details] sci-geosciences/googleearth-6.2.1.6014.ebuild Small mistake. Fixed ebuild. remove deb2targz
Created attachment 303803 [details] sci-geosciences/googleearth-6.2.1.6014.ebuild
*** Bug 392315 has been marked as a duplicate of this bug. ***
*googleearth-6.2.1.6014 (01 Mar 2012) 01 Mar 2012; Vlastimil Babka <caster@gentoo.org> +googleearth-6.2.1.6014.ebuild, +files/googleearth-mimetypes.xml: Version bump, bug #401297. Icon and elog improvements thanks to Oschtan. Decimal separator bug appears to be solved upstream, removing the locale patch. Reopen bug #262780 if it still occurs.
Why was deleted row QA_DT_HASH="opt/google/earth/free/.*" ?
The presence of app-arch/deb2targz in the system causes a problem when unpacking DEB-packages. Previously, the condition on the !app-arch/deb2targz existed for google-chrome, while the function unpack this package was not implemented in the eclass. Or DEB-packages are no longer trying to be unpacked app-arch/deb2targz?
(In reply to comment #21) > Why was deleted row > QA_DT_HASH="opt/google/earth/free/.*" ? Ugh, because it seems the notices from portage are now misleading. Fixed, thanks. (In reply to comment #22) > The presence of app-arch/deb2targz in the system causes a problem when > unpacking DEB-packages. Previously, the condition on the !app-arch/deb2targz > existed for google-chrome, while the function unpack this package was not > implemented in the eclass. Or DEB-packages are no longer trying to be > unpacked app-arch/deb2targz? Yes, by using unpack_deb from eclass, deb2targz is no longer a problem. So it's better than blocking packages.
