Hot answers tagged gdm3
Answer in 2 words: The location of Xserver for GDM is hard-coded at compile time in configure.ac, line 1199 in X_SERVER variable and can't be configured. So, may be you could play with symlinks, linking /usr/bin/Xorg (or, less probably /usr/bin/X, see this) to your build of Xserver. Details: I have a Debian 7, too and here's my process tree: ...
Since @Bob says there's no runtime configuration option for this and I didn't want to rebuild gdm3 from patched source, I took the following approach. First, move the real X server aside: sudo dpkg-divert --local --rename --add /usr/bin/Xorg Then drop a new shell script in place of /usr/bin/Xorg: #!/bin/sh test -x /usr/local/bin/Xorg && exec ...
This appears to be issues with gnome-shell at various times across multiple distros (Red Hat for example). Your best bet would be to browse and file a bug in Debian BTS, including relevant output from strace, top, etc. Note that Debian 6 is still the Stable release and Debian 7 is Testing. Your help reporting and tracking the issue in BTS will help make the ...
You should write [Unit] Wants=NetworkManager.service After=NetworkManager.service to /etc/systemd/system/gdm.service.d/after_networkmanager.conf
I see from this link that it is in wheezy-backports and sid, but not jessie, as you say. The version in sid appears to be quite a bit higher than I remember a couple of weeks ago. Most packages move to jessie automatically after 5 days, I think, so you could either wait for a bit or install from sid. The old version could have been removed from Jessie due to ...
To gracefully shutdown your desktop, you may need to raise the TimeoutStopSec= for GDM, or whatever other display manager you are using.
It looks like you haven't changed your default runlevel and X Server is already running. You should have set it to 3, i.e.: id:3:initdefault: Although I don't think your script is going to work anyway. This part: cd /home/user1/Documents/ProgramFile ./ myProgram.sh is going to be executed only after X Server stopped.
when removing the package, some cleanup scripts are run. it seems like one of these fails (namely /etc/init.d/gdm3), rendering the un-installation incomplete. the proper way to fix this, is by checking why the script fails. try running /etc/init.d/gdm3 stop manually, and see why it fails. fix the underlying error, then try to uninstall again. an ugly ...
Probably, the ownership or permissions of your home directory has changed. To fix it, run as root chown -R USER:USER ~USER chmod u+rwx ~USER where you need to replace USER with your username.
Only top voted, non community-wiki answers of a minimum length are eligible