Bug 200840

Summary:	zen-updater locked out somehow
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Robert Harvey <bobharvey>
Component:	Zenworks	Assignee:	E-mail List <zlm-code10-bugs>
Status:	RESOLVED INVALID	QA Contact:	Jawaad Tariq <jtariq>
Severity:	Normal
Priority:	P5 - None	CC:	andreas.hanke, suse-beta
Version:	Final
Target Milestone:	---
Hardware:	i586
OS:	SuSE Linux 10.1
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Screen grab of the failure

Description Robert Harvey 2006-08-22 11:32:44 UTC

OK, after the events that led to bugs 200828 and 200830 I rebooted and logged in as root (because of bug 200544) and ran the updater again.  When it condescended to complete it's internet furklings I pressed OK, and nothing happened.  (Certainly nothing happened for long enough that I had time to submit 200832 200833 200835) Then I got the enclosed desktop.

It isn't true.  I had done a clean reboot, and had not run yast, and there were no other isntances of zen-updater running.

I suspect something got stuck in the database from my earlier problems, but surely  such locking mechanisms should not survive a reboot?

Is there a manual way to repair the database from the command line?  I have not found any significant documentation anywhere.

Comment 1 Robert Harvey 2006-08-22 11:33:37 UTC

Created attachment 96764 [details]
Screen grab of the failure

Comment 2 Mauro Parra Miranda 2006-10-12 00:10:20 UTC

Please attach:

/var/log/zmd-messages.log 
/var/log/zmd-backend.log

TIA!

Comment 3 Stanislav Visnovsky 2007-02-20 15:06:17 UTC

No logs provided. Please, reopen if happens again and attach the logs.