LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-21-2014, 07:42 AM   #1
vovim
Member
 
Registered: Nov 2011
Location: England
Distribution: Slackware64 current and Slackware arm current
Posts: 64

Rep: Reputation: Disabled
Multilib problem - segmentation fault in gtk-query-immodules-2.0-32 --update-cache


Hi, I have a problem with the 32bit part of multilib. At boot time I get this error :
Code:
  /usr/bin/gtk-query-immodules-2.0-32 --update-cache
/usr/bin/update-gtk-immodules-2.0: line 14:  1042 Segmentation fault      
/usr/bin/gtk-query-immodules-2.0-32 --update-cache 2> /dev/null
I have seen the post of cwizardone (28-03-14) but I don't think that that post relates to my problem as I do not have the lesstif-compat32 package installed.

I have removed and re-installed the 32bit compatibility layer of multilib with compat32pkg and I still gert the same error at boot time.

I have run strace on /usr/bin/gtk-query-immodules-2.0-32 --update-cache and it was initially failing on missing directories so I created the following directories :

Code:
openat(AT_FDCWD, "/root/.gtk-2.0/2.10.0/i486-slackware-linux/immodules", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x21c80f9f} ---
+++ killed by SIGSEGV +++
Segmentation fault
/usr/lib/gtk-2.0/2.10.0/i486-slackware-linux/immodules

Code:
openat(AT_FDCWD, "/root/.gtk-2.0/i486-slackware-linux/immodules", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xc7b2af7c} ---
+++ killed by SIGSEGV +++
Segmentation fault
/usr/lib/gtk-2.0/i486-slackware-linux/immodules

Code:
openat(AT_FDCWD, "/root/.gtk-2.0/immodules", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb5d7fdfb} ---
+++ killed by SIGSEGV +++
Segmentation fault
/usr/lib/gtk-2.0/immodules

Creating these directories has allowed it to continue a bit further each time. However it is now failing with the following output from strace :
Code:
openat(AT_FDCWD, "/usr/lib/gtk-2.0/2.10.0/i486-slackware-linux/immodules", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3
getdents64(3, /* 2 entries */, 32768)   = 48
getdents64(3, /* 0 entries */, 32768)   = 0
close(3)                                = 0
openat(AT_FDCWD, "/usr/lib/gtk-2.0/2.10.0/immodules", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3
getdents64(3, /* 24 entries */, 32768)  = 832
stat64("/usr/lib/gtk-2.0/2.10.0/immodules/im-ti-er.so", {st_mode=S_IFREG|0755, st_size=19388, ...}) = 0
open("/usr/lib/gtk-2.0/2.10.0/immodules/im-ti-er.so", O_RDONLY|O_CLOEXEC) = 4
read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200\10\0\0004\0\0\0"..., 512) = 512
fstat64(4, {st_mode=S_IFREG|0755, st_size=19388, ...}) = 0
mmap2(NULL, 18136, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = 0xfffffffff775a000
mmap2(0xf775b000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x1000) = 0xfffffffff775b000
close(4)                                = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x317aa91f} ---
+++ killed by SIGSEGV +++
Segmentation fault
I am now stuck.

Does anybody have any ideas on what I can do to get multilib working properly ?

Thanks.
 
Old 10-22-2014, 11:58 AM   #2
vovim
Member
 
Registered: Nov 2011
Location: England
Distribution: Slackware64 current and Slackware arm current
Posts: 64

Original Poster
Rep: Reputation: Disabled
I think that this problem was somehow caused by using the proprietary nvidia driver (version 340.46).

I had previously had a problem with this nvidia proprietary driver deleting the libEGL.la file. I replaced the file with the copy from its backup according to this post (https://devtalk.nvidia.com/default/t...lib-libegl-la/).

I have now replaced the proprietary nvidia driver with the nvidia driver from SlackBuilds and the problem seems to have gone away.

I will continue to monitor this for the next few days and if the problem does not re-appear then I will mark this thread as solved.
 
Old 10-22-2014, 01:42 PM   #3
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657
Out of curiosity, did you build the previous Nvidia driver after you went multi-lib? That needs to be done to add the 32bit compatibility. If you did, and you already knew this, don't mind my little post
 
Old 10-23-2014, 05:56 AM   #4
vovim
Member
 
Registered: Nov 2011
Location: England
Distribution: Slackware64 current and Slackware arm current
Posts: 64

Original Poster
Rep: Reputation: Disabled
bassmadrigal: Yes, I did build the previous Nvidia driver I was using (the proprietary one) after I went multi-lib. That needs to be done because multilib installs a different mesa to the one which the Nvidia proprietary driver uses.
 
Old 10-23-2014, 07:55 AM   #5
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483
I use the 319.49 for slackware64 14.1 multi with a gt640 I have tried the 340 series did not see any benefits most of the fixes were for newer cards and compatibility with the newer xorg and mesa.
And now the 340 will be the last drivers my old Legacy gt9600 card I run slackware64 current multi-lib with that driver and never seen a problem like that.
After installing a new kernel in Slackware64-current multi-lib
How I upgrade my driver is. go to runlevel 3 and uninstall the nvidia driver. Then reinstall both mesa x86_64 then mesa compat32 then reboot.
then I run the sh NVidia-run and then startx all is good. I would suggest for newer cards need to run the latest drivers for the latest xorg and mesa.
Quote:
you may want to reinstall gtk 2 and 3 for both x86_64 and compat32 see what happens.
My way of installing multilib and keeping it updated. use the multilib install script that places a copy of. multilib in /var/cache/.
create a file name it multilib-install-14.1
Code:
#!/bin/sh

##INSTALL NEW MULTI-LIB
mkdir /var/cache/multilib/
mkdir /var/cache/multilib/slackware64-compat32
rsync -r -a -v --bwlimit=300 --delete --progress --stats rsync://rsync.slackware.org.uk/people/alien/multilib/14.1/ /var/cache/multilib/
cd /var/cache/multilib/
upgradepkg --reinstall --install-new *.t?z
cd /var/cache/multilib/slackware64-compat32#installpkg *?/*.t?z


##UPGRADE MULTI-LIB
rsync -r -a -v --bwlimit=500 --delete --progress --stats rsync://rsync.slackware.org.uk/people/alien/multilib/14.1/ /var/cache/multilib/
cd /var/cache/multilib
upgradepkg --install-new *.t?z
cd /var/cache/multilib/slackware64-compat32
upgradepkg --install-new *?/*.t?z
run that as root
Code:
sh multilib-install-14.1
it installs the multilib for slackware64-14.1.

after that you can checkout how I keep it up to date with everything.
I have tried it all slackpkg+ I even installed the new MLED and using slackpkg+ it still keeps breaking packages so I will not go there.

check here for my one click update for the system I have used for three distro upgrades and system updates. http://www.linuxquestions.org/questi...on-4175515564/

Last edited by Drakeo; 10-23-2014 at 08:14 AM.
 
Old 10-25-2014, 07:51 PM   #6
vovim
Member
 
Registered: Nov 2011
Location: England
Distribution: Slackware64 current and Slackware arm current
Posts: 64

Original Poster
Rep: Reputation: Disabled
Well, I have now done quite a few reboots and still no segmentation fault error in the "/usr/bin/gtk-query-immodules-2.0-32 --update-cache" command so I am now going to mark this as solved and close it.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Multilib related 32 Bit gtk.immodules Segmentation Fault. cwizardone Slackware 11 03-28-2014 08:32 AM
[SOLVED] System-Config-Printer -- > GTK /Segmentation Fault jv2112 Linux - Newbie 2 12-30-2012 07:47 AM
ALL GTK APPS do a segmentation fault when X win in monochrome smeezekitty Linux - Newbie 10 10-27-2009 01:25 AM
Segmentation Fault - Gtk Static App boogy Programming 2 01-22-2007 06:44 AM
segmentation fault with my Gtk Application jaganmolleti Programming 1 03-18-2003 11:05 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:50 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration