9.3 woes (the epilogue?)
Hi All, Am I the only one having serious problems getting 9.3 to straighten out and fly right? I don't want to drag everybody through all of the gory details again, but the problems I've experienced are: - apps crashing when menus are clicked - the file system getting severely corrupted, twice (ext3 and Reiserfs) - artifacts (leftover bits and pieces of windows) remaining after resizing windows and closing programs - in gnome, netapplet closing 'suddenly' when I log in - SuSE Watcher & Plugger not 'embedding' correctly in the panel - knights.desktop came with 'illegal characters' in the mime type - SuSEconfig laboring extensively over gtk2 (takes a looooong time) - there are others, but this is getting too long already... These problems aren't being caused by hardware: I've got two other OSs installed and running beautifully (XP Pro is a business necessity and SuSE 9.2 Pro.) I have only two hard disks attached... no cdrom or dvd (I access these through the LAN when I need them), no usb devices, no add-in graphics card, no directly attached printer, etc.. I have ample memory (512MB) consisting of a single Crucial name brand module with lifetime warranty that tests fine with memtest86. My drives are SMART enabled and reporting nothing out of the ordinary. My fans are all running and the mainboard voltages and temperatures are well within spec. The installation runs fine, as does YOU and all the dependencies are met. I've tried it 'stock' plus YOU a couple of times, and a couple of other times with supplementary upgrades of KDE and GNOME. The only success I seem to have had (so far) is avoiding a third occurrance of the file system corruptions. I've had 9.3 running as an alternate to 9.2 now for a couple of days and I've spent several hours solid updating and fine-tuning it; lots of logging in and out and shutting down and restarting and the file systems have remained intact. However, the other problems are persisting and making it impossible to use 9.3 for daily work. So, I guess my questions are really these: 1. Am I the only one this has been happening to? 2. Is there light at the end of this tunnel? 3. Is 9.3 worth my time and effort since 9.2 is being so nice? I'd really appreciate hearing your ideas and opinions. TIA & regards, - Carl
Carl E. Hartung wrote:
Am I the only one having serious problems getting 9.3 to straighten out and fly right? I don't want to drag everybody through all of the gory details again, but the problems I've experienced are: These problems aren't being caused by hardware: I've got two other OSs installed and running beautifully (XP Pro is a business necessity and SuSE 9.2 Pro.) So, I guess my questions are really these: 3. Is 9.3 worth my time and effort since 9.2 is being so nice?
Maybe not, though I directly installed 9.3 on my system (without 9.2) and have had none of the problems you describe. Maybe if you post the exact error messages that you get during the crashes etc, the guru-s here can help you. -- Shriramana Sharma http://samvit.org
On Friday 12 August 2005 07:16, Shriramana Sharma wrote:
Carl E. Hartung wrote:
Am I the only one having serious problems getting 9.3 to straighten out and fly right? I don't want to drag everybody through all of the gory details again, but the problems I've experienced are: These problems aren't being caused by hardware: I've got two other OSs installed and running beautifully (XP Pro is a business necessity and SuSE 9.2 Pro.) So, I guess my questions are really these: 3. Is 9.3 worth my time and effort since 9.2 is being so nice?
Maybe not, though I directly installed 9.3 on my system (without 9.2) and have had none of the problems you describe.
Maybe if you post the exact error messages that you get during the crashes etc, the guru-s here can help you.
First I've experienced non of these things on any of the 4 or 5 9.3 installations I've done. On 9.2 what kernel where you using? on 9.3? Could it be that your hardware in not (or badly) support in the new kernel? Have you tried it on another machine? I've been running 9.3 on my sony laptop since the day it was released (In germany, which used to be 2 weeks before USA), and it runs rock stable. In fact I 've only boot the original XP-Pro once in 3 months... (That is how I measure usefullness!).. So I think that your problems are hardware related, even though you seam to have crossed that off of your list. Jerry
Carl E. Hartung wrote:
Hi All,
Am I the only one having serious problems getting 9.3 to straighten out and fly right? I don't want to drag everybody through all of the gory details again, but the problems I've experienced are:
- apps crashing when menus are clicked - the file system getting severely corrupted, twice (ext3 and Reiserfs) - artifacts (leftover bits and pieces of windows) remaining after resizing windows and closing programs - in gnome, netapplet closing 'suddenly' when I log in - SuSE Watcher & Plugger not 'embedding' correctly in the panel - knights.desktop came with 'illegal characters' in the mime type - SuSEconfig laboring extensively over gtk2 (takes a looooong time) - there are others, but this is getting too long already...
These problems aren't being caused by hardware: I've got two other OSs installed and running beautifully (XP Pro is a business necessity and SuSE 9.2 Pro.) I have only two hard disks attached... no cdrom or dvd (I access these through the LAN when I need them), no usb devices, no add-in graphics card, no directly attached printer, etc.. I have ample memory (512MB) consisting of a single Crucial name brand module with lifetime warranty that tests fine with memtest86. My drives are SMART enabled and reporting nothing out of the ordinary. My fans are all running and the mainboard voltages and temperatures are well within spec.
The installation runs fine, as does YOU and all the dependencies are met. I've tried it 'stock' plus YOU a couple of times, and a couple of other times with supplementary upgrades of KDE and GNOME.
The only success I seem to have had (so far) is avoiding a third occurrance of the file system corruptions. I've had 9.3 running as an alternate to 9.2 now for a couple of days and I've spent several hours solid updating and fine-tuning it; lots of logging in and out and shutting down and restarting and the file systems have remained intact. However, the other problems are persisting and making it impossible to use 9.3 for daily work.
So, I guess my questions are really these:
1. Am I the only one this has been happening to? 2. Is there light at the end of this tunnel? 3. Is 9.3 worth my time and effort since 9.2 is being so nice?
I'd really appreciate hearing your ideas and opinions.
TIA & regards,
- Carl
I haven't experienced any of the problems I had with 9.1 --> 9.2 upgrades, 9.2 --> 9.3 x86 and x86_64 have been solid. A few weeks ago the HD in the x86_64 laptop died so I did a fresh install without problems. I run kernel.org vanilla kernels (2.6.13-rc6), the latest NVIDIA driver (on x86) and lots of other bits of software I built and installed from sources or downloaded binaries like OOO.org and firefox. My hardware on x86 ... USB printer, USB scanner, CH Joystick and pedals, plus a crappy Skypephone for which I can't raise anyone from the dead at their support, crappy received audio and possibly dead hardware bits. On the x86_64 laptop ... webcam, kodak DX3600 camera, USB 120G HD (at times these get moved to the x86 box) and a bluetooth dongle. I have 2 Mandriva LE 2005 boxes, one that loses its keyboard from time to time, whether it's PS/2 or USB connected, it used to work OK, at first I thought it was software, probably kernel, but I suspect it's the keyboard I bought some months ago when the other one died. I still have a gut suspicion that your hardware is on the edge of tolerance. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Thanks for the feedback, everyone. Your input is helping me a lot in terms of quantifying the situation. Comments/Responses: On Friday 12 August 2005 9:12 am, Bruce Marshall wrote:
Don't have any opinions but I have 9.3 running on 6 machines with nary a problem. That seems to be the experience of almost everybody else, doesn't it? I agree with Sid, this is starting to look a lot like a subtle hardware-specific issue.
Maybe not, though I directly installed 9.3 on my system (without 9.2) and have had none of the problems you describe. I had no problems installing 'fresh' *or* upgrading on top of 9.2; the
On Friday 12 August 2005 1:16 am, Shriramana Sharma wrote: procedures (about five iterations, so far) went smoothly with everything looking to be in order. After about Aug. 9th or 10th, I also had no difficulties with the GNOME 2.1x and KDE 3.4.2 supplementary updates. Again, the procedures went smoothly with none of the typical dependency hiccups... no discernable errors at all, in fact.
Maybe if you post the exact error messages that you get during the crashes etc, the guru-s here can help you.
First I've experienced non of these things on any of the 4 or 5 9.3 installations I've done. I am envious! Again, that does seem to be most people's experience...
On 9.2 what kernel where you using? on 9.3? 2.6.8-24.17-default in 9.2 2.6.11.4-21.8-default in 9.3
Could it be that your hardware in not (or badly) support in the new kernel? The mainboard is a PC Chips M810LMR v. 3.0 using an SiS730 chipset. It seems like (my theory) the IDE module, in concert with the 9.3 kernels, now bugs out when it tries to support adjacent ext3 and Reiserfs partitions on
Deciphering error messages is what Google and the many Linux list archives are for. When answers can't be found there, *then* I ask the great people here. In any event, I've chased down and resolved the repetitive items. That's why I've asked other people to share their experiences. If 20% had responded with short 'laundry lists' of things to check, based on comparable experiences to mine, I'd have a roadmap of sorts to follow. As it stands, I think I'm looking for a needle in a haystack. On Friday 12 August 2005 2:00 am, Jerry Westrick wrote: the same physical drive. After installation, I immediately started getting "barrier-based sync failure" errors and corruptions in *both* partitions. That only stopped when I wiped the partitions clean and formatted both as Reiserfs 3.6. Of course, 9.2, 9.0 and 8.2 (maybe 8.1?) didn't have the problem on this hardware. I think the graphics module (sis) is non-GPL and maintained, I believe, by a former SiS employee who also maintains portions of X. It hasn't posed a problem before.
Have you tried it on another machine?
I would, but the system I want to run it on here is unique in this respect: The other hardware I've got access to for experimentation is even more proprietary (horrible older Gateway & HP consumer boxes,) hence inherently prone to problems in other areas. I'm not sure going down that path gets me closer to a solution on this box.
I've been running 9.3 on my sony laptop since the day it was released (In germany, which used to be 2 weeks before USA), and it runs rock stable.
In fact I 've only boot the original XP-Pro once in 3 months... (That is how I measure usefullness!)..
That's funny... I also like to keep track of how often I'm forced to fire up that side. I wish it were never, but some programs have no counterparts in Linux, yet. That day is coming, though...
So I think that your problems are hardware related, even though you seam to have crossed that off of your list.
Try installing an DVD drive on the machine and reinstall i have found install data sometimes gets clobbered over network installs . Installing additional drives in this box isn't an option, I'm afraid, without upgrading the chassis, fans and power supply. In any event, I verified the md5 sums of the local iso images before installing (mount -o loop etc...). If data were being clobbered, it would have to be happening between hdc4 and hdc2... which I know is theoretically possible... but with that kind of
I haven't crossed hardware off the list completely, but where to start looking when it functions perfectly under different software? (The OS is still software, isn't it?) On Friday 12 August 2005 4:44 am, Peter Nikolic wrote: problem I wouldn't think the installer and YOU would run reliably at all. On Friday 12 August 2005 4:21 am, Sid Boyce wrote:
I still have a gut suspicion that your hardware is on the edge of tolerance. My gut instincts are pointing in that direction, too, but I'm hoping to identify a precise cause, which would open the possibility for a solution. It would be nice not to have my personal workhorse stuck at 9.2..
On Friday 12 August 2005 11:58 am, Janne Karhunen wrote:
- the file system getting severely corrupted, twice (ext3 and Reiserfs) Saw it once on Epox MB, VIA KT400 chipset. Great fodder for Google! Thanks!
- artifacts (leftover bits and pieces of windows) remaining after resizing windows and closing programs 9.1 (and possibly 9.2) with old versions of Qt suffered from this, but haven't seen it with 9.3 anymore. Another potentially useful tidbit. Thanks!
- in gnome, netapplet closing 'suddenly' when I log in - SuSE Watcher & Plugger not 'embedding' correctly in the panel That, indeed, happens with Gnome. KDE is ok. I realize these are small problems likely unrelated to the larger difficulties I'm having, but knowing that it isn't just happening on this system is an important clue for the mix. Thanks!
Both KDE and Gnome seem to be really, really close to functioning nicely. If I could identify the cause for the screen anomalies and random program crashes ... which are much less frequent with the file system stabilized... I could migrate to 9.3 and work through the small stuff like this in my spare time. But the crashes are sudden and yielding no useful backtraces. It's acting like the memory is marginal, but it passes all the tests and runs my other two OS's uneventfully. Thanks, everbody, for all of your feedback. I'll keep pluggin' at this and will let you know via the list if and when I find something... regards, - Carl
On Friday 12 August 2005 06:09, Carl E. Hartung wrote:
Hi All,
Am I the only one having serious problems getting 9.3 to straighten out and fly right? I don't want to drag everybody through all of the gory details again, but the problems I've experienced are:
- apps crashing when menus are clicked - the file system getting severely corrupted, twice (ext3 and Reiserfs) - artifacts (leftover bits and pieces of windows) remaining after resizing windows and closing programs - in gnome, netapplet closing 'suddenly' when I log in - SuSE Watcher & Plugger not 'embedding' correctly in the panel - knights.desktop came with 'illegal characters' in the mime type - SuSEconfig laboring extensively over gtk2 (takes a looooong time) - there are others, but this is getting too long already...
These problems aren't being caused by hardware: I've got two other OSs installed and running beautifully (XP Pro is a business necessity and SuSE 9.2 Pro.) I have only two hard disks attached... no cdrom or dvd (I access these through the LAN when I need them), no usb devices, no add-in graphics card, no directly attached printer, etc.. I have ample memory (512MB) consisting of a single Crucial name brand module with lifetime warranty that tests fine with memtest86. My drives are SMART enabled and reporting nothing out of the ordinary. My fans are all running and the mainboard voltages and temperatures are well within spec.
The installation runs fine, as does YOU and all the dependencies are met. I've tried it 'stock' plus YOU a couple of times, and a couple of other times with supplementary upgrades of KDE and GNOME.
The only success I seem to have had (so far) is avoiding a third occurrance of the file system corruptions. I've had 9.3 running as an alternate to 9.2 now for a couple of days and I've spent several hours solid updating and fine-tuning it; lots of logging in and out and shutting down and restarting and the file systems have remained intact. However, the other problems are persisting and making it impossible to use 9.3 for daily work.
So, I guess my questions are really these:
1. Am I the only one this has been happening to? 2. Is there light at the end of this tunnel? 3. Is 9.3 worth my time and effort since 9.2 is being so nice?
I'd really appreciate hearing your ideas and opinions.
TIA & regards,
- Carl
Try installing an DVD drive on the machine and reinstall i have found install data sometimes gets clobbered over network installs . -- If Bill Gates had gotten LAID at High School do YOU think there would be a Microsoft ? Of course NOT ! You gotta spend a lot of time at your school Locker stuffing underware up your ass to think , I am going to take on the worlds Computer Industry -------:heard on Cyber Radio.:-------
On Friday 12 August 2005 01:09 am, Carl E. Hartung wrote:
So, I guess my questions are really these:
1. Am I the only one this has been happening to? 2. Is there light at the end of this tunnel? 3. Is 9.3 worth my time and effort since 9.2 is being so nice?
I'd really appreciate hearing your ideas and opinions.
Don't have any opinions but I have 9.3 running on 6 machines with nary a problem.
Carl, Carl E. Hartung wrote:
- knights.desktop came with 'illegal characters' in the mime type
I have this in both of my 9.3 systems - not really bothering me but ugly when SuSEconfig runs. I also have seen other people having problems in gowe with susewatcher/pluger. Prefer KDE anyway. The only other problems i have i a constant change in which network card gets which name (a known problem) and some applications that can't handle hal's attitude with mounting with the label name. And an unstable beta openoffice that cannot open a lot of .doc files when i open them via mozilla and that nags me about 'recovered fles'. And konqueror crashing sometimes when deleting files. All of this are known problems. But apart from this suse runs rocksolid. Ad i finally can use a lot of things out of the box. Peter Vollebregt
Thanks, Peter, for the detailed feedback, especially on the known issues. All the feedback I've received has been very helpful. It's time for another report: I've narrowed the problem down a bit and it /does/appear to be software: - I did another clean 9.3 install, but switched my preference at the start to Gnome before going into Detailed Selection. This time, I did /not/ select 'KDE desktop' (which I have always done) or 'All of KDE' (which I've also always done) in addition to Gnome. I *did* select network services, java, experienced user and all of the other packages that I usually select. - At the end of the installation, I went straight into YaST Control Center, then YOU and applied the patches in two steps; kernel solo and last, everything else first. - When the updates were completed and after I rebooted (kernel update) I logged into a perfectly sane, stable and well behaved Gnome 2.10 desktop... the Metacity splash screen text was clean, no Netapplet closing unexpectedly and prompting for a restart, SuSEWatcher & SuSEPlugger properly embedded themselves in the panel, no unusual artifacts stranded on the screen, SuSEconfig did /not/ stall on Gtk2. I customized my desktop, logged out with a 'save settings', did an init 3 and init 5, logged back in and... returned to a sane, stable and well behaved Gnome 2.10 desktop looking exactly as I'd left it. Was I happy? You bet! Satisfied? Nope... - I added supplementary ftp Gnome and KDE to my installation sources then upgraded everything available and... drumroll... it pulled down more KDE packages than GNOME packages and when it was all done every single display anomaly and desktop stability issue returned. Waaaaaah! If you haven't followed this thread, here is what is significant: This time, it took me /two/ steps to 'break' SuSE 9.3, whereas before it was 'breaking' on my system as soon as I installed it. I tried the upgrade on top of 9.2, twice... once with and once without the supplementary upgrades. I tried two 'clean' installs... one with my /home partition on ext3 and then with /home on Reiserfs. Then I restored my 9.2 setup again, but added partitions to install 9.3 side-by-side, where I am now. So... am I the *only* person who has gotten into the habit of selecting Gnome, KDE Desktop /and/ All of KDE at the start of the installation? If there are inherent conflicts when doing this, why didn't YaST2/rpm pick it up? Is there some other mechanism that should have alerted me that this would result in a less than satisfactory environment? This is my first bad experience with a SuSE installation, so I've probably been spoiled. I happen to like KDE /and/ Gnome. I've gotten used to switching between them depending on the program I want to run. Am I being forced to choose between them now? Looking forward to any and all comments... regards, - Carl
On Friday 12 August 2005 17:18, Carl E. Hartung wrote:
Thanks, Peter, for the detailed feedback, especially on the known issues. All the feedback I've received has been very helpful.
It's time for another report:
I've narrowed the problem down a bit and it /does/appear to be software:
- I did another clean 9.3 install, but switched my preference at the start to Gnome before going into Detailed Selection. This time, I did /not/ select 'KDE desktop' (which I have always done) or 'All of KDE' (which I've also always done) in addition to Gnome. I *did* select network services, java, experienced user and all of the other packages that I usually select.
- At the end of the installation, I went straight into YaST Control Center, then YOU and applied the patches in two steps; kernel solo and last, everything else first.
- When the updates were completed and after I rebooted (kernel update) I logged into a perfectly sane, stable and well behaved Gnome 2.10 desktop... the Metacity splash screen text was clean, no Netapplet closing unexpectedly and prompting for a restart, SuSEWatcher & SuSEPlugger properly embedded themselves in the panel, no unusual artifacts stranded on the screen, SuSEconfig did /not/ stall on Gtk2. I customized my desktop, logged out with a 'save settings', did an init 3 and init 5, logged back in and... returned to a sane, stable and well behaved Gnome 2.10 desktop looking exactly as I'd left it.
Was I happy? You bet! Satisfied? Nope...
- I added supplementary ftp Gnome and KDE to my installation sources then upgraded everything available and... drumroll... it pulled down more KDE packages than GNOME packages and when it was all done every single display anomaly and desktop stability issue returned. Waaaaaah!
So... am I the *only* person who has gotten into the habit of selecting Gnome, KDE Desktop /and/ All of KDE at the start of the installation?
No, I've done the same thing for many install cycles although I haven't tried to update 9.2 yet. Both my installs of 9.3 have been clean.
If there are inherent conflicts when doing this, why didn't YaST2/rpm pick it up? Is there some other mechanism that should have alerted me that this would result in a less than satisfactory environment? This is my first bad experience with a SuSE installation, so I've probably been spoiled. I happen to like KDE /and/ Gnome. I've gotten used to switching between them depending on the program I want to run. Am I being forced to choose between them now?
Looking forward to any and all comments...
regards,
- Carl
Carl
Was I happy? You bet! Satisfied? Nope...
- I added supplementary ftp Gnome and KDE to my installation sources then upgraded everything available and... drumroll... it pulled down more KDE packages than GNOME packages and when it was all done every single display anomaly and desktop stability issue returned. Waaaaaah!
I have updated Suse in several ways and the only pitfall i never could solve were updates of gtk that messed up my system. This looks familiair. Try to downgrade gtk and see if that helps. If that is not possible try to update with newer packages. Maybe gwdg's apt repositories have newer versions.
So... am I the *only* person who has gotten into the habit of selecting Gnome, KDE Desktop /and/ All of KDE at the start of the installation? I used to do this but since i don't use gnome and the repeated misery with gtk updates a ileave out nome and all gnome/gtk updates that are any better than security updates.
Peter
Hi Everyone! There is /joy/ back in my desktop again! I don't know why I had to jump through these hoops... but I *did* get here, nonetheless, and in no small measure due to your feedback. So, thanks to all who responded with tidbits and advice and for confirming that I'm /not/ brain dead and that these things /do/ happen from time to time. My solution is really a grunt-level workaround because I can't explain why it resolved the problem. However, the results are 100%... I've got my rock solid, pretty, fast, flexible and highly personalized hybrid Gnome/KDE work environment back, only in the newer versions. I think I'm in love! :-) The procedure that worked: 1. Confirmed I was installing on clean, empty partitions. (Ctl+Alt+F2 at the installer main menu reveals a rescue-like console where they can be mounted, all files erased, then unmounted and fsck'd using the correct variant for the file system. I did this knowing the partitions would be formatted. I didn't care... I wanted them *empty*.) 2. I avoided 'Detailed Selections' and chose the default Gnome desktop. 3. I skipped running YOU, configured my hardware and completed the installation first. 4. I rebooted to verify all was well and, if I encountered a 'hiccup' of any kind, I rebooted, started from scratch and resolved the problem before continuing forward. 5. Once it was booting normally and supplying a stable desktop every time I logged in, I ran YOU and installed the kernel patch by itself. 6. Following the kernel patch, I rebooted, logged in and ran YOU again to install the recommended patches (no MS TT fonts; no multimedia option packs, etc.) 7. I rebooted to confirm no breakage had occurred and ran YOU for the third time to install the optional updates. Yes, I then rebooted again to confirm that nothing had broken. 8. I /then/ began shuffling the installation order of the package groups. I installed a group, confirmed no breakage, ran YOU for updates and checked for breakage again. 9. Only when a group plus any updates were confirmed to *not* break the system did it earn a spot in my written installation sequence. When a package and/or updates /did/ break it, I started from scratch again. 10. I built the system out from the 'core' in this manner until every group I wanted was installed and updated (excluding "KDE Desktop" and "All of KDE" of course) and nothing was broken. 11. I added supplementary KDE (only) as an installation source, then in Install and Remove Software, selected 'KDE Desktop' for installation. A couple of minor packages had to be uninstalled to resolve conflicts, but KDE 3.4.2 installed cleanly. 12. I switched window and desktop managers using the sysconfig editor in YaST, from gdm to kdm and gnome to kde, to "tame" SuSEplugger and SuSEwatcher again. This also proved necessary to get kontact launching in Gnome without having to first log into KDE. The net result is that I've circumvented whatever 'hiccup' was responsible for breaking normal installations on this system. I know from my numerous previous attempts that updating to supplementary Gnome, without question, will break it. Gnome 2.10, as originally supplied with 9.3, is coexisting quite nicely with the supplementary KDE 3.4.2 level 'a'. Finally, I know I could have chased this down to the library, program and script level, if I'd had to, to isolate the precise cause of the breakage. Fortunately, it wasn't necessary. So, there you have it folks. A happy conclusion to a lengthy and frustrating situation. Thanks again to all who responded and I hope this write-up may help someone else experiencing similar problems in the future. regards, - Carl Following are my direct replies to some individual posts: On Saturday 13 August 2005 15:23, Sid Boyce wrote:
I have always installed both Gnome and KDE mainly because there are certain Gnome apps that are not available in KDE and I build apps so all the devel packages are installed also, usually after I get the box up, even then some devel packages have to be dragged in as I hit bother. Apart from 9.1 --> 9.2 upgrades which took some voodoo to get going and in one case I had to do a fresh install without reformatting of 9.2 over 9.1 and I think 9.0 over 8.2 which is the ace up my sleeve as it leaves all the important stuff intact, they have otherwise always gone OK. Regards Sid.
I'm glad you know about that 'voodoo' stuff, Sid. It's certainly true you learn something new everyday... I hadn't even conceived that there might be occasions where one would want to overlay a newer release on top of an existing one. That's something only developers should do, right? ;-) Thanks again for your reply, too... very much appreciated. On Saturday 13 August 2005 07:50, Peter Vollebregt wrote:
Carl I have updated Suse in several ways and the only pitfall i never could solve were updates of gtk that messed up my system. This looks familiair. Try to downgrade gtk and see if that helps. If that is not possible try to update with newer packages. Maybe gwdg's apt repositories have newer versions.
So... am I the *only* person who has gotten into the habit of selecting Gnome, KDE Desktop /and/ All of KDE at the start of the installation?
I used to do this but since i don't use gnome and the repeated misery with gtk updates a ileave out nome and all gnome/gtk updates that are any better than security updates.
Peter
Thanks for the additional feedback, Peter. I'd heard that before and tried some futile gtk adjustments. I don't know the exact underlying cause and, honestly, at this point I don't care... I finally have my desktop back... in the new and improved version, no less... and running just the way it should be.
Carl E. Hartung wrote: < STUFF DELETED>
So... am I the *only* person who has gotten into the habit of selecting Gnome, KDE Desktop /and/ All of KDE at the start of the installation? If there are inherent conflicts when doing this, why didn't YaST2/rpm pick it up? Is there some other mechanism that should have alerted me that this would result in a less than satisfactory environment? This is my first bad experience with a SuSE installation, so I've probably been spoiled. I happen to like KDE /and/ Gnome. I've gotten used to switching between them depending on the program I want to run. Am I being forced to choose between them now?
Looking forward to any and all comments...
regards,
- Carl
I have always installed both Gnome and KDE mainly because there are certain Gnome apps that are not available in KDE and I build apps so all the devel packages are installed also, usually after I get the box up, even then some devel packages have to be dragged in as I hit bother. Apart from 9.1 --> 9.2 upgrades which took some voodoo to get going and in one case I had to do a fresh install without reformatting of 9.2 over 9.1 and I think 9.0 over 8.2 which is the ace up my sleeve as it leaves all the important stuff intact, they have otherwise always gone OK. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
participants (9)
-
Bruce Marshall -
Carl E. Hartung -
Carl Hartung
-
Jerry Westrick -
Peter Nikolic -
Peter Vollebregt -
Shriramana Sharma -
Sid Boyce -
Susemail