[Bug 1871685] Re: vagrant spits out ruby deprecation warnings on every call
** Patch added: "full merge debdiff from old ubuntu version to new ubuntu version" https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+attachment/5356998/+files/lp1871685_complete-merge_2.2.6+dfsg-2ubuntu1_2.2.7+dfsg-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: vagrant spits out ruby deprecation warnings on every call
** Patch added: "partial merge debdiff showing only the delta to current debian version" https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+attachment/5356999/+files/lp1871685_merge-only_2.2.7+dfsg-1_2.2.7+dfsg-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872588] Re: Please remove pyrit from Ubuntu
wifite (2.5.2-3) unstable; urgency=medium * Team upload. * Drop pyrit from autopkgtest deps (Closes: #956277) -- Raphaƫl Hertzog Fri, 10 Apr 2020 11:49:07 +0200 Removing packages: pyrit 0.5.1+git20180801-2ubuntu1 in focal pyrit 0.5.1+git20180801-2ubuntu1 in focal amd64 pyrit 0.5.1+git20180801-2ubuntu1 in focal arm64 pyrit 0.5.1+git20180801-2ubuntu1 in focal armhf pyrit 0.5.1+git20180801-2ubuntu1 in focal ppc64el pyrit 0.5.1+git20180801-2ubuntu1 in focal riscv64 pyrit 0.5.1+git20180801-2ubuntu1 in focal s390x pyrit-dbgsym 0.5.1+git20180801-2ubuntu1 in focal amd64 pyrit-dbgsym 0.5.1+git20180801-2ubuntu1 in focal arm64 pyrit-dbgsym 0.5.1+git20180801-2ubuntu1 in focal armhf pyrit-dbgsym 0.5.1+git20180801-2ubuntu1 in focal ppc64el pyrit-dbgsym 0.5.1+git20180801-2ubuntu1 in focal riscv64 pyrit-dbgsym 0.5.1+git20180801-2ubuntu1 in focal s390x Comment: (From Debian) ROM; no python 3 version in sight; Debian bug #955344 Remove [y|N]? y ** Changed in: pyrit (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872588 Title: Please remove pyrit from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyrit/+bug/1872588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: vagrant spits out ruby deprecation warnings on every call
Please sponsor this upload of a merge of Vagrant 2.2.7+dfsg-1 from Debian. It is a minor upstream version bump (2.2.6 -> 2.2.7) plus contains new patches from Debian to fix multiple Ruby 2.7 deprecation warnings on every command invocation. Two debdiffs attached: partial merge debdiff showing only the delta to current debian version (lp1871685_merge-only_2.2.7+dfsg-1_2.2.7+dfsg-1ubuntu1.debdiff) full merge debdiff from old ubuntu version to new ubuntu version (lp1871685_complete-merge_2.2.6+dfsg-2ubuntu1_2.2.7+dfsg-1ubuntu1.debdiff) This is a direct merge of the previous merge, which is simply to disable the autopkgtest as it is long time known flakey on Ubuntu infrastructure. It would be ideal to get this merge through ahead of Focal release to continue having no delta to Debian upstream. This package is in universe. ** Changed in: vagrant (Ubuntu) Status: New => Confirmed ** Changed in: vagrant (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873731] [NEW] i have upgrade from ubuntu 18.04 . most libraries are not upgrade i.e gcc-10-base. multiple library are not install and when i try to install them. error will generate that gcc-10-
Public bug reported: lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $apt-cache policy gcc-10-base gcc-10-base: Installed: 10-20200416-0ubuntu1~18.04 Candidate: 10-20200416-0ubuntu1~18.04 Version table: *** 10-20200416-0ubuntu1~18.04 100 100 /var/lib/dpkg/status 10-20200411-0ubuntu1 500 500 http://repo.isra.edu.pk/ubuntu focal/main amd64 Packages I have upgrade from ubuntu 18.04. most libraries are not upgraded i.e GCC-10-base. multiple libraries are not installed and when I try to install them. error will generate that GCC-10-base 2020-04 required but 18.04 is installed. I have remove all absolute packages and replace all packages. when I try to remove GCC-10-base or reinstall then the error is generated. multiple packages have broken during up-gradation. ``` reading package lists... Done Building dependency tree Reading state information... Done Reinstallation of gcc-10-base is not possible, it cannot be downloaded. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.``` ``` The following packages have unmet dependencies: libfcl-dev : Depends: libflann-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` I have continued to add missing packages in the list. but at the end following the problem raises. ``` sudo apt install gcc-10-base libgcc-10-dev gcc-10 libgfortran-10-dev libgfortran5 gfortran-10 libhdf5-openmpi-103 libopenmpi-dev libopenmpi-dev libhdf5-openmpi-dev mpi-default-dev libhdf5-mpi-dev libflann-dev libfcl-dev Reading package lists... Done Building dependency tree Reading state information... Done gcc-10-base is already the newest version (10-20200416-0ubuntu1~18.04). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gcc-10 : Depends: cpp-10 (= 10-20200411-0ubuntu1) but it is not going to be installed Depends: gcc-10-base (= 10-20200411-0ubuntu1) but 10-20200416-0ubuntu1~18.04 is to be installed gfortran-10 : Depends: gcc-10-base (= 10-20200411-0ubuntu1) but 10-20200416-0ubuntu1~18.04 is to be installed libgcc-10-dev : Depends: gcc-10-base (= 10-20200411-0ubuntu1) but 10-20200416-0ubuntu1~18.04 is to be installed Depends: libasan6 (>= 10-20200411-0ubuntu1) but it is not going to be installed libgfortran-10-dev : Depends: gcc-10-base (= 10-20200411-0ubuntu1) but 10-20200416-0ubuntu1~18.04 is to be installed libgfortran5 : Depends: gcc-10-base (= 10-20200411-0ubuntu1) but 10-20200416-0ubuntu1~18.04 is to be installed E: Unable to correct problems, you have held broken packages. ``` I am going to remove but ubuntu say ``` sudo apt remove gcc-10-base Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgcc-s1 : Depends: gcc-10-base (= 10-20200416-0ubuntu1~18.04) but it is not going to be installed libxml2 : Depends: libicu66 (>= 66.1-1~) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. $sudo apt install doxygen Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libxapian30 Suggested packages: doxygen-latex doxygen-doc doxygen-gui graphviz xapian-tools The following NEW packages will be installed: doxygen libxapian30 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 661 kB/10.3 MB of archives. After this operation, 46.1 MB of additional disk space will be used. Do you want to continue? [Y/n] y Err:1 http://repo.isra.edu.pk/ubuntu focal/universe amd64 libxapian30 amd64 1.4.14-2 404 Not Found [IP: 121.52.154.237 80] E: Failed to fetch http://repo.isra.edu.pk/ubuntu/pool/universe/x/xapian-core/libxapian30_1.4.14-2_amd64.deb 404 Not Found [IP: 121.52.154.237 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? ``` I expected after degradation all packages must upgrade into ubuntu 20.04. but multiple packages have not upgraded even I have replaced all packages and remove all old and absolute packages. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64
[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Doug, this was fixed by including the missing i386 packages in a newer image. What image did you see this issue with? You need to be using the latest daily image to get the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
I had this installer crash just now. (Apr 19, 2020) * Computer: MSI GT72 6QD laptop, 16MB RAM, Nvidia GTX970M video. Installing to a 1TB SATA SSD drive. * Used the installation option to use Internet connection to install third-party software (wired Ethernet connection to router) * Already have Ubuntu Studio 19.10 and Windows 10 on a separate PCI-E SSD. Note: I got thru the partitioning section, login name setup, and the installer progress showed being about 3/4 done (installing system message) when the crash occurred. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873728] Re: install on power server with excessive disks fails Invalid dep_id
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Also affects: subiquity Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** No longer affects: subiquity (Ubuntu) ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Also affects: curtin Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Foundations Team (canonical-foundations) ** Tags added: installer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873728 Title: install on power server with excessive disks fails Invalid dep_id To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1873728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Same here for a while now, really annoying $ inxi -SCGxxxz System:Host: Slenvy Kernel: 5.3.0-46-generic x86_64 bits: 64 gcc: 7.5.0 Desktop: Gnome 3.28.4 (Gtk 3.22.30-1ubuntu4) info: gnome-shell dm: gdm3 Distro: Ubuntu 18.04.4 LTS CPU: Quad core Intel Core i7-8550U (-MT-MCP-) arch: Kaby Lake rev.10 cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15999 clock speeds: min/max: 400/4000 MHz 1: 796 MHz 2: 799 MHz 3: 799 MHz 4: 799 MHz 5: 796 MHz 6: 799 MHz 7: 798 MHz 8: 795 MHz Graphics: Card-1: Intel UHD Graphics 620 bus-ID: 00:02.0 chip-ID: 8086:5917 Card-2: NVIDIA GP108M [GeForce MX150] bus-ID: 01:00.0 chip-ID: 10de:1d10 Display Server: x11 (X.Org 1.20.5 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) version: 4.5 Mesa 19.2.8 (compat-v: 3.0) Direct Render: Yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861655] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2020-04-20 01:11 EDT--- (In reply to comment #39) > Well, I assume that a new LP bug needs to be raised in this case, since the > initial NVMe problem seems to be gone. > We'll check with the very latest image (timestamp April 16) - that came out > very late yesterday (my day). I checked the 'Custom storage layout' on the 0417 pending ISO (20.04.1+git19.3bd1382b still) and it worked ok. That still is the current pending ISO, but I'll retry it as the new one gets available and open a new issue if I recreate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861655 Title: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873728] Re: install on power server with excessive disks fails Invalid dep_id
** Package changed: debian-installer (Ubuntu) => subiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873728 Title: install on power server with excessive disks fails Invalid dep_id To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1873728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873441] Re: modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory
added to git ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-oem-5.6 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873441 Title: modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1873441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873713] Re: appstreamcli: symbol lookup error: appstreamcli: undefined symbol: AS_APPSTREAM_METADATA_PATHS
I didn't include a specific package because I didn't know how to find it (I ran apt and got the error I posted, but I wasn not installing one package by myself, instead it was part of the upgrade to Ubuntu 20.04). I finally solved this bug by a series of: apt upgrade apt dist-upgrade ... apt upgrade apt dist-upgrade Each one was failing for a different reason, but doing some progress as each time the list of changes was smaller. Finally they converged and my system got up to date. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873713 Title: appstreamcli: symbol lookup error: appstreamcli: undefined symbol: AS_APPSTREAM_METADATA_PATHS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1873713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873713] Re: appstreamcli: symbol lookup error: appstreamcli: undefined symbol: AS_APPSTREAM_METADATA_PATHS
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1873713/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873713 Title: appstreamcli: symbol lookup error: appstreamcli: undefined symbol: AS_APPSTREAM_METADATA_PATHS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1873713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: vagrant spits out ruby deprecation warnings on every call
I was wrong this package requires a merge due to a small delta on the upstream Debian package. So I will have to prepare a patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873670] Re: python3-mapnik not working due to stale icu65: refernces
The attachment "lp1873670_mapnik_icu66.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873670 Title: python3-mapnik not working due to stale icu65: refernces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-mapnik/+bug/1873670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: vagrant spits out ruby deprecation warnings on every call
This has been fixed in a new Debian Release (2.2.7+dfsg-1). Tested a package built on Focal and these warnings go away. Specifically they added two patches: 0006-Fix-warnings-for-ruby-2.7.patch 0007-Fix-more-warnings-under-ruby-2.7.patch Since this is in universe but a popular too, hoping we can sneak in a Debian sync for Focal with the new version as well to fix this otherwise I can look to submit a patch for the warnings specifically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
** Merge proposal linked: https://code.launchpad.net/~hloeung/content-cache-charm/+git/content-cache-charm/+merge/382557 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873727] [NEW] apport results for bug 1873523
Public bug reported: trying to post this info to a current bug number 1873523 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-lowlatency 5.4.27 Uname: Linux 5.4.0-21-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Apr 20 00:13:15 2020 InstallCmdLine: file=/cdrom/preseed/ubuntustudio.seed only-ubiquity initrd=/casper/initrd quiet splash --- InstallationDate: Installed on 2020-04-17 (2 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873727 Title: apport results for bug 1873523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1873727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863752] Re: Removal of linux-image-5.3.0-29-generic fails
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863752 Title: Removal of linux-image-5.3.0-29-generic fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863973] Re: snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings
[Expired for linux (Ubuntu Eoan) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863973 Title: snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863939] Re: Linux 5.4.0-14 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4.0 from mainline PPA does boot
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863939 Title: Linux 5.4.0-14 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4.0 from mainline PPA does boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863761] Re: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863761 Title: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873728] [NEW] install on power server with excessive disks fails Invalid dep_id
Public bug reported:
== Comment: #0 - Michael Ranweiler - 2020-04-17 17:21:49
==
We have a p9 boston with a number of multipath disks. The install fails here
before even configuring the storage. There's no error displayed on screen
before the error/report screen. There's a lot of LVM volumes on the system,
from the log file:
2020-04-17 21:26:20,232 ERROR root:39 finish:
subiquity/Filesystem/_probe/probe_once: FAIL: Invalid dep_id
(disk-mpath-360050768028211d8b062) not in storage config
2020-04-17 21:26:20,232 ERROR block-discover:151 block probing failed
restricted=False
Traceback (most recent call last):
File
"/snap/subiquity/1705/lib/python3.6/site-packages/subiquity/controllers/filesystem.py",
line 144, in _probe
self._probe_once_task.task, 15.0)
File "/snap/subiquity/1705/usr/lib/python3.6/asyncio/tasks.py", line 358, in
wait_for
return fut.result()
File
"/snap/subiquity/1705/lib/python3.6/site-packages/subiquity/controllers/filesystem.py",
line 124, in _probe_once
self.model.load_probe_data(storage)
File
"/snap/subiquity/1705/lib/python3.6/site-packages/subiquity/models/filesystem.py",
line 1556, in load_probe_data
self.reset()
File
"/snap/subiquity/1705/lib/python3.6/site-packages/subiquity/models/filesystem.py",
line 1274, in reset
self._probe_data)["storage"]["config"]
File
"/snap/subiquity/1705/lib/python3.6/site-packages/curtin/storage_config.py",
line 1317, in extract_storage_config
tree = get_config_tree(cfg.get('id'), final_config)
File
"/snap/subiquity/1705/lib/python3.6/site-packages/curtin/storage_config.py",
line 275, in get_config_tree
for dep in find_item_dependencies(item, sconfig):
File
"/snap/subiquity/1705/lib/python3.6/site-packages/curtin/storage_config.py",
line 245, in find_item_dependencies
_validate_dep_type(item_id, dep_key, dep, config)
File
"/snap/subiquity/1705/lib/python3.6/site-packages/curtin/storage_config.py",
line 193, in _validate_dep_type
'Invalid dep_id (%s) not in storage config' % dep_id)
ValueError: Invalid dep_id (disk-mpath-360050768028211d8b062) not
in storage config
2020-04-17 21:26:20,234 INFO subiquity.core:436 saving crash report 'block
probing crashed with ValueError' to
/var/crash/1587158780.234095097.block_probe_fail.crash
** Affects: debian-installer (Ubuntu)
Importance: Undecided
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Status: New
** Tags: architecture-ppc64le bugnameltc-185357 severity-high
targetmilestone-inin---
** Tags added: architecture-ppc64le bugnameltc-185357 severity-high
targetmilestone-inin---
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873728
Title:
install on power server with excessive disks fails Invalid dep_id
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1873728/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860367] Re: New kernel 5.3 doesn't recognize older NVIDIA graphics card
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860367 Title: New kernel 5.3 doesn't recognize older NVIDIA graphics card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1860367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873728] tarball of installer, etc, log files
Default Comment by Bridge ** Attachment added: "tarball of installer, etc, log files" https://bugs.launchpad.net/bugs/1873728/+attachment/5356983/+files/instlogs.tgz ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => debian-installer (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873728 Title: install on power server with excessive disks fails Invalid dep_id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1873728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863973] Re: snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings
[Expired for linux (Ubuntu Focal) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863973 Title: snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1863434 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873725] [NEW] Folder under applications menu doesn't show text below last line of icons.
Public bug reported: Under the applications menu the "Utilities" folder does not show the last line of text below the icons. If you launch one of the applications on the last line ie terminal then it will reveal the text below the icon. Description:Ubuntu 20.04 LTS Release:20.04 nautilus: Installed: 1:3.36.1.1-1ubuntu2 Candidate: 1:3.36.1.1-1ubuntu2 Version table: *** 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 22:46:39 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "photo_2020-04-19_22-39-08.jpg" https://bugs.launchpad.net/bugs/1873725/+attachment/5356975/+files/photo_2020-04-19_22-39-08.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873725 Title: Folder under applications menu doesn't show text below last line of icons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873724] [NEW] Clipit unable to open preferences
Public bug reported: Clicking on Clipit icon, choosing "Preferences" - nothing happens, preferences window do not open. There is just a rectangle in the upper left corner which can not be used (transparent, unable to click) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: clipit 1.4.4+git20190202-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 19:11:43 2020 InstallationDate: Installed on 2020-04-01 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) SourcePackage: clipit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: clipit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - Clipt unable to open preferences + Clipit unable to open preferences -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873724 Title: Clipit unable to open preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/1873724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
There's a surprising number of clipboard fixes already landed upstream and waiting to be released in mutter 3.36.2 -- we should probably wait and see if they help. Most of them don't have associated bug reports :/ Also, in case you haven't already please try both 'Ubuntu' and 'Ubuntu on Wayland'. In case one works better than the other. It looks like some upstream fixes are specific to one or the other. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1872527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
** Tags added: hwe-bluetooth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
*** This bug is a duplicate of bug 1872527 *** https://bugs.launchpad.net/bugs/1872527 Actually this sounds related to bug 1872527. Maybe we should just use that for now. ** This bug has been marked a duplicate of bug 1872527 Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed ** Tags removed: cosmic disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868519 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1868519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers (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/1868519 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1868519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873266] Re: cannot change main monitor after setting scaling for monitors w/nvidia drivers
"screens go black" reminds me of bug 1873403 which might be somehow related. ** Summary changed: - cannot change main monitor after setting scaling for monitors w/nvidia drivers + [nvidia] cannot change main monitor after setting scaling for monitors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873266 Title: [nvidia] cannot change main monitor after setting scaling for monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872971] Re: Xorg crash
*** This bug is a duplicate of bug 1868519 *** https://bugs.launchpad.net/bugs/1868519 ** This bug has been marked a duplicate of private bug 1873195 ** This bug is no longer a duplicate of private bug 1873195 ** This bug has been marked a duplicate of bug 1868519 [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872971 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1872971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873266] Re: [nvidia] cannot change main monitor after setting scaling for monitors
Can you please look in Settings > Screen Display and tell us if 'Fractional Scaling' is enabled? ** Changed in: mutter (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/1873266 Title: [nvidia] cannot change main monitor after setting scaling for monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
Jumping in on this bug as well. Installed the daily from April 18, 2020 on a Lenovo Thinkpad T440s and had the same issue. After installing I had no grub boot menu upon rebooting. I edited /etc/default/grub and changed a few lines but that didn't seem to work. I also tried to reinstall grub but that didn't work either. Package: grub-efi-amd64 Version: 2.04-1ubuntu26 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873716] Re: Information on how to report a bug is incorrect
Thanks for your report! Something is apparently wrong here. ** Changed in: ubuntu-docs (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-docs (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-docs (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873716 Title: Information on how to report a bug is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1873716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
Sounds like this might be a kernel bug, or a hardware problem. I am skeptical of CSR Bluetooth dongles since they seem to be consistently unreliable, at least on Linux. Please try a newer (or older) kernel version and tell us if that makes any difference: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D Or more simply just try live booting Ubuntu 20.04 from USB and tell us if that has the same bug: http://cdimage.ubuntu.com/daily-live/current/ Ubuntu 20.04 is due for release at the end of this week. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** 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/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873670] Re: python3-mapnik not working due to stale icu65: refernces
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-mapnik (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/1873670 Title: python3-mapnik not working due to stale icu65: refernces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-mapnik/+bug/1873670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873670] Re: python3-mapnik not working due to stale icu65: refernces
= Test Case = Simple test case per upstream docs: python3 -c "import mapnik;print(mapnik.__file__)" # should return the path to the python bindings and no errors Fails with the current package (1:0.0~20180723-588fc9062-3ubuntu2) - works with a no-change rebuilt package ** Changed in: python-mapnik (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873670 Title: python3-mapnik not working due to stale icu65: refernces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-mapnik/+bug/1873670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873670] Re: python3-mapnik not working due to stale icu65: refernces
A no-change rebuild seems to correct this ** Patch added: "lp1873670_mapnik_icu66.debdiff" https://bugs.launchpad.net/ubuntu/+source/python-mapnik/+bug/1873670/+attachment/5356971/+files/lp1873670_mapnik_icu66.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873670 Title: python3-mapnik not working due to stale icu65: refernces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-mapnik/+bug/1873670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873719] Re: Relatar
Please explain in more detail what kind of problem you are having. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1873719 Title: Relatar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1873719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
Now we are getting somewhere. X windows system implicated. Though the 2d video shows how fast the shortcut boot is, I thought I should get a firm number so I did the shortcut boot and logged in to get output of 'systemd-analyze critical- chain' and I got the following very interesting responses, shell dialogue copied below. The same processes (I would assume) are hanging for 1m44s, but the shortcut somehow allows the user to log in while waiting for them to finish (as well as solving the other problems of clipboard and screen size, which seem to go with the more primitive login screen). Whether those processes should take 1m44s or not, I don't know, maybe it is normal, but the user should be able to log in before they are complete, as I can do with shortcut boot. If those processes are taking inordinately long, then shortcut boot gives opportunity to log in and catch them as they struggle, as seen below. The time I had to wait to get the critical-chain result was about as long as I had to wait to log in at all, under stock 19.10 without shortcut-boot procedure: wift@stock19:~$ sudo -i [sudo] password for swift: root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# systemctl list-jobs JOB UNIT TYPE STATE 48 setvtrgb.service start waiting 137 system-getty.slice start waiting 1 graphical.target start waiting 102 systemd-update-utmp-runlevel.service start waiting 83 plymouth-quit-wait.service start running 2 multi-user.targetstart waiting 6 jobs listed. root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# date Sun 19 Apr 2020 10:50:27 PM EDT root@stock19:~# systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 44.881s āāmulti-user.target @1min 44.881s āāxrdp.service @1.496s +1.036s āāxrdp-sesman.service @1.474s +20ms āānetwork.target @1.470s āāNetworkManager.service @1.381s +88ms āādbus.service @1.379s āābasic.target @1.375s āāsockets.target @1.375s āāsnapd.socket @1.373s +1ms āāsysinit.target @1.372s āāsystemd-timesyncd.service @1.175s +196ms āāsystemd-tmpfiles-setup.service @1.160s +10ms āālocal-fs.target @1.158s āāhome-swift-shared\x2ddrives.mount @11.731s āālocal-fs-pre.target @177ms āālvm2-monitor.service @116ms +61ms āādm-event.socket @115ms āāsystem.slice @110ms āā-.slice @110ms root@stock19:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873720] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1873720 Title: Failed to boot after upgrade due to video driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873718] [NEW] CSR8510 based BTA-402 Bluetooth device cannot be started
Public bug reported: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873720] [NEW] Failed to boot after upgrade due to video driver
Public bug reported: When I upgraded my system to 20.04, the boot sequence hung. When I changed my GRUB to include nomodeset, things booted up fine, but not much functionality for my display. I finally added modeprobe.blacklist=nouveau in order to get the machine to boot and get more display functionality. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: compat ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1606 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 19:33:29 2020 IwConfig: wlp60s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. VFS7552 Touch Fingerprint Sensor Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9365 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=88bc2510-1184-416f-8e62-077047a331e7 ro quiet splash modeprobe.blacklist=nouveau vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-18 (2 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 02MV1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.0:bd11/08/2019:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn02MV1F:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9365 dmi.product.sku: 077A dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873720 Title: Failed to boot after upgrade due to video driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873719] [NEW] Relatar
Public bug reported: Relatar erro na execuĆ§Ć£o Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Apr 19 23:33:32 2020 DistUpgraded: 2020-04-18 10:05:27,584 DEBUG icon theme changed, re-reading DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: intel-hid, 3.1, 4.4.0-177-generic, x86_64: installed oem-wifi-ath9k-msi, 1, 4.4.0-177-generic, x86_64: installed oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1, 4.4.0-177-generic, x86_64: installed radeon-si, 1a, 4.4.0-38-generic, x86_64: built ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:078c] InstallationDate: Installed on 2019-08-18 (246 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=10e0a602-865d-4c14-bc06-438dbffafffc ro locale=pt_BR alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-04-18 (1 days ago) dmi.bios.date: 07/17/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.0 dmi.board.name: 06J0HF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.0:bd07/17/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn06J0HF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Apr 18 01:24:06 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 29164 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873719 Title: Relatar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1873719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
I've created a 2m35s desktop video showing a boot of stock 18.04 and
19.10 on my system, posted at https://chaetura.net/ms-
vid1-bug-1848534.webm (18MB, renders in Chrome window for me, or use VLC
to watch).
I've posted a second video showing the shortcut to boot 19.10 quickly
that I described earlier, but which I have simplified to simply pulling
the plug with "power off" from Hyper-V at the grub menu, do not close
the Connection window, restart, and 19.10 will boot fast. Note that
"system setup" (I previously mistakenly wrote "system startup") doesn't
appear in the grub menu of stock 19.10; it appears only after updating
packages in Ubuntu. Yes, I am able to select the ārestartā button with
the keyboard. But then the shortcut doesnāt work; what triggers the
shortcut is powering off the VM.
https://chaetura.net/ms-vid2-bug-1848534.webm
Furthermore, the shortcut boot of 19.10 solves *THREE* significant
problems with stock 19.10 that are not problems with stock 18.04.3.
Reasonable conclusion is that all three problems have the same cause,
which somehow the shortcut boot avoids:
1) avoids the long delay in startup
2) allows user to select any screen size for the Connection (whereas
stock 19.10 came in one size only and user has no opportunity to select;
goes hand in hand with the different login screen, as you can see in
video.
3) after login, cut-and-paste from guest to host is possible. Not
functional with stock 19.10.
I see that graphical artifact at some point during boot of any Ubuntu VM
in Hyper-V. You can see it in the video too. In 19.10 it comes while the
Spectre mitigation message is on the screen in console, at a point where
console changes its rendering/mode somehow and the message reappears in
a slightly different font.
I forgot to show /proc/cmdline and "uname -a" in the video but for 19.10
it is:
BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=PARTUUID=[blahblah] ro quiet
splash
Linux stock19 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
and in 18.04.3 it is
BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=LABEL=desktop-rootfs ro
quiet splash vt.handoff=1
Linux stock18 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Note that I installed my 19.10 via Hyper-V Manager's "quick-create"
rather than from an .iso downloaded separately. Same kernel version, but
mine is an earlier packaging number, and who knows what else may be
different about the install image. The manager says the image was
updated 17 October 2019. The Manager downloads a zip file from partner-
images.canonical.com via https so I cannot snoop the URL looking at the
packets. I have a copy of the .vhdx which is insie the zip file, and I'm
messing around with trying to mount it in another VM but I haven't
solved that yet.
My Windows 10 Pro x64 build (today) is Win10: Version 1909 (OS Build
18363.778). No further windows updates are available, and I don't
understand Windows version numbers, so I can't explain the discrepancy
from yours.
The startup delay persists after updating the stock install of 19.10
(using aptitude; all available updates accepted but the grub packages
held back till I learn how to do them; they broke my last install).
I noticed while making the video that during the long startup delay, the
process is using GPU at 5% -- significant amount of usage (documented in
video). Therefore I've included my GPU information at bottom below.
I boot stock quick-create 19.10. I change the name of the VM only
("Stock19"). Default ethernet adapter. Note that the first boot is
immediate; the only one that will ever be that fast, unless I go through
the shortcut boot sequence. On first boot, I go through Ubuntu
configuration screens minimally. Post-install runs. No further updates,
just reboot now (because critical-chain timings are much longer the
first boot than all subsequent boots). Login, run terminal, sudo-i, then
systemd-analyze critical-chain:
first line is: graphical.target @1min 44.651s
This is typical of all subsequent boots.
I'm not copying the full output all because cut-and-paste text from
guest to host is broken for me in 19.10. It is not broken in an 18.04.3
guest ("updated 19 August 2019" in Hyper-V Manager).
Here for comparison is the critical-chain for 18.04, which I can cut-
and-paste. Less than 2s to "graphical.target", compared with 104s for
19.10.
swift@Riflebird:~$ sudo -i
[sudo] password for swift:
root@Riflebird:~# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @1.836s
āāmulti-user.target @1.836s
āākerneloops.service @1.829s +6ms
āānetwork-online.target @1.827s
āāNetworkManager-wait-online.service @663ms +1.163s
āāNetworkManager.service @566ms +96ms
āādbus.service @538ms
āābasic.target
[Bug 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423773 Title: Gnome-Shell don't free ram when I change a wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD
@vicamo, did this failure (comment#23) only happen this v5 patch? We did successfully aplly the earlier (v3?) patch, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873716] [NEW] Information on how to report a bug is incorrect
Public bug reported: I'm trying to report a bug about my Bluetooth dongle. I googled and was directed to https://help.ubuntu.com/stable/ubuntu-help/report-ubuntu-bug.html.en for direction on how to do so. I followed the instructions on that page, but they do not work: 1. I run ubuntu-bug without arguments since I don't know which program to report against. 2. A menu shows up asking me what kind of problem I would like to report. 3. I choose the only vaguely matching option "Other Problem" 4. ubuntu-bug aborts with an error message that I need to choose a package. There was nothing in the instructions about a package and in any case (while I can guess I should maybe report it against bluez), most people wouldn't know which package to choose anymore than what program is involved. Another menu entry for "hardware" or something of the sort would be useful. ** Affects: ubuntu-docs (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/1873716 Title: Information on how to report a bug is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1873716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771559] Fix proposed to horizon (stable/train)
Fix proposed to branch: stable/train Review: https://review.opendev.org/721138 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771559 Title: error while loading icon with pyscss 1.3.5 or later To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1771559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873441] Re: modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory
** Tags added: oem-priority originate-from-1873553 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873441 Title: modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1873441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873714] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1873714 Title: Computer freeze on application change / memory allocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873714] [NEW] Computer freeze on application change / memory allocation
Public bug reported: Experience behaviour: The system freezes for about 10 seconds often when - I change applications - I open applications - switch tabs in firefox - open new web pages - draw in GIMP with pen tablet Average occurance: - every 1 - 4 minutes // usual PC usage - every 30 seconds // when drawing in GIMP with pen tablet Reproducability: always My guess is: The system freezes, when memory management is done. Additional information: - 5.3.0-40-generic had none of these problems - 5.3.0-45-generic had similar problems, but instead of freezing for 10 seconds, the system would just freeze forever. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 1588 F pulseaudio /dev/snd/pcmC0D3p: nimono 1588 F...m pulseaudio /dev/snd/pcmC0D0c: nimono 1588 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Apr 20 11:19:29 2020 MachineType: FUJITSU FMVWB3U27 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-12-01 (141 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873714 Title: Computer freeze on application change / memory allocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper
** Tags added: leak ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423773 Title: Gnome-Shell don't free ram when I change a wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873700] Re: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
Thanks for the clarification. Can you please report that second "real" issue as a new bug by running: ubuntu-bug linux ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873700 Title: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
I've created a 2m35s desktop video showing a boot of stock 18.04 and
19.10 on my system, posted at https://chaetura.net/ms-
vid1-bug-1848534.webm (18MB, renders in Chrome window for me, or use VLC
to watch).
I've posted a second video showing the shortcut to boot 19.10 quickly
that I described earlier, but which I have simplified to simply pulling
the plug with "power off" from Hyper-V at the grub menu, do not close
the Connection window, restart, and 19.10 will boot fast. Note that
"system setup" (I previously mistakenly wrote "system startup") doesn't
appear in the grub menu of stock 19.10; it appears only after updating
packages in Ubuntu.
Furthermore, the shortcut boot of 19.10 solves *THREE* significant
problems with stock 19.10 that are not problems with stock 18.04.3:
1) avoids the long delay in startup
2) allows user to select any screen size for the Connection (whereas stock
19.10 came in one size only
and user has no opportunity to select; goes hand in hand with the
different login screen, as you
I see that graphical artifact at some point during boot of any Ubuntu VM in
Hyper-V. You can see it in the video too. In 19.10 it comes while the Spectre
mitigation message is on the screen in console, at a point where console
changes its rendering/mode somehow and the message reappears in a slightly
different font.
I forgot to show /proc/cmdline and "uname -a" in the video but for 19.10 it is:
BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=PARTUUID=[blahblah] ro quiet
splash
Linux stock19 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
and in 18.04.3 it is
BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=LABEL=desktop-rootfs ro
quiet splash vt.handoff=1
Linux stock18 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Note that I installed my 19.10 via Hyper-V Manager's "quick-create"
rather than from an .iso downloaded separately. Same kernel version, but
mine is an earlier packaging number, and who knows what else may be
different about the install image. The manager says the image was
updated 17 October 2019. The Manager downloads a zip file from partner-
images.canonical.com via https so I cannot snoop the URL looking at the
packets. I have a copy of the .vhdx which is insie the zip file, and I'm
messing around with trying to mount it in another VM but I haven't
solved that yet.
My Windows 10 Pro x64 build (today) is Win10: Version 1909 (OS Build
18363.778). No further windows updates are available, and I don't
understand Windows version numbers, so I can't explain the discrepancy
from yours.
The startup delay persists after updating the stock install of 19.10
(using aptitude; all available updates accepted but the grub packages
held back till I learn how to do them; they broke my last install).
I noticed while making the video that during the long startup delay, the
process is using GPU at 5% -- significant amount of usage (documented in
video). Therefore I've included my GPU information at bottom below.
I boot stock quick-create 19.10. I change the name of the VM only
("Stock19"). Default ethernet adapter. Note that the first boot is
immediate; the only one that will ever be that fast, unless I go through
the restart sequence described last time. (On that subject, I don't get
the "system setup" grub option in the stock 19.10, only after updates.
You probably figured out I mistakenly wrote "system startup" earlier
instead of "system setup" as well. And yes, keyboard can select
"restart" but in this case, the shortcut does *NOT* work. Only pulling
the plug on the VM from Hyper-V ) On first boot, I go through Ubuntu
configuration screens minimally. Post-install runs. No further updates,
just reboot noq (because critical-chain timings are much longer the
first boot than all subsequent boots). Login, run terminal, sudo-i, then
systemd-analyze critical-chain:
first line is: graphical.target @1min 44.651s
This is typical of all subsequent boots.
I'm not copying the full output all because cut-and-paste text from
guest to host is broken for me in 19.10. It is not broken in an 18.04.3
guest ("updated 19 August 2019" in Hyper-V Manager).
Also in 19.10 I never get the choice of a screen size for the guest when
connecting; it is always the same size. I get the choice in 18.04 and
can choose any size including full-screen, and it just works.
I understand that these other problems with 19.10 guest may be off-
topic; I am mentioning them here in case they correlate to the current
topic. In summary, four significant problems with 19.10 that do not
exist in 18.04, both out of the box quick-create, using same host: 1)
the long delay at startup. 2) no cut-and-paste from guest to host. 3) no
capability to resize Hyper-V Connection screen. 4) requires research to
get past a grub update.
Here for comparison is the critical-chain for 18.04, which I can cut-
and-paste. Less
[Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
A stray click sent my previous message before I had finished editing it, and I see no way to edit my post. I will post fully complete/edited version momentarily. I hope an admin will delete this message and my prior message to avoid cruft in this thread. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873625] Re: Mouse moves at the bottom right of the screen at log-in
This is a "feature" but efforts are underway upstream to change it: https://gitlab.gnome.org/GNOME/mutter/-/issues/651 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #651 https://gitlab.gnome.org/GNOME/mutter/-/issues/651 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/651 Importance: Unknown Status: Unknown ** Summary changed: - Mouse moves at the bottom right of the screen at log-in + Center the mouse cursor at startup ** Changed in: mutter (Ubuntu) Importance: Undecided => Wishlist ** Changed in: mutter (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873625 Title: Center the mouse cursor at startup To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1873625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Using GNOME in the guest isn't removing it from the equation, it's only changing the equation. Actually this could equally be a problem with virt-manager. What happens if both the host and guest are not GNOME? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872121] Re: Sync yubioath-desktop 5.0.2-3 (universe) from Debian unstable (main)
Sorry, s/5.0.2-3/5.0.3-1/g Thanks, Taowa ** Summary changed: - Sync yubioath-desktop 5.0.2-3 (universe) from Debian unstable (main) + Sync yubioath-desktop 5.0.3-1 (universe) from Debian unstable (main) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872121 Title: Sync yubioath-desktop 5.0.3-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yubioath-desktop/+bug/1872121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872121] Re: Sync yubioath-desktop 5.0.2-3 (universe) from Debian unstable (main)
Hello, Please sync yubioath-desktop 5.0.2-3 (universe) from Debian unstable (main). Latest changelog entry: yubioath-desktop (5.0.3-1) unstable; urgency=medium [ Taowa Munene-Tardif ] * New upstream version 5.0.3 * No longer requires root to build -- Taowa Munene-Tardif Thu, 16 Apr 2020 19:00:00 -0400 Thanks, Taowa ** Changed in: yubioath-desktop (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872121 Title: Sync yubioath-desktop 5.0.3-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yubioath-desktop/+bug/1872121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873630] Re: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting.
** Changed in: pulseaudio (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/1873630 Title: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa- ucm.c:2158, function device_add_hw_mute_jack(). Aborting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Note that we don't recommend use of nvidia-drm.modeset=1 for most users because it still results in some bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset And I'm not sure that's even a complete list. So you should be aware of what you're getting into. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
And yes nvidia-drm.modeset=1 will give you back the missing boot animation, but that discussion should stay in bug 1868240. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873712] [NEW] usb/sound module fails to configure USB Audio Interface
Public bug reported: When I connect my PreSonus USB AudioBox 96 to my Ubuntu 18.04LTS desktop via USB2.0 port, dmesg shows the following errors in a loop: ``` [ 8764.468004] usb 1-11: new high-speed USB device number 61 using xhci_hcd [ 8764.516953] usb 1-11: New USB device found, idVendor=194f, idProduct=0303, bcdDevice= 1.12 [ 8764.516955] usb 1-11: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 8764.516957] usb 1-11: Product: AudioBox USB 96 [ 8764.516958] usb 1-11: Manufacturer: PreSonus [ 8764.516959] usb 1-11: SerialNumber: [ 8769.723951] usb 1-11: 1:1: cannot set freq 96000 (v2/v3): err -110 [ 8774.843735] usb 1-11: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 5) [ 8820.921855] usb 1-11: USB disconnect, device number 61 [ 8821.065655] debugfs: Directory '56' with parent 'devices' already present! [ 8821.193535] usb 1-11: new high-speed USB device number 62 using xhci_hcd [ 8821.242166] usb 1-11: New USB device found, idVendor=194f, idProduct=0303, bcdDevice= 1.12 [ 8821.242168] usb 1-11: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 8821.242170] usb 1-11: Product: AudioBox USB 96 [ 8821.242171] usb 1-11: Manufacturer: PreSonus [ 8821.242172] usb 1-11: SerialNumber: [ 8831.417276] usb 1-11: uac_clock_source_is_valid(): cannot get clock validity for id 5 [ 8836.537052] usb 1-11: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 5) [ 8882.615203] usb 1-11: USB disconnect, device number 62 [ 8882.763151] debugfs: Directory '57' with parent 'devices' already present! [ 8882.890909] usb 1-11: new high-speed USB device number 63 using xhci_hcd [ 8882.919108] usb 1-11: device descriptor read/8, error -71 [ 8883.055305] usb 1-11: device descriptor read/8, error -71 [ 8883.163566] debugfs: Directory '58' with parent 'devices' already present! [ 8883.498882] usb 1-11: new high-speed USB device number 64 using xhci_hcd [ 8883.547227] usb 1-11: New USB device found, idVendor=194f, idProduct=0303, bcdDevice= 1.12 [ 8883.547229] usb 1-11: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 8883.547231] usb 1-11: Product: AudioBox USB 96 [ 8883.547232] usb 1-11: Manufacturer: PreSonus [ 8883.547233] usb 1-11: SerialNumber: [ 8883.657682] usb 1-11: USB disconnect, device number 64 ``` I suspect the failure is at this line of the linux kernel. Perhaps a new quirk is required? https://github.com/torvalds/linux/blob/50cc09c18985eacbbd666acfd7be2391394733f5/sound/usb/format.c#L398 The interface is intermittently available as an input source in alsamixer. It will be available for a few seconds, then disappear, reappear, etc. The device works fine on my Windows machine. I've included the output of lsusb -v below. ``` Bus 001 Device 041: ID 194f:0303 PreSonus Audio Electronics, Inc. Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x194f PreSonus Audio Electronics, Inc. idProduct 0x0303 bcdDevice1.12 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 328 bNumInterfaces 6 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Association: bLength 8 bDescriptorType11 bFirstInterface 0 bInterfaceCount 3 bFunctionClass 1 Audio bFunctionSubClass 0 bFunctionProtocol 32 iFunction 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 1 Audio bInterfaceSubClass 1 Control Device bInterfaceProtocol 32 iInterface 16 AudioControl Interface Descriptor: bLength 9 bDescriptorType36 bDescriptorSubtype 1 (HEADER) bcdADC 2.00 bCategory 8 wTotalLength 75 bmControl0x01 Latency control Control (read-only) AudioControl Interface Descriptor: bLength 8 bDescriptorType36 bDescriptorSubtype 10 (CLOCK_SOURCE) bClockID5 bmAttributes 0x03 Internal programmable Clock bmControls 0x07 Clock Frequency Control (read/write)
[Bug 1841145] Re: Impossible de switch user from lock screen on GDM3 18.04
Christian, I'm not sure that's exactly the same as this bug since this bug is about "flicker" and failure to log in, while you refer to "artifacts". It's probably best if you report a new bug for that by running: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841145 Title: Impossible de switch user from lock screen on GDM3 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873713] [NEW] appstreamcli: symbol lookup error: appstreamcli: undefined symbol: AS_APPSTREAM_METADATA_PATHS
Public bug reported: After upgrading from Kubuntu 18.04 to 20.04 I started getting this error: ``` ~ $ sudo apt update Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://security.ubuntu.com/ubuntu focal-security InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:4 https://packages.cloud.google.com/apt cloud-sdk InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease appstreamcli: symbol lookup error: appstreamcli: undefined symbol: AS_APPSTREAM_METADATA_PATHS Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi' E: Sub-process returned an error code ``` Other required information: ``` ~ $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 ``` ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873713 Title: appstreamcli: symbol lookup error: appstreamcli: undefined symbol: AS_APPSTREAM_METADATA_PATHS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1873713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802652] Re: keyboard backlight not working on Asus GM501
I'm trying to break this down further: This block is the set of keys which I've included the byte output for in a reply further back, repeated for clarity. This block is currently not interpreted by the kernel as anything I guess due to the vendor specific page: 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined 0xFF31) 0x09, 0x76, // Usage (0x76) 0xA1, 0x01, // Collection (Application) 0x85, 0x5A, // Report ID (90) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x05, // Report Count (5) 0x81, 0x00, // Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x3F, // Report Count (63) 0xB1, 0x00, // Feature (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile) 0xC0, // End Collection while the ROG key gives: [90, 56, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Fan: [90, 174, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Backlight-off: [90, 53, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Backlight-down: [90, 16, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Backlight-up: [90, 32, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Touchpad-toggle: [90, 107, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Sleep: [90, 108, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Airplane-toggle: [90, 136, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Keyboard backlight up: [90, 196, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Keyboard backlight down: [90, 197, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Aura-prev: [90, 178, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Aura-next: [90, 179, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] This block is functioning fine as a consumer device: 0x05, 0x0C, // Usage Page (Consumer) 0x09, 0x01, // Usage (Consumer Control) 0xA1, 0x01, // Collection (Application) 0x85, 0x02, // Report ID (2) 0x19, 0x00, // Usage Minimum (Unassigned) 0x2A, 0x3C, 0x02, // Usage Maximum (AC Format) 0x15, 0x00, // Logical Minimum (0) 0x26, 0x3C, 0x02, // Logical Maximum (572) 0x75, 0x10, // Report Size (16) 0x95, 0x02, // Report Count (2) 0x81, 0x00, // Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0xC0, // End Collection This block has I/O. 0x5D, // Report ID (93) is the LED backlight for the keyboard. The Backlight controller I think writes back the input data. 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined 0xFF31) 0x09, 0x79, // Usage (0x79) 0xA1, 0x01, // Collection (Application) 0x85, 0x5D, // Report ID (93) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x1F, // Report Count (31) 0x81, 0x00, // Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x3F, // Report Count (63) 0x91, 0x00, // Output (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x3F, // Report Count (63) 0xB1, 0x00, // Feature (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile) 0xC0, // End Collection I don't know what this block is. HID descriptors are a little confusing to look at: 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined 0xFF31) 0x09, 0x80, // Usage (0x80) 0xA1, 0x01, // Collection (Application) 0x85, 0x5E, // Report ID (94) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x05, // Report Count (5) 0x81, 0x00, // Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position) 0x19, 0x00, // Usage Minimum (0x00) 0x2A, 0xFF, 0x00, // Usage Maximum (0xFF)
[Bug 1808060] Re: libmirclient causes multiarch SDL2 headers to conflict with each other
worsk great. thanks. anyway, this should be fixed automaticaly :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808060 Title: libmirclient causes multiarch SDL2 headers to conflict with each other To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1808060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873700] Re: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
Sorry - not a total noob here, but enough to embarrass myself... I had to boot with "nomodeset" in order to get my machine to boot. That caused the situation I described here. When I blacklisted the nouveau video driver, I got my functionality back. For those who know better how to fix these things - the real problem is that the nouveau driver didn't work on my XPS 13 9365, causing it to hang while trying to boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873700 Title: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions
I have a feeling you are right that it may not be gnome-control-center doing this as setting the default value of show-banners in /usr/share/glib2.0/schemas to false ends up being ignored at login. It is unclear to me what the desired behaviour is from those discussions, but my expectation is that an exposed user setting will stay set until I unset it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873692 Title: Do Not Disturb setting does not persist across login sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871049] Re: FFe: darktable 2.6.3 in focal needs update to 3.0.1
At this point, it is impossible to get an update to 3.0.2 into the Ubuntu archives. Final Freeze happened on Thursday, which means nothing enters or leaves the archives aside minor bugfixes for known bugs. This "update" also includes some new features (meaning the version bump should've been more significant than a meer bugfix "point release"), meaning it would absolutely not be allowed as Feature Freeze Exceptions aren't allowed after Final Freeze. I'm afraid that due to the new features, even a Stable Release Update is out of the question as those are simply for bugfixes. That said, I might be able to backport it into the Ubuntu Studio Backports PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871049 Title: FFe: darktable 2.6.3 in focal needs update to 3.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/1871049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873700] Re: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873700 Title: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816653] Re: Memory Leak
Possible duplicate: bug #1620060 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816653 Title: Memory Leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1816653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871049] Re: FFe: darktable 2.6.3 in focal needs update to 3.0.1
FWIW, Upstream and Debian-"unstable" have now released 3.0.2 ... May be worth Updating now, in any-case keep an eye on upstream bug-fixes ongoing... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871049 Title: FFe: darktable 2.6.3 in focal needs update to 3.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/1871049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816653] Re: Memory Leak
Gthumb 3.8, browsing in a directory with >1300 pictures, mixture of webp and jpeg. Gthumb consumes all RAM (32GB), causing system to stutter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816653 Title: Memory Leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1816653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872546] Re: ipmi-oem dell reset-power-consumption-data , timezones, and reporting peak amp times in the future
nevermind, the correct option is --otc-to-localtime and it works after syncing the drac's time with ntp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872546 Title: ipmi-oem dell reset-power-consumption-data , timezones, and reporting peak amp times in the future To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1872546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816653] Re: Memory Leak
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gthumb (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/1816653 Title: Memory Leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1816653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866065] Re: weechat python.so not linked against libpython3 (undefined symbol: _Py_NoneStruct)
Bug confirmed in version 2.6-2ubuntu1 (currently in focal/universe). I tested 2.6-2ubuntu2 (currently in focal-proposed/universe) and confirmed that it's fixed there. ** Changed in: weechat (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866065 Title: weechat python.so not linked against libpython3 (undefined symbol: _Py_NoneStruct) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weechat/+bug/1866065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873696] Re: [needs-packaging] notcurses
*** This is an automated message *** This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs- packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist. ** Changed in: 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/1873696 Title: [needs-packaging] notcurses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1873696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873104] Re: Defaults to USB audio after every reboot
I agree. I don't see this as an upstream issue because I have tried it on other distros - they worked as expected. USB hotplugging updates the audio device. However, a reboot simply restores whatever was last in use. For some reason, only on Ubuntu, it treats a reboot as plugging a new USB device. And this occurs on every flavor I tested - Ubuntu, Mate, Kubuntu and Xubuntu. In Kubuntu it can be slightly mitigated because you can set the default from the tray. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873104 Title: Defaults to USB audio after every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1873104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873697] Re: [needs-packaging] Please sync ogre-1.12 from debian sid once more
*** This is an automated message *** This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs- packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist. ** Summary changed: - Please sync ogre-1.12 from debian sid once more + [needs-packaging] Please sync ogre-1.12 from debian sid once more ** Changed in: ogre-1.12 (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1873697 Title: [needs-packaging] Please sync ogre-1.12 from debian sid once more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ogre-1.12/+bug/1873697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858786] Re: Missing preferences menu option
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: meld (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/1858786 Title: Missing preferences menu option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1858786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858786] Re: Missing preferences menu option
Still happening in 20.04 focal... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858786 Title: Missing preferences menu option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1858786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873706] [NEW] Partition manager edit mount point not working..fstab not changed
Public bug reported: I ran parititionmanager to try and mount a windows partition: /media/bradlee/1C9CE9359CE909DA/Users/bradl/OneDrive/Downloads/ to /mnt/windows using the Edit Mount Point feature of the partitionmanager. But after exiting, the changes were not made, the partition was not mounted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: partitionmanager 4.1.0-1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Apr 19 19:16:53 2020 InstallationDate: Installed on 2020-04-16 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: partitionmanager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: partitionmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "I have attached screen snapshots of the test I made and it's also at the following link url: https://imgur.com/a/L5rNsV2; https://bugs.launchpad.net/bugs/1873706/+attachment/5356899/+files/kde%20partition%20mount%20windows%20drive.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873706 Title: Partition manager edit mount point not working..fstab not changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partitionmanager/+bug/1873706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
As mentioned in comment #37 the internal mic works well with Ubuntu 20.04 live mode. I haven't tried installing Ubuntu 20.04 though, as some report the mic doesn't work once installed. I wish I knew more and had the time to understand the difference (beyond kernel) between Ubuntu 20.04 live mode and non-live mode. I'm currently running Ubuntu 19.10. Let me know if there is something I can test to understand why Ubuntu 20.04 live mode works. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Sorry to post so much - I wish I could consolidate or edit all these posts. The next day I came back and it didn't work in Zoom. I tried a bunch of things listed on the following web page, starting with simplest first, from https://support.system76.com/articles/audio/ until finally I did sudo apt install --reinstall alsa-base alsa-utils pulseaudio linux- sound-base libasound2 then I rebooted and sudo alsa force-reload and it worked. Which is weird, I think, because I just did this reinstall of these modules 3 days ago. I don't think the versions of these modules changed. I don't know what's going on. My guess is that it breaks because something changes a configuration file. And then I guess it's fixed when the configuration file is re-initialized by re- installing these modules. I wish I could pinpoint it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872394] Re: Please remove system-integrity-check from Ubuntu
Removing packages from focal: system-integrity-check 0.2 in focal system-integrity-check 0.2 in focal amd64 system-integrity-check 0.2 in focal arm64 system-integrity-check 0.2 in focal armhf system-integrity-check 0.2 in focal ppc64el system-integrity-check 0.2 in focal s390x Comment: unused d-i component, unmaintained since 2007, Ubuntu-specific, FTBFS; LP: #1872394 1 package successfully removed. ** Changed in: system-integrity-check (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/1872394 Title: Please remove system-integrity-check from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-integrity-check/+bug/1872394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1108935] Re: [MIR] websockify, spice-html5
Override component to main spice-html5 0.2.2-0ubuntu1 in focal: universe/misc -> main spice-html5 0.2.2-0ubuntu1 in focal amd64: universe/web/extra/100% -> main spice-html5 0.2.2-0ubuntu1 in focal arm64: universe/web/extra/100% -> main spice-html5 0.2.2-0ubuntu1 in focal armhf: universe/web/extra/100% -> main spice-html5 0.2.2-0ubuntu1 in focal i386: universe/web/extra/100% -> main spice-html5 0.2.2-0ubuntu1 in focal ppc64el: universe/web/extra/100% -> main spice-html5 0.2.2-0ubuntu1 in focal riscv64: universe/web/extra/100% -> main spice-html5 0.2.2-0ubuntu1 in focal s390x: universe/web/extra/100% -> main 8 publications overridden. ** Changed in: spice-html5 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1108935 Title: [MIR] websockify, spice-html5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1108935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-trident 1:1.3.8-1build2 in focal xserver-xorg-video-trident 1:1.3.8-1build2 in focal amd64 xserver-xorg-video-trident 1:1.3.8-1build2 in focal arm64 xserver-xorg-video-trident 1:1.3.8-1build2 in focal armhf xserver-xorg-video-trident 1:1.3.8-1build2 in focal ppc64el xserver-xorg-video-trident 1:1.3.8-1build2 in focal riscv64 xserver-xorg-video-trident 1:1.3.8-1build2 in focal s390x xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal amd64 xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal arm64 xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal armhf xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal ppc64el xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal riscv64 xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-trident (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/1772588 Title: Remove obsolete X11 drivers from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from focal: xserver-xorg-video-geode 2.11.20-1 in focal Comment: obsolete source package, only builds xserver for i386 which is not supported as a host arch; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-video-geode (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/1772588 Title: Remove obsolete X11 drivers from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal amd64 xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal arm64 xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal armhf xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal ppc64el xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal riscv64 xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal s390x xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal amd64 xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal arm64 xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal armhf xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal ppc64el xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal riscv64 xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-sisusb (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/1772588 Title: Remove obsolete X11 drivers from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal amd64 xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal arm64 xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal armhf xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal ppc64el xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal riscv64 xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal s390x xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal amd64 xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal arm64 xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal armhf xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal ppc64el xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal riscv64 xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-siliconmotion (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/1772588 Title: Remove obsolete X11 drivers from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-tdfx 1:1.5.0-2 in focal xserver-xorg-video-tdfx 1:1.5.0-2 in focal amd64 xserver-xorg-video-tdfx 1:1.5.0-2 in focal arm64 xserver-xorg-video-tdfx 1:1.5.0-2 in focal armhf xserver-xorg-video-tdfx 1:1.5.0-2 in focal ppc64el xserver-xorg-video-tdfx 1:1.5.0-2 in focal riscv64 xserver-xorg-video-tdfx 1:1.5.0-2 in focal s390x xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal amd64 xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal arm64 xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal armhf xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal ppc64el xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal riscv64 xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-tdfx (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/1772588 Title: Remove obsolete X11 drivers from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-r128 6.12.0-1 in focal xserver-xorg-video-r128 6.12.0-1 in focal amd64 xserver-xorg-video-r128 6.12.0-1 in focal arm64 xserver-xorg-video-r128 6.12.0-1 in focal armhf xserver-xorg-video-r128 6.12.0-1 in focal ppc64el xserver-xorg-video-r128 6.12.0-1 in focal riscv64 xserver-xorg-video-r128 6.12.0-1 in focal s390x xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal amd64 xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal arm64 xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal armhf xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal ppc64el xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal riscv64 xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-r128 (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/1772588 Title: Remove obsolete X11 drivers from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
