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 RelatedIn 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 press On-button, Debian boots, logs in and automatically connects to the Wireless network AND! to my local pc via LAN. It runs an ssh server, so I can ssh into debian over internet and communicate with the local pc (send a magic packet).Here are my problems:
1) I don't how to log in automatically. This and this doesn't work.
2) I need a network tool that can manage multiple connections and has a reconnect feature. With the default network manager I cannot even connect to more than one network simultaneously although I have two network devices of course.
And I guess I can run all that in console mode, right?
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] .......
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 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 am trying to login as root but i end up with an error that says: su: Authentication failure
View 10 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 am new to Debian and I have been trying to find a way to auto login to a users account upon Debian booting. Is there a way to auto login to the root account upon a Debian boot? Is it possible to do this with GNOME installed as well as Minimal?
View 1 Replies View Relatedis there a way to auto login as root? login in window preferences won't allow me to select rootPS before anyone starts on the me bad, I'm a programmer using it on a closed embedded system, and need to link to others software, and need to be root
View 6 Replies View RelatedHow can i do auto login with gdm3 on debian jessie?
View 1 Replies View RelatedThe apt-get autoremove command, I use Debian 8 for some time now and I often install a package, test it for some minutes and remove it then. I noticed that in most cases (if not all, I'm not completely sure) all the dependencies that were installed with the package (mostly libraries, of course) stay installed on the system when I remove the package.
And there is no output of apt-get that there are unnecessary pacakges which I can remove with apt-get autoremove. The autoremove command does nothing.Before I changed to Debian, I used Ubuntu and there all the dependencies are removed with apt-get autoremove when I uninstalled a package.My question is now, is this normal? if there are fundamental differences in which packages "autoremove" removes between Debian and Ubuntu?
I have a "time-server". It's sending time to different devices through different ports/protocols. The problem is that it has no operator and that makes some extra difficulties.
Now when i try to start it using terminal Code: Select allsudo ./myprogram works fine and
Code: Select all./myprogram doesn't work.
It is so because without sudo i have no access to ports. As a result If i add my program to System->Preferences->Startup Applications it has the same problem. So i need to start it as root, auto-start, right after auto-login to system but without entering password cause nobody will do it.
Also I need to start ntpd but it also asks password sometimes I've tried googles but it offer a few ways with entering password that isn't suitable for me or writing some scripts/changing system files but with no example I'm afraid to break it all. So is there a way to start Myprogram and NTPD as root with no password entering?
My system is Debian 6.0.10 Squeeze, Kernel 2.6.32-5-686
I can use this at the end of bash_profile to autorun start x after logging on. code...
But what about to auto logout after killing the X session? I hit exit from fluxbox, but I could add a menu item I suppose to just kill the xsession. Wondering if there is a graceful way to do it with bash_profile.
Also, on a related note, if I switch to dash with the bash_profile method still work?
I have recently installed Debian Lenny with KDE3. I foolishly checked Auto Login after installation and now I can't get rid of it. The KDE Login Manager window seems to offer the option of turning off auto login, but it does not work. I have tried useradd and userdel but this only makes things worse.
View 3 Replies View RelatedAfter installing Jessie, apt-get gives me a huge list of packages with the suggestion to autoremove them. Now, I've tried auto-remove once and was left with a naked Gnome, so I was wondering if there's another way to find out which packages I should keep and which I can safely remove. Is it safe to delete packages that cannot be found using the search function for the stable release? I checked them one by one here URL....How about linux images that won't appear in the above search?
linux-image-3.14-0.bpo.1-amd64
linux-image-3.14-0.bpo.2-amd64
linux-image-3.16-0.bpo.2-amd64
linux-image-3.16-0.bpo.3-amd64
linux-image-3.2.0-4-amd64
How about results shown by deborphan?
I have a debian 8.1.1 server running owncloud and a proxy server at home. I have everything working fine, with one exception. The proxy server won't start on boot. If I ssh into the server, then run "sockd -D" as root, it starts up and runs just fine. Any guides I find refer to the init.d script method that worked in Wheezy, but that isn't working. I think it has to do with Jessie switching to systemd? I had used someone elses script in init.d, and ran update-rc.d, but it still doesn't start.
With Jessie, how can I make "sockd -D" execute on system startup?
I was just wondering if there's any point having both auto and allow-hotplug against the same interface in network/interfaces as allow-hotplug seems to bring an interface up at boot on its own.
View 3 Replies View RelatedI'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
....
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.
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.
I have successfully mounted my Win7 volume and my external hard drives NTFS volume as well. However, after modifying the fstab I seem to only be getting the win7 volume to auto-mount. Below is the contents of my fstab. /dev/sdf3 is not mounting. Again, it works no problem if I manually mount it.
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
[code]....
I'm trying to use network-manager in sid and it's incredibly frustrating because every 2 minutes or so it seems to scan for wireless access points, during which time my SSH connections completely hang and screw up. Pings start dropping packets as well. By doing an "iwlist scan" I can reproduce the behavior. Has anyone else dealt with this? I haven't been using network-manager, but I am currently due to mobility and needed VPN functionality... WICD with no network-manager works better but there's no gui-based VPN support. I've got an Atheros wireless device and I've read that supposedly it should be doing background scanning since kernel 2.6.32, but I haven't seen anything like that, and I'm on 2.6.32-5-amd64 currently, 2.6.32-3-amd64 behaves the same too.
View 4 Replies View RelatedI use Debian Squeeze on my laptop, and in my office we have a WinXP box where we store all our documents and stuff. When I'm in the office, I can directly mount my directory to edit documents, and at home/wherever I can use VPN to connect to the box so it's no problem again.
However: I'd like to know if there is a way to set up a directory on my laptop, that I can use even when offline, and then when I'm connected to the office computer, it automatically syncs with it.
I have a ppp0 entry with post-up options like this
mapping ppp0
map none photon-plus motorola
map timeout: 12
## map init-time: 12 # for slow drivers
[code]...
If I comment those off then no such problem, hence some how ppp0 executed automatically and there is no [auto ppp0] any where. How can I stop this forcefully ?
I recently installed 32bit maverick and wanted to make it login automatically. I tried enabling auto login from Admin > Login but that didnt work and I was still prompted for my password. Then I went to Users & Groups and changed the password option to Do Not ask for password at login now after I reboot, the user list is shown (only 1 user) and it doesnt ask for password after I click on my username.
However, then it gives a few errors (as i vaguely recall):
1. cannot load .ICE directory in my home directory
2. some error 256 about a gconf-sanity-2 file
3. nautilus cannot load my home directory etc
and then it gets stuck without loading anything (blank wallpaper). i ve tried navigating to my home directory using Alt F2, gksudo nautilus and my home dir contents are encrypted by the ecryptfs (there is a readme.txt file and a shortcut). i have tried to decrypt but it doesnt work... i ve also tried to start/stop gdm, and startx but nothing works. if i stop gdm, then the prompt doesnt recognize my password and keeps on rejecting the commands i enter... I think this has something to do with the home dir not being decrypted due to the dont ask for paswd option... how can i disable the dont ask for pwd without the gui (i can access my / by booting through an external usb).
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 have Debian Squeeze AMD64 bit release. It finds my wired ethernet connection and ues itfine, although nothing shows up in the top right corner under the networking icon.
When I plug my mobile phone in (HTC S620) it always uses this as the main internet connection and then even if disconnected wont use my wired connection until I reboot.
Is there a way to stop it doing this or at least have my wired connction as an option so I can just click to reconnect to my ethernet connection?
