Search the Community

Hi, Following the steps at http://www.funtoo.org/GNOME_First_Steps There's a note which says: However, this doesn't seem to happen. I have had to do a separate rc-update add dbus default to get gdm to start. Looking at /etc/init.d/xdm there's a line: use consolekit dbus xfs I've managed to make things work by changing this to: need dbus use consolekit xfs But I have no idea whether this is correct. In short, I believe either the documentation needs to tell people to do rc-update add dbus default, or the init script needs to be changed. I don't know which, I'm not that clever! I'm happy to file a bug report, but I thought I'd check here first in case I'm missing something obvious. I usually do :-). Matt

Hi everybody, i need help with the next problem: when i start my funtoo system with Gnome 3 (i use openrc) everything works well except for GDM, it starts in off screen; is initially shown as expected only for a second and a second later it goes to off screen and i have to move the mouse or to hit any key to see anything again. So after moving the mouse GDM is back, but now is shown with the damn screenshield. After this i can remove the screen shield and login so i guess is not a big problem, but i'm tired of that situation every time i power on my computer. Thanks in advance! Note:-----> this issue is presented as well when the session is closed, so it happens in every session change

I desperately tried to find a solution myself, but not succeeded. When I am logged in Gnome session via GDM no local user privileges (such as reboot/shutdown, passwordless usb media mount, user session switching) are available to me. No power management options while in GDM login window either. Obviously, the reason is inactive state of consolekit sessions run through GDM: Session6: unix-user = '115' realname = 'added by portage for gdm' seat = 'Seat5' session-type = 'LoginWindow' active = FALSE x11-display = ':0' x11-display-device = '' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2015-03-30T00:56:13.786129Z' login-session-id = '4' idle-since-hint = '2015-03-30T00:56:15.796297Z' Session7: unix-user = '1000' realname = 'Nexie' seat = 'Seat6' session-type = '' active = FALSE x11-display = ':0' x11-display-device = '' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2015-03-30T00:56:47.125458Z' login-session-id = '5' When I start Gnome session manually with startx, everything works as expected and consolekit session is active: Session5: unix-user = '1000' realname = 'Nexie' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '/dev/tty1' remote-host-name = '' is-local = TRUE on-since = '2015-03-30T00:54:22.822545Z' login-session-id = '4' .xinitrc ? as recommended in wiki: exec ck-launch-session gnome-session Here are the installed packages which may be relevant: [ebuild R ] sys-apps/dbus-1.8.16 USE="X -debug -doc (-selinux) -static-libs -systemd {-test}" ABI_X86="32 (64) (-x32)" 0 kB [ebuild R ] sys-fs/eudev-1.5.3-r2 USE="gudev hwdb introspection keymap kmod modutils openrc rule-generator static-libs -doc (-selinux) {-test}" ABI_X86="32 (64) (-x32)" 0 kB [ebuild R ] x11-base/xorg-server-1.17.1-r1:0/1.17.1 USE="ipv6 kdrive nptl suid udev xorg -dmx -doc -glamor -minimal (-selinux) -static-libs -systemd -tslib -unwind -wayland -xephyr -xnest -xvfb" 0 kB [ebuild R ] sys-auth/polkit-0.112-r2 USE="gtk introspection nls pam -examples -jit -kde (-selinux) -systemd" 0 kB [ebuild R ] sys-auth/consolekit-0.4.6 USE="acl pam policykit -debug -doc (-selinux) -systemd-units {-test}" 0 kB [ebuild R ] gnome-base/gdm-3.14.1 USE="introspection ipv6 tcpd -accessibility -audit -branding -debug -fprint -plymouth (-selinux) -smartcard -systemd {-test} -wayland -xinerama" 0 kB rc-status shows that consolekit, dbus and openrc-settingsd are running as dependencies. Tried to add them explicitly to default runlevel, nothing changed. Could you give me any suggestion how to solve this or where else to look?

Hello All. First off, kudos for finding a way around systemd and GNOME. What a pain in the ass that migration would be. second off, I'm having some behavioral issues with GNOME. I think it might be on the video front, but also might be on the power front (power up, power down, log out, restart, etc). I'm putting them in the same topic because I believe that they might be related on some way. But.... I really don't know how to diagnose this to be quite honest. Lets start with the video side. Everything works great, for a while. If I use a program such as VLC, or Totem, there are times when the whole screen freezes, but the mouse is still able to move around. But I cannot drag any of the windows in the gnome environment, and the video's picture stays on the same frame, but the audio continues to play. Another problem I've had, and I believe it might be video related is when GNOME goes into screen shutdown or lock mode. there are times when it shuts the screen down, and when I move the mouse, the mouse works but the screen is black and I am stuck. Everything else on GNOME continues to work, but I can't get to my desktop. Sometimes the default "drag up" gnome lock screen appears, then it works as intended. Sometimes I have to wait for the screen to turn back off, and when it turns back on, the normal drag up screen will appear and work perfectly as well.... Other times I have to ALT+F1, and killall gnome-shell That seems to kill that. I ALT-F7 back on to the desktop, and since I have guake fired up, I can run gnome-shell again, and work with the intended GNOME environment. Other times, I'll get a partial black screen, and a partially loaded GNOME drag-up, lock screen. Almost as if it's in mid load. Then, my system freezes completly. I can move my mouse around, but I can't ALT+F1 out. On the power up/down, restart, logout, I have another set of issues. Sometimes, once the system has been running, say an hour or two, and I want to restart/power down my computer, it takes an awful long time to shut down GNOME and go into the reboot/power down state. I've noticed that it isn't a specific program running on GNOME as I shut down all programs that are currently open and on the system tab, and it still takes its time to shutdown. There are moments when it might take up to 3 - 5 minutes for GNOME to shut off and go into reboot/power down mode. Is there any way to diagnose this? I would appreciate any help on learning how to check what's going on here. Or has anyone had these issues in the past as well? I am really getting used to using GNOME, and would hate to have to switch desktops because of these problems. Thanks!