0005616: GNOME-CONTROL-CENTER SIGSEGV - Kali Linux Bug Tracker

ID	Project	Category	View Status	Date Submitted	Last Update

0005616	Kali Linux	Kali Package Bug	public	2019-08-05 10:45	2019-12-12 08:05

Reporter	medaliyou	Assigned To	rhertzog
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	unable to reproduce
Product Version	2019.2

Summary	0005616: GNOME-CONTROL-CENTER SIGSEGV
Description	Linux may 4.19.0-kali5-amd64 0000001 (closed) SMP Debian 4.19.37-6kali1 (2019-07-22) x86_64 GNU/Linux root@may:~# apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.30.3-1 Candidate: 1:3.30.3-1 Version table: *** 1:3.30.3-1 990 990 http://http.kali.org/kali kali-rolling/main amd64 Packages 100 /var/lib/dpkg/status After Updates , GNOME-CONTROL-CENTER won't launch from GUI, so I laubched it from terminal , i got Segmentation Fault , i traced it with GDB it signals : __GI_libc_free (mem=0x1000000000) at malloc.c:3093 3093 malloc.c : No such file or directory So i used valgrind and the output is on these files below ! And this is the Stack Trace output
Attached Files	valgrind.out.err (338,199 bytes) strace-gnome-control-center.out.err (792,314 bytes)

rhertzog 2019-08-15 15:03 administrator ~0010889	I can't reproduce your issue here. The relevant part of valgrind gives some sort of stack trace: ==17133== Invalid free() / delete / delete[] / realloc() ==17133== at 0x48369AB: free (vg_replace_malloc.c:540) ==17133== by 0x49465E4: g_unix_mount_free (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.6000.6) ==17133== by 0x18DB87: ??? (in /usr/bin/gnome-control-center) ==17133== by 0x4A7E2F6: g_type_create_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6000.6) ==17133== by 0x4A60737: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6000.6) ==17133== by 0x4A625C3: g_object_new_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6000.6) ==17133== by 0x4A628F8: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6000.6) ==17133== by 0x1645C0: ??? (in /usr/bin/gnome-control-center) ==17133== by 0x4A5DB96: g_cclosure_marshal_VOID__STRINGv (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6000.6) ==17133== by 0x4A5B0C5: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6000.6) ==17133== by 0x4A7757C: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6000.6) ==17133== by 0x4A77B6E: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6000.6) ==17133== Address 0x100000000 is not stack'd, malloc'd or (recently) free'd It seems to be related with one of your mounts? Can you show us the output of "cat /etc/fstab" and "mount"? The failed address is 0x1000000000 which doesn't look like a valid address (a real address would look more random). So somehow the pointer got corrupted...

rhertzog 2019-12-12 08:05 administrator ~0011658	Closing due to lack of activity.

Date Modified	Username	Field	Change
2019-08-05 10:45	medaliyou	New Issue
2019-08-05 10:45	medaliyou	File Added: valgrind.out.err
2019-08-05 10:45	medaliyou	File Added: strace-gnome-control-center.out.err
2019-08-15 15:03	rhertzog	Assigned To	=> rhertzog
2019-08-15 15:03	rhertzog	Status	new => feedback
2019-08-15 15:03	rhertzog	Note Added: 0010889
2019-12-12 08:05	rhertzog	Status	feedback => closed
2019-12-12 08:05	rhertzog	Resolution	open => unable to reproduce
2019-12-12 08:05	rhertzog	Note Added: 0011658