[Bug 2071685] Re: package linux-headers-6.8.0-1005-raspi 6.8.0-1005.5 failed to install/upgrade: installed linux-headers-6.8.0-1005-raspi package post-installation script subprocess returned error exi
** Attachment added: "Screenshot from 2024-07-02 07-36-55.png" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2071685/+attachment/5794077/+files/Screenshot%20from%202024-07-02%2007-36-55.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071685 Title: package linux-headers-6.8.0-1005-raspi 6.8.0-1005.5 failed to install/upgrade: installed linux-headers-6.8.0-1005-raspi package post-installation script subprocess returned error exit status 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2071685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071685] [NEW] package linux-headers-6.8.0-1005-raspi 6.8.0-1005.5 failed to install/upgrade: installed linux-headers-6.8.0-1005-raspi package post-installation script subprocess returned error e
Public bug reported: It will not update. I get a dependency problems error ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-1005-raspi 6.8.0-1005.5 ProcVersionSignature: Ubuntu 6.8.0-1004.4-raspi 6.8.1 Uname: Linux 6.8.0-1004-raspi aarch64 ApportVersion: 2.28.1-0ubuntu3 AptOrdering: python3-netplan:arm64: Install netplan-generator:arm64: Install netplan.io:arm64: Install libnetplan1:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Tue Jul 2 07:25:45 2024 DpkgHistoryLog: Start-Date: 2024-07-02 07:25:39 Commandline: /usr/bin/unattended-upgrade Upgrade: netplan-generator:arm64 (1.0-2ubuntu1, 1.0-2ubuntu1.2), python3-netplan:arm64 (1.0-2ubuntu1, 1.0-2ubuntu1.2), netplan.io:arm64 (1.0-2ubuntu1, 1.0-2ubuntu1.2), libnetplan1:arm64 (1.0-2ubuntu1, 1.0-2ubuntu1.2) ErrorMessage: installed linux-headers-6.8.0-1005-raspi package post-installation script subprocess returned error exit status 11 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: linux-raspi Title: package linux-headers-6.8.0-1005-raspi 6.8.0-1005.5 failed to install/upgrade: installed linux-headers-6.8.0-1005-raspi package post-installation script subprocess returned error exit status 11 UpgradeStatus: Upgraded to noble on 2024-05-22 (41 days ago) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071685 Title: package linux-headers-6.8.0-1005-raspi 6.8.0-1005.5 failed to install/upgrade: installed linux-headers-6.8.0-1005-raspi package post-installation script subprocess returned error exit status 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2071685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065348] [NEW] python3-docker `from_env()` broken
Public bug reported: I have a python script that manages some docker resources. It uses the `from_env()` method to build the client. This script always runs as root. This worked in Ubuntu 22.04. However, it seems like something is mismatched in 24.04, as I now get the following error, even after a reboot (which seemed to solve this for others in the past?). It appears based on cursory googling that a library version might be out of sync. ``` Traceback (most recent call last): File "/usr/bin/oqm-captain", line 62, in ContainerUtils.ensureSharedDockerResources() File "/usr/lib/oqm/station-captain/ContainerUtils.py", line 55, in ensureSharedDockerResources client = docker.from_env() ^ File "/usr/lib/python3/dist-packages/docker/client.py", line 96, in from_env return cls( File "/usr/lib/python3/dist-packages/docker/client.py", line 45, in __init__ self.api = APIClient(*args, **kwargs) ^^ File "/usr/lib/python3/dist-packages/docker/api/client.py", line 197, in __init__ self._version = self._retrieve_server_version() ^^^ File "/usr/lib/python3/dist-packages/docker/api/client.py", line 221, in _retrieve_server_version raise DockerException( docker.errors.DockerException: Error while fetching server API version: HTTPConnection.request() got an unexpected keyword argument 'chunked' ``` This is on a fresh 24.04 install. Willing to help diagnose, but to replicate: 1. `apt install docker.io python3-docker` 2. `python3` 3. `import docker` 4. `docker.from_env()` ** Affects: python-docker (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/2065348 Title: python3-docker `from_env()` broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2065348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059308] [NEW] please update the bmake package to fix critical bugs
Public bug reported: The BMake package seems stuck on an ancient version (20200710). There have been numerous critical bugs fixed in bmake since that release, and indeed there have been many new upstream releases since then too. Please update to the latest upstream release, thanks! ** Affects: bmake (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/2059308 Title: please update the bmake package to fix critical bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bmake/+bug/2059308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970684] [NEW] SSL error when running weather-util in Jammy
Public bug reported:
After updating my Ubuntu Server install to Jammy, weather doesn't
execute with the following error:
greg@host ~ % weather -a -q KJFK
weather error: failed to retrieve
https://tgftp.nws.noaa.gov/data/observations/metar/decoded/KJFK.TXT
Traceback (most recent call last):
File "/usr/lib/python3.10/urllib/request.py", line 1348, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
File "/usr/lib/python3.10/http/client.py", line 1282, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1328, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1277, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1037, in _send_output
self.send(msg)
File "/usr/lib/python3.10/http/client.py", line 975, in send
self.connect()
File "/usr/lib/python3.10/http/client.py", line 1454, in connect
self.sock = self._context.wrap_socket(self.sock,
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy
renegotiation disabled (_ssl.c:997)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/greg/weather-2.4.2/./weather", line 72, in
partial = weather.get_metar(
File "/home/greg/weather-2.4.2/weather.py", line 270, in get_metar
metar = get_uri(
File "/home/greg/weather-2.4.2/weather.py", line 233, in get_uri
data = urlopen(uri).read().decode("utf-8")
File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.10/urllib/request.py", line 519, in open
response = self._open(req, data)
File "/usr/lib/python3.10/urllib/request.py", line 536, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain
result = func(*args)
File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open
return self.do_open(http.client.HTTPSConnection, req,
File "/usr/lib/python3.10/urllib/request.py", line 1351, in do_open
raise URLError(err)
urllib.error.URLError:
Trying to download the newest upstream release still has the issue, so I
think it may have something to do with changes to python or openssl in
jammy.
lsb_release:
Description:Ubuntu 22.04 LTS
Release:22.04
apt-cache policy weather-util:
weather-util:
Installed: 2.4.1-1
Candidate: 2.4.1-1
Version table:
*** 2.4.1-1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu jammy/universe i386 Packages
100 /var/lib/dpkg/status
== Dependencies =
adduser 3.118ubuntu5
apt 2.4.5
apt-utils 2.4.5
ca-certificates 20211016
debconf 1.5.79ubuntu1
debconf-i18n 1.5.79ubuntu1
dpkg 1.21.1ubuntu2
gcc-12-base 12-20220319-1ubuntu1
gpgv 2.2.27-3ubuntu2
init-system-helpers 1.62
krb5-locales 1.19.2-2
libacl1 2.3.1-1
libapt-pkg6.0 2.4.5
libaudit-common 1:3.0.7-1build1
libaudit1 1:3.0.7-1build1
libbz2-1.0 1.0.8-5build1
libc6 2.35-0ubuntu3
libcap-ng0 0.7.9-2.2build3
libcap2 1:2.44-1build3
libcom-err2 1.46.5-2ubuntu1
libcrypt1 1:4.4.27-1
libdb5.3 5.3.28+dfsg1-0.8ubuntu3
libexpat1 2.4.7-1
libffi8 3.4.2-4
libgcc-s1 12-20220319-1ubuntu1
libgcrypt20 1.9.4-3ubuntu3
libgmp10 2:6.2.1+dfsg-3ubuntu1
libgnutls30 3.7.3-4ubuntu1
libgpg-error0 1.43-3
libgpm2 1.20.7-10build1
libgssapi-krb5-2 1.19.2-2
libhogweed6 3.7.3-1build2
libidn2-0 2.3.2-2build1
libk5crypto3 1.19.2-2
libkeyutils1 1.6.1-2ubuntu3
libkrb5-3 1.19.2-2
libkrb5support0 1.19.2-2
liblocale-gettext-perl 1.07-4build3
liblz4-1 1.9.3-2build2
liblzma5 5.2.5-2ubuntu1
libmpdec3 2.5.1-2build2
libncursesw6 6.3-2
libnettle8 3.7.3-1build2
libnsl2 1.3.0-2build2
libnss-nis 3.1-0ubuntu6
libnss-nisplus 1.3-0ubuntu6
libp11-kit0 0.24.0-6build1
libpam-modules 1.4.0-11ubuntu2
libpam-modules-bin 1.4.0-11ubuntu2
libpam0g 1.4.0-11ubuntu2
libpcre2-8-0 10.39-3build1
libpython3-stdlib 3.10.4-0ubuntu2
libpython3.10-minimal 3.10.4-3
libpython3.10-stdlib 3.10.4-3
libreadline8 8.1.2-1
libseccomp2 2.5.3-2ubuntu2
libselinux1 3.3-1build2
libsemanage-common 3.3-1build2
libsemanage2 3.3-1build2
libsepol2 3.3-1build1
libsmartcols1 2.37.2-4ubuntu3
libsqlite3-0 3.37.2-2
libssl3 3.0.2-0ubuntu1
libstdc++6 12-20220319-1ubun
[Bug 1968631] Re: regression in jammy kernel 5.15 for module ath9k
Experiencing the same issue and also seeing the same dump: [ 104.357253] [ 104.357264] UBSAN: invalid-load in /build/linux-9H675w/linux-5.15.0/net/mac80211/status.c:1164:21 [ 104.357270] load of value 255 is not a valid value for type '_Bool' [ 104.357274] CPU: 1 PID: 1583 Comm: dbus-daemon Tainted: G OE 5.15.0-25-generic #25-Ubuntu [ 104.357279] Hardware name: ASUSTeK COMPUTER INC. X553MA/X553MA, BIOS X553MA.211 04/10/2015 [ 104.357281] Call Trace: [ 104.357285] [ 104.357289] show_stack+0x52/0x58 [ 104.357298] dump_stack_lvl+0x4a/0x5f [ 104.357312] dump_stack+0x10/0x12 [ 104.357315] ubsan_epilogue+0x9/0x45 [ 104.357319] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [ 104.357324] ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211] [ 104.357420] ieee80211_tx_status+0x72/0xa0 [mac80211] [ 104.357484] ath_txq_unlock_complete+0x12d/0x160 [ath9k] [ 104.357498] ath_tx_edma_tasklet+0xef/0x4c0 [ath9k] [ 104.357510] ? del_timer_sync+0x6c/0xb0 [ 104.357516] ath9k_tasklet+0x14e/0x290 [ath9k] [ 104.357528] tasklet_action_common.constprop.0+0xc0/0xf0 [ 104.357534] tasklet_action+0x22/0x30 [ 104.357538] __do_softirq+0xd9/0x2e3 [ 104.357544] irq_exit_rcu+0x8c/0xb0 [ 104.357548] common_interrupt+0x4a/0xa0 [ 104.357554] ? asm_common_interrupt+0x8/0x40 [ 104.357558] asm_common_interrupt+0x1e/0x40 [ 104.357562] RIP: 0033:0x55a15a659cdd [ 104.357566] Code: c0 75 23 e9 32 fe ff ff 0f 1f 44 00 00 e8 db e6 ff ff 41 89 c0 48 89 e8 45 85 c0 75 2a 48 85 ed 0f 84 14 fe ff ff 4c 8b 60 10 <48> 8b 68 08 49 8b 3c 24 48 3b 6b 18 75 d5 e8 b0 e6 ff ff 85 c0 0f [ 104.357570] RSP: 002b:7fffd4987cf0 EFLAGS: 0202 [ 104.357575] RAX: 7f4bd3f62d20 RBX: 55a15ac19e90 RCX: [ 104.357577] RDX: 00056ee0 RSI: 0068 RDI: 55a15ad6b990 [ 104.357580] RBP: 7f4bd3f62d20 R08: R09: [ 104.357582] R10: 7fffd49b9080 R11: 7fffd49b9090 R12: 55a15ad6cb70 [ 104.357584] R13: R14: R15: 7fffd4987e30 [ 104.357590] [ 104.357592] [ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968631 Title: regression in jammy kernel 5.15 for module ath9k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967799] Re: firefox, chromium and other snap apps can't print
$ dpkg -l | grep xdg-desktop-portal ii xdg-desktop-portal 1.14.1-2 amd64desktop integration portal for Flatpak and Snap ii xdg-desktop-portal-gnome 42.0.1-1 amd64GNOME portal backend for xdg-desktop-portal ii xdg-desktop-portal-gtk 1.14.0-1build1 amd64GTK+/GNOME portal backend for xdg-desktop-portal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967799 Title: firefox, chromium and other snap apps can't print To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1967799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967799] Re: firefox, chromium and other snap apps can't print
journalctl -b 0 ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1967799/+attachment/5577038/+files/log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967799 Title: firefox, chromium and other snap apps can't print To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1967799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967799] [NEW] firefox, chromium and other snap apps can't print
Public bug reported: Snap packages aren't seeing any cups printers (tried firefox and chromium snap). Native packages see printers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.2+22.04.1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 14:49:58 2022 InstallationDate: Installed on 2022-03-14 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap.Changes: ID Status Spawn Ready Summary 19 Done2022-04-04T12:25:24-04:00 2022-04-04T12:25:34-04:00 Auto-refresh snap "snapd" 20 Done2022-04-04T12:27:47-04:00 2022-04-04T12:27:47-04:00 Connect firefox:cups-control to snapd:cups-control SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967799 Title: firefox, chromium and other snap apps can't print To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1967799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927948] Re: Windows switch monitor after resuming from sleep
This is happening to me too. Fresh install of Debian 11, primary DP landscape, secondary HDMI portrait. Two effects: 1. A window on the right of the primary screen moves to the left of the primary screen. Another window on the left of the primary screen does not move. The moving window also resizes, although this contains Terminal and may be resizing to default row/column settings. 2. A maximised window on the secondary screen is moved down so there is a one-line gap at the top, despite still being maximised. Un-max/max removes the gap. It seems to happen when screen is blanked. I have disabled screen locking so don't know if it happens when screen locked too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927948 Title: Windows switch monitor after resuming from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1927948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868105] Re: No Sound, dummy output in settings
This same bug affects me as well. It might of happened the last time I updated but hard to say (I didn't notice right away) I have several sound card/devices; NVIDIA 1080 graphics card, intel, and a sound blaster, all of which are now gone. Running Ubuntu 20.04.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868105 Title: No Sound, dummy output in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1868105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1934529] Re: Postfix package install always fails
Thank you for your response. Note that I am a total novice. However, I did manage to find a log of a recent Software Updater that reported "Package operation failed" This always happens. Attached is the most recent log file which shows that "postfix" returned an error code. What more info do you need about this? How do I fix it? Thank you, Greg On 7/12/21 5:26 AM, Lucas Kanashiro wrote: > Thank you for taking the time to file a bug report. > > I tried to install and upgrade postfix in a container running Ubuntu > 21.04 and I could not reproduce the error you mentioned. Could you > please share the logs containing the error when you upgrade the package? > Also the postfix config file in case you have made any customization in > it. > > Since there is not enough information in your report to begin triage or to > differentiate between a local configuration problem and a bug in Ubuntu, I > am marking this bug as "Incomplete". We would be grateful if you would: > provide a more complete description of the problem, explain why you > believe this is a bug in Ubuntu rather than a problem specific to your > system, and then change the bug status back to "New". > > For local configuration issues, you can find assistance here: > http://www.ubuntu.com/support/community > > ** Changed in: postfix (Ubuntu) > Status: New => Incomplete > ** Attachment added: "history.log" https://bugs.launchpad.net/bugs/1934529/+attachment/5511603/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934529 Title: Postfix package install always fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1934529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934529] [NEW] Postfix package install always fails
Public bug reported: I have Ubuntu 21.04 on a Dell Precision T1500. When Ubuntu install updates Postfix package always fails to install. Otherwise, I have no problem. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934529 Title: Postfix package install always fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865566] Re: Large Page support disabled on Raspberry Pi kernels
I'm also hitting this. Hardware is raspberry pi 4, 8GB. Running latest nightly. root@ubuntu:~# hugeadm --explain hugeadm:ERROR: kernel does not support huge pages root@ubuntu:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Codename: hirsute root@ubuntu:~# grep -i huge /boot/config-5.11.0-1004-raspi CONFIG_SYS_SUPPORTS_HUGETLBFS=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_HUGE_VMAP=y CONFIG_TRANSPARENT_HUGEPAGE=y # CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is not set CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y # CONFIG_HUGETLBFS is not set -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865566 Title: Large Page support disabled on Raspberry Pi kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1865566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915767] [NEW] package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess was killed by signal (Aborted)
Public bug reported: I was performing a release upgrade from 18.04 to 20.04 and if failed about 90% of the way due to a inconsistency in the apt database. It did upgrade though. my sytem now shows: lsb_release output... Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal If you have more questions or suggestions ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lxd 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 15 03:50:56 2021 ErrorMessage: new lxd package pre-installation script subprocess was killed by signal (Aborted) InstallationDate: Installed on 2021-02-15 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: lxd Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess was killed by signal (Aborted) UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915767 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess was killed by signal (Aborted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1915767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913216] Re: unbound DNS service crashing/not starting
This is no longer an issue for me, although I am not sure what caused the failure in the first place the required 2 complete reinstalls. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913216 Title: unbound DNS service crashing/not starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1913216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913216] Re: unbound DNS service crashing/not starting
I'm probably going to close this bug report tomorrow. Giving this 24 hours but after reinstalling and re-configuring both Pi-Hole and Unbound, everything is working. If it fails again I will provide updates including the output of jornalctl -xe, otherwise I will just close/cancel my bug report. Thank you. Here is the link to the entire discussion I had in the Pi-Hole forum: https://discourse.pi-hole.net/t/ftl-failed-to-start-since-last-update/43578/15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913216 Title: unbound DNS service crashing/not starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1913216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913216] [NEW] unbound DNS service crashing/not starting
Public bug reported: When I try to install unbound on a clean install of Ubuntu Server 20.4.1, I get an error: ==Screen Output== Job for unbound.service failed because the control process exited with error code. See "systemctl status unbound.service" and "journalctl -xe" for details. Job for unbound.service failed because the control process exited with error code. See "systemctl status unbound.service" and "journalctl -xe" for details. invoke-rc.d: initscript unbound, action "start" failed. ● unbound.service - Unbound DNS server Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Mon 2021-01-25 20:37:44 UTC; 7ms ago Docs: man:unbound(8) Process: 2369 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS) Process: 2372 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS) Process: 2376 ExecStart=/usr/sbin/unbound -d $DAEMON_OPTS (code=exited, status=1/FAILURE) Main PID: 2376 (code=exited, status=1/FAILURE) Processing triggers for systemd (245.4-4ubuntu3.4) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for libc-bin (2.31-0ubuntu9.1) ... ==End Screen Output== The DNS service will not work and so Pi-Hole and its FTL service also fail. This seems to be after the most recent Ubuntu updates, because I was having no problems until this week, and the Ubuntu Focal Unbound has not been updated since May 2020. ** Affects: unbound (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/1913216 Title: unbound DNS service crashing/not starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1913216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908284] Re: [snap] chromium headless crashes at startup on non-desktop system
I can confirm this workaround works. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908284 Title: [snap] chromium headless crashes at startup on non-desktop system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792783] Re: Cannot update Identity Roles in Rocky
Perhaps I am dense, but this problem seems to affect me as well. I am using a brand-spanking new openstack-dashboard install out of JAAS.ai, and I cannot add roles using the admin user account provisioned during "juju deploy". I only following instructions for LDAP authentication for a new charmed Kubernetes install, and cannot make forward progress, because the documented setup requires that I create three roles that do not exist in an out-of-box deployment: https://ubuntu.com/kubernetes/docs/ldap If a neither users in the built-in "Admin" and "member" roles cannot create new roles, then who can? This charm seems pretty well broken as a result of this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792783 Title: Cannot update Identity Roles in Rocky To manage notifications about this bug go to: https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1792783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 565971] Re: I cannot mount my ipod shuffle. It shows up with the system>administration>disk utility; but it doesn't have any mountable partitions. (It actually does)
just stumbled on this bug while trying to revive an ancient ipod shuffle 1st gen. So... confirmed that this is still an issue on Ubuntu 20.04.1 LTS. (removing libgpod-common is the workaround) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/565971 Title: I cannot mount my ipod shuffle. It shows up with the system>administration>disk utility; but it doesn't have any mountable partitions. (It actually does) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpod/+bug/565971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904601] Re: lftp 4.8.1 crashes upon exit
I can confirm that downgrading to 4.8.1-1ubuntu0.1 allows the test case to run without triggering a core dump. Thank you @snowyeti! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904601 Title: lftp 4.8.1 crashes upon exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lftp/+bug/1904601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904601] Re: lftp 4.8.1 crashes upon exit
This command will trigger the segfault. This is predicated on the having an SSH-enabled account at . lftp sftp://user@host -e "ls; bye" The output should be an ls listing of the user's home directory and a clean exit / return to the shell prompt. But instead of clean exit the output will be similar to this: lftp: RateLimit.cc:30: void RateLimit::AddXfer(int): Assertion `xfer_number>=0' failed. Aborted (core dumped) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904601 Title: lftp 4.8.1 crashes upon exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lftp/+bug/1904601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904601] [NEW] lftp 4.8.1 crashes upon exit
Public bug reported: Release: Ubuntu 18.04.5 LTS Package: 4.8.1-1ubuntu0.2 lftp 4.8.1 and 4.8.2 have a known bug where it will crash upon exit. This bug was fixed on Oct 3, 2017 and is included in lftp 4.8.3. This is the error reported on the console: RateLimit.cc:30: void RateLimit::AddXfer(int): Assertion `xfer_number>=0' failed. Here is the commit that addresses the issue: https://github.com/lavv17/lftp/commit/8ac64e9d664270d67fa4b8f75186af0884c030f0 Currently lftp is not usable in scripts due to the segfault / core dump. ** Affects: lftp (Ubuntu) Importance: Undecided Status: New ** Description changed: Release: Ubuntu 18.04.5 LTS Package: 4.8.1-1ubuntu0.2 lftp 4.8.1 has a known bug where it will crash upon exit. This bug was fixed on Oct 3, 2017 but is not included in lftp 4.8.1. + This is the error reported on the console: + RateLimit.cc:30: void RateLimit::AddXfer(int): Assertion `xfer_number>=0' failed. + Here is the commit that addresses the issue: https://github.com/lavv17/lftp/commit/8ac64e9d664270d67fa4b8f75186af0884c030f0 Currently lftp is not usable in scripts due to the segfault / core dump. ** Description changed: Release: Ubuntu 18.04.5 LTS Package: 4.8.1-1ubuntu0.2 lftp 4.8.1 has a known bug where it will crash upon exit. This bug was - fixed on Oct 3, 2017 but is not included in lftp 4.8.1. + fixed on Oct 3, 2017 and is included in lftp 4.8.3. This is the error reported on the console: RateLimit.cc:30: void RateLimit::AddXfer(int): Assertion `xfer_number>=0' failed. Here is the commit that addresses the issue: https://github.com/lavv17/lftp/commit/8ac64e9d664270d67fa4b8f75186af0884c030f0 Currently lftp is not usable in scripts due to the segfault / core dump. ** Description changed: Release: Ubuntu 18.04.5 LTS Package: 4.8.1-1ubuntu0.2 - lftp 4.8.1 has a known bug where it will crash upon exit. This bug was - fixed on Oct 3, 2017 and is included in lftp 4.8.3. + lftp 4.8.1 and 4.8.2 have a known bug where it will crash upon exit. + This bug was fixed on Oct 3, 2017 and is included in lftp 4.8.3. This is the error reported on the console: RateLimit.cc:30: void RateLimit::AddXfer(int): Assertion `xfer_number>=0' failed. Here is the commit that addresses the issue: https://github.com/lavv17/lftp/commit/8ac64e9d664270d67fa4b8f75186af0884c030f0 Currently lftp is not usable in scripts due to the segfault / core dump. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904601 Title: lftp 4.8.1 crashes upon exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lftp/+bug/1904601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901411] [NEW] package mysql-server-5.7 5.7.31-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Trying to do an upgrade of my 14 system using sudo apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-server-5.7 5.7.31-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 3.13.0-182.233-generic 3.13.11-ckt39 Uname: Linux 3.13.0-182-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 Date: Sun Oct 25 10:13:26 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (2381 days ago) InstallationMedia: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLConf.etc.mysql.conf.d.mysqld_slow_log.cnf: [mysqld] log_slow_queries = /var/log/mysql/mysql-slow.log long_query_time = 0.1 #log-queries-not-using-indexes MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['debian-5.5.flag', 'ib_logfile1', 'ib_logfile0', 'performance_schema', 'ibdata1', 'mysql_upgrade_info', 'mysql', 'hporg@002dwp@002dfy8TDPyv'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-182-generic root=UUID=050e1e34-39e6-4072-a03e-ae0bf90ba13a ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.31-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2020-10-25 (0 days ago) ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-package uec-images xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901411 Title: package mysql-server-5.7 5.7.31-0ubuntu0.16.04.1 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/mysql-5.7/+bug/1901411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901380] Re: Installation of Ubuntu 20.10 first time while testing desktop
The issue was due to an EFI partition not being on the hard drive. I was able to correct by creating a FAT32 partition (flag boot) and then selecting as an efi partition during the install process. This fix was spotted with a similar issue for Ubuntu 18.04 after a google search. Sorry but I cannot remember the link as I found it in the Ubuntu test disk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901380 Title: Installation of Ubuntu 20.10 first time while testing desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1901380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901380] [NEW] Installation of Ubuntu 20.10 first time while testing desktop
Public bug reported: No further details known ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 Date: Sun Oct 25 17:17:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base linux-base linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901380 Title: Installation of Ubuntu 20.10 first time while testing desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1901380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
I was using nautilus to connect with ssh to a local server when it crashed for me. As soon as I hit enter after putting in my credentials the screen flickered a few times. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
I also can confirm that this issue persists in Ubuntu 20.04 (focal). It's pretty irritating... it's bad enough that all of these Electron- based apps and chromium-based browsers are chewing up ~400-500Mb each. I don't need a silly software management UI doing it, too! I recognize that gnome-software may not be a default-installed package on Ubuntu 20.04, but it still is widely used (I have several Flatpaks I need for work, and gnome-software offers the ability to easily install and coordinate their updates). Can't some developers at Red Hat and Canonical put their heads together for a few minutes and get this corrected, please? I also will second Meluco's comment. We should not all have to buy new 32Gb laptops just to run a simple productivity workstation. This really needs to get corrected. I am seeing reports of memory leaks in gnome-software going back as far as Ubuntu 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616332 Title: gnome-software using hundreds of MB of memory when not in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897752] [NEW] Installer crash says to file a bug report in terminal - no means to invoke a terminal
Public bug reported: Sorry - this is a noob comment, but in the spirit of making things easier for us noobs, please accept that this issue is preventing me from installing! Installer crashed and said "...the installer has crashed. Please file a new bug report using the command...in a terminal." As a new(ish) user I could not see any way to invoke a terminal at that point. The dialogue box has a close button, but maybe there should also be a "Open Terminal" button?? (Please remember at this point in the install the toolbar/menu button are not available, and any keyboard shortcuts that were suggested on help forums did not work). ** Affects: glibc (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/1897752 Title: Installer crash says to file a bug report in terminal - no means to invoke a terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1897752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
@Syver Stensholt, I don't think it's possible to screenshot it. The screenshot does not capture the cursor even though it's there when the screenshot is taken. When I notice the 2nd fixed mouse cursor icon, if I reboot the machine, it goes away. But then at some point the 2nd fixed mouse cursor will appear again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 confirmed that I can't switch between the two modes HSP/HFP and A2DP when using Sony CH-500 bluetooth headset. Initially it was stuck at HSP/HFP but after some messing with /etc/bluetooth/main.conf I got it to switch to A2DP but now it wont switch back and the mic never shows up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336794] Re: 9pfs does not honor open file handles on unlinked files
For the records. QEMU patches: https://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg07586.html Linux patches: https://sourceforge.net/p/v9fs/mailman/message/35175775/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336794 Title: 9pfs does not honor open file handles on unlinked files To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1336794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336794] Re: 9pfs does not honor open file handles on unlinked files
I haven't worked on this topic in years. ** Changed in: qemu Status: In Progress => Confirmed ** Changed in: qemu Assignee: Greg Kurz (gkurz) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336794 Title: 9pfs does not honor open file handles on unlinked files To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1336794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880228] [NEW] rtl-sdr crashes on aarm64 (RPi4 and RockPro64) on Ubuntu 20.04
*** This bug is a duplicate of bug 1876624 *** https://bugs.launchpad.net/bugs/1876624 Public bug reported: I think this is the same as Bug #1876624. If I run rtl_test: Reading samples in async mode... Allocating 15 zero-copy buffers Killed is the output. Ubuntu 20.04 ** Affects: rtl-sdr (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1876624 rtl apps crash "allocating zero-copy buffers", Pi 4, Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880228 Title: rtl-sdr crashes on aarm64 (RPi4 and RockPro64) on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl-sdr/+bug/1880228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] [NEW] Kernel panic booting after 18.04 to 20.04 upgrade
Public bug reported: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. ** Affects: libseccomp (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Attachment added: "Screen photograph of kernel panic during boot" https://bugs.launchpad.net/bugs/1876486/+attachment/5365144/+files/20200501_233503.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Same for me. Ubuntu 20.04 nvidia-driver-390 (also tried 340.108), GeForce GT-750M I noticed some weird behavior with the xrandr, note the "mm" size is different for the same scale setting at different times. greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 2x2 screen 0: 6400x3600 846x475 mm 192.10dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.25x1.25 crtc 0: disable screen 0: 4000x2250 527x296 mm 192.51dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.5x1.5 screen 0: 4800x2700 1587x892 mm 76.81dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.25x1.25 crtc 0: disable screen 0: 4000x2250 1321x743 mm 76.88dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.5x1.5 screen 0: 4800x2700 1587x892 mm 76.81dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.75x1.75 screen 0: 5600x3150 1850x1040 mm 76.88dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 2x2 screen 0: 6400x3600 2113x1188 mm 76.93dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1x1 crtc 0: disable screen 0: 3200x1800 1056x594 mm 76.97dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.75x1.75 screen 0: 5600x3150 1480x832 mm 96.05dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.75x1.75 screen 0: 5600x3150 1480x832 mm 96.05dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1x1 crtc 0: disable screen 0: 3200x1800 845x475 mm 96.17dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.25x1.25 screen 0: 4000x2250 528x297 mm 192.10dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1x1 crtc 0: disable screen 0: 3200x1800 422x237 mm 192.42dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.75x1.75 screen 0: 5600x3150 740x416 mm 192.10dpi crtc 0:3200x1800 59.98 +0+0 "eDP-1-1" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857383] Re: Fractional scaling does not work anymore
I also see the fractional increments and can select any, but only the 100 & 200 work correctly, the others change something but it doesn't scale properly. Probably expected, I tried record the transitions using screen recorder, it worked changing 200% to 100%, then when I select 125 the video gets scrambled, and seems to be getting worse as I switch to another until I get to 200. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857383 Title: Fractional scaling does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857383] Re: Fractional scaling does not work anymore
Same issue, downloaded & installed iso, fractional scaling was working, it stopped working after an update, I also installed drivers for the Wifi - Broadcom BCM4352 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857383 Title: Fractional scaling does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871684] Re: gnome-shell crashed - endlessly in a loop from lock screen - with SIGSEGV in st_theme_node_get_icon_style()
*** This bug is a duplicate of bug 1868660 *** https://bugs.launchpad.net/bugs/1868660 I ran into this on the 10th, had to open a vty and run `gsettings set org.gnome.desktop.lockdown disable-lock-screen true` to get back in. after installing updates that evening, and setting the previous setting to `false`, and restarting (to apply updates to gnome-shell (3.36.1-4ubuntu1)) this was no longer an issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871684 Title: gnome-shell crashed - endlessly in a loop from lock screen - with SIGSEGV in st_theme_node_get_icon_style() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850597] [NEW] Firefox 71.0~b5+build1-0ubuntu0.16.04.1 crashes at startup
Public bug reported: Sorry if this duplicates #1850529 but I wanted to be sure that there was an AppPort upload ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 71.0~b5+build1-0ubuntu0.16.04.1 [origin: LP-PPA-mozillateam-firefox-next] ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: greg 13968 F...m pulseaudio /dev/snd/controlC0: greg 13968 F pulseaudio BuildID: 20191028161640 Channel: beta CurrentDesktop: Unity Date: Wed Oct 30 16:39:06 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-05-06 (2002 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MostRecentCrashID: bp-374760d9-4963-467e-9ff4-761800191030 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 Profile1PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 Profile2PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=70.0/20191021052918 (Out of date) Profile0 (Default) - LastVersion=71.0/20191028161640 Profile2 - LastVersion=71.0/20191028161640 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to xenial on 2018-10-19 (375 days ago) dmi.bios.date: 09/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: Z370M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd09/18/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ370MD3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370MD3H-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370M D3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug beta-channel 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/1850597 Title: Firefox 71.0~b5+build1-0ubuntu0.16.04.1 crashes at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Apologies if I've incorrectly duplicated here - I've logged a separate bug to ensure there is a full AppPort bundle as suggested in the firefox bug wiki page. https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850597 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850529 Title: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Can confirm same issue here - also 16.04 x86_64 - also tried creating a new (clean) profile, but that does not resolve the issue. I've reverted off the beta/next ppa back to "70.0+build2-0ubuntu0.16.04.1", but can't use my old profile as reverting profiles isn't allowed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850529 Title: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850084] [NEW] fails to install 19.10 zfs
Public bug reported: disk read/write error ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 27 18:57:35 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.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 eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850084 Title: fails to install 19.10 zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1850084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846284] Re: UDEV Symlink Not Created In 19.10
However, it looks like debian is asking systemd to do this. Hmmm. I'm talking to a Plex guy in another forum. I'll follow up here, or he will. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846284 Title: UDEV Symlink Not Created In 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1846284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846284] Re: UDEV Symlink Not Created In 19.10
Plex for one -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846284 Title: UDEV Symlink Not Created In 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1846284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846284] Re: UDEV Symlink Not Created In 19.10
Sorry, the bug report tool pumped this under the upgrader. Feel welcome to move. Related to 19.04 > 19.10 upgrade. Removing that symlink breaks a few applications. The odd part is the symlink exists in 19.04. 19.10 goes out of it's way to remove it :'( ** No longer affects: ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846284 Title: UDEV Symlink Not Created In 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1846284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846284] [NEW] UDEV Symlink Not Created In 19.10
Public bug reported: Upon upgrade from 19.04 to 19.10, the symlink for udev is broken. /sbin/udevadm should link to /bin/udev It doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashDB: ubuntu Date: Tue Oct 1 19:53:28 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to eoan on 2019-09-29 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: udev (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade eoan uec-images ** Also affects: udev (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/1846284 Title: UDEV Symlink Not Created In 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1846284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507247] Re: avahi-daemon dies after about a minute
I actually have a fix for this. The reason why the daemon is dying is because dbus is disabled in avahi and the configuration expects DBUS to be enabled for status checking. Make sure you have "enable-dbus=yes" in avahi-daemon.conf :) ** Changed in: avahi (Ubuntu) Status: Confirmed => 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/1507247 Title: avahi-daemon dies after about a minute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1507247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811641] Re: Wodim permissions error: /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
I was affected by this, the sticky bit workaround resolved my issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811641 Title: Wodim permissions error: /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1811641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841354] Re: Show a "Confirm" dialog window when deleting files
But in Windows there's an easy option to change that. You should let users decide what's best for them, instead of making your own rules. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841354 Title: Show a "Confirm" dialog window when deleting files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1841354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841354] Re: Show a "Confirm" dialog window when deleting files
I don't want to switch file managers. This should be available in the default installation. So users can just open some "Settings" page, and check "show confirmation dialog when deleting files". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841354 Title: Show a "Confirm" dialog window when deleting files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1841354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812880] Re: Executables on desktop won't launch on double-click
But this is a serious problem, and this bug report has status "Won't Fix" I think it's common practice to put application shortcuts on the desktop. It used to work fine in previous Ubuntu releases. I have a bunch of applications that I use frequently. It's very convenient to have their shortcuts on the desktop. How can a serious problem like this be ignored? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812880 Title: Executables on desktop won't launch on double-click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1812880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841355] Re: Place Applications and Shortcuts on the desktop
*** This bug is a duplicate of bug 1812880 *** https://bugs.launchpad.net/bugs/1812880 But this is a serious problem, and that bug report has status "Won't Fix" I think it's common practice to put application shortcuts on the desktop. It used to work fine in previous releases. I have a bunch of applications that I use frequently. It's very convenient to have their shortcuts on the desktop. How can a serious problem like this be ignored? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841355 Title: Place Applications and Shortcuts on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1841355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841354] Re: Show a "Confirm" dialog window when deleting files
Are you sure you want to delete ...? Yes/Cancel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841354 Title: Show a "Confirm" dialog window when deleting files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1841354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841354] Re: Show a "Confirm" dialog window when deleting files
Sorry but what more information do you need? I think this is all the information you need. Deletion is instant, but I want confirmation window, like on Windows OS. Ubuntu 19.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841354 Title: Show a "Confirm" dialog window when deleting files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1841354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841354] [NEW] Show a "Confirm" dialog window when deleting files
Public bug reported: Currently files are deleted instantly when pressing "Del" key. I need a confirmation dialog window. "yes/no" ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841354 Title: Show a "Confirm" dialog window when deleting files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1841354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841355] [NEW] Place Applications and Shortcuts on the desktop
Public bug reported: Since updating Ubuntu to latest version, I can no longer place Applications and App Shortcuts on the desktop to run them by double- clicking!! What?! ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841355 Title: Place Applications and Shortcuts on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1841355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841352] [NEW] Graphics Driver Bug - Linux GLSL can't handle precisions
Public bug reported: https://forums.intel.com/s/question/0D50P4QfQyQSAV/graphics-driver- bug-linux-glsl-cant-handle-precisions?language=en_US ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841352 Title: Graphics Driver Bug - Linux GLSL can't handle precisions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1841352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841353] [NEW] Graphics Driver Bug - Linux Updating UBO's
Public bug reported: https://forums.intel.com/s/question/0D50P4QebSqSAJ/graphics-driver- bug-linux-updating-ubos ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841353 Title: Graphics Driver Bug - Linux Updating UBO's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1841353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840962] [NEW] No touchpad detected Lenovo P50
Public bug reported: My Lenovo P50 has a touchpad and a pointing device. Neither are detected by Ubuntu 19.04. Both work perfectly when I boot this machine into Windows 10. Output from this command is attached: cat /proc/bus/input/devices > ~/devices Thanks, Greg ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: greg 2730 F pulseaudio /dev/snd/controlC0: greg 2730 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Aug 21 11:19:50 2019 InstallationDate: Installed on 2018-10-09 (316 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20ENCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=5b44139e-ca55-4f98-85dc-cc26fb1dbfe4 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-05-01 (112 days ago) dmi.bios.date: 06/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET85W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET85W(1.58):bd06/26/2019:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20ENCTO1WW dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1840962/+attachment/5283797/+files/devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840962 Title: No touchpad detected Lenovo P50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830613] [NEW] Provide UI and API for customizing date/time formats
Public bug reported:
Linux should be able to support customized date/time formats like
Microsoft Windows can. It is a hair-pulling experience to try to get ISO
8601 date/time format implemented throughout a Linux desktop install.
As mentioned in this Mozilla bug report at Comment 20
(https://bugzilla.mozilla.org/show_bug.cgi?id=1426907), developer Zibi
Braniecki says,
"Yes, we do more on Windows, than we do on Linux. The reason being that Windows
provides UI and API for us to read customized date/time patterns for styles
short/medium/long.
Which means that we can fetch the *pattern* from the OS, and *localize*
it using our own CLDR resources. This means, that if on Windows you'll
tell us you want a date "{day} {month} {year}", and in Gecko you'll
specify you want Polish language we'll present you a date "25 sierpnia
2018", which will fit properly into your UI localization.
On the other hand on Linux, we do not have a way to retrieve a pattern,
that we could then localize."
This is terrible that Linux support for ISO 8601 date/time format is poor.
Please fix this!
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830613
Title:
Provide UI and API for customizing date/time formats
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830613/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830462] [NEW] please include the jcal package's jdate(1) utility
Public bug reported:
hi. i am hoping to see the functionality of jcal's jdate(1) utility
(*), included in the distribution.
Manfred Hampl points out there is already a debian bug report on this,
to wit: https://bugs.debian.org/863753
thanks very much.
(*) jcal is sort of a Persian 'Jalali' variant of cal(1); jdate is similarly a
sort of Jalali variant of date(1).
i am running jcal 0.4.1-2 on, hmm,
Linux minshall-apollo.minshall.org 4.4.0-146-generic #172-Ubuntu SMP Wed Apr 3
09:00:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
bash minshall-apollo: {1092} lsb_release --all
LSB Version:
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Codename: xenial
** Affects: jcal (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/1830462
Title:
please include the jcal package's jdate(1) utility
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jcal/+bug/1830462/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Intel microcode update definitely created same issue for me on Asus Zenbook 14 (UX433F) on 18.04.2 LTS. Can also confirm the instructions above "add dis_ucode_ldr to the kernel command line (from GRUB if you cannot boot)" worked perfectly for temporary workaround. This is my fourth Asus, and I've been using Linux since 1997, but I can't remember struggling as much with any other machine/distro combo as with this UX433F on Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I'm running into a similar issue with an HP Zbook Studio G4 running
Ubuntu 18.04, HP Thunderbolt 3 dock and an IOGEAR 3.0/4 Port Peripheral
Sharing Switch (GUS434). Often shortly after I switch back to the HP
using the USB switch I get the xHCI host controller not responding,
assume dead message. Based on Oded's input above I created the
following service to fix it for me:
/lib/systemd/system/xhci-watch.service
```
[Unit]
Description=Restart xhci when it dies
[Service]
ExecStart=/path/to/restart-xhci.sh
[Install]
WantedBy=multi-user.target
```
script:
```
#!/bin/bash
dmesg -l err -w -T | awk -F " " '
/xhci_hcd.*dead/ {
system("sleep 1");
device=substr($7, 1, length($7)-1);
cmd="echo -n \""device"\" | tee
/sys/bus/pci/drivers/xhci_hcd/unbind";
system(cmd);
system("sleep 1");
cmd="echo -n \""device"\" | tee
/sys/bus/pci/drivers/xhci_hcd/bind";
system(cmd);
notify="notify-send \"restarting "device" \" \""$0"\" -u
critical -i face-worried";
system(notify);
}'
```
obviously this is an ugly hack, but it might help some while a better
fix is developed. My bash/awk skills are not the best, so please feel
free to offer suggestions for improvement
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766076
Title:
USB over thunderbolt turns off every once in a while
To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825497] [NEW] flash player does not work in firefox or chromium
Public bug reported: after you allow it to run it doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 73.0.3683.103-0ubuntu1 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 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU= modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Fri Apr 19 04:29:19 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2017-04-20 (729 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Load-Avg-1min: 1.18 Load-Processes-Running-Percent: 0.4% Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) dmi.bios.date: 02/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4202 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 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.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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 firefox or 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
Re: [Bug 1803681] Re: osmesa doesn't suport core contexts but could
Fully patched 64-bit Ubuntu 18.04LTS Intel I7 AMD Radeon HD 7950 open-source drivers. Is this fixed in 18.10 or 19.04? And did you try the test program? And looking at https://packages.ubuntu.com/bionic/libs/libosmesa6, I don't see the dependency on llvm. -- Greg On Thu, Mar 14, 2019, 01:50 Timo Aaltonen wrote: > gallium osmesa is already enabled where it's supported, so what's your > platform? > > ** Changed in: mesa (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1803681 > > Title: > osmesa doesn't suport core contexts but could > > Status in mesa package in Ubuntu: > Incomplete > > Bug description: > If the --enable-osmesa in the mesa configuration were replaced with > --enable-gallium-osmesa, then the OSMesaCreateContextAttribs would be > able to return OpenGL core contexts. To show this I'm attaching a > modified version of mesa-demos-8.4.0/src/osdemos/osdemo.c (from > ftp://ftp.freedesktop.org/pub/mesa/demos/mesa-demos-8.4.0.tar.gz). > The modified code is all within the #ifdef USE_CORE_CONTEXT. To > compile it, do "gcc osdemo.c -lGLU -lOSMesa -lm". With the > libOSMesa.so.8 from Ubuntu 18.04, it fails with "OSMesaCreateContext > failed!". But with a libOSmesa.so from a mesa that is configured with > --enable-galliums-osmesa instead of --enable-osmesa, it works! > > Also note that libOSMesa.so on Ubuntu 18.04 only supports OpenGL 2.1. > While --enable-gallium-osmesa gets it up to OpenGL 3.3. My testing > was with mesa 17.3.9 and mesa 18.2.5. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803681/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803681 Title: osmesa doesn't suport core contexts but could To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)
Fix works for me (I opened duplicate #1815152): I apt upgraded to linux- modules-4.18.0-15-generic 4.18.0-15.16, and now my system boots just fine. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814555 Title: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] Re: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"
*** This bug is a duplicate of bug 1814555 *** https://bugs.launchpad.net/bugs/1814555 Bug fixed! I apt upgraded to linux-image-4.18.0-15-generic 4.18.0-15.16 as usual, and my system boots happily again. Thank you ~smb for the quick followup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236898/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236897/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] Re: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"
apport information ** Tags added: apport-collected cosmic ** Description changed: A few days ago, I let update-manager upgrade my kernel from 4.18.0-13 to 4.18.0-14. Since then, my system is unable to boot. It freezes after printing fb: switching to inteldrmfb from VESA VGA but before it gets around to asking me the passphrase for my encrypted main partition. (At first I thought it was a problem with cryptsetup because it never got to that prompt, but now I'm pretty sure it's something to do with changing video mode.) However, if I use the grub menu to select the older 4.18.0-13, the system boots just fine. It looks very much like a bug introduced between 4.18.0-13 and 4.18.0-14. Additionally, if I boot 4.18.0-14 in maintenance mode, the kernel modesetting does not happen, and the system boots just fine. (Except for the 1980s-style low-res video, that is.) This seems like good evidence that it's a problem with setting the video mode. - I'll test with some mainline builds, but I want to get this bug report - opened before I start rebooting. + I'll test with some mainline builds, but I want to get this bug report opened before I start rebooting. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.2 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.10 + HibernationDevice: RESUME=UUID=fb24f9f1-0e89-4ef6-a88a-fb9fc5d776c7 + InstallationDate: Installed on 2018-09-05 (155 days ago) + InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + IwConfig: + enp2s0no wireless extensions. + + lono wireless extensions. + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/lubuntu--vg-root ro + ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.18.0-14-generic N/A + linux-backports-modules-4.18.0-14-generic N/A + linux-firmware 1.175.1 + RfKill: + + Tags: cosmic + Uname: Linux 4.18.0-14-generic x86_64 + UpgradeStatus: Upgraded to cosmic on 2019-01-23 (16 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 07/22/2010 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1604 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: P7H55-M PRO + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: System Product Name + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236893/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236902/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236896/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236899/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236903/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236904/+files/WifiSyslog.txt ** Tags added: kernel-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236895/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236900/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236894/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1815152/+attachment/5236901/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] Re: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"
Results with mainline kernels: * linux-image-unsigned-4.18.20-041820-generic: bug present, same behaviour as in linux-image-4.18.0-14-generic * linux-image-unsigned-4.20.7-042007-generic: bug fixed! One other interesting factoid: after the failed modeset, the system isn't _completely_ dead. I can type in my passphrase for my encrypted partition, and after another 10-12 s (the usual delay) the system is ping'able and ssh'able. So stuff is up and running. But here's what does not work: * software reboot from console (Ctrl-Alt-F1, then Ctrl-Alt-Del) * "sudo reboot" from ssh session * "sudo poweroff" from ssh session The only ways I can regain control are the PC reset button or hardware power off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] Re: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"
** Attachment added: "happy boot sequence with previous build (4.18.0-13)" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+attachment/5236892/+files/happy-kernel.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815152] [NEW] kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"
Public bug reported: A few days ago, I let update-manager upgrade my kernel from 4.18.0-13 to 4.18.0-14. Since then, my system is unable to boot. It freezes after printing fb: switching to inteldrmfb from VESA VGA but before it gets around to asking me the passphrase for my encrypted main partition. (At first I thought it was a problem with cryptsetup because it never got to that prompt, but now I'm pretty sure it's something to do with changing video mode.) However, if I use the grub menu to select the older 4.18.0-13, the system boots just fine. It looks very much like a bug introduced between 4.18.0-13 and 4.18.0-14. Additionally, if I boot 4.18.0-14 in maintenance mode, the kernel modesetting does not happen, and the system boots just fine. (Except for the 1980s-style low-res video, that is.) This seems like good evidence that it's a problem with setting the video mode. I'll test with some mainline builds, but I want to get this bug report opened before I start rebooting. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Attachment added: "boot sequence hung at video mode change" https://bugs.launchpad.net/bugs/1815152/+attachment/5236891/+files/hung-kernel.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815152 Title: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192847] Re: NMI watchdog fails to increment the NMI counter in /proc/interrupts
This looks the same as https://bugzilla.redhat.com/show_bug.cgi?id=1335720 ** Bug watch added: Red Hat Bugzilla #1335720 https://bugzilla.redhat.com/show_bug.cgi?id=1335720 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192847 Title: NMI watchdog fails to increment the NMI counter in /proc/interrupts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1192847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809996] Re: PXE network boot fails when Intel SW Guard Extensions (SGX) are enabled
** Description changed: We use MAAS 2.3.5 to install Ubuntu to a cluster of computers, where - each computer boots via PXE. Each computer has 2 NICs. If you disable - one of the NICs, then when you boot the computer with Bionic (18.04), - immediately after it loads the Ramdisk (boot-initrd), the computer - immediately reboots. This continues in a loop. This seems like a - regression from 16.04. + each computer boots via PXE. On some computers, when you boot the + computer with Bionic (18.04), immediately after it loads the Ramdisk + (boot-initrd), the computer immediately reboots. This continues in a + loop. This seems like a regression from 16.04. Here are the steps to reproduce: 1. Add new computer as MAAS node - 2. Commission the node in MAAS - 3. In MAAS, go to Interfaces, select the unused NIC and select Remove Physical - 4. Deploy the node using 18.04 + 2. Commission the node in MAAS using 18.04 - Note that once you remove the unused NIC, you can reproduce this both in - MAAS Commission and MAAS Deployment. My guess is that when the init - script runs from the ramdisk, it tries to load the unused NIC and it - fails. unfortunately, the minimal PXE install (kernel + ramdisk) does - not print diagnostic info. - - Here are the steps to resolve this: - - 1. Commission the broken node using 16.04 - 2. Ensure both NICs are present under MAAS Interfaces - 3. Deploy the node using 18.04 + To resolve this, you need to disable Intel SW Guard Extensions (SGX) in + the BIOS, before Commissioning or Deploying with 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809996 Title: PXE network boot fails when Intel SW Guard Extensions (SGX) are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1809996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809996] Re: PXE network boot fails when Intel SW Guard Extensions (SGX) are enabled
** Summary changed: - PXE network boot fails when 1 NIC is disabled + PXE network boot fails when Intel SW Guard Extensions (SGX) are enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809996 Title: PXE network boot fails when Intel SW Guard Extensions (SGX) are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1809996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809996] Re: PXE network boot fails when 1 NIC is disabled
Update: I don't thinks the NIC is a reliable workaround. I'm now 99% sure a reliable workaround is to disable Intel SW Guard Extensions (SGX) in the BIOS. Once I did this, I can reliably Commission and Deploy 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809996 Title: PXE network boot fails when 1 NIC is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1809996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809996] [NEW] PXE network boot fails when 1 NIC is disabled
Public bug reported: We use MAAS 2.3.5 to install Ubuntu to a cluster of computers, where each computer boots via PXE. Each computer has 2 NICs. If you disable one of the NICs, then when you boot the computer with Bionic (18.04), immediately after it loads the Ramdisk (boot-initrd), the computer immediately reboots. This continues in a loop. This seems like a regression from 16.04. Here are the steps to reproduce: 1. Add new computer as MAAS node 2. Commission the node in MAAS 3. In MAAS, go to Interfaces, select the unused NIC and select Remove Physical 4. Deploy the node using 18.04 Note that once you remove the unused NIC, you can reproduce this both in MAAS Commission and MAAS Deployment. My guess is that when the init script runs from the ramdisk, it tries to load the unused NIC and it fails. unfortunately, the minimal PXE install (kernel + ramdisk) does not print diagnostic info. Here are the steps to resolve this: 1. Commission the broken node using 16.04 2. Ensure both NICs are present under MAAS Interfaces 3. Deploy the node using 18.04 ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809996 Title: PXE network boot fails when 1 NIC is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver
I deleted the whole section as suggested by Shawn, and also deleted the similar one with "USB". Now my touchscreen and everything else are working great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774242 Title: Wacom touchscreens should use libinput, not wacom driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I just saw that the fix is included in the new 4.19.10 kernel. You can use UKUU to install. --- Jian-Hong Pan (2): ALSA: hda/realtek: Enable audio jacks of ASUS UX533FD with ALC294 ALSA: hda/realtek: Enable audio jacks of ASUS UX433FN/UX333FA with ALC294 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336794] Re: 9pfs does not honor open file handles on unlinked files
Hi Alex, Well... it's slightly more than one patch in QEMU, and this also requires some linux kernel side changes. And I really can't^W^Wdon't want to invest more time there if no one helps. This being said, I see more and more activity on 9p since Dominique Martinet has taken maintainership. Maybe worth to resurrect the discussion on v9fs- develo...@lists.sourceforge.net ? If it gets enough momentum there, I'll be happy to go forward with the QEMU changes. Cheers, -- Greg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336794 Title: 9pfs does not honor open file handles on unlinked files To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1336794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I have same issue on new Asus ZenBook 14 UX433FA (ALC294) on Ubuntu 10.04.1 (NO dual boot). Tried the 4.19.2 kernel and nothing changed. Looking forward to some sort of fix/workaround! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803681] [NEW] osmesa doesn't suport core contexts but could
Public bug reported: If the --enable-osmesa in the mesa configuration were replaced with --enable-gallium-osmesa, then the OSMesaCreateContextAttribs would be able to return OpenGL core contexts. To show this I'm attaching a modified version of mesa-demos-8.4.0/src/osdemos/osdemo.c (from ftp://ftp.freedesktop.org/pub/mesa/demos/mesa-demos-8.4.0.tar.gz). The modified code is all within the #ifdef USE_CORE_CONTEXT. To compile it, do "gcc osdemo.c -lGLU -lOSMesa -lm". With the libOSMesa.so.8 from Ubuntu 18.04, it fails with "OSMesaCreateContext failed!". But with a libOSmesa.so from a mesa that is configured with --enable-galliums- osmesa instead of --enable-osmesa, it works! Also note that libOSMesa.so on Ubuntu 18.04 only supports OpenGL 2.1. While --enable-gallium-osmesa gets it up to OpenGL 3.3. My testing was with mesa 17.3.9 and mesa 18.2.5. ** Affects: mesa (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/1803681 Title: osmesa doesn't suport core contexts but could To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803681] Re: osmesa doesn't suport core contexts but could
** Attachment added: "simple osmesa test program" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803681/+attachment/5213361/+files/osdemo.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803681 Title: osmesa doesn't suport core contexts but could To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788035] Re: nvme: avoid cqe corruption
We did not have a series of steps to reproduce this. Just left a server running without much happening and boom. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788035 Title: nvme: avoid cqe corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607874] Re: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
#metoo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607874 Title: package sysv-rc 2.88dsf-59.3ubuntu2 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/sysvinit/+bug/1607874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788035] Re: nvme: avoid cqe corruption
We were reproducing this multiple times a day on multiple of our EC2 M5 instances. Interesting anecdote, our least loaded instances produced the bug more often than our heavily loaded instances. We've since switched to M4 servers and do not have time to flip back and help test this right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788035 Title: nvme: avoid cqe corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770604] Re: Arduino IDE from repository does not work because of "java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver"
Same problem on Lubuntu 18.04 with the build from the most current ubuntu repo (1.0.5 I believe. 2:1.0.5+dfsg2-4.1). The 1.8.4 version from the arduino website works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770604 Title: Arduino IDE from repository does not work because of "java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arduino/+bug/1770604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263633] Re:
http://just.healthyblendofcoffee.com Greg Clark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263633 Title: constracting molecules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/263633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
