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 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 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 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 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

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

Hi! On 9/5/06, Basil Chupin 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.

HG wrote:

Hi!

On 9/5/06, Basil Chupin 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

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

On Tuesday 05 September 2006 14:07, HG wrote:

Hi!

On 9/5/06, Basil Chupin 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

On Tuesday 05 September 2006 19:36, HG wrote:

Hi!

On 9/5/06, Stephen Boddy wrote:

...

On Tuesday 05 September 2006 14:07, HG wrote:

...

Hi!

On 9/5/06, Basil Chupin 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

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

* Patrick Shanahan [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

* HG [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

Actually... On 9/10/06, HG 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.

* Joe Morris (NTM) [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