SPAM: To all users of smart package manager
Several days ago smart was upgraded to .42-14 and I noticed that the ksmarttray now does not update the channels on bootup nor at the regular intervals while the system was running as in the past. I have to manually use the package manager to update the channels (and in most cases I find that there are upgrades waiting to be performed). Anyone else having the same experience? I asked in the smart mail list if something had changed in smart but was told (by Pascal Bleser) that nothing had changed. Nevertheless smart (ksmarttray that is) is not behaving as it did in the past so something has changed somewhere. Cheers. -- "Every burned book enlightens the world." Ralph Waldo Emerson
On 10/11/06, Basil Chupin <blchupin@tpg.com.au> wrote:
Several days ago smart was upgraded to .42-14 and I noticed that the ksmarttray now does not update the channels on bootup nor at the regular intervals while the system was running as in the past. I have to manually use the package manager to update the channels (and in most cases I find that there are upgrades waiting to be performed).
Anyone else having the same experience?
I have had this problem for quite some time. It also started after an upgrade, but I'm not sure which one ( I didn't notice it immediately). I'm still on 0.42-13 though, for exactly this reason I would guess. Should I check for updates through the Smart GUI, there would probably be many, but the ksmarttray shows nothing. No solution though, I was just hoping a new version will solve it (obviously 0.42-14 is not it :) Marius
On Wednesday 11 October 2006 05:11, Basil Chupin wrote:
Several days ago smart was upgraded to .42-14 and I noticed that the ksmarttray now does not update the channels on bootup nor at the regular intervals while the system was running as in the past. I have to manually use the package manager to update the channels (and in most cases I find that there are upgrades waiting to be performed).
Anyone else having the same experience?
I asked in the smart mail list if something had changed in smart but was told (by Pascal Bleser) that nothing had changed. Nevertheless smart (ksmarttray that is) is not behaving as it did in the past so something has changed somewhere.
Hi Basil, Hate to ask the obvious, but I believe you ended up configuring things as I do, so did you ensure smart-update is setuid after the upgrade? If the smart package is updated a fresh version of this binary is installed without setuid, which causes those symptoms. You need the line: /usr/bin/smart-update root.root 4755 in /etc/permissions.local, but whenever you see smart updated (should be done everytime you do an update of anything really) you need to run SuSEconfig as root. This will set the setuid flag on the file, and ksmarttray will do the right thing again. Regards -- Steve Boddy
Stephen Boddy wrote:
On Wednesday 11 October 2006 05:11, Basil Chupin wrote:
Several days ago smart was upgraded to .42-14 and I noticed that the ksmarttray now does not update the channels on bootup nor at the regular intervals while the system was running as in the past. I have to manually use the package manager to update the channels (and in most cases I find that there are upgrades waiting to be performed).
Anyone else having the same experience?
I asked in the smart mail list if something had changed in smart but was told (by Pascal Bleser) that nothing had changed. Nevertheless smart (ksmarttray that is) is not behaving as it did in the past so something has changed somewhere.
Hi Basil,
Hate to ask the obvious, but I believe you ended up configuring things as I do, so did you ensure smart-update is setuid after the upgrade? If the smart package is updated a fresh version of this binary is installed without setuid, which causes those symptoms. You need the line: /usr/bin/smart-update root.root 4755 in /etc/permissions.local, but whenever you see smart updated (should be done everytime you do an update of anything really) you need to run SuSEconfig as root. This will set the setuid flag on the file, and ksmarttray will do the right thing again.
Regards
BINGO! All in place as set up some time ago - but forgot to run SuSEconfig! Thanks, Stephen, ksmarttray now working correctly again :-) . Cheers. -- "Every burned book enlightens the world." Ralph Waldo Emerson
Basil Chupin wrote:
Stephen Boddy wrote:
... but whenever you see smart updated (should be done everytime you do an update of anything really) you need to run SuSEconfig as root. This will set the setuid flag on the file, and ksmarttray will do the right thing again.
Regards
BINGO!
All in place as set up some time ago - but forgot to run SuSEconfig!
Thanks, Stephen, ksmarttray now working correctly again :-) .
Cheers.
Hi all, Saw Stephen's post about running SuSeconfig after an update. Would this also apply to ZMD? I did some work about 3 weeks ago, to get rid of the zmd not running message. It appears to be running now, but I have not seen an update since. I am using SuSE 10.1. --ED--
Ed McCanless wrote:
Basil Chupin wrote:
Stephen Boddy wrote:
... but whenever you see smart updated (should be done everytime you do an update of anything really) you need to run SuSEconfig as root. This will set the setuid flag on the file, and ksmarttray will do the right thing again.
Regards
BINGO!
All in place as set up some time ago - but forgot to run SuSEconfig!
Thanks, Stephen, ksmarttray now working correctly again :-) .
Cheers.
Hi all, Saw Stephen's post about running SuSeconfig after an update. Would this also apply to ZMD? I did some work about 3 weeks ago, to get rid of the zmd not running message. It appears to be running now, but I have not seen an update since. I am using SuSE 10.1.
I have absolutely no idea if this would apply to zmd--but I doubt that it would. Cheers. -- "Every burned book enlightens the world." Ralph Waldo Emerson
We had a SLES 9.3 32-bit machine in our lab whose default KDE desktop was replaced by a few blue GUI boxes. I figured out that one of them was a console, and started KDE by typing in "kde" at a command prompt. KDE did start up at at that point, but there were new graphical icons on the KDE desktop which reflected those I'd seen on the first screen. What's the first set of icons, and how did this "spontaneous" upgrade occur? Could it have come from an upgrade performed automatically overnight? I was blamed for having changed the default desktop, and I took no such action. ================================================ George Falcon, Sr. Systems Engineer, GEICO HQ Software Distribution Team ================================================ ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message.
On 10/11/06, Stephen Boddy <stephen.boddy@btinternet.com> wrote:
On Wednesday 11 October 2006 05:11, Basil Chupin wrote:
Hi Basil,
Hate to ask the obvious, but I believe you ended up configuring things as I do, so did you ensure smart-update is setuid after the upgrade? If the smart package is updated a fresh version of this binary is installed without setuid, which causes those symptoms. You need the line: /usr/bin/smart-update root.root 4755 in /etc/permissions.local, but whenever you see smart updated (should be done everytime you do an update of anything really) you need to run SuSEconfig as root. This will set the setuid flag on the file, and ksmarttray will do the right thing again.
Hehe, same problem here. Thanks Steve. Marius
participants (5)
-
Basil Chupin -
Ed McCanless -
Falcon, George -
Marius Roets -
Stephen Boddy