update-notifier and -manager
update-notifier and -manager
This is the first time I have seen this in operation, now that Kent's simple proposal to delete that file (forget the name) works.
I tested this following a suggestion of Kent's in the following way:
1) enable a new repo:
deb
http://ftp.us.debian.org/debian/ [NOTE: substitute your favorite code in place of "us" if not in the US of A]
wheezy-proposed-updates
contrib non-free main
2) update and upgrade [NOTE: I suppose it would eventually catch up, not sure whether the repo needs somehow to be made active]
3) click on the yellow icon that appears in the Notification Area
4) up pops update-manager (also is a menu entry) with possible updates listed
5) I unchecked all except "whois," install went without a hitch.
Questions I have
--technical: how can that erroneous file be corrected during/after install?
--user: my root pwd was not requested, which surprised me. I see a good argument that packages already installed by the user do not need the same level of permissions that new installs need, but what do you think?
Certainly much nicer for the user IMHO.
I tested this following a suggestion of Kent's in the following way:
1) enable a new repo:
deb
http://ftp.us.debian.org/debian/ [NOTE: substitute your favorite code in place of "us" if not in the US of A]
wheezy-proposed-updates
contrib non-free main
2) update and upgrade [NOTE: I suppose it would eventually catch up, not sure whether the repo needs somehow to be made active]
3) click on the yellow icon that appears in the Notification Area
4) up pops update-manager (also is a menu entry) with possible updates listed
5) I unchecked all except "whois," install went without a hitch.
Questions I have
--technical: how can that erroneous file be corrected during/after install?
--user: my root pwd was not requested, which surprised me. I see a good argument that packages already installed by the user do not need the same level of permissions that new installs need, but what do you think?
Certainly much nicer for the user IMHO.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: update-notifier and -manager
Are you talking about the /etc/lsb-release file, or something else?Jerry3904 wrote:... --technical: how can that erroneous file be corrected during/after install? ...
I'm getting a gksu authentication box before update-manager will start:Jerry3904 wrote: ... --user: my root pwd was not requested, which surprised me. I see a good argument that packages already installed by the user do not need the same level of permissions that new installs need, but what do you think?...
{the screenshot below is from my sid install, but I'm pretty sure it will do the same on MX14} Had you previously done some other things that used gksu for authentication, and you didn't clear the "Remember password" checkbox?
Last edited by kmathern on Thu Jan 23, 2014 11:39 am, edited 1 time in total.
Re: update-notifier and -manager
Yes, that file
Maybe, will check. Glad that you are seeing it.
Maybe, will check. Glad that you are seeing it.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
- chrispop99
- Global Moderator
- Posts: 3171
- Joined: Tue Jan 27, 2009 3:07 pm
Re: update-notifier and -manager
I can confirm that changing repos to force an update, then logging out/in causes update manager to trigger, and then the root passwd is needed to proceed.Jerry3904 wrote: Questions I have
--user: my root pwd was not requested, which surprised me. I see a good argument that packages already installed by the user do not need the same level of permissions that new installs need, but what do you think?.
Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines
Re: update-notifier and -manager
So that seems to leave us with that file issue.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: update-notifier and -manager
There are two ways to modify the file.Jerry3904 wrote:So that seems to leave us with that file issue.
1. at install time, the installer can be modified to replace/remove file or replace strings in a file
2. after install with an update, ask Stevo or other packagers I think there's relatively easy to replace/remove files with a deb.
Re: update-notifier and -manager
How's the /etc/lsb-release file created in the first place? Isn't it just a text file that you or anticapitalista create? If that's the case couldn't you (or anti) just change the file before remastering the iso?Adrian wrote:There are two ways to modify the file.Jerry3904 wrote:So that seems to leave us with that file issue.
1. at install time, the installer can be modified to replace/remove file or replace strings in a file
2. after install with an update, ask Stevo or other packagers I think there's relatively easy to replace/remove files with a deb.
- anticapitalista
- Developer
- Posts: 4160
- Joined: Sat Jul 15, 2006 10:40 am
Re: update-notifier and -manager
It can be changed. Then, when grub is installed to MBR, the boot menu shows Debian rather than MX-14
anticapitalista
Reg. linux user #395339.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - lean and mean.
https://antixlinux.com
Reg. linux user #395339.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - lean and mean.
https://antixlinux.com
Re: update-notifier and -manager
I think that comes from the GRUB_DISTRIBUTOR line in the /etc/default/grub fileanticapitalista wrote:It can be changed. Then, when grub is installed to MBR, the boot menu shows Debian rather than MX-14
I wonder if you could change that line to: GRUB_DISTRIBUTOR="MX-14"$ head /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` <==
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
- anticapitalista
- Developer
- Posts: 4160
- Joined: Sat Jul 15, 2006 10:40 am
Re: update-notifier and -manager
I tried that before and grub failed to boot. I'll try it again.
anticapitalista
Reg. linux user #395339.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - lean and mean.
https://antixlinux.com
Reg. linux user #395339.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - lean and mean.
https://antixlinux.com