This past weekend I used YOU to update all four of the SuSE 7.3 machines on my network. Everything seemed to run to completion without error during the download and install phases. However, once YOU had finished, I logged root off, logged in as my regular user and launched KDE2 which was one of the packages updated by YOU. The instant the mouse pointer touched an icon on the desktop - the entire desktop crashed. The only exit at that point was Ctrl-Alt-Bkspc to kill the X server. This was true on all four systems, for all users including root. I finally gave up trying to determine just what was wrong and re-installed kde2 from the SuSE CD's, but I would really like to know what went wrong and how to avoid the hassle in the future. Plus, I'd like to ensure that future YOU updates don't cause a similar problem in other packages. JimW
On Monday 26 August 2002 08:30 pm, Jim Westbrook wrote:
The instant the mouse pointer touched an icon on the desktop - the entire desktop crashed. The only exit at that point was Ctrl-Alt-Bkspc to kill the X server. This was true on all four systems, for all users including root.
Surely there must be more to go on than that... Anything in the Xserver logs or any of the other logs? -- _________________________________________________ No I Don't Yahoo! And I'm getting pretty sick of being asked if I do. _________________________________________________ John Andersen / Juneau Alaska
Not much. Here's the entire .xsession-error file from root's attempt. ====================== den2:~ # cat .xsession-errors iceauth: creating new authority file /root/.ICEauthority DCOPServer up and running. DCOP aborting call from 'anonymous-1431' to 'kinternet' ERROR: KUniqueApplication: DCOP communication error! X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 7 (X_ReparentWindow) Resource id in failed request: 0x1e00011 Serial number of failed request: 49642 Current serial number in output stream: 49731 kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. warning: leaving MCOP Dispatcher and still 11 object references alive. - Arts::SampleStorage - Arts::Synth_MULTI_ADD - Arts::Synth_MULTI_ADD - Arts::Synth_PLAY - Arts::StereoVolumeControl - Arts::StereoEffectStack - Arts::Synth_BUS_DOWNLINK - Arts::SoundServerV2 - Arts::WavPlayObject - Arts::Synth_BUS_UPLINK - Arts::MidiManager warning: leaving MCOP Dispatcher and still 112 types alive. KLauncher: Exiting on signal 1 ICE default IO error handler doing an exit(), pid = 1430, errno = 0 kdeinit: sending SIGTERM to children. kdeinit: Exit. ==================== JimW John Andersen wrote:
On Monday 26 August 2002 08:30 pm, Jim Westbrook wrote:
The instant the mouse pointer touched an icon on the desktop - the entire desktop crashed. The only exit at that point was Ctrl-Alt-Bkspc to kill the X server. This was true on all four systems, for all users including root.
Surely there must be more to go on than that... Anything in the Xserver logs or any of the other logs?
Well. I always delete all things from /tmp along with the .mcop directory and .mcoprc. Also since your using 2.x.x you should delete .DCOP* in your home directory. Then go into .kde2 and delete the two temp files that point to directories in /tmp. After every update to KDE I do this and quite frankly I think YaST2, YaST...or even just SuSEconfig should do this. For SOME reason..God knows why..this fixes issues such as this. * Jim Westbrook (jimw@austin.rr.com) [020826 22:09]: ::Not much. Here's the entire .xsession-error file from root's attempt. :: ::====================== ::den2:~ # cat .xsession-errors ::iceauth: creating new authority file /root/.ICEauthority ::DCOPServer up and running. ::DCOP aborting call from 'anonymous-1431' to 'kinternet' ::ERROR: KUniqueApplication: DCOP communication error! ::X Error of failed request: BadWindow (invalid Window parameter) :: Major opcode of failed request: 7 (X_ReparentWindow) :: Resource id in failed request: 0x1e00011 :: Serial number of failed request: 49642 :: Current serial number in output stream: 49731 ::kdeinit: Fatal IO error: client killed ::kdeinit: sending SIGHUP to children. ::warning: leaving MCOP Dispatcher and still 11 object references alive. :: - Arts::SampleStorage :: - Arts::Synth_MULTI_ADD :: - Arts::Synth_MULTI_ADD :: - Arts::Synth_PLAY :: - Arts::StereoVolumeControl :: - Arts::StereoEffectStack :: - Arts::Synth_BUS_DOWNLINK :: - Arts::SoundServerV2 :: - Arts::WavPlayObject :: - Arts::Synth_BUS_UPLINK :: - Arts::MidiManager ::warning: leaving MCOP Dispatcher and still 112 types alive. ::KLauncher: Exiting on signal 1 ::ICE default IO error handler doing an exit(), pid = 1430, errno = 0 ::kdeinit: sending SIGTERM to children. ::kdeinit: Exit. ::==================== :: ::JimW :: ::John Andersen wrote: ::> ::> On Monday 26 August 2002 08:30 pm, Jim Westbrook wrote: ::> ::> >The instant the mouse pointer ::> > touched an icon on the desktop - the entire desktop crashed. The only ::> > exit at that point was Ctrl-Alt-Bkspc to kill the X server. This was ::> > true on all four systems, for all users including root. ::> > ::> ::> ::> Surely there must be more to go on than that... ::> Anything in the Xserver logs or any of the other logs? :: ::-- ::Check the headers for your unsubscription address ::For additional commands, e-mail: suse-security-help@suse.com ::Security-related bug reports go to security@suse.de, not here :: -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I tell you what you should see.
participants (3)
-
Ben Rosenberg -
Jim Westbrook -
John Andersen