[Bug 1880086] Re: [nvidia+xorg] High input latency while running gtk4 demos like Fishbowl
** Summary changed: - [nvidia+xorg] Poor desktop performance while running gtk4 demos like Fishbowl + [nvidia+xorg] High input latency while running gtk4 demos like Fishbowl ** Description changed: - Poor desktop performance while running gtk4 demos like Fishbowl, using - the Nvidia driver (on Xorg) + High input latency while running gtk4 demos like Fishbowl, using the + Nvidia driver (on Xorg) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880086 Title: [nvidia+xorg] High input latency while running gtk4 demos like Fishbowl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857764] Re: [nvidia] Brightness control is not working since last update
installed in Vaio vpceh25en having Nvidia Geforce 410M and brightness controller not working neither from slider nor from the keyboard. Also, the display looks dull and pixelated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857764 Title: [nvidia] Brightness control is not working since last update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857764] Re: [nvidia] Brightness control is not working since last update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857764 Title: [nvidia] Brightness control is not working since last update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874939] Re: ceph-osd can't connect after upgrade to focal
i filed this bug specifically for hyperconverged environments. Upgrading monitor nodes first and then upgrading separate OSD nodes is probably doable, but in a hyperconverged environment you can not separate. I tried do-release-upgrade (a couple of times) without rebooting at the end, but found the monitors and OSDs were upgraded and deadlocked at the end. I tried shutting down all Ceph services first and then do-release upgrade. Which started my Ceph services and destroyed my cluster. I tried manually upgrading Ceph, which is thwarted by the dependencies, it's all or nothing. I finally accomplished the upgrade by marking all Ceph packages held, then digging myself through the dependency jungle to upgrade the packages in the right sequence. This was an absolute nightmare and took me more than an hour per node. Obviously is not a production ready way to do so, but at least Ceph Octopus is running in 20.04 now now. ' There are two asks here: Separate the dependencies so that ceph-mon, ceph-mgr and ceph-osd can be installed separately (with the appropriate dependencies, but in a way that upgrading ceph-mon does not try to upgrade ceph-osd also. There is no good reason why upgrade of ceph-mon should go down and back up the dependency tree and try to upgrade ceph-osd too. In fact, I would not want monitor packages on my OSD nodes and vice versa in a traditional cluster. And fix do-release-upgrades, so a Ceph cluster does not get restarted when the upgrade procedure ends. I can vouch for the services being restarted, i tried it several times, once even with the services shut down before do-release-upgrade was started. An upgrade procedure that breaks customer data should be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874939 Title: ceph-osd can't connect after upgrade to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1874939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
This is very probably a bug in GnuTLS that has been fixed since. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/claws-mail/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868523] Re: "ERROR couldn't save system state: Current machine isn't Zsys, nothing to create" on non zsys system shouldn’t be visible
Hey Deepak, I’m a little bit unclear about your issue which is the different from the original bug report. ZSys was complaining on ZSys system when doing apt install or so: your logs don’t show that up. If you are running on a non ZSys system (meaning: you didn’t select ZFS on root installation), it’s normal that any ZSys service or command returns those error and you should remove ZSys. If this is not the case, please file another bug with ubuntu-bug zsys to report relevant informations to us, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868523 Title: "ERROR couldn't save system state: Current machine isn't Zsys, nothing to create" on non zsys system shouldn’t be visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1868523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876974] Re: Support multiple ESPs
IMO you should be running dpkg-reconfigure grub-efi-amd64-signed rather than grub-install or the grub-multi-install wrapper directly. grub-install cannot know if there are multiple ESPs, as the ESPs are stored in debconf. This is not different from BIOS systems, where grub-install also does not do the right thing. ** Changed in: grub2 (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876974 Title: Support multiple ESPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876974] Re: Support multiple ESPs
It's still not clear to me why you ran grub-install in the first place, though. What made you do that? If you change configuration, the right tool to run is update-grub, there is no need to reinstall grub. If you change the ESPs, you use dpkg-reconfigure, so you would not have stumbled across that. I can't really imagine a reason to run grub-install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876974 Title: Support multiple ESPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880095] [NEW] Keyboard entry stopped working
Public bug reported: I was toggling between text entry languages when the keyboard entry suddenly stopped working. Even the onscreen keyboard was not able to entry any keys. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-all (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 22 09:18:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2012-03-23 (2981 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri May 22 09:13:46 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 focal possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880095 Title: Keyboard entry stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1880095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1874939] Re: ceph-osd can't connect after upgrade to focal
Hi Christian
On Fri, May 22, 2020 at 8:10 AM Christian Huebner <
1874...@bugs.launchpad.net> wrote:
> i filed this bug specifically for hyperconverged environments. Upgrading
> monitor nodes first and then upgrading separate OSD nodes is probably
> doable, but in a hyperconverged environment you can not separate.
>
I appreciate that which is why I have endeavoured to reproduce your issue
on a hyperconverged deployment as well.
> I tried do-release-upgrade (a couple of times) without rebooting at the
> end, but found the monitors and OSDs were upgraded and deadlocked at the
> end.
> I tried shutting down all Ceph services first and then do-release upgrade.
> Which started my Ceph services and destroyed my cluster.
> I tried manually upgrading Ceph, which is thwarted by the dependencies,
> it's all or nothing.
>
> I finally accomplished the upgrade by marking all Ceph packages held,
> then digging myself through the dependency jungle to upgrade the
> packages in the right sequence. This was an absolute nightmare and took
> me more than an hour per node. Obviously is not a production ready way
> to do so, but at least Ceph Octopus is running in 20.04 now now.
>
> There are two asks here:
>
> Separate the dependencies so that ceph-mon, ceph-mgr and ceph-osd can be
> installed separately (with the appropriate dependencies, but in a way
> that upgrading ceph-mon does not try to upgrade ceph-osd also. There is
> no good reason why upgrade of ceph-mon should go down and back up the
> dependency tree and try to upgrade ceph-osd too. In fact, I would not
> want monitor packages on my OSD nodes and vice versa in a traditional
> cluster.
>
The versioning between the various binary packages that the ceph source
code produces are strongly versioned so that you can't end up with an
inappropriate/broken mix of binaries on disk at the same time.
Upgrading the ceph-mon package results in an upgrade of the ceph-osd
package because they both depend on ceph-base with a strong version
dependency of a matching binary version.
This is how we enforce a known good set of bits on disks - and is why the
package maintainer scripts don't do restarts of the daemons on upgrade so
that the restart process can be managed with appropriate upgrade ordering.
> And fix do-release-upgrades, so a Ceph cluster does not get restarted
> when the upgrade procedure ends. I can vouch for the services being
> restarted, i tried it several times, once even with the services shut
> down before do-release-upgrade was started.
>
If you shutdown services the postinst script starts
'ceph{-mon,osd,mgr}.target' so they would get started back up, but targets
and services won't get restarted - I tested and validated and checked the
installed maintainer scripts.
I think you'd have to disable and mask the targets *and* services to ensure
that the target start did not force daemons to start as well but I did not
observe any restart behaviour during my upgrade testing (other than due to
the reboot of the system).
>
> An upgrade procedure that breaks customer data should be fixed.
>
Agreed but the first step is reproduction of the issue so that we can
actually identify what the problem is.
I've followed what I think is the same process that you undertook but I've
not seen the same issue when running mixed version MON, MGR and OSD.
So there is something specific in your deployment that we've not captured
in this bug report yet.
Full details of a) /etc/ceph/ceph.conf and b) pool types and configurations
in use would be helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874939
Title:
ceph-osd can't connect after upgrade to focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1874939/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880095] Re: Keyboard entry stopped working
When the problem happens can you still operate anything with the mouse? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New ** Changed in: compiz (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880095 Title: Keyboard entry stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1880095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880099] [NEW] ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 'Gjs_ubuntu-dock_ubuntu_com_dash_Das
Public bug reported: ubuntu-dock no longer loads under gnome-shell 3.37: gnome-shell:3102): Gjs-WARNING **: 15:35:59.052: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 'Gjs_ubuntu-dock_ubuntu_com_dash_DashToDock_MyDashActor' _init@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:353:30 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: groovy ** Tags added: groovy ** Summary changed: - ubuntu-dock no longer loads under gnome-shell 3.37: S ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 'Gjs_ubuntu-dock_ubuntu_com_dash_DashToDock_MyDashActor' + ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 'Gjs_ubuntu-dock_ubuntu_com_dash_DashToDock_MyDashActor' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880099 Title: ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation- changed' on object 'Gjs_ubuntu- dock_ubuntu_com_dash_DashToDock_MyDashActor' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880095] Re: Keyboard entry stopped working
Yes the mouse did work, and I was able to use the Super key to bring up Unity's application menu (on this computer I use Unity). Typing text didn't work, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880095 Title: Keyboard entry stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1880095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874229] Re: RST/BitLocker - Do not make URLs translatable
Marking as public and not security. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874229 Title: RST/BitLocker - Do not make URLs translatable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1874229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock
I have tested xorg-server/2:1.20.8-2ubuntu2.1 in focal-proposed and it can fix this issue. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879893 Title: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878937] Re: [MIR] mathjax
All looks good on the MIR side. I’m not a big fan that we have the minimized MathJax.js source directly shipped rather than rebuilding it from the unpacked version that we shipped as well, but no rule is preventing this for javascript package. Note that this is manually overriden in: ./debian/source/lintian-overrides: mathjax source: source-is-missing mathjax source: source-contains-prebuilt-javascript-object It ships its vendored version of combiner and compressor. The code itself doesn’t seem to use particular tricks which should emit warnings to us. I would like though that a bug and fix is filed upstream to avoid having this ogg being executable: W: libjs-mathjax: executable-not-elf-or-script usr/share/javascript/mathjax/unpacked/extensions/a11y/invalid_keypress.ogg ubuntu-foundations is not assigned though, mind poking them? I’m happy to +1 on the MIR once this is done. ** Changed in: mathjax (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878937 Title: [MIR] mathjax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mathjax/+bug/1878937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880101] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1880101 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Trusty) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880101 Title: tsc test in monotonic_time failed on Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880101] [NEW] tsc test in monotonic_time failed on Trusty
Public bug reported: Issue found on Trusty 3.13.0-170-generic and 3.13.0-177.228 with amd64 node "gonzo" As this can be reproduced in the kernel from -updates, this is not a regression Test failed with: TestFail: FAIL: tsc_lfence-worst-warp=-7848 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: Incomplete ** Tags: 3.13 amd64 monotonic-time sru-20200518 trusty ** Tags added: 3.13 amd64 monotonic-time sru-20200518 trusty ** Description changed: - Issue found on Trusty 3.13.0-170-generic and 3.13.0-177.228 with node - "gonzo" + Issue found on Trusty 3.13.0-170-generic and 3.13.0-177.228 with amd64 + node "gonzo" As this can be reproduced in the kernel from -updates, this is not a regression Test failed with: - TestFail: FAIL: tsc_lfence-worst-warp=-7848 + TestFail: FAIL: tsc_lfence-worst-warp=-7848 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) 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/1880101 Title: tsc test in monotonic_time failed on Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880100] [NEW] On ARM systems, package error stops any system upgrade
Public bug reported: After system install on an ARM system (Orange Pi Zero), an attempt to update the system via `apt full-upgrade` results in the following error: Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 26, in col.create(db) File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 93, in create self._fill_commands(con) File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 127, in _fill_commands self._parse_single_commands_file(con, fp) File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 165, in _parse_single_commands_file suite=tagf.section["suite"] KeyError: 'suite' Quick fix for me was to remove the package with `sudo apt purge command- not-found && sudo apt --purge autoremove`. Reinstall of the package leads to the same results. command-not-found version: 20.04.2 Version table: 20.04.2 500 500 http://ports.ubuntu.com focal/main armhf Packages python --version: command not found python3 --version: Python 3.8.2 ** Affects: command-not-found (Ubuntu) Importance: Undecided Status: New ** Description changed: After system install on an ARM system (Orange Pi Zero), an attempt to update the system via `apt full-upgrade` results in the following error: Traceback (most recent call last): - File "/usr/lib/cnf-update-db", line 26, in - col.create(db) - File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 93, in create - self._fill_commands(con) - File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 127, in _fill_commands - self._parse_single_commands_file(con, fp) - File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 165, in _parse_single_commands_file - suite=tagf.section["suite"] + File "/usr/lib/cnf-update-db", line 26, in + col.create(db) + File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 93, in create + self._fill_commands(con) + File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 127, in _fill_commands + self._parse_single_commands_file(con, fp) + File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 165, in _parse_single_commands_file + suite=tagf.section["suite"] KeyError: 'suite' Quick fix for me was to remove the package with `sudo apt purge command- not-found && sudo apt --purge autoremove`. Reinstall of the package leads to the same results. command-not-found version: 20.04.2 Version table: - 20.04.2 500 - 500 http://ports.ubuntu.com focal/main armhf Packages + 20.04.2 500 + 500 http://ports.ubuntu.com focal/main armhf Packages + + python --version: command not found + python3 --version: Python 3.8.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880100 Title: On ARM systems, package error stops any system upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1880100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880005] Re: Shutdown/Poweroff Failed with Kernel 5.0.3-53
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 ** This bug has been marked a duplicate of bug 1879997 HP-255-G7-Notebook-PC 5.3.0-51-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880005 Title: Shutdown/Poweroff Failed with Kernel 5.0.3-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879997] Re: HP-255-G7-Notebook-PC 5.3.0-51-generic
Ubuntu-5.3.0-54.48 will fix it:
commit adfa5c21954fc496c64b5c492bd95d9e18c0d33f
Author: Prike Liang
Date: Mon Apr 13 21:41:14 2020 +0800
drm/amdgpu: fix the hw hang during perform system reboot and reset
BugLink: https://bugs.launchpad.net/bugs/1876321
commit b2a7e9735ab2864330be9d00d7f38c961c28de5d upstream.
The system reboot failed as some IP blocks enter power gate before perform
hw resource destory. Meanwhile use unify interface to set device CGPG to
ungate
state can simplify the amdgpu poweroff or reset ungate guard.
Fixes: 487eca11a321ef ("drm/amdgpu: fix gfx hang during suspend with video
playback (v2)")
Signed-off-by: Prike Liang
Tested-by: Mengbing Wang
Tested-by: Paul Menzel
Acked-by: Alex Deucher
Signed-off-by: Alex Deucher
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Kamal Mostafa
Signed-off-by: Kleber Sacilotto de Souza
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879997
Title:
HP-255-G7-Notebook-PC 5.3.0-51-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879997/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
** Changed in: ubuntu-z-systems Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880103] [NEW] Awaking problem after suspend mode still happens
Public bug reported: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "log messages_" https://bugs.launchpad.net/bugs/1880103/+attachment/5375514/+files/log%20messages_ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880103 Title: Awaking problem after suspend mode still happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880106] [NEW] colmap: error while loading shared libraries: libCGAL.so.13
Public bug reported: Upgraded to 20.04, package colmap was working, but now when I try to start it it gives colmap: error while loading shared libraries: libCGAL.so.13: cannot open shared object file: No such file or directory When I look for an installation candidate, I see cgal has gone to being header only, so there isn't an library any more. Description:Ubuntu 20.04 LTS Release:20.04 X64 colmap: Installed: 3.6+dev2+git20191105-1build1 Candidate: 3.6+dev2+git20191105-1build1 Version table: *** 3.6+dev2+git20191105-1build1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: colmap (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/1880106 Title: colmap: error while loading shared libraries: libCGAL.so.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colmap/+bug/1880106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877643] Re: netplan.io 0.98 introduced more strict parsing of bonding mode, causing failures at boot for existing systems
Hi Brian, for Bionic SRU verification, I checked the logs of the automatic integration test-suite (autopkgtests) of netplan.io (0.99-0ubuntu3~18.04.2) and made sure all tests finished successfully. Vorlon re-trigger one autopkgtest for bionic/amd64, due to a timing issue (flaky test); it ran successfully the 2nd time and all autopkgtests for Bionic are now green. All bionic test logs are attached to the description of this bug report. Additionally, I executed the following manual test inside a Bionic multipass instance, which shows that netplan's 'generate' is not rejecting the config anymore, but printing a warning instead! All looking good to me! === TEST SETUP === ubuntu@b:~$ cat test.yaml network: version: 2 ethernets: ens4: match: name: eth0 bonds: bond0: interfaces: [ens4] parameters: mode: lacp arp-ip-targets: - 192.168.0.10 dhcp4: true === BEFORE === ubuntu@b:~$ dpkg -l | grep netplan ii libnetplan0:amd640.99-0ubuntu3~18.04.1 ii netplan.io 0.99-0ubuntu3~18.04.1 ubuntu@b:~$ sudo /lib/netplan/generate test.yaml test.yaml:11:15: Error in network definition: unknown bond mode 'lacp' mode: lacp ^ ubuntu@b:~$ echo $? 1 === AFTER === ubuntu@b:~$ dpkg -l | grep netplan ii libnetplan0:amd640.99-0ubuntu3~18.04.2 ii netplan.io 0.99-0ubuntu3~18.04.2 ubuntu@b:~$ sudo /lib/netplan/generate test.yaml WARNING: unknown bond mode 'lacp'. Your config needs to be updated to work with future series of Ubuntu. ubuntu@b:~$ echo $? 0 ** Description changed: As noted in https://github.com/CanonicalLtd/netplan/pull/97#issuecomment-625868233 , netplan.io 0.98 has introduced stricter validation rules for netplan yaml compared to previous versions. This causes previously accepted netplan yaml to fail to validate and therefore fail to apply, regressing users' networks after SRU upgrade. === SRU === [Impact] This release contains one regression bug-fix for the bionic stable release and we would like to make sure all of our supported customers have access to these improvements. - * Do not reject invalid bonding mode config (LP: #1877643) -- Print a warning instead on bionic -- Only affects the bionic series + * Do not reject invalid bonding mode config (LP: #1877643) + - Print a warning instead on bionic + - Only affects the bionic series See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. Special attention is given to tests/generator/test_bonds.py -> - test_bond_invalid_mode, which was adopted to *not* reject an invalid - bond config, but print a "WARNING: unknown bond mode '%s'" instead. + test_bond_invalid_mode (unit test at compile time), which was adopted to + *not* reject an invalid bond config, but print a "WARNING: unknown bond + mode '%s'" instead. - + https://slyon.de/files/netplan/SRU-0.99b2/bionic_amd64_log + https://slyon.de/files/netplan/SRU-0.99b2/bionic_arm64_log + https://slyon.de/files/netplan/SRU-0.99b2/bionic_armhf_log + https://slyon.de/files/netplan/SRU-0.99b2/bionic_i386_log + https://slyon.de/files/netplan/SRU-0.99b2/bionic_ppc64el_log + https://slyon.de/files/netplan/SRU-0.99b2/bionic_s390x_log [Discussion] It may be appropriate from an upstream POV to make the validation of input more strict over time, but it is never acceptable for an SRU to regress the interpretation of user config in this manner and cause config to fail to apply. This PR either needs to be reverted for bionic, or it needs to be modified to treat unknown modes as a warning instead of a failure. [Changelog] debian/patches/Fix-invalid-bond-mode-SRU-regression-LP-1877643.patch: [PATCH] Fix invalid bond mode SRU regression (LP: #1877643) ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877643 Title: netplan.io 0.98 introduced more strict parsing of bonding mode, cau
[Bug 1874554] Re: gammu-smsd fails to install in focal
This bug was fixed in the package gammu - 1.41.0-1.1 --- gammu (1.41.0-1.1) unstable; urgency=medium [ Balint Reczey ] * Non-maintainer upload * Add Salsa CI configuration [ Rolf Leggewie ] * Fix systemd service file (Closes: #959176) (LP: #1874554) * Build-depend on systemd to let CMake install the gammu-smsd service -- Balint Reczey Thu, 21 May 2020 16:57:57 +0200 ** Changed in: gammu (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874554 Title: gammu-smsd fails to install in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gammu/+bug/1874554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879680] Re: Touchpad not detected on Wortmann 1460p
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879680 Title: Touchpad not detected on Wortmann 1460p To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879612] Re: Wifi looses connection more often after the upgrade
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879612 Title: Wifi looses connection more often after the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879612/+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%
hmm this bug was introduced here 1 month before the release of 20.4 and now a month after the release the bug is still there... that's somehow quite a bit of a downer, at least for me :( i know the devs always have a lot of work to do, but is there at least a light at the end of the tunnel ? can we expect a solution to this bug anytime soon ? -- 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 1880108] [NEW] package libgl-dev 1.3.1-1 failed to install/upgrade: 正试图覆盖 /usr/include/GL/gl.h，它同时被包含于软件包 mesa-common-dev:amd64 20.0.4-2ubuntu1~18.04.1
*** This bug is a security vulnerability *** Public security bug reported: When I was updating my system from 18.04LTS to 20.04, the computer's power shutting down unfortunately. After rebooted, the bugs throw out. So I've tried to --fix the problem. But they keep occurring. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgl-dev 1.3.1-1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 22 12:26:23 2020 ErrorMessage: 正试图覆盖 /usr/include/GL/gl.h，它同时被包含于软件包 mesa-common-dev:amd64 20.0.4-2ubuntu1~18.04.1 InstallationDate: Installed on 2018-06-20 (701 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libglvnd Title: package libgl-dev 1.3.1-1 failed to install/upgrade: 正试图覆盖 /usr/include/GL/gl.h，它同时被包含于软件包 mesa-common-dev:amd64 20.0.4-2ubuntu1~18.04.1 UpgradeStatus: Upgraded to focal on 2020-05-22 (0 days ago) ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880108 Title: package libgl-dev 1.3.1-1 failed to install/upgrade: 正试图覆盖 /usr/include/GL/gl.h，它同时被包含于软件包 mesa-common-dev:amd64 20.0.4-2ubuntu1~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1880108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879613] Re: Computer hung when resuming from suspend
No I don't think so. It's catch 22... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879613 Title: Computer hung when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880114] [NEW] Syntax error in LayoutLoaderSVG.py shipped with this package
Public bug reported:
During upgrade from 19.10 to 20.04 I saw an error message flying by:
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py in line 447
There currently is the following code:
raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
"definition of %s" (strerror, full_id))
Obviously this should be:
raise Exceptions.LayoutFileError("Unrecognized modifier {} in" \
"definition of {}".format(strerror, full_id))
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: onboard 1.4.1-2ubuntu7
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 22 10:25:57 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-11 (1653 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: onboard
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: onboard (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Patch added: "patch containing bug fix"
https://bugs.launchpad.net/bugs/1880114/+attachment/5375543/+files/onboard.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880114
Title:
Syntax error in LayoutLoaderSVG.py shipped with this package
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1880114/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880113] [NEW] Sync python-httplib2 0.17.4-1 (main) from Debian unstable (main)
Public bug reported: Please sync python-httplib2 0.17.4-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Add debian/patches/0003-Fix-autopkgtests.patch: Make test suite work, by skipping approx. 50 tests, which try to access an non-existent external server. Fix a few of them, using a HTTP mock server. The test suite activated by 0003-Fix-autopkgtests.patch is deprecated by upstream. I've integrated upstream's new test suite with 0.17.4 in Debian. Changelog entries since current groovy version 0.14.0-3ubuntu1: python-httplib2 (0.17.4-1) unstable; urgency=medium [ Lukas Märdian ] * Bump version to 0.17.4 * Use upstream's new test suite in tests/ & test/ - python3/httplib2test.py is deprecated * Refresh d/p/0001-Use-system-ca-certificates-not-the-bundled-ones.patch * Drop d/p/0002-Fix-debug-in-HTTPSConnectionWithTimeout.connect.patch - Fixed upstream * Add d/p/skip-ca-md-too-weak-ssl-tests.patch - Skip some tests, which fail because of CA_MD_TOO_WEAK ssl error with newer OpenSSL version [ Jelmer Vernooij ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update standards version to 4.5.0, no changes needed. -- Jelmer Vernooij Wed, 20 May 2020 19:03:38 + ** Affects: python-httplib2 (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/1880113 Title: Sync python-httplib2 0.17.4-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-httplib2/+bug/1880113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880103] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1880103 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880103 Title: Awaking problem after suspend mode still happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880109] [NEW] apparmor profile: allow read on /proc/sys/kernel/random/boot_id
Public bug reported: I get the follow kernel message: May 22 08:11:49 srv1 kernel: [29050.927299] audit: type=1400 audit(1590135109.257:99): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/sys/kernel/random/boot_id" pid=9559 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 It could be easy to fix it: --- /tmp/usr.sbin.mysqld2020-05-22 08:21:49.698953104 + +++ /etc/apparmor.d/usr.sbin.mysqld 2020-05-22 08:15:54.180942772 + @@ -11,6 +11,7 @@ # Allow system resource access /proc/*/status r, + /proc/sys/kernel/random/boot_id r, /sys/devices/system/cpu/ r, /sys/devices/system/node/ r, /sys/devices/system/node/** r, And replace the current profile with: apparmor_parser -r /etc/apparmor.d/usr.sbin.mysqld It would be nice, to include this fix to the current version. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mysql-server 8.0.20-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri May 22 08:18:37 2020 InstallationDate: Installed on 2020-05-01 (20 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLVarLibDirListing: ['#ib_16384_0.dblwr', 'binlog.07', 'client-key.pem', 'binlog.01', 'test', 'undo_001', 'debian-5.7.flag', 'ca.pem', 'binlog.10', 'performance_schema', 'public_key.pem', 'undo_002', 'debian-5.5.flag', 'server-cert.pem', 'binlog.06', 'client-cert.pem', 'mysql_upgrade_info', 'mysql', '#ib_16384_1.dblwr', 'binlog.11', 'ibtmp1', 'topackt', 'binlog.03', 'binlog.04', 'ib_buffer_pool', '#innodb_temp', 'auto.cnf', 'private_key.pem', 'ib_logfile0', 'ib_logfile1', 'binlog.index', 'binlog.05', 'mysql.ibd', 'sys', 'ca-key.pem', 'phpmyadmin', 'ibdata1', 'binlog.08', 'binlog.09', 'binlog.02', 'server-key.pem', 'proftpd', 'srv1.pid'] PackageArchitecture: all ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: mysql-8.0 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.usr.sbin.mysqld: [modified] modified.conffile..etc.mysql.mysql.conf.d.mysql.cnf: [modified] modified.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: [modified] mtime.conffile..etc.apparmor.d.usr.sbin.mysqld: 2020-05-22T08:15:54.180943 mtime.conffile..etc.mysql.mysql.conf.d.mysql.cnf: 2020-05-22T08:11:39.057082 mtime.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: 2020-05-22T08:10:42.401548 ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal third-party-packages uec-images ** Summary changed: - apparmor profile allow read on /proc/sys/kernel/random/boot_id + apparmor profile: allow read on /proc/sys/kernel/random/boot_id -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880109 Title: apparmor profile: allow read on /proc/sys/kernel/random/boot_id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1880109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879680] Re: Touchpad not detected on Wortmann 1460p
** Tags added: hwe-touchpad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879680 Title: Touchpad not detected on Wortmann 1460p To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878899] Re: Call trace from __video_do_ioctl
Bus 008 Device 015: ID 046d:08af Logitech, Inc. QuickCam Easy/Cool Bus 008 Device 013: ID 046d:0892 Logitech, Inc. OrbiCam Both used by OBS Studio, which then sent its output to a v4l2loobback device, module parameters: /sbin/modprobe v4l2loopback devices=1 video_nr=10 card_label="OBS Cam" exclusive_caps=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878899 Title: Call trace from __video_do_ioctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863021] Fix merged to watcher (stable/ussuri)
Reviewed: https://review.opendev.org/728397 Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=043ebb71c6354b62b56b0361b7fdbff54146241e Submitter: Zuul Branch:stable/ussuri commit 043ebb71c6354b62b56b0361b7fdbff54146241e Author: Chris MacNaughton Date: Wed May 6 08:10:32 2020 +0200 Monkey patch original current_thread _active Monkey patch the original current_thread to use the up-to-date _active global variable. This solution is based on that documented at: https://github.com/eventlet/eventlet/issues/592 Change-Id: I194eedd505d45137963eb40d1b1d5da2309caeac Closes-Bug: #1863021 (cherry picked from commit 0b4c4f1de68631164d62dbf66160e5d8cb923518) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863021 Title: [SRU] eventlet monkey patch results in assert len(_active) == 1 AssertionError To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1863021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879575] Re: Missing driver for rtl8822be in 20.04
Does cold boot help this issue? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879575 Title: Missing driver for rtl8822be in 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable"
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 For me, upgrading from groovy helped Add and uncomment lines to sources.list #deb http://pl.archive.ubuntu.com/ubuntu/ groovy main restricted universe multiverse #deb http://pl.archive.ubuntu.com/ubuntu/ groovy-backports main restricted universe multiverse #deb http://pl.archive.ubuntu.com/ubuntu/ groovy-security main restricted universe multiverse #deb http://pl.archive.ubuntu.com/ubuntu/ groovy-updates main restricted universe multiverse #deb http://pl.archive.ubuntu.com/ubuntu/ groovy-proposed main restricted universe multiverse apt update apt install libpulse0/groovy-proposed apt install pulseaudio/groovy-proposed ! comment out those lines in sources.list again ! run apt update again ! do not upgrade your ubuntu when groovy repositories are turned on -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)
It'll be fixed by Ubuntu-5.4.0-32.36. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870140 Title: Laptop freeze after unplug power-AC (USB-C) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] [NEW] System hangs on shut down Kernel 5.3.0-53
Public bug reported: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version and inxi output" https://bugs.launchpad.net/bugs/1880119/+attachment/5375547/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879612] Re: Wifi looses connection more often after the upgrade
I see a few "wlo1: deauthenticating from by local choice (Reason: 3=DEAUTH_LEAVING)". Could you attach the whole journal log? $ journalctl -b > journal.log And attach it here. We might have to enable verbose log for NetworkManager/wpasupplicant, but let's what do we have so far. ** Tags added: hwe-networking-wifi ** Summary changed: - Wifi looses connection more often after the upgrade + Ralink RT5390 [1814:539f] Subsystem [103c:1774] Wifi looses connection more often after the upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879612 Title: Ralink RT5390 [1814:539f] Subsystem [103c:1774] Wifi looses connection more often after the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873581] Re: install from 19.10 --> 20.04 crashed system
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub-installer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873581 Title: install from 19.10 --> 20.04 crashed system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1873581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869279] Re: zsys clutters up the system and stops system updates.
This issue has been reported again here: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876334 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869279 Title: zsys clutters up the system and stops system updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1869279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879776] Re: ubuntu 20 error mounting smb drive
Indeed, files shown as directories is this bug #1872476. The fix from the PPA works. There the same environment as I have (FritzBox) is mentioned. Newer software levels of FritzOs (expected this summer) will have support for smb2/3 Min protocol = NT1 solved the first problem. I wonder, why would a CLIENT bother about the level of the SERVER? Just accept the server as is, perhaps with some warning. Or at least give a message that the server is "old". Sebastien, thanks for your support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879776 Title: ubuntu 20 error mounting smb drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1879776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] CRDA.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375550/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] Re: System hangs on shut down Kernel 5.3.0-53
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Tags added: apport-collected tricia ** Description changed: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: toni 1676 F pulseaudio + /dev/snd/controlC1: toni 1676 F pulseaudio + /dev/snd/controlC0: toni 1676 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19.3 + HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 + InstallationDate: Installed on 2019-07-25 (301 days ago) + InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 + IwConfig: + enp8s0no wireless extensions. + + lono wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. B450M S2H + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-53-generic N/A + linux-backports-modules-5.3.0-53-generic N/A + linux-firmware1.173.18 + RfKill: + + Tags: tricia + Uname: Linux 5.3.0-53-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 11/27/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F50 + dmi.board.asset.tag: Default string + dmi.board.name: B450M S2H + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: Default string + dmi.product.name: B450M S2H + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375549/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] PulseList.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375559/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] ProcInterrupts.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375557/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] ProcCpuinfo.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375554/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] ProcCpuinfoMinimal.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/537/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] Lsusb.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375553/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] Re: System hangs on shut down Kernel 5.3.0-53
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 ** This bug has been marked a duplicate of bug 1879997 HP-255-G7-Notebook-PC 5.3.0-51-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879211] Re: Charging my cellphone through usb breaks internet connection.
** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879211 Title: Charging my cellphone through usb breaks internet connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1879211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] CurrentDmesg.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375551/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] ProcEnviron.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375556/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] Lspci.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375552/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] UdevDb.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375560/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] WifiSyslog.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375561/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] ProcModules.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375558/+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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
Hello Roman, or anyone else affected, Accepted pulseaudio into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pulseaudio (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags removed: verification-failed verification-failed-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876065 Title: After unplug headphones and plug them again no sound can be heard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864993] Re: platform.linux_distribution has been removed from Python3.8
James Page submitted a fix upstream: https://github.com/ceph/ceph-deploy/pull/496 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864993 Title: platform.linux_distribution has been removed from Python3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-deploy/+bug/1864993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen
Adding movie depicting the problem. And it happens without actually moving the mouse, after dragging the window. ** Attachment added: "IMG_1245.MOV" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870512/+attachment/5375562/+files/IMG_1245.MOV -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870512 Title: forced software cursor with PageFlip enabled triggers artifacts on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
Hello hugh, or anyone else affected, Accepted pulseaudio into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pulseaudio (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-failed-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880121] [NEW] /usr/bin/gnome-shell:11:__strncmp_avx2:g_str_has_prefix:_st_theme_node_ensure_background:st_theme_node_paint_equal:st_widget_recompute_style
*** This bug is a duplicate of bug 1877760 *** https://bugs.launchpad.net/bugs/1877760 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880121 Title: /usr/bin/gnome- shell:11:__strncmp_avx2:g_str_has_prefix:_st_theme_node_ensure_background:st_theme_node_paint_equal:st_widget_recompute_style To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
Thanks for suggestion but I do not feel comfortable drop a line from a patch before perfectly understanding everything in drivers. If Hisilicon can help on backporting or test case, that will be much helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880121] Re: /usr/bin/gnome-shell:11:__strncmp_avx2:g_str_has_prefix:_st_theme_node_ensure_background:st_theme_node_paint_equal:st_widget_recompute_style
*** This bug is a duplicate of bug 1877760 *** https://bugs.launchpad.net/bugs/1877760 ** This bug has been marked a duplicate of private bug 1877760 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880121 Title: /usr/bin/gnome- shell:11:__strncmp_avx2:g_str_has_prefix:_st_theme_node_ensure_background:st_theme_node_paint_equal:st_widget_recompute_style To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal
** Summary changed: - gnome-shell crashed with SIGSEGV in __strncmp_avx2() + gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal ** Information type changed from Private to Public ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Description changed: + https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3 + + --- + Started the computer from suspend. Started Gmail from Dash to Panel. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 18:30:48 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-04-16 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 SegvAnalysis: - Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu (%rdi),%ymm1 - PC (0x7fe9fdcc3e41) ok - source "(%rdi)" (0xf0250) not located in a known VMA region (needed readable region)! - destination "%ymm1" ok + Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu (%rdi),%ymm1 + PC (0x7fe9fdcc3e41) ok + source "(%rdi)" (0xf0250) not located in a known VMA region (needed readable region)! + destination "%ymm1" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - __strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101 - g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so - st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so - ?? () from /usr/lib/gnome-shell/libst-1.0.so + __strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101 + g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so + st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so + ?? () from /usr/lib/gnome-shell/libst-1.0.so Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877760 Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872901] Re: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyr
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872901 Title: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules /gnome-keyring.module', which is also in package gnome-keyring- pkcs11:amd64 3.34.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1872901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 I have a similar problem on an HP desktop, with the number affected, this requires a very urgent fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870779 Title: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843988] Re: python library installed into site-packages instead of into dist-packages
yes, it does.
I actually had the problem on a raspberry pi running Raspbian 10. There
I had to add the following to my script so that the library would be
found:
sys.path.append('/usr/lib/arm-linux-gnueabihf/python3.7/site-packages/')
(after having analyzed the problem I then sent the bug report from my
desktop computer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843988
Title:
python library installed into site-packages instead of into dist-
packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1843988/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872901] Re: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyr
** Changed in: gnome-keyring (Ubuntu) Assignee: (unassigned) => savan (hastler1990) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872901 Title: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules /gnome-keyring.module', which is also in package gnome-keyring- pkcs11:amd64 3.34.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1872901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Upgraded from ubuntu 18.04 to 20.04 today and was happy that DisplayLink finally started to work. Well, that is until I realised how totally unusable it was! Exactly the same experience as the other posters. I'm using an Acer Aspire V5 with a DisplayLink D3100 device and dual monitors. Then I noticed something very interesting. If I also plugged in a monitor to the VGA output, everything works perfectly. As soon as I unplug the VGA monitor, it is unusable again. While not ideal, this is a reasonable work-around for me until the bug is fixed. The down-side of this workaround for me is that the VGA output is plugged into a VGA input of one of my monitors. So although ubuntu thinks I have 3 monitors, there are only two. This means if I launch an app and it goes to the VGA output, I can't see it. It takes a bit of fiddling around to drag it to the DisplayLink output. Looking forward to this bug being fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1875015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852221] Re: ovs-vswitchd needs to be forced to reconfigure after adding protocols to bridges
** Summary changed: - ovsdb-server needs to be restarted after adding protocols to bridges + ovs-vswitchd needs to be forced to reconfigure after adding protocols to bridges ** Description changed: As part of programming OpenvSwitch, Neutron will add to which protocols bridges support [0]. - However, the Open vSwitch `ovsdb-server` process does not appear to - update its perspective of which protocol versions it should support - until it is restarted: + However, the Open vSwitch `ovs-vswitchd` process does not appear to + always update its perspective of which protocol versions it should + support for bridges: # ovs-ofctl -O OpenFlow14 dump-flows br-int 2019-11-12T12:52:56Z|1|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt: version negotiation failed (we support version 0x05, peer supports version 0x01) ovs-ofctl: br-int: failed to connect to socket (Broken pipe) - # systemctl restart ovsdb-server + # systemctl restart ovsdb-server # ovs-ofctl -O OpenFlow14 dump-flows br-int - cookie=0x84ead4b79da3289a, duration=1.576s, table=0, n_packets=0, n_bytes=0, priority=65535,vlan_tci=0x0fff/0x1fff actions=drop - cookie=0x84ead4b79da3289a, duration=1.352s, table=0, n_packets=0, n_bytes=0, priority=5,in_port="int-br-ex",dl_dst=fa:16:3f:69:2e:c6 actions=goto_table:4 + cookie=0x84ead4b79da3289a, duration=1.576s, table=0, n_packets=0, n_bytes=0, priority=65535,vlan_tci=0x0fff/0x1fff actions=drop + cookie=0x84ead4b79da3289a, duration=1.352s, table=0, n_packets=0, n_bytes=0, priority=5,in_port="int-br-ex",dl_dst=fa:16:3f:69:2e:c6 actions=goto_table:4 ... (Success) - 0: - https://github.com/openstack/neutron/blob/0fa7e74ebb386b178d36ae684ff04f03bdd6cb0d/neutron/agent/common/ovs_lib.py#L281 + The restart of the `ovsdb-server` process above will make `ovs-vswitchd` + reassess its configuration. + + + 0: https://github.com/openstack/neutron/blob/0fa7e74ebb386b178d36ae684ff04f03bdd6cb0d/neutron/agent/common/ovs_lib.py#L281 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852221 Title: ovs-vswitchd needs to be forced to reconfigure after adding protocols to bridges To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1852221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal
** Tags added: focal regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877760 Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878361] Re: After update in the gnome-clocks package, the sound of the timer and the alarm stopped working
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878361 Title: After update in the gnome-clocks package, the sound of the timer and the alarm stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/vala/+bug/1878361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879674] Re: audio card disappeared after suspend during audio playback
** Package changed: linux-meta-oem-osp1 (Ubuntu) => linux-oem-osp1 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879674 Title: audio card disappeared after suspend during audio playback To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880125] [NEW] v3d driver clock problem forces OpenGL to use software rendering
Public bug reported: release: 32-bit ubuntu 20.04 running on a raspberry pi 4 package: linux-raspi 5.4.0.1008.8 I made the configuration change described in: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862 and am running a kernel with v3d on a raspberry pi 4. Unfortunately, OpenGL is still not using the GPU; it's using the software renderer, llvmpipe. Setting LIBGL_DEBUG=verbose and running an OpenGL program shows that OpenGL can't open any /dev/dri/renderD* device. Looking in /dev/dri, there are no device files that begin with "render," indicating the v3d driver isn't starting up properly. Adding debugging code to the kernel, I find that: (1) drivers/gpu/drm/v3d/v3d_drv.c:v3d_platform_drm_probe() fails because it can't get a clock - devm_clk_get() returns an error. (2) in drivers/clk/clk.c:of_clk_get_hw(), the call to of_parse_clkspec() for the v3d driver yields a desired clock source of "firmware-clocks". (3) drivers/clk/clk.c:of_clk_get_hw_from_clkspec() fails because it can only find six clock providers (aux@7e215000, cprman@7e101000, clock@7ef0, clk-108M, clk-usb, clk-osc) none of which match the requested "firmware-clocks". The solution is to add a clock definition to the kernel source and a corresponding change to the device tree, but I'm not familiar enough with either to create that solution myself. In the raspbian kernel source tree, drivers/clk/bcm/clk-raspberrypi.c defines BCM2835_CLOCK_V3D, but there is no corresponding definition in the ubuntu source tree. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: device-tree kernel-bug opengl raspberry-pi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880125 Title: v3d driver clock problem forces OpenGL to use software rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880124] [NEW] xfce4-screensaver blocks UI on hyper-v
Public bug reported: I have a VM running in hyper-v (on Windows 10, a desktop). My system is a xubuntu, which means with xfce as standard window manager. It was previously running on xubuntu 18.04, but now, after upgrading to 20.04, the UI "freezes" every time after a few minutes. Using a text VT, I found that it's the process xfce4-screensaver which I have to kill to be able to continue my work. After killing, everyting works fine. It seems that under this environment, the screensaver blocks inputs (I guess for security reasons), but fails to paint anything on the screen which should now show a screensaver or blank. I don't see any text field for entering a password or similar, like I do on other installations which are not in a VM. I recognized some changes also on these other (non-virtualized) systems, they started now to ask for a password which they didn't on 18.04. So I can only guess that something on this mechanism is shaky. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xfce4-screensaver 0.1.10-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri May 22 11:19:15 2020 SourcePackage: xfce4-screensaver UpgradeStatus: Upgraded to focal on 2020-05-20 (2 days ago) ** Affects: xfce4-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880124 Title: xfce4-screensaver blocks UI on hyper-v To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1880124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880113] Re: Sync python-httplib2 0.17.4-1 (main) from Debian unstable (main)
I have ran syncpackage for this, should be done now. ** Changed in: python-httplib2 (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: python-httplib2 (Ubuntu) Status: New => 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/1880113 Title: Sync python-httplib2 0.17.4-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-httplib2/+bug/1880113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770731] Re: [nvidia] multimonitor ghostly flickering display artifacts
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #175 https://gitlab.gnome.org/GNOME/mutter/issues/175 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/175 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770731 Title: [nvidia] multimonitor ghostly flickering display artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1770731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844808] Re: Can't delete file from desktop by clicking it and hitting delete key
Hello Jonathan, or anyone else affected, Accepted gnome-shell-extension-desktop-icons into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons/20.04.0-2~ubuntu20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844808 Title: Can't delete file from desktop by clicking it and hitting delete key To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1844808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845491] Re: CTRL + "Single Click" fails to un-select a selected icon
Hello Banin, or anyone else affected, Accepted gnome-shell-extension-desktop-icons into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons/20.04.0-2~ubuntu20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845491 Title: CTRL + "Single Click" fails to un-select a selected icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1845491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879375] Re: Images thumbnails doesn't update on image changes
Hello Marco, or anyone else affected, Accepted gnome-shell-extension-desktop-icons into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons/20.04.0-2~ubuntu20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879375 Title: Images thumbnails doesn't update on image changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1879375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880077] Re: Unable to find RPi device on RPi 3B+ with libcec4
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libcec (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880077 Title: Unable to find RPi device on RPi 3B+ with libcec4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcec/+bug/1880077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876420] Re: do-release-upgrade -d does not work to upgrade to 20.04 LTS
If that is the expected behaviour, ok. But you can read the instructions to update 18.04LTS to 20.04LTS using Prompt=lts as in https://wiki.ubuntu.com/FocalFossa/ReleaseNotes : """ To upgrade on a server system: Install update-manager-core if it is not already installed. Make sure the Prompt line in /etc/update-manager/release-upgrades is set to 'normal' if you want non-LTS upgrades, or 'lts' if you only want LTS upgrades. Launch the upgrade tool with the command sudo do-release-upgrade Follow the on-screen instructions. """ It says "sudo do-release-upgrade" not "sudo do-release-upgrade -d" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876420 Title: do-release-upgrade -d does not work to upgrade to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1876420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880126] [NEW] After resume from suspend the desktop image is broken
Public bug reported: Wheb you resume from suspend Ubuntu 20.04 and unlock your session, the desktop image is corrupted as shown on screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 22 11:43:37 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-31-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-29-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G98M [GeForce 9200M GS] [10de:06e8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G98M [GeForce 9200M GS] [103c:3629] InstallationDate: Installed on 2020-04-27 (24 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=2bd6e5fb-c1e4-4103-902e-36c3fd5ea356 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3629 dmi.board.vendor: Quanta dmi.board.version: 18.3E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.25:bd07/10/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnQuanta:rn3629:rvr18.3E:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.sku: NG735EA#ABZ dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "Snímek obrazovky pořízený 2020-05-22 11-45-16.png" https://bugs.launchpad.net/bugs/1880126/+attachment/5375575/+files/Sn%C3%ADmek%20obrazovky%20po%C5%99%C3%ADzen%C3%BD%202020-05-22%2011-45-16.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880126 Title: After resume from suspend the desktop image is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1880126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880127] Re: [JSL] SD driver support for JasperLake
Jasper Lake patches are in the queue trending v5.8-rc1. ** Description changed: Description: SD driver could not attach to the device according to the lspci log: lspci -nk -vv -xx -s 14 - There seems to be no "Kernel driver in use" for device id 38f8 00:14.0 0c03: 8086:38ed (prog-if 30 [XHCI]) - Subsystem: 8086:7270 + Subsystem: 8086:7270 - Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- + Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ - Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- + Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- + Capabilities: [90] Vendor Specific Information: Len=14 00: 86 80 f8 38 02 00 10 00 00 01 05 08 00 00 00 00 10: 04 00 13 00 40 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 70 72 30: 00 00 00 00 80 00 00 00 00 00 00 00 ff 04 00 00 - According to boot up message: [4.909543] calling sdhci_drv_init+0x0/0x20 @ 1 [4.909564] sdhci: Secure Digital Host Controller Interface driver [4.917344] sdhci: Copyright(c) Pierre Ossman [4.923973] initcall sdhci_drv_init+0x0/0x20 returned 0 after 14069 usecs [4.923985] calling sdhci_driver_init+0x0/0x1a @ 1 [4.924182] sdhci-pci :00:14.5: SDHCI controller found [8086:38f8] (rev 0) [4.932636] sdhci-pci :00:14.5: enabling device ( -> 0002) [4.940727] sdhci-pci :00:14.5: GPIO lookup for consumer cd [4.940739] sdhci-pci :00:14.5: using ACPI for GPIO lookup [4.940752] acpi device:86: GPIO: looking up cd-gpios [4.940764] acpi device:86: GPIO: looking up cd-gpio [4.940776] sdhci-pci :00:14.5: using lookup tables for GPIO lookup [4.940789] sdhci-pci :00:14.5: No GPIO consumer cd found [4.940801] sdhci-pci :00:14.5: GPIO lookup for consumer (null) [4.940813] sdhci-pci :00:14.5: using ACPI for GPIO lookup [4.940825] acpi device:86: GPIO: looking up gpios [4.940838] acpi device:86: GPIO: looking up gpio [4.940850] acpi device:86: GPIO: looking up 0 in _CRS [4.940920] sdhci-pci :00:14.5: No GPIO consumer (null) found [4.941302] probe of :00:14.5 returned 0 after 17278 usecs [4.941346] initcall sdhci_driver_init+0x0/0x1a returned 0 after 16931 usecs - The failure of loading the driver for sd card host controller might be that, there's no gpio consumer on this device. And the ICP-N GPIO driver does not have the device ID (INT34C3) it needs because the device ID has already been used for a different device (sound/soc/intel/common /soc-acpi-intel-bxt-match.c). - Target Release: 20.10 - Target Kernel: 5.6 + Target Kernel: 5.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880127 Title: [JSL] SD driver support for JasperLake To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1880127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
I have a similar problem: https://bugs.launchpad.net/ubuntu/+bug/1879973 URL for the patch: https://launchpad.net/~kaihengfeng/+archive/ubuntu /fix-lp1869819 This patch didn't fix my built-in speaker and microphone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880127] [NEW] [JSL] SD driver support for JasperLake
Public bug reported: Description: SD driver could not attach to the device according to the lspci log: lspci -nk -vv -xx -s 14 There seems to be no "Kernel driver in use" for device id 38f8 00:14.0 0c03: 8086:38ed (prog-if 30 [XHCI]) Subsystem: 8086:7270 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- 00: 86 80 f8 38 02 00 10 00 00 01 05 08 00 00 00 00 10: 04 00 13 00 40 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 70 72 30: 00 00 00 00 80 00 00 00 00 00 00 00 ff 04 00 00 According to boot up message: [4.909543] calling sdhci_drv_init+0x0/0x20 @ 1 [4.909564] sdhci: Secure Digital Host Controller Interface driver [4.917344] sdhci: Copyright(c) Pierre Ossman [4.923973] initcall sdhci_drv_init+0x0/0x20 returned 0 after 14069 usecs [4.923985] calling sdhci_driver_init+0x0/0x1a @ 1 [4.924182] sdhci-pci :00:14.5: SDHCI controller found [8086:38f8] (rev 0) [4.932636] sdhci-pci :00:14.5: enabling device ( -> 0002) [4.940727] sdhci-pci :00:14.5: GPIO lookup for consumer cd [4.940739] sdhci-pci :00:14.5: using ACPI for GPIO lookup [4.940752] acpi device:86: GPIO: looking up cd-gpios [4.940764] acpi device:86: GPIO: looking up cd-gpio [4.940776] sdhci-pci :00:14.5: using lookup tables for GPIO lookup [4.940789] sdhci-pci :00:14.5: No GPIO consumer cd found [4.940801] sdhci-pci :00:14.5: GPIO lookup for consumer (null) [4.940813] sdhci-pci :00:14.5: using ACPI for GPIO lookup [4.940825] acpi device:86: GPIO: looking up gpios [4.940838] acpi device:86: GPIO: looking up gpio [4.940850] acpi device:86: GPIO: looking up 0 in _CRS [4.940920] sdhci-pci :00:14.5: No GPIO consumer (null) found [4.941302] probe of :00:14.5 returned 0 after 17278 usecs [4.941346] initcall sdhci_driver_init+0x0/0x1a returned 0 after 16931 usecs The failure of loading the driver for sd card host controller might be that, there's no gpio consumer on this device. And the ICP-N GPIO driver does not have the device ID (INT34C3) it needs because the device ID has already been used for a different device (sound/soc/intel/common /soc-acpi-intel-bxt-match.c). Target Release: 20.10 Target Kernel: 5.8 ** Affects: intel Importance: Undecided Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Tags: intel-kernel-20.10 ** Also 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/1880127 Title: [JSL] SD driver support for JasperLake To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1880127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
That's certainly incorrect, lvm2 was fixed in focal (and hence groovy). That only leaves xenial, but updating xenial close to its EOL for something as unusual as this seems unneccessary. The supported configuration for raid1 is mdadm after all, not removing mdadm and the meta packages that depend on it and using lvm's raid support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874939] Re: ceph-osd can't connect after upgrade to focal
"However it should be possible to complete the do-release-upgrade to the point of requesting a reboot - don't - drop to the CLI and get all machines to this point and then: restart the mons across all three machines restart the mgrs across all three machines restart the osds across all three machines" Yes, I believe this would work. However, that's not normally how I would do an upgrade. Normally, I upgrade one machine, make sure it works, and then upgrade the next. I have done it this way since I built the cluster back in Firefly. When I did this time, and it destroyed every OSD on the node that I upgraded. This was very unexpected and disappointing, to say the least. I wanted to warn others and try to prevent it from happening to them. I accept some of the blame. Part of it is on me, part of it is on Ceph, part of it is 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/1874939 Title: ceph-osd can't connect after upgrade to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1874939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04
Hello Krister, or anyone else affected, Accepted network-manager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.22.10-1ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: network-manager (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870359 Title: My machine as Wi-Fi Hotspot broken after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879730] Re: cloud-init build-depends on obsolete pyflakes package
Thanks Steve. I don't think pyflakes is even being used, so we can probably drop the dependency. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879730 Title: cloud-init build-depends on obsolete pyflakes package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1879730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880142] [NEW] [RKL]RKL intel idle support
Public bug reported: Description: Provide model specific Intel_idle support for RKL. Target Release: 20.10 Target Kernel: 5.6 ** Affects: intel Importance: Undecided Status: Fix Committed ** Affects: ubuntu Importance: Undecided Status: New ** Tags: intel-kernel-20.10 ** Also 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/1880142 Title: [RKL]RKL intel idle support To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1880142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880141] [NEW] Please remove nmapsi4 and forensics-all on ppc64el, riscv64, s390x
Public bug reported: nmapsi 0.5~alpha2 now uses Qt WebEngine instead of Qt WebKit: https://github.com/nmapsi4/nmapsi4/commit/674e565d384c2109 https://salsa.debian.org/pkg-security-team/nmapsi4/-/commit/253c7c57790b4c72 So it cannot be built on architectures where Qt WebEngine is not available: ppc64el, riscv64 and s390x. Please remove its binaries and binaries of its (only) reverse dependency: forensics-all. ** Affects: forensics-all (Ubuntu) Importance: Undecided Status: New ** Affects: nmapsi4 (Ubuntu) Importance: Undecided Status: New ** Also affects: nmapsi4 (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/1880141 Title: Please remove nmapsi4 and forensics-all on ppc64el, riscv64, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/forensics-all/+bug/1880141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880142] Re: [RKL]RKL intel idle support
18734958e9bfbc055805d110a38dc76307eba742 239ed06d0eefc4ee351af69bd64742ada56c4bdb 4ec32d9e8e5b6d6eb4913938665d8a2388fa 75a80267410e38ab76c4ceb39753f96d72113781 77fb4e0a559a960eb36d0b2c50c781c5492577eb 987c785319b99e32602f7f86cfae3cf9b81e402b 9f3d6daf61e5156139cd05643f7f1c2a9b7b49b0 a3299182216397a0b943d2549d1997f4eba2bdd2 aa659a3fca79abd9a3ca3ddc535db631b01c9a02 bc94638886ab21f8247d3f7f39573d3feb7d8284 bff8e60a86f4960133f90ad9add9adeb082b8154 e6d4f08a677654385869ba0c39d7c9ceec47e5c5 ** Changed in: intel Status: New => 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/1880142 Title: [RKL]RKL intel idle support To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1880142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874939] Re: ceph-osd can't connect after upgrade to focal
"As a side note - even if there is a bug here (and it sounds like there might be) I would recommend placing the mon and mgr daemons in LXD containers ontop of the machines hosting the osd's" Yes. I would strongly suggest doing this also. That is how Ceph now recommends it anyway. However, older installs are not usually set up this way. And there is no warning that if you aren't set up this way that do- release-upgrade will destroy the node. I would have been happy to make the change, I just didn't know it was necessary. Also, and not to complain, but if you are setting up this way, there is no reason for the monitor package to be installed outside of the container - and it should probably not be. This would suggest to me that ceph-mon should "conflict" with ceph-osd since they should never be installed in the same context/container/host. This would force a user to remove either the monitor or OSDs , preventing a reboot from destroying the node. In a perfect world, ceph-osd would notice that it is connecting to an old monitor and politely disconnect without destroying all it's OSDs. For now, however, I suggest some sort of stop-gap measure that prevents users from nuking their cluster without warning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874939 Title: ceph-osd can't connect after upgrade to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1874939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879893] Autopkgtest regression report (xorg-server/2:1.20.8-2ubuntu2.1)
All autopkgtests for the newly accepted xorg-server (2:1.20.8-2ubuntu2.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: gscan2pdf/2.6.4-1 (s390x) openjdk-8/8u252-b09-1ubuntu1 (armhf) apport/2.20.11-0ubuntu27 (amd64) jsunit/0.2.2-2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#xorg-server [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879893 Title: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
