. Is there any word on 8.1? Let me tell you what happened today. I am working on a complex project for the job I do. I had spent about 2 hours collecting info and developing about 15 streams of thought, to integrate in the project I'm working on. I clicked on Desktop C to apply these and... nothing happened. I was still on A. Processor was screaming at 100%, but nothing worked anymore. With <ctl><alt>F1 I got console1 and top. It was kdeinit. I could go back & forth between the consoles but nothing else. So no shutting down Win2k in VMware, no closing my projects, no orderly shutdown, nothing. I doubt the above conveys how disruptive and costly this is. Now, not only do I have to start over, but I am angry as well. When will 8.1 be out? -- You could get a new lease on life -- if only you didn't need the first and last month in advance.
On Wednesday 10 July 2002 19.48, Bill Southwell wrote:
Is there any word on 8.1?
If it's kdeinit, then an 8.1 SuSE release isn't going to help. It'll still have the same KDE programs which are available for 8.0, 7.3, etc. Make sure you've got the latest KDE setup ( 3.0.2 ) as found in: ftp://ftp.suse.com/pub/suse/i386/supplementary/ Having the latest X won't hurt either. (Also found in the same place.) I think that came with SuSE 8.0 if that's what you have, though. (X wouldn't be the problem here, but...) You didn't state anything about what you're using (which KDE, which SuSE...) so I'm giving this info with the thought that maybe you're not up to date. If you've got KDE 3.0.2, then that's the best that's available at the moment and it's not something SuSE can fix. Try bug reports to KDE. With kdeinit, the problem may also not be kdeinit at all, but it could have been caused by a program started by kdeinit. Among these is artsd, which caused a similar problem for me a while back. Turned out I had set the sound settings wrong in the Control Center. Run "kpm" and mark the "Tree" box at the bottom. You can then see which programs are going through kdeinit. There's a good chance it's actually one of those programs that caused the problem, though kdeinit can't be ruled out. Babbling, Joe "Flame" Sullivan -------------------------------------------------------------------------------------- Firechild Web Design and CGI Scripting Services http://firechild.net Secretary, World Association of Internet Marketing http://waim.org Webmaster, Amerikanska - For Americans In Sweden http://amerikanska.com Meta-editor, Open Directory Project http://dmoz.org ---------------------------------------------------------------------------------------
I would suggest going to KDE 3.0.2. It fixed the issue with kdeinit going wanky. It's not a SuSE issue...it's a KDE 3.0.1 and below issue. * Bill Southwell (quantum@ultra2k.com) [020710 11:00]: ::. ::Is there any word on 8.1? :: ::Let me tell you what happened today. I am working on a complex project for ::the job I do. I had spent about 2 hours collecting info and developing about ::15 streams of thought, to integrate in the project I'm working on. I clicked ::on Desktop C to apply these and... nothing happened. I was still on A. ::Processor was screaming at 100%, but nothing worked anymore. With ::<ctl><alt>F1 I got console1 and top. It was kdeinit. I could go back & ::forth between the consoles but nothing else. So no shutting down Win2k in ::VMware, no closing my projects, no orderly shutdown, nothing. :: ::I doubt the above conveys how disruptive and costly this is. :: ::Now, not only do I have to start over, but I am angry as well. :: ::When will 8.1 be out? ::-- ::You could get a new lease on life -- if only you didn't need the first ::and last month in advance. :: ::-- ::To unsubscribe, email: suse-kde-unsubscribe@suse.com ::For additional commands, email: suse-kde-help@suse.com ::Please do not cross-post to suse-linux-e :: -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- Tell me what you believe..I tell you what you should see. -DP --=====-----=====--
You suggested getting KDE 3.0.2, but SuSE doesn't seem to think I should have it, yet... YOU shows a 3.0.1-1, but it also applies the "G" marker in the list of available updates (implying that 3.0.1-1 does not apply to my system and therefore will not be installed, even if I insist on downloading. No mention of 3.0.2. So, if I went to KDE.org (or wherever) and got 3.0.2, will this affect future YOU updates? When SuSE tests and blesses an update from some supplier, does SuSE make a SuSE-specific package? Or is it the same package that the supplier created, only now made available via YOU...? I'm asking this because while I had 7.3, I got involved with Ximian and their Red Carpet updater, which was starting to become BORG-like (though perhaps not quite Micro$oft-like :-) I found it too intrusive, and I found that the profusion of Ximian-version packages on my system was an impediment to loading and updating non-Ximian packages -- too many dependency problems were creeping into my life. Does habitual use of YOU imply a similar growing addiction and the possibility of dependency spirals? /kevin On Wednesday 10 July 2002 15:02, Ben Rosenberg wrote:
I would suggest going to KDE 3.0.2. It fixed the issue with kdeinit going wanky. It's not a SuSE issue...it's a KDE 3.0.1 and below issue.
* Bill Southwell (quantum@ultra2k.com) [020710 11:00]: ::. ::Is there any word on 8.1? :: ::Let me tell you what happened today. I am working on a :: complex project for the job I do. I had spent about 2
* Kevin McLauchlan (kmclauchlan@chrysalis-its.com) [020710 12:31]: ::You suggested getting KDE 3.0.2, but SuSE doesn't seem ::to think I should have it, yet... ::YOU shows a 3.0.1-1, but it also applies the "G" marker in ::the list of available updates (implying that 3.0.1-1 does ::not apply to my system and therefore will not be installed, ::even if I insist on downloading. No mention of 3.0.2. :: ::So, if I went to KDE.org (or wherever) and got 3.0.2, will ::this affect future YOU updates? :: ::When SuSE tests and blesses an update from some ::supplier, does SuSE make a SuSE-specific package? ::Or is it the same package that the supplier created, ::only now made available via YOU...? :: Well, I've had issues with YOU for quite sometime. I guess I'm just to "old" to do this auto updater stuff. I would suggest using ftp (gftp or kbear will do) and downloading each set of packages from this directory on the ftp site. I would do this. 1. cd into /tmp 2. mkdir kde-updates 3. cd into kde-updates 4. mkdir apps base dev (and experimental if you wish) 5. fire up the ftp client and go to this url.... ftp://ftp.gwdg.de:0/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_8.0/ 6. Download the pkgs to the corrisponding directories...ie. all of base goes in /tmp/kde-updates/base .. etc..etc. I would download all the packages in each directory so deps are met. If you wish to do pick and choose..that's fine as well. 7. cd into dev and run rpm -Uvh --nodeps *.rpm then run SuSEconfig. A. Do this for each set of pkgs. 8. After you have installed all the go into /tmp and delete all your user files such as "kde-<username>" and in your /home directory remove .mcop* and in /home/<username>/.kde you should remove the follow 2 symlinks "socket-<machine name>" and "tmp-<machine name> which are symlinks to the kde files you've deleted in /tmp. These are actually sanctioned SuSE pkgs...and I believe if YaST2 is completely up to date it picks up the supplementary directory..or it should in the near future. Cheers! -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- Tell me what you believe..I tell you what you should see. -DP --=====-----=====--
On Wednesday 10 July 2002 13:48, Bill Southwell wrote:
. Is there any word on 8.1?
Let me tell you what happened today. I am working on a complex project for the job I do. I had spent about 2 hours collecting info and developing about 15 streams of thought, to integrate in the project I'm working on. I clicked on Desktop C to apply these and... nothing happened. I was still on A. Processor was screaming at 100%, but nothing worked anymore. With <ctl><alt>F1 I got console1 and top. It was kdeinit. I could go back & forth between the consoles but nothing else. So no shutting down Win2k in VMware, no closing my projects, no orderly shutdown, nothing.
I doubt the above conveys how disruptive and costly this is.
Now, not only do I have to start over, but I am angry as well.
When will 8.1 be out? =====================
My first guess here would be that this is what happens when you run something like Windows on a perfectly good OS like Linux! :o) It's kinda like skydiving, why would you want to jump out of a perfectly good airplane? I can't say I have ever had such a mishap with SuSE Linux. That's not to say it couldn't happen, but then again, I don't let Windows touch my hardware either. Patrick -- ----------end of line........ --- KMail v1.4.1 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206
On Wednesday 10 July 2002 04:03 pm, you wrote:
On Wednesday 10 July 2002 13:48, Bill Southwell wrote:
. Is there any word on 8.1?
My first guess here would be that this is what happens when you run something like Windows on a perfectly good OS like Linux! :o)
It's kinda like skydiving, why would you want to jump out of a perfectly good airplane? I can't say I have ever had such a mishap with SuSE Linux. That's not to say it couldn't happen, but then again, I don't let Windows touch my hardware either.
Patrick
True, but some things aren't made for *nix, like the Realtors' MLS software. Believe me, I'd like to ditch Win if I could. And to be honest I need Win to print. Never was able to print with Suse. (I know some aren't going to like that I said that) And about an hour ago I needed to scan something, so shut down, connected SCSI, booted and whoops, I forgot the Sane that comes with Suse doesn't work. I'd have to deinstall it and compile/install the project files. No time for that, so I have to skip it. I know they're doing their best, but it's a terrible distraction. I just wish I knew when 8.1 was expected so I could try and hold on.
On Wednesday 10 July 2002 17:15, Bill Southwell wrote:
On Wednesday 10 July 2002 04:03 pm, you wrote:
On Wednesday 10 July 2002 13:48, Bill Southwell wrote:
. Is there any word on 8.1?
My first guess here would be that this is what happens when you run something like Windows on a perfectly good OS like Linux! :o)
It's kinda like skydiving, why would you want to jump out of a perfectly good airplane? I can't say I have ever had such a mishap with SuSE Linux. That's not to say it couldn't happen, but then again, I don't let Windows touch my hardware either.
Patrick
True, but some things aren't made for *nix, like the Realtors' MLS software. Believe me, I'd like to ditch Win if I could.
And to be honest I need Win to print. Never was able to print with Suse. (I know some aren't going to like that I said that) And about an hour ago I needed to scan something, so shut down, connected SCSI, booted and whoops, I forgot the Sane that comes with Suse doesn't work. I'd have to deinstall it and compile/install the project files. No time for that, so I have to skip it.
I know they're doing their best, but it's a terrible distraction. I just wish I knew when 8.1 was expected so I could try and hold on. =======================
Bill, I honestly don't think 8.1 is gonna solve your problems. If you can't get things working on 8.0, then I don't think it will happen with another version. Sounds like you just didn't get a good setup to begin with and now you don't have time to correct it, but I do think it is correctable with very little effort. Hope you can hang in there until you get time. I know we would all really hate to lose you back to the demon OS! ;o) Patrick -- ----------end of line........ --- KMail v1.4.1 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206
Sorry to Bill Southwell, I pressed the wrong reply button, but here is my message to the group: On Thursday 11 July 2002 12:02, Stephan Winklbauer wrote:
On Wednesday 10 July 2002 21:15, Bill Southwell wrote:
... And to be honest I need Win to print. Never was able to print with Suse. (I know some aren't going to like that I said that) And about an hour ago I needed to scan something, so shut down, connected SCSI, booted and whoops, I forgot the Sane that comes with Suse doesn't work. I'd have to deinstall it and compile/install the project files. No time for that, so I have to skip it.
I know they're doing their best, but it's a terrible distraction. I just wish I knew when 8.1 was expected so I could try and hold on.
I agree with the printing issue. I had a lot of problems with setting up printing properly under SuSE. After I installed SuSE and wanted to add some packages to my installation I was told that CUPS interferes with some package from ldp and vice versa. When I tried to resolve the conflict my printer stopped working from several applications. I was never able to sort this out properly. Also I had many problems printing from KDevelope. I tried to print in colour, i.e. source code highlighting, and I got a b&w printout or a failure by the enscript package. I thought that by using the standard installation it would have been all set up to work. It didn't. No I use emacs to print my source code or use MS Visual C++ Studio under my W2k installation to do the job. Sad that I have to resort to this, since I really like Linux.
I also have several issues with broken programs. When I try to start then, they load for some time and simply abort without any message. You might want to thing that the rpm packages on the SuSE CD at least work with the SUSE setup and when you install them with YAST2 the dependencies are working.
Regards
Stephan Winklbauer
And to be honest I need Win to print. Never was able to print with Suse. (I know some aren't going to like that I said that) And about an hour ago I needed to scan something, so shut down, connected SCSI, booted and whoops, I forgot the Sane that comes with Suse doesn't work. I'd have to deinstall it and compile/install the project files. No time for that, so I have to skip it.
I think you must have a faulty installation then. Sane on Suse worked just out of the box in my experience. I was very surprised by that. And that much better than Windows. Praie
Is there any word on 8.1?
Let me tell you what happened today. I am working on a complex project for the job I do. I had spent about 2 hours collecting info and developing about 15 streams of thought, to integrate in the project I'm working on. I clicked on Desktop C to apply these and... nothing happened. I was still on A. Processor was screaming at 100%, but nothing worked anymore. With <ctl><alt>F1 I got console1 and top. It was kdeinit. I could go back & forth between the consoles but nothing else. So no shutting down Win2k in VMware, no closing my projects, no orderly shutdown, nothing.
I doubt the above conveys how disruptive and costly this is.
Now, not only do I have to start over, but I am angry as well.
When will 8.1 be out?
=====================
My first guess here would be that this is what happens when you run something like Windows on a perfectly good OS like Linux! :o)
It's kinda like skydiving, why would you want to jump out of a perfectly good airplane? I can't say I have ever had such a mishap with SuSE Linux. That's not to say it couldn't happen, but then again, I don't let Windows touch my hardware either.
Unfortunately, some can't do their daily work without, like me. But these problems haven't got anything to do with VMware. It's a stable tool for two years in my SuSE box. These problems appeared with KDE3. Till 3.0.1 anyhow one could connect them with kdeinit, but since updating to 3.0.2 the screen freezes without any chance for changing to an ascii console and without any log messages - since then I have to push the reset button at least once a day. Again this feature reminds me... Regards Frank
* Frank Reifenstahl (f.reifenstahl@seelig.de) [020711 03:39]: ::Unfortunately, some can't do their daily work without, like me. But these ::problems haven't got anything to do with VMware. It's a stable tool for two ::years in my SuSE box. These problems appeared with KDE3. Till 3.0.1 anyhow ::one could connect them with kdeinit, but since updating to 3.0.2 the screen ::freezes without any chance for changing to an ascii console and without any ::log messages - since then I have to push the reset button at least once a ::day. Again this feature reminds me... Question: Did you remove the kde related directories out of /tmp and remove the symlinks out of ~/.kde and .mcop* also in your home directory when you upgraded to 3.0.2? I've found that if you have a problem and then upgrade but don't remove these items that the problem can persist. Please do this and then if that doesn't work we can suggest other things. -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- Tell me what you believe..I tell you what you should see. -DP --=====-----=====--
participants (8)
-
Ben Rosenberg -
Bill Southwell -
Frank Reifenstahl -
Joe Sullivan -
Kevin McLauchlan -
Patrick -
Praise -
Stephan Winklbauer