I'm trying to login as guest, but this option does not seem to be available even after changing the LightDM configuration file. I'm on Debian Wheezy + XFCE 4.8. My /etc/lightdm/lightdm.conf looks like this:
[SeatDefaults]
#xserver-command=X
#xserver-layout=
#xserver-config=
xserver-allow-tcp=false
#xdmcp-manager=
#xdmcp-port=177
[Code] .......
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.
View 2 Replies View RelatedI have Debian 8.4.0 with lightdm. I'm trying to load some command lines at session startup, putting these in ~/.profile but the file is not loaded. The same procedure works well if I switch lightdm to gdm3.
Anyway, there is some idea to load some script lines at the session startup? The file .bash_profile neither works. I don't want to use ~/.bashrc because it would load every time I open a terminal. Neither to use init.d because it would load for all users.
I'm working on embedded debian. I do configuration to lightdm for autologin. My device start with autologin but sometimes I see login screen. ı will try it more than 20 times. 17 times its do autologin 3 times not do autologin and show login screen.
Autologin error log.URL...
Autologin log.URL...
Lightdm.conf. URL....
I'm tried lots of autologin lightdm document. Bu i cant success for auto login.
View 7 Replies View RelatedI just installed Lightdm from "bob"'s ppa, and it looks great when I run it from a virtual console (like Ctrl+Alt+F5), but how can I replace the gdm login manager with it? And when I do that how can I make ldm not register the Samba Guest User as an actual user? I am using ubuntu 10.10
View 9 Replies View RelatedI'm trying to get samba working on a debian/xebian box to use as a fileserver. I have a HTPC which is win 7 and a laptop which is OS X. I've installed SWAT and Samba to manage the whole settings. I'm trying to get it setup so that there's a user which has access to my ~/ and a guest user which just has read access to ~/Media/ so that the Media centre can read all the files from it without having to login.
The problem is when I have map to guest set as NEVER I can access the samba ~/ and I'm asked for a username and password which I login with fine and can access the files on both share ~/ and ~/Media. However when I set the map to guest to bad user or bad password I can access the share for ~/Media. But when I try and access the share ~/ I don't get any login box and I immediately get the error "Can't access share permission denied" or an error along those lines.
Here's my /etc/samba/smb.conf
# Samba config file created using SWAT
# from 192.168.1.65 (192.168.1.65)
# Date: 2010/07/10 20:39:16
# Global parameters
[global]
workgroup = MS_HOME
server string = %h server (Samba %v)
obey pam restrictions = Yes
passdb backend = tdbsam, guest
passwd program = /usr/bin/passwd %u
passwd chat = *EntersnewsUNIXspassword:* %n .....
How to get it working so I can have a guest share for my HTPC and a logged in user for my private files?
System is Wheezy 7.9 with lightdm and MATE desktop.
I have 128GB SSD with various partitions for operating systems and a separate HDD for the /home folders for each OS. Wheezy is my primary system, the others, apart from the original XP are experimental.
/etc/lightdm/lightdm-gtk-greeter.conf is
Code: Select all#
# background = Background file to use, either an image path or a color (e.g. #772953)
# show-language-selector (true or false)
# theme-name = GTK+ theme to use
[code]....
The problem is that each time I use the Ubuntu system and I change back to Debian, the greeter background contains snippets of whatever was displayed while I was in Ubuntu. What I don't understand is how this can happen, given that the operating systems are installed in separate partitions with separate /home partitions as well. After I have used Debian and restart, the greeter screen is clear, as it should be.URL....
I'm running Debian 8.4 on a Lenovo W500 laptop and I recently upgraded from kernel version 3.2.0-4 to 3.16.0-4. Since then I encounter issues with lightdm (I suppose) which manifest themselves in two different scenarios:
1) scenario 1: lightdm fails to start.Instead of showing the graphical login screen, the system boots into terminal. Lightdm seems to be running, but I can't enter the X-Session (Alt+Ctrl+F7 doesn't work), nor can I restart the lightdm via
Code: Select all# service lightdm stop
# service lightdm start
dmesg shows the following (I've only pasted the end of dmesg):
Code: Select all[ 240.100071] INFO: task kworker/0:2:39 blocked for more than 120 seconds.
[ 240.106512] Not tainted 3.16.0-4-amd64 #1
[ 240.112956] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.119494] kworker/0:2 D ffff880155155a48 0 39 2 0x00000000
[code].....
and /var/log/lightdm/lightdm.log shows errors of type
Code: Select allGtk-CRITICAL: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
when I then try to shutdown via
Code: Select all# shutdown -h now
the OS gets stuck on a message of the form
Code: Select allirq 17: nobody cared
and eventually I have to force a shutdown by holding the poweroff button.scenario 2: lightdm starts, but can't be stopped/In this case I can login and use the system as usual, but when I try to shutdown either via # shutdown -h now, or via the GUI or the power button, the system gets stuck and I have to force a shutdown by holding the poweroff button.It seems that people had similar issues on other distros (see e.g.: URL... but there doesn't seem to be a good fix so far. I can for now solve the issue by downgrading the kernel to 3.2.0-4, but I was wondering if there is a permanent fix.
Just made a strange discovery, visiting the website: [URL] .... with iceweasel within university's network makes my computer almost unusable. htop's output indicates:
USER: 'root' CPU: '98%' Command: '/usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch'
What this meant to be and/or how this could be circumnavigated?
I have an odd issue -- fairly fresh Debian Testing install, using Lightdm.
After booting up, Lightdm starts, and then a moment or two later restarts. As a result, any keystrokes captured by the first run (e.g. the first few characters of my username) are lost. My lightdm log is:
Code: Select all[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.16.7, UID=0 PID=827
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration
[Code] ....
This log shows me seeing the login screen, waiting for it to restart, and then logging in correctly on the first attempt.
Since I've made the switch to Systemd, I've been having various problems with LightDM.
The most interesting and frustrating problem is when I choose Shutdown or Restart from the XFCE4 shutdown menu, the XFCE4 session closes but then the lightDM greeter pops back up. The system doesn't even try to shut down.
Its as if restart and shutdown both act the same as the Logout button.
Im running XFCE4 4.12 (but same behaviour on 4.10). I have the latest LightDM and the latest Systemd.
I installed debian 7 with lightdm and MATE 1.8 (from backports) on a new PC.
Since the first day the mose keeps disappearing. For example when I click on something, the mouse disappears and only comes back when I move it. Sometimes it already disappears when hovering over a button (especially annoying when it happens while you try to resize a window).
That problem did not happen for example in LXDE, which I installed just to test that.
I did install MATE 1.8 on several laptops/PCs so far, never hat that problem. Maybe it's because of quite recent hardware?
Code: Select all00:02.0 VGA compatible controller: Intel Corporation Device 041e (rev 06)
I'm using MATE with Lightdm as display manager in Jessie and I've been using a very simple script run from /usr/share/lightdm/lightdm.conf.d/01_debian.conf to slow down the mouse cursor, something like
Code: Select all#!/bin/bash
xinput --set-prop 10 269 -1
xinput --set-prop 10 267 1.100000
the script was placed in my ~ and called from 01_debian.conf , and so far it used to work.
Lately this script wasn't executed properly, most likely because I had unplugged the mouse from its usb port and then plugged again in a different port, and as a result Lightdm wouldn't start at all.
After much trying, because this by coincidence happened after the update to 8.4, I realized that it wasn't a serious failure of the X server as I suspected (the update included a new version of the flgrx driver), but a simple matter of Lightdm failing because of this script: in fact, I could still manually start the session with startx as regular user, although this only gave me access to a LXDE session instead of MATE (I have also the LXDE environment because when I installed Jessie I did use the LXDE version and then added MATE).
What happened was that the mouse properties were scrambled up, so xinput --set-prop 10 269 -1 had now to be something like xinput --set-prop 10 268 -1 and so on - therefore the script failed and in turns Lightdm failed as well.
-is this supposed to happen when you unplug the mouse and then plug it back in a different usb port? It reminds me of some windows-like behavior, where usb peripherals had to be always in the same port to work properly.
-is Ligthdm supposed to fail because of this, or is it kind of a bug? It looks weird to me that instead of simply not executing the script, the whole display manager fails.
In testing, with an identical setup, as a matter of fact the script failed as well (it's on another partition on the same hardware) but Lightdm started as usual.
-when trying to modify the mouse properties in that script, I couldn't get them right again: what looked correct in the booted system, was once again off at the next reboot (i.e. property 269 was 270 again and so on), therefore I ditched the above setup and placed everything in the .xsessionrc file, and it worked again.
-why startx defaulted to the LXDE environment? where is this setting stored? How could I have specified to start a MATE session instead from command line?
i'm trying to setup a permanent CIFS share from my nas, but it keeps prompting for a password dispite GUEST access set on the share.FStab is as follows:
Code:
//192.168.0.253/media/ /mnt/nas1_media/ cifs guest,_netdev 0 0
if i do
[code]....
I like very much the Guest Session feature of Karmic, it comes very handy when someone needs to use your computer. However, it's only available if I'm already logged in, it won't show this option at login screen. Is there any way to make this possible? Also, I once tried the guest session and configured its appearance to my taste. The next time I entered, though, the default desktop reappeared. I know this happens because no setting is permanently stored for this session, so the only solution I can think of is to change the default configuration it is loaded from.
View 4 Replies View RelatedAdding 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
Code:
gksudo nautilus
[code]....
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 learned how to do this on the 'net somewhere. This HowTo will help you create an account on the login screen that will log in the same guest-session seen in the user menu. The advantage of this is that it will be an easily accessible guest account, while not preserving any files or changes on logout, and a higher security model for the account. Confirmed to work on 10.04 - 10.10, but the directions are for 10.10
1. Under an existing administrator account, go to the menu entry System --> administration --> Users and Groups.
2. Click Add. you may need to provide a password at this point. Name your new user anything you would like, except guest. The account cannot be called guest, but visitor does nicely. encryption of the account is not needed. This account will be a "booster" account to guest-session.
3. On the next screen, enter a password, and make sure that you click the check box "Don't ask for password on login", Click OK to finish.
4. As an extra precaution, click Advanced settings, when back on the Users and Groups screen, and on the User Privileges tab, uncheck Monitor System Logs.
5. Exit the Users and groups menu, and then log out and into your new account.
6. Once there, make a folder called GuestManager, and in that folder, make a plain text file called Guestmanager.sh, with this code in it :
Code:
#!/bin/bash
# Launches the guest session
/usr/share/gdm/guest-session/guest-session-launch
# Logs the user when done
/usr/bin/gnome-session-save --logout
7. Save that and then right click on it, go to properties, and then go to the permissions tab. On this tab, click "allow executing file as program", and then close that window.
8. Open the menu entry System --> Preferences --> Startup Applications, and once there, turn off all the startup applications, and then click add. Fill in the name and comment as GustManager, and for the command, enter /home/visitor/GuestManager/GuestManager.sh, where visitor would be the name you picked for the account in step 2. click add, then close
9. Delete all applets and extra toolbars (might want to leave the main gnome menu), and set the background to black or something else bland, and log out. Since this account is just a "booster" none of these toolbars and such will be needed, so removing them saves memory and load time.
i am wondering if it is possible to do this all i can find with google is idea proposals and brainstorms i know i could make a separate account and call it guest user bu that user would get to keep data/settings where as a guest session places a temporary account in the /tmp folder which combined with a ram disk for /tmp would result in some really fast performance since i use a ssd for / which would make the traditional hdd only used for /var also since /tmp would be a ram disk it would be like the guest is using a live cd with security restrictions and performance enhancements on top of this there would be no trace of the guest on my computer after shutdown
View 4 Replies View RelatedBasically, the problem is, we have a bunch of computers in a computer lab, that we want to students to access, but not modify in ANY way. That includes backgrounds or whatnot. And after restart, any changes they may have made, change back. Also, they can't have read access to the administrator account on the computer.
This needs to give a permission denied, or something:
Code:
cd /home/(admin account username)
ls
The Guest Session is exactly what we are looking for, but try as I might, I can't get it to work. Because, we don't want to have to login as administrators, then activate guest session, just for our students to use the computers. The idea being, we can leave the computers in there, and not worry about the students breaking anything.
One thread I tried was: [URL]. However, using his method, will log the student into the account, and after about 5 seconds, log them back out.
The other method listed lower in the thread,
Code:
/usr/bin/guest-session
Seems to work, but upon logging out, fails to launch the gdm
Only way to restore is restarting the computer.
I have a samba server with security user. I have a number of shares inside the share with different users logins. But while accessing the shares from windows, in the login prompt, by default username it takes as the guest. How will I disable the default guest user login ?
View 2 Replies View RelatedI was doing some thing on networking on virtual machine (rhel 3 as guest os) and winxp as host .. now when i started my guest os (linux) the login page letters (like username and password) size became very large so that i could not see them (crossed the screen) .
View 1 Replies View RelatedHas anyone sucessfully got LightDM to work? If so how did you do it? I am running Ubuntu 11.04 with the Classic Gnome Desktop and would like to use LightDM instead of GDM... I have installed LightDM but nothing is different at all.
View 6 Replies View RelatedI'm trying to install the Guest Additions for a VM running a guest Lucid Lynx Server. The problem I'm encountering is this: The vboxadd-install.log for vbox says it "couldn't find the sources of your current Linux kernel" and to "Specify KERN_DIR=<directory> and run Make again."
View 4 Replies View RelatedI have a local file server running Samba on Fedora 9. It's already configured and serves a few people without any problems. I am now trying to set up a new read-only share with the username 'guest' and the password 'guest'. However, with no success so far! If I log on as 'guest' with the password 'guest' like so:
Code:
su - guest
No problem. Once logged in, if I try:
Code:
smbclient //samba/share
I'm prompted for a password. If I enter 'guest' I get:
Code:
session setup failed: NT_STATUS_LOGON_FAILURE
If I enter nothing (null) I get:
Code:
Anonymous login successful
Domain=[RIVER] OS=[Unix] Server=[Samba 3.2.8-0.26.fc9]
tree connect failed: NT_STATUS_LOGON_FAILURE
OpenSUSE installed in a Virtualbox Virtual Machine and I want to set a shared folder.
1 - Set up a Virtual Machine and install OpenSUSE 11.2
2 - Create a shared folder on host (HostFolder)
3 - Setup the shared folder in Virtualbox Via the Virtual Machine details or via Devices > Shared Folders...
4 - Install dependencies for running the Virtualbox installer You need to install the right development kernelpackage for your machinetype (use 'zypper search -i kernel' to see what's installed) sudo zypper make gcc kernel-source kernel-hosttype/default-devel
5 - Run the Virtual Machine and go to Devices > Guest Additions This mounts an iso image in your OpenSUSE guest.
6 - Open a root terminal and run
cd /usr/src/linux
make oldconfig && make prepare && make scripts && make dep
cp ../linux-obj/$HOSTTYPE/default/Module.symvers .
make prepare
* A commenter on previously mentioned thread says this step is unnecessary but it doesn't work without on my system. I suggest trying step 7 first and returning to step 6 if that fails. *
7 - Run ./VirtualboxLinux yourhosttype .run from the mounted iso image.
8 - Create shared folder in OpenSUSE (GuestFolder)
9 - Test with sudo mount -t vboxsf HostFolder /home/user/GuestFolder It works? Great! Let's set up the system so it automounts for your regular useraccount instead of root-only access.
10 - Add this line to /etc/fstab HostFolder /home/user/GuestFolder vboxsf defaults,uid=1000,gid=1000 0 0
11 - It works for me but if it still doesn't automount after a reboot; sudo mount -a
I installed a Fedora 14 guest on a Fedora 14 host with Virtualbox, then i run these commands on the guest:yum install kernel-devel kernel-headersbut if i try to install the virtualbox-guest additions on the guest, is still complains about that it's unable to find the kernel source directory?Ha anyone succeded installing the guest additions on a guest Fedora 14?
View 2 Replies View RelatedI had a lot of trouble installing Guest Additions within the Fedora 13 Guest on a Linux host. I had to mount the vboxGuestadditions.iso from the Device --> CD/DVD Devices menu. Then I located the appropriate package for my system. In my case it was the AMD64 Linux version.I ran this as administrator in Terminal. I used the "bash" command followed by the package name. This was after CDing the the appropriate directory. The packaged installed, I then rebooted and it worked fine. (Something that would make this easier is to load a script into nautilus that would allow me to open a locatation as administartor at the open window. I'm sure there is something in Fedora to do this but I couldn't find it in a hurry so I used the command line way).
View 5 Replies View Relatedi've installed kubuntu 10.04 on a sun virtualbox , and when i tried to install the guest additions i got this error in the terminal:
Building the VirtualBox Guest Additions kernel modules. fail ! (Your system does not seem to be set up to build kernel modules. Look at /var/log/vboxadd-install.log to find out what went wrong) i'am running windows 7 as a host operating system .
im new to virtualbox and i run linux arch as guest os. now my question is how it can be that the vm has the same ip as my host os.
this is suppose to be diffrent machine isnt it? and how to configure my guest vm to be completely unrelated to my host