Bug 741876 – Program fails to start -- segmentation fault.

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 741876 - Program fails to start -- segmentation fault.


Summary:	Program fails to start -- segmentation fault.


Status:	RESOLVED FIXED

Product:	gnome-boxes
Classification:	Applications
Component:	general
Version:	3.14.x
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	3.22
Assigned To:	GNOME Boxes maintainer(s)
QA Contact:	GNOME Boxes maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2014-12-22 19:57 UTC by Matthew T. Hoare
Modified:	2016-03-31 13:22 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
output of `strace gnome-boxes` (1.27 MB, text/plain) 2014-12-22 19:57 UTC, Matthew T. Hoare	Details
backtrace for gnome-boxes (8.96 KB, text/x-log) 2014-12-22 22:31 UTC, Matthew T. Hoare	Details

Description Matthew T. Hoare 2014-12-22 19:57:30 UTC

Created attachment 293198 [details]
output of `strace gnome-boxes`

Running full GNOME 3.14.2 desktop under Arch Linux with kernel 3.17.6

Program segfaults immediately on launch.

Attached strace output.

Comment 1 Zeeshan Ali 2014-12-22 20:23:33 UTC

Thanks. Could you please provide a backtrace instead?

Comment 2 Matthew T. Hoare 2014-12-22 22:31:27 UTC

Created attachment 293209 [details]
backtrace for gnome-boxes

Comment 3 Zeeshan Ali 2014-12-23 00:43:41 UTC

(In reply to comment #2)
> Created an attachment (id=293209) [details]
> backtrace for gnome-boxes

Thanks so much but you seem to be missing debug symbols and backtrace isn't very useful w/o them. I don't know how it works in Arch but I'm guessing you need to install separate packages for each of the library you see the name of in the backtrace.

Comment 4 André Klapper 2014-12-23 13:23:29 UTC

Matthew: Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces and https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Zeeshan: Please use NEEDINFO status and stock answers.

Comment 5 Matthew T. Hoare 2014-12-24 12:49:49 UTC

Here is my new backtrace, I hope it's better this time.
Sorry for the delay, I've never done anything like this before.
Backtrace:

+ Trace 234449

Thread 4 (Thread 0x7fffdbfff700 (LWP 9073))

#0 syscall
at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
#1 g_cond_wait_until
at gthread-posix.c line 1437
#2 g_async_queue_pop_intern_unlocked
at gasyncqueue.c line 422
#3 g_async_queue_timeout_pop_unlocked
at gasyncqueue.c line 570
#4 g_thread_pool_wait_for_new_task
at gthreadpool.c line 262
#5 g_thread_pool_thread_proxy
at gthreadpool.c line 296
#6 g_thread_proxy
at gthread.c line 764
#7 start_thread
at pthread_create.c line 310
#8 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 109

Thread 3 (Thread 0x7fffe094d700 (LWP 9072))

#0 syscall
at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
#1 g_cond_wait_until
at gthread-posix.c line 1437
#2 g_async_queue_pop_intern_unlocked
at gasyncqueue.c line 422
#3 g_async_queue_timeout_pop_unlocked
at gasyncqueue.c line 570
#4 g_thread_pool_wait_for_new_task
at gthreadpool.c line 262
#5 g_thread_pool_thread_proxy
at gthreadpool.c line 296
#6 g_thread_proxy
at gthread.c line 764
#7 start_thread
at pthread_create.c line 310
#8 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 109

Comment 6 Matthew T. Hoare 2014-12-24 13:08:44 UTC

Managed to run valgrind as well, if that's any use to you.
See here:
https://bpaste.net/show/239f6702e532

Comment 7 Zeeshan Ali 2015-01-02 12:33:59 UTC

(In reply to comment #4)
> Matthew: Unfortunately, that stack trace is missing some elements that will
> help a lot to solve the problem, so it will be hard for the developers to fix
> that crash. Can you get us a stack trace with debugging symbols? Please see
> http://live.gnome.org/GettingTraces and
> https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces for more
> information on how to do so and reopen this bug or report a new one. Thanks in
> advance!
> 
> Zeeshan: Please use NEEDINFO status 

I usually do but I don't always remember to set status.

>and stock answers.

What are those?

Comment 8 Zeeshan Ali 2015-01-02 15:00:28 UTC

(In reply to comment #5)
> Here is my new backtrace, I hope it's better this time.
> Sorry for the delay, I've never done anything like this before.
> Backtrace:
> 

Some symbols still missing it seems. Also could you please provide also backtrace for the thread that gets the segfault? i-e `bt` command instead of `thread apply all bt`?

Comment 9 Lasse Schuirmann 2015-01-02 15:59:53 UTC

For the record, with a fully updated archlinux Boxes works for me. (3.14.2)

Comment 10 Zeeshan Ali 2015-02-23 19:21:55 UTC

Due to comment#9 and that reporter hasn't responded for a long time, I'm assuming issue is resolved.