Mailinglist Archive: opensuse-bugs (8045 mails)
| < Previous | Next > |
[Bug 230673] Too much trouble with ZMD in opensuse 10.2
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Fri, 29 Dec 2006 08:06:02 -0700 (MST)
- Message-id: <20061229150602.4214725C887@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=230673
f.alabas@xxxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Major |Critical
Priority|P5 - None |P1 - Urgent
Summary|zen-updater updates from |Too much trouble with ZMD in opensuse 10.2
|unsubscribed catalogs |
|instead of subscribed |
|official suse update catalog|
------- Comment #1 from f.alabas@xxxxxxxxxxxx 2006-12-29 08:06 MST -------
I have already experienced ZMD very long time with Suse Linux 10 and 10.1,
however I see that zmd has big problems with opensuse 10.2. I am not sure to
list them all here or open bug reports for each of them. Anyway as a starting
point I will list them here from minor to most critical ones.
1) After a successful update with zen-updater, the update notification sign in
the KDE panel still notifies, although there is no update. Then I need to
restart the zmd to clear this dummy notification.
2) When one/some of the repositories are unreachable, there is no notification
on the KDE panel.
3) When I add a repository using zen it is NOT automatically added into Yast's
package management as installation source. I need to add it again separately
using Yast itself.
4) The problem which is the one as already explained in my previous report.
5) When shutting down the system, RANDOMLY zmd can not be shutdown by the
system. I see the red failed message on the shutdown screen. Then after
next-boot zen-updater says that ZMD is not working, although it is working. I
try stoping or restrating the zmd, but it fails. I need to reboot to make the
zmd-related things work again.
6) Similarly as problem 5, when RANDOMLY zmd fails to be stopped during
shutdown, then after next-boot, some of the repositories are lost in the
zen-updater configuration. Restaring the zmd, zen-updater and rebooting does
not work, I manually need to add the lost repositories again.
7) Similarly as problem 5 & 6, after suspend/resume operation, zen-updater says
that either ZMD is not working ( so I reboot the machine ) or some of the
repositories are lost ( so I add them again )
8) After a normal boot or when refreshing, zmd tries to find the services and
refreshes the files, that's ok. But, during these operation zmd eats all the
CPU power of my machine and almost does not let another application work. So,
trying to do some work during the zmd restarting/refreshing is fooling. My 1.8
GHz Turion 64 with 1 GByte RAM and 128 MByte ATI collapses.
When I compare these 8 problems of ZMD with the ZMD in SL10.1, only problem 2
is common !?
I attach the necessary log files.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
f.alabas@xxxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Major |Critical
Priority|P5 - None |P1 - Urgent
Summary|zen-updater updates from |Too much trouble with ZMD in opensuse 10.2
|unsubscribed catalogs |
|instead of subscribed |
|official suse update catalog|
------- Comment #1 from f.alabas@xxxxxxxxxxxx 2006-12-29 08:06 MST -------
I have already experienced ZMD very long time with Suse Linux 10 and 10.1,
however I see that zmd has big problems with opensuse 10.2. I am not sure to
list them all here or open bug reports for each of them. Anyway as a starting
point I will list them here from minor to most critical ones.
1) After a successful update with zen-updater, the update notification sign in
the KDE panel still notifies, although there is no update. Then I need to
restart the zmd to clear this dummy notification.
2) When one/some of the repositories are unreachable, there is no notification
on the KDE panel.
3) When I add a repository using zen it is NOT automatically added into Yast's
package management as installation source. I need to add it again separately
using Yast itself.
4) The problem which is the one as already explained in my previous report.
5) When shutting down the system, RANDOMLY zmd can not be shutdown by the
system. I see the red failed message on the shutdown screen. Then after
next-boot zen-updater says that ZMD is not working, although it is working. I
try stoping or restrating the zmd, but it fails. I need to reboot to make the
zmd-related things work again.
6) Similarly as problem 5, when RANDOMLY zmd fails to be stopped during
shutdown, then after next-boot, some of the repositories are lost in the
zen-updater configuration. Restaring the zmd, zen-updater and rebooting does
not work, I manually need to add the lost repositories again.
7) Similarly as problem 5 & 6, after suspend/resume operation, zen-updater says
that either ZMD is not working ( so I reboot the machine ) or some of the
repositories are lost ( so I add them again )
8) After a normal boot or when refreshing, zmd tries to find the services and
refreshes the files, that's ok. But, during these operation zmd eats all the
CPU power of my machine and almost does not let another application work. So,
trying to do some work during the zmd restarting/refreshing is fooling. My 1.8
GHz Turion 64 with 1 GByte RAM and 128 MByte ATI collapses.
When I compare these 8 problems of ZMD with the ZMD in SL10.1, only problem 2
is common !?
I attach the necessary log files.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
| < Previous | Next > |