[Bug 1826461] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1826461 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Aroiu Ovidiu (ixanneo) 1. Could you describe somehow the performance difference? 2. How can I fix the touchpad issue which occurs by using your parameters Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787332] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen ...") from xf86VTEnter() from systemd_logind_vtenter()
This bug seems to have stopped for me a couple of months back. Now I get
black screens that have to be toggled off and back on with xrandr before
they display again after undocking/redocking.
That's a minor inconvenience compared to a crashing desktop environment,
so I'm quite happy. It would be good to know if anyone else has seen an
improvement in this behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787332
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
systemd_logind_vtenter()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1787332/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826461] [NEW] Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection.
Public bug reported: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826460] [NEW] Every snap gives "create user data directory" after upgrade to 19.04
Public bug reported: Since I upgraded to Ubuntu 19.04 and snapd 2.38+19.04, whenever I run any snap command, I get the following warning: cmd_run.go:876: WARNING: cannot create user data directory: failed to verify SELinux context of /home/hackel/snap: exec: "matchpathcon": executable file not found in $PATH I tried installing selinux-utils which contains the matchpathcon command, but most of the error remains: cmd_run.go:876: WARNING: cannot create user data directory: failed to verify SELinux context of /home/hackel/snap: exit status 1 I first noticed this when running ripgrep, but it happens with every snap I have installed: node, vlc, slack, even gnome-characters. As far as I can tell, it is not affecting functionality. The commands still run fine. Oddly, I do not even have golang-github-snapcore-snapd-dev installed, which contains cmd_run.go. I assume this must be baked into the core snap or something. ** Affects: snapd (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/1826460 Title: Every snap gives "create user data directory" after upgrade to 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1826460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826169] Re: linux-kvm: 4.18.0-1011.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 25. April 2019 11:36 UTC + phase: Promote to Proposed + phase-changed: Thursday, 25. April 2019 21:08 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826169 Title: linux-kvm: 4.18.0-1011.11 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826163] Re: linux-aws: 4.18.0-1015.17 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 25. April 2019 20:07 UTC + phase: Promote to Proposed + phase-changed: Thursday, 25. April 2019 21:07 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826163 Title: linux-aws: 4.18.0-1015.17 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826459] Re: systemd-networkd not installing GatewayOnlink=true
heres also the netplan file for it:
root@search-3 /run/systemd/network # netplan --debug apply
** (generate:22984): DEBUG: 21:03:47.073: Processing input file
/etc/netplan/01-netcfg.yaml..
** (generate:22984): DEBUG: 21:03:47.073: starting new processing pass
** (generate:22984): DEBUG: 21:03:47.073: Processing input file
/etc/netplan/02-vlan.yaml..
** (generate:22984): DEBUG: 21:03:47.073: starting new processing pass
** (generate:22984): DEBUG: 21:03:47.073: Processing input file
/etc/netplan/03-gw.yaml..
** (generate:22984): DEBUG: 21:03:47.073: starting new processing pass
** (generate:22984): DEBUG: 21:03:47.073: vlan4000: setting default backend to 1
** (generate:22984): DEBUG: 21:03:47.073: enp0s31f6: setting default backend to
1
** (generate:22984): DEBUG: 21:03:47.073: Generating output files..
** (generate:22984): DEBUG: 21:03:47.073: NetworkManager: definition vlan4000
is not for us (backend 1)
** (generate:22984): DEBUG: 21:03:47.073: NetworkManager: definition enp0s31f6
is not for us (backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:enp0s31f6 not found in {}
DEBUG:vlan4000 not found in {}
DEBUG:enp0s31f6 exists in {'enp0s31f6': {'addresses': ['95.216.96.148/26'],
'gateway4': '95.216.96.129', 'nameservers': {'search':
['148.96.216.95.clients.your-server.de'], 'addresses': ['8.8.8.8', '1.1.1.1']}}}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
enp0s31f6:
addresses:
- 95.216.96.148/26
gateway4: 95.216.96.129
nameservers:
addresses:
- 8.8.8.8
- 1.1.1.1
search:
- 148.96.216.95.clients.your-server.de
routes:
- on-link: true
to: 95.216.96.148/26
via: 95.216.96.129
vlans:
vlan4000:
addresses:
- 10.0.2.3/24
dhcp4: false
id: 4000
link: enp0s31f6
mtu: 1400
wifis: {}
DEBUG:Skipping non-physical interface: lo
DEBUG:device enp0s31f6 operstate is up, not changing
DEBUG:Skipping non-physical interface: docker0
DEBUG:Skipping non-physical interface: br-c7cc901345e8
DEBUG:Skipping non-physical interface: vlan4000
DEBUG:Skipping non-physical interface: veth20a5a67
DEBUG:Skipping non-physical interface: tun0
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp0s31f6
DEBUG:netplan triggering .link rules for docker0
DEBUG:netplan triggering .link rules for br-c7cc901345e8
DEBUG:netplan triggering .link rules for vlan4000
DEBUG:netplan triggering .link rules for veth20a5a67
DEBUG:netplan triggering .link rules for tun0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826459
Title:
systemd-networkd not installing GatewayOnlink=true
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1826459/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826171] Re: linux: 4.18.0-19.20 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826170 (bionic/linux-hwe) derivatives: bug 1826160 (linux-raspi2), bug 1826163 (linux-aws), bug 1826166 (linux-azure), bug 1826168 (linux-gcp), bug 1826169 (linux-kvm) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 11:01 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826171 Title: linux: 4.18.0-19.20 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826430] Re: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build
No problem, just be more careful in the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826430 Title: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1826430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826169] Re: linux-kvm: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826169 Title: linux-kvm: 4.18.0-1011.11 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826160] Re: linux-raspi2: 4.18.0-1013.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 25. April 2019 20:07 UTC + phase: Promote to Proposed + phase-changed: Thursday, 25. April 2019 21:07 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826160 Title: linux-raspi2: 4.18.0-1013.15 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826451] Re: crashes with mysql and php7.0 on arm
This is at least part of the problem. etting up mysql-server-5.7 (5.7.11-0ubuntu6) ...^M Installing new version of config file /etc/apparmor.d/usr.sbin.mysqld ...^M Installing new version of config file /etc/init.d/mysql ...^M Installing new version of config file /etc/init/mysql.conf ...^M Installing new version of config file /etc/logrotate.d/mysql-server ...^M Installing new version of config file /etc/mysql/debian-start ...^M update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode^M insserv: warning: script 'resolvconf' missing LSB tags and overrides^M insserv: Default-Start undefined, assuming empty start runlevel(s) for script `resolvconf'^M insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `resolvconf'^M insserv: warning: script 'firstrun' missing LSB tags and overrides^M mysql start/running, process 22749^M mysql stop/waiting^M mysql start/running, process 23042^M mysql_upgrade: Got error: 1045: Access denied for user 'debian-sys-maint'@'localhost' (using password: YES) while connecting to the MySQL server^M Upgrade process encountered error and will not continue.^M mysql_upgrade failed with exit status 11^M dpkg: error processing package mysql-server-5.7 (--configure):^M subprocess installed post-installation script returned error exit status 1^M dpkg: dependency problems prevent configuration of mysql-server:^M mysql-server depends on mysql-server-5.7; however:^M Package mysql-server-5.7 is not configured yet.^M ^M dpkg: error processing package mysql-server (--configure):^M dependency problems - leaving unconfigured^M ** Tags added: trusty2xenial ** Also affects: mysql-5.7 (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/1826451 Title: crashes with mysql and php7.0 on arm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1826451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826459] [NEW] systemd-networkd not installing GatewayOnlink=true
Public bug reported:
root@search-3 /run/systemd/network # for i in *; do echo $i; echo; cat $i; done
; sudo service systemd-networkd stop; SYSTEMD_LOG_LEVEL=debug
/lib/systemd/systemd-networkd
10-netplan-enp0s31f6.network
[Match]
Name=enp0s31f6
[Network]
LinkLocalAddressing=ipv6
Address=95.216.96.148/26
Gateway=95.216.96.129
DNS=8.8.8.8
DNS=1.1.1.1
Domains=148.96.216.95.clients.your-server.de
VLAN=vlan4000
[Route]
Destination=95.216.96.148/26
Gateway=95.216.96.129
GatewayOnlink=true
10-netplan-vlan4000.netdev
[NetDev]
Name=vlan4000
MTUBytes=1400
Kind=vlan
[VLAN]
Id=4000
10-netplan-vlan4000.network
[Match]
Name=vlan4000
[Network]
LinkLocalAddressing=ipv6
Address=10.0.2.3/24
ConfigureWithoutCarrier=yes
Failed to read $container of PID 1, ignoring: Permission denied
Found container virtualization none.
Bus n/a: changing state UNSET → OPENING
Bus n/a: changing state OPENING → AUTHENTICATING
Failed to open configuration file '/etc/systemd/networkd.conf': No such file or
directory
timestamp of '/etc/systemd/network' changed
timestamp of '/run/systemd/network' changed
Ignoring /run/systemd/network/10-netplan-enp0s31f6.network, because it's not a
regular file with suffix .netdev.
Ignoring /run/systemd/network/10-netplan-vlan4000.network, because it's not a
regular file with suffix .netdev.
Ignoring /lib/systemd/network/99-default.link, because it's not a regular file
with suffix .netdev.
Ignoring /lib/systemd/network/80-container-vz.network, because it's not a
regular file with suffix .netdev.
Ignoring /lib/systemd/network/80-container-ve.network, because it's not a
regular file with suffix .netdev.
Ignoring /lib/systemd/network/80-container-host0.network, because it's not a
regular file with suffix .netdev.
vlan4000: loaded vlan
Ignoring /run/systemd/network/10-netplan-vlan4000.netdev, because it's not a
regular file with suffix .network.
Ignoring /lib/systemd/network/99-default.link, because it's not a regular file
with suffix .network.
tun0: MAC address not found for new device, continuing without
tun0: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +POINTOPOINT +NOARP
tun0: Link 12 added
tun0: udev initialized link
tun0: Saved original MTU: 1500
veth20a5a67: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
veth20a5a67: Link 8 added
veth20a5a67: udev initialized link
veth20a5a67: Saved original MTU: 1500
vlan4000: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
vlan4000: Link 6 added
vlan4000: udev initialized link
vlan4000: netdev has index 6
vlan4000: Saved original MTU: 1400
br-c7cc901345e8: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
br-c7cc901345e8: Link 5 added
br-c7cc901345e8: udev initialized link
br-c7cc901345e8: Saved original MTU: 1500
docker0: Flags change: +UP +MULTICAST +BROADCAST
docker0: Link 3 added
docker0: udev initialized link
docker0: Saved original MTU: 1500
enp0s31f6: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
enp0s31f6: Link 2 added
enp0s31f6: udev initialized link
enp0s31f6: Saved original MTU: 1500
lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING
lo: Link 1 added
lo: udev initialized link
lo: Saved original MTU: 0
vlan4000: Adding address: fe80::921b:eff:fe93:5015/64 (valid forever)
vlan4000: Gained IPv6LL
tun0: Adding address: 10.0.0.13/24 (valid forever)
vlan4000: Adding address: 10.0.2.3/24 (valid forever)
br-c7cc901345e8: Adding address: 172.18.0.1/16 (valid forever)
docker0: Adding address: 172.17.0.1/16 (valid forever)
enp0s31f6: Adding address: 95.216.96.148/26 (valid forever)
lo: Adding address: 127.0.0.1/8 (valid forever)
rtnl: received address with invalid family 129, ignoring
Enumeration completed
Bus n/a: changing state AUTHENTICATING → HELLO
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1
reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RequestName
cookie=2 reply_cookie=0 signature=su error-name=n/a error-message=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch
cookie=3 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a
path=/org/freedesktop/network1/link/_312
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=4
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a
path=/org/freedesktop/network1/link/_38
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=5
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a
path=/org/freedesktop/network1/link/_36
interface=org.freedesktop.DBus.Properties
[Bug 1587695] Re: package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This bug was fixed in the package amavisd-new - 1:2.11.0-5ubuntu2 --- amavisd-new (1:2.11.0-5ubuntu2) eoan; urgency=medium * do not report FQDN misconfiguration through apport (LP: #1587695) - d/amavisd-new.apport: apport script - d/amavisd-new.dirs: layout required dirs - d/control: b-dep on dh_apport - d/rules: enable dh_apport -- Christian Ehrhardt Mon, 08 Apr 2019 16:48:34 +0200 ** Changed in: amavisd-new (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587695 Title: package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1587695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824430] Re: disco dist-upgrader tarball has a broken symlink in it
I followed the test case from the bug description and no longer received the message regarding livepatch being disabled. Additionally inspecting the downloaded dist-upgrader tarball we can see that the symlink is now good. bdmurray@clean-cosmic-amd64:/tmp/ubuntu-release-upgrader-jjhazydt$ file DistUpgrade DistUpgrade: broken symbolic link to DistUpgrade bdmurray@clean-cosmic-amd64:/tmp/ubuntu-release-upgrader-jjhazydt$ cat DistUpgradeVersion.py VERSION = '19.04.16.1' bdmurray@clean-cosmic-amd64:/tmp/ubuntu-release-upgrader-jjhazydt$ cd - /tmp/ubuntu-release-upgrader-27u554bb bdmurray@clean-cosmic-amd64:/tmp/ubuntu-release-upgrader-27u554bb$ file DistUpgrade DistUpgrade: symbolic link to . bdmurray@clean-cosmic-amd64:/tmp/ubuntu-release-upgrader-27u554bb$ cat DistUpgradeVersion.py VERSION = '19.04.16.2' Setting to verification-done. ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824430 Title: disco dist-upgrader tarball has a broken symlink in it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1824430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824245] Re: Can't create a bootable disk by doing image creation on a loop device
I've verified locally that this does fix my issue when I patch grub myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824245 Title: Can't create a bootable disk by doing image creation on a loop device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826458] [NEW] Remove gadmin-samba from the archive
Public bug reported: Please remove gadmin-samba from the archive. Reasons: a) upstream url from d/control is gone: http://www.gadmintools.org/ b) hasn't been updated in years: $ rmadison gadmin-samba gadmin-samba | 0.3.2-0ubuntu1 | precise/universe | source, amd64, armel, armhf, i386, powerpc gadmin-samba | 0.3.2-0ubuntu1 | trusty/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el gadmin-samba | 0.3.2-0ubuntu1 | xenial/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x gadmin-samba | 0.3.2-0ubuntu2 | bionic/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x gadmin-samba | 0.3.2-0ubuntu2 | cosmic/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x gadmin-samba | 0.3.2-0ubuntu2 | disco/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x gadmin-samba | 0.3.2-0ubuntu2 | eoan/universe| source, amd64, arm64, armhf, i386, ppc64el, s390x c) it generates incorrect configuration for modern samba. Here is the result of testparm on disco right after having run gadmin-samba: andreas@disco-desktop:~$ testparm WARNING: The "null passwords" option is deprecated Unknown parameter encountered: "password level" Ignoring unknown parameter "password level" WARNING: The "client schannel" option is deprecated WARNING: The "server schannel" option is deprecated Unknown parameter encountered: "update encrypted" Ignoring unknown parameter "update encrypted" WARNING: The "idmap uid" option is deprecated WARNING: The "idmap gid" option is deprecated Unknown parameter encountered: "winbind trusted domains only" Ignoring unknown parameter "winbind trusted domains only" Load smb config files from /etc/samba/smb.conf WARNING: The "null passwords" option is deprecated Unknown parameter encountered: "password level" Ignoring unknown parameter "password level" WARNING: The "client schannel" option is deprecated WARNING: The "server schannel" option is deprecated Unknown parameter encountered: "update encrypted" Ignoring unknown parameter "update encrypted" WARNING: The "idmap uid" option is deprecated WARNING: The "idmap gid" option is deprecated Unknown parameter encountered: "winbind trusted domains only" Ignoring unknown parameter "winbind trusted domains only" Loaded services file OK. WARNING: socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 This warning is printed because you set one of the following options: SO_SNDBUF, SO_RCVBUF, SO_SNDLOWAT, SO_RCVLOWAT Modern server operating systems are tuned for high network performance in the majority of situations; when you set 'socket options' you are overriding those settings. Linux in particular has an auto-tuning mechanism for buffer sizes (SO_SNDBUF, SO_RCVBUF) that will be disabled if you specify a socket buffer size. This can potentially cripple your TCP/IP stack. Getting the 'socket options' correct can make a big difference to your performance, but getting them wrong can degrade it by just as much. As with any other low level setting, if you must make changes to it, make small changes and test the effect before making any large changes. d) the GUI itself shows errors (see attached screenshot) e) google search found no other places where this might have moved to. github search only shows two results, both just packaging repositories and several years old (https://github.com/search?q=gadmin-samba=opensearch) ** Affects: gadmin-samba (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gadmin-samba-disco.png" https://bugs.launchpad.net/bugs/1826458/+attachment/5259105/+files/gadmin-samba-disco.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826458 Title: Remove gadmin-samba from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gadmin-samba/+bug/1826458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826163] Re: linux-aws: 4.18.0-1015.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826163 Title: linux-aws: 4.18.0-1015.17 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1517768] Re: GCC internal compiler error ... gen_type_die_with_usage, at dwarf2out.c:19493
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcc-4.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517768 Title: GCC internal compiler error ... gen_type_die_with_usage, at dwarf2out.c:19493 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1517768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826160] Re: linux-raspi2: 4.18.0-1013.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826160 Title: linux-raspi2: 4.18.0-1013.15 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826319] Re: Please upgrade cgdb to newest version (0.7.0)
** Changed in: cgdb (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826319 Title: Please upgrade cgdb to newest version (0.7.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgdb/+bug/1826319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616123] Re: rpc-svcgssd.service uses incorrrect variable SVCGSSDARGS
** Changed in: nfs-utils (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: nfs-utils (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: nfs-utils (Ubuntu Cosmic) Status: Confirmed => In Progress ** Description changed: - In /etc/default/nfs-kernel-server you can specify parameters for - rpc.svcgssd: + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Case] + * install nfs-server and a kerberos server. Use "EXAMPLE.LOCAL" for the realm, and "localhost" for the servers, when prompted: + sudo apt install nfs-server krb5-kdc krb5-user krb5-admin-server + + * create the EXAMPLE.LOCAL realm. Use any password you want for the database master key, it won't be requested again: + sudo krb5_newrealm + + * create a principal for the nfs service: + sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)" + + * extract the key into the system wide keytab: + sudo kadmin.local -q "ktadd -k /etc/krb5.keytab nfs/$(hostname -f)" + + * edit /etc/default/nfs-common and enable gssd: + NEED_GSSD=y + + * edit /etc/default/nfs-kernel-server and add an option to RPCSVCGSSDOPTS: + RPCSVCGSSDOPTS="-v" + + * restart nfs-server + sudo systemctl restart nfs-server + + * verify if /run/sysconfig/nfs-utils has the option we added above: + $ cat /run/sysconfig/nfs-utils + PIPEFS_MOUNTPOINT=/run/rpc_pipefs + RPCNFSDARGS=" 8" + RPCMOUNTDARGS="--manage-gids" + STATDARGS="" + RPCSVCGSSDARGS="-v" + + * Verify the running rpc.gssd process. Without the fix, it won't have the "-v" option: + ps axw|grep svcgssd|grep -v grep + 4285 ? Ss 0:00 /usr/sbin/rpc.svcgssd + + With the fix, right after installing the udpated packages, the option we added to /etc/default/nfs-kernel-server will show up: + ps axw|grep svcgssd|grep -v grep + 5656 ? Ss 0:00 /usr/sbin/rpc.svcgssd -v + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + + [Original Description] + In /etc/default/nfs-kernel-server you can specify parameters for rpc.svcgssd: # Options for rpc.svcgssd. RPCSVCGSSDOPTS="-n" But the variable is named incorrectly in /lib/systemd/system/rpc- svcgssd.service: ExecStart=/usr/sbin/rpc.svcgssd $SVCGSSDARGS ** Description changed: [Impact] - - * An explanation of the effects of the bug on users and - - * justification for backporting the fix to the stable release. - - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + Command line options set for rpc.svcgssd in the /etc/default/nfs-kernel-server file are not passed on to the service, being ignored. [Test Case] * install nfs-server and a kerberos server. Use "EXAMPLE.LOCAL" for the realm, and "localhost" for the servers, when prompted: sudo apt install nfs-server krb5-kdc krb5-user krb5-admin-server * create the EXAMPLE.LOCAL realm. Use any password you want for the database master key, it won't be requested again: sudo krb5_newrealm * create a principal for the nfs service: sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)" * extract the key into the system wide keytab: sudo kadmin.local -q "ktadd -k /etc/krb5.keytab nfs/$(hostname -f)" * edit /etc/default/nfs-common and enable gssd: NEED_GSSD=y * edit /etc/default/nfs-kernel-server and add an option to RPCSVCGSSDOPTS: RPCSVCGSSDOPTS="-v" * restart nfs-server sudo systemctl restart nfs-server * verify if /run/sysconfig/nfs-utils has the option we added above: $ cat /run/sysconfig/nfs-utils PIPEFS_MOUNTPOINT=/run/rpc_pipefs RPCNFSDARGS=" 8" RPCMOUNTDARGS="--manage-gids" STATDARGS="" RPCSVCGSSDARGS="-v" * Verify the running rpc.gssd process. Without the fix, it won't have the "-v" option: ps axw|grep svcgssd|grep -v grep - 4285 ? Ss 0:00 /usr/sbin/rpc.svcgssd + 4285 ? Ss 0:00 /usr/sbin/rpc.svcgssd With the fix, right after installing the udpated packages, the option we added to /etc/default/nfs-kernel-server will show up: ps axw|grep svcgssd|grep -v grep - 5656 ? Ss 0:00 /usr/sbin/rpc.svcgssd -v + 5656 ? Ss 0:00
[Bug 1616123] Re: rpc-svcgssd.service uses incorrrect variable SVCGSSDARGS
** Changed in: nfs-utils (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: nfs-utils (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: nfs-utils (Ubuntu Cosmic) Status: Confirmed => In Progress ** Description changed: - In /etc/default/nfs-kernel-server you can specify parameters for - rpc.svcgssd: + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Case] + * install nfs-server and a kerberos server. Use "EXAMPLE.LOCAL" for the realm, and "localhost" for the servers, when prompted: + sudo apt install nfs-server krb5-kdc krb5-user krb5-admin-server + + * create the EXAMPLE.LOCAL realm. Use any password you want for the database master key, it won't be requested again: + sudo krb5_newrealm + + * create a principal for the nfs service: + sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)" + + * extract the key into the system wide keytab: + sudo kadmin.local -q "ktadd -k /etc/krb5.keytab nfs/$(hostname -f)" + + * edit /etc/default/nfs-common and enable gssd: + NEED_GSSD=y + + * edit /etc/default/nfs-kernel-server and add an option to RPCSVCGSSDOPTS: + RPCSVCGSSDOPTS="-v" + + * restart nfs-server + sudo systemctl restart nfs-server + + * verify if /run/sysconfig/nfs-utils has the option we added above: + $ cat /run/sysconfig/nfs-utils + PIPEFS_MOUNTPOINT=/run/rpc_pipefs + RPCNFSDARGS=" 8" + RPCMOUNTDARGS="--manage-gids" + STATDARGS="" + RPCSVCGSSDARGS="-v" + + * Verify the running rpc.gssd process. Without the fix, it won't have the "-v" option: + ps axw|grep svcgssd|grep -v grep + 4285 ? Ss 0:00 /usr/sbin/rpc.svcgssd + + With the fix, right after installing the udpated packages, the option we added to /etc/default/nfs-kernel-server will show up: + ps axw|grep svcgssd|grep -v grep + 5656 ? Ss 0:00 /usr/sbin/rpc.svcgssd -v + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + + [Original Description] + In /etc/default/nfs-kernel-server you can specify parameters for rpc.svcgssd: # Options for rpc.svcgssd. RPCSVCGSSDOPTS="-n" But the variable is named incorrectly in /lib/systemd/system/rpc- svcgssd.service: ExecStart=/usr/sbin/rpc.svcgssd $SVCGSSDARGS ** Description changed: [Impact] - - * An explanation of the effects of the bug on users and - - * justification for backporting the fix to the stable release. - - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + Command line options set for rpc.svcgssd in the /etc/default/nfs-kernel-server file are not passed on to the service, being ignored. [Test Case] * install nfs-server and a kerberos server. Use "EXAMPLE.LOCAL" for the realm, and "localhost" for the servers, when prompted: sudo apt install nfs-server krb5-kdc krb5-user krb5-admin-server * create the EXAMPLE.LOCAL realm. Use any password you want for the database master key, it won't be requested again: sudo krb5_newrealm * create a principal for the nfs service: sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)" * extract the key into the system wide keytab: sudo kadmin.local -q "ktadd -k /etc/krb5.keytab nfs/$(hostname -f)" * edit /etc/default/nfs-common and enable gssd: NEED_GSSD=y * edit /etc/default/nfs-kernel-server and add an option to RPCSVCGSSDOPTS: RPCSVCGSSDOPTS="-v" * restart nfs-server sudo systemctl restart nfs-server * verify if /run/sysconfig/nfs-utils has the option we added above: $ cat /run/sysconfig/nfs-utils PIPEFS_MOUNTPOINT=/run/rpc_pipefs RPCNFSDARGS=" 8" RPCMOUNTDARGS="--manage-gids" STATDARGS="" RPCSVCGSSDARGS="-v" * Verify the running rpc.gssd process. Without the fix, it won't have the "-v" option: ps axw|grep svcgssd|grep -v grep - 4285 ? Ss 0:00 /usr/sbin/rpc.svcgssd + 4285 ? Ss 0:00 /usr/sbin/rpc.svcgssd With the fix, right after installing the udpated packages, the option we added to /etc/default/nfs-kernel-server will show up: ps axw|grep svcgssd|grep -v grep - 5656 ? Ss 0:00 /usr/sbin/rpc.svcgssd -v + 5656 ? Ss 0:00
[Bug 1826455] [NEW] update to openjdk 11.0.3 in 18.04 LTS
Public bug reported: Upstream release was on 16 Apr 2019 https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-April/000951.html Disco got the update a week ago so I'm filing this bug to track progress for bionic. ** Affects: openjdk-lts (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/1826455 Title: update to openjdk 11.0.3 in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1826455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822340] Re: [UIFe] motd messaging rewrite
Verified [...]ubuntu6 * Package built successfully, so motd output formatting is correct * motd output is correct, wrt counting stuff: (1) ESM disabled [will only happen with new ua client, so not that relevant right now] root@tt:~# /usr/lib/update-notifier/apt-check --human-readable Extended Security Maintenance (ESM) is not enabled. 2 updates can be installed immediately. 0 of these updates are security updates. Enable ESM to receive 5 additional security updates. See 'ua enable esm' or https://ubuntu.com/esm (2) ESM enabled root@tt:~# /usr/lib/update-notifier/apt-check --human-readable Extended Security Maintenance (ESM) is enabled. 7 updates can be installed immediately. 5 of these updates are provided through ESM. 5 of these updates are security updates. (3) ESM fully disabled (no sources.list entry) root@tt:~# ubuntu-advantage disable-esm Running apt-get update... OK Ubuntu ESM repository disabled. root@tt:~# /usr/lib/update-notifier/apt-check --human-readable 2 updates can be installed immediately. 0 of these updates are security updates. ** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822340 Title: [UIFe] motd messaging rewrite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1822340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826456] [NEW] installer crashes error input output on copying files from ubs drive to hard disk
Public bug reported: Can't install ubuntu from usb. Crashes copying files to HD. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 17:30:45 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826456 Title: installer crashes error input output on copying files from ubs drive to hard disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1826456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826453] [NEW] Grub2 Booting in blind mode due to "invalid video mode specification `text'"
Public bug reported: In a Ubuntu 16.04.6 VM, which runs as a Gen2 VM on Hyper-V, I add GRUB_GFXPAYLOAD_LINUX="text" into /etc/default/grub and run update-grub; next, grub2 prints the below error: error: invalid video mode specification `text'. Booting in blind mode This means grub2 passes a zero value for the "lfb_base" to Linux kernel, which then fails to reserve the framebuffer MMIO range in drivers/hv/vmbus_drv.c: vmbus_reserve_fb(); as a result, when we pass through a PCIe device to the VM, the PCIe device may get a PCI MMIO BAR in the FB MMIO range, causing a conflict, and the PCIe device can not work in the VM. The issue can not reproduce with Ubuntu 18.04. It turns out the grub2 in Ubuntu 18.04 has the below fix: video: skip 'text' gfxpayload if not supported, to fallback to default (https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/commit/?id=38d9e2f862a96a039ae8ca8b87b8615d154ceda4). I'm asking the patch author (Mathieu Trudel-Lapierre) to submit the patch to the upstream grub and this is the upstream bug link: https://savannah.gnu.org/bugs/?56217 . Here this launchpad bug is for Ubuntu 16.04 and 14.04. ** Affects: grub2 (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/1826453 Title: Grub2 Booting in blind mode due to "invalid video mode specification `text'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1826453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572908] Re: sssd-ad pam_sss(cron:account): Access denied for user
Sponsored for 'eoan', considering the patch is merged upstream and already part of debian. Nitpick: - Rename quilt patch d/p/GPO_CROND-customization.diff to d/p/GPO_CROND-customization.patch - Rework the DEP3 header Note for next sponsoring (Disco debdiff) I haven't look others yet. A quick look at the Disco debdiff, the actual proposed disco version would need to be changed from "1.16.3-3ubuntu2" to "1.16.3-3ubuntu1.1" Thanks Eric ** Changed in: sssd (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572908 Title: sssd-ad pam_sss(cron:account): Access denied for user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1572908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)
WaylandEnable=false workaround also works for 19.04 Nvidia 340 and 390 drivers still having issues with 19.04 but does not seem to be the cause of the gdm problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1823363] Re: Running "Junk Mail Controls" does not appear in Activity Manager
Thank you for thanking me and letting me know! It's greatly appreciated. On Thu, Apr 25, 2019, 9:20 AM Olivier Tilloy wrote: > Thanks Paul for the upstream report! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1823363 > > Title: > Running "Junk Mail Controls" does not appear in Activity Manager > > Status in Mozilla Thunderbird: > Confirmed > Status in thunderbird package in Ubuntu: > Confirmed > > Bug description: > "Running Junk Mail Controls" does not appear in Activity Manager > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1 > ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 > Uname: Linux 4.18.0-17-generic x86_64 > AddonCompatCheckDisabled: False > ApportVersion: 2.20.10-0ubuntu13.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC2: jeb3837 F pulseaudio >/dev/snd/controlC1: jeb3837 F pulseaudio >/dev/snd/controlC0: jeb3837 F pulseaudio > BuildID: 20190325141154 > Channel: Unavailable > CurrentDesktop: ubuntu:GNOME > Date: Fri Apr 5 11:09:14 2019 > Extensions: extensions.sqlite corrupt or missing > ForcedLayersAccel: False > IfupdownConfig: ># interfaces(5) file used by ifup(8) and ifdown(8) >auto lo >iface lo inet loopback > IncompatibleExtensions: Unavailable (corrupt or non-existant > compatibility.ini or extensions.sqlite) > InstallationDate: Installed on 2018-08-17 (231 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > IpRoute: >default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 >169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 >192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src > 192.168.86.25 metric 600 >192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 > linkdown > Locales: extensions.sqlite corrupt or missing > MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 > PrefSources: prefs.js > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use) > RunningIncompatibleAddons: False > SourcePackage: thunderbird > SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 > Themes: extensions.sqlite corrupt or missing > UpgradeStatus: Upgraded to cosmic on 2018-10-19 (168 days ago) > dmi.bios.date: 09/21/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 080016 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: A880G+ > dmi.board.vendor: BIOSTAR Group > dmi.chassis.asset.tag: None > dmi.chassis.type: 3 > dmi.chassis.vendor: BIOSTAR Group > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: A880G+ > dmi.product.sku: To Be Filled By O.E.M. > dmi.sys.vendor: BIOSTAR Group > > To manage notifications about this bug go to: > https://bugs.launchpad.net/thunderbird/+bug/1823363/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823363 Title: Running "Junk Mail Controls" does not appear in Activity Manager To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1823363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826290] Re: geoclue mozilla location api key rate limited
Same.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}
Hopefully we can get Mozilla to up the limit for the API key.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825587] Re: non-existent temporary desktop file appears on desktop
it would be sufficient just to symlink libfm-qt.so.6 -> libfm-qt.so in /usr/lib/x86* - maybe apt don't like it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826160] Re: linux-raspi2: 4.18.0-1013.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 25. April 2019 10:37 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 25. April 2019 20:07 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826160 Title: linux-raspi2: 4.18.0-1013.15 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826451] [NEW] crashes with mysql and php7.0 on arm
Public bug reported: I installed Linaro-Trusty-Server on Cubietruck-plus that works fine, but I wont for Upgrade to a newer Version. The System don't will boot up. The File /etc/lsb-release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS" The output from apt-cache: linaro@cubietruck-plus:~$ apt-cache policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://ports.ubuntu.com/ubuntu-ports xenial/universe armhf Packages release v=16.04,o=Ubuntu,a=xenial,n=xenial,l=Ubuntu,c=universe,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com/ubuntu-ports xenial/main armhf Packages release v=16.04,o=Ubuntu,a=xenial,n=xenial,l=Ubuntu,c=main,b=armhf origin ports.ubuntu.com Pinned packages: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dist-upgrade.zip" https://bugs.launchpad.net/bugs/1826451/+attachment/5259096/+files/dist-upgrade.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826451 Title: crashes with mysql and php7.0 on arm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1826451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826146] Re: linux-snapdragon: 5.0.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-disco ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826150 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 25. April 2019 13:06 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 25. April 2019 20:06 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826146 Title: linux-snapdragon: 5.0.0-1011.11 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826163] Re: linux-aws: 4.18.0-1015.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 25. April 2019 09:37 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 25. April 2019 20:07 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826163 Title: linux-aws: 4.18.0-1015.17 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826448] [NEW] debmirror doesn't work with Canonical ESM
Public bug reported:
debmirror tries to put Canonical Ubuntu Extended Support repos in the
wrong dist (e.g. 'trusty' instead of 'trusty-security', which breaks the
paths it looks for on the remote server. This is because there is a
check for origin='Ubuntu' but not origin='UbuntuESM'. This diff fixes
it:
} elsif ($origin eq "Ubuntu" or $origin eq "Canonical") {
to
} elsif ($origin eq "Ubuntu" or $origin eq "UbuntuESM" or $origin eq
"Canonical") {
I was able to reproduce with the latest versions on both Trusty and
Bionic.
** Affects: debmirror (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/1826448
Title:
debmirror doesn't work with Canonical ESM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1826448/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825587] Re: non-existent temporary desktop file appears on desktop
If you edit your repositories to include sources and make sure to use `sudo` on any `apt` commands, Alf's instructions could work, but it's an advanced and not a good ultimate solution. That solution has been implemented upstream and will be forthcoming. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826447] [NEW] Azure: Backport vIOMMU driver (increase vCPU limits)
Public bug reported: Description: To support VM instances with >255 vCPUS, we need the patch set below backported to the Azure 4.18 kernel. These patches include - - New Hyper-V IOMMU driver. This driver will be Hyper-V specific. - Minor update to the Hyper-V specific virtual PCI code. Need to expand the size of an array to allow for a larger number of vCPUs. There are very large VM instance sizes coming to Azure in 2019, and Ubuntu will require the following patches in order to function properly: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37 ** Affects: linux-azure (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/1826447 Title: Azure: Backport vIOMMU driver (increase vCPU limits) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825356] Re: libvirt silently fails to attach a cinder ceph volume
I wasn't able to recreate this on a bionic-queens deploy. My deployment was a bit different, quite a bit simpler. Results are attached. I did notice that you're using bluestore so it might be worth testing with that. Again logs or a small recreate scenarios will be useful to help us figure this out. ** Attachment added: "bionic-queens-results.txt" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1825356/+attachment/5259095/+files/bionic-queens-results.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825356 Title: libvirt silently fails to attach a cinder ceph volume To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1825356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825430] Re: linux-hwe-edge: 5.0.0-13.14~18.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825430 Title: linux-hwe-edge: 5.0.0-13.14~18.04.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825324] Re: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825324 Title: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825843] Re: systemd issues with bionic-rocky causing nagios alert and can't restart daemon
Reviewed: https://review.opendev.org/655434 Committed: https://git.openstack.org/cgit/openstack/charm-ceph-radosgw/commit/?id=ff90c0f058073292739bab33309d700d9bcfc4c6 Submitter: Zuul Branch:master commit ff90c0f058073292739bab33309d700d9bcfc4c6 Author: Pete Vander Giessen Date: Wed Apr 24 09:39:26 2019 -0400 Fix spurious nagios alerts for radosgw service. Currently, when the charm tears down the default radosgw daemon in order to make way for per host daemons, it does not remove the nrpe check for the daemon. This PR fixes the issue. It also closes a gap where alerts for the per host daemons are not setup until a hook that happens to call update_nrpe_checks as a side-effect is run. Change-Id: I7621b9671b010a77bb3e94bdd1e80f45274c73e5 Closes-Bug: #1825843 ** Changed in: charm-ceph-radosgw Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825843 Title: systemd issues with bionic-rocky causing nagios alert and can't restart daemon To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-radosgw/+bug/1825843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650880] Re: version of xpra in 16.04 (LTS) is an explicitly unsupported version
while the choice of version may have been unfortunate, it cannot be changed now. Closing as fixed for bionic and later. Closing as wontfix for xenial. ** Changed in: xpra (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650880 Title: version of xpra in 16.04 (LTS) is an explicitly unsupported version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpra/+bug/1650880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825868] Re: System tray icon doesn't appear
Sorry, I changed to public. Using Topicons Redux fixes this issue, but I don't call that a solution. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825868 Title: System tray icon doesn't appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1825868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826443] [NEW] GIMP crashed while being idle
Public bug reported:
```
GNU Image Manipulation Program version 2.10.10
git-describe: 5e662c37d7cc472266989f259c4ae579d66a6617
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
7.3.0-27ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
using GEGL version 0.4.14 (compiled against version 0.4.14)
using GLib version 2.56.3 (compiled against version 2.56.3)
using GdkPixbuf version 2.36.11 (compiled against version 2.36.11)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.40.14 (compiled against version 1.40.14)
using Fontconfig version 2.12.6 (compiled against version 2.12.6)
using Cairo version 1.15.10 (compiled against version 1.15.10)
```
> fatal error: Abgebrochen
Stack trace:
```
# Stack traces obtained from PID 10089 - Thread 10089 #
[New LWP 10091]
[New LWP 10092]
[New LWP 10093]
[New LWP 10094]
[New LWP 11224]
[New LWP 15828]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7facd3c63384 in __libc_read (fd=22, buf=0x7ffd9a591ed0, nbytes=256) at
../sysdeps/unix/sysv/linux/read.c:27
Id Target Id Frame
* 1Thread 0x7facd8a93e00 (LWP 10089) "gimp-2.10" 0x7facd3c63384 in
__libc_read (fd=22, buf=0x7ffd9a591ed0, nbytes=256) at
../sysdeps/unix/sysv/linux/read.c:27
2Thread 0x7faccac5e700 (LWP 10091) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7facc2496700 (LWP 10092) "gmain" 0x7facd3975bf9 in
__GI___poll (fds=0x557727ada3e0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7facc1c95700 (LWP 10093) "gdbus" 0x7facd3975bf9 in
__GI___poll (fds=0x557727b8fd60, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
5Thread 0x7faca208d700 (LWP 10094) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7faca0a77700 (LWP 11224) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
7Thread 0x7faca188c700 (LWP 15828) "paint" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 7 (Thread 0x7faca188c700 (LWP 15828)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7facd44a517f in g_cond_wait () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x5577257f8dbf in ?? ()
No symbol table info available.
#3 0x7facd4487105 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7facd3c596db in start_thread (arg=0x7faca188c700) at
pthread_create.c:463
pd = 0x7faca188c700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140379421198080,
-131350744636186408, 140379421194496, 0, 93971398410960, 140727192985392,
104737419910848728, 104988769269981400}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#5 0x7facd398288f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 6 (Thread 0x7faca0a77700 (LWP 11224)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7facd44a517f in g_cond_wait () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7facd5b07ab1 in ?? () from /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7facd4487105 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7facd3c596db in start_thread (arg=0x7faca0a77700) at
pthread_create.c:463
pd = 0x7faca0a77700
now =
unwind_buf = {cancel_jmp_buf =
[Bug 1825996] Re: Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04
*** This bug is a duplicate of bug 1825699 *** https://bugs.launchpad.net/bugs/1825699 It can boot but if I remove i2c_i801 from backlist touch pad does not work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825996 Title: Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826051] Re: VMs go to 100% CPU after live migration from Trusty to Bionic
Hi Christian, I cleared off the host leaving just the hung VM on it before running those commands. Because the VM is hung up, I'm not able to grab /proc/kallsyms and /proc/modules from it. I tried grabbing it from another VM using the same image/kernel, but it has kernel page tables isolation enabled, so I presume that's why it hasn't worked properly. If this output it critical, I would need to stage some VMs and grab those files and hope they fail live migration. Below is the output you requested. This is new to me, so hopefully it's correct. Thank you, Corey Melanson $ sudo perf kvm stat --live Analyze events for all VMs, all VCPUs: VM-EXITSamples Samples% Time%Min TimeMax Time Avg time MSR_WRITE 26919038.63%42.74% 0.65us855.99us 1.60us ( +- 2.06% ) PREEMPTION_TIMER 22262231.95%28.06% 0.61us946.08us 1.27us ( +- 2.46% ) PENDING_INTERRUPT 20386229.25%29.11% 0.62us799.59us 1.44us ( +- 2.57% ) EXTERNAL_INTERRUPT 1209 0.17% 0.09% 0.43us123.06us 0.78us ( +- 13.36% ) Total Samples:696883, Total events handled time:1009576.31us. $ sudo perf kvm stat live -d 30 --vcpu 0 --pid=53454 Analyze events for pid(s) 53454, VCPU 0: VM-EXITSamples Samples% Time%Min TimeMax Time Avg time MSR_WRITE222799950.05%54.64% 0.64us 1228.11us 1.78us ( +- 0.74% ) PENDING_INTERRUPT111294125.00%25.20% 0.61us 1080.49us 1.64us ( +- 1.10% ) PREEMPTION_TIMER110944724.92%20.13% 0.63us 1017.27us 1.32us ( +- 1.07% ) EXTERNAL_INTERRUPT 1350 0.03% 0.03% 0.44us366.12us 1.56us ( +- 28.55% ) Total Samples:4451737, Total events handled time:7264173.95us. $ sudo perf stat -e 'kvm:*' sleep 30s Performance counter stats for 'sleep 30s': 0 kvm:kvm_entry 0 kvm:kvm_hypercall 0 kvm:kvm_hv_hypercall 0 kvm:kvm_pio 0 kvm:kvm_fast_mmio 0 kvm:kvm_cpuid 0 kvm:kvm_apic 0 kvm:kvm_exit 0 kvm:kvm_inj_virq 0 kvm:kvm_inj_exception 0 kvm:kvm_page_fault 0 kvm:kvm_msr 0 kvm:kvm_cr 0 kvm:kvm_pic_set_irq 0 kvm:kvm_apic_ipi 0 kvm:kvm_apic_accept_irq 0 kvm:kvm_eoi 0 kvm:kvm_pv_eoi 0 kvm:kvm_nested_vmrun 0 kvm:kvm_nested_intercepts 0 kvm:kvm_nested_vmexit 0 kvm:kvm_nested_vmexit_inject 0 kvm:kvm_nested_intr_vmexit 0 kvm:kvm_invlpga 0 kvm:kvm_skinit 0 kvm:kvm_emulate_insn 0 kvm:vcpu_match_mmio 0 kvm:kvm_write_tsc_offset 0 kvm:kvm_update_master_clock 0 kvm:kvm_track_tsc 0 kvm:kvm_pml_full 0 kvm:kvm_ple_window 0 kvm:kvm_pvclock_update 0 kvm:kvm_wait_lapic_expire 0 kvm:kvm_enter_smm
[Bug 1826290] Re: geoclue mozilla location api key rate limited
I tried it again just now (roughly around the same time of day I tried
this previously):
$ curl https://location.services.mozilla.com/v1/geolocate?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826319] Re: Please upgrade cgdb to newest version (0.7.0)
** Bug watch added: Debian Bug tracker #778284 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778284 ** Also affects: cgdb (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778284 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826319 Title: Please upgrade cgdb to newest version (0.7.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgdb/+bug/1826319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826386] Re: 19.04, rdesktop is broken
** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826386 Title: 19.04, rdesktop is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdesktop/+bug/1826386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825741] Re: Multiple instances of global menu entries
Ok thank you for that. I’ve managed to reproduce the issue locally now. ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Triaged ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825741 Title: Multiple instances of global menu entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808951] Re: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object
For the Ubuntu SRU, a new version of the package has been uploaded to eoan and disco, and is awaiting review by the SRU team in disco [1]. [1] https://launchpad.net/ubuntu/disco/+queue?queue_state=1_text=nova -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808951 Title: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1808951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
I have an APC UPS too. Great find. Who would have guessed an IRQ handling problem message from the kernel was due to a serial or USB device. Wow. On Thu, Apr 18, 2019 at 7:16 AM Kai-Heng Feng wrote: > Thanks for the info. Have anyone filed a bug against upstream apcupsd? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1781016 > > Title: > Slow flood of do_IRQ: No irq for vector > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Every few seconds I get something like this in my dmesg: > > [44984.933221] do_IRQ: 1.34 No irq handler for vector > [44986.933976] do_IRQ: 1.34 No irq handler for vector > [44991.935614] do_IRQ: 1.34 No irq handler for vector > [45004.938590] do_IRQ: 1.34 No irq handler for vector > [45005.939002] do_IRQ: 4.34 No irq handler for vector > [45034.949161] do_IRQ: 4.34 No irq handler for vector > [45051.954569] do_IRQ: 4.34 No irq handler for vector > [45058.956019] do_IRQ: 4.34 No irq handler for vector > [45062.957727] do_IRQ: 4.34 No irq handler for vector > [45063.958204] do_IRQ: 4.34 No irq handler for vector > [45073.961103] do_IRQ: 4.34 No irq handler for vector > > The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, > 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log > is just messages like above with varying #.## numbers. > > I researched it and tried disabling irqbalance. It had no effect, the > messages continued. > > The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. > I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 > NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never > occurred before installing 18.03 on the same hardware. No overclocking > whatsoever has ever been done to this machine. > > Also, I had to disable selective suspend on USB in this version to > prevent major USB issues, which was not required in 17.10, that might > be related. > > My system seems stable, but spurious IRQs can't be good. I'd like to > resolve this if possible. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-26-generic 4.15.0-26.28 > ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 > Uname: Linux 4.15.0-26-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: gdm2145 F pulseaudio > doug 3736 F pulseaudio >/dev/snd/controlC1: gdm2145 F pulseaudio > doug 3736 F pulseaudio > Date: Tue Jul 10 12:49:00 2018 > HibernationDevice: > > InstallationDate: Installed on 2017-06-26 (379 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > MachineType: System manufacturer System Product Name > ProcEnviron: >LANGUAGE=en_CA:en >TERM=xterm-256color >PATH=(custom, no user) >LANG=en_CA.UTF-8 >SHELL=/bin/bash > ProcFB: > > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic > root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal > video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 > PulseList: >Error: command ['pacmd', 'list'] failed with exit code 1: Home > directory not accessible: Permission denied >No PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-4.15.0-26-generic N/A >linux-backports-modules-4.15.0-26-generic N/A >linux-firmware 1.173.1 > RfKill: > > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/19/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 4011 > dmi.board.asset.tag: Default string > dmi.board.name: PRIME B350-PLUS > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title: Slow flood
[Bug 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs
There is no problem with suspend. I want to choose " when lid closed do nothing" I want that apps running on background when lid closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825219 Title: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797748] Re: GNOME Extensions website doesn't find connector
Similar problem here, although the GNOME Integration extension works in Chromium for me. In Firefox, it remains broken. Ubuntu version: 18.04.2 LTS Chromium version: 73.0.3683.86 (installed via Software Center) GNOME Shell Integration version: 10.1 ( installed via https://chrome.google.com/webstore/detail/gnome-shell-integration/gphhapmejobijbbhgpjhcjognlahblep ) Firefox version: 66.0.3 Quantum (installed via Software Center) GNOME Shell Integration version: 10.1 ( installed via https://addons.mozilla.org/en-US/firefox/addon/gnome-shell-integration/ ) chrome-gnome-shell version: 10-1 (installed via apt-get) Please let me know if additional info is needed. ** Attachment added: "kpProcCpuInfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1797748/+attachment/5259092/+files/kpProcCpuInfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797748 Title: GNOME Extensions website doesn't find connector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1797748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825419] Re: Rancid deb missing arrancid executible
Ok, thanks. I missed that when perusing the changelogs. My mistake, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825419 Title: Rancid deb missing arrancid executible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rancid/+bug/1825419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824560] Re: pentobi fails to startup in Ubuntu 19.04 beta
** Also affects: pentobi (Ubuntu Eoan) Importance: Undecided Status: Fix Released ** Also affects: pentobi (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: pentobi (Ubuntu Disco) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824560 Title: pentobi fails to startup in Ubuntu 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pentobi/+bug/1824560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823753] Re: arm64: cma_alloc errors at boot
I only had time to look briefly, but here's a few notes. Firstly, a workaround for now is passing cma=0 on the kernel command line. I feel like there must be something wrong here if everything just works fine with CMA turned off, because obviously devices are getting CMA allocations when they don't really need them. I'm not familiar with CMA, but my assumption would be that you want as small a region as possible for it and thus you want to only use it for devices where it's actually necessary. Shooting from the hip I'd guess that one of two things is wrong, either some devices are doing their allocations wrong and getting CMA memory when they don't need it, or the DMA allocator is over zealous in its use of CMA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826273] Re: Potential Side-channel during Graphics Rendering
** Information type changed from Private Security to Public Security ** Changed in: onboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826273 Title: Potential Side-channel during Graphics Rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1826273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447968] Re: ImageMagick is missing JPEG2000 support (needs to be built with openjpeg)
Looks like bug #711061 is still blocking it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447968 Title: ImageMagick is missing JPEG2000 support (needs to be built with openjpeg) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1447968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825497] Re: flash player does not work in chromium
I upgraded my xubuntu 18.04 to 18.10 and then right away to 19.04 2 days ago. After this, Flash player on Firefox works, but on not Chromium and all derivates like Opera, Chrome, etc. I tried to reinstall them all, did all the workarounds that Google and Adobe say on troubleshooting help sites, tried to install and uninstall different packages through Synaptic package manager, clean caches, but no success. I installed a snap version of Chromium from command line, and that one says "plug in not supported", the others are on a permission looping without displaying content. In some time i will o a fresh install of 19.04, because maybe it can be related to installation errors or Kernel version TX! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825497 Title: flash player does not work in chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1825497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820211] Re: [MIR] python3-openid as dependency of mailman3
I reviewed python3-openid version 3.1.0-1 as checked into disco as of this writing. This shouldn't be considered a full audit but rather a quick gauge of maintainability. python3-openid is a set of python packages to support use of the OpenID decentralized identity system in your application. - No development or commit in the last 2 years. Some open issues but only one might get us worried. An user asks if python 3.7 is supported (which is the current version of python in disco). There's not much info if user saw an issue when running with python 3.7. https://github.com/necaris/python3-openid/issues/39 - No CVE history - Build-depends: - dh-python, - python3-all, - python3-setuptools - postinst and prerm added automatically - No init scripts - No dbus services - No setuid - No binaries in PATH - No sudo fragments - No udev rules - Some tests under openid/test/ - No cron jobs - No security relevant warnings: dpkg-scanpackages: warning: Packages in archive but missing from override file: dpkg-scanpackages: warning: sbuild-build-depends-core-dummy dpkg-scanpackages: warning: Packages in archive but missing from override file: dpkg-scanpackages: warning: sbuild-build-depends-core-dummy sbuild-build-depends-python3-openid-dummy dpkg-source: warning: extracting unsigned source package (python3-openid_3.1.0-1.dsc) warning: no files found matching 'NOTICE' warning: no files found matching 'CHANGELOG' warning: no files found matching 'README.md' under directory 'examples' warning: no files found matching '*.css' under directory 'doc' warning: no files found matching '*.html' under directory 'doc' dpkg-scanpackages: warning: Packages in archive but missing from override file: dpkg-scanpackages: warning: sbuild-build-depends-core-dummy sbuild-build-depends-lintian-dummy sbuild-build-depends-python3-openid-dummy - Subprocess spawned in contrib/openid-parse, it spawns "xsel -o -b" - File IO - a few file operations, look safe - Logging - logging in case of error or warning - uses logging module for logging errors and warning module for warnings - look safe - No environment variables (only in examples) - No privileged operations - Networking - SQLite3 connection - MySQL connection - PostgreSQL connection - fetches http request with pycurl - parses html - Encryption - makes use of pycurl for fetching http requests - No WebKit - No PolicyKit - No shell scripts - Coverity analysis: 1. False positive python3-openid-3.1.0/openid/fetchers.py:360 Checker: REVERSE_INULL python3-openid-3.1.0/openid/fetchers.py:356: deref: Accessing a property of "headers". python3-openid-3.1.0/openid/fetchers.py:360: check_after_deref: Null-checking "headers" suggests that it may be null, but it has already been dereferenced on all paths leading to the check. 2. Test code, so considering it low python3-openid-3.1.0/openid/test/__init__.py:170 Checker: UNREACHABLE python3-openid-3.1.0/openid/test/__init__.py:170: unreachable: This code cannot be reached: "return django.test.simple.r...". python3-openid-3.1.0/openid/test/test_association_response.py:331 Checker: FORWARD_NULL 3. Test code, so considering it low python3-openid-3.1.0/openid/test/test_association_response.py:330: 1. path: Condition "ret === None", taking true branch. python3-openid-3.1.0/openid/test/test_association_response.py:330: 2. null_check: Comparing "ret" to a null-like value implies that "ret" might be null-like. python3-openid-3.1.0/openid/test/test_association_response.py:331: 3. property_access: Accessing a property of null-like value "ret". 4. Test code, so considering it low python3-openid-3.1.0/openid/test/trustroot.py:42 Checker: FORWARD_NULL python3-openid-3.1.0/openid/test/trustroot.py:40: 1. path: Condition "tr === None", taking true branch. python3-openid-3.1.0/openid/test/trustroot.py:40: 2. null_check: Comparing "tr" to a null-like value implies that "tr" might be null-like. python3-openid-3.1.0/openid/test/trustroot.py:42: 3. property_access: Accessing a property of null-like value "tr". To sum up: 1. It would be nice if someone could verify the python issue. 2. Will we want to support a project that might have halted development or be abandoned? So before the ACK or NACK we would appreciate if someone could answer those questions. Thanks ** Bug watch added: github.com/necaris/python3-openid/issues #39 https://github.com/necaris/python3-openid/issues/39 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820211 Title: [MIR] python3-openid as dependency of mailman3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-openid/+bug/1820211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
IBus is not always launched via im-config when GNOME is involved. In Ubuntu 19.10 im-config will be disabled by default in Wayland sessions. So to achieve a consistent address of ibus daemon, it's better to change the default in ibus itself. Attached please find a debdiff with a proposed fix. Once this change is in the archive, the equivalent im-config patch can be dropped. ** Patch added: "ibus-fix-eoan_lp1580463.debdiff" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463/+attachment/5259090/+files/ibus-fix-eoan_lp1580463.debdiff ** Tags added: patch ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New ** No longer affects: ibus (Ubuntu Xenial) ** No longer affects: ibus (Ubuntu Yakkety) ** Changed in: ibus (Ubuntu) Importance: Undecided => Medium ** Changed in: ibus (Ubuntu) Status: New => In Progress ** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1580463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
** Changed in: gnome-online-accounts Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1825580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826438] Re: Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files
I've inferred that the reporting process itself possibly interferes with the misbehaviour. After submitting this report (before the terminal session was closed, however) (began through a terminal session and not the Alt-F2 launcher, using ubuntu-bug [PID of nautilus]) the reported behaviour is present again. The behaviour is identical to that recorded in the attached webm. To confirm this interference I am beginning a second report, which won't be submitted. Using the Alt-F2 method to begin the reporting process doesn't interfere with the misbehaviour; beginning the process again through a terminal session did not reproduce the interference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826438 Title: Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825425] Re: Upgrade Failure, Ubuntu 18.10 to 19.04
I got the same message from the bug description.
During the dist-upgrade, I noticed quite a few GdkPixbuf-WARNING errors
logged, e.g.:
(frontend:20874): GdkPixbuf-WARNING **: 23:46:47.169: Cannot open pixbuf
loader module file '/usr/lib/x86_64-linux-gnu/gdk-
pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
I found a way to fix my upgraded system, and it might help you as well.
See the instructions below.
---
# first, check if the following command produces any output
sudo egrep "WARNING.*pixbuf" /var/log/dist-upgrade/apt-term.log
# if the command above produces any output, then the commands below
might fix your broken 19.04 installation.
# I'm not sure if these three commands were necessary to fix the system, but
they should do no damage:
sudo apt install libgdk-pixbuf2.0-dev
sudo mv /var/lib/dpkg/info/install-info.postinst
/var/lib/dpkg/info/install-info.postinst.bad
sudo apt-get install --reinstall install-info
# and this will fix the packages that were not installed properly because of
the install-info error:
# explanation:
# select only the lines containing 'Setting up' or 'WARNING.*pixbuf',
# then select only the lines containing 'pixbuf' together with the 'Setting
up'
# line directly preceding it (with -B1), and discard other 'Setting up'
lines
# then select only those 'Setting up' lines
# in other words, select all 'Setting up' lines that resulted in that WARNING
message.
# then, select the package name (third word) from those lines with awk,
# and reinstall those packages.
for X in `sudo less /var/log/dist-upgrade/apt-term.log | egrep "Setting
up|WARNING.*pixbuf" | grep -B1 pixbuf | grep Setting | awk '{print $3}'`; do
echo REINSTALLING: $X; sudo sudo apt-get --reinstall install $X; done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825425
Title:
Upgrade Failure, Ubuntu 18.10 to 19.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1825425/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Still nothing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797665] Re: segfault when repeatedly sorting
** Changed in: trojita (Ubuntu) Assignee: Rolf Leggewie (r0lf) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797665 Title: segfault when repeatedly sorting To manage notifications about this bug go to: https://bugs.launchpad.net/trojita/+bug/1797665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807439] Re: openvpn crashes when run with fips openssl
** Changed in: openvpn (Ubuntu Xenial) Status: New => In Progress ** Changed in: openvpn (Ubuntu Xenial) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1807439 Title: openvpn crashes when run with fips openssl To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1807439/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1826438] [NEW] Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files
Public bug reported: I've recently upgraded from 18.10 to 19.04. When I right-click on any folder the context menu has extra padding on the bottom edge, below the 'properties' item. Performing the same action on files doesn't produce the problem. Strangely, while reporting this bug the noted (and recorded) behaviour doesn't occur, when minutes before reporting process began the observed behaviour was still observed following a cold boot (I witnessed and recorded the behaviour last night, and this morning). Attached is a recording of the behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 11:45:34 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'detailed_type', 'starred']" InstallationDate: Installed on 2018-12-30 (116 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Recording of extra padding in nautilus context menu of folders." https://bugs.launchpad.net/bugs/1826438/+attachment/5259083/+files/19.04%20Disco%20Dingo%20-%20Folder%20RMB%20Vertical%20Padding.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826438 Title: Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826439] [NEW] tracker-extract causes system lock-up due to 100% CPU and memory usage
Public bug reported: Immediately after upgrading from 18.10 to 19.04, my computer froze about 30-40 secs after I logged in. I finally tracked this down to the tracker-extract process. This process starts within about half a minute after logging in. When it starts, it's a matter of seconds until it consumes 100% CPU and all available system memory (I have 16 GB on an Intel 8700k @ 4.8 GHz and SSD/M.2) This only happens with my regular user. It does not occur with a newly created user (I guess due to the large amount of files within my home directory). It happens every time I log in. I'm filing this bug against the Ubuntu package because this phenomenon causes the entire system to freeze up completely. The wheels seem to fall off the wagon in such a way the system can't recover. The only alternative at this point is a hard reset or SysRQ REISUB. It is not possible to switch to a TTY (ctrl-alt-fX), and it's not possible to ssh in from another machine. SysRQ-k does not work. I've tried logging in to a TTY before logging in to the GUI, and then switching to the TTY quickly after logging in to the GUI. Surely enough - a few seconds later the TTY locks up as well. I can reproduce the problem easily, but I'm not sure how to go about debugging it - would be happy to assist. I can't let the process run for more than a few seconds at a time so bear that in mind. I tried grabbing the process in gdb, but the package seem to be stripped of debug symbols. I did a strace -p for a few seconds and the process _appears_ to be symlinking files in my homedirectory to a subdirectory within /tmp (?!?) - I can get more details here if it helps. A bonus question from me is how it's possible that a process run by a user can take down the entire system in this manner. tracker-extract and tracker-miner-fs: 2.1.6-1 tracker: 2.1.8-2 kernel: 5.0.0-13-generic (I've also tried 5.0.9) I've attached a photo(!) of top illustrating what's going on (at this point the machine has already frozen up. There appears to still be some memory available, but this is just because top never got around to report the true numbers before the machine died.) ** Affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Tags: freeze lock-up tracker-extract ** Attachment added: "2019-04-25 18.26.23.jpg" https://bugs.launchpad.net/bugs/1826439/+attachment/5259089/+files/2019-04-25%2018.26.23.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826439 Title: tracker-extract causes system lock-up due to 100% CPU and memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1826439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807439] Re: openvpn crashes when run with fips openssl
** Changed in: openvpn (Ubuntu Xenial) Status: New => In Progress ** Changed in: openvpn (Ubuntu Xenial) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807439 Title: openvpn crashes when run with fips openssl To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1807439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019
> Sponsored to Eoan, Disco, Cosmic, and Bionic. > Sponsored to Xenial. Thanks. I will wait verification request. > Does someone have an ESM contact they can poke just in case they support ibus-anthy? I have no contact. Anyway, a patch for anthy is here. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927929 However anthy package in trusty/precise is very very old. It seems that this patch couldn't be applied normally. ** Bug watch added: Debian Bug tracker #927929 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927929 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823444 Title: [SRU] The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589336] Re: version incompatibilities
I would like to thank you for your work upstream, especially since my last comment was unnecessarily harsh. I believe you and I understand the dilemma between a stable distribution and out of date code. Many attempts have been made to address this, including rolling releases, SRU policies, flatpak, appimage, snap etc. The problem remains. I understand your frustration when users complain that something is not working. I remember discussing the problem in IRC with the xpra community. I don't remember the details but I walked away with the strong feeling that they had no clue whatsoever about distros and packaging yet where attempting to package for hundreds of platforms, something that simply cannot be done correctly. I hope the relation between Debian/Ubuntu on one hand and xpra can become more productive. If your idea of that is to backport large swathes of code or even "worse" to push back entire upstream releases to a stable Ubuntu release, I am sure you will be disappointed. Once a release is finalized only targeted bugfixes can be applied (-> https://wiki.ubuntu.com/StableReleaseUpdates) I am a packager and I'm willing to do my part make Ubuntu packages in LTS releases better. Let's work together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589336 Title: version incompatibilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpra/+bug/1589336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545296] Re: xpra crashes when talking to same version on trusty
*** This bug is a duplicate of bug 1589336 *** https://bugs.launchpad.net/bugs/1589336 Antoine, before you come here accusing others of falsehood, I suggest you learn how Ubuntu releases work. It is by design that Ubuntu releases only get targetted bugfixes and not entire backports. When I looked at your "official" packages way back when they had numerous flaws from a packaging perspective but it has been a few years and I cannot recollect what they were. Given your lack of understanding of Ubuntu and Debian packaging policies and the sheer number of platforms that upstream xpra is attempting to package for it would be a miracle and an incredible amount of work if you got everything right. I am quite certain that your "official" packages do not work (or rather did not work when I tested them) on older (by now unsupported) versions of Ubuntu. In any case, you don't like people from Ubuntu and Debian releases go upstream and report bugs for code you released a few months or a year or two ago. Understandable. That is what this bug tracker is for, a Ubuntu bug tracker. At the same time, we at Ubuntu also do not like when people with "official" upstream packages come here and report problems. Neither of this is helpful. I am not sure you will understand this but it's simply the truth. If you want to run a distro and want support, you have to stick with the distro. If a user wants later packages, use the latest Ubuntu release or a snap package (I just checked and apparently there is no xpra package in snap, there might be an app image, dunno, but https://xpra.org/trac/ticket/1748 suggest to me there isn't). ** Bug watch added: xpra.org/trac/ #1748 https://xpra.org/trac/ticket/1748 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545296 Title: xpra crashes when talking to same version on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpra/+bug/1545296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545296] Re: xpra crashes when talking to same version on trusty
*** This bug is a duplicate of bug 1589336 *** https://bugs.launchpad.net/bugs/1589336 Also. please read up on what Ubuntu Universe is (where xpra resides) and what kind of support promise it gets. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545296 Title: xpra crashes when talking to same version on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpra/+bug/1545296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826150] Re: linux: 5.0.0-14.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826147 (bionic/linux-hwe-edge), bug 1826148 (bionic/linux-oem-osp1) derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 (linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 (linux-snapdragon) -- swm properties -- boot-testing-requested: true - phase: Ready for Promote to Proposed - phase-changed: Thursday, 25. April 2019 07:01 UTC + phase: Promote to Proposed + phase-changed: Thursday, 25. April 2019 17:31 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages copies requested -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826150 Title: linux: 5.0.0-14.15 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826230] Re: linux-azure: 4.15.0-1043.47 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826229 (trusty/linux-azure) -- swm properties -- boot-testing-requested: true - phase: Ready for Promote to Proposed - phase-changed: Thursday, 25. April 2019 12:01 UTC + phase: Promote to Proposed + phase-changed: Thursday, 25. April 2019 17:31 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826230 Title: linux-azure: 4.15.0-1043.47 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826150] Re: linux: 5.0.0-14.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826150 Title: linux: 5.0.0-14.15 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826430] Re: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build
>> arch/x86/Makefile:245: *** You are building kernel with non- retpoline compiler, please update your compiler.. Stop. Missed that, apologies! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826430 Title: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1826430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750786] Re: stress-ng enosys stressor triggers a kernel BUG
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750786 Title: stress-ng enosys stressor triggers a kernel BUG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822872] Re: Bionic: Luminous radosgw incompatible with libssl1.1
* debdiff: lp1822872-ceph-bionic.debdiff * MP: https://git.launchpad.net/~slashd/ubuntu/+source/ceph/commit/?id=1abb386339c34bb793f1d7caa168930217724c71 ** Patch added: "lp1822872-ceph-bionic.debdiff" https://bugs.launchpad.net/ubuntu/bionic/+source/ceph/+bug/1822872/+attachment/5259077/+files/lp1822872-ceph-bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822872 Title: Bionic: Luminous radosgw incompatible with libssl1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1822872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816669] Re: AMD Rome : Minimal support patches
I would like these patches in 18.04.1 LTS. What do I need to do? -thanks -kim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816669 Title: AMD Rome : Minimal support patches To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1816669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589336] Re: version incompatibilities
The only nonsense is your comment. Even if this was fixed ages ago (did you care to look at how long ago this report was made?) then if there are incompatibilities between the binary versions of supported Ubuntu releases then it is still a bug in Ubuntu. What you suggest should have happened (to backport patches) is generally a good approach in case that is feasible at all (and I have my doubts on this being an option). I cannot verify these incompatibilities (or others) still exist in later releases but given upstream's nonchalance attitude to breaking API between their different versions, I wouldn't be surprised if there still are some. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589336 Title: version incompatibilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpra/+bug/1589336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
With ivrs there are, at least, two problems: 1. Performance drop 2. With IOMMU disabled in bios these are useless -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826430] Re: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build
The error message is clear. ** Changed in: acpi-call (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826430 Title: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1826430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825735] Re: Display is corrupted after waking from sleep
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Another thing that I have noticed is that this problem only arises when I click suspend or close the lid. If the laptop naturally goes sleep then this problem doesn't occur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825735 Title: Display is corrupted after waking from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1825735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826150] Re: linux: 5.0.0-14.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826150 Title: linux: 5.0.0-14.15 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826230] Re: linux-azure: 4.15.0-1043.47 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826230 Title: linux-azure: 4.15.0-1043.47 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825741] Re: Multiple instances of global menu entries
Yes it still occurs. I'm currently using Ubuntu 19.04 with Unity desktop. I'll test it with my Neon & Kubuntu install when I get the chance. ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/+attachment/5259076/+files/Flameshot19Apr25-130843.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825741 Title: Multiple instances of global menu entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823351] Re: Add a "Settings..." button to the livepatch notification.
I will accept this, but could you make sure that the documentation for bionic won't have to be modified anywhere? Can you send an e-mail to the ubuntu-doc team as a heads up? Thanks! ** Changed in: update-notifier (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823351 Title: Add a "Settings..." button to the livepatch notification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1823351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820259] Re: [FFe] Add a indicator to show the status of Livepatch
I will accept this, but could you make sure that the documentation for bionic won't have to be modified anywhere? Can you send an e-mail to the ubuntu-doc team as a heads up? Thanks! ** Changed in: update-notifier (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820259 Title: [FFe] Add a indicator to show the status of Livepatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1820259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823351] Please test proposed package
Hello Andrea, or anyone else affected, Accepted update-notifier into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update- notifier/3.192.1.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823351 Title: Add a "Settings..." button to the livepatch notification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1823351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820259] Please test proposed package
Hello Andrea, or anyone else affected, Accepted update-notifier into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update- notifier/3.192.1.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820259 Title: [FFe] Add a indicator to show the status of Livepatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1820259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825928] Re: "Could not install 'linux-image-5.0.0-13-generic" during 18.10 to 19.04 upgrade
** Tags added: triggers-looping -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825928 Title: "Could not install 'linux-image-5.0.0-13-generic" during 18.10 to 19.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1825928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826398] Re: Deleting a game is not possible from program mannager.
** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826398 Title: Deleting a game is not possible from program mannager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1826398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826430] [NEW] acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build
Public bug reported: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build Linux mp 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 Codename: xenial ProblemType: Package DistroRelease: Ubuntu 16.04 Package: acpi-call-dkms 1.1.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_45_48_generic_50 lkp_Ubuntu_4_15_0_45_48_generic_49 zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSBuildLog: DKMS make.log for acpi-call-1.1.0 for kernel 4.15.0-48-generic (x86_64) Thu Apr 25 12:41:20 EDT 2019 make: Entering directory '/usr/src/linux-headers-4.15.0-48-generic' arch/x86/Makefile:245: *** You are building kernel with non-retpoline compiler, please update your compiler.. Stop. make: Leaving directory '/usr/src/linux-headers-4.15.0-48-generic' DKMSKernelVersion: 4.15.0-48-generic Date: Thu Apr 25 12:41:24 2019 InstallationDate: Installed on 2017-02-22 (791 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all PackageVersion: 1.1.0-2ubuntu1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: acpi-call Title: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: acpi-call (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826430 Title: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1826430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1825587]
@Walter: I'm sure you don't need me to confirm, but, just to confirm, your instructions to "reload" the desktop folder does work to clean up the desktop of this non-existent file . . . easy enough to do. As I posted on the bug, I did try to run Alf's series of commands . . . and w/o something from "sources" the whole series of commands "E'd" out . . . . So perhaps some further work has to be done "upstream"??? He seems to be the guy who is part of the team that has responded to this bug . . . in a sense "non-critical" . . . but on the aesthetic level . . . "critical" . . . . F > Until then, you cannot really do anything with the file since it doesn't > exist. The work around is in the description: > 1. Open pcmanfm-qt > 2. Go to the Desktop folder > 3. Refresh the folder (F5) > Now the errant file will not return, no matter whether or not you check > shortcuts on or off. It will return when you log in again, though. > > One other thing: the issue here is a timing issue, and it will be made > worse with less resources. That means that sometimes you might have the > issue and sometimes you might not. It's bizarre. Kudos to the upstream > developers for finding it so quickly. > > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
