After following a tutorial to install a pxe server for debian network install I can't log in my user session on gnome anymore
I got an error saying : /$home/.dmrc was ignored, can't save session and language the file must belong to the user and has persmission 644
I remember on my last session i got some icons on my home folder with a little lock icon on them i tried to remove them successfully using the command line but i still can't login. however i can successfully login with another user.
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
I updated my Jessie system today. Nothing crucial in the apt-get list as far as I can see, perhaps it's unrelated. Anyway, now I cannot open the terminal any longer. Launching `gnome-terminal` shows the app name in the menu bar, a spinning wheel, and then after a few seconds nothing. It doesn't appear in the list of processes, either. I can still log into the text shell via ctrl-alt-F1.
I also added `LC_TIME="en_GB.UTF-8"` to `/etc/environment` to get rid of the American date format. Could it be the cause? I just tried to launch the terminal from the JVM. I get this output:
Code: Select all(process:2629): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 8
I will delete the environment variable again and reboot, but I wonder if I can still have the British date format?
The following message comes up when I boot up: Logging in user Warning: Cannot open ConsoleKit session: Unable to open session: Launch helper exited with unknown return code 0. When I press OK, the system completes the start up and everything looks normal. But when I try to connect to internet, I get the following message:
KNetworkManager cannot start because the installation is misconfigured. System DBUS policy does not allow it to provide user settings; contact your system administrator or distribution. KNetworkManager will not start automatically in future. If I reboot the system, I logg in successfully. So far the problem has appeared approximately upon every second time I boot up. Rebooting the system seems to take care of it.
Don't know what info is of interest. I'm using
Opensuse 11.2 KDE 4.4.2 (Factory) After upgrade from 4.4.1 to 4.4.2 it worked fine for a week or so.
I do a clean install of slackware64 13.1 beta1 with KDE and switch default runlevel to 4 in /etc/inittab.
I try to login in kdm, I always come back to the login....
I try this with default runlevel 3 and an .xinitrc with "ck-launch-session startkde" .. works without problems, so I switch back to default runlevel 4, now i can login and only get the error "Cannot open ConsoleKit session: Unable to open session..."
Gnome sessions started hanging during login on a debian lenny box, and I can only think it's related to a recent package update as it was working fine before the last set. It affects all user accounts and hangs before the applications menu or any icons appear on the panels, but after after the top /bottom panels and the desktop background appears.
A few weeks ago I have installed Debian Jessie on KDE Desktop Version. I have a problem with the Display Manager Kdm, if i log out session the monitor turns off (DVI No Signal), the only option that I have it's forced shutdown or reboot via power button. I try another DM lightdm and this works fine. But i liked to know why log out session crash on Kdm.
Adding : TerminateServer=true at the end of /etc/kde4/kdm/kdmrc (Section :[X-:*-Core], solve the issue.
When I start a second X session using startx --:1, (as either my normal user or root), it goes straight into and LXDE session (Debian's default, I think). Once LXDE is started, there is no applications menu (only run and logout). How do I get it to show the full application menu that my regular user can see when I log in from GDM3 normally?
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 recently installed debian 8 stretch with xfce. Since the first time I boot, I have problem starting my X session: from lightdm I always attemped 2 or 3 times before it login (it returned me on lightdm prompt after a short splash screen).
Now it stopped working: the only way I can start xsession is running startx as root. When I try as user it starts the "splash" and return me to the tty with this error message:
Code: Select allServer terminated with error (1). Closing log file(EE)
This is my ~/.local/share/xorg/Xorg.0.log
Code: Select all[ 27.703] X.Org X Server 1.18.2 Release Date: 2016-03-11 [ 27.704] X Protocol Version 11, Revision 0 [ 27.704] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [ 27.704] Current Operating System: Linux debian 4.3.0-1-686-pae #1 SMP Debian 4.3.5-1 (2016-02-06) i686
[Code] .....
And this is my /etc/X11//Xsession
Code: Select all#!/bin/sh # # /etc/X11/Xsession # # global Xsession file -- used by display managers and xinit (startx) # $Id: Xsession 967 2005-12-27 07:20:55Z dnusinow $
[Code] ....
and this the .xsession-errors:
Code: Select allXsession: X session started for lucatastrophe at Tue Mar 29 10:21:09 CEST 2016 localuser:lucatastrophe being added to access control list openConnection: connect: No such file or directory cannot connect to brltty at :0 dbus-update-activation-environment: setting MAIL=/var/mail/lucatastrophe
[Code] ...
I try to reconfigure Xorg but the Xorg -configure command result in another segmentation fault.
I think that the problem could be related with old configuration (when I install this version of debian I maintain the /home partition and my previous OS was debian 7 with xfce).
What is the Failsafe Session Type that you can select from the KDM login screen supposed to do ? With Squeeze RC1, if I attempt to log in to a failsafe session, I am returned to the KDM login screen. This does not seem very failsafe to me but then I am not a desktop expert. With Lenny (5.0.7), I get a single console window, which, I guess, at least gives one a chance of fixing whatever may be stopping the normal KDE session from starting.
When I open an open office document from an NFS share it always opens as readonly. This was a problem I had on Arch linux and the fix was to change the locking options in the soffice script but I've tried that fix here and it doesn't work. I've seen a lot of discussions but they all go back to changing the locking options in soffice, has anyone got any alternative fixes or one that definitely works with locking?
When i logged into a gnome desktop i got this message: "The GNOME session manager was unable to read file:'/home/(desktop name)/ICEauthority'. If this file exists it must be readable by you for GNOME to work properly. try logging in with failsafe session and removing the file." What commands do i use for that? or do i need to do something else?
I'm currently building a ubuntu distro and would like to run a script on GNOME startup. I've read about doing it through the session manager but I have to do it through chroot so I'll need to set it up as a terminal command. Is there a way to add an item to the Session Manager from terminal or, even better, a directory where I can put the script so it will run on start?
I installed Open Office 4 on Debian 8 but when I run the program I get this error message.
root@localhost:/home/paul# openoffice4 No protocol specified No protocol specified /opt/openoffice4/program/soffice.bin X11 error: Can't open display: Set DISPLAY environment variable, use -display option or check permissions of your X-Server (See "man X" resp. "man xhost" for details)
Open Office works fine when I run the command "startx" in the Konsole but so far I haven't been able to configure it.
I have an app I've developed in Qt 5.3.1 that has display problems when using 3D accerelation in VirtualBox using Debian Cinnamon. It seems to happen with Cinnamon in any Linux distro I've tried. Once I boot into Debian Cinnamon, how can I stop my Cinnamon session (I think I must start with Ctrl+Alt+F1) , then get a straight X session to run my app without Cinnamon, with 3Dacceleration in VirtualBox?
I did an installation of amd64 testing with KDE 5 three days ago, and I noticed that my session is not restored upon login. I have this option checked at my kde system setting.
A quick search led me the next bug+patch: [URL] ....
(See also [URL] ....)
I did notice that files in ~/.config/session/ are created, but apparently not read upon login.
I tried to send a reply to the relevant bug 796062 but the email bounced back.
Having problem with latest testing and kde5 session restore?
Eye of Gnome aka EOG does not open some jpgs, here's what happens.
With some jpgs only, most work fine!!
If you open one of the problematic jpg files by clicking on the jpg in Nautilus, EOG never fully opens, the process starts but the application's window does not get displayed - I then kill the process with kill -9 PID.
The same jpg opens in other viewers, EG. FSpot and OO Draw on Linux, and IrfanView on Windows.
If you start EOG from the App menu or the command line and drag a problematic jpg to it, the jpg is also not displayed, nothing happens. BUT if you start EOG with a working jpg and, once that is being shown, drag a problematic jpg from Nautilus to EOG's window then now the problematic jpg is displayed.
PS. Anyone know if there is an Eye of GNOME 2.32 (latest stable) deb package which I can download or if I can install EOG 2.32 from some other repositories? Aptitude and Synaptic have only v. 2.30.
Whenever I try to open my home folder in GNOME, I get the following error as seen in the attachment. How can I fix this? I do have nautilus installed, so what could be the problem??
I have problem with VLC player. The problem, from the image below, appears whenever I open video file. I click Ok, and a everything is ok, until I jump to another time sequence, when sound and subtitles disappear.
Most of my gnome system administration tools are (suddenly) failing to open. The system is a new installation with both KDE and gnome, and the gnome system admin tools were working fine, but now they fail silently (nothing even in .xsession-errors). For instance, if I select Synaptic Package manager from the menu, I will get the gksu prompt to enter my administrative password, which I do. Then a notification will appear in the Taskbar "Granting Rights" and then after that nothing happens, it just fails silently. Note that this also happens if I enter 'gksu synaptic' or 'gksu /usr/sbin/synaptic' at the alt-F2 command line. Note that it doesn't seem to matter whether I check "Save Password for Session" or not. The same happens for time-admin, users-admin, etc. I have tried reinstalling gnome-system-tools, system-tools-backends, and gnome-keyring with no effect. I have googled extensively and have found a few other people with this same problem, but no solutions. Note also that kdesu does still work fine, and there doesn't seem to be any such problems in KDE in general. Only in gnome and with gksu.
P.S. Let me know if you need any more info (output from commands, files, etc).
Just installed Fedora 12 on a P4 IBM. Everything installed fine. Then, I rebooted, installed updates, and installed a few simple programs (emacs, ssh server). I rebooted since some kernel updates had been made. I can't login anymore. I get a brief message at GDM that says "unable to open session" after I enter my password. Root also doesn't work, but I figured out that root logins are disabled. I found something that recommended disabling selinux, so I reboot with selinux=0 parameter. That still didn't fix the problem, but did initiate selinux to re-label everything on the next boot.
My next thought was that maybe my password got corrupted, so I went into single usermode. I ran passwd justin, so I know that my password is correct. I still can't login via GDM or on a tty.
EDIT: I was also thinking I might need to uninstall something that I did; however, networking is disabled in single usermode, and if I init 3, then I get a login prompt that I can't open. Is there a way that I can enable root login? That might be a starting point to see if it's my user account or a general login problem.
