Adding Firefox add-ons to Guest Session?I wanted to include Add-on to Ubuntu Guest Session Firefox.Is there a proper or better way to do this? Procedure I used was as follows
1. Login to Ubuntu to a user account with sudo privileges (later sudoer account).
1. Switch to Guest Session
2. Install relevant Add-ons
3. Check what the home folder of the Guest Session is. It should be something like /tmp/guest-home.xxxxxx where xxxxxx = six random characters.
4. Switch to sudoer account
5. Open terminal and type
I tested this with Flashblock and it seemed to work. I also admit that since I did the thing for the first time it was not that straight forward for me, but above procedure should work. With quick Googling I was unable to find straight forward method. There is a way to install Add-ons to all users from command line using -install-global-extension but this was not what I wanted to do. I wanted the Add-on just for the temporary guest account.
I installed goblin by run GoblinUI.ymp and logged out. After I logged out, I chose meego as session type and tried to login again. I entered correct password, but when I press enter after type password , display change to black and got some message and backed to login session again.
On the other hand, I succeed in running MeeGo Live CD(1.0.1 build 1.4). I wrote MeeGo Live CD image on USB Flash Driver by using Win32 Disk Imager, and boot that one successfully, although it has some flaw.
Network Settings Window is stuck in workspace and can't move or close, so it cover other appication's window. Internet on toolbar is broken, so I have to run FireFox in application toolbar to use internet.
I'm using Netbook based on Atom CPU and GMA.OpenSUSE installed in my netbook is installed by KDE Live CD image.
Should I Use Gnome to use Goblin, because MeeGo is using Gnome? Or.... what is problem make Goblin doesn't work?
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 just reinstalled my OpenSuse 11.3 with the GNOME desktop. As soon as I was done installing and I was on a fresh desktop, I installed the Yast updates that were available, rebooted, and now I can't login to any of my User accounts. Whenever I try to login, it tells me that it is "Unable to Open Session".o any of you know how I can fix this without having to reinstall all over again
I've always wondered whether my process kills when I am in the process of doing something during my ssh session. For instance, I ssh from my local box to dev-formbox and did an scp transfer to another remote host. All of the sudden, I lost ssh connectivity on my local box due to network issue. Will the scp process (or any of my process that I am currently doing) kill also once I loose the ssh session?
I started a process in a PuTTY session that I want to survive after I've disconnected. I issued a `disown` on the process (forgot to add the -h option). I've attached a small summary of the commands issued within the PuTTY session as well as an excerpt from the pstree (essentially switched user contexts twice, issued command, suspended program, disown'ed, resumed program
Code: > su - > ... > su -l <useraccount> > ./myprogram
I am using putty to interact with Linux server. I have started a process using putty. The process is running and will take 5-6 hours. I want that process to keep running after I close the putty session. How can I keep that process alive after closing the putty session? I do not want to keep the computer ON all the time. Is there any way to do this?.
I am running Montavista distribution. I have an Apache server running in my machine. Now I want to know how many clients are connected to the Apache server and what are the process ids for those sessions. What is the command to do that?
I'm a new openSUSE user. Thought of giving some other distros a try, so I started with openSUSE.
I installed the Xfce packages and when I went to go install a panel plugin, it said that it needed to install some other stuff, including an update of xfce4-session to xfdesktop. After I did this, I could no longer see 'Xfce session' in the "Sessions" part of the log-in menu when I tried to log-in again.
I have upgraded suse from 11.3 to 11.4 as described here (command line) SDB:System upgrade - openSUSE.
When I rebooted computer I get message: "Loggining in myname Warning: Cannot open ConsoleKit session: Unable to open session: Lunch helper exited with unknown return code 127" The same problem is in safe mode. Mouse and keyboard are "death".
I need some help install and configure my vnc session at my Opensuse.
Right now I have installed nx client which works fine and is listening on port 5901.
I also want vnc to use when I want to check exactly what is going on my work's computer (when I go home)
I am reading the tutorial here:
And I would like to ask you the following
For VNC client connection remember to open ports 5901-> in the firewall. (1 port/Xsession.) nxserver is listening to 5901. How to configure vnc to listen to 5902.
2. The guide also refers that
Here we "Prestart" vnc sessions for specific users, therefore no login screen is presented. This uses more resources as the VNC Session is running even when no client is connected to the session watching it. But there in lies it's advantage, "watching a session" and "using a session" are not the same thing! This method is very usefull for starting long running programs before going home. Once home you can re-connect to the session and see how things are going.
I have ubuntu 10.04 & I telnet to windows vista. Even if I create a hidden process [URL].. from batch file . It seems the process gets killed when I end connection at port 23 to host. Maybe , the hidden process created is still child of current telnet session so tree is killed as session ends. Is there a way to keep process running even after telnet session has ended ?
My OpenSUSE 11.2 is working fine as samba server, no problems, but I have a problem with KDM.My default init runlevel is set to 5 and every time I try to login at KDM (KDE4), the monitor goes black and returns to the login screen.If I hit Ctrl+Alt+F1 to go to console and start /usr/sbin/console-kit-daemon manually, press Ctrl+Alt+F7 to return to KDM login, everything is fine.What do I have to do to fix this issue?
been using 11.2 with KDE on a Sony laptop since 11.2 was released always ran perfect suddenly I can't login, I get to the login screen type in password it begins to load my desktop, then fails and dumps me back to the login screen I can login as root, all my stuff is there (under /home/me) I tried changing my password, no luck I went to run level 3 and there I can login just fine seems to be something with my KDE profile any ideas where I might find some error messages telling me what's going on?
this seemed to happen when I was running "blender" and making the machine do some heavy number crunching, it actually locked up.
I usually shut down openSUSE in KDE by clicking the shutdown icon and selecting "Turn Off Computer". When I boot back into openSUSE, my session resumes automatically without it asking for my password.While I don't mind KDE resuming my session because it saves time, me not having to reenter my password is a security risk. How do I turn off the autologin?
when I get into the login page, I can only see the background and the login box in the middle of the page just turns whole white and keeps flashing. no response for any clicks. I was force to ctrl+alt+F1 to switch to init 1 to do my work. But I still want to use my graphical desktop either KDE or Gnome is ok. I am using gnome.
I want, when I boot up, to load and log-in automatically a default user. I get a login in screen with the option to login as root, I do not want this. How do disable the option to login to X as root and just load as me/default user?
Every account every option I try. when I login, it just cycles back to the login screen. I have attempted to do a repair install, but to no avail. it happens when I try to boot normally or if I boot into failsafe.
The graphical login screen is loaded just fine. Though very shortly after (a moment after the loading screen could be seen) it crashes back to the graphical login. And that happens no matter what wm I'm trying - gnome, kde3, kde4, e16, e17, even twm.
It happened after the logout after a zypper up yesterday morning. Looking through the list of what packages were upgraded (two machines, both last zypper up'ed last Sunday, checked on the second one after the problem with the first one), the only packages which might be responsible are kwin or qt4.
The graphics card seems to be fine (NVidia 9600), as it happens whether or not I use nv or the propietary driver. Also tried reinstalling it from the repo as well as using the binary blob from NVidia. Has been tested on Windows and games are running fine there, so it shouldn't be the card.
What is strange, is that when calling upon sax2 -r from runlevel three, the initial screen loads nicely, but sax2 crashes back to the cli once one presses 'Change Configuration'. No error messages are being printed.
Any pointers on how I can narrow down the cause (and get it fixed)?
There are often times when the best way to launch an application is from the terminal, but it is a graphical application and after it is launched the terminal is useless.
Examples of places where a terminal is convenient are when a process starts lots of child processes and is also unstable; you can be sure to kill all of its children simply by using Ctrl-C at the terminal. Also it allows me to read program output and to set up the terminal environment to be optimal for the application (for example "unset LIBGL_ALWAYS_INDIRECT")
With GNU screen, I can get around the hassle of having a terminal window open by using something like the following in a terminal window:
Code: screen my_command Ctrl-A d
and then I can close the terminal and the program will keep running. Then I just type "screen -r <Tab>" (the tab will get me my screen session if there is only one such session) in any terminal window, even a tty, and I can get the screen session back and use Ctrl-c or something.
So my question is, is there a way to do this automatically so that a launcher or script will start a screen session, inside that screen session start a process, and then detach from that screen session without me having to manually open and close a terminal and type the commands?