[Bug 2061245] Re: Ubuntu 24.04 - GNOME on Xorg session crashes on launch

[Rich McAllister]

I'm having the same xorg crash problem on Xubuntu 24.04 beta, see
#2061246 (dup'ed to here.)  I can reproduce the problem with a Ubuntu
24.04 beta install, but there xorg always crashes, unlike the
Xubuntu/xfce4 flavor where the first login after booting fails but
trying again immediately will succeed.

There's some crash info left in Xorg.0.log, I'll attach it.


** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061245/+attachment/5764900/+files/Xorg.0.log

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

Title:
  Ubuntu 24.04 - GNOME on Xorg session crashes on launch

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


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

[Bug 1970402] Re: Initrd out of memory error after upgrade to 22.04

[Rich Johnson]

I'm also experiencing the Out of Memory error on a fresh install of
Ubuntu Server 22.04 on an Intel NUC BXNUC10i5FNK1 with 8GB of memory.
After pressing any key it boots to a kernel panic stating not syncing
VFS, unable to mount root fs.

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

Title:
  Initrd out of memory error after upgrade to 22.04

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


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

[Bug 1960018] Re: Boot Failure - linux-image-5.13.0-28-generic | regression

[Rich Johnson]

Just did a fresh install of 20.04.3 LTS, updated & installed linux-
generic-hwe-20.04 and it booted up just fine. Only difference is
/etc/default/grub on a client's appliance, this is the default/grub on
the machine that freezes:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

GRUB_DISABLE_OS_PROBER="true"

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

Title:
  Boot Failure -  linux-image-5.13.0-28-generic | regression

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


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

[Bug 1960018] Re: Boot Failure - linux-image-5.13.0-28-generic | regression

[Rich Johnson]

Same thing, hardware is an Intel NUC NUC10i5FNK. OS: Ubuntu Server
20.04.3 LTS. Kiosk machine, when I select 5.13.0-28 to boot, it just
freezes at loading ramdisk. 5.11.0-46-generic works just fine.

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

Title:
  Boot Failure -  linux-image-5.13.0-28-generic | regression

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


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

[Bug 1953333] [NEW] package libpython3.8:amd64 3.8.10-0ubuntu1~20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Joseph Rich]

Public bug reported:

notice while upgrading

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpython3.8:amd64 3.8.10-0ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
AptOrdering:
 python3.8:amd64: Install
 libpython3.8-stdlib:amd64: Install
 python3.8-minimal:amd64: Install
 libpython3.8-minimal:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Dec  6 10:52:47 2021
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2021-12-06 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: python3.8
Title: package libpython3.8:amd64 3.8.10-0ubuntu1~20.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package libpython3.8:amd64 3.8.10-0ubuntu1~20.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/195/+subscriptions


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

[Bug 1906542] Re: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data

[Rich]

(A bit delayed, but just for anyone finding this...)

No, you cannot remove a FAULTED normal data device - device_removal
involves migrating all the data off the old one, which you cannot do if
it's not there.

(logs and caches are different.)

You'll need to recreate the pool.

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

Title:
  echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds  says
  premission error, unable to reapair lost zfs pool data

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


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

[Bug 1949249] [NEW] zfs send --dedup with HWE kernel modules produces unreceivable stream

[Rich]

Public bug reported:

If you do zfs send -D with 0.8.x userland and 2.0.x kernel, it will
actually try to produce a deduplicated send stream (whereas 2.0.x
userland stubs out that flag and prints a "this did nothing, stop trying
to use it" note).

On the system that generated it (20.04 amd64, running 5.11.0-38-generic with 
zfs-0.8.3-1ubuntu12.13 zfs-kmod-2.0.2-1ubuntu5.1):
$ dd if=/dev/urandom of=/badidea/1 bs=1M count=16
$ sudo dd if=/dev/urandom of=/badidea/1 bs=1M count=16
$ sudo cp /badidea/1 /badidea/2
$ sudo zfs snap badidea@snap1
$ sudo zfs send -RLeD badidea@snap1 > dedupstream
$ sudo zfs recv badidea/badbadidea < dedupstream
internal error: Unknown error 1037
Aborted

On my Debian 10 testbed running zfs-2.1.99-422_gb0f3f393d (and same for kmod):
cannot receive: stream has unsupported feature, feature flags = 7

This functionality was dropped in commit
196bee4cfd576fb15baa6a64ad6501c594f45497. Since it does all its voodoo
in userland, it can indeed still generate a dedup'd stream.

Might it make sense to at least print a warning if using zfs send
--dedup with 2.0.x, as well as maybe copying the warning that 2.0.x
spits out on attempting to receive such a stream, so people don't
conclude that being unable to receive a send stream they generated means
their system is broken?

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

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

Title:
  zfs send --dedup with HWE kernel modules produces unreceivable stream

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


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

[Bug 1947902] Re: Under particular load, virtio-scsi backed / errors out

[Rich]

I lied, it totally happens on 20.04 (w/5.4.0-89-generic) and 21.04
(5.11.0-37-generic), I just had forgotten I hadn't used virtio-scsi on
them, just SATA.

Oh boy.

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

Title:
  Under particular load, virtio-scsi backed / errors out

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


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

[Bug 1947902] [NEW] Under particular load, virtio-scsi backed / errors out

[Rich]

Public bug reported:

As I often do, I tried running OpenZFS git master's ZFS Test Suite
against the new Ubuntu 21.10 release, to make sure nothing was secretly
broken.

This is on an Ubuntu 21.10 amd64 VM (running 5.13.0-20-generic) inside
VirtualBox 6.1.26 on Windows 10 x64, using virtio-scsi for the root
disk. The host is not experiencing any errors or low disk space or
anything whenever this occurs, and other VMs running on the host and
same physical disk are unaffected.

I have seen failures like this happen before when using VirtualBox's
TRIM/discard functionality, but that has to be very explicitly enabled
on the VM, and it's not.

It runs fine for a bit...then suddenly everything crashes and burns, after the 
root disk starts erroring out:
[ 5281.077557] virtio_scsi virtio1: request:id 869 is not a head!
[ 5284.066557] sd 2:0:0:0: [sda] tag#390 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.066561] sd 2:0:0:0: [sda] tag#390 CDB: Write(10) 2a 00 01 d4 a3 78 00 00 
a0 00
[ 5284.066562] blk_update_request: I/O error, dev sda, sector 30712696 op 
0x1:(WRITE) flags 0x800 phys_seg 20 prio class 0
[ 5284.066575] Aborting journal on device sda3-8.
[ 5284.066580] sd 2:0:0:0: [sda] tag#391 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.066581] sd 2:0:0:0: [sda] tag#391 CDB: Write(10) 2a 00 01 d4 18 00 00 00 
08 00
[ 5284.066582] blk_update_request: I/O error, dev sda, sector 30676992 op 
0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[ 5284.066584] Buffer I/O error on dev sda3, logical block 3702784, lost sync 
page write
[ 5284.066586] JBD2: Error -5 detected when updating journal superblock for 
sda3-8.
[ 5284.070494] EXT4-fs error (device sda3): ext4_journal_check_start:83: comm 
rs:main Q:Reg: Detected aborted journal
[ 5284.070666] EXT4-fs (sda3): Remounting filesystem read-only
[ 5284.071033] sd 2:0:0:0: [sda] tag#392 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071036] sd 2:0:0:0: [sda] tag#392 CDB: Read(10) 28 00 02 79 f1 80 00 00 
08 00
[ 5284.071037] blk_update_request: I/O error, dev sda, sector 41546112 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 5284.071047] sd 2:0:0:0: [sda] tag#393 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071049] sd 2:0:0:0: [sda] tag#393 CDB: Read(10) 28 00 02 79 f1 a0 00 00 
18 00
[ 5284.071049] blk_update_request: I/O error, dev sda, sector 41546144 op 
0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[ 5284.071055] sd 2:0:0:0: [sda] tag#394 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071057] sd 2:0:0:0: [sda] tag#394 CDB: Read(10) 28 00 02 79 f1 d8 00 00 
08 00
[ 5284.071057] blk_update_request: I/O error, dev sda, sector 41546200 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 5284.071062] sd 2:0:0:0: [sda] tag#395 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071064] sd 2:0:0:0: [sda] tag#395 CDB: Read(10) 28 00 02 79 f1 f0 00 00 
08 00
[ 5284.071064] blk_update_request: I/O error, dev sda, sector 41546224 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 5284.071071] sd 2:0:0:0: [sda] tag#396 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071072] sd 2:0:0:0: [sda] tag#396 CDB: Read(10) 28 00 02 79 f2 00 00 00 
18 00
[ 5284.071073] blk_update_request: I/O error, dev sda, sector 41546240 op 
0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[ 5284.071078] sd 2:0:0:0: [sda] tag#397 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071079] sd 2:0:0:0: [sda] tag#397 CDB: Read(10) 28 00 02 79 f2 20 00 00 
08 00
[ 5284.071080] blk_update_request: I/O error, dev sda, sector 41546272 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 5284.071085] sd 2:0:0:0: [sda] tag#398 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071086] sd 2:0:0:0: [sda] tag#398 CDB: Read(10) 28 00 02 79 f2 00 00 00 
08 00
[ 5284.071087] blk_update_request: I/O error, dev sda, sector 41546240 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 5284.071092] sd 2:0:0:0: [sda] tag#399 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071093] sd 2:0:0:0: [sda] tag#399 CDB: Read(10) 28 00 02 79 f2 00 00 00 
08 00
[ 5284.071094] blk_update_request: I/O error, dev sda, sector 41546240 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 5406.093848] scsi_io_completion_action: 2 callbacks suppressed
[ 5406.093857] sd 2:0:0:0: [sda] tag#402 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5406.093861] sd 2:0:0:0: [sda] tag#402 CDB: Read(10) 28 00 00 24 ff 40 00 00 
08 00
[ 5406.093862] print_req_error: 2 callbacks suppressed
[ 5406.093863] blk_update_request: I/O error, dev sda, sector 2424640 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 5406.093868] Read-error on swap-device (8:0:2424648)
[ 5406.093937] sd 2:0:0:0: [sda] tag#403 FAILED 

[Bug 1931779] Re: kdump just hung out of the box

[Rich]

My suggestion would be to print a warning unconditionally on first
install that you should test it and not assume it will just work, and/or
to not set crashkernel=... with the default in the first place so people
have to go explicitly set it (and, implicitly, read about the fact that
one size does not fit all when finding out how). (I would even do the
former if your very next commit landed the heuristic estimator to
improve this, until you were confident it worked in the majority of
cases.)

I know it's not readily programmatically possible to tell "will this
work" short of actually doing it, because haha hardware, my lament is
that in my experience, the default has _never_ worked, on my VMs or real
hardware, and I would not expect something to configure itself with
defaults, resulting in e.g. kdump-config status reporting "ready to
kdump" when asked, and then...not.

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

Title:
  kdump just hung out of the box

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


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

[Bug 1931779] Re: kdump just hung out of the box

[Rich]

I suppose I should have made it clear that just changing the amount of
memory reserved was not sufficient.

Perhaps it would be useful to print a message saying "hey, I know we set
something by default, but we don't expect that to actually work, so you
should probably test and adjust it"?

Because it sounds like it's not expected to work out of the box, and
configuring it to "on, but doesn't actually work or warn you" when you
install the package seems worse than not configuring it, similar to how
I wouldn't expect installing ccache to result in it sticking itself in
my PATH, reporting "ccache enabled and working" when asked, but then
defaulting to a max cache size of 4 kilobytes.

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

Title:
  kdump just hung out of the box

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


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

[Bug 1931779] Re: kdump just hung out of the box

[Rich]

** Description changed:

  I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04
  system, installed specifically to try reproducing a bug.
  
  But when I tried, after kdump-config status reported "ready to dump" on
  reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the panic to
  console and then just hung forever.
  
  After some blind guessing and twiddling both variables, I found that
- crashkernel=512M-:256M works.
+ crashkernel=512M-:256M works on this particular setup. (MS7850
+ motherboard, i5-4670 CPU, 5.4.0-42-generic kernel)

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

Title:
  kdump just hung out of the box

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

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

[Bug 1931779] [NEW] kdump just hung out of the box

[Rich]

Public bug reported:

I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04
system, installed specifically to try reproducing a bug.

But when I tried, after kdump-config status reported "ready to dump" on
reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the panic to
console and then just hung forever.

After some blind guessing and twiddling both variables, I found that
crashkernel=512M-:256M works.

** Affects: makedumpfile (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/1931779

Title:
  kdump just hung out of the box

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

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

Re: [Bug 1902767] Re: do-release-upgrade exits with "An unresolvable problem occurred while calculating the upgrade"

[Rich Stillman]

Thanks. I eventually removed enough packages from the system to allow the
upgrade to work. It was a long time ago so I don't remember the details
anymore and I think I threw out my notes.

Since then, apt upgrades, including kernel upgrades, have been working
fine.

Just one more year, and we get to do this all over again...

On Fri, May 14, 2021 at 11:03 PM Jesse Mallen <1902...@bugs.launchpad.net>
wrote:

> I also ran into this exact issue attempting an upgrade from 18.04 to
> 20.04. Let me know if I can provide any additional detail.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1902767
>
> Title:
>   do-release-upgrade exits with "An unresolvable problem occurred while
>   calculating the upgrade"
>
> Status in ubuntu-release-upgrader package in Ubuntu:
>   Confirmed
>
> Bug description:
>   This error comes up both before and after removing two ppas using ppa-
>   purge. Note that I am using a low-latency kernel with bionic. I would
>   suspect this but I upgraded another system running this kernel with no
>   problems.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: ubuntu-release-upgrader-core 1:18.04.40
>   ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65
>   Uname: Linux 5.4.0-52-lowlatency x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.9-0ubuntu7.18
>   Architecture: amd64
>   CrashDB: ubuntu
>   Date: Tue Nov  3 13:18:42 2020
>   InstallationDate: Installed on 2020-06-07 (148 days ago)
>   InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64
> (20200203.1)
>   PackageArchitecture: all
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: ubuntu-release-upgrader
>   Symptom: ubuntu-release-upgrader
>   UpgradeStatus: Upgraded to bionic on 2020-11-03 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1902767/+subscriptions
>
>

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

Title:
  do-release-upgrade exits with "An unresolvable problem occurred while
  calculating the upgrade"

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

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

[Bug 1922996] [NEW] alien 8.95.3 cannot create any debs

[Rich]

Public bug reported:

As described in Debian bugs [1] and [2], alien 8.95.3 (and .1 and .2,
but those aren't being shipped by any release of Ubuntu) cannot
successfully generate any debs, ever - with neither bug patched, it will
error out on attempting to generate any deb at all due to a syntax error
in the debian/rules it generates, and with that fixed, it will
incorrectly locate the files to be installed (e.g. /usr/include files
will end up in /include, and so on).

Please package 8.95.4 for Hirsute, or anyone who wants to use alien to
generate debs on Hirsute will be quite sad.

(Yes, to be clear, I did verify these bugs reproduce on Ubuntu's 8.95.3
alien package, though it was sort of a foregone conclusion, since Ubuntu
doesn't appear to patch it at all.)

[1] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983492
[2] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985835

** Affects: alien (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/1922996

Title:
  alien 8.95.3 cannot create any debs

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

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

[Bug 1767431] Re: restore type-ahead find, again

[Rich Smith]

This is really annoying, counter-intuitive behaviour. At the very least
the old behaviour should be restorable by a setting.

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

Title:
  restore type-ahead find, again

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

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

[Bug 1912215] Re: Unable to select time zone when installing

[Rich Amies]

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

** This bug has been marked a duplicate of bug 1903312
   Ubiquity not selecting correct timezone when connected to Internet

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

Title:
  Unable to select time zone when installing

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

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

[Bug 1912215] [NEW] Unable to select time zone when installing

[Rich Amies]

Public bug reported:

When installing Kubuntu with the daily build, I am unable to select a
time zone.  With nothing selected, I clicked to proceed with the install
and it appears to still proceed as expected.

I'm reporting as whilst installation appeared to work correctly for me,
there may be fringe cases where more than one time zone may be in
use(USA).  I have tried a second install, testing in that area, and the
Time Zone field remains unpopulated.

This is my first report, so I've probably done everything wrong! :o)

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

** Attachment added: "kub_daily_timezone_installer_USA.png"
   
https://bugs.launchpad.net/bugs/1912215/+attachment/5454172/+files/kub_daily_timezone_installer_USA.png

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

Title:
  Unable to select time zone when installing

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

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

[Bug 1786822] Re: Pinta constantly crashes in Ubuntu 18.04 fresh install

[Rich Hildred]

I updated mono

```
Mono JIT compiler version 6.12.0.90 (tarball Fri Sep  4 14:02:38 UTC 2020)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. 
www.mono-project.com
TLS:   __thread
SIGSEGV:   altstack
Notifications: epoll
Architecture:  amd64
Disabled:  none
Misc:  softdebug 
Interpreter:   yes
LLVM:  yes(610)
Suspend:   hybrid
GC:sgen (concurrent by default)

```

I rebooted and it still crashes.

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

Title:
  Pinta constantly crashes in Ubuntu 18.04 fresh install

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

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

[Bug 1906312] [NEW] Atempted to install UBUNTU 20.04 with windows 10 three times. It always stops 3/4 of the way.

[Rich Case]

Public bug reported:

11/30/20

PROBLEM:  attempted to install ubuntu 20.04 with windows 10.  stops 3/4 of the 
way through.
  I think the problem is the partitioning of the drive, or the fact 
that I am using a
  gaming computer. I had ben running only UBUNTU on this computer for 
over a year.


Computer:  MSI X470,  AMD® Ryzen 5 1600 six-core processor,  Memory: 16
GB

New: 1.0 TB Hard disk:  WDC WD10EZEX-00RKKA0

Unplugged old drives.  Only the new drive connected.

Successfully installed windows 10 from CD.

Within Windows:  Disabled fast startup.
 Disabled secure boot.
 Shrunk Drive C by 1/2 to make free space for Linux.

I ran Ubuntu 20.04 from a USB pen drive and selected INSTALL.

While installing,  I created 3 new Linux partitions:  /dev/sda2,  24 GB, Ext4, 
/ target
  /dev/sda5, 471 GB, Ext4, 
/home target
  /dev/sda6,  17 MB, Linux 
Swap

Continued installation of UBUNTU 20.04 :  Failed


ubuntu@ubuntu:~$ lsb_release -rd
Description:Ubuntu 20.04 LTS

ubuntu@ubuntu:~$ apt-cache policy pkgname
N: Unable to locate package pkgname

ubuntu@ubuntu:~$ /var/log/syslog and /var/log/partman 
bash: /var/log/syslog: Permission denied

richc...@verizon.net

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/efi.img
CasperMD5CheckResult: fail
CasperVersion: 1.445
Date: Mon Nov 30 10:39:20 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Atempted to install UBUNTU 20.04 with windows 10 three times.  It
  always stops 3/4 of the way.

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

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

[Bug 1902767] Re: do-release-upgrade exits with "An unresolvable problem occurred while calculating the upgrade"

[Rich Stillman]

I've just noticed an additional problem - do-release-upgrade did not
restore third-party repositories to /etc/apt/sources.list, so all my
third party packages have silently stopped being updated.

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

Title:
  do-release-upgrade exits with "An unresolvable problem occurred while
  calculating the upgrade"

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

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

Re: [Bug 1246441] Re: do-release-upgrade fails with "Could not calculate the upgrade"

[Rich Stillman]

Thanks for checking. I have submitted the bug report. It is bug
#1902767.

On Tue, Nov 3, 2020 at 12:36 PM Brian Murray <1246...@bugs.launchpad.net>
wrote:

> Please submit a new bug using 'ubuntu-bug ubuntu-release-upgrader' as
> that will add log files which I can examine to help sort out the
> situation.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1246441
>
> Title:
>   do-release-upgrade fails with "Could not calculate the upgrade"
>
> Status in ubuntu-release-upgrader package in Ubuntu:
>   Invalid
>
> Bug description:
>   Could not calculate the upgrade
>
>   An unresolvable problem occurred while calculating the upgrade.
>
>This can be caused by:
>* Upgrading to a pre-release version of Ubuntu
>* Running the current pre-release version of Ubuntu
>* Unofficial software packages not provided by Ubuntu
>
>   If none of this applies, then please report this bug using the command
>   'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 13.04
>   Package: ubuntu-release-upgrader-core 1:0.192.13
>   ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
>   Uname: Linux 3.8.0-32-generic i686
>   ApportVersion: 2.9.2-0ubuntu8.5
>   Architecture: i386
>   CheckboxSubmission: c3bdf3cb22c4bd8acbc2616fa3f80669
>   CheckboxSystem: edda5d4f616ca792bf437989cb597002
>   CrashDB: ubuntu
>   Date: Wed Oct 30 23:59:27 2013
>   InstallationDate: Installed on 2012-10-20 (375 days ago)
>   InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386
> (20120423)
>   MarkForUpload: True
>   PackageArchitecture: all
>   SourcePackage: ubuntu-release-upgrader
>   UpgradeStatus: Upgraded to raring on 2013-10-30 (0 days ago)
>   VarLogDistupgradeTermlog:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1246441/+subscriptions
>
>

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

Title:
  do-release-upgrade fails with "Could not calculate the upgrade"

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

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

[Bug 1902767] [NEW] do-release-upgrade exits with "An unresolvable problem occurred while calculating the upgrade"

[Rich Stillman]

Public bug reported:

This error comes up both before and after removing two ppas using ppa-
purge. Note that I am using a low-latency kernel with bionic. I would
suspect this but I upgraded another system running this kernel with no
problems.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.40
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65
Uname: Linux 5.4.0-52-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CrashDB: ubuntu
Date: Tue Nov  3 13:18:42 2020
InstallationDate: Installed on 2020-06-07 (148 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-11-03 (0 days ago)

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


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

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

Title:
  do-release-upgrade exits with "An unresolvable problem occurred while
  calculating the upgrade"

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

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

[Bug 1246441] Re: do-release-upgrade fails with "Could not calculate the upgrade"

[Rich Stillman]

I added the PPA packages back in, reinstalled the related software, and
removed them with ppa-purge. Followed that with apt update, autoremove
and a necessary reboot. After all that, I got the same "unresolvable
problem" error when I tried to do-release-upgrade.

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

Title:
  do-release-upgrade fails with "Could not calculate the upgrade"

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

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

[Bug 1246441] Re: do-release-upgrade fails with "Could not calculate the upgrade"

[Rich Stillman]

I added the PPA packages back in, reinstalled the related software, and
removed them with ppa-purge. Followed that with apt update, autoremove
and a necessary reboot. After all that, I got the same "unresolvable
problem" error when I tried to do-release-upgrade.

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

Title:
  do-release-upgrade fails with "Could not calculate the upgrade"

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

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

[Bug 1246441] Re: do-release-upgrade fails with "Could not calculate the upgrade"

[Rich Stillman]

I followed instructions and removed all ppas using add-apt-repository
--remove followed by ppa-purge. Nothing changed in the flow of do-
release-upgrade.

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

Title:
  do-release-upgrade fails with "Could not calculate the upgrade"

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

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

[Bug 1880211] Re: Logwatch package points to wrong location for zfs utils

[rich painter]

I'm running Ubuntu 16.04.7 LTS 64bit and Logwatch 7.4.2. 
My root user has /sbin in the path and when I run zpool I don't have to prefix 
it with the path.

Still to make this logwatch section work, I had previously edited my
/usr/share/logwatch/scripts/services/zz-zfs on lines 54 and 55 to have
the a different path "/sbin/zpool" and "/sbin/zfs" some time back.

However recently logwatch stopped reporting the ZFS section. For some strange 
reason file zz-zfs lines 54 and 55 now say:
my $pathto_zpool = $ENV{'pathto_zpool'} || 'zpool';
my $pathto_zfs   = $ENV{'pathto_zfs'}   || 'zfs';

And $pathto_zpool gets set to zpool. But the test on line 59 takes the
"exit 0". This test for existence requires a path!!! So whoever changed
this did this wrong!

I AGAIN have changed these lines to:
my $pathto_zpool = $ENV{'pathto_zpool'} || '/sbin/zpool';
my $pathto_zfs   = $ENV{'pathto_zfs'}   || '/sbin/zfs';

and all is working!

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

Title:
  Logwatch package points to wrong location for zfs utils

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

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

[Bug 1895970] [NEW] trying to install to new partition on existing removable drive

[Rich Hildred]

Public bug reported:

I think that it attached the crash report, but on initial installation,
it let me resize a ntfs partition to do ext4. It looks like it was
installing and then it said that I had a fatal error. I will try again
to see if I can boot from the created drive but it is trying to send a
bug report.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
Date: Thu Sep 17 08:27:16 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed 
quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu-mate

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

Title:
  trying to install to new partition on existing removable drive

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

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

[Bug 1892782] [NEW] linuxfx settings shows error when double clicking an icon

[Rich Godlewski]

Public bug reported:

Reproduce the error:

Open system settings, you should see "winfx settings" screen.

Double click one of the icons. it may work but if you double click one
of the icons again, you'll see an error message that says:

This application has raised an unexpected error and must abort"

[29] invalid object

FrmMain.BtnContas_Click.387

Ignore or Close are the buttons to click.


Description:Windowsfx 10
Release:10


N: Unable to locate package pkgname

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Attachment added: "error message dialog"
   https://bugs.launchpad.net/bugs/1892782/+attachment/5404227/+files/error.xcf

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

Title:
  linuxfx settings shows error when double clicking an icon

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

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

[Bug 1880211] Re: Logwatch package points to wrong location for zfs utils

[rich painter]

Same problem occurs with logwatch 7.4.2-1ubuntu1 in U 16:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Codename:   xenial

fix is the same.

regards
rich

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

Title:
  Logwatch package points to wrong location for zfs utils

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

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

[Bug 1880682] Re: LTS 20.04 install fails with probe failure locating drives that were FreeBSD (pfSense) formatted

[Rich Brennan]

** Package changed: apport (Ubuntu) => installation-report (Ubuntu)

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

Title:
  LTS 20.04 install fails with probe failure locating drives that were
  FreeBSD (pfSense) formatted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/installation-report/+bug/1880682/+subscriptions

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

[Bug 1880682] [NEW] LTS 20.04 install fails with probe failure locating drives that were FreeBSD (pfSense) formatted

[Rich Brennan]

Public bug reported:

I tried to install LTS 20.04 on a machine (e5-2670 powered)  which had
drives (Crucial 500GB SATA, HGST 2GB rotating) formatted for a pfSense
(FreeBSD) test. Install failed to probe for disks multiple times. dd'ing
zeros over the front part of thedrives allowed installation to proceed.

** Affects: apport (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/1880682

Title:
  LTS 20.04 install fails with probe failure locating drives that were
  FreeBSD (pfSense) formatted

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

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

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

[Rich Dammkoehler]

Public bug reported:

/boot/vmlinuz-5.1.15-surface-linux-surface is unsigned.
E: Your kernels are not signed with a key known to your firmware. This system 
will fail to boot in a Secure Boot environment.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 installed grub-efi-amd64-signed package post-installation script subprocess 
returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64-signed 1.93.16+2.02-2ubuntu8.15
Uname: Linux 5.1.15-surface-linux-surface x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Tue May 12 12:10:22 2020
ErrorMessage: installed grub-efi-amd64-signed package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-02-19 (813 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.93.16+2.02-2ubuntu8.15 failed to 
install/upgrade: installed grub-efi-amd64-signed package post-installation 
script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2020-05-12 (0 days ago)

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


** Tags: amd64 apport-package bionic 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/1878249

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

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

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

[Bug 1878096] [NEW] Log to file does not work in loggedfs 0.9-0

[Rich]

Public bug reported:

The log to file functionality does not appear to work in 0.9-0ubuntu2
(default on Ubuntu Focal). On 0.5-0ubuntu4 (tried on Ubuntu Xenial) the
-l  flag wrote the log to the specified file. In 0.9-0 the log
always ends up written to syslog regardless of what I specify to -l.

Example:
loggedfs -l /tmp/log.txt /tmp/mydir
 -> On 0.5-0 all operations on mydir are written to log.txt
 -> On 0.9-0 all operations on mydir are written to syslog

Weirdly if I run loggedfs in the foreground (using -f) it seems to work
as expected and the log is written to the specified file.

I've also tried installing 0.5-0 onto Ubuntu Focal and it works as
expected. Either there is a bug here, or the behavior has changed and
the instructions not updated.

** Affects: loggedfs (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/1878096

Title:
  Log to file does not work in loggedfs 0.9-0

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

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

[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0

[Rich]

I followed the steps above on Linux Mint, and the output of "journalctl
-b | grep i915" no longer had the "GPU HANG or Resetting rcs0 for hang
on rcs0" errors.

I also confirmed that running Zoom no longer has any lags or hangs.  It
works as expected.

So confirming this fix worked!

(Sorry, I'm new to this forum and not sure if I'm supposed to put tags
on my message like Chris did above).

tags:   added: verification-done-eoan
removed: verification-needed-eoan

Thanks.

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

Title:
  5.3.0-46-generic - i915 - frequent GPU hangs  / resets rcs0

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

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

[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0

[Rich]

I can also confirm that this problem continues in 5.3.0-51-generic

However, I see it very frequently (not just for 5 seconds... happening
all the time) with two different use cases.

1) When i have a headset (with a mic) plugged into the front audio port.
One of my cores also goes to 100% utilization.

or

2) When I run Zoom conferencing software.

Here is the journalctl output with 5.3.0-51-generic:

journalctl -b | grep i915
Apr 30 08:02:17 breath-mint kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
Apr 30 08:02:17 breath-mint kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Apr 30 08:02:17 breath-mint kernel: [drm] Finished loading DMC firmware 
i915/kbl_dmc_ver1_04.bin (v1.4)
Apr 30 08:02:17 breath-mint kernel: [drm] Initialized i915 1.6.0 20190619 for 
:00:02.0 on minor 1
Apr 30 08:02:17 breath-mint kernel: fbcon: i915drmfb (fb0) is primary device
Apr 30 08:02:17 breath-mint kernel: i915 :00:02.0: fb0: i915drmfb frame 
buffer device
Apr 30 08:02:26 breath-mint kernel: snd_hda_intel :00:1f.3: bound 
:00:02.0 (ops i915_audio_component_bind_ops [i915])
Apr 30 08:03:11 breath-mint kernel: [drm:intel_pipe_update_end [i915]] *ERROR* 
Atomic update failure on pipe B (start=4635 end=4636) time 115 us, min 1073, 
max 1079, scanline start 1072, end 1080
Apr 30 08:04:15 breath-mint kernel: [drm:intel_pipe_update_end [i915]] *ERROR* 
Atomic update failure on pipe B (start=8521 end=8522) time 130 us, min 1073, 
max 1079, scanline start 1072, end 1081
Apr 30 08:04:40 breath-mint kernel: i915 :00:02.0: GPU HANG: ecode 
9:0:0x, hang on rcs0
Apr 30 08:04:40 breath-mint kernel: i915 :00:02.0: Resetting rcs0 for hang 
on rcs0
Apr 30 08:04:48 breath-mint kernel: i915 :00:02.0: Resetting rcs0 for hang 
on rcs0
Apr 30 08:04:56 breath-mint kernel: i915 :00:02.0: Resetting rcs0 for hang 
on rcs0


My temporary work around is to downgrade my kernel to 5.0.  I do not experience 
the problem there.

Thanks

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

Title:
  5.3.0-46-generic - i915 - frequent GPU hangs  / resets rcs0

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

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

[Bug 1874830] [NEW] install fails on grub install

[rich little]

Public bug reported:

wont install on any partition.
attempts to install on /dev/sda even though the install is going to /dev/sdb
for info, sdb is an ssd drive that I had 18.04 on previously.
/dev/sdb checks out as OK.
this is an install of 20.04 LTS

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
Date: Fri Apr 24 07:55:33 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash ---
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  install fails on grub install

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

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

[Bug 1008197] Re: Cinnamon desktop freeze - no mouse actions, keyboard atl, ctrl, del works

[Rich Wales]

It happened to me again just now.  I ssh'ed to the computer and did a
reboot, but even after the ssh service had shut down, the computer was
still hung with a frozen screen saver, and I still had to do a hardware
reset in order to get it going again.

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

Title:
  Cinnamon desktop freeze - no mouse actions, keyboard atl,ctrl, del
  works

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

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

[Bug 1869632] Re: AppArmor profile denied access to /etc/mdns.allow

[Rich McAllister]

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

** This bug has been marked a duplicate of bug 1869629
   please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

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

Title:
  AppArmor profile denied access to /etc/mdns.allow

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

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

[Bug 1869629] Re: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

[Rich McAllister]

This problem is indeed somewhat pervasive, I also filed bug 1869632 on
cups-browsed doing the same thing, for the same reason. I suspect more
will pop up. I don't think libnss_mdns is too widely used, most people
would use libnss_mdns_minimal.  I only have to use libnss_mdns because
my ISP is insane. If this bug were fixed by adding /etc/mdns.allow to
/etc/apparmor.d/abstractions/mdns bug 1869632 would be fixed as well
(I've verified this by patching it on my system.)

Not sure why /etc/apparmor.d/abstractions/mdns contains
/etc/nss_mdns.conf, though: libnss_mdns.so.2 doesn't refer to that file
(it appears to be used in the NetBSD implementation?)

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

Title:
  please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

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

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

[Bug 1869632] Re: AppArmor profile denied access to /etc/mdns.allow

[Rich McAllister]

Bug also exists in package version 1.27.3-1 (current version in focal)

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

Title:
  AppArmor profile denied access to /etc/mdns.allow

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

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

[Bug 1869632] [NEW] AppArmor profile denied access to /etc/mdns.allow

[Rich McAllister]

Public bug reported:

Many messages in syslog

audit: type=1400 audit(1585521672.468:40): apparmor="DENIED"
operation="open" profile="/usr/sbin/cups-browsed" name="/etc/mdns.allow"
pid=1323 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0
ouid=0

This is caused by configuring libnss-mdns to resolve local names, with
/etc/nsswitch.conf containing

hosts:  files mdns [NOTFOUND=return] dns myhostname

libnss-mnds reads /etc/mdns.allow to find which domains to resolve, but
/etc/apparmor.d/usr.sbin.cups-browsed does not allow access.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups-browsed 1.25.11-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
CupsErrorLog:
 
CurrentDesktop: XFCE
Date: Sun Mar 29 15:48:11 2020
InstallationDate: Installed on 2019-10-24 (157 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Papersize: letter
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_c53lph@/vmlinuz-5.3.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_c53lph ro quiet splash
SourcePackage: cups-filters
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  AppArmor profile denied access to /etc/mdns.allow

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

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

[Bug 1869629] Re: AppArmor denied access to /etc/mdns.allow to cronyd

[Rich McAllister]

As a workaround, hanging /etc/apparmor.d/local/usr.sbin.chronyd to
include

   /etc/mdns.allow r,

and reloading with

sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.chronyd

made it shut up.

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

Title:
  AppArmor denied access to /etc/mdns.allow to cronyd

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

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

[Bug 1869629] [NEW] AppArmor denied access to /etc/mdns.allow to cronyd

[Rich McAllister]

Public bug reported:

Many repetitions of

audit: type=1400 audit(1585517168.705:63): apparmor="DENIED"
operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow"
pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=123
ouid=0

in log.  I use libnss-mdns for .local name resolution, so
/etc/nsswitch.conf contains

hosts:  files mdns [NOTFOUND=return] myhostname dns

and /etc/mnds.allow contains the domains to resolve with mDNS (in may
case, "local." and "local"; see /usr/share/doc/libnss-mdns/README.html.)

Presumably cronyd calls a gethostbyX() somewhere, thus eventually
trickling down through the name service switch and opening
/etc/mdns.allow, which the AppArmor profile in the chrony package does
not allow.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chrony 3.5-6ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
Date: Sun Mar 29 15:02:39 2020
InstallationDate: Installed on 2020-03-26 (3 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200326)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: chrony
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Summary changed:

- AppArmor denied accss to /etc/mdns.allow to cronyd 
+ AppArmor denied access to /etc/mdns.allow to cronyd

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

Title:
  AppArmor denied access to /etc/mdns.allow to cronyd

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

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

[Bug 1867036] Re: Focal Fossa : chronyd unable to sync system clock

[Rich McAllister]

Looking into this, it seems the problem is that /usr/lib/systemd/scripts
/chronyd-starter.sh expects to be able to check for the cap_sys_time
capability by grepping the output of "capsh --print" for
"^Current.*cap_sys_time".  However, in Focal the output of "capsh
--print" for a root process is just "Current: =ep". I suspect this is a
linux kernel tools change, as on an eoan system with linux 5.3.0, "sudo
capsh --print" has all the capabilities listed in Current:, which is
what the starter script expects.

andol's dropin makes capsh output "Current: =ep cap_sys_time+i" which
the grep matches so all is fine. Not sure that's the right fix, though.
(It would help if I knew what "Current: =ep" is supposed to mean.

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

Title:
  Focal Fossa : chronyd unable to sync system clock

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

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

[Bug 1867971] [NEW] gsettings dependency is problematic

[Rich Morin]

Public bug reported:

A current discussion on orca-list indicates that some blind users are
finding Orca's use of gsettings to be problematic:

The most accessible Linux version to use with Orca?
https://mail.gnome.org/archives/orca-list/2020-March/msg00233.html

Here are some relevant snippets:

> ubuntu certainly fails here, the developers locked down orca
configuration attaching it to gsettings and making it impossible to
configure inside orca.

> You can't modify orca configuration settings in ubuntu-mate and save
those modifications.  You have to use gsettings to get at orca
configuration and change them so they're saved.  Garden variety ubuntu
in 19.10 does the same thing.  In earlier versions of ubuntu this was
not the case, you could make your changes inside orca and save those
changes.

> You never heard of gsettings before since using it is about as complex
as editing a windows registry.  The gsettings along with dconf-editor
controls the configuration on graphical user interface systems other
configuration files you might find in certain directories does not.  In
the case of ubuntu 19.10 orca got strait jacketed into gsettings.  This
was not the case in earlier ubuntu versions though.

> I tried installing ubuntu 19.10 a few minutes ago the desktop version
since I couldn't get a download url for ubuntu-mate.org and couldn't
even bring up orca and this was after I verified the download.  That
cured me of ubuntu I'm pretty sure permanently.  running alt-super-s
didn't work and alt-f2 orca also failed and even alt-f2 screen-reader
failed as well.  I waited until all disk action had stopped to run those
commands too.

** Affects: orca (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/1867971

Title:
  gsettings dependency is problematic

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

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

[Bug 1854589] Re: Windows move to different monitor when multiple monitors turned off and back on

[Rich Wales]

Noting once again that I am still having this problem.  I am worried
because no one seems to be working on it or have any idea how to work
around it (other than by disconnecting the cable from my computer to the
back of my TV when I'm not playing something on the TV screen).

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

Title:
  Windows move to different monitor when multiple monitors turned off
  and back on

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

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

[Bug 1008197] Re: Cinnamon desktop freeze - no mouse actions, keyboard atl, ctrl, del works

[Rich Wales]

I am still occasionally experiencing this problem (or something that
looks just like it) in 2020.  In my case, the freezing happens only when
the Cinnamon screen saver is active -- the date/time on the screen saver
stops advancing, and no keys or mouse clicks will revive it -- even
selectively killing processes on the computer via a remote login (ssh)
doesn't work -- I end up with no choice but to do a hardware reset.

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

Title:
  Cinnamon desktop freeze - no mouse actions, keyboard atl,ctrl, del
  works

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

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

[Bug 1854589] Re: Windows move to different monitor when multiple monitors turned off and back on

[Rich Wales]

Still having this problem.  I'm temporarily working around it by
disconnecting the HDMI cable from the computer to the back of the TV
when I'm not actually playing something on the larger screen, but this
is clearly not acceptable as a long-term solution.

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

Title:
  Windows move to different monitor when multiple monitors turned off
  and back on

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

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

Re: [Bug 1855477] Re: gnome-control-center will not let me paste in a password from my password manger

[Rich Hart]

I'm using Xorg.  And the password manager is xkeepass ( and keepass2 )

On 12/9/19 11:49 AM, Jamie Strandboge wrote:
> Thank you for using Ubuntu and reporting a bug.
>
> Are you using wayland or Xorg for your desktop session? What password
> manager are you using?
>
> ** Information type changed from Private Security to Public Security
>

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

Title:
  gnome-control-center will not let me paste in a password from my
  password manger

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

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

[Bug 1854589] Re: Windows move to different monitor when multiple monitors turned off and back on

[Rich Wales]

I don't think Compiz is relevant here.  My computer isn't running Compiz
— its display manager is GDM3 as best I can tell.  (ri...@richw.org, the
original reporter of this bug)

** Package changed: compiz (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Windows move to different monitor when multiple monitors turned off
  and back on

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

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

[Bug 1854589] Re: Windows move to different monitor when multiple monitors turned off and back on

[Rich Wales]

I note this bug has been classified as affecting Compiz.  However, as
best I can tell, Compiz is not running on my computer.  /etc/X11
/default-display-manager on my computer contains the value
"/usr/sbin/gdm3".

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

Title:
  Windows move to different monitor when multiple monitors turned off
  and back on

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

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

[Bug 1854589] [NEW] Windows move to different monitor when multiple monitors turned off and back on

[Rich Wales]

Public bug reported:

Ubuntu 19.10, gdm3 3.34.1-1ubuntu1, cinnamon 4.0.10-2, cinnamon-
screensaver 4.0.3-1, nvidia-driver 435.21-0ubuntu2.

I have a TV set connected to my computer as a second monitor (for
displaying YouTube videos, etc.).

When I turn off both my main monitor and the TV for the night, and turn
them back on in the morning, I often find that the windows I had left
open on the main monitor (email, browser, xterm, etc.) have moved from
the main monitor to the TV and need to be moved back individually to the
main monitor (via the "move to the other monitor" function on the
taskbar icons).

This doesn't always happen -- sometimes the windows show up on the main
monitor where I left them the night before, and sometimes not.  Maybe
50-50, one way or the other.

The main monitor is configured (in the Display settings) as the primary
monitor, and the taskbar panel remains on the main monitor -- and when I
wake up the screen saver to unlock it, the password dialogue always
shows up on the main monitor -- but the windows may end up on either
device after I've unlocked.

It doesn't appear to make any difference what order I turn the monitor
and the TV off/on.  In particular, I've conscientiously turned off the
TV before locking the screen and turning off the monitor, and then
turned on the monitor and unlocked the screen before turning the TV back
on, but the windows frequently still end up on the TV instead of the
main monitor.

I would like to somehow flag the windows so that they will stay put on
my main monitor when I turn things off at night and turn them back on in
the morning -- or, even better, I would like the windows to remain
associated with the same device and not move around on their own.

** Affects: compiz (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/1854589

Title:
  Windows move to different monitor when multiple monitors turned off
  and back on

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

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

[Bug 1821533] Re: drm fails to accept edid version 2.4

[Rich Drewes]

As I wrote earlier, the EDID file I used came from edid-generator github
and it is called 1920x1080.bin . You want me to google that for you?

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

Title:
  drm fails to accept edid version 2.4

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

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

[Bug 1821533] Re: drm fails to accept edid version 2.4

[Rich Drewes]

I'm not sure this is a Linux problem. It may be that the panel is
reporting bad EDID data. I haven't investigated enough to say for sure.
In any case none of the more recent Linux releases fixed the problem in
my tests. Also no other open source OSs were able to deal with the
onboard LCD panel either. (That may have changed since I tested.)

If you were interested, you might be able to patch the firmware on the
onboard panel to provide different EDID information. I looked into doing
this and there are some tutorials out there. However, it's possible you
could do something wrong and end up worse than you were before. If you
learn something new, please post it here. In particular if you find some
open source OS that can configure this display properly at full
resolution without resorting to forcing EDID information please say so
here.

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

Title:
  drm fails to accept edid version 2.4

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

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

[Bug 1821533] Re: drm fails to accept edid version 2.4

[Rich Drewes]

I was able to display on an external monitor, or the internal monitor,
but not both simultaneously. I didn't spend too much time trying to
solve the problem and now the laptop is with a family member at another
location. If you work on this issue and find a solution please post it
here.

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

Title:
  drm fails to accept edid version 2.4

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

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

[Bug 1825690] [NEW] Settings Panel _> Application Style -> Windows Decorations is Non-Usable

[Rich]

Public bug reported:

Settings Panel -> Application Style -> Windows Decorations is Non-Usable
and has been bugged since beta. Upgrade from beta to release Kubuntu
19.04. Panel looks like this when selected:
https://i.imgur.com/jLSysQS.jpg

rich@tworobots:~$ lsb_release -rd
Description:Ubuntu 19.04
Release:19.04

rich@tworobots:~$ apt-cache policy systemsettings
systemsettings:
  Installed: 4:5.15.4-0ubuntu1
  Candidate: 4:5.15.4-0ubuntu1
  Version table:
 *** 4:5.15.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages
100 /var/lib/dpkg/status

Expected to see the panel, received the screenshot above instead.

** Affects: kde-systemsettings (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/1825690

Title:
  Settings Panel _> Application Style -> Windows Decorations is Non-
  Usable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-systemsettings/+bug/1825690/+subscriptions

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

[Bug 1790966] Re: Electron apps segfault on glibc 2.28 (cosmic)

[Mark Rich via ubuntu-bugs]

@aM, your solution worked for me too.  I now have Crashplan working.

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

Title:
  Electron apps segfault on glibc 2.28 (cosmic)

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

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

[Bug 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly

[Rich Fiekowsky]

I also experienced "A stop job is running for Session c2 ... / 1min 30
s)". Newbies (like me) might need to know that in a fresh install of
Ubuntu 16.04, the file /etc/systemd/system.conf has (almost) all lines
commented out with a # . So, in addition to changing the number in the
line #DefaultTimeoutStopSec=90 , one must also remove the # at the
beginning of the line, to uncomment it. Also, before I changed the conf
file, I had fast restarts sometimes by logging out before I restarted.

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

Title:
  reduce 90s session kill timeout if the session does not shutdown
  cleanly

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

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

[Bug 1821533] Re: drm fails to accept edid version 2.4

[Rich Drewes]

** Summary changed:

- failure to detect and use Intel 620 graphics pci id 3ea0
+ drm fails to accept edid version 2.4

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

Title:
  drm fails to accept edid version 2.4

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I was able to get the onboard LCD panel working, finally, as follows:

First I extracted the edid file from the LCD panel using get-edid and
putting that in /lib/firmware/edid/ncp.bin, and then forcing the kernel
to take that using the kernel boot option
drm.edid_firmware=edid/ncp.bin. This failed, and dmesg said that the
ncp.bin file had a "bad block 0". Possibly that means that nothing
within Linux can accept edid version 2.4?

Then I grabbed a generic 1920x1080.bin edid file from edid-generator
github and put that one in /lib/firmware/edid/ and used that one with
drm.edid_firmware and the display worked for the first time!

I am still unsure why Linux couldn't accept the version 2.4 edid data
from the LCD panel.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Below is the EDID information from the onboard panel. Why can't drm/i915
deal with it?


guest@guest-ZenBook-UX431FA:~$ sudo get-edid | parse-edid 
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
1 potential busses found: 5
128-byte EDID successfully retrieved from i2c bus 5
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
Identifier ""
ModelName ""
VendorName "NCP"
# Monitor Manufactured week 1 of 2018
# EDID version 2.4
# Digital Display
DisplaySize 310 170
Gamma 2.20
Option "DPMS" "false"
Modeline"Mode 0" 138.50 1920 1968 2000 2080 1080 1083 1088  
+hsync -vsync 
EndSection

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Correction: last message should read "Why is the driver/module expecting
EDID major version *1* and getting *2*?

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I think the problem is that the laptop's onboard LCD panel is reporting
EDID data with version 2 and the i915 driver can only deal with version
1 at the moment. How can this be fixed?

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Progress! Based on information in dmesg, pasted in at the end of this
message, I thought maybe the graphics device was found OK but the laptop
was trying to drive an external monitor instead of the onboard display.
Sure enough, when I boot without nomodeset option and with an external
HDMI monitor attached the system does display to the external monitor
with proper 1920x1080 resolution.

What does the "EDID is invalid:" message mean? Why is the driver/module
expecting EDID major version 2 and getting 1? Does this have to do with
the version of kbl_dmc firmware loaded to the graphics device?


guest@guest-ZenBook-UX431FA:~$ dmesg | egrep  "drm|i915"
[3.196687] fb: switching to inteldrmfb from EFI VGA
[3.196881] [drm] Replacing VGA console driver
[3.210304] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[3.210306] [drm] Driver supports precise vblank timestamp query.
[3.212814] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[3.214857] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
[3.228865] [drm] EDID has major version 2, instead of 1
[3.236620] [drm] EDID has major version 2, instead of 1
[3.240878] [drm] EDID has major version 2, instead of 1
[3.244590] [drm] EDID has major version 2, instead of 1
[3.244595] i915 :00:02.0: eDP-1: EDID is invalid:
[3.244597] [drm] EDID has major version 2, instead of 1
[3.290049] [drm] Initialized i915 1.6.0 20180514 for :00:02.0 on minor 0
[3.326674] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[3.356268] fbcon: inteldrmfb (fb0) is primary device
[4.724973] i915 :00:02.0: fb0: inteldrmfb frame buffer device

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Is it known whether any machines with Intel Graphics 620 with pci id
0x3ea0 have functioning graphics with any version of Ubuntu?

This is relatively new hardware, but it seems unlikely that I am the
only one in the world who has tried this combination, and if other
people with different machines with the same 0x3ea0 pci id do have
working graphics then that would suggest that the problem is some quirk
of my particular ASUS UX431FA (perhaps some initialization timing quirk
or hardware/design bug that is worked-around for the Windows 10
installation that came with the system).

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I tried booting 4.18.0-16-generic (which i believe is the hwe kernel)
with kernel option drm.debug=0xff. When the system came up of course it
had no video but I could ssh in and grab the dmesg output, which is
attached to this message. dmesg had many drm-related debugging messages
and i915-related messages, but none of it was particularly helpful to me
yet.

** Attachment added: "dmesg-drm.debug.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821533/+attachment/5249204/+files/dmesg-drm.debug.txt

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Just in case my addition of i915 to initramfs was causing a problem with
drm-intel-next, I removed i915 from initramfs and repeated the test. The
result was the same, no video after a certain point in the boot process
with nomodeset using the drm-intel-next kernel as in #8.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I installed kernel and modules and headers from
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/
and rebooted without nomodeset option. Same behavior: after the "loading
initramfs" message the screen blanks and never comes back.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Based on a lead from an Arch Linux blog post, I tried adding the i915
module to the initramfs. This could possibly lead to earlier
initialization of the graphics device and it also seems consistent with
the DragonFlyBSD "probe early" patch I linked to in my initial bug
report which may have fixed the graphics problem in DragonFlyBSD (I
cannot tell for certain if the graphics problem was fixed there due to
another, unrelated problem, but the fix definitely allowed the boot to
proceed further and the text did seem to switch to full screen
resolution).

The update-initramfs operation failed on the v5.1-rc2 kernel because of
two missing firmware files.

The update-initramfs operation succeeded on the 4.x kernels I had
installed, one of which is the hwe kernel (I believe). I verified the
presence of the i915 module in the initramfs for those kernels using
lsinitramfs. Unfortunately, booting with i915 in the initramfs on the
4.x kernels and without nomodeset did not solve the problem.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Also: booting without nomodeset kernel option for v5.1-rc2 kernel leads
to black screen, just as before. At that point the system cannot even be
switched to text console with ctrl-alt-Fn.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Thanks for your help.

Unfortunately, no change after installing v5.1-rc2: Still stuck in
800x600 after booting with nomodeset kernel option.

Added kernel-bug-exists-upstream and marked confirmed.

dmesg output attached.

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821533/+attachment/5249132/+files/dmesg

** Tags added: kernel-bug-exists-upstream

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

** Changed in: linux-hwe (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/1821533

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

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

[Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

** Description changed:

  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware enablement
  packages does not solve problem: the system will still only boot with
  nomodeset kernel option, and X is limited to using fbdev module at
  800x600 resolution.
  
  The "modesetting" driver appears to be loaded and then unloaded during X
  startup. Trying to force intel module from xserver-xorg-video-intel by
  setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does not
  help.
  
  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.
  
  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
- DragonFlyBSD (see bug report 3167 here
- https://bugs.dragonflybsd.org/issues/3167). I have verified that the
- patch referenced in that bug report does make DragonFlyBSD boot past the
- video problem which I think is the same problem I experience with every
- Linux OS I have tried including Ubuntu.
+ DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
+ verified that the patch referenced in that bug report does make
+ DragonFlyBSD boot past the video problem which I think is the same
+ problem I experience with every Linux OS I have tried including Ubuntu.
  
  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  
  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver
  
  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
+  Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  

[Bug 1821533] [NEW] failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Public bug reported:

Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
install (also 18.10, also 19.04 daily) leads to black screen. Adding
"nomodeset" to kernel boot parameter gives 800x600 video only and
permits installing OS to disk. Applying updates and hardware enablement
packages does not solve problem: the system will still only boot with
nomodeset kernel option, and X is limited to using fbdev module at
800x600 resolution.

The "modesetting" driver appears to be loaded and then unloaded during X
startup. Trying to force intel module from xserver-xorg-video-intel by
setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does not
help.

The PCI id for the graphics device appears to be 3ea0 and the place
where that might be relevant is the i915 module.

This problem occurs with every other Linux release I have tried
including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
The one open source OS that I have found where it might be fixed is
DragonFlyBSD (see bug report 3167 here
https://bugs.dragonflybsd.org/issues/3167). I have verified that the
patch referenced in that bug report does make DragonFlyBSD boot past the
video problem which I think is the same problem I experience with every
Linux OS I have tried including Ubuntu.

guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04

guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
ii  linux-generic-hwe-18.044.18.0.16.66 
amd64Complete Generic Linux kernel and headers
ii  linux-headers-generic-hwe-18.044.18.0.16.66 
amd64Generic Linux kernel headers
ii  linux-image-generic-hwe-18.04  4.18.0.16.66 
amd64Generic Linux kernel image
ii  linux-signed-generic-hwe-18.04 4.18.0.16.66 
amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1 
amd64X.Org X server -- fbdev display driver

Expected result: Video at 1920x1080
Actual result: Video limited to 800x600

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 24 10:36:51 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
InstallationDate: Installed on 2019-03-24 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX431FA.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX431FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX431FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic resolution ubuntu

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

Title:
  failure to detect and use Intel 620 

[Bug 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks

[rich painter]

I have this same problem for some time and on the latest update too.
all of the discs affected are used in a zfs zpool.

uname -a 
Linux PEI-Server 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

cat /sys/module/zfs/version
0.7.5-1ubuntu16.4

I have a total of 6 discs split equally across 2 esata port multipliers.
All are part a a single raidz2 pool.

Zillions of these errors:
Mar  3 22:04:48 PEI-Server systemd[1]: 
dev-disk-by\x2dpath-pci\x2d:07:00.0\x2data\x2d1\x2dpart1.device: Dev 
dev-disk-by\x2dpath-pci\x2d:07:00.0\x2data\x2d1\x2dpart1.device appeared 
twice with different sysfs paths 
/sys/devices/pci:00/:00:1c.2/:07:00.0/ata3/host2/target2:0:0/2:0:0:0/block/sdd/sdd1
 and 
/sys/devices/pci:00/:00:1c.2/:07:00.0/ata3/host2/target2:1:0/2:1:0:0/block/sde/sde1

I have lots of detailed data if anyone wants to see it.

It would REALLY be nice if a fix trickled down soon...

thanks
rich

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

Title:
  /dev/disk/by-path not properly populated for (e)SATA port multiplier
  disks

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

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

[Bug 1817308] Re: GhostScript Update causes Blue Background

[Rich via ubuntu-bugs]

Update Manager came through with the update a couple of hours ago -
Fixed the blue background on HP Photosmart B210. Thanks for quick work
Guys

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

Title:
  GhostScript Update causes Blue Background

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

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

Re: [Bug 1806067] Re: package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.5 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1

[Rich Stillman]

Interesting. I never manually changed the configuration. If any conversion
was done, it was by the installation. There may be a bug after all.
  Thanks
  Rich

On Mon, Dec 3, 2018 at 4:45 AM Karl Stenerud 
wrote:

> Hi Rich,
>
> Thanks for reporting this. It looks from the logs to be a configuration
> issue. I'm guessing the netmask and IP address got mixed up in the
> config?
>
>   bind failed on port 137 socket_addr = 192.255.255.255.
> Failed to open nmb bcast socket on interface 192.255.255.255 for port
> 137.  Error was Cannot assign requested address
>   STATUS=daemon failed to start: NMBD failed when creating subnet lists,
> error code 13
>
>
> ** Changed in: samba (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1806067
>
> Title:
>   package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.5 failed to
>   install/upgrade: installed samba package post-installation script
>   subprocess returned error exit status 1
>
> Status in samba package in Ubuntu:
>   Invalid
>
> Bug description:
>I was able to partially mitigate the bug by replacing smb.conf with
>   the pre-upgrade version. That allowed access to drives and printers
>   from a Windows 7 computer, but did not help with a file share attached
>   from a fully patched Windows 10 computer. The Win 10 upgrade may be at
>   fault for that, however.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 18.04
>   Package: samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.5
>   ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
>   Uname: Linux 4.15.0-39-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   Date: Tue Nov 27 09:20:07 2018
>   ErrorMessage: installed samba package post-installation script
> subprocess returned error exit status 1
>   InstallationDate: Installed on 2017-11-23 (371 days ago)
>   InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
>   Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal,
> 3.6.7-1~18.04
>   PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
> 2.7.15~rc1-1
>   RelatedPackageVersions:
>dpkg 1.19.0.5ubuntu2.1
>apt  1.6.6
>   SambaServerRegression: Yes
>   SmbConfIncluded: Yes
>   SmbLog:
>
>   SourcePackage: samba
>   TestparmExitCode: 0
>   Title: package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.5 failed to
> install/upgrade: installed samba package post-installation script
> subprocess returned error exit status 1
>   UbuntuFailedConnect: Yes
>   UpgradeStatus: Upgraded to bionic on 2018-09-12 (78 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1806067/+subscriptions
>
>

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

Title:
  package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.5 failed to
  install/upgrade: installed samba package post-installation script
  subprocess returned error exit status 1

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

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

[Bug 1806067] [NEW] package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.5 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1

[Rich Stillman]

Public bug reported:

 I was able to partially mitigate the bug by replacing smb.conf with the
pre-upgrade version. That allowed access to drives and printers from a
Windows 7 computer, but did not help with a file share attached from a
fully patched Windows 10 computer. The Win 10 upgrade may be at fault
for that, however.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.5
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Tue Nov 27 09:20:07 2018
ErrorMessage: installed samba package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2017-11-23 (371 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:
 
SourcePackage: samba
TestparmExitCode: 0
Title: package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.5 failed to install/upgrade: 
installed samba package post-installation script subprocess returned error exit 
status 1
UbuntuFailedConnect: Yes
UpgradeStatus: Upgraded to bionic on 2018-09-12 (78 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.5 failed to
  install/upgrade: installed samba package post-installation script
  subprocess returned error exit status 1

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

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

[Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Rich McAllister]

ExecStart twice is what I meant (this is the way to replace the command
from the base definition instead of adding another command to the list,
see the systemd.unit man page for details.)

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

Title:
  ureadahead reports relative path errors in journalctl output

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

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

Re: [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Rich McAllister]

No, ExecStart twice is correct. This is the way systemd overrides
work; normally a value for a keyword  adds to the list of  values from
the base .service definition.  I don't want that, I want to replace
it.  The special ExecStart=   with no value tells systemd to reset the
base value to empty, then the second one starts a new list thus
replacing the old command.  (This is all explained in the systemd.unit
man page.)

I should tell you that I no longer use this workaround, since after a
fair amount of working with and investigating ureadahead (I thought I
might actually contribute a permanent fix)  I decided that ureadahead
is useless in my configuration, since I only reboot after a kernel
update anyway, and ureadahead only can ever help on the second and
subsequent boots of the same config (most any changes to /etc will
cause ureadahead to rescan at the the next boot.)  So I have just
purged ureadahead on all my systems.
On Sat, Sep 29, 2018 at 5:39 AM midenok <1579...@bugs.launchpad.net> wrote:
>
> Why it contains ExecStart 2 times?
>
> [Service]
> ExecStart=
> ExecStart=/sbin/ureadahead -q
>
> Did you mean ExecStop?
>
> [Service]
> ExecStop=
> ExecStart=/sbin/ureadahead -q
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1579580
>
> Title:
>   ureadahead reports relative path errors in journalctl output
>
> Status in ureadahead package in Ubuntu:
>   Confirmed
>
> Bug description:
>   ureadahead reports relative path errors in my journalctl output.
>
>   This is currently 4368 lines of useless annoyances in my logs.
>
>   To see if you have this problem, run: journalctl -b | grep ureadahead
>   | grep relative | wc -l
>
>   Thanks
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: ureadahead 0.100.0-19
>   ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
>   Uname: Linux 4.4.0-22-generic x86_64
>   NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   Date: Sun May  8 15:55:18 2016
>   InstallationDate: Installed on 2016-04-04 (34 days ago)
>   InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
> (20160325)
>   ProcEnviron:
>TERM=linux
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: ureadahead
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions

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

Title:
  ureadahead reports relative path errors in journalctl output

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

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

[Bug 1786910] Re: Latest patch breaks command line 'restart all'

[Rich Sutton]

This is also affecting my company. We use monit on all boxes for process
management and have had to pin on a downrev version.

Do we know if the package maintainer knows that this is an issue? Can we
get some confirmation of that?

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

Title:
  Latest patch breaks command line 'restart all'

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

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

Re: [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Rich McAllister]

Be aware the messages will come back next time you boot after
upgrading a package that touches something in /etc, which will trigger
another scan by ureadahead.  Better is the workaround I gave back in
#9, but really what I recommend is just purge ureadahead.  ureadahead
only ever can help the second (and subsequent) time one boots after
updating the system, and these days I never reboot unless I have
updated, since suspend works for desktops/laptops and who reboots
servers if you don't have to?

Rich
On Sat, Sep 22, 2018 at 8:54 AM Anders Hall  wrote:
>
> Thanks, workaround in #19 seem to have removed (thousands of) these
> messages.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1579580
>
> Title:
>   ureadahead reports relative path errors in journalctl output
>
> Status in ureadahead package in Ubuntu:
>   Confirmed
>
> Bug description:
>   ureadahead reports relative path errors in my journalctl output.
>
>   This is currently 4368 lines of useless annoyances in my logs.
>
>   To see if you have this problem, run: journalctl -b | grep ureadahead
>   | grep relative | wc -l
>
>   Thanks
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: ureadahead 0.100.0-19
>   ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
>   Uname: Linux 4.4.0-22-generic x86_64
>   NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   Date: Sun May  8 15:55:18 2016
>   InstallationDate: Installed on 2016-04-04 (34 days ago)
>   InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
> (20160325)
>   ProcEnviron:
>TERM=linux
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: ureadahead
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions

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

Title:
  ureadahead reports relative path errors in journalctl output

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

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

[Bug 1792938] Re: PHP 7.2.7 contains various security issues.

[Rich James]

** Package changed: ubuntu => php-defaults (Ubuntu)

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

Title:
  PHP 7.2.7 contains various security issues.

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

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

[Bug 1587204] Re: Spams motd with "proxy ... looks invalid"

[Rich McAllister]

Similarly, I have set in apt.conf.d

Acquire::https::Proxy "DIRECT";

(because apt-cacher-ng can't cache https) and I get

proxy 'DIRECT' looks invalid

The regexp definitely needs to be broadened.

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

Title:
  Spams motd with "proxy ... looks invalid"

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

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

[Bug 1779401] [NEW] Cacti 1.1.38 fails to display graphs and acts erratically

[Rich James]

Public bug reported:

Cacti fails to show many graphs, and also has problems reindexing.
The error given is: 
 sizeof(): Parameter must be an array or an object that implements Countable in 
/usr/share/cacti/site/lib/utility.php on line 541

Fix is by patch: 
diff --git a/lib/utility.php b/tmp/utility.php
index 6488d98..306e6e4 100644
--- a/lib/utility.php
+++ b/tmp/utility.php
@@ -459,7 +459,7 @@ function push_out_data_input_method($data_input_id) {
  */
 function poller_update_poller_cache_from_buffer($local_data_ids, 
&$poller_items) {
/* set all fields present value to 0, to mark the outliers when we are 
all done */
-   $ids = array();
+   $ids = '';
if (sizeof($local_data_ids)) {
$count = 0;
foreach($local_data_ids as $id) {
@@ -538,7 +538,7 @@ function 
poller_update_poller_cache_from_buffer($local_data_ids, &$poller_items)
}

/* remove stale records FROM the poller cache */
-   if (sizeof($ids)) {
+   if (strlen($ids)) {
db_execute("DELETE FROM poller_item WHERE present=0 AND 
local_data_id IN ($ids)");
} else {
/* only handle explicitely given local_data_ids */

** 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/1779401

Title:
  Cacti 1.1.38 fails to display graphs and acts erratically

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

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

[Bug 1776931] Re: ruby-rails 2:4.2.10 does not utilise PGSQL 10 sequence model

[Rich James]

** Also affects: redmine (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- ruby-rails 2:4.2.10 does not utilise PGSQL 10 sequence model
+ ruby-rails 2:4.2.10 is not compatible with PostgreSQL 10 (sequence handling 
changed since 9.x)

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

Title:
  ruby-rails 2:4.2.10 is not compatible with PostgreSQL 10 (sequence
  handling changed since 9.x)

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

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

[Bug 1776931] Re: ruby-rails 2:4.2.10 does not utilise PGSQL 10 sequence model

[Rich James]

Cleaner details found at: https://help.heroku.com/WKJ027JH/rails-error-
after-upgrading-to-postgres-10

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

Title:
  ruby-rails 2:4.2.10 does not utilise PGSQL 10 sequence model

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

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

[Bug 1776931] [NEW] ruby-rails 2:4.2.10 does not utilise PGSQL 10 sequence model

[Rich James]

Public bug reported:

>From PostgreSQL v10, the sequence object has altered, moving attributes such 
>as "increment_by" and "min_value" to the pg_sequences catalog, rather than 
>holding them in the sequence itself.
The rails package on Ubuntu 18.04 does not seem to have caught up with this.

The error was encountered using the community supported script to
migrate Trac projects to Redmine.

Error text given was:
ActiveRecord::StatementInvalid: PG::UndefinedColumn: ERROR:  column 
"increment_by" does not exist
LINE 1: ...sues_id_seq"', (SELECT COALESCE(MAX("id")+(SELECT increment_...
 ^
:   SELECT setval('"public"."issues_id_seq"', (SELECT 
COALESCE(MAX("id")+(SELECT increment_by FROM "public"."issues_id_seq"), (SELECT 
min_value FROM "public"."issues_id_seq")) FROM "issues"), false)
/usr/share/redmine/lib/tasks/migrate_from_trac.initial.rake:561:in `migrate'
/usr/share/redmine/lib/tasks/migrate_from_trac.initial.rake:782:in `block (2 
levels) in '

Caused by:
PG::UndefinedColumn: ERROR:  column "increment_by" does not exist
LINE 1: ...sues_id_seq"', (SELECT COALESCE(MAX("id")+(SELECT increment_...
 ^
/usr/share/redmine/lib/tasks/migrate_from_trac.initial.rake:561:in `migrate'
/usr/share/redmine/lib/tasks/migrate_from_trac.initial.rake:782:in `block (2 
levels) in '
Tasks: TOP => redmine:migrate_from_trac

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


** Tags: postgresql rails ruby

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

Title:
  ruby-rails 2:4.2.10 does not utilise PGSQL 10 sequence model

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

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

[Bug 571356] Re: gdbtui shows "dl-debug.c:77: No such file or directory."

[rich painter]

STILL not fixed.

4.4.0-124-generic #148~14.04.1-Ubuntu SMP Thu May 3 07:26:53 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1

any c program compiled with -g and then 
gdb -tui program
set a breakpoint
run

multiple dl-debug.c:74: No such file or directory.
will be produced.

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

Title:
  gdbtui shows "dl-debug.c:77: No such file or directory."

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

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

[Bug 1666166] Re: openafs-modules-dkms 1.6.15-1ubuntu1: openafs kernel module failed to build

[Rich Wales]

The ppa:openafs/stable workaround restored AFS client service to my
machine (which had been lost after I switched to the HWE kernel in early
January 2018).  Currently running openafs-client
1.6.22-3~ppa0~ubuntu16.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/1666166

Title:
  openafs-modules-dkms 1.6.15-1ubuntu1: openafs kernel module failed to
  build

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

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

[Bug 1744946] Re: Special characters change the width of trailing/leading space character in Gedit (and medit)

[Tao Rich]

I filed a bug report with GNOME:

https://bugzilla.gnome.org/show_bug.cgi?id=792832

I added the link to:

Also affects project.

** Bug watch added: GNOME Bug Tracker #792832
   https://bugzilla.gnome.org/show_bug.cgi?id=792832

** Also affects: gedit via
   https://bugzilla.gnome.org/show_bug.cgi?id=792832
   Importance: Unknown
   Status: Unknown

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

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

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

[Bug 1744946] Re: Special characters change the width of trailing/leading space character in Gedit (and medit)

[Tao Rich]

** Description changed:

  If I paste a special character - say from the Character Map - into Gedit
  or medit in Ubuntu 16.04 into the middle of a line, then the space
  characters directly after the special character display with a
- "compressed" character spacing/display until the behaviour is
- "interrupted" by a standard text character.
+ "compressed" character spacing until the behaviour is "interrupted" by a
+ standard text character.
  
  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines with
  the special character problem.
  
  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .
  
  https://askubuntu.com/questions/986258/why-do-special-characters-change-
  spacing-following-space-character-in-gedit-or-m
  
  Please see that post for full details, worked example, and screenshots.
  
  Additional comments:
  
  * As stated above:
  - running Ubuntu 16.04
  
  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0
  
  I am aware that it is thus not strictly a gedit issue, and probably
- affects multiple Gnome editor under multiple Linux variants but Gedit is
- my favourite text editor and Ubuntu is my favourite Linux so I thought I
- would start here.
+ affects multiple Gnome editors under multiple Linux variants - but Gedit
+ is my favourite text editor and Ubuntu is my favourite Linux so I
+ thought I would start here.
  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  
  $ apt-cache policy gedit
  gedit:
-   Installed: 3.18.3-0ubuntu4
-   Candidate: 3.18.3-0ubuntu4
-   Version table:
-  *** 3.18.3-0ubuntu4 500
- 500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.18.3-0ubuntu4
+   Candidate: 3.18.3-0ubuntu4
+   Version table:
+  *** 3.18.3-0ubuntu4 500
+ 500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  $ apt-cache policy medit
  medit:
-   Installed: 1.2.0-2
-   Candidate: 1.2.0-2
-   Version table:
-  *** 1.2.0-2 500
- 500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.2.0-2
+   Candidate: 1.2.0-2
+   Version table:
+  *** 1.2.0-2 500
+ 500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+ 100 /var/lib/dpkg/status

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

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

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

[Bug 1744946] Re: Special characters change the width of trailing/leading space character in Gedit (and medit)

[Tao Rich]

** Tags added: ui

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

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

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

[Bug 1744946] [NEW] Special characters change the width of trailing/leading space character in Gedit (and medit)

[Tao Rich]

Public bug reported:

If I paste a special character - say from the Character Map - into Gedit
or medit in Ubuntu 16.04 into the middle of a line, then the space
characters directly after the special character display with a
"compressed" character spacing/display until the behaviour is
"interrupted" by a standard text character.

So the basic problem result is that the uniform monospacing of
characters gets out of alignment on lines above and below the lines with
the special character problem.

I posted a detailed question on AskUbuntu and the prevailing opinion was that I 
should log a bug report.
Another user with different versions was easily able to reproduce the same 
issue .

https://askubuntu.com/questions/986258/why-do-special-characters-change-
spacing-following-space-character-in-gedit-or-m

Please see that post for full details, worked example, and screenshots.

Additional comments:

* As stated above:
- running Ubuntu 16.04

* This affects:
- Gedit 3.18.3
- medit 1.2.0

I am aware that it is thus not strictly a gedit issue, and probably
affects multiple Gnome editor under multiple Linux variants but Gedit is
my favourite text editor and Ubuntu is my favourite Linux so I thought I
would start here.

$ lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

$ apt-cache policy gedit
gedit:
  Installed: 3.18.3-0ubuntu4
  Candidate: 3.18.3-0ubuntu4
  Version table:
 *** 3.18.3-0ubuntu4 500
500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy medit
medit:
  Installed: 1.2.0-2
  Candidate: 1.2.0-2
  Version table:
 *** 1.2.0-2 500
500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

** Affects: gedit (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/1744946

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

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

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

[Bug 1739878] [NEW] package network-manager-config-connectivity-hostname 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Rich Perry]

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

Public bug reported:

I am using a Hyper-V virtual machine on Windows 10 Pro (1709 build
16299.125), and have received the error in the summary following the
first update after install.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Dec 23 21:40:50 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-12-23 (0 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
IpRoute:
 default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.163 metric 100 
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.163 
 192.168.1.1 dev eth0 proto dhcp scope link src 192.168.1.163 metric 100
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
PackageArchitecture: all
PciNetwork:
 
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
RfKill:
 
SourcePackage: network-manager
Title: package network-manager-config-connectivity-hostname 1.8.4-1ubuntu3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
 eth0ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
 running  1.8.4disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package network-manager-config-connectivity-hostname 1.8.4-1ubuntu3
  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/network-manager/+bug/1739878/+subscriptions

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

Re: [Bug 536766] Re: Personal file sharing preferences dialog does not offer to install needed packages

[Rich Jones]

:-O!

It only took eight years, but we did it folks!

Hooray!
R

On Tue, Dec 5, 2017 at 10:23 AM, Jeremy Bicha  wrote:

> This is finally "fixed" in Ubuntu 18.04 Alpha by having gnome-user-share
> depend on the packages it needs. The depends are not a fully functional
> Apache install but just an Apache binary and a WebDav server.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (645391).
> https://bugs.launchpad.net/bugs/536766
>
> Title:
>   Personal file sharing preferences dialog does not offer to install
>   needed packages
>
> Status in Ayatana Design:
>   Fix Committed
> Status in gnome-user-share package in Ubuntu:
>   Fix Released
>
> Bug description:
>   Binary package hint: nautilus
>
>   What happens -> I open the Personal file sharing preferences dialog via
> system-preferences or via nautilus, and Im told that the network sharing
> feature can not be enabled because the required packages are not on your pc.
>   I, as a tech user, went to synaptic, found the package, looked for its
> recommends and got the functionality.
>   A normal user wont be able to do so, and so a button to install those
> packages is needed for usabilty's sake.
>
>   --
>
>   Desired resolution:
>
>   - Change the "Sharing Options" text in them Nautilus right click folder
> menu to "Local network share"
>   - Change the 'Share' tab title text in the Nautilus 'Properties' window
> to "Local network share"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ayatana-design/+bug/536766/+subscriptions
>

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

Title:
  Personal file sharing preferences dialog does not offer to install
  needed packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/536766/+subscriptions

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

[Bug 1733260] [NEW] package linux-image-4.4.0-98-generic 4.4.0-98.121~14.04.1 failed to install/upgrade: package linux-image-4.4.0-98-generic is not ready for configuration cannot configure (current s

[RICH]

Public bug reported:

I have had problems sent i tried bilbop. I can.t reset any of BILIBOPS 
PERMISSIONS SENT I TRIED IT.
I HAVE NOT BEEN ABLE TO GET INSTRUCTIONS AS TO HOW USE IT .
I WANT HELP OR LEST OUT LAW THE SOFT WARE

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-4.4.0-98-generic 4.4.0-98.121~14.04.1
ProcVersionSignature: Ubuntu 3.13.0-135.184-generic 3.13.11-ckt39
Uname: Linux 3.13.0-135-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
Date: Sun Nov 19 20:41:28 2017
DuplicateSignature: 
package:linux-image-4.4.0-98-generic:4.4.0-98.121~14.04.1:package 
linux-image-4.4.0-98-generic is not ready for configuration  cannot configure 
(current status `half-installed')
ErrorMessage: package linux-image-4.4.0-98-generic is not ready for 
configuration  cannot configure (current status `half-installed')
InstallationDate: Installed on 2017-11-05 (14 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: linux-lts-xenial
Title: package linux-image-4.4.0-98-generic 4.4.0-98.121~14.04.1 failed to 
install/upgrade: package linux-image-4.4.0-98-generic is not ready for 
configuration  cannot configure (current status `half-installed')
UpgradeStatus: Upgraded to trusty on 2017-11-20 (0 days ago)

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


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-4.4.0-98-generic 4.4.0-98.121~14.04.1 failed to
  install/upgrade: package linux-image-4.4.0-98-generic is not ready for
  configuration  cannot configure (current status `half-installed')

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

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

Re: [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware

[rich painter]

no secure boot.
the lenovo t530 is configured for UEFI booting and it works fine.

i dont use unity I hate it. I have always used gnome classic (3).
before the attempt to fix the bluetooth yesterday the bluetooth menu from
the wifi icon on the upper right task bar on Ubuntu 14 gnome 3 at least
showed bluetooth.

i could also start the applications->systems settings-> bluetooth and get
the gnome app and it would at least say there were previous pairing listed
on the left (even tho they would not allow data to be exchanged).

now in that left list it just says "bluetooth is disabled".

I go thru the usual rfkill stuff and all seems OK. the "new driver from
github" reports it is good now in dmesg.

but I cant find any way to "enable"

any ideas?

thanks
rich


On Fri, May 5, 2017 at 4:00 PM, Cruz Fernandez <cruz.fernan...@gmail.com>
wrote:

> Another one, do you have Secure Boot enabled?
>
> Le ven. 5 mai 2017 à 18:55, Cruz Fernandez <cruz.fernan...@gmail.com> a
> écrit :
>
> > Have you tried to use Unity instead of Gnome?
> > Le ven. 5 mai 2017 à 18:49, rich painter <paintere...@gmail.com> a
> écrit :
> >
> >> I did this morning. unfortunately some strange side effect has
> completely
> >> disabled the bluetooth. I dont even see the Ubuntu bluetooth item on the
> >> wifi drop down menu at the upper right on the Gnome desktop. I have
> tried
> >> everything to "enable" bluetooth but to no avail.
> >>
> >> it seems the problem is now worse.
> >>
> >> any ideas?
> >>
> >> thanks
> >> rich
> >>
> >> On Fri, May 5, 2017 at 6:13 AM, Cruz Fernandez <
> cruz.fernan...@gmail.com>
> >> wrote:
> >>
> >> > @painterengr have you tried to download the file from somewhere else?
> >> > https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/
> >> > BCM20702A1-0a5c-21e6.hcd
> >> >
> >> > Hope this is not infringing any legal issues
> >> >
> >> > Le ven. 5 mai 2017 à 04:49, Jesse Sung <1065...@bugs.launchpad.net> a
> >> > écrit :
> >> >
> >> > > @painterengr, sorry #165 is not a reply to your comment. It's just
> >> > > another related bug for lp:1065400 and I added it here for record.
> >> > >
> >> > > --
> >> > > You received this bug notification because you are subscribed to the
> >> bug
> >> > > report.
> >> > > https://bugs.launchpad.net/bugs/1065400
> >> > >
> >> > > Title:
> >> > >   Support for loading Broadcom bluetooth firmware
> >> > >
> >> > > Status in linux package in Ubuntu:
> >> > >   Fix Released
> >> > > Status in linux source package in Precise:
> >> > >   Fix Released
> >> > > Status in linux source package in Quantal:
> >> > >   Fix Released
> >> > > Status in linux source package in Raring:
> >> > >   Fix Released
> >> > > Status in linux source package in Saucy:
> >> > >   Fix Released
> >> > > Status in linux source package in Trusty:
> >> > >   Confirmed
> >> > >
> >> > > Bug description:
> >> > >   Broadcom bluetooth chips require a tool called patchram uploader
> [1]
> >> > >   to load firmware. This applies to at least BCM20702 and BCM43142.
> >> > >   Although some of the devices have an OTPROM that contains required
> >> > >   firmware, but it is found that these devices would not have
> HFP/HSP
> >> > >   support unless a upgraded firmware is loaded via patchram
> uploader.
> >> > >
> >> > >   This tool requires hci device to do the firmware loading, but this
> >> may
> >> > >   cause some race condition between patchram tool and bluetoothd or
> >> > >   something that also works on hci interface.
> >> > >
> >> > >   Also it needs some hooks to make firmware loads after bootup, s3,
> >> s4,
> >> > >   rfkill, and device hotplug events. Implement this loader in kernel
> >> > >   module would make things more easier.
> >> > >
> >> > >   [1] http://marc.info/?l=linux-bluetooth=132039175324993=2
> >> > >
> >> > > To manage notifications about this bug go to:
> >> > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> >> > 1065400/+subscript

Re: [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware

[rich painter]

I did this morning. unfortunately some strange side effect has completely
disabled the bluetooth. I dont even see the Ubuntu bluetooth item on the
wifi drop down menu at the upper right on the Gnome desktop. I have tried
everything to "enable" bluetooth but to no avail.

it seems the problem is now worse.

any ideas?

thanks
rich

On Fri, May 5, 2017 at 6:13 AM, Cruz Fernandez <cruz.fernan...@gmail.com>
wrote:

> @painterengr have you tried to download the file from somewhere else?
> https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/
> BCM20702A1-0a5c-21e6.hcd
>
> Hope this is not infringing any legal issues
>
> Le ven. 5 mai 2017 à 04:49, Jesse Sung <1065...@bugs.launchpad.net> a
> écrit :
>
> > @painterengr, sorry #165 is not a reply to your comment. It's just
> > another related bug for lp:1065400 and I added it here for record.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1065400
> >
> > Title:
> >   Support for loading Broadcom bluetooth firmware
> >
> > Status in linux package in Ubuntu:
> >   Fix Released
> > Status in linux source package in Precise:
> >   Fix Released
> > Status in linux source package in Quantal:
> >   Fix Released
> > Status in linux source package in Raring:
> >   Fix Released
> > Status in linux source package in Saucy:
> >   Fix Released
> > Status in linux source package in Trusty:
> >   Confirmed
> >
> > Bug description:
> >   Broadcom bluetooth chips require a tool called patchram uploader [1]
> >   to load firmware. This applies to at least BCM20702 and BCM43142.
> >   Although some of the devices have an OTPROM that contains required
> >   firmware, but it is found that these devices would not have HFP/HSP
> >   support unless a upgraded firmware is loaded via patchram uploader.
> >
> >   This tool requires hci device to do the firmware loading, but this may
> >   cause some race condition between patchram tool and bluetoothd or
> >   something that also works on hci interface.
> >
> >   Also it needs some hooks to make firmware loads after bootup, s3,  s4,
> >   rfkill, and device hotplug events. Implement this loader in kernel
> >   module would make things more easier.
> >
> >   [1] http://marc.info/?l=linux-bluetooth=132039175324993=2
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1065400/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1065400
>
> Title:
>   Support for loading Broadcom bluetooth firmware
>
> Status in linux package in Ubuntu:
>   Fix Released
> Status in linux source package in Precise:
>   Fix Released
> Status in linux source package in Quantal:
>   Fix Released
> Status in linux source package in Raring:
>   Fix Released
> Status in linux source package in Saucy:
>   Fix Released
> Status in linux source package in Trusty:
>   Confirmed
>
> Bug description:
>   Broadcom bluetooth chips require a tool called patchram uploader [1]
>   to load firmware. This applies to at least BCM20702 and BCM43142.
>   Although some of the devices have an OTPROM that contains required
>   firmware, but it is found that these devices would not have HFP/HSP
>   support unless a upgraded firmware is loaded via patchram uploader.
>
>   This tool requires hci device to do the firmware loading, but this may
>   cause some race condition between patchram tool and bluetoothd or
>   something that also works on hci interface.
>
>   Also it needs some hooks to make firmware loads after bootup, s3,  s4,
>   rfkill, and device hotplug events. Implement this loader in kernel
>   module would make things more easier.
>
>   [1] http://marc.info/?l=linux-bluetooth=132039175324993=2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1065400/+subscriptions
>


-- 
Richard A. Painter, P.E.

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

Title:
  Support for loading Broadcom bluetooth firmware

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

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

[Bug 1065400] Re: Support for loading Broadcom bluetooth firmware

[rich painter]

Unfortunately this is a linux system and not a windows system. The
references to the procedures to "obtain the windows version file and
convert it to linux" does not work and the links are no good.

I don't understand your reply for a "413c" or "x/y/z". The chip the T530
has is 20702A1. I followed your link to 1166113 but could not find any
link to a firmware file.

How does this help us?

I have filed a report with Lenovo forums here
https://forums.lenovo.com/t5/Linux-Discussion/T530-Ubuntu-14-04-3-LTS-
Broadcom-Bluetooth-BCM20702A1-doesn-t/td-p/3662951

but history has shown Lenovo has not been responsive...

Thanks for trying but not 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/1065400

Title:
  Support for loading Broadcom bluetooth firmware

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

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