Bug#932109: libglib2.0-0: Caja crash due buggy libglib2.0-0 in Buster
Close 932109
Bug#932109: libglib2.0-0: Caja crash due buggy libglib2.0-0 in Buster
Ping.
Bug#932109: libglib2.0-0: Caja crash due buggy libglib2.0-0 in Buster
Sorry, I had been quite busy for several days. On Wed, 17 Jul 2019 22:59:57 +0100 Simon McVittie wrote: Control: reassign -1 caja 1.20.3-1 On Thu, 18 Jul 2019 at 04:28:00 +0700, Dio Putra wrote: >Stack trace of thread > 1413: >#0 0x7fa05c053673 > g_type_check_instance_cast (libgobject-2.0.so.0) >#1 0x562d365df197 > caja_extensions_get_for_type (caja) >#2 0x562d365f47f1 > caja_file_invalidate_extension_info_internal (caja) This looks like it indicates a bug in caja: caja_extensions_get_for_type() calls g_type_check_instance_cast() and passes an invalid object pointer to it. Looking at the code of caja_extensions_get_for_type(), that would probably mean that one of the Extension structs in the caja_extensions linked list has ext->state set to a true value and ext->module pointing to something that is not a valid object, probably freed memory. My guess would be a reference-counting bug somewhere. (The G_OBJECT() macro actually calls g_type_check_instance_cast().) If you don't know for sure that a crash is caused by a library, it's usually best to report it as a bug in the application/executable that crashed, and let the maintainer of the application reassign it to the library if they find evidence that it's a library bug. That way, the bug report has all the details of the application/executable and all the libraries it depends on. I'm assuming that you have the version of caja from buster. Yeah, it's caja from buster version. Please tell the caja maintainers (via the bug address) whether there is a way to reproduce this bug, like a particular sequence of actions that makes caja crash: if there is, that will make it much more likely that someone can find a solution. Last time I remember that I had to editing the user-dirs.dirs file with: $ sed -i 's/Destop/Desktop/g' $HOME/.config/user-dirs.dirs Not sure how to reproduce this bug, it's quite hard for me due randomness of using caja. It would also be useful to check the systemd journal for any log messages that show warnings or errors from caja. If there aren't any, running caja from a terminal might result in you seeing some warning messages from caja before the crash - if so, those messages would be very useful information. Running caja from terminal doesn't show any debug message. Like: $ caja $ There's no any warning/error. smcv
Bug#932109: libglib2.0-0: Caja crash due buggy libglib2.0-0 in Buster
Control: reassign -1 caja 1.20.3-1 On Thu, 18 Jul 2019 at 04:28:00 +0700, Dio Putra wrote: >Stack trace of thread > 1413: >#0 0x7fa05c053673 > g_type_check_instance_cast (libgobject-2.0.so.0) >#1 0x562d365df197 > caja_extensions_get_for_type (caja) >#2 0x562d365f47f1 > caja_file_invalidate_extension_info_internal (caja) This looks like it indicates a bug in caja: caja_extensions_get_for_type() calls g_type_check_instance_cast() and passes an invalid object pointer to it. Looking at the code of caja_extensions_get_for_type(), that would probably mean that one of the Extension structs in the caja_extensions linked list has ext->state set to a true value and ext->module pointing to something that is not a valid object, probably freed memory. My guess would be a reference-counting bug somewhere. (The G_OBJECT() macro actually calls g_type_check_instance_cast().) If you don't know for sure that a crash is caused by a library, it's usually best to report it as a bug in the application/executable that crashed, and let the maintainer of the application reassign it to the library if they find evidence that it's a library bug. That way, the bug report has all the details of the application/executable and all the libraries it depends on. I'm assuming that you have the version of caja from buster. Please tell the caja maintainers (via the bug address) whether there is a way to reproduce this bug, like a particular sequence of actions that makes caja crash: if there is, that will make it much more likely that someone can find a solution. It would also be useful to check the systemd journal for any log messages that show warnings or errors from caja. If there aren't any, running caja from a terminal might result in you seeing some warning messages from caja before the crash - if so, those messages would be very useful information. smcv
Bug#932109: libglib2.0-0: Caja crash due buggy libglib2.0-0 in Buster
Sadly no, I just really tired because my Debian Buster was reinstalled today. Pada tanggal Rab, 17 Jul 2019 19.28, Bernhard Übelacker < [email protected]> menulis: > Hello Dio Putra, > are there still files in /var/lib/systemd/coredump/ ? > If there are any, maybe you could copy it then to a > safe place where they do not get automatically deleted. > > Kind regards, > Bernhard > >
Bug#932109: libglib2.0-0: Caja crash due buggy libglib2.0-0 in Buster
Hello Dio Putra, are there still files in /var/lib/systemd/coredump/ ? If there are any, maybe you could copy it then to a safe place where they do not get automatically deleted. Kind regards, Bernhard
Bug#932109: libglib2.0-0: Caja crash due buggy libglib2.0-0 in Buster
systemd-coredump was installed on my system. I'll let you know when caja is crashed again with same segfault. Pada tanggal Rab, 17 Jul 2019 16.03, Bernhard Übelacker < [email protected]> menulis: > Hello Dio Putra, > the information might not yet be enough for > the maintainers to help. > > Maybe you could install the package systemd-coredump. > In the output of 'journalctl --no-pager' should then > the segfaults appear too, followed by a backtrace > that you could forward to this bug. > > Kind regards, > Bernhard >
Bug#932109: libglib2.0-0: Caja crash due buggy libglib2.0-0 in Buster
Hello Dio Putra, the information might not yet be enough for the maintainers to help. Maybe you could install the package systemd-coredump. In the output of 'journalctl --no-pager' should then the segfaults appear too, followed by a backtrace that you could forward to this bug. Kind regards, Bernhard
Bug#932109: libglib2.0-0: Caja crash due buggy libglib2.0-0 in Buster
Package: libglib2.0-0 Version: 2.58.3-2 Severity: important Dear Maintainer, Sometime when using Caja, it's closed unexpectedly due buggy libglib2.0-0. Look at this log: Jul 15 11:48:12 ASMDT-TN14 kernel: caja[1029]: segfault at 1 ip 7fc1eae6565c sp 7ffc5eb8ef00 error 4 in libgobject-2.0.so.0.5800.3[7fc1eae3b000+32000] Jul 15 11:48:13 ASMDT-TN14 kernel: Code: 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 41 54 55 53 48 89 fb 48 85 ff 0f 84 a4 00 00 00 48 8b 07 48 85 c0 0f 84 a4 00 00 00 <48> 8b 28 48 89 ea 48 81 fd fc 03 00 00 0f 86 f1 00 00 00 48 83 e2 Jul 15 11:48:14 ASMDT-TN14 mate-session[943]: WARNING: Child process 1029 was already dead. Jul 15 14:10:08 ASMDT-TN14 kernel: caja[1469]: segfault at 1 ip 7f8627c2665c sp 7ffec80606b0 error 4 in libgobject-2.0.so.0.5800.3[7f8627bfc000+32000] Jul 15 14:10:08 ASMDT-TN14 kernel: Code: 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 41 54 55 53 48 89 fb 48 85 ff 0f 84 a4 00 00 00 48 8b 07 48 85 c0 0f 84 a4 00 00 00 <48> 8b 28 48 89 ea 48 81 fd fc 03 00 00 0f 86 f1 00 00 00 48 83 e2 Jul 15 14:26:42 ASMDT-TN14 kernel: caja[1691]: segfault at 8ff52 ip 7f9dd15a165c sp 7ffca2857310 error 4 in libgobject-2.0.so.0.5800.3[7f9dd1577000+32000] Jul 15 14:26:43 ASMDT-TN14 kernel: Code: 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 41 54 55 53 48 89 fb 48 85 ff 0f 84 a4 00 00 00 48 8b 07 48 85 c0 0f 84 a4 00 00 00 <48> 8b 28 48 89 ea 48 81 fd fc 03 00 00 0f 86 f1 00 00 00 48 83 e2 -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=id_ID.UTF-8, LC_CTYPE=id_ID.UTF-8 (charmap=UTF-8), LANGUAGE=id_ID.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libglib2.0-0 depends on: ii libc62.28-10 ii libffi6 3.2.1-9 ii libmount12.33.1-0.1 ii libpcre3 2:8.39-12 ii libselinux1 2.8-1+b1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages libglib2.0-0 recommends: ii libglib2.0-data 2.58.3-2 ii shared-mime-info 1.10-1 ii xdg-user-dirs 0.17-2 libglib2.0-0 suggests no packages. -- no debconf information
