Re: [Bug 1870087] Re: Old broker lockfile blocks landscape-client starts

2020-04-15 Thread Mark Shuttleworth
Thanks all, I will keep an eye on my systems to see if the issue goes
away. It was triggered regularly on Focal machines so should be quite
easy to spot if it 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/1870087

Title:
  Old broker lockfile blocks landscape-client starts

To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1870087/+subscriptions

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

Re: [Bug 1872183] Re: package chrony 3.2-4ubuntu4.2 failed to install/upgrade: installed chrony package post-removal script subprocess returned error exit status 1

2020-04-15 Thread Mark Shuttleworth
Just wanted to say thank you Vincent, Christian, and it's really great
to see you working together this way!

Mark

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

Title:
  package chrony 3.2-4ubuntu4.2 failed to install/upgrade: installed
  chrony package post-removal script subprocess returned error exit
  status 1

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

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

[Bug 1872964] [NEW] Reliable crash in lowlatency kernel with LXD

2020-04-15 Thread Mark Shuttleworth
Public bug reported:

Hello, I am able to crash 5.4.0-21-lowlatency running LXD. This machine
in an Intel NUC, part of a three-member LXD cluster. The other machines
do not show this crash and they are not running the lowlatency kernel,
but that might be incidental. I will swap out the generic kernel for a
while to see if the behaviour continues there.

Here is the crash:

[ 3222.385724] [ cut here ]
[ 3222.385732] WARNING: CPU: 1 PID: 59852 at kernel/rcu/tree_plugin.h:293 
rcu_note_context_switch+0x46/0x460
[ 3222.385733] Modules linked in: binfmt_misc veth nft_masq nft_chain_nat vxlan 
ip6_udp_tunnel udp_tunnel dummy bridge stp llc ebtable_filter ebtables 
ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables 
iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 iptable_filter bpfilter nf_tables nfnetlink unix_diag ufs qnx4 
hfsplus hfs minix ntfs msdos jfs xfs pps_ldisc zfs(PO) zunicode(PO) zavl(PO) 
icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) dm_multipath zlua(PO) 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_hda_codec_realtek 
snd_hda_codec_generic ledtrig_audio intel_rapl_msr snd_hda_intel mei_hdcp 
snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_pcm kvm snd_timer 
intel_cstate mei_me intel_rapl_perf mei snd soundcore mac_hid acpi_pad 
sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor
[ 3222.385779]  async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel i2c_algo_bit 
crypto_simd cryptd glue_helper drm_kms_helper syscopyarea sysfillrect sysimgblt 
e1000e i2c_i801 fb_sys_fops ahci drm libahci lpc_ich video
[ 3222.385795] CPU: 1 PID: 59852 Comm: systemd-resolve Tainted: P   O   
   5.4.0-21-lowlatency #25-Ubuntu
[ 3222.385796] Hardware name:  /NUC5i5MYBE, BIOS 
MYBDWi5v.86A.0034.2017.0116.2148 01/16/2017
[ 3222.385801] RIP: 0010:rcu_note_context_switch+0x46/0x460
[ 3222.385803] Code: 54 53 48 c7 c3 80 ba 02 00 65 48 03 1d 8b 57 ce 6d 0f 1f 
44 00 00 41 8b 85 80 07 00 00 45 84 f6 0f 85 55 02 00 00 85 c0 7e 0c <0f> 0b 41 
80 bd 84 07 00 00 00 74 33 4c 89 ef e8 36 fb ff ff 65 66
[ 3222.385804] RSP: 0018:a7bf48e3bcf8 EFLAGS: 00010002
[ 3222.385806] RAX: 0001 RBX: 9817c5caba80 RCX: 0001
[ 3222.385807] RDX:  RSI: 92ce6379 RDI: 
[ 3222.385808] RBP: a7bf48e3bd20 R08:  R09: 
[ 3222.385808] R10:  R11:  R12: 9817c5caad00
[ 3222.385809] R13: 9816c39ecd00 R14:  R15: 0002ad00
[ 3222.385811] FS:  7f9c0f530940() GS:9817c5c8() 
knlGS:
[ 3222.385812] CS:  0010 DS:  ES:  CR0: 80050033
[ 3222.385812] CR2: 55988bb4b080 CR3: 0003b5e9a005 CR4: 003606e0
[ 3222.385813] DR0:  DR1:  DR2: 
[ 3222.385814] DR3:  DR6: fffe0ff0 DR7: 0400
[ 3222.385815] Call Trace:
[ 3222.385823]  __schedule+0x9d/0x750
[ 3222.385826]  ? ___sys_sendmsg+0x95/0xd0
[ 3222.385829]  schedule+0x49/0xd0
[ 3222.385831]  schedule_hrtimeout_range_clock+0xf9/0x110
[ 3222.385834]  ? __seccomp_filter+0x85/0x6b0
[ 3222.385837]  schedule_hrtimeout_range+0x13/0x20
[ 3222.385839]  ep_poll+0x3c8/0x410
[ 3222.385843]  ? wake_up_q+0x70/0x70
[ 3222.385845]  do_epoll_wait+0xb8/0xd0
[ 3222.385847]  __x64_sys_epoll_wait+0x1e/0x30
[ 3222.385850]  do_syscall_64+0x57/0x190
[ 3222.385852]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 3222.385854] RIP: 0033:0x7f9c0f04eb77
[ 3222.385856] Code: 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 
48 8d 05 91 ed 2c 00 41 89 ca 8b 00 85 c0 75 18 b8 e8 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 61 f3 c3 0f 1f 80 00 00 00 00 41 55 41 54 41
[ 3222.385857] RSP: 002b:7ffc6fd86d88 EFLAGS: 0246 ORIG_RAX: 
00e8
[ 3222.385859] RAX: ffda RBX: 55988d0ad3c0 RCX: 7f9c0f04eb77
[ 3222.385859] RDX: 000e RSI: 7ffc6fd86d90 RDI: 0004
[ 3222.385861] RBP: 7ffc6fd86f40 R08: 7ffc6fd86d90 R09: 55988d0b645c
[ 3222.385861] R10:  R11: 0246 R12: 00cf
[ 3222.385862] R13:  R14: 7ffc6fd86d90 R15: 0001
[ 3222.385865] ---[ end trace a8d20e83a2bda2fc ]---
[ 3282.386391] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 3282.386412] rcu: Tasks blocked on level-0 rcu_node (CPUs 0-3): P59852
[ 3282.386431]  (detected by 0, t=60002 jiffies, g=454773, q=28443)
[ 3282.386435] systemd-resolve S0 59852  59378 0x8320
[ 3282.386441] Call Trace:
[ 3282.386457]  __schedule+0x2e5/0x750
[ 3282.386465]  schedule+0x49/0xd0
[ 3282.386470]  schedule_hrtimeout_range_clock+0xf9/0x110
[ 

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

2020-04-15 Thread Mark Brouwers
Experiencing the same issues

System:
  Host: thinkpad Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 
9.2.1 
  Desktop: Gnome 3.34.1 wm: gnome-shell dm: GDM3 3.34.1 
  Distro: Ubuntu 19.10 (Eoan Ermine) 
CPU:
  Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP arch: 
Kaby Lake 
  rev: A L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 
31999 
  Speed: 2210 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 2210 2: 2827 3: 
3007 
  4: 2072 5: 2073 6: 2318 7: 2122 8: 1998 
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:5917 
  Display: x11 server: X.Org 1.20.5 driver: i915 compositor: gnome-shell 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa 
19.2.8 
  compat-v: 3.0 direct render: Yes

-- 
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 1864558] Re: Printer adds automatically at boot with notification or if printer deleted

2020-04-13 Thread Mark Richards
The bug referenced above #1725955 goes back to 2017. This issue I
describe has only started with focal 20.04 (I don't get the issue on
19.10 or any earlier release with the same laptop/network/printer
setup). Even if I don't remove the printer I still get the notification
that a my HP Envy wireless printer has been added each time I reboot,
popping up on the Ubuntu logon/greeter screen. If I can help by
providing more info or further testing please ask.

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

Title:
  Printer adds automatically at boot with notification or if printer
  deleted

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

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

[Bug 1872189] Re: Splitting graphical gpsd-clients into separate package would simplify headless installs

2020-04-12 Thread Mark Shuttleworth
gpsmon is the primary tool I use from the clients package, just to see
that gpsd it tracking things properly and to see the PPS is active.
Agree that gpsctl makes more sense in the gpsd package itself, if you
think the same applies to the non-Python bits then the dependencies of
gpsd might stay pretty simple, right?

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

Title:
  Splitting graphical gpsd-clients into separate package would simplify
  headless installs

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

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

[Bug 1872189] [NEW] Splitting graphical gpsd-clients into separate package would simplify headless installs

2020-04-11 Thread Mark Shuttleworth
Public bug reported:

gpsd-clients depends on gir1.2-gtk-3.0 which brings in a bunch of X
dependencies, I think for xgps and xgpsspeed. If those were split into a
separate package, perhaps gps-xclients or gps-clients-graphical, then
headless systems could avoid the X dependencies.

** Affects: gpsd (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/1872189

Title:
  Splitting graphical gpsd-clients into separate package would simplify
  headless installs

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

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

[Bug 1872178] Re: GPSD unable to use Kernel PPS

2020-04-11 Thread Mark Shuttleworth
** Also affects: gpsd (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: chrony (Ubuntu)

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

Title:
  GPSD unable to use Kernel PPS

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

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

[Bug 1872183] Re: package chrony 3.2-4ubuntu4.2 failed to install/upgrade: installed chrony package post-removal script subprocess returned error exit status 1

2020-04-11 Thread Mark Shuttleworth
Upgrade from bionic to focal broke for this system which has chrony
installed.

After do-release-upgrade exited (warning that the system was in an
indeterminate state) I was unable to fix the system initially. It seemed
that systemd-timesyncd was somehow interacting badly with chrony:

$ sudo apt --fix-broken install 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libboost-filesystem1.65.1 libboost-iostreams1.65.1 libboost-system1.65.1 
libcwidget3v5 libip4tc2 libnspr4 libnss3 python3.6 python3.6-minimal
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libboost-iostreams1.71.0 libcwidget4 libxapian30
Suggested packages:
  libcwidget-dev xapian-tools
The following packages will be REMOVED:
  chrony
The following NEW packages will be installed:
  libboost-iostreams1.71.0 libcwidget4
The following packages will be upgraded:
  libxapian30
1 upgraded, 2 newly installed, 1 to remove and 439 not upgraded.
2 not fully installed or removed.
Need to get 0 B/1204 kB of archives.
After this operation, 3022 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 171920 files and directories currently installed.)
Removing chrony (3.2-4ubuntu4.2) ...
Job for systemd-timesyncd.service failed because the control process exited 
with error code.
See "systemctl status systemd-timesyncd.service" and "journalctl -xe" for 
details.
dpkg: error processing package chrony (--remove):
 installed chrony package post-removal script subprocess returned error exit 
status 1
Errors were encountered while processing:
 chrony
E: Sub-process /usr/bin/dpkg returned an error code (1)

I turned off the systemd-timesync ntp and that then allowed chrony to be
removed (not quite what I wanted but that is another story):

mark@bigben:/var/log/chrony$ sudo timedatectl status
  Local time: Sat 2020-04-11 10:55:31 UTC
  Universal time: Sat 2020-04-11 10:55:31 UTC
RTC time: Sat 2020-04-11 10:55:31
   Time zone: Etc/UTC (UTC, +)
   System clock synchronized: yes
systemd-timesyncd.service active: yes
     RTC in local TZ: no
mark@bigben:/var/log/chrony$ sudo timedatectl set-ntp false
mark@bigben:/var/log/chrony$ sudo timedatectl status
  Local time: Sat 2020-04-11 10:55:50 UTC
  Universal time: Sat 2020-04-11 10:55:50 UTC
RTC time: Sat 2020-04-11 10:55:50
   Time zone: Etc/UTC (UTC, +)
   System clock synchronized: yes
systemd-timesyncd.service active: no
 RTC in local TZ: no

$ sudo apt --fix-broken install 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libboost-filesystem1.65.1 libboost-iostreams1.65.1 libboost-system1.65.1 
libcwidget3v5 libip4tc2 libnspr4 libnss3 python3.6 python3.6-minimal
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libboost-iostreams1.71.0 libcwidget4 libxapian30
Suggested packages:
  libcwidget-dev xapian-tools
The following packages will be REMOVED:
  chrony
The following NEW packages will be installed:
  libboost-iostreams1.71.0 libcwidget4
The following packages will be upgraded:
  libxapian30
1 upgraded, 2 newly installed, 1 to remove and 439 not upgraded.
2 not fully installed or removed.
Need to get 0 B/1204 kB of archives.
After this operation, 3022 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 171920 files and directories currently installed.)
Removing chrony (3.2-4ubuntu4.2) ...

And then installing chrony again worked.

So it looks like we need to harden the chrony packaging for the world of
systemd-timesync in general if we want upgrades to focal with chrony not
to have problems.

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

Title:
  package chrony 3.2-4ubuntu4.2 failed to install/upgrade: installed
  chrony package post-removal script subprocess returned error exit
  status 1

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

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

[Bug 1872183] [NEW] package chrony 3.2-4ubuntu4.2 failed to install/upgrade: installed chrony package post-removal script subprocess returned error exit status 1

2020-04-11 Thread Mark Shuttleworth
Public bug reported:

Failed during bionic->focal upgrade

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chrony 3.2-4ubuntu4.2
ProcVersionSignature: Ubuntu 4.15.0-97.98-lowlatency 4.15.18
Uname: Linux 4.15.0-97-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Sat Apr 11 10:42:36 2020
DpkgTerminalLog:
 Removing chrony (3.2-4ubuntu4.2) ...
 Job for systemd-timesyncd.service failed because the control process exited 
with error code.
 See "systemctl status systemd-timesyncd.service" and "journalctl -xe" for 
details.
 dpkg: error processing package chrony (--remove):
  installed chrony package post-removal script subprocess returned error exit 
status 1
ErrorMessage: installed chrony package post-removal script subprocess returned 
error exit status 1
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  2.0.1ubuntu1
SourcePackage: chrony
Title: package chrony 3.2-4ubuntu4.2 failed to install/upgrade: installed 
chrony package post-removal script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-04-11 (0 days ago)

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


** Tags: amd64 apport-package focal 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/1872183

Title:
  package chrony 3.2-4ubuntu4.2 failed to install/upgrade: installed
  chrony package post-removal script subprocess returned error exit
  status 1

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

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

[Bug 1872178] [NEW] GPSD unable to use Kernel PPS

2020-04-11 Thread Mark Shuttleworth
Public bug reported:

I am working with gpsd and a pulse-per-second (PPS) signal on a serial
port.

GPSD is able to detect the PPS signal but it is not able to use Kernel
PPS for lower jitter. Here are the relevant log lines when PPS is being
detected and enabled:

gpsd:INFO: KPPS:/dev/ttyS0 device not found.
gpsd:WARN: KPPS:/dev/ttyS0 kernel PPS unavailable, PPS accuracy will suffer
gpsd:PROG: PPS:/dev/ttyS0 thread launched
gpsd:INFO: PPS:/dev/ttyS0 ntpshm_link_activate: 1
gpsd:PROG: TPPS:/dev/ttyS0 ioctl(TIOCMIWAIT) succeeded, time: 
1586594708.000179259,  state: 0
gpsd:PROG: TPPS:/dev/ttyS0 Clear, cycle: 1586594708000179, duration: 
1586594708000179 @  1586594708.000179259
gpsd:PROG: PPS:/dev/ttyS0 Clear cycle: 1586594708000179, duration: 
1586594708000179 @  1586594708.000179259
gpsd:PROG: TPPS:/dev/ttyS0 ioctl(TIOCMIWAIT) succeeded, time: 
1586594708.100154827,  state: 64
gpsd:PROG: TPPS:/dev/ttyS0 Assert, cycle: 1586594708100154, duration: 99975 @  
1586594708.100154827
gpsd:PROG: PPS:/dev/ttyS0 Assert cycle: 1586594708100154, duration: 99975 @  
1586594708.100154827
gpsd:PROG: PPS:/dev/ttyS0 Assert ignored missing last_fixtime
gpsd:PROG: TPPS:/dev/ttyS0 ioctl(TIOCMIWAIT) succeeded, time: 
1586594709.000117775,  state: 0
gpsd:PROG: TPPS:/dev/ttyS0 Clear, cycle: 38, duration: 899962 @  
1586594709.000117775
gpsd:PROG: PPS:/dev/ttyS0 Clear cycle: 38, duration: 899962 @  
1586594709.000117775
gpsd:INFO: PPS:/dev/ttyS0 Clear hooks called clock:  1586594709.000117775 real: 
 1586594709.0: no fix
gpsd:PROG: PPS:/dev/ttyS0 Clear no fix @  1586594709.000117775 offset 
-0.000117775
gpsd:PROG: TPPS:/dev/ttyS0 ioctl(TIOCMIWAIT) succeeded, time: 
1586594709.100167645,  state: 64
gpsd:PROG: TPPS:/dev/ttyS0 Assert, cycle: 112, duration: 100049 @  
1586594709.100167645
gpsd:PROG: PPS:/dev/ttyS0 Assert cycle: 112, duration: 100049 @  
1586594709.100167645
gpsd:PROG: PPS:/dev/ttyS0 Assert ignored this second already handled

The kernel does have PPS configured and the pps_ldisc module loaded. I
think GPSd actually drove the loading of the module but I am not sure. I
see the module being loaded and the serial port becoming a pps0 source
during the boot sequence:

10:34:09 doorway kernel: [8.691161] pps_ldisc: PPS line discipline 
registered
10:34:09 doorway kernel: [8.691686] pps pps0: new PPS source serial0
10:34:09 doorway kernel: [8.691714] pps pps0: source "/dev/ttyS0" added

This is confirmed with ppsfind:

$ ppsfind ttyS0
pps0: name=serial0 path=/dev/ttyS0

And this pps0 device is working well:

$ sudo ppswatch /dev/pps0
trying PPS source "/dev/pps0"
found PPS source "/dev/pps0"
timestamp: 1586596125, sequence: 1418, offset:  85067
timestamp: 1586596125, sequence: 1418, offset:  85067
timestamp: 1586596126, sequence: 1419, offset:  81949
timestamp: 1586596126, sequence: 1419, offset:  81949
timestamp: 1586596127, sequence: 1420, offset:  80119
timestamp: 1586596127, sequence: 1420, offset:  80119
timestamp: 1586596128, sequence: 1421, offset:  81099
timestamp: 1586596128, sequence: 1421, offset:  81099


So, the kernel PPS subsystem is there and appears to be perfectly happy with 
the pps0 coming from /dev/ttyS0 but still GPSD appears unable to use all of 
that.

** Affects: chrony (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/1872178

Title:
  GPSD unable to use Kernel PPS

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

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

[Bug 1872175] [NEW] gpsd unable to open chrony PPS socket

2020-04-11 Thread Mark Shuttleworth
Public bug reported:

GPSd fails to access the socket used to communicate PPS signals with
Chrony.

>From the startup log:

gpsd:PROG: PPS:/dev/ttyS0 connect chrony socket failed:
/var/run/chrony.ttyS0.sock, error: -2, errno: 13/Permission denied

The socket in question has these permissions:

$ ls -l /var/run/chrony.ttyS0.sock 
srwxr-xr-x 1 root root 0 Apr 10 17:25 /var/run/chrony.ttyS0.sock

gpsd is running as its own user gpsd, and chrony as _chrony.

$ groups gpsd
gpsd : dialout
$ groups _chrony 
_chrony : _chrony

I have tried adding gpsd to group _chrony and changing the ownership and
permissions of chrony.ttyS0.sock but to no avail. I always see the
permission denied message.

AppArmor rules for gpsd appear to allow the connection, too:

  # default paths feeding GPS data into chrony
  /{,var/}run/chrony.tty{,S,USB,AMA}[0-9]*.sock rw,
  /tmp/chrony.tty{,S,USB,AMA}[0-9]*.sock rw,

So I am stumped.

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

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

** Also affects: chrony (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/1872175

Title:
  gpsd unable to open chrony PPS socket

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

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

[Bug 1872063] Re: NetworkManager IWD, wpa_supplicant backends

2020-04-10 Thread Mark
Related bug https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1872060

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

Title:
  NetworkManager IWD, wpa_supplicant backends

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

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

[Bug 1872063] [NEW] NetworkManager IWD, wpa_supplicant backends

2020-04-10 Thread Mark
Public bug reported:

focal, network-manager 1.22.10,

NetworkManager now support (alternative) IWD backend via `wifi.backend=iwd`, 
but the package still depends on wpa_supplicant. NM should require [iwd OR 
wpa_supplicant].

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


** Tags: packaging

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

Title:
  NetworkManager IWD, wpa_supplicant backends

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

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

[Bug 1872061] [NEW] IWD cannot connect to hidden SSID

2020-04-10 Thread Mark
Public bug reported:

focal, iwd 1.5-1,

I'm using NetworkManager to connect to my wifi network with hidden SSID. 
- when using wpa_supplicant, I can connect to the hidden ssid. 
- when switching `wifi.backend=iwd` to IWD, I no longer see the hidden networks 
(albeit already "known" to NetworkManager). I do see normal/visible SSIDs.

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


** Tags: wifi

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

Title:
  IWD cannot connect to hidden SSID

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

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

[Bug 1872060] [NEW] IWD should have replaces wpa_supplicant

2020-04-10 Thread Mark
Public bug reported:

Package: IWD
Version: 1.5-1
Ubuntu: focal

wpa_supplicant and iwd are mutually exclusive, so IWD should provide
replaces 'wpa_supplicant' (similar for wpa)

Additionally, NetworkManager should rely on either IWD or
wpa_supplicant. Currently I cannot uninstall wpa_supplicant if using
iwd, and must keep masking it.

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


** Tags: packaging

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

Title:
  IWD should have replaces wpa_supplicant

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

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

[Bug 1872026] [NEW] Activity Bar icon aspect ratio broken

2020-04-10 Thread Mark Smith
Public bug reported:

The aspect ratio of the icon on the top left of the screen (Activites
bar?) is broken so it looks taller and thinner than normal.

See attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
Uname: Linux 5.4.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 10 09:10:09 2020
InstallationDate: Installed on 2020-01-24 (76 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
 Log time: 2020-04-10 09:03:51.154471
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done
VarLogDistupgradeTermlog:
 
mtime.conffile..etc.update-manager.release-upgrades: 2020-04-03T20:22:43.358127

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


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

** Attachment added: "Screenshot of distorted icon"
   
https://bugs.launchpad.net/bugs/1872026/+attachment/5351098/+files/Screenshot%20from%202020-04-10%2009-04-23.png

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

Title:
  Activity Bar icon aspect ratio broken

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

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

[Bug 1868108]

2020-04-09 Thread Mark-lam
(In reply to Michael Catanzaro from comment #76)
> We wound up not reverting the patches.
> 
> aarch64 is still broken (bug #209670), but ppc64le is now fine.
> 
> Solving bug #209670 is basically impossible. We are being expected to
> provide a value at compile time that cannot be known until runtime. Very
> frustrating.
> 
> Oh, and I discovered people are actually using huge pages, so WebKit is
> guaranteed to be broken for them no matter what. *shrug!*

One way around this is to disable this mitigation for those platforms
that cannot be statically configured: basically, on those platforms, at
runtime, check if page size is within acceptable limits (and whatever
other criteria you need), and if not, disable the mitigation and don’t
do the page freeze.

On platforms that can guarantee their page sizes, this option to disable
the mitigation should be #if’d out.

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

Title:
  [autopkgtest][focal] ruby-gnome/3.4.1-2build1
  class:TestWebKit2GtkWebView failure

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

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

[Bug 1871566] [NEW] Files from packages installed in directory /debian

2020-04-08 Thread Mark Fraser
Public bug reported:

Installed the package libffmpeg-nvenc-dev, but it seems to be installing files 
in the wrong place.
dpkg -S libffmpeg-nvenc-dev
libffmpeg-nvenc-dev: /debian/libffmpeg-nvenc-dev/usr/include
libffmpeg-nvenc-dev: /debian/libffmpeg-nvenc-dev/usr/lib/pkgconfig/ffnvcodec.pc
libffmpeg-nvenc-dev: 
/debian/libffmpeg-nvenc-dev/usr/include/ffnvcodec/nvEncodeAPI.h
libffmpeg-nvenc-dev: /debian/libffmpeg-nvenc-dev/usr/include/ffnvcodec
libffmpeg-nvenc-dev: 
/debian/libffmpeg-nvenc-dev/usr/include/ffnvcodec/dynlink_loader.h
libffmpeg-nvenc-dev: 
/debian/libffmpeg-nvenc-dev/usr/include/ffnvcodec/dynlink_cuda.h
libffmpeg-nvenc-dev: /usr/share/doc/libffmpeg-nvenc-dev/changelog.Debian.gz
libffmpeg-nvenc-dev: /debian/libffmpeg-nvenc-dev/usr/lib/pkgconfig
libffmpeg-nvenc-dev: /debian/libffmpeg-nvenc-dev
libffmpeg-nvenc-dev: /debian/libffmpeg-nvenc-dev/usr
libffmpeg-nvenc-dev: /debian/libffmpeg-nvenc-dev/usr/lib
libffmpeg-nvenc-dev: /usr/share/doc/libffmpeg-nvenc-dev/copyright
libffmpeg-nvenc-dev: 
/debian/libffmpeg-nvenc-dev/usr/include/ffnvcodec/dynlink_cuviddec.h
libffmpeg-nvenc-dev: /usr/share/doc/libffmpeg-nvenc-dev
libffmpeg-nvenc-dev: 
/debian/libffmpeg-nvenc-dev/usr/include/ffnvcodec/dynlink_nvcuvid.h

lsb_release -a; uname -a; ls /debian | head

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
Codename: focal
Linux Laptop 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
libffmpeg-nvenc-dev

** Affects: nv-codec-headers (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/1871566

Title:
  Files from packages installed in directory /debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nv-codec-headers/+bug/1871566/+subscriptions

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

[Bug 1870748] Re: Authentication Window Stays Open

2020-04-06 Thread Mark Smith
Sorry, I should add that the pop-up window remained on top of all the others, 
so it wasn't hidden behind anything else before I went to bed. 
And although it was at the top, when I entered my password and the field went 
grey, the window remained visible, but if I clicked anywhere in the window, I 
actually clicked whatever was behind it.

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

Title:
  Authentication Window Stays Open

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

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

[Bug 1870748] Re: Authentication Window Stays Open

2020-04-06 Thread Mark Smith
Not at that time - I had just gone to bed. I had changed them earlier that day, 
and the error triggered. So I rebooted. This time the error came about without 
me touching it.
Journal output attached.
The bug doesn't appear to be triggered by any steps in Software-Updater


** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870748/+attachment/5347706/+files/journal.txt

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

Title:
  Authentication Window Stays Open

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

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

[Bug 1870748] Re: Authentication Window Stays Open

2020-04-04 Thread Mark Smith
I attempted to make a change to a repository by launching Software &
Updates and editing an unselected package from eoan to fossa - the
authentication window persisted at the top left of my screen throughout
- even after entering my credentials in the central authentication
window that popped up (and went as normal)

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

Title:
  Authentication Window Stays Open

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

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

[Bug 1870748] [NEW] Authentication Window Stays Open

2020-04-04 Thread Mark Smith
Public bug reported:

I left the Beta of Focal Fossa running overnight and when I logged in
this morning, I found an open Authentication window with the message "To
change software repository settings, you need to authenticate" (see
attached screenshot).

I enter my password and the password field grey out.

The window stays persistent but is "invisible" to the mouse - i.e. if I click 
anywhere in it, it actually clicks the thing behind it. 
The Cancel button does nothing.

I had this same issue yesterday when actually running Software &
Updates.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: software-properties-gtk 0.98.7
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 09:55:33 2020
InstallationDate: Installed on 2020-01-24 (70 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot of persistent Software & Updates 
authentication window"
   
https://bugs.launchpad.net/bugs/1870748/+attachment/5346150/+files/Screenshot%20from%202020-04-04%2009-58-06.png

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

Title:
  Authentication Window Stays Open

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

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

[Bug 1870616] [NEW] [MEDION E122X] hibernate/resume failure

2020-04-03 Thread Mark Petersen
Public bug reported:

Had terminal and firefox open.

Then atemmepted to see if i could hibernate with

pm-hibernate

just to see if it worked

ProblemType: KernelOops
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-21-generic 5.4.0-21.25
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  darkyere   1121 F pulseaudio
Date: Fri Apr  3 21:57:45 2020
DuplicateSignature: hibernate/resume:MEDION E122X:Medion-E122X_0107
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
InstallationDate: Installed on 2020-04-02 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
InterpreterPath: /usr/bin/python3.8
MachineType: MEDION E122X
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/LubuntuRootLVM-Root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-21-generic N/A
 linux-backports-modules-5.4.0-21-generic  N/A
 linux-firmware1.187
SourcePackage: linux
Title: [MEDION E122X] hibernate/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 05/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Medion-E122X_0107
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: E122X
dmi.board.vendor: MEDION
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: MEDION
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMedion-E122X_0107:bd05/11/2010:svnMEDION:pnE122X:pvrVer01.07:rvnMEDION:rnE122X:rvrRev1.0:cvnMEDION:ct10:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: E122X
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: Ver: 01.07
dmi.sys.vendor: MEDION

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


** Tags: amd64 apport-kerneloops focal hibernate resume

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

Title:
  [MEDION E122X] hibernate/resume failure

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

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

[Bug 1851682] Re: oscap is broken in ubuntu 19.10

2020-03-27 Thread Mark Morlino
** Description changed:

+ I think this needs an SRU, as such I'm modifying the description based
+ on the SRU template. I'll update the title and attach debdiffs shortly.
+ 
+ [Impact]
+ 
+ The bug causes oscap to fail to run with OVAL files produced by the
+ Ubuntu Security team.
+ 
+ This is the upstream issue:
+ https://github.com/OpenSCAP/openscap/issues/1367
+ 
+ The fix is simple and I've tested in under bionic, eoan, and focal.
+ 
+ The patch corrects an typo or copy/paste error in the original code.
+ 
https://github.com/OpenSCAP/openscap/commit/5e5bc61c1fc6a6556665aa5689a62d6bc6487c74
+ 
+ [Test Case]
+ 
+ This can be reproduced on eoan and focal by following the instructions
+ for using ubuntu security oval data here: https://people.canonical.com
+ /~ubuntu-security/oval/
+ 
+ The bug does not manifest directly in bionic but if you include
+ libopenscap8 in a snap based on core18, the version of oscap in the snap
+ will produce the same behavior when you run the snap on eoan or focal
+ 
+ [Regression Potential]
+ 
+ The potential for regression seems low in this case. I've built the deb
+ locally for bionic, eoan, and focal and smoke tested in in VMs using the
+ ubuntu security OVAL files and the test file from the comment below
+ https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/1851682/comments/2
+ 
+ If a regression were to exist, it would likely manifest itself with a
+ runtime error much like the original problem.
+ 
+ 
+ ORIGINAL BUG REPORT BELOW
+ ###
  oscap segfaults while trying to check using ubuntu-security definitions:
  
  The command:
  oscap oval eval --report /tmp/oscap_report.html 
/var/tmp/com.ubuntu.eoan.cve.oval.xml
  
  Segfault:
  ...
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Probe with PID=26379 has been killed with signal 11 
[../../../../../src/OVAL/probes/SEAP/sch_pipe.c:178]
  Probe with PID=26379 has core dumped. 
[../../../../../src/OVAL/probes/SEAP/sch_pipe.c:182]
  Unable to close probe sd [../../../src/OVAL/oval_probe_ext.c:424]
  Unable to receive a message from probe 
[../../../src/OVAL/oval_probe_ext.c:579]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Probe with PID=26393 has been killed with signal 11 
[../../../../../src/OVAL/probes/SEAP/sch_pipe.c:178]
  Probe with PID=26393 has core dumped. 
[../../../../../src/OVAL/probes/SEAP/sch_pipe.c:182]
  Unable to close probe sd [../../../src/OVAL/oval_probe_ext.c:424]
  Unable to receive a message from probe 
[../../../src/OVAL/oval_probe_ext.c:579]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  
  The OVAL definitions are taken directly from
  https://people.canonical.com/~ubuntu-
  security/oval/com.ubuntu.eoan.cve.oval.xml
  
  Version:
  oscap --version
  OpenSCAP command line tool (oscap) 1.2.16
  Copyright 2009--2017 Red Hat Inc., Durham, North Carolina.
  
   Supported specifications 
  XCCDF Version: 1.2
  OVAL Version: 5.11.1
  CPE Version: 2.3
  CVSS Version: 2.0
  CVE Version: 2.0
  Asset Identification Version: 1.1
  Asset Reporting Format Version: 1.1
  CVRF Version: 1.1
  
   Capabilities added by auto-loaded plugins 
  SCE Version: 1.0 (from libopenscap_sce.so.8)
  
   Paths 
  Schema files: /usr/share/openscap/schemas
  Default CPE files: /usr/share/openscap/cpe
  Probes: /usr/lib/x86_64-linux-gnu/openscap

** Patch added: "bionic debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/1851682/+attachment/5342345/+files/openscap_1.2.15-1ubuntu0.2.debdiff

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

Title:
  oscap is broken in ubuntu 19.10

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu

[Bug 1851682] Re: oscap is broken in ubuntu 19.10

2020-03-27 Thread Mark Morlino
** Patch added: "focal debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/1851682/+attachment/5342347/+files/openscap_1.2.16-2ubuntu4.debdiff

** Description changed:

- I think this needs an SRU, as such I'm modifying the description based
- on the SRU template. I'll update the title and attach debdiffs shortly.
- 
  [Impact]
  
  The bug causes oscap to fail to run with OVAL files produced by the
  Ubuntu Security team.
  
  This is the upstream issue:
  https://github.com/OpenSCAP/openscap/issues/1367
  
  The fix is simple and I've tested in under bionic, eoan, and focal.
  
  The patch corrects an typo or copy/paste error in the original code.
  
https://github.com/OpenSCAP/openscap/commit/5e5bc61c1fc6a6556665aa5689a62d6bc6487c74
  
  [Test Case]
  
  This can be reproduced on eoan and focal by following the instructions
  for using ubuntu security oval data here: https://people.canonical.com
  /~ubuntu-security/oval/
  
  The bug does not manifest directly in bionic but if you include
  libopenscap8 in a snap based on core18, the version of oscap in the snap
  will produce the same behavior when you run the snap on eoan or focal
  
  [Regression Potential]
  
  The potential for regression seems low in this case. I've built the deb
  locally for bionic, eoan, and focal and smoke tested in in VMs using the
  ubuntu security OVAL files and the test file from the comment below
  https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/1851682/comments/2
  
  If a regression were to exist, it would likely manifest itself with a
  runtime error much like the original problem.
  
  
  ORIGINAL BUG REPORT BELOW
  ###
  oscap segfaults while trying to check using ubuntu-security definitions:
  
  The command:
  oscap oval eval --report /tmp/oscap_report.html 
/var/tmp/com.ubuntu.eoan.cve.oval.xml
  
  Segfault:
  ...
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Probe with PID=26379 has been killed with signal 11 
[../../../../../src/OVAL/probes/SEAP/sch_pipe.c:178]
  Probe with PID=26379 has core dumped. 
[../../../../../src/OVAL/probes/SEAP/sch_pipe.c:182]
  Unable to close probe sd [../../../src/OVAL/oval_probe_ext.c:424]
  Unable to receive a message from probe 
[../../../src/OVAL/oval_probe_ext.c:579]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  Probe with PID=26393 has been killed with signal 11 
[../../../../../src/OVAL/probes/SEAP/sch_pipe.c:178]
  Probe with PID=26393 has core dumped. 
[../../../../../src/OVAL/probes/SEAP/sch_pipe.c:182]
  Unable to close probe sd [../../../src/OVAL/oval_probe_ext.c:424]
  Unable to receive a message from probe 
[../../../src/OVAL/oval_probe_ext.c:579]
  Invalid oval result type: -1. 
[../../../../src/OVAL/results/oval_resultTest.c:179]
  
  The OVAL definitions are taken directly from
  https://people.canonical.com/~ubuntu-
  security/oval/com.ubuntu.eoan.cve.oval.xml
  
  Version:
  oscap --version
  OpenSCAP command line tool (oscap) 1.2.16
  Copyright 2009--2017 Red Hat Inc., Durham, North Carolina.
  
   Supported specifications 
  XCCDF Version: 1.2
  OVAL Version: 5.11.1
  CPE Version: 2.3
  CVSS Version: 2.0
  CVE Version: 2.0
  Asset Identification Version: 1.1
  Asset Reporting Format Version: 1.1
  CVRF Version: 1.1
  
   Capabilities added by auto-loaded plugins 
  SCE Version: 1.0 (from libopenscap_sce.so.8)
  
   Paths 
  Schema files: /usr/share/openscap/schemas
  Default CPE files: /usr/share/openscap/cpe
  Probes: /usr/lib/x86_64-linux-gnu/openscap

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

Title:
  oscap is broken in ubuntu 19.10

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu

[Bug 1851682] Re: oscap is broken in ubuntu 19.10

2020-03-27 Thread Mark Morlino
** Patch added: "eoan debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/1851682/+attachment/5342346/+files/openscap_1.2.16-2ubuntu1.1.debdiff

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

Title:
  oscap is broken in ubuntu 19.10

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

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

[Bug 1868065] Re: [Net Boot] Ubuntu server 18.04.4 failed to diskless boot via IPv6 iSCSI

2020-03-27 Thread Mark Morlino
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  [Net Boot] Ubuntu server 18.04.4 failed to diskless boot  via IPv6
  iSCSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1868065/+subscriptions

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

[Bug 1869408] Re: package libvte-2.91-common 0.59.91-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/systemd/user/vte-spawn-.scope.d/defaults.conf', which is also in package libvte-2

2020-03-27 Thread Mark Morlino
*** This bug is a duplicate of bug 1869407 ***
https://bugs.launchpad.net/bugs/1869407

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libvte-2.91-common 0.59.91-0ubuntu2 failed to install/upgrade:
  trying to overwrite '/usr/lib/systemd/user/vte-
  spawn-.scope.d/defaults.conf', which is also in package
  libvte-2.91-0:amd64 0.59.91-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1869408/+subscriptions

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

[Bug 1868193] Re: package gufw 16.04.1-0ubuntu1.1 failed to install/upgrade: package gufw is already installed and configured

2020-03-27 Thread Mark Morlino
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package gufw 16.04.1-0ubuntu1.1 failed to install/upgrade: package
  gufw is already installed and configured

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

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

[Bug 1869357] [NEW] package libreoffice-math 1:6.4.2-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml', which is

2020-03-27 Thread Mark Shuttleworth
Public bug reported:

Looks like a file has moved between packages which caused the dpkg
error. The issue was resolved with "apt --fix-broken install" but
nevertheless we should make sure nobody sees this on upgrade. Thanks!

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libreoffice-math 1:6.4.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
Date: Fri Mar 27 11:22:13 2020
ErrorMessage: trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.1-0ubuntu1
InstallationDate: Installed on 2019-12-01 (117 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  2.0.1
SourcePackage: libreoffice
Title: package libreoffice-math 1:6.4.2-0ubuntu1 failed to install/upgrade: 
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.1-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libreoffice (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/1869357

Title:
  package libreoffice-math 1:6.4.2-0ubuntu1 failed to install/upgrade:
  trying to overwrite
  
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
  which is also in package libreoffice-common 1:6.4.1-0ubuntu1

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

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

Re: [Bug 1868706] Re: Snapd postinst script hangs

2020-03-26 Thread Mark Shuttleworth
Pawel, this is great debugging, thank you. Agree it's an edge case.

Mark

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

Title:
  Snapd postinst script hangs

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

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

[Bug 1869216] [NEW] failure during install

2020-03-26 Thread Mark Graham
Public bug reported:

failure during install.  Need to check the integrity of the USB drive
used to install

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
Date: Thu Mar 26 10:31:55 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  failure during install

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

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

[Bug 785701] Re: Inkscape freezes at opening

2020-03-25 Thread Mark Jeronimus
This recently this started happening to 0.92. I downloaded 1.0alpha
(AppImage) and it still happens.

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

Title:
  Inkscape freezes at opening

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

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

[Bug 1851682] Re: oscap is broken in ubuntu 19.10

2020-03-25 Thread Mark Morlino
** Also affects: openscap (Ubuntu Bionic)
   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/1851682

Title:
  oscap is broken in ubuntu 19.10

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

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

[Bug 1868706] Re: Snapd postinst script hangs

2020-03-25 Thread Mark Shuttleworth
OK, so *now* the situation has cleared on that machine. And there are no
snaps installed :/

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

Title:
  Snapd postinst script hangs

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

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

[Bug 1868244] Re: python3.8 crashed with signal 5 in g_object_new_with_properties()

2020-03-25 Thread Mark Morlino
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  python3.8 crashed with signal 5 in g_object_new_with_properties()

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

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

[Bug 1868205] Re: on installing ubuntu with updating

2020-03-25 Thread Mark Morlino
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  on installing ubuntu with updating

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

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

[Bug 1869035] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386

2020-03-25 Thread Mark Morlino
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: trying to
  overwrite shared '/etc/pulse/client.conf', which is different from
  other instances of package libpulse0:i386

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

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

[Bug 1868397] Re: touchpad not working

2020-03-23 Thread Mark Morlino
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  touchpad not working

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

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

[Bug 1868472] Re: start up delay and terminal problem

2020-03-23 Thread Mark Morlino
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  start up delay and terminal problem

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

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

[Bug 1868560] Re: The Software Updater Always say's " No Internet Connect" when I click it for Updating Apps.

2020-03-23 Thread Mark Morlino
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  The Software Updater Always say's " No Internet Connect" when I click
  it for Updating  Apps.

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

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

[Bug 1867930] [NEW] gnome-control centre crashed after clicking on 'About'

2020-03-18 Thread Mark Crouch
Public bug reported:

I clicked on 'About', nothing happened, ie the page was blank (hanging?), then 
clicking on another category caused the application to crash.
After the crash, trying to run gnome-control-centre from the terminal, gives 
the following error:

(gnome-control-center:10275): GLib-CRITICAL **: 14:02:17.704: g_environ_setenv: 
assertion 'value != NULL' failed
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 18 13:55:24 2020
InstallationDate: Installed on 2020-02-26 (20 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  gnome-control centre crashed after clicking on 'About'

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

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

[Bug 1867431] Re: ERROR got an error from dpkg for pkg: 'libc6'

2020-03-14 Thread Mark Shuttleworth
@kai-mast I think grub is the only way, since both sudo and login are
stuck under these circumstances.

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

Title:
  ERROR got an error from dpkg for pkg: 'libc6'

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

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

[Bug 1867431] Re: ERROR got an error from dpkg for pkg: 'libc6'

2020-03-14 Thread Mark Shuttleworth
@jbouter you are a lifesaver. Or at least, a weekend-saver, thank you :)

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

Title:
  ERROR got an error from dpkg for pkg: 'libc6'

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

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

[Bug 1867431] Re: ERROR got an error from dpkg for pkg: 'libc6'

2020-03-14 Thread Mark Shuttleworth
Added another term.log, hope that's useful

** Attachment added: "term.log"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867431/+attachment/5336953/+files/term.log

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

Title:
  ERROR got an error from dpkg for pkg: 'libc6'

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

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

[Bug 1867442] [NEW] settings dialog for extension "desktop icons" doesn't launch

2020-03-14 Thread Mark-Daniel Lüthje
Public bug reported:

Description:Ubuntu Focal Fossa (development branch)
Release:20.04

gnome-shell:
  Installiert:   3.35.91-1ubuntu2
  Installationskandidat: 3.35.91-1ubuntu2
  Versionstabelle:
 *** 3.35.91-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

I clicked the settings icon of Desktop Icons to change the settings of
this extension.

Instead no settings dialog appeared, no indication of any activity.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 14 16:21:27 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell-extension-prefs
InstallationDate: Installed on 2020-03-11 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  settings dialog for extension "desktop icons" doesn't launch

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

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

Re: [Bug 1863410] Re: Old isc-kea-common package removal looks dangerous

2020-03-05 Thread Mark Shuttleworth
Ah, thank you Andreas, that is a good catch.

I believe the ISC maintains some .debs themselves, and it would be worth
reaching out to see if they want to collaborate to avoid this sort of
gotcha. They do have some additional commercial packages they would care
about, and we should offer to collaborate to ensure that their pieces
fit well on standard Ubuntu packages of the open source pieces if they
are open to that.

Mark

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

Title:
  Old isc-kea-common package removal looks dangerous

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

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

[Bug 1851682] Re: oscap is broken in ubuntu 19.10

2020-03-04 Thread Mark Morlino
I created a test OVAL file to dig into this a little bit more.

$ cat com.ubuntu.test.cve.oval.xml 
http://oval.mitre.org/XMLSchema/oval-definitions-5";

xmlns:ind-def="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent";
xmlns:oval="http://oval.mitre.org/XMLSchema/oval-common-5";
xmlns:unix-def="http://oval.mitre.org/XMLSchema/oval-definitions-5#unix";
xmlns:linux-def="http://oval.mitre.org/XMLSchema/oval-definitions-5#linux";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://oval.mitre.org/XMLSchema/oval-common-5 
oval-common-schema.xsd   http://oval.mitre.org/XMLSchema/oval-definitions-5 
oval-definitions-schema.xsd   
http://oval.mitre.org/XMLSchema/oval-definitions-5#independent 
independent-definitions-schema.xsd   
http://oval.mitre.org/XMLSchema/oval-definitions-5#unix 
unix-definitions-schema.xsd   
http://oval.mitre.org/XMLSchema/oval-definitions-5#macos 
linux-definitions-schema.xsd">


Canonical CVE OVAL Generator
1.1
5.11.1
2020-03-03T10:37:20





CVE-1970-0200 on Ubuntu - high.
OVAL TEST
To simulate a vunlerable package with no 
available patch being installed on the system.
Checks for the 'linux-doesnotexist-base' 
package to be installed on the system.
There is no 'linux-doesnotexist-base' package 
so it will never be installed.
This test should always return false (not 
vulnerable) and appear green in the report.

Ubuntu


High
Copyright (C) 2018 Canonical Ltd.
2018-01-24 10:29:00 UTC








CVE-1970-0300 on Ubuntu - high.
OVAL TEST
This is the opposite of the previous test, just 
to confirm that oscap correct detects the installed package
Checks for the 'linux-base' package to be 
installed on the system.
There should always be a 'linux-base' package 
installed.
This test should always return true 
(vulnerable) and appear red/orange in the report.

Ubuntu


High
Copyright (C) 2018 Canonical Ltd.
2018-01-24 10:29:00 UTC








CVE-1907-0400 on Ubuntu - high.
OVAL TEST
To simulate an installed package that is 
vulnerable when there is an available version to fix the CVE.
Checks for version less than 
'99:99.9.9+dfsg-9ubuntu9.9' of the 'linux-base' package to be installed on the 
system.
There should always be a 'linux-base' package 
installed and the version will be less than '99:99.9.9+dfsg-9ubuntu9.9'.
This test should always return true 
(vulnerable) and appear red/orange in the report.

Ubuntu


High
Copyright (C) 2017 Canonical Ltd.
2017-03-27 17:59:00 UTC
2017-03-27








CVE-1907-0500 on Ubuntu - high.
OVAL TEST
To simulate an installed package that is 
updated to a patched version and not vulnerable to CVE.
Checks for version less than 
'00:00.0.0+dfsg-0ubuntu0.0' of the 'linux-base' package to be installed on the 
system.
There should always be a 'linux-base' package 
installed and the version will be greater than '00:00.0.0+dfsg-0ubuntu0.0'.
This test should always return false (not 
vulnerable) and appear green in the report.

Ubuntu

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6458"; />

High
Copyright (C) 2017 Canonical Ltd.
2017-03-27 17:59:00 UTC
2017-03-27































[Bug 1851682] Re: oscap is broken in ubuntu 19.10

2020-03-04 Thread Mark Morlino
** Also affects: openscap (Ubuntu Focal)
   Importance: Undecided
   Status: Confirmed

** Also affects: openscap (Ubuntu Eoan)
   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/1851682

Title:
  oscap is broken in ubuntu 19.10

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

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

[Bug 1865309] [NEW] openssh-server removed during bionic->focal upgrade

2020-02-29 Thread Mark Shuttleworth
Public bug reported:

I tested do-release-upgrade -d on a few servers with simple setups. In
both cases, openssh-server was removed. Given that the upgrader warned
me about doing the upgrade over SSH, this was surprising :) I think we
should whitelist openssh-server to ensure it stays installed during an
upgrade.

** Affects: ubuntu-release-upgrader (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/1865309

Title:
  openssh-server removed during bionic->focal upgrade

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

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

[Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

2020-02-28 Thread mark bower
The problem exists on my system:
 Ubuntu 18.04LTS with Gnome Classic Desktop
 ASUS N3050M-E M/B with the Intel N3050 (Braswell) CPU
 VGA video connector (not HDMI)

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

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

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

[Bug 1865131] Re: Evince 3.28.4-0 won't start anymore

2020-02-28 Thread Mark
** Description changed:

  Since a few days evince does not start anymore
  
  I tried reinstalling it but didn't fix it.
  
  If i type evince in terminal I get:
  (evince:10976): dbind-WARNING **: 12:53:45.012: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files
  Segmentation fault (core dumped)
  Don't know if it can be useful.
  If try to open a pdf I get:
  (evince:11711): dbind-WARNING **: 12:58:05.458: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files
  (evince:11719): dbind-WARNING **: 12:58:05.521: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files
  Segmentation fault (core dumped)
  
  I am on Lubuntu 18.04 evince 3.28.4-0
  
  The same issue was reported on evince gitlab but someone (a dev?) said
  that the version is too old to be handled by them and ask here.
  
  https://gitlab.gnome.org/GNOME/evince/issues/1346 that's the original
  report (by another user with the same issue)
+ 
+ Edit: Installing the latest version from Flathub makes evince to run again 
(even though in terminal shows the error below)
+ (evince:2): dbind-WARNING **: 22:11:54.800: AT-SPI: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: 
org.freedesktop.DBus.Error.ServiceUnknown
+ 
+ So while it does not fixes the issue from the affected version, it makes
+ evince usable for users again.

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

Title:
  Evince  3.28.4-0 won't start anymore

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

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

[Bug 1865131] [NEW] Evince 3.28.4-0 won't start anymore

2020-02-28 Thread Mark
Public bug reported:

Since a few days evince does not start anymore

I tried reinstalling it but didn't fix it.

If i type evince in terminal I get:
(evince:10976): dbind-WARNING **: 12:53:45.012: Error retrieving accessibility 
bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus 
was not provided by any .service files
Segmentation fault (core dumped)
Don't know if it can be useful.
If try to open a pdf I get:
(evince:11711): dbind-WARNING **: 12:58:05.458: Error retrieving accessibility 
bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus 
was not provided by any .service files
(evince:11719): dbind-WARNING **: 12:58:05.521: Error retrieving accessibility 
bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus 
was not provided by any .service files
Segmentation fault (core dumped)

I am on Lubuntu 18.04 evince 3.28.4-0

The same issue was reported on evince gitlab but someone (a dev?) said
that the version is too old to be handled by them and ask here.

https://gitlab.gnome.org/GNOME/evince/issues/1346 that's the original
report (by another user with the same issue)

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

Title:
  Evince  3.28.4-0 won't start anymore

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

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

[Bug 1854362] Re: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid, targetcli-fb

2020-02-26 Thread Mark Morlino
I reviewed urwid 2.0.1-2build3 as checked into focal.  This shouldn't be
considered a full audit but rather a quick gauge of maintainability. 

urwid is a console-based display and user interface framework/library
for python 2.7 and 3.4+

- CVE History: 
  - none found
- Build-Depends?
  - nothing troubling found
- pre/post inst/rm scripts?
  - n/a
- init scripts?
  - n/a
- systemd units?
  - n/a
- dbus services?
  - n/a
- setuid binaries?
  - n/a
- binaries in PATH?
  - n/a
- sudo fragments?
  - n/a
- udev rules?
  - n/a
- unit tests / autopkgtests?
  - there are some tests but no autopackage tests. The tests run fine when I 
manually run them but I don't see them running during the build.
- cron jobs?
  - n/a
- Build logs:
  - lintian warns about old python versions

- Processes spawned?
  - the default for Terminal is using the value of SHELL env var as the command
  - it execs a command for it virtual terminal class and some for mouse pointer 
integration
  - it also execs some python for reraising exceptions
- Memory management?
  - n/a
- File IO?
  - paths appear to be constructed safely
  - it's not really getting input from files
  - umask is set to 0 when deamonizing
  - umask not explicitly set for file creation
- Logging?
  - looking isn't used much and looks ok
- Environment variable usage?
  - env is not sanitized
  - this could possibly be misused or produce unanticipated results but that 
isn't happening as used by python-configshell-fb
- Use of privileged functions?
- Use of cryptography / random number sources etc?
  - n/a
- Use of temp files?
  - pipes located in /tmp by default, this isn't being used for our purposed 
right now.
- Use of networking?
  - I didn't focus on this very much becuause urwid as used by 
python-configshell-fb doesn't use networking
  - input is parsed one character at a time.
- Use of WebKit?
- Use of PolicyKit?
  - n/a

- Any significant cppcheck results?
  - No
- Any significant Coverity results?
  - No

Bandit flagged creation of pipes in /tmp in web_display.py as potentially 
unsafe. That functionality of the framework is not being used
by python-configshell-fb but it could probably be improved.

Security team ACK. My recommendation is that the web_display tmp files
be cleaned up to use python's tempfile but I don't think it needs to
block inclusion into main at this time because it isn't being used.


** Changed in: urwid (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb,
  urwid, targetcli-fb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1854362/+subscriptions

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

[Bug 1864567] Re: Ubuntu 20.04 lvm with encryption hang on reboot

2020-02-26 Thread Mark Richards
** Package changed: ubuntu => plymouth (Ubuntu)

** Description changed:

- I've installed 20.04 with lvm and encryption. When rebooting, the dell 
latitude e7470 laptop gets stuck on an ubuntu 20.04 splash screen. I have to 
hard power off and back on to boot back into the system.
+ I've installed 20.04 with lvm and encryption. When rebooting, or powering off 
and back on, the dell latitude e7470 laptop gets stuck on an ubuntu 20.04 
splash screen. I have to power off again or press ctrl+alt+del to get the 
encryption password prompt and be able to boot back into the system.
  This issue does not occur when installing ext4 with no encryption.
  I've attached my boot.log file if this helps. Happy to provide more 
information if needed.

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

Title:
  Ubuntu 20.04 lvm with encryption hang on reboot

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

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

[Bug 1864627] Re: Can't configure Google account

2020-02-25 Thread Mark Fraser
There is also no way of removing my Google account after setting it up.

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

Title:
  Can't configure Google account

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

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

[Bug 1864627] [NEW] Can't configure Google account

2020-02-25 Thread Mark Fraser
Public bug reported:

Adding a Google account in Kubuntu 20.04 either produces an empty window
after entering email and password details or if it does work, there
seems to be no way of reconfiguring the account.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemsettings 4:5.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Feb 25 09:30:35 2020
ExecutablePath: /usr/bin/systemsettings5
InstallationDate: Installed on 2020-02-25 (0 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 LANGUAGE=en_GB
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: systemsettings
UpgradeStatus: Upgraded to focal on 2020-02-25 (0 days ago)
XsessionErrors: (nvidia-settings:3664): GLib-GObject-CRITICAL **: 08:41:57.364: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed

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


** Tags: amd64 apport-bug focal

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

Title:
  Can't configure Google account

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

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

[Bug 1864567] [NEW] Ubuntu 20.04 lvm with encryption hang on reboot

2020-02-24 Thread Mark Richards
Public bug reported:

I've installed 20.04 with lvm and encryption. When rebooting, the dell latitude 
e7470 laptop gets stuck on an ubuntu 20.04 splash screen. I have to hard power 
off and back on to boot back into the system.
This issue does not occur when installing ext4 with no encryption.
I've attached my boot.log file if this helps. Happy to provide more information 
if needed.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: 20.04 encryption hang lvm reboot

** Attachment added: "boot.log"
   https://bugs.launchpad.net/bugs/1864567/+attachment/5330749/+files/boot.log

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

Title:
  Ubuntu 20.04 lvm with encryption hang on reboot

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

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

[Bug 1864558] [NEW] Printer adds automatically at boot with notification or if printer deleted

2020-02-24 Thread Mark Richards
Public bug reported:

When booting 20.04 I get a notification on the logon screen each time
advising that my wireless printer has been setup. If I remove the
printer via settings, then as soon as it's removed, it gets re-added and
I see the same notification as I do on the logon screen about the
printer having been setup. I've attached a screenshot of this
notification.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.35.91-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 24 21:49:43 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-02-24 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221)
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-02-24 21-54-45.png"
   
https://bugs.launchpad.net/bugs/1864558/+attachment/5330734/+files/Screenshot%20from%202020-02-24%2021-54-45.png

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

Title:
  Printer adds automatically at boot with notification or if printer
  deleted

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

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

[Bug 1863100] Re: Move control sockets out of /tmp

2020-02-15 Thread Mark Shuttleworth
Along with the move, please update the default configuration for
/etc/kea/kea-ctrl-agent.conf to refer to the appropriate location

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

Title:
  Move control sockets out of /tmp

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

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

[Bug 1863410] Re: Old isc-kea-common package removal looks dangerous

2020-02-15 Thread Mark Shuttleworth
Here is apt's term.log:

Log started: 2020-02-15  11:52:34
(Reading database ... 138590 files and directories currently installed.)
Purging configuration files for isc-kea-common (1.6.1-isc0042520191119145256) 
...
userdel: user _kea is currently used by process 1435
/usr/sbin/deluser: `/sbin/userdel _kea' returned error code 8. Exiting.
/usr/sbin/delgroup: `_kea' still has `_kea' as their primary group!
Log ended: 2020-02-15  11:52:35

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

Title:
  Old isc-kea-common package removal looks dangerous

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

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

[Bug 1863410] [NEW] Old isc-kea-common package removal looks dangerous

2020-02-15 Thread Mark Shuttleworth
Public bug reported:

I upgraded to kea 1.6 in Focal, and saw an old isc-kea-common package
with configuration files. Removing that threw up a number of
uncomfortable looking error messages about _kea user and group removal
failing. I don't think our transition approach is yet clean.

** Affects: isc-kea (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/1863410

Title:
  Old isc-kea-common package removal looks dangerous

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

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

[Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

2020-02-10 Thread Mark - Syminet
Got bit by this as well, recall fixing it a few years ago but must have
clobbered my changes on upgrade bionic -> eoan?  Having VirtualBox
installed broke it, fix was to comment out this line in
/lib/systemdd/system/systemd-timesyncd.service.d and restart systemd:

ConditionFileIsExecutable=!/usr/sbin/VBoxService

Don't recall being asked about a config file change during upgrade
although maybe it did and didn't remember.  Further info here:

https://askubuntu.com/questions/940311/time-in-ubuntu-16-04-not-
updating-from-internet#1005355

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

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

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

[Bug 1861837] Re: machine doesn't come up after suspend and re-opening the lid

2020-02-04 Thread Mark Pearson
I don't know if it's the same issue - but recently on Debian an issue was found 
with the tpm driver that was preventing suspend and resume working on a number 
of systems:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939170

They saw the issue on X1 4th Gen.

Maybe try blacklisting your tpm driver and see if that makes a
difference?

** Bug watch added: Debian Bug tracker #939170
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939170

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

Title:
  machine doesn't come up after suspend and re-opening the lid

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

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

[Bug 1860827] Re: [snap] chromium does not open

2020-02-03 Thread Mark - Syminet
You can close this, after recent updates it is now opening fine.

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

Title:
  [snap] chromium does not open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860827/+subscriptions

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

[Bug 752773] Re: dash should sort results (apps, files, ...) by relevance

2020-01-30 Thread Mark Jeronimus
The algorithm should use a balance between 'frequency of use' (or maybe
even 'duration of use') and *recency* of last use.

For example, I installed an application yesterday and launched it once.
Today I want to launch it again but forgot the name, and it's not in any
of the 29(!) suggested apps when I type nothing.

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

Title:
  dash should sort results (apps, files, ...) by relevance

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

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

[Bug 1860929] Re: Should include a /usr/bin/python symlink unless..

2020-01-29 Thread Mark Foster
Is this a written policy / guidance or just something you came up with
on the fly?

https://blogs.gnome.org/mcatanzaro/2018/02/16/on-python-shebangs/ has a
good discussion of this issue and even suggests using python2.7 (as
opposed to python2)

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

Title:
  Should include a /usr/bin/python symlink unless..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1860929/+subscriptions

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

[Bug 1860880] [NEW] Gimp crashed

2020-01-25 Thread Mark Freeman
Public bug reported:

```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/7/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-7 
--program-prefix=i686-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto 
--enable-targets=all --enable-multiarch --disable-werror --with-arch-32=i686 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu 
--target=i686-linux-gnu
Thread model: posix
gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) 

using babl version 0.1.72 (compiled against version 0.1.72)
using GEGL version 0.4.18 (compiled against version 0.4.18)
using GLib version 2.56.4 (compiled against version 2.56.4)
using GdkPixbuf version 2.36.11 (compiled against version 2.36.11)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.40.14 (compiled against version 1.40.14)
using Fontconfig version 2.12.6 (compiled against version 2.12.6)
using Cairo version 1.15.10 (compiled against version 1.15.10)

```
> fatal error: Aborted

Stack trace:
```

# Stack traces obtained from PID 15803 - Thread 15803 #

[New LWP 15804]
[New LWP 15810]
[New LWP 15811]
[New LWP 15834]
[New LWP 15962]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
0xb7ef0d09 in __kernel_vsyscall ()
  Id   Target Id Frame 
* 1Thread 0xb61e6d00 (LWP 15803) "gimp-2.10" 0xb7ef0d09 in 
__kernel_vsyscall ()
  2Thread 0xb5c8bb40 (LWP 15804) "worker" 0xb7ef0d09 in __kernel_vsyscall ()
  3Thread 0xb52ffb40 (LWP 15810) "gmain" 0xb7ef0d09 in __kernel_vsyscall ()
  4Thread 0xb48ffb40 (LWP 15811) "gdbus" 0xb7ef0d09 in __kernel_vsyscall ()
  5Thread 0xb0cb1b40 (LWP 15834) "async" 0xb7ef0d09 in __kernel_vsyscall ()
  6Thread 0xb04b0b40 (LWP 15962) "swap writer" 0xb7ef0d09 in 
__kernel_vsyscall ()

Thread 6 (Thread 0xb04b0b40 (LWP 15962)):
#0  0xb7ef0d09 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb6c5d3a7 in syscall () at ../sysdeps/unix/sysv/linux/i386/syscall.S:29
No locals.
#2  0xb6efc11e in g_cond_wait () from /usr/lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0xb73e3ad5 in ?? () from /usr/lib/i386-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#4  0xb6edc66a in ?? () from /usr/lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5  0xb6d4b3bd in start_thread (arg=0xb04b0b40) at pthread_create.c:463
pd = 0xb04b0b40
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1227485184, -1337259200, 
-1227485184, -1337262552, 379444545, 704766796}, mask_was_saved = 0}}, priv = 
{pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 
0}}}
not_first_call = 0
#6  0xb6c61e16 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108
No locals.

Thread 5 (Thread 0xb0cb1b40 (LWP 15834)):
#0  0xb7ef0d09 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb6c5d3a7 in syscall () at ../sysdeps/unix/sysv/linux/i386/syscall.S:29
No locals.
#2  0xb6efc11e in g_cond_wait () from /usr/lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0x007cd346 in ?? ()
No symbol table info available.
#4  0xb6edc66a in ?? () from /usr/lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5  0xb6d4b3bd in start_thread (arg=0xb0cb1b40) at pthread_create.c:463
pd = 0xb0cb1b40
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1227485184, -1328866496, 
-1227485184, -1328869848, 360570176, 704766796}, mask_was_saved = 0}}, priv = 
{pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 
0}}}
not_first_call = 0
#6  0xb6c61e16 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108
No locals.

Thread 4 (Thread 0xb48ffb40 (LWP 15811)):
#0  0xb7ef0d09 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb6c5743b in __GI___poll (fds=0x1df0560, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 
resultvar = 
sc_cancel_oldtype = 0
sc_ret = 
sc_ret = 
nfds = 2

[Bug 1860827] [NEW] chromium does not open

2020-01-24 Thread Mark - Syminet
Public bug reported:

Just upgraded to fossa.  When clicking chromium-browser, title bar
switches to "Chromium Web Browser", spins for awhile and then disappears
nothing opens.

If it helps, running 'chromium-browser' at CLI is:

mark@zynxps:~$ chromium-browser
Failed to move to new namespace: PID namespaces supported, Network namespace 
supported, but failed: errno = Operation not permitted
Trace/breakpoint trap (core dumped)
mark@zynxps:~$

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 79.0.3945.79-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 15:55:10 2020
InstallationDate: Installed on 2018-10-06 (475 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Snap.Changes:
 ID   Status  Spawn  Ready  Summary
 55   Done2020-01-24T12:55:57-08:00  2020-01-24T12:56:26-08:00  Install 
"chromium" snap
 56   Done2020-01-24T14:30:02-08:00  2020-01-24T14:30:02-08:00  Connect 
chromium:password-manager-service to core:password-manager-service
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.117 
(04f0a055010adab4484f7497fbfdbf312c307f1d-refs/branch-heads/3945@{#1019})
Snap.ChromiumVersion: Chromium 79.0.3945.117 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal 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/1860827

Title:
  chromium does not open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860827/+subscriptions

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

[Bug 1860824] [NEW] IMAP with STARTTLS on port 143 is broken

2020-01-24 Thread Mark - Syminet
Public bug reported:

Just upgraded from eoan -> fossa to test.  Incoming mail is configured
to use STARTTLS over port 143 and works fine in eoan and bionic.

But in fossa, upon startup IMAP immediately fails with error message:

'The reported error was "Error performing TLS handshake: An unexpected
TLS packet was received."'

...no incoming mail and none of the folders will open.

Workaround: Switch account configuration to use TLS directly over
dedicated port 993

Then everything works as normal.  But users for whom port 993 is not an
option, no incoming mail or access to their mailfolders.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: evolution 3.34.1-2build1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 15:34:28 2020
InstallationDate: Installed on 2018-10-06 (475 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

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


** Tags: amd64 apport-bug focal 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/1860824

Title:
  IMAP with STARTTLS on port 143 is broken

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

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

[Bug 1860823] Re: IMAP with STARTTLS is broken

2020-01-24 Thread Mark - Syminet
I went ahead and properly filed but 1860824 so this one can be closed.

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

Title:
  IMAP with STARTTLS is broken

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

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

[Bug 1860823] [NEW] IMAP with STARTTLS is broken

2020-01-24 Thread Mark - Syminet
Public bug reported:

Just upgraded from eoan -> fossa to test.  Incoming mail is configured
to use STARTTLS over port 143 and works fine in eoan and bionic.

But in fossa, upon startup IMAP immediately fails with error message:

The reported error was “Error performing TLS handshake: An unexpected
TLS packet was received.”.

...no incoming mail and none of the folders will open.

Workaround: Switch account configuration to use TLS directly over
dedicated port 993

Then everything works as normal.  Users for whom port 993 is not an
option, however, will have no incoming mail or access to any of their
existing mail folders.

** Affects: evolution-exchange (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/1860823

Title:
  IMAP with STARTTLS is broken

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

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

[Bug 1860823] Re: IMAP with STARTTLS is broken

2020-01-24 Thread Mark - Syminet
Somehow this went the the wrong package; hopefully someone can reassign
it was intended to go to the 'evolution' package directly.

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

Title:
  IMAP with STARTTLS is broken

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

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

[Bug 1809262] Re: Missing hooks library

2020-01-18 Thread Mark Shuttleworth
Ran into this today, confirming.

** Changed in: isc-kea (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/1809262

Title:
  Missing hooks library

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

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

[Bug 1858347] Re: Wrong PID-File-Directory in /usr/sbin/keactrl in Ubuntu 20.04 LTS

2020-01-18 Thread Mark Shuttleworth
** Changed in: isc-kea (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/1858347

Title:
  Wrong PID-File-Directory in /usr/sbin/keactrl in Ubuntu 20.04 LTS

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

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

[Bug 1838866] Re: Mailman 2.1: hardcoded site-packages dir prefix doesn't work on some 64 bit filesystem layouts

2020-01-11 Thread Mark Sapiro
** Changed in: mailman
   Status: Fix Committed => Fix Released

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

Title:
  Mailman 2.1: hardcoded site-packages dir prefix doesn't work on some
  64 bit filesystem layouts

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

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

[Bug 1858692] [NEW] ceph-common postinst does not check for ceph user existing externally

2020-01-07 Thread Mark Cunningham
Public bug reported:

If the $SERVER_USER name exists in LDAP outside the server the user will
not exist in /etc/passwd. This will cause the postinst script to attempt
to create the user, which will fail. This user creation/modification
failure then causes the configuration operation to be marked as failed
and prevent the package from completing installation.

Current workaround is to define $SERVER_USER in /etc/default/ceph or
otherwise export a custom value for this into the environment, so that
the postinst script uses a username that does not exist in LDAP, and can
be created within the local system. Ideally there would be a more robust
check for the existence of the $SERVER_USER perhaps using the 'id'
command.

Snippets from /var/lib/dpkg/info/ceph-common.postinst

---
[ -f "/etc/default/ceph" ] && . /etc/default/ceph

[ -z "$SERVER_HOME" ] && SERVER_HOME=/var/lib/ceph
[ -z "$SERVER_USER" ] && SERVER_USER=ceph
[ -z "$SERVER_NAME" ] && SERVER_NAME="Ceph storage service"
[ -z "$SERVER_GROUP" ] && SERVER_GROUP=ceph
[ -z "$SERVER_UID" ] && SERVER_UID=64045  # alloc by Debian base-passwd 
maintainer
[ -z "$SERVER_GID" ] && SERVER_GID=$SERVER_UID
---

---
case "$1" in
configure)
   # create user to avoid running server as root
   # 1. create group if not existing
   if ! getent group | grep -q "^$SERVER_GROUP:" ; then
  addgroup --quiet --system --gid $SERVER_GID \
  $SERVER_GROUP 2>/dev/null ||true
   fi
   # 2. create user if not existing
   if ! getent passwd | grep -q "^$SERVER_USER:"; then
 adduser --quiet \
 --system \
 --no-create-home \
 --disabled-password \
 --uid $SERVER_UID \
 --gid $SERVER_GID \
 $SERVER_USER 2>/dev/null || true
   fi
   # 3. adjust passwd entry
   usermod -c "$SERVER_NAME" \
   -d $SERVER_HOME   \
   -g $SERVER_GROUP  \
   $SERVER_USER 2>/dev/null
---

** Affects: ceph (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/1858692

Title:
  ceph-common postinst does not check for ceph user existing externally

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

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

[Bug 1854849] Re: [MIR] libscalar-list-utils-perl

2020-01-06 Thread Mark Morlino
I reviewed libscalar-list-utils-perl 1:1.53-1 as checked into focal.  This 
shouldn't be
considered a full audit but rather a quick gauge of maintainability. 
The guts of this perl module is in ListUtil.xs which is turned into C code. I 
did run that
portion of the build through coverity, which did not complain about anything I 
found to be
concerning.

libscalar-list-utils-perl is a replacement for the default List::Util 
distribution that
is built into perl core and adds some additional subroutines.

- CVE History:
  - no CVEs found
- Build-Depends:
  - perl
- pre/post inst/rm scripts?
  - not applicable
- init scripts?
  - not applicable
- systemd units?
  - not applicable
- dbus services?
  - not applicable
- setuid binaries?
  - not applicable
- binaries in PATH?
  - not applicable
- sudo fragments?
  - not applicable
- udev rules?
  - not applicable
- unit tests / autopkgtests?
  - there is a fairly comprehensive test suite
- cron jobs?
  - not applicable
- Build logs:
  - Everything looks fine
- Processes spawned?
  - not applicable
- Memory management?
  - I do not see anything that looks problematic
- File IO?
  - not applicable
- Logging?
  - not applicable
- Environment variable usage?
  - not applicable
- Use of privileged functions?
  - not applicable
- Use of cryptography / random number sources etc?
  - not applicable
- Use of temp files?
  - not applicable
- Use of networking?
  - not applicable
- Use of WebKit?
  - not applicable
- Use of PolicyKit?
  - not applicable

- Any significant cppcheck results?
  - not applicable
- Any significant Coverity results?
  - not applicable


Security team ACK for promoting libscalar-list-utils-perl to main.


** Changed in: libscalar-list-utils-perl (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] libscalar-list-utils-perl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libscalar-list-utils-perl/+bug/1854849/+subscriptions

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

[Bug 1853175] Re: [MIR] libmail-authenticationresults-perl

2020-01-06 Thread Mark Morlino
I reviewed libmail-authenticationresults-perl 1.20180923-2 as checked into 
focal.  This shouldn't be
considered a full audit but rather a quick gauge of maintainability. ANY
OTHER NOTES REGARDING THE NATURE OF THE REVIEW ITSELF.

libmail-authenticationresults-perl is a parser for Object Oriented 
Authentication-Results email
headers. It tokenizes the header into a usable set of objects.

- CVE History:
  - I was not able to find any CVE history
- Build-Depends?
  - perl
  - libscalar-list-utils-perl
- pre/post inst/rm scripts?
  - not applicable
- init scripts?
  - not applicable
- systemd units?
  - not applicable
- dbus services?
  - not applicable
- setuid binaries?
  - not applicable
- binaries in PATH?
  - not applicable
- sudo fragments?
  - not applicable
- udev rules?
  - not applicable
- unit tests / autopkgtests?
  - there is a comprehensive test suite
- cron jobs?
  - not applicable
- Build logs:
  - Everything looks fine
- Processes spawned?
  - not applicable
- Memory management?
  - I do not see anything that looks problematic
- File IO?
  - not applicable
- Logging?
  - not applicable
- Environment variable usage?
  - not applicable
- Use of privileged functions?
  - not applicable
- Use of cryptography / random number sources etc?
  - not applicable
- Use of temp files?
  - not applicable
- Use of networking?
  - not applicable
- Use of WebKit?
  - not applicable
- Use of PolicyKit?
  - not applicable

- Any significant cppcheck results?
  - not applicable
- Any significant Coverity results?
  - not applicable

Overall it seems to be cleanly written, organized and well documetned
code. Upstream is not very active. 111 git commits between
2017.12-2018.10 and nothing since then. It is maintained in debian
testing and unstable though.

Security team ACK for promoting libmail-authenticationresults-perl to
main.


** Changed in: libmail-authenticationresults-perl (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] libmail-authenticationresults-perl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmail-authenticationresults-perl/+bug/1853175/+subscriptions

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

[Bug 1857829] [NEW] gnome calender does not respect format settings

2019-12-29 Thread john mark
Public bug reported:

Ubuntu 19.10 (other versions are most likely affected too)

The gnome calender window (inside the notification window) that opens
when you click on the clock on the top does not respect the formating
that was set in the "Region & Language" settings. It only translates
months and days, but formating of my selected langauge is ignored.

I have my "Formats" set to german (and language set to english), so the correct 
formating should be
29. Dezember 2019
but what I actually get is
Dezember 29 2019

Another issues is, the letters used inside the calender to abbreviate the days 
are still displayed in english.
Example:
M T W T F S S
when it should be
M D M D F S S

BOTH of these issues are fixed by switching the system language to
german. This is not how it should be. These things should depend on the
systems format settings, not language.

** Affects: gnome-settings-daemon (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/1857829

Title:
  gnome calender does not respect format settings

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

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

[Bug 1857273] [NEW] discovery says there is updates but command line says no

2019-12-22 Thread Mark Tutone
Public bug reported:

Discover has been giving problems for quite a while now.
This time Discover says I need 4 updates but they will not download and 
discover acts erratically.
I did a command line update and the command line says there are 0 zero updates 
available.
Please see the screenshots that I will attach.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: discover (not installed)
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 22 19:58:28 2019
InstallationDate: Installed on 2017-11-23 (759 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LD_PRELOAD=
 SHELL=/bin/bash
SourcePackage: discover
UpgradeStatus: Upgraded to bionic on 2018-04-28 (603 days ago)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "DiscoveryProblem12-22-2019.png"
   
https://bugs.launchpad.net/bugs/1857273/+attachment/5314671/+files/DiscoveryProblem12-22-2019.png

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

Title:
  discovery says there is updates but command line says no

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

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

[Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

2019-12-16 Thread Mark Haiman
On a new XPS 15 9575 2-in-1 with BIOS 1.8.1, the symptoms are similar to
comment #24.  At the gdm login screen, the keyboard doesn't work at
first but is OK after 20-30 seconds. The touchpad is not affected.  The
Linux 4.15 kernel is not affected but later ones are.  I tried it with
4.18, 5.0 and 5.3 kernels.  I am running Mint 19.2, which uses the
Ubuntu kernels.

If I boot in recovery mode, the keyboard works on the recovery mode menu.  If I 
then exit to normal boot, the unresponsive keyboard recurs.  However, the 
elapsed time until it starts working
again is from the initial boot.  That is, if I wait 30 seconds in recovery mode 
before exiting to normal boot, the keyboard will then be working at the gdm 
screen.

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

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

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

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

[Bug 1841646] Re: White text on white background for HTML e-mail

2019-12-09 Thread Mark - Syminet
When av LTS is relkeased, is is considered according to it's promise: 6 years.  
But yet, after 3.5 years, here we are.  

Someone else said it works fine in Eoan.

...who approved this SRU?

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

Title:
  White text on white background for HTML e-mail

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

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

Re: [Bug 1467335] Re: Metadata for music files is randomly changed

2019-12-06 Thread Mark
Hi,

Thanks for the follow-up. I'm on a different release of Ubuntu now and a
different tag editing application. I do appreciate the reply, though. Thank
you!

Cheers,
Mark


On Fri, Dec 6, 2019 at 9:30 AM Paul White <1467...@bugs.launchpad.net>
wrote:

> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner.
>
> This release of Ubuntu is no longer receiving maintenance updates. If
> this is still an issue using a maintained version of Ubuntu please let
> us know otherwise this report can be left to expire in approximately 60
> days time.
>
> Paul White
> [Ubuntu Bug Squad]
>
> ** Changed in: rhythmbox (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1467335
>
> Title:
>   Metadata for music files is randomly changed
>
> Status in rhythmbox package in Ubuntu:
>   Incomplete
>
> Bug description:
>   On two occasions now I have found that Rhythmbox has tagged music
>   files erroneously that were previously fine in iTunes and Windows 8.
>   Here are two recent examples: track titles display album name or
>   artist name (and the artist/album names are entirely incorrect in and
>   of themselves); all tracks within a single album show Track ID
>   4294967295.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: rhythmbox 3.0.2-0ubuntu2
>   ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11
>   Uname: Linux 3.16.0-41-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.11
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sun Jun 21 15:55:19 2015
>   EcryptfsInUse: Yes
>   ExecutablePath: /usr/bin/rhythmbox
>   InstallationDate: Installed on 2015-06-13 (8 days ago)
>   InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
> (20150218.1)
>   ProcEnviron:
>LANGUAGE=en_US
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: rhythmbox
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1467335/+subscriptions
>

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

Title:
  Metadata for music files is randomly changed

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

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

[Bug 1850876] Re: CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

2019-12-03 Thread Mark Dunn
I think the original 1013 had flicker and tearing before the screen went blank
(the os was still functional - ssh worked).

With your image/modules/buildinfo i get:

uname -a
Linux ubuntu 5.3.0-1013-raspi2 #15+v3d SMP Sun Nov 24 13:41:44 CST 2019 aarch64 
aarch64 aarch64 GNU/Linux

Enlarging the glxgears window: I see flicker between the glxgears window, the 
background and terminal window when they overlap instead of just seeing the top 
one.
It hasn't gone blank ... yet

With pi 4.19 kernel/modules (from https://github.com/raspberrypi/linux)
there is no flicker and the screen has never gone blank.

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

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

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

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

[Bug 1850876] Re: CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

2019-11-29 Thread Mark Dunn
short version:

With raspberry pi 4:
your binaries applied (https://people.canonical.com/~hwang4/v3d-fix/)
The screen flickers then blanks
I installed an built the latest mesa 
The screen flickers then blanks
Back to the raspberry pi kernel (4.19) 
Which still works...

long version:

downloaded ubuntu-19.10-preinstalled-server-arm64+raspi3.img and
restored it to sdcard

sudo apt update
sudo apt upgrade
sudo apt install ubuntu-desktop

wget 
https://people.canonical.com/~hwang4/v3d-fix/linux-buildinfo-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
wget 
https://people.canonical.com/~hwang4/v3d-fix/linux-headers-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
wget 
https://people.canonical.com/~hwang4/v3d-fix/linux-image-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
wget 
https://people.canonical.com/~hwang4/v3d-fix/linux-modules-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb

sudo dpkg -i linux-modules-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
sudo dpkg -i linux-image-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
sudo dpkg -i linux-buildinfo-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb

sudo dpkg -i linux-headers-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
 linux-headers-5.3.0-1013-raspi2 depends on linux-raspi2-headers-5.3.0-1013; 
however:
  Package linux-raspi2-headers-5.3.0-1013 is not installed.
sudo apt --fix-broken install
The following packages will be REMOVED:
  linux-headers-5.3.0-1013-raspi2

sudo reboot
sudo apt-get install mesa-utils

glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Broadcom (0x14e4)
Device: V3D 4.2 (0x)
Version: 19.2.1
Accelerated: yes
Video memory: 3791MB
Unified memory: yes
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL vendor string: Broadcom
OpenGL renderer string: V3D 4.2
OpenGL version string: 2.1 Mesa 19.2.1
OpenGL shading language version string: 1.20

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

glxgears

Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
348 frames in 5.0 seconds = 69.440 FPS
247 frames in 5.0 seconds = 49.358 FPS
301 frames in 5.0 seconds = 60.029 FPS
301 frames in 5.0 seconds = 60.019 FPS
300 frames in 5.0 seconds = 59.999 FPS
300 frames in 5.0 seconds = 59.992 FPS
256 frames in 5.0 seconds = 51.041 FPS
300 frames in 5.0 seconds = 59.989 FPS
301 frames in 5.0 seconds = 60.011 FPS
X connection to :0 broken (explicit kill or server shutdown).

Eventually screen starts to flicker then blanks...
built and installed latest mesa - no change

sudo nano /etc/apt/sources.list   (commented in all sources)
sudo apt update
sudo apt-get build-dep mesa

mkdir git
cd git
sudo apt-get build-dep mesa
sudo apt-get install -y pkg-config bison flex 

git clone https://gitlab.freedesktop.org/mesa/drm.git
cd drm
meson build --prefix=/usr --libdir=/usr/lib/aarch64-linux-gnu
ninja -C build
sudo ninja -C build install
cd ..

git clone https://gitlab.freedesktop.org/mesa/mesa.git
cd mesa
meson build \
--prefix=/usr \
--libdir=/usr/lib/aarch64-linux-gnu \
-Dbuildtype=release \
-Dplatforms=x11,drm,surfaceless \
-Ddri-drivers= \
-Dgallium-drivers=vc4,v3d,kmsro
ninja -C build
sudo ninja -C build install

sudo reboot

flickers and then blanks :(

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

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

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

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

[Bug 1853679] [NEW] One package downloaded and installed without password two did not download or install

2019-11-22 Thread Mark Tutone
Public bug reported:

Opened Discover for downloads and one package downloaded and installed
but two others were not installed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: discover (not installed)
ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
Uname: Linux 4.15.0-70-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Nov 22 22:45:05 2019
InstallationDate: Installed on 2017-11-23 (729 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: discover
UpgradeStatus: Upgraded to bionic on 2018-04-28 (573 days ago)

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


** Tags: amd64 apport-bug bionic

** Patch added: "These two did not download and install"
   
https://bugs.launchpad.net/bugs/1853679/+attachment/5307230/+files/bug112220192250.png

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

Title:
  One package downloaded and installed without password  two did not
  download or install

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

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

[Bug 1852922] Re: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285

2019-11-18 Thread Mark
Please find the attached dumpfile

** Attachment added: "RtHDDump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+attachment/5306147/+files/RtHDDump.txt

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

Title:
  Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3,
  Laptop HP Envy 13, Realtek ALC285

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

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

[Bug 1852922] Re: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285

2019-11-17 Thread Mark
Yes, the internal microphone works perfectly fine in Windows 10 and is
being detected as Intel Smart Sound

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

Title:
  Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3,
  Laptop HP Envy 13, Realtek ALC285

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

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

[Bug 1852922] [NEW] Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285

2019-11-17 Thread Mark
Public bug reported:

I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13.
Everything works just fine except the microphone which is not being
detected at all.

My alsa-info output: http://alsa-
project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2

System info:

Description:Ubuntu 19.10
Release:19.10

Alsa version:

alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu5
  Candidate: 1.0.25+dfsg-0ubuntu5
  Version table:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages
100 /var/lib/dpkg/status

** Affects: alsa-driver (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/1852922

Title:
  Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3,
  Laptop HP Envy 13, Realtek ALC285

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

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

[Bug 1850876] Re: CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

2019-11-13 Thread Mark Dunn
I tried upgrading from eoan-proposed, but it isn't there yet on the
arm64 when is the next release please ?

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

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

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

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

[Bug 1841646] Re: White text on white background for HTML e-mail

2019-11-11 Thread Mark - Syminet
Thanks, was really surprised to see this happen in an LTS release.  Any
Ubuntu devs reading this, can we get a backport?

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

Title:
  White text on white background for HTML e-mail

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

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

[Bug 1841646] Re: White text on white background for HTML e-mail

2019-11-10 Thread Mark - Syminet
Same behavior here, after unattended upgrade.  This renders Evolution
pretty much unusable with dark theme.

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

Title:
  White text on white background for HTML e-mail

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

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

[Bug 1851858] Re: adds ESM to sources.list.d unconditionally, despite it being x86-only

2019-11-08 Thread Mark Morlino
This seems to require a 2-part fix:
1. The ubuntu-advantage-tools client should be changed, only x86 is supported 
by ESM.
2. Empty Release files can be added so that trusty machines of other 
architectures that have already been setup with ESM by the new ua tool can run 
apt without errors

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

Title:
  adds ESM to sources.list.d unconditionally, despite it being x86-only

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

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

[Bug 1848892] Re: "error: Unknown TPM error." after upgrading to grub 2.04

2019-11-07 Thread Mark Rijckenberg
@Adam Conrad (adconrad) : thanks for the updated packages. Seems to be
solved now on my laptop. My laptop can now successfully enable TPM and
Secure boot at the same time during boot

HP-EliteBook-820-G4 ~> dmesg|egrep 'ecure|tpm|TPM'
[0.00] efi:  ACPI=0xd9ffe000  ACPI 2.0=0xd9ffe014  
TPMFinalLog=0xd9f76000  SMBIOS=0xd9765000  SMBIOS 3.0=0xd9763000  
MEMATTR=0xd63c0018  ESRT=0xd9766b18  TPMEventLog=0xc50a8018 
[0.00] secureboot: Secure boot enabled
[0.00] Kernel is locked down from EFI secure boot; see man 
kernel_lockdown.7
[0.016255] ACPI: TPM2 0xD9FEB000 34 (v03 HPQOEM EDK2 
0002  0113)
[4.068308] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1B, rev-id 16)
[4.158924] integrity: Loaded X.509 cert 'Hewlett-Packard Company: HP UEFI 
Secure Boot 2013 DB key:

HP-EliteBook-820-G4:~$ apt-cache policy grub2-common grub2
grub2-common:
  Installed: 2.04-1ubuntu12.1
  Candidate: 2.04-1ubuntu12.1
  Version table:
 *** 2.04-1ubuntu12.1 100
100 /var/lib/dpkg/status
 2.04-1ubuntu12 500
500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
grub2:
  Installed: 2.04-1ubuntu12.1
  Candidate: 2.04-1ubuntu12.1
  Version table:
 *** 2.04-1ubuntu12.1 100
100 /var/lib/dpkg/status
 2.04-1ubuntu12 500
500 http://de.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages

$ uname -a
HP-EliteBook-820-G4 5.3.0-21-generic #22-Ubuntu SMP Tue Oct 29 22:55:51 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  "error: Unknown TPM error." after upgrading to grub 2.04

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

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

[Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-11-06 Thread mark kowski
Also interesting idea - especially if you need data from extensions
(which I miss too and I didn't try to recover). Also +1 for
blocking/removing this build from download sources. It's too dangerous
for now ;).

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

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

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

[Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-11-05 Thread mark kowski
Yep - fully agree - beta for testing (or for hardcore daily users ;).
Any chances for fix anytime soon anyway?

@j127 - downgrade to latest stable version, find your profile folder 
(about:profiles), open the folder with your new profile and copy/paste proper 
files from old profile (passwords, database, cookies, history, bookmarks): 
https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data.
Close browser, run again and you have temporary solution for using part of your 
private data on old version of FF. As mentioned above - you can't use your full 
new profile folder with older version of FF so you need to manually overwrite 
dedicated files.
Hope it helps :)!

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

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

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

[Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-10-31 Thread mark kowski
Thanks for info - I didn't know that profiles are forward-compatible
only.

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

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

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

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

2019-10-31 Thread Mark Dunn
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790

I have tried the v3d.ko with latest stable version of mesa
19.2 
Which works well. glxinfo is the application to show everything is working and 
it produces 
 ...Accelerated: yes
for a fast graphical interface

However Chromium 78.0.3904.70 snap fails for some reason
I am using a workaround until it is fixed 
   chromium -use-gl=egl 

The chromium-browser 76.0.3809.100 (from ubuntu 19.04) worked OK

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

Title:
  Raspberry Pi 4 - USB Bus not detecting any devices

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

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

<    2   3   4   5   6   7   8   9   10   11   >