[Bug 1966588] [NEW] Huge numbers of newlines in bash after snap install command

[Jeroen Baten]

Public bug reported:

Hi,

This is a completely fresh install on my laptop with the latest 22.04
beta.

There is a snap apt package as well as a snap snap package installed:
napd  2.54.415177  latest/stablecanonical✓  
snapd
snapd-desktop-integration  0.1   7  latest/stable/…  canonical✓ 
 -

After doing something like snap install I get the dialog to enter password for 
elevated rights.
At the same time my bash commandline gets a huge number of newlines from 
somewhere.

Thought you might like to know.

Regards,
Jeroen Baten

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: snapd 2.55.2+22.04
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 27 15:01:08 2022
InstallationDate: Installed on 2022-03-27 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Snap.Changes: no changes found
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Huge numbers of newlines in bash after snap install command

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


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

[Bug 1571533] Re: Cannot use my dual-monitor setup via docking station anymore

[Jeroen Ruigrok van der Werven]

It's been six years. I do not have access to that hardware setup
anymore, sorry.

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

Title:
  Cannot use my dual-monitor setup via docking station anymore

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


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

[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04

[Jeroen]

What exact version of the mainland kernel would you recommend?

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

Title:
  WD19 dock stops working in Ubuntu 21.04

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


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

[Bug 1935778] Re: [SRU] Request LLVM 12.0.1 backport to focal/updates

[Jeroen van Rijn | Odin-Lang.org]

Hi Timo,

I am happy to report that https://launchpad.net/ubuntu/+source/llvm-
toolchain-12/1:12.0.0-3ubuntu1~20.04.4 does indeed fix the problem.
Odin's LLVM branch builds against it and passes its test suite.

Enabling proposed on Focal did not show any upgrades for LLVM. I ended
up downloading and installing the build artifacts manually with `dpkg
-i`. It worked fine.

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

Title:
  [SRU] Request LLVM 12.0.1 backport to focal/updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1935778/+subscriptions


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

[Bug 1935778] Re: [SRU] Request LLVM 12.0.1 backport to focal/updates

[Jeroen van Rijn | Odin-Lang.org]

Thank you, Timo.

I'll test it this weekend and update the bug report with my findings as
outlined.

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

Title:
  [SRU] Request LLVM 12.0.1 backport to focal/updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1935778/+subscriptions


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

[Bug 1935778] Re: [SRU] Request LLVM 12.0.1 backport to focal/updates

[Jeroen van Rijn | Odin-Lang.org]

I can certainly do that. Much obliged. :-)

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

Title:
  [SRU] Request LLVM 12.0.1 backport to focal/updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1935778/+subscriptions


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

[Bug 1935778] Re: [SRU] Request LLVM 12.0.1 backport to focal/updates

[Jeroen van Rijn | Odin-Lang.org]

Thank you for your work on this, Gianfranco.

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

Title:
  [SRU] Request LLVM 12.0.1 backport to focal/updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1935778/+subscriptions


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

[Bug 1935778] [NEW] Request LLVM 12.0.1 backport to focal/updates

[Jeroen van Rijn | Odin-Lang.org]

Public bug reported:

Hi,

Focal Fossa currently carries LLVM 12.0.0, which has a bug in its C API
that renders it unusable as a backend for some compilers.

The upstream commit that fixes the bug is https://github.com/llvm/llvm-
project/commit/07234c7d6bc246925710b88a1f9552f678587165 and was included
in their 12.0.1 release.

Would you be so kind as to backport 12.0.1 to Ubuntu 20.04 LTS, please?

Thanks in advance for your reply.

** Affects: llvm-toolchain-12 (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/1935778

Title:
  Request LLVM 12.0.1 backport to focal/updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1935778/+subscriptions

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

[Bug 1880245] Re: Error loading extension ubuntu-shell-extension-move-clock

[Jeroen P]

I've found a patch here which works:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-move-
clock/+bug/1816834

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

Title:
  Error loading extension ubuntu-shell-extension-move-clock

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

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

[Bug 1880245] Re: Error loading extension ubuntu-shell-extension-move-clock

[Jeroen P]

PS I have the following versions:

Package: gnome-shell-extension-move-clock
Version: 1.01-2

Ubuntu 20.04.2 LTS

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

Title:
  Error loading extension ubuntu-shell-extension-move-clock

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

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

[Bug 1880245] Re: Error loading extension ubuntu-shell-extension-move-clock

[Jeroen P]

A bit more readable

JS WARNING: 
[/usr/share/gnome-shell/extensions/move_cl...@jonathan.bluemosh.com/extension.js
 13]: reference to undefined property "panel"
JS ERROR: Extension move_cl...@jonathan.bluemosh.com: TypeError: 
SessionMode._modes[mode].panel is undefined
enable@/usr/share/gnome-shell/extensions/move_cl...@jonathan.bluemosh.com/extension.js:13:18
_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:167:32
loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:349:26
_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:599:18
collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17
_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:574:19
_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:608:18
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:639:18
init@resource:///org/gnome/shell/ui/extensionSystem.js:56:14
_initializeUI@resource:///org/gnome/shell/ui/main.js:257:22
start@resource:///org/gnome/shell/ui/main.js:146:5
@:1:47

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

Title:
  Error loading extension ubuntu-shell-extension-move-clock

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

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

[Bug 1880245] Re: Error loading extension ubuntu-shell-extension-move-clock

[Jeroen P]

This is what I've been able to find in my logs (I'm a newbie, not sure
if this is all relevant).

JS WARNING: 
[/usr/share/gnome-shell/extensions/move_cl...@jonathan.bluemosh.com/extension.js
 13]: reference to undefined property "panel"
  JS ERROR: Extension 
move_cl...@jonathan.bluemosh.com: TypeError: SessionMode._modes[mode].panel is 
undefined
  
enable@/usr/share/gnome-shell/extensions/move_cl...@jonathan.bluemosh.com/extension.js:13:18
  
_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:167:32
  
loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:349:26
  
_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:599:18
  
collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17
  
_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:574:19
  
_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:608:18
  
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:639:18
  
init@resource:///org/gnome/shell/ui/extensionSystem.js:56:14
  
_initializeUI@resource:///org/gnome/shell/ui/main.js:257:22
  
start@resource:///org/gnome/shell/ui/main.js:146:5
  @:1:47

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

Title:
  Error loading extension ubuntu-shell-extension-move-clock

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

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

[Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode

[Jeroen Bobbeldijk]

Thanks Łukasz! 
It might be a bit problematic for me to test this in the same situation as I 
already upgraded my BIOS version, so I'm not having this issue anymore. 
Of course I can still test it in my current setup, but that does not hang while 
booting because the latest microcode is already loaded by BIOS.

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

Title:
  Add "dis_ucode_ldr" to linux boot options for Recovery Mode

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

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

[Bug 1888090] Re: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r

[Jeroen Baten]

IMHO kernel version 5.4.0-40 should be deleted with the highest prejudice.
Never before have I experienced 3 kernel panics in one day and a few after that.
This thing should have never left Canonical quality control for an LTS system.
And I have been running Ubuntu since the first release.


Jul 15 00:00:19 inzicht kernel: [21701.634416] [ cut here 
]
Jul 15 00:00:19 inzicht kernel: [21701.634421] percpu ref 
(cgroup_bpf_release_fn) <= 0 (-1) after switching to atomic
Jul 15 00:00:19 inzicht kernel: [21701.634432] WARNING: CPU: 4 PID: 0 at 
lib/percpu-refcount.c:160 percpu_ref_switch_to_atomic_rcu+0x12e/0x140
Jul 15 00:00:19 inzicht kernel: [21701.634433] Modules linked in: unix_diag 
veth vhost_net vhost tap tcp_diag inet_diag xt_nat nf_conntrack_netlink 
xfrm_user xfrm_algo xt_addrtype br_netfilter aufs bluetooth ecdh_generic ecc 
xt_CHECKSUM xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle 
ip6table_nat iptable_mangle nf_tables nfnetlink ip6table_filter ip6_tables 
iptable_filter rdma_ucm ib_uverbs overlay iptable_nat xt_MASQUERADE nf_nat 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bpfilter bridge stp llc binfmt_misc 
snd_hda_codec_hdmi xfs edac_mce_amd snd_hda_codec_realtek kvm_amd 
snd_hda_codec_generic ledtrig_audio kvm snd_hda_intel snd_intel_dspcfg 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event 
nls_iso8859_1 input_leds snd_rawmidi snd_seq snd_seq_device crct10dif_pclmul 
snd_timer eeepc_wmi usblp asus_wmi ghash_clmulni_intel snd wmi_bmof 
sparse_keymap ccp k10temp soundcore mac_hid sch_fq_codel cuse ib_iser rdma_cm 
iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi
Jul 15 00:00:19 inzicht kernel: [21701.634460]  scsi_transport_iscsi lm78 
hwmon_vid parport_pc ppdev lp parport nfsd auth_rpcgss nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid0 multipath linear raid1 hid_generic usbhid hid nouveau mxm_wmi 
video crc32_pclmul i2c_algo_bit ttm aesni_intel drm_kms_helper glue_helper 
crypto_simd syscopyarea sysfillrect sysimgblt cryptd fb_sys_fops drm r8169 
e1000e i2c_piix4 nvme ahci realtek nvme_core libahci wmi gpio_amdpt gpio_generic
Jul 15 00:00:19 inzicht kernel: [21701.634480] CPU: 4 PID: 0 Comm: swapper/4 
Not tainted 5.4.0-40-generic #44-Ubuntu
Jul 15 00:00:19 inzicht kernel: [21701.634481] Hardware name: System 
manufacturer System Product Name/PRIME B450-PLUS, BIOS 2008 12/06/2019
Jul 15 00:00:19 inzicht kernel: [21701.634482] RIP: 
0010:percpu_ref_switch_to_atomic_rcu+0x12e/0x140
Jul 15 00:00:19 inzicht kernel: [21701.634484] Code: 80 3d 17 43 2e 01 00 0f 85 
57 ff ff ff 49 8b 54 24 d8 49 8b 74 24 e8 48 c7 c7 30 e8 5a b6 c6 05 f9 42 2e 
01 01 e8 2d 7e b7 ff <0f> 0b e9 33 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 55 
48 89 e5
Jul 15 00:00:19 inzicht kernel: [21701.634484] RSP: 0018:aa5dc02fce70 
EFLAGS: 00010282
Jul 15 00:00:19 inzicht kernel: [21701.634485] RAX:  RBX: 
7ffe RCX: 
Jul 15 00:00:19 inzicht kernel: [21701.634486] RDX: 0006 RSI: 
b6d945e6 RDI: 0246
Jul 15 00:00:19 inzicht kernel: [21701.634486] RBP: aa5dc02fce88 R08: 
b6d945a0 R09: 0046
Jul 15 00:00:19 inzicht kernel: [21701.634487] R10:  R11: 
b6d945ab R12: 8b661feb18e8
Jul 15 00:00:19 inzicht kernel: [21701.634487] R13: 3ef75f603760 R14: 
8b665acf2e80 R15: 8b665e92bad0
Jul 15 00:00:19 inzicht kernel: [21701.634488] FS:  () 
GS:8b665e90() knlGS:
Jul 15 00:00:19 inzicht kernel: [21701.634489] CS:  0010 DS:  ES:  CR0: 
80050033
Jul 15 00:00:19 inzicht kernel: [21701.634489] CR2: 55f9f5584de8 CR3: 
0007f0296000 CR4: 00340ee0
Jul 15 00:00:19 inzicht kernel: [21701.634490] Call Trace:
Jul 15 00:00:19 inzicht kernel: [21701.634491]  
Jul 15 00:00:19 inzicht kernel: [21701.634494]  rcu_do_batch+0x12c/0x2b0
Jul 15 00:00:19 inzicht kernel: [21701.634496]  rcu_core+0xf4/0x270
Jul 15 00:00:19 inzicht kernel: [21701.634497]  rcu_core_si+0xe/0x10
Jul 15 00:00:19 inzicht kernel: [21701.634499]  __do_softirq+0xe1/0x2d6
Jul 15 00:00:19 inzicht kernel: [21701.634500]  ? hrtimer_interrupt+0x13b/0x220
Jul 15 00:00:19 inzicht kernel: [21701.634502]  irq_exit+0xae/0xb0
Jul 15 00:00:19 inzicht kernel: [21701.634503]  
smp_apic_timer_interrupt+0x7b/0x140
Jul 15 00:00:19 inzicht kernel: [21701.634505]  apic_timer_interrupt+0xf/0x20
Jul 15 00:00:19 inzicht kernel: [21701.634505]  
Jul 15 00:00:19 inzicht kernel: [21701.634507] RIP: 
0010:cpuidle_enter_state+0xc5/0x450
Jul 15 00:00:19 inzicht kernel: [21701.634508] Code: ff e8 cf 08 81 ff 80 7d c7 
00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 22 6c 87 ff 
fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d 
c8 48 8d
Jul 15 00:00:19 

[Bug 1890190] [NEW] package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug

[Jeroen Schwab]

Public bug reported:

don't know

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.2
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Aug  3 20:34:56 2020
ErrorMessage: subproces van pakket initramfs-tools werd script 
post-installation geïnstalleerd gaf de foutwaarde 1 terug
InstallationDate: Installed on 2014-03-02 (2346 days ago)
InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 
subproces van pakket initramfs-tools werd script post-installation 
geïnstalleerd gaf de foutwaarde 1 terug
UpgradeStatus: Upgraded to focal on 2020-08-03 (0 days ago)

** Affects: initramfs-tools (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/1890190

Title:
  package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade:
  subproces van pakket initramfs-tools werd script post-installation
  geïnstalleerd gaf de foutwaarde 1 terug

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

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

[Bug 1871645] [NEW] After update stuck in lock-screen

[Jeroen Rosier]

Public bug reported:

After a clean install of ubuntu 20.04 beta, I updated the system, after
the update was processed the system directed me to locked-screen. I was
unable to log back in, or to reboot or shutdown because the system said
i was still logged in. After a REISUB it would finally reboot :-)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-manager 1:20.04.4
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  8 15:52:47 2020
GsettingsChanges:
 b'com.ubuntu.update-manager' b'window-width' b'645'
 b'com.ubuntu.update-manager' b'launch-count' b'2'
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'launch-time' b'int64 1586353780'
InstallationDate: Installed on 2020-04-08 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: update-manager (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/1871645

Title:
  After update stuck in lock-screen

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

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

[Bug 433231] Re: xorg: directory "/usr/share/fonts/X11/cyrillic" does not exist.

[Jeroen]

sudo apt-get install xfonts-cyrillic fixed it on ubuntu 18.04

** Changed in: xorg (Ubuntu)
   Status: Invalid => New

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

Title:
  xorg: directory "/usr/share/fonts/X11/cyrillic" does not exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/433231/+subscriptions

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

[Bug 1868374] UdevDb.txt

[Jeroen Bobbeldijk]

apport information

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] Lsusb.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] RfKill.txt

[Jeroen Bobbeldijk]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1868374/+attachment/5339669/+files/RfKill.txt

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] ProcEnviron.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] IwConfig.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] ProcCpuinfo.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] ProcModules.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] ProcCpuinfoMinimal.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] Lspci.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] PulseList.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] CurrentDmesg.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] ProcInterrupts.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] Re: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios

[Jeroen Bobbeldijk]

apport information

** Tags added: apport-collected

** Description changed:

  When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook
  UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest
  BIOS (UX450FDX.313), the laptop keeps getting events to change the
  display mode (FN+F8), when having an external monitor connected this
  makes the laptop unusable, as the gnome mode selector keeps popping up.
  When not using an external monitor it seriously hinders/slows down
  keyboard input.
  
  When I revert back to the previous BIOS (UX450FDX.307) everything is
  fine again. What's odd is that when I use the FN+F8 button now I don't
  get this gnome mode selector, it just changes the mode right away.
  
  I'm guessing this is a bug in the kernel asus-wmi driver. I checked the
  history of the kernel for the file "drivers/platform/x86/asus-wmi.c",
  but I don't see anything that could have fixed this in 5.3+ kernels.
  
  I'm willing to upgrade bios/kernel and/or test experimental drivers in
  order to fix this.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  Date: Sat Mar 21 13:45:47 2020
  InstallationDate: Installed on 2019-05-01 (324 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.12
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  jeroen 2488 F pulseaudio
+  /dev/snd/controlC0:  jeroen 2488 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2019-05-01 (324 days ago)
+ InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
+ MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-42-generic N/A
+  linux-backports-modules-5.3.0-42-generic  N/A
+  linux-firmware1.173.16
+ Tags:  bionic
+ Uname: Linux 5.3.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: docker plugdev sudo
+ WifiSyslog:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 07/05/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX450FDX.307
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX450FDX
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: ZenBook
+ dmi.product.name: ZenBook UX450FDX_UX480FD
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] CRDA.txt

[Jeroen Bobbeldijk]

apport information

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

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1868374] [NEW] Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios

[Jeroen Bobbeldijk]

Public bug reported:

When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook
UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest
BIOS (UX450FDX.313), the laptop keeps getting events to change the
display mode (FN+F8), when having an external monitor connected this
makes the laptop unusable, as the gnome mode selector keeps popping up.
When not using an external monitor it seriously hinders/slows down
keyboard input.

When I revert back to the previous BIOS (UX450FDX.307) everything is
fine again. What's odd is that when I use the FN+F8 button now I don't
get this gnome mode selector, it just changes the mode right away.

I'm guessing this is a bug in the kernel asus-wmi driver. I checked the
history of the kernel for the file "drivers/platform/x86/asus-wmi.c",
but I don't see anything that could have fixed this in 5.3+ kernels.

I'm willing to upgrade bios/kernel and/or test experimental drivers in
order to fix this.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1
ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
Date: Sat Mar 21 13:45:47 2020
InstallationDate: Installed on 2019-05-01 (324 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  Asus WMI hotkey driver bug: External display mode button seems "stuck"
  on the latest bios

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

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

[Bug 1860277] [NEW] Failed mysql upgrade to 8.0 which is part of Ubuntu 19.10 upgrade cannot be repaired due to mysql-5.7 being unavailable after upgrade to Ubuntu 19.10

[Jeroen Van den Keybus]

Public bug reported:

Title says it all.

Although mysql_upgrade was run successfully on the original 5.7 database
files, the in-place upgrade ran into trouble (invalid key field),
causing mysql-8.0 to be unable to complete the table upgrade and
generate the DD tables.

There is no way to repair this, as mysql-5.7, which is the only package
that can operate on the database, is unavailable after the upgrade to
Ubuntu 19.10.

The request is to keep mysql-5.7 available in Ubuntu 19.10, at least to
be able to fix upgrade errors.

Thanks.

** Affects: mysql-8.0 (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/1860277

Title:
  Failed mysql upgrade to 8.0 which is part of Ubuntu 19.10 upgrade
  cannot be repaired due to mysql-5.7 being unavailable after upgrade to
  Ubuntu 19.10

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

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

[Bug 1851833] Re: [Sager Clevo notebook model PB50_70RF, RD, RC] Unable to adjust brightness of backlight

[Jeroen Bruinink]

Yes it does

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

Title:
  [Sager Clevo notebook model PB50_70RF,RD,RC] Unable to adjust
  brightness of backlight

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

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

[Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

[Jeroen Roumen]

@thorstenr-42: Also have a nfc model so still facing the same dead touchpad 
issues.
I've never built a custom kernel before, just loaded a kernel module for a wifi 
nic that didn't have drivers in the kernel. How do you go about building and 
running this?

Also I'm wondering what would be necessary, or what I can do, to finally
get these patches upstream?

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

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

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

[Bug 1851833] [NEW] Unable to adjust brightness of backlight

[Jeroen Bruinink]

Public bug reported:

I am unable to adjust the brightness of the backlight of my laptop
screen either by using the slider of by changing the value in
/sys/class/backlight/intel_backlight/brightness directly.

I have tried changing my GRUB configuration:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
But that did not help.

I am using Ubuntu 19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  8 14:03:33 2019
DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1]
 NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] [1558:65d1]
InstallationDate: Installed on 2019-10-09 (30 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Notebook PB50_70RF,RD,RC
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago)
dmi.bios.date: 02/01/2019
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.07
dmi.board.asset.tag: Tag 12345
dmi.board.name: PB50_70RF,RD,RC
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: PB50_70RF,RD,RC
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan ubuntu

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

Title:
  Unable to adjust brightness of backlight

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

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

[Bug 1837038] Re: Broken and defunct libv8-3.14 urgently needs removal

[Jeroen Ooms]

It looks like the problem has been solved upstream by Debian who has
removed this package from sid.

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

Title:
  Broken and defunct libv8-3.14 urgently needs removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libv8-3.14/+bug/1837038/+subscriptions

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

[Bug 1837038] Re: Broken and defunct libv8-3.14 urgently needs removal

[Jeroen Ooms]

In the latest versions of Debian/Ubuntu, postgresql-10-plv8 has already
been removed and r-cran-v8 has been ported to use the working v8
provided by libnode: https://packages.ubuntu.com/eoan/r-cran-v8

So this only leaves 'uwsgi-plugin-v8'. In Debian this package has been
removed from the stable distributions, but it is still in 'unstable'. I
am not sure what this package does but it can not possibly work because
libv8-314 crashes when you try to initiate it.

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

Title:
  Broken and defunct libv8-3.14 urgently needs removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libv8-3.14/+bug/1837038/+subscriptions

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

[Bug 1837038] Re: Broken and defunct libv8-3.14 urgently needs removal

[Jeroen Ooms]

Is there somebody that can take a look at this? Again libv8-3.14 crashes
on start, has a lot of security issues and has been removed from Debian
stable.

What's worse is that libv8-3.14 is masking the working version of
libv8-dev from libnode-dev.

Copying from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773671:

The following vulnerabilities were published for libv8-3.14.

CVE-2013-2632[0]:
| Google V8 before 3.17.13, as used in Google Chrome before 27.0.1444.3,
| allows remote attackers to cause a denial of service (application
| crash) or possibly have unspecified other impact via crafted
| JavaScript code, as demonstrated by the Bejeweled game.

CVE-2013-2838[1]:
| Google V8, as used in Google Chrome before 27.0.1453.93, allows remote
| attackers to cause a denial of service (out-of-bounds read) via
| unspecified vectors.

CVE-2013-2882[2]:
| Google V8, as used in Google Chrome before 28.0.1500.95, allows remote
| attackers to cause a denial of service or possibly have unspecified
| other impact via vectors that leverage "type confusion."

CVE-2013-2919[3]:
| Google V8, as used in Google Chrome before 30.0.1599.66, allows remote
| attackers to cause a denial of service (memory corruption) or possibly
| have unspecified other impact via unknown vectors.

CVE-2013-6638[4]:
| Multiple buffer overflows in runtime.cc in Google V8 before 3.22.24.7,
| as used in Google Chrome before 31.0.1650.63, allow remote attackers
| to cause a denial of service or possibly have unspecified other impact
| via vectors that trigger a large typed array, related to the (1)
| Runtime_TypedArrayInitialize and (2)
| Runtime_TypedArrayInitializeFromArrayLike functions.

CVE-2013-6639[5]:
| The DehoistArrayIndex function in hydrogen-dehoist.cc (aka
| hydrogen.cc) in Google V8 before 3.22.24.7, as used in Google Chrome
| before 31.0.1650.63, allows remote attackers to cause a denial of
| service (out-of-bounds write) or possibly have unspecified other
| impact via JavaScript code that sets the value of an array element
| with a crafted index.

CVE-2013-6640[6]:
| The DehoistArrayIndex function in hydrogen-dehoist.cc (aka
| hydrogen.cc) in Google V8 before 3.22.24.7, as used in Google Chrome
| before 31.0.1650.63, allows remote attackers to cause a denial of
| service (out-of-bounds read) via JavaScript code that sets a variable
| to the value of an array element with a crafted index.

CVE-2013-6649[7]:
| Use-after-free vulnerability in the RenderSVGImage::paint function in
| core/rendering/svg/RenderSVGImage.cpp in Blink, as used in Google
| Chrome before 32.0.1700.102, allows remote attackers to cause a denial
| of service or possibly have unspecified other impact via vectors
| involving a zero-size SVG image.

CVE-2013-6650[8]:
| The StoreBuffer::ExemptPopularPages function in store-buffer.cc in
| Google V8 before 3.22.24.16, as used in Google Chrome before
| 32.0.1700.102, allows remote attackers to cause a denial of service
| (memory corruption) or possibly have unspecified other impact via
| vectors that trigger incorrect handling of "popular pages."

CVE-2013-6668[9]:
| Multiple unspecified vulnerabilities in Google V8 before 3.24.35.10,
| as used in Google Chrome before 33.0.1750.146, allow attackers to
| cause a denial of service or possibly have other impact via unknown
| vectors.

CVE-2014-1704[10]:
| Multiple unspecified vulnerabilities in Google V8 before 3.23.17.18,
| as used in Google Chrome before 33.0.1750.149, allow attackers to
| cause a denial of service or possibly have other impact via unknown
| vectors.

CVE-2014-1705[11]:
| Google V8, as used in Google Chrome before 33.0.1750.152 on OS X and
| Linux and before 33.0.1750.154 on Windows, allows remote attackers to
| cause a denial of service (memory corruption) or possibly have
| unspecified other impact via unknown vectors.

CVE-2014-1716[12]:
| Cross-site scripting (XSS) vulnerability in the Runtime_SetPrototype
| function in runtime.cc in Google V8, as used in Google Chrome before
| 34.0.1847.116, allows remote attackers to inject arbitrary web script
| or HTML via unspecified vectors, aka "Universal XSS (UXSS)."

CVE-2014-1717[13]:
| Google V8, as used in Google Chrome before 34.0.1847.116, does not
| properly use numeric casts during handling of typed arrays, which
| allows remote attackers to cause a denial of service (out-of-bounds
| array access) or possibly have unspecified other impact via crafted
| JavaScript code.

CVE-2014-1717[14]:
| Google V8, as used in Google Chrome before 34.0.1847.116, does not
| properly use numeric casts during handling of typed arrays, which
| allows remote attackers to cause a denial of service (out-of-bounds
| array access) or possibly have unspecified other impact via crafted
| JavaScript code.

CVE-2014-1729[15]:
| Multiple unspecified vulnerabilities in Google V8 before 3.24.35.22,
| as used in Google Chrome before 34.0.1847.116, allow attackers to
| cause a denial of service or possibly have other impact via 

[Bug 1837038] Re: Broken and defunct libv8-3.14 urgently needs removal

[Jeroen Ooms]

Thank you!

Indeed, the Debian maintainer (Jérémy Lal) told me he is in the process
of removing libv8-3.14 entirely as well, but they need to deal with the
last reverse dependency (uwsgi-plugin-v8).

But for them it's less of an urgent issue because they have already
removed it from stable branches. However for Ubuntu it is currently
still affecting releases.

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

Title:
  Broken and defunct libv8-3.14 urgently needs removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libv8-3.14/+bug/1837038/+subscriptions

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

[Bug 1837038] [NEW] Broken and defunct libv8-3.14 urgently needs removal

[Jeroen Ooms]

Public bug reported:

I am the upstream author of r-cran-v8, the R bindings for libv8.

The libv8-3.14 package has been superseded in Debian by libnode-dev.
Both packages provide "libv8-dev" however libv8-3.14 is broken beyond
repair with many security problems and crashes when compiled with recent
versions of GCC.

Debian has removed libv8-3.14 from stable and modified libnode-dev to
provide a drop-in replacement. This works great and r-cran-v8 now uses
this.

Unfortunately Ubuntu also still has the broken libv8-3.14 (in disco and
eoan). And when users compile the R bindings from source via "apt-get
install libv8-dev", unfortunately apt installs the old, broken version
of v8, rather than the virtual one from libnode-dev.

There are two solutions:
 - Remove libv8-3.14 alltogether
 - Modify libv8-3.14 such that it no longer provides libv8-dev, but only 
libv8-3.14-dev. Therefore users will get the working version when they do 
apt-get install libv8-dev.

I hope this can be resolved before the next LTS!

** Affects: libv8-3.14 (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/1837038

Title:
  Broken and defunct libv8-3.14 urgently needs removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libv8-3.14/+bug/1837038/+subscriptions

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

[Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security

[Jeroen Bobbeldijk]

I have started the process of adding dis_ucode_ldr to grub recovery mode
in Ubuntu. https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789

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

Title:
  intel-microcode on ASUS makes kernel stuck during loading initramfs on
  bionic-updates, bionic-security

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions

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

[Bug 1831789] [NEW] Add "dis_ucode_ldr" to linux boot options for Recovery Mode

[Jeroen Bobbeldijk]

Public bug reported:

Due to some recent problems with a microcode update which broke booting
of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot
options to allow booting after a bad microcode update.

See the following topics that describe the problems:
 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620
 - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1

When such problems occur it's very hard to see that the microcode
loading is the issue, the booting just hangs at the purple screen, even
removing "quiet splash" or using the recovery option will not show the
error.

We'll need to double check that dis_ucode_ldr works as expected across all 
architectures.
According to the kernel docs (Documentation/admin-guide/kernel-parameters.txt), 
dis_ucode_ldr is x86 only, so my guess is that it will be ignored for other 
architectures. According to the kernel code  
(arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works for both AMD and 
Intel.
I have some time tomorrow on test this on a ARM device.

This was also discussed Ubuntu Developer mailing list where it was
suggested to post this here, see: https://lists.ubuntu.com/archives
/ubuntu-devel/2019-June/040725.html

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

** Description changed:

  Due to some recent problems with a microcode update which broke booting
  of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot
  options to allow booting after a bad microcode update.
  
  See the following topics that describe the problems:
-  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620
-  - 
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1
+  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 (#1829620)
+  - 
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1
  
  When such problems occur it's very hard to see that the microcode
  loading is the issue, the booting just hangs at the purple screen, even
  removing "quiet splash" or using the recovery option will not show the
  error.
  
  We'll need to double check that dis_ucode_ldr works as expected across all 
architectures.
  According to the kernel docs 
(Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, 
so my guess is that it will be ignored for other architectures. According to 
the kernel code  (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works 
for both AMD and Intel.
  I have some time tomorrow on test this on a ARM device.
  
  This was also discussed Ubuntu Developer mailing list where it was
  suggested to post this here, see: https://lists.ubuntu.com/archives
  /ubuntu-devel/2019-June/040725.html

** Description changed:

  Due to some recent problems with a microcode update which broke booting
  of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot
  options to allow booting after a bad microcode update.
  
  See the following topics that describe the problems:
-  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 (#1829620)
+  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620
   - 
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1
  
  When such problems occur it's very hard to see that the microcode
  loading is the issue, the booting just hangs at the purple screen, even
  removing "quiet splash" or using the recovery option will not show the
  error.
  
  We'll need to double check that dis_ucode_ldr works as expected across all 
architectures.
  According to the kernel docs 
(Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, 
so my guess is that it will be ignored for other architectures. According to 
the kernel code  (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works 
for both AMD and Intel.
  I have some time tomorrow on test this on a ARM device.
  
  This was also discussed Ubuntu Developer mailing list where it was
  suggested to post this here, see: https://lists.ubuntu.com/archives
  /ubuntu-devel/2019-June/040725.html

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

Title:
  Add "dis_ucode_ldr" to linux boot options for Recovery Mode

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

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

[Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode

[Jeroen Bobbeldijk]

Related to #1829620

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

Title:
  Add "dis_ucode_ldr" to linux boot options for Recovery Mode

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

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

[Bug 1830205] [NEW] There is no space between the offsets column and the first databyte

[Jeroen van der Laan]

Public bug reported:

The first databyte is placed directly after the offset. This makes it
seam like it's part of the offset. I had to look a few times before I
noticed this and it's still kind of annoying to read (this probably
differs for the chosen theme). A space here would improve the
readability a lot.

Best regards,
Jeroen van der Laan

** Affects: ghex (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/1830205

Title:
  There is no space between the offsets column and the first databyte

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

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

[Bug 1768565] Re: pdfsam crashes at launch on Bionic Beaver 18.04 LTS

[Jeroen]

I also can confirm that this bug is still not fixed:

Exception in thread "main" java.lang.NoClassDefFoundError: 
javafx/scene/layout/HBox
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1009)
at 
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:802)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:700)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:623)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
at org.pdfsam.community.App.main(App.java:34)
Caused by: java.lang.ClassNotFoundException: javafx.scene.layout.HBox
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
... 10 more

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

Title:
  pdfsam crashes at launch on Bionic Beaver 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11/+bug/1768565/+subscriptions

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

[Bug 1600299] Re: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted

[Jeroen Evens]

same issue
backup was working fine 2 weeks ago, now it started giving this error
Ubuntu 18.04

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

Title:
  Giving up after 5 attempts. Error: g-io-error-quark: The specified
  location is not mounted

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

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

[Bug 1318030] Re: Cannot login-without-password when home folder is encrypted

[Jeroen]

** Summary changed:

- Cannot login-without-password when home folder in encrypted
+ Cannot login-without-password when home folder is encrypted

** Description changed:

- Users of which the home folder is encrypted using the CLI (unfortunately
+ Users of whom the home folder is encrypted using the CLI (unfortunately
  there is no GUI option for this, see
  https://bugs.launchpad.net/ubuntu/+source/gnome-control-
  center/+bug/1279766), and for which the 'login without password' is set,
  cannot login.
  
  Steps to reproduce:
  1. Using an Administrator account, create a new user in System Settings > 
User Accounts and set a password.
  2. Open a shell and encrypt the newly created user folder by 'sudo 
ecryptfs-migrate-home -u '
  3. Login into the new account: successful
  4. Logout and login into the Administrator account and select 'Login without 
password' for the newly created user.
  5. Login into the new account: cannot login (the password field for this 
users now displays 'Log in' but trying to login results in a flickering screen 
and back to the login screen.
  
  Ubuntu 14.04 x64 (reproducable on two different machines)

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

Title:
  Cannot login-without-password when home folder is encrypted

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

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

[Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

[Jeroen]

In Kubuntu 18.04 the middle mouse button of my Logitech M310 didn't work 
anymore. 
After I tried the workaround as described in #91 and #95 it started working 
again.

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

Title:
  Middle mouse (wheel-click) button stopped working after upgrade to
  16.04

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

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

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

[Jeroen Hoek]

Viktor: Ah, OK, thanks for checking. Interesting that your builds fail
in OpenJDK 11 as well as 8, but mine only in this updated OpenJDK 8.

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

Title:
  Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11/+bug/1800792/+subscriptions

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

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

[Jeroen Hoek]

I've had to disable JaCoCo, and set the  of the Surefire-
plugin to 0 to get the mini-project 'NiceXVI' linked above to build
under this OpenJDK 8 version. So it looks like it is not just JaCoCo.

OpenJDK 11 works after updating JaCoCo though.

Viktor: I have the set $JAVA_HOME in order for Maven to use a different
JDK, regardless of the version of java available in the shell. Are you
sure you are running the build with javac 10/11?

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

Title:
  Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11/+bug/1800792/+subscriptions

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

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

[Jeroen Hoek]

So this probably not a bug for the OpenJDK 11 package, but it is for the
OpenJDK 8 package. No version of JaCoCo seems to work with the version
released today.

Viktor: Does your build work in OpenJDK 11?

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

Title:
  Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11/+bug/1800792/+subscriptions

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

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

[Jeroen Hoek]

After some more testing and frustration I've found that after updating
JaCoCo to 0.8.2 the newest OpenJDK 11 build works, as does the OpenJDK
10 provided by Ubuntu.

The OpenJDK 8 version now provided by Ubuntu doesn't.

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

Title:
  Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11/+bug/1800792/+subscriptions

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

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

[Jeroen Hoek]

Triage: I think this issue can be closed, although I don't quite
understand why a seemingly minor patch in JDK 8 should break tools in
this way.

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

Title:
  Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11/+bug/1800792/+subscriptions

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

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

[Jeroen Hoek]

Found the root cause: the JaCoCo plugin in my builds needed updating to
a more recent version. If anyone lights upon this problem; OpenJDK
8u181-b13-1ubuntu0.18.04.1 and newer break older JaCoCo releases. The
newer versions of this tool do work with these and newer JDK releases up
to and including 11.

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

Title:
  Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11/+bug/1800792/+subscriptions

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

[Bug 1800792] Re: Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

[Jeroen Hoek]

** Attachment added: "Output of mvn clean install"
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1800792/+attachment/5207389/+files/crash.txt

** Also affects: openjdk-11 (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/1800792

Title:
  Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11/+bug/1800792/+subscriptions

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

[Bug 1800792] [NEW] Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

[Jeroen Hoek]

Public bug reported:

Today both the OpenJDK 8 and 11 packages were updated. In the case of
OpenJDK 8:

openjdk-8-jdk: 8u181-b13-0ubuntu0.18.04.1 → 8u181-b13-1ubuntu0.18.04.1

OpenJDK 11 (10 really):

openjdk-11-jdk: 10.0.2+13-1ubuntu0.18.04.2 → 10.0.2+13-1ubuntu0.18.04.3

After this update all my local Maven builds fail with a crashed VM. From
the console output it looks like one of the prerequisites of JaCoCo
(Java code coverage tool) is no longer met, but I haven't been able to
figure out what the root cause is.

This problem occurs with both OpenJDK 8 and 10.

Reproduction:

This is one of our projects: https://github.com/LableOrg/java-nicerxvi

Clone the project, and call `mvn clean install`. For me it now fails to
build (output attached).

When I downgrade to 8u162-b12-1 everything works again.

** Affects: openjdk-11 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: openjdk-8 (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/1800792

Title:
  Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11/+bug/1800792/+subscriptions

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

[Bug 1797875] Re: ImageMagick 8:6.8.9.9-7ubuntu5.13 quality regression

[Jeroen]

** Attachment added: "The sample PDF"
   
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1797875/+attachment/5201213/+files/demo.pdf

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

Title:
  ImageMagick 8:6.8.9.9-7ubuntu5.13 quality regression

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

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

[Bug 1797875] [NEW] ImageMagick 8:6.8.9.9-7ubuntu5.13 quality regression

[Jeroen]

Public bug reported:

I would like to report a regression in ImageMagick
8:6.8.9.9-7ubuntu5.13. This report is related to
https://bugs.launchpad.net/bugs/1796563, but involves image quality
instead of permissions.

What happens:  In the new version (= security patch) of ImageMagick, the
quality of converted images is in some cases lower compared to the old
version. It is not visible on all converted images, some seem to suffer
more than others. In our case, converting postal barcodes from PDF to
PNG results in unscannable codes. The release information for the new
version does not mention any impact on quality.

Versions involved:

- OS: Ubuntu 16.04.4 LTS
- Imagemagick: 8:6.8.9.9-7ubuntu5.13 (suffering this issue)
- Imagemagick: 8:6.8.9.9-7ubuntu5.12 (working properly)

# convert --version
Version: ImageMagick 6.8.9-9 Q16 x86_64 2018-09-28 http://www.imagemagick.org
# convert demo.pdf demo_new.png

# convert --version
Version: ImageMagick 6.8.9-9 Q16 x86_64 2018-07-10 http://www.imagemagick.org
# convert demo.pdf demo_old.png

Attached a few sample images;
- On the demo_[old|new].png, note the text in the yellow area
- The eventbrite images are screenshots of a part of the converted
PNG, due to privacy protection.

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


** Tags: convert image imagemagick quality regression

** Attachment added: "Sample images"
   
https://bugs.launchpad.net/bugs/1797875/+attachment/5201212/+files/images.tar.gz

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

Title:
  ImageMagick 8:6.8.9.9-7ubuntu5.13 quality regression

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

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

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

** Attachment added: "bios screenshots.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193579/+files/bios%20screenshots.tar.gz

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

bios screenshots

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

sudo dmidecode
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
76 structures occupying 2828 bytes.
Table at 0xCBD62018.

Handle 0x, DMI type 11, 5 bytes
OEM Strings
String 1:  
String 2: $BIOSE121
String 3:  
String 4:  
String 5:  

Handle 0x0001, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: E1773IMS.110
Release Date: 11/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.16

Handle 0x0002, DMI type 1, 27 bytes
System Information
Manufacturer: Micro-Star International Co., Ltd.
Product Name: GS70 2QE
Version: REV:1.0
Serial Number: 9S7177311046ZE917
UUID: ----448A5B6EE822
Wake-up Type: Power Switch
SKU Number: To be filled by O.E.M.
Family: To be filled by O.E.M.

Handle 0x0003, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-1773
Version: REV:0.B
Serial Number: BSS-0123456789
Asset Tag: To be filled by O.E.M.
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To be filled by O.E.M.
Chassis Handle: 0x0004
Type: Motherboard
Contained Object Handles: 0

Handle 0x0004, DMI type 3, 25 bytes
Chassis Information
Manufacturer: To Be Filled By O.E.M.
Type: Notebook
Lock: Not Present
Version: To Be Filled By O.E.M.
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 1
 (0)
SKU Number: To be filled by O.E.M.

Handle 0x0005, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse Port

Handle 0x0006, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port

Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A1
Internal Connector Type: None
External Reference Designator: TV Out
External Connector Type: Mini Centronics Type-14
Port Type: Other

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2A
Internal Connector Type: None
External Reference Designator: COM A
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible

Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2B
Internal Connector Type: None
External Reference Designator: Video
External Connector Type: DB-15 female
Port Type: Video Port

Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB2
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External 

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

sudo mdadm --examine /dev/sd[a-z]
/dev/sda:
  Magic : Intel Raid ISM Cfg Sig.
Version : 1.2.06
Orig Family : b64dd376
 Family : b64de296
 Generation : 0806
 Attributes : All supported
   UUID : fe813c51:b5e27074:8e458e63:fd55063a
   Checksum : d3a21665 correct
MPB Sectors : 1
  Disks : 2
   RAID Devices : 1

  Disk00 Serial : S33HNX0HA01515T
  State : active
 Id : 
Usable Size : 976766976 (465.76 GiB 500.10 GB)

[Volume1]:
   UUID : 1cb157dd:43317668:a8db10af:a752a6c1
 RAID Level : 1
Members : 2
  Slots : [UU]
Failed disk : none
  This Slot : 0
Sector Size : 512
 Array Size : 976766976 (465.76 GiB 500.10 GB)
   Per Dev Size : 976767240 (465.76 GiB 500.10 GB)
  Sector Offset : 0
Num Stripes : 3815496
 Chunk Size : 64 KiB
   Reserved : 0
  Migrate State : idle
  Map State : normal
Dirty State : clean
 RWH Policy : off

  Disk01 Serial : S33HNX0J200852F
  State : active
 Id : 0001
Usable Size : 976766976 (465.76 GiB 500.10 GB)
/dev/sdb:
  Magic : Intel Raid ISM Cfg Sig.
Version : 1.2.06
Orig Family : b64dd376
 Family : b64de296
 Generation : 0806
 Attributes : All supported
   UUID : fe813c51:b5e27074:8e458e63:fd55063a
   Checksum : d3a21665 correct
MPB Sectors : 1
  Disks : 2
   RAID Devices : 1

  Disk01 Serial : S33HNX0J200852F
  State : active
 Id : 0001
Usable Size : 976766976 (465.76 GiB 500.10 GB)

[Volume1]:
   UUID : 1cb157dd:43317668:a8db10af:a752a6c1
 RAID Level : 1
Members : 2
  Slots : [UU]
Failed disk : none
  This Slot : 1
Sector Size : 512
 Array Size : 976766976 (465.76 GiB 500.10 GB)
   Per Dev Size : 976767240 (465.76 GiB 500.10 GB)
  Sector Offset : 0
Num Stripes : 3815496
 Chunk Size : 64 KiB
   Reserved : 0
  Migrate State : idle
  Map State : normal
Dirty State : clean
 RWH Policy : off

  Disk00 Serial : S33HNX0HA01515T
  State : active
 Id : 
Usable Size : 976766976 (465.76 GiB 500.10 GB)
/dev/sdc:
   MBR Magic : aa55
Partition[0] :   3907029167 sectors at1 (type ee)
/dev/sdd:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at1 (type ee)

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

sudo mdadm --assemble --scan
returns nothing

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

sudo  mdadm --detail-platform  
[sudo] password for jeroen: 
   Platform : Intel(R) Rapid Storage Technology
Version : 12.9.0.2006
RAID Levels : raid0
Chunk Sizes : 4k 8k 16k 32k 64k 128k
2TB volumes : supported
  2TB disks : supported
  Max Disks : 6
Max Volumes : 2 per array, 4 per controller
 I/O Controller : /sys/devices/pci:00/:00:1f.2 (SATA)
  Port5 : /dev/sdd (S33HNX0J200966L)
  Port1 : /dev/sdb (S33HNX0J200852F)
  Port4 : /dev/sdc (WDZ29M4J)
  Port0 : /dev/sda (S33HNX0HA01515T)
  Port2 : - no device attached -
  Port3 : - no device attached -

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

find /etc/initramfs-tools/ -ls
 14417979  4 drwxr-xr-x   5 root root 4096 sep 26 08:25 
/etc/initramfs-tools/
 14419131  4 -rw-r--r--   1 root root  378 jan  5  2018 
/etc/initramfs-tools/update-initramfs.conf
 14419128  4 drwxr-xr-x  12 root root 4096 jul 25 05:03 
/etc/initramfs-tools/scripts
 14419136  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/scripts/local-premount
 14419135  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/scripts/local-bottom
 14419137  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/scripts/local-top
 14419139  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/scripts/nfs-premount
 14419133  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/scripts/init-premount
 14419134  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/scripts/init-top
 14419140  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/scripts/nfs-top
 14419141  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/scripts/panic
 14419138  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/scripts/nfs-bottom
 14419132  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/scripts/init-bottom
 14419126  4 drwxr-xr-x   2 root root 4096 jul 25 05:17 
/etc/initramfs-tools/conf.d
 14419130  4 -rw-r--r--   1 root root  246 jul 25 05:03 
/etc/initramfs-tools/modules
 14419129  4 -rw-r--r--   1 root root 1646 jan  5  2018 
/etc/initramfs-tools/initramfs.conf
 14419127  4 drwxr-xr-x   2 root root 4096 feb 20  2018 
/etc/initramfs-tools/hooks

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

sudo cat /proc/mounts
[sudo] password for jeroen: 
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=8140992k,nr_inodes=2035248,mode=755 
0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=1634112k,mode=755 0 0
/dev/mapper/isw_dafiffhfja_Volume1p2 / ext4 
rw,relatime,errors=remount-ro,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/unified cgroup2 
rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0
cgroup /sys/fs/cgroup/systemd cgroup 
rw,nosuid,nodev,noexec,relatime,xattr,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup 
rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/rdma cgroup rw,nosuid,nodev,noexec,relatime,rdma 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup 
rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/perf_event cgroup 
rw,nosuid,nodev,noexec,relatime,perf_event 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs 
rw,relatime,fd=25,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15340 
0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
sunrpc /run/rpc_pipefs rpc_pipefs rw,relatime 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
/dev/mapper/isw_dafiffhfja_Volume1p1 /boot/efi vfat 
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
 0 0
tmpfs /run/user/119 tmpfs 
rw,nosuid,nodev,relatime,size=1634108k,mode=700,uid=119,gid=124 0 0
tmpfs /run/user/1000 tmpfs 
rw,nosuid,nodev,relatime,size=1634108k,mode=700,uid=1000,gid=1000 0 0

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

after a purge remove vagrant I get raid problems.

** Attachment added: "cannot activate member md127.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193074/+files/cannot%20activate%20member%20md127.jpg

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

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

initramfs

** Attachment added: "initramfs.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193066/+files/initramfs.tar.gz

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant

[Jeroen]

After installing vagrant it did a update-initramfs, which I presume,
broke booting from kernel 4.15.0-34-generic when I switched back, using
the grub menu, to a previous kernel  4.15.0-29-generic I could still
boot without problems

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant?

[Jeroen]

** Description changed:

- My system won't boot after a kernel upgrade. When I switch back to the 
previous kernel version it works fine.
- I've got 3 ssd's and 1 hdd.
- Currently I'm using 2 ssd's for intel fake raid 1(mirror) for kubuntu 18.04
- The last ssd has windows 10 installed.
+ Reproduction steps:
+ clean install of kubuntu & reboot
+ full update & reboot
+ apt-get install vagrant & reboot
+ =>busybox
  
- My hdd is currently unused.
+ My system won't boot after installing vagrant. When I switch back to the
+ previous kernel version it works until another initfs update.
  
- I've reinstalled my system multiple times. I can reproduce this kernel
- boot problem every time.
+ Currently I'm using 2 ssd's for intel fake raid 1(mirror) for kubuntu
+ 18.04
  
- Fake raid 0 has worked on my system for a a few years now.
- My fakeraid 0 setup broke somewhere on the beginning of september.
- Possibly with the same root cause.
+ I've reinstalled my system multiple times. I can reproduce this issue
+ every time.

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

** Summary changed:

- unable to boot after installing vagrant?
+ unable to boot after installing vagrant

** Description changed:

  Reproduction steps:
  clean install of kubuntu & reboot
  full update & reboot
  apt-get install vagrant & reboot
  =>busybox
  
  My system won't boot after installing vagrant. When I switch back to the
- previous kernel version it works until another initfs update.
+ previous kernel version it works until another update-initramfs.
  
  Currently I'm using 2 ssd's for intel fake raid 1(mirror) for kubuntu
  18.04
  
  I've reinstalled my system multiple times. I can reproduce this issue
  every time.

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

Title:
  unable to boot after installing vagrant

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

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

[Bug 1794318] Re: unable to boot after installing vagrant?

[Jeroen]

I've added my logs after a failed boot (using a usb live disk).

** Attachment added: "log.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193049/+files/log.tar.gz

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

Title:
  unable to boot after installing vagrant?

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

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

[Bug 1794318] Re: unable to boot after installing vagrant?

[Jeroen]

** Summary changed:

- unable to boot
+ unable to boot after installing vagrant?

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

Title:
  unable to boot after installing vagrant?

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

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

[Bug 1794318] Re: kernel update breaks boot on intel fake raid 1

[Jeroen]

full*

** Summary changed:

- kernel update breaks boot on intel fake raid 1
+ unable to boot

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

Title:
  unable to boot

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

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

[Bug 1794318] Re: kernel update breaks boot on intel fake raid 1

[Jeroen]

I reinstalled my system again and did a fool update and a reboot. It
looks like something else is causing the problem.

** Description changed:

  My system won't boot after a kernel upgrade. When I switch back to the 
previous kernel version it works fine.
  I've got 3 ssd's and 1 hdd.
  Currently I'm using 2 ssd's for intel fake raid 1(mirror) for kubuntu 18.04
  The last ssd has windows 10 installed.
  
  My hdd is currently unused.
  
  I've reinstalled my system multiple times. I can reproduce this kernel
  boot problem every time.
  
- Fake raid 0 has worked on my system for a a few years now. 
- My fakeraid 0 setup broke somewhere on the beginning of september.  
+ Fake raid 0 has worked on my system for a a few years now.
+ My fakeraid 0 setup broke somewhere on the beginning of september.
  Possibly with the same root cause.

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

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

Title:
  unable to boot

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

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

[Bug 1794318] Re: kernel update breaks boot on intel fake raid 1

[Jeroen]

View attachment for more info.

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

Title:
  kernel update breaks boot on intel fake raid 1

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

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

[Bug 1794318] [NEW] kernel update breaks boot on intel fake raid 1

[Jeroen]

Public bug reported:

My system won't boot after a kernel upgrade. When I switch back to the previous 
kernel version it works fine.
I've got 3 ssd's and 1 hdd.
Currently I'm using 2 ssd's for intel fake raid 1(mirror) for kubuntu 18.04
The last ssd has windows 10 installed.

My hdd is currently unused.

I've reinstalled my system multiple times. I can reproduce this kernel
boot problem every time.

Fake raid 0 has worked on my system for a a few years now. 
My fakeraid 0 setup broke somewhere on the beginning of september.  
Possibly with the same root cause.

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

** Attachment added: "https://github.com/arvidjaar/bootinfoscript output"
   
https://bugs.launchpad.net/bugs/1794318/+attachment/5192821/+files/bootinfoscript-output

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

Title:
  kernel update breaks boot on intel fake raid 1

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

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

[Bug 1766495] Re: "your libfreerdp does not support h264"

[Jeroen]

Same here, Ubuntu 18.04.1 LTS (Lubuntu), latest Remmina version.
Workaround the same as above, changing color depth to True Color (32bpp) fixed 
it.

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

Title:
  "your libfreerdp does not support h264"

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

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

[Bug 29894] Re: can't take screenshot when menu on panel is opened

[Jeroen]

Today I wanted to make a screenshot on Ubuntu 18.04.1 LTS with a menu
open but it still fails and the issue still persists.

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

Title:
  can't take screenshot when menu on panel is opened

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

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

[Bug 1711087] Re: ad2p sink profile mic not available

[Jeroen]

Yes, this is a duplicate of bug #508522. IMHO I think that we should
close this issue and re-open bug #508533.

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

Title:
  ad2p sink profile mic not available

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

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

[Bug 1711087] Re: ad2p sink profile mic not available

[Jeroen]

*re-open #508522

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

Title:
  ad2p sink profile mic not available

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

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

[Bug 1792790] Re: mismatch on package

[Jeroen Oudshoorn]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Invalid

** Converted to question:
   
https://answers.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+question/674023

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

Title:
  mismatch on package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1792790/+subscriptions

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

[Bug 1792790] Re: mismatch on package

[Jeroen Oudshoorn]

What to do next, I cannot update my desktop.

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: apport (Ubuntu)

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

Title:
  mismatch on package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1792790/+subscriptions

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

[Bug 1792790] [NEW] mismatch on package

[Jeroen Oudshoorn]

Public bug reported:

LANG=C; sudo apt-get -f 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:
  linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic 
linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic
  linux-modules-extra-4.15.0-32-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libnvidia-gl-390 libnvidia-gl-390:i386
The following NEW packages will be installed:
  libnvidia-gl-390 libnvidia-gl-390:i386
0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded.
3 not fully installed or removed.
Need to get 0 B/29.1 MB of archives.
After this operation, 147 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 256831 files and directories currently installed.)
Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_i386.deb ...
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340
dpkg-divert: error: mismatch on package
  when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by 
libnvidia-gl-390'
  found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340'
dpkg: error processing archive 
/var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb (--unpack):
 new libnvidia-gl-390:i386 package pre-installation script subprocess returned 
error exit status 2
Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_amd64.deb ...
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340
dpkg-divert: error: mismatch on package
  when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by 
libnvidia-gl-390'
  found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340'
dpkg: error processing archive 
/var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb (--unpack):
 new libnvidia-gl-390:amd64 package pre-installation script subprocess returned 
error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb
 /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

** Affects: nvidia-graphics-drivers-390 (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/1792790

Title:
  mismatch on package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1792790/+subscriptions

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

[Bug 1753518] Re: package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1

[Jeroen Claeys]

Latitude E7450. Same issue.

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

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

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

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

[Bug 1791421] [NEW] Nautilus hangs when opening a password protected .7z file

[Jeroen]

Public bug reported:

Very simple scenario: On a fresh Ubuntu 18.04 installation (with Unity
and pzip-full installed) I try to open a password protected .7z file
(created in an older Ubuntu version). Nautilus starts flickering, CPU
usage rises to 80% for minutes and Nautilus is not usable for a long
time. Minimising doesn't work, however terminating does, where after CPU
usage turns to normal.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Sep  8 12:30:29 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x540+226+183'"
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
InstallationDate: Installed on 2018-09-01 (6 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: dropbox 2015.10.28

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


** Tags: amd64 apport-bug bionic

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

Title:
  Nautilus hangs when opening a password protected .7z file

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

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

[Bug 1003682] Re: Borderless printing doesn't work on the Photosmart B8500 with hpcups

[Jeroen Dekkers]

I don't longer have access to a photosmart printer so I can't confirm if
it is still a problem or not.

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

Title:
  Borderless printing doesn't work on the Photosmart B8500 with hpcups

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

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

[Bug 1461698] Re: Cross-hair pointer leaves a trace on screen in eeschema

[Jeroen V]

Instaling version 5 (see http://kicad-pcb.org/download/ubuntu/ ) fixes
the problem.

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

Title:
  Cross-hair pointer leaves a trace on screen in eeschema

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

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

[Bug 1461698] Re: Cross-hair pointer leaves a trace on screen in eeschema

[Jeroen V]

I can confirm that a fresh ubuntu install with 4.0.7+dfsg1-1ubuntu2
shows the described behaviour.

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

Title:
  Cross-hair pointer leaves a trace on screen in eeschema

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

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

[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised

[Jeroen Lodewijks]

Ouch what a mistake to make!
Not sure what the fingerprint reader is:

jeroen@nice:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0bda:5768 Realtek Semiconductor Corp. 
Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
Bus 001 Device 003: ID 04f3:2335 Elan Microelectronics Corp. 
Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
jeroen@nice:~$ lspci
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 
08)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 515 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 08)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
(rev f1)
00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 
(rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 
(rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d46 (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
6c:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
6d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)

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

Title:
  [04f3:0903] Elan Microelectronics Corp fingerprint reader not
  recognised

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

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

[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised

[Jeroen Lodewijks]

Hi, I have an Dell Latitude 7370 with an Elan fingerprint reader and
can't get it to work

jeroen@nice:~/libfprint$ lsusb | grep -i elan
Bus 001 Device 003: ID 04f3:2335 Elan Microelectronics Corp.

I tried your fork of libprintf, Igor, and noticed you don't support ID 
04f3:2335.
I added it to elan.h but unfortunately no joy:

jeroen@nice:~/libfprint/builddir_dbg/examples$ sudo ./enroll
This program will enroll your right index finger, unconditionally overwriting 
any right-index print that was enrolled previously. If you want to continue, 
press enter, otherwise hit Ctrl+C

fp:debug [fp_init] 
fp:debug [register_driver] registered driver upekts
fp:debug [register_driver] registered driver aes3500
fp:debug [register_driver] registered driver aes4000
fp:debug [register_driver] registered driver aes2501
fp:debug [register_driver] registered driver aes2550
fp:debug [register_driver] registered driver uru4000
fp:debug [register_driver] registered driver vcom5s
fp:debug [register_driver] registered driver upeksonly
fp:debug [register_driver] registered driver aes1610
fp:debug [register_driver] registered driver aes1660
fp:debug [register_driver] registered driver aes2660
fp:debug [register_driver] registered driver vfs101
fp:debug [register_driver] registered driver vfs301
fp:debug [register_driver] registered driver vfs5011
fp:debug [register_driver] registered driver upektc
fp:debug [register_driver] registered driver upektc_img
fp:debug [register_driver] registered driver etes603
fp:debug [register_driver] registered driver vfs0050
fp:debug [register_driver] registered driver elan
fp:debug [find_supporting_driver] driver elan supports USB device 04f3:2335
fp:debug [find_supporting_driver] selected driver elan supports USB device 
04f3:2335
Found device claimed by ElanTech Fingerprint Sensor driver
sync:debug [fp_dev_open] 
async:debug [fp_async_dev_open] 
elan:debug [dev_init] 
elan:error [dev_init] could not claim interface 0: LIBUSB_ERROR_BUSY
async:error [fp_async_dev_open] device initialisation failed, driver=elan
Could not open device.
fp:debug [fp_exit]

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

Title:
  [04f3:0903] Elan Microelectronics Corp fingerprint reader not
  recognised

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

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

[Bug 1776615] [NEW] mysqldump: Got error: 1016: Can't open file: 'some_file' (errno: 24 - Too many open files) when using LOCK TABLES

[Jeroen Baten]

Public bug reported:

This is a report and also the fix. Please patch this so I don't have to
any more.

Error:
During run of automysqlbackup I get the following email:
mysqldump: Got error: 1016: Can't open file: 'some_file.frm' (errno: 24 - Too 
many open files) when using LOCK TABLES
mysqldump: Got error: 1016: Can't open file: 'some_file.frm' (errno: 24 - Too 
many open files) when using LOCK TABLES
mysqldump: Couldn't execute 'show events': Out of resources when opening file 
'./mysql/event.MYD' (Errcode: 24 - Too many open files) (23)

Solution:
There is an error in the maximum number of open files. The source is not in the 
kernel configuration!

This solves this problem:
Error: mysql: too much open files error

Changing /lib/systemd/system/mysql.service and adding in the Service
section 2 extra lines:

[Service]
... ... ...
LimitNOFILE=infinity
LimitMEMLOCK=infinity

After that:

systemctl daemon-reload
service mysql restart

Problem goes away (at least until I run an apt update again :-) )

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mysql-server 5.7.22-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Jun 13 10:06:48 2018
InstallationDate: Installed on 2012-07-01 (2172 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: False
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: mysql-5.7
UpgradeStatus: Upgraded to xenial on 2016-09-24 (627 days ago)

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


** Tags: amd64 apparmor apport-bug xenial

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

Title:
  mysqldump: Got error: 1016: Can't open file: 'some_file' (errno: 24 -
  Too many open files) when using LOCK TABLES

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

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

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

[Jeroen Evens]

can confirm after updating ubuntu Xenial and removing nomodeset from
boot options, everything seems to work again :)

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

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

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

[Jeroen Evens]

What about Xenial?!!

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

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

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

[Jeroen Evens]

i really don't understand why they allow anyone to update the status in 
launchpad, it only creates confusion, especially when you can't revert 
accidental changes :(
maybe @joseph salisbury can reopen this

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

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

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

[Jeroen Evens]

i'm also on the 4.13 kernel on xenial
thanks for fixing the issue!
it's really important for me cause i really need my external monitor to be more 
productive at work
can't wait for the xenial kernel update to drop

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

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

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

[Jeroen Evens]

will this also be fixed in xenial?

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

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

[Bug 1771758] Re: putty crashed with SIGSEGV in XrmQGetResource()

[Jeroen van Ingen]

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

Thank you, I wasn't sure if crash in XrmQGetResource was the same as
crash in XGetDefault, but just noticed that the workaround mentioned in
#1720905 (starting putty with 'sudo -u MY_USER putty') works for me too.
I'll upgrade to Bionic where it's fixed, if I understand correctly.

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

Title:
  putty crashed with SIGSEGV in XrmQGetResource()

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

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

[Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

[Jeroen Evens]

any way to fix it for regular users (without compiling a kernel)
nomodeset works, but i can't use my external display if i use it

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

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

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

[Jeroen Donkervoort]

Same here, after I read this message, I changed my login settings to Ubuntu
on Wayland and never got this error again

2018-04-14 8:38 GMT+02:00 Per-Inge :

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

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

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

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

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