Well, That was fun! Anyone else managed to create havoc with their KDE by updating to the latest KDE files? Seems the kdeinit would not start, thus preventing KDE from loading fully. The build that broke things is kdebase3-3.5.4-39.1, which became available today. From what I could tell from the logs, it was trying to run /opt/kde/bin/start_kdeinit, which is no longer there! Something didn't get changed in the /opt/kde/bin/startkde file or something was left out or named wrong. I'll let the SUSE guys explain which. Anyway, the quick fix for the problem was to create a link: ln -s /opt/kde/bin/kdeinit /opt/kde/bin/start_kdeinit I suppose also one could edit the startkde file to change the start_kdeinit line to just kdeinit. Decided on the link for now as I'm sure a fix will be quickly arriving. Hope that helps some other poor unsuspecting sap that gets eager to update their kde files! ;-) regards, Lee
On Sunday 03 September 2006 04:29, BandiPat wrote:
That was fun! Anyone else managed to create havoc with their KDE by updating to the latest KDE files?
i would love to - can you tell us where you got them? -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
On Saturday 02 September 2006 22:27, stephan beal wrote:
On Sunday 03 September 2006 04:29, BandiPat wrote:
That was fun! Anyone else managed to create havoc with their KDE by updating to the latest KDE files?
i would love to - can you tell us where you got them? ==========
Stephan Any of the mirrors will give you those. Here's one: http://ftp-1.gwdg.de/pub/opensuse/repositories/KDE:/ What update tool are you trying to use for 10.1? If you are still trying to use the broken yast2, move to something more reliable like KYum or Smart. Don't forget about the broken files also! You won't be able to boot back into KDE after you install these new files. regards, Lee
On Sunday 03 September 2006 04:44, BandiPat wrote:
Stephan Any of the mirrors will give you those. Here's one: http://ftp-1.gwdg.de/pub/opensuse/repositories/KDE:/
What update tool are you trying to use for 10.1? If you are still trying to use the broken yast2, move to something more reliable like KYum or Smart.
To be honest, i'm not sure if my updater works anymore. About 15 minutes ago i used rpm -i --force to install 15 newer yast/zmd/rug RPMs and have no idea if they work now. i'm trying to use the "Software Updater" under KDE tool right now and get nothing but errors, so i'm assuming that i've hosed my zmd. Have you got any pointers to a tutorial on how to set up kyum or smart of suse? This inability to update my box is really getting on my nerves.
Don't forget about the broken files also! You won't be able to boot back into KDE after you install these new files.
Thanks for the note :). -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
On Sunday 03 September 2006 04:44, BandiPat wrote:
Any of the mirrors will give you those. Here's one: http://ftp-1.gwdg.de/pub/opensuse/repositories/KDE:/
What update tool are you trying to use for 10.1? If you are still trying to use the broken yast2, move to something more reliable like KYum or Smart.
i give up. i've added the repo, moved it to the first of the Installation Source list, i see the 3.5.4 files in the Software Management tool (but not the Online Update), but selecting any of the KDE packages for updates causes an endless stream of dependency problems related to kdebase-SUSE. On my second attempt with the Online Update i found the KDE tools. i selected kdebase for upgrade and got a dialog saying that additional packages would be added to accommodate dependencies. Great! Then i clicked ok and then the Online Update tool crashed. Same thing happens on multiple attempts. As i said, i give up. :( -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
On Saturday 02 September 2006 22:10, stephan beal wrote:
On Sunday 03 September 2006 04:44, BandiPat wrote:
Any of the mirrors will give you those. Here's one: http://ftp-1.gwdg.de/pub/opensuse/repositories/KDE:/
What update tool are you trying to use for 10.1? If you are still trying to use the broken yast2, move to something more reliable like KYum or Smart.
i give up.
i've added the repo, moved it to the first of the Installation Source list, i see the 3.5.4 files in the Software Management tool (but not the Online Update), but selecting any of the KDE packages for updates causes an endless stream of dependency problems related to kdebase-SUSE.
On my second attempt with the Online Update i found the KDE tools. i selected kdebase for upgrade and got a dialog saying that additional packages would be added to accommodate dependencies. Great! Then i clicked ok and then the Online Update tool crashed. Same thing happens on multiple attempts.
As i said, i give up. :(
I see tonight there are 32 updates to my kde and what you are saying is don't install them right ? -- LostSon http://www.lostsonsvault.org /\ \ \ \__/ \__/ \ \ (oo) (oo) \_\/~~\_/~~\_ _.-~===========~-._ (___________________) \_______/ I Want To Believe
On Sunday 03 September 2006 05:26, lostson wrote:
I see tonight there are 32 updates to my kde and what you are saying is don't install them right ?
My results aren't conclusive because i did an rpm --force update of my zmd/rug tools tonight and that almost certainly broke something. BandiPat says the update works for him except that a script is either missing or misnamed. See his earlier post for the workaround. -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
On Saturday 02 September 2006 23:26, lostson wrote:
On Saturday 02 September 2006 22:10, stephan beal wrote:
On Sunday 03 September 2006 04:44, BandiPat wrote:
Any of the mirrors will give you those. Here's one: http://ftp-1.gwdg.de/pub/opensuse/repositories/KDE:/
What update tool are you trying to use for 10.1? If you are still trying to use the broken yast2, move to something more reliable like KYum or Smart.
i give up.
i've added the repo, moved it to the first of the Installation Source list, i see the 3.5.4 files in the Software Management tool (but not the Online Update), but selecting any of the KDE packages for updates causes an endless stream of dependency problems related to kdebase-SUSE.
On my second attempt with the Online Update i found the KDE tools. i selected kdebase for upgrade and got a dialog saying that additional packages would be added to accommodate dependencies. Great! Then i clicked ok and then the Online Update tool crashed. Same thing happens on multiple attempts.
As i said, i give up. :(
I see tonight there are 32 updates to my kde and what you are saying is don't install them right ? ========
Well, you can install them, but just remember KDE will be somewhat broken when you do. Anytime you update kdebase3 or kdelibs3 files, you should restart KDE to clear up any inconsistencies the new files may have caused. Due to something not done correctly with the kdebase3 files on this latest build, kdeinit does not get started, so you have to do a little fix for that. If you remember to do the symlink, as I pointed out, you'll be ok until the next build update when SuSE fixes the problem. If you don't feel adventurous though, stay where you are. regards, Lee
On Saturday 02 September 2006 22:58, BandiPat wrote:
On Saturday 02 September 2006 23:26, lostson wrote:
On Saturday 02 September 2006 22:10, stephan beal wrote:
On Sunday 03 September 2006 04:44, BandiPat wrote:
Any of the mirrors will give you those. Here's one: http://ftp-1.gwdg.de/pub/opensuse/repositories/KDE:/
What update tool are you trying to use for 10.1? If you are still trying to use the broken yast2, move to something more reliable like KYum or Smart.
i give up.
i've added the repo, moved it to the first of the Installation Source list, i see the 3.5.4 files in the Software Management tool (but not the Online Update), but selecting any of the KDE packages for updates causes an endless stream of dependency problems related to kdebase-SUSE.
On my second attempt with the Online Update i found the KDE tools. i selected kdebase for upgrade and got a dialog saying that additional packages would be added to accommodate dependencies. Great! Then i clicked ok and then the Online Update tool crashed. Same thing happens on multiple attempts.
As i said, i give up. :(
I see tonight there are 32 updates to my kde and what you are saying is don't install them right ?
========
Well, you can install them, but just remember KDE will be somewhat broken when you do. Anytime you update kdebase3 or kdelibs3 files, you should restart KDE to clear up any inconsistencies the new files may have caused. Due to something not done correctly with the kdebase3 files on this latest build, kdeinit does not get started, so you have to do a little fix for that.
If you remember to do the symlink, as I pointed out, you'll be ok until the next build update when SuSE fixes the problem. If you don't feel adventurous though, stay where you are.
regards, Lee
My question is how does something as simple as that get broken ?? -- LostSon http://www.lostsonsvault.org /\ \ \ \__/ \__/ \ \ (oo) (oo) \_\/~~\_/~~\_ _.-~===========~-._ (___________________) \_______/ I Want To Believe
On Sunday 03 September 2006 00:03, lostson wrote: [...]
========
Well, you can install them, but just remember KDE will be somewhat broken when you do. Anytime you update kdebase3 or kdelibs3 files, you should restart KDE to clear up any inconsistencies the new files may have caused. Due to something not done correctly with the kdebase3 files on this latest build, kdeinit does not get started, so you have to do a little fix for that.
If you remember to do the symlink, as I pointed out, you'll be ok until the next build update when SuSE fixes the problem. If you don't feel adventurous though, stay where you are.
regards, Lee
My question is how does something as simple as that get broken ??
Well, I could give you some thoughts on that part, but it would be best to wait for a Novell/suse developer/packager to give the most accurate description. Lee
On 02/09/06 22:12, BandiPat wrote:
On Sunday 03 September 2006 00:03, lostson wrote: [...]
<snip>
My question is how does something as simple as that get broken ??
-------------
Well, I could give you some thoughts on that part, but it would be best to wait for a Novell/suse developer/packager to give the most accurate description. Now I am even more glad that I decided to wait for 10.2 :)
On Sunday 03 September 2006 06:12, BandiPat wrote:
My question is how does something as simple as that get broken ?? Well, I could give you some thoughts on that part, but it would be best to wait for a Novell/suse developer/packager to give the most accurate
The most simple answer: kdebase3 was updated/built but kdelibs3 not. Bye, Steve
lostson wrote: ...
My question is how does something as simple as that get broken ??
Some errors is easy and the others hard to find, but at the end, when we know what was the reason, all they look simple and we can't understand how it happened. People are doing mistakes. It could be many reasons for something appearing as a work in progress slip in a snapshot. -- Regards, Rajko.
On Saturday 02 September 2006 22:29, BandiPat wrote:
Well,
That was fun! Anyone else managed to create havoc with their KDE by updating to the latest KDE files? Seems the kdeinit would not start, thus preventing KDE from loading fully. The build that broke things is kdebase3-3.5.4-39.1, which became available today. From what I could tell from the logs, it was trying to run /opt/kde/bin/start_kdeinit, which is no longer there! Something didn't get changed in the /opt/kde/bin/startkde file or something was left out or named wrong. I'll let the SUSE guys explain which.
Anyway, the quick fix for the problem was to create a link: ln -s /opt/kde/bin/kdeinit /opt/kde/bin/start_kdeinit
I suppose also one could edit the startkde file to change the start_kdeinit line to just kdeinit. Decided on the link for now as I'm sure a fix will be quickly arriving.
Hope that helps some other poor unsuspecting sap that gets eager to update their kde files! ;-)
regards, Lee
I had just finished upgrading to the latest kde with smart, but I thought I would read my mail before rebooting. Thank goodness. I tried rebooting without doing anything. Sure enough, I needed to use your fix. Same kde build. Thanks again. -- Jeremy Baker <jab@muskokatech.ca> GnuPGP fingerprint = EE66 AC49 E008 E09A 7A2A 0195 50EF 580B EDBB 95B6
BandiPat wrote:
Well,
That was fun! Anyone else managed to create havoc with their KDE by updating to the latest KDE files? Seems the kdeinit would not start, thus preventing KDE from loading fully. The build that broke things is kdebase3-3.5.4-39.1, which became available today. From what I could tell from the logs, it was trying to run /opt/kde/bin/start_kdeinit, which is no longer there! Something didn't get changed in the /opt/kde/bin/startkde file or something was left out or named wrong. I'll let the SUSE guys explain which.
Anyway, the quick fix for the problem was to create a link: ln -s /opt/kde/bin/kdeinit /opt/kde/bin/start_kdeinit
I suppose also one could edit the startkde file to change the start_kdeinit line to just kdeinit. Decided on the link for now as I'm sure a fix will be quickly arriving.
Hope that helps some other poor unsuspecting sap that gets eager to update their kde files! ;-)
regards, Lee
Thanks for this posting. There never was a start_kdeinit file just kdeinit. The start_kdeinit in /opt/kde3/bin/startkde was a last minute amendment (at 0429 hours 3/9/06) and I suspect that either the intention was to add a new file called start_kdeinit or rename the current kdeinit to start_kdeinit in /opt/kde3/bin/ but someone got all excited and forgot to do it :-) . The fix is to alter the start_kdeinit in the file /opt/kde3/bin/startkde (or as you suggested putting in a symlink). Thanks for you warning as I had the chance to amend the startkde file before rebooting :-). Cheers. -- This computer is environment-friendly and is running on OpenSuSE 10.1
On Sat, Sep 02, 2006 at 10:29:21PM -0400, BandiPat wrote:
Well,
That was fun! Anyone else managed to create havoc with their KDE by updating to the latest KDE files? Seems the kdeinit would not start, thus preventing KDE from loading fully. The build that broke things is kdebase3-3.5.4-39.1, which became available today. From what I could tell from the logs, it was trying to run /opt/kde/bin/start_kdeinit, which is no longer there! Something didn't get changed in the /opt/kde/bin/startkde file or something was left out or named wrong. I'll let the SUSE guys explain which.
Anyway, the quick fix for the problem was to create a link: ln -s /opt/kde/bin/kdeinit /opt/kde/bin/start_kdeinit
I suppose also one could edit the startkde file to change the start_kdeinit line to just kdeinit. Decided on the link for now as I'm sure a fix will be quickly arriving.
Hope that helps some other poor unsuspecting sap that gets eager to update their kde files! ;-)
It works fine for me. Are you using the BuildService KDE packages additionaly? Ciao, Marcus
On Sat, Sep 02, 2006 at 10:29:21PM -0400, BandiPat wrote:
Well,
That was fun! Anyone else managed to create havoc with their KDE by updating to the latest KDE files? Seems the kdeinit would not start, thus preventing KDE from loading fully. The build that broke things is kdebase3-3.5.4-39.1, which became available today. From what I could tell from the logs, it was trying to run /opt/kde/bin/start_kdeinit, which is no longer there! Something didn't get changed in the /opt/kde/bin/startkde file or something was left out or named wrong. I'll let the SUSE guys explain which.
Anyway, the quick fix for the problem was to create a link: ln -s /opt/kde/bin/kdeinit /opt/kde/bin/start_kdeinit
I suppose also one could edit the startkde file to change the start_kdeinit line to just kdeinit. Decided on the link for now as I'm sure a fix will be quickly arriving.
Hope that helps some other poor unsuspecting sap that gets eager to update their kde files! ;-)
It works fine for me.
Are you using the BuildService KDE packages additionaly?
Ciao, Marcus =========== Nope, Marcus, nothing but what is in the 10.1 directories. No other odd
On Sunday 03 September 2006 05:18, Marcus Meissner wrote: things or experimental stuff. Should someone drop a note to bugzilla about this? I haven't yet, just did the link quick fix for the moment. It seems since several here are experiencing the same problem, you're the odd man out. ;-) What did you do to keep your KDE sane? regards, Lee
On Sunday 03 September 2006 11:23, BandiPat wrote:
Should someone drop a note to bugzilla about this?
The problem is that a kdebase3 package that became available too early is causing this. Once other packages have caught up, the problem will go away. There is mention of this at Planet-KDE. If someone has prelinking enabled then kdeinit should be disabled already at startup and so they would most likely not experience this instance of breakage. That is my situation. -- /path/to/Truth
On Sunday 03 September 2006 18:23, BandiPat wrote:
broke things is kdebase3-3.5.4-39.1, which became available today. Are you using the BuildService KDE packages additionaly? Nope, Marcus, nothing but what is in the 10.1 directories.
That's impossible. The SUSE Linux 10.1 distro doesn't contain KDE 3.5.4. Bye, Steve
On Sunday 03 September 2006 12:39, Stephan Binner wrote:
On Sunday 03 September 2006 18:23, BandiPat wrote:
broke things is kdebase3-3.5.4-39.1, which became available today.
Are you using the BuildService KDE packages additionaly?
Nope, Marcus, nothing but what is in the 10.1 directories.
That's impossible. The SUSE Linux 10.1 distro doesn't contain KDE 3.5.4.
Bye, Steve ========
Yes, my mistake Steve, I misunderstood what Marcus was referring too on the buildservice kde packages. I guess I am afterall using those. duh! ;-) Lee
Hi! On 9/3/06, BandiPat <penguin0601@earthlink.net> wrote:
Well,
That was fun! Anyone else managed to create havoc with their KDE by updating to the latest KDE files? Seems the kdeinit would not start,
Um, yes. I just had this with 10.0 system using smart (and what ever repositories what were installed with smart :-) After the upgrade with smart, I hit Ctrl+Alt+Backspace to restart the X. It did not restart. (No, I have not actually rebooted the whole system... should I?) Writing startx on shell terminal starts and logs into KDE normally. But I do not get the graphical login.
Anyway, the quick fix for the problem was to create a link: ln -s /opt/kde/bin/kdeinit /opt/kde/bin/start_kdeinit
Hmmm. I do not have /opt/kde in my system. Just /opt/kde3 (BTW, on a separate not, when running shell in X, the fonts are wrong so that when I type ll (or ls -la) I can not see the last char of the dir names... it diesn't seem to fit there even though there is nothing to fit to.) And futher more, I have both /opt/kde3/bin/start_kdeinit and /opt/kde3/bin/kdeinit files there. Neither are symlinks to anywhere. Different files, with almost the same time stamp. So, your quick fix would replace one of these. Is this what you mean? -- HG.
HG wrote:
Hi!
On 9/3/06, BandiPat <penguin0601@earthlink.net> wrote:
Well,
That was fun! Anyone else managed to create havoc with their KDE by updating to the latest KDE files? Seems the kdeinit would not start,
Um, yes. I just had this with 10.0 system using smart (and what ever repositories what were installed with smart :-)
After the upgrade with smart, I hit Ctrl+Alt+Backspace to restart the X. It did not restart. (No, I have not actually rebooted the whole system... should I?) Writing startx on shell terminal starts and logs into KDE normally. But I do not get the graphical login.
Anyway, the quick fix for the problem was to create a link: ln -s /opt/kde/bin/kdeinit /opt/kde/bin/start_kdeinit
Hmmm. I do not have /opt/kde in my system. Just /opt/kde3 (BTW, on a separate not, when running shell in X, the fonts are wrong so that when I type ll (or ls -la) I can not see the last char of the dir names... it diesn't seem to fit there even though there is nothing to fit to.)
And futher more, I have both /opt/kde3/bin/start_kdeinit and /opt/kde3/bin/kdeinit files there. Neither are symlinks to anywhere. Different files, with almost the same time stamp. So, your quick fix would replace one of these. Is this what you mean?
If you have upgraded late yesterday or early today then there is nothing to do because the new upgrade contains the corrected files. Cheers. -- This computer is environment-friendly and is running on OpenSuSE 10.1
Hi! On 9/5/06, Basil Chupin <blchupin@tpg.com.au> wrote:
HG wrote:
After the upgrade with smart, I hit Ctrl+Alt+Backspace to restart the X. It did not restart. (No, I have not actually rebooted the whole system... should I?) Writing startx on shell terminal starts and logs
If you have upgraded late yesterday or early today then there is nothing to do because the new upgrade contains the corrected files.
I upgraded today. And yes I did have to do something: I rebooted the system (it's more like windows all the time) and now the X works.... ...Actually too well. I still do not get the log screen as now it logs me on automatically >:-( No, I did not have that enabled and I just checked wether something had changed it - from Control Center/System Administration/Login Manager/Convenience - and no, it's still not enabled and yet, this always logs me automatically on after reboot. No, sorry that's not all. I just rebooted this to be sure, and the above thing only happened twice. This time, I was not automatically logged on, but the list of users that was shown on the front page included me, root and just one other user. I have logged onto the X with root and my own username after the update. The other user might have been the one that would have been selected at the above auto-login dialog, which I only visited. Now, I checked the hidden users list (again from the KDE control center) and no, the other users have not been marked as hidden. Still they were not shown. One thing more, now the system asks for root password when doing reboot locally. That wasn't so and again from the KDE control center I can see that the value for allow shutdown local is Everybody. So, I think I'm having lot's of things wrong with the new KDE :-( -- HG.
On 9/5/06, HG <hg.list@gmail.com> wrote:
Hi!
above thing only happened twice. This time, I was not automatically logged on, but the list of users that was shown on the front page included me, root and just one other user. I have logged onto the X with root and my own username after the update. The other user might have been the one that would have been selected at the above auto-login dialog, which I only visited. Now, I checked the hidden users list (again from the KDE control center) and no, the other users have not been marked as hidden. Still they were not shown.
It went back to normal after I hid the root user. The others came back to the list. But this I could not fix:
One thing more, now the system asks for root password when doing reboot locally. That wasn't so and again from the KDE control center I can see that the value for allow shutdown local is Everybody.
I noticed that there is a setting for local shutdown in YaST which had value for KDE: automatic. I changed that to local users, but still I can not reboot the computer locally without root password. How to fix? -- HG.
HG wrote:
Hi!
On 9/5/06, Basil Chupin <blchupin@tpg.com.au> wrote:
HG wrote:
After the upgrade with smart, I hit Ctrl+Alt+Backspace to restart the X. It did not restart. (No, I have not actually rebooted the whole system... should I?) Writing startx on shell terminal starts and logs
If you have upgraded late yesterday or early today then there is nothing to do because the new upgrade contains the corrected files.
I upgraded today. And yes I did have to do something: I rebooted the system (it's more like windows all the time) and now the X works....
...Actually too well. I still do not get the log screen as now it logs me on automatically >:-( No, I did not have that enabled and I just checked wether something had changed it - from Control Center/System Administration/Login Manager/Convenience - and no, it's still not enabled and yet, this always logs me automatically on after reboot.
No, sorry that's not all. I just rebooted this to be sure, and the above thing only happened twice. This time, I was not automatically logged on, but the list of users that was shown on the front page included me, root and just one other user. I have logged onto the X with root and my own username after the update. The other user might have been the one that would have been selected at the above auto-login dialog, which I only visited. Now, I checked the hidden users list (again from the KDE control center) and no, the other users have not been marked as hidden. Still they were not shown.
One thing more, now the system asks for root password when doing reboot locally. That wasn't so and again from the KDE control center I can see that the value for allow shutdown local is Everybody.
So, I think I'm having lot's of things wrong with the new KDE :-(
No such behaviour here. All working perfectly. I have never allowed 'me' to be logged on automatically - never, ever. All restarts/reboots working as usual, without any problems. Cheers. -- This computer is environment-friendly and is running on OpenSuSE 10.1
Hello, I have a problem getting an 64bit driver for a special hardware. Now I'm thinking whether I really have big disadvantages when installing the 32bit version of SuSE10.1 to get rid of my problem. The system is a dual xeon with 4GB ram and two 1,5TB raids that I want to combine into an LV, making an 3TB PV and format it with reiserfs. Is there any restriction in: 1. filesize 2. reiserfs-size 3. LV-size 4. PV-size 5. ram-size that I will run into? Will I lost performance? Thanks, Robert
On Tuesday 05 September 2006 14:57, Robert wrote:
1. filesize 2. reiserfs-size
http://www.answers.com/topic/comparison-of-file-systems Max file size = 8TiB and max filesystem size is 16TiB TiB = http://www.answers.com/topic/tebibyte-1 == another name for terabyte In any case, any given file can be bigger than your whole filesystem.
3. LV-size 4. PV-size
???
5. ram-size
Several people have reported here that on 32bit systems they only see 3.4GB or so (i don't remember the exact number).
Will I lost performance?
Probably, but i'm guessing that with a dual xeon you won't notice much of a difference, at least not for desktop use. Maybe if you compile a lot of code you might notice. One of my boxes has a dual core and compiles about 50% faster than my single-core boxes (all approximately the same 1.2-1.4GHz). Since compiling is my most time-consuming task, i notice the difference. They're all 32bit, though. -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
Hi! On 9/5/06, Basil Chupin <blchupin@tpg.com.au> wrote:
No such behaviour here. All working perfectly. I have never allowed 'me' to be logged on automatically - never, ever. All restarts/reboots
Neither have I. That's why it was kind of unsuspected...
working as usual, without any problems.
I'm still asked for root password when trying to locally shutdown the computer. I have never had this on from either the KDE control center or YaST. And they are both now configured so that local users can shutdown. Why is it still asking for the root password? Anybody? -- HG.
On Tuesday 05 September 2006 14:07, HG wrote:
Hi!
On 9/5/06, Basil Chupin <blchupin@tpg.com.au> wrote:
No such behaviour here. All working perfectly. I have never allowed 'me' to be logged on automatically - never, ever. All restarts/reboots
Neither have I. That's why it was kind of unsuspected...
working as usual, without any problems.
I'm still asked for root password when trying to locally shutdown the computer. I have never had this on from either the KDE control center or YaST. And they are both now configured so that local users can shutdown. Why is it still asking for the root password? Anybody?
Check in YaST -> System ->/etc/sysconfig Editor Pertinent settings should be: Desktop/Display manager/DISPLAYMANAGER_SHUTDOWN System/Security/Permissions/PERMISSION_SECURITY For ref. mine are "auto" and "easy local" respectively, and I can shutdown from the desktop. HTH -- Steve Boddy
Hi! On 9/5/06, Stephen Boddy <stephen.boddy@btinternet.com> wrote:
On Tuesday 05 September 2006 14:07, HG wrote:
Hi!
On 9/5/06, Basil Chupin <blchupin@tpg.com.au> wrote:
No such behaviour here. All working perfectly. I have never allowed 'me' to be logged on automatically - never, ever. All restarts/reboots
Neither have I. That's why it was kind of unsuspected...
working as usual, without any problems.
I'm still asked for root password when trying to locally shutdown the computer. I have never had this on from either the KDE control center or YaST. And they are both now configured so that local users can shutdown. Why is it still asking for the root password? Anybody?
Check in YaST -> System ->/etc/sysconfig Editor
Pertinent settings should be: Desktop/Display manager/DISPLAYMANAGER_SHUTDOWN
There is no DISPLAYMANAGER_SHUTDOWN, but there is KDM_SHUTDOWN. For that I had "auto", but now it was "local" (I just changed this from YaST/Security and users/local security...
System/Security/Permissions/PERMISSION_SECURITY
For this I have "easy local" also.
For ref. mine are "auto" and "easy local" respectively, and I can shutdown from the desktop.
I just changed the KDM_SHUTDOWN back to "auto" to have the same settings as you. But now, still I'm required to enter the root password to shutdown. -- HG.
On Tuesday 05 September 2006 19:36, HG wrote:
Hi!
On 9/5/06, Stephen Boddy <stephen.boddy@btinternet.com> wrote:
On Tuesday 05 September 2006 14:07, HG wrote:
Hi!
On 9/5/06, Basil Chupin <blchupin@tpg.com.au> wrote:
No such behaviour here. All working perfectly. I have never allowed 'me' to be logged on automatically - never, ever. All restarts/reboots
Neither have I. That's why it was kind of unsuspected...
working as usual, without any problems.
I'm still asked for root password when trying to locally shutdown the computer. I have never had this on from either the KDE control center or YaST. And they are both now configured so that local users can shutdown. Why is it still asking for the root password? Anybody?
Check in YaST -> System ->/etc/sysconfig Editor
Pertinent settings should be: Desktop/Display manager/DISPLAYMANAGER_SHUTDOWN
There is no DISPLAYMANAGER_SHUTDOWN, but there is KDM_SHUTDOWN. For that I had "auto", but now it was "local" (I just changed this from YaST/Security and users/local security...
System/Security/Permissions/PERMISSION_SECURITY
For this I have "easy local" also.
For ref. mine are "auto" and "easy local" respectively, and I can shutdown from the desktop.
I just changed the KDM_SHUTDOWN back to "auto" to have the same settings as you. But now, still I'm required to enter the root password to shutdown.
Hmmm. I'm on 10.1, so that may be the difference in settings names. Having changed the setting, the programs will possibly need to restart to pick up the config changes. I'd recommend from a vt console (Ctrl-Alt-F1) as root: # init 3 # SuSEconfig # ldconfig # init 5 The middle two may or may not be necessary, but won't harm nothing, so why not? -- Steve Boddy
Stephen Boddy wrote:
On Tuesday 05 September 2006 19:36, HG wrote:
Hi!
On Tuesday 05 September 2006 14:07, HG wrote:
Hi!
On 9/5/06, Basil Chupin <blchupin@tpg.com.au> wrote:
No such behaviour here. All working perfectly. I have never allowed 'me' to be logged on automatically - never, ever. All restarts/reboots Neither have I. That's why it was kind of unsuspected...
working as usual, without any problems. I'm still asked for root password when trying to locally shutdown the computer. I have never had this on from either the KDE control center or YaST. And they are both now configured so that local users can shutdown. Why is it still asking for the root password? Anybody? Check in YaST -> System ->/etc/sysconfig Editor
Pertinent settings should be: Desktop/Display manager/DISPLAYMANAGER_SHUTDOWN There is no DISPLAYMANAGER_SHUTDOWN, but there is KDM_SHUTDOWN. For
On 9/5/06, Stephen Boddy <stephen.boddy@btinternet.com> wrote: that I had "auto", but now it was "local" (I just changed this from YaST/Security and users/local security...
System/Security/Permissions/PERMISSION_SECURITY For this I have "easy local" also.
For ref. mine are "auto" and "easy local" respectively, and I can shutdown from the desktop. I just changed the KDM_SHUTDOWN back to "auto" to have the same settings as you. But now, still I'm required to enter the root password to shutdown.
Hmmm. I'm on 10.1, so that may be the difference in settings names.
Having changed the setting, the programs will possibly need to restart to pick up the config changes. I'd recommend from a vt console (Ctrl-Alt-F1) as root:
# init 3 # SuSEconfig # ldconfig # init 5
The middle two may or may not be necessary, but won't harm nothing, so why not?
Both of the parameters are there - it's only a matter of looking for them (in the wrong places ) :-) . Cheers. -- This computer is environment-friendly and is running on OpenSuSE 10.1
HG wrote:
I'm still asked for root password when trying to locally shutdown the computer. I have never had this on from either the KDE control center or YaST. And they are both now configured so that local users can shutdown. Why is it still asking for the root password? Anybody?
Check /opt/kde3/share/config/kdm/kdmrc and make sure it is a symlink to /etc/opt/kde3/share/config/kdm/kdmrc. SUSE uses this file (and therefore looks there for the config options and changes to the config, but the one in opt is the one kde uses. HTH -- Joe Morris Registered Linux user 231871
* Joe Morris (NTM) <Joe_Morris@ntm.org> [09-05-06 20:09]:
Check /opt/kde3/share/config/kdm/kdmrc and make sure it is a symlink /to etc/opt/kde3/share/config/kdm/kdmrc. SUSE uses this file (and therefore looks there for the config options and changes to the config, but the one in opt is the one kde uses. HTH
there is *no* /etc/opt/kde3/share/config/kdm/kdmrc with kdebase3-3.5.4-42.1 -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
* Patrick Shanahan <ptilopteri@gmail.com> [09-05-06 20:43]:
there is *no* /etc/opt/kde3/share/config/kdm/kdmrc with kdebase3-3.5.4-42.1
btw: kdebase3-3.5.4-46.1 just hit the wires. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
Hi! On 9/6/06, Patrick Shanahan <ptilopteri@gmail.com> wrote:
* Patrick Shanahan <ptilopteri@gmail.com> [09-05-06 20:43]:
there is *no* /etc/opt/kde3/share/config/kdm/kdmrc with kdebase3-3.5.4-42.1
btw: kdebase3-3.5.4-46.1 just hit the wires.
I was finally able to upgrade to that (the mirrors for opensuse were so slow that I was getting timeouts until today). The new versions fixed the shutdown. Now all local users can shutdown the computer (as it was and as the settings were in the different places). But again, after this update, the auto-login was enabled... what's with that? This time, though, the setting was also changed, so I just changed it back. So, things are working again. Thanks. -- HG.
* HG <hg.list@gmail.com> [09-09-06 17:37]:
But again, after this update, the auto-login was enabled... what's with that?
Have no idea. I have *never* had auto-login enabled and it has *never* changed itself..... -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
Hi! On 9/10/06, Patrick Shanahan <ptilopteri@gmail.com> wrote:
* HG <hg.list@gmail.com> [09-09-06 17:37]:
But again, after this update, the auto-login was enabled... what's with that?
Have no idea. I have *never* had auto-login enabled and it has *never* changed itself.....
We'll, it's fine now after I changed it back. So no worries :-) I'm happy. -- HG.
Actually... On 9/10/06, HG <hg.list@gmail.com> wrote:
Hi!
We'll, it's fine now after I changed it back. So no worries :-) I'm happy.
It's not quite fine yet still. Well, I got rid of the auto-login, but the population of the login list is still acting weird. I have 7 users with UID 1000-1006 + root, of course. The only difference between these is that UID 1000 and 1002 are members of SSH-group (only they are allowed to use SSH). At the moment nobody is disabled and every user has been created the same way with YaST, How the login was and how I would like it to be is that all others are shown there, except root. So to do this, I open the KDE Control Center. From there I open the Login manager and select the administrator mode. On Users-tab there is the list of Hidden Users. From that list, I try to select root to be hidden. But it doesn't work as it should. Here are the different scenarios that I've found out: - If I do not have anybody selected, only UIDs 1000, 1002 and root are shown on the login screen. - If I select root to be hidden, only the UIDs 1000 and 1002 are shown. - Curiously, if I also select UID 1003 to be hidden, then all others except 1003 and root are shown (this is of course how it should be). But if I try to show the 1003, most of the others also disappear. - And further more, if I only hide the user 1003 (and not root), then shown are the users 1000, 1002 and root. So the problem is somehow connected to the user 1003. Except that I can not figure out why the user 1001 would never show along with 1000 and 1002. And I have absolutely no iea why 1003 would be any different. Anybody have any idea how to get this working? Where to look? -- HG.
Patrick Shanahan wrote:
* Joe Morris (NTM) <Joe_Morris@ntm.org> [09-05-06 20:09]:
Check /opt/kde3/share/config/kdm/kdmrc and make sure it is a symlink /to etc/opt/kde3/share/config/kdm/kdmrc. SUSE uses this file (and therefore looks there for the config options and changes to the config, but the one in opt is the one kde uses. HTH
there is *no* /etc/opt/kde3/share/config/kdm/kdmrc with kdebase3-3.5.4-42.1
I said nothing about what package it was in. joe@jmorris:~> rpm -qf /opt/kde3/share/config/kdm/kdmrc kdebase3-kdm-3.5.4-42.1 But it is the config file for kdm, and the likely problem of the OP. -- Joe Morris Registered Linux user 231871
* Joe Morris (NTM) <Joe_Morris@ntm.org> [09-06-06 07:25]:
I said nothing about what package it was in. joe@jmorris:~> rpm -qf /opt/kde3/share/config/kdm/kdmrc kdebase3-kdm-3.5.4-42.1 But it is the config file for kdm, and the likely problem of the OP.
no, it may be listed as being provided, but it is not. 07:29 wahoo:~ > rpm -qf /opt/kde3/share/config/kdm/kdmrc kdebase3-kdm-3.5.4-46.1 07:31 wahoo:~ > rpm -ql kdebase3-kdm |grep kdmrc /opt/kde3/share/config/kdm/kdmrc -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
participants (15)
-
BandiPat -
Basil Chupin -
Darryl Gregorash -
HG -
Jeremy Baker -
Joe Morris (NTM) -
lostson -
Marcus Meissner -
Mike McQueen -
Patrick Shanahan -
Rajko M -
Robert -
stephan beal -
Stephan Binner -
Stephen Boddy