OpenSUSE Install :: All Login / Su Attempts Fail After Applying Su Update Patch (11.2 / X86_64)
Mar 16, 2010
Yesterday I applied the su security patch to my openSuSE 11.2 x86_64 system.After applying the patch, any attempt at su failed, and after rebooting the system earlier this morning any login (root, user, otherwise) fails with a "Permission Denied".Is it possible that the su update somehow messed up my (standard) pam settings?
The problem is that Ubuntu 10.04 as delivered is not compatible with the Nvidia driver installed with 10.04. This problem is widely reported, as is a fix for it. The usual form of the fix is as follows:
To fix the above error message use the following procedure 1) Download Newest Nvidia drivers from here 2) Open module blacklist as admin gksudo gedit /etc/modprobe.d/blacklist.conf
After applying an update about two or three days ago, I restarted my system and now I'm getting a black screen at login. I can hear the brief drum sound clip that plays when the login dialog box pops up, but the screen is completely black and I can't see anything. I'm still able to access low graphics mode via the fail-safe option in the recovery mode menu. So far I've tried the following commands in the terminal:
In RHEL there is a problema with ACL as can be read in: [URL]
I've downloaded the patch from "Attachments". I try to apply the patch, but I receive this error:
usr/src # patch -p0 < aclPatch.txt can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option?
The text leading up to this was: -------------------------- |diff -uNr acl-2.2.3.org/libacl/acl_get_file.c acl-2.2.3/libacl/acl_get_file.c |--- acl-2.2.3.org/libacl/acl_get_file.c 2002-09-05 08:19:54.000000000 +0900 |+++ acl-2.2.3/libacl/acl_get_file.c 2004-08-25 12:49:58.000000000 +0900 -------------------------- File to patch: ========================================================
I get following error during automatic patch upgrade of my SuSE 11.2 to latest path revision. I assume it is due to the KDE 4.3.5 Update part of the patch set: compiz-kde4-0.7.8-9.14.x86_64 requires libkdecorations.so.4()(64 bit) but there are no providers. The package manager suggest to replace compiz-kde4-0.7.8-9.14.x86_64 with kwin-4.3.5-0.2.1.x86_64 but I don't want to loose compiz-kde. which repository I must add to resolve the dependency.
I've just install SUSE 11.3. GNOME and KDE are selected as GUI session.At the login screen, in Session list I saw TWM, and after selected it as login session I couldnt login, and login screen disappear as well. It shows a black screen and the mouse pointer, and I have no idea how to switch to KDE or GNOME since no login screen.
Recently I upgraded my kernel to 126.96.36.199-47.fc13.x86_64 and then also did an update to 188.8.131.52-47.fc13.x86_64. Both of these kernels I do not get a login dialogue box. I still have the one kernel that works and it is 184.108.40.206-149.fc13.x86_64. The system I am on has a Radeon graphics card, but I don't think the graphics card is the issue since I get the login screen's background, but not the login screen itself. <Later> After messing around with this for a while I came to the conclusion that livna-config-display was messing with the xorg.conf file. Removed it and things seem to be working fine now.
When attempting to install FC12 x86_64 on a Dell Optiplex 760, my USB devices stop working after initial boot. I see anaconda, but am unable to change anything since my keyboard, mouse and any other USB devices are not powering up after kernel boot.
Somehow an app on this box seems to have disappeared long ago which was configured to start immediatedly with a root login (eg su). Now, whenever upgrading permissions to root or logging (and assuming login as root), an error displays saying "cannot find <application>"
Considering root usually is different than other logins, am not sure where to start looking on an OpenSuSE box. I've tried without success
BASH -v to enable verbose mode before executing a "su." BASH --debugger to enable debugging mode before executing a "su."
Logout, Login as root and inspect /var/log/ hoping to find some logfile that audits the login sequence, but may be looking at a wrong logfile.
For about a week now I've been seeing mass attempts to relay through postfix and login to dovecot from the same 2 addresses, none are successful due to how postfix/dovecot are configured and I wouldn't be overly worried but my isp have picked up on it and are nagging at me
What ways do people go about just dropping connection attempts from offending addresses/ranges when stuff like that happens? An ideal thing would be something that detects repeated failed attempts from a host or range and subsequently ignore/ban them, perhaps for a specified length of time, something along the lines of denyhosts and fail2ban for ssh would be great Don't know if there's anything out there or just a plain tried and trusted method anyone might use for stuff like this, if not a hint on the most appropriate way to go about it 'manually' would do
I'm trying to install a patch but when I copy it into terminal I get message " /home/john/patch-modules_v62-opensuse.sh 'vmware-7.1.3-2.6.37-rc5.patch' not found. copy it to the current '/home/john' directory. Exiting" But I have it in my home directory!
My system is trying to install security update, but I get the following message: A package could not that allows the task to complete. Details are as follows: patch:libfreebl3-2258.noarch conflicts with libfreebl3-32bit.x86_64 < 3.12.6-3.1.1 provided by libfreebl3-32bit-3.12.6-2.pm.6.2.x86_64
In my update tray applet I often get a notification saying an update for my system is available and when I click for details the only patch listed is dummy Patch. Anyone know what or why this is? It's happening on my 11.1 and 11.2 machines.
I have been running 11.4 now for quite a while. I installed maintenance to it trough Yast's Online update and now can't boot except through the failsafe mode of GRUB. How can I pinpoint where the failure is?
I am whittling down my list of available YAST Online Updates for OpenSUSE 10.3. Most of the few remaining updates will not install because of an endless error list like this (xmessage on cancel):(gtk:4929): GLib-GObject-WARNING **: invalid cast from `GtkTextView' to `YGtkRichText'** (gtk:4929): WARNING **: Unknown tag 'p'
If someone, like me, updated the shipped kde 4.6 to 4.6.1. using the repo KDE46/11.4 only to find himself stuck at the login screen, try this: From the "type of session" choose "Kde plasma workspace (failsafe session)" and try to login. Once logged in, logout, then choose "Kde plasma workspace" type of session and login again.
I don't know if it's just my system, but after applying the latest Wine update, the mouse cursor in Wine windows is now purple/magenta/pink, whatever. Not a big problem, just annoying. I've looked through the various config files in ~home and /usr/share/wine, and can't find any parameter that might even remotely address this.
When I run the YAST Online Update OR Software Management OR Zypper, the Updates (or install of new software) fails when the download of the Delta RPM reaches 98%. I have added ALL of the community repositories and have Imported the appropriate certificates. When watching the DeltaRPM or normal RPM download, it starts the download at approx. 4Mbs/sec until it reaches 98% of file downloaded. Then, the speed drops to 0 B/sec and the file download fails. This then prompts a Retry which again fails when it reaches approx 98% download.
It does not matter if I am doing an Online Update, Doing a Software Management (to install new software) or using Zypper in a Terminal session, the result is the same. I have even gone so far as to connect the machine DIRECTLY to the internet, bypassing all firewalls so as to ensure it is not a firewall issue.
When I run the YAST Online Update OR Software Management OR Zypper, the Updates (or install of new software) fails when the download of the Delta RPM reaches 98%. I have added ALL of the community repositories and have Imported the appropriate certificates. When watching the DeltaRPM or normal RPM download, it starts the download at approx. 4Mbs/sec until it reaches 98% of file downloaded. Then, the speed drops to 0 B/sec and the file download fails. This then prompts a Retry which again fails when it reaches approx 98% download. It does not matter if I am doing an Online Update, Doing a Software Management (to install new software) or using Zypper in a Terminal session, the result is the same.
I have even gone so far as to connect the machine DIRECTLY to the internet, bypassing all firewalls so as to ensure it is not a firewall
OK, I'm not really a newbie, but I definitely no expert either.I've been surfing the web trying to find a good tutorial on locking out users after three failed logon attempts.At present I've reset everything in the /etc/pam.d directory back to the default state. This sets up all my password requirements and this works. Now I need to crack getting the account to lockout after three failed attempts. Let me know what files you need to see in the pam.d directory and I'll paste them in.
i've installed opensuse 11.3 x86_64 and everything works great. after install updates and restart i cannot access internet from wireless connection. Knetworkmanager says it is connected, i have a dhcp ip, gateway, and cannot access internet.... i tried to configure from yast and cannot access internet...
This is just a nit, but I have noticed that whenever the kernel is updated, the background picture that I have set up for the login screen seems to be reset to "default_blue". No other setting seems to be disturbed.
After each update, I have to go into Configure Desktop->Login manager and set my background picture again. Why is this happening? Is there a way to fix this?
After applying some updates to F11, I was unable to login. After putting the username and password in, the dialog would go away and it would appear that the window manager was trying to load. Somewhere in the process the mouse and keyboard stops responding. The HD activity lights flashes for quite a while but later goes out.
Hoping that F12 would help, I upgraded. The upgrade went well but the problem still exists.
I tried applying an emerald theme yesterday, and when I did, it somehow affected the login screen, now it looks old and crappy like win98. I tried disabling emerald and even uninstalling it, but the login screen remains crappy, how do I get it back to the way it was?
How do I limit the max login attempts in the sshd_config file? I found a way to do it on Google some time back but I can't find it now. I have Denyhost already, but I really wanna do the "MAx Login Attempts" what ever it was that I was able to do in the config file.