Summary: | dbus-daemon in session mode dies | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Zsolti <zsolt> |
Component: | [OLD] Core system | Assignee: | Project Gentopia <gentopia> |
Status: | RESOLVED CANTFIX | ||
Severity: | major | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge info |
Description
Zsolti
2006-10-05 06:27:07 UTC
Reopen if you can reproduce it after recompiling with C[XX]FLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer" Created attachment 98846 [details]
emerge info
still the same with -O2 -march=pentium3 -pipe -fomit-frame-pointer. system dbus-daemon runs fine though. maybe i have to rebuild everything with above cflags to be sure... Run it from console and attach a backtrace, we really can't guess. http://www.gentoo.org/proj/en/qa/backtraces.xml sorry but it's running fine on console and also if gnome is started within a shell. mean if i login into a shell and start gnome-session via .xinitrc. dbus-daemon --session is started prior when i login. btw. i digged into /etc/X11/Sessions/Gnome. the scripts in /etc/X11/xinit/xinitrc.d seems to be parsed and executed but simply launching dbus-daemon with dbus-launch doesn't work out of user context. the resulting command should be: dbus-launch gnome-session. at least with qingy, does dbus work with gdm this way? Qingy may not source those files, but last I checked, GDM does. (In reply to comment #6) > Qingy may not source those files, but last I checked, GDM does. > hm, maybe my english isn't so good. what i want to say is, that i think while starting gnome+x+whatever with qingy via the gnomesession script the scripts in X11/xinit/xinitrc.d/ *are sourced indeed*, also the script 30-dbus, but it is useless since only firering up dbus with dbus-launch doesn't work. theoretically someone has to do: dbus-launch gnome-session to pass the envs to gnome. but if it works with gdm, i mean if the dbus session daemon is started and stays up then it's probably a qingy only problem. im back to startx anyway... So quingy does the wrong thing but you no longer have a way to test? If you find any issues with dbus and have a way to test. Please reopen with new info. |