[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind

2020-06-09 Thread David Hansen
This is still a valid issue, I just performed a do-release-upgrade on a v14.04 system yesterday and the same rpcbind issue reared it's ugly little head. Reading the posts here should conclude that it is an understood issue for Xenial. My post here was two years ago. This ticket was created four

[Bug 1746865] Re: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

2018-07-13 Thread David Hansen
My apologies, I did not see this report when I created a duplicate issue (https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1781002 Bug #1781002 ). I encountered this bug three days ago when I performed a fresh 16.04 install and then immediately upgraded to 18.04 via "do-release-upgrade

[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind

2018-07-12 Thread David Hansen
date Thu Jul 12 12:57:35 EDT 2018 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial apt-cache policy rpcbind rpcbind: Installed: 0.2.3-0.2 Candidate: 0.2.3-0.2 This bug was opened on

[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind

2018-07-12 Thread David Hansen
** Changed in: rpcbind (Ubuntu Xenial) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: ypbind not able to socket activate rpcbind under systemd,

[Bug 1757072] Re: new session brings: "The panel encountered a problem while loading "BriskMenuFactory::BriskMenu".

2018-07-10 Thread David Hansen
Performed a fresh v16.04 install today. Then upgraded to v18.04 via do- release-upgrade. Immediately upon logging in with a desktop accont I encountered this problem as well. This is with a new (As in "not previously used", absolutely no configurations to inherit.) account so not making any layout

[Bug 1781002] Re: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

2018-07-10 Thread David Hansen
So generating the en_DK.UTF-8 locale seems to be what was needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781002 Title: package tex-common 6.09 failed to install/upgrade: installed tex-

[Bug 1781002] Re: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

2018-07-10 Thread David Hansen
Choices: 1: Launch a browser now C: Cancel Please choose (1/C): c Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Setting up tex-common (6.09) ... locale: Cannot set LC_ALL to default locale:

[Bug 1781002] [NEW] package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

2018-07-10 Thread David Hansen
Public bug reported: The error occurred during a "do-release-upgrade -d" on a fresh v16.04 installation to bring it up to v18.04. Errors were encountered while processing: tex-common Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package