[Bug 2059838] [NEW] installer crash on beta after grub install

[Donald Lillard]

Public bug reported:

24.04 beta installer crashed after setting up grub

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubiquity 24.04.2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.490
Date: Sat Mar 30 09:04:41 2024
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240204)
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble third-party-packages ubiquity-24.04.2 xubuntu

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

Title:
  installer crash on beta after grub install

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


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

[Bug 1973048] Re: White Date and Time on white background in Gnome Classic 42 notification area

[Donald]

** Changed in: gnome-shell-extensions (Ubuntu)
   Status: New => Confirmed

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

Title:
  White Date and Time on white background in Gnome Classic 42
  notification area

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


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

[Bug 1973048] [NEW] White Date and Time on white background in Gnome Classic 42 notification area

[Donald]

Public bug reported:

Description of problem:
White Date and Time on white background in Gnome Classic 42 notification area


Version-Release number of selected component (if applicable):
42

How reproducible:

Bug has been present on default config - download iso, install on
internal storage, install gnome-shell-extensions or gnome-classic-
session, and open clock in tray. There were no other interventions.


Actual results:
Image Bug 2 Wrong Behavior

https://gitlab.gnome.org/GNOME/gnome-shell-
extensions/uploads/e73160b7fba3ac889140344ed83d16b9/Bug2.PNG

Expected results:

Image Bug 3 Normal Behavior On Gnome 40

https://gitlab.gnome.org/GNOME/gnome-shell-
extensions/uploads/891e20650fb9e75c6b0dd17ddc9a5b6f/Bug3.png

Additional info:
Bug opened in gnome-shell-extensions gitlab.gnome.org #394.

** Affects: 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/1973048

Title:
  White Date and Time on white background in Gnome Classic 42
  notification area

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


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

[Bug 1944764] Re: APN command line : 'username' and 'user' are transposed

[Donald Mah]

The problem is that I was referring to the man pages for the embedded
Ubuntu version on my devices. I saw the incorrect info in multiple
places and lost a couple of days of online access until someone pointed
out the mistake with the man pages.  Just trying to help anyone else
with the same situation.

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

Title:
  APN command line : 'username' and 'user' are transposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1944764/+subscriptions


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

[Bug 1944764] Re: APN command line : 'username' and 'user' are transposed

[Donald Mah]

I see the last command line example at the following URL also shows
"username" and "user" are transposed:

   https://ubuntu.com/core/docs/networkmanager/configure-cellular-
connections

The page currently shows:

$ nmcli c add type gsm ifname  con-name  apn
 username  password  pin 


The page should show:

$ nmcli c add type gsm ifname  con-name  apn
 user  password  pin 

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

Title:
  APN command line : 'username' and 'user' are transposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1944764/+subscriptions


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

[Bug 1944764] [NEW] APN command line : 'username' and 'user' are transposed

[Donald Mah]

Public bug reported:

Pertains to the following man page's Connection Management Commands section :  
   https://manpages.ubuntu.com/manpages/xenial/man1/nmcli.1.html

Man page currently shows:

   type gsm [apn APN] [username user] [password passwd]

   apn
   APN - GSM Access Point Name.

   user
   user name.

   password
   password.

   type cdma [username user] [password passwd]

   user
   user name.

   password
   password.


The man page should be corrected to show:

   type gsm [apn APN] [user username] [password passwd]

   type cdma [user username] [password passwd]


I suggest correcting the man page so it's correct for people trying to
use this version of Ubuntu.

** Affects: network-manager (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/1944764

Title:
  APN command line : 'username' and 'user' are transposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1944764/+subscriptions


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

[Bug 1942681] [NEW] package grub-efi-amd64-signed 1.172+2.04-1ubuntu46 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status

[Donald]

Public bug reported:

Installed Ubuntu Impish Indri (development branch) onto my Thinkpad (X1
Extreme Gen 1) and I get this error every time my system tries to
install updates.

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: grub-efi-amd64-signed 1.172+2.04-1ubuntu46
ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
Uname: Linux 5.13.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu68
AptOrdering:
 grub-efi-amd64-signed:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Sep  2 19:38:58 2021
ErrorMessage: installed grub-efi-amd64-signed package post-installation script 
subprocess returned error exit status 32
Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt  2.3.7
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.172+2.04-1ubuntu46 failed to 
install/upgrade: installed grub-efi-amd64-signed package post-installation 
script subprocess returned error exit status 32
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package impish

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

Title:
  package grub-efi-amd64-signed 1.172+2.04-1ubuntu46 failed to
  install/upgrade: installed grub-efi-amd64-signed package post-
  installation script subprocess returned error exit status 32

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


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

[Bug 1941922] [NEW] Ubuntu dual-boot install from USB stick fails

[Donald]

Public bug reported:

Issue has happened multiple times when I try to install the latest
version of Ubuntu from my USB stick. OS boots off the stick and I go
through the install wizard. My Thinkpad has 2 hard drives, with the
primary running Win11 beta. I installed Ubuntu on a partition on my
secondary internal hard drive. The installation to my machine fails at
the executing grub-install step. Oddly, that errors out but then I get a
message saying installation is complete and to reboot my computer.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.19
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 27 15:42:28 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
RebootRequiredPkgs:
 linux-image-5.11.0-31-generic
 linux-base
 linux-image-5.11.0-16-generic
 linux-base
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute ubiquity-21.04.19 ubuntu

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

Title:
  Ubuntu dual-boot install from USB stick fails

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


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

[Bug 1925010] Re: shim-signed 15.4 does not boot on EFI 1.10 systems

[Donald]

^ Shot showing both failed Ubuntu recovery modes

-D.

** Attachment added: "ubuntu_recovery.jpeg"
   
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925010/+attachment/5508619/+files/ubuntu_recovery.jpeg

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

Title:
  shim-signed 15.4 does not boot on EFI 1.10 systems

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

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

[Bug 1925010] Re: shim-signed 15.4 does not boot on EFI 1.10 systems

[Donald]

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

Title:
  shim-signed 15.4 does not boot on EFI 1.10 systems

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

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

[Bug 1925010] Re: shim-signed 15.4 does not boot on EFI 1.10 systems

[Donald]

^ Here are some screenshots.

-D.

** Attachment added: "stuck_loading_ram_disk.jpeg"
   
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925010/+attachment/5508617/+files/stuck_loading_ram_disk.jpeg

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

Title:
  shim-signed 15.4 does not boot on EFI 1.10 systems

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

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

[Bug 1925010] Re: shim-signed 15.4 does not boot on EFI 1.10 systems

[Donald]

Hi Julian,

I tried booting Windows via grub and EFI, and Windows tries to repair
itself unsuccessfully.

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

Title:
  shim-signed 15.4 does not boot on EFI 1.10 systems

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

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

[Bug 1925010] Re: shim-signed 15.4 does not boot on EFI 1.10 systems

[Donald]

Hi -

I believe I'm experiencing this issue on my Thinkpad X1 Extreme (Gen1).
I set up a dual-boot, Ubuntu (Groovy) and Win11 beta. I'd be able to
select my OS in a Grub2 menu, after the Lenovo splash screen on start
up.

When I was navigating Ubuntu today, I was notified of the available
upgrade to 21.04 and went through the steps to upgrade.

At the end of the steps, I needed to reboot my machine:
1) Lenovo splash screen
2) Grub2 menu
3) Select Ubuntu
4) Screen goes black and is unresponsive
5) Hold power to shutdown/restart

After noticing the issue with booting into Ubuntu, I tried to boot into
Windows and experienced the same issue - black, unresponsive screen.

I tried several times to boot Ubuntu in recovery mode via advanced
options and no dice.

This is a really crummy issue that's rendered my laptop unusable.

-D.

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

Title:
  shim-signed 15.4 does not boot on EFI 1.10 systems

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

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

[Bug 1931783] [NEW] not sure

[Donald Crosiar]

Public bug reported:

stalled while installing

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-lowlatency 5.3.1
Uname: Linux 5.3.0-18-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CasperVersion: 1.427
Date: Sat Jun 12 18:23:39 2021
InstallCmdLine: file=/cdrom/preseed/ubuntustudio.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
LiveMediaBuild: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan third-party-packages ubiquity-19.10.21 
ubuntustudio

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

Title:
  not sure

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

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

[Bug 1931784] [NEW] not sure

[Donald Crosiar]

Public bug reported:

stalled while installing

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-lowlatency 5.3.1
Uname: Linux 5.3.0-18-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CasperVersion: 1.427
Date: Sat Jun 12 18:23:39 2021
InstallCmdLine: file=/cdrom/preseed/ubuntustudio.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
LiveMediaBuild: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan third-party-packages ubiquity-19.10.21 
ubuntustudio

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

Title:
  not sure

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

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

[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Donald Babcock]

I am seeing this on 18.04 Linux 5.3.0-1020-azure VM. Sister VM on same
kernel, same patch level, same host does not see the issue.

I isolated it to a Hyper-V integration service difference between the
issue vm and it's non-affect sibling. The issue reliably appears and
goes away if "data exchange services" under "integration services" are
disabled or re-enabled on the VM. Data Exchange disabled produces the
issue.

Clue was found here https://askubuntu.com/questions/996171/hv-kvp-
daemon-fails-in-ubuntu-16-04-on-hyper-v

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

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

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

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

Re: [Bug 1874901] Re: package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade: installed dms-core package post-installation script subprocess returned error exit status 3

[Donald Wilde]

Understood. Better to be safe than sorry. Thanks, Eduardo.

On 4/29/20, Eduardo Barretto <1874...@bugs.launchpad.net> wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. We appreciate the difficulties you are facing, but this appears
> to be a "regular" (non-security) bug.  I have unmarked it as a security
> issue since this bug does not show evidence of allowing attackers to
> cross privilege boundaries nor directly cause loss of data/privacy.
> Please feel free to report any other bugs you may find.
>
> ** Attachment removed: "Resume_DSW_2020-April.docx"
>
> https://bugs.launchpad.net/ubuntu/+source/dms/+bug/1874901/+attachment/5359825/+files/Resume_DSW_2020-April.docx
>
> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1874901
>
> Title:
>   package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade: installed
>   dms-core package post-installation script subprocess returned error
>   exit status 3
>
> Status in dms package in Ubuntu:
>   New
>
> Bug description:
>   I have gotten a number of these from 20.04 post-release while I was
>   attempting to re-install packages (that worked in 18.04.4) from a list
>   through a Ruby script.
>
>   If I try to manually install any one of the dms* packages it fails.
>   Removing works, but as soon as I re-install it dies again.
>
>   I was able to get apport working again by clearing /var/crash. I am
>   going to put a tail on syslog to see it happening live.
>
>   This is Bind9, so that is why I am reporting it also to Security team.
>
>   I am also getting 'audit' failures that come from AppArmor. I believe
>   these revolve around the snapd subsystem. They occurred in 18.04.4,
>   which was why I was eager to try an update.
>
>   Thanks in advance. I'll be glad to try a patch.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 20.04
>   Package: dms-core 1.0.8.1-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   Date: Fri Apr 24 11:20:51 2020
>   ErrorMessage: installed dms-core package post-installation script
> subprocess returned error exit status 3
>   InstallationDate: Installed on 2020-04-24 (0 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   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.2
>   SourcePackage: dms
>   Title: package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade:
> installed dms-core package post-installation script subprocess returned
> error exit status 3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dms/+bug/1874901/+subscriptions
>


-- 
Don Wilde

* What is the Internet of Things but a system *
* of systems including humans? *


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

Title:
  package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade: installed
  dms-core package post-installation script subprocess returned error
  exit status 3

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

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

[Bug 1874066] Re: Cannot install on non-RST drive if RST is enabled and there is a second RST-enabled drive

[Donald Smouse]

I also have an RST problem on my HP-laptop, I followed the instructions and 
went into my BIOS and my RST is in fact turned off. I canot get to the 
partition screen due to it saying that RST is turned on which it is not. here 
are my system specs:
https://support.hp.com/us-en/product/hp-15-da-laptop-pc/20395828/model/22185619/document/c06057186

I have upgraded the memory and put in a 500gb evo ssd drive, I do not
want to have to re-open this machine and take out the RST just to
install this OS.

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

Title:
  Cannot install on non-RST drive if RST is enabled and there is a
  second RST-enabled drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1874066/+subscriptions

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

[Bug 1861890] Re: package initramfs-tools 0.133ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Donald L Walters]

Problem resolved 4 Feb, 2020, DLW/w9dki

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

Title:
  package initramfs-tools 0.133ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861890/+subscriptions

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

[Bug 1861890] [NEW] package initramfs-tools 0.133ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Donald L Walters]

Public bug reported:

ubuntu 20.04LTS beta, main server install error using sudo apt update on
initramfs-tools

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.133ubuntu13
ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16
Uname: Linux 5.4.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Tue Feb  4 10:05:01 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-01-13 (21 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.1, python3-minimal, 3.8.0-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.8
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.133ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal package-from-proposed

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

Title:
  package initramfs-tools 0.133ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861890/+subscriptions

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

[Bug 1376380] Re: lxsession risks filling disk with improper log handling

[Donald]

Same here.

root@raspberrypi:/home/pi/.cache/lxsession/LXDE-pi# tail -f run.log

** (pcmanfm:672): WARNING **: 14:23:20.696: got unmount for unknown
desktop item

** (pcmanfm:672): WARNING **: 14:23:20.696: got unmount for unknown
desktop item

** (pcmanfm:672): WARNING **: 14:23:20.696: got unmount for unknown
desktop item

** (pcmanfm:672): WARNING **: 14:23:20.696: got unmount for unknown
desktop item


In my case the funny thing is that although the root FS seems ext4 I keep 
getting

write(2, "\n** (pcmanfm:672): WARNING **: 2"..., 82) = -1 EFBIG ...

when looking at the strace output of the pcmanfm process. Any new on how
to avoid this?

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

Title:
  lxsession risks filling disk with improper log handling

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

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

[Bug 1066480] Re: Installer doesn't show encrypted partitions

[Donald Burt]

** Changed in: ubiquity (Ubuntu)
 Assignee: (unassigned) => Donald Burt (doneburt)

** Changed in: ubuntu-release-notes
 Assignee: Andy Whitcroft (apw) => Donald Burt (doneburt)

** Changed in: ubuntu-release-notes/quantal
 Assignee: (unassigned) => Donald Burt (doneburt)

** Changed in: ubiquity (Ubuntu Quantal)
 Assignee: (unassigned) => Donald Burt (doneburt)

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

Title:
  Installer doesn't show encrypted partitions

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

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

[Bug 1844080] Re: Tilix crashes on start up after updating system today

[Donald Wray]

I could really use some help with this.  I'm not sure whats going on.
After i updated i try to run tilix in cli and i get this error.

tilix: symbol lookup error: tilix: undefined symbol:
_D4glib1c5types__T6ScopedTC3gio22ApplicationCommandLineQyZQBo6__dtorMFZv

even when i click my favorites shortcut for the app it shows up really
quick and then closes.  its weird.  I would be great full for any help.

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

Title:
  Tilix crashes on start up after updating system today

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

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

[Bug 1844080] [NEW] Tilix crashes on start up after updating system today

[Donald Wray]

Public bug reported:

Description:Kali GNU/Linux Rolling
Release:2019.4

When I try to load up Tilix it shows for a sec then quits.  started
today after i did my daily updates.  I know this has happened in the
past.  I just can't remember how to fix it or if the software needs to
be updated.

Thanks!

** Affects: tilix (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/1844080

Title:
  Tilix crashes on start up after updating system today

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

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

[Bug 1839013] [NEW] 'grub-install /dev/sda' failed

[Donald A. Syvanen]

Public bug reported:

I don't have any ideas now.  My 1 Tb must be too full.  I deleted old
directories from the EFI directory, so the active ones are Win10 and
Fedora.  I'll try 'grub-install /dev/sda' from a shell and look for more
information.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
Date: Mon Aug  5 11:27:19 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu

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

Title:
  'grub-install /dev/sda' failed

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

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

[Bug 1839005] [NEW] cannot install efi grub to boot.

[Donald A. Syvanen]

Public bug reported:

My efi boot directory probably is too full.  I will boot live Ubuntu,
cleanup my efi directory and try again.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  5 10:07:46 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu

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

Title:
  cannot install efi grub to boot.

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

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

[Bug 1697958] Re: HPLIP cannot detect printers in your network

[Donald T Campbell]

Oh, and what exactly is a "systemtray?" All of a sudden, for the past
year or so, the HP p1102w Pro has been eliciting an HPLIP error message
saying that there is no "systemtray" and so it was stopping. I have no
idea what a systemtray is. I obviously didn't lose a systemtray that was
once there--all is like new in my old printer. Windows' driver makes no
complaint about a systemtray but HPLIP in Linux is obsessed by it and
the danger caused by it being missing. I don't want to be forced to go
into Windows in order to print something. I have used Linux since 1997
and I don't want to have Linux suddenly fail to support my perfectly
fine older HP printer that has been working fine under Linux for years.

Because I'm annoyed at how much effort I've put into making this
perfectly fine printer work with the latest versions of Linux and HPLIP
I've considered buying another inexpensive printer but I'm not sure how
well that will work out in Linux.

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

Title:
  HPLIP cannot detect printers in your network

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

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

[Bug 1697958] Re: HPLIP cannot detect printers in your network

[Donald T Campbell]

For the first time in about 10 or 12 versions of Fedora, I cannot simply
install my HP p1102w Laserjet Pro printer using HPLIP.

For the first several hours I kept getting:

 "HPLIP cannot detect printers in your network. This may be due to existing 
firewall settings blocking the required ports. When you are in a trusted 
network environment, you may open the ports for network services like mdns and 
slp in the firewall. For detailed steps follow the link.
 http://hplipopensource.com/node/375  "

Nope. Turning off firewall didn't help. Ping showed printer ip alive.
Windows on a dual boot laptop worked immediately with the printer in the
same network. Windows in a VirtualBox VM running under Linux worked
immediately. Multiple machinations failed and eventually the network
failed entirely on the printer and I did a full reset. Reset turned
networking back on, DHCP from the router gave the printer the fixed IP
and Windows could again print to the printer.

Trying earlier versions of HPLIP (since earlier versions worked fine on
all 4 Fedora machines we have in the house) failed due to dependency
issues. Went back to HPLIP installed from repo. Failed. Found advice to
get HPLIP-3.19.6.run and use it to manually make the HPLIP files. Did
that.

That got me to the place where it stated that I needed a plugin and
could install it from HP via the network. I agreed. Plugin installed
successfully. So, that means the printer was found? but then when it
said I could install the printer from there--I got the ""HPLIP cannot
detect printers in your network." Switched to mDNS. No joy.

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

Title:
  HPLIP cannot detect printers in your network

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

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

[Bug 1017706] Re: [wishlist] ClamTk antivirus functionality within PCManFM

[donald george]

Hii i am doanldgeorge and i am a senior technician in Quickbooks .If you
face any technical issues in quickbooks then must dial https://www.quickbookssupportphonenumber247.co/;>Quickbooks
Support Phone Number  to get an instant solutions.

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

Title:
  [wishlist] ClamTk antivirus functionality within PCManFM

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

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

[Bug 1825188] [NEW] Just upgraded to ubunt 18 and now ulimit -n changes hard and soft limits

[Donald Jones]

Public bug reported:

I recently upgraded from Ubuntu 14 to 18 and now I can't use ulimit -n
to increase the allowed number of files open! This is a change from my
previous version of Ubuntu.

Lines from /etc/security/limits.conf
jonesdc  hardnofile  10
jonesdc  softnofile  1

Setting in /etc/sysctl.conf
# Max open files (system limit)
fs.file-max = 10

When I first open a terminal if I type 
$ulimit -n 1000
then
$ulimit -a 
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) 1
pending signals (-i) 30927
max locked memory   (kbytes, -l) 16384
max memory size (kbytes, -m) unlimited
open files  (-n) 1000
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 30927
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Now if I type
$ulimit -n 999
and then try again
$ulimit -n 1000
bash: ulimit: open files: cannot modify limit: Operation not permitted

Looking further, it appears that ulimit -n changes both the hard and soft limits
$ulimit -H -a
core file size  (blocks, -c) unlimited
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 30927
max locked memory   (kbytes, -l) 16384
max memory size (kbytes, -m) unlimited
open files  (-n) 999
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) unlimited
cpu time   (seconds, -t) unlimited
max user processes  (-u) 30927
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

** Affects: lightdm (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/1825188

Title:
  Just upgraded to ubunt 18 and now ulimit -n changes hard and soft
  limits

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

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

[Bug 1823110] Re: Screen not resized when rotating 90*

[Donald Wyman]

I can confirm having the same issues on my thinkpad x230 tablet.  When
trying to set the screen to portrait mode the image only takes up half
of the screen instead of resizing and for me my touch inputs and stylus
inputs do not sync with the images.  I also confirmed this as well on my
desktop monitor (with the exception of the input part as it is not a
touch monitor.)

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

Title:
  Screen not resized when rotating 90*

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

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

[Bug 1816896] Re: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

[Donald Gordon]

So this happened essentially from when I upgraded to 18.10 a few months
ago; now, after I file the bug, it's stopped happening.  I suspect a
recent software update.  Woohoo!

(sorry for any trouble caused)

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

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

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

[Bug 1816896] Re: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

[Donald Gordon]

apport information

** Tags added: apport-collected

** Description changed:

  This problem is new in Ubuntu 18.10; it did not occur with 18.04.
  
  When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics,
  comes out of resume, often the UI is unresponsive.  Typically I get a
  black screen, a screen with just the GNOME top bar, or what the screen
  was showing before the laptop was suspended.  The mouse cursor moves but
  the UI is unresponsive to input.
  
  If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my
  password and after that my GUI session begins to work again, where I
  left off.
  
  The problem appears to increase in frequency when I add external
  monitors.
  
  It occurs on every suspend/resume if one or more external monitors
  (DisplayPort or VGA) have been used since the laptop was booted, even if
  they were present at boot, or subsequently removed.
  
- If an extra monitor was plugged in while the laptop was turned off
- (scenario: come home, put laptop in docking station with extra monitor
- attached, turn on) then often the UI will still fail to respond after
- switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot
- the laptop.
+ If an extra monitor was plugged in while the laptop was turned off (scenario: 
come home, put laptop in docking station with extra monitor attached, turn on) 
then often the UI will still fail to respond after switching to the lock screen 
with Ctrl+Alt+F1 and I will need to reboot the laptop.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-08-13 (191 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ Package: gnome-shell
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
+ Tags:  cosmic
+ Uname: Linux 4.18.0-15-generic x86_64
+ UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1816896/+attachment/5240524/+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/1816896

Title:
  Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

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

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

[Bug 1816896] modified.conffile..etc.gdm3.custom.conf.txt

[Donald Gordon]

apport information

** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
   
https://bugs.launchpad.net/bugs/1816896/+attachment/5240527/+files/modified.conffile..etc.gdm3.custom.conf.txt

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

Title:
  Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

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

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

[Bug 1816896] ProcCpuinfoMinimal.txt

[Donald Gordon]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1816896/+attachment/5240525/+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/1816896

Title:
  Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

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

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

[Bug 1816896] ProcEnviron.txt

[Donald Gordon]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1816896/+attachment/5240526/+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/1816896

Title:
  Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

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

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

[Bug 1816896] Re: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

[Donald Gordon]

** Package changed: gnome-control-center (Ubuntu) => xorg-server
(Ubuntu)

** Package changed: xorg-server (Ubuntu) => gdm3 (Ubuntu)

** Also affects: xorg-server (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/1816896

Title:
  Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

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

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

[Bug 1816896] [NEW] Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

[Donald Gordon]

Public bug reported:

This problem is new in Ubuntu 18.10; it did not occur with 18.04.

When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics,
comes out of resume, often the UI is unresponsive.  Typically I get a
black screen, a screen with just the GNOME top bar, or what the screen
was showing before the laptop was suspended.  The mouse cursor moves but
the UI is unresponsive to input.

If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my
password and after that my GUI session begins to work again, where I
left off.

The problem appears to increase in frequency when I add external
monitors.

It occurs on every suspend/resume if one or more external monitors
(DisplayPort or VGA) have been used since the laptop was booted, even if
they were present at boot, or subsequently removed.

If an extra monitor was plugged in while the laptop was turned off
(scenario: come home, put laptop in docking station with extra monitor
attached, turn on) then often the UI will still fail to respond after
switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot
the laptop.

** Affects: gnome-control-center (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/1816896

Title:
  Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816896/+subscriptions

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

[Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc

[Donald E. Lund via ubuntu-bugs]

I would like to see this implemented too.

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

Title:
  Add support for top bars on all monitors to allow for multi-monitor
  support in primary extensions - apps-menu, places-menu, topbar, etc

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

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

[Bug 1745256] Re: bcmwl: module cannot be inserted on Bionic: unknown symbol

[James Donald]

I get the same error on loading 'wl' (and the exact same 19 unknown
symbols in dmesg) from installing bcmwl-kernel-source on Xenial.

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

Title:
  bcmwl: module cannot be inserted on Bionic: unknown symbol

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

>From what I can tell the maintainers have no intention of spending time
supporting Ubuntu 16.04 or older. Even when Xenial was the current LTS
they weren't responding here, and now that 18.04 has been out for 5
month there's even less motivation to handle older distros.

Having built Firefox 59 from source I think I get some of the reasons
why they'd consider this a heavy support task. It's hard to get gcc and
Rust to play nice on old cross-compiling toolchains, not to mention that
sketchy assembly code for XPCOM. From a practical perspective, user
workarounds can go in this order:

1) Use the latest firefox:armhf on 18.04 Bionic, if that's what you're
running or you're open to upgrading.

2) Earlier distros like 16.04 or Debian Stretch: Install the latest
firefox:arm64 if your system supports AArch64.

3) If armhf is the only option and you're on 16.04, you can still set up
the firefox 18.04 deb package from Launchpad. Download its dependencies
like libstdc++ and following my instructions in #117 to place the
appropriate runtime-linked libraries.

Relying on armhf builds from Bionic in the worst case 3): this avoids
having someone to maintain the whole build flow for Xenial and Trusty.

I'm only speaking for Firefox here, but if it all comes down to crashes
in libxul.so then maybe much of this is sufficient for Thunderbird too.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1802617] Re: After upgrade to 18.10 boot fails on waiting for encrypted source device

[Donald Pellegrino]

Candidate Work-around:

For the case of disabling swap, I was able to eliminate the boot-time
error with the following actions:

Remove swap line from /etc/fstab
Remove swap line from /etc/crypttab
Remove /swapfile
apt purge cryptsetup
apt autoremove (clean up cryptsetup dependencies)

The updates to /etc/fstab and /etc/crypttab were not enough to eliminate
the error message at boot. It seems cryptsetup was still doing something
in the boot sequence that caused it to try and create an encrypted swap
file. Purging the cryptsetup package was necessary to eliminate the
error message. Therefore, this issue may be relevant to both the Ubuntu
upgrade process and the cryptsetup package.

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

Title:
  After upgrade to 18.10 boot fails on waiting for encrypted source
  device

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

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

[Bug 1802617] Re: After upgrade to 18.10 boot fails on waiting for encrypted source device

[Donald Pellegrino]

A post on Ask Ubuntu seems relevant:
https://askubuntu.com/questions/1087828/cant-unlock-cryptswap1

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

Title:
  After upgrade to 18.10 boot fails on waiting for encrypted source
  device

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

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

[Bug 1802617] Re: After upgrade to 18.10 boot fails on waiting for encrypted source device

[Donald Pellegrino]

** Attachment added: "initramfs messages"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1802617/+attachment/5211025/+files/IMG_20181109_200714470.jpg

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

Title:
  After upgrade to 18.10 boot fails on waiting for encrypted source
  device

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

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

[Bug 1802617] [NEW] After upgrade to 18.10 boot fails on waiting for encrypted source device

[Donald Pellegrino]

Public bug reported:

After upgrading from 18.04.1 LTS to 18.10, all reboots of the system
give a boot screen with the error:

"cryptsetup: Waiting for encrypted source device /swapfile..."

After a minute or so, the graphical boot screen with that message is
replaced with a console screen reading:

"ALERT! encrypted source device /swapfile does not exist, can't unlock 
cryptswap1.
Check cryptopts=source= bootarg: cat /proc/cmdline
or missing modules, devices: cat /proc/modules; ls /dev

Dropping to a shell

BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) _"

Typing exit at the initramfs prompt gets the boot to continue. The boot
continues to a working system and graphical login.

The system was configured in 18.04.1 LTS to have encrypted home
directories and no swap file.

It looks like the /etc/fstab got a new swapfile line somewhere during
the upgrade process. However, commenting that out and rebooting does not
affect this issue.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-release-upgrader-core 1:18.10.11.1
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
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Fri Nov  9 20:22:09 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-12 (454 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to cosmic on 2018-11-09 (0 days ago)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug cosmic dist-upgrade wayland-session

** Attachment added: "Graphical boot error message"
   
https://bugs.launchpad.net/bugs/1802617/+attachment/5211016/+files/IMG_20181109_200409085.jpg

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

Title:
  After upgrade to 18.10 boot fails on waiting for encrypted source
  device

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

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

[Bug 1798888] Re: Displays shows only one display

[Donald Gordon]

OK so I've just found out where my extra displays were hiding.  The
Button that says 3 Viewsonic Corp ... can be clicked on to choose
another monitor.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Opinion

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

Title:
  Displays shows only one display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/179/+subscriptions

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

[Bug 1798888] Re: Displays shows only one display

[Donald Gordon]

Which is to say this is more of a usability issue than a "this
functionality is unavailable."

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

Title:
  Displays shows only one display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/179/+subscriptions

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

[Bug 1798888] [NEW] Displays shows only one display

[Donald Gordon]

Public bug reported:

Upon upgrading from 18.04 to 18.10, only one of my displays is working.

Only one display shows in control centre.  I have two, one connected via
DisplayPort, one via VGA.

The VGA works, DP doesn't.

If I unplug the VGA display, then the DisplayPort display turns on.
Plug it back in, the DisplayPort display turns off.

XRANDR shows both displays.  Confusingly, the VGA display appears as
"DP-2" in XRANDR, and the DisplayPort connected display shows as
"HDMI-1."

If I manually enable the second display with

xrandr --output HDMI-1 --right-of DP-2 --mode 1920x1080

then the second display starts to work, and it appears in the Displays
section of the control centre, as it used to in Ubuntu 18.04.

Here's the output of xrandr prior to manually enabling the second
display:

donald@silver:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS-1 connected (normal left inverted right x axis y axis)
   1600x900  60.06 +  59.9959.9459.9559.8240.04  
   1440x900  59.89  
   1400x900  59.9659.88  
   1440x810  60.0059.97  
   1368x768  59.8859.85  
   1360x768  59.8059.96  
   1280x800  59.9959.9759.8159.91  
   1152x864  60.00  
   1280x720  60.0059.9959.8659.74  
   1024x768  60.0460.00  
   960x720   60.00  
   928x696   60.05  
   896x672   60.01  
   1024x576  59.9559.9659.9059.82  
   960x600   59.9360.00  
   960x540   59.9659.9959.6359.82  
   800x600   60.0060.3256.25  
   840x525   60.0159.88  
   864x486   59.9259.57  
   800x512   60.17  
   700x525   59.98  
   800x450   59.9559.82  
   640x512   60.02  
   720x450   59.89  
   700x450   59.9659.88  
   640x480   60.0059.94  
   720x405   59.5158.99  
   684x384   59.8859.85  
   680x384   59.8059.96  
   640x400   59.8859.98  
   576x432   60.06  
   640x360   59.8659.8359.8459.32  
   512x384   60.00  
   512x288   60.0059.92  
   480x270   59.6359.82  
   400x300   60.3256.34  
   432x243   59.9259.57  
   320x240   60.05  
   360x202   59.5159.13  
   320x180   59.8459.32  
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected (normal left inverted right x axis y axis)
   1920x1080 60.00 +
   1600x1200 60.00  
   1680x1050 59.88  
   1280x1024 75.0260.02  
   1440x900  59.90  
   1280x960  60.00  
   1280x800  74.9359.91  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.3256.25  
   640x480   75.0072.8166.6759.94  
   720x400   70.08  
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
HDMI-3 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 
521mm x 293mm
   1920x1080 60.00*+
   1600x1200 60.00  
   1680x1050 59.95  
   1280x1024 75.0260.02  
   1440x900  59.89  
   1280x960  60.00  
   1280x800  74.9359.81  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.3256.25  
   640x480   75.0072.8166.6759.94  
   720x400   70.08  
DP-3 disconnected (normal left inverted right x axis y axis)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-control-center 1:3.30.1-1ubuntu2
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
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 20 08:10:51 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-08-13 (67 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=en_NZ:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic 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/179

Title:
  Displays shows only one display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/179/+subscriptions

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

[Bug 1704890] Re: Kea 1.2 has been out for awhile

[Donald]

I would also appreciate if you included kea-admin in version 1.1 (ubuntu
18.04) and upgrade the entire package to a newer version.

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

Title:
  Kea 1.2 has been out for awhile

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-kea/+bug/1704890/+subscriptions

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

[Bug 1787191] Re: Crash due to BUG: Bad page map in process X & BUG: Bad rss-counter state X

[Donald Babcock]

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

I have 4 similar trusty virtual machines 3.13.0-155 running on the same
hyper-v 12r2 host on intel e5s.

Three of the four were rebooted after the 155 kernel without issue (so
far). The four were built from the same base install, however they have
diverged in config for the last ~4 years.

One is exhibiting the described behavior in the op, after reboot
followed by bad maps for various things running (clamd, apache, mysql,
etc). Roll back to disk checkpoint before the reboot (3.13.0-153 running
state) returns the machine to an operational state.

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

Title:
  Crash due to BUG: Bad page map in process X & BUG: Bad rss-counter
  state X

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

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

[Bug 1776704] Re: since update laptop won't shut down and VLC won't launch

[Donald Soper]

I mneant tried to uninstall VLC

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

Title:
  since update laptop won't shut down and VLC won't launch

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

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

[Bug 1776704] [NEW] since update laptop won't shut down and VLC won't launch

[Donald Soper]

Public bug reported:

Hello
Since update on 11/6/2018 system 
won't shut down and VLC media player wont launch ,tried to uninstall and reload 
but won't let me 

hope  you can help

Don

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.25
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Wed Jun 13 17:05:46 2018
InstallationDate: Installed on 2018-02-28 (105 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  since update laptop won't shut down and VLC won't launch

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

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

[Bug 1430042] Re: Virtual Machine could not be evacuated because virtual interface creation failed

[Donald]

** Changed in: Ubuntu Trusty
   Status: Triaged => New

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

Title:
  Virtual Machine could not be evacuated because virtual interface
  creation failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1430042/+subscriptions

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

[Bug 988801] Re: Unable to install mysql-server, apt-get stuck at "Setting up".

[Donald]

In my case, apparmor isn't even installed, so it can't be removed.
Still,

  Setting up mysql-server-5.5 (5.5.60-0+deb8u1) ...

is hanging...

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

Title:
  Unable to install mysql-server, apt-get stuck at "Setting up".

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

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

[Bug 1756511] Re: Xorg freezes on bionic kernel 4.15.0-12

[Donald Pedersen]

I should say it's with the current kernel as of this date.  I can't go
check because I've gone back to Xenial for now.

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

Title:
  Xorg freezes on bionic kernel 4.15.0-12

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

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

[Bug 1756511] Re: Xorg freezes on bionic kernel 4.15.0-12

[Donald Pedersen]

This happens to me too.  Bionic freezes on the splash screen.  I can get
in via recovery mode but that's it.  Also this guy on Ask Ubuntu has a
similar Xorg.0.log where at the end the power button, keyboard, and
mouse get removed.

https://askubuntu.com/questions/1029384/can-not-start-xorg-after-
upgrade-ubuntu-to-18-04

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

Title:
  Xorg freezes on bionic kernel 4.15.0-12

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Lars, I went to sites like Gmail or Youtube that I thought had a chance
of using optional NaCl, but I haven't been able to reproduce those error
messages. I don't think Firefox supports NaCl, even with a plugin. Is it
possible you imported browser settings from Chromium and it happened to
include their NaCl extension? You could rule this out by moving or
deleting ~/.mozilla/firefox then trying again.

herrtimson, an illegal instruction would indicate your system lacks NEON
or ARMv7 altogether, the same reason Firefox does not run on ARMv6
boards like Raspberry Pi B+ or Pi Zero. To check, cat /proc/cpuinfo

There's also a chance that ungültiger maschienenbefehl means bad
interpreter or not in executable format / File format not recognized.
You can troubleshoot this with the ldd and file commands. Compare
properties of /usr/lib/firefox/firefox to any working command under
/usr/bin

> Oh, and how do I revert this to the ubuntu one? *_*

sudo apt-get purge firefox
sudo apt-get install firefox

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

@herrtimson I looked in the tarball and don't even see mention of my use
of clang in mozconfig.

Note I'm using a procedure similar to what Chituc outlined. If I kick
off dpkg-buildpackage, interrupt it, then edit the generated backend.mk
I would not expect that to appear in patch files. It's also possible
that due to use of the -b flag it skips version control comparisons, so
the C++ source diffs are not appearing either.

For now I have documented pieces manually in this repo:
https://github.com/jdonald/firefox-armhf

I'll update that repo as more steps come to mind.
firefox_59.0.2.build1-0ubuntu0.14.04.4.debian.tar.xz is available for
download there in the releases tab if you'd like to take a look through
it.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

@herrtimson

Here's a 14.04 Trusty build:
https://www.dropbox.com/s/977vzb3mu8bf34z/firefox_59.0.2%2Bbuild1-0ubuntu0.14.04.4_armhf.deb?dl=0

I used the same approach with clang + gcc headers inside a Trusty
(gcc-4.8) container. Initially I got errors about ::gets() and Stack
Overflow sent me down some rabbit holes of attempting to use gcc-4.9
headers or libc++ armhf. Ultimately the workaround was to comment out
the offending line in gcc headers, and also fix a constexpr bug in the
 header. These kinds of hacks are something one can be more
comfortable doing inside a Docker container.

I don't have a 14.04 armhf setup but I did test this on Raspbian
Stretch. Would be great if you could try it out on your system. Note
initially it used up all my Pi's RAM so I had to add 1 GB of swap.

For others, here is a 16.04 Xenial build:
https://www.dropbox.com/s/ogdut56m2i0k0t9/firefox_59.0.2%2Bbuild1-0ubuntu0.16.04.3_armhf.deb?dl=0

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1767073] [NEW] Bionic Beaver 18.04 Ubuntu-Desktop amd64 Installer Freeze

[Donald Tanner]

Public bug reported:

While performing testcase: "Install (manual partitioning) in Ubuntu Desktop 
amd64 in Bionic Daily"
the installer Freezes when clicking the "Install Now" button which is step #8 
of this testcase.

Test Machine:

iMac (Retina 5K, 27-inch, Late 2015)
Model Number A1419
CPU: 8 x Intel Core i7-6700K @ 4.00 GHz
SSD 1TB
Memory: 24G
Graphics: Radeon M395X
Intel Sunrise Point-H HD Audio

...
Link to Screenshots:
https://bionicmac.club/index.php/s/kIVdjxRYOauMFYq
...

This happened 3 times in a row to verify.

I made sure the iso was not corrupt, re-flashed the usb key and it
continues to be an issue.

Exactly after I click "Install Now" button the ubiquity gui goes corrupt as if 
it
is a graphics issue but the rest of the desktop looks fine. It is only the 
ubiquity
gui window that gets the rainbow/static video garbled.

That garbled ubiquity wondow only stays for 10-15 seconds then goes
away. Then the screens in the link above come up confirming an issue.

This leaves me unable to complete the installation.

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


** Tags: iso-testing

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

Title:
  Bionic Beaver 18.04 Ubuntu-Desktop amd64 Installer Freeze

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

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

Re: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from

[Donald L Walters]

fb 
I will try todo it in gcc / inline machine language if you can’t find the 
problem if you like

de w9dki / w9gty 40

Sent from my iPhoneX+(beta)


> On Apr 3, 2018, at 00:29, Thomas <1748...@bugs.launchpad.net> wrote:
> 
> Xorg
> 
> 
> 
> Van: boun...@canonical.com  namens Daniel van Vugt 
> 
> Verzonden: dinsdag 3 april 2018 3:52
> Aan: tomlemmen...@hotmail.com
> Onderwerp: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in 
> _g_log_abort() from g_log_default_handler() from 
> default_log_handler(message="Connection to xwayland lost") from g_logv() from 
> g_log() from 
> 
> This bug is indeed meant to be wayland only. Which duplicates are from
> Xorg?
> 
> Note that the login screen (gdm3) is using wayland by default. So your
> system may report this crash even if you only use Xorg sessions.
> 
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1759788).
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> 

Re: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from

[Donald L Walters]

fb thx try to fix it...if possible  using cinnamon now and had to shift to a 
macbook pro with homebrew and xcode. slmist a debian (from my dson Derek 
Walters the IphoneX chief engineering team leader
guess who gets the Msc OS “beta” version of new software patches for testing 
...me 藍

btu de w9dki 40

Sent from my iPhoneX+(beta)

> On Apr 2, 2018, at 23:54, Daniel van Vugt  
> wrote:
> 
> Yeah and that's actually good news.
> 
> I had feared the switch to Xorg by default would mean this bug wouldn't
> happen often enough for us to collect good data in 18.04 (since the
> related apport bug fix last week). But it turns out this will happen
> plenty often enough still.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

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

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

Re: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from

[Donald L Walters]

fb keep at it
btu de w9dki / w9gty 40

Sent from my iPhoneX+(beta)

> On Apr 2, 2018, at 23:54, Daniel van Vugt  
> wrote:
> 
> Yeah and that's actually good news.
> 
> I had feared the switch to Xorg by default would mean this bug wouldn't
> happen often enough for us to collect good data in 18.04 (since the
> related apport bug fix last week). But it turns out this will happen
> plenty often enough still.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

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

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

Re: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from

[Donald L Walters]

fb thx 73 bk
de w9dki 40

Sent from my iPhone

> On Apr 2, 2018, at 23:22, Jean-Baptiste Lallement 
>  wrote:
> 
> I checked tens of duplicates and all the crashes happen from the login
> screen (XDG_CURRENT_DESKTOP=GNOME-Greeter:GNOME)
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

@herrtimson from my tests that patch does not resolve the strd r2, r3,
[r1] crash on Xenial. However, I do believe it's entirely possible that
it indirectly fixed the issue with your gcc-7 toolchain. I'm starting to
wonder if this crash does not have a single cause but rather is a
codepath that Firefox goes down if there is one of many possible
failures in startup.

In addition to the Bionic build above, this weekend I got a Raspbian
Stretch build working:
https://www.dropbox.com/s/sdqwuda5eaw0cks/firefox_59.0.2%2Bbuild1
-stretch-rpi2_armhf.deb?dl=0 with some overview on the forums:
https://www.raspberrypi.org/forums/viewtopic.php?f=63=150438

I used Bionic sources (deb-src http://ports.ubuntu.com/ubuntu-ports/
bionic main restricted) in a Stretch container (gcc-6). Initially it
crashed on the same strd, so I tried switching to clang and then
encountered the same "undefined reference to `free'" errors you guys had
mentioned. These come about mainly due it not being supported to call
free() before declaration in C99, so then the fix was to add #include
 in a couple places.

I don't think I'll attempt another Xenial or Trusty build anytime soon.
I'd like to get some fixes documented and patches submitted upstream so
that others can start building Firefox armhf across more platforms.
Anyone can still run the 18.04 binary I linked earlier on 16.04 (and
possibly 14.04) using the LD_PRELOAD trick.

As for how Arch Linux has been working, I've confirmed it's due to
--disable-stylo (mentioned a while ago on the Raspberry Pi forum
thread). If I add that flag (while leaving SK_JUMPER_USE_ASSEMBLY
intact) then Firefox runs. For some reason the Stylo flag does not get
listed in about:buildconfig but it's a very different build path when
MOZ_STYLO is disabled, and Stylo is still disabled for Android nightly
too.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

@herrtimson are you expecting revert-128661.patch to fix the strd r2,
r3, [r1] startup segfault on xenial/trusty, the Skia assembly illegal
instruction, or both?

The discussion in bug 1434526 indicates this patch is necessary on
Firefox 60 to resolve an armhf build failure on the latest trunk, but
that regression appears to be newer than both of the crash symptoms at
hand here.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Here is a working Firefox 59 deb package cross-compiled for 18.04 armhf:
https://www.dropbox.com/s/17ypog6btdq4wj7/firefox_59.0.1%2Bbuild1-0ubuntu1_armhf.deb?dl=0

I have installed and tested on RaspEX (Bionic armhf). I can also confirm
it works sandboxed on Ubuntu MATE Xenial and Raspbian Stretch. One way
to run on older systems is to unpack locally using ar + tar, download
libc6 and libstdc++6 bionic armhf debfiles and untar them as well, then
do:

  cd path/to/usr/lib/firefox
  
LD_PRELOAD=path/to/usr/lib/arm-linux-gnueabihf/libstdc++.so.6:path/to/lib/arm-linux-gnueabihf/libm.so.6
 \
./firefox

Cross-compiling via dpkg-buildpackage is fraught of issues, and similar
to what Chituc experienced the most difficult part was getting rustc to
properly cross-compile in all cases. I posted my main workaround for a
host/target header bug here: https://github.com/rust-lang-nursery/rust-
bindgen/issues/1229

To prevent the Skia misaligned instruction crash, I ended up editing
gfx/skia/generate_mozbuild.py to force SK_JUMPER_USE_ASSEMBLY to False.
However, there's stubborn code at the top of SkJumper.cpp that ends up
turning it on again so I had to override that too. Telling Skia to use
its non-asm fallback mode should be better than disabling Skia
altogether as we had for Firefox 57.

I tested some of our earlier theories too, and so far building Skia with
clang, everything with -thumb, -fstack-protector-strong, --enable-rust-
simd or other suggestions above do not seem to help at all with the Skia
SIGILL nor the strd r2, r3, [r1] SIGSEGV.

As for that strd r2, r3, [r1] crash, not much progress there aside from
our theory that it's in the XPCOM armhf-specific code. I'm merely
avoiding it by building in a 18.04 Docker container, but still no idea
why that works.

** Bug watch added: github.com/rust-lang-nursery/rust-bindgen/issues #1229
   https://github.com/rust-lang-nursery/rust-bindgen/issues/1229

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

@levente (and maybe @herrtimson),

I set up a new Ubuntu MATE system, and in the process realized that your
segfault in /lib/ld-linux-armhf.so.3 is a symptom of bug 1576432. That's
where gdb fails not only for Firefox but even a simple helloworld
program. The workaround there is to install libc6-dbg, which will allow
you to see one of the other two crash signatures that we still don't
have a solution for.

@Chituc,

By waiting a couple days on my Pi 3 I managed to make a gcc-4.9 build of
Firefox 59.0.1, which then crashes on strd r2, r3, [r1]. I'm now
thinking that this startup crash may be more nuanced than being specific
to Ubuntu 16.04 or gcc-5.4. In fact, the Launchpad builds are now
showing something odd: While the 59.0.1 14.04 build that we've talked
about gets all the way to the Skia SIGILL, the recent 59.0.2 14.04 build
from
https://launchpad.net/ubuntu/trusty/armhf/firefox/59.0.2+build1-0ubuntu0.14.04.1
segfaults on the strd too.

At least with a custom build I'm now able to get accurate debug symbols.
With the TUI I inspected the source at each level of this stack trace:

#0  0x717c4bc8 in JS::Value::setObjectNoCheck (obj=0x67d62160, this=) at 
/home/jdonald/firefox-59.0.1+build1/obj-arm-linux-gnueabihf/dist/include/js/Value.h:380
#1  JS::Value::setObject (obj=..., this=) at 
/home/jdonald/firefox-59.0.1+build1/obj-arm-linux-gnueabihf/dist/include/js/Value.h:375
#2  js::MutableWrappedPtrOperations::setObject (obj=..., this=)
at 
/home/jdonald/firefox-59.0.1+build1/obj-arm-linux-gnueabihf/dist/include/js/Value.h:1362
#3  mozJSComponentLoader::Import (this=this@entry=0x67a08000, 
registryLocation=..., targetValArg=..., targetValArg@entry=..., 
cx=cx@entry=0x76a56000,
optionalArgc=optionalArgc@entry=0 '\000', retval=retval@entry=...) at 
/home/jdonald/firefox-59.0.1+build1/js/xpconnect/loader/mozJSComponentLoader.cpp:980
#4  0x717e8c64 in nsXPCComponents_Utils::Import (this=, 
registryLocation=..., targetObj=..., cx=0x76a56000, optionalArgc=0 '\000', 
retval=...)
at 
/home/jdonald/firefox-59.0.1+build1/js/xpconnect/src/XPCComponents.cpp:2297
#5  0x7119c544 in NS_InvokeByIndex (that=0x1, methodIndex=0, 
paramCount=1742086496, params=0x7effb9f8)
at 
/home/jdonald/firefox-59.0.1+build1/xpcom/reflect/xptcall/md/unix/xptcinvoke_arm.cpp:413
#6  0x001e in ?? ()

(and ran disas /r 0x717c4bc8,... to confirm that this symbol-laden debug
session was still hitting strd r2, r3, [r1])

The most suspicious code is actually the XPCOM invocation. The armhf-
specific assembly in https://hg.mozilla.org/mozilla-central/raw-
file/tip/xpcom/reflect/xptcall/md/unix/xptcinvoke_arm.cpp is worrisome.
It has no way of knowing whether registers d16 through d31 are
available, so may allocate the wrong amount of stack space and clobber
extra registers when mixing -mfpu=vfpv3-d16 with -mfpu=neon. The code in
xptcinvoke_aarch64.cpp is completely different and looks more robust.

Thus, if anyone is trying to set up a build environment on Ubuntu 14.04
Trusty, keep in mind you might still hit the strd r2, r3, [r1] SIGSEGV.
On Bionic: the 59.0.1 18.04 build from Launchpad was okay in this
regard, while the 59.0.2 18.04 build hasn't been posted yet so fingers
crossed that it does not regress in the same way.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Thanks @Chris!

@herrtimson you can do this:
  layout asm
  tui disable
  set logging on
  disas /r ,

It'll save the output of your disas command to gdb.txt

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

@herrtimson we already confirmed that the gcc-7 / Bionic build crashes
on the exact same misaligned instruction in Skia. See responses #48 and
#50 for how I tested this, the point being that waiting for Bionic alone
won't fix this.

Diagnosing a corrupt stack: whether you have debug symbols or not you
should run this in gdb: layout asm. This will tell you if it's the same
Skia illegal/misaligned instruction, the earlier SIGSEGV crash at strd
r2, r3, [r1], or something else. Because levente was using a 16.04 deb
he was most likely hitting the known SIGSEGV. Would be good to identify
your build's crash because we don't have any other datapoints for gcc 6.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

@Chituc,

I attempted to set up an Ubuntu 14.04 Firefox build environment, and am
realizing how difficult it is to troubleshoot something old and barely
supported.

Instead, could you take your existing 16.04 build flow but run sudo apt
install g++-4.8 then build with CC=gcc-4.8, CXX=g++-4.8?

There's a decent chance this will get you past the strd r2, r3, [r1]
crash, which would then allow you to complete your test of the clang
Skia theory.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Ugh, yeah doing some simple helloworld tests confirms these are armhf
gcc *defaults*.

> it's what *defines* armhf as armhf.

Defines: This appears true for -march=armv7-a -mfloat-abi=hard. As for
-mfpu, adding -mfpu=neon results in some assembly differences, namely
using register d16 and above.

> Unless something is explicitly setting those things differently

The Firefox build log has some instances of -mfpu=neon, particularly in
Skia. However, Chromium does as well so indeed this is a longshot.

Looks like we're back to the drawing board. Still some hope with changes
like building Skia using clang, adding -mthumb, or -fstack-protector-
strong, but none of these other differences stand out as something
present in both the Chromium and Arch Linux builds.

I think I misunderstood earlier about the intent of looking at Firefox
57's about:buildconfig. As that's technically still a Skia-broken build,
we can continue to examine that configuration for other differences vs
the Arch Linux one.

> [herrtimson] If there's a chance to get the output of
about:buildconfig regardless the segfault at startup, I'm all eager to
learn about this.

With broken browsers like Firefox 58 and 59 armhf, find the build config
like so:

strings /usr/lib/firefox/omni.ja | grep -A 31 "Built from"

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

> [herrtimson] I wrote an email to Chris Coulson, asking for some
assistance with the cflags. Hopefully he'll read it.

Thanks. I flagged him on #ubuntu-devel IRC as well. Hopefully we'll get
his attention this time.

> > [Chituc] Can you check if the firefox 57.04 trusty , the working one shows
"-march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16" in about:buildconfig ?
> [Chris] It’s not showing those flags in about:buildconfig

I don't think this matters, because Firefox 57 Trusty still has the Skia
crash for most armhf users. The main difference between Firefox 57 and
58/59 is that in Firefox 57 it's possible to disable Skia via prefs.js,
but otherwise the misaligned instruction bug is still there.

> it fixes freebsd only, but still it might be helpfull to see what they
changed.

The majority of that patch deals with atomics, compare-and-swap, and
memory barriers, although might be worth noticing that it does add
-march=armv7-a

> [Chituc] Builing on xenial did nto worked but a build in trusty have
great chances to work .

Right, but important to note that building on Bionic will likely work
too. That point may be helpful in getting the Ubuntu team to prioritize.

> CFLAGS="-march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16"

In case anyone is testing this soon, be sure to set both CFLAGS and
CXXFLAGS. SkJumper_generated.S is assembly and I'm not sure which of the
two flag sets gets passed, but the Skia project is largely C++.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Awesome, thanks for confirming Arch still works and posting the
screenshot.

> Also anyone tried to run the binary from bionic, which should be built
with gcc-7 as well?

Yes, Lars and I both tried this. It's rather buried in discussion above
but search for the part where I mention "ignore the dependency" in order
to test the gcc 7 Bionic build on a Xenial system.

> --enable-rust-simd caught eye, what is this all about?

There are Rust bindings for Skia, but the part where it crashes doesn't
use Rust. From your screenshot I think these are likely the key missing
flags: -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16

In the conversation above, those are exactly the flags we suspected from
comparing the Chromium build. Looks like we don't actually need clang,
and we don't need -mthumb

Well, there's still the other startup crash specific to Ubuntu 16.04
packages. Given we don't hit it on the Bionic nor Trusty builds, that
problem is likely specific to gcc 5.4

Now we just need someone with access to change the default build
settings on Launchpad.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

I think we just have the IRC logs that Chituc posted, no bug id.

When I searched https://bugs.chromium.org/p/skia/issues/list last months
for issues with the keyword "armhf" I did not find any such bug filed.

At the time I was about to file a ticket myself, but that made me first
run through the thought process of what their initial response might be.
Imagining that to be "well, it works for Chromium" is what inspired me
to look more closely at the chromium-browser build logs.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

> By the way I managed to set up a cross compile development

That's great news. Could you post your instructions? This would allow
others here to help out, considering most of us don't have ARM boards
with much RAM or 20 hours of patience.

This also opens up the possibility of making a build on Debian 9 to
match up better with Raspbian Stretch, rather than having to resort to
14.04 binaries there.

> Ok so in firefox 58.02 we have 2 bugs , this one "RootingAPI.h:580"
and the _sk_xor__vfp4 that I hope to get fixed by compiling with clang .

It appears that way, although worth noting that the crash at startup
also happens in Firefox 57, specific to the 16.04 build. You can check
that out by doing wget
http://launchpadlibrarian.net/352606050/firefox_57.0.4+build1-0ubuntu0.16.04.1_armhf.deb
and running it.

> You sugest me to get the firefox 58 from ubuntu 14 ?

Yeah, it appears to get around the crash at startup (before any window
appears, and thus before the SkJumper part) it might be necessary to
build under Ubuntu 14.04 toolchains (gcc 4.8, libc 2.19).

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

There was a typo in my above post, should say javascript.enabled, but
I'll assume you didn't have the extra dot when tried yesterday.

> I installed debug symbols

I just realized this makes it sound like you installed firefox-dbg,
which would give incorrect addresses because those symbols are for the
public apt binary. Do you mean that you *rebuilt* with debug symbols
(-g)?

> Can you check where that "crashes obscurely elsewhere" crashed ?

My NOP test earlier was flawed because it did not get the program
counter back onto a 4-byte aligned instruction + switch out of Thumb
mode. The fix was to hexedit in the thumb instructions 0020; 0047 (movs
r0, #0; bx r0). With this, Firefox 58 continues further on and then
crashes here:

   0x0040517c <_start+0>:   4f f0 00 0b mov.w   r11, #0
   0x00405180 <_start+4>:   4f f0 00 0e mov.w   lr, #0
   0x00405184 <_start+8>:   02 bc   pop {r1}
   0x00405186 <_start+10>:  6a 46   mov r2, sp
   0x00405188 <_start+12>:  04 b4   push{r2}
   0x0040518a <_start+14>:  01 b4   push{r0}
   0x0040518c <_start+16>:  df f8 24 a0 ldr.w   r10, [pc, #36]  ; 
0x4051b4 <_start+56

Firefox 59 crashes at the same instruction sequence, although the
addresses are of course different.

Getting a backtrace with symbols: Unfortunately for me if I install
firefox-dbg, firefox -g just hangs indefinitely. I thought this was due
to the limit of 1 GB RAM on a Raspberry Pi 3, but it doesn't get any
further even if I add gigabytes of swap space or wait a while.

It's also possible that the crash you're hitting is in the neighborhood
of the other one we were avoiding on Firefox 57 by specifically
installing the 14.04 package. The 16.04 packages of 57, 58, and 59 don't
even hit the SkJumper bug, instead crashing at an earlier point on this:

=> 0xf314e830:  c1 e9 00 23 strdr2, r3, [r1]
   0xf314e834:  05 9b   ldr r3, [sp, #20]
   0xf314e836:  06 9a   ldr r2, [sp, #24]
   0xf314e838:  1a 60   str r2, [r3, #0]
   0xf314e83a:  9d f8 38 30 ldrb.w  r3, [sp, #56]   ; 0x38

Although this does not appear the same as the crash on your custom
build, interestingly in both cases the segfaulting instruction is
precisely strd r2, r3, [r1]

To confirm if you're actually getting past the SkJumper problem point,
after a few seconds the Firefox window frame should appear on the screen
before it crashes. That's the behavior on
firefox_58.0+build6-0ubuntu0.14.04.1_armhf.deb currently while
firefox_58.0.2+build1_0ubuntu0.16.04.1_armhf.deb just aborts before
getting that far.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Nice work!

If you edit your prefs.js to disable JIT (javascript.options.baselinejit
= false) or try to disable JavaScript altogether (java.script.enabled =
false), does it crash at the same point?

(I would expect so as these flags have not helped much when
troubleshooting in the past, but it's still something I check whenever
seeing a backtrace with JS::)

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

That's an interesting idea. As I mentioned above chromium-browser builds
with -mthumb so it's possible this is a key flag.

Sorry to hear that Firefox does not build with clang out of the box.
Another possible approach is to build the majority of Firefox with gcc
but the Skia portion in clang. You could take a look at
https://hg.mozilla.org/mozilla-central/raw-
file/tip/gfx/skia/generate_mozbuild.py and figure out how to override
the compiler just for Skia. This would still take at least 20 hours but
you are less likely to encounter clang-specific bitrot across Firefox.

To build only libxul.so, as well as to iterate quickly when you attempt
fixes like -std=gnu89 to address specific errors, have you tried the
instructions at https://developer.mozilla.org/en-
US/docs/Mozilla/Developer_guide/Mozilla_build_FAQ#Making_builds_faster ?

Thanks for working on this. It's quite an endeavor to build Firefox from
source and we're all cheering you on.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

I see. You're right, the kernel is aarch64 but the compiler and build
tools are armhf. The chromium-browser build log reports the same, so
cross-compilation might not be necessary.

> If you can help with what mods are required to make it compile with
clang I can try to compile it in a armhf Ubuntu 16.04 .

According to this link (https://developer.mozilla.org/en-
US/docs/Mozilla/Developer_guide/Build_Instructions/Compiling_Firefox_With_Clang_On_Linux)
you just need to edit your mozconfig to set CC=clang and CXX=clang++. In
theory you could also test compiler flags like -mfpu=vfpv3-d16 just by
setting CFLAGS and CXXFLAGS.

Many thanks if you can try this out in your build environment.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Thanks for trying that, Lars. libfontconfig 2.11 vs 2.12 should be
compatible so you could force it to ignore the dependency or run in a
sandbox dir without installing. For example: ar xv
firefox_58.0.2+build1-0ubuntu1_armhf.deb; tar xvf data.tar.xz; cd
./usr/lib/firefox; ./firefox

This gave me the idea that this could even be tested on Ubuntu MATE
16.04, so I tried that. The only other dependency I had to unpack
locally was gcc-7 libstdc++6:
https://launchpad.net/ubuntu/bionic/armhf/libstdc++6/7.3.0-1ubuntu1

Unfortunately this gcc-7 build crashes on the same misaligned
instruction, so that dashes hopes of resolving this merely with a newer
toolchain.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Thanks Chituc. That's spot-on with the identical error in Firefox.
Specifically, it's not an illegal instruction so much as a misaligned
(+2 bytes) instruction, plus at that point it's in Thumb mode when
anything inside SkJumper should be in ARM mode.

Technically both firefox and chromium-browser are cross-compiled because the 
Launchpad logs show the host system as aarch64 while the target is armhf:
* 
https://launchpadlibrarian.net/356307711/buildlog_ubuntu-xenial-armhf.firefox_58.0.2+build1-0ubuntu0.16.04.1_BUILDING.txt.gz
* 
https://launchpadlibrarian.net/357154172/buildlog_ubuntu-xenial-armhf.chromium-browser_64.0.3282.167-0ubuntu0.16.04.1_BUILDING.txt.gz

Chromium adds a few more flags that might affect NEON i.e. -mfloat-
abi=hard -mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb, but as you've
pointed out the biggest difference is compiling with clang. Apparently
clang is actually supported for building Firefox on Linux, so maybe the
Launchpad script could be augmented to just add two required lines to
mozconfig.

Looks like Firefox 58 for 18.04 Bionic armhf built successfully and uses gcc 7: 
https://launchpad.net/ubuntu/+source/firefox/58.0.2+build1-0ubuntu1/+build/14326274
Anyone able to try it out?

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Various notes:

Good point by Chituc. I had assumed this was already cross-compiled, but 
according to the Ubuntu build log:
> checking whether cross compiling... no

Who here knows how the Arch Linux armhf package is built?

It's also still possible that a newer toolchain could fix things. I read
somewhere that Ubuntu 18.04 Bionic would be upgrading to gcc 7. Anyone
tried Firefox 58 or 59 on there?

The SkJumper_generated source is available on Mercurial:
https://hg.mozilla.org/mozilla-central/raw-
file/tip/gfx/skia/skia/src/jumper/SkJumper_generated.S

It's possible to take a closer look at the "illegal instruction" with
firefox -g. At the crash point in gdb, run: layout asm; set arm
fallback-mode arm; tui disable; disas /r ,. Initially it gets confused about the instruction layout,
but after trying different ranges it'll eventually decode properly:

(gdb) disas /r 0xf458bb28,0xf458bb3e
Dump of assembler code from 0xf458bb28 to 0xf458bb3e:
   0xf458bb28:  92 2c 44 f2 vfma.f32d18, d20, d2
   0xf458bb2c:  93 3c 44 f2 vfma.f32d19, d20, d3
   0xf458bb30:  b0 01 20 f2 vorrd0, d16, d16
   0xf458bb34:  b1 11 21 f2 vorrd1, d17, d17
   0xf458bb38:  b2 21 22 f2 vorrd2, d18, d18
   0xf458bb3c:  b3 31 23 f2 vorrd3, d19, d19
End of assembler dump.

However, those are exactly the instructions specified for _sk_xor__vfp4
in SkJumper_generated.S. It's hard to see how the compiler or binutils
could be directly responsible for generating an illegal instruction
here.

You can actually hexedit libxul.so and change those four vorr
instructions into NOPs. Firefox then makes it past this point but
crashes obscurely elsewhere, with different crash signatures on Firefox
58 vs 59.

Firefox arm64 (Pi 3 or other 64-bit board required) 58 and 59 still
work.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Darn, and I see the same error with Firefox 59. Your stack trace still
shows the illegal instruction in sk_xor__vfp4(). It seems like something
is now running Skia even when it's disabled in the config.

Among rendering differences, from the Firefox 58 blog post there's those
changes for OMTP which could have affected this:
https://mozillagfx.wordpress.com/2017/12/05/off-main-thread-painting/

If it's now going into Skia when it shouldn't that's a Firefox 58
regression. It would be somewhat of a bug affecting non-armhf platforms
too so we could finally get the attention of the Mozilla team.

Meanwhile the bad assembly in SkJumper_generated.S still seems like an
Ubuntu-specific problem. Is anyone able to reach the Ubuntu dev team on
IRC so that can set this bug's status back to "confirmed"?

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1745619] [NEW] Failed to open local calendar with "Timeout was reached"

[Donald Pellegrino]

Public bug reported:

After booting into a GNOME session, Evolution was started. Mail appeared
as expected. When the Calendar section was opened, none of the calendars
opened including the local calendar. A blue report was printed under the
toolbar with the error that it could not open the local calendar as
"Timeout was reached." It seems odd that there should be a timeout issue
when accessing local data. The local calendar is stored on the save
drive and mount point as the OS and Evolution.

Closing and reopening Evolution did not resolve the issue.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evolution 3.26.1-1
ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jan 26 09:12:29 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2017-08-12 (166 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to artful on 2017-10-21 (96 days ago)

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


** Tags: amd64 apport-bug artful 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/1745619

Title:
  Failed to open local calendar with "Timeout was reached"

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

levente,

I'm not sure how Lars and Sam Tygier (#1732954) are getting useful
backtraces. Might have something to do with running 17.10?

> ii firefox 57.0.4+build1-0ubuntu0.16.04.1 armhf

I see you're using 16.04. I should have mentioned that the workaround of
disabling Skia is something I verified using the 14.04 Trusty package
(on Raspbian). The flag also seems sufficient for Firefox to run on
17.10, but from what I can tell there's a second crash specific to the
16.04 build. To avoid that unknown, you can download and install the
Trusty .deb (via dpkg -i) even if your system is 16.04 Xenial:
https://launchpad.net/ubuntu/trusty/armhf/firefox/57.0.4+build1-0ubuntu0.14.04.1

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

Thanks for providing the stack trace, Lars.

This shows the illegal instruction is happening in Skia, specifically
SkJumper's implementation of _sk_xor__vfp4. To run with Skia disabled,
edit your user profile at ~/.mozilla/firefox/*.default/prefs.js and add
the following line:

user_pref("gfx.content.azure.backends", "");

Firefox 32-bit will then launch on Raspbian Stretch. Or if you have more
than one user, you can instead edit /usr/lib/firefox/defaults/pref
/vendor-gre.js

I expect rendering performance is taking a hit with Skia disabled. For a
proper fix we should figure out what's going on with the illegal
instruction(s) in SkJumper_generated.S. This file is auto-generated so
from what I can tell the armv7 version isn't readily available via git.
I have yet to set up a build environment for Firefox, but if someone
here has done so for Arch Linux and another for Ubuntu, we can diff and
track this down.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1741948] [NEW] Evolution ignores tile window commands in GNOME

[Donald Pellegrino]

Public bug reported:

As per the Help "Ubuntu Desktop Guide -> Desktop -> Applications and
windows -> Windows and workspaces -> Windows" documentation for "Tile
windows:"

"To maximize a window along a side of the screen, grab the titlebar and
drag it to the left or right side until half of the screen is
highlighted. Using the keyboard, hold down Super and press the Left or
Right key."

When the Evolution main window has focus, the Super + Left and Super +
Right commands are ignored. Additionally, it does not snap to the left
or right when the titlebar is grabbed and dragged to either side of the
screen.

All other GNOME apps do behave as expected. Testing was done with a
GNOME/Xorg session.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evolution 3.26.1-1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jan  8 13:34:57 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-12 (149 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to artful on 2017-10-21 (78 days ago)

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


** Tags: amd64 apport-bug artful 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/1741948

Title:
  Evolution ignores tile window commands in GNOME

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

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

[Bug 1741908] Re: Calendar Month View Appointment mouse-over context window disappears

[Donald Pellegrino]

This issue seems to be limited to a GNOME/Wayland session. The content
window persists as expected in a GNOME/Xorg session.

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

Title:
  Calendar Month View Appointment mouse-over context window disappears

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

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

[Bug 1741908] [NEW] Calendar Month View Appointment mouse-over context window disappears

[Donald Pellegrino]

Public bug reported:

In the Calendar Month View of the Evolution user interface, Appointments
are drawn within the day blocks. They begin with the time and the
beginning of the Appointment Summary. When the mouse is moved on top of
the Appointment rectangle, a content window is drawn to show additional
details. However, the context window display amounts to a flicker as it
almost immediately disappears again.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evolution 3.26.1-1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jan  8 09:37:32 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-12 (148 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to artful on 2017-10-21 (78 days ago)

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


** Tags: amd64 apport-bug artful third-party-packages 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/1741908

Title:
  Calendar Month View Appointment mouse-over context window disappears

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

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

[Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[James Donald]

That fix was:
>   * Hopefully fix LP: #1711337 by building the armhf build with
> -fno-schedule-insns to work around a compiler bug
?

According to 
https://launchpadlibrarian.net/351233449/buildlog_ubuntu-xenial-armhf.firefox_57.0.3+build1-0ubuntu0.16.04.1_BUILDING.txt.gz
 it's building with:
> --enable-optimize=-g -O2 -fno-schedule-insns

So it looks like the fix was indeed ported, but given the word
"hopefully", but was it ever confirmed?

Just like Adam Smith with version 55, arm64 appears to be fine. And just
like herrtimson with version 55, even armv7 works on Arch Linux but
still crashes on Debian/Ubuntu:
https://www.raspberrypi.org/forums/viewtopic.php?f=63=150438=50

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

[Bug 1729524] [NEW] No ability to set chuck size for mdadm during Ubuntu Server installation routine

[Donald Schultz]

Public bug reported:

When setting up a Linux software RAID array inside the Ubuntu Server
install routine (which uses mdadm), beyond the ability to specify array
members and personality, there is no ability to tweak the chunk size.
The chunk size defaults to 512KB which would be suitable for a very
specific set of uses but quite suboptimal for others.  The underlying
hardware is also a factor, as SSDs benefit from a much smaller chunk
size due to high performance at high queue depths regardless of use
case.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: bot-comment

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

Title:
  No ability to set chuck size for mdadm during Ubuntu Server
  installation routine

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

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

[Bug 1710491] [NEW] When the "Back Up" dialog is resized, the text panel does not expand vertically.

[Donald Pellegrino]

Public bug reported:

When a backup is being run, a details button can be clicked to show the
list of files being processed. The details appear in a "Back Up" dialog.
When this dialog is resized, the details text box expands horizontally
as expected. However, it does not expand vertically.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: deja-dup 34.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Aug 13 13:09:15 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-12 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  When the "Back Up" dialog is resized, the text panel does not expand
  vertically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1710491/+subscriptions

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

[Bug 1710383] Re: Could not install 'gconf2' and upgrade frozen

[Donald Pellegrino]

This is a critical bug. It led to a path requiring a clean install of
Ubuntu and a restore of user data from backups. The upgrade was
ultimately unrecoverable even when booting to a Live USB stick to
continue the upgrade.

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

Title:
  Could not install 'gconf2' and upgrade frozen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1710383/+subscriptions

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

[Bug 1710397] [NEW] Unable to identify package based on windows for some applications

[Donald Pellegrino]

Public bug reported:

When running ubuntu-bug -w the following message is output to terminal:

Gtk-Message: GtkDialog mapped without a transient parent. This is
discouraged.

Clicking on windows from GNOME Terminal or Backups has not effect.
Clicking on a Firefox window however, will trigger the expected
behavior. It seems ubuntu-bug -w is only recognizing some windows.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: apport 2.20.4-0ubuntu4.5
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CrashReports: 640:1000:122:995835:2017-08-12 12:30:28.203223748 
-0400:2017-08-12 12:30:27.252524580 
-0400:/var/crash/_usr_bin_update-notifier.1000.crash
CurrentDesktop: GNOME
Date: Sat Aug 12 13:40:46 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-12 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Unable to identify package based on windows for some applications

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

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

[Bug 1710383] [NEW] Could not install 'gconf2' and upgrade frozen

[Donald Pellegrino]

Public bug reported:

When performing a distribution upgrade from Ubuntu 16.04.3 xenial to
17.04, a dialog is generated with the following messages:

Could not install 'gconf2'
The upgrade will continue but the 'gconf2' package may not be in a working 
state. Please consider submitting a bug report about it.
dependency problems - leaving triggers unprocessed

The dialog has a Close button. Clicking it closes the dialog but it then
reappears again immediately. It is stuck in a loop.

The distribution upgrade dialog continues in the background for a while.
However, it then freeze having last reported "Configuring libpam-systemd
(amd64)" in the "Installing the upgrades" step.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-software 3.20.5-0ubuntu0.16.04.5
ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
Uname: Linux 4.4.0-91-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Aug 12 10:54:28 2017
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: Upgraded to xenial on 2017-08-12 (0 days ago)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

** Attachment added: "Screenshot of error dialog and progress as of freeze."
   
https://bugs.launchpad.net/bugs/1710383/+attachment/4931356/+files/Screenshot%20from%202017-08-12%2010-59-59.png

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

Title:
  Could not install 'gconf2' and upgrade frozen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1710383/+subscriptions

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

[Bug 1032456] Re: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2

[Donald Pellegrino]

I was having this problem with a Canon PIXMA MP470 printer
(https://www.usa.canon.com/internet/portal/us/home/support/details/printers
/support-inkjet-printer/mp-series/pixma-mp470) connected via USB to
Ubuntu 16.04.2 LTS. As per
https://wiki.ubuntu.com/DebuggingPrintingProblems, I applied the
following commands:

$ cancel -a
$ lpq
MP470-series is ready
no entries
$ lpadmin -p MP470-series -o usb-unidir-default=true

I hit "Print Test Page" from the Printers settings dialog. The printer
test page then printed as expected.

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

Title:
  Canon inkjets (and some other printers) print only half of the last
  page after 20120801 upgrade to v1.5.3-0ubuntu2

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

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

[Bug 245716] Re: file-roller puts temporary files in the home dir instead of /tmp

[Donald Dwane Ross]

I Deleted the ~/.cache/.fr-* files and saved 117GB on a 480GB SSD drive. My 
system had gone down with less than 500mb in free space after the last view zip 
file crash and my system would no longer let me log in to my main account 
(Constant re login attempts). I had to use the log in for fixing the system at 
the startup prompt and the system came up to Debian not Ubuntu 16.10. I 
Timeshifted back 2 days to get back to Ubuntu.
May need to look for a different file archive program, this is a big drive 
eater after a crash.

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

Title:
  file-roller puts temporary files in the home dir instead of /tmp

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/245716/+subscriptions

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

[Bug 1699396] [NEW] sha256sum mismatch in cloud images

[Donald Eugene Kutach]

Public bug reported:


6/20 Build

http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-
amd64-root.tar.gz

We have an automated process which downloads images. First the sha256sum
check passed but we saw unexpected EOF errors when trying to untar the
file. Later we were able to download and untar the file but the
sha256sum does not match.

>From the sha256sums file.

7584d5214285c249a9ae80f98b71d7cc216fd915be2ca40d82a1e4603b7ae257 
*xenial-server-cloudimg-amd64-root.tar.gz
Output in terminal

sha256sum  xenial-server-cloudimg-amd64-root.tar.gz
04f9bd06a12636ac1e747856de2797a8a17c8ebcfca4714c080912bff90eeca1  
xenial-server-cloudimg-amd64-root.tar.gz 

I suspect the file may have been replaced but the sha256sum value not
updated?

This fail on all of our build systems and the automated process has been
in place for months.

** Affects: livecd-rootfs (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/1699396

Title:
  sha256sum mismatch in cloud images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1699396/+subscriptions

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

[Bug 1673820] [NEW] package python3-uno 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Donald E. Lund]

Public bug reported:

this occurred after moving my ubuntu installation from an external usb
drive to my internal drive

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python3-uno 1:5.1.6~rc2-0ubuntu1~xenial1
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Tue Mar 14 08:52:15 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-03-13 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: libreoffice
Title: package python3-uno 1:5.1.6~rc2-0ubuntu1~xenial1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package python3-uno 1:5.1.6~rc2-0ubuntu1~xenial1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

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

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