glib2-2.32.4-1.fc17.i686 crashes during installation (segfault)
I had skype working well under Fedora 15 and earlier. After upgrading to fedora 17 I tried to install both current (4.0.08) static and rpm versions of skype as well as the static 2.2.0.35. All three crash on start with Segmentation fault. I used ldd to identify all required libraries and re-installed the relevant packages one by one. One of the packages (see Subject) gave the following warning during the re-installation:
=================== Installing : glib2-2.32.4-1.fc17.i686 1/1 Non-fatal POSTIN scriptlet failure in rpm package glib2-2.32.4-1.fc17.i686 /var/tmp/rpm-tmp.w4EW8A: line 2: 18234 Segmentation fault (core dumped) gio-querymodules-32 /usr/lib/gio/modules warning: %post(glib2-2.32.4-1.fc17.i686) scriptlet failed, exit status 139 Verifying : glib2-2.32.4-1.fc17.i686 1/1 ===================== I also noticed that /usr/lib/gio/modules contains only libgiofam.so while the 64 version has another 7 files including giomodule.cache I considered removing glib2-2.32.4-1.fc17.i686 but I am afraid it may effect other part of the system. Any suggestion how to proceed to install this library properly (and hopefully get skype working) would be very appreciated. |
probably your skype is a 32bit app and your os is a 64bit system.
|
Quote:
|
Quote:
and the FULL error also there should NOT be a conflict with the 64 bit and the auto installed 32 bit legacy compatibility that is UNLESS you are manually trying to install a mismatched version Quote:
if you did you would uninstall about 98% of Fedora17 ( about 600 dependencies - a guess) |
Quote:
BTW, I am new to using this forum - how do you look at new responses in a thread without starting all over again? I can't find any "see new" to click on .. I see that I don't know how to interrupt the quoted text neither |
Quote:
one issue with using a FULL name "glib2-2.32.4-1.fc17.i686 " this can cause all kinds of problems the 32 bit conpat should get puled Code:
su - |
Quote:
... 3.5.3-1.fc17.x86_64 #1 SMP Wed Aug 29 18:46:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux I followed your advice how to reinstall glib2 - two packages were selected - with similar warning: =================== Is this ok [y/N]: y Downloading Packages: (1/2): glib2-2.32.4-1.fc17.i686.rpm | 1.9 MB 00:09 (2/2): glib2-2.32.4-1.fc17.x86_64.rpm | 1.9 MB 00:09 ------------------------------------------------------------------------------------------------------------------------- Total 211 kB/s | 3.9 MB 00:18 Running Transaction Check Running Transaction Test Transaction Test Succeeded Running Transaction Installing : glib2-2.32.4-1.fc17.x86_64 1/2 Installing : glib2-2.32.4-1.fc17.i686 2/2 Non-fatal POSTIN scriptlet failure in rpm package glib2-2.32.4-1.fc17.i686 /var/tmp/rpm-tmp.BwYg4k: line 2: 21839 Segmentation fault (core dumped) gio-querymodules-32 /usr/lib/gio/modules warning: %post(glib2-2.32.4-1.fc17.i686) scriptlet failed, exit status 139 Verifying : glib2-2.32.4-1.fc17.i686 1/2 Verifying : glib2-2.32.4-1.fc17.x86_64 2/2 Installed: glib2.i686 0:2.32.4-1.fc17 glib2.x86_64 0:2.32.4-1.fc17 Complete! ================= Thank you very much for attending to this! |
can you install anything else (only glibc will cause segfault or other packages too?)
|
Quote:
|
An idea - att John VV:
How about if I reinstall all packages on which glib2 depends? "yum reinstall [package]" checks dependencies can I force it to re-install them? If not, "yum deplist glib2" gives two long lists looking like ======== package: glib2.i686 2.32.4-1.fc17 dependency: /bin/sh provider: bash.x86_64 4.2.37-2.fc17 dependency: libc.so.6 provider: glibc.i686 2.15-56.fc17 dependency: libc.so.6(GLIBC_2.0) provider: glibc.i686 2.15-56.fc17 ======== where the provider is often repeated. So I can reinstall them manually. If I do should I use the search first, as you suggested, or just "yum reinstall glibc.i686" ? I would like to avoid of installing the whole fc17 again ... |
Right now i am not running fedora so it is only from past experience and current with ScientificLinux
so on to debugging what is at the end of the yum.log ( /var/log/yum.log) is that glib2 ( 32bit) listed as installed ? then what repos are installed Code:
su - Now this is all for dealing with the VERY OLD linux version of "Skype" or the Now owned by Microsoft and in call Advertising supported the current fedora 16 32 bit version skype-4.0.0.8-fedora.i586 ( dated July 13 2012 ) http://www.skype.com/intl/en-us/get-...loading.fedora There ARE other VOIP programs that are probably in the repos . Like Ekiga or Sip ? or even "ekg2-core-0.3.1-2.fc17.x86_64.rpm" "ekg2-voip-0.3.1-2.fc17.x86_64.rpm" https://fedoraproject.org/wiki/VoIP |
Yes, yum.log reports glib2 installed every time I've tried it.
yum repolist all Loaded plugins: langpacks, presto, refresh-packagekit repo id repo name status adobe-linux-x86_64 Adobe Systems Incorporated enabled: 2 fedora Fedora 17 - x86_64 enabled: 27,033 fedora-debuginfo Fedora 17 - x86_64 - Debug disabled fedora-source Fedora 17 - Source disabled updates Fedora 17 - x86_64 - Updates enabled: 8,269 updates-debuginfo Fedora 17 - x86_64 - Updates - Debug disabled updates-source Fedora 17 - Updates Source disabled updates-testing Fedora 17 - x86_64 - Test Updates disabled updates-testing-debuginfo Fedora 17 - x86_64 - Test Updates Debu disabled updates-testing-source Fedora 17 - Test Updates Source disabled repolist: 35,304 Also, my skype 2.2... is not very old, it is the last which worked and i tried both static and rpm versions 4.0.0.8 with the same result. They also require glib2. Microsoft ownership/advertising is unfortunate - do they claim resposibility for the Linux versions, too? Can you comment on my last post (reinstalling dependencies), please? |
Quote:
that is an unknown sometimes it dose fix things however i am guessing here The 4.0.0.8.rpm is for fedora 16 built for fedora 16 and fedora 16 WILL have a different version of glib installed so i am guessing it is explicitly looking for the fedora 16 version welcome to the world of fedora Fedora is VERY often WAY too NEW to run most prebuilt binary blobs it is a fact of " fedora life" there are a BUNCHE of even "newish" programs that will not even build on the current fedora if it is not GCC that is TOO new then gtk ,or libpng,or libssl , or something even NEW programs have to be hacked to build with the VERY NEW gcc fedora uses |
All times are GMT -5. The time now is 07:55 PM. |