I want to set the login to the old default of having to enter a username,password. I've tried to use the configuration editor to achieve this and have ticked the "disable-user-list" option under /apps/gdm/simple-greeter but it makes no difference, the greeter still starts with a user list. It appears that the default valuef TRUE for this function is overriding my choice, but I'm notre why. My next step appears to be to edit /etc/gdm3/greeter.gconf-defaults to change the default value. I haven't actually tried that yet so not sure if it would work but, even if it does, it doesn't seem a very elegant way of setting this up. Is there some simple way of changing the behaviour back to asking for username first?
I seem to remember the whole login process as being more configurable than it is now, with options to choose backgrounds, allow root accest finystem->administration->login_screen only gives a choice between selecting a user or automatic login of a particular user, with no further options available.On a general note, would the old method not be a more secure default than presenting an unauthorised user with a list of login id's to be tried?
Having trouble installing 'Squeeze' 6.0.1a-amd64-netinst on a new AMD64 system.The installer boots and runs fine until it gets to hard disk detection. Then it hangs for about 20 minutes showing a blue screen, during which time the HDD-activity light flickers every 5 seconds. Eventually it says it can't detect a hard disk, and displays a (longish) list of possible drivers; no idea which, if any, would suit.Anyone else installed (successfully or otherwise) on this combo?
I want to install Adobe's Flash, as opposed to one of the free options (they don't handle some content well). I have Googled around to try to find out how Flash is installed, but there doesn't seem to be one recognized way.
I found the following:
[URL]
Is anyone using Adobe's Flash on amd64 and is happy with the install?
The following packages will be upgraded: libavcodec52 libpostproc51 libswscale0 3 packages upgraded, 18 newly installed, 0 to remove and 5 not upgraded. Need to get 16.5 MB of archives. After unpacking 31.5 MB will be used. The following packages have unmet dependencies: libavformat52: Depends: libavcodec52 (< 4:0.5.2-99) but 5:0.6.1+svn20101128-0.2 is to be installed. or libavcodec-extra-52 (< 4:0.5.2-99) which is a virtual package. The following actions will resolve these dependencies:
[code]....
Normally I say yes and hope for good, but this time... I do not use adobe flash player, but I would still like to watch ..... videos. Would be hard without gnash, right? I use iron portable and iceweasel. Also I use totem a lot, but aptitude seems not being able to resolve this inconsistency automatically. My question is: what would happen, if I just say "y"? gnash is completly away? And is there any way to install newer version of gnash or do whatever to have everything working?
After a fresh custom install of Squeeze I could not play any video. debian-multimedia.org repository is in my sources.list. Trying to play an AVI video with totem I get the message
Recently upgraded to 8GB RAM. BIOS shows 8GB, lshw shows 8GB (2 x4GB), Applications > System Tools > System Monitor > System shows 3.7GB. After 2 days of forum hunting I cannot find a way to check whether the machine is using all 8GB and, if not, how to make it do so. I have found a few postings about using the "bigmem" build but these seem to be for the 32-bit builds as well as a few postings saying that the amd64 build uses bigmem/highmem by default. I can't find any reference to CONFIG_HIGHMEM in /boot/config-2.6.32-5-amd64 and I don't have a menu.lst in /boot/grub to change to a "bigmem" type build.
The way I usually boot Linux distros, and this has worked for every distro I have tried up to Kubuntu 10.10, was to install Grub2 on an extended partition, run "dd if=/dev/sda5 of=linux.bin bs=512 count=1", and then adding that bin file to my Windows boot.ini. What usually happens after is that I get the Grub2 menu after selecting it from the Windows Bootloader.
The problem is, with the latest Squeeze AMD64, all I get when I do this is a static cursor and the computer is frozen and I have to hit the reset button.I mounted the Linux partition with Ext2IFS (mkfs.ext3 -I128 /dev/sda5 to get 128KB inodes), and I can see that the Squeeze installer did indeed install Grub2, because I can see the files in their respective directories.
I wanted to know which is the best firewall application for my debian squeeze amd64 home desktop. I prefer a simple interface yet powerful enough. After googling I found two options - gufw & firestarter. I am not sure which one to choose between these two.
Using the howto at http://wiki.debian.org/skype I installed Skype 2.1 beta 2. It launches OK using either skype or linux32 skype and brings up the login screen. It already has my username but when I enter my password skype crashes before logging me in. I get the error:
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 a laptop connected via HDMI port to different external displays throughout the day. I have configured the displays (Settings > Displays) to turn off the laptop display and set the external display as primary. However, this setting only takes effect after login. Thus, I am unable to see the login screen greeter on my external display because I close the laptop lid, so I am logging in blindly to a gray login screen background.
he issue I am facing is that when I start the laptop with an external display connected, the greeter only appears on the laptop display. The gray login screen background image spans both laptop and external displays and my mouse pointer appears on both displays, so I know both displays are detected and configured as dual displays. But, I am guessing, the laptop display is set as primary while the external as secondary.
I would like to know if there is a way to dynamically switch the greeter between the two displays, regardless of which one is set as primary and secondary. Or, is there a way to configure the system such that if there is an external display connected via HDMI, then it is set as primary, and if no external display is connected, then the laptop display is set as primary?
I have searched all over the net and this forum to no avail. I read a post which required copying the user's ~/.config/monitors.xml file over to /var/lib/gdm/.config/ but this caused my laptop monitor to be turned off at login even when there was no external display connected.
Hardware: Acer Aspire 8730G, Core 2 Duo T9900, 8GB RAM, Nvidia Geforce 9600M GT. Software: Debian 8.4 Jessie, Gnome 3.14.1, Gallium 0.4 on NV96 (I am assuming this is the Nouveau driver)
Contents of the /etc/X11/xorg.conf file which I generated with the command "Xorg -configure" as root in console mode:
Code: Select allSection "ServerLayout"   Identifier   "X.org Configured"   Screen   0 "Screen0" 0 0   InputDevice  "Mouse0" "CorePointer"   InputDevice  "Keyboard0" "CoreKeyboard" EndSection
[Code] ...
I suppose I will continue to login without seeing the greeter on my external display.
Some days ago (2015-09-28) I installed Debian testing amd64. Log in as a user failed and instead of the Gnome UI there was a sad face with the text: „Oh no! Something has gone wrong. A problem occurred and the system can't recover.
All extensions have been disabled as a precaution. Log out“.
The relevant output of journalctl (run as root) said:
etc/gdm3/Xsession[5379]: cannot connect to brltty at :0 - /etc/gdm3/Xsession[5379]: Service 'org.kde.kaccessibleapp' does not exist. - gnome-session[5379]: x-session-manager[5379]: WARNING: Application 'gnome-shell.desktop' killed by signal 5 - gnome-session[5379]: x-session-manager[5379]: WARNING: App 'gnome-shell.desktop' respawning too quickly - x-session-manager[5379]: Unrecoverable failure in required component gnome-shell.desktop
[Code] ...
After some investigating, I found three work-arounds.
(1) Use gdm3-autologin: In /etc/gdm3/daemon.conf, remove the double crosses and insert own user name AutomaticLoginEnable = true AutomaticLogin = <own user name> Disadvantage: Only one user can have access to the Gnome ui. If you log out, you enter the gdm3 greeter and … see above.
(2) Turn off gdm3 by running 'systemctl stop gdm3' as root, log in into a terminal as a user and run startx.
(3) Install package lightdm and make it to the standard display manager with 'dpkg-reconfigure lightdm'. Disadvantage: Energy manager and screensaver settings of the Gnome control center are ignored.
The easiest way, however, especially if there are several users, is logging in via the gdm3 greeter.
I like to rip DVDs to iso before taking my laptop on long bus/train rides and am at a complete loss as to why I can no longer rip.
First, dvd::rip failed. Then `dd if=/dev/cdrom of=file.iso` failed. Then right clicking the cd icon on desktop and clicking copy (via brasero) failed. Each of the above worked at some point, and now all are giving me an i/o error like:
I am running 11.4_64, KDE47 (recent update from 46) I have three Suse Linux pcs on my network. I'll call them desktop, media center and laptop.
I am logged in to my desktop , I want to open a new session and log in to my media center.
From GUI, I select application launcher - leave -switch user and get a fresh kdm greeter screen.
On the Greeter screen, I select Menu - Remote Login A window opens displaying three machines - my desktop, my laptop and my media center. When I move the mouse into the new window to select the media center as the new target machine, the window immediately closes.
I have Xdmcp access enabled in kdmrc on all three systems(and rebooted).
This did work fine back when I was on KDE45 and KDE46.
Is there a new permission or setting now under KDE47?
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.
My old computer started randomly rebooting so I went out yesterday and bought a new one. It's a standard Intel 64 architecture with 2gb ram etc.The old computer was running Lenny however I'm happy to upgrade, so I just went to the main Debian download site and downloaded:debian-6.0.1a-ia64.netinst.iso (this didn't work, apparently ia64 is for itanium and my machine is definitely not that), so I downloaded: debian-6.0.1a-amd64-netinst.iso, burnt the CD and ran the install. First time through I had a power failure.
Second time through (a complete fresh start - new partition and everything) it went all the way through to completion and reboot.Clicked 'Continue' to reboot and the machine reset as it would normally and the Grub loader started okay, prompted for the "Debian amd64" standard boot image, selected that and the first 6 lines appeared normal, then the messages wizzed by so fast that only superman could read them. Then they stop - here is some of the content...
[3.816673] Kernel panic - not syncing: Attempted to killl init! Call trace: get_empty_filp panic
[code].....
Running it again I get similar stack stuff but it's a different place: [3.541816], [3.427502] And sometimes if I wait for a minute or two it will continue on further but appear to crash again. Hardware details (everything is onboard - no added cards):
And answer from wine forums: [*]Migi wrote: but OpenGL is working, i have Debian Sid AMD64, Wine needs 32 bit OpenGL.[*] How can i (can I??) run 3D on wine on to amd64?
I recently purchased a new Lenovo Thinkpad T420i and am having problems installing the latest version of Squeeze from CD. After receiving the laptop, I started it up, configured Windows 7, and confirmed everything is working correctly. Next I went through the Debian installer, which completed successfully. I'll be dual-booting Windows 7 and Debian, so at the partitioning stage I resized my NTFS partition, added a shared VFAT partition, then used the "Guided" install to create my root and swap partitions. My partition layout is code...
I assumed something was wrong with grub, so I booted the CD into rescue mode and chose to reinstall grub onto the Master Boot Record. But nothing changed. Just to experiment, I went into fdisk, deleted all my new partitions (leaving just the Windows ones), and tried rebooting, but the same error happened. I then went through the Debian installer again, being careful to set everything up correctly, but still, the device won't boot.
I'm not even getting to the grub boot screen, so something is wrong even before the point. Reinstalling grub to the Master Boot Record (grub-install /dev/sda) isn't changing anything. How can I troubleshoot this?
This one has been bugging me for some time now. The network interface (as defined in Debian's /etc/network/interfaces file) fails to obtain an IP address from myuter. However dhclient br0 does.I'm using br0 since I run a XP virtual machine.network/interface changes are from a Debian howto on setting up the tap interface.As near as I can tell, the /etc/init.d/networking script basically calls /sbin/ifup -a. ifup is a binary.My /etc/network/interfaces file is:
I tried to install Skype, using the Debian download from Skype, but it didn't want to play. I downloaded the Ubuntu 64-bit deb and installed it with Gdebi. I started the application from the terminal and accepted the 'User Agreement'. Skype then tried to log me on, and I got the following error and the app closed:
I am running Squeeze on an older Compaq EVO laptop with radeon graphics.
A few months ago, after an upgrade, suspend and hibernate stopped working. The suspend or hibernate worked fine, but the resume just hung with a black screen. I finally got around to looking into it and found a workaround.
The workaround is to disable Kernel Mode Setting for the radeon. This can be done by adding the boot parameter "radeon.modeset=0" or by editing /etc/modprobe.d/radeon-kms.conf so that it includes the line "options radeon modeset=0".
If you are interested in the details, you can search for problem reports related to radeon kernel mode setting.
I'm in need of a bit of assistance from you Debian users. I have two servers that I thought were identical installations, both running Debian Lenny. Tonight I started the upgrade to Squeeze on both servers and one of them went smooth. The other one started out good but fails on the postconfiguration of openssh-server. I'm getting the following message:
It looks like there's an error in one of the files in openssh-server that prohibits it from installing correctly. However on the other server it all went well.
the mcr85+1 packages were built using qt 4.6.3, so will be squeeze-compatible. umplayer is a fork of the abandoned smplayer project which adds skinning, shoutcast stream, and minitube-like videos search, playback, and download capability to the program.
[url]
i did a pull and build from the svn repo, since that is newer than the 0.92 debs on the website and solves some videos issues. debianized sources included so one can build the program on any architecture that supports qt 4 4.6 and mplayer...plus it's a good idea not to trust anybody's binaries off the web, so to be really safe, rebuild the program yourself if you don't know who the heck i am. update 20 april 2011: link to svn 143 builds and sources: [url] update: 25 june 2011: new pull from svn--fixes the returning control bar problem with skins and kde 4 kwin desktop effects enabled:
[url]
squeeze users should use the mcr85 packages, the mcr110 ones need qt 4.7. sources included as usual. it looks like it would be a nice addition to the debian repo...
I'm trying to install Debian Squeeze (net install CD) on a PC with an EX100 wireless keyboard and mouse. The system starts the install without any problem, and the keyboard works up to the first blue menu on the Debian installer then stops - the system fails to respond to any key presses.
The mainboard of the system is an Asus M2N68-AM SE2, keyboard / mouse receiver is plugged into one of the USB ports on the back. I've had a look through the BIOS, there seems to be no option relating to the keyboard. Changing the PnP O/S option seems to make no difference. I've managed to install Ubuntu without problem on this system so I know the PC and keyboard are working fine.
After upgrading to Jessie (AMD64) I have a totally blank screen, not even a blinking cursor. The video card is a GeForce 6200 and I have nouveau loaded. I originally had an nvidia module in Wheezy. I decided to use the instructions at the Debian NvidiaGraphicsDriver wiki to install the NVIDIA legacy package. That was worse. The nvidia module was unloaded in the X.org log, and the screen presented as a login console.
I tediously removed all NVIDIA components, and reverted to nouveau since its report in X.org log says it supports GeForce 6 series cards. That brought me back to a totally blank screen. The nouveau module lists as "video" doing lsmod. Both gdm3 and the X server processes are up and running. Other than reporting that "nv" couldn't be loaded, there is nothing in X.org log that appear abnormal. The .xsessions_error log is troubling however, but I don't have the knowledge to interpret.
My university is checking LAN access through F5 Firepass server. Using amd 64 proc with squeeze and iceweasel 3.5.16 browser with F5 Network access plugin and F5 sam inspection host plugin, I cannot access university servers through the F5 firepass server.
Going through the forums I read a post, where it was told to rebuild a package... But unfortunately, I didnt understand a thing which was mentioned in the building rpm tutorail that I reffered... The replacement to that package which was mentioned in the same post was unavailable.
