[kinda solved!]nvidia-settings segmentation fault

hi
i use nvidia-settings to adjust my graphic card setup. I haven't used it in a while though (in fact, i think it was using kde about 8 months ago), and tried to fire it up today on openbox, this is what i get;
$ nvidia-settings
(nvidia-settings:6351): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(nvidia-settings:6351): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Segmentation fault
$
I have never installed murrine ever! is it as simple an issue to fix as install murrine??
i tried to pacman it & yaourt it, but its not found! before I go about finding the source code to compile, i was wondering if anyone else has any ideas?
thanks
Last edited by ninjaprawn (2009-02-01 02:40:17)

ghostHack wrote:
I find it a bit unlikely that a missing theme engine would cause a seg fault, however the package you need is in [community] and is called 'gtk-engine-murrine'.
What version of nvidia-utils do you have? and is the ret of your system up to date?
hi, thanks for that. I installed the theme engine, now the error message only says;
$ nvidia-settings
Segmentation Fault
$
I keep my system fully updated all the time, but how do i find out what version of nvidia-utils i am using??

Similar Messages

Nvidia-settings segmentation fault

I have nvidia 270.41.06-1 installed. And when I try to run nvidia-settings it gives me segmentation fault.
Anyone else experience this problem? I think it started happening to me only on very recent update.
PS. I am using KDE 64-bit
Last edited by kdar (2011-04-21 06:18:48)

I am on x86_64 also, XFCE4, and it segfaults on me too, here is the log (found in the kernel.log):
It segfaults only when trying to SAVE TO X CONFIGURATION FILE (xorg.conf) (and does not update xorg.conf)
nvidia-settings[1617]: segfault at 7f32b3a09ae0 ip 00007f32b3a09ae0 sp 00007fffca33e0b8 error 15
UPDATE: when I delete the ~/.nvidia-settings.rc file (in all my user's directories, including the root directory)
I can then SAVE the CONFIGURATION (as root). I just made sure aftewards, to save the new ~/.nvidia-settings.rc
too. (to all my user's directories).
I didn't have to change themes, or anything else. Just delete the old ~/.nvidia-settings.rc file from each user,
including root, then issue # sudo nvidia-setttings and save the X configurations to file. It worked.. then
saved the settings to each user's directory (~/.nvidia-settings-rc)
Last edited by Kilzool (2011-05-05 05:39:23)

[Solved]xfce 4.12: Display Settings - Segmentation fault (core dumped)

Just upgraded to Xfce 4.12 from 4.10 last week I have just one big issue so far: the display settings panel doesn't work. When I click on it, nothing happens.
If I run from terminal xfce4-display-settings I get "Segmentation fault (core dumped)" and with "gdb xfce4-display-settings" the output says "Reading symbols from xfce4-display-settings...(no debugging symbols found)...done."
What I'm thinking of is a missing dep. Since upgraded to 4.12 I also have a problem with Docky which displays a horizontal black line with shadow on my screen. I don't know if it's related, but this is the output when I run Docky from terminal: http://pastebin.com/cT5XNvWU
Before upgrading to 4.12, for some months, I had issues with xrandr which didn't detect my laptop screen resolution (full hd) and I had to manually add a profile that fits my normal resolution, otherwise I would had a resolution of 640x480px (this one is shown right now in my nVidia settings in "X Screen Information" section). I don't know if it's related, but I'm just saying.
I'm using bumblebee for my nvidia card & xf86-video-intel for my integrated graphics card. Yeah, I have hybrid graphics (Asus laptop).
General info:
- arch x86_64
- kernel 3.18.6-1
- slim display manager (just saw the warning on archwiki that this one has been abandoned)
- bumblebee & intel driver
- xfce 4.12
Anyone facing the same issue?
Last edited by kr3ck3n (2015-03-22 12:04:01)

kr3ck3n wrote:If I run from terminal xfce4-display-settings I get "Segmentation fault (core dumped)" and with "gdb xfce4-display-settings" the output says "Reading symbols from xfce4-display-settings...(no debugging symbols found)...done."
While not logged in, try renaming ~/.config/xfce4/xfconf/xfce-perchannel-xml/display.xml. A new one will be re-created on next login. There may be something in that file creating the crash.
What I'm thinking of is a missing dep. Since upgraded to 4.12 I also have a problem with Docky which displays a horizontal black line with shadow on my screen. I don't know if it's related, but this is the output when I run Docky from terminal: http://pastebin.com/cT5XNvWU
Settings Manager >> Window Manager Tweaks >> Compositor tab, and uncheck "Show shadows under dock windows".

[SOLVED] nvidia-settings startup delay

Does anyone happen to know why nvidia-settings takes a good 3-4 minutes to open after open it from the menu or the terminal, sudo or as user? I'm on xfce and didn't have this problem on Cinnamon or Ubuntu Gnome-Shell.
I have to use this settings panel to turn "on" my secondary display when I plug it up also for some reason, this is new too, but I suppose not relevant to the original question. Bonus points if you know why this is too!
Last edited by Somnus (2013-07-29 12:54:00)

Actually, chalk this up to not looking hard enough again. The suggestion to add
127.0.0.1 myhostname
to /etc/hosts seems to have solved the issue.
Reference:
https://bbs.archlinux.org/viewtopic.php?id=161837

(SOLVED) xfce4-appfinder Segmentation fault

Hi all,
I just discovered yesterday that xfce4-appfinder ins't working on my desktop (it works fine on my laptop though). Running it from xfce it just does nothing but if I run it from the terminal I just get this message: Segmentation fault.
I'm pretty sure it worked like two months ago. I installed some apps and did some upgrades from that time on. Already tried to downgrade xfce4-appfinder to the previous version but I still got the same error.
Does anyone have/had this problem?
Thanks in advance.
Last edited by harroxelas (2012-05-01 10:09:53)

Please mark your thread title as [solved] to avoid confusion .

[SOLVED] nvidia-settings taking a long time to load.

I just got an nvidia card yesterday, so I'm not sure if this is regular behavior, but nvidia-settings take about 3-5 minutes to load. I'm using KDE. When I try to load it from the terminal I see a bunch of errors like this:
nvidia-settings
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:335: Unable to locate image file in pixmap_path: "Expander/expander-normal-c.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:337: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:344: Unable to locate image file in pixmap_path: "Expander/expander-prelight-c.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:346: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:353: Unable to locate image file in pixmap_path: "Expander/expander-active-c.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:355: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:362: Unable to locate image file in pixmap_path: "Expander/expander-insens-c.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:364: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:372: Unable to locate image file in pixmap_path: "Expander/expander-normal-sc.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:374: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:381: Unable to locate image file in pixmap_path: "Expander/expander-prelight-sc.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:383: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:390: Unable to locate image file in pixmap_path: "Expander/expander-active-sc.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:392: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:409: Unable to locate image file in pixmap_path: "Expander/expander-normal-se.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:411: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:418: Unable to locate image file in pixmap_path: "Expander/expander-prelight-se.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:420: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:427: Unable to locate image file in pixmap_path: "Expander/expander-active-se.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:429: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:446: Unable to locate image file in pixmap_path: "Expander/expander-normal-e.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:448: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:455: Unable to locate image file in pixmap_path: "Expander/expander-prelight-e.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:457: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:464: Unable to locate image file in pixmap_path: "Expander/expander-active-e.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:466: Background image options specified without filename
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:473: Unable to locate image file in pixmap_path: "Expander/expander-insens-e.png"
/home/beelzebud/.themes/qt4/gtk-2.0/gtkrc:475: Background image options specified without filename
I searched around for this issue, and found people who had similar problems with Firefox in the past, but I never see anyone who has solved it. On my setup I don't have this issue with any other app besides nvidia-settings.
Last edited by Beelzebud (2013-05-02 17:13:52)

Beelzebud wrote:
Ok today i noticed that if I delete ~/.nvidia-settings-rc, the UI loads instantly just like it's supposed to. I started googling around and found that there is indeed a bug in nvidia-settings which has something to do with the way it handles a machine's hostname.
If I edit ~/.nvidia-settings-rc and delete every line that starts with my hostname, the program loads instantly. When you close nvidia-settings, it will re-write the file, and the next time you start it, you're back to waiting a long time for the UI to load. It seems there is nothing that can be done to truly fix this until nvidia fixes the bug that is causing it.
Thank you! I had this problem since the latest update.
To avoid having to remove/edit the configuration file, I have added a line in /etc/hosts:
127.0.0.1 myhostname

[SOLVED] Steam Client Segmentation Fault

The Steam client crashes with a segmentation fault when attempting to run "STEAM_RUNTIME=0 steam".
This wouldn't be so much of an issue if disabling the runtime wasn't required by SimpleScreenRecorder to inject it's libraries into steam games.
I've run steam through gdb with runtime disabled, here are a few errors that stand out:
/home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/vgui2/src/../vgui_surfacelib/FontManager.cpp (276) : Assertion Failed: descs.Count() >= 1
/home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/vgui2/src/../vgui_surfacelib/FontManager.cpp 276 Assertion Failed: descs.Count() >= 1
Program received signal SIGTRAP, Trace/breakpoint trap.
0xf4ccfd87 in AssertMsgImplementation ()
from /home/bigstiffy/.local/share/Steam/ubuntu12_32/libtier0_s.so
Program received signal SIGSEGV, Segmentation fault.
0xf7bfae86 in __strlen_sse2_bsf () from /usr/lib32/libc.so.6
Requested Force create but SharedObjectMutex already created
Forced create but already created for SharedObjectEvent
Forced create but already created for SharedObjectEvent
After a few hours of looking for answers, it seems that Steam requires an older version of lib32-glibc than what is currently installed,
although continues to functions so long as runtime is enabled by default. Running steam with default settings through gdb showed no
errors regarding either "libtier0_s.so" or "libc.so.6".
Is there a way to obtain an older package of lib32-glibc from the repo to test if this is the culprit?
Building and compiling glibc from source is just a little bit outside my realm of understanding.
Last edited by bigstiffy (2015-04-18 02:02:27)

Also following some information from another thread, I ran
STEAM_RUNTIME=0 strace -o tmp steam; head tmp
And got this output:
execve("/usr/bin/steam", ["steam"], [/* 32 vars */]) = 0
brk(0) = 0x1c89000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=242411, ...}) = 0
mmap(NULL, 242411, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb6211bb000
close(3) = 0
open("/usr/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\1\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1984416, ...}) = 0
So the Steam client is looking for ld.so.preload where it doesn't exist, and accessing the 64bit glibc library.
I think that when Steam runs with runtime disabled, it is supposed to use the 32bit libraries, but it doesn't search
in /usr/lib32 when the runtime is disabled. I rolled back lib32-glibc to 2.20-2 (Dec 1st, 04) and there was no change.
Any ideas?

[Solved] Get a segmentation fault message when try to run a Fullrecall

I'm running on Arch x86_64.
Then install this package with the packer.
https://aur.archlinux.org/packages/fullrecall/
run it with the terminal and get a segmentation fault message.
I have tried to install some lib32-* but still no luck.
http://sophie.zarb.org/distrib/Mageia/2 … 2f35d/deps
Any ideas ?
Otherwise, I will run it on Wine instead.
Last edited by fieldfirst (2013-03-25 07:16:53)

The fullrecall package is unmaintained, poorly written, and out of date (the latest version on the fullrecall website is 1.5.2). It's really hard to say why it is segfaulting but I would bet that it is because fullrecall is distributed as a binary rather than as source files. This means that it links against very specific versions of its dependencies, none of which are listed in the PKGBUILD. It's very possible that the versions in the arch repos of the various lib32-* dependencies that you installed are newer versions than the binary program requires.
You could try running namcap[1] on the built package and look for the specific version of the dependency you need in the Arch Rollback Machine[2], but I'm not sure how much that will help you. If you do manage to get it working, please adopt and update the package in the AUR.
[1]https://www.archlinux.org/packages/extra/any/namcap/
[2]http://arm.konnichi.com/
Last edited by jynnantonix (2013-03-24 18:32:00)

[SOLVED] cinnamon-settings doesn't start (segmentation fault)

Hi
I cannot start cinnamon-settings anymore, I get a segmentation fault error.
Here's the output of gdb:
Starting program: /usr/bin/python2 /usr/bin/cinnamon-settings
Got object file from memory but can't read symbols: File truncated.
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
process 1430 is executing new program: /usr/bin/python2.7
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe97ee700 (LWP 1434)]
Error while mapping shared library sections:
`/usr/lib/python2.7/site-packages/PIL/_imaging.so': not in executable format: File format not recognized
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7a9314b in PyModule_GetDict () from /usr/lib/libpython2.7.so.1.0
(gdb) bt
#0 0x00007ffff7a9314b in PyModule_GetDict () from /usr/lib/libpython2.7.so.1.0
#1 0x00007fffe1ddc68e in ?? ()
#2 0x0000000000c1e310 in ?? ()
#3 0x00007ffff7dd5058 in extensions () from /usr/lib/libpython2.7.so.1.0
#4 0x0000000000c1e310 in ?? ()
#5 0x00007ffff7b03807 in _PyImport_LoadDynamicModule ()
from /usr/lib/libpython2.7.so.1.0
#6 0x00007ffff7b018a1 in import_submodule () from /usr/lib/libpython2.7.so.1.0
#7 0x00007ffff7b01dc6 in ensure_fromlist () from /usr/lib/libpython2.7.so.1.0
#8 0x00007ffff7b02615 in PyImport_ImportModuleLevel ()
from /usr/lib/libpython2.7.so.1.0
#9 0x00007ffff7ae7d48 in builtin___import__ ()
from /usr/lib/libpython2.7.so.1.0
#10 0x00007ffff7a58773 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
#11 0x00007ffff7ae9a87 in PyEval_CallObjectWithKeywords ()
from /usr/lib/libpython2.7.so.1.0
#12 0x00007ffff7aecc96 in PyEval_EvalFrameEx ()
from /usr/lib/libpython2.7.so.1.0
#13 0x00007ffff7af0a90 in PyEval_EvalCodeEx ()
from /usr/lib/libpython2.7.so.1.0
#14 0x00007ffff7af0b89 in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0
#15 0x00007ffff7b009b9 in PyImport_ExecCodeModuleEx ()
from /usr/lib/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#16 0x00007ffff7b00c33 in load_source_module ()
from /usr/lib/libpython2.7.so.1.0
#17 0x00007ffff7b018a1 in import_submodule () from /usr/lib/libpython2.7.so.1.0
#18 0x00007ffff7b01dc6 in ensure_fromlist () from /usr/lib/libpython2.7.so.1.0
#19 0x00007ffff7b02615 in PyImport_ImportModuleLevel ()
from /usr/lib/libpython2.7.so.1.0
#20 0x00007ffff7ae7d48 in builtin___import__ ()
from /usr/lib/libpython2.7.so.1.0
#21 0x00007ffff7a58773 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
#22 0x00007ffff7ae9a87 in PyEval_CallObjectWithKeywords ()
from /usr/lib/libpython2.7.so.1.0
#23 0x00007ffff7aecc96 in PyEval_EvalFrameEx ()
from /usr/lib/libpython2.7.so.1.0
#24 0x00007ffff7af0a90 in PyEval_EvalCodeEx ()
from /usr/lib/libpython2.7.so.1.0
#25 0x00007ffff7af0b89 in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0
#26 0x00007ffff7b009b9 in PyImport_ExecCodeModuleEx ()
from /usr/lib/libpython2.7.so.1.0
#27 0x00007ffff7b00c33 in load_source_module ()
from /usr/lib/libpython2.7.so.1.0
#28 0x00007ffff7b018a1 in import_submodule () from /usr/lib/libpython2.7.so.1.0
#29 0x00007ffff7b01b1f in load_next () from /usr/lib/libpython2.7.so.1.0
#30 0x00007ffff7b024fe in PyImport_ImportModuleLevel ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/libpython2.7.so.1.0
#31 0x00007ffff7ae7d48 in builtin___import__ ()
from /usr/lib/libpython2.7.so.1.0
#32 0x00007ffff7a58773 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
#33 0x00007ffff7ae9a87 in PyEval_CallObjectWithKeywords ()
from /usr/lib/libpython2.7.so.1.0
#34 0x00007ffff7aecc96 in PyEval_EvalFrameEx ()
from /usr/lib/libpython2.7.so.1.0
#35 0x00007ffff7af0a90 in PyEval_EvalCodeEx ()
from /usr/lib/libpython2.7.so.1.0
#36 0x00007ffff7af0b89 in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0
#37 0x00007ffff7b009b9 in PyImport_ExecCodeModuleEx ()
from /usr/lib/libpython2.7.so.1.0
#38 0x00007ffff7b00c33 in load_source_module ()
from /usr/lib/libpython2.7.so.1.0
#39 0x00007ffff7b018a1 in import_submodule () from /usr/lib/libpython2.7.so.1.0
#40 0x00007ffff7b01b1f in load_next () from /usr/lib/libpython2.7.so.1.0
#41 0x00007ffff7b024fe in PyImport_ImportModuleLevel ()
from /usr/lib/libpython2.7.so.1.0
#42 0x00007ffff7ae7d48 in builtin___import__ ()
from /usr/lib/libpython2.7.so.1.0
#43 0x00007ffff7a58773 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
#44 0x00007ffff7ae9a87 in PyEval_CallObjectWithKeywords ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/libpython2.7.so.1.0
#45 0x00007ffff7aecc96 in PyEval_EvalFrameEx ()
from /usr/lib/libpython2.7.so.1.0
#46 0x00007ffff7af0a90 in PyEval_EvalCodeEx ()
from /usr/lib/libpython2.7.so.1.0
#47 0x00007ffff7af0b89 in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0
#48 0x00007ffff7b09fef in run_mod () from /usr/lib/libpython2.7.so.1.0
#49 0x00007ffff7b0b212 in PyRun_FileExFlags ()
from /usr/lib/libpython2.7.so.1.0
#50 0x00007ffff7b0c427 in PyRun_SimpleFileExFlags ()
from /usr/lib/libpython2.7.so.1.0
#51 0x00007ffff7b1d7ca in Py_Main () from /usr/lib/libpython2.7.so.1.0
#52 0x00007ffff746f040 in __libc_start_main () from /usr/lib/libc.so.6
#53 0x000000000040073e in _start ()
(gdb)
Thanks for any help!
Last edited by arnaudm (2014-10-15 08:08:40)

arnaudm wrote:
The problem indeed came from _imaging.so, I reinstalled the package python2-pillow and everything works fine now.
Thank you!
Hey man,
Sorry to be a pain but how did you figure out that it was 'python2-pillow' that needed reinstalling?
I cant see anywhere in the log that explicitly states a problem with python2-pillow?

[SOLVED] Cinnamon 2.4.6 cinnamon-settings themes segmentation fault

Hello,
I cannot get into the cinnamon-settings themes application. I debugged it with gdb:
Loading Themes module
[New Thread 0x7fffd233f700 (LWP 22746)]
[New Thread 0x7fffd3341700 (LWP 22695)]
[New Thread 0x7fffd4560700 (LWP 22692)]
[New Thread 0x7fffdf3d2700 (LWP 22687)]
[New Thread 0x7fffe9948700 (LWP 22680)]
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff33741a2 in ?? () from /usr/lib/libgtk-3.so.0
If I run it on console
~$ cinnamon-settings themes
Python module
Could not find bluetooth module; is the cinnamon-control-center package installed?
Loading Themes module
Segmentation fault (core dumped)
and from journalctl -x
-- Subject: Process 22999 (cinnamon-settin) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: man:core(5)
-- Process 22999 (cinnamon-settin) crashed and dumped core.
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
kernel: cinnamon-settin[22999]: segfault at 7f9ac9984045 ip 00007f9a87c0b1a2 sp 00007ffe3f759510 error 4 in libgtk-3.so.0.1400.9[7f9a87a57000+6ac000]
I've already reset all cinnamon settings and removed my used cinnamon theme numix and numix gtk theme. Also I created an softlink for default in ~/.themes, ~/.icons to Adwaita, because I've read that this is the gtk3 default Theme.
Has someone experienced the same problem?
this is my first post here, I hope someone can help me.
Tim
Last edited by quaddy (2015-04-08 11:42:34)

Hi,
update: after the last few updates the problem has vanished.. don't know why and what package was affected..
Tim

[SOLVED] Adobe Reader (acroread) Segmentation Fault (KDE)

Hello everyone!
I've been playing with arch quite a long time and I have a problem with the acroread package, which I installed from the AUR.
Adobe Reader will never start and this is the output I get:
$ acroread
dirname: missing operand
Try 'dirname --help' for more information.
Segmentation fault (core dumped)
I did run strace and the output I got (last few lines) is:
access("/etc/gtk-2.0/gtkrc.en_US", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/gtk-2.0/gtkrc.en", F_OK) = -1 ENOENT (No such file or directory)
lstat64("/home/errikos/.gtkrc-2.0", 0xfffffffffff5e7f4) = -1 ENOENT (No such file or directory)
access("/home/errikos/.gtkrc-2.0.en_US", F_OK) = -1 ENOENT (No such file or directory)
access("/home/errikos/.gtkrc-2.0.en", F_OK) = -1 ENOENT (No such file or directory)
lstat64("/home/errikos/.gtkrc-2.0-kde4", {st_mode=S_IFREG|0644, st_size=328, ...}) = 0
open("/home/errikos/.gtkrc-2.0-kde4", O_RDONLY|O_LARGEFILE) = 5
read(5, "# This file was written by KDE\n#"..., 4000) = 328
lstat64("/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc", {st_mode=S_IFREG|0644, st_size=6131, ...}) = 0
open("/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc", O_RDONLY|O_LARGEFILE) = 6
read(6, "# this file is part of the oxyge"..., 4000) = 4000
access("/home/errikos/.gtk-2.0/2.10.0/x86_64-unknown-linux-gnu/engines/liboxygen-gtk.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/errikos/.gtk-2.0/2.10.0/x86_64-unknown-linux-gnu/engines/liboxygen-gtk.la", F_OK) = -1 ENOENT (No such file or directory)
access("/home/errikos/.gtk-2.0/2.10.0/engines/liboxygen-gtk.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/errikos/.gtk-2.0/2.10.0/engines/liboxygen-gtk.la", F_OK) = -1 ENOENT (No such file or directory)
access("/home/errikos/.gtk-2.0/x86_64-unknown-linux-gnu/engines/liboxygen-gtk.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/errikos/.gtk-2.0/x86_64-unknown-linux-gnu/engines/liboxygen-gtk.la", F_OK) = -1 ENOENT (No such file or directory)
access("/home/errikos/.gtk-2.0/engines/liboxygen-gtk.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/errikos/.gtk-2.0/engines/liboxygen-gtk.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/2.10.0/x86_64-unknown-linux-gnu/engines/liboxygen-gtk.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/2.10.0/x86_64-unknown-linux-gnu/engines/liboxygen-gtk.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/2.10.0/engines/liboxygen-gtk.so", F_OK) = 0
stat64("/usr/lib32/gtk-2.0/2.10.0/engines/liboxygen-gtk.so", {st_mode=S_IFREG|0755, st_size=1309120, ...}) = 0
open("/usr/lib32/gtk-2.0/2.10.0/engines/liboxygen-gtk.so", O_RDONLY|O_CLOEXEC) = 7
read(7, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220-\4\0004\0\0\0"..., 512) = 512
fstat64(7, {st_mode=S_IFREG|0755, st_size=1309120, ...}) = 0
mmap2(NULL, 1314324, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 7, 0) = 0xf0f20000
mprotect(0xfffffffff105b000, 4096, PROT_NONE) = 0
mmap2(0xfffffffff105c000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 7, 0x13b) = 0xf105c000
close(7) = 0
mprotect(0xfffffffff105c000, 12288, PROT_READ) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
I am running Arch with KDE.
Should it find all those files it is not finding? Could they be part of the problem?
I did a Google search, but got nowhere until now.
Last edited by errikosd (2013-05-08 01:10:04)

Well, I found a workaround, for those who really need acroread and want it well integrated into the KDE environment.
The solution is to use another KDE look-alike theme, QtCurve, instead of the "problematic" oxygen-gtk for GTK2 applications.
What you have to do is install the following packages from the AUR:
gtk-engines
qtcurve-gtk2
qtcurve-kde
lib32-qtcurve-gtk2
and also lib32-gtk-engines if it isn't resolved as a dependency.
You will also need to install the kde-gtk-config package from the AUR.
Then go to: KDE System Settings > Application Appearance > GTK, select QtCurve as the GTK2 theme and enjoy acroread and other GTK2 applications (well not fully, but the QtCurve theme is OK) integrated into your KDE desktop!
PS1: QtCurve is not (yet?) available for GTK3, so I left oxygen-gtk there.
PS2: Status changed to solved.

[SOLVED] gdk-pixbuf-query-loaders Segmentation fault

When I update my packages via:
$ yaourt -Syu
I saw the error:
Segmentation fault (core dumped)
Then I found out the problem is about the binary file gdk-pixbuf-query-loaders.
When I run
gdk-pixbuf-query-loaders > /etc/gtk-2.0/gdk-pixbuf.loaders
I get the error
Segmentation fault (core dumped)
Is this a bug or did I do something wrong?
The file /usr/bin/gdk-pixbuf-query-loaders is owned by package gdk-pixbuf2 (2.31.3-1), I tried compiling the package from source myself, that didn't solve the issue.
I am using kde (new plasma).
Last edited by th0th (2015-05-10 11:36:42)

brebs wrote:
Sounds like Nvidia bug report.
Have you recompiled cairo with --enable-gl? That's a bad thing to do.
I was using cairo-ubuntu from AUR. Considering it might be the cause, I tried installing default cairo, it didn't solve the issue.

Xorg segmentation fault / nvidia proprietary blob

Hi!
I've been experiencing this issue with xorg crashing leaving the system completely unresponsive and with completely black screen. It appears to happen at random times and not consistently at all. It occurred for the first time several days ago. Unfortunately I'm not in a good position to track what may have caused this because I did pretty massive update 2-3 weeks ago. Since then I've been updating pretty regularly.
Here are some xorg logs.
It's pretty much full with:
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (mieqEnqueue+0x22b) [0x5615bb]
(EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fd27e33c000+0x580d) [0x7fd27e34180d]
(EE) 4: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 5: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 6: /usr/lib/libpthread.so.0 (0x7fd284986000+0xf870) [0x7fd284995870]
(EE) 7: /usr/lib/libc.so.6 (sigprocmask+0x10) [0x7fd283a1d6a0]
(EE) 8: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x81394) [0x7fd27ec28394]
(EE) 9: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x11c5d9) [0x7fd27ecc35d9]
(EE) 10: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x11ec7a) [0x7fd27ecc5c7a]
(EE) 11: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x124b0b) [0x7fd27eccbb0b]
(EE) 12: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x12628f) [0x7fd27eccd28f]
(EE) 13: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x1274c1) [0x7fd27ecce4c1]
(EE) 14: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x129920) [0x7fd27ecd0920]
(EE) 15: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x13d11f) [0x7fd27ece411f]
(EE) 16: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x1194f2) [0x7fd27ecc04f2]
(EE) 17: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x4d2432) [0x7fd27f079432]
(EE) 18: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x4d285e) [0x7fd27f07985e]
(EE) 19: /usr/bin/X (0x400000+0x58fa2) [0x458fa2]
(EE) 20: /usr/bin/X (FreeResource+0xa1) [0x459a31]
(EE) 21: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x4d263e) [0x7fd27f07963e]
(EE) 22: /usr/lib/xorg/modules/extensions/libglx.so (0x7fd281d58000+0x599834) [0x7fd2822f1834]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
(EE) [mi] EQ overflow continuing. 100 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fd27e33c000+0x580d) [0x7fd27e34180d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7fd284986000+0xf870) [0x7fd284995870]
(EE) 6: /usr/lib/libc.so.6 (sigprocmask+0x10) [0x7fd283a1d6a0]
(EE) 7: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x81394) [0x7fd27ec28394]
(EE) 8: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x11c5d9) [0x7fd27ecc35d9]
(EE) 9: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x11ec7a) [0x7fd27ecc5c7a]
(EE) 10: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x124b0b) [0x7fd27eccbb0b]
(EE) 11: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x12628f) [0x7fd27eccd28f]
(EE) 12: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x1274c1) [0x7fd27ecce4c1]
(EE) 13: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x129920) [0x7fd27ecd0920]
(EE) 14: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x13d11f) [0x7fd27ece411f]
(EE) 15: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x1194f2) [0x7fd27ecc04f2]
(EE) 16: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x4d2432) [0x7fd27f079432]
(EE) 17: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x4d285e) [0x7fd27f07985e]
(EE) 18: /usr/bin/X (0x400000+0x58fa2) [0x458fa2]
(EE) 19: /usr/bin/X (FreeResource+0xa1) [0x459a31]
(EE) 20: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x4d263e) [0x7fd27f07963e]
(EE) 21: /usr/lib/xorg/modules/extensions/libglx.so (0x7fd281d58000+0x599834) [0x7fd2822f1834]
(EE)
(EE) [mi] EQ overflow continuing. 1000 events have been dropped.
(EE) [mi] No further overflow reports will be reported until the clog is cleared.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fd27e33c000+0x580d) [0x7fd27e34180d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7fd284986000+0xf870) [0x7fd284995870]
(EE) 6: /usr/lib/libc.so.6 (sigprocmask+0x10) [0x7fd283a1d6a0]
(EE) 7: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x81394) [0x7fd27ec28394]
(EE) 8: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x11c5d9) [0x7fd27ecc35d9]
(EE) 9: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x11ece7) [0x7fd27ecc5ce7]
(EE) 10: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x126329) [0x7fd27eccd329]
(EE) 11: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x1274c1) [0x7fd27ecce4c1]
(EE) 12: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x12ae45) [0x7fd27ecd1e45]
(EE) 13: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x147f6e) [0x7fd27eceef6e]
(EE) 14: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x119164) [0x7fd27ecc0164]
(EE) 15: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x4d0f91) [0x7fd27f077f91]
(EE) 16: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x4db1a0) [0x7fd27f0821a0]
(EE) 17: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 18: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 19: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fd283a09bc5]
(EE) 20: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
[ 40751.796] [mi] Increasing EQ size to 1024 to prevent dropped events.
[ 40751.796] [mi] EQ processing has resumed after 3197 dropped events.
[ 40751.796] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
I'm not really sure whether this is separate issue or not but I thought I should include it here. I don't really know what this is about but I've seen "kwin effects restarted" KDE messages occurring at these times too. I'm not sure how related this may be but I'm seeing lots of artifacts on rendered pages when using chromium browser. Nothing of these used to happen before I went and updated the system. Everything was rock solid for me.
And here is the seg fault in the log:
[ 67406.515] (EE)
[ 67406.515] (EE) Backtrace:
[ 67406.515] (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
[ 67406.515] (EE) 1: /usr/bin/X (0x400000+0x1833e9) [0x5833e9]
[ 67406.515] (EE) 2: /usr/lib/libpthread.so.0 (0x7fd284986000+0xf870) [0x7fd284995870]
[ 67406.515] (EE) 3: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0xcd23c) [0x7fd27ec7423c]
[ 67406.515] (EE) 4: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0xdec9f) [0x7fd27ec85c9f]
[ 67406.515] (EE) 5: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x508770) [0x7fd27f0af770]
[ 67406.515] (EE) 6: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x5071f5) [0x7fd27f0ae1f5]
[ 67406.515] (EE) 7: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fd27eba7000+0x5089ad) [0x7fd27f0af9ad]
[ 67406.515] (EE) 8: /usr/bin/X (0x400000+0xcf3fb) [0x4cf3fb]
[ 67406.516] (EE) 9: /usr/bin/X (0x400000+0xd019d) [0x4d019d]
[ 67406.516] (EE) 10: /usr/bin/X (0x400000+0x373be) [0x4373be]
[ 67406.516] (EE) 11: /usr/bin/X (0x400000+0x2693a) [0x42693a]
[ 67406.516] (EE) 12: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fd283a09bc5]
[ 67406.516] (EE) 13: /usr/bin/X (0x400000+0x26c81) [0x426c81]
[ 67406.516] (EE)
[ 67406.516] (EE) Segmentation fault at address 0x7fd285661000
[ 67406.516] (EE)
Fatal server error:
[ 67406.516] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 67406.516] (EE)
[ 67406.516] (EE)
I'm not sure what is supposed to happen after xorg crashes and whether it's being restarted but everything related to xorg is unresponsive. The system otherwise is running fine but I haven't been able to find a solution to recover from this other than cold restart. I tried disconnecting and reconnecting the keyboard for instance and it's being registered(probably udev is responsible for this) but it's still "dead".
Is it nvidia's fault or something else may be going on? I know you can't really do much dealing with the binary blob. I haven't given nouveau a chance for a long time but I may try this in the future if it helps with something tracking this. I'm using nvidia 325.15-10 package from the official repos for now and the card is gtx 570 fermi. xorg is the latest one in the repos.
I'm not sure what driver version this package is based on(325.15 I guess). On the nvidia site the newest ones are 331.13 beta and 319.60. I can try them but I'm not even sure whether there are some patches needed to make them work with the newest kernels. At least I hope someone could provide more info on this because it seems interesting.
I'll gladly provide more info if needed. I just don't know what more could be useful.
Thanks!
Last edited by saty (2013-10-19 17:29:00)

saty,
Is this continuing to happen for you? I am experiencing the same issue with version 325. I downgraded from 331 because there were some major bugs in that version. Have you found any solution?

[SOLVED] Segmentation Fault with Clementine

When I open the preferences (Ctrl+P) of Clementine it crashes with a segmentation fault.
This is the backtrace:
18:53:58.858 WARN unknown libpng warning: iCCP: known incorrect sRGB profile
18:53:58.900 WARN unknown libpng warning: iCCP: known incorrect sRGB profile
[Thread 0x7fff9ffff700 (LWP 1566) exited]
Program received signal SIGSEGV, Segmentation fault.
0x00007fffec8b9ba1 in ?? () from /usr/lib/libfontconfig.so.1
(gdb) bt
#0 0x00007fffec8b9ba1 in ?? () from /usr/lib/libfontconfig.so.1
#1 0x00007fffec8ba03f in ?? () from /usr/lib/libfontconfig.so.1
#2 0x00007fffec8b9cd8 in ?? () from /usr/lib/libfontconfig.so.1
#3 0x00007fffec8ba554 in ?? () from /usr/lib/libfontconfig.so.1
#4 0x00007fffec8ba77d in FcConfigSubstituteWithPat ()
from /usr/lib/libfontconfig.so.1
#5 0x00007fffec8c85cc in FcFontRenderPrepare ()
from /usr/lib/libfontconfig.so.1
#6 0x00007ffff32d695e in QFontDatabase::load(QFontPrivate const*, int) ()
from /usr/lib/libQtGui.so.4
#7 0x00007ffff32b35e9 in QFontPrivate::engineForScript(int) const ()
from /usr/lib/libQtGui.so.4
#8 0x00007ffff32e9252 in QTextEngine::fontEngine(QScriptItem const&, QFixed*, QFixed*, QFixed*) const () from /usr/lib/libQtGui.so.4
#9 0x00007ffff32e9a03 in QTextEngine::shapeTextWithHarfbuzz(int) const ()
from /usr/lib/libQtGui.so.4
#10 0x00007ffff32eab02 in QTextEngine::shapeText(int) const ()
from /usr/lib/libQtGui.so.4
#11 0x00007ffff32eae25 in QTextEngine::shape(int) const ()
from /usr/lib/libQtGui.so.4
#12 0x00007ffff32f0a30 in QTextEngine::boundingBox(int, int) const ()
from /usr/lib/libQtGui.so.4
#13 0x00007ffff32c79f4 in QFontMetrics::boundingRect(QString const&) const ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/libQtGui.so.4
#14 0x00007ffff34673dd in ?? () from /usr/lib/libQtGui.so.4
#15 0x00007ffff3467534 in QComboBox::sizeHint() const ()
from /usr/lib/libQtGui.so.4
#16 0x00007ffff30ce65c in QWidgetItemV2::updateCacheIfNecessary() const ()
from /usr/lib/libQtGui.so.4
#17 0x00007ffff30ce96d in QWidgetItemV2::maximumSize() const ()
from /usr/lib/libQtGui.so.4
#18 0x00007ffff30b0b55 in ?? () from /usr/lib/libQtGui.so.4
#19 0x00007ffff30b11d6 in QBoxLayout::sizeHint() const ()
from /usr/lib/libQtGui.so.4
#20 0x00007ffff30caca4 in QLayout::totalSizeHint() const ()
from /usr/lib/libQtGui.so.4
#21 0x00007ffff30dec30 in QWidget::sizeHint() const ()
from /usr/lib/libQtGui.so.4
#22 0x00007ffff30ce65c in QWidgetItemV2::updateCacheIfNecessary() const ()
from /usr/lib/libQtGui.so.4
#23 0x00007ffff30ce96d in QWidgetItemV2::maximumSize() const ()
from /usr/lib/libQtGui.so.4
#24 0x00007ffff30b0b55 in ?? () from /usr/lib/libQtGui.so.4
#25 0x00007ffff30b1206 in QBoxLayout::minimumSize() const ()
from /usr/lib/libQtGui.so.4
#26 0x00007ffff30cac34 in QLayout::totalMinimumSize() const ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/libQtGui.so.4
#27 0x00007ffff30dec60 in QWidget::minimumSizeHint() const ()
from /usr/lib/libQtGui.so.4
#28 0x00007ffff30cc8c3 in qSmartMinSize(QWidget const*) ()
from /usr/lib/libQtGui.so.4
#29 0x00007ffff350e4b9 in ?? () from /usr/lib/libQtGui.so.4
#30 0x00007ffff350e897 in QScrollArea::setWidget(QWidget*) ()
from /usr/lib/libQtGui.so.4
#31 0x0000000000765b18 in SettingsDialog::AddPage(SettingsDialog::Page, SettingsPage*, QTreeWidgetItem*) ()
#32 0x0000000000765e67 in SettingsDialog::SettingsDialog(Application*, BackgroundStreams*, QWidget*) ()
#33 0x0000000000745360 in MainWindow::OpenSettingsDialog() ()
#34 0x000000000080c1ea in ?? ()
#35 0x00007ffff6cd7b48 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#36 0x00007ffff309cf82 in QAction::triggered(bool) ()
from /usr/lib/libQtGui.so.4
#37 0x00007ffff309e953 in QAction::activate(QAction::ActionEvent) ()
from /usr/lib/libQtGui.so.4
#38 0x00007ffff34c7d79 in ?? () from /usr/lib/libQtGui.so.4
#39 0x00007ffff34cc2a9 in ?? () from /usr/lib/libQtGui.so.4
#40 0x00007ffff30f262e in QWidget::event(QEvent*) ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/libQtGui.so.4
#41 0x00007ffff34d007b in QMenu::event(QEvent*) () from /usr/lib/libQtGui.so.4
#42 0x00007ffff30a30dc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQtGui.so.4
#43 0x00007ffff30a97dd in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/libQtGui.so.4
#44 0x00007ffff6cc3ebd in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQtCore.so.4
#45 0x00007ffff30a8f93 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
from /usr/lib/libQtGui.so.4
#46 0x00007ffff311aedc in ?? () from /usr/lib/libQtGui.so.4
#47 0x00007ffff311961c in QApplication::x11ProcessEvent(_XEvent*) ()
from /usr/lib/libQtGui.so.4
#48 0x00007ffff3140162 in ?? () from /usr/lib/libQtGui.so.4
#49 0x00007ffff41b3296 in g_main_context_dispatch ()
from /usr/lib/libglib-2.0.so.0
#50 0x00007ffff41b35e8 in ?? () from /usr/lib/libglib-2.0.so.0
#51 0x00007ffff41b368c in g_main_context_iteration ()
from /usr/lib/libglib-2.0.so.0
#52 0x00007ffff6cf0b25 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#53 0x00007ffff3140216 in ?? () from /usr/lib/libQtGui.so.4
---Type <return> to continue, or q <return> to quit---
#54 0x00007ffff6cc2b1f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#55 0x00007ffff6cc2e15 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#56 0x00007ffff6cc7f4b in QCoreApplication::exec() ()
from /usr/lib/libQtCore.so.4
#57 0x00000000005db094 in main ()
This happen every time. I searched on internet but I can't find similar issue.
Thanks.
Last edited by ryuzy (2014-02-06 11:30:13)

I tried installing Infinality-bundle+fonts and it fixed the problem.
So there was a problem with my fonts, I don't know why this happened but I'm happy to have solved.
Last edited by ryuzy (2014-02-06 11:30:59)

[SOLVED] flightgear crashes with segmentation fault

on startup:
creating 3D noise texture... Segmentation fault
what can I do?
Last edited by miro279 (2011-05-05 07:51:18)

the problem was the sound configuration. solved it by following this guide: http://wiki.flightgear.org/index.php/Li … F.asoundrc for alsa audio setup. before openal was assuming pulseaudio for some reason..

[kinda solved!]nvidia-settings segmentation fault

Similar Messages

Maybe you are looking for