from:"Francisco"

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543563/+files/acpidump.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543562/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1945542/+attachment/5543561/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543560/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543559/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543558/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543556/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543557/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543555/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543554/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543553/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1945542/+attachment/5543552/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543551/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1945542/+attachment/5543550/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1945542/+attachment/5543547/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543549/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] Re: mouse starts going up and has a laggy response

apport information

** Tags added: apport-collected

** Description changed:

  Writing lsb_release -rd I got this:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  
  I don't know exactly what package has the issue but I think is most probably 
the kernel itself. 
  I can use my touchpad normally most of the time. But randomly and suddenly, 
it stops working properly. When I don't move the cursor, it starts going up and 
for re-using it I have to pass my finger three times (aprox.) and then it 
starts to respond. But when I leave it, the bug comes again.
  The problem got solved when I restart my laptop. I've tried a lot of 
troubleshooting I've found on internet but nothing works without restarting. 
Also, when I write xinput -list in the terminal, it does not detect my touchpad.
  Moreover, today I got two like-windows blue screen but instead of having a 
blue screen I got something like a TV receiving noise in color. Nothing works 
-neither the power button- I've lost few of my college work (not anything 
serious by luck).
  Thank you for making Ubuntu and best Regards.
  Josue Laszeski, Argentina.
  
  PD: I'm not an English native speaker, please ignore my redaction
  faults.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Wed Sep 29 21:46:41 2021
  InstallationDate: Installed on 2021-07-26 (65 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  josue  1259 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-07-26 (122 days ago)
+ InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
+ MachineType: COMPAQ Presario 21
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=UUID=49c60cf2-3935-4fd9-87cc-3db4eed0d496 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
+ RelatedPackageVersions:
+  linux-restricted-modules-5.11.0-40-generic N/A
+  linux-backports-modules-5.11.0-40-generic  N/A
+  linux-firmware 1.187.20
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  focal
+ Uname: Linux 5.11.0-40-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/05/2012
+ dmi.bios.release: 0.1
+ dmi.bios.vendor: Phoenix Technologies Ltd.
+ dmi.bios.version: 77B
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: Presario 21
+ dmi.board.vendor: COMPAQ
+ dmi.board.version: FAB1
+ dmi.chassis.asset.tag: Asset Tag
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Intel Corporation
+ dmi.chassis.version: 0.1
+ dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr77B:bd07/05/2012:br0.1:svnCOMPAQ:pnPresario21:pvr0.1:skuSystemSKUNumber:rvnCOMPAQ:rnPresario21:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:
+ dmi.product.family: EasyTab
+ dmi.product.name: Presario 21
+ dmi.product.sku: System SKUNumber
+ dmi.product.version: 0.1
+ dmi.sys.vendor: COMPAQ

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543546/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945542] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1945542/+attachment/5543548/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945542

Title:
  mouse starts going up and has a laggy response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

2021-11-06 Thread Francisco Pombal

> I believe we can close this bug.

The change to the wiki is welcome, since it now reflects the current
situation.

However, in my opinion, the real problem uncovered here has not been
addressed:

Ubuntu should provide mainline kernels built with the latest LTS
toolchain alongside the current one that uses bleeding edge toolchains,
so that using/testing more recent kernels becomes more accessible to a
wider audience (i.e., the vast majority who does not compile their
kernels from source).

Historically, Ubuntu has had a major barrier to adoption: new users who
buy their hardware in between LTS cycles will usually have a very sub-
par experience with Ubuntu because of the outdated kernel. Their choice
is to either:

- use the latest intermediate release, which may still not provide a recent 
enough kernel and is a bad choice for a first time user anyway
- use the latest LTS which may not be usable at all on their systems with the 
very outdated kernel (this tends to happen a lot with laptops in particular).

With all due respect to the user who put up 
https://launchpad.net/~tuxinvader/+archive/ubuntu/kernel-build-tools and their 
efforts in doing so, there should be an official PPA/infrastructure in place 
for this. We all know users installing lots of PPAs without thinking is a huge 
risk and a practice that is advised against.
But then you can't just leave the user with only one remaining, untenable 
choice, which is for their system to be unusable, in the name of security 
concerns that they don't quite understand.
This is a common criticism of Ubuntu: it effectively _forces_ users into 
installing a whole bunch of random PPAs willy-nilly to get certain basic 
features.

Until something is done about this, "LTS" releases are actually unusable
(or usable with many jarring bugs) for many users. The HWE releases are
better than nothing, but not nearly enough.

A post above put it very nicely:

> If you are telling people that you are going to support it for 5
years, then that means being able to provide security updates to them as
well as allowing them to use hardware that was created during the 5
years following April 2020 within reason. To do that, people must be
able to update the kernel plain and simple.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890815] Re: vainfo requires a nvidia sofile not in repositories

2021-11-05 Thread Francisco Canela

Installing the package from 18.04
(https://launchpad.net/ubuntu/cosmic/amd64/vdpau-va-
driver/0.7.4-6ubuntu1) worked for me. Just download the .deb and install
it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890815

Title:
  vainfo requires a nvidia sofile not in repositories

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libva-utils/+bug/1890815/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945857] [NEW] Touchpad not working

2021-10-02 Thread Francisco Ruiz Martínez

Public bug reported:

The touchpad is not working in a fresh Ubuntu 21.04.
The laptop is a Lenovo ideapad 5.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-37-generic 5.11.0-37.41
ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  franrzm   12466 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct  2 13:16:02 2021
InstallationDate: Installed on 2021-10-02 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 81YK
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=bdb4910a-0994-4f31-b44c-494dfdfc9a95 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-37-generic N/A
 linux-backports-modules-5.11.0-37-generic  N/A
 linux-firmware 1.197.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2020
dmi.bios.release: 1.45
dmi.bios.vendor: LENOVO
dmi.bios.version: DPCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 15IIL05
dmi.ec.firmware.release: 1.45
dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN45WW:bd07/06/2020:br1.45:efr1.45:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:skuLENOVO_MT_81YK_BU_idea_FM_IdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
dmi.product.family: IdeaPad 5 15IIL05
dmi.product.name: 81YK
dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
dmi.product.version: IdeaPad 5 15IIL05
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug hirsute wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945857

Title:
  Touchpad not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945857/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940631] Re: Keep thunderbird 91 in impish-proposed until a point release enables profile upgrades

2021-09-29 Thread Francisco Pombal

Thumbs up to go ahead with 91 on impish.

Indeed, it does not seem like a great idea to:

- release impish with a series of thunderbird that is EOL (as @osomon stated)
- go into the 22.04 cycle without having proven tb >= 91 in at least one 
previous release

Furthermore, as of this writing, the disclaimer concerning profile
upgrades is no longer present in the release notes for 91.1.2, as
opposed to previous 91.x releases.

I would bet that upstream is confident that everything is in order, but
it is also possible that they simply forgot to add the disclaimer thus
far - here is an archive link as proof anyway:
https://web.archive.org/web/20210929002603/https://www.thunderbird.net/en-
US/thunderbird/91.1.2/releasenotes/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940631

Title:
  Keep thunderbird 91 in impish-proposed until a point release enables
  profile upgrades

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1940631/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927808] Re: rtw88_8821ce causes freeze

2021-08-31 Thread Francisco Z

I have the same problem in my hp g4 250 laptop, adding: options
rtw88_pci disable_aspm=1 to that file /etc/modprobe.d/rtw88_pci.conf
fixed the freezes, but it happends in every linux distro using kernel
5.11+

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927808

Title:
  rtw88_8821ce causes freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881941] Re: Ubuntu dock behaves crazy when hidden at the bottom of the screen

2021-06-17 Thread Francisco Marzoa

@Michael Erdely

Just realized that it happens to me too when using Android Studio, which
is kinda a fork of IntelliJ Idea, so maybe it's something related to
IntelliJ interface or Java or something alike...

I wonder if the rest of the users here have experienced it with the same
products.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881941

Title:
  Ubuntu dock behaves crazy when hidden at the bottom of the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1881941/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932305] [NEW] fstrim doesn't trim my /home separate partition

2021-06-17 Thread Francisco T.

Public bug reported:

My system is Kubuntu 20.04

I have 3 partitions in my nvme:
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
nvme0n1 259:00 465,8G  0 disk 
├─nvme0n1p1 259:10   251M  0 part /boot/efi
├─nvme0n1p2 259:20  53,7G  0 part /
├─nvme0n1p4 259:30   7,6G  0 part [SWAP]
└─nvme0n1p5 259:40   357G  0 part /home


I have activated fstrim.service and fstrim.timer:
sudo systemctl list-timers
...
Mon 2021-06-21 00:00:00 CEST 3 days left   Mon 2021-06-14 00:00:03 CEST 3 days 
ago   fstrim.timer fstrim.service  


But home partition is not trimmed:
...
jun 14 00:00:10 moon fstrim[5137]: /: 29,1 GiB (31264600064 bytes) trimmed on 
/dev/nvme0n1p2
jun 14 00:00:10 moon fstrim[5137]: /boot/efi: 239,1 MiB (250755584 bytes) 
trimmed on /dev/nvme0n1p1
jun 14 00:00:10 moon systemd[1]: fstrim.service: Succeeded.
...


The fstrim.service is Protected for home:
sudo systemctl cat fstrim.service 
# /lib/systemd/system/fstrim.service
[Unit]
Description=Discard unused blocks on filesystems from /etc/fstab
Documentation=man:fstrim(8)
ConditionVirtualization=!container

[Service]
Type=oneshot
ExecStart=/sbin/fstrim --fstab --verbose --quiet
ProtectSystem=strict
ProtectHome=yes
PrivateDevices=no
PrivateNetwork=yes
PrivateUsers=no
ProtectKernelTunables=yes
ProtectKernelModules=yes
ProtectControlGroups=yes
MemoryDenyWriteExecute=yes
SystemCallFilter=@default @file-system @basic-io @system-service


I think the problem is:
https://github.com/karelzak/util-linux/commit/61b384b36105fe682ddf16b9379f446d935603bc

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932305

Title:
  fstrim doesn't trim my /home separate partition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1932305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

2021-05-30 Thread Francisco Menchaca

Hi Chhristian.

I am going to try to install the ppa on a different Ubuntu 18.04 server
and will let you know my findings.

The only difference from the preduction servers and my test server is
the following:

Production servers were upgraded from Ubuntu 16.04 to Ubuntu 18.04 and
the production servers are sitting behind a proxy server.

Cheers.

Francisco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

2021-05-26 Thread Francisco Pombal

@racb OK, done: https://discourse.ubuntu.com/t/thunderbird-email-client-
update-policy/22470

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895643

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

2021-05-25 Thread Francisco Pombal

Thanks for seeing this through, but let me raise some important points.

Why is Thunderbird not covered by the same update policy as Firefox?
Sure it's not a web browser, but it's one of the most important and
widely used GUI email clients. Also, it is a close cousin of Firefox.

These updates took way too long to come out for LTS releases, and they
are/were already obsolete once they did roll out. For example, the
78.9.x and 78.10.x releases are more than a month old at this point, and
both contain fixes for "high" severity vulnerabilities:

https://www.mozilla.org/en-US/security/advisories/mfsa2021-12/
https://www.mozilla.org/en-US/security/advisories/mfsa2021-14/

I think Ubuntu should make a greater effort to keep up with Thunderbird
upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895643

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

2021-05-10 Thread Francisco Menchaca

Hi Christian,

Thanks for your response.

Do you mean disabling and enabling autostart to the old guests?

In our dev lab worked straight away after installing the first PPA you
bundled together, I didn't have to disable and enable  autostart.

Kind Regards,
FRANCISCO MENCHACASALES ENGINEER | https://about.me/francisco.menchaca
fxm...@gmail.com | +61 406 204 483
<http://linkedin.com/in/franciscomenchaca>
<http://facebook.com/pacomenchaca>  <http://twitter.com/paquito_>


On Mon, 10 May 2021 at 22:31, Christian Ehrhardt  <
1921...@bugs.launchpad.net> wrote:

> Hi Francisco,
> I have re-checked but I don't see any other related code for your issue.
> The PPA contains the one fix we know about.
>
> I could think of old guests (that existed and were configured autostart
> before the upgrade) to maybe stay in their odd state. But disabling and
> enabling autostart for them should make it work.
> Is at least that working for you?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1921325
>
> Title:
>   VM will not auto-start automatically when server is rebooted after
>   virsh domrename
>
> Status in libvirt package in Ubuntu:
>   Fix Released
> Status in libvirt source package in Bionic:
>   Triaged
> Status in libvirt source package in Focal:
>   Fix Released
>
> Bug description:
>
>   OS: Ubuntu 18.04.5
>   uname -r
>   4.15.0-118-generic
>
>
>   /usr/bin/qemu-system-x86_64 --version
>   QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.32)
>
>
>   $ virsh version
>   Compiled against library: libvirt 4.0.0
>   Using library: libvirt 4.0.0
>   Using API: QEMU 4.0.0
>   Running hypervisor: QEMU 2.11.1
>
>   VM running on KVM on different servers won't start automatically when
>   the server is rebooted after changing the VM domain name.
>
>   Issue Replication:
>
>   1. Set the VM to autostart
>   2. Reboot the server
>   3. VM will start automatically
>   4. Changed the VM domain name virsh domrename VM.old VM.new
>   5. Set the VM.new domain to autostart
>   6. Reboot the server
>   7. VM.new won't start automatically.
>
>   Can you please assist?
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

2021-05-06 Thread Francisco Menchaca

fig -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-EQX-ESM-vPRE-02/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew 
-global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global 
PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device 
pxb,bus_nr=180,id=pci.1,numa_node=0,bus=pci.0,addr=0xe -device 
pxb,bus_nr=200,id=pci.2,numa_node=1,bus=pci.0,addr=0xf -device 
ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x4.0x7 -device 
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x4 
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x4.0x1 
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x4.0x2 
-drive 
file=/data/VM/vpre02/vpre02-disk1.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:4a:b3:06,bus=pci.0,addr=0x2 
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-device vfio-pci,host=19:02.0,id=hostdev0,bus=pci.1,addr=0x1 -device 
vfio-pci,host=19:0a.0,id=hostdev1,bus=pci.1,addr=0x2 -device 
vfio-pci,host=3b:02.0,id=hostdev2,bus=pci.1,addr=0x3 -device 
vfio-pci,host=3b:0a.0,id=hostdev3,bus=pci.1,addr=0x4 -device 
vfio-pci,host=5e:02.0,id=hostdev4,bus=pci.1,addr=0x5 -device 
vfio-pci,host=5e:0a.0,id=hostdev5,bus=pci.1,addr=0x6 -device 
vfio-pci,host=60:02.0,id=hostdev6,bus=pci.1,addr=0x7 -device 
vfio-pci,host=60:0a.0,id=hostdev7,bus=pci.1,addr=0x8 -device 
vfio-pci,host=86:02.0,id=hostdev8,bus=pci.2,addr=0x1 -device 
vfio-pci,host=86:0a.0,id=hostdev9,bus=pci.2,addr=0x2 -device 
vfio-pci,host=88:02.0,id=hostdev10,bus=pci.2,addr=0x3 -device 
vfio-pci,host=88:0a.0,id=hostdev11,bus=pci.2,addr=0x4 -device 
vfio-pci,host=d8:02.0,id=hostdev12,bus=pci.2,addr=0x5 -device 
vfio-pci,host=d8:0a.0,id=hostdev13,bus=pci.2,addr=0x6 -object 
rng-random,id=objrng0,filename=/dev/urandom -device 
virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x6 -msg timestamp=on
2021-05-06 15:23:04.416+: Domain id=2 is tainted: host-cpu
2021-05-06T15:23:04.490801Z qemu-system-x86_64: -chardev pty,id=charserial0: 
char device redirected to /dev/pts/1 (label charserial0)
2021-05-06T15:23:55.192216Z qemu-system-x86_64: warning: Unknown firmware file 
in legacy mode: etc/msr_feature_control

I can see our dev server where the patch worked, and the two other
production servers have the same libvirt/ qemu/ppa releases:

libvirt version: 4.0.0, package: 1ubuntu8.20~bionicppa1 (Christian
Ehrhardt  Fri, 26 Mar 2021 10:21:27
+0100), qemu version: 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.36)

Are you able to assist?

Thanks

Francisco M.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

2021-04-20 Thread Francisco Menchaca

Hi Christian,

An update I tried reinstalling the ppa again and received the following
error:

Can you please advise what I'm doing wrong?

pladmin@maser-devtest-kvm:~$ sudo apt-get update

Hit:1 http://au.archive.ubuntu.com/ubuntu bionic InRelease

Err:3 http://ppa.launchpad.net/ci-train-ppa-service/4503/ubuntu bionic
InRelease

  403  Forbidden [IP: 91.189.95.85 80]

Get:4 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7
kB]

Get:2 http://au.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]

Get:5 http://au.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6
kB]

Get:6 http://ppa.launchpad.net/ci-train-ppa-service/4529/ubuntu bionic
InRelease [20.8 kB]

Reading package lists... Done

E: Failed to fetch
http://ppa.launchpad.net/ci-train-ppa-service/4503/ubuntu/dists/bionic/InRelease
403  Forbidden [IP: 91.189.95.85 80]

E: The repository 'http://ppa.launchpad.net/ci-train-ppa-service/4503/ubuntu
bionic InRelease' is no longer signed.

N: Updating from such a repository can't be done securely, and is therefore
disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration
details.

E: Release file for
http://au.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease is not
valid yet (invalid for another 13d 20h 8min 41s). Updates for this
repository will not be applied.

E: Release file for
http://au.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease is not
valid yet (invalid for another 13d 20h 9min 42s). Updates for this
repository will not be applied.

E: Release file for
http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease is not
valid yet (invalid for another 13d 22h 14min 55s). Updates for this
repository will not be applied.

E: Release file for
http://ppa.launchpad.net/ci-train-ppa-service/4529/ubuntu/dists/bionic/InRelease
is not valid yet (invalid for another 9d 3h 57min 50s). Updates for this
repository will not be applied.
FRANCISCO MENCHACASALES ENGINEER | https://about.me/francisco.menchaca
fxm...@gmail.com | +61 406 204 483
<http://linkedin.com/in/franciscomenchaca>
<http://facebook.com/pacomenchaca>  <http://twitter.com/paquito_>

On Tue, 20 Apr 2021 at 01:41, Paco Menchaca  wrote:

> Hi Christian,
>
> We tried installing the build you supplied:
>
> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4529
>
> In two different systems running Ubuntu 18.04.5 and we received this error:
>
> pladmin@maser-devtest-kvm:~$ sudo add-apt-repository
> ppa:ci-train-ppa-service/4529
>
> [sudo] password for pladmin:
>
> Cannot add PPA: 'ppa:~ci-train-ppa-service/ubuntu/4529'.
>
> ERROR: '~ci-train-ppa-service' user or team does not exist.
>
>
>
>
>
>
>
>
>
> Also , is there a way to install the ppa manually??
>
> Thanks in advance.
>
> FRANCISCO MENCHACASALES ENGINEER | https://about.me/francisco.menchaca
> fxm...@gmail.com | +61 406 204 483
> <http://linkedin.com/in/franciscomenchaca>
>
>
> On Fri, 16 Apr 2021 at 16:15, Christian Ehrhardt  <
> 1921...@bugs.launchpad.net> wrote:
>
>> Hi Francisco,
>> I thought I had lost your activity on this case - glad to see you back on
>> it.
>> Yeah the old PPA is gone - you fell victim to my bi-yearly PPA cleanup :-)
>> At some point I have to give launchpad all its gigabytes back ...
>>
>> I rebased the branch (since it aged anyway) and have thrown a new build
>> into
>> this new PPA/ticket:
>>
>> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4529
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1921325
>>
>> Title:
>>   VM will not auto-start automatically when server is rebooted after
>>   virsh domrename
>>
>> Status in libvirt package in Ubuntu:
>>   Fix Released
>> Status in libvirt source package in Bionic:
>>   Triaged
>> Status in libvirt source package in Focal:
>>   Fix Released
>>
>> Bug description:
>>
>>   OS: Ubuntu 18.04.5
>>   uname -r
>>   4.15.0-118-generic
>>
>>
>>   /usr/bin/qemu-system-x86_64 --version
>>   QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.32)
>>
>>
>>   $ virsh version
>>   Compiled against library: libvirt 4.0.0
>>   Using library: libvirt 4.0.0
>>   Using API: QEMU 4.0.0
>>   Running hypervisor: QEMU 2.11.1
>>
>>   VM running on KVM on different servers won't start automatically when
>>   the server is rebooted after changing the VM domain name.
>>
>>   Issue Replication:
>>
>>   1. Set the VM to autostart
>>   2. Reboot the server
>>   3. VM will start automatically

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

2021-04-19 Thread Francisco Menchaca

Hi Christian,

We tried installing the build you supplied:

https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4529

In two different systems running Ubuntu 18.04.5 and we received this
error:

pladmin@maser-devtest-kvm:~$ sudo add-apt-repository
ppa:ci-train-ppa-service/4529

[sudo] password for pladmin:

Cannot add PPA: 'ppa:~ci-train-ppa-service/ubuntu/4529'.

ERROR: '~ci-train-ppa-service' user or team does not exist.





Also , is there a way to install the ppa manually??

Thanks in advance.

FRANCISCO MENCHACASALES ENGINEER | https://about.me/francisco.menchaca
fxm...@gmail.com | +61 406 204 483
<http://linkedin.com/in/franciscomenchaca>


On Fri, 16 Apr 2021 at 16:15, Christian Ehrhardt  <
1921...@bugs.launchpad.net> wrote:

> Hi Francisco,
> I thought I had lost your activity on this case - glad to see you back on
> it.
> Yeah the old PPA is gone - you fell victim to my bi-yearly PPA cleanup :-)
> At some point I have to give launchpad all its gigabytes back ...
>
> I rebased the branch (since it aged anyway) and have thrown a new build
> into
> this new PPA/ticket:
>
> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4529
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1921325
>
> Title:
>   VM will not auto-start automatically when server is rebooted after
>   virsh domrename
>
> Status in libvirt package in Ubuntu:
>   Fix Released
> Status in libvirt source package in Bionic:
>   Triaged
> Status in libvirt source package in Focal:
>   Fix Released
>
> Bug description:
>
>   OS: Ubuntu 18.04.5
>   uname -r
>   4.15.0-118-generic
>
>
>   /usr/bin/qemu-system-x86_64 --version
>   QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.32)
>
>
>   $ virsh version
>   Compiled against library: libvirt 4.0.0
>   Using library: libvirt 4.0.0
>   Using API: QEMU 4.0.0
>   Running hypervisor: QEMU 2.11.1
>
>   VM running on KVM on different servers won't start automatically when
>   the server is rebooted after changing the VM domain name.
>
>   Issue Replication:
>
>   1. Set the VM to autostart
>   2. Reboot the server
>   3. VM will start automatically
>   4. Changed the VM domain name virsh domrename VM.old VM.new
>   5. Set the VM.new domain to autostart
>   6. Reboot the server
>   7. VM.new won't start automatically.
>
>   Can you please assist?
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

2021-04-16 Thread Francisco Menchaca

Thank you very much Christian.

I apologise for not responding earlier.

Quick question do PPA's are integrated into future patches?

Thanks in advance for your help.

Regards,

Francisco

On Fri, 16 Apr 2021, 4:15 pm Christian Ehrhardt , <
1921...@bugs.launchpad.net> wrote:

> Hi Francisco,
> I thought I had lost your activity on this case - glad to see you back on
> it.
> Yeah the old PPA is gone - you fell victim to my bi-yearly PPA cleanup :-)
> At some point I have to give launchpad all its gigabytes back ...
>
> I rebased the branch (since it aged anyway) and have thrown a new build
> into
> this new PPA/ticket:
>
> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4529
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1921325
>
> Title:
>   VM will not auto-start automatically when server is rebooted after
>   virsh domrename
>
> Status in libvirt package in Ubuntu:
>   Fix Released
> Status in libvirt source package in Bionic:
>   Triaged
> Status in libvirt source package in Focal:
>   Fix Released
>
> Bug description:
>
>   OS: Ubuntu 18.04.5
>   uname -r
>   4.15.0-118-generic
>
>
>   /usr/bin/qemu-system-x86_64 --version
>   QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.32)
>
>
>   $ virsh version
>   Compiled against library: libvirt 4.0.0
>   Using library: libvirt 4.0.0
>   Using API: QEMU 4.0.0
>   Running hypervisor: QEMU 2.11.1
>
>   VM running on KVM on different servers won't start automatically when
>   the server is rebooted after changing the VM domain name.
>
>   Issue Replication:
>
>   1. Set the VM to autostart
>   2. Reboot the server
>   3. VM will start automatically
>   4. Changed the VM domain name virsh domrename VM.old VM.new
>   5. Set the VM.new domain to autostart
>   6. Reboot the server
>   7. VM.new won't start automatically.
>
>   Can you please assist?
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1921325] Re: VM will not auto-start automatically when server is rebooted after virsh domrename

2021-04-15 Thread Francisco Menchaca

Hi Christian,

Thank you very much for your help.

I tried creating the symlink manually and that worked.  However, I tried to
install the build from the launchpad
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4503/ and is
not available anymore.

Can you please make it available again? I need to install it on a couple of
production servers.

Thanks.

Francisco Menchaca


On Fri, 26 Mar 2021 at 20:30, Christian Ehrhardt  <
1921...@bugs.launchpad.net> wrote:

> Upstream issue: https://bugzilla.redhat.com/show_bug.cgi?id=1594985
> Upstream fix:
> https://gitlab.com/libvirt/libvirt/-/commit/359b938b8b37254e3e714a2a50e4b9a444516133
> I have a build for you to try in this PPA:
> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4503/
>
> Please let me know if that would work fine for you, then we can consider
> to start the SRU process
>
> ** Bug watch added: Red Hat Bugzilla #1594985
>https://bugzilla.redhat.com/show_bug.cgi?id=1594985
>
> ** Changed in: libvirt (Ubuntu Bionic)
>Status: Confirmed => Triaged
>
> ** Tags added: sever-next
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1921325
>
> Title:
>   VM will not auto-start automatically when server is rebooted after
>   virsh domrename
>
> Status in libvirt package in Ubuntu:
>   Fix Released
> Status in libvirt source package in Bionic:
>   Triaged
> Status in libvirt source package in Focal:
>   Fix Released
>
> Bug description:
>
>   OS: Ubuntu 18.04.5
>   uname -r
>   4.15.0-118-generic
>
>
>   /usr/bin/qemu-system-x86_64 --version
>   QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.32)
>
>
>   $ virsh version
>   Compiled against library: libvirt 4.0.0
>   Using library: libvirt 4.0.0
>   Using API: QEMU 4.0.0
>   Running hypervisor: QEMU 2.11.1
>
>   VM running on KVM on different servers won't start automatically when
>   the server is rebooted after changing the VM domain name.
>
>   Issue Replication:
>
>   1. Set the VM to autostart
>   2. Reboot the server
>   3. VM will start automatically
>   4. Changed the VM domain name virsh domrename VM.old VM.new
>   5. Set the VM.new domain to autostart
>   6. Reboot the server
>   7. VM.new won't start automatically.
>
>   Can you please assist?
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921325] [NEW] VM will not auto-start automatically when server is rebooted after virsh domrename

2021-03-25 Thread Francisco Menchaca

Public bug reported:


OS: Ubuntu 18.04.5
uname -r
4.15.0-118-generic


/usr/bin/qemu-system-x86_64 --version
QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.32)


$ virsh version
Compiled against library: libvirt 4.0.0
Using library: libvirt 4.0.0
Using API: QEMU 4.0.0
Running hypervisor: QEMU 2.11.1

VM running on KVM on different servers won't start automatically when
the server is rebooted after changing the VM domain name.

Issue Replication:

1. Set the VM to autostart
2. Reboot the server
3. VM will start automatically
4. Changed the VM domain name virsh domrename VM.old VM.new
5. Set the VM.new domain to autostart
6. Reboot the server
7. VM.new won't start automatically. 

Can you please assist?

** Affects: libvirt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921325

Title:
  VM will not auto-start automatically when server is rebooted after
  virsh domrename

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904789] Re: [snap] Cannot confirm security exception for invalid certificate

2021-02-24 Thread Francisco Robles Martín

Same issue here. I end up downloading the tar.bz2 package with the
latest version and installing it myself. Will keep an eye to move back
to snap once this is fixed :(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904789

Title:
  [snap] Cannot confirm security exception for invalid certificate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915396] Re: /etc/lsb-release pointing to 18.04 after upgrade to 20.04

2021-02-15 Thread Francisco Robles Martín

Hi again Brian!

The content of /etc/lsb-release is in the first bug description (at the
top of this page.

The output of the command (I executed it with /etc/lsb-release as well)
are:

$ dpkg -S /etc/lsb-release.oem-release
diversion by oem-release from: /etc/lsb-release
diversion by oem-release to: /etc/lsb-release.oem-release


$ dpkg -S /etc/lsb-release
diversion by oem-release from: /etc/lsb-release
diversion by oem-release to: /etc/lsb-release.oem-release
base-files: /etc/lsb-release

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915396

Title:
  /etc/lsb-release pointing to 18.04 after upgrade to 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1915396/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915396] Re: /etc/lsb-release pointing to 18.04 after upgrade to 20.04

Hi Brian! Thank to you for replying! :)

Yes, there is indeed. This is what I have in that file and the /etc
folder and relating to release as well:

fran@fran-xps:/etc $ ll | grep lsb
-rw-r--r--   1 root root  133 ene 14 23:23 lsb-release
-rw-r--r--   1 root root  104 ene 27 10:38 lsb-release.oem-release
fran@fran-xps:/etc $ cat lsb-release.oem-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS"
fran@fran-xps:/etc $ ll | grep release
-rw-r--r--   1 root root  133 ene 14 23:23 lsb-release
-rw-r--r--   1 root root  104 ene 27 10:38 lsb-release.oem-release
lrwxrwxrwx   1 root root   21 ene 27 10:40 os-release -> 
../usr/lib/os-release
fran@fran-xps:/etc $ cat os-release 
NAME="Ubuntu"
VERSION="20.04.2 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.2 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915396

Title:
  /etc/lsb-release pointing to 18.04 after upgrade to 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1915396/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915396] Re: /etc/lsb-release pointing to 18.04 after upgrade to 20.04

Please find attached the /var/log/dist-upgrade folder in a zip file.

** Attachment added: "dist-upgrade logs"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1915396/+attachment/5462683/+files/dist-upgrade.zip

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915396

Title:
  /etc/lsb-release pointing to 18.04 after upgrade to 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1915396/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915396] Re: /etc/lsb-release pointing to 18.04 after upgrade to 20.04

** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915396

Title:
  /etc/lsb-release pointing to 18.04 after upgrade to 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1915396/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915396] [NEW] /etc/lsb-release pointing to 18.04 after upgrade to 20.04

Public bug reported:

Hello,

I have a Dell XPS 13 7390. It came with Ubuntu 18.04 LTS installed, and
then I upgraded it to 20.04 LTS (20.04.2 LTS).

I was installing git-lfs now, and thanks to the script they use to
determine the OS (https://packagecloud.io/install/repositories/github
/git-lfs/script.deb.sh detect_os function), I have found that in the
file /etc/lsb-release, it still points to 18.04. This is the current
content:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS (beaver-three-eyed-raven X92)"

Meanwhile, if I get the Ubuntu version with "lsb_release -a" command, I
get:

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal

Is this normal or there were some issue during the upgrade? Is the file
/etc/lsb-release deprecated? Should I fill it with the current values or
may I break something?

Thank you in advance!
Francisco Robles

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: dist-upgrade lsb-release

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915396

Title:
  /etc/lsb-release pointing to 18.04 after upgrade to 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1915396/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2021-02-07 Thread Francisco A . Hernández

Same issue here. As many others here, I need to use the mic at work's
meetings and I needed to spent extra money on a wired headset because of
this bug made my airpods useless for the task.

elementary OS 5.1.7 Hera, Built on Ubuntu 18.04.4 LTS.
Linux 4.15.0-135-generic.

$pactl list cards
Card #0
Name: alsa_card.pci-_00_1b.0
Driver: module-alsa-card.c
Owner Module: 7
Properties:
alsa.card = "0"
alsa.card_name = "HDA Intel"
alsa.long_card_name = "HDA Intel at 0xf000 irq 26"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "27d8"
device.product.name = "NM10/ICH7 Family High Definition Audio 
Controller"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Profiles:
input:analog-stereo: Analog Stereo Input (sinks: 0, sources: 1, 
priority: 60, available: no)
output:analog-stereo: Analog Stereo Output (sinks: 1, sources: 
0, priority: 6000, available: yes)
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex 
(sinks: 1, sources: 1, priority: 6060, available: yes)
output:iec958-stereo: Digital Stereo (IEC958) Output (sinks: 1, 
sources: 0, priority: 5500, available: yes)
output:iec958-stereo+input:analog-stereo: Digital Stereo 
(IEC958) Output + Analog Stereo Input (sinks: 1, sources: 1, priority: 5560, 
available: yes)
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: output:analog-stereo+input:analog-stereo
Ports:
analog-input-mic: Microphone (priority: 8700, latency offset: 0 
usec, not available)
Properties:
device.icon_name = "audio-input-microphone"
Part of profile(s): input:analog-stereo, 
output:analog-stereo+input:analog-stereo, 
output:iec958-stereo+input:analog-stereo
analog-output-speaker: Speakers (priority: 1, latency 
offset: 0 usec)
Properties:
device.icon_name = "audio-speakers"
Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-stereo
analog-output-headphones: Headphones (priority: 9000, latency 
offset: 0 usec, not available)
Properties:
device.icon_name = "audio-headphones"
Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-stereo
iec958-stereo-output: Digital Output (S/PDIF) (priority: 0, 
latency offset: 0 usec)
Part of profile(s): output:iec958-stereo, 
output:iec958-stereo+input:analog-stereo

Card #7
Name: bluez_card.AC_80_1C_01_34_B0
Driver: module-bluez5-device.c
Owner Module: 33
Properties:
device.description = "Baseus Encok W04 Pro"
device.string = "AC:80:1C:01:34:B0"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_AC_80_1C_01_34_B0"
bluez.class = "0x240404"
bluez.alias = "Baseus Encok W04 Pro"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
Profiles:
a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, 
sources: 0, priority: 40, available: yes)
headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, 
sources: 1, priority: 30, available: no)
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: off
Ports:
headset-output: Headset (priority: 0, latency offset: 0 usec)
Part of profile(s): a2dp_sink, headset_head_unit
headset-input: Headset (priority: 0, latency offset: 0 usec, 
not available)
Part of profile(s): headset_head_unit

$ bluetoothctl

[NEW] Controller 00:1A:7D:DA:71:11 siemens-AMILO-Pi-1505 [default]
[NEW] Device AC:80:1C:01:34:B0 Fran Hdez's Airpods
[NEW] Device 4B:A3:18:BC:21:5B Sony Home Sound System
[NEW] Device 2B:20:C2:C6:E1:5D Bose QC25
[NEW] Device B1:81:AE:C5:1D:20 Home Living Room Pioneer Sound System
Agent registered
[Fran Hdez's Airpods]# info

[Bug 1878045] Re: doing dist-upgrade got error related do Broadcom

2021-01-17 Thread Francisco Morelli

Thanks joaorami (joaomppr)!
I've tried your solution and is working fine for BCM4312 on Ubuntu 20.04 with 
kernel 5.8.0-38

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878045

Title:
  doing dist-upgrade got error related do Broadcom

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901945] Re: Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting Virtual machine.

2020-12-30 Thread Francisco Milán

** Package changed: minisapserver (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901945

Title:
  Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting
  Virtual machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1901945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909729] Re: Remaining time while running "sudo apt upgrade"

2020-12-30 Thread Francisco Milán

Hi Chris,

Thanks a lot for your guidance in using the apport tool, I ran the command 
that you provided and now I see some details were automatically added to the 
bug report.
In future bug reports, I'll try to follow your instructions. My apologies for 
not using the apport command before, but this is just the third bug that I've 
reported ever, and I was not familiar with the use of this tool.

Best regards,

Paco Milan.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909729

Title:
  Remaining time while running "sudo apt upgrade"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1909729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909729] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1909729/+attachment/5448203/+files/ProcEnviron.txt

** Description changed:

  Hi there,
  
     After running "sudo apt upgrade" in a Terminal window I noticed that
  the remaining time for 1 minute is displayed as "60s", I think to keep
  consistency this would need to be displayed as "1min 0s" since at some
  point I also saw the remaining time displayed as "5min 0s" (refer to the
  attached images). Going even further I would recommend removing the "0s"
- from the remaining time when applicable, e.g. displaying only "5min"
- instead of "5min 0s", "1min" instead of "1min 0s" and so on.
+ portion from the remaining time when applicable, e.g. displaying only
+ "5min" instead of "5min 0s", "1min" instead of "1min 0s" and so on.
  
  I'm using Ubuntu 20.04 (Focal Fossa).
  
  Best regards,
  
  Paco Milán.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-06 (299 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: apt 2.0.2ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-10 (235 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf
  _MarkForUpload: True

** Description changed:

  Hi there,
  
     After running "sudo apt upgrade" in a Terminal window I noticed that
  the remaining time for 1 minute is displayed as "60s", I think to keep
  consistency this would need to be displayed as "1min 0s" since at some
  point I also saw the remaining time displayed as "5min 0s" (refer to the
  attached images). Going even further I would recommend removing the "0s"
  portion from the remaining time when applicable, e.g. displaying only
- "5min" instead of "5min 0s", "1min" instead of "1min 0s" and so on.
+ "5min" instead of "5min 0s", "1min" instead of "1min 0s", and so on.
  
  I'm using Ubuntu 20.04 (Focal Fossa).
  
  Best regards,
  
  Paco Milán.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-06 (299 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: apt 2.0.2ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-10 (235 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf
  _MarkForUpload: True

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909729

Title:
  Remaining time while running "sudo apt upgrade"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1909729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909729] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1909729/+attachment/5448202/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909729

Title:
  Remaining time while running "sudo apt upgrade"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1909729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909729] Re: Remaining time while running "sudo apt upgrade"

apport information

** Tags added: apport-collected focal

** Description changed:

  Hi there,
  
     After running "sudo apt upgrade" in a Terminal window I noticed that
  the remaining time for 1 minute is displayed as "60s", I think to keep
  consistency this would need to be displayed as "1min 0s" since at some
  point I also saw the remaining time displayed as "5min 0s" (refer to the
  attached images). Going even further I would recommend removing the "0s"
  from the remaining time when applicable, e.g. displaying only "5min"
  instead of "5min 0s", "1min" instead of "1min 0s" and so on.
  
  I'm using Ubuntu 20.04 (Focal Fossa).
  
  Best regards,
  
  Paco Milán.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.12
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-03-06 (299 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Package: apt 2.0.2ubuntu0.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
+ Tags:  focal
+ Uname: Linux 5.4.0-54-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-05-10 (235 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1909729/+attachment/5448201/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909729

Title:
  Remaining time while running "sudo apt upgrade"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1909729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909729] Re: Remaining time while running "sudo apt upgrade"

** Attachment added: "Ubuntu version.jpg"

https://bugs.launchpad.net/ubuntu/+bug/1909729/+attachment/5448175/+files/Ubuntu%20version.jpg

** Description changed:

Hi there,

-After running "sudo apt upgrade" in a Terminal window I noticed that
- the remaining time for 1 minute is displayed as "60 s", I think to keep
+ After running "sudo apt upgrade" in a Terminal window I noticed that
+ the remaining time for 1 minute is displayed as "60s", I think to keep
consistency this would need to be displayed as "1m 0s" since at some
point I also saw the remaining time displayed as "5min 0s" (refer to the
attached images). Going even further I would recommend removing the "0s"
from the remaining time when applicable, e.g. displaying only "5min"
instead of "5min 0s", "1min" instead of "1min 0s" and so on.

I'm using Ubuntu 20.04 (Focal Fossa).

Best regards,

Paco Milán.

** Description changed:

Hi there,

After running "sudo apt upgrade" in a Terminal window I noticed that
the remaining time for 1 minute is displayed as "60s", I think to keep
- consistency this would need to be displayed as "1m 0s" since at some
+ consistency this would need to be displayed as "1min 0s" since at some
point I also saw the remaining time displayed as "5min 0s" (refer to the
attached images). Going even further I would recommend removing the "0s"
from the remaining time when applicable, e.g. displaying only "5min"
instead of "5min 0s", "1min" instead of "1min 0s" and so on.

I'm using Ubuntu 20.04 (Focal Fossa).

Best regards,

Paco Milán.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909729

Title:
Remaining time while running "sudo apt upgrade"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1909729/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909729] Re: Remaining time while running "sudo apt upgrade"

** Attachment added: "5min 0s.jpg"
   
https://bugs.launchpad.net/ubuntu/+bug/1909729/+attachment/5448171/+files/5min%200s.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909729

Title:
  Remaining time while running "sudo apt upgrade"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1909729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909729] Re: Remaining time while running "sudo apt upgrade"

** Attachment added: "60s.jpg"
   
https://bugs.launchpad.net/ubuntu/+bug/1909729/+attachment/5448173/+files/60s.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909729

Title:
  Remaining time while running "sudo apt upgrade"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1909729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909729] [NEW] Remaining time while running "sudo apt upgrade"

Public bug reported:

Hi there,

   After running "sudo apt upgrade" in a Terminal window I noticed that
the remaining time for 1 minute is displayed as "60s", I think to keep
consistency this would need to be displayed as "1min 0s" since at some
point I also saw the remaining time displayed as "5min 0s" (refer to the
attached images). Going even further I would recommend removing the "0s"
from the remaining time when applicable, e.g. displaying only "5min"
instead of "5min 0s", "1min" instead of "1min 0s" and so on.

I'm using Ubuntu 20.04 (Focal Fossa).

Best regards,

Paco Milán.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909729

Title:
  Remaining time while running "sudo apt upgrade"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1909729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1669734] Re: Quality decrease in libgd3 with upgrade to 2.1.1-4ubuntu0.16.04.5

2020-11-02 Thread Pedro Francisco

For reference, bug referred is
«Fixed bug #45030 (Destination image alpha channel noise when using 
imagecopyresampled). (Pierre)» from php-5.3.0beta1 release notes.

I was able to find a copy of the commit here
https://repos.bgemi.net/sikofitt/php-
src/-/commit/a3383ac3d7e21e54b1d7d89f308088d0692abc9f .

You'll have to compare the source and check if it is not fixed on
Ubuntu's package, or if it is a new, unrelated bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669734

Title:
  Quality decrease in libgd3 with upgrade to 2.1.1-4ubuntu0.16.04.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgd2/+bug/1669734/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901377] Re: Incorrect label in Software Updater

2020-10-31 Thread Francisco Milan

Hi Timo,

Shouldn't this fix be accepted into focal-proposed instead?

As you can see in the attached image, I would be able to test it with:
> "Software & Updates"
> "Developer Options"
> "Pre-released updates (focal-proposed)"

Thanks,

Paco Milan.

** Attachment added: "Capture.PNG"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901377/+attachment/5429919/+files/Capture.PNG

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901377

Title:
  Incorrect label in Software Updater

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901377/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901945] Re: Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting Virtual machine.

** Tags added: minisap

** Tags added: gorilla groovy

** Tags added: sybase

** Tags added: 20.10

** Tags removed: gorilla groovy
** Tags added: groovygorilla

** Tags removed: groovygorilla
** Tags added: groovy-gorilla

** Tags added: sap

** Tags added: virtualbox virtualmachine

** Tags added: upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901945

Title:
  Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting
  Virtual machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901945] Re: Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting Virtual machine.

** Attachment added: "Image 01 - startsap_D00.log"
   
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+attachment/5428684/+files/Image%2001%20-%20startsap_D00.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901945

Title:
  Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting
  Virtual machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901945] Re: Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting Virtual machine.

** Attachment added: "Image 02.png"
   
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+attachment/5428685/+files/Image%2002.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901945

Title:
  Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting
  Virtual machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901945] [NEW] Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting Virtual machine.

Public bug reported:

Hi there,

I think I found an issue and I wonder if you can have a look at
this.

Background:
I have Focal Fossa on VirtualBox and I use it to run SAP NetWeaver Developer 
Edition (refer to the link at the bottom of this message), after upgrading to 
Groovy Gorilla I'm able to start the sap server and I can log in to the SAP 
system, I'm also able to restart the sap server as many times as I want and I 
can also log in to SAP without any problem (see the attached file "Image 
01.png" and related log files).

Issue:
After restarting the virtual machine I'm not able to start the sap server 
anymore (see the attached file "Image 02.png" and related log file).

I don't know the specific package in Ubuntu that has the issue, so I'm
not sure if I'm filing this bug in the correct area, I started using
this tool to report bugs recently (this is just the second Ubuntu issue
I have reported ever).

Please let me know in case you need any additional information to fix
this issue.

Thanks a lot,

Francisco Milan.

"Installing SAP NetWeaver Developer Edition on an Ubuntu desktop VM – the 
non-concise guide"
https://blogs.sap.com/2018/04/05/installing-sap-netweaver-developer-edition-on-an-ubuntu-desktop-vm-the-non-concise-guide/

** Affects: minisapserver (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Image 01.png"
   
https://bugs.launchpad.net/bugs/1901945/+attachment/5428674/+files/Image%2001.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901945

Title:
  Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting
  Virtual machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901945] Re: Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting Virtual machine.

** Attachment added: "Image 02 - startdb.log"
   
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+attachment/5428686/+files/Image%2002%20-%20startdb.log

** Description changed:

  Hi there,
  
- I think I found an issue and I wonder if you can have a look at
+ I think I found an issue and I wonder if you can have a look at
  this.
  
  Background:
- I have Ubuntu 20.04 on VirtualBox and I use it to run SAP NetWeaver Developer 
Edition (refer to the link at the bottom of this message), after installing 
Ubuntu 20.10 I'm able to start the sap server and I can to login to SAP system, 
I'm also able to restart the sap server as many times as I want and I can also 
login to SAP without any problem. (see the attached file "Image 01.png" and 
related log files).
+ I have Ubuntu 20.04 on VirtualBox and I use it to run SAP NetWeaver Developer 
Edition (refer to the link at the bottom of this message), after upgrading to 
Groovy Gorilla I'm able to start the sap server and I can to login to SAP 
system, I'm also able to restart the sap server as many times as I want and I 
can also login to SAP without any problem. (see the attached file "Image 
01.png" and related log files).
  
  Issue:
-  After restarting the virtual machine I'm not able to start the sap server 
anymore (see the attached file "Image 02.png" and related log file).
+  After restarting the virtual machine I'm not able to start the sap server 
anymore (see the attached file "Image 02.png" and related log file).
  
- 
- I don't know the specific package in Ubuntu that has the issue, so I'm not 
sure if I'm filing this bug in the correct area, I starting using this tool to 
report bugs recently (this is just the second Ubuntu issue I have reported 
ever).
+ I don't know the specific package in Ubuntu that has the issue, so I'm
+ not sure if I'm filing this bug in the correct area, I starting using
+ this tool to report bugs recently (this is just the second Ubuntu issue
+ I have reported ever).
  
  Please let me know in case you need any additional information to fix
  this issue.
- 
  
  Thanks a lot,
  
  Francisco Milan.
  
  "Installing SAP NetWeaver Developer Edition on an Ubuntu desktop VM – the 
non-concise guide"
  
https://blogs.sap.com/2018/04/05/installing-sap-netweaver-developer-edition-on-an-ubuntu-desktop-vm-the-non-concise-guide/

** Description changed:

  Hi there,
  
  I think I found an issue and I wonder if you can have a look at
  this.
  
  Background:
- I have Ubuntu 20.04 on VirtualBox and I use it to run SAP NetWeaver Developer 
Edition (refer to the link at the bottom of this message), after upgrading to 
Groovy Gorilla I'm able to start the sap server and I can to login to SAP 
system, I'm also able to restart the sap server as many times as I want and I 
can also login to SAP without any problem. (see the attached file "Image 
01.png" and related log files).
+ I have Focal Fossa on VirtualBox and I use it to run SAP NetWeaver Developer 
Edition (refer to the link at the bottom of this message), after upgrading to 
Groovy Gorilla I'm able to start the sap server and I can to login to SAP 
system, I'm also able to restart the sap server as many times as I want and I 
can also login to SAP without any problem. (see the attached file "Image 
01.png" and related log files).
  
  Issue:
   After restarting the virtual machine I'm not able to start the sap server 
anymore (see the attached file "Image 02.png" and related log file).
  
  I don't know the specific package in Ubuntu that has the issue, so I'm
  not sure if I'm filing this bug in the correct area, I starting using
  this tool to report bugs recently (this is just the second Ubuntu issue
  I have reported ever).
  
  Please let me know in case you need any additional information to fix
  this issue.
  
  Thanks a lot,
  
  Francisco Milan.
  
  "Installing SAP NetWeaver Developer Edition on an Ubuntu desktop VM – the 
non-concise guide"
  
https://blogs.sap.com/2018/04/05/installing-sap-netweaver-developer-edition-on-an-ubuntu-desktop-vm-the-non-concise-guide/

** Description changed:

  Hi there,
  
  I think I found an issue and I wonder if you can have a look at
  this.
  
  Background:
- I have Focal Fossa on VirtualBox and I use it to run SAP NetWeaver Developer 
Edition (refer to the link at the bottom of this message), after upgrading to 
Groovy Gorilla I'm able to start the sap server and I can to login to SAP 
system, I'm also able to restart the sap server as many times as I want and I 
can also login to SAP without any problem. (see the attached file "Image 
01.png" and related log files).
+ I have Focal Fossa on VirtualBox and I use it to run SAP NetWeaver Developer 
Edition (refer to the link at the bottom of this message), after upgrading to 
Groovy Gorilla I'm able to start the sap server and I can logi

[Bug 1901945] Re: Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting Virtual machine.

** Attachment added: "Image 01 - startsap_ASCS01.log"
   
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+attachment/5428683/+files/Image%2001%20-%20startsap_ASCS01.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901945

Title:
  Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting
  Virtual machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901945] Re: Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting Virtual machine.

** Attachment added: "Image 01 - startdb.log"
   
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+attachment/5428675/+files/Image%2001%20-%20startdb.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901945

Title:
  Upgraded to Ubuntu 20.10. Can't start Mini SAP server after restarting
  Virtual machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/minisapserver/+bug/1901945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1899073] Re: Upgrade to release 20.04 from 18.04 failed

2020-10-11 Thread Francisco J. Murillo

*** This bug is a duplicate of bug 1898152 ***
https://bugs.launchpad.net/bugs/1898152

After removing gnuradio-dev, the upgrade completed successfully.

Many thanks to everyone for your help.

Kind regards,

Francisco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899073

Title:
  Upgrade to release 20.04 from 18.04 failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1899073/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1899073] [NEW] Upgrade to release 20.04 from 18.04 failed

2020-10-08 Thread Francisco J. Murillo

Public bug reported:

Attempted to upgrade from 18.04 to the newer LTS rel 20.04. Process
stopped  and a pop-up window indicated that a bug made the upgrade to
fail, suggesting to report the bug via "ubuntu-bug ubuntu-release-
upghrader-core" as I did, since I couldn't find any clue after checking
the suggested logs.

I'll be glad to send you any further information you may need to address
the failure.

Many thanks and regards.

Francisco.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME-Flashback:GNOME
Date: Thu Oct  8 21:25:26 2020
InstallationDate: Installed on 2019-02-05 (610 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-10-08 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899073

Title:
  Upgrade to release 20.04 from 18.04 failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1899073/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767299] Re: Ubuntu 18.04-20.04 Installer creates swap partition too small

2020-10-08 Thread Francisco Marques

It looks like this is still a problem in Ubuntu 20.
Can we remove 18.04-20.04 from the title?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767299

Title:
  Ubuntu 18.04-20.04 Installer creates swap partition too small

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897814] [NEW] package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1

2020-09-29 Thread Francisco Ernesto Teixeira

Public bug reported:

Just tried do-release-upgrade

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lxd 3.0.3-0ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-1026.26~18.04.1-azure 5.4.60
Uname: Linux 5.4.0-1026-azure x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Sep 29 22:21:30 2020
ErrorMessage: new lxd package pre-installation script subprocess returned error 
exit status 1
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: lxd
Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd 
package pre-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-09-29 (0 days ago)

** Affects: lxd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal third-party-packages uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897814

Title:
  package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd
  package pre-installation script subprocess returned error exit status
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1897814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

2020-09-03 Thread Francisco Soares

+1 same problem with me, asus UX425JA

5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878058] [NEW] Installer Crashed during Kubuntu instalation

2020-05-11 Thread Francisco Schmidt

Public bug reported:

Installation crashed during Kubuntu install process

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.445
CurrentDesktop: KDE
Date: Mon May 11 17:16:46 2020
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed maybe-ubiquity 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
LiveMediaBuild: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal kubuntu ubiquity-20.04.15

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878058

Title:
  Installer Crashed during Kubuntu instalation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1878058/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873277] [NEW] unable to continue installation from usb past a certain point

2020-04-16 Thread Francisco Guimaraes

Public bug reported:

trying to install ubuntu in 2011 computer which previously had windows
7. Used universal usb installer to create installation drive, cannot
advance past point where I was asked to create a password to encrypt
hard drive

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.14
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CasperVersion: 1.394.3
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 16 13:49:19 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid 
initrd=/casper/initrd quiet splash --- BOOT_IMAGE=/casper/vmlinuz
LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.14 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873277

Title:
  unable to continue installation from usb past a certain point

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1873277/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

2020-04-08 Thread Francisco Pombal

I was able to fully fix the issue of the microphone not working on my UX430UA 
by doing this:
https://forums.linuxmint.com/viewtopic.php?p=1790578#p1790578

Original source linked in that forum post:
https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX430/UX530#Headset_Microphone

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596381

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867148] Re: fprintd fails after libgusb2 update to 0.3.4-0ubuntu1

2020-03-18 Thread Francisco Gonzalez

Updating to:
libfprint-2-2:amd641:1.90.1+tod1-0ubuntu4
libgusb2:amd64 0.3.4-0.1
the problem has disappeared


** Changed in: libfprint (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867148

Title:
  fprintd fails after libgusb2 update to 0.3.4-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1867148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867148] Re: fprintd fails after libgusb2 update to 0.3.4-0ubuntu1

2020-03-13 Thread Francisco Gonzalez

** Package changed: fprintd (Ubuntu) => libfprint (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867148

Title:
  fprintd fails after libgusb2 update to 0.3.4-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1867148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867148] Re: fprintd fails after libgusb2 update to 0.3.4-0ubuntu1

2020-03-13 Thread Francisco Gonzalez

Hi, I have just rebuilt from ubuntu source the package: libfprint-2-tod1
(new version 1:1.90.1+tod1-0ubuntu3)
and the problem has disappeared.

So I think it is just the actual package is not linked against
the correct library.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867148

Title:
  fprintd fails after libgusb2 update to 0.3.4-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1867148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867148] [NEW] fprintd fails after libgusb2 update to 0.3.4-0ubuntu1

2020-03-12 Thread Francisco Gonzalez

Public bug reported:

Versions:
Distributor ID: Ubuntu
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
Codename:   focal
Linux 5.4.0-14-generic #17-Ubuntu SMP
fprintd 1.90.1-1
libgusb2 0.3.4-0ubuntu1

What happens:

fprintd.service  Fingerprint Authentication Daemon, fails to load

journalctl -xe:
fprintd[10586]: /usr/libexec/fprintd: symbol lookup error:  
/lib/x86_64-linux-gnu/libfprint-2.so.2: undefined symbol: 
g_usb_device_get_release,  version LIBGUSB_0.1.0

Downgrading libgusb2 to 0.3.0-1 solves the problem.

What should happen:
fprintd.service not fail

** Affects: fprintd (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Versions:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal
  Linux 5.4.0-14-generic #17-Ubuntu SMP
  fprintd 1.90.1-1
  libgusb2 0.3.4-0ubuntu1
  
  What happens:
  
- fprintd.service loaded failed failed Fingerprint Authentication Daemon
+ fprintd.service  Fingerprint Authentication Daemon, fails to load
  
  journalctl -xe:
  fprintd[10586]: /usr/libexec/fprintd: symbol lookup error:  
/lib/x86_64-linux-gnu/libfprint-2.so.2: undefined symbol: 
g_usb_device_get_release,  version LIBGUSB_0.1.0
  
  Downgrading libgusb2 to 0.3.0-1 solves the problem.
  
  What should happen:
  fprintd.service not fail

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867148

Title:
  fprintd fails after libgusb2 update to 0.3.4-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1867148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1517884] Re: libxp6 not available in xenial

2020-02-17 Thread Francisco Panis Kaseker

Does anyone know if there are a libxp for armhf? I only found for x86.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517884

Title:
  libxp6 not available in xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxp/+bug/1517884/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861717] Re: Desktop interface is rotated 180 degrees

2020-02-04 Thread Francisco Manuel

apport information

** Tags added: apport-collected

** Description changed:

- I have an HP Pavilion dv7 and when I download Ubuntu version 19. 04 and
- install it on my laptop, the interface appears face down. The
- functionality of the buttons or icons is normal, that is, the only thing
- that appears upside down is the image.
+ I have an HP Pavilion dv7 and when I download Ubuntu version 19. 04 and 
install it on my laptop, the interface appears face down. The functionality of 
the buttons or icons is normal, that is, the only thing that appears upside 
down is the image.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2020-02-03 (0 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Package: iio-sensor-proxy 2.8-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=es_ES.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
+ Tags:  eoan
+ Uname: Linux 5.3.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1861717/+attachment/5325199/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861717

Title:
  Desktop interface is rotated 180 degrees

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1861717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861717] ProcCpuinfoMinimal.txt

2020-02-04 Thread Francisco Manuel

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1861717/+attachment/5325200/+files/ProcCpuinfoMinimal.txt

** Changed in: iio-sensor-proxy (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861717

Title:
  Desktop interface is rotated 180 degrees

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1861717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861717] Re: Desktop interface is rotated when installing version 19.04

2020-02-03 Thread Francisco Manuel

I updated to 19.10 and the same thing continues

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861717

Title:
  Desktop interface is rotated when installing version 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1861717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

2020-01-23 Thread Francisco Sánchez-Aedo Gálvez

I just installed the 19.10 server iso and the machine doesn't use the
DNS server provided through DHCP.

As a workaround I had to:
$ sudo rm /etc/resolv.conf
$ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624320

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767299] Re: Ubuntu 18.04 Installer creates swap partition too small

2019-12-16 Thread Francisco Marques

I'm sorry, I had no intention to change the visibility of the bug, I
have reverted the change.

Regarding this bug, the average user should not, in any way have such a
low amount of swap by default. I think this bug is very relevant and
therefore an Importance should be assigned.

I have this bug installing 18.04.3 LTS via the quick setup with full
disk encryption on both Lenovo idealpad 720 and Thinkpad 13.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767299

Title:
  Ubuntu 18.04 Installer creates swap partition too small

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827732] Re: ocrfeeder won't start: ModuleNotFoundError: No module named 'ocrfeeder'

2019-09-19 Thread Francisco Ramirez

** Also affects: ocrfeeder
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827732

Title:
  ocrfeeder won't start: ModuleNotFoundError: No module named
  'ocrfeeder'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ocrfeeder/+bug/1827732/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

2019-07-20 Thread Francisco Lopes

@vanvugt can this fix be backported to gnome-3-32 branch? I just talked
to the package maintainer in Arch repos and they said 3.33.4 is odd
numbered, hence not a stable release, so we would have to wait for 3.34,
but given how this is affecting many people I wished it sooner rather
than later. They said they track 3.32, so if it gets backported, the
package registry will pick it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809407

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829025] [NEW] mouse

2019-05-14 Thread Francisco Valdes

Public bug reported:

mousse dont work well

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue May 14 10:20:32 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 82946GZ/GL Integrated Graphics Controller [8086:2972] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 82946GZ/GL Integrated Graphics Controller [17aa:300b]
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=876b673d-874d-476c-90be-90e7f71c5a7e ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/2007
dmi.chassis.vendor: LENOVO
dmi.product.name: 9642A34
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue May 14 09:21:50 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: modeset

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829025

Title:
  mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1829025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821545] [NEW] package bash 4.3-14ubuntu1 failed to install/upgrade: package bash is already installed and configured

2019-03-24 Thread Francisco Angel Javier Prieto

Public bug reported:

when install ever fatal error with idle-python3.5
I have Raspberry pi 3

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bash 4.3-14ubuntu1
Uname: Linux 4.1.19-v7+ armv7l
ApportVersion: 2.20.1-0ubuntu2
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: armhf
Date: Sun Mar 24 19:14:22 2019
ErrorMessage: package bash is already installed and configured
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: dpkg
Title: package bash 4.3-14ubuntu1 failed to install/upgrade: package bash is 
already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dpkg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed apport-package armhf xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821545

Title:
  package bash 4.3-14ubuntu1 failed to install/upgrade: package bash is
  already installed and configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1821545/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815965] [NEW] package grub-efi-amd64-signed 1.93.13+2.02-2ubuntu8.12 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit st

2019-02-14 Thread Francisco Ros Gascons

Public bug reported:

Updating software

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64-signed 1.93.13+2.02-2ubuntu8.12
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Feb 14 16:10:52 2019
ErrorMessage: installed grub-efi-amd64-signed package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-11-30 (76 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.8
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.93.13+2.02-2ubuntu8.12 failed to 
install/upgrade: installed grub-efi-amd64-signed package post-installation 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub2-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815965

Title:
  package grub-efi-amd64-signed 1.93.13+2.02-2ubuntu8.12 failed to
  install/upgrade: installed grub-efi-amd64-signed package post-
  installation script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1815965/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813309] [NEW] compiling TDA produce error: ‘next’ is not a member of ‘boost’

2019-01-25 Thread francisco javier

Public bug reported:

error: ‘next’ is not a member of ‘boost’ 
According with this page
"https://svn.boost.org/trac10/ticket/13497;
The bug was already fixed 
bug 13497 but no in ubuntu 18.

I am trying to compile TDA for R and produce that error.

** Affects: boost-defaults (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813309

Title:
  compiling TDA produce error: ‘next’ is not a member of ‘boost’

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost-defaults/+bug/1813309/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811513] [NEW] package mysql-server-5.7 5.7.24-0ubuntu0.18.10.1 failed to install/upgrade: instalado mysql-server-5.7 paquete post-installation guión el subproceso devolvió un error con estado de

2019-01-12 Thread Francisco Javier Azores Rayo

Public bug reported:

ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: mysql-server-5.7 5.7.24-0ubuntu0.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Sat Jan 12 13:42:55 2019
ErrorMessage: instalado mysql-server-5.7 paquete post-installation guión el 
subproceso devolvió un error con estado de salida 1
InstallationDate: Installed on 2018-11-26 (46 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: ['auto.cnf', 'ibdata1', 'performance_schema', 'sys', 
'ib_buffer_pool', 'ib_logfile1', 'mysql', 'debian-5.7.flag', 'ib_logfile0']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=08be34a2-29bd-4936-ade2-4443a7d195da ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.24-0ubuntu0.18.10.1 failed to 
install/upgrade: instalado mysql-server-5.7 paquete post-installation guión el 
subproceso devolvió un error con estado de salida 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mysql-5.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811513

Title:
  package mysql-server-5.7 5.7.24-0ubuntu0.18.10.1 failed to
  install/upgrade: instalado mysql-server-5.7 paquete post-installation
  guión el subproceso devolvió un error con estado de salida 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1811513/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1807399] [NEW] package libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2018-12-07 Thread francisco

Public bug reported:

ola

ProblemType: Package
DistroRelease: elementary 0.4.1
Package: libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Tue Dec  4 22:59:18 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2018-11-25 (11 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29
SourcePackage: systemd
Title: package libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package loki third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807399

Title:
  package libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 128

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807399/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1798418] Re: Liferea massive memory leak

2018-12-06 Thread Francisco Pombal

> Cosmic has 1.12.5-2

I am aware of this, but will the relevant fix be backported to Bionic?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798418

Title:
  Liferea massive memory leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1798418/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1806176] [NEW] package virtualbox-ext-pack 5.2.18-1~ubuntu18.04.1 failed to install/upgrade: instalado virtualbox-ext-pack paquete post-installation guión el subproceso devolvió un error con esta

2018-12-01 Thread Francisco José Ruiz Toledo

Public bug reported:

virtualbox-ext-pack failed.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: virtualbox-ext-pack 5.2.18-1~ubuntu18.04.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Sat Dec  1 11:34:55 2018
ErrorMessage: instalado virtualbox-ext-pack paquete post-installation guión el 
subproceso devolvió un error con estado de salida 4
InstallationDate: Installed on 2018-10-07 (54 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: virtualbox-ext-pack
Title: package virtualbox-ext-pack 5.2.18-1~ubuntu18.04.1 failed to 
install/upgrade: instalado virtualbox-ext-pack paquete post-installation guión 
el subproceso devolvió un error con estado de salida 4
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: virtualbox-ext-pack (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806176

Title:
  package virtualbox-ext-pack 5.2.18-1~ubuntu18.04.1 failed to
  install/upgrade: instalado virtualbox-ext-pack paquete post-
  installation guión el subproceso devolvió un error con estado de
  salida 4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1806176/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802527] [NEW] package mysql-server-5.7 5.7.21-1ubuntu1 failed to install/upgrade: new mysql-server-5.7 package pre-installation script subprocess returned error exit status 1

2018-11-09 Thread Francisco Valverde

Public bug reported:

The MySQL system is not possible install or error in installation.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mysql-server-5.7 5.7.21-1ubuntu1
Uname: Linux 4.4.71-ELAR-Systems armv7l
ApportVersion: 2.20.9-0ubuntu7
Architecture: armhf
Date: Fri Nov  9 06:36:35 2018
ErrorMessage: new mysql-server-5.7 package pre-installation script subprocess 
returned error exit status 1
KernLog:
 [0.004426] Security Framework initialized
 [2.109287] SGI XFS with ACLs, security attributes, realtime, no debug 
enabled
 [   11.308486] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid)
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: ['ibdata1', 'debian-5.7.flag', 'ibtmp1', 'auto.cnf', 
'sys', 'phpmyadmin', 'ib_logfile0', 'ib_logfile1', 'performance_schema', 
'mysql', 'ib_buffer_pool']
ProcCmdline: earlyprintk console=tty1 root=/dev/mmcblk0p2 rw init=/sbin/init 
uboot_version=2017.07-g7d17b02-dirty
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.21-1ubuntu1 failed to install/upgrade: new 
mysql-server-5.7 package pre-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mysql-5.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package armhf bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802527

Title:
  package mysql-server-5.7 5.7.21-1ubuntu1 failed to install/upgrade:
  new mysql-server-5.7 package pre-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1802527/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802368] [NEW] instalacion no puede instalar el grub

2018-11-08 Thread Francisco Javier

Public bug reported:

intente instalar ubuntu 18.10 y no puede terminar la instalacion porque
no se instalo el grub

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity 18.10.12
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CasperVersion: 1.399
Date: Thu Nov  8 19:29:00 2018
InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz root=UUID=5C7D-F064 
file=/cdrom/preseed/ubuntu.seed maybe-ubiquity debian-installer/language=es 
keyboard-configuration/layoutcode=es 
iso-scan/filename=/ubuntu-18.10-desktop-amd64.iso boot=casper noprompt quiet 
splash --
LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic ubiquity-18.10.12 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802368

Title:
  instalacion no puede instalar el grub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1802368/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1801811] [NEW] package am-utils 6.2+rc20110530-3.2ubuntu2 failed to install/upgrade: instalado am-utils paquete post-installation guión el subproceso devolvió un error con estado de salida 1

2018-11-05 Thread Francisco

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: am-utils 6.2+rc20110530-3.2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 libtirpc1:amd64: Install
 rpcbind:amd64: Install
 libamu4:amd64: Install
 am-utils:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Nov  4 21:28:04 2018
ErrorMessage: instalado am-utils paquete post-installation guión el subproceso 
devolvió un error con estado de salida 1
InstallationDate: Installed on 2018-11-04 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: am-utils
Title: package am-utils 6.2+rc20110530-3.2ubuntu2 failed to install/upgrade: 
instalado am-utils paquete post-installation guión el subproceso devolvió un 
error con estado de salida 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: am-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801811

Title:
  package am-utils 6.2+rc20110530-3.2ubuntu2 failed to install/upgrade:
  instalado am-utils paquete post-installation guión el subproceso
  devolvió un error con estado de salida 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/am-utils/+bug/1801811/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1798418] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1798418/+attachment/5202375/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798418

Title:
  Liferea massive memory leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1798418/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1798418] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1798418/+attachment/5202374/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798418

Title:
  Liferea massive memory leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1798418/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1798418] Re: Liferea massive memory leak

apport information

** Tags added: apport-collected bionic third-party-packages

** Description changed:

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  apt-cache policy liferea
  liferea:
Installed: 1.12.2-1
Candidate: 1.12.2-1
Version table:
   *** 1.12.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  
  
  There is a massive memory leak in this particular version of liferea, which 
is fixed in the next upstream point release, 1.12.3:
  
  The issue report upstream:
  https://github.com/lwindolf/liferea/issues/633
  
  The commit that fixed it (only two small lines of code):
  
https://github.com/lwindolf/liferea/commit/b74f050a7f9870c18b7ef46bb4ce647b5ac4b9fa
  
  The full changelog for the next upstream point release:
  https://github.com/lwindolf/liferea/releases/tag/v1.12.3
  
  
  There are also other important issues that are fixed in 1.12.3 and subsequent 
versions.
  Is it possible to upgrade liferea's packages on Bionic to the most recent 
upstream version? Or at the very least a backport of the fix for the memory 
leak.
  
  As it is, Liferea's memory consumption starts climbing into the GiB's
  after a few days with a modest number of feeds. If not restarted, it
  could probably trigger an OOM error, and, before that point, it may
  cause severe performance degradation of the entire system due to
  eventually forcing the use of swap.
  
  Thanks.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.4
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-05-31 (139 days ago)
+ InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
+ Package: liferea 1.12.2-1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
+ Tags: third-party-packages bionic
+ Uname: Linux 4.15.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo 
ubridge vboxusers wireshark
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1798418/+attachment/5202373/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798418

Title:
  Liferea massive memory leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1798418/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1798418] [NEW] Liferea massive memory leak