Andrei Verovski (aka MacGuru) wrote:
On Sunday 22 March 2009 10:29:29 pm Fred A. Miller wrote:
It's happened more than once......same results.....NO desktop, no GUI login. Most often, it's been with a system using nVidia, but can and will happen with other video.......but not as often.
How you cured that ?
I couldn't. The first time it happened, I did try to fix it, spending an hour or so at it. No matter what I reinstalled, I wasn't able to get "X" to start correctly. I finally just reinstalled from DVD and have had to do that every time this foolishness has happened, which is 3 times now over the past couple of months. MOST often, the system has a nVidia video chipset so I think there's a connection there. I've read all of the logs without finding any clue as to what foul play has occurred. To say I've been unhappy about it, is being as kind as I can possibly be. ;) I'd use the GNU driver except it's so bad that I can't tolerate using it. Fred -- "The fundamental premise of liberalism is the moral and rational incapacity of the American people." ~ Fred Miller -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 22 March 2009 11:05:28 pm Fred A. Miller wrote:
I couldn't. The first time it happened, I did try to fix it, spending an hour or so at it. No matter what I reinstalled, I wasn't able to get "X" to start correctly. I finally just reinstalled from DVD and have had to do that every time this foolishness has happened, which is 3 times now over the past couple of months. MOST often, the system has a nVidia video chipset so I think there's a connection there. I've read all of the logs without finding any clue as to what foul play has occurred. To say I've been unhappy about it, is being as kind as I can possibly be. ;) I'd use the GNU driver except it's so bad that I can't tolerate using it.
Yes, NO CLUE in the logs! Only message could not open or move log file "/var/log/x..org.xxx". As i said in one of my previous posts, I reinstalled X.org from DVD, downgraded MESA and reinstalled nvidia driver. AND RESTART. Without restart x.org did not start and vice versa. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 22 March 2009 10:41:50 pm Andrei Verovski (aka MacGuru) wrote:
Yes, NO CLUE in the logs! Only message could not open or move log file "/var/log/x..org.xxx".
The reason is that your X server lost its suid bit. "Why?" is the big one. Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Johansson wrote:
On Sunday 22 March 2009 10:41:50 pm Andrei Verovski (aka MacGuru) wrote:
Yes, NO CLUE in the logs! Only message could not open or move log file "/var/log/x..org.xxx".
The reason is that your X server lost its suid bit. "Why?" is the big one.
Ok.....I'll accept that as the reason. How should be correct that from command line, and which file(s)? Thanks, Fred -- The problem with socialism is that you eventually run out of other people's money. - Margaret Thatcher -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 22 March 2009 11:49:48 pm Fred A. Miller wrote:
Anders Johansson wrote:
On Sunday 22 March 2009 10:41:50 pm Andrei Verovski (aka MacGuru) wrote:
Yes, NO CLUE in the logs! Only message could not open or move log file "/var/log/x..org.xxx".
The reason is that your X server lost its suid bit. "Why?" is the big one.
Ok.....I'll accept that as the reason. How should be correct that from command line, and which file(s)?
Since I haven't actually seen the problem first hand, I can't say for certain. It could be as simple as chmod 4711 /usr/bin/X Since a reinstall helped Andrei, I have to assume that the cause of it is a broken X server package installed from some repository in the build service. Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Johansson wrote:
On Sunday 22 March 2009 11:49:48 pm Fred A. Miller wrote:
Anders Johansson wrote:
On Sunday 22 March 2009 10:41:50 pm Andrei Verovski (aka MacGuru) wrote:
Yes, NO CLUE in the logs! Only message could not open or move log file "/var/log/x..org.xxx". The reason is that your X server lost its suid bit. "Why?" is the big one. Ok.....I'll accept that as the reason. How should be correct that from command line, and which file(s)?
Since I haven't actually seen the problem first hand, I can't say for certain. It could be as simple as
chmod 4711 /usr/bin/X
Since a reinstall helped Andrei, I have to assume that the cause of it is a broken X server package installed from some repository in the build service.
That is logical. 'Hope someone gets it fixed ASAP! Thanks Anders, Fred -- The problem with socialism is that you eventually run out of other people's money. - Margaret Thatcher -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 22 Mar 2009 20:45:18 -0400, you wrote:
Since a reinstall helped Andrei, I have to assume that the cause of it is a broken X server package installed from some repository in the build service.
That is logical. 'Hope someone gets it fixed ASAP!
If nobody files a bug against the BS package it's not likely going to be fixed. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 22 March 2009 11:44:37 pm Anders Johansson wrote:
On Sunday 22 March 2009 10:41:50 pm Andrei Verovski (aka MacGuru) wrote:
Yes, NO CLUE in the logs! Only message could not open or move log file "/var/log/x..org.xxx".
The reason is that your X server lost its suid bit. "Why?" is the big one.
Anders
For the sake of experimental science I have run this update again (latest
x.org X64 RPMs from update repository, not factory builds).
SuSEconfig throws the following:
--------------------------------------------------------------------------
Executing /sbin/conf.d/SuSEconfig.permissions...
Checking permissions and ownerships - using the permissions files
/etc/permissions
/etc/permissions.easy
/etc/permissions.d/mail-server
/etc/permissions.d/postfix
/etc/permissions.local
setting /usr/bin/Xorg to root:root 4711. (wrong permissions 0711)
/usr/bin/Xorg: will not give away s-bits on an insecure path
setting /usr/bin/wall to root:tty 2755. (wrong permissions 0755)
/usr/bin/wall: will not give away s-bits on an insecure path
setting /usr/bin/write to root:tty 2755. (wrong permissions 0755)
/usr/bin/write: will not give away s-bits on an insecure path
setting /usr/bin/fileshareset to root:root 4755. (wrong permissions 0755)
/usr/bin/fileshareset: will not give away s-bits on an insecure path
ERROR: not all operations were successful.
--------------------------------------------------------------------------
I have corrected "/usr/bin/Xorg" and tried to solve another problem - diying
network startup (when system boots) which appeared after this unfortunate
update. I had suspected "waitmd" service, and disabled it. System hanged at
startup trying to start eth1.
I am was in Catch 22 mode - I did not remember how to abort frozen startup
script, and could not google for solution because PC was not working
properly.
I have "updated" system from install DVD, run again update without skipping
new X.org files in repository, almost everything is fine, except
auto-mounting. neither CD neither external USB storage could be automounted
(with error message "hal-storage-mount-removable no <-- (action, result)),
only from console as root, kinda awkaward.
Googling revealed 2 solutions:
1) /usr/share/PolicyKit/policy/org.freedesktop.hal.storage.policy
----->
<action id="org.freedesktop.hal.storage.mount-removable">
<description>Mount file systems from external drives.</description>
<message>System policy prevents mounting external media</message>
<defaults>
On Tuesday 24 March 2009 00:15:34 Andrei Verovski (aka MacGuru) wrote:
setting /usr/bin/Xorg to root:root 4711. (wrong permissions 0711) /usr/bin/Xorg: will not give away s-bits on an insecure path setting /usr/bin/wall to root:tty 2755. (wrong permissions 0755) /usr/bin/wall: will not give away s-bits on an insecure path setting /usr/bin/write to root:tty 2755. (wrong permissions 0755) /usr/bin/write: will not give away s-bits on an insecure path setting /usr/bin/fileshareset to root:root 4755. (wrong permissions 0755) /usr/bin/fileshareset: will not give away s-bits on an insecure path ERROR: not all operations were successful.
Oopla, so it isn't a problem with the X update. It looks like you have bad write permissions on /usr/bin, which is why chkstat won't add the suid bit What has happened to /usr/bin on your machine? Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 24 March 2009 09:13:06 am Anders Johansson wrote:
Oopla, so it isn't a problem with the X update. It looks like you have bad write permissions on /usr/bin, which is why chkstat won't add the suid bit
What has happened to /usr/bin on your machine?
I have no idea. aaa_base was upgraded, too. May be it comes with it ? My SUSE workstation was absolutely fine before this upgrade. Updates were from official SuSE update repo, packman, and KDE 4.2 factory. BTW, what should be correct permissions for /usr/bin ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 24 March 2009 09:26:30 Andrei Verovski (aka MacGuru) wrote:
On Tuesday 24 March 2009 09:13:06 am Anders Johansson wrote:
Oopla, so it isn't a problem with the X update. It looks like you have bad write permissions on /usr/bin, which is why chkstat won't add the suid bit
What has happened to /usr/bin on your machine?
I have no idea. aaa_base was upgraded, too. May be it comes with it ?
My SUSE workstation was absolutely fine before this upgrade. Updates were from official SuSE update repo, packman, and KDE 4.2 factory.
BTW, what should be correct permissions for /usr/bin ?
755, or drwxr-xr-x It could also be the permissions on /usr itself, since chkstat checks the whole path before setting the suid bit Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 24 March 2009 10:26:20 am Anders Johansson wrote:
755, or drwxr-xr-x Oh, and it should be owned by user root, group root
Permissions were OK, but owner/group for whatever reason NOT for /usr/bin and usr/share. I changed both to root/root. I have no clue how they could be reset, I even had no freezes or crashes before. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 24 March 2009 13:47:31 Andrei Verovski (aka MacGuru) wrote:
On Tuesday 24 March 2009 10:26:20 am Anders Johansson wrote:
755, or drwxr-xr-x Oh, and it should be owned by user root, group root
Permissions were OK, but owner/group for whatever reason NOT for /usr/bin and usr/share. I changed both to root/root.
I have no clue how they could be reset, I even had no freezes or crashes before.
What was the owner then? Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 24 March 2009 02:48:12 pm Anders Johansson wrote:
What was the owner then?
andrei/users very strange, I did not hacked anything there. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 24 March 2009 09:26:30 Andrei Verovski (aka MacGuru) wrote:
On Tuesday 24 March 2009 09:13:06 am Anders Johansson wrote:
Oopla, so it isn't a problem with the X update. It looks like you have bad write permissions on /usr/bin, which is why chkstat won't add the suid bit
What has happened to /usr/bin on your machine?
I have no idea. aaa_base was upgraded, too. May be it comes with it ?
My SUSE workstation was absolutely fine before this upgrade. Updates were from official SuSE update repo, packman, and KDE 4.2 factory.
BTW, what should be correct permissions for /usr/bin ?
Oh, and it should be owned by user root, group root Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Mar 24, 2009 at 08:13:06AM +0100, Anders Johansson wrote:
On Tuesday 24 March 2009 00:15:34 Andrei Verovski (aka MacGuru) wrote:
setting /usr/bin/Xorg to root:root 4711. (wrong permissions 0711) /usr/bin/Xorg: will not give away s-bits on an insecure path setting /usr/bin/wall to root:tty 2755. (wrong permissions 0755) /usr/bin/wall: will not give away s-bits on an insecure path setting /usr/bin/write to root:tty 2755. (wrong permissions 0755) /usr/bin/write: will not give away s-bits on an insecure path setting /usr/bin/fileshareset to root:root 4755. (wrong permissions 0755) /usr/bin/fileshareset: will not give away s-bits on an insecure path ERROR: not all operations were successful.
Oopla, so it isn't a problem with the X update. It looks like you have bad write permissions on /usr/bin, which is why chkstat won't add the suid bit
What has happened to /usr/bin on your machine?
It might be a symlink or something. ls -l / |grep usr ls -l /usr | grep bin Ciao, marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Anders Johansson -
Andrei Verovski (aka MacGuru) -
Fred A. Miller -
Marcus Meissner -
Philipp Thomas