Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #200962 > unrolled thread

Problem updating to Buster - gparted effectively MIA

Back to article view | Back to linux.debian.user

Contents

  Problem updating to Buster - gparted effectively MIA Richard Owlett <rowlett@cloud85.net> - 2018-10-07 15:20 +0200
    Re: Problem updating to Buster - gparted effectively MIA Reco <recoverym4n@enotuniq.net> - 2018-10-07 16:00 +0200
      Re: Problem updating to Buster - gparted effectively MIA Richard Owlett <rowlett@cloud85.net> - 2018-10-07 16:20 +0200
        Re: Problem updating to Buster - gparted effectively MIA Reco <recoverym4n@enotuniq.net> - 2018-10-07 16:30 +0200
          Re: Problem updating to Buster - gparted effectively MIA Richard Owlett <rowlett@cloud85.net> - 2018-10-08 15:50 +0200
            Re: Problem updating to Buster - gparted effectively MIA Reco <recoverym4n@enotuniq.net> - 2018-10-08 17:50 +0200
              Re: Problem updating to Buster - gparted effectively MIA Richard Owlett <rowlett@cloud85.net> - 2018-10-08 22:30 +0200
                Re: Problem updating to Buster - gparted effectively MIA Reco <recoverym4n@enotuniq.net> - 2018-10-08 22:50 +0200
              Re: Problem updating to Buster - gparted effectively MIA Richard Owlett <rowlett@cloud85.net> - 2018-10-09 17:20 +0200
                Re: Problem updating to Buster - gparted effectively MIA Brian <ad44@cityscape.co.uk> - 2018-10-09 18:30 +0200
        Re: Problem updating to Buster - gparted effectively MIA Gene Heskett <gheskett@shentel.net> - 2018-10-07 17:10 +0200
    Re: Problem updating to Buster - gparted effectively MIA Brian <ad44@cityscape.co.uk> - 2018-10-07 16:40 +0200
      Re: Problem updating to Buster - gparted effectively MIA Brian <ad44@cityscape.co.uk> - 2018-10-07 20:30 +0200
        Re: Problem updating to Buster - gparted effectively MIA mick crane <mick.crane@gmail.com> - 2018-10-07 20:50 +0200
          Re: Problem updating to Buster - gparted effectively MIA Linux-Fan <Ma_Sys.ma@web.de> - 2018-10-07 21:20 +0200
            Re: Problem updating to Buster - gparted effectively MIA Joe <joe@jretrading.com> - 2018-10-07 22:00 +0200
            Re: Problem updating to Buster - gparted effectively MIA mick crane <mick.crane@gmail.com> - 2018-10-07 23:10 +0200
        Re: Problem updating to Buster - gparted effectively MIA Dominic Knight <dominicknight@gmx.com> - 2018-10-07 21:40 +0200
          Re: Problem updating to Buster - gparted effectively MIA Richard Owlett <rowlett@cloud85.net> - 2018-10-07 22:00 +0200
            Re: Problem updating to Buster - gparted effectively MIA Brian <ad44@cityscape.co.uk> - 2018-10-08 00:00 +0200

#200962 — Problem updating to Buster - gparted effectively MIA

It was recommended that I update to Buster.
I started with Debian 9.1.0 installed from purchased DVD1.
[MATE desktop]
I edited sources.list to access online repository.
I then followed the instructions at
[linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-buster]
as it had everything conveniently shown.

Everything appeared to go normally up to a point well into the actual 
downloading of the Buster packages. I temporarily lost my internet 
connection. After reconnecting apt-get gave an error message suggesting 
I use "--fix-missing" IIRC.

It appeared to work and boot correctly.

However Gparted no longer appears in the System->Administration menu 
although Synaptic shows it as installed. I blindly chose to tell 
Synaptic to reinstall it.

I installed stretch to another partition which I'm using now.
Is the Buster install repairable?

TIA

[toc] | [next] | [standalone]

#200966

	Hi.

On Sun, Oct 07, 2018 at 08:14:05AM -0500, Richard Owlett wrote:
> It was recommended that I update to Buster.
> I started with Debian 9.1.0 installed from purchased DVD1.
> [MATE desktop]
> I edited sources.list to access online repository.
> I then followed the instructions at
> [linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-buster]
> as it had everything conveniently shown.

That guide misses so crucial details and so barebone that it even feels
wrong.
I mean, there's the obligatory "backup your system first"?
Where's the warning like "do *NOT* upgrade your system from X session
(VNC included)"?
And last, but not least, "if you do it via ssh, using screen(1) or
tmux(1) is a must. Or get yourself iLO/ILOM/BMC".

But it seems that you've figured out last part already, isn't it ;)?


> Everything appeared to go normally up to a point well into the actual downloading of the Buster packages.

That's harmless by itself, unless apt gone further and started
installing the packages.


> I temporarily lost my internet connection. After reconnecting apt-get
> gave an error message suggesting I use "--fix-missing" IIRC.

Which seems to be the above case.


> It appeared to work and boot correctly.

They call Debian "The Universal OS". The part of this universality (sp?)
is Debian's ability to provide you with bootable system even after
numerous deliberate attempts to break it.
Failed upgrade (and it's most likely failed) is one of those cases.

In short, a bootable system proves nothing by itself.


> However Gparted no longer appears in the System->Administration menu although Synaptic shows it as installed. I blindly chose to tell
> Synaptic to reinstall it.

If synaptic worked for you, it's likely that not everything's lost, and
the upgrade process can be completed.


> I installed stretch to another partition which I'm using now.
> Is the Buster install repairable?

Depends. I'd start with chrooting into this "another partition" and
doing like something like this:

dpkg --configure -a
apt update
apt upgrade -s

Just to estimate the damage.

Reco

[toc] | [prev] | [next] | [standalone]

#200968

On 10/07/2018 08:52 AM, Reco wrote:
> 	Hi.
> 
> On Sun, Oct 07, 2018 at 08:14:05AM -0500, Richard Owlett wrote:
>> It was recommended that I update to Buster.
>> I started with Debian 9.1.0 installed from purchased DVD1.
>> [MATE desktop]
>> I edited sources.list to access online repository.
>> I then followed the instructions at
>> [linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-buster]
>> as it had everything conveniently shown.
> 
> That guide misses so crucial details and so barebone that it even feels
> wrong.
> I mean, there's the obligatory "backup your system first"?

*ROFL* I am a graduate of School of Hard Knocks, Slow Learner division.
I have a system on a flash drive backup.
I have TWO copies of my /home partition.

> Where's the warning like "do *NOT* upgrade your system from X session
> (VNC included)"?
> And last, but not least, "if you do it via ssh, using screen(1) or
> tmux(1) is a must. Or get yourself iLO/ILOM/BMC".
> 
> But it seems that you've figured out last part already, isn't it ;)?
> 
> 
>> Everything appeared to go normally up to a point well into the actual downloading of the Buster packages.
> 
> That's harmless by itself, unless apt gone further and started
> installing the packages.
> 
> 
>> I temporarily lost my internet connection. After reconnecting apt-get
>> gave an error message suggesting I use "--fix-missing" IIRC.
> 
> Which seems to be the above case.
> 
> 
>> It appeared to work and boot correctly.
> 
> They call Debian "The Universal OS". The part of this universality (sp?)
> is Debian's ability to provide you with bootable system even after
> numerous deliberate attempts to break it.
> Failed upgrade (and it's most likely failed) is one of those cases.
> 
> In short, a bootable system proves nothing by itself.
> 
> 
>> However Gparted no longer appears in the System->Administration menu although Synaptic shows it as installed. I blindly chose to tell
>> Synaptic to reinstall it.
> 
> If synaptic worked for you, it's likely that not everything's lost, and
> the upgrade process can be completed.
> 
> 
>> I installed stretch to another partition which I'm using now.
>> Is the Buster install repairable?
> 
> Depends. I'd start with chrooting into this "another partition" and
> doing like something like this:

I've never used chroot - I wasn't clear on what happened on current 
system and what went on in the system chrooted to.

Are you saying to boot the "Buster" system and chroot into the known 
good Stretch system?

> 
> dpkg --configure -a
> apt update
> apt upgrade -s
> 
> Just to estimate the damage.
> 
> Reco

Will follow up this afternoon.
Thanks.

[toc] | [prev] | [next] | [standalone]

#200969

	Hi.

On Sun, Oct 07, 2018 at 09:17:10AM -0500, Richard Owlett wrote:
> On 10/07/2018 08:52 AM, Reco wrote:
> > 	Hi.
> > 
> > On Sun, Oct 07, 2018 at 08:14:05AM -0500, Richard Owlett wrote:
> > > It was recommended that I update to Buster.
> > > I started with Debian 9.1.0 installed from purchased DVD1.
> > > [MATE desktop]
> > > I edited sources.list to access online repository.
> > > I then followed the instructions at
> > > [linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-buster]
> > > as it had everything conveniently shown.
> > 
> > That guide misses so crucial details and so barebone that it even feels
> > wrong.
> > I mean, there's the obligatory "backup your system first"?
> 
> *ROFL* I am a graduate of School of Hard Knocks, Slow Learner division.
> I have a system on a flash drive backup.
> I have TWO copies of my /home partition.

<Tips hat>


> > > I installed stretch to another partition which I'm using now.
> > > Is the Buster install repairable?
> > 
> > Depends. I'd start with chrooting into this "another partition" and
> > doing like something like this:
> 
> I've never used chroot - I wasn't clear on what happened on current system and what went on in the system chrooted to.
> 
> Are you saying to boot the "Buster" system and chroot into the known good Stretch system?

No, stay in stretch.

1) Become root.

2) Mount buster installation in, say, /mnt.

3) Classic chroot sequence:

mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
mount -o bind /dev /mnt/dev
chroot /mnt /bin/bash
# You're in chroot now
# Do not leave until instructed

4) Prevent buster services from running:

cat > /usr/sbin/policy-rc.d << EOF
echo All rc operations are disabled by policy: \$1 \$2
exit 101
EOF

chmod 754 /usr/sbin/policy-rc.d

5) Hard part starts here:

dpkg --configure -a
apt update
apt upgrade -s


6) Cleanup:

rm -f /usr/sbin/policy-rc.d
exit
# You left chroot

7) Finally:

umount -l /mnt/proc
umount -l /mnt/sys
umount -l /mnt/dev
umount -l /mnt

Reco

[toc] | [prev] | [next] | [standalone]

#201016

On 10/07/2018 09:26 AM, Reco wrote:
> 	Hi.
> 
> On Sun, Oct 07, 2018 at 09:17:10AM -0500, Richard Owlett wrote:
>> On 10/07/2018 08:52 AM, Reco wrote:
>>> 	Hi.
>>>
>>> On Sun, Oct 07, 2018 at 08:14:05AM -0500, Richard Owlett wrote:
>>>> It was recommended that I update to Buster.
>>>> I started with Debian 9.1.0 installed from purchased DVD1.
>>>> [MATE desktop]
>>>> I edited sources.list to access online repository.
>>>> I then followed the instructions at
>>>> [linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-buster]
>>>> as it had everything conveniently shown.
>>>
>>> That guide misses so crucial details and so barebone that it even feels
>>> wrong.
>>> I mean, there's the obligatory "backup your system first"?
>>
>> *ROFL* I am a graduate of School of Hard Knocks, Slow Learner division.
>> I have a system on a flash drive backup.
>> I have TWO copies of my /home partition.
> 
> <Tips hat>
> 
> 
>>>> I installed stretch to another partition which I'm using now.
>>>> Is the Buster install repairable?
>>>
>>> Depends. I'd start with chrooting into this "another partition" and
>>> doing like something like this:
>>
>> I've never used chroot - I wasn't clear on what happened on current system and what went on in the system chrooted to.
>>
>> Are you saying to boot the "Buster" system and chroot into the known good Stretch system?
> 
> No, stay in stretch.
> 
> 1) Become root.
> 
> 2) Mount buster installation in, say, /mnt.
> 
> 3) Classic chroot sequence:
> 
> mount -o bind /proc /mnt/proc
> mount -o bind /sys /mnt/sys
> mount -o bind /dev /mnt/dev
> chroot /mnt /bin/bash
> # You're in chroot now
> # Do not leave until instructed
> 
> 4) Prevent buster services from running:
> 
> cat > /usr/sbin/policy-rc.d << EOF
> echo All rc operations are disabled by policy: \$1 \$2
> exit 101
> EOF
> 
> chmod 754 /usr/sbin/policy-rc.d
> 
> 5) Hard part starts here:
> 
> dpkg --configure -a
> apt update
> apt upgrade -s
> 
> 
> 6) Cleanup:
> 
> rm -f /usr/sbin/policy-rc.d
> exit
> # You left chroot
> 
> 7) Finally:
> 
> umount -l /mnt/proc
> umount -l /mnt/sys
> umount -l /mnt/dev
> umount -l /mnt
> 
> Reco
> 

It seemed to run OK. The only errors/warnings were related to not being 
able to reach [http://deb.debian.org/...].

It reported:
    "259 packages can be upgraded."
and
    "210 upgraded, 201 newly installed, 0 to remove and 49 not upgraded."

What, if anything, does that say about my upgrade from Stretch to Buster?
I stated by running "script", so I have a log.

Thank you.

[toc] | [prev] | [next] | [standalone]

#201021

	Hi.

On Mon, Oct 08, 2018 at 08:46:21AM -0500, Richard Owlett wrote:
> > No, stay in stretch.
> > 
> > 1) Become root.
> > 
> > 2) Mount buster installation in, say, /mnt.
> > 
> > 3) Classic chroot sequence:
> > 
> > mount -o bind /proc /mnt/proc
> > mount -o bind /sys /mnt/sys
> > mount -o bind /dev /mnt/dev
> > chroot /mnt /bin/bash
> > # You're in chroot now
> > # Do not leave until instructed
> > 
> > 4) Prevent buster services from running:
> > 
> > cat > /usr/sbin/policy-rc.d << EOF
> > echo All rc operations are disabled by policy: \$1 \$2
> > exit 101
> > EOF
> > 
> > chmod 754 /usr/sbin/policy-rc.d
> > 
> > 5) Hard part starts here:
> > 
> > dpkg --configure -a
> > apt update
> > apt upgrade -s
> > 
> > 
> > 6) Cleanup:
> > 
> > rm -f /usr/sbin/policy-rc.d
> > exit
> > # You left chroot
> > 
> > 7) Finally:
> > 
> > umount -l /mnt/proc
> > umount -l /mnt/sys
> > umount -l /mnt/dev
> > umount -l /mnt
> > 
> > Reco
> > 
> 
> It seemed to run OK. The only errors/warnings were related to not being able to reach [http://deb.debian.org/...].
> 
> It reported:
>    "259 packages can be upgraded."
> and
>    "210 upgraded, 201 newly installed, 0 to remove and 49 not upgraded."
> 
> What, if anything, does that say about my upgrade from Stretch to Buster?

It was not completed, but it's fixable.


> I stated by running "script", so I have a log.

1) First things first.

Install 'screen' utility into stretch.
run 'screen' and do everything else there.
In case of any trouble (such as network connectivity loss), reestablish
your connection and run 'screen -DR'.

2) Mount chroot again (from inside the screen). Ensure you're able to
run 'apt-get update' without trouble, as you'll need it.

3) Perform the usual upgrade dance:

apt-get upgrade

apt-get dist-upgrade

The process will ask you questions (many questions, in fact), you're
assumed to choose answers wisely ;). Take special care while upgrading
grub.

4) Unmount chroot, exit screen (simple 'exit' should do it).

5) Reboot into your brand-new buster installation.

Reco

[toc] | [prev] | [next] | [standalone]

#201049

On 10/08/2018 10:45 AM, Reco wrote:
> 	Hi.
> 
> On Mon, Oct 08, 2018 at 08:46:21AM -0500, Richard Owlett wrote:
[snip]
> 
>> I stated by running "script", so I have a log.
> 
> 1) First things first.
> 
> Install 'screen' utility into stretch.
> run 'screen' and do everything else there.

I browsed the man page for "screen".
Why use it rather than the MATE terminal?

The answer will suggest what I should be aware of as I give it a more 
detailed read.
It will be useful for me to do a review of how/why use chroot.
IOW saying "... you're assumed to choose answers wisely" I will have to 
"think first rather than repent at leisure" ;/



> In case of any trouble (such as network connectivity loss), reestablish
> your connection and run 'screen -DR'.
> 
> 2) Mount chroot again (from inside the screen). Ensure you're able to
> run 'apt-get update' without trouble, as you'll need it.
> 
> 3) Perform the usual upgrade dance:
> 
> apt-get upgrade
> 
> apt-get dist-upgrade
> 
> The process will ask you questions (many questions, in fact), you're
> assumed to choose answers wisely ;). Take special care while upgrading
> grub.
> 
> 4) Unmount chroot, exit screen (simple 'exit' should do it).
> 
> 5) Reboot into your brand-new buster installation.
> 
> Reco
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#201054

	Hi.

On Mon, Oct 08, 2018 at 03:19:42PM -0500, Richard Owlett wrote:
> On 10/08/2018 10:45 AM, Reco wrote:
> > 	Hi.
> > 
> > On Mon, Oct 08, 2018 at 08:46:21AM -0500, Richard Owlett wrote:
> [snip]
> > 
> > > I stated by running "script", so I have a log.
> > 
> > 1) First things first.
> > 
> > Install 'screen' utility into stretch.
> > run 'screen' and do everything else there.
> 
> I browsed the man page for "screen".
> Why use it rather than the MATE terminal?

What good will MATE terminal will do for you if you experience yet
another network disconnect?
Screen(1) will survive it. X session won't.

Reco

[toc] | [prev] | [next] | [standalone]

#201088

On 10/08/2018 10:45 AM, Reco wrote:
> 	Hi.
> 
> On Mon, Oct 08, 2018 at 08:46:21AM -0500, Richard Owlett wrote:
>[snip]
>> It seemed to run OK. The only errors/warnings were related to not being able to reach [http://deb.debian.org/...].
>>
>> It reported:
>>     "259 packages can be upgraded."
>> and
>>     "210 upgraded, 201 newly installed, 0 to remove and 49 not upgraded."
>>
>> What, if anything, does that say about my upgrade from Stretch to Buster?
> 
> It was not completed, but it's fixable.
> 
> 
>> I stated by running "script", so I have a log.
> 
> 1) First things first.
> 
> Install 'screen' utility into stretch.
> run 'screen' and do everything else there.
> In case of any trouble (such as network connectivity loss), reestablish
> your connection and run 'screen -DR'.

I use a USB connected T-Mobile WiFi Hotspot [WiFi turned off] to access 
the web through the cell network.
A chroot evidently could not connect to it.

As the partition had had a functional Stretch install.
My original attempt to upgrade to Buster had at least partially worked.
I booted into that partition and did the upgrade.
It upgraded and it is now running without any apparent problems.

If it gives problems I'll just wait for the final release.
One major reason I use Debian rather than another release is desire to 
avoid hassles of a rolling release. YMMV ;/

Thank you for your assistance.

[toc] | [prev] | [next] | [standalone]

#201093

On Tue 09 Oct 2018 at 10:10:50 -0500, Richard Owlett wrote:

> On 10/08/2018 10:45 AM, Reco wrote:
> > 	Hi.
> > 
> > On Mon, Oct 08, 2018 at 08:46:21AM -0500, Richard Owlett wrote:
> > [snip]
> > > It seemed to run OK. The only errors/warnings were related to not being able to reach [http://deb.debian.org/...].
> > > 
> > > It reported:
> > >     "259 packages can be upgraded."
> > > and
> > >     "210 upgraded, 201 newly installed, 0 to remove and 49 not upgraded."
> > > 
> > > What, if anything, does that say about my upgrade from Stretch to Buster?
> > 
> > It was not completed, but it's fixable.
> > 
> > 
> > > I stated by running "script", so I have a log.
> > 
> > 1) First things first.
> > 
> > Install 'screen' utility into stretch.
> > run 'screen' and do everything else there.
> > In case of any trouble (such as network connectivity loss), reestablish
> > your connection and run 'screen -DR'.
> 
> I use a USB connected T-Mobile WiFi Hotspot [WiFi turned off] to access the
> web through the cell network.
> A chroot evidently could not connect to it.
> 
> As the partition had had a functional Stretch install.
> My original attempt to upgrade to Buster had at least partially worked.
> I booted into that partition and did the upgrade.
> It upgraded and it is now running without any apparent problems.

Who would have thought that would have worked?

> If it gives problems I'll just wait for the final release.
> One major reason I use Debian rather than another release is desire to avoid
> hassles of a rolling release. YMMV ;/

You have the menu item for gparted back (the prupose of this thread)?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#200973

On Sunday 07 October 2018 10:17:10 Richard Owlett wrote:

> On 10/07/2018 08:52 AM, Reco wrote:
> > 	Hi.
> >
> > On Sun, Oct 07, 2018 at 08:14:05AM -0500, Richard Owlett wrote:
> >> It was recommended that I update to Buster.
> >> I started with Debian 9.1.0 installed from purchased DVD1.
> >> [MATE desktop]
> >> I edited sources.list to access online repository.
> >> I then followed the instructions at
> >> [linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-buste
> >>r] as it had everything conveniently shown.
> >
> > That guide misses so crucial details and so barebone that it even
> > feels wrong.
> > I mean, there's the obligatory "backup your system first"?
>
> *ROFL* I am a graduate of School of Hard Knocks, Slow Learner
> division. I have a system on a flash drive backup.
> I have TWO copies of my /home partition.

So am I Richard, a School of Hard Knocks (a division of Alderson-Broddus 
University in philippi WV) alumni, but I've never heard of the Slow 
Learner Division. :) Chuckle...

> > Where's the warning like "do *NOT* upgrade your system from X
> > session (VNC included)"?
> > And last, but not least, "if you do it via ssh, using screen(1) or
> > tmux(1) is a must. Or get yourself iLO/ILOM/BMC".
> >
> > But it seems that you've figured out last part already, isn't it ;)?
> >
> >> Everything appeared to go normally up to a point well into the
> >> actual downloading of the Buster packages.
> >
> > That's harmless by itself, unless apt gone further and started
> > installing the packages.
> >
> >> I temporarily lost my internet connection. After reconnecting
> >> apt-get gave an error message suggesting I use "--fix-missing"
> >> IIRC.
> >
> > Which seems to be the above case.
> >
> >> It appeared to work and boot correctly.
> >
> > They call Debian "The Universal OS". The part of this universality
> > (sp?) is Debian's ability to provide you with bootable system even
> > after numerous deliberate attempts to break it.
> > Failed upgrade (and it's most likely failed) is one of those cases.
> >
> > In short, a bootable system proves nothing by itself.
> >
> >> However Gparted no longer appears in the System->Administration
> >> menu although Synaptic shows it as installed. I blindly chose to
> >> tell Synaptic to reinstall it.
> >
> > If synaptic worked for you, it's likely that not everything's lost,
> > and the upgrade process can be completed.
> >
> >> I installed stretch to another partition which I'm using now.
> >> Is the Buster install repairable?
> >
> > Depends. I'd start with chrooting into this "another partition" and
> > doing like something like this:
>
> I've never used chroot - I wasn't clear on what happened on current
> system and what went on in the system chrooted to.
>
> Are you saying to boot the "Buster" system and chroot into the known
> good Stretch system?
>
> > dpkg --configure -a
> > apt update
> > apt upgrade -s
> >
> > Just to estimate the damage.
> >
> > Reco
>
> Will follow up this afternoon.
> Thanks.



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#200970

On Sun 07 Oct 2018 at 08:14:05 -0500, Richard Owlett wrote:

> It was recommended that I update to Buster.
> I started with Debian 9.1.0 installed from purchased DVD1.
> [MATE desktop]
> I edited sources.list to access online repository.
> I then followed the instructions at
> [linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-buster]
> as it had everything conveniently shown.
> 
> Everything appeared to go normally up to a point well into the actual
> downloading of the Buster packages. I temporarily lost my internet
> connection. After reconnecting apt-get gave an error message suggesting I
> use "--fix-missing" IIRC.
> 
> It appeared to work and boot correctly.
> 
> However Gparted no longer appears in the System->Administration menu
> although Synaptic shows it as installed. I blindly chose to tell Synaptic to
> reinstall it.
> 
> I installed stretch to another partition which I'm using now.
> Is the Buster install repairable?

Does gparted run from a terminal?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#200974

On Sun 07 Oct 2018 at 15:33:09 +0100, Brian wrote:

> On Sun 07 Oct 2018 at 08:14:05 -0500, Richard Owlett wrote:
> 
> > It was recommended that I update to Buster.
> > I started with Debian 9.1.0 installed from purchased DVD1.
> > [MATE desktop]
> > I edited sources.list to access online repository.
> > I then followed the instructions at
> > [linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-buster]
> > as it had everything conveniently shown.
> > 
> > Everything appeared to go normally up to a point well into the actual
> > downloading of the Buster packages. I temporarily lost my internet
> > connection. After reconnecting apt-get gave an error message suggesting I
> > use "--fix-missing" IIRC.
> > 
> > It appeared to work and boot correctly.
> > 
> > However Gparted no longer appears in the System->Administration menu
> > although Synaptic shows it as installed. I blindly chose to tell Synaptic to
> > reinstall it.
> > 
> > I installed stretch to another partition which I'm using now.
> > Is the Buster install repairable?
> 
> Does gparted run from a terminal?

It does?

A missing menu entry is hardly a show-stopper.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#200975

On 2018-10-07 19:23, Brian wrote:
> On Sun 07 Oct 2018 at 15:33:09 +0100, Brian wrote:
> 
>> On Sun 07 Oct 2018 at 08:14:05 -0500, Richard Owlett wrote:

>> Does gparted run from a terminal?
> 
> It does?
> 
> A missing menu entry is hardly a show-stopper.

I never made a menu entry, it looks a bit complicated.
The desktop is handy for accessing the software but sometimes it is 
difficult to start a program say over ssh if you don't know the precise 
name.
A list of the real names of what is on the desktop would be handy.
for example I didn't know the file browser thing was called thunar until 
noticing it somewhere.


mick




-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#200976

[Multipart message — attachments visible in raw view] — view raw

mick crane writes:

> On 2018-10-07 19:23, Brian wrote:
>> On Sun 07 Oct 2018 at 15:33:09 +0100, Brian wrote:
>>
>>> On Sun 07 Oct 2018 at 08:14:05 -0500, Richard Owlett wrote:
>
>>> Does gparted run from a terminal?
>>
>> It does?
>>
>> A missing menu entry is hardly a show-stopper.
>
> I never made a menu entry, it looks a bit complicated.
> The desktop is handy for accessing the software but sometimes it is  
> difficult to start a program say over ssh if you don't know the precise name.
> A list of the real names of what is on the desktop would be handy.
> for example I didn't know the file browser thing was called thunar until  
> noticing it somewhere.
>
>
> mick

Hello,

there are multiple ways of finding out the program's "real" names, but here  
are some ideas:

 * Use `xprop` and click on a program's window.
   For instance, if I click on a terminal window, I get (among other
   things) this output from `xprop`:

	$ xprop
	[...]
	_NET_WM_PID(CARDINAL) = 20886
	[...]
	WM_COMMAND(STRING) = { "/usr/bin/urxvt", "+sb", "+bc", [...]
	[...]

   Thus I know the command is `urxvt` and some parameters (one can also
   try and see what happens without the parameters to check if they are
   really needed).

 * Use Help > About menu entries, they at least often have the program's
   name (which need not be equal to the command but often is).
   For the `thunar` command, you get ``Thunar 1.6.11'' under Help > About.

 * Locate the .desktop files of your application (might work for desktop
   icons in some Desktop Environments). They sometimes have an `Exec=` line
   which identifies the command used to start the application.

HTH
Linux-Fan 

[toc] | [prev] | [next] | [standalone]

#200980

On Sun, 07 Oct 2018 21:12:39 +0200
Linux-Fan <Ma_Sys.ma@web.de> wrote:

> mick crane writes:
> 
> > On 2018-10-07 19:23, Brian wrote:  
> >> On Sun 07 Oct 2018 at 15:33:09 +0100, Brian wrote:
> >>  
> >>> On Sun 07 Oct 2018 at 08:14:05 -0500, Richard Owlett wrote:  
> >  
> >>> Does gparted run from a terminal?  
> >>
> >> It does?
> >>
> >> A missing menu entry is hardly a show-stopper.  
> >
> > I never made a menu entry, it looks a bit complicated.
> > The desktop is handy for accessing the software but sometimes it
> > is difficult to start a program say over ssh if you don't know the
> > precise name. A list of the real names of what is on the desktop
> > would be handy. for example I didn't know the file browser thing
> > was called thunar until noticing it somewhere.
> >
> >
> > mick  
> 
> Hello,
> 
> there are multiple ways of finding out the program's "real" names,
> but here are some ideas:
> 
>  * Use `xprop` and click on a program's window.
>    For instance, if I click on a terminal window, I get (among other
>    things) this output from `xprop`:
> 
> 	$ xprop
> 	[...]
> 	_NET_WM_PID(CARDINAL) = 20886
> 	[...]
> 	WM_COMMAND(STRING) = { "/usr/bin/urxvt", "+sb", "+bc", [...]
> 	[...]
> 
>    Thus I know the command is `urxvt` and some parameters (one can
> also try and see what happens without the parameters to check if they
> are really needed).
> 
>  * Use Help > About menu entries, they at least often have the
> program's name (which need not be equal to the command but often is).
>    For the `thunar` command, you get ``Thunar 1.6.11'' under Help >
> About.
> 
>  * Locate the .desktop files of your application (might work for
> desktop icons in some Desktop Environments). They sometimes have an
> `Exec=` line which identifies the command used to start the
> application.
>

Also check if you have 'Main Menu' in the Settings submenu of the main
desktop menu. If you don't, it's provided by the alacarte package,
which has some Gnome dependencies but makes messing about with menus
much easier. I've never thought it reasonable to expect a graphical
desktop user to muck about finding and editing XML dotfiles to make
simple menu changes.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#200981

On 2018-10-07 20:12, Linux-Fan wrote:
> mick crane writes:
> 
>> On 2018-10-07 19:23, Brian wrote:
>>> On Sun 07 Oct 2018 at 15:33:09 +0100, Brian wrote:
>>> 
>>>> On Sun 07 Oct 2018 at 08:14:05 -0500, Richard Owlett wrote:
>> 
>>>> Does gparted run from a terminal?
>>> 
>>> It does?
>>> 
>>> A missing menu entry is hardly a show-stopper.
>> 
>> I never made a menu entry, it looks a bit complicated.
>> The desktop is handy for accessing the software but sometimes it is 
>> difficult to start a program say over ssh if you don't know the 
>> precise name.
>> A list of the real names of what is on the desktop would be handy.
>> for example I didn't know the file browser thing was called thunar 
>> until noticing it somewhere.
>> 
>> 
>> mick
> 
> Hello,
> 
> there are multiple ways of finding out the program's "real" names, but
> here are some ideas:
> 
> * Use `xprop` and click on a program's window.
>   For instance, if I click on a terminal window, I get (among other
>   things) this output from `xprop`:
> 
> 	$ xprop
> 	[...]
> 	_NET_WM_PID(CARDINAL) = 20886
> 	[...]
> 	WM_COMMAND(STRING) = { "/usr/bin/urxvt", "+sb", "+bc", [...]
> 	[...]
> 
>   Thus I know the command is `urxvt` and some parameters (one can also
>   try and see what happens without the parameters to check if they are
>   really needed).
> 
> * Use Help > About menu entries, they at least often have the program's
>   name (which need not be equal to the command but often is).
>   For the `thunar` command, you get ``Thunar 1.6.11'' under Help > 
> About.
> 
> * Locate the .desktop files of your application (might work for desktop
>   icons in some Desktop Environments). They sometimes have an `Exec=` 
> line
>   which identifies the command used to start the application.
> 
> HTH
> Linux-Fan

thank you for these useful tips.
for me I wouldn't mind a text file that was updated when software was 
installed with a desktop item to show its actual run command and perhaps 
a brief description of what its purpose is.


mick

-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#200977

On Sun, 2018-10-07 at 19:23 +0100, Brian wrote:
> On Sun 07 Oct 2018 at 15:33:09 +0100, Brian wrote:
> 
> > On Sun 07 Oct 2018 at 08:14:05 -0500, Richard Owlett wrote:
> > 
> > > It was recommended that I update to Buster.
> > > I started with Debian 9.1.0 installed from purchased DVD1.
> > > [MATE desktop]
> > > I edited sources.list to access online repository.
> > > I then followed the instructions at
> > > [linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-
> > > buster]
> > > as it had everything conveniently shown.
> > > 
> > > Everything appeared to go normally up to a point well into the
> > > actual
> > > downloading of the Buster packages. I temporarily lost my
> > > internet
> > > connection. After reconnecting apt-get gave an error message
> > > suggesting I
> > > use "--fix-missing" IIRC.
> > > 
> > > It appeared to work and boot correctly.
> > > 
> > > However Gparted no longer appears in the System->Administration
> > > menu
> > > although Synaptic shows it as installed. I blindly chose to tell
> > > Synaptic to
> > > reinstall it.
> > > 
> > > I installed stretch to another partition which I'm using now.
> > > Is the Buster install repairable?
> > 
> > Does gparted run from a terminal?
> 
> It does?
> 
> A missing menu entry is hardly a show-stopper.
> 
It moved in Buster (Mate version of GUI) from system->admin to
Applications->system tools.
Try there.

[toc] | [prev] | [next] | [standalone]

#200978

On 10/07/2018 02:33 PM, Dominic Knight wrote:
> On Sun, 2018-10-07 at 19:23 +0100, Brian wrote:
>> On Sun 07 Oct 2018 at 15:33:09 +0100, Brian wrote:
>>
>>> On Sun 07 Oct 2018 at 08:14:05 -0500, Richard Owlett wrote:
>>>
>>>> It was recommended that I update to Buster.
>>>> I started with Debian 9.1.0 installed from purchased DVD1.
>>>> [MATE desktop]
>>>> I edited sources.list to access online repository.
>>>> I then followed the instructions at
>>>> [linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-
>>>> buster]
>>>> as it had everything conveniently shown.
>>>>
>>>> Everything appeared to go normally up to a point well into the
>>>> actual
>>>> downloading of the Buster packages. I temporarily lost my
>>>> internet
>>>> connection. After reconnecting apt-get gave an error message
>>>> suggesting I
>>>> use "--fix-missing" IIRC.
>>>>
>>>> It appeared to work and boot correctly.
>>>>
>>>> However Gparted no longer appears in the System->Administration
>>>> menu
>>>> although Synaptic shows it as installed. I blindly chose to tell
>>>> Synaptic to
>>>> reinstall it.
>>>>
>>>> I installed stretch to another partition which I'm using now.
>>>> Is the Buster install repairable?
>>>
>>> Does gparted run from a terminal?
>>
>> It does?
>>
>> A missing menu entry is hardly a show-stopper.
>>
> It moved in Buster (Mate version of GUI) from system->admin to
> Applications->system tools.
> Try there.
> 

It is there and it launches.
As to "does it run from terminal", I was treating its absence as a 
_symptom_ not a "show stopper". As a graduate of Hard Knock, I thought 
it unwise to attempt forcing it to run without cause.

When I've had some sleep I will follow follow the routine Reco suggested.

[toc] | [prev] | [next] | [standalone]

#200982

On Sun 07 Oct 2018 at 14:57:10 -0500, Richard Owlett wrote:

> On 10/07/2018 02:33 PM, Dominic Knight wrote:
> > On Sun, 2018-10-07 at 19:23 +0100, Brian wrote:
> > > On Sun 07 Oct 2018 at 15:33:09 +0100, Brian wrote:
> > > 
> > > > On Sun 07 Oct 2018 at 08:14:05 -0500, Richard Owlett wrote:
> > > > 
> > > > > It was recommended that I update to Buster.
> > > > > I started with Debian 9.1.0 installed from purchased DVD1.
> > > > > [MATE desktop]
> > > > > I edited sources.list to access online repository.
> > > > > I then followed the instructions at
> > > > > [linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-
> > > > > buster]
> > > > > as it had everything conveniently shown.
> > > > > 
> > > > > Everything appeared to go normally up to a point well into the
> > > > > actual
> > > > > downloading of the Buster packages. I temporarily lost my
> > > > > internet
> > > > > connection. After reconnecting apt-get gave an error message
> > > > > suggesting I
> > > > > use "--fix-missing" IIRC.
> > > > > 
> > > > > It appeared to work and boot correctly.
> > > > > 
> > > > > However Gparted no longer appears in the System->Administration
> > > > > menu
> > > > > although Synaptic shows it as installed. I blindly chose to tell
> > > > > Synaptic to
> > > > > reinstall it.
> > > > > 
> > > > > I installed stretch to another partition which I'm using now.
> > > > > Is the Buster install repairable?
> > > > 
> > > > Does gparted run from a terminal?
> > > 
> > > It does?
> > > 
> > > A missing menu entry is hardly a show-stopper.
> > > 
> > It moved in Buster (Mate version of GUI) from system->admin to
> > Applications->system tools.
> > Try there.
> > 
> 
> It is there and it launches.
> As to "does it run from terminal", I was treating its absence as a _symptom_
> not a "show stopper". As a graduate of Hard Knock, I thought it unwise to
> attempt forcing it to run without cause.

The third sentence is about as obtuse as it gets.
> 
> When I've had some sleep I will follow follow the routine Reco suggested.

A lot of work just to get a menu entry back.

-- 
Brian.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web