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.
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.
I am trying to make a web server with debian 6 and i want a xfce dsektop when i need to open files,extract,navigate but to be able to turn it off when i dont need it (to save ressources).I already installed it with aptitude install xorg and aptitude install xfce.
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:
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....
Just made a strange discovery, visiting the website: [URL] .... with iceweasel within university's network makes my computer almost unusable. htop's output indicates:
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.
After install debian 8, I can't see system start and stop message from console ... How can I enable system message from console in debain 8?
debian 7 output ---------------------------------------------- root@demo:~# service apache2 restart [ ok ] Restarting web server: apache2 ... waiting . root@demo:~#
debian 8 output ----------------------------------------------- root@demo:~# service apache2 restart root@demo:~# <=============================== No message (start or stop)
I am using debian squeeze server with asterisk 1.6 installed and configured.my problem is non root users need to access the server using ssh and restart asterisk server after making changes in asterisk configuration files.As of now i am giving root username/password for this process (i know it is not at all a good idea) .now how can i create a username and configure it which can only access and modify asterisk configuration files and restart asterisk server without any other privileges.
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'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.
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?
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 using debian 5 x64 with xfce.Is there a way to configure (start/stop/restart) services (especially Apache2, mySQL and PHP) using a graphical or cli tool? I tried to use sysv-rc, sysv-rc-conf, rcconf and rc-conf in the terminal but Bash didn't find them (Although Synaptic show that sysv-rc is installed).
I am trying to give access to ONE single user to start and shutdown tomcat server. The problem being, when I enter syntax: username ALL= /etc/init.d/tomcat5, /usr/local/tomcat/webapps, PASSWD:ALL This gives the user access to start and stop tomcat but also gives user access to start and stop other services within /etc/init.d - such as httpd etc... What is the proper way to give user access to start and stop service, and limiting that power to only one service....
I was able to start multiple X servers before. Now after the upgrade to rootless X, I had to add myself to the "input" group to be able to start X, but I'm unable to start 2nd X on a different vt.
Here are the errors and warnings I'm seeing:
Code: Select all[114940.404] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied [114940.409] (WW) Falling back to old probe method for modesetting [114940.409] (WW) Falling back to old probe method for vesa [114940.409] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [114940.409] (EE) Screen 0 deleted because of no matching config section. [114940.409] (EE) [114940.409] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
After doing Debian's apt-get dist-upgrade from Wheezy/oldstable to Jessie/stable, I decided to try Kernel v4.2.0 instead of v3.16.0-4-amd64 to be even more updated. However, X doesn't work. /var/log/Xorg.0.log showed:
Code: Select allX.Org X Server 1.16.4 Release Date: 2014-12-20 [ 453.305] X Protocol Version 11, Revision 0 [ 453.305] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
I'm trying to start/stop Informix along with my linux os start/stop. For this I've made a test script in order to test this but I'm facing a problem. The service is starting along with the system but when I'm stopping (rebooting) the system it doesn't run the "K10test" script.
After sistem reboot you can see that the /etc/init.d/test stop is not executed.
i've made a big update of almost 300Mb.I'had a working DNS server.Now, when i boot the box, named works and it resolves all the clients.If i make any change (enter a new client for example) and of course i restart named (service named restart), named stop but does not start again !!!In order to get a working named, i 'm obliged to reboot the box?
When copying files to USB drives, the file progress bar moves it 'bursts', sometimes doing nothing for long periods, then moving forward quickly and stopping again.It's almost like it is showing the transfer to the cache, not the transfer to the actual drive.
I need to stop KVM starting at boot. I added following 2 lines at the bottom of /etc/modprobe.d/blacklist.conf Code: blacklist kvm blacklist kvm-amd Reboot PC It doesn't work.
$ lsmod | grep kvm Code: kvm_amd 41556 0 kvm 190648 1 kvm_amd What further command I have to run in order to activate the new blacklist.conf ?
i am using putty to connect to my server and wanted to restart mysql server. searched the internet and found thatcommand is /etc/init.d/mysqld start or stopbut it did not worked.then tried /etc/init.d/mysql stop or startthis also did not worked.
