[opensuse-factory] zen bug?
until the last zen update, my 10.1 installation send this message at starting time: System.NullReferenceException: Object reference not set to an instance of an object in <0x003d6> Novell.Zenworks.Gui.ZenTrayIcon:CheckUpdatesLoop () in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () however I still have the zen icon in the tray. is this something worth a bug report? thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi,
until the last zen update, my 10.1 installation send this message at starting time:
System.NullReferenceException: Object reference not set to an instance of an object in <0x003d6> Novell.Zenworks.Gui.ZenTrayIcon:CheckUpdatesLoop () in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
however I still have the zen icon in the tray.
Nice backtrace, isn't it?
is this something worth a bug report?
No, it is not worth a bug report. Andreas -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
andreas.hanke@gmx-topmail.de a écrit :
Hi,
until the last zen update, my 10.1 installation send this message at starting time:
System.NullReferenceException: Object reference not set to an instance of an object in <0x003d6> Novell.Zenworks.Gui.ZenTrayIcon:CheckUpdatesLoop () in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
however I still have the zen icon in the tray.
Nice backtrace, isn't it?
?? I did not do anything to have this and it didn't show before
is this something worth a bug report?
No, it is not worth a bug report.
Andreas
ok jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
jdd schrieb:
?? I did not do anything to have this and it didn't show before
Maybe you did not do anything, but the resolve-dependencies zypp helper did something: It segfaulted. This caused zmd.db to be left in an unusable state. Zen-Updater likes to show exactly this stack trace whenever that happens. It's the most well-known one. Use Google: http://www.google.com/search?q=CheckUpdatesLoop While the resolve-dependencies segfault has been fixed in the meantime, the stack trace from Zen-Updater will _never_ be fixed. It's already in Bugzilla with 6 duplicates. Resolution: WORKSFORME Just forget it... Whenever this happens, you have to do: killall zen-updater /etc/init.d/novell-zmd stop rm -f /var/lib/zmd/zmd.db /etc/init.d/novell-zmd start zen-updater & Btw. this was a stack trace, not a backtrace. Backtraces are from the C/C++ world... Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Andreas Hanke a écrit :
jdd schrieb:
?? I did not do anything to have this and it didn't show before
Maybe you did not do anything, but the resolve-dependencies zypp helper did something: It segfaulted.
may be there was a problem with the last ipdate, the problem shows only until then
This caused zmd.db to be left in an unusable state. Zen-Updater likes to show exactly this stack trace whenever that happens. It's the most well-known one. Use Google:
http://www.google.com/search?q=CheckUpdatesLoop
While the resolve-dependencies segfault has been fixed in the meantime, the stack trace from Zen-Updater will _never_ be fixed. It's already in Bugzilla with 6 duplicates. Resolution: WORKSFORME
Just forget it... Whenever this happens, you have to do:
killall zen-updater /etc/init.d/novell-zmd stop rm -f /var/lib/zmd/zmd.db /etc/init.d/novell-zmd start zen-updater &
done, thanks
Btw. this was a stack trace, not a backtrace. Backtraces are from the C/C++ world...
Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
I add some words to inform anybody. http://en.opensuse.org/Using_zen-updater#Small_bug_fix thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
jdd schrieb:
may be there was a problem with the last ipdate, the problem shows only until then
The problem will disappear with libzypp 2.4.0. And come back next time something bad happens to your zmd.db for whatever reason. ;-)
I add some words to inform anybody.
That's not a bugfix. But the information is useful nevertheless as the 99 Google hits show. Btw. most bulletin boards explicitly lock out the googlebot. That's why there are just 99 hits - these could just as well be 999. ;-) So, thanks, I will direct people to that wiki page in the future. It makes life much easier because typing these commands again and again in user forums bec{omes,ame} boring. ;-) But there is a tiny mistake in it, because the problem is _not_ restricted to 10.1, 10.2 will have it as well. SLED10 anyone? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Andreas Hanke a écrit :
That's not a bugfix.
please, correct the title to be more appropriate, I'm short of idea :-(
So, thanks, I will direct people to that wiki page in the future. It makes life much easier because typing these commands again and again in user forums bec{omes,ame} boring. ;-)
the wiki is here for that purpose :-)
But there is a tiny mistake in it, because the problem is _not_ restricted to 10.1, 10.2 will have it as well. SLED10 anyone?
?? I had understood that with 10.2 zen should fix the database itself? jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
jdd schrieb:
?? I had understood that with 10.2 zen should fix the database itself?
You're confusing stuff here. A software named "zen" does not exist. There is Zenworks, which consists of different programs: zmd, the daemon rug, a CLI interface for the daemon zen-updater, a GUI interface for the daemon zmd in 10.1 crashes on startup if /var/lib/zmd/zmd.db is corrupted. zmd in 10.2 does not, but fixes the database instead, which is cool. Actually I think it crashed inside sqlite code, so it was not even zmd's fault. rug never crashes, neither in 10.1 nor 10.2. zen-updater in both 10.1 and 10.2 crashes when communicating with a zmd that has a corrupted database, even if zmd itself does not crash, because of an unhandled exception in the GUI code. These are totally different programs and totally different crashes, and a fix for one of them does not fix the other one. Theoretically, the zmd improvements should totally hide the zen-updater crash because zmd fixes the database on startup. But this doesn't work because the database can become corrupted _while_zmd_is_running_. And that's exactly what happened to you, because a zypp helper crashed while zmd was running. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Andreas Hanke a écrit :
jdd schrieb:
?? I had understood that with 10.2 zen should fix the database itself?
You're confusing stuff here.
I like your presentation. With it I think I begin to understand the all thing (not completely sure, but it comes :-). So, after some searching on the wiki, I thought the all Zenworks stuff was a bit confusing and add an other page named simply "Zenworks", mostly made with your letter. I added to this page as many links I could http://en.opensuse.org/Zenworks it needs certainly to be completed by people better informed than I am on the subject, but it's a starting point. I also renamed the other section, so you may need to update your pointer if it used the section part (the page title didn't change) http://en.opensuse.org/Using_zen-updater#Why_zen-updater_crashes Zenworks is probably a nice piece of code, but there have been so many trouble on it with 10.1 than clearing things can't be bad. thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Andreas Hanke -
andreas.hanke＠gmx-topmail.de
-
jdd