Gnome Forum have told me that changing the appearance of gdm I run: sudo -u gdm dbus-launch gnome-appearance-properties but I get this error: (Gnome-properties-Appearance: 18 047): Gtk-WARNING **: can not open display:
I am currently running Suse 11.3. I continue to get the following error when logging into the KDE login manager with my user account
"Warning: Cannot open ConsoleKit session: Unable to open session. The name org.freedesktop.ConsoleKit was not provided by any .service files."
After acknowledging the error, it resets back to the login manager screen. If I login with root, I get the same message, but it continues on and logins into the session
I am new to Linux and wow, it did not take me long to run into a huge snag. I am running Suse Linux Enterprise 10 on a laptop and by some strange reason the computer froze from overheating and I was forced to shutdown improperly. Once I restarted it booted right to the command prompt when it usually instead boots to the default user. I managed to get gnome running using the "startx gnome" command. But when gnome loads, none of my normal extentions load like my wireless driver, the sound driver, etc. how to restore gnome to automatically load the default user on start up or fix any other damage I might have done? lol
For example, the gparted application menu item doesn't work; using it means that there is almost no filesystem support. The only way to get it to work is to open a terminal, run 'su -', and then open it from there.As another example, I tried creating a nautilus script to open files as root with a command like this:
Code:
for uri in $NAUTILUS_SCRIPT_SELECTED_URIS; do gnomesu -c "gnome-open '$uri'" done
When I try using it, it just fails. Typing out the command in the terminal gives this (tested on a text file):
Code:
No protocol specified (gedit:13672): Gtk-WARNING **: cannot open display: :0
I'm pretty sure the problem is that it's granting privileges, but not using the full root environment, or something along those lines.
When I become root and try to run gedit, I get the error:
No protocol specified
(gedit:219: Gtk-WARNING **: cannot open display: :0.0
This does not happen from my user profile....xhost + actually solves the issue....so I guess I just need to add the host root to the list of hosts allowed to access the x server...
I need to get gksu to run programs. The goal is to be logged in as user1 and run firefox or google-chrome with user2 's settings stored in their own home directory. I'm trying the following with no success:
Code: user1@hostname:~$ su user2 Password: user2@hostname:/home/user1$ google-chrome No protocol specified (google-chrome:17144): Gtk-WARNING **: cannot open display: :2.0
Code: user2@hostname:/home/user1$ firefox No protocol specified No protocol specified Error: cannot open display: :2.0
Code: user2@hostname:/home/user1$ gedit No protocol specified (gedit:17162): Gtk-WARNING **: cannot open display: :2.0
I was running Ubuntu 10.10 Maverick with no big problems till last 3 days ago.
The update manager checked some updates to install and after installing them, I had no graphic desktop any more. Only the command line.
I tried to recover it by starting the X again.
Code:
But did not worked
So I've tried to install the nVidia driver again. I looked at nVidia Linux drivers site for how to do it and Ubuntu documentation and when I tried to
Code:
I just could not use gedit. It cannot open display. I googled for three days but could not solve it. I found some similar answers here at LQ but none was similar to my situation or worked even when I tried.
I am still learning the ropes on Ubuntu server. I am trying to set up samba, but when I use the "gedit" command, I get this error: GTK-WARNING **: cannot open display I had installed the gedit command by using apt-get and aptitude, but still no luck. I am using virtualbox to test Ubuntu Server 9.10.
I've been searching for a permanent solution for some time now, but the threads containing the same error message never seem to be about the same issue.I want to:I'm not trying anything fancy, all I want to do is open a write-protected file with gedit as root, like so:
Code:
# sudo gedit /usr/bin/deadbeef
..but every time I try, no matter the file, I get this error message:
Code:
(gedit: [process #] ): Gtk-WARNING **: cannot open display
I already know: I can circumvent this by going:
Code:
# xhost +local:root # sudo su # export DISPLAY=:0.0
I'm trying to install Fedora10 on my new desktop. It has Windows 7 beta on it and Vista. It starts up fine and I select install. For some reason my wired usb keyboard will not respond unless I press the caps lock button while it loads the begging. (I don't know if another button will work, ive only used the caps button since i can see the light come on) once it loads i skip the disk check and anaconda runs, i get the warning (mini-wm:1462): Gtk-WARNING **: cannot open display: :1 .
Just installed F15, was everything fine, but then gnome got away, from terminal I have<gnome-session:1951): Warning can't start display message.Before that I put in config file one extra line to start tint2 like <sleep 3 && tint2.Not sure was it the reason?
I have one Linux PC installed with Suse 11.1. In this I have created three users to get access.
Users able access their login from Windows PC via some utilities. 1. Putty 2. Xming
Users able login using both. With Putty there is no GUI. But with Xmings XLaunch they are able to get similar session as Linux Host PC. At this point of time the host linux PC will become too slow in perfarmance.
How to retrict the users not to open similar session by enablin/disabling some setting in Linux PC?
I'm using wmctrl on an Ubuntu machine to manage windows from a script, that I run inside a (gnu) screen.
If I start the screen session from the local machine, wmctrl works fine, including if I completely close the terminal window and issue the wmctrl commands when connecting to the screen remotely via ssh. Conversely, if I connect remotely with ssh and start a screen, wmctrl doesn't work (returns "Cannot open display") even if I attach that screen session locally from the Ubuntu Terminal.
I guess there is some hidden screen parameter that doesn't get set in a way that allows accessing the display when it's launched remotely -- any ideas what it is and how to modify it from within a remote ssh-screen session so that that the script can access the windows?
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.
When I attempt to use Putty for xterm (to run DBCA for Oracle) I check x11 and put my IP Address in the Display field of putty. However, when I then try to execute ./dbca I receive the following:
Xlib: connection to "localhost:10.0" refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted Error: Can't open display: localhost:10.0
I notice the following when logging in to the server as well.
Last login: Fri Mar 19 13:51:19 2010 from 10.47.48.33 /usr/X11R6/bin/xauth: error in locking authority file /home/oracle/.Xauthority. These are the same steps I take successfully on all the servers. The above file exists on the servers I can initiate the GUI, but not on <server1>.
I have a Dell Dimension 4400, 8 yrs old. It is set up to boot to either Open Suse 11 or Windows. I turned on the machine this morning, it booted very slowly. My screen says, "GRUB loading stage 1.5" then it says "Error 21." I can not go beyond this screen. My machine is stuck here.
Installed Suse 11.2 from download CD. During the "answering questions" at the beginning of the process, selected Gnome as the desktop enviornment instead of the default KDE. The install process ended with no reported errors. After the final reboot at the process's end, the Gnome logon screen was displayed. After the user name/password were entered, a medium green screen was displayed, but the Gnome desktop was never displayed. The "animal" logo was not on the screen just the green screen and some "filagree" lines, probably part of the logo.
Waited a few minutes, mouse-clocked, pressed various keys and then tried ctrl-alt-del, but no response. Did a power off/on reboot, but the results were the same.
I then did a re-install. Took the KDE default for desktop. At install's end, the KDE desktop appeared and everything works just fine. During this second install, all choices were the same as for the first/Gnome install. Worked from written notes, and not from memory, so am sure that the change to KDE was the only difference.
Couldn't find any information on this anomally via forum and Google searches, hence this post.
This is my first time to use Suse, so could well have "missed something".
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..."
I am trying to make wine work for explorer. I followed some instructions on this link [URL] To follow this link, I am supposed to
cd ~/ies4linux/ie6 cp user.reg ~/user.reg.old gedit user.reg
1st and 2nd line went well 3rd line when I try to execute the command gedit user.reg (gedit:2573): Gtk-WARNING ** cannot open display I then /ies4linux/ie6# ls dosdevices(in blue) drive_c(in blue) system.reg(in white) userdef.reg(in green) user.reg
I recently upgraded from 10.10 to 11.04. I am able to log into and use LXDE desktop, but at the GUI login when I try to log into gnome-shell or Open Box, the log in fails. With Open Box I just get a black screen. When trying gnome, I get error "Failed to load session "gnome." When trying KDE Plasma I get music and then black screen on which I can control the mouse cursor.
Attached is my hardware info and xsession error file. I am using a Samsung SyncMaster 175v monitor. Version 10.10 worked well, with not issues, and was fully updated. I followed the upgrade directions, I believe.
Last week, i updated, my fedora. After that, during every boot up, I am getting a warning message like " Your hard disk may failing". It indicates that it is due to bad sectors. But I don't think so. There was a bug reported for a similar problem in fedora 11. I think it is not fixed yet. Hard disk is not having any problem during data access. Other OS including windows are not giving any warning message.
I have a system with 2 hard drives (Ubuntu 10.10 and Windows XP) on them. Grub allows me to select which system to boot to.
Ubuntu 10.10 has stopped working (not loading gnome graphical interface) for some reason.
I can boot to a command line (after many errors on screen). When I try the command "gnome-terminal" I get: "Failed to Parse Arguments: Cannot open display:"
I am having issues with putty going inactive during a session and the job failing. I do not want to run nohup but would llike a korn shell script to keep putty alive.
I am trying to Install Open Suse 11.3 (burned as an ISO DVD) along with existing Win 2008 R2 OS. When I try to boot from the DVD it just logs in to Win2008 though boot from CD/DVD is enabled in the boot sequence. So i tried to mount the ISO and run from Windows ! BUT I get an error before installation starts telling that Win2008 R2 is not supported in open suse installer! Is there anything I can do to overcome this and install/retain both OS? In fact I am even trying to c hange my win2008 from R2 to Enterprise to see if I can overcome the problem!
