package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Barry Warsaw]

dist-upgrade from wily to xenial

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.2-0ubuntu4
Architecture: amd64
Date: Mon Nov 9 09:56:09 2015
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2011-07-12 (1580 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.3ubuntu1
 apt 1.0.10.2ubuntu1
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Gary Eitel (leti2egh)]

This doesn't mean much to me---all I know is that when I clicked the
"upgrade" button when I was notified of the newer 16.04 version that was
available, it didn't finish installing and kept asking me for passwords
before anything would boot as such. I entered my user and root
passwords and kept getting the message saying it was the wrong password.

Have finally bought a new hard drive and taken it to a Tech to hopefully
get running again but likely have lost all my files. Previous years I
had upgraded from version 11, 12, and to 14 with no problems---it needs
to be made more foolproof somehow. Been running Ubuntu for at least 5
yrs and like it--------

Gary

On 08/11/2016 02:30 PM, Alberto Salvia Novella wrote:
> ** Changed in: tex-common (Ubuntu)
> Importance: Undecided => High
>

[Tony Bradshaw (twerpinc)]

Similar problems here with the update on 2 laptops. What I did then was to download an iso, burn a dvd, backed up my files to external HDD and did a fresh install of version 16.04.1 on both laptops. So far everything is running well with no problems. Installed on a third laptop without any problems. That proves to me the update version is seriously flawed and should be avoided. Like you I am a long time user of Ubuntu Studio and have never had these type problems with an update. Hope this helps.T

      From: Gary Eitel <email address hidden>
 To: <email address hidden>
 Sent: Thursday, August 11, 2016 4:35 PM
 Subject: Re: [Bug 1514474] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

This doesn't mean much to me---all I know is that when I clicked the
"upgrade" button when I was notified of the newer 16.04 version that was
available, it didn't finish installing and kept asking me for passwords
before anything would boot as such.  I entered my user and root
passwords and kept getting the message saying it was the wrong password.

Have finally bought a new hard drive and taken it to a Tech to hopefully
get running again but likely have lost all my files. Previous years I
had upgraded from version 11, 12, and to 14 with no problems---it needs
to be made more foolproof somehow.  Been running Ubuntu for at least 5
yrs and like it--------

Gary

On 08/11/2016 02:30 PM, Alberto Salvia Novella wrote:
> ** Changed in: tex-common (Ubuntu)
>    Importance: Undecided => High
>

--
You received this bug notification because you are subscribed to a
duplicate bug report (1608240).
https://bugs.launchpad.net/bugs/1514474

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Confirmed

Bug description:
  dist-upgrade from wily to xenial

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu4
  Architecture: amd64
  Date: Mon Nov  9 09:56:09 2015
  ErrorMessage: subprocess installed post-installation script returned error exit status 1
  InstallationDate: Installed on 2011-07-12 (1580 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  PackageArchitecture: all
  RelatedPackageVersions:
  dpkg 1.18.3ubuntu1
  apt  1.0.10.2ubuntu1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+subscriptions

[Zenigata (zenigata17)]

It seems there is a faulty parameter in the call to fmtutils :

fmtutil: unknown option `--no-error-if-no-engine=luajittex'; try fmtutil --help if you need it.

It should not be that difficult to fix...

[Zenigata (zenigata17)]

Here is a modified postinst script for tex-common that did the job for me.

However I do not know if it is a correct fix or just a work around (I did just remove the incorrect option "--no-error-if-no-engine=luajittex" that may have been intended as usefull in some cases)

[Zenigata (zenigata17)]

For people affectés by this issue, you may try following procédure :
   - download the tex-common package
      $ aptitude download tex-common
   - unpack the deb package
      $ dpkg-deb -R tex-common_6.04_all.deb fixfolder
   - fix the postinst script in fixfolder/DEBIAN by removing the faulty parametrer :--no-error-if-no-engine=luajittex (3 occurrences to remove) or replace it by the fixed script joined in previous post
    - rebuid the package
      $ dpkg-deb -b fixfolder fixed-tex-common.deb
    - remove previous bugged installation and installation fixed
      $ sudo dpkg --force-all -r tex-common && sudo dpkg -i fixed-tex-common.deb

It worked like a charm for me, but the faulty parametrer may have been there for some cases...

[Jon Daries (jdaries)]

@zenigata17 this worked for me, thanks!

[Bob Solimeno (solimeno)]

Worked for me too!!

Thanks very much!

On Monday, August 15, 2016, Jon Daries <email address hidden> wrote:

> @zenigata17 this worked for me, thanks!
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1610554).
> https://bugs.launchpad.net/bugs/1514474
>
> Title:
> package tex-common 6.04 failed to install/upgrade: subprocess
> installed post-installation script returned error exit status 1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/tex-common/+
> bug/1514474/+subscriptions
>

[Larry Kovnat (consult-2)]

Worked for me as well - thanks!

[Nilfred (nilfred)]

In brief, copy & paste this:

cd /tmp
apt download tex-common
dpkg-deb -R tex-common_6.04_all.deb /tmp/fixfolder
sed -i -e 's/--no-error-if-no-engine=luajittex //' /tmp/fixfolder/DEBIAN/postinst
dpkg-deb -b /tmp/fixfolder /tmp/fixed-tex-common.deb
sudo dpkg --force-all -r tex-common

Authenticate, then copy & paste this:

sudo dpkg -i /tmp/fixed-tex-common.deb
sudo apt-get install

Please stop "thanks flood" let this be the last post.

[Larry C Schubert (schubie1)]

I've had problems with this ever since I installed a ssd and installed it. The computer never shuts down properly, and I've never been able to upgrade.

[George Kampouris (georte)]

Mine happened during upgrade from Trusty Tahr

[jonny (greyfaux01)]

Im greatful for the fix, so thank you.

  I'm just curious, I seen you have a new acct at launchpad. Like just today your acct was created, with what looks like the sole purpose to push this patch. I don't mean to be accusatory and I certainly don't know how to read source code, but I've read stories of malicious patches getting pushed thru under the radar, so I'm hoping you can just explain why this acct was created today, same day to push the patch. I'm sure I'm being paranoid so im sorry. Surely theres a perfectly good explanation for all this.

Thanks for your time and info. Thank you so much for helping the Linux community.

Sent via 📡

> On Sep 28, 2019, at 9:39 PM, ashley lakin <email address hidden> wrote:
>
> ** Changed in: tex-common (Ubuntu)
> Status: Confirmed => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1734294).
> https://bugs.launchpad.net/bugs/1514474
>
> Title:
> package tex-common 6.04 failed to install/upgrade: subprocess
> installed post-installation script returned error exit status 1
>
> Status in tex-common package in Ubuntu:
> Fix Released
>
> Bug description:
> dist-upgrade from wily to xenial
>
> ProblemType: Package
> DistroRelease: Ubuntu 16.04
> Package: tex-common 6.04
> ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
> Uname: Linux 4.2.0-16-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.19.2-0ubuntu4
> Architecture: amd64
> Date: Mon Nov 9 09:56:09 2015
> ErrorMessage: subprocess installed post-installation script returned error exit status 1
> InstallationDate: Installed on 2011-07-12 (1580 days ago)
> InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
> PackageArchitecture: all
> RelatedPackageVersions:
> dpkg 1.18.3ubuntu1
> apt 1.0.10.2ubuntu1
> SourcePackage: tex-common
> Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
> UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+subscriptions

[enrico de bernart (enricofromrome)]

Frankly long time passed and the only thing I can suppose that upgrading to
18.04 my account expired, hope this helps.

Pls note also that just couple of days ago I received a mail from Google
about the use of my account 65 days ago on Ubuntu 16 but is long time all
my computers are on 18 (I revoked access from that machine).

Regards
Enrico

Il dom 29 set 2019, 17:54 jonny <email address hidden> ha scritto:

> Im greatful for the fix, so thank you.
>
> I'm just curious, I seen you have a new acct at launchpad. Like just
> today your acct was created, with what looks like the sole purpose to
> push this patch. I don't mean to be accusatory and I certainly don't
> know how to read source code, but I've read stories of malicious patches
> getting pushed thru under the radar, so I'm hoping you can just explain
> why this acct was created today, same day to push the patch. I'm sure
> I'm being paranoid so im sorry. Surely theres a perfectly good
> explanation for all this.
>
> Thanks for your time and info. Thank you so much for helping the Linux
> community.
>
> Sent via 📡
>
> > On Sep 28, 2019, at 9:39 PM, ashley lakin <email address hidden>
> wrote:
> >
> > ** Changed in: tex-common (Ubuntu)
> > Status: Confirmed => Fix Released
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1734294).
> > https://bugs.launchpad.net/bugs/1514474
> >
> > Title:
> > package tex-common 6.04 failed to install/upgrade: subprocess
> > installed post-installation script returned error exit status 1
> >
> > Status in tex-common package in Ubuntu:
> > Fix Released
> >
> > Bug description:
> > dist-upgrade from wily to xenial
> >
> > ProblemType: Package
> > DistroRelease: Ubuntu 16.04
> > Package: tex-common 6.04
> > ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
> > Uname: Linux 4.2.0-16-generic x86_64
> > NonfreeKernelModules: nvidia
> > ApportVersion: 2.19.2-0ubuntu4
> > Architecture: amd64
> > Date: Mon Nov 9 09:56:09 2015
> > ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> > InstallationDate: Installed on 2011-07-12 (1580 days ago)
> > InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64
> (20110705.1)
> > PackageArchitecture: all
> > RelatedPackageVersions:
> > dpkg 1.18.3ubuntu1
> > apt 1.0.10.2ubuntu1
> > SourcePackage: tex-common
> > Title: package tex-common 6.04 failed to install/upgrade: subprocess
> installed post-installation script returned error exit status 1
> > UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)
> >
> > To manage notifications about this bug go to:
> >
> https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+subscriptions
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1629599).
> https://bugs.launchpad.net/bugs/1514474
>
> Title:
> package tex-common 6.04 failed to install/upgrade: subprocess
> installed post-installation script returned error exit status 1
>
> Status in tex-common package in Ubuntu:
> Fix Released
>
> Bug description:
> dist-upgrade from wily to xenial
>
> ProblemType:...

[jonny (greyfaux01)]

Hey thanks so much for your rapid response. Just the response makes me feel better.

Hmm but that is strange about your acct on 16.x being used with Google when you been using 18.x. That is strange. I hope no one injected anything malicious somehow. I don't see how an email from Google would imply that, but heck what if someone cloned an old machine or logged in as you from an Ubuntu 16.x machine.

Idk. Anyway you have a great day thanks again so much for the reply and not getting angry with me. Nothing is safe these days so I hope I can be viewed as being vigilant, opposed to just annoying lol.

See ya later!!

Sent via 📡

> On Sep 29, 2019, at 11:10 AM, enrico de bernart <email address hidden> wrote:
>
> Frankly long time passed and the only thing I can suppose that upgrading to
> 18.04 my account expired, hope this helps.
>
> Pls note also that just couple of days ago I received a mail from Google
> about the use of my account 65 days ago on Ubuntu 16 but is long time all
> my computers are on 18 (I revoked access from that machine).
>
> Regards
> Enrico
>
>
> Il dom 29 set 2019, 17:54 jonny <email address hidden> ha scritto:
>
>> Im greatful for the fix, so thank you.
>>
>> I'm just curious, I seen you have a new acct at launchpad. Like just
>> today your acct was created, with what looks like the sole purpose to
>> push this patch. I don't mean to be accusatory and I certainly don't
>> know how to read source code, but I've read stories of malicious patches
>> getting pushed thru under the radar, so I'm hoping you can just explain
>> why this acct was created today, same day to push the patch. I'm sure
>> I'm being paranoid so im sorry. Surely theres a perfectly good
>> explanation for all this.
>>
>> Thanks for your time and info. Thank you so much for helping the Linux
>> community.
>>
>> Sent via 📡
>>
>>> On Sep 28, 2019, at 9:39 PM, ashley lakin <email address hidden>
>> wrote:
>>>
>>> ** Changed in: tex-common (Ubuntu)
>>> Status: Confirmed => Fix Released
>>>
>>> --
>>> You received this bug notification because you are subscribed to a
>>> duplicate bug report (1734294).
>>> https://bugs.launchpad.net/bugs/1514474
>>>
>>> Title:
>>> package tex-common 6.04 failed to install/upgrade: subprocess
>>> installed post-installation script returned error exit status 1
>>>
>>> Status in tex-common package in Ubuntu:
>>> Fix Released
>>>
>>> Bug description:
>>> dist-upgrade from wily to xenial
>>>
>>> ProblemType: Package
>>> DistroRelease: Ubuntu 16.04
>>> Package: tex-common 6.04
>>> ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>>> Uname: Linux 4.2.0-16-generic x86_64
>>> NonfreeKernelModules: nvidia
>>> ApportVersion: 2.19.2-0ubuntu4
>>> Architecture: amd64
>>> Date: Mon Nov 9 09:56:09 2015
>>> ErrorMessage: subprocess installed post-installation script returned
>> error exit status 1
>>> InstallationDate: Installed on 2011-07-12 (1580 days ago)
>>> InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64
>> (20110705.1)
>>> PackageArchitecture: all
>>> RelatedPackageVersions:
>>> dpkg 1.18.3ubuntu1
>>> apt 1.0.10.2ubuntu1
>>> SourcePackage: tex-common
>>> Title: package tex-common 6...

[enrico de bernart (enricofromrome)]

Sorry still thinking about it... Maybe I restarted an old, very old
computer.

Ciao

Il dom 29 set 2019, 19:05 jonny <email address hidden> ha scritto:

> Hey thanks so much for your rapid response. Just the response makes me
> feel better.
>
> Hmm but that is strange about your acct on 16.x being used with Google
> when you been using 18.x. That is strange. I hope no one injected
> anything malicious somehow. I don't see how an email from Google would
> imply that, but heck what if someone cloned an old machine or logged in
> as you from an Ubuntu 16.x machine.
>
> Idk. Anyway you have a great day thanks again so much for the reply and
> not getting angry with me. Nothing is safe these days so I hope I can be
> viewed as being vigilant, opposed to just annoying lol.
>
> See ya later!!
>
> Sent via 📡
>
> > On Sep 29, 2019, at 11:10 AM, enrico de bernart <
> <email address hidden>> wrote:
> >
> > Frankly long time passed and the only thing I can suppose that upgrading
> to
> > 18.04 my account expired, hope this helps.
> >
> > Pls note also that just couple of days ago I received a mail from Google
> > about the use of my account 65 days ago on Ubuntu 16 but is long time all
> > my computers are on 18 (I revoked access from that machine).
> >
> > Regards
> > Enrico
> >
> >
> > Il dom 29 set 2019, 17:54 jonny <email address hidden> ha scritto:
> >
> >> Im greatful for the fix, so thank you.
> >>
> >> I'm just curious, I seen you have a new acct at launchpad. Like just
> >> today your acct was created, with what looks like the sole purpose to
> >> push this patch. I don't mean to be accusatory and I certainly don't
> >> know how to read source code, but I've read stories of malicious patches
> >> getting pushed thru under the radar, so I'm hoping you can just explain
> >> why this acct was created today, same day to push the patch. I'm sure
> >> I'm being paranoid so im sorry. Surely theres a perfectly good
> >> explanation for all this.
> >>
> >> Thanks for your time and info. Thank you so much for helping the Linux
> >> community.
> >>
> >> Sent via 📡
> >>
> >>> On Sep 28, 2019, at 9:39 PM, ashley lakin <email address hidden>
> >> wrote:
> >>>
> >>> ** Changed in: tex-common (Ubuntu)
> >>> Status: Confirmed => Fix Released
> >>>
> >>> --
> >>> You received this bug notification because you are subscribed to a
> >>> duplicate bug report (1734294).
> >>> https://bugs.launchpad.net/bugs/1514474
> >>>
> >>> Title:
> >>> package tex-common 6.04 failed to install/upgrade: subprocess
> >>> installed post-installation script returned error exit status 1
> >>>
> >>> Status in tex-common package in Ubuntu:
> >>> Fix Released
> >>>
> >>> Bug description:
> >>> dist-upgrade from wily to xenial
> >>>
> >>> ProblemType: Package
> >>> DistroRelease: Ubuntu 16.04
> >>> Package: tex-common 6.04
> >>> ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
> >>> Uname: Linux 4.2.0-16-generic x86_64
> >>> NonfreeKernelModules: nvidia
> >>> ApportVersion: 2.19.2-0ubuntu4
> >>> Architecture: amd64
> >>> Date: Mon Nov 9 09:56:09 2015
> >>> ErrorMessage: subprocess installed post-installation script returned
> >> error exit status 1
> >>> InstallationD...

[maria grantham (mgrantham)]

I don't know who you are or what this series of messages is.

On Mon, Sep 30, 2019, 1:35 AM enrico de bernart <email address hidden>
wrote:

> Sorry still thinking about it... Maybe I restarted an old, very old
> computer.
>
> Ciao
>
> Il dom 29 set 2019, 19:05 jonny <email address hidden> ha scritto:
>
> > Hey thanks so much for your rapid response. Just the response makes me
> > feel better.
> >
> > Hmm but that is strange about your acct on 16.x being used with Google
> > when you been using 18.x. That is strange. I hope no one injected
> > anything malicious somehow. I don't see how an email from Google would
> > imply that, but heck what if someone cloned an old machine or logged in
> > as you from an Ubuntu 16.x machine.
> >
> > Idk. Anyway you have a great day thanks again so much for the reply and
> > not getting angry with me. Nothing is safe these days so I hope I can be
> > viewed as being vigilant, opposed to just annoying lol.
> >
> > See ya later!!
> >
> > Sent via 📡
> >
> > > On Sep 29, 2019, at 11:10 AM, enrico de bernart <
> > <email address hidden>> wrote:
> > >
> > > Frankly long time passed and the only thing I can suppose that
> upgrading
> > to
> > > 18.04 my account expired, hope this helps.
> > >
> > > Pls note also that just couple of days ago I received a mail from
> Google
> > > about the use of my account 65 days ago on Ubuntu 16 but is long time
> all
> > > my computers are on 18 (I revoked access from that machine).
> > >
> > > Regards
> > > Enrico
> > >
> > >
> > > Il dom 29 set 2019, 17:54 jonny <email address hidden> ha scritto:
> > >
> > >> Im greatful for the fix, so thank you.
> > >>
> > >> I'm just curious, I seen you have a new acct at launchpad. Like just
> > >> today your acct was created, with what looks like the sole purpose to
> > >> push this patch. I don't mean to be accusatory and I certainly don't
> > >> know how to read source code, but I've read stories of malicious
> patches
> > >> getting pushed thru under the radar, so I'm hoping you can just
> explain
> > >> why this acct was created today, same day to push the patch. I'm sure
> > >> I'm being paranoid so im sorry. Surely theres a perfectly good
> > >> explanation for all this.
> > >>
> > >> Thanks for your time and info. Thank you so much for helping the Linux
> > >> community.
> > >>
> > >> Sent via 📡
> > >>
> > >>> On Sep 28, 2019, at 9:39 PM, ashley lakin <
> <email address hidden>>
> > >> wrote:
> > >>>
> > >>> ** Changed in: tex-common (Ubuntu)
> > >>> Status: Confirmed => Fix Released
> > >>>
> > >>> --
> > >>> You received this bug notification because you are subscribed to a
> > >>> duplicate bug report (1734294).
> > >>> https://bugs.launchpad.net/bugs/1514474
> > >>>
> > >>> Title:
> > >>> package tex-common 6.04 failed to install/upgrade: subprocess
> > >>> installed post-installation script returned error exit status 1
> > >>>
> > >>> Status in tex-common package in Ubuntu:
> > >>> Fix Released
> > >>>
> > >>> Bug description:
> > >>> dist-upgrade from wily to xenial
> > >>>
> > >>> ProblemType: Package
> > >>> DistroRelease: Ubuntu 16.04
> > >>> Package: tex-common 6.04
> > >>> ProcVersionSignature: Ubuntu 4.2....

[Renato Rodriguez (renato-rodriguez)]

IT looks like sometime someone reported a bbig in linux and somebody
started a reply to all the subscription group

I don't know neither none of these people

El mar., 1 de octubre de 2019 15:46, maria grantham <
<email address hidden>> escribió:

> I don't know who you are or what this series of messages is.
>
> On Mon, Sep 30, 2019, 1:35 AM enrico de bernart <email address hidden>
> wrote:
>
> > Sorry still thinking about it... Maybe I restarted an old, very old
> > computer.
> >
> > Ciao
> >
> > Il dom 29 set 2019, 19:05 jonny <email address hidden> ha scritto:
> >
> > > Hey thanks so much for your rapid response. Just the response makes me
> > > feel better.
> > >
> > > Hmm but that is strange about your acct on 16.x being used with Google
> > > when you been using 18.x. That is strange. I hope no one injected
> > > anything malicious somehow. I don't see how an email from Google would
> > > imply that, but heck what if someone cloned an old machine or logged in
> > > as you from an Ubuntu 16.x machine.
> > >
> > > Idk. Anyway you have a great day thanks again so much for the reply and
> > > not getting angry with me. Nothing is safe these days so I hope I can
> be
> > > viewed as being vigilant, opposed to just annoying lol.
> > >
> > > See ya later!!
> > >
> > > Sent via 📡
> > >
> > > > On Sep 29, 2019, at 11:10 AM, enrico de bernart <
> > > <email address hidden>> wrote:
> > > >
> > > > Frankly long time passed and the only thing I can suppose that
> > upgrading
> > > to
> > > > 18.04 my account expired, hope this helps.
> > > >
> > > > Pls note also that just couple of days ago I received a mail from
> > Google
> > > > about the use of my account 65 days ago on Ubuntu 16 but is long time
> > all
> > > > my computers are on 18 (I revoked access from that machine).
> > > >
> > > > Regards
> > > > Enrico
> > > >
> > > >
> > > > Il dom 29 set 2019, 17:54 jonny <email address hidden> ha scritto:
> > > >
> > > >> Im greatful for the fix, so thank you.
> > > >>
> > > >> I'm just curious, I seen you have a new acct at launchpad. Like
> just
> > > >> today your acct was created, with what looks like the sole purpose
> to
> > > >> push this patch. I don't mean to be accusatory and I certainly don't
> > > >> know how to read source code, but I've read stories of malicious
> > patches
> > > >> getting pushed thru under the radar, so I'm hoping you can just
> > explain
> > > >> why this acct was created today, same day to push the patch. I'm
> sure
> > > >> I'm being paranoid so im sorry. Surely theres a perfectly good
> > > >> explanation for all this.
> > > >>
> > > >> Thanks for your time and info. Thank you so much for helping the
> Linux
> > > >> community.
> > > >>
> > > >> Sent via 📡
> > > >>
> > > >>> On Sep 28, 2019, at 9:39 PM, ashley lakin <
> > <email address hidden>>
> > > >> wrote:
> > > >>>
> > > >>> ** Changed in: tex-common (Ubuntu)
> > > >>> Status: Confirmed => Fix Released
> > > >>>
> > > >>> --
> > > >>> You received this bug notification because you are subscribed to a
> > > >>> duplicate bug report (1734294).
> > > >>> https://bugs.launchpad.net/bugs/1514474
> > > >>>
> > > >>> Title:
> > > >>> package te...

[ian (7-i7n-8)]

Strangers to me too.
Snowy

On 1 October 2019 21:54:21 BST, Renato Rodriguez <[e-mail]> wrote:
>IT looks like sometime someone reported a bbig in linux and somebody
>started a reply to all the subscription group
>
>I don't know neither none of these people
>
>El mar., 1 de octubre de 2019 15:46, maria grantham <
><email address hidden>> escribió:
>
>> I don't know who you are or what this series of messages is.
>>
>> On Mon, Sep 30, 2019, 1:35 AM enrico de bernart
><email address hidden>
>> wrote:
>>
>> > Sorry still thinking about it... Maybe I restarted an old, very old
>> > computer.
>> >
>> > Ciao
>> >
>> > Il dom 29 set 2019, 19:05 jonny <email address hidden> ha scritto:
>> >
>> > > Hey thanks so much for your rapid response. Just the response
>makes me
>> > > feel better.
>> > >
>> > > Hmm but that is strange about your acct on 16.x being used with
>Google
>> > > when you been using 18.x. That is strange. I hope no one injected
>> > > anything malicious somehow. I don't see how an email from Google
>would
>> > > imply that, but heck what if someone cloned an old machine or
>logged in
>> > > as you from an Ubuntu 16.x machine.
>> > >
>> > > Idk. Anyway you have a great day thanks again so much for the
>reply and
>> > > not getting angry with me. Nothing is safe these days so I hope I
>can
>> be
>> > > viewed as being vigilant, opposed to just annoying lol.
>> > >
>> > > See ya later!!
>> > >
>> > > Sent via 📡
>> > >
>> > > > On Sep 29, 2019, at 11:10 AM, enrico de bernart <
>> > > <email address hidden>> wrote:
>> > > >
>> > > > Frankly long time passed and the only thing I can suppose that
>> > upgrading
>> > > to
>> > > > 18.04 my account expired, hope this helps.
>> > > >
>> > > > Pls note also that just couple of days ago I received a mail
>from
>> > Google
>> > > > about the use of my account 65 days ago on Ubuntu 16 but is
>long time
>> > all
>> > > > my computers are on 18 (I revoked access from that machine).
>> > > >
>> > > > Regards
>> > > > Enrico
>> > > >
>> > > >
>> > > > Il dom 29 set 2019, 17:54 jonny <email address hidden> ha
>scritto:
>> > > >
>> > > >> Im greatful for the fix, so thank you.
>> > > >>
>> > > >> I'm just curious, I seen you have a new acct at launchpad.
>Like
>> just
>> > > >> today your acct was created, with what looks like the sole
>purpose
>> to
>> > > >> push this patch. I don't mean to be accusatory and I certainly
>don't
>> > > >> know how to read source code, but I've read stories of
>malicious
>> > patches
>> > > >> getting pushed thru under the radar, so I'm hoping you can
>just
>> > explain
>> > > >> why this acct was created today, same day to push the patch.
>I'm
>> sure
>> > > >> I'm being paranoid so im sorry. Surely theres a perfectly good
>> > > >> explanation for all this.
>> > > >>
>> > > >> Thanks for your time and info. Thank you so much for helping
>the
>> Linux
>> > > >> community.
>> > > >>
>> > > >> Sent via 📡
>> > > >>
>> > > >>> On Sep 28, 2019, at 9:39 PM, ashley lakin <
>> > <email address hidden>>
>> > > >> wrote:
>> > > >>>
>> > > >>> ** Changed in: tex-common (Ubuntu)
>> > > >>> Status: Confirmed => Fix Released
>> > > >>>
>> > > >>>...

[Domren2 (domren2)]

Hi,

The answer :

"You received this bug notification because you are subscribed to a
duplicate bug report (1703980).
https://bugs.launchpad.net/bugs/1514474"

Unsubscribe ?

Good day ...

Le 02/10/2019 à 11:40, ian a écrit :
> Strangers to me too.
> Snow
--
Dominique Renaudin
http://domren.free.fr