1 Debian Gnome3 does not create ~/.config/monitors.xml
2 according to dconf editor
the location is
/etc/gnome-settings-daemon/xrandr/monitors.xml
and I tweaked, but no success.
[URL] .... method can be applied to GDM3 directory.
Since I have configured my x rortation only be xrandr command by shell init script, and never had configured by GUI setting, the monitors.xml was not created. When I done with GUI, the file is created as usual.
Using Debian testing and gdm3. I had set the login screen settings to automatically log me in however I want to change it back so that I have to login on startup however I cannot change the settings.In System > Administration > Login Screen the 'Click to make changes' highlights when I put the mouse pointer over it and it blinks when I click on it but that is all that happens so I cannot make any changes. Is there any way to fix this problem.
I'm trying to change my screen orientation from landscape to portrait mode. Here's my system information. (I don't have an auto-generated xorg.conf file.)
Here's the error message I get when I try to use randr:
$ xrandr --orientation right X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 149 (RANDR) Minor opcode of failed request: 2 (RRSetScreenConfig) Serial number of failed request: 14 Current serial number in output stream: 14
I just installed successfully Wheezy, but I can't change my Login Window Theme.I put the three files (.desktop .xml and.jpg) in/usr/share/gdm/autostart/LoginWindow/),I think that my mistake is here but I don't know where to put the .xml file and the .jpg files.And the I edited the file/etc/gdm3/greeter.gconf-defaults.The background is well-displayed but the "theme" is still the same.
I'm using jessie and since I upgraded from wheezy, gdm3 no longer shows a list of users in the logon screen. (I can still log on by selecting "other users").
I had previously had the same symptoms on wheezy, but had fixed it by changing "UID_MIN" to 500 in /etc/login.defs
Yesterday I done an upgrade with apt and since that time whenever I boot up I am presented with only a blank screen and an unresponsive cursor. I cannot switch console using Ctl+Alt+F*. The only thing I can do is Alt+SysRq+(R,E,I,S) which kills gdm3 and gets me back to the console.
* I can get into Xorg fine via the startx command * As a temporary fix, if I enable automatic login (via /etc/gdm3/daemon.conf) then gdm3 works.
But I can't get the normal authenticated login screen to work.
Output of journalctl for a failed attempt at running gdm3 with verbose debugging enabled:
Code: Select allOct 25 01:24:43 [hostname-removed] systemd[1]: Starting GNOME Display Manager... Oct 25 01:24:43 [hostname-removed] systemd[1]: Started GNOME Display Manager. Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Enabling debugging Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Changing user:group to Debian-gdm:Debian-gdm Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Successfully connected to D-Bus
[Code] ....
One other thing worth noting, before upgrading yesterday, I changed mirrors and accidentally pasted in "stable" into /etc/apt/sources.list. So basically I did an initial upgrade, realised my mistake, switched back to testing (which I was on before) and done another upgrade, which is when I noticed this problem.
To use most of my Kali applications, I want to be able to log into an X session as root. I know it is generally a bad idea and I don't want to do it as a rule, but it is useful for penetration testing (e.g. nmap and its GUI don't have most of the useful options when run as a regular user).
So how do I get GDM3 to allow me to log in as root? Currently, if I type in the user name "root" and log in, it just takes me back to GDM3. Could it work to add root to my user group (I really don't want to add all kinds of security holes)?
I installed jessie from a beta/rc shortly before release on my MacBook Pro 13 Retina and have kept it up to-date with apt-get dist-upgrade. Rcently gdm3/gnome-session have stopped working together. When I log in the screen goes black for a couple of seconds then goes back to the login screen. This happens with "System Default", "GNOME Classic" and "GNOME", but not with "GNOME on Wayland". However, Wayland seems to have some other issues. I haven't tried an alternative dm yet, eg lightdm, but the GNOME desktop does work when started with startx.
I've just used journalctl to get logs of what gdm3 and gnome-session were doing at the time. After booting I waited until the clock reached the next minute (19:55) so I'd know at which point in the logs I'd hit enter on my password. I'll post the gdm log separately in two chunks because the forum server doesn't seem to like text attachments and they're too long for one post.
Log from gnome-session: Code: Select all-- Logs begin at Thu 2015-05-07 19:54:06 CEST, end at Thu 2015-05-07 19:56:41 CEST. -- May 07 19:54:08 jeanette gnome-session[885]: gnome-session[885]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary
Running Jessie (with a low-pinned Debian-based repositories added to my sources.list (e.g. Kali, kxstudio) for those packages not currently available on Debian (like the Kali menu of security tools). Running on a HP 15-r189nd (Energy Star) laptop.
First question: How do I get GDM3 to add root as an option during login? I can type the root user name in. I don't need it to show the root user in the user list (would actually prefer to need to type it in), but I do want to be able to start an X session as root, since some of the Kali tools (e.g. nmap) needs root to function fully. If I type in root and try to start, it just takes me back to the GDM3 login.
Second question: When I want to select my Desktop Enviroment/Window Manager in GDM3, the list appears below the little gear so I can only see half of the list (xfce not visible to select). How do I change the GDM3 appearance/settings that will change the position of the DE list?
Third question: How do I get multiple X sessions running simultaneously? What I have been able to do, while logged in as myuser and running X on tty7, is to log into a tty[1-6] as root, and then startx -- :1, but this somehow skips my default desktop manager (GDM3) and boot straight into LXDE (with no menus!). In /etc/X11/default-diplay-manager I have: /usr/sbin/gdm3 ? How do I get startx -- :1 to start a desktop manager?
Fourth question: When I did the above startx -- :1 as root, it would start the X session in the same tty (e.g. tty2) where I was logged in as root running the startx command. It used to be (in older Linux versions) that startx -- :1 would start an X session on tty8 (and the default would be :0 on tty7). Is this the (new) way things are supposed to work? Or is there something wrong with my setup?
Question 5: Once I have started an LXDE session as root, how do I get it to show the full application menu that my regular user can see? Can I just copy the config files over? Which ones? Or is there a better way?
Question 6: Gnome used to start fine. Then I ran Gnome on Wayland once, and now regular Gnome (on X?) no longer runs, but give me a "Oops! Something went wrong" error and Alt-F4 just takes me back to GDM3. Classic Gnome and Gnome on Wayland still runs OK. Should I log a bug report?
I changed my user name with the following commands:usermod -l $newname $oldnamegroupmod -n $newname $oldname usermod -d /home/$newname -m $newnameAlso replaced every instance of /home/$oldname ith /home/$newname in ~/.config.Now gdm3 hangs with a black screen and wristwatch icon. (I can move the icon with the mouse.) This worked fine with gdm. I've looked for gdm3 files that have /home/$oldname in my home and in /etc and couldn't find anything significant.Anyone have any ideas or suggestions on how to fix this or where to look? For now, I've disabled gdm3, and I'm using startx. This is an installation in virtualbox. I just tried using ctrl-alt-F1, but it dropped me to console in the host system. (Nice rush of adrenaline came with that.)
The only errors in Xorg.0.log are there even with a successful startx. (EE) Failed to load module "xboxvideo" (module does not exist, 0)(EE) open /dev/fb0: No such file or directoryCouple more bits of relevant information - this was a live-build that I installed using refractainstaller. I also changed /etc/inittab to disable auto-login. Here are the changes, original lines commented out, new lines look like the inittab in my regular squeeze install, but I don't think this is the problem (see below.)
#1:2345:respawn:/bin/login -f user </dev/tty1 >/dev/tty1 2>&1 #2:23:respawn:/bin/login -f user </dev/tty2 >/dev/tty2 2>&1 #3:23:respawn:/bin/login -f user </dev/tty3 >/dev/tty3 2>&1
In the gmd3 greeter.conf-defaults file its tells me the themes are located /desktop/gnome/interface/gtk_theme, but wheres that directory actually at, like how I can find it?
Btw, I know I can go back to gdm, but I'd rather understand how to theme this, before. I might just.I'm using compiz, btw, if that makes any difference.
I recently upgrade from Lenny to Squeeze. My graphic card is nVidia Corporation G86 [GeForce 8400M GT] (rev a1). Using lenny latest drivers from nvidia worked fine. I installed nvidia drivers using Debian packages 195.36.31-6 and latest driver from nvidia site (260.19.36) and also other nvidia drivers. The problem is when I start gdm3 I saw nvidia logo but then when it loads gdm3 it shows gdm3 screen with lot of black pixels and other random pixels and then the screen freezes. And the only thing I can do is restart using [alt]+[sysrq]+b.
Some days ago (2015-09-28) I installed Debian testing amd64. Log in as a user failed and instead of the Gnome UI there was a sad face with the text: „Oh no! Something has gone wrong. A problem occurred and the system can't recover.
All extensions have been disabled as a precaution. Log out“.
The relevant output of journalctl (run as root) said:
etc/gdm3/Xsession[5379]: cannot connect to brltty at :0 - /etc/gdm3/Xsession[5379]: Service 'org.kde.kaccessibleapp' does not exist. - gnome-session[5379]: x-session-manager[5379]: WARNING: Application 'gnome-shell.desktop' killed by signal 5 - gnome-session[5379]: x-session-manager[5379]: WARNING: App 'gnome-shell.desktop' respawning too quickly - x-session-manager[5379]: Unrecoverable failure in required component gnome-shell.desktop
[Code] ...
After some investigating, I found three work-arounds.
(1) Use gdm3-autologin: In /etc/gdm3/daemon.conf, remove the double crosses and insert own user name AutomaticLoginEnable = true AutomaticLogin = <own user name> Disadvantage: Only one user can have access to the Gnome ui. If you log out, you enter the gdm3 greeter and … see above.
(2) Turn off gdm3 by running 'systemctl stop gdm3' as root, log in into a terminal as a user and run startx.
(3) Install package lightdm and make it to the standard display manager with 'dpkg-reconfigure lightdm'. Disadvantage: Energy manager and screensaver settings of the Gnome control center are ignored.
The easiest way, however, especially if there are several users, is logging in via the gdm3 greeter.
So, I have my trusty ol' Aspire One ZG5 running with Natty. I like changing the screen orientation (sideways) to read comic books and books. I've learned how by this page: URL...So, I have no trouble changing my screen orientation with a quick key-combo, but I still need help,I'm trying to figure out how to change the "orientation" of the arrow keys along with the screen. So when i have the screen oriented to the left, the left key works as the up, the up down as the right, etc.
I searched on the internet and notice that the setup gui for changing gnome login screen is no longer available (e.g. gdmsetup does not come up with a theme that can change login screen theme.)What is the right way or where there may contain such information? I google but most of returned are prior 2.30.2, which is the version currently I am using.
How do you enable a login screen? When I turn on my computer I only get command line. When I log into root I can start my KDE desktop using startx. But if I log into any other user I get the following errorX: usser not authorized to run the X server, aborting.giving up.xinit: No such file or directory (errno 2): unable to connect to X serverxinit: No such process (errno 3): Server error.
I recently installed Debian 8 with the Xfce Desktop Environment, which uses the Lightdm gtk greeter as its login manager. My login screen at the moment looks something like this: [URL] ..... In particular, I still have the "grey person" as the default user avatar.
I have been unsuccessfully attempting to change my personal login avatar, following the advice on the Arch Linux wiki: [URL] .... I began by naming my desired avatar .face and saving it in my home directory. That didn't work, but I was not discouraged because the wiki mentioned that there were issues with the ".icon method". So I then installed accountservice, created a directory for my user, and saved my desired avatar as a 96x96 PNG named username.png in the appropriate directory (making sure that it had the necessary permissions, of course). That didn't work either...
I'm on Debian testing Gnome 3.18 and I searched, tried, searched and tried... no way! numlock will always stays off whenever I reboot and reach login screen.
.... I checked bios settings > numlock is on - installed numlockx - added those lines to /etc/gdm3/Init/Default (if [ -x /usr/bin/numlockx ]; then /usr/bin/numlockx on fi) - checked dconf gnome /settings-daemon /peripherals /keyboard remember-numlock-state: true ....
After applying upgrades to debian 8.2 on a lenovo yoga3 notebook and a reboot I am not able to login into my GNOME desktop. The login screen stays black. If I press the power button to suspend I can see the login screen with default background for ~1 second before it turns black again. What can I do to fix this issue? Is there a way to login via terminal and do a rollback? Can I use my home folder an personal settings if i reinstall debian and keep the /home partition?
I'm running Squeeze with Gnome & GDM3. After 1 h my laptop automatically suspends while in the login screen (GDM3; so no user login). I want to prevent that, since this machine also has a server role. how this can be prevented?
I'm running an LMDE install, but with the Sid repositories.Everything has been fine until yesterday's updates, after which I can't boot normally. The boot hangs at the login screen, and nothing works - not the mouse, the keyboard, the touchpad, nothing, and it requires holding the power switch to get out. I can boot to a root recovery console, but networking doesn't work at all there. I can run startx there and get an X desktop as root, and networking still doesn't work. No wireless, no ethernet, no nothing. From the recovery console I can run shutdown, and when prompted for a password, can enter Ctrl-D, which immediately drops me back to X, to the normal login screen, which now works normally, and I get a normal X session in which everything works. This is the same for all installed kernels, including 3 versions of the Liquorix kernel and the standard Squeeze kernel. It would appear to be something in my settings in /home, but I can't find anything that looks suspicious. I ran smxi again after booting through the root console, without any improvement.
How can i change that login window's font rendering, i mean that screen which you can select user and type password. Is anybody have the experience for tweaking gnome login font or background image?
Running Compiz as a standalone WM.Managed to get Slim working, will post how later, but have no sound. If I boot using gdm3 the sound works. Obviously gdm3 loads something Slim doesn't, but can't workout what!Tried adding /usr/bin/pulseaudio --start --log-target=syslog & to my script - no dice, still no sound
My debian squeeze + testing + unstable came with gdm3. After setting in /etc/gdm3/daemon.conf: AutomaticLoginEnable=true AutomaticLogin=myname I don't have to type in my username and password on startup. But after a few inactive minutes the screen blanks out, and I have to type in my password now in order to continue. For me hitting any key would be enough. How can I change that?
In Jessie the lightdm login screen does not bring up a lightdm-gtk-greeter dialog box but what seems to be some other one. I can increase the font size by modifying the /etc/lightdm/lightdm-gtk-greeter.conf file, but the login dialog box will not grow to accommodate the larger font (old eyes). The lightdm-gtk-greeter dialog box in Wheezy was a rectangle with a glyph of a console centered in its upper portion, and all the files I have examined indicate that this should be the same in Jessie, but instead the login screen in Jessie displays a narrower rectangle with a head-and-shoulder stylization off to the left.
In playing around trying to get Debian/X installed/working on my PowerBook (machine details in signature), I at some point installed gdm. I then decided to try installing Gnome desktop from the list of tasks in aptitude. I didn't install absolutely everything in the list. (I skipped the accessibility stuff for the most part, for example.) But I did try installing gdm3. Since this conflicts with gdm, this meant uninstalling gdm. No problem. The install etc. seemed to go OK and Debian's configuration tool let me choose between gdm3 and xdm as the display manager. I chose gdm3.
Problem: gdm3 will not start on boot (and I'm not sure whether or how to start it later without leaving root logged in). I found that the init scripts for gdm were still installed in /etc/rc2.d/ etc. but nothing for gdm3. There was a script at /usr/sbin/gdm which appears to want to (1) delete itself; and (2) start gdm3. But the init script /etc/init.d/gdm contains a check for gdm being the default display manager. However, it isn't. The file it checks contained /usr/sbin/gdm3. So I tried using the update-rc.d and also insserv commands to disable gdm and to install the scripts for gdm3. I could disable the commands for gdm fine but not install links for /etc/init.d/gdm3. This script seemed to want console-screen which I didn't have but managed to install by some guesswork. I then got the init script for this installed for /etc/rcS.d but still couldn't get anything installed for init for gdm3. I also tried creating the links manually but this made no difference on boot. I also tried purging gdm rather than just uninstalling it and reinstalling gdm3. No go.
Eventually, I gave up and removed and purged gdm3 and reinstalled gdm and now the display manager starts as it should on boot.
I'm not sure what I did wrong and would like to know. I don't know that I'm bothered one way or another about gdm3 vs. gdm but I'd like to understand what is going on in case something similar happens with something I *do* care about. (I don't know what the advantages of gdm3 are so maybe I should care...)
I'm using Squeeze and my sources list includes stable contrib and non-free (added the last two so I can get firmware needed for wireless).
I like my monitor to turn off when I'm not at the computer for more than 10 or 20 minutes or so and it wasn't doing that. I haven't used Linux for years and was used to xorg.conf/x11.conf and xinitrc and such.
So I rediscovered xset is responsible for DPMS settings. xset -q revealed DPMS was off. So I used it and put it in ~/.xinitrc. It didn't work. After some canoodling around I found out about xfce's Session and Startup gui thing. I was using that to run ~/.xinitrc.
When I got to my desktop and did a check with xfce4-terminal by running xset -q it would show DPMS enabled but the values were wrong. 600, 0, 900 to be exact.
After some searching I came across the information that xscreensaver will override DPMS settings as it manages DPMS too. So after more canoodling I found out about xfce's Screensaver preferences dialogue and used that to set my values. The values would immediately be set but the problem is that they are not persistent. If I reboot or log out the values will revert to 600, 0, 900. They will only reset to what I want them to be by running xfce's Screensaver preferences dialogue manually.
man gdm3, info gdm3, grep -r DPMS in /etc/gdm3, grep -r dpms in /etc/gdm3 reveal nothing related to DPMS. I've done some searching and nothing useful.
there is an /etc/X11/app-defaults/XScreenSaver-nogl which has some DPMS settings but the times are too large (2 hours); the only thing that matches is the off setting which is specified there.
xscreensaver -no-splash is present in the output of ps so it is xscreensaver and not gnome-screensaver.
The weird thing is that I re-enabled my ~/.xinitrc in xfce's Session and Startup gui thing and it is being run, but the numbers are getting set wrong after it is run. (I put an echo command after xset dpms 900 1200 1500, and the file is appearing in ~)
Where does 600, 0, 900 come from? Mystified on how to proceed from here. I don't remember enough on how to see what's doing what. Is there some sys thing or proc thing I can monitor to find out what's setting these values?
Short version: my xset dpms values are getting reset to 600, 0, 900 every time I logout or reboot. They revert to 600, 0, 900 every time I get to my desktop. I use gdm3 and xfce. Where are these coming from?
