[opensuse] root login not allowed from kdm
A user has fiddled with a system so that root logins are not allowed from kdm. I can ssh in as root, and su to root. But not a graphic login. I get a window that says "Root logins are not allowed." So, I looked in the display manager settings, being sure that these items are set as follows: PERMISSION_SECURITY="easy local" DISPLAYMANAGER_REMOTE_ACCESS="yes" DISPLAYMANAGER_ROOT_LOGIN_REMOTE="yes" It makes no difference. I have no idea what else they may have changed. I edited the values in YaSt, just to be sure. I even restarted the display manager (rckdm restart). What else is controlling this? The system is openSUSE 11.2, running KDE 4.5.2 -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2010-10-13 at 15:07 +0200, Roger Oberholtzer wrote:
What else is controlling this?
The system is openSUSE 11.2, running KDE 4.5.2
View this thread: http://forums.opensuse.org/showthread.php?t=446115 - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky1sTQACgkQtTMYHG2NR9X3JgCfSlGpLbztNIw9sq40k8/g98a1 7vsAn29xwI3RTrRgwLTTZsU+oziOg720 =GHJ2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2010-10-13 at 15:16 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2010-10-13 at 15:07 +0200, Roger Oberholtzer wrote:
What else is controlling this?
The system is openSUSE 11.2, running KDE 4.5.2
View this thread: http://forums.opensuse.org/showthread.php?t=446115
Seesh... I know all the issues with doing this as root. However, I am trying to sort out a very long standing issue wherein the desktop renders properly for root, but not for any other user. Unreadable black text on a black background in panels, pop-up windows, etc. It is not a 'make it pretty' issue. It is a 'make is possible to use' issue that has now reached a head. It happens on a number of machines here (different hardware) - and I have no clue why. It is really odd in that we seem to be the only ones in the world with the issue. Which I find soo odd in that different people have done the installs from different media in different cities on different hardware. But the problem occurs most of the time. I want to test a theory as to what might be different between root and others. (Permissions have been explored to death - no joy.) But I need to log in graphically as root to test it. Perhaps trwing xdm just to get the login may help.
- -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux)
iEYEARECAAYFAky1sTQACgkQtTMYHG2NR9X3JgCfSlGpLbztNIw9sq40k8/g98a1 7vsAn29xwI3RTrRgwLTTZsU+oziOg720 =GHJ2 -----END PGP SIGNATURE-----
-- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2010-10-13 at 15:27 +0200, Roger Oberholtzer wrote:
Perhaps trwing xdm just to get the login may help.
As the Fixx said, one thing leads to another... I need to log in remotely (x11vnc). This works great with kdm. Seems not to work with xdm or gdm. I see they are running. But I cannot connect via vncviewer. Sigh. I have limited access to the machines. I did not expect to have to fight with this... -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2010-10-13 at 15:27 +0200, Roger Oberholtzer wrote:
View this thread: http://forums.opensuse.org/showthread.php?t=446115
Seesh...
I know all the issues with doing this as root. However, I am trying to
Wait, read the thread entirely. We found how exactly to solve this, it is a new feature of 4.5.1. A new variable in sysconfig. I just don't have the link to the exact post, I access via NNTP. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky1ufAACgkQtTMYHG2NR9U5JgCeJKhM7BZ2/zSTuWUmV/IzcZNc oQoAn1icCADiNlvaRR/sXzOEvOatTOjS =VuAh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2010-10-13 at 15:53 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2010-10-13 at 15:27 +0200, Roger Oberholtzer wrote:
View this thread: http://forums.opensuse.org/showthread.php?t=446115
Seesh...
I know all the issues with doing this as root. However, I am trying to
Wait, read the thread entirely. We found how exactly to solve this, it is a new feature of 4.5.1. A new variable in sysconfig.
I just don't have the link to the exact post, I access via NNTP.
I think it was the suggestion to use xdm instead of kdm. As I wrote in another messages in this thread, this did not work in my setup. Or was there another solution I missed (please say yes...)?
- -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux)
iEYEARECAAYFAky1ufAACgkQtTMYHG2NR9U5JgCeJKhM7BZ2/zSTuWUmV/IzcZNc oQoAn1icCADiNlvaRR/sXzOEvOatTOjS =VuAh -----END PGP SIGNATURE-----
-- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2010-10-13 at 16:00 +0200, Roger Oberholtzer wrote:
On Wed, 2010-10-13 at 15:53 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2010-10-13 at 15:27 +0200, Roger Oberholtzer wrote:
View this thread: http://forums.opensuse.org/showthread.php?t=446115
Seesh...
I know all the issues with doing this as root. However, I am trying to
Wait, read the thread entirely. We found how exactly to solve this, it is a new feature of 4.5.1. A new variable in sysconfig.
I just don't have the link to the exact post, I access via NNTP.
I think it was the suggestion to use xdm instead of kdm. As I wrote in another messages in this thread, this did not work in my setup.
Or was there another solution I missed (please say yes...)?
I missed the extra pages! The solution is to add DISPLAYMANAGER_ROOT_LOGIN_LOCAL="yes" to /etc/sysconfig/displaymanager Now I can destroy my system from the comfort of my favorite GUI. And, more importantly, test a rendering issue.
- -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux)
iEYEARECAAYFAky1ufAACgkQtTMYHG2NR9U5JgCeJKhM7BZ2/zSTuWUmV/IzcZNc oQoAn1icCADiNlvaRR/sXzOEvOatTOjS =VuAh -----END PGP SIGNATURE-----
-- Roger Oberholtzer
OPQ Systems / Ramböll RST
Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden
Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696
-- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2010-10-13 at 16:10 +0200, Roger Oberholtzer wrote:
On Wed, 2010-10-13 at 15:53 +0200, Carlos E. R. wrote:
I just don't have the link to the exact post, I access via NNTP.
I think it was the suggestion to use xdm instead of kdm. As I wrote in another messages in this thread, this did not work in my setup.
Not that one.
Or was there another solution I missed (please say yes...)?
Yes :-)
I missed the extra pages! The solution is to add
DISPLAYMANAGER_ROOT_LOGIN_LOCAL="yes"
to /etc/sysconfig/displaymanager
That one!
Now I can destroy my system from the comfort of my favorite GUI.
Enjoy. Glad it worked :-)
And, more importantly, test a rendering issue.
Ok. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky1xnMACgkQtTMYHG2NR9V13wCgjzeuI1PucNdgQF4w6+fBNv5q 4OkAmwfghg5yBAFncu9DmhPIwTi1SIM2 =pe+z -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2010-10-13 at 16:47 +0200, Carlos E. R. wrote:
Enjoy. Glad it worked :-)
Too bad my theory on why I have a slew of different machines that render badly for non-root users of KDE, yet render correctly for root remains. I am at a loss. And have a slew of upset users. William Stephenson was helping me with suggestions. But no solution has been found. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
Too bad my theory on why I have a slew of different machines that render badly for non-root users of KDE, yet render correctly for root remains. I am at a loss. And have a slew of upset users. William Stephenson was helping me with suggestions. But no solution has been found.
At one place I worked, we had a teddy bear that did the debugging for us. When you had a difficult bug, you sat the teddy where he could see both you and the screen and then explained to him exactly what was happening and why all the hypothetical explanations failed. He usually solved the problems quite quickly, just by staring at you intensely at the right moment. You could try explaining it all to us in excruciating detail if you like ... Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2010-10-13 at 16:40 +0100, Dave Howorth wrote: El 2010-10-13 a las 16:40 +0100, Dave Howorth escribió:
At one place I worked, we had a teddy bear that did the debugging for us. When you had a difficult bug, you sat the teddy where he could see both you and the screen and then explained to him exactly what was happening and why all the hypothetical explanations failed. He usually solved the problems quite quickly, just by staring at you intensely at the right moment.
You could try explaining it all to us in excruciating detail if you like ...
ROTFL! X'-) And then you put teddy in front of the screen for inspiration, eh? That's unfair on us, we don't have such a good helper. I have solved a few problems just by typing a question to post here. By the time I finish typing, often close to hitting send (minute before or after), I found the solution. Probably because typing it all clears and organizes the mind. Dave: if you post the problem, do so on another thread :-) - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky13fwACgkQtTMYHG2NR9WYTgCeKWtVktDEKFxJpNmbYzEX9E7n XrYAn2YtyYcNHIls4khy8QGd4wUQnuPD =aD0m -----END PGP SIGNATURE-----
On Wed, 2010-10-13 at 16:40 +0100, Dave Howorth wrote:
Roger Oberholtzer wrote:
Too bad my theory on why I have a slew of different machines that render badly for non-root users of KDE, yet render correctly for root remains. I am at a loss. And have a slew of upset users. William Stephenson was helping me with suggestions. But no solution has been found.
At one place I worked, we had a teddy bear that did the debugging for us. When you had a difficult bug, you sat the teddy where he could see both you and the screen and then explained to him exactly what was happening and why all the hypothetical explanations failed. He usually solved the problems quite quickly, just by staring at you intensely at the right moment.
You could try explaining it all to us in excruciating detail if you like ...
Having exhausted all other routes to a solution, I can consider this... I have an earlier thread on this list, and the opensuse-kde list (August 2010). Here is what I first reported: For regular KDE users, many screen components are not drawn. They are black. This includes the panel, KDE menus (like the kickstart menu or the knofity message window.) The result is often black text on a black background - which is impossible to read. The desktop folder shows icons and a title. But there is no window decoration at all. It is like some facet of rendering is not working. It makes no difference if I have rendering on or off. It happens on most system installs we do. The computers are different. Some are nvidia, others ATI. They are not installed by the same person or from the same media. Here is the strange part: it looks ok for root. So I can only conclude that the correct software is installed. So, the first thought was that some files needed are not accessible by the average user. Will Stephenson has spent a bit of time looking in to this, suggesting possible places where permissions could be a problem. We have found nothing. I used 'find' to try and locate things in the various kde directories that cannot be read by a non-root user. There were no violations. It seems that the users can at least read all system files - which is all they should be able to do. This has happened on 11.2 systems: * as on the original DVD * after upgrading (newer KDE) * with KDE 4.5.2 This is not a cosmetic issue. Some parts of the system are virtually unusable as a result. We have reinstalled, and tried other variations on the install, like: * install * update * user logs in for first time or * install * user logs in * update or * no updates etc... We have deleted the user's .kde4 and .config directories, as well as temp files in /tmp and /var. It makes no difference. I do not have the luxury of trying 11.3 on these systems. But as the problem happens with three versions of KDE4 (including 4.5.2), I am not sure what that would show. The last release known to work on these systems is 10.3. But we do not want to make any new systems with this release. 11.2 is the one we have tested the most in all other facets related to our use. I have a few screen dumps to show what I mean. I can send them along to anyone interested so they can see what I am trying to describe. A couple of users want to run off with their systems, and are a bit disappointed that the GUI is such a problem. Given the frequency and nature of our problem, it is absolutely surprising that we are the only ones to experience this problem so many times. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Oct 13, 2010 at 07:02:39PM +0200, Roger Oberholtzer wrote:
On Wed, 2010-10-13 at 16:40 +0100, Dave Howorth wrote:
Roger Oberholtzer wrote:
Too bad my theory on why I have a slew of different machines that render badly for non-root users of KDE, yet render correctly for root remains. I am at a loss. And have a slew of upset users. William Stephenson was helping me with suggestions. But no solution has been found.
At one place I worked, we had a teddy bear that did the debugging for us. When you had a difficult bug, you sat the teddy where he could see both you and the screen and then explained to him exactly what was happening and why all the hypothetical explanations failed. He usually solved the problems quite quickly, just by staring at you intensely at the right moment.
You could try explaining it all to us in excruciating detail if you like ...
Having exhausted all other routes to a solution, I can consider this...
I have an earlier thread on this list, and the opensuse-kde list (August 2010).
Here is what I first reported:
For regular KDE users, many screen components are not drawn. They are black.
I had ugly black KDE menues with several openSUSE 11.3 installes after upgrades from 11.2. All are caused by pulling some kde*upstream* packages in. Compare the results of the following two rpm calls: rpm -qa \*kde\*open\* and rpm -qa \*kde\*upstream\* If the last command reported any packages I had the KDE funeral theme installed. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Am Mittwoch, 13. Oktober 2010, 19:57:13 schrieb Lars Müller:
For regular KDE users, many screen components are not drawn. They are black.
I had ugly black KDE menues with several openSUSE 11.3 installes after upgrades from 11.2. All are caused by pulling some kde*upstream* packages in.
Yep, that happens if a theme that is not available anymore is set to be used by plasma, e.g. the default plasma theme Air is not available by default because openSUSE uses "openSUSE Air". So changing the plasma theme to some installed theme will solve the issue. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2010-10-13 at 21:32 +0200, Sven Burmeister wrote:
Am Mittwoch, 13. Oktober 2010, 19:57:13 schrieb Lars Müller:
For regular KDE users, many screen components are not drawn. They are black.
I had ugly black KDE menues with several openSUSE 11.3 installes after upgrades from 11.2. All are caused by pulling some kde*upstream* packages in.
Yep, that happens if a theme that is not available anymore is set to be used by plasma, e.g. the default plasma theme Air is not available by default because openSUSE uses "openSUSE Air". So changing the plasma theme to some installed theme will solve the issue.
I have tried all the installed themes to no avail. It is interesting to note that in the theme selection dialog, there is usually some rendering of the themes in the buttons used to select them. In these systems, these buttons only contain the text name of the theme. No other rendering. Unless you are root. The available Themes are Air, Air openSUSE, Aya, and Oxygen. As expected, Air openSUSE is selected. Choosing another does not help. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2010-10-13 at 19:57 +0200, Lars Müller wrote:
Compare the results of the following two rpm calls:
rpm -qa \*kde\*open\*
and
rpm -qa \*kde\*upstream\*
If the last command reported any packages I had the KDE funeral theme installed.
Sorry for the delayed answer. I have access to a diseased system again. So I can persue this issue (and I was forced to go to a work conference in Athens from which I have just returned). I have only these: kdelibs4-branding-openSUSE-11.2-29.31.1.i586 kdebase4-runtime-branding-openSUSE-11.2-29.31.1.i586 kdebase4-openSUSE-11.2-29.31.1.i586 kdebase4-workspace-branding-openSUSE-11.2-29.31.1.i586 There are no upstream RPMs installed. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-10-18 at 09:31 +0200, Roger Oberholtzer wrote:
Sorry for the delayed answer. I have access to a diseased system again. So I can persue this issue (and I was forced to go to a work conference in Athens from which I have just returned).
Any local security rules /etc/permissions.local? - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky8BnMACgkQtTMYHG2NR9W5OACfU99i365VwYdnFuW37cfNrKqq IRcAnR+pEC78/VybYg7sHFehp3KcAb6P =V1uR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2010-10-13 at 19:02 +0200, Roger Oberholtzer wrote: ...
Given the frequency and nature of our problem, it is absolutely surprising that we are the only ones to experience this problem so many times.
There must be something in common that you people are doing on those installs. Perhaps a common networked directory, some configuration you copy, home files, some partitioning scheme you do... You say that systems are installed by different people. Do you have common rules? Common notes? - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky1+c8ACgkQtTMYHG2NR9XaawCfa1kMZeoKPO6pzQ0n24UNcM33 XwUAnAtS3eFF7L4clWaYzhbn0309E75f =X3Co -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2010-10-13 at 20:26 +0200, Carlos E. R. wrote:
There must be something in common that you people are doing on those installs. Perhaps a common networked directory, some configuration you copy, home files, some partitioning scheme you do... You say that systems are installed by different people. Do you have common rules? Common notes?
Not that I can determine. For the most part it is a default install with the default packages. Nothing different than we have done before. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
On Wed, 2010-10-13 at 20:26 +0200, Carlos E. R. wrote:
There must be something in common that you people are doing on those installs. Perhaps a common networked directory, some configuration you copy, home files, some partitioning scheme you do... You say that systems are installed by different people. Do you have common rules? Common notes?
Not that I can determine. For the most part it is a default install with the default packages. Nothing different than we have done before.
The teddy is asleep; he's not helping at all :) So all I can throw out are wild questions. This is KDE-only, yes? The problem doesn't occur if the user logs in with say gnome. How about if you install kubuntu, do you see the problem then? How about locales and themes? If a normal user with the C locale logs in does he see the problem? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2010-10-14 at 11:15 +0100, Dave Howorth wrote:
Roger Oberholtzer wrote:
On Wed, 2010-10-13 at 20:26 +0200, Carlos E. R. wrote:
There must be something in common that you people are doing on those installs. Perhaps a common networked directory, some configuration you copy, home files, some partitioning scheme you do... You say that systems are installed by different people. Do you have common rules? Common notes?
Not that I can determine. For the most part it is a default install with the default packages. Nothing different than we have done before.
The teddy is asleep; he's not helping at all :) So all I can throw out are wild questions.
This is KDE-only, yes? The problem doesn't occur if the user logs in with say gnome. How about if you install kubuntu, do you see the problem then?
How about locales and themes? If a normal user with the C locale logs in does he see the problem?
Cheers, Dave
The solution is to add DISPLAYMANAGER_ROOT_LOGIN_LOCAL="yes" to /etc/sysconfig/displaymanager It seems it has been removed in newer packages. I hope there is no plan to remove the actual functionality. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-10-18 at 09:09 +0200, Roger Oberholtzer wrote:
How about locales and themes? If a normal user with the C locale logs in does he see the problem?
Cheers, Dave
The solution is to add
DISPLAYMANAGER_ROOT_LOGIN_LOCAL="yes"
to /etc/sysconfig/displaymanager
It seems it has been removed in newer packages. I hope there is no plan to remove the actual functionality.
Not removed, but rather, that the default is now "no" and was "yes". But Dave was asking about the locale of those systems that only work well for root. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky8BboACgkQtTMYHG2NR9WBLwCeOV+p60cY+i8ASt32/hWHy3gK PjYAn3vhWVFsMS5VIDYSkjNuKs3kFQA2 =7cfe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-10-18 at 10:30 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2010-10-18 at 09:09 +0200, Roger Oberholtzer wrote:
How about locales and themes? If a normal user with the C locale logs in does he see the problem?
Cheers, Dave
The solution is to add
DISPLAYMANAGER_ROOT_LOGIN_LOCAL="yes"
to /etc/sysconfig/displaymanager
It seems it has been removed in newer packages. I hope there is no plan to remove the actual functionality.
Not removed, but rather, that the default is now "no" and was "yes".
In fact, it did not exist in my file. It it had, I might have taken notice. I had to add the entire string, not just change the value. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-10-18 at 14:01 +0200, Roger Oberholtzer wrote:
On Mon, 2010-10-18 at 10:30 +0200, Carlos E. R. wrote:
The solution is to add
DISPLAYMANAGER_ROOT_LOGIN_LOCAL="yes"
to /etc/sysconfig/displaymanager
It seems it has been removed in newer packages. I hope there is no plan to remove the actual functionality.
Not removed, but rather, that the default is now "no" and was "yes".
In fact, it did not exist in my file. It it had, I might have taken notice. I had to add the entire string, not just change the value.
Precisely. If it does not exist, KDE now assumes "no", when it before assumed "yes" or did not use it. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky8SdYACgkQtTMYHG2NR9VlgwCcDqxgbKEuC+XXSVufdNKZ9Xhc bZYAoIdMGyKA+9ZUTPuy7ee9ZjWNMyzb =gpRn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 13/10/10 18:02, Roger Oberholtzer wrote:
Having exhausted all other routes to a solution, I can consider this... I have an earlier thread on this list, and the opensuse-kde list (August 2010).
Here is what I first reported:
For regular KDE users, many screen components are not drawn. They are black. This includes the panel, KDE menus (like the kickstart menu or the knofity message window.) The result is often black text on a black background - which is impossible to read. The desktop folder shows icons and a title. But there is no window decoration at all. It is like some facet of rendering is not working. It makes no difference if I have rendering on or off. It happens on most system installs we do. The computers are different. Some are nvidia, others ATI. They are not installed by the same person or from the same media.
Here is the strange part: it looks ok for root. So I can only conclude that the correct software is installed.
So, the first thought was that some files needed are not accessible by the average user. Will Stephenson has spent a bit of time looking in to this, suggesting possible places where permissions could be a problem. We have found nothing. I used 'find' to try and locate things in the various kde directories that cannot be read by a non-root user. There were no violations. It seems that the users can at least read all system files - which is all they should be able to do.
This has happened on 11.2 systems:
* as on the original DVD * after upgrading (newer KDE) * with KDE 4.5.2
This is not a cosmetic issue. Some parts of the system are virtually unusable as a result. We have reinstalled, and tried other variations on the install, like:
* install * update * user logs in for first time
or
* install * user logs in * update
or
* no updates
etc...
We have deleted the user's .kde4 and .config directories, as well as temp files in /tmp and /var. It makes no difference.
I do not have the luxury of trying 11.3 on these systems. But as the problem happens with three versions of KDE4 (including 4.5.2), I am not sure what that would show.
The last release known to work on these systems is 10.3. But we do not want to make any new systems with this release. 11.2 is the one we have tested the most in all other facets related to our use.
I have a few screen dumps to show what I mean. I can send them along to anyone interested so they can see what I am trying to describe. A couple of users want to run off with their systems, and are a bit disappointed that the GUI is such a problem.
Given the frequency and nature of our problem, it is absolutely surprising that we are the only ones to experience this problem so many times.
Hmph, a tough one, especially since you seem to seeing this on a range of machines whereas I have never seen it on any of mine. Here's my braindump of everything that could be involved, ordered from maybe to probably not (I know that you've already ruled some of this out, just bear with me) KDE Plasma Desktop Theme * Make sure an actually installed theme is selected in System Settings. Try switching themes. * Try downloading a new theme from khotnewstuff (the "Get new Themes" button) and using that. * Try installing one of the Plasma theme RPMs, e.g. "plasma-theme-glassified" from KDE:Extra and using that. KDE Plasma * Does "plasmapkg -l" give a reasonable list of the installed plasma applets? Are all the ones you expect there? * Does "plasma-windowed launcher" show the application launcher menu? Any errors? * Does "plasma-windowed desktop" show an empty desktop (right clicking should give you "Desktop settings")? Any errors? * Does "plasma-windowed folderview" show you a folderview of ~? Any errors? * Try running with "plasma-netbook" KDE Widget style By default this is Oxygen. * Try switching to a different widget style, e.g. Plastique. * Try fiddling with the settings in the "oxygen-settings" application when you are back to oxygen * Does the "oxygen-demo" application look OK? * Try switching the window decoration widget style also. KWin * Try running with a different WM, e.g. metacity, openbox. * Disable/enable overall desktop effects * Disable/enable individual desktop effects KDE Desktop Colour configuration Based on what you said, it seems to be happening by default even on the first login, so it's unlikely that it is a bad user setting. * Try explicitly setting the color configuration for each user. * Try fiddling with the global settings in /etc/kde4/share/config and /usr/share/kde4/config. RPMs * Make sure you're not installing off slightly corrupted installation media (look for rpm errors in the installation log) * Make sure no "-branding-upstream" packages are installed and all "-branding-openSUSE" packages are installed. * Make sure all packages are consistent, ie. no mixed Factory/Qt4.7 packages - which I assume you've not got since you're using vanilla 11.2. But this goes for updates as well, if you install any updates, make sure they are _all_ installed. With only standard 11.2 repos, make sure a "zypper dup" and a "zypper ve" doesn't want to change anything. * Make sure all package architectures match (all i586, or all x86_64) Video Drivers * On a nVidia system, try with nv, with nouveau, and with nvidia. * On a ATI system, try with radeon, radeonhd, and fglrx. * Try running with just the framebuffer driver (vesafb?) * Make sure the modules are not being loaded with any special options (look in /etc/modprobe.conf.d) * Make sure xorg.conf doesn't contain anything but the bare minumum. * Make sure that users are members of the "video" group and that "/dev/video0" and "/dev/fb0" have reasonable permissions (660 root:video) Hard Disk * Make sure to have lots of free space, esp. /tmp and /var/tmp * Make sure the symlinks in ~/.kde4 point to the right places that aren't full or non-writeable tejas@hobbes:~/.kde4> ls -l total 16 drwxr-xr-x 2 tejas users 4096 2010-09-02 16:53 Autostart lrwxrwxrwx 1 tejas users 23 2010-08-26 14:35 cache-hobbes -> /var/tmp/kdecache-tejas lrwxrwxrwx 1 tejas users 23 2010-08-26 12:16 cache-hobbes.site -> /var/tmp/kdecache-tejas drwxr-xr-x 2 tejas users 4096 2010-08-28 16:31 env drwx------ 8 tejas users 4096 2010-09-24 17:33 share drwxr-xr-x 2 tejas users 4096 2010-09-02 16:53 shutdown lrwxrwxrwx 1 tejas users 18 2010-08-26 14:35 socket-hobbes -> /tmp/ksocket-tejas lrwxrwxrwx 1 tejas users 18 2010-08-26 12:16 socket-hobbes.site -> /tmp/ksocket-tejas lrwxrwxrwx 1 tejas users 14 2010-08-26 14:35 tmp-hobbes -> /tmp/kde-tejas lrwxrwxrwx 1 tejas users 14 2010-08-26 12:16 tmp-hobbes.site -> /tmp/kde-tejas Hope this helps, Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2010-10-14 at 12:28 +0100, Tejas Guruswamy wrote:
of machines whereas I have never seen it on any of mine.
Here's my braindump of everything that could be involved, ordered from maybe to probably not (I know that you've already ruled some of this out, just bear with me)
Add language. A broken translation can have weird effects. Install in English instead. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky3BvIACgkQtTMYHG2NR9WTmACdEFIzC5rNSBD9h2UK8r9mHtuN mqQAmgNmYKOSjTkgvwf083N8Bb4CMOMO =LMlT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2010-10-14 at 15:34 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2010-10-14 at 12:28 +0100, Tejas Guruswamy wrote:
of machines whereas I have never seen it on any of mine.
Here's my braindump of everything that could be involved, ordered from maybe to probably not (I know that you've already ruled some of this out, just bear with me)
Add language. A broken translation can have weird effects. Install in English instead.
All is in English. The only 'Swedish' thing is the keyboard. But I even tried claiming a US keyboard. The root user, for whom all works fine, has the default Swedish keyboard. By process of elimination I guess I will eventually find the cause.
- -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux)
iEYEARECAAYFAky3BvIACgkQtTMYHG2NR9WTmACdEFIzC5rNSBD9h2UK8r9mHtuN mqQAmgNmYKOSjTkgvwf083N8Bb4CMOMO =LMlT -----END PGP SIGNATURE-----
-- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2010-10-14 at 12:28 +0100, Tejas Guruswamy wrote:
Hmph, a tough one, especially since you seem to seeing this on a range of machines whereas I have never seen it on any of mine.
Here's my braindump of everything that could be involved, ordered from maybe to probably not (I know that you've already ruled some of this out, just bear with me)
In going through your excellent and very much appreciated list, I noticed that a common complaint made by the plasma-windowed commands was: Cannot initialize zlib, because: Unknown error Which seemed an curious thing. I remember Will saying that some things were uncompressed and cached, and maybe the cache was having access issues. Well, in a way the cache was the problem: components that needed to be uncompressed before getting put in the cache could not even be made. It seems that an experimental libz (based on code from intel's excellent Performance Primitives library) has crept in to our distribution. We only enable our software for non-root users who opt for it. So, root never saw the library, which explains why the desktop looked fine for root. It is in some private folder in /opt. But, our users do see this library. When I removed the library from view, the desktop looked as expected. Now to see why that library is being distributed. I know that it should offer a significant increase in compression speed, and we compress all our collected data. But obviously we never intended for any software other than our own to use it. Even if it is a drop-in replacement for libz. It is only a drop-in replacement if the Intel Performance Primitive libraries are also available. But these sorts of problems I know how to deal with.
Hope this helps,
Tejas
Did this help? It led me to the solution!!!! Thanks more than I can say! -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-10-18 at 13:10 +0200, Roger Oberholtzer wrote:
On Thu, 2010-10-14 at 12:28 +0100, Tejas Guruswamy wrote:
Cannot initialize zlib, because: Unknown error
Which seemed an curious thing. I remember Will saying that some things were uncompressed and cached, and maybe the cache was having access issues. Well, in a way the cache was the problem: components that needed to be uncompressed before getting put in the cache could not even be made. It seems that an experimental libz (based on code from intel's excellent Performance Primitives library) has crept in to our distribution. We only enable our software for non-root users who opt for it. So, root never saw the library, which explains why the desktop looked fine for root. It is in some private folder in /opt. But, our users do see this library. When I removed the library from view, the desktop looked as expected.
Wow! Perhaps you could adjust paths so that /opt is searched/linked last.
Tejas
Did this help? It led me to the solution!!!! Thanks more than I can say!
Curious indeed :-) - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky8MzoACgkQtTMYHG2NR9X6LACeOoSxBzyywTEWBD4gM6++RiOO RBQAn2bSpdA/2IXYy/GJyUzxvVxMLSVv =9UQJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-10-18 at 13:44 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2010-10-18 at 13:10 +0200, Roger Oberholtzer wrote:
On Thu, 2010-10-14 at 12:28 +0100, Tejas Guruswamy wrote:
Cannot initialize zlib, because: Unknown error
Which seemed an curious thing. I remember Will saying that some things were uncompressed and cached, and maybe the cache was having access issues. Well, in a way the cache was the problem: components that needed to be uncompressed before getting put in the cache could not even be made. It seems that an experimental libz (based on code from intel's excellent Performance Primitives library) has crept in to our distribution. We only enable our software for non-root users who opt for it. So, root never saw the library, which explains why the desktop looked fine for root. It is in some private folder in /opt. But, our users do see this library. When I removed the library from view, the desktop looked as expected.
Wow!
Perhaps you could adjust paths so that /opt is searched/linked last.
I think the tricky bit is that /lib (where libz lives) tends to always be searched last. I have an ancient memory from SVR4 that the LD_RUN_PATH variable could contains colons and semicolons. This allowed some now forgotten control over if libraries were searched for before or after the system defaults. BTW, we use LD_RUN_PATH when linking and not ldconfig so we can have per-program (as opposed to system-wide) control over where libraries come from. I am going to consider changing LD_RUN_PATH=/usr/lib:/opt/rsoft/lib:/opt/lib to LD_RUN_PATH=/usr/lib:/lib:/opt/rsoft/lib:/opt/lib when linking. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-10-18 at 14:11 +0200, Roger Oberholtzer wrote: My thought about the libz causing problems being related to our messing about with the intel Performance Primitives libraries was incorrect. I see that the libz we were conflicting with is a libz 1.1.3. The Linux system uses libz.1.2.3. The strange thing is that openSUSE 10.3, where all works ok with our library (libz 1.1.3) in place in the same way, also uses libz 1.2.3 (in /lib). Perhaps the KDE (and presumably other 'system' apps) in 10.3 do not use libz and so the incompatibility was never seen. All has run very well on 10.3. (I think I may soon be able to say that about 11.2!) The main reason we have our own libz is so we can load it into Tcl interpreters. I will have to see if the interpreters work with the system's libz 1.2.3 If libz.so.1.1.3 and libz.so.1.2.3 are binary incompatible, it is too bad that libz.so.1 points to these on various systems. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 18 October 2010 13:10:20 Roger Oberholtzer wrote:
On Thu, 2010-10-14 at 12:28 +0100, Tejas Guruswamy wrote:
Hope this helps,
Tejas
Did this help? It led me to the solution!!!! Thanks more than I can say!
Finally! I'm glad (selfishly) that this was a local problem. Thanks, Roger, for seeing it through to the end rather than taking the easy 'KDE sucks' option, and thanks to Tejas for his very detailed debugging list. Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-10-18 at 15:28 +0200, Will Stephenson wrote:
On Monday 18 October 2010 13:10:20 Roger Oberholtzer wrote:
On Thu, 2010-10-14 at 12:28 +0100, Tejas Guruswamy wrote:
Hope this helps,
Tejas
Did this help? It led me to the solution!!!! Thanks more than I can say!
Finally!
I'm glad (selfishly) that this was a local problem. Thanks, Roger, for seeing it through to the end rather than taking the easy 'KDE sucks' option, and thanks to Tejas for his very detailed debugging list.
Given that the problem was unique to our system, it sort of had to be a local thing. The confusing bit is that the offending library has been in place in our installs since at least 2006 (svn tells me) and does not cause problems at least up to openSUSE 10.3. I don't think KDE sucks. It does cause me a fair share of issues. But it also solves many more. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Carlos E. R. -
Dave Howorth -
Lars Müller -
Roger Oberholtzer -
Sven Burmeister -
Tejas Guruswamy -
Will Stephenson