Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39244 - Inkscape 0.48.4-13 segfault when file browser dialog open
Attached to Project:
Arch Linux
Opened by Nourman Hajar (masnormen) - Sunday, 09 March 2014, 00:35 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 11 March 2014, 04:35 GMT
Opened by Nourman Hajar (masnormen) - Sunday, 09 March 2014, 00:35 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 11 March 2014, 04:35 GMT
|
DetailsDescription:
I have Inkscape 0.48.4-13 installed on my x64 Arch Linux. It ran fine on the previous installation. But after I reinstalled the system for some reason, now it produces a segfault whenever I'm trying to open a file browser dialog(s) (i.e. open, import file). I've googled the problem but I don't see if other users are experiencing this problem. It's just strange. However, it opens fine if I run it as a root user. I've also used previous versions of Inkscape using "downgrade". But nothing changes. GDB output: (not sure if I debug it right) (gdb) file inkscape Reading symbols from inkscape...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/inkscape 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". warning: File "/usr/lib/libstdc++.so.6.0.19-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.19-gdb.py line to your configuration file "/home/nourman/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/home/nourman/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" [New Thread 0x7fffe8caa700 (LWP 7837)] [New Thread 0x7fffe84a9700 (LWP 7838)] [New Thread 0x7fffe7ca8700 (LWP 7839)] [New Thread 0x7fffdc141700 (LWP 7840)] [New Thread 0x7fffdafce700 (LWP 7841)] [New Thread 0x7fffda4ab700 (LWP 7858)] [New Thread 0x7fffd9caa700 (LWP 7859)] [New Thread 0x7fffd94a9700 (LWP 7860)] [Thread 0x7fffd94a9700 (LWP 7860) exited] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000051 in ?? () Steps to reproduce: 1. Open Inkscape 2. Open a file browser dialog (i.e., open, import file) 3. Inkscape produces segfault. If you need some additional info, please ask for it and I will provide it for you. Thank you. |
This task depends upon
If I were you I would try cleaning up my inkscape and gtkmm configuration files.
Also try as another non-root user to confirm that your user profile is the issue.
We've established that the problem lies somewhere inside your profile files, it's virtually impossible for me to investigate and/or give advice on how to fix it since I have no access to those files... Good luck.