Greets; Ive noticed a very strange behaviour with Yast post updating to KDE3.3 suse rpms. All aspects of yast remain functional except "install software". If this is run the machine goes into complete lock-up in a few seconds after yast starts scanning what software has been installed. All efforts to resolve this (rebuilding the db etc etc) are fruitless. This behaviour started immediately post ugrading KDE by pointing yast to the suppplementary (and associated path) KDE rpms (exact path varies of course). The only other addition to the system was running an automated update shortly their after. Anyone have any ideas on what is going on here or how to repair this behaviour other then removing the SuSE supplied KDE rpms for 9.1? Yast remains broken on for adding and removing applications. All other aspects remain functional. Regards /ch
On Monday, 4 October 2004 16.50, Chris H wrote:
Greets;
Ive noticed a very strange behaviour with Yast post updating to KDE3.3 suse rpms. All aspects of yast remain functional except "install software". If this is run the machine goes into complete lock-up in a few seconds after yast starts scanning what software has been installed. All efforts to resolve this (rebuilding the db etc etc) are fruitless. This behaviour started immediately post ugrading KDE by pointing yast to the suppplementary (and associated path) KDE rpms (exact path varies of course). The only other addition to the system was running an automated update shortly their after.
Anyone have any ideas on what is going on here or how to repair this behaviour other then removing the SuSE supplied KDE rpms for 9.1? Yast remains broken on for adding and removing applications. All other aspects remain functional.
Works for me. Did you try removing the supplementary installation source? Maybe it's trying (unsuccessfully) to connect, and locking up while it's waiting for a timeout? If that's not it, do you get anything interesting in /var/log/YaST2/y2log ?
** Reply to message from Anders Johansson <andjoh@rydsbo.net> on Mon, 4 Oct 2004 17:00:25 +0200 (snipped) Welcome back, Anders! Really nice to see your posts again. ;o) Gil
On Monday 04 October 2004 05:15 am, Steve Kratz wrote:
Welcome back, Anders! Really nice to see your posts again. ;o) Gil
I was just going to say the same :)
No "flagged" post like normal, he's trying to sneak in through the back door.
WB Anders... We missed ya! Welcome back. Jerome
On Monday 04 October 2004 11:00, Anders Johansson wrote:
On Monday, 4 October 2004 16.50, Chris H wrote:
Greets;
Ive noticed a very strange behaviour with Yast post updating to KDE3.3 suse rpms. All aspects of yast remain functional except "install software". If this is run the machine goes into complete lock-up in a few seconds after yast starts scanning what software has been installed. All efforts to resolve this (rebuilding the db etc etc) are fruitless. This behaviour started immediately post ugrading KDE by pointing yast to the suppplementary (and associated path) KDE rpms (exact path varies of course). The only other addition to the system was running an automated update shortly their after.
Anyone have any ideas on what is going on here or how to repair this behaviour other then removing the SuSE supplied KDE rpms for 9.1? Yast remains broken on for adding and removing applications. All other aspects remain functional.
Works for me. Did you try removing the supplementary installation source? Maybe it's trying (unsuccessfully) to connect, and locking up while it's waiting for a timeout?
Yup and did an rpm --rebuilddb as well. No effect.
If that's not it, do you get anything interesting in /var/log/YaST2/y2log ?
[thanks all for the input btw] Not that I can tell. Copy of new y2log for this transaction posted here for review if interested. (to long to post in email) http://docs.opengroupware.org/Members/chris/y2log/view This one has me stumped. The only other information I can offer is that when testing Kmail 3.3 and running the anti-spam wizard, the main dialogue launches and then complete machine lockup. This is the only other time I can replicate a lockup behavior outside of yast. Now whats interesting is that I just reloaded 9.1 from the CD set to have a fresh install as things were getting way to cluttered with 4 OS's on this laptop. The previous 9.1 with KDE 3.3 from kde.org did not give any grief at all since the release date. I just thought I would try something different this time. Hence SuSE sources..and lockup....:) Any other idea's /ch
On Monday, 4 October 2004 18.29, Chris H wrote:
Not that I can tell. Copy of new y2log for this transaction posted here for review if interested. (to long to post in email)
http://docs.opengroupware.org/Members/chris/y2log/view
This one has me stumped.
Me too, I don't see anything wrong in that log
The only other information I can offer is that when testing Kmail 3.3 and running the anti-spam wizard, the main dialogue launches and then complete machine lockup. This is the only other time I can replicate a lockup behavior outside of yast.
Could you try running the ncurses version of yast (ie. running 'yast' instead of 'yast2' from a command line as root)? Maybe it's a qt/X problem that depends on your specific config for some weird reason?!
On Monday 04 October 2004 19:09, Anders Johansson wrote:
On Monday, 4 October 2004 18.29, Chris H wrote:
Not that I can tell. Copy of new y2log for this transaction posted here for review if interested. (to long to post in email)
http://docs.opengroupware.org/Members/chris/y2log/view
This one has me stumped.
Me too, I don't see anything wrong in that log
The only other information I can offer is that when testing Kmail 3.3 and running the anti-spam wizard, the main dialogue launches and then complete machine lockup. This is the only other time I can replicate a lockup behavior outside of yast.
Could you try running the ncurses version of yast (ie. running 'yast' instead of 'yast2' from a command line as root)? Maybe it's a qt/X problem that depends on your specific config for some weird reason?!
Chris: you might also want to try to run the module directly: yast sw_single starts the package manager, yast --list lists all available modules. When yast itself starts a module, it blocks the console output from the module, in contrast of running the module directly. Cheers, Leen
On Monday 04 October 2004 13:56, Leendert Meyer wrote:
Chris: you might also want to try to run the module directly:
yast sw_single
starts the package manager,
yast --list
Thanks I did not know the command set. At least I am learning something here. Tried it, same behavior, complete system lockup requiring forced shutdown. ie: turn off power..:) tks /ch
On Monday 04 October 2004 13:09, Anders Johansson wrote:
Could you try running the ncurses version of yast (ie. running 'yast' instead of 'yast2' from a command line as root)? Maybe it's a qt/X problem that depends on your specific config for some weird reason?!
Tried that. No go..:) Same problem What is strange here is that this is the first time I have experienced this with Yast on 9.1 on say may 30 installs. The only thing different was the source for the KDE rpm's. All other machines currently in my office (3 in total) are all at the same update level and no concerns what so ever. In fact the current laptop was fine as well other then reinstalling SuSE 9.1 (clean not overwritten) to make some extra space. Ran fine for months. Completely clueless in Ottawa..:) TKS for your patience.. /ch
What is strange here is that this is the first time I have experienced this with Yast on 9.1 on say may 30 installs. The only thing different was the source for the KDE rpm's. All other machines currently in my office (3 in total) are all at the same update level and no concerns what so ever. In fact the current laptop was fine as well other then reinstalling SuSE 9.1 (clean not overwritten) to make some extra space. Ran fine for months.
Completely clueless in Ottawa..:)
TKS for your patience..
Logged in with different users? dumped /tmp stuff?
On Monday 04 October 2004 15:07, Steve Kratz wrote:
Completely clueless in Ottawa..:)
TKS for your patience..
Logged in with different users? dumped /tmp stuff?
Yup and yup. No joy. Reinstalled from scratch and used rpm's from kde.org and its seamless as always. No issue for the last few hrs at all. In short, not repeatable What puzzles me is that I have no clue why this issue arose. This is what is perplexing as it will reappear at some point again when its not practical to reinstall everything. Thanks for you help everyone. Much appreciated. /ch
On Monday 04 October 2004 13:09, Anders Johansson wrote:
Could you try running the ncurses version of yast (ie. running 'yast' instead of 'yast2' from a command line as root)? Maybe it's a qt/X problem that depends on your specific config for some weird reason?!
Tried that. No go..:) Same problem tks /ch
On Mon, 2004-10-04 at 18:29, Chris H wrote:
On Monday 04 October 2004 11:00, Anders Johansson wrote:
On Monday, 4 October 2004 16.50, Chris H wrote:
Greets;
Ive noticed a very strange behaviour with Yast post updating to KDE3.3 suse rpms. All aspects of yast remain functional except "install software". If this is run the machine goes into complete lock-up in a few seconds after yast starts scanning what software has been installed. All efforts to resolve this (rebuilding the db etc etc) are fruitless. This behaviour started immediately post ugrading KDE by pointing yast to the suppplementary (and associated path) KDE rpms (exact path varies of course). The only other addition to the system was running an automated update shortly their after.
Anyone have any ideas on what is going on here or how to repair this behaviour other then removing the SuSE supplied KDE rpms for 9.1? Yast remains broken on for adding and removing applications. All other aspects remain functional.
Works for me. Did you try removing the supplementary installation source? Maybe it's trying (unsuccessfully) to connect, and locking up while it's waiting for a timeout?
Yup and did an rpm --rebuilddb as well. No effect.
If that's not it, do you get anything interesting in /var/log/YaST2/y2log ?
[thanks all for the input btw]
Not that I can tell. Copy of new y2log for this transaction posted here for review if interested. (to long to post in email)
http://docs.opengroupware.org/Members/chris/y2log/view
This one has me stumped. The only other information I can offer is that when testing Kmail 3.3 and running the anti-spam wizard, the main dialogue launches and then complete machine lockup. This is the only other time I can replicate a lockup behavior outside of yast.
Now whats interesting is that I just reloaded 9.1 from the CD set to have a fresh install as things were getting way to cluttered with 4 OS's on this laptop. The previous 9.1 with KDE 3.3 from kde.org did not give any grief at all since the release date. I just thought I would try something different this time. Hence SuSE sources..and lockup....:)
Any other idea's
/ch
Hardware related? Jerry. P.S. I have the KDE 3.3 sources still active with no problems so I don't think that's going to be the problem...
On Monday 04 October 2004 13:11, Jerome R. Westrick wrote:
Hardware related?
Well that cannot be a variable as KDE3.3 from KDE.org has been on this laptop with stock 9.1 for approx what 2 months now? Not a single hardware/software isssue so that cannot be a variable. As stated 9.1/KDE3.3 were fine on this laptop until yesterday when reinstalled 9.1 tested everything and configured/customized the install to where I wanted it. Then finally upgraded to KDE3.3 but this time from SuSE and...well the rest you know..:) tks anyways /ch
On Monday 04 October 2004 14:30, Chris H wrote: Tks for everyones help. Much appreciated. Reinstallation of 9.1 and 3.3 in progress..:) Need to get this one done now. till later /ch
On Mon, 2004-10-04 at 16:50, Chris H wrote:
Greets;
Ive noticed a very strange behaviour with Yast post updating to KDE3.3 suse rpms. All aspects of yast remain functional except "install software". If this is run the machine goes into complete lock-up in a few seconds after yast starts scanning what software has been installed. All efforts to resolve this (rebuilding the db etc etc) are fruitless. This behaviour started immediately post ugrading KDE by pointing yast to the suppplementary (and associated path) KDE rpms (exact path varies of course). The only other addition to the system was running an automated update shortly their after.
Anyone have any ideas on what is going on here or how to repair this behaviour other then removing the SuSE supplied KDE rpms for 9.1? Yast remains broken on for adding and removing applications. All other aspects remain functional.
Regards
/ch
Funny, I don't see theese symptoms, and I've done the KDE 3.3 update also... Jerry
Anyone have any ideas on what is going on here or how to repair this behaviour other then removing the SuSE supplied KDE rpms for 9.1? Yast remains broken on for adding and removing applications. All other aspects remain functional.
Well, install software, I believe, reads all of the install sources that are defined/active. Have you tried setting your install sources to just your cd/dvd source? It might not be reading a supplemental source properly. Steve
participants (7)
-
Anders Johansson -
Chris H -
Gil Weber -
Jerome Lyles -
Jerome R. Westrick -
Leendert Meyer -
Steve Kratz