I was trying to set up my Xfce desktop on a fresh install.
I personally dislike Xdm, which is given as the default login manager, and would prefer to use Slim instead.
It is possible to install it using the Package Search feature (it's listed under the Contrib repository), but I haven't been able to set it as the default login manager (I wasn't able to find such a setting in /etc/sysconfig).
yesterday i installed slim login manager on my computer (eee pc 1018p, ubuntu 11.04), and now it cannot get passed the ubuntu loading screen (with orange dots underneath) when booting. i tried booting into recovery mode and that didn't work either. i also left the computer trying to boot overnight and that didn't work. basically, during this loading screen that should eventually bring you to the login screen, i can alt+tab to see the progress of the load. the progress is stuck on
Is there anything I can do from grub to remove slim?or, is there any way I can access my ubuntu partition and save all my files?
I had Slim working with the latest -Current updates, but that was with a package I built before updating.
I borked my system yesterday and had to do a fresh install. Now I can't get Slim working.
I tried running the Slim SlackBuild from Slackbuilds.org, and it failed without giving any errors. I figured out that the problem was with this section:
Code:
The strip commands were failing and caused the SlackBuild to exit, so I added '|| true' to them.
Code:
Not sure why this is needed in -Current and not 13, maybe because of Bash 4.1?
Anyway, now the package builds successfully, but Slim won't start. My system just hangs at a black screen after 'Starting up X11 session manager'...Has anybody been able to get Slim working in -Current?
I have created a custom linux distro originating from the ubuntu server edition and have slim as the login manager, and openbox as the window manager. When it goes into power save mode and turns off the monitor and I move the mouse to wake it up it just goes to the shell with a mouse cursor on it. How can I get it to go right back to the openbox window manager?
I'm having a rather peculiar problem booting into openSUSE 11.2. After the installation (which goes fine), i get a black screen and my system freezes.
In detail, I can see the splash screen and booting details, but at the moment I am supposed to see a login manager, i just get a black screen. Sometimes it has a cursor indicator in the top left, sometimes it doesn't. Same thing happens in failsafe mode too.
This happens over and over, no matter which installation type I choose, 32bit or 64bit, KDE/Gnome/XFCE.
My problematic box is: AMD Athlon 3200+ 64bit 2GB DDR ATI Radeon x1950pro <-- which I believe might be causing all these issues.
So, upgraded and then installed slim b/c I wanted to have a nice login screen but now when logging in all I get is the background, no menu no panels no nothing, had to manually create a shortcut to firefox to get help, anyone know how to manually start the menu and/or how to fix.
openSUSE 11.3 with KDE 4.4.4 release 2.I can change the desktop theme and the splash theme, but I can not change the KDM login manager theme.First, I changed th setting /etc/sysconfig/displaymanager DISPLAYMANAGER_KDM_THEME from suse to nothing in Yast -> /etc/sysconfig editor in order to get rid of the ugly Suse login theme.That resulted in having the traditional KDM login theme with the clock.I go to Personal Settings -> Advanced tab -> System: Login Manager (I enter the root password).In tab "General" I checked "Use themed greeter". Gui style and color scheme are set to default.In tab "Theme" I select a theme, click apply, then clikc ok.I log out and log in again. Nothing has changed. I still have the oldstyle KDM login theme.
I downloaded a theme from gnomeart, and in the readme it tells me to use "gdmsetup" to install it - however, when I try typing "gdmsetup" in the console, it says "command not found". How would I go about installing the theme?
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 am having a boot problem with opensuse.i installed a theme named suse-elegant under personal settings(configure desktop)-system administration-login screen.
i had also added vbox users(i ticked vboxusers) under yast-security and users-user and group management-edit-details to make virtual box work.
i want to check that installed theme so i restarted my laptop.after the restart opensuse taking too long time to boot
note:the login theme also not working.
after the boot i restored defaults in login screen themes.it is also not working.
i don't know which cause this problem(vboxusers or login theme).i am also seeing a root user has been added in my login area.i tried opensuse failsafe also.
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)?
when i login to openSUSE a window named login keyring appears and it asks me root password. it happens everytime when i login. how to fix this problem?
I've recently switch to Arch with Lxde, and I'm looking for a login manager. I want this to support a "guest" account, a user that can be logged on passwordlessly, but not just auto-login. I don't really want to use kdm or gdm, either.
I had my motherboard fail and had to do a replacement. The motherboard I got has a feature (I don't think I can shut off) that lets you select what drive you want to boot off of. I have XP installed on the first drive and openSUSE 11.1 on the second drive. I am running openSUSE 11.2 with KDE 3.5 and I simply dropped my drives onto this new motherboard. I can boot up (Linux) just fine but am having other issues with my mouse. I am thinking of Updating to openSUSE 11.2 and the current KDE version.
Should I just update to 11.2 or do a new install. I have LOTS of data in my home directory I really don't want to lose and have a partition for data as well that is pretty full. I don't want to lose this stuff. What should I do about Grub with this BIOS that lets you pick which drive to boot off of? Put Grub in the MBR of the drive with openSUSE on it and nuke the MBR of the XP drive?
After I install 11.2 clean from the ISO, I would like to update ONLY knetworkmanager, and not all of KDE. I would like to use zypper commands similar to the one below, which work for KDE. However, I would like the syntax for only knetwork manager and not all of KDE sample for KDE:
# please let me have the correct commands for # ONLY updating Knetworkmanager # These work fine, but I don't want to update all # of KDE. I only want to update knetworkmanager [Code]...
I have installed VirtualBox and setup a Windows Vista host, initially with a .vdi of 10gb. That filled up quickly, so I added another 20gb secondary partition, after first trying to allocate a .vdi to a SCSI controller. Configured the drive in Windows (Computer Management), and all seemed ok. I shutdown VB, and rebooted my Linux host (openSuse 11.3). Now I keep bouncing back to the login screen, and can't login to Linux KDE, but can login to a console.I do have the following info:
I did see a message before, that I don't see anymore, that said it could not start NFS services due to missing entry in fstab. Another I'm seeing now is it couldn't start the avahi-daemon, no space left on device. This is odd, since I have a 200GB drive, with half of it left, only max 30GB set to VB. Here's my df -k output:
/dev/sda6 Use% is 100% devtmpfs Use% is 1% tmpfs Use% is 1% /dev/sda7 Use% is 46%
So root "/" is mounted on /dev/sda6, which looks like it could be a problem, but why would this suddenly be a problem after working with VirtualBox? Could this be a matter of just freeing up space on /dev/sda6? Like the /tmp folder that's under "/"?
installation opensuse 11.3 and kde 4.4 after update to kde 4.6, work fine, but problem is login screen is low like 640x350...? i wanted to change from lowtion to high 1024x768?when i start opensuse and begin to login was low resolution and log in my user and it's low resolutiona dn i change screen from setting system (kde) after change high display is works fine and rebbot same low resolution for LOGIN MANAGER how i can change it??
I try to install two window manager under openSUSE 11.4 x64. AmiWb and WindowLab. I compiled them and there were no errors, but they don't show up in the login menu. If i start them by switching ALT-F2 i can't connect to the xserver. As far as i can see, it is not in USR/X11 either. Have to check where it ended up in. But in my previous experience in installing a WM i did not have any problems.
Just installed 11.2 on my Thinkpad T61 and during install the mouse pointer (synaptics) works fine but not the mouse buttons. After the install on every first login the pointer works but not the buttons. If I restart the gui and try to login into gnome again then all works agin. But it always fails on the first login and gnome sessions
when i login, Ubuntu asks to install 3D Drivers for my grapics card. Can i make a script in openSUSE to do this as well? Or even better, check for drivers on startup and then install the drivers for the graphics card on boot.
It appears that my keyring manager has gone on strike. I did a "zupper up" today and ever since doing that, the computer has not asked me to enter my default keyring password when booting up. The only way for me to connect to my wireless is to enter the WPA security code every time and when loading Pidgin I have to enter all my passwords. This is very annoying!!!! I have deleted my default.keyring file, restarted and it is not asking me to enter a new password.