| Summary: | gnome-base/gnome-shell-3.8.3-r2 segfaults in libdbus-1.so.3.7.4 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | André Terpstra <andre> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
André Terpstra
2013-07-29 05:00:36 UTC
error message from dmesg:
[ 733.785407] gnome-shell[25834]: segfault at fffffffffffffff8 ip 00007f002a66ed25 sp 00007fff8ca63188 error 7 in libdbus-1.so.3.7.4[7f002a647000+3e000]
[ 734.514297] gnome-shell[25869]: segfault at fffffffffffffff8 ip 00007fae18b55d25 sp 00007fff272303f8 error 7 in libdbus-1.so.3.7.4[7fae18b2e000+3e000]
USE flag settings:
TitanGentoo2 ~ # emerge -pv1 dbus
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] sys-apps/dbus-1.6.12 USE="X systemd -debug -doc (-selinux) -static-libs {-test}" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
TitanGentoo2 ~ # emerge -pv1 gnome-shell
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] gnome-base/gnome-shell-3.8.3-r2 USE="bluetooth i18n networkmanager" PYTHON_TARGETS="python2_7 -python2_6" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
Unfortunately, the dmesg output is not enough to diagnose the crash. Please rebuild dbus, glib, gjs, gobject-introspection, and gnome-shell with debugging flags (-ggdb in CFLAGS and splitdebug in FEATURES, see http://www.gentoo.org/proj/en/qa/backtraces.xml) and obtain a detailed backtrace of the crash using app-admin/abrt. (To use abrt, you will need to first start abrtd.service and abrt-ccpp.service using systemctl, then make gnome-shell crash, and then obtain a backtrace using abrt-gui or abrt-cli.) (In reply to Alexandre Rostovtsev from comment #2) > ... Wow I were able to do that maybe I could solve the problem also? Upon reading my last post, I do not mean to be impolite of course or question the need for this information. It is just not easy to do and at least takes a lot of time. I'm beginning to feel maybe I should have postponed the system / gnome 3.8 migration... (In reply to André Terpstra from comment #3) You have informed us that a segmentation fault occurred somewhere in libdbus-1.so.3.7.4. I appreciate that this is ruining your day and preventing you from using your computer. But put yourself in our shoes: how do you think we could use the information you provided to fix the problem? libdbus contains hundreds of functions. We don't know in which one the crash happened. We don't know where in that function the crash happened. We don't know through what sequence of calls did gnome-shell end up calling that function with a (presumably) invalid pointer argument which made libdbus crash. And gnome-shell is written mostly in javascript; it won't be calling libdbus directly. The call sequence was probably something like gnome-shell → gjs → gobject-introspection → glib → libdbus, maybe with a dozen or two extra steps in the middle. Was it one of the intermediate steps that introduced the error? Maybe we should be looking for a bug in gjs, or in glib? At the moment, we don't know. Therefore, unless you or someone else who is suffering from the same crash (I have not experienced it on my machine) provides us with a debugging backtrace, we cannot even begin to look for a solution to the bug. Thank you for your explanation. I would probably have tried -maybe later- to assemble all necessary information, but the bug has vanished since today's world update :) Bug may be closed. It may very well be that your tried to log into gnome without restarting dbus or rebooting your system after switching the systemd use flag ? |
